Monitoring, Management & Location Tracking

AMP 4.3.1 Known Issues

Known Issues from Release Notes:

4.1 Upgrading to CentOS 4.3 kernel using yum/up2date degrades performance on the AMP

Upgrading the kernel to the CentOS 4.3 version increases the memory usage (and hence degrades performance on the AMP) causing the machine to be unusable. The yum/up2date config file can be configured to ignore updates to the kernel. Please contact support if you need help with the configuration. 

4.2 Static IP Provisioning with IOS APs has some issues

Cisco IOS APs that are in DHCP mode do not show the right mismatches if AP is in monitor mode and the Group is enabled to use static IP pool provisioning.

4.3 Known AWSP/Visual RF Issues

· HP420 and Enterasys APs do not display heatmap and channel views correctly. Please contact AirWave Support for the version of the AMP that fixes this issue.
· Visual RF becomes slow after loading a lot of sites and memory usage increases. Coordinates of walls are in inches, need to be in feet
· Delete survey button should work only in edit mode
· Auto-refresh option is missing
· Changing wall attenuation does not get reflected in db and (x,y) coordinates
· Site survey lines show up connected to rogues even when site survey is off
· High values of height and width could cause memory issues
· Visual RF link for rogues does not get displayed all the time.
· Edit button needs to be toggled after loading a new site.
· Site not found error message displayed when launching Visual RF from the AirWave Management Client.
· Stencils for Proxim 4900 APs are not supported.
· Cisco 1200 LWAPP APs with only 802.11g radio is not supported by AWSP and Visual RF
· Long site names could hide the size

4.4 AP count could be doubly counted on Master Console

The numbers of APs are doubly counted if the Master Console is monitoring both the failover AMP, which has taken over for one of the watched AMPs and the watched AMP itself.

4.5 Master Console has errors while monitoring AMPs running versions earlier than 4.3.0

Master Console displays errors about folder_list.xml on AMPs running versions earlier than 4.3.0.

4.6 Static Routes cannot be added on the AMP Setup->Network page

Users cannot add new static routes on the AMP Setup->Network page. The workaround is to change the permissions on the file /etc/sysconfig/static-routes to 644 and then add the static routes from the AMP Setup->Network page.

4.7 AMP Setup->Role on Master Console has option for folder

AMP Setup->Role page on the Master Console has option for folder, which is not used.

4.8 Open Issues with Enterasys AP3000/4102

· The AP->Monitor page displays - for ssid on the AP->Monitoring page on the Enterasys AP3000/4102 models.
· Switching between WEP and 802.1x results in mismatches on the AMP
· Max Station Data Rate is not supported for a and the b/g radios
· Disabling vlan tagging after enabling and configuring vlans does not work as desired.

4.9 Home->Overview page displays Nightly Backup Failed message after a clean install

Home->Overview page displays Nightly Backup Failed message after a clean install. The messages get cleared after the nightly maintenance has been run.

4.10 AMP has errors while managing Cisco 1200 IOS APs with only 802.11a radio using IOS Advanced

While managing Cisco 1200 IOS APs with only the 802.11a radio, the AMP populates empty values in the power, channel variables on the Group->Templates page.

4.11 AMP stuck in nightly maintenance mode when postgres cannot be stopped.

Postgres does not stop during nightly maintenance sometimes and that could cause the AMP to be stuck in nightly maintenance mode. The workaround for this issue is to restart Apache by typing service httpd restart. In order to fix the nightly maintenance issue and generate backups please contact AirWave Support. 

4.12 Saving the license on the failover AMP could cause errors

Users could have errors if they click on Save on the Home->License page of a failover AMP which has taken over one of the watched AMPs.

4.13 Disabling wireless scan may not work

AMP still detects and displays rogues on APs, which have wireless scanning disabled. 

4.14 Users with read-only RAPIDS access has link to score overrides

Users with read-only RAPIDS access have links editing the score overrides. The links should not be displayed for read-only RAPIDS users since they cannot edit them.

4.15 Rogue->Detail page includes multiple discovery events by same AP 

Sometimes the Rogue->Detail page includes multiple discovery events by the same AP. This bug seems to be limited to the Colubris APs.

