Software Release Notes 5.7.8 Build 19 Date: 4/6/06 · 2007-01-23 · Mobile Manager 5.7.8 Release...

Software Release Notes

Mobile Manager 5.7.8 Build 19

Release Date: 4/6/06

Mobile Manager 5.7.8 Release Notes, v. 01

Mobile Manager 5.7.8 Release Notes, v. 01 4/6/2006 2 of 27

Table of Contents

Table of Contents.............................................. 2 List of Tables................................................. 3

Introduction .............................................................................................................................. 4 New Additions and Enhancements ...................................................................................... 4 Important Notes about This Release..................................................................................... 4 Licensing.................................................................................................................................... 4 General Notes ........................................................................................................................... 4

AVAYA Support Updates.......................................... 5 Firmware Support.................................................................................................................... 5 Known Firmware Issues ......................................................................................................... 6

Cisco VxWorks Support Updates.................................. 7 Firmware Support.................................................................................................................... 7 Known Firmware Issues ......................................................................................................... 8

Cisco IOS Support Updates...................................... 9 Firmware Support.................................................................................................................... 9 Known Firmware Issues ....................................................................................................... 10

Dell Support Updates.......................................... 11 Firmware Support.................................................................................................................. 11 Known Firmware Issues ....................................................................................................... 11

HP Support Updates............................................ 12 Firmware Support.................................................................................................................. 12 Known Firmware Issues ....................................................................................................... 12

Proxim Support Updates........................................ 13 Firmware Support.................................................................................................................. 13 Known Firmware Issues ....................................................................................................... 14

Symbol Support Updates........................................ 16 Firmware Support.................................................................................................................. 16 Known Firmware Issues ....................................................................................................... 17

SYSTIMAX Support Updates...................................... 19 Firmware Support.................................................................................................................. 19 Known Firmware Issues ....................................................................................................... 20

Installing Mobile Manager 5.7.8............................... 21 Hardware Requirements ...................................................................................................... 21 Software Requirements ......................................................................................................... 21 First‐time Installations........................................................................................................... 22 Upgrading from Mobile Manager 5.7.7 to 5.7.8................................................................ 22 Upgrading from Mobile Manager 5.7.6 to 5.7.8................................................................ 22 Recreating Proxim AP Profiles after Upgrading from MM 5.7.4 or earlier versions.................................................................................................Error! Bookmark not defined. Upgrading from Previous Versions of Mobile Manager (5.3 ‐ 5.7.5) ............................ 23

Resolved Issues............................................... 23 Known Issues.................................................. 24 Documentation Updates......................................... 27 Version History............................................... 27



List of Tables

Table 1. Firmware Supported in Full Mode for AVAYA Access Points...... 5 Table 2. Firmware Supported in Compatibility Mode for AVAYA

Access Points..................................................... 5 Table 3. Known Firmware Issues for AVAYA Access Points................ 6 Table 4. Firmware Supported in Full Mode for Cisco VxWorks

Access Points..................................................... 7 Table 5. Firmware Supported in Compatibility Mode for Cisco

VxWorks Access Points............................................. 7 Table 6. Known Firmware Issues for Cisco VxWorks Access Points........ 8 Table 7. Firmware Supported in Full Mode for Cisco IOS Access

Points............................................................ 9 Table 8. Firmware Supported in Compatibility Mode for Cisco IOS

Access Points..................................................... 9 Table 9. Firmware Issues for Cisco IOS Access Points................. 10 Table 10. Firmware Supported in Full Mode for Dell Access Points..... 11 Table 11. Firmware Supported in Compatibility Mode for Dell

Access Points.................................................... 11 Table 12. Known Firmware Issues for Dell Access Points............... 11 Table 13. Firmware Supported in Full Mode for HP Access Points....... 12 Table 14. Firmware Supported in Compatibility Mode for HP Access

Point............................................................ 12 Table 15. Known Firmware Issues for HP Access Points................. 12 Table 16. WEP Support for Proxim Access Points with firmware

versions prior to 2.4.x.......................................... 13 Table 17. Firmware Supported in Full Mode for Proxim Access

Points........................................................... 13 Table 18. Firmware Supported in Compatibility Mode for Proxim

Access Points.................................................... 14 Table 19. Known Firmware Issues for Proxim Access Points............. 14 Table 20. Firmware Supported in Full Mode for Symbol Access

Points and Wireless Switches..................................... 16 Table 21. Firmware Supported in Compatibility Mode for Symbol

Access Points.................................................... 16 Table 22. Known Firmware Issues for Symbol Access Points............. 17 Table 23. Firmware Supported in Full Mode for SYSTIMAX Access

Points........................................................... 19 Table 24. Known Firmware Issues for SYSTIMAX Access Points........... 20 Table 25. Known Issues in Mobile Manager 5.7.8....................... 24



Introduction

Wavelink Mobile Manager allows you to deploy, configure and manage wireless LAN components.

This document describes new features, updates, and resolved and known issues for Mobile Manager Release 5.7.8. It also provides important information about installing and using this release.

Note: It is highly recommended that you review the contents of this document before you install Mobile Manager 5.7.8. If you are upgrading from an earlier Mobile Manager release, review the section Installing Mobile Manager 5.7.8 before you begin the upgrade.

In addition, if you are not familiar with Mobile Manager, it is recommended that you also review the release notes for Mobile Manager 5.7.0, 5.7.1, 5.7.2, 5.7.3, 5.7.4, 5.7.5, 5.7.6 and 5.7.7.

New Additions and Enhancements

Mobile Manager 5.7.8 contains the following updates:

• Symbol firmware 1.4.3.0‐012R and 2.0.0.0‐34r support for the WS5000 and WS5100 hardware.

• Changes to address field issues.

Important Notes about This Release

The following is important information about this release of Mobile Manager:

Licensing

• Customers who have Mobile Manager Maintenance licenses can upgrade to Mobile Manager 5.7.8 without any licensing changes. Customers who have a Base license prior to 5.7 will need to obtain a Mobile Manager 5.7 Base or Maintenance license.

