What is the command to check the changes in the spanning-tree topology?

What is the command to check the changes in the spanning-tree topology?

Hi,
Few commands which would help are:
1- Show spanning-tree detail
2-show spanning-tree detail | in ieee|from|occur|is exec  >> This will give from were the changes occuring- Ex:
C6K1#show spanning-tree detail | in ieee|from|occur|is exec  
 VLAN0001 is executing the rstp compatible Spanning Tree protocol
  Number of topology changes 9536 last change occurred 00:00:29 ago
          from GigabitEthernet4/6
3- show spanning-tree active  *& show spanning-tree root >> Will give you the root information.
4-  show spanning-tree inconsistentports >> If there are any port which are inconsistent state due to STP features.
STP running MST:
===============
show spanning-tree mst configuration  >> Need to check and match the same outputs with the other switches running in the same MST domain/region.
show spanning-tree mst detail
show spanning-tree mst <name of the region>
Debug on STP:
============
debug spanning-tree events/bpdu >> would be good but to be run with more cautious.
HTH
Inayath
*Plz rate if this info is usefull.

Similar Messages

  • The spanning-tree add strange value when I create new Vlans

    Hi,
    On all switchs access, the spanning-tree add strange value when I create new Vlans from Distrib Layer,
    and no association is created with any interface with spanning-tree vlan 700, see below in this exemple,
    until I reboot the switch.
    somebody already saw this values ?
    DSFDS112#sh span sum
    Switch is in rapid-pvst mode
    Root bridge for: none
    EtherChannel misconfig guard is enabled
    Extended system ID           is enabled
    Portfast Default             is disabled
    PortFast BPDU Guard Default  is disabled
    Portfast BPDU Filter Default is disabled
    Loopguard Default            is enabled
    UplinkFast                   is disabled
    Stack port is StackPort1
    BackboneFast                 is disabled
    Configured Pathcost method used is long
    Name                   Blocking Listening Learning Forwarding STP Active
    VLAN0001                     0         0        0          3          3
    VLAN0002                     0         0        0         22         22
    VLAN0006                     0         0        0          3          3
    VLAN0007                     0         0        0          8          8
    VLAN0009                     0         0        0          4          4
    VLAN0010                     0         0        0          3          3
    VLAN0011                     0         0        0          3          3
    VLAN0012                     0         0        0          3          3
    VLAN0013                     0         0        0          3          3
    VLAN0090                     0         0        0         15         15
    VLAN0109                     0         0        0          3          3
    VLAN0200                     0         0        0          4          4
    VLAN0300                     0         0        0         26         26
    VLAN0302                     0         0        0          4          4
    VLAN0700               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0702               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0704                     0         0        0          4          4
    VLAN0710               -   253  -1872756560  2087191206  -1872756549  2080375982
    VLAN0816                     0         0        0          3          3
    VLAN0820                     0         0        0          3          3
    20 vlans               -   759  -1323302384  1966606322  -1323302237  1946160764
    DSFDS112#sh span vlan 700
    VLAN0700
      Spanning tree enabled protocol rstp
      Root ID    Priority    4796
                 Address     0008.e3ff.fcbc
                 Cost        10000
                 Port        608 (Port-channel1)
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    62140  (priority 61440 sys-id-ext 700)
                 Address     885a.9213.6880
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  300 sec
    Interface           Role Sts Cost      Prio.Nbr Type
    Po1                Root FWD 10000     128.608  P2p
    DSFDS112#sh run int Gi1/0/25
    Building configuration...
    Current configuration : 194 bytes
    interface GigabitEthernet1/0/25
     description Station12
     switchport access vlan 700
     switchport mode access
    end
    DSFDS112#sh span interface Gi1/0/25
    no spanning tree info available for GigabitEthernet1/0/25
    DSFDS112#sh int status interface Gi1/0/25
    Port      Name               Status       Vlan       Duplex  Speed Type
    Gi1/0/25  Station12          connected    700          full    100 10/100/1000BaseTX
    Thanks for your help,
    Regards.

    Venki,
    The ORA-00942 is okay because there is no existing object. But what stuck me is the ORA-01921 error which may indicate that this might not be a new database.
    CREATE ROLE exp_full_database
    ERROR at line 1:
    ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name
    CREATE ROLE imp_full_database
    ERROR at line 1:
    ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name
    Are there any existing databases on this server? Have you tried to create it on other machine?I searched on Metalink too and found Doc ID: 237486.1 ORA-29807 Signalled While Creating Database using DBCA which say that eroror could be ignored. You may want to review that as well.
    Ittichai

  • Why the host ports are also seen in the spanning-tree output ?

    Why the host ports are also seen in the spanning-tree output ?
    Switch1#show spann
    VLAN0001
      Spanning tree enabled protocol ieee
      Root ID    Priority    32769
                 Address     0000.0CA2.138B
                 This bridge is the root
                 Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    32769  (priority 32768 sys-id-ext 1)
                 Address     0000.0CA2.138B
                 Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  20
    Interface        Role Sts Cost      Prio.Nbr Type
    Fa0/1            Desg FWD 19        128.1    P2p
    Fa0/2            Desg FWD 19        128.2    P2p
    Fa0/15           Desg FWD 19        128.15   P2p
    interface FastEthernet0/15
    description PC0 Interface
    switchport mode access
    spanning-tree portfast
    interface FastEthernet0/16
    I read somewhere that all the ports of a switch will participate in STP by default. Is there any way to remove the STP operation on host ports ?
    Regards,
    Chandu       

    All ports participate in Spanning Tree by default.
    Spanning tree is there to block redundant L2 paths in order to prevent loops. All ports are capable of causing a loop so you would not want to turn spanning tree off, in fact I don't think you can switch it off on a per port basis. You can switch it off on a per vlan basis.
    You are already using portfast which allows host ports to transition into a forwarding state without going through the listening and learning states of STP. If you switch off STP on a port, you risk the chance of a L2 loop.
    https://supportforums.cisco.com/docs/DOC-5180

  • Spanning Tree Topology Changes notifications

    Hello All,
    I've configured RSTP in one of our branch divisions because we decided to add a backup wireless bridge in case one of our fibers gets cut out. Everything is working great , i am getting the desired result, however, i wanted to also syslog the trap msg when a topology change occurs and send it by email. The problem is, i cannot get the root switch to log such an event. 
    The root switch is a Catalyst 6509, i have tried every level of logging possible, to no avail. I know the trap msg is a notice so i have set my logging to informational, but no change.
    I know on c3560's and 3750 i can define to log spanning-tree events, and on my lab setup i do get the trap msgs to my syslog server and email.
    What am i missing?! How can i have my Root switch send me that syslog msg?
    I do appreciate your help
    Thanks in advance!

    Hi Sarbjit-2014 
    Thank you for your response, i dont get any traps msg's at all, doing a sh log on the catalyst will not show me those events.
    Below is the output of my sh log ,for obvious reasons i have masked the logging host
    Syslog logging: enabled (0 messages dropped, 2 messages rate-limited, 0 flushes,
     0 overruns)
        Console logging: level debugging, 608 messages logged
        Monitor logging: level debugging, 23 messages logged
        Buffer logging: level debugging, 608 messages logged
        Exception Logging: size (4096 bytes)
        Count and timestamp logging messages: disabled
        Trap logging: level notifications, 649 message lines logged
            Logging to x.x.x.x, 560 message lines logged
    I also tried to enter the command spanning-tree logging, but it doesnt seem to be available
    Thanks 

  • Why does the command "spanning-tree mst simulate pvst disable" exist

    That's all really. Why would you turn it off? What is the advantage. If you're not receiving PVST BPDUs, you don't need it, but why turn it off?

    When you use the spanning-tree mst simulate pvst disable command, specified MST interfaces that receive a Rapid PVST+ (SSTP) bridge protocol data unit (BPDU) move into the STP blocking state. Those interfaces remain in the inconsistent state until the port stops receiving Rapid PVST+ BPDUs, and then the port resumes the normal STP transition process.
    OK, that's what it does, but why? the only effect it has is blocking your ports. 

  • What is the mean ??

    Hi all,
    I notice in hibernate code , have a line of code like
    what is that useful??
    private static org.apache.log4j.Logger logger = org.apache.log4j.Logger.getLogger("jsp.editbooking");
    thank you

    syjeon wrote:Hi.We test the Nexus as daisy chain.but When we attach the port to port in the same module, We got the following log :"%STP-2-DISPUTE_DETECTED"I had searched the log on CCO, but I can't find exactly what mean is.If you know the log, Please let me know as soon as possiblyThanks in advance.
    Error message -
    1. %STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars]. The spanning tree has detected a Dispute on this interface. The BPDU received from  the peer is Inferior with designated role and state as     learning and/or forwarding. Since this  condition could be caused by an     unidirectional link failure, the interface is put into blocking state  and marked as disputed in order to prevent possible loops from being created.
    Recommended Action: Issue the show spanning-tree inconsistentports command to review the list  of interfaces with Dispute. Dispute is caused if the peer in not receiving the Superior BPDUs sent  by this interface. That is why the peer continues to send its own Inferior BPDUs. Determine why  devices connected to the listed ports are not receiving BPDUs. One reason could be a failure in the  cable: if the link has a failure that makes it unidirectional (you can not transmit but you can receive)  it should be replaced with a proper cable.
    Related documents- No specific documents apply to this error message.
    Jon

  • What is the mean "%STP-2-DISPUTE_DETECTED" ?

    Hi.
    We test the Nexus as daisy chain.
    but When we attach the port to port in the same module, We got the following log :
    "%STP-2-DISPUTE_DETECTED"
    I had searched the log on CCO, but I can't find exactly what mean is.
    If you know the log, Please let me know as soon as possibly
    Thanks in advance.

    syjeon wrote:Hi.We test the Nexus as daisy chain.but When we attach the port to port in the same module, We got the following log :"%STP-2-DISPUTE_DETECTED"I had searched the log on CCO, but I can't find exactly what mean is.If you know the log, Please let me know as soon as possiblyThanks in advance.
    Error message -
    1. %STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars]. The spanning tree has detected a Dispute on this interface. The BPDU received from  the peer is Inferior with designated role and state as     learning and/or forwarding. Since this  condition could be caused by an     unidirectional link failure, the interface is put into blocking state  and marked as disputed in order to prevent possible loops from being created.
    Recommended Action: Issue the show spanning-tree inconsistentports command to review the list  of interfaces with Dispute. Dispute is caused if the peer in not receiving the Superior BPDUs sent  by this interface. That is why the peer continues to send its own Inferior BPDUs. Determine why  devices connected to the listed ports are not receiving BPDUs. One reason could be a failure in the  cable: if the link has a failure that makes it unidirectional (you can not transmit but you can receive)  it should be replaced with a proper cable.
    Related documents- No specific documents apply to this error message.
    Jon

  • View spanning tree configuraton for all the switches in ciscoworks

    Hi All,
    Is there any way I can see spanning tree configuration for all the switches we have on our networks in Ciscoworks.
    Waiting for your kind reply.
    Thanks in advance
    samir

    This can be done from within Campus Manager's Topology Services.  Open up the LAN Edge View map, and you should seesome switch clouds on the map.  If you drill into one of the clouds, you should see a Spanning Tree option in the right-hand tree.  If you expand this, you can visualize the spanning tree for MISTP or even for each VLAN.

  • "Peer-switch" command on vPC domain and spanning-tree priority interaction

    Hi guy,
    We have 2 N7K (N7KA and N7KB) which will be running vPC in hybird and pure vPC environment.
    I have a question about the Hybird and pure vPC environment. With the "peer-switch" command enable, should i tune the spanning-tree priority to be the same for all the vlan running on vPC on both N7KA and N7KB? This way, when i enter the "sh spanning-tree vlan X(vPC vlan) detail" command on N7K, it will list both N7K announc itself as "We are the root of the spanning tree".Also the switch running spanning-tree with N7K vPC vlan (Hybird), will see both N7K has the same priority (4096), and it is not desirable for a spanning-tree environment. Therefore, i used the "spanning-tree pseudo-information" on N7KB to tune the spanning-tree priority to "8192" and the switch running spanning-tree with N7K will list N7KB has a priority of 8192(perfect).
    However, I notice some strange "show" output on the switch running Port-channel with the N7KA and N7KB. The "Designated bridge" priority is flapping as show on the switch. It is constantly changing between "4096 and 8192" with the same vPC system wide mac address.
    Entering the "sh spanning-tree vlan X detail" command repeatly on switch with port-channel toward N7KA and N7KB.
    >>sh spanning-tree vlan 10 detail
    Port 65 (Port-channel1) of VLAN10 is root forwarding
    Port path cost 3, Port priority 128, Port Identifier 128.65.
    Designated root has priority 4106, address 0013.05ee.bac8
    Designated bridge has priority 4106, address 0013.05ee.bac8
    Designated port id is 144.2999, designated path cost 0
    Timers: message age 15, forward delay 0, hold 0
    Number of transitions to forwarding state: 1
    Link type is point-to-point by default
    BPDU: sent 5, received 603
    one sec later.
    >>sh spanning-tree vlan 10 detail
    Port 65 (Port-channel1) of VLAN10 is root forwarding Port path cost 3, Port priority 128, Port Identifier 128.65. Designated root has priority 4106, address 0013.05ee.bac8 Designated bridge has priority 8202, address 0013.05ee.bac8 Designated port id is 144.2999, designated path cost 0 Timers: message age 15, forward delay 0, hold 0 Number of transitions to forwarding state: 1 Link type is point-to-point by default BPDU: sent 5, received 603
    Configuration:
    N7KA
    spanning-tree vlan 1-10 priority 4096
    vpc domain 200
    peer-switch
    N7KB
    spanning-tree vlan 1-10 priority 4096spanning-tree pseudo-information vlan 1-10 designated priority 8192
    vpc domain 200
    peer-switch

    We have a issue similar to this in our environment. I am trying to upgrade the existing 3750 stack router with 2 Nexus 5596 running VPC between them. For the transition I have planned to create a channel between 3750 stack and 5596's. Once this environment is set, my plan is to migrate all the access switches to N5k.
    The issue is when I connect the 3750 port channel to both N5Ks, all the Vlans on 3750 started to flap. If I connect the port channel to only one N5K everything is normal; but when I connect the port channel to both N5K running VPC, vlans are flapping. Any idea what is going wrong here? Am I missing something?

  • Changing spanning tree modes / potential outages?

    Hi All,
    Our core / distribution / access layers are all currently configured to use Cisco's PVST+. We are now a fully populated Cisco network with no standards based STP so we can now migrate to Rapid PVST.
    By simply changing the spanning tree mode on a an access switch to Rapid PVST will the vlans with spanning tree enabled suffer an outage ? If so will this be time be based on how the rest of the network is configured ? That is, if the rest of the network is still PVST+ and I change a switch to Rapid PVST will the outage deault to around 45 seconds based on PVST+ timers ?
    Furthermore, as I understand it, even though this access switch would now be configured for Rapid PVST, the switch defaults back to PVST until the rest of the network (or VLAN) is configured for Rapid PVST.
    My second question is this :
    Assuming that all the access layer switches have been migrated to Rapid PVST, what would be the effect of then migrating the distributing and potentially core layer devices to Rapid PVST ? Will they also cause an outage on the VLAN on which STP is enabled ? Again, if so, what would the outage be ? Would this be based on PVST timers or Rapid PVST ?
    Thanks in advance.
    Chris.

    Mike
    No problem and please do come back if needed.
    One thing I should have answered from your questions but didn't directly was the question of the mac address of the root switch.
    The mac address that is important in the root switch election is the one contained in the BPDU not the source mac address of the BPDU. The source mac address is simply that of the port that transmitted the BDPU.
    If a switch flushes it's mac address table it would remove that mac address but that would make no difference as to whether the switch believed it had lost it's path to root or not.
    In terms of switch to switch communication BPDUs are sent with a multicast destination mac address so removing that mac address has no effect on BPDUs being exchanged.
    So the fact that you are seeing the switch reporting it has lost it's path to root is not a direct consequence of the mac address being flushed because it doesn't need that to send and receive BPDUs.
    However with all the flooding of end to end devices because of the flushing an indirect consequence may be that BPDUs are getting lost.
    Apologies for not making that clearer.
    Jon

  • Spanning-tree Root changes

    Hi All,
    I presently have a switched VLAN network (one 6500, several 4912G and 2948Gs) with a 2948G access-layer switch as spanning-tree root.I am planning to change the Spanning tree root to the core 6500 switch running PVST+.All switches are running trunking between them.I have read through the basic STP documents and would like to know any precautions to be aware of before doing it.Any first hand experience will be of great help.
    Thanx,
    Praful

    Praful,
    Wise decision to change your root switch, I'd just suggest doing it during your slower periods of time, just-in-case.
    It really is a quick change, just expect network connectivity to "pause" for up to 50 seconds while spanning tree stablizes.
    Provided you have a good handle on how your network is wired, and you're currently running PVST+ across your network, the actual outage should only be 2-3 seconds. I know I've had to tweak our vlans from time to time and I've never seen it take any longer than 2-3 seconds.
    HTH
    Steve

  • Why did we really need this "spanning-tree extend system-id" command?

    Folks,
    On the Spanning tree protocol I understood how does this spanning-tree extend system-id command work.
    But I have not understood why it is in place? or why do we really need it?
    Regards,
    Nikhil Kulkarni.

    Hi Nikhil,
    The STP and RSTP standard specifications mandate that each switch running STP/RSTP must have a unique Bridge ID (BID). Because Cisco runs STP or RSTP in each VLAN separately (called PVST and RPVST or PVRST), in each VLAN, the switch behaves like a standalone (albeit virtual) switch and thus, each STP/RSTP instance is required to have a unique BID to comply with the standard. Simply, having X VLANs means having X separate STP/RSTP instances and X unique BIDs.
    The question now is how to make sure the BIDs of STP/RSTP instances run on the same switch in different VLANs are truly unique. Older switches actually had a large reserve of MAC addresses. As new VLANs were created, these switches allocated a new MAC address for each new STP/RSTP instance in a new VLAN (recall that the BID originally consisted of the priority and the MAC address), making the BIDs unique.
    However, the consumption of MAC addresses this way was simply too large and ineffective. At the same time, having 65536 different values for priority in the BID was largely useless. So IEEE came with the idea of Extended System ID in which they reused a part of the priority field for a unique instance identifier. In Cisco's implementation, this field is populated with the VLAN number the STP/RSTP instance runs in. This easily and effectively makes the BID unique - even with the same priority for all VLANs on a single switch, and a single switch MAC address, multiple STP/RSTP instances running on this same switch with the same priority have different BIDs thanks to different VLAN numbers embedded into the BID.
    Some switch platforms actually allowed you to deactivate the Extended System ID and revert to the older style of assigning unique MAC addresses to individual STP/RSTP instance BIDs. That is why the command spanning-tree extend system-id exists in the first place. However, removing this command is only possible on those switching platforms which are equipped with 1024 MAC addresses for their disposal. Most new switching platforms have only 64 MAC addresses for their internal use, and while the spanning-tree extend system-id command is present in their configuration, you can not remove it. It is simply there to inform you that the Extended System ID is being used but you can not really deactivate it.
    Read more here:
    http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/spantree.html#wp1096536
    Best regards,
    Peter

  • Change of spanning-tree root

    Hi,
    Would appreciate some advise on the following:
    The network has already been configured with spanning-tree root primary as well as secondary.
    Reassigning another switch to be the spanning-tree root primary/secondary, will it cause a downtime in the network? If yes, how long?
    Thanks,
    Christina

    I'm assuming PVST (not rapid-PVST nor MST, that should behave better)
    It is very hard to give an exact estimate of a downtime. First, it's not going to be a global downtime. You can basically compare the topology with your current root bridge and the one with your new root bridge. The ports that need to block in the new topology will block quickly, in a matter of few seconds. However, the ports that were blocked in the old topology and that need to be forwarding in the new topology will take a little bit more than 30 seconds to become forwarding (15 second listening + 15 second learning phases). The topology change mechanism will age out stale CAM entries in 15 seconds. If you add a little margin for BPDU propagation, I would estimate that you are looking at a connectivity loss of about a minute, in part of your network.
    The more blocked ports need to move from the old to the new topology, the most connectivity loss you will experience. Some feature like uplinfast are able to switchover quickly between their uplinks in case of root ID changing and will reduce the downtime dramatically. It's mainly the core bridges that will take time to unblock their port.
    Note that you can expect better convergence time when a better root is introduced in the network (you are lowering the numerical value of the secondary root priority so that it takes over the primary) than when the primary root is downgraded into secondary (you increase the numerical value of the primary root so that it becomes worse than the secondary).
    Regards,
    Francois

  • What is the default key command for the COMMAND key?I seem to have changed it somehow along the way and now when I push the command key it hides all windows or shows desk top I need to correct this as soon as possible-.any ideas?

    What is the default key command for THE COMMAND (apple) key? I seem to have changed it somehow along the way and now when I push the command key (only) it hides all open windows and shows the desk top and when I push it again it shows all windows again...I need to return to default A.S.A.P. just this one key...Any ideas? Thanks in advance...

    Go to
     > System Preferences > Keyboard
    Click on the 'Keyboard' tab and hit the 'modifier keys...' button. You can see and change the defaults there.
    As I'm not sure if all the labels are the same in Lion, he's a screenshot from Snow Leopard. It should be similar enough:

  • The answer helped me.But still, what are the settings that I have to change for the behavior of the mouse pointer towards finder? Also the mouse pointer sometimes  doesn't accept my command and start clicking itself.what is the problem and how to fix it?

    The answer helped me.But still, what are the settings that I have to change for the behavior of the mouse pointer towards finder? Also the mouse pointer sometimes  doesn't accept my command and start clicking itself.what is the problem and how to fix it?

    If the mouse clicks something on its own then it looks like you have a hardware problem with the trackpad or possibly the battery that is right underneath the trackpad.
    I have read that the battery can swell and that would put pressure on the trackpad.

Maybe you are looking for