Nexus 5596 and Qlogic 8150

I am having a problem with getting the Qlogic 8150 working in a windows 2008 R2 server. I have the SAN connectivity working but I am having problem with the networking.
I have setup VLAN 666 as the data vlan
On the ethernet trunk I have setup
ethernet 1/17
switchport mode trunk
switchport trunk allowed vlan 666 spanning-tree port type edge trunk
This does not work but if I allow VLAN 1 on the trunk it works and I have full IP connectivity.
switchport trunk allowed vlan 666,1 Any ideas why adding VLAN 1 on the trunk makes everything workThanks

You set vlan 666 as the VlanID under the Qlogic adapter advanced properties, right? Should be the last value in the scroll box.

Similar Messages

Trunking nexus 5596 and netapp or exsi issue

hi
i have 2 issues with trunking between nexus 5596 and a esxi server .....can not get the servers to ping out
and the netapp connected to the same 5596 cannot ping.
if the server is a access port it works fine.
is there any tricks that are required to be configured on the nexus to make this work.

Make sure we are actually tagging for those vlans on the host (Netapp/ESXi). If we are not, then this would explain why it works in access mode on the switch.

Nexus 5596 and QOS config guide

Hi,
I need to implement qos on a nexus device for a client
Basically what I am trying to implement is this but on the nexus
Policy Map Enhanced_QoS_Customer_Out
      Description: Enhanced QoS customers outbound Percentages
    Class Cust_VoIP_Out
      priority 30 (%)
    Class Cust_Gold_Out
      bandwidth 30 (%)
    Class Cust_Silver_Out
      bandwidth 13 (%)
    Class Cust_Bronze_Out
      bandwidth 2 (%)
Policy Map Ethernet_QoS_Customer_Out_200Mb
    Class class-default
      Average Rate Traffic Shaping
      cir 200000000 (bps)
      service-policy Enhanced_QoS_Customer_Out
Is this possible on the nexus 5596?
I havent found much information around shaping.. Please advise if the above policy is achelievable on the nexus and if not what does the nexus support?
regards,

Hi,
I don't think the 5500 support shaping since it is mostly a layer-2 device. Here is the config guide for QOS.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/QoS.html
HTH

Connect Nexus 5600 and Qlogic

Hi,
Have a new DC solution with Nexus 56128 switches running LAN + Native FC.
Storage Arrays shall be connected to the Nexus switches via 8G FC
Customer has Dell blade with Qlogic SAN switches, where existing zoning is done. Today these are connected to the Storage Array.
Is it possible to connect the Qlogic switches to Nexus and disconnect the Storage from Qlogic?
Dell blade server -> Qlogic FC switch -> Nexus FC switch -> EMC VNX Storage
Thinking about interoperability issues between Nexus and Qlogic.
/Jorgen

Hi,
No problem with that, just bear in mind that you have to configure NPV mode (or the equivalent qlogic name...) on the qlogic switch.
Rgds,
Felipon

Cisco Nexus 5596 and Brocade 5300 compatibility

Hi
We have designed the SAN network with Brocade5300 connected to Nexus5596. we want to know about the campatibility of these two switches.
I can't find any compatibility matrix with this detail.
i would appreciate it if you let me know about your experience.
Thank you

Amir,
Check this.
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html
I am not sure how recent it is and when this testing was done. I would suggest you to run " Gateway mode" AKA NPIV mode for Cisco and test this with Brocade 5300. It should work fine.
Hope this helps.
Cheer,-amit singh

Nexus 5596 and N55-M4Q

In this document:
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/interfaces/602_n1_1/N5K_Interfaces_Ops_Guide/n5k_qsfp-_portsoperations.html
I read that "There is no additional configuration needed to specify the operation mode of the QSFP+ ports because all the ports only operate in 4 x10 Gigabit Ethernet mode". Is this hw or sw related? If sw, when will it be available for running 40G instead og 4x10G?
Geir

Hi,
I don't think the 5500 support shaping since it is mostly a layer-2 device. Here is the config guide for QOS.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/QoS.html
HTH

