spanning-tree config on different Switch OS

[Chris991]

Hello!

I have to implement a core switch on a remote site.

However at the remote sites there are some legacy switches witch don´t support my created spanning-tree config.

CoreSwitch = E5406 has this config

spanning-tree

spanning-tree config-name "sus"

spanning-tree config-revision 1

spanning-tree priority 0 force-version rstp-operation

Edge Switchs should use this config

spanning-tree

spanning-tree config-name "sus"

spanning-tree config-revision 1

spanning-tree force-version RSTP-operation

E.g. the 2626 with #H.10.113

2626 # configure

2626 (config)# spanning-tree

The best practice recommendation by HP Networking is

to enable MSTP or MSTP in forced RSTP operation.

2626 (config)# spanning-tree config-name "sus"

Invalid input: config

2626 (config)# spanning-tree config-revision 1

Invalid input: config

2626 (config)# spanning-tree force-version RSTP-operation

Or the 2524 with #F.05.77

2524 (config)# spanning-tree

2524 (config)# spanning-tree config-name "sus"

Invalid input: config

2524 (config)# spanning-tree config-revision 1

Invalid input: config

2524 (config)# spanning-tree force-version RSTP-operation

2524 (config)#

In witch way I have to modify the config for this two types to work correctly in a spanning tree situation.

[Ian Vaughan]

Howdy,
Are you actually using "multiple instances" or are you just using the MSTP protocol and instance 0?
MSTP with just an instance 0 is functioanlly identical to RSTP so don't lose any sleep over it.
In fact to "fake" real (.1w) RSTP on a Cisco switch I have used MSTP with no additional instances.
Think of RSTP on these switches as the same as MSTP instance zero and you won't go far wrong as all timers etc are the same.
Works a treat.
The most MSTP instances I've ever needed was 3 and that was to provide basic load-sharing in a north-south direction and I wanted a heartbeat network to go east-west between SAP instances. It should never get any more complicated than that.
So:
Set your priority nice & low on your core switch.
Leave the others at default.
Use a consistent untagged vlan on your inter-switch links.
Use descriptive names on your vlans.
Keep your vlan numbering consistent.
use spanning-tree <port-no> admin-edge port on PC facing ports.
Your 2626 will support MSTP if you upgrade it, I have a 2650 with MSTP SNMPv3 + all mod cons. Still getting updates in Dec'13.
Best of luck
Ian

[pbs123]

Hi, did you get the solution for your problem?

I have the same problem, I didn't find any solution for this.

if you do, please post it here.

Thanks,