MSTP vs RPVST

Hi,
I have a network as shown below. Where, Sw1 is running R-PVST and other switches Sw2,Sw3&Sw4 are aunning MSTP. Sw2 is the IST and CIST root.
The issue is, whenever I try to ping from Sw1 to the switches running MSTP, I can't ping without allowing VLAN 1 on Sw1's trunk port. Am I missing something here? Or, i'm lacking concept behind compatibility of RSTP & MSTP?
Additional info: NATIVE VLAN IS 1
MANAGEMENT VLAN IS 300
Here, Management VLAN is allowed on the trunks but not VLAN 1.
Sw1----Sw2-----Sw3
Sw4
Thanks!

With MST communicates with other regions(other than its own locally configured region), PVST+ regionns, or RSTP region, on VLAN1 using Native VLAN1 (Common Spanning Tree). This is because on the BPDU sent from MST, it includes a hash of the vlan-to-instance mapping table for each instance configured, whihc is included in its own M-record on this BPDU using VLAN 1.
I'm not sure about a Root Inconsistent mode though.
Now, Cisco will send out "two" BPDUs on native VLAN1. One on(0180.c200.0000 IEEE Standard BPDU), and one on (0100.0ccc.cccd Cisco Proprietary PVST+ BPD). But this only happens on trunk ports (802.1q). If this is an access port it will always use IEEE standard BPDU (0180.c200.0000).
So if you have multiple vlans, for instance, vlan 10, vlan 20, the MST switch will not undestand these BPDUs, since by Cisco switches ALWAYS send out BPDUs for all vlans other than vlan1 (as 0100.0ccc.cccd Cisco PVST+ BPDU).
Now, there is backward compatibility between these two.
I know that if a MST switch is connected to PVST+, the MST port that is connected to the PVST+ switch will detect this, and after a few seconds around 4 I think ( could be wrong ) If it detects a PVST+ BPDU it will turn the port from MST to PVST+ mode.

Similar Messages

RPVST vs MSTP

Hello all,
I am planning on implementing rapid-PVST in a data center switch fabric, as recommended by Cisco. However, I am very curious about MSTP.
What exactly are the advantages/disadvantages of running MSTP over PVST?
Would MSTP be an acceptable solution in a high availability environment such as a data center?

I thought the link covered that, sorry.
Here's a link to some good references for data center design.
http://www.cisco.com/en/US/netsol/ns340/ns394/ns431/ns432/networking_solutions_design_guidances_list.html
I run RPVST because it fis better. I only have a couple hundred vlans/networks so scalability isn't that big of a deal for me. I would *think* that VLANs in MST should be close in topology or troubleshooting could be a nightmare. I've never run MST, so take my comments with a grain of salt.

Attaching MST domain to a RPVST domain

Hi all,
I'm in a situation that i must stretch l2 between datacenters for server migration purposes.
Current:
Location1 - stretch network - LocationNEW
The first location is running RPVST+. The migration network (Cisco4900M switches) we also configured for RPVST till the boundary at the new network. We have 2 uplinks from location1 to the stretch network (The switches in location 1 are the spt root for all the vlans on the stretch) and with normal spanning-tree root bridge selection we load balance the vlans between the 2 uplinks fron the stretched network towards Location1 .
Desired situation :
Attach Location2 with 2 uplinks to the stretch to start also the server migration from Location2 to the LocationNEW.
Location1 - stretch network - LocationNEW
Location2 - stretch network - LocationNEW
The Location2 network is running MSTP. Ive read a lot of documentation on the network and it seems to interoperate without problems between the 2 protocols (MST & RPVST+). Ive NO VLAN OVERLAP between the networks. Lets say i want to stretch vlan 100-110 from this Location2 network to the LocationNEW. I make sure that de IST (Instance0) bridge-id is the lowest in the MST network AND stretch network. Ive read that at the boundary on the MST region only the IST BPDU's are replication on all vlans allowed on the trunks. (In my example vlan 100-110). Then from the stretched network (RPVST+) one port will be blocking and one port will be forwarding towards the MST region (Because the CST BPDU's are the lowest=best). (From the RPVST+ perspective the whole MST region is 1 virtual-bridge). On the uplinks from the stretched network towards location2 i can enter spanning-tree per vlan port cost to archive load-balancing. (For example vlan 100-105 takes the first uplink and vlan 106-110 takes the second uplink).
I got 2 questions:
-Am i right?
-Currently on the stretched network (I'm just starting here at the new client and i dont know the reason for this yet) they entered the command "no spanning-tree vlan 1". Vlan 1 is the native vlan on all trunks.... Is this causing for any problems in my setup? The documentation is very confusing on this part.....
I hope you can help me :-)
Kind regards,
Stefan

