You are on page 1of 236

Cambium

PTP 820G
Technical Description
System Release 7.9

phn-3968 001v000

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks
assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the
information obtained herein. Cambium reserves the right to make changes to any products described
herein to improve reliability, function, or design, and reserves the right to revise this document and to
make changes from time to time in content hereof with no obligation to notify any person of revisions
or changes. Cambium does not assume any liability arising out of the application or use of any
product, software, or circuit described herein; neither does it convey license under its patent rights or
the rights of others. It is possible that this publication may contain references to, or information about
Cambium products (machines and programs), programming, or services that are not announced in
your country. Such references or information must not be construed to mean that Cambium intends to
announce such Cambium products, programming, or services in your country.
Copyrights
This document, Cambium products, and 3rd Party software products described in this document may
include or describe copyrighted Cambium 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, 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 copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or
the 3rd Party software supplied material contained in the Cambium products described in this
document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any
manner without the express written permission of Cambium. Furthermore, the purchase of Cambium
products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied
software, except for the normal non-exclusive, royalty free license to use that arises by operation of
law in the sale of a product.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any language or computer language, in any form or by any means,
without prior written permission of Cambium.
License Agreements
The software described in this document is the property of Cambium and its licensors. It is furnished
by express license agreement only and may be used only in accordance with the terms of such an
agreement.
High Risk Materials
Cambium and its supplier(s) specifically disclaim any express or implied warranty of fitness for any
high risk activities or uses of its products including, but not limited to, the operation of nuclear
facilities, aircraft navigation or aircraft communication systems, air traffic control, life support, or
weapons systems (“High Risk Use”). Any High Risk is unauthorized, is made at your own risk and you
shall be responsible for any and all losses, damage or claims arising out of any High Risk Use.

© 2014 Cambium Networks Limited. All Rights Reserved.

phn-3968 001v000

Contents
About This User Guide......................................................................................................................1
Contacting Cambium Networks .................................................................................................. 1
Purpose ......................................................................................................................................... 2
Cross references ........................................................................................................................... 2
Feedback ....................................................................................................................................... 2
Problems and warranty ...................................................................................................................... 3
Reporting problems ..................................................................................................................... 3
Repair and service ........................................................................................................................ 3
Hardware warranty ...................................................................................................................... 3
Security advice .................................................................................................................................... 4
Warnings, cautions, and notes........................................................................................................... 5
Warnings ....................................................................................................................................... 5
Cautions ........................................................................................................................................ 5
Notes ............................................................................................................................................. 5
Caring for the environment ................................................................................................................ 6
In EU countries ............................................................................................................................. 6
In non-EU countries ..................................................................................................................... 6
Chapter 1: Product description ................................................................................................... 1-1
Product Overview............................................................................................................................. 1-2
PTP 820G Radio Options ........................................................................................................... 1-3
PTP 820G Highlights ................................................................................................................. 1-3
PTP 820G Protection Options ................................................................................................... 1-4
Chapter 2: Hardware Description ............................................................................................... 2-1
Hardware Architecture ..................................................................................................................... 2-2
Front Panel Description ................................................................................................................... 2-3
Ethernet Traffic Interfaces ............................................................................................................... 2-4
Ethernet Management Interfaces.................................................................................................... 2-6
DS1/E1 Interface (Optional) ............................................................................................................. 2-8
Radio Interfaces................................................................................................................................ 2-9
Power Interfaces............................................................................................................................. 2-11
Synchronization Interface .............................................................................................................. 2-12
Terminal Interface .......................................................................................................................... 2-13
Unit/ACT LED .................................................................................................................................. 2-14
External Alarms .............................................................................................................................. 2-15
Chapter 3: RFU Overview ........................................................................................................... 3-1
RFU-C ................................................................................................................................................ 3-2
Main Features of RFU-C ............................................................................................................ 3-2

phn-3968 001v000
Page i

Contents

Chapter 4: Activation Keys ......................................................................................................... 4-1
Working with Activation Keys ......................................................................................................... 4-2
Demo Mode License ........................................................................................................................ 4-3
Activation Key-Enabled Features .................................................................................................... 4-4
Chapter 5: Feature Description ................................................................................................... 5-1
Innovative Techniques to Boost Capacity and Reduce Latency ................................................... 5-2
Capacity Summary .................................................................................................................... 5-2
Header De-Duplication .............................................................................................................. 5-3
Latency ....................................................................................................................................... 5-5
Frame Cut-Through ................................................................................................................... 5-5
Radio Features.................................................................................................................................. 5-8
Adaptive Coding Modulation (ACM) ........................................................................................ 5-8
Cross Polarization Interference Canceller (XPIC) .................................................................. 5-11
1+1 HSB Radio Protection....................................................................................................... 5-13
ATPC......................................................................................................................................... 5-15
Multi-Carrier ABC .................................................................................................................... 5-16
BBS Space Diversity ................................................................................................................ 5-18
Radio Utilization PMs .............................................................................................................. 5-19
Ethernet Features ........................................................................................................................... 5-20
Ethernet Services Overview ................................................................................................... 5-20
PTP 820G’s Ethernet Capabilities ........................................................................................... 5-35
Supported Standards .............................................................................................................. 5-36
Ethernet Service Model .......................................................................................................... 5-36
Ethernet Interfaces .................................................................................................................. 5-51
Quality of Service (QoS) ......................................................................................................... 5-60
Global Switch Configuration .................................................................................................. 5-86
Network Resiliency.................................................................................................................. 5-86
OAM ......................................................................................................................................... 5-91
Synchronization ............................................................................................................................. 5-95
Synchronization Overview...................................................................................................... 5-95
PTP 820G Synchronization Solution ...................................................................................... 5-98
Available Synchronization Interfaces .................................................................................... 5-98
Configuring Native Sync Distribution .................................................................................... 5-99
Native Sync Distribution Mode ............................................................................................ 5-100
SyncE PRC Pipe Regenerator Mode..................................................................................... 5-104
SSM Support and Loop Prevention ..................................................................................... 5-105
TDM Services ............................................................................................................................... 5-106
Native TDM Trails.................................................................................................................. 5-107
TDM Pseudowire ................................................................................................................... 5-110
Chapter 6: PTP 820G Management ............................................................................................ 6-1
Management Overview ................................................................................................................... 6-2
Automatic Network Topology Discovery with LLDP Protocol ...................................................... 6-3
IPv6 Support ..................................................................................................................................... 6-4

phn-3968 001v000
Page ii

........................... 8-14 Frequency Bands ............................................................................................................................................................................................................................................................................................................................ 8-37 Mediation Device Losses ...................................................................................... 8-37 Mechanical Specifications ............................................................................................................................................................................................................. 8-13 Receiver Threshold (RSL) Specifications (dBm @ BER = 10-6)........... 8-30 Ethernet Specifications .. 6-10 Backup Software Version ................................................................................ 6-12 External Alarms ....................................................... 7-2 Supported TDM Pseudowire Encapsulations .............................................................................................................. 7-3 Standards Compliance ........................................................................................................................................................................................................................... and Alarms .. 8-35 Power Specifications ....................................... 6-21 Security Log ................................................... 8-36 Power Consumption Specifications ....................................................................................................................................................................................................................................................................................................................... 8-4 Transmit Power Specifications (dBm) ....... 6-18 Secure Communication Channels.... 6-11 Local Management...................................................................................................... 6-23 Chapter 7: Standards and Certifications ....................................................................Contents Management Communication Channels and Protocols ........................................................ 8-1 Radio Specifications ............................................................................................................................................................................................................................................................. 6-14 UTC Support ........................................................................................................................................................................................................................... 6-17 Defenses in Management Communication Channels ........................................................... Status...................... 8-30 Ethernet Latency Specifications ................................ 6-15 System Security Features ........................................................................................................ 8-38 phn-3968 001v000 Page iii .............................................................................................................................................. 7-1 Supported Ethernet Standards ........ 7-5 Chapter 8: Specifcations ............................................................................. 6-7 Command Line Interface (CLI)........................................................... 8-36 Physical and Electrical Specifications........................... 6-11 Alarms ....................................................... Diagnostics.............................................................. 7-4 Network Management...................................................................................................................................................... 6-5 Web-Based Element Management System (Web EMS) ....................................................... 6-10 In-Band Management .......................................................................................................................................................................................................................................... 8-2 Capacity Specifications ................................................................................. 6-17 Defenses in User and System Authentication Procedures .............................................. 8-2 General Specifications ..................... 6-12 Configurable RSL Threshold Alarms and Traps ...................................................................................... 6-16 Cambium’s Layered Security Concept .......... 6-8 Configuration Management ................ 6-12 Alarms Editing ......................................................... 6-13 NTP Support ........................................................................................................................ 8-18 Network Specifications ................................................................................................................... 8-36 Power Input Specifications .. 6-9 Software Management ............................................... 8-34 Synchronization Specifications ...................................................................................................................................................................................................................................................................................................................................... 8-37 TDM Specifications .......................................

............................. 5-9 Dual Polarization......................................................................................................................................................................................................................................................................................................................................................... 5-24 E-Line Service Type Using Point-to-Point EVC ....................................................................................................... 2-7 TDM Interface LEDs ........................................................................................................................... 5-12 Figure 20 XPIC – Impact of Misalignments and Channel Degradation ......................................................................................................................................................................................................................................................................................................................................... 5-23 MEF Ethernet Services Definition Framework................................................................................................................. 8-39 Glossary...................................................................................................................... 5-19 Figure 25 Basic Ethernet Service Model ................................................................................................................................................................. 5-22 Multipoint to Multipoint EVC ........ 5-21 Figure 26 Ethernet Virtual Connection (EVC) .................................................... 5-28 phn-3968 001v000 Page iv .................... 2-8 Radio Interface LEDs ..................................... 2-6 Figure 6 Figure 7 Figure 8 Figure 9 Management FE Interface LEDs ................................................ 5-14 Figure 22 Multi-Carrier ABC Traffic Flow...................................................... 2-3 Electrical GE Interface LEDs ............................................... 2-4 Optical GE Interface LED ................................. 5-3 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Header De-Duplication Potential Throughput Savings per Layer ........................... 5-7 Adaptive Coding and Modulation with 10 Working Points ......................................................................................................................................................................................................................................................................... 5-6 Frame Cut-Through ........................... 2-5 Management Interface Pin Connections ......................... 5-4 Propagation Delay with and without Frame Cut-Through ..... 5-22 Rooted Multipoint EVC ............................... 5-26 EVPL Application Example................................................................................................................................................. 2-14 Figure 12 Header De-Duplication ................................... 5-16 Figure 23 Direct and Reflected Signals .................................... 5-27 Figure 35 Adding a Site Using an E-Line service ........................................................................................................................................................................................................................................................... 5-12 XPIC Implementation ........................ I Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 PTP 820G Block Diagram ........... 5-28 Figure 36 Adding a Site Using an E-LAN service ................................................................................................................... 5-13 Figure 21 Path Loss on Secondary Path of 1+1 HSB Protection Link ................ 5-6 Frame Cut-Through Operation ............................................................................... 2-11 Figure 10 Sync Interface LEDs..............................................................................................Contents Environmental Specifications................................................................................................. 5-21 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Point to Point EVC .... 5-26 EPL Application Example ... 5-18 Figure 24 1+1 BBS Space Diversity Configuration – Receiving Side .................................................................................................................................. 8-39 Supported Antenna Types ......................................................................................................... 2-12 Figure 11 Unit/ACT LED ....................................................................................... 2-10 Power Interface LEDs .................. 5-27 Figure 34 E-LAN Service Type Using Multipoint-to-Multipoint EVC ........................................................................................................................................... 2-2 PTP 820G Front Panel and Interfaces .......................................................

5-40 Management Service ............................................................................................................................................ 5-80 G....................................................................... 5-46 Figure 55 Service Path Relationship on Point-to-Point Service Path.......... 5-100 phn-3968 001v000 Page v ........................................ 5-30 E-Tree Service Type Using Multiple Roots ................................................................................................................................ 5-45 SAP......................................................................................................................Contents Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 MEF Ethernet Private LAN Example ........................ 5-74 Figure 69 Detailed H-QoS Diagram ....................................................................................................................... 5-52 Grouped Interfaces as a Single Logical Interface on Ingress Side ................................................. 5-50 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Physical and Logical Interfaces ........................................................... 5-88 Load Balancing Example in G.................................................................................................................................................... 5-42 Management Service and its Service Points .............................................................................................................................................................. 5-61 Standard QoS and H-QoS Comparison ............8032 Ring in Idle (Normal) State.......................................................................................... 5-73 Figure 68 WRED Profile Curve.............................................................................................. 5-45 Pipe Service Points .................. 5-92 Ethernet Line Interface Loopback – Application Examples ...................................................................................................................................................................................................................................................... 5-39 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Multipoint Service ............................... 5-36 PTP 820G Services Core ....................................................................................................................................... 5-38 Point-to-Point Service ............................................... 5-72 Figure 67 Random Packet Loss with Increased Capacity Utilization Using WRED ............................................................................................................................................ 5-71 Figure 66 Synchronized Packet Loss .......................................................................................................................................................................................................................... 5-31 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Ethernet Virtual Private Tree Example ....................................................................................... 5-44 SAPs and SNPs ............... 5-37 PTP 820G Services Flow ................................................................................................... 5-33 Packet Service Core Building Blocks ................. 5-97 Figure 78 Synchronous Ethernet (SyncE).................................... 5-53 Relationship of Logical Interfaces to the Switching Fabric . 5-64 Figure 64 Ingress Policing Model ............................................................................................................................................................................. 5-63 Figure 63 Classification Method Priorities..................... 5-32 Mobile Backhaul Reference Model ......... 5-91 SOAM Maintenance Entities (Example) ........................................................................................................................... 5-29 MEF Ethernet Virtual Private LAN Example............................................. 5-31 MEF Ethernet Private Tree Example .... 5-89 PTP 820G End-to-End Service Management ............................................................... 5-30 E-Tree Service Type Using Rooted-Multipoint EVC ................................................................................................. 5-77 Figure 70 Figure 71 Figure 72 Figure 73 Figure 74 Figure 75 Figure 76 Scheduling Mechanism for a Single Service Bundle ...........................................................................................8032 Ring in Protecting State............ 5-56 QoS Block Diagram .............................. 5-33 PTP 820G Services Model ................................................................... 5-68 Figure 65 PTP 820G Queue Manager ...................... 5-53 Grouped Interfaces as a Single Logical Interface on Egress Side ...................................................................................................................................... 5-97 Figure 79 Synchronization Configuration..................................................................................... SNP and Pipe Service Points in a Microwave Network ......................................................8032 Ring .................. 5-62 Hierarchical Classification ... 5-93 Figure 77 Precision Timing Protocol (PTP) Synchronization ............. 5-88 G.......................

.................. 5-98 Synchronization Output Options .................................................. 4-6 Table 5 CET Node Activation Key Levels............................................................................. 5-84 Summary and Comparison of Standard QoS and H-QoS ............................................................... 4-7 Table 6 ACM Working Points (Profiles) ..................................................................................................................................... 5-82 802........................................................................ 5-108 1+1 Dual Homing TDM Path Protection – Network Topology .............................................................................................................. 5-106 Hybrid Ethernet and TDM Services Carried Over Cascading Interfaces ............................................................................ 5-41 Table 9 Service Point Types per Service Type ..................... 5-103 Native Sync Distribution Mode – Ring Scenario (Link Failure) ............................. 5-81 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 WFQ Profile Example ............................................................................................................. 5-84 802................................................................... 5-103 Native Sync Distribution Mode – Ring Scenario (Normal Operation) ........................................................................................................................... 5-49 Table 13 C-VLAN 802..... 6-2 Figure 92 Security Solution Architecture Concept ................................................. 5-46 Table 10 Service Point Types that can Co-Exist on the Same Interface ............. 5-48 Table 12 Attached Interface Type combinations SNP Pipe MNG ................ 5-25 Table 8 Ethernet Services Learning and Forwarding ........................................................................................................ 5-65 Table 15 DSCP Default Mapping to CoS and Color ...........1ad UP Marking Table (S-VLAN)......................................................................... 5-109 All-Packet Ethernet and TDM Pseudowire Services ..................... 5-85 Synchronization input Options .........Profile ID (1-9) ........................................Profile ID (1-7) ............................... 5-102 Native Sync Distribution Mode – Tree Scenario ............1q UP Marking Table (C-VLAN).................1 UP and CFI Default Mapping to CoS and Color ...................................................................... 6-7 phn-3968 001v000 Page vi .............................................................................................................................................. 5-9 Table 7 MEF-Defined Ethernet Service Types ............. 5-98 Dedicated Management Ports.............................................................................. 6-17 Tables Table 1 PTP 820G Interfaces .......................................... 2-6 Table 3 Activation Key Types ......................................................................................................................................................................................................................................................... 5-65 Table 16 MPLS EXP Default Mapping to CoS and Color .. 5-107 1:1 TDM Path Protection – Ring Topology .............. 5-64 Table 14 S-VLAN 802.....................................................................................................1 UP and DEI Default Mapping to CoS and Color ................................................................................................................. 6-6 Table 27 Web Receiving Data Ports ........................................ 4-4 Table 4 Capacity Activation Key Levels ................... 5-66 Table 17 QoS Priority Profile Example .....Contents Figure 80 Figure 81 Figure 82 Figure 83 Figure 84 Native Sync Distribution Mode ................................................................................................................................................................................. 5-106 Hybrid Ethernet and Native TDM Services ............................................................................................................................. 6-5 Table 25 NMS Server Receiving Data Ports ..................................................................... 2-3 Table 2 PTP820 Ethernet split cable for Management............. 5-104 Figure 85 Figure 86 Figure 87 Figure 88 Figure 89 Figure 90 Figure 91 Hybrid Ethernet and TDM Services ........................ 5-111 Integrated PTP 820G Management Tools ................................. 5-101 Native Sync Distribution Mode Usage Example ..................................................................................... 5-48 Table 11 Attached Interface Type combinations SAP ........................................................................................................... 6-6 Table 26 Web Sending Data Ports ....................

................... 8-15 Receiver Threshold for 30MHz Channel spacing ................................................................... 8-31 Table 59 Ethernet Latency 30 MHz Channel Bandwidth .. 8-16 Receiver Threshold for 50MHz Channel spacing ...................................................................... 8-5 Capacity 28 MHz Channel Bandwidth (no XPIC)................................ 8-32 Table 60 Ethernet Latency 40 MHz Channel Bandwidth ............................................................ 8-36 Power Consumption Specifications .................... 8-12 Table 46 Capacity 60 MHz Channel Bandwidth (no XPIC)............................................. 8-17 Table 55 Frequency Bands .......................................................................... Status and alarms ................................... 8-30 Table 58 Ethernet Latency 28 MHz Channel Bandwidth..... 8-16 Table 54 Receiver Threshold for 56 MHz Channel spacing ............................... 8-8 Capacity 40 MHz Channel Bandwidth (no XPIC)................................................................... 7-4 Network management....... 8-35 Power Input Specifications............................................................................................................................................................. 8-15 Receiver Threshold for 40 MHz Channel spacing ........... 7-3 Standards Compliancc ...............................................Contents Table 28 Table 29 Table 30 Table 31 Table 32 Additional Management Ports for PTP 820G ................................................................................................................................................. 8-8 Capacity 40 MHz Channel Bandwidth with XPIC ............................ 8-3 Capacity 7 MHz Channel Bandwidth (no XPIC) . 8-2 General Radio Specifications for ETSI ............................................ 8-4 Capacity 14 MHz Channel Bandwidth (no XPIC)........................................................................................................................................................................................................................................................................................................ Diagnostics............................................................... 8-7 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Capacity 30 MHz Channel Bandwidth with XPIC ................................................................ 8-37 Table 69 DS1 Interface Specifications .............................................................................................................................. 8-37 Table 70 E1 Interface Specifications ............ 8-18 Table 56 Ethernet Latency 7 MHz Channel Bandwidth ................................................................................................ 8-12 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Transmit Power Specifications .................................................... 8-5 Capacity 28 MHz Channel Bandwidth with XPIC ............ 7-5 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 General Radio Specifications for ANSI ............................................. 8-34 Ethernet Interface Specifications .................................................................................................................................................................................. 8-14 Receiver Threshold for 28 MHz Channel spacing ...................................................... 8-14 Receiver Threshold for 14 MHz Channel spacing .................................................................. 8-36 Table 68 RFU-C Mediation Device Losses .............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. 8-9 Capacity 50 MHz Channel Bandwidth (no XPIC).................................... 8-34 Synchronization Specifications.. 8-11 Capacity 56 MHz Channel Bandwidth with XPIC ........................................................... 8-10 Capacity 56 MHz Channel Bandwidth (no XPIC).................................................................. 8-6 Capacity 30 MHz Channel Bandwidth (no XPIC)......................... 8-38 phn-3968 001v000 Page vii ..... 8-30 Table 57 Ethernet Latency 14 MHz Channel Bandwidth ..................... 8-34 Carrier Ethernet Functionality ............................................................................................................................................ 8-33 Ethernet Latency 56 MHz Channel Bandwidth ....................................................... 8-32 Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Ethernet Latency 50 MHz Channel Bandwidth .... 6-7 Supported Ethernet Standards .............. 7-2 Supported TDM Pseudowire Encapsulations .................................................................................... 8-13 Receiver Threshold for 7 MHz Channel spacing ......

............................................................................................ 8-38 Table 72 RFU-C Mechanical Specifications .....................Contents Table 71 IDU Mechanical Specifications ................. 8-38 phn-3968 001v000 Page viii .................................................

com Sales enquiries: solutions@cambiumnetworks. Eastern Road. Linhay Business Park.cambiumnetworks.com Telephone number list: http://www.Activation Keys  Chapter 5: Feature Description  Chapter 6: PTP 820G Management  Chapter 7: Standards and Certifications  Chapter 8: Specifcations Contacting Cambium Networks Support website: http://www. Ashburton.cambiumnetworks.cambiumnetworks.About This User Guide This guide contains the following chapters:  Chapter 1: Product description  Chapter 2: Hardware Description  Chapter 3: RFU Overview  Error! Reference source not found. TQ13 7UP phn-3968 001v000 Page 1 . UK.com/support Main website: http://www. Devon.com/support/contact-support Address: Cambium Networks Limited.com Support enquiries: support@cambiumnetworks.

or recommendations made in this document. for any risk of damage. Cambium disclaims all liability whatsoever. This document is divided into numbered chapters that are divided into sections. installation and maintenance of the Cambium PTP equipment and ancillary devices. to abide by the instructions. This includes feedback on the structure. Feedback We appreciate feedback from the users of our documents. accuracy. It is recommended that all personnel engaged in such activities be properly trained. content. emphasized in blue text in electronic versions. loss or reduction in system performance arising directly or indirectly out of the failure of the customer. phn-3968 001v000 Page 2 . or anyone acting on the customer's behalf.com. Sections are not numbered. Cross references References to external publications are shown in italics. or completeness of our documents. but are individually named at the top of each page. are active links to the references. Other cross references. and are listed in the table of contents. implied or express.About This User Guide Problems and warranty Purpose Cambium Networks Point-To-Point (PTP) documents are intended to instruct and assist personnel in the operation. system parameters. Send feedback to support@cambiumnetworks.

2 Visit the support website.About This User Guide Problems and warranty Problems and warranty Reporting problems If any problems are encountered when installing or operating this equipment. obtain details of the Return Material Authorization (RMA) process from the support website. Cambium shall within this time. either repair or replace the defective product within thirty (30) days of receipt of the defective product. at its own option. visit the support website. contact the reseller or distributor. Use precautions to prevent damage. Hardware warranty Cambium’s standard hardware warranty is for one (1) year from date of shipment from Cambium Networks or a Cambium distributor. 4 Gather information from affected units. Caution Using non-Cambium parts for repair could damage the equipment or void warranty. To register PTP products or activate warranties. Cambium Networks warrants that hardware will conform to the relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. 3 Ask for assistance from the Cambium product supplier. Repair and service If unit failure is suspected. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. such as any available diagnostic downloads. follow this procedure to investigate and report: 1 Search this document and the software release notes of supported releases. Contact Cambium for service and repair instructions. phn-3968 001v000 Page 3 . 5 Escalate the problem by emailing or telephoning support. For warranty assistance.

Assets include the ability to communicate. phn-3968 001v000 Page 4 . and information about the parties involved. Cambium recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality. In certain instances Cambium makes specific recommendations regarding security practices. however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. and availability of information and assets. information about the nature of the communications. integrity.About This User Guide Security advice Security advice Cambium Networks systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment.

and notes Warnings. or individual items of equipment within a system. cautions. software. A note has the following format: Note Note text. Warnings Warnings precede instructions that contain potentially hazardous situations. A caution has the following format: Caution Caution text and consequence for not following the instructions in the caution. phn-3968 001v000 Page 5 .About This User Guide Warnings. However. Cautions Cautions precede instructions and are used when there is a possibility of damage to systems. this damage presents no danger to personnel. and notes The following describes how warnings and cautions are used in this document and in all documents of the Cambium Networks document set. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A warning has the following format: Warning Warning text and consequence for not following the instructions in the warning. cautions.

com/support Disposal of surplus packaging Do not dispose of surplus packaging in landfill sites. Disposal of Cambium equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Cambium equipment in landfill sites. In the EU. In EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives identified and any amendments made to these directives when using Cambium equipment in EU countries.About This User Guide Caring for the environment Caring for the environment The following information describes national or regional requirements for the disposal of Cambium Networks supplied equipment and for the approved disposal of surplus packaging. For disposal instructions. it is the individual recipient’s responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law. In non-EU countries In non-EU countries. refer to http://www.cambiumnetworks. phn-3968 001v000 Page 6 . dispose of Cambium equipment and all surplus packaging in accordance with national and regional regulations.

Chapter 1: Product description This chapter provides an overview of the PTP 820G. This enables operators to utilize a combination of PTP IDUs and radio units (RFUs) to build networks in which the most appropriate PTP product can be utilized for each node in the network to provide the feature support. and features a small footprint. and footprint that is optimized to meet the needs of that particular node. capacity support. The PTP series “pay-as-you-go” activation key models further enable operators to build for the future by adding capacity and functionality over time to meet the needs of network growth without the need to add additional hardware This chapter consists of the following sections:  Product Overview phn-3968 001v000 Page 1-1 . high density. frequency range. high-performance edge node product. density. and a high degree of availability. the PTP family of products provides a wide variety of backhaul solutions that can be used separately or combined to form integrated backhaul networks or network segments. PTP 820G is an integral part of the PTP family of high-capacity wireless backhaul products. PTP 820G is specially designed for edge/tail sites. Together.

The system provides support for emerging services. IP820G can also include the following optional features:  Multi-carrier package including two radio channels and radio interfaces. with a small footprint. frame cutthrough. and networking protocols (future proof). cutting-edge header de-duplication techniques. PTP 820G includes an advanced feature set for Carrier Ethernet Transport. simplified management for reduced OPEX. high density. It also enables operators to reduce TCO by supporting rich. with advanced support for TDM services. PTP 820G is built specifically for tail/edge sites deployments.Chapter 1: Product description Product Overview Product Overview PTP 820G is a compact wireless backhaul node that is optimized for tail and edge/chain nodal deployment. The following interfaces are supported:  6 x 1 GE interfaces total o 2 x dual mode GE electrical or cascading interfaces (RJ-45) o 2 x GE electrical interfaces (RJ-45) o 2x GE optical interfaces (SFP)  Optional: 16 x DS1 or 16 x E1 interfaces  Single or dual radio interfaces (TNC)  Single or dual power-feeds (-48v)  Sync in/out interface  Management interfaces  o Terminal – RS232 (RJ-45) o 2x FE electrical interfaces (RJ-45) External alarms interface PTP 820G is based on a passive cooling design that does not require fans. standards.  Dual-feed power option for power redundancy. and more. including a sophisticated Ethernet services engine. and supports essentially the same feature set but in a fixed form-factor and on a scale that is optimized for tail/edge sites. It is based on the same architecture and technology as PTP 820. PTP 820G enables operators to maximize QoE with an improved customer experience by providing TCP-friendly backhaul. revenue-generating services.  16 x DS1 or 16 x E1 interfaces. phn-3968 001v000 Page 1-2 . and a high degree of availability. for improved operational efficiency. and improved service availability and time-to-revenue.

