Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

rstp takes about 30s to be ready... ?

Stefan Priebe
Frequent Advisor

rstp takes about 30s to be ready... ?

Hi!

I've two Brocade XMR and about 30 HP Switches which run rstp. If the root bridge fails (one of the XMR's) the whole network takes up to 30s to be ready again.

Is this normal? I thought at least with rstp it should be really fast.

When this happens i see a lot of messages like this:
"FFI: port 7-High collision or drop rate. See help."

The config of an HP Switch looks like this:
spanning-tree
spanning-tree 1 bpdu-filter bpdu-protection
...
spanning-tree 48 bpdu-filter bpdu-protection
spanning-tree priority 15 force-version RSTP-operation
loop-protect 1-48

Uplinks are at Port 49 and 50. 1-48 are clients.

Stefan
48 REPLIES
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

Do i have to set something like admin-edge or have i to remove loop-protect or spanning tree at all on the ports to the clients?
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

Did you configure the one XMR with say priority 0 ad the other with priority 1.

Secondly what kind of hp switches is it and what software version is on them.

KR
Gerhard
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

> Did you configure the one XMR with say
> priority 0 ad the other with priority 1.
One has Prio 0 and the other one Prio 8192.

> Secondly what kind of hp switches is it and
> what software version is on them.
2848, 2824 and 2650-48

2848 => 10.73
2824 => 10.73
2650 => 11.54

Does it make sense to use admin-edge? And if which ports should be configured as admin-edge? Could it make sense to disable spanning tree at all on the edge switches? Does it make sense to have loop-protection AND spanning tree on?
Richard Brodie_1
Honored Contributor

Re: rstp takes about 30s to be ready... ?

You haven't got the thing with the routers runnning 802.3w draft 3 like last time around?
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

No - we buyed new 2010 XMR routers :-) which only know 802-1w protocol.
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

First item to note. A spanning tree root-failure is about the worst thing that can happen to a spanning tree. This can potentially lead to a significant convergence time.

Edge-port does not really help with root bridge failure and new bridge election.

Let me digress for a bit and then come back.

I see you have bpdu-filter and bpdu-protection on your edge ports. Those two features are sort off mutually exclusive. I would suggest you only use BPDU-protection. ( Except if you have a client on the port that does not like spanning-tree BPDU's, I have seen some very old systems crashing if they receive an STP BPDU.)

If a port has BPDU filtering configured it does not mean it will skip the blocking state, it means it will ignore BPDU's after the initial blocking state and always stay forwarding.

It is a good policy to configure edge-ports as admin-edge though.
-- To see if this might help you in your situation, would you mind posting the output of show span and show sys for a few switches(one of each model), I just want to see the state of the ports.

The above note is where admin-edge port might help. Since admin-edge implies it will skip the initial blocking state. Lets look at the output first though.

Having said the above.
2824/68 => 10.73
2650 => 11.54 ( Is this not a 2610 ? )
I just want to verify the versions and models above to be sure. :).

-- FYI NOTE --
BPDU-protection is for checking if you receive BPDU's where you are not expecting them, and then protecting that port by shutting it down.

BPDU-filtering is for throwing away BPDU's and that is if you have a sport where you do not want BPDU information to be shared circa a point to point routed link between separate switch domains.

-- END FYI --

In the end yes RSTP is very quick but you have to get the configuration good and right, as there is many options.

HTH
Gerhard
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

First i would like to thank you for your detailed answer.

> This can potentially lead to a significant
> convergence time.
OK good to know - but how long is this normally?

OK first things i should think about are:
1.) only use bpdu-protection
2.) configure each port where only a client/server is attached as admin-edge
3.) 2650 => 11.54 ( Is this not a 2610 ? )
i'm sorry i meant 2610 my fault.

4.) i've attached a .txt file with sh sys and sh span from different switches and some more explanation which switch is connected to which one.

> In the end yes RSTP is very quick but you
> have to get the configuration good and
> right, as there is many options.
I'm sure my config isn't the best.

