What are Routing Policies

Release: Juniper Apstra 5.1

date_range 21-Mar-25

arrow_backward

arrow_forward

Routing policies enable you to control (filter) which routes a routing protocol imports into the routing table and which routes a routing protocol exports from the routing table. Routing policies in Apstra include the following details:

Parameter	Description
Name	18 characters or fewer. Alphanumeric, _ and - only.
Import Policy	Specify the Import policies to import, either default route only, all routes, or extra routes only. Default - The default BGP route (0.0.0.0/0, ::/0) is permitted. If you select default here and add extra routes under Extra Import Routes below, both the default and the extra routes apply. All - Any BGP route is permitted. Extra Only - Only user-defined extra import routes (see below) are permitted or denied.
Extra Import Routes (user-defined)	User-defined import routes. If you want the default route to be included, make sure you've selected Default for Import Policy (above). If you want only the extra import routes to apply, make sure you've selected Extra Only for Import Policy. Prefix - IPv4 or IPv6 network address (format: network/prefixlen) or IP address (interpreted as /32 network address). GE Mask and LE Mask - GE Mask matches less-specific prefixes from a parent prefix, up from the GE mask to the prefix length of the route. (IPv4 range: 0-32. IPv6 range: 0-128). If you don't specify GE mask, then make sure that the prefix-list entry is an exact match. You can use this option in combination with LE Mask. GE mask must be longer than the subnet prefix length. If both the LE mask and GE mask are specified, then the LE mask must be greater than the GE mask. Action - Permit or Deny
Export Policy	Spine Leaf Links - Exports all spine-leaf (fabric) links within a VRF. EVPN routing zones don't have spine-leaf addressing, so this generated list may be empty. For routing zones of type Virtual L3 Fabric, subinterfaces between spine-leaf are included. Spine Superspine Links - Exports all spine-superspine (fabric) links within the default routing zone (VRF). L2 Edge Subnets - Exports all virtual networks (VLANs) that have L3 addresses within a routing zone (VRF). Loopbacks - Exports all loopbacks within a routing zone (VRF) across spine, leaf, and L3 servers. Static Routes - Exports all subnets in a VRF associated with static routes from all fabric systems to generic systems associated with this routing policy.
Extra Export Routes (user-defined)	User-defined export routes. If you want other export routes to be included, make sure you've selected them under Export Policy (above). If you want only the extra export routes to apply, make sure none of the export policies are selected under Export Policy. Note: To enable default route for EVPN host routes, go to Staged > Fabric Settings > Fabric Policy. Then, in the Route Options section, enable the Generate EVPN host routes from ARP/IPv6 ND ARP option. Prefix - IPv4 or IPv6 network address (format: network/prefixlen) or IP address (interpreted as /32 network address). GE Mask and LE Mask - GE Mask matches less-specific prefixes from a parent prefix, up from the GE mask to the prefix length of the route. (IPv4 range: 0-32. IPv6 range: 0-128). If you don't specify GE mask, then the prefix-list entry should be an exact match. You can use this option in combination with LE Mask. GE mask must be longer than the subnet prefix length. If both the LE mask and GE mask are specified, then the LE mask must be greater than the GE mask. Action - Permit or Deny
Aggregate Prefixes	If you have routing zones associated with your routing policy, and aggregate prefixes are supported on the platform (see the feature matrix) you can specify aggregate prefixes. These are the BGP aggregate routes to be imported into the routing zone (VRF) on all border switches. The aggregated routes are sent to all generic system peers in a routing zone (VRF). CAUTION: Routing policies with aggregate prefixes are applied to the entire routing zone. You cannot configure them individually for BGP sessions (per connectivity point). If you do attempt to apply them via a connectivity template (CT), you could receive the error “Protocol endpoint routing policy aggregate prefixes should be empty”.
Expect Default IPv4 Route	To add the expectation that the default route is used in the default routing zone, select this check box when you create the policy. (This field applies to the default route in the default routing zone only.) Checking this box does not change any configuration; it generates the expectation and raises an anomaly when the default route is not present.
Expect Default IPv6 Route	To add the expectation that the default route is used in the default routing zone, select this check box when you create the policy. (This field applies to the default route in the default routing zone only.) Checking this box does not change any configuration; it generates the expectation and raises an anomaly when the default route is not present.
Associated Routing Zones	Lists any routing zones that are associated with the routing policy.
Associated Protocol Endpoints	Lists any protocol endpoints that are associated with the routing policy.

From the blueprint, navigate to Staged > Policies > Routing Policies to go to routing policies in the blueprint.

The default routing policy (not shown in table) is associated with the default routing zone. To see details of a routing policy, click its name.

You can't change the default routing policy, but you can create, clone, edit, and delete other routing policies as described in subsequent pages.

arrow_backward PREVIOUS Interface Policies

NEXT arrow_forward Create Routing Policy

Juniper Apstra 5.1.0 User Guide

What are Routing Policies

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry