Why Is a Fabric-Enabled WLC Not Discovered by DNA Center?
During discovery, one out of five fabric-enabled WLAN controllers is not being properly discovered. The firewall rules are the same for all the controllers. Which element is missing?
Community Votes
67% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests DNA Center discovery prerequisites for SD-Access fabric WLCs, with the trap of choosing SNMP management when general discovery credentials are already working for other controllers.
Cisco DNA Center discovery of fabric-enabled WLAN controllers requires NETCONF; this page explains why a single undiscovered controller points to missing NETCONF rather than SNMP or firewall issues.
Many choose SNMP management (B) because SNMP is a standard discovery credential, but the question's fabric context and the four working controllers indicate NETCONF is the missing fabric-specific element.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Cisco DNA Center uses NETCONF (TCP port 830) to discover and manage fabric-enabled devices in an SD-Access fabric, including fabric WLAN controllers. If NETCONF is not enabled on the WLC, DNA Center cannot properly discover it as a fabric node, even when SNMP and CLI credentials are correct and firewall rules are consistent. Since four out of five controllers are discovered successfully, the shared credentials and firewall rules are not the issue; the single controller is missing the fabric-specific NETCONF configuration. Enabling NETCONF on that WLC resolves the discovery problem.Why the Other Options Are Wrong
A. YANG is a data modeling language used by NETCONF, but its presence or absence does not affect device discovery; it is not a transport protocol. B. SNMP management is mandatory for basic device discovery, but the question states that four controllers are discovered with the same firewall rules, implying SNMP is configured correctly across the board; the fabric requirement points to NETCONF. C. SNMP trap is used for event notifications and assurance data, not for initial device discovery, so a missing trap destination would not prevent discovery.Community Comment Notes
As rrahim noted, "If NETCONF is not enabled or properly configured on the WLC, it will not be discovered" by Cisco DNA Center, highlighting the fabric-specific requirement. However, 1bc4e4b argued that "For discovery, one set of CLI credentials and one set of SNMP credentials" is mandatory, which is true generally but does not explain why only one fabric-enabled WLC fails. Le91 also mentioned that "Netconf (Network Configuration Protocol) could also play a role in the discovery process" for fabric controllers, aligning with the correct answer.Exam Strategy
When troubleshooting DNA Center discovery, isolate shared versus device-specific settings: if multiple devices fail, suspect credentials, firewall, or routing; if a single fabric device fails, check fabric-specific protocols like NETCONF. Remember that NETCONF (TCP 830) is required for SD-Access fabric devices, including WLCs.
Frequently Asked Questions
Why is SNMP management (B) not the missing element here?
SNMP is required for all device discovery, but the scenario says four controllers are discovered with the same firewall rules, so SNMP is already working; NETCONF is the fabric-specific requirement.
What port does NETCONF use for DNA Center discovery?
NETCONF uses TCP port 830. If that port is blocked or NETCONF is disabled on the fabric WLC, DNA Center cannot discover it as a fabric device.