How are wireless endpoints registered in the HTDB in a Cisco SD-Access architecture?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.htmlIn a Cisco Software-Defined Access (SD-Access) architecture, the Host Tracking Database (HTDB) is used to keep track of endpoints and their locations within the network. This information is used to provide network services such as policy enforcement, network access control, and mobility services.
Wireless endpoints can be registered in the HTDB through several methods. The correct answer to the question is option C - Fabric APs update the HTDB with the clients' EID and RLO.
When a wireless endpoint connects to the network through a Fabric Access Point (AP), the AP sends an Extensible Authentication Protocol over LAN (EAPOL) message to the Fabric Wireless LAN Controller (WLC). The Fabric WLC then sends a message to the Fabric Border Node (BN) with the endpoint's identity (EID) and location information (RLO).
The Fabric BN then updates the HTDB with the new endpoint information. The RLO includes the Fabric Edge Node (EN) where the endpoint is connected and the access switch port information. The Fabric ENs then use this information to enforce policies and provide network services to the endpoint.
Option A is incorrect because border nodes do not register endpoints directly. They receive endpoint information from Fabric WLCs or Fabric APs.
Option B is incorrect because Fabric WLCs do not register endpoints directly in the HTDB. They forward the endpoint information to the Fabric BNs.
Option D is incorrect because Fabric ENs do not receive CAPPWAP messages from APs. CAPPWAP is a protocol used by Fabric APs to communicate with Fabric WLCs.