General Note

• During the migration process, the migration tool may indicate that more rows were migrated than the original number. This is normal, as Mobile Manager



may have received some statistical data during the migration progress that it had to add to the database.

• Mobile Manager will not install to a system that is already hosting a PostGreSQL database. Likewise, you will not be able to upgrade a previous version of Mobile Manager if the system is already hosting a PostGreSQL database.

• The executable you should launch to install the application is mm_5780.exe

AVAYA Support

The following information applies to AVAYA support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for AVAYA access points.

Note: Firmware versions that appear in bold are new in this release of Mobile Manager.

Full-mode Support Table 1. Firmware Supported in Full Mode for AVAYA Access Points

Access Point Type Firmware Version Supported in Full Mode

AVAYA AP-3 AVAYA AP-4 AVAYA AP-5 AVAYA AP-6

2.4.5 2.4.11 2.5.2

AVAYA AP-8 2.4.11 2.5.2

Firmware Supported in Compatibility Mode for AVAYA Access Points

Table 2. Firmware Supported in Compatibility Mode for AVAYA Access Points

Access Point Type Firmware range supported in Compatibility Mode

Firmware version used if match found in range

Firmware version used if no match found in range

2.0.0 to 2.3.1 2.2.2 2.3.3 AVAYA AP-3 AVAYA AP-4 AVAYA AP-5 AVAYA AP-6

2.4.1 to 2.5.0 2.4.5 2.3.3



Known Firmware Issues

The following table lists the known AVAYA firmware-related issues encountered in this Mobile Manager release. Table 3. Known Firmware Issues for AVAYA Access Points

Access Point Firmware Version Issue No.

2.3.3 Mobile device status does not show if the MU is Active. 10261

2.5.2 No known issues N/A AVAYA AP-4 AVAYA AP-5 AVAYA AP-6

All firmware versions (except 2.4.11 and 2.5.2)

Proxim 802.11a radio: Enabling Turbo mode results in the Frequency Channel being automatically selected (Auto Channel Select)

30049

2.3.3 Mobile device status does not show if the MU is Active. 10261

2.4.11 Intermittent failure of Proxim AP to display all VLAN properties. A workaround to this issue is to enable and disable the VLAN again.

30828

AVAYA AP-3

All firmware versions

APs on a production network without runtime firmware loaded will cause the following error to be reported on the serial interface of other APs with runtime firmware loaded: interrupt: ERROR: dp0 - rxnobuf interrupt! This is not a critical error because the affected APs with runtime firmware continue to operate while the condition is occurring. To correct the problem, remove all APs without runtime firmware from the production network.

N/A

2.4.11 Intermittent failure of Proxim AP to display all VLAN properties. A workaround to this issue is to enable and disable the VLAN again.

30828 AVAYA AP-8

2.5.2 No known issues N/A



Cisco VxWorks Support

The following information applies to Cisco VxWorks support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for Cisco VxWorks access points.


Full-mode Support Table 4. Firmware Supported in Full Mode for Cisco VxWorks Access Points


Cisco Aironet AP 340/350

11.10T1 11.23T 12.01T1 12.02T1 12.03T 12.04 12.05 (firmware patch – available upon request)

Cisco 350 BR

11.10T1 11.23T 12.01T 12.02T1 12.03T 12.04

Cisco Aironet AP 1200

11.42T 11.56 12.01T1 12.02T1 12.03T 12.04 12.05 (firmware patch – available upon request)

Compatibility-mode Support Table 5. Firmware Supported in Compatibility Mode for Cisco VxWorks Access Points




11.10 to 11.99 11.23 Cisco Aironet AP340/350 12.01T1 to 12.99 12.01T1

11.23T

11.10 to 11.99 11.23 Cisco 350 BR

12.01T1 to 12.99 12.01T1 11.23T

11.42 to 11.99 11.56 Cisco Aironet AP 1200

12.01T1 to 12.99 12.01T1 11.56




The following table lists the known Cisco VxWorks firmware related issues encountered in this Mobile Manager release.

Table 6. Known Firmware Issues for Cisco VxWorks Access Points


11.23T MM is not able to discover access points that are behind a switch and not IP-reachable. N/A

12.01T1 MM is not able to discover access points that are behind a switch and not IP-reachable. N/A

12.02T1 Same as 12.01T1 N/A

12.03T Cannot set Domain Name Server 3. 10217

12.04 No known issues.

Cisco 340/350 AP


MM is not able to discover access points that are behind a switch and not IP-reachable. N/A

11.56 When an AP’s firmware is updated, it goes into READY state, but there is no alert showing firmware download has completed. N/A

Same as version 11.56 N/A 12.01T1

After the Radio is turned off, enabling Radio fails to bring Radio on until the AP is reset.

20225

Same as 12.01T1 N/A 12.02T1

Putting an AP into a profile causes console warnings about radio being tampered with. 10046

12.03T Cannot set Domain Name Server 3. 10217

12.04 No known issues.

Cisco 1200 AP


MM is not able to discover access points that are behind a switch and not IP-reachable. N/A

Cisco 350 BR Same as 350 AP Same as Cisco AP350 access point N/A



Cisco IOS Support

The following information applies to Cisco IOS support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for Cisco IOS access points.

Note: Bolded firmware versions are new in this release of Mobile Manager.

Full-mode Support Table 7. Firmware Supported in Full Mode for Cisco IOS Access Points


Cisco Aironet AP 1130 12.3(2)JA 12.3(2)JA2

12.3(4)JA 12.3 (7)JA

Cisco Aironet AP 1100

12.2(11)JA1 12.2(13)JA1 12.2(13)JA3 12.2(15)JA

12.3(2)JA 12.3(2)JA2 12.3(4)JA 12.3 (7)JA

Cisco Aironet AP 1200 IOS

12.2(11)JA11 12.2(13)JA1 12.2(13)JA3 12.2(13)JA4 12.2(15)JA

