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-45
Introduction
ProCurve Wireless Edge Services xl Module
Before creating a certificate or certificate request, the Wireless Edge Services
xl Module must generate a public/private key pair. The module can create
Rivest-Shamir-Adleman (RSA) keys of between 1024 and 2048 bytes. Each
certificate can use a unique key pair, or multiple certificates can share a key pair.
The Wireless Edge Services xl Module uses certificates for several purposes:
■ HTTPS access—The module’s server certificate authenticates the mod-
ule to your Web browser.
■
RADIUS authentication services
—802.1X authentication with EAP
requires mutual authentication. In other words, the module’s internal
RADIUS server must send a server certificate and authenticate to
supplicants.
■ Autokey authentication for secure Network Time Protocol
(NTP)—The module sends its certificate to the secure NTP server to
authenticate itself and generate keys to secure NTP exchanges.
Because the Wireless Edge Services xl Module can store multiple trustpoints,
you can select different certificates for different functions.
GRE Tunnels
A GRE tunnel is a virtual point-to-point connection between two devices, or
tunnel endpoints. A tunnel endpoint selects traffic for transmission over the
tunnel. It then encapsulates that traffic in a GRE header and in a delivery IP
header, which is addressed to the remote tunnel endpoint. After receiving the
traffic over the tunnel, the remote endpoint decapsulates the traffic and sends
it to its original destination.
A GRE tunnel isolates traffic as it is sent between the two tunnel endpoints.
Intervening devices examine only the delivery header, not the encapsulated
packet. The GRE tunnel thus protects the encapsulated packet to some
degree; however, it does not provide the security of an IP Security (IPSec) or
Secure Sockets Layer (SSL) tunnel.
On the Wireless Edge Services xl Module, you can create GRE tunnels to any
ProCurve Networking device that supports GRE. After creating the tunnel,
you associate it with a particular WLAN. All traffic that arrives on that WLAN
is transmitted over the tunnel.
You might use a GRE tunnel when your wireless network is some distance
from the private network that wireless users should access. For example, you
could tunnel WLAN traffic to a router at a remote site. Remember that a GRE
tunnel does not provide rigorous security and that the module decrypts frames
received from the WLAN before forwarding them over the tunnel.