using vertical and horizontal polarization. service activation). MSTP).Chapter 1: Product description Product Overview PTP 820G provides an innovative packet backhaul services aggregation solution that is designed to meet the challenges faced by operators building next-generation wireless backhaul networks for delivery of packet-based services. The RFU-C is designed for a broad range of interfaces. and carrier-grade service resiliency (G. RFU-Ce provides a range of modulations from QPSK to 1024 QAM.8032. scaling to GE capacity  Future-proof with maximal investment protection  Supports RFU-Ce for modulations up to 1024QAM.  Optimized tail/edge solution supporting seamless integration of radio (L1) and end-to-end Carrier Ethernet transport/services (L2) functionality  Rich packet processing feature set for support of engineered end-to-end Carrier Ethernet services with strict SLA  Integrated support for multi-operator and converged backhaul business models. as well as PDH/SDH or hybrid Ethernet and TDM interfaces. from 6 to 38 GHz. The PTP 820G aggregation solution is based upon rich backhaul services and simplified management that are supported using personalized QoS (H-QoS). and supports capacities from 10 Mbps to 500 Mbps. For maximum user choice flexibility. Meeting these challenges requires the ability to maintain services with strict SLA by enforcing a services policy that guarantees and monitors service performance. RFU-C supports low to high capacities for traditional voice and Ethernet services. PTP 820G Highlights The following are some of the highlights of PTP 820G. PTP 820G maintains high capacity at the aggregation network. two carrier signals can be transmitted over a single channel. with modulation of up to 1024 QAM. phn-3968 001v000 Page 1-3 . such as wholesale services and RAN-sharing  Highest capacity. PTP 820G Radio Options A PTP 820G system consists of a PTP 820G indoor unit (IDU) and either one or two state-of-the-art RFU-C radio frequency units (RFUs). RFU-C operates in a wide range of spectrum bands. flexible packet synchronization solution combining SyncE and 1588v2  Best-in-class integrated TDM migration solution  Specifically built to support resilient and adaptive multi-carrier radio links. Traffic capacity throughput and spectral efficiency are optimized with the desired channel bandwidth. scalability and spectral efficiency  High precision. superb service OAM (CFM. PMs. channel bandwidths can be selected. When RFU-C operates in co-channel dual polarization (CCDP) mode using XPIC. It also requires the ability to manage the explosion of data by ensuring capacity allocation and traffic management under wireless link congestion scenarios. This enables double capacity in the same spectrum bandwidth.

In dual-carrier systems. the user can configure the two radio interfaces as a protection group. The CPU monitors the radio interfaces and initiates switchover upon indication of a hardware or signal failure.Chapter 1: Product description Product Overview PTP 820G Protection Options PTP 820G provides 1+1 HSB radio protection. phn-3968 001v000 Page 1-4 . A power redundancy option is also offered by means of a dual-feed power input hardware assembly option. which protects against hardware failure in the RFU.

including a description of the available hardware assembly options This chapter consists of the following sections:  Hardware Architecture  Front Panel Description  Ethernet Traffic Interfaces  Ethernet Management Interfaces  DS1/E1 Interface (Optional)  Radio Interfaces  Power Interfaces  Synchronization Interface  Terminal Interface  Unit/ACT LED  External Alarms phn-3968 001v000 Page 2-1 .Chapter 2: Hardware Description This chapter describes the PTP 820G indoor unit and its interfaces.

Chapter 2: Hardware Description Hardware Architecture Hardware Architecture PTP 820G is a compact unit that fits in a single rack unit. PTP 820G receives an external supply of -48V. A PTP 820G system consists of a PTP 820G indoor unit (IDU) and one or two radio frequency units (RFUs). an RJ-45 synchronization interface. and optionally a 16 x DS1 or E1 interface. transmits traffic and management data between the IDU and the RFU. Figure 1 PTP 820G Block Diagram Sync 48V 48V Radio Interface 1 Power Supply Framer Modem ABC/BBS XPIC Framer Modem IF RFU Interface RFU IF RFU Interface RFU (Optional Second Interface) PPS ToO 1588 OC/BC (Optional) Sync Sync In/Out FE Management Interfaces Radio Interface 2 (Optional) Sync Unit CPU Terminal Ethernet GE Traffic Interfaces GE/Cascading Interfaces Ethernet Services Network Processor TDM Interfaces (Optional) TDM Pseudowire Services Services Engine TDM Cross Connect o Native TDM Services phn-3968 001v000 Page 2-2 TDM Services Processor Framer LIU 16 x DS1 Interface . one or two radio interfaces depending on the hardware configuration. A PTP 820G IDU contains six Ethernet interfaces. a DB9 dry contact external alarms interface. and provides DC -48V power to the RFU. with a dual-feed option for power redundancy. The IDU also includes two FE management interfaces. with a passive cooling system that eliminates the need for fans. A coaxial cable connects the IDU to each RFU. The following hardware assembly options are available for the PTP 820G IDU:  One or two radio interfaces  One or two power interfaces  With or without 16 x DS1 or E1 interfaces The following figure provides a block diagram of the PTP 820G. and an RJ-45 terminal console interface for connection to a local craft terminal.

The following sections provide detailed descriptions of the PTP 820G interfaces and LEDs.Chapter 2: Hardware Description Front Panel Description Front Panel Description This section describes the PTP 820G’s front panel. Figure 2 PTP 820G Front Panel and Interfaces Table 1 PTP 820G Interfaces Interface For Further Information 16 x DS1s or E1 (optional) DS1/E1 Interface (Optional) External Alarms (DB9) External Alarms Sync Interface In/Out (RJ-45) Synchronization Interface 2 x FE Management Interfaces (RJ-45) Ethernet Management Interfaces Terminal Interface (RJ-45) Terminal Interface 2 x GE Dual Mode GE Electrical or Cascading Interfaces (RJ-45) Ethernet Traffic Interfaces 2 x GE Electrical Interfaces (RJ-45) Ethernet Traffic Interfaces 2 x GE Optical Interfaces (SFP) Ethernet Traffic Interfaces Radio Interfaces (TNC) Radio Interfaces Power Interfaces -48V Power Interfaces phn-3968 001v000 Page 2-3 .

as follows: o Off – The interface is shut down or the signal is lost. o Blinking Green – The interface is transmitting and/or receiving traffic. Indicates the speed of the interface. Each electrical interface has the following LEDs:   Port Status LED – Located on the upper left of each interface. o Green – The interface is enabled and the link is operational. as follows: o Off – 100Base-TX o Green – 1000Base-T o Blinking Green – 10Base-T Figure 3 Electrical GE Interface LEDs phn-3968 001v000 Page 2-4 . Indicates the link status of the interface. Port Rate LED – Located on the upper right of each interface. enabling operators to create links among multiple PTP 820G units in a node for multi-carrier and multi-directional applications based on hybrid Ethernet and Native TDM services. When operating in cascading mode. these interfaces can handle hybrid Ethernet and Native TDM traffic. SFP6 GbE1 and GbE2 can be configured as normal GE traffic interfaces or as cascading interfaces. GbE4  2 x GE optical interfaces (SFP) – SFP5.Chapter 2: Hardware Description Ethernet Traffic Interfaces Ethernet Traffic Interfaces Related Topics:  Physical Interfaces  Ethernet Interface Specifications The front panel of the PTP 820G contains four electrical and two optical GE Ethernet traffic interfaces:  2 x GE dual mode electrical or cascading interfaces (RJ-45) – GbE1/CS1. GbE2/CS2  2 x GE electrical interfaces (RJ-45) –GbE3.

as follows: o Off – The interface is shut down or the signal is lost. Each LED indicates the link status of the interface. o Green – The interface is enabled and the link is operational. o Blinking Green – The interface is transmitting and/or receiving traffic. Figure 4 Optical GE Interface LED phn-3968 001v000 Page 2-5 .Chapter 2: Hardware Description Ethernet Traffic Interfaces Each optical interface has the following LED:  Port Status LED – A Port Status LED is located on the lower left of SFP5 and the lower right of SFP6.

Table 2 PTP820 Ethernet split cable for Management Cambium Part No.Chapter 2: Hardware Description Ethernet Management Interfaces Ethernet Management Interfaces Related Topics:  Physical Interfaces  Ethernet Interface Specifications PTP 820G contains two FE management interfaces. Note The management interfaces cannot be shut down. o Blinking Green – The interface is transmitting and/or receiving management traffic. Each LED indicates the link status of the interface. Figure 5 Management Interface Pin Connections RJ-45 Connector (female) Management Switch Port 1 Port 2 TX+ 1 TX- 2 RX+ 3 RX- 4 TX+ 5 TX- 6 RX+ 7 RX- 8 If the user only needs to use a single management interface. a special Ethernet split cable for Management can be ordered from Cambium Networks. as follows: o Off – The cable is not connected or the signal is lost. construct a 2 x FE splitter cable according to Figure 5 The MGMT interface has the following LEDs:  Port Status LED – The LED for management interface 1 is located on the upper left of the MGMT interface. which connect to a single RJ-45 physical connector on the front panel (MGMT). The LED for management interface 2 is located on the upper right of the MGMT interface. phn-3968 001v000 Page 2-6 . To access both management interfaces. a standard Cat5 RJ-45 cable (straight or cross) can be connected to the MGMT interface. o Green – The interface is enabled and the link is operational. Marketing Description N000082L122A PTP820 Ethernet split cable for Management To access both management interfaces.

Chapter 2: Hardware Description Ethernet Management Interfaces Figure 6 Management FE Interface LEDs phn-3968 001v000 Page 2-7 .

 E1/DS1 LED – Indicates whether the interfaces are enabled with no alarms (Green). Figure 7 TDM Interface LEDs phn-3968 001v000 Page 2-8 . with alarms (Red).Chapter 2: Hardware Description DS1/E1 Interface (Optional) DS1/E1 Interface (Optional) Related Topics:  TDM Services  DS1/E1 Interface Specifications Optionally. The DS1/E1 interface has the following LEDs  ACT LED – Indicates whether the TDM card is working properly (Green) or if there is an error or a problem with the card’s functionality (Red). PTP 820G can be ordered with an MDR69 connector in which 16 DS1 / E1 interfaces are available (ports 1 through 16). or no interfaces enabled (Off).

or. RFU – Indicates the status of the RFU. o Yellow – A minor RFU alarm or a warning is present. Each radio interface has the following set of LEDs. in a protected configuration. LINK – Indicates the status of the radio link. if there is a second radio interface. The radio interfaces are labeled Radio 1 and. o Blinking Red – An RF loopback has been activated. Each radio interface is connected to an RFU via coaxial cable. o Blinking Red – Troubleshooting mode. o Blinking Green – An IF loopback is activated. o Blinking Red – An IF loopback is activated. The LEDs indicate the following:    ACT – Indicates whether the interface is working properly (Green) or if there is an error or a problem with the interface’s functionality (Red). o Green – The radio is active and operating normally. The LEDs for Radio 1 are located to the right of the interface. Each radio interface uses a TNC connector type. The LEDs for Radio 2 are located to the left of the interface. It is also used to provide -48V DC power from the IDU to the RFU. o Red – There is an LOF or Excessive BER alarm on the radio. phn-3968 001v000 Page 2-9 . and the result is Failed. Radio 2. or the RFU is in TX mute mode. as well as for management and configuration of the RFU. o Red – There is a hardware failure. as follows: o Green – The radio link is operational. o Blinking Green – An RF loopback has been activated. o Blinking Green – The radio is operating normally and is in standby mode. the RFU is in standby mode. and the result is OK. as follows: o Off – The radio is disabled. depending on the hardware assembly option that was selected. o Red – A cable is disconnected. as follows: o Green – The RFU is functioning normally. This connection is used for traffic between the RFU and the IDU. and the result is OK. or a major or critical RFU alarm is present.Chapter 2: Hardware Description Radio Interfaces Radio Interfaces PTP 820G includes one or two radio interfaces. and the result is Failed.

Chapter 2: Hardware Description Radio Interfaces Figure 8 Radio Interface LEDs phn-3968 001v000 Page 2-10 .

the system remains shut down. The PTP 820G monitors the power supply for under-voltage and includes reverse polarity protection. The allowed power input range for the PTP 820G is -40V to -60V. and an over voltage alarm is triggered if the power goes above the allowed range. and Red if the voltage is not within range or if a power cable is not connected. An under voltage alarm is triggered if the power goes below the allowed range. so that if the positive (+) and negative (-) inputs are mixed up.Chapter 2: Hardware Description Power Interfaces Power Interfaces PTP 820G receives an external supply of -48V current via one or two power interfaces (the second power interface is optional for power redundancy). The LED is Green when the voltage being fed to the power interface is within range. Figure 9 Power Interface LEDs phn-3968 001v000 Page 2-11 . There is an ACT LED for each power interface.

Indicates the status of T3 input clock. o Blinking Green – The clock unit is in a holdover state. o Green – There is legal T3 input clock. as follows:   T3 Status LED – Located on the upper left of the interface. as follows: o Off – There is no T3 input clock. as follows: o Off – T4 output clock is not available. Figure 10 Sync Interface LEDs phn-3968 001v000 Page 2-12 . or the input is illegal. one on the upper left of the interface and one on the upper right of the interface.Chapter 2: Hardware Description Synchronization Interface Synchronization Interface PTP 820G includes an RJ-45 synchronization interface for T3 clock input and T4 clock output. o Green – T4 output clock is available. The interface is labeled SYNC. The synchronization interface contains two LEDs. T4 Status LED – Located on the upper right of the interface. Indicates the status of T4 output clock.

phn-3968 001v000 Page 2-13 .Chapter 2: Hardware Description Terminal Interface Terminal Interface PTP 820G includes an RJ-45 terminal interface (RS-232). A local craft terminal can be connected to the terminal interface for local CLI management of the unit.

and no alarms are present on the unit. as follows:  Off – Power is off.  Green – Power is on. and there are minor alarms or warnings on the unit.  Yellow – Power is on. Figure 11 Unit/ACT LED phn-3968 001v000 Page 2-14 .Chapter 2: Hardware Description Unit/ACT LED Unit/ACT LED A general ACT LED for the unit is located on the lower left of the PTP 820G front panel.  Red – Power is on. This LED is labeled UNIT/ACT. and indicates the general status of the unit. and there are major or critical alarms on the unit.

Chapter 2: Hardware Description External Alarms External Alarms PTP 820G includes a DB9 dry contact external alarms interface. The input alarms are configurable according to: 1 Intermediate 2 Critical 3 Major 4 Minor 5 Warning The output alarm is configured according to predefined categories. The external alarms interface supports five input alarms and a single output alarm. phn-3968 001v000 Page 2-15 .

with vertical and horizontal polarizations. or hybrid Ethernet and TDM interfaces. High spectral efficiency can be ensured with XPIC. using the same bandwidth for double the capacity.5-56 MHz channels with configurable modulation schemes. via a single carrier. with an N-type connector (male) on the RFU and a TNC connector on the IDU. PTP RFUs deliver high capacity over 3. and compatibility in mind. power. phn-3968 001v000 Page 3-1 . The IDU and RFU are connected by a coaxial cable RG-223 (100 m/300 ft). These advanced systems provide high-power transmission for short and long distances and can be assembled and installed quickly and easily. mission critical. with any mix of interfaces.Chapter 3: RFU Overview PTP Radio Frequency Units (RFUs) were designed with sturdiness. simplicity. RFU-Cs provides a range of modulations from QPSK to 1024 QAM. The RFUs support low to high capacities for traditional voice. pure TDM. The antenna connection can be:  Direct mount using the same antenna type. and emerging Ethernet services. pure Ethernet. Belden 9914/RG-8 (300 m/1000 ft) or equivalent.

contact your Cambium Networks representative. state-of-the-art RFU that supports a broad range of interfaces and capacities from 100 Mbps up to 650 Mbps.Up to 26 dBm for extended distance. RFU-C operates in the frequency range of 6-38 GHz. two carrier signals can be transmitted over a single channel.Chapter 3: RFU Overview RFU-C RFU-C PTP RFU-C is a fully software configurable.Reduces installation and warehousing costs  Supported configurations: o  1+0 – direct mount Efficient and easy installation . Main Features of RFU-C  Frequency range – Operates in the frequency range 6-38 GHz  More power in a smaller package .1 When RFU-C operates in co-channel dual polarization (CCDP) mode using XPIC. lightweight form factor . enhanced availability. This enables double capacity in the same spectrum bandwidth. 1 phn-3968 001v000 Page 3-2 . RFU-C supports low to high capacities for traditional voice and Ethernet services. using vertical and horizontal polarization. channel bandwidths from 3.Direct mount installation with different antenna types For additional information:  Specifcations For details about supported modulation capabilities beyond 256 QAM using a standard RFU-C. With RFU-C.5 MHz – 56 MHz  Compact. use of smaller antennas  Configurable Channel Bandwidth – 3. For maximum user choice flexibility. RFU-Ce provides a range of modulations from QPSK to 1024 QAM. as well as PDH/SDH/SONET or hybrid Ethernet and TDM interfaces. traffic capacity throughput and spectral efficiency are optimized with the desired channel bandwidth.5-56 MHz can be selected together with a range of modulations.

Activation keys are divided into two categories:  Per Carrier – The activation key is per carrier.  Per Device – The activation key is per device. This chapter includes:  Working with Activation Keys  Demo Mode License  Activation Key-Enabled Features phn-3968 001v000 Page 4-1 . A 1+1 HSB configuration requires the same set of per-carrier activation key for both the active and the protected carriers. Each unit contains a single activation key. PTP 820G offers a pay as-you-grow concept in which future capacity growth and additional functionality can be enabled with activation keys.Chapter 4: Activation Keys This chapter describes PTP 820G’s activation key model. regardless of the number of carriers supported by the device.

Chapter 4: Activation Keys

Working with Activation Keys

Working with Activation Keys
Cambium Networks provides a System for managing activation keys. This system enables
authorized users to generate activation keys, which are generated per IDU serial number.
In order to upgrade an activation key, the activation-key must be entered into the PTP 820G. The
system checks and implements the new activation key, enabling access to new capacities and/or
features.
In the event that the activation-key-enabled capacity and feature set is exceeded an Activation Key
Violation alarm occurs. After a 48-hour grace period, all other alarms are hidden until the capacity
and features in use are brought within the activation key’s capacity and feature set.

phn-3968 001v000
Page 4-2

Chapter 4: Activation Keys

Demo Mode License

Demo Mode License
The system can be used in demo mode, which enables all features for 60 days. Demo mdoe
expires 60 days from the time it was activated, and the most recent valid activation key cipher goes
into effect. The 60-day period is only counted when the system is powered up. Ten days before the
demo mode expires, an alarm is raised indicating to the user that demo license is about to expire.

phn-3968 001v000
Page 4-3

Chapter 4: Activation Keys

Activation Key-Enabled Features

Activation Key-Enabled Features
As your network expands and additional functionality is desired, activation keys can be purchased
for the features described in the following table.
Table 3 Activation Key Types
Cambium Part
Number

Type (Per
Carrier/Per
Device)

Description

For Addition
Information

Refer to
Capacity
Activation Key
Levels on page
4-6

Per Carrier

Enables you to increase your system’s radio
capacity in gradual steps by upgrading your
capacity activation key level. Without a
capacity activation key, each carrier has a
capacity of 10 Mbps. Activation-Key-Enabled
capacity is available from 50 Mbps to 500
Mbps. Each RMC can be activation-keyenabled for a different capacity.

Capacity
Summary

ACM

Per Carrier

Enables the use of Adaptive Coding and
Modulation (ACM) scripts.

Adaptive
Coding
Modulation
(ACM)

Multi-carrier
ABC

Per Carrier

Enables Multi-Carrier ABC

Multi-Carrier
ABC

Header DeDuplication

Per Carrier

Enables the use of Header De-Duplication,
which can be configured to operate at L2
through L4.

Header DeDuplication

XPIC

Per Carrier

Enables the use of Cross Polarization Interface
Canceller (XPIC). Each carrier in the XPIC pair
must be licensed.

Cross
Polarization
Interference
Canceller (XPIC)

GE Port
Enabling

Per Device

Enables the use of an Ethernet traffic port in
GE mode (10/100/1000baseT or 1000baseX). A
license is required for each Ethernet traffic
port that is used on the device. License can be
installed multiple times with dynamic
allocation inside the unit to enable multiple
GE ports.

Ethernet Traffic
Interfaces

Note: All Ethernet traffic ports are enabled in
FE mode (10/100baseT) by default with
requiring any license.

phn-3968 001v000
Page 4-4

Chapter 4: Activation Keys

Activation Key-Enabled Features

Cambium Part
Number

Type (Per
Carrier/Per
Device)

Description

For Addition
Information

Refer to CET
Node Activation
Key Levels on
page 4-7

Per Device

Enables Carrier Ethernet Transport (CET) and
a number of Ethernet services (EVCs),
depending on the type of CET Node license:

Ethernet
Service Model

Edge CET Node – Up to 8 EVCs.
Aggregation Level 1 CET Node – Up to 64
EVCs.
A CET Node license also enables the
following:

Quality of
Service (QoS)
Link
Aggregation
Groups (LAG)

Network resiliency (MSTP/RSTP) for all
services.
Full QoS for all services including basic queue
buffer management (fixed queues buffer size
limit, tail-drop only) and eight queues per
port, no H-QoS.
LAG Support
N000082L050A

Per Device

Enables the following protocols for improving
network resiliency:

Network
Resiliency

G.8032
Native TDM services 1:1 path protection

2

N000082L044A

Per Device

Enables H-QoS.2 This license is required to
add service-bundles with dedicated queues to
interfaces. Without this license, only the
default eight queues per port are supported.

Quality of
Service (QoS)

N000082L038A

Per Device

Enables configurable (non-default) queue
buffer size limit for Green and Yellow frames.
Also enables WRED. The default queue buffer
size limit is 1 Mbits for Green frames and 0.5
Mbits for Yellow frames.

Quality of
Service (QoS)

N000082L052A

Per Device

Enables the G.8262 synchronization unit. This
license is required in order to provide end-toend synchronization distribution on the
physical layer. This license is also required to
use Synchronous Ethernet (SyncE).

Synchronization

N000082L041A

Per Device

Enables Frame Cut-Through.

Frame CutThrough

H-QoS support is planned for future release.

phn-3968 001v000
Page 4-5

Key . and RADIUS is planned for future release.Key . SNMPv3. 5 PM support is planned for future release.4 Connectivity Fault Management (FM) N000082L040A Per Device Enables performance monitoring pursuant to Y. 4 FM support is planned for future release. SFTP.1731 (CET mode only).Key . phn-3968 001v000 Page 4-6 .Capacity 100M with ACM Enabled N000082L83A PTP 820G Act.Capacity upgrade from 100 to 650M.Key . and RADIUS). HTTPS.Capacity upgrade from 100 to 500M.3ah (CET mode only).5 Table 4 Capacity Activation Key Levels Cambium Part Number Description N000082L82A PTP 820G Act.Capacity 650M with ACM Enabled N000082L85A PTP 820G Act. per carrier N000082L86A PTP 820G Act.Chapter 4: Activation Keys Activation Key-Enabled Features Cambium Part Number Type (Per Carrier/Per Device) Description For Addition Information N000082L053A Per Device Enables TDM pseudowire services on units with TDM interfaces. TDM Pseudowire N000082L051A Per Device Enables secure management protocols (SSH.Key . SFTP.3 Secure Communication Channels N000082L039A Per Device Enables Connectivity Fault Management (CFM) per 802. HTTPS. per carrier 3 Support for SSH.Capacity 500M with ACM Enabled N000082L84A PTP 820G Act. SNMPv3.1ag and 802. Without this activation key. only native TDM services are supported.

N000082L031A Enables CET with up to 1024 services/EVCs. N000082L054A Upgrades from "Edge-CET-Node" to "Agg-Lvl-2-CET-Node". N000082L030A Enables CET with up to 64 services/EVCs. phn-3968 001v000 Page 4-7 . N000082L055A Upgrades from "Edge-CET-Node" to "Agg-Lvl-1-CET-Node".Chapter 4: Activation Keys Activation Key-Enabled Features Table 5 CET Node Activation Key Levels Cambium Part Number Description N000082L037A Enables CET with up to 8 services/EVCs.

This chapter includes:  Innovative Techniques to Boost Capacity and Reduce Latency  Radio Features Ethernet FeaturesATPC enables the transmitter to operate at less than maximum power for most of the time. thus allowing new radio links to be easily coordinated in frequency congested areas.Chapter 5: Feature Description This chapter describes the main PTP 820G features. transmit power is increased as needed until the maximum is reached. thereby reducing overall system cost. phn-3968 001v000 Page 5-1 . The feature descriptions are divided into the categories listed below. When fading conditions occur. The ATPC mechanism has several potential advantages. including less transmitter power consumption and longer amplifier component life. ATPC is frequently used as a means to mitigate frequency interference issues with the environment.

Both the Ethernet link and the TDM links will be available over radios with individual variable capacity. The result is 100% utilization of radio resources in which traffic load is balanced based on instantaneous radio capacity per carrier. Note Multi-Carrier ABC support is planned for future release. In such conditions. Figure 22 Multi-Carrier ABC Traffic Flow Eth Carrier 1 Carrier 1 Carrier 2 Carrier 2 Traffic Combiner Traffic Splitter Carrier 3 Carrier 3 Carrier 4 Carrier 4 phn-3968 001v000 Page 5-2 Eth . the TDM links can be preserved by a sophisticated prioritizing scheme configured by the user. The following diagram illustrates the Multi-Carrier ABC traffic flow. and handled by a prioritizing scheme. Load balancing is performed without regard to the number of MAC addresses or the number of traffic flows. increasing capacity over a given bandwidth and maximizing spectrum utilization. In Multi-Carrier ABC mode. Multi-Carrier Adaptive Bandwidth Control (Multi-Carrier ABC) is an innovative technology that creates logical bundles of multiple radio links optimized for wireless backhaul applications. traffic is divided among the carriers optimally at the radio frame level without requiring Ethernet link aggregation (LAG). During fading events which cause ACM modulation changes. each carrier fluctuates independently with hitless switchovers between modulations. MultiCarrier ABC enables separate radio carriers to be combined into a virtual transport pipe for a high capacity Ethernet link and individual TDM links.Chapter 5: Feature Description Activation Key-Enabled Features Multi-Carrier ABC This feature requires:  PTP 820G hardware assembly with two radio interfaces.

Adding or removing a channel is hitless. which means that all channels must wait for the slowest arriving block.. Alignment does not add any delay to the slowest carrier. When an ACM profile change takes place on a specific carrier. not all data is lost. the number of data bytes inside a block. The system determines which radio carriers contribute to the aggregated link. Multi-Carrier ABC provides the maximum available aggregated capacity. so as not to disturb the aggregated data flow. The block size. Other criteria. Graceful Degradation of Service Multi-Carrier ABC provides for protection and graceful degradation of service in the event of failure of an RFU or the slave carrier. the latency variation for the aggregated data stream is determined by the latency variation of one radio channel. can also be used. Multi-Carrier ABC responds by changing the block size of that channel. the data path remains error free. since each radio script has a unique delay distribution. independently for each radio carrier. When all channels run the same radio script.e. PTP 820G supports the following configurations:  2+0 ABC  1+1 BBS Space Diversity Multi-Carrier ABC Operation Multi-Carrier ABC divides each radio carrier into blocks of data. The latency of the aggregated data flow is determined by the slowest arriving carrier. is configured based on the capacity of the carrier’s ACM profile. Even when one or more carriers are operating at limited capacity or are totally down. such as ACM profile and latency. i. all blocks are aligned. When all channels are up and running. This latency variation is slightly more complicated to predict if the various radio carriers run different radio scripts. Multi-Carrier ABC and ACM Multi-Carrier ABC automatically adapts to capacity changes that result from changes in the current ACM profile. On the receiving side of the link. Multi-Carrier ABC can tolerate a large difference in the degree of delay between the slowest and the fastest arriving carriers. The block size may vary from one block to the other. phn-3968 001v000 Page 5-3 . In the event of degradation in a particular carrier. the carrier is removed from the aggregated link before bit errors arise. based on the received channel qualities. Instead. This ensures that if one link is lost. A low ACM profile means more latency compared to a higher ACM profile.Chapter 5: Feature Description Activation Key-Enabled Features Multi-Carrier Configurations In ABC Multi-Carrier mode. bandwidth is simply reduced until the link returns to service.

The antennas must be separated by approximately 15 to 20 meters. Figure 23 Direct and Reflected Signals Space Diversity is a common way to negate the effects of fading caused by multipath phenomena. multipath phenomena are common. and selects the signal with the best quality. Note 2048 QAM support is planned for future release. Space Diversity is implemented by placing two separate antennas at a distance from one another that makes it statistically likely that if one antenna suffers from fading caused by signal reflection. In long distance wireless links with relatively low frequency. the other antenna will continue to receive a viable signal. Fading can be flat or dispersive. all frequency components of the signal experience the same magnitude of fading. BBS Space Diversity requires two antennas and RFUs. The Multi-Carrier ABC mechanism constantly monitors the signal quality of the main and diversity carrier. This fading phenomenon depends mainly on the link geometry and is more severe at long distance links and over flat surfaces or water. The impact of this distortion can vary over time.Chapter 5: Feature Description Activation Key-Enabled Features BBS Space Diversity This feature requires:  PTP 82G hardware assembly with two radio interfaces. and frequency. and can vary quickly during temperature changes due to rapid changes in the reflections phase. Switching between the main and diversity carriers is hitless. and modems at the receiving end of the link. It is also affected by air turbulence and water vapor. which can cause distortion of the signal resulting in signal fade. In flat fading. In dispersive. space. phn-3968 001v000 Page 5-4 . Both direct and reflected signals are received. The same data stream is received by both antennas. radios. different frequency components of the signal experience decorrelated fading. or frequency selective fading.

 Ethernet Features  Synchronization  TDM Services phn-3968 001v000 Page 5-5 . Radio Traffic Capacity – Measures the total L1 bandwidth (payload plus overheads) sent through the radio (Mbps). and used to generate Frame Error Rate PMs for every 15-minute interval. The threshold is defined as 0. as well as additional PMs based on these counters:    Radio Traffic Utilization – Measures the percentage of radio capacity utilization. The utilization threshold can be defined by the user (0-100%).Chapter 5: Feature Description Activation Key-Enabled Features Figure 24 1+1 BBS Space Diversity Configuration – Receiving Side Radio & RX RMC M U X SD ABC RX RX Radio Utilization PMs PTP 820G supports the following counters. and used to generate the following PMs for every 15-minute interval: o Peak Utilization (%) o Average Utilization (%) o Over-Threshold Utilization (seconds). and used to generate the following PMs for every 15-minute interval: o Peak Capacity o Average Capacity o Over-Threshold Utilization (seconds). Radio Traffic Throughput – Measures the total effective Layer 2 traffic sent through the radio (Mbps). and used to generate the following PMs for every 15-minute interval: o Peak Throughput o Average Throughput o Over-Threshold Utilization (seconds).  Frame Error Rate – Measures the frame error rate (%). The threshold is defined as 0.

including the same RFU. PTP 820G’s Header De-Duplication option is one of the innovative techniques that enables PTP 820G to boost capacity and provide operators with efficient spectrum utilization. 23. and up to 1 Gbps with Header De-Duplication. Once the high-priority frames are transmitted. This section includes:  Capacity Summary  Header De-Duplication  Latency  Frame Cut-Through Capacity Summary Each carrier in a PTP 820G provides the following capacity:  Supported Channels Bandwidth–7/14/28/30/40/50/56 MHz  All licensed bands – L6. 8. with no disruption of traffic and no addition of latency. Another of Cambium Network’s innovative features is Frame Cut-Through. 7. 11. 13. 18. which provides unique delay and delay-variation control for delay-sensitive services. using the same hardware. Note Header De-Duplication is planned for future release. 26.QPSK to 2048 QAM For additional information:  Capacity Specifications phn-3968 001v000 Page 5-6 .  Modulations . 31. 28. 10.Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency Innovative Techniques to Boost Capacity and Reduce Latency PTP 820G utilizes Cambium Network’s innovative technology to provide a high-capacity lowlatency solution. Frame Cut-Through enables highpriority frames to bypass lower priority frames even when the lower-priority frames have already begun to be transmitted. 15. transmission of the lowerpriority frames is resumed with no capacity loss and no re-transmission required. PTP 820G also utilizes established Cambium Networks technology to provide low latency representing a 50% latency reduction for Ethernet services compared to the industry benchmark for wireless backhaul. 38 GHz  High scalability – From 100 Mbps to 500 Mbps. U6.

 Layer3 – Header De-Duplication operates on the Ethernet and IP levels. PTP 820G still removes the IFG and Preamble fields. Header Duplication is also some times knan as head compression. This is done using a sophisticated algorithm that learns unique flows by looking for repeating frame headers in the traffic stream over the radio link and compressing them. The principle underlying this feature is that frame headers in today’s networks use a long protocol stack that contains a significant amount of redundant information. PTP 820G offers the option of Header De-Duplication. The user can determine the layer or layers on which Header De-Duplication operates. Note Without Header De-Duplication. enabling operators to significantly improve Ethernet throughput over the radio link without affecting user traffic. In Header De-Duplication can be customized for optimal benefit accordingly to network usage. with the following options available:  Layer2 – Header De-Duplication operates on the Ethernet level. phn-3968 001v000 Page 5-7 . This mechanism operates automatically.Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency Header De-Duplication Note Header De-Duplication is planned for future release.  Layer4 – Header De-Duplication operates on all supported layers up to Layer 4.  MPLS – Header De-Duplication operates on the Ethernet and MPLS levels. Figure 12 Header De-Duplication Header De-Duplication identifies traffic flows and replaces the header fields with a "flow ID". even if Header De-Duplication is not selected by the user. Header De-Duplication can be configured to operate on various layers of the protocol stack saving bandwidth by reducing unnecessary header overhead.

 Tunnel-Layer4 – Header De-Duplication operates on Layer 2. Operators must balance the depth of De-Duplication against the number of flows in order to ensure maximum efficiency. Layer 3. Layer 3. and on the Tunnel and T3 layers for packets carrying GTP or GRE frames. Figure 13 Header De-Duplication Potential Throughput Savings per Layer IP-20G Layer 2 | Untagged/C/S Tag/Double Tag Up to 22 bytes compressed Layer 2.  Tunnel-Layer3 – Header De-Duplication operates on Layer 2. T-3. Layer 3.Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency  Tunnel – Header De-Duplication operates on Layer 2. and on the Tunnel. and T-4 layers for packets carrying GTP or GRE frames. Up to 256 concurrent flows are supported. The following graphic illustrates how Header De-Duplication can save up to 148 bytes per frame.5 | MPLS: up to 7 Tunnels (Untagged/C-Tag) Up to 28 bytes compressed Layer 3 | IPv4/IPv6 18/40 bytes compressed Layer 4 | TCP/UDP 4/6 bytes compressed Tunneling Layer | GTP (LTE) / GRE 6 bytes compressed End User Inner Layer 3 | IPv4/IPv6 18/40 bytes compressed End User Inner Layer 4 | TCP/UDP 4/6 bytes compressed End User phn-3968 001v000 Page 5-8 . and on the Tunnel layer for packets carrying GTP or GRE frames.

With Frame Cut-Through. phn-3968 001v000 Page 5-9 . such as the number of currently active flows and the number of flows by specific flow type. This information can be used by operators to monitor network usage and capacity. and optimize the Header DeDuplication settings. PTP 820G provides counters when Header De-Duplication is enabled. high-priority frames are pushed ahead of lower priority frames. the operator can adjust these settings to ensure that the network achieves the highest possible effective throughput. such as CES. and control protocols. delay-sensitive traffic. This provides operators with: Immunity to head-of-line blocking effects – key for transporting high-priority. making it the obvious choice for LTE (Long-Term Evolution) networks. These counters include real-time information.Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency Depnding on the packet size and network topology. Latency PTP 820G provides best-in-class latency (RFC-2544) for all channels. PTP 820G’s ability to meet the stringent latency requirements for LTE systems provides the key to expanded broadband wireless services:  Longer radio chains  Larger radio rings  Shorter recovery times  More capacity  Easing of Broadband Wireless Access (BWA) limitations Frame Cut-Through Related topics:  Ethernet Latency Specifications  Egress Scheduling Frame Cut-Through is a unique and innovative feature that ensures low latency for delaysensitive services. See Ethernet Latency Specifications on page 8-30. Header De-Duplication can be increase capacity by up to:  50% (256 byte packets)  25% (512 byte packets)  8% (1518 byte packets) Header De-Duplication Counters In order to help operators optimize Header De-Duplication. VoIP. By monitoring the effectiveness of the Header De-Duplication settings. even if transmission of the lower priority frames has already begun. Once the high priority frame has been transmitted. transmission of the lower priority frame is resumed with no capacity loss and no re-transmission required.

with true transparency to lower priority services.Through   Max Delay  Max Delay Propagation Delay Frame Cut-Through Basic Operation Using Frame Cut-Through. o Improved QoE for VoIP and other streaming applications. Figure 14 Propagation Delay with and without Frame Cut-Through With Frame Cut-Through Without Frame Cut. all frames that are classified to a CoS queue with 4th (highest) priority..e. i. frames assigned to high priority queues can pre-empt frames already in transmission over the radio from other queues. This feature provides services that are sensitive to delay and delay variation. o Expedited delivery of critical control frames. phn-3968 001v000 Page 5-10 . Frame Cut-Through applies to all high priority frames. such as VoIP.Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency Reduced delay-variation and maximum-delay over the link: o Reduced end-to-end delay for TDM services. Figure 15 Frame Cut-Through Frame 1 Frame 2 Frame 3 Frame 4 Start Frame Cut-Through Frame 4 End Frame 5 When enabled. low-delay traffic stream. Transmission of the preempted frames is resumed after the cut-through with no capacity loss or re-transmission required. by enabling the transmission of a high-priority.

Chapter 5: Feature Description Innovative Techniques to Boost Capacity and Reduce Latency Figure 16 Frame Cut-Through Operation phn-3968 001v000 Page 5-11 .

PTP 820G utilizes advanced ACM technology. thereby transmitting two separate carrier waves over the same frequency. thus maintaining even the most stringent service level agreements (SLAs). XPIC enables operators to double their capacity by utilizing dual-polarization radio over a single-frequency channel. even interruptions as short as 50 milliseconds can lead to timeout of TCP/IP sessions. PTP 820G also supports Cross Polarization Interface Canceller (XPIC). Adaptive Coding Modulation (ACM) This feature requires:  ACM script Related topics:  Cross Polarization Interference Canceller (XPIC)  Quality of Service (QoS) PTP 820G employs full-range dynamic ACM. Ten Working Points PTP 820G implements ACM with 10 available working points.Chapter 5: Feature Description Radio Features Radio Features This chapter describes the main PTP 820G radio features. PTP 820G’s ACM mechanism copes with 90 dB per second fading in order to ensure high transmission quality. which are followed by a drastic throughout decrease while these sessions recover. Cambium Networks was the first to introduce hitless and errorless Adaptive Coding Modulation (ACM) to provide dynamic adjustment of the radio’s modulation from QPSK to 256 QAM. ACM shifts modulations instantaneously in response to changes in fading conditions. and extends it to the range of QPSK to 1024 QAM. The hitless and errorless functionality of PTP 820G’s ACM has another major advantage in that it ensures that TCP/IP sessions do not time-out. Without ACM. as follows: phn-3968 001v000 Page 5-12 . PTP 820G’s ACM mechanism is designed to work with PTP 820G’s QoS mechanism to ensure that high priority voice and data frames are never dropped. but with alternating polarities. This section includes:  Adaptive Coding Modulation (ACM)  Cross Polarization Interference Canceller (XPIC)  1+1 HSB Radio Protection  ATPC  Multi-Carrier ABC  BBS Space Diversity  Error! Reference source not found.

The system continues to operate at 64 QAM until the fading condition either intensifies or disappears. the modulation is switched back to the next higher step (e. If the fade intensifies.Chapter 5: Feature Description Radio Features Table 6 ACM Working Points (Profiles) Working Point (Profile) Modulation Profile 0 QPSK Profile 1 8 PSK Profile 2 16 QAM Profile 3 32 QAM Profile 4 64 QAM Profile 5 128 QAM Profile 6 256 QAM Profile 7 512 QAM Profile 8 1024 QAM (Strong FEC) Profile 9 1024 QAM (Light FEC) Figure 17 Adaptive Coding and Modulation with 10 Working Points Hitless and Errorless Step-by Step Adjustments ACM works as follows. If. and can reach all the way down to QPSK during extreme conditions. This is an errorless. 128 QAM) and so on. phn-3968 001v000 Page 5-13 .The switching continues automatically and as quickly as needed. when the receive signal Bit Error Ratio (BER) level reaches a predetermined threshold. the system preemptively switches to 64 QAM and the throughput is stepped down to ~140 Mbps. on the other hand. virtually instantaneous switch.g. step by step .. Assuming a system configured for 128 QAM with ~170 Mbps capacity over a 30 MHz channel. another switch takes the system down to 32 QAM. the weather condition improves.

The ACM TX profile can be different from the ACM RX profile. phn-3968 001v000 Page 5-14 . and the ACM engine will be forced to be OFF. In this mode. Users also have the option of running an ACM script in Fixed mode. according to a wide range of criteria. ACM is not active. If you want to rely on an external switch’s QoS. In this mode. Adaptive mode requires an ACM activation key. even if channel fading conditions allow it. If MSE degrades below a predefined threshold. the system will not climb above profile 5. and defines the profile’s capacity (bps). For ACM to be active. thus maintaining even the most stringent SLAs. Instead. users can configure PTP 820G to discard only low priority frames as conditions deteriorate. When an ACM script is activated. When MSE improves above a predefined threshold. For example. ACM can work with the switch via the flow control mechanism supported in the radio. ACM Benefits The advantages of PTP 820G’s dynamic ACM include:  Maximized spectrum usage  Increased capacity over a given bandwidth  10 working points.Chapter 5: Feature Description Radio Features ACM Radio Scripts An ACM radio script is constructed of a set of profiles. ACM and Built-In QoS PTP 820G’s ACM mechanism is designed to work with PTP 820G’s QoS mechanism to ensure that high priority voice and data frames are never dropped. the user can select the specific profile from all available profiles in the script. if the user selects a maximum profile of 5. Each profile is defined by a modulation order (QAM) and coding rate. The user can define a maximum profile. the ACM script must be run in Adaptive mode. all the required conditions for XPIC apply. with~3 db system gain for each point change  Hitless and errorless modulation/coding changes. The ACM TX profile is determined by remote RX MSE performance. without affecting traffic. The selected profile is the only profile that will be valid. In the case of XPIC/ACM scripts. RX generates a request to the remote TX to downgrade its profile. the system automatically chooses which profile to use according to the channel fading conditions. Fixed mode can be chosen without an ACM activation key. ACM profiles are decreased or increased in an errorless operation. The RX end is the one that initiates an ACM profile upgrade or downgrade. Since QoS provides priority support for different classes of service. based on signal quality  Adaptive Radio Tx Power per modulation for maximum system gain per working point  An integrated QoS mechanism that enables intelligent congestion management to ensure that high priority traffic is not affected during link fading conditions. which means that the radio adapts its profile according to the channel fading conditions. the ACM engine is running. RX generates a request to the remote TX to upgrade its profile.

phn-3968 001v000 Page 5-15 . Despite the obvious advantages of dual-polarization.  XPIC script XPIC is one of the best ways to break the barriers of spectral efficiency. This maximizes system gain and optimizes ACM behavior for the following reasons:  In the TX direction. That depends on whether the Standby TX was able to follow the remote RX Active unit’s ACM requests (only the active remote RX sends ACM request messages). Using dual-polarization radio over a single-frequency channel. or might stay at the lowest profile (profile-0). The following ACM behavior should be expected in a 1+1 configuration:  In the TX direction.  In the RX direction. making cross-polarization interference unavoidable.  In the RX direction. Cross Polarization Interference Canceller (XPIC) This feature requires:  PTP 820G hardware assembly with two radio interfaces. a dual polarization radio transmits two separate carrier waves over the same frequency. one must also keep in mind that typical antennas cannot completely isolate the two polarizations. but using alternating polarities. propagation effects such as rain can cause polarization rotation. both the active and the standby carriers follow the remote Active TX profile (which is the only active transmitter). the Active TX will follow the remote Active RX ACM requests (according to the remote Active Rx MSE performance).  The Standby TX might have the same profile as the Active TX. the received signal will be minimally attenuated. the receiver will be able to lock on a higher ACM profile (according to what is dictated by the RF channel conditions). the power will experience minimal attenuation. Thus. it is essential to feed the active RFU via the main channel of the coupler (lossless channel). In addition. and to feed the standby RFU via the secondary channel of the coupler (-6db attenuated channel).Chapter 5: Feature Description Radio Features ACM and 1+1 HSB When ACM is activated together with 1+1 HSB protection.

While lower spectral efficiency systems (with low SNR requirements such as QPSK) can easily tolerate such interference. The same happens with the vertical (V) signal reception= V+h. The XPIC mechanism utilizes the received signals from the V and H modems to extract the V and H signals and cancel the cross polarization interference due to physical signal leakage between V and H polarizations. to denote that it is the interfering signal). XPIC Implementation PTP 820G units with dual radio interfaces can support XPIC in a single unit utilizing the two carriers. For high-modulation schemes such as 1024 QAM. Figure 19 XPIC Implementation The H+v signal is the combination of the desired signal H (horizontal) and the interfering signal V (in lower case. at the right phase and level. an improvement factor of more than 20 dB is required so that crossinterference does not adversely affect performance. The following figure is a basic graphic representation of the signals involved in this process. manipulates them to produce the desired data. higher modulation schemes cannot and require XPIC. The XPIC mechanism uses the received signals from both feeds and. phn-3968 001v000 Page 5-16 . operating at a frequency of 30 GHz. PTP 820G’s XPIC algorithm enables detection of both streams even under the worst levels of XPD such as 10 dB.Chapter 5: Feature Description Radio Features Figure 18 Dual Polarization The relative level of interference is referred to as cross-polarization discrimination (XPD). PTP 820G accomplishes this by adaptively subtracting from each carrier the interfering cross carrier.

The interfaces in a protected pair operate in active and standby mode. In a 1+1 HSB configuration. Each carrier in a protected pair reports its status to the CPU. phn-3968 001v000 Page 5-17 . all the following conditions must be met:  Communications with the RFU must be established by both radio interfaces. signal.  RFU type must be the same for both carriers. In order for XPIC to be operational. 1+1 HSB Radio Protection This feature requires:  PTP 820G hardware assembly with two radio interfaces.  1+1 HSB protection must not be enabled. 1+1 HSB protection provides full protection in the event of interface. If there is a failure in the active radio interface or RFU. an alarm will alert the user. Conditions for XPIC XPIC is enabled by selecting an XPIC script for each carrier. For exact figures. In addition.Chapter 5: Feature Description Radio Features Figure 20 XPIC – Impact of Misalignments and Channel Degradation PTP 820G’s XPIC reaches a BER of 10e-6 at a high level of co-channel interference (modulationdependent). The CPU is responsible for determining when a switchover takes place.  The script must support XPIC If any of these conditions is not met. contact your Cambium representative.  The same script must be loaded for both carriers. events will inform the user which conditions are not met. the RFUs must be the same type and must have the same configuration. or RFU failure. PTP 820G offers radio redundancy via 1+1 HSB protection.  The frequency of both radios must be equal. the standby interface and RFU pair switches to active mode.

Whenever the primary path is operational and available. This makes it unnecessary to perform a copy-to-mate command when a configuration change is made. in order to maintain the carrier configuration alignment. When a pair of carriers is defined as a 1+1 HSB pair. Revertive HSB Protection In an HSB protection scheme. The primary radio should be the radio on the coupler’s main path and the secondary radio should be the radio on the coupling path. This mechanism is activated by the system periodically and independently of other protection mechanisms. phn-3968 001v000 Page 5-18 . the active and standby radios are usually connected to the antenna with a coupler. at fixed intervals. and then perform a copy to mate command. the user must first complete the required configuration of the active radio interface. This additional path loss will either reduce the link’s fade margin or increase the power consumption of the Power Amplifier (PA) in order to compensate for the additional path loss. any configuration performed on the active carrier will be automatically copied to the standby carrier. Figure 21 Path Loss on Secondary Path of 1+1 HSB Protection Link Coupler -6d Coupler -6d B B Primary Radio Primary Radio Main Path Main Path Coupling Path Coupling Path Secondary Radio Secondary Radio PTP 820G supports revertive HSB protection. Every revertive protection switch is recorded as an event in the event log. the mechanism clears the Mate Configuration Mismatch alarm. resulting in a 12dB increase in the total path loss for the link. In order to align the configuration between the active and standby carriers.Chapter 5: Feature Description Radio Features PTP 820G includes a mismatch mechanism that detects if there is a mismatch between the radio configurations of the local and mate interfaces and RFUs. The advantage of using revertive HSB mode is that the radio link budget will benefit from additional gain whenever it is possible to activate the primary path. This command copies the entire configuration of the active interface to the standby interface to achieve full configuration alignment between the active and standby carriers. user defines the primary radio on each side of the link. without any alarms. In revertive HSB protection mode. the system initiates a revertive protection switch. This causes a -6dB loss on the secondary path on each side of the link. The system monitors the availability of the primary path at all times. It is activated asynchronously for both the active and the standby carriers. but the secondary path is active. Once the mismatch mechanism detects a configuration mismatch. it raises a Mate Configuration Mismatch alarm. When the configuration of the active and standby carriers is changed to be identical.

ATPC enables the transmitter to operate at less than maximum power for most of the time. with the highest priority triggers listed first. When fading conditions occur. phn-3968 001v000 Page 5-19 . 6 Hardware module missing 7 Lockout 8 Force switch 9 Traffic failures 10 Manual switch ATPC ATPC is a closed-loop mechanism by which each carrier changes the transmitted signal power according to the indication received across the link. The ATPC mechanism has several potential advantages. including less transmitter power consumption and longer amplifier component life. thereby reducing overall system cost. transmit power is increased as needed until the maximum is reached.Chapter 5: Feature Description Radio Features Note Each protection switch causes traffic disruption. ATPC is frequently used as a means to mitigate frequency interference issues with the environment. in order to achieve a desired RSL on the other side of the link. Switchover Triggers The following events trigger switchover for 1+1 HSB protection according to their priority. thus allowing new radio links to be easily coordinated in frequency congested areas.

each carrier fluctuates independently with hitless switchovers between modulations. Both the Ethernet link and the TDM links will be available over radios with individual variable capacity. In Multi-Carrier ABC mode.Chapter 5: Feature Description Radio Features Multi-Carrier ABC This feature requires:  PTP 820G hardware assembly with two radio interfaces. traffic is divided among the carriers optimally at the radio frame level without requiring Ethernet link aggregation (LAG). Multi-Carrier Adaptive Bandwidth Control (Multi-Carrier ABC) is an innovative technology that creates logical bundles of multiple radio links optimized for wireless backhaul applications. MultiCarrier ABC enables separate radio carriers to be combined into a virtual transport pipe for a high capacity Ethernet link and individual TDM links. Note Multi-Carrier ABC support is planned for future release. The result is 100% utilization of radio resources in which traffic load is balanced based on instantaneous radio capacity per carrier. In such conditions. the TDM links can be preserved by a sophisticated prioritizing scheme configured by the user. The following diagram illustrates the Multi-Carrier ABC traffic flow. During fading events which cause ACM modulation changes. Load balancing is performed without regard to the number of MAC addresses or the number of traffic flows. Figure 22 Multi-Carrier ABC Traffic Flow Eth Carrier 1 Carrier 1 Carrier 2 Carrier 2 Traffic Combiner Traffic Splitter Carrier 3 Carrier 3 Carrier 4 Carrier 4 phn-3968 001v000 Page 5-20 Eth . increasing capacity over a given bandwidth and maximizing spectrum utilization. and handled by a prioritizing scheme.

This latency variation is slightly more complicated to predict if the various radio carriers run different radio scripts. Alignment does not add any delay to the slowest carrier. the data path remains error free. The block size. The block size may vary from one block to the other. Even when one or more carriers are operating at limited capacity or are totally down. which means that all channels must wait for the slowest arriving block. all blocks are aligned. Multi-Carrier ABC can tolerate a large difference in the degree of delay between the slowest and the fastest arriving carriers. not all data is lost. Adding or removing a channel is hitless. bandwidth is simply reduced until the link returns to service. PTP 820G supports the following configurations:  2+0 ABC  1+1 BBS Space Diversity Multi-Carrier ABC Operation Multi-Carrier ABC divides each radio carrier into blocks of data. This ensures that if one link is lost. Multi-Carrier ABC and ACM Multi-Carrier ABC automatically adapts to capacity changes that result from changes in the current ACM profile. Graceful Degradation of Service Multi-Carrier ABC provides for protection and graceful degradation of service in the event of failure of an RFU or the slave carrier. Multi-Carrier ABC responds by changing the block size of that channel. phn-3968 001v000 Page 5-21 . the carrier is removed from the aggregated link before bit errors arise. i. When all channels are up and running. the latency variation for the aggregated data stream is determined by the latency variation of one radio channel. In the event of degradation in a particular carrier. When an ACM profile change takes place on a specific carrier. When all channels run the same radio script. since each radio script has a unique delay distribution. On the receiving side of the link. is configured based on the capacity of the carrier’s ACM profile. Multi-Carrier ABC provides the maximum available aggregated capacity. The system determines which radio carriers contribute to the aggregated link. The latency of the aggregated data flow is determined by the slowest arriving carrier.. independently for each radio carrier. can also be used. based on the received channel qualities. so as not to disturb the aggregated data flow. Other criteria. Instead. such as ACM profile and latency.e.Chapter 5: Feature Description Radio Features Multi-Carrier Configurations In ABC Multi-Carrier mode. A low ACM profile means more latency compared to a higher ACM profile. the number of data bytes inside a block.

The same data stream is received by both antennas. The Multi-Carrier ABC mechanism constantly monitors the signal quality of the main and diversity carrier. Note 2048 QAM support is planned for future release. Switching between the main and diversity carriers is hitless. The antennas must be separated by approximately 15 to 20 meters. In flat fading. all frequency components of the signal experience the same magnitude of fading. which can cause distortion of the signal resulting in signal fade. radios. phn-3968 001v000 Page 5-22 . or frequency selective fading. In dispersive. and selects the signal with the best quality. BBS Space Diversity requires two antennas and RFUs. multipath phenomena are common. Figure 23 Direct and Reflected Signals Space Diversity is a common way to negate the effects of fading caused by multipath phenomena. This fading phenomenon depends mainly on the link geometry and is more severe at long distance links and over flat surfaces or water. and modems at the receiving end of the link. In long distance wireless links with relatively low frequency. The impact of this distortion can vary over time. Fading can be flat or dispersive.Chapter 5: Feature Description Radio Features BBS Space Diversity This feature requires:  PTP 82G hardware assembly with two radio interfaces. space. It is also affected by air turbulence and water vapor. Space Diversity is implemented by placing two separate antennas at a distance from one another that makes it statistically likely that if one antenna suffers from fading caused by signal reflection. and frequency. and can vary quickly during temperature changes due to rapid changes in the reflections phase. Both direct and reflected signals are received. the other antenna will continue to receive a viable signal. different frequency components of the signal experience decorrelated fading.

The utilization threshold can be defined by the user (0-100%). The threshold is defined as 0. and used to generate the following PMs for every 15-minute interval: o Peak Utilization (%) o Average Utilization (%) o Over-Threshold Utilization (seconds). Radio Traffic Throughput – Measures the total effective Layer 2 traffic sent through the radio (Mbps). The threshold is defined as 0. as well as additional PMs based on these counters:     Radio Traffic Utilization – Measures the percentage of radio capacity utilization.Chapter 5: Feature Description Radio Features Figure 24 1+1 BBS Space Diversity Configuration – Receiving Side Radio & RX RMC M U X SD ABC RX RX Radio Utilization PMs PTP 820G supports the following counters. Radio Traffic Capacity – Measures the total L1 bandwidth (payload plus overheads) sent through the radio (Mbps). and used to generate the following PMs for every 15-minute interval: o Peak Capacity o Average Capacity o Over-Threshold Utilization (seconds). phn-3968 001v000 Page 5-23 . and used to generate the following PMs for every 15-minute interval: o Peak Throughput o Average Throughput o Over-Threshold Utilization (seconds). and used to generate Frame Error Rate PMs for every 15-minute interval. Frame Error Rate – Measures the frame error rate (%).

activate. This section includes:  Ethernet Services Overview  PTP 820G’s Ethernet Capabilities  Supported Standards  Ethernet Service Model  Ethernet Interfaces  Quality of Service (QoS)  Global Switch Configuration  Network Resiliency  OAM Ethernet Services Overview The PTP 820G services model is premised on supporting the standard MEF services (MEF 6. application. for a total of six Ethernet interfaces available for traffic. enabling users to plan. PTP 820G’s service-oriented Ethernet paradigm enables operators to configure VLAN definition and translation. Operationally. then goes on to provide a basic overview of PTP 820G‘s Ethernet services implementation. and maintain any packet-based network scenario. security. PTP 820G also includes two FE interfaces for management. CoS. and interface level. or in any other way that reflects the operator’s business and network requirements. service-point. PTP 820G provides personalized and granular QoS that enables operators to customize traffic management parameters per customer. 10). the PTP 820G Ethernet services model is designed to offer a rich feature set combined with simple and user-friendly configuration. service type. PTP 820G contains four electrical and two optical 1 GE Ethernet interfaces. This section first describes the basic Ethernet services model as it is defined by the MEF. and builds upon this support by the use of very high granularity and flexibility. phn-3968 001v000 Page 5-24 . The following figure illustrates the basic MEF Ethernet services model.Chapter 5: Feature Description Ethernet Features Ethernet Features PTP 820G features a service-oriented Ethernet switching fabric. and network resiliency on a service.

as shown in the following figure. phn-3968 001v000 Page 5-25 . MPLS.3 Ethernet PHY and MAC.Chapter 5: Feature Description Ethernet Features Figure 25 Basic Ethernet Service Model In this illustration. enabling the transfer of Ethernet frames between them. and GFP. or host (end system). with a standard IEEE 802. A NI is defined as the demarcation point between the customer (subscriber) and provider network. Connectivity between UNIs is defined as an Ethernet Virtual Connection (EVC). Figure 26 Ethernet Virtual Connection (EVC) An EVC is defined by the MEF as an association of two or more UNIs that limits the exchange of service frames to UNIs in the Ethernet Virtual Connection. ATM. 1 Gbps). bridge/switch. The services are defined from the point of view of the network’s subscribers (users). the network connection at the user side of the UNI is only Ethernet. Ethernet services can be supported over a variety of transport technologies and protocols in the MEN. such as SDH/SONET. the Ethernet service is conveyed by the Metro Ethernet Network (MEN) provider. Ethernet. The EVC perform two main functions:  Connects two or more customer sites (UNIs). EVC Subscriber services extend from UNI to UNI. The CE may be a router. from the user’s perspective. However. Customer Equipment (CE) is connected to the network at the User Network Interface (UNI) using a standard Ethernet interface (10/100 Mbps.

and the others defined as Leaves. and to avoid delivery to a UNI that does not belong to the EVC. an EVC can be used to form a Layer 2 private line or Virtual Private Network (VPN). In the figure below. Service frames must be delivered with the same Ethernet MAC address and frame structure that they had upon ingress to the service. The MEF has defined three types of EVCs: 1 Point to Point EVC – Each EVC contains exactly two UNIs. but not to other Leaves. An ingress service frame that is mapped to the EVC can be delivered to one or more of the UNIs in the EVC. with one or more UNIs defined as Roots. three sites belong to a single Multipoint EVC and can forward Ethernet frames to each other. phn-3968 001v000 Page 5-26 . other than the ingress UNI. A single UNI can support multiple EVCs via the Service Multiplexing attribute. One or more VLANs can be mapped (bundled) to a single EVC.Chapter 5: Feature Description  Ethernet Features Prevents data transfer involving customer sites that are not part of the same EVC. The Roots can forward frames to the Leaves. In other words. Figure 27 Point to Point EVC 2 Multipoint (Multipoint-to-Multipoint) EVC – Each EVC contains two or more UNIs. An EVC is always bi-directional in the sense that ingress service frames can originate at any UNI in an EVC. the frame must be unchanged from source to destination. Based on these characteristics. It is vital to avoid delivery back to the ingress UNI. Figure 28 Multipoint to Multipoint EVC 3 Rooted Multipoint EVC (Point-to-Multipoint) – Each EVC contains one or more UNIs. This feature enables the EVC to maintain a secure and private data channel. Leaves can only forward frames to the Roots. in contrast to routing in which headers are discarded. The following figure shows two point-to-point EVCs connecting one site to two other sites.

or per CoS identifier for a specified EVC at the UNI.  Service frames that do not comply with the bandwidth profile are dropped at the ingress interface. respectively. The Color of the service frame is used to determine its bandwidth profile.  Service frames that comply with the bandwidth profile are forwarded. phn-3968 001v000 Page 5-27 . At ingress.Chapter 5: Feature Description Ethernet Features Figure 29 Rooted Multipoint EVC In the PTP 820G. the average and maximum service frame rates are less than or equal to the CIR and CBS.  Bandwidth profiles can be defined separately for each UNI (MEF 10. The MEF has defined the following three bandwidth profile service attributes:  Ingress BW profile per ingress UNI  Ingress BW profile per EVC  Ingress BW profile per CoS identifier The BW profile service attribute consists of four traffic parameters:  CIR (Committed Information Rate)  CBS (Committed Burst Size)  EIR (Excess Information Rate)  EBS (Excess Burst Size) Bandwidth profiles can be applied per UNI. it is marked Green. an EVC is defined by either a VLAN or by Layer 1 connectivity (Pipe Mode). If the service frame complies with the CIR and EIR defined in the bandwidth profile. Bandwidth Profile The bandwidth profile (BW profile) is a set of traffic parameters that define the maximum limits of the customer’s traffic.2). per EVC at the UNI. the bandwidth profile limits the traffic transmitted into the network:  Each service frame is checked against the profile for compliance with the profile. In this case.

PTP 820G supports a variety of service types defined by the MEF. phn-3968 001v000 Page 5-28 . it is marked Yellow. Services using All-to-One Bundling UNIs (port-based) are referred to as “Private” services. This relationship is shown in the following table. but does comply with the EIR and EBS. In the PTP 820G. Each Ethernet service type has a set of Ethernet service attributes that define the characteristics of the service. These services are differentiated by the method for service identification used at the UNIs. Ethernet Services Definitions The MEF provides a model for defining Ethernet services. and the maximum service frame size is less than the EBS. including their associated service attributes and parameters:  Ethernet Line (E-Line)  Ethernet LAN (E-LAN)  Ethernet Tree (E-Tree) Multiple Ethernet services are defined for each of the three generic Ethernet service types. bandwidth profiles are constructed using a full standardized TrTCM policer mechanism. Figure 30 MEF Ethernet Services Definition Framework The MEF defines three generic Ethernet service type constructs. it is marked Red and discarded. These Ethernet service attributes in turn are associated with a set of parameters that provide various options for the various service attributes. If the service frame fails to comply with both the CIR and the EIR defined in the bandwidth profile.Chapter 5: Feature Description Ethernet Features If the service frame does not comply with the CIR defined in the bandwidth profile. but there are also differences as explained below. All of these service types share some common attributes. while services using Service Multiplexed (VLAN-based) UNIs are referred to as “Virtual Private” services. In this case. the average service frame rate is greater than the CIR but less than the EIR. The purpose of the MEF model is to help subscribers better understand the variations among different types of Ethernet services. Ethernet service types are generic constructs used to create a broad range of services.

delay variation.Chapter 5: Feature Description Ethernet Features Table 7 MEF-Defined Ethernet Service Types Port Based VLAN-BASED (All to One Bundling) (EVC identified by VLAN ID) Ethernet Private Line (EPL) Ethernet Virtual Private Line (EVPL) Ethernet Private LAN (EP-LAN) Ethernet Virtual Private LAN (EVP-LAN) Ethernet Private Tree (EP-Tree) Ethernet Virtual Private Tree (EVP-Tree) All-to-One Bundling refers to a UNI attribute in which all Customer Edge VLAN IDs (CE-VLAN IDs) entering the service via the UNI are associated with a single EVC. Bundling refers to a UNI attribute in which more than one CE-VLAN ID can be associated with an EVC. To fully specify an Ethernet service. and availability for a given Class of Service (CoS) instance. The E-Line service type can be used to create a broad range of Ethernet point-to-point services and to maintain the necessary connectivity. e. For example. delay. phn-3968 001v000 Page 5-29 . more than one point-to-point EVC can be offered on the same physical port at one or both of the UNIs. loss. In its simplest form. an E-Line service type can provide connectivity between two UNIs with different line rates and can be defined with performance assurances such as CIR with an associated CBS. EIR with an associated EBS.. In more sophisticated forms. additional service attributes must be defined in addition to the UNI and EVC service attributes. an E-Line service type can provide symmetrical bandwidth for data sent in either direction with no performance assurances. best effort service between two FE UNIs. Service multiplexing can occur at one or both UNIs in the EVC.g. These service attributes can be grouped under the following categories:  Ethernet physical interfaces  Traffic parameters  Performance parameters  Class of service  Service frame delivery  VLAN tag support  Service multiplexing  Bundling  Security filters E-Line Service The Ethernet line service (E-Line service) provides a point-to-point Ethernet Virtual Connection (EVC) between two UNIs.

An EPL service uses a point-to-point EVC between two UNIs and provides a high degree of transparency for service frames between the UNIs that it interconnects such that the service frame’s header and payload are identical at both the source and destination UNI when the service frame is delivered (L1 service). the degree of transparency for service frames is lower in an EVPL than in an EPL. First. an EPL only enables a single service to be delivered over a single physical connection. which means it enables multiple EVCs to be delivered to customer premises over a single physical connection (UNI). an EVPL provides for service multiplexing at the UNI. with a single EVC across dedicated UNIs providing site-to-site connectivity. In contrast. However. In cases where the EVC speed is less than the UNI speed. phn-3968 001v000 Page 5-30 . and is used in diverse applications such as replacing a TDM private line.Chapter 5: Feature Description Ethernet Features Figure 31 E-Line Service Type Using Point-to-Point EVC Ethernet Private Line Service An Ethernet Private Line (EPL) service is specified using an E-Line Service type. several characteristics differ between EPL and EVPL services. Figure 32 EPL Application Example Ethernet Virtual Private Line Service An Ethernet Virtual Private Line (EVPL) is created using an E-Line service type. the CE is expected to shape traffic to the ingress bandwidth profile of the service to prevent the traffic from being discarded by the service. All service frames are mapped to a single EVC at the UNI. EPL is the most popular Ethernet service type due to its simplicity. Second. An EVPL can be used to create services similar to EPL services. The EPL is a portbased service. A dedicated UNI (physical interface) is used for the service and service multiplexing is not allowed.

Each site (UNI) is connected to a multipoint EVC. from the point of view of a customer using an E-LAN service. service multiplexing may occur at none. EVPL services can be used to replace Frame Relay and ATM L2 VPN services. and provides multipoint connectivity by connecting two or more UNIs. EIR with an associated EBS. some service frames may be sent to one EVC while others may be sent to other EVCs. in order to deliver higher bandwidth. In its basic form. end-to-end services. an E-LAN service can provide a best effort service with no performance assurances between the UNIs. they can be connected to the same multipoint EVC. If additional sites are added. loss. delay. For an E-LAN service type. an E-LAN service type can be defined with performance assurances such as CIR with an associated CBS. delay variation. Figure 33 EVPL Application Example E-LAN Service The E-LAN service type is based on Multipoint to Multipoint EVCs. and customer frames sent from one UNI can be received at one or more UNIs. and availability for a given CoS instance. Figure 34 E-LAN Service Type Using Multipoint-to-Multipoint EVC The E-LAN service type can be used to create a broad range of services. phn-3968 001v000 Page 5-31 . the MEN can be viewed as a LAN. In more sophisticated forms. simplifying the service activation process. an E-LAN service type (Multipoint-to-Multipoint EVC) and an E-Line service type (Point-to-Point EVC) can be service multiplexed at the same UNI. For example. one. or more than one of the UNIs in the EVC. with both services offered via service multiplexing at the same UNI.Chapter 5: Feature Description Ethernet Features Since service multiplexing is permitted in EVPL services. In such a case. Logically. the ELAN service type can be used to interconnect other customer sites while the E-Line service type is used to connect to the Internet.

The EP-LAN is a Layer 2 service in which each UNI is dedicated to the EP-LAN service. Customers commonly require a highly transparent service that connects multiple UNIs. For example. A typical use case for EPLAN services is Transparent LAN. separate EVC to all of the other sites in order to enable the new UNI to communicate with the other UNIs. it is only necessary to add the new UNI to the multipoint EVC. it is necessary to add a new. The Ethernet Private LAN (EP-LAN) service is defined with this in mind. consider a point-to-point network configuration implemented using E-Line services. If a new site (UNI) is added. Figure 35 Adding a Site Using an E-Line service In contrast. Only one EVC is required to achieve multi-site connectivity. Ethernet Private LAN Service It is often desirable to interconnect multiple sites using a Local Area Network (LAN) protocol model and have equivalent performance and access to resources such as servers and storage. as shown in the following figure. such as private LAN and virtual private LAN services. phn-3968 001v000 Page 5-32 .Chapter 5: Feature Description Ethernet Features E-LAN services can simplify the interconnection among a large number of sites. in comparison to hub/mesh topologies implemented using point-to-point networking technologies such as Frame Relay and ATM. Figure 36 Adding a Site Using an E-LAN service The E-LAN service type can be used to create a broad range of services. No additional EVCs are required. as shown in the following figure. when using an E-LAN service. using the E-LAN service type. since the E-LAN service uses a multipoint to multipoint EVC that enables the new UNI to communicate with each of the others UNIs.

EP-LAN supports CEVLAN CoS preservation. In addition. but is not mandatory. Bundling can be used on the UNIs in the Multipoint-to-Multipoint EVC. Customers can use this service to configure VLANs across the sites without the need to coordinate with the service provider. phn-3968 001v000 Page 5-33 . Each interface is configured for All-to-One Bundling.Chapter 5: Feature Description Ethernet Features The following figure shows an example of an EP-LAN service in which the service is defined to provide Customer Edge VLAN (CE-VLAN) tag preservation and tunneling for key Layer 2 control protocols. which enables the EP-LAN service to support CE-VLAN ID preservation. while at the same time accessing other services from one or more of those UNIs. The following figure provides an example of an EVP-LAN service. CE-VLAN tag preservation and tunneling of certain Layer 2 control protocols may or may not be provided. The Ethernet Virtual Private LAN (EVP-LAN) service is defined to address this need. Service multiplexing is allowed on each UNI. Figure 37 MEF Ethernet Private LAN Example Ethernet Virtual Private LAN Service Customers often use an E-LAN service type to connect their UNIs in an MEN. EVP-LAN is actually a combination of EVPL and E-LAN. As such. For example. A typical use case would be to provide Internet access a corporate VPN via one UNI. a customer might want to access a public or private IP service from a UNI at the customer site that is also used to provide E-LAN service among the customer’s several metro locations.

Figure 39 E-Tree Service Type Using Rooted-Multipoint EVC Two or more Root UNIs can be supported in advanced forms of the E-Tree service type. In this scenario.Chapter 5: Feature Description Ethernet Features Figure 38 MEF Ethernet Virtual Private LAN Example E-Tree Service The E-Tree service type is an Ethernet service type that is based on Rooted-Multipoint EVCs. A service frame sent from one Leaf UNI cannot be delivered to another Leaf UNI. and video-over-IP applications such as multicast/broadcast packet video. phn-3968 001v000 Page 5-34 . an E-Tree service can provide a single Root for multiple Leaf UNIs. In its basic form. The Root UNIs can communicate with each other. each Leaf UNI can exchange data only with the Root UNIs. Redundant access to the Root can also be provided. This service can be particularly useful for Internet access. Each Leaf UNI can exchange data with only the Root UNI. effectively allowing for enhanced service reliability and flexibility. One or more CoS values can be associated with an E-Tree service.

Ethernet Private Tree Service The Ethernet Private Tree service (EP-Tree) is designed to supply the flexibility for configuring multiple sites so that the services are distributed from a centralized site. the E-Tree service type can be used to support a specific application at the Subscriber UNI. For example. Each interface is configured for All-toOne Bundling. EP-Tree requires dedication of the UNIs to the single EP-Tree service. ISP access to redundant PoPs (multiple Roots at ISP PoPs). e. while the remaining sites are designated as Leaves.. and an E-Line service type using a Point-to-Point EVC. EP-Tree also supports CE-VLAN CoS preservation. which means that EP-Tree services support CE-VLAN ID preservation. In this setup. In this example.g. can be service multiplexed on the same UNI. or from a few centralized sites. The following figure provides an example of an EP-Tree service. an E-Tree service type using a Rooted-Multipoint EVC. Figure 41 MEF Ethernet Private Tree Example phn-3968 001v000 Page 5-35 . while the E-Line Service type is used to connect to another enterprise site with a Point-to-Point EVC. The advantage of such a configuration is that the customer can configure VLANs across its sites without the need to coordinate with the service provider. CE-VLAN tags are preserved and key Layer 2 control protocols are tunneled. the centralized site or sites are designed as Roots.Chapter 5: Feature Description Ethernet Features Figure 40 E-Tree Service Type Using Multiple Roots Service multiplexing is optional and may occur on any combination of UNIs in the EVC.

The following figure provides an example of a Virtual Private Tree service. such as EVPL and EVP-LAN services. the UNIs are attached to the service in a Rooted Multipoint connection. Customer UNIs can also support other services.Chapter 5: Feature Description Ethernet Features Ethernet Virtual Private Tree Service In order to access several applications and services from well-defined access points (Root). Bundling can be used on the UNIs in the Rooted Multipoint EVC. EVP-Tree enables each UNI to support multiple services. A good example would be a customer that has an EVP-LAN service providing data connectivity among three UNIs. Mobile Backhaul refers to the network between the Base Station sites and the Network Controller/Gateway sites for all generations of mobile technologies. As such. An EVP-Tree service is used in such cases. private networks and enterprises. phn-3968 001v000 Page 5-36 . CE-VLAN tag preservation and tunneling of certain Layer 2 Control Protocols may or may not be provided. Figure 42 Ethernet Virtual Private Tree Example PTP 820G enables network connectivity for Mobile Backhaul cellular infrastructure. Mobile equipment and networks with ETH service layer functions can support MEF Carrier Ethernet services using the service attributes defined by the MEF. fixed networks. but it is not mandatory. while using an EVP-Tree service to provide video broadcast from a video hub location.

Additional Layer 1 point-based services are supported as well. as an addition to the baseline definition of MEF Services (MEF 6) using service attributes (as well as in MEF 10). E-Line. E-LAN and E-Tree services are well defined as the standard services. PTP 820G provides rich and secure packet backhaul services over any transport type with unified. PTP 820G Universal Packet Backhaul Services Core PTP 820G addresses the customer demand for multiple services of any of the aforementioned types (EPL. and errorfree operation. Figure 44 Packet Service Core Building Blocks phn-3968 001v000 Page 5-37 . Services support in the mobile backhaul environment is provided using the PTP 820G services core. EP-Tree. simple. mobile backhaul implementation agreement).Chapter 5: Feature Description Ethernet Features Figure 43 Mobile Backhaul Reference Model The PTP 820G services concept is purpose built to support the standard MEF services for mobile backhaul (MEF 22. EVP-LAN. and EVP-Tree) through its rich service model capabilities and flexible integrated switch application. EVPL. which is structured around the building blocks shown in the figure below. EP –LAN. as explained in more detail below.

8 CFM support is planned for future release.1Q/Q-in-Q)  Any topology and any mix of radio and fiber interfaces  Seamless interworking with any optical network (NG-SDH. phn-3968 001v000 Page 5-38 .Chapter 5: Feature Description Ethernet Features Any Service   Ethernet services (EVCs) o E-Line (Point-to-Point) o E-LAN (Multipoint) o E-Tree (Point-to-Multipoint)6 Port based (Smart Pipe) services Any Transport  Native Ethernet (802. IP/MPLS service/VPN routers) Virtual Switching/Forwarding Engine  Clear distinction between user facing service interfaces (UNI) and intra-network interfaces  Fully flexible C-VLAN and S-VLAN encapsulation (classification/preservation/ translation)  Improved security/isolation without limiting C-VLAN reuse by different customers  Per-service MAC learning with 128K MAC addresses support Fully Programmable and Future-Proof  Network-processor-based services core  Ready today to support emerging and future standards and networking protocols Rich Policies and Tools with Unified and Simplified Management  Personalized QoS (H-QoS)7  Superb service OAM (CFM. 7 H-QoS support is planned for future release.8032) 6 E-Tree services are planned for future release. packet optical transport. PM)8  Carrier-grade service resiliency (G.

MPLS. and shaping at each level  1K hierarchical two-rate three-Color policers  o Port based – Unicast.8032) for ring/mesh support 9 E-Tree service support is planned for future release. 802.1q. PTP 820G’s services core includes a rich set of tools that includes:  Service-based Quality of Service (QoS). The following are PTP 820G’s main Carrier Ethernet transport features. Broadcast. simple.  Service OAM. including CFM.Chapter 5: Feature Description Ethernet Features PTP 820G’s Ethernet Capabilities PTP 820G is built upon a service-based paradigm that provides rich and secure frame backhaul services over any type of transport. This rich feature set provides a future-proof architecture to support backhaul evolution for emerging services. flexible frame synchronization solution combining SyncE and 1588v2  Hierarchical QoS with 2K service level queues. 11 LAG support is planned for future release. granular PMs. hierarchical scheduling via WFQ and Strict priority. with unified.  Up to 1024 services  Up to 32 service points per service  All service types: o Point-to-Point (E-Line) o Multipoint (E-LAN) o Point-to-Multipoint (E-Tree) 9 o Smart Pipe o Management  Split horizon between service points10  128K MAC learning table. with separate learning per service (including limiters)  Flexible transport and encapsulation via 802. deep buffering. L3. Ethertype o Service-based o CoS-based Up to four link aggregation groups (LAG)11 o  Hashing based on L2. phn-3968 001v000 Page 5-39 . Multicast. and service activation.8032. and L4 Enhanced <50msec network level resiliency (G. and error-free operation.  Carrier-grade service resiliency using G.1ad (Q-in-Q)  High precision. 10 Split horizon is planned for future release.

see Supported Ethernet Standards. Ethernet Service Model PTP 820G’s service-oriented Ethernet paradigm is based on Carrier-Ethernet Transport (CET).Chapter 5: Feature Description Ethernet Features Supported Standards PTP 820G is fully MEF-9 and MEF-14 certified for all Carrier Ethernet services. while intra-network interfaces (E-NNIs or NNIs) are configured as Service Network Points (SNPs). PTP 820G’s virtual switching/forwarding engine is based on a clear distinction between user-facing service interfaces and intra-network service interfaces. For a full list of standards and certifications supported by PTP 820G. and provides a highly flexible and granular switching fabric for Ethernet services. User-facing interfaces (UNIs) are configured as Service Access Points (SAPs). Figure 45 PTP 820G Services Model phn-3968 001v000 Page 5-40 .

and translation options available. PTP 820G contains a pre-defined management service (Service ID 1025). users can activate the management service and use it for in-band management. To define a service. PTP 820G’s switching fabric is designed to provide a high degree of flexibility in the definition of services and the treatment of data flows as they pass through the switching fabric. Each service constitutes a virtual bridge that defines the connectivity and behavior among the network element interfaces for the specific virtual bridge. Figure 46 PTP 820G Services Core P2P Service Port 1 C-ta g=20 Cta SP SAP g= C-ta SP SAP 10 o 20 00 t SP SAP SP SAP Port 6 Port 7 Untag C-tag=20 00 Port 5 4 2 . This is done by configuring service points (SPs) on these interfaces. If needed. The following figure illustrates the PTP 820G services model. Each service point includes both ingress and egress attributes. Service security and isolation is provided without limiting the C-VLAN reuse capabilities of different customers. with traffic entering and leaving the network element. Users can define up to 1024 services on a single PTP 820G. Service points define the movement of frames through the service. A service point is a logical entity attached to a physical or logical interface. preservation. the user must configure virtual connections among the interfaces that belong to the service.3 tag= SC- SP SAP Port 3 00 g= 10 Multipoint Service Port 2 30 C-tag= SP SAP SP SAP Port 8 200 a g= S-t SP SAP Smart Pipe Service Port 4 SP SAP SP SAP phn-3968 001v000 Page 5-41 Port 9 . with a full range of classification. In addition to user-defined services.Chapter 5: Feature Description Ethernet Features The PTP 820G services core provides for fully flexible C-VLAN and S-VLAN encapsulation. Note Management services can hold up to 30 SPs. A service can hold up to 32 service points.

072 entries. phn-3968 001v000 Page 5-42 . the frame is associated to the specific service to which the service point belongs.Chapter 5: Feature Description Ethernet Features Frame Classification to Service Points and Services Each arriving frame is classified to a specific service point. If the classification mechanism finds a match between the key of the arriving frame and a specific service point.  The frame’s C-VLAN and/or S-VLAN tags. and the other service points in the service are optional egress service points for the frame. based on a key that consists of:  The Interface ID of the interface through which the frame entered the PTP 820G. Services include a MAC entry table of up to 131. Figure 47 PTP 820G Services Flow P2P Service User Port GE/FE Port SAP SAP SNP SAP P2P Service User Port GE/FE Port SAP SAP Network Port SNP SAP Port Ethernet traffic Ethernet Radio Ethernet traffic Ethernet Radio Multipoint Service SAP SNP User Port GE/FE Port Network Port Port SAP SNP Service Types PTP 820G supports the following service types:  Point-to-Point Service (P2P)  MultiPoint Service (MP)  Management Service  Point-to-Multipoint Service (E-Tree) Note E-Tree service support is planned for future release. The frame is then forwarded from the ingress service point to an egress service point by means of flooding or dynamic address learning in the specific service. That service point is called the ingress service point for the frame. with a global aging timer and a maximum learning limiter that are configurable per-service.

Multipoint Service (MP) Multipoint services are used to provide connectivity between two or more service points. When traffic ingresses via one service point. This type of service contains exactly two service points and does not require MAC address-based learning or forwarding. it is directed to one of the service points in the service. and based on the learning and forwarding mechanism. The following figure illustrates a P2P service. other than the ingress service point. it is immediately directed to the other side. the arriving frame is flooded to all the other service points in the service except the ingress service point. phn-3968 001v000 Page 5-43 . When traffic ingresses via one side of the service. according to ingress and egress tunneling rules. Since the route is clear. Figure 48 Point-to-Point Service P2P Service Port 1 Port 4 SP SAP SP SAP Port 2 Port 5 P2P Service Port 3 SP SAP SP SAP Port 6 P2P services provide the building blocks for network services such as E-Line EVC (EPL and EVPL EVCs) and port-based services (Smart Pipe). according to ingress and egress tunneling rules. The following figure illustrates a Multipoint service.Chapter 5: Feature Description Ethernet Features Point to Point Service (P2P) Point-to-point services are used to provide connectivity between two interfaces of the network element. the traffic is tunneled from one side of the service to the other and vice versa. If the destination MAC address is not known by the learning and forwarding mechanism.

When a frame arrives via a specific service point. The following table illustrates the operation of the learning and forwarding mechanism. In parallel with the learning process. the user can disable MAC address learning in the service points to conserve system resources. The maximum size of the MAC forwarding table is configurable per service in granularity of 16 entries. users can limit the size of the MAC forwarding table. the frame is flooded to all service points in the service. phn-3968 001v000 Page 5-44 . PTP 820G performs learning per service in order to enable the use of 1024 virtual bridges in the network element. the learning mechanism checks the MAC forwarding table for the service to which the service point belongs to determine whether that MAC address is known to the service. and for E-Line EVCs (EPL and EVPL EVCs) in which only two service points are active. Learning and Forwarding Mechanism PTP 820G can learn up to 131.Chapter 5: Feature Description Ethernet Features Figure 49 Multipoint Service Multipoint Service Port 1 SP SAP SP SAP Port 4 SP SAP Port 2 Port 5 SP SAP SP SAP Port 3 Port 6 Multipoint services provide the building blocks for network services such as E-LAN EVCs (EP-LAN and EVP-LAN EVCs). the forwarding mechanism searches the service’s MAC forwarding table for the frame’s destination MAC address. If necessary due to security issues or resource limitations. If a match is found. In such a case. If not.072 Ethernet source MAC addresses. If the MAC address is not found. the learning mechanism adds it to the table under the specific service. the frame is forwarded to the service point associated with the MAC address.

the network element host CPU. The MAC forwarding table can be cleared on three levels:  Global Switch Flush – All dynamic entries for all services are erased. 12 The Service Flush option is planned for future release. users can add static MAC addresses for static routing in each service.  Loss of carrier occurs on the interface with which the entry is associated.12  Port Flush – All dynamic entries associated with a specific interface are erased. Management Service (MNG) The management service is a multipoint service that connects the two local management ports. An entry is erased from the table as a result of:  The global aging time expires for the entry. Users can manually clear the dynamic entries from the MAC forwarding table.8032. The system also provides an automatic flush process. and the traffic ports into a single service. The service behavior is same as the Multipoint service behavior.Chapter 5: Feature Description Ethernet Features Table 8 Ethernet Services Learning and Forwarding MAC Forwarding Table Input Key for learning / forwarding (search) operation Result Service ID MAC address Service Point 13 00:34:67:3a:aa:10 15 dynamic 13 00:0a:25:33:22:12 31 dynamic 28 00:0a:25:11:12:55 31 static 55 00:0a:25:33:22:12 15 dynamic 55 00:c3:20:57:14:89 31 dynamic 55 00:0a:25:11:12:55 31 dynamic Entry type In addition to the dynamic learning mechanism.  Service Flush – All dynamic entries for a specific service are flushed. phn-3968 001v000 Page 5-45 . 13 The Port Flush option is planned for future release. 13 Users can also delete static entries per service. These user entries are not considered when determining the maximum size of the MAC forwarding table.  Resiliency protocols. such as MSTP or G.

the user must connect the management service to the network by adding a service point on an interface that provides the required network connectivity. The user must select the Service ID upon creating the service. Users can enable or disable these ports. The CPU service point is read-only and cannot be modified. The following figure illustrates a management service. The first management interface is enabled by default. Service Attributes PTP 820G services have the following attributes: Service ID – A running number from 1 to 1024 that identifies the service. but their service points are not visible to users. Service ID 1025 is used for the pre-defined Management service. They can also be used to manage third-party devices. The second management interface must be manually enabled by the user. as well as E-Line EVCs (EPL and EVPL EVCs) in which only two service points are active. phn-3968 001v000 Page 5-46 . Figure 50 Management Service Management Service Port 1 Port 4 SP SAP SP SAP Port 2 Port 5 SP SAP SP SAP Port 3 Port 6 SP SAP SP SAP Local Management 1 Local Management 2 CPU Management services can provide building blocks for network services such as E-LAN EVCs (EPLAN and EVP-LAN). To configure in-band management over multiple network elements. The pre-defined management service has a single service point that connects the service to the network element host CPU and the two local management interfaces. The management ports can be used to manage the network element or to access a remote network element. The Service ID cannot be edited after the service has been created. Users can modify the attributes of the management service. The local management ports are also connected to the service.Chapter 5: Feature Description Ethernet Features The management service is pre-defined in the system. with Service ID 1025. but cannot delete it.

not static.. PTP 820G supports several types of service points:  Management (MNG) Service Point – Only used for management services. This parameter does not affect the network element’s behavior. In this example. a service is simply a virtual bridge with no ingress or egress interfaces. For example. EVC Description – The Ethernet Virtual Connection description. The service can be a traffic engineering service (instance ID 4095) or can be managed by the xSTP engines of the network element. It is the responsibility of the user not to use all the 131. and one serving as the network gateway.Chapter 5: Feature Description Ethernet Features Service Type – Determines the specific functionality that will be provided for Ethernet traffic using the service.072 entries in the table if the user also wants to utilize dynamic MAC address learning. When the Service Admin Mode is set to Operational. This parameter does not affect the network element’s behavior. see Classification on page 5-62. the service is fully functional. EVC-ID – The Ethernet Virtual Connection ID (end-to-end). each service contains three MNG service points. If the CoS Mode is set to overwrite previous classification decisions. When the Service Admin Mode is set to Reserved. the service occupies system resources but is unable to transmit and receive data. xSTP Instance (0-46. 4095) – The spanning tree instance ID to which the service belongs. The global aging time does not apply to static entries. phn-3968 001v000 Page 5-47 . CoS Mode – Defines whether the service inherits ingress classification decisions made at previous stages or overwrites previous decisions and uses the default CoS defined for the service. with no need to learn a service topology based on source and destination MAC addresses. a Point-to-Point service provides traffic forwarding between two service points. Default CoS – The default CoS value at the service level. and they are not counted with respect to the Maximum Dynamic MAC Address Learning. Static MAC Address Configuration – Users can add static entries to the MAC forwarding table. and only applies to dynamic. able to receive and transmit traffic. but is used by the NMS for topology management. This parameter is configured with a granularity of 16. Service Points Service points are logical entities attached to the interfaces that make up the service. Service Admin Mode – Defines whether or not the service is functional. The following figure shows a management service used for in-band management among four network elements in a ring. two for East-West management connectivity in the ring. A Multipoint service enables operators to create an E-LAN service that includes several service points. this is the CoS value used for frames entering the service. Service points define the movement of frames through the service.e. i. Maximum Dynamic MAC Address Learning per Service – Defines the maximum number of dynamic Ethernet MAC address that the service can learn. MAC addresses. For more details on PTP 820G’s hierarchical classification mechanism. but is used by the NMS for topology management. Without service points.

SNPs are used for Point-to-Point and Multipoint traffic services. An MP Service with three service points provides the connectivity over the network. phn-3968 001v000 Page 5-48 . SAPs are used for Pointto-Point and Multipoint traffic services. The following figure shows four network elements in ring. The SNPs provide the connectivity among the network elements in the user network while the SAPs provide the access points for the network.  Service Network Point (SNP) Service Point – An SNP is equivalent to an NNI or E-NNI in MEF terminology and defines the connection between the network elements in the user network.Chapter 5: Feature Description Ethernet Features Figure 51 Management Service and its Service Points MNG MNG MNG MNG MNG MNG MNG MNG MNG MNG MNG MNG  Service Access Point (SAP) Service Point – An SAP is equivalent to a UNI in MEF terminology and defines the connection of the user network with its access points.

The SNPs are used for interconnection between the network elements while the SAPs provide the access points for the network. all the traffic from one port passes to the other port. to provide connectivity between elements that require port-based connectivity. In other words. A Smart Pipe is also used. Pipe service points are used in Point-to-Point services The following figure shows a Point-to-Point service with Pipe service points that create a Smart Pipe between Port 1 of the network element on the left and Port 2 of the network element on the right. phn-3968 001v000 Page 5-49 .Chapter 5: Feature Description Ethernet Features Figure 52 SAPs and SNPs SAP SNP SNP SNP SNP SAP SAP SNP SNP SNP SNP SAP  Pipe Service Point – Used to create traffic connectivity between two points in a port-based manner (Smart Pipe).Figure 53 Pipe Service Points Pipe Pipe Pipe Pipe The following figure shows the usage of SAP. SNP and PIPE service points in a microwave network.

Chapter 5: Feature Description Ethernet Features Figure 54 SAP. Table 9 Service Point Types per Service Type Service point type Service Type MNG SAP SNP Pipe Point-to-Point Yes No No No Multipoint No Yes Yes Yes phn-3968 001v000 Page 5-50 . SNP and Pipe Service Points in a Microwave Network Fiber Aggregation Network SAP SNP SNP SNP SAP SNP Microwave Network SNP SNP NOC SNP SNP SNP SNP SNP SAP PIPE PIPE SNP SAP SAP Base Station The following table summarizes the service point types available per service type.

 Dot1q – A single C-VLAN is classified to the service point. frames are assigned to the earliest defined service point in case of conflict. service points connect the service to the network element interfaces.  Bundle C-Tag– A set of multiple C-VLANs are classified to the service point. SNP classification SNPs can be used with the following Attached Interface Types:  Dot1q – A single C VLAN is classified to the service point. phn-3968 001v000 Page 5-51 . This classification process is implemented by means of a parsing encapsulation rule for the interface associated with the service point.  The frame’s C-VLAN and/or S-VLAN tags.  Bundle S-Tag – A set of multiple S-VLANs and a set of multiple C VLANs are classified to the service point.  S-Tag – A single S. Since more than one service point may be associated with a single interface. The following table shows which service point types can co-exist on the same interface. MNG classification Management service points can be used with the following Attached Interface Types:  Dot1q – A single C-VLAN is classified to the service point.Chapter 5: Feature Description Ethernet Features Service point type Multipoint MNG SAP SNP Pipe No Yes Yes No Service Point Classification As explained above. and is based on a three part key consisting of:  The Interface ID of the interface through which the frame entered. SAP Classification SAPs can be used with the following Attached Interface Types:  All to one – All C-VLANs and untagged frames that enter the interface are classified to the same service point.  S-Tag – A single S-VLAN is classified to the service point.  QinQ – A single S-VLAN and C-VLAN combination is classified to the service point. This rule is called the Attached Interface Type.  QinQ – A single S-VLAN and C-VLAN combination is classified into the service point.VLAN is classified to the service point. The Attached Interface Type provides a definitive mapping of each arriving frame to a specific service point in a specific service. It is crucial that the network element have a means to classify incoming frames to the proper service point.

Yes Yes Yes SAP SP Yes Yes No No SNP SP Yes No Yes No PIPE SP Yes No No Only one Pipe SP is allowed per interface.1q No No No No No S-Tag No No No No No 802.1q Yes Yes No No No QinQ No No Yes No Yes S-Tag No No No No No SAP SNP Pipe MNG phn-3968 001v000 Page 5-52 .Chapter 5: Feature Description Ethernet Features Table 10 Service Point Types that can Co-Exist on the Same Interface MNG SP SAP SP SNP SP Pipe SP MNG SP Only one MNG SP is allowed per interface.1q Only for P2P Service Only for P2P Service No No No S-Tag No No No No No 802. The following table shows in more detail which service point – Attached Interface Type combinations can co-exist on the same interface Table 11 Attached Interface Type combinations SAP SP Type SP Type SAP Attached Interface Type 802.1q Bundle C-Tag Bundle S-Tag All to One QinQ 802.1q Yes Yes No No No Bundle C-Tag Yes Yes No No No Bundle S-Tag No No Yes No Yes No All to One No No No Only 1 All to One SP Per Interface QinQ No No Yes No Yes 802.

 Egress Attributes – Define how frames are handled upon egress. preservation of the ingress CoS value upon egress..1q QinQ S-Tag 802. The service point attributes are divided into two types:  Ingress Attributes – Define how frames are handled upon ingress.1q Yes No Yes No No No No QinQ No No No No No No No S-Tag No Yes No Yes No No No SNP Pipe MNG MNG Service Point Attributes As described above.1q Yes No Only for P2P Service No Yes No No S-Tag No Yes No Only for P2P Service No No Yes 802..1q Only for P2P Service No Only one Pipe SP Per Interface No Yes No No S-Tag No Only for P2P Service No Only one Pipe SP Per Interface No No Yes 802.g. e.1q S-Tag 802.Chapter 5: Feature Description Ethernet Features Table 12 Attached Interface Type combinations SNP Pipe MNG SP Type SAP SP Type SNP Pipe Attached Interface Type 802.g.1q S-Tag 802. VLAN swapping. policing and MAC address learning. traffic ingresses and egresses the service via service points.1q No No Only for P2P Service No Yes No No Bundle C-Tag No No Only for P2P Service No Yes No No Bundle S-Tag No No No No No Yes No All to One No No No No No No No QinQ No No No No No Yes No 802. phn-3968 001v000 Page 5-53 . e.

 Allow Flooding – Determines whether incoming frames with unknown MAC addresses are forwarded to other service points via flooding. except for management services which are limited to 30 service points in addition to the pre-defined management system service point. as described above. phn-3968 001v000 Page 5-54 . Service Point Type – The type of service point.  Allow Broadcast – Determines whether to allow frames to ingress the service via the service point when the frame has a broadcast destination MAC address. Service Point Name – A descriptive name.Chapter 5: Feature Description Ethernet Features The following figure shows the ingress and egress path relationship on a point-to-point service path.  Learning Administration – Enables or disables MAC address learning for traffic that ingresses via the service point. as described above. Ingress Service Point Attributes The ingress attributes are attributes that operate upon frames when they ingress via the service point. C-VLAN Encapsulation – The C-VLAN ID associated with the service point.  Attached Interface Type – The interface type to which the service point is attached. which can be up to 20 characters.  CoS Mode – Determines whether the service point preserves the CoS decision made at the interface level. When traffic arrives via port 1. S-VLAN Encapsulation – The S-VLAN ID associated with the service point. this attribute is used to create a list of C-VLANs associated with the service point. Attached C VLAN – For service points with an Attached Interface Type of Bundle C-Tag. This option enables users to enable or disable MAC address learning for specific service points. Permitted values depend on the service point type. the system handles it using service point 1 ingress attributes then forwards it to service point 2 and handles it using the SP2 egress attributes: Figure 55 Service Path Relationship on Point-to-Point Service Path SP1 SP2 Ingress Ingress Port 1 Port 2 Egress Egress Service points have the following attributes: General Service Point Attributes Service Point ID – Users can define up to 32 service points per service. overwrites the CoS with the default CoS for the service point. this attribute is used to create a list of S-VLANs associated with the service point. Attached S-VLAN – For service points with an Attached Interface Type of Bundle S-Tag.

Ethernet Interfaces The PTP 820G switching fabric distinguishes between physical interfaces and logical interfaces. this is the CoS value assigned to frames that ingress the service point.  Service Bundle ID – This attribute can be used to assign one of the available service bundles from the H-QoS hierarchy queues to the service point. Users can define a rate meter for each of the eight CoS values of the service point. marking is performed according to global mapping tables that map the 802. C-VLAN frames egressing the service point retain the same C-VLAN ID they had when they entered the service. For details. or the outer frame is C-VLAN and C-VLAN CoS preservation is disabled. If marking is enabled. the C-VLAN CoS value of frames egressing the service point is the same as the value when the frame entered the service. Permitted values are 1– 250. auto-negotiation. 14 This feature is planned for future release.  C-VLAN CoS Egress Preservation – If enabled.  Marking – Marking refers to the ability to overwrite the outgoing priority bits and Color of the outer VLAN of the egress frame. When marking is enabled and active. 16 This feature is planned for future release. This enables users to personalize the QoS egress path.  Token Bucket Profile – This attribute can be used to attach a rate meter profile to the service point.1p-UP bits and the DEI or CFI bit to a defined CoS and Color value. 14  CoS Token Bucket Profile – This attribute can be used to attach a rate meter profile to the service point at the CoS level.16 Egress Service Point Attributes The egress attributes are attributes that operate upon frames egressing via the service point. either the C-VLAN or the S-VLAN.15  CoS Token Bucket Admin – Enables or disables the rate meter at the service point CoS level. master/slave.Chapter 5: Feature Description Ethernet Features  Default CoS – The service point CoS. 15 This feature is planned for future release. duplex. such as speed.  C-VLAN ID Egress Preservation – If enabled. the service point overwrites the outgoing priority bits and Color of the outer VLAN of the egress frame. If the CoS Mode is set to overwrite the CoS decision made at the interface level. the S-VLAN CoS value of frames egressing the service point is the same as the value when the frame entered the service. phn-3968 001v000 Page 5-55 . and standard RMON statistics. The concept of a physical interface refers to the physical characteristics of the interface. Permitted values are 1-250 for CoS 0–7.  S-VLAN CoS egress Preservation – If enabled. Physical and logical interfaces serve different purposes in the switching fabric. see Standard QoS and Hierarchical QoS (H-QoS) on page 5-75. Marking mode is only relevant if either the outer frame is S-VLAN and S-VLAN CoS preservation is disabled.

. The following figure shows physical and logical interfaces in a one-to-one relationship in which each physical interface is connected to a single logical interface. On the group level. When physical interfaces are grouped into a logical interface. Figure 56 Physical and Logical Interfaces Physical Interface 1 Logical Interface Physical Interface 2 Logical Interface SP SP SP Service SP Logical Interface Logical Interface Physical Interface 3 Physical Interface 4 Note For simplicity only.e. or Radio. the user might limit the group to a rate of 200 mbps by configuring the rate meter on the logical interface level. the physical level and the logical level. rather than having to examine the statistics for each interface individually. both the physical and the logical radio interface come into being at the same time. Examples of the latter are protection groups and link aggregation groups. i. RJ-45. the user configures both the physical and the logical interface. This information enables users to determine the cumulative statistics for the group. when the user enables a radio interface. PTP 820G also shows standard RMON statistics for the logical interface. phn-3968 001v000 Page 5-56 . the creation of the logical interface is simultaneous with the creation of the physical interface. Switching and QoS functionality are implemented on the logical interface level. For example. SFP. The user configures each physical interface separately. this figure represents a uni-directional rather than a bi-directional traffic flow. In other words.g. It is important to understand that the PTP 820G switching fabric regards all traffic interfaces as regular physical interfaces. full duplex. for the group. with auto-negotiation off. and configures the logical interface as a single logical entity.Chapter 5: Feature Description Ethernet Features A logical interface can consist of a single physical interface or a group of physical interfaces that share the same function. e.. From the user’s point of view. the user might configure each physical interface to 100 mbps. distinguished only by the media type the interface uses. The next figure illustrates the grouping of two or more physical interfaces into a logical interface. For example. without grouping. a link aggregation group (LAG) in this example. Once the interface is created. The two physical interfaces on the ingress side send traffic into a single logical interface. the user configures the same interface on two levels.

The Media Type attribute defines the Layer 1 physical traffic interface type. which can be:  Radio interface.  RJ-45 or SFP for an Ethernet interface. this figure represents a uni-directional rather than a bi-directional traffic flow. such as scheduling. In this case. this figure represents a uni-directional rather than a bi-directional traffic flow.Chapter 5: Feature Description Ethernet Features Figure 57 Grouped Interfaces as a Single Logical Interface on Ingress Side Physical Interface 1 LAG Logic ce terfa al In SP SP Logical Interface Physical Interface 3 Physical Interface 2 SP Service SP Logical Interface Physical Interface 4 Note For simplicity only. Figure 58 Grouped Interfaces as a Single Logical Interface on Egress Side Physical Interface 1 Logical Interface SP SP Lo gic al I nte Physical Interface 3 rfa ce LAG Physical Interface 2 Logical Interface SP Physical Interface 4 Service SP Note For simplicity only. The following figure shows the logical interface at the egress side. phn-3968 001v000 Page 5-57 . the user can configure the egress traffic characteristics. for the group as a whole as part of the logical interface attributes.  TDM for a DS1 interface. Physical Interfaces The physical interfaces refer to the real traffic ports (layer 1) that are connected to the network.

Permitted values are: o Ethernet RJ-45 interfaces: 10Mbps HD.  Actual Flow Control State – The actual flow control state values for the Ethernet link as agreed by the two sides after the auto negotiation process.  Actual Speed and Duplex – The actual speed and duplex value for the Ethernet link as agreed by the two sides of the link after the auto negotiation process. SFP. 100Mbps HD. The following transmit statistic counters are available:  17 Transmitted bytes (not including preamble) in good or bad frames.  Interface description – A text description of the interface.  Speed and Duplex – The physical interface speed and duplex mode. o Ethernet SFP interfaces: Only 1000FD is supported o Radio and TDM interfaces: The parameter is read-only and set by the system to 1000FD.  Preamble – The physical port preamble value. it is strongly recommended not to modify the default values of 8 bytes without a thorough understanding of how the modification will impact traffic. This functionality is planned for future release. Permitted values are: Symmetrical Pause and/or Asymmetrical Pause. Low 32 bits. and 1000Mpbs FD. This parameter is only relevant in Full Duplex mode. When Auto Detect is selected.  Actual Physical Mode (only relevant for RJ-45 interfaces) – The actual physical mode (master or slave) for the Ethernet link. up to 40 characters. Although users can modify the IFG field length.  IFG – The physical port Inter-frame gap. This attribute is set via the Interface Manager section of the Web EMS. The following read-only physical interface status parameters can be viewed by users:  Operational State – The operational state of the physical interface (Up or Down). and SFP. and TDM interfaces. Permitted values are Auto Detect.Chapter 5: Feature Description Ethernet Features Physical Interface Attributes The following physical interface parameters can be configured by users:  Admin – Enables or disables the physical interface. Ethernet Statistics (RMON) The PTP PTP 820G platform stores and displays statistics in accordance with RMON and RMON2 standards. Although users can modify the preamble field length. 10Mbps FD.  Auto Negotiation – Enables or disables auto-negotiation on the physical interface. as agreed by the two sides after the auto negotiation process. Auto Detect can only be used when the interface speed is set to 1000 Mbps. This attribute is only relevant for Ethernet traffic ports (RJ-45 or SFP). 100Mbps FD. Auto Negotiation is always off for radio. 17  Media Type – The physical interface Layer 1 media type.  Flow Control – The physical port flow control capability. the system detects whether the optical or electrical port is being used. Permitted values are 6 to 15 bytes. Permitted values are 6 to 15 bytes. RJ-45. phn-3968 001v000 Page 5-58 . it is strongly recommended not to modify the default value of 12 bytes without a thorough understanding of how the modification will impact traffic.

good or bad  Frames with length 512-1023 bytes. good or bad. good or bad  Frames with length 256-511 bytes.  Transmitted frames (good or bad)  Multicast frames (good only)  Broadcast frames (good only)  Control frames transmitted  Pause control frame transmitted  FCS error frames  Frame length error  Oversized frames – frames with length > 1518 bytes (1522 bytes for VLAN-tagged frames) without errors  Undersized frames (good only)  Fragments frames (undersized bad)  Jabber frames – frames with length > 1518 bytes (1522 for VLAN-tagged frames) with errors  Frames with length 64 bytes.Chapter 5: Feature Description Ethernet Features  Transmitted bytes (not including preamble) in good or bad frames. good or bad  Frames with length 65-127 bytes. Low 32 bits.  Frames with length 1024-1518 bytes. good or bad phn-3968 001v000 Page 5-59 . High 32 bits.  Received frames (good or bad)  Multicast frames (good only)  Broadcast frames (good only)  Control frames received  Pause control frame received  FCS error frames  Frame length error  Code error  Counts oversized frames – frames with length > 1518 bytes (1522 bytes for VLAN-tagged frames) without errors and frames with length > MAX_LEN without errors  Undersized frames (good only)  Fragments frames (undersized bad)  Counts jabber frames – frames with length > 1518 bytes (1522 for VLAN-tagged frames) with errors  Frames with length 64 bytes. good or bad  Frames with length 1519-1522 bytes. High 32 bits.  Received bytes (not including preamble) in good or bad frames. good or bad The following receive statistic counters are available:  Received bytes (not including preamble) in good or bad frames. good or bad  Frames with length 128-255 bytes.

good or bad  Frames with length > MAX_LEN without errors  Frames with length > MAX_LEN with errors Logical Interfaces A logical interface consists of one or more physical interfaces that share the same traffic ingress and egress characteristics. QoS. The user configures and manages the logical interface just as if it represented a single 1+0 radio. It is important to understand that the user relates to logical interfaces in the same way in both a one-to-one scenario in which a single physical interface corresponds to a single logical interface.Chapter 5: Feature Description Ethernet Features  Frames with length 65-127 bytes. and resiliency attributes are configured and implemented on the logical interface level. in contrast to attributes such as interface speed and duplex mode. and a grouping scenario such as a link aggregation group or a radio protection group. good or bad  Frames with length 128-255 bytes. in which several physical interfaces correspond to a single logical interface. good or bad  Frames with length 1024-1518 bytes. From the point of view of the user configuring the logical interface attributes. classification. Figure 59 Relationship of Logical Interfaces to the Switching Fabric SP SP Radio Interface 1 Physical Interface 3 Physical Interface 1 Radio Protection Group 1 HSB Radio Interface 2 Logical Interface Physical Interface 2 SP Service SP Logical Interface Logical Interface Attributes The following logical interface attributes can be configured by users: phn-3968 001v000 Page 5-60 Physical Interface 4 . The following figure illustrates the relationship of a 1+1 HSB radio protection group to the switching fabric. good or bad  VLAN-tagged frames with length 1519-1522 bytes. the fact that there are two radios is not relevant. good or bad  Frames with length 256-511 bytes. good or bad  Frames with length 512-1023 bytes. Therefore. it is more convenient to define interface behavior for the group as a whole than for each individual physical interface that makes up the group. which are configured on the physical interface level. From the user’s point of view.

 Multicast Traffic Rate Meter Admin – Enables or disables the multicast rate meter (policer) on the logical interface. phn-3968 001v000 Page 5-61 . Ingress Path Classification at Logical Interface Level These attributes represent part of the hierarchical classification mechanism.1AD UP bit (S-VLAN frames) to CoS and Color classification.1p and DSCP classification have priority over MPLS Trust Mode. and overwrites any other classification criteria at the logical interface level. the interface performs QoS and Color classification according to user-configurable tables for 802.  IP DSCP Trust Mode –When this attribute is set to Trust mode and the arriving packet has IP priority bits.Chapter 5: Feature Description Ethernet Features General Attributes  Traffic Flow Administration – Enables traffic via the logical interface. so that if a match is found on either the 802. The user can enable or disable traffic to the group using this parameter.1q UP bit (C-VLAN frames) or 802. The Color is assumed to be Green.  MPLS Trust Mode – When this attribute is set to Trust mode and the arriving packet has MPLS EXP priority bits. the match must be with the frame’s outer VLAN.  802. This value can be overwritten on the service point and service level. in which the logical interface is the lowest point in the hierarchy. see Logical Interface-Level Classification on page 5-63. so that if a match is found on the 802.1AD. the interface performs QoS and Color classification according to a userconfigurable DSCP bit to CoS and Color classification table.1Q or 802. Permitted values are CoS 0 to 7 and Color Green or Yellow per VLAN ID.1p or DSCP levels.1p Trust Mode – When this attribute is set to Trust mode and the arriving packet is 802. the interface performs QoS and Color classification according to a userconfigurable MPLS EXP bit to CoS and Color classification table. In the case of double-tagged frames. DSCP bits are not considered.1p level.  Unicast Traffic Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile. This attribute is useful when the user groups several physical interfaces into a single logical interface.  Multicast Traffic Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile. Both 802.  VLAN ID – Users can specify a specific CoS and Color for a specific VLAN ID. For more information about classification at the logical interface level. Ingress Path Rate Meters at Logical Interface Level  Unicast Traffic Rate Meter Admin – Enables or disables the unicast rate meter (policer) on the logical interface.  Default CoS – The default CoS value for frames passing through the interface.  Broadcast Traffic Rate Meter Admin – Enables or disables the broadcast rate meter (policer) on the logical interface. MPLS bits are not considered.1p classification has priority over DSCP Trust Mode. This is the highest classification priority on the logical interface level. 802.

ARP). This attribute is reserved for future use. The field length is 4 nibbles (for example.  Ethertype 2 Value – The Ethertype value to which the user wants to apply the rate meter (policer). Any shaper attached to this interface. 18 phn-3968 001v000 Page 5-62 .18  Outline Compensation – The logical interface’s egress compensation value.Chapter 5: Feature Description Ethernet Features  Broadcast Traffic Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile. in any layer. The default value is 0 bytes. 0x0806 . The shaper on the interface level stops traffic from the interface if a specific user-defined peak information rate (PIR) has been exceeded. uses this value to compensate for Layer 1 non-effective traffic bytes.  Ethertype 3 Rate Meter Admin – Enables or disables the Ethertype 3 rate meter (policer) on the logical interface. The field length is 4 nibbles (for example.  Ethertype 2 Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile.  Ethertype 1 Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile.ARP). The field length is 4 nibbles (for example.  Inline Compensation – The logical interface’s ingress compensation value. Egress Path Scheduler at Logical Interface Level Logical Interface Priority Profile – This attribute is used to attach an egress scheduling priority profile to the logical interface.  Ethertype 1 Value – The Ethertype value to which the user wants to apply this rate meter (policer). which provides the equivalent of shaping per logical interface.  Ethertype 3 Value – The Ethertype value to which the user wants to apply the rate meter (policer).  Ethertype 3 Rate Meter Profile – Associates the rate meter (policer) with a specific rate meter (policer) profile.ARP). The current release supports traffic shaping per queue and per service bundle. 0x0806 . Permitted values are even numbers between 0 and 26 bytes. 0x0806 . Egress Path Shapers at Logical Interface Level  Logical Port Shaper Profile – Users can assign a single leaky bucket shaper to each interface. The rate meter (policer) attached to the logical interface uses this value to compensate for Layer 1 noneffective traffic bytes.  Ethertype 1 Rate Meter Admin – Enables or disables the Ethertype 1 rate meter (policer) on the logical interface.  Ethertype 2 Rate Meter Admin – Enables or disables the Ethertype 2 rate meter (policer) on the logical interface.

Traffic sent to the interfaces in a LAG group is distributed by means of a load balancing function. PTP 820G uses a distribution function of up to Layer 4 in order to generate the most efficient distribution among the LAG physical ports. Link Aggregation Groups (LAG) Link aggregation (LAG) enables users to group several physical interfaces into a single logical interface bound to a single MAC address. if the logical interface represents a group. The WFQ profile provides a means of allocating traffic among queues with the same priority. Logical Interface Statistics RMON Statistics at Logical Interface Level As discussed in Ethernet Statistics (RMON) on page 5-54. The following read-only logical interface status parameters can be viewed by users:  Traffic Flow Operational Status – Indicates whether or not the logical interface is currently functional.Chapter 5: Feature Description Ethernet Features Logical Port WFQ Profile – This attribute is used to attach an egress scheduling WFQ profile to the logical interface. taking into account:  MAC DA and MAC SA  IP DA and IP SA  C-VLAN  S-VLAN  Layer 3 Protocol Field  UDP/TCP Source Port and Destination Port  MPLS Label phn-3968 001v000 Page 5-63 . users can view the following statistics counters:  Green Frames  Green Bytes  Yellow Frames  Yellow Bytes  Red Frames  Red Bytes Note Rate meter (policer) counters are 64 bits wide. This logical interface is known as a LAG group. Rate Meter (Policer) Statistics at Logical Interface Level For the rate meter (policer) at the logical interface level. such as a LAG or a 1+1 HSB pair. the PTP 820G platform stores and displays RMON and RMON2 statistics for the logical interface.

PTP 820G enables users to select the LAG members without limitations. such as traffic congestion. streams from two different ports that egress via single port. The figure below shows the basic flow of PTP 820G’s QoS mechanism. Quality of Service (QoS) Related topics:  Ethernet Service Model  In-Band Management Quality of Service (QoS) deals with the way frames are handled within the switching fabric. the system determines how to route the traffic. the removed interface is assigned the default interface values. packet availability. For example.Chapter 5: Feature Description Ethernet Features LAG can be used to provide redundancy for Ethernet (line protection). such as interface speed and interface type. on the “ingress path. and delay restrictions. These can include. or a port-to-port connection that holds hundreds of services. can belong to a LAG group.  When removing an interface from a LAG group.” phn-3968 001v000 Page 5-64 . In each topology. not logical interfaces. LAG can be used to create a 4 Gbps channel. a customized approach to handling QoS will provide the best results. QoS is required in order to deal with many different network scenarios. LAG can also be used to aggregate several interfaces in order to create a wider (aggregate) Ethernet link.  Interfaces can only be added to the LAG group if no services or service points are attached to the interface.  Any classification rules defined for the interface are overridden by the classification rules defined for the LAG group. Proper configuration of a LAG group is the responsibility of the user. Traffic ingresses (left to right) via the Ethernet or radio interfaces. PTP 820G’s smart QoS mechanism operates from the frame’s ingress into the switching fabric until the moment the frame egresses via the destination port. Up to four LAG groups can be created. Traffic is then directed to the most appropriate output queue via the “egress path. for example. LAG groups can include interfaces with the following constraints:  Only physical interfaces (including radio interfaces). QoS capability is very important due to the diverse topologies that exist in today’s network scenarios. PTP 820G’s personalized QoS enables operators to handle a wide and diverse range of scenarios.” Based on the services model.

The classifier determines the exact traffic stream and associates it with the appropriate service. It also calculates an ingress frame CoS and Color. from a total 2K queues. and eligibility to transmit based on required shaping on several different levels (per queue. CoS and Color classification can be performed on three levels. therefore providing a true SLA to customers. The following two modes of operation are available on the egress path:  Standard QoS – This mode provides eight transmission queues per port. Weighted Fair Queuing (WFQ) in bytes per each transmission queue.  Scheduling and Shaping – A hierarchical mechanism that is responsible for scheduling the transmission of frames from the transmission queues. and service point CoS. service point. In H-QoS mode. and to determine whether to modify the color calculated during the classification stage. service point. The rate metering mechanism enables the system to measure the incoming frame rate on different levels using a TrTCM standard MEF rate meter. according to the user’s configuration. utilizing smart WRED per queue and per packet color (Green or Yellow).  Marker – This mechanism provides the ability to modify priority bits in frames based on the calculated CoS and Color. and per port). The egress path consists of the following QoS building blocks:  Queue Manager – This is the mechanism responsible for managing the transmission queues. and specific queues.  Hierarchical QoS (H-QoS) – In this mode. users can associate services from the service model to configurable groups of eight transmission queues (service bundles). based on priority among queues. PTP 820G performs QoS in a hierarchical manner in which the egress path is managed on three levels: ports. and service. service bundles.  Ingress Rate Metering – A hierarchical mechanism that deals with ingress traffic on three different levels: interface. This enables users to fully distinguish between streams.Chapter 5: Feature Description Ethernet Features Figure 60 QoS Block Diagram Egress Ingress GE/Radio Port Marker (Optional) Rate Limit (Policing) Classifier Queue Manager (Optional) Scheduler/ Shaper Port GE/Radio Standard QoS/ H-QoS Egress Ingress GE/Radio Port Marker (Optional) Rate Limit (Policing) Classifier Queue Manager (Optional) Scheduler/ Shaper Port GE/Radio Port GE/Radio Standard QoS/ H-QoS Ingress GE/Radio Port Classifier Rate Limit (Policing) (Optional) Egress CET/Pipe Services Marker (Optional) Queue Manager Scheduler/ Shaper Standard QoS/ H-QoS The ingress path consists of the following QoS building blocks:  Ingress Classifier – A hierarchical mechanism that deals with ingress traffic on three different levels: interface. phn-3968 001v000 Page 5-65 . per service bundle.

In this figure. The nature of each traffic stream defines which level of the hierarchical classifier to apply. The classification mechanism examines incoming frames and determines their CoS and Color. traffic S S Ethernet Radio Streaming S Service 3 H-QoS V D Service 1 Service 1 S V D Service 2 S Service 2 Ethernet Radio V Service 3 D Service 3 S QoS on the Ingress Path Classification PTP 820G supports a hierarchical classification mechanism. the service point level.Chapter 5: Feature Description Ethernet Features The following figure illustrates the difference between how standard QoS and H-QoS handle traffic: Figure 61 Standard QoS and H-QoS Comparison Standard QoS V Service 1 V Service 2 Voice D D V D Data Eth. The hierarchical classifier consists of the following levels:  Logical interface-level classification  Service point-level classification  Service level classification The following figure illustrates the hierarchical classification model. traffic enters the system via the port depicted on the left and enters the service via the SAP depicted on the upper left of the service. enabling classification at higher or lower levels of the hierarchy. The benefit of hierarchical classification is that it provides the ability to “zoom in” or “zoom out”. The classification can take place at the logical interface level. phn-3968 001v000 Page 5-66 . or whether to use several levels of the classification hierarchy in parallel. and/or the service level.

For example. This is useful. If no match is found at the logical interface level.1p classification is configured as un-trusted for a specific interface. For example. the default CoS is applied to incoming frames at this level. a match will not be found until the third priority level (DSCP priority bits). such as a LAG group. from highest (on the left) to lowest (on the right) priority. the Color of the frame is assumed to be Green. In this case. if the required classification is based on DSCP priority bits. the classification mechanism does not perform classification by VLAN UP bits. listed from highest to lowest priority.  DSCP bits. The CoS and Color values defined for the frame’s DSCP priority bits will be applied to the frame. if 802. Once a match is found.  Default CoS PTP 820G performs the classification on each frame ingressing the system via the logical interface. for example. The classifier at the logical interface level supports the following classification methods.1p-based CoS  DSCP-based CoS  MPLS EXP-based CoS  Default CoS SAP Service SNP SNP SAP Logical Interface-Level Classification Logical interface-level classification enables users to configure classification on a single interface or on a number of interfaces grouped tougher. phn-3968 001v000 Page 5-67 . The following figure illustrates the hierarchy of priorities among classification methods. Users can disable some of these classification methods by configuring them as un-trusted.  MPLS EXP field.Chapter 5: Feature Description Ethernet Features Figure 62 Hierarchical Classification Service point level  Preserve previous decision  Default CoS Port Logical Interface SNP SAP SAP Service level  Default CoS  Preserve Service Point Decision Logical interface level  VLAN ID  802.1p bits. Classification is performed step by step from the highest priority to the lowest priority classification method. the classifier determines the CoS and Color decision for the frame for the logical interface-level. A higher level classification method supersedes a lower level classification method:  VLAN ID  802. if the frame is an untagged IP Ethernet frame.

Table 13 C-VLAN 802. IP. For details. while the key results are the CoS and Colors calculated for incoming frames. These results are user-configurable. and MPLS). see Ingress Path Classification at Logical Interface Level on page 5-57. The following tables show the default values for logical interface-level classification. The key values for these tables are the priority bits of the respective frame encapsulation layers (VLAN.1p DSCP MPLS EXP Default CoS Lowest Priority Interface-level classification is configured as part of the logical interface configuration.1 UP and CFI Default Mapping to CoS and Color 802.Chapter 5: Feature Description Ethernet Features Figure 63 Classification Method Priorities Highest Priority VLAN ID 802.1 UP CFI CoS (configurable) Color (configurable) 0 0 0 Green 0 1 0 Yellow 1 0 1 Green 1 1 1 Yellow 2 0 2 Green 2 1 2 Yellow 3 0 3 Green 3 1 3 Yellow 4 0 4 Green 4 1 4 Yellow 5 0 5 Green 5 1 5 Yellow 6 0 6 Green 6 1 6 Yellow 7 0 7 Green 7 1 7 Yellow phn-3968 001v000 Page 5-68 . but it is recommended that only advanced users should modify the default values.

Chapter 5: Feature Description Ethernet Features Table 14 S-VLAN 802.1 UP DEI CoS (Configurable) Color (Configurable) 0 0 0 Green 0 1 0 Yellow 1 0 1 Green 1 1 1 Yellow 2 0 2 Green 2 1 2 Yellow 3 0 3 Green 3 1 3 Yellow 4 0 4 Green 4 1 4 Yellow 5 0 5 Green 5 1 5 Yellow 6 0 6 Green 6 1 6 Yellow 7 0 7 Green 7 1 7 Yellow Table 15 DSCP Default Mapping to CoS and Color DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable) 0 (default) 000000 BE (CS0) 0 Green 10 001010 AF11 1 Green 12 001100 AF12 1 Yellow 14 001110 AF13 1 Yellow 18 010010 AF21 2 Green 20 010100 AF22 2 Yellow 22 010110 AF23 2 Yellow 26 011010 AF31 3 Green 28 011100 AF32 3 Yellow 30 011110 AF33 3 Yellow phn-3968 001v000 Page 5-69 .1 UP and DEI Default Mapping to CoS and Color 802.

Users can configure these modes by means of the service point CoS mode.Chapter 5: Feature Description Ethernet Features DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable) 34 100010 AF41 4 Green 36 100100 AF42 4 Yellow 38 100110 AF43 4 Yellow 46 101110 EF 7 Green 8 001000 CS1 1 Green 16 010000 CS2 2 Green 24 011000 CS3 3 Green 32 100000 CS4 4 Green 40 101000 CS5 5 Green 48 110000 CS6 6 Green 56 111000 CS7 7 Green Default value is CoS equal best effort and Color equal Green.  Preserve previous CoS decision (logical interface level)  Default service point CoS phn-3968 001v000 Page 5-70 . in higher resolution. The following classification modes are supported at the service point level. to specific traffic flows using a single interface to which the service point is attached. Table 16 MPLS EXP Default Mapping to CoS and Color MPLS EXP bits CoS (configurable) Color (configurable) 0 0 Yellow 1 1 Green 2 2 Yellow 3 3 Green 4 4 Yellow 5 5 Green 6 6 Green 7 7 Green Service Point-Level Classification Classification at the service point level enables users to give special treatment.

