Quantum

Quantum 1000 Base Station
User Guide
Quantum 1000 Base Station User Guide
Rev 1.2,
1. Page 1 of 146
NOTICE
It is hoped that this document will be useful in understanding and using the PureWave System. Please
note that the information provided herein is subject to change without notice.
Always refer to the current set of Release Notes for the most up to date information and a description of
the current features as they relate to the PureWave system. These may be different to the information
contained within this User Guide.
Rev 1.2,
1. Page 2 of 146
REGULATORY NOTICE
It is the intention of PureWave Networks to ensure that this equipment is tested to comply with the limits
for a class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide
reasonable protection against harmful
harmful interference in a residential installation. This equipment generates,
uses and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However, there is
is no guarantee
that interference will not occur in a particular installation. If this equipment does cause harmful
interference to radio or television reception, which can be determined by turning the equipment off and
on, the user is encouraged to try to correct the interference by one or more of the following measures:
Re-orient
Re
orient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which
which the receiver is
connected.
Consult the dealer or an experienced radio/TV technician for help.
Shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC
regulations.
Changes or modifications not expressly approved iin
n writing by PureWave Networks may void the user's
authority to operate this equipment.
Note:
This device must be professionally installed

installed.
Rev 1.2,
1. Page 3 of 146
PROPRIETARY STATEMEN
STATEMENT
T
PureWave Networks, 2003
2003-200
2009.. All rights reserved. PureWave Networks has prepared this
manual for use by PureWave Networks personnel, licensees, customers and customers of customers.
The information contained herein is the property of PureWave Networks a
and
nd shall neither be reproduced
in whole nor in part without prior written approval from PureWave Networks.
PureWave Networks reserves the right to make changes without notice to the specifications and materials
contained herein, and shall not be responsible
responsible for any damages caused by reliance on the material
presented, including, but not limited to, typographical, arithmetic and listing errors.
Warranty Statement
Hardware
ardware
PureWave Inc (PureWave or the Company) warrants to the end
end-user
user (Customer) that this hardware
product will conform in all material respects to the specifications provided with the hardware and will be
free from defects in workmanship and materials, under normal use and service, for a period of 365 days
from the date of original shipm
shipment
ent by PureWave.
PureWave's sole obligation under this limited warranty shall be, at PureWave's option, to repair the
defective product or part, deliver to Customer an equivalent product or part to replace the defective item,
or if neither of the two for
foregoing
egoing options is reasonably possible, refund to Customer the purchase price
paid for the defective product. All products that are replaced will become the property of PureWave.
Replacement products may be new or reconditioned. PureWave's obligations hereunder
hereunder are conditioned
upon the returned of affected articles in accordance with PureWave's Return Material Authorization
(RMA) procedures.
Subject to the limitations and conditions herein and in the Supply Agreement, after Customer has
completed the steps
steps outlined below in Section 2, PureWave will evaluate each returned Product
roduct and will
use reasonable commercial efforts to either, in its discretion, repair or replace products confirmed by
PureWave as non-conforming
non conforming that are covered under the warranty provided
rovided in the Supply Agreement.
PureWave shall be responsible for shipping the repaired or replaced Product to Customer. PureWave will
use reasonable commercial efforts to ship
sh repaired or rep
replacement
lacement Product within twenty (30) business
days of its receipt,
receipt, however, the allegedly non-conforming
non conforming Product must be received
received by PureWave before
any replacement unit will be shipped.
shipped
The above warranty will also apply to any replaced or repaired product for 90 days from the date of
shipment from PureWave of th
the
e replaced or repaired product, or the remainder of the initial warranty
period, whichever is longer.
Software
PureWave warrants to the Customer that for a period of ninety (90) days from your receipt of the Product
(the Warranty Period) the Software will
will perform substantially in accordance with the Documentation.
If the Software fails to comply with the warranty set forth above, your exclusive remedy will be, at the
option of PureWave (i) a reasonable effort by PureWave to make the Software perform substantially
substantially in
accordance with the Documentation, or (ii) return of the purchase price. This limited warranty applies only
if you return all copies of the Product, together with proof of purchase, to PureWave during the Warranty
Period.
This limited warranty
warranty is VOID if failure of the Software is due to modification of the Software not made by
PureWave, or the abuse or misapplication of the Software. PureWave does not warrant that the Software
is error free, that the Customer will be able to operate the Soft
Software
ware without problems or interruptions or
Rev 1.2,
1. Page 4 of 146
that the Software or any equipment, system or network on which the Software is used will be free of
vulnerability to intrusion or attack.
For further details of the terms and conditions of PureWave's obligations ffrom
rom a software perspective
please refer to PureWave Software Maintenance Program.
Additional Conditions
Notwithstanding anything else herein or otherwise, PureWave reserves the right to establish amendments
to this RMA Policy from time to time. Further,
Furth PureWave Technical Support may prefer to troubleshoot
the wireless link with an onsite Customer technician while the Products are in their original nonnon
conforming state. This process might assist Customer in understanding and troubleshooting the issue.
issue If
PureWave was not afforded the opportunity to troubleshoot an allegedly non-conforming
non conforming Product in
original non-conforming
non conforming state, PureWave may approve or reject the RMA request in its sole discretion,
and such Products are not eligible for advance repl
replacement.
No Fault Found
Notwithstanding Sections 1.1 and 1.2 above, if
i PureWave cannot duplicate any alleged non-conformity
non conformity,
the Product will be returned to the Customer as "No Fault Found." PureWave reserves the right to charge
a testing fee in connect
connection
ion with a returned product that PureWave determines as No Fault Found, and
any such
uch payment
p
must be received by PureWave prior to return shipment of the applicable Product to
Customer.
Warranty Limitations
PureWaves warranties do not apply to any product
product (hardware or software) which has (a) been subjected
to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by
anyone other than PureWave, (c) been used for or subjected to applications, environments, or physical
physical or
electrical stress or conditions other than as intended and recommended by PureWave, (d) been
improperly stored, transported, installed, or used, or (e) had its serial number or other identification
markings altered or removed.
Warranty Disclaimer
Disclai
PURWAVES SPECIFIC WARRANTIES SUMMARIZED ABOVE ARE THE ONLY WARRANTIES GIVEN
BY PUREWAVE WITH RESPECT TO ITS PRODUCTS (HARDWARE AND SOFTWARE) AND ARE
GIVEN IN LIEU OF ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED,
STATUTORY, OR ARISING BY CUSTOM,
CUSTOM, TRADE USAGE, OR COURSE OF DEALING, INCLUDING
WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, AND PUREWAVE DISCLAIMS ANY AND ALL OTHER WARRANTIES TO
THE MAXIMUM EXTENT PERMITTED BY LAW. Without limiting the generality of the foregoing
sentence, PureWave makes no warranty or representation, either expressed or implied, as to, and
disclaims all liability and responsibility for, (a) the operation, compliance, labeling, or packaging of any of
its products under
under the laws of any jurisdiction outside of the United States of America and (b) the
regulatory compliance of any products in any jurisdiction in which it has not specifically identified
compliance or the use of any product in any jurisdiction in any manne
mannerr other than as contemplated in the
regulatory certifications and approvals for that product in that jurisdiction. To the extent an implied
warranty cannot be excluded, such warranty is limited in duration to the warranty period. The disclaimer
and exclusion
exclusion applies even if the express warranty fails of its essential purpose.
Rev 1.2,
1. Page 5 of 146
Obtaining Warranty Service

RMA Number
Customer must contact the Company, by sending an e-mail to support@pwnets.com to obtain warranty
service
ce authorization. When contacting PureWave for support, please be prepared to provide the product
description and serial number and a description of the problem. The Customer will be expected to
complete a Return Material Authorization (RMA) form to init
initiate
iate the request. Full instructions as to how
to complete and where to send the form are provided on the form. Date of proof of purchase from
PureWave will be required.
Products returned to PureWave Inc must be pre-authorized
pre authorized by PureWave with a Return Material
Mat
Authorization (RMA) number and sent prepaid and packaged appropriately for safe shipment. The
Customer requesting the
the RMA will be the exporter. The exporter is responsible to ship RMA equipment to
PureWaves address and has to bear the cost and risk involved in bringing the goods to PureWaves
location.
Risk of loss in return shipment will be borne by Customer, and it is recommended that returned goods be
insured and/or sent by a method that provides for tracking of the package. Responsibility for loss
l
or
damage does not transfer to PureWave until the returned item is received by PureWave. Provided that
PureWave determines that the item is actually defective, the repaired or replaced item will be shipped to
Customer, at PureWave's expense, (1) not later
later than thirty (30) days after PureWave receives the
defective product or (2) to the terms of a separate written agreement with PureWave.
If the allegedly non-conforming
non conforming P
Product
roduct is not received by PureWave within thirty (30) days of Customer
initiating the RMA request
request,, the RMA process for that Product will be deemed cancelled.
RMA Status
Customer may also obtain tthe
he status of their RMA request(s) by sending an e-mail to
support@pwnets.com referencing
ing their assigned
assigned RMA N
Number
umber(s).
Customer Obligations
No product will be accepted for repair or replacement by P
PureWave
ureWave without a RMA number. The product
must be returned to PureWave
PureWave,, properly packaged to prevent damage, shipping and handling charges
prepaid, with the RMA number prominently displayed on the outside of the container. If PureWave
P
determines that a returned product is not defective or is not covered by the terms of the warranty, the
Customer will be charged a service charge and return shipping charges
The following table 1 is a summary of the conditions and charges that PureWave reserves the right to
levy.
RMA Related
Repair and return
Shipment of unit to PureWave
Regular Shipment to Customer
Expedited shipment to Customer
No Fault Found
Warranty for repaired and or replaced
product
Under Warranty
No charge, PureWave pays
Customer pays
No charge,
rge, PureWave pays
Customer pays the additional cost of the
expedited shipping
PureWave reserves the right to levy a charge
Remainder of the orginal warranty or 90 days
Table 1 Summary of PureWave RMA Conditions and Charges
Rev 1.2,
1. Page 6 of 146
Out of Box Failure (OBF) / Dead on Arrival (DOA)

In the event a product becomes entirely inoperable within the first forty
forty-eight
eight (48) hours of the initial
installation of the product, and such installation takes place within ninety (90) days after the date of
shipment from PureWave, the Customer may request that the unit be considered as an Out Box Failure
(OBF) or Dead on Arrival (DOA).
PureWave will consider an OBF or DOA as being eli
eligible
gible to be considered for an advance replacement
request. The conditions for such a request are as outlined below in section 4.
Advance Replacement
In some unique situations, PureWave may consider
consider, at its sole discretion on a case-by-case
case
case basis, an
advance
dvance replacement request for a non-conforming
non conforming Product that is still covered under its warranty period.
Conditions
The following conditions apply to advance replacements
replacements:
(i)
PureWave has a suitable equivalent replacement unit available.
(ii)
Customers netw
network
ork is experiencing a severe degradation or a complete outage.
outage
(iii)
Customer has complied with the RMA procedures provided herein
(iv)
PureWave reserves the right to levy a charge for the processing and handling of the advance
replacement request. To waive this charge
charge will be the sole discretion of the Senior VP of Sales.
(v)
If expedited shipping is required then Customer pays for all expedited shipping and handling
charges that are in excess of the regular shipment charges. To waive this charge will be the sole
discretion of the Senior VP of Sales.
discretion
(vi)
When an advance replacement is provided and Customer fails to return the original product to
PureWave within fifteen (15) days after shipment of the replacement, PureWave will charge the
Customer for the replacement product,
product at list price.
(vii)
The shipment of advance replacement products is subject to local legal requirements and may
not be available in all locations.
Replacement Timing
PureWave will use reasonable commercial efforts to ship advance replacement Products within five (5)
business days after PureWave
PureWaves
s confirmation that advance replacement is appropriate. PureWave shall
not be responsible for shipping delays if any of conditions herein are not met.
Out of Warranty
For products that are out of warranty, the repair
repair of such products will be subject to a repair fee. In
addition, any request for the Advance Replacement of product that is out of warranty will be subject to not
only the repair fee but additional fees as well. Please contact PureWave for further details.
detai
PureWave does offer extended warranties and enhanced service options for its Customers who desire
those enhanced features. Please contact PureWave for further information about these options
ASSISTANCE
For assistance, contact your nearest PureWave Networks Sales and Service office.
Additional information is available on the PureWave Networks website at http://www.pwnets.com.
http://www.pwnets.com
For Customer Service call: 650
650-528--5200,
5200, or Email: support@pwnets.com.
Rev 1.2,
1. Page 7 of 146
SAFETY PRECAUT
PRECAUTIONS
IONS
When installing this equipment, observe the following precautions to minimize the danger of personnel
injury:
Danger:
NEVER install equipment if there is a chance of lightning or other adverse weather conditions.
NEVER install in a wet location unless

unless the equipment is specifically designed for wet locations.
NEVER touch uninsulated wires or terminals unless the wire has been disconnected at the
Network interface.
ALWAYS use caution when installing or modifying cables.

ESD Warning:
WARNING: Always as
assume
sume that all components and assemblies are static sensitive and always
follow local ESD
ESD-prevention
prevention guidelines to prevent equipment damage.
EXTERNAL POWER SOURCE:
WARNING: For any external power supply that provides the power source for the PureWave
equipment, replace any power supply fuse with the same rating or equivalent, otherwise
equipment,
PureWave Networks will not be responsible for any subsequent damage to its equipment.
Use normal caution when installing or modifying cables. Dangerous voltages may be present.
present. It is
also considered imprudent to install during a lightning storm.
Always disconnect all lines and power connections before servicing or disassembling this
equipment.
For performance and safety reasons, only power supplies listed for use with telephone
telephone equipment
by a Nationally Recognized Testing Laboratory (NRTL) should be used with equipment.
Refer to the installation section of the appropriate instruction manual for the unit you are installing
for:
o Cabling information
o Proper connections
o Grounding information
All wiring external to the product(s) should follow the provisions of the current edition of the
National Electrical Code.
WARNING:
These units contain no user serviceable components. Only authorized Service Personnel should service
or repair these units. "Use only isolated Class 2 Power Source, Rated 48V dc 5.0A Minimum."
Rev 1.2,
1. Page 8 of 146
TABLE OF CONTENTS
Warranty Statement ................................
................................................................
................................................................
....................................... 4
.......................................
Hardware ................................
................................................................
................................
................................................................
................................................................
...................................................4
...................................................
Software................................
................................................................
................................
................................................................
................................................................
.....................................................4
.....................................................
Additional Conditions ................................................................
................................................................................................
................................................................................................
................................ 5
.................................
No Fault Found ................................................................
................................................................................................
................................................................
..........................................................................
..........5
Warranty Limitations ................................................................
................................................................................................
................................................................................................
................................ 5
..................................
Warranty Disclaimer ................................................................
................................................................................................
................................................................................................
................................ 5
..................................
Obtaining Warranty Service................................

................................................................
..........................................................
.......................................................... 6
RMA Number ................................................................
................................................................................................
................................................................
.............................................................................
.............6
RMA Status................................
................................................................
................................
................................................................
................................................................
................................................6
................................................
Customer Obligations ................................................................
................................................................................................
................................................................................................
................................6
Out of Box Failure (OBF) / Dead on Arrival (DOA) ......................................................

...................................................... 7
Advance Replacement ................................
................................................................
................................................................
..................................................................
................................ 7
Conditions ................................
................................................................
................................
................................................................
................................................................
..................................................7
..................................................
Replacement Timing ................................................................
................................................................................................
................................................................................................
................................ 7
..................................
Out of Warranty ................................................................

................................................................................................
.............................................................................
............................................. 7
1. Introduction................................................................
................................................................................................
............................................................................
............................................ 11
1.1
1.2
1.3
Overview ................................................................
................................................................................................
................................................................
......................................................................
......11
System Components ................................
................................................................
................................................................
...................................................12
...................................................
Scope................................................................
................................................................................................
................................................................
...........................................................................
...........13
2. Base Station
Stat
................................................................................................
................................................................
...........................................................................
........................................... 14
2.1
Overview ................................................................
................................................................................................
................................................................
......................................................................
......14
2.2
MAC Software Architecture ................................
................................................................
................................................................
.........................................................................
.........14
2.3
Enclosure ................................................................
................................................................................................
................................................................
.....................................................................
.....15
2.4
External Connections ................................
................................................................
................................................................
..................................................17
..................................................
2.5
Power................................................................
................................................................................................
................................................................
...........................................................................
...........20
2.6
GPS ................................
................................................................
................................
................................................................
................................................................
.............................................................................
.............26
2.7
Antenna ................................................................
................................................................................................
................................................................
.......................................................................
.......28
2.7.1 Antenna Mounting Kit ................................
................................................................
................................................................
..............................................30
..............................................
2.8
Ethernet ................................................................
................................................................................................
................................................................
.......................................................................
.......32
2.8.1 Weather Protection of the Ethernet Connector ................................................................
.......................................................................
.......33
3. Grounding and Lightning Requirements .............................................................

............................................................. 37
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
Lightning
ning Protection Installation Components ................................................................
.............................................................................
.............37
Lightning Rod ................................................................
................................................................................................
..............................................................................................
..............................38
Down Conductor ................................................................
................................................................................................
..........................................................................................
..........................39
Co-axial
axial and/or Cat 5 Cable Shield Grounding ................................................................
...........................................................................
...........39
Grounding and Bonding................................
................................................................
................................................................
...............................................39
...............................................
Recommended Connection of a Bonded G
Ground ................................................................
.......................................................................
.......39
Single Point Grounding Concept ................................
................................................................
................................................................
................................ 40
.................................
Lightning and Surge Protection ................................
................................................................
................................................................
...................................................................
................................ 41
4. Weather Protection ................................

................................................................
................................................................
................................................................ 45
4.1
4.2
Weather Sealing ................................................................

................................................................................................
..........................................................................................
..........................45
Anti-Seize ................................................................
................................................................................................
................................................................
....................................................................
................................ 48
5. Base Station Operations and Management ............... Error! Bookmark not defined.
5.1
Overview ................................................................
.......................................................................................
....................... Error! Bookmark not defined.
Rev 1.2,
1. Page 9 of 146
5.2
Connect to the Base Station ................................
.........................................................
......................... Error! Bookmark
Bookmark not defined.
5.3
Base Station Configuration ................................
...........................................................
........................... Error! Bookmark not defined.
5.4
Base Station Software Upgrade ................................
................................................... Error! Bookmark not defined.
5.4.1 Overview ................................................................
...................................................................................
................................
Error! Bookmark not defined.
5.4.2 SoC Software Upgrade................................
.............................................................
............................. Error! Bookmark not defined.
5.4.3 Linux Software Upgrade ................................
...........................................................
........................... Error! Bookmark not defined.
5.5
Base Station General Operating Status .......................................
................................
5.6
Subscriber CPEs Operational Status ................................
........................................... Error! Bookmark not defined.
5.7
Base Station Statistics ................................
................................................................
.................................. Error! Bookmark not defined.
6. CPE Provisioning ................................

........................................................
........................ Error! Bookmark not defined.
6.1
6.2
6.3
6.4
Quality of Service (QoS) Profile................................

Profile....................................................
.................... Error! Bookmark not defined.
ARQ/HARQ Profile ................................
................................................................
....................................... Error! Bookmark not defined.
Client Profile ................................................................
.................................................................................
................................
Provisioning CPE ................................................................
..........................................................................
................................
Rev 1.2,
1. Page 10 of 146
1.
Introduction
1.1
Overview
PureWave Networks develops carrier-class

carrier class WiMAX 802.16e compliant Base Station equipment.
PureWaves use of advanced multi
multi-antenna
antenna technologies with software radio architecture
architecture enables
delivery of quadruple-play
quadruple play services (voice, video, data, and mobility) that are competitive with DSL and
Cable services. This equipment is the most spectrally
spectrally-efficient,
efficient, range-extending,
range extending, wireless broadband
metropolitan
metropolitan-area-networking
networking equipment in its class available in the world today.
The PureWave solution consists of four major elements:
PureWave Quantum 1000 Base Station (BS)
Subscriber customer premises equipment (CPE)
Quad Antenna panel
Element management system (EMS).

The Architecture Reference
Reference Model is shown in figure 1. The Base Station Sector supports the wireless
transfer of IP (Internet Protocol) packet data and communicates wirelessly to customer premise
equipment (CPE) terminals. The interface to the ASN
ASN-GW
GW (access service network gateway) adheres to
IETF RFCs, and Ethernet standards. The Element Management System (EMS) supports operations,
commissioning and network performance and characterization functions.
The Quantum 1000 Base Station provides standard WiMax smart antenna support:
supp
AAS processing (beam forming and null steering)
AMC like subchannel assignments

AMC-like
The system uses advanced technology to realize exceptional performance gains:
Fast transmit/receive compensation necessary for channel reciprocity for mobility,
Complexit reducing algorithms that allow more than 2 antennas per sector,
Complexity-reducing
Processing algorithms that virtually eliminate interference instead of beam steering algorithms
that provide limited benefits and do not scale to multi
multi-cell
cell deployments, and
Flexibility to grow
grow coverage by adding sectors in a compact and modular fashion.
A Quantum 1000 Base Station provides 8 times the spectral efficiency and significant link gain relative to
standard WiMax
WiM Wave--2 solutions.
The benefits are:
High capacity deployments using

using fewer channels,
Reduced or no cell planning,
Fewer base stations are needed to cover a region, and
Improved user performance.

