aci multisite overlay control-plane COOP steps

14.01 2020 | by massimiliano

aci multisite overlay control-plane COOP steps Information about all the endpoints connected to the leaf nodes is stored in […]

Information about all the endpoints connected to the leaf nodes is stored in the COOP database available in the spine nodes

Every time an endpoint is discovered as locally connected to a given leaf node, the leaf node originates a COOP control-plane message to communicate the endpoint information (IPv4/IPv6 and MAC addresses) to the spine nodes.

COOP is also used by the spines to synchronize this information between them.

STEPS:

Endpoints EP1 and EP2 connect to separate Sites 1 and 2

A COOP notification is generated inside each fabric from the leaf nodes on which EP1 and EP2 are discovered and sent to the local spine nodes

The endpoint information is stored in the local COOP database.

Spine nodes in Site 1 know about locally connected endpoints, and the same is true for spine nodes in Site 2.

Note that at this point no information is exchanged across sites for EP1 and EP2 EPGs, because there is no policy in place yet indicating a need for those endpoints to communicate

An intersite policy is defined in the Cisco Multi-Site policy manager and is then pushed and rendered in the two sites

The creation of the intersite policy triggers Type-2 EVPN updates across sites to exchange EP1 and EP2 host route information

5a)

the endpoint information always is associated with the DP-ETEP address univocally identifying the site at which each specific endpoint was discovered

5b)

no additional EVPN updates are required when an endpoint moves around different leaf nodes that are part of the same fabric, until an endpoint is migrated to a different site

after endpoint information is exchanged across sites, the VXLAN data plane is used to allow intersite Layer 2 and Layer 3 communication (data-plane)