Ingress and transit-chained CNHs for LDP, RSVP, L2VPN, L3VPN, and static protocols

You can configure chained composite next hops (CNHs) for devices carrying ingress or transit traffic in the network. We now support the following options:

• On the LDP ingress router, set routing-options forwarding-table chained-composite-next-hop ingress ldp
• For the LDP, RSVP, L2VPN, L3VPN, and static protocols on the transit router:
• set routing-options forwarding-table chained-composite-next-hop transit ldp
• set routing-options forwarding-table chained-composite-next-hop transit rsvp
• set routing-options forwarding-table chained-composite-next-hop transit static
• set routing-options forwarding-table chained-composite-next-hop transit l2vpn
• set routing-options forwarding-table chained-composite-next-hop transit l3vpn

We support class of service (CoS) and rewrite rules for ingress and transit-chained CNHs for these configuration commands.