So you got MST region with, for example, vlans 1,200-210, instance0; and pvst-domain with vlans 100-110. And you want to extend vlans 100-110 over switches running MST. And keep pvst vlans running on mst-switches using mst. Am I right?
Native vlan and no spanning-tree vlan 1 on pvst border switch entered to let mst border switch detect loop on uplinks and block one of it for instance0.

Upgrade ONS15454 MSTP from 7.0 to 9.8

Hi all
I would like to some help that customer need to upgrade ONS15454 MSTP from version 7.0 to 9.8. So, I may need some help
1. how to upgrade it ?a
2. Is it possible to direct upgrade to 9.8?
3. I saw many file information in cisco web site, and which one i must to download it ? ( ONS 15454 R9.8.0 System Software for MultiService Transport Platform, ONS 15454 R9.8.0 System Software for Multiservice Transport Platform - Lite Version for TCC2P/TCC3 -WSON) I do not know which one is to using
4. what should i know that my card support version 9.8? In my idea, i think it should be support but i may need confirm or information from this before. (my card have OSC-CSM, OPT-PRE, AD-2C, MXP-10DME and TCCP2)
5. Have any interrupt between upgrade ? and Is it upgrade in each TCCP2? because that may help when card reset or reboot. And the traffic still flow to another TCC2P.
Thanks
V

1. I try to using your upgrade tool, my ONS15454 is SDH version 7.0 so, I can choose only 9.3 for destination version. It means that i must to upgrade to 9.3 first and then go to 9.6 and 9.8, Correct?
yes it is true you go directly to 9.3.0, it is not a multi-shelf node.
please be sure that your software version is 7.0.0.
So upgrade path is 7.0.0 to 9.3.0
2. Is it possible to upgrade without downtime ? as my understand that ONS15454 have 2 site (east and west), Can i do upgrade east site before west site? and when finish upgrade east site and go to upgrade west site after that, can i ?
becase as i understand when finish upgrade per site all card in that site will reboot, so, i think that another site will take the traffic without downtime. I don't sure that i am correct or not if you have any mention please let's me know
no not possible without downtime,
there will be a traffic hit or 10seconds or less than that, it you are using MXP_MR_2.5G cards without Y-cable protection. same for GE_XP cards there will be a traffic loss for few seconds.
yes you can upgrade east node and after that upgrdae west node, but not like doing upgrade to 9.8 for one node and another still on 7.0
3. I don't have multishelf, i just have one shelf per site
4. I have plan to upgrade to customer soon, but i may need to give a plan for them. But right now, i may confuse about the way and solution to upgrade that include how and impact to upgrade.
1. There will be a traffic impact on MXP and GE_XP card for less than 10 seconds.
2. If MXP client ports are y-cable provisioned, than upgrade will be error less, in case of Y-cable protection just lock protection before proceeding to upgrade.
3. traffic will impact as MXP cards have to do FPGA upgrade also and for this they will take a reboot, but in case of y-cable other card is taking over.
4. As you have TCC2P card, so always select lite versions, if its SDH than SDH-DWDM.
5. also if possible, arrange spare TCC2P card, atleast one at each site, just to be on safe side.
6. here is the path which you have to follow:
7.0.0 to 9.3.0
9.3.0 to 9.6.0
9.6.0 to 9.8.0
also please feel free to reach for any queries.

MSTP Topology Change not in Logging

Hello,
we are trying to get rid ofsome MSTP problems at our campus, for any reason we get 10-15 topology changes per day.
With spanning-tree portfast enabled on all ports, we are still getting 5-10 changes per day.
Now i am trying to get a trap whenever a topology change appears to our cpi, but this event didn't even appears in the logging of the switch.
Configured Trap:
snmp-server enable traps bridge newroot topologychange
Any suggestions?
Greetings