12.3(2)JA 12.3(2)JA2 12.3(4)JA 12.3 (7)JA

Cisco Aironet AP 350 IOS

12.2(13)JA12 12.2(13)JA2 12.2(15)JA 12.3(2)JA

12.3(2)JA2 12.3(4)JA 12.3 (7)JA

Compatibility-mode Support Table 8. Firmware Supported in Compatibility Mode for Cisco IOS Access Points




Cisco AP 1100 N/A N/A 12.2(11)JA1

Cisco AP 1200 IOS N/A N/A 12.2(11)JA1

Cisco AP 350 IOS N/A N/A 12.2(13)JA1

Cisco AP 1130 N/A N/A 12.3(2)JA

1 This firmware version is specifically designed to upgrade Cisco 1200 access points from VxWorks to IOS 2 This firmware version is specifically designed to upgrade Cisco 350 access points from VxWorks to IOS.




The following table lists the known Cisco IOS firmware related issues encountered in this Mobile Manager release.

Table 9. Firmware Issues for Cisco IOS Access Points


MM reports the firmware file is being downloaded twice when updating an AP. 10009

12.2(11)JA1 Cisco IOS VLAN WKR - AP becomes IP unreachable after WKR has been running on VLANs for a long time. A hardware reset is then required.

20280

Same as 12.2(11)JA1 N/A 12.2(13)JA1

Cannot turn Broadcast SSID back on after turning is off. Restore to Factory Defaults to turn the setting back ON. 30092

12.2(15)JA The transmit power setting cannot be set to Max. This includes G Radio CCK transmit power and OFDM transmit power.

30885

12.3(2)JA No known issues N/A

Cisco 1100

12.3-4JA Reset Factory will remove all the SSIDs from the AP causing AP Radio to go down. 31977

12.2(11)JA1 Same as Cisco 1100 N/A

12.2(15)JA Same as Cisco 1100 N/A

12.3(2)JA No known issues N/A Cisco 1200 IOS

12.3-4JA Same as Cisco 1100 31977

12.2(13)JA1 Same as Cisco 1100 N/A

12.2(15)JA Same as Cisco 1100 N/A

12.3(2)JA No known issues N/A Cisco 350 IOS

12.3-4JA Same as Cisco 1100 31977

12.3(2)JA No known issues N/A Cisco 1130

12.3(2)JA Same as Cisco 1100 31977



Dell Support

The following information applies to Dell support within Mobile Manager 5.7.8.

1. Dell access points do not support VLANs; however, within the Advanced Properties dialog box of the Mobile Manager Administrator, the VLAN properties appear as active and configurable. According to Dell, these properties must not be configured.

2. Dell access points currently only support firmware version 2.2.2. If the firmware on a Dell access point is updated to a higher version, it behaves as a Proxim access point.

Firmware Support

This section lists the supported firmware for Dell access points.


Full-mode Support Table 10. Firmware Supported in Full Mode for Dell Access Points


Dell True Mobile 1170 2.2.2

Compatibility-mode Support Table 11. Firmware Supported in Compatibility Mode for Dell Access Points




Dell True Mobile 1170 2.2.2 to 2.3.3 2.2.2 2.2.2


The following table lists the known Dell firmware related issues encountered in this Mobile Manager release.

Table 12. Known Firmware Issues for Dell Access Points


Dell True Mobile 1170 2.2.2 Mobile device status does not show if MU is Active. 10261



HP Support Updates

The following information applies to HP support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for HP access points.


Full-mode Support Table 13. Firmware Supported in Full Mode for HP Access Points


HP ProCurve 520wl 2.1.2 2.4.5

Compatibility-mode Support Table 14. Firmware Supported in Compatibility Mode for HP Access Point




HP ProCurve 520wl 2.1.2 to 2.3.0 2.1.2 2.1.2


The following table lists the known HP firmware related issues encountered in this Mobile Manager release.

Table 15. Known Firmware Issues for HP Access Points


Incorrect VLAN settings can make access points unusable. 10258 HP ProCurve 520wl 2.1.2

Mobile device status does not show if MU is Active. 10261



Proxim Support Updates

The information in this section applies to Proxim support within Mobile Manager 5.7.8.

The following table lists the WEP capabilities that are supported for Proxim access points, based on the type of wireless card installed in the access point.

Table 16. WEP Support for Proxim Access Points with firmware versions prior to 2.4.x

802.11 b-only 802.11 b/g card Gold Silver Gold Feature Supports 40 bit & 128 bit

WEP key size

Supports 40 bit WEP key size

Supports 40 bit, 128bit, and 152 bit WEP key size

Observed Behavior

Functions normally Functions normally See Table 13.

Firmware Support

This section lists the supported firmware for Proxim access points.


Table 17. Firmware Supported in Full Mode for Proxim Access Points


Proxim AP-600

2.2.2 2.3.1 2.3.3 2.4.43

2.4.5 2.4.11 2.5.2 2.5.3

Proxim AP-2000

2.2.24 2.3.1 2.3.3 2.4.4Error! Bookmark not

defined.

2.4.5 2.4.11 2.5.2 2.5.3

Proxim AP-4000 2.4.10 2.4.11 2.5.2

2.6.0 3.1.0

Proxim AP-700 2.5.2 2.6.0 3.1.0

Proxim AP-4900 3.1.0

Proxim AP-4000M 3.1.0

3 Please note Issue #30007 4 For Proxim AP-2000, the following PC cards are supported: 802.11b-only Gold PC card, 802.11b-only Silver PC card, 802.11b/g upgrade kit, 5GHz upgrade kit, and 802.11a upgrade kit.



Compatibility-mode Support Table 18. Firmware Supported in Compatibility Mode for Proxim Access Points




2.2.2 to 2.3.0 2.2.2

2.3.1 to 2.3.9 2.3.1

2.4.0 to 2.4.10 2.4.4

2.4.11 to 2.4.99 2.4.11

Proxim AP-600