4.16 User Radio Mode may not be updated

If AMPs information on the APs radio mode is not accurate (i.e., the configuration on the AMP is not the same as on the AP) it could be possible that the user radio mode is not accurate. This could be corrected by refreshing the AMPs information of the AP.

4.17 Add/Edit Folder does not return to the right folder view

Add/Edit a folder brings the user back to the Top folder and not to the folder as per the folder display parameters.

4.18 128 bit WEP keys in hex cause the Aironet 4800 to disable radio

Configuring 128 bit hex WEP keys causes the Aironet 4800 AP to disable its own radio. 

4.19 AMP fails to parse transmit power of max correctly on 12.3(7)JA and higher

Default behavior of the max transmit power has been changed on Cisco IOS APs running 12.3(7)JA and higher. AMP shows a mismatch when the AP is set to transmit power of max. One of the workarounds will be to set the transmit power of 17 which is equivalent of max.

4.20 Columns not aligned on a Configuration Audit Report 

The Desired Config and the Device Config could be a little unaligned in the Configuration Audit Report.

4.21 IOS mismatches with bridge-group spanning lines

Users have encountered with issue resolving mismatches related to bridge-group spanning lines on Cisco IOS APs using Advanced Group Configuration. AirWave is working on resolving this issue in the future releases.

4.22 802.11a channels not complete for all regulatory domains

The 802.11a channels available for each regulatory domain are not complete on the AMP. Please contact support if you find any channels missing for a specific regulatory domain. 

4.23 No confirm page when deleting a role

Confirm page is not displayed when users try to delete a role from the AMP Setup->Roles page.

4.24 SNMP discovery issues

SNMP discovery of multiple class C scans fails to discover APs sometimes. Please contact AirWave 
Support if you encounter any issues with discovery.

4.25 Deleting Rogue APs while OS scanning is in progress could restart the APScanner Daemon (Case 9586)

The APScanner daemon will get restarted if rogues which are being scanned for their OS are deleted.

4.26 Lancom AP reports Client IP as the mac (Case 8130)

Sometimes, the Lancom AP reports the clients IP address as its radio mac address and hence the AMP displays the mac address in the ip column. 

4.27 RAPIDS->Rogue APs list order not preserved after deleting a rogue AP (Case 9581)

The RAPIDS->Rogue APs sort is not preserved if one or more rogues are deleted.

4.28 All users from Users->Connected do not show up on the Users->All page (Case 9152)

AMP has a bug where all the entries in the Users->Connected page do not show up on the Users->All page. This will be fixed in a future release.

4.29 Quotes in syslocation/syscontact fields can cause mismatch while using IOS Advanced Config (Case 8741)

Quotes in syslocation and syscontact fields on the AP->Manage page can cause mismatches on the AP->Replace page on a Cisco IOS AP using IOS Advanced Group Configuration. Please note in spite of the mismatches the AMP displays a configuration status of Good. Removing the quotes fixes the mismatch.

4.30 Configuration mismatch on Cisco IOS APs moving from non-VLAN config to VLAN-config (Case 8533)

Users trying to move from a non-VLAN config to VLAN config will see a configuration mismatch on Cisco IOS APs running firmware earlier than 12.3(4) JA. The AMP does not delete the ssid related to the non-VLAN config on the AP. The workaround is to manually delete the ssid from the Access Point or use IOS Advanced Configuration option. 

4.31 Deleting Triggers deletes alerts (Case 8473) 

AMP deletes alerts associated to the trigger if the trigger gets deleted from the System->Triggers page. 

4.32 AMP does not configure Radius Servers on the 3 Com APs (Case 9092)

AMP does not configure radius servers on the 3Com 8750 APs, it does configure the Radius Mac Authentication settings on the AP. 

4.33 AMP cannot disable radio on the 802.11a radios on the Cisco IOS 1130 APs

AMP does not disable radios on the Cisco IOS 1130 APs correctly.

4.34 R2s with firmware 6.01 cannot be discovered using http (Case 8115)

R2s running firmware 6.01 and having a/b/g cards cannot be discovered using http scans since the web server is disabled by default on the APs. However, the APs can be managed by the AMP by adding them manually from the Device Setup->Create page.

