Cambium Networks 50450M 5GHz Point to MultiPoint Multi User MIMO Access Point User Manual USERS MANUAL PART4

Cambium Networks Limited 5GHz Point to MultiPoint Multi User MIMO Access Point USERS MANUAL PART4

UserManual.wiki >

Cambium Networks >

50450M User Manual >

USERS MANUAL PART4 HTML Version

USERS MANUAL PART4

Chapter 9: Operation System information

Page 9-28

Link Quality tab

The Link Quality tab provides information on the Subscriber’s UID, Link quality, Downlink, Uplink,

Beacon, ReReg, and the Uptime.

This data is refreshed based on the Link Quality Update Interval parameter configuration under the

Sessions Status page.

The Link Quality tab displays the calculated Link Quality Indicator (LQI) for the configured interval (Link

Quality Update Interval parameter).

Table 217 Link Quality tab attributes

Attribute Meaning

Subscriber See Table 212 on page 9-20.

Link Quality Indicator This field displays quality of the link. It is calculated based on receive power,

modulation rate, re-registrations and beacon percentage.

Downlink - Quality

Index

This field displays the downlink quality in percentage. It is calculated based

on Downlink receiver power, modulation rate, and beacon percentage.

Downlink -Actual

Average Rate

This field displays the average Downlink modulation rate. For 450m, this field

specifies the SU-MIMO Modulation Rate.

Downlink - Expected

Rate

This field displays the expected modulation rate based on receive power in

Downlink.

Uplink - Quality Index This field displays the uplink quality in percentage. It is calculated based on

Uplink receiver power and modulation rate.

Uplink -Actual

Average Rate

This field displays the average Uplink modulation rate.

Uplink - Expected

Rate

This field displays the expected modulation rate based on receive power in

Uplink.

Chapter 9: Operation System information

Page 9-29

Beacon - Quality

Index

This field displays the beacon quality index. It is calculated based on beacon

percentage.

Beacon - Received

Percent

This field displays the received beacon percentage.

Re-Reg - Quality

Index

This field displays the re-registration quality. It is calculated based on the re-

registration count.

Re-Reg Count This field displays the number of re-registrations.

Uptime This field displays the uptime of the device.

Viewing Remote Subscribers

This page allows to view the web pages of registered SMs or BHS over the RF link. To view the pages for

a selected SM/BHS, click its link. The General Status page of the SM opens.

Figure 193 Remote Subscribers page of AP

Interpreting messages in the Event Log

Each line in the Event Log of a module Home page begins with a time and date stamp. However, some of

these lines wrap as a combined result of window width, browser preferences and line length. You may

find this tab easiest to use if you expand the window till all lines are shown beginning with time and date

stamp.

Time and Date Stamp

The time and date stamp reflect one of the following:

 GPS time and date directly or indirectly received from the CMM4.

 NTP time and date from a NTP server (CMM4 may serve as an NTP server)

 The running time and date that you have set in the Time & Date web page.

Chapter 9: Operation System information

Page 9-30

Note

In the Time & Date web page, if you have left any time field or date field unset and clicked

the

Set Time and Date

button, then the time and date default to

00:00:00 UT :

01/01/00

A reboot causes the preset time to pause or, in some cases, to run in reverse. Additionally, a

power cycle resets the running time and date to the default

00:00:00 UT : 01/01/00

Thus, whenever either a reboot or a power cycle has occurred, must reset the time and date

in the Time & Date web page of any module that is not set to receive sync.

Event Log Data Collection

The collection of event data continues through reboots and power cycles. When the buffer allowance for

event log data is reached, the system adds new data into the log and discards an identical amount of the

oldest data.

Each line that contains the expression WatchDog flags an event that was both:



considered by the system software to have been an exception



recorded in the preceding line.

Conversely, a Fatal Error () message flags an event that is recorded in the next line. Some exceptions

and fatal errors may be significant and require either operator action or technical support.

Figure 194

Event log data

Messages that Flag Abnormal Events

The messages listed below flag abnormal events and, case by case, may signal the need for corrective

action or technical support.

Table 218

Event Log messages for abnormal events

Event Message Meaning

Chapter 9: Operation System information

Page 9-31

Expected LUID = 6

Actual LUID = 7

Something is interfering with the control messaging of the module. Also

ensure that you are using shielded cables to minimize interference. Consider

trying different frequency options to eliminate or reduce interference.

FatalError() The event recorded on the line immediately beneath this message triggered

the Fatal Error ().

Loss of GPS Sync

Pulse Module has lost GPS sync signal.

Machine Check

Exception

This is a symptom of a possible hardware failure. If this is a recurring

message, begin the RMA process for the module.

RcvFrmNum =

0x00066d

ExpFrmNum =

0x000799

Something is interfering with the control messaging of the module. Also

ensure that you are using shielded cables to minimize interference. Consider

trying different frequency options to eliminate or reduce interference.

System Reset

Exception -- External

Hard Reset

The unit lost power or was power cycled.

System Reset

Exception -- External

Hard Reset WatchDog

The event recorded on the preceding line triggered this WatchDog message.

Messages that Flag Normal Events

The messages listed below record normal events and typically do not signal a need for any corrective

action or technical support.

Table 219 Event Log messages for normal events

Event Message Meaning

Acquired GPS Sync

Pulse. Module has acquired GPS sync signal.

FPGA Features Type of encryption.

FPGA Version FPGA (JBC) version in the module.

GPS Date/Time Set Module is now on GPS time.

Reboot from Webpage Module was rebooted from management interface.

Software Boot Version Boot version in the module.

Software Version The software release and authentication method for the unit.

System Log Cleared Event log was manually cleared.

Chapter 9: Operation System information

Page 9-32

Viewing the Network Interface

In any module, the LAN1 Network Interface section of this tab displays the defined Internet Protocol

scheme for the Ethernet interface to the module. In SM/BHS devices, this page also provides an RF

Public Network Interface section, which displays the Internet Protocol scheme defined for network access

through the master device (AP/BHM).

Figure 195

Network Interface tab of the AP

Figure 196

Network Interface tab of the SM

Viewing the Layer 2 Neighbors

In the Layer 2 Neighbors tab, a module reports any device from which it has received a message in Link

Layer Discovery Protocol within the previous two minutes. Given the frequency of LLDP messaging, this

means that the connected device will appear in this tab 30 seconds after it is booted and remain until two

minutes after its shutdown.

Figure 197

Layer 2 Neighbors page

Chapter 9: Operation System statistics

Page 9-33

System statistics

This section describes how to use the system statistics pages to manage the performance of the

PMP/PTP 450 Platform Family link.

Viewing the Scheduler statistics

The Statistics > Scheduler page is applicable for all modules (AP/SM/BHM/BHS) and the parameters

are displayed as shown below:

Table 220 Scheduler tab attributes

Chapter 9: Operation System statistics

Page 9-34

Attribute Meaning

Transmit Unicast Data

Count Total amount of unicast packets transmitted from the radio

Transmit Broadcast

Data Count Total amount of broadcast packets transmitted from the radio

Transmit Multicast

Data Count Total amount of multicast packets transmitted by the radio

Receive Unicast Data

Count Total amount of unicast packets received by the radio

Receive Broadcast

Data Count Total amount of broadcast packets received by the radio

Receive Multicast

Data Count Total amount of multicast packets received by the radio

Transmit Control

Count

Amount of radio control type messages transmitted (registration requests and

grants, etc.)

Receive Control Count Amount of radio control type messages received (registration requests and

grants, etc.)

In Sync Count Number of times the radio has acquired sync. When GPS synchronization is

used it is number of times GPS sync acquired. For the SM, itis the number of

times the SM successfully obtained sync with an AP.

Out of Sync Count Number of times the radio lost same sync lock

Overrun Count Number of times FPGA frame has overrun its TX Frame

Underrun Count Number of times FPGAs TX Frame aborted prematurely

Receive Corrupt Data

Count Number of times a corrupt packet has been received at the FPGA.

Receive Corrupt

Control Data Count

Number of times a corrupt control data packet has been received at the

FPGA.

Receive Bad

Broadcast Control

Count

