Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

moving port channel / ethernet uplinks to new switch

We have a pair of UCS 6248 Fabric Interconnects.  We need to move the ethernet uplinks to a new set of switches.  Is there any specific process for doing this?  We have two ethernet uplinks setup in a port channel on each of the Fabric Interconnects?  I was thinking of doing the following:


1)  disable the port channel on the subordinate Fabric Interconnect

2)  ensure that there are no issues with any of the machines that are running in the environment / validate connectivity

3)  move the cables for the ethernet uplinks to the new switch

4)  bring up the port channel

5)  validate the port channel comes up and that connectivity looks good.

6)  repeat the process on the primary Fabric Interconnect.


How do I validate that the new port channel has good network connectivity prior to disabling the port channel on the primary Fabric Interconnect.  I know I can look at the stats for the ports to validate that traffic is going down them and that there are no errors.



  • Unified Computing
Everyone's tags (1)
Cisco Employee

Russ,I assume you have set


I assume you have set the vNICs for fabric failover. Please correct me if assumption is incorrect. If you have fabric failover enabled, then there will VIFs instantiated and up on the  secondary fabric interconnect too though these vnics will be in standby state.

You can check whether all these vnics are pinned to its uplink(new port-channel) using the 'show pinning border-interface' command. From the upstream switch, you need to make sure all the required vlans are passing and STP states are in forwarding state. After failover, you can check if all the server MACs are being learnt upstream.

Hope this helps.




This widget could not be displayed.