Stefan
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

I would make the following initial recommendations.
1. For all interswitchs links(trunks and ports) to disable the auto-edge functionality on them with:
no spanning-tree PORTNUMBERS auto-edge-port

2. For all the edge ports. I would personally remove BPDU-filtering
no spanning-tree PORTNUMBERS bpdu-filter

3. For all the edge ports enable admin-edge
spanning-tree PORTNUMBERS admin-edge-port

Be aware that some of you switches port 48 seemingly as interswitch links. It is a bit bad if you interswitch links are admin edge as this might lead to transcient loops.

Looking at your data, I have noticed some buffer misses, this might be attributed to transcient loops.

Watch out for loop-protect on inter-switch links.


Also lastly make sure you Brocade ports linking to the switches is not auto-edge or admin-edge ports. ( I do not know the command for that one or how to verify it in the config).

Then what I would suggest once you have everything configured through the whole LAN, give it a test. If it improves good, if not post the output of show logging for a few switches with redundant connections to the core.

The recovery itself giving a number of expected seconds is not really realistic it depends on some factors most of all the diameter of your network.

HTH
Gerhard

Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

Hi

i'm trying to put your suggestions into my config. But i've some problems:

> 1. For all interswitchs links(trunks and ports) to disable the auto-edge functionality on them with:
> no spanning-tree PORTNUMBERS auto-edge-port
You mean "admin-edge-port"?

There is no auto-edge-port config.. ?

2.) Shouldn't i also disable LACP where it is not in use? I've seen in log that the switches are also checking for LACP on each up / down.

3.) Does loop-protect work fine with Spanning-Tree?

I've this on one switch:
Loop Loop Loop Time Rx Port
Port Protection Detected Count Since Last Loop Action Status
---- ----------- --------- ---------- ---------------- ------------ --------
1 Yes Yes 1 6d,7h,2m,11s send-disable Up
2 Yes No 0 send-disable Up
3 Yes No 0 send-disable Up
4 Yes No 0 send-disable Up
5 Yes Yes 1 12m,35s send-disable Down
6 Yes No 0 send-disable Down
7 Yes No 0 send-disable Down
8 Yes No 0 send-disable Down
9 Yes Yes 1 12m,35s send-disable Down
10 Yes No 0 send-disable Down
11 Yes No 0 send-disable Down
12 Yes No 0 send-disable Down
13 Yes No 0 send-disable Down
14 Yes No 0 send-disable Down
15 Yes No 0 send-disable Down
16 Yes No 0 send-disable Down
17 Yes No 0 send-disable Down
18 Yes No 0 send-disable Down
19 Yes No 0 send-disable Up
20 Yes Yes 1 12m,30s send-disable Down
21 Yes No 0 send-disable Down
22 Yes No 0 send-disable Down

But i don't understand how it could detect a loop on f.e. port 5 where the port is down?! Also i don't understand why it detects a loop on port 1 and the port status is still up?!

Thanks again.

Stefan


Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

And what about point-to-point-mac option?
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

1. You should disable auto-edge if possible. I will admit I tested it aon a 5400, and I just checked on a 2800 and I see that that option is not there.
no admin-edge should be fine.

2. Definitely disable LACP where it is not needed. This won't help with spanning tree, but it can create a security issue in practice.

3. Loop protect works fine with spanning tree.

The default behaviour for loop protect is to disable the port. Then you have to manually enable the port again. So yes you should see the loops detected on "down" ports.

You will notice in the release notes where loop-protect is documented that you should use it with spanning tree.

4. Now regarding the point to point mac.
That one is a bit difficult to describe, effectively it means if you have a shared ethernet medium between a se tof switch ports.

I.e. you have three switch link together through a hub.
Switch1-Port1<==>HUB-Port1
Switch2-Port1<==>HUB-Port2
Switch3-Port1<==>HUB-Port3
In that case you would disable point to point mac(This should happen automatically since it assumes hds=shared)

If you have any switches link together via a transparent bridge without spanning tree support that supports full duplex operation you should manually disable this.

