UCS vSAN FC Port-Channel – Isolation due to channel mis-configuration on local or remote switch
October 15, 2018
If you are getting similar error such as this: “2018 Oct 15 17:20:05 N5K1 %PORT-5-IF_DOWN_BUNDLE_MISCFG: %$VSAN 101%$ Interface fc1/44 is down (Isolation due to channel mis-configuration on local or remote switch) san-port-channel 101″ when configuring san-port-channel on your Nexus down to the Fabric Interconnects make sure you have the proper port-channel mode.
By default UCS FI’s will use active mode. Which is familiar behavior to ethernet but here you need to define active mode actually on the san-port-channel and not the interfaces.
Log prior applying active mode where san-port-channel is empty:
N5K2(config-vsan-db)# sh run int san-port-channel 101 interface san-port-channel 101 2018 Oct 15 17:20:05 N5K1 %PORT-5-IF_DOWN_BUNDLE_MISCFG: %$VSAN 101%$ Interface fc1/44 is down (Isolation due to channel mis-configuration on local or remote switch) san-port-channel 101 2018 Oct 15 17:20:09 N5K1 %PORT-CHANNEL-5-FOP_CHANGED: san-port-channel 101: first operational port changed from fc1/45 to none 2018 Oct 15 17:20:09 N5K1 %PORT-CHANNEL-5-PORT_DOWN: san-port-channel 101: san-port-channel 101 is down 2018 Oct 15 17:20:09 N5K1 %PORT-5-IF_DOWN_NONE: %$VSAN 101%$ Interface san-port-channel 101 is down (None) 2018 Oct 15 17:20:09 N5K1 %PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: %$VSAN 101%$ Interface san-port-channel 101 is down (No operational members)
After applying additional configuration:
N5K1(config-if)# sh run int san-port-channel 101 interface san-port-channel 101 channel mode active switchport trunk allowed vsan 101 2018 Oct 15 17:24:17 N5K1 %PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: %$VSAN 101%$ Interface san-port-channel 101 is down (No operational members) 2018 Oct 15 17:24:36 N5K1 %PORT-5-IF_UP: %$VSAN 101%$ Interface san-port-channel 101 is up in mode F
Something easy to overlook especially when fighting against time.
Thanks,
Bart
Reference: