History of default port adminEdge settings on the SecureStacks

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 5756 

SecureStack C2
Firmware 3.03.33 and higher
SecureStack B2
Firmware 3.00.14 and higher
SecureStack A2
Firmware 1.02.12 and higher 

'set spantree adminedge'
Spanguard / Securespan failing to block ports
Port link state changes trigger Spanning Tree respan 

The default adminEdge settings have changed, since release of the product. 

On the SecureStack C2; by default adminEdge="true" through firmware 3.03.27, and adminEdge="false" with firmware 3.03.33 and higher. 

On the SecureStack B2; by default adminEdge="true" through firmware 2.01.10, and adminEdge="false" with firmware 3.00.14 and higher. 

On the SecureStack A2; by default adminEdge="true" through firmware 1.01.46, and adminEdge="false" with firmware 1.02.12 and higher. 

For optimal automated adminEdge behavior: 
  • On the SecureStack C2, upgrade to firmware 3.03.38 or higher.
  • On the SecureStack B2, upgrade to firmware 3.00.14 or higher.
  • On the SecureStack A2, upgrade to firmware 1.02.12 or higher.
As of the stated firmware versions, the default adminEdge behavior begins with the value set to "false" initially, after the device is powered up. If a Spanning Tree BDPU is not received on the port within a few seconds, the adminEdge setting changes to "true". This process should take approximately four seconds, in line with the behavior displayed on the DFE product line. 

As desired... 

With earlier firmware, on InterSwitch Link ports configure 'set spantree adminedge <port_string> false' to override the default setting. 

With later firmware, on Edge ports configure 'set spantree adminedge <port_string> true' to override the default setting. 

Any such operation must be performed via the CLI or WebView, as SNMP access is not yet supported for the dot1dStpPortAdminEdgePort= MIB, on the SecureStack line. 

See also: 5258 and 5759.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.