PMP 320 Release Notes E2.3 Issue1 PDF

PMP 320 Administration and Configuration Guide
Cambium
PMP 320

Release Notes

System Release
e2.3
PMP320RELEASENOTES May 2012
2012 Cambium Networks. All Rights Reserved.

PMP 320 Module Essential Information
The following tables may be referenced for information regarding module management access and
factory default procedures.
AP
Default IP Address for
Management GUI Access
192.168.2.101
Default Administrator
Username
admin
Password
admin
Resetting to Factory
Defaults (2 options)
1. Restore Configuration Control Index 1 located in the AP GUI
at Administration > Configuration Control then reboot the
radio.
2. While powered, insert a default plug into the radios RJ11 port
for one minute, then remove. When the radio is rebooted, it
is configured with the factory defaults.
CSM
Default IP Address for
Management GUI Access
10.1.1.254
Username
administrator
Password
cambium

Previous to CSM software version f12b00-v8.1.4, the
CSMs default administrator password was motorola. If a
factory default procedure is initiated for a CSM with
software version >= f12b00-v8.1.4 which is still
configured with the default password of motorola, the
default administrator password will be changed to
cambium.
Resetting to Factory
Defaults (2 options)
1. Restore the factory default settings by using the CSM GUI
restore function located at Management > Restore Default,
then reboot the radio.
2. Use the Reset factory default tool, which may be downloaded
from the Cambium support website.

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any
inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium Networks reserves the right to make
changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make
changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium Networks does not
assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license
under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium
Networks products (machines and programs), programming, or services that are not announced in your country. Such references or
information must not be construed to mean that Cambium Networks intends to announce such Cambium Networks products, programming, or
services in your country.

Copyrights
This document, Cambium Networks products, and 3
rd
Party Software products described in this document may include or describe copyrighted
Cambium Networks and other 3
rd
Party supplied computer programs stored in semiconductor memories or other media. Laws in the United
States and other countries preserve for Cambium Networks, its licensors, and other 3
rd
Party supplied software certain exclusive rights for
copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted
material. Accordingly, any copyrighted material of Cambium Networks, its licensors, or the 3
rd
Party software supplied material contained in the
Cambium Networks products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified
in any manner without the express written permission of Cambium Networks. Furthermore, the purchase of Cambium Networks products shall
not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications
of Cambium Networks or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by
operation of law in the sale of a product.

Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or
documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer
language, in any form or by any means, without prior written permission of Cambium Networks

License Agreements
The software described in this document is the property of Cambium Networks and its licensors. It is furnished by express license agreement
only and may be used only in accordance with the terms of such an agreement.

High Risk Materials
Components, units, or 3
rd
Party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or
intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear
Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities).
Cambium Networks and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.

2012 Cambium Networks Limited. All Rights Reserved.
PMP 320 Release e2.3 Release Notes

Issue 2, May 2012 Page 5
Table of Contents

Introduction ..................................................................................................................... 6
Applicability ................................................................................................................. 6
New Access Point Hardware Notifications .................................................................. 6
Release Highlights ...................................................................................................... 7
AP Statistics ............................................................................................................... 7
Frame Utilization Monitoring ..................................................................................... 34
System Configuration Guidelines .............................................................................. 52
Network Management ............................................................................................... 57
Software Upgrade ..................................................................................................... 57
PMP 320 Administration and Configuration Guide .................................................... 58
PMP 320 Installation Guide ...................................................................................... 58
Abbreviations ............................................................................................................ 58
PMP 320 Series Product Nomenclature .................................................................... 59
Feedback on Documentation .................................................................................... 60
Technical Support ..................................................................................................... 60
Contacting Cambium Networks ................................................................................. 61
Resolved Issues ............................................................................................................ 62
Known Open Issues ...................................................................................................... 66


Introduction

This document provides information for the Cambium Networks PMP 320 product, software
release e2.3.
To ensure that all of the features of the PMP AP and CSM are available upon deployment,
be sure to upgrade the module software to the latest release available at:
http://www.cambiumnetworks.com/support/pmp/software/

The following procedure should be executed prior to upgrading to e2.3 to ensure that
QoS and service flow information may be reinstated in case of a downgrade from e2.3 to
e2.2.2.
Before upgrading from e2.2.2 to e2.3, save a configuration restore point on the APs
Administration > Configuration Control GUI page. If it is required that the network is
reverted back to a pre-2.3 release, the configuration control point may be restored, and
all QoS and service flow configuration will be restored. For pre-e2.3 software releases
only, if all configuration restore points are already populated, overwrite one of them with
the APs current configuration without changing the restore points name. Otherwise, an
unused configuration control slot may be used. This naming behavior is only present in
pre-e2.3 software releases (when using e2.3, existing configuration control restore points
may be overwritten with new names).
If an AP has been upgraded to e2.3, upon downgrading then re-upgrading the AP
software from a pre-e2.3 release to e2.3, non-default usernames and passwords added
in the pre-e2.3 release are deleted. This behavior is only exhibited when an AP with e2.3
software is downgraded, reconfigured with new usernames/passwords, and then re-
upgraded.

APPLICABILITY
The e2.3 PMP 320 System Release applies to the following products:
Access Point CAP 35320
Access Point CAP 36320
The e2.3 PMP 320 System Release contains the following components:
Access Point Version: System_Release_e2.3

NEW ACCESS POINT HARDWARE NOTIFICATIONS
IMPORTANT PMP 320 Access Points with Tanapa Numbers 3530CBA or 3630CBA
must NOT have their software downgraded FROM THE FACTORY VERSION (e2.1.1).

New versions of the PMP 320 Access Point have been shipping since mid-March 2011.
All units are labeled with a Model Number and a Tanapa Number. The Tanapa Number
is used to indicate the hardware version of the board. The currently shipping hardware
versions are listed below:
Model Number 3630APC, Tanapa=3630CBA
Model Number 3530APC, Tanapa=3530CBA

These units are shipping with PMP 320 software version e2.1.1. Downgrading units with
the Tanapa Numbers listed above will result in a locked, inaccessible radio that must be
returned to Cambium Networks for repair.
RELEASE HIGHLIGHTS
Improved Compatibility between UGPS Synchronized APs and CMM4 GPS
Synchronized APs
The PMP 320 AP software has been modified to ensure that APs that are transmission-
synchronized by a Universal GPS module (UGPS) do not interfere with APs that are
transmission-synchronized by a CMM4 module (with a GPS receiver). When upgraded
to Software Release e2.3, APs that are synchronized by a UGPS module and APs that
are synchronized by a CMM4 will transmit at the same time, thereby eliminating noise
received from nearby transmitting APs.
Expanded AP Performance Statistics
The APs performance statistics have been expanded to include MCS (Modulation and
Coding Scheme)-based statistical views as well as HARQ (Hybrid Automatic Repeat
reQuest) and Ethernet (wired interface) information. See section AP Statistics or more
information.
Frame Utilization Monitoring Updates
In Release e2.3, the APs Frame Utilization monitoring tool has been updated to include
better customization of data collection and additional statistics related to MCS
(Modulation and Coding Scheme) states, slot usage, and throughput. See section Frame
Utilization Monitoring for feature information and operating procedures.

AP STATISTICS
The PMP 320 AP contains network statistics and diagnostics that are available in the GUI
in the Performance Monitor menu which may be used to analyze and troubleshoot
network performance and operation.
Access Point Radio Info Menu
The APs Radio Info menu displays important radio link information for each registered
subscriber.

To retrieve statistical information via SNMP, an index must be appended to the SNMP
OID to distinguish for which MAC address statistics are being retrieved. For example, to
retrieve the Uplink RSSI 0 and RSSI 2 values for a CPE with MAC address
64:ed:57:40:00:9c, perform an SNMP get on the following OID:


RSSI 0:
<danBsUlChannelRssiStream0>.<CPE MAC address in decimal>.<radio channel index>
.1.3.6.1.4.1.32584.1.8.2.1.4.100.237.87.64.0.156.0
In this example, <CPE MAC address in decimal> is represented in the above OID as
100.237.87.64.0.156 and <radio channel index> is represented as 0

RSSI 2:
<danBsUlChannelRssiStream0>.<CPE MAC address in decimal>.<radio channel index>
.1.3.6.1.4.1.32584.1.8.2.1.4.100.237.87.64.0.156.2
100.237.87.64.0.156 and <radio channel index> is represented as 2

A large difference in RSSI values between the two uplink receive radio interfaces is to
be expected in certain RF environments. The AP is designed with two receive
antennas (one horizontal and one vertical). The CPE transmits on only one antenna,
which is vertical. In a LOS environment the vertical antenna will receive a higher level
of signal as it is receiving an unadulterated (vertical) signal. In an environment where
there is a lot of multipath or obstructions, the RSSI values will be much closer as the
APs antennas are receiving at a more consistent level.

Figure 1 AP Radio Info

Table 1 AP Radio Info Attributes
Attribute Meaning/SNMP Information
CPE MAC
Address
The CPE MAC Address represents the physical address of the registered RM.
Uplink,
RSSI 0
The RSSI represents the Received Signal Strength Indicator, which is a
measurement of the power level being received by the APs Main antenna. Refer
to the PMP 320 Link Budget Table available on the Cambium support website for
more information on how the measured RSSI relates to the systems link
performance.

Name danBsUlChannelRssiStream0
OID .1.3.6.1.4.1.32584.1.8.2.1.4
MIB DAN-BASIC-MIB-ADMIN
Syntax Integer32

Access read-only
Indexes danBsUlChannelMac, danBsUlChannelRadioIndex
Descr
Measured stream-0 RSSI (reports RSSI 0 value
when using danBsUlChannelRadioIndex 0)
Uplink,
RSSI 2
measurement of the power level being received by the APs Diversity antenna.
Refer to the PMP 320 Link Budget Table available on the Cambium support
website for more information on how the measured RSSI relates to the systems
link performance.

Name danBsUlChannelRssiStream0
OID .1.3.6.1.4.1.32584.1.8.2.1.4
Syntax Integer32
Access read-only
Indexes danBsUlChannelMac, danBsUlChannelRadioIndex
Descr
Measured stream-0 RSSI (reports RSSI 2 value
when using danBsUlChannelRadioIndex 2)
Uplink,
CINR
The CINR represents the APs receive Carrier to Interference Noise Ratio, which is
an expression of the carrier signal quality with respect to signal noise and co-
channel interference (or both). Refer to the PMP 320 Link Budget Table available
on the Cambium support website for more information on how the measured CINR
relates to the systems link performance.

Name danBsUlChannelCinrStream0
OID .1.3.6.1.4.1.32584.1.8.2.1.5
Syntax Integer32
Access read-only
Indexes
danBsUlChannelMac,
danBsUlChannelRadioIndex
Descr
Measured stream-0 CINR

Uplink,
MCS
The MCS represents the Modulation and Coding Scheme used for the system
uplink. This state and its associated throughput capabilities, are based on the PMP
320 system link budgets, which can be referenced in the PMP 320 Link Budget
Table available on the Cambium support website
Name danBsMcsStateUI
OID .1.3.6.1.4.1.32584.1.8.16.1.5
Syntax
INTEGER {qpsk_1_2(3), qpsk_3_4(4),
qam16_1_2(5), qam16_3_4(6), qam64_1_2(7),
qam64_2_3(8), qam64_3_4(9), qam64_5_6(10) }
Access read-only

