Static Route on a Bridge Domain

This chapter contains the following sections:

About Static Routes in Bridge Domains

A static route in a pervasive bridge domain is a configuration that enables endpoint reachability to IP addresses that are not directly connected to the bridge domain.

  • Enables connectivity to virtual services behind firewalls.

  • Deploys to leaf switches using the bridge domain and those with associated contracts.

  • Supports configuration via GUI, NX-OS Style CLI, and REST API.

Guidelines and Limitations for Static Routes

  • The subnet mask must be /32 (/128 for IPv6) pointing to one IP address out of the fabric.

  • Do not add routes within bridge domain subnets that are already defined.

  • The next hop must be inside the same bridge domain that this EPG is associated with.

  • The feature is supported on Cisco Nexus 9000 series switches with names that end in EX, and later.

  • The endpoint reachability feature is not supported for remote leafs.

Configuring a Static Route on a Bridge Domain Using the GUI

  • When creating the subnet for the static route, it is configured under the EPG (fvSubnet object under fvAEPg), associated with the pervasive BD (fvBD), not the BD itself.

  • The subnet mask must be /32 (/128 for IPv6) pointing to one IP address or one endpoint. It is contained in the EPG associated with the pervasive BD.

Before you begin

Create the tenant, VRF, BD, and EPG.

Procedure

Step 1

On the menu bar, click Tenants > tenant-name .

Step 2

In the Navigation pane, expand Application Profiles and click the application profile name.

Step 3

Click Application EPGs and expand the EPG for the static route.

Step 4

Expand Subnets , right-click the subnet for the static route, and choose Create Endpoints Behind EPG Subnet .

Step 5

Enter the NextHop IP Address for the endpoint and click Update .

Step 6

Click Submit .