Nexus 5500, FEX 2248T, ESX

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Hi Lucien,
I have a configuration in place according to the attached file net_design_n5k.vsd. Today I tried to configure port-channel interfaces between the FEX (in this case FEX 100) and attached ESX hosts.
When defining a VPC to the port-channel interface first by using stmt “vpc 203”, I received the error-msg below when entering the command “channel-group 203 ….” to the physical interfaces.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
When defining the physical interface first with the stmt “channel-group 203 ….” I was not able to add the stmt vpc 203 to the channel interface.
The devices are running the latest NX-OS image according to the following screen-shots:
Any hints or tips are very much appreciated.
Best regards
Roman

Allright. Regarding ESX channels: Maybe a better option is to setup VST-mode and loadbalancing based on the virtual port ID on the vSwitch. Then attach the vNIC's to different port-groups (you will have one port group per VLAN). With this setup you don't need to configure a channel on the ESX but you still have a active/active design due to the fact, that the port-groups are distributed to the uplink-NIC's on your ESX host (all vNIC's in port group 1 will be pinned to uplink NIC 1, all vNIC's in port group 2 to the uplink NIC 2, vNIC's in port group 3 to uplink NIC 1 etc. In case of a uplink failure the port group to uplink mapping will recalculate and the port groups uses the remaining uplink NIC's).