This means you have a point-to-point mac sublayer and not or multi-point mac sublayer.

If you disable this you loose in effect the gains of rapid port state transitions.

From what I have seen of your topology description. Leaving the defaults *should* be fine.


HTH
Gerhard




Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

thanks again - but i'm still now sure whether spanning tree and loop protect work correctly.

Here is the output of both. Some ports are eben not connected at all and other are in state blocking throught STP but are still detected as loop.

Status and Counters - Loop Protection Information

Transmit Interval (sec) : 5
Port Disable Timer (sec) : 300
Loop Detected Trap : Disabled


Loop Loop Loop Time Rx Port
Port Protection Detected Count Since Last Loop Action Status
---- ----------- --------- ---------- ---------------- ------------ --------
1 Yes Yes 1 6d,8h,45m,24s send-disable Up
2 Yes No 0 send-disable Up
3 Yes No 0 send-disable Up
4 Yes No 0 send-disable Up
5 Yes Yes 1 1h,55m,49s send-disable Down
6 Yes No 0 send-disable Down
7 Yes No 0 send-disable Down
8 Yes No 0 send-disable Down
9 Yes Yes 1 1h,55m,49s send-disable Down
10 Yes No 0 send-disable Down
11 Yes No 0 send-disable Down
12 Yes No 0 send-disable Down
13 Yes No 0 send-disable Down
14 Yes No 0 send-disable Down
15 Yes No 0 send-disable Down
16 Yes No 0 send-disable Down
17 Yes No 0 send-disable Down
18 Yes No 0 send-disable Down
19 Yes No 0 send-disable Up
20 Yes Yes 1 1h,55m,44s send-disable Up
21 Yes No 0 send-disable Down
22 Yes No 0 send-disable Down

Rapid Spanning Tree (RSTP) Information

STP Enabled : Yes
Force Version : RSTP-operation

Switch Priority : 40960 Hello Time : 2
Max Age : 20 Forward Delay : 15

Topology Change Count : 2579
Time Since Last Change : 61 mins

Root MAC Address : 002438-2c8d80
Root Path Cost : 40000
Root Port : 23
Root Priority : 0

Root Guard Ports :
TCN Guard Ports :
BPDU Protected Ports : 2,6-8,10-18,21-22
BPDU Filtered Ports :

Port Type Cost Priority State | Designated Bridge
----- --------- --------- -------- ---------- + -----------------
1 100/1000T 20000 144 Blocking | 000e7f-6e6a60
2 100/1000T 200000 144 Forwarding | 000f20-ce9f00
3 100/1000T 20000 144 Blocking | 000e7f-6e6a60
4 100/1000T 200000 144 Blocking | 000e7f-6e6a60
5 100/1000T 200000 144 Disabled |
6 100/1000T 20000 144 Disabled |
7 100/1000T 20000 144 Disabled |
8 100/1000T 20000 144 Disabled |
9 100/1000T 200000 144 Disabled |
10 100/1000T 20000 144 Disabled |
11 100/1000T 20000 144 Disabled |
12 100/1000T 20000 144 Disabled |
13 100/1000T 20000 144 Disabled |
14 100/1000T 20000 144 Disabled |
15 100/1000T 20000 144 Disabled |
16 100/1000T 20000 144 Disabled |
17 100/1000T 20000 144 Disabled |
18 100/1000T 20000 144 Disabled |
19 100/1000T 20000 144 Blocking | 000e7f-6e6a60
20 100/1000T 20000 144 Blocking | 000e7f-6e6a60
21 100/1000T 20000 144 Disabled |
22 100/1000T 20000 144 Disabled |
23 100/1000T 20000 96 Forwarding | 000e7f-6e6a60
24 1000SX 20003 112 Blocking | 001bed-b04e80

Stefan
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

What is connected to those ports above that is in the blocking state ?

You should use STP on the inter switch links and not loop protect though.

Spanning tree - Is for creating a loop free switched(bridged) topology.