2.5.1 to 2.6.99 2.5.3

2.2.2

2.2.2 to 2.3.0 2.2.2

2.3.1 to 2.3.9 2.3.1

2.4.0 to 2.4.10 2.4.4

2.4.11 to 2.4.99 2.4.11

Proxim AP-2000

2.5.1 to 2.6.99 2.5.3

2.2.2

Proxim AP-4000 2.4.11 to 2.4.99 2.4.11 2.4.10

Proxim AP-700 N/A N/A 2.5.2


The following table lists the known Proxim firmware related issues encountered in this release of Mobile Manager. Refer to the section Known Issues in this document, for more details and possible workarounds for these issues.

Table 19. Known Firmware Issues for Proxim Access Points


Mobile device status does not show if the MU is Active. 10261

Firmware update sometimes results in the AP not having a correct firmware image, making the AP unavailable. 20303 2.2.2

WEP issues with Proxim 802.11b / g. 20240


Proxim AP-600

2.3.1, 2.3.3 Mobile unit is able to communicate with AP using an “old” WEP transmission key instead of current Transmit Key. Happens on 802.11b/g only; 802.11b works correctly.

20232



2.4.4 Proxim AP 600 with FW version 2.4.4 cannot be downgraded to FW 2.3.3 or earlier firmware versions without executing a forced reload procedure.

30007


2.5.3 Transmit Power Level is not available on the B-only Radio AP. 31988


(except 2.4.11)

Proxim 802.11a: Enabling Turbo mode results in the Frequency Channel being automatically selected (Auto Channel Select) 30049



N/A


Firmware update sometimes results in the AP not having a correct firmware image, making the AP unavailable. 20303

WEP issues with Proxim 802.11b / g. 20240 2.2.2

Proxim 2000: Failure to detect 802.11A radio card 30070

2.3.1, 2.3.3 Mobile device status does not show if the MU is Active. 10261

2.4.10, 2.4.11 Intermittent failure of Proxim AP to display all VLAN properties. A workaround to this issue is to enable and disable the VLAN again. 30828

Proxim AP 2000 with FW version 2.4.4 cannot be downgraded to FW 2.1.2 or earlier firmware version without first executing a force reloads procedure.

30007

2.4.4 Proxim AP-2000: Error received when setting Rogue AP Scan Interface to include an 802.11B card 30219

2.5.2 No Known issues. N/A

2.5.3 Transmit Power Level is not available on the B-only Radio AP. 31988

Proxim AP-2000



N/A

2.4.10, 2.4.11 Intermittent failure of Proxim AP to display all VLAN properties. A workaround to this issue is to enable and disable the VLAN again.

30828

2.5.2 No known issues N/A Proxim AP-4000


2.5.2 No known issues N/A Proxim AP-700




Symbol Support

The following information applies to Symbol support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for Symbol access points.

Note: Bolded firmware versions are new in this release of Mobile Manager.

Full-mode Support Table 20. Firmware Supported in Full Mode for Symbol Access Points and Wireless Switches

Access Point / Wireless Switch Type Firmware Version Supported in Full Mode Symbol 11 MB T1 AP4111 and Symbol 11 MB T2 AP4121

2.51-23 2.52-13

2.70-06 2.70-12

Symbol 11 MB T3 AP4131 3.50-18 3.50-26 3.70-46a

3.70-77 3.92-215 3.9.3-00

Symbol 2 MB AP3020, 3021 4.02-19

Symbol WS 5000 Wireless Switch 1.2.5.0-022R (w/1.2.5.0-022R applet patch)6

1.4.1.0-014R

Symbol WS 5100 Wireless Switch 1.4.1.0-014R 1.4.3.0-21R 2.0.0.0-034R

Symbol WS 2000 Wireless Switch 1.0.10.8 1.5.0.0-216r 2.0.0-36R

Compatibility-mode Support Table 21. Firmware Supported in Compatibility Mode for Symbol Access Points




2.51-00 to 2.52-99 2.52-13 Symbol 11 MB T1 AP4111 and Symbol 11 MB T2 AP4121

2.70-00 to 2.70-99 2.70-06 2.52-13

3.50-00 to 3.50-99 3.50-18

3.70-46a to 3.70-76 3.70-46a

3.70-77 to 3.70-99 3.70-77 Symbol 11 MB T3 AP4131

3.92-21 3.92-21

3.50-18

Symbol 2MB AP3020 and Symbol 2MB AP3021

4.02-19 to 4.02-99 4.02-19 4.02-19

5 See the section on the Symbol AP 4131 under the Important Notes section of the document on page 6 for information on limitations. 6 The patch is supported when Mobile Manager installs the patch automatically during a firmware upgrade.



Symbol WS 5000 1.4.0.0-000 to 1.4.1.0-013R 1.4.1.0-014R None

Symbol WS 5100 1.4.0.0-000 to 1.4.1.0-013R 1.4.1.0-014R None


The following table lists the known Symbol firmware related issues encountered in this Mobile Manager release.

Table 22. Known Firmware Issues for Symbol Access Points


2.52-13 No known issues. N/A

2.51-23 No known issues. N/A

Mobile Manager is unable to set the RW Community Name. 4612

Enabling VLACL makes the access point unmanageable – when the ACL Trap is enabled, the community name is corrupted. Consequently, profile settings for "Advanced SNMP and Radio" cannot be configured.

4516

With T2 and T3 access points, if the read-only and read/write community names are the same, SNMP Set operation returns a "No such name" error.

4669

Symbol 11MB T1 AP 4111 And Symbol 11MB T2 AP 4121 2.70-06

The factory default for the Maximum Associated Device Trigger property exceeds the acceptable range for the property. You must change this property to a valid value of 1-127 to avoid related alerts.

30823

A reset is required for changes to the Access Control System settings to be effective. N/A

Mobile Manager can read and write only up to 127 entries in the access point’s ACL. 4653 3.50-18,

