In a Cisco, Huawei, or Juniper environment that is using LDP signaling to establish L2VPNs, MPLS Manager matches various attributes (LocalAddress, PeerAddress) that are associated with the LdpProtocolEndpoints that are discovered on different PE devices, and creates an LdpAdjacency instance for each complementary match. MPLS Manager sets each instance’s isTargeted attribute to True, to indicates that the LDP session is targeted.

An LdpAdjacency is ConnectedTo two LdpProtocolEndpoints, where one LdpProtocolEndpoint is HostedBy one PE device, and the second is HostedBy another PE device. The LdpAdjacency provides a bidirectional signaling path through which the two PE devices exchange VC ID and other types of information for the purpose of constructing, advertising, maintaining, or deleting PseudoWires between the two PE devices.

GUID-572E0B81-8DDC-43CC-B1DE-C91F07F7402C.html#GUID-572E0B81-8DDC-43CC-B1DE-C91F07F7402C___MPLS_USER_ELEMENTS_50631 lists some key attributes for LdpAdjacency.

“Root-cause problems for LdpAdjacency” on page 50 describes the root-cause problem that is diagnosed for LdpAdjacency.