ase Station
tation is highly modular. The key comp
components
onents are power units, Linux processing card, network
The Base
processing cards, and
and RF modules for interfacing to available frequency bands. The Base Station
connects to multiple single
single-antenna
antenna units or a multi
multi-antenna
antenna radome.
Rev 1.2,
1. Page 11 of 146
Figure 1 - Architecture Reference Model.
1.2
System Components
The PureWave System is composed of a Base Station (which is itself connected to an antenna or
antenna array) and subscriber stations (also known as customer premises equipment (CPE)), which
connect to each other through an air interface (airlink) and to their respective networks (figure 2). Base
Station connect to their customer or provider networks, also known as backhaul networks, via a provider
interface, whereas CPE connect to their subscriber or user networks through a subscriber interface.
ha hardware, software, and mechanic
mechanical
al characteristics that support their functional and
A Base Station has
performance requirements. Base Station and CPEs interconnect with each other and their respective
networks via sets of network, MAC, and PHY protocols.
Rev 1.2,
1. Page 12 of 146
Provider
(aka
aka Customer
Customer)
Base Station Sector
Provider Interface
(Backhaul
Backhaul)
Subscriber Station
(CPE)
Base Station
Subscriber
(aka User)
CPE
Subscriber Interface
HW
Layers
Layers/
Protocols
Air Interface
(Airlink))
SW
Mechanical
Network
MAC
PHY
Figure 2 - General View of System Components
1.3
Scope
This document is intended to be used by wireless broadband installation engineers. It contains

information needed to install and connect a Quantum 1000 Base Station and Antenna Assembly
The Quantum 1000 Base Station is designed
designed to be plug
plug-and-play direct from PureWave Networks;
however, guidance is given as to how to assess general system integrity and operational readiness upon
initial power-up.
power
Rev 1.2,
1. Page 13 of 146
2.
Base Station
2.1
Overview
The Quantum 1000 employs an extremely flexible and versatile hardware architecture. The heart of the
base station is a sophisticated and highly integrated ASIC that combines multiple DSP and general
purpose processor cores along with specialized DSP hardware. A Linux-based
Linux based subsystem supports
applications,
ns, SNMP and other management functions. The radio heart of the Quantum 1000 includes 2
RF transmitters and ass
associated
ociated PAs, and 4 RF receivers
receivers.
Important characteristics of the Quantum 1000 Base Station Sector are:
5 and 10 MHz profile

WiMAX OFDMA compl
compliance
iance
All layers implemented in software.
2.3 2.7 GHz and 3.3 3.7 GHz operations.
PureWave has implemented a scalable architecture that lets service providers upgrade their Base
Stations by:
2.2
Adding more Base Station

Stations to a physical location
Adding antennas
antennas (and corresponding RF module sets) within a sector
Adding processing capability in order to process traffic within additional spectrum
Upgrading software to allow for changes in features and standards.
MAC Software Architecture
he PureWave Quantum
Quantum is a
an
n 802.16e WiMAX base station. It contains two major silicon devices, one
The
comprising the Network and Management processor (referred to as the Linux), and the other comprising
the baseband PHY and MAC processors. The Network Processor is the system Manager and the
baseband SoC (sometimes called the Modem) is essentially a high
high-powere
powered
d signal processor. See
Figure 3.
The Network Processor contains a standard PowerPC core plus a Quic
Quick engine for packet processing.
The PowerPC runs Linux and hosts many highly complex applications including an SNMP device
management agent, multiple databases, web server, CLI, logging and other system services. The other
SoC is a WiMAX baseband processor. Together these perform network processing, MAC and PHY tasks.
The Network Processor connects to the external backhaul through a pair of gigabit Ethernet ports and to
the Modem through two 100
100/1000MB
MB Gigabit Ethernet ports. These ports carry a mix of traffic and
management/control messages. Various protocols carried over the two Ethernets link the applications,
including TCP/IP, UDP and custom Ethernet frames.
Rev 1.2,
1. Page 14 of 146
2.3
Enclosure
weather-resistant
resistant cabinet with the overall
The Quantum 1000 Base Station is made up of a single, weather
dimensions of: 24
2 W x 17 H x 5 D (figures 3 and 4).
). The unit has 4 mounting ears, each one located
near a corner of the rear of the enclosure. Each ear will accommodate a M10 bolt. The mounting holes
are spaced 37cm apart (center
(center-to-center),
center), horizontally, and 44.3cm apart, vertically (figures
(figure 5 and 6).
).
Figure 3 Quantum 1000 Base Station
Figure 3 - Tower Mounted Quantum 1000 Base Station
Rev 1.2,
1. Page 15 of 146
Figure 5 - Tower Mounted Quantum 1000 Base Station
37cm
44.3cm
Fig
Figure 6 Quantum 1000 Base Station Mounting Hole Pattern
Patt
The Base Station unit can be installed either as an entire outdoor unit (ODU) or as an entire indoor unit
(IDU). The antenna must always be installed outdoors.
Note: It is recommended that the Base Station Enclosure is mounted upright such that the
antenna N-type
N type connectors face down towards the ground. Please ensure that there is adequate
air flow around the Base Station heatsinks (refer to figure 5).
Rev 1.2,
1. Page 16 of 146
B
Station:
Table 2 lists the mechanical, electrical and environmental properties of Quantum 1000 Base
Physical & Environmental
Specifications
Dimensions
24.6 (H) x 17.4 (W) x 4.5 (D)
Weight
23 pounds
Power
-48V
48V DC, 65 Watts
Temperature
-33 to +55 degrees C
Humidity
5 to 95% non-condensing
non
Surge Protection
UL497B
Lightning Protection
10kA IEC 6100-4-5

6100 5 (optional via external kit)
Weatherproofing
IP67
Table 2 Base Station Physical and Environmental Properties
2.4
External Connections
There are basically 4 types of connections that need to be made to the Base Station unit (see figures 7
and 8).
POWER
ANT 2
ANT 1
ANT 4
232
RS232
E-NET 1 E--NET 2
ANT 3
GND
GPS ANT
Antenna Section
Figure 7 - Base Station External Connections (Bottom View)
Rev 1.2,
1. Page 17 of 146
Figure 8 - Base Station Connect

Connections
Once the Base Station enclosure has been mounted, the following connections must be made.
POWER
OWER:: Provides th
the
e DC power source for the Base Station unit.
GND: This provides a ground connection point for the Base Station. It is important to ensure that
the Base Station is professionally grounded and complies with all local relevant grounding
electrical codes.
GPS ANT:: This port provides the connection between the GPS antenna (external) and the GPS
G
receiver module (internal). GPS is used by the Base Station Sector to synchronize its TDD gate
to those of Base Stations in neighboring cells.
ANT
NT 1 ANT 4: This is where the Base Station is physically connected to an antenna. The 4
antenna ports are described as:
o
o
o
o
ANT 1: This is a transmit (Tx) and a receive (Rx) port.

ANT 2: This is a transmit (Tx) and a receive (Rx) port.
ANT 3: This is a receive (Rx) port only.
ANT 4: This is a receive (Rx) port only.
RS232: This is the serial interface to the Base Station. This interface will be primarily used for
out of the box configuration and debug purposes when directed by PureWave Technical
Support Engineers.
E--NET 1: This Gigabit Ethernet port provides the data traffic backhaul interface that should be
connected to the Service Providers network equipment. This port allows in-band
in band management of
the Base Station.
Rev 1.2,
1. Page 18 of 146
E--NET
NET 2: This Gigabit Ethernet port provides an out
out-of
of-band
band management interface. In addition,
this port can be used for daisy
aisy chaining to another base station or to connect to an external
device such as a web Camera.
Camera The
he traffic coming from the daisy chain connector shall be
aggregated and passed through the backhauling connector
connector.
NOTE:
DO NOT POWER ON THE BASE STATION OR REMO
REMOVE
VE THE BASE STATION POWER UNLESS THE
TWO TRANSMITTING ANT
ANTENNA
ENNA PORTS (ANT 1 AN
AND
D ANT 2) ARE EITHER TERMINATED BY A
SUITABLE RF LOAD OR AN ANTENNA. A FAILUR
FAILURE
E TO ENSURE THIS, AT ALL TIMES, COULD
RESULT IN INTERNAL D
DAMAGE
AMAGE TO THE BASE ST
STATION
ATION (FIGURE 9).
Figure 9 - Base Station Antenna Connections

ions
Connect the two transmitting ports (ANT 1 and ANT 2) to the two outer most elements of the actual
antenna thus ensuring that the transmission paths are as far apart as possible on the 4 available antenna
ports,, refer to figure 10
10.
Figure 10 Base Station to Antenna Physical Connection
Rev 1.2,
1. Page 19 of 146
2.5
Power
The Base Station DC power requirements is such that the external DC source needs to be capable of
delivering up to 4 Amps of current at -48 VDC. The Base Station nominally runs at approx 2 Amps at 48VDC (range -40VDC
40VDC to -57VDC, -38VDC
-38VDC min).
The power connector that is used on the Base Station will accommodate 14 to 18 gauge wire. Remember
ember
to take account of the voltage drop when running long power cable runs. For example, for 18 AWG, for a
cable length of 100
00 feet, a nominal 48VDC supply delivering into a 2A
A load will lead to a voltage drop of
2.7 volts. This power connector (Tyco P/N 796094
796094-2)
2) is provided as part of the Installation kit (figure 13).
Please ensure that the DC power source is powered off and solder the -48
48 VDC wires to connector pins 1
and 2.. Solder the 48 VDC Return wires to pins 3 and 4 (figures 1 to 14).
1
Figure 11 - Base Station Power Input Connector ((Tyco

Tyco P/N 796095-2))
Figure 12 - Base Station Power Input Connector on chassis
Rev 1.2,
1. Page 20 of 146
Figure 13 - Base Station Power Input Connector
Figure 14 - Base Station Power Input Connector

The following table 3 ind
indicates
icates the connector pinpin-outs.
Pin #
1
2
3
4
Signal
-48V DC
-48V DC
48v DC Return
48v DC Return
Table 3 Power Pin

Pin-out
out connections
Rev 1.2,
1. Page 21 of 146
Figure 15 is an expanded view of the connector onto which is attached the actual cable of wires.
Figure 15 - Base
e Station Power Input Cable Connector Expanded View
Instruction on how to crimp the power connector cable:

Things youll need:
Wire strippers
Needlenose pliers
Phillips Screwdrivers
Crimping tool
Step 1
Use your wire strippers to remove about 1/4 inch
in h of insulation from each wire and approximately 1 of
outer cable insulation.
insulation It is important to have each wire the same length and to have the same
amount of expose bare wire. Refer to figure 17..
Figure 161 Cable Termination Hardware Kit
Figure 17-- Yellow Crimper Pliers style, 14 gauge wire
Rev 1.2,
1. Page 22 of 146
Step 2
Slide the cable on to the

thecircular
circular socket connector. Place stripped wire into pin connector being
sure to have the wire insulation located at the first crimp location and the bare wire in the second
crimp location.
location Refer to figures 18 and 19 below.
First Crimp
Location for
Wire
Insulation
Second
Location for
bare wire
crimp
Figure 1818 Connector Housing assembly
Figure 19-- Cable contact with Pin Connector
Step 3
Now using the crimping tool in crimp head location B, squeeze very carefully making sure that
th
the first crimp location is forming properly. G
Give
ive it a slight tug to ensure that it is secure and that
the wire is tightly crimped into place. Refer to figures 20 and 21.
Figure 20-- Front view of crimping Pin connector
Figure 21- Aerial

rial view of crimping Pin Connector
Rev 1.2,
1. Page 23 of 146
Step 4
Crimp the cable again for the second crimp location by starting with the A side of the crimping tool to
form the crimp, once the second crimp location begins to curl stop crimping. Next place the second crimp
crimp
location in section B of the same crimping tool and make sure the pin is securely crimped.
crimped Refer to
figures 23,
23 27 and 25.
Figure 22-- View of crimped Socket connector
Figure 24-- Finish the crimp in Section B
Figure 23- Forming Second Crimp location
Figure 2525 Display of crimp pin.
At this point be sure that the crimped pin looks similar to the one in figure 25.
Rev 1.2,
1. Page 24 of 146
Step 5
Now using the Circular Connector plug, push the 4 crimped pins into each hole (Be sure that the pin out
ou
and color code match the polarity required be the base station, figure 14)
14). Use needle nose pliers to insert
all four pins securely by grabbing the first crimp location and pushing
push
all the way into the connector body.
It helps if you place the connector face down on a table to provide extra leverage, figure 28.
our crimped pins w connector

Figure 26-- Four
Figure 27- Display of pins inserted into DC plug.
Figure 28-- Pins are push down by needlenose pliers
Figure 29- Display of needlenose at work.
Rev 1.2,
1. Page 25 of 146
It is critical that the pins get pushed as far into the connector body as possible. After using the needle
nose pliers to insert the pins, it will be necessary to continue inserting the pins into the body with your
hand. By pushing and gentl
gently
y twisting the cable to get all four pins completely inserted. You must be able
to see the pins from the front of the connector body as in Figure 31.
Figure 30-- All four pins are securely in place
Figure 31 - View of pins from the other side
Step 6
Secure the DC plug by using the cable camp and tighten the two screws.
Figure 32-- Securing with Cable Clamp
2.6
Figure 32- Final view of power connector.
GPS
This port provides the connection between the GPS antenna (external) and the GPS receiver module
module
(internal). GPS is used by the Base Station to synchronize its TDD gate to those of Base Stations in
neighboring cells. Connect the coaxial cable from the external GPS antenna to the SMA-type
SMA type female
connector marked GPS on the bottom right corner o
off the Base Station unit (refer to figure 33).
). Typical
GPS antennas are shown in figure 34.
34
Rev 1.2,
1. Page 26 of 146
Figure 33 - Base Station Underside View of GPS Antenna Connection
Figure 34 - Typical Base Station Sector External GPS Antennas

In the event that there are co
co-located
located multiple Base Stations, it is important to synchronize all the Base
Stations to a 1 pps GPS such that this will co-ordinate
co ordinate all Base Station to transmit
transmit and receive
concurrently. To achieve synchronization the GPS antenna has to be pointed upwards
upwards into the sky with
as much view of the sky and horizon as possible. It needs to be able to receive a GPS signal from at least
3 GPS satellites.
The standard out of the box configuration has the GPS Synchronization disabled on the Base Station.
Please
ase note that GPS Synchronization must be enabled and there are a number of key points to note
concerning the GPS.
Rev 1.2,
1. Page 27 of 146
1)
An external GPS must be connected to the Base Station when the GPS Synchronization is
enabled. If no external GPS is connected then the Base Station transmission will be disabled.
enabled.
2)
If an external GPS is connected and the GPS Synchronization is disabled then the Base Station
may reboot.
Please refer to section 5.3 for details on how to configure GPS Synchronization.
2.7
Antenna
A low-loss,
loss, coaxial
coaxial cable has to be connected to each of the N
N-type
type female connectors located on the
back of the antenna panel and the respective antenna port on the base of the Base Station Sector. The
co-axial
axial cable must be capable of propagating the relevant RF frequ
frequency
ency and therefore it is
recommended to use any high
high-performance,
performance, lowlow-loss
loss coaxial cable (i.e. Hyperlink Technologies P/N
CA3N100 or Times Microwave LMR 400).The order of antenna connections is unimportant.
The important consideration is the length of the
the co
co-axial
axial cable as this will affect the amount of signal loss
and thus effective range of the system. In the case that the Base Station unit is installed outdoors and
close to the antenna, then the co
co-axial
axial cable runs can be kept short and thus loss is minimized.
minimized. If the
Base Station unit is installed indoors with long cable runs up the tower to the antennas then the amount of
signal loss will need to be calculated to ensure that adequate range will still be achieved. As an example,
a Times Microwave LMR400 cable has an attenuation loss of 6.8dB per 100 feet at a frequency of
2.5GHz.
For your information, the procedure to install co-axial
co axial connectors is provided in Appendix A.
devi
are
Note: It is strongly recommended that appropriate lightning surge protection devices
installed (refer to section 3). Please ensure that appropriate weather protection is applied to all
outdoor N-type
N type coaxial connections.
One antenna panel is used for each Base Station. The antenna panel is populated with a number of
directional patch-element
pa
element strips. All elements are enclosed within a single radome and common, rear
mounting plate. Access to each element (antenna) is provided by a dedicated N-type
N type female coaxial RF
connector. Thus, for a 4
4-element
element antenna panel configuration there ar
are
e a total of 4 exposed RF
connectors protruding from the rear mounting plate (refer to figures 35 and 36).
Note: Connect the two transmitting ports (ANT 1 and ANT 2) to the two outer most elements of
the actual antenna thus ensuring that the transmissio
transmission
n paths are as far apart as possible on the 4
available antenna ports.
The specifications for the 2.5GHz and the 3.65GHz antennas are detailed in Appendix A.
Rev 1.2,
1. Page 28 of 146
Figure 35 - Base Station Antenna
Figure 36 Typical Antenna Deployment

The antenna panel will be mounted to a pole having an outer diameter (OD) between 1 and 4,
, via the
provided mounting kit.
Rev 1.2,
1. Page 29 of 146
2.7.1 Antenna Mounting Kit

The antenna mounting kit is a heavy duty steel pole mount kit. It is provided with all the necessary
hardware is a simple
simple kit form and provides an adjustable elevation tilt mechanism (figure 20).
2
Figure 37 Antenna Alignment

Mechanical & Environmental
Specifications
Material
Steel
Weight
4 pounds
Load
510 N
Pole Diameter
1 to 4 inches
Movement Possibility Elevation

Ele
Tilt
+/- 15 degrees
Operating Temperature Range
- 40 degrees to + 85 degrees Celcius
Vibration
IEC 60721-3-4
60721
Flammability
UL94
Ice and Snow
25mm radial (survival)
Wind Load
210 km/h
Humidity
ETS 300 019-1-4,

019 4, EN 302 085 (annex A.1.1)
Service L
Life
>10 Years
Table 4 Antenna Physical and Environmental Properties

The procedure to install the antenna mounting kit is detailed below in figure 21.
2 . It is recommended that
the mounting kit is attached to the antenna prior to hoisting up the tower.
Rev 1.2,
1. Page 30 of 146
1)
Figure 38 Antenna Installation Diagram

Place items No.3 on the antenna (1), at its low back and high back (two places) as illustrated.
Align with the screw holes.
2)
Connect items No. 3 to the antenna with spring washers (9), plain washers (10) and nuts (8).(2 x
2 places).
places)
3)
Tighten the nuts at a torque of 30 In*Lbs.
4)
Connect item No. 6 to item No. 3 in the upper side of the antenna as illustrated, with items 7,
8,9,10. Leave screws slightly loose.
5)
Connect item No. 6 to item No. 5 as illustrated, with ititems

ems 7, 8,9,10 at the point marked 2.
6)
Connect item No. 3 to item No. 4 in the lower side of the antenna as illustrated, with items 7,
8,9,10. Leave screws slightly loose.
7)
Connect item No. 4 to item No. 5 with items 11,12,13,14, at its low back and high back
ba (two
places) sides of the Antenna as illustrated.
8)
Adjust the desired azimuth angle and tighten to the pole with a torque of 30 In*Lbs
9)
Adjust the desired elevation tilt to the angle marked, and fully tighten the loose screws.
Rev 1.2,
1. Page 31 of 146
2.8
Ethernet
This port allows

allows remote command and control of the Base Station and also provides the data traffic
backhaul interface that should be connected to the Service Providers network equipment. The cable
connection is a straight
straight-through TIA-568-B
B standard as shown below in figure 39.
Figure 39 Ethernet 568

568-B
B Straight Connection
In the case that the Base Station is mounted outdoors care it is important to ensure that the following
points are followed.
1)
2)
3)
4)
5)
It is recommended to install an appropriate outdoor rated, sshielded