We found it:
Trap ist called "The value of vlanTrunkPortDynamicStatus"

In ASR901 can you tag MSTP BPDU's

I have an ASR901 ring, dual homed to 2 ME3800's with a management VPLS connection between the 3800's. Running MPLS on all interfaces of the ring. Would like to use a VRF for in-band management of the 901's. These devices will be located at customer premises. I am using SVI's for MPLS interfaces and SVI's for in-band Management interfaces on the ring. Untagged encaps for MPLS and Tagged (vlan 2) for Management. In the 3800's, I have a VPLS to bring the traffic back to the Management router. So basically, in-band management uses a Layer 2 vlan switching on the ring, with vlan interfaces attached to a VRF. Customer traffic uses MPLS cross-connects.
Problem is the need for MSTP so management can be dual homed to both 3800's and Layer 2 Protocol forwarding over the VPLS in order for STP to work properly.
This doesn't work because the management traffic is tagged VLAN 2 and the BPDU's are untagged, therefore they are getting dropped at the service instance ingress to the 3800's (encap dot1q 2). Is there a way to tag MTSP BPDU's to make this work? MSTP is the only STP option on the ASR901.
Or is there a way to add a management interface to an EFP cross-connect? Or some other way to dual home the in-band management while using a VRF for management? Note ASR901 doesn't support VPLS.

Thanks for the link but unfortunately it didn't help. Although I did follow the instructions on the link but without success, I noticed that the link spoke of the iPod nano (5th generation). I'm wondering if the tagging feature isn't available for the iphone 4s. I bet it is but something just isnt right.

Simple MSTP Query

Hi all,
We have a site that is running MSTP that we need to add a new Vlan to that will be contained on the core switch. The Vlan in question is currently mapped to the default 0 instance but is not configured yet i.e. (config)#vlan 600
My question is what is the consequence on the MSTP region if I only add this Vlan to the core switch but don't map it to any of the currently configured instances (1 &2). I've read that it should not impact the region as I'm not adjusting the MSTP configuration, but wondered if this was correct based on people's experiences with the protocol. My experience with it is very limited.
Thanks,
Darren

Hi
I used same UNION SQL using OR it runs fine but the count do not match with the UNION query. Please let me know what I''m doing wrong and correct version.
UNION
select count(*)
from
select distinct listing_id, version_id from pubs.individual_listing_version a where a.version_type=2 and (inactive_reason_code is null or a.INACTIVE_REASON_CODE NOT IN (1,11,12,7,6,5 )) and (position_code is null or a.POSITION_CODE <> 5)
and has_listing_restriction_flag = 'Y' and exists(select 'x' from rating.nes_listing_restriction where listing_id = a.listing_id and version_id = a.version_id)
union
select distinct listing_id, version_id from pubs.individual_listing_version a where a.version_type=2 and (inactive_reason_code is null or a.INACTIVE_REASON_CODE NOT IN (1,11,12,7,6,5 )) and (position_code is null or a.POSITION_CODE <> 5)
and has_listing_restriction_flag = 'N'
dual
With OR operator (NOt working as the first query)
SELECT COUNT(9)
FROM
((select * from pubs.individual_listing_version a where version_type=2
and (inactive_reason_code is null or inactive_reason_code not in (1,11,12,7,6,5))
and (position_code is null or position_code <> 5)
and (has_listing_restriction_flag = 'N') OR has_listing_restriction_flag = 'Y' AND exists(select 'x' from rating.nes_rating_restriction where listing_id = a.listing_id and version_id = a.version_id)))
DUAL
Thanks in advance
Murthy

RPVST+ at Distribution and PVST at Access Switch

Hi. I have two Cat6506 (redundant collapsed-core config) configured w/ RPVST+ and connected to this are a series of Cat2950s configured with PVST. My question is, is this a good practice configuration of STP? (running both RPVST+ and PVST on the same topology) Will there be any problems with convergence? We recently are adding some vlans on the network and we experienced an outage for most of the vlans. The Cat6500s registered duplicate HSRP addresses. Any recommendation to fine-tune this network (considering that the Cat2950 does not support RPVST+) would be helpful. thanks.

