Техническая Инструкция для Cisco Cisco Nexus 5010 Switch

FIP Capable ? : TRUE

UP using DCBX ? : FALSE

Peer MAC : 00:c0:dd:22:79:39

PSS VN Port data:-

FC ID 0xA00000 -

vfc index 503316584 vfc name vfc105

vsan id 70

enode_mac 00:c0:dd:22:79:39

vfc wwn 50:0a:09:81:98:fd:66:a5

Before the output is continued...

The output contains a few useful pieces of information. It verifies current status, shows the actual
binding between VFC and portchannel and the actual state of the VFC on the VSAN. It shows
transitions between different states outlined in the diagram before the interface comes up. VLAN
discovery is performed and FIP solicitation is received and answered which allows the VFC to
come up.

Continuation of the output....

17) FSM:<vfc105> Transition at 554094 usecs after Sat Sep 27 22:48:06 2014

Previous state: [FCOE_MGR_VFC_ST_PHY_UP]

Triggered event: [FCOE_MGR_VFC_EV_BRING_UP]

Next state: [FSM_ST_NO_CHANGE]

18) FSM:<vfc105> Transition at 685820 usecs after Sat Sep 27 22:48:07 2014

Previous state: [FCOE_MGR_VFC_ST_PHY_UP]

Triggered event: [FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY]

Next state: [FSM_ST_NO_CHANGE]

19) FSM:<vfc105> Transition at 686781 usecs after Sat Sep 27 22:48:07 2014

Previous state: [FCOE_MGR_VFC_ST_PHY_UP]

Triggered event: [FCOE_MGR_VFC_EV_FIP_SOLICITATION]

Next state: [FSM_ST_NO_CHANGE]

Curr state: [FCOE_MGR_VFC_ST_PHY_UP]

There a couple of known and common problems with the FCoE configuration that the Data Center
Networking Solutions Technical Assistance Center team sees reoccur.

Trunk protocol - The trunk protocol needs to be up. 

bdsol-n5548-05# show trunk protocol

Trunk Protocol is enabled.

●

NetApp 8.2.2 and Nexus 5500/5600 that run NX-OS 7.x software. At the time that the
document was written, a known problem between these two versions exists and is under
investigation by Cisco and NetApp. Versions 6.x and 5.x of NX-OS work fine with NetApp
8.2.2.

●

●

●