Multi-Pod Provisioning
The IPN is not managed by the APIC. It must be preconfigured with the following information:
-
Configure the interfaces connected to the spines of all pods. Use Layer 3 sub-interfaces tagging traffic with VLAN-4 and increase the MTU at least 50 bytes above the maximum MTU required for inter-site control plane and data plane traffic.
If remote leaf switches are included in any pods, see Remote Leaf Switches and the Cisco ACI Remote Leaf Architecture White Paper.
-
If the IPN underlay protocol will be OSPF, enable OSPF on sub-interfaces with the correct area ID. Beginning with Cisco APIC Release 5.2(3), the IPN underlay protocol can be either OSPF or BGP (eBGP only).
-
Enable DHCP Relay on IPN interfaces connected to all spines.
-
Enable PIM.
-
Add bridge domain GIPO range as PIM Bidirectional (bidir) group range (default is 225.0.0.0/15).
A group in bidir mode has only shared tree forwarding capabilities.
-
Add 239.255.255.240/28 as PIM bidir group range.
-
Enable PIM and IGMP on the interfaces connected to all spines.
Note |
When deploying PIM bidir, at any given time it is only possible to have a single active RP (Rendezvous Point) for a given multicast group range. RP redundancy is hence achieved by leveraging a Phantom RP configuration. Because multicast source information is no longer available in Bidir, the Anycast or MSDP mechanism used to provide redundancy in sparse-mode is not an option for bidir. |