Enterasys APS-3000 Manual de usuario Pagina 7

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 11
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 6
Release Notes
© 2006, AirWave Wireless, Inc. All rights reserved. Confidential. Page 7 of 11
AMP’s 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.22 Rogue Scanning information on the AP->Details 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.23 “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.24 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.25 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.26 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.27 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.28 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.29 Duplicate/extraneous information AP->Detail page for Proxim/Avaya APs (Case 7586)
The AP->Detail page for Proxim/Avaya APs with 2.5.2 and above has some extraneous information.
This will be fixed in a future release.
4.30 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.31 User needs to configure all 4 WEP keys for “Require WEP” on Proxim/Avaya 2.5.2 APs.
Vista de pagina 6
1 2 3 4 5 6 7 8 9 10 11

Comentarios a estos manuales

Sin comentarios