Indexes danBsMcsMacAddr
Descr MCS State in the Uplink.
Downlink,
RSSI
measurement of the power level being received by the CPEs antenna. Refer to
the PMP 320 Link Budget Table available on the Cambium support website for
more information on how the measured RSSI relates to the systems link
performance.

Name danBsDlChannelRssiStream0
OID .1.3.6.1.4.1.32584.1.8.3.1.3
Syntax Integer32
Access read-only
Indexes danBsDlChannelMac
Descr Reported RSSI Stream-0
Downlink,
CINR
The CINR represents the CPEs receive Carrier to Interference Noise Ratio, which
is an expression of the carrier signal quality with respect to signal noise and co-
channel interference (or both). Refer to section the PMP 320 Link Budget Table
available on the Cambium support website for more information on how the
measured CINR relates to the systems link performance.
Name danBsDlChannelCinrStream0
OID .1.3.6.1.4.1.32584.1.8.3.1.4
Syntax Integer32
Access read-only
Indexes danBsDlChannelMac
Descr Reported CINR Stream-0
Downlink,
MIMO Type
The MIMO Type is the type of MIMO (A or B) used for downlink transmissions.
Multiple-Input Multiple-Output (MIMO) techniques provide protection against fading
and increase the probability that the receiver will decode a usable signal. When
the effects of MIMO are combined with those of OFDM techniques and a high link
budget, there is a high probability of a robust connection over a non-line-of-sight
path.

There are three major sub-features that comprise the MIMO techniques utilized in
the PMP 320 product:
Matrix B: This technique provides for the ability to double the throughput of a
radio transmission under proper RF conditions. Different data streams are
transmitted simultaneously on two different antennas.
Matrix A: This technique is also called Alamouti Space Time Coding. The

same data stream is transmitted at the same time on two different antennas
with special coding.
When transmitting in MIMO mode, the PMP 320 system also performs MRC:
MRC stands for Maximal Ratio Combining which is a form of receive diversity.
With this technique, two receivers and their associated antennas receive the
transmitted signal. The two received signals are combined into a single higher
quality signal. This technique increases the link budget of a system.
Downlink,
MCS
The MCS represents the Modulation and Coding Scheme used for the system
downlink. This state and its associated throughput capabilities, are based on the
PMP 320 system link budgets (see the PMP 320 Link Budget Table available on
the Cambium support website).
Name danBsMcsStateDl
OID .1.3.6.1.4.1.32584.1.8.16.1.2
Syntax
INTEGER {qpsk_1_2(3), qpsk_3_4(4),
qam16_1_2(5), qam16_3_4(6),
qam64_1_2(7), qam64_2_3(8),
qam64_3_4(9), qam64_5_6(10) }
Access read-only
Indexes danBsMcsMacAddr
Descr MCS State in the Downlink
Access Point Traffic Info Menu
The APs Traffic Info menu displays details about the management traffic received and
sent via the APs wired (Ethernet) and wireless (radio) interfaces. It is important to note
that these values do not represent the actual RF link data throughput to monitor actual
RF throughput to the CPE operators may reference the Status menu of the CPE GUI
under WIMAX RX and WIMAX TX. This throughput data may also be accessed via
SNMP queries (reference the PMP 320 CPE MIB file for OID information) or via the APs
Downlink MCS Stats, Uplink MCS Stats, and HARQ Statistics menus.

To retrieve statistical information via SNMP, the interface identifier must be appended to
the SNMP OID. For example, to retrieve the Rx Octects count, perform and SNMP get
on the following OID:

Rx Octets:
<ifInOctects>.<Interface ID>
.1.3.6.1.2.1.2.2.1.10.3
In this example, <Interface ID> is represented as 3 (wired interface)



Figure 2 AP Traffic Info

Table 2 AP Traffic Info Attributes
Attribute Meaning / SNMP Details
Interface The Interface represents the APs internal index of the interface.
Description Wired means that the data displayed is for the APs Ethernet interface.
IP Address /
Mask
The IP Address / Mask field represents the IP address and subnet mask
configured for the interface.
Rx Octets The Rx Octets represents the number of management octets that have
been received on the interface, including those containing framing
information.
Name ifInOctets
OID .1.3.6.1.2.1.2.2.1.10
MIB MIB2-DAN-MIB-ADMIN
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The total number of octets received on
the interface, including framing
characters
Rx Unicast
Packets
The Rx Unicast represents the number of management unicast
packets that have been received on the interface.
Name ifInUcastPkts
OID .1.3.6.1.2.1.2.2.1.11
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The number of subnetwork-unicast
packets delivered to a higher-layer
protocol.
Rx Non-Unicast
Packets
The Rx Non-Unicast Packets represents the number of
management non-unicast packets (broadcast and multicast) that
have been received on the interface.

Name ifInNUcastPkts
OID .1.3.6.1.2.1.2.2.1.12
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The number of non-unicast (i.e.,
subnetwork- broadcast or subnetwork-
multicast) packets delivered to a higher-
layer protocol.
Rx Discards
The Rx Discards represents the number of inbound
management octets have been discarded on the interface. Some
packets may have been discarded to increase buffer space.
Name ifInDiscards
OID .1.3.6.1.2.1.2.2.1.13
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The number of inbound packets which
were chosen to be discarded even
though no errors had been detected to
prevent their being deliverable to a
higher-layer protocol. One possible
reason for discarding such a packet
could be to free up buffer space.
Tx Octets The Tx Octets represents the number of management octets that have
been transmitted on the interface, including those containing framing
information.
Name ifOutOctets
OID .1.3.6.1.2.1.2.2.1.16
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The total number of octets transmitted
out of the interface, including framing
characters.
Tx Unicast
Packets
The Tx Unicast represents the number of management unicast
packets that have been transmitted on the interface.
Name ifOutUcastPkts
OID .1.3.6.1.2.1.2.2.1.17
Syntax Counter

Access read-only
Indexes ifIndex
Descr
The total number of packets that
higher-level protocols requested be
transmitted to a subnetwork-unicast
address, including those that were
discarded or not sent.
Tx Non-Unicast
Packets
The Tx Non-Unicast Packets represents the number of
management non-unicast packets (broadcast and multicast) that
have been transmitted on the interface.
Name ifOutNUcastPkts
OID .1.3.6.1.2.1.2.2.1.18
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The total number of packets that
higher-level protocols requested be
transmitted to a non- unicast (i.e., a
subnetwork-broadcast or subnetwork-
multicast) address.
Tx Discards
The Tx Discards represents the number of outbound
management octets have been discarded on the interface. Some
of these packets may have been discarded to increase buffer
space.
Name ifOutDiscards
OID .1.3.6.1.2.1.2.2.1.19
Syntax Counter
Access read-only
Indexes ifIndex
Descr
The number of outbound packets which
were chosen to be discarded even
though no errors had been detected to
prevent their being transmitted. One
possible reason for discarding such a
packet could be to free up buffer space.

Access Point Connected CPEs Menu
The APs Connected CPEs menu provides a display of all the CPEs that have been
allowed network entry by the AP. It also allows operators to control CPE registration via
the Deregister CPE and Reset CPE buttons.


OID to distinguish for which MAC address CID information is being retrieved. For
example, to retrieve the Basic CID for a CPE with MAC address 64:ed:57:40:00:9c,
perform an SNMP get on the following OID:

Basic CID:
<wmanIfBsSsBasicCid>.<CPE MAC address in decimal>.<interface index>
.1.3.6.1.4.1.32584.1.16.2.1.1.2.100.237.87.64.0.156.0
100.237.87.64.0.156 and <interface index> is represented as 0 (wireless interface).

Figure 3 AP Connected CPEs

Figure 4 AP Connected CPEs Attributes
Number of
Registered
CPEs
The current count of the number of CPEs that have successfully entered
the network.
Name wmanIf2BsRegisteredSsCount
OID .1.3.6.1.4.1.32584.1.16.2.1.2.10
Syntax Unsigned32
Access read-only
Descr
The current count of registered CPEs

CPE MAC The CPE MAC represents the MAC addresses of the registered RM.
Basic CID The Basic CID represents the Basic Connection Identifier, set by the AP.
The Basic Connection is used for delay-sensitive, critical MAC
messaging.
Name wmanIf2BsSsBasicCid
OID .1.3.6.1.4.1.32584.1.16.2.1.2.1.1.2
Syntax WmanIf2TcCidType
Access read-only

Indexes wmanIf2BsSsMacAddress, ifIndex
Descr
The value of this object indicates the
SS's basic CID that was sent in the RNG-
RSP message.

Primary CID The Primary CID represents the Primary Connection Identifier, set by the
AP. The Primary Connection is used for delay-tolerant MAC messaging.
Name wmanIf2BsSsPrimaryCid
OID .1.3.6.1.4.1.32584.1.16.2.1.2.1.1.3
Syntax WmanIf2TcCidType
Access read-only
Indexes wmanIf2BsSsMacAddress, ifIndex
Descr
The value of this object indicates the
primary CID of the SS received from the
RNG-RSP message.

Active Service Flow Stats, Active Service Flows Menu
The APs Active Service Flows menu provides a display of all the registered CPEs
service flow details. Operators may use the Clear Counters button to reset the service
flow counters.

example, to retrieve the Packet Count for a CPE with MAC address 64:ed:57:40:00:9c
and SF ID 5000, perform an SNMP get on the following OID:

Packet Count:
<danBsUsageRecordPcktsCount>.<CPE MAC address in decimal>.<SF ID>
.1.3.6.1.4.1.32584.1.8.1.1.4.100.237.87.64.0.156.5000
100.237.87.64.0.156 and <SF ID> is represented as 5000 (service flow ID)


Figure 5 AP Active Service Flows

Table 3 AP Service Flows Attributes
CPE MAC The CPE MAC represents the MAC addresses of the registered RM.
SF ID The SF ID represents the service flow identifier assigned by the AP.
Direction The Direction represents whether the service flow is operating in the downlink
direction or uplink direction.
QoS Profile The QoS Profile represents the QoS profile created in Configuration > Service
Flows > QoS Profiles that is implemented for the service flow.
Class
Profile
The Cls Profile is the classification profile created in Configuration > Service
Flows > Classification Rules that is implemented for the service flow.
Packet
Count
The Packet Count represents the number of packets transmitted using the service
flow.
Name danBsUsageRecordEntry.danBsUsageRecordPcktsCount
OID .1.3.6.1.4.1.32584.1.8.1.1.4
Syntax Unsigned32
Access read-only
Indexes danBsUsageRecordMacAddr, danBsUsageRecordSfId
Descr
Total packet count for the given MSS and SF ID

Bytes
Count
The Bytes Count represents the number of bytes transmitted using the service flow.
Name danBsUsageRecordBytesCount
OID .1.3.6.1.4.1.32584.1.8.1.1.5
Syntax Unsigned32
Access read-only

