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
114 Operation
Chapter 4 - Operation and Administration
4 When an SU attempt registering at the NPU, the NPU searches within its local
database whether this is a Permanent SU (defined in the database by its MAC
Address).
If the NPU recognizes the SU as a Permanent one, it provides the Local
(Permanent) Services as defined in the NPU's local database (see “Defining
Local (Permanent) Services” on page 236.
If the SU is not defined as Permanent in the NPU’s database, the NPU
queries the RADIUS server for SU authentication and service provisioning.
5 The RADIUS server searches for the corresponding Service defined for the SU
(based on the User Name and Password).
If it finds the applicable service(s) the RADIUS server replies to the NPU
with the Service parameters (Service Profile Name, VLAN List, Access VLAN
Configuration, VLAN Transparency Mode Option and VLAN Classification
Mode).
If the RADIUS server does not find matching SU’s credentials or defined
service(s), it replies to the NPU with a reject message.
6 According to the response from the RADIUS server, the NPU either
authenticates the SU and provides the appropriate service(s) or rejects the SU.
7 Part of the information sent from the RADIUS server can include the
Authentication Time Out. Before the end of this time the NPU should
re-authenticate the SU with the RADIUS server. This allows the operator to
stop service for a customer even if the SU was not reset and the network entry
process was not re-started.
A RADIUS server can be used for authentication purposes only, for accounting
purposes only, or for both authentication and accounting purposes. Up to two
servers of each type can be defined. Each server of each type
(Authentication/accounting) can be defined as either Primary or Secondary. Only
one server of each type can be defined as Primary. If two servers of a certain type
are defined, then upon first trial of an authentication/accounting transaction the
NPU will attempt to communicate with the Primary server of the relevant type
(provided the server’s Operation Status is Up). If it cannot communicate with the
Primary server, it will attempt communicating with the other server (and vice
versa). Upon succeeding to communicate with a certain server, this server is
defined as Active (and the other one as Standby). As long as the NPU succeeds to
communicate with an Active Authentication/Accounting server, it will continue
using it for authentication/accounting transactions.