Number of times the radio has received an invalid control message via

broadcast (SM only).

Rcv LT Start Number of Link Test Start messages received. A remote radio has requested

that this radio start a link test to it.

Rcv LT Start HS Number of Link Test Start Handshake messages received. This radio

requested that a remote radio start a link test and the remote radio has sent a

handshake back acknowledging the start.

Chapter 9: Operation System statistics

Page 9-35

Rcv LT Result This radio received Link Test results from the remote radio under test. When

this radio initiates a link test, the remote radio will send its results to this radio

for display.

Xmt LT Result This radio transmitted its link test results to the remote radio under test. When

the remote radio initiates a link test, this radio must send its results to the

remote radio for display there.

Frame Too Big This statistics indicates the number of packets received and processed by the

radios which were greater than max packet size 1700 bytes.

Bad Acknowledgment This statistics indicates the number of packets received as bad

acknowledgment. It is for engineering use only.

Bad Fragment This statistic indicates number of fragments tagged internally as bad. It is for

engineering use only.

VC Clear Error Count This statistic indicates number of times VC clear failed.

Rx No Buffer Count Currently unused

Scheduler Error This error is incremented when the scheduler cannot send or get scheduled

to send a packet. t is also general called a “VC Error”.

Viewing list of Registration Failures statistics

SM Registration Failures page of AP

The SM Registration Failures tab identifies SMs that have recently attempted and failed to register to this

AP. With its time stamps, these instances may suggest that a new or transient source of interference

exists.

Table 221 SM Registration Failures page attributes - AP

Attribute Meaning

Status 17 Flag 0 No response was received from the AAA server and hence SM is trying to

send a session request again.

Chapter 9: Operation System statistics

Page 9-36

BHS Registration Failures page of BHM

Table 222 BHS Registration Failures page attributes - BHM

Attribute Meaning

Status 17 Flag 0 No response was received from the AAA server and hence SM is trying to

send a session request again.

There is a list of flags from 0 to 20 as shown in Table 223 and the “Flags” can be ignored.

Table 223 Flags status

Flag Meaning Flag Meaning

0 Normal 11 AP Lite Limit Reached

1 Out of Range 12 Only Ver 9.5+ Allowed

2 No Luids 13 Temporary Data VC for AAA

3 BH ReRange 14 AAA Authentication Failure

4 Auth Fail 15 Registration Grant Reject

5 Encrypt Fail 16 Blank

6 Power Adjust 17 AAA Session Retry

7 No VCs 18 AAA Reauth Failure

8 Reserve VC Fail 19 RegReq at zero power

9 Activate VC Fail 20 RegReq no time ref

10 Hi VC Setup Fail - -

Chapter 9: Operation System statistics

Page 9-37

Interpreting Bridging Table statistics

If NAT (network address translation) is not active on the SM/BHS, then the Bridging Table page provides

the MAC address of all devices that are attached to registered SMs/BHS (identified by LUIDs).

The SM/BHS management MAC addresses are also added in bridge table upon SMs/BHS registration.

These entries will be remove automically from the table once SMs/BHS is de-registered. This alleviates

the arp cache > bridge cache timeout problems.

The bridging table allows data to be sent to the correct module as follows:

 For the AP/BHM, the uplink is from RF to Ethernet. Thus, when a packet arrives in the RF interface to

the AP/BHM, the AP/BHM reads the MAC address from the inbound packet and creates a bridging

table entry of the source MAC address on the other end of the RF interface.

 For the SM/BHS, the uplink is from Ethernet to RF. Thus, when a packet arrives in the Ethernet

interface to one of these modules, the module reads the MAC address from the inbound packet and

creates a bridging table entry of the source MAC address on the other end of the Ethernet interface.

Figure 198 Bridging Table page

The Bridging Table supports up to 4096 entries.

Interpreting Translation Table statistics

When Translation Bridging is enabled in the AP, each SM keeps a table mapping MAC addresses of

devices attached to the AP to IP addresses, as otherwise the mapping of end-user MAC addresses to IP

addresses is lost. (When Translation Bridging is enabled, an AP modifies all uplink traffic originating from

registered SMs such that the source MAC address of every packet is changed to that of the SM which

bridged the packet in the uplink direction.)

Chapter 9: Operation System statistics

Page 9-38

Figure 199 Translation Table page of SM

Interpreting Ethernet statistics

The Statistics > Ethernet page reports TCP throughput and error information for the Ethernet connection

of the module. This page is applicable for all modules (AP/SM/BHM/BHS).

The Ethernet page displays the following fields.

Table 224 Ethernet tab attributes

Attribute Meaning

Ethernet Link

Detected

1 indicates that an Ethernet link is established to the radio, 0 indicates that no

Ethernet link is established

Chapter 9: Operation System statistics

Page 9-39

Ethernet Link Lost This field indicates a count of how many times the Ethernet link was lost.

Undersized Toss

Count

This field indicates the number of packets that were too small to process and

hence discarded.

inoctets Count This field displays how many octets were received on the interface, including

those that deliver framing information.

inucastpkts Count This field displays how many inbound subnetwork-unicast packets were

delivered to a higher-layer protocol.

Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or

subnetwork-multicast) packets were delivered to a higher-layer protocol.

indiscards Count This field displays how many inbound packets were discarded without errors

that would have prevented their delivery to a higher-layer protocol. (Some of

these packets may have been discarded to increase buffer space.)

inerrors Count This field displays how many inbound packets contained errors that prevented

their delivery to a higher-layer protocol.

inunknownprotos

Count

This field displays how many inbound packets were discarded because of an

unknown or unsupported protocol.

outoctets Count This field displays how many octets were transmitted out of the interface,

including those that deliver framing information.

outucastpkts Count This field displays how many packets for which the higher-level protocols

requested transmission to a subnetwork-unicast address. The number

includes those that were discarded or not sent.

outnucastpkts Count This field displays how many packets for which the higher-level protocols

requested transmission to a non-unicast (subnetwork-broadcast or

subnetwork-multicast) address. The number includes those that were

discarded or not sent.

outdiscards Count This field displays how many outbound packets were discarded without errors

that would have prevented their transmission. (Some of these packets may

have been discarded to increase buffer space.)

outerrrors Count This field displays how many outbound packets contained errors that

prevented their transmission.

RxBabErr This field displays how many receiver babble errors occurred.

TxHbErr This field displays how many transmit heartbeat errors have occurred.

EthBusErr This field displays how many Ethernet bus errors occurred on the Ethernet

controller.

CRCError This field displays how many CRC errors occurred on the Ethernet controller.

RcvFifoNoBuf This field displays the number of times no FIFO buffer space was able to be

allocated.

Chapter 9: Operation System statistics

Page 9-40

Note:

PMP 450 AP running in Gigabit Ethernet Mode displays error

“RcfFifoNoBuf” which indicates packet loss.

For 450 AP platforms, if ethernet auto-negotation is set to

Gigabit, then it is a known limitation that “RcfFifoNoBuf” error will

be seen. This issue is not seen if autonegotation is set to

100Mbps or lower, and the issue is not seen on 450i or 450m

AP's.

RxOverrun This field displays how many receiver overrun errors occurred on the Ethernet

controller.

Late Collision

This field displays how many late collisions occurred on the Ethernet

controller. A normal collision occurs during the first 512 bits of the frame

transmission. A collision that occurs after the first 512 bits is considered a late

collision.

Caution

A late collision is a serious network problem because the frame being

transmitted is discarded. A late collision is most commonly caused by

a mismatch between duplex configurations at the ends of a link

segment.

RetransLimitExp This field displays how many times the retransmit limit has expired.

TxUnderrun This field displays how many transmission-underrun errors occurred on the

Ethernet controller.

CarSenseLost This field displays how many carrier sense lost errors occurred on the

Ethernet controller.

No Carrier This field displays how many no carrier errors occurred on the Ethernet

controller.

Chapter 9: Operation System statistics

Page 9-41

Interpreting RF Control Block statistics

The Statistics > Radio page is applicable for all module (AP/SM/BHM/BHS). The Radio page of the

Statistics page displays the following fields.

