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
  90% (28)
• B
  6% (2)
• D
  3% (1)

Explanation

SD-Access Wireless Architecture: Control Plane Node Role

In Cisco SD-Access, the fabric control plane node acts as the central directory (using LISP Map-Server/Map-Resolver) that tracks and manages all endpoint ID-to-location (RLOC/edge node) bindings, making it the authoritative source for knowing where any endpoint resides in the fabric. The fabric wireless controller (WLC) manages wireless-specific functions like AP registration and client association, but it delegates endpoint registration to the control plane node rather than maintaining the binding database itself. The fabric border node connects the SD-Access fabric to external networks (like the internet or data center) and handles policy translation, but is not responsible for tracking internal endpoint locations. The fabric edge node is the access-layer device where endpoints physically connect and registers bindings with the control plane node, but it does not manage the overall binding database.

Memory Tip: Think of the control plane node as the fabric's "phone book" - edge nodes submit entries, but the control plane node owns and manages the entire directory of who is located where.

No community discussion yet for this question.