3.50-26 If both the read-only and read/write community names are the same for an access point, SNMP Set operations returns a “No Such Name” error.

4669

Global WEP Key SNMP Sets are unstable and cannot be set consistently. Mobile Manager is unable to set 40-bit or 128-bit WEP keys on the AP

4302

VLACL fails to add associated mobile device MAC address when access point is connected to a Cisco switch. When the access point is rebooted, mobile device traps are not sent to the AP- the port on the Cisco switch re-initializes itself and traps are lost.

4424

Enabling VLAN Trunking causes the access point to become IP unreachable. 4546

Mobile Manager can read and write only up to 127 entries in the access point’s ACL. 4653

Symbol 11MB T3 AP 4131

3.70-46a

If the read-only and read/write community names are the same for an access point, the SNMP Set operations returns a “No Such Name” error.

4669



3.70-77 WEP keys are not preserved when updating to firmware version 3.70-77. 4726

WEP keys are not preserved when updating to firmware version 3.70-77. 4726

3.92-21 Firmware issues for FW versions 3.92-21 limit the management of VLANs using SNMP. While VLAN 1 can be managed, VLANs 2 and higher do not accept VLAN settings nor static WEP keys. These settings can be managed only through HTTP or Telnet.

N/A

Symbol 2MB AP 3020 4.02-19 No known issues. N/A

SNMP set error occurs when Mobile Manager tries to change Access Port properties with default blank values.

30318

Cannot remove an Access Port from an Access Port policy.

30319

The default power setting (30mW) cannot be set on a Switch Policy. Use a value other than 30mW or upgrade for firmware 1.2.0.39.

30434

1.1.4.30 SP1, 1.1.430f

Access Port policy is not reassigned to a wireless switch that has been deleted and rediscovered.

30350

For AP 200 Access Ports, when you assign a profile to the switch and the profile settings are unchanged from their defaults, the radio A and radio B ports of the Access Port are not configured with the Default Access Port policy. MM correctly reports the error.

31346

Kerberos Authentication Name property of WLAN policy is a read-write property, but it always takes the value of the ESSID of the WLAN policy and cannot be changed on the switch.

31404

An SNMP Set Unknown Errors occurs when trying to add an ACL entry to the ACL policy on the switch. Re-query the switch and any missing ACL entries will be applied to the policy.

31442

Cannot configure FH-specific access port properties via SNMP.

31519

Cannot set transmit rate value to 5.5 for 802.11b Access Port.

31667

1.2.0.39f 1.2.0.39o

Mobile Manager cannot set properties on the switch if the following conditions are all true: (1) the SNMP RO and RW community names are set to the same value (e.g., public), and (2) the SNMP RO community name is configured before the SNMP RW community name, and (3) the values are set using some method other than Mobile Manager.

31680

Mobile Manager cannot set properties on the switch if the following conditions are all true: (1) the SNMP RO and RW community names are set to the same value (e.g., public), and (2) the SNMP RO community name is configured before the SNMP RW community name, and (3) the values are set using some method other than Mobile Manager.

31680

Symbol WS 5000

1.2.5.0-022R

The WS 5000 does not support the disabling of VLAN and 802.11q trunking through SNMP once they are enabled. Consequently, you

31792



must disable these features through the Telnet or Web interface.

1.4.1.0-014R

Cannot delete AP-300 access port. 31973

1.4.3.0-21R none

2.0.0.0-034R

A Symbol WS 5100 may appear as a WS 5000 when upgraded to the 2.0 firmware. After upgrading, if you do a “show version” command at the switch’s console, the version shows up as a 5000. Therefore, when you delete and then rediscover the switch in MM, you’ll see that it now shows up as a WS 5000. When downgrading the firmware back to 1.4.1, the switch will usually show up again as a 5100. It is not clear at this time is factory-shipped WS 5100s running 2.0 have this problem This issue will be addressed by the 2.1 firmware release.

32134

The MU access control and AP adoption lists are ranges of MAC addresses (start - end). However, the switch shows the same value for the end address as the start address no matter whether the values are set differently.

31518

MM reports the incorrect state of one or more Access Ports after another Access Port is unplugged from the switch. (The incorrect state might be offline for Access Ports that are online or vice versa.) Power cycle the switch to resolve this issue.

31370

1.0.10.8

The wireless switch (and its Web interface) report the 256-Key Settings property (MM name) under the Encryption folder as the 128-Bit Key Settings. MM is correct and no workaround is required; all key settings are 256-bit.

31617 Symbol WS 2000

1.5.0.0-216r

MM reports the incorrect state of one or more Access Ports after another Access Port is unplugged from the switch. (The incorrect state might be offline for Access Ports that are online or vice versa.) Power cycle the switch to resolve issue.

31370

SYSTIMAX Support

The following information applies to SYSTIMAX support within Mobile Manager 5.7.8.

Firmware Support

This section lists the supported firmware for SYSTIMAX access points.


Full-mode Support Table 23. Firmware Supported in Full Mode for SYSTIMAX Access Points




SYSTIMAX AirSPEED AP541 2.5.2 2.6.0

SYSTIMAX AirSPEED AP542 2.4.11 2.5.2 2.6.0


The following table lists the known SYSTIMAX firmware‐related issues encountered in this Mobile Manager release.

Table 24. Known Firmware Issues for SYSTIMAX Access Points


AP541 2.5.2 No known issues N/A

2.4.11 Intermittent failure of the SYSTIMAX AP to display all VLAN properties. A workaround to this issue is to enable and disable the VLAN again.

30828 AP542




Installing Mobile Manager 5.7.8

This section guides you through the basic installation process for this release. Refer to the Mobile Manager User’s Guide for the detailed installation process.

Mobile Manager includes an internal database (PostgreSQL) which is used for internal data management. It is recommended that you install Mobile Manager on a system that does not include another installation of this database. The installation cannot complete if another instance of this PostgreSQL database exists on the system.

Before installing Mobile Manager 5.7.8 ensure that it will be installed on an NTFS partition. PostgreSQL will not install on a FAT or FAT32 partition.