4.35 AMP cannot create a new user on Colubris APs (Case 7996)

The Create New User option on the AP Setup->Communication does not work on the Colubris APs.

4.36 Group->Security page does not include AP-700 and AP-7 for MAC Format field (Case 7958)

AMP supports changing the MAC Address format for MAC Authentication feature on the AP-700 and AP-7 APs but the Group->Security UI does not reflect that.

4.37 Transmit Key cannot be changed while adding/editing a VLAN on Proxim/Avaya APs (Case 7650)

AMPs UI does not support changing the transmit key while configuring WEP on the VLAN add/edit page. This will be fixed in the future releases.

4.38 Rogue Scanning information on the AP->Replaces page for AP4000 and AP600 (g/a) APs is inconsistent (Case 7648)

Rogue Scanning information on the AP4000 and AP600 (with g/a radios) comes up under each radio and also the Group->Radio settings section. The information under each radio is accurate. The Rogue Scanning information in the Group->Radio section should be ignored. 

4.39 Modify These APs does not show the Group Name when APs are moved to a new group (Case 7843)

On the confirm page while the user is moving APs from one group to another the group name is not displayed. 

4.40 AirSpeed 542 is discovered as a AP4000 via Auto-Discovery daemons (Case 7718)

The AirSpeed 542 Access Point from Systimax is discovered by the AMP as an AP4000.

4.41 HTTP Scanning does not discover all rogues (Case 7860)

HTTP scanning needs a few more improvements to make it more reliable. This will be implemented in future releases.

4.42 Scheduled Firmware Upgrades List includes APs which are already on the desired firmware (Case 7862)

When user schedules firmware upgrade on APs from the Group->Firmware page the AMP lists the APs that are already on the desired firmware. Please note that the AMP will not try to push firmware on these APs since the firmware version is verified prior to doing that.

4.43 Confirm page for VLAN Add/Edit page has parameters which are not relevant to the security mode (Case 7625)

While adding/editing VLAN the user will notice a lot of parameters listed on the confirm page which he/she has not modified on the VLAN->Add page. 

4.44 AMP cannot configure correctly when VLAN 1 is not native VLAN on Cisco IOS APs (Case 7745)

AMP has problems configuring VLANs when VLAN #1 is a non-native VLAN on the Cisco IOS APs. The bridge group is not set up correctly in this case.

4.45 Duplicate/extraneous information AP->Replace page for Proxim/Avaya APs (Case 7586)

The AP->Audit page for Proxim/Avaya APs with 2.5.2 and above has some extraneous information. This will be fixed in a future release.

4.46 Known Issues with 802.11b or 802.11a 5GHz upgrade kit radios on Proxim/Avaya APs
· Only 1 VLAN can be configured when VLANs are enabled on the APs.
· WPA cannot be configured 

The limitations seem to be on the Access Point.

4.47 User needs to configure all 4 WEP keys for Require WEP on Proxim/Avaya 2.5.2 APs.

The Proxim/Avaya AP 2.5.2 firmware requires the user to configure all 4 WEP keys on the Group->Security page when encryption mode is set to Require WEP. This appears to be an AP bug and we have reported this issue to Proxim support. 

4.48 Proxim/Avaya 2.5.2 firmware configured with VLANs does not support changing SSID on slot B of a dual radio AP (Case 7587)

Proxim/Avaya 2.5.2 firmware configured with VLANs does not support changing SSID on slot B of a dual radio AP. This bug was noticed on an AP2000 with two radios irrespective of the radio type. Please note that VLAN configuration is not supported on AP2000 with 802.11b or 802.11a 5GHZ upgrade kit radios. 

4.49 "Transmit Power" is "failed to fetch" on the AP->Replace page for HP520 A-Radio (Case 7475)

On Proxim/Avaya/HP 520 firmware 2.4.3 and earlier, the Transmit Power setting comes up as failed_to_fetch on the AP->Replaces page for 802.11a radios. Upgrading the APs to firmware version 2.4.11 seems to resolve the error condition.

4.50 HTTP Scan does not find all APs in one scan (Case 7437)

The HTTP Scan does have some timing issues that prevent it from finding all the APs (that are HTTP Scannable) in one scan. The HTTP Scan can be repeated to ensure that all the APs in the network have been discovered.

