LACP or not in vPC?

hi out there
I have defined a vPC between 2 sets of nexus boxes:
nx51 ----vpc11--><--------vpc21--------nx53
II II
vpc10 peerlink vpc20 peerlink
II II
nx52-----vpc11--><---------vpc21------nx54
vpc10 & vpc20 is running lacp but vpc11 & 21 are not - I just defined the portchannels - but not as active
Do I get any benefits of running LACP on these ports when I am running this on multi-chassis vpc?
Or should I run lacp - define the portchannel as "active" ?
best regards /ti

As Upinder said LACP can help out by eliminating problems with miss-wiring.  This is the #1 reason I suggest LACP.
You won't see a performance difference as far as throughput with or w/o LACP...but it does buy you some assurance that negotiation will happen before we assume these two links should be treated as 1.  In my opinion the small time it takes for LACP to go through its handshake is will worth mitigating the risks of configuring static port-channels.
Chad

Similar Messages

  • SF300 LAG port doesn't work, LACP will not enable.

    I'm trying to configure something that seems pretty trivial.
    I need 2-3 ports to participate in a LAG port.  First off, I  get the "Port X belongs to a vlan" if the participating port is  something other than access vlan 1.  This is totally useless.  I need these ports to be dot1Q tunnels.  This happens even If i set the default vlan to 300, (300 is my native or PVID).  Another piece that doesn't seem to work is that LACP will not enable, even if I throw in the towel and make my ports access vlan 1.  What gives?  I've tried this on the only firmware available which has no patches avail yet.  I've tried this on 2x 24ports, and on 2x 48 ports..  all the same issue.

    Hi I just gave it a try  you can see my screen captures below.
    If you are having trouble, have a word to the good folk at the SBSC if the switch is still under phone support coverage.
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    Maybe play it safe and delete your settings and start again... Here are some screen shots from my attempt.
    I have to admit I enabled LAG and LACP before I created vlan 100.
    you can see i have the same software as you.
    add the ports and enable LACP at the same time.
    ports 47 and 48 are still excluded from my Tagged Vlan
    Now I selected port drop down for VLAN100 and selected LAG.
    I then  received and then modified the following screen capture.
    Note I manually added LAG interface 1 as a tagged member of VLAN 100.
    Why Lag interface 1, because I created LAG 1 previously, as seen in a previous screen shot above.
    regards Dave

  • Switch profile peers not reachable

    Hello:
    I have a couple of N5k 5.2(1)N1(1). I'm trying to create a switch profile for all vPC configuration. They are connected to a OOB network through their mgmt0 interface, and ping is succesful. However, the show switch-profile status command shows they can reach eachother.
    CONFIG SWITCH 1
    feature telnet
    feature tacacs+
    cfs ipv4 distribute
    cfs eth distribute
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    feature vtp
    feature fex
    interface mgmt0
      vrf member management
      ip address 10.161.20.88/24
    switch-profile XXX
      sync-peers destination 10.161.20.87
    SWITCH 1# sh cfs status
    Distribution : Enabled
    Distribution over IP : Enabled - mode IPv4
    IPv4 multicast address : 239.255.70.83
    IPv6 multicast address : ff15::efff:4653
    Distribution over Ethernet : Enabled
    SWITCH 1# sh switch-profile status
    switch-profile  : XXX
    Profile-Revision: 1
    Session-type: Initial-Exchange
    Session-subtype: Init-Exchange-All
    Peer-triggered: No
    Profile-status: -
    Local information:
    Status: Verify Failure
    Error(s): Peer not reachable over CFS
    Peer information:
    IP-address: 10.161.20.87
    Sync-status: Not yet merged
    Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
    Status: -
    Error(s):
    CONFIG SWICTH 2
    feature telnet
    feature tacacs+
    cfs ipv4 distribute
    cfs eth distribute
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    feature vtp
    feature fex
    interface mgmt0
      vrf member management
      ip address 10.161.20.87/24
    switch-profile XXX
      sync-peers destination 10.161.20.88
    SWITCH 2# SH CFS STATUs
    Distribution : Enabled
    Distribution over IP : Enabled - mode IPv4
    IPv4 multicast address : 239.255.70.83
    IPv6 multicast address : ff15::efff:4653
    Distribution over Ethernet : Enabled
    SWITCH 2# SH SWItch-PROfile STATUs
    switch-profile  : XXX
    Start-time: 371925 usecs after Thu Jan 17 06:37:58 2013
    End-time: 107348 usecs after Thu Jan 17 06:39:58 2013
    Profile-Revision: 1
    Session-type: Initial-Exchange
    Session-subtype: Init-Exchange-All
    Peer-triggered: No
    Profile-status: -
    Local information:
    Status: Verify Failure
    Error(s): Peer not reachable over CFS
    Peer information:
    IP-address: 10.161.20.88
    Sync-status: Not yet merged
    Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
    Status: -
    Error(s):
    What can I be missing here?

    Hi Robert:
    Sadly, not even the TAC could solve this. We ended up not using vPC, which is a pity.
    Best regards, Faimy.

  • Disruptive ISSU 6.1.4a- 6.2.8 on Nexus 7010 sup1 because of LACP timers.

    Hi all.
    The problem.
    Today I updated my Nexus 7010 sup1 from 6.1.4a to 6.2.8.
    I want did it in ISSU mode, but after impact check I got this:
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1       yes  non-disruptive       rolling  
         2       yes  non-disruptive       rolling  
         3       yes  non-disruptive       rolling  
         4       yes  non-disruptive       rolling  
         5       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         6       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         7       yes  non-disruptive       rolling  
         8       yes  non-disruptive       rolling  
         9       yes  non-disruptive       rolling  
        10       yes  non-disruptive       rolling  
    Additional info for this installation:
    Service "lacp" in vdc 1: LACP: Upgrade will be disruptive as 6 switch ports and 0 fex ports are not upgrade ready!!
          Issue the "show lacp issu-impact" cli for more details.
    (modified the impact to <Hitful>  for module <6>)
    Do you want to continue with the installation (y/n)?  [n] y
    I went on with yes and update script reboot both sups after updated all modules.
    It was quite a surprise for me (yes I know I must see word "disruptive" opposite my sups 5 and 6). Because I already had done two ISSU updates on two nexuses (from 5.1.* ->5.2.7 and 5.2.7 -> 6.1.4a) and didn`t have any trouble with LACP timers. Is it a new feature of the 6.* train?
    I have another Nexus that I want to update. And it also has same problem with LACP timers.
    show install all impact give me the same disruptive result because of LACP.
    Can I somehow suppress such ISSU behavior? In case of LACP. I don`t have vPC, just ordinal PC.
    It is a way better if some LACP interfaces flap in process, than an almost 14 minutes of all 7010 chassis reboot that I had.
    Although problem with LACP timers is that they must be the same on the switch side and on the other side. And in case of switches, linux boxes or HP VCs changing LACP timers isn`t a big problem. IT is a biggg problem in case of the Windows Server.
    sh lacp interface ethernet 8/13
    Interface Ethernet8/13 is up
      Channel group is 13 port channel is Po13
    Local Port: Eth8/13   MAC Address= 40-55-39-23-1e-c1
      System Identifier=0x8000,  Port Identifier=0x8000,0x80d
      Operational key=12
      LACP_Activity=active
      LACP_Timeout=Long Timeout (30s)
    Neighbor: 0x1
      MAC Address= ac-16-2d-a4-f2-54
      System Identifier=0xffff,  Port Identifier=0xff,0x1
      Operational key=17
      LACP_Activity=active
      LACP_Timeout=short Timeout (1s)
    They must be the same and equal 30s for successful ISSU

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

  • LACP Detection issue

    Hi All,
    In this scenario, On port channel 10 we executed spanning-tree port type network but on members of same PO10. There is diff command
    spanning-tree port type normal. In our env. it's running fine. But we are running static port-channel not LACP.
    If we run lacp.. Does LACP will throw error in this scenario? Because i read LACP will always match configuration. between two members or interfaces  NOT Between Portchannel and its member. Kindly help here. Does it true?
    interface port-channel10
      description vPC peer-link
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type network
      vpc peer-link
    interface Ethernet1/31
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type normal
      channel-group 10
    interface Ethernet1/32
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type normal
      channel-group 10

    Hi,
    I think, you will see error and LACP will not work in this scenario.
    For VPC peer link, the STP type should be network for all physical links and the Portchannel.
    It is also recommended to use LACP:
    You can only configure these port channels and vPC peer links statically. All ports in the vPC on each of the vPC peer devices must be in the same VDC. You can configure the port channels and vPC peer links either using LACP or no protocol. We recommend that you use LACP with the interfaces in active mode to configure port channels in each vPC, which ensures an optimized, graceful recovery in a port-channel failover scenario and provides configuration checks against configuration mismatches among the port channels themselves.
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_cli/if_vPC.html
    HTH

  • VPC Type-2 inconsistency problem

    Hi there. 
    Now I'm facing Type-2 inconsistency problem.  I don't know what's the problem. 
    Here is the output.
    what should i do to fix this ? 
    Thank you in advance : )
    [7K_1]
    switch# show vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                     : 1   
    Peer status                       : peer adjacency formed ok      
    vPC keep-alive status             : peer is alive                 
    Configuration consistency status  : success 
    Per-vlan consistency status       : success                       
    Type-2 inconsistency reason       : Consistency Check Not Performed
    vPC role                          : secondary                     
    Number of vPCs configured         : 1   
    Peer Gateway                      : Disabled
    Dual-active excluded VLANs        : -
    Graceful Consistency Check        : Enabled
    Auto-recovery status              : Disabled
    vPC Peer-link status
    id   Port   Status Active vlans    
    1    Po1    up     1,101                                                  
    vPC status
    id   Port   Status Consistency Reason                     Active vlans
    10   Po10   up     success     success                    1               
    switch# 
    switch# show vpc consistency-parameters global 
        Legend:
            Type 1 : vPC will be suspended in case of mismatch
    Name                        Type  Local Value            Peer Value             
    STP Mode                    1     Rapid-PVST             Rapid-PVST            
    STP Disabled                1     None                   None                  
    STP MST Region Name         1     ""                     ""                    
    STP MST Region Revision     1     0                      0                     
    STP MST Region Instance to  1                                                  
     VLAN Mapping                                                                  
    STP Loopguard               1     Disabled               Disabled              
    STP Bridge Assurance        1     Enabled                Enabled               
    STP Port Type, Edge         1     Normal, Disabled,      Normal, Disabled,     
    BPDUFilter, Edge BPDUGuard        Disabled               Disabled              
    STP MST Simulate PVST       1     Enabled                Enabled               
    Allowed VLANs               -     1,101                  1,101                 
    Local suspended VLANs       -     -                      -                     
    switch# 
    switch# show port-ch sum
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      NONE      Eth3/1(P)    Eth3/2(P)    
    10    Po10(SU)    Eth      LACP      Eth3/11(P)   
    switch# 
    switch# sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Po1, Po10, Eth3/1, Eth3/2
    101  VLAN0101                         active    Po1, Eth3/1, Eth3/2
    VLAN Type  Vlan-mode
    1    enet  CE     
    101  enet  CE     
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports
    switch# 
    [7K_2]
    switch# sh vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                     : 1   
    Peer status                       : peer adjacency formed ok      
    vPC keep-alive status             : peer is alive                 
    Configuration consistency status  : success 
    Per-vlan consistency status       : success                       
    Type-2 inconsistency reason       : Consistency Check Not Performed
    vPC role                          : primary                       
    Number of vPCs configured         : 1   
    Peer Gateway                      : Disabled
    Dual-active excluded VLANs        : -
    Graceful Consistency Check        : Enabled
    Auto-recovery status              : Disabled
    vPC Peer-link status
    id   Port   Status Active vlans    
    1    Po1    up     1,101                                                  
    vPC status
    id   Port   Status Consistency Reason                     Active vlans
    10   Po10   up     success     success                    1               
    switch# show vpc consistency-parameters global 
        Legend:
            Type 1 : vPC will be suspended in case of mismatch
    Name                        Type  Local Value            Peer Value             
    STP Mode                    1     Rapid-PVST             Rapid-PVST            
    STP Disabled                1     None                   None                  
    STP MST Region Name         1     ""                     ""                    
    STP MST Region Revision     1     0                      0                     
    STP MST Region Instance to  1                                                  
     VLAN Mapping                                                                  
    STP Loopguard               1     Disabled               Disabled              
    STP Bridge Assurance        1     Enabled                Enabled               
    STP Port Type, Edge         1     Normal, Disabled,      Normal, Disabled,     
    BPDUFilter, Edge BPDUGuard        Disabled               Disabled              
    STP MST Simulate PVST       1     Enabled                Enabled               
    Allowed VLANs               -     1,101                  1,101                 
    Local suspended VLANs       -     -                      -                     
    switch#  
    switch#  sh run vpc
    !Command: show running-config vpc
    !Time: Tue Nov 25 07:48:04 2014
    version 6.1(2)
    feature vpc
    vpc domain 1
      peer-keepalive destination 1.1.1.1
    interface port-channel1
      vpc peer-link
    interface port-channel10
      vpc 10
    switch# 
    switch# show port-ch summary 
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      NONE      Eth3/1(P)    Eth3/2(P)    
    10    Po10(SU)    Eth      LACP      Eth3/11(P)   
    switch# 
    5K
    switch# sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Po1, Po10, Eth3/1, Eth3/2
    101  VLAN0101                         active    Po1, Eth3/1, Eth3/2
    VLAN Type  Vlan-mode
    1    enet  CE     
    101  enet  CE     
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports
    switch# 

    Hi, as you can see from the output of "show vpc" the Type-2 consistency check not performed. It is probably due to you have not configured any type-2 consistency check related features on your devices that would triggers the type-2 inconsistency check to perform.
    You can read more about type-2 consistency parameters here:
    www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
    Regards,
    Peter

  • Nexus 5000 vPC suspended during reload delay period

    Hi ,
    after reloading on vPC-Peer-Switch be box comes up and all vPC-Member-Ports on the box are in suspended state until the reload delay time expired.
    Unfortunately the link of the vPC-Member Ports are already up. This behaviour leads us in some problems if we connect a Cisco-UCS-FI with a LACP-Portchannel to a vPC on N5K.
    Because the link of the suspended Port is up the FI detects the port also as up and running and set it to individual state, because of missing LACP-BPDUs, So at this time the FI hast two uplinks, one Port-Channel and one individual Ports. After 30 seconds the FI starts to repinning the servers over these two uplinks. Because the individual Port is not in forwarding state an the reloaded N5K until reload delay timer expired.
    So during this period all the servers which are pinned to the individual Port are blackholed.
    Possible Workarrounds
    1. Creating a Pin-Group for the Port-Channel and pinning all Servers to this Pin-Group to avoid in case on channel-Member goes to individual state, any server is pinned to this individual Port . This could be a solution
    2.Configuring the Port-Channel on FI for "suspend individual". Unfortunately I could not find a way to achive this. This would avoid that the individual Port is considered as possible uplink-port, so no pinning to the individual Port would happen.
    3. Find a way that during the delay restore time on the suspended vPC-Member-Ports also the link is down. (In my opinion this would be the best way)
    I am not sure if configuration of "individual suspend" on the vPC on the N5K would help.
    any other ideas?
    Hubert

    What I really want is a command I can use to prevent VPC from turning off ports at all.  I'd much rather have an active-active situation than have my entire network go down just because the primary VPC peer rebooted. VPC is not designed correctly to deal with that situation.  And yes, it has happened.  Multiple times with different VPC keepalive setups.

  • Cisco WLC 5508 and LACP

    Hi Fellows,
    I wanna know if 5508 Cisco WLC support LACP or not. Actually i work in a project where i must
    connect WLC 5508 in Enterasys Switches with Link Aggregation.
    Enterasys Switches support LACP 802.3ad but when i learn Cisco Books i see that WLC 5508
    doesn't support LACP.
    Can you help please ?
    Sincerely
    Joseph

    Hi,
    Please take a look into the config guide:
    http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mint.html#wp1277652.
    You can read there:
    Once the EtherChannel is configured as on at both  ends of the link, it does not matter if the Catalyst switch is  configured for either Link Aggregation Control Protocol (LACP) or Cisco  proprietary Port Aggregation Protocol (PAgP) because no channel  negotiation is done between the controller and the switch. Additionally,  LACP and PAgP are not supported on the controller.
    HTH,
    Tiago
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • VPC Compatibility issues on N7k?

    I'm trying to get VPC working on a NX7k that's got a few of the N7K-M148GT-1 copper modules installed.
    Whenever I have these linecards installed, VPC complains that it's not available:
    vPC enable status: Incompatible hardware not enabling vPC
    disabling the copper linecards allows me to now enable VPC. When I re-enable the copper linecards, they show an "ok" status in the output of show module, but they're not available in the box to configure. The interfaces don't show up in any status outputs, I can't configure them, etc.
    I've made sure that I've got the latest EPLD installed on every device in these 7ks.
    n7000-s1-epld.4.1.4.img
    What is suspicious is that I have V1.0 linecards:
    2 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok
    2 4.1(3) 1.0
    Is anybody aware of a hardware revthat'd make this an incompatible configuration? I can't find any documentaion regarding VPC requirements anywhere.
    (I also have some N7Ks with v1.3 hardware- and that doesn't seem to have any issues with VPC. So I've got a sinking suspicion that I'm stuck.)

    Yes, as a minimum you need 1.3 h/w rev 10/100/1000 Mbps Ethernet Module (N7K-M148GT-11).
    open a TAC case, they can assist you with hardware replacements at no charge to you.

  • SG200-18 LACP issue

    I have a pfSense based router connected to a SG200-08 switch using round robin load balancing on the switch.
    From the SG200-08, if I plug in a Macbook Pro with 2 thunderbolt GigE ethernet dongles, I can successfully get transfer speeds through the router at 1300Mbps.
    If I connect an SG200-18 with two Cat6 cables to the SG200-08 and setup a dynamic LAGG on the SG200-08 with a IP/MAC based (LACP enabled) LAGG on the SG200-18 I am maxing out at 940Mbps using the Macbook Pro as a client.
    Why is it that I seem to be limited when using the SG200-18.
    FWIW, the SG200-18 has firmware version 1.3.5.58, the SG200-08 has 1.0.6.2
    Network Overview
    2xFTTH 1Gbps links --> pfSense --(load-balance RR)--->SG200-08--(dynamic LAGG)-->SG200-18---LACP LAGG--->Macbook Pro (dual ethernet dongles)

    round robin will allow you to use multiple interfaces/switch ports in the same conversation (tcp session).  because of this you can achieve higher transfer speeds.
    lacp does not allow you to use multiple interfaces/switch port for the same conversation.  because of this, you are limited to the max throughput of the interface chosen for the session.
    it is really the differences in the bonding/port-channeling methods.  i think round-robin can result in high retransmission rates.

  • Nexus 3524 support vpc feature?

    Hi, I read that the Nexus 3524 does not support VPC feature, somebody can confirm me this, 
    Thanks you in advanced.

    The Nexus 3524 does have vPC support.  You have to enable it; it is not enabled by default. 
    (config)#feature vpc

  • LACP port-channel down but Individual ports up

    I have setup an active LACP consisting of two members in each port-channel. As it is configured now the individual ports are operational but not participating as members of the LACP. Not finding any reference to exactly why this is. From what I can gather this may be related to the host configuration? 
    If anyone can enlighten me to such a situation it would be greatly appreciated. Would be even better if anyone had experience with the Oracle Database Appliance requirements for network configuration on the Cisco side.
    Group Port-       Type     Protocol  Member Ports
          Channel
    210   Po210(SD)   Eth      LACP      Eth107/1/11(I)  Eth108/1/12(I)
    211   Po211(SD)   Eth      LACP      Eth107/1/12(I)  Eth108/1/11(I)
    interface port-channel210
      description pdxodaprod-node0
      switchport access vlan 48
    interface Ethernet107/1/11
      description pdxodaprod-node0-net0
      switchport access vlan 48
      speed auto
      channel-group 210 mode active
    interface Ethernet108/1/12
      description pdxodaprod-node0-net1
      switchport access vlan 48
      speed auto
      channel-group 210 mode active
    interface port-channel211
      description pdxodaprod-node1
      switchport access vlan 48
    interface Ethernet108/1/11
      description pdxodaprod-node1-net0
      switchport access vlan 48
      speed auto
      channel-group 211 mode active
    interface Ethernet107/1/12
      description pdxodaprod-node1-net1
      switchport access vlan 48
      speed auto
      channel-group 211 mode active

    Hi,
    Putting the EtherChannel to the "on" mode will force the ports to become bundled unconditionally but the true problem, then, is truly seeing if it works. The Cisco switch will happily keep the ports bundled and will even transmit data over these ports but how do we know if Oracle is happy with that and does the same?
    Personally, I would not recommend using the "on" mode precisely because of lack of any indication that things are operating just as they should, unless it can be shown without doubts that Oracle runs without LACP and uses a static EtherChannel.
    Best regards,
    Peter

  • 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.

  • UCS C-Series VIC-1225 to Nexus 5000 setup

    Hello,
    I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
    All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
    More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
    Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

    Hello again, Im stuck
    This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
    S02# sh port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    Group Port-       Type     Protocol  Member Ports
          Channel
    4     Po4(SD)     Eth      LACP      Eth1/9(D)
    vPC info:
    S02# sh vpc 4
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    4      Po4         down*  success     success                    -
    vPC config:
    interface port-channel4
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      vpc 4
    interface Ethernet1/9
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      channel-group 4 mode active
    Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
    Any ideas on what I am missing?
    Message was edited by: HDA

  • Two switches only one manageable

    Hi,
      I have a question that I hope someone can answer.  I have a Windows 2003 Server that has 4 QLE8152 CNAs that are teamed (using the QLogic utility) with a single IP address.  There are two Nexus switches and the mgmt0 interface on both are plugged into an Extreme switch.  The 2 Nexus switches and the single Extreme switch are connected through a port-channel interface on each with 2 physical interfaces from the Nexus.  With this configuration I can only get to a single IP address from the 2003 server, every other server on the network sees the network can get to both IP addresses.  The 2003 server is plugged into the Nexus, the other systems are not.  When I ping from the 2003 I get a reply from one address and no reply from the other.  The MAC for the non-responsive mgmt0 interface address shows up on the ARP table on the server and the MAC adress for the server shows up on the non-responsive mgmt for the server.  When I do an show ip arp vrf management on the responsive mgmt0 the address for the server shows up as learned through the port-channel and on the non-responsive it shows up on an Ethernet interface.  I have split the team so that it is two teams, two interfaces per with a single address on each and I still have the same results.  Has anyone seen anything similar to this?
    Thanks,
    Thom

    Hi Vinayak,
      The server now has two NIC teams with two separate IP addresses.  LACP is not set up because of the team settings, they're set for failover.  So I have one physical interface active while the other sits in standby.  The Teams are plugged directly into the 5Ks and not into a FEX.  So I have an Extreme switch upstream and it connects to the two 5Ks through static port-channel on each.  The port-channels have two interfaces.  vPC is not set up on the switches because they didn't have enough interfaces to set it up.  So are you suggesting I set up LACP on the teams and the switches?  And as far as the edge switch setting that would be on the uplink port-channels to the Extreme switch?  Here is the settings for the interfaces on the Nexus switches:
    Switch 1
    interface Ethernet1/6
      switchport mode trunk
      switchport trunk native vlan 65
    interface Ethernet1/25
      switchport mode trunk
      switchport access vlan 65
      switchport trunk native vlan 65
    Switch 2
    interface Ethernet1/6
      switchport mode trunk
      switchport trunk native vlan 65
    interface Ethernet1/25
      switchport mode trunk
      switchport access vlan 65
      switchport trunk native vlan 65
    Thanks for the assist,
    Thom

Maybe you are looking for