Release Notes
© 2006, AirWave Wireless, Inc. All rights reserved. Confidential. Page 5 of 11
4.
Known Issues
4.1 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.2 AMP parsing of ssl certificate broken on Cisco IOS APs running 12.3(7)JA and higher
AMP does not read in the ssl certificate correctly on the Cisco IOS APs running 12.3(7)JA and higher.
4.3 Master Console cannot talk to AMPs on an earlier AMP version
Master Console which is running AMP version 4.1 has errors while talking to AMPs running AMP
versions earlier than 4.1. The workaround is to upgrade all the AMPs to 4.1.
4.4 Inconsistent counts of mismatched APs
AMP displays different counts of mismatched APs if an AMP has some down APs which are stuck in
the verifying state. The workaround for this is to reset the verifying flag for down APs. Please contact
AirWave support for more information making this change.
4.5 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.6 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.7 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.8 “Modify These Devices” from Group->Monitor page does not work as expected (Case 9588)
The entire AP list displayed when “Modify These Devices” is selected from the Group->Monitor page
and any updates to those APs are cancelled. The AMP should be displaying only the APs in that group.
4.9 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.10 Lancom AP reports Client IP as the mac (Case 8130)
Sometimes, the Lancom AP reports the client’s IP address as its radio mac address and hence the AMP
displays the mac address in the ip column.
4.11 RAPIDS->Rogue APs list order not preserved after deleting a rogue AP (Case 9581)
(500 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji