Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Routing Zone (VRF) Constraints

Routing zone constraints allow you to constrain server-facing interfaces that connect to specific routing zones. Day-2 operators would be prevented from connecting a server to the wrong network, and assure that a given server never gets added to the wrong network. The constraint can be defined in various ways such as a list of allowed VRFs, a list of excluded VRFs, a maximum number of VRFs allowed, and so on. Once the constraint is defined, you can enforce the constraint on server-facing interfaces using connectivity templates of the type Routing Zone Constraint.

Create Routing Zone Groups (Optional)

If you want to constrain more than one routing zone to a single port, you can group them, then specify the group as a constraint when you create the routing zone constraint policy.

  1. From the blueprint, navigate to Staged > Virtual > Routing Zone Groups and click Create Routing Zone Group.
  2. Enter a group name and (optional) tags.
  3. In the Routing Zone drop-down list, select a routing zone to add to the group and click Add. The routing zone is added to the Members list.
  4. Repeat the previous step until you’ve added all the routing zones that you want in the group.
  5. Click Create to create the group and return to the table view.

Create Routing Zone Constraint Policy

You can create a routing zone constraint policy, then later when you create a connectivity template you can apply the policy to an application point. Some examples of how you could constrain VRFs include:
  • One VRF maximum
  • Any VRF except Management
  • Only VRFs Blue and Red
  • Only VRF Group Orange
  1. From the blueprint, navigate to Staged > Policies > Routing Zone Constraints and click Create Routing Zone Constraints.
  2. Enter a name and (optional) maximum number of routing zones that the application point can be part of.
  3. Set the (optional) Routing Zones List Constraint.
    1. Allow - only allow the specified routing zones (add specific routing zones to allow)
    2. Deny - denies allocation of specified routing zones (add specific routing zones to deny)
    3. None - no additional constraints on routing zones (any routing zones)
  4. Click Create to create the policy and return to the table view.

Edit / Delete Routing Zone Constraint Policy

If you need to, you can change or delete the policy after you've created it.

  • If you edit the policy to increase the number of routing zones, you don't need to unassign participating ports from the restriction.
  • If you edit the policy to reduce the number of routing zones, ensure that all participating ports are in compliance with the new restrictions before you save. Otherwise, you will receive an error.
  • You can delete a constraint policy to free up any restrictions on the participating ports. These ports should behave as if the constraint was never applied.

Apply Routing Zone Constraint

When you want to apply the constraint to an application point, add the Routing Zone Constraint primitive to the connectivity template and specify the routing zone or routing zone group. For more information about connectivity templates, see Connectivity Templates.