You should use Loop-protect on your edge ports. Loop-protect is there to get rid of "unexpected loops" remember it complements spanning tree and is not a 100% replacement.

Using loop-protected on the inter switch links might lead to some funnies. I.e. a an inter switch link toggling every 300 seconds. Inherently the failover time when using loop-protect would be 300seconds+.

Some of your counters for loops detected seems quite old .

What is worrying
1 100/1000T 20000 144 Blocking | 000e7f-6e6a60 <<<<<**
3 100/1000T 20000 144 Blocking | 000e7f-6e6a60 <<<<<**
4 100/1000T 200000 144 Blocking | 000e7f-6e6a60 <<<<<**
19 100/1000T 20000 144 Blocking | 000e7f-6e6a60 <<<<<**
20 100/1000T 20000 144 Blocking | 000e7f-6e6a60 <<<<<**

Seems those ports have a legitimate loop.

Also remember loop-protect does not use STP BPDUs to detect a loop, so this means if a port goes into forwarding by STP, and it receives a loop-protect BPDU from the same switch that switch-port will be disabled by loop-protect. Hence my statement of do not use loop-protect on inter switch links.

Remember to look at the counter "Time since last loop" field.

This *could* explain what you are seeing.
Topology change ... STP changes forwarding path... loop protects blocks a different port .... new topology change.

My Suggestion
Fully document the network and all inter switch links.
Remove loop-protect.
Tune spanning tree on inter switch links, and get all the parameters correct.
Tune spanning tree on all edge-ports make sure they are all edge-port.
Test spanning tree failover.
Now enable loop-protect on edge ports that is not under secure control.
Test spanning tree failover again.

Just a side note
show spanning-tree detail will help. For an edge port that is online it should contain.
AdminEdgePort : Yes
OperEdgePort : Yes
For an inter switch link. It should be
AdminEdgePort : No
OperEdgePort : No

HTH
Gerhard


Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

> What is connected to those ports above that is in the blocking state ?

A normal Switch - sometimes an unmanaged switch sometimes a managed switch.

> You should use STP on the inter switch links > and not loop protect though.
On a lot of switches i don't even know if the customer connects a switch or a computer to it. So i wanted to activate STP AND loop-protect. To be shure that even when BPDUs are blocked the network is loop free.

But in my case we see that the state is blocking to stp is working fine.


Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

OK i think a concrete example could help.

I've tried the following:
Two ports on two different switches connected to another switch.

Details on these ports:
Port 4 on Switch I:
Status and Counters - RSTP Port(s) Detailed Information

Port : 4
Status : Up
BPDU Protection : No
BPDU Filtering : No
Role : Designated
State : Forwarding
Priority : 128
Path Cost : 20000
Root Path Cost : 20000
Root Bridge ID : 0:002438-2c8d80
Designated Bridge ID : 12288:000e7f-6e6a60
Designated Port ID : 128:4
AdminEdgePort : Yes
OperEdgePort : Yes
AdminPointToPointMAC : True
OperPointToPointMAC : Yes
Aged BPDUs Count : 0
Loop-back BPDUs Count : 0
TC Detected : 83
TC Flag Transmitted : 0 TC ACK Flag Transmitted : 0
TC Flag Received : 0 TC ACK Flag Received : 0

RSTP RSTP CFG CFG TCN TCN
BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx
---------- ---------- ---------- ---------- ---------- ----------
310830 331 0 0 0 0


Port 3 on Switch II:
Status and Counters - RSTP Port(s) Detailed Information

Port : 3
Status : Up
BPDU Protection : No
BPDU Filtering : No
Role : Alternate
State : Blocking
Priority : 144
Path Cost : 20000
Root Path Cost : 20000
Root Bridge ID : 0:002438-2c8d80
Designated Bridge ID : 12288:000e7f-6e6a60
Designated Port ID : 128:4
AdminEdgePort : Yes
OperEdgePort : No
AdminPointToPointMAC : True
OperPointToPointMAC : Yes
Aged BPDUs Count : 0
Loop-back BPDUs Count : 0
TC Detected : 87
TC Flag Transmitted : 0 TC ACK Flag Transmitted : 0
TC Flag Received : 0 TC ACK Flag Received : 0

