Configuring a VPLS Service with CLI
Page 324 7210 SAS M Services Guide
SAP Auto Edge
The SAP edge-port command is used to instruct STP to dynamically decide whether the SAP is
connected to another bridge.
If auto-edge is enabled, and STP concludes there is no bridge behind the SAP, the OPER_EDGE
variable will dynamically be set to true. If auto-edge is enabled, and a BPDU is received, the
OPER_EDGE variable will dynamically be set to true (see SAP Edge Port on page 323).
Valid values for SAP auto-edge are enabled and disabled with enabled being the default.
CLI Syntax: config>service>vpls>sap>stp#
[no] auto-edge
Default: auto-edge
SAP Link Type
The SAP link-type parameter instructs STP on the maximum number of bridges behind this SAP.
If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast
transitions). If more than two bridges are connected by a shared media, their SAPs should all be
configured as shared, and timer-based transitions are used.
Valid values for SAP link-type are shared and pt-pt with pt-pt being the default.
CLI Syntax: config>service>vpls>sap>stp#
link-type {pt-pt|shared}
Default: link-type pt-pt
Restore Default: no link-type
MST Instances
The SAP mst-instance command is used to create MST instances at the SAP level. MST instance
at a SAP level can be created only if MST instances are defined at the service level.
The parameters that can be defined per instance are mst-path-cost and mst-port-priority.
• mst-path-cost — Specifies path-cost within a given MST instance. The
path-cost is proportional to link speed.
• mst-port-priority — Specifies the port priority within a given MST
instance.
To Next Page
Loading...
Need help?
General