Table 225 Radio (Statistics) page attributes – RF Control Block

Attribute Meaning

inoctets Count This field displays how many octets were received on the interface, including

those that deliver framing information.

inucastpkts Count This field displays how many inbound subnetwork-unicast packets were

delivered to a higher-layer protocol.

Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or

subnetwork-multicast) packets were delivered to a higher-layer protocol.

indiscards Count This field displays how many inbound packets were discarded without errors

that would have prevented their delivery to a higher-layer protocol. This stat is

pegged whenever corrupt data is received by software or whenever the RF

Software Bridge queue is full.

Corrupt data is a very unusual event because all packets are CRC checked

by hardware before being passed into software.

The likely case for indiscards is if the RF bridge queue is full. If this is the

case the radio is most likely PPS limited due to excessive small packet traffic

or a problem at the Ethernet interface. If there is a problem at the Ethernet

interface there is likely to be discards at the Ethernet as well.

inerrors Count This field displays how many inbound packets contained errors that prevented

their delivery to a higher-layer protocol.

inunknownprotos

Count

This field displays how many inbound packets were discarded because of an

unknown or unsupported protocol.

Chapter 9: Operation System statistics

Page 9-42

outoctets Count This field displays how many octets were transmitted out of the interface,

including those that deliver framing information.

outucastpkts Count This field displays how many packets for which the higher-level protocols

requested transmission to a subnetwork-unicast address. The number

includes those that were discarded or not sent.

outnucastpkts Count This field displays how many packets for which the higher-level protocols

requested transmission to a non-unicast (subnetwork-broadcast or

subnetwork-multicast) address. The number includes those that were

discarded or not sent.

outdiscards Count This field displays how many outbound packets were discarded without errors

that would have prevented their transmission. (Some of these packets may

have been discarded to increase buffer space.)

outerrrors Count This field displays how many outbound packets contained errors that

prevented their transmission.

Page 9-1

Interpreting Sounding statistics for AP

In the AP GUI, sounding statistics can be found under Statistics > Radio.

Table 226 Radio (Statistics - AP) page attributes - Sounding

Attribute Meaning

reference SF Spatial Frequency of VC. Values 0 to 1023 are valid and value 2048 is considered as invalid.

soundingState Different types of Sounding states are:

 UNKNOWN: VC has recently registered to the AP but not registered with the channel manager yet.

 NEW: VC has been registered with the channel manager and will soon transition to ASSESSING.

 ASSESSING: AP will instruct SM to take the channel measurements. Channel estimates and spatial

frequencies will be calculated.

 TRACKING: Valid measurements resulted in good channel estimates and spatial frequency. This VC can

now be used for MU-MIMO.

 INVALID: Inconsistent measurements resulting in no channel estimate or spatial frequency. This VC cannot

be used for MU-MIMO and it will ultimately be re-assessed.

Chapter 9: Operation System statistics

Page 9-2

soundingFault Generally if VC is UNTRUSTED, this means something went wrong. The fault codes can help to describe what is

wrong with this channel (If VC is TRACKING this will generally indicate 0 (SOUNDING_FAULT_NONE)).

Error codes are:

 SOUNDING_FAULT_VC_CEST: Channel Estimate Error, could be due to issues with the channel..

 SOUNDING_FAULT_NULLING_SNR: Channel Estimate Error, could be due to issues with the channel.

 SOUNDING_FAULT_SM_ERROR: SM returned Error code when taking channel measurements.

 SOUNDING_FAULT_CHANNEL_DISTORTION: Channel Distortion is beyond tolerance, could be due to

issues with the channel.

 SOUNDING_FAULT_UNSTABLE_SF: Inconsistent Spatial Frequency, could be due to issues with the

channel.

 SOUNDING_FAULT_SF_DEVIATION: Inconsistent Spatial Frequency, could be due to issues with the

channel.

 SOUNDING_FAULT_INTERNAL_ERROR: Could be due to incompatible software (AP – SM), or other

catastrophic software issue.

mumimoVetoCount If excessive channel distortion is observed during condensed nulling (tracking state) this count will increment and

VC will transition back to assessing state.

channelDistortion Channel distortion readings.

nullingSNR Signal to noise ratio of condensed nulling error response.

cnResponseCountSM The SM adds a counter to the CN (Condensed Nulling) response. This indicates how many responses were sent

by that SM.

cnResponseCountAP The AP increments a count for each CN response received.

missedTagCount This is the number of CN responses transmitted by SM but not received at AP.

Chapter 9: Operation System statistics

Page 9-3

Page 9-1

Interpreting Sounding statistics for SM

In the SM GUI, sounding statistics can be found under Statistics > Radio.

The top section, RF Control Block Statistics, is applicable to the SM communicating to any AP (450, 450i,

or 450m), and it is always visible. The bottom section, Sounding Statistics, is visible only if the SM is

communicating with a 450m AP.

Table 227 Radio (Statistics - SM) page attributes - Sounding

Attribute Meaning

Responses Number of sounding responses (full VC assessments or condensed nulling)

sent from the SM to the AP

Responses

Suppressed

Number of sounding requests suppressed by the SM.

The reason why a sounding response is suppressed is because the error

calculated during the sounding process is lower than the threshold set by the

AP. In this case, the SM does not need to transmit a sounding response to

the AP

Errors Number of errors in the sounding process at the SM

Examples of events that count as errors:

 Sounding type is not supported

 IQ capture not enabled: for example, if sounding requested too soon after

SM boot

 IQ capture did not complete

 Sounding processing took too long

Version Mismatch Number of sounding requests with mismatched version numbers

The Sounding Acquisition Command contains a version number. The SM

checks its own version number and flags any mismatch. Currently, AP and

SMs use V1.

Max Request Interval Largest time between two sounding requests received from the 450m AP

Avg Request Interval Average time between two sounding requests received from the 450m AP

Chapter 9: Operation System statistics

Page 9-2

The following attributes are applicable only for 450m:

Attribute Meaning

mumimoVetoCount If excessive channel distortion is observed during condensed nulling (tracking

state) this count will increment and VC will transition back to assessing state.

channelDistortion Channel distortion readings.

nullingSNR Signal to noise ratio of condensed nulling error response.

cnResponseCountSM The SM adds a counter to the CN (Condensed Nulling) response. This

indicates how many responses were sent by that SM.

cnResponseCountAP The AP increments a count for each CN response received.

missedTagCount This is the number of CN responses transmitted by SM but not received at

AP.

Interpreting VLAN statistics

The Statistics > VLAN page provides a list of the most recent packets that were filtered because of

VLAN membership violations. It is applicable for all modules (AP/SM/BHM/BHS).

Table 228 VLAN page attributes

Attribute Meaning

Unknown This must not occur. Contact Technical Support.

Only Tagged The packet was filtered because the configuration is set to accept only

packets that have an 802.1Q header and this packet did not.

Ingress When the packet entered through the wired Ethernet interface, the packet

was filtered because it indicated an incorrect VLAN membership.

Chapter 9: Operation System statistics

Page 9-3

Local Ingress When the packet was received from the local TCP/IP stack, the packet was

filtered because it indicated an incorrect VLAN membership. This must not

occur. Contact Technical Support.

Egress When the packet attempted to leave through the wired Ethernet interface, the

packet was filtered because it indicated an incorrect VLAN membership.

Local Egress When the packet attempted to reach the local TCP/IP stack, the packet was

filtered because it indicated an incorrect VLAN membership.

Chapter 9: Operation System statistics

Page 9-4

Interpreting Data VC statistics

The Statistics > Data VC page displays information about Virtual Channel (VC) used in data

communications. This page is applicable for all modules (AP/SM/BHM/BHS).

The Data VC tab displays the fields as explained in Table 229.

Table 229 Data VC page attributes

Attribute Meaning

Subscriber This field displays the LUID (logical unit ID), MAC address and Site Name of

the SM/BHS. As each SM or BHS registers to the AP/BHM, the system

assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS

loses registration with the AP/BHM and then regains registration, the SM/BHS

retains the same LUID.

VC This field displays the virtual channel number. Low priority channels start at

VC18 and count up. High priority channels start at VC255 and count down. If

