User's Manual
Table Of Contents
- System Manual BreezeMAX Extreme
- About This Manual
- Contents
- Chapter 1 - System Description
- 1.1 About WiMAX
- 1.2 WiMAX Network Architecture
- 1.3 BreezeMAX Extreme
- 1.4 Specifications
- 1.4.1 General Modem and Radio
- 1.4.2 3.x GHz BTS
- 1.4.3 5 GHz BTS
- 1.4.4 Sensitivity
- 1.4.5 3.x GHz Antennas
- 1.4.6 5 GHz Antennas
- 1.4.7 Power Supply
- 1.4.8 GPS Antennas
- 1.4.9 Data Communication (Ethernet Port)
- 1.4.10 Configuration and Management
- 1.4.11 Environmental
- 1.4.12 BTS Standards Compliance, General
- 1.4.13 Notes on Maximum Tx Power Limitations for 5 GHz Units Using FCC Country Code:
- 1.4.14 TDWR Interference Avoidance
- Chapter 2 - Installation
- 2.1 Site Deployment Options
- 2.2 BTS Installation
- 2.3 GPS Installation
- 2.4 Indoor Power Supply Installation
- 2.5 Cable Connections
- 2.6 External Antennas Connection
- Chapter 3 - Commissioning
- Chapter 4 - Operation and Administration
- 4.1 BreezeMAX Extreme System Management
- 4.2 The Monitor Program
- 4.3 IP Addresses Configuration
- 4.4 The Main Menu
- 4.5 BTS Menu
- 4.5.1 Show Summary
- 4.5.2 Show Properties
- 4.5.3 Show License Properties
- 4.5.4 Configuration
- 4.5.5 Unit Control
- 4.5.6 Fault Management
- 4.5.7 Performance Counters
- 4.6 ASN-GW Menu
- 4.6.1 AAA
- 4.6.2 Services Menu
- 4.6.2.1 Introduction
- 4.6.2.2 Common Operations in Services Menus
- 4.6.2.3 MSs Services
- 4.6.2.4 Service Profiles
- 4.6.2.5 QoS Profiles
- 4.6.2.6 Multiple Service Flows
- 4.6.2.7 Service Rules
- 4.6.2.8 Classifiers
- 4.6.2.9 Service Groups
- 4.6.2.9.1 Service Group ID
- 4.6.2.9.2 Service Group Name
- 4.6.2.9.3 DHCP Type
- 4.6.2.9.4 Nomadic Mode
- 4.6.2.9.5 Attribute 31
- 4.6.2.9.6 Attribute 32
- 4.6.2.9.7 Attribute 32 Free Text
- 4.6.2.9.8 Interface IP Address
- 4.6.2.9.9 Interface Subnet Mask
- 4.6.2.9.10 Default Gateway
- 4.6.2.9.11 VLAN ID
- 4.6.2.9.12 VLAN Priority
- 4.6.2.9.13 DHCP Server Specific Parameters
- 4.6.2.9.14 Option 82 Parameters
- 4.6.2.9.15 DHCP Relay with Option 82 Specific Parameters
- 4.6.2.9.16 Show DHCP Lease Times
- 4.6.2.10 Service Interfaces
- 4.6.2.10.1 Service Interface ID
- 4.6.2.10.2 Service Interface Name
- 4.6.2.10.3 Forwarding Rule Name
- 4.6.2.10.4 CS Type
- 4.6.2.10.5 VLAN Interface
- 4.6.2.10.6 VLAN Transparency
- 4.6.2.10.7 VLAN ID
- 4.6.2.10.8 VLAN Priority Marking
- 4.6.2.10.9 VLAN Priority
- 4.6.2.10.10 VLAN List
- 4.6.2.10.11 Inner DSCP Marking
- 4.6.2.10.12 Inner DSCP
- 4.6.2.11 Forwarding Rules
- 4.6.2.12 MSs Default Services
- 4.6.3 MAC Access Lists
- 4.7 Sector Menu
- 4.8 BS Menu
- 4.9 Radio Channel Menu
- 4.10 Antenna Menu
- 4.11 GPS Menu
- 4.12 MS Menu
- 4.13 Parameters Summary
- Glossary
Chapter 4 - Operation and Administration ASN-GW Menu
BreezeMAX Extreme 120 System Manual
Embedded Distributed ASN GW Local Authentication - internal NAS is used
for service provisioning and no AAA is required.
External ASN GW - a 3rd party NAS must handle the service provisioning and
also decide if AAA is required.
In order for the RADIUS server to accept requests from its ASN client, a shared
secret is required to be configured on both parties.
For each new network entry, the ASN initiates the creation of an encrypted
EAP-TTLS (EAP-Tunneled Transport Layer Security) tunnel between the user and
the RADIUS server, then continues relaying messages between the two parties
until the tunnel is complete. The purpose of this tunnel is for the user to send its
credentials (username & password) to the RADIUS server, transparent for the
ASN, using a second authentication protocol, MSCHAPv2 (Microsoft
Challenge-Handshake Authentication Protocol version 2).
The RADIUS server then checks the user's credentials against its database and
decides whether or not the user should be accepted and provisioned with services
by the ASN.
Keep-alive and retry mechanisms are implemented on the ASN to overcome
connectivity problems and loss of packets.
When working in internal ASN authentication mode, the settings and flow of the
authentication and service provisioning process are:
1 The user (i.e. MS) needs to have an authentication type (i.e EAP-TTLS) and a
username/password configured in the Registration menu.
2 The ASN requires the setting of the AAA client (server IP, shared secret and
keep-alive settings) and the service definition: Multiple Service Flows and
Service Profiles with all their sub-components.
3 The configuration of the RADIUS server is the most complex and requires the
following:
» Clients database, containing the IPs and shared secrets of all the ASNs
that connect to it;
» Users database, containing the users' credentials (username & password),
the corresponding services to be provisioned (the names of the Service