PMP 320 Release Notes e2.3

8/9/2019 PMP 320 Release Notes e2.3

1/68

PMP 320 Administration and Configuration Guide

Cambium

PMP 320

Release Notes

System Releasee2.3

PMP320RELEASENOTES April 2012© 2012 Cambium Networks. All Rights Reserved.


2/68

PMP 320 Module Essential Information

The following tables may be referenced for information regarding module management access andfactory default procedures.

AP

Default IP Address forManagement GUI Access

192.168.2.101

Default AdministratorUsername

admin

Default AdministratorPassword

admin

Resetting to FactoryDefaults (2 options)

1. Restore Configuration Control Index 1 located in the AP GUIat Administration > Configuration Control then reboot theradio.

2. While powered, insert a default plug into the radio‟s RJ11 portfor one minute, then remove. When the radio is rebooted, itis configured with the factory defaults.

CSM

Default IP Address for

Management GUI Access

10.1.1.254

Default AdministratorUsername

administrator

Default AdministratorPassword

cambium

Previous to CSM software version f12b00-v8.1.4, theCSM‟s default administrator password was „motorola‟. If afactory default procedure is initiated for a CSM withsoftware version >= f12b00-v8.1.4 which is still

configured with the default password of „motorola‟, thedefault administrator password will be changed to„cambium‟.

Resetting to FactoryDefaults (2 options)

1. Restore the factory default settings by using the CSM GUIrestore function located at Management > Restore Default,then reboot the radio.

2. Use the Reset factory default tool, which may be downloadedfrom the Cambium support website.


3/68

Accuracy

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

Copyrights

This document, Cambium Networks products, and 3rd Party Software products described in this document may include or describe copyrighted

Cambium Networks and other 3rd 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 3rd 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 copyrightedmaterial. 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 modifiedin any manner without the express written permission of Cambium Networks. Furthermore, the purchase of Cambium Networks products shallnot be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applicationsof Cambium Networks or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises byoperation 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 ordocumentation 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 agreementonly and may be used only in accordance with the terms of such an agreement.

High Risk Materials

Components, units, or 3rd 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 NuclearFacilities, 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.


4/68


5/68

PMP 320 Release e2.3 Release Notes

Issue 1, April 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


6/68



Introduction

This document provides information for the Cambium Networks PMP 320 product, softwarerelease e2.3.

To ensure that al l of the features of the PMP AP and CSM are avai lable upo n deployment,

be sure to up grade the mo dule softw are to the latest release avai lable at:

http://www.cambiumnetworks.com/support/pmp/software/

The following procedure should be executed prior to upgrading to e2.3 to ensure thatQoS and service flow information may be reinstated in case of a downgrade from e2.3 toe2.2.2.

Before upgrading from e2.2.2 to e2.3, save a configuration restore point on the AP‟sAdministration > Configuration Control GUI page. If it is required that the network isreverted back to a pre-2.3 release, the configuration control point may be restored, andall QoS and service flow configuration will be restored. For pre-e2.3 software releasesonly, if all configuration restore points are already populated, overwrite one of them withthe AP‟s current configuration without changing the restore point’ s name. Otherwise, anunused configuration control slot may be used. This naming behavior is only present inpre-e2.3 software releases (when using e2.3, existing configuration control restore pointsmay be overwritten with new names).

If an AP has been upgraded to e2.3, upon downgrading then re-upgrading the APsoftware from a pre-e2.3 release to e2.3, non-default usernames and passwords addedin the pre-e2.3 release are deleted. This behavior is only exhibited when an AP with e2.3software 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_e 3

NEW ACCESS POINT HARDWARE NOTIFICATIONS

IMPORTANT – PMP 320 Access Points with Tanapa Numbers 3530CBA or 3630CBAmust NOT have their software downgraded FROM THE FACTORY VERSION (e2.1.1).

http://www.cambiumnetworks.com/support/pmp/software/http://www.cambiumnetworks.com/support/pmp/software/http://www.cambiumnetworks.com/support/pmp/software/


7/68



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 Numberis used to indicate the hardware version of the board. The currently shipping hardwareversions 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 withthe Tanapa Numbers listed above will result in a locked, inaccessible radio that must bereturned to Cambium Networks for repair.

RELEASE HIGHLIGHTS

Improved Compatibility between UGPS Synchronized APs and CMM4 GPSSynchronized 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 upgradedto Software Release e2.3, APs that are synchronized by a UGPS module and APs thatare synchronized by a CMM4 will transmit at the same time, thereby eliminating noisereceived from nearby transmitting APs.

Expanded AP Performance Statistics

The AP‟s performance statistics have been expanded to include MCS (Modulati on andCoding Scheme)-based statistical views as well as HARQ (Hybrid Automatic RepeatreQuest) and Ethernet (wired interface) information. See section AP Statistics or moreinformation.

Frame Utilization Monitoring Updates

In Release e2.3, the AP‟s Frame Utilization monitoring tool has been updated to includebetter customization of data collection and additional statistics related to MCS(Modulation and Coding Scheme) states, slot usage, and throughput. See section FrameUtilization Monitoring for feature information and operating procedures.

AP STATISTICS

The PMP 320 AP contains network statistics and diagnostics that are available in the GUIin the Performance Monitor menu which may be used to analyze and troubleshootnetwork performance and operation.

Access Point Radio Info Menu

The AP‟s Radio Info menu displays important radio link information for each registeredsubscriber.

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


8/68



RSSI 0:

