Hi, I need a simple DCB or with Cisco wording FCoE pass through switch for a special test case. According to my current experience the Nexus does not pass through FIP VLAN Requests per default. All FCoE related features are disabled (again I do not need any FCF functionality)  and the switch keeps sending DCBX TLVs like I want him to. Only thing missing is the FIP pass through. Can anybody tell me the appropriate configuration to make him do that or is it not possible. Any help would be highly appreciated. Thank you! ... View more

Hi there, I don't have any clue what this problem might be so please help. I have a brandnew FEX 2232TM which is connected to a NEXUS 5010P running the following firmware: oftware   BIOS:      version 1.5.0   loader:    version N/A   kickstart: version 5.2(1)N1(1)   system:    version 5.2(1)N1(1)   power-seq: Module 1: version v1.2   BIOS compile time:       11/30/10   kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.1.bin   kickstart compile time:  7/12/2012 19:00:00 [07/13/2012 02:08:13]   system image file is:    bootflash:///n5000-uk9.5.2.1.N1.1.bin   system compile time:     7/12/2012 19:00:00 [07/13/2012 03:23:16] According to the Cisco download page it is the latest version and should definitely support the 2232TM. The problem is that the FEX is completely not recognized by the parent Nexus. It is connected via 8 FET modules. But when ich check the light on both sides I only have light on the NEXUS side never on the FEX side on all modules. From my understanding this should be the root cause of the issue because no light = no link. I tried standard 10GBase-SR and Twinax cables as well. Same behavior - the FEX is not recognized. The status LED if of course orange on the FEX. This is the FEX related config ont he NEXUS: feature fex fex 101   pinning max-links 8   description "FEX0101" interface Ethernet1/1   switchport mode fex-fabric   fex associate 101 interface Ethernet1/2   switchport mode fex-fabric   fex associate 101 interface Ethernet1/3   switchport mode fex-fabric   fex associate 101 interface Ethernet1/4   switchport mode fex-fabric   fex associate 101 interface Ethernet1/5   switchport mode fex-fabric   fex associate 101 interface Ethernet1/6   switchport mode fex-fabric   fex associate 101 interface Ethernet1/7   switchport mode fex-fabric   fex associate 101 interface Ethernet1/8   switchport mode fex-fabric   fex associate 101 Can anyone give me a hint what I am missing here?? Any help is really appreciated. Thanks a lot! ... View more

Hi, I would like to ask if anyone else experienced issues with Priority-Flow-Control after updating his Nexus 5000 to firmware 5.1(3)N1(1). I have a Fujitsu DCB switch connected to the Nexus and the setup worked fine before the FW update. But now I get errors in the DCBX TLVs and PFC gets disabled after a short while on the Nexus side. Which information should I post here so that anyone could get a cleue on this? Thanks! ... View more

Hi there, imagine the following (simple) configuration: - Server with dual port CNA connected to a N5k - CNA port 1 connected to interface Ethernet 1/9 - CNA port 2 connected to interface Ethernet 1/10 - CNA FCoE MAC port 1 bound to vfc 109 - CNA FCoE MAC port 2 bound to vfc 110 - CNA NIC ports as well as the corresponding connected Nexus ports e1/9 & e1/10   are configured as LACP 802.3ad port-channel - Storage subsystem connect to N5k native FC port Coming from the Ethernet world one could say how can this work because the LAG hash makes the traffic flow undeterministic but the N5k is a FCF and is therefore FCoe/FC traffic aware. For example you won't find the FCoE MACs vound to the vFCs in the MAC-address-table. It separates the FCoE/FC wordl from the Ethernet world. So a FCoE multipathing setup with a underlying LAGs/port-channels isn't a problem because Nexus takes care of this scenario. (As far as I know Brocade does not support that - does that mean an FCF switch is not equal an FCF?) But what I am curious about to know is how that exactly works internally. More precise, can someone tell me a command how to find out the physical port where the Nexus learnt the FCoE MAC which is bound to a vFC? The Nexus must have this information somewhere because otherwise the scenario described above wouldn't work. Please let me know if you have any hints. Thx and have a nice weekend! ... View more

Hi there, I've got the follwoing problem, I would like to enable the QoS policy statistics on my Nexus 5010 running  firmware 5.0(3)N2(2a). This is where I am at: nexus# show policy-map interface Global Statistics status : enable Ethernet1/1      Service-policy (qos) input:      default-in-policy           policy statistics status:     disabled      ...      Service-policy (queuing) input:     default-in-policy           policy statistics status:          disabled      ...      Service-policy (queuing) output: adapted-out-policy           policy statistics status:        disabled As you can see I managed to enable the statistics globally via "(config)# qos statistics" but I don't have any clue how to enable  the statistics for every service-policy on every interface. The config guides and examples already had them enabled but didn't mention the corresponding command(s). I really hope someone can help me on this. Thanks in advance! Greetings! ... View more

Hi there, I have virtualized my CNA WWNs to WWNN=50:00:00:00:00:00:00:c1 WWPN=50:00:00:00:00:00:00:c0 and it looks like there is no Fabric Login possible anymore. The Nexus 5020 keeps suspending the VFC because of too many invalid FLOGIs. Does anyone have an idea why? The response to the FLOGI I see with Wireshark is an LS_RJT (LinkService Reject) but unfortunately it only contains an unknown reason code. So no help from this side. Is there anything special about the used WWNs? Because if I use these WWNs on a FC HBA in conjunction wioth a Brocade Fabric it works perfect. Any hint is highly welcome. Thx! ... View more