Page 466 7750 SR OS Services Guide
However, when the command is run at the same time as both MC-EP PEs, when the endpoints
belong to the same mc-endpoint, the regular MC-EP selection algorithm (for example, the
operational status -> precedence value) will be applied to determine the winner.
Revertive Behavior for Primary Pseudowire(s) in a MC-EP
For a single-chassis endpoint a revert-time command is provided under the VPLS endpoint. Refer
to the VPLS Services Command Reference on page 591 for syntax and command useage
information.
In a regular endpoint the revert-time setting affects just the pseudowire defined as primary
(precedence 0). For a failure of the primary pseudowire followed by restoration the revert-timer is
started. After it expires the primary pseudowire takes the active role in the endpoint. This behavior
does not apply for the case when both pseudowires are defined as secondary: i.e. if the active
secondary pseudowire fails and is restored it will stay in standby until a configuration change or a
force command occurs.
In the MC-EP case the revertive behavior is supported for pseudowire defined as primary
(precedence 0). The following rules apply:
• The revert-time setting under each individual endpoint control the behavior of the local
primary pseudowire if one is configured under the local endpoint.
• The secondary pseudowires behave as in the regular endpoint case
Using B-VPLS for Increased Scalability and Reduced Convergence Times
The PBB-VPLS solution can be used to improve scalability of the solution and to reduce
convergence time. If PBB-VPLS is deployed starting at the edge PEs, the gateway PEs will
contain only BVPLS instances. The MC-EP procedures described for regular VPLS apply.
PBB-VPLS can be also enabled just on the gateway MC-EP PEs as depicted in Figure 69 below.
To Next Page
Loading...