one VC is displayed, the high-priority channel is disabled. If two are

displayed, the high-priority channel is enabled.

CoS This field displays the Class of Service for the virtual channel. The low priority

channel is a CoS of 00 and the high priority channel is a CoS of 01. CoS of 02

through 07 are not currently used.

Inbound Statistics,

octets

This field displays how many octets were received on the interface, including

those that deliver framing information.

Inbound Statistics,

ucastpkts

This field displays how many inbound subnetwork-unicast packets were

delivered to a higher-layer protocol.

Inbound Statistics,

nucastpkts

This field displays how many inbound non-unicast (subnetwork-broadcast or

subnetwork-multicast) packets were delivered to a higher-layer protocol.

Inbound Statistics,

discards

This field displays how many inbound packets were discarded without errors

that would have prevented their delivery to a higher-layer protocol. Inbound

discard statistics are incremented similar to the indiscards stat on the RF

control block stats page. The sum of all data VC indiscards must be close to

the RF control block in discards. If indiscards are evenly distributed across

SMs, then the radio is PPS limited due to either excessive small packet

transmissions, or a problem at the Ethernet link. If indiscards are contained to

one or a few SMs, then there is likely a problem at or underneath the SM

which is incrementing the count.

Chapter 9: Operation System statistics

Page 9-5

Inbound Statistics,

errors

This field displays how many inbound packets contained errors that prevented

their delivery to a higher-layer protocol.

Inbound Statistics,

QPSK frgmts

This field displays how many inbound fragments were received via the QPSK

modulation scheme.

Inbound Statistics, 16-

QAM frgmts

This field displays how many inbound fragments were received via the 16-

QAM modulation scheme.

Inbound Statistics, 64-

QAM frgmts

This field displays how many inbound fragments were received via the 64-

QAM modulation scheme.

Inbound Statistics,

256-QAM frgmts

This field displays how many inbound fragments were received via the 256-

QAM modulation scheme.

Outbound Statistics,

octets

This field displays how many octets were transmitted out of the interface,

including those that deliver framing information.

Outbound Statistics,

ucastpkts

This field displays how many packets for which the higher-level protocols

requested transmission to a subnetwork-unicast address. The number

includes those that were discarded or not sent.

Outbound Statistics,

nucastpkts

This field displays how many packets for which the higher-level protocols

requested transmission to a non-unicast (subnetwork-broadcast or

subnetwork-multicast) address. The number includes those that were

discarded or not sent.

Outbound Statistics,

discards

This field displays how many outbound packets were discarded without errors

that would have prevented their transmission. Outbound discard statistics are

incremented if a VC is not active when a packet is ready to send. This is a

rare condition.

Outbound Statistics,

errors

This field displays how many outbound packets contained errors that

prevented their transmission.

Queue Overflow This is a count of packets that were discarded because the queue for the VC

was already full. If Queue Overflows are being seen across most or all SMs,

then there is either an interferer local to the AP or the APs RF link is at

capacity. If Queue Overflows are being seen at one or only a few SMs, then it

is likely that there is a problem with those specific links whether it is

insufficient signal strength, interferer, or a problem with the actual SM

hardware.

High Priority Queue This is a count of packets that were received on high priority queue.

Chapter 9: Operation System statistics

Page 9-6

Interpreting Throughput statistics

The 450 Platform Family has a Statistics > Throughput page which shows historical information about

sector or backhaul throughput and packet discards. This page is applicable for AP and BHM modules.

This information can be useful to identify an overloaded sector or heavy bandwidth users. This page also

shows the user throughput in terms of data rate (kbps) and packet rate (packets per second, or PPS), as

well as the average packet size during the sample period.

Operators may set the AP/BHM to send an SNMP trap when it detects an RF overload condition based

on a configurable threshold.

The following configuration parameters are available on the Throughput tab GUI pane and a radio reboot

is not required when configuring these parameters:

Table 230 RF overload Configuration attributes – AP/BHM

Attribute Meaning

Throughput Monitoring This enables or disables the monitoring of sector throughput and packet

discards. This parameter is disabled by default.

SNMP Trap on RF

Overload

This enables or disables the sending of an SNMP trap when an AP/BHM

overload condition is reached (based on Downlink RF Overload Threshold).

Downlink RF Overload

Threshold

This parameter determines the overload threshold in percent of packets

discarded that triggers the generation of an SNMP trap.

Downlink RF Link

Status

This field displays the status of the capacity of the RF link.

Time Period Length

Time Period Ending

These two configuration parameters determine what set of collection samples

to show on the GUI display. The Time Period Length can be set from one to

three hours. Time Period Ending allows the operator to set the end time for

the set of collection samples to display.

Below the configuration settings are three tables that display the statistics that are collected.

Board Performance statistics

This table contains a row that corresponds to each 1 minute statistics collection interval. Each row

contains the following data aggregated for the entire AP/BHM:

Chapter 9: Operation System statistics

Page 9-7

 Ethernet Throughput - Statistics collected at the Ethernet port:

o kbps in – average throughput over the collection interval in Kbps into the AP/BHM on the

Ethernet Interface

o kbps out – average throughput over the collection interval in Kbps out of the AP/BHM on the

Ethernet Interface

o PPS in – average packets per second over the collection interval into the AP/BHM on the

Ethernet Interface

o PPS out – average packets per second over the collection interval out of the AP/BHM on the

Ethernet Interface

 RF Throughput - Statistics collected at the RF Interface:

o kbps in – average throughput over the collection interval in Kbps into the AP/BHM on the RF

Interface

o kbps out – average throughput over the collection interval in Kbps out of the AP/BHM on the RF

Interface

o PPS in – average packets per second over the collection interval into the AP/BHM on the RF

Interface

o PPS out – average packets per second over the collection interval out of the AP/BHM on the RF

Interface

 Aggregate Through Board – Sum of bidirectional data transferred through (not originating or

terminating at) the AP/BHM:

o kbps – average bidirectional throughput over the collection interval in Kbps

o PPS – average bidirectional packets per second over the collection interval

o Ave Pkt Size – Average Packet size over the collection interval of bidirectional data transferred

Board Throughput statistics

This table contains a row that corresponds to each one minute statistics collection interval. This table may

be used to determine if there are problems with any of the interfaces. For example, if the Ethernet in

packets is much higher than the RF out packets it could indicate a denial of service (DoS) attack on the

AP/BHM. Each row contains the following data aggregated for the entire AP/BHM:

 Ethernet Statistics - Statistics collected at the Ethernet port:

o inOctets – Number of octets (bytes) received by the AP/BHM at the Ethernet Interface over the

collection interval

o outOctets – Number of octets (bytes) sent by the AP/BHM at the Ethernet Interface over the

collection interval

o inPkts – Number of packets received by the AP/BHM at the Ethernet Interface over the collection

interval

o outPkts – Number of packets sent by the AP/BHM at the Ethernet Interface over the collection

interval

o Discards (in/out) – Number of packets that had to be discarded by the AP/BHM at the respective

Ethernet Interface Queue

 RF Statistics - Statistics collected at the RF Interface:

o inOctets – Number of octets (bytes) received by the AP/BHM at the RF Interface over the

collection interval

o outOctets – Number of octets (bytes) sent by the AP/BHM at the RF Interface over the collection

interval

o inPkts – Number of packets received by the AP/BHM at the RF Interface over the collection

interval

Chapter 9: Operation System statistics

Page 9-8

o outPkts – Number of packets sent by the AP/BHM at the RF Interface over the collection interval

o Discards (in/out) – Number of packets that had to be discarded by the AP/BHM at the respective

RF Interface Queue during the collection interval

o Discards % (in/out) – Percent of the total packets received / transmitted that had to be discarded

during the collection interval

LUID RF Throughput statistics

This table contains a row that corresponds to each active LUID served by the AP/BHM. Note that an LUID

may be assigned 1 or 2 VCs. If the LUID is assigned 2 VCs, then the data in the table is the sum of the

activity for both VCs. This table may be used to determine which LUIDs are experiencing overload so that

corrective action can be taken (i.e. fixing a poor RF link or moving a heavily loaded link to a less

congested AP/BHM). Each row contains counters and statistics related to the RF Interface that are