VPC trouble - link flapping between C3750 stack and Nexus 5596

Hi All,
I have configured 1 vPC's between 2 Nexus 5596 and 1 stack C3750 switch. The links in the stack are distributed over both members.
Gi1/1/1 -> Eth 1/44 NX 5596-02
Gi 2/1/1 -> Eth 1/45 NX 5596-02
Gi 1/1/2 -> Eth 1/46 NX 5596-01
Gi 2/1/2 -> Eth 1/47 NX 5596-01
The same logic is for another stack C3750 to the same pair of Nexus 5596 switches.
The problem is that the links from the vPCs keep flapping at random moments - 1-2 times per hour.
The network is not loaded at this time and the same issue is on both vPC's.
the flaps in the nexus 5596 looks like this
%ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel108: Ethernet1/44 is down
%ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel108: first operational port changed from Ethernet1/44 to Ethernet1/45
%ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/44 is down (Initializing)
%ETH_PORT_CHANNEL-5-PORT_UP: port-channel108: Ethernet1/44 is up
%ETHPORT-5-IF_UP: Interface Ethernet1/44 is up in mode trunk
On the stack is just up/down the pair interface.
I started few debugs on the stack and captured the folowing output:
C3750X-02#im_if_stack_relationship_add: Posting the ACP job for stack add for 5018.10902
im_if_stack_relationship_add: Posted the ACP job for stack add successfully
im_add_ifstackentry: higher_if_index = 5018 lower_if_index = 10902
im_add_ifstackentry: Failed to delete nolayerelem from NoLowerLayerTree for higher_ifIndex = 5018
im_add_ifstackentry: Failed to delete nolayerelem from NoHigherLayerTree for lower_ifIndex = 10902
im_add_ifstackentry: Deleted nolayerelems from NoHigherLayerTree and NoLowerLayerTree
im_add_ifstackentry: Failed to insert stackelem into StackTree
Jul 12 03:35:26.122: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/1/2, changed state to downim_if_stack_relationship_add: Posting the ACP job for stack add for 5018.10902
im_if_stack_relationship_add: Posted the ACP job for stack add successfully
im_add_ifstackentry: higher_if_index = 5018 lower_if_index = 10902
im_add_ifstackentry: Failed to delete nolayerelem from NoLowerLayerTree for higher_ifIndex = 5018
im_add_ifstackentry: Failed to delete nolayerelem from NoHigherLayerTree for lower_ifIndex = 10902
im_add_ifstackentry: Deleted nolayerelems from NoHigherLayerTree and NoLowerLayerTree
im_add_ifstackentry: Failed to insert stackelem into StackTree
Jul 12 03:35:29.058: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/1/2, changed state to up
Do someone have any idea what happens here ?
The configuration is ok because i have another vPC connected to FEX's and is working fine.
Kind regards,

Hello,
Problem solved after upgrade to the last version of NX OS 6.0.2.N2.3
BR,

Nexus 5596 FC-Port Link-Events

Hi all,
int the last 3 weeks,
almost every day , we have a series of events in the connection between one Nexus 5596 and one of our servers. The connection is in FC (4G).
I need help to understand the output of the following command to troubleshoot what could be happening.
Sw-cpd-mm-n5k-2# show hardware internal fc-mac 3 port 14 link-event
MMDDYY           HHMMSS usecs                                 Event                                      Current State
-                          -                                                                                                      LINK_ACTIVE
100113              020845 773895 (0001)                              E_LINK_IDLE                               LINK_LRR_RX
100113              020845 765016 (0000)                           E_LINK_LRR                           LINK_LR_TX
100113              020845 763545 (61CB28)                       E_LINK_LINK_RESET             LINK_ACTIVE
Sw-cpd-mm-n5k-2# show hardware internal fc-mac 3 port 14 port-event
MMDDYY               HHMMSS usecs                              Event                                                     Current State
-                              -                                                                                                        IPS_LINK_UP
100113                 020845 775908 (0000)                        E_IPS_LINK_INIT_SUC                   IPS_LINK_UP
100113                 020845 775907 (0000)                        E_IPS_IDLE                                   IPS_LINK_UP
100113                 020845 770040 (0001)                        E_IPS_LRR                                    IPS_LINK_UP
100113                 020845 763562 (61CB28)                    E_IPS_CREDIT_LOSS                    IPS_LINK_UP
Looking at the output I don't know who generates "E_LINK_LINK_RESET" , Nexus switch or server?
Thanks in advance!