..

.1.3.6.1.4.1.32584.1.8.2.1.4.100.237.87.64.0.156.0

In this example, is represented in the above OID as“ 100.237.87.64.0.156 ” and is represented as “ 0 ”

RSSI 2:

..

.1.3.6.1.4.1.32584.1.8.2.1.4.100.237.87.64.0.156.2

In this example, is represented in the above OID as“ 100.237.87.64.0.156 ” and 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 receiveantennas (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 levelof signal as it is receiving an unadulterated (vertical) signal. In an environment wherethere is a lot of multipath or obstructions, the RSSI values will be much closer as the AP‟s antennas are receiving at a more consistent level.

Figure 1 AP Radio Info

Table 1 AP Radio Info Attributes

Attribute Meaning/SNMP Information

CPE MACAddress

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 AP‟s Main antenna. Referto the PMP 320 Link Budget Table available on the Cambium support website formore information on how the measured RSSI relates to the system‟s linkperformance.

Name danBsUlChannelRssiStream0

OID .1.3.6.1.4.1.32584.1.8.2.1.4

MIB DAN-BASIC-MIB-ADMIN

Syntax Integer32


9/68




Access read-only

Indexes danBsUlChannelMac, danBsUlChannelRadioIndex

Descr Measured stream-0 RSSI (reports RSSI 0 valuewhen using danBsUlChannelRadioIndex 0)

Uplink,RSSI 2

The RSSI represents the Received Signal Strength Indicator, which is ameasurement of the power level being received by the AP‟s Diversity antenna.Refer to the PMP 320 Link Budget Table available on the Cambium supportwebsite for more information on how the measured RSSI relates to the system‟slink performance.

Name danBsUlChannelRssiStream0

OID .1.3.6.1.4.1.32584.1.8.2.1.4


Syntax Integer32

Access read-only

Indexes danBsUlChannelMac, danBsUlChannelRadioIndex

DescrMeasured stream-0 RSSI (reports RSSI 2 valuewhen using danBsUlChannelRadioIndex 2)

Uplink,CINR

The CINR represents the AP‟s receive Carrier to Interference Noise Ratio, which isan 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 availableon the Cambium support website for more information on how the measured CINRrelates to the system‟s link performance.

Name danBsUlChannelCinrStream0

OID .1.3.6.1.4.1.32584.1.8.2.1.5MIB DAN-BASIC-MIB-ADMIN

Syntax Integer32

Access read-only

IndexesdanBsUlChannelMac,danBsUlChannelRadioIndex

DescrMeasured stream-0 CINR

Uplink,MCS

The MCS represents the Modulation and Coding Scheme used for the systemuplink. This state and its associated throughput capabilities, are based on the PMP320 system link budgets, which can be referenced in the PMP 320 Link BudgetTable available on the Cambium support website

Name danBsMcsStateUI

OID .1.3.6.1.4.1.32584.1.8.16.1.5


SyntaxINTEGER {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


10/68




Indexes danBsMcsMacAddr

Descr MCS State in the Uplink.

Downlink,RSSI

The RSSI represents the Received Signal Strength Indicator, which is ameasurement of the power level being received by the CPE‟s antenna. Refer tothe PMP 320 Link Budget Table available on the Cambium support website formore information on how the measured RSSI relates to the system‟s linkperformance.

Name danBsDlChannelRssiStream0

OID .1.3.6.1.4.1.32584.1.8.3.1.3


Syntax Integer32

Access read-onlyIndexes danBsDlChannelMac

Descr Reported RSSI Stream-0

Downlink,CINR

The CINR represents the CPE‟s receive Carrier to Interference Noise Ratio, whichis 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 themeasured CINR relates to the system‟s 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


11/68




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 systemdownlink. This state and its associated throughput capabilities, are based on thePMP 320 system link budgets (see the PMP 320 Link Budget Table available onthe Cambium support website).

Name danBsMcsStateDl


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 AP‟s Traffic Info menu displays details about the management traffic received andsent via the AP‟s wired (Ethernet) and wireless (radio) interfaces. It is important to notethat these values do not represent the actual RF link data throughput – to monitor actualRF throughput to the CPE operators may reference the Status menu of the CPE GUIunder WIMAX RX and WIMAX TX. This throughput data may also be accessed viaSNMP queries (reference the PMP 320 CPE MIB file for OID information) or via the AP‟sDownlink MCS Stats, Uplink MCS Stats, and HARQ Statistics menus.

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

Rx Octets:

.

.1.3.6.1.2.1.2.2.1.10.3

In this example, is represented as “ 3” (wired interface)


12/68



Figure 2 AP Traffic Info

Table 2 AP Traffic Info Attributes

Attribute Meaning / SNMP Details

Interface The Interface represents the AP‟s internal index of the interface.

Description Wired means that the data displayed is for the AP‟s Ethernet interface.

IP Address /Mask

The IP Address / Mask field represents the IP address and subnet maskconfigured for the interface.

Rx Octets The Rx Octets represents the number of management octets that havebeen received on the interface, including those containing framinginformation.

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

DescrThe total number of octets received onthe interface, including framingcharacters

Rx UnicastPackets

The Rx Unicast represents the number of management unicastpackets 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

DescrThe number of subnetwork-unicastpackets delivered to a higher-layerprotocol.

Rx Non-UnicastPackets

The Rx Non-Unicast Packets represents the number ofmanagement non-unicast packets (broadcast and multicast) thathave been received on the interface.


13/68




Name ifInNUcastPkts

OID .1.3.6.1.2.1.2.2.1.12

MIB MIB2-DAN-MIB-ADMINSyntax 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 inboundmanagement octets have been discarded on the interface. Somepackets may have been discarded to increase buffer space.

Name ifInDiscardsOID .1.3.6.1.2.1.2.2.1.13


Syntax Counter

Access read-only

Indexes ifIndex

Descr

The number of inbound packets whichwere chosen to be discarded eventhough no errors had been detected toprevent their being deliverable to ahigher-layer protocol. One possiblereason for discarding such a packetcould be to free up buffer space.

Tx Octets The Tx Octets represents the number of management octets that havebeen transmitted on the interface, including those containing framinginformation.

Name ifOutOctets

OID .1.3.6.1.2.1.2.2.1.16


Syntax Counter

Access read-only

Indexes ifIndex

DescrThe total number of octets transmittedout of the interface, including framing

characters.

Tx UnicastPackets

The Tx Unicast represents the number of management unicastpackets that have been transmitted on the interface.

Name ifOutUcastPkts

OID .1.3.6.1.2.1.2.2.1.17


Syntax Counter


14/68




Access read-only

Indexes ifIndex

Descr

The total number of packets thathigher-level protocols requested betransmitted to a subnetwork-unicastaddress, including those that werediscarded or not sent.

Tx Non-UnicastPackets

The Tx Non-Unicast Packets represents the number ofmanagement non-unicast packets (broadcast and multicast) thathave 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 thathigher-level protocols requested betransmitted to a non- unicast (i.e., asubnetwork-broadcast or subnetwork-multicast) address.

Tx Discards The Tx Discards represents the number of outboundmanagement octets have been discarded on the interface. Someof these packets may have been discarded to increase bufferspace.

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 whichwere chosen to be discarded eventhough no errors had been detected toprevent their being transmitted. Onepossible reason for discarding such apacket could be to free up buffer space.

Access Point Connected CPEs Menu

The AP‟s Connected CPEs menu provides a display of all the CPEs that have beenallowed network entry by the AP. It also allows operators to control CPE registration viathe Deregister CPE and Reset CPE buttons.


15/68



To retrieve statistical information via SNMP, an index must be appended to the SNMPOID to distinguish for which MAC address CID information is being retrieved. Forexample, 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:..

.1.3.6.1.4.1.32584.1.16.2.1.1.2.100.237.87.64.0.156.0

In this example, is represented in the above OID as“ 100.237.87.64.0.156 ” and is represented as “ 0 ” (wireless interface).

Figure 3 AP Connected CPEs

Figure 4 AP Connected CPEs Attributes


Number ofRegisteredCPE’s

The current count of the number of CPEs that have successfully enteredthe network.

Name wmanIf2BsRegisteredSsCount

OID .1.3.6.1.4.1.32584.1.16.2.1.2.10


Syntax Unsigned32

Access read-only

DescrThe 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 MACmessaging.

Name wmanIf2BsSsBasicCid

OID .1.3.6.1.4.1.32584.1.16.2.1.2.1.1.2


Syntax WmanIf2TcCidType

Access read-only


16/68




Indexes wmanIf2BsSsMacAddress, ifIndex

Descr

The value of this object indicates theSS'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

DescrThe value of this object indicates theprimary CID of the SS received from theRNG-RSP message.

Active Service Flow Stats, Active Service Flows Menu

The AP‟s 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 serviceflow counters.

To retrieve statistical information via SNMP, an index must be appended to the SNMP

OID to distinguish for which MAC address CID information is being retrieved. Forexample, to retrieve the Packet Count for a CPE with MAC address 64:ed:57:40:00:9cand SF ID 5000, perform an SNMP get on the following OID:

Packet Count:

..

.1.3.6.1.4.1.32584.1.8.1.1.4.100.237.87.64.0.156.5000

In this example, is represented in the above OID as“ 100.237.87.64.0.156 ” and is represented as “ 5000 ” (service flow ID)


17/68



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 > ServiceFlows > 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.

PacketCount

The Packet Count represents the number of packets transmitted using the serviceflow.

Name danBsUsageRecordEntry.danBsUsageRecordPcktsCount

OID .1.3.6.1.4.1.32584.1.8.1.1.4


Syntax Unsigned32

Access read-only

Indexes danBsUsageRecordMacAddr, danBsUsageRecordSfId

DescrTotal packet count for the given MSS and SF ID

BytesCount

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


18/68




Indexes danBsUsageRecordMacAddr, danBsUsageRecordSfId

Descr Total bytes count for the given MSS and SF ID

PacketsDropped

The Packets Dropped represents the number of packets dropped due totransmission issues.

Name danBsUsageRecordPcktsDropped

OID .1.3.6.1.4.1.32584.1.8.1.1.6


Syntax Unsigned32

Access read-only

IndexesdanBsUsageRecordMacAddr,danBsUsageRecordSfId

DescrTotal packets dropped for the given MSS and SFID

BytesDropped

The Bytes Dropped represents the number of bytes dropped due to transmissionissues.

Name danBsUsageRecordBytesDropped

OID .1.3.6.1.4.1.32584.1.8.1.1.7


Syntax Unsigned32

Access read-only

IndexesdanBsUsageRecordMacAddr,danBsUsageRecordSfId

Descr Total bytes dropped for the given MSS and SF ID

Active Service Flow Stats, Downlink MCS

The AP‟s Downlink MCS menu displays information about the amount of data passed ateach MCS (Modulation and Coding Scheme) state per registered CPE. This menu isuseful for determining if CPEs are performing at the level they should be, based on thePMP 320 link budgets (see the PMP 320 Link Budget Table available on the Cambiumsupport website ).

To retrieve statistical information via SNMP, an index must be appended to the SNMPOID to distinguish for which MAC address CID information is being retrieved. For

example, to retrieve the byte count for 64QAM 5/6 for a CPE with MAC address64: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:

..

.1.3.6.1.4.1.32584.1.8.6.1.3.100.237.87.64.0.156.5000

In this example, is represented in the above OID as“ 100.237.87.64.0.156 ” and is represented as “ 5000 ” (service flow ID)


19/68



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 statsare displayed

CPE SFID The CPE SFID is the AP-assigned service flow ID used for the downlinkservice 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 (Aor B). Refer to section the PMP 320 Link Budget Table available on theCambium 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 performsMRC: MRC stands for Maximal Ratio Combining which is a form ofreceive diversity. With this technique, two receivers and their associatedantennas receive the transmitted signal. The two received signals arecombined into a single higher quality signal. This technique increasesthe link budget of a system.

Name danBsDlMcs64Qam56MimoBCount


20/68




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 thedownlink, 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

IndexesdanBsDlMcsMacAddr,danBsDlMcsSfId

DescrTotal number of bytes sent in thedownlink, in MCS state '64QAM 5/6MIMO A'.


OID .1.3.6.1.4.1.32584.1.8.6.1.5


Syntax Unsigned32

Access read-only




OID .1.3.6.1.4.1.32584.1.8.6.1.6






21/68





OID .1.3.6.1.4.1.32584.1.8.6.1.7

MIB DAN-BASIC-MIB-ADMINSyntax Unsigned32

Access read-only




OID .1.3.6.1.4.1.32584.1.8.6.1.8


Syntax Unsigned32

Access read-only





Syntax Unsigned32

Access read-only



Name danBsDlMcsQpsk34MimoACount

OID .1.3.6.1.4.1.32584.1.8.6.1.10


Syntax Unsigned32

Access read-only


Descr Total number of bytes sent in the


22/68




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

Name danBsDlMcsQpsk12MimoACount

OID .1.3.6.1.4.1.32584.1.8.6.1.11


Syntax Unsigned32

Access read-only


DescrTotal number of bytes sent in thedownlink, in MCS state 'QPSK 1/2MIMO A'.

Active Service Flow Stats, Uplink MCS

The AP‟s Uplink MCS menu displays information about the amount of data passed ateach MCS (Modulation and Coding Scheme) state per registered CPE. This menu isuseful for determining if CPEs are performing at the level they should be, based on thePMP 320 link budgets (see the PMP 320 Link Budget Table available on the Cambiumsupport website).

To retrieve statistical information via SNMP, an index must be appended to the SNMPOID to distinguish for which MAC address CID information is being retrieved. Forexample, to retrieve the byte count for 64QAM 5/6 for a CPE with MAC address64: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:

..

.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“ 100.237.87.64.0.156 ” and is represented as “ 5001” (service flow ID)

Figure 7 Uplink MCS Stats


23/68



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 websitefor more information.

Name danBsUlMcs64Qam56Count

OID .1.3.6.1.4.1.32584.1.8.7.1.3



Indexes danBsUlMcsMacAddr, danBsUlMcsSfId

DescrTotal number of bytes sent in theuplink, in MCS state '64QAM 5/6'.


OID .1.3.6.1.4.1.32584.1.8.7.1.4


Syntax Unsigned32

Access read-only




OID .1.3.6.1.4.1.32584.1.8.7.1.5


Syntax Unsigned32

Access read-only


Descr Total number of bytes sent in theuplink, in MCS state '64QAM 2/3'.


OID .1.3.6.1.4.1.32584.1.8.7.1.6


Syntax Unsigned32


24/68



Attribute Meaning

Access read-only


Descr Total number of bytes sent in theuplink, 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


Name danBsDlMcs16Qam12Count

OID .1.3.6.1.4.1.32584.1.8.7.1.8


Syntax Unsigned32

Access read-only



Name danBsDlMcsQpsk34CountOID .1.3.6.1.4.1.32584.1.8.7.1.9


Syntax Unsigned32

Access read-only


DescrTotal number of bytes sent in theuplink, 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


DescrTotal number of bytes sent in theuplink, in MCS state 'QPSK 1/2'.


25/68



Active Service Flow Stats, HARQ

The AP‟s HARQ Statistics menu displays information about the HARQ mechanismstatistics for each CPE‟s HARQ-enabled service flow. This menu is useful for analyzingHARQ feedback to determine the effectiveness of the protocol for each service flow.

To retrieve statistical information via SNMP, an index must be appended to the SNMPOID to distinguish for which MAC address CID information is being retrieved. Forexample, to retrieve the HARQ ACK count for CPE with MAC address 64:ed:57:40:00:9cand SF ID 5000, perform an SNMP get on the following OID:

HARQ ACK Count:

..

.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“ 100.237.87.64.0.156 ” and is represented as “ 5000 ” (service flow ID)

Figure 8 AP HARQ Statistics


26/68



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 andthroughput 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

IndexesdanHarqStatsMacAddr,danHarqStatsSfId

DescrNumber of ACK's.

NACKs When negative ACKS are being received (Nacks is increasing), this indicates thatthe HARQ transmitter has reached the maximum number of retransmissions withoutreceiving an ACK (data was not properly decoded). In this case, investigatepossible 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


DescrNumber of NACK's.

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

Name danHarqStatsDiscards

OID .1.3.6.1.4.1.32584.1.8.11.1.10



27/68





Access read-only


DescrNumber of transmission discards

Wired Interface Statistics Menu

The AP‟s Ethernet Statistics Menu displays information about the data received(destined for the AP‟s RF interface) and transmitted from the AP‟s 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


EthernetPackets:Tx, # ofBytes

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

DescrTotal bytes transmitted.

Ethernet

Packets:Tx, # ofPackets

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.


28/68




EthernetPackets:Tx, # ofPacketswith 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

DescrTotal number of error packets

EthernetPackets:Tx, # ofDroppedPackets

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

DescrTotal number of packets dropped

EthernetPackets:

Rx, # ofBytes

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

DescrTotal bytes received

EthernetPackets:Rx, # of

Packets

The number of packets that were received on the wired interface

Name danEthRxTotalPacketsOID .1.3.6.1.4.1.32584.1.8.13.6


Syntax Unsigned32

Access read-only

DescrTotal packets received


29/68




EthernetPackets:Rx, # of

Packetswith error

The number of received packets that contained errors that were dropped on thewired interface

Name danEthRxPacketErrors

OID .1.3.6.1.4.1.32584.1.8.13.8


Syntax Unsigned32

Access read-only

DescrTotal number of packets received witherrors

EthernetPackets:

Rx, # ofDroppedPackets

The number of dropped packets that did not contain errors (possibly dropped toincrease buffer space)

Name danEthRxDroppedPackets

OID .1.3.6.1.4.1.32584.1.8.13.9


Syntax Unsigned32

Access read-only

DescrTotal number of received packetsdropped

Ethernet

Packets:Rx, # ofBroadcastPackets

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

DescrTotal number of broadcast packetsreceived

Figure 10 AP Ethernet VLAN Rx Packets Statistics


30/68



Table 8 AP Ethernet VLAN Rx Packets Attributes


Ethernet Rx: IP

Packets, withVLAN 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

DescrTotal number of received IP packets, withVLAN tag

Ethernet RX: IP

Packets, withVLAN 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

DescrTotal number of received IP packets, withVLAN tag, dropped

Ethernet Rx: IPPackets,without VLANtag, 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

DescrTotal number of received IP packets,without VLAN tag

Ethernet Rx: IPPackets,

without VLANtag, Dropped

The number of IP packets received on the wired interface that were not tagged withVLAN information which were dropped (possibly to increase buffer space)

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,


31/68




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 withVLAN information

Name danEthRxNonIpPacketsVlan

OID .1.3.6.1.4.1.32584.1.8.13.12


Syntax Unsigned32

Access read-only

DescrTotal 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 withVLAN information which were dropped (possibly to increase buffer space)

Name danEthRxNonIpPacketsVlanDropped

OID .1.3.6.1.4.1.32584.1.8.13.16


Syntax Unsigned32

Access read-only

DescrTotal number of received Non-IP packets,with VLAN tag, dropped

Ethernet Rx:Non-IP Packets,without VLANtag, Received

The number of layer 2 packets received on the wired interface that were not taggedwith VLAN information

Name danEthRxNonIpPacketsNonVlan

OID .1.3.6.1.4.1.32584.1.8.13.13


Syntax Unsigned32

Access read-only

DescrTotal number of received Non-IP packets,without VLAN tag

Ethernet Rx:Non-IP Packets,without VLANtag, Dropped

The number of layer 2 packets received on the wired interface that were not taggedwith 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


32/68




Access read-only

Descr

Total number of received Non-IP packets,

without VLAN tag, dropped

Figure 11 AP QoS Rx Packet Classification Statistics

Table 9 AP QoS Rx Packet Classification Statistics Attributes


Ethernet Rx: IPPackets, ToS

The number of packets that contained a TOS value that matched a configuredclassification profile rule. These packets will be transmitted over the wirelessinterface using the QoS profile configured in the matching classification profile

Name danEthRxClsTos

OID .1.3.6.1.4.1.32584.1.8.13.21



DescrTotal number of received packets,classified by TOS

Ethernet Rx: IPPackets, IP,Destination

The number of packets that contained a destination IP that matched a configuredclassification profile rule. These packets will be transmitted over the wirelessinterface 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

DescrTotal number of received packets,classified by destination IP

Ethernet Rx: IPPackets, IP,Source

The number of packets that contained a source IP that matched a configuredclassification profile rule. These packets will be transmitted over the wirelessinterface using the QoS profile configured in the matching classification profile.


33/68




Name danEthRxClsSrcIp

OID .1.3.6.1.4.1.32584.1.8.13.20MIB DAN-BASIC-MIB-ADMIN

Syntax Unsigned32

Access read-only

DescrTotal number of received packets,classified by source IP

Ethernet Rx: IPPackets, VLAN,ID

The number of packets that contained a VLAN ID value that matched a configuredclassification profile rule. These packets will be transmitted over the wirelessinterface using the QoS profile configured in the matching classification profile.

Name danEthRxClsVlanId

OID .1.3.6.1.4.1.32584.1.8.13.22


Syntax Unsigned32

Access read-only

DescrTotal number of received packets,classified by VLAN Id

Ethernet Rx: IPPackets, VLAN,Priority

The number of packets that contained a VLAN priority value that matched aconfigured classification profile rule. These packets will be transmitted over thewireless interface using the QoS profile configured in the matching classificationprofile.

Name danEthRxClsVlanPriority

OID .1.3.6.1.4.1.32584.1.8.13.23


Syntax Unsigned32

Access read-only

DescrTotal number of received packets,classified by VLAN priority

Ethernet Rx: IPPackets, MAC,Destination

The number of packets that contained a destination MAC address that matched aconfigured classification profile rule. These packets will be transmitted over thewireless interface using the QoS profile configured in the matching classification

profile.

Name danEthRxClsDestMac

OID .1.3.6.1.4.1.32584.1.8.13.24


Syntax Unsigned32

Access read-only


34/68




DescrTotal number of received packets,classified by destination MAC

Ethernet Rx: IPPackets, MAC,Source

The number of packets that contained a source MAC address that matched aconfigured classification profile rule. These packets will be transmitted over thewireless interface using the QoS profile configured in the matching classificationprofile.

Name danEthRxClsSrcMac

OID .1.3.6.1.4.1.32584.1.8.13.25


Syntax Unsigned32

Access read-only

Descr

Total number of received packets,

classified by source MAC

FRAME UTILIZATION MONITORING

The Frame Utilization table located at the AP‟s Performance Monitor > FrameUtilization menu may be used to calculate frame usage on the PMP 320 downlink anduplink. 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 CodingScheme) state?

Sector capacity – does the AP have enough MAP slots available tohandle control messaging for all registered CPEs?

Network expansion feasibility- based on the RF link utilization, what canbe expected as the number of CPEs is increased?

Frame utilization data should be collected over an extended period of time thatincludes 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 frameswhen using the monitor. Analyzing this sample size or greater ensures that theresulting data provides a consistent representation of the RF link activity.

The frame utilization monitor may be configured, controlled, and monitored via SNMPcommands. See the procedure below for details on SNMP frame utilization usage.


35/68



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.


36/68



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

Only when monitoring AP frame utilization with a single registered CPE, using an AnalysisInterval of 5 frames may produce varying throughput table results.

It is recommended to use an Analysis Interval (frames) of at least 100 frames when usingthe monitor. Analyzing this sample size or greater ensures that the resulting data provides aconsistent 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

DescrDefines the number of frames (5 – 1000)to be analyzed for each monitoringrepetition.

4 Enter the Repetition Rate (secs). This value represents how often the AP will begin frame utilizationanalysis of the number of frames specified in Analysis Interval (frames). One table row will becreated for each repetition of analysis.

Repetition Rate SNMP OID Information:

Name danDevInfoFrameUtilRepetitionRate

OID .1.3.6.1.4.1.32584.1.3.4.8MIB DAN-BASIC-MIB-ADMIN

Syntax Integer32 (5..60)

Access read-write

Descr

Frame utilization data collection repetitioninterval in seconds (range 5 – 60). Thisfield identifies the time between twoconsecutive executions of the frameutilization data collection.

5 Click Update.


37/68



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 thefollowing OID.

Name danDevInfoFrameUtilCollectionOID .1.3.6.1.4.1.32584.1.3.4.7


SyntaxINTEGER {startCollection(1),stopCollection(2)}

Access read-write

Descr

Start and Stop operation for the FrameUtilization feature that is based on the theconfigured Analysis Interval andRepetition 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 SystemTime for which the data was collected.

For example, to retrieve the first collection of DL Slots Used (%), begin by performing an SNMPgetnext 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 byissuing 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 RepetitionRate (secs)

Name danDevInfoFrameUtilSysTime

OID .1.3.6.1.4.1.32584.1.3.4.6.1.1


Syntax Unsigned32


38/68



Access read-only

Indexes danDevInfoFrameUtilSysTime

DescrThe time in GMT at which the data wascollected

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 theaverage 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 theaverage 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 WiMAXframe. This value represents the average usage of the Map slots in theAnalysis Interval (frames). A good practice in network operation is totry to keep the Map Average Usage at or below 80%. If Map AverageUsage is reporting greater than 80% usage but the Average Usage isbelow 80% the Map Symbol # parameter located in the AP GUI atConfiguration > Mode may be increased to 7, thereby increasing theMap 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


DescrPercentage of MAP slots used in the Analysis Interval

Frames MAP Full (%) As a percentage of the Analysis Interval (frames), this value is anindication of the system capacity from a resource allocation (or control)perspective. The number of CPEs, number of service flows


39/68



established, and the polling intervals for non-Best Effort service flowscan all have an impact on this ratio.

Name danDevInfoFrameUtilMapFull

OID .1.3.6.1.4.1.32584.1.3.4.6.1.9

MIB DAN-BASIC-MIB-ADMINSyntax Integer32

Access read-only


DescrNumber of frames in the Analysis Intervalfor which scheduling stopped becauseMAP was full

DL Throughput(Kbps)

The average downlink throughput achieved during the AnalysisInterval (frames).

Name danDevInfoFrameUtilDlThroughput

OID .1.3.6.1.4.1.32584.1.3.4.6.1.27

MIB DAN-BASIC-MIB-ADMINSyntax Unsigned32

Access read-only


DescrOver the air DL throughput in bps duringthe 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




DescrOver the air UL throughput in bps duringthe Analysis Interval

MCS Metrics

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


OID .1.3.6.1.4.1.32584.1.3.4.6.1.1


Syntax Unsigned32

Access read-only


DescrThe time in GMT at which the datawas collected


40/68



DL 64QAM 5/6 MIMO-B %),