If upgrading, the Mobile Manager installation will give you the option to migrate your existing statistics database data. If you do not care about the contents of the statistics database for dashboard and reporting you can uncheck the “Migrate” checkbox during installation. A fully populated statistics database can add more than 10 minutes to the upgrade installation time.

Once upgraded it is not possible to recover the data in the Sybase database as the entire Sybase subsystem will be removed. If you want to ensure that this data is retained, consult the Mobile Manager documentation on how to backup your database.

Hardware Requirements

See the Mobile Manager Users Guide for hardware requirements.

Software Requirements

Mobile Manager runs on the following operating systems:

• Windows XP SP1, SP2

• Windows 2000/Server SP2, SP3, SP4

• Windows 2003 Server

Note: Mobile Manager 5.7.8 has not been tested on Windows 2003 Enterprise version. Windows NT 4.0 is not supported.



First-time Installations

To install Mobile Manager 5.7.8 for the first time:

1. If you have not already done so, review the Mobile Manager Quick Start Guide, or the Installation Chapter of the Mobile Manager Users Guide to ensure that all pre‐installation steps have been completed.

2. Close the Windows Service control panel. This is essential for a successful installation.

3. Double‐click on the Mobile Manager Software file (mm_5780.exe) and follow the instructions.

For Windows XP SP2, when the Agent attempts to start at the end of the installation program, a Windows Security Alert dialog box appears to inform you that Windows Firewall has blocked some features of the program. Click Unblock.

Upgrading from Mobile Manager 5.7.7 to 5.7.8

1. Close the Windows Service control panel and Mobile Manager Administrator. This is essential for a successful upgrade.


3. When upgrading from a previous MM installation, you will not be prompted for a new IP address for the Mobile Manager agent. If you wish to change the current IP address, select the Change Adapter option on the Start menu.

4. Follow the steps in the next section to recreate Proxim access point profiles. Note: you will not lose any existing Proxim access point settings.

Upgrading from Mobile Manager 5.7.6 to 5.7.8

1. Close the Windows Service control panel and Mobile Manager Administrator. This is essential for a successful upgrade.


3. When upgrading from a previous MM installation, you will not be prompted for a new IP address for the Mobile Manager agent. If you wish to change the current IP address, select the Change Adapter option on the Start menu.

4. Follow the steps in the next section to recreate Proxim access point profiles. Note: you will not lose any existing Proxim access point settings.



Upgrading from Previous Versions of Mobile Manager (5.3 - 5.7.5)

For instructions on upgrading from Mobile Manager Version 5.3.x, 5.4.x, or 5.5.x, 5.6.x, 5.7.1‐5.7.5 contact Wavelink Support.

Resolved Issues

The following issues were addressed with this release:

• Fixed issue with re-ordering of EAP servers for Cisco IOS APs

• Fixed issue with VLACL and Symbol 4131 APs where certain mobile devices would not be able to register with the AP

• Improved interface detection on the Symbol 4131 APs to help prevent SNMP

Get failures

• Site Survey tool now works with Cisco IOS APs with 802.11g Radios

• Fixed issue with database where errors would occur on system Startup

• Optimized connection handling on Cisco IOS APs to not reconnect for each element of a query, which improves bandwidth usage and load on AP

• Fixed issue where "all traps enabled" was not supported properly on Symbol

4131 APs

• Enhanced MM logging functionality to record VLACL events and licensing AP events

• postgresWL user (for PostGreSQL database) is now added to the Users group

during the installation of MM

