FC Port-Channel not working with BIOS v.3.6.0

ataranen · ‎01-26-2014

Hello,

I have downgraded one of the new FIs (6248UP) I just purchsed from version 2.1 to 2.0(5a). It is connected in a cluster with another 6248UP. The only difference between them is the BIOS version - the new 3.6.0 the old 3.5.0. The FC port-channel on the new FI refuses to work. The FC connections without port-channel work fine and register with NPIV mds switch, but the port-channel always shows Link Failure after it tries to come up for about 3 minutes. Anyone has an idea why FI downgraded from 2.1 to 2.0 won't function for FC port-channel?

Manuel Velasco · ‎01-26-2014

Hi Ataranen,

Was the fabric able to form the port-channel with the MDS switch when the fabric was running firmware 2.1?

Where do you see the firmware version on the fabric?

Can you run the following command on the fabric interconnect that is not able to form the port channel?

F-A# connect nxos

F-A(nxos)#show interface eth 1/1

What is the model of your MDS switch?

What software version is the MDS running?

ataranen · ‎01-26-2014

Hello,

I didn't test it with firmware 2.1, I will give it a try. I installed the latest 2.0 package - 2.0(5f). Below is the show version, and show interface. MDS model is 9222i with NX-OS 5.2. It works well with all my other FIs running firmware 2.0 and connected with SAN Port-Channel. The problem is only with that new FI that just came in, and the only difference I see with my old FI is the BIOS version 3.6. I eliminated all other problems - moved cables around, used different MDS ports.

The problem is only with SAN Port-Channel. Individual FC interfaces register with NPIV just fine.

dc101-B(nxos)# show interface e1/1

Ethernet1/1 is down (Link not connected)

Hardware: 1000/10000 Ethernet, address: 002a.6a3c.1d28 (bia 002a.6a3c.1d28)

Description: S: Server

MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA

Port mode is trunk

auto-duplex, 10 Gb/s, media type is 10G

Beacon is turned off

Input flow-control is off, output flow-control is off

Rate mode is dedicated

Switchport monitor is off

EtherType is 0x8100

Last link flapped never

Last clearing of "show interface" counters never

30 seconds input rate 0 bits/sec, 0 bytes/sec, 0 packets/sec

30 seconds output rate 0 bits/sec, 0 bytes/sec, 0 packets/sec

Load-Interval #2: 5 minute (300 seconds)

input rate 0 bps, 0 pps; output rate 0 bps, 0 pps

RX

0 unicast packets 0 multicast packets 0 broadcast packets

0 input packets 0 bytes

0 jumbo packets 0 storm suppression bytes

0 giants 0 input error 0 short frame 0 overrun 0 underrun 0 watchd

og 0 if down drop

0 input with dribble 0 input discard

0 Rx pause

TX

0 unicast packets 0 multicast packets 0 broadcast packets

0 output packets 0 bytes

0 jumbo packets

0 output errors 0 collision 0 deferred 0 late collision

0 lost carrier 0 no carrier 0 babble

0 Tx pause

0 interface resets

dc101-B(local-mgmt)# show version

System version: 2.0(5f)

dc101-B(nxos)# show version

...................

.....

Software

BIOS: version 3.6.0

loader: version N/A

kickstart: version 5.0(3)N2(2.05f)

system: version 5.0(3)N2(2.05f)

power-seq: Module 1: version v2.0

mds1(config-if)# show version

..........

.......

Software

BIOS: version 1.0.12

loader: version N/A

kickstart: version 5.2(2d)

system: version 5.2(2d)

Manuel Velasco · ‎01-26-2014

Hi Araranen,

There is no need to upgrade the firmware to 2.1 this won't resolve the issue. From What I can tell this is a problem with your MDS as it doesn't recognizes the OUI of the new UCS fabric interconnect (see defect below)

dc101-B(nxos)# show interface e1/1

Ethernet1/1 is down (Link not connected)

Hardware: 1000/10000 Ethernet, address: 002a.6a3c.1d28 (bia 002a.6a3c.1d28)

Add N7K OUIs to liboui's list of recognized Cisco OUIs

https://tools.cisco.com/bugsearch/bug/CSCtr01652

also

Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI

https://tools.cisco.com/bugsearch/bug/CSCty04686

The fix to this problem is to upgrade the software on the MDS to at least (version 5.2(8)) or later where this OUI was added to the MDS file system.

Please rate all useful posts

Arseny Taranenko · ‎01-27-2014

Hi Manuel,

you are the man. My problem was solved after upgrading mds to 5.2.8c. Thank you very much for the help.

mds1# show version

......

Software

BIOS: version 1.0.12

loader: version N/A

kickstart: version 5.2(8c)

system: version 5.2(8c)

BIOS compile time: 09/10/07

kickstart image file is: bootflash:///m9200-s2ek9-kickstart-mz.5.2.8c.bin

kickstart compile time: 12/25/2020 12:00:00 [10/23/2013 06:42:57]

system image file is: bootflash:///m9200-s2ek9-mz.5.2.8c.bin

dc101-B(nxos)# show interface san-port-channel 200

san-port-channel 200 is trunking

Hardware is Fibre Channel

Port WWN is 24:c8:00:2a:6a:3c:1d:40

Admin port mode is NP, trunk mode is on

snmp link state traps are enabled

Port mode is TNP

Port vsan is 1

Speed is 8 Gbps

Trunk vsans (admin allowed and active) (1,200)

Trunk vsans (up) (200)

Trunk vsans (isolated) (1)

Trunk vsans (initializing) ()

1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec

1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec

845 frames input, 46964 bytes

0 discards, 0 errors

0 CRC, 0 unknown class

0 too long, 0 too short

1451 frames output, 211896 bytes

0 discards, 0 errors

31 input OLS, 31 LRR, 65 NOS, 0 loop inits

88 output OLS, 94 LRR, 117 NOS, 0 loop inits

last clearing of "show interface" counters never

Member[1] : fc1/9

Member[2] : fc1/10

Interface last changed at Mon Jan 27 17:29:23 2014

Manuel Velasco · ‎01-27-2014

I am glad this worked for you!!