C
HAPTER
35
| ERPS Commands
– 1111 –
COMMAND USAGE
â—† Each node must be connected to two neighbors on the ring. For
convenience, the ports connected are referred to as east and west
ports. Alternatively, the closest neighbor to the east should be the next
node in the ring in a clockwise direction, and the closest neighbor to the
west should be the next node in the ring in a counter-clockwise
direction.
â—† Note that a ring port cannot be configured as a member of a spanning
tree, a dynamic trunk, or a static trunk.
â—† If a port channel (static trunk) is specified as a ring port, it can not be
destroyed before it is removed from the domain configuration.
â—† A static trunk will be treated as a signal fault, if it contains no member
ports or all of its member ports are in signal fault.
â—† If a static trunk is configured as a ring port prior to assigning any
member ports, spanning tree will be disabled for the first member port
assigned to the static trunk.
EXAMPLE
Console(config-erps)#ring-port east interface ethernet 1/12
Console(config-erps)#
rpl neighbor This command configures a ring node to be the Ring Protection Link (RPL)
neighbor. Use the no form to restore the default setting.
SYNTAX
rpl neighbor
no rpl
DEFAULT SETTING
None (that is, neither owner nor neighbor)
COMMAND MODE
ERPS Configuration
COMMAND USAGE
â—† The RPL neighbor node, when configured, is a ring node adjacent to the
RPL that is responsible for blocking its end of the RPL under normal
conditions (i.e., the ring is established and no requests are present in
the ring) in addition to the block at the other end by the RPL Owner
Node. The RPL neighbor node may participate in blocking or unblocking
its end of the RPL, but is not responsible for activating the reversion
behavior.
â—† Only one RPL owner can be configured on a ring. If the switch is set as
the RPL owner for an ERPS domain, the west ring port is set as one end
To Next Page
Loading...
Need help?
General