RSTP RSTP CFG CFG TCN TCN
BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx
---------- ---------- ---------- ---------- ---------- ----------
465 310936 0 0 0 0

Loop protection is on both ports disabled.

I then disabled Port 4 on Switch I which is active at the moment. Then it tooks 40s until Switch II Port 3 goes from Blocking state into Forwarding state. Most of the time it is in Learning and Listening state.

When i then enable port 4 again on Switch I it tooks only 3s to switch back.

Are these 40s really normal?

Stefan
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

You picked a very good example. If you look at SwitchI I see the following for port 4.

AdminEdgePort : Yes
OperEdgePort : Yes

That means that port will participate in STP but you might see some funnies, like extended failover times.

I also notice that that port is transmitting(TX) and receiving(RX) RSTP BPDUs.

That specific port should not be an admin edge port.

For SwitchII I notice
AdminEdgePort : Yes
OperEdgePort : No

It is an Admin-edge-port, it should not be an admin-edge-port but it is operating as a non-edge port.

If it goes through learning and listening mode it means it is not going through RSTP rapid state transitions.

Where are these ports connected to ?
Would you be able to post the same output for the neighbouring ports ? I.e. SwitchI port4 is connected to SwitchIII port 4 then post the "show span detail" for that port.
What are the models of SwitchI and SwitchII ?
Can you post an extract of your Brocade config containing the STP configuration ?

Thanks in advance.

HTH
Gerhard
Gerhard Roets
Esteemed Contributor

Re: rstp takes about 30s to be ready... ?

Hi Stefan

I missed the tiny in between post. It explains a lot.

In that case the scenario changes a lot , and this should be treated a little bit differently. Since you have ethernet devices outside your sphere of influence.

Am I correct in saying you basically provide an IP service to a customer over an ethernet device ?

Is it more than one customer on the same infrastructure ?

Does the customers have redundant connections ?

You mention customers can install there own switches this introduce a risk to STP.

I woulsd move the config to saying the following then.

1. BPDU filtering on the "untrusted edge". You do not want unknown devices to be able to effect your spanning tree. A customer can in theory pull you spanning tree root out from under you, especially if your Primary root goes down. This might effect other customers.
2. Loop-protect on the edge, be aware though that customers can accidentally filter loop-protect BPDU's.
3. Some kind of broadcast limiting on the edge ports to avoid a customer from accidentally looping your network down.

This really changes the ballgame, and I might suggest you need to look for support outside the scope of a forum as this might involve other choices to be made.

HTH
Gerhard




Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

Mhm i thought about my two last posts. They are not completely correct.

In 99,9% we manage the switch behind or the customer do not have access to the equipment. In my example there is a switch behind port 3 and 4 which is managed by us. So in this case the stuff should work fine?

So you want to have a show span detail of the ports on Switch III which are connected to Switch I and II?

Stefan
Richard Brodie_1
Honored Contributor

Re: rstp takes about 30s to be ready... ?

"So you want to have a show span detail of the ports on Switch III which are connected to Switch I and II?"

That would be helpful - and maybe show span for an overview also.
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

OK on Swith III spanning-tree isn't enabled - but is this a problem? I mean when spanning-tree is disabled the switch should still forward bpdu packets?
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

I've now enabled spanning-tree on Switch III but this doesn't change anything.

Here is the output:
Multiple Spanning Tree (MST) Information

STP Enabled : Yes
Force Version : RSTP-operation
IST Mapped VLANs : 1-4094
Switch MAC Address : 0024a8-f30fc0
Switch Priority : 32768
Max Age : 20
Max Hops : 20
Forward Delay : 15

Topology Change Count : 7
Time Since Last Change : 90 secs

CST Root MAC Address : 002438-2c8d80
CST Root Priority : 0
CST Root Path Cost : 40000
CST Root Port : 25