updated once per minute:

 Inbound Statistics - Statistics collected at the RF Interface for the Uplink:

o octets – Number of octets (bytes) received by the AP/BHM at the RF Interface for this LUID over

the collection interval

o pkts – Number of packets received by the AP/BHM at the RF Interface for this LUID over the

collection interval

o Ave Pkt Size – Average size of the packets received by the AP/BHM at the RF Interface for this

LUID over the collection interval

o discards – Number of packets received by the AP/BHM at the RF Interface for this LUID over the

collection interval that had to be discarded because the RF In Queue was full

o discards % – Percent of the total packets received by the AP/BHM at the RF Interface for this

LUID over the collection interval that had to be discarded because the RF In Queue was full

 Outbound Statistics - Statistics collected at the RF Interface for the Downlink:

o octets – Number of octets (bytes) transmitted by the AP/BHM at the RF Interface for this LUID

over the collection interval

o pkts – Number of packets transmitted by the AP/BHM at the RF Interface for this LUID over the

collection interval

o Ave Pkt Size – Average size of the packets transmitted by the AP/BHM at the RF Interface for

this LUID over the collection interval

o discards – Number of packets to be transmitted by the AP/BHM at the RF Interface for this LUID

over the collection interval that had to be discarded because the RF Out Queue was full

o discards % – Percent of the total packets to be transmitted by the AP/BHM at the RF Interface

for this LUID over the collection interval that had to be discarded because the RF Out Queue was

full.

Chapter 9: Operation System statistics

Page 9-9

Interpreting Overload statistics

The Statistics > Overload page displays statistics on packet overload and resultant packet discards.

Unlike the other fields, the Total Packets Overload Count is expressed in only this page. It is not a count

of how many packets have been lost, but rather of how many discard events (packet loss bursts) have

been detected due to overload condition.

This statistics page is applicable for all modules (AP/SM/BHM/BHS) and explained in Table 231.

Table 231 Overload page attributes – AP/SM/BHM/BHS

Attribute Meaning

Total Packets

Overload Count

This field represents the sum of all RF and Ethernet in/out discards.

Ethernet In Discards This field represents the number of packets tossed due to the Ethernet queue

being full. If a climb in this stat accompanies a climb in RF Out Discards stat,

then most likely the board is at RF capacity either due to traffic exceeding the

RF pipe, or interference temporarily limiting the RF throughput. If this stat

climbs without the RF Out Discards stat climbing, then the radio is most likely

PPS limited.

Ethernet Out Discards This field represents the number of packets tossed due to an Ethernet out

overload. This stat must not climb in normal operation because the Ethernet

link is much higher capacity than the RF link. If this stat is incrementing, then

either the Ethernet link is established at a low speed (i.e. 10Mbps – half

duplex), or there is a problem with cabling/Ethernet hardware.

RF In Discards This field indicates the number of packets tossed due to no resources

available within the radio to process them. This stat also must not be

increasing because the system is designed to shed packets on the RF Out

interface. If this stat is incrementing the board, it is most likely congested due

to high PPS rate in combination with an Ethernet Out problem, which limits

packet flow off the device.

Chapter 9: Operation System statistics

Page 9-10

RF Out Discards This field indicates the number of packets tossed due to RF link at capacity.

This stat will increase whenever the RF link is at capacity. When the internal

FPGA RF input queue overflows, this stat is incremented. If this stat is seen

to be incrementing at the AP, then the sector is congested. If seen at the SM,

the number of Contention Slots must be looked at to ensure that enough

Contention Slots are allocated to allow for bandwidth requests to be seen at

the AP.

Note

450m Overload:

The 450m Series AP is designed to handle high load in terms of high throughput and high

PPS. In terms of throughput, 450m is designed to achieve 3x or more throughput

improvement over 450 and 450i Series products. In terms of packets per second (PPS),

450m is designed to handle up to 100k PPS.

Overload occurs when the offered load exceeds the above limits. When overload occurs,

450m will start discarding packets and TCP throughput will degrade due to packet loss.

It’s worth noting that Frame Utilization statistics (Statistics > Frame Utilization tab: Frame

Utilization: Downlink and Uplink) are not necessarily indicative of overload condition. They

show how much the TDD frame is utilized. High frame utilization depends on:

 High traffic during busy periods: those statistics will be close to 100% and almost all

slots will be utilized. In this case if the Overload statistics show that packets are

discarded then this is an indication of overload condition.

 High percentage of VCs with low modulation with moderate traffic. Those VCs will

require more slots to service them (due to low modulation) and the frame utilization will

be high. In this case the TDD frame is fully utilized but the system is at low capacity and

is not in an overload condition.

450m has higher PPS than 450 and 450i and supports higher throughput through spatial

multiplexing, therefore when a 450m replaces an overloaded 450 or 450i AP the 450m will

not be overloaded under the same conditions but the frame utilization may still show close to

100%; this should not alarm the customer. The overload statistics shall be monitored on

450m to see if it is overloaded or not.

Interpreting DHCP Relay statistics

The Statistics > DHCP Relay page displays requests and replies received, relayed and discarded when

the AP is configured as a DHCP relay. Typically, in a working DHCP relay configuration a one-to-one ratio

is established between requests and replies that are received and relayed. This statistics page is only

applicable for PMP (AP and SM modules) and it is explained in Table 232.

Chapter 9: Operation System statistics

Page 9-11

Table 232 DHCP Relay page attributes – AP/SM

Attribute Meaning

Requests Received This field represents the number of DHCP relay requests received by the AP.

Requests Relayed This field represents the number of DHCP relay requests relayed by the AP.

Requests Discarded This field represents the number of DHCP relay requests discarded by the AP

due to errors in the request.

Replies Received This field represents the number of DHCP relay replies received by the AP.

Replies Relayed This field represents the number of DHCP relay replies relayed by the AP.

Replies Discarded This field represents the number of DHCP relay replies discarded by the AP

due to errors in the reply.

Untrusted Message

Discards

This field indicates messages that were discarded because the message

already contained Option 82 information with no Relay Agent specified.

Max Hop Exceeded

Discards

This field indicates messages that have been relayed too many times,

exceeding the max hop count (16).

Invalid Relay Agent

Address Discards

This field indicates messages that have been discarded because the

message relay agent address is already in place (relay agent address does

not equal address of the AP).

Relay Info Exceeding

Max Message Size

(DHCP message

relayed without Option

82)

This field indicates DHCP messages too large to fit Option 82 data. These

messages are sent on without Option 82 information.

Chapter 9: Operation System statistics

Page 9-12

Interpreting Filter statistics

The Statistics > Filter page displays statistics on packets that have been filtered (dropped) due to the

filters set on the Protocol Filtering page. The filter page of SM is explained in Table 233.

Table 233 Filter page attributes - SM

Attribute Meaning

PPPoE Count Number of PPPoE packets filtered.

All IPv4 Count Number of IPv4 packets filtered.

All Other IPv4 Count Any IPv4 message that was not SMB, SNMP, Bootp, Multicast or one of

the user defined filters, that was filtered out.

SMB Count Number of IPv4 Server Message Block (file sharing) packets filtered.

SNMP Count Number of IPv4 SNMP packets filtered.

Bootp Client Count Total number of IPv4 DHCP requests filtered.

Bootp Server Count Total number of IPv4 DHCP replies filtered.

IPv4 Multicast Count Number of IPv4 Multicast messages filtered.

All IPv6 Count Number of IPv6 messages filtered.

All Other IPv6 Count Any IPv6 message that was not SMB, SNMP, Bootp, Multicast or one of

the user defined filters, that was filtered out.

IPv6 SMB Count Number of IPv6 Server Message Block (file sharing) packets filtered

IPv6 SNMP Count Number of IPv6 SNMP messages filtered

IPv6 Bootp Client Count Total number of IPv6 DHCP replies filtered

IPv6 Bootp Server Count Total number of IPv6 DHCP replies filtered

IPv6 Multicast Count Number of IPv6 Multicast messages filtered

Chapter 9: Operation System statistics

Page 9-13

