Showing results for 
Search instead for 
Did you mean: 

Cisco SD-Access ATXs FAQ

Here are some commonly asked questions and answers to help with your adoption of Cisco Software-Defined Access (SD-Access). Subscribe (how-toto this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Q. Should I run SD-Access to use DNA Center?
A. No you need not run SD-Access to use DNA Center. You can add DNA Center to your traditional network and start using the Base Automation & Assurance feature. If you wish run SD-Access then DNA Center is mandatory but not vice versa.

Q. Will my SD-Access network be impacted if DNA Center goes down?
A. No. DNA Center is just a controller, even if the DNA Center goes down SD-Access network will still remain up and traffic will continue to flow. It just that you won’t be able to make any changes in to SD-Access network and you won’t be able to see the telemetry data.

Q. What are the steps needed to consider before starting LAN Automation for underlay?
A. Here are the steps:
  1. Before starting LAN automation, follow the steps in the Cisco DNA Center SD-Access LAN Automation Deployment Guide.
  2. If a LAN automated device is deleted from Cisco DNA Center, add it back via LAN automation. Do not add it back via the Inventory or Discovery pages.
  3. Do not modify the LAN automated interface configuration in the device manually, including Loopback0 or Loopback60000.  
  4. Do not move the LAN automated L3 interface configuration from one interface to another interface or from one device to another device manually.
  5. Do not use an IP address from the underlay pool for any other purpose in the network. Use a dedicated pool for the underlay
  6. Confirm that the PnP agent serial number does not already exist in the ISE NAD and in the PnP page. 
Q. Where should DHCP server reside in a SD-Access network?
A. The DHCP server must be outside of the SD-Access fabric, either multiple hops away (e.g. DC) or directly connected to the Fabric Border. In a Campus fabric network, DHCP server is deployed as a shared service located in a network that is different from the fabric endpoints. Every fabric edge is configured as a DHCP Relay agent to relay the DHCP traffic between fabric endpoints and DHCP server. DHCP server is located in the non-EID space in the enterprise fabric network and the fabric edge node uses the fabric border as Proxy Tunnel Router (PxTR) to communicate with the DHCP server.
Q. Should we use trunkports and Spanning Tree Protocols to propagate VLANs in the underlay of Cisco SD-Access? 
A. No, the underlay in SDA is a pure L3 routed network. VLANs will be present only on your edge devices at the access port level. Your intermediate devices will not need to know the VLANs of the End Hosts. 

Looking for more resources? Access the latest guides, recordings and more via Cisco SD-Access ATXs Resources. For more SD-Access FAQ, see Wireless in SD-Access. 
Want to learn more and get real-time Cisco expert advice? Through live Q&A and solution demos, Ask the Experts (ATXs) real-time sessions help you tackle deployment hurdles and learn advanced tips to maximize your use of Cisco technology. Bookmark IBN ATXs calendar to view and register for new sessions as they're added.