DL 64QAM 5/6 (%), DL64QAM 3/4 (%), DL 64QAM2/3 (%), DL 64QAM 1/2 (%),DL 16QAM 3/4 (%), DL

16QAM 1/2 (%), DL QPSK3/4 (%), DL QPSK 1/2 (%)

The percentage of downlink data slots used in theAnalysis Interval (frames) for each MCS (Modulationand Coding Scheme) state.

Name danDevInfoFrameUtilDl64QAM67MimoB

OID .1.3.6.1.4.1.32584.1.3.4.6.1.10MIB DAN-BASIC-MIB-ADMIN

Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith 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


DescrThe percentage of DL slots modulatedwith 64QAM 5/6 using MIMO Adiversity


OID .1.3.6.1.4.1.32584.1.3.4.6.1.12


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.13


Syntax Integer32

Access read-onlyIndexes danDevInfoFrameUtilSysTime



OID .1.3.6.1.4.1.32584.1.3.4.6.1.14


41/68




Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.15


Syntax Integer32

Access read-only


Descr

The percentage of DL slots modulated

with 16QAM 3/4 using MIMO Adiversity


OID .1.3.6.1.4.1.32584.1.3.4.6.1.16


Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith 16QAM 1/2 using MIMO A

diversity

Name danDevInfoFrameUtilDlQPSK34

