right now vlan 2 is connected to the 6500's via mgmt0. I am worried that if I bring up the trunk ports back to the 6500's the I will have an issue with vlan 2 being seen on mgmt0 and the trunk ports.

So you have a connection from the 5010 to the 6500 and the port is an access port allocated to vlan 2 ?

If so then you have a choice

1) include it on the trunk link and allow one of the connections to block for vlan 2

or

2) do not allow vlan 2 on the trunk link and then you will simply be using the access port link from the 6500 to the 5010

1) would provide some redundancy in case of failure of the access port link altho you could simply add vlan 2 to the trunk link if the access link went down to give you temporary access.

Jon

thanks good advice

Glad to have helped.

Jon

I don't think this is technically right- the MGMT and the data-path aren't actually connected. The MgmT 0 port doesn't have any concept that it's on "vlan 2"- it's just an access port.

Similarly, if VLAN 2 is on the trunk port, the IP address you assigned to MGMT0 isn't going to respond.

If you configured "feature interface vlan" and then put an IP address on VLAN 2, you could mange this box that way- on two separate IP addresses, via the two separate connections.

With the current lack of ability to wrap ACLs around the Interface VLANs, I'm more comfortable NOT using interface-vlan commands, and using a single uplink to mgmt0. Loss of the mgmt0 port is now only loss of the ability to manage the switch, not a data-path impacting event. (unless you need to configure the switch to correct an data-path issue, in which case you've got problems.)

The shift to out-of-band is a nice feature, but it's going to require a big shift in thinking from an implementation standpoint.