A municipal library consortium wants LISP map-server/map-resolver services to survive a single control-plane node failure. What redundancy approach aligns with SD-Access fabric design?
Select an answer to reveal the explanation.
Short Explanation
The control-plane node is the fabric’s phone book for who lives where. If you only keep one copy and that box dies, lookups go dark. Dual CP nodes keep map-server/map-resolver service up so one failure does not strand the consortium’s EIDs.
Full Explanation
SD-Access control-plane nodes provide LISP map-server and map-resolver functions for endpoint identifier to routing locator mappings. Designing two (or more, per validated scale) CP nodes provides redundancy so a single failure does not eliminate mapping services. Wireless controllers, multicast RP mechanisms, and the underlay IGP are not substitutes for fabric LISP mapping redundancy.