LdpAdjacency (non-targeted)

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

An LdpAdjacency is ConnectedTo two LdpProtocolEndpoints, where one LdpProtocolEndpoint is HostedBy one PE or P device, and the second is HostedBy a peering PE or P device. The LdpAdjacency provides a bidirectional signaling path through which the two directly connected peering devices exchange MPLS label information for the purpose of constructing, maintaining, or deleting LDP LSPs.