hielded Category-5
Category 5 (STP-Cat
(
5) with
drain wire 100 Mbps Ethernet cable.
It is recommended to use a shielded outdoor rated metal shielded RJ45 cable connector.
It is recommended that shielded Cat 5e
5 cables are used and make certain that the drain wire has
a good contact with the metal RJ-45
RJ 45 connector
A weatherized Ethernet connector backshell must be installed (Molex P/N 813969556) to weather
protect the connector.
The maximum distance from the Base Station to the Service Providers network equipment is
limited to 100m.
limited
One recommendation for an outdoor rated Cat 5 Ethernet cable is:

Name:
Descripton:
Manufacturer:
Distributor:
Commscope 2003 Cat 5e

Outdoor rated, UV protection, shielded Cat 5e cable
Commscope
Anixter (http://www.anixter.
(http://www.anixter.com)
Note: the procedure for installing Ethernet connectors is provided in Appendix C.
Rev 1.2,
1. Page 32 of 146
2.8.1 Weather Protection of the Ethernet Connector

onnector
An IP67 compliant weather protection connector is provided along with the Base Station. This will provide
the means to weather pr
protect
otect the RJ45 Ethernet connection.
Figure 40 is an illustration of the components that are included in the protection connector.
Figure 40 Ethernet Weather Connection
Note: Please remember to install all the pieces of the connector onto the cable
cable before the RJ45
connector is crimped.
The procedure to install the connector is given below. The instructions are provided assuming that either
one of the ends of the cable is exposed with no connector crimped or that all components have been
threaded
d onto the cable prior to assembling the connector.
Take the plastic RJ45 holder and ensure that the rubber gasket cut out is attached to the
the RJ45
holder (figure 2
24);; by peeling off the paper lining and fitting the adhesive side to the connector
housing shown
shown below.
Figure 41 Plastic RJ45 Holder
Rev 1.2,
1. Page 33 of 146
Slide all components onto the cable, in the displayed order, prior to crimping the Cat-5
Cat 5 cable.
Figure 42 External RJ
RJ-45
45 Weatherproof housing components
Crimp the RJ45 connector (figure 43) onto the cable using standard cable manufacturer
supported crimper and procedure seen in Appendix C.
Figure 43 Cable RJ45 Connector
Rev 1.2,
1. Page 34 of 146
Ensure
nsure that the RJ45 connector is pulled tight into the holder. Ensure that the connector flap is
locked in place
place (figure 44).
Figure 44 Plastic RJ45 Holder plus RJ45 Cable
Nearly completed Ethernet cable assembly prior to shown in figure 45
Figure 45 All Components Assembled
Tighten the end cable locks and the assembly is complete (figure 46).
46
Rev 1.2,
1. Page 35 of 146
Figure 46 Complete Assembly
The assembly can now be attached to the Base Station Sector thus creating a weather protected
connection (figure 47). Be sure to insert the connector into
to the base station before tightening the
cable strain relie
relief gasket.
Figure 47 Complete Assembly connected to Base Station
Rev 1.2,
1. Page 36 of 146
3.
Grounding and Lightning Requirements
Proper lightning protection requires the use of external primary protectors to complement the secondary
protection built into the PureWave equipment.
equipment. The primary protectors offer the surge currents a direct
path to earth ground versus the undesirable sneak paths it may find through the equipment.
Properly installed and grounded primary protectors will dramatically increase the surge withstanding
capabilities of the PureWave equipment. Surges that exceed the maximum ratings of the primary
protector devices will eventually cause them to fail, however these devices are generally designed to fail
short or open, as the application warrants, such that further surges will not damage the end equipment.
While a failed primary protector still results in a service outage, it does prevent further damage to the
more expensive end equipment.
A Base Station that is installed outdoor on the tower or mast (ODU) is especially vulnerable to lightning
surges. Good surge mitigation practice starts with the lightning rod and its connection to a proper sized
down conductor.
The ground down conductor should be as straight as possible and avoid incidental contact with other
other
conductors such that it represents the path of least resistance to earth ground from the lightning rod. The
tower/mast is also earth grounded to keep its conductive elements at earth potential (0V) for personnel
safety, and generally presents a less desirable
desirable path to ground to surge currents. ODU equipment and
external primary protection devices are mounted to the tower/mast and should be bonded to earth ground
at the same point on the down conductor. This practice is intended to avoid ground loop currents
currents that may
flow from differences in potential between the tower/mast structure and down conductor while large surge
currents are flowing in them respectively. Good surge mitigation practice also makes use of shielded
cables with peripheral shield grounding
grounding to minimize potentials induced on circuit conductors.
These cables should also be secured to the tower/mast at regular intervals to create physical separation
from conductors which are carrying surge currents. This practice avoids incidental contact or
or possible
insulation breakdown from high surge potentials.
A Base Station that is installed indoor units (IDU) requires similar protection as the outdoor installation
(ODU). Primary protection devices are installed on all cables just prior to entry of the
the facility and bonded
to an earth ground stake. Likewise, the cable shields are grounded at the entry panel which should be
bonded to the same earth ground stake.
IDU equipment may also be vulnerable to surges entering via the AC power connection and steps
steps should
be taken to install a proper AC Surge Suppressor device to complete a well protected installation.
3.1
Lightning Protection Installation Components
The following are considered to be the main elements that constitute the components of a lightning
protection
otection scheme.
Lightning Rod
Base Station and Antenna Grounding
Down Conductor
Coaxial and/or Cat 5 Cable Shield Grounding
Rev 1.2,
1. Page 37 of 146
Figure 30,, demonstrates graphically how these elements are applied to an overall lightning design.
Please note that this is ssimply
imply a generic diagram and that each individual installation may have its own
specific requirements which may differ from the diagram. The key point to note is the overall concept.
The main items will be outlined in more detail in the following sections.
Figure 48 - A Typical
ypical Lightning Protection Design
3.2
Lightning Rod
The Lightning Rod must be welded to the mast structure and to a down conductor. This should be
constructed of a steel pointed tip and is in general installed at the highest point of the tower. It operates to
intercept the downward moving lightning strike by launching an upward going attachment spark. Once the
attachment is achieved, the bulk of the lightning current follows the ionized path. In this way, the lightning
lightning
rod diverts the lightning away from equipment on the tower.
If the lightning rod is not installed at the highest point on the tower, the equipment that is connected to the
highest point (usually a radio) is the most likely attachment point.
A Class
lass I lightning rod (air terminal) is 3/8-inch
3/8 inch copper or 1/2
1/2-inch
inch aluminum, while Class II calls for 1/21/2
inch copper or 5/8-inch
5/8 inch aluminum. Conductor sizes vary accordingly, also depending on their composition
(stranded or strips) and materials (aluminum o
orr copper). Since most soils contain acid or alkaloid
compounds that react with aluminum, any aluminum used must not come in contact with the soil.
Lightning rods (air terminals) 24 inches or higher should be used.
Rev 1.2,
1. Page 38 of 146
Referring to figure 30 above, the Height Above Antenna above the highest item of equipment (generally
the antenna) must be at least twice the distance (2 x d) between the outer surface of the item and the
tower. This will ensure a protection cone of 60 degrees around the tower (30 degrees each
each side from
the lightning rod). In areas of high lightning activity, the Height Above Antenna should be increased to
up 5 times the distance.
3.3
Down Conductor
The purpose of the Down conductor is to provide the shortest and most direct path to the earth. The
grounding of the down conductor to earth must be of ground resistance no more than 1 ohm.
3.4
Co axial and/or Cat 5 Cable Shield Grounding

Co-axial
The purpose of the Shield grounding is to minimize the potentials induced on circuit conductors plus keep
the cable
e shields at earth potential (0V) for personnel safety.
All ground lugs must be properly bonded to the grounding system of the protected components along with
all Antenna cables. Prior to entry into any facility, the cables must be properly grounded to the
the building
primary ground system at the building entrance panel.
In case of an indoor installed Base Station then this will apply to the co
co-axial
axial cables that connect the Base
Station to the Antenna. This is because these coco-axial
axial cables provide the only inter-connection
connection between
the indoor and the outdoor.
In the case of an outdoor installed Base Station, then this will apply to the Cat 5 cable and power
connection to the Base Station. In the case of an installation of the Base Station, it is the Cat 5 cable
cable and
the power that provide the inter
inter-connections
connections between the indoor and the outdoor.
3.5
Grounding and Bonding
The National Electric Code requires that any accessible metallic surface of electronic equipment be
connected to earth ground for personnel safety.
safety. Earth ground connections are achieved by direct
connections to the AC power ground at the IDU and by a grounding lug on the ODU. A Craftsperson must
attach a proper size wire to the ODU ground lug during installation or else the ODU chassis will float
float at
whatever potential appears at the shield connection of the coax.
3.6
Recommended Connection of a Bonded Ground
We will now examine the concept of a bonded ground. Bonded connections for reliable, gas tight joints
between conductors require removal of all
all paint from both contact surfaces and holding them together
under high pressure such as with a bolt or screw. The use of toothed washers is also recommended to
cause the conductive surfaces to bite into each other for improved connectivity and eliminate movement
of the conductors due to vibration.
Rev 1.2,
1. Page 39 of 146
3.7
Single Point Grounding Concept
Extensive analysis and investigation of installations has led to the belief that the root cause at the heart of
the majority of the failures is likely to be the presence of mult
multi--point
point grounding of equipment on the towers
and in the huts. Single point grounding these elements will eliminate ground voltage differentials and this
will dramatically increase the equipment survivability during surges.
Single point grounding requires that the grounding leads from the antenna, Base Station and Surge
Protection devices for a particular sector, are bonded together at the same point on the tower down
conductor. It is not necessary to bond all the sectors together but to ensure the components
componen of any
individual sector have the same ground point on the tower.
In the equipment hut, in the event of an indoor installation of the Base Station then the chassis ground of
the Base Station and all the Surge Protection Devices grounds must be grounded
grounded at the same point (see
figure 31).
).
Figure 49 - Single Point Grounding Concept

It is important to note that the following ground guidelines are followed during installations:
1.
2.
3.
4.
5.
6.
7.
8.
Surge Protection devices generally connect to ground by using a ground

ground wire. Cut any extra
ground wire length when finished connecting it to the single point earth ground
Never loop or coil up the ground wire, always connect it straight to ground.
A good earth ground impedance is less than 1.0 ohm.
Measure ground impedan
impedance
ce at the point where the protector ground wire is connected and not at
the ground rod.
Avoid sharp bends. Connect the ground wire as straight as possible.
Connect the protector ground wire and equipment ground (both power ground and telecomm.
ground) to a single common ground.
Make sure all connections are fastened securely and are tight.
Never install protectors during a storm and always follow your local safety codes.
Rev 1.2,
1. Page 40 of 146
3.8
Lightning and Surge Protection
PureWave recommends that Surge Protection Devic

Devices
es are installed to protect the Base Station.
For an indoor installation of the Base Station these Surge Protectors devices would be installed at the
entrance to the building that houses the Base Station (see figure 50).
Figure 50 - Indoor Insta

Installed
lled Base Station Relative to Position of Lightning Protectors
Such a device will provide protection to the Base Station in the event of a surge event entering the Base
Station through the RF port.
Two recommended devices are:
PolyPhaser Model AL
AL-LSXM
M-ME
ME (see figure 51).
). This is a 2GHz to 6GHz in-line
in line surge filter with a
DC block. This is a uni
uni-directional
directional device.
Altelicon Model AL
AL-NMNFB--9
9 (see figure 52) This is a DC to 6GHz in-line
in line surge filter. This is a bibi
directional device.
Rev 1.2,
1. Page 41 of 146
Figure 51 - PolyPhaser
yPhaser Model AL-LSXM
AL LSXM-ME Surge Protector (with ground lug)
Figure 52 Altelicon Model AL-NMNFB

AL NMNFB-9 Surge Protector (with ground lug)
Care must be undertaken when installing the surge protectors. If the device is bi-directional
bi directional then it is
irrelevant as to the direction of installation. If the device is uni
uni--directional
directional therefore it must be installed to
ensure that the protected side of the surge protector is connected to the Base Station. In the case of the
Polyphasor the N-type
N type male connection is connected
connected directly to the Base Station output and the N-type
N type
female connection is connected to the Base Station to Antenna cable. The male to female design of the
surge protector means that it is very difficult to incorrectly connect. In addition it is recommended
recommended that a
ground wire is connected to the ground lug that is provided with the surge unit (see figure 53).
Rev 1.2,
1. Page 42 of 146
Figure 53 - PolyPhaser Surge Protector Connected to Cable with Ground Cable Attached
Actual installation will depend upon the tower specifics. General tower installation practices would have a
large ground bar or plate just at the cable entrance to the building and the Surge Protectors would be
either attached directly or via the ground wire to this plate/bar. Alternatively the Surge Protectors can be
directly attached to the Base Station and then appropriate ground connections can be made.
In the event that the Base Station Radio is installed outside then it is recommended to install the surge
protection unit(s) between the Base Station and the Antenna.
Figure 54 - Outdoor Installed Base Station Relative to Position of Lightning Protectors
Rev 1.2,
1. Page 43 of 146
These RF surge protection devices will provide the Customer with two advantages (see figure 54).
1)
2)
To protect the Base Station in the event of a surge e

event
vent entering the Base Station through the
RF port.
It provides a mechanism to effectively ground together the Base Station, the RF surge protector
and the antenna.
In the case of an outdoor installation, it is recommended that suitable building entry surge protection is
considered and the equipment installer may want to consider based upon individual installation
requirements.
Note: Please ensure that appropriate weather protection is applied to all outdoor Surge
Protection devices.
devices
Surge protection
protection devices for both the Cat 5 and the power connections to the Base Station are already
built into the unit. No further devices are required to protect the unit. In addition, for an appropriate fee,
PureWave provides a RF lightning surge protection kit. Thi
This
s includes the RF surge protection devices and
a ground bar which acts as a means to ground all the devices. Please refer to figure 55 for an example
of this kit when installed.
Figure 55 - Installed PureWave provides a RF lightning surge protection kit
Rev 1.2,
1. Page 44 of 146
4.
Weather Protection
PureWave recommends that appropriate weather protection sealing and the application of an anti-seize
anti seize
material is applied to all outdoor installed elements of the system. Weatherproofing tape kits flawlessly
seals the junction between
between two connectors. It not only protects the connection from water damage, it also
prevents vibrations from loosening the interface.
4.1
Weather Sealing
There are a range of commercially available weather protection kits that provide all the necessary
necessar
components in addition to full instructions on how to weather protect. A generic weather sealing concept
will be adopted rather than a specific one.
The following universal weatherproofing kit was used:
Name:
Part #:
Descripton:
Manufacturer:
Distributor:
Universal Weatherproofing Kit

488136
Weatherproofing tape kit. Each kit contains (6) rolls of 2-1/2"
2 1/2" x 24" butyl tape, (2)
rolls of 3/4" x 66' black electrical tape & (1) roll of 2" x 20' black electrical tape.
Andrew Networks (P/N 221213)
Tessco
sco (http://www.tessco.com)
The butyl tape is shown below in figure 56.
Figure 56 - Butyl Tape Weather Protection

The general procedure to install is:
1)
Completely wrap the connection with the smaller 3/4inch smaller electrical (plastic) tape. Ensure
Ensur
that the tape extends back up the cable to cover the entire connector and that the tape overlays
itself by approximately half a width (figures 57 and 58).
).
Rev 1.2,
1. Page 45 of 146
Figure 57 - Connection to Antenna
Figure 58 - Plastic (Electrical) Tape Applied
2)
Cut a length of the butyl such that it will completely cover the connection. Wrap the tape around
the connector and press into place. Ensure that there are no gaps (figures 59 and 60).
Rev 1.2,
1. Page 46 of 146
Figure 59 - Butyl Tape Being Applied
Figure 60 - Butyl Tape Applied
3)
Completely wrap the wrapped assembly with the larger 2 inch electrical (plastic) tape. Ensure
that the tape extends back up the cable to cover the entire butyl tape and that the tape overlays
itself by approximately half a width (figure 61).
Rev 1.2,
1. Page 47 of 146
Figure
Figu 61 - Second Plastic Tape Applied
4.2
Anti
Anti-Seize
It is also suggested that a suitable anti-corrosion

anti corrosion lubricant is applied to all exposed metal surfaces. A
suitable lubricant is recommended below.
Name:
Part #:
Descripton:
Distributor:
NEVER-SEEZ
SEEZ Regular Grade Lubricant 1OZ (figure 62)
V057940-8A
8A
NEVER-SEEZ
SEEZ regular grade lubricant is an anti
anti-seize
seize compound and extreme
pressure lubricant in a 1 ounce tube.. Protect metal parts against rust, corrosion
and seizure up to 1800F.
Ellsworth Adhesives (http:
(http://www.ellsworth.com)
//www.ellsworth.com)
Figure 62 - Anti
Anti-Seize
Seize Lubricant
Rev 1.2,
1. Page 48 of 146
To apply the material then the exposed metal surface is simply painted with the lubricant such that all
exposed metal surfaces are completely covered (see figure 63).
63
lubricants
cants tend to be messy and sticky to apply due to the
the nature of
Note: These types of lubri
their intended application. Always read the labels or instructions provided and take necessary
pre-cautions
cautions during application
application.
Figure 63 - Anti-Seize
Seize Applied
Rev 1.2,
1. Page 49 of 146
5. BASIC CONFIGURATION
This
is section describes the process of configuring the minimum required number of parameters for
basic operation of the Base Station. The PureWave Quantum family of WiMAX base stations is
accessible for configuration via two separate methods, a CLI and a Web Interface. Each interface
has the capability of configuring all parameters available in the base station.
5.1
Connect to the Base Station

In order to connect to the Base Station then the ffollowing
ollowing components are required. These are
provided as part of the Base Station Installation kit (refer to figure 64):
):
Networking Components
DB9 Female to DB9 Female (Part # 361

361-00001-001,
001, Qty: 1)
Cable, Cat 5E, WHT, 6 (Part # 361-00394
361 00394-006,
006, Qty: 1)
Adapter, Female Network (Part # 366
366-00346-001,
001, Qty: 1)
Figure 64 - Networking Components

There are three RJ45 ports to connect and hence access the Base Station.
RS232: This is the serial interface to the Base Station. This interface will be primarily used for out
of the box configuration and debug purposes.
E-NET
NET 1: This Gigabit Ethernet port provides the data traffic backhaul interface that should be
connected to the Service Providers network equipment. This port allows in-band
in band management of
the Base Station.
Rev 1.2,
1. Page 50 of 146
E-NET
NET 2: This Gigabit Ethernet port provides an out-of-band
band management interface. In addition,
this port can be used for daisy chaining to another base station or to connect to an external device
such as a web Camera.
The Base Station can be managed via its RS232 Serial port or its E
E-NET
NET 1 Ethernet
Etherne port. To
access the CLI the connection can be made via:
Telnet using Hyperterminal or Tera Term
Serial communications protocol, such as Hyper Terminal or Tera Term.
The procedure to connect to the Base Station is:
ports ANT 1 and ANT 2 are terminated.
Ensure the Base Station antenna ports
Connect and Power on the Base Station.
Connect a straight Cat 5 Ethernet cable directly between the E
E-NET
NET 1 port on the Base Station
and the Customer network or PC.
To connect to the Base Station RS232 port, the User will need the following hardware that is
provided with the install kit. These are as follows:
RJ45 cable.
DB9 male connector (Network Adapter).
DB9 female to DB9 female adapter.
Optional: Serial to USB connector. Most laptop nowadays comes with USB connection
connection instead of
serial connection. If your PC/laptop has serial connection then you wont need this adapter. If not,
then you will need to get serial to USB adapter to access the BS CLI (figure 65).
Figure 65 Serial to USB adapter (D

(DB9
B9 Male)
Plug one end of a straight Cat 5 Ethernet cable into the RS232 port on the Base Station and the
other end into the RJ45 to Modem adapter. Connect the other end of this Modem adapter to a
DB9 serial cable and connect this DB9 serial cable to a USB adapter that connect to your laptop.
Please refer to figure 66 for the physical layout.
Rev 1.2,
1. Page 51 of 146
Figure
66 Base Station Serial Connection
Rev 1.2,
1. Page 52 of 146
5.1.1 CLI
The PureWave Command Line Interface (CLI) provided has an IOS look and feel to
to its operation.
It is accessible via a serial console connection, telnet or ssh. All parameters available in the web
interface are also available in the CLI.
1.) Open a terminal emulation program: PuTTy, HyperTerminal, SecureCRT,
TeraTerm
2.) Create a new connection
connection with the following serial port settings
Port Settings
Baud
Data bits
Stop Bits
Parity
Flow Control
3.) Connect to serial port
38400
8
1
None
Xon/Xoff
Figure 68 CLI Login Page

4.) A login prompt will then be displayed
a. Default login: admin
b. Default
efault password: admin123
SSH
1.) Open a SSH client program : PuTTy, SecureCRT, Tunnelier, etc
2.) Create a new profile using the management IP
a. Default IP : 192.168.1.10
b. Port : 22
b. Default password: admin123
admin123
Telnet
1.) Open a Telnet client program : PuTTy, SecureCRT, etc
2.) Create a new profile using the management IP
a. Default IP : 192.168.1.10
b. Port : 23
b. Default password: admin123
Rev 1.2,
1. Page 53 of 146
5.1.2 Web Interface

PureWaves W
Web
eb Interface is accessible through most major web browsers that support SSL
connections. The web interface has been specifically tested on Internet Explorer (Version 7 and
up) and Mozilla FireFox. HTTP and HTTPS are supported with HTTPS being the default; HTTP is
disabled by default but can be enabled if desired.
PureWavess Web Interface is split into two separate modes of operation. View mode, which
allows for read
read-only
only access of all parameters, and an Edit mode which allows for configuration of
all available
available parameters. View mode is the default mode when initially logging into the interface.
Selection is Greyed
out not allowing
configuration changes
Figure 69 - WebGUI View Mode

Within edit mode there are two different varieties, Edit Private and Edit Exclusive. Selecting
Edit Private will allow tthe
he user to configure all parameters but will not lock the configuration
database allowing for other users to make configuration changes at the same time. Edit
Exclusive will lock the configuration database and prevent any other user from making
configuration changes.
configuration
Rev 1.2,
1. Page 54 of 146
Exit Transaction
returns to view mode
Commit
Applies
configuration
changes
Drop-down
Drop
down box
allows for
configuration
changes
Figure 70 WebGUI Edit Mode

Whichever edit mode that is chosen, the configuration changes and saving of those changes
behaves the same way. The user may change as many parameters at they like without
committing those changes, but none
none of those changes will take effect until they are committed.
committed
If all configuration changes are complete, select Exit
Exit Transaction to return to View Mode. After
committing the changes it may be required to reset the radio module.
Changes made to the configuration only remain persistent for the current boot, if the base station
is rebooted those changes will be lost if the user does not write the configuration. This command
is accessible from view or edit mode under the following section; Configuration
Configuration -> Write,, select
the Perform button to execute the command.
In many menus there are two sets of parameters, configured parameters and state parameters.
Configured parameters are the settings that are currently configured in the systems configuration
configuratio
database. State parameters are the settings that are currently in use by the system. Many of the
configuration menus will contain a Configured set of parameters and a State set that is identical
to the configured set.
Rev 1.2,
1. Page 55 of 146
5.2
5.3
BASIC CONFIGURATION
W
WebGUI
This section will detail the configuration parameters necessary for basic operation via the web
interface. Most parameters set by default do not require reconfiguration unless the user has
specific deployment or application requirement
requirement.. Only a handful
handful of parameters are required to
personalize the base station to any individual setup. These parameters include but are not limited
to:
Basic Parameters Quick Start
Data IP
Channel Bandwidth
Frequency
Power Output
5.3.1 Network Interface

A Purewave Quan
Quantum
tum Base Station has two network interfaces, the first for management and the
second for data. Each interface is bridged through either external physical network interface.
Figure 71 Management Interface Configuration Screen

The management network interface
interface configuration is located in the Web Interface under System
- Interface.. By default the management interface IP is 192.168.1.10.
->
192.168.1.10. Default values are placed
under the configured values in parentheses.
Rev 1.2,
1. Page 56 of 146
Address::
Netmask:
etmask:
Gateway:
Management IP; default 192.168.1.10

Default network mask 255.255.255.0
Default Gateway IP 192.168.1.254
Figure 72 Data Path Interface Configuration

