Jump to content United States-English
HP.com HomeProducts and ServicesSupport and DriversSolutionsHow to Buy
» Contact HP
 
HP ProCurve Networking

» My ProCurve Sign In

HP ProCurve Networking  >  Technical support  >  FAQs

FAQs


  »

HP Networking



The FAQs listed below are for these products:

  • J9051A ProCurve Wireless Edge Services zl Module
  • J9052A ProCurve Redundant Wireless Edge Services zl Module

» View FAQs for a different group of products

Customer Care

»  Overview
»  Services
»  Support
   »  Software
   »  Warranty
   »  FAQs
   »  Knowledge Base
   »  Manuals
   »  Reference library
   »  Configuration examples
   »  Support forms
   »  Security notices

My ProCurve gives you instant access to software update notifications.
» Register or log in now

Commercial help me agent » Contact ProCurve
Product Information
»Q: What is the J9051A ProCurve Wireless Edge Services zl Module?
»Q: How does the J9051A ProCurve Wireless Edge Services zl Module differ from the J9052A ProCurve Redundant Wireless Edge Services zl Module?
»Q: What types of radio ports are available for the Wireless Edge Services zl Module?
»Q: What are the radiation plots of the internal antennae for the available radio ports?

Licensing
»Q: How does licensing for the Radio Ports work?
»Q: Can a J9002A Radio Port License from a ProCurve Wireless Edge Services xl module be converted to the J9053A license for a ProCurve Wireless Edge Services zl module?
»Q: What is the process for converting an xl Radio Port License (J9002A) to a zl Radio Port License (J9053A)?

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?
» Q: What types of user authentication are possible using the ProCurve Wireless Edge Services zl modules?

Software
»Q: What is DFS-2 and how does it affect the functioning of my ProCurve Wireless Edge Services zl Module and radio ports?
»Q: Where can I learn more about the operation and use of the ProCurve Wireless Edge Services zl Module?
»Q: How do the capabilities and scalability of the ProCurve Wireless Edge Services zl Modules (J9051A, J9052A) differ from those of the xl Modules (J9001A, J9003A)?

Compatibility
»Q: Can ProCurve Wireless Edge Services xl and zl Modules be used together in a network?
»Q: Are there any limitations to the use of ProCurve Wireless Edge Services xl and zl modules together in a redundancy group?
»Q: Are any of the ProCurve Wireless Edge Services xl and zl features incompatible?

Troubleshooting
»Q: I have lost/misplaced/forgotten the password for access to my ProCurve Wireless Edge Services zl Module. How can I restore access?
»Q: I can’t seem to access the Management Interface. What should I do?
»Q: How do I clear the Java and browser caches?
»Q: My ProCurve Wireless Edge Services zl Module isn’t succeeding at adoption of my radio ports. What could be wrong?
»Q: When I purchase an SSL certificate from a Certificate Authority, I am asked for the server type. Which server type should I choose for the Wireless Edge Services zl Module?
»Q: Why do I get an error when I try to enable the DHCP server?
»Q: I created an “allow any” ACL on my ProCurve Wireless Edge Services zl Module, and now even the communication I intended to allow is not getting through. What could be wrong?
»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?
»Q: Should I configure the time on the host chassis and the ProCurve Wireless Edge Services zl Module? In what way would a time configuration conflict be resolved?

Answers

Product Information

Q: What is the J9051A ProCurve Wireless Edge Services zl Module?

A: The ProCurve Wireless Edge Services zl Module transforms a ProCurve Series 5400zl or 8200zl Switch 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, mobile multi-service network.

» Return to top

Q: How does the J9051A ProCurve Wireless Edge Services zl Module differ from the J9052A ProCurve Redundant Wireless Edge Services zl Module?

A: The Redundant Wireless Services zl Module (J9052A) is designed primarily to provide cost-effective failover and load balancing capabilities. The redundant module provides the same capabilities as the Wireless Edge Services zl 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 types of radio ports are available for the zl Wireless Edge Services Module?

A: The following radio ports are available.

Product Number

Product Name

Description

J9004A

ProCurve Radio Port 210

Single b/g radio

J9005A

ProCurve Radio Port 220

Dual a/b/g; plenum rated; requires external antenna

J9006A

ProCurve Radio Port 230

Dual a/b/g with integrated antenna

» 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:

1

The following are the radiation plots for the internal 802.11a 5 GHz antennae of the J9006A ProCurve Radio Port 230:

2

» Return to top

Licensing

Q: How does licensing for the Radio Ports (RPs) work?