and the Color is Green. and is based on a dual leaky bucket mechanism. The PTP 820G hierarchical rate metering mechanism is part of the QoS performed on the ingress path. Service-Level Classification Classification at the service level enables users to provide special treatment to an entire service. Rate Meter (Policing) PTP 820G’s TrTCM rate meter mechanism complies with MEF 10. the CoS is taken from the service point’s default CoS.Chapter 5: Feature Description Ethernet Features If the service point CoS mode is configured to preserve previous CoS decision. the user might decide that all frames in a management service should be assigned a specific CoS regardless of the ingress port. Hierarchical rate metering enables users to define rate meter policing for incoming traffic at any resolution point. from the interface level to the service point level. the CoS and Color are taken from the classification decision at the logical interface level. frames passing through the service are given the CoS and Color that was assigned at the service point level. 19 Service point-level rate metering is planned for future release. The TrTCM rate meter can change a frame’s CoS settings based on CIR/EIR+CBS/EBS. If the service point CoS mode is configured to default service point CoS mode. To prevent this. which makes the rate meter mechanism a key tool for implementing bandwidth profiles and enabling operators to meet strict SLA requirements. the rate meter can cut off traffic from a user that passes the expected ingress rate. 20 Service point and CoS-level rate metering is planned for future release. The following classification modes are supported at the service level:  Preserve previous CoS decision (service point level)  Default CoS If the service CoS mode is configured to preserve previous CoS decision. and PTP 820G’s QoS implementation provides the granularity necessary to implement service-oriented solutions. and the Color is Green. For example. and consists of the following levels:  Logical interface-level rate meter  Service point-level rate meter19  Service point CoS-level rate meter20 MEF 10. and even at the level of a specific CoS within a specific service point.2 is the de-facto standard for SLA definitions. Another important function of rate metering is to protect resources in the network element from malicious users sending traffic at an unexpectedly high rate.2. This option enables users to customize a set of eight policers for a variety of traffic flows within a single service point in a service. the CoS is taken from the service’s default CoS. phn-3968 001v000 Page 5-71 . If the service CoS mode is configured to default CoS mode.

