Q: What is the J9001A ProCurve Wireless Edge Services xl Module?
A:
The ProCurve Wireless Edge Services xl Module transforms a ProCurve Switch 5300xl Series into a wireless services-enabled switch. Together with one or more ProCurve radio ports (RPs), this wireless services-enabled switch creates a Wireless LAN System which provides centralized wireless LAN configuration, enabling a resilient, highly secure, multi-service network.
» Return to top
Q: How does the J9001A ProCurve Wireless Edge Services xl Module differ from the J9003A ProCurve Redundant Wireless Edge Services xl Module?
A: The Redundant Wireless Services xl Module (J9003A) is designed primarily to provide cost-effective failover and load balancing capabilities. The redundant module provides the same capabilities as the Wireless Edge Services xl Module, or primary module, with one exception: the redundant module does not include any RP licenses, and you cannot add licenses to it. Instead, the redundant module is authorized to use the primary module’s licenses when configured as part of a redundancy group.
» Return to top
Q: What radio ports are is available for the Wireless Edge Services xl Module?
A: The following radio ports are available.
» Return to top
Q: What are the radiation plots of the internal antennae for the available radio ports?
A: Both the J9004A ProCurve Radio Port 210 and the J9006A ProCurve Radio Port 230 use the same internal 802.11b/g 2.4 GHz antennae:
 |
 |
 |
 |
 |
| |
| The following are the radiation plots for the internal 802.11a 5 GHz antennae of the J9006A ProCurve Radio Port 230: |
| |
 |
 |
 |
 |
 |