OID .1.3.6.1.4.1.32584.1.3.4.6.1.17


Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith 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



42/68




UL 64QAM 5/6 (%), UL64QAM 3/4 (%), UL 64QAM

2/3 (%), UL 64QAM 1/2 (%),UL 16QAM 3/4 (%), UL16QAM 1/2 (%), UL QPSK3/4 (%), UL QPSK 1/2 (%)

The percentage of uplink data slots used in theAnalysis Interval (frames) for each MCS (Modulation

and Coding Scheme) state.

Name danDevInfoFrameUtilUl64QAM56

OID .1.3.6.1.4.1.32584.1.3.4.6.1.19


Syntax Integer32

Access read-only


DescrThe percentage of UL slots modulatedwith 64QAM 5/6


OID .1.3.6.1.4.1.32584.1.3.4.6.1.20


Syntax Integer32

Access read-only





Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.22


Syntax Integer32

Access read-only




43/68




OID .1.3.6.1.4.1.32584.1.3.4.6.1.23


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.24


Syntax Integer32

Access read-only



Name danDevInfoFrameUtilUlQPSK34

OID .1.3.6.1.4.1.32584.1.3.4.6.1.25


Syntax Integer32

Access read-only


DescrThe percentage of UL slots modulated

with QPSK 3/4