Indexes danBsUsageRecordMacAddr, danBsUsageRecordSfId
Descr Total bytes count for the given MSS and SF ID
Packets
Dropped
The Packets Dropped represents the number of packets dropped due to
transmission issues.
Name danBsUsageRecordPcktsDropped
OID .1.3.6.1.4.1.32584.1.8.1.1.6
Syntax Unsigned32
Access read-only
Indexes
danBsUsageRecordMacAddr,
danBsUsageRecordSfId
Descr
Total packets dropped for the given MSS and SF
ID
Bytes
Dropped
The Bytes Dropped represents the number of bytes dropped due to transmission
issues.
Name danBsUsageRecordBytesDropped
OID .1.3.6.1.4.1.32584.1.8.1.1.7
Syntax Unsigned32
Access read-only
Indexes
danBsUsageRecordMacAddr,
danBsUsageRecordSfId
Descr Total bytes dropped for the given MSS and SF ID
Active Service Flow Stats, Downlink MCS
The APs Downlink MCS menu displays information about the amount of data passed at
each MCS (Modulation and Coding Scheme) state per registered CPE. This menu is
useful for determining if CPEs are performing at the level they should be, based on the
PMP 320 link budgets (see the PMP 320 Link Budget Table available on the Cambium
support website ).

example, to retrieve the byte count for 64QAM 5/6 for a CPE with MAC address
64:ed:57:40:00:9c and SF ID 5000, perform an SNMP get on the following OID:

Downlink Bytes transferred in 64QAM 5/6 MCS:
<danBsDlMcs64Qam56MimoBCount>.<MAC address in decimal>.<SF ID>
.1.3.6.1.4.1.32584.1.8.6.1.3.100.237.87.64.0.156.5000
In this example, <MAC address in decimal> is represented in the above OID as


Figure 6 Downlink MCS Stats

Table 4 AP Downlink MCS Stats Attributes
CPE MAC The CPE MAC is the physical address of the unit for which MCS stats
are displayed
CPE SFID The CPE SFID is the AP-assigned service flow ID used for the downlink
service flow.
64QAM5/6 B,
64QAM5/6 A,
64QAM3/4 A,
64QAM2/3 A,
64QAM1/2 A,
16QAM3/4 A,
16QAM1/2 A,
QPSK3/4 A,
QPSK1/2 A
The MCS state for which stats are reported, including the MIMO state (A
or B). Refer to section the PMP 320 Link Budget Table available on the
Cambium support website for more information.
Multiple-Input Multiple-Output (MIMO) techniques provide protection
against fading and increase the probability that the receiver will decode a
usable signal. When the effects of MIMO are combined with those of
OFDM techniques and a high link budget, there is a high probability of a
robust connection over a non-line-of-sight path.

There are three major sub-features that comprise the MIMO techniques
utilized in the PMP 320 product:
Matrix B: This technique provides for the ability to double the
throughput of a radio transmission under proper RF conditions.
Different data streams are transmitted simultaneously on two
different antennas.
Matrix A: This technique is also called Alamouti Space Time Coding.
The same data stream is transmitted at the same time on two
different antennas with special coding.

When transmitting in MIMO mode, the PMP 320 system also performs
MRC: MRC stands for Maximal Ratio Combining which is a form of
receive diversity. With this technique, two receivers and their associated
antennas receive the transmitted signal. The two received signals are
combined into a single higher quality signal. This technique increases
the link budget of a system.

Name danBsDlMcs64Qam56MimoBCount

OID .1.3.6.1.4.1.32584.1.8.6.1.3
Syntax Unsigned32
Access read-only
Indexes danBsDlMcsMacAddr, danBsDlMcsSfId
Descr
Total number of bytes sent in the
downlink, in MCS state '64QAM 5/6
MIMO B'.

Name danBsDlMcs64Qam56MimoACount
OID .1.3.6.1.4.1.32584.1.8.6.1.4
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.

OID .1.3.6.1.4.1.32584.1.8.6.1.5
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.

OID .1.3.6.1.4.1.32584.1.8.6.1.6
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.


OID .1.3.6.1.4.1.32584.1.8.6.1.7
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.

OID .1.3.6.1.4.1.32584.1.8.6.1.8
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.

OID .1.3.6.1.4.1.32584.1.8.6.1.9
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
MIMO A'.

Name danBsDlMcsQpsk34MimoACount
OID .1.3.6.1.4.1.32584.1.8.6.1.10
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr Total number of bytes sent in the

downlink, in MCS state 'QPSK 1/2
MIMO A'.

Name danBsDlMcsQpsk12MimoACount
OID .1.3.6.1.4.1.32584.1.8.6.1.11
Syntax Unsigned32
Access read-only
Indexes
danBsDlMcsMacAddr,
danBsDlMcsSfId
Descr
downlink, in MCS state 'QPSK 1/2
MIMO A'.
Active Service Flow Stats, Uplink MCS
The APs Uplink MCS menu displays information about the amount of data passed at
each MCS (Modulation and Coding Scheme) state per registered CPE. This menu is
useful for determining if CPEs are performing at the level they should be, based on the
PMP 320 link budgets (see the PMP 320 Link Budget Table available on the Cambium
support website).

example, to retrieve the byte count for 64QAM 5/6 for a CPE with MAC address
64:ed:57:40:00:9c and SF ID 5001, perform an SNMP get on the following OID:

Uplink Bytes transferred in 64QAM 5/6 MCS:
<danBsDlMcs64Qam56MimoBCount>.<MAC address in decimal>.<SF ID>
.1.3.6.1.4.1.32584.1.8.7.1.3.100.237.87.64.0.156.5001
In this example, < MAC address in decimal> is represented in the above OID as

Figure 7 Uplink MCS Stats



Table 5 AP Uplink MCS Stats Attributes
Attribute Meaning
CPE MAC The CPE MAC is the physical address of the unit for which MCS stats are displayed
CPE SFID The CPE SFID is the AP-assigned service flow ID used for the downlink service
flow.
64QAM5/6,
64QAM3/4,
64QAM2/3,
64QAM1/2,
16QAM3/4,
16QAM1/2,
QPSK3/4,
QPSK1/2
The MCS state for which stats are reported, including the MIMO state (A or B).
Refer to the PMP 320 Link Budget Table available on the Cambium support website
for more information.
Name danBsUlMcs64Qam56Count
OID .1.3.6.1.4.1.32584.1.8.7.1.3
Syntax Unsigned32
Access read-only
Indexes danBsUlMcsMacAddr, danBsUlMcsSfId
Descr
uplink, in MCS state '64QAM 5/6'.

OID .1.3.6.1.4.1.32584.1.8.7.1.4
Syntax Unsigned32
Access read-only
Descr

OID .1.3.6.1.4.1.32584.1.8.7.1.5
Syntax Unsigned32
Access read-only
Descr

OID .1.3.6.1.4.1.32584.1.8.7.1.6
Syntax Unsigned32

Attribute Meaning
Access read-only
Descr
uplink, in MCS state '64QAM 1/2.

Name danBsDlMcs16Qam34Count
OID .1.3.6.1.4.1.32584.1.8.7.1.7
Syntax Unsigned32
Access read-only
Indexes danBsDlMcsMacAddr, danBsUlMcsSfId
Descr

Name danBsDlMcs16Qam12Count
OID .1.3.6.1.4.1.32584.1.8.7.1.8
Syntax Unsigned32
Access read-only
Descr

Name danBsDlMcsQpsk34Count
OID .1.3.6.1.4.1.32584.1.8.7.1.9
Syntax Unsigned32
Access read-only
Descr
uplink, in MCS state 'QPSK 3/4'.

Name danBsDlMcsQpsk12Count
OID .1.3.6.1.4.1.32584.1.8.7.1.10
Syntax Unsigned32
Access read-only
Descr
uplink, in MCS state 'QPSK 1/2'.

Active Service Flow Stats, HARQ
The APs HARQ Statistics menu displays information about the HARQ mechanism
statistics for each CPEs HARQ-enabled service flow. This menu is useful for analyzing
HARQ feedback to determine the effectiveness of the protocol for each service flow.

example, to retrieve the HARQ ACK count for CPE with MAC address 64:ed:57:40:00:9c
and SF ID 5000, perform an SNMP get on the following OID:

HARQ ACK Count:
<danHarqStatsAcks>.<MAC address in decimal>.<SF ID>
.1.3.6.1.4.1.32584.1.8.11.1.8.100.237.87.64.0.156.5000
In this example, < MAC address in decimal> is represented in the above OID as

Figure 8 AP HARQ Statistics


Table 6 AP HARQ Statistics Attributes
CPE MAC The physical address of the CPE
SF ID The AP-assigned service flow for which statistics are displayed
Direction The direction of the service flow either downlink or uplink
ACKs When successful ACKS are being received (Acks is increasing), this indicates that
the HARQ mechanism is able to properly decode data and system reliability and
throughput are being improved.

Name danHarqStatsAcks
OID .1.3.6.1.4.1.32584.1.8.11.1.8
Syntax INTEGER (0..65535)
Access read-only
Indexes
danHarqStatsMacAddr,
danHarqStatsSfId
Descr
Number of ACK's.

NACKs When negative ACKS are being received (Nacks is increasing), this indicates that
the HARQ transmitter has reached the maximum number of retransmissions without
receiving an ACK (data was not properly decoded). In this case, investigate
possible sources of RF interference that may be disrupting link quality.

Name danHarqStatsNacks
OID .1.3.6.1.4.1.32584.1.8.11.1.9
Access read-only
Indexes
danHarqStatsSfId
Descr
Number of NACK's.

Discards The Discards column represents the number of times a transmission was discarded
due to an uncorrectable error pattern. When the receiver discards a transmission, a
retransmission is requested. In this case, investigate possible sources of RF
interference that may be disrupting link quality.

Name danHarqStatsDiscards
OID .1.3.6.1.4.1.32584.1.8.11.1.10

Access read-only
Indexes
danHarqStatsSfId
Descr
Number of transmission discards

Wired Interface Statistics Menu
The APs Ethernet Statistics Menu displays information about the data received
(destined for the APs RF interface) and transmitted from the APs Ethernet (wired)
interface (from the RF interface), including VLAN-specific and QoS-specific information.

Figure 9 AP Ethernet Tx and Rx Statistics

Table 7 AP Ethernet Tx and Rx Statistics Attributes
Ethernet
Packets:
Tx, # of
Bytes
The number of bytes that were transmitted from the wired interface

Name danEthTxTotalBytes
OID .1.3.6.1.4.1.32584.1.8.13.1
Syntax Unsigned32
Access read-only
Descr
Total bytes transmitted.

Ethernet
Packets:
Tx, # of
Packets
The number of packets that were transmitted from the wired interface

Name danEthTxTotalPackets
OID .1.3.6.1.4.1.32584.1.8.13.2
Syntax Unsigned32
Access read-only
Descr Total packets transmitted.


Ethernet
Packets:
Tx, # of
Packets
with error
The number of packets that contained errors that prevented their transmission

Name danEthTxPacketErrors
OID .1.3.6.1.4.1.32584.1.8.13.3
Syntax Unsigned32
Access read-only
Descr
Total number of error packets

