Avaya Solution & Interoperability Test Lab Application Notes for Configuring the Wavelink Mobile Manager to Manage Avaya AP-3 and AP-4/5/6 Wireless Access Points - Issue 1.0 Abstract These Application Notes describe the procedure for configuring the Wavelink Mobile Manager to manage and monitor Avaya AP-3 and AP-4/5/6 Wireless Access Point (AP) devices on a local area network. The AP-3 may be equipped with up to two separate 802.11 radios, while the AP-4, AP-5, and AP-6 are equipped with a single 802.11b, 802.11a, and 802.11b/g radio, respectively. The AP-4/5/6 equipped with a single 802.11a/b/g radio is not covered in these Application Notes. During compliance testing, the Avaya AP-3, AP-4, and AP-5 were successfully discovered, configured, and monitored by the Wavelink Mobile Manager. The AP-6 was not used in the compliance testing, but aside from its 802.11b/g radio mode, it is functionally equivalent to the AP-4 and AP-5. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. 1 of 22
1. Introduction These Application Notes describe a compliance-tested configuration comprised of Avaya Wireless AP-3 and AP-4/5/6 Access Point (AP) devices and the Wavelink Mobile Manager. The AP-3 contains two slots that can be equipped with 802.11 radio cards. The AP-4, AP-5, and AP- 6 are equipped with a single 802.11b, 802.11a, and 802.11b/g radio, respectively. The AP-4/5/6 equipped with a single 802.11a/b/g radio is not supported in Mobile Manager Release 5.7.1. Avaya APs attach to existing wired LAN segments to extend them to wireless 802.11 clients such as wireless IP phones and PCs equipped with 802.11 interface cards. The Wavelink Mobile Manager is a server-based, wireless network management software application that allows network administrators to manage and monitor wireless APs such as the Avaya AP-3 and AP- 4/5/6. Mobile Manager servers, called Agents, run on Windows 2000 and XP platforms, and may be deployed in a network in a centralized or distributed fashion. The Agents automatically discover APs on their respective Layer 2 broadcast domains and may be configured to search specific IP address ranges for APs. The Mobile Manager Graphical User Interface (GUI), called the Administrator console, connects to one or more Agents, and provides the administrator with the ability to manage the APs associated with those Agents. From the Administrator console, the administrator may view and configure settings of individual APs, monitor AP performance, and provide firmware updates to APs. In addition, the administrator may create configuration profiles and assign APs to those profiles. APs that are assigned to the same profile have the same configuration settings, and the Agents ensure that profiled APs do not deviate from the settings of their respective profiles. Figure 1 shows a sample network configuration consisting of Avaya APs, wireless clients (wireless laptop and Avaya 3600 Series Wireless IP Telephones), a single Mobile Manager Agent, a DHCP/RADIUS/TFTP server, and other Avaya infrastructure components. Note that actual network configurations may vary. The infrastructure components, namely the Avaya P333T-PWR Layer 2 Switches, Avaya P333R Layer 2/3 Switch, Avaya S8500 Media Server, Avaya G650 Media Gateway, Avaya Voice Priority Processor, and Avaya 4600 Series IP Telephones support the verification and illustration of the Avaya/Wavelink solution. The configuration of the infrastructure components are not the focus of these Application Notes and are thus not described here. 2 of 22
4610 IP Phone Ext. 60000 VLAN 2 Avaya Voice Priority Processor IP Addr: 10.1.2.9 VLAN 2 G650 Media Gateway IPSI IP Addr: 10.1.2.6 C-LAN IP Addr: 10.1.2.7 MEDPRO IP Addr: 10.1.2.8 VLAN 2 S8500 Media Server IP Addr: 10.1.2.5 VLAN 2 DHCP/RADIUS/TFTP Server IP Addr: 10.1.1.100 VLAN 1 Mobile Manager Agent IP Addr: 10.1.1.150 VLAN 1 3616 Wireless IP Phone Ext. 61000 AP-3 VLAN 1 P333T-PWR Layer 2 Switch IP Addr: 10.1.1.20 AP-4 VLAN 1 3626 Wireless IP Phone Ext. 61001 VLAN 1, 2 P333R Layer 2/3 Switch IP Addr: 10.1.1.30 Wireless (802.11a/b/g) Laptop with IP Softphone and Odyssey Client VLAN 2, 3 4620 IP Phone Ext. 60001 VLAN 2 P333T-PWR Layer 2 Switch IP Addr: 10.1.3.20 AP-5 VLAN 3 Data/Management VLANs VLAN 1 (untagged): 10.1.1.0/24 VLAN 3 (untagged): 10.1.3.0/24 Voice VLAN VLAN 2 (tagged): 10.1.2.0/24 Figure 1: Sample Network of Avaya AP-3 and AP-4/5/6 Access Points Managed by Wavelink Mobile Manager 3 of 22
2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software/Firmware Avaya AP-3 Wireless Access Point 2.4.5 Avaya AP-4 Wireless Access Point 2.4.5 Avaya AP-5 Wireless Access Point 2.4.5 Avaya 3616 Wireless IP Telephone 96.024 Avaya 3626 Wireless IP Telephone 96.024 Avaya Voice Priority Processor 16x.110 Avaya S8500 Media Server 2.1 (R012x.01.0.411.7) Avaya G650 Media Gateway - TN2312BP IPSI 9 TN799DP C-LAN 11 TN2302AP MedPro 92 Avaya P333T-PWR Power over Ethernet Stackable 4.0.17 Ethernet Switch Avaya P333R Multilayer Stackable Switch 4.0.9 Avaya 4610SW IP Telephone 2.1 Avaya 4620SW IP Telephone 2.1 Avaya IP Softphone running on Windows XP SP1 5.1 laptop Wavelink Mobile Manager Agent running on 5.7.1 Build 30 Windows 2000 Professional SP4 Wavelink Mobile Manager Administrator running on 5.7.1 Build 30 Windows 2000 Professional SP4 Microsoft DHCP Server running on Windows 2000 - Advanced Server SP4 SolarWinds.Net TFTP Server running on Windows 5.0.46 2000 Advanced Server SP4 Funk Odyssey Server (RADIUS server) running on 2.0.1 Windows 2000 Advanced Server SP4 Funk Odyssey Client running on Windows XP SP1 3.00.0.937 laptop Laptop with Proxim ORiNOCO 802.11a/b/g Windows XP Professional SP1 ComboCard Gold 4 of 22
3. Configure the Avaya AP-3 and AP-4/5/6 Access Points The Wavelink Mobile Manager can automatically discover (see Chapter 4, Discovering Devices, of [3]) and configure Avaya APs. In situations where an AP is not reachable by Mobile Manager Agents (i.e., the AP is not on the same subnet as a Mobile Manager Agent and the AP does not have an IP address or a valid IP address), the Avaya ScanTool may be used to assign a static IP address to the AP. After the AP has been assigned an IP address, Wavelink Mobile Manager can automatically discover and configure the AP. The steps in this section describe how to use the ScanTool to configure static IP address information on an Avaya AP. If the AP is reachable and discovered by a Mobile Manager Agent, then this section may be skipped. Step 1. Install Avaya AP software on a PC (see the User s Guide for your AP [1][2]). 2. Connect the PC to a subnet where the Avaya AP resides. 3. Select Start->Programs->Avaya Wireless->ScanTool to run the ScanTool utility. Select the appropriate network adapter (i.e., LAN card) and click OK. ScanTool will find all Avaya APs on the subnet. 4. Select the Avaya AP to be configured and click on Change. 5 of 22
Step 5. Set the IP Address Type to Static, and specify the static IP Address, Subnet Mask, and Gateway IP address. Enter the appropriate Read/Write Password, and click on OK. 4. Configure the Wavelink Mobile Manager This section describes the steps for configuring the Wavelink Mobile Manager to manage Avaya APs. It assumes that one or more Mobile Manager Agents have been deployed in the network and the administrator has logged into the Mobile Manager Administrator console. 4.1. Device Access Privileges In order for a Mobile Manager Agent to retrieve information from and configure settings on an AP, it must have the correct SNMP access privileges for the AP. The following steps describe how to enter the SNMP Read-Only and SNMP Read/Write community strings of an AP into a Mobile Manager Agent. The Mobile Manager Agent can then use those SNMP community strings in querying and configuring the AP. To change the SNMP community strings of the AP from the Mobile Manager, see Sections 4.3 and 4.5. 6 of 22
Step 1. In the Mobile Manager Administrator console main window, right-click on a Mobile Manager Agent in the left pane and select Device Access Privileges from the pop-up menu or alternatively, select a Mobile Manager Agent in the left pane and select Device Access Privileges from the Options menu. In the example below, localhost is a Mobile Manager Agent because the Mobile Manager Administrator console is running on the same machine as the Mobile Manager Agent. 7 of 22
Step 2. In the Device Access Privileges window, enter the SNMP R/O (Read Only) and SNMP R/W (Read/Write) community strings of Avaya APs in the network. This allows the Mobile Manager Agent to query and configure Avaya APs in the network. Click OK when finished. Note: The Mobile Manager Agent can also change the SNMP community strings of an Avaya AP (see Sections 4.3 and 4.5). If the SNMP community strings are changed, the new SNMP community strings must be added to the Device Access Privileges list. Otherwise, the Mobile Manager Agent will not be able to query and configure the AP after the changes are applied. 8 of 22
4.2. Configure the Wavelink Mobile Manager to Discover Avaya APs Mobile Manager Agents automatically discover APs on their respective Layer 2 broadcast domains. Mobile Manager Agents may also be configured to discover APs on specific IP address ranges. The following steps show how to configure a Mobile Manager Agent to search specific IP address ranges for Avaya APs. Step 1. In the Mobile Manager Administrator console main window, right-click on a Mobile Manager Agent in the left pane and select Network Search Settings from the pop-up menu or alternatively, select a Mobile Manager Agent in the left pane and select Network Search Settings from the Options menu. 9 of 22
Step 2. In the Network Search Settings window, enter one or more IP address ranges for the Mobile Manager Agent to search for APs. Check the Enable network search on OK checkbox and click on OK. 10 of 22
4.3. Create Profiles for Avaya APs A Mobile Manager profile defines the uniform configuration settings for all APs assigned to it. All APs assigned to a particular profile must conform to the configuration settings of the profile; any deviations are automatically resolved by re-applying the profile s settings. The following steps demonstrate how to create configuration profiles for Avaya APs on Mobile Manager Agents. Step 1. In the Mobile Manager Administrator console main window, right-click on a Mobile Manager Agent in the left pane and select Agent Properties from the pop-up menu or alternatively, select a Mobile Manager Agent in the left pane and select Agent Properties from the Options menu. 11 of 22
Step 2. In the Agent Properties window, click on Add. 3. In the Add Profile window, select either Avaya AP-3 or Avaya AP-4/5/6 as the Hardware type. The Firmware field is then automatically populated with the latest firmware version for the Avaya AP type, but other versions may be selected from the drop-down menu box. Enter a meaningful Profile Name and click on Advanced. 12 of 22
Step 4. In the Advanced Properties window, configure the Wireless Interface Type, Operational Mode, SSID, SNMP community strings, and any other parameters as necessary. The parameters will apply to all Avaya APs that are assigned to this profile. Note that the 802.11 mode configuration for AP-4/5/6 profiles is a two-step process. Click on the Radio folder and select 802.11b, 802.11a, or 802.11b/g (for AP-4, AP-5, or AP-6, respectively) from the Wireless Interface Type drop-down menu box. If the Wireless Interface Type is 802.11b/g, then click on Operational Mode and select 802.11b only, 802.11g only, 802.11bg, or 802.11g-wifi. If the Wireless Interface Type is 802.11b or 802.11a, then the Operational Mode is fixed. The 802.11 mode configuration for AP-3 profiles is similar, except that the 802.11 modes of the AP-3 s two wireless interfaces are configured independently. 13 of 22
Step 5. Click on OK successively in the Advanced Properties and Add Profile windows. 6. Repeat Steps 2 5 to create additional Avaya AP profiles. 7. Click on OK in the Agent Properties window. If SNMP community strings were configured, then the following dialog box will appear. Click on Yes to automatically add the configured SNMP community strings to the Device Access Privileges list. 14 of 22
4.4. Assign Profiles to Avaya APs The following steps describe how to assign an Avaya AP to a Mobile Manager configuration profile. Step 1. In the Mobile Manager Administrator console main window, right-click on an Avaya AP and select Assign to Profile and a profile from the pop-up menu. 2. Click on Yes in the confirmation window. 15 of 22
4.5. Configure Non-Profiled Avaya APs The following steps describe how to configure Avaya APs that are not assigned to any Mobile Manager configuration profile. Step 1. In the Mobile Manager Administrator console main window, right-click on an Avaya AP and select Properties from the pop-up menu or alternatively, select an Avaya AP and select Properties from the Options menu. 16 of 22
Step 2. Click on Advanced in the Properties window. 17 of 22
Step 3. In the Advanced Properties window, configure parameters as necessary. The parameters will apply only to the selected Avaya AP. 4. Click on OK successively in the Advanced Properties and Properties windows. 5. Interoperability Compliance Testing The interoperability compliance testing included feature functionality and serviceability testing. The feature functionality testing evaluated the Mobile Manager s ability to discover, properly configure, and upgrade Avaya AP-3, AP-4, and AP-5 Wireless Access Point devices. The AP-6 18 of 22
was not used in the compliance testing, but aside from its 802.11b/g radio mode, it is functionally equivalent to the AP-4 and AP-5, and therefore should be supported. The serviceability testing introduced failure scenarios and examined the Mobile Manager s ability to resume management of the Avaya APs after failure recovery. 5.1. General Test Approach The general approach was to manage and monitor the Avaya APs using the Mobile Manager. The main objectives were to verify that: The Mobile Manager Agent automatically discovers Avaya APs on its Layer 2 broadcast domain as well as on specified IP address ranges. The Mobile Manager Agent is able to provide static IP addresses to Avaya APs. The Mobile Manager Agent correctly configures profiled and non-profiled APs. Configuration profile settings are enforced on profiled Avaya APs only. Access Control Lists, RADIUS, authentication, and encryption settings may be configured on Avaya APs using the Mobile Manager. Avaya AP firmware updates are successfully performed by the Mobile Manager Agent. Information reported by the Mobile Manager is accurate and consistent with the actual information on the Avaya APs. Avaya 3616 and 3626 Wireless IP Telephones are able to reach an Avaya Voice Priority Processor (which prioritizes wireless voice packets over data packets) and complete phone calls. A laptop PC equipped with a wireless PC card is able to access the network, i.e. has IP connectivity to other network components. The Mobile Manager Agent is able to manage Avaya APs after the failures such as cable pulls and server and device resets have been resolved. 5.2. Test Results All test cases completed successfully. The Mobile Manager was able to manage and accurately monitor the Avaya APs, and apply configuration settings to profiled and non-profiled APs. The wireless clients were able to access the network when permitted by Access Control Lists and authentication/encryption settings configured on the APs by the Mobile Manager. The following are notes and observations obtained from testing: The firmware on the AP-4/5/6 cannot be downgraded from version 2.4.x to 2.3.x. Version 2.4.x firmware must first be manually removed and then version 2.3.x must be manually loaded (see Forced Reload Procedure in [2]). The Avaya AP-4/5/6 equipped with a single 802.11a/b/g radio is not supported in Mobile Manager Release 5.7.1. 19 of 22
6. Verification Steps The following steps may be used to verify communication between a Mobile Manager Agent and Avaya APs, and to check the configurations of the APs. 1. Ping each Avaya AP from the machine on which the Mobile Manager Agent resides and verify connectivity. 2. For automatic discovery of Avaya APs in a particular IP address range, verify that the range is defined correctly and the SNMP community strings of those APs are in the Device Access Privileges list (see Sections 4.1 and 4.2). 3. For a profiled Avaya AP, check that its actual configuration settings match those of the profile s configuration settings. 4. For a profiled Avaya AP, consider whether the profile s configuration settings are appropriate (desired) for the AP. If not, remove the AP from the profile or reassign the AP to an appropriate profile. 5. Verify that the authentication and encryption settings of the wireless clients are consistent with their associated Avaya APs. 6. Verify on the Administrator console that the status of each Avaya AP is READY. 7. Support For technical support on the Wavelink Mobile Manager, consult the Wavelink support pages or contact Wavelink Customer Service. Wavelink support pages: http://www.wavelink.com/support/documentation.aspx http://www.wavelink.com/support/kb/ http://www.wavelink.com/support/forum/ Wavelink Customer Service: Email: customerservice@wavelink.com Phone: 1-888-699-WAVE (1-888-699-9283) 8. Conclusion These Application Notes illustrate the procedures for configuring the Wavelink Mobile Manager to manage and monitor Avaya AP-3 and AP-4/5/6 Wireless Access Point devices. The Mobile Manager and the Avaya APs were successfully compliance-tested in the network configuration described in these Application Notes. The Mobile Manager was able to discover, configure, and monitor the Avaya APs, as well as report the wireless clients associated with the Avaya APs. 20 of 22
9. Additional References The following Avaya product documentation may be found at http://support.avaya.com: [1] Avaya Wireless AP-3 User s Guide, Release 2.4.5, January 2004, Document Number 555-301-708 [2] Avaya Wireless AP-4, AP-5, and AP-6 User s Guide, Release 2.4.5, January 2004, Document Number 555-301-708 The following Wavelink product documentation may be found at http://www.wavelink.com/support/documentation.aspx: [3] Wavelink Mobile Manager Version 5.7.1 Users Guide [4] Wavelink Mobile Manager 5.7 Webhelp 21 of 22
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya DeveloperConnection Program at devconnect@avaya.com. 22 of 22