User's Manual
Table Of Contents
- About This Manual
- Contents
- Figures
- Tables
- Chapter 1 - System Description
- 1.1 Introducing BreezeMAX
- 1.2 Base Station Equipment
- 1.3 Networking Equipment
- 1.4 Management Systems
- 1.5 Specifications
- 1.5.1 Radio
- 1.5.2 Base Station 2.X GHz Antennas (Optional)
- 1.5.3 Base Station 3.x GHz Antennas (Optional)
- 1.5.4 ˘AU-IDU to AU-ODU Communication
- 1.5.5 Data Communication (Ethernet Ports)
- 1.5.6 Configuration and Management
- 1.5.7 Environmental
- 1.5.8 Standards Compliance, General
- 1.5.9 Services
- 1.5.10 Physical and Electrical
- Chapter 2 - Installation Guidelines
- 2.1 Installing the AU-ODU
- 2.2 Installing the Base Station Equipment
- 2.2.1 BST Installation Requirements
- 2.2.2 BMAX-BST-SH Chassis Slot Assignments
- 2.2.3 Power Requirements
- 2.2.4 HOT SWAP Support
- 2.2.5 Power Interface Unit (PIU)
- 2.2.6 Power Supply Unit (PSU)
- 2.2.7 Access Unit Indoor Module (AU-IDU)
- 2.2.8 Network Processing Unit (NPU)
- 2.2.9 Using the Hot Swap Injector/Ejector Handles
- 2.2.10 Installing the Base Station Chassis and Modules
- 2.2.11 Air Ventilation Unit (AVU)
- 2.2.12 Replacing Base Station Components
- 2.3 Installing the ODU Power Feeder
- 2.4 Installing the GPS Adapter
- Chapter 3 - Commissioning
- Chapter 4 - Operation and Administration
- 4.1 BreezeMAX System Management
- 4.2 The Monitor Program
- 4.3 IP Addresses Configuration
- 4.4 ˘The NPU's Main Menu
- 4.5 Base Station Menu
- 4.5.1 Show
- 4.5.2 Configuration
- 4.5.3 Alarms and Traps
- 4.5.4 RADIUS
- 4.5.5 ˘˘˘Licenses
- 4.6 ˘NPU Menu
- 4.7 Radio Cluster Menu
- 4.8 ODU Menu
- 4.9 AU Menu
- 4.9.1 Show Summary
- 4.9.2 Upgrading AU’s SW
- 4.9.3 SW Files in NPU
- 4.9.4 Select
- 4.9.5 AU Slot # Menu
- 4.9.6 Performance Monitoring
- 4.10 SU Menu
- 4.10.1 Show Summary
- 4.10.2 Show Summary by AU
- 4.10.3 Upgrading SU’s SW
- 4.10.4 ˘SW Files in NPU
- 4.10.5 Select by Name
- 4.10.6 Select by MAC Address
- 4.10.7 SU # Menu
- 4.10.7.1 Show
- 4.10.7.2 Unit Control
- 4.10.7.3 Configuration
- 4.10.7.3.1 Registration Parameters
- 4.10.7.3.2 MAC (Standard FDD) Parameters
- 4.10.7.3.3 Phy (Standard FDD) Parameters
- 4.10.7.3.4 Multirate and ATPC Parameters
- 4.10.7.3.5 Voice/Networking Gateways
- 4.10.7.3.6 Ethernet Port
- 4.10.7.3.7 Installer Password
- 4.10.7.3.8 ˘Bridging Parameters
- 4.10.7.3.9 License
- 4.10.7.3.10 Best BST/AU (Advanced Si)
- 4.10.7.3.11 Radio Parameters (Advanced Si)
- 4.10.7.4 Performance Monitoring
- 4.10.7.5 Show MAC Addresses Behind SU
- 4.10.7.6 Delete
- 4.10.8 Add New SU
- 4.10.9 Clear All Configured SU SW Files
- 4.11 Services Menu
- 4.11.1 Introduction to Services
- 4.11.2 Introduction to Filtering Features
- 4.11.3 Common Operations in Services Menu
- 4.11.4 The Services Menu
- 4.11.4.1 General
- 4.11.4.2 Subscribers
- 4.11.4.3 Services
- 4.11.4.4 Service Profiles
- 4.11.4.4.1 Service Profile Name
- 4.11.4.4.2 Service Type
- 4.11.4.4.3 VLAN Transparency Mode
- 4.11.4.4.4 VPL ID
- 4.11.4.4.5 Priority Marking Mode
- 4.11.4.4.6 Priority Marking Value
- 4.11.4.4.7 Forwarding Rule
- 4.11.4.4.8 Priority Classifier (L2 and PPPoE Service Type)
- 4.11.4.4.9 Maximum Number of Voice Calls (L2 and VoIP Service Type)
- 4.11.4.4.10 Service Profile Class
- 4.11.4.5 Forwarding Rules
- 4.11.4.6 Priority Classifiers
- 4.11.4.7 QoS Profiles
- 4.11.4.8 Filtering Rules
- 4.11.4.9 Interface Filtering
- 4.11.4.10 Filtering Examples
- 4.11.4.11 MAC Addresses Deny List
- 4.11.5 Defining Service Profiles
- 4.11.6 Defining Local (Permanent) Services
- 4.11.7 Defining RADIUS Based Services
- 4.11.8 Pre-configured Profiles
- 4.12 NPU Parameters Summary
- Appendix A - Software Upgrade
- Appendix B - Defining Service Profiles for Generic VoIP Gateways
- Glossary
- Index
Base Station Menu
BreezeMAX Modular Base Station System Manual 113
4.5.4 RADIUS
Managing a large number of users creates the need for significant administrative
support together with careful attention to security, authorization and accounting.
The use of RADIUS (Remote Authentication Dial In User Service) enables
operators to manage a single database of users, supporting authentication
(verifying user name and password) as well as configuration information detailing
the type of service to deliver to the user and the traffic that the user transmitted
and received, for billing proposes.
RADIUS is a protocol for carrying authentication, authorization, and configuration
information between a Network Access Server (NAS), which desires to
authenticate its links, and a shared Authentication server. A Network Access
Server operates as a client of RADIUS. The client is responsible for passing user
information to designated RADIUS server(s(, and then acting on the response.
RADIUS servers are responsible for receiving user connection requests,
authenticating the user, and then returning all configuration information
necessary for the client to deliver service to the user.
In BreezeMAX systems, a RADIUS NAS is implemented in each Base Station.
Transactions between the client and RADIUS server are authenticated using
Password Authentication Protocol (PAP) through encryption based on RSA
Message Digest Algorithm MD5 and a Shared Secret, which is never sent over the
network.
The Access-Request is submitted to the RADIUS server via the network. If no
response is returned within a length of time, the request is re-sent a number of
times. Once the RADIUS server receives the request, it validates the sending
client. A request from a client for which the RADIUS server does not have a shared
secret must be silently discarded. If the client is valid, the RADIUS server consults
a database of users to find the user whose User Name matches the request. The
user entry in the database contains the User Password that must be verified.
The SU authentication is a part of the network entry process:
1 User Name and Password should be configured in the SU.
2 All required Service Profiles and theitr components should be configured in the
NPU (see “Defining Service Profiles” on page 235.
3 The RADIUS Authentication server(s) should be configured with the relevant
SU’s details (User Name and Password) and their corresponding services (see
“Defining RADIUS Based Services” on page 236.