Ethernet
Packets:
Tx, # of
Dropped
Packets
The number of dropped packets that did not contain errors (possibly dropped to
increase buffer space)

Name danEthTxDroppedPackets
OID .1.3.6.1.4.1.32584.1.8.13.4
Syntax Unsigned32
Access read-only
Descr
Total number of packets dropped

Ethernet
Packets:
Rx, # of
Bytes
The number of bytes that were received on the wired interface

Name danEthRxTotalBytes
OID .1.3.6.1.4.1.32584.1.8.13.5
Syntax Unsigned32
Access read-only
Descr
Total bytes received

Ethernet
Packets:
Rx, # of
Packets
The number of packets that were received on the wired interface

Name danEthRxTotalPackets
OID .1.3.6.1.4.1.32584.1.8.13.6
Syntax Unsigned32
Access read-only
Descr
Total packets received


Ethernet
Packets:
Rx, # of
Packets
with error
The number of received packets that contained errors that were dropped on the
wired interface

Name danEthRxPacketErrors
OID .1.3.6.1.4.1.32584.1.8.13.8
Syntax Unsigned32
Access read-only
Descr
Total number of packets received with
errors

Ethernet
Packets:
Rx, # of
Dropped
Packets
The number of dropped packets that did not contain errors (possibly dropped to
increase buffer space)

Name danEthRxDroppedPackets
OID .1.3.6.1.4.1.32584.1.8.13.9
Syntax Unsigned32
Access read-only
Descr
Total number of received packets
dropped

Ethernet
Packets:
Rx, # of
Broadcast
Packets
The number of broadcast protocol packets that were received on the wired interface

Name danEthRxBroadcastPackets
OID .1.3.6.1.4.1.32584.1.8.13.7
Syntax Unsigned32
Access read-only
Descr
Total number of broadcast packets
received

Figure 10 AP Ethernet VLAN Rx Packets Statistics


Table 8 AP Ethernet VLAN Rx Packets Attributes
Ethernet Rx: IP
Packets, with
VLAN tag,
Received
The number of IP packets received on the wired interface that were tagged with
VLAN information

Name danEthRxIpPacketsVlan
OID .1.3.6.1.4.1.32584.1.8.13.10
Syntax Unsigned32
Access read-only
Descr
Total number of received IP packets, with
VLAN tag
Ethernet RX: IP
Packets, with
VLAN tag,
Dropped
The number of IP packets received on the wired interface that were tagged with
VLAN information which were dropped (possibly to increase buffer space)

Name danEthRxIpPacketsVlanDropped
OID .1.3.6.1.4.1.32584.1.8.13.14
Syntax Unsigned32
Access read-only
Descr
Total number of received IP packets, with
VLAN tag, dropped
Ethernet Rx: IP
Packets,
without VLAN
tag, Received
The number of IP packets received on the wired interface that were not tagged with
VLAN information

Name danEthRxIpPacketsNonVLAN
OID .1.3.6.1.4.1.32584.1.8.13.11
Syntax Unsigned32
Access read-only
Descr
Total number of received IP packets,
without VLAN tag
Ethernet Rx: IP
Packets,
without VLAN
tag, Dropped
The number of IP packets received on the wired interface that were not tagged with

Name danEthRxIpPacketsNonVlanDropped
OID .1.3.6.1.4.1.32584.1.8.13.15
Syntax Unsigned32
Access read-only
Descr Total number of received IP packets,

without VLAN tag, dropped
Ethernet Rx:
Non-IP Packets,
with VLAN tag,
Received
The number of layer 2 packets received on the wired interface that were tagged with
VLAN information

Name danEthRxNonIpPacketsVlan
OID .1.3.6.1.4.1.32584.1.8.13.12
Syntax Unsigned32
Access read-only
Descr
Total number of received Non-IP packets,
with VLAN tag

Ethernet Rx:
Non-IP Packets,
with VLAN tag,
Dropped
The number of layer 2 packets received on the wired interface that were tagged with

Name danEthRxNonIpPacketsVlanDropped
OID .1.3.6.1.4.1.32584.1.8.13.16
Syntax Unsigned32
Access read-only
Descr
with VLAN tag, dropped
Ethernet Rx:
Non-IP Packets,
without VLAN
tag, Received
The number of layer 2 packets received on the wired interface that were not tagged
with VLAN information

Name danEthRxNonIpPacketsNonVlan
OID .1.3.6.1.4.1.32584.1.8.13.13
Syntax Unsigned32
Access read-only
Descr
without VLAN tag
Ethernet Rx:
Non-IP Packets,
without VLAN
tag, Dropped
The number of layer 2 packets received on the wired interface that were not tagged
with VLAN information which were dropped (possibly to increase buffer space)

Name danEthRxNonIpPacketsNonVlanDropped
OID .1.3.6.1.4.1.32584.1.8.13.17
Syntax Unsigned32

Access read-only
Descr
without VLAN tag, dropped

Figure 11 AP QoS Rx Packet Classification Statistics

Table 9 AP QoS Rx Packet Classification Statistics Attributes
Ethernet Rx: IP
Packets, ToS
The number of packets that contained a TOS value that matched a configured
classification profile rule. These packets will be transmitted over the wireless
interface using the QoS profile configured in the matching classification profile

Name danEthRxClsTos
OID .1.3.6.1.4.1.32584.1.8.13.21
Syntax Unsigned32
Access read-only
Descr
Total number of received packets,
classified by TOS
Ethernet Rx: IP
Packets, IP,
Destination
The number of packets that contained a destination IP that matched a configured
interface using the QoS profile configured in the matching classification profile.

Name danEthRxClsDestIp
OID .1.3.6.1.4.1.32584.1.8.13.19
Syntax Unsigned32
Access read-only
Descr
classified by destination IP
Ethernet Rx: IP
Packets, IP,
Source
The number of packets that contained a source IP that matched a configured


Name danEthRxClsSrcIp
OID .1.3.6.1.4.1.32584.1.8.13.20
Syntax Unsigned32
Access read-only
Descr
classified by source IP
Ethernet Rx: IP
Packets, VLAN,
ID
The number of packets that contained a VLAN ID value that matched a configured

Name danEthRxClsVlanId
OID .1.3.6.1.4.1.32584.1.8.13.22
Syntax Unsigned32
Access read-only
Descr
classified by VLAN Id
Ethernet Rx: IP
Packets, VLAN,
Priority
The number of packets that contained a VLAN priority value that matched a
configured classification profile rule. These packets will be transmitted over the
wireless interface using the QoS profile configured in the matching classification
profile.

Name danEthRxClsVlanPriority
OID .1.3.6.1.4.1.32584.1.8.13.23
Syntax Unsigned32
Access read-only
Descr
classified by VLAN priority
Ethernet Rx: IP
Packets, MAC,
Destination
The number of packets that contained a destination MAC address that matched a
profile.

Name danEthRxClsDestMac
OID .1.3.6.1.4.1.32584.1.8.13.24
Syntax Unsigned32
Access read-only

Descr
classified by destination MAC
Ethernet Rx: IP
Packets, MAC,
Source
The number of packets that contained a source MAC address that matched a
profile.

Name danEthRxClsSrcMac
OID .1.3.6.1.4.1.32584.1.8.13.25
Syntax Unsigned32
Access read-only
Descr
classified by source MAC

FRAME UTILIZATION MONITORING
The Frame Utilization table located at the APs Performance Monitor > Frame
Utilization menu may be used to calculate frame usage on the PMP 320 downlink and
uplink. This calculation is valuable in answering the following questions:
RF link utilization is the RF link overloaded on the uplink or downlink,
or are the CPEs operating at the expected MCS (Modulation and Coding
Scheme) state?
Sector capacity does the AP have enough MAP slots available to
handle control messaging for all registered CPEs?
Network expansion feasibility- based on the RF link utilization, what can
be expected as the number of CPEs is increased?

Frame utilization data should be collected over an extended period of time that
includes peak and non-peak usage hours to properly analyze RF link utilization.
It is recommended to use an Analysis Interval (frames) of at least 100 frames
when using the monitor. Analyzing this sample size or greater ensures that the
resulting data provides a consistent representation of the RF link activity.
The frame utilization monitor may be configured, controlled, and monitored via SNMP
commands. See the procedure below for details on SNMP frame utilization usage.


Figure 12 Frame Utilization Monitoring Basic Metrics

Figure 13 Frame Utilization Monitoring MCS Metrics

Table 10 Using the Frame Utilization Monitoring Feature
1 Log in to the AP GUI
2 On the AP GUI navigate to Performance Monitor > Frame Utilization.

3 Enter the interval (number) of frames to be monitored in the field Analysis Interval (frames). This
value represents the number of frames to be analyzed for utilization during each iteration of the
monitoring process starting when the operator clicks Start Data Collection and ending when the
operator clicks Stop Data Collection. During the collection, frame utilization analysis is performed
on consecutive frames.

Only when monitoring AP frame utilization with a single registered CPE, using an Analysis
Interval of 5 frames may produce varying throughput table results.
It is recommended to use an Analysis Interval (frames) of at least 100 frames when using
the monitor. Analyzing this sample size or greater ensures that the resulting data provides a
consistent representation of the RF link activity.
Analysis Interval SNMO OID Information:
Name danDevInfoMeasureSlotsCmd
OID .1.3.6.1.4.1.32584.1.3.4.1
Syntax Integer (5..1000)
Access read-write
Descr
Defines the number of frames (5 1000)
to be analyzed for each monitoring
repetition.
4 Enter the Repetition Rate (secs). This value represents how often the AP will begin frame utilization
analysis of the number of frames specified in Analysis Interval (frames). One table row will be
created for each repetition of analysis.

Repetition Rate SNMP OID Information:
Name danDevInfoFrameUtilRepetitionRate
OID .1.3.6.1.4.1.32584.1.3.4.8
Syntax Integer32 (5..60)
Access read-write
Descr
Frame utilization data collection repetition
interval in seconds (range 5 60). This
field identifies the time between two
consecutive executions of the frame
utilization data collection.
5 Click Update.

6 To begin analysis, click Start Data Collection.

To begin analysis via SNMP, perform an SNMP set command (with a set value of 1) using the
following OID.
Name danDevInfoFrameUtilCollection
OID .1.3.6.1.4.1.32584.1.3.4.7
Syntax
INTEGER {startCollection(1),
stopCollection(2)}
Access read-write
Descr
Start and Stop operation for the Frame
Utilization feature that is based on the the
configured Analysis Interval and
Repetition Rate.
7 There are three table display option buttons available, Basic Metrics, MCS Metrics, and All Metrics,
detailed below.

Each metric may be retrieved individually via SNMP. Each metric is retrieved based on the System
Time for which the data was collected.

For example, to retrieve the first collection of DL Slots Used (%), begin by performing an SNMP
getnext command, similar to below:

snmpgetnext -v2c -c admin_admin 10.1.1.2 .1.3.6.1.4.1.32584.1.3.4.6.1.8
SNMPv2-SMI::enterprises.32584.1.3.4.6.1.8.3542662153 = INTEGER: 2

