ip-prefix-support

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 15.1x53-D30.

Description

In an Ethernet VPN (EVPN) Virtual Extensible LAN (VXLAN) environment, enable the provider edge (PE) switch to forward the IP prefix associated with a specified customer domain in scenarios where the Layer 2 domain does not extend across data centers. Such routes are referred to as EVPN pure type-5 routes. On QFX switches, only fully resolved next-hop routes are supported. The data packets are sent as Layer 2 frames that are encapsulated in the VXLAN header. A unique VXLAN numerical identifier is associated with each customer domain.

When the advertisement of the type-5 route is enabled, you can optionally use an export routing policy configured at the [edit policy-options policy-statement policy-name] hierarchy level to further control the IP prefixes to advertise or suppress through EVPN type-5 routes for each customer. The policy is applied to the routes that reside in the customer’s inet.0 routing table by specifying a routing-instance-name configured at the [edit routing-instances] hierarchy level. This routing-instance-name refers to a Layer 3 virtual routing and forwarding (VRF) domain for a specific customer. The corresponding name of the table is instance.name.inet.0 This table is created by default when you configure a routing instance.

Caution

This statement is deprecated starting with Junos OS Release 15.1x53-D60 and has been replaced with ip-prefix-routes. The statement ip-prefix-support forwarding-mode symmetric is now ip-prefix-routes advertise direct-nexthop. Any configuration with the original ip-prefix-support statement is automatically upgraded to the new ip-prefix-routes statement when you upgrade to Junos OS Release 15.1x53-D60 or later.

Options

The forwarding-mode symmetric, encapsulation vxlan and vni number options are required. The export policy-name option is optional.

encapsulation vxlan—Specify to encapsulate forwarded traffic in VXLAN for transmission to the other data center.

export routing-policy-name—(Optional) Specify the name of the routing policy configured at the [edit policy-options policy-statement policy-name] hierarchy level to apply to the routes for the specified customer domain. Applying an export policy allows you to further control the IP prefixes to advertise or to suppress for each customer. You can apply a separate export routing policy to one or more customer domains. This allows each customer to each have its own policy.

forwarding-mode symmetric—Enable the receiver to resolve the next-hop route using only information carried in the type-5 route.

vni number—Specify the identifier associated with a customer domain. Each customer domain must have a unique identifier.

Required Privilege Level

routing—To view this statement in the configuration.

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