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

[Stefan Priebe]

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]

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]

Anybody any idea to my last post?

[Stefan Priebe]

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]

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.

[Stefan Priebe]

Is there a way to recheck for loops? When i've a 2650 switch and the 2848 detected a loop. I can do a no loop-protect port 1 wait 2 min then do again a loop-protect port 1. And then it doesn't detect the loop again... strange

[Gerhard Roets]

Hi Stefan

From what I am seeing in this thread I would suggest the following.

1. Document your topology. Focusing on what is under your administrative control(Include switch models and software versions).

Check for fixes on the software versions that might be related to spanning tree.

2. Plan a spanning tree topology from scratch. A strong hint is NOT to use loop protect on inter switch links.

3. Start it small. Focus on the devices under your administrative control. Get it to work nice and quick there.

4. Implement loop protect only towards the edge.

5. Keep spanning tree in the "CORE" and "DISTRIBUTION" and have it active on all STP capable devices.

6. Move devices that only support STP to the edge.

7. Move devices that do not support spanning tree to the edge's edge :).

A small item to note regarding your last post. Loop-protect frames will not be sent out spanning tree blocked ports.
So if you imagine a small triangle network
SWITCH1 <====> SWITCH2 <====> SWITCH3 <====> SWITCH1

Now if you enable ONLY loop-protect the switch that receives its loop-protect frame back first will disable the port the received loop-protect packet was received on.

Now if you enable spanning tree AND loop protect one of 2 things can happen.
1. If you have a good spanning tree configuration and no transient loops loop-protect will never detect a loop.
2. If you have a transcient loop dues to funny timers etc you might get a port being disabled by loop-protect.
-- If loop protect auto re-enables you will get a new topology change.

----
I realize this is a huge amount of work but in the long run having a planned ancd predictable spanning tree should really help.

HTH
Gerhard

[Stefan Priebe]

OK i'll try todo this now. One question.

Should i configure a port differently if it is a connected to a switch which knows about rstp (f.e. 2610) or connected to a switch which doesn't know spanning tree at all (f.e. HP 1800G-24).

At the moment my config for a switchport which is connected to another switchport which knows rstp and is under my control looks like this:

f.e. port 23:
int e 23 broadcast-limit 0
no int 23 lacp
no spanning-tree 23 admin-edge-port
no spanning-tree 23 auto-edge-port
no spanning-tree 23 bpdu-protection
no spanning-tree 23 bpdu-filter
spanning-tree 23 point-to-point-mac true
no loop-protect e 23

Stefan

[Gerhard Roets]

Hi Stefan

Yes indeed they should be treated differently.

For your RSTP aware connected device it looks sane.

Now the 1800 is a difficult one. Since it does not support STP.

If you want to have redundant connection to an 1800 remember you are tied down to that loop-protect enable timer.

Do you daisy chain 1800s below one another ?
Do you use 1800s and 1810s ?

KR
Gerhard

[Stefan Priebe]

> Do you daisy chain 1800s below one another ?
Sorry no native english speaker what does daisy chain mean?

> Do you use 1800s and 1810s ?
no only some plain J9028A/B ProCurve Switch 1800-24G devices

I've updated a 1800 device today. On the 2848 Switch which is the uplink for the 1800 i got this:
08/25/10 17:01:46 FFI: port 45-High collision or drop rate. See help.
W 08/26/10 09:23:10 system: Out of pkt buffers; miss count: 437000
I 08/26/10 12:22:21 ports: port 20 is now off-line
I 08/26/10 12:22:43 ports: port 20 is Blocked by STP
I 08/26/10 12:22:44 ports: port 20 is now on-line
W 08/26/10 12:22:44 system: Out of pkt buffers; miss count: 484167
W 08/26/10 12:23:03 FFI: port 1-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 2-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 3-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 4-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 5-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 6-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 7-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 8-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 9-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 10-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 11-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 12-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 13-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 14-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 15-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 16-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 17-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 18-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 19-High collision or drop rate. See help.
W 08/26/10 12:23:03 FFI: port 20-Excessive Broadcasts. See help.
W 08/26/10 12:23:03 FFI: port 45-High collision or drop rate. See help.

Is this normal?

Stefan