Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater
Table Of Contents
- ProCurve Wireless Edge Services xl Module and ProCurve Redundant Wireless Services xl Module
- Title Page
- Copyright and Disclaimer Notices
- Table of Contents
- 1. Introduction
- Contents
- ProCurve Wireless Edge Services xl Module
- Wireless Networks and WLANs
- The Interface Between the Wireless and Wired Networks
- Layer 2 and Layer 3 Operation
- Determining the Layer 3 Services Your Wireless Edge Services xl Module Should Provide
- IP Routing
- DHCP Services
- Security Features
- Traffic Management and QoS
- Management Capabilities and sFlow
- RP Licensing
- Radio Ports
- Redundancy Groups
- Layer 2 and Layer 3 Roaming Between RPs and Modules
- 2. Configuring the ProCurve Wireless Edge Services xl Module
- Contents
- Management Interfaces
- Radio Port Adoption
- System Maintenance
- Software Images
- Configuration Files
- Viewing Configuration Files
- Transferring, or Copying, Files
- Transferring Configuration Files from an FTP or TFTP Server to the Wireless Edge Services xl Module
- Transferring Configuration Files from the Wireless Edge Services xl Module to Another Destination
- Managing the Directory Structure and Browsing for Files
- Deleting a Configuration File
- Returning the Startup-Config File to Factory Default Settings
- Update Server
- Password Encryption
- SNMP Traps and Error Reporting
- Radio Port Licenses
- Setting System Information-Name, Time, and Country Code
- Enabling Secure Network Time Protocol (NTP)
- Digital Certificates
- 3. Radio Port Configuration
- 4. Wireless Local Area Networks (WLANs)
- Contents
- Overview
- Configuration Options: Normal Versus Advanced Mode
- Configuring a WLAN
- VLAN Assignment
- Traffic Management (QoS)
- 5. Web Authentication for Mobile Users
- 6. IP Services-IP Settings, DHCP, and DNS
- 7. Access Control Lists (ACLs)
- 8. Configuring Network Address Translation (NAT)
- 9. Fast Layer 2 Roaming and Layer 3 Mobility
- 10. Redundancy Groups
- Contents
- High Availability for Wireless Services
- Configuring a Redundancy Group
- Configuring Redundancy Group Settings
- Adding Members to the Redundancy Group
- Enabling Redundancy
- Viewing Information about the Redundancy Group
- Viewing Information about the Other Members of the Redundancy Group
- Setting up Adoption Preference IDs to Control RP Adoption
- Reverting RPs Adopted by a Standby Member to the Active Member
- 11. RADIUS Server
- Contents
- Overview
- RADIUS Authentication
- Configuring the Internal RADIUS Server
- Choosing the Authentication Type for 802.1X/EAP
- Specifying the RADIUS Server’s Digital Certificate
- Choosing the Source for User Credentials
- Configuring the Local RADIUS Database
- Using LDAP for the Data Source
- Specifying a Domain Proxy RADIUS Server
- Specifying Global RADIUS Settings
- Adding RADIUS Clients
- Starting and Stopping the RADIUS Server
- Enabling Authentication to the Internal Server on a WLAN
- Configuring the Internal RADIUS Server
- RADIUS Accounting
- 12. Configuring Tunnels with Generic Routing Encapsulation
- 13. Wireless Network Management
- Contents
- Overview
- Monitoring the Wireless Network
- AP Detection
- Configuring Station Intrusion Detection
- Logging and Alarms
- MAC Filters (Local MAC Authentication)
- Network Self Healing
- 14. sFlow Agent
- Appendix A - ProCurve Wireless Services xl Module Command Line Reference
- Contents
- Overview
- Manager Commands
- Global Commands
- Interface Commands
- Wireless Commands
- Show Commands
- Show Commands (All Contexts)
- show alarm-log
- show commands
- show crypto
- show debug
- show file
- show flash
- show history
- show hostname
- show interfaces
- show ip
- show licenses
- show logging
- show management
- show password-encryption
- show redundancy-group
- show redundancy-history
- show redundancy-member
- show running-config
- show snmp
- show sntp
- show startup-config
- show terminal
- show time
- show timezone
- show upd-server
- show upgrade-status
- show version
- show vlans
- Show Commands (Wireless)
- show wireless ap-detection-config
- show wireless approved-aps
- show wireless channel-power
- show wireless config
- show wireless ids
- show wireless mac-auth-local entries
- show wireless phrase-to-key
- show wireless radio-config
- show wireless radio-statistics
- show wireless radio-status
- show wireless regulatory
- show wireless rp-images
- show wireless rp-status
- show wireless rp-unadopted
- show wireless self-heal-config
- show wireless station
- show wireless station-statistics
- show wireless unapproved-aps
- show wireless web-auth-config
- show wireless wireless-module-statistics
- show wireless wlan-config
- show wireless wlan-statistics
- Support Commands
- Support Commands (All Contexts)
- Support Commands (Wireless)
- Index
- Back Cover
1-8
Introduction
ProCurve Wireless Edge Services xl Module
Communicating with RPs: Radio Port VLANs
The Wireless Edge Services xl Module uses a Radio Port VLAN to send traffic
to and receive traffic from the RPs it adopts.
The RPs are designed to isolate traffic that they transmit into your network
until the Wireless Edge Services xl Module can control this traffic. An RP
encapsulates each wireless frame, leaving the 802.11 header and any encryp-
tion intact, and forwards it to the module on the Radio Port VLAN.
The Radio Port VLAN can be established in one of three ways:
■ with auto-provisioning on the wireless services-enabled switch
■ manually on an infrastructure switch (or, if you want, on the wireless
services-enabled switch)
■ dynamically on either a wireless services-enabled switch or an infrastruc-
ture switch based on a VLAN assignment stored on a RADIUS server
Note The rule that the Wireless Edge Services xl Module receives RP traffic on its
downlink port and a Radio Port VLAN has one exception. When an RP is
adopted at Layer 3, it can communicate with the module on either the uplink
or the downlink port. The only rule for the VLAN on which an RP is adopted
at Layer 3 is that this VLAN be tagged on only one of the internal ports.
For more information on Layer 3 adoption, see “Communications Between an
RP and the Wireless Edge Services xl Module: Layer 2 and Layer 3 Adoption”
on page 1-67.
Using Auto-Provisioning to Establish a Radio Port VLAN. When you
install a Wireless Edge Services xl Module in a 5300xl Switch, auto-provision-
ing is enabled by default: the switch automatically establishes VLAN 2100 as
the default Radio Port VLAN, or the Auto-VLAN. (If VLAN 2100 is unavailable,
the switch uses the next available VLAN number.)
The switch also automatically configures the module’s internal downlink port
as a tagged member of this Radio Port VLAN. (The port is a tagged member
because the module drops all untagged traffic.)
When an RP is connected to a port on the wireless services-enabled switch,
the switch uses Link Layer Discovery Protocol (LLDP) to identify itself to the
switch. The switch then automatically configures the port as an untagged
member of the Radio Port VLAN. (Because the RP does not support 802.1Q,
the port must be an untagged member of the VLAN.)