Hi,
I know it is a little bit late, but hope it can still be of use...
According to the log output, The switch detects a Credit Loss condition
00113                 020845 763562 (61CB28)                    E_IPS_CREDIT_LOSS                    IPS_LINK_UP
and to recover from it, the switch resets the link by sending a LR to the server
100113              020845 763545 (61CB28)                       E_LINK_LINK_RESET             LINK_ACTIVE
the server replies with a LRR, IDLE, etc.
100113              020845 765016 (0000)                           E_LINK_LRR                           LINK_LR_TX
Kind rgds,
Felipon

Nexus 4001i and MST tons of log errors

Went looking through my Nexus 4001i logs today, and started noticing a bunch of STP role and port change messages:
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/1 instance MST0000 role changed to designated
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel2 instance MST0000 role changed to alternate
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel1 instance MST0000 role changed to root
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/14 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/14 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/13 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/13 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/12 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/12 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/11 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/11 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/10 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/10 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/9 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/9 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/8 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/8 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/7 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/7 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/6 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/6 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/5 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/5 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/4 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/4 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/3 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/3 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/2 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/2 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/1 removed as MST Boundary port
After going through a variety of configuration validations, spanning-tree root and priority validations as well as making sure the instances and revisions between the various MST speaking switches (all of the Nexus gear including Nexus 5596 which are vPC peers, 4001i's which connect via vPC's to the 5596's, and Catalyst 3110X's which also use MST, but only have one uplink at this time to the 5596's not in a vPC setup).
None of the other devices appear to be experiencing this problem.
I am quite confused as to what is going on, and cannot figure out why the 4001i is wigging out like this.
A quick output of MST::
N4k-SLOT7-SW1# show spanning-tree mst
##### MST0    vlans mapped:   801-3109,3111-4094
Bridge        address 6073.5c8d.7e82 priority      24576 (24576 sysid 0)
Root          address 0023.04ee.be03 priority      16384 (16384 sysid 0)
              port    Po1             path cost     0
Regional Root address 0023.04ee.be03 priority      16384 (16384 sysid 0)
                                      internal cost 500       rem hops 19
Operational   hello time 2 , forward delay 15, max age 20, txholdcount 6
Configured    hello time 2 , forward delay 15, max age 20, max hops    20
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Root FWD 500        32.4096 P2p
Po2              Altn BLK 1000       64.4097 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
##### MST1    vlans mapped:   2-499,600-800,3110
Bridge        address 6073.5c8d.7e82 priority      24577 (24576 sysid 1)
Root          address 0023.04ee.be03 priority      16385 (16384 sysid 1)
              port    Po1             cost          500       rem hops 19
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Root FWD 500       128.4096 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
##### MST2    vlans mapped:   1,500-599
Bridge        address 6073.5c8d.7e82 priority      24578 (24576 sysid 2)
Root          address 0023.04ee.be03 priority      16386 (16384 sysid 2)
              port    Po2             cost          1000      rem hops 19
Interface        Role Sts Cost      Prio.Nbr Type
Po2              Root FWD 1000      128.4097 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
N4k-SLOT7-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:09 ago
          from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
          from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
          from port-channel2
(topology change was due to testing rapid-PVST for this switch, and then putting it back, the previous change occured 555 hours ago).
N4k-SLOT9-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID    Priority    16384
             Address     0023.04ee.be03
             Cost        0
             Port        4096 (port-channel1)
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    24576 (priority 24576 sys-id-ext 0)
             Address     2c54.2ded.b704
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Root FWD 500       128.4096 P2p
Po2              Altn BLK 1000      128.4097 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID    Priority    16385
             Address     0023.04ee.be03
             Cost        500
             Port        4096 (port-channel1)
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    24577 (priority 24576 sys-id-ext 1)
             Address     2c54.2ded.b704
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Root FWD 500       128.4096 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
MST0002
Spanning tree enabled protocol mstp
Root ID    Priority    16386
             Address     0023.04ee.be03
             Cost        1000
             Port        4097 (port-channel2)
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    24578 (priority 24576 sys-id-ext 2)
             Address     2c54.2ded.b704
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po2              Root FWD 1000      128.4097 P2p
Eth1/1           Desg FWD 2000      128.129 Edge P2p
Eth1/2           Desg FWD 2000      128.130 Edge P2p
Eth1/3           Desg FWD 2000      128.131 Edge P2p
Eth1/4           Desg FWD 2000      128.132 Edge P2p
Eth1/5           Desg FWD 2000      128.133 Edge P2p
Eth1/6           Desg FWD 2000      128.134 Edge P2p
Eth1/7           Desg FWD 2000      128.135 Edge P2p
Eth1/8           Desg FWD 2000      128.136 Edge P2p
Eth1/9           Desg FWD 2000      128.137 Edge P2p
Eth1/10          Desg FWD 2000      128.138 Edge P2p
Eth1/11          Desg FWD 2000      128.139 Edge P2p
Eth1/12          Desg FWD 2000      128.140 Edge P2p
Eth1/13          Desg FWD 2000      128.141 Edge P2p
Eth1/14          Desg FWD 2000      128.142 Edge P2p
N4k-SLOT9-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 18758 last change occurred 4:01:03 ago
          from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 45742 last change occurred 4:01:02 ago
          from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 21007 last change occurred 599:47:47 ago
          from port-channel2
N4k-SLOT9-SW2#
N5596-DC-SW1# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID    Priority    16384
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16384 (priority 16384 sys-id-ext 0)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Desg FWD 1000      128.4096 P2p
Po2              Desg FWD 200       128.4097 (vPC) P2p
Po3              Desg FWD 200       128.4098 (vPC) P2p
Po57             Desg FWD 200       128.4152 (vPC) P2p
Po100            Desg FWD 1000      128.4195 (vPC peer-link) Network P2p
Eth1/15          Desg FWD 2000      128.143 Edge P2p
Eth1/16          Desg FWD 2000      128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID    Priority    16385
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16385 (priority 16384 sys-id-ext 1)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po2              Desg FWD 200       128.4097 (vPC) P2p
Po3              Desg FWD 200       128.4098 (vPC) P2p
Po57             Desg FWD 200       128.4152 (vPC) P2p
Po100            Desg FWD 1000      128.4195 (vPC peer-link) Network P2p
MST0002
Spanning tree enabled protocol mstp
Root ID    Priority    16386
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16386 (priority 16384 sys-id-ext 2)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Desg FWD 1000      128.4096 P2p
Eth1/15          Desg FWD 2000      128.143 Edge P2p
Eth1/16          Desg FWD 2000      128.144 Edge P2p
N5596-DC-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44578 last change occurred 4:11:57 ago
          from port-channel2
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 98707 last change occurred 4:11:55 ago
          from port-channel2
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 4 last change occurred 4:11:55 ago
          from port-channel1
N5596-DC-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID    Priority    16384
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16384 (priority 16384 sys-id-ext 0)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Desg FWD 1000      128.4096 P2p
Po2              Desg FWD 200       128.4097 (vPC) P2p
Po3              Desg FWD 200       128.4098 (vPC) P2p
Po57             Desg FWD 200       128.4152 (vPC) P2p
Po100            Root FWD 1000      128.4195 (vPC peer-link) Network P2p
Eth1/9           Desg FWD 20000     128.137 P2p
Eth1/15          Desg FWD 2000      128.143 Edge P2p
Eth1/16          Desg FWD 2000      128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID    Priority    16385
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16385 (priority 16384 sys-id-ext 1)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po2              Desg FWD 200       128.4097 (vPC) P2p
Po3              Desg FWD 200       128.4098 (vPC) P2p
Po57             Desg FWD 200       128.4152 (vPC) P2p
Po100            Root FWD 1000      128.4195 (vPC peer-link) Network P2p
Eth1/9           Desg FWD 20000     128.137 P2p
MST0002
Spanning tree enabled protocol mstp
Root ID    Priority    16386
             Address     0023.04ee.be03
             This bridge is the root
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    16386 (priority 16384 sys-id-ext 2)
             Address     0023.04ee.be03
             Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface        Role Sts Cost      Prio.Nbr Type
Po1              Desg FWD 1000      128.4096 P2p
Eth1/9           Desg FWD 20000     128.137 P2p
Eth1/15          Desg FWD 2000      128.143 Edge P2p
Eth1/16          Desg FWD 2000      128.144 Edge P2p
N5596-DC-SW2# show spanning-tree | i occur|from|exec
N5596-DC-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44234 last change occurred 4:12:45 ago
          from port-channel100
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 97804 last change occurred 4:12:43 ago
          from port-channel100
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 49801 last change occurred 599:58:06 ago
          from Ethernet1/9
Except from MST configs:
Nexus 4001i switches:
vlan 1,301-499
vlan 500
fip-snooping enable
vlan 600-800
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 24576
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
Nexus 5596 switches:
N5596-DC-SW1
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree pseudo-information
mst 0-2 root priority 16384
mst 0-2 designated priority 16384
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
N5596-DC-SW2
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree vlan 3110 priority 24576
spanning-tree pseudo-information
mst 0-1 designated priority 20480
mst 2 designated priority 16384
vlan 1-499,501,600-800 designated priority 20480
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
5596's vPC configs
N5596-DC-SW1
vpc domain 3
peer-switch
role priority 100
peer-keepalive destination 192.168.92.223 source 192.168.92.222
auto-recovery
N5596-DC-SW2
vpc domain 3
peer-switch
role priority 200
peer-keepalive destination 192.168.92.222 source 192.168.92.223
auto-recovery
Quick rundown of connections between devices:
Nexus 4001's connect to Nexus 5596's for ethernet data via twinax cables in a four port vPC between both Nexus 5596's.
Nexus 4001's connect to one Nexus 5596 a piece for FCoE two port LACP port channel. (hence the two instances, and vlan 1,500-599 in the same instance)
Catalyst 3110X connects via one Fiber-Optic connection to the N5596-DC-SW2, eventually will have two in a port-channel
Also keep in mind I corrected a priority conflict between the 3110X and Nexus 5596's earlier last month, which would explain all of the topology changes.
I can provide any other information if it is useful. I am just confused!

I identified the problem.
Refer to
http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/interfaces/configuration/guide/if_vPC.html
for more information.
The problem I encountered was self-inflicted.
Using the spanning-tree pseudo-information command creates a psuedo priority setup that if implemented after the global spanning-tree commands sits alongside the spanning-tree priority and vlan definitions. This is intended to allow for non-vPC VLANs to have their own spanning-tree definitions separate of the spanning-tree environment for the vPC vlans. I am not sure the best way to describe it, but if you are not running a hybrid vPC setup (where you have vPC member VLANs and non-vPC VLANS with a separate link between the 5596's for the non-vPC VLANs) this setup would help you ensure you have a stable spanning-tree and prevent unnecessary blocking.
When I enabled this command, I applied it to the vPC VLAN's as well, and that caused the Nexus 4001i's vPC links to constantly change port role, and update all of the edge ports subsequently. While I didn't see a performance impact to end hosts (not much traffic is on the Nexus DataCenter environment yet), I did get a torrent of logs as shown above.
Once I removed the spanning-tree pseudo-information, the switches quieted down and spanning-tree stabilized on the Nexus 4001i's.
I will revisit the configuration though for trunks not using vPC if it is needed.

What is the best way to migrate zoning from an MDS9216i to a Nexus 5596?

I am migrating from a MDS9216i to a Nexus 5596. We have dual paths, so I can migrate one leg at a time and the full function for these switches is fiber channel attached storage.
What is the best way to migrate the zoning information? I have been told I can ISL the new and old switch together and then push the zoning to the new switch. Is that better than just cutting and pasting the zoning information to the new switch?
Also, I have to move four Brocade M4424 switches to the new switches - they are currently attached via interop mode 1, but will now be attached using NPIV. Has anyone done this before, and did you have any issues?
Any help or advice would be appreciated. Thanks!

Use an ethernet cable to connect the two computers, and set up file sharing. After that copying files from one computer to the other is exactly like copying from one hard drive to another:
http://docs.info.apple.com/article.html?artnum=106658

Interoperability issues between Nexus 5k and HP storageworks (8/20q)

Hello community,
I am trying to get a VM host and a windows server to connect to their storage across a nexus and HP (Qlogic) fabric switch. This is currently having issues with the VM host unable to see the datastores, possibly due to interoperability between Cisco and HP (Qlogic)
I have configured and tested the connectivity using only the cisco nexus and this worked, I then tested it using only the HP fabric switch (HP 8/20q) and this also worked.
However, when using the HP and Cisco Nexus as shown in the attached diagram, things stop working.
The connection is using Native Fibre channel, On the Cisco side I performed the following steps
Configured the Nexus with Domain ID 10 and the HP with Domain ID 20.
Connected the 2 fabric switches on fc1/48 (Cisco) and port 0 (HP) and confirmed that the ISL came up (E_port 8G), I confirmed connectivity using fcping both ways.
I connected the SAN to the Nexus and the servers to the HP
Configured VSAN 10
Added interfaces fc1/41 to 48 in VSAN 10
Created 2 zones ( ESXI and Windows)
Added the PWWN for the ESXI server and the MSA2040 to the ESXI zone
Added the PWWN for the Windows 2k8 server and MS2040 to the Windows zones
Created zoneset (Fabric-A) and added both the above zones in it
Activated the FABRIC-A zoneset
The result is that the zones and zoneset are synchronised to the HP switch .I confirmed that I was able to see the servers and SAN WWN in the correct zones on the HP.
From the 8/20q switch I am able to fcping the SAN, Nexus and servers, however the Nexus is only able to fcping the SAN and the HP, it returns a “no response from destination” when pinging the servers.
I have added the FCID for all the units in the same zones to see if it makes any difference to no avail the result seem to be the same. I have gone through various Nexus/MDS/HP/Qlogic user guides and forums; unfortunately I have not come across any that shows this specific topology.
source for HP user guide is here: http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c02256394
I’m attaching the nexus config and partial view of the “show interface brief” showing the fibre channel port status
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/47     10     auto   on      up               swl    F       8    --
fc1/48     10     auto   on      up               swl    E       8    --
Any help and advice would be greatly appreciated. thanks in advance

Hi all, after much reading, Walter Dey provided the hint to put me on the right track.
By default the Nexus 5k is in interop mode 1. However, one of the requirement for this to be "interoperable" with other vendor the FCDomain ID in the entire fabric needs to be between 97 and 127 as stated in the Cisco website.
http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/interoperability/guide/ICG_test.html
Another issue that had me and my colleague scratching our heads, was that we were seeing high level of CRC errors on the ISL interfaces. This was caused by ARBFF settings mismatch between the Nexus and the HP. This was resolved by ensuring that the ARBFF setting on the HP was set to false and the command "switchport fill-pattern ARBFF speed 8000" is configured on the ISL interface linking the 2 switches. (note that Cisco's default setting for the ports is IDLE, until this is changed the link will not stabilise)
Thanks for all your help guys.

Cisco Nexus 5596 does not boots up after NX-OS upgrade 5.1.3.N1.1 to 6.0.2.N2.5 [CSCun66310]

Hello Friends,
Just want to save your precious time & effort, while doing Nexus 5596 upgrades so wanted to share some useful info which you can have a look prior to your upgrades of Cisco Nexus 5596 device.
I recently ran into trouble when upgarding one of datacenter switch Nexus 5596 does not boots up and after investigation from Cisco TAC it comes out to be Bug documented below.
https://tools.cisco.com/bugsearch/bug/CSCun66310/?reffering_site=dumpcr
My Upgrade path of device was : 5.1(3)N1(1)  to 6.0(2)N2(5).
Since this upgarde involves upgrade of Bios and Power sequensor, I was having some doubts to get this succesfully upgraded, But there was more twist involved in this upgrade which I came to know after contacting Cisco TAC for my died Nexus 5596 device and got info that if you have below impacted version in your Nexus 5596 device and you are planning to do Upgrade, then you migh RUN into this serious BUG aftre which device won't come up at all and only Option left is to replace with RMA device.
PID                          Impacted                   Hardware versions      Updated Versions
UCS-FI-6296UP                                            1.0                                       1.1
N5K-C5596UP                                              1.0                                        1.1
N5K-C5596T                                                 1.1                                         1.2
You can check hardware version using below command from your device.
5596# show sprom sup | inc H/W
H/W Version     : 1.1
So please be carefull when planning your Nexus 5596 upgrade and verify above things as this Bug is not present anywhere in Upgrade docuemntations unfortunately.
Hope this will help and save someone's precious Time.

Today "upgraded" our switch (N5k-C5596UP) to from 5.1(2)N1 to 7.0(5) and after reboot no life from the switch either. Even no console response. show sprom sup | inc H/W shows 1:0.
Only thing we could do is RMA the switch. So what must I do with these switches? Have still to do 3 of them.

Maximum number of interfaces in Port Channel on Nexus 5596

Let me preface this by saying I am not a network expert....
I noticed that our customer had configured a port channel on their Nexus 5596 comprised of 16 interfaces. I thought the maximum number of interfaces in a port channel was 8 interfaces? I see in the Nexus 7000 documentation that if you configure 16 interfaces, the remaining 8 will be in "hot standby." Is this the same behavior on the Nexus 5000 series?
Thank you.

Same behavior on the 5500 series and other Cisco switches like 3750, 3850 , etc..
HTH

Nexus 5596 Ethernet Port Configuration

I have a Cisco Nexus 5596 with 48 Ethernet Ports (two of which are now configured for Fibre Channel). It has a FEX attached to it as well.
I was able to configure ANY Ethernet port with the typical interface commands when in interface configuration mode. However, I can now only configure existing and new Port Channel interfaces, FEX ports and standard Ethernet ports that have never been configured before.
If I try to configure an Ethernet interface that was configured in the past, I only seem to have access to global interface commands when in interface configuration mode. I can set spanning-tree, duplex, speed or any other interface parameters. The CLI acts like I'm not in interface config mode, but the prompt shows that I am.
Anyone else seen such a thing? I am logged in as admin.

Hi Mark
I suspect the interface in question is configured to be in a channel. Once an ethernet interface is configured to be in a port-channel. most interface commands need to be configured under the port-channel interface
Thanks
-Prashanth

Question about Nexus 5596 log.

Dear Mister
When I connect toward Nexus 5596, using ipv4 telnet, send the next message:
NITE3# 2013 May 9 18:32:53 NITE3 %LOCAL7-4-SYSTEM_MSG: service telnet, IPV6_ADDRFORM - dcos-xinetd[3193]
What is the reason for this?
Could be a bug?
Best Regards

Hi,
If you want to view the changes made to any an order than open that order and click on EXTRAS--> CHANGE DOCUMENTS in the main menu.
Also if u want to see the changes made it the status u can refer the table CRM_JCDS.
Regards,
PePe

Nexus 5596 and Qlogic 8150

Similar Messages

Maybe you are looking for