Common Pervasive Gateway
This chapter contains the following sections:
This example shows how to configure Common Pervasive Gateway for IPv4 when using the Cisco APIC.
Two ACI fabrics can be
configured with an IPv4 common gateway on a per bridge domain basis. Doing so
enables moving one or more virtual machine (VM) or conventional hosts across
the fabrics while the host retains its IP address. VM host moves across fabrics
can be done automatically by the VM hypervisor. The ACI fabrics can be
co-located, or provisioned across multiple sites. The Layer 2 connection
between the ACI fabrics can be a local link, or can be across a bridged
network. The following figure illustrates the basic common pervasive gateway
Depending upon the topology used to interconnect two Cisco ACI fabrics, it is required that the interconnecting devices filter out the traffic source with the Virtual MAC address of the gateway switch virtual interface (SVI).
Pervasive Gateway Using the GUI
Before You Begin
The tenant and VRF are created.
domain virtual MAC address and the subnet virtual IP address must be the same
across all ACI fabrics for that bridge domain. Multiple bridge domains can be
configured to communicate across connected ACI fabrics. The virtual MAC address
and the virtual IP address can be shared across bridge domains.
domain that is configured to communicate across ACI fabrics must be in
Only one EPG
from a bridge domain (If the BD has multiple EPGs) should be configured on a
border Leaf on the port which is connected to the second Fabric.
Do not connect
hosts directly to an inter-connected Layer 2 network that enables a pervasive
common gateway among the two ACI fabrics.
|| On the menu
Navigation pane, expand the
Domains, and click
|| In the Create Bridge Domain dialog box, perform the required actions to choose the appropriate attributes: |
- In the Main tab, in the Name field, enter a name for the bridge domain, and choose the desired values for the remaining fields.
- In the L3 configurations tab, expand Subnets, and in the Create Subnets dialog box, in the Gateway IP field, enter the IP address.
- In the Treat as virtual IP address field, check the check box. Click Ok, and click Finish.
- In the Make this IP address primary field, check the check box to specify this IP address for DHCP relay.
Checking this check box affects DHCP relay only.
- Click Ok, and click Finish.
- Expand Subnets again, and in the Create Subnets dialog box, to create the Physical IP address in the Gateway IP field, use the same subnet which is configured as the Virtual IP address.
The Physical IP address must be unique across the ACI fabric.
||Complete the appropriate steps and click Finish to complete.|
||Double click the Bridge Domain that you just created in the Work pane, and perform the following action: |
- In the L3 Configurations tab, click the Virtual MAC Address field, and change not-applicable to the appropriate value. Click Submit.
The default BD MAC address values are the same for all ACI fabrics; this configuration requires the bridge domain MAC values to be unique for each ACI fabric.
Confirm that the bridge domain MAC (pmac) values for each fabric are unique.
||To create an L2Out EPG to extend the BD to another fabric, in the Navigation pane, right-click External Bridged Networks and open the Create Bridged Outside dialog box, and perform the following actions: |
- In the Name field, enter a name for the bridged outside.
- In the Bridge Domain field, select the bridge domain already previously created.
- In the Encap field, enter the VLAN encapsulation to match the other fabric l2out encapsulation.
- In the Path Type field, select Port, PC, or VPC to deploy the EPG and click Next.
- To create an External EPG network click in the Name field, enter a name for the network and you can specify the QoS class and click Finish to complete Common Pervasive configuration.
Pervasive Gateway Using the NX-OS Style CLI
Common Pervasive Gateway.
apic1(config-tenant)#interface bridge-domain test
apic1(config-tenant-interface)#mac-address 00:CC:CC:CC:C1:01 (Should be unique for each ACI fabric)
apic1(config-tenant-interface)#ip address 192.168.10.1/24 multi-site
apic1(config-tenant-interface)#ip address 192.168.10.254/24 (Should be unique for each ACI fabric)
Pervasive Gateway Using the REST API
<!-Things that are bolded only matters-->
<?xml version="1.0" encoding="UTF-8"?>
<!-- api/policymgr/mo/.xml -->
<fvBD name="test" vmac="12:34:56:78:9a:bc">
<!-- Primary address -->
<fvSubnet ip="192.168.15.254/24" preferred="yes"/>
<!-- Virtual address -->
<fvSubnet ip="192.168.15.1/24" virtual="yes"/>
<fvRsPathAtt tDn="topology/pod-1/paths-101/pathep-[eth1/3]" encap="vlan-1002"/>