• Fixed bug that allowed you to proceed with the install when the installation destination was on a FAT32 partition (bug #32121)

• Fixed issue with WS5000 misidentifying the AP300 radio type (bug #32067)

• Fixed Load Balancing issue that caused SNMP Get errors on Proxim APs (bug

#32128)



Known Issues

The following table lists the known issues for Mobile Manager 5.7.8.

Table 25. Known Issues in Mobile Manager 5.7.8

No. Summary Workaround

30162 [Admin: AP Name]: The maximum length for an AP name should be 63 characters. However, a longer AP name can be entered and displayed in the Administrator and on the AP (through Web Interface), but only 63 characters are stored in the Agent database.

Shorten the name to 63 characters or less.

4647 [Agent] When you change the working directory for log files, you must restart the Agent.

No workaround available, you must restart the Agent.

20137 [Alert Profile} When deleting an email address that has been profiled in an Alert Profile, the Alert Profile still displays the email address.

Move the email address back to the unprofiled list in the Alert Profile dialog and save. Then delete the email address.

30653 [Cisco 350 IOS] Using a name for EAP servers, rather than an IP address, does not work.

Use an IP address.

30728 [Cisco IOS] For APs with dynamic IP address and a pre-defined DNS entry, DNS values assigned from the DNS server are not reflected in the Admin. When MM attempts to set DNS entries, the 3rd entry will not be changed.

Use the first two entries only.

31090 [Cisco IOS] MM Admin shows Wep key value of 0s within SSID/VLAN setup if Global WEP is enabled before 5.7.1 upgrade

Reenter WEP key values in the local settings for the specified SSID/VLAN.

30672 [Cisco IOS] TACACS server type displays an authentication port and account port of 0 when it should be 1812 (default) and 1813 (default) respectively.

None needed: the user-requested values will be used.

30907 [Cisco IOS] The default profile does not contain any properties for VLAN 1 under the Radio SSID/VLAN node. The impact of this issue is that because profiles do not have default values for VLANs, if a default profile is applied to an AP with existing VLAN settings, the existing settings on the AP will be erased.

Do NOT apply default profiles to APs that already have VLAN settings unless the profile contains default VLAN settings.

31092 [Cisco IOS] WEP will not be enabled if Global WEP and Local WEP are enabled and then Local WEP is disabled

Disable, then enable Global WEP

20244 [Cisco IOS] When Host name is used to configure Syslog Server in profile, MM configures Syslog Server every time AP is queried.

Use IP address rather than host name for the syslog server.

30794 [Cisco IOS] When multiple radios are in use and VLAN 1 is enabled, Mobile Manager will show Native VLAN ID set to 1 for the 2nd radio (identical to the 1st radio interface) although this VLAN is not enabled.

This is a minor issue and will not cause a serious problem. The disabled VLAN should have an ID of 0 rather than 1.

20256 [Cisco VxWorks with VLANs] When the VLACL is enabled, MM does not automatically set the Address Filter of the SSIDs to "disallowed". In other words, enabling VLACL will not block MUs from communicating with the VLAN that the MU is associated with.

The workaround is to set the Address Filter of the SSIDs to "disallowed" manually from the Admin, in order for VLACL to take effect on the SSIDs for these VLANs.

10264 [Cisco VxWorks] Resetting a Cisco 1200 AP to Factory Defaults does not clear the VLAN WEP Keys on the Admin UI although the WEP values on the AP are cleared.

Does not impact operations. The AP has the correct settings.

20214 [Cisco VxWorks] Cisco 1200 12.03T Profiled AP stays in “Applying settings” status.

No workaround available, the AP will eventually become READY.

20225 [Cisco VxWorks] Cisco 1200 AP FW 12.01T or 12.02T1. If the Radio is turned off, Radio On setting does not to bring Radio Up.

This is a firmware issue. The AP must be reset to turn the Radio on.

4599 [Cisco VxWorks] Cisco AP with HTTP user that is not in MM's HTTP user list shows READY state instead of "HTTP Query Failed" state, preventing you from selecting AP properties.

Add the user name on the AP to the Mobile Manager's Device Access Manager.

4600 [Cisco VxWorks] MM is unable to discover APs behind a switch if the user name for the AP does not exist in Mobile Manager's Device Access List.

Add the AP manually with the known Read-Only community name.



4708 [Cisco VxWorks] Partial AP properties are displayed when the AP's user

name is in the RO and RW community name lists, but not in HTTP user list. See the work-around for issue # 4689.

10096 [Cisco VxWorks] When a 350 AP is powered up immediately after MM is restarted, and the AP is assigned to a DHCP profile which has a newer firmware version than the AP has, this results in the AP staying in “updating firmware” status for a long time.

This issue can happen on new APs being powered up following MM startup. There is no workaround except to wait for the firmware update to complete.

4435 [Cisco VxWorks] When IP range discovery is used, a 350 AP is sometimes discovered as a switch. This happens when: 1) AP has a user with SNMP rights 2) AP has another user without SNMP rights 3) The User with SNMP rights is added as read-only in DAM.

Ensure that the AP's User List is synchronized with the Mobile Manager's Device Access Manager user list.

10258 [HP] HP with FW 2.1.0 ProCurve 520wl: Incorrect VLAN settings can make APs unusable. A warning is displayed.

This is a firmware issue. Ensure correct VLAN settings are applied.

20240 [Proxim 2000, FW 2.2.2] WEP issues with Proxim 802.11b/g and 802.11g: - MU cannot associate with AP regardless if the same Transmit Key and WEP values are set on both MU & AP. - Transmit Key, WEP values cannot be updated after the first initial change. - Every time the AP's Operation Mode is changed (i.e. from 802.11b/g to g), MUs can no longer associate with the AP although both devices have the same SSID setting. Note: this is not an issue on Orinoco cards with only 802.11b

In ORiNOCO AP firmware version 2.2.2, changing wireless protocols (i.e. from 802.11b/g to 802.11g) will prevent mobile clients from being associated despite the correct SSID and WEP key being set. This problem was corrected in Proxim firmware version 2.3.1. See # 20232 for a related issue.

31011 [Proxim 4000, AVAYA AP-3] Security settings that do no apply to WEP Key Rotation are not disabled in the Advanced Properties dialog box when WEP Key Rotation is enabled. If these properties are changed, the AP might reset when the next query occurs.

Once the AP resets, WEP key rotation will work correctly.

20303 [Proxim 600 and 2000, FW 2.2.2] Firmware update can result in the AP not having a correct firmware image, causing the AP to become unavailable.

When multiple ORiNOCO APs are upgraded simultaneously, it is possible for the image to be corrupted during transfer, likely due to overloading of the TFTP server or other network components. In ORiNOCO AP firmware images prior to 2.4.1, the AP would accept the corrupted image, and would require a force reload procedure in order to restore the AP to normal operation. Proxim firmware 2.4.4 and later versions correct this issue by verifying the integrity of the image before accepting it.

20232 [Proxim 600 b/g and 600 a, FW 2.3.1] Mobile unit is unable to communicate with AP using WEP keys 2, 3, or 4 if WEP key is set. If MU WEP key is not set, communication may be possible.

Static WEP keys 2-4 are not functional in fw version 2.3.1. Only WEP key #1 may be used. This issue is fixed in Proxim firmware version 2.4.4 and later.

31005 [Proxim AP] An SNMP Set General Error occurs when you create a profile with the MAC Access Control property enabled in RADIUS settings but you do not enable the RADIUS server (it is disabled by default). This might occur a RADIUS server has been previously configured on the AP.

Enable the RADIUS server or disable the MAC Access Control property.

31787 [Proxim, AVAYA, FW 2.5.2 and 2.6.0] WEP key values and PSK Passphrase values are not set on the AP if they are the only properties to change in the Security Profile.

Change another property value in the Security Profile to ensure that the values are set on the AP.

10261 [Proxim, Dell, HP, all APs, all FW] The Mobile Unit association table contains information about MUs that are currently or were previously associated with the AP. There is no information whether the MU is active or inactive.

The Mobile device status is inaccurate: Inactive stations may be indicated as active. A subsequent version of Mobile Manager will use the “Monitor Station Statistics” table, which provides the correct information.

31770 [Proxim, FW 2.4.11] SNMP error occurs when you create a new VLAN using an existing SSID and apply it to the access point.