ARP Count Total number of ARP packets filtered.

All other Count The count of any messages that did not fit above that were filtered out

User Defined Port1 Count Number of packets defined by the user port1 that were filtered.

User Defined Port2 Count Number of packets defined by the user port2 that were filtered.

User Defined Port3 Count Number of packets defined by the user port3 that were filtered.

Viewing ARP statistics

The Statistics > ARP page in a SM module correlated the IP address of the Ethernet-connected device

to its MAC address and provides data about the connection.

Figure 200 ARP page of the SM

Viewing NAT statistics

When NAT is enabled on a SM, statistics are kept on the Public and Private (WAN and LAN) sides of the

NAT and displayed on the Statistics > NAT Stats page. The NAT page of SM is explained in Table 234.

Chapter 9: Operation System statistics

Page 9-14

Table 234 NAT page attributes - SM

Attribute Meaning

Private NAT Statistics,

Packet In Count

This field represents the number of packets received on the SM’s

LAN/Ethernet interface

Private NAT Statistics,

Packet Out Count

This field represents the number of packets sent from the SM’s

LAN/Ethernet interface

Private NAT Statistics,

Packet Out Toss Count

This field represents the number of packets that we not sent from the

SM’s LAN/Ethernet interface due to addressing issues.

Private NAT Statistics,

Out of Resources Count

This field represents the number of times the NAT table for the SM’s

LAN/Ethernet interfaces has been filled.

Private NAT Statistics,

Failed Hash Insert Count

This field represents the number of times that the device failed to insert an

address binding into the NAT hash table.

Public NAT Statistics,

Packet In Count

This field represents the number of packets received on the SM’s

WAN/wireless interface

Public NAT Statistics,

Packet Out Count

This field represents the number of packets sent from the SM’s

WAN/wireless interface

Public NAT Statistics, Out

of Resources Count

This field represents the number of packets that we not sent from the

SM’s WAN/wireless interface due to addressing issues.

Public NAT Statistics,

Failed Hash Insert Count

This field represents the number of times the NAT table for the SM’s

WAN/wireless interfaces has been filled.

Chapter 9: Operation System statistics

Page 9-15

Viewing NAT DHCP Statistics

The Statistics > NAT DHCP page displays NAT enabled DHCP client statistics. This is statistics page is

applicable for SM only.

When NAT is enabled on a SM with DHCP client (DHCP selected as the Connection Type of the WAN

interface) and/or DHCP Server, statistics are kept for packets transmitted, received and tossed, as well as

a table of lease information for the DHCP server (Assigned IP Address, Hardware Address and Lease

Remained/State).

Table 235 NAT DHCP Statistics page attributes - SM

Attribute Meaning

PktXmt Count Represents the number of DHCP packets transmitted from the client

PktRcv Count This field represents the number of DHCP packets received by the client

PktToss

ARPUnresolved

Overflow Count

This field represents the number of packets tossed due to failed attempts to

resolve an IP address into a physical MAC address

PktToss Unsupported

MsgType Count

This field represents the number of packets tossed due to the receipt of an

unsupported message type (cannot be interpreted by DHCP client)

PktToss XID

Mismatch Count

The field represents the number of packets that were tossed due to a

transaction ID mismatch

PktToss NoSID Count This field represents the number of packets that were tossed due to lack of a

DHCP session ID

PktToss SID

Mismatch Count

Represents the number of packets tossed due to a session ID mismatch

Chapter 9: Operation System statistics

Page 9-16

Failure to Reset Client

Count

This field represents the number of times the DHCP client was unable to be

reset (resulting in no IP address being served).

Interpreting Sync Status statistics

The Statistics > Sync Status page of AP is only displayed when the Sync Input is set to AutoSync or

AutoSync+Free Run.

The Sync Status page is explained in Table 236.

Table 236 Sync Status page attributes - AP

Attribute Meaning

Sync Pulse Source This field indicates the status of the synchronization source:

 Searching indicates that the unit is searching for a GPS fix

 Timing Port/UGPS indicates that the module is receiving sync via the

timing AUX/SYNC timing port

 Power Port indicates that the module is receiving sync via the power port

(Ethernet port).

Sync Pulse Status This field indicates synchronization source pulse status.

Sync Pulse Status –

Timing Port/UGPS

This field indicates synchronization pulse status over Timing Port/UGPS port.

Sync Pulse Status -

Power Port

This field indicates synchronization pulse status over power port.

UGPS Power Status This field indicates UGPS power up status (on or off).

This information may be helpful in a decision of whether to climb a tower to diagnose a perceived antenna

problem.

Chapter 9: Operation System statistics

Page 9-17

Interpreting PPPoE Statistics for Customer Activities

The page can be access under Statistics > PPPoE of SM GUI.

When the PPPoE feature is enabled on the SM, PPPoE statistics provide data about activities of the

customer.

The PPPoE Statistics of SM is explained in Table 237.

Table 237 PPPoE Statistics page attributes - SM

Attribute Meaning

IP address This field displays the IP address of the PPPoE session initiator (situated

below the SM)

PPPoE Session

Status

This field displays the operational status of the PPPoE Session

PPPoE AC Name This field displays access concentrator name used in the PPPoE session

PPPoE Service Name This field displays the PPPoE service name associated with the PPPoE

server in use

PPPoE Session ID This field displays the current PPPoE session ID

PPPoE Session

Uptime

This field displays the total session uptime for the PPPoE session

PPPoE Session Idle

Time

This field displays the total idle time for the PPPoE session

PPPoE Session MTU This field displays Maximum Transmission Unit configured for the PPPoE

session

Primary DNS Address This field displays the primary DNS server used by the PPPoE session

Secondary DNS

Address

This field displays the secondary DNS server used by the PPPoE session

Chapter 9: Operation System statistics

Page 9-18

PPPoE Control Bytes

Sent

Displays the total number of PPPoE session control bytes sent from SM

PPPoE Control Bytes

Received

This field displays the total number of PPPoE session control bytes received

by the SM

PPPoE Data Session

Bytes Sent

This field displays the total number of PPPoE data session (non-control/non-

session management user data) sent by the SM

PPPoE Data Session

Bytes Received

This field displays the total number of PPPoE data session (non-control/non-

session management user data)

Chapter 9: Operation System statistics

Page 9-19

Interpreting Bridge Control Block statistics

The Statistics > Bridge Control Block page displays statistics of Bridge FEC, Bridge ratio and Bridge

error. The page is applicable for all modules (AP/SM/BHM/BHS). The Bridge Control Block Statistics page

is explained in Table 238.

Table 238 Bridge Control Block page attributes – AP/SM/BHM/BHS

Attribute Meaning

Bridge FEC Stats

Chapter 9: Operation System statistics

Page 9-20

FEC bin This field indicates the number of broadcast packets received by the bridge

control block on the Main Ethernet interface

FEC bout This field indicates the number of broadcast packets sent by the bridge

control block on the Main Ethernet interface

FEC btoss This field indicates the number of broadcast packets tossed out by the bridge

control block on the Main Ethernet interface

FEC btosscap This field indicates the number of broadcast packets tossed out at the Main

Ethernet interface due to MIR cap being exceeded.

FEC uin This field indicates the number of unicast packets received by the bridge

control block on the Main Ethernet interface

FEC uout This field indicates the number of unicast packets sent by the bridge control

block on the Main Ethernet interface

FEC utoss This field indicates the number of unicast packets tossed by the bridge control

block on the Main Ethernet interface

FEC utosscap This field indicates the number of unicast packets tossed out at the Main

Ethernet interface due to MIR cap being exceeded.

Bridge Eth Aux Stats

FEC bin This field indicates the number of broadcast packets received by the bridge

control block on the Aux Ethernet interface

FEC bout This field indicates the number of broadcast packets sent by the bridge

control block on the Aux Ethernet interface

FEC btoss This field indicates the number of broadcast packets tossed out by the bridge

control block on the Aux Ethernet interface

FEC btosscap This field indicates the number of broadcast packets tossed out at the Aux

Ethernet interface due to MIR cap being exceeded.

FEC uin This field indicates the number of unicast packets received by the bridge