or Red. Color Mode (CM). The following parameters can be defined for each profile:  Committed Information Rate (CIR) – Frames within the defined CIR are marked Green and passed through the QoS module. Users must create the profile first. Ingress rate meters operate at three levels:  Logical Interface: o Per frame type (unicast. or service point + CoS. Yellow. The CIR defines the average rate in bits/s of Service Frames up to which the network delivers service frames and meets the performance objectives. and Coupling flag (CF). based on CIR/EIR. Frames that exceed the CIR rate are marked Yellow. Global Rate Meter Profiles Users can define up to 250 rate meter user profiles. with a minimum granularity of 32Kbps. and broadcast) o Per frame ethertype  Per Service Point  Per Service Point CoS Figure 64 Ingress Policing Model CoS 1 CoS 2 Service Point Ethertype Frame Type CoS 3 At each level (logical interface. Permitted values are 0 to 1 Gbps. Frames within the Excess Information Rate (EIR) or Excess Burst Size (EBS) are marked Yellow. service point. service point. without being sent any further. Frames within the Committed Information Rate (CIR) or Committed Burst Size (CBS) are marked Green.Chapter 5: Feature Description Ethernet Features TrTCM rate meters use a leaky bucket mechanism to determine whether frames are marked Green. CBS/EBS. phn-3968 001v000 Page 5-72 . multicast. The rate meters implement a bandwidth profile. and service point + CoS). then attach it to the interface. Up to 250 different profiles can be configured. Frames that do not fall within the CIR/CBS+EIR/EBS are marked Red and dropped. PTP 820G provides up to 1120 user-defined TrTCM rate meters. users can attach and activate a rate meter profile.

