Pseudowire Redundancy Service Models
This section describes the various MC-LAG and pseudowire redundancy scenarios as well as the
algorithm used to select the active transmit object in a VLL endpoint.
The redundant VLL service model is described in the following section,
Model. The selection rules for the active transmit endpoint object are detailed in Section
Endpoint Active Transmit Object Selection
Redundant VLL Service Model
In order to implement pseudowire redundancy, a VLL service accommodates more than a single
object on the SAP side and on the spoke SDP side.
VLL service based on the concept of endpoints.
A VLL service supports by default two implicit endpoints managed internally by the system. Each
endpoint can only have one object, a SAP or a spoke SDP.
In order to add more objects, up to two (2) explicitly named endpoints may be created per VLL
service. The endpoint name is locally significant to the VLL service. Let's refer to them as
endpoint 'X' and endpoint 'Y' as illustrated in
7750 SR OS Services Guide
VLL
SAP
ICB
spoke-sdp
Endpoint X
Figure 14: Redundant VLL Endpoint Objects
Virtual Leased Line Services
Rules.
Figure 27
illustrates the model for a redundant
Spoke-SDP
Spoke-SDP
Spoke-SDP
Spoke-SDP
Endpoint Y
Figure
27.
Redundant VLL Service
VLL
Page 137