Wireless LAN Controller (WLC) Prerequisites and Common Questions
About
This document provides a list of questions that SevOne requires the user to respond to prior to a fresh install or an upgrade. For details on compatibility, please refer to Release Notes Wireless LAN Controller (WLC) Collector > section Compatibility Matrix.
For Fresh Installs only
Health and Compatibility Checklist
Prerequisites for WLC Collector | Response | Introduced in Wifi 6.7 |
---|---|---|
1 | Please confirm that this is a request for a fresh install. Please circle one option in the Response column. | Yes / No If Yes, this is a fresh install, please continue with this table. If No, this is an upgrade, then please go to for Upgrades only. |
2 | Please provide the collector version you would like to install. NOTE: Please install or upgrade to the latest available version that is compatible with your SevOne NMS, SevOne Data Insight, and controller versions. Please refer to the Release Notes Wireless LAN Controller (WLC) Collector > section Compatibility Matrix for version compatibility details. If you are using older versions, please opt to upgrade to the latest version (if possible). |
<enter version here> |
3 | Please provide the vendor you want to use for the collection of data. Please circle one
option in the Response column. NOTE: If your environment supports both Cisco and Aruba vendors, please complete this form separately - one for each vendor. |
Cisco / Aruba |
4 | Are credentials for the PAS ready to share during the session? (Applicable only in case of
remote installation) Please circle one option in the Response column.
NOTE: Please ensure you have SSH username and password for the root user available prior to the session. |
Yes / No |
5 | Do you want to install collector locally or remotely? Please circle one option in the
Response column.
NOTE: Please select Local if you would like to install the collector on the same NMS where the script is running and, select Remote for collector installation on another PAS rather than the SevOne NMS. |
Yes / No |
6 | Have you performed the health check on your SevOne NMS cluster to ensure that all critical
services are up and running with no potential issues? If Yes, please share the results in the
Response column.
NOTE: Execute SevOne-act check checkout --full-cluster command to perform the health check. If you do not have access to shell prompt, please contact IBM SevOne Support. |
<enter results here> |
7 | Is password for NMS ready to share during the installation/upgrade session? Please circle one
option in the Response column.
NOTE: Please ensure all passwords are available prior to the session. |
Yes / No |
8 | Has the installer tar been downloaded to your system? Please circle one option in the Response column. | Yes / No |
9 | Have you verified the checksum of the installer file? NOTE: If you do not know how to verify
the checksum,
|
Yes / No |
10 | Have you created the MySQL user?
NOTE: If you do not know how to create MySQL user, please refer to Wireless LAN Controller (WLC) Collector Installation Guide > section Pre-Installation > subsection Create MySQL User. |
|
11 | Do you want to display username of the station in SevOne NMS/Data Insight? Please circle one option in the Response column. | Yes / No |
Configuration Checklist
Prerequisites for WLC Collector | Response | Introduced in Wifi 6.7 |
---|---|---|
1. Please provide the system configuration details (RAM, Hard disk size, and CPU) of SevOne NMS.
NOTE: These are the system configuration details for SevOne NMS appliance where the deployment script will be executed from and where the collector will be sending data to. If you are unable to locate this information, please contact IBM SevOne Support. |
<enter configuration details> | Yes / No |
2. Please provide the SevOne NMS appliance username for an administrator-level account. | <enter SevOne NMS appliance username here> | Yes / No |
3. Do you want to distribute devices created by the collector among all or some peers of the
NMS cluster? Please provide details in the Response column.
NOTE: If you want to distribute devices to some peers only then, please provide the IP addresses / peer names of those selected peers in the Response column. |
<All / Some> <
If Some, please enter IP addresses / peer names of selected peers> |
Yes / No |
4. Please provide the IP address of the collector in the Response column. (Applicable only in case of remote installation) | <enter IP address> | Yes / No |
5. Please provide the Device Group name for the collector in the Response column. | <enter Device Group name> | Yes / No |
6. Please provide the IP address for (primary) PAS. Do you want to install collector on secondary HSA? If Yes, please provide the IP address for secondary HSA in the Response column. |
<enter IP address for PAS>
<enter IP address for HSA> |
Yes / No |
7. Please provide the vendor you want to use for the collection of data. Please circle one
option in the Response column.
NOTE: If your environment supports both Cisco and Aruba vendors, please complete this form separately - one for each vendor. |
Cisco / Aruba | Yes / No |
8. Is Administration > Cluster Manager > Cluster Settings tab > Security subtab > Mask Read Community String field disabled in your SevOne appliance? Please circle one option in the Response column. | Yes / No | Yes / No |
9. Do you want to enable the cleanup feature for removing the inactive wifi station license(s)? If Yes, please provide the configuration (.json) file. | <enter configuration (.json) file here> For example, {"SevOne": 168, "SevOne-guest": 48} | Yes / No |
10. Do you want to disable the creation of any specific ESSID's aggregation object for all AP
(Access Point) devices? If Yes, please provide the list of ESSIDs. In
/opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable
AP_ESS_AGG_BL.
For example, AP_ESS_AGG_BL=guest1, guest2, where ESSID aggregation objects for guest1 and guest2 will not get created for any AP devices. The default is "". NOTE:
|
<enter list of ESSIDs here> | Yes / No |
11. Do you want to completely disable ESSID aggregation object creation for all AP devices?
Please circle one option in the Response column.
If Yes, in /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable AP_ESS_AGG_BL_ALL=false. Variable AP_ESS_AGG_BL will be ignored. |
Yes / No | Yes / No |
12. Do you want to distribute devices across the cluster on its own on all the peers? If Yes,
please provide the list of peers to distribute data in the Response column.
NOTE: If you want to distribute devices to some peers only then, please provide the IP addresses / peer names of those selected peers in the Response column. |
<enter list of peers here> | Yes / No |
13. Do you want to enable SSL authentication for the collector to SevOne NMS REST API
communication? If Yes, please provide an absolute path in the Response column. The default is "".
NOTE: If you are unable to locate this information, please contact IBM SevOne Support. |
<enter absolute path here> | Yes / No |
14. Please provide the time to add in the policy for detecting unused Access Points (APs) in
the Response column.
NOTE: This value must be greater than twice the poll interval. |
<enter time (in seconds) here> | Yes / No |
15. Do you want to enable UPDATE UNAVAILABLE APS flag? Please circle one option in the
Response column.
NOTE: If you select Yes, all the unavailable APs that are collected from WLC will have their indicators sent as zero and changed its WLC name to unknown. If you select No, no changes will be made to AP and all its values will be left as they are. |
Yes / No | Yes / No |
16. Do you want to stop monitoring individual stations for WLCs that are in the blocklist?
Please circle one option in the Response column.
NOTE: These stations will still be considered for other aggregations. |
Yes / No | Yes / No |
17. Have you checked that no duplicate WLC is pinned in the collector polling group? | Yes / No | Yes / No |
18. Have you removed the same AP (Access Point) reported by multiple WLCs from all except one of the WLCs? | Yes / No | Yes / No |
19. Do you want to disable the creation of any specific ESSID's aggregation object for all
WLCs (Wireless LAN Controllers)?
If Yes, please provide the list of ESSIDs. In /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable WLC_ESS_AGG_BL. For example, WLC_ESS_AGG_BL=guest1, guest2, where ESSID aggregation objects for guest1 and guest2 will not get created for any WLC devices. The default is "". NOTE:
|
<enter list of ESSIDs here> | Yes / No |
20. Do you want to completely disable ESSID aggregation object creation for all WLC devices?
Please circle one option in the Response column.
If Yes, in /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable WLC_ESS_AGG_BL_ALL=false. Variable WLC_ESS_AGG_BL will be ignored. |
Yes / No | Yes / No |
21. Do you want to enable Wifi Stations monitoring for only a few ESSIDs?
If Yes, please provide the list of ESSIDs in the Response column, where you want to enable Wifi Station monitoring. In /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable WLC_ESS_WL. For example, WLC_ESS_WL=guest1, guest2, where Wifi Stations belonging to guest1 and guest2 will be monitored. The default is None. NOTE: The Wifi Stations belonging to other ESSIDs will still be considered for other aggregations. |
<enter list of ESSIDs here> | Yes / No |
22. Do you want to disable creation of manufacturer aggregation objects for the given list of
WLCs?
If Yes, please provide the list of WLC names in the Response column. In /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable WLC_MFG_AGG_BL. For example, WLC_MFG_AGG_BL=cisco-wlc1, cisco-wlc2, where Manufacturer aggregation objects will not get created for cisco-wlc1 and cisco-wlc2. The default is "". NOTE: Manufacturer aggregation object Created for WLC devices and it helps you to monitor the
following:
|
<enter list of WLC names here> | Yes / No |
23. Do you want to completely disable creation of manufacturer aggregation objects for all
WLCs? Please circle one option in the Response column.
If Yes, in /opt/WLCCollector/configuration/cisco.env or aruba.env file, set environment variable WLC_MFG_AGG_BL_ALL=true. Variable WLC_MFG_AGG_BL will be ignored. |
Yes / No | Yes / No |
24. Please highlight any detail that must be addressed during the fresh installation session. | <enter details> | Yes / No |
For Upgrades only
Health and Compatibility Checklist
Prerequisites for WLC Collector | Response |
---|---|
1. Please confirm that this is an upgrade request. Please circle one option in the Response column. | Yes / No
If Yes, this is an upgrade, please continue with this table. |
2. Please provide the collector version you would like to install.
NOTE: Please install or upgrade to the latest available version that is compatible with your SevOne NMS, SevOne Data Insight, and controller versions. Please refer to the Release Notes Wireless LAN Controller (WLC) Collector > section Compatibility Matrix for version compatibility details. If you are using older versions, please opt to upgrade to the latest version (if possible). |
<enter version here> |
3. Please provide the vendor you want to use for the collection of data. Please circle one option in the Response column. If your environment supports both Cisco and Aruba vendors, please complete this form separately - one for each vendor. | Cisco / Aruba |
4. Have you checked and verified the version numbers of your SevOne NMS, SevOne Data Insight,
SOA, Docker, and Controller? If Yes, please provide the current versions of your setup in the
Response column. Please refer to the Release Notes Wireless LAN Controller (WLC) Collector > section Compatibility Matrix for version compatibility details. To check the docker version, please run the following command on the collector and augmentor VM: $ docker -v To check the SOA version, please run the following command on the NMS appliance: $ docker ps | grep soa If you do not have access to shell prompt, please contact IBM SevOne Support. |
|
5. Are credentials for the PAS ready to share during the session? (Applicable only in case of
remote installation) Please circle one option in the Response column.
NOTE: Please ensure you have SSH username and password for the root user available prior to the session. |
Yes / No |
6. Has the installer tar been downloaded to your system? Please circle one option in the Response column. | Yes / No |
7. Have you verified the checksum of the installer file? NOTE: If you do not know how to
verify the checksum,
|
Yes / No |
8. Have you created the MySQL user? NOTE: If you do not know how to create MySQL user, please refer to Wireless LAN Controller (WLC) Collector Installation Guide > section Pre-Installation > subsection Create MySQL User. | Yes / No |
9. Please attach the output of docker images from the collector VM in the Response column. | <enter output here> |
10. Have you performed the health check on your SevOne NMS cluster to ensure that all critical services are up and running with no potential issues? If Yes, please share the results in the Response column. Execute SevOne-act check checkout --full-cluster command to perform the health check. If you do not have access to shell prompt, please contact IBM SevOne Support. | <enter results here> |
11. Please confirm whether the existing collector is collecting data without any issue or not? Please circle one option in the Response column. | Yes / No |
Configuration Checklist
Prerequisites for WLC Collector | Response | Introduced in Wifi 6.7 |
---|---|---|
1. Please provide the SevOne NMS appliance IP address / Virtual IP address in the Response column. | <enter IP address / Virtual IP address here> | Yes / No |
2. Please provide the IP address for (primary) PAS. Do you want to install collector on secondary HSA? If Yes, please provide the IP address for secondary HSA in the Response column. | <enter IP address for PAS> <enter IP address for HSA> | Yes / No |
3. Do you want to distribute devices created by the collector among all or some peers of the
NMS cluster?
NOTE: If you want to distribute devices to some peers only then, please provide the IP addresses / peer names of those selected peers in the Response column. |
<All / Some> <If Some, please enter IP addresses / peer names of selected peers> | Yes / No |
4. Please provide the vendor you want to use for the collection of data. Please circle one
option in the Response column.
If your environment supports both Cisco and Aruba vendors, please complete this form separately - one for each vendor. |
Cisco / Aruba | Yes / No |
5. Do you want to modify an existing configuration? Please circle one option in the Response column. | Yes / No | Yes / No |
6. Please highlight any detail that must be addressed during the upgrade session. | <enter details> | Yes / No |