Nexus 5596 Layer 2 Switching Fabric Statistics

Hi everybody
Basic question, I would like to know how much traffic the is switch forwarding in Layer 2.
In other words, a simple set of counters that in an aggregated way includes statistics from all interfaces.
Any show commands or SNMP MIBs are welcomed.
Thanks in advance

• Cisco Nexus 5548P and 5548UP: Layer 2 hardware forwarding at 960 Gbps or 714.24 mpps; Layer 3 performance of up to 160 Gbps or 240mpps
• Cisco Nexus 5596UP and 5596T: Layer 2 hardware forwarding at 1920 Gbps or 1428 mpps; Layer 3 performance of up to 160 Gbps or 240mpps

Similar Messages

  • Nexus 5596 to join Brocade fabric

    Hi all, I tried to search but didn't find a "real" answer, it is not clear if it is possible or not...
    Problem: I always worked with homogeneous Brocade fabrics. Some days ago my company asked me if it is possible to add a Nexus 5596UB to an existing (6 switches) production Brocade fabric. I underlined production as we should not interrupt SAN traffic on joining the fabric nor we should reboot and/or reconfigure existing switches.
    I found a lot of info about "interoperability mode" on MDS switches but nothing on Nexus.
    Can someone help me? Thanks.

    According to the datasheet
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-618603.html
    Native interop 1,2,3 and 4 is supported !
    Therefore you are ok, and have a TAC supported configuration.
    Fibre Channel and FCoE Features (Requires Storage Services License)
    ●  T11 standards-compliant FCoE (FC-BB-5)
    ●  T11 FCoE Initialization Protocol (FIP) (FC-BB-5)
    ●  Any 10 Gigabit Ethernet port configurable as FCoE
    ●  SAN administration separate from LAN administration
    ●  FCP
    ●  Fibre Channel forwarding (FCF)
    ●  Fibre Channel standard port types: E, F, and NP
    ●  Fibre Channel enhanced port types: VE, TE, and VF
    ●  F-port trunking
    ●  F-port channeling
    ●  Direct attachment of FCoE and Fibre Channel targets
    ●  Up to 240 buffer credits per native Fibre Channel port
    ●  Up to 32 VSANs per switch
    ●  Fibre Channel (SAN) PortChannel
    ●  Native Interop Mode 1
    ●  Native Interop Mode 2
    ●  Native Interop Mode 3
    ●  Native Interop Mode 4
    ●  VSAN trunking
    ●  Fabric Device Management Interface (FDMI)
    ●  Fibre Channel ID (FCID) persistence
    ●  Distributed device alias services
    ●  In-order delivery
    ●  Port tracking
    ●  Cisco N-Port Virtualization (NPV) technology
    ●  N-port identifier virtualization (NPIV)
    ●  Fabric services: Name server, registered state change notification (RSCN), login services, and name-server zoning
    ●  Per-VSAN fabric services
    ●  Cisco Fabric Services
    ●  Diffie-Hellman Challenge Handshake Authentication Protocol (DH-CHAP) and Fibre Channel Security Protocol (FC-SP)
    ●  Distributed device alias services
    ●  Host-to-switch and switch-to-switch FC-SP authentication
    ●  Fabric Shortest Path First (FSPF)
    ●  Fabric binding for Fibre Channel
    ●  Standard zoning
    ●  Port security
    ●  Domain and port
    ●  Enhanced zoning
    ●  SAN PortChannels
    ●  Cisco Fabric Analyzer
    ●  Fibre Channel traceroute
    ●  Fibre Channel ping
    ●  Fibre Channel debugging
    ●  Cisco Fabric Manager support
    ●  Storage Management Initiative Specification (SMI-S)
    ●  Boot from SAN over VPC/EVPC

  • Nexus 5596 switch-profile synchronization problem

    hi
    I can't synchronize switch-profile
    System version: 5.1(3)N1(1)
    Sync-status: Not yet merged
    Merge Flags: pending_merge:0 rcv_merge:1 pending_validate:1
    Status: Verify Failure
    Error(s):
    Following commands failed parsing: If the error is 'Command Parsing Failed', please check if some conditional feature(s) needs to be enabled
    switchport mode trunk (Command Parsing Failed)
    how to find the source of the problem ?

    Hello Pawel
    Can you attach following from both Nexus 5596 switches in question
    term length 0
    show version
    show run
    show tech-support port-profile

  • Connect Nexus 5548UP-L3 to Catalyst 3750G-24T-E Layer 3 Switch

    Please help!
    Could anyone out there please assist me with basic configuration between Nexus Switch and Catalyst Switch, so that devices connected on the catalyst switch can talk to devices connected on nexus switch and vice-versa? In my current setup all servers on VLAN 40 are connected on the Catalyst Switch A as shown in the diagram below, and all desktops and all other peripherals are connected on the Catalyst Switch B.  I am required to implement/add a new Nexus Switch 5548 that in the future will replace the Switch A. From now I just need to connect both switches together and start moving the server from Switch A to the Nexus Switch.
    The current network setup is shown as per diagram below:
    SWITCH A – this is a layer 3 switch. All servers are connected to this switch on the VLAN 40.
    SWITCH B – all desktops, VoIP telephones, and printers are connected on tis switch. This switch is also a layer 3 switch.
    I have connected together the Nexus 5548UP and SWITCH A (3750G) using the GLC-T= 1000BASE-T SFP transceiver module for Category 5 copper wire. The new network is shown as per diagram below:
    Below is the configuration I have created in both Switches:
    SWITCH A - 3750G
    interface Vlan40
    description ** Server VLAN **
    ip address 10.144.40.2 255.255.255.128
    ip helper-address 10.144.40.39
    ip helper-address 10.144.40.40
    interface Vlan122
    description connection to N5K-C5548UP Switch mgmt0
    ip address 172.16.0.1 255.255.255.128
    no ip redirects
    interface Port-channel1
    description UpLink to N5K-C5548UP Switch e1/1-2
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,30,40,100,101,122
    switchport mode trunk
    interface GigabitEthernet1/0/3
    description **Connected to server A**
    switchport access vlan 40
    no mdix auto
    spanning-tree portfast
    interface GigabitEthernet1/0/20
    description connection to N5K-C5548UP Switch mgmt0
    switchport access vlan 122
    switchport mode access
    spanning-tree portfast
    interface GigabitEthernet1/0/23
    description UpLink to N5K-C5548UP Switch e1/1
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,30,40,100,101,122
    switchport mode trunk
    channel-group 1 mode active
    interface GigabitEthernet1/0/24
    description UpLink to N5K-C5548UP Switch e1/2
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,30,40,100,101,122
    switchport mode trunk
    channel-group 1 mode active
    N5K-C5548UP Switch
    feature interface-vlan
    feature lacp
    feature dhcp
    feature lldp
    vrf context management
      ip route 0.0.0.0/0 172.16.0.1
    vlan 1
    vlan 100
    service dhcp
    ip dhcp relay
    interface Vlan1
      no shutdown
    interface Vlan40
      description ** Server VLAN **
      no shutdown
      ip address 10.144.40.3/25
      ip dhcp relay address 10.144.40.39
      ip dhcp relay address 10.144.40.40
    interface port-channel1
      description ** Trunk Link to Switch A g1/0/23-24 **
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,122
      speed 1000
    interface Ethernet1/1
      description ** Trunk Link to Switch A g1/0/23**
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,12
      speed 1000
      channel-group 1 mode active
    interface Ethernet1/2
      description ** Trunk Link to Switch A g1/0/24**
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,122
      speed 1000
      channel-group 1 mode active
    interface Ethernet1/3
      description **Connected to server B**
      switchport access vlan 40
      speed 1000
    interface mgmt0
      description connection to Switch A g2/0/20
      no ip redirects
      ip address 172.16.0.2/25
    I get a successful response from Server A when I ping the N5K-C5548UP Switch (VLAN 40 interface (10.144.40.3) .But if I try to ping from Server A to Server B or vice-versa the ping fails. From N5K-C5548UP I can ping successful either Server A or Server B. What am I doing wrong here? Is there any additional configuration that I need to add on the Nexus Switch? Please Help. Thank you.

    no, no secret aukhadiev
    I made a mistake without realising and the interface e1/3 was showing "Interface Ethernet1/3 is down (Inactive)". After spending sometime trying to figure out what was wrong with that interface or switch, it turned out to be that i forgot to add the vlan 40. Now the config looks like this:
    N5K-C5548UP Switch
    feature interface-vlan
    feature lacp
    feature dhcp
    feature lldp
    vrf context management
      ip route 0.0.0.0/0 172.16.0.1
    vlan 1
    vlan 40
    vlan 100
    service dhcp
    ip dhcp relay
    interface Vlan1
      no shutdown
    interface Vlan40
      description ** Server VLAN **
      no shutdown
      ip address 10.144.40.3/25
      ip dhcp relay address 10.144.40.39
      ip dhcp relay address 10.144.40.40
    interface port-channel1
      description ** Trunk Link to Switch A g1/0/23-24 **
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,122
      speed 1000
    interface Ethernet1/1
      description ** Trunk Link to Switch A g1/0/23**
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,12
      speed 1000
      channel-group 1 mode active
    interface Ethernet1/2
      description ** Trunk Link to Switch A g1/0/24**
      switchport mode trunk
      switchport trunk allowed vlan 1,30,40,100-101,122
      speed 1000
      channel-group 1 mode active
    interface Ethernet1/3
      description **Connected to server B**
      switchport access vlan 40
      speed 1000
    interface mgmt0
      description connection to Switch A g2/0/20
      no ip redirects
      ip address 172.16.0.2/25
    Thank you,
    JN

  • Nexus 7000 Switch Fabric Redundancy with Fab-2 ?

    Hi all,
    I know that N7K did not have N+1 Switch Fabric redundancy. It is required to have all five SF modules to provide full throughput. Does this change with FAB-2 modules ? I mean with new modules, does N7K have N+1 SF redundancy ?
    Thanks in advance.
    Dumlu

    The N+1 fabric redundancy will depend on the type of module.
    If you are using M132 (80G) per slot and you have 3x FAB-1 (46G each), it will provide N+1.
    The same story applies to FAB-2. If you are using the F1 series, and have 4x FAB-2, you have N+1. Of course, if you are using F2 series linecard and have all FAB-2 populated, you don't have N+1 because F2 is 480G and all 5 FAB-2 will give you 550G.
    HTH,
    jerry

  • 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

  • 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

  • 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 Licensing - filename exceeds 30 characters

    Hi,
    I'm trying to licensing two Nexus 5596 (Evaluated License), when i'm enter the "install license bootflash:LICENSE.lic" the Nexus reflect this error:
    "Installing license failed: Invalid filename size, filename exceeds 30 characters".
    After i changed the name the Nexus reflect this error:
    "Installing license failed: Invalid/Corrupt license file"
    I tried to clear the license from one switch and now i'm cannot reinstall the license.
    In the mail that cisco sent to me with the license they wrote that do not change the filename.
    Thanks in advance,
    Nadav Katz.

    Hi Eric,
    I received the Nexus switches with corrupted license.
    The license team of cisco was generate a new license and send it to me.
    Regareds,
    Nadav.

  • 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

  • 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 SFP Issue

    We have a pair of Nexus 5596 switches, that each have a 1 gigabit conection to ISP CE switches (ME3400).
    Switch 1 has a fibre connection using GLC-SX-MM with the following information...
    sh int e1/48 trans
    Ethernet1/48
        transceiver is present
        type is SFP-1000BASE-SX
        name is CISCO-AVAGO
        part number is SFBR-5766PZ-CS2
        revision is
        serial number is AGA1549L2BE
        nominal bitrate is 1300 MBit/sec
        cisco id is --
        cisco extended id number is 4
    I cannot get the port to come up on switch 2, transceiver info...
    sh int e1/48 trans
    Ethernet1/48
        transceiver is present
        type is SFP-1000BASE-SX
        name is CISCO-AVAGO
        part number is SFBR-5766PZ-CS2
        revision is
        serial number is AGA1549L2BE
        nominal bitrate is 1300 MBit/sec
        cisco id is --
        cisco extended id number is 4
    The port is up on the ISP switch, but down on the N5K...
    Ethernet1/48 is down (Link not connected)
      Hardware: 1000/10000 Ethernet, address: 547f.ee41.e337 (bia 547f.ee41.e337)
      Description: Intech WAN ME3400-1 (BT)
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
      reliability 255/255, txload 255/255, rxload 255/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 1000 Mb/s, media type is 10G
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      Last link flapped 00:31:00
      Last clearing of "show interface" counters 00:00:47
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 242.30 Gbps, 163.37 Mpps; output rate 63.30 Gbps, 231.54 Mpps
      RX
        17828772964 unicast packets  2506759 multicast packets  991 broadcast packets
        17831280714 input packets  3305852407174 bytes
        897530002 jumbo packets  0 storm suppression bytes
        20 runts  0 giants  0 CRC  0 no buffer
        20 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard Ethernet1/48 is down (Link not connected)
      Hardware: 1000/10000 Ethernet, address: 547f.ee41.e337 (bia 547f.ee41.e337)
      Description: Intech WAN ME3400-1 (BT)
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
      reliability 255/255, txload 255/255, rxload 255/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 1000 Mb/s, media type is 10G
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      Last link flapped 00:31:00
      Last clearing of "show interface" counters 00:00:47
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 242.30 Gbps, 163.37 Mpps; output rate 63.30 Gbps, 231.54 Mpps
      RX
        17828772964 unicast packets  2506759 multicast packets  991 broadcast packets
        17831280714 input packets  3305852407174 bytes
        897530002 jumbo packets  0 storm suppression bytes
        20 runts  0 giants  0 CRC  0 no buffer
        20 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
    I have tested the SFP's in use on a pair of 2960's & they work fine!
    If i replace the SFP's for copper, then they work fine also.
    Does anyone know of any incompatibility issue with this SFP?
    Thanks
    Colin

    Did you try a different port such as e1/1?  Sounds like a bug to me
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
    Table 2.
    Cisco Nexus 5500 Platform Transceiver Support Matrix

  • MAC flapping reported between 2 port channels on Nexus 5596

    Hi all, I'm seeing messages like the following reported on a Nexus 5596:
    2015 Jan  7 12:40:48.954 Switch-5596A %FWM-6-MAC_MOVE_NOTIFICATION: Host 00ab.cdef.0123 in vlan 104 is flapping between port Po5 and port Po10
    Po5 is connected to a storage cluster and is configured as an access port. It is connected to 2 Nexus 5596 switches using vpc.
    interface port-channel5
      description Storage Shelf 1
      priority-flow-control mode off
      switchport access vlan 104
      spanning-tree port type edge
      spanning-tree bpduguard enable
      speed 10000
      flowcontrol receive on
      vpc 5
    Po10 is the uplink to the core switch:
    interface port-channel10
      description uplink
      switchport mode trunk
      switchport trunk native vlan 2702
      switchport trunk allowed vlan 64,94,104,124
      spanning-tree port type network
      speed 10000
      vpc 10
    Any ideas on why we would be seeing these log messages?
    Thank you.

    You need to trace this mac address: - 00ab.cdef.0123 and check if this has dual nic card if yes then check if nic teaming is configured correctly ...then shut down one of the link and see if you are learning the same mac address on two different ports?
    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,

Maybe you are looking for