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
Similar Messages
-
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,
DarrenHi
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 -
Two root bridge in same network
Dear Team,
As I checked, there are two root bridge in the same LAN.
We have 6500 which is manually configured as root bridge and this is showing root for all the vlans in the network. Once switch connected to 6500 through 4500 is showing root for the vlans that not assigned to any of the port. Please help to clear it.
Setup
Cisco 6500 -- Cisco 4500 -- Cisco3560 -- Cisco 3560
Cisco 6500
CORE_SW#show spanning-tree root detail
VLAN0001
Root ID Priority 24577
Address 0025.84d9.ac80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0002
Root ID Priority 24578
Address 0025.84d9.ac80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Cisco 3560 Second
Access#show spanning-tree root de
VLAN0001
Root ID Priority 24577
Address 0025.84d9.ac80
Cost 16
Port 28 (GigabitEthernet0/4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0002
Root ID Priority 32770
Address 000a.b8ff.be00
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Here, I have not assigned any port in vlan 2 and this is showing root bridge for vlan 2. In which cases such thing can happen?
Thank You,
Abhisar.By default, Cisco switches run one spanning tree instance per VLAN and negotiate the topology with other connected switches. If your 3560 believes it is the root for VLAN 2 and there are no ports using VLAN 2, it will consider itself the to be the root because it hasn't been able to negotiate a topology for this VLAN with any other devices. This is normal. Once ports are connected to VLAN 2 and the 3560 can talk to the other switches, the spanning tree will be renegotiated and should behave as you expect.
If you want to have a single spanning tree topology for all VLANs and avoid this behaviour, consider moving to a single-instance MSTP configuration. -
i am new at metro ethernet. What is needed in a standard switch (Cat4500, Cat6500, etc) in order to support metroethernet services. thanks ahead
asanesHi,
It basically depends where you want to put the devices you stated in the network, looking at the devices I think you should have MPLS, LDP/RSVP and other standard routing protocol.
For access, you also should have STP (RSTP/MSTP) configured.
Please go through this link for further information
http://cisco.com/en/US/customer/netsol/ns341/ns396/ns223/ns227/networking_solutions_package.html
Cheers,
Sultan -
Sample configuration of using (MSTP) feature on 3560
Hi,
I have 3560 switch running PVST, performing purely as layer 2 vlans, I already reached 120 vlans so I will be running out of spantree soon.
I would like to have a sample configuration of using (MST) feature to map multiple vlans to a single vlan to minimize my maximum spantree per vlan usage.
Any sample config would be highly appreciated.
thanks,Hi Friend,
Have a look at this
Switch(config)# spanning-tree mst configuration
Switch(config-mst)# instance 1 vlan 10-20
Switch(config-mst)# name region1
Switch(config-mst)# revision 1
But I will recommend you to go through the complete link below to get full idea of MST before implementing in your network.
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swmstp.htm#wp1017196
HTH,if yes please rate the post
Ankur -
Load balancing imbalance in ACE
We are facing slowness an http application which is due to connection imbalance. This setup has one set of Load balancer and a proxy in DMZ where the connections gets terminated from the users and a load balancer inside LAN which load balances between the end point servers. All user connections terminate on the DMZ load balancer / proxy and proxy connects back to the internal load balancer VIP. (By collating a number of connections to very few - default proxy behavior) . Internal load balancer VIP does load balancing based on the number of connections in a least loaded manner and this load balancer doesn’t see how many sessions are beneath each connections and it distributes each connection to server underneath. Thus if one connection has around 100 sessions, another may have only a few and each of this gets forwarded to the end server causing the imbalance.
Is there a way that this imbalance can be tackled in this setup.
Users --> Proxy ---> Load balancer (Cisco ACE) --> Server 1
Server 2
Server 3
Least Connections predictor
HTTP Cookie insert stickyHi,
Persistance rebalance should solve the issue for you.
The persistent-rebalance function is required if you have proxy users and the proxy shares one TCP connection between multiple users.
With this behavior, inside a single connection you will see different cookies. Therefore, for each cookie, ACE needs to first detect the new cookie and then loadbalance to the appropriate server.
this is from the admin Guide :
The following example specifies the parameter-map type http command to enable HTTP persistence after it has been disabled:
host1/Admin(config)# parameter-map type http http_parameter_map
Host1/Admin(config-parammap-http)# persistence-rebalance
Please refer the following link for more info :
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA4_2_0/configuration/slb/guide/classlb.html#wp1062907
hope that helps,
Ajay Kumar -
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?
GreetingsWe found it:
Trap ist called "The value of vlanTrunkPortDynamicStatus" -
Hei,guys. As i got from the Cisco Official documents that the cmd to configure a root bridge has two styles. one is to set the switch to be root directly, and the other is to deploy the priority of the switch. However, I am confused by the cmd.
Switch(config)#spanning-tree Vlan 1 root primary
why should mention the Vlan 1 in the cmd. if it is the native vlan or other reasons?Wei,
A gross simplification but perhaps helpful to you:
Use Rapid PVST+ if you have at most tens of VLANs and the entire network is based on Cisco switches
Use MSTP if you have hundreds of VLANs or the network is composed of Cisco and non-Cisco switches
Do not either use or activate STP. Both Rapid PVST+ and MSTP will automatically downgrade their operation to STP if they detect an old neighbor on a per-port basis while retaining their advantages on remaining ports.
A good reading can be found here:
http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml
http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfc.shtml
http://blog.ine.com/2008/07/17/pvst-explained/
http://blog.internetworkexpert.com/2008/07/27/mstp-tutorial-part-i-inside-a-region/
http://blog.ine.com/2008/09/24/mstp-tutorial-part-ii-outside-a-region/
Best regards,
Peter -
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 ?
SimonWe'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 -
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 BlockingThe 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 -
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 regardsHello 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 -
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. -
RSTP/MSTP compatibility to Cisco REP (Resilience Ethernet Protocol)
hi,
need help to find a official document about RSTP/MSTP compatibility to Cisco's REP. I actually found a document but only STP was mentioned. Please refer to the link below.
http://www.cisco.com/en/US/prod/collateral/switches/ps6568/ps6580/prod_white_paper0900aecd806ec6fa.pdf
thanks,
shawnHello Shawn,
Apologies using my mobile and for some reason I must have deleted my post
Never implemented rep but after reviewing cco it seems its not compatible with stp -so in order to implement this - stp cannot be run on an rep
Segment
http://www.cisco.com/en/US/docs/ios-xml/ios/lanswitch/configuration/xe-3s/lsw-cfg-rep.html
Res
Paul -
Hi all the guru, i got 2 swtiches here. Cisco 3524 & Huawei 3900. I got three vLAN, which is VLAN 100 , 200 & 300. By default, Cisco are running PVST. Huawei is running IEEE STP, how can they talk to each other, without changing any configuration on Cisco site. Can Huawei run MSTP and divide each vlan into different instance to match PVST ? coz in PVST, each vLan have its own STP. Do you think its work like this ??? or any other good sugestion ?
The Cisco box will consider the Huawei as a hub for vlan 100, 200, 300. If there is no vlan 1 on your 3524, the Huawei will just not see the Cisco bridge.
So it will be the Cisco bridge that will block any potential loop between the two bridges, and you will be able to do some load balancing per-vlan configuring PVST. Convergence time wise, don't expect stellar result as this will regular STP calculation.
If the 3524 does not run MST, there is nothing much else you can do unfortunately...
Regards,
Francois
Maybe you are looking for
-
Iphone confused - thinks it is associated with more than one apple ID.
iTunes (v11.3) running on OS X.9.4 repeatedly crashes when I try to sync my wife's iPhone 5s (v7.1.2). Sometimes instead of crashing it gives the error message that my computer is no longer associated with my apple ID and to reauthorize it. I reaut
-
I have an iTunes account along with an older iPod and a new iPhone. My iTunes account shows about 50 songs on it. When I try to play about half of the songs, they play for 15 seconds and then it quits and goes on to the next song. Anybody have any id
-
Hi all i have a pdf that i generate with FOP then i want to print it in silent mode.I have try the FOAWTRenderer,PDFBox and the basic javax.print but the results are very far from the Acrobat or Foxit print. Any idea for this problem? Thanks
-
OSX 5.7 update display problems
I have never had problems with updates before. With 10.5.7 I have an external display running with my macbook, (which was connected during the install), but since installing the update, I cannot correct the display. Now my macbook display has turned
-
Making Examine utilty read only
We are managing 11.5.10.2 (RUP 3) instance. As per our Auditing requirements we have to disable Examine Utility (By setting the profile option Utilities:Diagnostics to No) but our support team members wanted to have this feature as it is required for