Reset Search



Difference between EOS Spanning Tree 'portadmin' and 'portenable' commands

« Go Back


TitleDifference between EOS Spanning Tree 'portadmin' and 'portenable' commands
Difference between Spanning Tree 'portadmin' and 'portenable' commands
The 'set spantree portadmin <port-string> {enable | disable}' command will enable/disable the Spanning Tree protocol on a per-port basis as long as STP is globally enabled (this is the default). If per-port spantree portadmin is disabled, any received BPDUs will be discarded and no BPDUs will be transmitted out this port. This command has no effect if STP is globally disabled ('set spantree stpmode none').

The 'set spantree portenable <port-string> {enable | disable}' command will enable/disable data traffic switching on a per-port basis. However, if disabled then operMAC will stay up and the port will still indicate link. Higher layer entities can still process traffic; but the traffic won't be learned/forwarded.
If you want to shut the port down completely, you would instead use 'set port disable <port-string>'. Note that there is no practical application that isn't met equally well using the 'set port disable <port-string>' command, which engages the ifMIB to disable the interface. The spanning tree command is an artifact of an earlier time.
Additional notes
also see:  Spanguard Considerations on EOS Switches

From legacy KB 5483,"Difference between Spanning Tree 'portadmin' and 'portenable' commands".
Ported here to resolve Hub thread

Also see Hub KB 5298, "General Port Administration tasks on Enterasys Products".




Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255