Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Routing Policies

Routing Policy Overview

Routing policies include the following details:

Parameter Description
Name

18 characters or fewer. Alphanumeric, _ and - only.
Import Policy
  • Default - The default BGP route (0.0.0.0/0, ::/0) is permitted. If extra import routes are defined, they are also permitted.
  • All - Any BGP route is permitted.
  • Extra Only - Only user-defined extra import routes are permitted (or denied).
Extra Import Routes (user-defined)
  • 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
Export Policy
  • Spine Leaf Links - Exports all spine-leaf (fabric) links within a VRF. EVPN routing zones do not 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.
  • L3 Edge Server Links - Exports all leaf to L3 server links within a routing zone (VRF). On layer 2 blueprints this is an empty list.
  • 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. These policies are additive. To advertise extra routes only, unselect all export policies.

Note:

To enable default route for EVPN host routes, go to Staged > Settings > Virtual Network Policy and enable the Generate EVPN host routes 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, check the 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, check the 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. A default routing policy is associated with the default routing zone. You cannot change the default routing policy, but you can create, clone, edit, and delete other routing policies as described below.

Create Routing Policy

  1. From the blueprint, navigate to Staged > Policies > Routing Policies and click Create Routing Policy.
  2. Configure the policy. For parameter details, see the Routing Policy Overview.
  3. Click Create to stage the policy addition and return to the table view.

Edit Routing Policy

  1. From the blueprint, navigate to Staged > Policies > Routing Policies and click the Edit button for the policy to edit.
  2. Make your changes.
  3. Click Update (bottom-right) to stage the policy change and return to the table view.

Delete Routing Policy

  1. From the blueprint, navigate to Staged > Policies > Routing Policies and click the Delete button for the policy to delete.
  2. Click Delete to stage the policy removal and return to the table view.