In a Cisco SD-Access wireless architecture, which device manages endpoint ID to Edge Node bindings?

Question

Options

• Afabric control plane node
• Bfabric wireless controller
• Cfabric border node
• Dfabric edge node.

• A
  96% (25)
• B
  4% (1)

Explanation

SD-Access Wireless Architecture: Control Plane Node

In Cisco SD-Access, the Fabric Control Plane Node (typically running LISP Map-Server/Map-Resolver) is responsible for maintaining the mapping database that tracks Endpoint ID (EID) to Routing Locator (RLOC) bindings, including which Edge Node an endpoint is currently associated with - this is its core function in the fabric.

The Fabric Wireless Controller (B) handles wireless-specific functions like AP management and client association, but it relies on the control plane node to register and resolve endpoint location mappings. The Fabric Border Node (C) connects the SD-Access fabric to external networks (like the internet or WAN) and handles policy translation, but does not manage endpoint-to-edge bindings. The Fabric Edge Node (D) is where endpoints connect to the fabric and registers bindings with the control plane node, but it does not manage the binding database itself.

Memory Tip: Think of the Control Plane Node as the "phone book" of SD-Access - every other device looks up where an endpoint lives by querying it. If you need to find someone, you consult the book; the book doesn't move people around.

No community discussion yet for this question.