Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?





Hierarchy Level

Release Information

Statement introduced in Junos OS Release 15.1X53-D60 and Junos OS Release 17.2R1.

Support for logical systems on MX Series routers added in Junos OS Release 17.4R1.


In an Ethernet VPN (EVPN) environment, enable the device to advertise the IP prefix associated with a specified customer domain as a type-5 route to remote data centers or in a metro transport network. You use this feature when the Layer 2 domain does not exist at the remote data centers or metro network peering points.

Two models for implementing type-5 routes are supported:

  • Pure type-5 route without overlay next hop and type-2 route

  • Type-5 route with gateway IRB interface as overlay next hop and type-2 route

A pure type-5 route advertises the summary IP prefix and includes a BGP extended community called a router MAC, which is used to carry the MAC address of the sending switch and to provide next-hop reachability information for the prefix. In contrast, a standard type-5 route requires a gateway IP address as a next-hop overlay and a supporting type-2 route to provide recursive route resolution.

On QFX5110 and QFX10000 switches, only fully resolved next-hop—that is, EVPN pure type-5—routes are currently supported. QFX10000 switches support only EVPN Virtual Extensible LAN (VXLAN). MPLS encapsulation is not supported.

On QFX5110 switches, you must also configure the overlay-ecmp statement at the [edit forwarding-options vxlan-routing] hierarchy level with pure type-5 routes in an overlay EVPN-VXLAN network. We strongly recommend also configuring the overlay-ecmp statement whenever you enable pure type-5 routes on a QFX5110 switch. Configuring this statement causes the Packet Forwarding Engine to restart. Restarting the Packet Forwarding Engine interrupts all forwarding operations. Therefore, we strongly recommend configuring the overlay-emcp statement before the EVPN-VXLAN network becomes operational.

On EX9200 switches, both type-5 routes are supported. Only MPLS encapsulation is supported with pure type-5 routes. Both MPLS and VXLAN encapsulation are supported with the standard type-5 route with a gateway IP address as next-hop overlay.


Pure type-5 routing for EVPN-VXLAN was introduced in Junos OS Release 15.1X53-D30 for QFX10002 switches only. In that release, this statement is ip-prefix-support forwarding-mode symmetric.

Starting with Junos OS Release 15.1X53-D60, the statement is 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.


Pure type-5 routing is supported on all QFX10000 switches starting in Junos OS Release 15.1X53-D60.

By default, all Juniper Networks devices that support pure type-5 routes do not advertise IP prefixes with a mask length of /32 as pure type-5 routes. To advertise /32 prefixes, you must set up a term in an export policy that explicitly accepts these prefixes into the routing table. The following are excerpts from a sample configuration:


The advertise, encapsulation and vni number options are required. The export routing–policy-name option is optional.

advertise direct-nexthopEnable the switch to send IP prefix information using an EVPN pure type-5 route, which includes a router MAC extended community used to send the MAC address of the switch. This router MAC extended community provides next-hop reachability without requiring an overlay next-hop or supporting type-2 route.

For pure route type-5, QFX5110 and QFX10000 switches support only VXLAN encapsulation, and EX9200 switches support only MPLS encapsulation.

advertise gateway-address (EX9200 switches only)Enable the switch to advertise a gateway address in exported IP prefix routes. This gateway address provides overlay next-hop reachability.

You must also specify a gateway address by including the gateway-interface interface-name statement.

encapsulation (vxlan | mpls)Specify to encapsulate forwarded traffic in VXLAN or MPLS for transmission to the remote data center.

The same type of encapsulation must be used end to end. Only VXLAN encapsulation is supported on QFX10000 and QFX5110 switches.

donot-advertise-communityStarting with Junos release 19.4R1, for when a type-5 routes is created from the type-2 MAC and IP advertisement that was learned from a remote PE device, the default behavior is to include the community information from the type-2 route (if any) in the type-5 route. You can prevent behavior this by enabling the donot-advertise-community option.
export routing-policy-name(Optional) Specify the name of the routing policy configured at the [edit policy-options policy-statement policy-statement-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 through EVPN type-5 routes 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.
gateway-interface interface-nameSpecify the gateway interface to use as a next-hop overlay for a standard type-5 route. You must use this option in conjunction with the advertise gateway-address option.
vni numberSpecify 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.