you can run rpvst+ and pvst+ simultaneously.
rpvst+ has been built to interoperate with pvst+.
an rpvst+ configured switch will revert to pvst+ in a pvst+ rootBridge scenario.
cisco recommends a slightly different configuration in this case:
1) run two STP instances, one for rpvst+ and one for pvst+.
2) the rpvst+ instance must have an rpvst+ switch as the rootBridge; the pvst+ instances must have an pvst+ switch as the rootBridge.
3) keep the pvst+ switches at the edge of the network; likewise, keep the rpvst+ switches at the core of the network.
please see this link for more info on STP modes:
http://www.cisco.com/en/US/products/hw/switches/ps5213/products_configuration_guide_chapter09186a0080216672.html#wp1150156
please see the following link for much more STP info:
http://www.cisco.com/en/US/tech/tk389/tk621/tsd_technology_support_protocol_home.html

MSTP configuration imbalance

I am configuring MSTP for the first time on three switches in my network (lab environment) my running config for the three switches is :
spanning-tree mode mst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 1 priority 24576
spanning-tree vlan 1 forward-time 12
spanning-tree vlan 1 max-age 16
spanning-tree mst configuration
name Greg_MSTP_Lab_Config
revision 1
instance 1 vlan 1
spanning-tree mst 1 priority 24576
==========================================LabSwitch1
spanning-tree mode rapid-pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
----------------------------------------Server Room Sw
spanning-tree mode mst
spanning-tree portfast bpduguard default
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
no spanning-tree vlan 1
spanning-tree vlan 1 priority 61440
=====================================LabSwitch2
My Problem: 1) I cannot ping the default gateway with LabSwitch 2
2) I cannot telnet from LSW2 to any other devices
I know I have a problem with my MST config, and I think the biggest one is the "no spanning-tree vlan 1" statement in LSW2. I have tried to reconfigure several times with no success. I am trying to put all three switches in the same region, enable them and pass traffic.
Thank you for any help you can provide.

How are these switches physically connected together?
If you are planning to make labswitch1 the root, than your config seems to be correct on that switch.
You also need to configure Server Room Sw and LabSwitch2 with the same mst config as
LabSwitch1 but no need for "spanning-tree mst 1 priority 24576"
This way, both Room Sw and LabSwitch2 will have the default stp config of 32768 and should point to labswitch1 as the root.
HTH

SG302-08P & MSTP problem

