iES12G
User’s
Manual
UM-iES12G-1.72.2-EN.docx
Pages 48 of 166
© 2020 IS5 COMMUNICATIONS INC. ALL RIGHTS RESERVED
Label
Description
Maximum Hop
Count
This defines the initial value of remaining hops for MSTI information generated
at the boundary of an MSTI region. It defines how many bridges a root bridge
can distribute its BPDU information. The range of valid values is 4 to 30 seconds,
and MaxAge must be <= (FwdDelay-1)*2.
Transmit Hold
Count
The number of BPDUs a bridge port can send per second. When exceeded,
transmission of the next BPDU will be delayed. The range of valid values is 1 to
10 BPDUs per second.
Advanced Settings
Edge Port BPDU
Filtering
Controls whether a port
explicitly
configured as
Edge
will transmit and receive
BPDUs.
Edge Port BPDU
Guard
Control whether a port
explicitly
configured as
Edge
will disable itself upon
reception of a BPDU. The port will enter the
error-disabled
state, and will be
removed from the active topology.
Port Error
Recovery
Control whether a port in the
error-disabled
state automatically will be enabled
after a certain time. If recovery is not enabled, ports have to be disabled and re-
enabled for normal STP operation. The condition is also cleared by a system
reboot.
Port Error
Recovery
Timeout
The time to pass before a port in the
error-disabled
state can be enabled. Valid
values are between 30 and 86400 seconds (24 hours).
Save
Click to save changes.
Reset
Click to undo any changes made locally and revert to previously saved values.
MSTI Mapping
This page allows the user to inspect the current Multiple Spanning Tree Instances (MSTI) bridge
instance priority configurations, and possibly change them as well.
Switches participating in MST instances must be constantly configured with the same MST configuration
information. The collection of switches which have the same MST information form an MST region.
Within each MST region, MSTP maintains multiple STIs. Instance 0 is known as IST. All other instances
are numbered from 1 to 15. The IST is the only spanning tree instance that sends and receives the MST
configuration messages, all other instance information are encapsulated in MST BPDUs. Thus, in MSTP
there are two contexts of operation, one in the context of the entire topology called Common and
Internal Spanning Tree (CIST), which is the default spanning tree instance for MSTP, and the other in the
context of each individual spanning tree context, that is, MSTI. [6]