» Return to top
Licensing
Q: How does licensing for the radio ports work?
A:
With its default RP license, each J9001A Wireless Edge Services xl Module can support up to 12 ProCurve RPs (for a total of up to 24 radios). Support for additional ProCurve radio ports may be enabled with the purchase of one or more of the following licenses:
J9002A The ProCurve Wireless Services Module 12 RP License provides support for 12 additional ProCurve Radio Ports on a Wireless Edge Services xl Module, and may be installed up to the following maximum capacities.
| ProCurve Wireless Edge Services xl Module software version |
Maximum supported number of Radio Ports per module |
| WS.01.xx |
36 |
| WS.02.xx |
48 |
» Return to top
Features
Q: I see that there is an active and standby function on each of the available modules. Can the “redundant” module play the “active” role?
A: Redundancy group members can operate in either active mode or standby mode. The type of module (primary or redundant) has no relation to the operation mode. You can place a primary module in standby mode, or more typically, you can place a redundant module in active mode. An active member can adopt RPs at any time. If a group has more than one active member, together the active members can adopt as many RPs as allowed by the group authorization level. The group authorization level is determined by the authorization level of the single group member with the greatest number of licenses. For more detail about how this works, please see “Rules of Redundancy Groups” in the Wireless Edge Services xl Module Management and Configuration Guide.
Q: What types of user authentication are possible using the ProCurve Wireless Edge Services xl Modules?
A:
The Wireless Edge Services xl Module supports three types of authentication:
- 802.1X authentication
- Web-Auth
- MAC authentication
Alternatively, the Wireless Edge Services xl Module can allow stations to connect to a Wireless LAN without authenticating formally. In this case, an encryption key usually acts as a password. Differing strategies may be configured for use with the various WLANs configured.
Software Updates
Q: What is DFS-2 and how does it affect the function of my ProCurve Wireless Edge Services xl Module and radio ports?
A:
Customers in the U.S. should be aware of FCC Changes to Dynamic Frequency Selection (DFS) in the 5 GHz Band. Effective July 20, 2007, new FCC regulations on the use of the 5GHz band, the band used by radios supporting the IEEE 802.11a standard, prohibit the sale of radios not meeting the new specifications. To comply with these new requirements, several channels in the ProCurve Radio Ports 220 (J9005A), and 230 (J9006A) are disabled by software version WS.01.11 (and later). Software version WS.01.11 (and all versions of WS.02 software) disables channels 52, 56, 60, 64 (5.25-5.35 GHz) in the U.S. These channels remain available for use in other countries.
Configurations that have WLANs statically configured to use the 802.11a channels which are disabled after a software update to WS.01.11 or WS.02.xx will find those WLANs returned to default 802.11a settings.
» Return to top
Q: Can I still use a software version earlier than WS.01.11 legally in the United States after July 20, 2007?
A: If you purchased your ProCurve Wireless Edge Services xl Module prior to July 20, 2007, you are permitted to continue to use WS.01.05 and earlier versions of software; utilizing all the originally available 802.11a channels in compliance with FCC regulation. Radio Ports and modules purchased on or after July 20th will not be in compliance with FCC regulations if they use a software version prior to WS.01.11. ProCurve will not sell U.S. devices with non-compliant software after the relevant deadline.
Q: In what ways have the capabilities and scalability of the ProCurve Wireless Edge Services xl Module changed with the update to WS.02.xx software?
A:
The following is a summary of some of the improvements in the WS.02.xx software.
| Feature/Function |
WS.01.xx |
WS.02.xx |
| Throughput - Unencrypted |
290 Mbits |
400 Mbits |
| Maximum number of Radio Ports supported |
36 |
48 |
| Maximum number of associated stations |
1000 |
4096 |
| Maximum number stations per radio |
64 |
256 |
| Maximum number of modules in Redundancy Group |
2 |
12 |
| Maximum number of VLANs per module |
8 |
32 |
| Radio Port Failover time (Layer 2) |
55 sec typical |
20 sec typical |
| Maximum number of static routes |
1000 |
300 |
| Maximum number RADIUS Authentications per second |
N/A |
15 Internal / 5 LDAP |
| Maximum number of DHCP Lease Grants per second |
N/A |
15 |
| Maximum number of modules in Layer 3 Roaming Group |
N/A |
12 |
Troubleshooting
Q: I have lost/misplaced/forgotten the password for access to my ProCurve Wireless Edge Services xl Module. How can I restore access?
A:
The module will have to be reset to factory defaults. This may be done from the CLI of the module by accessing it through the host 5300xl switch, as follows.
ProCurve5308xl>enable
ProCurve5308xl#config
ProCurve5308xl(config)#wireless-services <slot ID>
ProCurve5308xl(wireless-services-d)#erase startup-config
» Return to top
Q: I just updated from WS.01.xx to WS.02.xx and now I can’t seem to access the Web Management Interface. What should I do?
A:
The Java interface has changed significantly from the WS.01.xx to the WS.02.xx versions. It is recommended that you clear both the Java cache and the IE browser cache immediately following an update or backward revision between major versions of the software. Instructions for that process follow (see next question/answer). As of WS.02.07, Internet Explorer version 7 is not supported.
Module management passwords which were configured using WS.01.xx software will NOT carry forward to the module running WS.02.xx software. Manager and operator passwords will return to their default values. ProCurve strongly recommends that the module’s management should be immediately accessed and the management password reconfigured.
Q: How do I clear the Java and Web browser caches?
A: The following steps will allow you to complete the following:
- Clear your browser’s cache.
- Clear the Java cache.
- Close the browser and re-open it.
Note: This procedure also applies if you downgrade from version 02.XX to 01.XX software.
How to Clear the Internet Explorer (IE) Browser Cache
The following steps detail the process of clearing the cache in IE version 6. If you are using a different version, your steps might vary slightly.
1. Open IE.
» Enlarge Image
2. Select Tools > Internet Options. The Internet Options window is displayed...
3. Make sure that you are in the General tab.
4. In the Temporary Internet files section, click Delete Files. The Delete Files window is displayed.
5. Check the Delete all offline content box.
6. Click the OK button.
7. In the Internet Options window, click the OK button.
How to Clear the Java Cache
The following steps explain how to delete the cache for Sun Java version 1.5 or higher on a Windows XP machine. If you are using a different Java or operating system (OS) version, your steps might vary.
Follow these steps to delete the Java cache:
1. Select Start > Settings > Control Panel.
2. Select Java. The Java Control Panel window is displayed.
3. In the Temporary Internet Files section, click the Settings button. The Temporary Files Settings window is displayed.
4. Click the Delete Files button. The Delete Temporary Files window is displayed.
5. Make sure that the Applications and Applets box is checked.
6. Click the OK button.
7. In the Temporary Files Settings window, click the OK button.
8. In the Java Control Panel window, click the OK button.
Next, Restart (close and re-open) the Browser
You are now ready to access the Wireless Edge Services xl Module’s Web browser interface:
1. Close and re-open your browser.
2. Enter the IP address (or hostname) of your Wireless Edge Services xl Module in the browser.
3. The Java applet should begin to download from the module. You might need to activate the applet (as shown in Figure 8). Press <Space> or <Enter>.
4. After about a minute, the Login screen is displayed.
Q: My ProCurve Wireless Edge Services xl Module isn’t succeeding at Layer 3 adoption of my radio ports. What could be wrong?
A: Radio ports that were manufactured or adopted by a ProCurve Wireless Edge Services xl Module running WS.01.xx software will require an update to their bootloader code prior to their successful adoption at Layer 3. If you recently updated from WS.01.xx to WS.02.xx, it is important to prepare your radio port for Layer 3 adoption by first adopting the radio port in the same Layer 2 domain, either by connecting it directly to the Wireless Services-Enabled 5300xl switch or by connecting to an infrastructure switch in the same Layer 2 domain. The adoption time is extended slightly as the new bootloader code loads. When the radio port has been adopted, (the radio port LEDs flash about once every five seconds) the correct radio port bootloader code is installed. You may now finish the process for adopting the radio port at Layer 3 (see “Radio Port Adoption” in the Wireless Edge Services xl Module Management and Configuration Guide).
If you continue to have difficulty adopting the radio port at Layer 3, you should confirm that the radio port is able to reach its default gateway and obtain a DHCP address. You also may wish to review the section “Radio Port Adoption” in chapter 2 of the management and configuration guide.
Q: What do I need to consider prior to updating my software from WS.01.xx to WS.02.xx?
A: Any major software update containing multiple new features carries some risk to the configuration integrity with the update or backward revision. ProCurve recommends that you always copy your configuration to an FTP or TFTP server prior to updates. In order to minimize the risk of service interruption to a production network, software updates should be done during a maintenance window.
The Java engine in WS.01.xx software and WS.02.xx software is significantly changed – both browser (Internet Explorer) and Java caches should be cleared after the update to allow proper access to the module management.
Release notes may be consulted for other known issues and limitations.
» Return to top
Q: Are the WS.01.xx and WS.02.xx versions of software interoperable?
A: For the widest set of features and functionality, ProCurve recommends that you update all Wireless Edge Services Modules to version WS.02.xx. Software version WS.01.xx and version WS.02.xx may co-exist in a network. If doing so, keep in mind the following guidelines.
- Radio port bootloader code may be updated when a radio port is added or moved from the WS.01.xx software to or from the WS.02.xx software.
- There is a greater maximum number of radio port licenses (and other system configuration maximums) supported using software version WS.02.xx, so failover of a WS.02.xx module to a WS.01.xx module may not be complete if the failover is to a module running the older software.
- When using Layer 3 adoption, all redundancy group members must be using version WS.02.xx.
- Fast Layer 2 roaming is not supported by modules using version WS.01.xx software.
- GRE tunnels are not supported by version WS.01.xx.
» Return to top
Q: Why do I get an error when I try to enable the DHCP server?
A:
A valid DHCP scope should be configured and applied to an interface prior to enabling the DHCP server. If the user attempts to enable the server prior to performing the prerequisite steps, a message will appear in the lower left corner, stating “DHCP server could not be started on any interface(s). Please check log for more details.”.
Errors may also occur if a conflicting/redundant DHCP strategy configuration is attempted. For example:
- If DHCP is configured to assign IP addresses and an IP helper is added, or
- If an IP helper address is configured and a DHCP scope is added.
Q: I created an “allow any” ACL on my ProCurve Wireless Edge Services xl Module, and now even the communication I intended to allow is not getting through. What could be wrong?
A:
When an ACL is created that permits only IP traffic, the implicit “deny all else” statement at the end of the ACL prevents other (non-IP) traffic from getting through. You will have to explicitly configure a “MAC Extended - permit any any type ARP” rule (also known as an Access Control Entry) to allow ARP traffic to succeed. Please see the chapter “Access Control Lists (ACLs)” in the Wireless Edge Services xl Module Management and Configuration Guide for more information on creating and using ACLs.
Q: I created a Guest Web Administrator for creation of guest accounts, but my Guest Web Administrator cannot log in to the module. What might be wrong?
A: When a RADIUS Server is used to authenticate the Guest Web Administrator, the password must be a minimum of 8 characters. The Web configuration interface does not enforce that password minimum. If the account is configured with less than the 8 character minimum, the Guest Web Administrator will not be successful in logging in to create guest accounts.
» Return to top
|
