In a Cisco or Juniper M/T environment that is using RSVP-TE signaling to establish LSPs, MPLS Manager discovers the PE and P devices and the RSVP-TE speakers that are associated with the LSPs. The complete MPLS forwarding path for a TE LSP or subLSP is determined by IP forwarding and the explicit constraints that are applied to the LSP.
The RsvpProtocolEndpoint relationship Peer points from an RsvpProtocolEndpoint to the RsvpProtocolEndpoint at the other end of the RSVP session. Because an RSVP session is TCP- or UDP-based, a peer RsvpProtocolEndpoint can terminate on a PE or P device that is multiple Layer 3 hops away.
MPLS Manager creates an RsvpProtocolEndpoint instance for each discovered RSVP-TE speaker that is associated with a TE LSP or subLSP.