The WLC Manager lets you discover, model, and monitor Wireless LAN controller (WLC) module components, regardless of the device it is present in, allows you to centrally manage and configure a number of access points (APs) in a simplified manner within the network environment. WLC Manager provides AP (Wireless Access Point) Names and Device discovery and modeling, AP connectivity status, SNMP trap handling, monitoring of WLC conditions, and performs calculation of and alarming on AP conditions.
WLC Manager discovers all the Access Points (AP) associated with a particular WLC Controller. If the intermediate L2 and L3 devices are discovered connections are automatically made.
DX NetOps Spectrumcreates AP models representing each unique Access Point. These AP models can then be polled for their current operational status (Up or Down).
In addition, WLC Manager supports CAPWAP and CISCO LWAPP (Lightweight Access Point Protocol), a protocol that can control multiple WiFi Wireless Access Points at once. This helps reduce the amount of time that is spent on configuring, monitoring, or troubleshooting a large network. The system also allows network administrators to closely analyze the network. This system is installed in a central server that gathers data from RF devices from different brands and settings. The server can command a selected group of devices to apply given settings simultaneously.
This enables you to monitor the status of the paths between the sites in each of the modeled APs. You can configure threshold alarms to alert you when path changes exceed the configured tolerance.
- Do not delete a WLC device, while it is still being modeled. We recommend that you wait until the WLC model is activated and the modeling is completed, before you delete the WLC, so that all the AP models created (associated with the WLC you want to delete) are also deleted.
- If you delete a WLC device before all its associated Access Points (AP) model creation is complete, all the sub-modules or models may not be deleted and can be found in the Lost/Found Container.
- DHCP IP changes are now supported for APs; duplicate models were being created as dynamic IPs were created when WLC/ AP down/ reboot happened.
- Now models are created on unique MAC ID thus negating the possibility of duplicate models.
- AP name changes are now supported and the updated AP name will reflect after the next polling cycle of the WLC.
From 10.2, you can no longer manually discover and model APs by model type (AP-Pingable in earlier releases). Navigate to the
WLC Controller > Information Tab > Configuration sub-view and Run AccessPoint discovery.
If you are upgrading to 10.2, all existing AP-Pingable models will be modeled as AccessPoint models after the upgrade.
To view the WLC Manager in the OneClick Console Topology view, select WLC Manager from the Explorer Hierarchy
WLC Manager provides searches that let you quickly find a particular AP or all APs. Search results contain a list of the current Wireless Access Points that are configured within the environment and their status.
You can drill into a single AP to see the current list of Wireless interfaces participating within that AP and the status of the Access Point(s).
Moving Access Points (APs) with WLC
From 10.2.2, the WLC Manager includes the option to move access points (APs) with the WLC. When the WLC is moved to any other container, all the APs attached to it are moved to that respective WLC container. This feature automates the movement of APs across various containers. By default, this value is set to
Yes.If you want to retain the APs attached in the WLC container, then set this value to
No, then access points (APs) remain in the same container, although the WLC is moved to a different container.
DX NetOps Spectrumlets you generate reports for events that are raised on Wireless APs, by enabling the Event Generation for Reporting option, at the WLC Manager level.
The default value for the
Event Generation for Reportingfield is
To enable these Wireless reports, from the OneClick console> Explorer Hierarchy, navigate to the
Event Generation for Reportingfield and select
Enabledfrom the corresponding drop down option.
Once you set this to
Enabled,the events that are raised on the selected WLC Controller, are registered in the SRM DB, parsed and the event information is saved in the MySQL database named 'reporting' which Report Manager uses to store data. This database contains all the tables that are required to store the data that is used by SRM application to generate reports. At startup, the Report Manager retrieves the data from the primary Archive Manager for each SpectroSERVER through OneClick and stores the data in the SRM databases.
Discover Connections Only toward Access Points
In 10.3 release and earlier releases, when the Access Point Discovery is run, the WLC Manager discovered connections on all the subnet switches corresponding to the access points (APs). From 10.3.1, the WLC Manager includes an option to discover connections only toward the access points (APs) from their right upstream switches, which skip creation of other neighbor connections for subnet switches. This feature uses mac address (SAT Table) or IP address (CDP Table) of the Access Point to discover connection toward its upstream switch.
By default, this value is set to
No. If you want to see the connections only toward access points, then set this value to
In 10.4.2, this option is enabled by default; that is, the parameter value is already set to Yes.
In 10.4.1, if any applicable alarm is raised on an access point (AP), then the alarm is asserted to that AP. Similarly, if any alarm is raised on a WLC controller, then the alarm is asserted to the WLC controller. This functionality helps in the proper organization of the alarms based on the associated AP or WLC controller, allowing you to manage your devices more efficiently. Previously, all alarms were getting asserted to the WLC controller irrespective of the fact where the alarm had been raised: AP or WLC controller.
Raise Access Point-Related Alarms Only on Associated Access Points
If the required AP is not accessible for asserting the alarm, then the related AP alarm is asserted to the associated WLC controller.