Describes the configuration of static routes in pervasive bridge domains to enable endpoint reachability for IP addresses not directly connected to the fabric. This feature supports virtual services behind firewalls using regular EPGs.
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.