I have a Nexus 5548UP switch running version 5.2(1)N1(1b) and a UCS C240 M3S with firmware version 1.4(7b) directly attached via a 10G link (fiber) between the switch port and a UCS VIC P81E in slot 2 of the C240 (Eth 1/32 to port 0 on the P81E).
- I have set the default vlan on the vHBA to vlan 1 9the same as the trunk on interface Eth 1/32)
- FIP is enabled on the VIC P81E
- The switch configuration is attached:
Any thoughts on why the VIC P81E does not seem to respond to the FIP and then perform a flogi? I assume an operating system on the C240 is not required, however am I wrong here?
Let me know and thanks.
Below is output from interface vfc 20
Message was edited by: Edward Storey More information: As it turns out when I run the command "sh platform software fcoe_mgr info interface vfc 4" there is no appearance of the following event "[FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY]". So it appears the FCoE vlan discovery never takes place and so no FIP solicitation. This must be why the state of the vsan continues to be "Vsan 20 is down (waiting for flogi)". I think? Any thoughts?
Message was edited by: Edward Storey So first, I have answered my own question regarding needing an operating system with the correct driver for the Cisco P81E VIC to make this work and the answer is yes. Clearly the P81E cannot produce a flogi to the vsan without a fibre channel software stack loaded. As for the configuration of the switch, it appears I had the correct configuration all along, however what was confusing was the “native vlan” property on the vHBA on the P81E VIC. In some posts the direction was to make it the same as the “native vlan” of the 5548UP Ethernet trunking interface and in at least one document it indicated to use the designated FCoE vlan for the vsan. For my successful test the answer was to use the designated FCoE vlan for the vsan as the “native vlan” property on the vHBA. The only other property I believe I made sure was enabled on the P81E was the “FIP mode”. My test was to try an installation of ESXi 5.0 (VMware-VMvisor-Installer-5.1.0.update01-1065491.x86_64) which, based on other posts, has the correct P81E driver. When the installation came to the point where it was ready to scan for devices I was then able to see the entry in the “flogi database” on the 5548UP. My next test will be to attach an array on the 5548UP and present a LUN from it to see if I can complete the ESXi 5.0 installation. The following command “sh platform software fcoe_mgr info interface vfc 20” was invaluable in understanding the FCoE establishment process on the vfc. When I saw the following event “Triggered event: [FCOE_MGR_VFC_EV_FIP_SOLICITATION]” then the flogi entry showed in the “flogi database”. I have attached another configuration document, since I made a couple of changes to vlan numbers and used a different Ethernet interface. Lastly, I saw the postings regarding the QoS configurations, however from what I can see my system already had the default system QoS configurations for FCoE.
