MC endpoint groups and MC peer groups

MC endpoint groups and MC endpoint peer groups

An MC endpoint group consists of two MC endpoint peers that are configured as peers in a pair of sites. Multiple VPLS endpoints can use the MC endpoint peer. The endpoints must be on a supporting NE, and must support PW redundancy. Each endpoint can be associated with different destinations, with a maximum of two spoke SDPs for each endpoint. The endpoints communicate with each other to get the associated status of the spoke SDPs, which ensures that only one spoke SDP is active at any time; the other spoke SDPs have a standby status. The grouping of multiple spoke SDPs that are associated with the two MC endpoint peers eliminates traffic loops in a VPLS or B-VPLS.

An MC endpoint group includes:

• two MC endpoint peers that can be used by a spoke SDP

• an MC protocol that is used for:

  • determination of which MC endpoint peers are active or standby

  • synchronization of the PW information between the peers

  • fault detection using centralized BFD; the MC endpoint protocol includes a keep-alive mechanism because BFD cannot detect the state of an MC endpoint peer

• T-LDP signaling, which is used to communicate whether a PW is active or standby to other gateway pairs. The other gateway pairs may not have an MC endpoint.

An MC peer group that is managed by the NFM-P contains two MC peers. Each MC peer is configured as the peer of the other MC peer. An MC peer group must be created before you create an MC endpoint group. When only one peer in an MC peer group is managed by the NFM-P, you can configure node redundancy parameters only for the managed peer and only from the NE properties form. See Chapter 40, MC peer groups for information about MC peer groups.

BFD

The MC endpoint protocol uses keep-alive mechanisms. The MC endpoint protocol also supports BFD to eliminate traffic loops. See To configure an MC endpoint group for information about how to configure an MC endpoint group for BFD.