control block on the Aux Ethernet interface

FEC uout This field indicates the number of unicast packets sent by the bridge control

block on the Aux Ethernet interface

FEC utoss This field indicates the number of unicast packets tossed by the bridge control

block on the Aux Ethernet interface

FEC utosscap This field indicates the number of unicast packets tossed out at the Aux

Ethernet interface due to MIR cap being exceeded.

Bridge Radio Stats

RF bin This field indicates the number of broadcast packets received by the bridge

control block on the radio interface

Chapter 9: Operation System statistics

Page 9-21

RF bout This field indicates the number of broadcast packets sent by the bridge

control block on the radio interface

RF btoss This field indicates the number of broadcast packets tossed by the bridge

control block on the radio interface

RF btosscap This field indicates the number of broadcast packets tossed out at the radio

interface due to MIR cap being exceeded.

RF uin This field indicates the number of unicast packets received by the bridge

control block on the radio interface

RF uout This field indicates the number of unicast packets sent by the bridge control

block on the radio interface

RF utoss This field indicates the number of unicast packets tossed by the bridge control

block on the radio interface

RF utosscap This field indicates the number of unicast packets tossed out at the radio

interface due to MIR cap being exceeded.

Bridge Error Stats

ErrNI1QSend This field indicates that a packet which was sourced from the radio network

stack interface 1 (Ethernet interface) could not be sent because the radio

bridge queue was full. The packet was tossed out.

ErrNI2QSend This field indicates that a packet which was sourced from the radio network

stack interface 2 (RF interface) could not be sent because the radio bridge

queue was full. The packet was tossed out.

ErrBridgeFull This field indicates the total number of times the bridging table was full and

could not accept new entries.

ErrSendMsg This field displays the error message from bridge core call back routine.

ErrApFecQSend This field indicates that a packet which was received on the Ethernet interface

could not be processed because the radio bridge queue was full and packet

was tossed out.

ErrApRfQSend This field indicates that a packet which was received on the RF interface

could not be processed because the radio bridge queue was full. The packet

was tossed out.

Note:

PMP 450m Series AP does not support Aux port in current release of 15.0/15.0.0.1.

Chapter 9: Operation System statistics

Page 9-22

Interpreting Pass Through Statistics

The Statistics > Pass Through Statistics page displays radius related statistics. The page is applicable

for PMP 450 Platform Family - AP only. The Pass Through Statistics page is explained in Table 239.

Table 239 Pass Through Statistics page attributes – AP

Attribute Meaning

IdentityReqSent This field indicates the number of EAP Identity requests sent through

the AP with respect to an SM.

PktsEncapsulated This field indicates no of packets received from the SM which are

encapsulated by the AP.

PktsDecasulated This field indicates no of packets received from the radius server and

are decapsulated by the AP with respect to an SM

AccessAcceptRcvd This field indicates no of RADIUS Access Accept message received

by the AP with respect to an SM.

Chapter 9: Operation System statistics

Page 9-23

Interpreting SNMPv3 Statistics

The Statistics > SNMPv3 Statistics page displays all SNMPv3 related statistics. The page is applicable

for all type of ODUs of PMP 450 Platform. The SNMPv3 Statistics page is explained in Table 240.

Table 240 SNMPv3 Statistics page attributes – AP

Attribute Meaning

Statistics for

snmpMPDStats group SNMP Message Processing and Dispatching RFC 3412

Chapter 9: Operation System statistics

Page 9-24

snmpUnknownSecurityMod

els

The total number of packets received by the SNMP engine which

were dropped because they referenced a securityModel that was not

known to or supported by the SNMP engine.

snmpInvalidMsgs The total number of packets received by the SNMP engine which

were dropped because there were invalid or inconsistent components

in the SNMP message.

snmpUnknownPDUHandler

The total number of packets received by the SNMP engine which

were dropped because the PDU contained in the packet could not be

passed to an application responsible for handling the pduType, e.g.

no SNMP application had registered for the proper combination

of the contextEngineID and the pduType.

usmStatsUnsupportedSecL

evels

The total number of packets received by the SNMP engine which

were dropped because they requested a securityLevel that was

unknown to the SNMP engine or otherwise unavailable.

usmStatsNotInTimeWindow

The total number of packets received by the SNMP engine which

were dropped because they appeared outside of the authoritative

SNMP engine's window.

usmStatsUnknownUserNa

mes

The total number of packets received by the SNMP engine which

were dropped because they referenced a user that was not known to

the SNMP engine.

usmStatsUnknownEngineI

The total number of packets received by the SNMP engine which

were dropped because they referenced a snmpEngineID that was not

known to the SNMP engine.

usmStatsWrongDigests The total number of packets received by the SNMP engine which

were dropped because they didn't contain the expected digest value.

usmStatsDecryptionErrors The total number of packets received by the SNMP engine which

were dropped because they could not be decrypted.

snmpTargetSpinLock This object is used to facilitate modification of table entries in the

SNMP-TARGET-MIB module by multiple managers.

snmpUnavailableContexts The total number of packets received by the SNMP engine which

were dropped because the context contained in the message was

unavailable.

snmpUnknownContexts The total number of packets received by the SNMP engine which

were dropped because the context contained in the message was

unknown.

usmUserSpinLock The use of usmUserSpinlock is to avoid conflicts with another SNMP

command generator application which may also be acting on the

usmUserTable.

Chapter 9: Operation System statistics

Page 9-25

vacmViewSpinLock An advisory lock used to allow cooperating SNMP Command

Generator applications to coordinate their use of the Set operation in

creating or modifying views.

snmpEngineBoots It is a count of the number of times the SNMP engine has re-

booted/re-initialized since snmpEngineID was last configured

snmpEngineTime

time since engine is up

which is the number of seconds since the snmpEngineBoots counter

was last incremented

Interpreting syslog statistics

The Statistics > Syslog Statistics page displays statistics of syslog messages. The page is applicable

for all modules (AP/SM/BHM/BHS). The Syslog Statistics page is explained in Table 241.

Table 241 Syslog statistics page attributes – AP/SM/BH

Attribute Meaning

Syslog Server This displays dotted decimal or DNS name (if the DNS is enabled) of

the syslog server address.

Syslog Server Port The syslog server port (default 514) to which syslog messaging is

sent.

Syslog Status This indicates status of syslog messaging. It can be Enable or

Disabled based on configuration

Syslog Message

Transmissions This field indicates the count of syslog messages sent to UDP layer.

Syslog Message Dropped This field indicates the count of dropped syslog messages.

Interpreting Frame Utilization statistics

The Frame Utilization Statistics is a feature helps user to understand how effectively the RF channel is

being utilized. This feature allows to check Time Division Duplex (TDD) frame utilization pattern and

diagnose for any excessive usage in uplink or downlink direction.

This forms the first step of identifying the TDD frame utilization information. If the user finds excessive

utilization based on this stats, the second step would be to take several actions like sectorization, tuning

the uplink/downlink ratio etc. to improve RF channel utilization. Efficient use of the TDD frame will help to

achieve optimum performance of link.

Chapter 9: Operation System statistics

Page 9-26

Note

The backhauls (BHM and BHS) will have only the downlink scheduler based statistics

Table 242 Frame utilization statistics for PMP 450m AP

Chapter 9: Operation System statistics

Page 9-27

Chapter 9: Operation System statistics

Page 9-28

Attribute Meaning

Frame Utilization Interval

Statistics Display interval This allows to configure timer interval to monitor and display the

frame utilization statistics. It can be configured for 1 minute (low

interval), 5 minutes (medium interval) or 15 minutes (high interval)

based on requirement.

MU-MIMO Utilization

Spatial Utilization This is a table (32 rows) that lists frame utilization for each spatial

frequency (SF) range with following information:

 Spatial frequency: Range of spatial frequency for each bin.

Each bin includes 32 consecutive spatial frequency values.

 Azimuth (degrees): Azimuth range in degrees corresponding to

the spatial frequencies of the bin. The zero degree azimuth is

boresight.

Note:

Some SF ranges correspond to multiple azimuth ranges.

This is due to the fact that for some spatial frequencies