All data path related traffic from Base Station to MS is routed via this interface. Configuration of
the data port inte
interface
rface IP is located under Sector ->
> General ->
> 1 -> System ->
- IP.
Address:
Address
Netmask:
Gateway:
Data Path IP; default Data IP

192.168.1.11
Default network mask 255.255.255.0
Default Gateway IP 192.168.1.254
Rev 1.2,
1. Page 57 of 146
5.3.2 Radio Parameters

All specific radio param
parameters
eters are configured under this configuration menu. The menu is available
under Sector -->
> Advanced -> Radio.. Center frequency and power output settings are the only
two parameters in this section that make a physical change to the function of the base station.
station.
Antenna gain and cable loss are logical parameters that are used when calculating the EIRP of
the system. Setting these parameters correctly is important as it can impact the output power the
CPE chooses to use during operation.
Figure 73 Radio P
Parameters
arameters Configuration
Antenna Gain: Gain in dB of the connected antenna
Cable Loss: Loss in dB of the RF cable running between the antenna and base station
Center Frequency: Radio center frequency in kHz
Power Output: Power in dBm as seen at the antenna connectors
Rev 1.2,
1. Page 58 of 146
5.3.3 WiMAX Parameters

WiMAX parameter configuration pertains to the protocol specific settings of the system. This
menu can be accessed under Sector ->
> advanced ->
> 1 ->
> WiMAX.
Figure 74 WiMAX specific configuration parameters

Maximum Uplink Rate: Maximum Global Uplink MCS Level; Default QAM64 5/6
Maximum Downlink Rate: Maximum Global Downlink MCS Level; Default QAM64 5/6
Antenna TX Mode: MIMO Antenna mode, MIMO
MIMO-A
A or MIMO-A/B;
MIMO A/B; Default MIMO-A
MIMO
Auto Power Control: Open-loop,
Open loop, or Closed
Closed-Loop,
Loop, Default:
Defau Open-Loop
Loop
Auto Transmit After Reset Mode: Starts radio transmission automatically after reset; Default
disabled
Channel Bandwidth: 5 MHz, or 10 MHz; Default 10 MHz
DCD Interval: Downlink Channel Descriptor Interval; Default 1000
Default Provisioning En
Enabled:
abled: Provides a default service profile to any entering MS if enabled;
Default disabled
Downlink/Uplink Frame Ratio: Ratio of downlink to uplink symbols determines the amount of
downlink throughput vs. uplink throughput; Default 35:12
*Refer to Appendix D for DL/UL Ratio vs. throughput tables
Maximum Distance: MS maximum allowable range; 1 24 km
Noise and Interference Settings:
UCD Interval: Uplink Channel Descriptor Interval
Rev 1.2,
1. Page 59 of 146
5.3.4 GPS
GPS configuration generically pertains to enabling or disabling the use of GPS by the system for
air frame synchronization. In addition to enabling GPS, there is a feature called the Synch
Recovery Timeout Interval, which issues a reset of the base station when GPS synch is lost for
more than the timeout interval. This interval
interval is user configurable, however it is recommended to
leave the value set to the default five minute interval. The GPS menu is accessible from the main
title page under GPS.
Note: Be sure the GPS antenna is connected to the base station before enabling
enabling this feature
Figure 75 - GPS Configuration Menu
GPS Admin Status : Enable (On), Not Enabled (off)

Sync Recovery Timeout Interval: Time in seconds
Latitude: Displayed in Decimal Degrees
Longitude: Displayed in Decimal Degrees
Altitude: Meters above sea level
State: Online/Offline
Sync Loss Occurrences since Last Reboot: Number of times GPS lost 1 PPS signal since last
reboot
Rev 1.2,
1. Page 60 of 146
5.3.5 Time/NTP
This section allows the user to configure the time and NTP servers used by the system.
Configuring the time will ali
align
gn the system logs to the current time, making it easier to interpret
them during troubleshooting.
Current System Time
Figure 76 - Current System Time and Time Zone

Current system time and time zone are displayed above. Be sure to set the time zone to
to keep the
time relative to the users local time.
Rev 1.2,
1. Page 61 of 146
System time can be set manually or set to use a NTP server to keep the system time in synch.
Due to the implementation of NTP, the system time must be set within 15 minutes of the actual
time for NTP to properly update.
Figure 77 - Setting System Time Manually
Time can be manually set with the above configuration menu.

Time
Hour: 0-23
Minutes: 0-59
59
Seconds 0-59
Seconds:
59
Milliseconds: 0-999
Timezone Hours offset from UTC: -23
23 to +23
Timezone Minute offset from UTC (Coordinated Universal Time): 0-59
0
Date
Year
Month
Day
Timezone Hours offset from UTC: -23
23 to +23
Timezone Minute offset from UTC (Coordinated Universal Time): 0-59
0
Rev 1.2,
1. Page 62 of 146
NTPDate
NTPDate queries the time via a configurable NTP server aand
nd sets this time value as the
current time.
Figure 78 NTPDate execution page
NTPDate can be accessed under Time ->> ntpdate.

ntpdate
1.) Enter a NTP server IP address
2.) Click Perform to execute the time update
3.) Verify the current time by selecting the time menu
Rev 1.2,
1. Page 63 of 146
NTP Servers
NTP
NTP servers used to synchronize the system time can be added here. Servers can be specified
by hostname or IP address each having a specific version of three or four.
Figure 79 NTP Server configuration

IP-Address: IP of NTP Server
IP
Version NTP server software version
Version:
Enabled: Checked (Enabled), Un-Checked
Enabled:
Un Checked (Disabled)
Rev 1.2,
1. Page 64 of 146
6. Advanced Configuration
Client Profiles
Client profile configuration is a complicated yet extremely flexible system that creates over-the
over the-air
enforcement of specific applications.
applications. As it can be seen in the diagram below, the structure of a
Client Profile is based on a building block approach. The bottom level of the structure is formed
from: packet flow direction, QoS, ARQ/HARQ, and classifier profiles. One building block up from
the bottom is service flows that each contains the set of profiles from the level below.
Client Profile
1-8
Service Flow
2
Service Flow
1
.....
6.1
Service Flow
15
Direction - Downlink
Direction - Uplink
QoS Profile 1-16
QoS Profile 1-16
ARQ Profile 1 - 3
HARQ Profile 1 - 6
ARQ Profile 1 - 3
HARQ Profile 1 - 6
Classifier Profile 1 - 64
Classifier Profile 1 - 64
Service Flow
16
Figure 80 Client Profile Structure

Each service flow then takes on a specific form that applies to the intended application. A
supported application is, normally, comprised of two service flows; one uplink service flow and
supported
one downlink service flow. For example, a typical residential internet application would have two
service flows; one each downlink and uplink service flow with best effort
effort QoS type, disabled
ARQ/HARQ and no classification.
Client Profile - Basic
Residential Service
Service Flow 1
Service Flow 2
Direction
QoS
hARQ/ARQ
Classification
Downlink
Uplink
Best Effort
Best Effort
None
None
None
None
Every client profile ha

has
s support for up to 16 individual unidirectional service flows. This number of
service flows allows the user to create more complex client profiles that serve multiple
applications in one profile. Heres an example of a residential internet service with VoIP
VoIP support.
Client Profile - Basic
Residential Service w/ VoIP
Service Flow 1
Service Flow 2
Service Flow 3
Direction
QoS
Downlink
Uplink
Downlink
Best Effort
Best Effort
eRTPS
HARQ
ARQ
/ARQ
None
None
None
Service Flow 4
Uplink
eRTPS
None
Classification
None
None
IP Protocol = 17
Destintation
tion Port =
11000 - 20000
IP Protocol = 17
Destintation Port =
11000 - 20000
Rev 1.2,
1. Page 65 of 146
Providing restricted data rates is an important aspect of the QoS functions in an application. At
the base level the QoS profile sets the maxim
maximum
um or minimum sustained or reserved rate
respectively. The best effort QoS type provides an up
up-to
to or MIR (Maximum Information Rate);
while UGS or eRTPS provides a CIR (Committed Information Rate). This is not the only method
of rate limiting available in a client profile. A user has the ability to set a MIR and CIR in the client
profile configuration separately from the QoS profile. This function has been provided in order for
a network operator to specify several different service flows with varying QoS levels while
maintaining a per client profile minimum or maximum. It must be noted that between the QoS
and client profile rate limiting, the lower of the two rates will be enforced by the system.
Prioritizing data traffic is another key element in mainta
maintaining
ining reliable data rates to critical
applications. Throughout the client profile building block structure are various levels of
prioritization. The user has the ability set priorities at the QoS, classifier and client profile levels.
Classifier priorities provide the ability to prioritize traffic within the client profile of a single CPE
and between its service flows. At the client profile level the user can prioritize service levels or
groups of CPE.
Rev 1.2,
1. Page 66 of 146
6.1.1 Client Profile Configuration

Client profiles are sservice
ervice levels that are assigned to each mobile station. A client profile is made
up of several components, service flows, direction, QoS profile, ARQ/HARQ, and packet classifier
profile. All settings pertaining to client profiles are located under Service-profile
Service profile -> Clientprofile.
Name: User configurable
profile name; max 15
characters
Description: User configurable
profile description; max 64
characters
Max-dl-rate:
Max
rate: Maximum
downlink rate reserved for this
client; in bps
Max-ul-rate:
Max
Maximum uplink
rate reserved for this client; in
bps
Max-traffic-burst:
Max
burst: Maximum
traffic burst per frame, bytes
Min-dl-reserved
Min
reserved-rate:
Minimum downlink reserved
rate; in bps
Min-ul-reserved
Min
reserved-rate:
Minimum uplink reserved rate,
in bps
Max-pps:
Max
Maximum packets
per second
Num-sflow:
Num
Number of used
service flows
Priority: Priority for this client
profile
Figure 81 Client Profile Configuratino
Rev 1.2,
1. Page 67 of 146
6.1.2 Service Flows

Each client profile supports up to 16 unidirectional service flows each with a specific direction,
QoS profile,
profile, ARQ/HARQ profile and classifier profile. A service flow is a packet flow that conforms
to a set of QoS settings. This provides a mechanism for prioritizing and shaping traffic to satisfy
the needs of different applications, i.e VoIP, video streaming, an
and
d etc.
Profile #: Service Flow

Profile Index
Name: Name, up to 31
chars, optional
Description: Description,
up to 31 chars, optional
Direction:: Packet flow
direction, downlink or uplink
Arq-profile
profile-num: ARQ
profile index, 1 -3
cls-profile
profile-num:: Classifier
Classifi
profile index, 1 - 64
harq-profile
profile-num: HARQ
ARQ
profile index 1 - 6
qos-profile
profile-num: QoS
profile index
Figure 82 Service Flow Profile Configuration
Rev 1.2,
1. Page 68 of 146
Direction
Direction specifies whether the flow of packets is traveling from the BS to MS (downlink) or from MS to BS
(uplink).
QoS_Profiles
A QoS profile enforces an over-the-air
over
air service type that provides rate limiting and link
prioritization that can enhance the performance of specific applications. VoIP, for example,
requires a small de
dedicated
dicated amount of traffic with low latency to provide a good user experience. A
properly configured QoS profile will provide the required level of service for any application. One
QoS profile is assigned to each service flow that is used by the subscriber station.
name - Profile Name, up to 15 chars,

optional
description - Profile Description, up
to 31 chars, optional
max-sustained
sustained-traffic
traffic-rate Maximum Sustained Traffic Rate (bits
per second)
max-latency
latency Maximum Latency
(milliseconds), 0 - 65535
data-delivery
elivery-service
service - Data
Delivery Service Type, one of
{UGS_Service, RTP_Service,
nRTP_Service, BE_Service,
eRTP_Service}
max-traffic
traffic-burst - Maximum Traffic
Burst Size, 0 - 4294967295
min-reserved
reserved-traffic
traffic-rate - Minimum
Reserved Traffic Rate (bits per sec), 0
4294967295
Figure 83 QoS Profile Configuration
request-transmission
request
transmission-policy
policy Request Transmission Policy, 0
0-7F
7F hexadecimal Default: 10
sdu
sdu-inter-arrival
arrival-interval
SDU Inter
Inter-Arrival
Arrival Interval, 0 - 65535
sdu
sdu-size
Service Data Unit Size (bytes), 0 - 255
tolerated jitter
tolerated-jitter
Tolerated Jitter (milliseconds), 0 - 65535
traffic priority
traffic-priority
Traffic Priority Level, 1 - 8
ul
ul-grant-schedule
schedule-typeUplink Grant Schedule Type, one of {BS_Defined_UL_Sched,
BE_UL_Sched, nRTP_UL_Sched, RTP_UL_Sched, eRTP_UL_Sched, UGS_UL_Sched}
UGS_UL_Sched}
unsolicited grant-interval
unsolicited-grant
Unsolicted Grant Interval, 0 - 65535
unsolicited poll-interval
unsolicited-poll
Unsolicted Poll Interval, 0 - 65535
Rev 1.2,
1. Page 69 of 146
HARQ
Hybrid ARQ is an optimized version of ARQ that provides link layer retransmission for error
correction. Using H
HARQ
ARQ has benefits in increasing overall sector range at the cell edge by
providing data redundancy. The number of retries determines the level of improvement and
redundancy but at the cost of throughput. There are six different profiles that have been prepre
configured
onfigured by default.
Enable Select to enable, deselect to disable
profile
Channel Mapping Number of HARQ channels
Channel-Mapping
to use per Subscriber Station
Num--retries Number of times the system will
re-transmit
transmit a burst until it is discarded. More
retries results
results in higher availability but reduces
available throughput
Figure 84 HARQ Profile Settings
ARQ
ARQ is very similar to HARQ but does not scale very well in large deployments. It is supported by
the base station but is not recommended
recommended for use as HARQ is a more efficient algorithm.
Figure 85 ARQ Profile Settings
Rev 1.2,
1. Page 70 of 146
Classifier Profile
This profile refers to a packet level classification system that provides the ability to allow or deny
packets conforming to the configured profile. Vl
Vlan
an ID, DSCP value, source/destination port are
just a few examples of what the classifier can provide. Using classifiers can further increase the
performance of specific applications when coupled with the right QoS profile. In order to enabled
the appropriate
appropriate classifier rule, the box labeled Classifer_rule
Classifer_rule-used
used must be checked for the
system to enforce the rule.
Description Profile Description, up to 31
chars, optional
dest
dest-port-high
high Classifier Destination Port
High Limit, 0 - 65535
dest
dest-port-low
Classifier
ssifier Destination Port
Low Limit, 0 - 65535
dest
dest-ip-addr-prfx
prfx Classifier IP Destination
Address and Prefix (mask length); examples:
192.0.0.0/2, 192.168.0.0/13,
192.168.254.0/23, 192.168.1.1/32
dest
dest-ip-addr-used
used Classifier IP Destination
Address Rule is used, true/false
dest
dest-ip-port-used
used Classifier Destination port
Rule is used, true/false
eth
eth-type
Classifier Ethernet Type, 1501 65535
eth
eth-type-used
Classifier EtherType Rule is
used, true/false
ip
ip-protocol
Classifier IP Protocol Type, 0 255
ip-protoc
protocol-used
used Classifier IP Protocol Rule is
used, true/false
ip-tos
tos-high Classifier IP TOS High Limit, 0 - 7
ip-tos
tos-low Classifier IP TOS low limit, 0 - 7
ip-tos
tos-used Classifier IP TOS Rule is used,
true/false
name Profile Name, up to 15 chars, optional
priorit Classifier Priority, 0 - 255
priority
priority
priority-used
Classifier Priority Rule is used,
true/false
src
src-ip-addr-prfx
prfxClassifier
Classifier IP Source Address
and Prefix (mask length); examples:
192.0.0.0/2, 192.168.0.0/13,
192.168.254.0/23, 192.168.1.1/32
src
src-ip-addr-used
used
Classifier IP Source
Classifier
Address Rule is used, true/false
Figure 86 Classifier Profile Configuration
src-ip-port-used
src
used
Rule is used, true/false
src
src-port-high
src
src-port-low
type
vlan
vlan-id
vlan
vlan-id-used
Classifier Source port

Classifier Source Port High Limit, 0 - 65535
Classifier Source Por
Portt Low Limit, 0 - 65535
Classifier Type, one of {none, ipDest, tos, vlan, macDest}
Classifier VLAN ID Tag, 0 - 4095
Classifier VLAN ID Rule is used, true/false
Rev 1.2,
1. Page 71 of 146
SNMP
The SNMP server configuration settings allow the user to d
define
efine what versions of SNMP are
used. Many parameters and performance metrics can be queried via SNMP. The PureWave
PureView EMS system utilizes SNMP to configure and
Figure 87 SNMP Supported Version Configuration
Rev 1.2,
1. Page 72 of 146
6.2
SERVICE ACTIONS
Start Radio
Radio transmission
Performing this action will start the radio transmission of the system if it is not automatically set.
Figure 88 Start Radio Transmission
Reboot Sector Module

This action has the effect of rebooting the radio module separately from
from the management module.
Figure 89 Reboot Sector Module
Rev 1.2,
1. Page 73 of 146
Abort Subscriber Station Network Entry

A CPE can be aborted during network entry if the user chooses to do so. By entering the MAC
address of the CPE and then selecting perform the CPE will a
abort
bort its network entry process.
Figure 90 Abort Subscriber Station
DEREGISTER SUBSCRIBER STATION

Any CPE can be disconnected from the system by issuing this command. Enter the CPEs MAC
address and select perform to remove it from the system. The C
CPE
PE will attempt to re-register
re register into
the system after being removed. Using this feature allows the user to modify a CPEs service
profile and force of network entry in order for the new profile to take effect.
Figure 91 Subscriber Station Deregister Utility

U
Rev 1.2,
1. Page 74 of 146
Reset Subscriber Station

In addition to deregistering the CPE, a user has the ability to issue a full CPE reset remotely from
the base station. Enter the MAC address of the CPE to be reset and press perform.
Figure 92 Subscriber Station Rese

Resett Utility
Rev 1.2,
1. Page 75 of 146
7. Monitoring
onitoring
7.1
7.1.1
Monitoring Via Web Interface

A full set of base station statistics are available via the web interface.
BS Statistics
The root of the statistics menu contains a summary of all the Base Station related statistics.
These statistics
statistics include packet error counters, throughput counters, service flow metrics and
network entry statistics. The Base Station statistics status page is located under the following
section, Sector ->
> Statistics.
Statistics. At the top level of the menu an overall status
status page is available that
displays all statistics in a summary that auto updates every 10 seconds.
Figure 93 BS Statistics Status Page
Rev 1.2,
1. Page 76 of 146
Service Flow Metrics

These metrics provide information of service flows currently active, created, deleted and total
total
number at any given point in time.
DSA-REQ
DSA
REQ Count:
DSA REQ Success
DSA-REQ
DSC REQ Count
DSC-REQ
DSC REQ Success
DSC-REQ
DSD REQ Count
DSD-REQ
DSD REQ Success
DSD-REQ
Max Active Service Flow
Max DL Service Flow
Max UL Service Flow
Figure 94 BS Service Flow Metrics

Metr
Rev 1.2,
1. Page 77 of 146
Packet Error Rate Metrics

Packet error metrics pertain to the flow of packets through the radio interface of the base station.
These are separate from Ethernet level statistics as the only relate to the air interface. Downlink
and uplink packet st
stats
ats are available the show the amount of packets sent, the number that are in
error and the rate at which those errors
occur over time.
DL Packet Sent:
DL Packet Error:
DL Packet Error Rate:
UL Packet Received:
UL Packet Error:
UL Packet Error Rate:
Figure 95 BS Packet Error Metrics
Startup Counters
Startup counters pertain to CPEs attempting to perform network entry into the base station. This
is important in that the user can see if CPEs a
are
re successful in performing the initial ranging
during network entry and if they have been authenticated into the system. If the number of
attempts far out weights the number of success then it can be deduced that CPEs are having
trouble associating to th
the
e base station.
Ranging Attempt Count Number of

attempts by CPEs to range into the base
station
Ranging Success Count Number of
successful ranging attempts by CPEs
Authentication Attempt Count - Number of
attempts by CPEs to authenticate into
into the
base station
Authentication Success Count Number
of successful authentications by CPEs into
the base station
Figure 96 BS Start-up
Start up Counters Page
Rev 1.2,
1. Page 78 of 146
Throughput Counters
Theses metrics provide information pertaining to throughput through the air
air interface measured in
megabits per second. Downlink and uplink peak and average throughput counters are available.
Figure 97 BS Throughput Counters
Rev 1.2,
1. Page 79 of 146
7.1.2 MSS Statistics

The PureWave Quantum base station provides a detailed set of st
statistics
atistics for all the CPEs that
are registered. MSS statistics is located in the following menu, Sector ->
> statistics-mss.
statistics
Available statistics include but not limited to the following: mss throughput, throughput per service
flow, RSSI, CINR ARQ/HARQ counters,
counters, and modulation level. The top level of this menu displays
a summary of all the metrics available and is updated automatically every 10 seconds.
Figure 98 MSS Statistics Status Page
MSS Throughput Counters

Throughput counters are available on an individual CPE basis sorted by MAC address. This set
of metrics includes downlink and dplink counters for Bytes, packets and packet error
DL Bytes Number of downlink bytes

UL Bytes Number of uplink bytes
DL Pkts Number of downlink packet
errors
UL Pkts Number of uplink packet errors

DL Pkt Err Number of downlink packet
errors
UL Pkt Err Number of uplink packet

errors
Figure 99 MSS Throughput Counters
Rev 1.2,
1. Page 80 of 146
Service Flow Throughput Counters

This set of metrics displays throughput on
on a per service flow basis. Since each service flow is
unidirectional the stats for downlink service flows will only reflect the DL stats while the uplink
service flows reflect the uplink stats.
DL Bytes Number of downlink bytes