4.51 VLAN Configuration Page - wording is confusing (Case 7461)

The option suggests that VLAN configuration is only supported on Colubris APs. VLAN configuration is supported on Cisco IOS/Vxworks, Colubris and Proxim APs.

4.52 Assert message on HTTP scan (Case 7458)

HTTP scans of some Enterasys R2 APs generate an error message in the AMPs log files. 

4.53 Hitting enter on the channel field while creating the Overlapping Channel Trigger does not add the trigger (Case 7460)

When the user hits enter in the channel field on the Overlapping Channel Trigger Page, the trigger does not get added and takes the user to the Trigger list page. This appears to be an IE bug and does not happen on other browsers. Please refer to this link for more information:

4.54 Very high bandwidth numbers on Symbol 4131 (Case 7455)

Sometimes, the Users on the Symbol 4131 Access Points display huge spikes of user bandwidth as reported by the AP. 

4.55 Radio enabled/disabled not supported on the Proxim AP2000, AP4000 and AP600 APs (Case 7147)

AMP does not support the Radio enabled/disabled on the Proxim AP2000, AP4000 and AP600 APs temporarily. This will be fixed in the next release of the AMP. Please note that the Radio type information is also not displayed on the AP->Manage page.
4.56 AMP supports Distance Between APs on AP1000 APs but the AMP UI does not reflect that

AMPs UI does not display the AP1000 as the APs that support the Distance between APs on the Group->Radio page. However the AMP does support setting and reading this parameter on the AP1000/AP500 family of Access Points.

4.57 Occasionally the freeradius rpm stops processing RADIUS accounting packets (Case 6545)

It has been found that occasionally freeradius version -1.0.2 stalls/hangs while processing radius accounting packets from the RADIUS accounting server. The AMP has been modified to handle this situation by monitoring the freeradius process (30 secs is the monitoring interval) closely and restarting it when it hangs. Please ensure that the (number of retries * timeout) is greater than 30 seconds while configuring the RADIUS accounting server to minimize packet loss.

4.58 VPN user information for Colubris Access Points does not work (Case 6534)

VPN user information feature for Colubris Access Points is broken on the AMP. AMP does not query the right MIB table for getting the vpn user information for the Users on the Colubris Access Points.

4.59 AMP cannot configure ? in the ssid for Cisco IOS and Accton-based Access Points 

User cannot configure an SSID which includes the ? on Cisco IOS, HP 420 and Roamabout 3000
Access Points.

4.60 AMP fails to configure Cisco IOS APs with a non-VLAN config when VLANs have been previously configured on the APs (Case 6049)

AMP fails in deleting the last VLAN defined on the Cisco IOS AP when a user is trying to change the configuration from a VLAN to a non-VLAN config.

4.61 User can add more than 16 VLANs (Case 6302)

AMP could allow user to enter more than 16 VLANs if the user does not do a Save & Apply on each VLAN addition.

4.62 Applying Changes to other groups can get groups in invalid state (Case 6015)

When changes are propagated to other groups, the other groups can get forced into invalid States (e.g., deleting a radius server when one is required).

4.63 AMP tries to fetch transmit power on an AP600 with b card (Case 6697)

AMP tries to fetch transmit power on an AP600 with b card which results in an error message on the AMP. Similar behavior has also been seen on an AP2000 with 5Ghz upgrade kit.

4.64 AMP fails to delete the last VLAN on Cisco IOS APs (Case 6049)

AMP fails to push configuration if the configuration change includes deleting the last VLAN defined on the Access Point.

4.65 AMP cannot manage IOS access points which do not require username or password for telnet access (Case 6220)

AMP cannot manage IOS access points, which do not require username or password when a user tries to access the CLI.

4.66 "Users All" page doesn't paginate. (Case 429)

Customers with large numbers of users will experience a very unresponsive Users All page.

4.67 User session report does not match user session detail (Case 429)

User Session Report and User Session Detail have slightly different values for MB used. The data for the historical user sessions comes from our internal database bandwidth tables, and the data for the reports comes from RRD files.

4.68 Deleting large number of APs fails intermittently (Case 5087)

