STP mode or default, whats the difference?

[Anonymous]

Hi there,

Working on a site that has adopted an odd configuration for spanning-tree that I'm trying to make sense of. The below is an edited example taken from an edge switch. The network consists of all extreme devices.

Its seems as though PVST+ has been adopted as the spanning tree protocol between switchs and RSTP else where.

One of the things I can't make complete sense of is the 'mode', and then the 'default-encapsulation', then configuration of the spanning-tree protocol on the uplink ports.

My question is, if you configure the mode, say dot1w, then does configuring the default-encapsulation for that same STP domain (say pvst-plus) override it?

Also, as in the case of the STP domain of s1, is there any need to specify pvst-plus on the port 1:48 if you have already configured the 'default-encapsulation' as pvst-plus?

create stpd s1
configure stpd s1 mode dot1w
enable stpd s1 rapid-root-failover
configure stpd s1 default-encapsulation pvst-plus
create stpd s2
configure stpd s2 mode dot1w
enable stpd s2 rapid-root-failover
create stpd s3
configure stpd voice mode dot1w
enable stpd voice rapid-root-failover
configure stpd voice default-encapsulation dot1d

configure stpd mangament tag 1000
configure stpd data tag data 500
configure stpd data tag data 300

enable stpd management
enable stpd data
enable stpd voice

enable stpd s0 auto-bind vlan Default
enable stpd s1 auto-bind vlan management
enable stpd s2 auto-bind vlan data
enable stpd s3 auto-bind voice

configure stpd s1 add vlan managment ports 1:48 pvst-plus
configure stpd s2 add vlan data ports 1:48 pvst-plus
configure stpd s3 add vlan voice ports 1:48 pvst-plus

I believe the answer is that the default encapsulation will override it, and with auto-bind on each of the stp domains of each of the ports will automatically bind to the default encapsulation type of the Vlans configured. So there is no need to add the addition of pvst-plus on port 1:48 for s1?

Should the default encapsulation type not be compatible it will step back to that configured for the mode?

I base that on the output below that shows

STACK.7 # show stpd "voice" ports 1:2 detail
Stpd: DATA Port: 1:2 PortId: 8002 Stp: ENABLED Path Cost: 200000
Port Mode: 802.1D
Port State: FORWARDING Topology Change Ack: FALSE
Port Priority: 128
Designated Root: 10:00:02:04:96:27:89:1c Designated Cost: 18000
Designated Bridge: 80:00:02:04:96:83:78:bf Designated Port Id: 8002
Partner STP version: Dot1w
Restricted Role: Disabled
Active Role: Disabled
Edge Port Safe Guard: Disabled
Bpdu Restrict: Disabled
Participating Vlans: voice

STACK.8 # show stpd "management" ports 1:2 detail
Stpd: managment Port: 1:2 PortId: 8002 Stp: ENABLED Path Cost: 200000
Port Mode: PVST+
Port State: FORWARDING Topology Change Ack: FALSE
Port Priority: 128
Designated Root: 10:00:02:04:96:27:89:1c Designated Cost: 18000
Designated Bridge: 80:00:02:04:96:83:78:bf Designated Port Id: 8002
Partner STP version: Dot1w
Restricted Role: Disabled
Active Role: Disabled
Edge Port Safe Guard: Disabled
Bpdu Restrict: Disabled
Participating Vlans: management

Many thanks in advance

[Anonymous]

Just bumping this one as I'm going to need the answer very soon in order to correct any configuration errors. Thanks

[Anonymous]

How are you getting on Mike. Thanks

[Anonymous]

Thanks Mike