Vubiq Networks Inc. V10G-L Benutzerhandbuch
55
Vubiq HaulPass V10g User Manual
© 2018 Vubiq Networks, Inc. All Rights Reserved
All parameters, except Path Cost and Priority, are specific for the port and not for CIST. These two parameters can
be set for each MSTI, but the other parameters cannot because they apply to the port. If, for example, spanning tree
is disabled (as it is for port 3), it applies to the CIST and all the MSTIs.
be set for each MSTI, but the other parameters cannot because they apply to the port. If, for example, spanning tree
is disabled (as it is for port 3), it applies to the CIST and all the MSTIs.
When using the ICLI, the CIST Aggregation Port Configuration commands are performed at the Config mode
prompt as follows:
prompt as follows:
(config)#
The CIST Normal Port Configuration commands are performed in the Config Interface mode prompt as follows:
(config-if)#
The following commands below assume that the user is in the interface config mode:
STP Enabled
A port can be individually enabled or disabled for taking part in the spanning tree protocol with the following
command:
command:
(config-if)# [no] spanning-tree
Path Cost and Priority
The path cost and priority are set by the following commands:
(config-if)# spanning-tree mst 0 cost <Cost>
(config-if)# spanning-tree mst 0 port-priority <Priority>
<Cost> is a number in the range 1 to 200000000 or it may be auto. If set to auto, the path cost will be set to some
value appropriate for the physical link speed, using IEEE 802.1D recommended values.
value appropriate for the physical link speed, using IEEE 802.1D recommended values.
<Priority> is a number in the range 0 to 240 and a multiple of 16. If it is not a multiple of 16 then it will be set to 0.
The path cost is used by STP when selecting ports. Low cost is chosen in favor of high cost. If two ports have the
same cost, then priority is used as a tie breaker.
same cost, then priority is used as a tie breaker.
Admin Edge and Auto Edge
These two features are activated by the following ICLI commands:
(config-if)# [no] spanning-tree edge (config-if)# [no] spanning-tree auto-edge
The first command changes the field Admin Edge in the web GUI, and the second changes Auto Edge. These two
values control how a port is declared to be an edge port or not. An edge port is a port which is not connected to a
bridge.
values control how a port is declared to be an edge port or not. An edge port is a port which is not connected to a
bridge.
If auto edge is enabled, then the port determines whether it is an edge port by registering if BPDUs are received on
that port. The admin edge determines what the port should start as, being edge or not, until auto edge if enabled,
then change.
that port. The admin edge determines what the port should start as, being edge or not, until auto edge if enabled,
then change.
The decision can be seen by selecting Monitor > Spanning Tree > Bridge Status, then clicking on CIST. Then the
Edge field shows the decision.
Edge field shows the decision.
Restricted Role and Restricted TCN
These two features are activated by the following ICLI commands:
(config-if)# [no] spanning-tree restricted-role (config-if)# [no] spanning-tree restricted-tcn
If restricted role is enabled it causes the port not to be selected as root port for the CIST or any MSTI, even if it has
the best spanning tree priority vector. Such a port will be selected as an alternate port after the root port has been
selected. If set, it can cause lack of spanning tree connectivity. It can be set by a network administrator to prevent
bridges external to a core region of the network to influence the spanning tree active topology, possibly because
those bridges are not under the full control of the administrator. This feature is also known as Root Guard.
the best spanning tree priority vector. Such a port will be selected as an alternate port after the root port has been
selected. If set, it can cause lack of spanning tree connectivity. It can be set by a network administrator to prevent
bridges external to a core region of the network to influence the spanning tree active topology, possibly because
those bridges are not under the full control of the administrator. This feature is also known as Root Guard.