the AP generates beams in multiple azimuth directions.

The SM can be physically located in any of the azimuth

ranges.

Spatial Utilization  Instantaneous (%): Frame utilization for the SF bin, updated

every 500 ms. The frame utilization percentage accounts for all

traffic, both sector mode and MU-MIMO transmissions.

 Total (%): Average utilization in the SF bin for the past 1/5/15

minutes, as selected in the Statistics Display Interval.

 Max (%): Maximum Instantaneous utilization in the 1/5/15 minute

interval

 Min (%): Minimum Instantaneous utilization in the 1/5/15 minute

interval

 VCs in Range: List of VCs with spatial frequency falling in the

bin.

Note:

The size of each SF bin is smaller than the beam

generated by the AP during a MU-MIMO transmission.

This means that when a VC in a bin is scheduled for a

MU-MIMO transmission, the adjacent bins also receive

the signal, and the transmission is counted towards their

utilization as well. Bins with consistent low utilization

indicate the areas of the sector where more SMs could

be installed, or the customers that could be offered

higher data plans.

Chapter 9: Operation System statistics

Page 9-29

Grouping This specifies the distribution of group size for the past 1/5/15

minutes. For each group size, from 0 to 7, the table shows the

percentage of slots using that group size.

 A group size of 0 corresponds to unused slots.

 A group size of 1 corresponds to sector mode transmissions

(ungrouped).

 A group size of 2 to 7 corresponds to MU-MIMO transmissions.

Instantaneous Distribution This table is updated every 500 ms and displays the following:

 Group: Each row corresponds to the top (most active) 1, 2, 4, 8,

16, 32, 64, 128, and 256 VCs.

 Median Slot Count: Median value of the average number of slots

scheduled for the VCs in each group in the past 500 ms.

 VCs in Group: List of VCs belonging to each bin where each bin

includes all VCs listed in preceding rows along with the VCs

listed in the corresponding row.

For example, the row labeled “Top 32 VCs” considers up to 32

VCs, which are: one VC listed in “Top VC” row, plus one VC

listed in “Top 2 VCs” row, plus 2 VCs listed in “Top 4 VCs” row,

plus four VCs listed in “Top 8 VCs” row, plus 8 VCs listed in “Top

16 VCs” rows, plus up to 16 VCs listed in “Top 32 VCs” row. If

the number of VCs in the sector is less than 32, this row will

include less than 16 VCs; if the number of VCs in the sector is

equal to or greater than 32, this row will include 16 VCs.

Note:

For best MU-MIMO operation, the distribution of the

median values in this table should be as close to flat as

possible. If many VCs are equally active, there is a

higher probability of being able to group their

transmissions. If only a few VCs are active, the

probability of grouping transmissions is lower, and both

the Average MU-MIMO Group size and the Multiplexing

Gain are expected to be lower.

Average MU-MIMO Group

Size

This specifes the average number of users in the MU-MIMO groups

formed in the last 1/5/15 minutes.

Sector Utilization This specifes the average of the 32 values of the Spatial Utilization

table.

MU-MIMO Utilization This specifies the portion of the Sector Utilization used for MU-MIMO

transmissions.

SU-MIMO Utilization This specifies the portion of the Sector Utilization used for SU-MIMO

transmissions.

Chapter 9: Operation System statistics

Page 9-30

Canopy MAC

Acknowledgment Utilization

This specifies the portion of the Sector Utilization used for

acknowledgments transmission.

Broadcast/Multicast

Utilization

This specifies the portion of the Sector Utilization used for broadcast

and multicast transmissions.

Multiplexing Gain This specifies the ratio between the number of logical slots and the

number of physical slots used.

A physical slot is an OFDM symbol. In non MU-MIMO mode, each

logical slot is sent during one physical slot. In MU-MIMO mode a

number of logical slots are sent during a physical slot, equal to the

number of VCs in the group. A logical slot carries new information; if

data is repeated in a group, because some VCs have more data to

send then others, then the repeated transmissions are not counted as

a logical slots.

Without MU-MIMO operation, the multiplexing gain would always be

equal to 1.

With MU-MIMO operation, this number accounts for parallel

transmissions to multiple users in the MU-MIMO group.

The difference between the Average MU-MIMO Group Size and the

Multiplexing Gain is that the Average MU-MIMO Group Size only

considers the MU-MIMO groups, and it averages the number of VCs

in the Group. The Multiplexing Gain also considers non MU-MIMO

transmissions, which are counted as groups of size 1.

Frame Utilization

Downlink This indicates the percentage of downlink data slots used against the

maximum number of slots possible in the configured interval.

Uplink This indicates the percentage of uplink data slots used against the

maximum number of uplink slots possible in the configured interval.

Bandwidth Requests The "Bandwidth Request" is a message sent from the SM to the AP

asking to be scheduled for bandwidth to send in the uplink. This gets

transmitted in the unscheduled portion of the uplink. Unscheduled

uplink is defined as Contention Slots + unscheduled uplink slots.

Since this is sent in the unscheduled portion of the uplink, it will result

in collisions when SMs randomly pick the same slot.

The "Bandwidth Request Missed" metrics are to add data to know

how many of requests are colliding. If it is near 100%, then near all of

the SM’s bandwidth requests are getting through to the AP, so this a

is near perfect scenario. If it is significantly less than that, you may be

experiencing uplink latency as your SMs are attempting to request

bandwidth and are unable to do so.

Also note that if it is consistently at 100% the AP may be able to

reduce its contention slots to a lower value and gain more data slots.

Chapter 9: Operation System statistics

Page 9-31

Downlink Counts

Total This indicates the sum of all downlink data slots used in the

configured interval.

Per Frame Average This indicates the average data per frame in the downlink traffic.

Low Priority The number of downlink data slots used for low priority downlink

traffic.

High Priority The number of downlink data slots used for high priority downlink

traffic.

Broadcast/Multicast The number of downlink data slots used for broadcast and multicast

traffic.

Canopy MAC

Acknowledgements

The number of downlink data slots used as ACKs.

Registration Messages The number of downlink data slots used for registration messages.

Uplink Counts

Total This indicates the sum of all uplink data slots used in configured

interval.

Per Frame Average This indicates the average data per frame in the uplink traffic.

Low Priority The number of uplink data slots used for low priority uplink traffic.

High Priority The number of uplink data slots used for high priority uplink traffic.

Canopy MAC

Acknowledgements

The number of uplink data slots used as ACKs.

Contention Slots The number of (reserved contention slots + unscheduled symbols

that can be used as contention slots) Contention slots configured by

the operator.

Contention Slots Average

Per Frame

It is the average number of contention slots in a frame for the last

duration. Duration is 1/5/15 mins.

Bandwidth Requests

Received

This indicates the number of Bandwidth Requests received from

SMs.

Bandwidth Requests

Missed

This indicates how many of Bandwidth Requests are colliding.

Maximum possible counts

Downlink This indicates the maximum possible downlink data slots in the

configured interval. This is based on the configuration of Channel

Bandwidth, Frame period, uplink/downlink allocation, contention slots

and configured Statistics Display interval.

Chapter 9: Operation System statistics

Page 9-32

Uplink This indicates the maximum possible uplink data slots in the

configured interval. This is based on the configuration of Channel

Bandwidth, Frame period, uplink/downlink allocation, contention slots

and configured Statistics Display interval.

Contention This indicates the maximum possible contention slots.

Packet Discard counts

Ethernet indiscards This indicates the number of Ethernet packets discarded in the IN

queue.

Ethernet outdiscards This indicates the number of Ethernet packets discarded in the OUT

queue.

Radio indiscards This indicates the number of packets discarded over radio in the IN

queue.

Radio outdiscards This indicates the number of packets discarded over radio in the OUT

queue.

Chapter 9: Operation System statistics

Page 9-33

Table 243 Frame utilization statistics for 450/450i/450m

Attribute Meaning

Frame Utilization Interval

Statistics Display interval This allows to configure timer interval to monitor and display the

frame utilization statistics. It can be configured for 1 minute (low

interval), 5 minutes (medium interval) or 15 minutes (high interval)

based on requirement.

Frame Utilization