DGS-3024 Layer 2 Switch CLI Reference Manual
config stp
packets from other network devices when STP is disabled on the
Switch. The default is enabled.
Restrictions Only administrator-level users can issue this command.
Example usage:
To configure STP with maxage 18 and hellotime 4:
DGS-3024:4#config stp maxage 18 hellotime 4
Command: config stp maxage 18 hellotime 4
Success.
DGS-3024:4#
config stp ports
Purpose Used to setup STP on the port level.
Syntax
config stp ports <portlist> {cost [auto | <value 1-200000000>] |
priority <value 0-240> | migrate [yes | no] | edge [true | false] |
p2p [true | false | auto] | state [enable | disable]}
Description This command is used to create and configure STP for a group of
ports.
Parameters
<portlist> − Specifies a port or range of ports to be configured.
cost
•
•
− This defines a metric that indicates the relative cost of
forwarding packets to the specified port list. Port cost can be set
automatically or as a metric value. The default value is auto.
auto – Setting this parameter for the external cost will
automatically set the speed for forwarding packets to the
specified port(s) in the list for optimal efficiency. Default
port cost: 100Mbps port = 200000. Gigabit port = 20000.
<value 1-200000000> - Define a value between 1 and
200000000 to determine the external cost. The lower the
number, the greater the probability the port will be chosen
to forward packets.
priority <value 0-240> − Port Priority can be from 0 to 240. The lower
the number, the greater the probability the port will be chosen as the
Root Port. Default = 128.
migrate [yes | no] – yes will enable the port to migrate from 802.1d
STP status to 802.1w RSTP status. RSTP can coexist with standard
STP, however the benefits of RSTP are not realized on a port where
an 802.1d network connects to an 802.1w enabled network.
Migration should be enabled (yes) on ports connected to network
stations or segments that will be upgraded to 802.1w RSTP on all or
some portion of the segment.
edge [true | false] – true designates the port as an edge port. Edge
ports cannot create loops, however an edge port can lose edge port
status if a topology change creates a potential for a loop. An edge
67
To Next Page
Loading...