Rate Metering (Policing) at the Logical Interface Level Rate metering at the logical interface level supports the following:  Unicast rate meter  Multicast rate meter  Broadcast rate mete  User defined Ethertype 1 rate meter  User defined Ethertype 2 rate meter  User defined Ethertype 3 rate meter For each rate meter.  Excess Burst Size (EBS) – Frames within the defined EBS are marked Yellow and processed according to network availability. When Line Compensation is 20. Permitted values are 2 to 128 Kbytes. Layer 1 capacity is equal to Layer 2 capacity plus 20 additional bytes for each frame due to the preamble and Inter Frame Gap (IFG). the physical level. This limits the maximum number of bytes available for a burst of service frames in order to ensure that traffic conforms to the CIR. nor specifically a rate meter parameter.  Color Mode – Color mode can be enabled (Color aware) or disabled (Color blind). all ingress frames are treated first as Green frames regardless of CFI/DEI value. with a minimum granularity of 2 Kbytes. but ~986 Mbps if the frame size is 1500 bytes. see Logical Interfaces on page 5-56.Chapter 5: Feature Description Ethernet Features  Committed Burst Size (CBS) – Frames within the defined CBS are marked Green and passed through the QoS module.  Line Compensation – A rate meter can measure CIR and EIR at Layer 1 or Layer 2 rates. the rate meter operates as Layer 1. Permitted values are 0 to 1 Gbps. This parameter is very important to users that want to distinguish between Layer 1 and Layer 2 traffic. Line compensation defines the number of bytes to be added to each frame for purposes of CIR and EIR calculation. The following parameter is neither a profile parameter. Permitted values are 2 to 128 Kbytes. This demonstrates that counting at Layer 2 is not always fair in comparison to counting at Layer 1. the preamble and IFG equals 20 bytes. In Color blind mode. In Color aware mode. even if credits remain in the CIR bucket. Frames beyond the combined CBS and EBS are marked Red and dropped by the policer. 1 Gbps of traffic at Layer 1 is equal to ~760 Mbps if the frame size is 64 bytes.  Excess Information Rate (EIR) – Frames within the defined EIR are marked Yellow and processed according to network availability. then if the Green bucket reaches the maximum CBS value the remaining credits are sent to the Yellow bucket up to the maximum value of the Yellow bucket. but rather. is a logical interface parameter. Frames beyond the combined CIR and EIR are marked Red and dropped by the policer. In most cases. that is.  Coupling Flag – If the coupling flag between the Green and Yellow buckets is enabled. the rate meter operates as Layer 2. with a minimum granularity of 32 Kbps. then as Yellow frames (when there is no credit in the Green bucket). For example. For more information about logical interfaces. When Line Compensation is 0. A Color-blind policer discards any previous Color decisions. with a minimum granularity of 2 Kbytes. but other values are also possible. all frames that ingress with a CFI/DEI field set to 1 (Yellow) are treated as EIR frames. the following statistics are available: phn-3968 001v000 Page 5-73 .

The following considerations should be taken into account in determining the proper buffer size:  Latency considerations – If low latency is required (users would rather drop frames in the queue than increase latency) small buffer sizes are preferable. Users can specify the buffer size of each queue independently. up to a total number of 1024 rate meters per network element at the service point and CoS per service point levels. up to a total number of 1024 rate meters per network element at the service point and CoS per service point levels.Chapter 5: Feature Description  Green Frames (64 bits)  Green Bytes (64 bits)  Yellow Frames (64 bits)  Yellow Bytes (64 bits)  Red Frames (64 bits)  Red Bytes (64 bits) Ethernet Features Rate Metering (Policing) at the Service Point Level Users can define a single rate meter on each service point. phn-3968 001v000 Page 5-74 . PTP 820G supports up to 2K service-level transmission queues. The total amount of memory dedicated to the queue buffers is 2 Gbits. The following statistics are available for each service point + CoS rate meter:  Green Frames (64 bits)  Green Bytes (64 bits)  Yellow Frames (64 bits)  Yellow Bytes (64 bits)  Red Frames (64 bits)  Red Bytes (64 bits) QoS on the Egress Path Queue Manager The queue manager (QM) is responsible for managing the output transmission queues. The following statistics are available for each service point rate meter:  Green Frames (64 bits)  Green Bytes (64 bits)  Yellow Frames (64 bits)  Yellow Bytes (64 bits)  Red Frames (64 bits)  Red Bytes (64 bits) Rate Metering (Policing) at the Service Point + CoS Level Users can define a single rate meter for each CoS on a specific service point. with configurable buffer size.

if the calculated CoS is 6. from 0 to 7. The following figure depicts the queue manager. it is recommended to increase the buffer sizes to prevent packet loss. the traffic is sent to queue 6. For example. traffic is passing from left to right. After the traffic is tunneled from the ingress service points to the egress service points. Figure 65 PTP 820G Queue Manager Traffic Flow CoS0 CoS1 SP1 CoS2 SP3 CoS3 CoS4 Multipoint Service Service Bundle 1 (8 Queues) CoS5 CoS6 SP2 SP7 CoS7 CoS0 SP2 Multipoint Service CoS1 SP3 CoS2 CoS3 SP1 SP5 SP7 CoS4 WRED SP6 Service Bundle 2 (8 Queues) CoS5 CoS6 CoS7 CoS0 SP1 Multipoint Service Drop Ratio (%) SP3 CoS1 Queue Occupancy (KB) CoS2 CoS3 CoS4 Service Bundle 3 (8 Queues) CoS5 SP2 CoS6 CoS7 Point to Point Service SP1 SP2 CoS0 CoS1 CoS2 CoS3 SP1 CoS4 Service Bundle 32 (8 Queues) CoS5 Multipoint Service CoS6 SP3 CoS7 SP2 In the figure above. As part of the assignment of the service points to the interfaces. according the application requirements.Chapter 5: Feature Description  Ethernet Features Throughput immunity to fast bursts – When traffic is characterized by fast bursts. the queue manager is located between the ingress path and the egress path. users define the group of eight queues through which traffic is to be transmitted out of the service point. The traffic passing from the ingress path is routed to the correct egress destination interfaces via the egress service points. Of course. it is aggregated into one of the eight queues associated with the specific service point. and so on. The 2K queues are ordered in groups of eight queues. this comes at the cost of a possible increase in latency. Physically. These eight queues correspond to CoS values. in other words. Users can configure burst size as a tradeoff between latency and immunity to bursts. The exact queue is determined by the CoS calculated by the ingress path. phn-3968 001v000 Page 5-75 . This is part of the service point egress configuration. eight priority queues.

Chapter 5: Feature Description Ethernet Features Before assigning traffic to the appropriate queue. the queue manager will drop incoming frames without applying the usual priority rules among frames. The queue size is defined by the WRED profile that is associated with the queue. users can create an oversubscription scenario among the queues for when the buffer size of the aggregate queues is lower than the total memory allocated to all the queues. Since the frames are dropped randomly. The 2K queues share a single memory of 2 Gbits. Each queue occupancy level is monitored by the WRED mechanism and randomly selected frames are dropped before the queue becomes overcrowded. For more details. In this way. namely. statistically each time another flow has to restrain its transmission rate as a result of frame loss (before the real congestion occurs). This operation is integrated with the queue occupancy level. Moreover. the user must understand both the benefits and the potential hazards. PTP 820G enables users to define a specific size for each queue which is different from the default size. Global synchronization occurs when TCP flows sharing bottleneck conditions receive loss indications at around the same time. Each TCP flow recognizes a frame loss and restrains its transmission rate (basically by reducing the window size). This can result in periods during which link bandwidth utilization drops significantly as a consequence of simultaneous falling to a ”slow start” of all the TCP flows. WRED The Weighted Random Early Detection (WRED) mechanism can increase capacity utilization of TCP traffic by eliminating the phenomenon of global synchronization. The following figure demonstrates the transmission rate of two TCP flows and the aggregated load over time when WRED is enabled. see WRED on page 5-72. Figure 66 Synchronized Packet Loss WRED eliminates the occurrence of traffic congestion peaks by restraining the transmission rate of the TCP flows. the system makes a determination whether to forward or drop the traffic using a WRED algorithm with a predefined green and yellow curve for the desired queue. The following figure demonstrates the behavior of two TCP flows over time without WRED. phn-3968 001v000 Page 5-76 . the overall aggregated load on the radio link remains stable while the transmission rate of each individual flow continues to fluctuate similarly. In doing this. that if a lack of buffer space occurs.

the probability of dropping each incoming frame increases as well. As a consequence. The WRED profile assigned to the queue determines whether or not to drop incoming packets according to the occupancy of the queue. These curves describe the probability of randomly dropping frames as a function of queue occupancy. since PTP 820G will not egress packets to the media at a rate which is higher than the media is able to transmit.Chapter 5: Feature Description Ethernet Features Figure 67 Random Packet Loss with Increased Capacity Utilization Using WRED When queue occupancy goes up. phn-3968 001v000 Page 5-77 . In addition. This profile is assigned profile number 31. Basically. as queue occupancy grows. To deal with this. using different curves for Yellow packets and Green packets enables users to enforce the rule that Yellow packets be dropped before Green packets when there is congestion. and is configured with the following values:  100% Yellow traffic drop after 16kbytes occupancy.  Yellow maximum drop is 100%  Green maximum drop is 100% A WRED profile can be assigned to each queue. PTP 820G also includes a pre-defined read-only WRED profile that defines a tail-drop curve. Each profile contains a Green traffic curve and a Yellow traffic curve.  100% Green traffic drop after 32kbytes occupancy. statistically more TCP flows will be restrained before traffic congestion occurs. PTP 820G enables users to define up to 30 WRED profiles. This difference in rates should be fixed in order to reduce packet drops and to reach the maximal media utilization. this means that the ingress path rate (the TCP stream that is ingressing the switch) is higher than the egress path rate. The following figure provides an example of a WRED profile.

with granularity of 8 Kbytes. the software automatically rounds off the setting according to the granularity. Users can enter any value within the permitted range.  Green Maximum Threshold – Permitted values are 0 Kbytes to 8 Mbytes. Global WRED Profile Configuration PTP 820G supports 30 user-configurable WRED profiles and one pre-defined (default) profile.  Yellow Maximum Threshold – Permitted values are 0 Kbytes to 8 Mbytes. The following are the WRED profile attributes:  Green Minimum Threshold – Permitted values are 0 Kbytes to 8 Mbytes. with granularity of 8 Kbytes. If the user enters a value below the lowest granular value (except 0). Based on the value entered by the user. with 1% drop granularity. the software adjusts the setting to the minimum. Note K is equal to 1024. is the default profile for each queue.  Yellow Maximum Drop – Permitted values are 1% to 100%. A tail drop curve is useful for reducing the effective queue size. with granularity of 8 Kbytes.  Green-Maximum Drop – Permitted values are 1% to 100%.Chapter 5: Feature Description Ethernet Features Figure 68 WRED Profile Curve Probability to drop [%] Yellow max threshold Green max threshold 100 Yellow max drop ratio Green max drop ratio Queue depth [bytes] Yellow min threshold Green min threshold Note The tail-drop profile.  Yellow Minimum Threshold – Permitted values are 0 Kbytes to 8 Mbytes. Profile 31. with granularity of 8 Kbytes. phn-3968 001v000 Page 5-78 . such as when low latency must be guaranteed. with 1% drop granularity.

Moreover. there is no way to distinguish between different services and traffic streams within the same priority. Note With standard QoS call services are assigned to a single default service bundle The service bundle level represents the groups of eight priority queues. frames are passed on and not dropped up to the minimum Green and Yellow thresholds. WRED performs a pseudo-random drop with a ratio based on the curve up to the maximum Green and Yellow thresholds. or for a group of streams that are bundled together. Since all traffic for the interface egresses via these queues. different behavior among the different traffic streams that constitute the aggregate stream can cause unpredictable behavior between the streams. This enables the system to fully perform H-QoS with a top-down resolution. 100% of frames with the applicable Color are dropped. From this point. H-QoS Hierarchy The egress path hierarchy is based on the following levels:  Queue level  Service bundle level  Logical interface level The queue level represents the physical priority queues. egress data is mapped to a single egress interface. Hierarchical QoS (H-QoS) solves this problem by enabling users to create a real egress tunnel for each stream. in a situation in which one traffic stream can transmit 50 Mbps in a shaped manner while another can transmit 50 Mbits in a burst. This single interface supports up to eight priority queues. One or more service points can be attached to a specific bundle. For example.Chapter 5: Feature Description Ethernet Features For each curve. each with three distinct types of traffic streams:  Voice – high priority  Data – medium priority  Streaming – lower priority While the benefits of QoS on the egress path can be applied to the aggregate streams. Each eight queues are bundled and represent eight CoS priority levels. frames may be dropped in an unexpected way due to a lack of space in the queue resulting from a long burst. The system automatically assigns the default “tail drop” WRED profile (Profile ID 31) to every queue. Standard QoS and Hierarchical QoS (H-QoS) In a standard QoS mechanism. This level holds 2K queues. Users can change the WRED profile per queue based on the application served by the queue. without HQoS they will not be able to distinguish between the various services included in these aggregate streams. phn-3968 001v000 Page 5-79 . Every eight queues are managed as a single service bundle. The figure below shows three services. and the traffic from the service point to one of the eight queues is based on the CoS that was calculated on the ingress path. Beyond this point. which correspond to the CoS of the data. and to fully control the required SLA for each stream.

Note With standard QoS. Mapping to the eight priority queues is based on the CoS calculated on the ingress path. The shaper on the queue level stops traffic from leaving the queue if a specific user-defined PIR has been exceeded.  Weighted Fair Queuing (WFQ) among queues with the same priority. the shaper changes the scheduling priority if traffic via the service bundle is above the userdefined CIR and below the PIR. which only changes the egress CoS and Color.  Eight queues per service bundle H-QoS on the Interface Level Users can assign a single leaky bucket shaper to each interface. Service bundle traffic counters are valid on this level. Usually. as follows:  Scheduling (serve) priorities among the eight priority queues. the scheduler stops transmission for the service bundle. RMON counters are valid on the interface level. In addition. before any marking operation.Chapter 5: Feature Description Ethernet Features The interface level represents the physical port through which traffic from the specified service point egresses. The following summarizes the egress path hierarchy:  Up to 8 physical interfaces  One service bundle per interface in standard QoS / 256 service bundles in H-QoS. H-QoS on the Service Bundle Level Users can assign a dual leaky bucket shaper to each service bundle. Note The system assigns the rules for all service bundles under the interface. the service points will share the same traffic type and characteristics. Users can assign a single leaky bucket to each queue. The shaper on the interface level stops traffic from the interface if a specific user-defined peak information rate (PIR) has been exceeded. If traffic is above the PIR. users can configure scheduling rules for the priority queues. phn-3968 001v000 Page 5-80 . users assign the egress traffic to a single service bundle (Service Bundle ID 1). H-QoS on the Queue Level The egress service point points to a specific service bundle. if multiple service points are connected to a service bundle. On the service bundle level. Depending on the user application. the user can connect either a single service point or multiple service points to a service bundle.

the operational mode is H-QoS.QoS Mode As discussed above. H-QoS mode enables users to fully distinguish among the streams and to achieve SLA per service. The following figure provides a detailed depiction of the H-QoS levels.  If the user configured the egress service points to transmit traffic via multiple service bundles. only Service Bundle 1 is active and there are eight output transmission queues.Chapter 5: Feature Description Ethernet Features Traffic counters are valid on this level.  If the user configured all the egress service points to transmit traffic via a single service bundle. phn-3968 001v000 Page 5-81 . users can select whether to work in Standard QoS mode or H-QoS mode. Figure 69 Detailed H-QoS Diagram Priority 4 (Highest) Priority 3 Priority 2 Priority 1 (Lowest) Queues (CoS) Service Bundle Port Service Point Service 1 CoS0 Single Rate CoS1 Single Rate CoS2 Single Rate CoS3 Single Rate CoS4 Single Rate CoS5 Single Rate CoS6 Single Rate CoS7 Single Rate WFQ Dual Shaper WFQ Single Shaper CoS0 Single Rate CoS1 Single Rate CoS2 Single Rate CoS3 Single Rate CoS4 Single Rate CoS5 Single Rate CoS6 Single Rate CoS7 Single Rate WFQ Service 2 Dual Shaper WFQ Service Point H. the operational mode is Standard QoS. In this mode.

no egress shaping is performed on that service bundle.000. Based on the value entered by the user.000.000.000 bps – granularity of 16.000. phn-3968 001v000 Page 5-82 .000 bps – granularity of 64.000 bps o 32. The profiles can be configured as follows:   Valid CIR values are: o 0 – 32.000 bps Note Users can enter any value within the permitted range.  Service Bundle level – Dual leaky bucket shaping  Interface level – Single leaky bucket shaping Queue Shapers Users can configure up to 31 single leaky bucket shaper profiles.000 – 32. Based on the value entered by the user.000 bps o 32. If no profile is attached to the queue. If no profile is attached to the service bundle.000 – 131. Service Bundle Shapers Users can configure up to 255 dual leaky bucket shaper profiles. PTP 820G performs egress shaping on the following three levels:  Queue level – Single leaky bucket shaping.000 bps – granularity of 16.000 bps  32. the software automatically rounds off the setting according to the granularity.Chapter 5: Feature Description Ethernet Features Shaping on the Egress Path Egress shaping determines the traffic profile for each queue. the software adjusts the setting to the minimum. the software adjusts the setting to the minimum.000.000 bps – granularity of 64.000. If the user enters a value below the lowest granular value (except 0). Users can attach one of the configured service bundle shaper profiles to each service bundle.000.000.000 – 32. The CIR value can be set to the following values:  16.000 bps Valid PIR values are: o 16. Users can attach one of the configured queue shaper profiles to each priority queue.000 bps – granularity of 16.000 bps Note Users can enter any value within the permitted range.000 – 1. no egress shaping is performed on that queue. the software automatically rounds off the setting according to the granularity.000 – 1.000.008. If the user enters a value below the lowest granular value (except 0).000 bps – granularity of 64.000.

000 – 999. If no profile is attached to the interface.192. The CIR can be set to the following values:  0 – 8.000 bps – granularity of 32.768. the software automatically rounds off the setting according to the granularity.000 bps  32.768. see Global Rate Meter Profiles on page 5-68. and determines which queue is ready to transmit.192.  Weighted Fair Queuing (WFQ) – If two or more queues have the same priority and are ready to transmit. Line Compensation for Shaping Users can configure a line compensation value for all the shapers under a specific logical interface.000 bps – granularity of 8. When a user assigns traffic to more than a single service bundle (H-QoS mode).192.000 bps Note Users can enter any value within the permitted range. For more information.000 – 32. If the user enters a value below the value (except 0).000 bps – granularity of 512. PTP 820G uses a unique algorithm with a hierarchical scheduling model over the three levels of the egress path that enables compliance with SLA requirements.424.072.000 – 131. no egress shaping is performed on that interface.000 bps – granularity of 128.072. If more than one queue is ready to transmit.Chapter 5: Feature Description Ethernet Features Interface Shapers Users can configure up to 31 single leaky bucket shaper profiles. The scheduler scans all the queues over all the service bundles. Users can attach one of the configured interface shaper profiles to each interface. Egress Scheduling Egress scheduling is responsible for transmission from the priority queues.000 bps  131. the software adjusts the setting to the minimum. phn-3968 001v000 Page 5-83 .000 bps  8. per interface. the scheduler determines which queue transmits first based on:  Queue Priority – A queue with higher priority is served before lower-priority queues. the scheduler transmits frames from the queues based on a WFQ algorithm that determines the ratio of frames per queue based on a predefined weight assigned to each queue. multiple instances of this model (up to 32 per port) are valid. The following figure shows the scheduling mechanism for a single service bundle (equivalent to Standard QoS). Based on the value entered by the user.

all the service bundles under the interface inherit the profile. The priority mechanism distinguishes between two states of the service bundle:  Green State – Committed state  Yellow state – Best effort state Green State refers to any time when the service bundle total rate is below the user-defined CIR. For details.Chapter 5: Feature Description Ethernet Features Figure 70 Scheduling Mechanism for a Single Service Bundle Interface Priority The profile defines the exact order for serving the eight priority queues in a single service bundle. from 4 (highest) to 1 (lowest). An additional four Yellow priority profiles are defined automatically. Yellow State refers to any time when the service bundle total rate is above the user-defined CIR but below the PIR. The following table provides a sample of an interface priority profile. see Frame Cut-Through on page 5-5. When the user attaches a profile to an interface. Note When Frame Cut-Through is enabled. User can define up to four Green priority profiles. frames in queues with 4 th priority pre-empt frames already in transmission over the radio from other queues. phn-3968 001v000 Page 5-84 . This profile is also used as the default interface priority profile.

no matter what the service bundle state is. from 4 (highest) to 1 (lowest).  CoS 1 Description – CoS 1 user description field. PDUs.  CoS 3 Priority – CoS 3 queue priority. from 4 (highest) to 1 (lowest). from 4 (highest) to 1 (lowest). the service bundle priorities are system-defined priorities shown in the Yellow Priority column.  CoS 3 Description – CoS 3 user description field. up to 20 characters. while profile 9 is the pre-defined read-only default interface priority profile. up to 20 characters. The system supports up to nine interface priority profiles. since it is assumed that only high priority traffic will be tunneled via CoS 7. When the service bundle state is Yellow (best effort state).  CoS 2 Description – CoS 2 user description field. etc.  CoS 5 Description – CoS 5 user description field. up to 20 characters. up to 20 characters. from 4 (highest) to 1 (lowest). phn-3968 001v000 Page 5-85 . Note CoS 7 is always marked with the highest priority.Chapter 5: Feature Description Ethernet Features Table 17 QoS Priority Profile Example . from 4 (highest) to 1 (lowest).Profile ID (1-9) CoS Green Priority (user defined) Yellow Priority (read only) Description 0 1 1 Best Effort 1 2 1 Data Service 4 2 2 1 Data Service 3 3 2 1 Data Service 2 4 2 1 Data Service 1 5 3 1 Real Time 2 (Video with large buffer) 6 3 1 Real Time 1 (Video with small buffer) 7 4 4 Management (Sync. Permitted values are 1 to 8.  CoS 4 Priority – CoS 4 queue priority.  CoS 2 Priority – CoS 2 queue priority. the service bundle priorities are as defined in the Green Priority column.) When the service bundle state is Green (committed state).  CoS 0 Description – CoS 0 user description field. up to 20 characters.  CoS 0 Priority – CoS 0 queue priority. up to 20 characters. The following interface priority profile parameters can be configured by users:  Profile ID – Profile ID number.  CoS 1 Priority – CoS 1 queue priority. Profiles 1 to 8 are defined by the user. from 4 (highest) to 1 (lowest).  CoS 4 Description – CoS 4 user description field.  CoS 5 Priority – CoS 5 queue priority.

The following table provides an example of a WFQ profile. Profile ID 1 is a pre-defined read-only profile. The system supports up to six WFQ interface profiles.Profile ID (1-7) CoS Queue Weight (Green) Queue Weight 0 20 20 1 20 20 2 20 20 3 20 20 4 20 20 5 20 20 6 20 20 7 20 20 (Yellow – not visible to users) For each CoS. All the service bundles under the interface inherit the WFQ profile attached to the interface. Permitted values are 1 to 20.Chapter 5: Feature Description Ethernet Features  CoS 6 Priority – CoS 6 queue priority.  CoS 7 Priority – CoS 7 queue priority.  CoS 7 Description – CoS 7 user description field. Permitted values are 2 to 6. By default. WFQ defines the transmission ratio. Users can attach one of the configured interface priority profiles to each interface. up to 20 characters. Profiles 2 to 6 are user-defined profiles. By default. the pre-defined system profile. the pre-defined system profile. from 4 (highest) to 1 (lowest). Users can attach one of the configured interface WFQ profiles to each interface. in bytes. up to 20 characters.  Profile ID – Profile ID number.  CoS 6 Description – CoS 6 user description field. but when two or more queues have data to transmit and their priority is the same. phn-3968 001v000 Page 5-86 . the scheduler uses Weighted Fair Queuing (WFQ) to determine the priorities within each priority.  Weight – Transmission quota in bytes. the interface is assigned Profile ID 9. the interface is assigned Profile ID 1. Weighted Fair Queuing (WFQ) As described above. Table 18 WFQ Profile Example . and is used as the default profile. the user can define. between the queues. from 4 (highest) to 1 (lowest). the scheduler serves the queues based on their priority.

the egress CoS and Color are the same as the CoS and Color of the frame when it ingressed into the switching fabric. phn-3968 001v000 Page 5-87 . or if the outer frame is C-VLAN and C-VLAN CoS preservation is disabled.Chapter 5: Feature Description Ethernet Features Egress Statistics Queue-Level Statistics PTP 820G supports the following counters per queue at the queue level:  Transmitted Green Packet (64 bits counter)  Transmitted Green Bytes (64 bits counter)  Transmitted Green Bits per Second (32 bits counter)  Dropped Green Packets (64 bits counter)  Dropped Green Bytes (64 bits counter)  Transmitted Yellow Packets (64 bits counter)  Transmitted Yellow Bytes (64 bits counter)  Transmitted Yellow Bits per Second (32 bits counter)  Dropped Yellow Packets (64 bits counter)  Dropped Yellow Bytes (64 bits counter) Service Bundle-Level Statistics PTP 820G supports the following counters per service bundle at the service bundle level:  Transmitted Green Packets (64 bits counter)  Transmitted Green Bytes (64 bits counter)  Transmitted Green Bits per Second (32 bits counter)  Dropped Green Packets (64 bits counter)  Dropped Green Bytes (64 bits counter)  Transmitted Yellow Packets (64 bits counter)  Transmitted Yellow Bytes (64 bits counter)  Transmitted Yellow Bits per Second (32 bits counter)  Dropped Yellow Packets (64 bits counter)  Dropped Yellow Bytes (64 bits counter) Interface-Level Statistics For information on statistics at the interface level. Marking mode is only applied if the outer frame is S-VLAN and S-VLAN CoS preservation is disabled. Marker Marking refers to the ability to overwrite the outgoing priority bits and Color of the outer VLAN of the egress frame. see Ethernet Statistics (RMON) on page 5-54. If outer VLAN preservation is enabled for the relevant outer VLAN.

the following global tables are used by the marker to decide which CoS and Color to use as the egress CoS and Color bits. If marking and CoS preservation for the relevant outer VLAN are both disabled. If Marking is enabled on a service point. When marking is performed.1ad UP (configurable) DEI Color (configurable) 0 Green 0 0 0 Yellow 0 1 1 Green 1 0 1 Yellow 1 1 2 Green 2 0 phn-3968 001v000 Page 5-88 .Chapter 5: Feature Description Ethernet Features Marking is performed according to a global table that maps CoS and Color values to the 802.1q UP Marking Table (C-VLAN) CoS Color 802. marking is applied according to the Green frame values in the global marking table. Table 19 802. the CoS and Color of frames egressing the service via that service point are overwritten according to this global mapping table.1ad UP Marking Table (S-VLAN) CoS Color 802.1q UP (Configurable) CFI Color (Configurable) 0 Green 0 0 0 Yellow 0 1 1 Green 1 0 1 Yellow 1 1 2 Green 2 0 2 Yellow 2 1 3 Green 3 0 3 Yellow 3 1 4 Green 4 0 4 Yellow 4 1 5 Green 5 0 5 Yellow 5 1 6 Green 6 0 6 Yellow 6 1 7 Green 7 0 7 Yellow 7 1 Table 20 802.1p-UP bits and the DEI or CFI bits.

Chapter 5: Feature Description Ethernet Features CoS Color 802.1q/802.1ad UP and CFI/DEI bits.1ad UP (configurable) DEI Color (configurable) 2 Yellow 2 1 3 Green 3 0 3 Yellow 3 1 4 Green 4 0 4 Yellow 4 1 5 Green 5 0 5 Yellow 5 1 6 Green 6 0 6 Yellow 6 1 7 Green 7 0 7 Yellow 7 1 The keys for these tables are the CoS and Color. which are user-configurable. The results are the 802. It is strongly recommended that the default values not be changed except by advanced users. Table 21 Summary and Comparison of Standard QoS and H-QoS Capability Standard QoS Hierarchical QoS Number of transmission queues per port 8 256 Number of service bundles 1 (always service bundle id equal 1) 32 WRED Per queue (two curves – for green traffic and for yellow traffic via the queue) Per queue (two curves – for green traffic and for yellow traffic via the queue) Shaping at queue level Single leaky bucket Single leaky bucket Shaping at service bundle level Dual leaky bucket Dual leaky bucket Shaping at port level Single leaky bucket (this level is not relevant since it is recommended to use service bundle level with dual leaky bucket) Single leaky bucket phn-3968 001v000 Page 5-89 . Standard QoS and Hierarchical QoS (H-QoS) Summary The following table summarizes and compares the capabilities of standard QoS and H-QoS.

Chapter 5: Feature Description

Ethernet Features

Capability

Standard QoS

Hierarchical QoS

Transmission queues
priority

Per queue priority (4
priorities).

Per queue priority (4
priorities). All service bundles
for a specific port inherit the
8-queues priority settings.

Weighted fair Queue
(WFQ)

Queue level (between
queues)

Queue level (between
queues)
Service Bundle level
(between service bundles)21

Marker

Supported

Supported

Statistics

Queue level (8 queues)

Queue level (256 queues)

Service bundle level (1
service bundle)

Service bundle level (32
service bundles)

Port level

Port level

Global Switch Configuration
The following parameters are configured globally for the PTP 820G switch:

S- VLAN Ethertype –Defines the ethertype recognized by the system as the S-VLAN ethertype.
PTP 820G supports the following S-VLAN ethertypes:
o

0x8100

o

0x88A8 (default)

o

0x9100

o

0x9200

C-VLAN Ethertype – Defines the ethertype recognized by the system as the C-VLAN ethertype.
PTP 820G supports 0x8100 as the C-VLAN ethertype.

MRU – The maximum segment size defines the maximum receive unit (MRU) capability and
the maximum transmit capability (MTU) of the system. Users can configure a global MRU for
the system. Permitted values are 64 bytes to 9612 bytes.

Network Resiliency
PTP 820G provides carrier-grade service resiliency using the following protocols:

G.8032 Ethernet Ring Protection Switching (ERPS)

Multiple Spanning Tree Protocol (MSTP)

These protocols are designed to prevent loops in ring/mesh topologies.

21

WFQ on the service bundle level is planned for future release.

phn-3968 001v000
Page 5-90

Chapter 5: Feature Description

Ethernet Features

G.8032 Ethernet Ring Protection Switching (ERPS)
ERPS, as defined in the G.8032 ITU standard, is currently the most advanced ring protection
protocol, providing convergence times of sub-50ms. ERPS prevents loops in an Ethernet ring by
guaranteeing that at any time, traffic can flow on all except one link in the ring. This link is called
the Ring Protection Link (RPL). Under normal conditions, the RPL is blocked, i.e., not used for
traffic. One designated Ethernet Ring Node, the RPL Owner Node, is responsible for blocking traffic
at one end of the RPL. When an Ethernet ring failure occurs, the RPL Owner unblocks its end of the
RPL, allowing the RPL to be used for traffic. The other Ethernet Ring Node adjacent to the RPL, the
RPL Neighbor Node, may also participate in blocking or unblocking its end of the RPL. A number of
ERP instances (ERPIs) can be created on the same ring.

G.8032 ERPS Benefits
ERPS, as the most advanced ring protection protocol, provides the following benefits:

Provides sub-50ms convergence times.

Provides service-based granularity for load balancing, based on the ability to configure
multiple ERPIs on a single physical ring.

Provides configurable timers to control switching and convergence parameters per ERPI.

G.8032 ERPS Operation
The ring protection mechanism utilizes an APS protocol to implement the protection switching
actions. Forced and manual protection switches can also be initiated by the user, provided the
user-initiated switch has a higher priority than any other local or far-end request.
Ring protection switching is based on the detection of defects in the transport entity of each link in
the ring. For purposes of the protection switching process, each transport entity within the
protected domain has a state of either Signal Fail (SF) or Non-Failed (OK). R-APS control messages
are forwarded by each node in the ring to update the other nodes about the status of the links.

Note
An additional state, Signal Degrade (SD), is planned for future release. The SD state is
similar to SF, but with lower priority.
Users can configure up to 16 ERPIs. Each ERPI is associated with an Ethernet service defined in the
system. This enables operators to define a specific set of G.8032 characteristics for individual
services or groups of services within the same physical ring. This includes a set of timers that
enables operators to optimize protection switching behavior per ERPI:

Wait to Restore (WTR) Timer – Defines a minimum time the system waits after signal failure is
recovered before reverting to idle state.

Guard Time – Prevents unnecessary state changes and loops.

Hold-off Time – Determines the time period from failure detection to response.

Each ERPI maintains a state machine that defines the node’s state for purposes of switching and
convergence. The state is determined according to events that occur in the ring, such as signal
failure and forced or manual switch requests, and their priority. Possible states are:

Idle

phn-3968 001v000
Page 5-91

Chapter 5: Feature Description

Protecting

Forced Switch (FS)

Manual Switch (MS)

Pending

Ethernet Features

As shown in the following figure, in idle (normal) state, R-APS messages pass through all links in
the ring, while the RPL is blocked for traffic. The RPL can be on either edge of the ring. R-APS
messages are sent every five seconds.
Figure 71 G.8032 Ring in Idle (Normal) State

Once a signal failure is detected, the RPL is unblocked for each ERPI. As shown in the following
figure, the ring switches to protecting state. The nodes that detect the failure send periodic SF
messages to alert the other nodes in the link of the failure and initiate the protecting state.
Figure 72 G.8032 Ring in Protecting State

phn-3968 001v000
Page 5-92

Chapter 5: Feature Description

Ethernet Features

The ability to define multiple ERPIs and assign them to different Ethernet services or groups of
services enables operators to perform load balancing by configuring a different RPL for each ERPI.
The following figure illustrates a ring in which four ERPIs each carry services with 33% capacity in
idle state, since each link is designated the RPL, and is therefore idle, for a different ERPI.
Figure 73 Load Balancing Example in G.8032 Ring

Multiple Spanning Tree Protocol (MSTP)
MSTP, as defined in IEEE 802.1q, provides full connectivity for frames assigned to any given VLAN
throughout a bridged LAN consisting of arbitrarily interconnected bridges.
With MSTP, an independent multiple spanning tree instance (MSTI) is configured for each group of
services, and only one path is made available (unblocked) per spanning tree instance. This
prevents network loops and provides load balancing capability. It also enables operators to
differentiate among Ethernet services by mapping them to different, specific MSTIs. The maximum
number of MSTIs is configurable, from 2 to 16.
MSTP is an extension of, and is backwards compatible with, Rapid Spanning Tree Protocol (RSTP).
PTP 820G supports MSTP according to the following IEEE standards:

802.1q

802.1ad amendment (Q-in-Q)

802.1ah (TE instance)

phn-3968 001v000
Page 5-93

 Common Internal Spanning Tree (CIST) – A collection of the ISTs in each MST Region. Each bridge selects a CIST priority vector for each port based on the priority vectors and MST Configuration Identifiers received from the other bridges and on an incremental path cost associated with each receiving port. without the formation of transient data loops.  A minimum cost path to the CIST Root is selected for each bridge.  An MSTI priority vector for any given MSTI within each MST Region.  Provides for predictable and reproducible active topology based on management of the MSTP parameters. MSTP specifies:  An MST Configuration Identifier that enables each bridge to advertise its configuration for allocating frames with given VIDs to any of a number of MSTIs. constituting a small percentage of the total available bandwidth which is independent of both the total traffic supported by the network and the total number of bridges or LANs in the network.  Provides for fault tolerance by automatically reconfiguring the spanning tree topology whenever there is a bridge failure or breakdown in a data path. MSTP Operation MSTP includes the following elements:  MST Region – A set of physically connected bridges that can be portioned into a set of logical topologies. The resulting priority vectors are such that in a stable network:  One bridge is selected to be the CIST Root.  A priority vector that consists of a bridge identifier and path cost information for the CIST.  Operates transparently to the end stations. and the CST that interconnects the MST regions and individual spanning trees. RSTP. which is a special spanning tree instance that disseminates STP topology information for all other MSTIs. All bridges and LANs are connected into a single CST.  Automatically reconfigures the spanning tree to accommodate addition of bridges and bridge ports to the network.  Common Spanning Tree (CST) – The single spanning tree calculated by STP.  Does not require bridges to be individually configured before being added to the network. and MSTP to connect MST Regions. phn-3968 001v000 Page 5-94 .Chapter 5: Feature Description Ethernet Features MSTP Benefits MSTP significantly improves network resiliency in the following ways:  Prevents data loops by configuring the active topology for each MSTI such that there is never more than a single route between any two points in the network.  Enables frames assigned to different services or service groups to follow different data routes within administratively established regions of the network.  Consumes very little bandwidth to establish and maintain MSTIs.  CIST Root – The bridge that has the lowest Bridge ID among all the MST Regions.  Internal Spanning Tree (IST) – Every MST Region runs an IST. MSTP connects all bridges and LANs with a single CIST.