UL Bytes Number of uplink bytes
DL Pkts Number of downlink packet errors
UL Pkts Number of uplink packet errors
DL Pkt Err Number of downlink packet
errors
UL Pkt Err Number of uplink packet errors
Figure 100 Service Flow Throughput Counters
RSSI
RSSI-CNR
Metrics
etrics
This set of metrics displays the RF stats of each CPE. RSSI and CINR statistics are available.
CINR Mean Mean CINR Value

CINR Std Dev CINR standard
deviation
RSSI Mean Mean RSSI Value

RSSI Std Dev RSSI standard
deviation
Figure 101 Physical Layer Metrics
Rev 1.2,
1. Page 81 of 146
Modulation Code Rate

Modulation coding scheme or MCS is provided for each CPE in the downlink and uplink
directions. The current MCS level is shown.
DL MCS Downlink MCS Level

UL MCS - Uplink MCS Level
MCS
S Level
QAM64 5/6
QAM64
QAM64 2/3
QAM64
QAM16
QAM16
QPSK
QPSK
Figure 102 MCS Rates Metrics
Rev 1.2,
1. Page 82 of 146
Active Service Flows

The active service flows currently associated on the system are displayed in this menu. Service
flow direction,
direction, service flow ID and SAID are available. At a minimum there are two service flows
per CPE and as much as 16 per CPE. The stats is sorted by MAC address of the CPE and
service flow index.
Svc Flow Dir Service flow direction;

Uplink or Downlink
Svc Flow
Flow CID Connection ID of the
service flow; 4096
Svc Flow SAID SAID of service flow
Figure 103 Active Service Flows Statistics

Registered SS
A list of all registered SS (subscriber stations) or CPE is available in this menu. Information
Informati
regarding the internal IDs or each CPE are displayed along with the OUI of the MAC address and
the CPEs MAC Version.
Basic CID Basic Connection ID of the

CPE
Primary CID Primary Connection ID of

the CPE
Vendor ID OUI of CPEs MAC address

that defines
efines the vendor of the CPE
Mac Version WiMAC Mac version

used by the CPE
Figure 104 Registered Subscriber Stations
Rev 1.2,
1. Page 83 of 146
8. Administration and Operation

8.1
Administration and Operation Via Web Interface

Administration and operation pertain to loggin
logging,
g, CPE provisioning, configuration file
control and reset functions.
8.1.1 CPE Provisioning

A database of Customer Premise Equipment (CPE) is stored locally on the base station.
This database is used to assign a specific client profile (service level) to each CPE.
CPE. As a
CPE is attempting to perform network entry to the base station, the MAC of the CPE is
compared against this database. If a matching entry exists, then the CPE is assigned the
configured client profile and the CPE is allowed to pass traffic. If a matching
matching entry does
not exist, then one of two things can happen. In the first scenario, the CPE will be given
a default client profile if default provisioning is enabled. Otherwise, with default
provisioning disabled, the CPE will fail to enter the netwo
network
rk and not be allowed to pass
traffic.
8.1.2 Logging
The logging section pertains to syslog notification levels and file access control. The base
station contains its own internal syslog server that gathers all statistics about the
function of the base station. An external syslog server may be configured for syslog
capture and viewing external to the base station. Individual log files are also available
for upload to an external PC for advanced troubleshooting.
Figure 105 Logging Menu Status
Rev 1.2,
1. Page 84 of 146
Remote
This selection allows users to configure setting for a remote syslog
This
log server. Utilizing this feature
will forward all related syslog traffic on the base station to the external syslog server configured.
Figure 106 Remote Syslog Server Configuration
Rev 1.2,
1. Page 85 of 146
Force Log File Rotation

Log files will grow in file size the longer a base station is running. The base station will perform a
log file rotation periodically that compresses the existing log file and renames it. Doing this
prevents any log file from growing
growing too large if many system messages are being generated. This
function allows the user to manually force this process to occur.
Figure 107 Force Log File Rotation
Rev 1.2,
1. Page 86 of 146
8.1.3 Configuration
Configuration pertains to the management of the Base Stations configuration database. The
base station configuration database is stored internally in a running configuration and a start-up
start
configuration. A running configuration is the currently active configuration for the base station as
opposed to the start
start-up
up configuration which only pertains to the configuration of the base station
when it initially boots up. Any changes made to the running config will not be persistent across a
system reboot unless the running config is copied over to tthe
he start-up
start up config. These system
level configuration databases are internal to the base station and cannot be deleted or moved,
however, the user can export portions or the entire configuration into external files that can be
transferred to a PC for backup
backup or editing purposes. This section will detail all the operations the
user has to manipulate the configuration database.
At the top level of the Configuration menu is a status page that displays the current operational
state of the configuration. The operational
operational state pertains to whether the configuration is
performing one of many different tasks, such as exporting, downloading, uploading or backing up
to name a few. Download and Upload Progress display the percentage of the file transferred to
the system.
syste Configuration Files lists the created configuration files that are currently available
along with their file size and the last date modified.
Figure 108 Configuration Menu Status Page
Rev 1.2,
1. Page 87 of 146
Copy
Copying an existing configuration file is po
possible
ssible in this section. The copy is performed by
selecting the existing file and specifying a new copied filename. Enabling the Force option will
overwrite the file to be created if one exists with the same name.
1. 1.) Select a file from the drop-down

drop down box
b
under Existing File Name
2. 2.) Enter the filename of the copy under
Copied File Name
3. 3.) (Optional) Select Force to overwrite if
a file of the same name exists
4. 4.) Select Perform
Figure 109 Copy Configuration File Page

Move
Moving a configuration file is the same as renaming a file and follows the same procedure as
coping.
5. 1.) Select a file from the drop-down
drop down box
under Existing File Name
6. 2.) Enter the filename of the copy under
New File Name
7. 3.) (Optional) Select Force to overwrite if a
file of the same name exists
8. 4.) Select Perform
Figure 110 Move Configuration File Page
Rev 1.2,
1. Page 88 of 146
Delete
Deleting a configuration file is permitted only on files that are created by the user. This is
performed by selecting the desired
desired file to be deleted and then selecting the Perform button.
Figure 111 Delete Configuration File
Export
Exporting creates an external copy of the configuration database in one of three
different forms. This copy is stored locally on the base station
station and is available for
upload or importing. Exporting creates an ASCII file that allows the user to
manually edit the file. These files follow an IOS
IOS-like
like format. To export the file,
select the type of exported configuration file and enter a name for the file and
then press Perform
Perform.
1. All - Export the entire
configuration database
2. CPE - Export the CPE
provisioning database only
3. Service Profile - Export the
Service Profile database only
Figure 112 Export Configuration File
Rev 1.2,
1. Page 89 of 146
Import
Importing a configuration file into the base station configures the base station will the parameters
specified in the file. Configuration files from other base station sharing the same software version
can be imported to ease in configuring complex settings.
Figure 113 Import Configuration Files

Write
This allows user to save new changes made to the base station into non-volatile
non volatile memory.
memory Doing
this makes the current configuration be persistent across a base station reboot.
Figure 114 Write Configuration
Rev 1.2,
1. Page 90 of 146
Backup
Backup creates a binary copy of the database in its entirety. The user can not edit a backup file.
Figure 115 Database Backup

Restore
Restoring the database configuration will completely replace the current configuration with the
backup. After restoration is complete the base station will reboot automatically.
backup.
Figure 116 Database Restoration
Rev 1.2,
1. Page 91 of 146
Download
This allows to user to download BS and CPE provision database configuration file from a remote
server or PC to the base station.
ftp://username:password@<ip_of_ftp_server>/dir/filename
ftp://username:password@<ip_of_ftp_server>/dir/
ftp://test:test123@192.168.1.5/
ftp://test:test123@192.168.1.5/BS_Backup.cnf
BS_Backup.cnf
Figure 117 Download Configuration files
Rev 1.2,
1. Page 92 of 146
Upload
This allows user to upload BS and CPE provision database configuration file to a remote server
or PC.
ftp://username:password@<ip_of_ftp_server>/dir/
ftp://username:password@<ip_of_ftp_server>/dir/filename
ftp://test:test123@192.168.1.5/
ftp://test:test123@192.168.1.5/BS_Backup.cnf
BS_Backup.cnf
Figure 118 Upload Configuration Files Page

Files
This section display all the BS backup and CPE provision database files.
Figure 119 List of Configuration Files
Rev 1.2,
1. Page 93 of 146
8.1.4 Administration
Reboot
Re
This allows user to cold boot the entire BS. A full base station reset takes approximately 5
minutes to boot.
Figure 120 Full Base Station Reboot Page
Reboot Sectors
Reboot-Sectors
Reboot-Sectors
Reboot
Sectors comma
command
nd will issue a reboot to the radio module of the base station. This is not a
full base station reboot but only a reboot of the radio module
Figure 121 Reboot Sector Modules only
Rev 1.2,
1. Page 94 of 146
9. Software Upgrade
9.1
Software Upgrade Via Web Interface

Upgrading firmware on the PureWave Quantum base station is a streamlined process that
requires only one click to perform. By simply providing access to the image via FTP or HTTP the
entire upgrade process will be handled automatically. Transfer of the image, writing of the flash
partition and base station reboot are all part of the automatic upgrade process.
An addition feature has been added that also allows the firmware image to be upgraded in two
parts. This allows for the firmware to be staged prior to the actual upgrade
upgrade process. A user can
prepare for the upgrade during the day or night before the actual cut-over
cut over and can simply execute
the transition during a scheduled maintenance window early in the morning. This reduces the
overall time spent performing the upgrade d
during
uring the early hours of the day.
9.1.1 Software Version and Status

The root of the software upgrade menu when selected will display a status page, which can be
found in the root menu system under software
software.. This status page displays the currently running
flash partition,
partition, the next boot flash partition, the specifc firmware image in both flash partitions and
a status of the current upgrade operation.
Figure 122 Software Version Status Page
Rev 1.2,
1. Page 95 of 146
9.1.2 Software Upgrade

Software upgrade performs a one-click
one click u
upgrade
pgrade operation from a single firmware image file. This
image file is transfer via FTP or HTTP/S depending on your network settings. A detailed
description of the url format is available when clicking on the blue question mark button.
Software Upgrade ccan
an be located in the following menu: Software -> Upgrade.. Here is an
example of the url string for transferring the image via FTP.
ftp://username:password@<ip_of_ftp_server>/dir/image-1.1.1.xxxx--pwnets.tgz
ftp://username:password@<ip_of_ftp_server>/dir/image
ftp://test:test123@192.168.1.5/image
ftp://test:test123@192.168.1.5/image-1.1.1.5675
1.1.1.5675-pwnets.tgz
pwnets.tgz
Figure 123 Software Upgrade Page

After entering the URL string into the text box, press perform to execute the upgrade process.
Select the software top level menu item to observe the status of the upgrade process. This status
will update
update the display automatically every 10 seconds.
Rev 1.2,
1. Page 96 of 146
9.1.3 Software Install

Software Install provides the user a two step installation process that allows for staging of new
firmware images. Software Install will transfer the image file to the base station,
station, prepare the
image, and load it into the flash partition without rebooting the base station. At this point the user
can let the base station operate normally until a designated maintenance window and then
perform the cut over to the new image. Softwar
Software
e Install is located at the following menu:
Software - > Install
Install.. Here is an example of the url string for transferring the image via FTP.
ftp://username:password@<ip_of_ftp_server>/dir/image
ftp://username:password@<ip_of_ftp_server>/dir/image-1.1.1.xxxx
1.1.1.xxxx-pwnets.tgz
pwnets.tgz
ftp://test:test123@192.168.1.5/image
ftp://test:test123@192.168.1.5/image-1.1.1.5675
1.5675-pwnets.tgz
Figure 124 Software Install Page

Press the perform button to execute the software install function. Select the software menu item
to view the status of the installation process. After the status has move to Idle,, the next step is to
perform a Software Boot which is located under the same Software menu and its function is
outlined below.
Rev 1.2,
1. Page 97 of 146
9.1.4 Software Boot

Software Boot is step two in the Software Install process that sets the non-active
non active flash partition to
the active partition and performs a base station reboot. Aside from completing the software install
procedure, this is how a user would swap between software images. The available drop-down
drop down
box has three options to choose from: A, B and Next. By selecting Next the system will
will make the
non active partition active and vice versa. Selecting the Now option will issue a base station
non-active
reboot after swapping the flash partitions. Selecting either A or B will make the active partition A
or B after reboot.
Figure 125 Software Boot

Boo Page
Rev 1.2,
1. Page 98 of 146
Appendix A
CLI Overview
The Fiji Base station provides a Cisco like CLI that can be accessed via the serial console connection or a user
initiated Secure-Socket-Shell
Secure
Shell (SSH) session.
When you log in to the CLI, you are in user EXEC mode. User EX
EXEC
EC mode contains only a limited subset of
commands. To have access to all commands, you must enter privileged EXEC mode, normally by using a password.
From privileged EXEC mode you can issue any EXEC command
commanduser
user or privileged modeor
mode or you can enter global
configuration mode. Most EXEC commands are one-time
one time commands. For example, show commands show
important status information, and clear commands clear counters or interfaces. The EXEC commands are not
saved when the software reboots.
Configuration modes allo
allow
w you to make changes to the running configuration. If you later save the running
configuration to the startup configuration, these changed commands are stored when the software is rebooted. To
enter specific configuration modes, you must start at global cconfiguration
onfiguration mode. From global configuration mode,
you can enter interface configuration mode and a variety of other modes, such as protocol-specific
protocol specific modes.
For simplicity and readability, the following sections will list Operational CLI commands (User/Privileged
(User/Privileged EXEC
mode commands) and Configuration CLI commands (Configuration mode commands). The prompt device-name#
device name#
indicates CLI is in operational mode. When moving from operational mode to configuration mode, command
config
config terminal
terminal is used and the prompt
mpt is changed from device
device-name
name# to device-name(config)#
device
(config)#.
9.1.5 General CLI Commands

This section describes the general CLI usability features related to command line editing, getting help
information, and the basic set of CLI commands for general purposes.
9.1.6 CLI Help

Entering a question mark ((?)) at the CLI prompt displays a list of commands available for each command
mode. You can also get a list of keywords and arguments associated with any command by using the
context sensitive help feature.
context-sensitive
To get help specific
specific to a command mode, a command, a keyword, or an argument, use one of the
following commands:
Command
Help
abbreviated command-entry?
abbreviated-command
abbreviated-command
abbreviated
command-entry<Tab
Tab>
?
command ?
Purpose
Provides a brief description of the help system in any command
mode.
Provides a list of commands that begin
begin with a particular character
string. (No space between command and question mark.)
Completes a partial command name.
Lists all commands available for a particular command mode.
Lists the keywords or arguments that you must enter next on the
command line. (Space between command and question mark.)
Table 1:: CLI Command Help
9.1.7 Command line editing

The default key strokes for editing the command line and moving around the command history are as
follows. Note that it is possible to change these commands using the keymap clispec modification.
Rev 1.2,
1. Page 99 of 146
9.1.7.1 Moving the cursor

Move the cursor back one character
Ctrl-b
b or Left Arrow
Move the cursor back one word
Esc-b or Alt-b
Move the cursor forward one character
ch
Ctrl-ff or Right Arrow
Move the cursor forward one word
Esc-ff or Alt-f
Alt
Move the cursor to the beginning of the command line
Ctrl-aa or Home
Move the cursor to the end of the command line
Ctrl-e
e or End
9.1.7.2 Delete characters

Delete the character befo
before
re the cursor
Ctrl-h,
h, Delete, or Backspace
Delete the character following the cursor
Ctrl-d
Delete all characters from the cursor to the end of the line
Ctrl-k
Delete the whole line
Ctrl-u
Ctrl or Ctrl-x
Delete the word before the cursor
Ctrl-w, Esc-Backspace,
Backspace, or Alt-Backspace
Alt
Delete the word after the cursor
Esc-d
d or Alt-d
Alt
9.1.7.3 Insert recently deleted text

Insert the most recently deleted text at the cursor
Ctrl-y
9.1.7.4 Display previous command lines

Scroll backward through the command history
Ctrl-p
p or Up
U Arrow
Scroll forward through the command history
Ctrl-n
n or Down Arrow
Search the command history in reverse order
Ctrl-r
Show a list of previous commands
Run the "show cli history" command
9.1.7.5 Capitalization
Capitalize the word at the cursor, i.e. make tthe
he first character
uppercase and the rest of the word lowercase.
Esc-c
Change the word at the cursor to lowercase.
Esc-l
Change the word at the cursor to uppercase.
Esc-u
9.1.7.6 Special
Abort a command/Clear line
Ctrl-c
Ctrl
Quote insert character, ie do not treat the next keystroke as an edit command.
Ctrl-v/ESC-q
Ctrl
Redraw the screen
Ctrl-l
Ctrl
Transpose characters
Ctrl-t
Ctrl
Enter multi-line
multi line mode. This lets you enter multi
multi-line
line values when prompted for a value in the CLI. It is not
available when editing a CLI command. ESC
ESC-m
Exit configuration mode. Only in CC and I-style.
style.
Ctrl-z
9.1.8 General Operational Mode Commands

9.1.8.1 config terminal
Switch from operational mode to configuration mode. Options are:
Rev 1.2
2, Page 100 of 146
9.1.8.2 terminal
Edit a private copy of running configuration, no lock

lock is taken.
9.1.8.3 enable (<level>)

Only available in IOS (i) mode. Enables privileged EXEC commands. The default level is 15. The CLI
will prompt for a password if a password has been assigned to the level.
9.1.8.4 disable (<level>)

Only available in IOS (i) mode. Downg
Downgrade
rade to a lower privilege level.
9.1.8.5 help <command>

Display help text related to <command>
9.1.8.6 history [<limit>]

Display CLI command history.
9.1.8.7 logout
9.1.8.8 logout session <session-id>
<session
9.1.8.9 logout user <user
<user-id>
Terminate the current session, a session identified by a particul
particular
ar session ID or all session
associated with a user ID.
9.1.8.10
paginate <true | false>

Display CLI output in a page format based on the defined screen width and length parameters.
9.1.8.11
ping <hostname> [ count <int> ] [ interval <seconds> ] [ size <bytes> ]

Perform a d
diagnostics
iagnostics ping command along with optional arguments.
9.1.8.12
screen
screen-length
length <num-rows>
<num
Configure the CLI session screen length value for the number of rows displayed for each screen
page.
9.1.8.13
screen
screen-width
width <num-columns>
<num columns>
Configure the CLI session screen width value for the number of columns displayed for each
screen page.
9.1.8.14
terminal <generic | xterm | vt100 | ansi | linux>

Configure the terminal type to one of the supported types.
9.1.8.15
traceroute <hostname>
Perform a diagnostics traceroute command for a particular hostname or IP address.
9.1.8.16
who
Display currently logged on users. The current session, i.e. the session running the show status
command, is marked with an asterisk.
Example:
Rev 1.2
2, Page 101 of 146
io# who
Session User
*7
joe
io#
9.1.8.17
Context From
cli
Proto
127.0.0.1
Date
console 13:19:05
show cli
Display CLI session configuration settings.
9.1.8.18
show running
running-config
config [details | all]
Display current running configuration. By default the whole configuration is displayed. Per
default only elements that have been explicitly set to a value are shown.
shown. This makes it easier to
handle large configurations. However, it is possible to force the show command to display all
elements. This is done using the 'details' or 'all' options.
9.1.8.19
show startup
startup-config
config [details | all]
Display the startup configuration that was last saved and loaded at system startup. Per default
only elements that have been explicitly set to a value are shown. This makes it easier to handle
large configurations. However, it is possible to force the show command to display all elements.
This is done using the 'details' or 'all' options.
9.1.9 General Configure Mode Commands

9.1.9.1 alias ( <alias
<alias-name>
name> <alias-expansion>)
<alias expansion>)
Defines the alias alias-name.
alias name. It will be expanded to alias
alias-expansion.
expansion. The alias can be used
anywhere on the command line. After a command with an alias has been entered, the expanded
command line is displayed so that you can verify the alias value.
For example:
io# alias myUser c87923
io# config t
Entering configuration mode terminal
io(config)# aaa authentication users user myUser
io(confi
io(config)#
g)# aaa authentication users user c87923
9.1.9.2 clear
Remove all configuration changes.
9.1.9.3 cli session idle

idle-timeout
timeout <length in minutes>
Configure the CLI session inactivity timeout required before the CLI automatically logs a user out.
9.1.9.4 configuration copy source <filename>

<filename> dest <filename> [force]
9.1.9.5 configuration move source <filename> dest <filename> [force]
Rename or copy selected configuration source file to the destination filename.
9.1.9.6 configuration delete <filename>

Delete the selected configuration file (cannot be the current configuration file being used).
Rev 1.2
2, Page 102 of 146
9.1.9.7 configuration export pathfilter <All | CPE | Service

Service-Profile>
Profile> filename <filename>
Save existing running configuration to the specified filename. The export command can be
limited to a part of the configuration by pr
providing
oviding a <pathfilter>
<
> NOTE: Current values supported
are All, Service
Service-Profile
Profile and CPE.
9.1.9.8 configuration import source <filename> [overwrite]

Import the specified configuration filename into the running database. The default behavior is to
merge the con
configuration,
figuration, unless the optional argument overwrite is used.
9.1.9.9 configuration download source-url

source url <URL> dest
dest--filename
filename <destination filename>
ACTION: This command will download the file from the specified URL, using the destination file
name if provided.
9.1.9.10
configuration
figuration upload source-filename
source filename <filename> dest-url
dest url <URL>
ACTION: This command will upload the selected file to the specified destination URL.
9.1.9.11
configuration write
Save the current running configuration to the startup configuration file (same as write memory
memory
command).
9.1.9.12
do <command>
Run command in operational mode.
9.1.9.13
enable (secret | password) level <level> ( 0 | 7) <password>