To retrieve the next collection of DL Slots Used (%), perform an SNMP getnext command using the
system time (in integer format) from the previous retrieval, similar to below:

snmpgetnext -v2c -c admin_admin 10.1.1.2
.1.3.6.1.4.1.32584.1.3.4.6.1.8.3542662153
SNMPv2-SMI::enterprises.32584.1.3.4.6.1.8.3542662158 = INTEGER: 1

Operators may also choose to retrieve all of the collection data at once, which may be performed by
issuing an SNMP walk command, similar to below:

snmpwalk -v2c -c admin_admin 10.1.1.2.1.3.6.1.4.1.32584.1.3.4.6
Result: All table values are retrieved and displayed

Basic Metrics / SNMP Details
System Time The time for which the period of analysis began, based on Repetition
Rate (secs)
Name danDevInfoFrameUtilSysTime
OID .1.3.6.1.4.1.32584.1.3.4.6.1.1
Syntax Unsigned32

Access read-only
Indexes danDevInfoFrameUtilSysTime
Descr
The time in GMT at which the data was
collected
DL Slots Used (%) The percentage of downlink data slots used in the Analysis Interval
(frames). A good practice in network operation is to try to keep the
average usage at or below 80%.
Name danDevInfoFrameUtilPercDLSlotsUsed
OID .1.3.6.1.4.1.32584.1.3.4.6.1.4
Syntax Integer32
Access read-only
Descr
Percentage of total DL slots used in the
Analysis Interval not including MAP
(Medium Access Control) and FCH
(Frame Control Header)
UL Slots Used (%) The percentage of uplink data slots used in the Analysis Interval
(frames). A good practice in network operation is to try to keep the
average usage at or below 80%.
Name danDevInfoFrameUtilPercULSlotsUsed
OID .1.3.6.1.4.1.32584.1.3.4.6.1.6
Syntax Integer32
Access read-only
Descr
Number of DL slots used in the Analysis
Interval not including uplink control slots
MAP Slots Used (%) The Map slots allocate downlink and uplink resources in each WiMAX
frame. This value represents the average usage of the Map slots in the
Analysis Interval (frames). A good practice in network operation is to
try to keep the Map Average Usage at or below 80%. If Map Average
Usage is reporting greater than 80% usage but the Average Usage is
below 80% the Map Symbol # parameter located in the AP GUI at
Configuration > Mode may be increased to 7, thereby increasing the
Map header and allowing for more Map overhead.
Name danDevInfoFrameUtilMapSlotsUsed
OID .1.3.6.1.4.1.32584.1.3.4.6.1.8
Syntax Integer32
Access read-only
Descr
Percentage of MAP slots used in the
Analysis Interval
Frames MAP Full (%) As a percentage of the Analysis Interval (frames), this value is an
indication of the system capacity from a resource allocation (or control)
perspective. The number of CPEs, number of service flows

established, and the polling intervals for non-Best Effort service flows
can all have an impact on this ratio.
Name danDevInfoFrameUtilMapFull
OID .1.3.6.1.4.1.32584.1.3.4.6.1.9
Syntax Integer32
Access read-only
Descr
Number of frames in the Analysis Interval
for which scheduling stopped because
MAP was full
DL Throughput
(Kbps)
The average downlink throughput achieved during the Analysis
Interval (frames).
Name danDevInfoFrameUtilDlThroughput
OID .1.3.6.1.4.1.32584.1.3.4.6.1.27
Syntax Unsigned32
Access read-only
Descr
Over the air DL throughput in bps during
the Analysis Interval
UL Throughput
(Kbps)
The average uplink throughput achieved during the Analysis Interval
(frames).
Name danDevInfoFrameUtilUlThroughput
OID .1.3.6.1.4.1.32584.1.3.4.6.1.28
Syntax Unsigned32
Access read-only
Descr
Over the air UL throughput in bps during
the Analysis Interval

MCS Metrics

System Time The time for which the period of analysis began, based
on Repetition Rate (secs)
OID .1.3.6.1.4.1.32584.1.3.4.6.1.1
Syntax Unsigned32
Access read-only
Descr
The time in GMT at which the data
was collected

DL 64QAM 5/6 MIMO-B %),
DL 64QAM 5/6 (%), DL
64QAM 3/4 (%), DL 64QAM
2/3 (%), DL 64QAM 1/2 (%),
DL 16QAM 3/4 (%), DL
16QAM 1/2 (%), DL QPSK
3/4 (%), DL QPSK 1/2 (%)
The percentage of downlink data slots used in the
Analysis Interval (frames) for each MCS (Modulation
and Coding Scheme) state.
Name danDevInfoFrameUtilDl64QAM67MimoB
OID .1.3.6.1.4.1.32584.1.3.4.6.1.10
Syntax Integer32
Access read-only
Descr
The percentage of DL slots modulated
with 64QAM 5/6 using MIMO B diversity

Name danDevInfoFrameUtilDl64QAM56
OID .1.3.6.1.4.1.32584.1.3.4.6.1.11
Syntax Integer32
Access read-only
Descr
with 64QAM 5/6 using MIMO A
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.12
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.13
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.14

Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.15
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.16
Syntax Integer32
Access read-only
Descr
diversity

Name danDevInfoFrameUtilDlQPSK34
OID .1.3.6.1.4.1.32584.1.3.4.6.1.17
Syntax Integer32
Access read-only
Descr
with QPSK 3/4 using MIMO A diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.18
Syntax Integer32
Access read-only

Descr
UL 64QAM 5/6 (%), UL
64QAM 3/4 (%), UL 64QAM
2/3 (%), UL 64QAM 1/2 (%),
UL 16QAM 3/4 (%), UL
16QAM 1/2 (%), UL QPSK
3/4 (%), UL QPSK 1/2 (%)
The percentage of uplink data slots used in the

Name danDevInfoFrameUtilUl64QAM56
OID .1.3.6.1.4.1.32584.1.3.4.6.1.19
Syntax Integer32
Access read-only
Descr
The percentage of UL slots modulated
with 64QAM 5/6

OID .1.3.6.1.4.1.32584.1.3.4.6.1.20
Syntax Integer32
Access read-only
Descr
with 64QAM 3/4

OID .1.3.6.1.4.1.32584.1.3.4.6.1.21
Syntax Integer32
Access read-only
Descr
with 64QAM 2/3

OID .1.3.6.1.4.1.32584.1.3.4.6.1.22
Syntax Integer32
Access read-only
Descr
with 64QAM 1/2


OID .1.3.6.1.4.1.32584.1.3.4.6.1.23
Syntax Integer32
Access read-only
Descr
with 16QAM 3/4

OID .1.3.6.1.4.1.32584.1.3.4.6.1.24
Syntax Integer32
Access read-only
Descr
with 16QAM 1/2

Name danDevInfoFrameUtilUlQPSK34
OID .1.3.6.1.4.1.32584.1.3.4.6.1.25
Syntax Integer32
Access read-only
Descr
with QPSK 3/4

OID .1.3.6.1.4.1.32584.1.3.4.6.1.26
Syntax Integer32
Access read-only
Descr
with QPSK 1/2

All Metrics

System Time The time for which the period of analysis began, based
on Repetition Rate (secs)

OID .1.3.6.1.4.1.32584.1.3.4.6.1.1

Syntax Unsigned32
Access read-only
Descr
The time in GMT at which the data
was collected
Total DL Slots The total number of downlink slots analyzed during the
Analysis Interval (frames).

Name danDevInfoFrameUtilTotalDLSlots
OID .1.3.6.1.4.1.32584.1.3.4.6.1.2
Syntax Integer32
Access read-only
Descr
Total number of DL slots in the
DL Slots Used The total number of downlink slots used during the

Name danDevInfoFrameUtilTotalDLSlots
OID .1.3.6.1.4.1.32584.1.3.4.6.1.2
Syntax Integer32
Access read-only
Descr
Total number of DL slots in the
DL Slots Used (%) The percentage of downlink data slots used in the
Analysis Interval (frames). A good practice in
network operation is to try to keep the average usage at
or below 80%.

OID .1.3.6.1.4.1.32584.1.3.4.6.1.4
Syntax Integer32
Access read-only
Descr

Total UL Slots The total number of uplink slots analyzed during the

OID .1.3.6.1.4.1.32584.1.3.4.6.1.4
Syntax Integer32
Access read-only
Descr
UL Slots Used The total number of uplink slots used during the
UL Slots Used (%) The percentage of uplink data slots used in the
Analysis Interval (frames). A good practice in
network operation is to try to keep the average usage at
or below 80%.

Name danDevInfoFrameUtilPercULSlotsUsed
OID .1.3.6.1.4.1.32584.1.3.4.6.1.6
Syntax Integer32
Access read-only
Descr
Number of DL slots used in the
Analysis Interval not including uplink
control slots
MAP Slots Used (%) The Map slots allocate downlink and uplink resources in
each WiMAX frame. This value represents the average
usage of the Map slots in the Analysis Interval
(frames). A good practice in network operation is to try
to keep the Map Average Usage at or below 80%. If
Map Average Usage is reporting greater than 80%
usage but the Average Usage is below 80% the Map
Symbol # parameter located in the AP GUI at
Configuration > Mode may be increased to 7, thereby
increasing the Map header and allowing for more Map
overhead.

Name danDevInfoFrameUtilMapSlotsUsed
OID .1.3.6.1.4.1.32584.1.3.4.6.1.8
Syntax Integer32
Access read-only

Descr
Percentage of MAP slots used in the
Analysis Interval
Frames MAP Full (%) As a percentage of the Analysis Interval (frames), this
value is an indication of the system capacity from a
resource allocation (or control) perspective. The
number of CPEs, number of service flows established,
and the polling intervals for non-Best Effort service
flows can all have an impact on this ratio.

Name danDevInfoFrameUtilMapFull
OID .1.3.6.1.4.1.32584.1.3.4.6.1.9
Syntax Integer32
Access read-only
Descr
Number of frames in the Analysis
Interval for which scheduling stopped
because MAP was full
DL 64QAM 5/6 MIMO-B
(%),DL 64QAM 5/6 (%), DL
64QAM 3/4 (%), DL 64QAM
2/3 (%), DL 64QAM 1/2 (%),
DL 16QAM 3/4 (%), DL
16QAM 1/2 (%), DL QPSK
3/4 (%), DL QPSK 1/2 (%)
The number of downlink data slots used in the

Name danDevInfoFrameUtilDl64QAM56MimoB
OID .1.3.6.1.4.1.32584.1.3.4.6.1.10
Syntax Integer32
Access read-only
Descr
with 64QAM 5/6 using MIMO B diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.11
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.12

Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.13
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.14
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.15
Syntax Integer32
Access read-only
Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.16
Syntax Integer32
Access read-only

Descr
diversity

OID .1.3.6.1.4.1.32584.1.3.4.6.1.17
Syntax Integer32
Access read-only
Descr

