STP error

[Tore Valberg]

Yup. the problem seem to be your spanning-tree configuration.

First set all client ports as admin-edge ports, example:
"span int 1-22 admin-edge-port"

Make sure to set all ports that do not lead to another switch to admin-edge.

And make sure to do this on ALL switches with STP enabled

Then chose what switch you want to have as root-bridge. Set the priority on this switch to 1. Example
"span prio 1"

You also might want to pick a second switch as "backup root-bridge" Assign that switch priority 2.

Hope this helps

Tore

[Nikunj Damani]

Thank you Tore for the quick response.

I would like to experiment only on one switch first. Can I do it on one switch or I have to do it on all switches at the same time?
Also can you tell me the problem with the Spanning tree please because I will have to run it by my manager first before doing anything on the switch.

Thank you.

[Tore Valberg]

Hi

Yeah you should be able to test on one switch. At least for the port-toggling.

For the root-bridge change messages you probably need to set the priority as well.

Ill try and explain as good as i can"

Basically whenever a port looses link, goes up and down it will trigger Spanning-tree calculations.

Unless the port is configured as admin-edge.

Admin-edge is basically telling the switch that "this port is a infrastructure port, and should immediately forward data"

You might want to include this document in the discussion with your manager :)

http://h40060.www4.hp.com/procurve/uk/en/pdfs/application-notes/How_to_improve_and_harden_spanning-tree_configuration_Configuration_note_Dec_08_A4.pdf

Tore

[Tore Valberg]

Ohh, i also noticed the following errors:

W 04/20/90 01:51:22 snmp: SNMP Security access violation from 192.168.100.23
W 04/20/90 01:51:24 snmp: SNMP Security access violation from 192.168.100.23
W 04/20/90 01:51:26 snmp: SNMP Security access violation from 192.168.100.23
W 04/20/90 01:51:28 snmp: SNMP Security access violation from 192.168.100.23

Do you by any chance have a Procurve Manager sever running in the network?

In any case, it looks like the SNMP Management station with ip 192.168.100.23 is using a community name different then "public"

To get rid of these messages, correct the community name specified at the management station.

Tore

[Shadow13]

To add to what Tore mentioned, disable LACP if you are not using it by issuing the command

#no interface < interface range> LACP

[Nikunj Damani]

Tore, I read through the link you sent me and did a show spanning tree command. I saw that the 'Edge' is set to Yes. You can look at the log that I have included.


Rapid Spanning Tree Configuration

STP Enabled [No] : Yes
Force Version [RSTP-operation] : RSTP-operation
Switch Priority [8] : 8 Hello Time [2] : 2
Max Age [20] : 20 Forward Delay [15] : 15

Port Type | Cost Priority Edge Pnt-to-Pnt MCheck BPDU Filter
----- --------- + --------- -------- ---- ---------- ------ -----------
1 100/1000T | 20000 8 Yes True No No
2 100/1000T | 20000 8 Yes True No No
3 100/1000T | 20000 8 Yes True No No
4 100/1000T | 20000 8 Yes True No No
5 100/1000T | 20000 8 Yes True No No
6 100/1000T | 20000 8 Yes True No No
7 100/1000T | 20000 8 Yes True No No
8 100/1000T | 20000 8 Yes True No No
9 100/1000T | 20000 8 Yes True No No
10 100/1000T | 20000 8 Yes True No No
11 100/1000T | 20000 8 Yes True No No
12 100/1000T | 20000 8 Yes True No No
13 100/1000T | 20000 8 Yes True No No
14 100/1000T | 20000 8 Yes True No No
15 100/1000T | 20000 8 Yes True No No
16 100/1000T | 20000 8 Yes True No No
17 100/1000T | 20000 8 Yes True No No
18 100/1000T | 20000 8 Yes True No No
19 100/1000T | 20000 8 Yes True No No
20 100/1000T | 20000 8 Yes True No No
21 100/1000T | 20000 8 Yes True No No
22 100/1000T | 20000 8 Yes True No No
23 100/1000T | 20000 8 Yes True No No
24 100/1000T | 20000 8 Yes True No No

******************

[Tore Valberg]

Hi

Yeah that is as a result of auto-edge. By setting it to admin-edge the port will go immidiately to forward, instead of auto detecting it.

Tore

[Nikunj Damani]

Got you. I will try to do that and get back to you.
Might not be today.

Thanks