A: With its default RP license, each J9051A Wireless Edge Services zl Module can support up to 12 ProCurve RPs. Support for additional ProCurve radio ports may enabled with the purchase of one or more of the following licenses.

  • J9053A - ProCurve Wireless Services zl 12 RP License provides support for 12 additional ProCurve Radio Ports on a Wireless Edge Services zl Module, up to a maximum of 156 radio ports per module.
  • J9090A - ProCurve Wireless Services zl 48 RP License provides support for 48 additional ProCurve radio ports on a Wireless Edge Services zl Module, up to a maximum of 156 radio ports per module.

» Return to top

Q: Can a J9002A Radio Port License from a ProCurve Wireless Edge Services xl module be converted to the J9053A license for a ProCurve Wireless Edge Services zl module?

A: Yes. Prior to conducting such a transfer, however, be aware that the conversion of an xl License to a zl License is not reversible.

» Return to top

Q: What is the process for converting an xl Radio Port License (J9002A) to a zl Radio Port License (J9053A)?

A: Step-by-step instructions for this one-way conversion may be viewed in the document, Converting xl Radio Port Licenses for use with Wireless Edge Services zl Modules.

» 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 Management and Configuration Guide for the ProCurve Wireless Edge and Redundant Wireless Services zl Modules.

» Return to top

Q: What types of user authentication are possible using the ProCurve Wireless Edge Services zl Modules?

A: The Wireless Edge Services zl Module supports three types of authentication:

  • 802.1X authentication
  • Web-Auth
  • MAC authentication

Alternatively, the Wireless Edge Services zl 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.

» Return to top

Software

Q: What is DFS-2 and how does it affect the functioning of my ProCurve Wireless Edge Services zl Module and radio ports?

A: This applies to US customers only: 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 on Wireless Edge Services zl Modules, and on Wireless Edge Services xl Modules running software version WS.01.11 (or later). These modules disable channels 52, 56, 60, 64 (5.25-5.35 GHz) in the U.S. These channels remain available for use in other countries.

» Return to top

Q: Where can I learn more about the operation and use of the ProCurve Wireless Edge Services zl Module?

A:  The following documents may help:

  • The ProCurve Wireless Edge Services zl Module Management and Configuration Guide is the primary resource for information about the ProCurve Wireless Edge zl module.
  • The Wireless Edge Services zl Module Supplement to the ProCurve zl Switch Management and Configuration Guide provides module and switch interaction information.
  • Some additional insight on the module behavior may also be found in the Release Notes for the module software.

These documents are available on the ProCurve Web site.

» Return to top

Q: How do the capabilities and scalability of the ProCurve Wireless Edge Services zl Modules (J9051A, J9052A) differ from those of the xl Modules (J9001A, J9003A)?

A: The following is a summary, comparing and contrasting the xl and zl modules.

Feature/Function

xl Module on software
WS.01.xx

xl Module on software WS.02.xx

zl Module on software WT.01.xx

Throughput - Unencrypted

290 Mbps

400 Mbps

2000 Mbps

Maximum number of Radio Ports supported

36

48

156

Maximum number of associated stations

1000

4096

4096

Maximum number stations per radio

64

256

256

Maximum number of modules in Redundancy Group

2

12

12

Maximum number of VLANs per module

8

32

32

Radio Port Failover time (Layer 2)

55 sec (typical)

20 sec (typical)

20 sec (typical)

Maximum number of static routes

1000

300

300

Maximum number RADIUS Authentications per second

N/A

15 Internal / 5 LDAP

4 Internal / 3 LDAP

Maximum number of DHCP Lease Grants per second

N/A

15

15

Maximum number of modules in Layer 3 Roaming Group

N/A

12

12

» Return to top

Compatibility

Q: Can ProCurve Wireless Edge Services xl and zl Modules be used together in a network?

A: Redundancy and Layer 3 roaming operation can be integrated as long the xl modules are running the proper software version. For example, Wireless Edge Services xl Modules require software version WS.02.07 (or later) to use these features with zl Modules.

» Return to top

Q: Are there any limitations to the use of ProCurve Wireless Edge Services xl and zl modules together in a redundancy group?

A: The Radio Port capacity limitations of each module should be considered. For example, the zl Module supports up to 156 Radio Ports at first release, while the xl Module with software version WS.02.07 supports a maximum of 48 Radio Ports. Using the xl Module as a failover backup for a zl Module is supported, but some Radio Ports may fail to be adopted. (For the latest information on supported Radio Port limits, visit www.procurve.com.)

» Return to top

Q: Are any of the ProCurve Wireless Edge Services xl and zl features incompatible?

A: Selected features and configurations may not be compatible. For example, zl Modules do not support GRE tunnels. Additionally, the xl Modules allow the uplink and downlink module ports to be a member of the same VLAN; that is not a valid configuration on the zl module.

» Return to top

Troubleshooting

