Hi all.
I have : nexus 5548UP (5.0(3)N2(1)) with nexus 4000 in Bladecenter-H (last code 4.1(2)E1(1g)).
The config is quite basic and compliant with all best-practices.
Everything went fine until we saw some strange things, we decided to reboot everything. One of the strange things was that my vfc has gone into TF (Trunking F port) at some point, which is totally unexpected. When everything worked it ran as a standard F port. Now trunk mode is "on" on the vfc, I don't know if it's normal or not.
Now I have a VFC which is stuck in "down (Initializing)" state.
N5K-01# show interface vfc 103
vfc103 is down (Initializing)
Bound MAC is 00:c0:dd:1b:82:c5
Hardware is Virtual Fibre Channel
Port WWN is 20:66:54:7f:ee:08:ec:bf
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port vsan is 2
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
0 frames input, 0 bytes
0 discards, 0 errors
0 frames output, 0 bytes
0 discards, 0 errors
last clearing of "show interface" counters never
The VFC is correctly bound to the right mac-address learnt via fip-snooping
N5K-01# show run int vfc 103
interface vfc103
bind mac-address 00:c0:dd:1b:82:c5
no shutdown
N5K-01#
NX-BCH1-M7# show fip-snooping vlan-discovery
Legend:
-------------------------------------------------------------------------------
Interface VLAN FIP MAC
-------------------------------------------------------------------------------
Eth1/3 1 00:c0:dd:1b:82:c5
NX-BCH1-M7#
I believe it's "down (Initializing)" because of FIP negociation not complete ?
Upstream FCF is seen from the 4000
NX-BCH1-M7# show fip-snooping fcf
Legend:
-------------------------------------------------------------------------------
Interface VLAN Active FPMA/ FCMAP FCF-MAC Pri Switch WWN Fabric Name
Enodes SPMA
-------------------------------------------------------------------------------
por2 600 0 FPMA 0x0efc00 54:7f:ee:08 128 10:00:00:05: 10:00:00:05:
:ec:a7 1e:90:4a:0b 1e:90:4a:0b
por2 600 0 FPMA 0x0efc00 54:7f:ee:08 128 10:00:00:05: 10:00:00:05:
:ec:a6 1e:90:4a:0b 1e:90:4a:0b
No more session or enode detected through the 4000 (it was working before)
NX-BCH1-M7# show fip-snooping enode
NX-BCH1-M7# show fip-snooping sessions
NX-BCH1-M7#
It seems that the driver on the host still sends FIP messages as I can read on the 4000
NX-BCH1-M7# show fip-snooping counters interface ethernet 1/3
Legend:
-------------------------------------------------------------------------------
Interface Name Counter Desciption Value
-------------------------------------------------------------------------------
Ethernet1/3 Unicast packets received 0
Multicast packets received 9
Vlan discovery packets received 9
Vlan discovery response packets received 0
flogi (fabric login) packets received 0
flogi lsacc (acknowledgment) packets received 0
flogi lsrjt (reject) packes received 0
fdisc packets received 0
fdisc lsacc received 0
fdisc lsrjt received 0
logo (logout) packets received 0
logo lsacc received 0
logo lsrjt received 0
Enode Keepalive received 0
Enode Discovery received 0
FCF Discovery Solicit received 0
FCF Keepalive received 0
Clear Virtual Link received 0
Clear Virtual Link generated 0
Unicast packets transmitted 0
Packets dropped due to invalid length 0
Packets dropped due to tlv parse error 0
Packets dropped due to unsupported tlv 0
Packets dropped due to fcmap mismatch 0
NX-BCH1-M7# show lldp traffic interface ethernet 1/3
LLDP traffic statistics:
Total frames out: 44
Total Entries aged: 0
Total frames in: 43
Total frames received in error: 0
Total frames discarded: 0
Total TLVs unrecognized: 0
NX-BCH1-M7#
My last idea is to configure a SPAN session on the 5000 and see with wireshark what is going on. Are there any extra commands that can help me before sniffing ? (show, debug...)
I suspect an issue on the host, where can I find the compatibility matrix for FCoE ?
