Registering Embedded Wireless Controller to Cisco Umbrella Account
Before you Begin
You should have an account with Cisco Umbrella.
You should have an API token from Cisco Umbrella.
The embedded wireless controller is registered to Cisco Umbrella server using the Umbrella parameter map. Each of the Umbrella parameter map must have an API token. The Cisco Umbrella responds with the device ID for the embedded wireless controller. The device ID has a 1:1 mapping with the Umbrella parameter map name.
Fetching API token for Embedded Wireless Controller from Cisco Umbrella Dashboard
From Cisco Umbrella dashboard, verify that your embedded wireless controller shows up under Device Name, along with their identities.
Applying the API Token on Embedded Wireless Controller
Registers the Cisco Umbrella API token on the network.
DNS Query and Response
Once the device is registered and Umbrella parameter map is configured on WLAN, the DNS queries from clients joining the WLAN are redirected to the Umbrella DNS resolver.
This is applicable for all domains not configured in the local domain RegEx parameter map.
The queries and responses are encrypted based on the DNScrypt option in the Umbrella parameter map.
For more information on the Cisco Umbrella configurations, see the Integration for ISR 4K and ISR 1100 – Security Configuration Guide.
Limitations and Considerations
The limitations and considerations for this feature are as follows:
You will be able to apply the wireless Cisco Umbrella profiles to wireless entities, such as, WLAN or AP groups, if the device registration is successful.
In case of L3 mobility, the Cisco Umbrella must be applied on the anchor embedded wireless controller always.
When two DNS servers are configured under DHCP, two Cisco Umbrella server IPs are sent to the client from DHCP option 6. If only one DNS server is present under DHCP, only one Cisco Umbrella server IP is sent as part of DHCP option 6.