AMP 5.3 Known Issues

AMP 5.3 (all versions) - we've seen a few cases where on an upgrade or on an amp_restore Apache disappears. This is a serious bug that we have been unable to reproduce in house.

Cisco Airespace firmware 5.0 and also 4.2.112 :

- Mismatches with the trap controls. Looks like the Cisco added another trap control for the Security traps and hence the mismatch. - Syslog server format changed.

5.3.1: upgrade path from does not work due to dependency on an old postgres version. This issue is resolved for 5.3.2.

The following are taken from the AMP 5.3 Release Notes, which are downloadable from our Docs & Info page:

4. Known Issues4.1 APs reported down on Meru firmware 3.5AMP does not support firmware 3.5 on Meru controllers. All thin APs connected to controllers running this version are reported down on the AMP. The new firmware will be supported in the next release 6.0.4.2 Aruba controllers running the 3.1.1 firmware might have issues displaying clients in AMP4.3 Reversing TACACS+ servers on AMP creates more than required TACACS+ serversReversing a controllers config that uses the same TACACS+ server for more than one of the AAA functions will have to enter the same AAA server secret multiple times. 4.4 Mismatched header missing when there are mismatched APsThe mismatched header is missing from the UI when there are some mismatched APs on the AMP for monitoring users. 4.5 Deleting a managed device with discovery events causes some errorsDeleting a discovering AP will remove links to some other discovering APs in the rogue report.4.6 Rogue_detail.xml can filter with radio_macPreviously all rogues were included in the rogue_detail.xml when filtered by radio_mac. 4.7 Not all IDS Traps pages are sortableThe user cannot change the sort order on the IDS Attack Detail list.4.8 TACACS+ Priority configuration is not pushed to Airespace controllers.The user can set the Management priority to RADIUS or TACACS+, but this setting is not pushed to the controller.4.9 Scheduled Changes deleted on upgradesOn upgrade to 5.2 all changes that have been scheduled to run in the next 24 hours will be deleted. This includes changes to APs/Devices, Groups etc.4.10 CDP discovers same Cisco Vxworks AP multiple timesAMP discovers the same Cisco Vxworks AP (some of the models) multiple times using CDP causing multiple records to be displayed for the same AP on the AP->New page. Please contact support if you are seeing this issue.4.11 Moving/deleting large number of APs does not completeMoving/deleting a large number of APs from Modify These Devices does not complete sometimes.4.12 AMP not enabling Transmit Power Control on the AP4000sAMP does not enable the Transmit Power Control on the Proxim APs, AP4000, and AP700 etc. 4.13 Proxim WiMax IssuesAMP does not handle the condition where the combined number of desired and actual PIRs are greater than 16. Also, AMPs UI does not prevent users from adding more than 16 allowed PIRs. 4.14 Some dot11counters have negative valuesSome of the dot11counter graphs display negative values for the counters, specifically the average values.4.15 Static IP Provisioning with IOS APs has some issuesCisco 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.16 Known AMC/ QuickView/Visual RF IssuesAMP 5.3 (all versions) - we've seen a few cases where on an upgrade or on an amp_restore Apache disappears. This is a serious bug that we have been unable to reproduce in house.

Cisco Airespace firmware 5.0 and also 4.2.112 :

- Mismatches with the trap controls. Looks like the Cisco added another trap control for the Security traps and hence the mismatch. - Syslog server format changed.

5.3.1: upgrade path from does not work due to dependency on an old postgres version. This issue is resolved for 5.3.2.

The following are taken from the AMP 5.3 Release Notes, which are downloadable from our Docs & Info page:

4. Known Issues4.1 APs reported down on Meru firmware 3.5AMP does not support firmware 3.5 on Meru controllers. All thin APs connected to controllers running this version are reported down on the AMP. The new firmware will be supported in the next release 6.0.4.2 Aruba controllers running the 3.1.1 firmware might have issues displaying clients in AMP4.3 Reversing TACACS+ servers on AMP creates more than required TACACS+ serversReversing a controllers config that uses the same TACACS+ server for more than one of the AAA functions will have to enter the same AAA server secret multiple times. 4.4 Mismatched header missing when there are mismatched APsThe mismatched header is missing from the UI when there are some mismatched APs on the AMP for monitoring users. 4.5 Deleting a managed device with discovery events causes some errorsDeleting a discovering AP will remove links to some other discovering APs in the rogue report.4.6 Rogue_detail.xml can filter with radio_macPreviously all rogues were included in the rogue_detail.xml when filtered by radio_mac. 4.7 Not all IDS Traps pages are sortableThe user cannot change the sort order on the IDS Attack Detail list.4.8 TACACS+ Priority configuration is not pushed to Airespace controllers.The user can set the Management priority to RADIUS or TACACS+, but this setting is not pushed to the controller.4.9 Scheduled Changes deleted on upgradesOn upgrade to 5.2 all changes that have been scheduled to run in the next 24 hours will be deleted. This includes changes to APs/Devices, Groups etc.4.10 CDP discovers same Cisco Vxworks AP multiple timesAMP discovers the same Cisco Vxworks AP (some of the models) multiple times using CDP causing multiple records to be displayed for the same AP on the AP->New page. Please contact support if you are seeing this issue.4.11 Moving/deleting large number of APs does not completeMoving/deleting a large number of APs from Modify These Devices does not complete sometimes.4.12 AMP not enabling Transmit Power Control on the AP4000sAMP does not enable the Transmit Power Control on the Proxim APs, AP4000, and AP700 etc. 4.13 Proxim WiMax IssuesAMP does not handle the condition where the combined number of desired and actual PIRs are greater than 16. Also, AMPs UI does not prevent users from adding more than 16 allowed PIRs. 4.14 Some dot11counters have negative valuesSome of the dot11counter graphs display negative values for the counters, specifically the average values.4.15 Static IP Provisioning with IOS APs has some issuesCisco 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.16 Known AMC/ QuickView/Visual RF Issues