OID .1.3.6.1.4.1.32584.1.3.4.6.1.18
Syntax Integer32
Access read-only
Descr
UL 64QAM 5/6 (%), UL
64QAM 3/4 (%), UL 64QAM
2/3 (%), UL 64QAM 1/2 (%),
UL 16QAM 3/4 (%), UL
16QAM 1/2 (%), UL QPSK
3/4 (%), UL QPSK 1/2 (%)
The number of uplink data slots used in the Analysis
Interval (frames) for each MCS (Modulation and
Coding Scheme) state.

OID .1.3.6.1.4.1.32584.1.3.4.6.1.19
Syntax Integer32
Access read-only
Descr
with 64QAM 5/6

OID .1.3.6.1.4.1.32584.1.3.4.6.1.20
Syntax Integer32
Access read-only
Descr
with 64QAM 3/4


OID .1.3.6.1.4.1.32584.1.3.4.6.1.21
Syntax Integer32
Access read-only
Descr
with 64QAM 2/3

OID .1.3.6.1.4.1.32584.1.3.4.6.1.22
Syntax Integer32
Access read-only
Descr
with 64QAM 1/2

OID .1.3.6.1.4.1.32584.1.3.4.6.1.23
Syntax Integer32
Access read-only
Descr
with 16QAM 3/4

OID .1.3.6.1.4.1.32584.1.3.4.6.1.24
Syntax Integer32
Access read-only
Descr
with 16QAM 1/2

Name danDevInfoFrameUtilUlQPSK34
OID .1.3.6.1.4.1.32584.1.3.4.6.1.25
Syntax Integer32
Access read-only

Descr
with QPSK 3/4

OID .1.3.6.1.4.1.32584.1.3.4.6.1.26
Syntax Integer32
Access read-only
Descr
with QPSK 1/2
DL Throughput (Kbps) The average downlink throughput achieved during the

Name danDevInfoFrameUtilDlThroughput
OID .1.3.6.1.4.1.32584.1.3.4.6.1.27
Syntax Unsigned32
Access read-only
Descr
Over the air DL throughput in bps
during the Analysis Interval
UL Throughput (Kbps) The average uplink throughput achieved during the

Name danDevInfoFrameUtilUlThroughput
OID .1.3.6.1.4.1.32584.1.3.4.6.1.28
Syntax Unsigned32
Access read-only
Descr
Over the air UL throughput in bps
Avg DL MCS (bits/slot) The average number of downlink bits per slot over the
Analysis Interval, based on the MCS state.

Name danDevInfoFrameUtilDlAvgMCS
OID .1.3.6.1.4.1.32584.1.3.4.6.1.29
Syntax Integer32
Access read-only
Descr
Average DL MCS (in bits/slot units)
utilized during the Analysis Interval

Avg UL MCS (bits/slot) The average number of uplink bits per slot over the
Analysis Interval, based on the MCS state.

Name danDevInfoFrameUtilUlAvgMCS
OID .1.3.6.1.4.1.32584.1.3.4.6.1.30
Syntax Integer32
Access read-only
Descr
Average UL MCS (in bits/slot units)
utilized during the Analysis Interval
Avg DL Unused
Slots/Frame
The average (over the Analysis Interval) number of
downlink slots that were not used for data transmission.

Name danDevInfoFrameUtilAvgDlUnusedSlots
OID .1.3.6.1.4.1.32584.1.3.4.6.1.31
Syntax Integer32
Access read-only
Descr
Average unused DL slots per frame
Avg UL Unused
Slots/Frame
The average (over the Analysis Interval) number of
uplink slots that were not used for data transmission.

Name danDevInfoFrameUtilAvgUlUnusedSlots
OID .1.3.6.1.4.1.32584.1.3.4.6.1.32
Syntax Integer32
Access read-only
Descr
Average unused UL slots per frame

8 To stop analysis, click Stop Data Collection.

To stop analysis via SNMP, perform an SNMP set command (with a set value of 2) using the
following OID.
Name danDevInfoFrameUtilCollection
OID .1.3.6.1.4.1.32584.1.3.4.7
Syntax
INTEGER {startCollection(1),
stopCollection(2)}
Access read-write
Descr
Start and Stop operation for the Frame
Utilization feature that is based on the the
configured Analysis Interval and
Repetition Rate.

SYSTEM CONFIGURATION GUIDELINES
System Release e2.3-Specific Upgrade Notes
After upgrading a PMP 320 CSM to System Release e2.3 (CSM version 8.1.4), if the
CSM device type changes to generic in CNUT, the element may be changed back to a
PMP 320 CSM device in CNUT by right-clicking on the element and selecting Change
Network Element Type.
Before upgrading from e2.2.2 to e2.3, save a configuration restore point on the APs
Administration > Configuration Control GUI page. If it is required that the network is
reverted back to a pre-2.3 release, the configuration control point may be restored, and
all QoS and service flow configuration will be restored. Before upgrading to e2.3, if all
configuration restore points are already populated, overwrite one of them with the APs
current configuration without changing the restore points name. Otherwise, an unused
configuration control slot may be used. When using e2.3, configuration control restore
points may be created with new names.
Before upgrading to e2.3, the APs admin account password should be set to admin.
During the upgrade process, all AP usernames and passwords are reset to their default
values. By configuring the APs admin account password to its default value before
upgrading, the CNUT upgrade process will be completed in one step.
PMP 320 Module Staging
It is common to stage the equipment prior to installation on-site. During the staging
process, the modules may be upgraded to the latest software version, configured to the
operators specifications, and validated for proper functionality.
PMP 320 Module Pre-deployment Upgrading
When the radios arrive from the factory, the software version may be upgraded
immediately to take advantage of the latest software functionality and performance. The