IST Regional Root MAC Address : 0024a8-f30fc0
IST Regional Root Priority : 32768
IST Regional Root Path Cost : 0
IST Remaining Hops : 20

Root Guard Ports :
TCN Guard Ports :
Protected Ports : 1-24
Filtered Ports : 1-24

| Prio | Designated Hello
Port Type | Cost rity State | Bridge Time PtP Edge
----- --------- + --------- ----- ---------- + ------------- ----- --- ----
1 10/100TX | Auto 128 Disabled |
2 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
3 10/100TX | Auto 128 Disabled |
4 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
5 10/100TX | Auto 128 Disabled |
6 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
7 10/100TX | Auto 128 Disabled |
8 10/100TX | Auto 128 Disabled |
9 10/100TX | Auto 128 Disabled |
10 10/100TX | Auto 128 Disabled |
11 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
12 10/100TX | Auto 128 Disabled |
13 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
14 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
15 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
16 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
17 10/100TX | Auto 128 Disabled |
18 10/100TX | Auto 128 Disabled |
19 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
20 10/100TX | Auto 128 Disabled |
21 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
22 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
23 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
24 10/100TX | 200000 128 Forwarding | 0024a8-f30fc0 2 Yes Yes
25 100/1000T | 20000 128 Forwarding | 000e7f-6e6a60 2 Yes No
26 100/1000T | 20000 128 Forwarding | 0024a8-f30fc0 2 Yes No
27 | Auto 128 Disabled |
28 | Auto 128 Disabled |


Status and Counters - CST Port(s) Detailed Information

Port : 25
Status : Up
BPDU Protection : No
BPDU Filtering : No
Errant BPDU Count : 0
Root Guard : No
TCN Guard : No
MST Region Boundary : Yes
External Path Cost : 20000
External Root Path Cost : 20000
Administrative Hello Time : Global
Operational Hello Time : 2
AdminEdgePort : No
Auto Edge Port : No
OperEdgePort : No
AdminPointToPointMAC : True
OperPointToPointMAC : Yes
Aged BPDUs Count : 0
Loop-back BPDUs Count : 0
TC ACK Flag Transmitted : 0
TC ACK Flag Received : 0

MST MST CFG CFG TCN TCN
BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx
---------- ---------- ---------- ---------- ---------- ----------
0 0 0 0 0 0



Status and Counters - CST Port(s) Detailed Information

Port : 26
Status : Up
BPDU Protection : No
BPDU Filtering : No
Errant BPDU Count : 0
Root Guard : No
TCN Guard : No
MST Region Boundary : Yes
External Path Cost : 20000
External Root Path Cost : 40000
Administrative Hello Time : Global
Operational Hello Time : 2
AdminEdgePort : No
Auto Edge Port : No
OperEdgePort : No
AdminPointToPointMAC : True
OperPointToPointMAC : Yes
Aged BPDUs Count : 0
Loop-back BPDUs Count : 0
TC ACK Flag Transmitted : 0
TC ACK Flag Received : 0

MST MST CFG CFG TCN TCN
BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx BPDUs Tx BPDUs Rx
---------- ---------- ---------- ---------- ---------- ----------
0 0 0 0 0 0


Stefan
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

Anybody any idea to my last post?
Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

OK - it def. seems i've to check the whole network.

At the moment i've found out that i've two HP 1800-24G which doesn't seem to support STP actively but i thought that even then the Switches in fron of it will handle this. But in this case it also takes 30-40s if the forwarding port fails.

Is this normal? or do i have to replace the 1800-24G with another switch. I thought they'll simply forward the BPDU packets and the backup switch will block the port and will go immediatly to forwardig state after the man switch fails.

Stefan Priebe
Frequent Advisor

Re: rstp takes about 30s to be ready... ?

Also 2650 switches seems to be problematic. My uplink switches 2848 always detect the port as a loop even if span tree on the 2650 is enabled. This doesn't happen with a 2610 with enabled spanning tree.