Wireless Edge Services zl Module Release Notes WT.01.39

Support Notes and Clarifications

Release WT.01.03

Note If you do not correctly configure the RADIUS server, you can lock yourself out of the Wireless Edge

Services zl Module Web browser interface.

To fix the problem, access the module CLI through the wireless services-enabled switch. Enter this

global configuration mode command to have the module authenticate Web-Users against its local list:

Syntax: aaa authentication login default local

Then configure at least one user in the local list:

Syntax: username <username> password <password>

The password must be between 8 and 32 characters.

Then assign the user rights sufficient to correct the problem. For example:

Syntax: username <username> privilege superuser

Special Characters for the ACL ID Field

As indicated in the chapter “Access Control Lists (ACLs)” of the Management and Configuration Guide (5991-8626), string

names for ACL IDs may contain alphanumeric characters, but spaces and non-alphanumeric characters are not allowed.

However, the following special characters may be used:

` ~ ! @ # $ % ^ & * ( ) _ - { } [ ] | : ; ' < > , .

Correction: SNMP v3 Default Password

The chapter “Configuring the HP Wireless Edge Services zl Module” of the Management and Configuration Guide (5991-

8626) incorrectly states that for the snmptrap user, the default password is “procurve”. Instead, the default password is

“trapuser.”

Clarification: For Layer 3 Adoption, DHCP Server Option 189 Requires Value Type ‘String’

You must properly set up your DHCP server to support Layer 3 adoption of Radio Ports. Refer to your DHCP server

documentation for instructions on adding private options and the configurations that your Radio Ports will receive.

For adopting Radio Ports at Layer 3, you must set up the DHCP option so that its code is 189, and its value type is string (instead

of Byte or IP).

Refer to the zl Module’s Management and Configuration Guide for more information.

Correction: Stations per Module in a Layer 3 Mobility Domain

The zl Module’s Management and Configuration Guide (February 2008), page 1-85, incorrectly states that a Layer 3 Mobility

Domain can include up to 12 modules, each of which can support up to 500 stations. Instead, the number of local stations per

module is 4096.

Correction: Disabling TKIP Countermeasures

TKIP countermeasures are used to prevent “man-in-the-middle” TKIP attacks by disabling client connections for a short period

of time. In some cases, you may want to disable TKIP Countermeasures. The zl Module’s Management and Configuration

Guide (February 2008) includes a command that is not available for disabling TKIP Countermeasures:

no support wireless tkip-countermeasures