following steps can be used to update a single AP and all of its CSMs in a rapid fashion.
This can be useful if a single sector is being updated for testing purposes. Also, these
operations are a logical building block for performing larger updates across your entire
network. By default the PMP 320 AP and CSM are configured in layer 3 mode, and the
AP will issue IP addresses (via DHCP) to the CSMs beginning with 192.168.4.20 for the
first registered SM, 192.168.4.21 for the second registered CSM, and so on.
Assumptions
Canopy Network Updater is installed and operational on your computer. The
software may be downloaded via the Cambium Support website.
The AP has a routable IP address that the Network Updater computer can
communicate.
All of the CSMs associated with the AP are powered up and currently registered
to the AP. By default, upon shipment and powering on the CSMs will register to
the AP (assuming the APs associated antenna is connected).
The Installation Package needed to upgrade the radio has been downloaded
from the Cambium Support website
(http://www.cambiumnetworks.com/support/pmp/software) and added to the
Network Updater through the Manage Packages operation (located in Update >
Manage Packages).
Steps to Perform a Single AP Sector Upgrade
1
Start Network Updater (CNUT).
2
If you dont start up with a blank new network file, then open a new network file
with the New Network Archive operation (see File > New Network Archive in
CNUT).
3
Enter a new network element to the empty network tree using the Add Elements
to Network Root operation (see Edit > Add Elements to Network Root in CNUT).
4
On the Add Elements dialogue, enter the IP address of the AP within the
Element Host Names area of the dialogue. The Telnet/FTP Login ID is admin
and the Telnet/FTP Password is admin. The SNMP Community string is
admin_admin. All other parameters in the dialogue may be left at their default
values.
5
On the Add Elements dialogue, enter the IP address of the CSM (beginning with
192.168.4.20 for the first registered CSM, 192.168.4.21 for the second
registered CSM, and so on). The Telnet/FTP Login ID is administrator and the
Telnet/FTP password is motorola. The SNMP Community string is private.
All other parameters in the dialogue may be left at their default values.

If a factory default procedure is initiated for a CSM with software version
>= f12b00-v8.1.4, the default Telnet/FTP password will be changed to
cambium.
6
Make sure the proper Installation Package is active with the Package Manager
dialogue (see Update > Manage Packages in CNUT).
7 To verify connectivity with the radio, perform a Discover Entire Network

operation (see View > Refresh/Discover Entire Network in CNUT). You should
see the details columns for the AP and CSMs be filled in with ESN and software
version information.
8
Initiate the upgrade of the AP and its CSMs using the Update Entire Network
Root operation (see Update > Update Entire Network Root in CNUT).
9
When the AP and all CSMs show updated software and FPGA version, the AP
sector upgrade is complete.

Quality of Service (QoS)
When configuring Classification Rules in a Layer 2 AP and using type Src MAC Addr
(Source MAC Address), the rule will only be functional for uplink traffic. This is due to the
inherent functionality of Layer 2 networks such that each routing device in the network
situated above the AP will modify the source MAC address field in the packet with its own
MAC address. Therefore, the source MAC address field may not represent the
originating device by the time the classification rule is applied to the packet.
When creating uplink service flows on the CSM the user may only create one uplink
service flow with HARQ enabled. Operators requiring more than one uplink service flow
with HARQ enabled should deploy CSMs with software release 7.1.3.
Service flows and impacts to single CSM throughput: In certain scenarios presence of
additional higher priority QOS service flows to a single CSM will impact the maximum
possible throughput of the CSM.
HARQ Configuration Recommendations:
The recommended service flow configuration for systems not exhibiting packet
loss is with HARQ Disabled.
Enabling HARQ with Retries=0 is NOT a valid configuration for uplink or downlink
service flows.
Please refer to the PMP 320 Administration and Configuration Guide for more
details.
Downlink Service Flow HARQ Configuration Details:
To reduce downlink packet loss and to minimize fluctuations in TCP
throughput operators may configure Best Effort (BE), Non-realtime polling
service (nrtPS), and Real-time polling service (rtPS) service flows with HARQ
enabled and Retries > 0. If VOIP-specific QoS profiles are required, rtPS
may be used to handle the traffic (with HARQ enabled).
Do not configure HARQ enabled with > 0 retries for Unsolicited Grant Service
(UGS) and Extended-real time polling service (ertPS) QoS types. Even in
systems exhibiting downlink packet loss, using these service flows with
HARQ disabled is recommended to maximize performance of applications
that benefit from these data delivery types (i.e. VOIP, Video).

Although total sector throughput is not impacted, enabling downlink HARQ
will restrict single CSM downlink TCP throughput to <= 10 Mbps.
Uplink Service Flow HARQ Configuration Details:
To reduce uplink packet loss and to minimize fluctuations in TCP throughput
operators may configure Best Effort (BE), Non-realtime polling service
(nrtPS), and Real-time polling service (rtPS) service flows with HARQ
enabled and Retries > 0. If VOIP-specific QoS profiles are required, rtPS
may be used to handle the traffic (with HARQ enabled).
Do not configure HARQ enabled with > 0 retries for Unsolicited Grant Service
(UGS) and Extended-real time polling service (ertPS) QoS types. Even in
systems exhibiting uplink packet loss, using these service flows with HARQ
disabled is recommended to maximize performance of applications that
benefit from these data delivery types (i.e. VOIP, Video).
Prior to release e2.1, it was recommended that VOIP support in the PMP 320 system is
set up via configuration of UGS service flows. Starting from e2.1 ertPS is the
recommended data delivery configuration for VOIP services. The key differentiator is that
for UGS, the PMP 320 AP will reserve the uplink bandwidth based on the MIR/CIR values
for that service flow regardless of traffic being present or not. This can be a limiting factor
for the number of subscribers one can provision for VOIP before running into UL
bandwidth limitations. In the case of ertPS, the bandwidth is allocated only when the
CSM requests it via a polling mechanism.
Radio Link
Software release e2.2 included design improvements in the PMP 320 uplink algorithm for
packet loss reduction in challenging RF environments and for better sector capacity.
Operators may observe uplink MCS state transitions sooner (2dB - 3dB) at a given RSSI
than what is detailed in the PMP320 Link Budget Table. Since CINR Uplink Backoff
values are global parameters affecting the entire sector, operators deploying CINR
backoff values of 6dB or greater should revisit configured CINR backoff parameters and
reduce the backoff by 3dB to coordinate with the e2.2 design improvements.
In order for a radio to achieve a particular uplink modulation and coding state (i.e.
quam64-ctc-5/6, qam16-ctc-3/4, qpsk-ctc-3/4, etc.) certain CINR value requirements
must be met. For example, a 10MHz channel bandwidth AP has a minimum uplink CINR
requirement of 25 dB to achieve maximum MCS qam64-ctc-5/6. For state qam16-ctc-
3/4, the AP has a minimum uplink CINR requirement of 22 dB. See document PMP320
Link Budget Table on the Cambium Support website for detailed descriptions and
tables on MCS CINR requirements. Since these requirements contain a corresponding
minimum required AP receive power level, the AP adjusts the SM transmit power level
accordingly for each MCS state. By increasing the uplink backoff parameters, the
required uplink CINR levels for each MCS state are increased, resulting in stricter uplink
CINR requirements for each MCS state and generally reduced SM transmit levels.
For example, a configured uplink backoff value of 6dB for a 10MHz channel bandwidth
AP will translate as follows:

Table 11: UL CINR Backoff Example
MCS Default
Minimum
Required
UL CINR
(dB)
Default
Minimum
Required AP
Rx (dBm)
Backoff-applied Minimum
Required UL CINR (dB):
Configured backoff value
3dB (default backoff) +
Default Minimum Required
UL CINR
qam64-ctc-5/6 25 -73 28
qam64-ctc-3/4 22 -75 25
qam64-ctc-2/3 21 -77 24
qam64-ctc-1/2 19 -78 22
qam16-ctc-3/4 17 -81 20
qam16-ctc-1/2 14 -84 17
qpsk-ctc-3/4 11 -87 14
qpsk-ctc-1/2 5 -93 8
Sensitivity 4 -94 7
If upgrading from software release e2.1.1 (and only e2.1.1) to e2.3, operators with
previously applied uplink backoff values will need to re-apply the desired values in AP
Configuration > Air Interface > CINR Configuration after upgrading to release e2.3. Once
the values are entered, click Update, click the Save icon, then reset the AP.
After the AP upgrade to e2.3 is complete, log in to the AP GUI and browse to AP
Configuration > Air Interface > CINR Configuration. Confirm that both the downlink and
uplink backoff fields display a numerical value rather than a No Access error. If the
error message is displayed, enter the desired backoff values, save the changes, and
reboot the AP.
When using the PMP 320 CSM (CSM 35320 or CSM 36320), the downlink backoff
should always be set to the default value of 3 dB.
Spectrum Analyzer Mode
Spectrum Analyzer mode is a listening-only radio function and when using this mode all
AP to CSM communication will cease until AP is changed back to Operation Mode
Internal AAA or External AAA.
The AP spectrum analyzer is constantly scanning once enabled and hence is not timed
with only the UL or DL portions of reception. The spectrum analyzer will report power
from APs and CSMs alike so proper planning and understanding of the results must be

applied. If the purpose of the spectrum analysis being conducted is to determine RF
integrity of the environment or to look for transmitters outside of the PMP 320 towers,
then all PMP 320 APs should be turned off or turned into spectrum analyzer mode. If the
purpose of the spectrum analysis being conducted is to determine RF levels arriving from
various PMP 320 units, dont forget to plan for collocated APs and remote towers that
might have a clear view of your spectrum analyzer. Remember, when the AP is actually
functioning with synchronization, the AP receiver will not hear any of the other APs.
For best results of the spectrum analyzer, change the AP channel bandwidth to 5MHz
prior to setting the AP into spectrum analyzer mode. Setting the AP channel bandwidth
to 5MHz increases the resolution of each scan and gives a more detailed image of the
RF environment.
MIB Support
PMP 320 AP and CSM MIB files are available on the Cambium Support website
(http://www.cambiumnetworks.com/support/pmp/software under PMP Enterprise MIBs).
Please ensure to review accompanying MIB guideline spreadsheet to understand
dependencies. Incorrect MIB usage may result in an unstable system.
AP DHCP Server
When operating in Layer 3 mode, in order for the AP to activate its DHCP server to
allocate IP addressing information, the DHCP Dynamic Pools IP space must not overlap
with the DHCP Static Pools IP space.

NETWORK MANAGEMENT
Cambium Networks Wireless Manager Release 3.0 Service Pack 3 Hot fix 1 may be used to
manage PMP 320 System Release e2.3 networks. Previous versions of Wireless Manager will
not properly discover PMP 320 System Release e2.3 devices. Wireless Manager may be
downloaded from the Cambium Support website at:
http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=1

SOFTWARE UPGRADE
Pre-requisites
CNUT Version 3.20.19 or later
CAP Version e2.1 or later ((PMP 320 System Release e2.1 or later)
CSM Version 6.5.1 or later (PMP 320 System Release e2.1 or later)

Reference Documentation
Software upgrade procedures are defined in the CNUT Online Help document found at:
http://www.cambiumnetworks.com/support/planning/index.php?cat=3&type=0
Software upgrade procedures are also defined in Chapter 2 (AP) and Chapter 3 (CSM) of the
PMP 320 Administration and Configuration Guide found at:

PMP 320 ADMINISTRATION AND CONFIGURATION GUIDE
Please refer to the PMP 320 Administration and Configuration Guide for details on system
configuration and operation. All PMP 320 documentation is available for download from the
Cambium support web site.

PMP 320 INSTALLATION GUIDE
Please refer to the PMP 320 Installation Guide for details on equipment installation. All PMP 320
documentation is available for download from the Cambium support web site.

ABBREVIATIONS
The following abbreviations may be used in these notes:
AAA
AP
BW
CAP
CID
CIR
CNUT
CPE
DSCP
DHCP
FTP
GHz
GUI
Authentication Authorization Accounting
Access Point Module
Bandwidth
Cluster Access Point
Connection Identifier
Committed Information Rate
Canopy Network Updater Tool
Customer Premises Equipment
Differentiated Services Code Point
Dynamic Host Configuration Protocol
File Transfer Protocol
Gigahertz
Graphical User Interface

HARQ
KHz
L2
L3
MAC
MCC
MCS
MIB
NAT
NTP
OID
PMP
QOS
RIP
SNMP
TOS
UGPS
UGS
UL
VDC
VoIP
WAN
WMAC
Hybrid Automatic Repeat reQuest
Kilohertz
Layer Two
Layer Three
Media Access Control (Ethernet address)
Multicast Channel Communication
Modulation and Coding State
Management Information Base
Network Address Translation
Network Time Protocol
Object Identifier for an object in a MIB
Point to Multi-Point
Quality of Service
Routing Information Protocol
Simple Network Management Protocol
Type Of Service
Universal Global Positioning System
Unsolicited Grant Service
UpLink
Volts Direct Current
Voice over Internet Protocol
Wide Area Network
Wireless Media Access Control

PMP 320 SERIES PRODUCT NOMENCLATURE

Table 12 includes PMP 320 Series model numbers, product names and supported frequencies.
The 3.5 GHz and 3.65 GHz products visually appear identical to one another. The labels on the
sides of the units provide the proper identifiers for the APs and CSMs.
Table 12: Product Nomenclature
Licensed
Spectrum
Ranges
System Name AP Name CSM Name AP Model
Number
CSM
Model
Numbers
Frequencies
Supported
3.3 to 3.4
GHz
PMP 35320
CAP
35320
CSM 35320 3530APC
3530SM
3530SMC
3.3 to 3.6 GHz
3.4 to 3.6
GHz
3.6 to 3.8
GHz
PMP 36320
CAP
36320
CSM 36320 3630APC
3630SM
3630SMC
3.6 to 3.8 GHz
(Includes 3.65
GHz)


FEEDBACK ON DOCUMENTATION
Please send your feedback on this product documentation to:
support@cambiumnetworks.com

TECHNICAL SUPPORT
If you encounter any technical issues with the product, please capture the event logs at both the
CAP and CSM. It may provide useful debug help for you and for the Technical Support team.
Prior to contacting the PMP 320 technical support team please do the following:

1
Search this document and the software release notes of supported releases
2
Visit the support website
3
Ask for assistance from the Cambium product integrator
4
Gather information from affected units such as:
The IP addresses and MAC addresses
The software releases
The configuration of software features
Any available diagnostic downloads
5
Escalate the problem by emailing or telephoning support


CONTACTING CAMBIUM NETWORKS
Support website: http://www.cambiumnetworks.com/support
Main website: http://www.cambiumnetworks.com
Sales inquiries: solutions@cambiumnetworks.com
Support inquiries: support@cambiumnetworks.com
Telephone Numbers:
North America: +1 866-961-9288
Latin/Central America: +420 533 336 946
Europe, Middle East or Africa: +44 203 0277499
Asia/Pacific: +420 533 336 946
Full list:
http://www.cambiumnetworks.com/support/technical.php

Address:
Cambium Networks
1299 E Algonquin Road
Schaumburg, IL 60196

Resolved Issues

Refer to the following tables for PMP 320 system issues that have been fixed since software
release e2.0.
Table 13: Resolved Issues in e2.3
Product Ref # Description Discussion and Recommendations
PMP 320
CAP
10005 Enabling security for a service
flow (using mode External
AAA) eventually causes traffic
flow to cease
Fixed in e2.3. When using External AAA as
the AP operation mode, if security is enabled
for a service flow, the flow of data between
the devices using the service flow continues
normally.
PMP 320
CAP
10190 Next Navigation arrow on
Connected CPEs page not
functional
Fixed in e2.3. Next arrow functions properly
to navigate to subsequent pages.
PMP 320
CAP
10194 GUI Display Issues for System
Uptime, System Time, and
Connected CPEs page
Fixed in e2.3. System Uptime, System Time,
and Connected CPE information is updated
properly in the AP GUI.
PMP 320
CAP
10160 MIB syntax entry for SNMP
object danSyncStatus does not
match description
Fixed in e2.3 MIB.
-syncStateNoSync(0) - Not in Sync
-syncStateSync(1) - In sync
-syncStateSync1PPSLost(2) - External sync
missing operating based on internal clock
PMP 320
CAP
1184 After upgrading the AP with the
Extended Range feature
enabled, the AP undergoes an
unsolicited reboot.
Fixed in e2.3. Upgrading an AP with the
Extended Range feature enabled does not
trigger an additional AP reboot.
PMP 320
CAP
10091 Internal AAA database lost
during upgrade
Fixed in e2.3. When upgrading an AP, the
Internal AAA database information is
retained from release to release.
PMP 320
CAP
1080 For 3.5MHz and 5MHz channel
bandwidths, the CSM may
experience difficulty achieving
registration for CSM RSSI
levels below -87dBm.
Fix verified in e2.3. The CPE can register at
RSSI levels >= 90 dBm.


Table 14: Resolved Issues in e2.2.2
PMP 320
CSM
1571 Add CSM VLAN functionality to
include VLAN Management ID
in the CSMs VLAN
Membership Table
The CSMs configured VLAN Management
ID may be added to the CSMs VLAN
Membership Table to allow management
traffic (tagged with same management VID
as the CSM) from devices situated below the
CSM (for example, a PC requesting DHCP
information from a server above the AP) to
flow through the 320 network.
PMP 320
CSM
1577 CSM resets with invalid URL
request
Fixed in e2.2.2. Invalid URL requests to the
CSM will result in redirection to the CSMs
login screen.
PMP 320
CAP
10098 AP resets after navigating
through provisioned service
flows pages
Fixed in e2.2.2. Navigating through multiple
pages of service flows and then clicking the
navigation menus does not affect device
operation.

PMP 320
CAP
1555504 With the Upper 3.65 feature
disabled on the AP, non-US
users are not able to set
operating frequencies in the
3.65-3.70 range using the
Center Frequency field on the
AP GUI.
Fixed in e2.2.1. PMP 320 operators outside
of the United States may now input upper
3.65 GHz band (3675 3700 MHz)
frequencies into the APs Center Frequency
(KHz) field (located in the AP GUI at AP
Configuration > Air Interface > WiMAX
Capabilities). This allows non-US operators
to transmit using upper 3.65 GHz band
frequencies without utilizing the APs
contention-based upper 3.65 GHz scanning
protocol (i.e. AP GUI parameter North
America: Upper 3.65 Scanning is set to
Disable).
All customers configuring operating
frequencies outside of the 3.675 3.700
GHz range should set the AP GUI parameter
North America: Upper 3.65 Scanning to
Disable.

For compliance with Section 90.7 of Part 90
of the United States FCC, US PMP 320
operators must use the restricted contention-
based scanning protocol when using
frequencies in the upper 3.65 GHz band.


PMP 320
CAP
1169 Traffic delivery issues with
routing protocols OSPF/EIGRP
(protocols which establish
adjacency relationships)
Fixed in e2.2. On the AP, ensure that
Forward Multicast on MCC Service flow is
set to Enable for Multicast-based routing
messaging to be sent properly on the PMP
320 downlink.
PMP 320
CSM
1133 CSM with 7MHz channel
bandwidth and Extended
Range enabled may randomly
reboot
Fixed in e2.2. CSMs configured with 7MHz
bandwidth and Extended Range enabled do
not randomly reboot.
PMP 320
CSM
1084 CSM Preferred AP List
behavior upon CSM loss of
registration
Fixed in e2.2. If the CSM loses registration
to an AP that is the highest priority AP in the
AP priority list, the CSM correctly selects the
highest priority AP available.
PMP 320
CSM
1082 AP Preferred List feature does
not work if the APs in the list
are on the same frequency and
Channel Bandwidth
Fixed in e2.2. If all APs in the CSMs BSID
List are configured with the same frequency
and channel bandwidth, The CSM adheres to
the configured list for AP scanning selection.

PMP 320
CAP
1164,
1165
AP Instability Resolution In certain networks, operators have
experienced AP instability, specifically AP
reboots. The issues causing these crashes
have been resolved in e2.1.3.
PMP 320
CAP
1160 Include Map Symbol 7 Option
for 65%/35% Downlink/Uplink
Ratio
Included in e2.1.3.
PMP 320
CAP
1161 Random AP GUI Lockup Fixed in e2.1.3.

PMP 320
CAP
1132 SNMP interface bug Fixed in e2.1.2


PMP 320
CSM
1142 Using UL HARQ causes AP
crash
Fixed in e2.1.1
PMP 320
CAP
1120 UL packet loss in noisy RF
environments
Improved in e2.1.1
PMP 320
CAP
1121 Increased UL packet loss and
CSM Tx power not adjusted to
target
Improved in e2.1.1
PMP 320
CAP
1122 General AP GUI
slowness/timeout
Improved in e2.1.1
PMP 320
CSM
1104 CSM converted from NAT
mode to Bridge mode with
DHCP enabled does not
respond to DHCP offer
Fixed in e2.1.1
PMP 320
CSM
1145 ARP leakage results in CSM
performance degradation
Fixed in e2.1.1
PMP 320
CAP
15903 AP Bridge Table displays
incomplete information
Fixed in e2.1.1

PMP 320
CAP
1072 AP Crashed During CSM
Upgrade
Fixed in e2.1
PMP 320
CAP
1010 AP Web Server Lock-up due to
unicast packet destined for
WMAC
Fixed in e2.1
PMP 320
CAP
990 AP stability Improvements have been made to address
unplanned reboots of the AP
PMP 320
CSM
1099 Degraded CINR Fixed in e2.1


Known Open Issues

Known open issues for Release e2.3 are listed in Table 21. For Layer 3 convergence mode-
specific open issues, reference Table 22.
Table 21: Release e2.3 Open Issues
Product
Family
Ref #
Description Discussion and Recommendations
PMP 320
CAP
10228 AP GUI downlink RSSI is
refreshed every 60 seconds
In Release e2.3, the APs GUI downlink
RSSI value is only refreshed every 60
seconds (all other information is refreshed
every 2 seconds). The frequency of the
refresh of downlink RSSI information is to be
increased in a later release.
PMP 320
CAP
10178 If an AP has been upgraded to
e2.3, upon downgrading then re-
upgrading the AP software from
a pre-e2.3 release to e2.3, non-
default usernames and
passwords added in the pre-
e2.3 release are deleted.
This behavior is only exhibited when an AP
with e2.3 software is downgraded,
reconfigured with new
usernames/passwords, and then re-
upgraded.
PMP 320
CSM
17801 During software downgrade,
CSM may become a CNUT
generic device
To resolve the change of the CSMs
representation in CNUT operators may right-
click on the element and select Change
Network Element Type to set the device
type back to PMP 320 CSM. Alternatively,
the generic device may be removed from the
CNUT network and re-added as a PMP 320
CSM device.
PMP 320
CSM
17727,
1632
After software upgrade or
downgrade from CSM version
8.1.4 (System Release e2.2.2)
to 8.0.0 (System Release
e2.2.1), CNUT may report the
operation as unsuccessful
If downgrading from CSM version 8.1.4
(System Release e2.2.2) to 8.0.0 (System
Release e2.2.1), operators may need to
refresh the CSM GUI or reboot the CSM in
order to see the update in the software
version. If the GUI refresh or CSM reboot
does not result in an updated display of the
CSM software version, reinitiate the CNUT
downgrade.
PMP 320
CSM
1435 CSM DHCP Client List not
persistent across CSM reboots
After the CSM has successfully leased IP
address information to a device situated
below it, if the CSM is rebooted the CSM
DHCP Client List will not display the clients
that have successfully received IP
addressing information. If the DHCP clients
re-request IP addressing information from
the CSM, the clients are displayed again in
the CSM DHCP Client List.

Product
Family
Ref #
PMP 320
CAP
1220 Layer 2 Classification Rule
based on source MAC address
is not functional in downlink
direction
Operators may configure Layer 2
Classification Rule profiles to instead use
type IP TOS, IP Masked Source Address,
IP Masked Destination Address,
Destination MAC Address, VLAN Priority,
or VLAN ID.
PMP 320
CAP
1175 QoS Profiles Lost when
Downgrading from e2.3 to any
Previous Software Release
The following procedure should be
executed prior to upgrading to e2.3 to
ensure that QoS and service flow
information may be reinstated in case of
a downgrade from e2.3 to a previous
software release.
Before upgrading from a pre-e2.3
release to e2.3, save a configuration
restore point on the APs
Administration > Configuration
Control GUI page. If it is required that
the network is reverted back to a pre-2.3
release, the configuration control point
may be restored, and all QoS and
service flow configuration will be
restored. For pre-e2.3 software
releases only, if all configuration restore
points are already populated, overwrite
one of them with the APs current
configuration without changing the
restore points name. Otherwise, an
unused configuration control slot may be
used. This naming behavior is only
present in pre-e2.3 software releases
(when using e2.3, existing configuration
control restore points may be overwritten
with new names).
PMP 320
CSM
1178 Inability to Create More Than
One Uplink Service Flow with
HARQ Enabled
When creating uplink service flows on the
CSM the user may only create one uplink
service flow with HARQ enabled. Operators
requiring more than one uplink service flow
with HARQ enabled should deploy CSMs
with software release 7.1.3.
PMP 320
CSM
1162 In CSM installations with poor
RSSI conditions (close to radio
sensitivity, -94 dBm), the CSM
may display incorrect values for
Zone CINR channel 0
In CSM installations with poor RSSI
conditions, the CSM may display on its
homepage invalid values for Zone CINR
channel 0 resulting in radio link MCS states
that are not in alignment with the Zone CINR
that is reported (see Tables 12-8 and 12-9 in
the PMP 320 Administration and
Configuration Guide). Operators are
encouraged to evaluate potential physical
interferers and also to relocate CSM units for
better signal quality.

Product
Family
Ref #
PMP 320
CAP
1114 Layer 2 AP Requires a Valid
Default Gateway Configuration
to maintain accessibility to AP
GUI via Ethernet
If the AP does not have a valid default
gateway IP address configured, while traffic
will continue to pass through the system,
users may lose connectivity to the AP
management GUI via Ethernet. Configuring
a valid default gateway IP address in the AP
and resetting the unit will reestablish
connectivity from a directly connected PC to
the APs management GUI.

Table 22: Release e2.3 Open Issues Layer 3-specific
Product
Family
Ref #
PMP 320
CAP
1151 NTP client must be enabled for
AP to release more than 1 IP
from its wireless interface DHCP
server
For deployments using the AP to serve more
than one IP address DHCP address for CSM
wireless interfaces, the APs NTP server
must be enabled. If the NTP server is not
configured on the AP, the CSMs will register
but only one CSM will receive an IP address
for its wireless interface from the APs DHCP
server.
PMP 320
CAP
1168 Data traversing an IPSEC VPN
tunnel via a Layer 3 NAT AP
may be dropped after five
minutes
There are two ways to reestablish IPSEC
VPN tunnel traffic when this issue is
encountered. One way is to reset the edge
routers in the network or the SM which is
carrying the VPN traffic. Another way is to
halt the VPN traffic through the PMP 320
link, wait 5 minutes, then initiate the VPN
traffic again.
PMP 320
CSM
1058 Game invite from PS3 below a
CSM to a target PS3 above the
AP fails to connect
This is a known issue with the type of NAT
device the PS3 is represented. Currently
duplicated in Cambium labs. Please refer to
Field Service Bulletin 9020: Playstation 3
Communication Issue for more details.

PMP 320 Release Notes E2.3 Issue1 PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PMP 320 Release Notes E2.3 Issue1 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

PMP 320 Administration and Configuration Guide

Anda mungkin juga menyukai