Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

Simplest option to designate STP route bridege.

Twin_Turbo
Advisor

Simplest option to designate STP route bridege.

Our network has never properly had STP configured.

As it stands we have a mix of Procurve and Comware (the new core) . I am not overly familiar with the concept of MST/IST although I have used RSTP previously.

Our route bridge is an old 3500YL that has the lowest MAC address and the same Bridge ID as all the other switches. This switch sits at our Disaster site 5 miles away down a 1GB Leased line...

I want to do the simplest work possible to make the Comware7 5700FF at head office the route bridge for the network.

I want to disable STP across the 1GB LAN as it makes no sense having it.

Our actual present topology has no redundant links anyway.

Cheers

Rob

 

5 REPLIES
johnk3r
Respected Contributor

Re: Simplest option to designate STP route bridege.

First: What version of STP you are running in your environment (STP, RSTP / MSTP)?

To configure 5700FF as root STP topology, just type the following:

global enable stp -> enabling STP on the switch
stp mode rstp ---> setting the version of STP
stp root primary ---> Setting the switch to be the root of the STP topology.

 After this setting, the 5700 will have the information bridge ID like: 0.4667-870a-0100

For 1GB ports, you can configure them as "edge-port".

After making these settings, enter here the command output: 

dis stp brief

 

**************************************
ATP FLEXNETWORK V3 | ACSA
Twin_Turbo
Advisor

Re: Simplest option to designate STP route bridege.

I guess MSTP judging by the tow outputs.

Cheers

Rob

 

THE Comware Core

<SW-HO-CORE-1>disp stp
-------[CIST Global Info][Mode MSTP]-------
 Bridge ID           : 32768.5c8a-3842-723b
 Bridge times        : Hello 2s MaxAge 20s FwdDelay 15s MaxHops 20
 Root ID/ERPC        : 32768.0016-b96c-2380, 20038
 RegRoot ID/IRPC     : 32768.5c8a-3842-723b, 0
 RootPort ID         : 128.40
 BPDU-Protection     : Disabled
 Bridge Config-
 Digest-Snooping     : Disabled
 TC or TCN received  : 2949
 Time since last TC  : 4 days 18h:41m:32s

----[Port683(Bridge-Aggregation1)][FORWARDING]----
 Port protocol       : Enabled
 Port role           : Designated Port (Boundary)
 Port ID             : 128.683
 Port cost(Legacy)   : Config=auto, Active=14
 Desg.bridge/port    : 32768.5c8a-3842-723b, 128.683
 Port edged          : Config=disabled, Active=disabled
 Point-to-Point      : Config=auto, Active=true
 Transmit limit      : 10 packets/hello-time
 TC-Restriction      : Disabled
 Role-Restriction    : Disabled

 

ONE OF THE PROCURVE

SW-DR-EDGE-1# show span

 Multiple Spanning Tree (MST) Information

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

  Topology Change Count  : 296
  Time Since Last Change : 4 days

  CST Root MAC Address : 0016b9-6c2380
  CST Root Priority    : 32768
  CST Root Path Cost   : 20000
  CST Root Port        : D23

  IST Regional Root MAC Address : 0024a8-6d0200
  IST Regional Root Priority    : 32768
  IST Regional Root Path Cost   : 0

Twin_Turbo
Advisor

Re: Simplest option to designate STP route bridege.

After setting both ends of the WAN link to

"STP EDGED-PORT"

and then setting the switch priotity

"STP ROOT PRIMARY" on each main switch at each site.

I expected site A to become the root for Site A, and Site B the root for Site B.

But site B "xxxxxxx:6505" is still the CIST root? And all switches now reference Site B Core.

 

-------[CIST Global Info][Mode MSTP]-------
 Bridge ID           : 0.5c8a-3842-723b
 Bridge times        : Hello 2s MaxAge 20s FwdDelay 15s MaxHops 20
 Root ID/ERPC        : 0.5c8a-3842-6505, 20
 RegRoot ID/IRPC     : 0.5c8a-3842-723b, 0
 RootPort ID         : 128.40
 BPDU-Protection     : Disabled
 Bridge Config-
 Digest-Snooping     : Disabled
 Root type           : Primary root
 TC or TCN received  : 3085
 Time since last TC  : 0 days 13h:29m:12s

 

I could convert Site B to "Secondary" but was expecting the two site to now be independant...

 

Rob

 

 

 

 

 

 

Linkk
Frequent Advisor

Re: Simplest option to designate STP route bridege.

I assume that you have one link between your sites that are directly connected to the switches. 

To stop the switches sending BPDUs use this command on the ProCurve switch:

 

Switch (config)# spanning-tree <interface> bpdu-filter
Switch (config)# spanning-tree <interface> admin-edge-port

And this on the Comware:

 

 

[Switch-GigabitEthernet1/0/10]stp edged-port enable

 

This should prevent the switches sending BPDUs to each other on this ports. There should two seperate root switches now.

 

Twin_Turbo
Advisor

Re: Simplest option to designate STP route bridege.

 ends are comware.

I tried  "bpdu-drop any" a couple of weeks back and that just stopped all trraffic ( it's a hybrid L2/L3 link)

Last night I set the Disaster site as priority secondary and that's more or less achived what's needed.

 

Rob