I am seeing a weird behaviour with this Nexus 5548p-2 switch. My interfaces are configured for FCoE. Initiator logs into the switch stay on name server for a few minutes and then logs out. If i go and do a disable/enable at the pcie device on the windows host, it logs in back but then again after few minutes it logs out. I did a write erase in the switch, begin the config from scratch but no help.
If i look at the eth config fcoe status it shows up. Why not pwwn printed in the command below?
I want to add one more question to the original one. This is regarding vfc. From the above "show int vfc1" look at the "initializing" key word. (highlighted above). I guess this started happening after release of 5.0.x firmware. In 4.2.x i did not see this. Now what this "initializing" stands for? Also why do we need Trunking at a port where a initiator to be connected ?
I used to remove trunking from vfc and add only the vsan which it is part of. I am not sure if doing that is right. But many times it resolves my initializing problem.
c5548p-2(config-if)# no switchport trunk allowed vsan all
Thanks Kris for your valuable reply. I have not tried to make the VLAN change on the ethernet int like you have shown above. In my previous experiences i got similar issue resolved by changing it on the vfc interface alone. On VLAN VSAN association i have similar config that you have shown on the example. On a educational based, i want to know what made cisco to choose TF port for vfc? In reality only one VN_port can get attached to it.
What ever i tried the issue did not go away.
Finally i resorted to borrow a switch config from another C5548p switch we have on the lab and apply it to the not working switch. That tricks seemed to work. I had to change the mgmt ip address after applying the config. I saved the earlier not working config. Still have to scan through it to find out what was missing or wrong. Traditionally cisco Nexus switches are found to be more stable on FCoE than other vendor. This time only this was stuck at the corner.
Re: Nexus 5548p-2 fcoe initiator wont stay logged in
It sounds like you have an issue with FIP Keep Alive. If the 5548 does not recieve a keep alive within 2.5 times the Keep Alive Timeout value, it will log the end device out. Since you are saying it happens after a few minutes, this could mean the VN_Port keep alive is not being received by the switch and since FKA_VN_PERIOD = 90 seconds by default, the CNA would be logged out after 2.5 * 90 or 225 seconds..
I think I've seen this issue before but it was NX-OS or CNA driver specific. Since you are running a recent version of NX-OS, Im inclined to think the problem could be related to the end device you are using.
On the logical analysis front you are exactly right. The initiator did not send FKA for more than 2.5 times the FKA period. This resulted sewitch to send CVL. But when i move the same initiator to ther working sewitch it satyed logged in for long. Interestingly, Netapp target never logged into the switch. If i move the same target to another switch it logged in. I have not seen a issue like this before at cisco nexus switch.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...