WSM FAQ

The WSM component identifies a wireless device by reading its MIB node properties. If the WSM component fails to read the MIB of a device, it will not display the device. In such a case, check whether the version of the WSM component matches that of the device. If it does not, change the version of the WSM component or the device. If it does, provide system logs and captured packets to R&D personnel for assistance in troubleshooting the issue.

ACs use platform licenses. Fat APs and fit APs use WSM licenses.

The number of licenses for fit APs is calculated based on the number of AP templates with different SNs configured on the AC.

An AC can be added to WSM even if the number of AP templates on the AC exceeds the maximum number permitted by the license. However, the number of APs managed in WSM cannot exceed the maximum number.

The realtime reports are generated every hour and are saved for 30 days. You can view the realtime report data one hour later.

If a large number of AP templates or VLANs exist, WSM requires some time to synchronize the device information. During this period, exceptions might occur for some operations.

Repetitive data is displayed because a device is added to multiple custom views. To avoid repetitive data, make sure each device is added to only one custom view.

WSM aggregates the performance data every hour, on the hour. If WSM related processes are stopped at this time, the aggregating operation is also stopped. As a result, the collected performance data cannot be aggregated to the per-hour table and per-day table. To solve this problem, do not restart WSM related processes on the hour.

The wireless performance statistics cover only data messages (traffic, packet, and rate) instead of control messages of the protocol or physical layer.

This problem occurs because the performance data collecting function is disabled (the default) for clients. To enable the function, add startStaPerfColl=true and StaPerfCollIntv=900 (the value of StaPerfCollIntv can be any positive integer) to the qvdm_wlan.conf file in the installation directory server/conf, and then restart the imcwlandm.exe and imcwlanperfdm.exe processes.

In INC, report data can be saved as raw data, hourly data, and daily data.

For an AP bandwidth statistics report, data is generated in the following ways:

• Raw data: INC collects traffic data every 5 minutes. The raw data at a specific time is the difference of the traffic data collected between two statistics collection operations divided by the statistics collection interval (5 minutes).
• Hourly data: Every hour, INC takes the mean value of the raw data collected within the last hour as the hourly data.
• Daily data: At 00:00 every day, INC takes the mean value of the hourly data collected during the last day as the daily data.

For a wireless traffic statistics report, data is generated in the following ways:

• Raw data: INC collects traffic data every 15 minutes. The raw data is the difference between the traffic data collected in two statistics collection periods.
• Hourly data: INC takes the sum of the raw data collected within the last hour as the hourly data.
• Daily data: At 00:00 every day, INC takes the sum of the hourly data collected during the last day as the daily data.

If you query the history data of the last 3 days, INC reads the raw data. If you query the history data of the last week, INC reads the hourly data. If you query the history data of a long period, for example, the last month, INC reads the daily data.

The following issues might occur:

• The sum of the traffic of the last day is greater than the sum of the traffic of the last week. This is because no hourly data is generated within the last hour. The sum of the traffic of the last day contains the traffic of the last hour, while the sum of the traffic of the last week does not, so if INC has been deployed for less than a week, and the volume of traffic during the last hour is large, the sum of the traffic of the last day can be greater than the sum of the traffic of the last week.
• The sum of the traffic of the last week is greater than the sum of the traffic of the last month. This is because no daily data is generated within the last day. The sum of the traffic of the last week contains the traffic of the last day, while the sum of the traffic of the last month does not, so if INC has been deployed for less than a month, and the volume of traffic during the last day is large, the sum of the traffic of the last week can be greater than the sum of the traffic of the last month.

In INC, data can be saved as raw data, hourly data, and daily data.

The client count data is generated in the following ways:

• Raw data¡ªCollected every 5 minutes.
• Hourly data¡ªThe mean value of the raw data collected within the previous hour.
• Daily data¡ªThe mean value of the hourly data collected during the previous day.

If you query the history data for the last 3 days, last week, and a longer period, INC reads the raw data, hourly data, and daily data, respectively.

The following situations might exist:

• The client count at a specific time point in the last week is smaller than the count at the same time point in the last three days. This is because the data for the last week is generated based on hourly data and the data for the last three days is generated based on raw data.
• The client count at a time point in the last month is smaller than the count at the same time point in the last week. This is because the data for the last month is generated based on daily data and the data for the last week is generated based on hourly data.

A radio-related report displays information about radios whose duplicate serial IDs are filtered out. However, a radio list displays radio information by AC. When the primary and backup ACs contain fit APs of the same serial ID, the radio list displays multiple records for the radio because the radio is associated with different ACs.

The actual location of the AP might change after the client online history information is collected.