G.  A change in an MSTI bridge priority. MEF-30. Figure 74 PTP 820G End-to-End Service Management phn-3968 001v000 Page 5-95 .  Maintenance commands.1ag.  A change in the service to instance mapping.1731. MEF-17. or port cost. and MEF-31.  Maintenance signals.  A change in the operational state of a port or group (LAG or protection). and RDI. such as AIS.Chapter 5: Feature Description  Ethernet Features The CIST Regional Root is identified as the one root per MST Region whose minimum cost path to the root is not through another bridge using the same MST Configuration Identifier. such as loopbacks and Linktrace commands. Based on priority vector comparisons and calculations performed by each bridge for each MSTI.  Third-party bridges running RSTP OAM PTP 820G provides complete Service Operations Administration and Maintenance (SOAM) functionality at multiple layers. port priority.  A change in the maximum number of MSTIs. The following events trigger MSTP re-convergence:  Addition or removal of a bridge or port.8013/Y. The last trigger only affects the modified MSTI. Note All except the last of these triggers can cause the entire MSTP to re-converge. PTP 820G is fully compliant with 802. MEF-20. one bridge is independently selected for each MSTI to be the MSTI Regional Root. including:  Fault management status and alarms. and a minimum cost path is defined from each bridge or LAN in each MST Region to the MSTI Regional Root. MSTP Interoperability MSTP in PTP 820G units is interoperable with:  Third-party bridges running MSTP.

SOAM is concerned with detecting. PTP 820G utilizes these protocols to maintain smooth system operation and non-stop data flow. MEF-30. including LANs other than IEEE 802. and MEF-31 specifications define SOAM.8013/Y. and the managed objects required to create and administer them.1731 standards and the MEF-17. isolating. Figure 75 SOAM Maintenance Entities (Example)  Protocols and procedures used by maintenance points to maintain and diagnose connectivity faults within a maintenance domain.1ag Ethernet FM (Connectivity Fault Management) consists of three protocols that operate together to aid in fault management:  Continuity check  Link trace  Loopback. The following are the basic building blocks of FM:  Maintenance domains. phn-3968 001v000 Page 5-96 . o Loopback: LBM/LBR mechanism is an on-demand mechanism. MEF-20. It is used to verify connectivity from any MEP to any certain Maintenance Point in the MA/MEG. IEEE 802.1ag and G.3 media. o CCM (Continuity Check Message): CCM can detect Connectivity Faults (loss of connectivity or failure in the remote MEP). their constituent maintenance points. A session of loopback messages can include up to 1024 messages with varying intervals ranging from 1 to 60 seconds. The IEEE 802. and reporting connectivity faults spanning networks comprising multiple LANs.Chapter 5: Feature Description Ethernet Features Connectivity Fault Management (FM) Note This feature is planned for future release. Message size can reach jumbo frame size.

AIS: AIS (defined in G. The difference between the sequences provides information about the fault location.8013/Y. as shown in the figure below.1731O) is the Ethernet alarm indication signal function used to suppress alarms following detection of defect conditions at the server (sub) layer. phn-3968 001v000 Page 5-97 . Multi-Carrier ABC groups. the system loops back all packets ingressing the interface. the Ethernet Line Interface Loopback feature provides the ability to run loopbacks over the link.Chapter 5: Feature Description o Ethernet Features Linktrace: The LTM/LTR mechanism is an on-demand mechanism. and 1+1 HSB groups. When Ethernet loopback is enabled on an interface. Fault localization – The ETH-LT function can be used for fault localization. LAGS. This enables loopbacks to be performed over the link from other points in the network. It can be used for the following purposes: Adjacent relation retrieval – The ETH-LT function can be used to retrieve the adjacency relationship between an MEP and a remote MEP or MIP. Ethernet loopbacks cannot be performed on the management interfaces. radio interfaces. Ethernet Line Interface Loopback Figure 76 Ethernet Line Interface Loopback – Application Examples Loopback on Radio Link PTP 820G IP-20G IP-20G PTP 820G Loopback from from Test Test Loopback EquipmenttotoIP-20G PTP 820G Equipment Ethernet EthernetInterface Interface Test Equipment Ethernet loopbacks can be performed on any logical interface. It can detect the route of the data from any MEP to any other MEP in the MA/MEG. A loopback can also be performed from the other side of the radio link. a loopback can be performed from test equipment over the line to an Ethernet interface. the sequence of MIPs and/or MEP will probably be different from the expected sequence. For example. When a fault occurs. In addition. PTP 820G supports loopback testing for its radio and TDM interfaces. This includes optical and electrical GbE interfaces. which enables loopback testing of the radio and TDM traffic interfaces as well as the IDU-RFU connection. The result of running ETH-LT function is a sequence of MIPs from the source MEP until the target MIP or MEP.

