Virtual Leased Line Services
7210 SAS M Services Guide Page 157
T-LDP Status Notification Handling Rules
Referring to Figure 28 on page 155 as a reference, the following are the rules for generating,
processing, and merging T-LDP status notifications in VLL service with endpoints. Note that any
allowed combination of objects as specified in Redundant VLL Service Model on page 155 can be
used on endpoints “X” and “Y”. The following sections refer to the specific combination objects
in Figure 28 as an example to describe the more general rules.
Processing Endpoint SAP Active/Standby Status Bits
The advertised admin forwarding status of active/standby reflects the status of the local LAG SAP
in MC-LAG application. If the SAP is not part of a MC-LAG instance, the forwarding status of
active is always advertised.
When the SAP in endpoint “X” is part of a MC-LAG instance, a node must send T-LDP
forwarding status bit of “SAP active/standby” over all “Y” endpoint spoke SDPs, except the ICB
spoke SDP, whenever this status changes. The status bit sent over the ICB is always zero (active
by default).
When the SAP in endpoint “X” is not part of a MC-LAG instance, then the forwarding status sent
over all “Y” endpoint spoke SDP's should always be set to zero (active by default).
To Next Page
Loading...