Change the SSID of the VLAN on the access point, apply it, then create a new VLAN using the original SSID.

31772 [Proxim, FW 2.5.2 and 2.6.0] Mobile Manager fails to delete a security profile that is associated with a VLAN that is also being deleted.

Remove the association of the security profile to the VLAN before applying to the profile. This allows the security profile to be deleted.



31726 [Proxim, FW 2.5.2 and 2.6.0] The WEP key values in a Security Profile

cannot be set outside of a Mobile Manager profile. Use a Mobile Manager profile to configure WEP key values.

31604 [Proxim FW 2.5.2 and 2.6.0] SNMP Set error when setting a VLAN ID to a value that is already used by another VLAN

Use a different unused VLAN ID.

31856 [Symbol T3] AP to MU communication is lost when stopping WKR on VLANs. The WEP Encryption is not being disabled on AP when stopping WKR, while WEP Encryption on MU’s is disabled, causing a disconnect between AP and MU’s

When stopping WKR, manually disable Encryption on all Dynamic WKR enabled VLANs.

31506 [Symbol 4131] WEP settings for a VLAN are automatically disabled after switching firmware from 3.70-77 to 3.92-21 in a profile.

Reconfigure the profile settings for WEP after changing the specified firmware.

4651 [Symbol AP] Incorrect values appear in the Advanced Property dialog box when an AP has an unreachable IP address or is in a Query Failed state.

Ensure the AP has a valid IP address.

4672 [Symbol AP] The Reset Factory feature does not clear an AP's ACL. Telnet to the AP to Reset Factory and clear the ACL list.

31803 [Symbol WS 2000, FW 1.5.0.0-216r] When applying a new profile with country code set to US, default settings fail and access ports are offline.

Wait for the next query cycle or manually force a query to fix the issue.

31420 [Symbol WS 2000] After setting the IP Assign Mode to DHCP Client Mode in a profile and after the Agent applies the settings, the switch becomes IP unreachable and cannot be re-discovered by MM. This might happen if a switch has been previously assigned a static IP address.

31442 [Symbol WS 5000, FW 1.2.0.39o] A Get SNMP Set Unknown Error occurs for some ACL entries when the Agent attempts to apply an ACL list to the switch.

Update the firmware.

31479 [Symbol WS 5000] No alert is generated when an SNMP Set failure occurs as the result of an incorrect RW community name.

Ensure that you configure a RW community name (client) on the switch and that the matching name is configured in Mobile Manager.

31353 [Symbol WS 5000] The MM Administrator allows the user to add one WLAN policy to more than one VLAN.

Do not assign a WLAN to more than one VLAN. If you attempt to do so, an error message appears warning the user that each WLAN may only be associated with one VLAN.

30495 [Symbol WS 5000] When a second profiile is applied to a switch while the Agent is in the process of applying a first profile, the Administrator will report that the second profile has been applied once the Agent completes the task. (In fact, only the first profile has been applied.)

Either wait until the first profile is fully applied before changing the profile assignment, or query the switch to force an immediate update.

30969 [Symbol WS 5000] When manually adding a switch, the Agent does not use its internal list of names to discover the switch if the wrong RW or RO community names are entered in the Add Network Device dialog box.

Use the correct RO and RW community names when adding the switch.

31458 [Symbol WS 5000] When the switch and access ports are reset, the status remains in “RESET” status until the next query.

Manually force a query to update the status immediately.

31011 [SYSTIMAX AirSPEED AP542] Security settings that do no apply to WEP Key Rotation are not disabled in the Advanced Properties dialog box when WEP Key Rotation is enabled. If these properties are changed, the AP might reset when the next query occurs.

Once the AP resets, WEP key rotation will work correctly.

31787 [SYSTIMAX, FW 2.5.2 and 2.6.0] WEP key values and PSK Passphrase values are not set on the AP if they are the only properties to change in the Security Profile.

Change another property value in the Security Profile to ensure that the values are set on the AP.

30376 Due to a rollover bug in the bytes sent statistic, Mobile Manager might periodically retain an erroneous spike in its bytes sent statistical records. This will appear as a momentary spike or dip in some of the Dashboard graphs, depending on the graph.

As a temporary workaround, base your evaluation of Dashboard data on patterns rather than momentary spikes or dips.

30598 On Windows 2000 and earlier versions, Pick Adapter function fails when user tries to use Pick Adapter through a Terminal Services Client. This occurs whether running the Pick Adapter during or following the installation.

See Appendix A in MM 5.7.0 release notes for a workaround.

31984 [WS5000] Unable to set primary for A radio WLAN under APP No workaround. Try to set in the web interface.

32012 [WS 5000] snmpclient list is corrupted and switch does not respond to snmp after firmware upgrade.

Remove the corrupted snmpclient entries from the Switch using the web interface.

32015 [SF 8438] Proxim requires two step process to set VLANs on Japanese AP600 running 2.4.11

This will be fixed in the next MM release.



31997 [Cisco IOS] Firmware 12.3-4JA no longer shows main ESSID in status pane View the ESSID from AP Advanced Properties.

[Cisco IOS] Firmware 12.3 and above you cannot set VLAN ID to 0 to disable the VLAN if the value is currently 1.

This is the behavior of the firmware.

32016 Cisco IOS - bridge-group of vlan is set to 0 after changing Native VLAN ID to a newly added VLAN ID and VLAN 1 exists.

Delete VLAN 1 or set Native VLAN ID to one to restore bridge-group info for VLAN 1.

Documentation Updates

At the time of publication for these release notes, all information in the Mobile Manager 5.7.8 User Guide is up to date.

Version History

• 4/6/2006. Document version 1 created for MM 5.7.8.

Software Release Notes 5.7.8 Build 19 Date: 4/6/06 · 2007-01-23 · Mobile Manager 5.7.8 Release...

Documents

Transcript of Software Release Notes 5.7.8 Build 19 Date: 4/6/06 · 2007-01-23 · Mobile Manager 5.7.8 Release...