It is recommended to enable MAC address swapping if MSTP or LLDP is enabled. but can be disabled manually before the duration period ends. Ethernet loopback activation on the remote side of the link causes loss of management to the remote unit. Permanent loopback is not supported. In a system using in-band management.8032 and MSTP) will detect interface failure due to the failure to receive BPDUs.Chapter 5: Feature Description Ethernet Features The following parameters can be configured for an Ethernet loopback:  The interface can be configured to swap DA and SA MAC addresses during the loopback. This prevents Ethernet loops from occurring.  Ethernet loopback has a configurable duration period of up to 2 ½ hours. The duration period of the loopback should take this into account. phn-3968 001v000 Page 5-98 . Ethernet loopbacks can be configured on more than one interface simultaneously. network resiliency protocols (G. When an Ethernet loopback is active.

and having other nodes derive their clocks from that source. o The transported frequency is used to drive the outgoing Ethernet signal. for example. The following synchronization applications are relevant:  Distribution of synchronization to equipment that supports synchronous Ethernet (SyncE) in a PDH-synchronized network (co-located synchronization): o Synchronization sources are entered into the system as PDH trails transported through the system. and/or T4 sync input and output. which was derived from some reference clock source. phn-3968 001v000 Page 5-99 . This section includes:  Synchronization Overview  PTP 820G Synchronization Solution  Available Synchronization Interfaces  Configuring Native Sync Distribution  Native Sync Distribution Mode  SyncE PRC Pipe Regenerator Mode  SSM Support and Loop Prevention Related topics:  NTP Support Synchronization Overview Frequency synchronization consists of the transport of a frequency timing reference through the physical layer of a certain interface. based on the operator’s network and migration strategy. FE. In 2G networks. SDH. E1. PDH.Chapter 5: Feature Description Synchronization Synchronization This section describes PTP 820G’s flexible synchronization solution that enables operators to configure a combination of synchronization techniques. o In the desired nodes. T3/T4 dedicated frequency interface. providing PRC grade (G. The interface used to convey the frequency may be an Ethernet. Synchronization enables the receiving side of an interface to lock onto the physical layer clock of the received signal. or logical interface. including:  Native Sync Distribution. Synchronization can be used to synchronize network elements by feeding one node with a reference clock. thereby frequencysynchronizing the receiver with that source. T3. the frequency is taken from the local trails (which derive their frequency from the original input).  SyncE PRC Pipe Regenerator mode. all PDH trails are synchronized to a common clock.811) performance for pipe (“regenerator”) applications. DS1. for end-to-end distribution using GE.

Chapter 5: Feature Description   Synchronization Distribution of synchronization in a hybrid network. including:  IEEE-1588  NTP  RTP phn-3968 001v000 Page 5-100 . or using GPS. o Typical performance target: frequency accuracy of < 50 ppb. o In nodes with PDH support. the reference frequency is conveyed to the user through a DS1 / E1 interface used for synchronization. Precision Timing-Protocol (PTP) PTP synchronization refers to the distribution of frequency. and absolute time information across an asynchronous frame switched network. CDMA-2000. o Typical performance target: frequency accuracy of < 20 . for example) and distributed through the radio links. Frequency distribution is the traditional technique used.50 ppb. o GPS is the traditional technique used. Synchronization is an essential part of any mobile backhaul solution and is sometimes required by other applications as well. where some of the sites require SyncE and others require PDH synchronization: o A synchronization source is entered into the network (through Ethernet or SDH. Two unique synchronization issues must be addressed for mobile networks:  Frequency Lock: Applicable to GSM and UMTS-FDD networks. and WiMAX networks. the reference frequency is conveyed to the user via SyncE interfaces Distribution of synchronization in an Ethernet-only network: o A synchronization source is entered into the network through SyncE or SDH and distributed through the radio links o The reference frequency is conveyed to the user through the network via SyncE interfaces. o In nodes with Ethernet support. o Limits coding time division overlap. o Limits channel interference between carrier frequency bands. UMTS-TDD.  Phase Lock with Latency Correction: Applicable to CDMA. phase difference of < 1-3 ms. PTP can use a variety of protocols to achieve timing distribution. with traceability to a PRS master clock carried over PDH/SDH networks. phase.

with similar performance. and refers to a method whereby the frequency is delivered on the physical layer. This method offers the same synchronization quality provided over DS1 /E1 interfaces to legacy BTS/NodeB. The method is based on SDH/TDM timing.8261 and G. and does not change the basic Ethernet standards. The SyncE technique supports synchronized Ethernet outputs as the timing source to an all-IP BTS/NodeB.Chapter 5: Feature Description Synchronization Figure 77 Precision Timing Protocol (PTP) Synchronization Synchronous Ethernet (SyncE) SyncE is standardized in ITU-T G.8262. Figure 78 Synchronous Ethernet (SyncE) phn-3968 001v000 Page 5-101 .

phn-3968 001v000 Page 5-102 . 23 SyncE PRC Pipe Regenerator mode is planned for future release. supporting both 2048 Kbp/s and 2048 KHz Planned for future release E1/DS1 via T3 from Sync Interface Planned for future release Radio Carrier Yes Table 23 Synchronization Output Options Synchronization Input SSM Support Ethernet Interfaces Yes.811) performance for pipe (“regenerator”) applications Available Synchronization Interfaces Frequency signals can be taken by the system from a number of different interfaces (one reference at a time). The reference frequency may also be conveyed to external equipment through different interfaces.Chapter 5: Feature Description Synchronization PTP 820G Synchronization Solution Cambium’s synchronization solution ensures maximum flexibility by enabling the operator to select any combination of techniques suitable for the operator’s network and migration strategy. Table 22 Synchronization input Options Synchronization Input SSM Support Ethernet Interfaces Yes. per SyncE standards 2MHz via T3 input from Sync Interface.   Native Sync Distribution o End-to-End Native Synchronization distribution o GE/FE/DS1/E1/T322 o GE/FE/DS1/E1/T4 output o Supports any radio link configuration and network topology o Synchronization Status Messages (SSM) to prevent loops and enable use of most reliable clock source o User-defined clock source priority and quality level o Automated determination of relative clock source quality levels SyncE PRC Pipe Regenerator mode23 o PRC grade (G. per SyncE standards Traffic E1/DS1 Planned for future release 22 T3 input support is planned for future release.

o Synchronization reference: Causes the interface to generate its signal from the system reference clock. This can be: o Automatic: In this mode. only one of these sources is active. A revertive timer can be configured. o Its priority (1-16). No two interfaces may have the same priority. user must configure: o Its clock quality level.781 option II) or automatic. When using a radio channel to distribute a frequency. The quality level may be fixed (according to ITU-T G. o Force: The user can force the system to use a certain interface as the reference clock source. the source of its outgoing signal clock. phn-3968 001v000 Page 5-103 . Up to 16 sources can be configured in each node. o Loop Timing: Causes the interface to generate the signal from its own input. When the quality level is automatic. These are the interfaces from which the frequency is taken and distributed to other interfaces. it is not recommended. This can be: o Local clock: Causes the interface to generate its signal from a local oscillator. unrelated to the system reference frequency. Otherwise.Chapter 5: Feature Description Synchronization Synchronization Input SSM Support 2MHz via T4 output from Sync interface Planned for future release E1/DS1 via T4 output from Sync interface Planned for future release Radio Carrier Yes Radio Channels Used for backwards compatibility with FibeAir IP-10 units across a radio link. It is possible to configure up to 16 synchronization sources in the system. the active source is automatically selected based on the interface with highest available quality. Among interfaces with identical quality. the interface with the highest priority is used. it is determined by SSM messages. The node’s synchronization mode. which is taken from the synchronization source.24 Force mode is planned for future release. At any given moment. the clock is taken from the active source onto all other appropriately configured interfaces Configuring Native Sync Distribution Frequency is distributed by configuring the following parameters in each node:    24 System synchronization sources. For each interface. 2Mbps of bandwidth is used for this purpose. For each interface.

phn-3968 001v000 Page 5-104 . where the reference frequency from a single node is distributed to a number of base stations. No TDM trails or DS1/E1 interfaces at the tail sites are required. a frequency “flow” can be achieved. except locally in SDH interfaces). Figure 79 Synchronization Configuration The following restrictions apply for frequency distribution configuration:  An interface can either be used as a synchronization source or can take its signal from the system reference. but not both (no loop timing available. as shown in the example below. If the signal driving the synchronization fails.  The clock taken from a radio channel cannot be conveyed to another radio channel in the same radio. synchronization is distributed natively end-to-end over the radio links in the network.Chapter 5: Feature Description Synchronization By configuring synchronization sources and transporting the reference frequency to the related interfaces in a network. Ethernet) cannot be conveyed to another line interface in the same card.  The clock taken from a line interface (DS1/E1. Native Sync Distribution Mode In this mode. an alarm will alert the user and the system will enter holdover mode until another synchronization source signal is found. Synchronization is typically provided by one or more clock sources (SSU/GPS) at fiber hub sites. SDH.

or in which topology loops may exist.  There are no reference loops. preferably the source with the highest accuracy. no element in the network will use an input frequency from an interface that ultimately derived that frequency from one of the outputs of that network element. PTP 820G’s Native Sync Distribution mechanism enables users to define a priority level for each possible clock source. phn-3968 001v000 Page 5-105 . Synchronization Status Messages (SSM) are sent regularly through each interface involved in frequency distribution. requires an active mechanism to ensure that:  A single source is be used as the clock source throughout the network. 25 Planned for future release. enabling the network to gather and maintain a synchronization status for each interface according to the system’s best knowledge about the frequency quality that can be conveyed by that interface. In other words.Chapter 5: Feature Description Synchronization Figure 80 Native Sync Distribution Mode In native Sync Distribution mode. Ring topologies present special challenges for network synchronization. the following interfaces can be used for sync output:  DS1/E1  GE/FE (SyncE)  T4 (2MHz or DS1 waveform) Native Sync Distribution mode can be used in any link configuration and any network topology. Any system that contains more than one clock source for synchronization. 26 Planned for future release. the following interfaces can be used as the sync references:  E1 / DS125  GE (SyncE)  T3 (DS1 /E1 waveform)26 Additionally.

from those interfaces with the highest quality. an PTP 820G at a fiber node is synchronized to:  SyncE input from an Ethernet uplink  External synchronization input via a DS1/E1 interface Figure 81 Native Sync Distribution Mode Usage Example The following figure illustrates Native Sync Distribution in a tree scenario. The network does this by evaluating the clock quality of the available source interfaces and selecting. the network assigns each interface a quality level and determines which interface to use as the current clock source. The synchronization is re-evaluated whenever one of the following occurs:  Any synchronization source is added.  The clock quality status changes for any source interface. Native Sync Distribution Examples The figure below provides a Native Sync Distribution mode usage example in which synchronization is provided to all-frame Node-Bs using SyncE.Chapter 5: Feature Description Synchronization Based on these parameters. the interface with the highest user-defined priority. or deleted by a user. edited. In this illustration. phn-3968 001v000 Page 5-106 .  The synchronization reference is changed for the node.

phn-3968 001v000 Page 5-107 . during normal operation.Chapter 5: Feature Description Synchronization Figure 82 Native Sync Distribution Mode – Tree Scenario The following figure illustrates Native Sync Distribution in a ring scenario. where a link has failed and the Native Sync timing distribution has been restored over an alternate path by using SSM messages. Figure 83 Native Sync Distribution Mode – Ring Scenario (Normal Operation) The following figure illustrates Native Sync Distribution in a ring scenario.

each PHY must act either as clock master or as clock slave in its own link. Frequency distribution behaves in a different way for optical and electrical GE interfaces. because of the way these interfaces are implemented:  For optical interfaces.  For electrical interfaces. separate and independent frequencies are transported in each direction. phn-3968 001v000 Page 5-108 . For this reason. the radio frame frequency is used as the reference signal for the outgoing Ethernet PHY. and used as a reference for the radio frame.  Simplified configuration In PRC pipe regenerator mode. determined by the user.Chapter 5: Feature Description Synchronization Figure 84 Native Sync Distribution Mode – Ring Scenario (Link Failure) SyncE PRC Pipe Regenerator Mode Note SyncE PRC Pipe Regenerator Mode is planned for future release. In SyncE PRC pipe regenerator mode. PRC pipe regenerator mode makes use of the fact that the system is acting as a simple link (so no distribution mechanism is necessary) in order to achieve the following:  Improved frequency distribution performance. frequency is transported between two GE interfaces through the radio link. frequency is taken from the incoming GE Ethernet or radio interface signal. with PRC quality. frequency can only be distributed in one direction. On the receiver side.

781.811  SSU-A  SSU-B  G. then the quality is determined by the received SSMs or becomes “failure” upon interface failure (such as LOS. The following are the principles of operation:  At all times.Chapter 5: Feature Description Synchronization SSM Support and Loop Prevention In order to provide topological resiliency for synchronization transfer.).). the following are the possible quality values (from highest to lowest):  AUTOMATIC (available only in interfaces for which SSM support is implemented)  G. As a reference. PTP 820G implements the passing of SSM messages over the radio interfaces.  In order to prevent loops.813/8262 .  The reference source quality is transmitted through SSM messages to all relevant radio interfaces. This is the quality of the current synchronization source interface. since a network may have more than one source clock.  The current received SSM status for every source interface. an SSM with quality “Do Not Use” is sent towards the active source interface  At any given moment. each source interface has a “quality status” which is determined as follows: o If quality is configured as fixed.default  DO NOT USE  Failure (cannot be configured by phn-3968 001v000 Page 5-109 . the SSM mechanism provides reference source resiliency. LOF. In addition. o If quality is automatic.  Each unit determines the current active clock reference source interface: o The interface with the highest available quality is selected. LOC. then the quality status becomes “failure” upon interface failure (such as LOS. SSM timing in PTP 820G complies with ITU-T G. the system enables users to display:  The current source interface quality.  The current node reference source quality.  Each unit holds a parameter which indicates the quality of its reference clock. etc. o From among interfaces with identical quality. LOF. etc. the interface with the highest priority is selected. LOC.

Figure 85 Hybrid Ethernet and TDM Services Services engine TDM cross-connect (VCs) E1 TDM Traffic TDM PW Network processor (EVCs) Hybrid Radio Packet Traffic GE/FE Hybrid Ethernet and TDM services can also be transported via cascading interfaces. This enables the creation of links among multiple PTP 820G units in a node for multi-carrier and multidirectional applications. Hybrid services can utilize either Native TDM or pseudowire. PTP 820G offers hybrid Ethernet and TDM services. Figure 86 Hybrid Ethernet and TDM Services Carried Over Cascading Interfaces TDM cross-connect (VCs) SAP Cascading Port TDM Traffic Port Ethernet Services (EVCs) SNP SAP SNP TDM cross-connect (VCs) E1 Port SAP Cascading Port Port User Port (UNI) GE/FE Port Ethernet Services (EVCs) SAP SAP SNP SAP phn-3968 001v000 Page 5-110 Packet Traffic Hybrid Radio .Chapter 5: Feature Description TDM Services TDM Services PTP 820G provides integrated support for transportation of TDM (DS1 / E1) services with integrated DS1/ E1 interfaces (optional). Two types of TDM services are supported using the same hardware:  Native TDM trails  TDM Pseudowire services (enabling interoperability with third party packet/PW equipment) In addition.

Figure 87 Hybrid Ethernet and Native TDM Services TDM cross-connect (VCs) E1/ch-STM-1 Port SAP Ethernet Services (EVCs) PtP Service User Port (UNI) GE/FE Port TDM Traffic SAP SAP SNP SAP Packet Traffic Hybrid Radio Multipoint Service User Port (UNI) GE/FE SAP SNP Network Port Port Port SAP GE/FE SNP Native TDM Trails Provisioning The PTP 820G Web EMS provides a simple and easy-to-use GUI that enables users to provision end-to-end TDM trails. Cascading interface support is planned for future release.Chapter 5: Feature Description TDM Services Native TDM Trails PTP 820G provides native TDM support. The Services Provisioning GUI includes the following trail-creation end points:  TDM interface  Radio interface  Cascading interface27 TDM Trails and Synchronization Related topics:  Synchronization Synchronization for TDM trails can be provided by any of the following synchronization methods:  27 Loop Timing – Timing is taken from incoming traffic. along with a TDM trail utilizing virtual connections (VCs) via PTP 820G’s cross-connect. phn-3968 001v000 Page 5-111 . PTP 820G also supports hybrid Ethernet and native TDM services. The following figure shows an example of a hybrid service package that includes a Point-to-Point and a Multipoint Ethernet service. utilizing a cross-connect module to support up to 256 TDM trails. utilizing cascading ports.

Figure 88 1:1 TDM Path Protection – Ring Topology phn-3968 001v000 Page 5-112 . Two different kinds of path protection are available. TDM Trail Priority In situations where ACM switches to lower modulations. but requires low PDV. PTP 820G enables users to define trails as high or low priority.Chapter 5: Feature Description TDM Services  Recovered Clock– Clock information is recovered on the egress path. reducing throughput. In this case. The ring is closed on one side by the PTP 820G or any other equipment by third party supporting standard SNCP. it is sometimes necessary to drop some of the outgoing traffic.  1+1 Dual Homing TDM path protection is suitable for networks in which the PTP 820G elements are set up as a chain connected to the third party networks at two different sites. For native TDM trails. each suitable for a different network topology:  1:1 TDM path protection is suitable for ring networks that consist entirely of PTP 820G elements with two end-point interfaces for the TDM service. This helps to ensure that high priority TDM traffic is not interrupted due to fading or other temporary conditions affecting throughput. TDM Path Protection TDM path protection enables the operator to define two separate network paths for a single TDM service. Recovered Clock can provide very accurate synchronization. Extra information may be located in an RTP header that can be used to correct frequency offsets. there are three end-point interfaces in the PTP 820G section of the network.  System Reference Clock –Trails are synchronized to the system reference clock.

After switchover to the protecting path. In revertive mode. phn-3968 001v000 Page 5-113 . the system monitors the availability of the protected path at all times. once the protected path is operational and available without any alarms. 1:1 TDM path protection can be configured to operate in revertive mode. TDM path protection is implemented by means of configuring active and backup path at the TDM service end-points. freeing up resources on the standby path. if the protected path remains operational and available. but traffic flows to the destination via different paths. Each path has the same TDM interface end points. the system waits the user-configured Wait to Restore (WTR) time and then. initiates a revertive protection switch. A single WTR time is configured for all the TDM trails in the system. Bandwidth is utilized only on the active path. 1+1 Dual Homing TDM Path Protection 1+1 TDM dual homing path protection is used for networks in which the PTP 820G and/or PTP 820 network elements are set up as a chain connected to third party networks at two different sites.Chapter 5: Feature Description TDM Services Figure 89 1+1 Dual Homing TDM Path Protection – Network Topology 1:1 TDM Path Protection 1:1 TDM path protection enables the operator to define two separate network paths for a single TDM service. where one end-point is located on an PTP 820G or PTP 820 unit and the other end-point is located on third-party equipment supporting standard SNCP.

However. This service package can be carried on any of the PTP 820G’s Ethernet ports. phn-3968 001v000 Page 5-114 . thereby supporting interoperability with standard SNCP in the third party equipment. The following figure shows an example of an all-packet service package that includes two Point-to-Point services and one Multipoint Ethernet service. PTP 820G also supports all-packet Ethernet and TDM pseudowire services. where the first Point-to-Point service carries E1 pseudowire traffic. 28 Support for TDM PMs is planned for future release. with one second granularity. send the data through the system in frame format that can be processed by the PTP 820G’s Ethernet ports. and convert the data back to TDM format. the operator defines two separate network paths for a single TDM service. TDM Performance Monitoring The following monitoring features are available for TDM services and interfaces: 28 PMs are computed at the TDM card and reported at 15-minute intervals. unlike 1:1 TDM path protection. traffic flows through both paths simultaneously.Chapter 5: Feature Description TDM Services As with 1:1 TDM path protection.    PMs for the outgoing TDM trail: o Errored seconds o Severely errored seconds o Unavailable seconds PMs for incoming native DS1 / E1 signal: o Errored seconds o Severely errored seconds o Unavailable seconds PMs for incoming SDH 155MHz signal: o Errored seconds o Severely errored seconds o Severely errored framing seconds o Coding Violations TDM Pseudowire PTP 820G’s TDM Pseudowire provides TDM-over-packet capabilities by means of optional integrated TDM interface that process TDM data.

32 A subset of DS0 is supported in CESoP.Chapter 5: Feature Description TDM Services Figure 90 All-Packet Ethernet and TDM Pseudowire Services Ethernet Services (EVCs) TDM PW E1 Port PtP Service SAP SAP SNP SAP User Port (UNI) GE/FE Port PtP Service S. which is always transported over Layer 2 Ethernet.32 PSN Tunnel 29 CESoP mode is planned for future release. phn-3968 001v000 Page 5-115 . 30 IP/UDP (IETF) encapsulation is planned for future release. bidirectional flow of information between a TDM signal and a packed flow. 31 MPLS (MFA8) encapsulation is planned for future release. Such a service interconnects and makes use of the following elements:  TDM Signal o  The TDM signal may be an entire DS1 /E1 or a subset of DS0s (or DS1/E1 time-slots).VLAN = 200 SAP SAP SNP SAP Packet Traffic Packet Radio Multipoint Service User Port (UNI) GE/FE SAP SNP Network Port Port Port SAP GE/FE SNP TDM Pseudowire Supported Standards TDM Pseudowire supports the following standards:  SAToP – RFC 4553  CESoP – RFC 508629 TDM Pseudowire is compliant with the following encapsulations:  Ethernet VLAN (MEF-8)  IP/UDP (IETF)30  MPLS (MFA8 )31 Pseudowire Services A Pseudowire service is a user-defined. which is planned for a future release.

RTP timestamp usage details (for adaptive clock recovery).” The secondary tunnel is used whenever the primary path fails. the addressing is done through the TDM card’s MAC address. and MPLS (MFA8). there are a number of parameters at the PW Card level that must be configured properly to ensure proper operation:  Ethernet traffic port settings o Speed o Duplex o Auto-negotiation o Flow control  TDM card IP address and subnet mask  Clock distribution TDM Pseudowire and Synchronization Related topics:  Synchronization A key requirement of pseudowire technology is managing the synchronization of TDM signals. phn-3968 001v000 Page 5-116 . o For IP tunnels. PTP 820G’s TDM Pseudowire supports the following synchronization methods:  Absolute Reference Clock (Common Clock) – All DS1/E1 lines are synchronized to the system reference clock. the pseudowire services make use of the TDM card’s IP address. Jitter buffer – In milliseconds. Pseudowire Profile o A profile is a set of parameters that determine various operational settings of a PW service. but readable by users. o The following is a short explanation of the main parameters: Payload size – In terms of DS1/E1 frames per frame. which is fixed. PSN Tunnel Group o A PSN tunnel group is a grouping of two TDM tunnels. Payload suppression and transmission patterns in case of errors. In addition. For MEF-8 tunnels. one of which will carry the pseudowire service frames at any given time. which is user-configurable. MAC addresses are fixed per unit. UDP/IP.Chapter 5: Feature Description   TDM Services o A PSN tunnel is the means by which the frames containing the TDM information are sent and received through a PSN network. The other tunnel is designated as “secondary. LOPS detection thresholds. o One of the tunnels is designated as “primary. o Three types of PSN tunnels are supported: MEF-8 (Ethernet).” The primary tunnel carries the pseudowire frames in the absence of any failures. The type of tunnel to be used should match the relevant transport network. o A PSN tunnel group is used when path protection is required for a pseudowire service. A single profile can be used for any number of services.

 Differential Clock Recovery – A single common clock is given. Both data streams contain continuity messages (CCMs). This enables the TDM module to monitor the status of both paths without doubling the amount of data being sent over the network.Chapter 5: Feature Description TDM Services  Adaptive Clock Recovery – Clock information is included in the frames that contain the TDM data. 1:1 TDM Path protection requires the use of SOAM (CFM) at both end-point interfaces. 33 Differential Clock Recovery is planned for future release. protection for the traffic along the path can be achieved using 1+1HSB protection for the radios. but traffic flows to the destination via different paths. while each DS1 line has its independent clock referenced to this common clock. The extracted clock information is used for the reconversion to TDM. Only the data stream for the active path contains actual traffic. In order to achieve TDM Pseudowire path protection. 1:1 TDM Pseudowire and Path Protection For TDM pseudowire traffic redundancy. Each path has the same TDM interfaces end points. PTP 820G offers 1:1 TDM path protection. Note Alternatively. Because SOAM (CFM) is configured on the TDM module level. The TDM module sends two data streams to the CPU. different provisioning should be made for the Ethernet service corresponding to each of the two data streams. Adaptive Clock Recovery can provide very accurate synchronization. it is recommended to map the corresponding Ethernet services to MSTP instance number 63. The TDM module determines when a switchover is necessary based on the monitored network status. In order to do this. 1:1 TDM pseudowire path protection uses CFM (G. which protects the traffic along the path. 33  Loop Timing – The pseudowire output signal uses the clock of the incoming DS1 lines Timing will be independent for each DS1/E1 line. the TDM module can determine the status of the entire network path. Extra information may be located in an RTP header that can be used to correct frequency offsets. For TDM Pseudowire services. The clock information is extracted at the point where the frames are received and reconverted to TDM.8031) to monitor the network paths. which is meant for Traffic Engineering (ports are always forwarding) and to map the two different transport VLANs over two different paths. 1:1 TDM path protection enables the operator to define two separate network paths for a single TDM service. phn-3968 001v000 Page 5-117 . but requires low PDV. up to and including the card’s TDM interface.

phn-3968 001v000 Page 5-118 . with one second granularity. A single WTR time is configured for all the TDM trails in the system. initiates a revertive protection switch. if the protected path remains operational and available.Chapter 5: Feature Description TDM Services 1:1 TDM path protection can be configured to operate in revertive mode. once the protected path is operational and available without any alarms. the system waits the user-configured Wait to Restore (WTR) time and then. In revertive mode. TDM Pseudowire Performance Monitoring The following monitoring features are available for TDM Pseudowire services and interfaces: TDM PMs Standard PM measurements are provided for each configured service:  Number of frames transmitted  Number of frames received  Number of lost frames detected  Number of frames received out-of-sequence but successfully reordered  Number of transitions from normal state to LOPS (loss of frame state)  Number of malformed frames received  Number of frames dropped because the receive buffer exceeded the maximum allowed depth (jitter overruns)  Maximum deviation from the middle of the jitter buffer (maximum jitter buffer deviation)  Minimum jitter buffer usage registered during the prior one second (current minimum jitter buffer count)  Maximum jitter buffer usage registered during the prior one second (current maximum jitter buffer count) TDM Signal PMs34 PMs are computed at the TDM card and reported at 15-minute intervals. After switchover to the protecting path. the system monitors the availability of the protected path at all times.   PMs for the recovered DS1/E1: o Errored seconds o Severely errored seconds o Unavailable seconds PMs for the pseudowire Ethernet connection: o  34 Frame Error Ratio (FER) performance RFC 5604 PMs: o Lost frames o Reordered frames Support for TDM pseudowire signal PMs is planned for future release.

Chapter 5: Feature Description   o Buffer underruns o Misordered frames dropped o Malformed frames TDM Services PMs for incoming native DS1/E1 signal: o Errored seconds o Severely errored seconds o Unavailable seconds PMs for incoming SDH 155MHz signal: o Errored seconds o Severely errored seconds o Severely errored framing seconds o Coding Violations phn-3968 001v000 Page 5-119 .

Chapter 6: PTP 820G Management This chapter includes:  Management Overview  Automatic Network Topology Discovery with LLDP Protocol  Management Communication Channels and Protocols  Web-Based Element Management System (Web EMS)  Command Line Interface (CLI)  Configuration Management  Software Management  IPv6 Support  In-Band Management  Local Management  Alarms  External Alarms  NTP Support  UTC Support  System Security Features phn-3968 001v000 Page 6-1 .

which provides centralized operation and maintenance capability for the complete range of network elements in an PTP 820G system. and more. Cambium Networks provides an SNMP v1/v2c/v3 northbound interface on the PTP 820G. Cambium Networks offers the NetMaster network management system (NMS). PTP 820G and other Cambium Networks network elements can also be managed via Cambium’s PolyView NMS. Figure 91 Integrated PTP 820G Management Tools phn-3968 001v000 Page 6-2 . and maintenance tasks can be performed directly via the PTP 820G Command Line Interface (CLI). performance monitoring. management. remote diagnostics. In addition. configuration.Chapter 6: PTP 820G Management Management Overview Management Overview The Cambium Networks management solution is built on several layers of management:  NEL – Network Element-level CLI  EMS – HTTP web-based EMS  NMS and SML –PolyView/NetMaster platform Every PTP 820 network element includes an HTTP web-based element manager that enables the operator to perform element configuration. alarm reports. PTP 820G supports the Link Layer Discovery Protocol (LLDP). The CLI can be used to perform configuration operations for PTP 820G units. as well as to configure several PTP 820G units in a single batch command. In addition. To facilitate automated network topology discovery via NMS.

phn-3968 001v000 Page 6-3 .  Automatically detect a third-party switch or router neighboring the managed PTP 820 unit. Enabling LLDP on PTP 820 units enables the NMS to:  Automatically detect the PTP 820 unit neighboring the managed PTP 820 unit. a vendor-neutral layer 2 protocol that can be used by a station attached to a specific LAN segment to advertise its identity and capabilities and to receive identity and capacity information from physically adjacent layer 2 peers.Chapter 6: PTP 820G Management Automatic Network Topology Discovery with LLDP Protocol Automatic Network Topology Discovery with LLDP Protocol PTP 820G supports the Link Layer Discovery Protocol (LLDP).1AB – 2009 standard. This enables the NMS to quickly identify changes to the network topology. LLDP provides automatic network connectivity discovery by means of a port identity information exchange between each port and its peer. The port exchanges information with its peer and advertises this information to the NMS managing the unit. and determine the connectivity state between the PTP 820 unit and the switch or router. and determine the connectivity state between the two units. PTP 820G’s LLDP implementation is based on the IEEE 802.

Additionally. The unit IP address for management can be configured in either or both formats.Chapter 6: PTP 820G Management IPv6 Support IPv6 Support PTP 820G management communications can use both IPv4 and IPv6. other management communications can utilize either IPv4 or IPv6. This includes:  Software file downloads  Configuration file import and export  Trap forwarding  Unit information file export (used primarily for maintenance and troubleshooting) phn-3968 001v000 Page 6-4 .

The FTP server sends ACKs (and data) to client's data port. which may run locally or in a separate platform. The NMS can be accessed through its GUI interface application. it also has an SNMP-based northbound interface to communicate with other management systems.Chapter 6: PTP 820G Management Management Communication Channels and Protocols Management Communication Channels and Protocols Related Topics:  Secure Communication Channels Network Elements can be accessed locally via serial or Ethernet management interfaces. The application layer is indifferent to the access channel used.. Optional FTP server random port range can be limited according to need (i. phn-3968 001v000 Page 6-5 . according to the number of parallel configuration uploads).e. Table 24 Dedicated Management Ports Port number Protocol Frame structure Details 161 SNMP UDP Sends SNMP Requests to the network elements 162 Configurable SNMP (traps) UDP Sends SNMP traps forwarding (optional) 25 SMTP (mail) TCP Sends NMS reports and triggers by email (optional) 69 TFTP UDP Uploads/ downloads configuration files (optional) 80 HTTP TCP Manages devices 443 HTTPS TCP Manages devices (optional) From 21 port to any remote port (>1023) FTP Control Port TCP Downloads software and configuration files. or remotely through the standard Ethernet LAN. (FTP Server responds to client's control port) (optional) From Any port (>1023) to any remote port (>1023) FTP Data Port TCP Downloads software and configuration files.

Chapter 6: PTP 820G Management Management Communication Channels and Protocols All remote system management is carried out through standard IP communications. The communications protocol used depends on the management channel being accessed. As a baseline. Each NE behaves as a host with a single IP address. (FTP client initiates a connection) (optional) To any port (>1023) from any Port (>1023) FTP Data Port TCP Downloads software and configuration files. these are the protocols in use:  Standard HTTP for web-based management  Standard telnet for CLI-based management  The NMS uses a number of ports and protocols for different functions: Table 25 NMS Server Receiving Data Ports Port number Protocol Frame structure Details 162 UDP Configurable SNMP (traps) Receive SNMP traps from network elements 4001 Propriety TCP CeraMap Server 69 TFTP UDP Downloads software and files (optional) 21 FTP Control Port TCP Downloads software and configuration files.(FTP Client initiates data connection to random port specified by server) (optional) Configurable FTP Server random port range can be limited according to needed configuration (number of parallel configuration uploads). 9205 Propriety TCP User Actions Logger server (optional) Propriety TCP CeraView Proxy (optional) Configurable 9207 Configurable Table 26 Web Sending Data Ports Port number Protocol Frame structure Details 80 HTTP TCP Manages device 443 HTTPS TCP Manages device (optional) phn-3968 001v000 Page 6-6 .

However.  User Management – Enables you to define users and user profiles. The Web EMS shows the actual unit configuration and provides easy access to any interface in the IDU.  Performance Monitoring – Enables you to view and clear performance monitoring values and counters. Most system configurations and statuses are available via the Web EMS. software updates. phn-3968 001v000 Page 6-7 . including:  Configuration Management – Enables you to view and define configuration data for the PTP 820G system.  Diagnostics and Maintenance – Enables you to define and perform loopback tests. A Web-Based EMS connection to the PTP 820G can be opened using an HTTP Browser (Explorer or Mozilla Firefox).  Security Configuration – Enables you to configure PTP 820G security features.Chapter 6: PTP 820G Management Management Communication Channels and Protocols Table 27 Web Receiving Data Ports Port number Protocol Frame structure Details 21 FTP TCP Downloads software files (optional) Data port FTP TCP Downloads software files (optional) Table 28 Additional Management Ports for PTP 820G Port number Protocol Frame structure Details 23 telnet TCP Remote CLI access (optional) 22 SSH TCP Secure remote CLI access (optional) Web-Based Element Management System (Web EMS) The PTP 820G Element Management System (Web EMS) is an HTTP web-based element manager that enables the operator to perform configuration operations and obtain statistical and performance information related to the system.  Fault Monitoring – Enables you to view active alarms. The Web EMS uses a graphical interface. some advanced configuration options are only available via CLI. and IDU-RFU interface monitoring.

Data: 8 bits. or via telnet. All parameter configurations can be performed via CLI.Chapter 6: PTP 820G Management Command Line Interface (CLI) Command Line Interface (CLI) A CLI connection to the PTP 820G can be opened via terminal (serial COM. phn-3968 001v000 Page 6-8 . Stop: 1 bit. Flow-Control: None). The Terminal format should be VT-100 with a screen definition of 80 columns X 24 rows. speed: 115200.

By default. security settings are included. these restore points are referred to as “file numbers. Note The option to enable or disable import and export of security parameters is planned for future release. a user may want to use one restore point to keep a last good configuration. such as users and user profiles. phn-3968 001v000 Page 6-9 . Each restore point contains a single configuration file.Chapter 6: PTP 820G Management Configuration Management Configuration Management The system configuration file consists of a set of all the configurable system parameters and their current values. Any of the restore points can be used to apply a configuration file to the system. System configuration files consist of a zip file that contains three components:  A binary configuration file which is used by the system to restore the configuration. The user can determine whether or not to include security-related settings. This file is executed by the system after restoring the configuration.35 The system provides three restore points to manage different configuration files. in the exported configuration file. and the third to store the current configuration.  A text file which enables users to examine the system configuration in a readable format.” For example. The file includes the value of all system parameters at the time of creation of the backup file. This enables you to copy the system configuration to multiple PTP 820G units.  An additional text file which enables users to write CLI scripts in order to make desired changes in the backed-up configuration. Note In the Web EMS. 35 The option to edit the backup configuration is planned for future release. another to import changes from an external server. Files can be added to restore points by creating backups of the current system state or by importing them from an external server. PTP 820G configuration files can be imported and exported.

A timer can be used to perform the installation after a defined time interval.  Installation – The files are installed in the appropriate modules and components of the PTP 820G. PTP 820G software and firmware releases are provided in a single bundle that includes software and firmware for all components supported by the system. the user initiates the installation. 36 Installation timer is planned for future release. The system also compares the files in the bundle to the files currently installed in the PTP 820G and its components.Chapter 6: PTP 820G Management Software Management Software Management The PTP 820G software installation and upgrade process includes the following steps:  Download – The files required for the installation or upgrade are downloaded from a remote server. When the user downloads a software bundle. After the software download is complete. or HTTPS. phn-3968 001v000 Page 6-10 . When the user restarts the PTP 820G after a software upgrade. including RFUs. Backup Software Version Note Backup software version support is planned for future release. you must perform the upgrade manually. the system verifies the validity of the bundle. including files that are already installed. so that only files that differ between the new version bundle and the current version in the system are actually downloaded.36 Although RFU software is included in the standard installation bundle. HTTP. the system performs an automatic reset after the installation. A message is displayed to the user for each file that is actually downloaded.  Reset – The PTP 820G is restarted in order to boot the new software and firmware versions. SFTP. This enables users to manage IDU and RFU software versions separately. all files in the bundle may be downloaded. To upgrade the software in an RFU. Software bundles can be downloaded via FTP. When an installation timer is used. only the components whose software or firmware was actually upgraded are restarted. Note When downloading an older version. the current software version is not automatically updated when an installation is performed. per radio carrier.

Chapter 6: PTP 820G Management

Software Management

PTP 820G maintains a backup copy of the software bundle. In the event that the working software
version cannot be found, or the operating system fails to start properly, the system automatically
boots from the backup version, and the previously active version becomes the backup version.
Users can also update the backup version manually. The Web EMS includes a field that indicates
whether or not the active and backup software versions are identical.

In-Band Management
PTP 820G can optionally be managed In-Band, via its radio and Ethernet interfaces. This method of
management eliminates the need for a dedicated management interface. For more information,
see Management Service (MNG) on page 5-41.

Local Management
PTP 820G provides two FE interfaces for local management. The two management interfaces give
users the ability not only to manage the PTP 820G directly via a laptop or PC, but also to manage
other devices via the second management port of the PTP 820G.
For additional information:

Ethernet Management Interfaces

phn-3968 001v000
Page 6-11

Chapter 6: PTP 820G Management

Alarms

Alarms
Configurable RSL Threshold Alarms and Traps
Users can configure alarm and trap generation in the event of RSL degradation beneath a userdefined threshold. An alarm and trap are generated if the RSL remains below the defined threshold
for at least five seconds. The alarm is automatically cleared if the RSL subsequently remains above
the threshold for at least five seconds.
The RSL threshold is based on the nominal RSL value minus the RSL degradation margin. The
user defines both the nominal RSL value and the RSL degradation margin.

Alarms Editing
Users can change the description text (by appending extra text to the existing description) or the
severity of any alarm in the system. This feature is available through CLI only.
This is performed as follows:

Each alarm in the system is identified by a unique name (see separate list of system alarms
and events).

The user can perform the following operations on any alarm:

o

View current description and severity

o

Define the text to be appended to the description and/or severity

o

Return the alarm to its default values

The user can also return all alarms and events to their default values.

phn-3968 001v000
Page 6-12

Chapter 6: PTP 820G Management

External Alarms

External Alarms
PTP 820G includes a DB9 dry contact external alarms interface. The external alarms interface
supports five input alarms. For each alarm input, the user can configure the following:
1

Alarm administration (On or Off)

2

Alarm text

3

Alarm severity

Alarm severity can be configured to:
1

Indeterminate

2

Critical

3

Major

4

Minor

5

Warning

phn-3968 001v000
Page 6-13

Chapter 6: PTP 820G Management

NTP Support

NTP Support
Related topics:

Synchronization

PTP 820G supports Network Time Protocol (NTP). NTP distributes Coordinated Universal Time
(UTC) throughout the system, using a jitter buffer to neutralize the effects of variable latency.
PTP 820G supports NTPv3 and NTPv4. NTPv4 provides interoperability with NTPv3 and with SNTP.

phn-3968 001v000
Page 6-14

phn-3968 001v000 Page 6-15 . Every PTP 820G unit holds the UTC offset and daylight savings time information for the location of the unit.Chapter 6: PTP 820G Management UTC Support UTC Support PTP 820G uses the Coordinated Universal Time (UTC) standard for time and date configuration. UTC is a more updated and accurate method of date coordination than the earlier date standard. Greenwich Mean Time (GMT). Each management unit presenting the information (CLI and Web EMS) uses its own UTC offset to present the information in the correct time.

System security is based on making attacks difficult (in the sense that the effort required to carry them out is not worth the possible gain) by putting technical and operational barriers in every layer along the way. up to every data link in the network. it is imperative to protect it from all potential threats. through the authentication process. both internal (misuse by operators and administrators) and external (attacks originating outside the network). from the access outside the network.Chapter 6: PTP 820G Management System Security Features System Security Features To guarantee proper performance and availability of a network as well as the data integrity of the traffic. phn-3968 001v000 Page 6-16 .

requirements refer to both network elements and the NMS. In addition. it is necessary to protect the communication channels’ contents end to end. However. phn-3968 001v000 Page 6-17 . no single layer protection provides a complete solution to threats. This can greatly help deal with all sorts of DoS attacks. While these features are implemented in Cambium Networks equipment. it is the combination of them that provides adequate protection to the network. In most cases. thus providing standard secure means to manage the network. They provide defense at any point (including public networks and radio aggregation networks) of communications. These defenses are based on existing and proven cryptographic techniques and libraries. inside Cambium Networks networking equipment it is possible to control physical channels used for management. The layered security concept is presented in the following figure. Unless stated otherwise. with minimal impact on usability. Each layer presents the security features and the threats addressed by it. it is the responsibility of the operator to have the proper capabilities in any external devices used to manage the network. Figure 92 Security Solution Architecture Concept Defenses in Management Communication Channels Since network equipment can be managed from any location.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept Cambium’s Layered Security Concept Each layer protects against one or more threats.

The system parameters are divided into the following functional groups:  Security  Management  Radio  TDM  Ethernet  Synchronization A user profile defines the permitted access level per functionality group. Attack types addressed  Tempering with management flows  Management traffic analysis  Unauthorized software installation  Attacks on protocols (by providing secrecy and integrity to messages)  Traffic interfaces eavesdropping (by making it harder to change configuration)  DoS through flooding Defenses in User and System Authentication Procedures User Configuration and User Profiles User configuration is based on the Role-Based Access Control (RBAC) model.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept Operators can use secure channels instead or in addition to the existing management channels:  SNMPv3 for all SNMP-based protocols for both NEs and NMS  HTTPS for access to the NE’s web server  SSH-2 for all CLI access SFTP for all software and configuration download between NMS and NEs All protocols run with secure settings using strong encryption techniques. Users are assigned to particular roles. In the network elements. Users are allowed to disable all insecure channels. and defines the management protocols (access channels) that can be used to access the system by users to whom the user profile is assigned. and algorithms used must meet modern and client standards. the access level is defined separately for read and write operations. in particular. and through those role assignments acquire the permissions to perform particular system functions. the bandwidth of physical channels transporting management communications is limited to the appropriate magnitude. According to the RBAC model. Up to 50 user profiles can be configured. In the PTP 820G GUI. channels carrying management frames to the CPU. these roles are called user profiles. For each functionality group. The following access levels can be assigned: phn-3968 001v000 Page 6-18 . permissions to perform certain operations are assigned to specific roles. Unencrypted modes are not allowed. Each profile contains a set of privilege levels per functionality group.

upper-case characters. o Password must include at least three of the following categories: lower-case characters. NEs and NMS software provide the tools required for operators to enforce their policy and create certificates according to their established processes.  Users can be prompted to change passwords after a configurable amount of time (password aging). passwords must comply with the following rules: o Password must be at least eight characters long. issuing its own certificates vs. as well as parameters that have a significant impact on the system as a whole. It is enabled by default. phn-3968 001v000 Page 6-19 . o The password cannot have been used within the user’s previous five passwords. Users may choose to use this feature or not for all secure communication channels.  Users can be blocked for a configurable time period after a configurable number of unsuccessful login attempts. using an external CA or allowing the NMS system to be a CA).  Normal – The user has access to parameters that require basic knowledge about the functional group. Remote Authentication Note Remote authorization is planned for future release. upper-case letters used as the first character and digits used as the last character of a password are not counted. When password strength enforcement is enabled.  Advance – The user has access to parameters that require advanced knowledge about the functional group. o When calculating the number of character categories.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept  None – No access to this functional group. Server authentication capabilities are provided. such as restoring the configuration to factory default settings. User Identification PTP 820G supports the following user identification features:  Configurable inactivity time-out for automatically closing unused management channels  Optional password strength enforcement. digits. and special characters. Certificate-based strong standard encryption techniques are used for remote authentication. Since different operators may have different certificate-based authentication policies (for example.  Users can be configured to expire at a certain date  Mandatory change of password at first time login can be enabled and disabled upon user configuration.

a user attempting to log into the system from any access channel (CLI.specific privilege levels. NMS) is not authenticated locally. PTP 820G supports RADIUS server and provides a RADIUS client for authentication and authorization. Otherwise. Instead. If the RADIUS server is unavailable. RADIUS login works as follows:   If the RADIUS server is reachable. Note Local login authentication is provided in order to enable users to manage the system in the event that RADIUS server is unavailable. the user will be unable to log in. the PTP 820G will attempt to authenticate the user locally. This means that when a user is authorized via RADIUS. the user will be unable to login locally in case the RADIUS server is unavailable. the access channel limitations defined per user profile are not applicable. WEB.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept RADIUS Support Note Support for RADIUS is planned for future release. This requires previous definition of users in the system. or notifies the PTP 820G that the user was rejected. When RADIUS is enabled. the user will log in with the appropriate privilege and will continue to operate normally. the user can access the unit via any available access channel. RADIUS uses the same user attributes and privileges defined for the user locally. the vendor-specific field is used. In order to support PTP 820G . RADIUS can be enabled or disabled. o If rejected. the user’s credentials are sent to a centralized standard RADIUS server which indicates to the PTP 820G whether the user is known. and which privilege is to be given to the user. The following RADIUS servers are supported:  FreeRADIUS  RADIUS on Windows Server (IAS)  o Windows Server 2008 o Windows Server 2003 Cisco ACS phn-3968 001v000 Page 6-20 . according to the existing list of defined users. Note When using RADIUS for user authentication and authorization. the system expects authorization to be received from the server: o The server sends the appropriate user privilege to the PTP 820G. The RADIUS protocol provides centralized user management services. If the user is only defined in the RADIUS server.

This value cannot be changed. Server authentication is based on PTP 820G’s public key. which is enabled by default. hmac-sha1.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept Secure Communication Channels PTP 820G supports a variety of standard encryption protocols and algorithms. SSH protocol can be used as a secured alternative to Telnet.  Supported Encryptions: aes128-cbc. The number of failed authentication attempts is not limited. HTTPS combines the Hypertext Transfer protocol with the SSL/TLS protocol to provide encrypted communication and secure identification of a network web server. Admin users can choose whether to disable Telnet protocol.  RSA and DSA key types are supported. SFTP (Secure FTP) SFTP can be used for the following operations:  Configuration upload and download. 3des-cbc. aes192-ctr. aes256-cbc. hmac-md5-96'  The server authenticates the user based on user name and password.  Uploading unit information  Uploading a public key  Downloading certificate files  Downloading software phn-3968 001v000 Page 6-21 . arcfour256. cast128-cbc. hmac-sha1-96. In PTP 820G:  SSHv2 is supported. Supported MAC: hmac-md5. aes256-ctr. hmac-ripemd160. HTTPS (Hypertext Transfer Protocol Secure) Note HTTPS support is planned for future release. blowfish-cbc. key length = 160 bit). arcfour128.  The server timeout for authentication is 10 minutes. aes128-ctr. SSH (Secured Shell) Note SSH support is planned for future release.  SSH protocol will always be operational. PTP 820G enables administrators to configure secure access via HTTPS protocol. aes192-cbc. as described in the following sections.  MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits. arcfour.

and country. Certificate authority (CA) will use the CSR to create the desired certificate for the NE. and v3.The state/region where the organization is located. the user will be asked to input the following parameters that should be known to the operator who applies the command:  Common name – The identify name of the element in the network (e. While creating the CSR file. SNMP PTP 820G supports SNMP v1. PTP 820G supports the following MIBs:  RFC-1213 (MIB II)  RMON MIB  Cambium Networks (proprietary) MIB.  City/Locality . For additional information:  PTP 820G MIB Reference phn-3968 001v000 Page 6-22 .  Email address . Users are allowed to set community strings for access to IDUs.  Organizational Unit . the IP address). respectively. a Certificate Signing Request (CSR) file should be created by the NE.The city where the organization is located.The division of the organization handling the certificate. The CSR contains information that will be included in the NE's certificate such as the organization name.  State/County/Region . The common name can be a network IP or the FQDN of the element. V2c.  Organization – The legal name of the organization. common name (domain name). The default community string in NMS and the SNMP agent in the embedded SW are disabled.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept Creation of Certificate Signing Request (CSR) File Note CSR support is planned for future release. Access to all IDUs in a node is provided by making use of the community and context fields in SNMPv1 and SNMPv2c/SNMPv3.g. It also contains the public key that will be included in the certificate.  Country .An email address used to contact the organization. In order to create a digital certificate for the NE. locality..The two-letter ISO code for the country where the organization is location.

The security log records:  Changes in security configuration o Carrying out “security configuration copy to mate” phn-3968 001v000 Page 6-23 . or modify the log file. o Users can load trusted public keys for this purpose.  The contents of the log file are cryptographically protected and digitally signed. SSH  The CLI interface supports SSH-2 o Users of type of “administrator” or above can enable or disable SSH. delete. an alarm will be raised.  The log can only be read by users with "admin" or above privilege. The security log file has the following attributes:  The file is of a “cyclic” nature (fixed size.  In the event of an attempt to modify the file. Security Log The security log is an internal system file which records all changes performed to any security feature. Non-SSL protocols using asymmetric encryption.509 certificatesbased server authentication. the user must upload the log to his or her server. o Load a server RSA key pair that was generated externally for use by protocols making use of SSL.Chapter 6: PTP 820G Management Cambium’s Layered Security Concept Server Authentication (SSL / SLLv3) Note SSL and SLLv3 support is planned for future release.  Users with type of “administrator” or above can perform the following server (IDU) authentication operations for certificates handling:  o Generate server key pairs (private + public) o Export public key (as a file to a user-specified address) o Install third-party certificates o The Admin user is responsible for obtaining a valid certificate.  All protocols making use of SSL (such as HTTPS) use SLLv3 and support X. Note In order to read the security log.  Users may not overwrite. newest events overwrite oldest). can make use of public-key based authentication. such as SSH and SFTP. as well as all security related events.

Chapter 6: PTP 820G Management

Cambium’s Layered Security Concept

o

Management channels time-out

o

Password aging time

o

Number of unsuccessful login attempts for user suspension

o

Warning banner change

o

Adding/deleting of users

o

Password changed

o

SNMP enable/disable

o

SNMP version used (v1/v3) change

o

SNMPv3 parameters change

Security mode
Authentication algorithm
User
Password
o

SNMPv1 parameters change

Read community
Write community
Trap community for any manager
o

HTTP/HTTPS change

o

FTP/SFTP change

o

Telnet and web interface enable/disable

o

FTP enable/disable

o

Loading certificates

o

RADIUS server

o

Radius enable/disable

o

Remote logging enable/disable (for security and configuration logs)

o

Syslog server address change (for security and configuration logs)

o

System clock change

o

NTP enable/disable

Security events

Successful and unsuccessful login attempts

N consecutive unsuccessful login attempts (blocking)

Configuration change failure due to insufficient permissions

SNMPv3/PV authentication failures

User logout

User account expired

For each recorded event the following information is available:

User ID

Communication channel (WEB, terminal, telnet/SSH, SNMP, NMS, etc.)

phn-3968 001v000
Page 6-24

Chapter 6: PTP 820G Management

IP address, if applicable

Date and time

Cambium’s Layered Security Concept

phn-3968 001v000
Page 6-25

Chapter 7: Standards and Certifications
This chapter includes:

Supported Ethernet Standards

Supported TDM Pseudowire Encapsulations

Standards Compliance

Network Management, Diagnostics, Status, and Alarms

phn-3968 001v000
Page 7-1

Chapter 7: Standards and Certifications

Supported Ethernet Standards

Supported Ethernet Standards
Table 29 Supported Ethernet Standards
Standard

Description

802.3

10base-T

802.3u

100base-T

802.3ab

1000base-T

802.3z

1000base-X

802.3ac

Ethernet VLANs

802.1Q

Virtual LAN (VLAN)

802.1p

Class of service

802.1ad

Provider bridges (QinQ)

802.3ad

Link aggregation

802.1ag

Connectivity Fault Management (CFM)37

Auto MDI/MDIX for 1000baseT

37

RFC 1349

IPv4 TOS

RFC 2474

IPv4 DSCP

RFC 2460

IPv6 Traffic Classes

Planned for future release.

phn-3968 001v000
Page 7-2

IP/UDP (IETF) Layer 3 encapsulation over Ethernet Planned for future release. phn-3968 001v000 Page 7-3 .Chapter 7: Standards and Certifications Supported TDM Pseudowire Encapsulations Supported TDM Pseudowire Encapsulations Table 30 Supported TDM Pseudowire Encapsulations Certification Description Availability VLAN (MEF-8) Circuit Emulation Services over native Ethernet frames Available. MPLS (MFA8) MPLS encapsulation over Ethernet Planned for future release.

2 Specification: ETSI EN 300 019-2-1 Specification T 1.2 Operation – RFU Operating: ETSI EN 300 019-1-4 Class 4.3 Specification: ETSI EN 300 019-2-2 Specification T 2.Chapter 7: Standards and Certifications Standards Compliance Standards Compliance Table 31 Standards Compliancc Specification Standard EMC EN 301 489-4 Safety IEC 60950-1 Ingress Protection IEC 60529 IP56 Operation – IDU Operating: ETSI EN 300 019-1-3 Class 3.2 Transportation Classification: ETSI EN 300 019-1-2 Class 2.1 Storage Classification: ETSI EN 300 019-1-1 Class 1.3 phn-3968 001v000 Page 7-4 .

39 HTTPS support is planned for future release. CLI Management Channels & Protocols HTTP/HTTPS39 Telnet/SSH-240 FTP/SFTP41 Authentication. Diagnostics.Chapter 7: Standards and Certifications Network Management. 40 SSH support is planned for future release. Authorization & Accounting User access control X-509 Certificate Management Interface Dedicated Ethernet interfaces or in-band in traffic ports In-Band Management Support dedicated VLAN for management TMN The NMS functions are in accordance with ITU-T recommendations for TMN RSL Indication Power reading (dBm) available at RFU42. and NMS Performance Monitoring Integral with onboard memory per ITU-T G.826/G. Status. Status and alarms Network Management System NetMaster NMS38 / PolyView NMS Interface protocol SNMPv1/v2c/v3 XML over HTTP/HTTPS toward the NMS Element Management Web based EMS. 41 SFTP support is planned for future release. and Alarms Network Management. Diagnostics. phn-3968 001v000 Page 7-5 . and Alarms Table 32 Network management. Diagnostics. 42 Note that the voltage measured at the BNC port is not accurate and should be used only as an aid.828 38 PolyView NMS is also supported. Status.

Specifcations Chapter 8: Specifcations This chapter includes:     Radio Specifications o General Specifications o Capacity Specifications o Transmit Power Specifications (dBm) o Receiver Threshold (RSL) Specifications (dBm @ BER = 10-6) o Frequency Bands Network Specifications o Ethernet Latency Specifications o Ethernet Specifications o Synchronization Specifications Power Specifications o Power Input Specifications o Power Consumption Specifications Physical and Electrical Specifications o Mediation Device Losses o TDM Specifications o Supported Antenna Types o Error! Reference source not found. phn-3968 001v000 Page 8-1 . o Mechanical Specifications o Environmental Specifications Related Topics:  Standards and Certifications Note All specifications are subject to change without prior notification.

5 350.7 490. 250.5 800. 700 Standards ANSI Frequency Stability +0.2-23. 240.9. 168. 728 18 17. 208.7-19.2-26. 168.75-13. 311. 6. 300.350.1-7. 300. 245. 161. 160.001% Frequency Source Synthesizer RF Channel Selection Via EMS/NMS Tx Range (Manual/ATPC) Up to 20dB dynamic range phn-3968 001v000 Page 8-2 . 490.7 1010.3 266 15 14.7-8.65 1008.0-10. 170. 182. 1232 26 24. 500. 1260.35-29.35 315.4-15.6H 5.45. 119. 1008 32 31. 1560 23 21.Chapter 8: Specifcations Radio Specifications Radio Specifications General Specifications Note The specifications in this section refer to a PTP 820G system using an RFU-C General Radio Specification for ANSI Table 33 General Radio Specifications for ANSI Frequency (GHz) Operating Frequency Range (GHz) Tx/Rx Spacing (MHz) 6L. 340.8 7. 420. 475. 530 13 12. 266. 1008. 530 10 10.0 700 38 37-40 1000. 7. 450.7-11.0-37.7 91.8-33.310. 266.4 812 36 36. 500 7. 1008 28 27. 550 11 10.04.5 154. 1120. 1200. 196.4-7.85-6. 644.312. 490. 520.1 252.

310.0-10. 160.2-23.8-33. 644. 266. 250. 1260.7 1010.04. 500.312. 1008 32 31. 475. 420. 1560 23 21. 1200. 119. 1232 26 24. 161. 530 10 10.1 252.85-6. 340. 520. 1008. 490.2-26.65 1008. 450. 300.0 700 38 37-40 1000. 240. 728 18 17.45.4-15. 170.8 7.6H 5.5 800.4-7.7-11. 550 11 10.001% Frequency Source Synthesizer RF Channel Selection Via EMS/NMS Tx Range (Manual/ATPC) Up to 20dB dynamic range phn-3968 001v000 Page 8-3 .7-8. 300.Chapter 8: Specifcations Radio Specifications General Radio Specification for ETSI Table 34 General Radio Specifications for ETSI Frequency (GHz) Operating Frequency Range (GHz) Tx/Rx Spacing (MHz) 6L. 6. 208. 196.7 91. 245. 182.35 315.5 350.5 154. 1008 28 27. 168. 500 7.75-13. 7. 311.9. 490. 1120. 530 13 12.35-29. 168.1-7.350.7 490. 700 Standards ETSI Frequency Stability +0.4 812 36 36.3 266 15 14. 266.7-19.0-37.

Capacity for IPv6 encapsulation is higher.25 Header De-Duplication is planned for future release.18 50.98 24.37 8.24 2 16 QAM 50 8 17.79-26. Layer-2 Header De-Duplication.24 52.15-40.99 41.39-114.7-161.52 12.62-14.15-141.19-77. with ranges given for no Header De-Duplication.17-27.73 49.34 5 128 QAM 50 15 35.95 44.4 6 256 QAM 50 17 40.36 9 1024 QAM (Light FEC) 50 21 50.29-50.45 18.47-53. the capacity figures are for LTE packets encapsulated inside GTP tunnels with IPv4/UDP encapsulation and double VLAN tagging (QinQ).36 25. For LTE-Optimized Header De-Duplication.05-131. RFU-C units support modulations of up to 256 QAM and higher.57-57.07 4 64 QAM 50 12 29.55 8.31-46.9-33. A Capacity Calculator tool is available for different encapsulations and flow types. These figures are valid for RFU-Ce.Chapter 8: Specifcations Radio Specifications Capacity Specifications Each table in this section includes ranges of capacity specifications according to frame size.06-20.23 8 1024 QAM (Strong FEC) 50 19 47.14 46.6 35.43 Note Ethernet capacity depends on average frame size.92 18. contact your Cambium Networks representative.88-40.82-57. 7 MHz Channel Bandwidth (No XPIC) Table 35 Capacity 7 MHz Channel Bandwidth (no XPIC) Profile 43 Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 10 4 8.29 13.76 43.59 3 32 QAM 50 10 23.72 7 512 QAM 50 18 43. and LTE-optimized Header De-Duplication.16-95.1 47.91 1 8 PSK 50 5 12.44-9.46-151.67 29. phn-3968 001v000 Page 8-4 .85 31. For exact capacity specifications for modulations beyond 256 QAM using standard RFU models.61 37.

65 65.38-190.23 81.99-59.97 4 64 QAM 50 26 64.65 1 8 PSK 50 12 28.39 59.03 112.74 4 64 QAM 150 53 131.93 9 1024 QAM (Light FEC) 150 45 110.53 111.19 89.33-21.2 28 MHz Channel Bandwidth (No XPIC) Table 37 Capacity 28 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 16 39.46-334.61 7 512 QAM 100 40 98.76 67.41-316.39-126.64-127.55 5 128 QAM 150 64 158.64 39.8 132.76180.87-92.08-355.75 93.33 103.42-423.9 109.95-45.85-67.33 41.7 3 32 QAM 50 22 52.94 6 256 QAM 100 36 89.15-61.04-118.09 78.8-122.97 107.05 3 32 QAM 100 43 106.73-127.16-73.83150.4 1 8 PSK 50 24 59.1 116.2-33.05 30.46 99.31-261.23-112.77 5 128 QAM 100 32 78.41 8 1024 QAM (Strong FEC) 150 42 104.23 41.01-250.74 40.Chapter 8: Specifcations Radio Specifications 14 MHz Channel Bandwidth (No XPIC) Table 36 Capacity 14 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 8 19.9-207.68 85.09 82.53 159.89 20.76 62.99 55.34-343.45 phn-3968 001v000 Page 8-5 .37 138.69-89.1 2 16 QAM 50 16 39.49-509.22 105.88-101.97 29.18 19.05-45.43-93.86 166.86 2 16 QAM 100 33 81.22-168.58 52.67-286.

17 104.85202.33 177.46 5 128 QAM 150 63 155.77227.47 186.82-186.56 4 64 QAM 150 52 128.85 109.29239.99 225 85 209.07 156.57 181.83-412.17 40.31 83.64 10 2048 QAM 250 97 241.86-498.22 200.38 129.38146.43-775.74 222.66-124.92 58.66 211.53-680.74224.74 220.12-633.54241.12 2 16 QAM 100 32 79.21 198.92 236.37-66.98206.74 6 7 8 256 QAM 512 QAM 1024 QAM (Strong FEC) 200 72 200 80 197.28176.23-640.28 225 85 211.14-254.19-673.96 226.Chapter 8: Specifcations Profile 6 7 Modulation 256 QAM 512 QAM Radio Specifications Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 200 73 180.91 253.89 213.41-334.47 8 1024 QAM (Strong FEC) 9 1024 QAM (Light FEC) 225 90 224.28 209.98118.47 178.19 phn-3968 001v000 Page 8-6 .71256.77 134.91 162.31 243.16 79.01 189.31 207.02-44.26-722.3 28 MHz Channel Bandwidth with XPIC Table 38 Capacity 28 MHz Channel Bandwidth with XPIC Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 16 38.39-570.42 1 8 PSK 50 24 57.22 200 80 199.19-275.72 39.78-90.07 60.38 3 32 QAM 100 42 104.64-580.

44 250 97 30 MHz Channel Bandwidth (No XPIC) Table 39 Capacity 30 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 23 42.77-764.19 61.3-256.91 216.42-775.66-69.04-364.63 2 16 QAM 100 46 86.26-196.31 241.35 114.58 140.56 226.67271.67 176.55 168.15-135.45-276.32 249.Chapter 8: Specifcations Profile 9 10 Modulation 1024 QAM (Light FEC) 2048 QAM Radio Specifications Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 225 90 222.96 44.24 146.04 42.18275.51234.81 64.25-661.25 90.26 6 7 256 QAM 512 QAM phn-3968 001v000 Page 8-7 .23129.01 169.67 5 128 QAM 150 89 200 103 193.91 207.69 8 1024 QAM (Strong FEC) 225 119 224.12 86.79-98.32 4 64 QAM 150 74 139.94 233.19 235.3 243.32253.59-448.84-721.76 119.59 224.14 194.26 3 32 QAM 100 60 113.36-47.09 1 8 PSK 50 33 61.9 202.67159.82 239.64220.63 9 1024 QAM (Light FEC) 250 126 237.44-539.77-715.29 253.31191.84-620.34 200 109 205.

53 83.28 3 32 QAM 150 81 148.53-197.16-132.42-46.61-528.38 200 109 209.29-169 155.63-187.35 165.71 phn-3968 001v000 Page 8-8 .09 58.73-63.14 149.54-671.16 86.45 61.56 197.1 64.95 40 MHz Channel Bandwidth with XPIC Table 41 Capacity 40 MHz Channel Bandwidth with XPIC Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 31 55.78253.1 41.08 116.07-361.68-265.07-355.54-95.15 142.36207.76 233.52-604.08 1 8 PSK 50 33 61.26 118.72 1 8 PSK 100 45 82.38126.92-70.1-269.58-476.58 3 32 QAM 100 60 110.17 200 103 188.06155.3-128.52 111.22 2 16 QAM 100 62 112.09-584.16 5 128 QAM 150 89 164.46 2 16 QAM 100 46 83.21-713.05 4 64 QAM 200 99 181.48 219.83-437.42 113.75 237.59-757.58 247.95 183.58 191.Chapter 8: Specifcations Radio Specifications 30 MHz Channel Bandwidth with XPIC Table 40 Capacity 30 MHz Channel Bandwidth with XPIC Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 23 41.07 189.17-94.7 88.04 210.89 43.05 223.66238.89 84.5 172.04 4 64 QAM 150 74 136 137.54214.58268.08-177.33 9 1024 QAM (Light FEC) 250 126 235.3 55.59 6 7 256 QAM 512 QAM 8 1024 QAM (Strong FEC) 225 119 222.

06 221.33 317.67 116.95 238.43 245.49339.88-833.03 312.8-270.86-761.61173.2 188.37-64.32277.72 255.22 300 160 302.01 phn-3968 001v000 Page 8-9 .82 3 32 QAM 150 81 152.59-96.16 275.82-727.6-601.94 2 16 QAM 100 62 115.6-833.17 299.06-833.96 121.69 250 129 243.92 57.56 318.1-833.92 1 8 PSK 100 45 84.56 196.41-833.2-258.66 268.44 228.33 6 7 8 256 QAM 512 QAM 1024 QAM (Strong FEC) 300 141 266.33 7 512 QAM 300 141 160 1024 QAM (Strong FEC) 300 8 1024 QAM (Light FEC) 350 9 170 40 MHz Channel Bandwidth (No XPIC) Table 42 Capacity 40 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 50 31 56.78-182.Chapter 8: Specifcations Profile Modulation Radio Specifications Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 5 128 QAM 200 120 220.74304.28 280.57131.28311.34 237.57 5 128 QAM 200 120 226.66-782.72 160.93 85.48-371.42 153.05 231.33 297.01-360 331.33 315.76345.89 4 64 QAM 200 99 187.9 89.11-707.2-272.17 6 256 QAM 250 129 236.47 273.77251.94 59.65213.63 286.41 304.33 248.08-489.

26 4 64 QAM 250 125 236.33 6 7 256 QAM 512 QAM 8 1024 QAM (Strong FEC) 9 1024 QAM (Light FEC) 350 174 327.33 400 204 386.26-468.62366.79 238.07166.96 5 128 QAM 300 151 276.49315.41 329.65 413.26 290.85209.44 373.42 184.97 192.12 323.25-833.45 3 32 QAM 200 102 183.56 108.33 400 216 phn-3968 001v000 Page 8-10 .91 1 8 PSK 100 56 107.91-79.Chapter 8: Specifcations Profile 9 Modulation 1024 QAM (Light FEC) Radio Specifications Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 350 170 321.33 343.33 50 MHz Channel Bandwidth (No XPIC) Table 43 Capacity 50 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 100 39 69.1 406.15 248.85-833.49 431.67 2 16 QAM 150 78 145.23-833.34 278.65-441.14 72.69-760.37 69.95373.06-833.15405.64-589.27-833.97-345.72 112.64270.35 337.33 410.85-222.22-833.38 358.49 153.52 350 187 355.84468.4-122.93 147.64 389.

02 420.33 400 161 400.6 228.42 2 16 QAM 150 67 165.25-833.43572.56 485.17 526.07-92.69 127.43 466.4-188.52-261.98 371.92304.04 400 148 368.6 325.84 268.72-833.33 5 6 7 128 QAM 256 QAM 512 QAM 300 130 322.53 505.29-698.33 10 2048 QAM 500 201 phn-3968 001v000 Page 8-11 .99 4 64 QAM 300 107 266.43 280.09497.33 8 1024 QAM (Strong FEC) 450 175 435.66-833.07247.9 1 8 PSK 150 49 121.8-833.42-389.9 85.27138.03527.55 3 32 QAM 225 88 217.11 166.85420.Chapter 8: Specifcations Radio Specifications 56 MHz Channel Bandwidth (No XPIC) Table 44 Capacity 56 MHz Channel Bandwidth (no XPIC) Profile 0 Modulation QPSK Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 100 33 81.71457.37 173.72-833.38 219.7 439.59-833.33 338.33 501.11368.51-833.07 9 1024 QAM (Light FEC) 500 185 462.43 82.33 457.95 387.41-530.33 122.59 403.

1 182.91 448.23-833.Chapter 8: Specifcations Radio Specifications 56 MHz Channel Bandwidth with XPIC Table 45 Capacity 56 MHz Channel Bandwidth with XPIC Profile 0 Modulation QPSK Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 100 32 79.99184.64 174.45298.5 230.33 450 182 60 MHz Channel Bandwidth (No XPIC) Table 46 Capacity 60 MHz Channel Bandwidth (no XPIC) Profile Modulation Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 0 QPSK 100 33 85.41-97.19 4 64 QAM 300 105 261.05 318.98 1 8 PSK 150 48 118.53447.51 169.9 223.74-833.36-558 228.29 3 32 QAM 225 88 phn-3968 001v000 Page 8-12 .92-833.43-91.79 475.19-833.98-734.8 2 16 QAM 150 67 173.33 452.55-833.86 119.64 131.36 379.76 450 172 426.74 86.05 83.28260.91 214.79135.6-833.81 80.61 2 16 QAM 150 65 161.33 6 7 256 QAM 512 QAM 8 1024 QAM (Strong FEC) 9 1024 QAM (Light FEC) 400 145 400 158 392.82 90.47 395.47 124.56 331.74 3 32 QAM 225 86 212.56-242.42 263.11486.99-198.68 239.33 361.51516.03 126-142.45 364.86-519.73 162.84-381.5-360.26412.82-256.79 430.98 456.33 412.33 5 128 QAM 300 127 316.6-684.54 1 8 PSK 150 49 125.31-401.24 274.05-275.

33 5 128 QAM 300 130 339.96 531.44-833.19 9 1024 QAM (Light FEC) 500 185 486.1-833.33 420.33 10 2048 QAM 500 201 Transmit Power Specifications (dBm) Table 47 Transmit Power Specifications Modulation 6-8 GHz 11-15 GHz 18-23 GHz 26 GHz 28 GHz 31 GHz 32.23480.08554.3 490.33 6 256 QAM 400 148 391.42-446. phn-3968 001v000 Page 8-13 .83386.77-320.5 411.03-833.07601.Chapter 8: Specifcations Profile Modulation Radio Specifications Minimum required capacity license Max # of supported DS1s /E1s Ethernet throughput No Header DeDuplication L2 Header DeDuplication LTE-Optimized Header DeDuplication 4 64 QAM 300 107 280.23-833.1 294.72 461.19 553.95 424.68-833.96 356.58 282.33 526.37 394.19 341.33 480.73-833.24 442.79 510.38 GHz QPSK 26 24 22 21 14 16 18 8 PSK 26 24 22 21 14 16 18 16 QAM 25 23 21 20 14 15 17 32 QAM 24 22 20 19 14 14 16 64 QAM 24 22 20 19 14 14 16 128 QAM 24 22 20 19 14 14 16 256 QAM 22 20 18 17 12 12 14 512 QAM 22 20 18 17 9 12 14 1024 QAM 21 19 17 16 8 11 13 2048 QAM 19 17 15 14 6 9 11 Note 2048 QAM support is planned for future release.71-833.33 7 512 QAM 400 161 8 1024 QAM (Strong FEC) 450 175 457.28522.

5 -89 -88 -87.5 -72 -71.5 -74 -73.5 -66.0 -70.5 -89.5 2 16 QAM -85.5 -75.0 -84.0 -85.0 -84.5 -83.0 3 32 QAM -85 -84.0 -71.5 -90.5 -74.5 3 32 QAM -82.5 -70 -69 -68.0 8 1024 QAM (strong FEC) -70 -69.5 -82 -81 -80.5 -70.5 9 1024 QAM (light FEC) -69.5 -80.5 -81.0 -65.0 -73.5 -85 -84 -83.5 -85.5 -73 -73.5 -79 -78 -77.5 -92.5 -82.5 -72.5 -81.5 -82.0 -81.5 -67.0 -72.5 Refer to RFU-C roll-out plan for availability of each frequency.5 -86.5 -95 -94 -93.5 -76.5 -91.5 -74.5 -75.0 7 512 QAM -73.0 -78.5 -70.5 1 8 PSK -89 -88.5 -77.0 -75.5 -79.5 -74.0 Table 49 Receiver Threshold for 14 MHz Channel spacing Profile 44 Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -92.5 -65.5 -87.0 6 256 QAM -73.5 -86.0 -72.0 -81.5 -78.5 -66.5 6 256 QAM -75.5 -87.5 -88.0 -90.0 -71.5 -75.0 -68.0 -66.5 2 16 QAM -88.0 -69.5 -84.0 -69.5 -82.5 4 64 QAM -82 -81.5 -79.5 -74.5 -68.5 -69 -69.5 -68 -67.5 -67.0 -72.5 -65.5 -79.0 -91.0 -85.5 -87 -86.5 -80.5 -68.0 -72.0 -80.5 -74.0 -84.5 -78.0 -91.5 -85.5 -69.5 5 128 QAM -75.0 -77.5 -88 -88.5 -75 -75.0 -71.5 5 128 QAM -79 -78. phn-3968 001v000 Page 8-14 .5 -77.0 -69.0 -83.5 -73.5 1 8 PSK -86.5 -76.5 4 64 QAM -79.0 -84.5 -81.Chapter 8: Specifcations Radio Specifications Receiver Threshold (RSL) Specifications (dBm @ BER = 10-6)44 Table 48 Receiver Threshold for 7 MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -95 -94.0 -85.0 -78.5 7 512 QAM -70.5 -92.5 -82.

0 -72.0 -78.5 -65.5 -72.5 -64.5 -74.0 -65.0 4 64 QAM -75.0 -67.0 2 16 QAM -82.0 -60.5 -66.5 -63.0 9 1024 QAM (Light FEC) -63.5 -62.5 -82.0 -62.5 -78.0 -81.0 -66.5 -83.5 -83.5 -71.5 -81.0 -78.0 -88.5 -77.5 -89.0 Table 50 Receiver Threshold for 28 MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -89.0 -87.5 1 8 PSK -83.0 -88.0 -75.0 -88.0 -59.0 -83.0 -63.0 -75.0 -79.0 -80.0 -64.5 -67.0 8 1024 QAM (Strong FEC) -64.0 -61.5 -64.5 -68.0 -60.0 -70.5 -71.5 -86.0 -63.5 -62.0 -61.5 -78.5 -79.5 -60 -59 -58.0 -80.0 -66.5 -65.0 -79.5 -69.0 -62.5 -83.5 -67.5 -77.0 -69.0 3 32 QAM -79.0 -76.0 -81.5 -85.0 -66.0 10 2048 QAM -60 -59.0 -66.0 -77.5 -71.0 -72.5 -68.0 -68.5 -72.5 -74.5 -82.0 -65.5 -82.5 -75.0 -75.5 -89.0 -67.0 -80.5 -71.5 -66.5 1 8 PSK -84.0 -71.5 -82.0 -82.0 -87.0 -64.5 3 32 QAM -78.0 -84.0 -72.5 -56.5 -81.0 -63.5 -76.5 -84.5 -63.5 5 128 QAM -72.0 5 128 QAM -72.0 -74.5 -73.0 7 512 QAM -67.5 -79.0 -69.5 -71.0 phn-3968 001v000 Page 8-15 .0 -74.0 -78.0 -68.5 -63.0 -73.0 6 256 QAM -69.0 -70.0 -80.0 -81.0 -64.0 -78.5 -76.5 -62.5 9 1024 QAM (light FEC) -66.5 -66.5 -74.5 4 64 QAM -76.5 -86.Chapter 8: Specifcations Profile Modulation Radio Specifications Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 8 1024 QAM (strong FEC) -67.0 -69.5 -63.5 -75.5 -85.5 -57.0 -65.0 -81.0 2 16 QAM -82.5 -84.5 -72.5 -55.0 -82.5 Table 51 Receiver Threshold for 30MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -89.0 -88.0 -75.5 -77.5 -84.

5 -85.0 -68.0 -62.5 -77.5 -66.5 -62.5 -65.0 -74.0 -67.0 -86.5 -82.0 -81.0 -80.0 -82.5 -70.0/ -69.5 -70.0 -80.0 -77.0 -69.5 -80.5/ -70.0 -62.0 -79.5 -72.0 -63.5 -60.0 -81.5 -64.5 -78.0 -62.0 -63.5 -64.0 -60.0 -71.0 -68.0* -66.5 -66.5 -76.0 -77.5/ -70.5 -73.5 Table 53 Receiver Threshold for 50MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -86.5 -73.0* -69.0 4 64 QAM -74.0 -62.0 -75.0 -78.5 -59.5 -58.0 -79.5 -80.Chapter 8: Specifcations Profile Modulation Radio Specifications Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 6 256 QAM -69.5 -71.5 -65.0 -65.5 -86.5 -73.5 -60.5 -59.5 -74.5 phn-3968 001v000 Page 8-16 .5 -87.5* -68.5 -77.0 -63.0 6 256 QAM -69.0 -73.5 9 1024 QAM (light FEC) -63.5 -76.0 -75.5/ -69.5 Table 52 Receiver Threshold for 40 MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -87.5 3 32 QAM -77.0 -61.0 -67.0 -61.5 -69.0 1 8 PSK -81.5 -63.5 -71.5 -65.5 -59.5 -81.5* -68.0* -65.0 8 1024 QAM (strong FEC) -64.5 -61.0/ -68.0 -79.5 -60.5 -76.5 -78.0 -62.5 -80.0 8 1024 QAM (strong FEC) -63.0 -63.0 -66.0* -67.5 -79.5 -77.0 2 16 QAM -81.5 -58.0/ -66.0 -87.5* -69.5 -76.0 -80.0 -74.0 -81.0 -74.0 -67.5 -86.5 -67.5 3 32 QAM -76.0 1 8 PSK -82.0 -84.0 -72.0 -84.0 -79.0 -75.0/ -70.5 -66.0 -61.0 -62.0 -64.5 -57.5 -81.5 -59.5 -75.0 -83.0 -71.5 -77.0 -68.5 -63.0 -85.5 -86.0 -78.5 9 1024 QAM (light FEC) -62.5 7 512 QAM -66.0 -61.0/ -67.5 -58.0 -64.5 2 16 QAM -80.0 5 128 QAM -71.5 -66.0 -83.0* 7 512 QAM -67.5 -85.0 -70.5 -76.

5 -61.0 -62.5 -68.0 2 16 QAM -79.5 -69.5 -59.0 -81.5 -66.0 6 256 QAM -66.5 -57.0 -65.0 8 1024 QAM (strong FEC) -61.0 -72.0 -64.0 -61.5 -71.5 -69.0 -70.5 10 2048 QAM -55.0 -64.0 -73.0 -69.5 -75.5 -54 -53 -51 -52 phn-3968 001v000 Page 8-17 .5 -85.5 -60.0 -62.5 -57.5 -73.5 -80.0 -73.0 -60.0 1 8 PSK -81.0 -63.5 -74.0 -66.5 -66.0 -72.0 -78.5 -70.5 -80.5 -67.5 -61.0 -60.5 -65.0 -81.5 -72.0 -63.5 -56.0 -85.5 -62.0 -59.0 -68.5 8 1024 QAM (strong FEC) -62.0 -64.0 -61.0 4 64 QAM -72.0 -67.5 -72.5 -64.5 -55 -55.0 -63.5 -84.0 -77.0 -78.5 -72.0 -64.0 -83.0 -69.5 -76.0 7 512 QAM -65.5 -58.0 6 256 QAM -67.0 -60.0 5 128 QAM -70.0 -67.0 -64.0 -71.5 -54.5 -68.0 -65.5 -57.0 5 128 QAM -69.0 -66.5 -58.0 -61.0 -68.5 -66.5 9 1024 QAM (light FEC) -61.0 -60.5 -79.0 -71.0 -70.5 -61.5 Note 50 MHz support is planned for future release.0 -60.5 -60 -59 -58.5 9 1024 QAM (light FEC) -60 -59.0 -69.5 -71.5 3 32 QAM -75.5 -84.0 -77.5 -65.0 -59.5 -55.0 -67.0 -79.5 -58.5 -56.5 -63.0 7 512 QAM -64.5 -56.Chapter 8: Specifcations Profile Modulation Radio Specifications Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 4 64 QAM -73.5 -75.5 -74.0 -60.5 -57.0 -82.0 -78.5 -74.0 -66.0 -70.0 -75.5 -63.5 -65.5 -62.5 -69. Table 54 Receiver Threshold for 56 MHz Channel spacing Profile Modulation Frequency (GHz) 6 7-10 11-15 18 23 26 28 31-38 0 QPSK -85.5 -81.

5-6152.5 6059.69 5929.5-6152.5-6150.465 6033.69 6241.74-6301.25 6048.5-6030.425 6345.5-6050.5 5939.5-6150.5-6418.5-6306.5 6355-6410.5-6575.5 6303.04-6360.5 5925.5-7075.5-6306.5 6059.25 6300.74-6301.5 6424.5 phn-3968 001v000 Page 8-18 Tx/Rx Spacing 300A 266A 260A 252B 252A 240A 500 .5 6245-6290.49-6405.5 5939.3-6168.34-6420.49-6405.865 5914.5 6226.5 6037. Table 55 Frequency Bands Frequency Band 6L GHz 6H GHz TX Range RX Range 6332.29 6235-6290.89-6286.5 6355-6410.875-6034.5 6191.875-6034.5 6059.5-6393 6191.5-7075.7-6049.5 6059.425 6033.865 6345.5 6924.89-6286.65 5929.5 6924.5 6303.475-6153.34-6420.95 5989-6108.5 6037.825 6226.465 6181.825 5914.5 6365-6410.5 5939.04-6360.3-6168.5-6418.29 6048.99 5989-6108.95 6241.5 6245-6290.5-6170.5-6050.475-6153.65 6181.5 5939.5 5925.5-6393 5972-6093 5972-6093 6332.5 6424.5-6575.Chapter 8: Specifcations Radio Specifications Frequency Bands This section outlines the supported tuning range of each RFU unit.5 6365-6410.99 6300.7-6049.5-6040.5-6040.5 6235-6290.5-6030.5-6170.

5 7301.5 7440.5-6735.5-6772.5-6712.5-6832.5 7412.5-7555.5-7653.5-7499.5-6915.5 6667.5 6924.5-7737.5-6772.5 7622.5-7248.5-7499.5-7444.5-6751.5-7555.Chapter 8: Specifcations Frequency Band 7 GHz Radio Specifications TX Range RX Range 7032.5-7653.5-7091.5-6612.5-7388.5 6707.5-6612.5 6827.5 7664.5-7075.5-6832.5 7105.5 6667.5-6915.5 7538.5 7412.5 6537.5-7555.5-6735.5 7301.5 6607.5-7681.5 6767.5-7192.5 7783.5 6924.5-7667.5-7723.5-7075.5 6764.5-6872.5-7898.5-7471.5 7580.5-7898.5-7388.5 6692.5-6575.5 7608.5 6607.5 7105.5 7161.5-7639.5 7496.5 7678.5 6692.5-6712.5 7496.5 6767.5 7440.5 6424.5-7444.5-7192.5-7737.5-6872.5-6672.5 7357.5 6781-6939 6441-6599 6441-6599 6781-6939 6941-7099 6601-6759 6601-6759 6941-7099 6707.5-7471.5-7667.5 7496.5 6827.5 7357.5-7499.5 7161.5 6424.5 7032.5 7538.5-7248.5 7678.5 7440.5 7783.5-6672.5 7580.5 6764.5 7608.5 6584.5-7639.5 phn-3968 001v000 Page 8-19 Tx/Rx Spacing 340C 340B 340A 160A 196A 168C .5-6575.5-6751.5 6537.5-7091.5 6584.

5-7555.5-7646.5 7336.5 7609.5-7500.5 7280.5-7248.5 7436.5 7693.5 7520.5 7664.5 phn-3968 001v000 Page 8-20 Tx/Rx Spacing 168B 168A 161P 161O 161M 161K .5 7693.Chapter 8: Specifcations Frequency Band Radio Specifications TX Range RX Range 7496.5 7273.5-7206.5 7482.5-7668.5-7206.5-7461.5-7702.5-7192.5-7164.5-7696.5-7513.5 7469.5 7637.5-7178.5-7262.5-7367.5 7454.5-7423.5-7395.5 7175.5 7147.5 7615.5-7706.5 7469.5-7192.5 7525.5-7584.5 7280.5-7234.5-7545.5-7706.5 7637.5 7357.5-7360.5 7203.5 7681.5 7454.5 7525.5-7416.5-7262.5-7674.5-7545.5-7485.5 7436.5-7248.5 7587.5-7646.5 7597.5 7681.5 7441.5 7273.5 7587.5-7513.5-7360.5-7485.5 7426.5 7520.5-7528.5 7105.5 7189.5-7339.5 7364.5 7609.5 7301.5-7668.5 7119.5-7395.5 7308.5 7105.5 7597.5 7615.5-7541.5 7301.5-7367.5-7164.5-7178.5-7723.5-7416.5-7752.5 7133.5-7584.5-7423.5 7119.5-7332.5 7189.5-7234.5 7357.5-7461.5-7622.5 7203.5 7441.5-7674.5-7500.5 7308.5-7752.5 7643.5 7426.5 7336.5-7528.5-7332.5 7364.5 7133.5 7147.5-7696.5-7622.5 7175.5-7339.

5 7273.5-7639.5-7702.5 7580.5-7562.5-7541.5 7608.5 7608.5-7667.5 7671.5-7723.5 7419.5-7730.5-7506.5-7478.5 7622.5-7639.5-7241.5-7402.5 7580.5-7241.5-7402.5 7447.5 7412.5-7562.5 7419.Chapter 8: Specifcations Frequency Band Radio Specifications TX Range RX Range 7482.5-7478.5 7671.5-7702.5-7653.5-7492.5-7506.5 7664.5-7667.5 7447.5-7541.5 7461.5 7510.5-7723.5 7580.5-7353.5 7643.5-7192.5 7322.5-7639.5-7562.5 7503.5 7112.5 7447.5 7573.5-7723.5 7112.5-7667.5 7161.5 7322.5-7569.5-7478.5 7664.5-7702.5-7730.5-7506.5-7562.5 7161.5-7192.5-7667.5-7541.5-7492.5-7569.5 7573.5-7353.5 7580.5 7622.5 7664.5 7419.5-7478.5 7447.5 7503.5-7639.5 7608.5-7653.5 7510.5 7503.5 7461.5 7412.5 7419.5 7608.5-7723.5-7506.5 7273.5 7664.5 7709-7768 7548-7607 7548-7607 7709-7768 7737-7796 7576-7635 7576-7635 7737-7796 7765-7824 7604-7663 7604-7663 7765-7824 7793-7852 7632-7691 phn-3968 001v000 Page 8-21 Tx/Rx Spacing 161J 161I 161F 161D .5 7503.

5-7367.5-7213.5 7182.5-7241.5-7185.5 7308.5 7308.5 7280.5-7395.5 7126.Chapter 8: Specifcations Frequency Band Radio Specifications TX Range RX Range 7632-7691 7793-7852 7584-7643 7423-7482 7423-7482 7584-7643 7612-7671 7451-7510 7451-7510 7612-7671 7640-7699 7479-7538 7479-7538 7640-7699 7668-7727 7507-7566 7507-7566 7668-7727 7409-7468 7248-7307 7248-7307 7409-7468 7437-7496 7276-7335 7276-7335 7437-7496 7465-7524 7304-7363 7304-7363 7465-7524 7493-7552 7332-7391 7332-7391 7493-7552 7284-7343 7123-7182 7123-7182 7284-7343 7312-7371 7151-7210 7151-7210 7312-7371 7340-7399 7179-7238 7179-7238 7340-7399 7368-7427 7207-7266 7207-7266 7368-7427 7280.5-7367.5 7154.5 7126.5-7339.5-7213.5 phn-3968 001v000 Page 8-22 Tx/Rx Spacing 161C 161B 161A 154C .5 7336.5 7154.5-7185.5-7339.

5 7364.5-7695.5 7636.5-7695.5 7678.5 7744.5-7513.5-8305.5 8023-8186.5 8274.5 7468.5 7510.5 – 8497.5 7364.5-7681.245 7835.5 7524.5-7423.5-8395.5 8319.5 8274.375-7837.325 7717.5 8438.5 – 8378.5-7681.5 7678.5 8304.5 8396.5-7583.5-7485.5 7608.5-7737.5 7608.5 8304.5 7210.5-7513.68-7875 7711.975-7955.5 7804.32 7711.375-7837.695-8148.5 7336.295-8267.5-7775.5 7426.5 – 8497.5-7527.5-7541.68-7875 8023-8186.5-7241.5-7269.5-7583.Chapter 8: Specifcations Frequency Band 8 GHz Radio Specifications TX Range RX Range 7182.5 7636.5 7482.5-7269.5-8455.5-7639.5-7541.5 7454.5 8438.5-8305.5-7723.5-8455.5-7737.5 8396.5-7395.5-7653.645 311B 8147.695-8148.32 8028.5-7667.5 7510.5-7569.5-7639.5 7594.5 7744.5 7482.5 7524.5-7423.5 7580.5-7485.5 7580.5-7569.5 8277.5 7622.5-7723.5 7468.5-7527.5-8336.5 7426.5-7499.5 7664.5 7594.5 7804.5 8319.5 7454.5-7895.5-8395.5 7440.925 phn-3968 001v000 Page 8-23 Tx/Rx Spacing 154B 154A 119A 530A 500A 311C-J .5-7895.5 7664.5-7775.5-8336.5 7210.645 7717.5 7622.5-7667.325 8028.5-7499.5 7440.5 – 8378.5-7653.5 8277.

8-7970.5 phn-3968 001v000 Page 8-24 Tx/Rx Spacing 311A 310D 310C 310A 300A 266C .8-7970.5 8144.5 7849.5 8159.5 8024.15 8043.5 8024.5-8145.5-8270.245 8043.12-8282.5-8123.925 8147.5 7729.5-7840.5 8159.2-7852.5 8036.07 7850.75 7850.295-8267.5-7965.5 7844.5 7724.12-8282.5-8150.5 8144.5 8302.5-8270.75 8162.5-7960.5 7729.975-7955.5-8265.5-7845.Chapter 8: Specifcations Frequency Band Radio Specifications TX Range RX Range 7835.47 7732.5-7960.5 7849.5-8145.5-7965.5 8039.5-8389.5-8150.52-8163.15 7732.5 7724.5-7840.52-8163.2-7852.5 7844.47 8162.5-8265.07 8212-8302 7902-7992 7902-7992 8212-8302 8240-8330 7930-8020 7930-8020 8240-8330 8296-8386 7986-8076 7986-8076 8296-8386 8212-8302 7902-7992 7902-7992 8212-8302 8240-8330 7930-8020 7930-8020 8240-8330 8296-8386 7986-8076 7986-8076 8296-8386 8380-8470 8070-8160 8070-8160 8380-8470 8408-8498 8098-8188 8098-8188 8408-8498 8039.5-7845.

5-8291.5 8022.5-8137.5 7924.5-8349.5-8277.5 8226.5-8137.52 8270.5 7924.5 7974.5 8176.5-8277.5-8025.52-8287.5-8035.5 8226.5-8403.52-8287.5 8020.5 7910.5 8190.5 7910.Chapter 8: Specifcations Frequency Band 10 GHz Radio Specifications TX Range RX Range 8036.5 8288.5 8176.5 8022.5-8035.5-8389.5 8288.5-8123.5 8190.52 7974.5-8099.5-8025.5 10501-10563 10333-10395 10333-10395 10501-10563 10529-10591 10361-10423 10361-10423 10529-10591 10585-10647 10417-10479 10417-10479 10585-10647 10501-10647 10151-10297 10151-10297 10501-10647 10498-10652 10148-10302 10148-10302 10498-10652 10561-10707 10011-10157 10011-10157 10561-10707 10701-10847 10151-10297 10151-10297 10701-10847 10590-10622 10499-10531 10499-10531 10590-10622 10618-10649 10527-10558 10527-10558 10618-10649 10646-10677 10555-10586 phn-3968 001v000 Page 8-25 Tx/Rx Spacing 266B 266A 252A 250A 168A 350A 350B 550A 91A .5-8011.5-8291.5 8302.5-8403.5-8011.

Chapter 8: Specifcations Frequency Band 11 GHz 13 GHz 15 GHz Radio Specifications TX Range RX Range 10555-10586 10646-10677 11425-11725 10915-11207 10915-11207 11425-11725 11185-11485 10700-10950 10695-10955 11185-11485 13002-13141 12747-12866 12747-12866 13002-13141 13127-13246 12858-12990 12858-12990 13127-13246 12807-12919 13073-13185 13073-13185 12807-12919 12700-12775 12900-13000 12900-13000 12700-12775 12750-12825 12950-13050 12950-13050 12750-12825 12800-12870 13000-13100 13000-13100 12800-12870 12850-12925 13050-13150 13050-13150 12850-12925 15110-15348 14620-14858 14620-14858 15110-15348 14887-15117 14397-14627 14397-14627 14887-15117 15144-15341 14500-14697 14500-14697 15144-15341 14975-15135 14500-14660 14500-14660 14975-15135 phn-3968 001v000 Page 8-26 Tx/Rx Spacing All 266 266A 200 490 644 475 .

Chapter 8: Specifcations Frequency Band 18 GHz 23 GHz 26 GHz Radio Specifications TX Range RX Range 15135-15295 14660-14820 14660-14820 15135-15295 14921-15145 14501-14725 14501-14725 14921-15145 15117-15341 14697-14921 14697-14921 15117-15341 14963-15075 14648-14760 14648-14760 14963-15075 15047-15159 14732-14844 14732-14844 15047-15159 15229-15375 14500-14647 14500-14647 15229-15375 19160-19700 18126-18690 18126-18690 19160-19700 18710-19220 17700-18200 17700-18200 18710-19220 19260-19700 17700-18140 17700-18140 19260-19700 23000-23600 22000-22600 22000-22600 23000-23600 22400-23000 21200-21800 21200-21800 22400-23000 23000-23600 21800-22400 21800-22400 23000-23600 25530-26030 24520-25030 24520-25030 25530-26030 25980-26480 24970-25480 phn-3968 001v000 Page 8-27 Tx/Rx Spacing 420 315 728 1010 1560 1008 1232 /1200 1008 .

Chapter 8: Specifcations Frequency Band 28 GHz 31 GHz 32 GHz 38 GHz Radio Specifications TX Range RX Range 24970-25480 25980-26480 25266-25350 24466-24550 24466-24550 25266-25350 25050-25250 24250-24450 24250-24450 25050-25250 28150-28350 27700-27900 27700-27900 28150-28350 27950-28150 27500-27700 27500-27700 27950-28150 28050-28200 27700-27850 27700-27850 28050-28200 27960-28110 27610-27760 27610-27760 27960-28110 28090-28315 27600-27825 27600-27825 28090-28315 29004-29453 27996-28445 27996-28445 29004-29453 28556-29005 27548-27997 27548-27997 28556-29005 29100-29125 29225-29250 29225-29250 29100-29125 31000-31085 31215-31300 31215-31300 31000-31085 31815-32207 32627-33019 32627-33019 31815-32207 32179-32571 32991-33383 32991-33383 32179-32571 38820-39440 37560-38180 phn-3968 001v000 Page 8-28 Tx/Rx Spacing 800 450 350 490 1008 125 175 812 1260 .

Chapter 8: Specifcations Frequency Band Radio Specifications TX Range RX Range 37560-38180 38820-39440 38316-38936 37045-37676 37045-37676 38316-38936 39650-40000 38950-39300 38950-39300 39500-40000 39300-39650 38600-38950 38600-38950 39300-39650 37700-38050 37000-37350 37000-37350 37700-38050 38050-38400 37350-37700 37350-37700 38050-38400 phn-3968 001v000 Page 8-29 Tx/Rx Spacing 700 .

Chapter 8: Specifcations Network Specifications Network Specifications Ethernet Latency Specifications Ethernet Latency – 7 MHz Channel Bandwidth Table 56 Ethernet Latency 7 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1518 0 QPSK 924 987 1106 1353 1840 2317 1 8 PSK 678 718 799 969 1298 1623 2 16 QAM 525 549 604 728 962 1194 3 32 QAM 446 470 515 605 787 961 4 64 QAM 399 419 456 531 679 824 5 128 QAM 369 383 416 479 603 725 6 256 QAM 366 380 408 463 573 681 7 512 QAM 371 384 411 462 566 668 8 1024 QAM (strong FEC) 352 366 390 439 538 633 9 1024 QAM (light FEC) 349 360 384 430 524 613 Ethernet Latency – 14 MHz Channel Bandwidth Table 57 Ethernet Latency 14 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1518 0 QPSK 460 480 534 647 867 1086 1 8 PSK 346 364 402 479 629 778 2 16 QAM 265 278 307 364 477 588 3 32 QAM 233 244 267 312 401 487 phn-3968 001v000 Page 8-30 .

Chapter 8: Specifcations ACM Modulation Working Point Network Specifications Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1518 4 64 QAM 213 222 241 279 353 426 5 128 QAM 193 202 219 251 315 377 6 256 QAM 177 184 199 228 286 341 7 512 QAM 209 216 230 256 310 361 8 1024 QAM (strong FEC) 195 202 215 241 292 341 9 1024 QAM (light FEC) 190 197 210 234 283 330 Ethernet Latency – 28 MHz Channel Bandwidth Table 58 Ethernet Latency 28 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1518 0 QPSK 154 169 198 257 373 484 1 8 PSK 130 141 162 204 286 363 2 16 QAM 109 117 133 166 231 290 3 32 QAM 105 111 125 152 204 252 4 64 QAM 101 107 119 142 187 228 5 128 QAM 95 100 110 131 171 207 6 256 QAM 89 94 103 123 160 193 7 512 QAM 113 117 126 145 179 210 8 1024 QAM (strong FEC) 104 108 117 135 168 198 9 1024 QAM (light FEC) 106 110 118 136 168 197 phn-3968 001v000 Page 8-31 .

Chapter 8: Specifcations Network Specifications Ethernet Latency – 30 MHz Channel Bandwidth Table 59 Ethernet Latency 30 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1280 1518 0 QPSK 228 242 270 326 439 495 548 1 8 PSK 171 181 202 242 323 363 400 2 16 QAM 138 145 160 190 250 280 309 3 32 QAM 124 130 142 166 214 238 260 4 64 QAM 115 120 130 151 191 212 231 5 128 QAM 105 109 118 136 172 190 206 6 256 QAM 110 115 122 138 171 187 202 7 512 QAM 116 120 128 143 174 189 204.2 8 1024 QAM (strong FEC) 107 111 118 133 162 177 190 9 1024 QAM (light FEC) 110 113 120 134 162 176 190 Ethernet Latency – 40 MHz Channel Bandwidth Table 60 Ethernet Latency 40 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1280 1518 0 QPSK 194 206 230 278 373 420 465 1 8 PSK 147 156 173 208 277 311 342 2 16 QAM 120 126 139 165 216 242 267 3 32 QAM 108 113 124 144 186 207 226 4 64 QAM 100 104 113 131 166 185 201 5 128 QAM 92 96 104 120 151 167 181 6 256 QAM 95 100 106 120 149 163 177 7 512 QAM 100 104 111 124 151 165 178 phn-3968 001v000 Page 8-32 .

Chapter 8: Specifcations ACM Modulation Working Point Network Specifications Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1280 1518 8 1024 QAM (strong FEC) 93 96 102 116 141 155 166 9 1024 QAM (light FEC) 95 97 104 116 141 154 166 Ethernet Latency – 50 MHz Channel Bandwidth Table 61 Ethernet Latency 50 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1280 1518 0 QPSK 127 135 150 180 240 270 298 1 8 PSK 100 105 116 139 183 205 226 2 16 QAM 83 88 96 114 149 166 182 3 32 QAM 76 80 87 101 130 145 158 4 64 QAM 70 73 79 92 117 130 141 5 128 QAM 67 70 75 87 109 120 131 6 256 QAM 66 69 74 85 106 116 126 7 512 QAM 68 71 76 86 106 116 125 8 1024 QAM (strong FEC) 64 66 71 81 100 110 119 9 1024 QAM (light FEC) 64 66 71 81 99 109 117 Note 50 MHz support is planned for future release. phn-3968 001v000 Page 8-33 .

Chapter 8: Specifcations Network Specifications Ethernet Latency – 56 MHz Channel Bandwidth Table 62 Ethernet Latency 56 MHz Channel Bandwidth ACM Modulation Working Point Latency (usec) with GE Interface Frame 64 Size 128 256 512 1024 1518 0 QPSK 94 102 119 152 216 275 1 8 PSK 83 89 102 127 174 218 2 16 QAM 72 77 87 108 146 182 3 32 QAM 69 73 82 99 133 162 4 64 QAM 66 69 77 93 123 149 5 128 QAM 65 68 75 90 116 140 6 256 QAM 61 64 71 84 110 132 7 512 QAM 69 72 78 92 116 137 8 1024 QAM (strong FEC) 65 68 74 87 110 131 Ethernet Specifications Ethernet Interface Specifications Table 63 Ethernet Interface Specifications 4 x 10/100/1000Base-T (RJ-45) and Supported Ethernet Interfaces for Traffic 2 x 1000base-X (SFP) Supported Ethernet Interfaces for Management 2 x 10/100 Base-T (RJ-45) Optical 1000Base-LX (1310 nm) or Supported SFP Types SX (850 nm) Carrier Ethernet Functionality Table 64 Carrier Ethernet Functionality Switching capacity 8 Gbps "Jumbo" Frame Support Up to 9600 Bytes phn-3968 001v000 Page 8-34 .

3ad link aggregation Advanced CoS classification and remarking Per interface CoS based packet queuing/buffering (8 queues) Per queue statistics Tail-drop and WRED with CIR/EIR support QoS Flexible scheduling schemes (SP/WFQ/Hierarchical) Per interface and per queue traffic shaping Hierarchical-QoS (H-QoS) – 2K service level queues46 2 Gbit packet buffer MSTP Network resiliency ERP (G.8261 45 Planned for future release.1731/802. Capacity.1731) 48 Per port Ethernet counters (RMON/RMON2) Performance Monitoring Radio ACM statistics Enhanced radio Ethernet statistics (Frame Error Rate.1ag) 47 Service OAM PM (Y. phn-3968 001v000 Page 8-35 .1ad provider bridges (QinQ) 802. Utilization) Synchronization Specifications Table 65 Synchronization Specifications Sync Unit / SyncE ITU-T G.Chapter 8: Specifcations Network Specifications General Header De-Duplication45 Integrated Carrier Ethernet Switch MAC address learning with 128K MAC addresses 802. 47 Planned for future release. 46 Planned for future release. 48 Planned for future release. Throughput.8032) FM (Y.

RFU-C phn-3968 001v000 Page 8-36 . 28-38 GHz 1+0: 26 1+1: 43 RFU only.5 to -59 VDC Power Consumption Specifications The following table shows the maximum power consumption for PTP 820G IDU and supported RFUs.Chapter 8: Specifcations Power Specifications Power Specifications Power Input Specifications Table 66 Power Input Specifications IDU Standard Input -48 VDC IDU DC Input range -40 to --60 VDC RFU-C Operating Range -40. Table 67 Power Consumption Specifications Configuration Power (W) IDU Eth-only with single modem 23.9W Addition for 16 DS1s 11W Comments 6-26 GHz 1+0: 22 1+1: 39 RFU only. The maximum power consumption for the entire system is the sum of the IDU and the RFUs connecting to it.5W Addition for second modem 2.

8 1. an adaptor with a 0.4 0.5 0.2 0. TDM Specifications DS1/E1 Interface Specifications Table 69 DS1 Interface Specifications Interface Type DS1/E1 Number of Ports 16 x DS1s /E1 Connector Type MDR 69-pin Framing Framed / Unframed Coding HDB3 phn-3968 001v000 Page 8-37 .5 0.6 1.5 Main Path 1.5 0. If other antennas are to be used.2 0.5 0.8 3.8 Secondary Path 6 6 6 6 6 Integrated antenna 0.Chapter 8: Specifcations Physical and Electrical Specifications Physical and Electrical Specifications Mediation Device Losses Table 68 RFU-C Mediation Device Losses Configuration Interfaces 1+0 Direct Mount 1+1 HSB 6-8 GHz 11 GHz 1315 GHz 1826 GHz 28-38 GHz Integrated antenna 0.1 dB loss should be considered.5 0.9 4 4 with asymmetrical coupler Direct Mount 2+0 DP (OMT) Direct Mount 2+0/1+1 FD SP Integrated antenna Note The antenna interface is always the RFU-C interface.8 1.5 3.6 1.8 3.

824.432. G. Belden 9914/RG-8 (1000 ft) or equivalent. ITU-T I.736.73” (1RU) IDU Dimensions Width: 16.87 inches Depth: 3. G. ETS 300 417.775.77” Depth: 7.5” (subject to vendor and antenna size) phn-3968 001v000 Page 8-38 . TR-NWT-000499 E1 Cross Connect Table 70 E1 Interface Specifications E1 Cross Connect Capacity 256 E1 Trails (VCs) E1 Trails Protection 1+1 / 1:1 Mechanical Specifications Table 71 IDU Mechanical Specifications Height: 1.Chapter 8: Specifcations Physical and Electrical Specifications Line Impedance 120 ohm/100 ohm balanced.35 inches Weight: 9 lbs RFU-C Standard Mounting OD Pole 50 mm-120 mm/2”-4. G.08” Weight: 5. Bellcore GR-253-core.823. G. ETSI ETS 300 147.828. Compatible Standards ITU-T G. N-type connectors (male) to the RFU. Table 72 RFU-C Mechanical Specifications Height: 7. G. TNC connectors to the IDU.5 lbs IDU-RFU Connection Coaxial cable RG-223 (300 ft).87 inches RFU-C Dimensions Width: 7.703. Optional 75 ohm unbalanced supported using panel with integrated impedance adaption.

o -13F to 149F – Temperature range for exceptional temperatures. with limited margins. tested successfully. Note Cold startup requires at least 23F  Humidity: 5%RH to 95%RH Environmental Specifications for RFU   Temperature: o -27F to 131F – Temperature range for continuous operating temperature with high reliability: o -49F to 140F – Temperature range for exceptional temperatures. tested successfully.Chapter 8: Specifcations Physical and Electrical Specifications Environmental Specifications Environmental Specifications for IDU  Temperature: o 23F to 131F – Temperature range for continuous operating temperature with high reliability. specific antennas PNs are required):  Andrew: VHLP series  Radio Wave phn-3968 001v000 Page 8-39 . RFU-C can be mounted directly for all frequencies (6-38 GHz) using the following antenna types (for integrated antennas. with limited margins: Humidity: 5%RH to 100%RH Supported Antenna Types RFU-C uses Andrew and Radio Wave antennas.

Glossary Term Definition ACM Adaptive Coding and Modulation ACR Adaptive Clock Recovery AES Advanced Encryption Standard AIS Alarm Indication Signal ATPC Automatic Tx Power Control BBS Baseband Switching BER Bit Error Ratio BLSR Bidirectional Line Switch Ring BPDU Bridge Protocol Data Units BWA Broadband Wireless Access CBS Committed Burst Size CCDP Co-channel dual polarization CE Customer Equipment CET Carrier-Ethernet Transport CFM Connectivity Fault Management CIR Committed Information Rate CLI Command Line Interface CoS Class of Service DA Destination Address DSCP Differentiated Service Code Point EBS Excess Burst Size EIR Excess Information Rate EPL Ethernet Private Line EVPL Ethernet Virtual Private Line EVC Ethernet Virtual Connection FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol) phn-3968 001v000 Page I .

