User's Manual
Table Of Contents
- Cambium
- PMP 450 Operations Guide
- Safety and regulatory information
- Contents
- List of Figures
- List of Tables
- PMP support website: http://www.cambiumnetworks.com/support
- Cambium main website: http://www.cambiumnetworks.com/
- Sales enquiries: solutions@cambiumnetworks.com
- Email support: support@cambiumnetworks.com
- Cambium Networks
- 3800 Golf Road, Suite 360
- Rolling Meadows, IL 60008
- Growing Your Network
- Managing Bandwidth and Authentication
- Configuring quality of service
- Maximum Information Rate (MIR) Parameters
- Token Bucket Algorithm
- Maximum Information Rate Data Entry Checking
- Bandwidth from the SM Perspective
- Interaction of Burst Allocation and Sustained Data Rate Settings
- High-priority Bandwidth
- Traffic Scheduling
- Setting the Configuration Source
- Quality of Service (QoS) Tab of the AP
- DiffServ Tab of the AP
- Quality of Service (QoS) Tab of the SM
- DiffServ Tab of the SM
- Configuring a RADIUS server
- Understanding RADIUS for PMP 450
- Choosing Authentication Mode and Configuring for Authentication Servers - AP
- SM Authentication Mode – Require RADIUS or Follow AP
- Handling Certificates
- Configuring your RADIUS servers for SM authentication
- Configuring your RADIUS server for SM configuration
- Using RADIUS for centralized AP and SM user name and password management
- RADIUS Device Data Accounting
- RADIUS Device Re-Authentication
- RADIUS Attribute Framed-IP-Address
- Configuring quality of service
- Managing the network from a Network Management Station (NMS)
- Using Informational Tabs in the GUI
- Viewing General Status (AP)
- Viewing General Status (SM)
- Viewing Session Status (AP)
- Viewing Remote Subscribers (AP)
- Interpreting messages in the Event Log
- Viewing the Network Interface Tab (All)
- Viewing the Layer 2 Neighbors Tab (AP and SM)
- Viewing the Scheduler Tab (AP and SM)
- List of Registration Failures (AP)
- Interpreting Data in the Bridging Table (All)
- Translation Table (SM)
- Interpreting Data in the Ethernet Tab (All)
- Interpreting RF Control Block Statistics in the Radio Tab (All)
- Interpreting Data in the VLAN Tab (ALL)
- Viewing Data VC Statistics (All)
- Viewing Summary Information in the Overload Tab (All)
- Viewing Filter Statistics (SM)
- Viewing ARP Statistics (SM)
- Viewing NAT Statistics (SM)
- Viewing NAT DHCP Statistics (SM)
- Interpreting Data in the GPS Status Page (AP)
- Accessing PPPoE Statistics About Customer Activities (SM)
- Viewing Bridge Control Block Statistics (All)
- Using Tools in the GUI
- Using the Spectrum Analyzer Tool
- Graphical spectrum analyzer display
- Using the AP as a Spectrum Analyzer
- Using the Remote Spectrum Analyzer Tool (AP)
- Using the Alignment Tool (SM)
- Using the Link Capacity Test Tool (AP or SM)
- Using the AP Evaluation Tool (SM)
- Using the OFDM Frame Calculator Tool for Collocation (AP or SM)
- Using the Subscriber Configuration Tool (AP)
- Reviewing the Link Status Tool Results (AP)
- Using the BER Results Tool (SM)
- Using the Throughput Monitoring Tool (AP)
- Using the Sessions Tool (AP)
- Maintaining Your Software
- Troubleshooting
- General planning for troubleshooting
- General fault isolation process
- Secondary Steps
- Procedures for Troubleshooting
- Module Has lost or does not establish connectivity
- NAT/DHCP-configured SM has lost or does not establish connectivity
- SM Does Not Register to an AP
- Module has lost or does not gain sync
- Module does not establish Ethernet connectivity
- Module does not power on
- Power supply does not produce power
- CMM does not pass proper GPS sync to connected modules
- Module Software Cannot be Upgraded
- Module Functions Properly, Except Web Interface Became Inaccessible
- Reference information
Configuring quality of service
PMP 450 Operations Guide
2-4
pmp-0049 (September 2012)
High-priority Bandwidth
To support low-latency traffic such as VoIP (Voice over IP) or video, the system implements a high-
priority channel. This channel does not affect the inherent latencies in the system but allows high-
priority traffic to be immediately served. The high-priority pipe separates low-latency traffic from
traffic that is latency tolerant, such as standard web traffic and file downloads.
The number of channels available to the AP is reduced by the number of SMs configured for the high-
priority channel. With high priority channel enabled on all SMs, the total sector capacity is reduced
by 50%.
A module prioritizes traffic by
reading the Low Latency bit (Bit 3) in the IPv4 Type of Service (ToS) byte in a received packet.
Bit 3 is set by a device outside the system.
reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the
module.
comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received
packet to a corresponding value in the Diffserv tab of the Configuration page of the module. A
packet contains no flag that indicates whether the encoding is for the Low Latency bit or the
DSCP field. For this reason, you must ensure that all elements in your trusted domain, including
routers and endpoints, set and read the ToS byte with the same scheme.
Modules monitor ToS bytes with DSCP fields, but with the following differences:
The 6-bit length of the field allows it to specify one of 64 service differentiations.
These correlate to 64 individual (CodePoint) parameters in the Diffserv tab of the
Configuration page.
Per RFC 2474, 3 of these 64 are preset and cannot be changed. (See
http://www.faqs.org/rfcs/rfc1902.html.)
For any or all of the remaining 61 CodePoint parameters, you can specify a value of
o 0 through 3 for low-priority handling.
o 4 through 7 for high-priority handling.
Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as
needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft
of service level.
An example of the Diffserv tab in the Configuration page and parameter descriptions are provided
under DiffServ Tab of the AP on Page 2-10. This tab and its rules are identical from module type to
module type. However, any of the 61 configurable Code Points can be set to a different value from
module to module, thus defining unique per-hop behavior for some traffic.