Tag :: RSVP

For MPLS forwarded traffic the tunnel destination needs to know the address-family of the payload IP/IPv6 packet to correctly parse the header. On some platforms this address-family is deduced from the address family of the Bottom of stack( BOS ) MPLS label seen by the router or by relying on the Ether Type in the Ethernet header.

LSPs formed by LDP normally follow IGP routing. The LDP speaker selects the downstream LSR for a particular prefix as

This feature adds a new CLI command which can be used to clear RSVP sessions. Clearing a session will remove the current

RSVP TE, the Resource Reservation Protocol (RSVP) for Traffic Engineering (TE), is used to distribute MPLS labels

RSVP-TE, the Resource Reservation Protocol (RSVP) for Traffic Engineering (TE), is used to distribute MPLS labels for steering traffic and reserving bandwidth. The Label Edge Router (LER) feature implements the headend functionality, i.e., RSVP-TE tunnels can originate at an LER which can steer traffic into the tunnel.

RSVP-TE applies the Resource Reservation Protocol (RSVP) for Traffic Engineering (TE), i.e., to distribute MPLS labels for steering traffic and reserving bandwidth.

RSVP-TE P2MP LER adds ingress and egress support for Point-to-Multipoint (P2MP) LSPs to be used in Multicast Virtual Private Network (MVPN) as an extension to the LSR support which adds transit support.

RSVP-TE P2MP LSR adds transit support for Point-to-Multipoint (P2MP) LSPs. Specifically the feature adds protocol support for the transit role as described in RFC 4875.

This feature adds RSVP information for three tables from MPLS TE STD MIB:. mplsTunnelTable.