OID .1.3.6.1.4.1.32584.1.3.4.6.1.26


Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith QPSK 1/2

All Metrics

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


OID .1.3.6.1.4.1.32584.1.3.4.6.1.1


44/68




Syntax Unsigned32

Access read-only


Descr The time in GMT at which the datawas collected

Total DL Slots The total number of downlink slots analyzed during theAnalysis 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 Analysis Interval not including MAP(Medium Access Control) and FCH(Frame Control Header)

DL Slots Used The total number of downlink slots used during theAnalysis Interval (frames).

Name danDevInfoFrameUtilTotalDLSlots

OID .1.3.6.1.4.1.32584.1.3.4.6.1.2


Syntax Integer32


Descr

Total number of DL slots in the Analysis Interval not including MAP(Medium Access Control) and FCH(Frame Control Header)

DL Slots Used (%) The percentage of downlink data slots used in theAnalysis Interval (frames). A good practice innetwork operation is to try to keep the average usage ator below 80%.



Syntax Integer32

Access read-only


DescrPercentage of total DL slots used in the Analysis Interval not including MAP


45/68



(Medium Access Control) and FCH(Frame Control Header)

Total UL Slots The total number of uplink slots analyzed during theAnalysis Interval (frames).


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 total number of uplink slots used during theAnalysis Interval (frames).

