Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

ingress (Chained Composite Next Hop)

Syntax

Hierarchy Level

Description

Allows you to configure chained composite next hops for devices handling ingress traffic in the network.

Note:
  • On MX Series routers containing both DPC and MPC FPCs, the chassis must be configured with enhanced-ip option for enabling chained composite next hops. Only the l3vpn option under the ingress statement is supported on DPC and DPCE-based MX Series routers. All other statements and functionality under the ingress statement are not supported on MX routers with DPC linecards.

  • The extended-space statement is not supported in ACX Series routers.

  • The [edit logical-systems] hierarchy level is not applicable in ACX Series routers.

Default

This statement is disabled by default.

Options

evpn | no-evpn

Enable or disable composite chained next hop for ingress EVPN label-switched paths (LSPs).

fec129-vpws | no-fec129-vpws

Enable or disable composite chained next hop for ingress FEC 129 virtual private wire service (VPWS) LSPs.

l2ckt | no-l2ckt

Enable or disable composite chained next hop for ingress Layer 2 circuit LSPs.

l2vpn | no-l2vpn

Enable or disable composite chained next hop for ingress Layer 2 virtual private network (VPN) LSPs.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

This statement was introduced in Junos OS Release 12.1.

labeled-bgp option was introduced in Junos OS Release 12.3.

l2ckt, l2vpn, no-l2ckt, and no-l2vpn options were introduced in Junos OS Release 13.3.

evpn, fec129-vpws, no-evpn, and no-fec129-vpws options were introduced in Junos OS Release 14.1.