We've just added some of the SG302 switches to an existing network of (mostly) 2950 switches - to provide some PoE ports for wireless APs.
After configuring MSTP identically to that on the existing network, it looks like the SG302 switches can't handle the pre-standard MSTP from the older switches and are forming their own tree/domain. Or it could be that I just don't understand what I'm seeing ! I'd appreciate some help.
On one of the 2950 :
MST01
Spanning tree enabled protocol mstp
Root ID Priority 24577
Address 000c.ceac.a700
Cost 40000
Port 25 (GigabitEthernet0/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 000c.852d.8540
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 0
Interface Port ID Designated Port ID
Name Prio.Nbr Cost Sts Cost Bridge ID Prio.Nbr
Gi0/1 128.25 20000 FWD 20000 32769 000c.852d.6bc0 128.25
Gi0/2 128.26 20000 FWD 40000 32769 000c.852d.8540 128.26
That looks fine, it's correctly identified the root bridge (a 3550) and route to it.
On an SF302 attached to it, I get this :
###### MST 1 Vlans Mapped: 1
Root ID Priority 32768
Address 00:e1:6d:8f:d1:b1
This switch is the regional Root
Interfaces
Name State Prio.Nbr Cost Sts Role PortFast Type
gi1 enabled 128.49 20000 Frw Mstr No P2P Bound (RSTP)
This looks to me like it's oblivious to the real tree root and has elected itself.
But for instance 0, it does seem to recognise the master :
###### MST 0 Vlans Mapped: 99
CST Root ID Priority 24576
Address 00:0c:ce:ac:a7:00
Path Cost 20000
Root Port gi1
This switch is the IST master
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768
Address 00:e1:6d:8f:d1:b1
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Max hops 20
Name State Prio.Nbr Cost Sts Role PortFast Type
gi1 enabled 128.49 20000 Frw Root No P2P Bound (RSTP)
Configs :
2950 :
sho spanning-tree mst configuration
Name      [main]
Revision  1
Instance  Vlans mapped
0         2-99,300-4094
1         1
2         100-299
And on the 302 :
sho spanning-tree mst-configuration
Gathering information ..........
Current MST configuration
Name: main
Revision: 1
Instance  Vlans Mapped                                       State
0         99                                                 enabled
1         1                                                  enabled
2         100-299                                            enabled
At the moment I've left ports administratively shutdown to avoid any potential loops, but I was hoping as part of the extra work we've done to add some redundancy. Am I missing something ?
Simon

We've just added some of the SG302 switches to an existing network of (mostly) 2950 switches - to provide some PoE ports for wireless APs.
After configuring MSTP identically to that on the existing network, it looks like the SG302 switches can't handle the pre-standard MSTP from the older switches and are forming their own tree/domain. Or it could be that I just don't understand what I'm seeing ! I'd appreciate some help.
On one of the 2950 :
MST01
Spanning tree enabled protocol mstp
Root ID Priority 24577
Address 000c.ceac.a700
Cost 40000
Port 25 (GigabitEthernet0/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 000c.852d.8540
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 0
Interface Port ID Designated Port ID
Name Prio.Nbr Cost Sts Cost Bridge ID Prio.Nbr
Gi0/1 128.25 20000 FWD 20000 32769 000c.852d.6bc0 128.25
Gi0/2 128.26 20000 FWD 40000 32769 000c.852d.8540 128.26
That looks fine, it's correctly identified the root bridge (a 3550) and route to it.
On an SF302 attached to it, I get this :
###### MST 1 Vlans Mapped: 1
Root ID Priority 32768
Address 00:e1:6d:8f:d1:b1
This switch is the regional Root
Interfaces
Name State Prio.Nbr Cost Sts Role PortFast Type
gi1 enabled 128.49 20000 Frw Mstr No P2P Bound (RSTP)
This looks to me like it's oblivious to the real tree root and has elected itself.
But for instance 0, it does seem to recognise the master :
###### MST 0 Vlans Mapped: 99
CST Root ID Priority 24576
Address 00:0c:ce:ac:a7:00
Path Cost 20000
Root Port gi1
This switch is the IST master
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768
Address 00:e1:6d:8f:d1:b1
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Max hops 20
Name State Prio.Nbr Cost Sts Role PortFast Type
gi1 enabled 128.49 20000 Frw Root No P2P Bound (RSTP)
Configs :
2950 :
sho spanning-tree mst configuration
Name      [main]
Revision  1
Instance  Vlans mapped
0         2-99,300-4094
1         1
2         100-299
And on the 302 :
sho spanning-tree mst-configuration
Gathering information ..........
Current MST configuration
Name: main
Revision: 1
Instance  Vlans Mapped                                       State
0         99                                                 enabled
1         1                                                  enabled
2         100-299                                            enabled
At the moment I've left ports administratively shutdown to avoid any potential loops, but I was hoping as part of the extra work we've done to add some redundancy. Am I missing something ?
Simon

MSTP issue

We have ring created of 3750s and 2950 are connected to 3750 in spur. MSTP is running and multiple vlans are running across the ring. When one of 3750 is restarted 2950 connected to another 3750 is affected when 3750 goes down and comes up. Evenif STP path of 2950 and it's connected 3750 is not changing.

The MST Instances are all dependent on instance 0, the CIST. If there is a reconvergence in the CIST (in particular if the root port is changing for instance 0, which is very likely in the case of a link failure in a ring topology), there might be some "sync" events that affect all the instances, and as a result all the vlans.
Regards,
Francois

Frequent MSTP topology changes on SF-300-08 and SG-300-10

Hi,
I am trying to configure MSTP on Layer-2 network at work. We have multiple switches connected on Wireless point-to-point links with redundent links.
MSTP is configured with multiple regions. All the servers are located in RegionA and other regions are connected to RegionA via multiple links.
There are 3 SG-300-10 switches in RegionA --- SwitchA_1, SwitchA_2 and SwitchA_3.
One of the simple regions (RegionB) has a single SF-300-08 switch (SwitchB) connected to SwitchA_2 via port e7 and SwitchA_3 via port e8. Hello Time, Forward Delay and Max Age are at their default values of 2, 15 and 20 respectively. The link between SwitchB (port e7) ---- SwitchA_2 is the primary link with cost 200,000 and the link between SwitchB (port e8) ---- SwitchA_3 is the backup link with cost 500,000.
The log on SwitchB is shows in the table below. As it is seen from the table there are frequent topology changes for very short duration (1-4 seconds) before the topology settles back to the configured one. (Primary link forwarding and secondary link blocking). During this time there have been no link failures reported.
Same thing is also observed within RegionA (SwitchA_1, SwitchA_2 and SwitchA_3 are connected to each other).
How to stop these frequent topology changes? The topology changes within RegionA causes a lot of PPPoE sessions to reset and re-establish.
Is there any way to find out what triggers these topology changes? Has anyone experienced similar behaviour?
2147464623
2011-May-24 13:54:15
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464624
2011-May-24 13:54:15
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464625
2011-May-24 13:54:15
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464626
2011-May-24 13:54:15
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464627
2011-May-24 13:54:13
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464628
2011-May-24 13:54:13
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464629
2011-May-24 13:54:13
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464630
2011-May-24 13:54:13
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464631
2011-May-24 12:53:22
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464632
2011-May-24 12:53:22
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464633
2011-May-24 12:53:22
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464634
2011-May-24 12:53:22
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464635
2011-May-24 12:53:19
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464636
2011-May-24 12:53:19
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464637
2011-May-24 12:53:19
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464638
2011-May-24 12:53:19
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464639
2011-May-24 10:56:48
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464640
2011-May-24 10:56:48
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464641
2011-May-24 10:56:48
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464642
2011-May-24 10:56:48
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464643
2011-May-24 10:56:46
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464644
2011-May-24 10:56:46
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464645
2011-May-24 10:56:46
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464646
2011-May-24 10:56:46
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464647
2011-May-24 10:35:46
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464648
2011-May-24 10:35:46
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464649
2011-May-24 10:35:46
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464650
2011-May-24 10:35:46
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464651
2011-May-24 10:35:45
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464652
2011-May-24 10:35:45
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464653
2011-May-24 10:35:45
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464654
2011-May-24 10:35:45
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464655
2011-May-24 08:52:41
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464656
2011-May-24 08:52:41
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464657
2011-May-24 08:52:41
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464658
2011-May-24 08:52:41
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464659
2011-May-24 08:52:40
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464660
2011-May-24 08:52:40
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464661
2011-May-24 08:52:40
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464662
2011-May-24 08:52:40
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464663
2011-May-24 08:04:28
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464664
2011-May-24 08:04:28
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464665
2011-May-24 08:04:28
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464666
2011-May-24 08:04:28
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464667
2011-May-24 08:04:27
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464668
2011-May-24 08:04:27
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464669
2011-May-24 08:04:27
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464670
2011-May-24 08:04:27
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464671
2011-May-24 07:38:19
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464672
2011-May-24 07:38:19
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464673
2011-May-24 07:38:19
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464674
2011-May-24 07:38:19
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464675
2011-May-24 07:38:18
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464676
2011-May-24 07:38:18
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464677
2011-May-24 07:38:18
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464678
2011-May-24 07:38:18
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464679
2011-May-24 06:50:12
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464680
2011-May-24 06:50:12
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464681
2011-May-24 06:50:12
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464682
2011-May-24 06:50:12
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464683
2011-May-24 06:50:10
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464684
2011-May-24 06:50:10
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464685
2011-May-24 06:50:10
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464686
2011-May-24 06:50:10
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464687
2011-May-24 06:14:42
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464688
2011-May-24 06:14:42
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464689
2011-May-24 06:14:42
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464690
2011-May-24 06:14:42
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464691
2011-May-24 06:14:41
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464692
2011-May-24 06:14:41
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464693
2011-May-24 06:14:41
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464694
2011-May-24 06:14:41
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464695
2011-May-24 06:00:52
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464696
2011-May-24 06:00:52
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464697
2011-May-24 06:00:52
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464698
2011-May-24 06:00:52
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464699
2011-May-24 06:00:51
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464700
2011-May-24 06:00:51
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464701
2011-May-24 06:00:51
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464702
2011-May-24 06:00:51
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464703
2011-May-24 05:48:34
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464704
2011-May-24 05:48:34
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464705
2011-May-24 05:48:34
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464706
2011-May-24 05:48:34
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464707
2011-May-24 05:48:33
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464708
2011-May-24 05:48:33
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464709
2011-May-24 05:48:33
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464710
2011-May-24 05:48:33
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464711
2011-May-24 05:47:53
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464712
2011-May-24 05:47:53
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464713
2011-May-24 05:47:53
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464714
2011-May-24 05:47:53
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464715
2011-May-24 05:47:52
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464716
2011-May-24 05:47:52
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464717
2011-May-24 05:47:52
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464718
2011-May-24 05:47:52
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464719
2011-May-24 04:31:27
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464720
2011-May-24 04:31:27
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464721
2011-May-24 04:31:27
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464722
2011-May-24 04:31:27
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464723
2011-May-24 04:31:25
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464724
2011-May-24 04:31:25
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464725
2011-May-24 04:31:25
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464726
2011-May-24 04:31:25
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464727
2011-May-24 03:24:27
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464728
2011-May-24 03:24:27
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464729
2011-May-24 03:24:27
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464730
2011-May-24 03:24:27
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464731
2011-May-24 03:24:26
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464732
2011-May-24 03:24:26
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464733
2011-May-24 03:24:26
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464734
2011-May-24 03:24:26
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464735
2011-May-24 03:16:19
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464736
2011-May-24 03:16:19
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464737
2011-May-24 03:16:19
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464738
2011-May-24 03:16:19
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464739
2011-May-24 03:16:18
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464740
2011-May-24 03:16:18
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464741
2011-May-24 03:16:18
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464742
2011-May-24 03:16:18
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464743
2011-May-24 03:11:57
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464744
2011-May-24 03:11:57
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464745
2011-May-24 03:11:57
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464746
2011-May-24 03:11:57
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464747
2011-May-24 03:11:55
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464748
2011-May-24 03:11:55
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464749
2011-May-24 03:11:55
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464750
2011-May-24 03:11:55
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464751
2011-May-24 02:52:39
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464752
2011-May-24 02:52:39
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464753
2011-May-24 02:52:39
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464754
2011-May-24 02:52:39
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464755
2011-May-24 02:52:38
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464756
2011-May-24 02:52:38
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464757
2011-May-24 02:52:38
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464758
2011-May-24 02:52:38
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464759
2011-May-24 01:29:23
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464760
2011-May-24 01:29:22
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464761
2011-May-24 01:29:22
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464762
2011-May-24 01:29:22
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464763
2011-May-24 01:29:21
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464764
2011-May-24 01:29:21
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464765
2011-May-24 01:29:21
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464766
2011-May-24 01:29:21
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464767
2011-May-24 00:41:14
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464768
2011-May-24 00:41:14
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464769
2011-May-24 00:41:14
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464770
2011-May-24 00:41:14
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464771
2011-May-24 00:41:12
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464772
2011-May-24 00:41:12
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464773
2011-May-24 00:41:12
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464774
2011-May-24 00:41:12
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464775
2011-May-24 00:14:15
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464776
2011-May-24 00:14:15
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464777
2011-May-24 00:14:15
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464778
2011-May-24 00:14:15
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464779
2011-May-24 00:14:14
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464780
2011-May-24 00:14:14
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464781
2011-May-24 00:14:14
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464782
2011-May-24 00:14:14
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking
2147464783
2011-May-24 00:13:57
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Forwarding
2147464784
2011-May-24 00:13:57
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Forwarding
2147464785
2011-May-24 00:13:57
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Blocking
2147464786
2011-May-24 00:13:57
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Blocking
2147464787
2011-May-24 00:13:56
Warning
%STP-W-PORTSTATUS: e8 of instance 1: STP status Forwarding
2147464788
2011-May-24 00:13:56
Warning
%STP-W-PORTSTATUS: e8 of instance 0: STP status Forwarding
2147464789
2011-May-24 00:13:56
Warning
%STP-W-PORTSTATUS: e7 of instance 1: STP status Blocking
2147464790
2011-May-24 00:13:56
Warning
%STP-W-PORTSTATUS: e7 of instance 0: STP status Blocking

The best way to get this resolved is to open a case with the Support Center and reference this thread. We would need to have a look at your configs to determine the issue. One thing that would likely work is for you to assign a different STP priority on each switch for each STP group.You can open a case by calling the following:
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
Ivor

REP MSTP Compatibility mode on Cisco 4500 ????

Hi all.
I having issue when deploy REP bethween Cisco 4500 Sup 7E/6LE with ASR 9000.
Follow the guide http://www.2mul.com/en/US/docs/routers/asr9000/software/asr9k_r4.0/lxvpn/configuration/guide/lesc40book.pdf , page 319 then ASR 9000 work at REP Access Gateway is supported when the access device (cisco 4500) interfaces that connect to the gateway devices are configured with REP MSTP Compatibility mode.
How to config REP MSTP Compatibility mode on interface of Cisco 4500 ??????????
How to config REP Access Gateway on ASR 9000 ???????????
Please help!
Thanks.

Tran,
you can configure REP-AG on the A9k as follows:
spanning-tree repag
int g0/0/0/0.1
int g0/0/0/0.1 l2trans
encap untagged
Note that REP-AG is not full rep, we only trigger on the TCN from the rep ring and invoke a mac flush then.
Because the 9k needs to be at the head of the ring you need to configure the following on your peer:
rep edge no-neighbor
and the compatibility mode is done via:
rep stcn stp
Finally, if the 2 endpoints of the rep ring are on the same device, you may want to put the encap untagged EFP's into an XCON or BD, if the 9k's are remote a PW to make sure that you can transport the TCN's from one ring point to the other if need be in specific design scenarios.
xander
sr Tech Lead ASR9000
CCIE

MSTP: fixing "equipment low tx power" location near

15454 9.2.1 MSTP
OTU2_XP 1-1 client port is 10GIG LAN PHY
I'm getting the following error in CTC:
Does this mean we are receiving low signal from the client's equipment, or does it mean that we are transmitting signal too low? Any way to correct this?

Roman,
Looking at the ONS 15454 Troubleshooting Guilde, your card is outputing (transmitting) a low signal level, compared to the threshhold, which may have been set by an admin. The guide provides a possible solution.
LO-TXPOWER
http://www.cisco.com/en/US/docs/optical/15000r9_2/dwdm/troubleshooting/guide/454d92_ts_chapter2.html#r_lotxpower
If the signal was too low coming (compared to the threshhold) into the card (say from the clients equipment), you would receive the following alarm:
LO-RXPOWER
http://www.cisco.com/en/US/docs/optical/15000r9_2/dwdm/troubleshooting/guide/454d92_ts_chapter2.html#r_lorxpower
I hope this helps!

Two SGE2000 in Stack and MSTP

Hi,
I have Blade Server and Blade Switches from Fujitsu-Siemens. Two Blade Switches are configured with port channel/trunk (2 ports on everyswitch in port-channel/trunk and then interconnected) and MSTP. They are functioning very well. Few days ago I got two SGE2000 switches and connected them in stack config and would like to make such configuration like in this picture : http://www.cisco.com/image/gif/paws/10556/16d.gif
Lets say "B" and "C" switches are mine blade switches. "A" would be mine SGE2000 stack. If I connect all of them this way and configure MSTP on every of them this does not work. As if the switches do not support MSTP and network traffic overall just "dies" as if there were some kind of broadcast storm. Am I missing something ? What should I do ?
Best regards

Hello Sir,
I believe you might do best by calling our support. Here is a link:
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
If you want to check into this a little more, there here are a few thoughts.
The switches do support MSTP. Have you checked for which switch is the root, do all switches agree? You also need to make sure all the configs are the same, native VLANs and allowed VLANs, instance IDs and vlan ranges, etc ...
A "broadcast storm" sounds like you have introduced a loop into the network, all the lights come on, and your network looks like a Christmas Tree. Is this what is happening? If the traffic simply dies, then this might indicate a port mismatch of some kind and the port is getting shut down by either system. Having ports shut down for mismatches is fairly common.
I would suggest placing these switches into your environment one at a time, and then watching to see which switch introduces the problem. Check the configs and make sure everything is compatible.
I would also suggest a call to our support center, as they might be able to answer your questions while you are adding the switches.
HTH,
Andrew Lissitz

MSTP vs RPVST

Similar Messages

Maybe you are looking for