UL Slots Used (%) The percentage of uplink data slots used in theAnalysis Interval (frames). A good practice in

network operation is to try to keep the average usage ator below 80%.

Name danDevInfoFrameUtilPercULSlotsUsed

OID .1.3.6.1.4.1.32584.1.3.4.6.1.6


Syntax Integer32

Access read-only


DescrNumber of DL slots used in the Analysis Interval not including uplinkcontrol slots

MAP Slots Used (%) The Map slots allocate downlink and uplink resources ineach WiMAX frame. This value represents the averageusage of the Map slots in the Analysis Interval(frames). A good practice in network operation is to tryto keep the Map Average Usage at or below 80%. IfMap Average Usage is reporting greater than 80%usage but the Average Usage is below 80% the MapSymbol # parameter located in the AP GUI atConfiguration > Mode may be increased to 7, thereby

increasing the Map header and allowing for more Mapoverhead.

Name danDevInfoFrameUtilMapSlotsUsed

OID .1.3.6.1.4.1.32584.1.3.4.6.1.8


Syntax Integer32

Access read-only


46/68




DescrPercentage 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 aresource allocation (or control) perspective. Thenumber of CPEs, number of service flows established,and the polling intervals for non-Best Effort serviceflows 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


DescrNumber of frames in the AnalysisInterval for which scheduling stoppedbecause MAP was full

