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
206 Operation
Chapter 4 - Operation and Administration
The guidelines that should be followed when defining VLAN IDs and related
parameters are:
A specific VLAN ID behind a certain SU can be associated only with a single
Service of a certain Service Type. It is not possible to define two Services of the
same Service Type for the same SU and VLAN ID. However, the same SU and
VLAN ID can be associated with two Services of different Service Types,
excluding the combination of L2 Service and VoIP Service.
For each Service Type, a maximum of one Service that enables forwarding of
untagged packets can be assigned to an SU. Forwarding of untagged packets
is supported when either Hybrid VLAN Mode is On, or Hybrid VLAN Mode is
Off and the VLAN List is empty. It is not possible to define for the same SU two
Services of the same Service Type that enable forwarding of untagged packets.
However, the same SU and untagged packets can be associated with two
Services of different Service Types, excluding the combination of L2 Service
and VoIP Service.
The maximum total number of VLAN IDs behind the same SU is 16 (15 when
there is a Service with Hybrid VLAN Mode On is assigned to the SU).
The combination of VLAN Transparency Service On, Hybrid VLAN Mode Off
and an empty VLAN List means that all packets are forwarded. This
combination should be used only if the Service Provider can ensure that there
will not be conflicts between VLAN IDs used by devices behind the SU and
existing VPL IDs.
To avoid conflicts, a transparent Service Profile cannot be assigned to a Service
if the Service's VLAN ID list includes a VLAN ID that is equal to any of the
already assigned VPL IDs.
The combination VLAN Transparency Mode On, Hybrid VLAN Mode On and an
empty VLAN List means that only untagged frames should be forwarded. Such
a Service cannot be assigned if there is an assigned non-transparent Service
with VPL ID = None.