Interconnect Policy Provisioning (Ipp); Opflex Peering And Multi-Pod - Cisco Nexus 7000 Series Configuration Manual

Interconnect Policy Provisioning (IPP)

create a standard that enables policies to be applied across physical and virtual switches/routers in a multi-user
environment.
For more details on OpFlex refer to
To enable automation of fabric facing tenant configuration on the DCI, DCI interfaces with the fabric as an
external Policy Element (PE) that talks to ACI fabric spine acting as a proxy-Policy Repository (PR) for DCI
specific policy information. An OpFlex policy framework is used between the spines and the DCIs to distribute
this DCI policy model from the fabric to the DCI gateways. DCI uses this policy information pushed from
the spine to auto generate fabric facing per-tenant configuration.
ACI spine in turn derives this DCI object model from the concrete object model (object store) populated on
the Spine through the ACI DME infrastructure. APIC controller (via DME infra) pushes a logical model that
results in a resolved concrete model on the Spine Policy Element. Spine gleans specific attributes required to
instantiate the ACI WAN Interconnect DCI service for individual tenants from this resolved concrete model
and populates a per-DCI object-model that is distributed to individual DCIs via the OpFlex framework. Spine
essentially acts a proxy on behalf of the fabric to push per-tenant DCI policies to the DCI that acts as an
external policy element to the fabric.
Note that this PR – PE contract between the fabric and the DCI is limited to fabric facing per-tenant provisioning
and not a contract for management functions in general. All remaining configuration, including WAN facing
configuration, as well as all other management, operational aspects on the DCI will continue to work
independent of this PR – PE contract with the fabric, via existing mechanisms.
Interconnect Policy Provisioning (IPP)
Interconnect Policy Provisioning (IPP) enables automation of fabric facing per-tenant provisioning on the
DCI gateway.
The IPP utilizes OpFlex to push policies from ACI fabric to the DCI gateway. Using these policy attributes,
HMM auto-config is triggered to apply the profile along with the attributes to provision the required
fabric-facing configurations.

OpFlex Peering and Multi-POD

In a multi-POD topology, where the same DCI pair peers with multiple PODs, each POD would be configured
as a separate fabric ID and would result in a separate OpFlex framework to be instantiated with the respective
spine peers in that fabric that would result in OpFlex sessions to the spine peers within each POD.
Each OpFlex framework translates to a separate managed object database that is populated as a result of policy
information distributed from respective spines.
In a scenario where the same L3 domain is spread across the two PODs, DCI can receive updates for the same
VRF from multiple OpFlex frameworks, possibly with different RTs. DCI handles this multiple update scenario
by appending the route targets for the POD if the fabric facing local VRF configuration has already been
instantiated.
Cisco Nexus 7000 Series NX-OS VXLAN Configuration Guide
70
OpFlex: An Open Policy Protocol White
Configuring ACI WAN Interconnect
Paper.