DL 64QAM 5/6 MIMO-B(%),DL 64QAM 5/6 (%), DL64QAM 3/4 (%), DL 64QAM2/3 (%), DL 64QAM 1/2 (%),DL 16QAM 3/4 (%), DL16QAM 1/2 (%), DL QPSK3/4 (%), DL QPSK 1/2 (%)

The number of downlink data slots used in theAnalysis Interval (frames) for each MCS (Modulationand Coding Scheme) state.

Name danDevInfoFrameUtilDl64QAM56MimoB

OID .1.3.6.1.4.1.32584.1.3.4.6.1.10


Syntax Integer32


DescrThe percentage of DL slots modulatedwith 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




OID .1.3.6.1.4.1.32584.1.3.4.6.1.12



47/68



Syntax Integer32

Access read-only


Descr

The percentage of DL slots modulated

with 64QAM 3/4 using MIMO Adiversity


OID .1.3.6.1.4.1.32584.1.3.4.6.1.13


Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith 64QAM 2/3 using MIMO A

diversity


OID .1.3.6.1.4.1.32584.1.3.4.6.1.14


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.15


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.16


Syntax Integer32

Access read-only



48/68




Name danDevInfoFrameUtilDlQPSK34OID .1.3.6.1.4.1.32584.1.3.4.6.1.17


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.18