Deleting a large number of APs fails sometimes because rrdtool exits unexpectedly. 

4.69 Cisco APs with VLANs display "unknown" SSID On Monitor page and Incorrect SSID On AP List page (Case 5123)

On the AP monitor page AMP displays the SSID as "unknown" for APs configured with VLANs and on the AP List page, the SSID displayed is an incorrect one.

4.70 Client Inactivity Timeout Not Set On Intel/Symbol (Case 5135)

When the user changes the Client inactivity timeout from AMP the SNMP value gets updated correctly on the AP. However, the APs web UI and telnet interface does not get updated with the changed value. 

4.71 Unsupported Security Modes not displayed properly on the AP->Replaces page for Colubris APs (Case 6295)

AMP does not make it obvious to the user that a certain security mode is unsupported on the AP->Replaces page for Colubris APs. For example if the user sets the security mode to 802.1x + WEP which is an unsupported mode the CNMS will show a BAD config with mismatches which are not obvious to the user. The supported security modes on the Colubris APs are 802.1x, WPA and WEP.

4.72 RoamAbout 2000 bandwidth is artificially high (Case 721)

The numbers stored in the MIB are artificially high so the problem is internal to the AP. AirWave has 
reported the problem to Enterasys and working with them to ensure a timely resolution.

4.73 Cisco IOS APs cannot have names with spaces (Case 5322)

Cisco IOS Access Points do not let the user configure the name with spaces in them. This is an issue with the AP implementation.

4.74 Upgrading Firmware and configuration on Cisco IOS APs suffers when network contains latency (Case 4788)

AMP cannot successfully push configurations or upgrade firmware on APs located on networks, which contain latency. Firmware requires latency (one-way) less than 1 second and configuration requires latency less than 2 seconds. Please contact to manage AP on networks where latency exceeds 1 second.

4.75 HTML firmware downgrade from 3.5 to 3.0 fails for Intel 2011b APs (Case 8)

The workaround is to change the SNMP Agent to "Read/Write" using the telnet session
before the html is downgraded.

4.76 AMP silently allows non-VLAN-capable APs in VLAN groups (Case 308)

AMP presently supports 802.1Q VLAN tagging with Cisco VxWorks and IOS APs only. AMP does not report an error if an administrator configures a Group to support VLAN tagging and all APs in that group do not support VLAN tagging.

4.77 Graphs include zeroes for uncollected data (Case 434)

AMP collects data from each AP periodically, as determined by the polling period and the load on the system. When the data collection period grows large, it becomes visible on the graphs. AMP graphs data after the last known point for an AP as zero. On a graph for a single AP or user, this shows up as a sharp "cliff" at the last data collection point. 

When a graph consists of data for many APs for example, the aggregate bandwidth or user count graph for a group, the graph gradually slopes down toward zero with many smaller cliffs, one at the most recent data point for each AP. This effect can mislead the network administrator.

4.78 Proxim AP-2000s with firmware earlier that 2.4.0 dont provide reliable user statistics (Case 435)

AMP provides reliable user statistics for Proxim APs with firmware versions 2.4.0 and above

4.79 Proxim AP-2000 bandwidth spikes

Proxim AP-2000s intermittently spike radio bandwidth from 10-20 Mbps, which results in skewed AP bandwidth graphs. This is an internal AP problem which AirWave is actively working with Proxim to resolve.

4.80 Monitoring users can still make changes (Cases 331, 44, 45, 58)

The "monitoring" user should not be allowed to make any configuration changes on AMP, but AMP still allows them to make some; for example, the monitoring user can acknowledge and delete alerts and un-ignore ignored APs. 

4.81 Usage report data intervals inconsistent (Case 413)

The network usage report contains a table with overall bandwidth and user count for the entire network for time intervals throughout the report period (for one day standard) and also contains graphs at the top displaying the same data graphically. Under some circumstances, the graphed data will have different resolution, usually higher, than the data in the table.

4.82 Dot11counters are not supported on Proxim AP-600a/g and Proxim AP-2000a/g.

These APs do not support dot11 counters information, hence AMP does not display any dot11counter information.

Version History
Revision #:
1 of 1
Last update:
‎06-09-2014 08:52 AM
Updated by:
Labels (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.