Glossary Term Definition GE Gigabit Ethernet GMT Greenwich Mean Time HSB Hot Standby HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP) IDC Indoor Controller IDU Indoor unit LANs Local area networks LMS License Management System LOC Loss of Carrier LOF Loss Of Frame LOS Loss of Signal LTE Long-Term Evolution MAID Maintenance Association (MA) Identifier (ID) MEN Metro Ethernet Network MPLS Multiprotocol Label Switching MRU Maximum Receive Unit MSP Multiplex Section Protection MSTI Multiple Spanning Tree Instance MSTP Multiple Spanning Tree Protocol MTU Maximum Transmit Capability NMS Network Management System NTP Network Time Protocol OAM Operation Administration & Maintenance (Protocols) ODU Out Door Unit OOF Out-of-Frame PBB-TE Provider Backbone Bridge Traffic Engineering PBS Peak Burst Rate PDV Packed Delay Variation PIR Peak Information Rate PM Performance Monitoring phn-3968 001v000 Page II .

Glossary Term Definition PN Provider Network (Port) PSN Frame Switched Network PTP Precision Timing-Protocol PW Pseudowire QoE Quality of-Experience QoS Quality of Service RBAC Role-Based Access Control RDI Reverse Defect Indication RFU Radio Frequency Unit RMON Ethernet Statistics RSL Received Signal Level RSTP Rapid Spanning Tree Protocol SAP Service Access Point SFTP Secure FTP SLA Service level agreements SNMP Simple Network Management Protocol SNP Service Network Point SNTP Simple Network Time Protocol SP Service Point STP Spanning Tree Protocol SSH Secured Shell (Protocol) SSM Synchronization Status Messages SyncE Synchronous Ethernet TC Traffic Class TOS Type of Service UNI User Network Interface UTC Coordinated Universal Time VC Virtual Containers Web EMS Web-Based Element Management System WG Wave guide phn-3968 001v000 Page III .

Glossary Term Definition WFQ Weighted Fair Queue WRED Weighted Random Early Detection XPIC Cross Polarization Interference Cancellation phn-3968 001v000 Page IV .