Q: I have lost/misplaced/forgotten the password for access to my ProCurve Wireless Edge Services zl 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 5400zl switch, as follows.
  • ProCurve5406zl>enable
  • ProCurve5406zl#wireless-services <slot #>
  • ProCurve5406zl(wireless-services-d)#erase startup-config

» Return to top

Q: I can’t seem to access the Management Interface. What should I do?

A: The Java interface has changed significantly from the xl module’s WS.01.xx to the WS.02.xx and zl module WT.01.xx software versions. It is recommended that you clear both the Java cache and the IE browser cache immediately following an update or backrev between major versions of the software. Instructions for that process follow (see next question/answer). As of WT.01.03, Internet Explorer version 7 is not supported.

ProCurve strongly recommends that the module’s management should be immediately accessed and the default management password reconfigured.

» Return to top

Q: How do I clear the Java and browser caches?

A: Complete the following steps:

  1. Clear your browser’s cache.
  2. Clear the Java cache.
  3. Close the browser and re-open it.

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.

Follow these steps to clear the cache:

1. Open IE.

Log on screen

Figure 1. IE Browser

2. Select Tools > Internet Options. The Internet Options window is displayed.

Internet options

Figure 2. Tools > Internet Options

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.

6

Figure 3. Delete Files

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. Double-click on on the "Java Control".

Control panel

Figure 4. Control Panel

2. Select Java. The Java Control Panel window is displayed.

  Java control panel

Figure 5. Java Control Panel

3. In the Temporary Internet Files section, click the Settings button. The Temporary Files Settings window is displayed.

  Temporary file settings dialogue box

Figure 6. Temporary Files Settings (Java Control Panel)

4. Click the Delete Files button. The Delete Temporary Files window is displayed.

Delte temporary internet files

Figure 7. Delete Temporary Files (Java Control Panel)

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 zl Module’s Web browser interface:

1. Close and re-open your browser.
2. Enter the IP address (or hostname) of your Wireless Edge Services zl 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>.

Java Applet

Figure 8. Activate the Java Applet

4. After about a minute, the Login screen is displayed.

Wireless services login screen

Figure 9. Login Screen for Wireless Edge Services zl Module Version WT.01.XX

» Return to top

Q: My ProCurve zl Wireless Edge Services Module isn’t succeeding at adoption of my radio ports. What could be wrong?

A: A radio port that has been adopted by a ProCurve Wireless Edge Services xl Module running WS.01.xx software, requires a bootloader update before it can successfully be adopted at Layer 3. Also, a new radio port may require an update to the factory-installed bootloader software, before it can successfully be adopted at Layer 3.

In these cases, 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 zl switch or by connecting to an infrastructure switch in the same Layer 2 network. The adoption time is extended slightly as the new bootloader software loads. When the radio port has been adopted, (the radio port LEDs flash about once every five seconds) the correct radio port bootloader software is installed. You may now finish the process for adopting the radio port at Layer 3 (see “Radio Port Adoption” in the Management and Configuration Guide for the ProCurve Wireless Edge and Redundant Wireless Services zl Modules).

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 may also wish to view the configuration example for “Layer 3 RP Adoption Using DHCP Option 189”, available shortly on the Configuration examples page.

» Return to top

Q: When I purchase an SSL certificate from a Certificate Authority, I am asked for the server type. Which server type should I choose for the Wireless Edge Services zl Module?

A: When purchasing an SSL certificate for the Wireless Edge Services Module, choose “Apache-MOD SSL” as the server type.

» 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:

  1. If DHCP is configured to assign IP addresses and an IP helper is added, or
  2. If an IP helper address is configured and a DHCP scope is added.

» Return to top

Q: I created an “allow any” ACL on my ProCurve Wireless Edge Services zl 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 configuration examples for more specific help on how to accomplish this.

» Return to top

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

Q: Should I configure the time on the host chassis and the ProCurve Wireless Edge Services zl Module? In what way would a time configuration conflict be resolved?

A: Best Practice Recommendation: configure the host ProCurve zl Series Switch to get its’ time from a simple network time server (SNTP) as demonstrated by the example below. The module will synchronize its time when the chassis receives time updates from the time server. In addition to configuring the time zone on the chassis, you will need to indicate the time zone on the module (Network Setup -> Configuration tab -> Time Zone drop down list).

  • ProCurve8212zl>enable
  • ProCurve8212zl#config
  • ProCurve8212zl(config)#sntp server <ip address of your NTP server>
  • ProCurve8212zl(config)#sntp server unicast <or broadcast, depending on server config>
  • ProCurve8212zl(config)#time timezone <number of minutes offset from GMT>

» Return to top

Printable version
Privacy statement Using this site means you accept its terms
© 2010 Hewlett-Packard Development Company, L.P.