Cisco Wireless Controller Configuration Guide, Release Cisco Cisco Wireless Controller Cisco Flex Wireless Controller. Cisco Wireless Controller Configuration Guide, Release Series Wireless Controllers · Wireless Controller · Wireless Controller · . Cisco Wireless LAN Controller Configuration Guide, Release .. The controller supports up to lightweight access points and.

Author: Mektilar Najas
Country: Saint Kitts and Nevis
Language: English (Spanish)
Genre: Environment
Published (Last): 7 May 2014
Pages: 172
PDF File Size: 9.3 Mb
ePub File Size: 3.81 Mb
ISBN: 498-7-72049-791-6
Downloads: 32182
Price: Free* [*Free Regsitration Required]
Uploader: Dobar

The purpose of this guide is to:. As such, this guide refers to “OpenDNS”, “Cisco Umbrella”, or simply “Umbrella” wherein all three are the same and thus interchangeable. In a future release, all names will be simply “Cisco Umbrella” or “Umbrella”. The information in this document was created from devices in a specific lab environment.

All of the devices used in this document started with a cleared default configuration. If your network is live, make sure that you understand the potential impact of any command.

Cisco Umbrella is a cloud delivered network security service which protects devices from malware and breach protection in real cicso. Umbrella uses evolving big data and data mining methods to proactively predict attacks. As well, Umbrella can be configured to filter content access to websites so you can better control your network environment. If the domain is marked as malicious, Umbrella returns the IP of a block page to the client.

If it is determined to be safe, Umbrella returns the resolved IP address to client.

VIEW Certified AP Configuration Guides | Spectralink Support

The Cisco Umbrella profile when mapped to local policy allows for a granular differentiated user browsing experience configruation on the dynamic evaluation of attributes user role, device type etc. For the rest of buide document, we will discuss following scenarios:. We will also touch upon basic configuration on Cisco Umbrella Server.

In an organization, our goal is to restrict internet access for particular websites to users based on their role types. For example, regular employees should be permitted cisoc internet access barring sites such as adult, gambling, nudity.


At the same time, contractor access should be more rigid, barring access to social websites, sports, and news, as well as adult, gaming, nudity, and other such sites.

We will be using an external AAA server to authenticate a user and based on the identity, pass the user role as either contractor or employee to WLC. On the WLC, user will configure two policies for employee and contractor and apply a different Cisco Umbrella profile to each to restrict their browsing activity gkide connected to the same dot1x enabled WLAN. To achieve this, we will:.

Hardware Integrations

These profiles are automatically pushed to your Umbrella account as Identities and you should see the State of the Profiles populated as Profile Registered.

This is subject to a successful connection between the WLC and Umbrella server. Next, create classification rules for employee and contractor user roles selecting the domains that should be blocked for both of these roles. The employeeCategory is blocking certain content categories; cpnfiguration example, Adult themes, Adware, and Gambling. Expand employeeCategory to view its list of blocked categories.

You can edit the list to add or remove categories. For a list of all categories and details for each, see Understanding Content Categories. A policy wizard is available to configure each WLAN identity affected and the mapped category setting.

Here, employeePolicy is assigned to employeeOD identity and tied to a category employeeCategory created in the last step. Similarly, contractorPolicy is assigned to contractorOD identity and tied to a custom category contractorCategory created earlier. Create an ISE policy for a specific group of users with a desired role, that is, employee or contractor.

Now create two local polices for employee and contractors on the WLC. From the dropdown list, select “employeeOD” then click Apply. The CLI command is “command: These reports can be filtered by client identity, destination and source IP. Only admins can see this Enable it for everyone. The purpose of this guide is to: Next, apply the Token on the Wireless Lan Controller. This should register the device to the Umbrella account. Profiles will automatically be pushed to the Umbrella dashboard as Identities and policy can be enforced on a per identity basis.


Wireless client traffic flow from to the Umbrella server. Profile is the identity of the packet which also resides on OpenDNS. Umbrella then enforces a policy on it depending on the identity and applies category based filtering rules to ensure organization compliance.

Depending on the policy and whether a destination is considered malicious, the service either returns the IP of a block page or resolved IP address to the client for the DNS request queried.

We have created employeeCategory and contractorCategory for this exercise. As illustrated below, on the ISE, configure users, that is, employee and contractor: Next, configure groups, that is, group Employee and contractor.

Configure local policies for OpenDNS. Finally, map the local policy to a particular WLAN. Create Local Policy name as “employee” and “contractor” and click Apply. Click Back to go to the Local Policy page and click the contractor policy. Connect a client to your WLAN with employee user credentials.

VIEW Certified AP Configuration Guides

Try accessing sites that are blocked under the category filtering rules you created for employee. Try to associate to the same WLAN using contractor user credentials and repeat the test.

You will notice the difference in browsing access granted to an employee versus a contractor. Happens in the client join phase.