Only available in IOS (i) mode. Configures a password for a specific EXEC level. If both a password
and a secret is configured, the secret is used.
secret | password
Specifies how the password is to be encrypted
<level>
The EXEC level to password protect (1
(1-15)
0|7
Use 0 to indicate that the password given at the end of the
command is in plain text, and 7 for an already encrypted
encrypte
password.
<password>
The actual password
Example:
io(config)# enable secret level 3 0 bluebox
io(config)#
9.1.9.14
exit (level | configuration-mode)

configuration mode)
level
Exit from current mode. If performed on the top level, will exit
configure mode. This is the default iiff no option is given.
configuration
configuration-mode
mode
Exit from configuration mode regardless of mode.
9.1.9.15
help <command>
Shows help text for command.
9.1.9.16
privilege <mode> level <level> <command>

Only available in IOS (i) mode. Configures for which level a command should be
available.
vailable.
Rev 1.2
2, Page 103 of 146
<mode>
In which mode is the command.
<level>
In which privilege level should the command be available (1(1-15)
<command>
Command string.
Example:
io(config)# privilege exec level 4 show
io(config)#
9.1.9.17
pwd
Display current submode path.
9.1.9.18
rollback con
configuration
figuration [<number>
[<number>]
Return the configuration to a previously committed configuration. The system stores a
limited number of old configurations. The number of old configurations to store is
configured in the confd.conf file. If more than the configured number
number of configurations are
stored, then the oldest configuration is removed before creating a new one.
The most recently committed configuration (the running configuration) is number 0, the
next most recent 1, etc.
The files are called rollback0 - rollback
rollbackX,
X, where X is the maximum number of saved
committed configurations.
Example:
io(config)# rollback configuration 1
io#
9.1.9.19
show configuration rollback changes <nr>

Show changes for rolling back to rollback file nr.
9.1.9.20
show full
full-configuration
configuration [details] [[<pathfilter
<pathfilter> ]
Show current configuration. The show command can be limited to a part of the
configuration by providing a <pathfilter>.
9.1.9.21
write memory
Save the current running configuration to the startup configuration file.
9.1.9.22
write terminal [details] [<pathfilter>

[<pathfilter> ]
Display
lay current running configuration in the terminal window. The write terminal
command can be limited to a part of the configuration by providing a <pathfilter>.
Rev 1.2
2, Page 104 of 146
9.2
SYSTEM CLI COMMANDS
9.2.1 System Operational Mode Commands

9.2.1.1 reboot [sectors | force]
ACTION: Reboot the entire system. The optional sectors argument is for resetting all
BS sectors. The force argument can be used to ignore system shutdown and force BS reboot.
9.2.1.2 show clock

Display current system time, date and time zone.
9.2.1.3 show gps

Display current GPS information
information including latitude, longitude, altitude and status. The
Synchronization loss counters keep track of the total number of times the GPS has lost synch and
how many of them were past the configured recovery threshold (counter for number of WMD
resets due to GPS synch loss).
# show gps
GPS Information:
Enabled:
true
Synch--Recovery
Recovery Timeout:
true
Status:
Offline
Longitude:
0.000000
Latitude:
0.000000
Altitude:
0.000000
Synch Loss:
15
Non-Recoverable
Recoverable Synch Loss: 5
9.2.1.4 show ntp

Display current N
NTP
TP settings.
9.2.1.5 show system

Display basic system information.
9.2.1.6 show system inventory

Display system inventory information.
9.2.1.7 show system utilization

Display system CPU and memory utilization information.
9.2.1.8 tech-support
tech support generate-system-debug
generate
debug-log
Generate technical support information that contains detailed BS system information and
saved to a log file that can be uploaded for PureWave Technical support team to review.
9.2.2 System Configure Mode Commands

9.2.2.1 clock set time <hh:mm:ss.sss> [date <yyyy
<yyyy--mm-dd>]
Set the system cl
clock
ock with the specified time. The optional date can also be provided,
otherwise the date will be left unchanged.
NOTE: Only available if NTP is DISABLED
Rev 1.2
2, Page 105 of 146
9.2.2.2 clock timezone <zone>

9.2.2.3 no clock timezone
Set the system time zone from a list of supported time zone values.
values. The no option sets
the time zone to the default UTC value.
9.2.2.4 [no] dns search <domain-name>

<domain
Configure list of DNS search domain names. The no option is used to delete the
specified name server.
9.2.2.5 [no] dns server <IP address>

Configure a list of DNS name
name servers. The no option is used to delete the specified
name server.
9.2.2.6 gps disabled <true | false>

Enable or disable GPS device (Default is enabled).
9.2.2.7 ntpdate ip-address

ip address <IP address>
ACTION: Set the system clock using the specified NTP server. This is one-time
one time operation
which does not provide NTP clock synchronization afterwards. This command will fail if
NTP is enabled, since NTP and this command both use the same NTP socket.
NOTE: Only available if NTP is DISABLED
9.2.2.8 ntp server <IP address> [version <numbe

<number>]
r>]
9.2.2.9 no ntp server <IP address>
Add or remove an NTP server from the configuration. Supported NTP version numbers
are 3 and 4, with a default of 4 if not specified.
9.2.2.10
ntp server <IP address> enabled <true | false>

Disable or re
re-enable
enable an NTP server in the con
configuration.
figuration. Disabling NTP servers allows
the user to keep the configuration by making the server entry inactive.
9.2.2.11
ntp enabled <true | false>

Enable or disable NTP support altogether.
9.2.2.12
system base
base-station
station groupgroup-id
id <string (0-64)>
(0
Set the system group ID (string
(stri 64 chars max) which is use by the EMS to identify the
group the base station belongs to.
9.2.2.13
system base
base-station
station groupgroup-descr
descr <string>
Set the system group description for the group ID that is configured.
9.2.2.14
system base
base-station
station asn-gateway
asn gateway ip
ip-address
address <IP address>
addr
Set the system Base station ASN gateway IP address, which is only applicable if the
mode selected is asn-gateway.
asn gateway. This information is global and will be propagated to all
Sectors for configuration and usage.
Rev 1.2
2, Page 106 of 146
9.2.2.15
system base
base-station
station mode <standalone
<standalone-locall | standalone-remote
standalone remote | asnasngateway >
Set the system Base station operational mode to standalone local provisioning,
standalone remote provisioning database (remote provisioning requires a AAA Radius
server configuration see command system base
base-station
station radius ip address <IP
address>), or ASN gateway which requires the setting of the ASN gateway IP address.
This configuration will be needed by each sector so that they can figure where to forward
all CPE lookup requests (TLV-based
(TLV based message request sent to WMD Manager, external
AAA/Radius server or ASN gateway).
9.2.2.16
system base
base-station
station radius ip
ip-address
address <IP address>
Set the system Base station Radius/AAA server IP address to be used by all Sectors for
configuration and usage.
9.2.2.17
system base
base-station
station radius port
port-number
er <port>
Set the system Base station Radius/AAA server IP port number to be used by all Sectors
for configuration and usage.
9.2.2.18
system base
base-station
station radius secret <key
<key-string>
Set the system Base station Radius/AAA server secret to be used by all Sectors for
configuration and usage.
9.2.2.19
system contact <contact info>

Set the system contact information.
9.2.2.20
system console baudrate <9600 | 19200 | 38400 | 57600 | 115200>
9.2.2.21
no system console baudrate

Set the system console baud rate to the specified value. The no option sets
sets the baud
rate to the default value 38400 bps.
9.2.2.22
system hostname <name>
9.2.2.23
no system hostname
Set the system hostname to the specified string name. The no option is used to reset
the system hostname to default.
9.2.2.24
[no] system interface dhcp

Configure the syst
system
em management interface for DHCP which ignores the configured IP
address / netmask settings used for the Base station control and management. The no
option disables DHCP on the system interface, enables usage of the configured IP
address/netmask.
9.2.2.25
system interface ip address <IP address> <netmask>
9.2.2.26
no system interface ip address <IP address>

Set the system management IP address and netmask used for Base station control and
management. The no option sets the IP address to the system default.
Rev 1.2
2, Page 107 of 146
9.2.2.27
system interfa
interface
ce ip default-gateway
default gateway <IP address>
9.2.2.28
no system interface ip default

default-gateway
gateway
Set the system management default gateway route used for the Base station control and
management. The no option removes the system default gateway route.
9.2.2.29
system interface mtu <mtu size in bytes>
9.2.2.30
no system interface mtu

Set the system management maximum MTU size in bytes which is applied to all the
interfaces associated with the management bridge interface. The no option resets the
MTU to its default value.
9.2.2.31
system location <location

<location info>
Set the system location information.
Rev 1.2
2, Page 108 of 146
9.3
LOGGING CLI COMMANDS
This section provides a brief overview of our system logging infrastructure and its configuration
capabilities that will provide very useful system debugging capabilities. The following diagrams
diagrams provide a
visual display of this logging functionality.
Figure 1 - Logging Configuration
Rev 1.2
2, Page 109 of 146
9.3.1 Logging Operational Mode Commands

9.3.1.1 show log continuous [ count <linecount> ]
Display the last ten lines of the current log file
file,, and then continue to display new lines as
they come in, until the user hits Ctrl+C. If the count option is entered, then the last
linecount lines will initially be displayed. The command is equivalent to invoking Linux
tail -f on the logfile.
9.3.1.2 show log [ count <linecount> ]

Display the first ten logged events from syslog. If the count option is entered, then the
first linecount lines will be displayed. The command is equivalent to invoking Linux head
on the logfile.
9.3.1.3 show log last [ count <linecount> ]

Display
splay the last ten logged events from syslog. If the count option is entered, then the
last linecount lines will be displayed. The command is equivalent to invoking Linux tail
on the logfile.
9.3.1.4 show log files

Display list of local log files.
9.3.1.5 [help] show log interactive

Pipe the logfile through the Linux less utility. This provides an interactive session in
which the user can search and navigate forwards and backwards. If the help option is
entered, verbose instructions on the less utility is displayed.
9.3.1.6 show log

log files upload status
Display status of log file upload progress.
9.3.1.7 show logging

Display system logging configuration settings.
9.3.2 Logging Configure Mode Commands

9.3.2.1 logging file <filename> delete
ACTION: Delete the selected file from the available list of log files.
f
9.3.2.2 logging file rotation force

ACTION:
ACTION:Force
Force an immediate rotation of all the log files.
9.3.2.3 logging file <filename> upload dest

dest-url
url <URL>
ACTION:
ACTION:Upload
Upload the specified log file to a remote server identified by the provided URL.
Rev 1.2
2, Page 110 of 146
9.3.2.4 logging global level <log level>

leve
9.3.2.5 logging local level <log level>
9.3.2.6 no logging local level
Set the minimum logging level for the default global system log messages (Default:
NOTICE in syslog.conf). It alters the settings in syslog.conf and also alters the source
filter levels in each application
application equipped with such. The following set of log levels are
supported: none, emergency, alert, critical, error, warning, notice, info, debug, trace1,
trace2, trace3
trace3.. The none log level disables local logging feature, and the no option
resets the lo
log
g level to the default value.
9.3.2.7 logging local override source <app

<app-name>
name> level <log level>
9.3.2.8 no logging local override source <app
<app-name>
name> level
Override the minimum logging level for the source application generating system log
messages. This allows specific a
applications
pplications to override the default global system log
level and provide more debugging capabilities for that application. This change will also
be propagated to the syslog.conf file.
Supported values for level are the same as for the logging local level command.
co
Supported values for source are: system, swupgrade.
swupgrade. (More values will appear as
additional application daemons are created.)
The none log level disables local logging feature, and the no option resets the log level
to the default value.
9.3.2.9 no logging
logging local override
Disables the logging overrides for all applications (including level and trace).
9.3.2.10
logging local override source <app

<app-name>
name> trace <trace level>
9.3.2.11
logging local trace <tracelevel>
9.3.2.12
logging remote level <log level>
9.3.2.13
no logging remote level

Set
et the default minimum logging level for messages sent to all configured remote syslog
servers. The following set of log levels are supported: none, emergency, alert, critical,
error, warning, notice, info, debug
debug.. The none log level disables local logging
logging feature,
and the no option resets the log level to the default value.
9.3.2.14
[no] logging remote host <IP address>

Send syslog messages to a remote syslog server. The server will use the default level set
using the logging remote level command
command.
Use the no option
ption to stop sending messages to the specified server (and delete its entry
from syslog.conf).
Rev 1.2
2, Page 111 of 146
9.3.2.15
logging remote host <IP address> level <log level>
9.3.2.16
no logging remote host <IP address> level

Set the minimum logging level for messages sent to the specified remote
remote syslog server.
The following set of log levels are supported: none, emergency, alert, critical, error,
warning, notice, info, debug, default
default. The none level disables logging to the specified
server (but keeps its entry in syslog.conf, commented out). The default option sets the
level to the default configured via the logging remote level command.
The no option sets the level to the default value of default.
9.4
NETWORKING CLI COMMANDS
9.4.1 Networking Operational Mode Commands

9.4.1.1 show arp [static]
Display the entire
entire ARP cache table or just the statically configured ARP cache table entries.
9.4.1.2 show interface [<ifname>]

Display interface configuration information for all interfaces or the specified interface name.
9.4.1.3 show interface [<ifname>] stats

Display interface stat
statistics
istics information for all interfaces or the specified interface name.
9.4.1.4 show interface [<ifname>] stats detail

Display detailed interface statistics information for all interfaces or the specified interface name.
9.4.1.5 show ip route

Display the system routing table
table including dynamic and static route entries.
9.4.1.6 show ip route static

Display the list of configured static route table entries.
9.4.2 Networking Configure Mode Commands

9.4.2.1 arp <IP address> <MAC address>
9.4.2.2 no arp <IP address>
Add or delete a static ARP cache table ent
entry.
ry.
9.4.2.3 arp clear-cache

cache
ACTION: Clear the ARP cache table (Action command).
9.4.2.4 [no] interface <ifname> dhcp

Configure the specified interface for DHCP which ignores the configured IP address /
netmask settings. The no option disables DHCP on the specified interface,
interface, enables
usage of the configured IP address/netmask.
Rev 1.2
2, Page 112 of 146
9.4.2.5 interface <ifname> ip address <IP address> <netmask>

9.4.2.6 no interface <ifname> ip address <IP address>
Set the system IP address and netmask to the specified interface. The no option
removes the IIP
P address configuration.
9.4.2.7 interface <ifname> mtu <mtu size in bytes>

9.4.2.8 no interface <ifname> mtu
Set the system MTU size in bytes to the specified interface. The no option resets the
MTU to its default value.
9.4.2.9 interface <ifname> speed-duplex

speed duplex <auto | 1G
1G--full | 100M--full | 10M-full>
full>
9.4.2.10
no interface <ifname> speed

speed-duplex
Set the specified interfaces speed and duplex settings. The no option resets the
specified interfaces speed and duplex settings to its default value (auto).
9.4.2.11
[no] interface <ifname> shutdown

Enable
ble / disable the specified interface.
9.4.2.12
ip route <network prefix> <network mask> <next hop IP address>
9.4.2.13
no ip route <network prefix> <network mask> [<next hop IP address>]

Create/modify or delete a static route table entry. If the no option is called with
with only a
network prefix and mask, it deletes all routes for that prefix.
9.5
USER MANAGEMENT CLI COMMANDS
9.5.1 User Management Operational Mode Commands

9.5.1.1 show usernames
Display the list of all configured user accounts and their associated capabilities.
9.5.1.2 show users

Display a list of all currently logged-in
logged in users, and session based information such as idle time and
what host/interface they have connected from.
9.5.2 User Management Configure Mode Commands

9.5.2.1 username <userid> password
9.5.2.2 username <userid> password <clear text pa
password>
ssword>
9.5.2.3 username <userid> password 7 <encrypted password>
This command will create/modify a user account and prompt for a password if it is not
provided.
Rev 1.2
2, Page 113 of 146
9.5.2.4 username <userid> capability <admin | operator>

9.5.2.5 no username <userid> capability
This command will configure
configure the user account specific privilege level. The no option is
used to revert to the default admin privilege level.
9.5.2.6 no username <userid>

Delete a user account from the configuration.
9.6
AAA CLI COMMANDS
9.6.1 AAA Operational Mode Commands

9.6.1.1 show aaa
Display the AAA configuration information.
Display
9.6.2 AAA Configure Mode Commands

9.6.2.1 aaa authentication login default <auth method> [<auth method> [<auth
method>]]
9.6.2.2 no aaa authentication login

Sets the list of acceptable authentication methods for system logins. 'local', 'radius',
'radi
'tacacs+' are acceptable methods. The order in which the methods are specified is the
order in which the authentication is attempted.
9.6.2.3 aaa authorization map default-user

default user <user name>
9.6.2.4 no aaa authorization map defaultdefault-user
When a user is authenticated (via
(via RADIUS or TACACS+) and does not have a local
account, this command specifies what local account the authenticated user will be logged
on as. If the user name is local, this mapping is ignored. This mapping is used depending
on the setting of the 'authorization
'authorization map order'.
9.6.2.5 aaa authorization map order <remote

<remote-only,
only, remote-first,
remote first, local-only>
local only>
9.6.2.6 no aaa authorization map order
Can be set to one of three choices: 'remote
'remote-first',
first', 'remote-only',
'remote only', or 'local'local-only'.
only'. Used when
authenticating users via RADIUS or TACACS+. The order determines how the remote
user mapping behaves. Again, if the authenticated user name is valid locally, no mapping
is performed.
The setting has the following three possible behaviors:
1. remote
remote-first:
first: If a local-user
local user mapping attribute is returne
returned
d by the remote authentication
server and is a valid local user name, map the authenticated user to the local user
specified in the attribute. Otherwise, if the attribute is not present or not valid locally, use
the user specified by the defaultdefault-user command.
nd. (This is the default behavior).
2. remote
remote-only:
only: Only try to map a remote authenticated user if the remote authentication
server sends a local-user
local user mapping attribute. If the attribute does not specify a valid local
user, no further mapping is tried, and the user is not permitted to log in.
Rev 1.2
2, Page 114 of 146
3. local
local-only:
only: All remote users will be mapped to the user specified by the 'aaa
authorization map default-user
default user <user name>' command. Any vendor attributes received
by an authentication server are ignored.
9.7
RADIUS CLI COMMANDS
9.7.1 RADIUS Operational Mode Commands

9.7.1.1 show radius
Display the RADIUS configuration information.
9.7.2 RADIUS Configure Mode Commands

9.7.2.1 radius-server
radius server timeout <seconds>
9.7.2.2 no radius-server
radius server timeout
Sets (or resets to the default) a global communication value for all RADIUS servers. Can
be overridden in a 'radius-server
'radius server host' command. Default is 3. Sets the timeout for
retransmitting a request to any RADIUS server. Range is 1-60.
1
radius server retransmit <retries>
radius server retransmit
Sets (or resets to 0) a global
global communication value for all RADIUS servers. Can be
overridden in a 'radius-server
'radius server host' command. Defaults to 1. Sets the number of times the
client will attempt to authenticate with any RADIUS server. To disable retransmissions set
it to zero. Range is 0-5.
radius server key [<string>]
radius server key
Sets (or clears) a global communication value for all RADIUS servers. Can be
overridden in a 'radius-server
'radius server host' command. Sets the shared secret text string used to
communicate with any RADIUS serve
server.
If the positive form of the command is used with no key, the user will be prompted for the
key. Any entries made at this prompt will only echo with the '*' character, and the user
will have to enter the same string twice for confirmation.
radius server login-lat
lat-group
group <string>
radius server login-lat-group
login
Sets (or clears) the string to send as the LOGIN_LAT_GROUP attribute in all RADIUS
requests (authentication_request, accounting_request, and password_request). If the
string is cleared (or set to the empty string), the attribute will not be sent. Note that this
can be overridden on a per-host
per host basis using commands documented below.
Rev 1.2
2, Page 115 of 146
radius server host <ip-address>
<ip address> [auth
[auth-port
port <port-number>]
<port number>] [timeout <seconds>]
[retransmit <retries>] [key <string>| pr
prompt--key] [login--lat-group
group <string>]
9.7.2.10
no radius
radius-server
server host <IP address> [auth
[auth-port
port <port-number>]
<port number>]
Add a RADIUS server to the set of servers used for authentication. Some of the
parameters given may override the configured global defaults for all RADIUS servers.
servers.
The 'auth
'auth-port'
port' defaults to 1812 and is used for authentication requests.
The same IP address can be used in more than one 'radius-server
'radius server host' command as
long as the 'auth
'auth-port'
port' is different for each. 'auth
'auth-port'
port' is a UDP port number. 'auth-port'
'auth port'
must
st be specified immediately after the host option (if present).
The "prompt
"prompt-key"
key" parameter is mutually exclusive with "key <string>". It requests to be
prompted for the key, with the entry echoed as '*' characters, for greater security.
If 'no radius
radius-server
rver host <ip-address>'
<ip address>' is specified, all radius specific configuration for this
host is deleted. 'no radius-server
radius server host <IP address> auth
auth-port
port <port>' may be specified to
refine which host is deleted, as the previous command will delete all RADIUS servers
with the specified IP address.
The login
login-lat-group
group parameter overrides the global setting if it is not the empty string.
Specifying the empty string here means to use the global setting for this host.
RADIUS servers are tried in the order they are config
configured.
9.8
IMAGE MANAGEMENT CLI COMMANDS
9.8.1 Image Management Operational Mode Commands

9.8.1.1 show image
Display the list of installed images along with the image upgrade/candidate status.
9.8.1.2 show image upgrade status

Display the image upgrade status.
9.8.2 Software Image Manag

Management
ement Configure Mode Commands
9.8.2.1 software install url <URL>
ACTION: This command will download the image from the specified URL, verify its
integrity via MD5 checksum and install the image on the other non-running
non running partition.
9.8.2.2 software upgrade url <URL>

ACTION
ACTION: This command will download the image from the specified URL, verify its
integrity via MD5 checksum, install the image on the other non-running
non running partition, select
the newly installed partition for next boot and reboot the system.
9.8.2.3 software boot select <A | B | Next> [now]

Select the image that will be used during the next reboot. Options are to select image
partition A, or B or the next partition that is not currently running. The optional now
argument will switch boot partitions as specified and perform a reboot right after NOTE:
This option should prompt the user to verify the operation and notify them of the reboot
that will occur.
Rev 1.2
2, Page 116 of 146
9.9
FILE MANAGEMENT CLI COMMANDS
9.9.1 File Management Operational Mode Commands (FUTURE)

9.9.1.1 show files configuration
Display the list of configuration files which include database configuration files as all as
exported partial configuration files such as CPE database.
9.9.1.2 show file download status

Display the file download status.
9.9.1.3 show files statistics

Display the list of statistics files.
f
9.9.1.4 show files tech

tech-support
support
Display the list of tech-support
tech support generated files.
9.9.1.5 show file upload status

Display the file upload status.
9.9.2 File Management Configure Mode Commands (FUTURE)

9.9.2.1 file download configuration <URL> [<destination filename>]
ACTION: This
s command will download the file from the specified URL, using the
destination file name if provided.
9.9.2.2 file download cancel

ACTION: This command will cancel an existing file download operation.
9.9.2.3 file upload configuration <filename> <URL>

ACTION: This command
command will upload the selected file to the specified destination URL.
9.9.2.4 file upload statistics <filename> <URL>

9.9.2.5 file upload tech

tech-support
support <filename> <URL>
9.9.2.6 file upload cancel

ACTION: This command will cancel an existing file upload operation.
Rev 1.2
2, Page 117 of 146
9.10 SSH / TELNET / WEB SERVER CLI COMMANDS

9.10.1 SSH / Telnet / Web Server Operational Mode Commands
9.10.1.1
show ssh se
server
rver
Display the SSH server configuration settings.
9.10.1.2
show ssh server host-keys

host
Display the SSH server information including the host key fingerprints and full host keys.
9.10.1.3
show telnet
Display the Telnet server configuration settings.
9.10.1.4
show web
Display the Web UI server configuration settings.
9.10.2 SSH / Telnet / Web Server Configure Mode Commands

9.10.2.1
ssh server enabled | disabled

This command will enable or disable the SSH server (Default is enabled).
9.10.2.2
ssh server ports <port> [<port2> [<port3>]]

This command will configure
configure the list of TCP ports that the SSH server listens on. A
minimum of 1 port needs to be provided. The default port is 22.
9.10.2.3
ssh server host

host-key
key generate
ACTION: This command will re-generate
re generate new host keys (RSA and DSA) for the SSH
server. These keys are automatically
automatically generated during first system boot, and dont need
to be re
re-generated
generated unless a security breach is suspected or the IP/hostname has
changed.
9.10.2.4
telnet server enabled | disabled

This command will enable or disable the Telnet server (default is Disable).
Disable).
9.10.2.5
web server enabled | disabled

This command will enable or disable the Web UI server (Default is enabled).
9.10.2.6
web http enabled | disabled

This command will enable or disable HTTP access to the Web UI server (Default is
disabled).
9.10.2.7
web http port <TCP port>

po
9.10.2.8
no web http port

This command will configure TCP port number for HTTP. The default is port 80 which is
set when the no option is selected.
Rev 1.2
2, Page 118 of 146
9.10.2.9
web https enabled | disabled

This command will enable or disable HTTPS (HTTP over SSL) access to the Web UI
server
rver (Default is enabled).
9.10.2.10
web https port <TCP port>
9.10.2.11
no web https port

This command will configure TCP port number for HTTPS. The default is port 443 which
is set when the no option is selected.
9.10.2.12
web https certificate generate

ACTION: This command will generate
generate a new certificate to use for HTTPS
communications.
9.10.2.13
web idle
idle-timeout
timeout <length in minutes>
Configure the length of user inactivity required before the Web UI automatically logs out a
user.
9.11 SNMP SERVER CLI COMMANDS

9.11.1 SNMP Server Security Background
9.11.1.1
SNMPv3
SNMPv3 provides secure access to devices by a combination of authenticating and

encrypting frames over the network. The security features provided in SNMPv3 are the
following:
Message integrity
integrityEnsures
Ensures that a packet has not been tampered with in-transit.
in
Authentication
AuthenticationDetermines
Determines the message is from a valid source.
Encryption
EncryptionScrambles
Scrambles the packet contents to prevent it from being seen by
unauthorized sources.
SNMPv3 provides for both security models and security levels. A security model is an
authentication strategy that is set up for a user and the role in which the user resides. A
authentication
security level is the permitted level of security within a security model. A combination of
a security model and a security level determines which security mechanism is employed
when handling an SNMP packet.
9.11.1.2
Security Models and Levels for SNMPv1, v2, v3
The security level determines if an SNMP message needs to be protected from disclosure
and if the message needs to be authenticated. The various security levels that exist within
a security model are as follows:
Rev 1.2
2, Page 119 of 146
noAuthNoPriv
noAuthNoPrivSecurity
Security level that does not provide authentication or encryption.
authNoPriv
authNoPrivSecurity
Security level that provides authentication but does not provide
encryption.
authPriv
Security
Security level that prov
provides
ides both authentication and encryption.
Three security models are available: SNMPv1, SNMPv2c, and SNMPv3. The security
model combined with the security level determine the security mechanism applied when
the SNMP message is processed.
9.11.1.3
User-Based
Based Security
Security Model
The following table identifies what the combinations of security models and levels mean.
Model
Level
Authentication
Encryption
What Happens
v1
noAuthNoPriv Community string
No
Uses a community string match for

authentication.
v2c
noAuthNoPriv
uthNoPriv Community string
No
Uses a community string match for

authentication.
v3
noAuthNoPriv Username
No
Uses a username match for

authentication.
v3
authNoPriv
HMAC-MD5
HMAC MD5 or
HMAC-SHA
HMAC SHA
No
Provides authentication based on

the Hash-Based
Hash Based Message
Messa
Authentication Code (HMAC)
Message Digest 5 (MD5)
algorithm or the HMAC Secure
Hash Algorithm (SHA).
v3
authPriv
HMAC-MD5
HMAC MD5 or
HMAC-SHA
HMAC SHA
DES
Provides authentication based on

the HMAC-MD5
HMAC MD5 or HMAC-SHA
HMAC
algorithms. Provides Data
Encryption Standard (DES) 56-bit
encryption in addition to
authentication based on the Cipher
Block Chaining (CBC) DES
(DES-56)
(DES 56) standard.
Table 2:: SNMP Security Models and Levels
SNMPv3 User
User-Based
Based Security Model (USM) refers to SNMP message-level
message level security and
offers the following services:
Rev 1.2
2, Page 120 of 146
Message integrity
integrityEnsures
Ensures that messages have not been altered or destroyed in an
unauthorized manner and that data sequences have not been altered to an extent greater
than can occur non
non-maliciously.
maliciously.
Message origin authenticationEnsures
authentication Ensures that the claimed identity of the user on
whose behalf received data was originated is confirmed.
Message confidentialityEnsures
confidentiality Ensures that information is not made available or disclosed
to unauthorized individuals, entities, or proces
processes.
ses.
SNMPv3 authorizes management operations only by configured users and encrypts
SNMP messages.
Fiji uses two authentication protocols for SNMPv3:
HMAC-MD5
MD5-96
96 authentication protocol
HMAC-SHA
SHA-96
96 authentication protocol
Fiji uses Advanced Encryption

Encryption Standard (AES) as one of the privacy protocols for
SNMPv3 message encryption and conforms with RFC 3826.
The priv option offers a choice of DES or 128
128-bit
bit AES encryption for SNMP security
encryption. The priv option along with the aes-128
128 token indicates
indicates that this privacy
password is for generating a 128-bit
128 bit AES key.The AES priv password can have a
minimum of eight characters. If the passphrases are specified in clear text, you can
specify a maximum of 64 characters. If you use the localized key, you can
can specify a
maximum of 130 characters.
9.11.2 SNMP Server Operational Mode Commands
9.11.2.1
show snmp
Display all SNMP configuration options, except for what is displayed by the other "show
snmp ..." commands described below.
9.11.2.2
show snmp engineID

Display the SNMP engine ID
ID of this system (this should be the value of the MAC address
of the management interface).
9.11.2.3
show snmp sessions

Display SNMP sessions.
9.11.2.4
show snmp user

Display SNMP v3 user authentication options. This includes which users are enabled,
and what hash and privacy
privacy types were selected for each. Neither the passwords nor
their hashes are displayed (though the hashes can be seen with "show configuration").
Rev 1.2
2, Page 121 of 146
9.11.3 SNMP Server Configure Mode Commands

9.11.3.1
snmp
snmp-server
server enabled | disabled
Enable or disable the SNMP server. Note that this not only stops serving of SNMP
variables, but also the sending of SNMP traps.
9.11.3.2
[no] snmp
snmp-server
server disable traps
Enable or disable sending of SNMP traps from this system. Traps may only be enabled if
the SNMP server overall is enabled.
Note that tra
traps
ps are only sent if there are trap sinks configured with the "snmp-server
"snmp server host
..." command, and if these trap sinks are themselves enabled.
9.11.3.3
snmp
snmp-server
server v1 enabled | disabled
Enable or disable SNMP v1 authentication on this system. If disabled, the community
community
configured will be ignored. Note that this has the same effect as removing the community
entirely.
9.11.3.4
snmp
snmp-server
server v2c enabled | disabled
Enable or disable SNMP v2c authentication on this system. If disabled, the community
configured will be ignored. Note that this has the same effect as removing the community
entirely.
9.11.3.5
snmp
snmp-server
server v3 enabled | disabled
Enable or disable SNMP v3 authentication on this system. If disabled, the users
configured will be ignored. Note that this has the same effect as removing
removing the users
entirely.
9.11.3.6
snmp
snmp-server
server port <TCP port>
9.11.3.7
no snmp
snmp-server
server port
This command will configure UDP port number for SNMP server. The default is port 161
which is set when the no option is selected.
9.11.3.8
snmp
snmp-server
server community <community name> security-name
security ame [read-only
[read only |
read-write]
read
9.11.3.9
no snmp
snmp-server
server community
Set a community name for either read
read-only
only or read/write SNMP requests. If neither "ro"
or "rw" is specified, the read-only
read only community is set (the same as if "ro" had been
specified). There are two community
community strings that can be set: if the readread-only
only community
is specified, only queries can be performed; if the read/write community is specified, both
queries and sets can be performed.
The "no ..." command resets the ro community to its default name public
publi and rw
community to the default name private.
9.11.3.10
snmp
snmp-server
server host <IP address> traps version 1 <community string> [udp[udp
port <number>]
Configures a host receiver for SNMPv1 traps. The community can be any alphanumeric
string up to 255 characters. The UDP port number range is from 0 to 65535.
Rev 1.2
2, Page 122 of 146
9.11.3.11
snmp
snmp-server
server host <IP address> {traps | informs} version 2c <community
string> [udp
[udp-port
port <number>]
Configures a host receiver for SNMPv2c traps or informs. The community can be any
alphanumeric string up to 255 characte
characters.
rs. The UDP port number range is from 0 to
65535.
9.11.3.12
snmp
snmp-server
server host <IP address> {traps | informs} version 3 {auth | noauth |
priv} <username> [udp-port
[udp port <number>]
9.11.3.13
no snmp
snmp-server
server host <IP address>
Configures a host receiver for SNMPv2c traps or informs. The username can be any
alphanumeric string up to 255 characters. The UDP port number range is from 0 to
65535.
9.11.3.14
[no] snmp
snmp-server
server host <IP address> enable
Disable a trap sink without actually removing it altogether from the configuration. All trap
sinks are cr
created
eated enabled.
9.11.3.15
snmp
snmp-server
server user <username> v3 auth {md5 | sha} <plaintext auth
password> [priv {des | aes-128}
aes 128} [<plaintext privacy password>]]
9.11.3.16
snmp
snmp-server
server user <username> v3 encrypted auth {md5 | sha} <hashed auth
password> [priv {des | aes-128}
aes 128} [<hashed p
privacy
rivacy password>]]
9.11.3.17
snmp
snmp-server
server user <username> v3 prompt auth {md5 | sha} [priv {des | aesaes
128}]
Set security parameters on a per
per-user
user basis for SNMP v3 access. Currently the only user
permitted here is "admin". The hash algorithm specified is used both to
to create digests of
the authentication and privacy passwords for storage in configuration, and also in HMAC
form for the authentication protocol itself.
If the command ends after the auth password, the privacy algorithm is set to its default,
which is AES
AES-128,
128, and the privacy password is set to the same as whatever was
specified for the authentication password. You may also specify the privacy algorithm
while still not specifying a separate password.
There are three variants of the command, which branch out
out after the "v3" keyword. If
"auth" is the next word, the passwords are specified in plaintext on the command line. If
"encrypted" is the next word, the passwords are specified encrypted (hashed) on the
command line. If "prompt-pass"
"prompt pass" is the next word, tthe
he passwords are not specified on the
command line: the user is prompted for them while the command is executing. If "priv" is
not specified, only the auth password is prompted for. If "priv" is specified, the privacy
password is prompted for; entering a
an
n empty string for this prompt will result in using the
same password as specified for authentication.
9.11.3.18
[no] snmp
snmp-server
server user <username> v3 enable
Enable or disable access via SNMP v3 for the specified user. As above, only the "admin"
account can be used here
here at the present time.
Rev 1.2
2, Page 123 of 146
9.12 SECTOR MANAGEMENT CLI COMMANDS

9.12.1 Sector Management Operational Mode Commands
The following set of show commands will retrieve the actual values directly from the Sectors (WMD
board) and display the actual values used. These can the
then
n be compared with the configuration database
values via the show running sector command.
9.12.1.1
show sector general [<1-65535>]

[<1 65535>]
Display the sector information for all sectors or the user specified one. Note that each
Sector will have a status variable which is provided by the WMD Manager to identify the
state that the Sector it is managing is in.
# show sector general 1
Sector #1 General State Information
Sector Status:
<Up | Initialization | ResetReset-Required
Required | Down >
Base Station ID:
00:11:22:33:44:55
IP Address:
192.168.2.101
MAC Address:
12:23:41:66:71:33
AAA / Radius Server:
192.168.2.225
Network Mode:
Standalone with Local Provisioning
# Resets:
5
Last Reset Reason:
<GPS Synchronization Recovery Failure | User
Initiated | System Startup
Start >
WiMax Information
MAC Protocol Version:
1
DL:UL Frame Ratio:
35:12
Channel BW:
10 MHz
UCD Interval:
1000 msec
DCD Interval:
1000 msec
BS TX Power:
5000
Max Initial Ranging TX Power:
10000
TX Antenna Mode:
MIMO
MIMO-A
RX Antenna Mode:
MRC
MRC-2
Auto Power Control Mode:
Closed loop
Open Loop Power Control Mode:
Active
Noise & Interference:
30
Feature Information
Auto TX Start Support:
enabled
Default Provisioning Support:
enabled
Security Support:
enabled
AK Lifetime:
1
TEK Lifetime:
1
9.12.1.2
show sector [<1

[<1--65535>]
65535>] radio
Display the sector radio information for all sectors or the user specified one.
# show sector 1 radio
Sector #1 Radio State Information
Center Frequency:
0x11223344
Antenna Gain:
0x33335577
Cable Los
Loss:
0x11118888
Power Output:
1000
9.12.1.3
show sector general [<1-65535>]

[<1 65535>] status
Sector <ID> Status Information:
Rev 1.2
2, Page 124 of 146
Status:
Restart count:
Current Frame Number:
Number of MSS:
Number of Service Flow:
Software Version:
Up
1
55
17
45
1.0.10.3145
9.12.1.4
show sector statistics [<1-65535>]

[<1 65535>] <counters | throughput-metrics
throughput metrics | startupstartup
metrics | packet
packet-error--rate-metrics
metrics | service
service--flow-metrics>
metrics>
9.12.1.5

[<1 65535>] counters
Sector <ID> Statistics Counters:
Statistics Reset Count:
DL Packet Sent:
Ranging
ging Attempt Count:
Ranging Success Count:
Authentication Attempt Count:
Authentication Success Count:
9.12.1.6
0
2330
5
3
10
8

[<1 65535>] throughput
throughput-metrics
metrics
Sector <ID> Statistics Throughput Metrics:
Avg DL User Throughput:
10 Mbps
Peak DL User Throughput:
15 Mbps
Avg UL User Throughput:
5 Mbps
Peak UL User Throughput:
7 Mbps
Avg DL MAC Throughput:
8 Mbps
Peak DL MAC Throughput:
10 Mbps
Avg UL MAC Throughput:
4 Mbps
Peak UL MAC Throughput:
4.5 Mbps
9.12.1.7

[<1 65535>] startup
startup-metrics
metrics
Sector <ID> Statistics Startup Metrics:
Authentication Attempt: 15
Authentication Success:
10
Authentication Success Rate: 66%
Ranging Attempt:
33
Ranging Success:
27
Ranging Success Rate:
75%
9.12.1.8

[<1 65535>] packet
packet-error-rate
ate-metrics
Sector <ID> Statistics Packet Error Rate Metrics:
DL Packet Sent:
245666
DL Packet Error:
1123
DL Packet Error Rate:
0.5
UL Packet Received: 332511
UL Packet Error:
3100
UL Packet Error Rate:
0.95
Rev 1.2
2, Page 125 of 146
9.12.1.9
show sector statistics

statistic [<1-65535>]
65535>] service
service-flow-metrics
metrics
Sector <ID> Statistics Service Flow Metrics:
DSA-REQ
REQ Count:
120
DSA-REQ
REQ Success:
105
DSC-REQ
REQ Count:
211
DSC-REQ
REQ Success:
204
DSD-REQ
REQ Count:
319
DSD-REQ
REQ Success:
285
Max Active Service Flow:
451
Max DL Service Flow:
321
Max UL Service Flow:
130
9.12.1.10
show sector statistics-mss

statistics mss [<1
[<1-65535>]
65535>] <registered-ss
<registered
| rssi--cinr-metrics>
metrics>
9.12.1.11

statistics mss [<1
[<1-65535>]
65535>] registered-ss
registered
Sector <ID> Statistics MSS Registered SS:
MAC Address | Basic CID
| Primary CID | Vendor ID Encoding
Encod
| MAC Version
------------------------------------------------------------------------------------------------------------------00:11:22:33:44:55
1234
66
112233
1.5
9.12.1.12

statistics mss [<1
[<1-65535>]
65535>] rssi-cinr-metrics
rssi
metrics
Sector <ID> Statistics MSS RSSI / CINR Metrics:
MAC Address | Direction
| CINR Mean/Deviation | RSSI Mean/Deviation
------------------------------------------------------------------------------------------------------------------00:11:22:33:44:55
UL
66/12
128/33
9.12.2 Sector Management Configure Mode Commands

The following set of Sector configuration items will also have a state object equivalent that is displayed
in the show commands to reflect the actual values used by the Sector.
9.12.2.1
sector general <1-65535>

<1 65535> system <enable
<enabled
d | disabled>
This command is used to enable or disable a particular Sector (Default: Enabled).
Disabling will be done by holding the Sector in reset until the user re-enables
re enables the Sector.
9.12.2.2

<1 65535> system bs
bs-id
id <MAC address format>
This com
command
mand is used to configure a base station ID for the specified sector that requires
6 bytes in a MAC address format.
9.12.2.3

<1 65535> system ip address <IP address>
This command is used to configure the external IP address for the specified sector.
9.12.2.4

<1 65535> system ip netmask <netmask>
This command is used to configure the external IP network mask for the specified sector.
9.12.2.5

<1 65535> system ip gateway <IP address>
This command is used to configure the external next
next-hop gateway for the specified
sector.
Rev 1.2
2, Page 126 of 146
9.12.2.6

<1 65535> system ip dhcp <enabled | disabled>
This command is used to enable or disable DHCP on the sector (Default: Disabled).
9.12.2.7

<1 65535> system max
max--supported--cpe
cpe <uint32>
This command is used to configure the maximum number of registered CPEs supported.
9.12.2.8
sector advanced <1-65535>

<1 65535> wimax antenna
antenna-tx-mode
mode < MIMOMIMO-A | MIMO-B
B|
MIMO-AB>
MIMO
This command is used to configure the TX antenna mode setting.
9.12.2.9

<1 65535> wimax auto
auto-power-cont
control
rol <closed-loop
<closed loop | openopen
loop>
This command is used to configure the setting.
9.12.2.10

<1 65535> wimax auto
auto-tx-start-enabled
enabled <true | false>
This command is used to enable or disable the auto transmit after reset setting.
9.12.2.11

<1 65535> w
wimax
imax channel-bw
channel bw <5MHz | 10MHz>
This command is used to configure the channel bandwidth selection in MHz.
9.12.2.12

<1 65535> wimax dl
dl-ul
ul-frame-ratio
ratio <35:12 | 32:15 | 29:18 |
26:21>
This command is used to configure the Downlink/Uplink frame ratio setting.
setting.
9.12.2.13

<1 65535> wimax default
default-provisioning
provisioning-enabled
enabled <true|
false>
This command is used to enable or disable the default provisioning setting.
9.12.2.14

<1 65535> wimax dcd
dcd-interval
interval <15-10000>
<15
This command is used to configure the D
DCD
CD interval in milliseconds.
9.12.2.15

<1 65535> wimax ucd
ucd-interval
interval <15-10000>
<15
This command is used to configure the UCD interval in milliseconds.
9.12.2.16

<1 65535> radio antenna
antenna-gain
gain <uint32>
This command is used to configure the radio ant
antenna
enna gain.
9.12.2.17

<1 65535> radio cable
cable-loss
loss <uint32>
This command is used to configure the radio cable loss.
9.12.2.18

<1 65535> radio center
center-freq
freq <uint32>
This command is used to configure the radio center frequency.
9.12.2.19

<1 65535> radio power
power-output
output <int32>
This command is used to configure the radio power output.
Rev 1.2
2, Page 127 of 146
9.12.2.20

<1 65535> security <enabled | disabled>
This command is used to enable or disable the security feature.
9.12.2.21

<1 65535> security ak
ak-lifetime
time <300 - 6048000>
This command is used to configure the AK lifetime security setting.
9.12.2.22

<1 65535> security tek
tek-lifetime
lifetime <180 - 604800>
This command is used to configure the TEK lifetime security setting.
9.12.2.23
sector action <1

<1--65535>
65535> reboot
ACTION:
TION: This command is used to reset the statistics counters to zero.
9.12.2.24
sector action <1

<1--65535>
65535> statistics reset
reset-counters
ACTION: This command is used to reset the statistics counters to zero.
9.12.2.25
sector action <1

<1--65535>
65535> subscriber
subscriber-station
station <MAC address> abort
ACTION:
ION: This command is used to abort the subscriber station identified by its MAC
address.
9.12.2.26
sector action <1

<1--65535>
65535> subscriber
subscriber-station
station <MAC address> deregister
ACTION: This command is used to de
de-register
register the subscriber station identified by its
MAC address.
9.12.2.27
sector
ector action <1
<1--65535>
65535> subscriber
subscriber-station
station <MAC address> reset
ACTION: This command is used to reset the subscriber station identified by its MAC
address.
9.13 PROVISIONING CLI COMMANDS

9.13.1 Provisioning Operational Mode Commands
9.13.1.1
show running
running-config
config cpe [<MAC address>]
Display CPE provision table entries.
Rev 1.2
2, Page 128 of 146
9.13.1.2
show service
service-profile
profile [ arq-profile
arq profile | client
client-profile
profile | cls-profile
cls profile | harq-profile
harq profile |
mcast-profile
mcast
profile | qos
qos-profile
profile ] [<index>]
Display all provisioning profiles: ARQ, Classifier, Client, HARQ, Client, Multicast
Multicast and
QoS. This will retrieve all the service
service-profile
profile profiles configuration values on the WMD
board.
9.13.2 Provisioning Configure Mode Commands

9.13.2.1
cpe <MAC address> cs-type

cs type <ETHERNET_CS | IPv4_CS> customer-id
customer
<string> ipip-address
address <IP address> mcast
mcast-profile
profile <1-50>
< 50> client-profile
client profile <1-8>
<1 8> maxmax
downlink rate <MCS rates> max-uplink
downlink-rate
max uplink-rate
rate <MCS rates>
9.13.2.2
no cpe <MAC address>

This command is used to create or modify a CPE entry in the CPE provisioning table.
The no option is used to delete the CPE entry.
mcast
mcast-profile
client--profile
cs-type
type
customer
customer-id
ip-address
address
9.13.2.3
Client
Client Multicast Profile 1
1-50
50 (selects existing Mcast profile)
Client Profile 1-8
1 8 (selects existing Client profile)
Convergence Sublayer Type, one of {ETHERNET_CS, IPv4_CS}
Customer Reference ID, any string up to 31 chars
CPE IP Address (only valid for csType=IPV4_CS)
service
service-profile
profile arq-profile
arq profile <index> <ARGS >
This command is used to configure ARQ profiles. The following are the set of parameters
used for the profile configurations.
ack-processing
processing-time
time ARQ Acknow
Acknowledge
ledge Processing Time in msec, 0-255
0
block--lifetime
ARQ Block Lifetime Timeout, units of 5msec, 0 - 1310
block--size
ARQ Block Size, one of {16, 32, 64, 128, 256, 512 or 1024}
deliver
deliver-in-order
ARQ Deliver in Order, true/false
description
Profile Descript
Description,
ion, up to 31 chars, optional
enabled
ARQ Enabled, true/false
name
Profile Name, up to 15 chars, optional
purge--timeout
ARQ Purge Timeout, units of 5msec, 0 - 1310
sync-loss
loss
ARQ Sync Loss Timeout, units of 5msec, 0 - 1310
timeout
timeout-rx-delay
ARQ Receiv
Receive
e Retry Timeout Delay, units of 5msec, 0 - 1310
timeout
timeout-tx-delay
ARQ Transmit Retry Timeout Delay, units of 5msec, 0 - 1310
window
window-size
ARQ Window Size, 0 - 1024
9.13.2.4
service
service-profile
profile client-profile
client profile <index> <ARGS >
This command is used to configure Client prof
profiles.
iles. The following are the set of
parameters used for the profile configurations.
description
Profile Description, up to 31 chars, optional
max-dl
dl-rate
Maximum downlink rate reserved for this client (bits per sec), 0 4294967295
max-pps
pps
Maximum Packets per sec, 1 - 65535
max-traffic
traffic-burst
Maximum Client Traffic Burst, 0 - 4294967295
max-ul
ul-rate
Maximum uplink rate for this client (bits per sec), 0 - 4294967295
mcast
mcast-profile-num
num
Mcast Profile Number used by this Client profile, 1-50
1
min-dl
dl-reserved-rate
rate Minimum downlink rate reserved for this client (bits per sec), 0 4294967295
min-ul
ul-reserved-rate
rate Minimum uplink rate reserved for this client (bits per sec), 0 4294967295
name
Rev 1.2
2, Page 129 of 146
num-sflow
sflow
Number of Service Flows For this Client Profile, 1 - 16
priority
Traffic Priority for this client, 1 - 8
sflow--profile
profile <index> Configure a client Service Flow Profile
name
Name, up to 31 chars, optional
description
Description, up to 31 chars, optional
direction
Direction opti
option:
on: downlink or uplink
arq-profile--num
ARQ profile reference index number
cls-profile--num
harq-profile
profile-num
qos-profile
profile-num
9.13.2.5
service
service-profile
profile cls-profile
cls
<index> <ARGS >
This command is used to configure Classifier profiles. The following are the set of
description
dest-port
port-high
Classifier Destination Port High Limit, 0 - 65535
dest-port
port-low
Classifier Destination Port Low Limit, 0 - 65535
dest-ip
ip-addr-prfx
Classifier IP Destination Address and Prefix (mask length);
examples: 192.0.0.0/2, 192.168.0.0/13, 192.168.254.0/23, 192.168.1.1/32
dest-ip
ip-addr-used
Classifier
ifier IP Destination Address Rule is used, true/false
dest-ip
ip-port-used
Classifier Destination port Rule is used, true/false
eth-type
type
Classifier Ethernet Type, 1501 - 65535
eth-type
type-used Classifier EtherType Rule is used, true/false
ip-protocol
protocol
Classifier
fier IP Protocol Type, 0 - 255
ip-protocol
protocol-used
Classifier IP Protocol Rule is used, true/false
ip-tos--high
Classifier IP TOS High Limit, 0 - 7
ip-tos--low
Classifier IP TOS low limit, 0 - 7
ip-tos--used
Classifier IP TOS Rule is used, true/false
name
Profile
rofile Name, up to 15 chars, optional
priority
Classifier Priority, 0 - 255
priority
priority-used
Classifier Priority Rule is used, true/false
src-ip--addr-prfx
Classifier IP Source Address and Prefix (mask length);
examples: 192.0.0.0/2, 192.168.0.0/13, 192.168
192.168.254.0/23,
.254.0/23, 192.168.1.1/32
src-ip--addr-used
Classifier IP Source Address Rule is used, true/false
src-ip--port-used
Classifier Source port Rule is used, true/false
src-port
port-high
Classifier Source Port High Limit, 0 - 65535
src-port
port-low
Classifier Source Po
Port
rt Low Limit, 0 - 65535
type
Classifier Type, one of {none, ipDest, tos, vlan, macDest}
vlan-id
id
Classifier VLAN ID Tag, 0 - 4095
vlan-id
id-used
Classifier VLAN ID Rule is used, true/false
9.13.2.6
service
service-profile
profile harq-profile
harq profile <index> <ARGS >
This command is u
used
sed to configure HARQ profiles. The following are the set of
channel
channel-mapping
HARQ Map Length, 0 - 16
description
enable
HARQ Enable, true/false
name
num-retries
retries
HARQ Number of Retries, 0 - 16
pdu-sn
sn-support
HARQ PDU SN Support, one of {none, short, long}
Rev 1.2
2, Page 130 of 146
9.13.2.7
service
service-profile
profile mcast-profile
mcast profile <index> <ARGS >
This command is used to configure Multicast profiles. The following are the set of
description
ethernet
ethernet-addr
Multicast MAC Address, only valid if multicast type is
Ethernet Multicast; example: 11:22:33:44:55:66
11:22:33:44:55:6
ip-address
address
Multicast IP Address, only valid if multicast type is IP
Multicast; example: 192.168.1.1
name
type
Multicast type, one of {IP_MULTICAST,
ETHERNET_MULTICAST}
9.13.2.8
service
service-profile
profile qos-profile
qo profile <index> <ARGS >
This command is used to configure QoS profiles. The following are the set of parameters
used for the profile configurations.
data-delivery
delivery-service
service Data Delivery Service Type, one of {UGS_Service,
RTP_Service,
nRTP_Service, BE_Service, eRTP_Service}
description
max-latency
latency
Maximum Latency (milliseconds), 0 - 65535
max-sustained
sustained-traffic
traffic-rate
Maximum Sustained Traffic Rate (bits per second), 0 42949672
4294967295
max-traffic
traffic-burst
Maximum Traffic Burst Size, 0 - 4294967295
min-reserved
reserved-traffic
traffic-rate
Minimum Reserved Traffic Rate (bits per sec), 0 4294967295
name
request
request-transmission
transmission-policy Request Transmission Policy, 0-7F
0 7F hexadecimal
comprised of following bit masks:
1 - SF Shall not use Broadcast BW Request Opportunities (UL only)
2 - SF Shall not use Multicast BW Request Opportunities (UL only)
4 - SF Shall not Piggyback Requests with Data (UL only)
8 - SF Shall not Fragment Data
0x10 - SF Shall not Supress Payload headers (CS Parameter)
0x20 - SF Shall not Pack Data; 0x40 - SF Shall not include CRC
sdu-inter
inter-arrival-interval
interval
SDU Inter-Arrival
Arrival Interval, 0 - 65535
sdu-size
size
Service Data Unit Size (bytes), 0 - 255
tolerated
erated-jitter
Tolerated Jitter (milliseconds), 0 - 65535
traffic--priority
Traffic Priority Level, 1 - 8
ul-grant
grant-schedule--typeUplink Grant Schedule Type, one of {BS_Defined_UL_Sched,
BE_UL_Sched, nRTP_UL_Sched, RTP_UL_Sched,
RTP_UL_Sched,
eRTP_UL_Sched,
UGS_UL_Sched}
unsolicited
unsolicited-grant-interval
interval
Unsolicted Grant Interval, 0 - 65535
unsolicited
unsolicited-poll-interval
interval
Unsolicted Poll Interval, 0 - 65535
Rev 1.2
2, Page 131 of 146
9.14 STATISTICS CLI COMMANDS

9.14.1 Statistics Operational Mode Comma
Commands
9.14.1.1
show stats cpu

Display some basic statistics about CPU utilization: current level, peak over the last hour
and average for the last hour.
9.14.1.2
show stats memory

Display some basic statistics about memory utilization: current level, peak over the last
hour and
nd average for the last hour.
9.14.2 Statistics Configure Mode Commands

9.14.2.1
stats clear
clear-all
This command will clear all historical statistics that have been collected up to this time.
9.14.2.2
stats export <format> <report name> [filename <filename>]

This will export the statistics
statistics for the specified report name to a file. The only supported
format is CSV which is comma separated value. The optional filename is used to export
the statistics to that name.
Rev 1.2
2, Page 132 of 146
Appendix A
Quantum 1000
10
Base Station
Data Sheet
Rev 1.2
2, Page 133 of 146
Rev 1.2
2, Page 134 of 146
Appendix B
4 (Quad) Antenna Panel
Data Sheet
Rev 1.2
2, Page 135 of 146
Rev 1.2
2, Page 136 of 146
Rev 1.2
2, Page 137 of 146
Appendix C
Cable Terminations
Rev 1.2
2, Page 138 of 146
EZ
EZ-400-NMH
NMH Connector Installation Procedure on
Times Microwave Cable LMR
LMR-400
This installation procedu
procedure
re has been re-produced
re produced in its entirety from the Times Microwave website.
1.
Flush cut the cable squarely.
2.
Slide the heat shrink boot and crimp ring onto the cable. Strip the cable end using the ST-400
ST 400-EZ
prep/strip tool by inserting the cable into
into End 1 and rotating the tool. Remove any residual plastic
from the center conductor.
3.
Insert the cable into End 2 of the ST-400

ST 400-EZ
EZ prep/strip tool and rotate the tool to remove the
plastic jacket.
Rev 1.2
2, Page 139 of 146
4.
Debur the center conductor using the DB

DBT-01
01 deburring tool.
5.
Flare the braid slightly and push the connector body onto the cable until the connector snaps into
place, then slide the crimp ring forward creasing the braid.
6.
Temporarily slide the crimp ring back, and remove the con
connector
nector body from the cable to trim the
excess braid at the crease line, then remount the connector and slide the crimp ring forward until
it butts up against the connector body
Rev 1.2
2, Page 140 of 146
7.
Position either the heavy duty HX-4

HX 4 crimp tool with the appropriate dies (.429 hex) or the CTCT
400/300 crimp tool directly behind and adjacent to the connector body, and crimp the connector.
The HX-4
HX 4 crimp tool automatically releases when the crimp is complete.
8.
Position the heat shrink boot as far forward on the cconnector

onnector body as possible, without interfering
with the coupling nut and use a heat gun to form a weather tight seal.
Rev 1.2
2, Page 141 of 146
Ethernet Cat 5 Cable
Identifying the RJ-45

RJ 45 Cable Type
To identify the RJ-45
RJ 45 cable type, hold the two ends of the cable next to each other so you can see the
colored wires inside the ends, as shown. In a straight
straight-through
through cable, the colored wires are in the same
sequence at both ends of the cable.
When making a straight

straight-through
through cable using Cat 5E, it is mandatory tha
thatt you follow the 568-B
568 B standard
shown below. Otherwise, you risk the possibility of damaging the equipment.
equipment
Rev 1.2
2, Page 142 of 146
Termination of the Cat 5E Shielded Cable
lease Note: It is recommended to use shielded Cat 5e cables and make certain that the drain wire
Please
hass a good contact with the metal RJ-45
RJ 45 connector.
Rev 1.2
2, Page 143 of 146
APPENDIX D
CAPACITY TABLES
Rev 1.2
2, Page 144 of 146
Per Sector Throughput Tables by Channel Size and DL/UL Frame Ratio
We present here a set of tables specifying the raw (MAC
(MAC-layer)
layer) throughput of a PureWave Quantum
Family base station for 5 and 10MHz, under ideal conditions, corresponding to the maximum achievable
performance that can be achieved using IEEE 802.16e per channel bandwidth and TDD configuration
ratio.
All results assume PUSC, a MAP size of 4 symbols, and 1 pr
preamble
eamble symbol. The numbers represent the
maximum MAC layer performance using all sub-channels
sub channels and exclude Ethernet Layer 2 or higher layer
overheads.
Note that these results are specific to the stated configuration under ideal conditions and should be
considered
nsidered indicative of expected results. Actual results will vary depending upon the actual
configuration, error rate, environment, and numerous other factors.
MCS Rate
64QAM-5/6
5/6
64QAM-3/4
3/4
64QAM-2/3
2/3
64QAM-1/2
1/2
16QAM-3/4
3/4
16QAM-1/2
1/2
QPSK-3/4
3/4
QPSK-1/2
1/2
Downlink
21.60
19.44
17.28
12.96
12.96
8.64
6.48
4.32
10 MHz
Uplink
5.04
4.54
4.03
3.02
3.02
2.02
1.51
1.01
Bi-Di
25.44
22.90
20.35
15.26
15.26
10.18
7.63
5.09
Downlink
10.80
9.72
8.64
6.48
6.48
4.32
3.24
2.16
5 MHz
Uplink
2.45
2.20
1.96
1.47
1.47
0.98
0.73
0.49
Bi-Di
12.72
11.45
10.18
7.63
7.63
5.09
3.82
2.54
Table 3:: Max Throughput - 35:12 - 74%:26%
MCS Rate
64QAM-5/6
5/6
64QAM-3/4
3/4
64QAM-2/3
2/3
64QAM-1/2
1/2
16QAM-3/4
3/4
16QAM-1/2
1/2
QPSK-3/4
3/4
QPSK-1/2
1/2
Downlink
18.72
16.85
85
14.98
11.23
11.23
7.49
5.62
3.74
10 MHz
Uplink
6.72
6.05
5.38
4.03
4.03
2.69
2.02
1.34
Bi-Di
25.44
22.90
20.35
15.26
15.26
10.18
7.63
5.09
Downlink
9.36
8.42
7.49
5.62
5.62
3.74
2.81
1.87
5 MHz
Uplink
3.26
2.94
2.61
1.96
1.96
1.31
0.98
0.65
Bi-Di
12.62
11.36
10.10
7.57
7.57
5.05
3.79
2.52
Table 4:: Max Throughput - 32:15 68%:32%
MCS Rate
64QAM-5/6
5/6
64QAM-3/4
3/4
64QAM-2/3
2/3
64QAM-1/2
1/2
Downlink
17.28
15.55
13.82
10.37
10 MHz
Uplink
8.40
7.56
6.72
5.04
Bi-Di
25.68
23.11
20.54
15.41
Downlink
8.64
7.78
6.91
5.18
5 MHz
Uplink
4.08
3.67
3.26
2.45
Bi-Di
12.72
11.45
10.18
7.63
Rev 1.2
2, Page 145 of 146
16QAM-3/4
3/4
16QAM-1/2
1/2
QPSK-3/4
3/4
QPSK-1/2
1/2
10.37
6.91
5.18
3.46
5.04
3.36
2.52
1.68
15.41
10.27
7.70
5.14
2.45
1.63
1.22
0.82
7.63
5.09
3.82
2.54
5 MHz
Uplink
4.90
4.41
3.92
2.94
2.94
1.96
1.47
0.98
Bi-Di
12.10
10.89
9.68
7.26
7.26
4.84
3.63
2.42
5.18
3.46
2.59
1.73
Table 5:: Max Throughput 29:18 - 62%:38%
MCS Rate
64QAM-5/6
5/6
64QAM-3/4
3/4
64QAM-2/3
2/3
64QAM-1/2
1/2
16QAM-3/4
3/4
16QAM-1/2
1/2
QPSK-3/4
3/4
QPSK-1/2
1/2
Downlink
14.40
12.96
11.52
8.64
8.64
5.76
4.32
2.88
10 MHz
Uplink
10.08
9.07
8.06
6.05
6.05
4.03
3.02
2.02
Bi-Di
24.48
22.03
19.58
14.69
14.69
9.79
7.34
4.90
Downlink
7.20
6.48
5.76
4.32
4.32
2.88
2.16
1.44
Table 6:: Max Throughput 26:21 - 55%:45%
Rev 1.2
2, Page 146 of 146

Quantum

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Quantum

Caricato da

Copyright:

Formati disponibili

Quantum 1000 Base Station

Quantum 1000 Base Station User Guide

Quantum 1000 Base Station User Guide

This device must be professionally installed

Quantum 1000 Base Station User Guide

Quantum 1000 Base Station User Guide

Quantum 1000 Base Station User Guide

Obtaining Warranty Service

Table 1 Summary of PureWave RMA Conditions and Charges

Quantum 1000 Base Station User Guide

Out of Box Failure (OBF) / Dead on Arrival (DOA)

Quantum 1000 Base Station User Guide

NEVER install in a wet location unless

ALWAYS use caution when installing or modifying cables.

Quantum 1000 Base Station User Guide

Obtaining Warranty Service................................

Out of Box Failure (OBF) / Dead on Arrival (DOA) ......................................................

Out of Warranty ................................................................

3. Grounding and Lightning Requirements .............................................................

4. Weather Protection ................................

Weather Sealing ................................................................

Quantum 1000 Base Station User Guide

6. CPE Provisioning ................................

Quality of Service (QoS) Profile................................

Quantum 1000 Base Station User Guide

PureWave Networks develops carrier-class

PureWave Quantum 1000 Base Station (BS)

Subscriber customer premises equipment (CPE)

Quad Antenna panel

Element management system (EMS).

AAS processing (beam forming and null steering)

AMC like subchannel assignments

Fast transmit/receive compensation necessary for channel reciprocity for mobility,

High capacity deployments using

Reduced or no cell planning,

Fewer base stations are needed to cover a region, and

Improved user performance.

Quantum 1000 Base Station User Guide

Figure 1 - Architecture Reference Model.

Quantum 1000 Base Station User Guide

Base Station Sector

Figure 2 - General View of System Components

This document is intended to be used by wireless broadband installation engineers. It contains

Quantum 1000 Base Station User Guide

5 and 10 MHz profile

Adding more Base Station

MAC Software Architecture

Quantum 1000 Base Station User Guide

Figure 3 Quantum 1000 Base Station

Figure 3 - Tower Mounted Quantum 1000 Base Station

Quantum 1000 Base Station User Guide

Figure 5 - Tower Mounted Quantum 1000 Base Station

Quantum 1000 Base Station User Guide

Physical & Environmental

24.6 (H) x 17.4 (W) x 4.5 (D)

-33 to +55 degrees C

10kA IEC 6100-4-5

Table 2 Base Station Physical and Environmental Properties

Quantum 1000 Base Station User Guide

Figure 8 - Base Station Connect

ANT 1: This is a transmit (Tx) and a receive (Rx) port.

Quantum 1000 Base Station User Guide

Figure 9 - Base Station Antenna Connections

Figure 10 Base Station to Antenna Physical Connection