Similar Messages

  • Uplink-ID 0 in Nexus 5500 with FEX 2248.

    Hi all,
    I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
    On the log of the first Nexus 5500 I see this:
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    On the log of the second nexus 5500, I see this:
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
    Thanks in advace for your assistance.

    Hi Sonu,
    I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
    sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
    Did you find the fix7workaround of this problem ?
    Regards,
    Umair

  • Cannot InterVlan on Cisco Nexus 5500

    Dear All,
    I have problem with my nexus 5500,
    Intervlan on my nexus not work,
    i dont know why..
    Before i have only this kind of license:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         No    -   Unused        -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    and feature i used is :
    - feature privilege
    - feature telnet
    - feature interface-vlan
    - feature hsrp
    - feature dhcp
    - feature lldp
    I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
    And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
    and then i read this article:
    http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
    Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
    But, the other vlan is still DOWN. and Intervlan is not work to.
    Anyone, can help me please?
    I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
    Thanks.

    Marvin,
    This is the output.
    `show module`
    Mod Ports Module-Type                       Model                  Status
    1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.2(1)N1(1b)    1.0     --
    `show interface brief`
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  trunk  up      none                        10G(D) --
    Eth1/2        1       eth  trunk  up      none                        10G(D) --
    Eth1/3        1       eth  trunk  up      none                        10G(D) --
    Eth1/4        1       eth  trunk  up      none                        10G(D) --
    Eth1/5        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/6        1       eth  trunk  up      none                        10G(D) --
    Eth1/7        1       eth  trunk  up      none                        10G(D) --
    Eth1/8        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/31       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/32       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/33       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/34       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/35       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/36       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/37       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/38       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/39       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/40       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/41       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/42       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/43       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/44       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/45       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/46       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/47       1       eth  trunk  down    SFP not inserted            10G(D) --
    Eth1/48       1       eth  trunk  down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           down   --                                      --       1500
    Interface Secondary VLAN(Type)                    Status Reason                
    Vlan1     --                                      down   Administratively down 
    Vlan199   --                                      up     --       
    Vlan999   --                                      down   Non-routable VDC mode 
    sh ip int bri
    IP Interface Status for VRF "default"(1)
    Interface            IP Address      Interface Status
    Vlan199              192.168.36.10   protocol-up/link-up/admin-up      
    Vlan999              192.168.99.1    protocol-down/link-down/admin-up  
    sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/9, Eth1/10, Eth1/11
                                                    Eth1/12, Eth1/13, Eth1/14
                                                    Eth1/15, Eth1/16, Eth1/17
                                                    Eth1/18, Eth1/19, Eth1/20
                                                    Eth1/21, Eth1/22, Eth1/23
                                                    Eth1/24, Eth1/25, Eth1/26
                                                    Eth1/27, Eth1/28, Eth1/29
                                                    Eth1/30, Eth1/31, Eth1/32
                                                    Eth1/33, Eth1/34, Eth1/35
                                                    Eth1/36, Eth1/37, Eth1/38
                                                    Eth1/39, Eth1/40, Eth1/41
                                                    Eth1/42, Eth1/43, Eth1/44
                                                    Eth1/45, Eth1/46, Eth1/47
                                                    Eth1/48
    5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    199  B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    391  C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    392  D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    393  E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    394  F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    395  G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    500  H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    526  I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    VLAN Type  Vlan-mode
    1    enet  CE    
    5    enet  CE    
    199  enet  CE    
    391  enet  CE    
    392  enet  CE    
    393  enet  CE    
    394  enet  CE    
    395  enet  CE    
    500  enet  CE    
    526  enet  CE    
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports

  • Mix of Nexus 5500 & Catalyst 6500

    Hi there,
    Does Nexus 5500 series require a Nexus 7000 parent device? or it will be supported with Catalyst 6509?
    If this is the scenario :
    CAT6509 - Core Layer 3
    CAT6509 - Distribution Layer 2/3
    NX-5548 - Access Layer 2
    And FYI, no VSS on Catalyst 6509.
    Thanks in advance,
    Gerard

    Hello Chad,
    Cool thanks ... that is perfect. We're eventually moving towards NX at the Core and Distribs really soon. Yeah, that's what I've known with the Extenders requirement with parent 5k or 7k too ... 
    Gerard

  • Nexus 5500 duplicate ICMP echo-replay

    I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
    In some cases I receive normal response when pinging from one Nexus,  but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
    5501# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms
    5502# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=0.985 ms
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=254 time=0.884 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=0.875 ms
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=254 time=3.105 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=254 time=8.378 ms
    Thanks
    Jarek

    Hi
    I found this in the configuration guide for the Nexus 7000 configuring VPCs
    "When you enable this feature (peer-gateway), Cisco NX-OS automatically disables IP redirects on all interface VLANs mapped over a vPC VLAN to avoid generation of IP redirect messages for packets switched through the peer gateway router."
    However this is not happening automatically on the 5K, so you need to manually add "no ip redirects" on each VPC vlan interface to prevent duplicate pings.

  • Connecting the nexus 5500 with multiple vsans

    Hi,
    it's my first experience in the fibre channel world and i have a few doubts about the best way to connect the nexus 5500 to a EMC storage.
    This is my scenario
    this is my configuration:
    vsan database
    vsan 2
    vsan 2 interface fc 1/1
    vsan 3
    vsan 3 interface fc 1/2
    interface fc1/1
    switchport mode f
    no shut
    interface fc1/2
    switchport mode f
    no shut
    now I don't know how can I connect the port fc1/3 to the vnx storage, I think I can't make a trunk like ethernet, can anyone help me?
    Or i only can do this with zoning
    Thanks
    Fred

    Hello Fred,
    All interfaces must be in the same vsan for them to see each other
    vsan database
    vsan 2 interface fc1/1, fc1/2, fc1/3
    exit
    Then you can zone each separately
    example:
    zone name host1 vsan 2
    member pwwn 11:11:11:11:11:11:11:11    (host1 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zone name host2 vsan 2
    member pwwn 22:22:22:22:22:22:22:22    (host2 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zoneset name Zoneset1 vsan 2
    mem host1
    mem host2
    zoneset activate name Zoneset1 vsan 2
    Thanks

  • DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

    When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
    Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

    Here is the solution:
    in the menubar on the top, in the lower one go to Admin > Server Properties
    scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false 
    restart the DCNM Servers

  • Nexus 5500 FCoE

    Hi,
    If I use a SFP-10G-SR transceiver in a Nexus 5500, can I have FCoE in this port?
    Sorry for the question but i'm begining in the FCoE world
    Thanks

    Thanks Vinayak
    I'm very excited to be working with Nexus switches. Currently we only going to use ethernet, but with the new servers will be able to use FCoE.

  • Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

    Hi,
    I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
    What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
    The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
    Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
    Thanks!

    That should not be an issue.  You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
    HTH

  • Nexus 5548 fex interface configuration in vPC scenario

    Hello Forum Team!
    I have a pair of Nexus 5548UP configured as a vPC domain active-standby couple with six Nexus 2248TP Fex's in a dual-homed scenario (each fex is connected to each 5548UP). At the same time, both 5548UP are dual-homed to a pair of VSS Catalyst 6509.
    I have a couple of questions regarding performance and configuration:
    1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour? For now I am replicating manually the configuration on both 5548UP (not confyg-sync).
    2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
    Thanks in advanced team!

    Hi,
    1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour?
    Yes, that is a normal behavior.  Since yours FEXes are connected to BOTH 5ks, you have to configure both 5Ks in order for the FEX to come up. If you connect your FEX physically to only one 5k, then you only configurethat one 5k, but in your case you need to configure both 5ks exactly the same.
    2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
    I have never tested this, but I would think since the 2k needs to to 5k for every packet including talking to another host on the same 2k, the delay would slightly be higher then when you ping directly from the 5k.
    HTH

  • VM-FEX with Nexus 5500

    While configuring vcenter to N5K connection(svs connection just like in Nexus  1000v) we need to connect only thru vpc primary switch i.e. connect  command under svs connection <name> only applied on vpc primary  switch. What happens when VPC primary switch is reloaded and secondary  becomes operational primary. I tested this but it seems that while primary  switch is going thru reboot second switch does not automatically bring  up vcenter connection. Also while primary is going thru reboot process  the whole vpc domain breaks connection to vcenter.
    pod5-n5k-1# sh vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 55
    Peer status                     : peer link is down
    vPC keep-alive status           : Suspended (Destination IP not reachable)
    Configuration consistency status: success
    Per-vlan consistency status     : success
    Type-2 consistency status       : success
    vPC role                        : secondary, operational primary
    Number of vPCs configured       : 0
    Peer Gateway                    : Disabled
    Dual-active excluded VLANs      : -
    Graceful Consistency Check      : Enabled
    vPC Peer-link status
    id   Port   Status Active vlans
    1    Po1718 down   -
    pod5-n5k-1# sh svs connectionsLocal Info:
    connection MyVC:
        ip address: 10.2.8.51
         remote port: 80
        vrf: management
        protocol: vmware-vim https
        certificate: default
        datacenter name: MyDC
        extension key: Cisco_Nexus_1000V_1813219752
        dvs name: MyVMFex
        DVS uuid: -
         config status: Disabled
        operational status: Disconnected
        sync status: -
        version: -
    Peer Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
         protocol: vmware-vim https
        extension key: Cisco_Nexus_1000V_1813219752
        certificate: default
          certificate match: TRUE
        datacenter name: MyDC
        dvs name: MyVMFex
        DVS uuid: 54 b6 2c 50 47 50 92 f9-b3 32 c1 b0 a9 28 df aa
         config status: Enabled
        operational status: ConnectedAfter primary came up with operational secondary both switches loose the svs connection to vcenter See belowpod5-n5k-1# sh svs connections
    Local Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        certificate: default
        datacenter name: MyDC
        extension key: Cisco_Nexus_1000V_1813219752
         dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
       operational status: Disconnected
        sync status: -
        version: -
    Peer Info:
    connection MyVC:
        ip address: 10.2.8.51
         remote port: 80
        vrf: management
        protocol: vmware-vim https
        extension key: Cisco_Nexus_1000V_1813219752
        certificate: default
          certificate match: TRUE
        datacenter name: MyDC
         dvs name: MyVMFex
        DVS uuid: 54 b6 2c 50 47 50 92 f9-b3 32 c1 b0 a9 28 df aa
        config status: Enabled
       operational status: Disconnectedpod5-n5k-2# sh svs connectionspod5-n5k-1# sh vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 55
    Peer status                     : peer adjacency formed ok
    vPC keep-alive status           : peer is alive
    Configuration consistency status: success
    Per-vlan consistency status     : success
    Type-2 consistency status       : success
    vPC role                        : secondary, operational primary
    Number of vPCs configured       : 0
    Peer Gateway                    : Disabled
    Dual-active excluded VLANs      : -
    Graceful Consistency Check      : Enabled
    vPC Peer-link status
    id   Port   Status Active vlans
    1    Po1718 up     1,1422
    Local Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        certificate: default
        datacenter name: MyDC
        extension key: Cisco_Nexus_1000V_1813219752
         dvs name: MyVMFex
        DVS uuid: 54 b6 2c 50 47 50 92 f9-b3 32 c1 b0 a9 28 df aa
        config status: Enabled
       operational status: Disconnected
        sync status: -
        version: -
    Peer Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        extension key: Cisco_Nexus_1000V_1813219752
        certificate: default
           certificate match: TRUE
        datacenter name: MyDC
        dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
        operational status: DisconnectedMy question is how to make sure when secondary switch becomes operational primary it initiates the vcenter connection?

    Also one more thing,
    After vpc primary switch came up and became operational secondary none of the switches cannot connect to vcenter
    pod5-n5k-2# sh vpc role
    vPC Role status
    vPC role                        : primary, operational secondary
    Dual Active Detection Status    : 0
    vPC system-mac                  : 00:23:04:ee:be:37
    vPC system-priority             : 32667
    vPC local system-mac            : 00:05:73:be:eb:bc
    vPC local role-priority         : 1
    pod5-n5k-2# config t
    Enter configuration commands, one per line.  End with CNTL/Z.
    pod5-n5k-2(config)# svs connection MyVC
    pod5-n5k-2(config-svs-conn)# no connect
    pod5-n5k-2(config-svs-conn)# connect
    pod5-n5k-2(config-svs-conn)# exit
    pod5-n5k-2(config)# sh svs connections
    Local Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        certificate: default
        datacenter name: MyDC
        extension key: Cisco_Nexus_1000V_1813219752
        dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
        operational status: Disconnected
        sync status: -
        version: -
    Peer Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        extension key: Cisco_Nexus_1000V_1813219752
        certificate: default
          certificate match: TRUE
        datacenter name: MyDC
        dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
        operational status: Disconnected
    pod5-n5k-1# sh vpc role
    vPC Role status
    vPC role                        : secondary, operational primary
    Dual Active Detection Status    : 0
    vPC system-mac                  : 00:23:04:ee:be:37
    vPC system-priority             : 32667
    vPC local system-mac            : 00:05:73:ca:f7:01
    vPC local role-priority         : 10
    pod5-n5k-1# config t
    Enter configuration commands, one per line.  End with CNTL/Z.
    pod5-n5k-1(config)# svs connection MyVC
    pod5-n5k-1(config-svs-conn)# no connect
    pod5-n5k-1(config-svs-conn)# connect
    pod5-n5k-1(config-svs-conn)# sh svs connections
    Local Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        certificate: default
        datacenter name: MyDC
        extension key: Cisco_Nexus_1000V_1813219752
        dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
        operational status: Disconnected
        sync status: -
        version: -
    Peer Info:
    connection MyVC:
        ip address: 10.2.8.51
        remote port: 80
        vrf: management
        protocol: vmware-vim https
        extension key: Cisco_Nexus_1000V_1813219752
        certificate: default
          certificate match: TRUE
        datacenter name: MyDC
        dvs name: MyVMFex
        DVS uuid: -
        config status: Disabled
        operational status: Disconnected

  • Nexus 5500 - Fabricpath Core Port - Error disabled. Reason:DCX-No ACK in 100 PDUs

    Has anyone seen Fabricpath Core Interfaces between two Nexus 5596UP switches error-disabled because of missing DCBX Acks after 50mins?
    I do not see interface errors and the peer is another 5500.
    Both switches are running 5.1(3)N2(1) with this port config:
    int e1/3
    switchport mode fabricpath
    ! Cisco 5m Twinax cables
    Log messages
    2012 May 25 17:40:59 nexus1 %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet1/3 down in fabricpath topology 0 - Interface down
    2012 May 25 17:40:59 nexus1 %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/3 is down (None)
    2012 May 25 17:40:59 nexus1 %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [3365]  P2P adj L1 nexus5 over Ethernet1/3 - DOWN (Delete All) on MT-0
    2012 May 25 17:40:59 nexus1 %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor nexus5(FOX1550GDH1) on port Ethernet1/3 has been removed
    2012 May 25 17:40:59 nexus1 %LLDP-5-SERVER_REMOVED: Server with Chassis ID 547f.ee63.fa88 Port ID Eth1/1 on local port Eth1/3 has been removed
    2012 May 25 17:40:59 nexus1 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/3 is down (Error disabled. Reason:DCX-No ACK in 100 PDUs)
    Robert

    Can you send the output of
    show lldp interface ethernet 1/3
    show lldp dcbx interface ethernet 1/3
    a workaround may be to disable lldp on both sides on these physical interfaces

  • Layer 3 config design on Nexus 5500 with Fabric Path

    I trying to Network deisgn for new data Center ,  i am new to DataCenter desgin, i attached the network diagram
    i would like to know if can configure my layer3 on 5500 and configure Fabric path to uplink switch
    please help give your suggestions on this design 

    You can configure layer-3 on the 5500 series, but you need to install a daughter cards in each 5500.
    See this link:
    Layer 3 Daughter Card and Expansion Module Options for Cisco Nexus 5548P, 5548UP, 5596UP, and 5596T Switches
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
    HTH

  • Nexus 5500 VoIP cos 3 and FCoE

    Hi
    I have a requirment to do QoS for a DC that includes some VoIP as well FCoE with CNAs in the servers. I want to use COS 3 for the VoIP signalling and drop it in the same input and output quues to the servers as FCoE.
    so we have
    class-map type qos class-fcoe
    class-map type queuing class-fcoe
      match qos-group 1
    which is the default for FCoE and I have 50% bandwidth assoicated with it.
    policy-map type queuing
         class type queuing class-fcoe
           bandwidth percent 50
         class type queing someother class etc
    The issue is the "class-fcoe" is a default class and there doesnt seem to be anywhere I can edit it to add the VOIP control traffic to the same class or can I just add it here:
    class-map type queuing match any class-fcoe
      match qos-group 1
      match cos 3
    Thanks
    Pat

    Hmm
    From the UCS 8 SRND
    For instance, voice signaling traffic with L3 DSCP  value of CS3 is mapped to L2 CoS value of 3 by Nexus 1000V. All Fibre  Channel over Ethernet (FCoE) traffic is marked with L2 CoS value of 3 by  Cisco UCS. When voice signaling and FCoE traffic enter the Cisco  UCS 6100 Fabric Interconnect Switch, both will carry a CoS value of 3.  In this situation voice signaling traffic will share queues and  scheduling with the Fibre Channel priority class and will be given  lossless behavior. (Fibre Channel priority class for CoS 3 in the  UCS 6100 Fabric Interconnect Switch does not imply that the class cannot  be shared with other types of traffic.)
    This seems ti pmply you can run Call SIgnalling COS 3 in the same queueu as FCOE COS 3. I kow its talking about a 6100 fabric switch but thats very similar to a 5500.
    Could I not do something like:
    class-map type qos match-all voice-signal-global
       match-cos 3
    policy-map type qos classify-global
       class voice-signal-global
          set qos-group 1
       class class-fcoe
          set qos-group 1
    But then I cant see how to link this where we set the queuing bandwidth percentages as this uses the "class-fcoe"
    policy-map type queuing global-fcoe-queuing-in
       class type queuing class-fcoe
          bandwidth percent 50
    Could I create a class to replace "class-fcoe" and jsut match on qos-group 1 to define whats in it ?
    Regards
    Pat

  • Nexus 2K FEX dual-homed to two Nexus 5K Configuration

    Hi.
    I am trying to look for Nexus 5K config when the nexus2K FEX is dual-homed into it.
    What will be the configuration on both 5K especiall the pinning?
    Assuming one N2K 10G port is connected to N5K-1 and another N2K 10G port connected to N5K-2?
    N5Ks are also configured as dual-sided vpc with two N7K.
    thanks

    N5k-1 ====vpc peer==== N5k-2
    \  E1/10                     E1/10  /
          \      Fex-100           /
    N5k-1 & N5k-2 config:
    ===============
    Interface po100
    switchport mode fex-fabric
    fex associat 100
    vpc 100
    int e1/10
    switchport mode fex-fabric
    channel-group 100

Maybe you are looking for

  • Drilldown bar and pie charts

    I am looking for charts with drilldown feature. I need to drilldown to another chart or a report. can you please point me to any articles doing this from scratch? I looked the sample packaged application with charts but it does not have drilldown lin

  • Cant download apps with my apple id on iphone 4

    Ok i had the iphone 4 and was working with my apple id and then i gave the phone to my uncle.  Then he took my apple id off and put his ID on the iphone4.  But it still had my apps from my ID and now ever time he said he tried to download an app it w

  • Sound don't work in KDE

    Hello, I've installed arch linux with KDE in my laptop. I've installed meta packages "kde" and "phonon-xine". The sound don't work in the desktop. Mi hardware sound is: 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Co

  • Parallel  query in Oracle 11g

    We use Oracle 11g DB on windows2008R2. We wrote very long and heavy SELECT SQL query usign several table join and sub-queries and it take very long time to get result. We did SQL statement tuning as much as we can do so far. ( I will get the Executio

  • CHANGE EVENT CREATOR IN EVENT CONTAINER

    Hello, In CRM 7.0, I need to change in the EVENT CONTAINER the element &_EVT_CREATOR&, wich passes the value to the &_Wf_Initiator&. Can you please tell me where the  EVENT COINTAINER is populated (FM, program, etc) Thanks. Best Regards, Filipe Pinhe