Syntax Integer32

Access read-only



UL 64QAM 5/6 (%), UL64QAM 3/4 (%), UL 64QAM2/3 (%), UL 64QAM 1/2 (%),UL 16QAM 3/4 (%), UL16QAM 1/2 (%), UL QPSK3/4 (%), UL QPSK 1/2 (%)

The number of uplink data slots used in the AnalysisInterval (frames) for each MCS (Modulation andCoding Scheme) state.


OID .1.3.6.1.4.1.32584.1.3.4.6.1.19


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.20

MIB DAN-BASIC-MIB-ADMINSyntax Integer32

Access read-only




49/68




OID .1.3.6.1.4.1.32584.1.3.4.6.1.21


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.22


Syntax Integer32

Access read-only




OID .1.3.6.1.4.1.32584.1.3.4.6.1.23


Syntax Integer32

Access read-only


DescrThe percentage of UL slots modulated

with 16QAM 3/4


OID .1.3.6.1.4.1.32584.1.3.4.6.1.24


Syntax Integer32

Access read-only



Name danDevInfoFrameUtilUlQPSK34

OID .1.3.6.1.4.1.32584.1.3.4.6.1.25


Syntax Integer32

Access read-only



50/68



DescrThe percentage of UL slots modulatedwith QPSK 3/4



Syntax Integer32

Access read-only


DescrThe percentage of DL slots modulatedwith QPSK 1/2

DL Throughput (Kbps) The average downlink throughput achieved during theAnalysis Interval (frames).

Name danDevInfoFrameUtilDlThroughput

OID .1.3.6.1.4.1.32584.1.3.4.6.1.27


Syntax Unsigned32

Access read-only


DescrOver the air DL throughput in bpsduring the Analysis Interval

UL Throughput (Kbps) The average uplink throughput achieved during theAnalysis Interval (frames).

Name danDevInfoFrameUtilUlThroughput

OID .1.3.6.1.4.1.32584.1.3.4.6.1.28


Syntax Unsigned32

Access read-only


DescrOver the air UL throughput in bpsduring the Analysis Interval

Avg DL MCS (bits/slot) The average number of downlink bits per slot over theAnalysis 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


51/68



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

Name danDevInfoFrameUtilUlAvgMCS


Syntax Integer32

Access read-only


Descr Average UL MCS (in bits/slot units)utilized during the Analysis Interval

Avg DL UnusedSlots/Frame

The average (over the Analysis Interval) number ofdownlink slots that were not used for data transmission.

Name danDevInfoFrameUtilAvgDlUnusedSlots


Syntax Integer32

Access read-only


Descr Average unused DL slots per frameduring the Analysis Interval

Avg UL UnusedSlots/Frame

The average (over the Analysis Interval) number ofuplink 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 frameduring the Analysis Interval


52/68



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 thefollowing OID.

Name danDevInfoFrameUtilCollectionOID .1.3.6.1.4.1.32584.1.3.4.7


SyntaxINTEGER {startCollection(1),stopCollection(2)}

Access read-write

Descr

Start and Stop operation for the FrameUtilization feature that is based on the theconfigured Analysis Interval andRepetition 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 theCSM device type changes to “generic” in CNUT, the element may be changed back to aPMP 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 AP‟sAdministration > Configuration Control GUI page. If it is required that the network isreverted back to a pre-2.3 release, the configuration control point may be restored, andall QoS and service flow configuration will be restored. Before upgrading to e2.3, if allconfiguration restore points are already populated, overwrite one of them with the AP‟scurrent configuration without changing the restore point’s name. Otherwise, an unusedconfiguration control slot may be used. When using e2.3, configuration control restorepoints may be created with new names.

Before upgrading to e2.3, the AP‟s “admin” account password should be set to “admin”.During the upgrade process, all AP usernames and passwords are reset to their defaultvalues. By configuring the AP‟s “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 stagingprocess, the modules may be upgraded to the latest software version, configured to theoperator‟s specifications, and validated for proper functionality.


53/68



PMP 320 Module Pre-deployment Upgrading

When the radios arrive from the factory, the software version may be upgradedimmediately to take advantage of the latest software functionality and performance. Thefollowing steps can be used to update a single AP

Documents

PMP 320 Release Notes e2.3