A new access point joins a Catalyst 9800 and its radios stay down. Other access points in the same country are serving clients. This access point's regulatory domain does not match the configured country. What is the mismatch?
Select an answer to reveal the explanation.
Short Explanation
You can trust that the working access points show the configured country is serving the site. This access point has a regulatory-domain mismatch, so its radios stay down. A DHCP lease timer does not set a country code.
Full Explanation
An access point is built for a regulatory domain, and the controller enables its radios only when that domain agrees with the configured country. This access point joined the controller, but its radios stay down while other access points in the same country serve clients. The mismatch is between this access point’s regulatory domain and the country the controller is using. The guest VLAN is a client network; it does not need to match a regulatory domain before a radio can start. DHCP lease length is an address timer, not a setting that assigns an access point’s regulatory domain. The beacon interval controls beacon timing and does not carry the country code. Country is configured on the controller, while the access point has its own regulatory domain; neither a VLAN nor a timing value substitutes for that match. Exam caveat: do not change the controller country to match one incompatible access point when the rest of the site is legal and working. Replace or re-domain the outlier only if the hardware permits it. Practical check: compare this access point’s regulatory domain with a working neighbor’s and with the configured country, then confirm its radios come up when the domain agrees.