User Guide

PTP 820C/820C-HP
820S/820E
System Release 11.5
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.

© 2019 Cambium Networks Limited. All Rights Reserved.

Phn 3963 013v000

Contents
About This User Guide ....................................................................................................................................... 1
Contacting Cambium Networks ......................................................................................................................2
Purpose ...........................................................................................................................................................3
Cross references ..............................................................................................................................................3
Feedback .........................................................................................................................................................3
Problems and warranty...........................................................................................................................................4
Reporting problems.........................................................................................................................................4
Repair and service ...........................................................................................................................................4
Hardware warranty .........................................................................................................................................4
Security advice ........................................................................................................................................................5
Warnings, cautions, and notes ...............................................................................................................................6
Warnings .........................................................................................................................................................6
Cautions...........................................................................................................................................................6
Notes ...............................................................................................................................................................6
Caring for the environment ....................................................................................................................................7
In EU countries ................................................................................................................................................7
In non-EU countries .........................................................................................................................................7
Chapter 1: Introduction.................................................................................................................................. 8
System Overview ....................................................................................................................................................9
Configuration Tips ...........................................................................................................................................9
4x4 MIMO and 2+2 Space Diversity ..............................................................................................................10
PTP 820C - Overview .....................................................................................................................................10
PTP 820C-HP Overview ..................................................................................................................................10
PTP 820S ........................................................................................................................................................11
PTP 820E Overview........................................................................................................................................11
PoE Injector Overview ...................................................................................................................................12
PTP 820 Assured Platform .............................................................................................................................12
The Web-Based Element Management System ............................................................................................13
Reference Guide to Web EMS Menu Structure ....................................................................................................26
Chapter 2: Getting Started .......................................................................................................................... 101
Assigning IP Addresses in the Network ...............................................................................................................102
Establishing a Connection ...................................................................................................................................103
PC Setup ..............................................................................................................................................................104
Logging on ...........................................................................................................................................................106
Logging in Without Knowing the IP Address ...............................................................................................106
Changing Your Password.....................................................................................................................................109
Applying a Pre-Defined Configuration File ..........................................................................................................110

Phn 3963 013v000

Page i
Contents

Performing Quick Platform Setup .......................................................................................................................112

Mate Management Access (IP Forwarding) ........................................................................................................115
Configuring In-Band Management......................................................................................................................116
Changing the Management IP Address ...............................................................................................................117
Configuring the Activation Key ...........................................................................................................................118
Activation Key Overview .............................................................................................................................118
Viewing the Activation Key Status Parameters ...........................................................................................118
Entering the Activation Key .........................................................................................................................119
Activating Demo Mode................................................................................................................................120
Displaying a List of Activation-Key-Enabled Features .................................................................................120
Setting the Time and Date (Optional) .................................................................................................................126
Enabling the Interfaces (Interface Manager) ......................................................................................................128
Configuring the Radio (MRMC) Script(s) .............................................................................................................130
Radio Profiles...............................................................................................................................................138
Running the Frequency Scanner (PTP 820E) .......................................................................................................139
Configuring the Radio Parameters ......................................................................................................................142
Enabling Link ID Mismatch Security ............................................................................................................146
Enabling ACM with Adaptive Transmit Power ....................................................................................................148
Operating in FIPS Mode ......................................................................................................................................150
Requirements for FIPS Compliance .............................................................................................................150
Enabling FIPS Mode .....................................................................................................................................150
Encrypting the External Protection Link ......................................................................................................151
Configuring Grouping (Optional) ........................................................................................................................154
Creating Service(s) for Traffic..............................................................................................................................155
Chapter 3: Configuration Guide ................................................................................................................... 156
System Configurations ........................................................................................................................................157
Configuring a Link Using the Quick Configuration Wizard ..................................................................................158
Configuring a 1+0 Link Using the Quick Configuration Wizard....................................................................177
Configuring a 1+0 (Repeater) Link Using the Quick Configuration Wizard..................................................182
Configuring a 2 x (1+0) Link Using the Quick Configuration Wizard............................................................187
Configuring a 2+0 Multi-Carrier ABC Link Using the Quick Configuration Wizard ......................................197
Configuring a Multiband (Enhanced Multi-Carrier ABC) Link Using the Quick Configuration Wizard ........203
Configuring Multi-Carrier ABC ............................................................................................................................211
Multi-Carrier ABC Overview ........................................................................................................................211
Configuring a Multi-Carrier ABC Group .......................................................................................................211
Configuring the Multi-Carrier ABC Minimum Bandwidth Override Option ................................................214
Adding and Removing Group Members ......................................................................................................215
Deleting a Multi-Carrier ABC Group ............................................................................................................216
Configuring Multiband (Enhanced Multi-Carrier ABC)........................................................................................217
This feature requires: ..................................................................................................................................217
Multiband Overview ....................................................................................................................................217
Multiband Configuration .............................................................................................................................220

Phn 3963 013v000

Page ii
Contents

Multiband Management .............................................................................................................................226

Configuring Synchronization in a Multiband Node .....................................................................................230
Configuring Link Aggregation (LAG) and LACP ....................................................................................................232
LAG Overview ..............................................................................................................................................232
Configuring a LAG Group .............................................................................................................................233
Enabling and Disabling LAG Group Shutdown in Case of Degradation Event .............................................236
Configuring Enhanced LAG Distribution ......................................................................................................236
Deleting a LAG Group ..................................................................................................................................237
Displaying LACP Parameters and Statistics .................................................................................................238
Configuring XPIC .................................................................................................................................................244
XPIC Overview .............................................................................................................................................244
Configuring the Radio Carriers ....................................................................................................................244
Creating an XPIC Group ...............................................................................................................................245
Performing Antenna Alignment for XPIC .....................................................................................................245
Configuring Unit Protection with HSB Radio Protection (External Protection) ..................................................247
Unit Protection Overview ............................................................................................................................247
Configuring Ethernet Interface Protection ..................................................................................................248
Configuring HSB Radio Protection ...............................................................................................................249
Configuring 2+2 HSB Protection on a PTP 820C Unit ..................................................................................251
Viewing the Configuration of the Standby unit ...........................................................................................252
Editing Standby Unit Settings ......................................................................................................................252
Viewing Link and Protection Status and Activity .........................................................................................253
Manually Switching to the Standby Unit .....................................................................................................253
Disabling Automatic Switchover to the Standby Unit .................................................................................254
Disabling Unit Protection ............................................................................................................................254
Configuring 1 + 1 HSB with Space Diversity ........................................................................................................255
Configuring MIMO and Space Diversity ..............................................................................................................258
MIMO and Space Diversity Overview ..........................................................................................................258
Upgrading a 4x4 MIMO Link from an Earlier Version to Release 10.5 or Higher ........................................259
Configuring a 4x4 MIMO Link ......................................................................................................................260
Configuring a 2x2 MIMO Link ......................................................................................................................266
Configuring a 1+0 or 2+2 Space Diversity Link ............................................................................................268
Viewing MMI Levels ....................................................................................................................................269
Deleting a MIMO or Space Diversity Group ................................................................................................271
Configuring Advanced Space Diversity (ASD)......................................................................................................272
ASD Overview ..............................................................................................................................................272
Configuring an ASD Link ..............................................................................................................................274
Viewing ASD Status .....................................................................................................................................278
Deleting an ASD Group ................................................................................................................................279
Configuring Advanced Frequency Reuse (AFR) ...................................................................................................280
AFR Overview ..............................................................................................................................................280
Initial Link Configuration and Alignment for AFR ........................................................................................280

Phn 3963 013v000

Page iii
Contents

Software Configuration for AFR ..................................................................................................................281

Deleting an AFR Group ................................................................................................................................285
Operating a PTP 820C or PTP 820C-HP in Single Radio Carrier Mode ................................................................287
Chapter 4: Unit Management ...................................................................................................................... 288
Defining the IP Protocol Version for Initiating Communications ........................................................................289
Configuring the Remote Unit’s IP Address..........................................................................................................290
Changing the Subnet of the Remote IP Address .........................................................................................292
Configuration SNMP ...........................................................................................................................................293
Configuring Trap Managers ................................................................................................................................296
Installing and Configuring an FTP or SFTP Server ...............................................................................................299
Configuring the Internal Ports for FTP or SFTP ...................................................................................................302
Upgrading the Software ......................................................................................................................................303
Viewing Current Software Versions ............................................................................................................303
Software Upgrade Overview .......................................................................................................................304
Downloading and Installing Software .........................................................................................................305
Downloading Software Via HTTP or HTTPS .................................................................................................305
Downloading Software Via FTP or SFTP ......................................................................................................307
Installing Software .......................................................................................................................................309
Configuring a Timed Installation .................................................................................................................310
Backing Up and Restoring Configurations...........................................................................................................312
Configuration Management Overview ........................................................................................................312
Viewing Current Backup Files ......................................................................................................................312
Setting the Configuration Management Parameters ..................................................................................313
Exporting a Configuration File .....................................................................................................................316
Importing a Configuration File ....................................................................................................................317
Deleting a Configuration File .......................................................................................................................318
Backing Up the Current Configuration ........................................................................................................318
Restoring a Saved Configuration .................................................................................................................319
Editing CLI Scripts ........................................................................................................................................319
Setting the Unit to the Factory Default Configuration........................................................................................321
Performing a Hard (Cold) Reset ..........................................................................................................................322
Configuring Unit Parameters ..............................................................................................................................323
Configuring NTP ..................................................................................................................................................325
Displaying Unit Inventory....................................................................................................................................278
Displaying SFP DDM and Inventory Information ................................................................................................279
Displaying Information about an SFP Module .............................................................................................279
Displaying PMs about an SFP Module .........................................................................................................282
Defining a Login Banner ......................................................................................................................................284
Chapter 5: Radio Configuration ................................................................................................................... 285
Viewing the Radio Status and Settings ...............................................................................................................286
Configuring the Remote Radio Parameters ........................................................................................................289
Configuring ATPC and ATPC Override Timer .......................................................................................................292

Phn 3963 013v000

Page iv
Contents

Configuring Header De-Duplication and Frame Cut-Through .............................................................................295

Viewing Header De-Duplication and Frame Cut-Through Counters ...........................................................297
Configuring AES-256 Payload Encryption ...........................................................................................................301
Configuring and Viewing Radio PMs and Statistics .............................................................................................305
Configuring BER Thresholds and Displaying Current BER............................................................................305
Displaying MRMC Status .............................................................................................................................307
Displaying MRMC PMs ................................................................................................................................309
Displaying and Clearing Defective Block Counters ......................................................................................311
Displaying Signal Level PMs and Configuring Signal Level PM Thresholds ..................................................314
Displaying Modem BER (Aggregate) PMs ....................................................................................................316
Displaying MSE PMs and Configuring MSE PM Thresholds .........................................................................318
Displaying XPI PMs and Configuring XPI PM Threshold ..............................................................................320
Displaying Traffic PMs .................................................................................................................................322
Chapter 6: Ethernet Services and Interfaces ................................................................................................ 329
Configuring Ethernet Service(s) ..........................................................................................................................330
Ethernet Services Overview ........................................................................................................................330
General Guidelines for Provisioning Ethernet Services ...............................................................................330
The Ethernet Services Page .........................................................................................................................331
Adding an Ethernet Service .........................................................................................................................332
Editing a Service ..........................................................................................................................................334
Deleting a Service ........................................................................................................................................334
Enabling, Disabling, or Deleting Multiple Services ......................................................................................334
Viewing Service Details ...............................................................................................................................335
Configuring Service Points ...........................................................................................................................335
Setting the MRU Size and the S-VLAN Ethertype ................................................................................................349
Configuring Ethernet Interfaces..........................................................................................................................350
Configuring Automatic State Propagation and Link Loss Forwarding .................................................................353
Viewing Ethernet PMs and Statistics ..................................................................................................................356
RMON Statistics ...........................................................................................................................................356
Egress CoS Statistics ....................................................................................................................................357
Port TX Statistics ..........................................................................................................................................359
Port RX Statistics .........................................................................................................................................362
Chapter 7: Quality of Service (QoS) ............................................................................................................. 365
QoS Overview .....................................................................................................................................................366
Configuring Classification....................................................................................................................................368
Classification Overview ...............................................................................................................................368
Configuring Ingress Path Classification on a Logical Interface ....................................................................369
Modifying the C-VLAN 802.1Q UP and CFI Bit Classification Table .............................................................371
Modifying the S-VLAN 802.1 UP and DEI Bit Classification Table ................................................................372
Modifying the DSCP Classification Table .....................................................................................................373
Modifying the MPLS EXP Bit Classification Table ........................................................................................376
Modifying the MAC DA Classification Table ................................................................................................378

Phn 3963 013v000

Page v
Contents

Configuring Policers (Rate Metering) ..................................................................................................................380

Policer (Rate Metering) Overview ...............................................................................................................380
Configuring Policer Profiles .........................................................................................................................380
Assigning Policers to Interfaces ...................................................................................................................383
Configuring the Ingress and Egress Byte Compensation .............................................................................386
Configuring Marking ...........................................................................................................................................387
Marking Overview .......................................................................................................................................387
Enabling Marking.........................................................................................................................................387
Modifying the 802.1Q Marking Table .........................................................................................................387
Modifying the 802.1AD Marking Table .......................................................................................................389
Configuring WRED...............................................................................................................................................391
WRED Overview ..........................................................................................................................................391
Configuring WRED Profiles ..........................................................................................................................391
Assigning WRED Profiles to Queues ............................................................................................................394
Configuring Egress Shaping .................................................................................................................................395
Egress Shaping Overview.............................................................................................................................395
Configuring Queue Shaper Profiles .............................................................................................................395
Configuring Service Bundle Shaper Profiles ................................................................................................397
Assigning a Queue Shaper Profile to a Queue .............................................................................................399
Assigning a Service Bundle Shaper Profile to a Service Bundle ...................................................................401
Configuring Scheduling .......................................................................................................................................404
Scheduling Overview ...................................................................................................................................404
Configuring Priority Profiles ........................................................................................................................404
Configuring WFQ Profiles ............................................................................................................................408
Assigning a Priority Profile to an Interface ..................................................................................................410
Assigning a WFQ Profile to an Interface ......................................................................................................410
Configuring and Displaying Queue-Level PMs ....................................................................................................412
Chapter 8: Ethernet Protocols ..................................................................................................................... 416
ETH-BN Overview ........................................................................................................................................425
Adding an ETH-BN entity .............................................................................................................................425
Editing an ETH-BN Entity .............................................................................................................................428
Deleting an ETH-BN Entity ...........................................................................................................................428
Viewing the Statistics for an ETH-BN Entity ................................................................................................428
Configuring Adaptive Bandwidth Notification (ABN) ..........................................................................................430
Adaptive Bandwidth Notification Overview ................................................................................................430
Adding an ABN entity ..................................................................................................................................430
Editing an ABN Entity ..................................................................................................................................432
Deleting an ABN Entity ................................................................................................................................432
Viewing the Statistics for an ABN Entity ......................................................................................................433
Configuring LLDP .................................................................................................................................................435
LLDP Overview.............................................................................................................................................435
Displaying Peer Status .................................................................................................................................435

Phn 3963 013v000

Page vi
Contents

Configuring the General LLDP Parameters ..................................................................................................436

Configuring the LLDP Port Parameters ........................................................................................................438
Displaying the Unit’s Management Parameters..........................................................................................441
Displaying Peer Unit’s Management Parameters........................................................................................444
Displaying the Local Unit’s Parameters .......................................................................................................446
Displaying LLDP Statistics ............................................................................................................................450
Chapter 9: Synchronization ......................................................................................................................... 454
Configuring the SyncE Regenerator ....................................................................................................................455
Configuring the Sync Source ...............................................................................................................................457
Viewing the Sync Source Status ..................................................................................................................457
Adding a Sync Source ..................................................................................................................................458
Editing a Sync Source...................................................................................................................................459
Deleting a Sync Source ................................................................................................................................460
Configuring the Outgoing Clock and SSM Messages ..........................................................................................461
Configuring 1588 Transparent Clock ...................................................................................................................463
Chapter 10: Access Management and Security ............................................................................................ 466
Quick Security Configuration ..............................................................................................................................467
Quick Security Configuration – General Parameters Page ..........................................................................467
Quick Security Configuration – Protocols Page ...........................................................................................468
Quick Security Configuration – Access Control Page...................................................................................469
Quick Security Configuration – RSA Key & Certificate Page ........................................................................470
Configuring the General Access Control Parameters..........................................................................................471
Configuring the Password Security Parameters..................................................................................................473
Configuring the Session Timeout ........................................................................................................................475
Configuring Users ................................................................................................................................................476
User Configuration Overview ......................................................................................................................476
Configuring User Profiles .............................................................................................................................476
Configuring Users ........................................................................................................................................479
Configuring RADIUS ............................................................................................................................................482
RADIUS Overview ........................................................................................................................................482
Activating RADIUS Authentication ..............................................................................................................482
Configuring the RADIUS Server Attributes ..................................................................................................483
Viewing RADIUS User Permissions and Connectivity ..................................................................................484
Configuring a RADIUS Server .......................................................................................................................486
Configuring X.509 CSR Certificates and HTTPS ...................................................................................................509
Generating a Certificate Signing Request (CSR) File ....................................................................................509
Downloading a Certificate ...........................................................................................................................511
Enabling HTTPS ............................................................................................................................................513
Downloading and Installing an RSA Key ..............................................................................................................514
Downloading an RSA Key via HTTP or HTTPS ..............................................................................................515
Downloading an RSA Key via SFTP...............................................................................................................516
Blocking Telnet Access ........................................................................................................................................518

Phn 3963 013v000

Page vii
Contents

Uploading the Security Log .................................................................................................................................519

Uploading the Configuration Log ........................................................................................................................521
Chapter 11: Alarm Management and Troubleshooting ................................................................................ 524
Viewing Current Alarms ......................................................................................................................................525
Viewing Alarm Statistics......................................................................................................................................527
Viewing and Saving the Event Log ......................................................................................................................528
Editing Alarm Text and Severity and Disabiling Alarms and Events ....................................................................530
Displaying Alarm Information .....................................................................................................................530
Viewing the Probable Cause and Corrective Actions for an Alarm Type.....................................................531
Editing an Alarm Type and Disabiling Alarms and Events ...........................................................................531
Setting Alarms to their Default Values ........................................................................................................533
Configuring Voltage Alarm Thresholds and Displaying Voltage PMs ..................................................................534
Uploading Unit Info .............................................................................................................................................537
Performing Diagnostics .......................................................................................................................................541
Performing Radio Loopback ........................................................................................................................541
Performing Ethernet Loopback ...................................................................................................................542
Configuring Service OAM (SOAM) Fault Management (FM) .......................................................................543
Chapter 12: Web EMS Utilities .................................................................................................................... 561
Restarting the HTTP Server .................................................................................................................................562
Calculating an ifIndex ..........................................................................................................................................562
Displaying, Searching, and Saving a list of MIB Entities ......................................................................................564
Chapter 13: Getting Started (CLI) ................................................................................................................ 565
General (CLI) .......................................................................................................................................................566
Establishing a Connection (CLI) ...........................................................................................................................566
PC Setup (CLI) ..............................................................................................................................................566
Logging On (CLI) ..................................................................................................................................................567
General CLI Commands .......................................................................................................................................568
Changing Your Password (CLI) ............................................................................................................................569
Mate Management Access (IP Forwarding) (CLI) ................................................................................................570
Configuring In-Band Management (CLI)..............................................................................................................572
Changing the Management IP Address (CLI).......................................................................................................573
Configuring the Activation Key (CLI) ...................................................................................................................575
Activation Key Overview (CLI) .....................................................................................................................575
Viewing the Activation Key Status Parameters (CLI) ...................................................................................575
Entering the Activation Key (CLI) .................................................................................................................575
Activating a Demo Mode (CLI) .....................................................................................................................576
Activation Key Reclaim (CLI) ........................................................................................................................576
Displaying a List of Activation-Key-Enabled Features (CLI) .........................................................................577
Setting the Time and Date (Optional) (CLI) .........................................................................................................578
Setting the Daylight Savings Time (CLI) .......................................................................................................579
Enabling the Interfaces (CLI) ...............................................................................................................................580
Configuring the Radio Parameters (CLI) ..............................................................................................................582

Phn 3963 013v000

Page viii
Contents

Entering Radio View (CLI) ............................................................................................................................582

Muting and Unmuting a Radio (CLI) ............................................................................................................582
Configuring the Transmit (TX) Level (CLI) ....................................................................................................583
Configuring the Transmit (TX) Frequency (CLI) ...........................................................................................584
Configuring the Radio (MRMC) Script(s) (CLI) .....................................................................................................585
Displaying Available MRMC Scripts (CLI) .....................................................................................................585
Assigning an MRMC Script to a Radio Carrier (CLI) .....................................................................................586
Configuring the Radio Parameters (CLI) ......................................................................................................588
Enabling ACM with Adaptive Transmit Power (CLI) ............................................................................................543
Configuring the RSL Threshold Alarm (CLI) .........................................................................................................544
Operating in FIPS Mode (CLI) ..............................................................................................................................545
Requirements for FIPS Compliance (CLI) .....................................................................................................545
Enabling FIPS Mode (CLI) .............................................................................................................................545
Encrypting the External Protection Link (CLI) ..............................................................................................546
Initial Configuration of FIPS-Compliant Unit Redundancy Configuration (CLI) ...........................................546
Configuring Grouping (Optional) (CLI) ................................................................................................................548
Creating Service(s) for Traffic (CLI) .....................................................................................................................549
Chapter 14: Configuration Guide (CLI) ......................................................................................................... 550
System Configurations (CLI) ................................................................................................................................551
Configuring Multi-Carrier ABC (CLI) ....................................................................................................................552
Multi-Carrier ABC Overview (CLI) ................................................................................................................552
Configuring a Multi-Carrier ABC Group (CLI) ...............................................................................................552
Configuring the Multi-Carrier ABC Minimum Bandwidth Override Option (CLI) ........................................553
Removing Members from a Multi-Carrier ABC Group (CLI) ........................................................................554
Deleting a Multi-Carrier ABC Group (CLI) ....................................................................................................554
Configuring Multiband (Enhanced Multi-Carrier ABC) (CLI) ...............................................................................556
Configuring Synchronization in a Multiband Node (CLI) .............................................................................558
Deleting a Multiband Group (CLI)................................................................................................................558
Displaying Multiband Group Statistics (CLI) ................................................................................................558
Configuring Link Aggregation (LAG) and LACP (Optional) (CLI) ...........................................................................559
LAG Overview (CLI) ......................................................................................................................................559
Configuring a LAG Group (CLI) .....................................................................................................................560
Configuring LACP (CLI) .................................................................................................................................560
Viewing LAG Details (CLI) ............................................................................................................................561
Editing and Deleting a LAG Group (CLI) .......................................................................................................561
Enabling and Disabling the LAG Group Shutdown in Case of Degradation Event Option (CLI) ...................563
Configuring Enhanced LAG Distribution (CLI) ..............................................................................................564
Displaying LACP Parameters and Staistics (CLI) ...........................................................................................565
Configuring XPIC (CLI) .........................................................................................................................................570
XPIC Overview (CLI) .....................................................................................................................................570
Configuring the Radio Carriers for XPIC (CLI) ..............................................................................................570
Creating an XPIC Group (CLI) .......................................................................................................................571

Phn 3963 013v000

Page ix
Contents

Performing Antenna Alignment for XPIC (CLI).............................................................................................571

Configuring Unit Protection with HSB Radio Protection (External Protection) (CLI) ..........................................573
Unit Protection Overview (CLI) ....................................................................................................................573
Configuring Ethernet Interface Protection (CLI) ..........................................................................................574
Configuring HSB Radio Protection (CLI) .......................................................................................................575
Configuring 2+2 HSB Protection on a PTP 820C/PTP 820C-HP Unit (CLI) ....................................................576
Viewing the Configuration of the Standby unit (CLI) ...................................................................................576
Editing Standby Unit Settings (CLI) ..............................................................................................................576
Viewing Link and Protection Status and Activity (CLI) .................................................................................577
Manually Switching to the Standby Unit (CLI) .............................................................................................577
Disabling Automatic Switchover to the Standby Unit (CLI) .........................................................................578
Disabling Unit Protection (CLI) ....................................................................................................................578
Configuring 1+1 HSB with Space Diversity (CLI) ..........................................................................................578
Configuring MIMO and Space Diversity (CLI) ......................................................................................................580
MIMO and Space Diversity Overview (CLI) ..................................................................................................580
Upgrading a 4x4 MIMO Link from an Earlier Version to System Release 10.5 or Higher (CLI)....................581
Configuring a 4x4 MIMO Link (CLI) ..............................................................................................................582
Configuring a 2x2 MIMO Link (CLI) ..............................................................................................................583
Configuring a 1+0 or 2+2 Space Diversity Link (CLI) ....................................................................................584
Viewing MMI Levels (CLI) ............................................................................................................................584
Deleting a 4x4 MIMO Group (CLI) ...............................................................................................................586
Deleting a 2x2 MIMO or Space Diversity Group (CLI)..................................................................................586
Configuring Advanced Space Diversity (ASD) (CLI)..............................................................................................587
Configuring an ASD Link (CLI) ......................................................................................................................587
Viewing ASD Status (CLI) .............................................................................................................................589
Deleting an ASD Group (CLI) ........................................................................................................................590
Configuring Advanced Frequency Reuse (AFR) (CLI) ...........................................................................................592
Initial Link Configuration and Alignment for AFR (CLI) ................................................................................592
Software Configuration for AFR (CLI) ..........................................................................................................592
Deleting an AFR Group (CLI) ........................................................................................................................593
Operating a PTP 820C/PTP 820C-HP in Single Radio Carrier Mode (CLI) ............................................................595
Chapter 15: Unit Management (CLI) ............................................................................................................ 596
Defining the IP Protocol Version for Initiating Communications (CLI) ................................................................597
Configuring the Remote Unit’s IP Address (CLI)..................................................................................................598
Configuring the Remote Radio's IP Address in IPv4 format (CLI) ................................................................598
Configuring the Remote Radio's IP Address in IPv6 format (CLI) ................................................................599
Configuring SNMP (CLI) .......................................................................................................................................600
Configuring Basic SNMP Settings (CLI) ........................................................................................................600
Configuring SNMPv3 (CLI) ...........................................................................................................................601
Displaying the SNMP Settings (CLI) .............................................................................................................602
Configuring Trap Managers (CLI) .................................................................................................................603
Configuring the Internal Ports for FTP or SFTP (CLI) ...........................................................................................606

Phn 3963 013v000

Page x
Contents

Upgrading the Software (CLI) ..............................................................................................................................607

Software Upgrade Overview (CLI) ...............................................................................................................607
Viewing Current Software Versions (CLI) ....................................................................................................607
Configuring a Software Download (CLI) ......................................................................................................608
Downloading a Software Package (CLI) .......................................................................................................609
Installing and Upgrading Software (CLI) ......................................................................................................610
Backing Up and Restoring Configurations (CLI) ..................................................................................................611
Configuration Management Overview (CLI) ................................................................................................611
Setting the Configuration Management Parameters (CLI) ..........................................................................612
Backing up and Exporting a Configuration File (CLI)....................................................................................613
Importing and Restoring a Configuration File (CLI) .....................................................................................614
Editing CLI Scripts (CLI) ................................................................................................................................615
Setting the Unit to the Factory Default Configuration (CLI)................................................................................616
Performing a Hard (Cold) Reset (CLI) ..................................................................................................................617
Configuring Unit Parameters (CLI) ......................................................................................................................618
Configuring NTP (CLI) ..........................................................................................................................................620
Displaying Unit Inventory (CLI) ...........................................................................................................................621
Displaying SFP DDM and Inventory Information (CLI) ........................................................................................621
Displaying Static Information about an SFP Module (CLI) ...........................................................................622
Displaying Dynamic (DDM) Information about an SFP Module (CLI) ..........................................................623
Displaying DDM PMs about an SFP Module (CLI) ........................................................................................624
Chapter 16: Radio Configuration (CLI) ......................................................................................................... 626
Viewing and Configuring the Remote Radio Parameters (CLI) ...........................................................................627
Displaying Communication Status with the Remote Radio (CLI) .................................................................627
Displaying the Remote Radio’s Link ID (CLI) ................................................................................................627
Muting and Unmuting the Remote Radio (CLI) ...........................................................................................627
Displaying the Remote Radio’s RX Level (CLI) .............................................................................................628
Configuring the Remote Radio’s TX Level (CLI) ...........................................................................................628
Configuring Remote ATPC (CLI) ...................................................................................................................628
Configuring Header De-Duplication (CLI) ............................................................................................................633
Displaying Header De-Duplication Information (CLI) ..................................................................................634
Configuring Frame Cut-Through (CLI) .................................................................................................................636
Displaying Frame Cut-Through Information (CLI) ........................................................................................636
Configuring AES-256 Payload Encryption (CLI) ...................................................................................................638
Configuring and Viewing Radio PMs and Statistics (CLI) .....................................................................................642
Displaying General Modem Status and Defective Block PMs (CLI) .............................................................642
Displaying Excessive BER (Aggregate) PMs (CLI) .........................................................................................643
Displaying BER Level and Configuring BER Parameters (CLI).......................................................................644
Configuring RSL Thresholds (CLI) .................................................................................................................645
Configuring TSL Thresholds (CLI) .................................................................................................................645
Displaying RSL and TSL Levels (CLI)..............................................................................................................647
Configuring the Signal Level Threshold (CLI) ...............................................................................................648

Phn 3963 013v000

Page xi
Contents

Configuring the MSE Thresholds and Displaying the MSE PMs (CLI)...........................................................649
Configuring the XPI Thresholds and Displaying the XPI PMs (CLI)...............................................................651
Displaying ACM PMs (CLI)............................................................................................................................654
Chapter 17: Ethernet Services and Interfaces (CLI) ...................................................................................... 657
Configuring Ethernet Services (CLI).....................................................................................................................658
Ethernet Services Overview (CLI) ................................................................................................................658
General Guidelines for Provisioning Ethernet Services (CLI) .......................................................................658
Defining Services (CLI) .................................................................................................................................659
Configuring Service Points (CLI)...................................................................................................................664
Appendix A: Configuring C-VLAN CoS Preservation (CLI) ............................................................................... 677
Appendix B: Configuring C-VLAN Preservation (CLI) ..................................................................................... 678
Appendix C: Configuring S-VLAN CoS Preservation (CLI) ............................................................................... 678
Defining the MAC Address Forwarding Table for a Service (CLI).................................................................684
Setting the MRU Size and the S-VLAN Ethertype (CLI)........................................................................................688
Configuring the S-VLAN Ethertype (CLI) ......................................................................................................688
Configuring the C-VLAN Ethertype (CLI) ......................................................................................................689
Configuring the MRU (CLI) ...........................................................................................................................689
Configuring Ethernet Interfaces (CLI)..................................................................................................................689
Entering Interface View (CLI) .......................................................................................................................690
Displaying the Operational State of the Interfaces in the Unit (CLI) ...........................................................692
Viewing Interface Attributes (CLI) ...............................................................................................................692
Configuring an Interface’s Media Type (CLI) ...............................................................................................692
Configuring an Interface’s Speed and Duplex State (CLI) ............................................................................693
Configuring an Interface’s Auto Negotiation State (CLI) .............................................................................694
Configuring an Interface’s IFG (CLI) .............................................................................................................694
Configuring an Interface’s Preamble (CLI) ...................................................................................................695
Adding a Description for the Interface (CLI) ................................................................................................695
Displaying Interface Statistics (RMON) (CLI) ...............................................................................................696
Configuring Automatic State Propagation and Link Loss Forwarding (CLI).........................................................697
Viewing Ethernet PMs and Statistics (CLI) ..........................................................................................................703
Displaying RMON Statistics (CLI) .................................................................................................................703
Configuring Ethernet Port PMs and PM Thresholds (CLI) ...........................................................................704
Displaying Ethernet Port PMs (CLI) .............................................................................................................704
Clearing Ethernet Port PMs (CLI) .................................................................................................................707
Chapter 18: Quality of Service (QoS) (CLI) ................................................................................................... 740
Configuring Classification (CLI)............................................................................................................................741
Classification Overview (CLI) .......................................................................................................................741
Configuring Ingress Path Classification on a Logical Interface (CLI) ............................................................741
Configuring VLAN Classification and Override (CLI) ....................................................................................742
Configuring 802.1p Classification (CLI) ........................................................................................................743
Configuring DSCP Classification (CLI) ...........................................................................................................747
Configuring MPLS Classification (CLI) ..........................................................................................................750

Phn 3963 013v000

Page xii
Contents

Configuring a Default CoS (CLI) ...................................................................................................................752

Configuring Ingress Path Classification on a Service Point (CLI) ..................................................................753
Configuring Ingress Path Classification on a Service (CLI) ...........................................................................753
Configuring Policers (Rate Metering) (CLI)..........................................................................................................754
Overview of Rate Metering (Policing) (CLI) .................................................................................................754
Configuring Rate Meter (Policer) Profiles (CLI) ...........................................................................................754
Displaying Rate Meter Profiles (CLI) ............................................................................................................756
Deleting a Rate Meter Profile (CLI)..............................................................................................................756
Attaching a Rate Meter (Policer) to an Interface (CLI) ................................................................................756
Configuring the Line Compensation Value for a Rate Meter (Policer) (CLI) ................................................761
Displaying Rate Meter Statistics for an Interface (CLI) ................................................................................763
Configuring Marking (CLI) ...................................................................................................................................766
Marking Overview (CLI) ...............................................................................................................................766
Configuring Marking Mode on a Service Point (CLI)....................................................................................766
Marking Table for C-VLAN UP Bits (CLI).......................................................................................................767
Marking Table for S-VLAN UP Bits (CLI) .......................................................................................................769
Configuring WRED (CLI).......................................................................................................................................771
WRED Overview (CLI) ..................................................................................................................................771
Configuring WRED Profiles (CLI) ..................................................................................................................771
Assigning a WRED Profile to a Queue (CLI) .................................................................................................773
Configuring Shapers (CLI) ....................................................................................................................................774
Overview of Egress Shaping (CLI) ................................................................................................................774
Configuring Service Bundle Shapers (CLI)....................................................................................................776
Configuring Egress Line Compensation for Shaping (CLI) ............................................................................779
Configuring Scheduling (CLI) ...............................................................................................................................780
Overview of Egress Scheduling (CLI)............................................................................................................780
Configuring Queue Priority (CLI)..................................................................................................................780
Configuring Interface Priority Profiles (CLI) .................................................................................................781
Attaching a Priority Profile to an Interface (CLI) .........................................................................................783
Configuring Weighted Fair Queuing (WFQ) (CLI) ........................................................................................784
Displaying Egress PMs and Statistics (CLI) ..........................................................................................................788
Displaying Queue-Level Statistics (CLI) ........................................................................................................788
Configuring and Displaying Queue-Level PMs (CLI).....................................................................................789
Displaying Service Bundle-Level PMs (CLI) ..................................................................................................784
Chapter 19: Ethernet Protocols (CLI) ........................................................................................................... 780
Configuring Adaptive Bandwidth Notification (ABN) (CLI) ..................................................................................808
Adaptive Bandwidth Notification Overview (CLI) ........................................................................................808
Configuring an ABN Entity (CLI) ...................................................................................................................808
Configuring Ethernet Bandwidth Notification (ETH-BN) (CLI) .....................................................................812
Configuring LLDP (CLI) .........................................................................................................................................751
Configuring the General LLDP Parameters (CLI) ..........................................................................................751
Displaying the General LLDP Parameters (CLI) ............................................................................................752

Phn 3963 013v000

Page xiii
Contents

Configuring LLDP Port Parameters (CLI) ......................................................................................................753

Displaying LLDP Port Parameters (CLI) ........................................................................................................754
Displaying LLDP Local System Parameters (CLI) ..........................................................................................754
Displaying the LLDP Remote System Parameters (CLI) ...............................................................................756
Displaying LLDP Statistics (CLI) ....................................................................................................................759
Chapter 20: Synchronization (CLI) ............................................................................................................... 762
Configuring SyncE Regenerator (CLI) ..................................................................................................................763
Changing the ETSI/ANSI Mode (CLI) ....................................................................................................................765
Configuring the Sync Source (CLI) .......................................................................................................................766
Configuring an Ethernet Interface as a Synchronization Source (CLI) .........................................................767
Configuring a Radio Interface as a Synchronization Source (CLI) ................................................................768
Clearing All Sync Sources (CLI).....................................................................................................................770
Configuring the Outgoing Clock (CLI) ..................................................................................................................771
Configuring SSM Messages (CLI) .........................................................................................................................773
Displaying Synchronization Status and Parameters (CLI)....................................................................................775
Configuring 1588 Transparent Clock (CLI)...........................................................................................................777
Chapter 21: Access Management and Security (CLI) .................................................................................... 780
Configuring the General Access Control Parameters (CLI)..................................................................................781
Configuring the Inactivity Timeout Period (CLI) ..........................................................................................781
Configuring Blocking Upon Login Failure (CLI) ............................................................................................781
Configuring Blocking of Unused Accounts (CLI) ..........................................................................................782
Configuring the Password Security Parameters (CLI) .........................................................................................784
Configuring Password Aging (CLI) ................................................................................................................784
Configuring Password Strength Enforcement (CLI) .....................................................................................784
Forcing Password Change Upon First Login (CLI) ........................................................................................785
Displaying the System Password Settings (CLI) ...........................................................................................786
Configuring Users (CLI)........................................................................................................................................787
User Configuration Overview (CLI) ..............................................................................................................787
Configuring User Profiles (CLI).....................................................................................................................787
Configuring User Accounts (CLI) ..................................................................................................................789
Configuring RADIUS (CLI) ....................................................................................................................................791
RADIUS Overview (CLI) ................................................................................................................................791
Activating RADIUS Authentication (CLI) ......................................................................................................791
Configuring the RADIUS Server Attributes (CLI) ..........................................................................................791
Displaying Remote Access Users .................................................................................................................792
Configuring X.509 CSR Certificates and HTTPS (CLI) ...........................................................................................794
Generating a Certificate Signing Request (CSR) File (CLI) ............................................................................794
Downloading a Certificate (CLI) ...................................................................................................................796
Enabling HTTPS (CLI) ....................................................................................................................................797
Configuring HTTPS Cipher Hardening (CLI) .........................................................................................................799
Downloading and Installing an RSA Key (CLI) ......................................................................................................800
Blocking Telnet Access (CLI) ................................................................................................................................802

Phn 3963 013v000

Page xiv
Contents

Uploading the Security Log (CLI) .........................................................................................................................803

Uploading the Configuration Log (CLI) ................................................................................................................805
Enabling NETCONF (CLI) ......................................................................................................................................808
Terminating all Active Sessions (CLI) ...................................................................................................................809
Chapter 22: Alarm Management and Troubleshooting (CLI) ........................................................................ 810
Viewing Current Alarms (CLI) ..............................................................................................................................811
Viewing the Event Log (CLI) ................................................................................................................................812
Editing Alarm Text and Severity (CLI) ..................................................................................................................813
Displaying Alarm Information (CLI) .............................................................................................................813
Editing an Alarm Type (CLI) .........................................................................................................................813
Setting Alarms to their Default Values (CLI) ................................................................................................814
Configuring a Timeout for Trap Generation (CLI) ...............................................................................................815
Disabling Alarms and Events (CLI) .......................................................................................................................816
Configuring Voltage Alarm Thresholds and Displaying Voltage PMs (CLI) ..........................................................817
Uploading Unit Info (CLI).....................................................................................................................................819
Activating the Radio Logger (CLI) ........................................................................................................................822
Performing Diagnostics (CLI) ...............................................................................................................................823
Performing Radio Loopback (CLI) ................................................................................................................823
Performing Ethernet Loopback (CLI) ...........................................................................................................824
Configuring Service OAM (SOAM) Fault Management (FM) (CLI) ......................................................................826
SOAM Overview (CLI) ..................................................................................................................................826
Configuring MDs (CLI) ..................................................................................................................................827
Configuring MA/MEGs (CLI) ........................................................................................................................828
Configuring MEPs (CLI) ................................................................................................................................830
Displaying MEP and Remote MEP Attributes (CLI) ......................................................................................833
Displaying Detailed MEP Error Information (CLI) ........................................................................................836
Performing Loopback (CLI) ..........................................................................................................................837
Working in CW Mode (Single or Dual Tone) (CLI) ...............................................................................................841
Chapter 23: Maintenance ........................................................................................................................... 842
Temperature Ranges...........................................................................................................................................843
Troubleshooting Tips ...................................................................................................................................843
PTP 820C Connector Pin-outs .............................................................................................................................845
Eth1/PoE - GbE Electrical+PoE/Optical........................................................................................................845
Eth2 - GbE Electrical/Optical .......................................................................................................................846
MIMO Port ..................................................................................................................................................846
Troubleshooting Tips ..........................................................................................................................................847
DC ................................................................................................................................................................847
RSL Interface................................................................................................................................................848
Source Sharing .............................................................................................................................................848
PTP 820C LEDs.....................................................................................................................................................849
Electrical GbE Interface (RJ-45) LEDs ...........................................................................................................849
Optical GbE Interface (SFP) LEDs .................................................................................................................849

Phn 3963 013v000

Page xv
Contents

Management FE Interface (RJ-45) LEDs ......................................................................................................849

Status LED ....................................................................................................................................................850
Protection LED .............................................................................................................................................850
PTP 820C-HP Connector Pin-outs .......................................................................................................................851
Data Port 1 - GbE Electrical (RJ-45) .............................................................................................................851
Management Port (FE-Standard) and Protection (FE-Non-Standard) .........................................................852
DC ................................................................................................................................................................852
RSL Interface................................................................................................................................................852
Source Sharing .............................................................................................................................................853
PTP 820C-HP LEDs ...............................................................................................................................................854
Electrical GbE Interface (RJ-45) LEDs ...........................................................................................................854
Optical GbE Interface (SFP) LEDs .................................................................................................................854
Management FE Interface (RJ-45) LEDs ......................................................................................................854
Radio LED.....................................................................................................................................................855
Status LED ....................................................................................................................................................855
Protection LED .............................................................................................................................................855
PTP 820S Connector Pin-outs .............................................................................................................................856
Eth1/PoE - GbE Electrical+PoE/Optical........................................................................................................856
Eth2 - GbE Electrical/Optical .......................................................................................................................857
Eth3 - GbE Electrical/Optical .......................................................................................................................857
MGT/PROT - Management (FE-Standard) and Protection (FE-Non-Standard) ...........................................858
DC ................................................................................................................................................................858
RSL Interface................................................................................................................................................858
PTP 820S LEDs .....................................................................................................................................................859
Electrical GbE Interface (RJ-45) LEDs ...........................................................................................................859
Optical GbE Interface (SFP) LEDs .................................................................................................................859
Management FE Interface (RJ-45) LEDs ......................................................................................................860
Radio LED.....................................................................................................................................................860
Status LED ....................................................................................................................................................860
Protection LED .............................................................................................................................................860
PTP 820E Connector Pin-outs .............................................................................................................................861
PTP 820E Interfaces – ESE ...........................................................................................................................862
PTP 820E Interfaces – ESP ...........................................................................................................................863
Eth2/Eth3 GbE Optical Interface (SFP/CSFP) ...............................................................................................864
Eth1 10G Optical Interface (SFP+) (ESP only) ..............................................................................................864
MGT GbE Electrical Interface (RJ-45)...........................................................................................................864
EXT Port .......................................................................................................................................................864
Power Adaptor ............................................................................................................................................865
RSL Interface................................................................................................................................................865
PTP 820E LEDs .....................................................................................................................................................866
Eth1/PoE GbE Interface (RJ-45) LEDs (ESE only)..........................................................................................866
Eth1 10G Optical Interface (SFP+) LEDs (ESP only) ......................................................................................866

Phn 3963 013v000

Page xvi
Contents

Eth2/Eth3 GbE Optical Interface (SFP/CSFP) LEDs ......................................................................................866

MGT GbE Electrical Interface (RJ-45) LEDs ..................................................................................................867
Radio LED.....................................................................................................................................................867
Status LED ....................................................................................................................................................867
Protection LED .............................................................................................................................................868
PoE Injector Pin-outs...........................................................................................................................................868
PoE Port .......................................................................................................................................................868
Data Port .....................................................................................................................................................869
DC ................................................................................................................................................................869
PoE Injector LEDs ................................................................................................................................................869
Radio LED.....................................................................................................................................................869
Chapter 24: Alarms List ............................................................................................................................... 871
Glossary .............................................................................................................................................................. I

Phn 3963 013v000

Page xvii
Contents

List of Figures
Figure 1 Main Web EMS Page .....................................................................................................................................14
Figure 2 Displaying a Representation of the Front Panel ...........................................................................................15
Figure 3: Main Web EMS Page with Representation of Front Panel – PTP 820C and PTP 820S ..................................15
Figure 4: Main Web EMS Page with Representation of Front Panel – PTP 820C-HP ................................................15
Figure 5 Main Web EMS Page with Representation of Front Panel – PTP -820E ......................................................16
Figure 6 Main Web EMS Page with Active and Standby Tabs ....................................................................................17
Figure 7 Related Pages Drop-Down List ......................................................................................................................18
Figure 8 Unit Summary Page ......................................................................................................................................21
Figure 9 Unit Summary Page – Customizing Columns ................................................................................................21
Figure 10 Radio Summary Page ..................................................................................................................................22
Figure 11 Radio Summary Page- Customizing Columns .............................................................................................22
Figure 12: Security Summary Page ..............................................................................................................................23
Figure 13: Security Summary Page – FIPS Security Warnings......................................................................................24
Figure 14: Security Summary Page – Customizing Columns ........................................................................................25
Figure 15 Internet Protocol Properties Window ......................................................................................................105
Figure 16 Login Page .................................................................................................................................................106
Figure 17 Change User Password Page.....................................................................................................................109
Figure 18: Quick Configuration – From File Page ......................................................................................................110
Figure 19: Quick Configuration – From File Page – Configuration File Loaded .........................................................111
Figure 20 Quick Configuration – Platform Setup Page .............................................................................................112
Figure 21 Quick Configuration– Platform Setup Summary Page ..............................................................................114
Figure 22 Local Networking Configuration Page.......................................................................................................117
Figure 23 Activation Key Configuration Page ...........................................................................................................119
Figure 24 Activation Key Overview Page ..................................................................................................................121
Figure 25 Time Services Page....................................................................................................................................126
Figure 26 Interface Manager Page............................................................................................................................128
Figure 27 Interface Manager – Edit Page..................................................................................................................128
Figure 28 Multiple Selection Operation Section (Interface Manager Page) .............................................................129
Figure 29: Traffic over Management Page ................................................................................................................132
Figure 30 MRMC Symmetrical Scripts Page (ETSI) ....................................................................................................133
Figure 31 MRMC Symmetrical Scripts Page (PTP 820C) (ETSI) .................................................................................134
Figure 32 MRMC Symmetrical Scripts Page (PTP 820C) (FCC) ..................................................................................134
Figure 33 MRMC Symmetrical Scripts Page (Configuration) – PTP 820C..................................................................135
Figure 34 MRMC Symmetrical Scripts Page – Configuration – Adaptive Mode (PTP 820C) .....................................136
Figure 35 Frequency Scanner Page – PTP820E – Single Mode ..................................................................................139
Figure 36 Frequency Scanner Results – Graph Format (PTP 820E – Single Mode)....................................................141
Figure 37 Radio Parameters Page – PTP 820C/PTP 820C-HP.....................................................................................143
Figure 38 Radio Parameters Page Per Carrier – PTP 820C/PTP 820C-HP ..................................................................144
Figure 39 Radio Parameters Page Per Carrier – PTP 820C ........................................................................................149
Figure 40 Security General Configuration Page ........................................................................................................151
Figure 41: Unit Redundancy Page ..............................................................................................................................152

Phn 3963 013v000

Page xviii
Contents

Figure 42 1+0 Quick Configuration Wizard – Page 1 ................................................................................................177

Figure 43 1+0 Quick Configuration Wizard – Page 2 ................................................................................................177
Figure 44: 1+0 Quick Configuration Wizard – Page 3 ................................................................................................178
Figure 45 1+0 Quick Configuration Wizard – Page 4 ................................................................................................180
Figure 46 1+0 Quick Configuration Wizard – Page 4 ................................................................................................181
Figure 47 1+0 Quick Configuration Wizard – Page 5 (Summary Page) .....................................................................182
Figure 48 1+0 Repeater Quick Configuration Wizard – Page 1.................................................................................182
Figure 49 1+0 Repeater Quick Configuration Wizard – Page 2.................................................................................182
Figure 50 1+0 Repeater Quick Configuration Wizard – Page 3.................................................................................184
Figure 51 1+0 Repeater Quick Configuration Wizard – Page 4.................................................................................184
Figure 52 1+0 Repeater Quick Configuration Wizard – Page 5.................................................................................185
Figure 53 1+0 Repeater Quick Configuration Wizard – Page 6.................................................................................187
Figure 54: 2 X (1 + 0) Quick Configuration Wizard – Page 1 ......................................................................................188
Figure 55: 2X (1 + 0) Quick Configuration Wizard – Page 2 .......................................................................................189
Figure 56: 2X (1 + 0) Quick Configuration Wizard – Page 3 .......................................................................................189
Figure 57: 2X (1 + 0) Quick Configuration Wizard – Page 4 .......................................................................................191
Figure 58: 2X (1 + 0) Quick Configuration Wizard – Page 5 .......................................................................................191
Figure 59: 2X (1 + 0) Quick Configuration Wizard – Page 5 .......................................................................................192
Figure 60: 2X (1 + 0) Quick Configuration Wizard – Page 6 (Non-XPIC).....................................................................192
Figure 61: 2 X (1 + 0) Quick Configuration Wizard – Page 7 (XPIC) ............................................................................193
Figure 62: 2 X (1 + 0) Quick Configuration Wizard – Page 7 (Non-XPIC) ....................................................................193
Figure 63: X (1 + 0) Quick Configuration Wizard – Page 8 .........................................................................................194
Figure 64: 2 X (1 + 0) Quick Configuration Wizard – Page 9 .....................................................................................195
Figure 65: 2 X (1 + 0) Quick Configuration Wizard –Summary Page (XPIC) ..............................................................196
Figure 66: 2 X (1 + 0) Quick Configuration Wizard –Summary Page (No XPIC) ..........................................................196
Figure 67 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Page 1..................................................................198
Figure 68 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio #2 Selection Page ......................................199
Figure 69 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio XPIC Configuration Page ...........................199
Figure 70 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio Parameters Configuration Page ................200
Figure 71 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio Parameters Configuration Page (XPIC) .....200
Figure 72 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio MRMC Script Configuration Page .............201
Figure 73 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio MRMC Script Configuration Page - XPIC ...201
Figure 74 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Management Configuration Page .......................202
Figure 75 2 + 0 Multi Carrier ABC Quick Configuration Wizard –Summary Page .....................................................203
Figure 76: Multiband Quick Configuration Wizard – Page 1 .....................................................................................204
Figure 77: Multiband Quick Configuration Wizard – Page 2 .....................................................................................204
Figure 78: Multiband Quick Configuration Wizard – Page 3 .....................................................................................205
Figure 79: Multiband Quick Configuration Wizard – Page 4 .....................................................................................206
Figure 80: Multiband Quick Configuration Wizard – Page 5 .....................................................................................207
Figure 81: Multiband Quick Configuration Wizard – Summary Page .......................................................................208
Figure 82: Bandwidth Notification Page (Empty) ......................................................................................................209
Figure 83: Bandwidth Notification – Add Page ..........................................................................................................209

Phn 3963 013v000

Page xix
Contents

Figure 84: Bandwidth Notification Page (Populated with Radio BNM) .....................................................................210
Figure 85 Multi-Carrier ABC Group Page (Empty) ....................................................................................................212
Figure 86 Create ABC Group Wizard – First Page .....................................................................................................212
Figure 87 Create ABC Group Wizard – Second Page.................................................................................................213
Figure 88 Create ABC Group Wizard – Finish Page ...................................................................................................213
Figure 89 Multi-Carrier ABC Group – Edit Group Page .............................................................................................215
Figure 90 Multi Carrier ABC Group - Add/Remove Members Page ..........................................................................216
Figure 91 Multiband Operation – PTP 820E and PTP 820C/PTP 820C-HP .................................................................219
Figure 92 Multiband Operation – PT 820E and Third-Party Unit ...............................................................................220
Figure 93 Multi Carrier ABC Groups Page (Empty) ....................................................................................................221
Figure 94 Create ABC Group Wizard – Page 1 ...........................................................................................................221
Figure 95 Create ABC Group Wizard – Page 2 ...........................................................................................................222
Figure 96 Create ABC Group Wizard – Page 3 ...........................................................................................................222
Figure 97 Create ABC Group Wizard – Page 3 ...........................................................................................................223
Figure 98 Multi Carrier ABC Groups Page (Populated with Multiband Group) .........................................................224
Figure 99 Bandwidth Notification Page (Empty) .......................................................................................................224
Figure 100 Bandwidth Notification – Add Page .........................................................................................................225
Figure 101 Bandwidth Notification Page (Populated with Radio BNM) ....................................................................226
Figure 102 Multiband Cable for Use with CSFP Port .................................................................................................227
Figure 103 Multiband Configuration with Inband Management and/or SyncE via the PTP 820E .............................228
Figure 104 Multiband Configuration with Direct Inband Management to the Paired Unit ......................................229
Figure 105 Multiband Configuration with Direct Inband Management to the PTP 820C, PTP 820C-HP, or PTP 820S
............................................................................................................................................................................230
Figure 106 Create LAG Group – Page 1.....................................................................................................................233
Figure 107 Create LAG Group – Page 2.....................................................................................................................234
Figure 108 Create LAG Group – Final Page ...............................................................................................................234
Figure 109 Link Aggregation - Edit Page ...................................................................................................................235
Figure 110 Link Aggregation - Edit Page ...................................................................................................................237
Figure 111 LACP Aggregation Page ...........................................................................................................................238
Figure 112 LACP Port Staus Page ..............................................................................................................................239
Figure 113 LACP Port Status – View Page .................................................................................................................240
Figure 114 LACP Port Statistics Page ........................................................................................................................242
Figure 115 LACP Port Debug Page ............................................................................................................................243
Figure 116 XPIC Configuration Page .........................................................................................................................245
Figure 117 Logical Interfaces – Edit Page .................................................................................................................249
Figure 118 Unit Redundancy Page ............................................................................................................................250
Figure 119 Unit Redundancy Page when Redundancy Enabled ...............................................................................250
Figure 120 Interface Manager Page – Both Radio Carriers Enabled .........................................................................252
Figure 121 Standby Tab of Radio Parameters Page ..................................................................................................252
Figure 122 Unit Redundancy Page ............................................................................................................................253
Figure 123 Create Space Diversity Group- Page 1. ...................................................................................................255
Figure 124 Create Space Diversity Group- Selection Summary ................................................................................256
Figure 125 Diversity - Edit Page (Space Diversity Group) .........................................................................................256

Phn 3963 013v000

Page xx
Contents

Figure 126: Advanced Multi Carrier Configuration Page ..........................................................................................261

Figure 127: 4x4 MIMO Group – Select Group Parameters Page ...............................................................................261
Figure 128: 4x4 MIMO Group – Select Members Parameters Page ..........................................................................262
Figure 129: 4x4 MIMO Group – Select MRMC Parameters Page ..............................................................................263
Figure 130: 4x4 MIMO Group – Select Members Parameters Page ..........................................................................264
Figure 131: Advanced Multi Carrier Configuration Page (Populated – 4x4 MIMO Group) .......................................265
Figure 132: 4x4 MIMO Configuration ........................................................................................................................265
Figure 133: Create Diversity Group Page – 2x2 MIMO – Page 1 ...............................................................................266
Figure 134: Create Diversity Group Page – 2x2 MIMO – Page 2 ...............................................................................266
Figure 135: Diversity Groups – 2x2 MIMO - Edit Page...............................................................................................267
Figure 136: Create Diversity Group – Page 1 .............................................................................................................268
Figure 137: Create Diversity Group – Page 2 .............................................................................................................268
Figure 138: Diversity - Edit Page ................................................................................................................................269
Figure 139: 4x4 MIMO - Edit Members Page.............................................................................................................270
Figure 140: Diversity Groups - Edit Members Page ...................................................................................................270
Figure 141 Advanced Space Diversity (ASD) ..............................................................................................................272
Figure 142 ASD Data Paths ........................................................................................................................................273
Figure 143 Advanced Multi Carrier Configuration Page ............................................................................................275
Figure 144 AMCC Group - Select Group Parameters Page ........................................................................................275
Figure 145 AMCC Group - Select Members Parameters Page ...................................................................................276
Figure 146 AMCC Group - Select MRMC Parameters Page .......................................................................................277
Figure 147 Advanced Multi Carrier Configuration Page – Populated with ASD Group .............................................278
Figure 148 AMCC – ASD – Radio Members Page .......................................................................................................278
Figure 149 AFR 1+0 Deployment ..............................................................................................................................280
Figure 150 AFR 1+0 Configuration ............................................................................................................................281
Figure 151 Advanced Multi Carrier Configuration Page (Empty)..............................................................................282
Figure 152 AMCC Group – Select Group Parameters Page ......................................................................................282
Figure 153 AMCC Group – Select Group Parameters Page (Hub Site)......................................................................283
Figure 154 AMCC Group – Select Group Parameters Page (Tail Site).......................................................................284
Figure 155 AMCC Group – Selection Summary Page ................................................................................................285
Figure 156 Advanced Multi Carrier Configuration Page (Populated) .......................................................................286
Figure 157 AMCC Group – Edit Page ........................................................................................................................286
Figure 158 Local Networking Configuration Page ....................................................................................................289
Figure 159 Remote Networking Configuration Page – PTP 820C .............................................................................290
Figure 160 Remote Networking Configuration Page – PTP 820S and PTP 820E.......................................................291
Figure 161 Remote IP Configuration Page Per Carrier – PTP 820C and PTP 820C-HP ..............................................292
Figure 162 SNMP Parameters Page ..........................................................................................................................293
Figure 163 V3 Users Page .........................................................................................................................................294
Figure 164 V3 Users - Add Page ................................................................................................................................295
Figure 165 Trap Managers Page ...............................................................................................................................296
Figure 166 Trap Managers - Edit Page ......................................................................................................................297
Figure 167 FileZilla Server User Configuration .........................................................................................................300

Phn 3963 013v000

Page xxi
Contents

Figure 168 FileZilla Server Shared Folder Setup .......................................................................................................301

Figure 169 FTP Port Page ..........................................................................................................................................302
Figure 170 Versions Page..........................................................................................................................................303
Figure 171 Download & Install Page – HTTP/ HTTPS Download – No File Selected .................................................306
Figure 172 Download & Install page – HTTP/ HTTPS Download – File Selected.......................................................306
Figure 173 Download & Install Page - FTP ................................................................................................................307
Figure 174 FTP Parameters Page ..............................................................................................................................308
Figure 175 Install parameters Page. .........................................................................................................................311
Figure 176 Install parameters page- Software Management Timer. ........................................................................311
Figure 177 Backup Files Page....................................................................................................................................312
Figure 178 Configuration Management Page FTP/SFTP ...........................................................................................313
Figure 179 FTP Parameters Page ..............................................................................................................................314
Figure 180 Set to Factory Default Page ....................................................................................................................321
Figure 181 Reset Page ..............................................................................................................................................322
Figure 182 Unit Parameters Page .............................................................................................................................323
Figure 183 NTP Configuration Page ..........................................................................................................................325
Figure 184 Inventory Page ........................................................................................................................................278
Figure 185 SFP Alarm Example ..................................................................................................................................279
Figure 186 Radio Parameters Page – PTP 820C/PTP 820C-HP...................................................................................280
Figure 187 SFP PM Report Page ................................................................................................................................282
Figure 188: Login Banner Page ..................................................................................................................................284
Figure 189 Radio Parameters Page – PTP 820C/PTP 820C-HP .................................................................................286
Figure 190 Radio Parameters Page Per Carrier – PTP 820C/PTP 820C-HP ................................................................287
Figure 191 Remote Radio Parameters Page – PTP 820C/PTPT 820C-HP ..................................................................289
Figure 192 Remote Radio Parameters Page – PTP 820S /PTP 820E .........................................................................289
Figure 193: Remote Radio Parameters Page Per Carrier – PTP 820C ........................................................................290
Figure 194 ATPC Page – PTP 820C/PTP 820C-HP ......................................................................................................293
Figure 195 ATPC – Edit Page per Carrier – PTP 820C/PTP 820C-HP .........................................................................293
Figure 196 Radio Ethernet Interface Configuration Page – PTP 820C/PTP 820C-HP................................................295
Figure 197 Radio Ethernet Interface Configuration – Edit Page Per Carrier – PTP 820C/PTP 820C-HP ...................296
Figure 198 Radio Ethernet Interface Counters Page – PTP 820C/PTP 820C-HP .......................................................297
Figure 199 Radio Ethernet Interface Counters Page – Single-Carrier.......................................................................298
Figure 200 Radio Ethernet Interface Counters Page Per Carrier – PTP 820C/PTP 820C-HP .....................................299
Figure 201 Payload Encryption Page ........................................................................................................................302
Figure 202 Payload Encryption – Edit Page ..............................................................................................................302
Figure 203 Payload Encryption – Edit Page with Master Key Displayed...................................................................303
Figure 204 Radio BER Thresholds Page ....................................................................................................................306
Figure 205 Radio BER Thresholds – Edit Page ..........................................................................................................306
Figure 206 MRMC Status Page .................................................................................................................................307
Figure 207 MRMC PM Report Page ..........................................................................................................................309
Figure 208 Counters Page – Multi-Carrier ................................................................................................................311
Figure 209 Counters Page – Single-Carrier ...............................................................................................................312

Phn 3963 013v000

Page xxii
Contents

Figure 210 Counters Page Per Carrier – Multi-Carrier ..............................................................................................313

Figure 211 Signal Level PM Report Page ..................................................................................................................314
Figure 212 Signal Level Thresholds Configuration - Edit Page ..................................................................................315
Figure 213 Aggregate PM Report Page.....................................................................................................................316
Figure 214 MSE PM Report Page ..............................................................................................................................318
Figure 215 Modem MSE Thresholds Configuration – Edit Page ...............................................................................319
Figure 216 XPI PM Report Page ................................................................................................................................320
Figure 217 XPI Thresholds Configuration – Edit Page ...............................................................................................321
Figure 218 Capacity PM Report Page .......................................................................................................................322
Figure 219: Ethernet Radio Capacity and Throughput Threshold Page .....................................................................323
Figure 220 Utilization PM Report Page.....................................................................................................................324
Figure 221 Ethernet Radio Utilization Threshold Page .............................................................................................325
Figure 222 Frame Error PM Report Page ..................................................................................................................327
Figure 223 Ethernet Services Page ...........................................................................................................................331
Figure 224 Ethernet Services - Add page ..................................................................................................................333
Figure 225 Multiple Selection Operation Section (Ethernet Services) .....................................................................335
Figure 226 Ethernet Service Points Page ..................................................................................................................337
Figure 227 Ethernet Service Points Page – Ingress Attributes..................................................................................340
Figure 228 Ethernet Service Points Page – Egress Attributes ...................................................................................341
Figure 229 Ethernet Service Points - Add Page ........................................................................................................344
Figure 230 Attached VLAN List Page.........................................................................................................................346
Figure 231 Attached VLAN List - Add Page ...............................................................................................................347
Figure 232 Ethernet General Configuration Page.....................................................................................................349
Figure 233 Physical Interfaces Page .........................................................................................................................350
Figure 234 Physical Interfaces - Edit Page ................................................................................................................351
Figure 235 Automatic State Propagation Page..........................................................................................................354
Figure 236 Automatic State Propagation - Add Page ................................................................................................354
Figure 237 RMON Page.............................................................................................................................................356
Figure 238 RMON Page – Hiding and Displaying Columns .......................................................................................356
Figure 239 Egress Cos Statistics Page .......................................................................................................................358
Figure 240 Egress CoS Statistics – Edit Page .............................................................................................................359
Figure 241 Ethernet Port TX PM Report Page ..........................................................................................................359
Figure 242 Ethernet PM Port Admin Page ................................................................................................................361
Figure 243 Ethernet Port Tx Threshold Page ............................................................................................................362
Figure 244: Ethernet Port RX PM Report Page ..........................................................................................................363
Figure 245 Ethernet PM Port Admin Page .................................................................................................................364
Figure 246 Ethernet Port Rx Threshold Page ............................................................................................................364
Figure 247 QoS Block Diagram .................................................................................................................................366
Figure 248 Logical Interfaces Page ...........................................................................................................................369
Figure 249 Logical Interfaces - Edit Page ..................................................................................................................370
Figure 250 802.1Q Classification Page ......................................................................................................................372
Figure 251 802.1Q Classification - Edit Page ............................................................................................................372

Phn 3963 013v000

Page xxiii
Contents

Figure 252 802.1AD Classification Page....................................................................................................................373

Figure 253 802.1Q Classification - Edit Page ............................................................................................................373
Figure 254 DSCP Classification Page .........................................................................................................................374
Figure 255 DSCP Classification - Edit Page................................................................................................................374
Figure 256: DSCP Classification - Add Page ................................................................................................................375
Figure 257 MPLS Classification Page ........................................................................................................................376
Figure 258 MPLS Classification - Edit Page ...............................................................................................................377
Figure 259 MAC DA Classification Page .....................................................................................................................378
Figure 260 MAC DA Classification – Add Page ...........................................................................................................378
Figure 261 MAC DA Classification – Edit Page ...........................................................................................................379
Figure 262 Policer Profile Page .................................................................................................................................381
Figure 263 Policer Profile - Add Page .......................................................................................................................381
Figure 264 Logical Interfaces – Policers Page – Unicast Policer (Default) ................................................................383
Figure 265 Logical Interfaces – Policers Page – Multicast Policer ............................................................................384
Figure 266 Logical Interfaces – Policers Page – Broadcast Policer ...........................................................................385
Figure 267 Logical Interfaces – Policers Page – Ethertype Policer ...........................................................................385
Figure 268 802.1Q Marking Page .............................................................................................................................388
Figure 269 802.1Q Marking - Edit Page ....................................................................................................................388
Figure 270 802.1AD Marking Page ...........................................................................................................................389
Figure 271 802.1AD Marking - Edit Page ..................................................................................................................389
Figure 272 WRED Profile Page ..................................................................................................................................392
Figure 273 WRED Profile - Add Page ........................................................................................................................392
Figure 274 Logical Interfaces – WRED Page .............................................................................................................394
Figure 275: Logical Interfaces – WRED - Edit Page ....................................................................................................394
Figure 276 Queue Shaper Profile Page .....................................................................................................................396
Figure 277 Queue Shaper Profile – Add Page ...........................................................................................................396
Figure 278 Service Bundle Shaper Profile Page ........................................................................................................398
Figure 279 Service Bundle Shaper Profile – Add Page ..............................................................................................398
Figure 280 Logical Interfaces – Shaper – Egress Queue Shaper ...............................................................................400
Figure 281 Logical Interfaces – Egress Queue Shaper Configuration – Add Page ....................................................400
Figure 282 Logical Interfaces – Shaper – Egress Service Bundle Shaper ..................................................................402
Figure 283 Logical Interfaces – Egress Service Bundle Shaper Configuration – Add Page .......................................403
Figure 284 Scheduler Priority Profile Page ...............................................................................................................405
Figure 285 Scheduler Priority Profile – Add Page .....................................................................................................406
Figure 286 Scheduler WFQ Profile Page ...................................................................................................................408
Figure 287 Scheduler WFQ Profile – Add Page .........................................................................................................409
Figure 288 Logical Interfaces – Scheduler – Egress Port Scheduling Priority ...........................................................410
Figure 289 Logical Interfaces – Scheduler – Egress Port Scheduling WFQ ...............................................................410
Figure 290 Egress CoS PM Configuration Page ..........................................................................................................413
Figure 291 Egress CoS PM Configuration – Add Page................................................................................................414
Figure 292 Egress CoS PM Page .................................................................................................................................415
Figure 293: G.8032 General Attribute Page...............................................................................................................417

Phn 3963 013v000

Page xxiv
Contents

Figure 294: G.8032 ERPI Attribute Page ....................................................................................................................418

Figure 295: G.8032 ERPI Attribute Wizard – Page 1 ..................................................................................................418
Figure 296: G.8032 ERPI Attribute Wizard – Page 2 ..................................................................................................419
Figure 297: G.8032 ERPI Attribute Wizard – Page 3 ..................................................................................................419
Figure 298: G.8032 ERPI Attribute Wizard – Page 4 ..................................................................................................420
Figure 299: G.8032 ERPI Attribute Wizard – Submit ................................................................................................420
Figure 300: G.8032 ERPI Attribute – Edit Page ..........................................................................................................421
Figure 301: G.8032 ERPI Attribute – State Page ........................................................................................................402
Figure 302: G.8032 ERPI Attribute – Statistics Page ..................................................................................................403
Figure 303: Instance Per Service Mapping – Edit Page ..............................................................................................406
Figure 304: MSTP Bridge General Attributes Page ....................................................................................................407
Figure 305: MSTP Bridge Configuration ID Page........................................................................................................409
Figure 306: MSTP Bridge Spanning Tree Page ...........................................................................................................410
Figure 307; MSTP Bridge CIST Page ...........................................................................................................................413
Figure 308: MSTP Bridge MSTI Page ..........................................................................................................................414
Figure 309: MSTP Bridge MSTI – Edit Page ................................................................................................................414
Figure 310: MSTP Bridge VLAN Page .........................................................................................................................415
Figure 311: MSTP Port Spanning Tree Page (PTP 820C) ............................................................................................417
Figure 312: MSTP Port Spanning Tree – Edit Page ....................................................................................................417
Figure 313: MSTP Port CIST Page (PTP 820C) ............................................................................................................418
Figure 314: MSTP Port CIST – Edit Page.....................................................................................................................419
Figure 315: MSTP Port MSTI Page .............................................................................................................................421
Figure 316: MSTP Port MSTI – Edit Page ...................................................................................................................422
Figure 317: MSTP Port BDPU Counters Page .............................................................................................................424
Figure 318: Bandwidth Notification Page ..................................................................................................................425
Figure 319: Bandwidth Notification – Add Page ........................................................................................................426
Figure 320: Bandwidth Notification - Statistics Page (ETH-BN) .................................................................................428
Figure 321 Bandwidth Notification Page ..................................................................................................................430
Figure 322 ABN Configuration and Status – Add Page .............................................................................................431
Figure 323 Bandwidth Notification - Statistics Page.................................................................................................434
Figure 324 LLDP Remote System Management Page ...............................................................................................435
Figure 325 LLDP Configuration Parameters Page .....................................................................................................437
Figure 326 LLDP Port Configuration Page .................................................................................................................439
Figure 327 LLDP Port Configuration - Edit Page .......................................................................................................439
Figure 328 LLDP Destination Address Table Page ....................................................................................................442
Figure 329 LLDP Management TLV Configuration Page ...........................................................................................443
Figure 330 LLDP Remote System Management Page ...............................................................................................444
Figure 331 LLDP Remote System Table Page ............................................................................................................445
Figure 332 LLDP Local System Parameters Page ......................................................................................................446
Figure 333 LLDP Local System Port Page ..................................................................................................................448
Figure 334 LLDP Local System Management Page ...................................................................................................448
Figure 335 LLDP Local System Management – View Page .......................................................................................449

Phn 3963 013v000

Page xxv
Contents

Figure 336 LLDP Statistic Page ..................................................................................................................................450

Figure 337 LLDP Port TX Statistic Page .....................................................................................................................451
Figure 338 LLDP Port RX Statistic Page .....................................................................................................................452
Figure 339 SyncE Regenerator Page .........................................................................................................................455
Figure 340 Pipe Configurations - Add Page ..............................................................................................................456
Figure 341 Sync Source Page ....................................................................................................................................458
Figure 342 Sync Source – Add Page ..........................................................................................................................458
Figure 343 Outgoing Clock Page ...............................................................................................................................462
Figure 344 Outgoing Clock – Edit Page .....................................................................................................................462
Figure 345 1588-TC Page ..........................................................................................................................................463
Figure 346 1588 Transparent Clock Page .................................................................................................................464
Figure 347 1588-TC – Edit Page ................................................................................................................................464
Figure 348: Quick Configuration Security General Parameters Page ........................................................................467
Figure 349: Quick Configuration Security Protocols Page .........................................................................................468
Figure 350: Quick Configuration Security Access Control Page .................................................................................469
Figure 351: Quick Configuration Security RSA Key & Certificate Page ......................................................................470
Figure 352 Access Control General Configuration Page ...........................................................................................471
Figure 353 Access Control User Accounts - Edit Page ..............................................................................................472
Figure 354 Access Control Password Management Page .........................................................................................473
Figure 355 Protocols Control Page ...........................................................................................................................475
Figure 356 Access Control User Profiles Page ..........................................................................................................477
Figure 357 Access Control User Profiles - Add Page .................................................................................................478
Figure 358 Access Control User Accounts Page ........................................................................................................479
Figure 359 Access Control User Accounts - Add Page ..............................................................................................480
Figure 360 Remote Access Control Configuration Page ...........................................................................................483
Figure 361 Radius Configuration – Edit Page............................................................................................................484
Figure 362 Radius Users Page ...................................................................................................................................484
Figure 363 Radius Users Page – Expanded ...............................................................................................................485
Figure 364 Server Manager – Creating User Groups .................................................................................................487
Figure 365 Server Manager – Creating Users ............................................................................................................488
Figure 366: Server Manager – User Password Settings .............................................................................................489
Figure 367 Server Manager – Creating a RADIUS Client ............................................................................................490
Figure 368 Create Network Policy – Specify Name and Connection Type ................................................................492
Figure 369 Create Network Policy – Select Condition ...............................................................................................493
Figure 370 Create Network Policy – User Group added to Policy’s Conditions ........................................................494
Figure 371 Create Network Policy – Specifying Access Permission ...........................................................................495
Figure 372 Create Network Policy – Configuring Authentication Methods ..............................................................496
Figure 373 Create Network Policy – Insecure Authentication Method Query ..........................................................496
Figure 374 Create Network Policy – Configuring Constraints ...................................................................................497
Figure 375 Create Network Policy – Configuring Settings .........................................................................................498
Figure 376 Create Network Policy – Adding Vendor Specific Attributes ...................................................................499
Figure 377 Create Network Policy – Selecting to Add Attribute Information ...........................................................500

Phn 3963 013v000

Page xxvi
Contents

Figure 378 Create Network Policy – Specifying the Vendor ......................................................................................501

Figure 379 Create Network Policy – Configuring Vendor-Specific Attribute Information.........................................502
Figure 380 Create Network Policy – Example of Vendor-Specific Attribute Configuration ......................................503
Figure 381 Create Network Policy – Stopping/Starting NPS Services .......................................................................504
Figure 382 Security Certificate Request Page ...........................................................................................................510
Figure 383 FTP Parameters Page (Security Certificate Request) ..............................................................................511
Figure 384 Security Certification Download and Install Page ...................................................................................512
Figure 385 FTP Parameters Page (Security Certification Download & Install) .........................................................512
Figure 386: RSA Key Download & Install Page (HTTP Selected) ................................................................................515
Figure 387: RSA Key Download & Install Page (FTP Selected) ...................................................................................516
Figure 388: FTP Parameters Page ..............................................................................................................................516
Figure 389 Protocols Control Page ............................................................................................................................518
Figure 390 Security Log Upload Page .......................................................................................................................519
Figure 391 FTP Parameters Page (Security Log Upload) ...........................................................................................520
Figure 392 Configuration Log Upload Page ..............................................................................................................521
Figure 393 Configuration Log Upload Page ..............................................................................................................522
Figure 394 Current Alarms Page ...............................................................................................................................525
Figure 395 Current Alarms - View Page ....................................................................................................................525
Figure 396 Alarm Statistics Page ..............................................................................................................................527
Figure 397 Event Log ................................................................................................................................................528
Figure 398 Alarm Configuration Page .......................................................................................................................530
Figure 399 Alarm Configuration Page – Expanded ...................................................................................................531
Figure 400 Alarm Configuration - Edit Page .............................................................................................................533
Figure 401 Voltage Alarm Configuration Page...........................................................................................................535
Figure 402 Voltage Alarm Configuration – Edit Page ................................................................................................535
Figure 403 Voltage PM Report Page ..........................................................................................................................536
Figure 404: Unit Info Page – HTTP/HTTPS Upload .....................................................................................................537
Figure 405 Unit Info Page .........................................................................................................................................538
Figure 406: FTP Parameters Page ..............................................................................................................................539
Figure 407 Radio Loopbacks Page ............................................................................................................................541
Figure 408 Radio Loopbacks – Edit Page ..................................................................................................................542
Figure 409 Logical Interfaces – Loopback Page ........................................................................................................543
Figure 410 SOAM MD Page ......................................................................................................................................545
Figure 411 SOAM MD Page ......................................................................................................................................545
Figure 412 SOAM MA/MEG Page .............................................................................................................................546
Figure 413 SOAM MA/MEG – Add Page ...................................................................................................................547
Figure 414 MEP List Page..........................................................................................................................................550
Figure 415 Add MEP Page.........................................................................................................................................551
Figure 416 SOAM MEP Page .....................................................................................................................................551
Figure 417 Add SOAM MEP Wizard – Page 1............................................................................................................551
Figure 418 Add SOAM MEP Wizard – Page 2............................................................................................................552
Figure 419 Add SOAM MEP Wizard –Summary Page ...............................................................................................553

Phn 3963 013v000

Page xxvii
Contents

Figure 420 SOAM MEP - Edit Page............................................................................................................................555

Figure 421 SOAM MEP DB Table ..............................................................................................................................556
Figure 422 MEP Last Invalid CCMS Page ...................................................................................................................557
Figure 423 SOAM MEP Loopback Page.....................................................................................................................559
Figure 424 Restart HTTP Page ...................................................................................................................................562
Figure 425 ifIndex Calculator Page ............................................................................................................................563
Figure 426 MIB Reference Table Page .......................................................................................................................564
Figure 427 PTP 820C Interfaces ................................................................................................................................845
Figure 428 PTP 820C DC Port Connector ..................................................................................................................848
Figure 429: PTP 820C-HP Interfaces ..........................................................................................................................851
Figure 430: PTP 820C-HP DC Port Connector ............................................................................................................852
Figure 431 PTP 820S Interfaces ................................................................................................................................856
Figure 432 PTP 820S DC Connector ..........................................................................................................................858
Figure 433 PTP 820E Interfaces – ESE ........................................................................................................................862
Figure 434 PTP 820E Interfaces – ESP........................................................................................................................863
Figure 435: Two-Wire to PoE Port Power Adaptor ....................................................................................................865
Figure 436 RSL Pins ....................................................................................................................................................865
Figure 437: PoE Injector Connectors .........................................................................................................................868

Phn 3963 013v000

Page xxviii
Contents

List of Tables
Table 1 PTP 820 Web EMS Menu Hierarchy ...............................................................................................................26
Table 2 Cables for Direct CPU Connection ................................................................................................................106
Table 3 PTP 820 Web EMS Menu Hierarchy .............................................................................................................119
Table 4 Activation Key-Enabled-Features Table Parameters ....................................................................................121
Table 5 Time Services Parameters ............................................................................................................................126
Table 6 MRMC Symmetrical Scripts Page Parameters .............................................................................................137
Table 7 Available Radio Profiles for PTP 820C, PTP 820C-HP and PTP 820S.............................................................138
Table 8 Available Radio Profiles for PTP 820E ...........................................................................................................138
Table 9 System Configurations .................................................................................................................................157
Table 10 Multiband Cable for Use with CSFP Port.....................................................................................................227
Table 11 LACP Aggregation Status Parameters ........................................................................................................238
Table 12 LACP Port Status Parameters .....................................................................................................................240
Table 13 LACP Port Statistics ....................................................................................................................................242
Table 14 LACP Port Debug Statistics .........................................................................................................................243
Table 15 SNMP V3 Authentication Parameters ........................................................................................................295
Table 16 Trap Manager Parameters .........................................................................................................................297
Table 17 Versions Page Columns ..............................................................................................................................304
Table 18 Download & Install Status Parameters ......................................................................................................310
Table 19 Backup Files Page Columns ........................................................................................................................313
Table 20 Unit Parameters .........................................................................................................................................323
Table 21 SFP Inventory Parameters ...........................................................................................................................280
Table 22 SFP Digital Diagnostic Monitoring (DDM) Parameters ................................................................................281
Table 23 DDM PMs ....................................................................................................................................................282
Table 24 Radio Status Parameters............................................................................................................................288
Table 25 Remote Radio Parameters .........................................................................................................................290
Table 26: Radio Ethernet Interface Counters Fields ..................................................................................................299
Table 27 MRMC Status Parameters ..........................................................................................................................309
Table 28 MRMC PMs ................................................................................................................................................310
Table 29 Signal Level PMs.........................................................................................................................................314
Table 30 Signal Level Thresholds ..............................................................................................................................316
Table 31 Modem BER (Aggregate) PMs ....................................................................................................................317
Table 32 Modem MSE PMs.......................................................................................................................................318
Table 33 XPI PMs ......................................................................................................................................................321
Table 34 Capacity/Throughput PMs .........................................................................................................................324
Table 35 Utilization PMs ...........................................................................................................................................326
Table 36 Frame Error Rate PMs ................................................................................................................................327
Table 37 Ethernet Services Page Parameters ...........................................................................................................332
Table 38 General Service Point Attributes ...............................................................................................................337
Table 39 Attached Interface Types ...........................................................................................................................339
Table 40 Service Point Ingress Attributes .................................................................................................................340
Table 41 Service Point Egress Attributes ..................................................................................................................341

Phn 3963 013v000

Page xxix
Contents

Table 42 VLAN Classification Parameters .................................................................................................................347

Table 43 Physical Interface Status Parameters ........................................................................................................352
Table 44 Ethernet TX Port PMs.................................................................................................................................360
Table 45 Ethernet RX Port PMs ................................................................................................................................363
Table 46 Logical Interface Classification Parameters ...............................................................................................370
Table 47 Policer Profile Parameters .........................................................................................................................382
Table 48: ERPI Configuration Parameters..................................................................................................................400
Table 49: ERPI Status Parameters ..............................................................................................................................401
Table 50: ERPI State Parameters ...............................................................................................................................402
Table 51: ERPI Statistics .............................................................................................................................................404
Table 52: MSTP Bridge Configuration ID Parameters ................................................................................................409
Table 53: MSTP Bridge Spanning Tree Status Parameters ........................................................................................411
Table 54: MSTP Bridge Spanning Tree Configuration Parameters ............................................................................411
Table 55: MSTP Bridge CIST Status Parameters.........................................................................................................413
Table 56: MSTP Bridge MSTI Status Parameters .......................................................................................................415
Table 57: MSTP Port Spanning Tree Status Parameters ............................................................................................418
Table 58: MSTP Port CIST Status Parameters ............................................................................................................420
Table 59: MSTP Port MSTI Status Parameters ...........................................................................................................422
Table 60: MSTP BPDU Counters ................................................................................................................................424
Table 61 ABN Status Parameters ..............................................................................................................................432
Table 62 ABN Entity Statistics Parameters ...............................................................................................................434
Table 63 LLDP Remote System Management Parameters .......................................................................................436
Table 64 LLDP Read-Only Configuration Parameters ...............................................................................................437
Table 65 LLDP Configurable Configuration Parameters ...........................................................................................438
Table 66 LLDP Port Configuration Status Parameters ..............................................................................................441
Table 67 LLDP Management TLV Parameters...........................................................................................................443
Table 68 LLDP Remote System Management Parameters .......................................................................................444
Table 69 LLDP Remote System Table Parameters ....................................................................................................445
Table 70 LLDP Local System Parameters ..................................................................................................................446
Table 71 LLDP Local System Port Parameters ..........................................................................................................448
Table 72 LLDP Local System Management Parameters............................................................................................449
Table 73 LLDP Statistics ............................................................................................................................................450
Table 74 LLDP Port TX Statistics................................................................................................................................451
Table 75 LLDP Port RX Statistics ...............................................................................................................................452
Table 76 Sync Source Parameters ............................................................................................................................458
Table 77: RSA File Download & Install Status Parameters ........................................................................................517
Table 78 Alarm Information .....................................................................................................................................526
Table 79 Event Log Information ...............................................................................................................................528
Table 80 Alarm Configuration Page Parameters ......................................................................................................530
Table 81 Voltage PMs ................................................................................................................................................536
Table 82 SOAM MA/MEG Configuration Parameters ...............................................................................................547
Table 83 SOAM MA/MEG Status Parameters ...........................................................................................................548

Phn 3963 013v000

Page xxx
Contents

Table 84 SOAM MEP Parameters .............................................................................................................................553

Table 85 SOAM MEP DB Table Parameters ..............................................................................................................556
Table 86 MIMO Protection Cables. ...........................................................................................................................570
Table 87 IP Address (IPv4) CLI Parameters ...............................................................................................................573
Table 88 IP Address (IPv6) CLI Parameters ...............................................................................................................574
Table 89 Local Time Configuration CLI Parameters ..................................................................................................578
Table 90: Daylight Savings Time CLI Parameters .......................................................................................................579
Table 91 Interface Configuration CLI Parameters.....................................................................................................581
Table 92 Entering Radio View CLI Parameters..........................................................................................................582
Table 93 Radio Mute/Unmute CLI Parameters ........................................................................................................583
Table 94 Radio Transmit (TX) Level CLI Parameters .................................................................................................583
Table 95 Radio Transmit (TX) Frequency CLI Parameters.........................................................................................584
Table 96 MRMC Script CLI Parameters .....................................................................................................................585
Table 97 MRMC Script Assignation to Radio Carrier CLI Parameters .......................................................................587
Table 98 System Configurations (CLI) .......................................................................................................................551
Table 99 LAG Group CLI Parameters .........................................................................................................................561
Table 100 LACP Aggregation Status Parameters (CLI) ..............................................................................................565
Table 101 LACP Port Status Parameters (CLI) ............................................................................................................567
Table 102 LACP Port Statistics (CLI) ..........................................................................................................................569
Table 103: MMI and XPI Levels CLI Parameters.........................................................................................................585
Table 104 Remote Unit IP Address (IPv4) CLI Parameters........................................................................................598
Table 105 Remote Unit IP Address (IPv6) CLI Parameters........................................................................................599
Table 106 Basic SNMP CLI Parameters .....................................................................................................................600
Table 107 SNMPv3 CLI Parameters ..........................................................................................................................601
Table 108 Trap Managers CLI Parameters ................................................................................................................603
Table 109 Software Download CLI Parameters ........................................................................................................608
Table 110 Configuration Management CLI Parameters ...........................................................................................612
Table 111 Configuration Backup and Restore CLI Parameters .................................................................................613
Table 112 Configuration Import and Restore CLI Parameters..................................................................................614
Table 113 Unit Parameters CLI Parameters..............................................................................................................618
Table 114 NTP CLI Parameters .................................................................................................................................620
Table 115: SFP Inventory Parameters (CLI)................................................................................................................622
Table 116: SFP Digital Diagnostic Monitoring (DDM) Parameters (CLI) ....................................................................623
Table 117 Remote Radio Mute/Unmute CLI Parameters ..........................................................................................627
Table 118 Remote Radio TX Level CLI Parameters ...................................................................................................628
Table 119 Remote Radio ATPC CLI Parameters ........................................................................................................628
Table 120 Radio ATPC CLI Parameters......................................................................................................................631
Table 121 Header De-Duplication CLI Parameters ...................................................................................................634
Table 122 Aggregate PMs (CLI) .................................................................................................................................643
Table 123 Excessive BER CLI Parameters ..................................................................................................................645
Table 124 RSL Thresholds CLI Parameters ................................................................................................................645
Table 125 TSL Thresholds CLI Parameters ................................................................................................................647

Phn 3963 013v000

Page xxxi
Contents

Table 126 RSL and TSL PMs (CLI) ...............................................................................................................................648

Table 127 Signal Level Threshold CLI Parameters ....................................................................................................649
Table 128 MSE CLI Parameters .................................................................................................................................649
Table 129 MSE PMs (CLI) ..........................................................................................................................................651
Table 130 XPI Threshold CLI Parameters ..................................................................................................................651
Table 131 XPI PMs (CLI) ............................................................................................................................................653
Table 132 ACM PMs (CLI) ..........................................................................................................................................655
Table 133 Adding Ethernet Service CLI Parameters .................................................................................................659
Table 134 Entering Ethernet Service View CLI Parameters ......................................................................................660
Table 135 Displaying Ethernet Service Details CLI Parameters ................................................................................661
Table 136 Ethernet Service Operational State CLI Parameters ................................................................................662
Table 137 Ethernet Service CoS Mode CLI Parameters ............................................................................................662
Table 138 Ethernet Service EVC CLI Parameters ......................................................................................................663
Table 139 Deleting Ethernet Service CLI Parameters ...............................................................................................664
Table 140 Service Points per Service Type ...............................................................................................................665
Table 141 Service Point Types per Interface ............................................................................................................665
Table 142 Legal Service Point – Interface Type Combinations per Interface – SAP and SNP ...................................667
Table 143 Legal Service Point – Interface Type Combinations per Interface – Pipe and MNG ................................667
Table 144 Add Service Point CLI Parameters ............................................................................................................670
Table 145 Enable/Disable Broadcast Frames CLI Parameters ..................................................................................673
Table 146 Service Point CoS Preservation CLI Parameters .......................................................................................674
Table 147 Service Point Enable/Disable Flooding CLI Parameters ...........................................................................676
Table 148 C-VLAN CoS Preservation Mode CLI Parameters .....................................................................................677
Table 149 C-VLAN Preservation CLI Parameters.......................................................................................................678
Table 150 S-VLAN CoS Preservation CLI Parameters ................................................................................................680
Table 151 Service Bundle CLI Parameters ................................................................................................................681
Table 152 VLAN Bundle to Service Point CLI Parameters .........................................................................................682
Table 153 Display Service Point Attributes CLI Parameters .....................................................................................682
Table 154 Delete Service Point Attributes CLI Parameters ......................................................................................684
Table 155 MAC Address Forwarding Table Maximum Size CLI Parameters .............................................................684
Table 156 MAC Address Forwarding Table Aging Time CLI Parameters...................................................................685
Table 157 Adding Static Address to MAC Address Forwarding Table CLI Parameters .............................................686
Table 158 Enabling MAC Address Learning CLI Parameters .....................................................................................687
Table 159 Configure S-VLAN Ethertype CLI Parameters ...........................................................................................688
Table 160 Configure MRU CLI Parameters ...............................................................................................................689
Table 161 Entering Interface View CLI Parameters ..................................................................................................690
Table 162 Interface Media Type CLI Parameters......................................................................................................693
Table 163 Interface Speed and Duplex State CLI Parameters ..................................................................................693
Table 164 Interface Auto Negotiation State CLI Parameters....................................................................................694
Table 165 Interface IFG CLI Parameters ...................................................................................................................694
Table 166 Interface Preamble CLI Parameters .........................................................................................................695
Table 167 Interface Description CLI Parameters ......................................................................................................695

Phn 3963 013v000

Page xxxii
Contents

Table 168 Interface Statistics (RMON) CLI Parameters ............................................................................................696

Table 169: Automatic State Propagation to an Ethernet Port CLI Parameters .........................................................699
Table 170 RMON Statistics CLI Parameters ..............................................................................................................703
Table 171 Port PM Thresholds CLI Parameters ........................................................................................................704
Table 172 Ethernet Port PMs ...................................................................................................................................706
Table 173 VLAN Classification and Override CLI Parameters ...................................................................................742
Table 174 802.1p Trust Mode CLI Parameters .........................................................................................................744
Table 175 C-VLAN 802.1 UP and CFI Bit Classification Table Default Values............................................................744
Table 176 C-VLAN 802.1 UP and CFI Bit Classification Table CLI Parameters ...........................................................745
Table 177 S-VLAN 802.1 UP and DEI Bit Classification Table Default Values ...........................................................745
Table 178 S-VLAN 802.1 UP and DEI Bit Classification Table CLI Parameters...........................................................746
Table 179 Trust Mode for DSCP CLI Parameters ......................................................................................................748
Table 180 DSCP Classification Table Default Values .................................................................................................748
Table 181 Modify DSCP Classification Table CLI Parameters....................................................................................750
Table 182 Trust Mode for MPLS CLI Parameters ......................................................................................................751
Table 183 MPLS EXP Bit Classification Table Default Values ....................................................................................751
Table 184 MPLS EXP Bit Classification Table Modification CLI Parameters ..............................................................751
Table 185 Default CoS CLI Parameters .....................................................................................................................753
Table 186 Rate Meter Profile CLI Parameters ..........................................................................................................754
Table 187 Assigning Rate Meter for Unicast Traffic CLI Parameters ........................................................................758
Table 188 Assigning Rate Meter for Multicast Traffic CLI Parameters .....................................................................759
Table 189 Assigning Rate Meter for Broadcast Traffic CLI Parameters ....................................................................760
Table 190 Assigning Rate Meter per Ethertype CLI Parameters...............................................................................761
Table 191: Assigning Rate Meter for Service Point and Service Point/CoS CLI Parameters ........................................762
Table 192 Assigning Line Compensation Value for Rate Meter CLI Parameters ......................................................763
Table 193 Displaying Rate Meter Statistics CLI Parameters .....................................................................................764
Table 194 Marking Mode on Service Point CLI Parameters .....................................................................................766
Table 195 Marking Table for C-VLAN UP Bits ...........................................................................................................767
Table 196 802.1q CoS and Color to UP and CFI Bit Mapping Table CLI Parameters.................................................768
Table 197 802.1ad UP Marking Table (S-VLAN)........................................................................................................769
Table 198 802.1ad UP Marking Table (S-VLAN) CLI Parameters ..............................................................................770
Table 199 WRED Profile CLI Parameters...................................................................................................................772
Table 200 Assigning WRED Profile to Queue CLI Parameters ..................................................................................773
Table 201 Queue Shaper Profiles CLI Parameters ....................................................................................................775
Table 202 Attaching Shaper Profile to Queue CLI Parameters .................................................................................776
Table 203 Service Bundle Shaper Profiles CLI Parameters .......................................................................................777
Table 204 Attaching Shaper Profile to Service Bundle CLI Parameters ....................................................................778
Table 205 Egress Line Compensation for Shaping CLI Parameters ...........................................................................779
Table 206 Interface Priority Profile Example ............................................................................................................780
Table 207 Interface Priority Profile CLI Parameters .................................................................................................782
Table 208 Interface Priority Sample Profile Parameters ..........................................................................................783
Table 209 Attaching Priority Profile to Interface CLI Parameters.............................................................................784

Phn 3963 013v000

Page xxxiii
Contents

Table 210 WFQ Profile Example ...............................................................................................................................785

Table 211 WFQ Profile CLI Parameters.....................................................................................................................785
Table 212 WFQ Sample Profile Parameters .............................................................................................................786
Table 213 Attaching WFQ Profile to Interface CLI Parameters ................................................................................787
Table 214 Egress Queue Level PMs CLI Parameters .................................................................................................788
Table 215 Egress Service Bundle Level PMs CLI Parameters ....................................................................................784
Table 216: G.8032 Destination MAC Address CLI Parameters ..................................................................................782
Table 217: G.8032 ERPI Configuration CLI Parameters .............................................................................................783
Table 218: G.8032 RPL Owner CLI Parameters ..........................................................................................................784
Table 219: G.8032 Timer Configuration CLI Parameters ...........................................................................................785
Table 220: G.8032 Switching and Reversion CLI Parameters ....................................................................................787
Table 221: G.8032 ERPI Display Command Input Parameters ...................................................................................790
Table 222: G.8032 ERPI Display Command Output Parameters ................................................................................791
Table 223: G.8032 Service Point Display Command Output Parameters ..................................................................792
Table 224: Defining Number of MSTIs CLI Parameters..............................................................................................795
Table 225: BPDU Destination MAC Address CLI Parameters .....................................................................................795
Table 226: MSTP Signal Degrade Failure CLI Parameters ..........................................................................................796
Table 227: MSTP Configuration ID CLI Parameters....................................................................................................797
Table 228: MSTP Service to MSTI Mapping CLI Parameters ......................................................................................798
Table 229: MSTP Bridge Level Spanning Tree CLI Parameters ..................................................................................799
Table 230: Bridge Level MSTI CLI Parameters ...........................................................................................................800
Table 231: CIST Port CLI Parameters .........................................................................................................................802
Table 232: MSTI Port CLI Parameters ........................................................................................................................804
Table 233: Port BPDU Counters CLI Parameters........................................................................................................806
Table 234 ABN Entity CLI Parameters .......................................................................................................................809
Table 235 General LLDP CLI Parameters...................................................................................................................752
Table 236 LLDP Port CLI Parameters ........................................................................................................................753
Table 237 LLDP Remote Unit CLI Parameters ...........................................................................................................757
Table 238 LLDP Remote Management Data Per Port CLI Parameters .....................................................................758
Table 239 SyncE Regenerator CLI Parameters ..........................................................................................................763
Table 240 Sync Source Ethernet CLI Parameters ......................................................................................................768
Table 241 Sync Source Radio CLI Parameters ...........................................................................................................769
Table 242 Outgoing Clock CLI Parameters................................................................................................................771
Table 243 1588 Transparent Clock CLI Parameters ..................................................................................................778
Table 244 Inactivity Timeout Period CLI Parameters ...............................................................................................781
Table 245 Blocking Upon Login Failure CLI Parameters ...........................................................................................782
Table 246 Blocking Unused Accounts CLI Parameters..............................................................................................783
Table 247 Password Aging CLI Parameters...............................................................................................................784
Table 248 Password Strength Enforcement CLI Parameters ....................................................................................785
Table 249 Force Password Change on First Time Login CLI Parameters ..................................................................785
Table 250 User Profile CLI Parameters .....................................................................................................................788
Table 251 User Profile Access Protocols CLI Parameters .........................................................................................788

Phn 3963 013v000

Page xxxiv
Contents

Table 252 User Accounts CLI Parameters .................................................................................................................790

Table 253 Activate RADIUS CLI Parameters..............................................................................................................791
Table 254 Configure RADIUS Server CLI Parameters ................................................................................................791
Table 255 CSR Generation and Upload CLI Parameters ...........................................................................................795
Table 256 Certificate Download and Install CLI Parameters ....................................................................................797
Table 257: RSA Key Download and Install CLI Parameters ........................................................................................801
Table 258 Security Log CLI Parameters ....................................................................................................................803
Table 259 Configuration Log CLI Parameters ...........................................................................................................805
Table 260 Editing Alarm Text and Severity CLI Parameters......................................................................................813
Table 261 Restoring Alarms to Default CLI Parameters ...........................................................................................814
Table 262 Uploading Unit Info CLI Parameters ........................................................................................................820
Table 263 Radio Loopback CLI Parameters...............................................................................................................823
Table 264 Ethernet Loopback CLI Parameters..........................................................................................................824
Table 265 Maintenance Domain CLI Parameters .....................................................................................................827
Table 266 SOAM MEG CLI Configuration Parameters ..............................................................................................828
Table 267 MEP CLI Configuration Parameters ..........................................................................................................832
Table 268 MEP and Remote MEP Status Parameters (CLI) ......................................................................................834
Table 269 Loopback CLI Parameters.........................................................................................................................839
Table 270 CW Mode CLI Parameters ........................................................................................................................841
Table 271: PTP 820C Eth1/PoE Interface- RJ-45/SFP Pinouts....................................................................................845
Table 272 PTP 820C Eth2 Interface - RJ-45/SFP Pinouts...........................................................................................846
Table 273 PTP 820C MIMO Port - RJ-45/SFP pinouts ...............................................................................................846
Table 274 PTP 820C MGT/PROT Interface - RJ-45 Pinouts .......................................................................................847
Table 275:PTP 820C-HP Data Port 1 – Pinouts ..........................................................................................................851
276: PTP 820C-HP Management Interface - RJ-45 Pinouts .......................................................................................852
Table 277 PTP 820S Eth1/PoE Interface- RJ-45/SFP Pinouts .....................................................................................856
Table 278 PTP 820S Eth2 Interface - RJ-45/SFP Pinouts ............................................................................................857
Table 279 PTP 820S Eth3/EXP Interface - RJ-45/SFP Pinouts ...................................................................................857
Table 280 PTP 820S MGT/PROT Interface - RJ-45 Pinouts .......................................................................................858
Table 281 PTP 820E Port Distribution Per Hardware Model .....................................................................................861
Table 282 PTP 820E Eth1/PoE Interface- RJ-45 .........................................................................................................863
Table 283 PTP 820E MGT Interface - RJ-45/ Pinouts .................................................................................................864
Table 284 PoE Injector PoE Port - RJ-45 Pinouts ......................................................................................................868
Table 285 PoE Injector RJ-45 Data Port Supporting 10/100/1000Base-T ................................................................869

Phn 3963 013v000

Page xxxv
About This User Guide
This document explains how to configure and operate a PTP 820C/820S system. This document applies to software
version 11.1
The PTP 820 system is a modular system with a wide variety of configuration options. Not all configurations are
described in this manual.

This guide covers the following sections of PTP 820C/PTP 820S:

• Introduction
• Web EMS configuration
• CLI Configuration
• Maintenance
• Appendices

This guide contains the following Chapters:

• Chapter 1: Introduction
• Chapter 2: Getting Started
• Chapter 3: Configuration Guide
• Chapter 4: Unit Management
• Chapter 5: Radio Configuration
• Chapter 6: Ethernet Services and Interfaces
• Chapter 7: Quality of Service (QoS)
• Chapter 8: Ethernet Protocols
• Chapter 9: Synchronization
• Chapter 10: Access Management and Security
• Chapter 11: Alarm Management and Troubleshooting
• Chapter 12: Web EMS Utilities
• Chapter 13: Getting Started (CLI)
• Chapter 14: Configuration Guide (CLI)
• Chapter 15: Unit Management (CLI)
• Chapter 16: Radio Configuration (CLI)
• Chapter 17: Ethernet Services and Interfaces (CLI)
• Chapter 18: Quality of Service (QoS) (CLI)
• Chapter 19: Ethernet Protocols (CLI)
• Chapter 20: Synchronization (CLI)
• Chapter 21: Access Management and Security (CLI)

Phn 3963 013v000

Page 1
About This User Guide Problems and warranty

• Chapter 22: Alarm Management and Troubleshooting (CLI)

• Chapter 23: Maintenance
• Chapter 24: Alarms List

Contacting Cambium Networks

Support website: https://support.cambiumnetworks.com

Main website: http://www.cambiumnetworks.com

Sales enquiries: solutions@cambiumnetworks.com
Support enquiries: https://support.cambiumnetworks.com

Repair enquiries https://support.cambiumnetworks.com

Telephone number list: http://www.cambiumnetworks.com/support/contact-support
Address: Cambium Networks Limited,
Unit B2, Linhay Business Park, Eastern Road
Ashburton, United Kingdom, TQ13 7UP

Phn 3963 013v000

Page 2
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,
installation and maintenance of the Cambium Networks PTP equipment and ancillary devices. It is recommended
that all personnel engaged in such activities be properly trained.
Cambium Networks disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction
in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the
customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document.

Cross references
References to external publications are shown in italics. Other cross references, emphasized in blue text in
electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but
are individually named at the top of each page, and are listed in the table of contents.

Feedback
We appreciate feedback from the users of our documents. This includes feedback on the structure, content,
accuracy, or completeness of our documents. Send feedback to support@cambiumnetworks.com.

Phn 3963 013v000

Page 3
About This User Guide Problems and warranty

Problems and warranty

Reporting problems
If any problems are encountered when installing or operating this equipment, follow this procedure to investigate
and report:
1 Search this document and the software release notes of supported releases.
2 Visit the support website.
3 Ask for assistance from the Cambium Networks product supplier.
4 Gather information from affected units, such as any available diagnostic downloads.
5 Escalate the problem by emailing or telephoning support.

Repair and service

If unit failure is suspected, obtain details of the Return Material Authorization (RMA) process from the support
website.

Hardware warranty
Cambium Networks’s standard hardware warranty is for one (1) year from date of shipment from Cambium
Networks or a Cambium distributor. 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. Cambium shall within this time, at its own option, either repair or replace the defective product within
thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original
warranty period but not less than thirty (30) days.
To register PTP products or activate warranties, visit the support website. For warranty assistance, contact the
reseller or distributor.

Caution
Using non-Cambium parts for repair could damage the equipment or void warranty. Contact
Cambium for service and repair instructions.
Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use
precautions to prevent damage.

Phn 3963 013v000

Page 4
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. Cambium recommends setting and using these parameters
following industry recognized security practices. Security aspects to be considered are protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate,
information about the nature of the communications, and information about the parties involved.
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.

Phn 3963 013v000

Page 5
About This User Guide Warnings, cautions, and notes

Warnings, cautions, 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
Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader
to possible hazards that could cause loss of life or physical injury. A warning has the following format:

Warning
Warning text and consequence for not following the instructions in the warning.

Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems, software, or
individual items of equipment within a system. However, this damage presents no danger to personnel. A caution
has the following format:

Caution
Caution text and consequence for not following the instructions in the caution.

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 note has the following format:

Note
Note text.

Phn 3963 013v000

Page 6
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.

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.

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. For disposal instructions, refer to
http://www.cambiumnetworks.com/support

Disposal of surplus packaging

Do not dispose of surplus packaging in landfill sites. In the EU, 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, dispose of Cambium equipment and all surplus packaging in accordance with national and
regional regulations.

Phn 3963 013v000

Page 7
Chapter 1: Introduction
This section includes:
• System Overview
• Configuration tips
• The Web-Based Element Management System
• Reference Guide to Web EMS Menu Structure
This user manual provides instructions for configuring and operating the following systems:
• Configuration Tips
• PTP 820C
• PTP 820C-HP
• PTP 820S
• PTP 820E
Each of these systems products except PTP 820C-HP can be used with a PoE (PoE Injector Overview).
Wherever applicable, the manual notes the specific distinctions between these products. The manual also notes
when specific features are only applicable to certain products and not others.

Phn 3963 013v000

Page 8
Chapter 1: Introduction System Overview

System Overview

Configuration Tips
This section describes common issues and how to avoid them.
Ethernet Port configuration
• The Ethernet ports of a PTP 820C and PTP 820S are not enabled by default in a new unit. You must manually
enable the Ethernet port or ports in order for the unit to process Ethernet traffic. See Enabling the Interfaces
(Interface Manager)
• For RJ-45 ports, it is recommended to enable Auto-Negotiation for both the local port and its peer in order to
obtain optimal performance.
• For SFP ports, it is recommended to disable Auto-Negotiation.
• For instructions, see Configuring Ethernet Interfaces.
SyncE Interface Configuration
• When configuring a Sync source or outgoing clock on an Ethernet interface, the Media Type of the interface
must be RJ-45 or SFP, not Auto-Type. See Synchronization.
In-Band Management
It is strongly recommended not to configure ASP on an Ethernet interface that carries in-band management traffic.
If you do need to use ASP on this interface, it is recommended to use it in ASP Management Safe (CSF) mode to
avoid loss of management in the event that ASP is triggered. See Configuring Automatic State Propagation and Link
Loss Forwarding.
When inband management is being transmitted via a LAG configuration, it is recommended to enable LACP to
overcome uni-directional failures. See Configuring a LAG Group.
If you are using 1588 Transparent Clock, make sure the Transparent Clock settings are symmetrical; that is, make
sure Transparent Clock is either enabled or disabled on both sides of the link. To avoid loss of management, make
sure to configure Transparent Clock on the remote side of the link first, then on the local side. See Configuring
1588 Transparent Clock.
To avoid loss of management when configuring Multi-Carrier ABC, make sure to add or remove members on the
remote side of the link first, then on the local side. See Configuring Multi-Carrier ABC
• In order to use in-band management with an external switch, it must be supported on the external switch.
• When configuring in-band management, be sure to tag the management traffic to avoid overflow of the CPU.
• It is strongly recommended to assign the management service (1025) a CoS of 7 to ensure that management
packets receive high priority and are not discarded in instances of network congestion. See Configuring
Ethernet Service(s).
• For instructions on configuring in-band management on the PTP 820, see Configuring in-Band Management.
Link Aggregation
• If you are configuring LAG with an external switch, the switch must support LAG. For instructions on
configuring LAG, see Configuring Link Aggregation (LAG) and LACP.

Phn 3963 013v000

Page 9
Chapter 1: Introduction System Overview

• When using IEEE 1588 PTP synchronization across a LAG link, follow the recommendations set forth in ITU-T
standard G.8275.1, Annex 6 in order to prevent PTP packets from following different paths between the
devices, which can lead to asymmetric delay. For instructions on configuring LAG, see Configuring Link
Aggregation (LAG) and LACP.
Software Upgrade
• When upgrading software via HTTP, make sure the software package is not unzipped. For instructions, see
Upgrading the Software.
Configuration Management and Backup Restoration
Configuration files can only be copied to the same PTP 820 hardware type with the same part number as the unit
from which they were originally saved. For example, a PTP 820C configuration file can only be restored to a PTP
820C with the same part number as the unit from which it was saved

4x4 MIMO and 2+2 Space Diversity

For PTP 820C 2E2SX hardware models, if you try to apply a 4x4 MIMO or 2+2 Space Diversity configuration while
P4 is assigned one or more service points, ASP or LLF instances, or a LAG group or Sync source is configured on P4,
the configuration will fail and an error message will be generated. Also, the Admin status of the port must be set to
Down before applying the 4x4 MIMO or 2+2 Space Diversity configuration. See Enabling the Interfaces (Interface
Manager).

PTP 820C - Overview

PTP 820C represents a new generation of radio technology, capable of high bit rates and longer reach, and suitable
for more diverse deployment scenarios. PTP 820C is a dual-core, compact, all-outdoor backhaul Ethernet product
that combines radio, baseband, and Carrier Ethernet functionality in a single, durable box for outdoor installations.
PTP 820C offers the convenience of an easy installation procedure, and full compatibility with RFU-C antennas. It is
designed for use in network configurations which require high capacity solutions. PTP 820C covers the entire
licensed frequency spectrum (6-38 GHz) and offers a wide capacity range, including Header De-Duplication.
PTP 820C is available in several hardware models:
• PTP 820C ESS – Includes one RJ-45 port and two SFP ports for Ethernet traffic.
• PTP 820C ESX – Includes one RJ-45 port and one SFP port for Ethernet traffic, and an SFP+ port for use as
an Extension port with 4x4 MIMO and 2+2 Space Diversity configurations.

PTP 820C-HP Overview

PTP 820C-HP is a high-power version of PTP 820C, operating in the 4-11 GHz bands and providing TX power of up
to 35 dBm. Together, PTP 820C and PTP 820C-HP represent a new generation of radio technology, capable of high
bit rates and longer reach, and suitable for diverse deployment scenarios.
PTP 820C-HP provides the same basic feature set as PTP 820C, including unique MultiCore features such as 4x4
MIMO, ASD, and AFR.

Phn 3963 013v000

Page 10
Chapter 1: Introduction System Overview

In addition, PTP 820C-HP uses field-replaceable diplexer units. An PTP 820C-HP can be ordered in two parts: A
generic radio unit and a diplexer unit. The generic radio unit covers an entire frequency band. It is the diplexer
unit, which is passive, that determines the sub-band coverage for the entire integrated PTP 820C-HP unit. This
provides operators with major benefits in terms of both maintenance and deployment time.
For maintenance, the operator can reduce the number of spare radio units in its inventory because a single generic
radio unit can be used for any sub-band. This means that for a site covering four channel ranges within a single
frequency band, a single spare radio unit can be kept on hand, because that unit can be used as a spare for any of
the PTP 820C-HP nodes in the site. The diplexer units, because they are passive, are much less likely to require
replacement, so the maintenance of spare parts for the diplexer units is much less of a concern for the operator.
The use of separate generic radio units and diplexer units also enables operators to achieve a quicker system
deployment time. In the planning stage, when the frequency bands have been determined but the exact sub-band
layout is still under consideration, operators can already order all the radio units required for the frequency bands
that have been determined, and can begin ordering diplexer units for the approximate sub-bands that are
anticipated, while still determining the exact network parameters. This enables faster delivery and deployment of
the network.

PTP 820S
PTP 820S is an all-outdoor solution for backhaul sites. It provides high-performance, internetworking operating
system, and supports all common features of the PTP 820 platform in a compact, environmentally friendly
architecture.
PTP 820S supports cutting edge capacity-boosting techniques, such as QPSK to 2048 QAM and Header De-
Duplication, to offer a high capacity solution for every network topology and every site configuration. Its green,
compact, all-outdoor configuration makes PTP 820S ideal for any location.
PTP 820S includes one RJ-45 port and two SFP ports for Ethernet traffic.

PTP 820E Overview

PTP 820E is a compact and versatile high capacity backhaul Ethernet system which operates in the E-band (70-80
GHz). Its light weight and small footprint make it versatile for many different applications. Thanks to its small
footprint, low power consumption, and simple installation, PTP 820E can be installed in many different types of
remote outdoor locations.
PTP 820E R2 offers ACM, with a modulation BPSK (2 QAM) through 1024 QAM. PTP 820E supports a diverse set of
features that is optimally suited for macro–to–macro site connectivity. It is equally well suited to be used as a high
capacity aggregation link connecting an array of small cells or BTS sites to a macro site.
All references to PTP 820E in this document refer to PTP 820E hardware release 2, high-power (R2H). There are
several hardware options for PTP 820E R2H, with variations in interface layout and capacity. For a full description
of these options.
For purposes of this document, when it is necessary to distinguish between different PTP 820E R2H hardware
models, the following terms are used:
• PTP 820E R2H ESP – Includes all PTP 820E R2 models that support a 10G interface and include ESP in their
marketing models.
• PTP 820E R2H – All other PTP 820E R2H models.

Phn 3963 013v000

Page 11
Chapter 1: Introduction System Overview

Note
For instructions on using PTP 820E hardware release 1 (R1), refer to the PTP 820C, PTP 820S,
and PTP 820E User Guide Rev E, for System Release 8.2, or earlier versions.

PoE Injector Overview

The PoE injector box is designed to offer a single cable solution for connecting both data and the DC power supply
to the PTP 820C or PTP 820S unit. To do so, the PoE injector combines 48VDC input and GbE signals via a standard
CAT5E cable using a proprietary design.
The PoE injector can be ordered with a DC feed protection and with +24VDC support, as well as EMC surge
protection for both indoor and outdoor installation options. It can be mounted on poles, walls, or inside racks.

PTP 820 Assured Platform

Cambium’s PTP 820 Assured platform enhances network reliability and security, ensuring that mission-critical
networks maintain availability, and protecting the confidentiality and integrity of their users’ data.
The PTP 820 Assured platform is compliant with FIPS 140-2, including:
• Compliance with FIPS 140-2 specifications for cryptography module.
• FIPS 140-2 Level 2 physical security.
• AES-256 encryption (FIPS 197) over radio links.
The PTP 820 Assured platform also provides:
• Secured communication and protocols for management interface.
• Centralized user authentication management via RADIUS.
• Advanced identity management and password policy enforcement.
• Security events log.
• Secure product architecture and development.
The following products are included in the PTP 820 Assured platform:
• PTP 820C Assured
• PTP 820C-HP Assured

Note
System release 11.3 cannot be used in PTP 820 Assured platforms. For PTP 820 Assured, use system
release 10.9.6 and 8.3.

Phn 3963 013v000

Page 12
Chapter 1: Introduction System Overview

The Web-Based Element Management System

This section includes:
• Introduction to the Web EMS
• Web EMS Page Layout
• Unit Summary Page
• Radio Summary Page
• Security Summary Page

Introduction to the Web EMS

The 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,
including:
• Configuration Management – Enables you to view and define configuration data.
• Fault Monitoring – Enables you to view active alarms.
• Performance Monitoring – Enables you to view and clear performance monitoring values and counters.
• Diagnostics and Maintenance – Enables you to define and perform loop back tests and software updates.
• Security Configuration – Enables you to configure security features.
• User Management – Enables you to define users and user groups.
The Web EMS opens to a page that summarizes the key unit parameters. The next page, when scrolling down the
Web EMS main menu, summarizes the key radio parameters. Next is a page that summarizes the key security-
related parameters of the unit. See Unit Summary Page and Radio Summary Page.
A Web-Based EMS connection to the unit can be opened using a Web browser (Internet Explorer, Mozilla Firefox,
or Google Chrome). The Web-Based EMS uses a graphical interface.

Note
For optimal Web EMS performance, it is recommended to ensure that the network speed is at least
100 Kbps for most operations, and at least 5 Mbps for software download operations.

The Web-Based EMS shows the actual unit configuration and provides easy access to any interface. A wide range
of configuration, testing, and system monitoring tasks can be performed through the Web EMS.

Note
The alarms and system configuration details shown in this manual do not necessarily represent
actual parameters and values on a fully operating PTP 820 system. Some of the pages and tasks
described in this Manual may not be available to all users, based on the actual system configuration,
activation key, and other details.

Web EMS Page Layout

Each Web EMS page includes the following sections:
• The left section of the page displays the Web EMS menu tree:

Phn 3963 013v000

Page 13
Chapter 1: Introduction System Overview

o Click to display the sub-options under a menu item.

o Click to hide the sub-options under a menu item.
• The main section of the page provides the page's basic functionality.

Figure 1 Main Web EMS Page

Phn 3963 013v000

Page 14
Chapter 1: Introduction System Overview

Front Panel Representation

Optionally, you can display a representation of the PTP 820 front panel by clicking either the arrow in the center or
the arrow at the right of the bottom toolbar.

Figure 2 Displaying a Representation of the Front Panel

Figure 3: Main Web EMS Page with Representation of Front Panel – PTP 820C and PTP 820S

Figure 4: Main Web EMS Page with Representation of Front Panel – PTP 820C-HP

Phn 3963 013v000

Page 15
Chapter 1: Introduction System Overview

Figure 5 Main Web EMS Page with Representation of Front Panel – PTP -820E

Phn 3963 013v000

Page 16
Chapter 1: Introduction System Overview

Active, Standby and Merged (All) Tabs

When HSB radio protection is enabled, two tabs appear on the top of the main section. These tabs are
labeled Active and Standby and enable you to configure the Active and Standby units separately if necessary. The
title above the main section indicates whether you are working with the Active or Standby TCC. For details on
configuring HSB radio protection, see Configuring Unit Protection with HSB Radio Protection (External Protection).

Figure 6 Main Web EMS Page with Active and Standby Tabs

Certain Web EMS pages include an additional, merged tab labelled All. The All tab includes rows for both the Active
and the Standby unit, so that you can work with both units from a single page. In merged pages, an additional
column labelled Device Role appears to indicate whether the row is from the Active or the Standby unit.
The All tab appears in the following Web EMS pages
• Interface Manager
• Radio Parameters
• Current Alarms
• Event Log

Figure 7: Merged (All) Tab – Interface Manager Page

Phn 3963 013v000

Page 17
Chapter 1: Introduction System Overview

Figure 8: Merged (All) Tab – Radio Parameters Page

Figure 9: Merged (All) Tab – Current Alarms Page

Figure 10: Merged (All) Tab – Event Log Page

Related Pages Drop-Down List

Certain pages include a Related Pages drop-down list on the upper right of the main section of the page. You can
navigate to a page related to the current page by selecting the page from this list.

Figure 11 Related Pages Drop-Down List

Page Refresh and Refresh Interval

To refresh the current page in the Web EMS, click Refresh on the lower right of the page.

Figure 12: Page Refresh Options

Phn 3963 013v000

Page 18
Chapter 1: Introduction System Overview

You can also set the page to refresh automatically at selected intervals. Click the arrow next to Page
Refresh Interval (Seconds) on the lower left of the page and select the automatic refresh interval
(in seconds).

Figure 13: Automatic Refresh Interval Drop-Down List

Export to CSV Option

Some pages in the Web EMS include an Export to CSV option. When the Export to CSV button
appears in the lower right of the page, you can click this button to export the data displayed in that
page as an CSV file.

Advanced Mode and Basic Mode

The Web EMS includes the following menu tree options:
• Advanced – Includes all available options, including both basic link and configuration and
advanced configuration such as QoS and Ethernet protocols.
• Basic – Provides a basic set of menu options that cover most or all of the configurations
necessary to set up and maintain an PTP 820 unit, including link configuration wizards for
most link types. The purpose of Basic mode is to provide the average user with a menu
tree that is simple to navigate yet includes most or all options that most users need.

You can toggle between Advanced or Basic mode by clicking Advanced and Basic in the upper left
corner or any page in the Web EMS. The default mode is Advanced mode.
This manual includes a separate chapter to guide you through PTP 820 configuration using Basic
mode, with cross-references to more detailed explanations of PTP 820 features found elsewhere in
the manual. See Configuring an PTP 820 Unit Using Basic Mode. Except in the Basic mode chapter,
references to the Web EMS menu structure and screens refer to Advanced mode except when
otherwise noted.

Phn 3963 013v000

Page 19
Chapter 1: Introduction System Overview

Phn 3963 013v000

Page 20
Chapter 1: Introduction System Overview

Unit Summary Page

The Unit Summary page is the first page that appears when you log into the Web EMS. It gathers the unit
parameters, current alarms and unit inventory information on a single page for quick viewing.

Figure 14 Unit Summary Page

The Unit Summary page includes:

• Unit Parameters – Basic unit parameters such as the current software version, unit temperature, and voltage
input level. For additional information, see Configuring Unit Parameters.
• Current Alarms – All alarms currently raised on the unit. For additional information, see Viewing Current
Alarms.
The Unit Summary page can be customized to include only specific columns and tables. This enables you to hide
information you do not need in order to focus on the information that is most relevant.
To hide a specific section of the Unit Summary page, click the section title. To display a section that has been
hidden, click the section title again.
To customize which columns appear in a section, click next to the section title. A list of columns is displayed.
Select only the columns you want to display and click again.

Note
When one or more columns are hidden, the icon turns white ( ).

Figure 15 Unit Summary Page – Customizing Columns

Phn 3963 013v000

Page 21
Chapter 1: Introduction System Overview

Radio Summary Page

The Radio Summary page gathers the key link and radio parameters on a single page for quick viewing. To display
the Radio Summary page, select Radio Summary from the Web EMS main menu.

Figure 16 Radio Summary Page

The Radio Summary page includes:

• Link Status – Link status per radio carrier, including whether or not the link is Up, groups to which the link is
assigned (such as LAG, XPIC, protection, and/or Multi-Carrier ABC), and the IP address (both IPv4 and IPv6) of
the remote carrier. For additional information, see Configuring the Radio Parameters.
• Radio Information – The TX and RX frequencies, frequency separation, and channel bandwidth on which the
link is operating. For additional information, see Configuring the Radio Parameters.
• Remote Radio Parameters – Key information about the status of the remote carrier. For additional
information, see Configuring the Remote Radio Parameters.
• Radio Transmitter – Mute status, maximum and operational TX level, modulation, and bit rate. For additional
information, see Configuring the Radio Parameters.
• Radio Receiver – Receiver PMs and statistics, including defective blocks, modem MSE, and RX level,
modulation, and bit rate. For additional information, see Configuring the Radio Parameters and Configuring
the Radio (MRMC) Script(s).
The Radio Summary page can be customized to include only specific columns and tables. This enables you to hide
information you do not need in order to focus on the information that is most relevant.
To hide a specific section of the Radio Summary page, click the section title. To display a section that has been
hidden, click the section title again.
To customize which columns, appear in a section, click next to the section title. A list of columns is displayed.
Select only the columns you want to display and click again.

Note
When one or more columns are hidden, the icon turns white ( ).

Figure 17 Radio Summary Page- Customizing Columns

Security Summary Page

Note
The Security Summary page is only available in system release 10.9.6.

The Security Summary page gathers a number of important security-related parameters on a single page for quick
viewing. To display the Security Summary page, select Security Summary from the Web EMS main menu.

Phn 3963 013v000

Page 22
Chapter 1: Introduction System Overview

Figure 18: Security Summary Page

If FIPS mode is enabled, a yellow Warning icon may appear next to certain items. These items indicate fields for
which the current security settings are not appropriate for FIPS mode. Hover over an item to display a tooltip
explaining the warning.

Phn 3963 013v000

Page 23
Chapter 1: Introduction System Overview

Figure 19: Security Summary Page – FIPS Security Warnings

The Security Summary page includes:

• General Parameters – Includes the following fields:
o FIPS Mode Admin – See Operating in FIPS Mode.
o Session Timeout (Minutes) – See Configuring the Session Timeout.
o Login Banner Text – See Defining a Login Banner.
Radio Payload Encryption – For each radio interface, displays whether AES-256 payload encryption is enabled and
its validation state.
For radio interfaces on which AES-256 payload encryption is enabled, you can display the master key by hovering
the mouse over the icon to the right of the Master Key field.

For additional information, see Configuring AES-256 Payload Encryption.

• Ports & Protocols – Displays information about the current configuration of the following protocols used
for communicating with the device:
o HTTP – See Configuring X.509 CSR Certificates and HTTPS.
o Telnet – See Blocking Telnet Access.
o SNMP – See Configuring SNMP.
• SNMP V3 Users – Displays a list of SNMP V3 users configured on the device. For additional information,
see Configuring SNMP.
• Login & Password Management – Displays login and password security parameters configured on the
device. See Configuring the General Access Control Parameters and Configuring the Password Security
Parameters.
• User Accounts – Displays a list of users configured for the device and their parameters. See Configuring
Users.
• RSA Key – Displays the public RSA key currently configured on the device. See Downloading and Installing
an RSA Key.
The Security Summary page can be customized to include only specific columns and tables. This enables you to
hide information you do not need in order to focus on the information that is most relevant.

Phn 3963 013v000

Page 24
Chapter 1: Introduction System Overview

To hide a specific section of the Radio Summary page, click the section title. To display a section that has been
hidden, click the section title again.
To customize which columns appear in a section, click next to the section title. A list of columns is displayed.
Select only the columns you want to display and click again.

Note
When one or more columns are hidden, the icon turns white ( ).

Figure 20: Security Summary Page – Customizing Columns

Phn 3963 013v000

Page 25
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Reference Guide to Web EMS Menu Structure

The following table shows the Web EMS menu hierarchy, with links to the sections in this document that provide
instructions for the relevant menu item.

Note
Some menu items are only available if the relevant activation key or feature is enabled.

Table 1 PTP 820 Web EMS Menu Hierarchy

Root Sub-Menus For Further Information

Menu
Item

Shelf Management > Chassis Configuration Performing a Hard (Cold) Reset

Setting the Unit to the Factory Default Configuration

Shelf Management > Unit Redundancy Configuring Unit Protection with HSB Radio
Protection

Interfaces > Interface Manager Enabling the Interfaces (Interface Manager)

Interfaces > SFP Displaying SFP DDM and Inventory Information

Management > Unit Parameters Configuring Unit Parameters

Management > NTP Configuration Configuring NTP

Management > Time Services Setting the Time and Date (Optional)

Management > Inventory Displaying Unit Inventory

Platform Management > Unit Info Uploading Unit Info

Management > Login Banner Defining a Login Banner

Management > Networking > Local Changing the Management IP Address

Defining the IP Protocol Version for Initiating
Communications

Management > Networking > Remote Configuring the Remote Unit’s IP Address

Management > SNMP > SNMP Parameters Configuration SNMP

Management > SNMP > Trap Managers Configuring Trap Managers

Management > SNMP > V3 Users Configuration SNMP

Software > Versions Viewing Current Software Versions

Software > Download & Install Downloading and Installing Software

Phn 3963 013v000

Page 26
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

Configuration > Timer Parameters Reserved for future use.

Configuration > Backup Files Viewing Current Backup Files

Configuration > Configuration Management Backing Up and Restoring Configurations

Activation Key > Activation Key Configuring the Activation Key

Configuration

Activation Key > Activation Key Overview Displaying a List of Activation-Key-Enabled Features

Security > General > Configuration Operating in FIPS mode

Security > General > Security Log Upload Uploading the Security Log

Security > General > Configuration Log Uploading the Configuration Log
Upload

Security > X.509 Certificate > CSR Configuring X.509 CSR Certificates and HTTPS

Security > X.509 Certificate > Download & Configuring X.509 CSR Certificates and HTTPS
Install

Security > Access Control > General Configuring the General Access Control Parameters

Security > Access Control > User Profiles Configuring User Profiles

Security > Access Control > User Accounts Configuring Users

Security > Access Control > Password Configuring the Password Security Parameters
Management

Security > Access Control > Change Changing Your Password

Password

Security > Access Control > Radius > Radius Configuring RADIUS
Configuration

Security > Access Control > Radius > Radius Viewing RADIUS User Permissions and Connectivity
Users

Security > Protocols Control Configuring the Session Timeout

PM & Statistics > SFP Displaying SFP DDM and Inventory Information

PM & Statistics > Voltage Configuring Voltage Alarm Thresholds and Displaying
Voltage PMs

Phn 3963 013v000

Page 27
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

Current alarms Viewing Current Alarms

Alarm Statistics Viewing Alarm Statistics

Faults Event Log Viewing the Event Log

Alarm Configuration Editing Alarm Text and Severity

Voltage Alarm Configuration Configuring Voltage Alarm Thresholds

Radio Parameters Configuring the Radio Parameters

Remote Radio Parameters Configuring the Remote Radio Parameters

Radio BER Thresholds Configuring BER Thresholds and Displaying Current

BER

ATPC Configuring ATPC

Payload Encryption Configuring AES-256 Payload Encryption

Ethernet Interface > Configuration Configuring Header De-Duplication and Frame Cut-
Through

Ethernet Interface > Counters Viewing Header De-Duplication and Frame Cut-
Through Counters

MRMC > Symmetrical Scripts > ETSI Configuring the Radio (MRMC) Script(s)

MRMC > Symmetrical Scripts > FCC Configuring the Radio (MRMC) Script(s)
Radio
MRMC > MRMC > Status Displaying MRMC Status

PM & Statistics > Counters Displaying and Clearing Defective Block Counters

PM & Statistics > Signal Level Displaying Signal Level PMs

PM & Statistics > Diversity Not relevant for these products

PM & Statistics > Combined Not relevant for these products

PM & Statistics > Aggregate Displaying Modem BER (Aggregate) PMs

PM & Statistics > MSE Displaying MSE PMs and Configuring MSE PM
Thresholds

PM & Statistics > XPI Displaying XPI PMs and Configuring XPI PM
Threshold

PM & Statistics > MRMC Displaying MRMC PMs

Phn 3963 013v000

Page 28
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

PM & Statistics > Traffic > Displaying Capacity and Throughput PMs
Capacity/Throughput

PM & Statistics > Traffic > Utilization Displaying Utilization PMs

PM & Statistics > Traffic > Frame error rate Displaying Frame Error Rate PMs

Diagnostics > Loopback Performing Radio Loopback

Groups > XPIC Configuring XPIC

Groups > Multi Carrier ABC Configuring Multi-Carrier ABC

Configuring Multiband (Enhanced Multi-Carrier ABC)

Groups > Diversity Configuring a 2x2 MIMO Link

Configuring a 1+0 or 2+2 Space Diversity Link

Groups > AMCC Configuring a 4x4 MIMO Link

Configuring Advanced Space Diversity (ASD)
Configuring Advanced Frequency Reuse (AFR)

General Configuration Setting the MRU Size and the S-VLAN Ethertype

Services Configuring Ethernet Service(s)

Interfaces > Physical Interfaces Configuring Ethernet Interfaces

Interfaces > Logical Interfaces Configuring Ingress Path Classification on a Logical

Interface
Assigning Policers to Interfaces
Configuring the Ingress and Egress Byte
Compensation
Assigning WRED Profiles to Queues
Assigning a Queue Shaper Profile to a Queue
Ethernet Assigning a Service Bundle Shaper Profile to a Service
Bundle
Assigning a Priority Profile to an Interface
Assigning a WFQ Profile to an Interface
Performing Ethernet Loopback

Interfaces > ASP & LLF Configuring Automatic State Propagation and Link
Loss Forwarding

PM & Statistics > Egress CoS PM > Configuring and Displaying Queue-Level PMs
Configuration

PM & Statistics > RMON RMON Statistics

PM & Statistics > Egress CoS Statistics Egress CoS Statistics

Phn 3963 013v000

Page 29
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

PM & Statistics > Port TX Port TX Statistics

PM & Statistics > Port RX Port RX Statistics

PM & Statistics > Egress CoS PM > Egress Configuring and Displaying Queue-Level PMs
CoS PM

QoS > Classification > 802.1Q Modifying the C-VLAN 802.1Q UP and CFI Bit
Classification Table

QoS > Classification > 802.1AD Modifying the S-VLAN 802.1 UP and DEI Bit
Classification Table

QoS > Classification > DSCP Modifying the DSCP Classification Table

QoS > Classification > MPLS Modifying the MPLS EXP Bit Classification Table

QoS > Classification > MAC DA Modifying the MAC DA Classification Table

QoS > Policer > Policer Profile Configuring Policer Profiles

QoS > Marking > 802.1Q Modifying the 802.1Q Marking Table

QoS > Marking > 802.1AD Modifying the 802.1AD Marking Table

QoS > WRED > WRED Profile Configuring WRED

QoS > Shaper > Queue Profiles Configuring Queue Shaper Profiles

QoS > Shaper > Service Bundle Profiles Configuring Service Bundle Shaper Profiles

QoS > Scheduler > Priority Profiles Configuring Priority Profiles

QoS > Scheduler > WFQ Profiles Configuring WFQ Profiles

Protocols > Adaptive Bandwidth Notification Configuring Adaptive Bandwidth Notification (ABN)

Protocols > LLDP > Remote Management Displaying Peer Status

Protocols > LLDP > Advanced > Configuring the General LLDP Parameters
Configuration > Parameters

Protocols > LLDP > Advanced > Configuring the LLDP Port Parameters
Configuration > Port Configuration

Protocols > LLDP > Advanced > Displaying the Unit’s Management Parameters
Configuration > Destination Address

Protocols > LLDP > Advanced > Displaying the Unit’s Management Parameters
Configuration > Management TLV

Protocols > LLDP > Advanced > Remote Displaying Peer Unit’s Management Parameters
System > Management

Phn 3963 013v000

Page 30
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

Protocols > LLDP > Advanced > Remote Displaying Peer Unit’s Management Parameters
System > Remote Table

Protocols > LLDP > Advanced > Local System Displaying the Local Unit’s Parameters
> Parameters

Protocols > LLDP > Advanced > Local System Displaying the Local Unit’s Parameters
> Port

Protocols > LLDP > Advanced > Local System Displaying the Local Unit’s Parameters
> Management

Protocols > LLDP > Advanced > Statistic > Displaying LLDP Statistics
General

Protocols > LLDP > Advanced > Statistic > Displaying LLDP Statistics
Port TX

Protocols > LLDP > Advanced > Statistic > Displaying LLDP Statistics
Port RX

Protocols > SOAM > MD Configuring Service OAM (SOAM) Fault Management
(FM)

Protocols > SOAM > MA/MEG Configuring Service OAM (SOAM) Fault Management
(FM)

Protocols > SOAM > MEP Configuring Service OAM (SOAM) Fault Management
(FM)

Protocols > LACP > Aggregation Displaying LACP Aggregation Status Parameters

Protocols > LACP > Port > Status Displaying LACP Port Status Parameters

Protocols > LACP > Port > Statistics Displaying LACP Port Statistics

Protocols > LACP > Port > Debug Displaying LACP Port Debug Statistics

Interfaces > Groups > LAG Configuring Link Aggregation (LAG) and LACP

SyncE Regenerator Configuring the SyncE Regenerator

Sync Source Configuring the Sync Source

Outgoing Clock Configuring the Outgoing Clock and SSM Messages

Sync 1588 >General Configuration Configuring 1588 Transparent Clock

1588 > Transparet Clock Not relevant for these products

1588 > Boundary Clock > Clock Parameters > Not relevant for these products
Default

Phn 3963 013v000

Page 31
Chapter 1: Introduction Reference Guide to Web EMS Menu Structure

Root Sub-Menus For Further Information

Menu
Item

1588 > Boundary Clock > Clock Parameters > Not relevant for these products
Advanced

1588 > Boundary Clock > Port Parameters Not relevant for these products

1588 > Boundary Clock > Port Statistics Not relevant for these products

From File Applying a Pre-Defined Configuration File

Platform Setup Performing Quick Platform Setup

PIPE > Single Carrier > 1+0 Configuring a 1+0 Link Using the Quick Configuration
Wizard

PIPE > Single Carrier > 1+0 (Repeater) Configuring a 1+0 (Repeater) Link Using the Quick
Configuration Wizard

Quick PIPE > Single Carrier > 2 X (1 + 0) Configuring a 2 x (1+0) Link Using the Quick
Configur- Configuration Wizard
ation PIPE > Multi Carrier ABC > 2 + 0 Configuring a 2+0 Multi-Carrier ABC Link Using the
Quick Configuration Wizard

PIPE > Multi Carrier ABC > Multiband Configuring a Multiband (Enhanced Multi-Carrier
ABC) Link Using the Quick Configuration Wizard

Restart HTTP Restarting the HTTP Server

ifIndex Calculator Calculating an ifIndex

Utilities
Displaying, Searching, and Saving a list of MIB
MIB Reference Guide Entities

Phn 3963 013v000

Page 32
Chapter 2: Getting Started Reference Guide to Web EMS Menu Structure

Chapter 2: Getting Started

This section includes:
• Assigning IP Addresses in the Network
• Establishing a Connection
• Logging on
• Changing Your Password
• Applying a Pre-Defined Configuration File
• Performing Quick Platform Setup
• Mate Management Access (IP Forwarding)
• Configuring In-Band Management
• Changing the Management IP Address
• Configuring the Activation Key
• Setting the Time and Date (Optional)
• Enabling the Interfaces (Interface Manager)
• Configuring the Radio Parameters
• Configuring the Radio (MRMC) Script(s)
• Enabling ACM with Adaptive Transmit Power
• Operating in FIPS Mode
• Configuring Grouping (Optional)
• Creating Service(s) for Traffic

Phn 3963 013v000

Page 101
Chapter 2: Getting Started Assigning IP Addresses in the Network

Assigning IP Addresses in the Network

Before connection over the radio hop is established, it is of high importance that you assign the PTP 820 unit a
dedicated IP address, according to an IP plan for the total network. See Changing the Management IP Address.
By default, a new PTP 820 unit has the following IP settings:
• IP address: 192.168.1.1
• Subnet mask: 255.255.255.0

Caution
If the connection over the link is established with identical IP addresses, an IP address conflict will
occur and remote connection may be lost.

Phn 3963 013v000

Page 102
Chapter 2: Getting Started Establishing a Connection

Establishing a Connection

Connect the PTP 820 unit to a PC by means of a Twisted Pair cable. The cable is connected to the MGT port on
the PTP 820 and to the LAN port on the PC. Refer to the Installation Guide for the type of unit you are connecting for
cable connection instructions.

Phn 3963 013v000

Page 103
Chapter 2: Getting Started PC Setup

PC Setup

To obtain contact between the PC and the PTP 820 unit, it is necessary to configure an IP address on the PC within the
same subnet as the PTP 820 unit. The default PTP 820 IP address is 192.168.1.1. Set the PC address to e.g.
192.168.1.10 and subnet mask to 255.255.255.0. Note the initial settings before changing.

Note
The PTP 820 IP address, as well as the password, should be changed before operating the system. See
Changing the Management IP Address and Changing Your Password. In Basic mode, select Platform >
IP Configuration to change the unit’s IP address. To change your password, click on the upper left of
any Web EMS screen and Select Change Your
.

1. Select Control Panel > All Control Panel Items > Network and Sharing Center.
2. Click Change the adapter settings.
3. Select Local Area Connection > Properties > Internet Protocol Version 4 (TCP/IP), and set the following
parameters:
o IP address: 192.168.1.10
o Subnet mask 255.255.255.0
o No default gateway
4. Click OK to apply the settings.

Phn 3963 013v000

Page 104
Chapter 2: Getting Started PC Setup

Figure 21 Internet Protocol Properties Window

Phn 3963 013v000

Page 105
Chapter 2: Getting Started Logging on

Logging on

1. Open an Internet browser (Internet Explorer or Mozilla Firefox).

2. Enter the default IP address “192.168.1.1” in the Address Bar. The Login page opens.

Figure 22 Login Page

3. In the Login window, enter the following:

o User Name: admin
o Password: admin
4. Click Apply.

Logging in Without Knowing the IP Address

If the unit's IP address has been changed from its default of 192.168.1.1, and you do not know the new IP address,
you can log into the unit by establishing a connection directly to the CPU. This requires a Cambium Networks
proprietary Ethernet cable. This cable should be ordered from Cambium Networks according to the following table.

Table 2 Cables for Direct CPU Connection

Product Part Number Description

PTP 820C and PTP 820S N000082L062A PTP 820C MIMO or Prot management
ODU spltr

Product Cable Marketing Model Cable Description

PTP 820C, PTP 820C-HP, and PTP 820_MIMO_Prot_ mng_spltr CABLE,RJ45M TO 2xRJ45F, 1.0M, WITH
PTP 820S GLANDS, UV PROTECTED

PTP 820E R2H PTP 820_Mini-MNG-CBL CABLE,MiniDP TO RJ45F,0.2M,FOR FIELD

DEBUG

PTP 820E R2H ESP PTP 820_Mini-MNG-CBL_ESP CABLE,MiniDP TO RJ45F,0.2M,FOR FIELD

DEBUG. ESP

For PTP 820E R2H, as an alternative to the proprietary cable described above, you can use a cable with the following
pinouts:

P1 WIRE P2

Phn 3963 013v000

Page 106
Chapter 2: Getting Started Logging on

2 3
TWISTED PAIR 1
8 6

14 1
TWISTED PAIR 2
20 2

SHELL SHIELD SHELL

For PTP 820E ESP, as an alternative to the proprietary cable described above, you can use a cable with the following
pinouts:

P1 WIRE P2

14 3
TWISTED PAIR 1
16 6

18 1
TWISTED PAIR 2
20 2

SHELL SHIELD SHELL

To log in using this cable:

1. The IP address of the CPU is 192.0.2.1. To connect, set up a new Local Area Connection with an IP address as
follows:
o IP address: 192.0.2.3
o Subnet mask 255.255.255.240
o No default gateway

Note
In the event that you fail to connect using 192.0.2.1, use 192.0.2.2 instead.

2. Connect Channel 2 of the cable to the MGT port on the PTP 820
o PTP 820C, PTP 820C-HP, and PTP 820S: The MGT port on the PTP 820 unit.
o PTP 820E: The EXT port on the PTP 820 unit.
3. Connect the single end of the cable to the LAN port on the PC.

Phn 3963 013v000

Page 107
Chapter 2: Getting Started Logging on

4. Verify that the MGT port LED is orange. (When a connection is established using Channel 1 of the cable, the LED
on the MGT port is green.)
5. The system will prompt you for a user name and password (see Figure 13).
6. Enter the default user name and password:
o User Name: admin
o Password: admin
7. Click Apply.
8. After a connection is established, you can view or configure the unit's IP address using the Web EMS. See
Changing the Management IP Address.

Phn 3963 013v000

Page 108
Chapter 2: Getting Started Changing Your Password

Changing Your Password

It is recommended to change your default Admin password as soon as you have logged into the system.
In addition to the Admin password, there is an additional password protected user account, “root user”, which is
configured in the system. The root user password and instructions for changing this password are available from
Cambium Networks Customer Support. It is strongly recommended to change this password.

To change your password , click on the upper left of any Web EMS screen and select Change Your
Password.
In Advanced mode, you can also change your password as follows:

1. Select Platform > Security > Access Control > Change Password. The Change User Password page opens.
Figure 23 Change User Password Page

2. In the Old password field, enter the current password. For example, upon initial login, enter the default password
(admin).
3. In the New password field, enter a new password. If Enforce Password Strength is activated (see Configuring the
Password Security Parameters), the password must meet the following criteria:
o Password length must be at least eight characters.
o Password must include characters of at least three of the following character types:
lower case letters, upper case letters, digits, and special characters. For purposes of
meeting this requirement, upper case letters at the beginning of the password and
digits at the end of the password are not counted.
o A password cannot be repeated within five changes of the password.
4. Click Apply.

Phn 3963 013v000

Page 109
Chapter 2: Getting Started Applying a Pre-Defined Configuration File

Applying a Pre-Defined Configuration File

PTP 820 units can be configured from the Web EMS in a single step by applying a pre-defined configuration file. A pre-
defined configuration file can be prepared for multiple PTP 820 units, with the relevant configuration details specified
and differentiated per-unit.
Pre-defined configuration files can include all the parameters necessary to configure basic links, including:
• Platform parameters:
o ETSI to ANSI conversion
o General unit parameters, such as unit name, location, and contact person
o Activation Key (or Demo mode) configuration
o IP configuration (IPv4 and IPv6)
o NTP configuration
o Basic SNMP Parameters (Enable/Disable, Read and Write Communities)
o Time services configuration
• Interface configuration:
o Radio
o Ethernet
o LAG
o Radio protection
o Multi-Carrier ABC groups
• Advanced radio configuration
o XPIC
o MIMO
• Services configuration
o Management
o Point-to-Point
o Multipoint
The pre-defined configuration file is generated by Cambium Global Services and provided as a service.
The pre-defined configuration file must be compatible with the Release version the PTP 820 device is running.
Configuration files created for Release 9.2 cannot be used with later Release versions. Configuration files must also be
compatible with the type of PTP 820 device. For example, a configuration file created for PTP 820C cannot be applied
to an PTP 820G device.
For further information on the creation of pre-defined configurations, consult your Cambium Networks
representative.
You can apply a pre-defined configuration file from Advanced mode or Basic mode.
To apply a pre-defined configuration file:
1. Select Quick Configuration > From File. The Quick Configuration – From File page opens.

Figure 24: Quick Configuration – From File Page

2. Click Browse, and select the configuration file for your unit.

Phn 3963 013v000

Page 110
Chapter 2: Getting Started Applying a Pre-Defined Configuration File

Figure 25: Quick Configuration – From File Page – Configuration File Loaded
3. In the Device List field, select the PTP 820 unit you are configuring.

Note:
Although the configuration file may contain parameters for multiple types of devices, only
devices of the same product type as the unit you are configuring are displayed in this field.

4. Optionally, click View file to display the configuration file (read-only).

5. To initiate the configuration, click Submit. Progress is updated in the Quick Configuration – From File page.

When the configuration is complete, the unit reboots.

Note:
If the pre-defined configuration file included a new IP address for the unit, make sure to
configure an IP address on the PC or laptop you are using to perform the configuration within
the same subnet as the PTP 820 unit’s new IP address.

Phn 3963 013v000

Page 111
Chapter 2: Getting Started Performing Quick Platform Setup

Performing Quick Platform Setup

The Platform Setup page in the Web EMS centralizes the main configurable items from several Web EMS pages in a
single location:
• Unit Parameters (Name, Contact Person, Location, Longitude, and Latitude)
• IPv4 Address, Subnet Mask, and Default Gateway
• NTP Enable/Disable
• Demo Activation Key Enable/Disable
• SNMP Parameters
These items enable you to configure the basic platform parameters quickly, in a single Web EMS page. Combined with
the quick link configuration wizards, this enables you to configure a new link in the field quickly and efficiently, to the
point where the link is up and functioning and any necessary advanced configurations can be performed remotely
without the need to physically access the PTP 820 unit.
To use the Platform Setup page:
1. Select Quick Configuration > Platform Setup. The Quick Configuration – Platform Setup page opens.
Figure 26 Quick Configuration – Platform Setup Page

2. The Unit Parameters section is optional. For details on each field, see Configuring Unit Parameters.

Phn 3963 013v000

Page 112
Chapter 2: Getting Started Performing Quick Platform Setup

3. In the IPv4 Address section, configure the unit’s management IP address, subnet mask, and, optionally, a default
gateway. If you want to use an IPv6 address, see Changing the Management IP Address.
4. In the Date & Time section, you can enable Network Time Protocol (NTP). NTP distributes Coordinated Universal
Time (UTC) throughout the system, using a jitter buffer to neutralize the effects of variable latency.
If you select Enable, the NTP version and NTP server IP address fields are also displayed, enabling you to
configure the NTP parameters. For details on these fields, see Configuring NTP.

5. In the Activation Key section, you can enable or disable Demo mode in the Demo admin field. Demo mode
enables all features for 60 days. When demo mode expires, the most recent valid activation key goes into effect.
The 60-day period is only counted when the system is powered up. 10 days before demo mode expires, an alarm
is raised indicating that demo mode is about to expire.
If you set Demo admin to Disable, the Activation Key field is displayed. Enter a valid activation key in this field.
For a full explanation of activation keys, see Configuring the Activation Key.

6. In the SNMP Parameters section, you can set whether to enable or disable SNMP monitoring in the Admin field,
and set the SNMP Read Community and SNMP Write Community. For a full explanation of SNMP parameters, see
Configuring SNMP.

7. Click Finish. The Selection Summary page opens. To go back and change any of the parameters, click Back. To
implement the new parameters, click Submit.

Phn 3963 013v000

Page 113
Chapter 2: Getting Started Performing Quick Platform Setup

Figure 27 Quick Configuration– Platform Setup Summary Page

Phn 3963 013v000

Page 114
Chapter 2: Getting Started Mate Management Access (IP Forwarding)

Mate Management Access (IP Forwarding)

Mate Management Access enables the use of in-band management for nodes that use two PTP 820C or PTP 820C-HP
units (4x4 MIMO, 2+2 XPIC, and 4+0 Multi-Carrier ABC), where traffic comes from an external switch operating in LAG
mode. When Mate Management Access is enabled, the two units exchange incoming management packets, ensuring
that all management data is received by both units.
Mate Management Access must be configured via the CLI. For instructions, see Mate Management Access (IP
Forwarding) (CLI) on page 570.

Phn 3963 013v000

Page 115
Chapter 2: Getting Started Configuring In-Band Management

Configuring In-Band Management

You can configure in-band management in order to manage the unit remotely via its radio and/or Ethernet interfaces.

Note
Before configuring in-band management, it is recommended to review the configuration
recommendations for in-band management listed in Configuration Tips.
To use in-band management for nodes that utilize two PTP 820C or PTP 820C-HP units (4x4 MIMO,
2x2 XPIC, and 4+0 Multi-Carrier ABC), you must first configure Mate Management Access (IP
Forwarding). For instructions, see Mate Management Access (IP Forwarding) (CLI).

To use in-band management for nodes that utilize two PTP 820C units (4x4 MIMO, 2x2 XPIC, and 4+0 Multi-Carrier
ABC), you must first configure Mate Management Access (IP Forwarding). For instructions, see on page 115.
Each PTP 820C or PTP 820C-HP unit includes a pre-defined management service with Service ID 257. The
management service is a multipoint service that connects the two local management ports and the network element
host CPU in a single service. In order to enable in-band management, you must add at least one service point to the
management service, in the direction of the remote site or sites from which you want to access the unit for
management.

Note
In order to use in-band management, it must be supported on the external switch.

For instructions on adding service points, see Configuring Service Points.

Phn 3963 013v000

Page 116
Chapter 2: Getting Started Changing the Management IP Address

Changing the Management IP Address

Related Topics:
• Defining the IP Protocol Version for Initiating Communications
• Configuring the Remote Unit’s IP Address
To change the management IP address of the local unit:
1. Select Platform > Management > Networking > Local. The Local Networking Configuration page opens.

Figure 28 Local Networking Configuration Page

2. Optionally, in the Description field, enter descriptive information about the unit.
3. In the IP address field, enter an IP address for the unit. You can enter the address in IPv4 format in this field,
and/or in IPv6 format in the IPv6 Address field. The unit will receive communications whether they are sent to its
IPv4 address or its IPv6 address.
4. In the Subnet mask field, enter the subnet mask.
5. Optionally, in the Default gateway field, enter the default gateway address.
6. Optionally, in the IPv6 Address field, enter an IPv6 address for the unit. You can enter the address in IPv6 format
in this field, and/or in IPv4 format in the IP Address field. The unit will receive communications whether they are
sent to its IPv4 address or its IPv6 address.
7. If you entered an IPv6 address, enter the IPv6 prefix length in the IPv6 Prefix-Length field.
8. Optionally, if you entered an IPv6 address, enter the default gateway in IPv6 format in the Default Gateway IPv6
field.
9. Click Apply.

Phn 3963 013v000

Page 117
Chapter 2: Getting Started Configuring the Activation Key

Configuring the Activation Key

This section includes:

• Activation Key Overview
• Viewing the Activation Key Status Parameters
• Entering the Activation Key
• Activating a Demo Activation Key
• Displaying a List of Activation-Key-Enabled Features

Activation Key Overview

PTP 820 offers a pay-as-you-grow concept in which future capacity growth and additional functionality can be
enabled with activation keys. Each device contains a single unified activation key cipher.
New PTP 820 units are delivered with a default activation key that enables you to manage and configure the unit.
Additional feature and capacity support requires you to enter an activation key cipher in the Activation Key
Configuration page. Contact your vendor to obtain your activation key cipher.

Note
To obtain an activation key cipher, you may need to provide the unit’s serial number. You can display
the serial number in the Web EMS Inventory page. See Displaying Unit Inventory.

Each required feature and capacity should be purchased with an appropriate activation key. It is not permitted to
enable features that are not covered by a valid activation key. In the event that the activation-key-enabled capacity
and feature set is exceeded, an Activation Key Violation alarm occurs and the Web EMS displays a yellow background
and an activation key violation warning. 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.
In order to clear the alarm, you must configure the system to comply with the activation key that has been loaded in
the system. The system automatically checks the configuration to ensure that it complies with the activation-key-
enabled features and capacities. If no violation is detected, the alarm is cleared.
When entering sanction state, the system configuration remains unchanged, even after power cycles. However, the
alarms remain hidden until an appropriate activation key is entered or the features and capacities are re-configured
to be within the parameters of the current activation key.
A demo activation key is available that enables all features for 60 days. When the demo activation key expires, the
most recent valid activation key goes into effect. The 60-day period is only counted when the system is powered up.
10 days before the demo activation key expires, an alarm is raised indicating that the demo activation key is about to
expire.

Viewing the Activation Key Status Parameters

To display the current activation key status parameters:
1. Select Platform > Activation Key > Activation Key Configuration. The Activation Key Configuration page opens.

Phn 3963 013v000

Page 118
Chapter 2: Getting Started Configuring the Activation Key

Figure 29 Activation Key Configuration Page

Table 3 PTP 820 Web EMS Menu Hierarchy

Parameter Definition

Type Displays the current activation key type.

Validation number Displays a random, system-generated validation number.

Date code Displays a date code used for validation of the current activation key
cipher.

Violation runtime counter In the event of an Activation Key Violation alarm, this field displays
(hours) the number of hours remaining in the 48-hour activation key
violation grace period.

Sanction state If an Activation Key Violation alarm has occurred, and the 48-hour
activation key violation grace period has expired without the system
having been brought into conformance with the activation-key-
enabled capacity and feature set, Yes appears in this field to indicate
that the system is in an Activation Key Violation sanction state. All
other alarms are hidden until the capacity and features in use are
brought within the activation-key-enabled capacity and feature set.

Entering the Activation Key

1. To enter a new activation key:
2. Select Platform > Activation Key > Activation Key Configuration. The Activation Key Configuration page opens
(Figure 20).
3. Enter the activation key cipher you have received from the vendor in the Activation Key field. The activation key
cipher is a string that enables all features and capacities that have been purchased for the unit.
4. Click Apply.

Phn 3963 013v000

Page 119
Chapter 2: Getting Started Configuring the Activation Key

If the activation key cipher is not legal (e.g., a typing mistake or an invalid serial number), an Activation Key Loading
Failure event is sent to the Event Log. When a legal activation key cipher is entered, an Activation Key Loaded
Successfully event is sent to the Event Log.

Activating Demo Mode

To activate demo mode:
1. Select Platform > Activation Key > Activation Key Configuration. The Activation Key Configuration page opens
(Figure 21).
2. In the Demo admin field, select Enable.
3. Click Apply.
The Demo timer field displays the number of hours that remain before the demo activation key expires.

Activation Key Reclaim

If it is necessary to deactivate an PTP 820 device, whether to return it for repairs or for any other reason, the device’s
activation key can be reclaimed for a credit that can be applied to activation keys for other devices.

Note
Activation key reclaim is only available for PTP 820 devices running system release 9.2 or later.

Where the customer has purchased upgrade activation keys, credit is given for the full feature or capacity, not for
each individual upgrade. For example, if the customer purchased two capacity activation keys for 300M and later
purchased one upgrade activation key to 350M, credit is given as if the customer had purchased one activation key
for 350M and one activation key for 300M.
For instructions on how to reclaim an activation key, refer to the User Guide for the Activation Key Management
System, Rev A.15 or later, Chapter 7, Reclaiming an Activation Key.

Displaying a List of Activation-Key-Enabled Features

To display the status of activation key coverage for features and capacities in the PTP 820:
1. In Adavanced mode Platform > Activation Key > Activation Key Overview. The Activation Key Overview page
opens.

Note
To display this information in Basic mode, select Platform > Activation
Key and click Show Activation Key Overivew at the bottom of the Activation Key page.

Phn 3963 013v000

Page 120
Chapter 2: Getting Started Configuring the Activation Key

Figure 30 Activation Key Overview Page

The Activation Key Overview page displays the activation-key-enabled features and capacities for the PTP 820, and
indicates the activation key status of each feature according to the activation key currently implemented in the unit.

Note
Some of the features listed in the Activation Key Overview page may not be supported in the
currently installed software version. For details on feature support, refer to the Release Notes or
Technical Description for the PTP 820 product and System release you are using.

Table 4 Activation Key-Enabled-Features Table Parameters

Parameter Definition

Feature ID A unique ID that identifies the feature.

Feature name The name of the feature.

Feature Description A description of the feature.

Activation key-enabled Indicates whether the activation-key-enabled feature is actually

feature usage being used.

Activation key-enabled Indicates whether the feature is allowed under the activation key
feature credit that is currently installed in the unit.

Activation key violation Indicates whether the system configuration violates the currently
status installed activation key with respect to this feature.

Table 6: Activation Key-Enabled-Features Description

Activation Key Name Description
Services Mode Enables a number of Ethernet services, depending on
the type of activation key:
Smart-Pipe –Smart Pipe (L1) services only (unlimited)
and a single management service with MSTP.
Edge-CET Node – Up to 8 services (all supported service
types).
Agg-Lvl-1-CET-Node – Up to 64 services (all supported
service types).

Phn 3963 013v000

Page 121
Chapter 2: Getting Started Configuring the Activation Key

Activation Key Name Description

Agg-Lvl-2-CET-Node – Up to 1024 services (all
supported service types).
Any CET activation key also enables the following:
A GbE traffic port in addition to the port provided by
the default activation key, for a total of 2 GbE traffic
ports.
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.

Number of Services Indicates how many services are allowed according to

the Services Mode activation key, and how many are
actually configured on the device.

H-QoS Not relevant in the current System Release release.

Network Resiliency Enables the following network resiliency

protocols:
• G.8032
Only relevant for PTP 820C devices.

Ethernet OAM – Fault Management Enables Connectivity Fault Management (FM) per
Y.1731 (CET mode only).

Ethernet OAM – Performance Monitoring Not relevant in the current systems release.

LACP Enables Link Aggregation Control Protocol (LACP).

Sync Unit Enables the G.8262 synchronization unit. This

activation key is required in order to provide end-to-
end synchronization distribution on the physical layer.
This activation key is also required to use SyncE.

IEEE 1588 Transparent Clock Enables IEEE-1588 Transparent Clock.

IEEE 1588 Ordinary Clock (quantity) Not relevant in the current system release.

IEEE 1588 Boundary Clock Not relevant for all-outdoor devices.

Main Card Redundancy Not relevant for all-outdoor devices.

TDM Pseudowire Not relevant for all-outdoor devices.

Frame cut-through Enables Frame Cut-Through.

Secured Management Enables secure management protocols (SSH, HTTPS,

SFTP, SNMPv3, and RADIUS).

FE traffic ports (quantity) Displays the number of FE traffic ports allowed under
the current activation key.

GbE traffic ports (quantity) Displays the number of GbE traffic ports allowed under
the current activation key.

Phn 3963 013v000

Page 122
Chapter 2: Getting Started Configuring the Activation Key

Activation Key Name Description

10GbE traffic ports (quantity) Displays the number of 10G traffic ports allowed under
the current activation key. Only relevant for PTP 820E
devices.

ACM (quantity) Displays the number of radio carriers that are allowed
to use ACM under the current activation key. Only
elevant for PTP 820E devices.

Narrow CHBW 1.75MHz script (quantity) Not relevant for all-outdoor devices.

Header De-Duplication (quantity) Displays the number of radio carriers that are allowed
to use Header De-Duplication.

XPIC (quantity) Displays the number of radio carriers that are allowed
to use XPIC. Each carrier in the XPIC pair requires an
XPIC activation key.

Multi-Carrier ABC (quantity) Displays the number of radio carriers that are allowed
to use Multi-Carrier ABC. Each carrier in the Multi-
Carrier ABC group requires a Multi-Carrier ABC
activation key.

MIMO Enables the use of MIMO. A separate activation key is

required for each core in the MIMO configuration.

SD Not relevant for all-outdoor devices.

ASD Enables the use of Advanced Space Diversity (ASD). A

separate activation key is required per core. This
means that for a single link, with two PTP 820C or PTP
820C-HP units on one side of the link and one PTP
820C or PTP 820C-HP unit on the other side, a total of
six ASD activation keys are required.

AFR 1+0 (quantity) Enables the use of Advanced Frequency Reuse (AFR).
For an AFR 1+0- configuration, two activation keys are
required for the hub site (one per carrier) and one
activation key is required for each tail site.

Payload Encryption AES-256 (quantity) Displays the number of radio carriers that can use of
AES-256 encryption Note that:
If no AES activation key is configured for the unit and
the user attempts to enable AES on a radio carrier, in
addition to an Activation Key Violation alarm the
feature will remain inactive and no encryption will be
performed.
After entering an AES activation key, the user must
reset the unit before AES can be activated. Unit reset is
only necessary for the first AES activation key. If AES
activation keys are acquired later for additional radio
carriers, unit reset is not necessary.

Second core activation Enables the use of the second core on an PTP 820C.

Phn 3963 013v000

Page 123
Chapter 2: Getting Started Configuring the Activation Key

Activation Key Name Description

Second core activation for RFU-D Note relevant for all-outdoor devices.

Second core activation for HP Enables the use of the second core on an PTP 820C-
HP.

Second modem activation Note relevant for all-outdoor devices.

RFU port activation key Not relevant in the current system release.

Radio capacity level 1 Displays the number of radio carriers for which there is
permission to use up to 10 Mbps. This is the default
level, so every radio carrier on the device has this
capacity level.

Radio capacity level 2 Displays the number of radio carriers for which there is
permission to use up to 50 Mbps.

Radio capacity level 3 Displays the number of radio carriers for which there is
permission to use up to 100 Mbps.

Radio capacity level 4 Displays the number of radio carriers for which there is
permission to use up to 150 Mbps.

Radio capacity level 5 Displays the number of radio carriers for which there is
permission to use up to 200 Mbps.

Radio capacity level 6 Displays the number of radio carriers for which there is
permission to use up to 225 Mbps.

Radio capacity level 7 Displays the number of radio carriers for which there is
permission to use up to 250 Mbps.

Radio capacity level 8 Displays the number of radio carriers for which there is
permission to use up to 300 Mbps.

Radio capacity level 9 Displays the number of radio carriers for which there is
permission to use up to 350 Mbps.

Radio capacity level 10 Displays the number of radio carriers for which there is
permission to use up to 400 Mbps.

Radio capacity level 11 Displays the number of radio carriers for which there is
permission to use up to 450 Mbps.

Radio capacity level 12 Displays the number of radio carriers for which there is
permission to use up to 500 Mbps.

Radio capacity level 13 Displays the number of radio carriers for which there is
permission to use up to 650 Mbps.

Radio capacity level 14 Displays the number of radio carriers for which there is
permission to use up to 1000 Mbps.

Radio capacity level 15 Displays the number of radio carriers for which there is
permission to use up to 1600 Mbps.

Radio capacity level 16 Displays the number of radio carriers for which there is
permission to use up to 2000 Mbps.

Phn 3963 013v000

Page 124
Chapter 2: Getting Started Configuring the Activation Key

Activation Key Name Description

Radio capacity level 17 Displays the number of radio carriers for which there is
permission to use up to 2500 Mbps.

Auto State Propagation and LLF Enables the use of Link Loss Forwarding (LLF) with
Automatic State Propagation (ASP). Without the
activation key, only one LLF ID can be configured. This
means that only one ASP pair can be configured per
radio interface or radio group.

Enhanced Multi-Carrier ABC (quantity) Enables the configuration and use of a Multiband
(Enhanced Multi-Carrier ABC) link. Two activation keys
are required per Multiband node, on the PTP 820E.
One of these activation keys is for the radio port, the
other is for the Ethernet port carrying traffic to the unit
paired with the PTP 820E. No activation key is required
for the unit paired with the PTP 820E.

Phn 3963 013v000

Page 125
Chapter 2: Getting Started Setting the Time and Date (Optional)

Setting the Time and Date (Optional)

Related Topics:
• Configuring NTP
PTP 820 uses the Universal Time Coordinated (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).
Every PTP 820 unit holds the UTC offset and daylight savings time information for the location of the unit. Each
management unit presenting the information uses its own UTC offset to present the information in the correct time.

Note
If the unit is powered down, the time and date are saved for 96 hours (four days). If the unit remains
powered down for longer, the time and date may need to be reconfigured.

1. To display and configure the UTC parameters:Select Platform > Management > Time Services in Advanced
mode or Platform > Time Services in Basic mode.. The Time Services page opens.

Figure 31 Time Services Page

1. Configure the fields listed in Table 5.

2. Click Apply.

Table 5 Time Services Parameters

Parameter Definition

Date & Time UTC Date and Time The UTC date and time.
Configuration
Local Current Date and Read-only. The calculated local date and time, based
Time on the local clock, Universal Time Coordinated (UTC),
and Daylight Savings Time (DST) configurations.

Phn 3963 013v000

Page 126
Chapter 2: Getting Started Setting the Time and Date (Optional)

Parameter Definition

Offset from GMT UTC Offset Hours The required hours offset (positive or negative)
relative to GMT. This is used to offset the clock
relative to GMT, according to the global meridian
location.

UTC Offset Minutes The required minutes offset (positive or negative)

relative to GMT. This is used to offset the clock
relative to GMT, according to the global meridian
location.

Daylight Saving Start Month The month when Daylight Savings Time begins.
Time
Day The date in the month when Daylight Savings Time
begins.

Daylight Saving End Month The month when Daylight Savings Time ends.
Time
Day The date in the month when Daylight Savings Time
ends.

DST Offset (Hours) The required offset, in hours, for Daylight Savings
Time. Only positive offset is supported.

Phn 3963 013v000

Page 127
Chapter 2: Getting Started Enabling the Interfaces (Interface Manager)

Enabling the Interfaces (Interface Manager)

By default:
• Ethernet traffic interfaces are disabled and must be manually enabled.
• The Ethernet management interface is enabled.
• Radio interfaces are enabled.

Note
PTP 820S units have a single radio interface.

To enable or disable interfaces:

1. Select Platform > Management > Interface Manager. The Interface Manager page opens, displaying all of the
system's traffic and management interfaces.

Figure 32 Interface Manager Page

To enable or disable an individual interface:

1. Select the interface in the Interface Manager table.
2. Click Edit. The Interface Manager – Edit page opens.

Figure 33 Interface Manager – Edit Page

3. In the Admin status field, select Up to enable the interface or Down to disable the interface.
4. Click Apply, then Close.

To enable or disable multiple interfaces:

1. Select the interfaces in the Interface Manager table or select all the interfaces by selecting the check box in the
top row.
2. In the Multiple Selection Operation section underneath the Interface Manager Table, select Admin status – Up or
Admin status – Down.

Phn 3963 013v000

Page 128
Chapter 2: Getting Started Enabling the Interfaces (Interface Manager)

Figure 34 Multiple Selection Operation Section (Interface Manager Page)

3. Click Apply.

Note
The Operational Status field displays the current, actual operational state of the interface (Up or
Down).

Phn 3963 013v000

Page 129
 Chapter 2: Getting Started PTP 820E Management Interface

PTP 820E Management Interface

The management ports of PTP 820E can be used for traffic as well as management and (except for PTP
820E ESE) PoE. This increases the number of available Ethernet traffic ports for these devices and
enables customers to configure setups in which a single cable is used to carry management, power,
and traffic from the customer equipment to the PTP 820 device.
The following are the relevant ports:
• PTP 820E:
◦ ESP and ESS – Port 1 (Management/PoE/Traffic)
◦ ESE – Port 3 (Management/Traffic)
In most respects, these ports can be used like other Ethernet traffic ports, including:
• Support for Auto Negotiation
• Support for synchronization
• Support for LLDP
• Support for Y.1731 CFM-SOAM
• Support for RMON
Because this interface is used for management, a management service (Service ID 257) and service point
(Service Point ID 1) are configured on the interface and cannot be removed.
A Policer (Policer ID 251) is attached to this service point and cannot be edited or removed.
In order to ensure that the port can be used for traffic services, the Attached Interface Type of the
management service point can be modified from its default value of dot1q untagged.
Leaving the management service point as Untagged will result in untagged data traffic being classified
into the management service. This should be avoided.
The management service point can be changed to dot1q with a specific C-VLAN, or to s-tag or QinQ,
giving you the flexibility to configure services on the interface according to the expected user traffic.
See Editing a Service Point.
Specifically, it is recommended to perform the following service configuration changes:
• Change the VLAN encapsulation of the management service point from
Untagged to a specific VLAN.
• Configure a PIPE service point for data traffic on the management port. This service
point should be untagged (e.g., dot1q-untagged or Bundle-C with “Untagged” as
the C-VLAN encapsulation).

Note
As long as the management service point is configured as dot1q- Untagged, you will be unable to
configure the PIPE service point.

Be very careful when reconfiguring this service point to ensure continued management access. Make
sure that if you change the management service point’s VLAN tagging, management traffic is then
tagged with the same VLAN as the management service point.
.
The following limitations exist for these ports:
• Cannot belong to LAG groups
• Do not support MSTP and G.8032
• Automatic State Propagation can only be used in CSF mode
Phn 3963 013v000
Page 130
Chapter 2: Getting Started PTP 820E Management Interface

To use the PTP 820E management port for traffic, you should perform the following configurations:
• An egress Service Bundle Shaper (Shaper ID 256) is also attached to this service
point. This Shaper cannot be edited, but it can and must be either detached or
disabled on the port in order for the port to support 1G traffic. See Assigning a
Service Bundle Shaper Profile to a Service Bundle.
• Change the port speed from its default value of 100 Mbps to 1 Gbps. See
Configuring Ethernet Interfaces.
• Enable the LOC alarm (Alarm ID 401) for the management port. By default, this alarm
is disabled on the management port and must be manually enabled when using the
port for traffic.

Phn 3963 013v000

Page 131
 To enable the LOC alarm:
1 Select Platform > Interfaces > Traffic over Management. The Traffic over
Management page opens.

Figure 35: Traffic over Management Page

2 In the Loss of Carrier Alarm Supported field, select Yes.

3 Click Apply.

Phn 3963 013v000

Page 132
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Configuring the Radio (MRMC) Script(s)

Related Topics:
• Displaying MRMC Status
Multi-Rate Multi-Constellation (MRMC) radio scripts define how the radio utilizes its available capacity. Each script
is a pre-defined collection of configuration settings that specify the radio’s transmit and receive levels, link
modulation, channel spacing, and bit rate. Scripts apply uniform transmit and receive rates that remain constant
regardless of environmental impact on radio operation.

Note
The list of available scripts reflects activation-key-enabled features. Only scripts within your
activation-key-enabled capacity will be displayed.

To display the MRMC scripts and their basic parameters and select a script:
1. Select one of the following, depending on the regulatory framework in which you are operating:
o To display ETSI scripts, select Radio > MRMC > Symmetrical Scripts > ETSI.
o To display ANSI (FCC) scripts, select Radio > MRMC > Symmetrical Scripts > FCC.
The MRMC Symmetrical Scripts page opens. For a description of the parameters displayed in the MRMC
Symmetrical Scripts page, see Configuring the Radio (MRMC) Scripts (s).

Note
PTP 820S and PTP 820E units do not support XPIC or MIMO. For detailed information on the exact
scripts and profiles available per unit type, channel, and configuration, refer to the Release Notes for
the System Release version you are using.

Figure 36 MRMC Symmetrical Scripts Page (ETSI)

Phn 3963 013v000

Page 133
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Figure 37 MRMC Symmetrical Scripts Page (PTP 820C) (ETSI)

Figure 38 MRMC Symmetrical Scripts Page (PTP 820C) (FCC)

2. In the Select Radio Interface field, select the slot for which you want to configure the script.

Note
This step is only applicable for PTP 820C and PTP 820C-HP units.

3. Select the script you want to assign to the radio. The currently-assigned script is marked by a check mark
(Script ID 1504 in the image above).
4. Click Configure Script. A separate MRMC Symmetrical Scripts page opens similar to the page shown below.

Phn 3963 013v000

Page 134
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Figure 39 MRMC Symmetrical Scripts Page (Configuration) – PTP 820C

5. In the MRMC Script operational mode field, select the ACM mode: Fixed or Adaptive.
o Fixed ACM mode applies constant Tx and Rx rates. However, unlike regular scripts,
with a Fixed ACM script you can specify a maximum profile to inhibit inefficient
transmission levels.
o In Adaptive ACM mode, Tx and Rx rates are dynamic. An ACM-enabled radio system
automatically chooses which profile to use according to the channel fading
conditions. If you select Adaptive, two fields are displayed enabling you to select
minimum and maximum ACM profiles.

Phn 3963 013v000

Page 135
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Figure 40 MRMC Symmetrical Scripts Page – Configuration – Adaptive Mode (PTP 820C)

6. Define the script profile or profiles

o If you selected Fixed ACM mode, select the ACM profile in the MRMC Script profile
field.
o If you selected Adaptive ACM mode, select the maximum and minimum ACM profiles
in the MRMC Script maximum profile and the MRMC Script minimum profile fields.

Note
Refer to Configuring the Radio (MRMC) Scrips(s) for a list of available radio profiles.

7. Click Apply.

Note
Changing the script resets the radio interface and affects traffic. Changing the maximum or minimum
profile does not reset the radio interface.

Configuring the Radio (MRMC) Scrips(s) describes the MRMC Symmetrical Scripts page parameters.

Phn 3963 013v000

Page 136
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Table 6 MRMC Symmetrical Scripts Page Parameters

Parameter Definition

Script ID A unique ID assigned to the script in the system.

Channel bandwidth (MHz) The script's channel bandwidth (channel spacing).

Occupied bandwidth The script's occupied bandwidth.

(MHz)

Modulation Script Indicates whether the script supports Adaptive Coding Modulation (ACM). In
ACM mode, a range of profiles determines Tx and Rx rates. This enables the
radio to modify its transmit and receive levels in response to environmental
conditions.

Multi-Carrier PTP 820C and PTP 820C-HP only. Indicates the Multi-Carrier status of the
script (XPIC, MIMO, or Single-Carrier).

Adjacent Channel Displays the script’s adjacent channel polarization mode.

Latency Level Always displays Normal.

Symmetry Indicates that the script is symmetrical (Normal). Only symmetrical scripts are
supported in the current release.

Standard Indicates whether the script is compatible with ETSI or FCC (ANSI) standards,
or both.

MRMC Script operational The ACM mode: Fixed or Adaptive.

mode • Fixed ACM mode applies constant TX and RX rates. However, unlike
regular scripts, with a Fixed ACM script you can specify a maximum
profile to inhibit inefficient transmission levels.
• In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled
radio system automatically chooses which profile to use according to the
channel fading conditions.

MRMC Script profile Fixed ACM mode only: The profile in which the system will operate.

MRMC Script maximum The maximum profile for the script. For example, if you select a maximum
profile profile of 5, the system will not climb above profile 5, even if channel fading
conditions allow it.

MRMC Script minimum Adaptive ACM mode only: The minimum profile for the script. For example, if
profile you select a minimum profile of 3, the system will not go below profile 3
regardless of the channel fading conditions. The minimum profile cannot be
greater than the maximum profile, but it can be equal to it.

Phn 3963 013v000

Page 137
Chapter 2: Getting Started Configuring the Radio (MRMC) Script(s)

Radio Profiles
Table 7 lists the available radio profiles for PTP 820C, PTP 820C-HP, and PTP 820S. Table 17 lists
the available radio profiles for PTP 820E.

Note
For detailed information on the exact profiles available per unit type, channel, and configuration,
refer to the Release Notes for the software version you are using.

Table 7 Available Radio Profiles for PTP 820C, PTP 820C-HP and PTP 820S

Parameter Definition

Profile 0 QPSK

Profile 1 8 QAM

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)

Profile 10 2048 QAM

Table 8 Available Radio Profiles for PTP 820E

Parameter Definition

Profile 0 BPSK

Profile 1 QPSK

Profile 2 8 QAM

Profile 3 16 QAM

Profile 4 32 QAM

Profile 5 64 QAM

Profile 6 128 QAM

Profile 7 256 QAM

Phn 3963 013v000

Page 138
Chapter 2: Getting Started Running the Frequency Scanner (PTP 820E)

Running the Frequency Scanner (PTP 820E)

To facilitate optimal operation in frequency scenarios, PTP 820E include a frequency scanner that enables you to
scan a defined frequency range and determine the current interference level for each channel.
The frequency scanner can be used both in the initial provisioning of the link and at any time after the link has
been provisioned. The scanner determines the interference level for each RX channel. Using this information, you
can select the channels with the least interference, and configure the unit’s frequency accordingly.
When the frequency scan begins, the unit stops receiving traffic until the scan is complete. This means the link is
effectively down while the frequency scanner is operating. Once the frequency scan operation has been
completed, either at the end of a Single Mode scan or by user action in the case of a Continuous scan, the link is
automatically restored at the same frequency settings as before the scan.

Note:
The frequency scanner does not automatically change the link’s frequency settings. These
settings must be changed manually. The frequency scanner simply provides information you can
use in determining the proper frequency configuration.

To perform a frequency scan:

1. Select Radio > Frequency Scanner. The Frequency Scanner page opens.

Figure 41 Frequency Scanner Page – PTP820E – Single Mode

2. Enter a range for the scan (in MHz) by entering the lower frequency of the range in the Start Frequency
field and the upper frequency of the range in the Stop Frequency field. The range of permissible values is:
o For PTP 820E : 81000-86000 MHz on the high side and 71000-76000 MHz on the low side

Phn 3963 013v000

Page 139
Chapter 2: Getting Started Running the Frequency Scanner (PTP 820E)

3. In the Scanner Mode field, select from the following options:

o Continuous Mode – The frequency scanner scans each channel in the script, and repeats the
scan continuously until you manually stop the scan by clicking Stop. For each channel, the Web
EMS will display the minimum, maximum, and most recently measured interference levels, in
both table and graph formats.
o Single Mode – The frequency scanner scans each channel in the script once, over the defined
frequency range. For each channel, the Web EMS will display the measured interference level.

Note:
When running the Frequency Scanner on the remote side of a link using in-band management,
make sure to run the Frequency Scanner in Single mode, not Continuous mode. Since the link is
down during the scan, management to the remote site is lost, so that if the scan is run in
Continuous mode, it will not be possible to de-activate the Frequency Scanner.

1 Click Apply to save the scan configuration.

2 Click Scan:
o The Scan Progress field displays the scan’s progress, in percentage of the defined spectrum that
has been scanned. In Continuous Mode, the Scan Progress field rises to 100 when the defined
spectrum has been scanned, returns to 0, and continues to advance from 0 to 100 for each scan
until you click Stop. In Single Mode, the Scan Progress field rises to 100 and stays at 100 once the
defined spectrum has been scanned.
o The Frequency Scanner Band field displays the frequency channel configured in the current
MRMC script. See Error! Reference source not found..
o The Last Scan Date and Time field displays the date and time of the most recently completed
frequency scan.
Scan results are displayed are displayed in table format, and can also be displayed in graph format. In Single Mode,
results are displayed after the scan is completed. In Continuous Mode, results are displayed after the scan has
completed one cycle over the defined spectrum, and are automatically updated as the scan proceeds.
Figure 34 shows the results of a Single Mode scan on an PTP 820E in table format. For each RX channel in the
defined frequency range, the table displays the following columns:
o Frequency (MHz) – The starting frequency in the scanned channel.
o RSL Sample Value (dBm) – In Single Mode, the RSL value measured for the scanned channel. In
Continuous Mode, the latest RSL value measured for the scanned channel.
o Minimum RSL (dBm) – In Continuous Mode, the lowest RSL value measured for the scanned
channel. In Single Mode, the same as the RSL Sample Value.
o Maximum RSL (dBm) – In Continuous Mode, the highest RSL value measured for the scanned
channel. In Single Mode, the same as the RSL Sample Value.
You can also display the scan results in graph format by clicking Graph. The Graph page presents the scan results in
graphical format, with the frequency on the horizontal axis and the RSL on the vertical axis.
The Graph page has the following tabs:
o RSL Sample Value (dBm) – In Single Mode, the RSL value measured for the scanned channel. In
Continuous Mode, the latest RSL value measured for the scanned channel.

Phn 3963 013v000

Page 140
Chapter 2: Getting Started Running the Frequency Scanner (PTP 820E)

o Minimum RSL (dBm) – In Continuous Mode, the lowest RSL value measured for the scanned
channel. In Single Mode, the same as the RSL Sample Value.
o Maximum RSL (dBm) – In Continuous Mode, the highest RSL value measured for the scanned
channel. In Single Mode, the same as the RSL Sample Value.

Figure 42 Frequency Scanner Results – Graph Format (PTP 820E – Single Mode)

Phn 3963 013v000

Page 141
Chapter 2: Getting Started Configuring the Radio Parameters

Configuring the Radio Parameters

In order to establish a radio link, you must:

o Verify that the radio is muted (the TX Mute Status should be On).
o Configure the radio frequencies.

Note:
Even if you are using the default frequencies, it is mandatory to actually
configure the frequencies.

o Configure the TX level.

o Click Apply to apply these configurations.

Note:
If you are using the default values and did not change any other parameters
on the Radio Parameters page, the Apply button will be grayed out. To
activate the Apply button, change any parameter on the page, then change it
back to the desired value.

o Set TX Mute to Unmute.

o Click Apply to apply the unmute.
o Verify that the radio is unmuted (the TX Mute Status should be Off).
You can do these tasks, perform other radio configuration tasks, and display the radio parameters in the Radio
Parameters page.
To configure the radio parameters:
1 Select Radio > Radio Parameters. The Radio Parameters page opens.

Note:
This page is only available in Advanced mode. However, the basic radio
parameters can also be configured during link configuration with a Quick
Configuration wizard. See Configuring a Link Using the Quick Configuration
Wizard. You can also configure the basic radio parameters in Basic mode by
selecting Interfaces > Interface Manager, selecting a radio interface, and
clicking Radio Parameters.

o For multi-carrier units, the Radio Parameters page initially displays a table.
o For single-carrier units, a page appears, similar to Error! Reference source not found.36.

Phn 3963 013v000

Page 142
 Chapter 2: Getting Started Configuring the Radio Parameters

Figure 43 Radio Parameters Page – PTP 820C/PTP 820C-HP

For
multi-carrier units, select the carrier in the Radio table and click Edit. A separate Radio Parameters page opens.

Phn 3963 013v000

Page 143
 Chapter 2: Getting Started Configuring the Radio Parameters

The page is essentially identical to the PTP 820S and PTP 820E page, except for the addition of a Radio location
parameter.

Figure 44 Radio Parameters Page Per Carrier – PTP 820C/PTP 820C-HP

2. Set the radio frequency in the Frequency control (Local) section:

a. In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
b. In the RX Frequency (MHz) field, set the received radio frequency in MHz.

Phn 3963 013v000

Page 144
Chapter 2: Getting Started Configuring the Radio Parameters

c. Click Apply. The system automatically calculates and displays the frequency separation in the TX to RX
frequency separation (MHz) field, based on the configured TX and RX frequencies.
d. Optionally, select Set also remote unit to apply the frequency settings to the remote unit as well as
the local unit.

Note:
If the carrier belongs to a 4x4 MIMO group, an ASD group, an AFR group, or
an XPIC group, you must disable the group before changing the TX or RX
frequency.

For PTP 820E , a frequency scanner is available to scan the frequency range
covered by the currently configured MRMC script and determine the current
interference level for each channel. This enables you to select the best
channel in accordance with current interference levels.

3. Set the other radio parameters in the Configuration parameters section:

a. In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values depends
on the frequency and RFU type.
b. The RSL Connector Source field is used when you are measuring the RSL at the unit’s RSL port,
and determines which receiver’s RSL is measured at the RSL port:
▪ Main – The default value for PTP 820E. Keep this setting when measuring RSL on an PTP
820E. This option does not appear for other all-outdoor PTP 820 products.
▪ PHY1 – The default value for PTP 820C, PTP 820C-HP, and PTP 820S. Select PHY1 to
measure the RSL of an PTP 820S and Radio Port 1 of an PTP 820C or PTP 820C-HP.
▪ PHY2 – Select PHY2 to measure the RSL of Radio Port 2 of an PTP 820C or PTP 820C-HP.

Note:
The voltage at the RSL port is 1.XX where XX is the RSL level. For example:
1.59V means an RSL of -59 dBm. Note that the voltage measured at the RSL
port is not accurate and should be used only as an aid).
Note that the voltage measured at the RSL port is not accurate and should be
used only as an aid)
.
c. To mute the TX output of the radio carrier, select Unmute in the TX Mute field. To unmute the TX
output of the radio carrier, select Off. To configure a timed mute, select Mute with Timer.
If you select Mute with Timer, an additional field appears: Mute timeout (minutes). This field
defines a timer for the mute, in minutes (1-1440). When the timer expires, the mute
automatically ends. This provides a fail-safe mechanism for maintenance operations that
eliminates the possibility of accidently leaving the radio muted after the maintenance has been
completed. By default, the timer is 10 minutes.

Phn 3963 013v000

Page 145
Chapter 2: Getting Started Configuring the Radio Parameters

Note:
In contrast to an ordinary mute, a timed mute is not persistent. This means that if the
unit is reset, the radio is not muted when the unit comes back online, even if the timer
had not expired. Also, in unit and radio protection configurations, a timed mute is not
copied to the mate unit or radio, and no mismatch alarm is raised if a timed mute is
configured on only one radio in the protection pair.

e. In the Link ID field, enter a unique link identifier from 1 to 65535. The Link ID identifies the link, in
order to distinguish it from other links. If the Link ID is not the same at both sides of the link, a Link ID
Mismatch alarm is raised. If Link ID Mismatch Security is enabled, traffic is also blocked on the link.
See Enabling Link ID Mismatch Security.
f. In the RSL degradation alarm admin field, select Enable if you want the unit to generate an alarm in
the event that the RSL falls beneath the threshold defined in the RSL degradation threshold field. The
range of values is -99 to 0. By default, the alarm is disabled, with a default degradation threshold
of -68 dBm. The RSL degradation alarm is alarm ID 1610, Radio Receive Signal Level is below the
configured threshold.
g. The alarm is cleared when the RSL goes above the configured threshold. The alarm is masked if the
radio interface is disabled, the radio does not exist, or a communication-failure alarm (Alarm ID
#1703) is raised.
h. In the Adaptive TX power admin field, select Enable if you wish the PTP 820 to automatically adjust
power levels on the fly in order to optimize the available capacity at every modulation point. See
Error! Reference source not found..

Note:
The RSL Connector Source field is used in dual-carrier systems to switch between one
carrier and the other when measuring RSL at the BNC connector.

Enabling Link ID Mismatch Security

Note:
This feature is only relevant for PTP 820C, PTP 820C-HP, and PTP 820S units.

You can configure the unit to block all Ethernet traffic over the radio link in the event of a Link ID mismatch by
enabling Link ID Mismatch Security. When Link ID Mismatch Security is enabled and a Link ID mismatch occurs:
• All Ethernet traffic over the link is blocked.

Phn 3963 013v000

Page 146
Chapter 2: Getting Started Configuring the Radio Parameters

• The operational status of the radio is set to Down.

• Automatic State Propagation is triggered.
• You cannot change the Link ID of the remote radio, but the local-remote channel remains open for other
remote configurations.
• In-band management is lost. Once the mismatch is cleared, in-band management is automatically restored.
• The relevant interfaces are treated as being Down for purposes of MSTP and G.8032
Link ID Mismatch Security must be enabled and disabled via CLI.
To enable Link ID Mismatch Security, enter the following command in root view:
root> platform security link-id mismatch security set admin enable
To disable Link ID Mismatch Security, enter the following command in root view:
root> platform security link-id mismatch security set admin disable
To display the current Link ID Mismatch Security setting, enter the following command in root view:
root> platform security link-id mismatch security show admin
By default, Link ID Mismatch Security is disabled.

Phn 3963 013v000

Page 147
Chapter 2: Getting Started Enabling ACM with Adaptive Transmit Power

Enabling ACM with Adaptive Transmit Power

When planning ACM-based radio links, the radio planner attempts to apply the lowest transmit power that will
perform satisfactorily at the highest level of modulation. During fade conditions requiring a modulation drop, most
radio systems cannot increase transmit power to compensate for the signal degradation, resulting in a deeper
reduction in capacity. The PTP 820 is capable of adjusting power on the fly, and optimizing the available capacity at
every modulation point.
To enable ACM with adaptive transmit power:
1. Select Radio > Radio Parameters. The Radio Parameters page opens.
o For multi-carrier units, the Radio Parameters page initially displays a table as shown
in Figure 26.
o For single-carrier units and units, a page appears, similar to Figure 27 (which shows a
PTP 820C page).
2. For multi-carrier units, select the carrier in the Radio table (see Figure 26) and click Edit. A separate Radio
Parameters page opens. The page is essentially identical to the Single-carrier page, except for the addition of a
Radio location parameter.

Phn 3963 013v000

Page 148
Chapter 2: Getting Started Enabling ACM with Adaptive Transmit Power

Figure 45 Radio Parameters Page Per Carrier – PTP 820C

3. In the Adaptive TX power admin field, select Enable. The AdaptiveTX power operational status field should
now indicate Up to indicate that the feature is fully functional.

Note
Adaptive TX Power only operates when the MRMC script is configured to Adaptive mode. If the script
is configured to Fixed mode (or Adaptive mode with the Minimum and Maximum Profile set to the
same value), you can set Adaptive TX Power to Enable, but the Adaptive TX power operational
status field will indicate Down.

Phn 3963 013v000

Page 149
Chapter 2: Getting Started Operating in FIPS Mode

Operating in FIPS Mode

Note
This feature is only relevant for PTP 820C, PTP 820C-HP, and PTP 820S units.
FIPS 140-2 compliance is only available with the PTP 820 Assured platform.
The PTP 820 Assured Platform is supported by System release 8.3 and 10.9.6. It is not supported by
System release 11.1.

PTP 820C, PTP 820C-HP, and PTP 820S can be configured to be FIPS 140-2-compliant in specific hardware and
software configurations, as described in this section.

Requirements for FIPS Compliance

For a full list of FIPS requirements, refer to the PTP 820 FIPS 140-2 Security Policy, available upon request. It is the
responsibility of the customer to ensure that these requirements are met.
For PTP 820C, PTP 820C-HP or PTP 820S node to be FIPS-compliant, the unit must be FIPS-compliant hardware.

Note
To display the part numbers of the hardware components of your PTP 820 unit, see Displaying Unit
Inventory.

Unit redundancy configurations can be configured to be FIPS 140-2-compliant. This requires encryption of the
protection link between the two units. See Encrypting the External Protection Link.
A Special labels must be affixed to a FIPS-compliant PTP 820C or PTP 820S unit. These labels are tamper-evident
and must be applied in such a way that it is not possible to remove the diplexer unit from the radio unit without
also removing a label and leaving evidence that the label was tampered with. This label must be replaced if the SM
card is replaced. Replacement labels can be ordered from Cambium Networks, part number BS-0341-2. Tamper-
evident labels should be inspected for integrity at least once every six months. For further details, refer to the PTP
820C Installation Guide or the PTP 820S Installation Guide.

Enabling FIPS Mode

To set the unit to operate in FIPS mode:
1 Select Platform > Security > General > Configuration. The Security General Configuration page opens.

Phn 3963 013v000

Page 150
Chapter 2: Getting Started Operating in FIPS Mode

Figure 46 Security General Configuration Page

The Import/Export security settings field determines whether security configurations are included in configuration
backup files. To enhance unit security, it is recommended to select Enable in this field, so that security
configurations will not be included in backup files. When you are finished, click Apply.
In the FIPS admin configuration field, select Enable.
2 Click Apply.

Note
Changing the FIPS configuration causes a unit reset.

After enabling FIPS:

• The MD5 option for SNMPv3 is blocked.
• After any system reset, the length of time before users can log back into the system is longer than usual due to
FIPS-related self-testing.
For a full list of FIPS requirements, including software configuration requirements, refer to the PTP 820 FIPS 140-2
Security Policy, available upon request.

Encrypting the External Protection Link

For unit redundancy configurations, the external protection link must be encrypted using IPsec. This encrypts all IP
packets that pass between the management ports of the two PTP 820 units.
IPsec uses a 32-character pre-shared key. The pre-shared key is a 32-byte symmetric encryption key. The same pre-
shared key must be configured on both ends of the encrypted link.
IPsec encryption is automatically enabled when FIPS mode is enabled. However, it is enabled with a default value:
protectionpresharedkey0123456789.
If this default value is not changed, the following alarm is triggered:

Phn 3963 013v000

Page 151
Chapter 2: Getting Started Operating in FIPS Mode

• 5113 – Protection Pre-Shared-Key has the default value

Initial Configuration of FIPS-Compliant Unit Redundancy Configuration

To set up a unit redundancy configuration that is FIPS 140-2-compliant, you must follow these steps:
• Configure and enable unit redundancy on both units. See Configuring Unit Protection with HSB Radio
Protection (External Protection).
• Enable FIPS on both PTP 820 units. See Enabling FIPS Mode.
When you enable FIPS mode, IPsec encryption will automatically be enabled on the protection link, using the
default protection pre-shared key. Alarm 5113 will be raised.
• Verify that there is no Configuration Mismatch alarm by checking in the Faults > Current Alarms page. If a
Configuration Mismatch alarm is present, you must clear the alarm before configuring a new pre-shared key.
Otherwise, the key will not be copied to the Standby unit.

Note
You can use the following CLI command to display a list of mismatched parameters:
root> platform management protection show mismatch details

• Configure a new pre-shared key on the active unit. To configure a protection key:
o Verify that the web interface protocol for accessing the unit is configured to HTTPS. See
Configuring X.509 CSR Certificates and HTTPS.
o Select Platform > Unit Redundancy. The Unit Redundancy page opens.

Figure 47: Unit Redundancy Page

o In the Protection Pre-Shared Key field, enter a 32-character key. The key must be exactly 32
characters.
o Click Apply. The key is automatically copied to the standby unit.

Phn 3963 013v000

Page 152
Chapter 2: Getting Started Operating in FIPS Mode

Note
Communication with the standby unit may be lost for a few seconds while the key is being copied.

To clear the user-defined protection pre-shared key and restore it to its default value, enter the following CLI
command in root view:
root> platform management protection clear pre-shared-key

Replacing a Unit in a FIPS-Compliant Unit Redundancy Configuration

If it becomes necessary to replace a unit in a FIPS 140-2-compliant unit redundancy configuration, you must pre-
configure the replacement unit as follows:
• Enable FIPS on the replacement unit. See Enabling FIPS Mode.
• Configure the protection pre-shared key on the replacement unit. See Initial Configuration of FIPS-Compliant
Unit Redundancy Configuration, Step 3.
• Configure and enable unit redundancy on the replacement unit. See Configuring Unit Protection with HSB
Radio Protection (External Protection).
• Perform copy-to-mate. See Configuring HSB Radio Protection.

Phn 3963 013v000

Page 153
Chapter 2: Getting Started Configuring Grouping (Optional)

Configuring Grouping (Optional)

At this point in the configuration process, you should configure any interface groups that need to be set up
according to your network plan. For details on available grouping and other configuration options, as well as
configuration instructions, see System Configurations.

Phn 3963 013v000

Page 154
Chapter 2: Getting Started Creating Service(s) for Traffic

Creating Service(s) for Traffic

In order to pass traffic through the PTP 820, you must configure Ethernet traffic services. For configuration
instructions, see Configuring Ethernet Service(s).

Phn 3963 013v000

Page 155
Chapter 3: Configuration Guide Creating Service(s) for Traffic

Chapter 3: Configuration Guide

This section includes:
• System Configurations
• Configuring a Link Using the Quick Configuration Wizard
• Configuring Multi-Carrier ABC
• Configuring Link Aggregation (LAG)Configuring Link Aggregation (LAG) and LACP
• Configuring XPIC
• Configuring Unit Protection with HSB Radio
• Configuring MIMO and Space Diversity
• Operating a PTP 820C or PTP 820C-HP in Single Radio Carrier Mode

Note
Multi-Carrier ABC, XPIC, MIMO, and Space Diversity are only supported with PTP 820C. HSB radio
protection is only supported with PTP 820C and PTP 820S

Phn 3963 013v000

Page 156
Chapter 3: Configuration Guide System Configurations

System Configurations

This section lists the basic system configurations and the PTP 820 product types that support them, as well as links to
configuration instructions.

Table 9 System Configurations

Configuration Supported Link to Configuration Instructions

Products

Multi-Carrier ABC (Multi- PTP 820C/C- Configuring Multi-Carrier ABC

Radio) HP

Multiband (Enhanced PTP 820E Configuring Multiband (Enhanced Multi-Carrier ABC)

Multi-Carrier ABC) PTP 820C
PTP 820C-HP
PTP 820S

Link Aggregation (LAG) PTP 820C/S Configuring Link Aggregation (LAG) and LACP

1+1 XPIC PTP 820C/C- Configuring XPIC

HP

HSB Radio Protection PTP 820C/S/C- Configuring Unit Protection with HSB Radio
HP

1+1 HSB with Space PTP 820C Configuring 1+1 HSB with Space Diversity
Diversity

MIMO and Space Diversity PTP 820C Configuring MIMO and Space Diversity

ASD 2+0 (XPIC) PTP 820C Configuring Advanced Space Diversity (ASD)
PTP 820C-HP

AFR 1+0 PTP 820C (hub Configuring Advanced Frequency Reuse (AFR)
site or tail
site)
PTP 820S (tail
site only)

PTP 820C/PTP 820C-HP in PTP 820C/C- Operating a PTP 820C in Single Radio Carrier Mode
Single Radio Carrier Mode HP

Phn 3963 013v000

Page 157
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Configuring an PTP 820 Unit Using Basic Mode

This section guides you through the Basic mode Web EMS menu tree. The purpose of this section is to enable Basic
mode users to configure an PTP 820 unit, including unit and link parameters, quickly and efficiently. Cross-references
are provided to other sections of the User Guide for more detailed explanations and instructions for PTP 820 features
and configurations.
This section is divided and ordered according to the Basic mode menu tree:
• Device View – Enables you to reset the unit and restore the unit’s factory
• default configuration settings.
• Unit Summary – Displays unit parameters, current alarms, and unit inventory information on a single
page for quick viewing.
• Quick Configuration – Enables you to configure links quickly and simply using a collection of Quick
Configuration wizards. Also enables you to configure the entire unit by applying a pre-configured
CeraPlan file.
• Platform – Includes pages for configuring the unit, including user access settings, activation keys,
software upgrades, unit time, and other unit settings.
• Interfaces – Includes an expanded version of the Interface Manager page. From this page, you can
enable and disable interfaces, configure radio parameters and MRMC scripts, display radio status,
configure the physical parameters of an Ethernet interface, and configure basic ingress classification
parameters of an interface.
• Services – Enables you to create Ethernet services.
• Faults – Includes options to display current alarms and the event log.
• Performance Monitoring – Enables you to display radio and Ethernet PMs.
• Diagnostic & Maintenance – Enables you to perform diagnostics, troubleshooting, and configuration
management.

Phn 3963 013v000

Page 158
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Device View
Device View is similar to the Chassis Configuration page in Advanced mode. From Device view, you can perform the
following actions:
• Reset the unit. See Performing a Hard (Cold) Reset.
• Set the unit to its default factory configuration settings. See Setting the Unit to the Factory Default
Configuration.

Figure 48: Basic Mode – Device View Page

Unit Summary
The Unit Summary page gathers the unit parameters, current alarms, and unit inventory information on a single page
for quick viewing. For details, see The Unit Summary Page.

Figure 49: Basic Mode – Unit Summary Page

Phn 3963 013v000

Page 159
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Quick Configuration
The Quick Configuration menu includes two options for quick configuration of an PTP 820 unit:
• From System Release – Enables you apply a pre-defined configuration file that was created using System
Release. See Applying a Pre-Defined Configuration File.
• PIPE Wizards – Opens sub-menus from which you can access a collection of Quick Configuration wizards, that
guide you through the process of configuring most types of PTP 820 links, from simple 1+0 links to more
complex Multi-Carrier ABC and Multiband links. For a full description of these wizards and step-by-step
instructions for using each wizard, see Configuring a Link Using the Quick Configuration Wizard.

Platform
From the Platform menu, you can access pages that enable you to configure the unit, including:
• Unit Parameters Page – Display and configure unit information, such as unit name and description, language,
measurement format, and unit temperature and voltage input.
• Software Versions & Upgrade Page – Display the current System release version and perform software
upgrades.
• Time Services Page – Configure the unit’s time and date settings.
• IP Configuration Page – Configure the unit’s IP address and enable or disable in-band management.
• Activation Key Page – Configure the unit’s activation key and display current activation key coverage.
• Security Pages – Configure unit acess settings, including protocols for accessing the unit, login parameters,
users, SNMP settings, and password settings.

Phn 3963 013v000

Page 160
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Unit Parameters Page

In the Unit Parameters page, you can configure information such as the unit name and description, language, and
measurement format. You can also display important information about the unit, such as the current unit
temperature and voltage input. For more information, see Configuring Unit Parameters.

Figure 50: Basic Mode – Unit Parameters Page

Phn 3963 013v000

Page 161
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Software Versions & Upgrade Page

In the Software Versions & Upgrade page, you can display the current System Release version and download and
install new versions using HTTP or FTP.
For a full explanation of software management, see Upgrading the Software.

Figure 51: Basic Mode – Software Versions & Upgrade Page

Phn 3963 013v000

Page 162
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Time Services Page

In the Time Services page, you can configure the unit’s time and date settings. See
Setting the Time and Date (Optional).

Figure 52: Basic Mode – Software Versions & Upgrade Page

IP Configuration Page
In the IP Configuration page, you can configure the unit’s IP address and related parameters. You can also enable or
disable in-band management.
For an explanation of IP configuration, see Changing the Management IP Address. For an explanation of in-band
management, see Configuring In-Band Management.

Figure 53: Basic Mode – IP Configuration Page

Page 163 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Activation Key Page

In the Activation Key page, you can configure the unit’s activation key. You can also display the status of activation
key coverage for features and capacities in the unit.
To display the status of activation key coverage, select ShowActivation Key Overview. The status details appear at the
bottom of the page, as shown in Figure 56.For an explanation of activation key management, see Configuring the
Activation Key.

Figure 54: Basic Mode – Activation Key Page

Security Pages
From the Security menu, you can access pages that enable you to configure the unit, including:
• General Parameters Page – Enable and disable import and export of security settings, configure the session
timeout, and configure a login banner.
• Protocols Page – Configure the HTTP type, Telnet blocking, and SNMP parameters.
• Access Control Page – Configure users and login settings.

General Parameters Page

In the Security General Parameters page, you can enable and disable import and export of security settings, configure
the session timeout, and configure a login banner. For more details about these settings, see Quick Security
Configuration – General Parameters Page.

Page 164 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Figure 55: Basic Mode – Security – General Parameters Page

Protocols Page
In the Protocols page, you can configure the HTTP type, Telnet blocking, and SNMP parameters. For more details
about these settings, see Quick Security Configuration – Protocols Page.

Figure 56: Basic Mode – Security – Protocols Page

Access Control Page

In the Security Access Control page, you can configure users and login parameters.For more information about
password and user settings, see Configuring Users.

Page 165 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Figure 57: Basic Mode – Security – Security Access Control Page

To configure user profiles, click Access Control User Profiles. The Access Control User Profiles page opens. For details,
see Configuring User Profiles.

Figure 58: Basic Mode – Security – Access Control User Profiles Page

Interfaces
From the Interfaces menu, you can select Interface Manager to display the Interface Manager page.

Figure 59: Basic Mode – Interface Manager Page

From the Interface Manager page,you can perform the following interface configurations:
Enable and disable interfaces – select the interface and click Interface Admin. See Enabling the Interfaces (Interface
Manager).

Figure 60: Basic Mode – Interface Manager Page – Interface Admin

Page 166 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Configure the radio parameters of a radio interace – select the interface and click Radio Parameters. See Configuring
the Radio Parameters.

Figure 61: Basic Mode – Interface Manager Page – Radio Parameters

Configure the MRMC script of a radio interace – select the interface and click
Radio MRMC. See Configuring the Radio (MRMC) Script(s).

Figure 62: Basic Mode – Interface Manager Page – Radio MRMC

Page 167 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Display status parameters of a radio interace – select the interface and click
Radio Status. See Viewing the Radio Status and Settings.

Figure 63: Basic Mode – Interface Manager Page – Radio Status

Configure the physical parameters of an Ethernet interace – select the interface and click Physical Interface. See
Configuring Ethernet Interfaces.

Figure 64: Basic Mode – Interface Manager Page – Physical Interface

Page 168 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Configure the basic ingress classification parameters of an interace – select the interface and click Basic QoS. See
Configuring Ingress Path Classification on a Logical Interface.

Figure 65: Basic Mode – Interface Manager Page – Basic QoS

Services
The Services menu enables you to create Ethernet services.
To configure Ethernet services, click Ethernet Services. For information about configuring Ethernet services, see
Configuring Ethernet Service(s).

Figure 66: Basic Mode – Ethernet Services

Page 169 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Faults
The Faults menu includes options to display current alarms and the event log.
To display current alarms, click Current Alarms. For information about alarms, see
Viewing Current Alarms.

Figure 67: Basic Mode – Current Alarms

To display the event log, click Event Log. For information about the event log, see
Viewing and Saving the Event Log.

Figure 68: Basic Mode – Event Log

Performance Monitoring
From the Performance Monitoring menu, you can access pages that display important information about link
performance, including:
• RMON
• Signal Level
• MSE
• MRMC
• Capacity/Throughput
• Utilization
• Frame Error Rate

Page 170 of 1073

Ceragon Proprietary and

Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

RMON
To display RMON statistics, click RMON. For further information, see Viewing Ethernet PMs and Statistics.

Figure 69: Basic Mode – RMON Page

Signal Level
To display Signal Level PMs and define Signal Level PM thresholds, click Signal Level. For further information, see
Displaying Signal Level PMs and Configuring Signal Level PM Thresholds.

Figure 70: Basic Mode – Signal Level Page

MSE
To display MSE PMs and define MSE PM thresholds, click MSE. For further information, see Displaying MSE PMs and
Configuring MSE PM Thresholds.

Figure 71: Basic Mode – MSE Page

Phn 3963 013v000

Page 171
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

MRMC
You can display the minimum and maximum ACM profile and the minimum and maximum bitrate (throughput) per
15-minute or daily intervals. You can also define two ACM profile thresholds for each radio carrier, and display the
number of seconds per interval that the radio’s ACM profile was below each of these thresholds.
To display ACM profile PMs and define ACM profile thresholds, click MRMC. For further information, see Displaying
MRMC PMs and Configuring ACM Profile Thresholds.

Figure 72: Basic Mode – MRMC Page

Capacity/Throughput
To display capacity and throughput PMs and define capacity and throughput thresholds, click Capacity/Throughput.
For further information, see Displaying Capacity and Throughput PMs.

Figure 73: Basic Mode – Capacity/Throughput Page

Phn 3963 013v000

Page 172
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Utilization
To display utilization PMs and define utilization thresholds, click Utilization. For further information, see Displaying
Frame Error Rate PMs.

Figure 74: Basic Mode – Utilization Page

Frame Error Rate

To display Frame Error Rate PMs, click Frame Error Rate. For further information, see Displaying Frame Error Rate
PMs.

Figure 75: Basic Mode – Frame Error Rate Page

Phn 3963 013v000

Page 173
Diagnostic & Maintenance
From the Diagnostic & Maintenance menu, you can access pages that enable you to perform diagnostics,
troubleshooting, and configuration management, including:
• Radio Loopback – Perform radio loopback
• Unit Info – Generate and export a user info file, used primarily for troubleshooting.
• Configuration Management – Import and export unit configuration files, used to backup and restore
system configurations.

Radio Loopback
To perform radio loopback, the radio must be set to its maximum TX power. For reliable loopback results, the
loopback should performed with the modulation at 1024 QAM or lower.To perform radio loopback, click
Radio Loopback. For further information, see
Performing Radio Loopback.

Figure 76: Basic Mode – Radio Loopbacks Page

Unit InfoYou can generate a Unit Information file, which includes technical data about the unit. This file can be
uploaded and forwarded to customer support, at their request, to help in analyzing issues that may occur.
You can upload the Unit Information file using HTTP, HTTPS, FTP, or SFTP.
For troubleshooting, it is important that an updated configuration file
be included in User Info files that are sent to customer support. To ensure that an up-to-date configuration
file is included, it is recommended to back up the unit’s configuration before generating the Unit Info file.
To generate a Unit Information file, click Create & Export Unit Info. For further information, see Uploading Unit
Info.

Figure 77: Basic Mode – Unit Info Page

Phn 3963 013v000

Page 174
Chapter 3: Configuration Guide Configuring an PTP 820 Unit Using Basic Mode

Configuration Management
You can import and export PTP 820 configuration files. This enables you to copy the system configuration to
multiple PTP 820 units. You can also backup and save configuration files. Importing and exporting configuration
files can be done using HTTP, HTTPS, FTP, or SFTP.
Basic mode combines the actions required to perform configuration management into a single Web EMS page. To
display this page, click Configuration Management. For further information, see Backing Up and Restoring
Configurations.

Figure 78: Basic Mode – Configuration Management Page

Phn 3963 013v000

Page 175
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Configuring a Link Using the Quick Configuration

Wizard
The Web EMS provides wizards to configure radio links. The wizards guide you through configuration of the basic
radio parameters and services necessary to establish a working pipe link. The following link types can be
configured with the Quick Configuration wizard:
• 1+0 – Configures a 1+0 radio link consisting of a user-selected Ethernet and radio interface connected. This
link passes traffic between the radio and Ethernet interfaces via a point-to-point pipe service. See Configuring
a 1+0 Link Using the Quick Configuration Wizard.
• 1+0 Repeater – Configures a 1+0 radio link that passes traffic between two user-selected radios via a point-to-
point pipe service. This type of link is used to configure a node that functions as a repeater, passing traffic
between two other nodes. See Configuring a 1+0 (Repeater) Link Using the Quick Configuration Wizard.
• 2 x (1+0) – Configures a 2 x (1+0) radio link, which is essentially a 2+0 link without Multi-Carrier ABC. You can
configure these 1+0 links as an XPIC link or as ordinary 1+0 non-XPIC links. Each link consists of a user-selected
Ethernet (or LAG) and radio interface. Each link passes traffic between the radio and Ethernet interfaces via a
point-to-point pipe service. See Configuring a 2 x (1+0) Link Using the Quick Configuration Wizard.
• 2+0 Multi-Carrier ABC – Configures a 2 + 0 Multi-Carrier ABC group consisting of an Ethernet interface or LAG
and the two radio interfaces. See Configuring a 2+0 Multi-Carrier ABC Link Using the Quick Configuration
Wizard. For a detailed explanation of Multi-Carrier ABC and its requirements, see Configuring Multi-Carrier
ABC.
You can also use this wizard to configure XPIC between the radios within the Multi-Carrier ABC group. For a
detailed explanation of XPIC and its requirements, see Configuring XPIC.

Note
1+0 Repeater links and Multi-Carrier ABC are only available for PTP 820C dual-carrier units.

• Multiband – Configures a link that bundles E-Band and microwave radios in a single group that is shared with
an Ethernet interface. A Multiband link uses an PTP 820E and an PTP 820C, PTP 820C-HP, PTP 820S, or third-
party microwave unit. The Multiband group is only configured on the PTP 820E unit. See Configuring a
Multiband (Enhanced Multi-Carrier ABC) Link Using the Quick Configuration Wizard.
Because the Quick Configuration wizard creates Pipe links, you cannot add an interface to a link using the Quick
Configuration wizard if any service points are attached to the interface prior to configuring the link. See Deleting a
Service Point.

Phn 3963 013v000

Page 176
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Configuring a 1+0 Link Using the Quick Configuration Wizard

To configure a 1+0 link using the Quick Configuration wizard:
1 Select Quick Configuration > PIPE > Single Carrier > 1+0. Page 1 of the 1+0 Quick Configuration wizard opens.
Figure 79 1+0 Quick Configuration Wizard – Page 1

2 In the Pipe Type field, select the Attached Interface type for the service that will connect the radio and
Ethernet interfaces. Options are:
o s-tag – All VLANs and untagged frames are classified into the service.
o dot1q - All C-VLANs and untagged frames are classified into the service.

Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s).

3 In the Ethernet Interface field, select an Ethernet interface or LAG for the link for the link.

Note
To create a LAG, click Create LAG. The Create LAG Group page opens. For instructions on creating
LAG groups, see Configuring Link Aggregation (LAG) and LACP.

4. Click Next. Page 2 of the 1+0 Quick Configuration wizard opens.

Figure 80 1+0 Quick Configuration Wizard – Page 2

Phn 3963 013v000

Page 177
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

5 In the Radio Interface field, select a radio interface for the link.
6 Click Next. Page 3 of the 1+0 Quick Configuration wizard opens.

Figure 81: 1+0 Quick Configuration Wizard – Page 3

7 In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
8 In the RX Frequency (MHz) field, set the received radio frequency in MHz.

Phn 3963 013v000

Page 178
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Note
If the carrier belongs to a 4x4 MIMO group, an ASD group, an AFR group, or an XPIC group, you must
disable the group before changing the TX or RX frequency.

For PTP 820E a frequency scanner is available to scan the frequency range covered by the currently
configured MRMC script and determine the current interference level for each channel. This enables
you to select the best channel in accordance with current interference levels. See Running the
Frequency Scanner (PTP 820E).

9 In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values depends on the
frequency and RFU type.
10 To mute the TX output of the RFU, select On in the TX mute field. To unmute the TX output of the RFU, select
Off.
21 Click Next. of the 1+0 Quick Configuration wizard opens.

Phn 3963 013v000

Page 179
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 82 1+0 Quick Configuration Wizard – Page 4

12 In the Script ID field, select the MRMC script you want to assign to the radio. For a full explanation of
choosing an MRMC script, see Configuring the Radio (MRMC) Script(s).
13 In the Operational Mode field, select the ACM mode: Fixed or Adaptive.
o Fixed ACM mode applies constant TX and RX rates. However, unlike regular scripts,
with a Fixed ACM script you can specify a maximum profile to inhibit inefficient
transmission levels.
o In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled radio system
automatically chooses which profile to use according to the channel fading
conditions.
14 Do one of the following:
o If you selected Fixed in the Operational Mode field, the next field is Profile. Select
the ACM profile for the radio in the Profile field.
o If you selected Adaptive in the Operational Mode field, the following two fields are
displayed:
- Maximum Profile: Enter the maximum profile for the script. See Configuring the Radio (MRMC)
Script(s).
- Minimum Profile: Enter the minimum profile for the script. See Configuring the Radio (MRMC)
Script(s).
15 Click Next. Page 5 of the 1+0 Quick Configuration wizard opens.

Phn 3963 013v000

Page 180
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 83 1+0 Quick Configuration Wizard – Page 4

16 In the In Band Management field, select Yes to configure in-band management, or No if you do not need in-
band management. If you select Yes, the Management VLAN field appears.
17 If you selected Yes in the In Band Management field, select the management VLAN in the Management
VLAN field.

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and
you want to configure IP Forwarding later, you will first have to change Untagged to a specific
VLAN. See Mate Management Access (IP Forwarding) (CLI).

18 If you want to use the Ethernet interface as well as the radio interface for in-band management, select In
Band includes Ethernet interface.
19 Click Finish. Page 5 of the 1+0 Quick Configuration wizard opens. This page displays the parameters you have
selected for the link.

Phn 3963 013v000

Page 181
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 84 1+0 Quick Configuration Wizard – Page 5 (Summary Page)

3 To complete configuration of the link, click Submit. If you want to go back and change any of the parameters,
click Back. After you click Submit, the unit is reset.

Configuring a 1+0 (Repeater) Link Using the Quick

Configuration Wizard
To configure a 1+0 repeater (radio-to-radio) link using the Quick Configuration wizard:
1 Select Quick Configuration > PIPE > Single Carrier > 1+0 (Repeater). Page 1 of the 1+0 Repeater Quick
Configuration wizard opens.

Figure 85 1+0 Repeater Quick Configuration Wizard – Page 1

2 In the Radio #1 Interface field, select the first radio interface for the link.
3 Click Next. Page 2 of the 1+0 Repeater Quick Configuration wizard opens.

Figure 86 1+0 Repeater Quick Configuration Wizard – Page 2

Phn 3963 013v000

Page 182
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

4 In the Radio #2 Interface field, select the second radio interface for the link.
5 In the Pipe Type field, select the Attached Interface type for the service that will connect the radios. Options
are:
o s-tag – All S-VLANs and untagged frames are classified into the service
o dot1q - – All C-VLANs and untagged frames are classified into the service.

Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s).

6 Click Next. Page 3 of the 1+0 Repeater Quick Configuration wizard opens.

Phn 3963 013v000

Page 183
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 87 1+0 Repeater Quick Configuration Wizard – Page 3

7 For each interface, configure the following parameters:

I. In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
II. In the RX Frequency (MHz) field, set the received radio frequency in MHz.

Note
For PTP 820E a frequency scanner is available to scan the frequency range covered by the currently
configured MRMC script and determine the current interference level for each channel. This enables
you to select the best channel in accordance with current interference levels. See Running the
Frequency Scanner (PTP 820E).

III. In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values
depends on the frequency and RFU type.
IV. To mute the TX output of the radio, select Mute in the TX mute field. To unmute the TX
output of the radio, select Unmute.
8 Click Next. Page 4 of the 1+0 Repeater Quick Configuration wizard opens.

Figure 88 1+0 Repeater Quick Configuration Wizard – Page 4

Phn 3963 013v000

Page 184
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

9 For each interface, configure the following MRMC script parameters:

I. In the Script ID field, select the MRMC script you want to assign to the radio. For a full explanation of
choosing an MRMC script, see Configuring the Radio (MRMC) Script(s).
II. In the Operational Mode field, select the ACM mode for the first radio: Fixed or Adaptive.
o Fixed ACM mode applies constant TX and RX rates. However, unlike regular scripts,
with a Fixed ACM script you can specify a maximum profile to inhibit inefficient
transmission levels.
o In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled radio system
automatically chooses which profile to use according to the channel fading
conditions.
III. Do one of the following:
o If you selected Fixed in the Operational Mode field, the next field is Profile. Select
the ACM profile for the radio in the Profile field.
o If you selected Adaptive in the Operational Mode field, the following two fields are
displayed:
- Maximum Profile: Enter the maximum profile for the script. See Configuring the Radio (MRMC)
Script(s).
- Minimum Profile: Enter the minimum profile for the script. See Configuring the Radio (MRMC)
Script(s).
10 Click Next. Page 5 of the 1+0 Repeater Quick Configuration wizard opens.

Figure 89 1+0 Repeater Quick Configuration Wizard – Page 5

Phn 3963 013v000

Page 185
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

11 In the In Band Management field, select Yes to configure in-band management, or No if you do not need in-
band management. If you select Yes, the Management VLAN field appears.
12 If you selected Yes in the In Band Management field, select the management VLAN in the Management
VLAN field. Management will be available through both radio interfaces.

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and you want
to configure IP Forwarding later, you will first have to change Untagged to a specific VLAN. See Mate
Management Access (IP Forwarding) (CLI).

13 Click Finish. Page 6 of the 1+0 Repeater Quick Configuration wizard opens. This page displays the parameters
you have selected for the link.

Phn 3963 013v000

Page 186
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 90 1+0 Repeater Quick Configuration Wizard – Page 6

14 To complete configuration of the link, click Submit. If you want to go back and change any of the parameters,
click Back. After you click Submit, the unit is reset.

Configuring a 2 x (1+0) Link Using the Quick Configuration

Wizard
To configure a 2 x (1+0) link using the Quick Configuration wizard:
1. Select Quick Configuration > PIPE > Single Carrier > 2 X (1 + 0). Page 1 of the 2 X (1 + 0) Quick Configuration
wizard opens.

Phn 3963 013v000

Page 187
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 91: 2 X (1 + 0) Quick Configuration Wizard – Page 1

2. In the First PIPE Type field, select the Attached Interface type for the service that will connect the first
Ethernet interface and the first radio interface. Options are:
◦ s-tag – All S-VLANs and untagged frames are classified into the service.
◦ dot1q – All C-VLANs and untagged frames are classified into the service.
Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s).

3. In the Ethernet Interface field, select the Ethernet interface or a LAG that will send and receive traffic to and
from the first radio interface.

Note
To create a LAG, click Create LAG. The Create LAG Group page opens. For instructions on
creating LAG groups, see Configuring Link Aggregation (LAG) and LACP.

Phn 3963 013v000

Page 188
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

4. Click Next. Page 2 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 92: 2X (1 + 0) Quick Configuration Wizard – Page 2

5. In the First Radio Interface field, select the radio interface for the first link.
6. Click Next. Page 3 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 93: 2X (1 + 0) Quick Configuration Wizard – Page 3

7. In the Second PIPE Type field, select the Attached Interface type for the service that will connect the second
Ethernet interface and the second radio interface. Options are:
◦ s-tag – All S-VLANs and untagged frames are classified into the service.
◦ dot1q – All C-VLANs and untagged frames are classified into the service.

Phn 3963 013v000

Page 189
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s)

8. In the Ethernet Interface field, select an Ethernet interface or a LAG that will send and receive traffic to and
from the second radio interface.

Note
To create a LAG, click Create LAG. The Create LAG Group page opens. For instructions on
creating LAG groups, see Configuring Link Aggregation (LAG) and LACP.

Phn 3963 013v000

Page 190
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

9. Click Next. Page 4 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 94: 2X (1 + 0) Quick Configuration Wizard – Page 4

10. In the Second Radio Interface field, select the radio interface for the second link.
11. Click Next. Page 5 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 95: 2X (1 + 0) Quick Configuration Wizard – Page 5

12. If you want to set up an XPIC configuration, select XPIC. For full instructions on configuring XPIC, including
antenna alignment instructions, see Configuring XPIC.

Phn 3963 013v000

Page 191
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

13. Click Next. Page 6 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 96: 2X (1 + 0) Quick Configuration Wizard – Page 5

Figure 97: 2X (1 + 0) Quick Configuration Wizard – Page 6 (Non-XPIC)

14. You can configure the basic radio parameters for each interface. If you selected XPIC in the Radio XPIC
Configuration page, configure the parameters for the group rather than the individual interfaces.
15. For each radio interface or XPIC group, configure the following radio parameters.
i In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
ii In the RX Frequency (MHz) field, set the received radio frequency in MHz.

Phn 3963 013v000

Page 192
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

iii In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values depends on the
frequency and RFU type.
iv To mute the TX output of the radio, select Mute in the TX mute field. To unmute the TX output of the radio,
select Unmute.
16. Click Next. Page 7 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 98: 2 X (1 + 0) Quick Configuration Wizard – Page 7 (XPIC)

Figure 99: 2 X (1 + 0) Quick Configuration Wizard – Page 7 (Non-XPIC)

17. You can configure the MRMC script parameters for each interface. For an XPIC group, configure the
parameters for the group rather than the individual interfaces.

Phn 3963 013v000

Page 193
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

18. For each interface or XPIC group, configure the following MRMC script parameters.
i In the Script ID field, select the MRMC script you want to assign to the radio or XPIC group. For a full
explanation of choosing an MRMC script, see Configuring the Radio (MRMC) Script(s).
ii In the Operational Mode field, select the ACM mode: Fixed or Adaptive.
◦ Fixed ACM mode applies constant TX and RX rates. However, unlike
regular scripts, with a Fixed ACM script you can specify a maximum profile
to inhibit inefficient transmission levels.
◦ In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled
radio system automatically chooses which profile to use according to the
channel fading conditions.
iii Do one of the following:
◦ If you selected Fixed in the Operational Mode field, the next field is Profile.
Select the ACM profile in the Profile field.
◦ If you selected Adaptive in the Operational Mode field, the following two
fields are displayed:
◦ Maximum profile – Enter the maximum profile for the script. See
Configuring the Radio (MRMC) Script(s).
◦ Minimum profile – Enter the minimum profile for the script. See
Configuring the Radio (MRMC) Script(s).
19. Click Next. Page 8 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 100: X (1 + 0) Quick Configuration Wizard – Page 8

20. In the First In Band Management field, select Yes to configure in-band management for the first 1+0 link, or
No if you do not need in-band management for this link. If you select Yes, the Management VLAN field
appears.
21. If you selected Yes in the In Band Management field, select the management VLAN in the Management VLAN
field.

Phn 3963 013v000

Page 194
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and
you want to configure IP Forwarding later, you will first have to change Untagged to a specific
VLAN. See Mate Management Access (IP Forwarding) (CLI)

22. If you want to use the Ethernet interface as well as the radio interface for in-band management, select In
Band includes Ethernet interface.
23. Click Next. Page 9 of the 2 X (1 + 0) Quick Configuration wizard opens.

Figure 101: 2 X (1 + 0) Quick Configuration Wizard – Page 9

24. In the Second In Band Management field, select Yes to configure in-band management for the second 1+0
link, or No if you do not need in-band management for this link. If you select Yes, the Management VLAN field
appears.
25. If you selected Yes in the In Band Management field, select the management VLAN in the Management VLAN
field.

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and
you want to configure IP Forwarding later, you will first have to change Untagged to a specific
VLAN. See Mate Management Access (IP Forwarding) (CLI)

26. If you want to use the Ethernet interface as well as the radio interface for in-band management, select In
Band includes Ethernet interface.
27. Click Finish. The Summary page opens. This page displays the parameters you have selected for the group.

Phn 3963 013v000

Page 195
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 102: 2 X (1 + 0) Quick Configuration Wizard –Summary Page (XPIC)

Figure 103: 2 X (1 + 0) Quick Configuration Wizard –Summary Page (No XPIC)

28. To complete configuration of the links, click Submit. If you want to go back and change any of the parameters,
click Back. After you click Submit, the unit is reset.

Phn 3963 013v000

Page 196
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Configuring a 2+0 Multi-Carrier ABC Link Using the Quick

Configuration Wizard
To configure a 2+0 Multi-Carrier ABC link using the Quick Configuration wizard:
1. Select Quick Configuration > Link Setup (PIPE) > Multi Carrier ABC > 2+0. Page 1 of the 2 + 0 Multi Carrier ABC
Quick Configuration wizard opens.

Phn 3963 013v000

Page 197
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 104 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Page 1

1 In the Ethernet Interface field, select an Ethernet interface or a LAG for the group.

Note
To create a LAG, click Create LAG. The Create LAG Group page opens. For instructions on creating
LAG groups, see Configuring Link Aggregation (LAG) and LACP.

2 In the Radio #1 Interface field, select the first radio interface for the group.

Note
The Number of Radio Interfaces field is read-only.

3 In the Pipe Type field, select the Attached Interface type for the service that will connect the radio and
Ethernet interfaces. Options are:
o s-tag – All S-VLANs and untagged frames are classified into the service.
o dot1q – All C-VLANs and untagged frames are classified into the service.

Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s).

4 Click Next. The Radio #2 Selection page opens.

Phn 3963 013v000

Page 198
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 105 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio #2 Selection Page

5 In the Radio #2 Interface field, select the second radio interface for the group.
6 Click Next. The Radio XPIC Configuration page opens. If you want to set up an XPIC configuration, select the
radio pair. For full instructions on configuring XPIC, including antenna alignment instructions, see
Configuring XPIC.

Figure 106 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio XPIC Configuration Page

7 Click Next. The Radio Parameters Configuration page opens. You can configure the basic radio parameters
for each interface. If you selected XPIC in the Radio XPIC Configuration page, you configure the parameters
for the group rather than the individual interfaces.

Phn 3963 013v000

Page 199
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 107 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio Parameters Configuration Page

Figure 108 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio Parameters Configuration Page (XPIC)

8 For each interface or XPIC group, configure the following radio parameters.
I. In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
II. In the RX Frequency (MHz) field, set the received radio frequency in MHz.

Note
For PTP 820E a frequency scanner is available to scan the frequency range covered by the
currently configured MRMC script and determine the current interference level for each
channel. This enables you to select the best channel in accordance with current interference
levels. See Running the Frequency Scanner (PTP 820E).

III. In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values depends on the
frequency and RFU type.

Phn 3963 013v000

Page 200
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

IV. To mute the TX output of the Radio, select Mute in the TX mute field. To unmute the TX output of the
Radio, select Unmute.
9 Click Next. The Radio MRMC Script Configuration page opens. You can configure the MRMC script
parameters for each interface. For an XPIC group, you configure the parameters for the group rather than
the individual interfaces.

Figure 109 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio MRMC Script Configuration Page

Figure 110 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Radio MRMC Script Configuration Page - XPIC

10 For each interface or XPIC group, configure the following MRMC script parameters:
I. In the Script ID field, select the MRMC script you want to assign to the radio or XPIC group. For a full
explanation of choosing an MRMC script, see Configuring the Radio (MRMC) Script(s).
II. In the Operational Mode field, select the ACM mode: Fixed or Adaptive.
o Fixed ACM mode applies constant TX and RX rates. However, unlike regular scripts, with a Fixed
ACM script you can specify a maximum profile to inhibit inefficient transmission levels.
o In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled radio system automatically
chooses which profile to use according to the channel fading conditions.
III. Do one of the following:
o If you selected Fixed in the Operational Mode field, the next field is Profile. Select the ACM profile
in the Profile field.

Phn 3963 013v000

Page 201
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

o If you selected Adaptive in the Operational Mode field, the following fields are displayed:
- Maximum Profile: Enter the maximum profile for the script. See Configuring the Radio
(MRMC) Script(s).
- Maximum Profile: Enter the maximum profile for the script. See Configuring the Radio
(MRMC) Script(s).
11 Click Next. The Management Configuration page opens.

Figure 111 2 + 0 Multi Carrier ABC Quick Configuration Wizard – Management Configuration Page

12 In the In Band Management field, select Yes to configure in-band management, or No if you do not need in-
band management. If you select Yes, the Management VLAN field appears.
13 If you selected Yes in the In Band Management field, select the management VLAN in the Management
VLAN field.

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and
you want to configure IP Forwarding later, you will first have to change Untagged to a specific
VLAN. See Mate Management Access (IP Forwarding) (CLI).

14 If you want to use the Ethernet interface as well as the radio interface for in-band management, select In
Band includes Ethernet interface.
15 Click Finish. The Summary page opens. This page displays the parameters you have selected for the group.

Phn 3963 013v000

Page 202
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 112 2 + 0 Multi Carrier ABC Quick Configuration Wizard –Summary Page

16 To complete configuration of the Multi-Carrier ABC group, click Submit. If you want to go back and change
any of the parameters, click Back. After you click Submit, the unit is reset.

Configuring a Multiband (Enhanced Multi-Carrier ABC) Link

Using the Quick Configuration Wizard
For important general information about Multiband links, see Multiband Overview.
To configure a Multiband node using the Quick Configuration wizard:
1 Connect the external switch to the Eth1 port on the PTP 820E.
2 Connect the Eth2 port on the PTP 820E to the unit paired with the PTP 820E. When the paired unit is an PTP
820C, PTP 820C-HP, or PTP 820S, use the Eth2 port on the PTP 820C, PTP 820C-HP, or PTP 820S.
3 Verify that no service points are configured on the Eth2 port of the PTP 820E. If there are service points on
Eth2, remove them. See Deleting a Service Point.
4 On the PTP 820E, select Quick Configuration > PIPE > Multi Carrier ABC > Multiband. Page 1 of the Multiband
Quick Configuration wizard opens.

Phn 3963 013v000

Page 203
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 113: Multiband Quick Configuration Wizard – Page 1

5 In the Pipe Type field, select the Attached Interface type for the service that will connect the radio and
Ethernet interfaces. Options are:
◦ s-tag – All S-VLANs and untagged frames are classified into the service.
◦ dot1q – All C-VLANs and untagged frames are classified into the service.
Note
For a full explanation of Ethernet Services, service types, and attached interface types, see
Configuring Ethernet Service(s).

6 In the Ethernet Interface field, select the port connected to the external switch. This should be Ethernet: Slot
1, Port 1.
7 In the Radio #1 Interface field, select Radio: Slot 2, Port 1.
8 Click Next. Page 2 of the Multiband Quick Configuration wizard opens.

Figure 114: Multiband Quick Configuration Wizard – Page 2

9 In the Ethernet #1 Interface field, select Ethernet: Slot 1, Port 2.

Phn 3963 013v000

Page 204
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

10 In the Maximum Bandwidth (Mbps) field, select the maximum traffic that the PTP 820E will pass to the paired
unit.
◦ When using Fixed ACM mode, set this parameter to the actual rate you
want the paired unit to broadcast.
◦ When using Adaptive ACM mode, set this parameter to the maximum of
the paired unit’s capacity.
The default value is 1000 Mbps.

Note
The Maximum Bandwidth represents the L1 capacity of the radio link connected to the Ethernet
member. The actual bandwidth that will be available for traffic is less due to overhead.

When using a third-party radio as the paired unit, it is particularly important to set this
parameter properly in order to ensure optimal performance. Failure to properly set this
parameter may lead to frequent pauses as the queue fills up during low capacity periods,
such as when weather conditions cause the ACM profile to drop.
11 Click Next. Page 3 of the Multiband Quick Configuration wizard opens.

Figure 115: Multiband Quick Configuration Wizard – Page 3

12 Configure the following radio parameters.

i In the TX Frequency (MHz) field, set the transmission radio frequency in MHz.
ii In the RX Frequency (MHz) field, set the received radio frequency in MHz.
iii In the TX Level (dBm) field, enter the desired TX signal level (TSL). The range of values depends on the
frequency and RFU type.
iv To mute the TX output of the radio, select Mute in the TX mute field. To unmute the TX output of the radio,
select Unmute.

Phn 3963 013v000

Page 205
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

13 Click Next. Page 4 of the Multiband Quick Configuration wizard opens.

Figure 116: Multiband Quick Configuration Wizard – Page 4

14 In the Script ID field, select the MRMC script you want to assign to the radio or XPIC group. For a full
explanation of choosing an MRMC script, see Configuring the Radio (MRMC) Script(s).
15 In the Operational Mode field, select the ACM mode: Fixed or Adaptive.
◦ Fixed ACM mode applies constant TX and RX rates. However, unlike
regular scripts, with a Fixed ACM script you can specify a maximum profile
to inhibit inefficient transmission levels.
◦ In Adaptive ACM mode, TX and RX rates are dynamic. An ACM-enabled
radio system automatically chooses which profile to use according to the
channel fading conditions.
16 Do one of the following:
◦ If you selected Fixed in the Operational Mode field, the next field is Profile.
Select the ACM profile in the Profile field.
◦ If you selected Adaptive in the Operational Mode field, the following two
fields are displayed:
◦ Maximum profile – Enter the maximum profile for the script. See
Configuring the Radio (MRMC) Script(s).
◦ Minimum profile – Enter the minimum profile for the script. See
Configuring the Radio (MRMC) Script(s).

Phn 3963 013v000

Page 206
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

17 Click Next. Page 5 of the Multiband Quick Configuration wizard opens.

Figure 117: Multiband Quick Configuration Wizard – Page 5

18 In the In Band Management field, select Yes to configure in-band management, or No if you do not need in-
band management. If you select Yes, the Management VLAN field appears.
19 If you selected Yes in the In Band Management field, select the management VLAN in the Management VLAN
field.

Note
You can only select Untagged if you are not using IP Forwarding. If you select Untagged and
you want to configure IP Forwarding later, you will first have to change Untagged to a specific
VLAN. See Mate Management Access (IP Forwarding) (CLI).

20 If you want to use the Ethernet interface as well as the radio interface for in-band management, select In Band
includes Ethernet interface.

Note
If you want to manage the via the PTP 820E, refer to the instructions in Inband Management via
the PTP 820E.

21 Click Finish. The Summary page opens. This page displays the parameters you have selected for the group.

Phn 3963 013v000

Page 207
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 118: Multiband Quick Configuration Wizard – Summary Page

22 To complete configuration of the Multiband group on the PTP 820E, click Submit. If you want to go back and
change any of the parameters, click Back. After you click Submit, the unit is reset.

Note
After adding Eth2 to the Multiband group, an alarm is raised (Alarm 1794). This alarm is cleared
when the unit is reset.

After configuring the Multiband group on the PTP 820E, you must perform the following configurations on the PTP
820C, PTP 820C-HP, or PTP 820S:
1 Configure a Pipe service between the Ethernet port connected to the PTP 820E and the radio or Multi-Carrier
ABC group. See Configuring Ethernet Service(s).

Note
If the paired unit is an PTP 820C, PTP 820C-HP, PTP 820S, or third-party microwave radio, the service
must be a Pipe service.
2 Configure Automatic State Propagation with ASP trigger by remote fault enabled. See Configuring Automatic
State Propagation and Link Loss Forwarding.
3 Configure Bandwidth Notification:
i Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth Notification page opens.

Phn 3963 013v000

Page 208
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

Figure 119: Bandwidth Notification Page (Empty)

ii Click Add. The Bandwidth Notification – Add page opens.

Figure 120: Bandwidth Notification – Add Page

iii In the Name field, select a descriptive name. In the Protocol Type field, select Radio BNM.
iv In the Name field, select a descriptive name.
v In the Admin field, select Up.
vi In the Monitored Interface field, select the interface or group connected to the PTP 820E.
Vii In the TX VLAN Type field, select the VLAN type that will be used in bandwidth notification
messages. Options are:
◦ C-Vlan
◦ S-Vlan
vii In the TX VLAN field, select the VLAN to be used in bandwidth notification

Phn 3963 013v000

Page 209
Chapter 3: Configuration Guide Configuring a Link Using the Quick Configuration Wizard

messages. Options are:

◦ 1-4090
◦ Untagged

Note
You should configure the same VLAN encapsulation as the radio service point attached to the service
for the Multiband group. For example, if the service point on the radio interface is C-Vlan 20, select
C-Vlan in the TX VLAN Type field and 20 in the TX VLAN field.

vii Click Apply. The configuration is added to the Bandwidth Notification page with the Protocol Type Radio
BNM.

Figure 121: Bandwidth Notification Page (Populated with Radio BNM)

Phn 3963 013v000

Page 210
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

Configuring Links, Link Groups, and Redudancy

This section provides instructions for configuring links, link groups, and protection manually, using Advanced
mode.
Most link configurations can be configured using Quick Configuration wizards, and it is recommended to do so
whenever possible. See Configuring a Link Using the Quick Configuration Wizard.

Note
This option is only relevant for PTP 820C and PTP 820C-HP units.

This section includes:

• Multi-Carrier ABC Overview
• Configuring a Multi-Carrier ABC Group
• Configuring the Multi-Carrier ABC Minimum Bandwidth Override Option
• Adding and Removing Group Members
• Deleting a Multi-Carrier ABC Group

Multi-Carrier ABC Overview

Multi-Carrier Adaptive Bandwidth Control (ABC) enables multiple separate radio carriers to be shared by a single
Ethernet port. This provides an Ethernet link over the radio with the total sum of the capacity of all the radios in
the group, while still behaving as a single Ethernet interface. In Multi-Carrier ABC mode, traffic is dynamically
divided among the carriers, at the Layer 1 level, without requiring Ethernet Link Aggregation.
Load balancing is performed regardless of the number of MAC addresses or the number of traffic flows. During
fading events which cause ACM modulation changes, each carrier fluctuates independently with hitless
switchovers between modulations, increasing capacity over a given bandwidth and maximizing spectrum
utilization. The result is 100% utilization of radio resources in which traffic load is balanced based on instantaneous
radio capacity per carrier.
One Multi-Carrier ABC group that includes both radio interfaces can be configured per unit. The MRMC scripts for
both radio carriers must be identical.

Configuring a Multi-Carrier ABC Group

To configure a Multi-Carrier ABC group:
1. Select Radio > Groups > Multi Carrier ABC. The Multi Carrier ABC page opens.

Phn 3963 013v000

Page 211
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

Figure 122 Multi-Carrier ABC Group Page (Empty)

2. Click Create Group. The first page of the Create ABC Group wizard opens.

Figure 123 Create ABC Group Wizard – First Page

3. Optionally, enter a descriptive name for the group in the Group Name field.
4. In the Minimum bandwidth field, select Enable to enable Minimum Bandwidth Override or Disable to disable
Minimum Bandwidth Override.
5. In the Minimum bandwidth threshold field, enter the minimum bandwidth override threshold (in Mbps). The
threshold can be between 0 – 20000 Mbps, with a resolution of 1 Mbps. If the group’s bandwidth capacity falls
beneath this threshold, the group is automatically placed in Down state until the bandwidth capacity exceeds
this threshold.

Note
For an explanation of Multi-Carrier ABC Minimum Bandwidth Override, see Configuring the Multi-
Carrier ABC Minimum Bandwidth Override Option.

6. Click Next. The next page of the Create Group wizard opens.

Phn 3963 013v000

Page 212
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

Figure 124 Create ABC Group Wizard – Second Page

7. In the Member 1 field, select a radio interface.

Note
Although you may select the Radio members in any order you wish, ABC configuration will not
succeed unless Radio slot 2 port 1 is selected first and Radio slot 2 port 2 is selected second.

8. Click Next. The next page of the Create Group wizard opens.
9. In the Member 2 field, select a radio interface.
10. Click Next. A summary page opens.

Figure 125 Create ABC Group Wizard – Finish Page

11. Click Submit, A message appears indicating whether or not the operation was successful.
12. Click Close to close the Create Group wizard. You must click Submit before clicking Close, or the selections you
made will be discarded and the process cancelled.

Phn 3963 013v000

Page 213
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

Configuring the Multi-Carrier ABC Minimum Bandwidth

Override Option
A multi-carrier ABC group can be configured to be placed in Down state if the group’s capacity falls beneath a user-
defined threshold.
By default, the Multi-Carrier ABC minimum bandwidth override option is disabled. When enabled, the Multi-
Carrier ABC group is automatically placed in a Down state in the event that the group’s aggregated capacity falls
beneath the user-configured threshold. The group is returned to an Up state when its aggregated capacity goes
above the threshold.
In order to use Multi-Carrier ABC Minimum Bandwidth Override, an ASP group must be configured on the PTP
820C or PTP 820C-HP unit in which the Monitored Interface is the Multi-Carrier ABC group and the Controlled
Interface is the Ethernet interface that faces the upstream PTP 820 unit. See Configuring Automatic State
Propagation.
An alarm is also raised when this feature is enabled and the group’s aggregated capacity falls beneath the
threshold:
• Alarm ID – 2201
• Alarm Description – Multi Carrier ABC bandwidth is below the threshold
This option is used in conjunction with the LAG group shutdown in case of degradation event option (see LAG
Group Shutdown in Case of Degradation Event ) in cases where the operator wants to re-route traffic from an
upstream switch connected to an another PTP 820 unit whenever the link is providing less than a certain capacity.
To set up a configuration in which a drop in the capacity of the Multi-Carrier ABC group closes the Ethernet port in
the upstream PTP 820 unit, you must perform all of the following steps:
• Enable the Multi-Carrier ABC minimum bandwidth option and set a threshold on the PTP 820C unit, as
described below.
• Enable an ASP group on the PTP 820C unit, where the Monitored Interface is the Multi-Carrier ABC group and
the Controlled Interface is the Ethernet interface that faces the upstream PTP 820 unit. See Configuring
Automatic State Propagation.
• Enable the LAG group shutdown in case of degradation event option on the upstream PTP 820 unit.

Note
When using in-band management, management is lost in the event of radio failure and returns when
the radio link is restored.
The minimum bandwidth threshold is based on the capacity of the Multi-Carrier ABC group, not the
combined capacities of the group’s members. The group’s aggregated capacity is displayed in the
Multi-Carrier ABC Group – Edit Group page (Figure 63).

You can configure Multi-Carrier ABC Minimum Bandwidth Override when creating the group. See Configuring a
Multi-Carrier ABC Group.

Phn 3963 013v000

Page 214
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

To configure Multi-Carrier ABC Minimum Bandwidth Override after the group has been created:
1. Select the group in the Multi-Carrier ABC table and click Edit Group. The Edit Group page opens.

Figure 126 Multi-Carrier ABC Group – Edit Group Page

2. In the Minimum bandwidth field, select Enable to enable Minimum Bandwidth Override or Disable to disable
Minimum Bandwidth Override.
3. In the Minimum bandwidth threshold field, enter the minimum bandwidth override threshold (in Mbps). If
the group’s bandwidth capacity falls beneath this threshold, the group is automatically placed in Down state
until the bandwidth capacity exceeds this threshold.
4. Click Apply.

Adding and Removing Group Members

You can add and remove interfaces from the group after creating the group. This is relevant if you want to delete a
Multi-Carrier ABC group, since you must remove the members individually before deleting the group.
To remove interfaces:
1. Select the group in the Multi-Carrier ABC table and click Add/Remove Members. The Multi Carrier ABC -
Add/Remove Members page opens.

Phn 3963 013v000

Page 215
Chapter 3: Configuration Guide Configuring Links, Link Groups, and Redudancy

Figure 127 Multi Carrier ABC Group - Add/Remove Members Page

2. Select a member in the Remove Member field or select Remove All.

Note
Although you may select the Radio members in any order you wish, member removal will not
succeed unless Radio slot 2 port 1 is removed first and Radio slot 2 port 2 is removed second.

3. Click Apply.
4. Repeat these steps to remove additional members from the group.

Deleting a Multi-Carrier ABC Group

Todelete a Multi-Carrier ABC group:
1. Select Radio > Groups > Multi Carrier ABC. The Multi Carrier ABC page opens (Figure 59).
2. Select the group in the Multi-Carrier ABC table and click Add/Remove Members. The Multi Carrier ABC –
Add/Remove Members page opens (Figure 64 Multi Carrier ABC Group - Add/Remove Members Page).
3. Remove each member of the group. See Adding and Removing Group Members.
4. Click Close to close the Mulit Carrier ABC – Add/ Remove Members page.
5. Select the group and click Delete.

Phn 3963 013v000

Page 216
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Configuring Multiband (Enhanced Multi-Carrier

ABC)

This feature requires:

• PTP 820E ESP hardware version
• When used with PTP 820C, PTP 820C-HP, or PTP 820S, PTP 820C/PTP 820C-HP/PTP 820S ESS hardware
version (two SFP ports) is required in order to configure synchronization and/or in-band management for
the PTP 820C, PTP 820C-HP, or PTP 820S

Multiband Overview
Multiband bundles E-Band and microwave radios in a single group that is shared with an Ethernet interface. This
provides an Ethernet link over the radio with capacity of up to 2.5 Gbps. A Multiband link is highly resilient because
the microwave link acts, in effect, as a backup for the E-Band link.
In the event of radio failure in one device, the other device continues to operate to the extent of its available
capacity. Thus, operators benefit from both the high capacity of E-Band and the high reliability of microwave.

Notes:
LLDP is not supported between Eth2 of the PTP 820E and Eth2 of the IP 20C, PTP 820C-HP, or
PTP 820S in Multiband configurations.

Multiband with version 10.5 is not compatible over the link with Multiband using earlier
versions, and Multiband with version 10.7 and higher is not compatible over the link with
Multiband using earlier versions. Therefore, when upgrading the software on a Multiband link to
10.5 or to 10.7 or higher from an earlier version, make sure to upgrade the remote unit first
when using inband management to avoid loss of management.

Multiband Operation
A Multiband node consists of an PTP 820E unit and an PTP 820C, PTP 820C-HP, or PTP 820S unit or a third-party
microwave radio.

Note
Multiband is also supported with PTP 850E. For more information and configuration instructions, refer
to the User Guide for PTP 850E, System Release 10.9.5 or higher.

In a Multiband configuration, all traffic enters the node via the 10G port on the PTP 820E (Eth1). Traffic is passed to
a Multiband group that includes Eth2 and the radio carrier.

Phn 3963 013v000

Page 217
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

The unit paired with the PTP 820E acts as a pipe. When traffic is passed from the PTP 820E to the paired unit, it is
transmitted via Eth2 on the PTP 820E to either a single radio carrier or 2+0 Multi-Carrier ABC group, and
transmitted. To ensure a smooth traffic flow, certain configurations must be performed on the paired unit.
When the PTP 820E is paired with an PTP 820 microwave unit, the following must be configured on the PTP 820
microwave unit:
• A service must be configured between the Ethernet port connected to the PTP 820E and the radio or
Multi-Carrier ABC group being used for the Multiband link.
Note:
If the paired unit is an PTP 820C, PTP 820C-HP, PTP 820S, or third-party microwave radio, the
service must be a Pipe service.
• Automatic State Propagation, with ASP trigger by remote fault enabled.
• Radio BNM.
When the PTP 820E is paired with a third-party unit, the following must be configured on the third-party unit:
• The unit’s switching mechanism must be set to Pipe mode and a Pipe service must be configured between
the Ethernet port connected to the PTP 820E and the paired unit’s radio or radio group.
• Automatic State Propagation must be enabled.
• 802.3X Flow Control must be enabled.
A Pipe service must be configured between the Ethernet port connected to the PTP 820E and the paired unit’s
radio or radio group.

Note:
The latency differential between the PTP 820E and the paired unit cannot be more than 1.6 ms.
That means that under all foreseeable conditions, such as a high ACM profile on one unit and a
low ACM profile on the other unit, there should be no more than a 1.6 ms difference between
the latency of the two radio carriers in the Multiband link.

Phn 3963 013v000

Page 218
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Illustrates Multiband operation with an PTP 820E and PTP 820C or PTP 820C-HP. Error! Reference source not
found. illustrates a configuration that includes synchronization and management of the PTP 820C/PTP 820C-HP via
the PTP 820E. Both of these items are optional, and requires an optical cable between Eth3 on the PTP 820E and
Eth3 on the PTP 820C/PTP 820C-HP, as described in the following sections.

Figure 128 Multiband Operation – PTP 820E and PTP 820C/PTP 820C-HP

Phn 3963 013v000

Page 219
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

This figure illustrates Multiband operation with an PTP 820E paired with a third-party radio. It also illustrates a
configuration that includes synchronization and management of the third-party unit via the PTP 820E.
Synchronization via the PTP 820E requires an optical cable between Eth3 on the PTP 820E and an Ethernet port on
the third-party unit, as described in the following sections.

Figure 129 Multiband Operation – PT 820E and Third-Party Unit

Multiband Configuration
To configure a Multiband node:
1. Connect the external switch to the Eth1 port on the PTP 820E.
2. Connect the Eth2 port on the PTP 820E to the paired unit. When the paired unit is an PTP 820C, PTP 820C-
HP, or PTP 820S, use the Eth2 port on the PTP 820C, PTP 820C-HP, or PTP 820S.
3. Verify that no service points are configured on the Eth2 port of the PTP 820E. If there are service points
on Eth2, remove them. See Deleting a Service Point.
4. Set Eth2 on the PTP 820E to Admin – Down. See Enabling the Interfaces (Interface Manager).
5. On the PTP 820E, configure a Multiband group that includes Eth2 and the radio:
a. Select Radio > Groups > Multi-Carrier ABC. The Multi Carrier ABC Groups page opens.

Phn 3963 013v000

Page 220
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Figure 130 Multi Carrier ABC Groups Page (Empty)

b. Click Create Group. Page 1 of the Create ABC Group wizard opens.

Figure 131 Create ABC Group Wizard – Page 1

c. In the Group ID field, select Enhanced Multi Carrier ABC (Group #1).
d. Optionally, in the Group Name field, enter a descriptive name for the group.
e. Click Next. Page 2 of the Create ABC Group wizard opens.

Phn 3963 013v000

Page 221
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Figure 132 Create ABC Group Wizard – Page 2

f. In the Member #1 field, select Radio: Slot 2, Port 1.

g. Click Next. Page 3 of the Create ABC Group wizard opens.

Figure 133 Create ABC Group Wizard – Page 3

h. In the Member #2 field under Member Selection, select Ethernet: Slot 1, Port 2.
i. In the Member #2 field under Maximum Bandwidth (Mbps), select the maximum traffic that the
PTP 820E will pass to the paired unit.
• When using Fixed ACM mode, set this parameter to the actual rate you want the paired
unit to broadcast.
• When using Adaptive ACM mode, set this parameter to the maximum of the paired
unit’s capacity. The default value is 1000 Mbps.

Phn 3963 013v000

Page 222
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Note:
The Maximum Bandwidth represents the L1 capacity of the radio link connected to the Ethernet
member. The actual bandwidth that will be available for traffic is less due to overhead.

When using a third-party radio as the paired unit, it is particularly important to set this
parameter properly in order to ensure optimal performance. Failure to properly set this
parameter may lead to frequent pauses as the queue fills up during low capacity periods, such as
when weather conditions cause the ACM profile to drop.

j. Click Finish. The Selection Summary page of the Create ABC Group wizard opens.

Figure 134 Create ABC Group Wizard – Page 3

k. Click Submit. The group is added to the Multi Carrier ABC page.

Phn 3963 013v000

Page 223
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Figure 135 Multi Carrier ABC Groups Page (Populated with Multiband Group)

l. Reset the PTP 820E.

Note:
After adding Eth2 to the Multiband group, an alarm is raised (Alarm 1794). This
alarm is cleared when the unit is reset.
6. On the paired unit, configure a Pipe service between the port receiving traffic from the PTP 820E and the
radio or Multi-Carrier ABC group. See Configuring Ethernet Service(s).
7. On the paired unit, configure Automatic State Propagation with ASP trigger by remote fault enabled. See
Error! Reference source not found..
8. If the paired unit is an PTP 820C, PTP 820C-HP, or PTP 820S, configure Radio BNM:

Note:
If the paired unit is a third-party radio, enable 802.3X Flow Control.

a. Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth Notification page opens.

Figure 136 Bandwidth Notification Page (Empty)

b. Click Add. The Bandwidth Notification – Add page opens.

Phn 3963 013v000

Page 224
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Figure 137 Bandwidth Notification – Add Page

c. In the Name field, select a descriptive name.

d. In the Protocol Type field, select Radio BNM.
e. In the Name field, select a descriptive name.
f. In the Admin field, select Up.
g. In the Monitored Interface field, select the interface or group connected to the PTP 820E.
h. In the TX VLAN Type field, select the VLAN type that will be used in bandwidth
notification messages. Options are:
• C-Vlan
• S-Vlan
i. In the TX VLAN field, select the VLAN to be used in bandwidth notification messages.
Options are:
• 1-4090
• Untagged
j. Click Apply. The configuration is added to the Bandwidth Notification page with the Protocol Type
Radio BNM.

Phn 3963 013v000

Page 225
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Figure 138 Bandwidth Notification Page (Populated with Radio BNM)

Multiband Management
The PTP 820E unit in a Multiband configuration can be managed normally, as in any other configuration. For in-
band management of the PTP 820E, configure the management service on the PTP 820E Multiband group. See
Error! Reference source not found..
The following options are available for managing the paired unit in a Multiband configuration:
• Inband management via the PTP 820E
• Inband management directly from the external switch
• Out-of-Band management

Phn 3963 013v000

Page 226
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Inband Management via the PTP 820E

The paired unit can managed via the PTP 820E. In-band management via the PTP 820E requires that the paired unit
have at least two free SFP ports. When the paired unit is an PTP 820C, PTP 820C-HP, or PTP 820S, this requires an
ESS hardware version for the PTP 820C, PTP 820C-HP, or PTP 820S. To manage the paired unit via the PTP 820E, an
optical cable must be connected between port Eth3 on the PTP 820E and Eth3 on the PTP 820C, PTP 820C-HP, or
PTP 820S or the Ethernet port receiving management data on the third-party unit.
Since Eth2 and Eth3 on the PTP 820E are accessed via a single gland on a single physical port, a special cable must
be used. This cable fits into the single gland on the PTP 820E in order to connect to both Eth2 and Eth3. On the
other side of the cable, the cable is split so that a separate cable can be inserted into the gland for each of the
Ethernet ports on the paired unit.

Figure 139 Multiband Cable for Use with CSFP Port

Table 10 Multiband Cable for Use with CSFP Port

Cable Marketing Model Cable Description

PTP 820_FO_SM_LC2SNG2LC_ARM_5m CABLE,FO,DUAL LC TO LC/LC SPLIT,5.3M,SM,3xM28

GLAND,OUTDOOR

Phn 3963 013v000

Page 227
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

On the PTP 820E, a CSFP module must be used for Port 2 in order to utilize both Eth2 and Eth3.
When the paired unit is an PTP 820C, PTP 820C-HP, or PTP 820S, Eth2 and Eth3 on the PTP 820C, PTP 820C-HP, or
PTP 820S must use BiDi SFP modules.

Figure 140 Multiband Configuration with Inband Management and/or SyncE via the PTP 820E

A management service must be defined between the management port of the PTP 820E and Eth3 on the PTP 820E.
This transmits management to the paired unit. See Error! Reference source not found..

Note: To avoid loops, in-band management must not be configured on the slave unit.

Phn 3963 013v000

Page 228
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Inband Management Directly via the External Switch

An PTP 820 microwave radio paired with an PTP 820E can be managed by means of a TP cable connected to the
MGT port on the PTP 820 and to the LAN port on a PC or laptop. If the paired unit is a third-party radio, it can also
be managed via out-of-band management.
In this configuration, the special Multiband cable is not required unless you are using synchronization via the PTP
820E for the paired unit. See Configuring Synchronization in a Multiband Node.

Figure 141 Multiband Configuration with Direct Inband Management to the Paired Unit

Phn 3963 013v000

Page 229
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

Out-of-Band Management
The PTP 820 microwave radio can be managed by means of a TP cable connected to the MGT port on the PTP 820
and to the LAN port on a PC or laptop.
In this scenario, the PTP 820E is managed by connecting the PC or laptop used for management to the PoE Injector,
which provides transfers power and management to the MGT/PoE port of the PTP 820E.

Figure 142 Multiband Configuration with Direct Inband Management to the PTP 820C, PTP 820C-HP, or PTP 820S

Configuring Synchronization in a Multiband Node

SyncE and 1588 Transparent Clock can be used in Multiband nodes. SyncE and 1588 Transparent Clock can be
configured for both the PTP 820E and the unit paired with the PTP 820E.

Note:
When a third-party unit is paired with the PTP 820E, it is a prerequisite that the third-party radio unit
support SyncE and, if required, 1588 Transparent Clock in order to provide synchronization for the
Multiband node.

Phn 3963 013v000

Page 230
Chapter 3: Configuration Guide Configuring Multiband (Enhanced Multi-Carrier ABC)

In Release 11.3, synchronization for the paired unit requires an optical cable between port Eth3 on the PTP 820E
and Eth3 on the PTP 820C, PTP 820C-HP, or PTP 820S or a free Ethernet port on the third-party radio. In this
configuration, Port 2 on the PTP 820E must be used as a CSFP port. The paired unit must have at least two 1G SFP
ports on the paired unit. For PTP 820C, PTP 820C-HP, or PTP 820S, this means an ESS hardware version is required.
Eth2 and Eth3 on the PTP 820C, PTP 820C-HP, or PTP 820S must use BiDi SFP modules.
The cable fits into the single gland on the PTP 820E in order to connect to both Eth2 and Eth3. On the other side of
the cable, the cable is split so that a separate cable can be inserted into the gland for each of the Ethernet ports on
the paired unit. This is the same cable and the same setup used for inband management via the PTP 820E. For
details, see Inband Management via the PTP 820E.
To configure SyncE on a Multiband node:
1. On the PTP 820E, configure three synchronization sources: Eth1, the radio, and Eth3. Do not configure Eth2 as
a synchronization source.
2. On the paired unit, configure two synchronization sources: the Ethernet port receiving synchronization from
the PTP 820E, and the radio. When using Multi-Carrier ABC, configure both radios as synchronization sources.
In ring configurations, configure priority order in the direction of traffic on the ring.

Phn 3963 013v000

Page 231
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Configuring Link Aggregation (LAG) and LACP

Link aggregation (LAG) enables you to group several physical Ethernet or radio interfaces into a single logical
interface bound to a single MAC address. This logical interface is known as a LAG group. Traffic sent to the
interfaces in a LAG group is distributed by means of a load balancing function. PTP 820 uses a distribution function
of up to Layer 4 in order to generate the most efficient distribution among the LAG physical ports.
This section explains how to configure LAG and includes the following topics:
• LAG Overview
• Configuring Link Aggregation (LAG) and LACP
• Enabling and Disabling LAG Group Shutdown in Case of Degradation Event
• Configuring Enhanced LAG Distribution
• Deleting a LAG Group
• Displaying LACP Parameters and Statistics

LAG Overview
LAG can be used to provide redundancy for Ethernet interfaces, both on the same PTP 820 unit (line protection)
and on separate units (line protection and equipment protection). LAGs can also be used to provide redundancy
for radio links.
LAG can also be used to aggregate several interfaces in order to create a wider (aggregate) link. For example, LAG
can be used to create a 4 Gbps channel.
You can create up to four LAG groups. The following restrictions exist with respect to LAG groups:
• Only physical interfaces (including radio interfaces), not logical interfaces, can belong to a LAG group.
• 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.
• When removing an interface from a LAG group, the removed interface is assigned the default interface values.
There are no restrictions on the number of interfaces that can be included in a LAG. It is recommended, but not
required, that each interface in the LAG have the same parameters (e.g., speed, duplex mode).
The LAG page lists all LAG groups configured on the unit.

Note
To add or remove an Ethernet interface to a LAG group, the interface must be in an administrative
state of “down”. This restriction does not apply to radio interfaces. For instructions on setting the
administrative state of an interface, see Enabling the Interfaces (Interface Manager).

PTP 820 supports LACP, which expands the capabilities of static LAG and provides interoperability with third-party
equipment that uses LACP. LACP improves the communication between LAG members. This improves error
detection capabilities in situations such as improper LAG configuration or improper cabling. It also enables the LAG
to detect uni-directional failure and remove the link from the LAG, preventing packet loss.

Phn 3963 013v000

Page 232
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

When LACP is enabled, the device sends LACPDUs to the LAG members on the other side of the link every 30
seconds. If a LAG member fails to respond to three consecutive LACPDUs, the LAG member is temporarily removed
from the LAG. This is known as a long timeout, with the total timeout adding up to the time it takes to send three
LACPDUs (90 seconds). The device continues to send LACPDUs, and the member is restored to the LAG as soon as
it responds to an LACPDU.
LACP is enabled as part of the LAG configuration process. It should only be used if the LAG is in a link with another
LACP-enabled LAG.

Note
LACP is not supported with unit protection. For unit protection, a special, limited implementation is
configured on the logical interface level. See Error! Reference source not found..
LACP can only be used with Ethernet interfaces.
LACP cannot be used with Enhanced LAG Distribution or with the LAG Group Shutdown in Case of
Degradation Event feature.

Configuring a LAG Group

Adding and Removing Group Members
To create a LAG group:
1. Select Ethernet > Interfaces > Groups > LAG. The LAG page opens.
2. Click Create Group underneath the Link Aggregation table. The Create LAG Group page opens.

Figure 143 Create LAG Group – Page 1

3. In the Group ID field, select a LAG Group ID. Only LAG IDs that are not already assigned to a LAG group appear
in the dropdown list.
4. In the LACP field, select Enable to enable LACP on the LAG or Disable to disable LACP on the LAG. The default
value is Disable.

Phn 3963 013v000

Page 233
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

5. In the Member 1 field, select an interface to assign to the LAG group. Only interfaces not already assigned to a
LAG group appear in the dropdown list.
6. Click Next. A new Create LAG Group page opens.

Figure 144 Create LAG Group – Page 2

7. In the Member 2 field, select an additional interface to assign to the LAG Group.
8. To add additional interfaces to the LAG group, repeat steps 5 and 6.
9. When you have finished adding interfaces to the LAG group, click Finish. A new Create LAG Group page opens
displaying all the interfaces you have selected to include in the LAG group.

Figure 145 Create LAG Group – Final Page

10. Click Submit. If all the interfaces meet the criteria listed above, a message appears that the LAG group has
been successfully created. If not, a message appears indicating that the LAG group was not created and giving
the reason.

Editing a LAG Group

To edit an existing LAG group:

Phn 3963 013v000

Page 234
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

1. Select Ethernet > Interfaces > Groups > LAG. The LAG page opens.
2. Select the LAG group you want to edit in the Link Aggregation table.
3. Click Edit underneath the Link Aggregation table. The Link Aggregation - Edit page opens.

Figure 146 Link Aggregation - Edit Page

4. Do any of the following:

o To enable or disable LACP, select Enable or Disable in the LACP field. See LAG
Overview for restrictions.
o To enable or disable LAG Group Shutdown in case of Degradation Event, select
Enable or Disable in the LAG degrade field. See LAG Group Shutdown in Case of
Degradation Event for restrictions.
o To remove an interface from the LAG Group, select the interface in the Remove
Member field.
o To add an interface to the LAG Group, select the interface in the Add Member field.
5. Click Apply.
6. To remove or add additional interfaces, repeat steps 4 and 5.
7. When you are finished, click Close to close the Link Aggregation – Edit page.

Note
When removing an interface from a LAG group, the removed interface is assigned the default
interface values.
For information about the LAG degrade field, see Enabling and Disabling LAG Group Shutdown in
Case of Degradation Event .

Phn 3963 013v000

Page 235
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Enabling and Disabling LAG Group Shutdown in Case of

Degradation Event
Note
LAG Group Shutdown in Case of Degredation Event cannot be used with LACP.

A LAG group can be configured to be automatically closed in the event of LAG degradation. This option is used if
you want traffic from the switch to be re-routed during such time as the link is providing less than a certain
capacity.
By default, the LAG group shutdown in case of degradation event option is disabled. When enabled, the LAG is
automatically closed in the event that any one or more ports in the LAG fail. When all ports in the LAG are again
operational, the LAG is automatically re-opened.

Note
Failure of a port in the LAG also triggers a lag-degraded alarm, Alarm ID 100.

To enable or disable the LAG group shutdown in case of degradation event option:
1. Select Ethernet > Interfaces > Groups > LAG to open the LAG page.
2. Select the LAG group in the Link Aggregation table.
3. Click Edit underneath the Link Aggregation table. The Link Aggregation - Edit page opens (Figure 83).
4. In the LAG degrade field, select Enable to enable the LAG group shutdown in case of degradation event option
or Disable to disable the LAG group shutdown in case of degradation event option.
5. Click Apply.

Configuring Enhanced LAG Distribution

You can change the distribution function by selecting from ten pre-defined LAG distribution schemes. The feature
includes a display of the TX throughput for each interface in the LAG, to help you identify the best LAG distribution
scheme for the specific link.

Note
Enhanced LAG distribution is only available for LAG groups that consist of exactly two interfaces. It
cannot be used with LACP.

To configure enhanced LAG distribution:

1. Select Ethernet > Interfaces > Groups > LAG. The LAG page opens.
2. Click LAG DF underneath the Link Aggregation table. The LAG Distribution Function (DF) page opens.

Phn 3963 013v000

Page 236
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Figure 147 Link Aggregation - Edit Page

3. In the Distribution Function field, select a pre-set distribution scheme, from 1 to 10. It is recommended to
experiment with the various schemes, monitoring the TX byte count fields for each interface to determine the
efficiency of each distribution scheme for the link. The default distribution scheme is 1. The default LAG
distribution pattern is 1.
4. To clear the TX byte counts, select Clear on read for one or both interfaces. The byte counts will be cleared
when you close the LAG Distribution Function (DF) page or click Refresh.

Note
This counter will also be cleared for the members of the LAG in the Port RMON Statistics page.

5. Click Apply to apply the selected distribution scheme.

Deleting a LAG Group

In order to delete a LAG group, you must first make sure that no service points are attached to the LAG group.
To delete a LAG group:
1. Select Ethernet > Interfaces > Groups > LAG. The LAG page opens.
2. Select the LAG group you want to delete in the Link Aggregation table.
3. Click Delete underneath the Link Aggregation table. The LAG group is deleted.
To delete multiple LAG groups:
1. Select the LAG groups in the Link Aggregation table or select all the LAG groups by selecting the check box in
the top row.
2. Click Delete underneath the Link Aggregation table.

Phn 3963 013v000

Page 237
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Displaying LACP Parameters and Statistics

You can display the following LACP parameters and staistics:
• LACP Aggregation (per LAG)
• LACP Port Status
• LACP Port Statistics
• LACP Port Debug Statistics

Note
PTP 820 does not support any LACP write parameters.

Displaying LACP Aggregation Status Parameters

To Display LACP aggregation status parameters:
1. Select Ethernet > Protocols > LACP > Aggregation to open the LACP Aggregation page.

Figure 148 LACP Aggregation Page

The following table describes the LACP aggregation status parameters.

Table 11 LACP Aggregation Status Parameters

Parameter Definition
LAG Interface Location Identifies the LAG group.
Administrative Key The current administrative value of the key for the Aggregator.
Aggregator MAC The individual MAC address assigned to the Aggregator.
Address
Aggregate or Individual Indicates whether the Aggregator represents an aggregate or an
individual link.

Phn 3963 013v000

Page 238
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Frame Collector The maximum delay, in tens of microseconds.

Maximum Delay
Actor System ID The MAC address value used as a unique identifier for the system that
contains this Aggregator.
Actor System Priority The priority value associated with the Actor’s System ID.
Actor Operational Key The current operational value of the Key for the Aggregator.
Partner System ID The MAC address value consisting of the unique identifier for the current
protocol Partner of this Aggregator.
Partner System Priority The priority value associated with the Partner’s System ID.
Partner Operational Key The current operational value of the Key for the Aggregator’s current
Protocol partner.

Displaying LACP Port Status Parameters

To display LACP port status parameters:
1. Select Ethernet > Protocols > LACP > Port > Status to open the LACP Port Status page.

Figure 149 LACP Port Staus Page

2. The LACP Port Status page displays the major port status parameters, per port. To display all the available
LACP port status parameters, select a port and click View. The LACP Port Status – View page is displayed.

Phn 3963 013v000

Page 239
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Figure 150 LACP Port Status – View Page

Table 12 LACP Port Status Parameters

Parameter Definition
Port Interface Location The location of the port.
Selected Aggregator ID The identifier value of the Aggregator that this Aggregation port has
currently selected.
Attached Aggregator ID The identifier value of the Aggregator that this Aggregation port is
currently attached to.
Aggregate or Individual Indicates whether the Aggregation Port is able to aggregate or is only
able to operate as an individual link.
Actor System ID The MAC Address value that defines the value of the System ID for the
system that contains this Aggregation Port.
Actor System Priority The priority value associated with the Actor’s System ID.
Actor Port The port number locally assigned to the Aggregation Port.

Phn 3963 013v000

Page 240
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Actor Port Priority The priority value assigned to this Aggregation Port.
Actor Administrative Key The current administrative value of the Key for the Aggregation Port.
Actor Administrative The administrative values of the Actor’s state as transmitted by the Actor
State via LACPDUs.
Actor Operational Key The current operational value of the Key for the Aggregation Port.
Actor Operational State The current operational values of the Actor’s state as transmitted by the
Actor via LACPDUs.
Partner Operational Key The current operational value of the Key for the protocol Partner.
Partner Operational The current values of Actor State in the most recently received LACPDU
State transmitted by the protocol Partner.
Partner Operational The MAC Address value representing the current value of the
System ID Aggregation Port’s protocol Partner’s System ID.
Partner Operational The operational value of priority associated with the Partner’s System ID.
System Priority
Partner Operational Port The operational port number assigned to this Aggregation port by the
Aggregation port’s port Partner.
Partner Operational Port The Priority value assigned to this Aggregation port by the Partner.
Priority
Partner Administrative The current administrative value of the Key for the protocol Partner.
Key
Partner Administrative The current administrative value of Actor state for the protocol Partner.
State
Partner Administrative The MAC Address value representing the administrative value of the
System ID Aggregation Port’s Protocol partner’s System ID.
Partner Administrative The administrative priority value associated with the Partner’s System ID.
System Priority
Partner Administrative The current administrative value of the port number for the protocol
Port partner.
Partner Administrative The current administrative value of the port priority for the protocol
Port Priority partner.

Displaying LACP Port Statistics

To Display LACP port statistics:
1. Select Ethernet > Protocols > LACP > Port > Statistics to open the LACP Port Statistics page.

Phn 3963 013v000

Page 241
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Figure 151 LACP Port Statistics Page

Table 13 LACP Port Statistics

Parameter Definition
Port Interface Location The location of the port.
Selected Aggregator ID The identifier value of the Aggregator that this Aggregation port has
currently selected.
LACPDUs TX The number of LACPDUs that this port has transmitted.
LACPDUs RX The number of LACPDUs that this port has received.
Unknown RX The number of unknown protocol frames that this port has received.
Illegal RX The number of illegal protocol frames that this port has received.

Displaying LACP Port Debug Staistics

To Display LACP port debug statistics:
1. Select Ethernet > Protocols > LACP > Port > Debug to open the LACP Port Debug page.

Phn 3963 013v000

Page 242
Chapter 3: Configuration Guide Configuring Link Aggregation (LAG) and LACP

Figure 152 LACP Port Debug Page

Table 14 LACP Port Debug Statistics

Parameter Definition
Port Interface Location The location of the port.
Selected Aggregator ID The identifier value of the Aggregator that this Aggregation port has
currently selected.
Debug RX State The state of the receive state machine for the Aggregation port.
Possible values are:
• Current – An LACPDU was received before expiration of the most
recent timeout period.
• Expired – No LACPDU was received before expiration of the most
recent timeout period.
• Defaulted – No LACPDU was received during the two most recent
timeout periods.
Debug Last RX Time The value of a TimeSinceSystemReset (F.2.1) when the last LACPDU was
received by this Aggregation port.
Debug Mux State The state of the Mux state machine for the Aggregation port. Possible
values are Collecting, Distributing, Attached, and Detached.
Debug Mux Reason A text string indicating the reason for the most reason change in the state
of the Mux machine.

Phn 3963 013v000

Page 243
Chapter 3: Configuration Guide Configuring XPIC

Configuring XPIC

Note
This option is only relevant for PTP 820C units.

This section includes:

• XPIC Overview
• Configuring the Radio Carriers
• Creating an XPIC Group
• Performing Antenna Alignment for XPIC

XPIC Overview
Cross Polarization Interference Canceller (XPIC) is a feature that enables two radio carriers to use the same
frequency with a polarity separation between them. Since they will never be completely orthogonal, some signal
cancelation is required.
In addition, XPIC includes an automatic recovery mechanism that ensures that if one carrier fails, or a false signal is
received, the mate carrier will not be affected. This mechanism also ensures that both carriers will be operational,
after the failure is cleared.
To configure and enable XPIC, first configure the carriers and then perform antenna alignment, as described below.
For 2+2 XPIC using an external switch operating in LAG mode, Mate Management Access enables users to manage
both units via in-band management. See Mate Management Access (IP Forwarding) (CLI).

Configuring the Radio Carriers

To configure the radio carriers:
1. Configure the carriers on both ends of the link to the desired frequency channel. Both carriers must be
configured to the same frequency channel.
2. Assign an XPIC (CCDP operational mode) support-enabled script to the carriers on both ends of the link. Each
carrier must be assigned the same script. For details, refer to Configuring the Radio (MRMC) Script(s).

Note
XPIC support is indicated by an X in the script name. For example, mdN_A2828X_111_1205 is an
XPIC-enabled script. mdN_A2828N_130_100 is not an XPIC-enabled script. For a list of XPIC support-
enabled scripts, refer to the most recent PTP 820C Release Notes.

Phn 3963 013v000

Page 244
Chapter 3: Configuration Guide Configuring XPIC

3. In the XPIC page, create an XPIC group that consists of the two RMCs that will be in the XPIC group. See
Creating an XPIC Group.

Creating an XPIC Group

To create an XPIC group:
1. Select Radio > Groups > XPIC. The XPIC page opens.

Figure 153 XPIC Configuration Page

2. In the XPIC Configuration page, select Enable in the Admin state field and click Apply.
To disable XPIC, select Disable in the Admin state field and click Apply.

Performing Antenna Alignment for XPIC

1. Align the antennas for the first carrier. For a 2+2 XPIC configuration (or a 4x4 MIMO configuration), align the
antennas for the first carrier on the upper PTP 820C units. While you are aligning these antennas, mute the second
carrier. See Configuring the Radio Parameters. For a 2+2 XPIC configuration (or a 4x4 MIMO configuration), mute
all the carriers except the first carrier on the upper PTP 820C units.
2. Adjust the antenna alignment until you achieve the maximum RSL for the first-carrier link (the “RSLwanted”).
This RSL should be no more than +/-2 dB from the expected level. Record the RSL of the first carrier as the
“RSLwanted”).
o Measure the RSL of the second carrier and record it as the “RSLunwanted”).

Note
To measure the second carrier, leave the Voltmeter connected to the BNC connector. In the Radio
Parameters page of the Web EMS, change the RSL Connector Source field from PHYS1 to PHYS2 (or 2
to 1). The BNC connector will now measure RSL from the other carrier.

3. Determine the XPI, using either of the following two methods:

o To calculate the XPI, subtract RSLunwanted from the RSLwanted.
o Read the XPI from the Modem XPI field of the Radio Parameters page in the Web
EMS. See Viewing the Radio Status and Settings.

Phn 3963 013v000

Page 245
Chapter 3: Configuration Guide Configuring XPIC

4. The XPI should be between 25dB and 30dB. If it is not, you should adjust the OMT assembly on the back of
the antenna at one side of the link until you achieve the highest XPI, which should be no less than 25dB. Adjust the
OMT very slowly in a right-left direction. OMT adjustment requires very fine movements and it may take several
minutes to achieve the best possible XPI.

Note
As an extra step, to check the veracity of the initial measurements, you can mute the first carrier and
unmute the second carrier on the upper PTP 820C units on both sides of the link. Then measure the
RSL of the second carrier link (the “RSLwanted”), measure the RSL of the first carrier (the
“RSLunwanted”) and determine the XPI. The XPI should match the XPI with the second carriers
muted.

5. Unmute all the carriers and check the RSL levels of all the carriers on both sides of the link. The RSL of the
horizontal carrier of the local unit should match the RSL of the vertical carrier of the remote unit, within ±2dB.
The RSL of the vertical carrier of the local unit should match the RSL of the horizontal carrier of the remote unit,
within ±2dB.
6. For a 2x2 configuration, repeat StepsError! Reference source not found. through Error! Reference source not
found. for the lower PTP 820C units.
7. Check the XPI levels of all the carriers on both sides of the link. All the carriers should have approximately the
same XPI value. Do not adjust the XPI at the remote side of the link, as this may cause the XPI at the local side
of the link to deteriorate.

Note
In some cases, the XPI might not exceed the required 25dB minimum due to adverse atmospheric
conditions. If you believe this to be the case, you can leave the configuration at the lower values, but
be sure to monitor the XPI to make sure it subsequently exceeds 25dB. A normal XPI level in clear sky
conditions is between 25 and 30dB.

Phn 3963 013v000

Page 246
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

Configuring Unit Protection with HSB Radio

Protection (External Protection)

This section explains how to configure unit protection, including HSB radio protection and Ethernet interface
protection, and includes the following topics:
• Unit Protection Overview
• Configuring Ethernet Interface Protection
• Configuring 2+2 HSB Protection on a PTP 820C Unit
• Viewing the Configuration of the Standby unit
• Editing Standby Unit Settings
• Viewing Link and Protection Status and Activity
• Manually Switching to the Standby Unit
• Disabling Automatic Switchover to the Standby Unit
• Disabling Unit Protection
• Configuring 1+1 HSB Unit Protection with Space Diversity

Note
For instructions on configuring 1+1 unit protection with Space Diversity.

Unit Protection Overview

PTP 820C, PTP 820C-HP and PTP 820S support 1+1 HSB radio protection. PTP 820C and PTP 820C-HP also supports
2+2 HSB radio protection. In HSB radio protection, one PTP 820 operates in active mode and the other operates in
standby mode. If a protection switchover occurs, the Active unit goes into standby mode and the Standby unit
goes into active mode.
• For a full explanation of 1+1 HSB radio protection and 2+2 HSB radio protection support in PTP 820C and PTP
820C-HP, refer to the PTP 820C Technical Description.
• For a full explanation of 1+1 HSB radio protection support in PTP 820S, refer to the PTP 820S Technical
Description.

To configure unit protection, you must perform the following steps:

1 Configure Ethernet interface protection – See Configuring Ethernet Interface Protection.
2 Configure HSB radio protection – See Configuring HSB Radio Protection.
3 For 2+2 HSB configurations (PTP 820C only), perform the additional steps described in Configuring 2+2
HSB Protection on a PTP 820C Unit.

Phn 3963 013v000

Page 247
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

Note
For FIPS configurations, the external protection link must be encrypted using IPsec. This encrypts all IP
packets that pass between the management ports of the two PTP 820 units. For instructions, see
Encrypting the External Protection Link.

Configuring Ethernet Interface Protection

There are two modes for Ethernet interface protection in an HSB radio protection configuration:
• Line Protection Mode – Traffic is routed to the Ethernet ports via two ports on an external switch (only Cisco
Switch has been certified).
• Split Protection Mode – Only available for optical Ethernet ports. An optical splitter cable is used to connect to
both the active and the standby optical Ethernet ports.

Configuring Line Protection Mode with Cisco Switch

To configure line protection mode:
1 Configure the GE ports on the external switch in LACP mode. The external switch must support LACP.

Note
PTP 820 supports a special LACP implementation for purposes of line protection only. This LACP
implementation is configured on the logical interface level, as described below. Regular LACP is
configured as part of the LAG configuration, and is not supported with unit redundancy. See
Configuring Link Aggregation (LAG) and LACP.

2 Connect one port on the external switch to an Ethernet port on the active PTP 820, and the other port on
the external switch to an Ethernet port on the standby PTP 820.
3 Enable LACP on the Ethernet interface connected to the external switch on the active PTP 820:
i Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens .
ii Select the interface and click Edit. The Logical Interfaces – Edit page opens.

Phn 3963 013v000

Page 248
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

Figure 154 Logical Interfaces – Edit Page

iii In the Interface Mode field, select LACP.

iv Click Apply, then Close.

Configuring Split Ethernet Interface Protection Mode (CLI)

To configure split Ethernet interface protection mode:
1 Use an optical splitter to route traffic to an optical Ethernet port on each PTP 820 unit.
2 Proceed to Configuring HSB Radio Protection.

Configuring HSB Radio Protection

You must perform the initial configuration of a 1+1 or 2+2 HSB system using a splitter cable for each unit to
provide a management connection to each unit. For instructions on preparing and connecting the splitter cables,
refer to the Installation Guide for PTP 820C or PTP 820S.
To configure HSB radio protection:
1. Before enabling protection, you must:
i. Verify that both units have the same hardware part number (see Displaying Unit Inventory) and the
same software version (see Viewing Current Software Versions). If the units do not have the same
software version, upgrade each unit to the most recent software release (see Upgrading the
Software)
ii. Assign an IP address to each unit. For instructions, see Changing the Management IP Address.

Phn 3963 013v000

Page 249
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

iii. Establish a management connection to one of the units. You can select either unit; once you enable
Protection Administration, the system will determine which unit becomes the Active unit.
2. Select Platform > Management > Unit Redundancy. The Unit Redundancy (HSB Protection) page opens.

Figure 155 Unit Redundancy Page

3. In the Protection Admin field, select Enable.

4. Click Apply.
• The system configures itself for HSB protection:
• The system determines which unit is the Active unit based on a number of pre-defined criteria.
• When the system returns online, all management must be performed via the Active unit using the IP address
you defined for that unit.
• The IP address you defined for the unit which is now the Standby unit is no longer valid, and the management
port of the Standby unit becomes non-operational.
• Management of the Standby unit is performed via the Active unit, via the cable between the two MIMO/Prot
ports on the splitters connecting the two units.
• HSB protection is enabled on both units.
• The Unit Redundancy page refreshes to include additional radio protection fields.

Figure 156 Unit Redundancy Page when Redundancy Enabled

In addition, almost every Web EMS page will now include two tabs on top of the main section of the page:
o Active – Enables you to configure the Active unit.

Phn 3963 013v000

Page 250
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

o Standby – In most cases, this tab is read-only and enables you to display Standby unit
parameters. Even when a switchover occurs, the unit displayed in the Web EMS is
always the currently Active unit.

Note
The parameters that are editable on the Standby tab are described in Editing Standby Unit Settings.

5. Once you have enabled Protection:

i. Perform all necessary radio configurations on the Active unit, such as setting the frequency, assigning
MRMC scripts, unmuting the radio, and setting up radio groups such as XPIC or Multi-Carrier ABC
(Multi-Radio).
ii. Perform all necessary Ethernet configurations on the Active unit, such as defining Ethernet services.
iii. In the Unit Redundancy page, click Copy to Mate to copy the configuration of the Active unit to the
Standby unit. Confirm the action in the confirmation window that appears.

Note
While the system is performing the copy-to-mate operation, a temporary loss of management
connection will occur.

To keep the Standby unit up-to-date, after any change to the configuration of the Active unit click Copy to Mate to
copy the configuration to the Standby unit.
If you change the configuration of the Active unit but do not perform Copy to Mate, a Configuration
Mismatch alarm appears in the Faults > Current Alarms page.

Note
You can use the following CLI command to display a list of mismatched parameters:
root> platform management protection show mismatch details

Configuring 2+2 HSB Protection on a PTP 820C Unit

In order to configure 2+2 HSB unit protection on a PTP 820C unit, you must simply enable the second radio carrier
on both units on both sides of the link. No other configuration is necessary other than the configuration described
above.
• To enable the second radio carrier on both units, use the Interface Manager page (see Figure 23). The
following figure shows the Interface Manager page with both radio carriers enabled.

Phn 3963 013v000

Page 251
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

Figure 157 Interface Manager Page – Both Radio Carriers Enabled

Viewing the Configuration of the Standby unit

You can view the settings of the standby unit any time.
To view the settings of the standby unit, click the Standby tab of the desired page. The following is an example of
the Standby tab of the Radio Parameters page after Protection Admin has been enabled.

Figure 158 Standby Tab of Radio Parameters Page

Editing Standby Unit Settings

Almost all settings of the standby unit are view-only. However, several settings are editable on the Standby unit.
They must be configured separately for the Standby unit, and are not copied via copy-to-mate, nor do they trigger
a configuration mismatch in the CLI.
In the Web EMS, failure to synchronize these configuration settings causes a configuration mismatch alarm.
The following settings must be configured separately on the standby unit:
• Setting the Unit Name – in the Name field of the Unit Parameters page (see Configuring Unit Parameters).
• Disabling/enabling Radio TX-mute – in the TX mute field of the Edit Radio Parameters window. Refer
to Configuring the Radio Parameters.
• Clearing the Radio and RMON counters – in the TX mute field of the Counters Page. Refer to Displaying and
Clearing Defective Block Counters.
• Setting the activation key configuration – in the Activation Key and Demo admin fields of the Figure 21
Activation Key Overview Page (see Configuring the Activation Key).
• Defining user accounts – Refer to the Access Control User Accounts Page (see Configuring Users).

Phn 3963 013v000

Page 252
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

• Setting synchronization settings – Refer to the SyncE Regenerator page (see Configuring the SyncE
Regenerator).

Viewing Link and Protection Status and Activity

You can view link and protection status and activity any time.
To view link and protection status and activity:
1. Select Platform > Management > Unit Redundancy. The Unit Redundancy (HSB Protection) page opens.

Figure 159 Unit Redundancy Page

The following information is displayed:

• Protection Operational State – Indicates whether HSB protection is functional (available in practice). Radio
protection is not functional if any of the following occurred:
o MIMO is configured.
o The management connection to the mate is down.
• Protection Activity – The activity state of the device: Active or Standby.
• Protection Link to Mate – Indicates whether the two units (the Active and the Standby) are physically
connected.
• Copy to mate status – Indicates the status of the last copy-to-mate operation
• Protection Admin – Indicates whether HSB protection is enabled or disabled.
• Lockout – Indicates whether lockout is enabled or disabled.

Manually Switching to the Standby Unit

The following events trigger switchover for HSB radio protection according to their priority, with the highest
priority triggers listed first.
1 Loss of active unit
2 Lockout

Phn 3963 013v000

Page 253
Chapter 3: Configuration Guide Configuring Unit Protection with HSB Radio Protection
(External Protection)

3 Radio/Ethernet interface failure

4 Manual switch
At any point, you can manually switch to the Standby unit, provided that the highest protection fault level in the
Standby unit is no higher than the highest protection fault level on the Active unit.
To manually switchover to the Standby unit:
1. Select Platform > Management > Unit Redundancy. The Unit Redundancy (HSB Protection) page opens.
2. Click Manual Switch.
3. Confirm the action in the confirmation window that appears.

Disabling Automatic Switchover to the Standby Unit

At any point, you can perform lockout, which disables automatic switchover to the standby unit.
To disable automatic switchover to the Standby unit:
1. Select Platform > Management > Unit Redundancy. The Unit Redundancy (HSB Protection) page opens.
2. Select On in the Lockout field.
3. Click Apply.
To re-enable automatic switchover, select Off in the Lockout field and then click Apply.

Disabling Unit Protection

You can disable unit protection at any time. If you disable unit protection, keep in mind that while the unit that
was formerly the active unit maintains its IP address, the unit that was formerly the standby unit is assigned the
default IP address (192.168.1.1)
To disable protection:
1. Select Platform > Management > Unit Redundancy. The Unit Redundancy (HSB Protection) page opens.
2. Select Disable in the Protection Admin field.
3. Click Apply.

Phn 3963 013v000

Page 254
Chapter 3: Configuration Guide Configuring 1 + 1 HSB with Space Diversity

Configuring 1 + 1 HSB with Space Diversity

Note
This feature is only relevant to PTP 820C. it can be used with all PTP 820 hardware versions.

A 1+1 HSB-SD configuration utilizes two PTP 820C units on each side of the link, with both radio carriers activated.
The PTP 820C units are combined and connected to the primary and diversity antennas via a dual coupler and two
flexible waveguides.
Radio carrier 2 is muted on each unit. On the receiving side, the signals are combined in the active unit to produce
a single, optimized signal. The link is protected via external protection, so that if a protection switchover occurs,
the standby unit becomes the active unit, and the link continues to function with full space diversity.
To configure a 1+1 HSB link with Space Diversity:
1. For one PTP 820 unit, select radio > Groups > Diversity. The Diversity page opens.
2. Click Create Group. The Create Diversity Group page opens.

Figure 160 Create Space Diversity Group- Page 1.

3. In the Group Type Field, select 1+0 Space Diversity.

4. Click Next. The Selection Summary page opens.

Phn 3963 013v000

Page 255
Chapter 3: Configuration Guide Configuring 1 + 1 HSB with Space Diversity

Figure 161 Create Space Diversity Group- Selection Summary

4. Click Submit to create the Diversity group.

5. In the Diversity page, select the group you just created and click Edit Group. The Diversity - Edit page
opens

Figure 162 Diversity - Edit Page (Space Diversity Group)

8. In the Admin State field, select Enable

9. Click Apply.
10. Repeat Steps 1 through 9 for the second unit.

Phn 3963 013v000

Page 256
Chapter 3: Configuration Guide Configuring 1 + 1 HSB with Space Diversity

Note
The identity of the active and standby units is not determined until unit protection is configured.

11. Configure Unit Protection, according to the instructions in Configuring Unit Protection with HSB Radio
Protection (External Protection).
12. On the active PTP 820 unit, mute the transmitter of radio carrier 2. For instructions, see configuring the radio
parameters.
13. Perform Copy to Mate. See Step 5 in configuring HSB Radio Protection.

Note
It is crucial to ensure that the port connected to the Diversity antenna is muted in each PTP 820 unit.
If you perform Copy to Mate after configuring unit protection, as indicated above, the mute
configuration will be copied to the standby unit. If you mute the interface before configuring unit
protection, you must make sure to manually mute the interface on both PTP 820 units. Otherwise,
configuring unit protection will override the mute configuration.

Phn 3963 013v000

Page 257
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Configuring MIMO and Space Diversity

Note
This feature is only relevant for PTP 820C units.

This section describes how to configure MIMO and space diversity, and include the following topics:
• MIMO and Space Diversity Overview
• Configuring a MIMO Link
• Creating a MIMO or Space Diversity Group
• Enabling/Disabling a MIMO or Space Diversity Group
• Setting the Role of a MIMO or Space Diversity Group
• Resetting MIMO
• Viewing MMI and XPI Levels
• Deleting a MIMO or Space Diversity Group

MIMO and Space Diversity Overview

Note
MIMO and Space Diversity are not supported with ATPC. ATPC must be
disabled before configuring ASD. See Configuring ATPC and ATPC Override Timer.

Line-of-Sight (LoS) Multiple Input Multiple Output (MIMO) achieves spatial multiplexing by creating an artificial
phase de-correlation by deliberate antenna distance at each site in deterministic constant distance. At each site in
a LoS MIMO configuration, data to be transmitted over the radio link is split into two bit streams (MIMO 2x2) or
four bit streams (MIMO 4x4). These bit streams are transmitted via two antennas. In MIMO 2x2, the antennas use
a single polarization. In MIMO 4x4, each antenna uses dual polarization. The phase difference caused by the
antenna separation enables the receiver to distinguish between the streams.
PTP 820C supports both MIMO 2x2 and MIMO 4x4. For a full explanation of MIMO support in PTP 820C, refer to
the PTP 820C Technical Description.
For 4x4 MIMO using an external switch operating in LAG mode, Mate Management Access enables users to
manage both units via in-band management. See Mate Management Access (IP Forwarding) (CLI).
For PTP 820C 2E2SX hardware models, if you try to apply a 4x4 MIMO or 2+2 Space Diversity configuration while
P4 is assigned one or more service points, ASP or LLF instances, or a LAG group or Sync source is configured on P4,
the configuration will fail and an error message will be generated. Also, the Admin status of the port must be set to
Down before applying the 4x4 MIMO or 2+2 Space Diversity configuration. See Enabling the Interfaces (Interface
Manager).

Phn 3963 013v000

Page 258
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

The same hardware configurations can also be used to implement BBS Space Diversity. PTP 820C supports 1+0, 2+0
and 2+2 Space Diversity. For a full explanation of Space Diversity support in PTP 820C, refer to the PTP 820C
Technical Description.

Note
Only one MIMO or Space Diversity group can be created per PTP 820C unit. All MRMC scripts that
support MIMO also support Space Diversity.

2+2 Space Diversity (CLI)

2+2 HSB Space Diversity provides both equipment protection and signal protection. If one unit goes out of service,
the other unit takes over and maintains the link until the other unit is restored to service and Space Diversity
operation resumes.
2+2 HSB Space Diversity utilizes two PTP 820C units operating in dual core mode. In each PTP 820C unit, both radio
carriers are connected to a single antenna. One optical GbE port on each PTP 820C is connected to an optical
splitter. Traffic must be routed to an optical GbE port on each PTP 820C unit.
In effect, a 2+2 HSB configuration is a protected 2+0 Space Diversity configuration. Each PTP 820C monitors both of
its cores. If the active PTP 820C detects a radio failure in either of its cores, it initiates a switchover to the standby
PTP 820C.

Notes: Only one MIMO or Space Diversity group can be created per PTP 820C or PTP 820C-HP
unit. All MRMC scripts that support MIMO also support Space Diversity.
For 4x4 MIMO links, versions 10.5 and higher are not interoperable with earlier versions. If you
are upgrading from an earlier version with an existing 4x4 MIMO link, you must follow the
procedure in Upgrading a 4x4 MIMO Link from an Earlier Version to release 10.5 or Higher.

Upgrading a 4x4 MIMO Link from an Earlier Version to Release

10.5 or Higher
For 4x4 MIMO links, software versions 10.5 and higher are not interoperable with earlier software versions. When
upgrading from a software version prior to release 10.5 to release 10.5 or higher, if there is an existing 4x4 MIMO
link, you must perform either of the following procedures to properly upgrade the link. Option 1 is the preferred
option.

Important Note: You must download the new software package to all four units before beginning
the upgrade process. All four units in the 4x4 MIMO link must use the same Release build and
version.
Upgrade Procedure – Option 1
1. Upgrade the remote Slave unit.
2. Upgrade the remote Master unit.
3. Upgrade the local Slave unit.

Phn 3963 013v000

Page 259
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

4. Upgrade the local Master unit.

Upgrade Procedure – Option 2
1. Upgrade the remote Master unit.
2. Upgrade the local Slave unit.
3. Upgrade the local Master unit.
4. Wait for the link to be restored between the Master units.
5. Mute both radio carriers on the remote Slave unit.
6. Upgrade the remote Slave unit.
7. Unmute both radio carriers on the remote Slave unit.

Configuring a 4x4 MIMO Link

To configure a 4x4 MIMO link, you must perform the following steps:
1. If you are configuring a 4x4 MIMO link, verify that the following three cables are connected between the
Master and Slave PTP 820C units on each side of the link. For details, refer to the PTP 820C Installation
Guide:
o Source sharing cable between both EXT REF PTP 820C radio connectors.
o MIMO data sharing cable between both PTP 820C ETH3/EXT ports.
o MIMO signaling cable between both PTP 820C MGT/PROT ports.
2. If you are configuring a 4x4 MIMO link, you must initially configure the PTP 820C carriers as XPIC links, using
XPIC scripts, and configuring the carriers as XPIC groups. See Configuring XPIC.
3. Perform antenna alignment for XPIC. See Performing Antenna Alignment for XPIC.
4. Configure MIMO groups on each PTP 820C unit. See Creating a MIMO or Space Diversity Group.
5. If you are configuring a 4x4 MIMO link, configure the groups in the following order:
i Upper unit (Master) on the local side of the link.
ii Upper unit (Master) on the remote side of the link.
iii Lower unit (Slave) on the local side of the link.
iv Lower unit (Slave) on the remote side of the link.
To configure a 4x4 MIMO group:
i Select Radio > Groups> AMCC. The Advanced Multi Carrier Configuration page opens.

Phn 3963 013v000

Page 260
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Figure 163: Advanced Multi Carrier Configuration Page

ii Click Create Group. The AMCC Group – Select Group Parameters page opens.

Figure 164: 4x4 MIMO Group – Select Group Parameters Page

iii In the Group Type field, select MIMO 4X4.

iv In the Group Admin Status field, select Enable.
v Click Next. The AMCC Group – Select Members Parameters page opens.

Phn 3963 013v000

Page 261
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Figure 165: 4x4 MIMO Group – Select Members Parameters Page

vi In the Member #1 field, select one of the radio carriers.

vii In the Member Role field, select MIMO Master if the unit is the Master unit, or MIMO Slave if the unit is
the Slave unit.

Phn 3963 013v000

Page 262
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

viii Click Next. The AMCC Group – Select MRMC Parameters page opens.

Figure 166: 4x4 MIMO Group – Select MRMC Parameters Page

ix Select Set MRMC Script, and configure the Script ID, Operational mode, Maximum profile, and Minimum
profile. For an explanation of these fields, see Configuring the Radio (MRMC) Script(s). Make sure the script
you select supports MIMO.
Notes:
For a list of available scripts, including an indication of which scripts support MIMO, refer to
the Release Notes for the release you are using.

Phn 3963 013v000

Page 263
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

x Click Finish. The AMCC Group – Selection Summary page opens. Note that the second radio
carrier is automatically added to the group, with the same Member Role and MRMC script as
you defined for the first radio carrier you added to the group.

Figure 167: 4x4 MIMO Group – Select Members Parameters Page

xi Click Submit to configure the group. If you changed the MRMC script from the script that had previously
been configured, or if you set the Group Admin Status to Enable, the unit is reset.

Phn 3963 013v000

Page 264
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Figure 168: Advanced Multi Carrier Configuration Page (Populated – 4x4 MIMO Group)

1 Verify that the MMI levels are appropriate. See Viewing MMI Levels.
2 Configure LAG on the two Ethernet ports of the external switches connected to the PTP 820 units on both sides
of the link.
3 Configure Automatic State Propagation with ASP trigger by remote fault enabled on the MIMO group in all
four PTP 820 units that make up the link. See Configuring Automatic State Propagation and Link Loss
Forwarding.
Note: The last two steps are crucial to ensure that the link continues to function via the
MIMO resiliency mechanism in the event of a hardware failure scenario.
4x4 MIMO link.

Figure 169: 4x4 MIMO Configuration

EXT REF

Eth1
Carrier 1

GbE Port
Source Eth3/
Carrier 2
OMT
EXT
Sharing Cable
MIMO
MGT/
Group ASP – Remote
PROT
Fault Trigger
MIMO Sharing Enabled
External Cable
Master IP-20
LAG
Switch
ASP – Remote
Eth1 Fault Trigger
Enabled
Carrier 1
Eth3/
GbE Port EXT
Carrier 2
OMT
MIMO Signaling
Cable MGT/ MIMO
PROT
Group

EXT REF

Slave IP-20

Phn 3963 013v000

Page 265
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Configuring a 2x2 MIMO Link

To configure a 2x2 MIMO link, you must perform the following steps:
1 Select Radio > Groups> Diversity. The Diversity Group page opens.
2 Click Create Group. The Diversity Groups page opens.

Figure 170: Create Diversity Group Page – 2x2 MIMO – Page 1

3 In the Group Type field, select MIMO 2x2.

4 Click Next. The Create Diversity Group page is updated and displays your system configuration.

Figure 171: Create Diversity Group Page – 2x2 MIMO – Page 2

5 Click Submit to create the 2x2 MIMO group.

Phn 3963 013v000

Page 266
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

6 After creating the group, you must enable the group in the MIMO - Edit page:
i From the MIMO page, select the group from the table and click Edit Group. The MIMO - Edit page opens

Figure 172: Diversity Groups – 2x2 MIMO - Edit Page

ii In the Admin state field, select Enable.

iii Click Apply.
7 In the Role field, leave the setting Not-relevant.
8 Verify that the MMI levels are appropriate. See Viewing MMI Levels.

Phn 3963 013v000

Page 267
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Configuring a 1+0 or 2+2 Space Diversity Link

To create a Space Diversity group:
1 Select Radio > Groups> Diversity. The Diversity page opens.
2 Click Create Group. The Create Diversity Group page opens.

Figure 173: Create Diversity Group – Page 1

3 In the Group Type field, select one of the following according to your desired system configuration:
◦ 1+0 Space Diversity
◦ 2+0 Space Diversity
4 Click Next. The Create Diversity Group page is updated and displays your system configuration.

Figure 174: Create Diversity Group – Page 2

5 Click Submit to create the Diversity group.

Phn 3963 013v000

Page 268
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

6 After creating the group, you must enable the group and, for 2+0 groups, set the unit’s role (Master or Slave) in
the Diversity - Edit page.
i From the Diversity page, select the group from the table and click Edit Group. The Diversity - Edit page
opens.

Figure 175: Diversity - Edit Page

ii In the Admin state field, select Enable.

iii In the Role field:
◦ For 1+0 Space Diversity groups, leave the setting Not-relevant.
◦ For 2+2 Space Diversity groups, set the role of the group
to Master or Slave.
iv Click Apply.

Viewing MMI Levels

You can view MMI and XPI levels for the individual radio carriers in a MIMO group.
Note that the MMI value can also be calculated manually. To calculate it manually, you must measure the
following RSL levels per receiver:
1. Mute all remote transmitters except the transmitter for the link you want to measure, and measure the local
RSL level (RSL_Wanted).

Phn 3963 013v000

Page 269
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

2. Mute all remote transmitters except the same polarization interferer and measure the local RSL2 (RSL_Int).
The MMI is equal to RSL_Wanted – RSL_Int
To view MMI Levels for a 4x4 MIMO group:
1 Select Radio > Groups> AMCC. The Advanced Multi Carrier Configuration page opens.
2 Select the 4x4 MIMO group from the table.
3 Click Edit Members. The AMCC Group - Edit Members page opens.

Figure 176: 4x4 MIMO - Edit Members Page

To view MMI Levels for a 2x2 MIMO group:

1 Select Radio > Groups> Diversity. The Diversity Groups page opens.
2 Select the 2x2 MIMO group from the table.
3 Click Edit Members. The Diversity Groups - Edit Members page opens.

Figure 177: Diversity Groups - Edit Members Page

The MIMO - Edit Members page provides the following information for each radio carrier in the MIMO group:
• MMI – MIMO Mate Interference. MMI represents the difference between the RSL1 and the RSL2 of the
remote Master and Slave transmitters with the same polarization. The nominal range is 0. The range should be
from -3 dB to +3 dB.
This parameter is not relevant for 1+0 Space Diversity (as indicated by a value of -99).

Phn 3963 013v000

Page 270
Chapter 3: Configuration Guide Configuring MIMO and Space Diversity

Deleting a MIMO or Space Diversity Group

You can delete a MIMO or Space Diversity Group.
To delete a MIMO or Space Diversity Group:
1. Before deleting a MIMO or Space Diversity group, you must disable the group. To disable the group, set the
Admin State to Disable in the MIMO - Edit Page.

Note
When the MIMO or Space Diversity group is disabled, the system is automatically reset.

2. Select a MIMO group from the table.

3. Click Delete. The Delete MIMO confirmation page opens.
4. Confirm the operation.

Phn 3963 013v000

Page 271
 Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

Configuring Advanced Space Diversity (ASD)

Note
This feature is only relevant for PTP 820C and PTP 820C-HP.

This section describes how to configure Advanced Space Diversity (ASD), and includes the following topics:
• ASD Overview
• Configuring an ASD Link
• Viewing ASD Status
• Deleting an ASD Group

ASD Overview
ASD uses a combination of BBC Space Diversity and beam forming technology to increase system gain and reduce
the effects of fading and multipath. ASD is implemented as an asymmetrical link with three antennas and three
PTP 820C or PTP 820C-HP units, as shown in Error! Reference source not found..
• In one direction, two transmitters transmit to one receiver. ASD increases system gain in this direction by
6 dB.
• In the other direction, transmissions from one transmitter are received by two receivers. This is a simple
case of Space Diversity, and provides a 3 dB increase in system gain.

Figure 178 Advanced Space Diversity (ASD)

Master Master
Network RF Network
Switch Eth Port
Processor
Modem 1
Chain V +6dB V RF Chain Modem 1
Processor Eth Port Switch
OMT f1 f1 OMT
Modem 2 RF Chain H H RF Chain Modem 2
+3dB
Communications

Source Sharing
Data Sharing
Protection

Network
Processor
Modem 1 RF Chain V
OMT f1
Modem 2 RF Chain H

Slave

The ability to implement space diversity with only three PTP 820 units and three antennas is made possible by the
use of standard space diversity in one direction and a phase-synchronized beam-forming mechanism in the other
direction. Each PTP 820C or PTP 820C-HP unit is installed in a 2+0 XPIC configuration, with an OMT as the
mediation device and a dual-polarization antenna. Alignment is performed using an XPIC script. Following
alignment, the ASD groups are configured and a special ASD script (28 MHz or 56 MHz) is applied to each of the
three ASD groups.
• MRMC Script 1951 – 28 MHz

Phn 3963 013v000

Page 272
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

• MRMC Script 1953 – 56 MHz

Error! Reference source not found. shows the data paths between Site 1, with two PTP 820C or PTP 820C-HP units
and two antennas, and Site 2, with one PTP 820C or PTP 820C-HP unit and one antenna.

Figure 179 ASD Data Paths

Site 1 Site 2
+3dB +6dB
f1 f1

f1

The data path from Site 1 to Site 2 includes the same TX signals being sent from the main and diversity radios at
Site 1 (RX diversity). PTP 820 uses beam forming technology to achieve optimal reception by the PTP 820C or PTP
820C-HP unit at Site 2. This quadruples the signal’s strength, adding 6dB in system gain and resilience to selective
fading.
The data path from Site 2 to Site 1 is similar to that of a standard space diversity configuration. The signal
transmitted from Site 2 is received by the main and diversity antennas at Site 1 (RX diversity). These signals are
combined using Baseband Combining (BBC). This adds 3dB in system gain since the signal practically doubles its
level as it is received in a phase-synchronized manner by two receivers.

Phn 3963 013v000

Page 273
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

ASD Failure Scenarios

In the event of hardware failure on a Slave unit, the link continues to function in Master-only configuration.
In the event of hardware failure on a Master unit, the link ceases to function until the failure is rectified.
To restore full ASD operation, the faulty equipment must be replaced. The replacement equipment must be pre-
configured to the same configuration as the equipment being replaced. Once the new equipment has been
properly installed and, if necessary, powered up, the system automatically reverts to full ASD operation, with no
user intervention required.

Configuring an ASD Link

Note
ASD is not supported with ATPC and XPIC. ATPC and XPIC must both be disabled before configuring
ASD.

To configure an ASD link, you must perform the following steps:

1. Install the PTP 820C or PTP 820C-HP units as follows:
a. At Site 1, install two PTP 820C/PTP 820C-HP units in a 4x4 MIMO configuration.
b. At Site 2, install one PTP 820C/PTP 820C-HP unit in a 2+0 Dual Polarization (XPIC) configuration.
For instructions, refer to the Installation Manual for PTP 820C or PTP 820C-HP.
2. Verify that the Ethernet interfaces on the Slave unit are set to Admin = Down in the Interface Manager.
See Enabling the Interfaces (Interface Manager).
3. Configure the radio parameters for each of the six radio carriers in the link. Make sure each carrier is
configured with the same radio parameters. See Configuring the Radio Parameters.
4. Assign an ASD script to each of the six radio carriers in the link. Options are:
• MRMC Script 1951 (28/30 MHz)
• MRMC Script 1953 (56/60 MHz)

Note
Make sure to set the same MRMC parameters for all the radio carriers in the ASD link. For ASD, the
scripts must be set to Adaptive mode.
5. Mute both carriers on the Slave unit. See Configuring the Radio Parameters.
6. Align the antenna of the Master unit to the antenna at Site 2 until you achieve a steady link at the RSL that
is expected according to the site plan, at 2048 QAM.
7. Unmute the carriers of the Slave unit and mute both carriers on the Master unit. See Configuring the
Radio Parameters.
8. Align the antenna of the Slave unit to the antenna at Site 2 until you achieve a steady link at the RSL that
is expected according to the site plan, at 2048 QAM.
9. Unmute the carriers of the Master unit. At this point, all of the carriers in the ASD link should be unmuted.
10. Configure ASD on each unit:
a. Select Radio > Groups> AMCC. The Advanced Multi Carrier Configuration page opens.

Phn 3963 013v000

Page 274
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

Figure 180 Advanced Multi Carrier Configuration Page

b. Click Create Group. The AMCC Group – Select Group Parameters page opens.

Figure 181 AMCC Group - Select Group Parameters Page

c. In the Group Type field:

• At Site 1 (two units), select Dual ASD.
• At Site 1 (one unit), select Single ASD.

Phn 3963 013v000

Page 275
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

Note
After you select one of the ASD options in the Group Type field, ASD 2+0 will be displayed in the
Group Subtype field.
d. In the Group Admin Status field, select Enable.
e. Click Next. The next page of the AMCC Group – Select Members Parameters page opens.

Figure 182 AMCC Group - Select Members Parameters Page

f. In the Member Role field for Member #1:

• For the Master unit at Site 1 (two units), select Master. The Member Role for Member
#2 is automatically set to Master.
• For the Slave unit at Site 1, select Slave. The Member Role for Member #2 is
automatically set to Slave.
• For the unit at Site 2, select Master. The Member Role for Member #2 is automatically
set to Master.
g. Click Next. The AMCC Group – Select MRMC Parameters page opens.

Phn 3963 013v000

Page 276
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

Figure 183 AMCC Group - Select MRMC Parameters Page

h. In the Script ID field:

• MRMC Script 1951 (28/30 MHz)
• MRMC Script 1953 (56/60 MHz)
i. In the Operational Mode field, select Adaptive.
j. Select the maximum and minimum ACM profiles in the Maximum profile and the Minimum
profile fields.

Note
Make sure to set the same MRMC parameters for all the radio carriers in the ASD link. Refer to
Configuring the Radio (MRMC) Script(s) for a list of available radio profiles.

Phn 3963 013v000

Page 277
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

k. Click Finish. The AMCC Group – Selection Summary page opens.

l. Click Submit. The group is created.

Figure 184 Advanced Multi Carrier Configuration Page – Populated with ASD Group

Note
No unit reset takes place when the group is created.

Viewing ASD Status

To view ASD status:
1. Select Radio > Groups > AMCC. The Advanced Multi Carrier Configuration page opens (Error! Reference
source not found.).
2. Select a group and click View Members. The AMCC – ASD – Radio Members page opens.

Figure 185 AMCC – ASD – Radio Members Page

The Operational State field displays one of the following statuses:

• Idle – All units are operational.

Phn 3963 013v000

Page 278
Chapter 3: Configuration Guide Configuring Advanced Space Diversity (ASD)

• Master Only – The Slave unit is not operational.

• ASD Configuration not supported – The link has been misconfigured. Make sure that each radio carrier is
configured with the same radio parameters and MRMC scripts and parameters.
The Combined Status field indicates the status of the ASD group’s received radio signal:
• Combined – Only relevant for the Master unit at the dual-unit side of the link. ASD is functioning to
produce a combined radio signal.
• Main Only – Only relevant for Master units. Only the main path signal is being received.
• Diversity Only – Only relevant for Slave units and the Master unit at the single-unit side of the link. Only
the diversity path is providing a usable signal.
• N/A – No adequate signal is being received, either because of an LOF condition or misconfiguration of the
link.

Deleting an ASD Group

To delete an ASD group, you must perform the following steps:
1 Select Radio > Groups> AMCC. The Advanced Multi Carrier Configuration page opens.
2 Select the group and click Edit. The AMCC Group Edit page opens.

3 In the Group Admin Status field, select Disable, then Apply. At this point, a system reset takes place.
4 Once the unit comes back online, return to the Advanced Multi Carrier Configuration page opens, select the
group, and click Delete. The group is deleted.

Phn 3963 013v000

Page 279
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

Configuring Advanced Frequency Reuse (AFR)

AFR Overview
AFR works in conjunction with ACM to enable links to achieve high modulations and high capacities despite the
presence of adjacent links transmitting at the same frequency. By mitigating the effects of side lobe interference
(SLI) completely, or nearly completely, AFR can reduce adjacent link interference to levels that enable links that
would otherwise be limited to QPSK modulation to transmit at modulations of up to 2048 QAM. This enables the
placement of links that would otherwise be impractical due to high interference.
In an AFR 1+0 configuration, a dual-modem PTP 820C unit is deployed at the hub site and two PTP 820C or PTP
820S units are deployed in two tail sites. Each carrier at the hub site is known as an “aggregator.”
The hub site utilizes a single PTP 820C unit with two radio carriers. Each carrier is in a link, via its own directional
antenna, with a tail site that consists of a PTP 820C or PTP 820S unit.
One hub site cannot have more than two tail sites. Also, a hub site cannot be a tail site for another AFR hub site.

Note
The links should be located so as to ensure that the two data streams do not cross.

Figure 186 AFR 1+0 Deployment

For information about planning links with AFR, contact Cambium support.

Initial Link Configuration and Alignment for AFR

AFR 1+0 requires the following hardware configurations:

Phn 3963 013v000

Page 280
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

• Hub Site – Install a single PTP 820C unit with two antennas using a PTP 820C Dual Core kit, as described in
Section 6.12 of the PTP 820C Installation Guide, 2x2 LoS MIMO Direct Mount.
• Tail Sites – Install a 1+0 PTP 820C or PTP 820S configuration.
Before performing the software configuration for AFR, you must set up and align the two links as individual 1+0
links. Use Script 1801 for the alignment, but do not enable AFR before aligning the links.
When aligning Link A, mute both sides of Link B. When you are finished aligning Link A, mute both sides of Link A,
unmute both sides of Link B, and align link B. When you are finished aligning Link B, unmute both sides of both
links.

Figure 187 AFR 1+0 Configuration

Software Configuration for AFR

Note
AFR is not supported with ATPC. ATPC should be disabled before configuring AFR. See Configuring
ATPC and ATPC Override Timer.

Perform the following steps for each site in the AFR configuration.
• If you are performing the configuration locally at the Hub site and each Tail site, the order in which you
configure the sites does not matter.
• If you are performing the configuration for all three sites remotely from the Hub Site, you must configure the
sites in the following order:
o Tail Site 1
o Tail Site 2
o Hub Site
After you configure AFR on the Tails Sites, the link between the Hub Site and the Tail Sites will be lost. The links will
be restored after you configure AFR on the Hub site and the Hub site comes back up after unit reset.

Phn 3963 013v000

Page 281
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

6. Select Radio > Groups > AMCC. The Advanced Multi Carrier Configuration page opens.

Figure 188 Advanced Multi Carrier Configuration Page (Empty)

1 Click Create Group. The AMCC Group – Select Group Parameters page opens.

Figure 189 AMCC Group – Select Group Parameters Page

2 In the Group type field, select one of the following:

o If you are configuring the Hub site, select AFR Aggregate.
o If you are configuring a Tail site, select AFR Tail.

Phn 3963 013v000

Page 282
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

3 In the Group admin status field, select Enable.

4 Click Next. The AMCC Group – Select Members Parameters page opens.

Figure 190 AMCC Group – Select Group Parameters Page (Hub Site)

Phn 3963 013v000

Page 283
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

Figure 191 AMCC Group – Select Group Parameters Page (Tail Site)

5 In the Member #1 field, select a radio interface.

6 In the Member role field, select the role of the interface in the AFR 1+0 configuration:
o If you are configuring the Hub site, select Aggregate #1 or Aggregate #2.
o If you are configuring the Tail site, select Tail #1 or Tail #2.
Make sure the interface you configure as Aggregate #1 is part of the link with Tail #1 and that the interface you
configure as Aggregate #2 is part of the link with Tail #2.
7 Select Set MRMC Script (1801).

Note
Script 1801 is a 28/30 MHz script, with a maximum ACM profile of 10 (2048 QAM). For additional
details, refer to the relevant Release Notes or product Technical Description.

8 In the MRMC Script maximum profile field, select the maximum ACM profile for the links.
9 Click Finish. This page displays the parameters you have selected for the link.

Phn 3963 013v000

Page 284
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

Figure 192 AMCC Group – Selection Summary Page

10 Click Submit. The unit is automatically reset. Once AFR has been configured on the Hub site and both Tail sites,
the configuration is complete.

Deleting an AFR Group

If you want to disable AFR and convert the two links into non-AFR links, you must perform the following steps for
each site in the AFR configuration. If you are managing the links by in-band management from the hub site, you
must disable AFR at the tail sites first, then disable AFR at the hub site. Once AFR has been disabled at all of the
sites, you can delete the AFR groups in any order.
1 Select Radio > Groups > AMCC. The Advanced Multi Carrier Configuration page opens.

Phn 3963 013v000

Page 285
Chapter 3: Configuration Guide Configuring Advanced Frequency Reuse (AFR)

Figure 193 Advanced Multi Carrier Configuration Page (Populated)

2 Select the group and click Edit Group. The AMCC Group – Edit page opens.

Figure 194 AMCC Group – Edit Page

3 In the Group admin status field, select Disable.

4 Click Apply, then Close. The unit is automatically reset.
5 In the Advanced Multi Carrier Configuration page, select the group and click Delete.
Once you have performed this procedure for the Hub site and both Tail sites, you can reconfigure the links
according to the new network plan.

Phn 3963 013v000

Page 286
Chapter 3: Configuration Guide Operating a PTP 820C or PTP 820C-HP in Single Radio Carrier
Mode

Operating a PTP 820C or PTP 820C-HP in Single

Radio Carrier Mode

If you wish to operate a PTP 820C unit in single radio carrier mode, you must perform the following steps:
1. Verify that XPIC is disabled. See Configuring XPIC.
2. Disable Multi-Carrier ABC, as described.
3. Disable one of the two radio interfaces, as described in Enabling the Interfaces (Interface Manager).
4. Mute the disabled radio interface, as described in Configuring the Radio Parameters.

Phn 3963 013v000

Page 287
Chapter 4: Unit Management Operating a PTP 820C or PTP 820C-HP in Single Radio Carrier
Mode

Chapter 4: Unit Management

This section includes:
• Defining the IP Protocol Version for Initiating Communications
• Configuring the Remote Unit’s IP Address
• Configuration SNMP
• Configuring Trap Managers
• Installing and Configuring an FTP or SFTP Server
• Configuring the Internal Ports for FTP or SFTP
• Upgrading the Software
• Backing Up and Restoring Configurations
• Setting the Unit to the Factory Default Configuration
• Performing a Hard (Cold) Reset
• Configuring Unit Parameters
• Configuring NTP
• Displaying Unit Inventory
Related topics:
• Setting the Time and Date (Optional)
• Enabling the Interfaces (Interface Manager)
• Uploading Unit Info
• Changing the Management IP Address

Phn 3963 013v000

Page 288
Chapter 4: Unit Management Defining the IP Protocol Version for Initiating Communications

Defining the IP Protocol Version for Initiating

Communications

You can specify which IP protocol the unit will use when initiating communications, such as downloading software,
sending traps, pinging, or exporting configurations. The options are IPv4 or IPv6.
To set the IP protocol version of the local unit:
1. Select Platform > Management > Networking > Local. The Local Networking Configuration page opens.
Figure 195 Local Networking Configuration Page

2. In the IP address Family field, select the IP protocol the unit will use when initiating communications. The options
are IPv4 or IPv6.

Phn 3963 013v000

Page 289
Chapter 4: Unit Management Configuring the Remote Unit’s IP Address

Configuring the Remote Unit’s IP Address

You can configure the IP address of a remote unit.

To configure the IP address of a remote unit:
1. Select Platform > Management > Networking > Remote. The Remote Networking Configuration page opens.
o For multi-carrier units, the Radio Parameters page initially displays a table as shown in
Figure 126.
o For single-carrier units, the page appears as shown in Figure 127.

Figure 196 Remote Networking Configuration Page – PTP 820C

Phn 3963 013v000

Page 290
Chapter 4: Unit Management Configuring the Remote Unit’s IP Address

Figure 197 Remote Networking Configuration Page – PTP 820S and PTP 820E

2. For multi-carrier units, select the carrier in the Radio table (see Figure 126) and click Edit. A separate Remote IP
Configuration page opens. The page is identical to the single-carrier page.

Phn 3963 013v000

Page 291
Chapter 4: Unit Management Configuring the Remote Unit’s IP Address

Figure 198 Remote IP Configuration Page Per Carrier – PTP 820C and PTP 820C-HP

3. In the Remote IP address field, enter an IP address for the remote unit. You can enter the address in IPv4 format
in this field, and/or in IPv6 format in the IPv6 Address field. The remote unit will receive communications
whether they are sent to its IPv4 address or its IPv6 address.
4. In the Remote Subnet mask field, enter the subnet mask of the remote radio.
5. Optionally, in the Remote default gateway field, enter the default gateway address for the remote radio.
6. Optionally, in the Remote IPv6 Address field, enter an IPv6 address for the remote unit. You can enter the
address in IPv6 format in this field, and/or in IPv4 format in the IP Address field. The unit will receive
communications whether they are sent to its IPv4 address or its IPv6 address.
7. If you entered an IPv6 address, enter the IPv6 prefix length in the Remote IPv6 Prefix-Length field.
8. Optionally, if you entered an IPv6 address, enter the default gateway in IPv6 format in the Remote default
Gateway IPv6 field.
9. Click Apply.

Changing the Subnet of the Remote IP Address

If you wish to change the Remote IP Address to a different subnet:
1. Change the address of the Remote Default Gateway to 0.0.0.0.
2. Click Apply.
3. Set the Remote IP Address as desired, and the Remote Default Gateway as desired.
Similarly, if you wish to change the Remote IPv6 Address to a different subnet:
1. Change the address of the Remote IPv6 Default Gateway to 0:0:0:0:0:0:0:0.
2. Click Apply.
3. Set the Remote IPv6 Address as desired, and the Remote IPv6 Default Gateway as desired.

Phn 3963 013v000

Page 292
Chapter 4: Unit Management Configuration SNMP

Configuration SNMP

PTP 820 products support SNMP v1, V2c, and v3. You can set community strings for access to PTP 820 units.
PTP 820 products support the following MIBs:
• RFC-1213 (MIB II).
• RMON MIB.
• Proprietary MIB.
Access to the unit is provided by making use of the community and context fields in SNMPv1 and SNMPv2c/SNMPv3,
respectively.
To configure SNMP:
1. Select Platform > Management > SNMP > SNMP Parameters. The SNMP Parameters page opens.
Figure 199 SNMP Parameters Page

2. In the Admin field, select Enable to enable SNMP monitoring, or Disable to disable SNMP monitoring.

Note
The Operational Status field indicates whether SNMP monitoring is currently active (Up) or inactive
(Down).

3. In the SNMP Read Community field, enter the community string for the SNMP read community.

Phn 3963 013v000

Page 293
Chapter 4: Unit Management Configuration SNMP

4. In the SNMP Write Community field, enter the community string for the SNMP write community
5. In the SNMP Trap Version field, select V1, V2, or V3 to specify the SNMP version.

Note
The SNMP MIB Version field displays the current SNMP MIB version the unit is using.

6. In the V1V2 Blocked field, select Yes if you want to block SNMPv1 and SNMPv2 access so that only SNMPv3
access will be enabled.

Note
Additional security parameters can be configured in the Quick
Configuration Security Protocols page. See Quick Security Configuration – Protocols Page, Step 4.

7. Click Apply.
If you are using SNMPv3, you must also configure SNMPv3 users. SNMPv3 security parameters are configured per
SNMPv3 user.
To add an SNMP user:
1. Select Platform > Management SNMP > V3 Users. The V3 Users page opens.

Figure 200 V3 Users Page

2. Click Add. The V3 Users - Add page opens.

Phn 3963 013v000

Page 294
 Chapter 4: Unit Management Configuration SNMP

Figure 201 V3 Users - Add Page

3. Configure the SNMP V3 Authentication parameters, as described below.

4. Click Apply, then Close.

Table 15 SNMP V3 Authentication Parameters

Parameter Definition

User Name Enter the SNMPv3 user name.

Password Enter a password for SNMPv3 authentication. The

password must be at least eight characters.

Authentication Algorithm Select an authentication algorithm for the user. Options

are:
• None
• SHA
• MD5

Encryption (Privacy) Mode Select an encryption (privacy) protocol for the user.
Options are:
• None
• DES
• AES

Access Mode Select an access permission level for the user. Options
are:
• Read Write User
• Read Only User

Phn 3963 013v000

Page 295
Chapter 4: Unit Management Configuring Trap Managers

Configuring Trap Managers

You can configure trap forwarding parameters by editing the Trap Managers table. Each line in the Trap Managers
table displays the setup for a manager defined in the system.
To configure trap managers:
1. Select Platform > Management SNMP > Trap Managers. The Trap Managers page opens.
Figure 202 Trap Managers Page

2. Select a trap manager and click Edit. The Trap Managers Edit page opens.

Phn 3963 013v000

Page 296
Chapter 4: Unit Management Configuring Trap Managers

Figure 203 Trap Managers - Edit Page

3. Configure the trap manager parameters, as described in Table 15 Trap Manager Parameters.
4. Click Apply, then Close.

Table 16 Trap Manager Parameters

Parameter Definition

IPv4 Address If the IP address family is configured to be IPv4, enter the destination IPv4
address. Traps will be sent to this IP address. See Defining the IP Protocol
Version for Initiating Communications.

IPv6 Address If the IP address family is configured to be IPv6, enter the destination IPv6
address. Traps will be sent to this IP address. See Defining the IP Protocol
Version for Initiating Communications.

Description • Enter a description of the trap manager (optional).

Admin • Select Enable or Disable to enable or disable the selected trap

manager.

Community • Enter the community string for the SNMP read community.

Port • Enter the number of the port through which traps will be sent.

Heartbeat Period • Enter the interval, in minutes, between each heartbeat trap.

CLLI • Enter a Common Language Location Identifier (CLLI). The CLLI is free
text that will be sent with the trap. You can enter up to 100
characters.

Phn 3963 013v000

Page 297
Chapter 4: Unit Management Configuring Trap Managers

Parameter Definition

V3 User Name If the SNMP Trap version selected in Figure 129 SNMP Parameters
Page page is V3, enter the name of a V3 user defined in the system.
To view or define a V3 user, use the Figure 130 V3 Users Page page.
Note: Make sure that an identical V3 user is also defined on the
manager's side.

Phn 3963 013v000

Page 298
Chapter 4: Unit Management Installing and Configuring an FTP or SFTP Server

Installing and Configuring an FTP or SFTP Server

Several tasks, such as software upgrade (except when performed using HTTP or HTTPS) and configuration backup,
export, and import, require the use of FTP or SFTP. The PTP 820 can function as an FTP or SFTP client. If you wish to
use FTP/SFTP, you must install FTP/SFTP server software on the PC or laptop you are using.

Note
For FTP, it is recommended to use FileZilla_Server software that can be downloaded from the web
(freeware).
For SFTP, it is recommended to use SolarWinds SFTP/SFCP server (freeware).
If you are using IPv6 to perform the operation, make sure to use FileZilla version 0.9.38 or higher to
ensure IPv6 support. If you are using another type of FTP or SFTP server, make sure the application
version supports IPv6.

To install and configure FTP or SFTP server software on the PC or laptop:

1. Create a user and (optional) password on the FTP/SFTP server. For example, in FileZilla Server, perform the
following:
From the Edit menu, select Users.
I. In the Users window, click Add.
II. In the Add user account window, enter a user name and click OK.
III. In the Users window, select Enable account and, optionally, select Password and enter a password.
IV. In the Users window, click OK.

Phn 3963 013v000

Page 299
Chapter 4: Unit Management Installing and Configuring an FTP or SFTP Server

Figure 204 FileZilla Server User Configuration

2. Create a shared FTP/SFTP folder on the PC or laptop you are using to perform the FTP/SFTP operation (for
example, C:\FTPServer).
3. In the FTP/SFTP server, set up the permissions for the shared FTP/SFTP folder. For example, in FileZilla Server:
I. From the Edit menu, select Users.
II. In the Users window, select Shared folders.
III. Underneath the Shared folders section, click Add and browse for your shared FTP folder.
IV. Select the folder and click OK.
V. In the Shared folders section, select your shared FTP folder.
VI. In the Files and Directories sections, select all of the permissions.
VII. Click Set as home directory to make the Shared folder the root directory for your FTP server
VIII. Click OK to close the Users window.

Phn 3963 013v000

Page 300
Chapter 4: Unit Management Installing and Configuring an FTP or SFTP Server

Figure 205 FileZilla Server Shared Folder Setup

Phn 3963 013v000

Page 301
Chapter 4: Unit Management Configuring the Internal Ports for FTP or SFTP

Configuring the Internal Ports for FTP or SFTP

By default, the following PTP 820 ports are used for FTP and SFTP when the PTP 820 unit is acting as an FTP or SFTP
client (e.g., software downloads, configuration file backup and restore operations):
• FTP – 21
• SFTP – 22
You can change either or both of these ports from the following pages:
• Platform > Management > Unit Info
• Platform > Software > Download & Install
• Platform > Configuration > Configuration Management
• Platform > Security > General > Security Log Upload
• Platform > Security > General > Configuration Log Upload
• Platform > Security > X.509 Certificate > CSR
• Platform > Security > X.509 Certificate > Download & Install
• Platform > Security > RSA Key
From any of these pages, click FTP Port. The FTP Port page opens.
Figure 206 FTP Port Page

Edit the File transfer port number for FTP and or SFTP and click Apply.

Phn 3963 013v000

Page 302
Chapter 4: Unit Management Upgrading the Software

Upgrading the Software

PTP 820 software and firmware releases are provided in a single bundle that includes software and firmware for all
components in the system. Software is first downloaded to the system, then installed. After installation, a reset is
automatically performed on all components whose software was upgraded.

Note
Make sure to use the original System Release software file, without any modification. Otherwise the
software download process will fail.

This section includes:

• Viewing Current Software Versions
• Software Upgrade Overview
• Downloading and Installing Software
• Configuring a Timed Installation

Viewing Current Software Versions

To display a list of software version running and downloaded on theunit:
1. Select Platform > Software > Versions. The Versions page opens. displays the following:
• Running Version – The software version currently run
• ning on the unit.
• Downloaded Version – The version, if any, that has been downloaded from the server but not yet installed. Upon
installation and reset, this version will become the Running Version.
2.
Figure 207 Versions Page

3. To display more detailed information about software component versions, select Show Detailed Information. The
Software Versions table opens in the Versions page. For a description of the information provided in the Software
Versions table, see Table 27: Software Versions Table Columns.

Phn 3963 013v000

Page 303
Chapter 4: Unit Management Upgrading the Software

Table 17 Versions Page Columns

Parameter Definition

Package Name The name of the software package.

Target Device The specific component on which the software runs.

Running Version The software version currently running on the component.

Downloaded Version The version, if any, that has been downloaded from the server but not yet
installed. Upon installation, this version will become the Installed Version.

Reset Type The level of reset required by the component in order for the Installed
Version to become the Active Version. A cold (hard) reset powers down
and powers back up the component. A warm (soft) reset simply reboots
the software or firmware in the component.

Software Upgrade Overview

The PTP 820 software installation process includes the following steps:
1. Download – The files required for the installation or upgrade are downloaded from a remote server.
2. Installation – The downloaded software and firmware files are installed in all modules and components of the
PTP 820 that are currently running an older version.
3. Reset – The PTP 820 is restarted in order to boot the new software and firmware versions.
Software and firmware releases are provided in a single bundle that includes software and firmware for all
components in the system. When you download a software bundle, the system verifies the validity of the bundle. The
system also compares the files in the bundle to the files currently installed in the PTP 820 and its components, so that
only files that need to be updated are actually downloaded. A message is displayed for each file that is actually
downloaded.

Phn 3963 013v000

Page 304
Chapter 4: Unit Management Upgrading the Software

Note
When downloading an older version, all files in the bundle may be downloaded, including files that
are already installed.

Software bundles can be downloaded via HTTP, HTTPS, FTP or SFTP. After the software download is complete, you
can initiate the installation.

Note
Before performing a software upgrade, it is important to verify that the system date and time are
correct. See Setting the Time and Date (Optional).
When upgrading a node with unit protection, upgrade the standby unit first, followed by the active
unit.

Downloading and Installing Software

Note
For HTTPS and SFTP downloads, be aware that only certain ciphers are supported in some operation
modes. For a list of supported ciphers, including an indication of which ciphers are supported in
HTTPS strong mode and FIPS mode, refer to Annex A – Supported Ciphers for Secured Communication
Protocols in the Release Notes for the product and version you are using.

You can download software using HTTP, HTTPS, FTP or SFTP.

When downloading software via HTTPS or HTTPS, the PTP 820 functions as the server, and you can download the
software directly to the PTP 820 unit.

Note
HTTP and HTTPS can only be used to download files for System release 9.5 and later. If there is a
requirement to downgrade from System release 9.5 or higher to an earlier version using HTTP or
HTTPS, contact Cambium Customer Support for assistance.

When downloading software via FTP or SFTP, the PTP 820 functions as an FTP or SFTP client. You must install FTP or
SFTP server software on the PC or laptop you are using to perform the software upgrade. For details, see Installing
and Configuring an FTP or SFTP Server.

Downloading Software Via HTTP or HTTPS

To download and install a new software version using HTTP or HTTPS:
1. Before performing a software upgrade, it is important to verify that the system date and time are correct. See
Setting the Time and Date (Optional).
2. In the PTP 820’s Web EMS, select Platform > Software > Download & Install. The Download & Install page opens.

Phn 3963 013v000

Page 305
Chapter 4: Unit Management Upgrading the Software

Figure 208 Download & Install Page – HTTP/ HTTPS Download – No File Selected

3. Select HTTP
4. Click Choose File. A browser window opens.
5. Navigate to the directory in which the software file is located and selected the file. The selected file must be a ZIP
file.
6. Click Open. The file name of the selected file appears in the File Name field.

Figure 209 Download & Install page – HTTP/ HTTPS Download – File Selected

7. Click Download. The download begins. You can view the status of the download in the Download Status field.

Note
To Discontinue the download process, Click Abort.

Phn 3963 013v000

Page 306
Chapter 4: Unit Management Upgrading the Software

8. Once the download has been completed, verify that the version you want to install has been downloaded. You
can check the downloaded version for each component by viewing the Downloaded Version column in the
Versions page. See Viewing Current Software versions.

Downloading Software Via FTP or SFTP

To download and install a new software version using FTP or SFTP:
1. Before performing a software upgrade, it is important to verify that the system date and time are correct. See
Setting the Time and Date (Optional).
2. Install and configure FTP or SFTP server software on the PC or laptop you are using to perform the software
upgrade, as described in Installing and Configuring an FTP or SFTP Server.
3. Unzip the new software package for PTP 820 into your shared FTP or SFTP folder.
4. In the PTP 820’s Web EMS, select Platform > Software > Download & Install. The Download & Install page opens.
5. Select FTP.
Figure 210 Download & Install Page - FTP

6. Click FTP Parameters to view the FTP Parameters page.

Phn 3963 013v000

Page 307
Chapter 4: Unit Management Upgrading the Software

Figure 211 FTP Parameters Page

7. In the File Transfer Protocol field, select the file transfer protocol you want to use (FTP or SFTP).
8. In the User name field, enter the user name you configured in the FTP server.
9. In the User password field, enter the password you configured in the FTP server. If you did not configure a
password for your FTP/SFTP user, simply leave this field blank.
10. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
FTP/SFTP server in the Server IPv4 address field. See Defining the IP Protocol Version for Initiating
Communications.
11. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
FTP/SFTP server in the Server IPv6 Address field. See Defining the IP Protocol Version for Initiating
Communications.
12. In the Path field, enter the directory path from which you are downloading the files. Enter the path relative to
the FTP user's home directory, not the absolute path. If the location is the home directory, it should be left
empty. If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is
"C:\", this parameter can be left empty or populated with "//".
13. Click Apply to save your settings, and Close to close the FTP Parameters page.

14. Click Download. The download begins. You can view the status of the download in the Download Status field of
the Download & Install page. See Table 17 Download & Install Status Parameters.
15. Once the download has been completed, verify that the version you want to install has been downloaded. You
can check the downloaded version for each component by viewing the Downloaded Version column in the
Versions page. See Viewing Current Software Versions.

Note
If upgrading from version 7.9 or earlier:
Before you proceed to install the software, repeat the download process even if Download Success is
displayed in the Download status field, until the unit displays the message No new software modules
found.
In case of failure, wait at least 30 minutes and repeat the software download.

Phn 3963 013v000

Page 308
Chapter 4: Unit Management Upgrading the Software

Installing Software
Note
For Instructions on how to configure a timed installation, see Configuring a Timed Installation.

To Install software:
1. Download the software version you want to install. See Downloading and installing Software.
2. Select Platform > Software > Download & Install. The Download & Install page opens. (Figure 140).
3. Click Install. The installation begins. You can view the status of the installation in the Download & Install - Status
Parameters section of the Download & Install Download & Install page. See Table 17 Download & Install Status
Parameters.
Upon completion of the installation, the system performs an automatic reset.

Note
• DO NOT reboot the unit during the software installation process. As soon as the process is
successfully completed, the unit will reboot itself.
• Sometimes the installation process can take up to 30 minutes.
• Only in the event that software installation was not successfully finished and more than 30
minutes have passed can the unit be rebooted..

Phn 3963 013v000

Page 309
Chapter 4: Unit Management Upgrading the Software

Table 18 Download & Install Status Parameters

Parameter Definition

Download status The status of any pending software download. Possible values are:
• Ready – The default value, which appears when no download is in progress.
• Verifying download files – The system is verifying the files to be downloaded.
• Download in progress – The download files have been verified, and the
download is in progress.
If an error occurs during the download, an appropriate error message is displayed
in this field.
When the download is complete, one of the following status indications appears:
• Download Success
• Download Failure
• All components already found in the system
When the system is reset, the Download Status returns to Ready.

Download progress Displays the progress of the current software download.

Install status The status of any pending software installation. Possible values are:
• Ready – The default value, which appears when no installation is in progress.
• Verifying installation files – The system is verifying the files to be installed.
• Installation in progress – The installation files have been verified, and the
installation is in progress.
If an error occurs during the installation, an appropriate error message is displayed
in this field.
When the installation is complete, one of the following status indications appears:
• Installation Success
• Installation Partial Success
• Installation Failure
• incomplete-sw-version
When the system is reset, the Installation Status returns to Ready.

Install progress Displays the progress of the current software installation.

Configuring a Timed Installation

You can schedule a timed (deferred) software installation to take place at any time within 24 hours after you
configure the installation.
To schedule a timed software installation:
1. Download the software version you want to install. See Downloading and Installing Software.
2. Select Platform > Software > Download & Install. The Download & Install page opens.
3. Click Install Parameters. The Install Parameters page opens.

Phn 3963 013v000

Page 310
Chapter 4: Unit Management Upgrading the Software

Figure 212 Install parameters Page.

4. Select Yes in the Timed Installation field.

5. Click Apply. The Software Management timer field appears.

Figure 213 Install parameters page- Software Management Timer.

6. In the Software management timer field, enter the amount of time, in hours and minutes, you want to defer the
installation. For example, inFigure 116, the timer is set for two hours after the timer was configured (02:00).

7. Click Apply, then Close to close the Install Parameters page.

Phn 3963 013v000

Page 311
Chapter 4: Unit Management Backing Up and Restoring Configurations

Backing Up and Restoring Configurations

You can import and export PTP 820 configuration files. This enables you to copy the system configuration to multiple
PTP 820 units. You can also backup and save configuration files.
Configuration files can only be copied between units of the same type, i.e., PTP 820C to PTP 820C, PTP 820C-HP
to PTP 820C-HP, PTP 820E to PTP 820E and PTP 820S to PTP 820S.
This section includes:
• Configuration Management Overview
• Viewing Current Backup Files
• Setting the Configuration Management Parameters
• Exporting a Configuration File
• Importing a Configuration File
• Deleting a Configuration File
• Backing Up the Current Configuration
• Restoring a Saved Configuration
• Editing CLI Scripts

Configuration Management Overview

System configuration files consist of a zip file that contains three components:
• A binary configuration file used by the system to restore the configuration.
• A text file which enables users to examine the system configuration in a readable format. The file includes the
value of all system parameters at the time of creation of the backup file.
• An additional text file which enables you to write CLI scripts in order to make desired changes in the backed-up
configuration. This file is executed by the system after restoring the configuration.
The system provides three restore points to manage different configuration files. Each restore point contains a single
configuration file. Files can be added to the restore points by creating backups of the current system state or by
importing them from an external server. For example, you may want to use one restore point to keep a last good
configuration, another to import changes from an external server, and the third to store the current configuration.
You can apply a configuration file to the system from any of the restore points.

Viewing Current Backup Files

The system provides three restore points to manage different configuration files. Each restore point contains a single
configuration file. Files can be added to the restore points by creating backups of the current system state or by
importing them from an external server. For example, you may want to use one restore point to keep a last good
configuration, another to import changes from an external server, and the third to store the current configuration.
To display the configuration files currently saved at the system restore points:
1. Select Platform > Configuration > Backup Files. The Backup Files page opens. For a description of the information
provided in the Backup Files page, see Table 18 Backup Files Page Columns.
Figure 214 Backup Files Page

Phn 3963 013v000

Page 312
Chapter 4: Unit Management Backing Up and Restoring Configurations

Table 19 Backup Files Page Columns

Parameter Definition

File number A number from 1 to 3 that identifies the restore point.

Original system type The type of unit from which the backup configuration file was created.

Software version The software version of the unit from which the backup configuration file
was created.

Time of creation The time and date on which the configuration file was created.

Original IP address The IP address of the unit from which the configuration file was created.

System ID The System ID, if any, of the unit from which the configuration file was
created. This is taken from the Name field in the Unit Parameters page.
See Configuring Unit Parameters.

Valid Reserved for future use.

Setting the FTP/SFTP Configuration Management Parameters

When importing and exporting configuration files via FTP/SFTP, the PTP 820 functions as an FTP or SFTP client. You
must install FTP or SFTP server software on the PC or laptop you are using to perform the import or export. For
details, see Installing and Configuring an FTP or SFTP Server.
Before importing or exporting a configuration file via FTP/SFTP, you must perform the following steps:
1. Verify that the system date and time are correct. See Setting the Time and Date (Optional).
2. Install and configure an FTP server on the PC or laptop you are using to perform the import or export. See
Installing and Configuring an FTP or SFTP Server.
3. In the PTP 820’s Web EMS, select Platform > Configuration > Configuration Management. The Configuration
Management page opens.
4. In the Configuration Management page, select FTP.
Figure 215 Configuration Management Page FTP/SFTP
Phn 3963 013v000
Page 313
Chapter 4: Unit Management Backing Up and Restoring Configurations

5. Click FTP Parameters to display the FTP Parameters page.

Figure 216 FTP Parameters Page

6. In the File transfer protocol field, select FTP or SFTP.

7. In the User name field, enter the user name you configured in the FTP server.
8. In the Password field, enter the password you configured in the FTP server. If you did not configure a password
for your FTP user, simply leave this field blank.
9. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
FTP server in the Server IP address field. See Defining the IP Protocol Version for Initiating Communications.

Phn 3963 013v000

Page 314
Chapter 4: Unit Management Backing Up and Restoring Configurations

10. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
FTP server in the IPv6 Server Address field. See Defining the IP Protocol Version for Initiating Communications.
11. In the Path field, enter the location of the file you are downloading or uploading. If the location is the root shared
folder, it should be left empty. If the location is a sub-folder under the root shared folder, specify the folder
name. If the shared folder is "C:\", this parameter can be left empty or populated with "//".
12. In the FileName field, enter the name of the file you are importing, or the name you want to give the file you are
exporting.

Note
You must add the suffix .zip to the file name. Otherwise, the file import may fail. You can export the
file using any name, then add the suffix .zip manually.

13. Click Apply, then Close, to save the FTP parameters and return to the Configuration Management page
14. In the File number field, select from three system restore points:
o When you import a configuration file, the file is saved to the selected restore point, and
overwrites whichever file was previously held in that restore point.
o When you export a configuration file, the file is exported from the selected restore
point.
o When you back up the current configuration, the backup configuration file is saved to
the selected restore point, and overwrites whichever file was previously held in that
restore point.
o When you restore a configuration, the configuration file in the selected restore point is
the file that is restored.

Note
The Timed installation field is reserved for future use.

15. Click Apply to save your settings.

Phn 3963 013v000

Page 315
Chapter 4: Unit Management Backing Up and Restoring Configurations

Exporting a Configuration File

You can export a saved configuration file from one of the system's three restore points to a PC or
laptop. You can use FTP, SFTP, HTTP, or HTTPS to export a configuration file.

Exporting a Configuration File Via HTTP or HTTPS

To export a configuration file using HTTP or HTTPS:
1. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
2. Select HTTP.

3. In the File Number field, select the restore point from which you want to export the file.

Note
The Timed installation field is reserved for future use.

4. Click Export. The export begins. You can view the status of the export in the File Transfer status field in the
Export/Import file status section. Possible values are:
o Ready – The default value, which appears when no import or export is in progress.
o File-in-Transfer – The file export is in progress.
o If an error occurs during the import or export, an appropriate error message is displayed
in this field.
When the import or export is complete, one of the following status indications appears:
o Succeeded
o Failure
The next time the system is reset, the File Transfer status field returns to Ready.

Phn 3963 013v000

Page 316
Chapter 4: Unit Management Backing Up and Restoring Configurations

To abort the export, click Abort Export.

Exporting a Configuration File Via FTP or SFTP
To export a configuration file via FTP or SFTP:
1. Verify that you have followed all the steps in Setting the FTP/SFTP Configuration Management Parameters.
2. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
(Figure 184).
3. Select FTP.
4. In the File Number field, select the restore point from which you want to export the file.

Note
The Timed installation field is reserved for future use.

5. Click Apply to save your settings.

6. Click Export. The export begins. You can view the status of the export in the File Transfer status field in the
Export/Import file status section. Possible values are:
◦ Ready – The default value, which appears when no import or export is in
progress.
◦ File-in-Transfer – The file export is in progress.
◦ If an error occurs during the import or export, an appropriate error
message is displayed in this field.
When the import or export is complete, one of the following status indications appears:
• Succeeded
• Failure
The next time the system is reset, the File Transfer status field returns to Ready.

Importing a Configuration File

You can import a saved configuration file from a PC or laptop to one of the system's three restore points.
You can use FTP, SFTP, HTTP, or HTTPS to export a configuration file.

Importing a Configuration File Via HTTP or HTTPS

To export a configuration file using HTTP or HTTPS:
1. Select Platform > Configuration > Configuration Management. The Configuration Management page opens.
2. Select HTTP.
3. Select Choose File and from your directory, select the file you want to import.
4. In the File Number field, select the restore point to which you want to import the file. The imported file will be
saved to the selected restore point, and will overwrite whatever file was previously held in that restore point.
5. Click Apply to save your settings.
6. Click Import. The import begins. You can view the status of the import in the File Transfer status field in the
Export/Import file status section. Possible values are:
o Ready – The default value, which appears when no import or export is in progress.
o File-in-Transfer – The file import is in progress.

Phn 3963 013v000

Page 317
Chapter 4: Unit Management Backing Up and Restoring Configurations

o If an error occurs during the import or export, an appropriate error message is displayed
in this field.
When the import or export is complete, one of the following status indications appears:
o Succeeded
o Failure
The next time the system is reset, the File Transfer status field returns to Ready.
After importing the configuration file, you can apply the configuration by restoring the file from the restore point to
which you saved it. See Restoring a Saved Configuration.
Importing a Configuration File Via FTP or SFTP
To import a configuration file using FTP or SFTP:
1. Verify that you have followed all the steps in Setting the FTP/SFTP Configuration Management Parameters.
2. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
(Figure 184).
3. Select FTP.
4. In the File Number field, select the restore point to which you want to import the file. The imported file will be
saved to the selected restore point, and will overwrite whatever file was previously held in that restore point.
5. Click Apply to save your settings.
6. Click Import. The import begins. You can view the status of the import in the File Transfer status field in the
Export/Import file status section. Possible values are:
◦ Ready – The default value, which appears when no import or export is in
progress.
◦ File-in-Transfer – The file import is in progress.
If an error occurs during the import or export, an appropriate error message is displayed in this
fieldWhen the import or export is complete, one of the following status indications appears:
• Succeeded
• Failure
The next time the system is reset, the File Transfer status field returns to Ready.
After importing the configuration file, you can apply the configuration by restoring the file from the restore point to
which you saved it. See Restoring a Saved Configuration.

Deleting a Configuration File

You can delete a saved configuration file from any of the system's three restore points:
To delete a configuration file:
1. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
(Figure 145).
2. In the File Number field, select the restore point that holds the configuration file you want to delete.
3. Click Delete. The file is deleted.

Backing Up the Current Configuration

You can back up the current configuration file to one of the system's three restore points.
To back up a configuration file:
Phn 3963 013v000
Page 318
Chapter 4: Unit Management Backing Up and Restoring Configurations

1. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
(Figure 145).
2. In the File Number field, select the restore point to which you want to back up the file. If another configuration
file is already saved to that restore point, it will be overwritten by the file you back up.
3. Click Backup. The backup begins. You can view the status of the backup in the Backup file creation status field.
Possible values in the status field are:
o Ready – The default value, which appears when no backup is in progress.
o Generating file – The system is verifying the files to be backed up.
If an error occurs during the backup, an appropriate error message is displayed in this field.
When the backup is complete, one of the following status indications appears:
o Succeeded
o Failure
The next time the system is reset, the Backup file creation status field returns to Ready.

Restoring a Saved Configuration

You can replace the current configuration with any configuration file saved to one of the system's three
restore points by restoring the configuration file from the restore point. Restoring a saved
configuration does not change the unit’s FIPS mode.
To restore a configuration file:
1. Select Platform > Configuration > Configuration Management. The Configuration Management page opens
(Figure 145 Configuration Management Page).
2. In the File Number field, select the restore point that holds the configuration you want to restore.
3. Click Restore. The configuration restoration begins. You can view the status of the restoration in the
Configuration restore status field.

Note
While a configuration restoration is taking place, no user can make any changes to the configuration.
All system configuration parameters are read-only during the configuration restoration.

Editing CLI Scripts

The configuration file package includes a text file that enables you to write CLI scripts in a backed-up configuration
that are executed after restoring the configuration.
To edit a CLI script:
1. Back up the current configuration to one of the restore points. See Backing Up the Current Configuration.
2. Export the configuration from the restore point to a PC or laptop. See Exporting a Configuration File.
3. On the PC or laptop, unzip the file Configuration_files.zip.
4. Edit the cli_script.txt file using clish commands, one per line.
5. Save and close the cli_script.txt file, and add it back into the Configuration_files.zip file.
6. Import the updated Configuration_files.zip file back into the unit. See Importing a Configuration File.
7. Restore the imported configuration file. See Restoring a Saved Configuration. The unit is automatically reset.
During initialization, the CLI script is executed, line by line.

Phn 3963 013v000

Page 319
Chapter 4: Unit Management Backing Up and Restoring Configurations

Note
If any specific command in the CLI script requires reset, the unit is reset when that that command is
executed. During initialization following the reset, execution of the CLI script continues from the
following command.

Phn 3963 013v000

Page 320
Chapter 4: Unit Management Setting the Unit to the Factory Default Configuration

Setting the Unit to the Factory Default

Configuration

You can restore the unit to its factory default configuration, while retaining the unit’s IP address settings and logs.
To restore the factory default settings:
1 Select Platform > Shelf Management > Chassis Configuration. The Chassis
Configuration page opens.
Note
This page is only available in Advanced mode. A limited version,
without the drag-and-drop functionality, is available in Basic view by selecting Device View.

Figure 217 Chassis Configuration Page

1. Click Set to Factory Default. The unit is restored to its factory default settings. This does not change the unit's IP
address.

Phn 3963 013v000

Page 321
Chapter 4: Unit Management Performing a Hard (Cold) Reset

Performing a Hard (Cold) Reset

To initiate a hard (cold) reset on the unit:

1 Select Platform > Shelf Management > Chassis Configuration. The Chassis
Configuration page opens (Figure 223).

1. Figure 218 Reset Page

2. Click Reset.
3. A prompt appears asking if you want to proceed with the reset. Click Yes to initiate the reset.
The unit is reset.

Phn 3963 013v000

Page 322
Chapter 4: Unit Management Configuring Unit Parameters

Configuring Unit Parameters

To view and configure system information:

1. Select Platform > Management > Unit Parameters. The Unit Parameters page opens.
2. Table 19 describes the fields in the Unit Parameters page.

Figure 219 Unit Parameters Page

Table 20 Unit Parameters

Parameter Definition

Name A name for the unit (optional). This name appears at the top of every
Web EMS page.

Description Descriptive information about the unit. This information is used for
debugging, and should include information such as the chassis type.

System up time The time since the system was last reinitialized.

Contact person The name of the person to be contacted if and when a problem with the
system occurs (optional).

Location The actual physical location of the node or agent (optional).

Longitude The unit's longitude coordinates.

Latitude The unit's latitude coordinates.

Phn 3963 013v000

Page 323
Chapter 4: Unit Management Configuring Unit Parameters

Parameter Definition

Measurement format The type of measurement you want the system to use: Metric or
Imperial.

Unit Temperature The current temperature of the unit. If the unit temperature goes lower
than -40°C or higher than 90°C, the unit raises an extreme temperature
alarm (Alarm ID 25). This alarm is cleared when the unit temperature rises
above -37°C or goes below 87°C.

Voltage input (Volt) The voltage input of the unit. If the voltage exceeds 60V, the unit raises a
high voltage alarm (Alarm ID 27). This alarm is cleared when the voltage
goes lower than 58V. If the voltage goes lower than 32V, the unit raises a
low voltage alarm (Alarm ID 26). This alarm is cleared when the voltage
rises above 34V.

User Comment A free text field for any information you want to record (up to 500
characters)

Phn 3963 013v000

Page 324
Chapter 4: Unit Management Configuring NTP

Configuring NTP

PTP 820 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.
You can configure up to four NTP servers. Each server can be configured using IPv4 or IPv6. When multiple servers are
configured, the unit chooses the best server according to the implementation of Version 4.2.6p1 of the NTPD
(Network Time Protocol Daemon). The servers are continually polled. The polling interval is determined by the NTPD,
to achieve maximum accuracy consistent with minimum network overhead.
To view and configure the NTP Parameters:
1. Select Platform > Management > NTP Configuration. The NTP Configuration page opens.

Figure 220 NTP Configuration Page

2 Select a row in the NTP Configuration table and click Edit. The NTP Configuration Edit
page opens.

Phn 3963 013v000

Page 325
Chapter 4: Unit Management Configuring NTP

2. In the Admin field, select Enable.

3. In the NTP version field, select the NTP version you want to use. Options are NTPv3 and NTPv4. NTPv4 provides
interoperability with NTPv3 and with SNTP.
3 Select IPv4 or IPv6.

Note: For each NTP server, you can define an IPv4 address or an IPv6
address but not both.
4 In the NTP server IPv4 address or NTP server IPv6 address field, enter the IP address of the
NTP server.

Phn 3963 013v000

Page 326
Chapter 4: Unit Management Configuring NTP

5 Click Apply. Once you click Apply, the NTP Status Parameters appear. Table 31
describes the NTP Status Parameters.

Figure 193: NTP Configuration Page (Disabled)

6 Repeat these steps for each NTP server you want to configure, up to four servers.

Table 31: NTP Status Parameters

Parameter Definition

Lock status Indicates the NTP status of the unit. Possible values are:
• LOCK – The NTP client is locked on a remote server.
• LOCAL – The NTP client is locked on the local system clock
(free running clock).
• CANDIDATE – The server is next in line to be selected if the
currently locked server is discarded.
• N/A – The NTP client is not locked on any clock or NTP is
disabled.
IPv4 address The IPv4 address of the NTP server (if configured).
IPv6 address The IPv6 address of the NTP server (if configured).
Refid The NTP client time server.

Phn 3963 013v000

Page 276
Chapter 4: Unit Management Configuring NTP

Stratum The NTP client statum..

Peer type The server peer type.

Reach The result of the last 8 polls in octal form.
Delay The round trip delay to peer in milliseconds.
Offset Offset to the client in milliseconds.
Jitter Variance in latency on the network.

Phn 3963 013v000

Page 277
Chapter 4: Unit Management Displaying Unit Inventory

Displaying Unit Inventory

To view the unit's part number and serial number:

Select Platform > Management > Inventory. The Inventory page opens, showing the unit's part number and serial
number.

Figure 221 Inventory Page

Phn 3963 013v000

Page 278
Chapter 4: Unit Management Displaying SFP DDM and Inventory Information

Displaying SFP DDM and Inventory Information

Static and dynamic monitoring is available for SFP modules, including all SFP, SFP+, and CSFP modules used in
Ethernet and MIMO ports in PTP 820 all-outdoor products.
Dynamic monitoring (DDM) PMs are also available.

Note: DDM parameters are not relevant for electrical SFPs.

The following alarms are available in connection with SFP DDM and inventory monitoring. The polling interval for
these alarms is one minute.
• Alarm #803- SFP port RX power level is too low.
• Alarm #804 – SFP port RX power level is too high.
• Alarm #805- SFP port TX power level is too low.
• Alarm #806 – SFP port TX power level is too high.
These alarms are based on thresholds defined by the SFP module vendor, which are static. They also display the
actual RX or TX values as of the time when the alarm was raised, which are dynamic. The dynamic values are not
changed as long as the alarm is still raised. They are only updated if the alarm is cleared, then raised again.
If there is no signal on the interface, a Loss of Carrier alarm (LOC) is raised, and this alarm masks the DDM alarms.

Figure 222 SFP Alarm Example

Displaying Information about an SFP Module

To display information about an SFP module:
1 Select Platform > Interfaces > SFP. The SFP Transceiver Inventory and DDM page opens.
• The SFP Inventory section displays static information about the SFP module.
• The SFP Digital Diagnostic Monitoring (DDM) section displays dynamic information about the current state
of the SFP module.

Phn 3963 013v000

Page 279
Chapter 4: Unit Management Displaying SFP DDM and Inventory Information

Figure 223 Radio Parameters Page – PTP 820C/PTP 820C-HP

2 In the SFP Transceiver field, select the SFP interface about which you want to display information.
Note: In a 2E2SX PTP 820C unit, P4 is displayed as Ethernet: Slot 1, Port 4 when used as a
traffic port, and Extension: Slot 1, Port 1 when used as an Extension port in MIMO and Space
Diversity configurations.

Table 21 SFP Inventory Parameters

Parameter Description
Transceiver Present Indicates whether an SFP module is attached to the interface.
Connector Type Always displays LC.
Transceiver Type Displays a description of the SFP module.
Vendor Name Displays the name of the SFP’s vendor.
Vendor Part Number Displays the vendor’s part number for the SFP module.
Vendor Serial Number Displays the vendor’s serial number for the SFP module.
Vendor Revision Displays the revision number of the serial number provided by
the vendor for the SFP module.
Laser Wavelength (nm) Display’s the SFP module’s laser wavelength. For CSFP modules,
two wavelengths are displayed. This parameters is not relevant
for copper SFPs.

Phn 3963 013v000

Page 280
Chapter 4: Unit Management Displaying SFP DDM and Inventory Information

Parameter Description
Link Length SM Fiber (km) The maximum length of the cable (in km) for single mode fiber
cables.
Link Length OM1 Fiber (m) The maximum length of the cable (in meters) for OM1 multi-
mode fiber cables.
Link Length OM2 Fiber (m) The maximum length of the cable (in meters) for OM2 multi-
mode fiber cables.
Link Length OM3 Fiber (m) The maximum length of the cable (in meters) for OM3 multi-
mode fiber cables.

Table 22 SFP Digital Diagnostic Monitoring (DDM) Parameters

Parameter Description
Optical Diagnostics Displays whether the SFP module supports DDM monitoring. For
Supported modules that do not support DDM monitoring, the parameters
below are not available.
RX Power Level (dBm) The SFP module’s current RX power signal strength (in dBm).
TX Power Level (dBm) The SFP module’s current TX power signal strength (in dBm).
Bias Current (mA) The laser bias current of the SFP module (in mA)
Temperature The current temperature of the SFP module (displayed in both C°
and F°).

If no signal is being received, RX Power Level is displayed as -40 dBm.

If the Admin status of the port is Down, the TX Power Level is displayed as -40 DBm and the Bias Current is
displayed as 0 mA.
The Temperature is always shown as long as the SFP module is inserted in the port.

Phn 3963 013v000

Page 281
Chapter 4: Unit Management Displaying SFP DDM and Inventory Information

Displaying PMs about an SFP Module

To display DDM PMs:
1 Select Platform > PM & Statistics > SFP. The SFP PM Report page opens.

Figure 224 SFP PM Report Page

2 In the Interface field, select the interface for which you want to display PMs.

Note: In a 2E2SX PTP 820C unit, P4 is displayed as Ethernet: Slot 1, Port 4 when used as a
traffic port, and Extension: Slot 1, Port 1 when used as an Extension port in MIMO and
Space Diversity configurations.

3 In the Interval Type field:

• To display reports for the past 24 hours, in 15 minute intervals, select 15 minutes.
• To display reports for the past month, in daily intervals, select 24 hours.

Note: No entries are displayed if the SFP device does not support DDM, or if the Admin
status of the interface is Down.

DDM PMs are not persistent, which means they are not saved in the event of unit reset. RX and TX power levels
are collected five times per 15-minute interval. 15-minute PM data is saved for 24 hours. 24-hour PM data, which
is updated every 15 minutes, is saved for 30 days.
Error! Reference source not found. describes the DDM PMs.

Table 23 DDM PMs

Parameter Definition
Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.
Min RX Power (dBm) The minimum RX power during the interval (dBm).
Max RX Power (dBm) The maximum RX power during the interval (dBm).

Phn 3963 013v000

Page 282
Chapter 4: Unit Management Displaying SFP DDM and Inventory Information

Parameter Definition
Avg RX Power (dBm) The average RX power during the interval (dBm).
Min TX Power (dBm) The minimum TX power during the interval (dBm).
Max TX Power (dBm) The maximum TX power during the interval (dBm).
Avg TX Power (dBm) The average TX power during the interval (dBm).
Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. An x in the column indicates that the values are not
reliable. Possible causes are (i) an LOC alarm, (ii) changing the Admin status
of the interface, or (iii) unit reset.

Phn 3963 013v000

Page 283
Chapter 4: Unit Management Defining a Login Banner

Defining a Login Banner

You can define a login banner of up to 2,000 bytes. This banner will appear every time a user establishes a
connection with the Web EMS. The banner appears before the login prompt, so that users will always see the login
banner and must manually close the banner before logging in to the Web EMS.
To define a login banner:
1 Select Platform > Management > Login Banner. The Login Banner page opens.

Figure 225: Login Banner Page

2 Enter a text message of up to 2,000 bytes.

3 To display a test banner as it will appear to users, click Test Banner.
4 Click Apply.

Phn 3963 013v000

Page 284
Chapter 5: Radio Configuration
This section includes:
• Viewing the Radio Status and Settings
• Configuring the Remote Radio Parameters
• Configuring ATPC and ATPC Override Timer
• Configuring Header De-Duplication and Frame Cut-Through
• Configuring AES-256 Payload Encryption
• Configuring and Viewing Radio PMs and Statistics
Related topics:
• Configuring the Radio Parameters
• Configuring the Radio (MRMC) Script(s)
• System Configurations
• Configuring Multi-Carrier ABC
• Configuring XPIC
• Configuring Unit Protection with HSB Radio
• Configuring MIMO and Space Diversity
• Configuring Advanced Frequency Reuse (AFR)

Phn 3963 013v000

Page 285
Chapter 5: Radio Configuration Viewing the Radio Status and Settings

Viewing the Radio Status and Settings

You can configure the radios and display the radio parameters in the Radio Parameters page.

Note
For instructions how to configure the radio parameters, see Configuring the Radio Parameters.

To display the radio parameters:

1. Select Radio > Radio Parameters. The Radio Parameters page opens.
o For multi-carrier units, the Radio Parameters page initially displays a table as shown
in Figure 155.
o For single-carrier units, a page appears, similar to Figure 27 (which shows a PTP
820C/PTP 820C-HP page).

Figure 226 Radio Parameters Page – PTP 820C/PTP 820C-HP

2. For multi-carrier units, select the carrier in the Radio table (see Figure 155) and click Edit. A separate Radio
Parameters page opens. The page is essentially identical to the single-carrier page, except for the addition of a
Radio location parameter.

Phn 3963 013v000

Page 286
Chapter 5: Radio Configuration Viewing the Radio Status and Settings

Figure 227 Radio Parameters Page Per Carrier – PTP 820C/PTP 820C-HP

Table 24 lists and describes the parameters in the Radio table of the PTP 820C or PTP 820C-HP Radio Parameters
page and the Status parameters section of the Radio Parameters configuration page.

Phn 3963 013v000

Page 287
Chapter 5: Radio Configuration Viewing the Radio Status and Settings

Table 24 Radio Status Parameters

Parameter Definition

Type The RF module type.

XPIC Support Indicates whether the carrier is operating in XPIC mode. For instructions
on configuring XPIC, refer to Configuring XPIC.
Note: Only relevant for PTP 820C units.

TX Frequency The configured TX radio frequency. The TX radio frequency is configured

in the Frequency control (Local) section of the Radio Parameters page.
See Configuring the Radio Parameters.

RX Frequency The configured RX radio frequency. The RX radio frequency is configured

in the Frequency control (Local) section of the Radio Parameters page.
See Configuring the Radio Parameters.

Radio Interface Indicates whether the carrier is operational (Up) or not operational
operational status (Down).

Operational TX Level The actual TX signal level (TSL) of the carrier (in dBm).
(dBm)

RX Level (dBm) The actual measured RX signal level (RSL) of the carrier (in dBm).

Modem MSE (dB) The MSE (Mean Square Error) of the RX signal, measured in dB. A value of
0 means that the modem is not locked.

Modem XPI (dB) The XPI (Cross Polarization Interference) level, measured in dB.
Note: Only relevant for PTP 820C units.

Defective Blocks The number of defective radio blocks that have been counted. Click Clear
Counter to reset this counter.

TX Mute Status Indicates whether radio transmission is muted.

Adaptive TX power Indicates whether Adaptive TX power is currently operational.

operational status

Phn 3963 013v000

Page 288
Chapter 5: Radio Configuration Configuring the Remote Radio Parameters

Configuring the Remote Radio Parameters

You can view and configure the parameters of the carrier or carriers at the remote side of the link in the Remote
Radio Parameters page.
To display the remote radio parameters:
1. Select Radio > Remote Radio Parameters. The Remote Radio Parameters page opens.
o For multi-carrier units, the Radio Parameters page initially displays a table as shown
in Figure 157.
o For single-carrier units, the page appears as shown in Figure 158

Figure 228 Remote Radio Parameters Page – PTP 820C/PTPT 820C-HP

Figure 229 Remote Radio Parameters Page – PTP 820S /PTP 820E

Phn 3963 013v000

Page 289
Chapter 5: Radio Configuration Configuring the Remote Radio Parameters

2. For multi-carrier units, select the carrier in the Remote Radio table (see Figure 157) and click Edit. A separate
Remote Radio Parameters page opens. The page is identical to the single-carrier page.

Figure 230: Remote Radio Parameters Page Per Carrier – PTP 820C

3. Configure the remote radio parameters. For a description of these parameters, see Table 25 Remote Radio
Parameters.
4. Click Apply.
You can also reset the remote unit from the Remote Radio Parameters – Edit page:
To reset the remote unit, click Reset Remote Unit.

Table 25 Remote Radio Parameters

Parameter Definition

Radio Location Read-only. Identifies the carrier.

Remote Radio Location Read-only. Identifies the location of the remote radio.

Local Remote Channel Read-only. The operational status of the active (in a protection
Operational Status configuration) remote channel.

Remote Receiver Signal Read-only. The Rx level of the remote radio, in dBm.
Level

Phn 3963 013v000

Page 290
Chapter 5: Radio Configuration Configuring the Remote Radio Parameters

Parameter Definition

Remote Most Severe Read-only. The level of the most severe alarm currently active on the
Alarm remote unit.

Remote Unit Link ID Edit page only. Identifies the link, in order to distinguish it from other
links. Enter a unique identifier from 1 to 65535.

Remote Tx Output Level The remote unit's Tx output level, if the remote unit has been configured
to operate at a fixed Tx level (in dBm).

Remote Radio Mute To mute the TX output of the remote radio, select On. To unmute the TX
output of the remote radio, select Off.

Remote IP Address The IPv4 IP address of the remote unit.

Remote IPv6 Address The IPv6 IP address of the remote unit.

Phn 3963 013v000

Page 291
Chapter 5: Radio Configuration Configuring ATPC and ATPC Override Timer

Configuring ATPC and ATPC Override Timer

ATPC is a closed-loop mechanism by which each carrier changes the TX power according to the indication received
across the link, in order to achieve a desired RSL on the other side of the link.
With ATPC, if the radio increases its TX power up to the configured TX power, it can lead to a period of sustained
transmission at maximum power, resulting in unacceptable interference with other systems.
In order to minimize interference, PTP 820C and PTP 820S provide an ATPC override mechanism. If ATPC override
is enabled, a timer begins whenever ATPC raises the TX power to its maximum. When the timer expires, the radio
enters ATPC override state. In ATPC override state, the radio transmits no higher than the pre-determined ATPC
override TX level, and an ATPC override alarm is raised. The radio remains in ATPC override state until the ATPC
override state is manually cancelled by the user (or until the unit is reset). The radio then returns to normal ATPC
operation.
In a configuration with unit protection, the ATPC override state is propagated to the standby unit in the event of
switchover.

Note
When canceling an ATPC override state, you should ensure that the underlying problem has been
corrected. Otherwise, ATPC may be overridden again.
You cannot use ATPC in MIMO mode. See Configuring MIMO and Space Diversity

To enable and configure ATPC and display ATPC settings:

1. Select Radio > ATPC. The ATPC page opens.
o For multi-carrier units, the Radio Parameters page initially displays a table as shown
in Figure 160.
o For Single-carrier units, a page appears, similar to Figure 161 (which shows a PTP
820C/PTP 820C-HP page).

Phn 3963 013v000

Page 292
Chapter 5: Radio Configuration Configuring ATPC and ATPC Override Timer

Figure 231 ATPC Page – PTP 820C/PTP 820C-HP

1 For multi-carrier units, select the carrier you wish to configure in the ATPC
table (see Figure 160) and click Edit. A separate ATPC –Edit page opens. The
page is essentially identical to the single-carrier page.

Figure 232 ATPC – Edit Page per Carrier – PTP 820C/PTP 820C-HP

2. In the ATPC Admin field, select Enable to enable ATPC or Disable to disable ATPC.
3. Click Apply. If you selected ATPC -Admin – Enable, the Reference RX Level (dBm) and ATPC Override Admin
fields are now displayed.
4. In the Reference RX Level (dBm) field, enter a number between -70 and -30 as the reference value for the
ATPC mechanism. When ATPC is enabled, it adjusts the TX power dynamically to preserve this RSL level. The
range of values depends on the frequency, MRMC script, and RFU type.
5. In the ATPC Override Admin field, select Enable to enable ATPC override or Disable to disable ATPC override.
You can only enable ATPC override if ATPC itself is enabled.

Phn 3963 013v000

Page 293
Chapter 5: Radio Configuration Configuring ATPC and ATPC Override Timer

Note
Make sure to set an appropriate value in the Override Timeout field before enabling ATPC override.
Failure to do so can lead to unexpected reduction of the TX power with corresponding loss of
capacity if TX override is enabled with the timer set to a lower-than-desired value.

6. Click Apply. If you selected ATPC Override Admin – Enable, the ATPC Override State, Override TX Level, and
ATPC Override Admin fields are now displayed.
7. In the Override TX Level field, select the TX power, in dBm, to be used when the unit is in an ATPC override
state. The range of values depends on the frequency, MRMC script, and RFU type.
8. In the Override Timeout field, select the amount of time, in seconds, the timer counts from the moment the
radio reaches its maximum configured TX power until ATPC override goes into effect. You can select from 0 to
1800 seconds.
9. In the Remote ATPC Admin field, select Enable to enable ATPC or Disable to disable ATPC on the remote radio
carrier.
10. Click Apply. If you selected Remote ATPC Admin – Enable, the Remote Reference RX Level (dBm) field is now
displayed.
11. In the Remote Reference RX Level (dBm) field, enter a number between -70 and -30 as the reference value for
the ATPC mechanism on the remote radio carrier.
12. Click Apply.
To cancel an ATPC override state on the local unit, click Cancel Override.

Phn 3963 013v000

Page 294
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Configuring Header De-Duplication and Frame Cut-

Through

Note
ForPTP 820E Header De-Duplication is available for all channels except 500 MHz. Make sure to disable
Header De-Duplication before selecting a 500 MHz MRMC script

Header De-Duplication enables operators to significantly improve Ethernet throughout over the radio link without
affecting user traffic. Header De-Duplication can be configured to operate on various layers of the protocol stack,
saving bandwidth by reducing unnecessary header overhead. Header De-duplication is also sometimes known as
header compression.

Note
The Header De-Duplication configuration must be identical on both sides of the link.

Using the Frame Cut-Through feature, frames assigned to queues with 4th priority pre-empt frames already in
transmission over the radio from other queues. Transmission of the pre-empted frames is resumed after the
cut -through with no capacity loss or re-transmission required.

Note
If Frame Cut-Through is used together with 1588 Transparent Clock, the 1588 packets must be given
a CoS that is not assigned to the fourth priority queue.

To configure Header De-Duplication and Frame Cut-Through:

1. Select Radio > Ethernet Interface > Configuration. The Radio Ethernet Interface Configuration page opens.
o For multi-carrier units, the Radio Ethernet Interface Configuration page initially
displays a table as shown in Figure 162.
o For PTP 820S units, a page appears, similar to Figure 163 (which shows a PTP
820C/PTP 820C-HP page).

Figure 233 Radio Ethernet Interface Configuration Page – PTP 820C/PTP 820C-HP

Phn 3963 013v000

Page 295
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Note
The Header De-duplication type column in the Main page and the Header De-duplication type field
in the Edit page are not operational. To monitor the Header De-Duplication setting and status, use
the Header De-duplication mode and Header De-duplication operational state columns and fields.

2. For multi-carrier units, select the carrier in the Radio Ethernet and Compression table (see Figure 162) and
click Edit. A separate Radio Ethernet Interface Configuration page opens. The page is essentially identical to
the single-carrier page.
3. Click Edit. The Radio Ethernet Interface Configuration – Edit page opens.
Figure 234 Radio Ethernet Interface Configuration – Edit Page Per Carrier – PTP 820C/PTP 820C-HP

4. In the Cut through mode field, select Yes to enable Frame Cut-Through or No to disable Frame Cut-Through.
5. In the Header Compression mode field, select from the following options:
o Disabled – Header De-Duplication is disabled.
o Layer2 – Header De-Duplication operates on the Ethernet level.
o MPLS – Header De-Duplication operates on the Ethernet and MPLS levels.
o Layer3 – Header De-Duplication operates on the Ethernet and IP levels.
o Layer4 – Header De-Duplication operates on all supported layers up to Layer 4.
o Tunnel – Header De-Duplication operates on Layer 2, Layer 3, and on the Tunnel
layer for packets carrying GTP or GRE frames.
o Tunnel-Layer3 – Header De-Duplication operates on Layer 2, Layer 3, and on the
Tunnel and T-3 layers for packets carrying GTP or GRE frames.
o Tunnel-Layer4 – Header De-Duplication operates on Layer 2, Layer 3, and on the
Tunnel, T-3, and T-4 layers for packets carrying GTP or GRE frames.
6. Click Apply, then Close

Phn 3963 013v000

Page 296
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Note
The Utilization threshold field is not applicable.

Viewing Header De-Duplication and Frame Cut-Through

Counters
You can view PMs on the usage of Header De-Duplication and Frame Cut-Through.
To view Header De-Duplication and Frame Cut-Through counters:
1. Select Radio > Ethernet Interface > Counters. The Radio Ethernet Interface Configuration page opens.
o For multi-carrier units, the Radio Ethernet Interface Configuration page initially
displays a table as shown in Figure 164.
o For Single-carrier units, the page appears as shown in Figure 165.

Figure 235 Radio Ethernet Interface Counters Page – PTP 820C/PTP 820C-HP

Phn 3963 013v000

Page 297
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Figure 236 Radio Ethernet Interface Counters Page – Single-Carrier

2. For multi-carrier units, select the carrier in the Header Compression Counters table (Figure 164) and
click View. A separate Radio Ethernet Interface Configuration page opens. The page is essentially identical to
the Single-carrier page.

Phn 3963 013v000

Page 298
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Figure 237 Radio Ethernet Interface Counters Page Per Carrier – PTP 820C/PTP 820C-HP

Table 26 lists and describes the fields in the Radio Ethernet Interface Counters page.

Table 26: Radio Ethernet Interface Counters Fields

Parameter Definition

Interface Location Identifies the radio interface.

Header Compression Counters

TX bytes before enhanced Bytes on the TX side before Header De-Duplication.

HC

TX compressed bytes Bytes on the TX side that were compressed by Header De-Duplication.

TX frames before Frames on the TX side before Header De-Duplication.

enhanced HC

Phn 3963 013v000

Page 299
Chapter 5: Radio Configuration Configuring Header De-Duplication and Frame Cut-Through

Parameter Definition

TX frames compressed by Frames on the TX side that were compressed by Header De-Duplication.
enhanced HC

TX learning frames The number of frames that have been used to learn unique data flows.
Once a particular flow type has been learned, subsequent frames with
that flow type are compressed by Header De-Duplication.

TX frames not compressed Frames on the TX side that were not compressed due to exclusion rules.
due to excluding rule Note: The use of exclusion rules for Header De-Duplication is planned for
future release.

TX frames not compressed Frames on the TX side that were not compressed for reasons other than
due to other reasons the use of exclusion rules.

TX number of active flows The number of Header De-Duplication flows that are active on the TX
side.

Number of active flows of Not supported.

user selected flow type

Ethernet Port Counters

Port RX good bytes The number of good bytes received on the port since the last time the
Radio Ethernet Interface counters were cleared.

Port RX good frames The number of good frames received on the port since the last time the
Radio Ethernet Interface counters were cleared.

Port TX total bytes The number of bytes transmitted since the last time the Radio Ethernet
Interface counters were cleared.

Port TX frames The number of frames transmitted since the last time the Radio Ethernet
Interface counters were cleared.

Port TX idle bytes The number of idle bytes transmitted since the last time the Radio
Ethernet Interface counters were cleared.

Cut Through Counters

TX frames The number of frames that have been transmitted via Frame Cut-Through
since the last time the Radio Ethernet Interface counters were cleared.

Phn 3963 013v000

Page 300
Chapter 5: Radio Configuration Configuring AES-256 Payload Encryption

Configuring AES-256 Payload Encryption

Note
This feature is only relevant for PTP 820C, PTP 820C-HP, and PTP 820S units.
This feature is not supported with MIMO or space diversity links.

This feature requires:

• Requires an activation key per radio. If no valid AES activation key has been applied to the unit, AES will not
operate on the unit. See Configuring the Activation Key. For PTP 820S and PTP 820C, any radio manufactured
after July 1, 2015, is AES hardware-ready. An easy way to validate this is to check the radio’s S/N number.
S/N’s starting F265xxx and above are AES hardware-ready.

Note
In order for the AES activation key to become active, you must reset the unit after configuring a valid
AES activation key. Until the unit is reset, an alarm will be present if you enable AES. This is not the
case for other activation keys.

PTP 820C and PTP 820S support AES-256 payload encryption. AES is enabled and configured separately for each
radio carrier.
PTP 820 uses a dual-key encryption mechanism for AES:
• The user provides a master key. The master key can also be generated by the system upon user command. The
master key is a 32-byte symmetric encryption key. The same master key must be manually configured on both
ends of the encrypted link.
• The session key is a 32-byte symmetric encryption key used to encrypt the actual data. Each link uses two
session keys, one for each direction. For each direction, the session key is generated by the transmit side unit
and propagated automatically, via a Key Exchange Protocol, to the other side of the link. The Key Exchange
Protocol exchanges session keys by encrypting them with the master key, using the AES-256 encryption
algorithm. Session keys are regenerated at user-configured intervals.
The first KEP exchange that takes place after a new master key is configured causes traffic to be blocked for up to
one minute, until the Crypto Validation State becomes Valid. Subsequent KEP exchanges that take place when a
session key expires do not affect traffic. KEP exchanges have no effect upon ACM, RSL, and MSE.
To configure payload encryption:
1. Verify that both the local and remote units are running with no alarms. If any alarm is present, take corrective
actions to clear the alarms before proceeding.
2. If the link is using in-band management, identify which unit is local and which unit is remote from the
management point of view.
3. In a protected link, enable protection lockout, first on the remote and then on the local unit. See Disabling
Automatic Switchover to the Standby Unit.
4. On the remote unit, select Radio > Payload Encryption. The Payload Encryption page opens.

Phn 3963 013v000

Page 301
Chapter 5: Radio Configuration Configuring AES-256 Payload Encryption

o For multi-carrier units, the Payload Encryption page initially displays a table as shown in Figure 167
Payload Encryption Page
o For PTP 820S units, a page appears, similar to Figure 168(which shows in PTP 820C/PTP 820C-HP
page).

Figure 238 Payload Encryption Page

5. Select the carrier you want to configure and click Edit. The Payload Encryption – Edit page opens.

Figure 239 Payload Encryption – Edit Page

6. Configure the master key by doing one of the following:

o Enter a master key in the Master Key field. You must enter between 8 and 32 ASCII characters.
o Click Generate key to generate a master key automatically.

Phn 3963 013v000

Page 302
Chapter 5: Radio Configuration Configuring AES-256 Payload Encryption

You must use the same master key on both sides of the link. This means that if you generate a master key
automatically on one side of the link, you must copy that key and for use on the other side of the link. Once
payload encryption has been enabled on both sides of the link, the Key Exchange Protocol periodically verifies that
both ends of the link have the same master key. If a mismatch is detected, an alarm is raised and traffic
transmission is stopped for the mismatched carrier at both sides of the link. The link becomes non-valid and traffic
stops being forwarded.
When you enter a master key, or when the master key is automatically generated, the key is hidden behind dots.
To copy the master key, you must display the key. To display the master key, click Show Key. A new Master key
field appears, displaying the master key. You can copy the key to the clipboard from this field.

Figure 240 Payload Encryption – Edit Page with Master Key Displayed

7. Record and save the master key generated in Step 6.

8. On the local unit, follow Steps 4 through 6 to configure the same master key configured on the remote unit
also on the local unit.
9. Enable payload encryption on the remote unit:
i In the Admin Mode field, select AES-256 to enable payload encryption.
II In the Session Key Period field, configure a time interval in hours and minutes (HH:MM). This is the inteval
at which the session key is automatically regenerated.

Note
The Session Key Period must be the same on both sides of the link.

III When you are finished, click Apply.

This step will cause the link status to be Down until payload encryption is successfully enabled on the local
unit. However, the RSL measured on the link should remain at an acceptable level.

Phn 3963 013v000

Page 303
Chapter 5: Radio Configuration Configuring AES-256 Payload Encryption

Note
The Crypto Validation State field indicates whether the interface is functioning properly, with AES-256
encryption. In order for this field to display Valid, both the interface itself and AES-256 encryption
must be enabled, the hardware must be in place and functioning properly, initialization must be
finished, and AES-256 encryption must be functioning properly, with no loopback on the interface.

10. Enable payload encryption on the local unit by following the procedure described in Step 9 Verify that on both
the local and remote active units, the link status returns to Up and user traffic is restored. In links using in-
band management, verify also that in-band management returns.
11. In a protected link, perform copy-to-mate, first on the remote and then on the local unit. See Step 5 in
Configuring HSB Radio Protection. After the copy-to-mate operation, wait for both standby units to re-boot
and verify that there are no alarms.

Note
The standby unit may have a payload encryption failure alarm for up to about one minute after the
unit is up and running.
12. In a protected link, remove the protection lockout, first on the remote and then on the local unit. See
Disabling Automatic Switchover to the Standby Unit.
13. Verify that there are no alarms on the link.

Note
Any time payload encryption fails, the Operational status of the link is Down until payload encryption
is successfully restored.

Phn 3963 013v000

Page 304
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Configuring and Viewing Radio PMs and Statistics

This section includes:

• Configuring BER Thresholds and Displaying Current BER
• Displaying MRMC Status
• Displaying MRMC PMs
• Displaying and Clearing Defective Block Counters
• Displaying Signal Level PMs and Configuring Signal Level PM Thresholds
• Displaying Modem BER (Aggregate) PMs
• Displaying MSE PMs and Configuring MSE PM Thresholds
• Displaying XPI PMs and Configuring XPI PM Threshold
• Displaying Traffic PMs

Note
The Radio > PM & Statistics > Diversity and Radio > PM & Statistics > Combined pages are reserved
for future use.

Configuring BER Thresholds and Displaying Current BER

You can configure PM thresholds, BER thresholds, and Excessive BER Administration. This enables you to define the
levels at which certain PMs are counted, such as the number of seconds in which the configured threshold RX and
TX levels are exceeded. This also enables you to define the levels at which certain alarms are triggered.
• Signal level PM thresholds, such as RX and TX level thresholds, are configured from the Signal Level PM Report
page. See Displaying Signal Level PMs and Configuring Signal Level PM Thresholds.
• MSE PM Thresholds are configured from the MSE PM Report page. See Displaying MSE PMs and Configuring
MSE PM Thresholds.
• XPI PM Thresholds are configured from the XPI PM Report page. See Displaying XPI PMs and Configuring XPI
PM Threshold.

Phn 3963 013v000

Page 305
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

You can also display the current BER level.

To configure the BER thresholds and Excessive BER Administration, and display current BER levels
1. Select Radio > Radio BER Thresholds. The Radio BER Thresholds page opens. The current BER level is
displayed, per radio, in the Radio BER column.

Figure 241 Radio BER Thresholds Page

2. In the Excessive BER admin field, select Enable to enable excessive BER administration or Disable to disable
excessive BER administration. Excessive BER administration determines whether or not excessive BER is
propagated as a fault and considered a system event. For example, if excessive BER administration is enabled,
excessive BER can trigger a protection switchover and can cause a synchronization source to go into a failure
status. Excessive BER administration is enabled or disabled for the entire unit rather than for specific radios.
3. In the Thresholds table, select the radio for which you want to configure thresholds.
4. Click Edit. The Radio BER Thresholds – Edit page opens.

Figure 242 Radio BER Thresholds – Edit Page

Phn 3963 013v000

Page 306
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

5. In the Excessive BER Threshold field, select the level above which an excessive BER alarm is issued for errors
detected over the radio link. The range values is 1e-3 to 1e-10.
6. In the Signal Degrade BER Threshold field, select the level above which a Signal Degrade alarm is issued for
errors detected over the radio link. The range values is 1e-6 to 1e-15.
7. Click Apply, then Close.

Displaying MRMC Status

Related Topics:
• Configuring the Radio (MRMC) Script(s)
To display the current modulation and bit rate per radio:
1. Select Radio > MRMC > MRMC Status. The MRMC Status page opens.

Figure 243 MRMC Status Page

Phn 3963 013v000

Page 307
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Table 27 describes the MRMC status parameters.

Note
To display the same parameters for an individual radio in a separate page, select the radio in the
MRMC script status table and click Edit. You can configure Adaptive TX Power from the MRMC Status
– Edit page. See Enabling ACM with Adaptive Transmit Power.

Phn 3963 013v000

Page 308
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Table 27 MRMC Status Parameters

Parameter Definition

Radio Location Identifies the carrier (Slot 2, port 1 or Slot 2, port 2).
Note: Only relevant for PTP 820C and PTP 820C-HP units.

Configured MRMC Script The current MRMC script.

TX profile The current TX profile.

TX QAM The current TX modulation.

TX bit-rate The current TX bit-rate.

RX profile The current RX profile.

RX QAM The current RX modulation.

RX bit-rate The current RX bit-rate.

Displaying MRMC PMs

Related Topics:
• Configuring the Radio (MRMC) Script(s)
For each radio carrier, you can display the minimum and maximum ACM profile and the minimum and maximum
bitrate (throughput) per 15-minute or daily intervals.
You can also define two ACM profile thresholds for each radio carrier, and display the number of seconds per
interval that the radio’s ACM profile was below each of these thresholds. These thresholds trigger the following
alarms:
• Threshold 1 – When the ACM profile goes beneath this threshold, Alarm ID 1313 (Major) is raised. The alarm is
cleared when the ACM profile is at or above this threshold.
• Threshold 2 – When the ACM profile goes beneath this threshold, Alarm ID 1314 (Critical) is raised. The alarm
is cleared when the ACM profile is at or above this threshold.

To display Multi-Rate Multi-Constellation PMs, including information on ACM profile

fluctuations per interval per radio:
1. Select Radio > PM & Statistics > MRMC. The MRMC PM Report page opens.
Figure 244 MRMC PM Report Page

Phn 3963 013v000

Page 309
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

2. For the PTP 820C and PTP 820C-HP, In the Port field, select the port that holds the radio for which you want to
display PMs.

3. In the Interval Type field:

• To display reports in 15-minute intervals, select 15 minutes.
• To display reports in daily intervals, select 24 hours.
Table 28 describes the MRMC PMs.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
MRMC PM table and click View.

To set the ACM profile thresholds:

1. Click Thresholds. The MRMC Thresholds Configuration – Edit page opens.

Figure 245: MRMC Thresholds Configuration – Edit Page

2. For each radio carrier, you can enter define two thresholds. In the MRMC PM Threshold 1 column, select the
higher profile threshold. In the MRMC PM Threshold 2 column, select the lower profile threshold. The default
value for each threshold is Profile 0.
3. Click Apply, then Close.

Table 28 MRMC PMs

Phn 3963 013v000

Page 310
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Parameter Definition

PM Interval The length of the interval for which the PMs were measured (15 Minutes
or 24 Hours).

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Min profile Displays the minimum ACM profile that was measured during the
interval.

Max profile Displays the maximum ACM profile that was measured during the
interval.

Min bitrate Displays the minimum total radio throughput (Mbps) delivered during the
interval.

Max bitrate Displays the maximum total radio throughput (Mbps) delivered during
the interval.

Seconds above Threshold Displays the number of seconds the radio was above both ACM profile
1 thresholds during the interval.

Seconds below Threshold Displays the number of seconds the radio was below ACM profile
1 threshold 1 during the interval.

Seconds below Threshold Displays the number of seconds the radio was below ACM profile
2 threshold 2 during the interval.

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

Displaying and Clearing Defective Block Counters

The Counters page displays the number of blocks in which errors were detected. The larger the amount, the
poorer the radio link quality.
To display the number of blocks in which errors were detected per radio:
1. Select Radio > PM & Statistics > Counters. The Counters page opens.
o For multi-carrier units, the Counters page initially displays a table as shown in
Figure 174.
o For Single-carrier unit, the Counters page appears as shown in Figure 175.

Figure 246 Counters Page – Multi-Carrier

Phn 3963 013v000

Page 311
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Figure 247 Counters Page – Single-Carrier

Phn 3963 013v000

Page 312
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

2. For Multi-carrier units, you can select the carrier in the Radio table (see Figure 174) and click View to display a
page for that carrier. A separate Counters page opens.

Figure 248 Counters Page Per Carrier – Multi-Carrier

3. To clear the counters, click Clear Counters.

Phn 3963 013v000

Page 313
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Displaying Signal Level PMs and Configuring Signal Level PM

Thresholds
To display signal level PMs per radio:
1. Select Radio > PM & Statistics > Signal Level. The Signal Level PM report page opens.

Figure 249 Signal Level PM Report Page

2. For the PTP 820C and PTP 820C-HP, in the Interface field, select the radio for which you want to display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.
Table 29 describes the Signal Level PMs.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the RF
PM table and click View.

Table 29 Signal Level PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Max TSL (dBm) The maximum TSL (Transmit Signal Level) that was measured during the
interval.

Min TSL (dBm) The minimum TSL (Transmit Signal Level) that was measured during the
interval.

Max RSL (dBm) The maximum RSL (Received Signal Level) that was measured during the
interval.

Phn 3963 013v000

Page 314
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Parameter Definition

Min RSL (dBm) The minimum RSL (Received Signal Level) that was measured during the
interval.

TSL exceed threshold The number of seconds the measured TSL exceeded the threshold during
seconds the interval. TSL thresholds are configured in the Radio Thresholds page.
See Configuring BER Thresholds and Displaying Current BER

RSL exceed threshold1 The number of seconds the measured RSL exceeded RSL threshold 1
seconds during the interval. RSL thresholds are configured in the Radio Thresholds
page. See Configuring BER Thresholds and Displaying Current BER.

RSL exceed threshold2 The number of seconds the measured RSL exceeded RSL threshold 2
seconds during the interval. RSL thresholds are configured in the Radio Thresholds
page. See Configuring BER Thresholds and Displaying Current BER

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

To set the Signal Level PM thresholds, click Thresholds. The Signal Level Thresholds Configuration – Edit Page
opens. Set the thresholds, described in Table 30, and click Apply.

Figure 250 Signal Level Thresholds Configuration - Edit Page

Phn 3963 013v000

Page 315
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Table 30 Signal Level Thresholds

Parameter Definition

RX Level Threshold 1 Specify the threshold for counting exceeded seconds if the RSL is below
(dBm) this level.

RX Level Threshold 2 Specify a second threshold for counting exceeded seconds if the RSL is
(dBm) below this level.

TX Level Threshold (dBm) Specify the threshold for counting exceeded seconds if the TSL is below
this level.

Displaying Modem BER (Aggregate) PMs

To display modem BER (Bit Error Rate) PMs per radio:
1. Select Radio > PM & Statistics > Aggregate. The Aggregate PM report page opens.

Figure 251 Aggregate PM Report Page

2. For the PTP 820C and PTP 820C-HP, in the Interface field, select the radio for which you want to display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.
Table 31 describes the Modem BER (Aggregate) PMs.

Phn 3963 013v000

Page 316
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
Modem BER PM table and click View.

Table 31 Modem BER (Aggregate) PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

ES Displays the number of seconds in the measuring interval during which

errors occurred.

SES Displays the number of severe error seconds in the measuring interval.

UAS Displays the Unavailable Seconds value of the measured interval. The
value can be between 0 and 900 seconds (15 minutes).

BBE Displays the number of background block errors during the measured
interval.

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

Phn 3963 013v000

Page 317
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Displaying MSE PMs and Configuring MSE PM Thresholds

To display modem MSE (Minimum Square Error) PMs per radio:
1. Select Radio > PM & Statistics > MSE. The MSE PM report page opens.

Figure 252 MSE PM Report Page

2. For the PTP 820C and PTP 820C-HP, in the Interface field, select the radio for which you want to display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.
Table 32 describes the Modem MSE PMs.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
Modem MSE PM table and click View.

Table 32 Modem MSE PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Min MSE (dB) Displays the minimum MSE in dB, measured during the interval. A 0 in
this field and an X in the Integrity field may also indicate that the modem
was unlocked during the entire interval.

Phn 3963 013v000

Page 318
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Parameter Definition

Max MSE (dB) Displays the maximum MSE in dB, measured during the interval. A 0 in
this field and an X in the Integrity field may also indicate that the modem
was unlocked.

Exceed threshold seconds Displays the number of seconds the MSE exceeded the MSE PM threshold
during the interval. The MSE PM is configured in the Radio Thresholds
page. See Configuring BER Thresholds AND Displaying Cureent BER.

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time. An X and a 0 value in the Max MSE field may also
indicate that the modem was unlocked.

To set the Modem MSE PM thresholds, click Thresholds. The Modem MSE Thresholds Configuration– Edit Page
opens. For each radio, specify the modem MSE (Mean Square Error) threshold for calculating MSE Exceed
Threshold seconds, and click Apply.

Figure 253 Modem MSE Thresholds Configuration – Edit Page

Phn 3963 013v000

Page 319
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Displaying XPI PMs and Configuring XPI PM Threshold

Related topics:
• Configuring XPIC
To display XPI (Cross Polarization Interface) PMs per radio:
Select Radio > PM & Statistics > XPI. The XPI PM report page opens.

Note
The XPI page only appears if XPIC is configured on the unit.

Figure 254 XPI PM Report Page

4. In the Interface field, select the radio for which you want to display PMs.
5. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.

Table 33 describes the XPI PMs.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
Modem XPI PM table and click View.

Phn 3963 013v000

Page 320
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Table 33 XPI PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Min XPI (dB) The minimum XPI level that was measured during the interval.

Max XPI (dB) The maximum XPI level that was measured during the interval.

XPI below threshold The number of seconds the measured XPI level was below the threshold
seconds during the interval.

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

To set the XPI PM thresholds, click Thresholds. The XPI Thresholds Configuration– Edit Page opens. For each radio,
specify the modem XPI threshold for calculating XPI Exceed Threshold seconds, and click Apply.
Figure 255 XPI Thresholds Configuration – Edit Page

Phn 3963 013v000

Page 321
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Displaying Traffic PMs

This section includes:
• Displaying Capacity and Throughput PMs
• Displaying Utilization PMs
• Displaying Frame Error Rate PMs

Displaying Capacity and Throughput PMs

You can display PMs for capacity and throughput for a radio, based on:
• The total Layer 1 bandwidth (payload plus overheads) sent through the radio (Mbps).
• The total effective Layer 2 traffic sent through the radio.
You can also configure thresholds for capacity and throughput PMs. The number of seconds during which these
thresholds are exceeded are among the displayed PMs.
Peak counters display the maximum data rate for each interval, with a resolution of one second. This means the
PM mechanism records the number of bytes sent during each second of the interval and displays the number of
bytes for the highest one-second period during that interval. So, for example, when measuring 15-minute intervals,
the PM mechanism chooses the peak value from 900 recorded values in that interval (60 seconds multiplied by 15
60-second record periods).
Average counters display the average number of bytes received on the interface measured with a resolution of one
second. This means the PM mechanism divides the total number of bytes received during the interval by the total
number of seconds in the interval. So, for example, when measuring 15-minute intervals, the PM mechanism
divides the total number of bytes received during the 15-minute interval by 900.
To display capacity and throughput PMs per radio:
1. Select Radio > PM & Statistics > Traffic > Capacity/Throughput. The Capacity PM report page opens.

Figure 256 Capacity PM Report Page

Phn 3963 013v000

Page 322
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

2. For the PTP 820C and PTP 820C-HP, in the Port field, select the port that holds the radio for which you want to
display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.
To set the thresholds for capacity and throughput PMs:
1. Select Threshold. The Ethernet Radio Capacity & Throughput Threshold page opens.

Figure 257: Ethernet Radio Capacity and Throughput Threshold Page

o
2. Enter the capacity and throughput thresholds you want, in Mbps. The range of values is 0 to 4294967295. The
default value for is 1000.
3. Click Apply, then Close.

Table 34 describes the capacity and throughput PMs.

Phn 3963 013v000

Page 323
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
PM table and click View.

Table 34 Capacity/Throughput PMs

Parameter Definition

Time interval index For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Peak capacity (Mbps) Displays the highest L1 bandwidth, in Mbps, sent through the selected
radio during the measured time interval.

Average capacity (Mbps) Displays the average L1 bandwidth, in Mbps, during the measured time
interval.

Seconds exceeding Displays the number of seconds during the measured time interval during
Threshold which the L1 bandwidth exceeded the configured capacity threshold.

Peak throughput (Mbps) Displays the highest throughput, in Mbps, that occurred for the selected
radio during the measured time interval.

Average throughput Displays the average throughput, in Mbps, for the selected radio during
(Mbps) the measured time interval.

Seconds exceeding Displays the number of seconds during the measured time interval during
Threshold which the throughput exceeded the configured throughput threshold.

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

Displaying Utilization PMs

You can configure three radio capacity utilization thresholds, in percentage. The Utilization PM
Report displays, for each radio carrier and Multi-Carrier ABC group, the number of seconds in which
the radio or group exceeded each threshold in each interval. It also displays the peak and average
utilization, in percentage, per interval.
To display radio capacity utilization PMs per radio:
1. Select Radio > PM & Statistics > Traffic > Utilization. The Utilization PM report page opens.

Figure 258 Utilization PM Report Page

Phn 3963 013v000

Page 324
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

2. For the PTP 820C and PTP 820C-HP, in the Port field, select the port that holds the radio for which you want to
display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.

To set the thresholds for utilization PMs:

1 Select Threshold.
The Utilization Threshold page opens.
.
Figure 259 Ethernet Radio Utilization Threshold Page

1 2For each radio and Multi-Carrier ABC group, you can enter three thresholds, in % (1-100).
Utilization Threshold 1 should be the highest and Utilization Threshold 3 should be the lowest. The
default value for each threshold is 0.
3 Click Apply, then Close
Table 35 describes the capacity and throughput PMs.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
PM table and click View.

Phn 3963 013v000

Page 325
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Table 35 Utilization PMs

Parameter Definition

Time interval index For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Peak utilization (%) Indicates the highest utilization of the radio capacity that occurred for the
selected radio or group during the measured time interval.

Average utilization (%) Indicates the average utilization of the radio capacity for the selected
radio or group during the measured time interval.

Seconds exceeding Displays the number of seconds during the measured time interval during
Threshold which the L1 bandwidth exceeded the configured utilization threshold.

Seconds exceeding Displays the number of seconds during the measured time interval during
Threshold 2 which the L1 bandwidth exceeded Threshold 2.

Seconds exceeding Displays the number of seconds during the measured time interval during
Threshold 3 which the L1 bandwidth exceeded Threshold 3 (the lowest threshold).

Seconds below Threshold 3 Displays the number of seconds during the measured time interval during
which the L1 bandwidth was less than Threshold 3 (the lowest threshold).

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

Displaying Frame Error Rate PMs

To display frame error rate PMs per radio or Multi-Carrier ABC group:
1. Select Radio > PM & Statistics > Traffic > Frame error rate. The Frame error rate PM report page opens.

Phn 3963 013v000

Page 326
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Figure 260 Frame Error PM Report Page

2. For the PTP 820C and PTP 820C-HP, in the Port field, select the port that holds the radio for which you want to
display PMs.
3. In the Interval Type field:
o To display reports in 15-minute intervals, select 15 minutes.
o To display reports in daily intervals, select 24 hours.

Note
To display the same parameters for a specific interval in a separate page, select the interval in the
PM table and click View.

Table 36 Frame Error Rate PMs

Parameter Definition

Time interval index For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

FER Displays the frame error rate (%) during the measured time interval.

Phn 3963 013v000

Page 327
Chapter 5: Radio Configuration Configuring and Viewing Radio PMs and Statistics

Parameter Definition

Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the
values are not reliable due to a possible power surge or power failure that
occurred at that time.

Phn 3963 013v000

Page 328
Chapter 6: Ethernet Services and Interfaces
This section includes:
• Configuring Ethernet Service(s)
• Setting the MRU Size and the S-VLAN Ethertype
• Configuring Ethernet Interfaces
• Configuring Automatic State Propagation and Link Loss Forwarding.
• Viewing Ethernet PMs and Statistics
Related topics:
• Deleting a Multi-Carrier ABC Group
• Configuring Link Aggregation (LAG)Configuring Link Aggregation (LAG) and LACP
• Quality of Service (QoS)
• Ethernet Protocols
• Performing Ethernet Loopback

Phn 3963 013v000

Page 329
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Configuring Ethernet Service(s)

This section includes:

• Ethernet Services Overview
• General Guidelines for Provisioning Ethernet Services
• The Ethernet Services Page
• Adding an Ethernet Service
• Editing a Service
• Deleting a Service
• Enabling, Disabling, or Deleting Multiple Services
• Viewing Service Details
• Configuring Service Points

Ethernet Services Overview

Users can define up to 64 Ethernet services. Each service constitutes a virtual bridge that defines the connectivity
between logical ports in the PTP 820 network element.
This version of PTP 820 supports the following service types:
• Multipoint (MP)
• Point-to-Point (P2P)
• Management (MNG)
In addition to user-defined services, PTP 820 contains a pre-defined management service (Service ID 257). By
default, this service is operational.

Note
You can use the management service for in-band management. For instructions on configuring in-
band management, see Configuring In-Band Management.

A service point is a logical entity attached to a physical or logical interface. Service points define the movement of
frames through the service. Each service point includes both ingress and egress attributes. A Point-to-Point or
Multipoint service can hold up to 32 service points. A Management service can hold up 30 service points.
For a more detailed overview of PTP 820's service-oriented Ethernet switching engine, refer to the Technical
Description for the PTP 820 product type you are using.

General Guidelines for Provisioning Ethernet Services

When provisioning Ethernet services, it is recommended to follow these guidelines:

Phn 3963 013v000

Page 330
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

• Use the same Service ID for all service fragments along the path of the service.
• Do not re-use the same Service ID within the same region. A region is defined as consisting of all PTP 820
devices having Ethernet connectivity between them.
• Use meaningful EVC IDs.
• Give the same EVC ID (service name) to all service fragments along the path of the service.
• Do not reuse the same EVC ID within the same region.
It is recommended to follow these guidelines for creating service points:
• Always use SNP service points on NNI ports and SAP service points on UNI ports.
• For each logical interface associated with a specific service, there should never be more than a single service
point.
• The transport VLAN ID should be unique per service within a single region. That is, no two services should use
the same transport VLAN ID.

The Ethernet Services Page

The Ethernet Services page is the starting point for defining Ethernet services on the PTP 820.
To open the Ethernet Services page:
1. Select Ethernet > Services. The Ethernet Services page opens.

Figure 261 Ethernet Services Page

Figure 42 describes the parameters displayed in the Ethernet Services page.

Phn 3963 013v000

Page 331
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Table 37 Ethernet Services Page Parameters

Parameter Definition

Services ID A unique ID for the service.

Service Type The service type:

• MP – Multipoint
• P2P – Point-to-Point
• MNG – Management

Service sub type Indicates the type of service (Ethernet).

EVC ID The Ethernet Virtual Connection (EVC) ID. This parameter does not affect
the network element’s behavior, but is used by the NMS for topology
management.

EVC description The Ethernet Virtual Connection (EVC) description. This parameter does
not affect the network element’s behavior, but is used by the NMS for
topology management.

Admin Indicates whether the service is enabled (Operational) or disabled

(Reserved). You can configure services for later use by defining the
service as Reserved. In Reserved mode, the service occupies system
resources but is unable to transmit and receive data.

Adding an Ethernet Service

To add an Ethernet service:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. In the Ethernet Services page, click Add. The Ethernet Services – Add page opens.

Phn 3963 013v000

Page 332
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Figure 262 Ethernet Services - Add page

3. In the Service ID field, select a unique ID for the service. You can choose any unused value from 1 to 4095.
Once you have added the service, you cannot change the Service ID. Service ID 1025 is reserved for a
pre-defined management service.
4. In the Service Type field, select the service type:
o MP – Multipoint
o MNG – Management
o P2P – Point-to-Point
5. Optionally, in the EVC ID field, enter an Ethernet Virtual Connection (EVC) ID (up to 20 characters). This
parameter does not affect the network element’s behavior, but is used by the NMS for topology management.
6. Optionally, in the EVC Description field, enter a text description of the service (up to 64 characters). This
parameter does not affect the network element’s behavior, but is used by the NMS for topology management.
7. In the Admin field, select one of the following options:
o Operational - The service is functional.
o Reserved - The service is disabled until this parameter is changed to Operational. In
this mode, the service occupies system resources but is unable to receive and
transmit data.
8. In the MAC table size field, enter the maximum MAC address table size for the service. The MAC address table
is a source MAC address learning table used to forward frames from one service point to another. You can
select a value from 16 to 131,072, in multiples of 16. This maximum only applies to dynamic, not static, MAC
address table entries.

Phn 3963 013v000

Page 333
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Note
Additional configuration of the MAC address table can be performed via the CLI. See Defining the
MAC Address Forwarding Table for a Service.

9. In the Default CoS field, enter a default Class of Service (CoS) value (0-7). This value is assigned to frames at
the service level if CoS Mode is set to Default-CoS. Otherwise, this value is not used, and frames retain
whatever CoS value they were assigned at the service point or logical interface level.
10. In the CoS Mode field, select one of the following options. This parameter determines whether or not frames
passing through the service have their CoS modified at the service level. The CoS determines the priority
queue to which frames are assigned.
o Default CoS – Frames passing through the service are assigned the default CoS
defined above. This CoS value overrides whatever CoS may have been assigned at the
service point or interface level.
o Preserve-SP-COS-Decision – The CoS of frames passing through the service is not
modified by the service's default CoS.
11. Click Apply, then Close to close the Ethernet Services - Add page.
12. Add service points. You must add service points to the service in order for the service to carry traffic. See
Configuring Service Points.

Editing a Service
To edit a service:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the service in the Service Configuration Table.
3. In the Ethernet Services page, click Edit. The Ethernet Services - Edit page opens.
4. This page is identical to the Ethernet Services - Add page (Figure 190). You can edit any parameter that can be
configured in the Add page, except the Service ID.

Deleting a Service
Before deleting a service, you must first delete any service points attached to the service.
To delete a service:
1. Delete all service points attached to the service you wish to delete, as described in Deleting a Service Point.
2. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
3. Select the service in the Ethernet Service Configuration Table.
4. Click Delete. The service is deleted.

Enabling, Disabling, or Deleting Multiple Services

To enable, disable, or delete multiple services:

Phn 3963 013v000

Page 334
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the services in the Ethernet Services Configuration table, or select all the services by selecting the check
box in the top row.
o To enable the selected services, in the Multiple Selection Operation section
underneath the Ethernet Services Configuration Table, select Operational and click
Apply.
o To disable the selected services, in the Multiple Selection Operation section
underneath the Ethernet Services Configuration Table, select Reserved and click
Apply.
o To delete the selected services, select Delete underneath the Ethernet Services
Configuration Table. Before deleting a service, you must delete any service points
attached to the service, as described in Deleting a Service Point.

Figure 263 Multiple Selection Operation Section (Ethernet Services)

Note
When setting multiple services to Reserve state, make sure to avoid setting the management service
to Reserve state.

When setting multiple services to Reserve state, make sure to avoid setting the management service to Reserve
state

Viewing Service Details

To view the full service parameters:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the service in the Ethernet Services Configuration table.
3. In the Ethernet Services page, click Service Details. The Ethernet Services – Service Details page opens. The
Service Details page contains the same fields as the Add page (Figure 189). However, in the Service Details
page, these fields are read-only.

Configuring Service Points

This section includes:
• Ethernet Services Points Overview
• The Ethernet Service Points Page
• Adding a Service Point
• Editing a Service Point
• Deleting a Service Point

Phn 3963 013v000

Page 335
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

• Attaching VLANs

Ethernet Services Points Overview

Service points are logical interfaces within a service. A service point is a logical entity attached to a physical or
logical interface. Service points define the movement of frames through the service. Each service point includes
both ingress and egress attributes.
Each service point for a Point-to-Point or Multipoint service can be either a Service Access Point (SAP) or a Service
Network Point (SNP). A Point-to-Point service can also use Pipe service points.
• An SAP is equivalent to a UNI in MEF terminology and defines the connection of the user network with its
access points. SAPs are used for Point-to-Point and Multipoint traffic services.
• 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. SNPs are used for Point-to-Point and Multipoint traffic services.
• A Pipe service point is used to create traffic connectivity between two ports in a port-based manner (Smart
Pipe). In other words, all the traffic from one port passes to the other port.
Management services utilize Management (MNG) service points.
A Point-to-Point or Multipoint service can hold up to 32 service points. A management service can hold up to 30
service points.

The Ethernet Service Points Page

The Ethernet Service Points page is the starting point for configuring Ethernet service points.
To open the Ethernet Service Points page:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the relevant service in the Ethernet Services Configuration table.
3. Click Service Points. The Ethernet Service Points page opens.

Phn 3963 013v000

Page 336
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Figure 264 Ethernet Service Points Page

You can choose to display the following sets of attributes by selecting the appropriate button above the SP
Attributes table:

• General – See Ethernet Service Points – General SP Attributes Table

• Ingress – See 2. Ethernet Service Points – Ingress Attributes
• Egress – See 3. Ethernet Service Points – Egress Attributes
To return to the Ethernet Services page at any time, click Back to Services table at the top of the Ethernet Service
Points page.

1. Ethernet Service Points – General SP Attributes Table

The General SP Attributes table is shown in Figure 192 Ethernet Service Points Page. Table 38 describes the
parameters displayed in the General SP Attributes table.

Table 38 General Service Point Attributes

Parameter Definition

Service point ID This ID is unique within the service. For Point-to-Point and Multipoint
services, the range of values is 1-32. For Management services, the range
of values is 1-30.
When adding a service point, you can select a service point ID from the
available options in the Service point ID drop-down list in the Ethernet
Service Points – Add page. Once you have added the service point, you
cannot change the service point ID.

Service point name A descriptive name for the service point (optional). The Service Point
Name can be up to 20 characters.

Phn 3963 013v000

Page 337
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

Service point type The service point type. Options are:

• SAP – Service Access Point.
• SNP – Service Network Point.
• MNG – Management service point.
• PIPE – Pipe service point.
The following rules apply to the mixing of different types of service points
on a single logical interface:
You cannot configure both SAPs and SNPs on the same logical interface.
• You can configure both SAPs or SNPs on the same logical interface as
a MNG service point.
• If you configure a Pipe service point on an interface, you cannot
configure an SAP, SNP, or another Pipe service point on the same
interface. You can, however, configure an MNG service point on the
same interface.
• You cannot configure more than one MNG service point on a single
logical interface.
• Once you have added the service point, you cannot change this
parameter.

Interface location The physical or logical interface on which the service point is located.
Once you have added the service point, you cannot change this
parameter.

Attached interface type The encapsulation type (Ethertype) for frames entering the service point.
Once you have added the service point, you cannot change this
parameter.
The Attached Interface Type determines which frames enter the service
via this service point, based on the frame’s VLAN tagging. Since more than
one service point may be associated with a single interface, frames are
assigned to the earliest defined service point in case of conflict.
For a list of available Attached Interface Types, the types of frames to
which each one applies, and the service point types for which each one is
available, see Table 39.

C-Vlan encapsulation The C-VLAN classified into the service point. Options are 1-4094,
Untagged, or N.A. (Not Applicable). Once you have added the service
point, you cannot change this parameter.
If you selected Bundle-C in the Attached Interface Type field, select
Untagged or N.A. You can then add multiple C-VLANs via the Attach
VLAN option. See Attaching VLANs.

Phn 3963 013v000

Page 338
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

S-Vlan encapsulation The S-VLAN classified into the service point. Options are 1-4094,
Untagged, or N.A. (Not Applicable). Once you have added the service
point, you cannot change this parameter.
If you selected Bundle-S in the Attached Interface Type field, select the S-
VLAN value to classify into the service point (1-4094), or select Untagged.
You can then add multiple C-VLANs via the Attach VLAN option. See
Attaching VLANs.

Table 39 describes the available Attached Interface Types.

Table 39 Attached Interface Types

Attached Interface Type Types of Frames Available for Service

Point Types

dot1q A single C-VLAN is classified into the service All

point.

s-tag A single S-VLAN is classified into the service SNP, PIPE, and MNG
point.

Bundle-C A set of C-VLANs is classified into the service SAP

point.

Bundle-S A single S-VLAN and a set of C-VLANs are SAP

classified into the service point.

All-to-One All C-VLANs and untagged frames that enter SAP

the interface are classified into the service
point.

Q-in-Q A single S-VLAN and C-VLAN combination is SAP and MNG

classified into the service point.

2. Ethernet Service Points – Ingress Attributes

Select Ingress in the Ethernet Service Points page to display the Ethernet Service Points – Ingress Attributes table.
Table 40 describes the parameters displayed in the Ingress SP Attributes table.

Phn 3963 013v000

Page 339
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Figure 265 Ethernet Service Points Page – Ingress Attributes

Table 40 Service Point Ingress Attributes

Parameter Definition

Service point ID This ID is unique within the service. For Point-to-Point and Multipoint
services, the range of values is 1-32. For Management services, the range
of values is 1-30.

Service point name A descriptive name for the service point (optional). The Service Point
Name can be up to 20 characters.

Service point type The service point type. Options are:

• SAP – Service Access Point.
• SNP – Service Network Point.
• MNG – Management service point.
• PIPE – Pipe service point.

Learning admin Determines whether MAC address learning for incoming frames is
enabled (Enable) or disabled (Disable). When enabled, the service point
learns the source MAC addresses of incoming frames and adds them to a
MAC address forwarding table.

Allow flooding Determines whether incoming frames with unknown MAC addresses are
forwarded to other service points via flooding. Select Allow to allow
flooding or Disable to disable flooding.

Allow broadcast Indicates whether frames with a broadcast destination MAC address are
allowed to ingress the service via this service point. Select Allow to allow
broadcast or Disable to disable broadcast.

Phn 3963 013v000

Page 340
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

CoS Mode Indicates how the service point handles the CoS of frames that pass
through the service point. Options are:
• Default CoS – The service point re-defines the CoS of frames that pass
through the service point, according to the Default CoS (below). This
decision can be overwritten on the service level.
• Interface-Decision – The service point preserves the CoS decision
made at the interface level. The decision can still be overwritten at
the service level.
• MAC DA - The service point checks each frame against a list of user-
defined MAC DAs. If there is a match, the service point applies to the
frame the CoS and Color defined for that MAC DA. If there is no
match, the service point preserves the CoS decision made at the
interface level. See Classification Overview.
Note: For Bundle-S and Bundle-C service points, if Cos Overwrite
Valid is set to True, the CoS and Color defined in the Attached VLAN
page has priority over the interface decision, but not over a MAC DA
match.

Default CoS The default CoS. If the CoS Mode is sp-def-cos, this is the CoS assigned to
frames that pass through the service point. This decision can be
overwritten at the service level. Possible values are 0 to 7.

Split horizon group Reserved for future use.

3. Ethernet Service Points – Egress Attributes

Select Egress in the Ethernet Service Points page to display the Ethernet Service Points – Egress Attributes table.
Table 41 `describes the parameters displayed in the General SP Attributes table.
Figure 266 Ethernet Service Points Page – Egress Attributes

Table 41 Service Point Egress Attributes

Phn 3963 013v000

Page 341
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

Service point ID This ID is unique within the service. For Point-to-Point and Multipoint
services, the range of values is 1-32. For Management services, the range
of values is 1-30.

Service point name A descriptive name for the service point (optional). The Service Point
Name can be up to 20 characters.

Service point type The service point type. Options are:

• SAP – Service Access Point.
• SNP – Service Network Point.
• MNG – Management service point.
• PIPE – Pipe service point.

C-Vlan CoS preservation Determines whether the original C-VLAN CoS value is preserved or
restored for frames egressing from the service point.
• If C-VLAN CoS preservation 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.
• If C-VLAN CoS preservation is disabled, the C-VLAN CoS value of
frames egressing the service point is set at whatever value might
have been re-assigned by the interface, service point, or service, or
whatever value results from marking (see Marking admin, below).

C-Vlan preservation Determines whether the original C-VLAN ID is preserved or restored for
frames egressing from the service point.
• If C-VLAN preservation is enabled, the C-VLAN ID of frames egressing
the service point is the same as the C-VLAN ID when the frame
entered the service.
• If C-VLAN preservation is disabled, the C-VLAN ID of frames egressing
the service point is set at whatever value might have been re-
assigned by the interface, service point, or service, or whatever value
results from marking (see Marking admin, below).

S-Vlan CoS preservation Determines whether the original S-VLAN CoS value is preserved or
restored for frames egressing from the service point.
If S-VLAN CoS preservation is enabled, the S-VLAN CoS value of frames
egressing the service point is the same as the value when the frame
entered the service.
If S-VLAN CoS preservation is disabled, the C-VLAN CoS value of frames
egressing the service point is set at whatever value might have been
re-assigned by the interface, service point, or service, or whatever value
results from marking

Phn 3963 013v000

Page 342
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

S-Vlan preservation Read-only. Indicates whether the original S-VLAN ID is preserved or

restored for frames egressing from the service point.
If S-VLAN preservation is enabled, the S-VLAN ID of frames egressing the
service point is the same as the S-VLAN ID when the frame entered the
service.
If S-VLAN preservation is disabled, the S-VLAN ID of frames egressing the
service point is set at whatever value might have been re-assigned by the
interface, service point, or service, or whatever value results from
marking

Marking admin Determines whether re-marking of the outer VLAN (C-VLAN or S-VLAN) of
tagged frames that pass through the service point is enabled.
If Marking admin is set to Enable, and CoS preservation for the relevant
outer VLAN is set to Disable, the SAP re-marks the C-VLAN or S-VLAN
802.1p UP bits of egress frames according to the calculated CoS and
Color, and the user-configurable 802.1Q and 802.1AD marking tables. You
can configure these tables by selecting Ethernet > QoS > Marking from
the menu on the left side of the Web EMS.
If Marking admin and CoS preservation for the relevant outer VLAN are
both set to Enable, re-marking is not performed.
If Marking admin and CoS preservation for the relevant outer VLAN are
both set to Disable, re-marking is applied, but only according to the
values defined for Green frames in the 802.1Q and 802.1AD marking
tables.

Service Bundle ID This can be used to assign one of the available service bundles from the
H-QoS hierarchy queues to the service point. This enables you to
personalize the QoS egress path. Permitted values are 1-63.

Adding a Service Point

To add a service point:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the relevant service in the Ethernet Services Configuration table.
3. Click Service Points. The Ethernet Service Points page opens (Figure 192).
4. Select the relevant service point in the Ethernet Services Points – General SP Attributes table.
5. Click Add. The Ethernet Service Points – Add page opens.

Phn 3963 013v000

Page 343
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Figure 267 Ethernet Service Points - Add Page

6. Configure the service point attributes, as described in Table 38, Table 40, and Table 41.

Phn 3963 013v000

Page 344
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Note
Optionally, you can select from a list of pre-defined service point options in the Pre defined options
field at the top of the Ethernet Service Points - Add page. The system automatically populates the
remaining service point parameters according to the system-defined parameters. However, you can
manually change these parameter values. The pre-defined options are customized to the type of
service to which you are adding the service point.

7. Click Apply, then Close.

Editing a Service Point

To edit a service point:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the relevant service in the Ethernet Services Configuration table.
3. Click Service Points. The Ethernet Service Points page opens (Figure 192).
4. Select the relevant service point in the Ethernet Services Points – General SP Attributes table.
5. Click Edit. The Ethernet Service Points– Edit page opens. The Ethernet Service Points – Edit page is similar to
the Ethernet Service Points - Add page (Figure 195). You can edit any parameter that can be configured in the
Add Service Point page, except Service Point ID, Service Point Type, and the General SP Attributes.
6. Edit the service point attributes, as described in Table 38, Table 40, and Table 41.
7. Click Apply, then Close.

Deleting a Service Point

You can only delete a service point with an Attached Interface Type of Bundle-C or Bundle-S if no VLANs are
attached to the service point. See Attaching VLANs.
To delete a service point:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the relevant service in the Ethernet Services Configuration table.
3. Click Service Points. The Ethernet Service Points page opens (Figure 192).
4. Select the relevant service point in the Ethernet Services Points – General SP Attributes table.
5. Click Delete. The service point is deleted.

Attaching VLANs
When the Attached Interface Type for a service point is set to Bundle-C or Bundle-S, you can add multiple C-VLANs
to the service point.
To add multiple C-VLANs:
1. Select Ethernet > Services. The Ethernet Services page opens (Figure 189).
2. Select the relevant service in the Ethernet Services Configuration table.
3. Click Service Points. The Ethernet Service Points page opens (Figure 192).

Phn 3963 013v000

Page 345
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

4. Select the relevant service point in the Ethernet Services Points – General SP Attributes table.
5. Click Attached VLAN. The Attached VLAN List page opens.

Figure 268 Attached VLAN List Page

6. Click Add. The Attached VLAN List - Add page opens.

Phn 3963 013v000

Page 346
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Figure 269 Attached VLAN List - Add Page

7. Configure the VLAN Classification parameters, described in Table 42.

8. Click Apply, then Close.

Table 42 VLAN Classification Parameters

Parameter Definition

Interface Location Read-only. The physical or logical interface on which the service point is
located.

Service ID Read-only. The ID of the service to which the service point belongs.

Service Point ID Read-only. The ID of the service point.

C-Vlan Encapsulation Select the C-VLAN you want to add to the service point.

S-Vlan Encapsulation Read-only.

If the Attached Interface Type for the service point is Bundle-S, this field
displays the S-VLAN encapsulation selected when the service point was
created.
If the Attached Interface Type for the service point is Bundle-C, this field
is inactive.

Phn 3963 013v000

Page 347
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Service(s)

Parameter Definition

CoS Overwrite Valid If you want to assign a specific CoS and Color to frames with the C-VLAN
or S-VLAN defined in the C-VLAN Encapsulation field, select true. This CoS
and Color values defined below override the CoS and Color decisions
made at the interface level. However, if the service point or service are
configured to apply their own CoS and Color decisions, those decisions
override the decision made here.

CoS Value If CoS Overwrite Valid is set to true, the CoS value defined in this field is
applied to frames with the C-VLAN defined in the C-VLAN Encapsulation
field. This CoS overrides the CoS decision made at the interface level.
However, if the service point or service are configured to apply their own
CoS, that decision overrides the decision made here.
If CoS Overwrite Valid is set to false, this parameter has no effect.

Color If CoS Overwrite Valid is set to true, the Color value defined in this field is
applied to frames with the C-VLAN defined in the C-VLAN Encapsulation
field. This Color overrides the Color decision made at the interface level.
However, if the service point or service are configured to apply their own
Color, that decision overrides the decision made here.
If CoS Overwrite Valid is set to false, this parameter has no effect.

To edit a VLAN Classification table entry, select the entry in the VLAN Classification table and click Edit. You can
edit all the fields that can be configured in the Attached VLAN List – Add page, except the C-VLAN Encapsulation
field.
To delete a VLAN Classification table entry, select the entry in the VLAN Classification table and click Delete.

Phn 3963 013v000

Page 348
Chapter 6: Ethernet Services and Interfaces Setting the MRU Size and the S-VLAN Ethertype

Setting the MRU Size and the S-VLAN Ethertype

To configure the size of the MRU (Maximum Receive Unit) and the S-VLAN Ethertype:
1. Select Ethernet > General Configuration. The Ethernet General Configuration page opens.

Figure 270 Ethernet General Configuration Page

2. In the MRU field, enter the global size (in bytes) of the Maximum Receive Unit (MRU). Permitted values are 64
to 9612. The default value is 2000. Frames that are larger than the global MRU will be discarded.
3. In the S VLAN Ether type field, select the S-VLAN Ethertype. This defines the ethertype recognized by the
system as the S-VLAN ethertype. Options are: 0x8100, 0x88A8, 0x9100, and 0x9200. The default value is
0x88A8.

Note
The C-VLAN Ethertype is set at 0x8100 and cannot be modified.

4. Click Apply.

Phn 3963 013v000

Page 349
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Interfaces

Configuring Ethernet Interfaces

Related Topics:
• Enabling the Interfaces (Interface Manager)
• Performing Ethernet Loopback
• Configuring Ethernet Service(s)
• Quality of Service (QoS)
The PTP 820’s switching fabric distinguishes between physical interfaces and logical interfaces. Physical and logical
interfaces serve different purposes in the switching fabric. In some cases, a physical interface corresponds to a
logical interface on a one-to-one basis. For some features, such as LAG, a group of physical interfaces can be joined
into a single logical interface.
The basic interface characteristics, such as media type, port speed, duplex, and auto-negotiation, are configured
for the physical interface via the Physical Interfaces page. Ethernet services, QoS, and OAM characteristics are
configured on the logical interface level.
To configure the physical interface parameters:
1. Select Ethernet > Interfaces > Physical Interfaces. The Physical Interfaces page opens.

Note
Ethernet: Slot 1, Port 4 is only used for P4 on an IP-20C 2E2SX unit
when used as a traffic port. When P4 is used as an Extension port, it is not displayed at all.

Figure 271 Physical Interfaces Page

2. Select the interface you want to configure and click Edit. The Physical Interfaces - Edit page opens.

Phn 3963 013v000

Page 350
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Interfaces

Figure 272 Physical Interfaces - Edit Page

3. Optionally, in the Description field, enter a description of the interface.

4. In the Media type field, select the physical interface layer 1 media type. Options are:
o Auto-Type – NA.
o RJ45 – An electrical (RJ-45) Ethernet interface.
o SFP – An optical (SFP) Ethernet interface.
o Radio – A radio interface.
In the Auto negotiation field, select On to enable or Off to disable Auto-Negotiation. When the
Media-Type is Radio, Auto Negotiation is always Off. Auto negotiation should not be used for 100
Mbps SFP interfaces.

5. In the Speed field, select the maximum speed of the interface. In Mbps Options are:
o Ethernet RJ-45 interfaces –100 and 1000.
o Ethernet SFP interfaces – Only 1000is supported.
o Ethernet SFP+ interfaces (PTP 820E R2H ESP models only) – Only
o 1000 and 10000 are supported.
o Radio interfaces – The parameter is read-only and set by the system to 1000FD.

Note
To use an SFP+ interface in 10G mode, the third-party switch must be running Pause Frame Flow
Control, as defined in IEEE 802.3x. It is also recommended to configure shapers on the third-party
switch so as to limit the packet flow from the switch to the PTP 820E unit to 2.5 Gbps.
After changing the speed of an SFP+ interface, you must reset the unit in order for the change to take
effect.

Phn 3963 013v000

Page 351
Chapter 6: Ethernet Services and Interfaces Configuring Ethernet Interfaces

When an SFP interface is configured for 100 Mbps, the link must be symmetric, i.e., the same
interface speed must be configured on both sides of the link.

7. In the Duplex field, select the interface's duplex setting (Full-Duplex or Half-Duplex). Only Full-Duplex is
available in this release.
8. Click Apply, then Close.
Table 43 describes the status parameters that appear in the Physical Interfaces page.
Table 43 Physical Interface Status Parameters

Parameter Definition

Interface location The location of the interface.

Operational Status Indicates whether the interface is currently operational (Up) or non-
operational (Down).

Admin Status Indicates whether the interface is currently enabled (Up) or disabled
(Down). You can enable or disable an interface from the Interface
Manager page. See Enabling the Interfaces (Interface Manager).

Media Type The physical interface layer 1 media type.

Actual port speed Displays the actual speed of the interface for the link as agreed by the
two sides of the link after the auto negotiation process.

Actual port duplex Displays the actual duplex status of the interface for the link as agreed by
the two sides of the link after the auto negotiation process.

Phn 3963 013v000

Page 352
Chapter 6: Ethernet Services and Interfaces Configuring Automatic State Propagation and Link Loss
Forwarding

Configuring Automatic State Propagation and Link

Loss Forwarding

Automatic state propagation enables propagation of radio failures back to the Ethernet port. You can also
configure Automatic State Propagation to close the Ethernet port based on a radio failure at the remote carrier.
Automatic state propagation is configured as pairs of interfaces. Each interface pair includes one Monitored
Interface and one Controlled Interface. You can create multiple pairs using the same monitored interface and
multiple controlled interfaces.
The Monitored Interface is a radio interface, or a radio protection or Multi-Carrier ABC group. The Controlled
Interface is an Ethernet interface or LAG. An Ethernet interface can only be assigned to one Monitored interface.
Each Controlled Interface is assigned an LLF ID. If ASP trigger by remote fault is enabled on the remote side of the
link, the ASP state of the Controlled Interface is propagated to the Controlled Interface with the same LLF ID at the
remote side of the link. This means if ASP is triggered locally, it is propagated to the remote side of the link, but
only to Controlled Interfaces with LLF IDs that match the LLF IDs of the affected Controlled Interfaces on the local
side of the link.

Note
LLF requires an activation key (SL-LLF). Without this activation key, only LLF ID 1 is available. See
Configuring the Activation Key.

The following events in the Monitored Interface trigger ASP:

• Radio LOF
• Radio Excessive BER
• Remote Radio LOF
• Remote Excessive BER
• Remove LOC
The user can also configure the ASP pair so that Radio LOF, Radio Excessive BER, or loss of the Ethernet connection
at the remote side of the link will also trigger ASP.
In addition, ASP is triggered if the Controlled Interface is a LAG, and the physical interfaces that belong to the LAG
are set to Admin = Down in the Interface Manager.
When a triggering event takes place:
• If the Controlled Interface is an electrical GbE port, the port is closed.
• If the Controlled Interface is an optical GbE port, the port is muted.
The Controlled Interface remains closed or muted until all triggering events are cleared.
In addition, when a local triggering event takes place, the ASP mechanism sends an indication to the remote side of
the link. Even when no triggering event has taken place, the ASP mechanism sends periodic update messages
indicating that no triggering event has taken place.

Phn 3963 013v000

Page 353
Chapter 6: Ethernet Services and Interfaces Configuring Automatic State Propagation and Link Loss
Forwarding

A trigger delay time can be configured, so that when a triggering event takes place, the ASP mechanism does not
propagate the event until this delay time has elapsed. A trigger delay from 0 to 10,000 ms can be set per LLD ID.
The delay time must be configured via CLI. See Configuring Automatic State Propogation and Link Loss Forwarding
(CLI).
It is recommended to configure both ends of the link to the same Automatic State Propagation configuration.
To configure an Automatic State Propagation interface pair:
1. Select Ethernet > Interfaces > Automatic State Propagation. The Automatic State Propagation page opens.
Figure 273 Automatic State Propagation Page

2. Click Add. The Automatic State Propagation - Add page opens.

Figure 274 Automatic State Propagation - Add Page

3. In the Controlled Ethernet interface field, select an interface that will be disabled upon failure of the
Monitored Radio Interface, defined below.
4. In the Monitored Radio interface field, select the Monitored Radio Interface. The Controlled Ethernet
Interface, defined above, is disabled upon a failure indication on the Monitored Radio Interface.
5. In the ASP admin field, select Enable to enable Automatic State Propagation on the interface pair, or Disable
to disable Automatic State Propagation on the pair.

Phn 3963 013v000

Page 354
Chapter 6: Ethernet Services and Interfaces Configuring Automatic State Propagation and Link Loss
Forwarding

6. Optionally, in theASP trigger by remote fault field, select Enable if you want to configure the system to disable
the Controlled Ethernet Interface upon a radio failure at the remote side of the link from the Monitored Radio
Interface. ASP events will only be propagated to Controlled Interfaces with LLF IDs that match LLF IDs of
affected Controlled Interfaces at the other side of the link.
7. Optionally, in the ASP management Safe mode admin field, select Enable or Disable to enable or disable
management Safe mode. In management Safe mode, the ASP mechanism does not physically shut down the
Controlled Interface when ASP is triggered. Instead, the ASP mechanism sends a failure indication message.
This message is used to propagate the failure indication to external equipment.

Note
CSF mode must be enabled when ASP is configured on the
management port of an PTP 820E
When ASP Management Safe mode (CSF) is configured, the peer unit must be configured to
receive CSF PDUs. CSF receive must be enabled in order for G.8032 ERPI topology changes to
be initiated upon receipt of a CSF PDU. This must be configured via the CLI. For details, see
Configuring Receipt of CSF PDUs (CLI).

8. In the ASP LLF ID field, select an ID for Link Loss Forwarding (LLF). When ASP trigger by remote fault is set to
Enable, ASP events at the other side of the link are propagated to Controlled Interfaces with LLF IDs that
match the LLF IDs of affected Controlled Interfaces at the other side of the link. LLF IDs are unique per
Monitored Interface. That is, if LLF ID 1 has been used for a Controlled Interface that is grouped with radio
interface 1, that ID cannot be used again for another Controlled Interface grouped fixed radio interface 1.
However, it can be used for Controlled Interface grouped with radio interface 2. You can select an LLF ID
between 1 and 30.
9. Repeat this procedure to assign additional Controlled Interfaces to the Monitored Interface, or to set up
additional ASP pair with other interfaces. Controlled Interfaces can only be assigned to one ASP pair.
Monitored Interfaces can be assigned to multiple ASP pairs.
To edit an Automatic State Propagation interface pair:
1. Select the interface pair in the Automatic state propagation configuration table.
2. Click Edit. The Automatic State Propagation – Edit page opens. The Edit page is similar to the Add page (Figure
202), but the Controlled Ethernet Interface and Monitored Radio Interface parameters are read-only.
To delete an Automatic State Propagation interface pair:
1. Select the interface pair in the Automatic state propagation configuration table.
2. Click Delete. The interface pair is removed from the Automatic state propagation configuration table.
To delete multiple interface pairs:
1. Select the interface pairs in the Automatic state propagation configuration table or select all the interfaces by
selecting the check box in the top row.
2. Click Delete. The interface pairs are removed from the Automatic state propagation configuration table.

Phn 3963 013v000

Page 355
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Viewing Ethernet PMs and Statistics

PTP 820 stores and displays statistics in accordance with RMON and RMON2 standards. You can display various
peak TX and RX rates (per second) and average TX and RX rates (per second), both in bytes and in packets, for each
measured time interval. You can also display the number of seconds in the interval during which TX and RX rates
exceeded the configured threshold.
This section includes:
• RMON Statistics
• Egress CoS Statistics
• Port TX Statistics
• Port RX Statistics

RMON Statistics
To view and reset RMON statistics:
1. Select Ethernet > PM & Statistics > RMON. The RMON page opens.

Figure 275 RMON Page

• To clear the statistics, click Clear All at the bottom of the page.
• To refresh the statistics, click Refresh at the bottom of the page.
Each column in the RMON page displays RMON statistics for one of the unit’s interfaces. To hide or display
columns:
1. In the header row, select the arrow next to any of the columns.
2. Select Columns.
3. Mark the interfaces you want to display and clear the interfaces you do not want to display.

Figure 276 RMON Page – Hiding and Displaying Columns

Phn 3963 013v000

Page 356
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Egress CoS Statistics

You can display packet egress statistics per CoS value. For each CoS value, the following statistics are displayed per
Color (Green and Yellow):
• Number of packets transmitted
• Number of packets dropped
• Number of bytes transmitted
• Number of bytes dropped

Note
Transmitted bits per second are not supported in the current release.

To display egress CoS statistics:

1. Select Ethernet > PM & Statistics > Egress CoS Statistics. The Egress CoS Statistics page opens.

Phn 3963 013v000

Page 357
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Figure 277 Egress Cos Statistics Page

2. In the Show Service bundle ID field, select 1.

Note
Service Bundles are bundles of queues, grouped together in order to configure common egress
characteristics for specific services. In the current release, only Service Bundle 1 is supported.

By default, the egress CoS statistics are cumulative. That is, they are not automatically cleared. You can set each
individual CoS number to be cleared whenever the Egress CoS Statistics page is opened by changing the Clear on
read value to Yes.
3. To change the clear on read value, select the CoS number in the CoS queue index column and click Edit. The
Egress CoS Statistics – Edit page opens.

Phn 3963 013v000

Page 358
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Figure 278 Egress CoS Statistics – Edit Page

4. In the Clear on read field, select Yes to have statistics for the CoS value cleared every time you open the page.
5. Click Apply.

Port TX Statistics
The Ethernet Port TX PM report page displays PMs that measure various peak transmission rates (per second) and
average transmission rates (per second), both in bytes and in packets, for each measured time interval.
The page also displays the number of seconds in the interval during which transmission rates exceeded the
configured threshold.
This section includes:
• Displaying Ethernet Port TX PMs
• Enabling or Disabling Gathering of Port TX PM Statistics per Interface
• Setting the Ethernet Port TX Threshold

Displaying Ethernet Port TX PMs

To display Ethernet Port TX PMs:
1. Select Ethernet > PM & Statistics > Port TX. The Ethernet Port TX PM Report page opens.
Figure 279 Ethernet Port TX PM Report Page

Phn 3963 013v000

Page 359
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

2. In the Interface field, select the interface for which you want to display PMs.
3. In the Interval Type field:
o To display reports for the past 24 hours, in 15 minute intervals, select 15 minutes.
o To display reports for the past month, in daily intervals, select 24 hours.
Table 44 describes the Ethernet TX port PMs.

Table 44 Ethernet TX Port PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Peak... Average... bytes... Various peak transmission rates (per second) and average transmission
Packets... rates (per second), both in bytes and in packets, for each measured time
interval.

TX bytes Layer 1 exceed The number of seconds the TX bytes exceeded the specified threshold
threshold (sec) during the interval. For instructions on setting the threshold, see Setting
the Ethernet Port TX Threshold.

Invalid data flag Indicates whether the values received during the measured interval are
valid. An x in the column indicates that the values are not valid (for
example, because of a power surge or power failure that occurred during
the interval).

To clear the PMs, click Clear All.

Phn 3963 013v000

Page 360
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Enabling or Disabling Gathering of Port TX PM Statistics per Interface

To select the interfaces for which to gather and display Port TX PMs:
1. In the Ethernet Port TX PM Report page, click PM Admin. The Ethernet PM Port Admin page opens.
Figure 280 Ethernet PM Port Admin Page

2. Select the interface.

3. Click Enable Port PM or Disable Port PM to enable or disable the gathering of Port TX PMs on the selected
interface.
4. Click Close.

Phn 3963 013v000

Page 361
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Setting the Ethernet Port TX Threshold

The TX bytes Layer 1 exceed threshold (sec) column shows, for each interval, the number of seconds the TX bytes
exceeded the specified threshold during the interval:
To view and set this threshold:
1. In the Ethernet Port TX PM Report page, click Threshold. The Ethernet Port Tx Threshold page opens.

Figure 281 Ethernet Port Tx Threshold Page

2. Enter a threshold, between 0 and 4294967295.

3. Click Apply, then Close.

Port RX Statistics
The Ethernet Port RX PM report page displays PMs that measure various peak transmission rates (per second) and
average RX rates (per second), both in bytes and in packets, for each measured time interval.
The page also displays the number of seconds in the interval during which RX rates exceeded the configured
threshold.
This section includes:
• Displaying Ethernet Port RX PMs
• Enabling or Disabling Gathering of Port RX PM Statistics per Interface
• Setting the Ethernet Port RX Threshold

Displaying Ethernet Port RX PMs

To display Ethernet Port RX PMs:
1. Select Ethernet > PM & Statistics > Port RX. The Ethernet Port RX PM Report page opens.

Phn 3963 013v000

Page 362
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Figure 282: Ethernet Port RX PM Report Page

2. In the Interface field, select the interface for which you want to display PMs.
3. In the Interval Type field:
o To display reports for the past 24 hours, in 15 minute intervals, select 15 minutes.
o To display reports for the past month, in daily intervals, select 24 hours.
Table 45 describes the Ethernet RX port PMs.

Table 45 Ethernet RX Port PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Peak... Average... bytes... Various peak transmission rates (per second) and average RX rates (per
Packets... second), both in bytes and in packets, for each measured time interval.

RX bytes Layer 1 exceed The number of seconds the RX bytes exceeded the specified threshold
threshold (sec) during the interval. For instructions on setting the threshold, see Setting
the Ethernet Port RX Threshold.

Invalid data flag Indicates whether the values received during the measured interval are
valid. An x in the column indicates that the values are not valid (for
example, because of a power surge or power failure that occurred during
the interval).

To clear the PMs, click Clear All.

Enabling or Disabling Gathering of Port RX PM Statistics per Interface

To select the interfaces for which to gather and display Port RX PMs:
1. In the Ethernet Port RX PM Report page, click PM Admin. The Ethernet PM Port Admin page opens.

Phn 3963 013v000

Page 363
Chapter 6: Ethernet Services and Interfaces Viewing Ethernet PMs and Statistics

Figure 283 Ethernet PM Port Admin Page

2. Select the interface.

3. Click Enable Port PM or Disable Port PM to enable or disable the gathering of Port RX PMs on the selected
interface.
4. Click Close.

Setting the Ethernet Port RX Threshold

The RX bytes Layer 1 exceed threshold (sec) column shows for each interval, the number of seconds the RX bytes
exceeded the specified threshold during the interval:
To view and set this threshold:
1. In the Ethernet Port RX PM Report page, click Threshold. The Ethernet Port Rx Threshold page opens.

Figure 284 Ethernet Port Rx Threshold Page

2. Enter a threshold, between 0 and 4294967295.

3. Click Apply, then Close.

Phn 3963 013v000

Page 364
Chapter 7: Quality of Service (QoS) Viewing Ethernet PMs and Statistics

Chapter 7: Quality of Service (QoS)

This section includes:
• QoS Overview
• Configuring Classification
• Configuring Policers (Rate Metering)
• Configuring Marking
• Configuring WRED
• Configuring Egress Shaping
• Configuring Scheduling
• Configuring and Displaying Queue-Level PMs

Note
You can display QoS egress statistics, but only via CLI. For information, see Displaying Egress Statistics
(CLI).

Phn 3963 013v000

Page 365
Chapter 7: Quality of Service (QoS) QoS Overview

QoS Overview

Quality of Service (QoS) deals with the way frames are handled within the switching fabric. QoS is required in order to
deal with many different network scenarios, such as traffic congestion, packet availability, and delay restrictions.
PTP 820’s personalized QoS enables operators to handle a wide and diverse range of scenarios. PTP 820’s smart QoS
mechanism operates from the frame’s ingress into the switching fabric until the moment the frame egresses via the
destination port.
QoS capability is very important due to the diverse topologies that exist in today’s network scenarios. These can
include, for example, streams from two different ports that egress via single port, or a port-to-port connection that
holds hundreds of services. In each topology, a customized approach to handling QoS will provide the best results.
Figure 213 shows the basic flow of PTP 820’s QoS mechanism. Traffic ingresses (left to right) via the Ethernet or radio
interfaces, on the “ingress path.” Based on the services model, the system determines how to route the traffic. Traffic
is then directed to the most appropriate output queue via the “egress path.”

Figure 285 QoS Block Diagram

Egress
Ingress
Marker
Rate Limit (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS

Egress
Ingress
Marker
Rate Limit (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
Standard QoS/ H-QoS

Egress
Ingress CET/Pipe Marker
Rate Limit Services (Optional)
GE/Radio Port Classifier
(Policing) Queue Scheduler/
Manager Shaper
Port GE/Radio
(Optional)
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,
service point, and service. The classifier determines the exact traffic stream and associates it with the
appropriate service. It also calculates an ingress frame CoS and Color. CoS and Color classification can be
performed on three levels, according to the user’s configuration.
• Ingress Rate Metering – A hierarchical mechanism that deals with ingress traffic on three different levels:
interface, service point, and service point CoS. The rate metering mechanism enables the system to measure the
incoming frame rate on different levels using a TrTCM standard MEF rate meter, and to determine whether to
modify the color calculated during the classification stage.

The egress path consists of the following QoS building blocks:

• Queue Manager – This is the mechanism responsible for managing the transmission queues, utilizing smart
WRED per queue and per packet color (Green or Yellow).
• Scheduling and Shaping – A hierarchical mechanism that is responsible for scheduling the transmission of frames
from the transmission queues, based on priority among queues, Weighted Fair Queuing (WFQ) in bytes per each
transmission queue, and eligibility to transmit based on required shaping on several different levels (per queue,
per service bundle, and per port).

Phn 3963 013v000

Page 366
Chapter 7: Quality of Service (QoS) QoS Overview

• Marker – This mechanism provides the ability to modify priority bits in frames based on the calculated CoS and
Color.
For a more detailed description of QoS in the PTP 820, refer to the Technical Description for the PTP 820 product type
you are using.

Phn 3963 013v000

Page 367
Chapter 7: Quality of Service (QoS) Configuring Classification

Configuring Classification

The hierarchical classifier consists of the following levels:

• Logical interface-level classification
• Service point-level classification
• Service level classification
This section explains how to configure classification at the logical interface level.
• For instructions how to configure classification at the service point level, see 2. Ethernet Service Points – Ingress
Attributes.
• For instructions how to configure classification at the service level, see Adding an Ethernet Service.
This section includes:
• Classification Overview
• Configuring Ingress Path Classification on a Logical Interface
• Modifying the C-VLAN 802.1Q UP and CFI Bit Classification Table
• Modifying the S-VLAN 802.1 UP and DEI Bit Classification Table
• Modifying the DSCP Classification Table
• Modifying the MPLS EXP Bit Classification Table
• Modifying the MAC DA Classification Table
In addition to the procedures described in this section, you can specify a specific CoS and Color for a specific VLAN ID.
This is the highest classification priority on the logical interface level, and overrides any other classification criteria at
the logical interface level. Classification by VLAN ID can only be configured via CLI. See Configuring VLAN Classification
and Override (CLI).

Classification Overview
PTP 820 supports a hierarchical classification mechanism. The classification mechanism examines incoming frames
and determines their CoS and Color. The benefit of hierarchical classification is that it provides the ability to “zoom
in” or “zoom out”, enabling classification at higher or lower levels of the hierarchy. The nature of each traffic stream
defines which level of the hierarchical classifier to apply, or whether to use several levels of the classification
hierarchy in parallel.
Classification takes place on the logical interface level according to the following priorities:
• VLAN ID (CLI-only – see Configuring VLAN Classification and Override (CLI))
• 802.1p bits
• DSCP bits
• MPLS EXP field
• Default interface CoS
PTP 820 performs the classification on each frame ingressing the system via the logical interface. Classification is
performed step by step from the highest priority to the lowest priority classification method. Once a match is found,
the classifier determines the CoS and Color decision for the frame for the logical interface-level.
For example, if the frame is an untagged IP Ethernet frame, a match will not be found until the third priority level
(DSCP). The CoS and Color values defined for the frame’s DSCP value will be applied to the frame.

Phn 3963 013v000

Page 368
Chapter 7: Quality of Service (QoS) Configuring Classification

You can disable some of these classification methods by configuring them as un-trusted. For example, if 802.1p
classification is configured as un-trusted for a specific interface, the classification mechanism does not perform
classification by UP bits. This is useful, for example, if classification is based on DSCP priority bits.
If no match is found at the logical interface level, the default CoS is applied to incoming frames at this level. In this
case, the Color of the frame is assumed to be Green.
Classification may also be performed by Destination MAC Address (MAC DA) at the service point level. When MAC DA
classification is enabled on a service point, the classification mechanism checks each frame ingressing the interface on
which the service point is defined against a list of user-defined MAC DAs. If there is a match, the mechanism applies
to the frame the CoS and Color defined for that MAC DA. Classification by MAC DA overrides the other classification
criteria at the service point level.
Up to 64 MAC addresses can be defined per device, including four predefined MAC addresses. You can assign each of
these MAC addresses a CoS value and a Color.
The following MAC addresses are predefined, with a high priority (CoS=7, Color=Green). You can edit or delete these
MAC addresses:
• 09:00:2B:00:00:04
• 09:00:2B:00:00:05
• 01:80:C2:00:00:14
• 01:80:C2:00:00:15
These are protocol MAC addresses used to transport IS-IS frames as defined in ISO 9542 and ISO/IEC 10589.

Configuring Ingress Path Classification on a Logical Interface

This section explains how to configure the classification criteria per each logical interface. The following sections
explain how to modify the classification tables per bit type.
To configure the classification criteria for a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens.

Figure 286 Logical Interfaces Page

2. Select the interface you want to configure and click Edit. The Logical Interfaces - Edit page opens.

Phn 3963 013v000

Page 369
Chapter 7: Quality of Service (QoS) Configuring Classification

Figure 287 Logical Interfaces - Edit Page

3. Configure the parameters described in Table 46.

4. Click Apply, then Close.

Note
The Ingress byte compensation and Egress byte compensation fields are described in Configuring
the Ingress and Egress Byte Compensation.

Table 46 Logical Interface Classification Parameters

Parameter Definition

Trust VLAN UP bits Select the interface's trust mode for user priority (UP) bits:
Trust – The interface performs QoS and color classification according to
UP and CFI/DEI bits according to user-configurable tables for 802.1q UP
bits (C-VLAN frames) or 802.1AD UP bits (S-VLAN frames). VLAN UP bit
classification has priority over DSCP and MPLS classification, so that if a
match is found with the UP bit of the ingressing frame, DSCP values and
MPLS bits are not considered.
Un-Trust – The interface does not consider 802.1 UP bits during
classification.

Trust DSCP Select the interface's trust mode for DSCP:

Trust – The interface performs QoS and color classification according to a
user-configurable table for DSCP to CoS and color classification. DSCP
classification has priority over MPLS classification, so that if a match is
found with the DSCP value of the ingressing frame, MPLS bits are not
considered.
Un-Trust – The interface does not consider DSCP during classification.

Phn 3963 013v000

Page 370
Chapter 7: Quality of Service (QoS) Configuring Classification

Parameter Definition

Trust MPLS Select the interface's trust mode for MPLS bits:
Trust – The interface performs QoS and color classification according to a
user-configurable table for MPLS EXP to CoS and color classification.
Un-Trust – The interface does not consider MPLS bits during
classification.

Default port CoS Select the default CoS value for frames passing through the interface (0 to
7). This value can be overwritten on the service point and service level.

Modifying the C-VLAN 802.1Q UP and CFI Bit Classification

Table
To modify the classification criteria for 802.1Q User Priority (UP) bits:
1. Select Ethernet > QoS > Classification > 802.1Q. The 802.1Q Classification page opens.

Phn 3963 013v000

Page 371
Chapter 7: Quality of Service (QoS) Configuring Classification

Figure 288 802.1Q Classification Page

2. Select the row you want to modify and click Edit. The 802.1Q Classification – Edit page opens.

Figure 289 802.1Q Classification - Edit Page

3. Modify the parameters you want to change:

o 802.1Q UP – Read-only. The User Priority (UP) bit to be mapped.
o 802.1Q CFI – Read-only. The CFI bit to be mapped.
o 802.1Q CoS – The CoS assigned to frames with the designated UP and CFI.
o 802.1Q Color – The Color assigned to frames with the designated UP and CFI.
4. Click Apply, then Close.

Modifying the S-VLAN 802.1 UP and DEI Bit Classification Table

To modify the classification criteria for 802.1AD User Priority (UP) bits:

Phn 3963 013v000

Page 372
Chapter 7: Quality of Service (QoS) Configuring Classification

1. Select Ethernet > QoS > Classification > 802.1AD. The 802.1AD Classification page opens.

Figure 290 802.1AD Classification Page

2. Select the row you want to modify and click Edit. The 802.1AD Classification - Edit page opens.
Figure 291 802.1Q Classification - Edit Page

3. Modify the parameters you want to change:

o 802.1AD UP – Read-only. The User Priority (UP) bit to be mapped.
o 802.1ADQ DEI – Read-only. The DEI bit to be mapped.
o 802.1AD CoS – The CoS assigned to frames with the designated UP and DEI.
o 802.1AD Color – The Color assigned to frames with the designated UP and DEI.
4. Click Apply, then Close.

Modifying the DSCP Classification Table

You can configure the classification criteria for Differentiated Service Code Point (DSCP) priority values. The DSCP is a
6-bit length field inside the IP datagram header carrying priority information. Classification by DSCP can be used for
untagged frames, as well as 802.1Q tagged or provider VLAN tagged frames.
PTP 820 units have a DSCP classification table with 24 pre-defined entries. Each entry includes the following criteria:
Phn 3963 013v000
Page 373
Chapter 7: Quality of Service (QoS) Configuring Classification

• DSCP – The DSCP value to be mapped.

• Binary – The binary representation of the DSCP value.
• Description – A description of the DSCP value.
• CoS – The CoS assigned to frames with the designated DSCP value.
• Color – The Color assigned to frames with the designated DSCP value.
You can modify the Description, CoS, and Color for any of the pre-defined entries. You can also add and delete
entries. The maximum number of entries is 32.

To modify the classification criteria for DSCPs:

1. Select Ethernet > QoS > Classification > DSCP. The DSCP Classification page opens.

Figure 292 DSCP Classification Page

2. Select the row you want to modify and click Edit. The DSCP Classification - Edit page opens.

Figure 293 DSCP Classification - Edit Page

3. Modify the parameters you want to change:

Phn 3963 013v000

Page 374
Chapter 7: Quality of Service (QoS) Configuring Classification

o DSCP – Read-only. The DSCP value to be mapped.

o Binary – Read-only. The binary representation of the DSCP value.
o Description – Read-only. The description of the DSCP value.
o CoS – The CoS assigned to frames with the designated DSCP value.
o Color – The Color assigned to frames with the designated DSCP value.
4. Click Apply, then Close.
To add an entry to the DSCP Classification table:
1. Select Ethernet > QoS > Classification > DSCP. The DSCP Classification page opens (Figure 260).
2. Click Add. The DSCP Classification - Add page opens.
Figure 294: DSCP Classification - Add Page

3. In the DSCP field, select the DSCP value you want to add. The Binary field is automatically adjusted to display the
binary representation of the DSCP value you selected.

Phn 3963 013v000

Page 375
Chapter 7: Quality of Service (QoS) Configuring Classification

4. In the Description field, enter a description of the DSCP entry.

5. In the CoS field, select a CoS value to assign to frames with the designated DSCP value.
6. In the Color field, select a Color to assign to frames with the designated DSCP value.
7. Click Apply.
To delete an entry from the DSCP Classification table:
1. Select Ethernet > QoS > Classification > DSCP. The DSCP Classification page opens (Figure 260).
2. Select the row you want to modify and click Delete. A confirmation window opens.
3. Click OK. The entry is deleted.

Modifying the MPLS EXP Bit Classification Table

MPLS bits are used to provide QoS capabilities by utilizing the bits set in the MPLS labels. Classification by MPLS
bits is supported in both untagged and 802.1Q provider-tagged frames.
To modify the classification criteria for MPLS EXP bits:
1. Select Ethernet > QoS > Classification > MPLS. The MPLS Classification page opens.

Figure 295 MPLS Classification Page

Phn 3963 013v000

Page 376
Chapter 7: Quality of Service (QoS) Configuring Classification

2. Select the row you want to modify and click Edit. The MPLS Classification - Edit page opens.

Figure 296 MPLS Classification - Edit Page

3. Modify the parameters you want to change:

o MPLS EXP – Read-only. The MPLS (experimental) bit to be mapped.
o CoS – The CoS assigned to frames with the designated MPLS EXP value.
o Color – The Color assigned to frames with the designated MPLS EXP value.
4. Click Apply, then Close.

Phn 3963 013v000

Page 377
Chapter 7: Quality of Service (QoS) Configuring Classification

Modifying the MAC DA Classification Table

You can determine whether classification is performed by MAC DA in the CoS Mode field of the service point’s
Ingress Parameters page. See Classification Overview.
To add an entry to the MAC DA Classification Table:
1 Select Ethernet > QoS > Classification > MAC DA. The MAC DA Classification page opens.

Figure 297 MAC DA Classification Page

2 Click Add. The MAC DA Classification – Add page opens.

Figure 298 MAC DA Classification – Add Page

Phn 3963 013v000

Page 378
Chapter 7: Quality of Service (QoS) Configuring Classification

3 In the Destination MAC Address field, enter the MAC address.

4 In the CoS field, enter the CoS to be assigned to frames with this MAC DA.
5 In the Color field, enter the Color to be assigned to frames with this MAC DA.
6 Click Apply, then Close.
To modify an entry in the MAC DA Classification Table:
1 In the MAC DA Classification page, select the row you want to modify and click Edit. The MAC DA Classification
– Edit page opens.

Figure 299 MAC DA Classification – Edit Page

2 Modify the parameters you want to change:
• CoS – The CoS assigned to frames with this MAC DA.
• Color – The Color assigned to frames with this MAC DA.
3 Click Apply, then Close.
To delete an entry from the MAC DA Classification Table:
1 In the MAC DA Classification page, select the row you want to delete and click Delete. A confirmation window
opens.
2 Click OK.

Phn 3963 013v000

Page 379
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

Configuring Policers (Rate Metering)

This section includes:

• Policer (Rate Metering) Overview
• Configuring Policer Profiles
• Assigning Policers to Interfaces
• Configuring the Ingress and Egress Byte Compensation

Policer (Rate Metering) Overview

The PTP 820 switching fabric supports hierarchical policing on the logical interface level. You can define up to 250
rate meter (policer) profiles.

Note
Policing on the service point level, and the service point and CoS level, is planned for future release.

PTP 820's policer mechanism is based on a dual leaky bucket mechanism (TrTCM). The policers can change a
frame’s color and CoS settings based on CIR/EIR + CBS/EBS, which makes the policer mechanism a key tool for
implementing bandwidth profiles and enabling operators to meet strict SLA requirements.
The output of the policers is a suggested color for the inspected frame. Based on this color, the queue
management mechanism decides whether to drop the frame or to pass it to the queue.

Configuring Policer Profiles

This section includes:
• Adding a Policer Profile
• Editing a Policer Profile
• Deleting a Policer Profile

Adding a Policer Profile

To add a policer profile:
1. Select Ethernet > QoS > Policer > Policer Profile. The Policer Profile page opens.

Phn 3963 013v000

Page 380
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

Figure 300 Policer Profile Page

2. Click Add. The Policer Profile - Add page opens.

Figure 301 Policer Profile - Add Page

3. Configure the profile’s parameters. See Table 47 Policer Profile Parameters for a description of the policer
profile parameters.
4. Click Apply, then Close.

Phn 3963 013v000

Page 381
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

Table 47 Policer Profile Parameters

Parameter Definition

Profile ID A unique ID for the policer profile. You can choose from any unused value
from 1 to 250. Once you have added the profile, you cannot change the
Profile ID.

Description A description of the policer profile.

Policer type Read-only. The type of policer. Always set to MEF-TRTCM.

CIR Enter the Committed Information Rate (CIR) for the policer, in bits per
second. Permitted values are 0, or 64,000 through 1,000,000,000 bps. If
the value is 0, all incoming CIR traffic is dropped.

CBS Enter the Committed Burst Rate (CBR) for the policer, in Kbytes.
Permitted values are 0 through 8192 Kbytes.

EIR Enter the Excess Information Rate (EIR) for the policer, in bits per second.
Permitted values are 0, or 64,000 through 1,000,000,000 bps. If the value
is 0, all incoming EIR traffic is dropped.

EBS Enter the Excess Burst Rate (EBR) for the policer, in Kbytes. Permitted
values are 0 through 8192 Kbytes.

Color mode Select how the policer treats packets that ingress with a CFI or DEI field
set to 1 (yellow). Options are:
Color Aware – All packets that ingress with a CFI/DEI field set to 1
(yellow) are treated as EIR packets, even if credits remain in the CIR
bucket.
Color Blind – All ingress packets are treated as green regardless of their
CFI/DEI value. A color-blind policer discards any former color decisions.

Coupling flag Select Enable or Disable. When enabled, frames that ingress as yellow
may be converted to green when there are no available yellow credits in
the EIR bucket. Coupling Flag is only relevant in Color Aware mode.

Editing a Policer Profile

To edit a policer profile, select the profile in the Police Profile table and click Edit. The Policer Profile Table Edit
page opens.
The Policer Profile Table - Edit page is identical to the Policer Profile Table - Add page (Figure 228). You can edit any
parameter that can be configured in the Policer Profile Table Add page, except the Profile ID.

Deleting a Policer Profile

You cannot delete a policer profile that is attached to a logical interface. You must first remove the profile from the
logical interface, then delete the profile. See Assigning Policers to Interfaces.
To delete a policer profile, select the profile in the Police Profile table and click Delete. The profile is deleted.

Phn 3963 013v000

Page 382
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

To delete multiple policer profiles:

1. Select the profiles in the Policer Profile table or select all the profiles by selecting the check box in the top row.
2. Click Delete. The profiles are deleted.

Assigning Policers to Interfaces

To assign policers to a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select the interface in the Ethernet Logical Port Configuration table and click Policers. The Policers page
opens.

Figure 302 Logical Interfaces – Policers Page – Unicast Policer (Default)

For a logical interface, you can assign policers to the following traffic flows:
• Unicast Policer
• Multicast Policer
• Broadcast Policer
• Ethertype Policers

Assigning Unicast Policers

To assign a policer for unicast traffic to a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select the interface in the Ethernet Logical Port Configuration Table and click Policers. The Policers page
opens. By default, the Policers page opens to the Unicast Policer table (Figure 229).
3. In the Policer profile field, select a profile from the policer profiles defined in the system. The Policer profile
drop-down list includes the ID and description of all defined profiles.

Phn 3963 013v000

Page 383
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

4. In the Unicast admin field, select Enable to enable policing on unicast traffic flows from the logical interface,
or Disable to disable policing on unicast traffic flows from the logical interface.
5. Click Apply.

Assigning Multicast Policers

To assign a policer for multicast traffic to a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select the interface in the Ethernet Logical Port Configuration table and click Policers. The Policers page opens.
By default, the Policers page opens to the Unicast Policer table (Figure 229).
3. Select Multicast Policer. The Multicast Policer table appears.

Figure 303 Logical Interfaces – Policers Page – Multicast Policer

4. In the Policer profile field, select a profile from the policer profiles defined in the system. The Policer profile
drop-down list includes the ID and description of all defined profiles.
5. In the Multicast admin field, select Enable to enable policing on multicast traffic flows from the logical
interface, or Disable to disable policing on multicast traffic flows from the logical interface.
6. Click Apply.

Assigning Broadcast Policers

To assign a policer for broadcast traffic to a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).

Phn 3963 013v000

Page 384
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

2. Select the interface in the Ethernet Logical Port Configuration table and click Policers. The Policers page
opens. By default, the Policers page opens to the Unicast Policer table (Figure 229).
3. Select Broadcast Policer. The Broadcast Policer table appears.
Figure 304 Logical Interfaces – Policers Page – Broadcast Policer

4. In the Policer profile field, select a profile from the policer profiles defined in the system. The Policer profile
drop-down list includes the ID and description of all defined profiles.
5. In the Broadcast admin field, select Enable to enable policing on broadcast traffic flows from the logical
interface, or Disable to disable policing on broadcast traffic flows from the logical interface.
6. Click Apply.

Assigning Ethertype Policers

You can define up to three policers per Ethertype value.
To assign a policer to an Ethertype:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select the interface in the Ethernet Logical Port Configuration Table and click Policers. The Policers page
opens. By default, the Policers page opens to the Unicast Policer table (Figure 229).
3. Select Ethertype type 1 Policer. The Ethertype type 1 Policer table appears.

Figure 305 Logical Interfaces – Policers Page – Ethertype Policer

Phn 3963 013v000

Page 385
Chapter 7: Quality of Service (QoS) Configuring Policers (Rate Metering)

4. In the Ethertype 1 profile field, select a profile from the policer profiles defined in the system. The Ethertype 1
profile drop-down list includes the ID and description of all defined profiles.
5. In the Ethertype 1 user value field, enter the Ethertype value to which you want to apply this policer. The field
length is 4 nibbles (for example, 0x0806 - ARP).
6. In the Ethertype 1 admin field, select Enable to enable policing on the logical interface for the specified
ethertype, or Disable to disable policing on the logical interface for the specified ethertype.
7. Click Apply.
8. To assign policers to additional Ethertypes, select Ethertype type 2 Policer and Ethertype type 3 Policer and
repeat the steps above.

Configuring the Ingress and Egress Byte Compensation

You can define the ingress and egress byte compensation value per logical interface. The policer attached to the
interface uses these values to compensate for Layer 1 non-effective traffic bytes.
To define the ingress byte compensation value for a logical interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select the interface you want to configure and click Edit. The Logical Interfaces - Edit page opens (Figure 215).
3. In the Ingress byte compensation field, enter the ingress byte compensation value, in bytes. Permitted values
are 0 to 32 bytes. The default value is 20 bytes.
4. In the Egress byte compensation field, enter the egress byte compensation value, in bytes. Permitted values
are 0 to 32 bytes. The default value is 0 bytes. Only even values are permitted.
5. Click Apply, then Close.

Phn 3963 013v000

Page 386
Chapter 7: Quality of Service (QoS) Configuring Marking

Configuring Marking
This section includes:
• Marking Overview
• Enabling Marking
• Modifying the 802.1Q Marking Table
• Modifying the 802.1AD Marking Table

Marking Overview
When enabled, PTP 820's marking mechanism modifies each frame’s 802.1p UP bit and CFI/DEI bits according to
the classifier decision. The CFI/DEI (color) field is modified according to the classifier and policer decision. The color
is first determined by a classifier and may be later overwritten by a policer. Green color is represented by a CFI/DEI
value of 0, and Yellow color is represented by a CFI/DEI value of 1. Marking is performed on egress frames that are
VLAN-tagged.
The marking is performed according to global mapping tables that describe the 802.1p UP bits and the CFI bits (for
C-VLAN tags) or DEI bits (for S VLAN tags). The marking bit in the service point egress attributes determines
whether the frame is marked as green or according to the calculated color.

Note
The calculated color is sent to the queue manager regardless of whether the marking bit is set.

Regular marking is only performed when:

• The outer frame is S-VLAN, and S-VLAN CoS preservation is disabled, or
• The outer frame is C-VLAN, and C-VLAN CoS preservation is disabled.
If marking and CoS preservation for the relevant outer VLAN are both disabled, special marking is applied. Special
marking means that marking is performed, but only according to the values defined for Green frames in the
802.1Q and 802.1AD marking tables.
When marking is performed, the C-VLAN or S-VLAN 802.1p UP bits are re-marked according to the calculated CoS
and color, and the mapping table for C-VLAN or S-VLAN.

Enabling Marking
Marking is enabled and disabled on the service point level. See 3. Ethernet Service Points – Egress Attributes.

Modifying the 802.1Q Marking Table

The 802.1Q Marking table enables you to modify the CoS to UP and CFI bit mapping that is implemented when
marking is enabled.
To modify the 802.1Q Marking table:

Phn 3963 013v000

Page 387
Chapter 7: Quality of Service (QoS) Configuring Marking

1. Select Ethernet > QoS > Marking > 802.1Q. The 802.1Q Marking page opens. Each row in the 802.1Q Marking
page represents a CoS and color combination.

Figure 306 802.1Q Marking Page

2. Select the row you want to modify and click Edit. The 802.1Q Marking - Edit page opens.

Figure 307 802.1Q Marking - Edit Page

3. Enter the new 802.1Q UP and 802.1Q CFI values.

4. Click Apply, then Close.

Phn 3963 013v000

Page 388
Chapter 7: Quality of Service (QoS) Configuring Marking

Modifying the 802.1AD Marking Table

The 802.1AD Marking table enables you to modify the CoS to UP and DEI bit mapping that is implemented when
marking is enabled.
To modify the 802.1AD Marking table:
1. Select Ethernet > QoS > Marking > 802.1AD. The 802.1AD Marking page opens. Each row in the 802.1AD
Marking page represents a CoS and color combination.

Figure 308 802.1AD Marking Page

2. Select the row you want to modify and click Edit. The 802.1AD Marking - Edit page opens.

Figure 309 802.1AD Marking - Edit Page

3. Enter the new 802.1AD UP and 802.1AD DEI values.

Phn 3963 013v000

Page 389
Chapter 7: Quality of Service (QoS) Configuring Marking

4. Click Apply, then Close.

Phn 3963 013v000

Page 390
Chapter 7: Quality of Service (QoS) Configuring WRED

Configuring WRED

This section includes:

• WRED Overview
• Configuring WRED Profiles
• Assigning WRED Profiles to Queues

WRED Overview
Weighted Random Early Detection (WRED) enables differentiation between higher and lower priority traffic based
on CoS. You can define up to 30 WRED profiles. Each profile contains a green traffic curve and a yellow traffic
curve. This curve describes the probability of randomly dropping frames as a function of queue occupancy.
The system also includes two pre-defined read-only profiles. These profiles are assigned profile IDs 31 and 32.
• Profile number 31 defines a tail-drop curve and is configured with the following values:
o 100% Yellow traffic drop after 64kbytes occupancy.
o 100% Green traffic drop after 128kbytes occupancy.
o Yellow maximum drop is 100%
o Green maximum drop is 100%
• Profile number 32 defines a profile in which all will be dropped. It is for internal use and should not be applied
to traffic.
A WRED profile can be assigned to each queue. The WRED profile assigned to the queue determines whether or
not to drop incoming packets according to the occupancy of the queue. As the queue occupancy grows, the
probability of dropping each incoming frame increases as well. As a consequence, statistically more TCP flows will
be restrained before traffic congestion occurs.

Configuring WRED Profiles

This section includes:
• Adding a WRED Profile
• Editing a WRED Profile
• Deleting a WRED Profile

Adding a WRED Profile

To add a WRED profile:
1. Select Ethernet > QoS > WRED > WRED Profile. The WRED Profile page opens.

Phn 3963 013v000

Page 391
Chapter 7: Quality of Service (QoS) Configuring WRED

Figure 310 WRED Profile Page

2. Click ADD. The WRED Profile - Add page opens, with default values displayed.

Figure 311 WRED Profile - Add Page

3. In the WRED Profile ID field, select a unique ID to identify the profile. Permitted values are 1-30.
4. In the Green curve min point field, enter the minimum throughput of green packets for queues with this
profile, in Kbytes (0-8192). When this value is reached, the system begins dropping green packets in the
queue.
5. In the Green curve max point field, enter the maximum throughput of green packets for queues with this
profile, in Kbytes (0-8192). When this value is reached, all green packets in the queue are dropped.
6. In the Green curve max drop ratio field, enter the maximum percentage (1-100) of dropped green packets for
queues with this profile.
7. In the Yellow curve min point field, enter the minimum throughput of yellow packets for queues with this
profile, in Kbytes (0-8192). When this value is reached, the system begins dropping yellow packets in the
queue.

Phn 3963 013v000

Page 392
Chapter 7: Quality of Service (QoS) Configuring WRED

8. In the Yellow curve max point field, enter the maximum throughput of yellow packets for queues with this
profile, in Kbytes (0-8192). After this value is reached, all yellow packets in the queue are dropped.
9. In the Yellow curve max drop ratio field, enter the maximum percentage (1-100) of dropped yellow packets
for queues with this profile.
10. Click Apply, then Close.

Editing a WRED Profile

To edit a WRED profile:
1. Select Ethernet > QoS > WRED > WRED Profile. The WRED Profile page opens ().
2. Select the profile you want to edit and click Edit. The WRED Profile – Edit page opens. This page is similar to
the WRED Profile – Add page (Figure 238). You can edit any parameter except the WRED Profile ID.
3. Modify the profile.
4. Click Apply, then Close.

Deleting a WRED Profile

You cannot delete a WRED profile that is assigned to a queue. You must first remove the WRED profile from the
queue, then delete the WRED profile. See Assigning WRED Profiles to Queues.
To delete a WRED profile, select the profile in the WRED Profile Configuration table (Figure 237) and click Delete.
The profile is deleted.
To delete multiple WRED profiles:
1. Select the profiles in the WRED Profile Configuration table or select all the profiles by selecting the check box
in the top row.
2. Click Delete. The profiles are deleted.

Phn 3963 013v000

Page 393
Chapter 7: Quality of Service (QoS) Configuring WRED

Assigning WRED Profiles to Queues

To assign a WRED profile to a queue:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click WRED. The WRED page opens.

Figure 312 Logical Interfaces – WRED Page

3. In the Show Service bundle ID field, select 1.

Note
Service Bundles are bundles of queues, grouped together in order to configure common egress
characteristics for specific services. In the current release, only Service Bundle 1 is supported.

4. Select a CoS Queue ID and click Edit. The Logical Interfaces – WRED – Edit page opens.

Figure 313: Logical Interfaces – WRED - Edit Page

5. In the Profile ID field, select the WRED profile you want to assign to the selected queue.
6. Click Apply, then Close.

Phn 3963 013v000

Page 394
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Configuring Egress Shaping

This section includes:
• Egress Shaping Overview
• Configuring Queue Shaper Profiles
• Configuring Service Bundle Shaper Profiles
• Assigning a Queue Shaper Profile to a Queue
• Assigning a Service Bundle Shaper Profile to a Service Bundle

Egress Shaping Overview

Egress shaping determines the traffic profile for each queue. PTP 820 can perform queue shaping on the following
levels:
• Queue Level – Single leaky bucket shaping. On the queue level, you can configure up to 31 single leaky bucket
shaper profiles. If no profile is attached to the queue, no egress shaping is performed on that queue.
• Service Bundle Level – Dual leaky bucket shaping. On the service bundle level, users can configure up to 256
dual leaky bucket shaper profiles. If no profile is attached to the service bundle, no egress shaping is
performed on that service bundle.
• Interface Level – Single leaky bucket shaping.

Note
Egress shaping on the interface level is planned for future release.

Configuring Queue Shaper Profiles

This section includes:
• Adding a Queue Shaper Profile
• Editing a Queue Shaper Profile
• Deleting a Queue Shaper Profile

Adding a Queue Shaper Profile

To add a queue shaper profile:
1. Select Ethernet > QoS > Shaper > Queue Profiles. The Queue Shaper Profile page opens.

Phn 3963 013v000

Page 395
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Figure 314 Queue Shaper Profile Page

2. Click Add. The Queue Shaper – Add page opens, with default values displayed.

Figure 315 Queue Shaper Profile – Add Page

3. In the Profile ID field, select a unique ID to identify the profile. Permitted values are 1-31.
4. Optionally, in the Description field, enter a description of the profile.
5. In the CIR field, enter the Committed Information Rate (CIR) assigned to the profile, in bits per second.
Permitted values are:
o 16,000 - 32,000,000 bps, with granularity of 16,000.
o 32,000,000 - 131,008,000 bps, with granularity of 64,000.
6. Click Apply, then Close.

Editing a Queue Shaper Profile

To edit a queue shaper profile:
1. Select Ethernet > QoS > Shaper > Queue Profiles. The Queue Shaper Profile page opens (Figure 241).

Phn 3963 013v000

Page 396
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

2. Select the profile you want to edit and click Edit. The Queue Shaper Profile – Edit page opens. This page is
similar to the Queue Shaper Profile – Add page (Figure 242). You can edit any parameter except the Profile ID.
3. Modify the profile.
4. Click Apply, then Close.

Deleting a Queue Shaper Profile

You cannot delete a queue shaper profile that is assigned to a queue. You must first remove the profile from the
queue, then delete the profile. See Assigning a Queue Shaper Profile to a Queue.
To delete a queue shaper profile, select the profile in the Queue Shaper Profiles Configuration table (Figure 241)
and click Delete. The profile is deleted.
To delete multiple queue shaper profiles:
1. Select the profiles in the Queue Shaper Profiles Configuration table or select all the profiles by selecting the
check box in the top row.
2. Click Delete. The profiles are deleted.

Configuring Service Bundle Shaper Profiles

This section includes:
• Adding a Service Bundle Shaper Profile
• Editing a Service Bundle Shaper Profile
• Deleting a Service Bundle Shaper Profile

Adding a Service Bundle Shaper Profile

To add a service bundle shaper profile:
1. Select Ethernet > QoS > Shaper > Service Bundle Profiles. The Service Bundle Shaper Profile page opens.

Phn 3963 013v000

Page 397
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Figure 316 Service Bundle Shaper Profile Page

2. Click Add. The Service Bundle Shaper Profile – Add page opens, with default values displayed.

Figure 317 Service Bundle Shaper Profile – Add Page

3. In the Profile ID field, select a unique ID to identify the profile. Permitted values are 1-31.
4. Optionally, in the Description field, enter a description of the profile.
5. In the CIR field, enter the Committed Information Rate (CIR) assigned to the profile, in bits per second.
Permitted values are:
o 0 – 32,000,000 bps, with granularity of 16,000.
o 32,000,000 – 1,000,000,000 bps, with granularity of 64,000.
6. In the PIR field, enter the Peak Information Rate (PIR) assigned to the profile, in bits per second. Permitted
values are:
o 16,000 – 32,000,000 bps, with granularity of 16,000.
o 32,000,000 – 1,000,000,000 bps, with granularity of 64,000.
7. Click Apply, then Close.

Phn 3963 013v000

Page 398
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Editing a Service Bundle Shaper Profile

To edit a service bundle shaper profile:
1. Select Ethernet > QoS > Shaper > Service Bundle Profiles. The Service Bundle Shaper Profile page opens
(Figure 243).
2. Select the profile you want to edit and click Edit. The Service Bundle Shaper Profile – Edit page opens. This
page is similar to the Service Bundle Shaper Profile – Add page (Figure 244). You can edit any parameter
except the Profile ID.
3. Modify the profile.
4. Click Apply, then Close.

Deleting a Service Bundle Shaper Profile

You cannot delete a service bundle shaper profile that is assigned to a service bundle. You must first remove the
profile from the service bundle, then delete the profile.
To delete a service bundle shaper profile, select the profile in the Service Bundle Shaper Profiles Configuration
table (Figure 243) and click Delete. The profile is deleted.
To delete multiple service bundle shaper profiles:
1. Select the profiles in the Service Bundle Shaper Profiles Configuration table or select all the profiles by
selecting the check box in the top row.
2. Click Delete. The profiles are deleted.

Assigning a Queue Shaper Profile to a Queue

To assign a queue shaper profile to a queue:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Shaper. The Logical Interfaces –
Shaper page opens, with the Egress Queue Shaper Configuration table open by default. All queue shaper
profiles defined in the system are listed in the table.

Phn 3963 013v000

Page 399
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Figure 318 Logical Interfaces – Shaper – Egress Queue Shaper

3. Click Add. The Egress Queue Shaper Configuration – Add page opens.

Figure 319 Logical Interfaces – Egress Queue Shaper Configuration – Add Page

Note
In this release, only one service bundle (Service Bundle ID 1) is supported.

4. In the CoS queue ID field, select the CoS queue ID of the queue to which you want to assign the shaper.
Queues are numbered according to CoS value, from 0 to 7.
5. In the Profile ID field, select from a list of configured queue shaper profiles. See Configuring Queue Shaper
Profiles.

Phn 3963 013v000

Page 400
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

6. In the Shaper Admin field, select Enable to enable egress queue shaping for the selected queue, or Disable to
disable egress queue shaping for the selected queue.
7. Click Apply, then Close.
To assign a different queue shaper profile to a queue:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Shaper. The Logical Interfaces –
Shaper page opens, with the Egress Queue Shaper Configuration table open by default (Figure 245).
3. Select an interface in the Ethernet Logical Port Configuration table and click Shaper. The Logical Interfaces –
Shaper page opens, with the Egress Queue Shaper Configuration table open by default (Figure 245).
4. Select the row you want to edit and click Edit. The Egress Queue Shaper Configuration – Edit page opens. This
page is similar to the Egress Queue Shaper Configuration – Add page (Figure 246).
5. To assign a different egress queue shaper profile, select the profile in the Profile ID field.
6. To enable or disable egress queue shaping for the selected queue, select Enable to enable egress queue
shaping for the queue, or Disable to disable egress queue shaping for the queue.
7. Click Apply, then Close.

Assigning a Service Bundle Shaper Profile to a Service Bundle

To assign a service bundle shaper profile to a service bundle:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Shaper. The Logical Interfaces –
Shaper page opens, with the Egress Queue Shaper Configuration table open by default (Figure 245).
3. Select Egress Service Bundle Shaper. The Egress Service Bundle Shaper Configuration table appears. All service
bundle shaper profiles defined in the system are listed in the table.

Phn 3963 013v000

Page 401
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Figure 320 Logical Interfaces – Shaper – Egress Service Bundle Shaper

4. Click Add. The Egress Service Bundle Shaper Configuration – Add page opens.

Phn 3963 013v000

Page 402
Chapter 7: Quality of Service (QoS) Configuring Egress Shaping

Figure 321 Logical Interfaces – Egress Service Bundle Shaper Configuration – Add Page

Note
In this release, only one service bundle (Service Bundle ID 1) is supported.

5. In the Profile ID field, select from a list of configured service bundle shaper profiles. See Configuring Service
Bundle Shaper Profiles.
6. In the Shaper Admin field, select Enable to enable egress service bundle shaping, or Disable to disable egress
service bundle shaping.
7. Click Apply, then Close.
To assign a different service bundle shaper profile:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Shaper. The Logical Interfaces –
Shaper page opens, with the Egress Queue Shaper Configuration table open by default (Figure 245).
3. Select Egress Service Bundle Shaper. The Egress Service Bundle Shaper Configuration table appears (Figure
247). All service bundle shaper profiles defined in the system are listed in the table.
4. Select the row you want to edit and click Edit. The Egress Service Bundle Shaper Configuration – Edit page
opens. This page is similar to the Egress Service Bundle Shaper Configuration – Add page (Figure 248).
5. To assign a different egress queue shaper profile, select the profile in the Profile ID field.
6. To enable or disable egress service bundle shaping, select Enable or Disable.
7. Click Apply, then Close.

Phn 3963 013v000

Page 403
Chapter 7: Quality of Service (QoS) Configuring Scheduling

Configuring Scheduling

This section includes:

• Scheduling Overview
• Configuring Priority Profiles
• Configuring WFQ Profiles
• Assigning a Priority Profile to an Interface
• Assigning a WFQ Profile to an Interface

Scheduling Overview
Scheduling determines the priority among the queues. PTP 820 provides a unique hierarchical scheduling model
that includes four priorities, with Weighted Fair Queuing (WFQ) within each priority, and shaping per port and per
queue.
The scheduler scans the queues and determines which queue is ready to transmit. If more than one queue is ready
to transmit, the scheduler determines which queue transmits first based on:
• Queue Priority – A queue with higher priority is served before lower-priority queues.
• Weighted Fair Queuing (WFQ) – If two or more queues have the same priority and are ready to transmit, 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.

Configuring Priority Profiles

Scheduling priority profiles determine the queue priority. Each profile contains eight CoS-based priorities,
corresponding to eight queues in an interface to which the profile is assigned. You can configure up to eight
priority profiles. A ninth profile, Profile ID 9, is pre-configured. You can configure Green priorities from 4 (highest)
to 1 (lowest). An additional four Yellow priority profiles are defined automatically.
This section includes:
• Adding a Scheduler Priority Profile
• Editing a Service Scheduler Priority Profile
• Deleting a Scheduler Priority Profile

Adding a Scheduler Priority Profile

To add a scheduler priority profile:
1. Select Ethernet > QoS > Scheduler > Priority Profiles. The Scheduler Priority Profile page opens.

Phn 3963 013v000

Page 404
Chapter 7: Quality of Service (QoS) Configuring Scheduling

Figure 322 Scheduler Priority Profile Page

2. Click Add. The Scheduler Priority Profile – Add page opens, with default values displayed.

Phn 3963 013v000

Page 405
Chapter 7: Quality of Service (QoS) Configuring Scheduling

Figure 323 Scheduler Priority Profile – Add Page

3. In the Profile ID field, select a unique Profile ID between 1 and 8.

Phn 3963 013v000

Page 406
Chapter 7: Quality of Service (QoS) Configuring Scheduling

4. For each CoS value, enter the Green priority, from 4 (highest) to 1 (lowest) (1-4). This priority is applied to
Green frames with that CoS egressing a queue to which the profile is assigned.
5. Optionally, you can enter a description of up to 20 characters in the field to the right of each CoS value.
6. Click Apply, then Close.

Note
The Yellow priority values are assigned automatically by the system.

Editing a Service Scheduler Priority Profile

To edit a scheduler priority profile:
1. Select Ethernet > QoS > Scheduler > Priority Profiles. The Scheduler Priority Profile page opens (Figure 249).
2. Select the profile you want to edit and click Edit. The Scheduler Priority Profile – Edit page opens. This page is
similar to the Scheduler Priority Profile – Add page (Figure 250). You can edit any parameter except the Profile
ID.
3. Modify the profile.
4. Click Apply, then Close.

Deleting a Scheduler Priority Profile

To delete a scheduler priority profile, select the profile in the Scheduler Priority Profiles page (Figure 249) and click
Delete. The profile is deleted.
To delete multiple scheduler priority profiles:
1. Select the profiles in the Scheduler Priority Profiles page or select all the profiles by selecting the check box in
the top row.
2. Click Delete. The profiles are deleted.

Phn 3963 013v000

Page 407
Chapter 7: Quality of Service (QoS) Configuring Scheduling

Configuring WFQ Profiles

WFQ profiles determine the relative weight per queue. Each profile contains eight CoS-based weight values,
corresponding to eight queues in an interface to which the profile is assigned. You can configure up to five WFQ
profiles. A sixth profile, Profile ID 1, is pre-configured.
This section includes:
• Adding a WFQ Profile
• Editing a WFQ Priority Profile
• Deleting a WFQ Profile

Adding a WFQ Profile

To add a WFQ profile:
1. Select Ethernet > QoS > Scheduler > WFQ Profiles. The Scheduler WFQ Profile page opens.

Figure 324 Scheduler WFQ Profile Page

2. Click Add. The Scheduler WFQ Profile – Add page opens, with default values displayed.

Phn 3963 013v000

Page 408
Chapter 7: Quality of Service (QoS) Configuring Scheduling

Figure 325 Scheduler WFQ Profile – Add Page

3. In the Profile ID field, select a unique Profile ID between 2 and 7. Profile ID 1 is used for a pre-defined WFQ
profile.
4. For each CoS value, enter the weight for that CoS, from 1 to 20.
5. Click Apply, then Close.

Editing a WFQ Priority Profile

To edit a scheduler WFQ profile:
1. Select Ethernet > QoS > Scheduler > WFQ Profiles. The Scheduler WFQ Profile page opens (Figure 251).
2. Select the profile you want to edit and click Edit. The Scheduler WFQ Profile – Edit page opens. This page is
similar to the Scheduler WFQ Profile – Add page (Figure 241). You can edit any parameter except the Profile
ID.
3. Modify the profile.
4. Click Apply, then Close.

Deleting a WFQ Profile

To delete a scheduler WFQ profile, select the profile in the Scheduler WFQ Profiles page (Figure 251) and click
Delete. The profile is deleted.
To delete multiple scheduler WFQ profiles:

Phn 3963 013v000

Page 409
Chapter 7: Quality of Service (QoS) Configuring Scheduling

1. Select the profiles in the Scheduler WFQ Profiles page or select all the profiles by selecting the check box in
the top row.
2. Click Delete. The profiles are deleted.

Assigning a Priority Profile to an Interface

To assign a priority profile to an interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Scheduler. The Logical Interfaces –
Scheduler page opens, with the Egress Port Scheduling Priority Configuration – Edit page open by default.

Figure 326 Logical Interfaces – Scheduler – Egress Port Scheduling Priority

3. In the Profile ID field, select from a list of configured scheduling priority profiles. See Configuring Priority
Profiles.
4. Click Apply, then Close.

Assigning a WFQ Profile to an Interface

To assign a WFQ profile to an interface:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Scheduler. The Logical Interfaces –
Scheduler page opens, with the Egress Port Scheduling Priority Configuration – Edit page open by default
(Figure 253).
3. Select Egress Port Scheduling WFQ. The Egress Port Scheduling WFQ Configuration – Edit page opens.

Figure 327 Logical Interfaces – Scheduler – Egress Port Scheduling WFQ

Phn 3963 013v000

Page 410
Chapter 7: Quality of Service (QoS) Configuring Scheduling

4. In the Profile ID field, select from a list of configured scheduling priority profiles. See Configuring WFQ Profiles.
5. Click Apply, then Close.

Phn 3963 013v000

Page 411
Chapter 7: Quality of Service (QoS) Configuring and Displaying Queue-Level PMs

Configuring and Displaying Queue-Level PMs

PTP 820 devices support advanced traffic PMs per CoS queue and service bundle. For each logical interface, you
can configure thresholds for Green and Yellow traffic per queue. You can then display the following PMs for 15-
minute and 24-hour intervals, per queue and color:
• Maximum bytes passed per second
• Minimum bytes passed per second
• Average bytes passed per second
• Maximum bytes dropped per second
• Minimum bytes dropped per second
• Average bytes dropped per second
• Maximum packets passed per second
• Minimum packets passed per second
• Average packets passed per second
• Maximum packets dropped per second
• Minimum packets dropped per second
• Average packets dropped per second
• Seconds bytes per second were over the configured threshold per interval
These PMs are available for any type of logical interface, including groups. To activate collection of these PMs, the
user must add a PM collection rule on a logical interface and service bundle and set the relevant thresholds per
CoS and Color. When the PM is configured on a group, queue traffic PMs are recorded for the group and not for
the individual interfaces that belong to the group.
One collection rule is available per interface.
PMs for queue traffic are saved for 30 days, after which they are removed from the database. It is important to
note that they are not persistent, which means they are not saved in the event of unit reset.

Phn 3963 013v000

Page 412
Chapter 7: Quality of Service (QoS) Configuring and Displaying Queue-Level PMs

To configure queue-level PMs:

1 Select Ethernet > PM & Statistics > Egress CoS PM > Configuration. The Egress CoS PM Configuration page
opens.

Figure 328 Egress CoS PM Configuration Page

2 Click Add. The Egress CoS PM Configuration – Add page opens.

Phn 3963 013v000

Page 413
Chapter 7: Quality of Service (QoS) Configuring and Displaying Queue-Level PMs

Figure 329 Egress CoS PM Configuration – Add Page

3 In the Interface Location field, select the interface for which you want to configure the collection rule.
4 In the Service Bundle field, select a service bundle (1-6).
5 In the Admin field, select Enable to enable the collection rule.
6 Enter the Green and Yellow thresholds for each CoS, in bytes (0-4294967295).
7 Click Apply.
8 Repeat these steps to configure collection rules for additional interfaces.
To display queue-level PMs:
1 Select Ethernet > PM & Statistics > Egress CoS PM > Egress CoS PM. The Egress CoS PM page opens.

Phn 3963 013v000

Page 414
Chapter 7: Quality of Service (QoS) Configuring and Displaying Queue-Level PMs

Figure 330 Egress CoS PM Page

The Integrity column indicates whether the values received at the time and date of the measured interval are
valid. An X in the column indicates that the values are invalid. This can occur for a number of reasons, including but
not limited to a disconnected cable, a missing SFP module, muting of a radio interface, and an operational status of
Down.

Phn 3963 013v000

Page 415
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Chapter 8: Ethernet Protocols

This section includes:
• Configuring G.8032
• Configuring MSTP
• Configuring Adaptive Bandwidth Notification (ABN)
• Configuring Ethernet Bandwidth Notification (ETH-BN)
• Configuring LLDP

Configuring G.8032
• This section includes:
• G.8032 Overview
• Configuring the Destination MAC Address
• Adding ERPIs
• Configuring the RPL Owner
• Configuring Timers
• Viewing the ERPI Configuration and Status Parameters
• Viewing ERPI State Information
• Initiating a Manual or Forced Switch and Clearing the Switch or Initiating Reversion
• Blocking or Unblocking R-APS Messages on a Service Point
• Viewing ERPI Statistics

G.8032 Overview
Note
P2P services are not affected by G.8032, and continue to traverse ports that are blocked by G.8032.

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.
For a more detailed description of G.8032 in the PTP 820C, refer to the Technical Description for the product you are
using.

Phn 3963 013v000

Page 416
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Configuring the Destination MAC Address

To configure the destination MAC address for G.8032:
• Select Ethernet > Protocols > G.8032 > General Attribute. The G.8032 General Attribute page opens.
Figure 331: G.8032 General Attribute Page

• In the G8032 destination MAC address field, enter the destination MAC address for PDUs generated by the node.
• Click Apply.
Note
The G.8032 Node ID field displays the base MAC address for the node. This field is read-only.

Adding ERPIs
You can configure up to 16 Ethernet Ring Protection instances (ERPIs). Each ERPI is associated with an Ethernet
service defined in the system.

Note
Before adding an ERPI to an Ethernet service, the service must be mapped to an MSTP instance. See
Mapping Ethernet Services to MSTP instances (MSTIs).

To add an ERPI:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens.

Phn 3963 013v000

Page 417
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Figure 332: G.8032 ERPI Attribute Page

• Click Add. The Add G8032 ERPI Attribute wizard opens.

Figure 333: G.8032 ERPI Attribute Wizard – Page 1

• In the ERPI ID field, select an available ID. The ERPI ID is a unique ID that identifies the ERPI.
• Optionally, in the ERPI Name field, enter a descriptive name for the ERPI.
• In the Type field, select the type of ERPI, based on the type of ring:
◦ Ring: A Ring is an Ethernet ring that is connected on two ports (East and West service points) to an
interconnection node.
◦ Sub-ring: A Sub-Ring is an Ethernet ring which is connected to another ring or network through the use of
interconnection nodes (East and West service points). On their own, the Sub-Ring links do not form a closed
physical loop. A closed loop may be formed by the sub-ring links and the link between interconnection nodes
that is controlled by other ring or network.

◦ Ring with sub-ring: The ERPI includes both a ring, with East and West service points, and a connection to a
sub-ring using a Sub-Ring service point.
• In the Service ID field, select the ID of the Ethernet service to which the ERPI belongs.
• Optionally, in the MEG Level field, select the Maintenance Entity Group (MEG) level used for R-APS messages
sent in the ERPI (0-7).

Phn 3963 013v000

Page 418
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• Click Next. The second page of the Add G.8032 ERPI Attribute wizard opens.

Figure 334: G.8032 ERPI Attribute Wizard – Page 2

• In the West ERPI port (SP) field, select the first endpoint for the ERPI. This can be any service point that has been
configured for the service.
Note
Service points on the PTP 820 side of the link must have a single, determinate VLAN. This means the
service point type must be dot1q, s-tag, or QinQ. On the customer side, any service point type can be
used.

• Click Next. The third page of the Add G.8032 ERPI Attribute wizard opens.

Figure 335: G.8032 ERPI Attribute Wizard – Page 3

• In the East ERPI port (SP) field, select the second endpoint for the ERPI. This can be any service point that has
been configured for the service.
• Click Next:
Phn 3963 013v000
Page 419
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• If the Type is Ring or Sub-ring, the Submit page opens. Go to Step 15.
• If the Type is Ring with sub-ring, the fourth page of the Add G.8032 ERPI Attribute wizard opens.
Figure 336: G.8032 ERPI Attribute Wizard – Page 4

• In the Sub Ring port (SP) field, select the service point that connects the Ring with the Sub-Ring. This can be any
service point that has been configured for the service.
• Click Next. The Submit page opens.

Figure 337: G.8032 ERPI Attribute Wizard – Submit

• Verify that the parameters of the ERPI are correct and click Submit.

Phn 3963 013v000

Page 420
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Configuring the RPL Owner

• The RPL Owner Node is a node in the ERPI that is responsible for blocking traffic at one end of the ERPI. You can
select one RPL per ERPI. To designate the RPL Owner Node:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click Edit. The ERPI Attribute – Edit page opens.
Figure 338: G.8032 ERPI Attribute – Edit Page

Phn 3963 013v000

Page 421
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• In the RPL Owner field, select the service point you want to configure as RPL Owner.
• Click Apply, then Close.

Configuring Timers
• You can configure timers per ERPI to control the ERPI's switching and convergence parameters. The following
timers are available:
• Wait to Restore (WTR) Timer – Defines a minimum time the system waits after signal failure is recovered before
reverting to idle state, when the RPL can again be blocked.
• Guard Time – The guard time is the minimum time the system waits after recovery from a signal failure before
accepting new R-APS messages. The Guard Time should be greater than the maximum expected forwarding delay
for which one R-APS message circles around the ring.
Note
The Guard Time is used to prevent Ethernet ring nodes from acting upon outdated R-APS messages
and prevents the possibility of forming a closed loop.

• Hold-Off Time – Determines the time period from failure detection to response. It is used to coordinate between
recovery mechanisms (which mechanism takes place first).
• To configure the ERPI timers:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click Edit. The ERPI Attribute – Edit page opens (Figure 306).
• In the ERPI WTR field, enter the Wait to Restore (WTR) timer (in minutes).
• In the ERPI Guard Time field, enter the ERPI guard time (in msec). You must enter a multiple of 10.
• In the ERPI Holdoff Time field, enter the ERPI hold-off time (in msec). You must enter a multiple of 100.
• Click Apply, then Close.

Viewing the ERPI Configuration and Status Parameters

• The G.8032 ERPI Attribute page (Figure 300) displays some of the configuration and status parameters for ERPIs
configured in the system.
• To display a full list of configuration and status parameters for an ERPI:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click Edit. The ERPI Attribute – Edit page opens (Figure 306).
• Table 59 lists and describes the parameters in the ERPI configuration section of the ERPI Attribute – Edit page.
• Table 60 lists and describes the parameters in the ERPI status section of the ERPI Attribute – Edit page.

Table 48: ERPI Configuration Parameters

Parameter Definition
ERPI ID Read-only. A unique ID that identifies the ERPI.
ERPI Name A descriptive name for the ERPI.
ERPI Type Read-only. The ERPI type.
ERPI Service ID Read-only. The ID of the Ethernet service to which the ERPI belongs.

Phn 3963 013v000

Page 400
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Instance ID Read-only. The MSTI to which the Ethernet service is mapped. See
Mapping Ethernet Services to MSTP instances (MSTIs).
West ERPI Port (SP) Read-only. The interface to which the west ERPI service point
belongs.

East ERPI Port (SP) Read-only. The interface to which the east ERPI service point belongs.

Sub Ring Port (SP) Read-only. The interface to which the service point that connects the
Ring with the Sub-Ring belongs.

ERPI Protocol Version Read-only. The ERPI (G.8032) protocol version currently being used
in the unit.

RPL Owner The RPL Owner Node is a node in the ERPI that is responsible for
blocking traffic at one end of the ERPI. See Configuring the RPL
Owner.

Revertive Read-only. Indicates whether the ERPI is currently in revertive mode.

Virtual Channel VLAN Read-only. The VLAN of the virtual channel. If the value is 0, there is
no virtual channel.

Table 49: ERPI Status Parameters

Parameter Definition
ERPI State Indicates the current ERPI state. Possible values are:
Initializing
Idle
Pending
Protecting
FS (Forced Switch)
MS (Manual Switch)

MEG Level The Maintenance Entity Group (MEG) level used for R-APS messages
sent in the ERPI.

Last Local State Describes the current local state input to the ERPI state machine.
Last Remote State Indicates the last event received from the other end of the link.
Last HP Request Indicates the last high-priority event.
Last Change Timestamp Indicates the time of the last ring state transition.

Phn 3963 013v000

Page 401
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Viewing ERPI State Information

To view information about an ERPI’s state:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click State. The ERPI Attribute – State page opens.

Figure 339: G.8032 ERPI Attribute – State Page

• Table 61 lists and describes the parameters in the ERPI Attribute – State page.

Table 50: ERPI State Parameters

Parameter Definition
ERPI Port Identifies whether the row is for the West endpoint, the East
endpoint, or a Sub-Ring connection point.
ERPI Port Active State Indicates whether or not the service point is active for traffic
forwarding.

R-APS Channel Forwarding Indicates whether the service point is forwarding R-APS
State messages.

ERPI Data Forwarding State Indicates whether the service point is in unblocked (forwarding)
state.

RPL Blocking State Only relevant if the ERPI to which the service point belongs is
the RPL owner. Indicates whether the service point is in blocked
state.
ERPI Port Defect State Indicates whether the service point is in Signal Fail (SF) or
Signal Defect (SD) state.
Note: Support for Signal Defect state is planned for future
release.

Phn 3963 013v000

Page 402
 Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• Initiating a Manual or Forced Switch and Clearing the Switch or Initiating Reversion
• You can initiate a manual or forced switch, clear the switch, and initiate reversion, from the G.8032 ERPI Attribute – State page:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Slect the ERPI and click State. The ERPI Attribute – State page opens (Figure 307).
• Select the service point on which you want to perform the operation.
• To initiate a forced switch, click Force Switch.
• To initiate a manual switch, click Manual Switch.
• To clear a forced or manual switch, click Clear. You can also click Clear to trigger convergence prior to the expiration of the
relevant timer.

Blocking or Unblocking R-APS Messages on a Service Point

• To enable or disable transmission of R-APS messages on a service point:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click State. The ERPI Attribute – State page opens (Figure 307).
• Select the service point on which you want to perform the operation.
• To block R-APS message transmission on the service point, click R-APS Block.
• To enable R-APS message transmission on the service point, click R-APS Unblock.

Viewing ERPI Statistics

To view statistics about an ERPI:
• Select Ethernet > Protocols > G.8032 > ERPI Attribute. The G.8032 ERPI Attribute page opens (Figure 300).
• Select the ERPI and click Statistics. The ERPI Attribute – Statistics page opens.
Figure 340: G.8032 ERPI Attribute – Statistics Page

Phn 3963 013v000

Page 403
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Table 62 lists and describes the statistics shown in the ERPI Attribute – Statistics page.

Table 51: ERPI Statistics

Parameter Definition
ERPI Port Identifies whether the row is for the West endpoint, the East
endpoint, or a Sub-Ring connection point.
Transmitted Total R-APS The number of R-APS frames that have been transmitted via the
Frames service point.

Transmitted SF PDU The number of R-APS Signal Fail (SF) frames that have been
transmitted via the service point.

Transmitted NR PDU The number of R-APS No Request (NR) frames that have been
transmitted via the service point.

Transmitted RB PDU The number of R-APS RPL Blocked (RB) frames that have been
transmitted via the service point.

Transmitted FS PDU The number of R-APS Force Switched (FS) frames that have been
transmitted via the service point.

Transmitted MS PDU The number of R-APS Manual Switched (MS) frames that have been
transmitted via the service point.

Transmitted R-APS Events Reserved for future use.

Received R-APS Frames The number of R-APS frames that have been received via the service
point.

Received Invalid R-APS The number of R-APS frames with an invalid format that have been
Frames received via the service point.

Received SF PDU The number of R-APS Signal Fail (SF) frames that have been
received via the service point.

Received NR PDU The number of R-APS No Request (NR) frames that have been
received via the service point.

Received RB PDU The number of R-APS RPL Blocked (RB) frames that have been
received via the service point.

Received SD PDU The number of R-APS Signal Degrade (SD) frames that have been
received via the service point.

Received FS PDU The number of R-APS Forced Switch (FS) frames that have been
received via the service point.

Received MS PDU The number of R-APS Manual Switch (MS) frames that have been
received via the service point.

Received R-APS Events Reserved for future use.

Phn 3963 013v000

Page 404
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Configuring MSTP
This section includes:
• MSTP Overview
• Mapping Ethernet Services to MSTP instances (MSTIs)
• Configuring the MSTP Bridge Parameters
• Configuring the MSTP Port Parameters

MSTP Overview
Note
P2P services are not affected by MSTP, and continue to traverse ports that are blocked by 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 820F, and PTP 820G support MSTP according to the following IEEE standards:

• 802.1q
• 802.1ad amendment (Q-in-Q)
• 802.1ah (TE instance)
For a more detailed description of MSTP support in the PTP 820C, refer to the Technical Description for the product
you are using.

Mapping Ethernet Services to MSTP instances (MSTIs)

Ethernet services can be mapped to MSTP instances (MSTIs) in the Instances per Service Mapping section of the
Ethernet General Configuration page. All mapping of Ethernet services to MSTP instances (MSTIs) should be
performed before enabling MSTP.

Note
Ethernet service-to-MSTI mapping is also a prerequisite to configuring G.8032. See Configuring
G.8032.

To map Ethernet services to MSTP instances (MSTIs):

• Select Ethernet > General Configuration. The Ethernet General Configuration page opens (Figure 238).
• In the Instance per Service Mapping table, select the Service ID of the service you want to map.
• Click Edit. The Instance per Service Mapping – Edit page opens.

Phn 3963 013v000

Page 405
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Figure 341: Instance Per Service Mapping – Edit Page

• In the Instance ID field, enter a number between 0 and 16, or 4095. A service mapped to MSTI 4095 is never
blocked by any protocol.
• Click Apply.
• By default, all Ethernet services are mapped to MSTI 0, which represents the CIST (Common Instance Spanning
Tree).

Phn 3963 013v000

Page 406
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Configuring the MSTP Bridge Parameters

This section includes:
• Enabling MSTP and Configuring the MSTP Bridge General Attributes
• Viewing and Configuring the MSTP Bridge Configuration ID
• Viewing and Configuring the MSTP Bridge Spanning Tree
• Viewing and Configuring the MSTP Bridge CIST Parameters
• Viewing and Configuring the MSTP Bridge MSTI Parameters
• Viewing the MSTP VLAN Parameters

Enabling MSTP and Configuring the MSTP Bridge General Attributes

To configure the MSTP bridge general attributes:
• Select Ethernet > Protocols > MSTP > Bridge > General Attributes. The MSTP Bridge General Attributes page
opens.
Figure 342: MSTP Bridge General Attributes Page

• In the MSTP Enable field, select True to enable MSTP on the unit. To disable MSTP, select False.
◦ Enabling MSTP starts the protocol and sets all ports in all MSTP instances to Blocking state. Convergence
upon enabling the protocol generally takes less than two seconds.
◦ Disabling MSTP stops the MSTP protocol from running and sets all ports in all MSTP instances to Forwarding
state.

Phn 3963 013v000

Page 407
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• In the Number of Instances (excluding CIST) field, select the number of Multiple Spanning Tree instances (MSTIs).
Possible values are 1-16. This number does not include the Common and Internal Spanning Tree (CIST).

Note
Changing the Number of Instances causes the MSTP stack to reset.

• In the MSTP BPDU Destination MAC field, select the destination MAC address of BPDUs generated in the unit.
Options are:
◦ Customer – The destination MAC address of BPDUs is 0x0180-C200-0000. Provider BPDUs are either
tunneled or discarded.
◦ Provider – The destination MAC address of BPDUs is 0x0180-C200-0008. Customer BPDUs are either
tunneled or discarded.
• In the MSTP SD Handling field, select how MSTP handles Signal Degrade (SD) failures. Options are:
◦ Ignored – Signal Degrade (SD) failures are ignored in MSTP.
◦ Same as SF – SD failures trigger a topology change.

Note
SD handling is planned for future release.

• Click Apply.
To reset the MSTP stack, click Reset Protocol.

Phn 3963 013v000

Page 408
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Viewing and Configuring the MSTP Bridge Configuration ID

To configure the Configuration Name and Revision Level:
• Select Ethernet > Protocols > MSTP > Bridge > Configuration ID. The MSTP Bridge Configuration ID page opens.

Figure 343: MSTP Bridge Configuration ID Page

• Modify the configurable parameters.

• Click Apply.
Table 53 lists and describes the parameters in the MSTP Bridge Configuration ID page.

Table 52: MSTP Bridge Configuration ID Parameters

Parameter Definition
MSTP Configuration ID Format Read-only. Indicates the format specified in 802.1Q.
Selector
MSTP Configuration Name Enter a valid configuration name.
Note: Changing the Configuration Name when MSTP is
enabled causes the MSTP stack to reset.
MSTP Configuration Digest Read-only. Displays the MSTP Configuration Digest.
MSTP Revision Level Enter a valid MSTP revision level.
Note: Changing the Revision Level when MSTP is enabled
causes the MSTP stack to reset.

Phn 3963 013v000

Page 409
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Viewing and Configuring the MSTP Bridge Spanning Tree

To configure the bridge-level spanning tree parameters:
• Select Ethernet > Protocols > MSTP > Bridge > Spanning Tree. The MSTP Bridge Spanning Tree page opens.

Figure 344: MSTP Bridge Spanning Tree Page

• Modify the configurable parameters, described in Table 65.

• Click Apply.
Table 64 lists and describes the status parameters in the MSTP Bridge Spanning Tree page.

Phn 3963 013v000

Page 410
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Table 53: MSTP Bridge Spanning Tree Status Parameters

Parameter Definition
STP Time Since Last TC The time that has elapsed (in cs) since the last time the bridge
entity detected a topology change.
STP Number of Topology The total number of topology changes that have been detected
Changes by this bridge since the management entity was last reset or
initialized.
Note: Discontinuities in the value of this counter can occur
upon reinitialization of the management system.

STP Designated Root The Bridge ID of the spanning tree root, as determined by MSTP
in this node. This value is used as the Root ID in all configuration
BPDUs originated by this node.

STP Root Cost The cost of the path to the root as seen from this bridge.
STP Root Port The port number of the port that offers the lowest cost path
from this bridge to the external root bridge

STP Max Age The maximum age (in cs) of MSTP information learned from the
network on any port before the information is discarded.
Note: This field displays the value actually being used by the
bridge, in contrast to the STP Bridge Max Age parameter
described below, which is user-configurable and which
represents the value that this and all other bridges use if and
when this bridge becomes the root.

STP Forward Delay The speed at which ports change their spanning state when
moving towards the Forwarding state. This value determines
how long the port stays in Listening state and Learning state.
This value is also used when a topology change has been
detected and is underway for purposes of aging all dynamic
entries in the filtering database.
Note: This field displays the value actually being used by the
bridge, in contrast to the STP Bridge Forward Delay parameter
described below, which is user-configurable and which
represents the value that this and all other bridges use if and
when this bridge becomes the root.

STP Version The STP version the bridge is currently running (MSTP).

Table 54: MSTP Bridge Spanning Tree Configuration Parameters

Parameter Definition
STP Priority Select a value as the writeable portion of the Bridge ID. This value
constitutes the first two octets of the Bridge ID. Possible values are
0-61440, in steps of 4096
STP Hold Time Select a value (in cs) as the interval length during which no more
than two configuration bridge PDUs will be transmitted by this
node. Possible values are 10-100.

Page 411 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

STP Bridge Max Age Select a value (in cs) that all bridges will use, when this bridge is the
root, as the maximum age of MSTP information learned from the
network on any port before the information is discarded.
Options are 600-4000 cs.
STP Bridge Forward Delay Select a value (in cs) that all bridges will use, when this bridge is the
root, as the speed at which ports change their spanning state when
moving towards the Forwarding state. This value determines how
long the port stays in Listening state and Learning state. This value
is also used when a topology change has been detected and is
underway for purposes of aging all dynamic entries in the filtering
database. Options are 400-3000 cs.

STP Bridge Hello Time Select the value (in cs) that all bridges will use, when this bridge is
the root, as the Hello Time. The Hello Time determines how often
the switch broadcasts its hello message to other switches, and is the
same for all MSTIs. Options are 100-1000 cs.

Page 412 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Viewing and Configuring the MSTP Bridge CIST Parameters

To configure the maximum hops parameter for the Common and Internal Spanning Tree (CIST) and view CIST status
information:
• Select Ethernet > Protocols > MSTP > Bridge > CIST. The MSTP Bridge CIST page opens.
Figure 345; MSTP Bridge CIST Page

• In the CIST Max Hops field, select the value that all bridges will use, when this bridge is the root, as the maximum
number of hops allowed for a BPDU within a region before it is discarded. Options are 6-40.
• Click Apply.
Table 56 lists and describes the status parameters in the MSTP Bridge CIST page.

Table 55: MSTP Bridge CIST Status Parameters

Parameter Definition
CIST Bridge Identifier The Bridge ID of the CIST.
CIST Topology Change in Indicates whether a topology change is currently in progress for any
Progress port that is part of the CIST.

CIST Regional Root ID The Bridge ID of the current CIST regional root.
CIST Path Cost The CIST path cost from the transmitting bridge to the CIST regional
root. If the transmitting bridge is the CIST regional root, the value of
this parameter may be 0.

Page 413 of 998

Ceragon Proprietary and

 Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Viewing and Configuring the MSTP Bridge MSTI Parameters

To view the parameters of each MSTI in the system, and to configure the MSTI bridge priority for each MSTI:
• Select Ethernet > Protocols > MSTP > Bridge > MSTI. The MSTP Bridge MSTI page opens.

Figure 346: MSTP Bridge MSTI Page

• To view all the bridge parameters of an MSTI and/or configure its bridge priority, select the MSTI and click Edit.

Figure 347: MSTP Bridge MSTI – Edit Page

• To view all the bridge parameters of an MSTI and/or configure its bridge priority, select the MSTI and click Edit.

Page 414 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• In the MSTI Bridge Priority field, enter the MSTI writeable portion of the Bridge ID. Possible values are 0-61440, in
steps of 4096.
• Click Apply, then Close.
Table 57 lists and describes the status parameters in the MSTP Bridge MSTI page.

Table 56: MSTP Bridge MSTI Status Parameters

Parameter Definition
MSTI Instance ID The MSTI ID.
MSTI Bridge Identifier The Bridge ID for the MSTI.
MSTI Designated Root The Bridge ID of the root bridge for the MSTI.
MSTI Root Cost The path cost from the transmitting bridge to the root bridge for the
MSTI.

MSTI Root Port The root port for the MSTI.

MSTI Number of Topology The number of topology changes that the bridge has detected in the
Changes MSTI since the last time the management entity was reset or
initialized.

MSTI Topology Change in Indicates whether a topology change is currently in progress on any
Progress port in the MSTI.

MSTI Time Since Last TC The number of centi-seconds that have elapsed since the last time
the bridge identified a topology change for a port in the MSTI.

Viewing the MSTP VLAN Parameters

Each Ethernet service is mapped to an MSTI. By default, all services (VLAN ID) are assigned to MSTI 0 (CIST). See
Mapping Ethernet Services to MSTP instances (MSTIs).

Note
A service mapped to MSTI 4095 is never blocked by any protocol.

To view the VLAN ID to MSTI mapping table:

• Select Ethernet > Protocols > MSTP > Bridge > VLAN. The MSTP Bridge VLAN page opens.
Figure 348: MSTP Bridge VLAN Page

Page 415 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Page 416 of 998

Ceragon Proprietary and

 Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Configuring the MSTP Port Parameters

This section includes:
• Viewing and Configuring the MSTP Port Spanning Tree
• Viewing and Configuring the MSTP Port CIST Parameters
• Viewing and Configuring the MSTP Port MSTI Parameters
• Viewing and Resetting the BPDU Counters

Viewing and Configuring the MSTP Port Spanning Tree

To view the port-level spanning tree parameters and configure the STP port priority:
• Select Ethernet > Protocols > MSTP > Port > Spanning Tree. The MSTP Port Spanning Tree page opens.
Figure 349: MSTP Port Spanning Tree Page (PTP 820C)

• Select an interface and click Edit. The MSTP Port Spanning Tree – Edit page opens.

Figure 350: MSTP Port Spanning Tree – Edit Page

• In the STP Port Priority field, select the CIST port priority of the interface. You can select values from 0-240, in multiples of 16.

Page 417 of 998

Ceragon Proprietary and

 Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• Click Apply, then Close.

Table 58 lists and describes the status parameters in the MSTP Port Spanning Tree page.

Table 57: MSTP Port Spanning Tree Status Parameters

Parameter Definition

STP Interface Location The slot number and port number of the port.
STP Port State The port's current state, as defined by application of STP. The port's state
controls the action the port takes upon receipt of a frame.
Possible values are:
Forwarding – The port sends and receives traffic normally.
Blocking – The port does not send or receive traffic, but does receive
BPDUs.
Learning – The port receives traffic but does not forward the traffic. The
port learns the source MAC addresses of incoming frames.
Listening – The port monitors BPDUs, but does not forward traffic and does
not learn the source MAC addresses of incoming frames.
Disabled – The port is disabled (not by MSTP).

STP Port Designated Cost The CIST Path Cost of the segment connected to this port. This value is
compared to the root path cost in received BPDUs.
STP Port Designated The CIST Bridge ID of the bridge that this port considers to be the
Bridge designated bridge for this port's segment.

Viewing and Configuring the MSTP Port CIST Parameters

To view and configure CIST port parameters:
• Select Ethernet > Protocols > MSTP > Port > CIST. The MSTP Port CIST page opens.
Figure 351: MSTP Port CIST Page (PTP 820C)

Page 418 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• Select an interface and click Edit. The MSTP Port CIST – Edit page opens.

Figure 352: MSTP Port CIST – Edit Page

• In the CIST Port Admin Path Cost field, enter an assigned value for the contribution of this port to the path cost of
paths towards the spanning tree root.

Note
Changing the value of this parameter is considered to be a topology change by the MSTP mechanism.

• In the CIST Port Edge Admin field, select the port's administrative edge port parameter, for the CIST.
• In the CIST MAC enabled field, select the port's MAC Enabled parameter. A value of True indicates that
administratively, the MAC is set as if it were connected to a point-to-point LAN. Options are:
• Force True – The MAC is treated as if it is connected to a point-to-point LAN, regardless of any indications to the
contrary that are generated by the MAC entity.
• Force False –The MAC is treated as if it is connected to a non-point-to- point LAN, regardless of any indications to
the contrary that are generated by the MAC entity.
• Automatic – The MAC Enabled parameter is set to True if the MAC is connected to a point-to-point or full-duplex
LAN. The MAC Enabled parameter is set to False if the MAC is connected to a non-point-to-point and half-duplex
LAN.

Page 419 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

• Click Apply, then Close.

Table 59 lists and describes the status parameters in the MSTP Port Spanning Tree page.

Table 58: MSTP Port CIST Status Parameters

Parameter Definition
CIST Port Interface The slot number and port number of the port.
Location
CIST Port Designated The CIST Regional Root ID component of the port's Port Priority vector
Root for the CIST

CIST Port Edge Oper Indicates whether or not the port is operating as an Edge port. Possible
State values are:
True – The port is operating as an Edge port, which means it does not
process the BPDUs that it receives.
False – The port is operating as a non-Edge port, which means it
processes the BPDUs that it receives.
If CIST Port Edge Admin is set to True, the system automatically
determines its operational Edge port state.

CIST Port Role The port's current role in the CIST. Transient port roles may be:
Blocking – The port does not send or receive traffic, but does
receive BPDUs.
Learning – The port receives traffic but does not forward the traffic. The
port learns the source MAC addresses of incoming frames.
Listening – The port monitors BPDUs, but does not forward traffic and
does not learn the source MAC addresses of incoming frames.
Final port roles may be:
Disabled – The port is in Operational - Down state and is not included in
the MSTP calculation.
Designated – The port is in Operational - Up state and has been
designated to forward traffic.
Root – The port is forwarding traffic towards the root bridge.
Alternate – The port is not forwarding traffic (blocked) but can become
a Designated port after MSTP calculation.

CIST Port CIST Regional The Bridge ID of the current CIST Regional Root.
Route ID

CIST Port CIST Path Cost The CIST path cost from the transmitting bridge to the CIST regional
root. If the transmitting bridge is the CIST regional root, the value of this
parameter will be 0.

CIST Port Hello Time The port's Hello Time timer parameter value, for the CIST (in cs).
CIST Port Protocol The current value of the mcheck variable for the port.
Migration

Page 420 of 998

Ceragon Proprietary and

Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Parameter Definition
Note: Migration support is planned for future release.
CIST Port MAC Oper State The current state of the port's MAC operational parameter. True
indicates the MAC is operational.

CIST Port Uptime The number of seconds that have elapsed since the port was last reset
or initialized.

Viewing and Configuring the MSTP Port MSTI Parameters

To view and configure MSTI port parameters:
• Select Ethernet > Protocols > MSTP > Port > MSTI. The MSTP Port MSTI page opens.

Figure 353: MSTP Port MSTI Page

• To view the parameters for a specific MSTI-port combination in a separate window and modify several of the
parameters, select the row with the MSTI- port combination you want to view and/or modify and click Edit. The
MSTP Port MSTI – Edit page opens.

Phn 3963 013v000

Page 421
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Figure 354: MSTP Port MSTI – Edit Page

• In the MSTI Port Priority field, select the port's Priority parameter value for the MSTI, i.e., the priority field for the
Port ID for the MSTI. You can select values from 0-240, in multiples of 16.

Note
Changing the value of this parameter is considered to be a topology change by the MSTP
mechanism.

• In the MSTI Port Path Cost field, select the port's Path Cost parameter value for the MSTI.

Note
Changing the value of this parameter may cause re-initialization of the MSTI for which the parameter
is changed. No other MSTI is affected.

• Click Apply, then Close.

Table 60 lists and describes the status parameters in the MSTP MSTI Tree page.

Table 59: MSTP Port MSTI Status Parameters

Parameter Definition
MSTI Port MSTI ID The MSTI ID.
MSTI Port Interface The slot number and port number of the port.
Location
MSTI Port State The port's current state for the MSTI. Possible values are:

Parameter Definition

Phn 3963 013v000

Page 422
Chapter 8: Ethernet Protocols Configuring and Displaying Queue-Level PMs

Forwarding – The port sends and receives traffic normally.

Blocking – The port does not send or receive traffic, but does receive BPDUs.
Learning – The port receives traffic but does not forward the traffic. The port learns the source MAC
addresses of incoming frames.
Listening – The port monitors BPDUs, but does not forward traffic and does not learn the source MAC
addresses of incoming frames.
Disabled – The port is disabled (not by MSTP).

MSTI Port Designated The Regional Root ID component of the port's Port Priority vector for the
Root MSTI.
MSTI Port Designated The Internal Root Path Cost component of the port's MSTI port priority
Cost vector, for the MSTI.
MSTI Port Designated The Designated Bridge ID component of the port's MSTI port priority vector.
Bridge
MSTI Port Role The port's current role in the MSTI. Transient port roles may be:
Blocking – The port does not send or receive traffic, but does receive BPDUs.
Learning – The port receives traffic but does not forward the traffic. The port
learns the source MAC addresses of incoming frames.
Listening – The port monitors BPDUs, but does not forward traffic and does
not learn the source MAC addresses of incoming frames.
Final port roles may be:
Disabled – The port is in Operational - Down state and is not included in the
MSTP calculation.
Designated – The port is in Operational - Up state and has been designated to
forward traffic.
Root – The port is forwarding traffic towards the root bridge.
Alternate – The port is not forwarding traffic (blocked) but can become a
Designated port after MSTP calculation.
Master – The port is forwarding traffic towards the CIST root bridge.

MSTI Port Uptime The port's uptime parameter value for the MSTI. This is the number of
seconds that have elapsed since the port was last reset or initialized.

Phn 3963 013v000

Page 423
 Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

Viewing and Resetting the BPDU Counters

To view and reset the BPDU counters:
• Select Ethernet > Protocols > MSTP > Port > BPDU Counters. The MSTP Port BPDU Counters page opens.

Figure 355: MSTP Port BDPU Counters Page

• To reset the counters, click Reset Counters.

• To display the counters for a specific interface in a separate page, select the interface and click View.
Table 61 describes the available MSTP BPDU counters.

Table 60: MSTP BPDU Counters

Parameter Definition
Interface Location The location of the port.
Received TCN The number of Topology Change Notifications (TCNs) received since the last counter
reset.

Received Configuration BPDU The number of configuration BPDUs received since the last counter reset.
Received RST BPDU The number of Rapid Spanning Tree (RST) BPDUs received since the last counter
reset.
Received MST BPDU The number of Multiple Spanning Tree (MST) BPDUs received since the last counter
reset.

Transmitted TCN BPDU The number of Topology Change Notifications (TCNs) transmitted since the last
counter reset.

Transmitted Configuration The number of configuration BPDUs transmitted since the last counter reset.
BPDU

Transmitted RST BPDU The number of Rapid Spanning Tree (RST) BPDUs transmitted since the last counter
reset.

Transmitted MST BPDU The number of Multiple Spanning Tree (MST) BPDUs transmitted since the last
counter reset.

Configuring Ethernet Bandwidth Notification (ETH-

Phn 3963 013v000
Page 424
 Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

BN)
This section includes:
• ETH-BN Overview
• Adding an ETH-BN entity
• Editing an ETH-BN Entity
• Deleting an ETH-BN Entity
• Viewing the Statistics for an ETH-BN Entity

ETH-BN Overview
Ethernet Bandwidth Notification (ETH-BN) is defined by the Y.1731 OAM standard. The purpose of ETH-BN is to inform
the L2 or L3 customer switch of the capacity of the radio link in transmit direction. This enables the switch to respond to
fluctuations in the radio link by, for example, reconfiguring the shaper on the egress port facing the radio link or
rerouting traffic to other egress ports.
Once ETH-BN is enabled, the radio unit reports bandwidth information to upstream third-party switches. The ETH-BN
entity creates a logical relationship between a radio interface, called the Monitored Interface, and an Ethernet interface,
called the Control Interface. When bandwidth degrades from the nominal value in the Monitored Interface, messages
relaying the actual bandwidth values (BNM frames) are periodically sent over the Control Interface. Once the bandwidth
returns to its nominal level, BNM messages are no longer sent. Optionally, the device can be configured to send BNM
frames even when bandwidth is at its nominal level.
The Monitored Interface can be a single radio interface, a Multi-Carrier ABC group, a Multiband group, or a radio LAG. To
be used as a Monitored Interface, the LAG must consist of radio interfaces only.
The Control Interface can be a single Ethernet interface or an Ethernet LAG. To be used as a Control Interface, the LAG
must consist of Ethernet interfaces only.

Note
ETH-BN cannot be used with HSB protection groups.
When the Control Interface is a LAG, EBN messages are only sent to the first active member of the LAG.
When used with PTP 820C, PTP 820S, and PTP 820C-HP unit redundancy, the reported bandwidth may
be inaccurate when switchover is in effect.

The same radio interface can be configured as a Monitored Interface for multiple EBN instances. However, an Ethernet
interface can only be configured as a Control Interface for a single EBN instance.

Adding an ETH-BN entity

To add an ETH-BN entity:
1 Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth
Notification page opens.

Figure 356: Bandwidth Notification Page

Phn 3963 013v000

Page 425
 Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

2 Click Add. The Bandwidth Notification - Add page opens.

Figure 357: Bandwidth Notification – Add Page

3 In the Name field, enter a name for the ETH-BN entity.

4 In the Protocol Type field, select Ethernet BNM.
5 In the Admin field, select Up to enable ETH-BN monitoring or Down to disable ETH-BN
monitoring.
6 In the Monitored Interface field, select the Monitored Interface. This is the interface
which is constantly monitored for its bandwidth value.
7 In the Control Interface field, select the Control Interface. This is the interface to which
messages are transmitted when bandwidth in the monitored interface degrades below
the nominal value.
8 In the MEL field, select the CFM Maintenance Level in the messages (0-7).
Note
The CoS of the VLAN is automatically set to 7. If CFM MEPs are being used,
the MEL must be set to a value greater than the MEG level of the MEP.
Otherwise, the BNM frames will be dropped.
If CFM MEPs are not being used, the MEL for ETH-BN must be set to a
value greater than 0. Otherwise, the BNM frames will be dropped.
Phn 3963 013v000
Page 426
Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

9 In the Tx VLAN field, specify the VLAN on which messages are transmitted.
Options are:
◦ Untagged.
◦ 1 – 4090.
Note
The CoS of the VLAN is automatically set to 7.

10 In the Is Always Sent field, specify whether periodic BNM frames should be sent
even when there is no bandwidth degradation in the monitored interface:
◦ True – BNM frames are always sent, even when the bandwidth is at its
nominal value.
◦ False – BNM frames are only sent when the current bandwidth is lower than
the nominal bandwidth (default value).
11 In the Tx Period field, specify how often messages are transmitted when Is Always
Sent is set to True or, if not, when bandwidth is below the nominal value. Options
are:
◦ One second
◦ Ten seconds (default)
◦ Sixty seconds
12 In the Holdoff Time field, specify the amount of time (in seconds) the system waits
when bandwidth degradation occurs, before transmitting a message. If the bandwidth
is below the nominal value when the holdoff period ends, the system starts
transmitting messages. Options are 0-10. The default value is 10.
Note
If the bandwidth fluctuates before the Holdoff Time expires, and is
lower than the nominal bandwidth when the Holdoff Time expires, the first BNM frame sent
when the timer expires gives the lowest bandwidth that was recorded while the timer was
running.
Subsequent BNM frames are sent with the actual current bandwidth.

13 Click Apply, then Close.

Table 61 describes the status (read-only) fields in the ABN Configuration and Status
table.
Table 61: ETH-BN Status Parameters

Parameter Definition

Nominal BW The maximum radio TX bitrate achievable with the current radio configuration.
Current BW The current radio TX bitrate.

Phn 3963 013v000

Page 427
Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

Editing an ETH-BN Entity

To edit an ETH-BN entity:
1 Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth
Notification page opens (Figure 300).
2 Select the ETH-BN entity in the Bandwidth Notification page.
3 Click Edit. The Bandwidth Notification - Edit page opens.
The Edit page is similar to the Bandwidth Notification – Add page (Figure 301).
However, the Control interface and Monitored interface parameters are read-only,
and additional read-only parameters display the Nominal BW, and the Current BW.
4 Edit the ETH-BN attributes, as described in Adding an ETH-BN entity.
5 Click Apply, then Close.

Deleting an ETH-BN Entity

To delete an ETH-BN entity:
1 Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth
Notification page opens (Figure 300).
2 Select the ETH-BN entity in the Bandwidth Notification page.
3 Click Delete. The ETH-BN entity is removed.

Viewing the Statistics for an ETH-BN Entity

To view the statistics for an ETH-BN entity:
1 Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth
Notification page opens (Figure 300).
2 Select the ETH-BN entity in the Bandwidth Notification page.
3 Click Statistics. The Bandwidth Notification - Statistics page opens.

Figure 358: Bandwidth Notification - Statistics Page (ETH-BN)

Phn 3963 013v000

Page 428
Chapter 8: Ethernet Protocols Configuring Ethernet Bandwidth Notification (ETH-BN)

Table 62 describes the ETH-BN entity statistics.

Table 62: ETH-BN Entity Statistics Parameters

Parameter Definition

Name The name of the ETH-BN entity.

Protocol Type Ethernet BNM.
Tx Messages Counter The number of bandwidth messages transmitted since the counter
was last reset.
Holdoff State The Holdoff state of the monitored link. Options are:
• Off – Holdoff time measurement has not been started.
• Counting – Holdoff time measurement has started but the
timeout has not elapsed yet.
• On – Holdoff measurement time has ended and the current
bandwidth is still below the nominal value.

Phn 3963 013v000

Page 429
Chapter 8: Ethernet Protocols Configuring Adaptive Bandwidth Notification (ABN)

Configuring Adaptive Bandwidth Notification

(ABN)

This section includes:

• Adaptive Bandwidth Notification Overview
• Adding an ABN entity
• Editing an ABN Entity
• Deleting an ABN Entity
• Viewing the Statistics for an ABN Entity

Adaptive Bandwidth Notification Overview

Adaptive Bandwidth Notification (ABN), also known as Ethernet Operation and Maintenance (EOAM), enables third
party applications to learn about bandwidth changes in a radio link when ACM is active. Once ABN is enabled, the
radio unit reports bandwidth information to upstream third-party switches.
The ABN entity creates a logical relationship between a radio interface or a logical group of radio interfaces, called
the Monitored Interface, and an Ethernet interface or a logical group of Ethernet interface, called the Control
Interface. When bandwidth degrades from the nominal value in the Monitored Interface, messages relaying the
actual bandwidth values are periodically sent over the Control Interface. A termination message is sent once the
bandwidth returns to its nominal level.

Adding an ABN entity

To add an ABN entity:
1. Select Ethernet > Protocols > Bandwidth Notification. The BN ( Bandwidth Notification) page opens.
Figure 359 Bandwidth Notification Page

Phn 3963 013v000

Page 430
Chapter 8: Ethernet Protocols Configuring Adaptive Bandwidth Notification (ABN)

Click Add. The Bandwidth Notification - Add page opens.

Figure 360 ABN Configuration and Status – Add Page

In the Name field, enter a name for the ABN entity.

1 In the Protocol Type field, select VSM ABN.
2 In the Admin field, select Up to enable ABN monitoring or Down to disable ABN monitoring.
3 In the Monitored Interface field, select the Monitored Interface. This is the interface which is constantly
monitored for its bandwidth value.
4 In the Control Interface field, select the Control Interface. This is the interface to which messages are
transmitted when bandwidth in the monitored interface degrades below the nominal value.
5 In the MEL field, select the Maintenance Level in the messages.
6 In the Tx VLAN field, specify the VLAN on which messages are transmitted. Options are:
◦ Untagged.
◦ 1 – 4090.

Phn 3963 013v000

Page 431
Chapter 8: Ethernet Protocols Configuring Adaptive Bandwidth Notification (ABN)

7 In the Tx Period field, specify how often messages are transmitted when bandwidth is below the nominal value.
Options are:
◦ 4 – One second.
◦ 5 – Ten seconds.
◦ 6 – One minute.
8 In the Holdoff Time field, specify the amount of time the system waits when bandwidth degradation occurs,
before transmitting a message. If the bandwidth is below the nominal value when the holdoff period ends, the
system starts transmitting messages.
9 In the Monitoring Interval field, select the interval for which a weighted average of the bandwidth readings is
calculated.
10 Click Apply, then Close.
Table 48 describes the status (read-only) fields in the ABN Configuration and Status table.

Table 61 ABN Status Parameters

Parameter Definition

Nominal BW The nominal bandwidth of the link.

Current BW The weighted average of the bandwidth readings taken during the last
Monitoring Interval.

Version The ABN version used.

Editing an ABN Entity

To edit an ABN entity:
1. Select Ethernet > Protocols > Bandwidth Notification. The ABN (Adaptive Bandwidth Notification) page opens
(Figure 258).
2. Select the ABN entity in the Bandwidth Notification and Status Table.
3. Click Edit. The Bandwidth Notification - Edit page opens.
The Edit page is similar to the Bandwidth Notification – Add page (Figure 259). However, the Control
interface and Monitored interface parameters are read-only, and additional read-only parameters display
the Nominal BW, the Current BW, and the Version.
4. Edit the ABN entity attributes, as described in Adding an ABN entity.
5. Click Apply, then Close.

Deleting an ABN Entity

To delete an ABN entity:
1. Select Ethernet > Protocols > Bandwidth Notification. The Bandwidth Notification page opens (Figure 258).
2. Select the ABN entity in the Bandwidth Notification page.
3. Click Delete. The ABN entity is removed.

Phn 3963 013v000

Page 432
Chapter 8: Ethernet Protocols Configuring Adaptive Bandwidth Notification (ABN)

Viewing the Statistics for an ABN Entity

To view the statistics for an ABN entity:
1. Select Ethernet > Protocols Bandwidth Notification. The Bandwidth Notification page opens (Figure 258).
2. Select the ABN entity in the Bandwidth Notification page.
3. Click Statistics. The Bandwidth Notification - Statistics page opens.

Phn 3963 013v000

Page 433
Chapter 8: Ethernet Protocols Configuring Adaptive Bandwidth Notification (ABN)

Figure 361 Bandwidth Notification - Statistics Page

Table 49 describes the ABN entity statistics.

Table 62 ABN Entity Statistics Parameters

Parameter Definition

Name The name of the ABN entity.

Tx Messages Counter The number of bandwidth messages transmitted since the counter was
last reset.

Holdoff State The Holdoff state of the monitored link. Options are:
Off – Holdoff time measurement has not been started.
Counting – Holdoff time measurement has started but the timeout has
not elapsed yet.
On – Holdoff measurement time has ended and the current bandwidth is
still below the nominal value.

Holdoff Start Time (mSec) The Holdoff start time for the last event.

Last Tx message The last transmitted bandwidth message, in hexadecimal notation.

Phn 3963 013v000

Page 434
Chapter 8: Ethernet Protocols Configuring LLDP

Configuring LLDP

This section includes:

• LLDP Overview
• Displaying Peer Status
• Configuring the General LLDP Parameters
• Configuring the LLDP Port Parameters
• Displaying the Unit’s Management Parameters
• Displaying Peer Unit’s Management Parameters
• Displaying the Local Unit’s Parameters
• Displaying LLDP Statistics

LLDP Overview
Link Layer Discovery Protocol (LLDP) is a vendor-neutral layer 2 protocol that can be used by a network element
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. LLDP is a part of the IEEE 802.1AB – 2005 standard that enables
automatic network connectivity discovery by means of a port identity information exchange between each port
and its peer. Each port periodically sends and also expects to receive frames called Link Layer Discovery Protocol
Data Units (LLDPDU). LLDPDUs contain information in TLV format about port identity, such as MAC address and
IP address.
LLDP is used to send notifications to the NMS, based on data of the local unit and data gathered from peer
systems. These notifications enable the NMS to build an accurate network topology.

Displaying Peer Status

To display a summary of the important LLDP management information regarding the unit's nearest neighbor
(peer):
1. Select Ethernet > Protocols > LLDP > Remote Management. The LLDP Remote Management page opens.

Figure 362 LLDP Remote System Management Page

Phn 3963 013v000

Page 435
Chapter 8: Ethernet Protocols Configuring LLDP

Table 50 describes the LLDP remote system management parameters. These parameters are read-only.

Table 63 LLDP Remote System Management Parameters

Parameter Definition

Local Interface Location The location of the local interface.

Management Address The octet string used to identify the management address component
associated with the remote system.

Address Sub Type The type of management address identifier encoding used in the
associated LLDP Agent Remote Management Address.

Time Mark The time the entry was created.

Configuring the General LLDP Parameters

This section explains how to define the general LLDP parameters for the unit. For instructions on defining port-
specific parameters, see Configuring the LLDP Port Parameters.

Note
The management IP address advertised by the local element depends on the IP protocol (IPv4 or
IPv6) configured for the unit. See Defining the IP Protocol Version for Initiating Communications.

To display and configure the general LLDP parameters for the unit:
1. Select Ethernet > Protocols > LLDP > Advanced > Configuration > Parameters. The LLDP Configuration
Parameters page opens.

Phn 3963 013v000

Page 436
Chapter 8: Ethernet Protocols Configuring LLDP

Figure 363 LLDP Configuration Parameters Page

2. Modify the configurable parameters, described in Table 52.

3. Click Apply.
Table 51 lists and describes the status parameters in the LLDP Configuration Parameters page.

Table 64 LLDP Read-Only Configuration Parameters

Parameter Definition

Max TX Credit Displays the maximum number of consecutive LLDPDUs that can be
transmitted at any one time. In this release, the Max TX Credit is set at 5.

Fast TX Interval (Seconds) Displays, in seconds, the interval at which LLDP frames are transmitted
during fast transmission periods, such as when the unit detects a new
peer. In this release, the Fast TX Interval is set at 1.

Fast TX The initial value used to initialize the variable which determines the
number of transmissions that are made during fast transmission periods.
In this release, the Fast TX No. is set at 4.

Phn 3963 013v000

Page 437
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Reinit Delay (Seconds) Defines the minimum time, in seconds, the system waits after the LLDP
Admin status becomes Disabled until it will process a request to
reinitialize LLDP. For instructions on disabling or enabling LLDP on a port,
see Configuring the LLDP Port Parameters.
In this release, the Reinit Delay is set at 2.

Table 65 LLDP Configurable Configuration Parameters

Parameter Definition

TX Interval (Seconds) Defines the interval, in seconds, at which LLDP frames are transmitted.
You can select a value from 5 to 32768. The default value is 30.

Notification Interval Defines the interval, in seconds, between transmissions of LLDP

(Seconds) notifications during normal transmission periods. You can select a value
from 5 to 3600. The default value is 10.

Hold Multiplier Defines the time-to-live (TTL) multiplier. The TTL determines the length of
time LLDP frames are retained by the receiving device. The TTL is
determined by multiplying the TX Interval by the Hold Multiplier.
You can select a value from 2 to 10. The default value is 4.

Configuring the LLDP Port Parameters

To enable LLDP per port and determine how LLDP operates and which TLVs are sent for each port:
1. Select Ethernet > Protocols > LLDP > Advanced > Configuration > Port Configuration. The LLDP Port
Configuration page opens.

Phn 3963 013v000

Page 438
Chapter 8: Ethernet Protocols Configuring LLDP

Figure 364 LLDP Port Configuration Page

2. Select an interface and click Edit. The LLDP Port Configuration - Edit page opens.

Figure 365 LLDP Port Configuration - Edit Page

3. In the Admin field, select from the following options to define how the LLDP protocol operates for this port:
o TX Only – LLDP agent transmits LLDP frames on this port but does not update
information about its peer.
o RX Only – LLDP agent receives but does not transmit LLDP frames on this port.

Phn 3963 013v000

Page 439
Chapter 8: Ethernet Protocols Configuring LLDP

o TX and RX – LLDP agent transmits and receives LLDP frames on this port (default
value).
o Disabled – LLDP agent does not transmit or receive LLDP frames on this port.

Phn 3963 013v000

Page 440
Chapter 8: Ethernet Protocols Configuring LLDP

4. In the Notification Enable field, select from the following options to define, on a per agent basis, whether or
not notifications from the agent to the NMS are enabled:
o True – The agent sends a Topology Change trap to the NMS whenever the system
information received from the peer changes.
o False – Notifications to the NMS are disabled (default value).
5. Click Apply, then Close.
Table 53 lists and describes the status parameters in the LLDP Port Configuration page.

Table 66 LLDP Port Configuration Status Parameters

Parameter Definition

Interface Location Identifies the port.

Destination Address The destination address of the LLDP agent associated with this port.

TLV TX Indicates which of the unit's capabilities is transmitted by the LLDP agent
for the port:
• PortDesc – The LLDP agent transmits Port Description TLVs.
• SysName – The LLDP agent transmits System Name TLVs.
• SysDesc – The LLDP agent transmits System Description TLVs.
• SysCap – The LLDP agent transmits System Capabilities TLVs.

Displaying the Unit’s Management Parameters

To display the unit's destination LLDP MAC address:
1. Select Ethernet > Protocols > LLDP > Advanced > Configuration > Destination Address. The LLDP Destination
Address Table page opens.

Phn 3963 013v000

Page 441
Chapter 8: Ethernet Protocols Configuring LLDP

Figure 366 LLDP Destination Address Table Page

To displays the MAC address associated with the unit for purposes of LLDP transmissions:
1. Select Ethernet > Protocols > LLDP > Advanced > Configuration > Management TLV. The LLDP Management
TLV Configuration page opens.

Phn 3963 013v000

Page 442
Chapter 8: Ethernet Protocols Configuring LLDP

Figure 367 LLDP Management TLV Configuration Page

Table 54 lists and describes the status parameters in the LLDP Management TLV Configuration page.

Table 67 LLDP Management TLV Parameters

Parameter Definition

Interface Location Identifies the port.

Destination Address Defines the MAC address associated with the port for purposes of LLDP
transmissions.

Management Address The unit's IP address.

Address Subtype Defines the type of the management address identifier encoding used for
the Management Address.

Tx Enable Indicates whether the unit's Management Address is transmitted with

LLDPDUs. In this release, the Management Address is always sent.

Phn 3963 013v000

Page 443
Chapter 8: Ethernet Protocols Configuring LLDP

Displaying Peer Unit’s Management Parameters

To display LLDP management information about the unit's nearest neighbor (peer):
1. Select Ethernet > Protocols > LLDP > Advanced > Remote System > Management. The LLDP Remote System
Management page opens.

Figure 368 LLDP Remote System Management Page

Table 55 describes the LLDP remote system management parameters. These parameters are read-only.

Table 68 LLDP Remote System Management Parameters

Parameter Definition

Local Interface Location The location of the local interface.

Management Address The octet string used to identify the management address component
associated with the remote system.

Address Sub Type The type of management address identifier encoding used in the
associated LLDP Agent Remote Management Address.

Destination Address The peer LLDP agent's destination MAC Address.

Remote ID An arbitrary local integer value used by this agent to identify a particular
connection instance, unique only for the indicated remote system.

Time Mark The time the entry was created.

Phn 3963 013v000

Page 444
Chapter 8: Ethernet Protocols Configuring LLDP

To display unit parameter information received via LLDP from the unit's nearest neighbor (peer):
1. Select Ethernet > Protocols > LLDP > Advanced > Remote System > Remote Table. The LLDP Remote System
Table page opens.

Figure 369 LLDP Remote System Table Page

Table 56 describes the parameters in the LLDP Remote System Table page. These parameters are read-only.

Table 69 LLDP Remote System Table Parameters

Parameter Definition

Local Interface Location The location of the local interface.

Remote ID An arbitrary local integer value used by this agent to identify a particular
connection instance, unique only for the indicated peer.

Remote Chassis ID An octet string used to identify the peer's hardware unit

Chassis ID Subtype The type of encoding used to identify the peer's hardware unit

Remote Port An octet string used to identify the port component associated with the
remote system.

Port Sub type The type of port identifier encoding used in the peer's Port ID.

Time Mark The time the entry was created.

Phn 3963 013v000

Page 445
Chapter 8: Ethernet Protocols Configuring LLDP

Displaying the Local Unit’s Parameters

To display the unit parameters, as transmitted by the LLDP agents:
1. Select Ethernet > Protocols > LLDP > Advanced > Local System > Parameters. The LLDP Local System
Parameters page opens.
Figure 370 LLDP Local System Parameters Page

Table 57 describes the parameters in the LLDP Local System Parameters page. These parameters are read-only.

Table 70 LLDP Local System Parameters

Parameter Definition

System Name The system name included in TLVs transmitted by the LLDP agent, as
defined in the Name field of the Unit Parameters page. See Configuring
Unit Parameters.

System Description The system description included in TLVs transmitted by the LLDP agent, as
defined in the Description field of the Unit Parameters page. See
Configuring Unit Parameters.

Chassis ID The MAC Address of the local unit.

Phn 3963 013v000

Page 446
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Chassis ID SubType The type of encoding used to identify the local unit. In this release, this
parameter is always set to MAC Address.

Capabilities Supported A bitmap value used to identify which system capabilities are supported
on the local system, as included in TLVs transmitted by the LLDP agent.
The bitmap is defined by the following parameters:
0 – other
1 – repeater
2 – bridge
3 – wlanAccessPoint
4 – router
5 – telephone
6 – docsisCableDevice
7 – stationOnly
8 – cVLANComponent
9 – sVLANComponent
10 – twoPortMACRelay

Capabilities Enabled A bitmap value used to identify which system capabilities are enabled on
the local system, as included in TLVs transmitted by the LLDP agent.
The bitmap is defined by the following parameters:
0 – other
1 – repeater
2 – bridge
3 – wlanAccessPoint
4 – router
5 – telephone
6 – docsisCableDevice
7 – stationOnly
8 – cVLANComponent
9 – sVLANComponent
10 – twoPortMACRelay

To display the unit’s port parameters, as transmitted by the LLDP agents:

1. Select Ethernet > Protocols > LLDP > Advanced > Local System > Port. The LLDP Local System Port page opens.

Phn 3963 013v000

Page 447
Chapter 8: Ethernet Protocols Configuring LLDP

Figure 371 LLDP Local System Port Page

Table 58 describes the parameters in the LLDP Local System Port page. These parameters are read-only.

Table 71 LLDP Local System Port Parameters

Parameter Definition

Interface Location Identifies the port.

Port ID The port's MAC address.

Port Sub Type The type of encoding used to identify the port in LLDP transmissions. In
this release, this parameter is always set to MAC Address.

Port Description A description of the port.

To display the unit’s management parameters, as transmitted by the LLDP agents:

1. Select Ethernet > Protocols > LLDP > Advanced > Local System > Management. The LLDP Local System
Management page opens.

Figure 372 LLDP Local System Management Page

Phn 3963 013v000

Page 448
Chapter 8: Ethernet Protocols Configuring LLDP

2. To display all the parameters, select a row and click View.

Figure 373 LLDP Local System Management – View Page

Table 59 describes the parameters in the LLDP Local System Management page. These parameters are read-only.

Table 72 LLDP Local System Management Parameters

Parameter Definition

Management Address The local unit's IP address.

Address Sub Type The format of the local unit's IP Address.

Address Length Reserved for future use.

Address Interface ID Reserved for future use.

Phn 3963 013v000

Page 449
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Address Interface Sub Reserved for future use.

Type

Address OID Reserved for future use.

Displaying LLDP Statistics

To display statistics about changes reported via LLDP by the remote unit:
1. Select Ethernet > Protocols > LLDP > Advanced > Statistic > General. The LLDP Statistic page opens.

Figure 374 LLDP Statistic Page

Table 60 describes the statistics in the LLDP Statistic page.

Table 73 LLDP Statistics

Parameter Definition

Last Change Time The time of the most recent change in the remote unit, as reported via
LLDP.

Phn 3963 013v000

Page 450
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Inserts The number of times the information from the remote system has
changed.

Deletes The number of times the information from the remote system has been
deleted.

Drops Reserved for future use.

Ageouts The number of times the information from the remote system has been
deleted from the local unit's database because the information's TTL has
expired.
The RX Ageouts counter in the Port RX page is similar to this counter, but
is for specific ports rather than the entire unit.

To display statistics about LLDP transmissions and transmission errors:

1. Select Ethernet > Protocols > LLDP > Advanced > Statistic > Port TX. The LLDP Port TX Statistic page opens.

Figure 375 LLDP Port TX Statistic Page

Table 61 describes the statistics in the LLDP Port TX Statistic page.

Table 74 LLDP Port TX Statistics

Phn 3963 013v000

Page 451
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Interface Location The index value used to identify the port in LLDP transmissions.

Destination Address The LLDP MAC address associated with this entry.

Total Frames The number of LLDP frames transmitted by the LLDP agent on this port to
the destination MAC address.

Errored Length Frames The number of LLDPDU Length Errors recorded for this port and
destination MAC address.
If the set of TLVs that is selected in the LLDP local system MIB by network
management would result in an LLDPDU that violates LLDPDU length
restrictions, then the No. of Length Error statistic is incremented by 1,
and an LLDPDU is sent containing the mandatory TLVs plus as many of the
optional TLVs in the set as will fit in the remaining LLDPDU length.

To display statistics about LLDP frames received by the unit:

Select Ethernet > Protocols > LLDP > Advanced > Statistic > Port RX. The LLDP Port TX Statistic page opens.

Figure 376 LLDP Port RX Statistic Page

Table 62 describes the statistics in the LLDP Port TX Statistics page.

Table 75 LLDP Port RX Statistics

Parameter Definition

Interface Location The index value used to identify the port in LLDP transmissions.

Destination Address The LLDP MAC address associated with this entry.

Phn 3963 013v000

Page 452
Chapter 8: Ethernet Protocols Configuring LLDP

Parameter Definition

Total Discarded The number of LLDP frames received by the LLDP agent on this port, and
then discarded for any reason. This counter can provide an indication that
LLDP header formatting problems may exist with the local LLDP agent in
the sending system or that LLDPDU validation problems may exist with
the local LLDP agent in the receiving system.

Invalid Frames The number of invalid LLDP frames received by the LLDP agent on this
port while the agent is enabled.

Valid Frames The number of valid LLDP frames received by the LLDP agent on this port.

Discarded TLVs The number of LLDP TLVs discarded for any reason by the LLDP agent on
this port.

Unrecognized TLVs The number of LLDP TLVs received on the given port that are not
recognized by LLDP agent.

Ageouts The number of age-outs that occurred on the port. An age-out is the
number of times the complete set of information advertised by the
remote system has been deleted from the unit's database because the
information timeliness interval has expired.
This counter is similar to the LLDP No. of Ageouts counter in the LLDP
Statistic page, except that it is per port rather than for the entire unit.
This counter is set to zero during agent initialization. This counter is
incremented only once when the complete set of information is
invalidated (aged out) from all related tables on a particular port. Partial
ageing is not allowed.

Phn 3963 013v000

Page 453
Chapter 9: Synchronization Configuring LLDP

Chapter 9: Synchronization
This section includes:
• Configuring the SyncE Regenerator
• Configuring the Sync Source
• Configuring the Outgoing Clock and SSM Messages
• Configuring 1588 Transparent Clock

Phn 3963 013v000

Page 454
Chapter 9: Synchronization Configuring the SyncE Regenerator

Configuring the SyncE Regenerator

Note
For PTP 820E R2H ESP, SyncE Regenerator is planned for future release.

In SyncE PRC pipe regenerator mode, frequency is transported between two interfaces through the radio link.
With the system acting as a simple link, no distribution mechanism is necessary, resulting in improved frequency
distribution performance with PRC quality and a simplified configuration.

Note
SyncE Regenerator currently supports only a single pipe configuration. It cannot be used together with
1588 Transparent Clock.

To add a pipe configuration:

1. Set the Sync mode to Pipe. You must do this via the CLI. Enter the following command in root view:
root> platform sync mode set pipe

Note
By default, the Sync mode is set to Automatic. To display the current Sync mode, enter the following
command in root view:
root> platform sync mode show

2. In the Web EMS, select Sync > SyncE Regenerator. The SyncE Regenerator page opens.

Figure 377 SyncE Regenerator Page

3. Click Add underneath the Pipe Configurations Table. The Pipe Configuration - Add window opens.

Phn 3963 013v000

Page 455
Chapter 9: Synchronization Configuring the SyncE Regenerator

Figure 378 Pipe Configurations - Add Page

4. Select a Pipe ID.

5. Select one of the available interfaces for each Sync Interface.

Note
One of the Sync Interfaces must be a Radio interface and the other must be an Ethernet interface. If
the two interfaces are the same type, the operation will fail.
Only one radio port is available for PTP 820S unit.

6. Click Apply.

Phn 3963 013v000

Page 456
Chapter 9: Synchronization Configuring the Sync Source

Configuring the Sync Source

Note
To configure a sync source on which the sync source Quality parameter must be set according to
ANSI specifications and you must change the ETSI/ANSI mode to ANSI before configuring the sync
source. See Changing the ETSI/ANSI Mode (CLI).

Frequency signals can be taken by the system from Ethernet and radio interfaces.
The reference frequency may also be conveyed to external equipment through different interfaces. For
instructions how to configure the outgoing clock, see Configuring the Outgoing Clock and SSM Messages.
Frequency is distributed by configuring the following parameters in each node:
• System Synchronization Sources – These are the interfaces from which the frequency is taken and distributed
to other interfaces. Up to 16 sources can be configured in each node. A revertive timer can be configured. For
each interface, you must configure:
o Priority (1-16) – No two synchronization sources can have the same priority.
o Quality – The quality level applied to the selected synchronization source. This
enables the system to select the source with the highest quality as the current
synchronization source.
• Each unit determines the current active clock reference source interface:
o The interface with the highest available quality is selected.
o From among interfaces with identical quality, the interface with the highest priority is
selected.

When configuring the Sync source, the Sync mode must be set to its default setting of automatic. To display the
current Sync mode, enter the following CLI command in root view:
root> platform sync mode show
If the Sync mode is set to pipe, you must set it to automatic by entering the following CLI command in root view:
root> platform sync mode set automatic
When configuring an Ethernet interface as a Sync source, the Media Type of the interface must be RJ45 or SFP, not
Auto-Type. To view and configure the Media Type of an Ethernet interface, see Configuring Ethernet Interfaces.

Viewing the Sync Source Status

To view the current sync source and its quality:
1 Select Sync > Sync Source. The Sync Source page opens.

Phn 3963 013v000

Page 457
Chapter 9: Synchronization Configuring the Sync Source

Figure 379 Sync Source Page

Table 76 Sync Source Parameters

Parameter Definition

System Reference Quality The quality of the current synchronization source interface. A value of
DNU indicates that no synchronization source interfaces are currently
defined.

Current Active Sync Source The currently active system synchronization source interface.

Sync Clock Unit Status The status of the unit’s Sync E mechanism.

Sync Interface Displays the interface that is configured as a synchronization source.

Sync Interface Quality Displays the quality level assigned to this synchronization source. This
enables the system to select the source with the highest quality as the
current synchronization source.
If the Sync Interface Quality is set to Automatic, the quality is
determined by the received SSMs. If no valid SSM messages are received
or in case of interface failure (such as LOS, LOC, LOF), the quality becomes
"Failure." SSM must be enabled on the remote interface in order for the
interface to receive SSM messages. For instructions how to enable SSM,
see Configuring the Outgoing Clock and SSM Messages.

Sync Interface Priority Displays the priority assigned to this synchronization source.

Sync Interface Quality Displays the current actual synchronization quality of the interface.
Status

Adding a Sync Source

To add a synchronization source:
1 In the Sync Source page (Figure 278), click Add. The Sync Source – Add page opens.

Figure 380 Sync Source – Add Page

Phn 3963 013v000

Page 458
Chapter 9: Synchronization Configuring the Sync Source

2 In the Sync Interface field, select the interface you want to define as a synchronization source. You can
select from the following interface types:
o Ethernet interfaces
o Radio interface

Note
In order to select an Ethernet interface, you must first specify the media type for this interface. See
Configuring Ethernet Interfaces.

3 In the Sync Interface Quality field, select the quality level applied to the selected synchronization source.
This enables the system to select the source with the highest quality as the current synchronization
source.
o If the Sync Interface Quality is set to Automatic, the quality is determined by the received SSMs. If no
valid SSM messages are received or in case of interface failure (such as LOS, LOC, LOF), the quality
becomes Failure. SSM must be enabled on the remote interface in order for the interface to receive
SSM messages. For instructions how to enable SSM, see Configuring the Outgoing Clock and SSM
Messages.
o If the Sync Interface Quality is set to a fixed value, then the quality status becomes Failure upon
interface failure (such as LOS, LOC, LOF).
4 In the Sync Interface Priority field, select the priority of this synchronization source relative to other
synchronization sources configured in the unit (1-16). You cannot assign the same priority to more than
one synchronization source. Once a priority value has been assigned, it no longer appears in the Sync
Interface Priority dropdown list.
5 Click Apply, then Close.

Editing a Sync Source

To edit a synchronization source:
1 In the Sync Source page (Figure 278), click Edit. The Sync Source – Edit page opens.
2 Edit the parameters, as defined above. You can edit all the parameters except Sync Interface, which is
read-only.

Phn 3963 013v000

Page 459
Chapter 9: Synchronization Configuring the Sync Source

3 Click Apply, then Close.

Deleting a Sync Source

To delete a synchronization source:
1 Select the synchronization source in the Sync Source page (Figure 278).
2 Click Delete. The synchronization source is deleted.

Phn 3963 013v000

Page 460
Chapter 9: Synchronization Configuring the Outgoing Clock and SSM Messages

Configuring the Outgoing Clock and SSM Messages

In the Outgoing Clock page, you can view and configure the following synchronization settings per interface:
• The interface's clock source (outgoing clock).
• For radio interfaces, the synchronization radio channel (used for interoperability).
• SSM message administration.
In order to provide topological resiliency for synchronization transfer, PTP 820C implements the passing of SSM
messages over the radio interfaces. SSM timing in PTP 820C complies with ITU-T G.781.
In addition, the SSM mechanism provides reference source resiliency, since a network may have more than one
source clock. The following are the principles of operation:
• At all times, each source interface has a “quality status” which is determined as follows:
o If quality is configured as fixed, then the quality status becomes “failure” upon
interface failure (such as LOS, LOC, LOF).
o If quality is automatic, then the quality is determined by the received SSMs. If no
valid SSM messages are received or in case of interface failure (such as LOS, LOC,
LOF), the quality becomes "failure.
• Each unit holds a parameter which indicates the quality of its reference clock. This is the quality of the current
synchronization source interface.
• The reference source quality is transmitted through SSM messages to all relevant radio interfaces.
• In order to prevent loops, an SSM with quality “Do Not Use” is sent from the active source interface (both
radio and Ethernet)
In order for an interface to transmit SSM messages, SSM must be enabled on the interface. By default, SSM is
disabled on all interfaces.
When configuring the outgoing clock and SSM administration, the Sync mode must be set to its default setting of
automatic. To display the current Sync mode, enter the following CLI command in root view:
root> platform sync mode show
If the Sync mode is set to pipe, you must set it to automatic by entering the following CLI command in root view:
root> platform sync mode set automatic
To configure the outgoing clock on an Ethernet interface, the Media Type of the interface must be RJ45 or SFP, not
Auto-Type. To view and configure the Media Type of an Ethernet interface, see Configuring Ethernet Interfaces.
To view and configure the synchronization parameters of the unit’s interfaces:
1 Select Sync > Outgoing Clock. The Outgoing Clock page opens.

Phn 3963 013v000

Page 461
Chapter 9: Synchronization Configuring the Outgoing Clock and SSM Messages

Figure 381 Outgoing Clock Page

2 Select
the interface you want to configure and click Edit. The Outgoing Clock – Edit page opens.
Figure 382 Outgoing Clock – Edit Page

3 In the Outgoing clock source field, select the interface's synchronization source. Options are:
o Local Clock – The interface uses its internal clock as its synchronization source.
o System Clock – Default value. The interface uses the system clock as its synchronization source.
o Source Interface – Reserved for future use.
o Time Loop – Reserved for future use.
4 In Sync Radio Channel field, use the default value of 0.
5 In the SSM Admin field, select On or Off to enable or disable SSM for the interface. By default, SSM is
disabled on all interfaces.

Phn 3963 013v000

Page 462
Chapter 9: Synchronization Configuring 1588 Transparent Clock

Configuring 1588 Transparent Clock

Note
1588 Transparent Clock is supported by PTP 820C and PTP 820S.

PTP 820 uses 1588v2-compliant Transparent Clock to counter the effects of delay variation. Transparent Clock
measures and adjusts for delay variation, enabling the PTP 820 to guarantee ultra-low PDV.
A Transparent Clock node resides between a master and a slave node, and updates the timestamps of PTP packets
passing from the master to the slave to compensate for delay, enabling the terminating clock in the slave node to
remove the delay accrued in the Transparent Clock node. The Transparent Clock node is itself neither a master nor
a slave node, but rather, serves as a bridge between master and slave nodes.
Note that in release 11.1:
• 1588 TC is not supported when Master-Slave communication is using the IPv6 transport layer.
• 1588 TC cannot be used on 1+1 HSB links.
• 1588 TC cannot be used with 2 x 1+0 (East-West) configurations
• 1588 TC is not supported with Frame Cut-Through.

Note
Make sure to enable Transparent clock on the remote side of the link before enabling it on the local
side.

To configure Transparent Clock:

1. Add the port receiving synchronization from the customer side as a Sync source, with Sync Interface Priority 1.
See Adding a Sync Source.
2. Add a radio interface as a Sync source, with lower priority than the port receiving synchronization from the
customer side. See Adding a Sync Source.
3. On the remote side of the radio link, add the radio interface facing the local device as a Sync source, with Sync
Interface Priority 1. See Adding a Sync Source.
4. On the remote side of the radio link, if there is an Ethernet port conveying synchronization, add this port as a
Sync source, with lower priority than the radio interface. See Adding a Sync Source.
5. Verify that the Sync Interface Quality Status of the first Sync source is not Failure. See Viewing the Sync Source
Status.
6. Select Sync > 1588 > General Configuration. The 1588-General Configuration page opens.
Figure 383 1588-TC Page

Phn 3963 013v000

Page 463
Chapter 9: Synchronization Configuring 1588 Transparent Clock

7. In the 1588 PTP field, select Enable.

8. Click Apply.
9. Select Sync > 1588 > Transparent Clock. The 1588 Transparent Clock page opens.

Figure 384 1588 Transparent Clock Page

10. Select a radio interface or Multi-Carrier ABC group and click Edit. The 1588 Transparent Clock – Edit page
opens.

Figure 385 1588-TC – Edit Page

Phn 3963 013v000

Page 464
Chapter 9: Synchronization Configuring 1588 Transparent Clock

11. In the Port direction field, select Upstream or Downstream. This field must be set to different values on two
sides of the link so that if local side is set to Upstream, then the remote side of the link must be set to
Downstream and vice versa. Otherwise than the mentioned configuration, it does not matter how this field is
set.
12. Click Apply, then Close.
13. 1588 packets should be mapped to CoS 7. By default, 1588 packets are not mapped to any CoS. To map 1588
packets to CoS 7, you must disable CoS preservation for 1588 packets. This must be performed via CLI, using
the following command:
root> ethernet generalcfg ptp-tc cos-preserve set admin disable
14. To map 1588 packets to CoS 7, enter the following command:
root> ethernet generalcfg ptp-tc cos-preserve cos value 7
After you enter these commands, 1588 packets will automatically be mapped to CoS 7.

Note
If necessary, you can use the ethernet generalcfg ptp-tc cos-preserve cos value
command to map a different CoS value (0-7) to 1588 packets, but it is recommended to map 1588
packets to CoS 7.
To disable Transparent Clock synchronization:
1 Select Sync > 1588 > General Configuration. The 1588 – General Configuration page opens (Figure 320).
2 In the 1588 PTP field, select Disable.
3 Click Apply.

Note
Disabling 1588 PTP disables both Transparent Clock and Boundary Clock, and can drastically affect
time synchronization performance in the entire network.

Phn 3963 013v000

Page 465
Chapter 10: Access Management and Security Configuring 1588 Transparent Clock

Chapter 10: Access Management and

Security
This section includes:
• Quick Security Configuration
• Configuring the General Access Control Parameters
• Configuring the Password Security Parameters
• Configuring the Session Timeout
• Configuring Users
• Configuring RADIUS
• Configuring X.509 CSR Certificates
• Uploading the Security Log
• Uploading the Configuration Log

Note
Another security feature, HTTPS cipher hardening, can be configured via CLI. For instructions, see
Configuring HTTPS Cipher Hardening (CLI)
PTP 820 devices support SDN, with NETCONF/YANG capabilities. This enables PTP 820 devices to be
managed via SDN using Cambium Networks SDN controller, SDN Master. NETCONF must be enabled
via CLI. See Enabling NETCONF (CLI).

Related topics:
• Changing Your Password
• Operating in FIPS Mode
• Configuring AES-256 Payload Encryption

Phn 3963 013v000

Page 466
Chapter 10: Access Management and Security Quick Security Configuration

Quick Security Configuration

The Web EMS provides a set of Quick Configuration pages that enable you to quickly configure the unit’s access
and security parameters. This section describes these pages, with cross references to the sections in which each
parameter is described in depth.

Note
The Quick Security Configuration pages are only available in system release 10.9.6 and higher.

Quick Security Configuration – General Parameters Page

To configure the FIPS Admin, import and export security settings, session timeout, a login banner, and AES-256
payload encryption:

Note
T FIPS and AES-256 are not supported with PTP 820E.

4 Select Quick Configuration > Security > General Parameters. The Quick Configuration Security General
Parameters page opens.

Figure 386: Quick Configuration Security General Parameters Page

5 In the FIPS Mode Admin field, you can enable or disable FIPS mode. For details, see Operating in FIPS Mode.

Note
Only certain system release versions support FIPS mode. These versions include system release
8.3 and 10.9.6.

Phn 3963 013v000

Page 467
Chapter 10: Access Management and Security Quick Security Configuration

6 The Import/Export security settings field determines whether security configurations are included in
configuration backup files. If you select Enable, security configurations will not be included in backup files.
7 In the Session timeout field, you can configure a session timeout, in minutes, from 1 to 60 minutes. The default
session timeout is 10 minutes. For details, see Configuring the Session Timeout.
8 In the Login Banner Text field, you can define a login banner of up to 2,000 bytes. This banner will appear every
time a user establishes a connection with the Web EMS. The banner appears before the login prompt, so that
users will always see the login banner and must manually close the banner before logging in to the Web EMS.
For details, see Defining a Login Banner.
9 In the Radio Payload Encryption area, select an interface and click Edit to define AES-256 payload encryption.
For details, see Configuring AES-256 Payload Encryption.

Quick Security Configuration – Protocols Page

To configure the HTTP type, Telnet blocking, and SNMP parameters:
1 Select Quick Configuration > Security > Protocols. The Quick Configuration Security Protocols page opens.

Figure 387: Quick Configuration Security Protocols Page

2 In the HTTP protocol field, you can determine the web interface protocol for accessing the unit (HTTP or
HTTPS). By default, the web interface protocol is HTTP. For details, see Enabling HTTPS (CLI).

Note
After changing the HTTP protocol, management is lost. To restore management, simply refresh
the page.

3 In the Telnet Admin field, you can block or enable telnet access to the unit. By default, telnet access is enabled.
For details, see Blocking Telnet Access.
4 In the SNMP Parameters area, you can configure the unit’s SNMP parameters. For details, see Configuring
SNMP.

Phn 3963 013v000

Page 468
Chapter 10: Access Management and Security Quick Security Configuration

In addition, you can configure the following parameters only in the Quick Configuration Security Protocols
page:
i In the Block SNMP from Write Security Parameters field, select Yes if you want to block SNMP from writing
security parameters.
ii In the Block SNMP from Read Security Parameters field, select Yes if you want to block SNMP from reading
security parameters.
5 When you are finished editing the parameters described above, click Apply.
6 In the SNMP V3 Users are, you can click Add to add SNMP V3 users. For details, see Configuring SNMP.

Quick Security Configuration – Access Control Page

To configure parameters relating to users and login parameters:
1 Select Quick Configuration > Security > Access Control. The Quick Configuration Security Protocols page opens.

Figure 388: Quick Configuration Security Access Control Page

2 In the Login & Password Management area, you can configure enhanced security requirements for user
passwords and for logging into the unit. For details, see Configuring the General Access Control Parameters and
Configuring the Password Security Parameters.
3 When you are finished editing the login and password parameters, click Apply.
4 In the User Accounts area, you can configure individual users:
• To add a user, click Add.
• To edit an existing user, select the user in the User Accounts table and click Edit.
For details, see Configuring Users.
5 To configure user profiles, click Access Control User Profiles. For details, see Configuring User Profiles.

Phn 3963 013v000

Page 469
Chapter 10: Access Management and Security Quick Security Configuration

Quick Security Configuration – RSA Key & Certificate Page

To download and install an RSA key and/or a Certificate Signing Request (CSR) file:
1 Select Quick Configuration > Security > RSA Key & Certificate. The Quick Configuration Security RSA Key &
Certificate page opens.

Figure 389: Quick Configuration Security RSA Key & Certificate Page

2 In the RSA Key Download Status area, you can download and install an RSA key. For details, see Downloading
and Installing an RSA Key.
3 In the Download Certification Status area, you can download and install a CSR file. For details, see Configuring
X.509 CSR Certificates and HTTPS.

Phn 3963 013v000

Page 470
Chapter 10: Access Management and Security Configuring the General Access Control Parameters

Configuring the General Access Control Parameters

To avoid unauthorized login to the system, PTP 820 automatically blocks users upon a configurable number of
failed login attempts. You can also configure PTP 820 to block users that have not logged into the unit for a defined
number of days.
To configure the blocking criteria:
1. Select Platform > Security > Access Control > General. The Access Control General Configuration page opens.

Figure 390 Access Control General Configuration Page

2. In the Failure login attempts to block user field, select the number of failed login attempts that will trigger
blocking. If a user attempts to login to the system with incorrect credentials this number of times
consecutively, the user will temporarily be prevented from logging into the system for the time period defined
in the Blocking period field. Valid values are 1-10. The default value is 3.
3. In the Blocking period (Minutes) field, enter the length of time, in minutes, that a user is prevented from
logging into the system after the defined number of failed login attempts. Valid values are 1-60. The default
value is 5.
4. In the Unused account period for blocking (Days) field, you can configure a number of days after which a user
is prevented from logging into the system if the user has not logged in for the configured number of days.
Valid values are 0, or 30-90. If you enter 0, this feature is disabled. The default value is 0.
5. Click Apply.

Phn 3963 013v000

Page 471
Chapter 10: Access Management and Security Configuring the General Access Control Parameters

Once a user is blocked, you can unblock the user from the User Accounts page. To unblock a user:
1. Select Platform > Security > Access Control > User Accounts. The Access Control User Accounts page opens
(Figure 291).
2. Select the user and click Edit. The Access Control User Accounts - Edit page opens.

Figure 391 Access Control User Accounts - Edit Page

3. In the Blocked field, select No.

4. Click Apply, then Close.

Phn 3963 013v000

Page 472
Chapter 10: Access Management and Security Configuring the Password Security Parameters

Configuring the Password Security Parameters

To configure enhanced security requirements for user passwords:

1. Select Platform > Security > Access Control > Password Management. The Access Control Password
Management page opens.

Figure 392 Access Control Password Management Page

2. In the Enforce password strength field, select Yes or No. When Yes is selected:
o Password length must be at least eight characters.
o Password must include characters of at least three of the following character types:
lower case letters, upper case letters, digits, and special characters. For purposes of
meeting this requirement, upper case letters at the beginning of the password and
digits at the end of the password are not counted.
o The last five password you used cannot be reused.
3. In the Password change for first login field, select Yes or No. When Yes is selected, the system requires the
user to change his or her password the first time the user logs in.
4. In the Password aging (Days) field, select the number of days that user passwords will remain valid from the
first time the user logs into the system. You can enter 20-90, or No Aging. If you select No Aging, password
aging is disabled and passwords remain valid indefinitely.

Phn 3963 013v000

Page 473
Chapter 10: Access Management and Security Configuring the Password Security Parameters

5. Click Apply.

Phn 3963 013v000

Page 474
Chapter 10: Access Management and Security Configuring the Session Timeout

Configuring the Session Timeout

By default, there is a 10 minute session timeout. If you do not perform any activity on the system for the period of
time defined as the session timeout, the user session times out and you will have to log in to the system again.
To modify the session timeout:
1. Select Platform > Security > Protocols Control. The Protocols Control page opens.

Figure 393 Protocols Control Page

2. In the Session timeout (Minutes) field, select a session timeout, in minutes, from 1 to 60.
3. Click Apply.

Phn 3963 013v000

Page 475
Chapter 10: Access Management and Security Configuring Users

Configuring Users

This section includes:

• User Configuration Overview
• Configuring User Profiles
• Configuring Users
Related topics:
• Changing Your Password

User Configuration Overview

User configuration is based on the Role-Based Access Control (RBAC) model. According to the RBAC model,
permissions to perform certain operations are assigned to specific roles. Users are assigned to particular roles, and
through those role assignments acquire the permissions to perform particular system functions.
In the PTP 820 GUI, these roles are called user profiles. Up to 50 user profiles can be configured. Each profile
contains a set of privilege levels per functionality group, and defines the management protocols (access channels)
that can be used to access the system by users to whom the user profile is assigned.
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. For each functionality group, the access
level is defined separately for read and write operations. The following access levels can be assigned:
• None – No access to this functional group.
• Normal – The user has access to parameters that require basic knowledge about the functional group.
• Advanced – The user has access to parameters that require advanced knowledge about the functional group,
as well as parameters that have a significant impact on the system as a whole, such as restoring the
configuration to factory default settings.

Configuring User Profiles

User profiles enable you to define system access levels. Each user must be assigned a user profile. Each user profile
contains a detailed set of read and write permission levels per functionality group.
The system includes a number of pre-defined user profiles. You can edit these profiles, and add user profiles.
Together, the system supports up to 50 user profiles.

Phn 3963 013v000

Page 476
Chapter 10: Access Management and Security Configuring Users

To add a user profile:

1. Select Platform > Security > Access Control > User Profiles. The Access Control User Profiles page opens.

Figure 394 Access Control User Profiles Page

2. Click Add. The Access Control User Profiles - Add page opens.

Phn 3963 013v000

Page 477
Chapter 10: Access Management and Security Configuring Users

Figure 395 Access Control User Profiles - Add Page

3. In the Profile field, enter a name for the profile. The profile name can include up to 49 characters. Once you
have created the user profile, you cannot change its name.

Note
The Usage counter field displays the number of users to whom the user profile is assigned.

4. In the Permitted access channels row, select the access channels the user will be permitted to use to access
the system.
5. For each functionality group, select one of these options for write level and read level. All users with this
profile will be assigned these access levels:
o None
o Normal
o Advanced
6. Click Apply, then Close.
To view a user profile, click + next to the profile you want to view.
To edit a user profile, select the profile and click Edit. You can edit all of the profile parameters except the profile
name.
To delete a user profile, select the profile and click Delete.

Phn 3963 013v000

Page 478
Chapter 10: Access Management and Security Configuring Users

Note
You cannot delete a user profile if the profile is assigned to any users.

Configuring Users
You can configure up to 2,000 users. Each user has a user name, password, and user profile. The user profile
defines a set of read and write permission levels per functionality group. See Configuring User Profiles.
To add a new user:
1. Select Platform > Security > Access Control > User Accounts. The Access Control User Accounts page opens.

Figure 396 Access Control User Accounts Page

2. Click Add. The Access Control User Profiles - Add page opens.

Phn 3963 013v000

Page 479
Chapter 10: Access Management and Security Configuring Users

Figure 397 Access Control User Accounts - Add Page

3. In the User name field, enter a user name for the user. The user name can be up to 32 characters.
4. In the Profile field, select a User Profile. The User Profile defines the user’s access levels for functionality
groups in the system. See Configuring User Profiles.
5. In the Password field, enter a password for the user. If Enforce Password Strength is activated (see
Configuring the Password Security Parameters), the password must meet the following criteria:
o Password length must be at least eight characters.
o Password must include characters of at least three of the following character types:
lower case letters, upper case letters, digits, and special characters. For purposes of
meeting this requirement, upper case letters at the beginning of the password and
digits at the end of the password are not counted.
o The last five passwords you used cannot be reused.
6. In the Blocked field, you can block or unblock the user. Selecting Yes blocks the user. You can use this option
to block a user temporarily, without deleting the user from the system. If you set this option to Yes while the
user is logged into the system, the user will be automatically logged out of the system within 30 seconds.

Note
Users can also be blocked by the system automatically. You can unblock the user by selecting No in
the Blocked field. See Configuring the General Access Control Parameters.

7. Optionally, in the Expiration date field, you can configure the user to remain active only until a defined date.
After that date, the user automatically becomes inactive. To set an expiration date, click the calendar icon and
select a date, or enter a date in the format dd-mm-yyyy. The latest date that can be configured is 30-12-2037

Note
If no expiration date is configured, the user account will expire five years after the date configured on
the unit.

Phn 3963 013v000

Page 480
Chapter 10: Access Management and Security Configuring Users

In addition to the configurable parameters described above, the Access Control User Accounts page displays the
following information for each user:
o Login Status – Indicates whether the user is currently logged into the system.
o Last Logout – The date and time the user most recently logged out of the system.
To edit a user’s account details, select the user and click Edit. You can edit all of the user account parameters
except the User name and password.
To add a user, click Add.
To delete a user, select the user and click Delete.

Phn 3963 013v000

Page 481
Chapter 10: Access Management and Security Configuring RADIUS

Configuring RADIUS

This section includes:

• RADIUS Overview
• Activating RADIUS Authentication
• Configuring the RADIUS Server Attributes
• Viewing RADIUS User Permissions and Connectivity
• Configuring a RADIUS Server

RADIUS Overview
The RADIUS protocol provides centralized user management services. PTP 820 supports RADIUS server and
provides a RADIUS client for authentication and authorization. When RADIUS is enabled, a user attempting to log
into the system from any access channel (CLI, WEB, NMS) is not authenticated locally. Instead, the user’s
credentials are sent to a centralized standard RADIUS server which indicates to the PTP 820 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
You can define up to two Radius servers. If you define two, one serves as the primary server and the other as the
secondary server.

Activating RADIUS Authentication

To activate RADIUS authentication:
1. Select Platform > Security > Access Control > Remote Access Control. The Radius Configuration page opens.

Phn 3963 013v000

Page 482
Chapter 10: Access Management and Security Configuring RADIUS

Figure 398 Remote Access Control Configuration Page

2. In the Select Remote Access Protocol to Configure field, select RADIUS.

3. Configure the RADIUS server attributes. See Configuring the RADIUS Server Attributes.
4. In the Radius Admin field, select Enable.
5. Click Apply.

Note
When the Protocol is changed, all active sessions are terminated when you click Apply.

Configuring the RADIUS Server Attributes

To configure the RADIUS server attributes:
1. Select Platform > Security > Access Control > Remote Access Control. The Remote Access Control
Configuration page opens (Figure 293).
2. In the Radius Configuration table, select the line that corresponds to the RADIUS server you want to configure:
o Select Server ID 1 to configure the Primary Radius server.
o Select Server ID 2 to configure the Secondary Radius server.
3. Click Edit. The Radius Configuration – Edit page opens.

Phn 3963 013v000

Page 483
Chapter 10: Access Management and Security Configuring RADIUS

Figure 399 Radius Configuration – Edit Page

4. In the IPV4 address field, enter the IP address of the RADIUS server.
5. In the Port field, enter the port ID of the RADIUS protocol in the RADIUS server.
6. In the Retries field, enter the number of times the unit will try to communicate with the RADIUS server before
declaring the server to be unreachable.
7. In the Timeout field, enter the timeout (in seconds) that the agent will wait in each communication with the
selected RADIUS server before retrying if no response is received.
8. In the Secret field, enter the shared secret of the RADIUS server. The string must be between 22-128
characters long.
9. Click Apply, then Close.
In addition to the configurable parameters described above, the Remote Access Control Configuration page
displays the following information for each RADIUS server:
• Server Id – The server ID of the Radius server:
o 1 – The primary Radius server.
o 2 – The secondary Radius server.
• Connectivity Status – The connectivity status of the Radius server in the last attempted connection:
o True – The last connection attempt succeeded.
o False – The last connection attempt failed.

Viewing RADIUS User Permissions and Connectivity

You can view RADIUS user connectivity and permissions information for all Radius users currently connected.
To view RADIUS users:
1. Select Platform > Security > Access Control > Radius > Radius Users. The Radius Users page opens.

Figure 400 Radius Users Page

Phn 3963 013v000

Page 484
Chapter 10: Access Management and Security Configuring RADIUS

o The User ID column displays the user’s name.

o The Access Channels column displays the access channels the user is allowed to use
to access the unit.
o The User Instances column displays the number of open sessions the user currently
has.
To view the user’s authorized access levels, click + next to the user name. The page refreshes and displays the
additional access level information.

Figure 401 Radius Users Page – Expanded

Phn 3963 013v000

Page 485
Chapter 10: Access Management and Security Configuring RADIUS

For each of the six functional groups (Ethernet, Management, Radio, Security, Sync, TDM), the page displays the
Read access level (None, Regular, or Advanced), and the Write access level (None, Regular, or Advanced).

Configuring a RADIUS Server

If you want to use the PTP 820 RADIUS feature, you must first install a RADIUS server and configure it to work with
the PTP 820 device.
The following subsections describe how to configure a Win2008 RADIUS server and a Linux FreeRADIUS server to
work with a PTP 820. For the sake of simplicity, the subsections describe how to create three users: an Advanced
user with Advanced read/write permissions, a Normal user with regular read/write permissions, and a Viewer user
with no read/write permissions.

Note
These RADIUS servers are third-party software. The instructions provided in this section are
illustrative only and are provided for the convenience of PTP 820 users. For exact and up-to-date
instructions, we urge you to rely on the documentation provided with the RADIUS server you are
using. Ceragon is not responsible for syntax changes or variations in different GNU distributions.

Configuring a Win 2008 RADIUS Server

The following sub-sections describe how to configure a Win 2008 RADIUS Server to work with a PTP 820 device.

Step 1 – Creating Groups and Users

To create groups and users:
1. Create three user groups, as follows:
i In the Server Manager, navigate to Configuration > Local Users and Groups.
ii Right click Groups and create the following three user groups:

Phn 3963 013v000

Page 486
Chapter 10: Access Management and Security Configuring RADIUS

• Radius_Advanced
• Radius_Normal
• Radius_Viewer
Figure 402 Server Manager – Creating User Groups

2. Create three users:

o u1
o u2
o u3

Phn 3963 013v000

Page 487
Chapter 10: Access Management and Security Configuring RADIUS

Figure 403 Server Manager – Creating Users

Phn 3963 013v000

Page 488
Chapter 10: Access Management and Security Configuring RADIUS

3. In the Device Properties – General tab, make sure to select Password never expires. If you leave the default
setting (User must change password at next logon), authentication may fail.

Figure 404: Server Manager – User Password Settings

4 Attach each user to a group, as follows:

o Attach u1 to Radius_Advanced
o Attach u2 to Radius_Normal
o Attach u3 to Radius_Viewer

Phn 3963 013v000

Page 489
Chapter 10: Access Management and Security Configuring RADIUS

Step 2 – Creating a RADIUS Client

Define the PTP 820 device as a RADIUS client, as follows:
1 In the Server Manager, navigate to Roles > Network Policy and Access Services > NPS (Local) > RADIUS
Clients and Servers > RADIUS Clients.
2 Right-click RADIUS Clients, and select New RADIUS Client. The New RADIUS Client window appears.

Figure 405 Server Manager – Creating a RADIUS Client

Phn 3963 013v000

Page 490
Chapter 10: Access Management and Security Configuring RADIUS

3 In the New RADIUS Client window:

i Select the Enable this RADIUS client check box.
ii Enter a descriptive Friendly name for the device, such as PTP 820X.
iii Enter the device IP Address.
iv Select RADIUS Standard as the Vendor name.
v In the Shared Secret section, select Manual, and enter a Shared secret, then enter it again in Confirm
shared secret. Note down the secret because you will need to enter the same value in the Secret field
of the Radius Configuration – Edit page (Figure 294).

Step 3 – Creating a Network Policy

Create a network policy for each of the three groups you created: Radius_Advanced, Radius_Normal,
Radius_Viewer. That is, follow the instructions in this section, for each of the three groups.
To create a network policy:
1 In the Server Manager, navigate to Roles > Network Policy and Access Service > NPS (Local) > Policies >
Network Policies.
2 Right-click Network Policies, and select New. The New Network Policy wizard appears.
3 In the specify Network Policy Name and Connection Type, give the policy a descriptive name, indicating
whether it is a policy for the Advanced, the Normal or the Viewer group.

Phn 3963 013v000

Page 491
Chapter 10: Access Management and Security Configuring RADIUS

Figure 406 Create Network Policy – Specify Name and Connection Type

4 Click Next.
5 In the Specify Conditions window, click Add.
6 In the Select Condition window that appears, select the User Groups condition and click Add.

Phn 3963 013v000

Page 492
Chapter 10: Access Management and Security Configuring RADIUS

Figure 407 Create Network Policy – Select Condition

7 In the User Groups window that appears, click Add Groups.

8 In the Select Group window that appears, click Advanced.
9 In the Select Group window that appears, click Find Now to list all groups, and then select the appropriate
group from the list: Radius_Advanced, Radius_Normal, or Radius_Viewer.
10 Click OK.

Phn 3963 013v000

Page 493
Chapter 10: Access Management and Security Configuring RADIUS

Figure 408 Create Network Policy – User Group added to Policy’s Conditions

11 Click OK to save settings.

12 Click Next.

Phn 3963 013v000

Page 494
Chapter 10: Access Management and Security Configuring RADIUS

13 In the Specify Access Permission window that appears, select the Access Granted option.

Figure 409 Create Network Policy – Specifying Access Permission

14 Click Next.

Phn 3963 013v000

Page 495
Chapter 10: Access Management and Security Configuring RADIUS

15 In the Configure Authentication Methods window that appears, make sure only the Unencrypted
Authentication (PAP, SPAP) option is selected.

Figure 410 Create Network Policy – Configuring Authentication Methods

16 In the query window that appears, click No.

Figure 411 Create Network Policy – Insecure Authentication Method Query

Phn 3963 013v000

Page 496
Chapter 10: Access Management and Security Configuring RADIUS

17 In the Configure Constraints window that appears, click Next.

Figure 412 Create Network Policy – Configuring Constraints

Phn 3963 013v000

Page 497
Chapter 10: Access Management and Security Configuring RADIUS

18 In the Configure Settings window that appears:

i Remove all Standard RADIUS attributes. Make sure the Attributes table is empty.

Figure 413 Create Network Policy – Configuring Settings

ii Select the Vendor Specific checkbox and click Add under the Attributes table.

Phn 3963 013v000

Page 498
Chapter 10: Access Management and Security Configuring RADIUS

19 In the Add Vendor Specific Attribute window that appears:

i Select Custom in the Vendor drop down field.
ii Click Add.

Figure 414 Create Network Policy – Adding Vendor Specific Attributes

Phn 3963 013v000

Page 499
Chapter 10: Access Management and Security Configuring RADIUS

20 In the Attribute Information window that appears, click Add.

Figure 415 Create Network Policy – Selecting to Add Attribute Information

Phn 3963 013v000

Page 500
Chapter 10: Access Management and Security Configuring RADIUS

21 In the Vendor-Specific Attribute Information window that appears:

i Select Enter Vendor Code.
ii Enter 2281 in the Enter Vendor Code field.
iii Select the option Yes. It conforms.
iv Click Configure Attribute.

Figure 416 Create Network Policy – Specifying the Vendor

22 In the Configure VSA (RFC Compliant) window that appears, configure 13 attributes as follows:
i For Vendor-assigned attribute number from 21 till 32, select Decimal in the Attribute format field. These
twelve attributes define the Read access level (None, Regular, or Advanced), and the Write access level
(None, Regular, or Advanced) for each of the six functional groups (Ethernet, Management, Radio,

Phn 3963 013v000

Page 501
Chapter 10: Access Management and Security Configuring RADIUS

Security, Sync, TDM). Therefore, in the Attribute value field enter the value corresponding to the access
level you wish to permit to members of the group whose policy you are configuring, where:
• 2 = Advanced
• 1 = Regular
• 0 = None
Thus for example, enter 2 for all twelve attributes if you are configuring a policy for
the Radius_Advanced group. This gives Advanced read permissions and Advanced
write permissions, for all six functional groups, to the members of the
Radius_Advanced group.
Figure 417 Create Network Policy – Configuring Vendor-Specific Attribute Information

ii For Vendor-assigned attribute number 50, select Decimal in the Attribute format field. The Attribute
value of this attribute defines the access channel(s) permitted to members of the group whose policy you

Phn 3963 013v000

Page 502
Chapter 10: Access Management and Security Configuring RADIUS

are configuring. The Attribute value is the sum of the values corresponding to the access channels you
wish to permit, where the value for each access channel is:
• none=0
• serial=1
• telnet=2
• ssh=4
• web=8
• nms=16
• snmp=32
• snmpV3=64
Thus for example, enter 127 to allow access from all channels:
Serial + Telnet + SSH + Web + NMS + SNMP +SNMPv3;

Or enter 24 to allow access only from NMS + SNMP channels.

iii Click OK.
23 Click OK.
The following figure shows the Attributes table for the Radius_Advanced group, where access to
the device is allowed from all channels.

Figure 418 Create Network Policy – Example of Vendor-Specific Attribute Configuration

24 Close all opened windows and click Next.

25 In the Completing New Network Policy window, click Finish.

Phn 3963 013v000

Page 503
Chapter 10: Access Management and Security Configuring RADIUS

26 Reset the Network Policy Server (NPS) by stopping and starting the NPS service as follows:
i Right click the NPS (Local) node, and select Stop NPS Service.
ii Right click the NPS (Local) node, and select Start NPS Service.

Figure 419 Create Network Policy – Stopping/Starting NPS Services

Configuring a Linux FreeRADIUS Server

The following sub-sections describe how to configure a Linux FreeRADIUS server to work with a PTP 820 device.
To so do, you will need to modify the following three files:
• /etc/raddb/users
• /etc/raddb/clients.conf
• /usr/share/freeradius/dictionary.cambium
• /etc/raddb/dictionary

Step 1 – Creating Users

This step describes how to create the following three users:

• u1 – with advanced read/write privileges, password 1111

• u2 – with normal read/write privileges, password 2222
• u3 – with no read/write privileges, password 3333

Phn 3963 013v000

Page 504
Chapter 10: Access Management and Security Configuring RADIUS

To create these RADIUS users:

1 Add the users in the /etc/raddb/users file, using any editor you like, according to the following example:
# user1 - advanced privileges

u1 auth-type := local, Cleartext-Password := "1111"

security-ro = advanced,

security-wo = advanced,

mng-ro = advanced,

mng-wo = advanced,

radio-ro = advanced,

radio-wo = advanced,

tdm-ro = advanced,
tdm-wo = advanced,

eth-ro = advanced,

eth-wo = advanced,

sync-ro = advanced,

sync-wo = advanced,

access_channel = u1accesschannel,

fall-through = yes

# user2 - regular privileges

u2 auth-type := local, Cleartext-Password := "2222"

security-ro = regular,

security-wo = regular,

mng-ro = regular,

mng-wo = regular,

radio-ro = regular,

radio-wo = regular,

tdm-ro = regular,

tdm-wo = regular,

eth-ro = regular,

eth-wo = regular,

sync-ro = regular,

sync-wo = regular,

access_channel = u2accesschannel,

fall-through = yes

Phn 3963 013v000

Page 505
Chapter 10: Access Management and Security Configuring RADIUS

# user3 - no privilege (viewer)

u3 auth-type := local, Cleartext-Password := "3333"

security-ro = none,

security-wo = none,

mng-ro = none,

mng-wo = none,

radio-ro = none,

radio-wo = none,

tdm-ro = none,

tdm-wo = none,

eth-ro = none,

eth-wo = none,

sync-ro = none,

sync-wo = none,

access_channel = u3accesschannel,

fall-through = yes
2 Save the changes in the /etc/raddb/users file.

Step 2 – Defining the Permitted Access Channels

The access_channel of each user we configured in the /etc/raddb/users file, defines the channels through which that
user is allowed to access the unit.
This is done by summing the values corresponding to the allowed channels, where the values are:
### none 0

### serial 1

### telnet 2

### ssh 4

### web 8

### nms 16

### snmp 32

### snmpV3 64
For example:
• The value 127 denotes permission to access the device from all channels:
Serial + Telnet + SSH + Web + NMS + SNMP +SNMPv3
• The value 24 indicates permission to access the device only from the Web + NMS channels.

Phn 3963 013v000

Page 506
Chapter 10: Access Management and Security Configuring RADIUS

To define each user’s access channels:

1 In the usr/share/freeradius/dictionary.cambium file, configure the values of the access channels according to the
following example:
### access channel for u1 user:serial+telnet+ssh+web+nms+snmp+snmpV4

VALUE ACCESS_CHANNEL u1accesschannel 127

2 Save the changes to the usr/share/freeradius/dictionary. cambium file.

Step 3 – Specifying the RADIUS client

This step describes how to define a device as a RADIUS client. The RADIUS server accepts attempts to connect to a
device only if that is device is defined as a RADIUS client.
To define a device as a RADIUS client:
1 In the /etc/raddb/clients.conf file, add the device according to the following example.
The example shows how to add a PTP 820G device with IP address 192.168.1.118:
# PTP 820C

client 192.168.1.118 {

secret = default_not_applicable

shortname = cambium -ptp 820G

Keep in mind:
o The secret must be between 22 and 128 characters long. Note down the secret
because you will need to enter the same value in the Secret field of the Radius
Configuration – Edit page (Figure 294).
o The shortname is not mandatory, but should be added, and should be different for
each RADIUS client.
2 Save the changes to the /etc/raddb/clients.conf file.

Step 4 – Adding a call to the Cambium Dictionary File

To add a call to the Cambium dictionary file:
1. Add the following at the end of the /etc/raddb/dictionary file, using any editor you like:

#include the dictionary.cambium file

$INCLUDE dictionary.cambium
2. Save the changes in the /etc/raddb/dictionary file.

Note
Make sure to use absolute path mode if the target file is located in a different directory. For
example:
$INCLUDE ../share/freeradius/dictionary.cambium)

Step 5 – Restarting the RADIUS Server

After configuring all of the above, restart the RADIUS process.

Phn 3963 013v000

Page 507
Chapter 10: Access Management and Security Configuring RADIUS

To restart the RADIUS process:

1 Stop the process by entering:
killall -9 radiusd
2 Start the process running in the background by entering:
radius –X &

Note
To check the logs each time a user connects to the server, enter:
radius –X &

Phn 3963 013v000

Page 508
Chapter 10: Access Management and Security Configuring X.509 CSR Certificates and HTTPS

Configuring X.509 CSR Certificates and HTTPS

The web interface protocol for accessing PTP 820 can be configured to HTTP (default) or HTTPS. It cannot be set to
both at the same time.
Before setting the protocol to HTTPS, you must:
1. Create and upload a CSR file. See Generating a Certificate Signing Request (CSR) File.
2. Download the certificate to the PTP 820 and install the certificate. See Downloading a Certificate.
3. Enable HTTPS. This must be performed via CLI. See Enabling HTTPS (CLI).
When uploading a CSR and downloading a certificate, the PTP 820 functions as an SFTP client. You must install
SFTP server software on the PC or laptop you are using to perform the upload or download. For details, see
Installing and Configuring an FTP or SFTP Server.

Note
For these operations, SFTP must be used.

Generating a Certificate Signing Request (CSR) File

Note
If you need a customized public RSA key, you must download and install the RSA key first, before
generating a CSR file. Otherwise, the CSR file will include the current public RSA key. See Downloading
and Installing an RSA Key.

To generate a Certificate Signing Request (CSR) file:

1. Select Platform > Security > X.509 Certificate > CSR. The Security Certificate Request page opens.

Phn 3963 013v000

Page 509
Chapter 10: Access Management and Security Configuring X.509 CSR Certificates and HTTPS

Figure 420 Security Certificate Request Page

2. In the Common Name field, enter the fully–qualified domain name for your web server. You must enter the
exact domain name.
3. In the Organization field, enter the exact legal name of your organization. Do not abbreviate.
4. In the Organization Unit field, enter the division of the organization that handles the certificate.
5. In the Locality field, enter the city in which the organization is legally located.
6. In the State field, enter the state, province, or region in which the organization is located. Do not abbreviate.
7. In the Country field, enter the two-letter ISO abbreviation for your country (e.g., US).
8. In the Email field, enter an e-mail address that can be used to contact your organization.
9. In the File Format field, select the PEM or DER to determine the file format.

Note
In this version, only PEM is supported.

10. Click Apply to save your settings.

11. Click FTP Parameters to display the FTP Parameters page.

Phn 3963 013v000

Page 510
Chapter 10: Access Management and Security Configuring X.509 CSR Certificates and HTTPS

Figure 421 FTP Parameters Page (Security Certificate Request)

12. In the Username field, enter the user name you configured in the SFTP server.
13. In the Password field, enter the password you configured in the SFTP server. If you did not configure a
password for your SFTP user, simply leave this field blank.
14. In the Path field, enter the directory path to which you are uploading the CSR. Enter the path relative to the
SFTP user's home directory, not the absolute path. If the location is the home directory, it should be left
empty. If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is
"C:\", this parameter can be left empty or populated with "//".
15. In the File name field, enter the name you want to give to the exported CSR.
16. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
SFTP server in the Server IPV4 address field. See Defining the IP Protocol Version for Initiating
Communications.
17. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
SFTP server in the Server IPv6 address field. See Defining the IP Protocol Version for Initiating
Communications.
18. Click Apply, then Close, to save the FTP parameters and return to the Security Log Upload page.
19. Click Generate & Upload. The file is generated and uploaded.
The CSR Status field displays the status of any pending CSR generation and upload. Possible values are:
o Ready – The default value, which appears when CSR generation and upload is in
progress.
o File-in-transfer – The upload operation is in progress.
o Success – The file has been successfully uploaded.
o Failure – The file was not successfully uploaded.
The CSR Percentage field displays the progress of any current CSR upload operation.

Downloading a Certificate
To download a certificate:
1. Select Platform > Security > X.509 Certificate > Download & Install. The Security Certification Download and
Install page opens.

Phn 3963 013v000

Page 511
Chapter 10: Access Management and Security Configuring X.509 CSR Certificates and HTTPS

Figure 422 Security Certification Download and Install Page

2. Click FTP Parameters to display the FTP Parameters page

Figure 423 FTP Parameters Page (Security Certification Download & Install)

3. In the User name for logging field, enter the user name you configured in the SFTP server.
4. In the User password to server field, enter the password you configured in the SFTP server. If you did not
configure a password for your SFTP user, simply leave this field blank.

Phn 3963 013v000

Page 512
Chapter 10: Access Management and Security Configuring X.509 CSR Certificates and HTTPS

5. In the Path field, enter the directory path from which you are uploading the certificate. Enter the path relative
to the SFTP user’s home directory, not the absolute path. If the location is the home directory, it should be left
empty. If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is
"C:\", this parameter can be left empty or populated with "//".
6. In the File Name field, enter the certificate’s file name in the SFTP server.
7. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
SFTP server in the Server IPV4 address field. See Defining the IP Protocol Version for Initiating
Communications.
8. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
SFTP server in the Server IPv6 address field. See Defining the IP Protocol Version for Initiating
Communications.
9. Click Apply to save your settings.
10. Click Download. The certificate is downloaded.
11. Click Install. The certificate is installed on the PTP 820.

Enabling HTTPS
By default, HTTP is used by PTP 820 as its web interface protocol.
To enable HTTPS instead of HTTP:
1. Select Platform > Security > Protocols Control. The Protocols Control page
2. opens (Figure 370).
3. In the HTTP protocol field, select HTTPS.
4. Click Apply.

Note
Make sure you have installed a valid certificate in the PTP 820 before changing the web interface
protocol to HTTPS. Failure to do this may prevent users from accessing the Web EMS.

Phn 3963 013v000

Page 513
Chapter 10: Access Management and Security Downloading and Installing an RSA Key

Downloading and Installing an RSA Key

PTP 820 devices support RSA keys for communication using HTTPS and SSH protocol. The PTP 820 device comes
with randomly generated default private and public RSA keys. However, you can replace the private key with a
customer-defined private key. The corresponding RSA public key will be generated based on this private key. The
file must be in PEM format. Supported RSA private key sizes are 2048, 4096, and 8192.
The following is an example of a valid RSA private key file:
-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC+7jRmt27yF4xDh5Pc8w4ikvXUu32BI0eOyELmeUB
nEeIHbCOXD3upi8+ZnH51Q+8hzgoSqXgEYFgZMoF/sXCrO2yf62UJ5ohj3zadhx/7585zoGwHtYz1S62hsa4+cdAl/i1Vbc
6CoUBh5642XYje+Q+q1XJtObed884eaQcXUFLlBipYKvVx2kuelymansE91WJU+UjFlc3aiQG8qsSgW5Ar6wet0pXkP2V
demo//QAXXjcTqqMBuizrlhlcvi+OKYFl9kSh21ZqSgjvK3cfAssCJBIY5d6t6bVkX9p2gjo/IPnErjAv7W6lZoemotb5KAeSHe
R1sYTw17/xIpM7AgMBAAECggEAAwliLKQMOq4kh/UXD/OPAlPDXyp1jjaTw8dBm811OG5wttzXGrxJ+OIFX5Rn79Db
HnbayCiJL8tMe2dx5yhY+hA247roX3ua0w57cuPxnp21izc+S0fC7H/TTM1jpRCbATparuTRMlitinZshJGA73Lsod3v36GE
Xxm/6dHnz/drCs2F4NdHWpjMAAG/1CiBwut8jNkJUwa78Ivk3JF+XRoZ0txN2mIybQxxzjuNXqZbNO6H3Ua2u1iYyD+
McfgOWCCUfSnstGRhFg0OsQuqj6d74qKVQWaukEH91SVZHEoqX6DgpKy4INZBxORZmlTNmadwNhw5O7rvFxZ205u
4gQKBgQDT5bXvc0Ok+Ypm2xnIbu2GFjxNYwYhR3TvHPy14NIO5Q9I/uDqwrSL1igzalr6EbZyLu8cDXa4aybrzCyBfPeG8
9Qq+a6J3JR/RwJndLyjV4h5CT8Zy4O/wjgTrP3Rhq7LAbWgLjSarafLgruHTcnOifhkK7MK7Fr+xi2IJfOKQQKBgQDmq1eY
NzlMPlATESlsfbkcL49jSsu70kYg0g5Iol6+bVPo9K7mopICtWC/fwdNlUAfO+vr/231YUfSo7YNEDNNRoT/NwvqqtAYxZaI
UdIQxhMywF9jjYBBuq6+f/7+dwDfNBtMb2q7hceTdk6yZ8/MehCkvSwOBmP+lq0FwTmmewKBgQClxmj31G1ve+rTX
UZmkKIy7OJwiLAbCRRqnXr3r9Om43151i2QfJNTc1AwKVzTl1ftLNrUT5Q541qnzyxigaoFYmzy0jPCl1d128/9sE6EW87
hImLDg3ynYQMOIaDRc1T8bXHyxzNQb9t+U+DykeD4POifNbD1MsRd3h1xDn/iAQKBgHmKpukJkCNgYgjp7g3AYR084i
zLaHZa4aDBjc0v4QQtzxzccJwN5SmQMJ42bL6wecz7YeBEAshcrd+La42Oj7mUAtgHRTwtLOEgm6TQmANGmy8OtjRa
hs4bc5/lCZNDWS5C4m9v9alBYFuO5wCSOqffWY20L9Zj/6RR+HEj0yCpAoGAHwrbRqPVZtZptFuNsCq130dtmqI7HFQ
Alqrc5DwP7YSsznE6biHfLUw891xu0vmevALrCaoeOMaidugohgiorSJO4qk7I3XN3pUJhPYqbhtdCVnBI2Fm9pr3V/SHG
vrl1NW92cXObeQ2UEBiKPOyQKfOBlbac707u0HqaTu+/ts=
-----END PRIVATE KEY-----

Phn 3963 013v000

Page 514
Chapter 10: Access Management and Security Downloading and Installing an RSA Key

To download and install a private RSA key:

1 Select Platform > Security > RSA Key. The RSA Key Download & Install page opens.

Figure 424: RSA Key Download & Install Page (HTTP Selected)

2 Select HTTP to download the file via HTTP/HTTPS or FTP to download the file via SFTP.

Note
It is strongly recommended not to use HTTP to download RSA key files.

Downloading an RSA Key via HTTP or HTTPS

To download and install a private RSA key file using HTTP or HTTPS:
1 Select HTTP.
2 Click Choose Private Key File.
3 Browse to and select the file.
4 Click Download. The download begins. You can view the status of the download in the Download Status field. See
Table 75.
5 Once the download has been completed, click Install to install the RSA key file. You can view the status of the
installation in the Install Status field. See Table 75.

Note
To discontinue the download process, click Abort.

Phn 3963 013v000

Page 515
Chapter 10: Access Management and Security Downloading and Installing an RSA Key

Downloading an RSA Key via SFTP

To download and install a private RSA key file using SFTP:
1 Install and configure SFTP server software on the PC or laptop you are using to perform the software upgrade.
See Installing and Configuring an FTP or SFTP Server.
2 In the RSA Key Download & Install page, select FTP.

Figure 425: RSA Key Download & Install Page (FTP Selected)

3 Click FTP Parameters to display the FTP Parameters page.

Figure 426: FTP Parameters Page

Phn 3963 013v000

Page 516
Chapter 10: Access Management and Security Downloading and Installing an RSA Key

4 The File Transfer Protocol field is read-only and displays SFTP. RSA key files cannot be downloaded to an PTP
820 device using FTP.
5 In the Username field, enter the user name you configured in the SFTP server.
6 In the Password field, enter the password you configured in the SFTP server. If you did not configure a
password for your SFTP user, simply leave this field blank.
7 In the Path field, enter the directory path from which you are downloading the file. Enter the path relative to
the SFTP user's home directory, not the absolute path. If the location is the home directory, it should be left
empty. If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is
"C:\", this parameter can be left empty or populated with "//"..
8 If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
SFTP server in the Server IPv4 address field.
9 If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
SFTP server in the Server IPv6 address field.
10 Click Apply to save your settings.
11 In the RSA Key Download & Install page, click Download. The download begins. You can view the status of the
download in the Download Status field. See Table 75.
12 Once the download has been completed, click Install to install the RSA key file. You can view the status of the
installation in the Install Status field. See Table 75.

Note
To discontinue the download process, click Abort.

Table 77: RSA File Download & Install Status Parameters

Parameter Definition
Download The status of any pending RSA file download. Possible values are:
Status • Ready – The default value, which appears when no download is in progress.
• In Progress – The download is in progress.
• Aborted – The download was aborted by user command.
If an error occurs during the download, an appropriate error message is
displayed in this field.
When the download is complete, one of the following status indications
appears:
• Success – File downloaded and verified successfully.
• Failed – File download failed or verification failed.
When the system is reset, the Download Status returns to Ready.

Download Displays the progress of the current download.

Progress

Install Status The status of any pending installation. Possible values are:
• Success
• Failed

Phn 3963 013v000

Page 517
Chapter 10: Access Management and Security Blocking Telnet Access

Blocking Telnet Access

You can block telnet access to the unit. By default, telnet access is not blocked.
To block telnet access:
1 Select Platform > Security > Protocols Control. The Protocols Control page opens.

Figure 427 Protocols Control Page

2 In the Telnet Admin field, select Disable to block telnet access. By default, telnet access is enabled (Enable).
3 Click Apply.

Phn 3963 013v000

Page 518
Chapter 10: Access Management and Security Uploading the Security Log

Uploading the Security Log

The security log is an internal system file which records all changes performed to any security feature, as well as all
security related events.
When uploading the security log, the PTP 820 functions as an FTP or SFTP client. You must install FTP or SFTP
server software on the PC or laptop you are using to perform the import or export. For details, see Installing and
Configuring an FTP or SFTP Server.
To upload the security log:
1. Install and configure an FTP server on the PC or laptop you are using to perform the upload. See Installing and
Configuring an FTP or SFTP Server.
2. Select Platform > Security > General > Security Log Upload. The Security Log Upload page opens.

Figure 428 Security Log Upload Page

3. Click FTP Parameters to display the FTP Parameters page.

Phn 3963 013v000

Page 519
Chapter 10: Access Management and Security Uploading the Security Log

Figure 429 FTP Parameters Page (Security Log Upload)

4. In the Username field, enter the user name you configured in the FTP server.
5. In the Password field, enter the password you configured in the FTP server. If you did not configure a
password for your FTP user, simply leave this field blank.
6. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
FTP server in the Server IPV4 address field. See Defining the IP Protocol Version for Initiating Communications.
7. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
FTP server in the Server IPv6 address field. See Defining the IP Protocol Version for Initiating Communications.
8. In the Path field, enter the directory path to which you are uploading the files. Enter the path relative to the
FTP user's home directory, not the absolute path. If the location is the home directory, it should be left
empty. If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is
"C:\", this parameter can be left empty or populated with "//".
9. In the File name field, enter the name you want to give to the exported security log.

Note
The directory path and fie name, together, cannot be more than:
If the IP address family is configured to be IPv4: 236 characters
If the IP address family is configured to be IPv6: 220 characters

10. Click Apply, then Close to save the FTP parameters and return to the Security Log Upload page.
11. Click Upload. The upload begins.
The File transfer operation status field displays the status of any pending security log upload. Possible values are:
o Ready – The default value, which appears when no file transfer is in progress.
o File-in-transfer – The upload operation is in progress.
o Success – The file has been successfully uploaded.
o Failure – The file was not successfully uploaded.
The Process percentage field displays the progress of any current security log upload operation.

Phn 3963 013v000

Page 520
Chapter 10: Access Management and Security Uploading the Configuration Log

Uploading the Configuration Log

The configuration log lists actions performed by users to configure the system. This file is mostly used for security,
to identify suspicious user actions. It can also be used for troubleshooting.
When uploading the configuration log, the PTP 820 functions as an FTP or SFTP client. You must install FTP or SFTP
server software on the PC or laptop you are using to perform the upload. For details, see Installing and Configuring
an FTP or SFTP Server.
To upload the configuration log:
1. Install and configure an FTP server on the PC or laptop you are using to perform the upload. See Installing and
Configuring an FTP or SFTP Server.
2. Select Platform > Security > General > Configuration Log Upload. The Configuration Log Upload page opens.

Figure 430 Configuration Log Upload Page

3. Click FTP Parameters to display the FTP Parameters page.

Phn 3963 013v000

Page 521
Chapter 10: Access Management and Security Uploading the Configuration Log

Figure 431 Configuration Log Upload Page

4. In the Username field, enter the user name you configured in the FTP server.
5. In the Password field, enter the password you configured in the FTP server. If you did not configure a
password for your FTP user, simply leave this field blank.
6. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
FTP server in the Server IPV4 address field. See Defining the IP Protocol Version for Initiating Communications.
7. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
FTP server in the Server IPv6 address field. See Defining the IP Protocol Version for Initiating Communications.
8. In the Path field, enter the directory path to which you are uploading the files. Enter the path relative to the
FTP user's home directory, not the absolute path. If the location is the home directory, it should be left empty.
If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is "C:\",
this parameter can be left empty or populated with "//".
9. In the File Name field, enter the name you want to give to the exported configuration log.

Note
The directory path and fie name, together, cannot be more than:
If the IP address family is configured to be IPv4: 236 characters
If the IP address family is configured to be IPv6: 220 characters

10. Click Apply, and Close to save the FTP parameters and return to the Configuration Log Upload page.
11. Click Upload. The upload begins.
The File transfer operation status field displays the status of any pending configuration log upload. Possible values
are:
o Ready – The default value, which appears when no file transfer is in progress.

Phn 3963 013v000

Page 522
Chapter 10: Access Management and Security Uploading the Configuration Log

o File-in-transfer – The upload operation is in progress.

o Success – The file has been successfully uploaded.
o Failure – The file was not successfully uploaded.
The File transfer progress field displays the progress of any current configuration log upload operation.

Phn 3963 013v000

Page 523
Chapter 11: Alarm Management and Troubleshooting Uploading the Configuration Log

Chapter 11: Alarm Management and

Troubleshooting
This section includes:
• Viewing Current Alarms
• Viewing Alarm Statistics
• Viewing and Saving the Event Log
• Editing Alarm Text and Severity and Disabling Alarms and Events
• Configuring Voltage Alarm Thresholds and Displaying Voltage PMs
• Uploading Unit Info
• Performing Diagnostics

Note
CW mode, used to transmit a single or dual frequency tones for debugging purposes, can be
configured using the CLI. See Working in CW Mode (Single or Dual Tone) (CLI).

You can configure a 30-second wait time after an alarm is cleared in the system before the alarm is
actually reported as being cleared. This prevents traps flooding the NMS in the event that some
external condition causes the alarm to be raised and cleared continuously. By default, the timeout
for trap generation is disabled. It can be enabled and disabled via CLI. See Configuring a Timeout for
Trap Generation (CLI).

Phn 3963 013v000

Page 524
Chapter 11: Alarm Management and Troubleshooting Viewing Current Alarms

Viewing Current Alarms

To display a list of current alarms in the unit:

1. Select Faults > Current Alarms. The Current Alarms page opens. The Current Alarms page displays current alarms
in the unit. Each row in the Current Alarms table describes an alarm and provides basic information about the
alarm. For a description of the information provided in the Current Alarms page, see Table 64.

Figure 432 Current Alarms Page

2. To view more detailed information about an alarm, click + at the beginning of the row or select the alarm and
click View.
Figure 433 Current Alarms - View Page

Phn 3963 013v000

Page 525
Chapter 11: Alarm Management and Troubleshooting Viewing Current Alarms

Table 78 Alarm Information

Parameter Definition

Sequence Number (#) A unique sequence number assigned to the alarm by the system.

Time The date and time the alarm was triggered.

Severity The severity of the alarm. In the Current Alarms table, the severity is
indicated by a symbol. You can display a textual description of the
severity by holding the cursor over the symbol.
Note: You can edit the severity of alarm types in the Alarm
Configuration page. See Editing Alarm Text and Severity.

Description A system-defined description of the alarm.

User Text Additional text that has been added to the system-defined description of
the alarm by users.
Note: You can add user text to alarms in the Alarm Configuration page.
See Editing Alarm Text and Severity.

Origin The module that generated the alarm.

Probable Cause This field only appears in the Current Alarms - View page. One or more
possible causes of the alarm, to be used for troubleshooting.

Corrective Actions This field only appears in the Current Alarms - View page. One or more
possible corrective actions to be taken in troubleshooting the alarm.

Alarm ID A unique ID that identifies the alarm type.

Phn 3963 013v000

Page 526
Chapter 11: Alarm Management and Troubleshooting Viewing Alarm Statistics

Viewing Alarm Statistics

To display a summary of alarms per module and per interface:

1. Select Faults > Alarm Statistics. The Alarm Statistics page opens.
Figure 434 Alarm Statistics Page

The Alarm Statistics page displays the number of current alarms per severity level for each module, interface, and
virtual interface (such as Multi-Carrier ABC groups) in the unit. Only modules and interfaces for which one or more
alarms are currently raised are listed in the Alarm Statistics page.

Phn 3963 013v000

Page 527
Chapter 11: Alarm Management and Troubleshooting Viewing and Saving the Event Log

Viewing and Saving the Event Log

The Event Log displays a list of current and historical events and information about each event.
To display the Event Log:
1. Select Faults > Event Log. The Event Log opens. For a description of the information provided in the Event Log,
see Table 65 Event Log Information.
Figure 435 Event Log

2. To export the Event Log to a CSV file, click Export to CSV in the lower right corner of the Event Log page.

Table 79 Event Log Information

Parameter Definition

Time The date and time the event was triggered.

Sequence Number (#) A unique sequence number assigned to the event by the system.

Severity The severity of the event. In the Event Log table, the severity is indicated
by a symbol. You can display a textual description of the severity by
holding the cursor over the symbol.
Note: You can edit the severity of event types in the Alarm
Configuration page. See Editing Alarm Text and Severity.

State Indicates whether the event is currently raised or has been cleared.

Description A system-defined description of the event.

User Text Additional text that has been added to the system-defined description of
the event by users.
Note: You can add user text to events in the Alarm Configuration page.
See Editing Alarm Text and Severity.

Origin The module that generated the event.

Phn 3963 013v000

Page 528
Chapter 11: Alarm Management and Troubleshooting Viewing and Saving the Event Log

Phn 3963 013v000

Page 529
Chapter 11: Alarm Management and Troubleshooting Editing Alarm Text and Severity and Disabiling Alarms and
Events

Editing Alarm Text and Severity and Disabiling

Alarms and Events

You can view a list of alarm types, edit the severity level assigned to individual alarm types, disable alarms and events
and add additional descriptive text to individual alarm types.
This section includes:
• Displaying Alarm Information
• Viewing the Probable Cause and Corrective Actions for an Alarm Type
• Editing an Alarm Type
• Setting Alarms to their Default Values

Displaying Alarm Information

To view the list of alarms defined in the system:
1. Select Faults > Alarm Configuration. The Alarm Configuration page opens. For a description of the information
provided in the Alarm Configuration page, see Table 66 Alarm Configuration Page Parameters.

Figure 436 Alarm Configuration Page

Table 80 Alarm Configuration Page Parameters

Parameter Definition

Sequence Number (#) A unique sequence number assigned to the row by the system.

Alarm ID A unique ID that identifies the alarm type.

Phn 3963 013v000

Page 530
Chapter 11: Alarm Management and Troubleshooting Editing Alarm Text and Severity and Disabiling Alarms and
Events

Parameter Definition

Severity The severity assigned to the alarm type. You can edit the severity in the
Alarm Configuration – Edit page. See Editing an Alarm Type.

Description A system-defined description of the alarm.

Additional Text Additional text that has been added to the system-defined description of
the alarm by users. You can edit the text in the Alarm Configuration – Edit
page. See Editing an Alarm Type.

Service Affecting Indicates whether the alarm is considered by the system to be service-
affecting (on) or not (off).

Alarm Admin Indicates whether the alarm is enabled or disabled. By default, all alarms
are enabled. See Editing an Alarm Type and Disabling Alarms and Events.

Viewing the Probable Cause and Corrective Actions for an

Alarm Type
Most alarm types include a system-defined probable cause and suggested corrective actions. To view an alarm type's
probable cause and corrective actions, click + on the left side of the alarm type's row in the Alarm Configuration page.
The Probable Cause and Corrective Actions appear underneath the alarm type's row, as shown below. If there is no +,
that means no Probable Cause and Corrective Actions are defined for the alarm type.

Figure 437 Alarm Configuration Page – Expanded

Editing an Alarm Type and Disabiling Alarms and Events

You can change the severity of an alarm type, and add additional text to the alarm type’s description.
You can also choose to disable selected alarms and events. Any alarm or event can be disabled, so that no indication
of the alarm is displayed, and no traps are sent for the alarm.
If you disable an alarm that is currently raised, the alarm is treated as if it has been cleared. If an alarm that has been
disabled is enabled while it is in a raised state, the alarm is treated as if it has just been raised when it is enabled.
If a timeout for trap generation is configured, and a disabled alarm is enabled while the alarm is raised, the timeout
count begins to run when the alarm is enabled. If an alarm is disabled while raised, the timeout count begins to run
upon disabling the alarm, and an alarm cleared trap is sent when the timeout expires.

Phn 3963 013v000

Page 531
Chapter 11: Alarm Management and Troubleshooting Editing Alarm Text and Severity and Disabiling Alarms and
Events

To change the severity of an alarm type and add additional text to the alarm type's description:
1. Select the alarm type in the Alarm Configuration page (Figure 327).
2. Click Edit. The Alarm Configuration - Edit page opens.

Phn 3963 013v000

Page 532
Chapter 11: Alarm Management and Troubleshooting Editing Alarm Text and Severity and Disabiling Alarms and
Events

Figure 438 Alarm Configuration - Edit Page

3. Modify the Severity and/or Additional Text fields.

4. To disable an alarm or event, select Disable in the Alarm Admin field. To re- enable an alarm or event, select
Enable in the Alarm Admin field.
5. Click Apply, then Close.

Setting Alarms to their Default Values

To set all alarms to their default severity levels and text descriptions, click Set All to Default in the Alarm
Configuration page (Figure 327).

Phn 3963 013v000

Page 533
Chapter 11: Alarm Management and Troubleshooting Configuring Voltage Alarm Thresholds and Displaying Voltage
PMs

Configuring Voltage Alarm Thresholds and

Displaying Voltage PMs

You can configure undervoltage and overvoltage alarm thresholds and display voltage PMs.
The default thresholds for PTP 820C are:
• Undervoltage Raise Threshold: 32V
• Undervoltage Clear Threshold: 34V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
The default thresholds for the other PTP 820 all-outdoor products are:
• Undervoltage Raise Threshold: 36V
• Undervoltage Clear Threshold: 38V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
These thresholds determine when the following alarms are raised and cleared:
• Alarm #32000: Under voltage
• Alarm #32001: Over voltage
To configure voltage alarm thresholds:
1 Select Faults > Voltage Alarm Configuration. The Voltage Alarm Configuration page opens.
Note: You can also open the Voltage Alarm Configuration page by selecting Platform > PM &
Statistics > Voltage and clicking Thresholds.

Phn 3963 013v000

Page 534
Chapter 11: Alarm Management and Troubleshooting Configuring Voltage Alarm Thresholds and Displaying Voltage
PMs

Figure 439 Voltage Alarm Configuration Page

2 Click Edit. The Voltage Alarm Configuration – Edit page opens.

Figure 440 Voltage Alarm Configuration – Edit Page

3 Select the thresholds you want in the Undervoltage clear threshold (V), Undervoltage raise threshold (V),
Overvoltage clear threshold (V), and Overvoltage raise threshold (V) fields. The configurable values for these
thresholds are 0-100V.
4 Click Apply.

Phn 3963 013v000

Page 535
Chapter 11: Alarm Management and Troubleshooting Configuring Voltage Alarm Thresholds and Displaying Voltage
PMs

To display voltage PMs:

1 Select Platform > PM & Statistics > Voltage. The Voltage PM Report page opens.

Figure 441 Voltage PM Report Page

2 In the Interval Type field:
• To display reports for the past 24 hours, in 15 minute intervals, select 15 minutes.
• To display reports for the past month, in daily intervals, select 24 hours.
Note: The Interface field displays PDC #1.

Table 81 Voltage PMs

Parameter Definition
Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.
Minimum Voltage (V) The lowest voltage during the measured period.
Maximum Voltage (V) The highest voltage during the measured period.
Undervoltage Seconds The number of seconds the unit was in an undervoltage state during the
measured period.
Overvoltage Seconds The number of seconds the unit was in an overvoltage state during the
measured period.
Integrity Indicates whether the values received at the time and date of the
measured interval are reliable. An x in the column indicates that the values
are not reliable due to a possible power surge or power failure that
occurred during the interval.

Phn 3963 013v000

Page 536
Chapter 11: Alarm Management and Troubleshooting Uploading Unit Info

Uploading Unit Info

You can generate a Unit Information file, which includes technical data about the unit. This file can be uploaded and
forwarded to customer support, at their request, to help in analyzing issues that may occur.
You can upload the Unit Information file using HTTP, HTTPS, FTP, or SFTP.

Note
For troubleshooting, it is important that an updated configuration file be included in Unit Info files
that are sent to customer support. To ensure that an up-to-date configuration file is included, it is
recommended to back up the unit’s configuration before generating the Unit Info file.
For PTP 820C, PTP 820C-HP, and PTP 820S units with Unit Redundancy, you must use FTP or SFTP to
upload the User Information file.

Uploading a Unit Info File Via HTTP or HTTPS

To uploading a User Information file using HTTP or HTTPS:
1. Platform > Management > Unit Info. The Unit Info page opens.Select HTTP.

Figure 442: Unit Info Page – HTTP/HTTPS Upload

2. Select HTTP.
3. Click Create to create the Unit Information file. The following fields display the status of the file
creation process:
◦ File Creation Status – Displays the file creation status. You must wait until the
status is Success to upload the file. Possible values are:

Phn 3963 013v000

Page 537
Chapter 11: Alarm Management and Troubleshooting Uploading Unit Info

◦ Ready – The default value, which appears when no file is being

created.
◦ Generating File – The file is being generated.
◦ Success – The file has been successfully created. You may now
upload the file.
◦ Failure – The file was not successfully created.
◦ File Creation Progress – Displays the progress of the current Unit
Information file creation operation.
4. Click Export. The upload begins. The following fields display the status of the upload process:
◦ File Transfer Status – Displays the status of any pending Unit Information file
upload. Possible values are:
◦ Ready – The default value, which appears when no file transfer is in
progress.
◦ File-in-transfer – The upload operation is in progress.
◦ Success – The file has been successfully uploaded.
◦ Failure – The file was not successfully uploaded.
If you try to export the file before it has been created, the following error message
appears: Error #3-Invalid set value.
If this occurs, wait about two minutes then click Export again.
◦ File Creation Progress – Displays the progress of the current Unit
Information file upload operation.

Uploading a Unit Info File Via FTP or SFTP

When uploading a Unit Information file via FTP or SFTP, the PTP 820 functions as an FTP or SFTP client. You must
install FTP or SFTP server software on the PC or laptop you are using to perform the upload. For details, see
Installing and Configuring an FTP or SFTP Server.
To generate and upload a Unit Information file:
1. Install and configure an FTP server on the PC or laptop you are using to perform the upload. See Installing and
Configuring an FTP or SFTP Server.
2. Select Platform > Management > Unit Info. The Unit Info page opens.

Figure 443 Unit Info Page

Phn 3963 013v000

Page 538
Chapter 11: Alarm Management and Troubleshooting Uploading Unit Info

3. Select FTP
4. Set the FTP parameters:
◦ Click FTP Parameters. The FTP Parameters page opens.

Figure 444: FTP Parameters Page

Phn 3963 013v000

Page 539
Chapter 11: Alarm Management and Troubleshooting Uploading Unit Info

5. In the File transfer protocol field, select the file transfer protocol you want to use (FTP or SFTP).
6. In the Username in server field, enter the user name you configured in the FTP server.
7. In the Password in server field, enter the password you configured in the FTP server. If you did not configure a
password for your FTP user, simply leave this field blank.
8. If the IP address family is configured to be IPv4, enter the IPv4 address of the PC or laptop you are using as the
FTP server in the Server IPv4 address field. See Defining the IP Protocol Version for Initiating Communications.
9. If the IP address family is configured to be IPv6, enter the IPv6 address of the PC or laptop you are using as the
FTP server in the IPv6 Server Address field. See Defining the IP Protocol Version for Initiating Communications.
10. In the Path field, enter the directory path to which you are uploading the file. Enter the path relative to the
FTP user's home directory, not the absolute path. If the location is the home directory, it should be left empty.
If the location is a sub-folder under the home directory, specify the folder name. If the shared folder is "C:\",
this parameter can be left empty or populated with "//".
11. In the File Name field, enter the name you want to give to the exported Unit Information file.
12. Click Apply to save your settings.
13. Click Create to create the Unit Information file. The following fields display the status of the file creation
process:
o Unit Info File creation status – Displays the file creation status. You must wait until
the status is Success to upload the file. Possible values are:
o Ready – The default value, which appears when no file is being created.
o Generating File – The file is being generated.
o Success – The file has been successfully created. You may now upload the file.
o Failure – The file was not successfully created.
o Unit Info File creation progress – Displays the progress of the current Unit
Information file creation operation.
14. Click Export. The upload begins. The following fields display the status of the upload process:
o File File transfer status – Displays the status of any pending Unit Information file
upload. Possible values are:
o Ready – The default value, which appears when no file transfer is in progress.
o File-in-transfer – The upload operation is in progress.
o Success – The file has been successfully uploaded.
o Failure – The file was not successfully uploaded.
If you try to export the file before it has been created, the following error message appears: Error #3-Invalid
set value.
If this occurs, wait about two minutes then click Export again.
o File transfer progress – Displays the progress of the current Unit Information file
upload operation.

Phn 3963 013v000

Page 540
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Performing Diagnostics

This section includes:

• Performing Radio Loopback
• Performing Ethernet Loopback
• Configuring Service OAM (SOAM) Fault Management (FM)

Performing Radio Loopback

Note
To perform radio loopback, the radio must be set to its maximum TX power.

To perform loopback on a radio:

1. Select Radio > Diagnostics > Loopback. The Radio Loopbacks page opens.
Figure 445 Radio Loopbacks Page

2. Select the slot on which you want to perform loopback and click Edit. The Radio Loopbacks – Edit page opens.

Phn 3963 013v000

Page 541
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Note
You cannot perform loopback directly on a Multi-Carrier ABC group. To perform traffic-level
diagnostics on a Multi-Carrier ABC group, the loopback must be activated for all members of the
group. Radio-level diagnostics can still be performed on individual members of the group.

Figure 446 Radio Loopbacks – Edit Page

3. In the Loopback timeout (minutes) field, enter the timeout, in minutes, for automatic termination of the
loopback (0-1440). A value of 0 indicates that there is no timeout.
4. In the RF loopback field, select On.
5. Click Apply.

Performing Ethernet Loopback

Ethernet loopbacks can be performed on any logical Ethernet interface except a LAG. When Ethernet loopback is
enabled on an interface, the system loops back all packets ingressing the interface. This enables loopbacks to be
performed over the link from other points in the network.
To perform Ethernet loopback:
1. Select Ethernet > Interfaces > Logical Interfaces. The Logical Interfaces page opens (Figure 214).
2. Select an interface in the Ethernet Logical Port Configuration table and click Loopback. The Logical Interfaces –
Loopback page opens.

Phn 3963 013v000

Page 542
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 447 Logical Interfaces – Loopback Page

3. In the Ethernet loopback admin field, select Enable to enable Ethernet loopback on the logical interface, or
Disable to disable Ethernet loopback on the logical interface.
4. In the Ethernet loopback duration (sec) field, enter the loopback duration time (in seconds).
5. In the Swap MAC address admin field, select whether to swap DA and SA MAC addresses during the loopback.
Swapping addresses prevents Ethernet loops from occurring. It is recommended to enable MAC address
swapping if LLDP is enabled.
6. Click Apply to initiate the loopback.

Configuring Service OAM (SOAM) Fault Management (FM)

This section includes:
• SOAM Overview
• Configuring MDs
• Configuring MA/MEGs
• Configuring MEPs
• Displaying Remote MEPs
• Displaying Last Invalid CCMS

SOAM Overview
The Y.1731 standards and the MEF-30 specifications define Service OAM (SOAM). SOAM is concerned with
detecting, isolating, and reporting connectivity faults spanning networks comprising multiple LANs, including LANs
other than IEEE 802.3 media.

Phn 3963 013v000

Page 543
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Y.1731 Ethernet FM (Fault Management) consists of three protocols that operate together to aid in fault
management:
• Continuity check
• Link trace
• Loopback

Note
Link trace is planned for future release.

PTP 820 utilizes these protocols to maintain smooth system operation and non-stop data flow.
The following are the basic building blocks of FM:
• MD (Maintenance Domain) – An MD defines the management space on a network, typically owned and
operated by a single entity, for which connectivity faults are managed via SOAM.
• MA/MEG (Maintenance Association/Maintenance Entity Group) – An MA/MEG contains a set of MEPs or
MIPs.
• MEP (MEG End Points) – Each MEP is located on a service point of an Ethernet service at the boundary of the
MEG. By exchanging CCMs (ContinuityCheck Messages), local and remote MEPs have the ability to detect the
network status, discover the MAC address of the remote unit/port where the peer MEP is defined, and
identify network failures.

Note
MIP – (MEG Intermediate Points) Similar to MEPs, but located inside the MEG and can only respond
to, not initiate, CMM message.

• CCM (Continuity Check Message) – MEPs in the network exchange CCMs with their peers at defined intervals.
This enables each MEP to detect loss of connectivity or failure in the remote MEP.

Configuring MDs
In the current release, you can define one MD, with an MD Format of None.
To add an MD:
1. Select Ethernet > Protocols > SOAM > MD. The SOAM MD page opens.

Phn 3963 013v000

Page 544
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 448 SOAM MD Page

2. Click Add. The SOAM MD – Add page opens.

Figure 449 SOAM MD Page

3. In the MD Name field, enter an identifier for the MD (up to 43 alphanumeric characters). The MD Name
should be unique over the domain.
4. In the MD Format field, select None.

Note
Support for MDs with the MD format Character String is planned for future release. In this release,
the software enables you to configure such MDs, but they have no function.

Phn 3963 013v000

Page 545
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

5. In the MD Level field, select the maintenance level of the MD (1-7). The maintenance level ensures that the
CFM frames for each domain do not interfere with each other. Where domains are nested, the encompassing
domain must have a higher level than the domain it encloses. The maintenance level is carried in all CFM
frames that relate to that domain. The MD Level must be the same on both sides of the link.

Note
In the current release, the MD level is not relevant to the SOAM functionality.

6. Click Apply, then Close.

The MHF (MIP) Creation field displays the types of MHF format included in the CCMs sent in this MD (in the
current release, this is MHF none and MHF default).
The Sender TLV Content field displays the types of TLVs included in the CCMs sent in this MD (in the current
release, this is only Send ID Chassis).

Configuring MA/MEGs
You can configure up to 1280 MEGs per network element: MEGs are classified as Fast MEGs or Slow MEGs
according to the CCM interval
• Fast MEGs have a CCM interval of 1 second.
• Slow MEGs have a CCM interval of 10 seconds, 1 minute, or 10 minutes.
You can configure up to 32 MEP pairs per network element.

To add a MEG:
1. Select Ethernet > Protocols > SOAM > MA/MEG. The SOAM MA/MEG page opens.

Figure 450 SOAM MA/MEG Page

2. Click Add MEG. The SOAM MA/MEG – Add page opens.

Phn 3963 013v000

Page 546
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 451 SOAM MA/MEG – Add Page

3. Configure the fields described in Table 68.

4. Click Apply, then Close.
Table 69 describes the status (read-only) fields in the SOAM MA/MEG Component table.

Table 82 SOAM MA/MEG Configuration Parameters

Parameter Definition

MD (ID, Name) Select the MD to which you are assigning the MEP.

MA/MEG short name Enter a name for the MEG (up to 44 alphanumeric characters).

Phn 3963 013v000

Page 547
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Parameter Definition

MEG Level Select a MEG level (0-7). The MEG level must be the same for MEGs on
both sides of the link. Higher levels take priority over lower levels.
If MEGs are nested, the OAM flow of each MEG must be clearly
identifiable and separable from the OAM flows of the other MEGs. In
cases where the OAM flows are not distinguishable by the Ethernet layer
encapsulation itself, the MEG level in the OAM frame distinguishes
between the OAM flows of nested MEGs.
Eight MEG levels are available to accommodate different network
deployment scenarios. When customer, provider, and operator data path
flows are not distinguishable based on means of the Ethernet layer
encapsulations, the eight MEG levels can be shared among them to
distinguish between OAM frames belonging to nested MEGs of
customers, providers and operators. The default MEG level assignment
among customer, provider, and operator roles is:
The customer role is assigned MEG levels 6 and 7.
The provider role is assigned MEG levels 3 through 5.
The operator role is assigned MEG levels: 0 through 2.
The default MEG level assignment can be changed via a mutual
agreement among customer, provider, and/or operator roles.
The number of MEG levels used depends on the number of nested MEs
for which the OAM flows are not distinguishable based on the Ethernet
layer encapsulation.

CCM Interval The interval at which CCM messages are sent within the MEG. Options
are:
1 second (default)
10 seconds
1 minute
10 minutes
It takes a MEP 3.5 times the CCM interval to determine a change in the
status of its peer MEP. For example, if the CCM interval is 1 second, a
MEP will detect failure of the peer 3.5 seconds after it receives the first
CCM failure message. If the CCM interval is 10 minutes, the MEP will
detect failure of the peer 35 minutes after it receives the first CCM failure
message.

Service ID Select an Ethernet service to which the MEG belongs. You must define
the service and add service points before you configure the MEG.

Table 83 SOAM MA/MEG Status Parameters

Phn 3963 013v000

Page 548
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Parameter Definition

MIP Creation Determines whether MIPs are created on the MEG. Options are:
• MHF none – No MIPs are created.
• MHF default – MIPs are created automatically on any service point in
the MEG’s Ethernet service.
• MHF explicit – MIPs are created on the service points of the MEG
when a lower-level MEP exists on the service point. This option is
usually used when the operator’s domain is encompassed by another
domain.
MHF defer – No MIPs are created. Not used in the current release.

MA/MEG ID Automatically generated by the system. You can change this value.

MA/MEG Name Format Reserved for future use. In the current release, this is Char String only.

Tx Sender ID TLV content Reserved for future use. Sender ID TLV is not transmitted.

Port Status TLV TX Reserved for future use. No Port Status TLV is transmitted in the CCM
frame.

Interface Status TLV TX Reserved for future use. No Interface Status TLV is transmitted in the
CCM frame, indicating the operational status of the interface on which
the transmitting MEP is configured (Up or Down).

MEP List Lists all local and remote MEPs that have been defined for the MEG.

Configuring MEPs
Each MEP is attached to a service point in an Ethernet service. The service and service point must be configured
before you configure the MEP. See Configuring Ethernet Service(s).
Each MEP inherits the same VLAN, C-VLAN, or S-VLAN configuration as the service point on which it resides. See
Configuring Service Points (CLI).Configuring Service Points
In order to set the VLAN used by CCM/LBM/LTM if the service point is defined ambiguously (for example PIPE,
Bundle-C, Bundle-S, or All-to-One), the service point’s C-VLAN/S-VLAN parameter should not be set to N.A.

To configure a MEP, you must:

1. Add MEPs to the relevant MA/MEG. In this stage, you add both local and remote MEPs. The only thing you
define at this point is the MEP ID. See 1. Adding Local and Remote MEPs.
2. Configure the local MEPs. At this point, you determine which MEPs are local MEPs. The system automatically
defines the other MEPs you configured in the previous step as remote MEPs. See 2. Configuring the Local
MEPs.
3. Enable the Local MEPs. See 3. Enabling Local MEPs.

Phn 3963 013v000

Page 549
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

1. Adding Local and Remote MEPs

To add a MEP to the MA/MEG:
1. In the SOAM MA/MEG page, select a MA/MEG and click MEP List. The MEP List page opens.

Figure 452 MEP List Page

2. Click Add. The Add MEP page opens.

Phn 3963 013v000

Page 550
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 453 Add MEP Page

3. In the MEP ID field, enter a MEP ID (1-8191).

4. Click Apply, then Close.

2. Configuring the Local MEPs

Once you have added local and remote MEPs, you must define the MEPs and determine which are the local MEPs:
1. Select Ethernet > Protocols > SOAM > MEP. The SOAM MEP page opens. Table 70 lists and describes the
parameters displayed in the SOAM MEP page.

Figure 454 SOAM MEP Page

Note
To display MEPs belonging to a specific MEG, select the MEG in the Filter by MA/MEG field near the
top of the SOAM MEP page. To display all MEPs configured for the unit, select All.

2. Click Add. Page 1 of the Add SOAM MEP wizard opens.

Figure 455 Add SOAM MEP Wizard – Page 1

Phn 3963 013v000

Page 551
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

3. In the MEG Name field, select an MA/MEG.

4. Click Next. Page 2 of the Add SOAM MEP wizard opens.

Figure 456 Add SOAM MEP Wizard – Page 2

5. In the Direction field, select Up or Down.

6. In the MEP ID field, select a MEP ID from the list of MEPs you have added to the selected MEG.
7. In the Service Point field, select the service point on which you want to place the MEP.
8. Click Finish. The Add SOAM MEP wizard displays the parameters you have selected.

Phn 3963 013v000

Page 552
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 457 Add SOAM MEP Wizard –Summary Page

9. Verify that you want to submit the displayed parameters and click Submit.

Table 84 SOAM MEP Parameters

Parameter Definition

MD (ID, Name) The MD ID and name are automatically generated by the system.

MA/MEG (ID, Name) The MA/MEG ID and name are automatically generated by the system.

MEP ID The MEP ID.

Interface Location The interface on which the service point associated with the MEP is
located.

SP ID The service point ID.

MEP Direction Up or Down

MEP Fault Notification The initial Indicates the status of the defect SOAM state machine.
State Possible values are:
• Fng Reset – Initial state.
• Fng Defect – Transient state when a defect is detected.
• Fng Defect Reported – The defect state is steady (stable).
• Fng Defect Clearing – Transient state when a defect is in the process
of being cleared.
Fng Defect Cleared – The defect has been cleared (Transient state).

Phn 3963 013v000

Page 553
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Parameter Definition

Connectivity Status Indicates whether a MEP can exchange PDU (CCM, Loopback, LTR) with its
remote MEP. A MEP with some defect or an inactive MEP cannot
exchange PDUs.
Possible values are:
• inactive – At least one of the remote MEPs is enabled (True).in
rMEPFailed status (not discovered).
• active – All remote MEPs are discovered correctly and have an
rMEPOk status.

MEP Active Indicates whether the MEP is enabled (True) or disabled (False).

MEP CCM TX Enable Indicates whether the MEP is sending CCMs (True/False).

CCM and LTM Priority The p-bit included in CCMs and/or LTM frames sent by this MEP (0 to 7).

MEP Defects Indicates if a defect has been detected by the MEP level.

RMEP List Once you have configured at least one local MEP, all other MEPs that you
have added but not configured as local MEPs are displayed here, and are
considered to be remote MEPs.

3. Enabling Local MEPs

Once you have added a MEP and defined it as a local MEP, you must enable the MEP.
To enable a MEP:
1. In the SOAM MEP page (Figure 343), select the MEP you want to enable.
2. Click Edit. The SOAM MEP - Edit page opens.

Phn 3963 013v000

Page 554
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 458 SOAM MEP - Edit Page

3. In the MEP Active field, select True.

4. In the MEP CCM TX Enable field, select True.
5. In the CCM and LTM Priority field, select the p-bit that will be included in CCMs sent by this MEP (0 to 7). It is
recommended to select 7.
6. Click Apply, then Close.

Displaying Remote MEPs

To display a list of remote MEPs (RMEPs) and their parameters:
1. Select Ethernet > Protocols > SOAM > MEP. The SOAM MEP page opens (Figure 343).

Phn 3963 013v000

Page 555
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

2. Select a MEP and click RMEP List. The SOAM MEP DB table is displayed.

Figure 459 SOAM MEP DB Table

Table 71 lists and describes the parameters displayed in the SOAM MEP DB table. To return to the SOAM MEP
page, click Back to MEP.

Note
To display these parameters in a separate window for a specific remote MEP, select the RMEP ID and
click View.

Table 85 SOAM MEP DB Table Parameters

Parameter Definition

RMEP ID The remote MEP ID.

RMEP Operational State The operational state of the remote MEP.

RMEP Last rx CCM MAC The MAC Address of the interface on which the remote MEP is located.
Address

RMEP Last CCM OK or Fail The timestamp marked by the remote MEP indicated the most recent
Timestamp CCM OK or failure it recorded. If none, this field indicates the amount of
time since SOAM was activated.

RMEP Last rx CCM RDI Displays the state of the RDI (Remote Defect Indicator) bit in the most
Indication recent CCM received by the remote MEP. If none, displays False.

RMEP Last rx CCM Port The Port Status TLV in the most recent CCM received from the remote
Status TLV MEP. Reserved for future use.

RMEP Last rx CCM Displays the operational status of the interface on which the remote MEP
Interface Status TLV has been defined.
• True – RDI was received in the last CCM.

RMEP Last rx CCM Chassis Displays the format of the remote. chassis (always the MAC address).
ID Format

Phn 3963 013v000

Page 556
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Parameter Definition

RMEP Last rx CCM Chassis Displays the MAC address of the remote chassis.
ID

Displaying Last Invalid CCMS

To display the entire frame of the last CCM error message and the last CCM cross-connect error message received
by a specific local MEP:
1. Select Ethernet > Protocols > SOAM > MEP. The SOAM MEP page opens (Figure 343).
2. Select a MEP and click Last Invalid CCMS. The MEP Last Invalid CCMS page opens.

Figure 460 MEP Last Invalid CCMS Page

The Last RX error CCM message field displays the frame of the last CCM that contains an error message received
by the MEP.
The Last RX Xcon fault message field displays the frame of the last CCM that contains a cross-connect error
message received by the MEP.

Note
A cross-connect error occurs when a CCM is received from a remote MEP that has not been defined
locally.

Phn 3963 013v000

Page 557
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Configuring MIPs with MHF Default

If you configure a MEG with the MHF default option, MIPS are created automatically on all service points of the
service to which the MEG is attached. These MIPs cannot be displayed in the Web EMS, but can be displayed via
CLI. See Displaying MEP and Remote MEP Attributes (CLI).
Creating MIPs is subject to the following limitations:
• Once you have created a MEG that contains MIPS, i.e., a MEG with the MHF default attribute, you cannot
create a MEG with the MHF none attribute on the same or higher level on the same Ethernet Service.
However, you can create MEGs with the MHF none attribute on the same service on lower levels then the
MEG with the MHF default attribute.
• MEPs cannot be attached to a MEG with the MHF default attribute.
• The Ethernet service and service points must already be defined before creating the MEG with the MHF
default attribute in order for MIPs to be created on the service points.
To configure MEGs with MIPs:
1 Create a MEG with the MHF none attribute on the intended Ethernet service. See Configuring MA/MEGs.
2 Select the MEG and click Edit. The SOAM MA/MEG – Edit page opens.
3 In the MIP Creation field, select MHF Default.
4 Click Apply, then Close.

Performing Loopback
To perform loopback on a MEP:
1 In the SOAM MEP page (Figure 343), select the MEP on which you want to perform the loopback.
2 Click Loopback. The SOAM MEP – Loopback page opens.

Phn 3963 013v000

Page 558
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

Figure 461 SOAM MEP Loopback Page

3 In the Loopback Destination area, select from the following options:

o MEP ID – If you select MEP ID, you must enter the MEP ID of the MEP on the interface to which you
want to perform the loopback in the Loopback Messages Destination MEP ID field. If you select MEP
ID, the loopback will only be activated if CCMs have already been received from the MEP. For this
reason, it is recommended to initiate loopback via MAC address.

Phn 3963 013v000

Page 559
Chapter 11: Alarm Management and Troubleshooting Performing Diagnostics

o MAC Address (default) – If you select MAC Address, you must enter the MAC address of the
interface to which you want to send the loopback in the Loopback Messages Destination MAC
Address. If you are not sure what the interface’s MAC address is, you can get it from the Interface
Manager by selecting Platform > Management > Interface Manager.
4 In the Loopback messages to be transmitted field, select the number of loopback messages to transmit (0
– 1024). If you select 0, loopback will not be performed.
5 In the Loopback Messages Interval field, select the interval (in seconds) between each loopback message
(0.1 – 60). You can select in increments of 1/10 second. However, the lowest possible interval is 1 second. If
you select a smaller interval, the actual interval will still be 1 second.
6 In the Loopback Messages Frame Size field, select the frame size for the loopback messages (64 – 1516).
Note that for tagged frames, the frame size will be slightly larger than the selected frame size.
7 In the Loopback Messages Priority field, select a value (0 – 7) for the priority bit for tagged frames.
8 In the Drop Enable field, choose the value of the DEI field for tagged loopback frames (True or False). The
default value is False.
9 In the Loopback Messages Data Pattern Type field, select the type of data pattern to be sent in an OAM
PDU Data TLV. Options are All Zeros and All Ones. The default value is All Zeros.
10 Click Apply to begin the loopback. The Loopback session state field displays the status of the loopback:
o SOAM Loopback Complete – The loopback has been successfully completed.
o SOAM Loopback Stopped – The loopback has been manually stopped.
o SOAM Loopback Failed – The loopback failed.
o SOAM Loopback Active – The loopback is currently active.
o SOAM Loopback Inactive – No loopback has been initiated.
The remote interface will answer and the loopback session will be completed if either of the following is true:
• A remote MEP has been defined on the destination interface.
• A MIP has been defined on the destination interface. See Configuring MIPs with MHF Default.

Note
To manually stop a loopback, you must use the CLI. Enter the following command in root view:
root> ethernet soam loopback stop meg-id <meg-id> mep-id <mep-id>

Phn 3963 013v000

Page 560
Chapter 12: Web EMS Utilities Performing Diagnostics

Chapter 12: Web EMS Utilities

This section includes:
• Restarting the HTTP Server
• Calculating an ifIndex
• Displaying, Searching, and Saving a list of MIB Entities

Phn 3963 013v000

Page 561
Chapter 12: Web EMS Utilities Calculating an ifIndex

Restarting the HTTP Server

To restart the unit’s HTTP server:

1 Select Utilities > Restart HTTP. The Restart HTTP page opens.

Figure 462 Restart HTTP Page

2 Click Restart. The system prompts you for confirmation.

3 Click OK. The HTTP server is restarted, and all HTTP sessions are ended. After a few seconds, the Web EMS
prompts you to log in again.

Calculating an ifIndex
The ifIndex calculator enables you to:
• Calculate the ifIndex for any object in the system.
• Determine the object represented by any valid ifIndex.
To use the ifIndex calculator:
1 Select Utilities > ifCalculator. The ifIndex Calculator page opens.

Phn 3963 013v000

Page 562
Chapter 12: Web EMS Utilities Calculating an ifIndex

Figure 463 ifIndex Calculator Page

• If you have an ifIndex and you want to determine which hardware item in the unit it represents, enter the
number in the ifIndex number field and click Calculate Index to name. A description of the object appears in
the Result field.
• To determine the ifIndex of a hardware item in the unit, such as an interface, card, or slot, select the object
type in the Functional Type field, select the Slot and Port (if relevant), and click Calculate Name to Index. The
object’s ifIndex appears in the Result field.

Phn 3963 013v000

Page 563
Chapter 12: Web EMS Utilities Displaying, Searching, and Saving a list of MIB Entities

Displaying, Searching, and Saving a list of MIB

Entities

To display a list of entities in the PTP 820 private MIB:

1 Select Utilities > ifCalculator. The ifIndex Calculator page opens.

Figure 464 MIB Reference Table Page

The MIB Reference Table is customized to the type of PTP 820 product you are using. There are three separate
versions of the MIB Reference Table:
• PTP 820G
• PTP 20C/S/C-HP/E

Note
Even though the MIB Reference Table is customized to these three product groups, some of the
entities listed in the Table may not be relevant to the particular unit you are using. This may occur
because of activation key restrictions, minor differences between product types, or simply because a
certain feature is not used in a particular configuration.

• To search for a text string, enter the string in the Search field and press <Enter>. Items that contain the string
are displayed in yellow. Searches are not case-sensitive.
• To save the MIB Reference Table as a .csv file, click Save to File.

Phn 3963 013v000

Page 564
Chapter 13: Getting Started (CLI) Displaying, Searching, and Saving a list of MIB Entities

Chapter 13: Getting Started (CLI)

This section includes:
• General (CLI)
• Establishing a Connection (CLI)
• Logging On (CLI)
• General CLI Commands
• Changing Your Password (CLI)
• Mate Management Access (IP Forwarding) (CLI)
• Mate Management Access (IP Forwarding) (CLI)
• Configuring In-Band Management (CLI)
• Changing the Management IP Address (CLI)
• Configuring the Activation Key (CLI)
• Setting the Time and Date (Optional) (CLI)
• Enabling the Interfaces (CLI)
• Configuring the Radio Parameters (CLI)
• Configuring the Radio (MRMC) Script(s) (CLI)
• Enabling ACM with Adaptive Transmit Power (CLI)
• Configuring the RSL Threshold Alarm (CLI)
• Operating in FIPS Mode (CLI)
• Configuring Grouping (Optional) (CLI)
• Creating Service(s) for Traffic (CLI)

Phn 3963 013v000

Page 565
Chapter 13: Getting Started (CLI) Establishing a Connection (CLI)

General (CLI)

Before connection over the radio hop is established, it is of high importance that you assign to the PTP 820 unit a
dedicated IP address, according to an IP plan for the total network. See Changing the Management IP Address (CLI).
By default, a new PTP 820 unit has the following IP settings:
• IP address: 192.168.1.1
• Subnet mask: 255.255.255.0

Caution
If the connection over the link is established with identical IP addresses, an IP address conflict will
occur and remote connection to the element on the other side of the link may be lost.

Establishing a Connection (CLI)

Connect the PTP 820 unit to a PC by means of a Twisted Pair cable. The cable is connected to the MGT port on
the PTP 820 and to the LAN port on the PC. Refer to the Installation Guide for the type of unit you are connecting for
cable connection instructions.

Note
The PTP 820 IP address, as well as the password, should be changed before the system is set in
operation. See Changing the Management IP Address (CLI) and Changing Your Password (CLI).

PC Setup (CLI)
To obtain contact between the PC and the PTP 820 unit, it is necessary to have an IP address on the PC within the
same subnet as the PTP 820 unit. The default PTP 820 IP address is 192.168.1.1. Set the PC address to e.g.
192.168.1.10 and subnet mask to 255.255.255.0. Note the initial settings before changing.

Note
The PTP 820 IP address, as well as the password, should be changed before operating the system is
set in operation. See Changing the Management IP Address (CLI) and Changing Your Password (CLI).

Phn 3963 013v000

Page 566
Chapter 13: Getting Started (CLI) Logging On (CLI)

Logging On (CLI)

Use a telnet connection to manage the PTP 820 via CLI. You can use any standard telnet client, such as PuTTy or ZOC
Terminal. Alternatively, you can simply use the telnet <ip address> command from the CMD window of your
PC or laptop.
The default IP address of the unit is 192.168.1.1. Establish a telnet connection to the unit using the default IP address.
When you have connected to the unit, a login prompt appears. For example:
login:
At the prompt, enter the default login user name: admin
A password prompt appears. Enter the default password: admin
The root prompt appears. For example:
login: admin

Password:

Wind River Linux glibc_cgl (cgl) 4.1 CE.1.0

Last login: Mon Apr 13 11:27:02 on console

Wind River Linux glibc_cgl (cgl) 4.1 CE.1.0

PTP 820C

root>

Phn 3963 013v000

Page 567
Chapter 13: Getting Started (CLI) General CLI Commands

General CLI Commands

To display all command levels available from your current level, press <TAB> twice. For example, if you press <TAB>
twice at the root level, the following is displayed:
root>

auto-state-propagation ethernet exit multi-carrier-abc

platform quit radio radio-groups

switch-back switch-to wait

Some of these are complete commands, such as quit and exit. Others constitute the first word or phrase for a
series of commands, such as ethernet and radio.
Similarly, if you enter the word “platform” and press <TAB> twice, the first word or phrase of every command that
follows platform is displayed:
root> platform

activation-key configuration if-manager management

security software status

sync unit-info unit-info-file

root> platform
To auto-complete a command, press <TAB> once.
Use the up and down arrow keys to navigate through recent commands.
Use the ? key to display a list of useful commands and their definitions.
At the prompt, or at any point in entering a command, enter the word help to display a list of available
commands. If you enter help at the prompt, a list of all commands is displayed. If you enter help after
entering part of a command, a list of commands that start with the portion
of the command you have already entered is displayed.
To scroll up and down a list, use the up and down arrow keys.
To end the list and return to the most recent prompt, press the letter q.
To ping another network device, enter one of the following commands:
root> ping ipv4-address <x.x.x.x> count <number of echo packets> packet-size
<packet-size>

root> ping ipv6-address <ipv6> count <number of echo packets> packet-size

<packet-size>
The optional count parameter determines how many packets are sent. This parameter can be an integer from 1 to
1000. The default value is 4.
The optional packet-size parameter determines the size of each packet, in bytes. This parameter can be an integer
from 64 to 1480. The default value is 64.
The ping command is available from all views (e.g., root, interface views, group views).

Phn 3963 013v000

Page 568
Chapter 13: Getting Started (CLI) Changing Your Password (CLI)

Changing Your Password (CLI)

It is recommended to change your default Admin password as soon as you have logged into the system.
In addition to the Admin password, there is an additional password protected user account, “root user”, which is
configured in the system. The root user password and instructions for changing this password are available from
Cambium Networks Customer Support. It is strongly recommended to change this password.
To change your password, enter the following command in root view:
root> platform security access-control password edit own-password
The system will prompt you to enter your existing password. The system will then prompt you to enter the new
password.
If Enforce Password Strength is activated, the password must meet the following criteria:
• Password length must be at least eight characters.
• Password must include characters of at least three of the following character types: lower case letters, upper
case letters, digits, and special characters. For purposes of meeting this requirement, upper case letters at the
beginning of the password and digits at the end of the password are not counted.
• A password cannot be repeated within five changes in password.
See Configuring the Password Security Parameters (CLI).

Phn 3963 013v000

Page 569
Chapter 13: Getting Started (CLI) Mate Management Access (IP Forwarding) (CLI)

Mate Management Access (IP Forwarding) (CLI)

Mate Management Access enables the use of in-band management for nodes that use two PTP 820C units (4x4
MIMO, 2+2 XPIC, and 4+0 Multi-Carrier ABC), where traffic comes from an external switch operating in LAG mode.
When Mate Management Access is enabled, the two units exchange incoming management packets, ensuring that all
management data is received by both units.

Note
Mate Management Access can be used regardless of whether the unit’s IP address is in IPv4 or IPv6
format.

Mate Management Access should only be enabled for nodes receiving traffic from a LAG, where in-band management
is to be used. If either of these conditions is not present, Mate Management Access should be disabled. By default,
the feature is disabled.
The following are the requirements for using Mate Management Access:
• The management ports of both PTP 820 units must be connected by a protection cable The cable can be ordered
in a variety of sizes, depending on the distance between the two PTP 820 units. See the following Table.
• To ensure proper convergence after failure events, Automatic State Propagation must be enabled on both units
at the local node and both units at the remote node. See Configuring Automatic State Propagation and Link Loss
Forwarding (CLI).
• Mate Management Access must be enabled on both units at the local node and both units at the remote node.
On each unit, Mate Management Access must be enabled before configuring in-band management.

Table 86 MIMO Protection Cables.

Marketing Model Description
PTP 820_MIMO_Prot_mng_cbl_1m PTP 820 MIMO or Prot management cable 1m
PTP 820_MIMO_Prot_ mng_cbl_5m PTP 820C MIMO or Prot management cable 5m
PTP 820_MIMO_Prot_ mng_cbl_10m PTP 820C MIMO or Prot management cable 10m
PTP 820_MIMO_Prot_ mng_cbl_20m PTP 820C MIMO or Prot management cable 20m
PTP 820_MIMO_Prot_ mng_cbl_30m PTP 820C MIMO or Prot management cable 30m

To enable Mate Management Access, enter the following command:

root> platform management mate-access admin enable

Note
When you enable or disable Mate Management Access, the unit is reset.

To disable Mate Management Access, enter the following command:

root> platform management mate-access admin disable
To display whether Mate Management Access is enabled, enter the following command:
root> platform management mate-access show

Phn 3963 013v000

Page 570
Chapter 13: Getting Started (CLI) Mate Management Access (IP Forwarding) (CLI)

Note
Mate Management Access can only be configured via CLI.

Upon recovery from a failure event, management may be lost for up to 40 seconds.

Phn 3963 013v000

Page 571
Chapter 13: Getting Started (CLI) Configuring In-Band Management (CLI)

Configuring In-Band Management (CLI)

You can configure in-band management in order to manage the unit remotely via its radio and/or Ethernet interfaces.

Note
Before configuring in-band management, it is recommended to review the configuration
recommendations for in-band management listed in Configuration tips.
To use in-band management for nodes that utilize two PTP 820C and PTP 820C-HP units (4x4 MIMO,
2x2 XPIC, and 4+0 Multi-Carrier ABC), you must first configure Mate Management Access (IP
Forwarding). See Mate Management Access (IP Forwarding) (CLI).

Each PTP 820 unit includes a pre-defined management service with Service ID 257. The management service is a
multipoint service that connects the two local management ports and the network element host CPU in a single
service. In order to enable in-band management, you must add at least one service point to the management service,
in the direction of the remote site or sites from which you want to access the unit for management. For instructions
on adding service points, see Configuring Service Points (CLI).

Note
In order to use in-band management, it must be supported on the external switch

Phn 3963 013v000

Page 572
Chapter 13: Getting Started (CLI) Changing the Management IP Address (CLI)

Changing the Management IP Address (CLI)

Related Topics:
• Defining the IP Protocol Version for Initiating Communications (CLI)
• Configuring the Remote Unit’s IP Address (CLI)
You can enter the unit's address in IPv4 format and/or in IPv6 format. The unit will receive communications whether
they were sent to its IPv4 address or its IPv6 address.
To set the unit's IP address in IPv4 format, enter the following command in root view to configure the IP address,
subnet mask, and default gateway:
root> platform management ip set ipv4-address <ipv4-address> subnet
<subnet> gateway <gateway> name <name> description <name>

Table 87 IP Address (IPv4) CLI Parameters

Parameter Input Type Permitted Values Description

ipv4-address Dotted decimal format. Any valid IPv4 address. The IP address for the
unit.

subnet Dotted decimal format. Any valid subnet mask. The subnet mask for the
unit.

gateway Dotted decimal format. Any valid IPv4 address. The default gateway for
the unit (optional).

name Text String. Enter a name (optional).

description Text String. Enter a description

(optional).

To set the unit's IP address in IPv6 format, enter the following command in root view to configure the IP address,
subnet mask, and default gateway:
root> platform management ip set ipv6-address <ipv6-address> prefix-length
<prefix-length> gateway <gateway>

Note
It is recommended not to configure addresses of type FE:80::/64 (Link Local addresses) because traps
are not sent for these addresses.

Phn 3963 013v000

Page 573
Chapter 13: Getting Started (CLI) Changing the Management IP Address (CLI)

Table 88 IP Address (IPv6) CLI Parameters

Parameter Input Type Permitted Values Description

ipv6-address Eight groups of four Any valid IPv6 address. The IP address for the
hexadecimal digits unit.
separated by colons.

prefix-length Number. 1-128 The prefix-length for the

unit.

gateway Eight groups of four Any valid IPv6 address. The default gateway for
hexadecimal digits the unit (optional).
separated by colons.

Examples
The command below sets the following parameters:
• IPv4 Address - 192.168.1.160
• Subnet Mask – 255.255.0.0
• Default Gateway – 192.168.1.100
root> platform management ip set ipv4-address 192.168.1.160 subnet
255.255.0.0 gateway 192.168.1.100
The command below sets the following parameters:
• IPv6 Address - FE80:0000:0000:0000:0202:B3FF:FE1E:8329
• Prefix length – 64
• Default Gateway - FE80:0000:0000:0000:0202:B3FF:FE1E:8329
root> platform management ip set ipv6-address
FE80:0000:0000:0000:0202:B3FF:FE1E:8329 prefix-length 64 gateway
FE80:0000:0000:0000:0202:B3FF:FE1E:8329

Phn 3963 013v000

Page 574
Chapter 13: Getting Started (CLI) Configuring the Activation Key (CLI)

Configuring the Activation Key (CLI)

This section includes:

• Activation Key Overview (CLI)
• Viewing the Activation Key Status Parameters (CLI)
• Entering the Activation Key (CLI)
• Activating a Demo Activation Key (CLI)
• Displaying a List of Activation-Key-Enabled Features (CLI)

Activation Key Overview (CLI)

PTP 820 offers a pay-as-you-grow concept in which future capacity growth and additional functionality can be
enabled with activation keys. Each device contains a single unified activation key cipher.
New PTP 820 units are delivered with a default activation key that enables you to manage and configure the unit.
Additional feature and capacity support requires you to enter an activation key. Contact your vendor to obtain your
activation key cipher.

Note
To obtain an activation key cipher, you may need to provide the unit’s serial number. See Displaying
Unit Inventory (CLI).

Each required feature and capacity should be purchased with an appropriate activation key. It is not permitted to
enable features that are not covered by a valid activation key. In the event that the activation-key-enabled capacity
and feature set is exceeded, an Activation Key Violation alarm occurs and the Web EMS displays a yellow background
and an activation key violation warning. 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.
In order to clear the alarm, you must configure the system to comply with the activation key that has been loaded in
the system. The system automatically checks the configuration to ensure that it complies with the activation-key-
enabled features and capacities. If no violation is detected, the alarm is cleared.
When entering sanction state, the system configuration remains unchanged, even after power cycles. However, the
alarms remain hidden until an appropriate activation key is entered or the features and capacities are re-configured
to be within the parameters of the current activation key.
A demo mode is available which enables all features for 60 days. When the demo mode expires, the most recent valid
activation key 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 that the demo mode is about to expire.

Viewing the Activation Key Status Parameters (CLI)

To display information about the currently installed activation key, enter the following command in root view:
root> platform activation-key show all

Entering the Activation Key (CLI)

To enter the activation key, enter the following command in root view.
Phn 3963 013v000
Page 575
Chapter 13: Getting Started (CLI) Configuring the Activation Key (CLI)

root> platform activation-key set key string <key string>

If the activation key is not legal (e.g., a typing mistake or an invalid serial number), an Activation Key Loading Failure
event is sent to the Event Log. When a legal activation key is entered, an Activation Key Loaded Successfully event is
sent to the Event Log.
To set the default activation key, enter the following command in root view:
activation-key set key string “Default Activation Key

Note
Make sure to enter the command using the exact syntax above, including the spaces and
quotation marks, or an error will be returned.

Activating a Demo Mode (CLI)

To activate the demo activation key, enter the following command in root view:
root> platform activation-key set demo admin enable
To display the current status of the demo activation key, enter the following command in root view:
root> platform activation-key show demo status

Activation Key Reclaim (CLI)

If it is necessary to deactivate an PTP 820 device, whether to return it for repairs or for any other reason, the device’s
activation key can be reclaimed for a credit that can be applied to activation keys for other devices.
Note:

Note
Activation key reclaim is only available for PTP 820 devices running release 9.2 or later.

A composite type activation key provides free activation keys when certain activation keys are purchased. For
example, if a customer purchases an activation key for one GB ethernet port, two FE ethernet port activation keys are
also provided. If the customer reclaims the activation key, the customer only gets credit for the original activation
key, not for the composite items.
Where the customer has purchased upgrade activation keys, credit is given for the full feature or capacity, not for
each individual upgrade. For example, if the customer purchased two capacity activation keys for 300M and later
purchased one upgrade activation key to 350M, credit is given as if the customer had purchased one activation key
for 350M and one activation key for 300M.
For instructions on how to reclaim an activation key, refer to the User Guide for the Activation Key Management
System, Rev A.15 or later, Chapter 7, Reclaiming an Activation Key. During the activation key reclaim procedure, you
will need to obtain a Validation Number from the PTP 820 unit. To display the Validation Number, enter the following
command in root view:
root> platform activation-key show all

Phn 3963 013v000

Page 576
Chapter 13: Getting Started (CLI) Configuring the Activation Key (CLI)

Displaying a List of Activation-Key-Enabled Features (CLI)

To display a list of features that your current activation key supports, and usage information about these features,
enter the following command in root view:
root> platform activation-key show usage all
To display a list of the radio capacities that your current activation key supports and their usage information, enter
the following command in root view:
root> platform activation-key show usage radio

Phn 3963 013v000

Page 577
Chapter 13: Getting Started (CLI) Setting the Time and Date (Optional) (CLI)

Setting the Time and Date (Optional) (CLI)

Related Topics:
• Configuring NTP (CLI)
PTP 820 uses the Universal Time Coordinated (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).
Every PTP 820 unit holds the UTC offset and daylight savings time information for the location of the unit. Each
management unit presenting the information uses its own UTC offset to present the information with the correct
time.

Note
If the unit is powered down, the time and date are saved for 96 hours (four days). If the unit remains
powered down for longer, the time and date may need to be reconfigured.

To set the UTC time, enter the following command in root view:
root> platform management time-services utc set date-and-time <date-and-
time>
To set the local time offset relative to UTC, enter the following command in root view:
root> platform management time-services utc set offset hours-offset <hours-
offset> minutes-offset <minutes-offset>
To display the local time configurations, enter the following command in root view:
root> platform management time-services show status

Table 89 Local Time Configuration CLI Parameters

Parameter Input Type Permitted Values Description

date-and- Number dd-mm-yyyy,hh:mm:ss Sets the UTC time.

time where:
dd = date
mm = month
yyyy= year
hh = hour
mm = minutes
ss = seconds

hours-offset Number -12 – 13 The required hours offset (positive or

negative) relative to GMT. This is used to
offset the clock relative to GMT, according to
the global meridian location.

minutes-offset Number 0 – 59 The required minutes relative to GMT. This is

used to offset the clock relative to GMT,
according to the global meridian location.

Phn 3963 013v000

Page 578
Chapter 13: Getting Started (CLI) Setting the Time and Date (Optional) (CLI)

Examples
The following command sets the GMT date and time to January 30, 2014, 3:07 pm and 58 seconds:
root> platform management time-services utc set date-and-time 30-01-
2014,15:07:58
The following command sets the GMT offset to 13 hours and 32 minutes:
root> platform management time-services utc set offset hours-offset 13
minutes-offset 32

Setting the Daylight Savings Time (CLI)

To set the daylight savings time parameters, enter the following command in root view:
root> platform management time-services daylight-savings-time set start-
date-month <start-date-month> start-date-day <start-date-day> end-date-
month <end-date-month> end-date-day <end-date-day> offset <offset>
Table 90: Daylight Savings Time CLI Parameters

Parameter Input Type Permitted Values Description

start-date- Number 1 – 12 The month when Daylight Savings Time

month begins.

start-date-day Number 1 – 31 The date in the month when Daylight Savings

Time begins.

end-date- Number 1 – 12 The month when Daylight Savings Time ends.

month

end-date-day Number 1 – 31 The date in the month when Daylight Savings

Time ends.

offset Number 0 – 23 The required offset, in hours, for Daylight

Savings Time. Only positive offset is
supported.

Examples
The following command configures daylight savings time as starting on May 30 and ending on October 1, with an
offset of 20 hours.
root> platform management time-services daylight-savings-time set start-
date-month 5 start-date-day 30 end-date-month 10 end-date-day 1 offset 20

Phn 3963 013v000

Page 579
Chapter 13: Getting Started (CLI) Enabling the Interfaces (CLI)

Enabling the Interfaces (CLI)

By default:
• Ethernet traffic interfaces are disabled and must be manually enabled.
• The Ethernet management interface is enabled.
• Radio interfaces are enabled.

Note
PTP 820S and PTP 820E unit has a single radio interface.

For PTP 820C 2E2SX hardware versions, P4 can be used as a traffic port (Eth 4). However, in 4x4 MIMO and 2+2 Space
Diversity configurations, P4 is used as an Extension port.
When one of these configurations is applied, the system automatically configures P4 to operate in MIMO mode and it
is no longer available for use as a traffic port (Eth 4). In these configurations, P4 must be used with an SFP+ module.
If you try to apply a 4x4 MIMO or 2+2 Space Diversity configuration while P4 is assigned one or more service points,
ASP or LLF instances, or a LAG group or Sync source is configured on P4, the configuration will fail and an error
message will be generated. Also, the admin status of the port must be set to down before applying the 4x4 MIMO or
2+2 Space Diversity configuration.
In PTP 820C 2E2SX models, P2 is a DisplayPort that uses a special splitter cable and gland to accommodate two RJ-45
cables (see Table 14).
• One end of the cable is labelled GbE1/PoE. This is used for the RJ-45 connection to Eth 1
(traffic/PoE).
• The other end of the cable is labelled GbE2. This is used for the RJ-45 connection to Eth 2
(traffic).

To enable or disable an interface, enter the following command in root view:

Phn 3963 013v000

Page 580
Chapter 13: Getting Started (CLI) Enabling the Interfaces (CLI)

root> platform if-manager set interface-type <interface-type> slot <slot>

port <port> admin <admin>
To display the status of all the interfaces in the unit, enter the following command in root view:
root> platform if-manager show interfaces

Table 91 Interface Configuration CLI Parameters

Parameter Input Type Permitted Values Description

interface-type Variable ethernet ethernet – an Ethernet

radio traffic interface.
radio – a radio interface.

slot Number Ethernet: 1 The slot on which the

Radio in PTP 820C or PTP 820S: 2 interface is located.

port Number GbE 1: 1 The specific interface you

GbE 2: 2 want to enable or disable.
GbE 3: 3Radio Carrier 1: 1
Radio Carrier 2 (PTP 820C and PTP
820C-HP only): 2

admin Variable up Enter up to enable the

down interface or down to disable
the interface.
Examples
The following command enables Ethernet port 2:
root> platform if-manager set interface-type ethernet slot 1 port 2 admin
up
The following command enables radio interface 1 in a PTP 820C or PTP 820S unit:
root> platform if-manager set interface-type radio slot 2 port 1 admin up
The following command disables Ethernet port 3:
root> platform if-manager set interface-type ethernet slot 1 port 3 admin
down

Phn 3963 013v000

Page 581
Chapter 13: Getting Started (CLI) Configuring the Radio Parameters (CLI)

Configuring the Radio Parameters (CLI)

In order to establish a radio link, you must:

• Enter radio view.
• Unmute the radio carrier.
• Configure the radio frequencies.

Note
Even if you are using the default frequencies, it is mandatory to actually configure the
frequencies.

• Configure the TX level.

• Set Mute Admin to Off.
• Verify that the radio is unmuted (the Mute Status should be Off).

Entering Radio View (CLI)

To view and configure radio parameters, you must first enter the radio’s view level in the CLI.
To enter a radio’s view level, enter the following command in root view:
root> radio slot <slot> port <port>

Table 92 Entering Radio View CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 2

port Number Radio Carrier 1: 1 The specific radio carrier you

Radio Carrier 2 (PTP 820C only): 2 want to access.

Examples
The following command enters radio view for radio carrier 1:
root> radio slot 2 port 1
The following prompt appears:
radio[2/1]>

Note
For convenience, this User Guide generally shows the radio prompt as radio[2/1]>.

Muting and Unmuting a Radio (CLI)

To mute or unmute the radio, enter the following command:

Phn 3963 013v000

Page 582
Chapter 13: Getting Started (CLI) Configuring the Radio Parameters (CLI)

radio[x/x]>rf mute set admin <admin>

To display the mute status of a radio, enter the following command:
radio[x/x]>rf mute show status
When the timer expires, the radio is automatically unmuted. A timed mute provides a fail-safe mechanism for
maintenance operations that eliminates the possibility of accidently leaving the radio muted after the maintenance
has been completed. By default, the timer is 10 minutes.

Note
In contrast to an ordinary mute, a timed mute is not persistent. This means that if the unit is
reset, the radio is not muted when the unit comes back online, even if the timer had not expired.
Also, in unit and radio protection configurations, a timed mute is not copied to the mate unit or
radio, and no mismatch alarm is raised if a timed mute is configured on only one radio in the
protection pair.

To display the mute status of a radio, enter the following command in radio view:
radio[x/x]>rf mute show status

Table 93 Radio Mute/Unmute CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable on Mutes (on) or unmutes (off)

off the radio.

Examples
The following command mutes radio carrier 1:
radio[2/1]>rf mute set admin on
The following command unmutes radio carrier 2 in a PTP 820C or PTP 820C-HP unit:
radio[2/2]>rf mute set admin off
The following command configures a timed mute on radio carrier 1. This mute will automatically expire in 30 minutes.
radio[2/1]> rf mute set admin on-with-timer timeout-value 30

Configuring the Transmit (TX) Level (CLI)

To set the transmit (TX) level of a radio, enter the following command:
radio[x/x]>rf set tx-level <tx-level>
To display the maximum transmit (TX) level of a radio, enter the following command:
radio[x/x]>rf show max-tx-level

Table 94 Radio Transmit (TX) Level CLI Parameters

Parameter Input Type Permitted Values Description

tx-level Number PTP 820C and PTP 820S units: -1 to The desired TX signal level
22 (Hardware model dependent) (TSL), in dBm.

Phn 3963 013v000

Page 583
Chapter 13: Getting Started (CLI) Configuring the Radio Parameters (CLI)

Examples
The following command sets the TX level of radio carrier 1 to 10 dBm:
radio[2/1]>rf set tx-level 10

Configuring the Transmit (TX) Frequency (CLI)

To set the transmit (TX) frequency of a radio, enter the following command. This command includes an option to set
the remote RX frequency in parallel:
radio[x/x]>rf set tx-frequency <tx-frequency> local-remote <local-remote>

Table 95 Radio Transmit (TX) Frequency CLI Parameters

Parameter Input Type Permitted Values Description

tx-frequency Number Depends on the MRMC The desired TX frequency (in KHz) and, if <local-
script and the unit type. remote> is set to enable, the desired RX
frequency of the remote unit.

local-remote Variable enable Optional. Determines whether to apply the

disable configured TX frequency value to the RX
frequency of the remote unit.

Note
If the carrier belongs to a 4x4 MIMO group, an ASD group, an AFR group, or an XPIC group, you
must disable the group before changing the TX or RX frequency.

For PTP 820E, a frequency scanner is available to scan the frequency range covered by the
currently configured MRMC script and determine the current interference level for each
channel. This enables you to select the best channel in accordance with current interference
levels. See Running the Frequency Scanner (PTP 820E)

The following command sets the TX frequency of radio carrier 1 in an PTP 820C, PTP 820C-HP, or PTP 820S unit to
12900000 KHz, and sets the RX frequency of the remote unit to the same value.
radio[2/1]>rf set tx-frequency 12900000 local-remote enable
The following command sets the TX frequency of radio carrier 1 in an PTP 820C, PTP 820C-HP, or PTP 820S unit to
12900000 KHz, but does not set the RX frequency of the remote unit.
radio[2/1]>rf set rx-frequency 12900000 local-remote disable
The following command sets the TX frequency of the radio in an PTP 820E unit to 71000000 KHz, and sets the RX
frequency of the remote unit to the same value.
radio[2/1]> rf set tx-frequency 71000000 local-remote enable
The following command sets the TX frequency of the radio in an PTP 820E unit to 71000000 KHz, but does not set the
RX frequency of the remote unit.
radio[2/1]> rf set rx-frequency 71000000 local-remote disable

Phn 3963 013v000

Page 584
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Configuring the Radio (MRMC) Script(s) (CLI)

Multi-Rate Multi-Constellation (MRMC) radio scripts define how the radio utilizes its available capacity. Each script is
a pre-defined collection of configuration settings that specify the radio’s transmit and receive levels, link modulation,
channel spacing, and bit rate. Scripts apply uniform transmit and receive rates that remain constant regardless of
environmental impact on radio operation.

Note
The list of available scripts reflects activation-key-enabled features. Only scripts within your
activation-key-enabled capacity will be displayed.

Displaying Available MRMC Scripts (CLI)

To display all scripts that are available for a specific radio carrier in your unit, enter the following command in radio
view:
radio[x/x]>mrmc script show script-type <script-type> acm-support <acm-
support>

Note
The list of available scripts reflects activation-key-enabled features. Only scripts within your
activation-key-enabled capacity will be displayed.

Table 96 MRMC Script CLI Parameters

Parameter Input Type Permitted Values Description

script-type Variable normal Determines the type of scripts to be displayed:

asymmetrical normal – Scripts for symmetrical bandwidth.
asymmetrical – Scripts for asymmetrical
bandwidth.
Note: Asymmetrical scripts are not supported in
this release.

acm-support Boolean yes Determines whether to display scripts that

no support Adaptive Coding Modulation (ACM). In
ACM mode, a range of profiles determines Tx
and Rx rates. This allows the radio to modify its
transmit and receive levels in response to
environmental conditions.

Examples
The following command displays available symmetrical (normal) scripts for radio carrier 1:
radio[2/1]>mrmc script show script-type normal acm-support yes

Phn 3963 013v000

Page 585
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

The following command displays available symmetrical (normal) scripts with ACM support for radio carrier 2 in a PTP
820C unit:
radio[2/2]>mrmc script show script-type normal acm-support yes

Assigning an MRMC Script to a Radio Carrier (CLI)

Once you have a list of valid scripts, you can assign a script to the radio carrier. The command syntax differs
depending on whether you are assigning a script with ACM support or a script without ACM support.

Note
When you enter a command to change the script, a prompt appears informing you that changing the
script will reset the unit and affect traffic. To continue, enter yes. Changing the maximum or
minimum profile does not reset the radio interface.

To assign a script with ACM enabled, enter the following command:

radio[x/x]> mrmc set acm-support script-id <script-id> modulation adaptive
max-profile <profile>
To assign a script without ACM enabled, enter the following command:
radio[x/x]> mrmc set acm-support script-id <script-id> modulation fixed
profile <profile>
To display the current MRMC script configuration, enter the following command:
radio[x/x]>mrmc show script-configuration

Phn 3963 013v000

Page 586
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Table 97 MRMC Script Assignation to Radio Carrier CLI Parameters

Parameter Input Type Permitted Values Description

script-id Number Depends on The ID of the script you want to assign to the
available scripts. radio carrier.

modulation Variable adaptive Determines whether ACM is enabled (adaptive)

fixed or disabled (fixed).

max-profile Number Depends on the unit Adaptive ACM mode only: The maximum profile
type. See for the script. For example, if you select a
Configuring the maximum profile of 5, the system will not climb
Radio (MRMC) above profile 5, even if channel fading
Scripts (CLI). conditions allow it.

min-profile Number Depends on the unit Adaptive ACM mode only: The minimum profile
type. See for the script. For example, if you select a
Configuring the minimum profile of 3, the system will not go
Radio (MRMC) below profile 3 regardless of the channel fading
Scripts (CLI). conditions. The minimum profile cannot be
greater than the maximum profile, but it can be
equal to it.
If you do not include this parameter in the
command, the minimum profile is set at the
default value of 0.

profile Number Depends on the unit Fixed ACM mode only: The profile in which the
type. See system will operate
Configuring the
Radio (MRMC)
Scripts (CLI).

Examples
The following command assigns MRMC script ID 1503, with ACM enabled, a minimum profile of 3, and a maximum
profile of 9, to radio carrier 1 in a PTP 820C or PTP 820S unit:
radio[2/1]>mrmc set acm-support script-id 13 modulation adaptive max-
profile 9 min-profile 3
The following command assigns MRMC script ID 1502, with ACM disabled and a profile of 5, to radio carrier 2 in an
PTP 820C or PTP 820C-HP unit:
radio[2/2]>mrmc set acm-support script-id 13 modulation fixed profile 5
The following command assigns MRMC script ID 4702, with ACM disabled and a profile of 5, to the radio carrier in an
PTP 820E unit:
radio[2/1]>mrmc set acm-support script-id 4702 modulation fixed profile 5
The following command assigns MRMC script ID 4701, with ACM enabled, and both a minimum and a maximum
profile of 5, to the radio carrier in an PTP 820E unit. This is the functional equivalent of assigning a fixed profile.
radio[2/1]>mrmc set acm-support script-id 4701 modulation max-profile 5
min-profile 5

Phn 3963 013v000

Page 587
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Configuring the Radio Parameters (CLI)

In order to establish a radio link, you must:
• Enter radio view.
• Verify that the radio is muted (the Mute Status should be On).
• Configure the radio frequencies.
Note
Even if you are using the default frequencies, it is mandatory to actually
configure the frequencies.

• Configure the TX level.

• Set Mute Admin to Off.
• Verify that the radio is unmuted (the Mute Status should be Off).
Entering Radio View (CLI)
To view and configure radio parameters, you must first enter the radio’s view level in the CLI.
To enter a radio’s view level, enter the following command in root view:

root> radio slot <slot> port <port>

Table 95: Entering Radio View CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 2

port Number Radio Carrier 1: 1 The specific radio carrier

Radio Carrier 2 (PTP you want to access.
820C and PTP 820C-HP
only): 2

The following command enters radio view for radio carrier 1:

root> radio slot 2 port 1

The following prompt appears:

radio[2/1]>

Phn 3963 013v000

Page 588
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Muting and Unmuting a Radio (CLI)

To mute or unmute the radio, enter the following command in radio view:

radio[x/x]>rf mute set admin <admin>

To configure a timed mute, enter the following command in radio view:

radio[x/x]> rf mute set admin on-with-timer timeout-value <1-1440>

When the timer expires, the radio is automatically unmuted. A timed mute provides a fail-safe mechanism for
maintenance operations that eliminates the possibility of accidently leaving the radio muted after the maintenance
has been completed. By default, the timer is 10 minutes.

Note
In contrast to an ordinary mute, a timed mute is not persistent. This
means that if the unit is reset, the radio is not muted when the unit comes back
online, even if the timer had not expired. Also, in unit and radio protection
configurations, a timed mute is not copied to the mate unit or radio, and no
mismatch alarm is raised if a timed mute is configured on only one radio in the
protection pair.

To display the mute status of a radio, enter the following command in radio view:

radio[x/x]>rf mute show status

Table 96: Radio Mute/Unmute CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable on Mutes (on) or unmutes (off)

off the radio.

The following command mutes radio carrier 1:

radio[2/1]>rf mute set admin on

The following command unmutes radio carrier 2 in an PTP 820C or PTPT 820C-HP unit:

radio[2/2]>rf mute set admin off

The following command configures a timed mute on radio carrier 1. This mute will automatically expire
in 30 minutes.

radio[2/1]> rf mute set admin on-with-timer timeout-value 30

Phn 3963 013v000

Page 589
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Configuring the Transmit (TX) Frequency (CLI)

To set the transmit (TX) frequency of a radio, enter the following command in radio view. This command includes an
option to set the remote RX frequency in parallel:

radio[x/x]>rf set tx-frequency <tx-frequency> local-remote

<local-remote>

Table 97: Radio Transmit (TX) Frequency CLI Parameters

Parameter Input Type Permitted Values Description

tx-frequency Number Depends on the The desired TX

MRMC script and the frequency (in KHz) and,
unit type. if <local-remote> is set
to enable, the desired
RX frequency of the
remote unit.
local-remote Variable enable Optional. Determines
disable whether to apply the
configured TX frequency
value to the RX
frequency of the remote
unit.

Notes: If the carrier belongs to a 4x4 MIMO group, an ASD group, an AFR
group, or an XPIC group, you must disable the group before changing the
TX or RX frequency.

For PTPT 820E a frequency scanner is available to scan the

frequency range covered by the currently configured MRMC script and
determine the current interference level for each channel. This enables you
to select the best channel in accordance with current interference levels. See
Running the Frequency Scanner (PTP 820E).

The following command sets the TX frequency of radio carrier 1 in an PTP 820C, PTP 820C-HP, or
PTP 820S unit to 12900000 KHz, and sets the RX frequency of the remote unit to the same value.

radio[2/1]>rf set tx-frequency 12900000 local-remote enable

The following command sets the TX frequency of radio carrier 1 in an PTP 820C,
PTP 820C-HP, or PTP 820S unit to 12900000 KHz, but does not set the RX frequency of the remote
unit.

radio[2/1]>rf set rx-frequency 12900000 local-remote disable

The following command sets the TX frequency of the radio in an PTP 820E unit to 71000000 KHz, and
sets the RX frequency of the remote unit to the same value.

radio[2/1]> rf set tx-frequency 71000000 local-remote enable

The following command sets the TX frequency of the radio in an PTP 820E unit to 71000000 KHz, but
does not set the RX frequency of the remote unit.

Phn 3963 013v000

Page 540
Page 540 of 929
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

radio[2/1]> rf set rx-frequency 71000000 local-remote disable

Phn 3963 013v000

Page 541
Page 541 of 929
Chapter 13: Getting Started (CLI) Configuring the Radio (MRMC) Script(s) (CLI)

Configuring the Transmit (TX) Level (CLI)

To set the transmit (TX) level of a radio, enter the following command in radio view:

radio[x/x]>rf set tx-level <tx-level>

To display the maximum transmit (TX) level of a radio, enter the following command in radio view:

radio[x/x]>rf show max-tx-level

Table 98: Radio Transmit (TX) Level CLI Parameters

Parameter Input Type Permitted Values Description

tx-level Number Depends on hardware The desired TX signal

model. level (TSL), in dBm.

The following command sets the TX level of radio carrier 1 to 10 dBm:

radio[2/1]>rf set tx-level 10

Phn 3963 013v000

Page 542
Chapter 13: Getting Started (CLI) Enabling ACM with Adaptive Transmit Power (CLI)

Enabling ACM with Adaptive Transmit Power (CLI)

When planning ACM-based radio links, the radio planner attempts to apply the lowest transmit power that will
perform satisfactorily at the highest level of modulation. During fade conditions requiring a modulation drop, most
radio systems cannot increase transmit power to compensate for the signal degradation, resulting in a deeper
reduction in capacity. The PTP 820 is capable of adjusting power on the fly, and optimizing the available capacity at
every modulation point.
To enable Adaptive TX Power for a radio, enter the following command:
radio[x/x]>rf adaptive-power set admin enable
To disable Adaptive TX Power for a radio, enter the following command:
radio[x/x]>rf adaptive-power set admin disable
To display whether Adaptive TX Power is enabled, enter the following command:
radio[x/x]>rf adaptive-power show status
The output of this command is:
radio [x/x]>rf adaptive-power show status

RF adaptive power admin status: [enable/disable]

RF adaptive power operational status: [up/down]
RF adaptive power operational status: Up means the feature is enabled and fully functional for that
radio link. Note that the feature is configured and operates independently for each radio link.

Note
Adaptive TX Power only operates when the MRMC script is configured to Adaptive mode. If the script
is configured to Fixed mode (or Adaptive mode with the Minimum and Maximum Profile set to the
same value), you can set adaptive-power admin to enable, but the adaptive power operational
status field will indicate down.

Phn 3963 013v000

Page 543
Chapter 13: Getting Started (CLI) Configuring the RSL Threshold Alarm (CLI)

Configuring the RSL Threshold Alarm (CLI)

You can enable an alarm to be triggered in the event that the RSL falls beneath a defined threshold. This alarm is
alarm ID 1610, Radio Receive Signal Level is below the configured threshold. By default, the alarm is disabled.
To enable the RSL threshold alarm, enter the following command in radio view:
radio[x/x]> rf rsl-degradation set admin enable
To disable the RSL threshold alarm, enter the following command in radio view:
radio[x/x]> rf rsl-degradation set admin disable
To set the threshold of the RSL threshold alarm, enter the following command in radio view:
radio[x/x]> rf rsl-degradation set threshold <-99-0>
The default threshold is -68 dBm.
To display the current alarm configuration, enter the following command in radio view:
radio[x/x]> rf rsl-degradation show status
The following commands enable the RSL threshold alarm for radio carrier 1 and set the threshold to -55 dBm.
root> radio slot 2 port 1
radio [2/1]>rf rsl-degradation set admin enable
radio [2/1]>rf rsl-degradation set threshold -55
radio [2/1]>rf rsl-degradation show status

RSL degradation alarm admin: enable

RSL degradation threshold: -55

radio [2/1]>
The alarm is cleared when the RSL goes above the configured threshold. The alarm is masked if the radio interface
is disabled, the radio does not exist, or a communication-failure alarm (Alarm ID #1703) is raised.

Phn 3963 013v000

Page 544
Chapter 13: Getting Started (CLI) Operating in FIPS Mode (CLI)

Operating in FIPS Mode (CLI)

Note
This feature is only relevant for PTP 820C, PTP 820C-HP and PTP 820S units.
FIPS 140-2 compliance is only available with the PTP 820 Assured platform. 1The PTP 820 Assured
0F

Platform is not supported by System release 11.1.

From release 10.9.6, PTP 820C, PTP 820C-HP and PTP 820S can be configured to be FIPS 140-2-compliant in specific
hardware and software configurations, as described in this section.

Requirements for FIPS Compliance (CLI)

For a full list of FIPS requirements, refer to the PTP 820 FIPS 140-2 Security Policy, available upon request. It is the
responsibility of the customer to ensure that these requirements are met.
For details on hardware requirements for operating in FIPS mode, see Requirements for FIPS Compliance.
Unit redundancy configurations can be configured to be FIPS 140-2-compliant. This requires encryption of the
protection link between the two units. See Encrypting the External Protection Link (CLI).

Enabling FIPS Mode (CLI)

To set the unit to operate in FIPS mode, enter the following command in root view:
root> platform security fips-mode set admin enable
To disable FIPS mode, enter the following command in root view:
root> platform security fips-mode set admin disable

Note
Changing the FIPS configuration causes a unit reset.

To display the unit’s current FIPS setting, enter the following command in root view:
root> platform security fips-mode show
Status values are:
• enable – FIPS mode is enabled.
• disable – FIPS mode is disabled.
After enabling FIPS:
• The MD5 option for SNMPv3 is blocked.

1
The PTP 820 Assured platform is supported with Release 8.3. It is not supported with Release 9.0.

Phn 3963 013v000

Page 545
Chapter 13: Getting Started (CLI) Operating in FIPS Mode (CLI)

• After any system reset, the length of time before users can log back into the system is longer than usual due to
FIPS-related self-testing.
For a full list of FIPS requirements, including software configuration requirements, refer to the PTP 820 FIPS 140-2
Security Policy, available upon request.

Encrypting the External Protection Link (CLI)

For unit redundancy configurations, the external protection link must be encrypted using IPsec. This encrypts all IP
packets that pass between the management ports of the two PTP 820 units.
IPsec uses a 32-character pre-shared key. The pre-shared key is a 32-byte symmetric encryption key. The same pre-
shared key must be configured on both ends of the encrypted link.
IPsec encryption is automatically enabled when FIPS mode is enabled. However, it is enabled with a default value:
protectionpresharedkey0123456789.
If this default value is not changed, the following alarm is triggered:
• 5113 – Protection Pre-Shared-Key has the default value

Initial Configuration of FIPS-Compliant Unit Redundancy

Configuration (CLI)
To set up a unit redundancy configuration that is FIPS 140-2-compliant, you must follow these steps:
1 Configure and enable unit redundancy on both units. See Configuring Unit Protection with HSB Radio Protection
(External Protection).
2 Enable FIPS on both PTP 820 units. See Enabling FIPS Mode (CLI).
When you enable FIPS mode, IPsec encryption will automatically be enabled on the protection link, using the
default protection pre-shared key. Alarm 5113 will be raised.
3 Configure a new pre-shared key on the active unit. To configure a protection key:
i Verify that the web interface protocol for accessing the unit is configured to HTTPS. See Configuring X.509
CSR Certificates and HTTPS (CLI).
ii Enter the following command in root view:
root>platform management protection set pre-shared-key <key>
The key must be exactly 32 characters.
Note: Communication with the standby unit may be lost for a few seconds while the key is
being copied.
To clear the user-defined protection pre-shared key and restore it to its default value, enter the following
command in root view:
root> platform management protection clear pre-shared-key
To display the protection pre-shared key, enter the following command in root view:
root> platform management protection show pre-shared-key

Phn 3963 013v000

Page 546
Chapter 13: Getting Started (CLI) Operating in FIPS Mode (CLI)

Replacing a Unit in a FIPS-Compliant Unit Redundancy

Configuration (CLI)
If it becomes necessary to replace a unit in a FIPS 140-2-compliant unit redundancy configuration, you must pre-
configure the replacement unit as follows:
1 Enable FIPS on the replacement unit. See Enabling FIPS Mode (CLI).
2 Configure the protection pre-shared key on the replacement unit. See Initial Configuration of FIPS-Compliant
Unit Redundancy Configuration (CLI), Step 3.
3 Configure and enable unit redundancy on the replacement unit. See Configuring Unit Protection with HSB Radio
Protection (External Protection).

Phn 3963 013v000

Page 547
Chapter 13: Getting Started (CLI) Configuring Grouping (Optional) (CLI)

Configuring Grouping (Optional) (CLI)

At this point in the configuration process, you should configure any interface groups that need to be set up
according to your network plan. For details on available grouping and other configuration options, as well as
configuration instructions, see System Configurations (CLI).

Phn 3963 013v000

Page 548
Chapter 13: Getting Started (CLI) Creating Service(s) for Traffic (CLI)

Creating Service(s) for Traffic (CLI)

In order to pass traffic through the PTP 820, you must configure Ethernet traffic services. For configuration
instructions, see Configuring Ethernet Services (CLI).

Phn 3963 013v000

Page 549
Chapter 14: Configuration Guide (CLI) Creating Service(s) for Traffic (CLI)

Chapter 14: Configuration Guide (CLI)

This section includes:
• System Configurations (CLI)
• Configuring Multi-Carrier ABC (CLI)
• Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)
• Configuring XPIC (CLI)
• Configuring Unit Protection with HSB Radio Protection (External Protection) (CLI)
• Configuring MIMO and Space Diversity (CLI)
• Operating a PTP 820C/PTP 820C-HP in Single Radio Carrier Mode (CLI)

Phn 3963 013v000

Page 550
Chapter 14: Configuration Guide (CLI) System Configurations (CLI)

System Configurations (CLI)

This section lists the basic system configurations and the PTP 820 product types that support them, as well as links
to configuration instructions.

Table 98 System Configurations (CLI)

Configuration Supported Link to Configuration Instructions

Products

Multi-Carrier ABC (Multi- PTP 820C/C-HP Configuring Multi-Carrier ABC (CLI)

Radio)

Multiband (Enhanced Multi- PTP 820E Configuring Multiband (Enhanced Multi-Carrier ABC)
Carrier ABC) PTP 820C (CLI)
PTP 820C-HP
PTP 820S

Link Aggregation (LAG) PTP 820C/S Configuring Link Aggregation (LAG) and LACP
(Optional) (CLI)

XPIC PTP 820C Configuring XPIC (CLI)

HSB Radio Protection PTP 820C/S Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

1+1 HSB with Space Diversity PTP 820C Configuring 1+1 HSB with Space Diversity (CLI)

MIMO and Space Diversity PTP 820C Configuring MIMO and Space Diversity (CLI)

ASD 2+0 (XPIC) PTP 820C/C-HP Configuring adavanced space Diversity (CLI)

AFR+1+0 PTP 820C (hub Configuring Advanced Frequency Reuse (AFR) (CLI)
site or tail site)
PTP 820S (tail
site only)

PTP 820C in Single Radio PTP 820C/C-HP Operating a PTP 820C/PTP 820C-HP in Single Radio
Carrier Mode Carrier Mode (CLI)

Phn 3963 013v000

Page 551
Chapter 14: Configuration Guide (CLI) Configuring Multi-Carrier ABC (CLI)

Configuring Multi-Carrier ABC (CLI)

Note
This option is only relevant for PTP 820C and PTP 820C-HPunits.

This section includes:

• Multi-Carrier ABC Overview (CLI)
• Configuring a Multi-Carrier ABC Group (CLI)
• Configuring the Multi-Carrier ABC Minimum Bandwidth Override Option (CLI)
• Removing Members from a Multi-Carrier ABC Group (CLI)
• Deleting a Multi-Carrier ABC Group (CLI)

Multi-Carrier ABC Overview (CLI)

Multi-Carrier Adaptive Bandwidth Control (ABC) enables multiple separate radio carriers to be shared by a single
Ethernet port. This provides an Ethernet link over the radio with the total sum of the capacity of all the radios in
the group, while still behaving as a single Ethernet interface. In Multi-Carrier ABC mode, traffic is dynamically
divided among the carriers, at the Layer 1 level, without requiring Ethernet Link Aggregation.
Load balancing is performed regardless of the number of MAC addresses or the number of traffic flows. During
fading events which cause ACM modulation changes, each carrier fluctuates independently with hitless
switchovers between modulations, increasing capacity over a given bandwidth and maximizing spectrum
utilization. The result is 100% utilization of radio resources in which traffic load is balanced based on instantaneous
radio capacity per carrier.
One Multi-Carrier ABC group that includes both radio interfaces can be configured per unit. The MRMC scripts for
both radio carriers must be identical.

Configuring a Multi-Carrier ABC Group (CLI)

Note
Radio slot 2 port 1 should always be configured on channel 1 while Radio slot 2 port 2 should always
be configured on channel 2.

To configure a Multi-Carrier ABC group:

1 Create the group by entering the following command in root view:
root> multi-carrier-abc create group group_id 1
multi-carrier-abc group-id [1]>
2 Enter Multi-Carrier ABC Group view by entering the following command in root view:

Phn 3963 013v000

Page 552
Chapter 14: Configuration Guide (CLI) Configuring Multi-Carrier ABC (CLI)

root> multi-carrier-abc group-id [1]

3 Add members to the group as follows:
o To add a radio interface to the group, enter the following command in Multi-Carrier
ABC Group view. Repeat this command for each radio interface you want to add.
multi-carrier-abc group-id [1]> attach-member slot 2 port <port> channel-
id <1-16>
The Channel ID identifies the interface within the group.
4 Repeat for the second radio interface.
The following commands create a Multi-Carrier ABC group.
root> multi-carrier-abc create group group_id 1
multi-carrier-abc group-id[1]> attach-member slot 2 port 1 channel-id 1
multi-carrier-abc group-id[1]> attach-member slot 2 port 2 channel-id 2
multi-carrier-abc group-id[1]> exit

Configuring the Multi-Carrier ABC Minimum Bandwidth

Override Option (CLI)
A multi-carrier ABC group can be configured to be placed in Down state if the group’s capacity falls beneath a user-
defined threshold.
By default, the Multi-Carrier ABC minimum bandwidth override option is disabled. When enabled, the Multi-
Carrier ABC group is automatically placed in a Down state in the event that the group’s aggregated capacity falls
beneath the user-configured threshold. The group is returned to an Up state when its aggregated capacity goes
above the threshold.
In order to use Multi-Carrier ABC Minimum Bandwidth Override, an ASP group must be configured on the PTP
820C or PTP 820C-HP unit in which the Monitored Interface is the Multi-Carrier ABC group and the Controlled
Interface is the Ethernet interface that faces the upstream PTP 820 unit. See Configuring Automatic State
Propagation and Link Loss Forwarding (CLI).
An alarm is also raised when this feature is enabled and the group’s aggregated capacity falls beneath the
threshold:
• Alarm ID – 2201
• Alarm Description – Multi Carrier ABC bandwidth is below the threshold
This option is used in conjunction with the LAG group shutdown in case of degradation event option (see Enabling
and Disabling the LAG Group Shutdown in Case of Degradation Event Option (CLI)) in cases where the operator
wants to re-route traffic from an upstream switch connected to an another PTP 820 unit whenever the link is
providing less than a certain capacity. To set up a configuration in which a drop in the capacity of the Multi-Carrier
ABC group closes the Ethernet port in the upstream PTP 820 unit, you must perform all of the following steps:
• Enable the Multi-Carrier ABC minimum bandwidth option and set a threshold on the PTP 820C or PTP 820C-HP
unit, as described below.
• Enable an ASP group on the PTP 820C or PTP 820C-HP unit, where the Monitored Interface is the Multi-Carrier
ABC group and the Controlled Interface is the Ethernet interface that faces the upstream PTP 820 unit. See
Configuring Automatic State Propagation and Link Loss Forwarding (CLI).
• Enable the LAG group shutdown in case of degradation event option on the upstream PTP 820C unit.

Phn 3963 013v000

Page 553
Chapter 14: Configuration Guide (CLI) Configuring Multi-Carrier ABC (CLI)

Notes:

Note
When using in-band management, management is lost in the event of radio failure and returns when
the radio link is restored.
The minimum bandwidth threshold is based on the capacity of the Multi-Carrier ABC group, not the
combined capacities of the group’s members. The group’s aggregated capacity is displayed in the
Multi-Carrier ABC Group – Edit Group page (Figure 63).

To enable Multi-Carrier ABC Minimum Bandwidth Override, enter the following command in root view:
root> platform if-manager set group-type abc group-number <1-4> minimum-
bw-admin enable
To disable Multi-Carrier ABC Minimum Bandwidth Override, enter the following command in root view:
root> platform if-manager set group-type abc group-number <1-4> minimum-
bw-admin disable
To set the Multi-Carrier ABC Minimum Bandwidth Override threshold (in Mbps), enter the following command in
root view:
root> platform if-manager set group-type abc group-number <1-4> minimum-
bw-threshold <0-20000>
The threshold can be between 0 – 20000 Mbps, with a resolution of 1 Mbps.
The following commands enable Multi-Carrier ABC Minimum Bandwidth Override threshold for Multi-Carrier ABC
group 1, and set a threshold of 12000 Mbps.
root> platform if-manager set group-type abc group-number 1 minimum-bw-
admin enable
root> platform if-manager set group-type abc group-number 1 minimum-bw-
threshold 12000
To view the status and the threshold use the following command:
root> platform if-manager show interfaces

Removing Members from a Multi-Carrier ABC Group (CLI)

To remove members from a Multi-Carrier ABC group:
1 To remove an individual radio interface from the Multi-Carrier ABC group, go to Multi-Carrier ABC group
view and enter the following command:
multi-carrier-abc group-id[1]> detach-member channel-id <channel-id>

Deleting a Multi-Carrier ABC Group (CLI)

To delete a Multi-Carrier ABC group:
1 Remove the members from the group. See Configuring the Multi-Carrier ABC Minimum Bandwidth Override
Option (CLI).

Phn 3963 013v000

Page 554
Chapter 14: Configuration Guide (CLI) Configuring Multi-Carrier ABC (CLI)

2 Delete the group by entering the following command in root view:

root> multi-carrier-abc delete group group_id 1

Phn 3963 013v000

Page 555
Chapter 14: Configuration Guide (CLI) Configuring Multiband (Enhanced Multi-Carrier ABC) (CLI)

Configuring Multiband (Enhanced Multi-Carrier

ABC) (CLI)

This feature requires:

• PTP 820E ESP hardware version
• When used with PTP 820C, PTP 820C-HP, or PTP 820S, PTP 820C/PTP 820C-HP/PTP 820S ESS hardware
version (two SFP ports) is required in order to configure synchronization and/or in-band management for
the PTP 820C, PTP 820C-HP, or PTP 820S

Multiband Overview (CLI)

For general information about Multiband and how it operates, see Multiband Overview.

Multiband Configuration (CLI)

To configure a Multiband node:
1 Connect the external switch to the Eth1 port on the PTP 820E.
2 Connect the Eth2 port on the PTP 820E to the unit paired with the PTP 820E. When the paired unit is an PTP
820C, PTP 820C-HP, or PTP 820S, use the Eth2 port on the PTP 820C, PTP 820C-HP, or PTP 820S.
3 Verify that no service points are configured on the Eth2 port of the PTP 820E. If there are service points on
Eth2, remove them. See Deleting a Service Point (CLI).
4 Set Eth2 on the PTP 820E to Admin – Disable. See Error! Reference source not found..
5 On the PTP 820E, configure a Multiband group that includes Eth2 and the radio:
i Create the group by entering the following command in root view:
root>multi-carrier-abc create group group_id 1 slot 1 type Enhanced
ii Enter Multi-Carrier ABC Group view by entering the following command in root view:
root>multi-carrier-abc group-id 1 slot 1 type Enhanced
multi-carrier-abc enhanced-group-id [1] slot [1]>
iii In Multi-Carrier ABC Group view, add the radio interface by entering the following command:
multi-carrier-abc enhanced-group-id [1] slot [1]>attach-eth-member slot 1
port 2 channel-id 2
iv In Multi-Carrier ABC Group view, add the Ethernet interface by entering the following command:
multi-carrier-abc enhanced-group-id [1] slot [1]>attach-member slot 2
port 1 channel-id 1
Note: The channel-id parameter must be set to 1 for the radio interface and 2 for the
Ethernet interface.
v In Multi-Carrier ABC Group view, use the following command to set the maximum traffic that
the PTP 820E will pass to the paired unit
• When using Fixed ACM mode, set this parameter to the actual rate you want the paired
unit to broadcast.
• When using Adaptive ACM mode, set this parameter to the maximum of the paired unit’s
capacity.

Phn 3963 013v000

Page 556
Chapter 14: Configuration Guide (CLI) Configuring Multiband (Enhanced Multi-Carrier ABC) (CLI)

The default value is 1000 Mbps.

multi-carrier-abc enhanced-group-id [1] slot [1]>abc-set-eth-max-
bandwidth slot 1 port 2 max-bandwidth <1-1000>
For example, the following command sets the maximum traffic to 900 Mbps:
multi-carrier-abc enhanced-group-id [1] slot [1]>abc-set-eth-max-
bandwidth slot 1 port 2 max-bandwidth 900

Maximum bandwith: 900 Mbps

Use the following command in Multi-Carrier ABC Group view to display the current maximum traffic
setting:
multi-carrier-abc enhanced-group-id [1] slot [1]>abc-show-eth-max-
bandwidth slot 1 port 2
Note: The Maximum Bandwidth represents the L1 capacity of the radio link connected to
the Ethernet member. The actual bandwidth that will be available for traffic is less due to
overhead.

When using a third-party radio as the paired unit, it is particularly important to set this
parameter properly in order to ensure optimal performance. Failure to properly set this
parameter may lead to frequent pauses as the queue fills up during low capacity periods,
such as when weather conditions cause the ACM profile to drop.
vi Reset the PTP 820E. See Error! Reference source not found..

Note: After adding Eth2 to the Multiband group, an alarm is raised (Alarm 1794). This
alarm is cleared when the unit is reset.

6 On the PTP 820C, PTP 820C-HP, or PTP 820S, configure a Pipe service between Eth2 and the radio or Multi-
Carrier ABC group. See Configuring Ethernet Services (CLI).
7 On the PTP 820C, PTP 820C-HP, or PTP 820S, configure Automatic State Propagation with ASP trigger by
remote fault enabled. See Error! Reference source not found..
8 On the PTP 820C, PTP 820C-HP, or PTP 820S, configure Bandwidth Notification. Bandwidth Notification must be
configured via the Web EMS. See Multiband Configuration, Step Error! Reference source not found..

Multiband Management (CLI)

The PTP 820E unit in a Multiband configuration can be managed normally, as in any other configuration. For in-
band management of the PTP 820E, configure the management service on the PTP 820E Multiband group.
The following options are available for managing the PTP 820C, PTP 820C-HP, or PTP 820S unit in a Multiband
configuration:
• Inband management via the PTP 820E
• Inband management directly from the external switch
• Out-of-Band management
For a detailed explanation of these options and their requirements, see Multiband Management.

Phn 3963 013v000

Page 557
Chapter 14: Configuration Guide (CLI) Configuring Multiband (Enhanced Multi-Carrier ABC) (CLI)

Configuring Synchronization in a Multiband Node (CLI)

SyncE and 1588 Transparent Clock can be used in Multiband nodes. In Multiband nodes that consist of an PTP 820E
and an PTP 820C, PTP 820C-HP, or PTP 820S, SyncE and 1588 Transparent Clock can also be configured for the PTP
820C, PTP 820C-HP, or PTP 820S via the PTP 820E. SyncE and 1588 Transparent Clock for the PTP 820C, PTP 820C-
HP, or PTP 820S require an ESS hardware version for PTP 820C, PTP 820C-HP, or PTP 820S (two SFP ports) and a
special cable. For details, see Configuring Synchronization in a Multiband Node.

Note:
When a third-party unit is paired with the PTP 820E, it is a prerequisite that the third-
party radio unit support SyncE and, if required, 1588 Transparent Clock in order to
provide synchronization for the Multiband node.

For instructions on configuring SyncE, see Error! Reference source not found..
For instructions on configuring 1588 Transparent Clock, see Error! Reference source not found..

Deleting a Multiband Group (CLI)

If you need to delete the Multiband group, you must first remove the group’s members, then delete the group.
To remove members from a Multi-Carrier ABC group, go to Multi-Carrier ABC group view and enter the following
command for each interface in the group:
multi-carrier-abc enhanced-group-id [1] slot [1]>detach-member channel-id
<1-2>
After removing the members, enter the following command in root view:
root> multi-carrier-abc delete group group_id 1 slot 1 type Enhanced

Displaying Multiband Group Statistics (CLI)

To display general information about a Multiband group, including the group’s TX and RX capacity, go to Multi-
Carrier ABC group view and enter the following command:
multi-carrier-abc enhanced-group-id [1] slot [1]>summary-show
To display port counters for a Multiband group, go to Multi-Carrier ABC group view and enter the following
command:
multi-carrier-abc enhanced-group-id [1] slot [1]>show-ethernet-port-
counters

Phn 3963 013v000

Page 558
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Configuring Link Aggregation (LAG) and LACP

(Optional) (CLI)

Link aggregation (LAG) enables you to group several physical Ethernet or radio interfaces into a single logical
interface bound to a single MAC address. This logical interface is known as a LAG group. Traffic sent to the
interfaces in a LAG group is distributed by means of a load balancing function. PTP 820 uses a distribution function
of up to Layer 4 in order to generate the most efficient distribution among the LAG physical ports.
This section explains how to configure LAG and includes the following topics:
• LAG Overview (CLI)
• Configuring a LAG Group (CLI)
• Configuring LACP (CLI)
• Viewing LAG Details (CLI)
• Editing and Deleting a LAG Group (CLI)
• Enabling and Disabling the LAG Group Shutdown in Case of Degradation Event Option (CLI)
• Configuring Enhanced LAG Distribution (CLI)
• Displaying LACP Parameters and Statistics (CLI)

LAG Overview (CLI)

Link aggregation (LAG) enables you to group several physical Ethernet or radio interfaces into a single logical
interface bound to a single MAC address. This logical interface is known as a LAG group. Traffic sent to the
interfaces in a LAG group is distributed by means of a load balancing function. PTP 820 uses a distribution function
of up to Layer 4 in order to generate the most efficient distribution among the LAG physical ports.
LAG can be used to provide interface redundancy, both on the same card (line protection) and on separate cards
(line protection and equipment protection).
LAG can also be used to aggregate several interfaces in order to create a wider (aggregate) link. For example, LAG
can be used to create a 4 Gbps channel.
You can create up to four LAG groups.
The following restrictions exist with respect to LAG groups:
• Only physical interfaces (including radio interfaces), not logical interfaces, can belong to a LAG group.
• 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.
• When removing an interface from a LAG group, the removed interface is assigned the default interface values.
There are no restrictions on the number of interfaces that can be included in a LAG. It is recommended, but not
required, that each interface in the LAG have the same parameters (e.g., speed, duplex mode).

Phn 3963 013v000

Page 559
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Note
To add or remove an Ethernet interface to a LAG group, the interface must be in an administrative
state of “down”. This restriction does not apply to radio interfaces. For instructions on setting the
administrative state of an interface, see Enabling the Interfaces (CLI)

PTP 820 supports LACP, which expands the capabilities of static LAG and provides interoperability with third-party
equipment that uses LACP. LACP improves the communication between LAG members. This improves error
detection capabilities in situations such as improper LAG configuration or improper cabling. It also enables the LAG
to detect uni-directional failure and remove the link from the LAG, preventing packet loss.
LACP is enabled as part of the LAG configuration process. It should only be used if the LAG is in a link with another
LACP-enabled LAG.

Note
LACP is not supported with unit protection. For unit protection, a special, limited implementation is
configured on the logical interface level. See Configuring Line Protection Mode (CLI).
LACP can only be used with Ethernet interfaces.

LACP cannot be used with Enhanced LAG Distribution or with the LAG Group Shutdown in Case of
Degradation Event feature.

Configuring a LAG Group (CLI)

To create a LAG:
1 Go to interface view for the first interface you want to assign to the LAG and enter the following
command:
eth type eth [x/x]> static-lag add lagid <lagid>
2 Repeat this process for each interface you want to assign to the LAG.

Configuring LACP (CLI)

To enable LACP on a LAG group, go to interface view for the LAG and enter the following command:
eth group [lagx]> lacp admin set enable
To disable LACP on a LAG group, go to interface view for the LAG and enter the following command:
eth group [lagx]> lacp admin set disable
To display whether or not LACP is enabled on a LAG group, go to interface view for the LAG and enter the following
command:
eth group [lagx]>lacp admin show
The following commands enable LACP for LAG group 1:
root> ethernet interfaces group lag1
eth group [lag1]>lacp admin set enable
eth group [lag1]>

Phn 3963 013v000

Page 560
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Viewing LAG Details (CLI)

To display the name of a LAG to which an interface belongs, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> static-lag show name
To enter interface view for a LAG, enter the following command in root view:
root> ethernet interfaces group <lagid>
To display details about a LAG, go to interface view for the LAG and enter the following command:
eth group [lagx]> summary show
To display a LAG's operational state, go to interface view for the LAG and enter the following command:
eth group [lagx]> operational state show
To display a list of interfaces that belong to a LAG, go to interface view for the LAG and enter the following
command:
eth group [lagx]> port static-lag show members

Editing and Deleting a LAG Group (CLI)

To remove a member Ethernet interface from a LAG, go to interface view for the LAG and enter the following
command:
eth group [lagx]> port static-lag remove member interface eth slot <slot>
port <port>
To remove a member radio interface from a LAG, go to interface view for the LAG and enter the following
command:
eth group [lagx]> port static-lag remove member interface radio slot
<slot> port <port>
To delete a LAG, go to interface view for the LAG and simply remove all the members, as described above.

Table 99 LAG Group CLI Parameters

Parameter Input Type Permitted Values Description

lagid Variable lag1 The ID for the LAG.

lag2
lag3
lag4

slot Number Ethernet: 1 Depends on the

Radio: 2 interface and unit
type.

Phn 3963 013v000

Page 561
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Parameter Input Type Permitted Values Description

port Number GbE 1: 1 The port number of

GbE 2: 2 the interface.

GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (PTP 820C only): 2

Examples
The following commands create a LAG with the ID lag2. The LAG includes the Ethernet interfaces 1 and 2 and radio
interface 1:
root> platform if-manager set interface-type ethernet slot 1 port 1 admin
down

root> platform if-manager set interface-type ethernet slot 1 port 2 admin

down

root> ethernet interfaces eth slot 1 port 1

eth type eth [1/1]>

eth type eth [1/1]> static-lag add lagid lag2

eth type eth [1/1]> exit

root>

root> ethernet interfaces eth slot 1 port 2

eth type eth [1/2]>

eth type eth [1/2]> static-lag add lagid lag2

eth type eth [1/2]> exit

root>

root> ethernet interfaces radio slot 2 port 1

eth type radio[2/1]>

eth type radio[2/1]> static-lag add lagid lag2

eth type radio[2/1]> exit

root> platform if-manager set interface-type ethernet slot 1 port 1 admin

up

root> platform if-manager set interface-type ethernet slot 1 port 2 admin

up
The following command displays the name of the LAG to which Ethernet port 1 belongs:
eth type eth [1/1]> static-lag show name

Static-lag group name: lag2

The following commands display details about the LAG:
root> ethernet interfaces group lag2

Phn 3963 013v000

Page 562
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

eth group [lag2]>

eth group [lag2]> port static-lag show members

Static-lag members

-------------------

Eth#[1/1]
Eth#[1/2]
Radio#[2/1]

eth group [lag2]> summary show

Group lag2 Summary: Value

Port Description:
Port Admin state: enable
Port Operational state: down
Port Edge state: non-edge-port
Member Port#(1) 1/1
Member Port#(2) 1/2
Member Port#(3) 2/1

eth group [lag2]> operational state show

Port operational state: up.

eth group [lag2]>

The following commands remove port 2 on slot 1 from the LAG:
root> platform if-manager set interface-type ethernet slot 1 port 2 admin
down

root> ethernet interfaces group lag2

eth group [lag2]>

eth group [lag2]> port static-lag remove member interface eth slot 1 port
2

Enabling and Disabling the LAG Group Shutdown in Case of

Degradation Event Option (CLI)
Note
LAG Group Shutdown in Case of Degredation Event cannot be used with LACP.

A LAG group can be configured to be automatically closed in the event of LAG degradation. This option is used if
you want traffic from the switch to be re-routed during such time as the link is providing less than a certain
capacity.
By default, the LAG group shutdown in case of degradation event option is disabled. When enabled, the LAG is
automatically closed in the event that any one or more ports in the LAG fail. When all ports in the LAG are again
operational, the LAG is automatically re-opened.

Phn 3963 013v000

Page 563
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Note
Failure of a port in the LAG also triggers a lag-degraded alarm, Alarm ID 100.

To enable the LAG group shutdown in case of degradation event option, go to interface view for the LAG and enter
the following command:
eth group [lagx]> static-lag set lag-degrade-admin admin enable
To disable the LAG group shutdown in case of degradation event option, go to interface view for the LAG and enter
the following command:
eth group [lagx]> static-lag set lag-degrade-admin admin disable
To display the current LAG group shutdown in case of degradation event option setting, go to interface view for
the LAG and enter the following command:
eth group [lagx]> static-lag show lag-degrade-admin
The following commands enable the LAG group shutdown in case of degradation event option for LAG group 1:
root> ethernet interfaces group lag1
eth group [lag1]>static-lag set lag-degrade-admin admin enable
eth group [lag1]>

Configuring Enhanced LAG Distribution (CLI)

You can change the distribution function by selecting from ten pre-defined LAG distribution schemes. The feature
includes a display of the TX throughput for each interface in the LAG, to help you identify the best LAG distribution
scheme for the specific link.

Note
Enhanced LAG distribution is only available for LAG groups that consist of exactly two interfaces. It
cannot be used with LACP.

To configure enhanced LAG distribution, go to interface view for the LAG and enter the following command:
eth group [lagx]> static-lag set df-pattern df <1-10>
The following commands set the LAG distribution scheme for LAG group 1 as distribution pattern 3.
root> ethernet interfaces group lag1
eth group [lag1]>static-lag set df-pattern df 3
The default LAG distribution pattern is 1.
To display the current LAG distribution scheme, go to interface view for the LAG and enter the following command:
eth group [lagx]> static-lag show df-pattern
It is recommended to experiment with the various schemes by monitoring the TX port PMs for each interface in
the LAG for each LAG distribution scheme. In the Web EMS, the page in which you configure enhanced LAG
distribution also displays TX throughput PMs per interface. See Configuring Enhanced LAG Distribution. For
information on monitoring Ethernet port PMs via the CLI, see Displaying Ethernet Port PMs (CLI).

Phn 3963 013v000

Page 564
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Displaying LACP Parameters and Staistics (CLI)

You can display the following LACP parameters and statistics:
• LACP Aggregation (per LAG)
• LACP Port Status
• LACP Port Statistics
• LACP Port Debug Statistics

Note
PTP 820 does not support any LACP write parameters.

Displaying LACP Aggregation Status Parameters (CLI)

To display LACP aggregation status parameters, go to interface view for the LAG and enter the following command:
eth group [lagx]> lacp show status

Table 100 LACP Aggregation Status Parameters (CLI)

Parameter Definition
Admin Key The current administrative value of the key for the Aggregator.
System ID The MAC address value used as a unique identifier for the system that
contains this Aggregator.
System Priority The priority value associated with the Actor’s System ID.
Aggregate or Individual Indicates whether the Aggregator represents an aggregate or an
individual link.
Actor Oper Key The current operational value of the Key for the Aggregator.

Phn 3963 013v000

Page 565
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Agg MAC Address The individual MAC address assigned to the Aggregator.
Partner System ID The MAC address value consisting of the unique identifier for the current
protocol Partner of this Aggregator.
Partner System Priority The priority value associated with the Partner’s System ID.
Partner Oper Key The current operational value of the Key for the Aggregator’s current
Protocol partner.
Collector Max Delay The maximum delay, in tens of microseconds.

Displaying LACP Port Status Parameters (CLI)

To display LACP port status parameters, go to interface view for the LAG and enter the following command:
eth group [lagx]> lacp show ports status

Phn 3963 013v000

Page 566
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Table 101 LACP Port Status Parameters (CLI)

Parameter Definition
System Priority The priority value associated with the Actor’s System ID.
Admin Key The current administrative value of the Key for the Aggregation Port.
System ID The MAC Address value that defines the value of the System ID for the
system that contains this Aggregation Port.
Port Priority The priority value assigned to this Aggregation Port.
Actor State The current operational values of the Actor’s state as transmitted by the
Actor via LACPDUs.
Partner State The current values of Actor State in the most recently received LACPDU
transmitted by the protocol Partner.

Phn 3963 013v000

Page 567
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

Parameter Definition
Last RX Time The value of a TimeSinceSystemReset (F.2.1) when the last LACPDU was
received by this Aggregation port.
RX State The state of the receive state machine for the Aggregation port.
Possible values are:
• Current – An LACPDU was received before expiration of the most
recent timeout period.
• Expired – No LACPDU was received before expiration of the most
recent timeout period.
• Defaulted – No LACPDU was received during the two most recent
timeout periods.
Mux State The state of the Mux state machine for the Aggregation port. Possible
values are Collecting, Distributing, Attached, and Detached.
Mux Reason A text string indicating the reason for the most reason change in the state
of the Mux machine.
Partner Oper Port The operational port number assigned to this Aggregation port by the
Aggregation port’s port Partner.
Partner Oper System The operational value of priority associated with the Partner’s System ID.
Priority
Partner Oper Key The current operational value of the Key for the protocol Partner.
Partner Oper System ID The MAC Address value representing the current value of the
Aggregation Port’s protocol Partner’s System ID.
Partner Oper Port The Priority value assigned to this Aggregation port by the Partner.
Priority

Displaying LACP port Statistics (CLI)

To display LACP port statistics, go to interface view for the LAG and enter the following command:

Phn 3963 013v000

Page 568
Chapter 14: Configuration Guide (CLI) Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)

eth group [lagx]> lacp show ports statistics

Table 102 LACP Port Statistics (CLI)

Parameter Definition
LACPDU RX The number of LACPDUs that this port has received.
LACPDU TX The number of LACPDUs that this port has transmitted.
Illegal RX The number of illegal protocol frames that this port has received.
Unknown RX The number of unknown protocol frames that this port has received.

Phn 3963 013v000

Page 569
Chapter 14: Configuration Guide (CLI) Configuring XPIC (CLI)

Configuring XPIC (CLI)

Note
This option is only relevant for PTP 820C units.

This section explains how to configure XPIC and includes the following topics:
• XPIC Overview (CLI)
• Configuring the Radio Carriers for XPIC (CLI)
• Creating an XPIC Group (CLI)
• Performing Antenna Alignment for XPIC (CLI)

XPIC Overview (CLI)

Cross Polarization Interference Canceller (XPIC) is a feature that enables two radio carriers to use the same
frequency with a polarity separation between them. Since they will never be completely orthogonal, some signal
cancelation is required.
In addition, XPIC includes an automatic recovery mechanism that ensures that if one carrier fails, or a false signal is
received, the mate carrier will not be affected. This mechanism also ensures that both carriers will be operational,
after the failure is cleared.
To configure and enable XPIC, first configure the Carriers and then perform antenna alignment, as described
below.
For 2+2 XPIC using an external switch operating in LAG mode, Mate Management Access enables users to manage
both units via in-band management. See Mate Management Access (IP Forwarding) (CLI).

Configuring the Radio Carriers for XPIC (CLI)

To configure the radio carriers:
1. Configure the carriers on both ends of the link to the desired frequency channel. Both carriers must be
configured to the same frequency channel.
2. Assign XPIC (CCDP operational mode) support-enabled script to both RMCs on both ends of the link. Each RMC
must be assigned the same script. See Configuring the Radio (MRMC) Script(s) (CLI).

Note
XPIC support is indicated by an X in the script name. For example, mdN_A2828X_111_1205 is an
XPIC-enabled script. mdN_A2828N_130_100 is not an XPIC-enabled script. For a list of XPIC support-
enabled scripts, refer to the most recent PTP 820C/S Release Notes.

Phn 3963 013v000

Page 570
Chapter 14: Configuration Guide (CLI) Configuring XPIC (CLI)

3. Create an XPIC group. See Creating an XPIC Group (CLI).

Creating an XPIC Group (CLI)

To create an XPIC group, enter the following commands:
root> radio-groups

radio-groups>

radio-groups> xpic set admin enable

To disable XPIC, enter the following commands:
root> radio-groups

radio-groups>

radio-groups> xpic set admin disable

Performing Antenna Alignment for XPIC (CLI)

To configure the antennas:
1. Align the antennas for the first carrier. For a 2+2 XPIC configuration (or a 4x4 MIMO configuration), align the
antennas for the first carrier on the upper PTP 820C unit. While you are aligning these antennas, mute the
second carrier. See Error! Reference source not found.. For a 2+2 XPIC configuration (or a 4x4 MIMO
configuration), mute all the carriers except the first carrier on the upper PTP 820C or PTP 820C-HP unit.
2. Adjust the antenna alignment until you achieve the maximum RSL for the first-carrier link (the “RSLwanted”).
This RSL should be no more than
+/-2 dB from the expected level. Record the RSL of the first carrier as the RSLwanted.
3. Measure the RSL of the second carrier and record it as the “RSLunwanted”.

Note
To measure the second carrier, leave the Voltmeter connected to the BNC connector. In the Radio
Parameters page of the Web EMS, change the RSL Connector Source field from PHYS1 to PHYS2 (or
vice versa). The BNC connector will now measure RSL from the other carrier.

4. Determine the XPD, using either of the following two methods:

o To calculate the XPI, subtract RSLunwanted from the RSLwanted.
o Read the XPI by going to radio view and entering one of the following commands:
radio [x/x]>modem pm-xpi show interval 15min

radio [x/x]>modem pm-xpi show interval 24hr

5. The XPD should be between 25dB and 30 dB. If it is not, you should adjust the OMT assembly on the back of
the antenna at one side of the link until you achieve the highest XPD, which should be no less than 25dB.
Adjust the OMT very slowly in a right-left direction. OMT adjustment requires very fine movements and it may
take several minutes to achieve the best possible XPI.

Phn 3963 013v000

Page 571
Chapter 14: Configuration Guide (CLI) Configuring XPIC (CLI)

Note
As an extra step, to check the veracity of the initial measurements, you can mute the first carrier and
unmute the second carrier on the upper PTP 820C units on both sides of the link. Then measure the
RSL of the second carrier link (the “RSLwanted”), measure the RSL of the first carrier (the
“RSLunwanted”) and determine the XPD. The XPD should match the XPD with the second carriers
muted.

6. Unmute all the carriers and check the RSL levels of all the carriers on both sides of the link. The RSL of the
horizontal carrier of the local unit should match the RSL of the vertical carrier of the remote unit, within ±2dB.
The RSL of the vertical carrier of the local unit should match the RSL of the horizontal carrier of the remote
unit, within ±2dB.
7. For a 2x2 configuration, repeat Steps Error! Reference source not found. through Error! Reference source not
found. for the lower PTP 820C unit.
8. Check the XPI levels of all the carriers at both sides of the link by going to radio view and entering one of the
following commands:
radio [x/x]>modem pm-xpi show interval 15min

radio [x/x]>modem pm-xpi show interval 24hr

All four carriers should have approximately the same XPI value. Do not adjust the XPI at the remote side of the link,
as this may cause the XPI at the local side of the link to deteriorate.

Note
In some cases, the XPI might not exceed the required 25dB minimum due to adverse atmospheric
conditions. If you believe this to be the case, you can leave the configuration at the lower values, but
be sure to monitor the XPI to make sure it subsequently exceeds 25dB. A normal XPI level in clear sky
conditions is between 25 and 30dB.

Displaying XPIC Status (CLI)

To display the status of an XPIC group, enter the following command in radio-groups view:
radio-groups> xpic show status
The following is a typical command output:
XPIC:
Carrier 1: Radio #[2/1] ; Carrier 2: Radio #[2/2]
Admin mode: enable
XPIC state: XPIC-Idle

Phn 3963 013v000

Page 572
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

Configuring Unit Protection with HSB Radio

Protection (External Protection) (CLI)

This section explains how to configure unit protection, including HSB radio protection and Ethernet interface
protection, and includes the following topics:
• Unit Protection Overview (CLI)
• Configuring HSB Radio Protection (CLI)
• Configuring 2+2 HSB Protection on a PTP 820C/PTP 820C-HP Unit (CLI)
• Viewing the Configuration of the Standby unit (CLI)
• Editing Standby Unit Settings (CLI)
• Viewing Link and Protection Status and Activity (CLI)
• Manually Switching to the Standby Unit (CLI)
• Disabling Automatic Switchover to the Standby Unit (CLI)
• Disabling Unit Protection (CLI)

Note
For instructions on configuring 1+1 unit protection with Space Diversity, see Configuring 1+1 HSB
with Space Diversity (CLI).

Unit Protection Overview (CLI)

PTP 820C, PTP 820C-HP and PTP 820S support 1+1 HSB radio protection. PTP 820C and PTP 820C-HP also supports
2+2 HSB radio protection. In HSB radio protection, one PTP 820 operates in active mode and the other operates in
standby mode. If a protection switchover occurs, the Active unit goes into standby mode and the Standby unit
goes into active mode.
• For a full explanation of 1+1 HSB radio protection and 2+2 HSB radio protection support in PTP 820C and PTP
820C-HP, refer to the PTP 820C or PTP 820C-HP Technical Description.
• For a full explanation of 1+1 HSB radio protection support in PTP 820S, refer to the PTP 820S Technical
Description.

To configure unit protection, you must perform the following steps:

1 Configure Ethernet interface protection – See Configuring Ethernet Interface Protection (CLI).
2 Configure HSB radio protection – See Configuring HSB Radio Protection (CLI).
3 For 2+2 HSB configurations (PTP 820C and PTP 820C-HP only), perform the additional steps described in
Configuring 2+2 HSB Protection on a PTP 820C/PTP 820C-HP Unit (CLI).

Phn 3963 013v000

Page 573
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

Note
For FIPS configurations, the external protection link must be encrypted using IPsec. This encrypts all
IP packets that pass between the management ports of the two units. For instructions, see
Encrypting the External Protection Link (CLI)

Configuring Ethernet Interface Protection (CLI)

There are two modes for Ethernet interface protection in an HSB radio protection configuration:
Line Protection Mode – Traffic is routed to the Ethernet ports via two ports on an external switch.
Split Protection Mode – Only available for optical Ethernet ports. An optical splitter cable is used to connect to
both the active and the standby optical Ethernet ports.

Configuring Line Protection Mode (CLI)

To configure line protection mode:

1 Configure the GE ports on the external switch in LACP mode. The external switch must support LACP.

Note
PTP 820 supports a special LACP implementation for purposes of line protection only. This LACP
implementation is configured on the logical interface level, as described below. Regular LACP is
configured as part of the LAG configuration, and is not supported with unit redundancy. See
Configuring Link Aggregation (LAG) and LACP (optional) (CLI).

2 Connect one port on the external switch to an Ethernet port on the active PTP 820, and the other port on
the external switch to an Ethernet port on the standby PTP 820.
3 Enable LACP on the Ethernet interface connected to the external switch on the active PTP 820:
i Go to interface view for the Ethernet interface connected to the external switch on the active PTP 820.
ii In interface view, enter the following command:
eth type eth [1/x]>interface-mode-set interface-mode LACP
To disable LACP mode, enter the following command in Ethernet interface view:
eth type eth [1/x]>interface-mode-set interface-mode NONE
To display an interface’s current LACP setting, enter the following command in Ethernet interface view:
eth type eth [1/x]>interface-mode-show

Configuring Split Ethernet Interface Protection Mode (CLI)

To configure split Ethernet interface protection mode:
1 Use an optical splitter to route traffic to an optical Ethernet port on each PTP 820 unit.
2 Proceed to Configuring HSB Radio Protection (CLI).

Phn 3963 013v000

Page 574
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

Configuring HSB Radio Protection (CLI)

You must perform the initial configuration of a 1+1 or 2+2 HSB system using a splitter cable for each unit to
provide a management connection to each unit. For instructions on preparing and connecting the splitter cables,
refer to the Installation Guide for PTP 820C, PTP 820C-HP or PTP 820S.
To configure HSB radio protection:
1. Before enabling protection, you must:
i. Verify that both units have the same hardware part number (see Displaying Unit Inventory (CLI)) and
the same software version (see Viewing Current Software Versions (CLI)). If the units do not have the
same software version, upgrade each unit to the most recent software release (see Configuring a
Software Download (CLI)).
ii. Assign an IP address to each unit. For instructions, see Changing the Management IP Address (CLI).
iii. Establish a management connection to one of the units. You can select either unit; once you enable
Protection Administration, the system will determine which unit becomes the Active unit.
2. To enable protection, enter the following command in root view:
root> platform management protection set admin enable
The system configures itself for HSB protection:
o The system determines which unit is the Active unit based on a number of pre-
defined criteria.
o When the system returns online, all management must be performed via the Active
unit using the IP address you defined for that unit.
o The IP address you defined for the unit which is now the Standby unit is no longer
valid, and the management port of the Standby unit becomes non-operational.
o Management of the Standby unit is performed via the Active unit, via the cable
between the two MIMO/Prot ports on the splitters connecting the two units.
o HSB protection is enabled on both units.
3. Once you have enabled Protection Admin:
i. Perform all necessary radio configurations on the Active unit, such as setting the frequency, assigning
MRMC scripts, unmuting the radio, and setting up radio groups such as XPIC or Multi-Carrier ABC
(Multi-Radio).
ii. Perform all necessary Ethernet configurations on the Active unit, such as defining Ethernet services.
iii. Enter the following command in root view to copy the configuration of the Active unit to the Standby
unit:
root> platform management protection copy-to-mate

Note
While the system is performing the copy-to-mate operation, a temporary loss of management
connection will occur.

Phn 3963 013v000

Page 575
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

To keep the Standby unit up-to-date, after any change to the configuration of the Active unit enter the copy-to-
mate command to copy the configuration to the Standby unit.
If you are unsure whether the Standby unit’s configuration matches that of the Active unit, enter the following
command in root view. The command output displays the list of mismatched parameters.
root> platform management protection show mismatch details

Configuring 2+2 HSB Protection on a PTP 820C/PTP 820C-HP

Unit (CLI)
In order to configure 2+2 HSB unit protection on a PTP 820C unit, you must simply enable the second radio carrier
on both units on both sides of the link. No other configuration is necessary other than the configuration described
above.
To enable the second radio carrier on both units using the CLI, enter the following commands in root view:
root> platform if-manager set interface-type radio slot 2 port 2 admin up

root> platform management protection copy-to-mate

Viewing the Configuration of the Standby unit (CLI)

You can view the settings of the standby unit any time.
To view the settings of the standby unit, you can run show commands in the standby unit. To do so, first enter the
mate/root context, as described in Performing CLI operations on the Standby unit (CLI), then run the relevant show
command, and then switch back to the active unit.

Editing Standby Unit Settings (CLI)

Almost all settings of the standby unit are view-only. However, several settings are editable on the Standby unit.
They must be configured separately for the Standby unit, and are not copied via copy-to-mate, nor do they trigger
a configuration mismatch in the CLI.
In the Web EMS, failure to synchronize these configuration settings causes a configuration mismatch alarm.
The following settings must be configured separately on the standby unit:
• Setting the Unit Name. Refer to the description of platform management system-name set
name in Configuring Unit Parameters (CLI).
• Disabling/enabling Radio TX-mute. Refer to the description of rf mute set admin in Muting and Unmuting
a Radio (CLI).
• Clearing the Radio and RMON counters. Refer to the description of modem clear counters in Displaying
General Modem Status and Defective Block PMs (CLI).
• Setting the activation key configuration. Refer to Mate Management Access (IP Forwarding) (CLI) and
Activating a Demo Activation Key (CLI).
• Defining user accounts. Refer to Configuring User Accounts (CLI).

Phn 3963 013v000

Page 576
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

• Setting synchronization settings. Refer to Activating a Demo Activation Key (CLI).

To configure these settings in the standby unit, first enter the mate/root context, as described in Performing CLI
operations on the Standby unit (CLI), then run the relevant commands, and then switch back to the active unit.

Performing CLI operations on the Standby unit (CLI)

You can run CLI commands in the standby unit.
To run CLI commands in the standby unit:
1. Use the following command to enter view context for the standby unit:
root> switch-to mate

mate/root>
2. Enter the specific CLI command you want to run in mate/root context.
3. To switch back to the active unit, enter the following command:
mate/root> switch-back

root>

Viewing Link and Protection Status and Activity (CLI)

You can view link and protection status and activity any time.
• To view whether HSB protection is enabled or disabled, enter the following command in root view:
root> platform management protection show admin
• To view whether HSB protection is functional (available in practice), enter the following command in root
view. Note that protection is not functional if MIMO is configured, or if the management connection to the
mate is down.
root> platform management protection show operational-state
• To view protection activity, enter the following command in root view:
root> platform management protection show activity-state
• To view the status of the protection link to the mate, enter the following command in root view:
root> platform management protection show link-status
• To view the status of the last copy-to-mate operation, enter the following command in root view:
root> platform management protection show copy-to-mate status
• To view the current lockout status, enter the following command in root view:
root> platform management protection show lockout status

Manually Switching to the Standby Unit (CLI)

The following events trigger switchover for HSB radio protection according to their priority, with the highest
priority triggers listed first.

Phn 3963 013v000

Page 577
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

1 Loss of active unit

2 Lockout
3 Radio/Ethernet interface failure
4 Manual switch
At any point, you can manually switch to the Standby unit, provided that the highest protection fault level in the
Standby unit is no higher than the highest protection fault level on the Active unit.
To manually switchover to the Standby unit enter the following command in root view:
root> platform management protection set manual-switch

Disabling Automatic Switchover to the Standby Unit (CLI)

At any point, you can perform lockout, which disables automatic switchover to the standby unit.
To disable automatic switchover to the Standby unit, use the following command in root view:
root> platform management protection lockout set admin on
To re-enable automatic switchover to the standby unit, use the following command in root view:
root> platform management protection lockout set admin off

Disabling Unit Protection (CLI)

You can disable unit protection at any time. If you disable unit protection, keep in mind that while the unit that
was formerly the active unit maintains its IP address, the unit that was formerly the standby unit is assigned the
default IP address (192.168.1.1)
To disable protection, enter the following command in root view.
root> platform management protection set admin disable

Configuring 1+1 HSB with Space Diversity (CLI)

Note
This feature is only relevant for PTP 820C. it can be used with all PTP 820C hardware versions.

A 1+1 HSB-SD configuration utilizes two PTP 820C units on each side of the link, with both radio carriers activated.
The PTP 820C units are combined and connected to the primary and diversity antennas via a dual coupler and two
flexible waveguides.
Radio carrier 2 is muted on each unit. On the receiving side, the signals are combined in the active unit to produce
a single, optimized signal. The link is protected via external protection, so that if a protection switchover occurs,
the standby unit becomes the active unit, and the link continues to function with full space diversity.
To configure a 1+1 HSB link with Space Diversity:
1. For one PTP 820C unit, enter the following command in root view to create a Space Diversity group:

Phn 3963 013v000

Page 578
Chapter 14: Configuration Guide (CLI) Configuring Unit Protection with HSB Radio Protection
(External Protection) (CLI)

root> radio mimo create group 1 mimo-type 1-plus-0-sd radio 2 port 1

radio 2 port 2
2. Enter the following command in root view to enable the Space Diversity group:
root> radio mimo set-admin group 1 admin enable
3. Repeat Steps Error! Reference source not found. and Error! Reference source not found. for the second unit.

Note
The identity of the active and standby units is not determined until unit protection is configured.

4. Configure Unit Protection, according to the instructions in Configuring Unit Protection with HSB Radio
Protection (External Protection) (CLI)
5. on the active PTP 8200 unit, mute the transmitter of radio carrier2. For instructions, see Muting and Unmuting
a Radio (CLI).
6. Perform Copy to Mate. See Step 3 in Configuring HSB Radio Protection (CLI)

Note
It is crucial to ensure that the port connected to the Diversity antenna is muted in each PTP 820 unit.
If you perform Copy to Mate after configuring unit protection, as indicated above, the mute
configuration will be copied to the standby unit. If you mute the interface before configuring unit
protection, you must make sure to manually mute the interface on both PTP 820 units. Otherwise,
configuring unit protection will override the mute configuration.

Phn 3963 013v000

Page 579
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

Configuring MIMO and Space Diversity (CLI)

Note
This feature is only relevant for PTP 820C and PTP 820C-HP units.

This section describes how to configure MIMO and space diversity, and include the following topics:
• MIMO and Space Diversity Overview (CLI)
• Upgrading a 4x4 MIMO Link from an Earlier Version to System release 10.5 or Higher (CLI)
• Configuring a 4x4 MIMO Link (CLI)
• Configuring a 2x2 MIMO Link (CLI)
• Configuring a 1+0 or 2+2 Space Diversity Link (CLI)
• Viewing MMI Levels (CLI)
• Deleting a 4x4 MIMO Group (CLI)
• Deleting a 2x2 MIMO or Space Diversity Group (CLI)

MIMO and Space Diversity Overview (CLI)

Note
MIMO and Space Diversity are not supported with ATPC. ATPC must be disabled before configuring
ASD. See Configuring ATPC and ATPC Override Timer (CLI).

Line-of-Sight (LoS) Multiple Input Multiple Output (MIMO) achieves spatial multiplexing by creating an artificial
phase de-correlation by deliberate antenna distance at each site in deterministic constant distance. At each site in
a LoS MIMO configuration, data to be transmitted over the radio link is split into two bit streams (MIMO 2x2) or
four bit streams (MIMO 4x4). These bit streams are transmitted via two antennas. In MIMO 2x2, the antennas use
a single polarization. In MIMO 4x4, each antenna uses dual polarization. The phase difference caused by the
antenna separation enables the receiver to distinguish between the streams.
PTP 820C supports both 2x2 MIMO and 4x4 MIMO. For a full explanation of MIMO support in PTP 820C, refer to
thePTP 820C Technical Description.
For 4x4 MIMO using an external switch operating in LAG mode, Mate Management Access enables users to
manage both units via in-band management. See Mate Management Access (IP Forwarding) (CLI).
For PTP 820C 2E2SX hardware models, if you try to apply a 4x4 MIMO or 2+2 Space Diversity configuration while
P4 is assigned one or more service points, ASP or LLF instances, or a LAG group or Sync source is configured on P4,
the configuration will fail and an error message will be generated. Also, the Admin status of the port must be set
to Down before applying the 4x4 MIMO or 2+2 Space Diversity configuration. See Enabling the Interfaces (CLI).
The same hardware configurations can also be used to implement BBS Space Diversity. PTP 820C and PTP 820C-HP
support 1+0 and 2+2 Space Diversity. For a full explanation of Space Diversity support in PTP 820C and PTP 820C-
HP, refer to the Technical Description for the product and system release version you are using.

Phn 3963 013v000

Page 580
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

2+2 HSB Space Diversity provides both equipment protection and signal protection. If one unit goes out of service,
the other unit takes over and maintains the link until the other unit is restored to service and Space Diversity
operation resumes.
2+2 HSB Space Diversity utilizes two PTP 820C units operating in dual core mode. In each PTP 820C unit, both radio
carriers are connected to a single antenna. One optical GbE port on each PTP 820C is connected to an optical
splitter. Traffic must be routed to an optical GbE port on each PTP 820C unit.
In effect, a 2+2 HSB configuration is a protected 2+0 Space Diversity configuration. Each PTP 820C monitors both of
its cores. If the active PTP 820C detects a radio failure in either of its cores, it initiates a switchover to the standby
PTP 820C.

Note
Only one MIMO or Space Diversity group can be created per PTP 820C or PTP 820C-HP unit. All
MRMC scripts that support MIMO also support Space Diversity.

For 4x4 MIMO links, system release is not interoperable with earlier System release versions. If
you are upgrading from an earlier version with an existing 4x4 MIMO link, you must follow the
procedure in Upgrading a 4x4 MIMO Link from an Earlier Version to system release 10.5 or Higher
(CLI).

Upgrading a 4x4 MIMO Link from an Earlier Version to System

Release 10.5 or Higher (CLI)
For 4x4 MIMO links, system release 10.5 and higher are not interoperable with earlier system release. When
upgrading from a system release prior to system release 10.5 to system release 10.5 or higher, if there is an
existing 4x4 MIMO link, you must perform either of the following procedures to properly upgrade the link. Option
1 is the preferred option.

Note
You must download the new system release software package to all four units before beginning
the upgrade process. All four units in the 4x4 MIMO link must use the same system release build
and version.

Upgrade Procedure – Option 1

1. Upgrade the remote Slave unit.
2. Upgrade the remote Master unit.
3. Upgrade the local Slave unit.
4. Upgrade the local Master unit.
Upgrade Procedure – Option 2
1. Upgrade the remote Master unit.
2. Upgrade the local Slave unit.
3. Upgrade the local Master unit.
4. Wait for the link to be restored between the Master units.
5. Mute both radio carriers on the remote Slave unit.
6. Upgrade the remote Slave unit.

Phn 3963 013v000

Page 581
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

7. Unmute both radio carriers on the remote Slave unit.

Configuring a 4x4 MIMO Link (CLI)

To configure a MIMO link, you must perform the following steps:
To configure a MIMO link, you must perform the following steps:
1 Verify that the following three cables are connected between the Master and Slave PTP 820C units on each side
of the link. For details, refer to the PTP 820C Installation Guide or the PTP 820C-HP Installation Guide:
◦ Source sharing cable between both EXT REF PTP 820 radio connectors.
◦ MIMO data sharing cable between both PTP 820 ETH3/EXT ports.
◦ MIMO signaling cable between both PTP 820 MGT/PROT ports.
2 Configure the PTP 820 carriers as XPIC links, using XPIC scripts, and configuring the carriers as XPIC groups. See
Configuring XPIC (CLI).
3 Perform antenna alignment for XPIC. See Performing Antenna Alignment for XPIC (CLI).
4 Configure MIMO groups on each PTP 820C unit, in the following order:
i Upper unit (Master) on the local side of the link.
ii Upper unit (Master) on the remote side of the link.
iii Lower unit (Slave) on the local side of the link.
iv Lower unit (Slave) on the remote side of the link.
To configure a 4x4 MIMO group, enter the following commands:
i Enter the following command in root view to create the group:
root> amcc create group group_id <1-4> group_type mimo_4x4 group_sub_type
external
ii Enter the following command to go into group view:
root> amcc group group_id <1-4> group_type mimo_4x4

mimo-4X4-group[x]:
iii In group view, enter the following commands to add the unit’s two carriers to the group:
mimo-4X4-group[x]> amcc attach slot 2 port 1 role <mimo-master|mimo-
slave>
mimo-4X4-group[x]> amcc attach slot 2 port 2 role <mimo-master|mimo-
slave>
iv In group view, enter the following command to enable the group:
mimo-4X4-group[x]> set admin enable
Note: To display details about the group, enter the following command in root view:

root> amcc show group_id <1-4> group_type mimo_4x4

The following commands configure a Master group on Unit 1 and a Slave group on Unit 2:

Phn 3963 013v000

Page 582
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

Unit 1
root> amcc create group group_id 1 group_type mimo_4x4 group_sub_type
external

group_id 1, group_type mimo-4x4 created

root> amcc group group_id 1 group_type mimo_4x4

mimo-4X4-group[1]> amcc attach slot 2 port 1 role mimo-master

mimo-4X4-group[1]> amcc attach slot 2 port 2 role mimo-master

mimo-4X4-group[1]> set admin enable

Unit 2
root> amcc create group group_id 1 group_type mimo_4x4 group_sub_type
external

group_id 1, group_type mimo-4x4 created

root> amcc group group_id 1 group_type mimo_4x4

mimo-4X4-group[1]> amcc attach slot 2 port 1 role mimo-slave

mimo-4X4-group[1]> amcc attach slot 2 port 2 role mimo-slave

mimo-4X4-group[1]> set admin enable

5 Verify that the MMI and XPIC levels are appropriate. See Viewing MMI Levels (CLI).
6 Configure LAG on the two Ethernet ports of the external switches connected to the PTP 820C units on both
sides of the link.
7 Configure Automatic State Propagation with ASP trigger by remote fault enabled on the MIMO group in all
four PTP 820 units that make up the link. See Configuring Automatic State Propagation and Link Loss
Forwarding (CLI).

Note
The last two steps are crucial to ensure that the link continues to function via the MIMO
resiliency mechanism in the event of a hardware failure scenario.

Figure 136 shows one side of a 4x4 MIMO link.

Configuring a 2x2 MIMO Link (CLI)

1 Create a 2x2 MIMO group by entering the following command in root view:
root> radio mimo create group <1-4> mimo-type mimo-2x2 radio 2 port
<first radio carrier in the group: either 1 or 2> radio 2 port <second
radio carrier in the group: either 2 or 1>
2 Enable the group by entering the following command in root view:
root > radio mimo set-admin group <1-4> admin enable
To reset MIMO, enter the following command in root view:
root > radio mimo reset group 1
3 Verify that the XPIC levels are appropriate. See Viewing MMI Levels (CLI).

Phn 3963 013v000

Page 583
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

Note
XPI is not relevant for 2x2 MIMO.

Configuring a 1+0 or 2+2 Space Diversity Link (CLI)

1 Create a Space Diversity group by entering the following command in root view:
root> radio mimo create group 1 mimo-type <mimo-type> radio 2 port <first
radio carrier in the group: either 1 or 2> radio 2 port <second radio
carrier in the group: either 2 or 1 >
where <mimo-type> defines the Space Diversity configuration. The options are:
◦ 1-plus-0-sd – 1+0 Space Diversity.
◦ 2-plus-0-sd – 2+0 Space Diversity.
2 Enable the group by entering the following command in root view:
root > radio mimo set-admin group <1-4> admin enable
3 For 2+2 Space Diversity configurations, you must set the role of the group to Master or Slave. This determines
the role of the PTP 820 unit in the overall Space Diversity configuration.
To set the role of a MIMO or Space Diversity group, enter the following command in root view:
root > radio mimo set-role group <1-4> mimo-role <slave|master>

Viewing MMI Levels (CLI)

You can view MMI levels for the individual radio carriers in a MIMO group.
Note that the MMI value can also be calculated manually. To calculate it manually, you must measure the
following RSL levels per receiver:
1 Mute all remote transmitters except the transmitter for the link you want to measure, and measure the local
RSL level (RSL_Wanted).
2 Mute all remote transmitters except the same polarization interferer and measure the local RSL2 (RSL_Int).
3 The MMI is equal to RSL_Wanted – RSL_Int.
To show the status of a MIMO group, as well as the MMI and XPI levels for the individual radio carriers, enter the
following command:
root > radio mimo show status group 1
The following is a sample output from this command:

Phn 3963 013v000

Page 584
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

root> radio mimo show status group 1

MIMO group type: mimo-4x4.

MIMO group 1st member: slot 2 port 1.
MIMO group 2nd member: slot 2 port 2.
MIMO group admin status: disable.
MIMO state: MIMO-Disabled.
MIMO advanced state: disabled.
MIMO RFU role: slave.
MIMO 1st carrier MMI: -0.0
MIMO 2nd carrier MMI: -0.0
MIMO 1st carrier XPI: 99.0
MIMO 2nd carrier XPI: 99.0

Table 103: MMI and XPI Levels CLI Parameters

Parameter Input Type
MIMO group type The MIMO or Space Diversity configuration:
• mimo-2x2 – 2x2 MIMO.
• mimo-4x4 – 4x4 MIMO.
• 1-plus-0-sd – 1+0 BBS Space Diversity.
• 2-plus-0-sd – 2+0 XPIC with BBS Space
Diversity.

MIMO group 1st member The first radio carrier in the group.

MIMO group 2nd member The second radio carrier in the group.

MIMO group admin status Indicates whether the MIMO group is enabled or
disabled.

MIMO state Indicates whether MIMO is enabled or disabled.

MIMO advanced state A detailed description of the MIMO state.

MIMO RFU role Indicates the role of the unit in the MIMO
configuration (Master or Slave).

MIMO 1st carrier MMI MIMO Mate Interference for the first group
member. MMI represents the difference between
the RSL1 and the RSL2 of the remote Master and
Slave transmitters with the same polarization. The
nominal range is 0. The range should be from -3
dB to +3 dB.
MMI is not relevant for 1+0 Space Diversity.

MIMO 2nd carrier MMI MMI for the second group member.

MIMO 1st carrier XPI Cross Polarization Interference for the first group
member. This is only relevant in 4x4 MIMO
configurations, where each unit operates in dual
polarization (XPIC) mode. The XPI value should be
at least 25 dB. For further information, refer to
Configuring XPIC (CLI).

Phn 3963 013v000

Page 585
Chapter 14: Configuration Guide (CLI) Configuring MIMO and Space Diversity (CLI)

Parameter Input Type

MIMO 2nd carrier XPI XPI for the second group member.

Deleting a 4x4 MIMO Group (CLI)

To delete a 4x4 MIMO Group:
1 Enter the following command to go into group view:
root> amcc group group_id <1-4> group_type mimo_4x4

mimo-4X4-group[x]:
2 In group view, enter the following commands to remove the unit’s two carriers from the group:
mimo-4X4-group[x]> amcc detach slot 2 port 1
mimo-4X4-group[x]> amcc detach slot 2 port 2
3 In group view, enter the following command to disable the group:
mimo-4X4-group[x]> set admin disable
4 In root view, enter the following command to delete the group:
root> amcc delete group group_id <1-4> group_type mimo_4x4

Deleting a 2x2 MIMO or Space Diversity Group (CLI)

You can delete a 2x2 MIMO or Space Diversity Group.
To delete a 2x2 MIMO or Space Diversity Group:
1 Before deleting a MIMO or Space Diversity group, you must first disable the group using the following
command in root view:
root > radio mimo set-admin group 1 admin disable
Note: When the MIMO or Space Diversity group is disabled, the system is
automatically reset.
2 Delete the MIMO or Space Diversity group by entering the following command in root view:
root > radio mimo delete group 1

Phn 3963 013v000

Page 586
Chapter 14: Configuration Guide (CLI) Configuring Advanced Space Diversity (ASD) (CLI)

Configuring Advanced Space Diversity (ASD) (CLI)

Note: This feature is only relevant for PTP 820C and PTP 820C-HP.

This section describes how to configure Advanced Space Diversity (ASD), and includes the following topics:
• Configuring an ASD Link (CLI)
• Viewing ASD Status (CLI)
• Deleting an ASD Group (CLI)

Note: For an overview of ASD, see ASD Overview.

Configuring an ASD Link (CLI)

Note: ASD is not supported with ATPC and XPIC. ATPC and XPIC must both be disabled before
configuring ASD. See Error! Reference source not found. and Error! Reference source not found..

To configure an ASD link, you must perform the following steps:

1 Install the PTP 820C or PTP 820C-HP units as follows:
• At Site 1, install two PTP 820C/PTP 820C-HP units in a 4x4 MIMO configuration.
• At Site 2, install one PTP 820C/PTP 820C-HP unit in a 2+0 Dual Polarization (XPIC) configuration.
For instructions, refer to the Installation Manual for PTP 820C or PTP 820C-HP.
2 Verify that the Ethernet interfaces on the Slave unit are set to Admin = Down in the Interface Manager. See
Error! Reference source not found..
3 Configure the radio parameters for each of the six radio carriers in the link. Make sure each carrier is
configured with the same radio parameters. See Error! Reference source not found..
4 Assign an ASD script to each of the six radio carriers in the link. Options are:
• MRMC Script 1951 (28/30 MHz)
• MRMC Script 1953 (56/60 MHz)
See Error! Reference source not found..

Note: Make sure to set the same MRMC parameters for all the radio carriers in the ASD
link. For ASD, the scripts must be set to Adaptive mode.

5 Mute both carriers on the Slave unit. See Error! Reference source not found..
6 Align the antenna of the Master unit to the antenna at Site 2 until you achieve a steady link at the RSL that is
expected according to the site plan, at 2048 QAM.
7 Unmute the carriers of the Slave unit and mute both carriers on the Master unit. See Error! Reference source
not found..

Phn 3963 013v000

Page 587
Chapter 14: Configuration Guide (CLI) Configuring Advanced Space Diversity (ASD) (CLI)

8 Align the antenna of the Slave unit to the antenna at Site 2 until you achieve a steady link at the RSL that is
expected according to the site plan, at 2048 QAM.
9 Unmute the carriers of the Master unit. At this point, all of the carriers in the ASD link should be unmuted.
10 Create an ASD group on each unit:
• To create an ASD group at Site 1 (two units), enter the following command in root view:
root> amcc create group group_id <1-4> group_type dual-asd group_sub_type
asd-2+0
• To create an ASD group at Site 2 (one unit), enter the following command in root view:
root> amcc create group group_id <1-4> group_type single-asd
group_sub_type asd-2+0
11 Enter group view:
• Use the following command to enter group view at Site 1 (two units):
root>amcc group group_ id <1-4> group_type dual-asd
dual-asd-group[1]>
• Use the following command to enter group view at Site 1 (two units):
root>amcc group group_id <1-4> group_type single-asd
single-asd-group[1]>
12 In group view, add members and set the unit’s role (Master or Slave):
• Use the following commands to add members and set the group’s role for the Master unit at Site 1:
dual-asd-group[1]>amcc attach slot 2 port 1 role master
dual-asd-group[1]>amcc attach slot 2 port 2 role master
• Use the following commands to add members and set the group’s role for the Slave unit at Site 1:
dual-asd-group[1]>amcc attach slot 2 port 1 role slave
dual-asd-group[1]>amcc attach slot 2 port 2 role slave
• Use the following commands to add members and set the group’s role for the unit at Site 2:
single-asd-group[1]>amcc attach slot 2 port 1 role master
single-asd-group[1]>amcc attach slot 2 port 2 role master
13 In group view, enter the following command to enable the group:
dual|single-asd-group[1]>set admin enable
To display details about the group at Site 1 enter the following command in root view:
root>amcc show group_id 1 group_type dual-asd
To display details about the group at Site 2 enter the following command in root view:
root>amcc show group_id 1 group_type single-asd
The following commands configure an ASD link:
Site 1, Unit 1 (Master)
root>amcc create group group_id 1 group_type dual-asd group_sub_type asd-2+0
group_id 1, group_type dual-asd created

root>amcc group group_id 1 group_type dual-asd

dual-asd-group[1]>

dual-asd-group[1]>amcc attach slot 2 port 1 role master

slot 2 port 1 role master attached to group_id 1 group_type dual-asd

Phn 3963 013v000

Page 588
Chapter 14: Configuration Guide (CLI) Configuring Advanced Space Diversity (ASD) (CLI)

dual-asd-group[1]>amcc attach slot 2 port 2 role master

slot 2 port 2 role master attached to group_id 1 group_type dual-asd

dual-asd-group[1]>set admin enable

group_id 1 group_type dual-asd 'Admin Enabled'

dual-asd-group[1]>
Site 1, Unit 2
root>amcc create group group_id 1 group_type dual-asd group_sub_type asd-2+0
group_id 1, group_type dual-asd created

root>amcc group group_id 1 group_type dual-asd

dual-asd-group[1]>

dual-asd-group[1]>amcc attach slot 2 port 1 role slave

slot 2 port 1 role slave attached to group_id 1 group_type dual-asd

dual-asd-group[1]>amcc attach slot 2 port 2 role slave

slot 2 port 2 role slave attached to group_id 1 group_type dual-asd

dual-asd-group[1]>set admin enable

group_id 1 group_type dual-asd 'Admin Enabled'

dual-asd-group[1]>
Site 2 (Master)
root>amcc create group group_id 1 group_type single-asd group_sub_type asd-2+0
group_id 1, group_type single-asd created

root>amcc group group_id 1 group_type single-asd

single-asd-group[1]>

single-asd-group[1]>amcc attach slot 2 port 1 role master

slot 2 port 1 role master attached to group_id 1 group_type single-asd

single-asd-group[1]>amcc attach slot 2 port 2 role master

slot 2 port 2 role master attached to group_id 1 group_type single-asd

single-asd-group[1]>set admin enable

group_id 1 group_type single-asd 'Admin Enabled'

single-asd-group[1]>

Viewing ASD Status (CLI)

To view BBC Space Diversity status, enter the following command in group view:
dual-asd-group[x]>show members
For each member of the group, the command displays the member’s role (master or slave) and state:
• Idle – All units are operational.
• Master Only – The Slave unit is not operational.
• ASD Configuration not supported – The link has been misconfigured. Make sure that each radio carrier is
configured with the same radio parameters and MRMC scripts and parameters.
For master units only, the command also displays the status of the ASD group’s received radio signal:
• Combined – Only relevant for the Master unit at the dual-unit side of the link. ASD is functioning to
produce a combined radio signal.

Phn 3963 013v000

Page 589
Chapter 14: Configuration Guide (CLI) Configuring Advanced Space Diversity (ASD) (CLI)

• Main Only – Only relevant for Master units. Only the main path signal is being received.
• Diversity Only – Only relevant for Slave units and the Master unit at the single-unit side of the link. Only
the diversity path is providing a usable signal.
• N/A – No adequate signal is being received, either because of an LOF condition or misconfiguration of the
link.
For example:
Dual-asd-group[1]>show members
slot 2 port 1 role master state Idle Combined Combined
slot 2 port 2 role master state Idle Combined Combined
You can also display the status of the ASD group’s received radio signal, but you must do so via the Web EMS. See
Viewing ASD Status.

Deleting an ASD Group (CLI)

To delete an ASD group, you must perform the following steps:
1 In group view, enter the following command to disable the group. When you execute the command, the unit is
automatically reset.
dual|single-asd-group[1]>set admin disable
2 Once the unit comes back online, enter group view and enter the following commands to remove the members
from the group:
dual|single-asd-group[1]> amcc detach slot 2 port 1
dual|single-asd-group[1]> amcc detach slot 2 port 2
3 In root view, enter the following command to delete the group:
root> amcc delete group group_id <1-4> group_type
<single asd|dual-asd>
The following sequence of commands disables the ASD group at one of the units at Site 1:
root>amcc group group_id 1 group_type dual-asd
dual-asd-group[1]>

dual-asd-group[1]>set admin disable

Power UP reset after 10 seconds...
group_id 1 group_type dual-asd 'Admin Disabled'
dual-asd-group[1]>

Broadcast message from root@hostname (console) (Sun May 7 23:10:01

2000):

The system is going down for reboot NOW!

root>amcc group group_id 1 group_type dual-asd

dual-asd-group[1]>

dual-asd-group[1]>amcc detach slot 2 port 1

slot 2 port 1 detached from group_id 1 group_type dual-asd

dual-asd-group[1]>amcc detach slot 2 port 2

slot 2 port 2 detached from group_id 1 group_type dual-asd

dual-asd-group[1]>exit
root>

Phn 3963 013v000

Page 590
Chapter 14: Configuration Guide (CLI) Configuring Advanced Space Diversity (ASD) (CLI)

root>amcc delete group group_id 1 group_type dual-asd

group_id 1 group_type dual-asd deleted

root>

Phn 3963 013v000

Page 591
Chapter 14: Configuration Guide (CLI) Configuring Advanced Frequency Reuse (AFR) (CLI)

Configuring Advanced Frequency Reuse (AFR) (CLI)

For a general description of AFR, see AFR Overview.

Initial Link Configuration and Alignment for AFR (CLI)

Before performing the software configuration for AFR, you must set up and align the two links as individual 1+0
links. For instructions, see Initial Link Configuration and Alignment for AFR.

Software Configuration for AFR (CLI)

Note
AFR is not supported with ATPC. ATPC should be disabled before configuring AFR. See Configuring
ATPC and ATPC Override Timer (CLI).

Perform the following steps for each site in the AFR configuration.
• If you are performing the configuration locally at the Hub site and each Tail site, the order in which you
configure the sites does not matter.
• If you are performing the configuration for all three sites remotely from the Hub Site, you must configure the
sites in the following order:
o Tail Site 1
o Tail Site 2
o Hub Site
After you configure AFR on the Tails Sites, the link between the Hub Site and the Tail Sites will be lost. The
links will be restored after you configure AFR on the Hub site and the Hub site comes back up after unit reset.
1. Create an AFR group by entering on of the following commands in root view:
If you are configuring the Hub site, enter the following command:
root> amcc create group group_id 1 group_type afr-agg group_sub_type
internal
If you are configuring a Tail site, enter the following command:
root>amcc create group group_id 1 group_type afr-tail group_sub_type
internal
2. Enter AMCC Group view by entering the following command in root view:
root> amcc group group_id 1
group [1]>
3. Assign a role to each radio interface, as follows:
If you are configuring the Hub site, enter the following command in group view for each radio interface:
group [1]> amcc attach slot 2 port <1|2> role <agg-1|agg-2>
If you are configuring a Tail site, enter the following command in group view:

Phn 3963 013v000

Page 592
Chapter 14: Configuration Guide (CLI) Configuring Advanced Frequency Reuse (AFR) (CLI)

group [1]> amcc attach slot 2 port <1|2> role <tail-1|tail-2>

Make sure the interface you configure as agg-1 is part of the link with tail-1 and that the interface you
configure as agg-2 is part of the link with tail-2.
4. Enter the following command to enable the group. When you execute the command, the unit is automatically
reset.
group [1]> amcc set enable
Once AFR has been configured on the Hub site and both Tail sites, the configuration is complete.
To display the current AFR configuration, enter the following command in root view:
root> amcc show
The following sequence of commands enables AFR at the Hub site, in a configuration where radio interface 1 is
Aggregator 1, connected to Tail Site 1, and radio interface 2 is Aggregator 2, connected to Tail Site 2:
root> amcc create group group_id 1 group_type afr-agg group_sub_type
internal
root> amcc group group_id 1
group[1]> amcc attach slot 2 port 1 role agg-1
group [1]> amcc set enable
The following sequence of commands enables AFR at Tail Site 1:
root> amcc create group group_id 1 group_type afr-tail group_sub_type
internal
root> amcc group group_id 1
group[1]> amcc attach slot 2 port 1 role tail-1
group [1]> amcc set enable
The following sequence of commands enables AFR at Tail Site 2:
root> amcc create group group_id 1 group_type afr-tail group_sub_type
internal
root> amcc group group_id 1
group[1]> amcc attach slot 2 port 1 role tail-2
group [1]> amcc set enable

Deleting an AFR Group (CLI)

If you want to disable AFR and convert the two links into non-AFR links, you must perform the following steps for
each site in the AFR configuration. If you are managing the links by in-band management from the hub site, you
must disable AFR at the tail sites first, then disable AFR at the hub site. Once AFR has been disabled at all of the
sites, you can delete the AFR groups in any order.
1. Enter AMCC Group view by entering the following command in root view:
root> amcc group group_id 1
group [1]>
2. Enter the following command to disable the group. When you execute the command, the unit is automatically
reset.
group [1]> amcc set disable
3. Detach the radio interface from the group. If you are disabling AFR at the Hub site, detach both interfaces. To
detach an interface from the group, enter the following command in root view for each interface:

Phn 3963 013v000

Page 593
Chapter 14: Configuration Guide (CLI) Configuring Advanced Frequency Reuse (AFR) (CLI)

group [1]> amcc detach slot 2 port <port>

4. Exit group view and enter the following command in root view to delete the group:
root> amcc delete group group_id 1
Once you have performed this procedure for the Hub site and both Tail sites, you can reconfigure the links
according to the new network plan.
The following sequence of commands disables AFR at the Hub site:
root> amcc group group_id 1
group[1]> amcc set disable
group[1]> amcc detach slot 2 port 1
slot 2 port 1 detached from group_id 1
group[1]> amcc detach slot 2 port 2
slot 2 port 2 detached from group_id 1
group[1]> exit
root> amcc delete group group_id 1
group_id 1 deleted

Phn 3963 013v000

Page 594
Chapter 14: Configuration Guide (CLI) Operating a PTP 820C/PTP 820C-HP in Single Radio Carrier
Mode (CLI)

Operating a PTP 820C/PTP 820C-HP in Single Radio

Carrier Mode (CLI)

If you wish to operate a PTP 820C unit in single radio carrier mode, you must perform the following steps:
1. Verify that XPIC is disabled. See Configuring XPIC (CLI)
2. Disable Multi-Carrier ABC, as described in Deleting a Multi-Carrier ABC Group (CLI)
3. Disable one of the two radio interfaces, as described in Enabling the Interfaces (CLI)
4. Mute the disabled radio interface, as described in Muting and Unmuting a Radio (CLI)

Phn 3963 013v000

Page 595
Chapter 15: Unit Management (CLI) Operating a PTP 820C/PTP 820C-HP in Single Radio Carrier
Mode (CLI)

Chapter 15: Unit Management (CLI)

This section includes:
• Defining the IP Protocol Version for Initiating Communications (CLI)
• Configuring the Remote Unit’s IP Address (CLI)
• Configuring SNMP (CLI)
• Configuring the Internal Ports for FTP or SFTP (CLI)
• Upgrading the Software (CLI)
• Backing Up and Restoring Configurations (CLI)
• Setting the Unit to the Factory Default Configuration (CLI)
• Performing a Hard (Cold) Reset (CLI)
• Configuring Unit Parameters (CLI)
• Configuring NTP (CLI)
• Displaying Unit Inventory (CLI)
• Displaying SFP DDM and Inventory Information (CLI)

Related topics:
• Setting the Time and Date (Optional) (CLI)
• Uploading Unit Info (CLI)
• Changing the Management IP Address (CLI)

Phn 3963 013v000

Page 596
Chapter 15: Unit Management (CLI) Defining the IP Protocol Version for Initiating Communications
(CLI)

Defining the IP Protocol Version for Initiating

Communications (CLI)

You can specify which IP protocol the unit will use when initiating communications, such as downloading software,
sending traps, pinging, or exporting configurations. The options are IPv4 or IPv6.
To define which IP protocol the unit will use when initiating communications, enter the following command in root
view:
root> platform management ip set ip-address-family <ipv4|ipv6>
To show the IP protocol version the unit will use when initiating communications, enter the following command in
root view:
root> platform management ip show ip-address-family

Phn 3963 013v000

Page 597
Chapter 15: Unit Management (CLI) Configuring the Remote Unit’s IP Address (CLI)

Configuring the Remote Unit’s IP Address (CLI)

You can configure the remote unit’s IP address, subnet mask and default gateway in IPv4 format and/or in IPv6
format. The remote unit will receive communications whether they were sent to its IPv4 address or its IPv6
address.

Configuring the Remote Radio's IP Address in IPv4 format (CLI)

To set the remote radio’s IP Address, enter the following command in radio view:
radio[x/x]>remote-unit set ip-address <ipv4-address>
To display the remote radio’s IP Address, enter the following command in radio view:
radio[x/x]>remote-unit show ip-address
To set the remote radio’s subnet mask, enter the following command in radio view:
radio[x/x]>remote-unit set subnet-mask IP <subnet-mask>
To display the remote radio’s subnet mask, enter the following command in radio view:
radio[x/x]>remote-unit show subnet-mask
To set the remote radio’s default gateway, enter the following command in radio view:
radio[x/x]>remote-unit set default-gateway IP <ipv4-address>
To display the remote radio’s default gateway, enter the following command in radio view:
radio[x/x]>remote-unit show default-gateway

Table 104 Remote Unit IP Address (IPv4) CLI Parameters

Parameter Input Type Permitted Values Description

ipv4-address Dotted decimal format. Any valid IPv4 address. Sets the default gateway or IP
address of the remote radio.

subnet-mask Dotted decimal format. Any valid subnet mask. Sets the subnet mask of the
remote radio.

Examples
The following command sets the default gateway of the remote radio as 192.168.1.20:
radio[2/1]>remote-unit set default-gateway IP 192.168.1.20
The following commands set the IP address of the remote radio as 192.168.1.1, with a subnet mask of
255.255.255.255.
radio[2/2]>remote-unit set ip-address 192.168.1.1

radio[2/2]>remote-unit set subnet-mask IP 255.255.255.255

Phn 3963 013v000

Page 598
Chapter 15: Unit Management (CLI) Configuring the Remote Unit’s IP Address (CLI)

Configuring the Remote Radio's IP Address in IPv6 format (CLI)

To set the remote radio’s IP Address, enter the following command in radio view:
radio[x/x]>remote-unit set ip-address-ipv6 <ipv6-address>
To display the remote radio’s IP Address, enter the following command in radio view:
radio[x/x]>remote-unit show ip-address-ipv6
To set the remote radio’s prefix length , enter the following command in radio view:
radio[x/x]>remote-unit set prefix-length <prefix-length >
To display the remote radio’s prefix-length, enter the following command in radio view:
radio[x/x]>remote-unit show prefix-length
To set the remote radio’s default gateway, enter the following command in radio view:
radio[x/x]>remote-unit set default-gateway-ipv6 IPv6 <ipv6-address>
To display the remote radio’s default gateway, enter the following command in radio view:
radio[x/x]>remote-unit show default-gateway-ipv6

Table 105 Remote Unit IP Address (IPv6) CLI Parameters

Parameter Input Type Permitted Values Description

ipv6-address Eight groups of four Any valid IPv6 address. Sets the default gateway or IP
hexadecimal digits address of the remote radio.
separated by colons.

prefix-length Number 1-128 Sets the prefix length of the

remote radio.
It should be different for each
RADIUS client.

Examples
The following command sets the default gateway of the remote radio as
FE80:0000:0000:0000:0202:B3FF:FE1E:8329 :
radio[2/1]>remote-unit set default-gateway-ipv6 IPv6
FE80:0000:0000:0000:0202:B3FF:FE1E:8329
The following commands set the IP address of the remote radio as FE80:0000:0000:0000:0202:B3FF:FE1E:8329,
with a prefix length of 64:
radio[2/2]>remote-unit set ip-address-ipv6
FE80:0000:0000:0000:0202:B3FF:FE1E:8329

radio[2/2]>remote-unit set prefix-length 64

Phn 3963 013v000

Page 599
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

Configuring SNMP (CLI)

PTP 820 supports SNMP v1, V2c, and v3. You can set community strings for access to PTP 820 units.
PTP 820supports the following MIBs:
• RFC-1213 (MIB II).
• RMON MIB.
• Proprietary MIB.
Access to the unit is provided by making use of the community and context fields in SNMPv1 and
SNMPv2c/SNMPv3, respectively.
This section includes:
• Configuring Basic SNMP Settings (CLI)
• Configuring SNMPv3 (CLI)
• Displaying the SNMP Settings (CLI)
• Configuring Trap Managers (CLI)

Configuring Basic SNMP Settings (CLI)

To enable SNMP, enter the following command in root view:
root> platform security protocols-control snmp admin set <admin>
To specify the SNMP version, enter the following command in root view:
root> platform security protocols-control snmp version set <version>
To specify the SNMP read and write communities, enter the following command in root view:
root> platform security protocols-control snmpv1v2 set read-community
<read-community> write-community <write-community>

Note
Additional security parameters can be configured in the Quick Configuration Security Protocols page.
See Quick Security Configuration – Protocols Page, Step 4.

Table 106 Basic SNMP CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable enable Select enable to enable SNMP

disable monitoring, or disable to
disable SNMP monitoring.

version Variable v1 Specifies the SNMP version.

v2
v3

Phn 3963 013v000

Page 600
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

Parameter Input Type Permitted Values Description

read- Text String Any valid SNMP read The community string for the
community community. SNMP read community.

write- Text String Any valid SNMP write The community string for the
community community. SNMP write community.

Example
The following commands enable SNMP v2 on the unit, and set the read community to “public” and the write
community to “private”:
root> platform security protocols-control snmp admin set enable

root> platform security protocols-control snmp version set v2

root> platform security protocols-control snmpv1v2 set read-community

public write-community private

Configuring SNMPv3 (CLI)

The following commands are relevant for SNMPv3.
To block SNMPv1 and SNMPv2 access so that only SNMPv3 access will be enabled, enter the following command in
root view:
root> platform security protocols-control snmp v1v2-block set <set-block>
To add an SNMPv3 user, enter the following command in root view:
root> platform security protocols-control snmp v3-authentication add v3-
user-name <v3-user-name> v3-user-password <v3-user-password> v3-security-
mode <v3-security-mode> v3-encryption-mode <v3-encryption-mode> v3-auth-
algorithm <v3-auth-algorithm> v3-access-mode <v3-access-mode>
To remove an SNMP v3 user, enter the following command in root view:
root> platform security protocols-control snmp v3-authentication remove
v3-user-name <v3-user-name>
To display all SNMP v3 users and their authentication parameters, enter the following command in root view:
root> platform security protocols-control snmp v3-authentication show

Table 107 SNMPv3 CLI Parameters

Parameter Input Type Permitted Values Description

set-block Variable yes yes – SNMPv1 and SNMPv2 access is

no blocked.
no – SNMPv1 and SNMPv2 access is
not blocked.

v3-user-name Text String A SNMPv3 user name.

Phn 3963 013v000

Page 601
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

Parameter Input Type Permitted Values Description

v3-user- Text String Must be at least eight An SNMPv3 user password.

password characters.

v3-security- Variable authNoPriv Defines the security mode to be used

mode authPriv for this user.
noAuthNoPriv

v3-encryption- Variable None Defines the encryption (privacy)

mode DES protocol to be used for this user.
AES

v3-auth- Variable None Defines the authentication algorithm

algorithm SHA to be used for this user.
MD5

v3-access- Variable readWrite Defines the access permission level for

mode readOnly this user.

Example
The following commands enable SNMP v2 on the unit, and set the read community to “public” and the write
community to “private”:
root> platform security protocols-control snmp admin set enable

root> platform security protocols-control snmp version set v2

root> platform security protocols-control snmpv1v2 set read-community

public write-community private
The following commands enable SNMP v3 on the unit, block SNMP v1 and SNMP v2 access, and define an SNMPv3
user with User Name=Geno, Password=abcdefgh, security mode authPriv, encryption mode DES, authentication
algorithm SHA, and read-write access:
root> platform security protocols-control snmp admin set enable

root> platform security protocols-control snmp version set v3

root> platform security protocols-control snmp v1v2-block set yes

root> platform security protocols-control snmp v3-authentication add v3-

user-name geno v3-user-password abcdefgh v3-security-mode authPriv v3-
encryption-mode DES v3-auth-algorithm SHA v3-access-mode readWrite

Displaying the SNMP Settings (CLI)

To display the general SNMP parameters, enter the following command in root view:
root> platform security protocols-control snmp show-all
To display all SNMP v3 users and their authentication parameters, enter the following command in root view:

Phn 3963 013v000

Page 602
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

root> platform security protocols-control snmp v3-authentication show

To display the current MIB version used in the system, enter the following command in root view:
root> platform security protocols-control snmp show-mib-version
To display details about the current MIB version used in the system, enter the following command in root view:
root> platform security protocols-control snmp show-mib-version-table
To display the SNMP read and write communities, enter the following command in root view:
root> platform security protocols-control snmpv1v2 show

Configuring Trap Managers (CLI)

To display the current SNMP trap manager settings, enter the following command in root view:
root> platform security protocols-control snmp trap-manager show
To modify the settings of an SNMP trap manger, enter the following command in root view:
root> platform security protocols-control snmp trap-manager set manager-
id <manager-id> manager-admin <manager-admin> manager-ipv4 <manager-ipv4>
manager-ipv6<manager-ipv6> manager-port <manager-port> manager-community
<manager-community> manager-v3-user <manager-v3-user> manager-description
<manager-description>
To enable an SNMP trap manger without modifying its parameters, enter the following command in root view:
root> platform security protocols-control snmp trap-manager admin
manager-id <manager-id> manager-admin <manager-admin>
To specify the number of minutes between heartbeat traps, enter the following command in root view:
root> platform security protocols-control snmp trap-manager heartbeat
manager-id <manager-id> manager-heartbeat <manager-heartbeat>

Table 108 Trap Managers CLI Parameters

Parameter Input Type Permitted Values Description

manager-id Number. 1–4 Enter the Manager ID of the trap

manager you want to modify.

manager- Variable. enable Enter enable or disable to enable or

admin disable disable the trap manager.

manager-ipv4 Dotted Any valid IPv4 address. If the IP protocol selected in platform
decimal management ip set ip-address-
format. family is IPv4, enter the destination
IPv4 address. Traps will be sent to this
IP address.

Phn 3963 013v000

Page 603
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

Parameter Input Type Permitted Values Description

manager-ipv6 Eight groups Any valid IPv6 address. If the IP protocol selected in platform
of four management ip set ip-address-
hexadecimal family is IPv6, enter the destination
digits IPv6 address. Traps will be sent to this
separated by IP address.
colons.

manager-port Number. 70 – 65535 Enter the number of the port through

which traps will be sent.

manager- Text String. Any valid SNMP read Enter the community string for the
community community. SNMP read community.

manager-v3- Text String. The name of a V3 user If the SNMP Trap version selected in
user defined in the system. platform security protocols-
control snmp version set is V3, enter
the name of a V3 user defined in the
system.
Note: Make sure that an identical V3
user is also defined on the manager's
side

manager- Text String. Enter a description of the trap

description manager (optional).

manager- Number. 0 – 1440 Specifies the number of minutes

heartbeat between heartbeat traps. If you enter
0, no heartbeat traps will be sent.
Note: To reduce unnecessary traffic,
heartbeat traps are only sent if no
other trap was sent during the
Heartbeat Period.

Examples
The following commands enable trap manager 2, and assign it IP address 192.168.1.250, port 164, and community
“private”, with a heartbeat of 12 minutes.
root> platform security protocols-control snmp trap-manager set manager-
id 2 manager-admin enable manager-ip 192.168.1.250 manager-port 164
manager-community private manager-description text

root> platform security protocols-control snmp trap-manager heartbeat

manager-id 2 manager-heartbeat 12

Phn 3963 013v000

Page 604
Chapter 15: Unit Management (CLI) Configuring SNMP (CLI)

Phn 3963 013v000

Page 605
Chapter 15: Unit Management (CLI) Configuring the Internal Ports for FTP or SFTP (CLI)

Configuring the Internal Ports for FTP or SFTP (CLI)

By default, the following PTP 820 ports are used for FTP and SFTP when the PTP 820 unit is acting as an FTP or SFTP
client (e.g., software downloads, configuration file backup and restore operations):
• FTP – 21
• SFTP – 22
To change the port for either protocol, enter the following command in root view:
root> platform management file-transfer port-config protocol <ftp|sftp>
port-number <0-65535>
To display the ports that are currently configured for FTP and SFTP, enter the following command in root view:
root> platform management file-transfer port-show
These ports are configured globally, rather than per specific operation.
The following sequence of commands displays the current (default) FTP and SFTP port settings, changes the FTP
port to 125 and the SFTP port to 126, and shows the new FTP and SFTP port settings.
root>platform management file-transfer port-show

Port config table:

==================
File transfer File transfer port

protocol number
=====================================
ftp 21
sftp 22

root> platform management file-transfer port-config protocol ftp port-

number 125

root> platform management file-transfer port-config protocol sftp port-

number 126

root>platform management file-transfer port-show

Port config table:

==================
File transfer File transfer port

protocol number
=====================================

ftp 125
sftp 126

root>

Phn 3963 013v000

Page 606
Chapter 15: Unit Management (CLI) Upgrading the Software (CLI)

Upgrading the Software (CLI)

PTP 820 software and firmware releases are provided in a single bundle that includes software and firmware for all
components in the system. Software is first downloaded to the system, then installed. After installation, a reset is
automatically performed on all components whose software was upgraded.
This section includes:
• Software Upgrade Overview (CLI)
• Viewing Current Software Versions (CLI)
• Configuring a Software Download (CLI)
• Downloading a Software Package (CLI)
• Installing and Upgrading Software (CLI)

Software Upgrade Overview (CLI)

The PTP 820 software installation process includes the following steps:
1. Download – The files required for the installation or upgrade are downloaded from a remote server.
2. Installation – The downloaded software and firmware files are installed in all modules and components of the
PTP 820 that are currently running an older version.
3. Reset – The PTP 820 is restarted in order to boot the new software and firmware versions.
Software and firmware releases are provided in a single bundle that includes software and firmware for all
components in the system. When you download a software bundle, the system verifies the validity of the bundle.
The system also compares the files in the bundle to the files currently installed in the PTP 820 and its components,
so that only files that need to be updated are actually downloaded. A message is displayed for each file that is
actually downloaded.

Note
When downloading an older version, all files in the bundle may be downloaded, including files that
are already installed.

Software bundles can be downloaded via HTTP, HTTPS, FTP or SFTP. After the software download is complete, you
can initiate the installation.

Note
Before performing a software upgrade, it is important to verify that the system date and time are
correct. See Setting the Time and Date (Optional) (CLI).
When upgrading a node with unit protection, upgrade the standby unit first, then the active unit.

Viewing Current Software Versions (CLI)

To display the software version running and downloaded on the unit, enter the following command in root view:

Phn 3963 013v000

Page 607
Chapter 15: Unit Management (CLI) Upgrading the Software (CLI)

The following appears:

• Downloaded Version – The version, if any, that has been downloaded from the server but not yet
installed. Upon installation and reset, this version will become the Running Version.
• Installed Version – The software version currently running on the unit.
To display more detailed information about software component versions, enter the following command in root
view:
root> platform software show versions

Configuring a Software Download (CLI)

You can download software using HTTP, HTTPS, FTP, or SFTP.
When downloading software via HTTP or HTTPS, the PTP 820 functions as the server, and you can download the
software directly to the PTP 820 unit.

Note
HTTP/HTTPS software download is only supported using the Web EMS. For instructions, see
Downloading and Installing Software.

When downloading software, the IDU functions as an FTP or SFTP client. You must install FTP or SFTP server
software on the PC or laptop you are using to perform the software upgrade. For details, see Installing and
Configuring an FTP or SFTP Server.

Note
For SFTP downloads, be aware that only certain ciphers are supported in some operation modes. For
a list of supported ciphers, including an indication of which ciphers are supported in HTTPS strong
mode and FIPS mode, refer to Annex A – Supported Ciphers for Secured Communication Protocols in
the Release Notes for the product and System release version you are using.

To set the file transfer protocol you want to use (FTP or SFTP), enter the following command:
root> platform software download version protocol <ftp|sftp>
If the IP protocol selected in platform management ip set ip-address-family is IPv4, enter the following command:
root> platform software download channel server set server-ip <server-
ipv4> directory <directory> username <username> password <password>
If the IP protocol selected in platform management ip set ip-address-family is IPv6, enter the following command:
root> platform software download channel server-ipv6 set server-ip
<server-ipv6> directory <directory> username <username> password
<password>
To display the software download channel configuration, enter one of the following commands:
root> platform software download channel server show
root> platform software download channel server-ipv6 show

Table 109 Software Download CLI Parameters

Phn 3963 013v000

Page 608
Chapter 15: Unit Management (CLI) Upgrading the Software (CLI)

Parameter Input Type Permitted Values Description

server-ipv4 Dotted Any valid IPv4 address. The IPv4 address of the PC or laptop
decimal you are using as the FTP server.
format.

server-ipv6 Eight groups Any valid IPv6 address. The IPv6 address of the PC or laptop
of four you are using as the FTP server.
hexadecimal
digits
separated by
colons.

directory Text String. The directory path from which you are
downloading the files. Enter the path
relative to the FTP user's home
directory, not the absolute path. To
leave the path blank, enter //. If the
location is the home directory, it
should be left empty. If the location is
a sub-folder under the home directory,
specify the folder name. If the shared
folder is "C:\", this parameter can be
left empty or populated with "//".

server- Text String. The user name you configured in the

username FTP server.

server- Text String. The password you configured in the

password FTP server. If you did not configure a
password for your FTP user, simply
omit this parameter.

The following command configures a download from IP address 192.168.1.242, in the directory “current”, with
user name “anonymous” and password “12345.”
root> platform software download channel server set server-
ip 192.168.1.242 directory \current username anonymous password 12345

Downloading a Software Package (CLI)

To initiate a software download, enter the following command in root view:
root> platform software download version protocol ftp
The following prompt appears:
You are about to perform a software management operation. This may cause
a system reset.

Phn 3963 013v000

Page 609
Chapter 15: Unit Management (CLI) Upgrading the Software (CLI)

Are you sure? (yes/no)

Enter Yes at the prompt. When the prompt appears again, enter the following command to check the download
status:
root> platform software download status show
Once the following message appears, proceed with the installation:
DOWNLOAD VERSION status: download success, process percentage: 100

Important Note – If upgrading from version 7.9 or earlier:

• Before you proceed to install the software, repeat the download process even if the platform software
download status show command produced a download success message, until the unit displays the
message all components exist.
• In case of failure, wait at least 30 minutes and repeat the software download.

Installing and Upgrading Software (CLI)

To install or upgrade the software, enter the following command in root view after downloading the software
bundle:
root> platform software install version
If you wish to delay the start of installation, enter instead the following command. The time you enter in HH:MM
format is the amount of time to delay until the start of the installation process:
root> platform software install version timer-countdown <hh:mm>
The following prompt appears:
Software version to be installed:

Are you sure? (yes/no)

To display the status of a software installation or upgrade, enter the following command:
root> platform software install status show
Important Notes:
• DO NOT reboot the unit during software installation process. As soon as the process is successfully completed,
the unit will reboot itself.
• Sometimes the installation process can take up to 30 minutes.
• Only in the event that software installation was not successfully finished and more than 30 minutes have
passed can the unit be rebooted.
If you configured delayed installation, you can do any of the following:
• Abort the current delayed installation. To do so, enter the following command:
root> platform software install abort-timer
• Show the time left until the installation process begins. To do so, enter the following command:
root> platform software install time-to-install
• Show the original timer as configured for a delayed installation. To do so, enter the following command:
root> platform software install show-time

Phn 3963 013v000

Page 610
Chapter 15: Unit Management (CLI) Backing Up and Restoring Configurations (CLI)

Backing Up and Restoring Configurations (CLI)

You can import and export PTP 820 configuration files. This enables you to copy the system configuration to
multiple PTP 820 units. You can also backup and save configuration files.
Importing and exporting configuration files can be done using HTTP, HTTPS, FTP, or SFTP. However, import and
export using HTTP or HTTPS must be performed using the Web EMS. See Backing Up and Restoring Configurations.
Configuration files can only be copied between units of the same type, i.e., PTP 820C to PTP 820C, PTP 820C-HP to
PTP 820C-HP, PTP 820E to PTP 820E and PTP 820S to PTP 820S.
Note that you can also write CLI scripts that will automatically execute a series of commands when the
configuration file is restored. For information, refer to Editing CLI Scripts (CLI).
This section includes:
• Configuration Management Overview (CLI)
• Setting the Configuration Management Parameters (CLI)
• Backing up and Exporting a Configuration File (CLI)
• Importing and Restoring a Configuration File (CLI)
• Editing CLI Scripts (CLI)

Configuration Management Overview (CLI)

System configuration files consist of a zip file that contains three components:
• A binary configuration file used by the system to restore the configuration.
• A text file which enables users to examine the system configuration in a readable format. The file includes the
value of all system parameters at the time of creation of the backup file.
• An additional text file which enables you to write CLI scripts in order to make desired changes in the backed-
up configuration. This file is executed by the system after restoring the configuration.
The system provides three restore points to manage different configuration files. Each restore point contains a
single configuration file. Files can be added to the restore points by creating backups of the current system state or
by importing them from an external server. For example, you may want to use one restore point to keep a last
good configuration, another to import changes from an external server, and the third to store the current
configuration.
You can apply a configuration file to the system from any of the restore points.
You must configure from 1 to 3 restore points:
• When you import a configuration file, the file is saved to the selected restore point, and overwrites whichever
file was previously held in that restore point.
• When you export a configuration file, the file is exported from the selected restore point.
• When you backup the current configuration, the backup configuration file is saved to the selected restore
point, and overwrites whichever file was previously held in that restore point.
• When you restore a configuration, the configuration file in the selected restore point is the file that is
restored.

Phn 3963 013v000

Page 611
Chapter 15: Unit Management (CLI) Backing Up and Restoring Configurations (CLI)

Setting the Configuration Management Parameters (CLI)

When importing and exporting configuration files, the PTP 820 functions as an FTP or SFTP client. You must install
FTP or SFTP server software on the PC or laptop you are using to perform the import or export. For details, see
Installing and Configuring an FTP or SFTP Server.

Note
Before importing or exporting a configuration file, you must verify that the system date and time are
correct. See Setting the Time and Date (Optional) (CLI).

To set the FTP or SFTP parameters for configuration file import and export, enter one of the following commands
in root view:
• If the IP protocol selected in platform management ip set ip-address-family is IPv4, enter the following
command:
root> platform configuration channel server set ip-address <server-ipv4>
directory <directory> filename <filename> username <username> password
<password>
• If the IP protocol selected in platform management ip set ip-address-family is IPv6, enter the following
command:
root> platform configuration channel server-ipv6 set ip-address <server-
ipv6> directory <directory> filename <filename> username <username>
password <password>
To set the file transfer protocol you want to use (FTP or SFTP), enter the following command:
root>platform configuration channel set protocol <ftp|sftp>
To display the FTP channel parameters for importing and exporting configuration files, enter one of the following
commands in root view:
root> platform configuration channel server show

root> platform configuration channel server-ipv6 show

Table 110 Configuration Management CLI Parameters

Parameter Permitted
Input Type Values Description

server-ipv4 Dotted Any valid IPv4 The IPv4 address of the PC or laptop you are using
decimal address. as the FTP server.
format.

server-ipv6 Eight groups Any valid IPv6 The IPv6 address of the PC or laptop you are using
of four address. as the FTP server.
hexadecimal
digits
separated by
colons.

Phn 3963 013v000

Page 612
Chapter 15: Unit Management (CLI) Backing Up and Restoring Configurations (CLI)

Parameter Permitted
Input Type Values Description

directory Text String. The location of the file you are downloading or
uploading. If the location is the root shared folder,
it should be left empty. If the location is a sub-
folder under the root shared folder, specify the
folder name. If the shared folder is "C:\", this
parameter can be left empty or populated with
"//".

filename Text String. The name of the file you are importing, or the
name you want to give the file you are exporting.
Note: You must add the suffix .zip to the file name.
Otherwise, the file import may fail. You can export
the file using any name, then add the suffix .zip
manually.

username Text String. The user name you configured in the FTP server.

password Text String. The password you configured in the FTP server. If
you did not configure a password for your FTP
user, simply omit this parameter.

Examples
The following command configures the FTP channel for configuration file import and export to IP address
192.168.1.99, in the directory “current”, with file name “version_8_backup.zip”, user name “anonymous”, and
password “12345.”
root> platform configuration channel server set server-ip 192.168.1.99
directory \current filename version_8_backup.zip username anonymous
password 12345

Backing up and Exporting a Configuration File (CLI)

To save the current configuration as a backup file to one of the restore points, enter the following command in
root view:
root> platform configuration configuration-file add <restore-point>
To export a configuration from a restore point to the external server location, enter the following command in root
view:
root> platform configuration configuration-file export <restore-point>

Table 111 Configuration Backup and Restore CLI Parameters

Phn 3963 013v000

Page 613
Chapter 15: Unit Management (CLI) Backing Up and Restoring Configurations (CLI)

Parameter Input Type Permitted Values Description

restore-point Variable restore-point-1 Identifies the restore point to or from

restore-point-2 which to perform the backup
operation.
restore-point-3

Examples
The following commands save the current configuration as a configuration at Restore Point 1, and export the file to
the external server location:
root> platform configuration configuration-file add restore-point-1

root> platform configuration configuration-file export restore-point-1

Importing and Restoring a Configuration File (CLI)

You can import a configuration file from an external PC or laptop to one of the restore points. Once you have
imported the file, you can restore the configuration. Restoring a saved configuration does not change the unit’s
FIPS mode.

Note
In order to import a configuration file, you must configure the FTP channel parameters and restore
points, as described in Setting the Configuration Management Parameters and Backing up and
Exporting a Configuration File.

To import a configuration file, enter the following command in root view:

root> platform configuration configuration-file import <restore-point>
To restore a configuration from a restore point to become the active configuration file, enter the following
command in root view:
root> platform configuration configuration-file restore <restore-point>

Table 112 Configuration Import and Restore CLI Parameters

Parameter Input Type Permitted Values Description

restore-point Variable restore-point-1 Identifies the restore point to or from

restore-point-2 which to perform the backup
operation.
restore-point-3

Examples
The following commands import a configuration file from an external PC or laptop to Restore Point 2 on the PTP
820, and restore the file to be the system configuration file for the PTP 820:

Phn 3963 013v000

Page 614
Chapter 15: Unit Management (CLI) Backing Up and Restoring Configurations (CLI)

root> platform configuration configuration-file import restore-point-2

root> platform configuration configuration-file restore restore-point-2

Editing CLI Scripts (CLI)

The configuration file package includes a text file that enables you to write CLI scripts in a backed-up configuration
that are executed after restoring the configuration.
To edit a CLI script:
1. Back up the current configuration to one of the restore points. See Backing up and Exporting a Configuration
File (CLI).
2. Export the configuration from the restore point to a PC or laptop. See Backing up and Exporting a
Configuration File (CLI).
3. On the PC or laptop, unzip the file Configuration_files.zip.
4. Edit the cli_script.txt file using clish commands, one per line.
5. Save and close the cli_script.txt file, and add it back into the Configuration_files.zip file.
6. Import the updated Configuration_files.zip file back into the unit. See Importing and Restoring a Configuration
File (CLI).
7. Restore the imported configuration file. See Importing and Restoring a Configuration File (CLI). The unit is
automatically reset. During initialization, the CLI script is executed, line by line.

Note
If any specific command in the CLI script requires reset, the unit is reset when that that command is
executed. During initialization following the reset, execution of the CLI script continues from the
following command.

Phn 3963 013v000

Page 615
Chapter 15: Unit Management (CLI) Setting the Unit to the Factory Default Configuration (CLI)

Setting the Unit to the Factory Default

Configuration (CLI)

To restore the unit to its factory default configuration, while retaining the unit’s IP address settings and logs, enter
the following commands in root view:
root> platform management set-to-default
The following prompt appears:
WARNING: All database and configuration will be lost, unit will be
restart.
Are you sure? (yes/no):yes
At the prompt, type yes.

Note
This does not change the unit’s IP address or FIPS configuration.

Phn 3963 013v000

Page 616
Chapter 15: Unit Management (CLI) Performing a Hard (Cold) Reset (CLI)

Performing a Hard (Cold) Reset (CLI)

To initiate a hard (cold) reset on the unit, enter the following command in root view:
root> platform management chassis reset
The following prompt appears:
You are about to reset the shelf
Are you sure? :(yes/no):
Enter yes. The unit is reset.

Phn 3963 013v000

Page 617
Chapter 15: Unit Management (CLI) Configuring Unit Parameters (CLI)

Configuring Unit Parameters (CLI)

You can view and configure system information:

To configure a name for the unit, enter the following command in root view:
root> platform management system-name set name <name>
To define a location for the unit, enter the following command in root view:
root> platform management system-location set name <name>
To define a contact person for questions pertaining to the unit, enter the following command in root view:
root> platform management system-contact set name <name>
To define the unit's latitude coordinates, enter the following command in root view:
root> platform management system-latitude set <latitude>
To define the unit's longitude coordinates, enter the following command in root view:
root> platform management system-longitude set <longitude>
To define the type of measurement unit you want the system to use, enter the following command in root view:
root> platform management set unit_measure_format <unit_measure_format>
To display the type of measurement unit used by the system, enter the following command in root view:
root> platform management show unit_measure_format

Table 113 Unit Parameters CLI Parameters

Parameter Input Type Permitted Values Description

name Text Up to 64 characters. Defines the name of the unit.

latitude Text Up to 256 characters. Defines the latitude coordinates of the

unit.

longitude Text Up to 256 characters. Defines the longitude coordinates of

the unit.

unit_measure Variable metric Defines the measurement units of the

_format imperial unit.

Examples
The following commands configure a name, location, contact person, latitude coordinates, longitude coordinates,
and units of measurements for the PTP 820:
root> platform management system-name set name "My-System-Name"

root> platform management system-location set name "My-System-Location"

Phn 3963 013v000

Page 618
Chapter 15: Unit Management (CLI) Configuring Unit Parameters (CLI)

root> platform management system-contact set name "John Doe"

root> platform management system-latitude set 40

root> platform management system-longitude set 73

root> platform management set unit_measure_format metric

Phn 3963 013v000

Page 619
Chapter 15: Unit Management (CLI) Configuring NTP (CLI)

Configuring NTP (CLI)

PTP 820 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.
You can configure up to four NTP servers. Each server can be configured using IPv4 or IPv6. When multiple servers
are configured, the unit chooses the best server according to the implementation of Version 4.2.6p1 of the
NTPD (Network Time Protocol Daemon). The servers are continually polled. The polling interval is determined by
the NTPD, to achieve maximum accuracy consistent with minimum network overhead.
To configure an NTP server, enter the following commands in root view:

root> platform management ntp set admin index <index> admin

<admin>

To specify the server’s IP address, use one of the following commands.

For each NTP server you configure, you can define an IPv4 address or an IPv6 address, but not both.
• To configure the NTP server with an IPv4 address, enter the following
command in root view:

root> platform management ntp set server ipv4 index <index>

ipv4 <ipv4> ntp-version <ntp-version>
• To configure the NTP server with an IPv6 address, enter the following
command in root view:

root> platform management ntp set server ipv4 index <index>

ipv4 <ipv6> ntp-version <ntp-version>
To display the current configuration of all the defined NTP servers, enter the following command
in root view:

root> platform management ntp show status

To display the current configuration and status of all the defined NTP servers, including details that
can be used for debugging, enter the following command in root view:

root> platform management ntp show status all

Table 114 NTP CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable. enable Enter enable or disable to enable or

disable disable the NTP server.

ntp-version Variable. v3 Enter the NTP version you want to use.

v4 NTPv4 provides interoperability with
NTP v3 and with SNTP.

Phn 3963 013v000

Page 620
Chapter 15: Unit Management (CLI) Displaying SFP DDM and Inventory Information (CLI)

Parameter Input Type Permitted Values Description

ntp-server-ip- Dotted Any valid IP address. Enter the IP address of the NTP server.
address decimal
format.

Example
The following command enables NTP, using NTP v4, and sets the IP address of the NTP server as 62.90.139.210.
root> platform management ntp set admin enable ntp-version ntpv4 ntp-
server-ip-address-1

Displaying Unit Inventory (CLI)

To view inventory information, such as the part number and serial number of the unit hardware, enter the
following command in root view:
root> platform management inventory show-info
For example:
root> platform management inventory show info

System information:

card-name : PTP 820

Subtype : 350

part number : 22-0001-0|

serial number : F493606212

company name : Cambium Networks

product name : AODU DC, All-outdoor, dual radio carriers in one product
product description : AODU DC, All-outdoor, dual radio carriers in one
product

root>

Displaying SFP DDM and Inventory Information

(CLI)
Static and dynamic monitoring is available for SFP modules, including all SFP, SFP+, and CSFP modules used in
Ethernet and MIMO ports in PTP 820 all-outdoor products. Dynamic monitoring PMs are also available.
Dynamic monitoring (DDM) PMs are also available.

Phn 3963 013v000

Page 621
Chapter 15: Unit Management (CLI) Displaying SFP DDM and Inventory Information (CLI)

Note
DDM parameters are not relevant for electrical SFPs.

The following alarms are available in connection with SFP DDM and inventory monitoring. The polling interval for
these alarms is one minute.
• Alarm #803- SFP port RX power level is too low.
• Alarm #804 – SFP port RX power level is too high.
• Alarm #805- SFP port TX power level is too low.
• Alarm #806 – SFP port TX power level is too high.
These alarms are based on thresholds defined by the SFP module vendor, which are static. They also display the
actual RX or TX values as of the time when the alarm was raised, which are dynamic. The dynamic values are not
changed as long as the alarm is still raised. They are only updated if the alarm is cleared, then raised again.
If there is no signal on the interface, a Loss of Carrier alarm (LOC) is raised, and this alarm masks the DDM alarms.

Displaying Static Information about an SFP Module (CLI)

To display static information about an SFP module, enter the following command in root view:
root> platform interfaces sfp-inventory show
For example:

Table 115: SFP Inventory Parameters (CLI)

Parameter Description
Transceiver Indicates whether an SFP module is attached to the interface.
Present
Connector Type Always displays LC.
transceiver Type Displays a description of the SFP module.
Vendor Name Displays the name of the SFP’s vendor.
Vendor Part Displays the vendor’s part number for the SFP module.
Number
Vendor Serial Displays the vendor’s serial number for the SFP module.
Number
Vendor Revision Displays the revision number of the serial number provided by
the vendor for the SFP module.

Phn 3963 013v000

Page 622
Chapter 15: Unit Management (CLI) Displaying SFP DDM and Inventory Information (CLI)

Parameter Description
Laser Wavelength Display’s the SFP module’s laser wavelength. For CSFP modules,
(nm) two wavelengths are displayed. This parameters is not relevant
for copper SFPs.
Link Length SM The maximum length of the cable (in km) for single mode fiber
Fiber (km) cables.
Link Length OM1 The maximum length of the cable (in meters) for OM1 multi-
Fiber (m) mode fiber cables.
Link Length OM2 The maximum length of the cable (in meters) for OM2 multi-
Fiber (m) mode fiber cables.
Link Length OM3 The maximum length of the cable (in meters) for OM3 multi-
Fiber (m) mode fiber cables.
Optical Diagnostics Displays whether the SFP module supports DDM monitoring. For
Supported modules that do not support DDM monitoring, the parameters
described in Table 114 are not available.

Displaying Dynamic (DDM) Information about an SFP Module

(CLI)
To display dynamic information about an SFP module, enter the following command in root view:
root> platform interfaces sfp-diagnostic show
For example:

Table 116: SFP Digital Diagnostic Monitoring (DDM) Parameters (CLI)

Parameter Description
Transceiver Indicates whether an SFP module is attached to the interface.
Present
RX Power Level The SFP module’s current RX power signal strength (in dBm).
(dBm)
TX Power Level The SFP module’s current TX power signal strength (in dBm).
(dBm)
Bias Current (mA) The laser bias current of the SFP module (in mA)
Temperature The current temperature of the SFP module (displayed in both
C° and F°).

Phn 3963 013v000

Page 623
Chapter 15: Unit Management (CLI) Displaying SFP DDM and Inventory Information (CLI)

If no signal is being received, RX Power Level is displayed as -40 dBm.

If the Admin status of the port is Down, the TX Power Level is displayed as -40 DBm and the Bias Current
is displayed as 0 mA.
The Temperature is always shown as long as the SFP module is inserted in the port.

Displaying DDM PMs about an SFP Module (CLI)

DDM PMs can be displayed for 15-minute and 24-hour intervals. For each interval, the following PMs are
displayed:
• Minimum RX power during the interval (dBm)
• Average RX power during the interval (dBm)
• Maximum RX power during the interval (dBm)
• Minimum TX power during the interval (dBm)
• Average TX power during the interval (dBm)
• Maximum TX power during the interval (dBm)
To display DDM PMs, enter the following command in root view:
root> platform interfaces sfp-pm show slot <slot> port <port> interface
eth interval <15min|24h|all>
For example:

The Integrity column indicates whether the PM is valid:

• 0 indicates a valid entry.
• 1 indicates an invalid entry. This can be caused by any of the following events that occurred during the interval
o LOC alarm
o Changing the Admin status of the interface
o Unit reset
Note: No entries are displayed if the SFP device does not support DDM, or if the
Admin status of the interface is Down.

DDM PMs are not persistent, which means they are not saved in the event of unit reset. RX and TX power levels
are collected five times per 15-minute interval. 15-minute PM data is saved for 24 hours. 24-hour PM data, which
is updated every 15 minutes, is saved for 30 days.

Phn 3963 013v000

Page 624
Chapter 15: Unit Management (CLI) Displaying SFP DDM and Inventory Information (CLI)

Phn 3963 013v000

Page 625
Chapter 16: Radio Configuration (CLI) Displaying SFP DDM and Inventory Information (CLI)

Chapter 16: Radio Configuration (CLI)

This section includes:
• Viewing and Configuring the Remote Radio Parameters (CLI)
• Configuring ATPC and ATPC Override Timer (CLI)
• Configuring Header De-Duplication (CLI)
• Configuring Frame Cut-Through (CLI)
• Configuring AES-256 Payload Encryption (CLI)
• Configuring and Viewing Radio PMs and Statistics (CLI)
Related topics:
• Entering Radio View (CLI)
• Muting and Unmuting a Radio (CLI)
• Configuring the Transmit (TX) Level (CLI)
• Configuring the Transmit (TX) Frequency (CLI)
• Configuring the Radio (MRMC) Script(s) (CLI)
• System Configurations (CLI)
• Configuring Multi-Carrier ABC (CLI)
• Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)
• Configuring XPIC (CLI)
• Configuring Unit Protection with HSB Radio Protection (External Protection) (CLI)
• Configuring MIMO and Space Diversity (CLI)
• Operating a PTP 820C/PTP 820C-HP in Single Radio Carrier Mode (CLI)

Note
For convenience, this User Guide generally shows the radio prompt as radio[2/1]>.
To view and configure radio parameters, you must first enter the radio’s view level in the CLI. For
details, refer to Entering Radio View (CLI)

Phn 3963 013v000

Page 626
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

Viewing and Configuring the Remote Radio

Parameters (CLI)

This section includes:

• Displaying Communication Status with the Remote Radio (CLI)
• Displaying the Remote Radio’s Link ID (CLI)
• Muting and Unmuting the Remote Radio (CLI)
• Displaying the Remote Radio’s RX Level (CLI)
• Configuring the Remote Radio’s TX Level (CLI)
• Configuring Remote ATPC (CLI)
• Displaying the Remote Unit’s Most Severe Alarm (CLI)

Related topics:
• Configuring the Remote Unit’s IP Address (CLI)

Displaying Communication Status with the Remote Radio (CLI)

To display the communication status with the remote radio, enter the following command in radio view:
radio[x/x]>remote-unit communication status show

Displaying the Remote Radio’s Link ID (CLI)

To display the remote radio’s Link ID, enter the following command in radio view:
radio[x/x]>remote-unit show link-id

Muting and Unmuting the Remote Radio (CLI)

To mute or unmute the remote radio, enter the following command in radio view:
radio[x/x]>remote-unit mute set admin <admin>
To display the mute status of the remote radio, enter the following command in radio view:
radio[x/x]>remote-unit mute show status

Table 117 Remote Radio Mute/Unmute CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable on Mutes (on) or unmutes (off) the

off remote unit.

Phn 3963 013v000

Page 627
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

The following command mutes the remote radio:

radio[2/1]>remote-unit mute set admin on
The following command unmutes the remote radio:
radio[2/1]>remote-unit mute set admin off

Displaying the Remote Radio’s RX Level (CLI)

To display the remote radio’s RX level, enter the following command in radio view:
radio[x/x]>remote-unit show rx-level

Configuring the Remote Radio’s TX Level (CLI)

To set the transmit (TX) level of the remote radio, enter the following command in radio view:
radio[x/x]>remote-unit set tx-level <tx-level>
To display the transmit (TX) level of the remote radio, enter the following command in radio view:
radio[x/x]>remote-unit show tx-level

Table 118 Remote Radio TX Level CLI Parameters

Parameter Input Type Permitted Values Description

tx-level Number Depends on the frequency The desired TX signal level (TSL), in
and unit type. dBm.

The following command sets the TX level of the remote radio to 10 dBm:
radio[2/1]>remote-unit set tx-level 10

Configuring Remote ATPC (CLI)

To set the RX reference level for ATPC on the remote radio, enter the following command:
radio[x/x]>remote-unit atpc set ref-level <ref-level>
To display the RX reference level for ATPC on the remote radio, enter the following command:
radio[x/x]>remote-unit atpc show ref-level

Table 119 Remote Radio ATPC CLI Parameters

Parameter Input Type Permitted Values Description

ref-level Number -70 - -30 The RX reference level for the ATPC
mechanism.

The following command sets the ATPC RX reference level of the remote radio to -55:
radio[2/1]>remote-unit atpc set ref-level -55

Phn 3963 013v000

Page 628
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

Displaying the Remote Unit’s Most Severe Alarm (CLI)

To display the most severe alarm currently raised in the unit, enter the following command in radio view:
radio[x/x]>remote-unit show most-severe-alarm

Phn 3963 013v000

Page 629
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

Configuring ATPC and ATPC Override Timer (CLI)

ATPC is a closed-loop mechanism by which each carrier changes the TX power according to the indication received
across the link, in order to achieve a desired RSL on the other side of the link.
With ATPC, if the radio increases its TX power up to the configured TX power, it can lead to a period of sustained
transmission at maximum power, resulting in unacceptable interference with other systems.
In order to minimize interference, PTP 820 provides an ATPC override mechanism. When ATPC override is enabled,
a timer begins when ATPC raises the TX power to its maximum. When the timer expires, the radio enters ATPC
override state. In ATPC override state, the radio transmits no higher than the pre-determined ATPC override TX
level, and an ATPC override alarm is raised. The radio remains in ATPC override state until the ATPC override state
is manually cancelled by the user (or until the unit is reset). The radio then returns to normal ATPC operation.
In a configuration with unit protection, the ATPC override state is propagated to the standby unit in the event of
switchover.

Note
When canceling an ATPC override state, you should ensure that the underlying problem has been
corrected. Otherwise, ATPC may be overridden again. You cannot use ATPC in MIMO mode. See
Configuring MIMO and Space Diversity (CLI).

To enable or disable ATPC, enter the following command:

radio[x/x]>atpc set admin <admin>
To display whether or not ATPC is enabled, enter the following command:
radio[x/x]>atpc show admin
To set the RX reference level for ATPC, enter the following command
radio[x/x]>atpc set rx-level atpc_ref_rx_level <rx-level>
To display the RX reference level for ATPC, enter the following command:
radio[x/x]>atpc show rx-level
To set an ATPC override timer, enter the following command in radio view:
radio[x/x]>atpc set override timeout <timeout>

Note
The next command actually enables ATPC override. However, it is recommended to set the timer
before enabling ATPC override. Failure to do so can lead to unexpected reduction of the TX power
with corresponding loss of capacity if TX override is enabled with the timer set to a lower-than-
desired value.

To enable ATPC override, enter the following command in radio view. ATPC must be enabled before you enable
ATPC override.
radio[x/x]>atpc override set admin <override admin>
To display whether or not ATPC override is enabled, enter the following command in radio view:
radio[x/x]>atpc override show admin

Phn 3963 013v000

Page 630
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

To display the ATPC override timeout, enter the following command in radio view:
radio[x/x]>atpc show override timeout
To set the TX power to be used when the unit is in an ATPC override state, enter the following command in radio
view:
radio[x/x]>atpc set override-tx-level <override-tx-level>
To display the ATPC override TX power, enter the following command in radio view:
radio[x/x]>atpc show override tx-level
To display the current ATPC override state, enter the following command in radio view:
radio[x/x]>atpc show override
Possible values are:
• Normal – ATPC override is enabled, and there is no override.
• Disabled – ATPC override is not enabled.
• Override – ATPC override has been activated.
To cancel ATPC override, enter the following command in radio view:
radio[x/x]>atpc set override-cancel

Table 120 Radio ATPC CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable enable Enables or disables ATPC mode.

disable

rx-level Number -70 - -30 The RX reference level for the ATPC
mechanism.

timeout Number 0-1800 The amount of time, in seconds, the

timer counts from the moment the
radio reaches its maximum configured
TX power until ATPC override goes into
effect.

override Variable Enable Enables or disables ATPC override.

admin disable

override-tx- Number -50 - 50 The TX power, in dBm, to be used

level when the unit is in an ATPC override
state. The range of values depends on
the frequency, MRMC script, and radio
type.

The following commands enable ATPC mode and ATPC override for radio carrier 1, with an RSL reference level of -
55, an ATPC override timeout of 15 minutes, and an override TX level of 18 dBm:

Phn 3963 013v000

Page 631
Chapter 16: Radio Configuration (CLI) Viewing and Configuring the Remote Radio Parameters (CLI)

radio[2/1]>atpc set admin enable

radio[2/1]>atpc set rx-level atpc_ref_rx_level -55
radio[2/1]>atpc set override timeout 900
radio[2/1]>atpc override set admin enable
radio[2/1]> atpc set override-tx-level 18

Phn 3963 013v000

Page 632
Chapter 16: Radio Configuration (CLI) Configuring Header De-Duplication (CLI)

Configuring Header De-Duplication (CLI)

Note
For PTP 820E, Header De-Duplication is available for all channels except 500 MHz. Make sure to
disable Header De-Duplication before selecting a 500 MHz MRMC script.

Header De-Duplication identifies traffic flows and replaces header fields with a flow ID. The Header De-Duplication
module includes an algorithm for learning each new flow, and implements compression on the flow type starting
with the next frame of that flow type.
You can determine the depth to which the compression mechanism operates, from Layer 2 to Layer 4. You must
balance the depth of compression against the number of flows in order to ensure maximum efficiency. Multi-Layer
(Enhanced) compression supports up to 256 flow types.

Note
The Header De-Duplication configuration must be identical on both sides of the link.

To configure Header De-Duplication, enter the following command:

radio[2/1]> compression header-compression set <mode>

Note
In this release, if two radio carriers in a PTP 820C unit are activated, the Header De-Duplication
configuration for radio carrier 1 are applied to both carriers. You must enter radio view for radio
interface 1.

To clear Ethernet port counters, including both Frame Cut-Through and Header De-Duplication counters, enter the
following command:
radio[x/x]>clear-ethernet-port-counters

Phn 3963 013v000

Page 633
Chapter 16: Radio Configuration (CLI) Configuring Header De-Duplication (CLI)

Table 121 Header De-Duplication CLI Parameters

Parameter Input Type Permitted Values Description

mode Variable Disabled Disabled - Header De-Duplication is

Layer2 disabled.
MPLS Layer2 - Header De-Duplication
operates on the Ethernet level.
Layer3
MPLS - Header De-Duplication
Layer4
operates on the Ethernet and MPLS
Tunnel levels.
Tunnel-Layer3 Layer3 - Header De-Duplication
Tunnel-Layer4 operates on the Ethernet and IP levels.
Layer4 - Header De-Duplication
operates on all supported layers up to
Layer 4.
Tunnel - Header De-Duplication
operates on Layer 2, Layer 3, and on
the Tunnel layer for packets carrying
GTP or GRE frames.
Tunnel-Layer3 - Header De-Duplication
operates on Layer 2, Layer 3, and on
the Tunnel and T-3 layers for packets
carrying GTP or GRE frames.
Tunnel-Layer4 - Header De-Duplication
operates on Layer 2, Layer 3, and on
the Tunnel, T-3, and T-4 layers for
packets carrying GTP or GRE frames.

The following command enables Layer 2 Header De-Duplication on radio carrier 1:

root> radio slot 2 port 1

radio[2/1]> compression header-compression set mode Layer2

radio[2/1]> compression header-compression set flow-type 0x00

Displaying Header De-Duplication Information (CLI)

To display the current Header De-Duplication configuration, enter the following command:
radio[2/1]> compression show-configuration
To display counters for Header De-Duplication, enter the following command:
radio[2/1]> compression header-compression show-counters
The following counters are displayed:
• TX in octet count - Bytes on the TX side before Header De-Duplication.
• TX out octet count - Bytes on the TX side that were compressed by Header De-Duplication.
• TX frame in count - Frames on the TX side before Header De-Duplication.

Phn 3963 013v000

Page 634
Chapter 16: Radio Configuration (CLI) Configuring Header De-Duplication (CLI)

• TX frame out compressed count - Frames on the TX side that were compressed by Header De-Duplication.
• TX frame uncompressed count - The number of frames on the TX side that were not compressed due to
exclusion rules.

Note
The use of exclusion rules for Header De-Duplication is planned for future release.

• TX frame uncompressed other count - Frames on the TX side that were not compressed for reasons other than
the use of exclusion rules.
• TX out frame learning count - The number of frames that have been used to learn unique data flows. Once a
particular flow type has been learned, subsequent frames with that flow type are compressed by Header De-
Duplication.
• TX out number of active flows in count - The number of Header De-Duplication flows that are active on the TX
side.

Phn 3963 013v000

Page 635
Chapter 16: Radio Configuration (CLI) Configuring Frame Cut-Through (CLI)

Configuring Frame Cut-Through (CLI)

Using the Frame Cut-Through feature, frames assigned to queues with 4th priority pre-empt frames already in
transmission over the radio from other queues. After the 4th queue frames have been transmitted, transmission of
the pre-empted framesresumes.

Note
The Frame Cut-Through configuration must be identical on both sides of the link.
If Frame Cut-Through is used together with 1588 Transparent Clock, the 1588 packets must be given
a CoS that is not assigned to the fourth priority queue.
Frame Cut-Through cannot be used together with 1588 Transparent Clock.

To enable Frame Cut-Through, enter the following command in radio view:

radio[2/1]> cut-through mode yes
To disable Frame Cut-Through, enter the following command in radio view:
radio[2/1]> cut-through mode no
To display whether Frame Cut-Through is currently enabled or disabled, enter the following command in radio
view:
radio[2/1]> cut-through show-mode
To display the number of frames and bytes that have been transmitted via Frame Cut-Through, enter the following
command in radio view:
radio[2/1]> cut-through show-counters

Displaying Frame Cut-Through Information (CLI)

To display the current Frame Cut-Through mode for carrier, enter the following command:
radio[x/x]>cut-through show-mode
To display counters for Frame Cut-Through for a carrier, enter the following command:
radio[x/x]>cut-through show-counters
The command output displays the number of frames, bytes, good frames, and good bytes that have been
transmitted via Frame Cut-Through since the last time the counters were cleared.
The following is a sample output of the command:

Phn 3963 013v000

Page 636
Chapter 16: Radio Configuration (CLI) Configuring Frame Cut-Through (CLI)

radio [2/1]>cut-through show-counters

Total frame count = 0

Total byte count = 0

Total good frame count = 0

Total good byte count = 0

Radio [2/1]>

Phn 3963 013v000

Page 637
Chapter 16: Radio Configuration (CLI) Configuring AES-256 Payload Encryption (CLI)

Configuring AES-256 Payload Encryption (CLI)

Note
This feature is only relevant for PTP 820C and PTP 820S units.
This feature is not supported with MIMO or Space Diversity links.

This feature requires:

• Requires an activation key per radio. If no valid AES activation key has been applied to the unit, AES will not
operate on the unit. See Configuring the Activation Key.

Note
In order for the AES activation key to become active, you must reset the unit after configuring a valid
AES activation key. Until the unit is reset, an alarm will be present if you enable AES. This is not the
case for other activation keys.

PTP 820C, PTP 820C-HP and PTP 820S support AES-256 payload encryption. The purpose of payload encryption is
to secure the radio link and provide protection against eavesdropping and/or personification (“man-in-the-
middle”) attacks.
AES is enabled and configured separately for each radio carrier.
PTP 820 uses a dual-key encryption mechanism for AES:
• The user provides a master key. The master key can also be generated by the system upon user command. The
master key is a 32-byte symmetric encryption key. The same master key must be manually configured on both
ends of the encrypted link.
• The session key is a 32-byte symmetric encryption key used to encrypt the actual data. Each link uses two
session keys, one for each direction. For each direction, the session key is generated by the transmit side unit
and propagated automatically, via a Key Exchange Protocol, to the other side of the link. The Key Exchange
Protocol exchanges session keys by encrypting them with the master key, using the AES-256 encryption
algorithm. Session keys are regenerated at user-configured intervals.
The first KEP exchange that takes place after a new master key is configured causes traffic to be blocked for up to
one minute, until the Crypto Validation State becomes Valid. Subsequent KEP exchanges that take place when a
session key expires do not affect traffic. KEP exchanges have no effect upon ACM, RSL, and MSE.
To display the current payload encryption status for all available radio links on the unit, enter the following
command in root view:
root> payload encryption status show
The following is a sample output of this command in which payload encryption is enabled but not operational on
radio interface 1, and disabled on radio interface 2.

Phn 3963 013v000

Page 638
Chapter 16: Radio Configuration (CLI) Configuring AES-256 Payload Encryption (CLI)

Note
The Crypto Validation State field indicates whether the interface is functioning properly, with AES-256
encryption. In order for this field to display Valid, both the interface itself and AES-256 encryption
must be enabled, the hardware must be in place and functioning properly, initialization must be
finished, and AES-256 encryption must be functioning properly, with no loopback on the interface.

To configure payload encryption:

1 Verify that both the local and remote units are running with no alarms. If any alarm is present, take
corrective actions to clear the alarms before proceeding.
2 If the link is using in-band management, identify which unit is local and which unit is remote from the
management point of view.
3 In a protected link, enable protection lockout, first on the remote and then on the local unit. See Disabling
Automatic Switchover to the Standby Unit (CLI).
4 To configure AES on a radio carrier, you must first enter traffic encryption view for the specific radio. To
enter Payload Encryption view, enter the following command in root view:
root> payload encryption slot 2 port <port>
For example, to configure AES on radio interface 1, enter the following command in root view:
root> payload encryption slot 2 port 1
Payload Encryption [1/1]>To display the payload encryption mode of the radio interface, enter the
following command in PayloadEncryption view:
PayloadEncryption [2/x]> payload encryption mode show
The following display indicates that payload encryption is enabled on radio interface 1:
PayloadEncryption [2/1]> payload encryption mode show

Admin Mode: AES-256

The following display indicates that payload encryption is disabled on radio interface 1:
PayloadEncryption [2/1]> payload encryption mode show

Admin Mode: Disable

5 Configure the master key by doing one of the following:
o Enter a master key manually.
o Generate the master key automatically.

Phn 3963 013v000

Page 639
Chapter 16: Radio Configuration (CLI) Configuring AES-256 Payload Encryption (CLI)

You must use the same master key on both sides of the link. This means that if you generate a master key
automatically on one side of the link, you must copy that key and for use on the other side of the link.
Once payload encryption has been enabled on both sides of the link, the Key Exchange Protocol
periodically verifies that both ends of the link have the same master key. If a mismatch is detected, an
alarm is raised and traffic transmission is stopped for the mismatched carrier at both sides of the link. The
link becomes non-valid and traffic stops being forwarded.
To define the master key manually, enter the following command in PayloadEncryption view:
PayloadEncryption [2/x]> payload encryption mkey
When you press <Enter>, the following prompt appears:
Please enter key:
Enter the master key and press <Enter>. The master key must be between 8 and 32 ASCII characters. The
characters do not appear as you type them. To display the master key and verify that you typed it
correctly, enter the payload encryption status show command described above. You can copy the
master key from the output of this command.
To generate the master key automatically, enter the following command in PayloadEncryption view:
PayloadEncryption [2/x]> master key generate
A random master key is generated. You must copy and paste this key to the other end of the link to
ensure that both sides of the link have the same master key. To display and copy the master key, enter
the traffic encryption status show command described above. You can copy the master key
from the output of this command.
6 On the local unit, follow the procedure described in Step 5 to configure the same master key configured
on the remote unit also on the local unit.
7 Enable payload encryption on the remote unit:
i Enter the following command in Payload Encryption view:
Payload Encryption [2/x]> payload encryption mode admin AES-256
This step will cause the link status to be Down until payload encryption is successfully enabled on the local
unit. However, the RSL measured on the link should remain at an acceptable level.
To disable payload encryption, enter the following command in Payload Encryption view:
Payload Encryption [2/x]> payload encryption mode admin Disable
ii The session key is automatically regenerated at defined intervals. To set the session key regeneration
interval, enter the following command in Payload Encryption view:
Payload Encryption [x/x]> payload encryption session-key period set
<00:00-00:00>
Enter the regeneration interval in hours and minutes (HH:MM). For example, the following command
configures radio interface 1 to regenerate the session key every 4 hours and 15 minutes:
Payload Encryption [2/1]> payload encryption session-key period set 04:15
To display the session key regeneration interval, enter the following command in Payload Encryption
view:
Payload Encryption [2/x]> payload encryption session-key period show

Phn 3963 013v000

Page 640
Chapter 16: Radio Configuration (CLI) Configuring AES-256 Payload Encryption (CLI)

Note
The session key regeneration interval must be the same on both sides of the link.

8 Enable payload encryption on the local unit by following the procedure described in Step 7. Verify that on
both the local and remote active units, the link status returns to Up and user traffic is restored. In links
using in-band management, verify also that in-band management returns.
9 In a protected link, perform copy-to-mate, first on the remote and then on the local unit. See Step 3 in
Configuring HSB Radio Protection (CLI). After the copy-to-mate operation, wait for both standby units to
re-boot and verify that there are no alarms.

Note
The standby unit may have a payload encryption failure alarm for up to about one minute after the
unit is up and running.

4 In a protected link, remove the protection lockout, first on the remote and then on the local unit. See
Disabling Automatic Switchover to the Standby Unit (CLI).
5 Verify that there are no alarms on the link.

You can set all master keys defined on the unit to zero value. To zeroize the master keys, enter the following
command in root view:
root> payload encryption key zeroize

Warning
Executing this command on a FIPS-enabled unit formats the unit’s disk, and renders the unit non-
operational. If it is necessary to use this command, contact Cambium Networks Technical Support
for instructions how to re-configure the unit.
This command has no effect on units that are not enabled for FIPS

Note
Any time payload encryption fails, the Operational status of the link is Down until payload encryption
is successfully restored.

Phn 3963 013v000

Page 641
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Configuring and Viewing Radio PMs and Statistics

(CLI)

This section includes:

• Displaying General Modem Status and Defective Block PMs (CLI)
• Displaying Excessive BER (Aggregate) PMs (CLI)
• Displaying BER Level and Configuring BER Parameters (CLI)
• Configuring RSL Thresholds (CLI)
• Configuring TSL Thresholds (CLI)
• Displaying RSL and TSL Levels (CLI)
• Configuring the Signal Level Threshold (CLI)
• Configuring the MSE Thresholds and Displaying the MSE PMs (CLI)
• Configuring the XPI Thresholds and Displaying the XPI PMs (CLI)
• Displaying ACM PMs (CLI)

Displaying General Modem Status and Defective Block PMs

(CLI)
To display the general status of the modem, enter the following command:
radio[x/x]>modem show status
The following is a sample output of the modem show status command:
MSE[db]: -99.00
Defective Blocks count: 0

Current Tx profile: 0
Current Tx QAM: 4
Current Tx rate(Kbps): 43389
Current Rx profile: 0
Current Rx QAM: 4
Current Rx rate(Kbps): 43389

A value of 0 in the MSE (Db) field means that the modem is not locked.
To clear all radio PMs in the system, enter the following command in root view:
root> radio pm clear all
To clear defective blocks counters for a radio, enter the following command:
radio[x/x]>modem clear counters

Phn 3963 013v000

Page 642
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Displaying Excessive BER (Aggregate) PMs (CLI)

You can display modem BER (Bit Error Rate) PMs in either 15-minute or daily intervals.
To display modem BER PMs in 15-minute intervals, enter the following command:
radio [x/x]>framer pm-aggregate show interval 15min
The following is a partial sample output of the framer pm-aggregate show interval 15min command:
radio [2/1]>framer pm-aggregate show interval 15min
Modem BER PM table:
===================

Interval Integrity ES SES UAS BBE

===========================================================
0 1 0 0 333 0
1 1 0 0 900 0
2 1 0 0 900 0
3 1 0 0 900 0
4 1 0 0 900 0
5 1 0 0 900 0
6 1 0 0 900 0
7 1 0 0 900 0
8 1 0 0 900 0

radio [2/1]>
To display modem BER PMs in daily intervals, enter the following command:
radio [x/x]>framer pm-aggregate show interval 24hr
The following is a sample output of the framer pm-aggregate show interval 24hr command:
radio [2/1]>framer pm-aggregate show interval 24hr

Modem BER PM table:

===================

Interval Integrity ES SES UAS BBE

===============================================================
0 1 0 0 53843 0
4 1 0 0 37061 0
5 1 0 0 4034 0
6 1 0 0 85971 0
8 1 0 0 46171 0
11 1 0 0 24184 0
15 1 0 0 85978 0
17 1 0 0 54979 0

radio [2/1]>

Table 122 Aggregate PMs (CLI)

Phn 3963 013v000

Page 643
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Parameter Description

Interval The number of the interval: 1-30 for daily PM reports, and 1-96 for 15 minute
PM reports.

Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. "1" in the column indicates that the values are not
reliable due to a possible power surge or power failure that occurred at that
time.

ES Indicates the number of seconds in the measuring interval during which

errors occurred.

SES Indicates the number of severe error seconds in the measuring interval.

UAS Indicates the Unavailable Seconds value of the measured interval. The value
can be between 0 and 900 seconds (15 minutes).

BBE Indicates the number of background block errors during the measured
interval.

Displaying BER Level and Configuring BER Parameters (CLI)

To display the current BER level, enter the following command:
radio [x/x]>modem show ber
The excessive-ber parameter determines whether or not excessive BER is propagated as a fault and considered
a system event. For example, if excessive-ber is enabled, excessive BER can trigger a protection switchover.
To enable or disable Excessive BER Admin, enter the following command in root view:
root> radio excessive-ber set admin <admin>
To display the current setting for excessive-ber, enter the following command in root view:
root> radio excessive-ber show admin
To set the level above which an excessive BER alarm is issued for errors detected over the radio link, enter the
following command:
radio [x/x]>modem excessive-ber set threshold <threshold>
To display the excessive BER threshold, enter the following command:
radio [x/x]>modem excessive-ber show threshold

Phn 3963 013v000

Page 644
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Table 123 Excessive BER CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable enable Enables or disables propagation of excessive

disable BER as a fault.

threshold Variable 1e-3 The level above which an excessive BER alarm
1e-4 is issued for errors detected over the radio
1e-5 link.
1e-6
1e-7
1e-8
1e-9
1e-10

The following command enables excessive-ber:

root> radio excessive-ber set admin enable
The following command sets the excessive BER threshold to 1e-5:
radio [2/1]>modem excessive-ber set threshold 1e-5

Configuring RSL Thresholds (CLI)

You can set two RSL (RX Signal Level) thresholds. The number of seconds during which the RSL exceeds these
thresholds are counted as RSL Exceed Threshold Seconds. See Displaying RSL and TSL Levels (CLI).
To set the RSL thresholds, enter the following command:
radio [x/x]>rf pm-rsl set threshold1 <threshold1> threshold2 <threshold2>

Table 124 RSL Thresholds CLI Parameters

Parameter Input Type Permitted Values Description

threshold1 Number -75 - -15 The first RSL threshold (dBm).

threshold2 Number -75 - -15 The second RSL threshold (dBm).

The following command sets the RSL thresholds to -30 dBm and -60 dBm, respectively.
radio [2/1]>rf pm-rsl set threshold1 -30 threshold2 -60

Configuring TSL Thresholds (CLI)

The number of seconds during which the TX Signal Level exceeds the TSL threshold are counted as TSL Exceed
Threshold Seconds. See Displaying RSL and TSL Levels (CLI).
To set the TSL threshold, enter the following command:
radio [x/x]>rf pm-tsl set threshold -15

Phn 3963 013v000

Page 645
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Phn 3963 013v000

Page 646
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Table 125 TSL Thresholds CLI Parameters

Parameter Input Type Permitted Values Description

threshold Number -10 - 34 The TSL threshold (dBm).

The following command sets the TSL threshold to 10 dBm:

radio [2/1]>rf pm-tsl set threshold 10

Displaying RSL and TSL Levels (CLI)

You can display the RSL (RX Signal Level) and TSL (TX Signal Level) PMs in either 15-minute or daily intervals.
To display RSL and TSL PMs in 15-minute intervals, enter the following command in radio view:
radio [x/x]>rf pm-rsl-tsl show interval 15min
To display RSL and TSL PMs in daily intervals, enter the following command in radio view:
radio [x/x]>rf pm-rsl-tsl show interval 24hr
The following is the output format of the rf pm-rsl-tsl show commands:

Phn 3963 013v000

Page 647
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Table 126 RSL and TSL PMs (CLI)

Parameter Description

Interval The number of the interval: 1-30 for daily PM reports, and 1-96 for 15 minute
PM reports.

Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. "1" in the column indicates that the values are not
reliable due to a possible power surge or power failure that occurred at that
time.

Min RSL (dBm) The minimum RSL (Received Signal Level) that was measured during the
interval.

Max RSL (dBm) The maximum RSL (Received Signal Level) that was measured during the
interval.

Min TSL (dBm) The minimum TSL (Transmit Signal Level) that was measured during the
interval.

Max TSL (dBm) The maximum TSL (Transmit Signal Level) that was measured during the
interval.

TSL exceed The number of seconds the measured TSL exceeded the threshold during the
threshold seconds interval. See Configuring TSL Thresholds (CLI).

RSL exceed The number of seconds the measured RSL exceeded RSL threshold 1 during
threshold1 the interval. See Configuring RSL Thresholds (CLI).
seconds

RSL exceed The number of seconds the measured RSL exceeded RSL threshold 2 during
threshold2 the interval. See Configuring RSL Thresholds (CLI).
seconds

Configuring the Signal Level Threshold (CLI)

To set the BER (Bit Error Rate) level above which a Signal Degrade alarm is issued for errors detected over the radio
link, enter the following command in radio view:
radio [x/x]>modem signal-degrade set threshold 1e-7
To display the Signal Degrade BER threshold, enter the following command in radio view:
radio [x/x]>modem signal-degrade show threshold

Phn 3963 013v000

Page 648
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Table 127 Signal Level Threshold CLI Parameters

Parameter Input Type Permitted Values Description

threshold Variable 1e -6 The BER level above which a Signal Degrade

1e -7 alarm is issued for errors detected over the
radio link.
1e -8
1e -9
1e -10
1e-11
1e-12
1e-13
1e-14
1e-15

The following command sets the Signal Degrade threshold at 1e-7:

radio [2/1]>modem signal-degrade set threshold 1e-7

Configuring the MSE Thresholds and Displaying the MSE PMs

(CLI)
To configure the MSE (Mean Square Error) threshold, enter the following command in radio view:
radio [x/x]>modem set mse-exceed threshold <threshold>
To display the currently configured MSE threshold, enter the following command in radio view:
radio [x/x]>modem show threshold-mse-exceed

Table 128 MSE CLI Parameters

Parameter Input Type Permitted Values Description

threshold Number -99 - -1 The MSE threshold.

To display MSE (Mean Square Error) PMs in 15-minute intervals, enter the following command in radio view:
radio [x/x]>modem pm-mse show interval 15min
The following is a partial sample output of the modem pm-mse show interval 15min command:

Phn 3963 013v000

Page 649
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

radio [2/1]>modem pm-mse show interval 15min

Modem MSE PM Table:

===================

Interval Integrity Min MSE (dB) Max MSE (dB)

Exceed
threshold
seconds
===============================================================
0 1 0.00 0.00 708
1 1 0.00 0.00 900
2 1 0.00 0.00 900
3 1 0.00 0.00 900
4 1 0.00 0.00 900
5 1 0.00 0.00 900
6 1 0.00 0.00 900
7 1 0.00 0.00 900
8 1 0.00 0.00 900
9 1 0.00 0.00 900
10 1 0.00 0.00 900

radio [2/1]>
To display MSE (Mean Square Error) PMs in daily intervals, enter the following command in radio view:
radio [x/x]>modem pm-mse show interval 24hr
The following is sample output of the modem pm-mse show interval 24hr command in radio view:
radio [2/1]>modem pm-mse show interval 24hr

Modem MSE PM Table:

===================

Interval Integrity Min MSE (dB) Max MSE (dB)

Exceed
threshold
seconds
===============================================================
0 1 0.00 0.00 63745
4 1 0.00 0.00 37062
5 1 0.00 0.00 3495
6 1 0.00 0.00 85976
8 1 0.00 0.00 46173
11 1 0.00 0.00 24185
15 1 0.00 0.00 85988
17 1 0.00 0.00 54981

radio [2/1]>modem

Phn 3963 013v000

Page 650
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Table 129 MSE PMs (CLI)

Parameter Description

Interval The number of the interval: 1-30 for daily PM reports, and 1-96 for 15 minute
PM reports.

Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. "1" in the column indicates that the values are not
reliable due to a possible power surge or power failure that occurred at that
time. A 1 and a 0 value in the Max MSE field may also indicate that the
modem was unlocked.

Min MSE (dB) Indicates the minimum MSE in dB, measured during the interval. A 0 in this
field and a 1 in the Integrity field may also indicate that the modem was
unlocked during the entire interval.

Max MSE (dB) Indicates the maximum MSE in dB, measured during the interval. A 0 in this
field and a 1 in the Integrity field may also indicate that the modem was
unlocked.

Exceed Threshold Indicates the number of seconds the MSE exceeded the MSE PM threshold
Seconds during the interval.

The following command sets the MSE threshold to -30:

radio [2/1]>modem set mse-exceed threshold -30

Configuring the XPI Thresholds and Displaying the XPI PMs

(CLI)
To configure the modem XPI threshold for calculating XPI Exceed Threshold seconds, enter the following command
in radio view:
radio[x/x]>modem set threshold-xpi-exceed threshold <threshold>
To display the currently configured XPI threshold, enter the following command in radio view:
radio[x/x]>modem show threshold-xpi-below

Table 130 XPI Threshold CLI Parameters

Parameter Input Type Permitted Values Description

threshold Number 0-99 The XPI threshold.

To display XPI PMs in 15-minute intervals, enter the following command in radio view:
radio[x/x]>modem pm-xpi show interval 15min

Phn 3963 013v000

Page 651
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

The following is a partial sample output of the modem pm-xpi show interval 15min command:
radio [2/1]>modem pm-xpi show interval 15min

Modem XPI PM Table:

===================

Interval Integrity Min XPI (dB) Max XPI (dB)

XPI below
threshold
seconds
===============================================================
1 1 55.00 0.00 0
2 1 55.00 0.00 0
3 1 55.00 0.00 0
4 1 55.00 0.00 0
5 1 55.00 0.00 0
6 1 55.00 0.00 0
7 1 55.00 0.00 0
8 1 55.00 0.00 0
9 1 55.00 0.00 0
10 1 55.00 0.00 0
11 1 55.00 0.00 0
12 1 55.00 0.00 0
13 1 55.00 0.00 0
14 1 55.00 0.00 0
15 1 55.00 0.00 0
16 1 55.00 0.00 0
17 1 55.00 0.00 0
18 1 55.00 0.00 0
19 1 55.00 0.00 0
20 1 55.00 0.00 0

radio [2/1]>
To display XPI PMs in daily intervals, enter the following command in radio view:
radio[x/x]>modem pm-xpi show interval 24hr

The following is a partial sample output of the modem pm-xpi show interval 24hr command:

Phn 3963 013v000

Page 652
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

radio [2/1]>modem pm-xpi show interval 24hr

Modem XPI PM Table:

===================

Interval Integrity Min XPI (dB) Max XPI (dB)

XPI below
threshold
seconds
===============================================================
1 1 55.00 0.00 0
2 1 55.00 0.00 0
3 1 55.00 0.00 0
4 1 55.00 0.00 0
5 1 55.00 0.00 0
6 1 55.00 0.00 0
7 1 55.00 0.00 0
8 1 55.00 0.00 0
9 1 55.00 0.00 0
10 1 55.00 0.00 0
11 1 55.00 0.00 0
12 1 55.00 0.00 0
13 1 55.00 0.00 0
14 1 55.00 0.00 0
15 1 55.00 0.00 0
16 1 55.00 0.00 0
17 1 55.00 0.00 0
18 1 55.00 0.00 0
19 1 55.00 0.00 0
20 1 55.00 0.00 0

radio [2/1]>

Table 131 XPI PMs (CLI)

Parameter Description

Interval The number of the interval: 1-30 for daily PM reports, and 1-96 for 15 minute
PM reports.

Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. "1" in the column indicates that the values are not
reliable due to a possible power surge or power failure that occurred at that
time.

Min XPI (dB) Indicates the lowest XPI value in dB, measured during the interval.

Max XPI (dB) Indicates the highest XPI value in dB, measured during the interval.

XPI Below Indicates the number of seconds the XPI value was lower than the XPI
Threshold threshold during the interval.
Seconds

The following command sets the XPI threshold for radio carrier 2 to 15:

Phn 3963 013v000

Page 653
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

radio[2/1]>modem set threshold-xpi-below threshold 15

Displaying ACM PMs and Configuring ACM Profile Thresholds

(CLI)
For each radio carrier, you can display the minimum and maximum ACM profile and the minimum and maximum
bitrate (throughput) per 15-minute or daily intervals.
You can also define two ACM profile thresholds for each radio carrier, and display the number of seconds per
interval that the radio’s ACM profile was below each of these thresholds. These thresholds trigger the following
alarms:
• Threshold 1 – When the ACM profile goes beneath this threshold, Alarm ID
1313 (Major) is raised. The alarm is cleared when the ACM profile is at or above
this threshold.
• Threshold 2 – When the ACM profile goes beneath this threshold, Alarm ID
1314 (Critical) is raised. The alarm is cleared when the ACM profile is at or
above this threshold.
To define the ACM thresholds, enter the following command in radio view:

radio [x/x]>mrmc pm-acm set threshold1 <threshold1> threshold2

<threshold2>

To display the ACM thresholds, enter the following command in radio view:

radio [x/x]>mrmc pm-acm get thresholds

To display ACM PMs in 15-minute intervals, enter the following command in radio view:
radio [x/x]>mrmc pm-acm show interval 15min
The following is a partial sample output of the modem pm-acm show interval 15min command:
radio [2/1]>mrmc pm-acm show interval 15min

Phn 3963 013v000

Page 654
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

MRMC PM Table:
==============

Interval Integrity Min profile Max profile Min bitrate Max bitrate
============================================================================
0 1 0 0 43389 43389
1 1 0 0 43389 43389
2 1 0 0 43389 43389
3 1 0 0 43389 43389
4 1 0 0 43389 43389
5 1 0 0 43389 43389
6 1 0 0 43389 43389
7 1 0 0 43389 43389
8 1 0 0 43389 43389
9 1 0 0 43389 43389
10 1 0 0 43389 43389

radio [2/1]>
To display ACM PMs in daily intervals, enter the following command in radio view:
radio [x/x]>mrmc pm-acm show interval 24hr
The following is sample output of the modem pm-acm show interval 24hr command:
radio [2/1]>mrmc pm-acm show interval 24hr

MRMC PM Table:
==============

Interval Integrity Min profile Max profile Min bitrate Max bitrate
===========================================================================
0 1 0 0 43389 43389
4 1 0 0 43389 43389
5 1 0 0 43389 43389
6 1 0 0 43389 43389
8 1 0 0 43389 43389
11 1 0 0 43389 43389
15 1 0 0 43389 43389
17 1 0 0 43389 43389

radio [2/1]>

Table 132 ACM PMs (CLI)

Parameter Description

threshold1 The higher ACM profile threshold (0-15). The default value is 0.

Threshold2 The lower ACM profile threshold (0-15). The default value is 0.

Interval The number of the interval: 1-30 for daily PM reports, and 1-96 for 15 minute
PM reports.

Phn 3963 013v000

Page 655
Chapter 16: Radio Configuration (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Parameter Description

Integrity Indicates whether the values received at the time and date of the measured
interval are reliable. "1" in the column indicates that the values are not
reliable due to a possible power surge or power failure that occurred at that
time.

Min profile Indicates the minimum ACM profile that was measured during the interval.

Max profile Indicates the maximum ACM profile that was measured during the interval.

Min bitrate Indicates the minimum total radio throughput (Mbps), delivered during the
interval.

Max bitrate Indicates the maximum total radio throughput (Mbps), delivered during the
interval.

Phn 3963 013v000

Page 656
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring and Viewing Radio PMs and Statistics (CLI)

Chapter 17: Ethernet Services and Interfaces

(CLI)
This section includes:
• Configuring Ethernet Services (CLI)
• Setting the MRU Size and the S-VLAN Ethertype (CLI)
• Configuring Ethernet Interfaces (CLI)
• Configuring Automatic State Propagation and Link Loss Forwarding (CLI)
• Viewing Ethernet PMs and Statistics (CLI)
Related topics:
• Configuring Link Aggregation (LAG) and LACP (Optional) (CLI)
• Quality of Service (QoS) (CLI)
• Ethernet Protocols (CLI)
• Performing Ethernet Loopback (CLI)

Phn 3963 013v000

Page 657
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Configuring Ethernet Services (CLI)

This section includes:

• Ethernet Services Overview (CLI)
• General Guidelines for Provisioning Ethernet Services (CLI)
• Defining Services (CLI)
• Configuring Service Points (CLI)
• Defining the MAC Address Forwarding Table for a Service (CLI)

Ethernet Services Overview (CLI)

Users can define up to 64 Ethernet services. Each service constitutes a virtual bridge that defines the connectivity
between logical ports in the PTP 820 network element.
This version of PTP 820 supports the following service types:
• Multipoint (MP)
• Point-to-Point (P2P)
• Management (MNG)
In addition to user-defined services, PTP 820 contains a pre-defined management service (Service ID 257). By
default, this service is operational.

Note
You can use the management service for in-band management. For instructions on configuring in-
band management, see Mate Management Access (IP Forwarding) (CLI)

A service point is a logical entity attached to a physical or logical interface. Service points define the movement of
frames through the service. Each service point includes both ingress and egress attributes. A Point-to-Point or
Multipoint service can hold up to 32 service points. A Management service can hold up 30 service points.
For a more detailed overview of the PTP 820 service-oriented Ethernet switching engine, refer to the Technical
Description for the PTP 820 product type you are using.

General Guidelines for Provisioning Ethernet Services (CLI)

When provisioning Ethernet services, it is recommended to follow these guidelines:
• Use the same Service ID for all service fragments along the path of the service.
• Do not re-use the same Service ID within the same region. A region is defined as consisting of all PTP 820
devices having Ethernet connectivity between them.
• Use meaningful EVC IDs.
• Give the same EVC ID (service name) to all service fragments along the path of the service.

Phn 3963 013v000

Page 658
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

• Do not reuse the same EVC ID within the same region.

It is recommended to follow these guidelines for creating service points:
• Always use SNP service points on NNI ports and SAP service points on UNI ports.
• For each logical interface associated with a specific service, there should never be more than a single service
point.
• The transport VLAN ID should be unique per service within a single region. That is, no two services should use
the same transport VLAN ID.

Defining Services (CLI)

Use the commands described in the following sections to define a service and its parameters. After defining the
service, you must add service points to the service in order for the service to carry traffic.

Adding a Service (CLI)

To add a service, enter the following command in root view:
root> ethernet service add type <service type> sid <sid> admin <service
admin mode> evc-id <evc-id> description <evc-description>

Table 133 Adding Ethernet Service CLI Parameters

Parameter Input Type Permitted Values Description

service type Variable p2p Defines the service type:

mp p2p - Point-to-Point
mp - Multipoint

sid Number Any unused value A unique ID for the service. Once you have added
from 1-256 the service, you cannot change the Service ID.
Service ID 257 is reserved for a pre-defined
management service.

service admin Variable Operational The administrative state of the service:

mode reserved operational - The service is functional.
reserved - The service is disabled until this
parameter is changed to operational. In this mode,
the service occupies system resources but is
unable to receive and transmit data.

evc-id Text String Up to 20 Defines an Ethernet Virtual Connection (EVC) ID.

characters. This parameter does not affect the network
element’s behavior, but is used by the NMS for
topology management.

evc- Text String Up to 64 A text description of the service. This parameter

description characters. does not affect the network element’s behavior,
but is used by the NMS for topology management.

Phn 3963 013v000

Page 659
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Example
The following command adds a Multipoint service with Service ID 18.
root> ethernet service add type mp sid 18 admin operational evc-id Ring_1
description east_west
The following command adds a Point-to-Point service with Service ID 10.
root> ethernet service add type p2p sid 10 admin operational evc-id
Ring_1 description east_west
These services are immediately enabled, although service points must be added to the services in order for the
services to carry traffic.

Entering Service View (CLI)

To view service details and set the service’s parameters, you must enter the service’s view level in the CLI.
To enter a service’s view level:
root> ethernet service sid <sid>

Table 134 Entering Ethernet Service View CLI Parameters

Parameter Input Type Permitted Values Description

sid Number Any unused value A unique ID for the service. Once you have added
from 1-256 the service, you cannot change the Service ID.
Service ID 257 is reserved for a pre-defined
management service.

Example
The following command enters service view for the service with Service ID 10:
root> ethernet service sid 10
The following prompt appears:
service[10]>

Showing Service Details (CLI)

To display the attributes of a service, go to service view for the service and enter the following command:
service[SID]>service info show
For example:
service[1]>service info show

Phn 3963 013v000

Page 660
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

service info:
service id: 1
service type: p2p
service admin: operational
Maximal MAC address learning entries: 131072
default cos: 0
cos mode: preserve-sp-cos-decision
EVC id: N.A.
EVC description: N.A.
split horizon group: disable
configured multicast grouping: no

service[1]>
To display the attributes of a service and its service points, go to service view for the service and enter the
following command:
service[SID]>service detailed-info show
For example:

To display a list of service points and their attributes, enter the following command in root view:
root>ethernet service show info sid <sid>

Table 135 Displaying Ethernet Service Details CLI Parameters

Parameter Input Type Permitted Values Description

sid Number Any defined Service None

ID.

For example:

Phn 3963 013v000

Page 661
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Configuring a Service’s Operational State (CLI)

To change the operational state of a service, go to service view for the service and enter the following command:
service[SID]>service admin set <service admin mode>
To display a service’s admin mode, go to service view for the service and enter the following command:
Service[SID]> service admin show state

Table 136 Ethernet Service Operational State CLI Parameters

Parameter Input Type Permitted Values Description

service admin Variable Operational The administrative state of the service:

mode reserved operational - The service is functional.
reserved - The service is disabled until this
parameter is changed to Operational. In this mode,
the service occupies system resources but is
unable to receive and transmit data.

Example
The following command sets Service 10 to be operational:
service[10]>service admin set operational

Configuring a Service’s CoS Mode and Default CoS (CLI)

The CoS mode determines whether or not frames passing through the service have their CoS modified at the
service level. The CoS determines the priority queue to which frames are assigned.
The CoS of frames traveling through a service can be modified on the interface level, the service point level, and
the service level. The service level is the highest priority, and overrides CoS decisions made at the interface and
service point levels. Thus, by configuring the service to apply a CoS value to frames in the service, you can define a
single CoS for all frames traveling through the service.
To set a service’s CoS mode, go to service view for the service and enter the following command:
service[SID]>service cos-mode set cos-mode <cos-mode>
If the CoS mode is set to default-cos, you must define the Default CoS. Use the following command to define
the Default CoS:
service[SID]>service default-cos set cos <cos>

Table 137 Ethernet Service CoS Mode CLI Parameters

Phn 3963 013v000

Page 662
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

cos-mode Variable default-cos default cos - Frames passing through the service
preserve-sp-cos- are assigned the default CoS defined below. This
decision CoS value overrides whatever CoS may have been
assigned at the service point or interface level.
preserve-sp-cos-decision - The CoS of frames
passing through the service is not modified by the
service.

cos Number 0–7 This value is assigned to frames at the service level
if cos-mode is set to default-cos. Otherwise, this
value is not used, and frames retain whatever CoS
value they were assigned at the service point or
logical interface level.

Examples
The following commands configure Service 10 to assign a CoS value of 7 to frames traversing the service:
service[10]>service cos-mode set cos-mode default-cos
service[10]>service default-cos set cos 7
The following command configures Service 10 to preserve the CoS decision made at the interface or service point
level for frames traveling through the service:
service[10]>service cos-mode set cos-mode preserve-sp-cos-decision

Configuring a Service’s EVC ID and Description (CLI)

To add or change the EVC ID of a service, go to service view for the service and enter the following command:
service[SID]>service evcid set <evcid>
To display a service’s EVC ID, go to service view for the service and enter the following command:
service[SID]>service evcid show
To add or change the EVC description of a service, go to service view for the service and enter the following
command:
service[SID]>service description set <evc description>
To display a service’s EVC description, go to service view for the service and enter the following command:
service[SID]>service description show

Table 138 Ethernet Service EVC CLI Parameters

Phn 3963 013v000

Page 663
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

evcid Text String Up to 20 Defines an Ethernet Virtual Connection (EVC) ID.

characters. This parameter does not affect the network
element’s behavior, but is used by the NMS for
topology management.

evc descriptio Text String Up to 64 A text description of the service. This parameter
n characters. does not affect the network element’s behavior,
but is used by the NMS for topology management.

Examples
The following commands add the EVC ID "East_West" and the EVC description "Line_to_Radio" to Service 10:
service[10]>service evcid set East_West
service[10]>service description set Line_to_Radio

Deleting a Service (CLI)

Before deleting a service, you must first delete any service points attached to the service (refer to Deleting a
Service Point (CLI)).
Use the following command to delete a service:
root>ethernet service delete sid <sid>
Use the following command to delete a range of services:
root>ethernet service delete sid <sid> to <sid>

Table 139 Deleting Ethernet Service CLI Parameters

Parameter Input Type Permitted Values Description

sid Number Any defined Service The Service ID.

ID.

Examples
The following command deletes Service 10:
root>ethernet service delete sid 10
The following command deletes Services 10 through 15:
root>ethernet service delete sid 10 to 15

Configuring Service Points (CLI)

This section includes:
• Service Points Overview (CLI)
• Service Point Classification (CLI)

Phn 3963 013v000

Page 664
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

• Adding a Service Point (CLI)

• Configuring Service Point Ingress Attributes (CLI)
• Configuring Service Point Egress Attributes (CLI)
• Displaying Service Point Attributes (CLI)
• Deleting a Service Point (CLI)

Service Points Overview (CLI)

Service points are logical interfaces within a service. A service point is a logical entity attached to a physical or
logical interface. Service points define the movement of frames through the service. Each service point includes
both ingress and egress attributes.
Each service point for a Point-to-Point or Multipoint service can be either a Service Access Point (SAP) or a Service
Network Point (SNP). A Point-to-Point service can also use Pipe service points.
• An SAP is equivalent to a UNI in MEF terminology and defines the connection of the user network with its
access points. SAPs are used for Point-to-Point and Multipoint traffic services.
• 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. SNPs are used for Point-to-Point and Multipoint traffic services.
• A Pipe service point is used to create traffic connectivity between two ports in a port-based manner (Smart
Pipe). In other words, all the traffic from one port passes to the other port.
Management services utilize Management (MNG) service points.
A Point-to-Point or Multipoint service can hold up to 32 service points. A management service can hold up to 30
service points.
Table 124 summarizes the service point types available per service type.

Table 140 Service Points per Service Type

Service Point Type

MNG SAP SNP Pipe

Management Yes No No No

Service Type Point-to-Point No Yes Yes Yes

Multipoint No Yes Yes No

Table 125 shows which service point types can co-exist on the same interface.

Table 141 Service Point Types per Interface

MNG SAP SNP Pipe

MNG Only one MNG SP is Yes Yes Yes

allowed per interface.

SAP Yes Yes No No

Phn 3963 013v000

Page 665
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

MNG SAP SNP Pipe

SNP Yes No Yes No

PIPE Yes No No Only one Pipe SP is allowed per

interface.

Service Point Classification (CLI)

This section includes:
• Overview of Service Point Classification (CLI)
• SAP Classification (CLI)
• SNP Classification (CLI)
• Pipe Service Point Classification (CLI)
• MNG Service Point Classification (CLI)

Overview of Service Point Classification (CLI)

Service points connect the service to the network element interfaces. It is crucial that the network element have a
means to classify incoming frames to the proper service point. This classification process is implemented by means
of a parsing encapsulation rule for the interface associated with the service point. This rule is called the Interface
Type, and is based on a key consisting of:
• The Interface ID of the interface through which the frame entered.
• The frame’s C-VLAN and/or S-VLAN tags.
The Interface Type provides a definitive mapping of each arriving frame to a specific service point in a specific
service. Since more than one service point may be associated with a single interface, frames are assigned to the
earliest defined service point in case of conflict.

SAP Classification (CLI)

SAPs can be used with the following Interface Types:
• All to one – All C-VLANs and untagged frames that enter the interface are classified to the same service point.
• Dot1q – A single C-VLAN is classified to the service point.
• QinQ – A single S-VLAN and C-VLAN combination is classified to the service point.
• Bundle C-Tag – A set of multiple C-VLANs is classified to the service point.
• Bundle S-Tag – A single S-VLAN and a set of multiple C-VLANs are classified to the service point.

SNP Classification (CLI)

SNPs can be used with the following Attached Interface Types:
• Dot1q – A single C-VLAN is classified to the service point.
• S-Tag – A single S-VLAN is classified to the service point.

Pipe Service Point Classification (CLI)

Pipe service points can be used with the following Attached Interface Types:
• Dot1q – All C-VLANs and untagged frames that enter the interface are classified to the same service point.

Phn 3963 013v000

Page 666
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

• S-Tag – All S-VLANs and untagged frames that enter the interface are classified to the same service point.

MNG Service Point Classification (CLI)

Management service points can be used with the following Interface Types:
• Dot1q – A single C-VLAN is classified to the 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.
Table 126 and Table 127 show which service point – Interface Type combinations can co-exist on the same
interface.

Table 142 Legal Service Point – Interface Type Combinations per Interface – SAP and SNP

SP Type SAP SNP

SP Attached 802.1q Bundle- Bundle- All to One Q in 802.1q S-Tag

Type Interface C S Q
Type

SAP 802.1q Yes Yes No No No No No

Bundle-C Yes Yes No No No No No

Bundle-S No No Yes No Yes No No

All to One No No No Only 1 All to No No No

One SP
Allowed

Q in Q No No Yes No Yes No No

SNP 802.1q No No No No No Yes No

S-Tag No No No No No No Yes

Pipe 802.1q No No No No No No No

S-Tag No No No No No No No

MNG 802.1q Yes Yes No No No Yes No

Q in Q No No Yes No Yes No No

S-Tag No No No No No No Yes

Table 143 Legal Service Point – Interface Type Combinations per Interface – Pipe and MNG

SP Type Pipe MNG

SP Attached 802.1q S-Tag 802.1q Q in Q S-Tag

Type Interface Type

SAP 802.1q No No Yes No No

Bundle-C No No Yes No No

Phn 3963 013v000

Page 667
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

SP Type Pipe MNG

SP Attached 802.1q S-Tag 802.1q Q in Q S-Tag

Type Interface Type

Bundle-S No No No Yes No

All to One No No No No No

Q in Q No No No Yes No

SNP 802.1q No No Yes No No

S-Tag No No No No Yes

Pipe 802.1q Only one No Yes No No

Pipe SP
Allowed

S-Tag No Only one No No Yes

Pipe SP
Allowed

MNG 802.1q Yes No Only 1 MNG No No

SP Allowed

Q in Q No No No Only 1 MNG No
SP Allowed

S-Tag No Yes No No Only 1 MNG

SP Allowed

Adding a Service Point (CLI)

The command syntax for adding a service point depends on the interface type of the service point. The interface
type determines which frames enter the service via this service point.
To add a service point with an All-to-One interface type, go to service view for the service and enter the following
command:
service[SID]>sp add sp-type <sp-type> int-type all-to-one spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> sp-name <sp-
name>
To add a service point with a Dot1q interface type, go to service view for the service and enter the following
command:
service[SID]>sp add sp-type <sp-type> int-type dot1q spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> vlan <vlan>
sp-name <sp-name>
To add a service point with an S-Tag interface type, go to service view for the service and enter the following
command:

Phn 3963 013v000

Page 668
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

service[SID]>sp add sp-type <sp-type> int-type s-tag spid <sp-id>

[interface|group] <interface|group> slot <slot> port <port> vlan <vlan>
sp-name <sp-name>
To add a service point with a Bundle-C interface type, go to service view for the service and enter the following
command:
service[SID]>sp add sp-type <sp-type> int-type bundle-c spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> sp-name <sp-
name>
To add a service point with a Bundle-S interface type, go to service view for the service and enter the following
command:
service[SID]>sp add sp-type <sp-type> int-type bundle-s spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> [outer-
vlan <outer-vlan>|vlan <vlan>] sp-name <sp-name>
Note: In SAP service points, use the parameter outer-vlan. In SP service points, use the
parameter vlan.
To add a service point with a Q-in-Q interface type, go to service view for the service and enter the following
command:
service[SID]>sp add sp-type <sp-type> int-type qinq spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> outer-
vlan <outer-vlan> inner-vlan <inner-vlan> sp-name <sp-name>
To add a Pipe service point, go to service view for the service and enter the following command:
service[SID]>sp add sp-type pipe int-type <int-type> spid <sp-id>
[interface|group] <interface|group> slot <slot> port <port> sp-name <sp-
name>

Phn 3963 013v000

Page 669
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 144 Add Service Point CLI Parameters

Parameter Input Type Permitted Values Description

sp-type Variable sap SAP - Service Access Point

snp SNP - Service Network Point
pipe PIPE - Pipe service point
mng MNG - Management service point

int-type Variable all-to-one Determines which frames enter the service via this
dot1q service point, based on the frame's VLAN tagging.
Since more than one service point may be
s-tag
associated with a single interface, frames are
bundle-c-tag assigned to the earliest defined service point in
bundle-s-tag case of conflict.
qinq all-to-one - All C-VLANs and untagged frames that
enter the interface are classified to the service
point. Only valid for SAP service point types.
dot1q - A single C-VLAN is classified to the service
point. Valid for all service point types.
s-tag - A single S- VLAN is classified to the service
point. Valid for SNP and MNG service point types.
bundle-c-tag - A set of multiple C-VLANs is
classified to the service point. Only valid for SAP
service point types.
bundle-s-tag - A single S-VLAN and a set of multiple
C-VLANs are classified to the service point. Only
valid for SAP service point types.
qinq - A single S-VLAN and C-VLAN combination is
classified to the service point. Valid for SAP and
MNG service point types.

sp-id Number 1-32 for P2P and This ID is unique within the service.
MP services.
1-30 for MNG
services.

interface Variable eth The Interface type for the service point:
radio eth - An Ethernet interface.
radio - A radio interface.
When you are defining the service point on a
group, such as a LAG, use the group parameter
instead of the interface parameter.

Phn 3963 013v000

Page 670
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

group Variable rp1 When you are defining the service point on an HSB
rp2 group (rp1 - rp-4), a LAG (lag1 - lag4), or a Multi-
Carrier ABC group (mc-abc1 - mc-abc4), use this
rp3
parameter instead of the interface parameter to
rp4 identify the group. The group must be defined
lag1 before you add the service point.
lag2 Note: Multi-Carrier ABC and HSB protection are
lag3 only relevant for PTP 820C units.
lag4
mc-abc1
mc-abc2
mc-abc3
mc-abc4

slot Number Ethernet: 1

Radio: 2

port Number For an Ethernet The port or radio carrier on which the service point
interface: 1-3 is located.
For a radio
interface in PTP
820C units: 1-2
For a radio
interface in PTP
820S: 1

vlan Number or 1-4094 (except Defines the VLAN classified to the service point.
Variable 4092 which is This parameter should not be included for service
reserved for the points with an interface type of bundle-C-tag. For
default instructions on attaching a bundled VLAN, refer to
management Attaching a VLAN Bundle to a Service Point (CLI).
service), or
This parameter is also not relevant for:
Untagged
Service points with an interface type of qinq and
all-to-one.
Pipe service points.

outer-vlan Number 1-4094 (except Defines the S-VLAN classified to the service point.
4092, which is This parameter is only relevant for service points
reserved for the with the interface type bundle-s-tag or qinq.
default
management
service), or
Untagged

Phn 3963 013v000

Page 671
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

inner-vlan Number 1-4094 (except Defines the C-VLAN classified to the service point.
4092, which is This parameter is only relevant for service points
reserved for the with the interface type qinq.
default
management
service), or
Untagged

sp-name Text string Up to 20 A descriptive name for the service point (optional).
characters.

Examples
The following command adds an SAP service point with Service Point ID 10 to Service 37, with interface type dot1q.
This service point is located on radio carrier 1. VLAN ID 100 is classified to this service point.
service[37]>sp add sp-type sap int-type dot1q spid 10 interface radio
slot 2 port 1 vlan 100 sp-name Radio
The following command adds an SAP service point with Service Point ID 10 to Service 37, with interface type
bundle-s-tag. This service point is located on radio carrier 2 in a PTP 820C unit. S-VLAN 100 is classified to the
service point.
service[37]>sp add sp-type sap int-type bundle-s-tag spid 10 interface
radio slot 2 port 2 outer-vlan 100 sp-name Radio
The following command adds an SAP service point with Service Point ID 10 to Service 37, with interface type qinq.
This service point is located on radio carrier 2 in a PTP 820C unit. S-VLAN 100 and C-VLAN 200 are classified to the
service point.
service[37]>sp add sp-type sap int-type qinq spid 10 interface radio slot
2 port 2 outer-vlan 100 inner-vlan 200 sp-name Radio
The following command adds an SAP service point with Service Point ID 10 to Service 37, with interface type all-to-
one. This service point is located on radio carrier 1. All traffic entering the system from that port is classified to the
service point.
service[37]>sp add sp-type sap int-type all-to-one spid 10 interface
radio slot 2 port 1 sp-name "all-to-one"
The following command adds an SNP service point with Service Point ID 10 to Service 37, with interface type s-tag.
This service point is located on radio carrier 1. S-VLAN 100 is classified to the service point.
service[37]>sp add sp-type snp int-type s-tag spid 10 interface radio
slot 2 port 1 vlan 100 sp-name Radio
The following command adds an SAP service point with Service Point ID 7 to Service 36, with interface type dot1q.
This service point is connected to HSB group 1 (rp1). VLAN ID 100 is classified to the service point.
service[36]>sp add sp-type sap int-type dot1q spid 7 group rp1 vlan 100
sp-name test1
The following command adds a Pipe service point with Service Point ID 1 to Service 1, with interface type dot1q.
This service point is connected to Eth1.

Phn 3963 013v000

Page 672
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

service[1]>sp add sp-type pipe int-type dot1q spid 1 interface eth slot 1
port 1 sp-name pipe_dot1q
The following commands create a Smart Pipe service between Eth1 and radio carrier 1. This service carries S-VLANs
and untagged frames between the two interfaces:
root> ethernet service add type p2p sid 10 admin operational evc-id test
description east_west

root>

root> ethernet service sid 10

service[10]>

service[10]>sp add sp-type pipe int-type s-tag spid 1 interface eth slot
1 port 1 sp-name test1

service[10]>

service[10]>sp add sp-type pipe int-type s-tag spid 2 interface radio

slot 2 port 1 sp-name test2

service[10]>

Configuring Service Point Ingress Attributes (CLI)

A service point’s ingress attributes are attributes that operate upon frames ingressing via the service point. This
includes how the service point handles the CoS of ingress frames and how the service point forwards frames to
their next destination within the service.
This section includes:
• Enabling and Disabling Broadcast Frames (CLI)
• CoS Preservation and Modification on a Service Point (CLI)
• Enabling and Disabling Flooding (CLI)

Enabling and Disabling Broadcast Frames (CLI)

To determine whether frames with a broadcast destination MAC address are allowed to ingress the service via this
service point, go to service view for the service and enter the following command:
service[SID]>sp broadcast set spid <sp-id> state <state>

Table 145 Enable/Disable Broadcast Frames CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

state Variable allow Determines whether frames with a broadcast

disable destination MAC address are allowed to ingress
the service via this service point.

Phn 3963 013v000

Page 673
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Examples
The following command allows frames with a broadcast destination MAC address to ingress Service 37 via Service
Point 1.
service[37]>sp broadcast set spid 1 state allow
The following command prevents frames with a broadcast destination MAC address from ingressing Service 37 via
Service Point 1.
service[37]>sp broadcast set spid 1 state disable

CoS Preservation and Modification on a Service Point (CLI)

The CoS of frames traversing a service can be modified on the logical interface, service point, and service level. The
service point can override the CoS decision made at the interface level. The service, in turn, can modify the CoS
decision made at the service point level.
To determine whether the service point modifies CoS decisions made at the interface level, go to service view for
the service and enter the following command:
service[SID]> sp cos-mode set spid <sp-id> mode <cos mode>
If you set cos-mode to sp-def-cos, you must then configure a default CoS. This CoS is applied to frames that
ingress the service point, but can be overwritten at the service level.
To configure the default CoS, go to service view for the service and enter the following command:
service[SID]>sp sp-def-cos set spid <sp-id> cos <cos>

Table 146 Service Point CoS Preservation CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

Phn 3963 013v000

Page 674
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

cos mode Variable sp-def-cos sp-def-cos - The service point re-defines the CoS of
interface-decision frames that pass through the service point,
according to the Default CoS (below). This decision
can be overwritten on the service level.
interface-decision - The service point preserves the
CoS decision made at the interface level. This
decision can still be overwritten at the service
level.
mac-da – The service point checks each frame
against a list of user-defined MAC DAs. If there is a
match, the service point applies to the frame the
CoS and Color defined for that MAC DA. If there is
no match, the service point preserves the CoS
decision made at the interface level. See
Classification Overview.
Note: For Bundle-S and Bundle-C service points, if
Cos Overwrite Valid is set to True, the CoS and
Color defined in the Attached VLAN page has
priority over the interface decision, but not over a
MAC DA match.

cos Number 0–7 If cos-mode is sp-def-cos, this is the CoS assigned

to frames that pass through the service point. This
decision can be overwritten on the service level.

Examples
The following commands configure Service Point 1 in Service 37 to apply a CoS value of 5 to frames that ingress the
service point:
service[37]>sp cos-mode set spid 1 mode sp-def-cos
service[37]>sp sp-def-cos set spid 1 cos 5
The following command configures Service Point 1 in Service 37 to preserve the CoS decision made at the interface
level for frames that ingress the service point:
service[37]>sp cos-mode set spid 1 mode interface-decision

Enabling and Disabling Flooding (CLI)

The ingress service point for a frame can forward the frame within the service by means of flooding or dynamic
MAC address learning in the service.
To enable or disable forwarding by means of flooding for a service point, go to service view for the service and
enter the following command:
service[SID]>sp flooding set spid <sp-id> state <flooding state>

Phn 3963 013v000

Page 675
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 147 Service Point Enable/Disable Flooding CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

state Variable Allow Determines whether incoming frames with

disable unknown MAC addresses are forwarded to other
service points via flooding.

Examples
The following command configures Service Point 1 in Service 37 to flood incoming frames with unknown MAC
addresses to other service points:
service[37]>sp flooding set spid 1 state allow
The following command configures Service Point 1 in Service 37 not to flood incoming frames with unknown MAC
addresses to other service points:
service[37]>sp flooding set spid 1 state disable

Configuring Service Point Egress Attributes (CLI)

A service point’s egress attributes are attributes that operate upon frames ingressing via the service point. This
includes VLAN preservation and marking attributes.
This section includes:
• Configuring VLAN and CoS Preservation (CLI)
• Configuring Service Bundles (CLI)
• Attaching a VLAN Bundle to a Service Point (CLI)

Configuring VLAN and CoS Preservation (CLI)

CoS and VLAN preservation determines whether the CoS and/or VLAN IDs of frames egressing the service via the
service point are restored to the values they had when the frame entered the service.

This section includes:

• Configuring C-VLAN CoS Preservation (CLI)
• Configuring C-VLAN Preservation (CLI)
• Configuring S-VLAN CoS Preservation (CLI)

Phn 3963 013v000

Page 676
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Appendix A: Configuring C-VLAN CoS

Preservation (CLI)
To configure CoS preservation for C-VLAN-tagged frames, go to service view for the service and enter the following
command:
service[SID]>sp cvlan-cos-preservation-mode set spid <sp-id> mode <c-
vlan cos preservation mode>

Table 148 C-VLAN CoS Preservation Mode CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

c-vlan cos Variable enable Select enable or disable to determine whether the
preservation disable original C-VLAN CoS value is preserved or restored
mode for frames egressing the service point.
enable - the C-VLAN CoS value of frames egressing
the service point is the same as the value when the
frame entered the service.
disable - the C-VLAN CoS value of frames egressing
the service point is set at whatever value might
have been re-assigned by the interface, service
point, or service, or whatever value results from
marking (see Configuring Marking (CLI)).

Examples
The following command enables C-VLAN CoS preservation for Service Point 1 on Service 37:
service[37]>sp cvlan-cos-preservation-mode set spid 1 mode enable
The following command disables C-VLAN CoS preservation for Service Point 1 on Service 37:
service[37]>sp cvlan-cos-preservation-mode set spid 1 mode disable

Phn 3963 013v000

Page 677
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Appendix B: Configuring C-VLAN

Preservation (CLI)
To configure VLAN preservation for C-VLAN-tagged frames, go to service view for the service and enter the
following command:
service[SID]>sp cvlan-preservation-mode set spid <sp-id> mode <c-
vlan preservation mode>

Table 149 C-VLAN Preservation CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

c-vlan Variable enable Determines whether the original C-VLAN ID is

preservation disable preserved or restored for frames egressing from
mode the service point.
enable - The C-VLAN ID of frames egressing the
service point is the same as the C-VLAN ID when
the frame entered the service.
disable - The C-VLAN ID of frames egressing the
service point is set at whatever value might have
been re-assigned by the interface, service point, or
service, or whatever value results from marking
(see Configuring Marking (CLI)).

Examples
The following command enables C-VLAN preservation for Service Point 1 on Service 37:
service[37]>sp cvlan-preservation-mode set spid 1 mode enable
The following command disables C-VLAN preservation for Service Point 1 on Service 37:
service[37]>sp cvlan-preservation-mode set spid 1 mode disable

Appendix C: Configuring S-VLAN CoS

Preservation (CLI)
To configure CoS preservation for S-VLAN-tagged frames, go to service view for the service and enter the following
command:

Phn 3963 013v000

Page 678
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

service[SID]>sp svlan-cos-preservation-mode set spid <sp-id> mode <s-

vlan cos preservation mode>

Phn 3963 013v000

Page 679
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 150 S-VLAN CoS Preservation CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

s-vlan cos Variable enable Select enable or disable to determine whether the
preservation disable original S-VLAN CoS value is preserved or restored
mode for frames egressing the service point.
enable - the S-VLAN CoS value of frames egressing
the service point is the same as the value when the
frame entered the service.
disable - the S-VLAN CoS value of frames egressing
the service point is set at whatever value might
have been re-assigned by the interface, service
point, or service, or whatever value results from
marking (see Configuring Marking (CLI)).

Examples
The following command enables S-VLAN CoS preservation for Service Point 1 on Service 37:
service[37]>sp svlan-cos-preservation-mode set spid 1 mode enable
The following command disables S-VLAN CoS preservation for Service Point 1 on Service 37:
service[37]>sp svlan-cos-preservation-mode set spid 1 mode disable

Configuring Service Bundles (CLI)

You can use service bundles to personalize common sets of egress queue attributes that can be applied to multiple
service points. In this version only one service bundle is supported.
To assign a service point to a service bundle, go to service view for the service and enter the following command:
service[SID]>sp egress-service-bundle set spid 1 service-bundle-id
<service-bundle-id>

Phn 3963 013v000

Page 680
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 151 Service Bundle CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.

service- Number 1 – 63 The service bundle assigned

bundle-id Note: In the current to the service point.
release, only
Service Bundle 1 is
supported.

Examples
The following command assigns Service Bundle 1 to Service Point 1 in Service 37.
service[37]>sp egress-service-bundle set spid 1 service-bundle-id 1

Attaching a VLAN Bundle to a Service Point (CLI)

For service points with an interface type of bundle-C-tag or bundle-S-tag, you must classify a group of VLANs (VLAN
Bundle) to the service point.
To classify a VLAN Bundle to a bundle-c-tag or bundle s-tag service point, go to service view for the service and
enter the following command:
service[SIP]>sp bundle cvlan attach spid <sp-id> vlan <vlan> to-vlan <to-
vlan>
To remove a VLAN Bundle from a bundle-c-tag or bundle-s-tag service point, go to service view for the service and
enter the following command:
service[SIP]>sp bundle cvlan remove spid <sp-id> vlan <vlan> to-vlan <to-
vlan>
To remove untagged frames from a bundle-c-tag or bundle s-tag service point, go to service view for the service
and enter the following command:
service[SIP]>sp bundle remove untagged spid <sp-id>
To display a service point’s attributes, including the VLANs classified to a bundle service point, go to service view
for the service to which the service point belongs and enter the following command:
service[SID]>sp service-point-info show spid <sp-id>

Phn 3963 013v000

Page 681
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 152 VLAN Bundle to Service Point CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and MP services. The Service Point ID.
1-30 for MNG services.

vlan Number 1-4094 (except 4092, which is The C-VLAN at the beginning of
reserved for the default the range of the VLAN Bundle.
management service)

to-vlan Number 1-4094 (except 4092, which is The C-VLAN at the end of the
reserved for the default range of the VLAN Bundle.
management service)

Examples
The following command classifies C-VLANs 100 through 200 to Service Point 1 in Service 37:
service[37]>sp bundle cvlan attach spid 1 vlan 100 to-vlan 200
The following command removes C-VLANs 100 through 200 from Service Point 1 in Service 37:
service[37]>sp bundle cvlan remove spid 1 vlan 100 to-vlan 200

Displaying Service Point Attributes (CLI)

To display a service point’s attributes, go to service view for the service to which the service point belongs and
enter the following command:
service[SID]>sp service-point-info show spid <sp-id>

Table 153 Display Service Point Attributes CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and MP services. The Service Point ID.
1-30 for MNG services.

Example
The following command displays the attributes of Service Point 1 in Service 37:
service[37]>sp service-point-info show spid 1

Deleting a Service Point (CLI)

You can only delete a service point if no VLAN bundles are attached to the service point. This is only relevant if the
interface type of the service point is bundle-c-tag or bundle-s-tag. For more information, refer to Attaching a VLAN
Bundle to a Service Point (CLI).
To delete a service point from a service, go to service view for the service and enter the following command:

Phn 3963 013v000

Page 682
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

service[SID]>sp delete spid <sp-id>

Phn 3963 013v000

Page 683
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Table 154 Delete Service Point Attributes CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and MP services. The Service Point ID.
1-30 for MNG services.

Example
The following command deletes Service Point 10 from Service 37:
service[37]>sp delete spid 10

Defining the MAC Address Forwarding Table for a Service (CLI)

This section includes:
• MAC Address Forwarding Table Overview (CLI)
• Setting the Maximum Size of the MAC Address Forwarding Table (CLI)
• Setting the MAC Address Forwarding Table Aging Time (CLI)
• Adding a Static MAC Address to the Forwarding Table (CLI)
• Displaying the MAC Address Forwarding Table (CLI)
• Flushing the MAC Address Forwarding Table (CLI)
• Enabling MAC Address Learning on a Service Point (CLI)

MAC Address Forwarding Table Overview (CLI)

PTP 820 performs MAC address learning per service. PTP 820 can learn up to 131,072 MAC addresses.
If necessary due to security issues or resource limitations, you can limit the size of the MAC address forwarding
table. The maximum size of the MAC address forwarding table is configurable per service in granularity of 16
entries.
When a frame arrives via a specific service point, the learning mechanism checks the MAC address forwarding
table for the service to which the service point belongs to determine whether that MAC address is known to the
service. If the MAC address is not found, the learning mechanism adds it to the table.
In parallel with the learning process, the forwarding mechanism searches the service’s MAC forwarding table for
the frame’s MAC address. If a match is found, the frame is forwarded to the service point associated with the MAC
address. If not, the frame is flooded to all service points in the service.

Setting the Maximum Size of the MAC Address Forwarding Table (CLI)
To limit the size of the MAC address forwarding table for a specific service, go to service view for the service and
enter the following command:
service[SID]>service mac-limit-value set <mac limit>

Table 155 MAC Address Forwarding Table Maximum Size CLI Parameters

Phn 3963 013v000

Page 684
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Parameter Input Type Permitted Values Description

mac limit Number 16 to 131,072, in multiples of The maximum MAC address

16 table size for the service. This
maximum only applies to
dynamic, not static, MAC
address table entries.

Example
The following command limits the number of dynamic MAC address forwarding table entries for Service 10 to 128:
service[10]>service mac-limit-value set 128

Setting the MAC Address Forwarding Table Aging Time (CLI)

You can configure a global aging time for dynamic entries in the MAC address forwarding table. Once this aging
time expires for a specific table entry, the entry is erased from the table.
To set the global aging time for the MAC address forwarding table, enter the following command:
root> ethernet service learning-ageing-time set time <time>
To display the global aging time for the MAC address forwarding table, enter the following command:
root> ethernet service learning-ageing-time show

Table 156 MAC Address Forwarding Table Aging Time CLI Parameters

Parameter Input Type Permitted Values Description

time Number 15 - 3825 The global aging time for the MAC address
forwarding table, in seconds.

Example
The following command sets the global aging time to 2500 seconds:
root> ethernet service learning-ageing-time set time 2500

Adding a Static MAC Address to the Forwarding Table (CLI)

You can add static entries to the MAC forwarding table. The global aging timer does not apply to static entries, and
they are not counted with respect to the maximum size of the MAC address forwarding table. It is the
responsibility of the user not to use all the entries in the table if the user also wants to utilize dynamic MAC
address learning.
To add a static MAC address to the MAC address forwarding table, go to service view for the service to which you
want to add the MAC address and enter the following command:
service[SID]>service mac-learning-table set-static-
mac <static mac> spid <sp-id>

Phn 3963 013v000

Page 685
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

To delete a static MAC address from the MAC address forwarding table, go to service view for the service from
which you want to delete the MAC address and enter the following command:
service[SID]>service mac-learning-table del-static-
mac <static mac> spid <sp-id>

Table 157 Adding Static Address to MAC Address Forwarding Table CLI Parameters

Parameter Input Type Permitted Values Description

static mac Six groups of The MAC address.

two
hexadecimal
digits

sp-id Number 1-32 The Service Point ID of the service point

associated with the MAC address.

Examples
The following command adds MAC address 00:11:22:33:44:55 to the MAC address forwarding table for Service 10,
and associates the MAC address with Service Point ID 1 on Service 10:
service[10]>service mac-learning-table set-static-
mac 00:11:22:33:44:55 spid 1
The following command deletes MAC address 00:11:22:33:44:55, associated with Service Point 1, from the MAC
address forwarding table for Service 10:
service[10]>service mac-learning-table del-static-
mac 00:11:22:33:44:55 spid 1

Displaying the MAC Address Forwarding Table (CLI)

You can display the MAC address forwarding table for an interface, a service, or for the entire unit.
To display the MAC address forwarding table for a service, go to service view for the service and enter the
following command:
service[SID]>service mac-learning-table show
To display the MAC address forwarding table for an interface, go to interface view for the interface and enter the
following command:
eth type xxx[x/x]>mac-learning-table show
To display the MAC address forwarding table for the entire unit, enter the following command:
root> ethernet generalcfg mac-learning-table show

Example
To display the MAC address forwarding table for GbE 1, enter the following commands:
root> ethernet interfaces eth slot 1 port 1

eth type eth[1/1]>mac-learning-table show

Phn 3963 013v000

Page 686
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Services (CLI)

Flushing the MAC Address Forwarding Table (CLI)

You can perform a global flush on the MAC address forwarding table. This erases all dynamic entries for all
services. Static entries are not erased.

Note
The ability to flush the MAC address forwarding table per-service and per-interface is planned for
future release.
To perform a global flush of the MAC address forwarding table, enter the following command:

root> ethernet service mac-learning-table set global-flush

Enabling MAC Address Learning on a Service Point (CLI)

You can enable or disable MAC address learning for specific service points. By default, MAC learning is enabled.
To enable or disable MAC address learning for a service point, go to service view for the service and enter the
following command:
service[SID]>sp learning-state set spid <sp-id> learning <learning>

Table 158 Enabling MAC Address Learning CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 The Service Point ID of the service point

associated with the MAC address.

learning Variable Enable Select enable or disable to enable or

disable disable MAC address learning for frames
that ingress via the service point.
When enabled, the service point learns
the source MAC addresses of incoming
frames and adds them to the MAC
address forwarding table.

Examples
The following command enables MAC address learning for Service Point 1 on Service 37:
service[37]>sp learning-state set spid 1 learning enable
The following command disables MAC address learning for Service Point 1 on Service 37:
service[37]>sp learning-state set spid 1 learning disable

Phn 3963 013v000

Page 687
Chapter 17: Ethernet Services and Interfaces (CLI) Setting the MRU Size and the S-VLAN Ethertype (CLI)

Setting the MRU Size and the S-VLAN Ethertype

(CLI)

The following parameters are configured globally for the PTP 820 switch:
• S- VLAN Ethertype – Defines the ethertype recognized by the system as the S-VLAN ethertype.
• C-VLAN Ethertype – Defines the ethertype recognized by the system as the C-VLAN ethertype. PTP 820
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. You can configure a global MRU for the system.

Note
The MTU is determined by the receiving frame and editing operation on the frame.
This section includes:

• Configuring the S-VLAN Ethertype (CLI)

• Configuring the C-VLAN Ethertype (CLI)
• Configuring the MRU (CLI)

Configuring the S-VLAN Ethertype (CLI)

To configure the S-VLAN Ethertype, enter the following command in root view:
root> ethernet generalcfg ethertype set svlan-value <ethertype>
To display the system S-VLAN ethertype, enter the following command in root view:
root> ethernet generalcfg ethertype show svlan

Table 159 Configure S-VLAN Ethertype CLI Parameters

Parameter Input Type Permitted Values Description

ethertype Hexadecimal 0x8100 Defines the ethertype recognized by the

0x88a8 system as the S-VLAN ethertype.
0x9100
0x9200

Example
For example, the following command sets the system S-VLAN ethertype to 0x88a8:
root> ethernet generalcfg ethertype set svlan-value 0x88a8

Phn 3963 013v000

Page 688
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Configuring the C-VLAN Ethertype (CLI)

The system C-VLAN Ethertype is set by the system as 0x8100.
To display the system C-VLAN ethertype, enter the following command in root view:
root> ethernet generalcfg ethertype show cvlan

Configuring the MRU (CLI)

To define the global size (in bytes) of the Maximum Receive Unit (MRU), enter the following command in root
view:
root> ethernet generalcfg mru set size <size>
To display the system MRU, enter the following command in root view:
root> ethernet generalcfg mru show

Table 160 Configure MRU CLI Parameters

Parameter Input Type Permitted Values Description

size Number 64 to 9612 Defines the global size (in bytes) of the
Maximum Receive Unit (MRU). Frames
that are larger than the global MRU will be
discarded.

Example
For example, the following command sets the system MRU to 9612:
root> ethernet generalcfg mru set size 9612

Configuring Ethernet Interfaces (CLI)

Related Topics:
• Enabling the Interfaces (CLI)
• Performing Ethernet Loopback (CLI)
• Configuring Ethernet Services (CLI)
• Quality of Service (QoS) (CLI)
P-20's switching fabric distinguishes between physical interfaces and logical interfaces. Physical and logical
interfaces serve different purposes in the switching fabric. In some cases, a physical interface corresponds to a
logical interface on a one-to-one basis. For some features, such as LAG, a group of physical interfaces can be joined
into a single logical interface.
The basic interface characteristics, such as media type, port speed, duplex, and auto-negotiation, are configured
on the physical interface level. Ethernet services, QoS, and OAM characteristics are configured on the logical
interface level.

Phn 3963 013v000

Page 689
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Note
You cannot change the configuration of the Management interface. By default, the Management
interface has the following configuration:
• Auto negotiation ON
• Full Duplex
• RJ45 - 100Mbps

This section includes:

• Entering Interface View (CLI)
• Displaying the Operational State of the Interfaces in the Unit (CLI)
• Viewing Interface Attributes (CLI)
• Configuring an Interface’s Media Type (CLI)
• Configuring an Interface’s Speed and Duplex State (CLI)
• Configuring an Interface’s Auto Negotiation State (CLI)
• Configuring an Interface’s IFG (CLI)
• Configuring an Interface’s Preamble (CLI)
• Adding a Description for the Interface (CLI)
• Displaying Interface Statistics (RMON) (CLI)

Entering Interface View (CLI)

To view interface details and set the interface’s parameters, you must enter the interface’s view level in the CLI.
Use the following command to enter an Ethernet interface’s view level:
root> ethernet interfaces eth slot <slot> port <port>
Use the following command to enter the radio interface’s view level:
root> ethernet interfaces radio slot <slot> port <port>
Use the following command to enter the view level of a group, such as a Multi-Carrier ABC group, an HSB
protection group, or a LAG:
root> ethernet interfaces group <group>

Table 161 Entering Interface View CLI Parameters

Parameter Input Type Permitted Values Description

size Number 64 to 9612 Defines the global size (in bytes) of the
Maximum Receive Unit (MRU). Frames
that are larger than the global MRU will be
discarded.

slot Number Ethernet: 1 Depends on the interface and unit type.

Radio in PTP 820C
or PTP 820S: 2

Phn 3963 013v000

Page 690
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Parameter Input Type Permitted Values Description

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (PTP
820C and PTP 820C-
HP): 2

group Variable rp1 To enter interface view for a group, enter

rp2 the group ID for one of the following types
of group:
rp3
HSB group (rp1 - rp-4)
rp4
LAG (lag1 - lag4)
lag1
Multi-Carrier ABC group (mc-abc1 - mc-
lag2
abc4)
lag3
Note: HSB and Multi-Carrier ABC groups
lag4 are only relevant for PTP 820C and PTP
mc-abc1 820C-HP.
mc-abc2
mc-abc3
mc-abc4

Example
The following command enters interface view for Ethernet port 3:
root> ethernet interfaces eth slot 1 port 3
The following prompt appears:
eth type eth [1/3]>
The following command enters interface view for radio interface 2 in a PTP 820C or PTP 820C-HP unit:
root> ethernet interfaces radio slot 2 port 2
The following prompt appears:
radio [2/2]>
The following command enters interface view for the radio interface in a PTP 820S unit:
root> ethernet interfaces radio slot 2 port 1
The following prompt appears:
radio [2/1]>
The following prompt appears:
radio [16/1]>

Phn 3963 013v000

Page 691
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

The following command enters interface view for LAG 1:

root> ethernet interfaces group lag1
The following prompt appears:
eth type group [64/1]>

Note
For simplicity, the examples in the following sections show the prompt for an Ethernet interface.

Displaying the Operational State of the Interfaces in the Unit

(CLI)
To display a list of all interfaces in the unit and their operational states, enter the following command:
root> platform if-manager show interfaces
The following is a sample output of this command:

Viewing Interface Attributes (CLI)

To display an interface’s attributes, go to interface view for the interface and enter the following command:
eth type eth [x/x]>summary show
To display an interface’s current operational state (up or down), go to interface view for the interface and enter
the following command:
eth type eth [x/x]>operational state show

Examples
The following command shows the attributes of GbE 1:
eth type eth [1/1]>summary show
The following command shows the operational state of GbE 1:
eth type eth [1/1]>operational state show

Configuring an Interface’s Media Type (CLI)

The Media Type attribute defines the physical interface Layer 1 media type. Permitted values are RJ-45 and SFP.
To configure an Ethernet interface’s Media Type, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>media-type state set <media type>

Phn 3963 013v000

Page 692
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Table 162 Interface Media Type CLI Parameters

Parameter Input Type Permitted Values Description

media type Variable rj45 Select the physical interface layer 1 media
sfp type:
RJ45 - An electrical (RJ-45) Ethernet
interface.
SFP - An optical (SFP) Ethernet interface.

Example
The following command sets GbE 1 to RJ-45 (electrical):
eth type eth [1/2]>media-type state set rj45
The following command sets GbE 2 to SFP:
eth type eth [1/2]>media-type state set sfp

Configuring an Interface’s Speed and Duplex State (CLI)

To configure an Ethernet interface’s maximum speed and duplex state, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>speed-and-duplex state set <speed-and-duplex state>

Table 163 Interface Speed and Duplex State CLI Parameters

Parameter Input Type Permitted Values Description

speed-and- Variable '10hd' This parameter sets the maximum speed

duplex state '10fd' and the duplex state of the interface. For
RJ-45 interfaces, any of the permitted
'100hd'
values except 10000fd can be configured.
'100fd' For SFP interfaces, only '1000fd' is
'1000fd' supported. For SFP+ interfaces (PTP 820E
‘10000fd’ R2H ESP models only), only 1000fd and
10000fd are supported.

Note
To use an SFP+ interface in 10G mode, the third-party switch must be running Pause Frame Flow
Control, as defined in IEEE 802.3x. It is also recommended to configure shapers on the third-party
switch so as to limit the packet flow from the switch to the PTP 820E unit to 2.5 Gbps.
After changing the speed of an SFP+ interface to or from 10000fd, you must reset the unit in order for
the change to take effect.
10HD is not supported in the current release.

Phn 3963 013v000

Page 693
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Examples
The following command sets GbE 1 to 100 Mbps, full duplex:
eth type eth [1/1]>speed-and-duplex state set '100fd'

Note
Before performing this command, you must verify that the media-type attribute is set to RJ45.

The following command sets GbE 1 to 1000 Mbps, full duplex:

eth type eth [1/1]>speed-and-duplex state set '1000fd'

Configuring an Interface’s Auto Negotiation State (CLI)

To configure an Ethernet interface’s auto-negotiation state, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>autoneg state set <autoneg state>

Table 164 Interface Auto Negotiation State CLI Parameters

Parameter Input Type Permitted Values Description

autoneg state Variable On Enables or disables auto-negotiation on

off the physical interface.

Example
The following command enables auto negotiation for GbE 2:
eth type eth [1/2]>autoneg state set on

Configuring an Interface’s IFG (CLI)

The IFG attribute represents the physical port Inter-frame gap. Although you can modify the IFG field length, it is
strongly recommended not to modify the default value of 12 bytes without a thorough understanding of how the
modification will impact traffic.
To configure an Ethernet interface’s IFG, go to interface view for the interface and enter the following command:
eth type eth [x/x]>ifg set <ifg>

Table 165 Interface IFG CLI Parameters

Parameter Input Type Permitted Values Description

ifg Number 6 - 15 Sets the interface’s IFG (in bytes).

Example
The following command sets the ifg for GbE 1 to 12:

Phn 3963 013v000

Page 694
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

eth type eth [1/1]>ifg set 12

The following displays the currently configured ifg for GbE 1:
eth type eth [1/1]>ifg get

Configuring an Interface’s Preamble (CLI)

Although you can modify an Ethernet interface’s preamble, it is strongly recommended not to modify the default
value of 8 bytes without a thorough understanding of how the modification will impact traffic.
To configure an Ethernet interface’s preamble, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>preamble set <preamble>

Table 166 Interface Preamble CLI Parameters

Parameter Input Type Permitted Values Description

preamble Number 6 - 15 Sets the interface’s preamble (in bytes).

Example
The following command sets the preamble for GbE 1 to 8:
eth type eth [1/1]>preamble set 8
The following command displays the current preamble for GbE 1:
eth type eth [1/1]>preamble get

Adding a Description for the Interface (CLI)

You can add a text description for an interface. To add a description, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>description set <description>
To delete a description, go to interface view for the interface and enter the following command:
eth type eth [x/x]>description delete
To display an interface’s description, go to interface view for the interface and enter the following command:
eth type eth [x/x]>description show

Table 167 Interface Description CLI Parameters

Parameter Input Type Permitted Values Description

description Text String Up to 40 characters Adds a text description to the interface.

Phn 3963 013v000

Page 695
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Ethernet Interfaces (CLI)

Example
The following command adds the description “Line” to GbE 1:
eth type eth [1/1]>description set Line

Displaying Interface Statistics (RMON) (CLI)

PTP 820 stores and displays statistics in accordance with RMON and RMON2 standards.
To display RMON statistics for a physical interface, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>rmon statistics show clear-on-read <clear-on-read>
layer-1 <layer-1>

Table 168 Interface Statistics (RMON) CLI Parameters

Parameter Input Type Permitted Values Description

clear-on-read Boolean yes If you enter yes, the statistics are cleared
no once you display them.

layer-1 Boolean yes yes – Statistics are represented as Layer 1

no statistics, including preamble and IFG.
no – Statistics are represented as Layer 2
statistics.

Example
The following commands enter interface view for GbE 1, and clear the statistics after displaying them.
root> ethernet interfaces eth slot 1 port 1

eth type eth [1/1]>rmon statistics show clear-on-read yes layer-1 yes
The following commands enter interface view for radio carrier 1 in a PTP 820C, PTP 820C-HP or PTP 820S unit, and
display statistics for the interface, without clearing the statistics.
root> ethernet interfaces radio slot 2 port 1

eth type radio[2/1]>rmon statistics show clear-on-read no layer-1 no

Phn 3963 013v000

Page 696
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Automatic State Propagation and Link Loss
Forwarding (CLI)

Configuring Automatic State Propagation and Link

Loss Forwarding (CLI)

Automatic state propagation enables propagation of radio failures back to the Ethernet port. You can also
configure Automatic State Propagation to close the Ethernet port based on a radio failure at the remote carrier.
Automatic state propagation is configured as pairs of interfaces. Each interface pair includes one Monitored
Interface and one Controlled Interface.
Automatic state propagation is configured as pairs of interfaces. Each interface pair includes one Monitored
Interface and one Controlled Interface. You can create multiple pairs using the same Monitored Interface and
multiple Controlled Interfaces.

Note
A radio interface that belongs to a LAG group cannot be used as a monitored interface.

The Monitored Interface is a radio interface, a radio protection, or Multi-Carrier ABC group. The Controlled
Interface is an Ethernet interface or LAG. An Ethernet interface can only be assigned to one Monitored interface.
Each Controlled Interface is assigned an LLF ID. If ASP trigger by remote fault is enabled on the remote side of the
link, the ASP state of the Controlled Interface is propagated to the Controlled Interface with the same LLF ID at the
remote side of the link. This means if ASP is triggered locally, it is propagated to the remote side of the link, but
only to Controlled Interfaces with LLF IDs that match the LLF IDs of the affected Controlled Interfaces on the local
side of the link.

Note
LLF requires an activation key. Without this activation key, only LLF ID 1 is available. See Configuring
the Activation Key (CLI).

The following events in the Monitored Interface trigger ASP:

• Radio LOF
• Radio Excessive BER
• Remote Radio LOF
• Remote Excessive BER
• Remove LOC
The user can also configure the ASP pair so that Radio LOF, Radio Excessive BER, or loss of the Ethernet connection
at the remote side of the link will also trigger ASP.
In addition, ASP is triggered if the Controlled Interface is a LAG, and the physical interfaces that belong to the LAG
are set to Admin = Down in the Interface Manager.
When a triggering event takes place:
• If the Controlled Interface is an electrical GbE port, the port is closed.
• If the Controlled Interface is an optical GbE port, the port is muted.

Phn 3963 013v000

Page 697
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Automatic State Propagation and Link Loss
Forwarding (CLI)

The Controlled Interface remains closed or muted until all triggering events are cleared.
In addition, when a local triggering event takes place, the ASP mechanism sends an indication to the remote side of
the link. Even when no triggering event has taken place, the ASP mechanism sends periodic update messages
indicating that no triggering event has taken place.
A trigger delay time can be configured, so that when a triggering event takes place, the ASP mechanism does not
propagate the event until this delay time has elapsed. A trigger delay from 0 to 10,000 ms can be set per LLD ID.

Note
It is recommended to configure both ends of the link to the same Automatic State Propagation
configuration.

To configure propagation of a radio interface failure to an Ethernet port, use the following command:
root> auto-state-propagation add eth-port-to-radio eth-slot <eth-slot>
eth-port <eth-port> radio-slot <radio-slot> radio-port <radio-port> llf-
id <llf-id>
To configure propagation of a Multi-Carrier ABC group failure to an Ethernet port, use the following command:
root> auto-state-propagation add eth-port-to-multi-radio-group eth-slot
<eth-slot> eth-port <eth-port> multi-radio-group <multi-radio-group> slot
1 type TCC llf-id <llf-id>
To configure propagation of an HSB-SD protection group failure to an Ethernet port, use the following command:
root> auto-state-propagation add eth-port-to-protection-group eth-slot
<eth-slot> eth-port <eth-port> protection-group <protection-group> llf-id
<llf-id>
To enable automatic state propagation on an Ethernet port, determine whether remote interface failures are also
propagated, enable CSF mode (optional), and set a trigger delay (optional), use the following command:
root> auto-state-propagation configure eth-port eth-slot <eth-slot> eth-
port <eth-port> asp-admin <asp-admin> remote-fault-trigger-admin <remote-
fault-trigger-admin> csf-mode-admin <csf-mode-admin> trigger-delay
<trigger-delay> llf-id <llf-id>

Note
In this command, the llf-id command is used optionally to change the LLF ID of the Ethernet port.

To delete automatic state propagation on an Ethernet port, use the following command:
root> auto-state-propagation delete eth-port eth-slot <eth-slot> eth-port
<eth-port>
To display all automatic state propagation configurations on the unit, use the following command:
root> auto-state-propagation show-config all
To display the automatic state propagation configuration for a specific Ethernet port, use the following command:
root> auto-state-propagation show-config eth-port eth-slot <eth-slot>
eth-port <eth-port>

Phn 3963 013v000

Page 698
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Automatic State Propagation and Link Loss
Forwarding (CLI)

Table 169: Automatic State Propagation to an Ethernet Port CLI Parameters

Parameter Input Type Permitted Values Description

eth-slot Number 1 Always enter 1.

eth-port Number 1-3 The interface to which you want to

propagate faults from the selected radio or
group.

radio-slot Number 2

radio-port Number Radio Carrier 1: 1 The radio interface.

Radio Carrier 2
(PTP 820C): 2

multi-radio-group Number 1-4 The Multi-Carrier ABC group failure of which

is propagated to the defined interface.
Note: Only relevant for PTP 820C units.

protection-group Number 1-4 The HSB-SD protection group failure of

which is propagated to the defined
interface.
Note: Only relevant for PTP 820C units.

llf-id Number 1-31 An ID for Link Loss Forwarding (LLF). When

remote-fault-trigger-admin is set to enable,
ASP events at the other side of the link are
propagated to Controlled Interfaces with LLF
IDs that match the LLF IDs of affected
Controlled Interfaces at the other side of the
link. LLF IDs are unique per Monitored
Interface. That is, if LLF ID 1 has been used
for a Controlled Interface that is grouped
with radio interface 1, that ID cannot be
used again for another Controlled Interface
grouped with radio interface 1. However, it
can be used for Controlled Interface
grouped with radio interface 2.

asp-admin Variable enable Enables or disables automatic state

disable propagation on the Ethernet interface.

remote-fault-trigger- Variable enable Determines whether faults on the remote

admin disable radio interface or group are propagated to
the local Ethernet interface.

Phn 3963 013v000

Page 699
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Automatic State Propagation and Link Loss
Forwarding (CLI)

Parameter Input Type Permitted Values Description

csf-mode-admin Variable enable Enables or disables ASP Management mode.

disable In ASP Management mode, the ASP
mechanism does not physically shut down
the Controlled Interface when ASP is
triggered. Instead, the ASP mechanism
sends a failure indication message. This
message is used to propagate the failure
indication to external equipment.

trigger-delay Number 0-10000 Sets a trigger delay time, in milliseconds.

When a triggering event takes place, the ASP
mechanism does not propagate the event
until this delay time has elapsed. By default,
the trigger-delay is 0 (no delay time). In XPIC
configurations, it is recommended to
configure a trigger-delay of 100 ms.

The following commands configure and enable automatic state propagation to propagate faults from radio
interface 1 to Ethernet ports 1 and 2, and from radio interface 2 to Ethernet port 3. ASP Management Safe mode is
disabled. Faults on the remote carrier are propagated to the local Ethernet ports as follows:
• A failure on the remote side of the link with radio interface 1 is propagated to any of local Ethernet ports 1 or
2 that share an LLF ID with an Ethernet interface in an ASP pair with the remote radio.
• A failure on the remote side of the link with radio interface 2 is propagated to Ethernet port 3 if it shares an
LLF ID with an Ethernet interface in an ASP pair with the remote radio.
• The trigger delay for Ethernet port 1 is 100 ms. The trigger delay for Ethernet port 2 is 5000 ms. There is no
trigger delay for Ethernet port 3.
root> auto-state-propagation add eth-port-to-radio eth-slot 1 eth-port 1
radio-slot 2 radio-port 1 llf-id 1

root> auto-state-propagation add eth-port-to-radio eth-slot 1 eth-port 2

radio-slot 2 radio-port 2 llf-id 2

root> auto-state-propagation configure eth-port eth-slot 1 eth-port 1

asp-admin enable remote-fault-trigger-admin enable csf-mode-admin disable
trigger-delay 100

root> auto-state-propagation configure eth-port eth-slot 1 eth-port 2

asp-admin enable remote-fault-trigger-admin enable csf-mode-admin disable
trigger-delay 5000

root> auto-state-propagation add eth-port-to-radio eth-slot 1 eth-port 3

radio-slot 1 radio-port 2 llf-id 1

root> auto-state-propagation configure eth-port eth-slot 1 eth-port 3

asp-admin enable remote-fault-trigger-admin enable csf-mode-admin disable
The following commands configure and enable automatic state propagation to propagate faults from Multi-Carrier
ABC group 1 to Ethernet port 1. Faults on the remote carrier are also propagated to Ethernet port 1 if the LLF ID of
an Ethernet port paired with the remote carrier is 4. CSF mode is disabled and the trigger delay is 300 ms.

Phn 3963 013v000

Page 700
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Automatic State Propagation and Link Loss
Forwarding (CLI)

root> auto-state-propagation add eth-port-to-multi-radio-group eth-slot 1

eth-port 1 multi-radio-group 1 llf-id 4

root> auto-state-propagation configure eth-port eth-slot 1 eth-port 1

asp-admin enable remote-fault-trigger-admin enable csf-mode-admin disable
trigger-delay 300
The following commands configure and enable automatic state propagation to propagate faults from 1+1 HSB
protection group 1 to Ethernet port 2. Faults on the remote carrier are not propagated to Ethernet port 2. ASP
Management Safe mode is disabled and there is no trigger delay.
root> auto-state-propagation add eth-port-to-protection-group eth-slot 1
eth-port 2 protection-group 1 llf-id 1

root> auto-state-propagation configure eth-port eth-slot 1 eth-port 2

asp-admin enable remote-fault-trigger-admin disable csf-mode-admin
disable

Phn 3963 013v000

Page 701
Chapter 17: Ethernet Services and Interfaces (CLI) Configuring Receipt of CSF PDUs (CLI)

Configuring Receipt of CSF PDUs (CLI)

When ASP Management Safe mode (CSF) is configured, the peer unit must be configured to receive
CSF PDUs. To enable the unit to receive CSF PDUs, enter the following command in root view:

root> ethernet soam csf receive set admin enable ifc-down

<yes|no>

CSF receive must be enabled in order for G.8032 ERPI topology changes to be initiated upon receipt
of a CSF PDU.
To disable this setting, enter the following command

root> ethernet soam csf receive set admin disable

The ifc-down parameter should usually be set to Yes. This means that all network protocols, LAG,
and other unit modules will treat the interface on which the CSF PDU was received as Operation
Status = Down. Also, a soam-csf-rdi-alarm will be raised to indicate that that relevant port is set to
Operational Status = Down due to ASP triggered by the remote unit.
To display the current setting of this parameter, enter the following command:

root> ethernet soam csf receive show

Phn 3963 013v000

Page 702
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

Viewing Ethernet PMs and Statistics (CLI)

PTP 820 stores and displays statistics in accordance with RMON and RMON2 standards. You can display various
peak TX and RX rates (per seconds) and average TX and RX rates (per seconds), both in bytes and in packets, for
each measured time interval. You can also display the number of seconds in the interval during which TX and RX
rates exceeded the configured threshold.
This section includes:
• Displaying RMON Statistics (CLI)
• Configuring Ethernet Port PMs and PM Thresholds (CLI)
• Displaying Ethernet Port PMs (CLI)
• Clearing Ethernet Port PMs (CLI)

Displaying RMON Statistics (CLI)

To display RMON statistics for a physical interface, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>rmon statistics show clear-on-read <clear-on-read>
layer-1 <layer-1>

Table 170 RMON Statistics CLI Parameters

Parameter Input Type Permitted Values Description

clear-on-read Boolean yes If you enter yes, the statistics are cleared
no once you display them.

layer-1 Boolean yes yes – Statistics are represented as Layer 1

no statistics, including preamble and IFG.
no – Statistics are represented as Layer 2
statistics.

The following commands bring you to interface view for Ethernet port 1, and clears the statistics after displaying
them.
root> ethernet interfaces eth slot 1 port 1

eth type eth [1/1]>rmon statistics show clear-on-read yes layer-1 yes
The following commands bring you to interface view for radio interface 2, without clearing the statistics.
root> ethernet interfaces radio slot 2 port 1

eth type radio[2/2]>rmon statistics show clear-on-read no layer-1 no

Phn 3963 013v000

Page 703
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

Configuring Ethernet Port PMs and PM Thresholds (CLI)

To enable the gathering of PMs for an Ethernet interface, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm set admin <enable|disable>
You can configure thresholds and display the number of seconds these thresholds were exceeded during a
specified interval.
To configure interface PM thresholds, go to interface view for the interface and enter the following command:
eth type eth [x/x]> pm set thresholds rx-layer1-rate-threshold <0-
4294967295> tx-layer1-rate-threshold <0-4294967295>
To display whether or not PM gathering is enabled for an Ethernet interface, as well as the configured thresholds,
go to interface view for the interface and enter the following command:
eth type eth [x/x]> pm show configuration

Table 171 Port PM Thresholds CLI Parameters

Parameter Input Type Permitted Values Description

rx-layer1-rate- Number 0-4294967295 The exceed threshold for port RX PMs, in

thershold bytes per second.

tx-layer1-rate- Number 0-4294967295 The exceed threshold for port TX PMs, in

thershold bytes per second.

The following commands bring you to interface view for Ethernet port 1, enable PM gathering, and set the
thresholds for RX and TX PMs at 850,000,000 bytes per second:
root> ethernet interfaces eth slot 1 port 1

eth type eth [1/1]>pm set admin enable

eth type eth [1/1]>pm set thresholds rx-layer1-rate-threshold 850000000

tx-layer1-rate-threshold 850000000

Displaying Ethernet Port PMs (CLI)

Note
The port PM results may be several pages long. Remember:
To view the next results page, press the space bar.
To end the list and return to the most recent prompt, press the letter q.

To display RX packet PMs in 15-minute intervals, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> pm show rx-packets interval 15min
To display RX packet PMs in 24-hour intervals, go to interface view for the interface and enter the following
command:

Phn 3963 013v000

Page 704
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

eth type eth [x/x]> pm show rx-packets interval 24hr

To display RX broadcast packet PMs in 15-minute intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show rx-bcast-packets interval 15min
To display RX broadcast packet PMs in 24-hour intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show rx-bcast-packets interval 24hr
To display RX multicast packet PMs in 15-minute intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show rx-mcast-packets interval 15min
To display RX multicast packet PMs in 24-hour intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show rx-mcast-packets interval 24hr
To display Layer 1 RX PMs, in bytes per second, in 15-minute intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show rx-bytes-layer1 interval 15min
To display Layer 1 RX PMs, in bytes per second, in 24-hour intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show rx-bytes-layer1 interval 24hr
To display Layer 2 RX PMs, in bytes per second, in 15-minute intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show rx-bytes-layer2 interval 15min
To display Layer 2 RX PMs, in bytes per second, in 24-hour intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show rx-bytes-layer2 interval 24hr
To display TX packet PMs in 15-minute intervals, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> pm show tx-packets interval 15min
To display TX packet PMs in 24-hour intervals, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> pm show tx-packets interval 24hr
To display TX broadcast packet PMs in 15-minute intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show tx-bcast-packets interval 15min
To display TX broadcast packet PMs in 24-hour intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show tx-bcast-packets interval 24hr
To display TX multicast packet PMs in 15-minute intervals, go to interface view for the interface and enter the
following command:

Phn 3963 013v000

Page 705
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

eth type eth [x/x]> pm show tx-mcast-packets interval 15min

To display TX multicast packet PMs in 24-hour intervals, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> pm show tx-mcast-packets interval 24hr
To display Layer 1 TX PMs, in bytes per second, in 15-minute intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show tx-bytes-layer1 interval 15min
To display Layer 1 TX PMs, in bytes per second, in 24-hour intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show tx-bytes-layer1 interval 24hr
To display Layer 2 TX PMs, in bytes per second, in 15-minute intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show tx-bytes-layer2 interval 15min
To display Layer 2 TX PMs, in bytes per second, in 24-hour intervals, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> pm show tx-bytes-layer2 interval 24hr

Table 172 Ethernet Port PMs

Parameter Definition

Interval For 24-hour intervals, displays the date of the interval. For 15-minute
intervals, displays the date and ending time of the interval.

Invalid data flag Indicates whether the values received during the measured interval are
valid. An x in the column indicates that the values are not valid (for
example, because of a power surge or power failure that occurred
during the interval).

Peak RX Packets The peak rate of RX packets per second for the measured time interval.

Average RX Packets The average rate of RX packets per second for the measured time
interval.

Peak RX Broadcast Packets The peak rate of RX broadcast packets per second for the measured
time interval.

Average RX Broadcast The average rate of RX broadcast packets per second for the measured
Packets time interval.

Peak RX Multicast Packets The peak rate of RX multicast packets per second for the measured time
interval.

Average RX Multicast The average rate of RX multicast packets per second for the measured
Packets time interval.

Peak RX Bytes in Layer1 The peak RX rate, in bytes per second, for the measured time interval
(including preamble and IFG).

Phn 3963 013v000

Page 706
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

Parameter Definition

Average RX Bytes in The average RX rate, in bytes per second, for the measured time
Layer1 interval (including preamble and IFG).

RX Bytes Layer1 Exceed The number of seconds during the measured time interval that the RX
Threshold (sec) rate exceeded the configured threshold.

Peak RX Bytes in Layer2 The peak RX rate, in bytes per second, for the measured time interval
(excluding preamble and IFG).

Average RX Bytes in The average RX rate, in bytes per second, for the measured time
Layer2 interval (excluding preamble and IFG).

Peak TX Packets The peak rate of TX packets per second for the measured time interval.

Average TX Packets The average rate of TX packets per second for the measured time
interval.

Peak TX Broadcast Packets The peak rate of TX broadcast packets per second for the measured
time interval.

Average TX Broadcast The average rate of TX broadcast packets per second for the measured
Packets time interval.

Peak TX Multicast Packets The peak rate of TX multicast packets per second for the measured time
interval.

Average TX Multicast The average rate of TX multicast packets per second for the measured
Packets time interval.

Peak TX Bytes in Layer1 The peak TX rate, in bytes per second, for the measured time interval
(including preamble and IFG).

Average TX Bytes in Layer1 The average TX rate, in bytes per second, for the measured time interval
(including preamble and IFG).

TX Bytes Layer1 Exceed The number of seconds during the measured time interval that the TX
Threshold (sec) rate exceeded the configured threshold.

Peak TX Bytes in Layer2 The peak TX rate, in bytes per second, for the measured time interval
(excluding preamble and IFG).

Average TX Bytes in Layer2 The average TX rate, in bytes per second, for the measured time interval
(excluding preamble and IFG).

Clearing Ethernet Port PMs (CLI)

To clear all PMs for an Ethernet interface, go to interface view for the interface and enter the following command:
eth type eth [x/x]> pm clear-all

Phn 3963 013v000

Page 707
Chapter 17: Ethernet Services and Interfaces (CLI) Viewing Ethernet PMs and Statistics (CLI)

Phn 3963 013v000

Page 708
Chapter 18: Quality of Service (QoS) (CLI) Viewing Ethernet PMs and Statistics (CLI)

Chapter 18: Quality of Service (QoS) (CLI)

This section includes:
• Configuring Classification (CLI)
• Configuring Policers (Rate Metering) (CLI)
• Configuring Marking (CLI)
• Configuring WRED (CLI)
• Configuring Shapers (CLI)
• Configuring Scheduling (CLI)
• Displaying Egress Statistics (CLI)

Phn 3963 013v000

Page 740
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Configuring Classification (CLI)

This section includes:

• Classification Overview (CLI)
• Configuring Ingress Path Classification on a Logical Interface (CLI)
• Configuring VLAN Classification and Override (CLI)
• Configuring 802.1p Classification (CLI)
• Configuring DSCP Classification (CLI)
• Configuring MPLS Classification (CLI)
• Configuring a Default CoS (CLI)
• Configuring Ingress Path Classification on a Service Point (CLI)
• Configuring Ingress Path Classification on a Service (CLI)

Classification Overview (CLI)

PTP 820 supports a hierarchical classification mechanism. The classification mechanism examines incoming frames
and determines their CoS and Color. The benefit of hierarchical classification is that it provides the ability to “zoom
in” or “zoom out”, enabling classification at higher or lower levels of the hierarchy. The nature of each traffic stream
defines which level of the hierarchical classifier to apply, or whether to use several levels of the classification
hierarchy in parallel.
The hierarchical classifier consists of the following levels:
• Logical interface-level classification
• Service point-level classification
• Service level classification

Configuring Ingress Path Classification on a Logical Interface

(CLI)
Logical interface-level classification enables you to configure classification on a single interface or on a number of
interfaces grouped tougher, such as a LAG group.
The classifier at the logical interface level supports the following classification methods, listed from highest to lowest
priority. A higher level classification method supersedes a lower level classification method:
• VLAN ID
• 802.1p bits.
• DSCP values.
• MPLS EXP field.
• Default CoS
PTP 820 performs the classification on each frame ingressing the system via the logical interface. Classification is
performed step by step from the highest priority to the lowest priority classification method. Once a match is found,
the classifier determines the CoS and Color decision for the frame for the logical interface-level.

Phn 3963 013v000

Page 741
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

For example, if the frame is an untagged IP Ethernet frame, a match will not be found until the third priority level
(DSCP). The CoS and Color values defined for the frame’s DSCP value will be applied to the frame.
You can disable some of these classification methods by configuring them as un-trusted. For example, if 802.1p
classification is configured as un-trusted for a specific interface, the classification mechanism does not perform
classification by UP bits. This is useful, for example, if classification is based on DSCP priority bits.
If no match is found at the logical interface level, the default CoS is applied to incoming frames at this level. In this
case, the Color of the frame is assumed to be Green.
Classification may also be performed by Destination MAC Address (MAC DA) at the service point level. When MAC DA
classification is enabled on a service point, the classification mechanism checks each frame ingressing the interface on
which the service point is defined against a list of user-defined MAC DAs. If there is a match, the mechanism applies
to the frame the CoS and Color defined for that MAC DA. Classification by MAC DA overrides the other classification
criteria at the service point level.

Configuring VLAN Classification and Override (CLI)

You can specify a specific CoS and Color for a specific VLAN ID. In the case of double-tagged frames, the match must
be with the frame’s outer VLAN. Permitted values are CoS 0 to 7 and Color Green or Yellow per VLAN ID. This is the
highest classification priority on the logical interface level, and overrides any other classification criteria at the logical
interface level.
To configure CoS and Color override based on VLAN ID, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>vlan-cos-override set outer-vlan-id <outer-vlan-id>
inner-vlan-id <inner-vlan-id> use-cos <use-cos> use-color <use-color>
To display configured VLAN-based CoS and Color override values, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>vlan-cos-override show outer-vlan-id <outer-vlan-id>
inner-vlan-id <inner-vlan-id>
To delete a set of VLAN-based CoS and Color override values, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>vlan-cos-override delete outer-vlan-id <outer-vlan-id>
inner-vlan-id <inner-vlan-id>

Table 173 VLAN Classification and Override CLI Parameters

Parameter Input Type Permitted Values Description

outer-vlan-id Number 1 – 4094 (except For double-tagged frames, the S-VLAN

4092, which is value mapped to the CoS and Color values
reserved for the defined in the command.
default management For single-tagged frames, the VLAN value
service) mapped to the CoS and Color values
defined in the command.

Phn 3963 013v000

Page 742
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Parameter Input Type Permitted Values Description

inner-vlan-id Number 1 – 4094 (except Optional. Include this parameter when

4092, which is you want to map double-tagged frames to
reserved for the specific CoS and Color values. When this
default management parameter is included in the command,
service) both the S-VLAN and the C-VLAN IDs must
match the configured outer-vlan-id
and inner-vlan-id values, respectively,
in order for the defined CoS and Color
values to be applied to the frame.

use-cos Number 0–7 The CoS value applied to matching frames.

use-color Variable green The Color applied to matching frames.

yellow

Examples
The following command configures the classification mechanism on GbE 1 to override the CoS and Color values of
frames with S-VLAN ID 10 and C-VLAN ID 30 with a CoS value of 6 and a Color value of Green:
eth type eth [1/1]>vlan-cos-override set outer-vlan-id 10 inner-vlan-id 30
use-cos 6 use-color green
The following command configures the classification mechanism on GbE 2 to override the CoS and Color values of
frames with VLAN ID 20 with a CoS value of 5 and a Color value of Green:
eth type eth [1/2]>vlan-cos-override set outer-vlan-id 20 use-cos 5 use-
color green
The following command displays the CoS and Color override values for frames that ingress on GbE 1, with S-VLAN ID
10 and C-VLAN ID 20:
eth type eth [1/1]>vlan-cos-override show outer-vlan-id 10 inner-vlan-id 20
The following command displays all CoS and Color override values for frames that ingress on GbE 2:
eth type eth [1/2]>vlan-cos-override show all
The following command deletes the VLAN to CoS and Color override mapping for frames that ingress on GbE 1, with
S-VLAN ID 10 and C-VLAN ID 20:
eth type eth [1/1]>vlan-cos-override delete outer-vlan-id 10 inner-vlan-id
20

Configuring 802.1p Classification (CLI)

When 802.1p classification is set to Trust mode, the interface performs QoS and Color classification according to user-
configurable tables for 802.1q UP bit (C-VLAN frames) or 802.1AD UP bit (S-VLAN frames) to CoS and Color
classification.
This section includes:
• Configuring Trust Mode for 802.1p Classification (CLI)
• Modifying the C-VLAN 802.1 UP and CFI Bit Classification Table (CLI)
• Modifying the S-VLAN 802.1 UP and DEI Bit Classification Table (CLI)

Phn 3963 013v000

Page 743
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Configuring Trust Mode for 802.1p Classification (CLI)

To define the trust mode for 802.1p classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification set 802.1p <802.1p>
To display the trust mode for 802.1p classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification show 802.1p state

Table 174 802.1p Trust Mode CLI Parameters

Parameter Input Type Permitted Values Description

802.1p Variable trust Enter the interface's trust mode for user priority
un-trust (UP) bits:
trust – The interface performs QoS and color
classification according to UP and CFI/DEI bits
according to user-configurable tables for 802.1q
UP bits (C-VLAN frames) or 802.1AD UP bits (S-
VLAN frames). VLAN UP bit classification has
priority over DSCP and MPLS classification, so
that if a match is found with the UP bit of the
ingressing frame, DSCP values and MPLS bits are
not considered.
un-trust – The interface does not consider
802.1 UP bits during classification.

Examples
The following command enables 802.1p trust mode for GbE 1:
eth type eth [1/1]>classification set 802.1p trust
The following command disables 802.1p trust mode for GbE 1:
eth type eth [1/1]>classification set 802.1p un-trust

Modifying the C-VLAN 802.1 UP and CFI Bit Classification Table (CLI)
The following table shows the default values for the C-VLAN 802.1 UP and CFI bit classification table.

Table 175 C-VLAN 802.1 UP and CFI Bit Classification Table Default Values

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

Phn 3963 013v000

Page 744
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

802.1 UP CFI CoS(Configurable) Color(Configurable)

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

To modify the C-VLAN 802.1 UP and CFI bit classification table, enter the following command:
root> ethernet qos 802.1q-up-bits-mapping-tbl set 802.1p <802.1p> cfi <cfi>
cos <cos> color <color>
To display the C-VLAN 802.1 UP and CFI bit classification table, enter the following command:
root> ethernet qos 802.1q-up-bits-mapping-tbl show

Table 176 C-VLAN 802.1 UP and CFI Bit Classification Table CLI Parameters

Parameter Input Type Permitted Values Description

802.1p Number 0–7 The User Priority (UP) bit to be mapped.

cfi Number 0–1 The CFI bit to be mapped.

cos Number 0–7 The CoS assigned to frames with the designated
UP and CFI.

color Variable green The Color assigned to frames with the designated
yellow UP and CFI.

Examples
The following command maps frames with an 802.1p UP bit value of 1 and a CFI bit value of 0 to CoS 1 and Green
color:
root> ethernet qos 802.1q-up-bits-mapping-tbl set 802.1p 1 cfi 0 cos 1
color green

Modifying the S-VLAN 802.1 UP and DEI Bit Classification Table (CLI)
The following table shows the default values for the S-VLAN 802.1 UP and DEI bit classification table.

Table 177 S-VLAN 802.1 UP and DEI Bit Classification Table Default Values

Phn 3963 013v000

Page 745
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

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

To modify the S-VLAN 802.1 UP and DEI bit classification table, enter the following command:
root> ethernet qos 802.1ad-up-bits-mapping-tbl set 802.1p <802.1p> dei
<dei> cos <cos> color <color>
To display the S-VLAN 802.1 UP and CFI bit classification table, enter the following command:
root> ethernet qos 802.1ad-up-bits-mapping-tbl show

Table 178 S-VLAN 802.1 UP and DEI Bit Classification Table CLI Parameters

Parameter Input Type Permitted Values Description

802.1p Number 0–7 The User Priority (UP) bit to be mapped.

dei Number 0-1 The DEI bit to be mapped.

cos Number 0–7 The CoS assigned to frames with the designated
UP and CFI.

color Variable green The Color assigned to frames with the designated
yellow UP and CFI.

Example
The following command maps frames with an 802.1ad UP bit value of 7 and a DEI bit value of 0 to CoS 7 and Green
color:
root> ethernet qos 802.1ad-up-bits-mapping-tbl set 802.1p 7 dei 0 cos 7
color green
Phn 3963 013v000
Page 746
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Configuring DSCP Classification (CLI)

When DSCP classification is set to Trust mode, the interface performs QoS and Color classification according to a user-
configurable DSCP to CoS and Color classification table. 802.1p classification has priority over DSCP Trust Mode, so
that if a match is found on the 802.1p level, DSCP is not considered.
This section includes:
• Configuring Trust Mode for DSCP Classification (CLI)
• Modifying the DSCP Classification Table (CLI)

Configuring Trust Mode for DSCP Classification (CLI)

To define the trust mode for DSCP classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification set ip-dscp <ip-dscp>
To display the trust mode for DSCP classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification show 802.1p state

Phn 3963 013v000

Page 747
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Table 179 Trust Mode for DSCP CLI Parameters

Parameter Input Type Permitted Values Description

ip-dscp Variable trust Select the interface's trust mode for DSCP
un-trust classification:
trust – The interface performs QoS and color
classification according to a user-configurable
table for DSCP to CoS and color classification.
DSCP classification has priority over MPLS
classification, so that if a match is found with the
DSCP value of the ingressing frame, MPLS bits are
not considered.
un-trust – The interface does not consider
DSCP during classification.

Examples
The following command enables DSCP trust mode for GbE 1:
eth type eth [1/1]>classification set ip-dscp trust
The following command disables DSCP trust mode for GbE 1:
eth type eth [1/1]>classification set ip-dscp un-trust

Modifying the DSCP Classification Table (CLI)

PTP 820 units have a DSCP classification table with 24 pre-defined entries. Each entry includes the following criteria:
◦ DSCP – The DSCP value to be mapped.
◦ Binary – The binary representation of the DSCP value.
◦ Description – A description of the DSCP value.
◦ CoS – The CoS assigned to frames with the designated DSCP value.
◦ Color – The Color assigned to frames with the designated DSCP value.
You can modify the Description, CoS, and Color for any of the pre-defined entries. You can also add and delete
entries. The maximum number of entries is 32.
The following table shows the default values for the DSCP classification table.

Table 180 DSCP Classification Table Default Values

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

Phn 3963 013v000
Page 748
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

DSCP DSCP (bin) Description CoS (Configurable) Color (Configurable)

26 011010 AF31 3 Green

28 011100 AF32 3 Yellow

30 011110 AF33 3 Yellow

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

51 110011 DSCP_51 6 Green

52 110100 DSCP_52 6 Green

54 110110 DSCP_54 6 Green

56 111000 CS7 7 Green

To modify the DSCP classification table, enter the following command:

root> ethernet qos dscp-mapping-tbl set dscp <dscp> cos <cos> color <color>
To display the DSCP classification table, enter the following command:
root> ethernet qos dscp-mapping-tbl show

Phn 3963 013v000

Page 749
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Table 181 Modify DSCP Classification Table CLI Parameters

Parameter Input Type Permitted Values Description

dscp Number Valid DSCP values. The DSCP value to be mapped.

Refer to the DSCP
column in the table
above.

cos Number 0–7 The CoS assigned to frames with the

designated DSCP value.

color Variable green The Color assigned to frames with the

yellow designated DSCP value.

description String A description of the entry.

Example
The following command maps frames with DSCP value of 10 to CoS 1 and Green color:
root> ethernet qos dscp-mapping-tbl set dscp 10 cos 1 color green

Configuring MPLS Classification (CLI)

When MPLS classification is set to Trust mode, the interface performs QoS and Color classification according to a
user-configurable MPLS EXP bit to CoS and Color classification table. Both 802.1p and DSCP classification have priority
over MPLS Trust Mode, so that if a match is found on either the 802.1p or DSCP levels, MPLS bits are not considered.
This section includes:
• Configuring Trust Mode for MPLS Classification (CLI)
• Modifying the MPLS EXP Bit Classification Table (CLI)

Configuring Trust Mode for MPLS Classification (CLI)

To define the trust mode for MPLS classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification set mpls <mpls>
To display the trust mode for MPLS classification, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification show mpls state

Phn 3963 013v000

Page 750
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Table 182 Trust Mode for MPLS CLI Parameters

Parameter Input Type Permitted Values Description

mpls Variable Trust Select the interface's trust mode for MPLS
un-trust bits:
trust – The interface performs QoS and
color classification according to a user-
configurable table for MPLS EXP to CoS
and color classification.
un-trust – The interface does not
consider MPLS bits during classification.

Examples
The following command enables MPLS trust mode for GbE 1:
eth type eth [1/1]>classification set mpls trust
The following command disables MPLS trust mode for GbE 1:
eth type eth [1/1]>classification set mpls un-trust

Modifying the MPLS EXP Bit Classification Table (CLI)

The following table shows the default values for the MPLS EXP bit classification table.

Table 183 MPLS EXP Bit Classification Table Default Values

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

To modify the MPLS EXP bit classification table, enter the following command:
root> ethernet qos mpls-exp-bits-mapping-tbl set mpls-exp <mpls-exp> cos
<cos> color <color>
To display the MPLS EXP bit classification table, enter the following command:
root> ethernet qos mpls-mapping-tbl show
Table 184 MPLS EXP Bit Classification Table Modification CLI Parameters

Parameter Input Type Permitted Values Description

mpls-exp Number 0–7 The MPLS EXP bit to be mapped.

Phn 3963 013v000

Page 751
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

Parameter Input Type Permitted Values Description

cos Number 0–7 The CoS assigned to frames with the

designated MPLS EXP bit value.

color Variable green The Color assigned to frames with the

yellow designated MPLS EXP bit value.

Example
The following command maps frames with MPLS EXP bit value of 4 to CoS 4 and Yellow color:
root> ethernet qos mpls-exp-bits-mapping-tbl set mpls-exp 4 cos 4 color
yellow

Configuring MAC DA Classification (CLI)

You can determine whether classification is performed by MAC DA in the service
point’s CoS Mode parameter. See Classification Overview.
To add an entry to the MAC DA classification table, enter the following command in root view:

root>ethernet generalcfg mac-da add mac <MAC address> color

<green|yellow>

To edit an entry to the MAC DA classification table, enter the following command in root view:

root>ethernet generalcfg mac-da edit mac <MAC address> color

<green|yellow>

To delete an entry to the MAC DA classification table, enter the following command in root view:

root>ethernet generalcfg mac-da delete mac <MAC address>

The following command adds MAC address 00:11:22:33:44:55 to the MAC DA classification table, with
a CoS of 7 and the Color green.

root>ethernet generalcfg mac-da add mac 00:11:22:33:44:55 cos 7

color green
The following command changes the CoS assigned to this MAC address to 6.

root>ethernet generalcfg mac-da edit mac 00:11:22:33:44:55 cos

6 color green

The following command deletes this MAC address.

root>ethernet generalcfg mac-da delete mac 00:11:22:33:44:55

Configuring a Default CoS (CLI)

You can define a default CoS value for frames passing through the interface. This value can be overwritten on the
service point and service level. The Color is assumed to be Green.

Phn 3963 013v000

Page 752
Chapter 18: Quality of Service (QoS) (CLI) Configuring Classification (CLI)

To define a default CoS value for an interface, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification set default-cos <default-cos>
To display the default CoS value for an interface, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>classification show default-cos

Table 185 Default CoS CLI Parameters

Parameter Input Type Permitted Values Description

default-cos Number 0–7 Enter the default CoS value for frames
passing through the interface. This value
can be overwritten on the service point
and service level.

Example
The following command sets the default CoS for GbE 1 as 7:
eth type eth [1/1]>classification set default-cos 7

Configuring Ingress Path Classification on a Service Point (CLI)

For instruction on configuring ingress path classification on a service point, see CoS Preservation and Modification on
a Service Point (CLI).

Configuring Ingress Path Classification on a Service (CLI)

For instruction on configuring ingress path classification on a service, see Configuring a Service’s CoS Mode and
Default CoS (CLI).

Phn 3963 013v000

Page 753
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Configuring Policers (Rate Metering) (CLI)

This section includes:

• Overview of Rate Metering (Policing) (CLI)
• Configuring Rate Meter (Policer) Profiles (CLI)
• Displaying Rate Meter Profiles (CLI)
• Deleting a Rate Meter Profile (CLI)
• Attaching a Rate Meter (Policer) to an Interface (CLI)
• Configuring the Line Compensation Value for a Rate Meter (Policer) (CLI)
• Displaying Rate Meter Statistics for an Interface (CLI)

Overview of Rate Metering (Policing) (CLI)

The PTP 820 switching fabric supports hierarchical policing on the logical interface level. You can define up to 250 rate
meter (policer) profiles.

Note
Policing on the service point level, and the service point and CoS level, is planned for future release.

The PTP 820's policer mechanism is based on a dual leaky bucket mechanism (TrTCM). The policers can change a
frame’s color and CoS settings based on CIR/EIR + CBS/EBS, which makes the policer mechanism a key tool for
implementing bandwidth profiles and enabling operators to meet strict SLA requirements.
The output of the policers is a suggested color for the inspected frame. Based on this color, the queue management
mechanism decides whether to drop the frame or to pass it to the queue.

Configuring Rate Meter (Policer) Profiles (CLI)

To add a rate meter (policer) profile, enter the following command:
root> ethernet qos rate-meter add profile-id <profile-id> cir <cir> cbs
<cbs> eir <eir> ebs <ebs> color-mode <color-mode> coupling-flag <coupling-
flag> rate-meter-profile-name <rate-meter-profile-name>
To edit an existing rate meter (policer) profile, enter the following command:
root> ethernet qos rate-meter edit profile-id <profile-id> cir <cir> cbs
<cbs> eir <eir> ebs <ebs> color-mode <color-mode> coupling-flag <coupling-
flag> rate-meter-profile-name <rate-meter-profile-name>

Table 186 Rate Meter Profile CLI Parameters

Phn 3963 013v000

Page 754
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Parameter Input Type Permitted Values Description

profile-id Number 1 – 250 A unique ID for the rate meter (policer)

profile.

cir Number 0, or 64,000 - The Committed Information Rate (CIR)

1,000,000,000 defined for the rate meter (policer), in bits
per second.
If the value is 0, all incoming CIR traffic is
dropped.

cbs Number 0 - 8192 The Committed Burst Rate (CBR) for the
rate meter (policer), in Kbytes.

eir Number 0, or 64,000 - The Excess Information Rate (EIR) for the
1,000,000,000 rate meter (policer), in bits per second.
If the value is 0, all incoming EIR traffic is
dropped.

ebs Number 0 - 8192 The Excess Burst Rate (EBR) for the rate
meter (policer), in Kbytes.

color-mode Variable color-blind Determines how the rate meter (policer)

color-aware treats frames that ingress with a CFI or DEI
field set to 1 (yellow). Options are:
color aware – All frames that ingress
with a CFI/DEI field set to 1 (yellow) are
treated as EIR frames, even if credits
remain in the CIR bucket.
color blind – All ingress frames are
treated as green regardless of their
CFI/DEI value. A color-blind policer
discards any former color decisions.

coupling-flag Variable enable When enabled, frames that ingress as

disable yellow may be converted to green when
there are no available yellow credits in the
EIR bucket. Only relevant in color-
aware mode.

rate-meter- Text string Up to 20 characters. A description of the rate meter (policer)

profile-name profile.

Examples
The following command creates a rate meter (policer) profile with Profile ID 50, named “64k.”
root> ethernet qos rate-meter add profile-id 50 cir 64000 cbs 5 eir 64000
ebs 5 color-mode color-blind coupling-flag disable rate-meter-profile-name
64k
This profile includes the following parameters:
• CIR – 64,000 bps
• CBS – 5 Kbytes
• EIR – 64,000 bps
Phn 3963 013v000
Page 755
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

• EBS – 5 Kbytes
• Color Blind mode
• Coupling Flag disabled
The following command edits the rate meter (policer) profile with Profile ID 50, and changes its name to
“256 kBytes.”
root> ethernet qos rate-meter edit profile-id 50 cir 128000 cbs 5 eir
128000 ebs 5 color-mode color-aware coupling-flag enable rate-meter-
profile-name 256 kBytes
This edited profile includes the following parameters:
• CIR – 128,000 bps
• CBS – 5 Kbytes
• EIR – 128,000 bps
• EBS – 5 Kbytes
• Color Aware mode
• Coupling Flag enabled

Displaying Rate Meter Profiles (CLI)

You can display all configured rate meter (policer) profiles or a specific profile.
To display a specific profile, enter the following command:
root> ethernet qos rate-meter show profile-id <profile-id>
To display all configured profiles, enter the following command:
root> ethernet qos rate-meter show profile-id all

Example
The following command displays the parameters of Rate Meter Profile 50:
root> ethernet qos rate-meter show profile-id 50

Deleting a Rate Meter Profile (CLI)

You cannot delete a rate meter (policer) profile that is attached to a logical interface. You must first remove the
profile from the logical interface, then delete the profile.
To delete a rate meter (policer) profile, use the following command:
root> ethernet qos rate-meter delete profile-id <profile-id>

Example
The following command deletes Rate Meter Profile 50:
root> ethernet qos rate-meter delete profile-id 50

Attaching a Rate Meter (Policer) to an Interface (CLI)

On the logical interface level, you can assign rate meter (policer) profiles as follows:
• Per frame type (unicast, multicast, and broadcast)
• Per frame ethertype

Phn 3963 013v000

Page 756
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

This section includes:

• Assigning a Rate Meter (Policer) for Unicast Traffic (CLI)
• Assigning a Rate Meter (Policer) for Multicast Traffic (CLI)
• Assigning a Rate Meter (Policer) for Broadcast Traffic (CLI)
• Assigning a Rate Meter (Policer) per Ethertype (CLI)

Assigning a Rate Meter (Policer) for Unicast Traffic (CLI)

To assign a rate meter (policer) profile for unicast traffic to the interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter unicast add capability admin-state <admin-
state> profile-id <profile-id>
To change the rate meter (policer) profile for unicast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter unicast edit admin-state <admin-state>
profile-id <profile-id>
To display the current unicast rate meter (policer) profile for an interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter unicast show configuration
To delete the rate meter (policer) profile for unicast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter unicast delete

Phn 3963 013v000

Page 757
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Table 187 Assigning Rate Meter for Unicast Traffic CLI Parameters

Parameter Input Type Permitted Values Description

admin-state Variable enable Enables or disables rate metering on

disable unicast traffic flows from the logical
interface.

profile-id Number 1 – 250 Select from the rate meter profiles

defined in the system.

Examples
The following command assigns Rate Meter Profile 1 to unicast traffic on GbE 1, and enables rate metering on the
port:
eth type eth [1/1]>rate-meter unicast add capability admin-state enable
profile-id 1
The following command changes the rate meter (policer) profile for unicast traffic on GbE 1 to 4:
eth type eth [1/1]>rate-meter unicast edit admin-state enable profile-id 4

Assigning a Rate Meter (Policer) for Multicast Traffic (CLI)

To assign a rate meter (policer) profile for multicast traffic to the interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter multicast add capability admin-state <admin-
state> profile-id <profile-id>
To change the rate meter (policer) profile for multicast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter multicast edit admin-state <admin-state>
profile-id <profile-id>
To display the current multicast rate meter (policer) profile for an interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter multicast show configuration
To delete the rate meter (policer) profile for multicast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter multicast delete

Phn 3963 013v000

Page 758
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Table 188 Assigning Rate Meter for Multicast Traffic CLI Parameters

Parameter Input Type Permitted Values Description

admin-state Variable enable Enables or disables rate metering on

disable multicast traffic flows from the logical
interface.

profile-id Number 1 – 250 Select from the rate meter profiles

defined in the system.

Examples
The following command assigns Rate Meter Profile 1 to multicast traffic on GbE 1, and enables rate metering on the
port.
eth type eth [1/1]>rate-meter multicast add capability admin-state enable
profile-id 1
The following command changes the rate meter (policer) profile for multicast traffic on GbE 1 to 4:
eth type eth [1/1]>rate-meter multicast edit admin-state enable profile-id
4

Assigning a Rate Meter (Policer) for Broadcast Traffic (CLI)

To assign a rate meter (policer) profile for broadcast traffic to the interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter broadcast add capability admin-state <admin-
state> profile-id <profile-id>
To change the rate meter (policer) profile for broadcast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter broadcast edit admin-state <admin-state>
profile-id <profile-id>
To display the current broadcast rate meter (policer) settings for an interface, go to interface view for the interface
and enter the following command:
eth type eth [x/x]>rate-meter broadcast show configuration
To delete the rate meter (policer) profile for broadcast traffic, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter broadcast delete

Phn 3963 013v000

Page 759
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Table 189 Assigning Rate Meter for Broadcast Traffic CLI Parameters

Parameter Input Type Permitted Values Description

admin-state Variable enable Enables or disables rate metering on

disable broadcast traffic flows from the logical
interface.

profile-id Number 1 – 250 Select from the rate meter profiles

defined in the system.

Examples
The following command assigns Profile 1 to broadcast traffic on GbE 1, and enables rate metering on the port.
eth type eth [1/1]>rate-meter broadcast add capability admin-state enable
profile-id 1
The following command changes the rate meter (policer) profile for broadcast traffic on GbE 1 to 4:
eth type eth [1/1]>rate-meter broadcast edit admin-state enable profile-id
4

Assigning a Rate Meter (Policer) per Ethertype (CLI)

You can define up to three policers per Ethertype value.
To assign a rate meter (policer) profile for a specific Ethertype to an interface, go to interface view for the interface
and enter the following command:
eth type eth [x/x]>rate-meter <ethertype#> add capability ethertype-value
<ethertype-value> admin-state <admin-state> profile-id <profile-id>
To change the rate meter (policer) profile for a specific Ethertype, go to interface view for the interface and enter the
following command:
eth type eth [x/x]>rate-meter <ethertype#> edit ethertype-value <ethertype-
value> admin-state <admin-state> profile-id <profile-id>
To display the current Ethertype rate meter (policer) settings for an interface, go to interface view for the interface
and enter the following commands:
eth type eth [x/x]>rate-meter ethertype1 show configuration
eth type eth [x/x]>rate-meter ethertype2 show configuration
eth type eth [x/x]>rate-meter ethertype3 show configuration
To delete the rate meter (policer) profile for an Ethertype, go to interface view for the interface and enter one or
more of the following commands:
eth type eth [x/x]>rate-meter ethertype1 delete
eth type eth [x/x]>rate-meter ethertype2 delete
eth type eth [x/x]>rate-meter ethertype3 delete

Phn 3963 013v000

Page 760
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

Table 190 Assigning Rate Meter per Ethertype CLI Parameters

Parameter Input Type Permitted Values Description

ethertype# Variable ethertype1 Identifies which of three possible policer-

ethertype2 per-Ethertype combinations you are
defining.
ethertype3 I

ethertype- Hexadecimal 1-65535 Identifies the Ethertype to which the

value profile applies.

admin-state Variable enable Enables or disables policing on broadcast

disable traffic flows from the logical interface.

profile-id Number 1 – 250 Select from the policer profiles defined in

the system. For instructions on defining
rate meter (policer) profiles, refer to
Configuring Rate Meter (Policer) Profiles
(CLI).

Examples
The following commands assign Rate Meter Profiles 1, 2, and 3 to Ethertypes 0x8000, 0x8100, and 0x9100,
respectively, on GbE 1, and enable rate metering on the port.
eth type eth [1/1]>rate-meter ethertype1 add capability ethertype-value
0x8000 admin-state enable profile-id 1

eth type eth [1/1]>rate-meter ethertype2 add capability ethertype-value

0x8100 admin-state enable profile-id 2

eth type eth [1/1]>rate-meter ethertype3 add capability ethertype-value

0x9100 admin-state enable profile-id 3
The following commands change the rate meter (policer) profiles assigned in the examples above to 4, 5, and 6,
respectively.
eth type eth [1/1]>rate-meter ethertype1 edit ethertype-value 0x8000 admin-
state enable profile-id 4

eth type eth [1/1]>rate-meter ethertype2 edit ethertype-value 0x8100 admin-

state enable profile-id 5

eth type eth [1/1]>rate-meter ethertype3 edit ethertype-value 0x9100 admin-

state enable profile-id 6

Attaching a Rate Meter (Policer) to a Service Point and CoS (CLI)

To assign a rate meter (policer) profile to a service point, go to service view for the service and enter
the following commands:

service[x]>sp rate-meter add capability spid <spid>

service[x]>sp rate-meter edit spid <spid> admin-state <admin-

state> profile-id <profile-id>

To change the rate meter (policer) profile for a service point, go to service view for the service and
enter the following command:

Phn 3963 013v000

Page 761
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

service[x]>sp rate-meter edit spid <spid> admin-state <admin-

state> profile-id <profile-id>
To display the current rate meter (policer) profile for a service point, go to service view for the service
and enter the following command:

service[x]>sp rate-meter show configuration spid <spid>

To assign a rate meter (policer) profile to a service point and CoS, go to service view for the service
and enter the following commands:

service[x]>sp rate-meter add capability spid <spid>

service[x]>sp rate-meter edit spid <spid> cos <cos> admin-state

<admin-state> profile-id <profile-id>
To change the rate meter (policer) profile for a service point and CoS, go to service view for the
service and enter the following command:

service[x]>sp rate-meter edit spid <spid> cos <cos> admin-state

<admin-state> profile-id <profile-id>

The current rate meter (policer) profile for a service point and CoS, go to service view for the
service and enter the following command:

service[x]>sp rate-meter show configuration spid <spid> cos

<cos>

To delete the rate meter (policer) profile for a service point or service point/CoS combination, go to service
view for the service and enter the following command:
service[x]>sp rate-meter delete spid <spid>

Table 191: Assigning Rate Meter for Service Point and Service Point/CoS CLI Parameters

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and The Service Point ID.
MP services.
1-30 for MNG
services.
admin-state Variable enable Enables or disables rate metering on unicast
disable traffic flows from the logical interface.

profile-id Number 1 – 250 Select from the rate meter profiles defined in the
system.
cos Number 0–7 The CoS value to which you are assigning the rate
meter.

The following commands assign Rate Meter Profile 2 to service point 10 on service 5:

Phn 3963 013v000

Page 762
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

root> ethernet service sid 5

service[5]> sp rate-meter add capability spid 10

service[5]>sp rate-meter edit spid 10 admin-state enable

profile-id 2
The following commands assign Rate Meter Profile 4 to service point 10 and CoS 6 on service 5:

root> ethernet service sid 5

service[5]> sp rate-meter add capability spid 10

service[5]>sp rate-meter edit spid 10 cos 6 admin-state enable

profile-id 4

Configuring the Line Compensation Value for a Rate Meter

(Policer) (CLI)
A rate meter can measure CIR and EIR at Layer 1 or Layer 2 rates. 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). In most cases, the preamble and IFG
equals 20 bytes, but other values are also possible. Line compensation defines the number of bytes to be added to
each frame for purposes of CIR and EIR calculation. When Line Compensation is 20, the rate meter operates as Layer
1. When Line Compensation is 0, the rate meter operates as Layer 2. This parameter is very important to users that
want to distinguish between Layer 1 and Layer 2 traffic.
To configure the rate meter (policer) line compensation value for an interface, go to interface view for the interface
and enter the following command:
eth type eth [x/x]>rate-meter-compensation-value set <value>
To display the rate meter (policer) line compensation value for an interface, go to interface view for the interface and
enter the following command:
eth type eth [x/x]>rate-meter-compensation-value get

Table 192 Assigning Line Compensation Value for Rate Meter CLI Parameters

Parameter Input Type Permitted Values Description

value Number 0 – 32 Policers attached to the interface use this

value to compensate for Layer 1 non-
effective traffic bytes.

Example
The following command sets the line compensation value for policers attached to GbE 1 to 20:
eth type eth [1/1]>rate-meter-compensation-value set 20

Displaying Rate Meter Statistics for an Interface (CLI)

For the rate meter (policer) at the logical interface level, you can display the following statistics counters:
• Green Frames
Phn 3963 013v000
Page 763
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

• Green Bytes
• Yellow Frames
• Yellow Bytes
• Red Frames
• Red Bytes

Note
Rate meter (policer) counters are displayed in granularity of 64 bits.

The following commands display rate meter counters for the available frame types and Ethertypes:
eth type eth [x/x]>rate-meter unicast show statistics clear-on-read <clear-
on-read> layer-1 <layer-1>

eth type eth [x/x]>rate-meter multicast show statistics clear-on-read

<clear-on-read> layer-1 <layer-1>

eth type eth [x/x]>rate-meter broadcast show statistics clear-on-read

<clear-on-read> layer-1 <layer-1>

eth type eth [x/x]>rate-meter ethertype1 show statistics clear-on-read

<clear-on-read> layer-1 <layer-1>

eth type eth [x/x]>rate-meter ethertype2 show statistics clear-on-read

<clear-on-read> layer-1 <layer-1>

eth type eth [x/x]>rate-meter ethertype3 show statistics clear-on-read

<clear-on-read> layer-1 <layer-1>

Table 193 Displaying Rate Meter Statistics CLI Parameters

Parameter Input Type Permitted Values Description

clear-on-read Boolean yes If you enter yes, the statistics are cleared once you
no display them.

layer 1 Boolean yes yes – Statistics are represented as Layer 1

no statistics, including preamble and IFG.
no – Statistics are represented as Layer 2 statistics.

Example
The following commands display rate meter counters for GbE 1, for each of the available frame types and Ethertypes.
These commands clear the counters after displaying them.
eth type eth [1/1]>rate-meter unicast show statistics clear-on-read yes
layer-1 no

eth type eth [1/1]>rate-meter multicast show statistics clear-on-read yes

layer-1 no

eth type eth [1/1]>rate-meter broadcast show statistics clear-on-read yes

layer-1 no

eth type eth [1/1]>rate-meter ethertype1 show statistics clear-on-read yes

layer-1 no

eth type eth [1/1]>rate-meter ethertype2 show statistics clear-on-read yes

layer-1 no

Phn 3963 013v000

Page 764
Chapter 18: Quality of Service (QoS) (CLI) Configuring Policers (Rate Metering) (CLI)

eth type eth [1/1]>rate-meter ethertype3 show statistics clear-on-read yes

layer-1 no

Phn 3963 013v000

Page 765
Chapter 18: Quality of Service (QoS) (CLI) Configuring Marking (CLI)

Configuring Marking (CLI)

This section includes:

• Marking Overview (CLI)
• Configuring Marking Mode on a Service Point (CLI)
• Marking Table for C-VLAN UP Bits (CLI)
• Marking Table for S-VLAN UP Bits (CLI)

Marking Overview (CLI)

When enabled, PTP 820’s marking mechanism modifies each frame’s 802.1p UP bit and CFI/DEI bits according to the
classifier decision. The CFI/DEI (color) field is modified according to the classifier and policer decision. The color is first
determined by a classifier and may be later overwritten by a policer. Green color is represented by a CFI/DEI value of
0, and Yellow color is represented by a CFI/DEI value of 1. Marking is performed on egress frames that are VLAN-
tagged.
The marking is performed according to global marking tables that describe the 802.1p UP bits and the CFI bits (for C-
VLAN tags) or DEI bits (for S VLAN tags). The marking mode attribute in the service point egress attributes determines
whether the frame is marked as Green or Yellow according to the calculated color.

Note
The calculated color is sent to the queue manager regardless of whether the marking bit is set.

Regular marking is only performed when:

• The outer frame is S-VLAN, and S-VLAN CoS preservation is disabled
• The outer frame is C-VLAN, and C-VLAN CoS preservation is disabled
If marking and CoS preservation for the relevant outer VLAN are both disabled, special marking is applied. Special
marking means that marking is performed, but only according to the values defined for Green frames in the 802.1Q
and 802.1AD marking tables.
When marking is performed, the C-VLAN or S-VLAN 802.1p UP bits are re-marked according to the calculated CoS and
Color.

Configuring Marking Mode on a Service Point (CLI)

To enable or disable marking mode on a service point, go to service view for the service and enter the following
command:
service[SID]>sp marking set spid <sp-id> mode <mode>

Table 194 Marking Mode on Service Point CLI Parameters

Phn 3963 013v000

Page 766
Chapter 18: Quality of Service (QoS) (CLI) Configuring Marking (CLI)

Parameter Input Type Permitted Values Description

sp-id Number 1-32 for P2P and MP The Service Point ID.
services.
1-30 for MNG
services.

mode Variable enable Determines whether re-marking of the

disable outer VLAN (C-VLAN or S-VLAN) of tagged
frames that pass through the service point
is enabled.
If mode is set to enable, and CoS
preservation for the relevant outer VLAN
is set to disable, the service point re-
marks the C-VLAN or S-VLAN 802.1p UP
bits of egress frames according to the
calculated CoS and Color, and the user-
configurable 802.1Q and 802.1AD marking
tables.
If mode is set to enable and CoS
preservation for the relevant outer VLAN
is also set to enable, re-marking is not
performed.
If mode is set to disable and CoS
preservation for the relevant outer VLAN
is also set to disable, re-marking is
applied, but only according to the values
defined for Green frames in the 802.1Q
and 802.1AD marking tables.
For information about configuring CoS
Preservation, refer to CoS Preservation
and Modification on a Service Point (CLI).

Examples
The following command enables marking mode on Service Point 3 on Service 2:
service[2]>sp marking set spid 3 mode enable
The following command disables marking mode on Service Point 3 on Service 2:
service[2]>sp marking set spid 3 mode disable

Marking Table for C-VLAN UP Bits (CLI)

When marking is performed, the following table is used by the marker to decide which CoS and Color to use as the
egress CoS and Color bits for C-VLAN-tagged frames.

Table 195 Marking Table for C-VLAN UP Bits

Phn 3963 013v000

Page 767
Chapter 18: Quality of Service (QoS) (CLI) Configuring Marking (CLI)

CoS Color 802.1q (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

To modify the 802.1q CoS and Color to UP and CFI bit mapping table, enter the following command in root view:
root> ethernet qos 802.1q-up-bits-marking-tbl set cos <cos> color <color>
802.1p <802.1p> cfi <cfi>
To display the 802.1q CoS and Color to UP and CFI bit mapping table, enter the following command in root view:
root> ethernet qos 802.1q-up-bits-marking-tbl show

Table 196 802.1q CoS and Color to UP and CFI Bit Mapping Table CLI Parameters

Parameter Input Type Permitted Values Description

cos Number 0–7 The CoS value to be mapped.

color Variable green The Color to be mapped.

yellow

802.1p Number 0–7 The UP bit value assigned to matching

frames.

Phn 3963 013v000

Page 768
Chapter 18: Quality of Service (QoS) (CLI) Configuring Marking (CLI)

Parameter Input Type Permitted Values Description

cfi Number 0–1 The CFI bit value assigned to matching

frames.

Example
The following command maps CoS 0, Green, to 802.1p UP bit 0, and CFI bit 0:
root> ethernet qos 802.1q-up-bits-marking-tbl set cos 0 color green 802.1p
0 cfi 0

Marking Table for S-VLAN UP Bits (CLI)

When marking is performed, the following table is used by the marker to decide which CoS and Color to use as the
egress CoS and Color bits for S-VLAN-tagged frames.

Table 197 802.1ad UP Marking Table (S-VLAN)

CoS Color 802.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

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

To modify the 802.1ad CoS and Color to UP and DEI bit mapping table, enter the following command in root view:
root> ethernet qos 802.1ad-up-bits-marking-tbl set cos <cos> color <color>
802.1p <802.1p> dei <dei>
To display the 802.1q CoS and Color to UP and CFI bit mapping table, enter the following command in root view:

Phn 3963 013v000

Page 769
Chapter 18: Quality of Service (QoS) (CLI) Configuring Marking (CLI)

root> ethernet qos 802.1ad-up-bits-marking-tbl show

Table 198 802.1ad UP Marking Table (S-VLAN) CLI Parameters

Parameter Input Type Permitted Values Description

cos Number 0–7 The CoS value to be mapped.

color Variable green The Color to be mapped.

yellow

802.1p Number 0–7 The UP bit value assigned to matching

frames.

dei Number 0–1 The DEI bit value assigned to matching

frames.

Example
The following command marks CoS 5, Yellow, to 802.1p UP bit 5, and DEI bit 1:
root> ethernet qos 802.1ad-up-bits-marking-tbl set cos 5 color yellow
802.1p 5 dei 1

Phn 3963 013v000

Page 770
Chapter 18: Quality of Service (QoS) (CLI) Configuring WRED (CLI)

Configuring WRED (CLI)

This section includes:

• WRED Overview (CLI)
• Configuring WRED Profiles (CLI)
• Assigning a WRED Profile to a Queue (CLI)

WRED Overview (CLI)

Weighted Random Early Detection (WRED) enables differentiation between higher and lower priority traffic based on
CoS. You can define up to 30 WRED profiles. Each profile contains a green traffic curve and a yellow traffic curve.
These curves describe the probability of randomly dropping frames as a function of queue occupancy.
The system also includes two pre-defined read-only profiles. These profiles are assigned WRED profile IDs 31 and 32.
• Profile number 31 defines a tail-drop curve and is configured with the following values:
o 100% Yellow traffic drop after 64kbytes occupancy.
o 100% Green traffic drop after 128kbytes occupancy.
o Yellow maximum drop is 100%
o Green maximum drop is 100%
• Profile number 32 defines a profile in which all will be dropped. It is for internal use and should not be applied to
traffic.
A WRED profile can be assigned to each queue. The WRED profile assigned to the queue determines whether or not
to drop incoming frames according to the occupancy of the queue. As the queue occupancy grows, the probability of
dropping each incoming frame increases as well. As a consequence, statistically more TCP flows will be restrained
before traffic congestion occurs.

Configuring WRED Profiles (CLI)

To configure a WRED profile, enter the following command in root view:
root> ethernet qos wred-profile-tbl add profile-id <profile-id> green-min-
threshold <green-min-threshold> green-max-threshold <green-max-threshold>
green-max-drop <green-max-drop> yellow-min-threshold <yellow-min-threshold>
yellow-max-threshold <yellow-max-threshold> yellow-max-drop <yellow-max-
drop>
To edit an existing WRED profile, enter the following command in root view:
root> ethernet qos wred-profile-tbl edit profile-id <profile-id> green-min-
threshold <green-min-threshold> green-max-threshold <green-max-threshold>
green-max-drop <green-max-drop> yellow-min-threshold <yellow-min-threshold>
yellow-max-threshold <yellow-max-threshold> yellow-max-drop <yellow-max-
drop>
To display a WRED profile, enter the following command in root view:
root> ethernet qos wred-profile-tbl show profile-id <profile-id>
To delete a WRED profile, enter the following command in root view:
root> ethernet qos wred-profile-tbl delete profile-id <profile id>

Phn 3963 013v000

Page 771
Chapter 18: Quality of Service (QoS) (CLI) Configuring WRED (CLI)

You cannot delete a WRED profile that is assigned to a queue. You must first remove the WRED profile from the
queue by replacing it with a different WRED profile. You can then delete the WRED profile.

Note
Each queue always has a WRED profile assigned to it. By default, WRED Profile 31 is assigned to every
queue until a different profile is assigned.

Table 199 WRED Profile CLI Parameters

Parameter Input Type Permitted Values Description

profile-id Number 1 - 30 A unique ID to identify the profile.

green-min- Number 0 - 8192 The minimum throughput of green frames

threshold for queues with this profile, in Kbytes.
When this value is reached, the system
begins dropping green frames in the
queue.

green-max- Number 0 - 8192 The maximum throughput of green frames

threshold for queues with this profile, in Kbytes.
When this value is reached, all green
frames in the queue are dropped.

green-max- Number 1 - 100 The maximum percentage of dropped

drop green frames for queues with this profile.

yellow-min- Number 0 - 8192 The minimum throughput of yellow

threshold frames for queues with this profile, in
Kbytes. When this value is reached, the
system begins dropping yellow frames in
the queue.

yellow-max- Number 0 - 8192 The maximum throughput of yellow

threshold frames for queues with this profile, in
Kbytes. After this value is reached, all
yellow frames in the queue are dropped.

yellow-max- Number 1 - 100 The maximum percentage of dropped

drop yellow frames for queues with this profile.

Examples
The following command adds a WRED profile.
root> ethernet qos wred-profile-tbl add profile-id 2 green-min-threshold
8000 green-max-threshold 8000 green-max-drop 100 yellow-min-threshold 8000
yellow-max-threshold 8000 yellow-max-drop 100
The new profile has the following parameters:
• profile-id – 2
• green-min-threshold – 8000 Kbytes
• green-max-threshold – 8000 Kbytes
• green-max-drop – 100%

Phn 3963 013v000

Page 772
Chapter 18: Quality of Service (QoS) (CLI) Configuring WRED (CLI)

• yellow-min-threshold – 8000 Kbytes

• yellow-max-threshold – 8000 Kbytes
• yellow-max-drop – 100%
The following command edits the WRED profile created by the previous command:
root> ethernet qos wred-profile-tbl edit profile-id 2 green-min-threshold
8000 green-max-threshold 8000 green-max-drop 100 yellow-min-threshold 4000
yellow-max-threshold 4000 yellow-max-drop 100
The edited profile has the following parameters:
• green-min-threshold – 8000 Kbytes
• green-max-threshold – 8000 Kbytes
• green-max-drop – 100%
• yellow-min-threshold – 4000 Kbytes
• yellow-max-threshold –4000 Kbytes
• yellow-max-drop – 100%

Assigning a WRED Profile to a Queue (CLI)

To assign a WRED profile to a queue, go to interface view for the interface and enter the following command:
eth type eth [x/x]> wred set service-bundle-id <service-bundle-id> cos
<cos> profile-id <profile-id>
To display the WRED profile assigned to a queue, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> wred show profile-id service-bundle-id <service-bundle-
id> cos <cos>

Table 200 Assigning WRED Profile to Queue CLI Parameters

Parameter Input Type Permitted Values Description

service- Number 1 – 63 Assigns the WRED profile to a Service

bundle-id Note: In the Bundle. Service Bundles are bundles of
current release, only queues, grouped together in order to
Service Bundle 1 is configure common egress characteristics
supported. for specific services.

cos Number 0–7 Assigns the WRED profile to a queue in

the designated service bundle.

profile-id Number 1 – 32 A unique ID that identifies the profile.

Examples
The following command assigns WRED Profile 2 to the CoS 0 queue in Service Bundle 1, on GbE 1:
eth type eth [1/1]> wred set service-bundle-id 1 cos 0 profile-id 2
The following command displays the WRED profile assigned to the CoS 0 queue in Service Bundle 1, on GbE 1:
eth type eth [1/1]> wred show profile-id service-bundle-id 1 cos 0

Phn 3963 013v000

Page 773
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

Configuring Shapers (CLI)

This section includes:

• Overview of Egress Shaping (CLI)
• Configuring Shapers (CLI)
• Configuring Service Bundle Shapers (CLI)
• Configuring Egress Line Compensation for Shaping (CLI)

Overview of Egress Shaping (CLI)

Egress shaping determines the traffic profile for each queue. PTP 820 performs egress shaping on the following levels:
• Queue level – Single leaky bucket shaping
• Service Bundle level – Dual leaky bucket shaping

Note
Single leaky bucket shaping on the interface level is planned for future release.

You can configure up to 32 single leaky bucket queue shaper profiles. The CIR value can be set to the following values:
• 16,000 – 32,000,000 bps – granularity of 16,000 bps
• 32,000,000 – 131,008,000 bps – granularity of 64,000 bps

Note
You can enter any value within the permitted range. Based on the value you enter, the software
automatically rounds off the setting according to the granularity. If you enter a value below the
lowest granular value (except 0), the software adjusts the setting to the minimum.

You can attach one of the configured queue shaper profiles to each priority queue. If no profile is attached to the
queue, no egress shaping is performed on that queue.
This section includes:
• Configuring Queue Shaper Profiles (CLI)
• Attaching a Shaper Profile to a Queue (CLI)

Configuring Queue Shaper Profiles (CLI)

To configure a queue shaper profile, enter the following command in root view:
root> ethernet qos queue-shaper-profile-tbl add profile-id <profile-id> cir
<cir> shaper-profile-name <shaper-profile-name>
To edit the parameters of an existing queue shaper profile, enter the following command in root view:
root> ethernet qos queue-shaper-profile-tbl edit profile-id <profile-id>
cir <cir> shaper-profile-name <shaper-profile-name> burst-type short

Phn 3963 013v000

Page 774
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

Note
The burst-type parameter is reserved for future use. However, you must enter this parameter in
order for the command to execute.

To display the parameters of a queue shaper profile, enter the following command in root view:
root> ethernet qos queue-shaper-profile-tbl show profile-id <profile-id>
To delete a queue shaper profile, enter the following command in root view:
root> ethernet qos queue-shaper-profile-tbl delete profile-id <profile id>
You cannot delete a queue shaper profile if it is attached to a queue. You must first remove the profile from the
queue. You can then delete the profile.

Table 201 Queue Shaper Profiles CLI Parameters

Parameter Input Type Permitted Values Description

profile-id Number 1 - 32 A unique ID that identifies the profile.

cir Number 16000 – 131008000 The Committed Information Rate (CIR)

assigned to the profile (in bps).

shaper- Text String Up to 20 characters. A description of the profile.

profile-name

Examples
The following command creates Queue Shaper 1, named “p1”, with a CIR value of 16000 bps.
root> ethernet qos queue-shaper-profile-tbl add profile-id 1 cir 16000
shaper-profile-name p1
The following command changes the CIR value of the profile created above from 16000 to 32000, and changes the
profile name to p3.
root> ethernet qos queue-shaper-profile-tbl edit profile-id 1 cir 32000
shaper-profile-name p3 burst-type short

Attaching a Shaper Profile to a Queue (CLI)

You can attach one of the configured queue shaper profiles to each priority queue. If no profile is attached to the
queue, no egress shaping is performed on that queue. Shapers are attached to queues based on the logical interface
and service bundle to which the queue belongs, and the queue’s CoS value.
To attach a queue shaper profile to a queue, go to interface view for the interface and enter the following command:
eth type eth [x/x]> queue-shaper add capability service-bundle-id <service-
bundle-id> cos <cos> admin-state <admin-state> profile-id <profile-id>
To change the queue shaper profile attached to a queue, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> queue-shaper edit service-bundle-id <service-bundle-id>
cos <cos> admin-state <admin-state> profile-id <profile-id>
To display the queue shaper profile attached to a queue, go to interface view for the interface and enter the following
command:

Phn 3963 013v000

Page 775
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

eth type eth [x/x]> queue-shaper show configuration service-bundle-id

<service-bundle-id> cos <cos>
To remove a queue shaper profile from a queue, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> queue-shaper delete service-bundle-id <service-bundle-
id> cos <cos>

Table 202 Attaching Shaper Profile to Queue CLI Parameters

Parameter Input Type Permitted Values Description

service- Number 1 – 63 The service bundle to which you are

bundle-id Note: In the attaching the queue shaper profile.
current release, only
Service Bundle 1 is
supported.

cos Number 0–7 The CoS queue ID of the queue to which

you want to assign the shaper. Queues are
numbered according to CoS value.

admin-state Variable enable Select enable to enable egress queue

disable shaping on the queue, or disable to
disable egress queue shaping on the
queue. If you set shaping to disable, the
shaper profile remains attached to the
queue, but does not affect traffic.

profile-id Number 1 – 32 Enter the ID of one of the configured

queue shaper profiles.

Examples
The following command adds Queue Shaper Profile 5 to queues with CoS 0, on Service Bundle 1, on GbE 1, and
enables shaping on these queues.
eth type eth [1/1]> queue-shaper add capability service-bundle-id 1 cos 0
admin-state enable profile-id 5
The following command changes the Queue Shaper Profile assigned in the previous command to Queue Shaper
Profile 2:
eth type eth [1/1]> queue-shaper edit service-bundle-id 1 cos 0 admin-state
enable profile-id 2

Configuring Service Bundle Shapers (CLI)

You can configure up to 256 dual leaky bucket service bundle shaper profiles. The profiles can be configured as
follows:
Valid CIR values are:
• 0 – 32,000,000 bps, with granularity of 16,000 bps

Phn 3963 013v000

Page 776
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

• 32,000,000 – 1,000,000,000 bps, with granularity of 64,000 bps

Valid PIR values are:
• 16,000 – 32,000,000 bps, with granularity of 16,000 bps
• 32,000,000 – 1,000,000,000 bps, with granularity of 64,000 bps

Note
You can enter any value within the permitted range. Based on the value you enter, the software
automatically rounds off the setting according to the granularity. If you enter a value below the
lowest granular value (except 0), the software adjusts the setting to the minimum.

You can attach one of the configured service bundle shaper profiles to each service bundle. If no profile is attached to
the service bundle, no egress shaping is performed on that service bundle.
This section includes:
• Configuring Service Bundle Shaper Profiles (CLI)
• Attaching a Shaper Profile to a Service Bundle (CLI)

Configuring Service Bundle Shaper Profiles (CLI)

To configure a service bundle shaper profile, enter the following command in root view:
root> ethernet qos service-bundle-shaper-profile-tbl add profile-id
<profile-id> cir <cir> pir <pir> shaper-profile-name <shaper-profile-name>
To edit the parameters of an existing service bundle shaper profile, enter the following command in root view:
root> ethernet qos service-bundle-shaper-profile-tbl edit profile-id
<profile-id> cir <cir> pir <pir> shaper-profile-name <shaper-profile-name>
To display the parameters of a service bundle shaper profile, enter the following command in root view:
root> ethernet qos service-bundle-shaper-profile-tbl show profile-id
<profile-id>
To display the parameters of all configured service bundle shaper profiles, enter the following command in root view:
root> ethernet qos service-bundle-shaper-profile-tbl show profile-id all
To delete a service bundle shaper profile, enter the following command in root view:
root> ethernet qos service-bundle-shaper-profile-tbl delete profile-id
<profile-id>
You cannot delete a service bundle shaper profile if it is attached to a service bundle. You must first remove the
profile from the service bundle. You can then delete the profile.

Table 203 Service Bundle Shaper Profiles CLI Parameters

Parameter Input Type Permitted Values Description

profile-id Number 1 - 256 A unique ID that identifies the profile.

cir Number 1 - 1000000000 The Committed Information Rate (CIR)

assigned to the profile (in bps).

pir Number 16000 - 1000000000 The Peak Information Rate (PIR) assigned
to the profile (in bps).

shaper- Text String Up to 20 characters. A description of the profile.

profile-name
Phn 3963 013v000
Page 777
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

The following command creates Service Bundle Shaper 1, named “p1”, with a CIR value of 100000000 bps and a PIR
value of 200000000 bps:
root> ethernet qos service-bundle-shaper-profile-tbl add profile-id 1 cir
100000000 pir 200000000 shaper-profile-name p1
The following command changes the CIR value in the Service Bundle Shaper created above from 100000000 bps to
110000000 bps:
root> ethernet qos service-bundle-shaper-profile-tbl edit profile-id 1 cir
110000000 pir 200000000 shaper-profile-name p1

Attaching a Shaper Profile to a Service Bundle (CLI)

You can attach one of the configured service bundle shaper profiles to each service bundle. If no profile is attached to
the service bundle, no egress shaping is performed on that service bundle.
To attach a service bundle shaper profile to a service bundle, go to interface view for the service bundle and enter the
following command:
eth type eth [x/x]> service-bundle-shaper add capability service-bundle-id
<service-bundle-id> admin-state <admin-state> profile-id <profile-id>
To change the service bundle shaper profile attached to a service bundle, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> service-bundle-shaper edit service-bundle-id <service-
bundle-id> admin-state <admin-state> profile-id <profile-id>
To display the service bundle shaper profile attached to a service bundle, go to interface view for the interface and
enter the following command:
eth type eth [x/x]> service-bundle-shaper show configuration service-
bundle-id <service-bundle-id>
To remove a service bundle shaper profile from a service bundle, go to interface view for the interface and enter the
following command:
eth type eth [x/x]> service-bundle-shaper delete service-bundle-id
<service-bundle-id>

Table 204 Attaching Shaper Profile to Service Bundle CLI Parameters

Parameter Input Type Permitted Values Description

service- Number 1 – 63 The service bundle to which you are

bundle-id Note: In the attaching the queue shaper profile.
current release, only
Service Bundle 1 is
supported.

admin-state Variable enable Select enable to enable egress shaping

disable on the service bundle, or disable to
disable egress shaping on the service
bundle.

profile-id Number 1 – 256 Enter the ID of one of the configured

service bundle shaper profiles.

Phn 3963 013v000

Page 778
Chapter 18: Quality of Service (QoS) (CLI) Configuring Shapers (CLI)

Examples
The following command adds Service Bundle Shaper Profile 5 to Service Bundle 1, on GbE 1, and enables shaping on
this service bundle.
eth type eth [1/1]> service-bundle-shaper add capability service-bundle-id
1 admin-state enable profile-id 5
The following command changes the Service Bundle Shaper Profile assigned in the previous command to Service
Bundle 1, from 5 to 4:
eth type eth [1/1]> service-bundle-shaper edit service-bundle-id 1 admin-
state enable profile-id 4

Configuring Egress Line Compensation for Shaping (CLI)

You can configure a line compensation value for all the shapers under a specific logical interface. This value is used to
compensate for Layer 1 non-effective traffic bytes on egress.
To set the egress line compensation value, go to interface view for the interface and enter the following command:
eth type eth [x/x]>shaping-compensation-value set <value>
To display the egress line compensation value, go to interface view for the interface and enter the following
command:
eth type eth [x/x]>shaping-compensation-value get

Table 205 Egress Line Compensation for Shaping CLI Parameters

Parameter Input Type Permitted Values Description

value Number 0 – 26 (even numbers Shapers attached to the interface use this
only) value to compensate for Layer 1 non-
effective traffic bytes on egress.

Example
The following command sets the egress line compensation value to 0 on GbE 1:
eth type eth [1/1]>shaping-compensation-value set 0

Phn 3963 013v000

Page 779
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Configuring Scheduling (CLI)

This section includes:

• Overview of Egress Scheduling (CLI)
• Configuring Queue Priority (CLI)
• Configuring Interface Priority Profiles (CLI)
• Attaching a Priority Profile to an Interface (CLI)
• Configuring Weighted Fair Queuing (WFQ) (CLI)

Overview of Egress Scheduling (CLI)

Egress scheduling is responsible for transmission from the priority queues. PTP 820 uses a unique algorithm with a
hierarchical scheduling model over the three levels of the egress path that enables compliance with SLA
requirements.
The scheduler scans all the queues over all the service bundles, per interface, and determines which queue is ready to
transmit. If more than one queue is ready to transmit, the scheduler determines which queue transmits first based
on:
• Queue Priority – A queue with higher priority is served before lower-priority queues.
• Weighted Fair Queuing (WFQ) – If two or more queues have the same priority and are ready to transmit, 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.

Configuring Queue Priority (CLI)

A priority profile defines the exact order for serving the eight priority queues in a single service bundle. When you
attach a priority profile to an interface, 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 rate is below the user-defined CIR. Yellow State refers to any
time when the service bundle is above the user-defined CIR but below the PIR.
You can define up to four Green priority profiles, from 4 (highest) to 1 (lowest). An additional four Yellow priority
profiles are defined automatically and cannot be changed or edited.
The following table provides a sample of an interface priority profile. This profile is also used as the default interface
priority profile.

Table 206 Interface Priority Profile Example

Phn 3963 013v000

Page 780
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Profile ID (1-9)

Green Priority Yellow Priority

CoS (user defined) (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, PDUs, etc.)

When the service bundle state is Green (committed state), the service bundle priorities are as defined in the Green
Priority column. When the service bundle state is Yellow (best effort state), the service bundle priorities are system-
defined priorities shown in the Yellow Priority column.

Note
CoS 7 is always marked with the highest priority and cannot be changed or edited, no matter what
the service bundle state is, since it is assumed that only high priority traffic will be tunneled via CoS
7.

The system supports up to nine interface priority profiles. Profiles 1 to 8 are defined by the user, while profile 9 is the
pre-defined read-only default interface priority profile.

Configuring Interface Priority Profiles (CLI)

To define an interface priority profile, enter the following command in root view:
root> ethernet qos port-priority-profile-tbl add profile-id <profile-id>
cos0-priority <cos0-priority> description <description> cos1-priority
<cos1-priority> description <description> cos2-priority <cos2-priority>
description <description> cos3-priority <cos3-priority> description
<description> cos4-priority <cos4-priority> description <description> cos5-
priority <cos5-priority> description <description> cos6-priority <cos6-
priority> description <description> cos7-priority <cos7-priority>
description <description>
To edit an existing interface priority profile, enter the following command in root view:
root> ethernet qos port-priority-profile-tbl edit profile-id <profile-id>
cos0-priority <cos0-priority> description <description> cos1-priority
<cos1-priority> description <description> cos2-priority <cos2-priority>
description <description> cos3-priority <cos3-priority> description
<description> cos4-priority <cos4-priority> description <description> cos5-
priority <cos5-priority> description <description> cos6-priority <cos6-
priority> description <description> cos7-priority <cos7-priority>
description <description>

Phn 3963 013v000

Page 781
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

To display the parameters of an interface priority profile, enter the following command in root view:
root> ethernet qos port-priority-profile-tbl show profile-id <profile-id>
To delete an interface priority profile, enter the following command in root view:
root> ethernet qos port-priority-profile-tbl delete profile-id <profile-id>
You can only delete an interface priority profile if the profile is not attached to any interface.

Table 207 Interface Priority Profile CLI Parameters

Parameter Permitted
Input Type Values Description

profile-id Number 1–8 A unique ID to identify the profile.

cos0-priority Number 1–4 The Green priority for the CoS 0 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 0 egressing the service
bundle to which the profile is assigned.

description Text String Up to 20 A description of the priority level.

characters.

cos1-priority Number 1–4 The Green priority for the CoS 1 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 1 egressing the service
bundle to which the profile is assigned.

cos2-priority Number 1–4 The Green priority for the CoS 2 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 2 egressing the service
bundle to which the profile is assigned.

cos3-priority Number 1–4 The Green priority for the CoS 3 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 3 egressing the service
bundle to which the profile is assigned.

cos4-priority Number 1–4 The Green priority for the CoS 4 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 4 egressing the service
bundle to which the profile is assigned.

cos5-priority Number 1–4 The Green priority for the CoS 5 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 5 egressing the service
bundle to which the profile is assigned.

cos6-priority Number 1–4 The Green priority for the CoS 6 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 6 egressing the service
bundle to which the profile is assigned.

Phn 3963 013v000

Page 782
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Parameter Permitted
Input Type Values Description

cos7-priority Number 1–4 The Green priority for the CoS 7 queue, from 4
(highest) to 1 (lowest). This priority is applied to
Green frames with CoS 7 egressing the service
bundle to which the profile is assigned.

Example
The following command configures a priority profile with Profile ID 1.
root> ethernet qos port-priority-profile-tbl add profile-id 1 cos0-priority
1 description c0_p1 cos1-priority 1 description c1_p1 cos2-priority 1
description c2_p1 cos3-priority 2 description c3_p2 cos4-priority 2
description c4_p2 cos5-priority 3 description c5_p3 cos6-priority 4
description c6_p4 cos7-priority 4 description c7_p4
This profile has the parameters listed in the following table.

Table 208 Interface Priority Sample Profile Parameters

CoS Green Priority Yellow Priority Description

(user defined) (read only)

0 1 1 c0_p1

1 1 1 c1_p1

2 1 1 c2_p1

3 2 1 c3_p2

4 2 1 c4_p2

5 3 1 c5_p3

6 4 1 c6_p4

7 4 4 c7_p4

The following command edits the profile you created in the previous command so that CoS 6 queues have a Green
priority of 3 instead of 4, and a description of “c6_p3”.
root> ethernet qos port-priority-profile-tbl edit profile-id 1 cos0-
priority 1 description c0_p1 cos1-priority 1 description c1_p1 cos2-
priority 1 description c2_p1 cos3-priority 2 description c3_p2 cos4-
priority 2 description c4_p2 cos5-priority 3 description c5_p3 cos6-
priority 3 description c6_p3 cos7-priority 4 description c7_p4

Attaching a Priority Profile to an Interface (CLI)

To attach a priority profile to an interface, go to interface view for the interface and enter the following command:
eth type eth [x/x]> priority set profile-id <profile-id>
To display which priority profile is attached to an interface, go to interface view for the interface and enter the
following command:
Phn 3963 013v000
Page 783
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

eth type eth [x/x]> port-priority show profile-id

Table 209 Attaching Priority Profile to Interface CLI Parameters

Parameter Permitted
Input Type Values Description

profile-id Number 1–9 Enter the ID of one of the configured logical

interface priority profiles.

Examples
The following command attaches Interface Priority Profile 3 to GbE 1:
eth type eth [1/1]> priority set profile-id 3
The following is a sample output from the port-priority show profile-id command:
eth type eth [1/1]>port-priority show profile-id

Profile ID: 9

CoS Priority Priority Description

(When queue is green) (When queue is yellow)

0 1 1 best effort

1 2 1 data service

2 2 1 data service

3 2 1 data service

4 2 1 data service

5 3 1 real time

6 3 1 real time

7 4 4 management

eth type eth [1/1]>

Configuring Weighted Fair Queuing (WFQ) (CLI)

This section includes:
• Overview of WFQ (CLI)
• Configuring a WFQ Profile (CLI)
• Attaching a WFQ Profile to an Interface (CLI)

Overview of WFQ (CLI)

The scheduler serves the queues based on their priority, but when two or more queues have data to transmit and
their priority is the same, the scheduler uses Weighted Fair Queuing (WFQ) to determine the priorities within each
priority. WFQ defines the transmission ratio, in bytes, between the queues. All the service bundles under the
interface inherit the WFQ profile attached to the interface.
The system supports up to six WFQ interface profiles. Profile ID 1 is a pre-defined read-only profile, and is used as the
default profile. Profiles 2 to 6 are user-defined profiles.
The following table provides an example of a WFQ profile.
Phn 3963 013v000
Page 784
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Table 210 WFQ Profile Example

Profile ID (1-7)

CoS Queue Weight (Green) Queue Weight (Yellow – not

visible to users, and cannot be
edited)

0 20 20

1 20 20

2 20 20

3 20 20

4 20 20

5 20 20

6 20 20

7 20 20

You can attach one of the configured interface WFQ profiles to each interface. By default, the interface is assigned
Profile ID 1, the pre-defined system profile.

Configuring a WFQ Profile (CLI)

To define a WFQ profile, enter the following command in root view:
root> ethernet qos wfq-weight-profile-tbl add profile-id <profile.id> cos0-
weight <cos0-weight> cos1-weight <cos1-weight> cos2-weight <cos2-weight>
cos3-weight <cos3-weight> cos4-weight <cos4-weight> cos5-weight <cos5-
weight> cos6-weight <cos6-weight> cos7-weight <cos7-weight>
To edit an existing WFQ profile, enter the following command in root view:
root> ethernet qos wfq-weight-profile-tbl edit profile-id <profile.id>
cos0-weight <cos0-weight> cos1-weight <cos1-weight> cos2-weight <cos2-
weight> cos3-weight <cos3-weight> cos4-weight <cos4-weight> cos5-weight
<cos5-weight> cos6-weight <cos6-weight> cos7-weight <cos7-weight>
To display the parameters of a WFQ profile, enter the following command in root view:
root> ethernet qos wfq-weight-profile-tbl show profile-id <profile-id>
To delete a WFQ profile, enter the following command in root view:
root> ethernet qos wfq-weight-profile-tbl delete profile-id <profile-id>
You can only delete WFQ profile if the profile is not attached to any interface.

Table 211 WFQ Profile CLI Parameters

Parameter Permitted
Input Type Values Description

profile-id Number 2–6 A unique ID to identify the profile.

cos0-weight Number 1 - 20 The relative weight for the CoS 0 queue.

Phn 3963 013v000

Page 785
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Parameter Permitted
Input Type Values Description

cos1- weight Number 1 - 20 The relative weight for the CoS 1 queue.

cos2- weight Number 1 - 20 The relative weight for the CoS 2 queue.

cos3- weight Number 1 - 20 The relative weight for the CoS 3 queue.

cos4- weight Number 1 - 20 The relative weight for the CoS 4 queue.

cos5- weight Number 1 - 20 The relative weight for the CoS 5 queue.

cos6- weight Number 1 - 20 The relative weight for the CoS 6 queue.

cos7- weight Number 1 - 20 The relative weight for the CoS 7 queue.

Examples
The following command configures a WFQ profile with Profile ID 2.
root> ethernet qos wfq-weight-profile-tbl add profile-id 2 cos0-weight 15
cos1-weight 15 cos2-weight 15 cos3-weight 15 cos4-weight 15 cos5-weight 15
cos6-weight 15 cos7-weight 20
This profile has the parameters listed in the following table. Note that the yellow queue weight is constant and
cannot be changed. This means that all best effort traffic (yellow) will always have the same weight, regardless of
CoS.

Table 212 WFQ Sample Profile Parameters

CoS Queue Weight (Green) Queue Weight (Yellow – not

visible to users, and cannot be
edited)

0 15 20

1 20 20

2 20 20

3 20 20

4 20 20

5 20 20

6 20 20

7 20 20

The following command edits the profile you created in the previous command so that CoS 6 queues have a weight of
20 instead of 15:
root> ethernet qos wfq-weight-profile-tbl edit profile-id 2 cos0-weight 15
cos1-weight 15 cos2-weight 15 cos3-weight 15 cos4-weight 15 cos5-weight 15
cos6-weight 20 cos7-weight 20

Phn 3963 013v000

Page 786
Chapter 18: Quality of Service (QoS) (CLI) Configuring Scheduling (CLI)

Attaching a WFQ Profile to an Interface (CLI)

To attach a WFQ profile to an interface, go to interface view for the interface and enter the following command:
eth type eth [x/x]> port-wfq set profile-id <profile-id>
To display which WFQ profile is attached to an interface, go to interface view for the interface and enter the following
command:
eth type eth [x/x]> port-wfq show profile-id

Table 213 Attaching WFQ Profile to Interface CLI Parameters

Parameter Permitted
Input Type Values Description

profile-id Number 1–6 Enter the ID of one of the configured WFQ profiles.

Examples
The following command assigns WFQ Profile 3 to GbE 1:
eth type eth [1/1]> port-wfq set profile-id 3
The following is a sample display for the port-wfq show profile-id command:
eth type eth [1/1]>port-wfq show profile-id

Profile ID: 1

CoS Queue Weight

(Green)

0 20
1 20
2 20
3 20
4 20
5 20
6 20
7 20

eth type eth [1/1]>

Phn 3963 013v000

Page 787
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

Displaying Egress PMs and Statistics (CLI)

PTP 820 collects egress PMs at the queue level and the service bundle level.

Displaying Queue-Level Statistics (CLI)

PTP 820 supports the following counters per queue at the queue 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)
To display queue-level PMs, enter interface view for the interface and enter the following command:
eth type eth [x/x]> tm-queue show statistics service-bundle-id <service-
bundle-id> cos <cos> clear-on-read <clear-on-read> layer-1 <layer-1>
To clear queue-level PMs for a specific service bundle, enter interface view for the interface and enter the following
command:
eth type eth [x/x]> tm-queue clear statistics service-bundle-id <service-
bundle-id>

Table 214 Egress Queue Level PMs CLI Parameters

Parameter Permitted
Input Type Values Description

service- Number 1 – 63 The service bundle for which you want to display
bundle-id Note: In the PMs.
current
release, only
Service
Bundle 1 is
supported.

cos Number 0-7 The queue for which you want to display PMs.

clear-on-read Boolean yes If you enter yes, the statistics are cleared once you
no display them.

layer-1 Boolean yes yes – Statistics are represented as Layer 1

no statistics, including preamble and IFG.
no – Statistics are represented as Layer 2 statistics.

Phn 3963 013v000

Page 788
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

The following command displays PMs for the CoS 0 queue in Service Bundle 1, on GbE 2. The PMs are cleared after
they are displayed.
eth type eth [1/2]> tm-queue show statistics service-bundle-id 1 cos 0
clear-on-read yes layer-1 yes
The following command clears PMs for all queues in Service Bundle 1, on GbE 2.
eth type eth [1/2]> tm-queue clear statistics service-bundle-id 1

Configuring and Displaying Queue-Level PMs (CLI)

PTP 820 devices support advanced traffic PMs per CoS queue and service bundle. For each logical
interface, you can configure thresholds for Green and Yellow traffic per queue. You can then display
the following PMs for 15-minute and 24-hour intervals, per queue and color:
• Maximum bytes passed per second
• Minimum bytes passed per second
• Average bytes passed per second
• Maximum bytes dropped per second
• Minimum bytes dropped per second
• Average bytes dropped per second
• Maximum packets passed per second
• Minimum packets passed per second
• Average packets passed per second
• Maximum packets dropped per second
• Minimum packets dropped per second
• Average packets dropped per second
• Seconds bytes per second were over the configured threshold per interval
These PMs are available for any type of logical interface, including groups. To activate collection of
these PMs, the user must add a PM collection rule on a logical interface and service bundle and set
the relevant thresholds per CoS and Color. When the PM is configured on a group, queue traffic PMs
are recorded for the group and not for the individual interfaces that belong to the group.
One collection rule is available per interface.
PMs for queue traffic are saved for 30 days, after which they are removed from the database. It is
important to note that they are not persistent, which means they are not saved in the event of unit
reset.
To configure and display queue-level PMs, you must first enter interface view. See
Entering Interface View (CLI).

Phn 3963 013v000

Page 789
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

To display whether any service bundles are configured on an interface, enter the following command in
interface view:

eth type eth [x/x]> eth type eth [1/2]>pm tm-queue show
configuration all

If no service bundles have been configured, the following output is displayed:

eth type eth [x/x]>pm tm-queue show configuration all

Num entries: 0

If a service bundle has been configured and enabled, the following output is displayed:

eth type eth [x/x]>pm tm-queue show configuration all

Service bundle: 1 Admin: enable
Num entries: 1

If a service bundle has been configured but it’s Admin status is disabled, the
following output is displayed:

eth type eth [x/x]>pm tm-queue show configuration all

Service bundle: 1 Admin: disable
Num entries: 1

To configure a service bundle, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue create service-bundle-id <1-6>

admin-state <enable|disable>

To change the Admin state of a service bundle, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue set service-bundle-id <1-6> admin-

state <enable|disable>

To remove a service bundle, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue remove service-bundle-id <1-6>

For example:

eth type eth [1/1]>pm tm-queue remove service-bundle-id 1

WARNING: All PM history for that service bundle will be deleted.
Are you sure? (yes/no):yes
eth type eth [1/1]>

To display the threshold settings for a service bundle, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show configuration service-bundle-id

<1-6>

Phn 3963 013v000

Page 790
 Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

For example:

eth type eth [1/1]>pm tm-queue show configuration service-

bundle-id 1
Admin: enable
cos0 green bytes passed threshold: 675000 bytes
cos1 green bytes passed threshold: 675000 bytes
cos2 green bytes passed threshold: 675000 bytes
cos3 green bytes passed threshold: 675000 bytes
cos4 green bytes passed threshold: 675000 bytes
cos5 green bytes passed threshold: 675000 bytes
cos6 green bytes passed threshold: 675000 bytes
cos7 green bytes passed threshold: 675000 bytes
cos0 yellow bytes passed threshold: 675000 bytes
cos1 yellow bytes passed threshold: 675000 bytes
cos2 yellow bytes passed threshold: 100000 bytes
cos3 yellow bytes passed threshold: 675000 bytes
cos4 yellow bytes passed threshold: 675000 bytes
cos5 yellow bytes passed threshold: 675000 bytes
cos6 yellow bytes passed threshold: 675000 bytes
cos7 yellow bytes passed threshold: 675000 bytes
To set thresholds for green bytes, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue set service-bundle-id <1-6> cos <0-7>
green-bytes-passed-threshold <0-4294967295>

To set thresholds for yellow bytes, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue set service-bundle-id <1-6> cos <0-7>
yellow-bytes-passed-threshold <0-4294967295>

To display PMs for green bytes passed, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter green_bytes_passed

service-bundle-id 1 cos <0-7> interval <15min|24hr>

For example:

To display PMs for green packets passed, enter the following command in interface view:

Phn 3963 013v000

Page 780
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

eth type eth [x/x]> pm tm-queue show counter green_packets_passed

service-bundle-id 1 cos <0-7> interval <15min|24hr>

Phn 3963 013v000

Page 781
 Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

For example:

To display PMs for green bytes dropped, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter green_bytes_dropped

service-bundle-id 1 cos <0-7> interval <15min|24hr>

For example:

To display PMs for green packets dropped, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter green_packets_dropped

service-bundle-id 1 cos <0-7> interval <15min|24hr>

For example:

To display PMs for yellow bytes passed, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter yellow_bytes_passed

service-bundle-id 1 cos <0-7> interval <15min|24hr>

Phn 3963 013v000

Page 782
 Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

For example:

To display PMs for yellow packets passed, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter yellow_packets_passed

service-bundle-id 1 cos <0-7> interval <15min|24hr>
For example:

To display PMs for yellow bytes dropped, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter yellow_bytes_dropped

service-bundle-id 1 cos <0-7> interval <15min|24hr>

For example:

To display PMs for yellow packets dropped, enter the following command in interface view:

eth type eth [x/x]> pm tm-queue show counter yellow_packets_dropped

service-bundle-id 1 cos <0-7> interval <15min|24hr>

Phn 3963 013v000

Page 783
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

For example:

The integrity column indicates whether the PM is valid:

• 0 indicates a valid entry.
• 1 indicates an invalid entry. This can occur for a number of reasons,
including but not limited to a disconnected cable, a missing SFP module,
muting of a radio interface, and an operational status of Down.

Displaying Service Bundle-Level Statistics (CLI)

PTP 820 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)
To display service bundle-level PMs, enter interface view for the interface and enter the following command:
eth type eth [x/x]> tm-service-bundle show statistics service-bundle-id
<service-bundle-id> clear-on-read <clear-on-read> layer-1 <layer-1>
To clear service bundle-level PMs for all service bundles on an interface, enter interface view for the interface and
enter the following command:
eth type eth [x/x]> tm-service-bundle clear statistics

Table 215 Egress Service Bundle Level PMs CLI Parameters

Phn 3963 013v000

Page 784
Chapter 18: Quality of Service (QoS) (CLI) Displaying Egress PMs and Statistics (CLI)

Parameter Permitted
Input Type Values Description

service- Number 1 – 63 The service bundle for which you want to display
bundle-id Note: In PMs.
the current
release, only
Service
Bundle 1 is
supported.

clear-on-read Boolean yes If you enter yes, the statistics are cleared once you
no display them.

layer-1 Boolean yes yes – Statistics are represented as Layer 1

no statistics, including preamble and IFG.
no – Statistics are represented as Layer 2 statistics.

Examples
The following command displays service bundle PMs for Service Bundle 1, on GbE 1. The PMs are cleared after
they are displayed.
eth type eth [1/1]> tm-service-bundle show statistics service-bundle-id 1
clear-on-read yes layer-1 yes

Phn 3963 013v000

Page 785
Chapter 19: Ethernet Protocols (CLI) Displaying Egress PMs and Statistics (CLI)

Chapter 19: Ethernet Protocols (CLI)

This section includes:
• Configuring G.8032 (CLI)
• Configuring MSTP (CLI)
• Configuring Ethernet Bandwidth Notification (ETH-BN) (CLI)
• Configuring Adaptive Bandwidth Notification (ABN) (CLI)
• Configuring LLDP (CLI)
Related Topics:
• Configuring Service OAM (SOAM) Fault Management (FM)

Phn 3963 013v000

Page 780
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Configuring G.8032 (CLI)

This section includes:

• Configuring the Destination MAC Address (CLI)
• Configuring ERPIs (CLI)
• Configuring the RPL Owner (CLI)
• Configuring Timers (CLI)
• Initiating a Manual or Forced Switch and Clearing the Switch or Initiating Reversion (CLI)
• Blocking or Unblocking R-APS Messages on a Service Point (CLI)
• Displaying the ERPI Attributes (CLI)

Note
P2P services are not affected by G.8032, and continue to traverse ports that are blocked by G.8032.

Configuring the Destination MAC Address (CLI)

To set the destination MAC address for PDUs generated by the node, enter the following command in root view:
root> ethernet generalcfg g8032-dest-mac-address set MAC <MAC address>

To display the destination MAC address, enter the following command in root view:
root> ethernet generalcfg g8032-dest-mac-address show
To display the destination MAC address and the node ID, enter the following command in root view:
root> ethernet g8032 show-node-attributes
The node ID is the base MAC address for the node.

Phn 3963 013v000

Page 781
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Table 216: G.8032 Destination MAC Address CLI Parameters

Parameter Input Type Permitted Values Description

MAC Six groups of two 01:19:a7:00:00:x where x can The destination MAC address
address hexadecimal digits be any number between 0 and for PDUs generated by the
16. node.

The following command sets the destination MAC address as 01:19:a7:00:00:02:

root> ethernet generalcfg g8032-dest-mac-address set MAC 01:19:a7:00:00:02

Configuring ERPIs (CLI)

You can configure up to 16 Ethernet Ring Protection instances (ERPIs). Each ERPI is associated with an Ethernet
service defined in the system. An ERPI can be:
Ring: A Ring is an Ethernet ring that is connected on two ports (East and West service points) to an interconnection
node.
Sub-Ring: A Sub-Ring is an Ethernet ring which is connected to another ring or network through the use of
interconnection nodes (East and West service points). On their own, the Rub-Ring links do not form a closed physical
loop. A closed loop may be formed by the sub-ring links and the link between interconnection nodes that is controlled
by other ring or network.
Ring with Sub-Ring: The ERPI includes both a ring, with East and West service points, and a connection to a sub-ring
using a Sub-Ring service point.

Note
Service points on the PTP 820 side of the link must have a single, determinate VLAN. This means the
service point type must be dot1q, s-tag, or QinQ. On the customer side, any service point type can be
used.

To add a Ring ERPI, enter the following command in root view:

root> ethernet g8032 create-erpi erp-type ring erpi-id <erpi- id> erpi-service-id
<erpi-service-id> west-sp <west-sp> east-sp
<east-sp> level <level> version <version>

To add a Sub-Ring ERPI, enter the following command in root view:

root> ethernet g8032 create-erpi erp-type sub-ring erpi-id

<erpi-id> erpi-service-id <erpi-service-id> west-sp <west-sp> east-sp <east-sp>
level <level> version <version>

To add a Ring with Sub-Ring ERPI, enter the following command in root view:

Phn 3963 013v000

Page 782
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

root> ethernet g8032 create-erpi erp-type ring-with-sub-ring erpi-id <erpi-id>

erpi-service-id <erpi-service-id> west-sp
<west-sp> east-sp <east-sp> sub-ring-sp <sub-ring-sp> level
<level> version <version>

To assign a name to an ERPI, enter the following command in root view:

root> ethernet g8032 set-erpi-name erpi-id <erpi-id> erpi-name

<erpi-name>

To delete an ERPI, enter the following command in root view:

root> ethernet g8032 delete-erpi erpi-id 1

Table 217: G.8032 ERPI Configuration CLI Parameters

Parameter Input Type Permitted Values Description

erpi-id Number 1-64 A unique ID that identifies the ERPI.

erpi- service- Number 1-4095 The ID of the Ethernet service to which the ERPI belongs.
id

west-sp Number 1-32 The first endpoint for the ERPI. This can be any service
point that has been configured for the service.

east-sp Number 1-32 The second endpoint for the ERPI. This can be any service
point that has been configured for the service.

sub-ring-sp Number 1-32 The service point that connects the Ring with the Sub-
Ring. This can be any service point that has been
configured for the service.

level Number 0-7 Optional. The Maintenance Entity Group (MEG) level used
for R-APS messages sent in the ERPI.

version Number 1-2 Optional. The ERPI (G.8032) protocol version currently
being used in the unit.

erpi-name Text A descriptive name for the ERPI.

The following commands create a Ring ERPI with ID 1, and name the ERPI "service_x". This ERPI is associated with
Ethernet Service 1. The end points of the ERPI are Service Point 1 and Service Point 2. The ERPI is configured with
MEG level 2:

root> ethernet g8032 create-erpi erp-type ring erpi-id 1 erpi- service-id 1 west-
sp 1 east-sp 2 level 2
root> ethernet g8032 set-erpi-name erpi-id 1 erpi-name
service_x

Phn 3963 013v000

Page 783
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

The following commands create a Sub-Ring ERPI with ID 10, and name the ERPI "Sub_ring". This ERPI is associated
with Ethernet Service 20. The end points of the ERPI are Service Point 1 and Service Point 2. The ERPI is configured
with MEG level 4:

root> ethernet g8032 create-erpi erp-type sub-ring erpi-id 10 erpi-service-id 20

west-sp 1 east-sp 2 level 4
root> ethernet g8032 set-erpi-name erpi-id 1 erpi-name Sub_ring

The following commands create a Ring with Sub-Ring ERPI with ID 20, and name the ERPI "RSRi". This ERPI is
associated with Ethernet Service 30. The end points of the ERPI are Service Point 1 and Service Point 2, and the point
of connection between the Ring and the Sub-Ring is Service Point 3. The ERPI is configured with MEG level 5:

root> ethernet g8032 create-erpi erp-type ring-with-sub-ring erpi-id 20 erpi-service-

id 30 west-sp 1 east-sp 2 sub-ring-sp 3
level 5
root> ethernet g8032 set-erpi-name erpi-id 1 erpi-name RSRi

The following command deletes ERPI 1:

root> ethernet g8032 delete-erpi erpi-id 1

Configuring the RPL Owner (CLI)

The RPL Owner Node is a node in the ERPI that is responsible for blocking traffic at one end of the ERPI. You can select
one RPL per ERPI.
To set the RPL Owner Node, enter the following command in root view:

root> ethernet g8032 set-rpl-owner erpi-id <erpi-id> SP <SP>

To remove the RPL Owner Node, enter the following command in root view:

root> ethernet g8032 remove-rpl-owner erpi-id <erpi-id>

Table 218: G.8032 RPL Owner CLI Parameters

Parameter Input Type Permitted Values Description

erpi-id Number 1-64 The ID of the ERPI for which you want to set
or delete the RPL owner.
SP Number or east west sub-ring Specifies the service point you want to
Variable designate as the RPL owner.

The following command sets the East service point as the RPL owner for ERPI 1:

Phn 3963 013v000

Page 784
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

root> ethernet g8032 set-rpl-owner erpi-id 1 SP east

The following command sets the Sub-Ring service point as the RPL owner for ERPI 20:

root> ethernet g8032 set-rpl-owner erpi-id 20 SP sub-ring

The following command removes the RPL owner for ERPI 1:

root> ethernet g8032 remove-rpl-owner erpi-id 1

Configuring Timers (CLI)

You can configure timers per ERPI to control the ERPI's switching and convergence parameters. The following timers
are available:
Wait to Restore (WTR) Timer – Defines a minimum time the system waits after signal failure is recovered before
reverting to idle state, when the RPL can again be blocked.
Guard Time – The guard time is the minimum time the system waits after recovery from a signal failure before
accepting new R-APS messages. The Guard Time should be greater than the maximum expected forwarding delay for
which one R-APS message circles around the ring.

Note
The Guard Time is used to prevent Ethernet ring nodes from acting upon outdated R-APS messages
and prevents the possibility of forming a closed loop.

Hold-Off Time – Determines the time period from failure detection to response. It is used to coordinate between
recovery mechanisms (which mechanism takes place first).
To configure the WTR timer, enter the following command in root view:

root> ethernet g8032 set-wtr erpi-id <erpi-id> wtr <wtr>

To configure the guard time, enter the following command in root view:

root> ethernet g8032 set-guard-time erpi-id <erpi-id> guard- time <guard-time>

To configure the hold-off, enter the following command in root view:

root> ethernet g8032 set-holdoff-time erpi-id <erpi-id> holdoff-time <holdoff-time>

Table 219: G.8032 Timer Configuration CLI Parameters

Parameter Input Type Permitted Values Description

erpi-id Number 1-64 The ID of the ERPI for which you want to set a timer.

Phn 3963 013v000

Page 785
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

wtr Number 1-12 The minimum time (in minutes) the system waits
after signal failure is recovered before reverting to
idle state.

guard- time Number 10-2000, in The minimum time (in msec) the system waits after
multiples of 10 recovery from a signal failure before accepting new R-
APS messages.

holdoff- time Number 0-10000, in The minimum time (in msec) the system waits before
multiples of 100 reacting to a signal failure.

The following command sets the WTR timer for ERPI 1 to 2 minutes:

root> ethernet g8032 set-wtr erpi-id 1 wtr 2

The following command sets the guard time for ERPI 1 to 20 msecs:

root> ethernet g8032 set-guard-time erpi-id 1 guard-time 20

The following command sets the hold-off time for ERPI 1 to 1000 msecs:

root> ethernet g8032 set-holdoff-time erpi-id 1 holdoff-time 1000

Initiating a Manual or Forced Switch and Clearing the Switch or Initiating Reversion (CLI)
To initiate a forced switch, enter the following command in root view:

root> ethernet g8032 fs-erpi erpi-id <erpi-id> SP <SP>

To initiate a manual switch, enter the following command in root view:

root> ethernet g8032 ms-erpi erpi-id <erpi-id> SP <SP>

You can use a "clear" command to clear a forced or manual switch. You can also use a "clear" command to trigger
convergence prior to the expiration of the relevant timer. To issue a "clear" command, enter the following command
in root view:

root> ethernet g8032 clear-erpi erpi-id <erpi-id> SP <SP>

Phn 3963 013v000

Page 786
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Table 220: G.8032 Switching and Reversion CLI Parameters

Parameter Input Type Permitted Values Description

erpi-id Number 1-64 The ID of the ERPI on which you want to perform
or clear the switch or initiate convergence.

SP Number or east west sub-ring Specifies the service point on which to clear the
Variable manual or forced switch or to implement
convergence.

The following command initiates a forced switch in the East service point of ERPI 1:

root> ethernet g8032 fs-erpi erpi-id 1 SP east

The following command initiates a manual switch in the Sub-Ring service point of ERPI 20:

root> ethernet g8032 ms-erpi erpi-id 20 SP sub-ring

The following command initiates convergence in the East service point of ERPI 1:

root> ethernet g8032 clear-erpi erpi-id 1 SP east

Blocking or Unblocking R-APS Messages on a Service Point (CLI)

To enable or disable transmission of R-APS messages on a service point, enter the following command in root view:

root> ethernet g8032 set-erpi-sp-tx-raps-cntrl erpi-id <erpi- id> SP <SP> tx-raps <tx-raps>

Table 234: G.8032 Switching and Reversion CLI Parameters

Parameter Input Type Permitted Values Description

erpi-id Number 1-64 The ID of the ERPI on which you want to perform or
clear the switch or initiate convergence.

SP Variable east west sub-ring Specifies the service point on which to clear the
manual or forced switch or to implement
convergence.

tx-raps Variable true false true – R-APS message transmission is enabled on

the service point.
false – R-APS message transmission is blocked on
the service point.

Phn 3963 013v000

Page 787
 Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Displaying the ERPI Attributes (CLI)

To display a list of all ERPIs configured on the unit, enter the following command in root view:
root> ethernet g8032 show-all-erpi

The following is an example of this command's output.

To display all ERPIs that include a service point on a specific port, enter the following command in root view:

root> ethernet g8032 show-all-port-erpi interface <interface>slot <slot> port <port>

To display all ERPIs that include a service point on a specific group, enter the following command in root view:

root> ethernet g8032 show-all-port-erpi group <group>

The following command displays all ERPIs with a service point on LAG group 1:

root> ethernet g8032 show-all-port-erpi group lag1

The following command displays all ERPIs with a service point on HSB protection group 2:

root> ethernet g8032 show-all-port-erpi group rp2

The following command displays all ERPIs with a service point on Multi-Carrier ABC group 1:

root> ethernet g8032 show-all-port-erpi group mc-abc1

Phn 3963 013v000

Page 788
 Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

The following is an example of this command's output.

To display detailed information about a specific ERPI, enter the following command in root view:

root> ethernet g8032 show-erpi-config erpi-id <erpi-id>

The following command displays detailed output for ERPI 1:

root> ethernet g8032 show-erpi-config erpi-id 1

The following is an example of this command's output.

To display state information about a specific ERPI, enter the following command in root view:

root> ethernet g8032 show-erpi-dynamic erpi-id <erpi-id>

The following command displays detailed output for ERPI 1:

root> ethernet g8032 show-erpi-dynamic erpi-id 1

Phn 3963 013v000

Page 789
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

The following is an example of this command's output.

Table 221: G.8032 ERPI Display Command Input Parameters

Parameter Input Type Permitted Values Description

interface Variable eth radio Enter the type of interface:

eth – Ethernet
radio – Radio
slot Number Ethernet: 1 Depends on the interface and unit type.
Radio: 2

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1:
1
Radio Carrier 2
(PTP820C only): 2

group Variable rp1 rp2 rp3 rp4 To enter interface view for a group, enter the group
lag1 lag2 lag3 lag4 ID for one of the following types of group:
mc-abc1 mc-abc2 HSB group (rp1 - rp-4)
mc-abc3 mc-abc4 LAG (lag1 - lag4)
Multi-Carrier ABC group (mc-abc1 - mc- abc4)
Note: HSB and Multi-Carrier ABC groups are only
relevant for PTP 820C.

erpi-id Number 1-64 The ID of the ERPI for which you want to perform or
clear the switch, initiate convergence, or display
information.

Phn 3963 013v000

Page 790
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Table 222: G.8032 ERPI Display Command Output Parameters

Parameter Description
ERPI ID A unique ID that identifies the ERPI.
ERPI Name A descriptive name for the ERPI.
Service The ID of the Ethernet service to which the ERPI belongs.
User Instance The MSTI to which the Ethernet service is mapped.
Ring State Indicates the current ERPI state. Possible values are: Initializing
Idle Pending Protecting
West SP The interface to which the west ERPI service point belongs.
FS (Forced Switch) MS (Manual Switch)
East SP The interface to which the east ERPI service point belongs.
Sub-Ring SP The interface to which the ERPI service point that connects the Ring to the
Sub-Ring belongs.
ERPI Type The ERPI type (Ring, Sub-Ring, or Ring with Sub-Ring).
MEG Level The Maintenance Entity Group (MEG) level used for R-APS messages sent
in the ERPI.
Version The ERPI (G.8032) protocol version currently being used in the unit.
Virtual Channel Reserved for future use.
RPL Owner Indicates whether the ERPI is currently an RPL owner, and if it is, which
ERPI port is the owner.
Revertive Indicates whether the ERPI is currently in revertive mode.
WTR The Wait to Restore (WTR) timer. This timer sets the minimum time (in
minutes) the system waits after signal failure before entering revertive
Guard Time The
mode.minimum time (in msec) the system waits after recovery from a signal
failure before accepting new R-APS messages. The purpose of this timer is
Hold-Off Time The minimum
to prevent time (in msec)
unnecessary the system
state changes thatwaits
mightbefore reacting
be caused to a signal
by outdated
failure.
messages.
SD Handling Reserved for future use.
West SP SD Capacity Reserved for future use.
Threshold
East SP SD Capacity Reserved for future use.
Threshold
Sub-Ring SP SD Reserved for future use.
Capacity Threshold
Local State The current local state input to the ERPI state machine.
Remote State The last event received from the other end of the link.

Phn 3963 013v000

Page 791
Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

Parameter Description
Last HP Request The last high priority request.
Last Change Time The time of the last ring state transition.

To display the state of a specific service point, enter the following command in root view:

root> ethernet g8032 show-erpi-sp-state erpi-id <erpi-id> SP<SP>

The following command displays the current state of the East service point for ERPI 1:

root> ethernet g8032 show-erpi-sp-state erpi-id 1 SP east

The following is an example of this command's output.

Table 223: G.8032 Service Point Display Command Output Parameters

Parameter Description
ERPI ID A unique ID that identifies the ERPI.
SP Index Identifies the service point in the ERPI.
SP ID The Service Point ID.
Active State Indicates whether or not the service point is active for traffic
forwarding.

R-APS Channel Forwarding Indicates whether the service point is forwarding R-APS messages.
State

Data Forwarding State Indicates whether the service point is in unblocked (forwarding)
state.

RPL Link Blocked State Only relevant if the ERPI to which the service point belongs is the
RPL owner. Indicates whether the service point is in blocked state.

Defect State Indicates whether the service point is in Signal Fail (SF) or Signal
Defect (SD) state.
Note: Support for Signal Defect state is planned for future release.

TX R-APS Frames The number of R-APS frames that have been transmitted via the
service point.

TX R-APS SF The number of R-APS Signal Fail (SF) frames that have been
transmitted via the service point.

Page 792 of 998

Ceragon Proprietary and

Chapter 19: Ethernet Protocols (CLI) Configuring G.8032 (CLI)

TX R-APS NR The number of R-APS No Request (NR) frames that have been
transmitted via the service point.

TX R-APS RB The number of R-APS RPL Blocked (RB) frames that have been
transmitted via the service point.
TX R-APS SD The number of R-APS Signal Degrade (SD) frames that have been
transmitted via the service point.

TX R-APS FS The number of R-APS Forced Switch (FS) frames that have been
transmitted via the service point.

TX R-APS MS The number of R-APS Manual Switch (MS) frames that have been
transmitted via the service point.

TX R-APS Event Reserved for future use.

RX R-APS Frames The number of R-APS frames that have been received by the service
point.

RX Invalid R-APS Frames The number of R-APS frames with an invalid format that have been
received by the service point.

RX R-APS SF The number of R-APS Signal Fail (SF) frames that have been received
by the service point.

RX R-APS NR The number of R-APS No Request (NR) frames that have been
received by the service point.

TX R-APS RB The number of R-APS RPL Blocked (RB) frames that have been
transmitted by the service point.

TX R-APS SD The number of R-APS Signal Degrade (SD) frames that have been
transmitted by the service point.

TX R-APS FS The number of R-APS Forced Switch (FS) frames that have been
transmitted by the service point.

TX R-APS MS The number of R-APS Manual Switch (MS) frames that have been
transmitted by the service point.

TX R-APS Event Reserved for future use.

Page 793 of 998

Ceragon Proprietary and

Chapter 19: Ethernet Protocols (CLI) Configuring MSTP (CLI)

Configuring MSTP (CLI)

This section includes:

• Configuring the MSTP Bridge Parameters (CLI)
• Configuring the MSTP Port Parameters (CLI)

Note
P2P services are not affected by MSTP, and continue to traverse ports that are blocked by MSTP.

Configuring the MSTP Bridge Parameters (CLI)

This section includes:
• Enabling and Disabling MSTP (CLI)
• Defining the Number of MSTIs (CLI)
• Setting the BPDU Destination MAC Address (CLI)
• Freezing MSTP (CLI)
• Resetting the MSTP Stack (CLI)
• Handling Signal Degrade (SD) Failures (CLI)
• Setting the Configuration ID (CLI)
• Mapping Services to MSTIs (CLI)
• Setting the Bridge Level Spanning Tree Parameters (CLI)
• Setting and Viewing the Bridge Level MSTI Parameters (CLI)
• Viewing the MSTP Parameters (CLI)

Enabling and Disabling MSTP (CLI)

Enabling MSTP starts the protocol and sets all port states in all MSTP instances to Blocking. Convergence upon
enabling the protocol generally takes less than two seconds.

Note
All mapping of Ethernet services to MSTP instances (MSTIs) should be performed before
enabling MSTP, For instructions, see Mapping Services to MSTIs (CLI).

To enable MSTP on the unit, enter the following command in root view:

root> ethernet mstp mstp-enable

Disabling MSTP stops the MSTP protocol from running and sets all ports in all MSTP instances to Forwarding state.
To disable MSTP on the unit, enter the following command in root view:
root> ethernet mstp mstp-disable
To display whether MSTP is currently enabled or disabled on the unit, enter the following command in root view:

root> ethernet mstp show-mstp-enabled

Page 794 of 998

Ceragon Proprietary and

Chapter 19: Ethernet Protocols (CLI) Configuring MSTP (CLI)

Defining the Number of MSTIs (CLI)

PTP 820C can support from 1 to 16 Multiple Spanning Tree Instances (MSTIs) on a single unit. This does not include
the Common and Internal Spanning Tree (CIST).
To specify the number of MSTIs, enter the following command in root view:

root> ethernet mstp set number-of-instances <MSTI>

Note
Changing the number of MSTIs causes the MSTP stack to reset.

To display the number of MSTIs on the unit, enter the following command in root view:

root> ethernet mstp show-number-of-instances

Table 224: Defining Number of MSTIs CLI Parameters

Parameter Input Type Permitted Values Description

MSTI Number 2-16 The number of MSTIs on the unit. This number does
not include the Common and Internal Spanning Tree
(CIST).

The following command sets the number of MSTIs to 14:

root> ethernet mstp set number-of-instances 14

Setting the BPDU Destination MAC Address (CLI)

To specify the destination MAC address for BPDUs generated in the unit, enter the following command in root view:
root> ethernet mstp set bpdu-destination-mac <bpdu-destination- mac>

Table 225: BPDU Destination MAC Address CLI Parameters

Parameter Input Type Permitted Values Description

bpdu-destination- Variable customer provider customer – The destination MAC address of

mac BPDUs is 0x0180-C200-0000. Provider
BPDUs are either tunneled or discarded.
provider – The destination MAC address of
BPDUs is 0x0180-C200-0008. Customer
BPDUs are either tunneled or discarded.

Page 795 of 998

Ceragon Proprietary and

Freezing MSTP (CLI)
You can freeze MSTP in the unit. When MSTP is frozen, BPDUs are neither transmitted nor processed, and all port
states are maintained as they were before MSTP was frozen.
To freeze MSTP, enter the following command in root view:
root> ethernet mstp mstp-freeze

To unfreeze MSTP, enter the following command in root view:

root> ethernet mstp mstp-defreeze

To display whether MSTP is or is not currently frozen in the unit, enter the following command in root view:

root> ethernet mstp show-mstp-frozen

Resetting the MSTP Stack (CLI)

To reset MSTP on the unit, enter the following command in root view:

root> ethernet mstp mstp-reset

Handling Signal Degrade (SD) Failures (CLI)

Signal Degrade failures (SD) can either be ignored or treated the same as SF, which means an SD failure triggers a
topology change.

Note
This feature is planned for future release.

To determine how SD failures are treated, enter the following command in root view:

root> ethernet mstp set sd-handling <sd-handling>

Table 226: MSTP Signal Degrade Failure CLI Parameters

Parameter Input Type Permitted ValuesDescription

sd- handling Variable ignored same-as-ignored – Signal Degrade (SD) failures are ignored in
SF MSTP.
same-as-SF – MSTP handles SD failures the same as
Signal Failure, i.e., an SD failure triggers a topology
change.

Page 796 of 998

Ceragon Proprietary and

Setting the Configuration ID (CLI)
The configuration ID attributes include the Configuration Name and the Revision Level. These attributes are part of
the Bridge Configuration Identifier.
To set the configuration ID attributes, enter the following command in root view:

root> ethernet mstp set configuration-name <configuration-name> revision-level

<revision-level>

To display the configuration ID attributes, enter the following command in root view:

root> ethernet mstp show-config-id

Table 227: MSTP Configuration ID CLI Parameters

Parameter Input Type Permitted Description

Values
configuration- Text String The IEEE 802.1Q Configuration Name. The
name Configuration Name is part of the bridge
configuration Identifier.
revision-level Number 0-65535 The IEEE 802.1Q Revision Level. The Revision Level
is part of the bridge configuration Identifier.

Mapping Services to MSTIs (CLI)

By default, all Ethernet services are assigned to MSTI 0 (CIST). You can map Ethernet services to other MSTIs.

Note
All mapping of Ethernet services to MSTP instances (MSTIs) should be performed before enabling
MSTP.

To assign a service to another MSTI, enter the following command in root view:

root> ethernet generalcfg instance-to-service-mapping set service sid <sid>

instance-id <instance-id>

To assign a range of services to another MSTI, enter the following command in root view:

root> ethernet generalcfg instance-to-service-mapping set service sid <sid> to

<sid> instance-id <instance-id>

To display the service to MSTI mapping for a specific service, enter the following command in root view:

root> ethernet generalcfg instance-to-service-mapping show service sid <sid>

Page 797 of 998

Ceragon Proprietary and

To display the service to MSTI mapping for a range of services, enter the following command in root view:

root> ethernet generalcfg instance-to-service-mapping show service sid <sid> to

<sid>

Table 228: MSTP Service to MSTI Mapping CLI Parameters

Parameter Input Type Permitted Values Description

sid Number or Any Ethernet service or range of The service ID.
Range services configured in the unit.

instance- id Number 1-16, 4095 The MSTI to which you want to

map the service.

The following command assigns Service 1 to MSTI 2:

root> ethernet generalcfg instance-to-service-mapping set service sid 1 instance-id 2

The following command assigns Services 1 through 10 to MSTI 2:

root> ethernet generalcfg instance-to-service-mapping set service sid 1 to 10 instance-id 2

The following command displays the service to MSTI mapping for services 1 through 1000:

root> ethernet generalcfg instance-to-service-mapping show service sid 1 to 1000

Setting the Bridge Level Spanning Tree Parameters (CLI)

The bridge level spanning tree parameters determine most of the bridge MSTP parameters, including
parameters that are applied to all bridges when this bridge is acting as the root.
To set the CIST bridge priority, enter the following command in root view:

root> ethernet mstp set cist-bridge-priority <cist-bridge- priority>

To set the CIST hold time, enter the following command in root view:
root> ethernet mstp set cist-bridge-hold-time <cist-bridge- hold-time>

To set the CIST maximum age, enter the following command in root view:
root> ethernet mstp set cist-bridge-max-age <cist-bridge-max- age>

To set the CIST forward delay, enter the following command in root view:
root> ethernet mstp set cist-bridge-forward-delay <cist-bridge- forward-delay>

To set the CIST Hello Time, enter the following command in root view:

root> ethernet mstp set cist-bridge-hello-time <cist-bridge- hello-time>

To set the CIST maximum number of hops, enter the following command in root view:

Page 798 of 998

Ceragon Proprietary and

root> ethernet mstp set cist-bridge-max-hops <cist-bridge-max- hops>

Table 229: MSTP Bridge Level Spanning Tree CLI Parameters

Parameter Input Type Permitted Values Description

cist-bridge-priority Number 0-61440, in steps of Enter a value as the writeable portion of

4096. the Bridge ID. This value constitutes the
first two octets of the Bridge ID.
cist-bridge-hold- timeNumber 10-100 Enter a value (in cs) as the interval length
during which no more than two
configuration bridge PDUs will be
transmitted by this node.

cist-bridge-max-age Number 600-4000 Enter a value (in cs) that all bridges will
use, when this bridge is the root, as the
maximum age of MSTP information
learned from the network on any port
before the information is discarded.

cist-bridge-forward- Number 400-3000 Enter a value (in cs) that all bridges will
delay use, when this bridge is the root, as the
speed at which ports change their
spanning state when moving towards the
Forwarding state. This value determines
how long the port stays in Listening state
and Learning state. This value is also used
when a topology change has been
detected and is underway for purposes of
aging all dynamic entries in the filtering
database.

cist-bridge-hello- Number 100-1000 Enter the value (in cs) that all bridges will
time use, when this bridge is the root, as the
Hello Time. The Hello Time determines
how often the switch broadcasts its hello
message to other switches, and is the
same for all MSTIs.

cist-bridge-max- Number 6-40 Enter the value that all bridges will use,
hops when this bridge is the root, as the
maximum number of hops allowed for a
BPDU within a region before it is
discarded.

Page 799 of 998

Ceragon Proprietary and

Setting and Viewing the Bridge Level MSTI Parameters (CLI)
To set the bridge priority for an MSTI, enter the following command in root view:
root> ethernet mstp set instance <msti-id> msti-bridge-priority
<msti-bridge-priority>
To display the bridge parameters of an MSTI, enter the following command in root view:
root> ethernet mstp show-msti-attributes instance <msti-id>

Table 230: Bridge Level MSTI CLI Parameters

Parameter Input Type Permitted Values Description

instance Number 1-16 Enter the MSTI ID of the MSTI you want to
configure.
msti- Number 0-61440, in steps of The MSTI writeable portion of the Bridge ID.
bridge- 4096.
priority

interface Variable eth radio pwe Enter the type of interface:

eth – Ethernet radio – Radio pwe – TDM

slot Number Ethernet: 1 Depends on the interface and unit type.

Radio: 2

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (IP- 20C
only): 2

group Variable rp1 rp2 rp3 rp4 lag1 To enter interface view for a group, enter the
lag2 lag3 lag4 group ID for one of the following types of group:
mc-abc1 mc-abc2 mc- HSB group (rp1 - rp-4)
abc3 mc-abc4 LAG (lag1 - lag4)
Multi-Carrier ABC group (mc-abc1 - mc- abc4)
Note: HSB and Multi-Carrier ABC groups are only
relevant for PTP 820C.

Page 800 of 998

Ceragon Proprietary and

The following command sets the bridge priority for MSTI 15 to 28672:
root> ethernet mstp set instance 15 msti-bridge-priority 28672

The following command displays the bridge parameters of MSTI 10:

root> ethernet mstp show-msti-attributes instance 10

Viewing the MSTP Parameters (CLI)

To display the general MSTP parameters, enter the following command in root view:
root> ethernet mstp show-gen-attributes

Configuring the MSTP Port Parameters (CLI)

This section includes:
• Configuring and Viewing the CIST Port Parameters (CLI)
• Configuring and Viewing the MSTI Port Parameters (CLI)
• Viewing and Resetting Port BPDU Counters (CLI)

Configuring and Viewing the CIST Port Parameters (CLI)

To set the CIST port priority of a port, enter the following command in root view:
root> ethernet mstp set interface <interface> slot <slot> port
<port> cist-port-priority <cist-port-priority>

To set the CIST port priority of an interface group, enter the following command in root view:

root> ethernet mstp set group <group> cist-port-priority <cist- port-priority>

To set the CIST path cost of a port, enter the following command in root view:

root> ethernet mstp set interface <interface> slot <slot> port<port> cist-port-path-cost <cist-port-path-
cost>

To set the CIST path cost of an interface group, enter the following command in root view:

root> ethernet mstp set group <group> cist-port-path-cost<cist-port-path-cost>

To set a port's administrative edge port parameter for the CIST, enter the following command in root view:

root> ethernet mstp set interface <interface> slot <slot> port

<port> cist-port-edge-port <cist-port-edge-port>
To set an interface group's administrative edge port parameter for the CIST, enter the following command in
root view:

Page 801 of 998

Ceragon Proprietary and

root> ethernet mstp set group <group> cist-port-edge-port
<cist-port-edge-port>

To set a port's MAC Enabled parameter for the CIST, enter the following command in root view:

root> ethernet mstp set interface <interface> slot <slot> port

<port> cist-port-mac-enabled <cist-port-mac-enabled>
To set an interface group's MAC Enabled parameter for the CIST, enter the following command in root view:

root> ethernet mstp set group <group> cist-port-mac-enabled

<cist-port-mac-enabled
To display a port's CIST parameters, enter the following command in root view:

root> ethernet mstp show-cist-port-attributes interface

<interface> slot <slot> port <port>
To display an interface group's CIST parameters, enter the following command in root view:

root> ethernet mstp show-cist-port-attributes group <group>

Table 231: CIST Port CLI Parameters

Parameter Input Type Permitted Values Description

interface Variable eth radio Enter the type of interface:
eth – Ethernet
radio – Radio
slot Number Ethernet: 1 Depends on the interface and unit type.
Radio: 2

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (PTP 820C
only): 2

group Variable rp1 rp2 rp3 rp4 lag1 lag2 To enter interface view for a group, enter
lag3 lag4 the group ID for one of the following types
mc-abc1 mc-abc2 mc-abc3 of group:
mc-abc4 HSB group (rp1 - rp-4)
LAG (lag1 - lag4)
Multi-Carrier ABC group (mc-abc1 - mc-
abc4)
Note: HSB and Multi-Carrier ABC groups are
only relevant for PTP 820C.

Page 802 of 998

Ceragon Proprietary and

 cist-port- Number 0-240, in multiples of 16. The priority contained in the first octet of
priority the two-octet Port ID.

cist-port- Number 1-200000000. The configurable assigned value for the

path-cost contribution of this port to the path cost of
paths towards the spanning tree root.
Note: Changing the value of this parameter
is considered to be a topology change by the
MSTP mechanism.

cist-port- Variable true false true – The port is considered an edge port in
edge-port the CIST.
false – The port is considered a non-edge
port in the CIST.

cist-port- Variable forceTrue forceFalse forceTrue – The MAC is treated as if it is

mac- auto connected to a point-to-point LAN, regardless of
enabled any indications to the contrary that are generated
by the MAC entity.
forceFalse –The MAC is treated as if it is
connected to a non-point-to-point LAN,
regardless of any indications to the contrary that
are generated by the MAC entity.
auto – The MAC Enabled parameter is set to True
if the MAC is connected to a point-to- point or
full-duplex LAN. The MAC Enabled parameter is
set to False if the MAC is connected to a non-
point-to-point and half- duplex LAN.

The following command sets the CIST port priority for Ethernet port 2 to 192:

root> ethernet mstp set interface eth slot 1 port 2 cist-port- priority 192

The following command sets the CIST port priority for HSB protection group 1 to 192:

root> ethernet mstp set group rp1 cist-port-priority 192

The following command sets the CIST path cost for Ethernet port 1 to 20,000:

root> ethernet mstp set interface eth slot 1 port 1 cist-path-

cost 20000
The following command sets the CIST path cost for LAG 1 to 20,000:

root> ethernet mstp set group lag1 cist-path-cost 20000

The following command sets fixed radio interface 1 to be an Edge port in the CIST:

root> ethernet mstp set interface radio slot 3 port 1 cist- port-admin-edge true

The following command sets HSB protection group 1 to be an Edge port in the CIST:

root> ethernet mstp set group rp1 cist-port-admin-edge true

Page 803 of 998

Ceragon Proprietary and

The following command displays the CIST parameters of fixed radio interface 2:

root> ethernet mstp show-cist-port-attributes interface radio slot 2 port 2

The following command displays the CIST parameters of LAG 1:

root> ethernet mstp show-cist-port-attributes group lag1

Configuring and Viewing the MSTI Port Parameters (CLI)

To set the port priority for an MSTI and port, enter the following command in root view:

root> ethernet mstp set instance <instance> interface

<interface> slot <slot> port <port> msti-port-priority <msti- port-priority>

To set the port priority for an MSTI and an interface group, enter the following command in root view:

root> ethernet mstp set instance <instance> group <group> msti- port-priority
<msti-port-priority>
To set the path cost for a port in a specific MSTI, enter the following command in root view:

root> ethernet mstp set instance <instance> interface

<interface> slot <slot> port <port> msti-port-path-cost <msti- port-path-cost>

To set the path cost for an interface group in a specific MSTI, enter the following command in root view:

root> ethernet mstp set instance <instance> group <group> msti- port-path-cost
<msti-port-path-cost>
To display the MSTI parameters for a specific MSTI and port, enter the following command in root view:

root> ethernet mstp show-msti-port-attributes instance

<instance> interface <interface> slot <slot> port <port>

To display the MSTI parameters for a specific MSTI and interface group, enter the following command in root
view:

root> ethernet mstp show-msti-port-attributes instance

<instance> group <group>

Table 232: MSTI Port CLI Parameters

Parameter Input Type Permitted Values Description

instance Number 1-16 Enter the MSTI ID of the MSTI you want to
configure.

Page 804 of 998

Ceragon Proprietary and

 interface Variable eth radio Enter the type of interface:
eth – Ethernet
radio – Radio
slot Number Ethernet: 1 Depends on the interface and unit type.
Radio: 2

Parameter Input Type Permitted Values Description

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (PTP 820C
only): 2

group Variable rp1 rp2 rp3 rp4 lag1 lag2 To enter interface view for a group, enter the
lag3 lag4 group ID for one of the following types of
mc-abc1 mc-abc2 mc-abc3 group:
mc-abc4 HSB group (rp1 - rp-4)
LAG (lag1 - lag4)
Multi-Carrier ABC group (mc-abc1 - mc-abc4)
Note: HSB and Multi-Carrier ABC groups are
only relevant for PTP 820C.

msti-port- Number 0-240, in multiples of 16. The priority contained in the first octet of the
priority two-octet Port ID.

msti-port- Number 1-200000000. The port's Path Cost parameter for the MSTI.
path-cost Note: Changing the value of this parameter
may cause re-initialization of the MSTI for
which the parameter is changed. No other
MSTI should be affected.

The following command sets the MSTI port priority for MSTI 14 on Ethernet port 2 to 192:

root> ethernet mstp set instance 14 interface eth slot 1 port 2 msti-port-priority
192
The following command sets the MSTI port priority for MSTI 14 on LAG 1 to 192:

root> ethernet mstp set instance 14 group lag1 msti-port-

priority 192

The following command sets the MSTI path cost for MSTI 12 on Ethernet port 3 to 20000:

Page 805 of 998

Ceragon Proprietary and

root> ethernet mstp set instance 12 interface eth slot 1 port 3 msti-port-path-cost
20000
The following command sets the MSTI path cost for MSTI 12 on HSB protection group 1 to 20000:

root> ethernet mstp set instance 12 group rp1 msti-port-path- cost 20000

The following command displays the MSTI parameters for MSTI 10 and radio interface 1:

root> ethernet mstp show-msti-port-attributes instance 10 interface radio slot 2

port 1
The following command displays the MSTI parameters for MSTI 10 and LAG 1:

root> ethernet mstp show-msti-port-attributes instance 10 group lag1

Viewing and Resetting Port BPDU Counters (CLI)

To view the BPDU counters for a port, enter the following command in root view:

root> ethernet mstp show-port-counters interface <interface> slot <slot> port

<port>
To view the BPDU counters for an interface group, enter the following command in root view:

root> ethernet mstp show-port-counters group <group>

To reset the BPDU counters, enter the following command in root view:

root> ethernet mstp reset-counters

Table 233: Port BPDU Counters CLI Parameters

Parameter Input Type Permitted Values Description

interface Variable eth radio Enter the type of interface:

eth – Ethernet
radio – Radio
slot Number Ethernet: 1 Depends on the interface and unit type.
Radio: 2

port Number GbE 1: 1 The port number of the interface.

GbE 2: 2
GbE 3: 3
Radio Carrier 1: 1
Radio Carrier 2 (PTP
820C only): 2

Page 806 of 998

Ceragon Proprietary and

group Variable rp1 rp2 rp3 rp4 lag1 lag2 To enter interface view for a group, enter the
lag3 lag4 group ID for one of the following types of
mc-abc1 mc-abc2 mc-abc3 group:
mc-abc4 HSB group (rp1 - rp-4)
LAG (lag1 - lag4)
Multi-Carrier ABC group (mc-abc1 - mc-
abc4)
Note: HSB and Multi-Carrier ABC groups are
only relevant for PTP 820C.

Page 807 of 998

Ceragon Proprietary and

Configuring Adaptive Bandwidth Notification (ABN)
(CLI)

This section includes:

• Adaptive Bandwidth Notification Overview (CLI)
• Configuring an ABN Entity (CLI)

Adaptive Bandwidth Notification Overview (CLI)

Adaptive Bandwidth Notification (ABN), also known as Ethernet Operation and Maintenance (EOAM), enables third
party applications to learn about bandwidth changes in a radio link when ACM is active. Once ABN is enabled, the
radio unit reports bandwidth information to upstream third-party switches.
The ABN entity creates a logical relationship between a radio interface or a logical group of radio interfaces, called
the Monitored Interface, and an Ethernet interface or a logical group of Ethernet interfaces, called the Control
Interface. When bandwidth degrades from the nominal value in the monitored interface, messages relaying the
actual bandwidth values are periodically sent over the Control Interface. A termination message is sent once the
bandwidth returns to its nominal level.

Configuring an ABN Entity (CLI)

You must first create an ABN entity consisting of the Monitored Interface on the one hand, and the Control Interface
on the other. You must then use separate commands to enable or disable bandwidth monitoring of the monitored
interface and transmission of messages. You can also set various parameters relating to the bandwidth sampling and
the transmitted bandwidth messages.
To create an ABN entity consisting of a physical radio interface as the monitored interface and a physical Ethernet
interface as the control interface, enter the following command in root view:
root> ethernet abn abn-entity-create abn-name <ab-name> monitored-interface
<monitored-interface> monitored-slot <monitored-slot> monitored-port
<monitored-port> control-interface <control-interface> control-slot
<control-slot> control-port <control-port> vlan <vlan>
To create an ABN entity consisting of a physical radio interface as the monitored interface and an interface group as
the control interface, enter the following command in root view:
root> ethernet abn abn-entity-create abn-name <abn-name> monitored-
interface <monitored-interface> monitored-slot <monitored-slot> monitored-
port <monitored-port> control-group <control-group> vlan <vlan>
To create an ABN entity consisting of an interface group as the monitored interface and a physical Ethernet interface
as the control interface, enter the following command in root view:
root> ethernet abn abn-entity-create abn-name <abn-name> monitored-group
<monitored-group> control-interface <control-interface> control-slot
<control-slot> control-port <control-port> vlan <vlan>
To create an ABN entity consisting of an interface group as the monitored interface and an interface group as the
control interface, enter the following command in root view:
root> ethernet abn abn-entity-create abn-name <abn-name> monitored-group
<monitored-group> control-group <control-group> vlan <vlan>
To set the Admin status of an ABN entity, enter the following command in root view:

Page 808 of 998

Ceragon Proprietary and

 root> ethernet abn abn-admin-set abn-name <abn-name> admin <admin-state>
To delete an ABN entity, enter the following command in root view:
root> ethernet abn abn-entity-delete abn-name <abn-name>
To show a summary of all ABN entities defined, enter the following command in root view:
root> ethernet abn abn-entities-summary-show
To show a summary of the configuration and status of a specific ABN entity, enter the following command in root
view:
root> ethernet abn abn-entity-show abn-name <abn-name>
To set the monitoring interval for which a weighted average of the bandwidth readings is calculated, enter the
following command in root view:
root> ethernet abn abn-monitoring-interval-set abn-name <abn-name> period
<monitoring-interval>
To set how often messages are transmitted when bandwidth is below the nominal value, enter the following
command in root view:
root> ethernet abn abn-period-set abn-name <abn-name> period <message-
frequency>
To set the holdoff time, enter the following command in root view. Holdoff time is the amount of time the system
waits when bandwidth degradation occurs, before transmitting a message. If the bandwidth is below the nominal
value when the holdoff period ends, the system starts transmitting messages:
root> ethernet abn abn-holdoff-set abn-name <abn-name> holdoff <holdoff-
time>
To clear the messages counter, enter the following command in root view:
root> ethernet abn abn-entity-counter-reset abn-name <abn-name>

Table 234 ABN Entity CLI Parameters

Parameter Input Type Permitted Values Description

pipe-id Number 1 The pipe ID. Only one pipe is supported

in the current release.

abn-name Text String The name of the ABN entity.

monitored- Variable radio This parameter is always set to radio.

interface

monitored- Number 2
slot

monitored- Number Radio Carrier 1: 1

port Radio Carrier 2 (PTP
820C and PTP 820C-
HP): 2

Page 809 of 998

Ceragon Proprietary and

Parameter Input Type Permitted Values Description

monitored- Variable rp1 When the monitored group is an HSB

group rp2 protection group (rp1 - rp-4), a LAG (lag1
- lag4), or a Multi-Carrier ABC group (mc-
rp3
abc1 - mc-abc4), use this parameter
rp4 instead of the monitored-interface
lag1 parameter to identify the group. The
lag2 group must be defined before you
lag3 create the ABN entity.

lag4 Note: Multi-Carrier ABC and HSP

protection are only relevant for PTP
mc-abc1
820C and PTP 820C-HP units.
mc-abc2
mc-abc3
mc-abc4

control- Variable eth This parameter is always set to ethernet.

interface

control-slot Number 1 This parameter is always set to 1.

control-port Number 1-3 The specific Ethernet interface to which

messages are transmitted when
bandwidth in the monitored interface
degrades below the nominal value.

control-group Variable rp1 When the control group is an HSB

rp2 protection group (rp1 - rp-4), a LAG (lag1
- lag4), or a Multi-Carrier ABC group (mc-
rp3
abc1 - mc-abc4), use this parameter
rp4 instead of the control-interface
lag1 parameter to identify the group. The
lag2 group must be defined before you
lag3 create the ABN entity.

lag4 Note: Multi-Carrier ABC and HSP

protection are only relevant for PTP
mc-abc1
820C and PTP 820C-HP units.
mc-abc2
mc-abc3
mc-abc4

vlan Variable untag The VLAN on which messages are

1 - 4094, except 4092 transmitted (optional).
(reserved for the
default management
service)

admin-state Variable isUp Enter isUp to enable ABN monitoring on

isDown the interface, or isDown to disable ABN
monitoring on the interface.

Page 810 of 998

Ceragon Proprietary and

 Parameter Input Type Permitted Values Description

monitoring- Number 1 - 20 The interval (in seconds) for which a

interval weighted average of the bandwidth
readings is calculated.

message- Variable 4-one-second - sets How often messages are transmitted

frequency message frequency to when bandwidth is below the nominal
1 second value.
5-ten-seconds - sets
message frequency to
10 seconds
6-one-minute - sets
message frequency to
1 minute

holdoff-time Number 10 - 29 The amount of time the system waits

when bandwidth degradation occurs,
before transmitting a message.

Examples
The following command creates an ABN entity with radio interface 1 as the monitored interface and Ethernet port 1
as the control interface. It also specifies to transmit bandwidth messages on VLAN 1:
root> ethernet abn abn-entity-create abn-name ABN-1 monitored-interface
radio monitored-slot 1 monitored-port 1 control-interface ethernet control-
slot 1 control-port 1 vlan 1
The following command creates an ABN entity in a PTP 820C or PTP 820C-HP unit with radio interface 2 as the
monitored interface and LAG group lag1 as the control interface. It also specifies to transmit bandwidth messages on
VLAN 55:
root> ethernet abn abn-entity-create abn-name ABN-3 monitored-interface
radio monitored-slot 1 monitored-port 2 control-group lag1 vlan 55
The following command creates an ABN entity in a PTP 820C or PTP 820C-HP unit with HSB protection group rp1 as
the monitored interface and Ethernet port 2 as the control interface. It also specifies to transmit bandwidth messages
on VLAN 200:
root> ethernet abn abn-entity-create abn-name ABN-4 monitored-group rp1
control-interface ethernet control-slot 1 control-port 2 vlan 200
The following command creates an ABN entity in a PTP 820C or PTP 820C-HP unit with HSB protection group rp1 as
the monitored interface and LAG group lag1 as the control interface. It also specifies to transmit bandwidth messages
on VLAN 300:
root> ethernet abn abn-entity-create abn-name ABN-5 monitored-group rp1
control-group lag1 vlan 300
The following command deletes ABN-1:
root> ethernet abn abn-entity-delete abn-name ABN-1
The following command sets the monitoring interval of ABN-1 to 1 second:
root> ethernet abn abn-monitoring-interval-set abn-name ABN-1 period 1
The following command sets the frequency of bandwidth messages regarding ABN-1 to 10 seconds:
root> ethernet abn abn-period-set abn-name ABN-1 period 5-ten-seconds
The following command sets the Holdoff time of ABN-1 to 15 seconds:
root> ethernet abn abn-holdoff-set abn-name ABN-1 holdoff 15

Page 811 of 998

Ceragon Proprietary and

The following command clears the messages counter for ABN-1:
root> ethernet abn abn-entity-counter-reset abn-name ABN-1

Configuring Ethernet Bandwidth Notification (ETH-BN) (CLI)

Note
For an overview of ETH-BN, see ETH-BN Overview.

You must first create an ETH-BN entity consisting of the Monitored Interface on the one hand, and the
Control Interface on the other. You must then use separate commands to enable or disable bandwidth
monitoring of the monitored interface and transmission of messages. You can also set various
parameters related to the bandwidth sampling and the transmitted bandwidth messages.
To create an ETH-BN entity in which the Monitored and Control interfaces are both single interfaces,
enter the following command in root view:

root> ethernet ebn ebn-entity-create ebn-name <eb-name>

monitored-interface <monitored-interface> monitored-slot
<monitored-slot> monitored-port <monitored-port> control-
interface <control-interface> control-slot <control-slot> vlan
<vlan>

To create an ETH-BN entity on an PTP 820E in which the Monitored interface is an Enhanced Multi-
Carrier ABC (Multiband) group and the Control interface is a single Ethernet interface, enter the
following command in root view:

root> ethernet ebn ebn-entity-create ebn-name <eb-name>

monitored-group-on-slot enhanced-abc monitored-slot 1
monitored-port 1 control-interface <control-interface> control-
slot <control-slot> vlan <vlan>

To create an ETH-BN entity in which the Monitored interface is an individual radio interface and the
Control interface is a LAG, enter the following command in root view:

root> ethernet ebn ebn-entity-create ebn-name <eb-name>

monitored-interface <monitored-interface> monitored-slot
<monitored-slot> monitored-port <monitored-port> control-group
<control-group> vlan <vlan>

To create an ETH-BN entity in which the Monitored interface is a Multi-Carrier ABC group and the
Control interface is a LAG, enter the following command in root view:

root> ethernet ebn ebn-entity-create ebn-name <eb-name>

monitored-group <monitored-group> control-group <control-group>
vlan <vlan>

To create an ETH-BN entity on an PTP 820E in which the Monitored interface is an Enhanced Multi-
Carrier ABC (Multiband) group and the Control interface is a LAG, enter the following command in root
view:

Page 812 of 998

Ceragon Proprietary and

 root> ethernet ebn ebn-entity-create ebn-name <eb-name>
monitored-group-on-slot enhanced-abc monitored-slot 1
monitored-port 1 control-group <control-group> vlan <vlan>
To change the name of an ETH-BN entity, enter the following command in root view:

root> ethernet ebn ebn-name-set ebn-name <ebn-name> new-ebn-

name <ebn-name>
To set the Admin status of an ETH-BN entity, enter the following command in root view:

root> ethernet ebn ebn-admin-set ebn-name <ebn-name> admin

<admin-state>

To set the Maintenance Level of messages sent by the ETH-BN entity, enter the following command in
root view:

root> ethernet ebn ebn-mel-set ebn-name <ebn-name> mel <mel>

Note
If CFM MEPs are being used, the MEL must be set to a value greater than the MEG
level of the MEP. Otherwise, the BNM frames will be dropped.
If CFM MEPs are not being used, the MEL for ETH-BN must be set to a value greater than 0.
Otherwise, the BNM frames will be dropped.

To set the VLAN with which messages sent by the ETH-BN entity are transmitted, enter the following
command in root view:

root> ethernet ebn ebn-vlan-set ebn-name <ebn-name> vlan <vlan>

To determine whether periodic BNM frames should be sent even when there is no bandwidth
degradation in the monitored interface, enter the following command in root view:

root> ethernet ebn ebn-is-always-send ebn-name <string> is-

always-send <is-always-send>

To delete an ETH-BN entity, enter the following command in root view:

root> ethernet ebn ebn-entity-delete ebn-name <ebn-name>

To show a summary of all ETH-BN entities defined, enter the following command in root view:

root> ethernet ebn ebn-entities-summary-show

To show a summary of the configuration and status of a specific ABN entity, enter the following
command in root view:

root> ethernet ebn ebn-entity-show ebn-name <ebn-name>

To set how often messages are transmitted when bandwidth is below the nominal value, enter the
following command in root view:

root> ethernet ebn ebn-period-set ebn-name <ebn-name> period

<period>

To set the holdoff time, enter the following command in root view. Holdoff time is the amount of time
the system waits when bandwidth degradation occurs, before transmitting a message. If the
bandwidth is below the nominal value when the holdoff period ends, the system starts transmitting
messages:

Page 813 of 998

Ceragon Proprietary and

 root> ethernet ebn ebn-holdoff-set ebn-name <ebn-name> holdoff
<holdoff-time>

To clear the messages counter, enter the following command in root view:

root> ethernet ebn ebn-entity-counter-reset ebn-name <ebn-name>

Table 217: ETH-BN Entity CLI Parameters

Parameter Input Type Permitted Values Description

ebn-name Text String The name of the ABN entity.
monitored-interface Variable radio This parameter is always set to radio.
monitored-slot Number 2
monitored-port Number Radio Carrier 1: 1
Radio Carrier 2 (PTP
820C and PTP 820C-
HP
monitored-group Variable mc-abc1
only): 2 To configure a Multi-Carrier ABC group
mc-abc2 as the monitored interface, use this
parameter instead of the interface,
mc-abc3
slot, and port parameters to identify
mc-abc4 the group.

control-interface Variable eth This parameter is always set to eth.

control-slot Number 1 This parameter is always set to 1.
control-port Number 1-3 The specific Ethernet interface to which
messages are transmitted when
bandwidth in the monitored interface
degrades below the nominal value.

control-group Variable lag1 To configure a LAG group as the control

lag2 interface, use this parameter instead of
the interface, slot, and port parameters
lag3
to identify the group.
lag4

mel Number 0-7 The CFM Maintenance Level of

messages sent by an ETH-BN entity.
vlan Variable untag The VLAN on which messages are
1 - 4094, except transmitted (optional). The CoS of the
VLAN is automatically set to 7.
4092 (reserved for
the default
management service)

is-always-send Variable true false Specifies whether periodic BNM

frames are sent even when there is
no bandwidth degradation in the
monitored interface:
true – BNM frames are always sent,
even when the bandwidth is at its
nominal value.

Page 814 of 998

Ceragon Proprietary and

no bandwidth degradation in the monitored interface:
true – BNM frames are always sent, even when the bandwidth is at its nominal value.
false – BNM frames are only sent when the current bandwidth is lower than the nominal bandwidth
(default value).

admin-state Variable up down Enter up to enable ETH-BN monitoring

on the interface,
or down to disable EBN monitoring on
the interface.
period Variable 4-one-second 5-ten- How often messages are transmitted
seconds 6-sixty- when is-always-send is set to true or, if
seconds not, when bandwidth is below the
nominal value:
one-second – Message is sent every one
second.
ten-seconds – Message is sent every ten
seconds.
sixty-seconds – Message is sent every
minute.
The default value is ten seconds.
holdoff-time Number 0-10 The amount of time (in seconds) the
system waits when bandwidth
degradation occurs, before transmitting
a message. The default value is 10
seconds.

Page 815 of 998

Ceragon Proprietary and

The following command creates an EBN entity with the following attributes:
• The name of the EBN entity is Test.
• The monitored radio interface is interface 1
• The Ethernet control interface is Ethernet port 1
• The MEL is set to 7.
• BNM frames are only sent when the current bandwidth is lower than the
nominal bandwidth.
• When the current bandwidth is below the nominal value, BNM frames are sent
every 60 seconds, after a holdoff time of 10 seconds.
• BNM frames are untagged

root>ethernet ebn ebn-entity-create ebn-name Test monitored-

interface radio monitored-slot 2 monitored-port 1 control-
interface eth control-slot 1 control-port 7 vlan untag
root>ethernet ebn ebn-admin-set ebn-name Test admin up

root>ethernet ebn ebn-mel-set ebn-name Test mel 7

root>ethernet ebn ebn-is-always-send ebn-name Test is-always-

send false
root>ethernet ebn ebn-period-set ebn-name Test period 6-sixty-
seconds
root>ethernet ebn ebn-holdoff-set ebn-name Test holdoff 10

root>

Phn 3963 013v000

Page 750
Page 750 of 929

Ceragon Proprietary and Confidential

Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Configuring LLDP (CLI)

Link Layer Discovery Protocol (LLDP) is a vendor-neutral layer 2 protocol that can be used by a network element
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. LLDP is a part of the IEEE 802.1AB – 2005 standard that enables
automatic network connectivity discovery by means of a port identity information exchange between each port
and its peer. Each port periodically sends and also expects to receive frames called Link Layer Discovery Protocol
Data Units (LLDPDU). LLDPDUs contain information in TLV format about port identity, such as MAC address and IP
address.
LLDP is used to send notifications to the NMS, based on data of the local unit and data gathered from peer
systems. These notifications enable the NMS to build an accurate network topology.
This section includes:
• Configuring the General LLDP Parameters (CLI)
• Displaying the General LLDP Parameters (CLI)
• Configuring LLDP Port Parameters (CLI)
• Displaying LLDP Port Parameters (CLI)
• Displaying LLDP Local System Parameters (CLI)
• Displaying the LLDP Remote System Parameters (CLI)
• Displaying LLDP Statistics (CLI)

Configuring the General LLDP Parameters (CLI)

This section explains how to define the general LLDP parameters for the unit. For instructions on defining port-
specific parameters, see Configuring LLDP Port Parameters (CLI).
To define the Transmit Interval, which is the interval at which LLDP frames are transmitted, enter the following
command in root view:
root> ethernet lldp tx-interval-set tx-interval <tx-interval>
The time-to-live (TTL) determines the length of time LLDP frames are retained by the receiving device. The TTL is
determined by multiplying the Transmit Interval by the TTL Multiplier.
To define the TTL Multiplier, enter the following command in root view.
root> ethernet lldp tx-hold-multiplier-set hold-multiplier <hold-
multiplier>
To define the interval between transmissions of LLDP notifications during normal transmission periods, enter the
following command in root view.
root> ethernet lldp notif-interval-set notif-interval <notif-interval>

Phn 3963 013v000

Page 751
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Table 235 General LLDP CLI Parameters

Parameter Input Type Permitted Values Description

tx-interval Number 5-3600 The interval, in seconds, at which LLDP

frames are transmitted. The default
value is 30.

hold- Number 2-10 The TTL Multiplier, which is multiplied

multiplier by the Transmit Interval to determine
the TTL, in seconds, of LLDP frames. The
default value is 4.

notif-interval Number 5-3600 The interval, in seconds, between

transmission of LLDP notifications during
normal transmission periods. The
default value is 30.

Examples
The following commands set the Transmit Interval to 50 seconds with a TTL Multiplier of 5. This produces a TTL of
4 minutes and 10 seconds.
root> ethernet lldp tx-interval-set tx-interval 50
root> ethernet lldp tx-hold-multiplier-set hold-multiplier 50
The following command sets a Notification Interval of 20 seconds.
root> ethernet lldp notif-interval-set notif-interval 20

Displaying the General LLDP Parameters (CLI)

To display the general LLDP parameters, enter the following command in root view:
root> ethernet lldp configuration-scalers-show
The following information is displayed:
• Message Tx Interval - The interval, in seconds, at which LLDP frames are transmitted, as defined by
the ethernet lldp tx-interval-set tx-interval command. The default value is 30.
• Message Tx Hold Multiplier - The TTL Multiplier, as defined by the ethernet lldp tx-hold-
multiplier-set hold-multiplier command. The TTL Multiplier is multiplied by the Transmit Interval to
determine the TTL, in seconds, of LLDP frames. The default value is 4.
• Reinit Delay - The minimum time, in seconds, the system waits after the LLDP Admin status becomes Disabled
until it will process a request to reinitialize LLDP. In this release, this parameter is set at 2.
• Notification Interval - The interval, in seconds, between transmission of LLDP notifications during normal
transmission periods, as defined by the ethernet lldp notif-interval-set notif-
interval command. The default value is 30.
• Tx Credit Max - The maximum number of consecutive LLDPDUs that can be transmitted at any one time. In
this release, the Tx Credit Max is set at 5.

Phn 3963 013v000

Page 752
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

• Message Fast Tx - The interval, in seconds, at which LLDP frames are transmitted during fast transmission
periods, such as when the unit detects a new neighbor. In this release, this parameter is set at 1.
• Message Fast Init - The initial value used to initialize the variable which determines the number of
transmissions that are made during fast transmission periods. In this release, this parameter is set at 4.

Configuring LLDP Port Parameters (CLI)

This section explains how to enable LLDP per port, and determine how LLDP operates and which TLVs are sent for
each port:
To define how the LLDP agent operates on a specific port, enter the following command in root view:
root> ethernet lldp agent-admin-set interface eth slot <slot> port <port>
agent-admin <agent-admin>
To enable or disable LLDP notifications to the NMS on a specific port, enter the following command in root view:
root> ethernet lldp agent-notif-enable interface eth slot <slot> port
<port> agent-notif-enable <agent-notif-enable>

Table 236 LLDP Port CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 1 The slot in which the card resides.

port Number 1-3 The port for which you want to

configure LLDP.

agent-admin Variable txOnly Defines how the LLDP protocol operates

rxOnly for this port:

txAndRx txOnly - The LLDP agent transmits LLDP

frames on this port but does not update
disabled
information about its peer.
rxOnly - The LLDP agent receives but
does not transmit LLDP frames on this
port.
txAndRx - The LLDP agent transmits and
receives LLDP frames on this port
(default value).
disabled - The LLDP agent does not
transmit or receive LLDP frames on this
port.

agent-notif- Variable true true - The agent sends a Topology

enable false Change trap to the NMS whenever the
system information received from its
peer changes.
false - Notifications to the NMS are
disabled (default value).

Phn 3963 013v000

Page 753
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Example
The following commands configure Ethernet port 2 to transmit and receive LLDP frames and to send a Topology
Change trap to the NMS whenever the system information of its peer changes:
root> ethernet lldp agent-admin-set interface eth slot 1 port 2 agent-
admin txAndRx

root> ethernet lldp agent-notif-enable interface eth slot 1 port 2 agent-

notif-enable true

Displaying LLDP Port Parameters (CLI)

To display the LLDP agent configuration on all ports, enter the following command in root view:
root> ethernet lldp agent-configuration-show
The following is a sample output of the command:

Displaying LLDP Local System Parameters (CLI)

This section includes:
• Displaying Local Unit Parameters (CLI)
• Displaying Local Port Parameters (CLI)
• Displaying Local Unit Management Information (CLI)
• Displaying Local Unit Management Information per Port (CLI)
• Displaying Unit’s Destination MAC Addresses (CLI)

Displaying Local Unit Parameters (CLI)

To display the local unit's unit parameters, as transmitted by the LLDP agents, enter the following command in root
view:
root> ethernet lldp local-system-scalars-show
The following information is displayed:
• local Chassis Id Subtype - The type of encoding used to identify the local unit. In this release, this parameter is
always set to 4 (MAC Address).
• local Chassis Id - The MAC Address of the local unit.

Phn 3963 013v000

Page 754
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

• local System Name - The system name included in TLVs transmitted by the LLDP agent. To define the system
name, see Configuring Unit Parameters (CLI).
• local System Description - The system description included in TLVs transmitted by the LLDP agent.
• local System Cap Supported - A bitmap value used to identify which system capabilities are supported on the
local system, as included in TLVs transmitted by the LLDP agent. The bitmap is defined by the following
parameters:
o 0 - other
o 1 - repeater
o 2 - bridge
o 3 - wlanAccessPoint
o 4 - router
o 5 - telephone
o 6 - docsisCableDevice
o 7 - stationOnly
o 8 - cVLANComponent
o 9 - sVLANComponent
o 10 - twoPortMACRelay
• local System Cap Enabled - A bitmap value used to identify which system capabilities are enabled on the local
system, as included in TLVs transmitted by the LLDP agent. The bitmap is defined by the following parameters:
o 0 - other
o 1 - repeater
o 2 - bridge
o 3 - wlanAccessPoint
o 4 - router
o 5 - telephone
o 6 - docsisCableDevice
o 7 - stationOnly
o 8 - cVLANComponent
o 9 - sVLANComponent
o 10 - twoPortMACRelay

Displaying Local Port Parameters (CLI)

To display local port parameters, as transmitted by the LLDP agent, enter the following command in root view:
root> ethernet lldp local-port-show
The following information is displayed:
• Interface type/slot/port - The port type, slot number, and port number.
• Port ID Subtype - The type of encoding used to identify the port in LLDP transmissions. In this release, this
parameter is always set to MAC Address.
• Port ID - The port's MAC address.
• Description - A text string that describes the port. In this release, this parameter is always set to ethPort.

Phn 3963 013v000

Page 755
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Displaying Local Unit Management Information (CLI)

To display the local unit's management information, enter the following command in root view:
root> ethernet lldp local-mng-show
The following information is displayed:
• Mng Addr SubType - The format of the local unit's IP Address. In this release, only IPV4 is supported.
• Management Address - The local unit's IP address.
• Mng Addr Length - Reserved for future use.
• Mng Addr IF SubType - Reserved for future use.
• Mng Addr IF - Reserved for future use.
• Mng Addr OID - Reserved for future use.

Displaying Local Unit Management Information per Port (CLI)

To display the local unit's management information per port, enter the following command in root view:
root> ethernet lldp mng-addr-table-show
The following information is displayed:
• Interface type/slot/port - The port type, slot number, and port number.
• Dest Mac Address - Defines the MAC address associated with the port for purposes of LLDP transmissions.
• Mng Address subType - Defines the type of the management address identifier encoding used for the
Management Address. In this release, only IpV4 is supported.
• Management Address - The unit's IP address.
• Mng Address Tx Enable - Indicates whether the unit's Management Address is transmitted with LLDPDUs. In
this release, the Management Address is always sent.

Displaying Unit’s Destination MAC Addresses (CLI)

To display the destination MAC address or range of MAC addresses associated with the unit, and their internal
index, enter the following command in root view:
root> ethernet lldp mac-da-table-show
The following information is displayed:
• LLDP DA Index - The internal index associated with the unit's destination LLDP MAC address.
• LLDP DA - The unit's destination LLDP MAC address.

Displaying the LLDP Remote System Parameters (CLI)

This section includes:
• Displaying the LLDP Remote Unit Parameters (CLI)
• Displaying the LLDP Remote Management Data per Port (CLI)

Phn 3963 013v000

Page 756
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Note
Remote information is not displayed for ports that belong to a LAG group.

Displaying the LLDP Remote Unit Parameters (CLI)

To display the peer's LLDP unit parameter information, starting from a specific time, enter the following command
in root view. If no time is specified, all data is displayed.
root> ethernet lldp agent-remote-table-show agent-start-time <agent-
start-time> interface eth slot <slot> port <port>
Table 237 LLDP Remote Unit CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 1 The slot in which the card resides.

port Number 1-3 The port for which you want to

configure LLDP.

agent-start- Date Use the format: The sys-up-time of the entry creation.
time dd-mm-yyyy,hh:mm:ss

The following information is displayed:

• Time Mark – The time the entry was created.
• Interface Type/Slot/Port – The port for which you are displaying data about the peer.
• Rem Dest Mac Address – The peer LLDP agent's destination MAC Address.
• Remote Index – An arbitrary local integer value used by this agent to identify a particular connection instance,
unique only for the indicated peer.
• Remote Chassis ID subType – The type of encoding used to identify the peer's hardware unit.
• Remote Chassis ID – An octet string used to identify the peer's hardware unit.
• Rem Port ID subType – The type of port identifier encoding used in the peer's Port ID.
• Rem Port ID – An octet string used to identify the port component associated with the peer.
• Rem Port Description – A description of the peer's port.
• Rem System Name – The peer's system name.
• Rem System Description – The peer's system description.

Note
The Rem Port Description, Rem System Name, and Rem System Description fields are not used in the
current version.

• Rem System Cap Supported - The bitmap value used to identify which system capabilities are supported on
the peer. The bitmap is defined by the following parameters:
o 0 - other

Phn 3963 013v000

Page 757
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

o 1 - repeater
o 2 - bridge
o 3 - wlanAccessPoint
o 4 - router
o 5 - telephone
o 6 - docsisCableDevice
o 7 - stationOnly
o 8 - cVLANComponent
o 9 - sVLANComponent
o 10 - twoPortMACRelay
• Rem System Cap Enabled - The bitmap value used to identify which system capabilities are enabled on the
peer. The bitmap is defined by the following parameters:
o 0 - other
o 1 - repeater
o 2 - bridge
o 3 - wlanAccessPoint
o 4 - router
o 5 - telephone
o 6 - docsisCableDevice
o 7 - stationOnly
o 8 - cVLANComponent
o 9 - sVLANComponent
o 10 - twoPortMACRelay
• Remote Changes - Indicates whether there are changes in the peer's MIB, as determined by the variable
remoteChanges. Possible values are:
o True - Changes have taken place in the peer's MIB since the defined agent-start-time.
o False - No changes have taken place in the peer's MIB since the defined agent-start-
time.

Displaying the LLDP Remote Management Data per Port (CLI)

To display remote LLDP management data from a specific port, starting from a specific time, enter the following
command in root view. If no time is specified, all data is displayed.
root> ethernet lldp agent-remote-mng-show agent-start-time <agent-start-
time> interface eth slot <slot> port <port>

Table 238 LLDP Remote Management Data Per Port CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 1

port Number 1-3 The port for which you want to

configure LLDP.

Phn 3963 013v000

Page 758
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

Parameter Input Type Permitted Values Description

agent-start- Date Use the format: The sys-up-time of the entry creation.
time dd-mm-yyyy,hh:mm:ss

The following information is displayed:

• Time Mark - The time the entry was created.
• Interface Type/Slot/Port - The port for which you are displaying data about the peer.
• Rem Dest Mac Address - The peer LLDP agent's destination MAC Address.
• Remote Index - An arbitrary local integer value used by this agent to identify a particular connection instance,
unique only for the indicated peer.
• Remote Mng Addr subType - The type of management address identifier encoding used in the associated
LLDP Agent Remote Management Address.
• Remote Mng Address - The octet string used to identify the management address component associated with
the remote system. The purpose of this address is to contact the management entity.
• Remote Mng IF subType - The enumeration value that identifies the interface numbering method used for
defining the interface number, associated with the remote system. Possible values are:
o unknown(1)
o ifIndex(2)
o systemPortNumber(3)
• Agent Rem OID - The OID value used to identify the type of hardware component or protocol entity associated
with the management address advertised by the remote system agent.

Displaying LLDP Statistics (CLI)

This section includes:
• Displaying Statistics Regarding Changes in Peer Unit (CLI)
• Displaying LLDP Transmission Statistics (CLI)
• Displaying LLDP Received Frames Statistics (CLI)

Displaying Statistics Regarding Changes in Peer Unit (CLI)

To display statistics about changes reported via LLDP by the remote unit, enter the following command in root
view:
root> ethernet lldp statistics-scalars-show
The following information is displayed:
• stats Rem Tables Last Change Time - The time of the most recent change in the remote unit, as reported via
LLDP.
• stats Rem Tables Inserts - The number of times the information from the remote system has changed.
• stats Rem Tables Deletes - The number of times the information from the remote system has been deleted.
• stats Rem Tables Drops - Reserved for future use.

Phn 3963 013v000

Page 759
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

• stats Rem Tables Ageouts - The number of times the information from the remote system has been deleted
from the local unit's database because the information's TTL has expired. The RX Ageouts counter is similar
to this counter, but is for specific ports rather than the entire unit.

Displaying LLDP Transmission Statistics (CLI)

To display statistics about LLDP transmissions and transmission errors, enter the following command in root view:
root> ethernet lldp statistics-port-tx-show
The following information is displayed:
• LLDP TX Statistics Ifindex - The index value used to identify the port in LLDP transmissions.
• LLDP TX Statistics DA ID - The LLDP MAC address associated with this entry.
• LLDP TX Statistics Total Frames - The number of LLDP frames transmitted by the LLDP agent on this port to
the destination MAC address.
• LLDP TX Statistics No. of Length Error - The number of LLDPDU Length Errors recorded for this port and
destination MAC address. If the set of TLVs that is selected in the LLDP local system MIB by network
management would result in an LLDPDU that violates LLDPDU length restrictions, then the No. of Length Error
statistic is incremented by 1, and an LLDPDU is sent containing the mandatory TLVs plus as many of the
optional TLVs in the set as will fit in the remaining LLDPDU length.

Displaying LLDP Received Frames Statistics (CLI)

To display statistics about LLDP frames received by the unit, enter the following command in root view:
root> ethernet lldp statistics-port-rx-show
The following information is displayed:
• RX Destination Port - The index value used to identify the port in LLDP transmissions.
• RX DA Index - The index value used to identify the destination MAC address associated with this entry.
• RX Total Discarded - The number of LLDP frames received by the LLDP agent on this port, and then discarded
for any reason. This counter can provide an indication that LLDP header formatting problems may exist with
the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP
agent in the receiving system.
• RX Invalid Frames - The number of invalid LLDP frames received by the LLDP agent on this port while the
agent is enabled.
• RX Valid Frames - The number of valid LLDP frames received by the LLDP agent on this port.
• RX Discarded TLVs - The number of LLDP TLVs discarded for any reason by the LLDP agent on this port.
• RX Unrecognized TLVs - The number of LLDP TLVs received on the given port that are not recognized by LLDP
agent.

Phn 3963 013v000

Page 760
Chapter 19: Ethernet Protocols (CLI) Configuring LLDP (CLI)

• RX Ageouts - The number of age-outs that occurred on the port. An age-out is the number of times the
complete set of information advertised by the remote system has been deleted from the unit's database
because the information timeliness interval has expired. This counter is similar to the LLDP No. of
Ageouts counter, except that it is per port rather than for the entire unit. This counter is set to zero during
agent initialization. This counter is incremented only once when the complete set of information is invalidated
(aged out) from all related tables on a particular port. Partial ageing is not allowed.

Phn 3963 013v000

Page 761
Chapter 20: Synchronization (CLI) Configuring LLDP (CLI)

Chapter 20: Synchronization (CLI)

This section includes:
• Configuring SyncE Regenerator (CLI)
• Changing the ETSI/ANSI Mode (CLI)
• Configuring the Sync Source (CLI)
• Configuring the Outgoing Clock (CLI)
• Configuring SSM Messages (CLI)
• Configuring the Revertive Timer (CLI)
• Displaying Synchronization Status and Parameters (CLI)
• Configuring 1588 Transparent Clock (CLI)

Phn 3963 013v000

Page 762
Chapter 20: Synchronization (CLI) Configuring SyncE Regenerator (CLI)

Configuring SyncE Regenerator (CLI)

Note
PTP 820E R2H ESP, SyncE Regenerator is planned for future release.

In SyncE PRC pipe regenerator mode, frequency is transported between two interfaces through the radio link.
With the system acting as a simple link, no distribution mechanism is necessary, resulting in improved frequency
distribution performance with PRC quality and a simplified configuration.

Note
SyncE Regenerator currently supports only a single pipe configuration. It cannot be used
together with 1588 Transparent Clock.

Before adding a pipe configuration, you must set the Sync mode to Pipe. Enter the following command in root
view:
root> platform sync mode set pipe
By default, the Sync mode is set to Automatic. To display the current Sync mode, enter the following command in
root view:
root> platform sync mode show
To add a pipe configuration, enter the following command in root view:
root> platform sync pipe add pipe-id <pipe-id> interface-1-type
<interface-1-type> slot <slot> port <port> interface-2-type <interface-2-
type> slot <slot> port <port>
To change the first interface in a SyncE pipe, enter the following command in root view:
root> platform sync pipe edit interface-1 pipe-id <pipe-id> interface-1-
type <interface-1-type> slot <slot> port <port>
To change the second interface in a SyncE pipe, enter the following command in root view:
root> platform sync pipe edit interface-1 pipe-id <pipe-id> interface-2-
type <interface-2-type> slot <slot> port <port>
To remove a SyncE pipe, enter the following command in root view:
root> platform sync pipe remove pipe-id <pipe-id>
To remove all SyncE Regenerators (pipes), enter the following command in root view:
root> platform sync pipe remove all
To view the configured SyncE pipes, enter the following command in root view:
root> platform sync pipe show

Table 239 SyncE Regenerator CLI Parameters

Phn 3963 013v000

Page 763
Chapter 20: Synchronization (CLI) Configuring SyncE Regenerator (CLI)

Parameter Input Type Permitted Values Description

pipe-id Number 1 The pipe ID. Only one pipe is supported

in the current release.

interface-1- Variable ethernet The interface type for the first interface
type radio in the pipe.

slot Number Ethernet: 1

Radio: 2

port Number GbE 1: 1

GbE 2: 2
GbE 3: 3 (PTP 820E
only)
Radio Carrier 1: 1
Radio Carrier 2 (PTP
820C amd PTP 820C-
HP): 2

interface-2- Variable ethernet The interface type for the second

type radio interface in the pipe. If the first interface
type is ethernet, the second must by
radio, and vice versa.

Examples
The following command configures a SyncE pipe between Ethernet port 1 and radio interface 1:
root> platform sync pipe add pipe-id 1 interface-1-type ethernet slot 1
port 1 interface-2-type radio slot 2 port 1
The following command changes the first interface in the pipe from ethernet port 1 to Ethernet port 2:
root> platform sync pipe edit interface-1 pipe-id 1 interface-1-type
ethernet slot 1 port 2
The following command changes the second interface in the pipe from radio interface 1 to radio interface 2:
root> platform sync pipe edit interface-2 pipe-id 1 interface-2-type
radio slot 2 port 2
The following command removes SyncE pipe 1:
root> platform sync pipe remove pipe-id 1

Phn 3963 013v000

Page 764
Chapter 20: Synchronization (CLI) Changing the ETSI/ANSI Mode (CLI)

Changing the ETSI/ANSI Mode (CLI)

By default, PTP 820 units are set to ETSI mode. No mode change is necessary to configure an MRMC script, even if
an FCC (ANSI) script is used. However, to configure a sync source on which the sync source Quality parameter must
be set according to ANSI specifications. You must change the ETSI/ANSI mode to ANSI before configuring the sync
source.
To change the ETSI/ANSI mode, enter the following command in root view:
root> platform management set interfaces-standard <ansi|etsi>
The following command changes the ETSI/ANSI mode from the default value of ETSI to ANSI mode:
root> platform management set interfaces-standard ansi
To display the current ETSI/ANSI mode, enter the following command in root view:
root> platform management show interfaces-standard
Changing the ETSI/ANSI mode does not require unit reset.

Phn 3963 013v000

Page 765
Chapter 20: Synchronization (CLI) Configuring the Sync Source (CLI)

Configuring the Sync Source (CLI)

Note
To configure a sync source on which the sync source Quality parameter must be set according to
ANSI specifications, change the ETSI/ANSI mode to ANSI before configuring the sync source. See
Changing the ETSI/ANSI Mode (CLI).

Frequency signals can be taken by the system from Ethernet and radio interfaces. The reference frequency may
also be conveyed to external equipment through different interfaces.
Frequency is distributed by configuring the following parameters in each node:
• System Synchronization Sources – These are the interfaces from which the frequency is taken and distributed
to other interfaces. Up to 16 sources can be configured in each node. A revertive timer can be configured. For
each interface, you must configure:
o Priority (1-16) – No two synchronization sources can have the same priority.
o Quality – The quality level applied to the selected synchronization source. This
enables the system to select the source with the highest quality as the current
synchronization source.
• Each unit determines the current active clock reference source interface:
o The interface with the highest available quality is selected.
o From among interfaces with identical quality, the interface with the highest priority is
selected.
When configuring the Sync source, the Sync mode must be set to its default setting of automatic. To display the
current Sync mode, enter the following CLI command in root view:
root> platform sync mode show
If the Sync mode is set to pipe, you must set it to automatic by entering the following CLI command in root view:
root> platform sync mode set automatic
When configuring an Ethernet interface as a Sync source, the Media Type of the interface must be rj45 or sfp, not
auto-type. To view and configure the Media Type of an Ethernet interface, see Configuring an Interface’s Media
Type (CLI).
This section includes:
• Configuring an Ethernet Interface as a Synchronization Source (CLI)
• Configuring a Radio Interface as a Synchronization Source (CLI)
• Clearing All Sync Sources (CLI)

Phn 3963 013v000

Page 766
Chapter 20: Synchronization (CLI) Configuring the Sync Source (CLI)

Configuring an Ethernet Interface as a Synchronization Source

(CLI)

Note
In order to select an Ethernet interface, you must first specify the media type for this interface. See
Configuring Ethernet Services (CLI).

To configure an Ethernet interface as a synchronization source, enter the following command in root view:
root> platform sync source add eth-interface slot <slot> port <port>
priority <priority> quality <quality>
To edit the parameters of an existing Ethernet interface synchronization source, enter the following command in
root view:
root> platform sync source edit eth-interface slot <slot> port <port>
priority <priority> quality <quality>
To remove an Ethernet interface as a synchronization source, enter the following command in root view:
root> platform sync source remove eth-interface slot <slot> port <port>

Phn 3963 013v000

Page 767
Chapter 20: Synchronization (CLI) Configuring the Sync Source (CLI)

Table 240 Sync Source Ethernet CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 1

port Number 1-3(PTP 820E only) The interface to be configured as a

synchronization source.

priority Number 1 – 16 The priority of this synchronization

source relative to other synchronization
sources configured in the unit.

quality Variable For ETSI systems: The quality level applied to the selected
• automatic synchronization source. This enables the
system to select the source with the
• prc
highest quality as the current
• ssu-a synchronization source.
• ssu-b If the quality is set to automatic, then
• g813.8262 the quality is determined by the
For ANSI (FCC) received SSMs. If no valid SSM messages
systems: are received or in case of interface
failure (such as LOS, LOC, LOF), the
• automatic
quality becomes "failure."
• prs
SSM must be enabled on the remote
• stratum-2 interface in order for the interface to
• transit-node receive SSM messages.
• stratum-3e If the quality is configured to a fixed
• stratum-3 value, then the quality status becomes
“failure” upon interface failure (such as
• smc
LOS, LOC, LOF).
• unknown

The following command configures Ethernet port 2 as a synchronization source with priority = 8, and quality =
automatic:
root> platform sync source add eth-interface slot 1 port 2 priority 8
quality automatic
The following command changes the priority of this synchronization source to 6:
root> platform sync source edit eth-interface slot 1 port 2 priority 6
The following command removes this synchronization source:
root> platform sync source remove eth-interface slot 1 port 2

Configuring a Radio Interface as a Synchronization Source (CLI)

To configure a radio interface as a synchronization source, enter the following command in root view:

Phn 3963 013v000

Page 768
Chapter 20: Synchronization (CLI) Configuring the Sync Source (CLI)

root> platform sync source add radio-interface slot <slot> port <port>
radio-channel <radio-channel> priority <priority> quality <quality>
To edit the parameters of an existing radio interface synchronization source, enter the following command in root
view:
root> platform sync source edit radio-interface slot <slot> port <port>
radio-channel <radio-channel> priority <priority> quality <quality>
To remove a radio interface as a synchronization source, enter the following command in root view:
root> platform sync source remove radio-interface slot <slot> port <port>
radio-channel <radio-channel>

Table 241 Sync Source Radio CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 2

port Number 1-2

radio-channel Number 0 – 85 Must be set to 0.

priority Number 1 – 16 The priority of this synchronization

source relative to other synchronization
sources configured in the unit.

quality Variable For ETSI systems: The quality level applied to the selected
• automatic synchronization source. This enables the
system to select the source with the
• prc
highest quality as the current
• ssu-a synchronization source.
• ssu-b If the quality is set to automatic, then
• g813.8262 the quality is determined by the
For ANSI (FCC) received SSMs. If no valid SSM messages
systems: are received or in case of interface
failure (such as LOS, LOC, LOF), the
• automatic
quality becomes "failure."
• prs
SSM must be enabled on the remote
• stratum-2 interface in order for the interface to
• transit-node receive SSM messages.
• stratum-3e
• stratum-3
• smc
• unknown

The following command configures radio interface 1 as a synchronization source with priority = 16, and quality =
automatic:
root> platform sync source add radio-interface slot 2 port 1 radio-
channel 0 priority 16 quality automatic

Phn 3963 013v000

Page 769
Chapter 20: Synchronization (CLI) Configuring the Sync Source (CLI)

The following command changes the priority of this synchronization source to 14:
root> platform sync source edit radio-interface slot 2 port 1 radio-
channel 0 priority 14
The following command removes this synchronization source:
root> platform sync source remove radio-interface slot 2 port 1 radio-
channel 0

Clearing All Sync Sources (CLI)

To clear all synchronization sources that have been configured in the system, enter the following command in root
view:
root> platform sync source remove all

Phn 3963 013v000

Page 770
Chapter 20: Synchronization (CLI) Configuring the Outgoing Clock (CLI)

Configuring the Outgoing Clock (CLI)

For each interface, you can choose between using the system clock or the interface’s internal clock as its
synchronization source. By default, interfaces use the system clock.
When configuring the outgoing clock, the Sync mode must be set to its default setting of automatic. To display the
current Sync mode, enter the following command in root view:
root> platform sync mode show
If the Sync mode is set to pipe, you must set it to automatic by entering the following command in root view:
root> platform sync mode set automatic
;
To set the interface clock for a radio interface, enter the following command in root view:
root> platform sync interface-clock set radio-interface slot <slot> port
<port> radio-channel <radio-channel> source <source>
To set the interface clock for an Ethernet interface, enter the following command in root view:
root> platform sync interface-clock set eth-interface slot <slot> port
<port> source <source>

Note
To configure the interface clock on an Ethernet interface, the Media Type of the interface must be
rj45 or sfp, not auto-type. To view and configure the Media Type of an Ethernet interface, see
Configuring Ethenet Interfaces (CLI).

Table 242 Outgoing Clock CLI Parameters

Parameter Input Type Permitted Values Description

slot Number ethernet: 1

radio: 2

port Number ethernet: 1-3 The port number of the interface.

(3 only for PTP
820E) radio: 1-
2
(2 only for PTP 820C
and PTP 820C-HP)

radio-channel Number 0 – 84 The radio-channel configured for the

synchronization source.

Phn 3963 013v000

Page 771
Chapter 20: Synchronization (CLI) Configuring the Outgoing Clock (CLI)

Parameter Input Type Permitted Values Description

source Variable system-clock system-clock – The interface uses the

local-clock system clock as its synchronization
source.
local-clock – The interface uses its
internal clock as its synchronization
source.

The following command sets the clock source for radio interface 2 to its internal clock:
root> platform sync interface-clock set radio-interface slot 2 port 2
radio-channel 0 source local-clock
The following command sets the clock source for Ethernet port 2 to the system clock:
root> platform sync interface-clock set eth-interface slot 1 port 2
source system-clock

Phn 3963 013v000

Page 772
Chapter 20: Synchronization (CLI) Configuring SSM Messages (CLI)

Configuring SSM Messages (CLI)

In order to provide topological resiliency for synchronization transfer, PTP 820C, PTP 820S, PTP 820C-HP and PTP
820E implements the passing of SSM messages over the Ethernet and radio interfaces. SSM timing in PTP 820C
complies with ITU-T G.781.
In addition, the SSM mechanism provides reference source resiliency, since a network may have more than one
source clock.
The following are the principles of operation:
• At all times, each source interface has a “quality status” which is determined as follows:
o If quality is configured as fixed, then the quality status becomes “failure” upon
interface failure (such as LOS, LOC, LOF).
o If quality is automatic, then the quality is determined by the received SSMs. If no
valid SSM messages are received or in case of interface failure (such as LOS, LOC,
LOF), the quality becomes "failure."
• Each unit holds a parameter which indicates the quality of its reference clock. This is the quality of the current
synchronization source interface.
• The reference source quality is transmitted through SSM messages to all relevant radio interfaces.
• In order to prevent loops, an SSM with quality “Do Not Use” is sent from the active source interface (both
radio and Ethernet).
In order for an interface to transmit SSM messages, SSM must be enabled on the interface. By default, SSM is
disabled on all interfaces.
When configuring SSM, the Sync mode must be set to its default setting of automatic. To display the current Sync
mode, enter the following command in root view:
root> platform sync mode show
If the Sync mode is set to pipe, you must set it to automatic by entering the following command in root view:
root> platform sync mode set automatic

To enable SSM on a radio interface, enter the following command in root view:
root> platform sync ssm admin radio-interface slot <slot> port <port>
admin on
To disable SSM on a radio interface, enter the following command in root view:
root> platform sync ssm admin radio-interface slot <slot> port <port>
admin off
To enable SSM on an Ethernet interface, enter the following command in root view:
root> platform sync ssm admin eth-interface slot <slot> port <port> admin
on
To disable SSM on an Ethernet interface, enter the following command in root view:
root> platform sync ssm admin eth-interface slot <slot> port <port> admin
off
The following command enables SSM on radio interface 2:

Phn 3963 013v000

Page 773
Chapter 20: Synchronization (CLI) Configuring SSM Messages (CLI)

root> platform sync ssm admin radio-interface slot 2 port 2 admin on

The following command enables SSM on Ethernet port 1:
root> platform sync ssm admin eth-interface slot 1 port 1 admin on

Phn 3963 013v000

Page 774
Chapter 20: Synchronization (CLI) Displaying Synchronization Status and Parameters (CLI)

Displaying Synchronization Status and Parameters

(CLI)

To display the synchronization sources configured in the system, enter the following command in root view:
root> platform sync source config show
The following is a sample synchronization source display output:
number of configured sources = 4
|============================================================|
| Slot | Port | Type | Instance | Priority | Quality |
|============================================================|
| 1 | 1 | Ethernet | | 11 | automatic |
|------------------------------------------------------------|
| 1 | 2 | Ethernet | | 3 | automatic |
|------------------------------------------------------------|
| 2 | 1 | Radio | | 5 | automatic |
|------------------------------------------------------------|
| 2 | 2 | Radio | | 6 | automatic |
|------------------------------------------------------------|
To display the synchronization source status, enter the following command in root view:
root> platform sync source status show
The following is a sample synchronization source status display output:
number of configured sources = 4
|=============================================================|
| Slot | Port | Type | Instance | Active-Src | Act. Quality | Received
SSM | revert-time |
|=============================================================|
| 1 | 1 | ethernet | | false | PRC | do-not-use | 0 |
|------------------- -----------------------------------------|
| 1 | 2 | ethernet | | false | do-not-use | do-not-use | 0 |
|-------------------------------------------------------------|
| 2 | 1 | radio | | false | failure | do-not-use | 0 |
|------------------- -----------------------------------------|
| 2 | 2 | radio | | true | failure | g.813 | 0 |
|=============================================================|
To display the current system reference clock quality, enter the following command in root view:
root> platform sync source show-reference-clock-quality
To display the current synchronization configuration of the unit’s interfaces, enter the following command in root
view:
root> platform sync interface config show
The following is a sample interface synchronization configuration display output:

Phn 3963 013v000

Page 775
Chapter 20: Synchronization (CLI) Displaying Synchronization Status and Parameters (CLI)

number of configured clock-interfaces = 14

|=============================================================|
| Slot | Port | Type | Trail Radio | Source-Type | SSM-Admin |
|=============================================================|
| 1 | 1 | Ethernet | | System Clock | Off |
| 1 | 2 | Ethernet | | System Clock | Off |
| 1 | 3 | Ethernet | | System Clock | Off |
| 2 | 1 | Radio | | System Clock | On |
| 2 | 2 | Radio | | System Clock | On |
|=============================================================|
To display the current system clock status, enter the following command in root view:
root> platform sync clu-state show
The following is a sample system clock status display output:
CLU is in Free-running mode

Phn 3963 013v000

Page 776
Chapter 20: Synchronization (CLI) Configuring 1588 Transparent Clock (CLI)

Configuring 1588 Transparent Clock (CLI)

Note
1588 Transparent Clock is supported with PTP 820C and PTP 820S.

PTP 820 uses 1588v2-compliant Transparent Clock to counter the effects of delay variation. Transparent Clock
measures and adjusts for delay variation, enabling the PTP 820 to guarantee ultra-low PDV.
A Transparent Clock node resides between a master and a slave node, and updates the timestamps of PTP packets
passing from the master to the slave to compensate for delay, enabling the terminating clock in the slave node to
remove the delay accrued in the Transparent Clock node. The Transparent Clock node is itself neither a master nor
a slave node, but rather, serves as a bridge between master and slave nodes.
Note that in release 10.9.6:
• 1588 TC Transparent Clock is not supported when Master-Slave communication is using the UDP/IPv6
transport layer.
• 1588 TC cannot be used on 1+1 HSB links.
• 1588 TC cannot be used with 2 x 1+0 (East-West) configurations
• If 1588 TC is not supported with Frame Cut-Through.

Note
Make sure to enable Transparent Clock on the remote side of the link before enabling it on the local
side.

To configure Transparent Clock:

1. Add the port receiving synchronization from the customer side as a Sync source. See Configuring an
Ethernet Interface as a Synchronization Source (CLI).
2. Add a radio interface as a Sync source, with lower priority than the port receiving synchronization from
the customer side. See Configuring a Radio Interface as a Synchronization Source (CLI).
3. On the remote side of the radio link, add the radio interface facing the local device as a Sync source, with
Sync Interface Priority 1. See Configuring a Radio Interface as a Synchronization Source (CLI).
4. Add the port receiving synchronization from the customer side as a Sync source, with Sync Interface
Priority 1. See Configuring an Ethernet Interface as a Synchronization Source (CLI).
5. Verify that the Sync Interface Quality Status of the first Sync source is not Failure. See Displaying
Synchronization Status and Parameters (CLI).
6. Enter the following command in root view to enable Transparent Clock:
root> platform sync ptp-tc set admin enable

Note
To disable Transparent Clock, enter the following command in root view:
root> platform sync ptp-tc set admin disable

Phn 3963 013v000

Page 777
Chapter 20: Synchronization (CLI) Configuring 1588 Transparent Clock (CLI)

Note
Disabling 1588 PTP can drastically affect time synchronization performance in the entire network.

7. Enter one of the following commands in root view to assign the radio or Multi-Carrier ABC group that will
carry the PTP packets and determine the direction of the PTP packet flow:
For an individual radio, enter the following command:
root> platform sync ptp-tc set radio slot <slot> port <port> direction
<upstream|downstream>
For a Multi-Carrier ABC group, enter the following command:
root> platform sync ptp-tc set group id <group> direction
<upstream|downstream>
The direction parameter must be set to different values on the two sides of the link, so that if you set the local side
to upstream, you must set the remote side to downstream, and vice versa. Otherwise than that, it does not
matter how you set this parameter.
To display the Transparent Clock settings, enter the following command in root view:
root> platform sync ptp-tc show status
The following commands enable Transparent Clock on radio carrier 1 and configure the radio to send PTP packets
upstream:
root> platform sync ptp-tc set admin enable
root> platform sync ptp-tc set radio slot 2 port 1 direction upstream
The following commands enable Transparent Clock on Multi-Carrier ABC group 1 and configure the radio to send
PTP packets upstream:
root> platform sync ptp-tc set group id mc-abc1 direction upstream

Table 243 1588 Transparent Clock CLI Parameters

Parameter Input Type Permitted Values Description

slot Number 2

port Number 1-2

group Variable mc-abc1

8. 1588 packets should be mapped to CoS 7. By default, 1588 packets are not mapped to any CoS. To map
1588 packets to CoS 7, you must disable CoS preservation for 1588 packets. This must be performed via
CLI, using the following command:
root> ethernet generalcfg ptp-tc cos-preserve set admin disable
9. To map 1588 packets to CoS 7, enter the following command:
root> ethernet generalcfg ptp-tc cos-preserve cos value 7
After you enter these commands, 1588 packets will automatically be mapped to CoS 7.

Phn 3963 013v000

Page 778
Chapter 20: Synchronization (CLI) Configuring 1588 Transparent Clock (CLI)

Note
If necessary, you can use the ethernet generalcfg ptp-tc cos-preserve cos value
command to map a different CoS value (0-7) to 1588 packets, but it is recommended to map 1588
packets to CoS 7.

Phn 3963 013v000

Page 779
Chapter 21: Access Management and Security (CLI) Configuring 1588 Transparent Clock (CLI)

Chapter 21: Access Management and

Security (CLI)
This section includes:
• Configuring the General Access Control Parameters (CLI)
• Configuring the Password Security Parameters (CLI)
• Configuring Users (CLI)
• Configuring RADIUS (CLI)
• Configuring X.509 CSR Certificates and HTTPS (CLI)
• Configuring HTTPS Cipher Hardening (CLI)
• Downloading and Installing an RSA Key (CLI)
• Blocking Telnet Access (CLI)
• Uploading the Security Log (CLI)
• Uploading the Configuration Log (CLI)
• Enabling NETCONF (CLI)Related Topics:
• Logging On (CLI)
• Operating in FIPS Mode (CLI)
• Configuring AES-256 Payload Encryption (CLI)

Phn 3963 013v000

Page 780
Chapter 21: Access Management and Security (CLI) Configuring the General Access Control Parameters (CLI)

Configuring the General Access Control Parameters

(CLI)

To avoid unauthorized login to the system, the following parameters should be set:
• Inactivity Timeout
• Blocking access due to login failures
• Blocking unused accounts
This section includes:
• Configuring the Inactivity Timeout Period (CLI)
• Configuring Blocking Upon Login Failure (CLI)
• Configuring Blocking of Unused Accounts (CLI)

Configuring the Inactivity Timeout Period (CLI)

A system management session automatically times out after a defined period (in minutes) with no user activity. To
configure the session timeout period, enter the following command in root view:
root> platform security protocols-control session inactivity-timeout set
<inactivity-timeout>
To display the currently configured session timeout period, enter the following command in root view:
root> platform security protocols-control session inactivity-timeout show

Table 244 Inactivity Timeout Period CLI Parameters

Parameter Input Type Permitted Values Description

inactivity- Number 1 - 60 The session inactivity timeout period (in

timeout minutes).

Example
The following command sets the session inactivity timeout period to 30 minutes:
root> platform security protocols-control session inactivity-timeout set
30

Configuring Blocking Upon Login Failure (CLI)

Upon a configurable number of failed login attempts, the system blocks the user from logging in for a configurable
number of minutes.
To configure the number of failed login attempts that will temporarily block the user from logging into the system,
enter the following command in root view:

Phn 3963 013v000

Page 781
Chapter 21: Access Management and Security (CLI) Configuring the General Access Control Parameters (CLI)

root> platform security access-control block-failure-login attempt set

<attempt>
To define the period (in minutes) for which a user is blocked after the configured number of failed login attempts,
enter the following command in root view:
root> platform security access-control block-failure-login period set
<period>
To display the current failed login attempt blocking parameters, enter the following command in root view:
root> platform security access-control block-failure-login show

Table 245 Blocking Upon Login Failure CLI Parameters

Parameter Input Type Permitted Values Description

attempt Number 1 - 10 If a user attempts to login to the system

with incorrect credentials this number of
times consecutively, the user will
temporarily be prevented from logging
into the system for the time period
defined by the platform security access-
control block-failure-login period set
command.

period Number 1 - 60 The duration of time, in minutes, that a

user is prevented from logging into the
system after the defined number of
failed login attempts.

Example
The following commands configure a blocking period of 45 minutes for users that perform 5 consecutive failed
login attempts:
root> platform security access-control block-failure-login attempt set 5

root> platform security access-control block-failure-login period set 45

Configuring Blocking of Unused Accounts (CLI)

You can configure a number of days after which a user is prevented from logging into the system if the user has
not logged in for the configured number of days. You can also manually block a specific user.
To configure the blocking of unused accounts period, enter the following command in root view:
root> platform security access-control block-unused-account period set
<period>
Once the user is blocked, you can use the following command to unblock the user:
root> platform security access-control user-account block user-name
<user-name> block no
To manually block a specific user, enter the following command in root view:

Phn 3963 013v000

Page 782
Chapter 21: Access Management and Security (CLI) Configuring the General Access Control Parameters (CLI)

root> platform security access-control user-account block user-name

<user-name> block yes
To display the currently configured blocking of unused account period, enter the following command in root view:
root> platform security access-control block-unused-account show

Table 246 Blocking Unused Accounts CLI Parameters

Parameter Input Type Permitted Values Description

period Number 0, 30 - 90 The number of days after which a user is

prevented from logging into the system
if the user has not logged in for the
configured number of days. If you enter
0, this feature is disabled.

user-name Text String Any valid user name. The name of the user being blocked or
unblocked.

Examples
The following command configures the system to block any user that does not log into the system for 50 days:
root> platform security access-control block-unused-account period set 50
The following commands block, then unblock, a user with the user name John_Smith:
root> platform security access-control user-account block user-name
John_Smith block yes

root> platform security access-control user-account block user-name

John_Smith block no

Phn 3963 013v000

Page 783
Chapter 21: Access Management and Security (CLI) Configuring the Password Security Parameters (CLI)

Configuring the Password Security Parameters

(CLI)

You can configure enhanced security requirements for user passwords.

This section includes:
• Configuring Password Aging (CLI)
• Configuring Password Strength Enforcement (CLI)
• Forcing Password Change Upon First Login (CLI)
• Displaying the System Password Settings (CLI)

Configuring Password Aging (CLI)

Passwords remain valid from the first time the user logs into the system for the number of days (20-90) set by this
command. If you set this parameter to 0, password aging is disabled, and passwords remain valid indefinitely.
To configure password aging, enter the following command in root view:
root> platform security access-control password aging set <password
aging>

Table 247 Password Aging CLI Parameters

Parameter Input Type Permitted Values Description

password Number 0, 20 - 90 The number of days that user passwords

aging will remain valid from the first time the
user logs into the system.

Example
The following command sets the password aging time to 60 days:
root> platform security access-control password aging set 60

Configuring Password Strength Enforcement (CLI)

To set password strength enforcement, enter the following command in root view:
root> platform security access-control password enforce-strength set
<enforce-strength>

Phn 3963 013v000

Page 784
Chapter 21: Access Management and Security (CLI) Configuring the Password Security Parameters (CLI)

Table 248 Password Strength Enforcement CLI Parameters

Parameter Input Type Permitted Values Description

password Number 0, 20 - 90 The number of days that user passwords

aging will remain valid from the first time the
user logs into the system.

enforce- Boolean Yes When yes is selected:

strength no Password length must be at least eight
characters.
Password must include characters of at
least three of the following character
types: lower case letters, upper case
letters, digits, and special characters. For
purposes of meeting this requirement,
upper case letters at the beginning of
the password and digits at the end of
the password are not counted.
The last five password you used cannot
be reused.

Example
The following command enables password strength enforcement:
root> platform security access-control password enforce-strength set yes

Forcing Password Change Upon First Login (CLI)

To determine whether the system requires users to change their password the first time they log into the system,
enter the following command in root view.
root> platform security access-control password first-login set <first-
login>
To require users to change their password the first time they log in, enter the following command in root view:
root> platform security access-control password first-login set yes

Table 249 Force Password Change on First Time Login CLI Parameters

Parameter Input Type Permitted Values Description

first-login Boolean Yes When yes is selected, the system

no requires users to change their password
the first time they log in.

Phn 3963 013v000

Page 785
Chapter 21: Access Management and Security (CLI) Configuring the Password Security Parameters (CLI)

Displaying the System Password Settings (CLI)

Use the following command to display the system password settings:
root> platform security access-control password show-all

Phn 3963 013v000

Page 786
Chapter 21: Access Management and Security (CLI) Configuring Users (CLI)

Configuring Users (CLI)

This section includes:

• User Configuration Overview (CLI)
• Configuring User Profiles (CLI)
• Configuring User Accounts (CLI)
Related topics:
• Logging On (CLI)

User Configuration Overview (CLI)

User configuration is based on the Role-Based Access Control (RBAC) model. According to the RBAC model,
permissions to perform certain operations are assigned to specific roles. Users are assigned to particular roles, and
through those role assignments acquire the permissions to perform particular system functions.
In the PTP 820 GUI, these roles are called user profiles. Up to 50 user profiles can be configured. Each profile
contains a set of privilege levels per functionality group, and defines the management protocols (access channels)
that can be used to access the system by users to whom the user profile is assigned.
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. For each functionality group, the access
level is defined separately for read and write operations. The following access levels can be assigned:
• None – No access to this functional group.
• Normal – The user has access to parameters that require basic knowledge about the functional group.
• Advanced – The user has access to parameters that require advanced knowledge about the functional group,
as well as parameters that have a significant impact on the system as a whole, such as restoring the
configuration to factory default settings.

Configuring User Profiles (CLI)

User profiles enable you to define system access levels. Each user must be assigned a user profile. Each user profile
contains a detailed set of read and write permission levels per functionality group.
The system includes a number of pre-defined user profiles. You can edit these profiles, and add user profiles.
Together, the system supports up to 50 user profiles.
To create a new user profile with default settings, enter the following command:

Phn 3963 013v000

Page 787
Chapter 21: Access Management and Security (CLI) Configuring Users (CLI)

root> platform security access-control profile add name <profile-name>

To edit the settings of a user profile, enter the following command:
root> platform security access-control profile edit group name <profile-
name> group <group> write-lvl <write-lvl> read-lvl <read-lvl>

Table 250 User Profile CLI Parameters

Parameter Input Type Permitted Values Description

profile--name Text String Up to 49 characters The name of the user profile.

group Variable security The functionality group for which you

management are defining access levels.
radio
ethernet
sync

write-lvl Variable none The read level for the functionality

normal group.
advanced

read-lvl Variable none The read level for the functionality

normal group.
advanced

Example
The following commands create a user profile called “operator” and give users to whom this profile is assigned
normal write privileges for all system functionality and advanced read privileges for all functionality except security
features.
root> platform security access-control profile add name operator

root> platform security access-control profile edit group name operator

group security write-lvl normal read-lvl normal group management write-
lvl normal read-lvl advanced group radio write-lvl normal read-
lvl advanced group ethernet write-lvl normal read-lvl advanced group sync
write-lvl normal read-lvl advanced

Limiting Access Protocols for a User Profile (CLI)

The user profile can limit the access channels that users with the user profile can use to access the system. By
default, a user profile includes all access channels.
Use the following command to limit the protocols users with this user profile can use to access the system.
root> platform security access-control profile edit mng-channel name
<profile-name> channel-type <channel-type> allowed <allowed>

Table 251 User Profile Access Protocols CLI Parameters

Phn 3963 013v000

Page 788
Chapter 21: Access Management and Security (CLI) Configuring Users (CLI)

Parameter Input Type Permitted Values Description

profile--name Text String Up to 49 characters The name of the user profile.

profile-name Text String Up to 49 characters The name of the user profile.

channel-type Variable Serial The access channel type allowed or

Web disallowed by the command for users
with this user profile.
NMS
Telnet
SSH

allowed Boolean yes yes – Users with this user profile can
no access the access channel type defined
in the preceding parameter.
no - Users with this user profile cannot
access the access channel type defined
in the preceding parameter.

Example
The following command prevents users with the user profile “operator” from accessing the system via NMS:
root> platform security access-control profile edit mng-channel name
operator channel-type NMS allowed no

Configuring User Accounts (CLI)

You can configure up to 2,000 users. Each user has a user name, password, and user profile. The user profile
defines a set of read and write permission levels per functionality group (see Configuring User Profiles (CLI)).
To create a new user account, enter the following command:
root> platform security access-control user-account add user-name <user-
name> profile-name <profile-name> expired-date <expired-date>
When you create a new user account, the system will prompt you to enter a default password. If Enforce Password
Strength is activated (refer to Configuring Password Strength Enforcement (CLI)), the password must meet the
following criteria:
• Password length must be at least eight characters.
• Password must include characters of at least three of the following character types: lower case letters, upper
case letters, digits, and special characters. For purposes of meeting this requirement, upper case letters at the
beginning of the password and digits at the end of the password are not counted.
• The last five password you used cannot be reused.
To block or unblock a user account, enter the following command:
root> platform security access-control user-account block user-name
<user-name> block <block>
To change a user account's expiration date, enter the following command:

Phn 3963 013v000

Page 789
Chapter 21: Access Management and Security (CLI) Configuring Users (CLI)

root> platform security access-control user-account edit expired-date

user-name <user-name> expired-date <expired-date>

Note
The latest date that can be configured is 30-12-2037. If no expiration date is configured, the user
account will expire five years after the date configured on the unit.

To change a user account's profile, enter the following command:

root> platform security access-control user-account edit profile-name
user-name <user-name> profile-name <profile name>
To delete a user account, enter the following command:
root> platform security access-control user-account delete user-name
<user-name>
To display all user accounts configured on the unit and their settings, including whether the user is currently
logged in and the time of the user's last logout, enter the following command:
root> platform security access-control user-account show
To display the settings of a specific user account, enter the following command:
root> platform security access-control user-account show user-name <user-
name>

Table 252 User Accounts CLI Parameters

Parameter Input Type Permitted Values Description

user-name Text String Up to 32 characters The name of the user profile.

profile name Text String Up to 49 characters The name of the User Profile you want
to assign to the user. The User Profile
defines the user’s access permissions
per functionality group.

expired-date Date Use the format: Optional. The date on which the user
YYYY-MM-DD account will expire. On this date, the
user automatically becomes inactive.

block Variable yes yes - blocks the account.

no no - unblocks the account.

Example
The following command creates a user account named Tom_Jones, with user profile “operator”. This user’s
account expires on February 1, 2014.
root> platform security access-control user-account add user-name
Tom_Jones profile-name operator expired-date 2014-02-01

Phn 3963 013v000

Page 790
Chapter 21: Access Management and Security (CLI) Configuring RADIUS (CLI)

Configuring RADIUS (CLI)

This section includes:

• RADIUS Overview (CLI)
• Activating RADIUS Authentication (CLI)
• Configuring the RADIUS Server Attributes (CLI)
• Viewing RADIUS Access Control and Server Attributes (CLI)
• Viewing RADIUS User Permissions and Connectivity (CLI)

RADIUS Overview (CLI)

The RADIUS protocol provides centralized user management services. PTP 820 supports RADIUS server and
provides a RADIUS client for authentication and authorization. When RADIUS is enabled, a user attempting to log
into the system from any access channels (CLI, WEB, NMS) is not authenticated locally. Instead, the user’s
credentials are sent to a centralized standard RADIUS server which indicates to the PTP 820 whether the user is
known, and which privilege is to be given to the user.
You can define up to two Radius servers. If you define two, one serves as the primary server and the other as the
secondary server.

Activating RADIUS Authentication (CLI)

To enable or disable Radius access control, enter the following command:
root> platform security radius-admin set <admin>

Table 253 Activate RADIUS CLI Parameters

Parameter Input Type Permitted Values Description

admin Variable enable Enables or disables Radius access

disable control.

Configuring the RADIUS Server Attributes (CLI)

To configure Radius server attributes, enter the following command:
root> platform security radius-server-communication-ipv4 set server-id
<server-id> ip-address <ip-address> port <radius-port> retries <retries>
timeout <timeout> secret <shared-secret>

Table 254 Configure RADIUS Server CLI Parameters

Phn 3963 013v000

Page 791
Chapter 21: Access Management and Security (CLI) Configuring RADIUS (CLI)

Parameter Input Type Permitted Values Description

server-id Number 1 1 - The primary Radius server

2 2 - The secondary Radius server.

ip-address Dotted Any valid IP address The IP address of the Radius server.
decimal
format

radius-port Number 0-65535 The port ID of the RADIUS server.

retries Number 3-30 The number of times the device will try
to communicate with the RADIUS server
before declaring the server to be
unreachable.

timeout Number 1-10 The timeout (in seconds) that the agent
will wait in during each communication
with the selected RADIUS server before
retrying if no response is received.

shared-secret String Between 22-128 The shared secret of the RADIUS server.
characters

Example
The following command configures Radius server attributes for the primary Radius server:
root> platform security radius-server-communication-ipv4 set server-id 1
ip-address 192.168.1.99 port 1812 retries 5 timeout 10 secret
U8glp3KJ6FKGksdgase4IQ9FMm

Displaying Remote Access Users

You can view remote access user connectivity and permissions information for all Radius users currently
connected. To do so, enter the following command:
root> platform security radius-server-privileges show
The following user information is displayed, for each currently connected Radius user:
• User Name - The user name
• Access Channels - The permitted access channels.
• Number of Active Sessions - The number of currently open sessions.
• Security Func Group Read level – The Read access level in the Security functional group: None, Regular or
Advanced.
• Security Func Group Write level – The Write access level in the Security functional group: None, Regular or
Advanced.
• Management Func Group Read level – The Read access level in the Management functional group: None,
Regular or Advanced.

Phn 3963 013v000

Page 792
Chapter 21: Access Management and Security (CLI) Configuring RADIUS (CLI)

• Management Func Group Write level – The Write access level in the Management functional group: None,
Regular or Advanced.
• Radio Func Group Read level – The Read access level in the Radio functional group: None, Regular or
Advanced.
• Radio Func Group Write level – The Write access level in the Radio functional group: None, Regular or
Advanced.
• TDM Func Group Read level – The Read access level in the TDM functional group: None, Regular or Advanced.
• TDM Func Group Write level – The Write access level in the TDM functional group: None, Regular or
Advanced.
• Eth Func Group Read level – The Read access level in the Eth functional group: None, Regular or Advanced.
• Eth Func Group Write level – The Write access level in the Eth functional group: None, Regular or Advanced.
• Sync Func Group Read level – The Read access level in the Sync functional group: None, Regular or Advanced.
• Sync Func Group Write level – The Write access level in the Sync functional group: None, Regular or
Advanced.

Phn 3963 013v000

Page 793
Chapter 21: Access Management and Security (CLI) Configuring X.509 CSR Certificates and HTTPS (CLI)

Configuring X.509 CSR Certificates and HTTPS (CLI)

The web interface protocol for accessing PTP 820 can be configured to HTTP (default) or HTTPS. It cannot be set to
both at the same time.
Before setting the protocol to HTTPS, you must:
1 Create and upload a CSR file. See Generating a Certificate Signing Request (CSR) File (CLI).
2 Download the certificate to the PTP 820 and install the certificate. See Downloading a Certificate (CLI).
3 Enable HTTPS. See Enabling HTTPS (CLI).
When uploading a CSR and downloading a certificate, the PTP 820 functions as an SFTP client. You must install
SFTP server software on the PC or laptop you are using to perform the upload or download. For details, see
Installing and Configuring an FTP or SFTP Server.

Note
For these operations, SFTP must be used.

This section includes:

• Generating a Certificate Signing Request (CSR) File (CLI)
• Downloading a Certificate (CLI)
• Enabling HTTPS (CLI)

Generating a Certificate Signing Request (CSR) File (CLI)

Note
If you need a customized public RSA key, you must download and install the RSA key first, before
generating a CSR file. Otherwise, the CSR file will include the current public RSA key. See
Downloading and Installing an RSA Key (CLI).

To set the CSR parameters, enter the following command in root view:
root> platform security csr-set-parameters common-name <common-name>
country <country> state <state> locality <locality> organization
<organization> org-unit <org-unit> email <email> file-format <file-
format>
To display the currently-configured CSR parameters, enter the following command in root view:
root> platform security csr-show-parameters
If the IP address family is configured to be IPv4, enter the following command in root view to configure the SFTP
server parameters for the CSR file upload:
root> platform security csr-set-server-parameters server-ipv4 <server-
ipv4> server-path <server-path> filename <filename> server-username
<username> server-password <password>
If the IP address family is configured to be IPv6, enter the following command in root view to configure the SFTP
server parameters for the CSR file upload:

Phn 3963 013v000

Page 794
Chapter 21: Access Management and Security (CLI) Configuring X.509 CSR Certificates and HTTPS (CLI)

root> platform security csr-set-server-parameters server-ipv6 <server-

ipv6> server-path <server-path> filename <filename> server-username
<username> server-password <password>
To display the currently-configured SFTP parameters for CSR upload, enter the following command in root view:
root> platform security csr-show-server-parameters
To generate and upload a CSR, enter the following command in root view:
root> platform security csr-generate-and-upload
To display the status of a pending CSR generation and upload operation, enter the following command in root
view:
root> platform security csr-generate-and-upload-show-status

Table 255 CSR Generation and Upload CLI Parameters

Parameter Input Type Permitted Values Description

common String The fully–qualified domain name for

name your web server. You must enter the
exact domain name.

country String The two-letter ISO abbreviation for your

country (e.g., US)

state String The state, province, or region in which

the organization is located. Do not
abbreviate.

locality String The city in which the organization is

legally located.

organization String The exact legal name of your

organization. Do not abbreviate.

org-unit String The division of the organization that

handles the certificate.

email String An e-mail address that can be used to

contact your organization.

file-format Variable PEM The file format of the CSR. In this

DER version, only PEM is supported.

server-ipv4 Dotted Any valid IPv4 IP The IPv4 address of the PC or laptop you
decimal address. are using as the SFTP server.
format.

server-ipv6 Eight groups Any valid IPv6 address. The IPv6 address of the PC or laptop you
of four are using as the SFTP server.
hexadecimal
digits
separated by
colons.

Phn 3963 013v000

Page 795
Chapter 21: Access Management and Security (CLI) Configuring X.509 CSR Certificates and HTTPS (CLI)

Parameter Input Type Permitted Values Description

server-path Text String The directory path to which you are

uploading the CSR. Enter the path
relative to the SFTP user's home
directory, not the absolute path.If the
location is the home directory, it should
be left empty. If the location is a sub-
folder under the home directory, specify
the folder name. If the shared folder is
"C:\", this parameter can be left empty
or populated with "//".

filename Text String The name you want to give the CSR.

username Text String The user name for the SFTP session.

password Text String The password for the SFTP session. To

configure the SFTP settings without a
password, simply omit this parameter.

Downloading a Certificate (CLI)

If the IP address family is configured to be IPv4, enter the following command in root view to configure the SFTP
server parameters for downloading a certificate:
root> platform security certificate-set-download-parameters server-ipv4
<server-ipv4> server-path <server-path> filename <filename> server-
username <username> server-password <password>
If the IP address family is configured to be IPv6, enter the following command in root view to configure the SFTP
server parameters for downloading a certificate:
root> platform security certificate-set-download-parameters server-ipv6 <
server-ipv6> server-path <server-path> filename <filename> server-
username <username> server-password <password>
To display the currently-configured SFTP parameters for downloading a certificate, enter the following command
in root view:
root> platform security certificate-show-download-parameters
To download a certificate, enter the following command in root view:
root> platform security certificate-download
To display the status of a pending certificate download, enter the following command in root view:
root> platform security certificate-download-show-status
To install a certificate, enter the following command in root view:
root> platform security certificate-install

Phn 3963 013v000

Page 796
Chapter 21: Access Management and Security (CLI) Configuring X.509 CSR Certificates and HTTPS (CLI)

Table 256 Certificate Download and Install CLI Parameters

Parameter Input Type Permitted Values Description

server-ipv4 Dotted Any valid IPv4 IP The IPv4 address of the PC or laptop you
decimal address. are using as the SFTP server.
format.

server-ipv6 Eight groups Any valid IPv6 address. The IPv6 address of the PC or laptop you
of four are using as the SFTP server.
hexadecimal
digits
separated by
colons.

server-path Text String The directory path from which you are
downloading the certificate. Enter the
path relative to the SFTP user's home
directory, not the absolute path. If the
location is the home directory, it should
be left empty. If the location is a sub-
folder under the home directory, specify
the folder name. If the shared folder is
"C:\", this parameter can be left empty
or populated with "//".

filename Text String The certificate’s file name in the SFTP

server.

username Text String The user name for the SFTP session.

password Text String The password for the SFTP session. To

configure the SFTP settings without a
password, simply omit this parameter.

Enabling HTTPS (CLI)

By default, HTTP is used by PTP 820 as its web interface protocol.
To change the protocol to HTTPS, enter the following command in root view:
root> platform security url-protocol-set url-protocol https

Note
Make sure you have installed a valid certificate in the PTP 820 before changing the web interface
protocol to HTTPS. Failure to do this may prevent users from accessing the Web EMS.

To change the protocol back to HTTP, enter the following command in root view:

Phn 3963 013v000

Page 797
Chapter 21: Access Management and Security (CLI) Configuring X.509 CSR Certificates and HTTPS (CLI)

root> platform security url-protocol-set url-protocol http

To display which protocol is currently enabled, enter the following command in root view:
root> platform security url-protocol-show

Phn 3963 013v000

Page 798
Chapter 21: Access Management and Security (CLI) Configuring HTTPS Cipher Hardening (CLI)

Configuring HTTPS Cipher Hardening (CLI)

You can configure the PTP 820 to operate in HTTPS strong mode. In HTTPS strong mode, SSLv3, TLSv1.0, and
TLSv1.1 are disabled completely and only certain ciphers are supported in TLSv1.2.
In FIPS mode also, SSLv3, TLSv1.0, and TLSv1.1 are disabled completely and only certain ciphers are supported in
TLSv1.2.
For a list of supported HTTPS ciphers, including an indication of which ciphers are supported in HTTPS strong mode
and FIPS mode, refer to Annex B – Supported Ciphers for Secured Communication Protocols in the Release Notes
for the System release version you are using.

Note
HTTPS cipher hardening is supported from system release 10.3. HTTPS cipher hardening is not
available in FIPS mode.

To set HTTPS strong mode, enter the following command:

root> platform security https-ciphers-hardening-level-set level strong
To set HTTPS normal mode, enter the following command:
root> platform security https-ciphers-hardening-level-set level normal
Note: The default HTTP cipher mode is normal.
To display the current HTTPS cipher mode, enter the following command:
root> platform security https-ciphers-hardening-level-show

Phn 3963 013v000

Page 799
Chapter 21: Access Management and Security (CLI) Downloading and Installing an RSA Key (CLI)

Downloading and Installing an RSA Key (CLI)

PTP 820 devices support RSA keys for communication using HTTPS and SSH protocol. The PTP 820 device comes
with randomly generated default private and public RSA keys. However, you can replace the private key with a
customer-defined private key. The corresponding RSA public key will be generated based on this private key. The
file must be in PEM format. Supported RSA private key sizes are 2048, 4096, and 8192.
The following is an example of a valid RSA private key file:
-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC+7jRmt27yF4xDh5Pc8w4ikvXUu32BI0eOyELmeUB
nEeIHbCOXD3upi8+ZnH51Q+8hzgoSqXgEYFgZMoF/sXCrO2yf62UJ5ohj3zadhx/7585zoGwHtYz1S62hsa4+cdAl/i1Vbc
6CoUBh5642XYje+Q+q1XJtObed884eaQcXUFLlBipYKvVx2kuelymansE91WJU+UjFlc3aiQG8qsSgW5Ar6wet0pXkP2V
demo//QAXXjcTqqMBuizrlhlcvi+OKYFl9kSh21ZqSgjvK3cfAssCJBIY5d6t6bVkX9p2gjo/IPnErjAv7W6lZoemotb5KAeSHe
R1sYTw17/xIpM7AgMBAAECggEAAwliLKQMOq4kh/UXD/OPAlPDXyp1jjaTw8dBm811OG5wttzXGrxJ+OIFX5Rn79Db
HnbayCiJL8tMe2dx5yhY+hA247roX3ua0w57cuPxnp21izc+S0fC7H/TTM1jpRCbATparuTRMlitinZshJGA73Lsod3v36GE
Xxm/6dHnz/drCs2F4NdHWpjMAAG/1CiBwut8jNkJUwa78Ivk3JF+XRoZ0txN2mIybQxxzjuNXqZbNO6H3Ua2u1iYyD+
McfgOWCCUfSnstGRhFg0OsQuqj6d74qKVQWaukEH91SVZHEoqX6DgpKy4INZBxORZmlTNmadwNhw5O7rvFxZ205u
4gQKBgQDT5bXvc0Ok+Ypm2xnIbu2GFjxNYwYhR3TvHPy14NIO5Q9I/uDqwrSL1igzalr6EbZyLu8cDXa4aybrzCyBfPeG8
9Qq+a6J3JR/RwJndLyjV4h5CT8Zy4O/wjgTrP3Rhq7LAbWgLjSarafLgruHTcnOifhkK7MK7Fr+xi2IJfOKQQKBgQDmq1eY
NzlMPlATESlsfbkcL49jSsu70kYg0g5Iol6+bVPo9K7mopICtWC/fwdNlUAfO+vr/231YUfSo7YNEDNNRoT/NwvqqtAYxZaI
UdIQxhMywF9jjYBBuq6+f/7+dwDfNBtMb2q7hceTdk6yZ8/MehCkvSwOBmP+lq0FwTmmewKBgQClxmj31G1ve+rTX
UZmkKIy7OJwiLAbCRRqnXr3r9Om43151i2QfJNTc1AwKVzTl1ftLNrUT5Q541qnzyxigaoFYmzy0jPCl1d128/9sE6EW87
hImLDg3ynYQMOIaDRc1T8bXHyxzNQb9t+U+DykeD4POifNbD1MsRd3h1xDn/iAQKBgHmKpukJkCNgYgjp7g3AYR084i
zLaHZa4aDBjc0v4QQtzxzccJwN5SmQMJ42bL6wecz7YeBEAshcrd+La42Oj7mUAtgHRTwtLOEgm6TQmANGmy8OtjRa
hs4bc5/lCZNDWS5C4m9v9alBYFuO5wCSOqffWY20L9Zj/6RR+HEj0yCpAoGAHwrbRqPVZtZptFuNsCq130dtmqI7HFQ
Alqrc5DwP7YSsznE6biHfLUw891xu0vmevALrCaoeOMaidugohgiorSJO4qk7I3XN3pUJhPYqbhtdCVnBI2Fm9pr3V/SHG
vrl1NW92cXObeQ2UEBiKPOyQKfOBlbac707u0HqaTu+/ts=
-----END PRIVATE KEY-----
You can download and install a private RSA key via HTTP, HTTPS, or SFTP. It is strongly recommended not to use
HTTP to download RSA key files.
Note: To download an RSA key file using HTTP or HTTPS, you must use the Web EMS. See
Downloading an RSA Key via HTTP or HTTPS.
To display the current RSA public key, enter the following command in root view:
root> platform security rsa-show-installed-public-key
If the IP address family is configured to be IPv4, enter the following command in root view to configure the SFTP
server parameters for downloading the RSA key:
root> platform security rsa-set-download-parameters server-ipv4 <server-
ipv4> server-path <server-path> filename <filename> server-username
<username> server-password <password>
If the IP address family is configured to be IPv6, enter the following command in root view to configure the SFTP
server parameters for downloading the RSA key:
root> platform security rsa-set-download-parameters server-ipv6 <server-
ipv6> server-path <server-path> filename <filename> server-username
<username> server-password <password>
To download an RSA key, enter the following command in root view:
root> platform security rsa-download

Phn 3963 013v000

Page 800
Chapter 21: Access Management and Security (CLI) Downloading and Installing an RSA Key (CLI)

To install the RSA key, enter the following command in root view:
root> platform security rsa-install

Table 257: RSA Key Download and Install CLI Parameters

Paramet Input Permitt Description
er Type ed
Values
server- Dotted Any valid The IPv4 address of the PC or
ipv4 decimal IPv4 IP laptop you are using as the SFTP
format. address. server.

server- Eight Any valid The IPv6 address of the PC or

ipv6 groups of IPv6 laptop you are using as the SFTP
four address. server.
hexadeci
mal digits
separated
by colons.

server- Text The directory path from which you

path String are downloading the RSA key.
Enter the path relative to the SFTP
user's home directory, not the
absolute path. If the location is
the home directory, it should be
populated with "". If the location
is a sub-folder under the home
directory, specify the folder name.
If the shared folder is "C:\", this
parameter can be populated with
"".

filename Text The RSA key file’s name in the

String SFTP server.

username Text The user name for the SFTP

String session.

password Text The password for the SFTP

String session. To configure the SFTP
settings without a password,
populate this parameter with “”..

Phn 3963 013v000

Page 801
Chapter 21: Access Management and Security (CLI) Blocking Telnet Access (CLI)

Blocking Telnet Access (CLI)

You can block telnet access to the unit. By default, telnet access is not blocked.
To block telnet access, enter the following command:
root> platform security protocols-control telnet admin set disable
To unblock telnet access, enter the following command:
root> platform security protocols-control telnet admin set enable
To display whether telnet is currently allowed (enable) or blocked (disable), enter the following command:
root> platform security protocols-control telnet show

Note
When you block telnet, any current telnet sessions are immediately disconnected.

Phn 3963 013v000

Page 802
Chapter 21: Access Management and Security (CLI) Uploading the Security Log (CLI)

Uploading the Security Log (CLI)

The security log is an internal system file which records all changes performed to any security feature, as well as all
security related events.
In order to read the security log, you must upload the log to an FTP or SFTP server. PTP 820 works with any
standard FTP or SFTP server. For details, see Installing and Configuring an FTP or SFTP Server.
Before uploading the security log, you must install and configure the FTP server on the laptop or PC from which
you are performing the download. See Installing and Configuring an FTP or SFTP Server.
To set the FTP parameters for security log upload, enter the following command in root view:
root> platform security file-transfer set server-path <server-path> file-
name <file-name> ip-address <ip-address> protocol <protocol> username
<username> password <password>
To display the FTP channel parameters for uploading the security log, enter the following command in root view:
root> platform security file-transfer show configuration
To upload the security log to your FTP server, enter the following command in root view:
root> platform security file-transfer operation set upload-security-log
To display the progress of a current security log upload operation, enter the following command in root view:
root> platform security file-transfer show operation
To display the result of the most recent current security log upload operation, enter the following command in
root view:
root> platform security file-transfer show status

Table 258 Security Log CLI Parameters

Parameter Input Type Permitted Values Description

server-path Text String The directory path to which you are

uploading the security log. Enter the
path relative to the FTP user's home
directory, not the absolute path. If the
location is the home directory, it should
be left empty. If the location is a sub-
folder under the home directory, specify
the folder name. If the shared folder is
"C:\", this parameter can be left empty
or populated with "//".

file-name Text String The name you want to give the file you
are uploading.

ip-address Dotted Any valid IP address. The IP address of the FTP server.
decimal
format.

Phn 3963 013v000

Page 803
Chapter 21: Access Management and Security (CLI) Uploading the Security Log (CLI)

Parameter Input Type Permitted Values Description

protocol Variable ftp

sftp

username Text String The user name for the FTP or SFTP
session.

password Text String The password for the FTP or SFTP

session. To configure the FTP settings
without a password, simply omit this
parameter.

Example
The following commands configure an FTP channel for security log upload to IP address 192.168.1.80, in the
directory “current”, with file name “security_log_Oct8.zip”, user name “anonymous”, and password “12345”, and
initiate the upload:
root> platform security file-transfer set server-path \current file-name
security_log_Oct8.zip ip-address 192.168.1.80 protocol ftp username
anonymous password 12345

root> platform security file-transfer operation set upload-security-log

Phn 3963 013v000

Page 804
Chapter 21: Access Management and Security (CLI) Uploading the Configuration Log (CLI)

Uploading the Configuration Log (CLI)

The configuration log lists actions performed by users to configure the system. This file is mostly used for security,
to identify suspicious user actions. It can also be used for troubleshooting.
In order to upload the configuration log, you must install an FTP or SFTP server on the laptop or PC from which you
are performing the upload. PTP 820 works with any standard FTP or SFTP server. For details, see Installing and
Configuring an FTP or SFTP Server.
To set the FTP or SFTP parameters for configuration log export, enter the following command in root view:
root> platform security configuration-log-upload-params set path <path>
file-name <file-name> ip-address <ip-address> protocol <protocol>
username <username> password <password>
To display the FTP or SFTP parameters for configuration log export, enter the following command in root view:
root> platform security configuration-log-upload-params show
To export the configuration log, enter the following command in root view:
root> platform security configuration-log upload
To display the status of a configuration log export operation, enter the following command in root view
root> platform security configuration-log-upload-status show

Table 259 Configuration Log CLI Parameters

Parameter Input Type Permitted Values Description

path Text String The directory path to which you are

exporting the configuration log. Enter
the path relative to the FTP user's home
directory, not the absolute path. If the
location is the home directory, it should
be left empty. If the location is a sub-
folder under the home directory, specify
the folder name. If the shared folder is
"C:\", this parameter can be left empty
or populated with "//".

Phn 3963 013v000

Page 805
Chapter 21: Access Management and Security (CLI) Uploading the Configuration Log (CLI)

Parameter Input Type Permitted Values Description

file-name Text String The name you want to give the file you
are exporting.
Note: You must add the suffix .zip to
the file name. Otherwise, the file import
may fail. You can export the file using
any name, then add the suffix .zip
manually. For example: UnitInfo.zip
If the Unit Information file is exported
several times consecutively, the file
itself will not be replaced. Instead, the
filename will be updated by time stamp.
For example: UnitInfo.zip.11-05-14 03-
31-04

ip-address Dotted Any valid IP address. The IP address of the PC or laptop you
decimal are using as the FTP or SFTP server.
format.

protocol Variable ftp The file transfer protocol.

sftp

username Text String The user name for the FTP or SFTP
session.

password Text String The password for the FTP or SFTP

session. To configure the FTP or SFTP
settings without a password, simply
omit this parameter.

Note
The path and fie name, together, cannot be more than:
If the IP address family is configured to be IPv4: 236 characters
If the IP address family is configured to be IPv6: 220 characters

Examples
The following commands configure an FTP channel for configuration log export to IP address 192.168.1.99, in the
directory “current”, with file name “cfg_log”, user name “anonymous”, and password “12345.”
root> platform security configuration-log-upload-params set path \file-
name cfg_log ip-address 192.168.1.99 protocol ftp username anonymous
password 12345

root> platform unit-info channel set protocol frp

The following command exports the configuration log to the external server location:

Phn 3963 013v000

Page 806
Chapter 21: Access Management and Security (CLI) Uploading the Configuration Log (CLI)

root> platform security configuration-log upload

Phn 3963 013v000

Page 807
Chapter 21: Access Management and Security (CLI) Enabling NETCONF (CLI)

Enabling NETCONF (CLI)

PTP 820 devices support SDN, with NETCONF/YANG capabilities. This enables PTP 820
devices to be managed via SDN using Cambium Networks SDN controller, SDN Master.
In order for the device to be managed via SDN, you must enable NETCONF on the device. By default,
NETCONF is disabled.
To enable NETCONF, enter the following command in root view:

root>platform security protocols-control netconf admin set

enable

To disable NETCONF, enter the following command in root view:

root>platform security protocols-control netconf admin set

disable

To display the current NETCONF configuration on the device, enter the following command in root
view:
root>platform security protocols-control netconf show-all

Phn 3963 013v000

Page 808
Chapter 21: Access Management and Security (CLI) Terminating all Active Sessions (CLI)

Terminating all Active Sessions (CLI)

You can terminate all active sessions of all users by entering the following command in root view:

root> platform security access-control disconnect all

This command terminates sessions using any channel type:
• Serial
• Web
• NMS
• Telnet
• SSH

Phn 3963 013v000

Page 809
Chapter 22: Alarm Management and Troubleshooting (CLI) Terminating all Active Sessions (CLI)

Chapter 22: Alarm Management and

Troubleshooting (CLI)
This section includes:
• Viewing Current Alarms (CLI)
• Viewing the Event Log (CLI)
• Editing Alarm Text and Severity (CLI)
• Configuring a Timeout for Trap Generation (CLI)
• Disabling Alarms and Events (CLI)
• Configuring Voltage Alarm Thresholds and Displaying Voltage PMs (CLI)
• Uploading Unit Info (CLI)
• Activating the Radio Logger (CLI)
• Performing Diagnostics (CLI)
• Working in CW Mode (Single or Dual Tone) (CLI)

Phn 3963 013v000

Page 810
Chapter 22: Alarm Management and Troubleshooting (CLI) Viewing Current Alarms (CLI)

Viewing Current Alarms (CLI)

To display all alarms currently raised on the unit, enter the following command in root view:
root> platform status current-alarm show module unit
To display the most severe alarm currently raised in the unit, enter the following command in root view:
root> platform status current-alarm show most-severe-alarm module unit

Phn 3963 013v000

Page 811
Chapter 22: Alarm Management and Troubleshooting (CLI) Viewing the Event Log (CLI)

Viewing the Event Log (CLI)

The Event Log displays a list of current and historical events and information about each event.
To display the event log, enter the following command in root view:
root> platform status event-log show module unit
To clear the event log, enter the following command in root view:
root> platform status event-log clear module unit

Note
You can save the event log to a CSV file from the Web EMS. See Viewing and Saving the Event Log

Phn 3963 013v000

Page 812
Chapter 22: Alarm Management and Troubleshooting (CLI) Editing Alarm Text and Severity (CLI)

Editing Alarm Text and Severity (CLI)

You can view a list of alarm types, edit the severity level assigned to individual alarm types, and add additional
descriptive text to individual alarm types.
This section includes:
• Displaying Alarm Information (CLI)
• Editing an Alarm Type (CLI)
• Setting Alarms to their Default Values (CLI)

Displaying Alarm Information (CLI)

To display a list of all alarm types, their severity levels, descriptions, and admin status (enabled or disabled), enter
the following command in root view:
root> platform status alarm-management show alarm-id all
To display the attributes of a specific alarm, enter the following command in root view:
root> platform status alarm-management show alarm-id <alarm-id>
attributes

Editing an Alarm Type (CLI)

To edit an alarm type’s severity level, enter the following command in root view:
root> platform status alarm-management set alarm-id <alarm-id> severity-
level <severity-level>
To add descriptive information to an alarm type, enter the following command in root view:
root> platform status alarm-management set alarm-id <alarm-id>
additional-text <additional-text>

Table 260 Editing Alarm Text and Severity CLI Parameters

Parameter Input Type Permitted Values Description

alarm-id Number All valid alarm type IDs, Enter the unique Alarm ID that identifies
depending on system the alarm type.
configuration

severity-level Variable indeterminate The severity of the alarm, as displayed

critical to users.
major
minor
warning

Phn 3963 013v000

Page 813
Chapter 22: Alarm Management and Troubleshooting (CLI) Editing Alarm Text and Severity (CLI)

Parameter Input Type Permitted Values Description

additional-text Text String 255 characters An additional text description of the

alarm type.

Example
The following command changes the severity level of alarm type 401 (Ethernet Loss of Carrier) to minor:
root> platform status alarm-management set alarm-id 401 severity-level
minor

Setting Alarms to their Default Values (CLI)

To restore an alarm type’s severity level and description to their default values, enter the following command in
root view:
root> platform status alarm-management set alarm-id <alarm-id> restore
default
To restore the severity levels and descriptions of all alarm types to their default values, enter the following
command in root view:
root> platform status alarm-management set all default

Table 261 Restoring Alarms to Default CLI Parameters

Parameter Input Type Permitted Values Description

alarm-id Number All valid alarm type IDs, Enter the unique Alarm ID that identifies
depending on system the alarm type.
configuration

Example
The following command restores alarm type 401 (Ethernet Loss of Carrier) to its default severity level:
root> platform status alarm-management set alarm-id 401 restore default

Phn 3963 013v000

Page 814
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring a Timeout for Trap Generation (CLI)

Configuring a Timeout for Trap Generation (CLI)

You can configure a wait time of up to 120 seconds after an alarm is cleared in the system before the alarm is
actually reported as being cleared. This prevents traps flooding the NMS in the event that some external condition
causes the alarm to be raised and cleared continuously.
This means that when the alarm is cleared, the alarm continues to be displayed and no clear alarm trap is sent until
the timeout period is finished.
The timeout for trap generation can be configured via CLI. By default, the timeout is 10 seconds.

Note
If the unit is upgraded from an earlier version to System Release 10.0 or higher, the timeout retains
its previous value until it is changed. That means if it was never configured, it retains its previous
default value of 0. If the unit is set to its factory default configuration, the timeout is set to 10
seconds.

To configure the timeout (in seconds) for trap generation, enter the following command in root view:
root> platform status alarm-management alarm-stabilization-set time <0-120>
To disable the timeout for trap generation, enter the following command in root view:
root> platform status alarm-management alarm-stabilization-set time 0
To display the current trap generation timeout, enter the following command in root view:
root> platform status alarm-management alarm-stabilization-show
The following command sets a trap generation timeout of 60 seconds:
root> platform status alarm-management alarm-stabilization-set time 60

Phn 3963 013v000

Page 815
Chapter 22: Alarm Management and Troubleshooting (CLI) Disabling Alarms and Events (CLI)

Disabling Alarms and Events (CLI)

You can choose to disable selected alarms and events. Any alarm or event can be disabled, so that no indication of
the alarm is displayed, and no traps are sent for the alarm.
If you disable an alarm that is currently raised, the alarm is treated as if it has been cleared. If an alarm that has
been disabled is enabled while it is in a raised state, the alarm is treated as if it has just been raised when it is
enabled.
If a timeout for trap generation is configured, and a disabled alarm is enabled while the alarm is raised, the
timeout count begins to run when the alarm is enabled. If an alarm is disabled while raised, the timeout count
begins to run upon disabling the alarm, and an alarm cleared trap is sent when the timeout expires.
To disable an alarm or event, enter the following command in root view:
root> platform status alarm-management set alarm-id <alarm ID> admin disable
To enable an alarm or event, enter the following command in root view:
root> platform status alarm-management set alarm-id <alarm ID> admin enable
To display a list of all disabled alarms and events, and their attributes, enter the following command in root view:
root> platform status alarm-management show all admin disable attributes
To display a list of all enabled alarms and events and their attributes, enter the following command in root view:
root> platform status alarm-management show all admin enable attributes
To enable all alarms and events, enter the following command in root view:
root> platform status alarm-management set all admin default
The alarm status commands platform status alarm-management show alarm-id all and platform
status alarm-management show alarm-id <alarm-id> attributes display alarms, even if they are
disabled. The Alarm Admin column in the output displays whether the alarm or event is enabled or disabled.

Phn 3963 013v000

Page 816
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Voltage Alarm Thresholds and Displaying Voltage
PMs (CLI)

Configuring Voltage Alarm Thresholds and

Displaying Voltage PMs (CLI)

You can configure undervoltage and overvoltage alarm thresholds.

The default thresholds for PTP 820C are:
• Undervoltage Raise Threshold: 32V
• Undervoltage Clear Threshold: 34V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
The default thresholds for the other PTP 820 all-outdoor products are:
• Undervoltage Raise Threshold: 36V
• Undervoltage Clear Threshold: 38V
• Overvoltage Raise Threshold: 60V
• Overvoltage Clear Threshold: 58V
These thresholds determine when the following alarms are raised and cleared:
• Alarm #32000: Under voltage
• Alarm #32001: Over voltage
To display the current thresholds, enter the following command in root view.
root> platform management voltage thresholds show
To change the threshold for raising an undervoltage alarm, enter the following command in root view:
root> platform management undervoltage set raise-threshold <0-100>
To change the threshold for clearing an undervoltage alarm, enter the following command in root view:
root> platform management undervoltage set clear-threshold <0-100>
To change the threshold for raising an overvoltage alarm, enter the following command in root view:
root> platform management overvoltage set raise-threshold <0-100>
To change the threshold for clearing an overvoltage alarm, enter the following command in root view:
root> platform management overvoltage set clear-threshold <0-100>
You can display voltage PMs that indicate, per 15-minute and 24-hour periods:
• The number of seconds the unit was in an undervoltage state during the measured
period.
• The number of seconds the unit was in an overvoltage state during the measured
period.
• The lowest voltage during the measured period.
• The highest voltage during the measured period.
To display voltage PMs, enter the following command in root view:
root> platform management voltage pm show pm-interval-type
<all|15min|24hr>

Phn 3963 013v000

Page 817
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Voltage Alarm Thresholds and Displaying Voltage
PMs (CLI)

For example:

The IDF column indicates whether the PM is valid:

• 0 indicates a valid entry.
• 1 indicates an invalid entry. This can be caused by a power surge or power failure that
occurred during the interval.

Phn 3963 013v000

Page 818
Chapter 22: Alarm Management and Troubleshooting (CLI) Uploading Unit Info (CLI)

Uploading Unit Info (CLI)

You can generate a unit information file, which includes technical data about the unit. This file can be forwarded to
customer support, at their request, to help in analyzing issues that may occur.

Note
For troubleshooting, it is important that an updated configuration file be included in Unit Info files
that are sent to customer support. To ensure that an up-to-date configuration file is included, it is
recommended to back up the unit’s configuration before generating the Unit Info file.

In order to export a unit information file, you must install an FTP or SFTP server on the laptop or PC from which
you are performing the upload. PTP 820 works with any standard FTP or SFTP server. For details, see Installing and
Configuring an FTP or SFTP Server.

Note
You can also use HTTP or HTTPS to upload the Unit Information file. HTTP or HTTPS upload must be
performed via the Web EMS. See Uploading Unit Info.

To set the FTP or SFTP parameters for unit information file export, enter one of the following commands in root
view. If the IP protocol selected in platform management ip set ip-address-family is IPv4, enter the destination IPv4
address. If the selected IP protocol is IPv6, enter the destination IPv6 address.
root> platform unit-info channel server set ip-address <server-ipv4>
directory <directory> filename <filename> username <username> password
<password>

root> platform unit-info channel server-ipv6 set ip-address <server-ipv6>

directory <directory> filename <filename> username <username> password
<password>
To set the protocol for unit information file export, enter the following command in root view.
root> platform unit-info channel set protocol <protocol>
To display the FTP or SFTP parameters for unit information file export, enter one of the following commands in
root view:
root> platform unit-info-file channel show

root> platform unit-info-file channel-ipv6 show

To create a unit information file based on the current state of the system, enter the following command in root
view:
root> platform unit-info-file create
To export the unit information file you just created, enter the following command in root view:
root> platform unit-info-file export
To display the status of a unit information file export operation, enter the following command in root view
root> platform unit-info-file status show

Phn 3963 013v000

Page 819
Chapter 22: Alarm Management and Troubleshooting (CLI) Uploading Unit Info (CLI)

Table 262 Uploading Unit Info CLI Parameters

Parameter Input Type Permitted Values Description

server-ipv4 Dotted Any valid IPv4 address. The IPv4 address of the PC or laptop you
decimal are using as the FTP or SFTP server.
format.

server-ipv6 Eight groups Any valid IPv6 address. The IPv6 address of the PC or laptop you
of four are using as the FTP or SFTP server.
hexadecimal
digits
separated by
colons.

directory Text String The directory path to which you are

exporting the unit information file. Enter
the path relative to the FTP or SFTP
user's home directory, not the absolute
path. If the location is the home
directory, it should be left empty. If the
location is a sub-folder under the home
directory, specify the folder name. If the
shared folder is "C:\", this parameter can
be left empty or populated with "//".

filename Text String The name you want to give the file you
are exporting.
Note: You must add the suffix .zip to
the file name. Otherwise, the file import
may fail. You can export the file using
any name, then add the suffix .zip
manually.

username Text String The user name for the FTP or SFTP
session.

password Text String The password for the FTP or SFTP

session. To configure the FTP or SFTP
settings without a password, simply
omit this parameter.

protocol Variable ftp The file transfer protocol.

sftp

The following commands configure an FTP or SFTP channel for configuration log export to IP address 192.168.1.99,
in the directory “current”, with file name “cfg_log”, user name “anonymous”, and password “12345.”

Phn 3963 013v000

Page 820
Chapter 22: Alarm Management and Troubleshooting (CLI) Uploading Unit Info (CLI)

root> platform security configuration-log-upload-params set path \\ file-

name cfg_log ip-address 192.168.1.99 protocol ftp username anonymous
password 12345
root> platform unit-info channel set protocol ftp
The following commands create a unit information file and export the file to the external server location:
root> platform unit-info-file create
root> platform unit-info-file export

Example
The following commands configures an FTP channel for unit information file export to IP address 192.168.1.99, in
the directory “current”, with file name “version_8_backup.zip”, user name “anonymous”, and password “12345.”
root> platform unit-info channel server set ip-address 192.168.1.99
directory \current filename version_8_backup.zip username anonymous
password 12345

root> platform unit-info channel set protocol ftp

The following commands create a unit information file and export the file to the external server location:
root> platform unit-info-file create

root> platform unit-info-file export

Phn 3963 013v000

Page 821
Chapter 22: Alarm Management and Troubleshooting (CLI) Activating the Radio Logger (CLI)

Activating the Radio Logger (CLI)

The Radio Logger, when it is activated, gathers technical data about the radio and its operation. By default, the
Radio Logger is inactive. It should only be activated by technical support personnel, or by the customer upon
request of Cambium Networks Customer Support team. Data gathered by the Radio Logger is added to the Unit
Info file, which can be exported from the unit and sent to Customer Support upon their request. See Uploading
Unit Info (CLI).

Note
In order to conserve CPU resources, do not activate the Radio Logger unless it is necessary for
unit diagnostic purposes, and do not leave it active longer than necessary.

To activate the Radio Logger, enter the following command in root view:
root> logger start logger-type radio logger-duration <1-1440> slot1 2
port1 1 slot2 2 port2 2
The logger-duration parameter is set in minutes. You can activate the logger on one or (for PTP 820C and PTP
820C-HP) two radios in a single command. For example, the following command activates the logger for 40
minutes on both carriers of an PTP 820C and PTP 820C-HP device:
root> logger start logger-type radio logger-duration 40 slot1 2 port1 1
slot2 2 port2 2
To display whether the Radio Logger is currently active, enter the following command in root view:
root> logger get status logger-type radio
For example, the following display indicates the Radio Logger has been set on both carriers for 20 minutes, and
that the Logger is set to run for an additional 1191 seconds:
root> logger get status logger-type radio
Logger status:
Logger duration(in minutes): 20
Logger time left(in seconds): 1191
Active instances list:
Slot 2 Port 1
Slot 2 Port 2
root>
To stop the Radio Logger manually, enter the following command in root view:
root> logger stop logger-type radio
To delete all data that has been saved by the Radio Logger, enter the following command in root view:
root> logger delete logger files<logger-type>.
Important Note: Whenever you activate the Radio Logger, any previous Radio
Logger results are deleted.

Phn 3963 013v000

Page 822
Chapter 22: Alarm Management and Troubleshooting (CLI) Performing Diagnostics (CLI)

Performing Diagnostics (CLI)

This section includes:

• Performing Radio Loopback (CLI)
• Performing Ethernet Loopback (CLI)
• Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Performing Radio Loopback (CLI)

Note
To perform radio loopback, the radio must be set to its maximum TX power.

You can perform loopback on a radio.

To set the timeout for a radio loopback, enter the following command:
radio[x/x]> radio loopbacks-timeout set duration <duration>
To display the radio loopback timeout, enter the following command:
radio[x/x]>radio loopbacks-timeout show
To activate an RF loopback, enter the following command:
radio[x/x]>rf loopback-rf set admin <admin>

Table 263 Radio Loopback CLI Parameters

Parameter Input Type Permitted Values Description

duration Number 0 – 1440 The timeout, in minutes, for automatic

termination of a loopback. A value of 0
indicates that there is no timeout.

admin Variable on Set on to initiate an RF loopback.

off

Examples
The following commands initiate an RF loopback on radio carrier 1 with a timeout of two minutes:
radio[2/1]> radio loopbacks-timeout set duration 2

radio[2/1]>rf loopback-rf set admin on

Phn 3963 013v000

Page 823
Chapter 22: Alarm Management and Troubleshooting (CLI) Performing Diagnostics (CLI)

Performing Ethernet Loopback (CLI)

Ethernet loopbacks can be performed on any logical Ethernet interface except a LAG. When Ethernet loopback is
enabled on an interface, the system loops back all packets ingressing the interface. This enables loopbacks to be
performed over the link from other points in the network.
To configure loopback on an Ethernet interface, go to interface view for the interface and enter the following
command:
eth type eth[x/x]> loopback admin <loopback-admin-state>
To configure the loopback duration time, go to interface view for the interface and enter the following command:
eth type eth[x/x]> loopback set duration <loopback-duration>
You can select whether to swap DA and SA MAC addresses during the loopback. Swapping addresses prevents
Ethernet loops from occurring. It is recommended to enable MAC address swapping if LLDP is enabled.
To configure MAC address swapping, go to interface view for the interface and enter the following command:
eth type eth[x/x]> loopback swap-mac-address admin <MAC_swap-admin-state>
To view loopback status, go to interface view for the interface and enter the following command:
eth type eth[x/x]> loopback status show

Table 264 Ethernet Loopback CLI Parameters

Parameter Input Type Permitted Values Description

loopback- Variable enable Enter enable to enable Ethernet

admin-state disable loopback on the interface, or disable to
disable Ethernet loopback on the
interface.

loopback- Number 1 - 900 The loopback duration time, in seconds.

duration

MAC_swap- Variable enable Enter enable to enable MAC address

admin-state disable swapping, or disable to disable MAC
address swapping.

Examples
The following command enables Ethernet loopback on Ethernet interface 2.
eth type eth [1/2]> loopback admin enable
The following command sets the loopback duration time to 900 seconds.
eth type eth [1/2]> loopback set duration 900
The following command enables MAC address swapping during the loopback.
eth type eth [1/2]> loopback swap-mac-address admin enable
The following command displays Ethernet port loopback status.
eth type eth [1/2]> loopback status show

Phn 3963 013v000

Page 824
Chapter 22: Alarm Management and Troubleshooting (CLI) Performing Diagnostics (CLI)

Phn 3963 013v000

Page 825
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Configuring Service OAM (SOAM) Fault

Management (FM) (CLI)

This section includes:

• SOAM Overview (CLI)
• Configuring MDs (CLI)
• Configuring MA/MEGs (CLI)
• Configuring MEPs (CLI)
• Displaying MEP and Remote MEP Attributes (CLI)
• Displaying Detailed MEP Error Information (CLI)
• Performing Loopback (CLI)

SOAM Overview (CLI)

The Y.1731 standard and the MEF-30 specifications define Service OAM (SOAM). SOAM is concerned with
detecting, isolating, and reporting connectivity faults spanning networks comprising multiple LANs, including LANs
other than IEEE 802.3 media.
Y.1731 Ethernet FM (Fault Management) consists of three protocols that operate together to aid in fault
management:
• Continuity check
• Link trace
• Loopback

Note
Link trace is planned for future release.

PTP 820 utilizes these protocols to maintain smooth system operation and non-stop data flow.
The following are the basic building blocks of FM:
• MD (Maintenance Domain) – An MD defines the management space on a network, typically owned and
operated by a single entity, for which connectivity faults are managed via SOAM.
• MA/MEG (Maintenance Association/Maintenance Entity Group) – An MA/MEG contains a set of MEPs or
MIPs.
• MEP (MEG End Points) – Each MEP is located on a service point of an Ethernet service at the boundary of the
MEG. By exchanging CCMs (Continuity Check Messages), local and remote MEPs have the ability to detect the
network status, discover the MAC address of the remote unit/port where the peer MEP is defined, and
identify network failures.
• MIP –(MEG Intermediate Points) – Similar to MEPs, but located inside the MEG and can only respond to, not
initiate, CCM messages.

Phn 3963 013v000

Page 826
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

• CCM (Continuity Check Message) – MEPs in the network exchange CCMs with their peers at defined intervals.
This enables each MEP to detect loss of connectivity or failure in the remote MEP.

Configuring MDs (CLI)

In the current release, you can define one MD, with an MD Format of None.
To add an MD, enter the following command in root view:
root> ethernet soam md create md-id <md-id> md-format none md-name <md-
name> md-level <md-level>

Note
Support for MDs with the MD format Character String is planned for future release. In this release,
the software enables you to configure such MDs, but they have no functionality.

The following command creates MD 5, named TR-988 with maintenance level 5.

root> ethernet soam md create md-id 5 md-format none md-name TR-988 md-
level 5
To delete an MD, enter the following command in root view. Before deleting an MD, you must delete any MA/MEG
associated with the MD.
root> ethernet soam md delete md-id <md-id>
To display a list of MDs and their attributes, enter the following command in root view:
root> ethernet soam md show

Table 265 Maintenance Domain CLI Parameters

Parameter Input Type Permitted Values Description

md-id Number 1-4294967295

md-name String Up to 43 alphanumeric An identifier for the MD. The MD Name should be
characters. unique over the domain.

md-level Number 0-7 The maintenance level of the MD. The

maintenance level ensures that the CFM frames for
each domain do not interfere with each other.
Where domains are nested, the encompassing
domain must have a higher level than the domain
it encloses. The maintenance level is carried in all
CFM frames that relate to that domain. The
maintenance level must be the same on both sides
of the link.
Note: In the current release, the maintenance
level is not relevant to the SOAM functionality.

Phn 3963 013v000

Page 827
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Configuring MA/MEGs (CLI)

You can configure up to 1280 MEGs per network element. MEGs are classified as Fast MEGs or Slow MEGs
according to the CCM interval (see Table 231):
• Fast MEGs have a CCM interval of 1 second.
• Slow MEGs have a CCM interval of 10 seconds, 1 minute, or 10 minutes.
You can configure up to 64 MEP pairs per network element.
To add an MA/MEG, enter the following command in root view:
root> ethernet soam meg create meg-id <meg-id> meg-fmt charString meg-
name <meg-name> meg-level <meg-level> service-id <0-4095>

Note
In the current release, charString is the only available MEG name format.

The following command creates MEG ID 1, named FR-10, with MEG level 4, assigned to Ethernet service 20.
root> ethernet soam meg create meg-id 1 meg-fmt charString meg-name FR-10
meg-level 4 service-id 20
To set the interval at which CCM messages are sent within the MEG, enter the following command in root view:
root> ethernet soam meg ccm-interval set meg-id <meg-id> ccm <ccm>
The following command sets an interval of one second between CCM messages for MEG 1.
root> ethernet soam meg ccm-interval set meg-id 1 ccm interval1s
To determine whether MIPs are created on the MEG, enter the following command in root view:
root> ethernet soam meg mip set meg-id <meg-id> mhf <1-
4|defMHFnone|defMHFdefault|defMHFexplicit|defMHFdefer>
The following command creates MIPs on any service point in the MEG:
root> ethernet soam meg mip set meg-id 1 mhf defMHFdefault
To delete a MEG, enter the following command in root view:
root> ethernet soam meg delete <meg-id> ccm <ccm>

Note
To can only delete a MEG if no MEPs or MIPs are attached to the MEP.

To display a list of all MEGs configured on the unit, enter the following command in root view:
root> ethernet soam meg show
To display MEG attributes, including the number of MEPS, local MEPS, and MIPs attached to the MEG, enter the
following command in root view:
root> ethernet soam meg attributes show meg-id <meg-id>

Table 266 SOAM MEG CLI Configuration Parameters

Phn 3963 013v000

Page 828
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Input Type Permitted Values Description

meg-id Number 1-4294967295 Enter an ID for the MEG.

meg-name String Up to 44 alphanumeric A name to identify the MEG.

characters

meg-level Number 0-7 The MEG level must be the same for MEGs on both
sides of the link. Higher levels take priority over
lower levels.
If MEGs are nested, the OAM flow of each MEG must
be clearly identifiable and separable from the OAM
flows of the other MEGs. In cases where the OAM
flows are not distinguishable by the Ethernet layer
encapsulation itself, the MEG level in the OAM
frame distinguishes between the OAM flows of
nested MEGs.
Eight MEG levels are available to accommodate
different network deployment scenarios. When
customer, provider, and operator data path flows
are not distinguishable based on means of the
Ethernet layer encapsulations, the eight MEG levels
can be shared among them to distinguish between
OAM frames belonging to nested MEGs of
customers, providers and operators. The default
MEG level assignment among customer, provider,
and operator roles is:
The customer role is assigned MEG levels 6 and 7
The provider role is assigned MEG levels 3 through 5
The operator role is assigned MEG levels: 0 through
2
The default MEG level assignment can be changed
via a mutual agreement among customer, provider,
and/or operator roles.
The number of MEG levels used depends on the
number of nested MEs for which the OAM flows are
not distinguishable based on the Ethernet layer
encapsulation.

service-id Number 0-4095 Assign the MEG to an Ethernet service. You must
define the service before you configure the MEG.

Phn 3963 013v000

Page 829
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Input Type Permitted Values Description

ccm Variable interval1s interval1s – One second (default)

interval10s interval10s – 10 seconds
interval1min interval1min – One minute
interval10min interval10min – 10 minutes
It takes a MEP 3.5 times the CCM interval to
determine a change in the status of its peer MEP. For
example, if the CCM interval is 1 second, a MEP will
detect failure of the peer 3.5 seconds after it
receives the first CCM failure message. If the CCM
interval is 10 minutes, the MEP will detect failure of
the peer 35 minutes after it receives the first CCM
failure message.

mhf Variable defMHFnone Determines whether MIPs are created on the MEG.
defMHFdefault Options are:
defMHFexplicit defMHFnone – No MIPs are created.
defMHFdefer defMHFdefault – MIPs are created on any service
point in the MEG.
defMHFexplicit – MIPs are created on the service
points of the MEG when a lower-level MEP exists on
the service point. This option is usually used when
the operator’s domain is encompassed by another
domain.
defMHFdefer – No MIPs are created.

Configuring MEPs (CLI)

Each MEP is attached to a service point in an Ethernet service. The service and service point must be configured
before you configure the MEP. See Configuring Ethernet Services (CLI).
Each MEP inherits the same VLAN, C-VLAN, or S-VLAN configuration as the service point on which it resides. See
Configuring Service Points (CLI).
In order to set the VLAN used by CCM/LBM/LTM if the service point is defined ambiguously (for example PIPE,
Bundle-C, Bundle-S, or All-to-One), the service point’s C-VLAN/S-VLAN parameter should not be set to N.A.
To configure a MEP, you must:
1 Add MEPs to the relevant MA/MEG. In this stage, you add both local and remote MEPs. The only thing you
define at this point is the MEP ID. See Adding Local and Remote MEPs (CLI).
2 Configure the local MEPs. At this point, you determine which MEPs are local MEPs. The system
automatically defines the other MEPs you configured in the previous step as remote MEPs. See
Configuring the Local MEPs (CLI).
3 Enable the Local MEPs. See Enabling Local MEPs (CLI).

Phn 3963 013v000

Page 830
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Adding Local and Remote MEPs (CLI)

To add a MEP, enter the following command in root view:
root> ethernet soam meg mep add meg-id <meg-id> mep-id <mep-id>
The following command adds MEP 25 on MEG 2.
root> ethernet soam meg mep add meg-id 2 mep-id 25
To remove a MEP, enter the following command in root view:
root> ethernet soam meg mep remove meg-id <meg-id> mep-id <mep-id>
The following command removes MEP 25 from MEG 2.
root> ethernet soam meg mep remove meg-id 2 mep-id 25
To display a list of all MEPs that belong to a specific MEG, enter the following command in root view:
root> ethernet soam meg mep show meg-id <meg-id>

Configuring the Local MEPs (CLI)

Once you have added local and remote MEPs, you must configure the MEPs and determine which are the local
MEPs.
To make a defined MEP a local MEP, you must assign the MEP to a service point on the Ethernet service on which
the MEG resides.
To assign a MEP to a service point, enter the following command in root view:
root> ethernet soam mep create meg-id <meg-id> mep-id <mep-id> sp-id <sp-
id> mep-dir <mep-dir>
The following command assigns MEP 35 on MEG 2 to Service Point 3 on the service on which MEG 2 resides.
root> ethernet soam mep create meg-id 2 mep-id 35 sp-id 3 mep-dir down
To change a MEP from a local to a remote MEP, enter the following command in root view:
root> ethernet soam mep delete meg-id <meg-id> mep-id <mep-id>
The following command changes MEP 35 from a local to a remote MEP.
root> ethernet soam mep delete meg-id 2 mep-id 35
To display a list of local MEPs for a specific MEG, enter the following command in root view:
root> ethernet soam meg local-mep show meg-id <meg-id>
For example:

Phn 3963 013v000

Page 831
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Enabling Local MEPs (CLI)

Once you have added a MEP and defined it as a local MEP, you must enable the MEP by setting the MEP to Active,
enabling CCM messages from the MEP, and assigning a CCM-LTM priority to the MEP.
To set a MEP to Active, enter the following command in root view:
root> ethernet soam mep active set meg-id <meg-id> mep-id <mep-id> mep-
active <mep-active>
The following command sets MEP 35 on MEG 2 to Active.
root> ethernet soam mep active set meg-id 2 mep-id 35 mep-active true
To enable or disable the sending of CCM messages on a MEP, enter the following command in root view:
root> ethernet soam mep ccm-enable set meg-id <meg-id> mep-id <mep-id>
enabled <ccm-enabled>
The following command assigns enables CCM messages for MEP 35 on MEG 2.
root> ethernet soam mep ccm-enable set meg-id 2 mep-id 35 enabled true
To set a MEP’s CCM-LTM priority, enter the following command in root view:
root> ethernet soam mep ccm-ltm-prio set meg-id <meg-id> mep-id <mep-id>
ccm-ltm-priority <ccm-ltm-priority>
The following command sets the CCM-LTM priority of MEP 35 in MEG 2 to 5.
root> ethernet soam mep ccm-ltm-prio set meg-id 2 mep-id 35 ccm-ltm-
priority 5

Table 267 MEP CLI Configuration Parameters

Parameter Input Type Permitted Values Description

meg-id Number 1-4294967295 Enter an ID for the MEG.

mep-id Number 1-8191 A name to identify the MEG.

sp-id Number 0-32 The Service Point ID of the service point to which
you want to assign the MEP.

mep-dir Variable up The MEP direction.

down

Phn 3963 013v000

Page 832
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Input Type Permitted Values Description

ccm-enabled Variable true true – CCM messages are enabled on the MEP.
false false – CCM messages are disabled on the MEP.

ccm-ltm- Number 0-7 The p-bit included in CCMs sent by this MEP.
priority

mep-active Variable true true – The MEP is Active.

false false – The MEP is Inactive.

Displaying MEP and Remote MEP Attributes (CLI)

To display the attributes of a specific MEP, enter the following command in root view:
root> ethernet soam mep configuration general show meg-id <meg-id <meg-
id> mep-id <mep-id>
For example:

To display a list of remote MEPs (RMEPs) and their parameters per MEG and local MEP, enter the following
command in root view:
root> ethernet soam mep rmep list show meg-id <meg-id <meg-id> mep-id
<mep-id>
For example:

Phn 3963 013v000

Page 833
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

To display a list of remote MEPs (RMEPs) and their parameters per MEG and local MEP, enter the following
command in root view:
root> ethernet soam mep rmep show meg-id meg-id < meg-id <meg-id> mep-id
<mep-id> rmep-id <rmep-id>
For example:

Table 268 MEP and Remote MEP Status Parameters (CLI)

Parameter Description

MD Parameters

MD ID The MD ID.

MD Name The MD name (44 characters).

MD Format The MD format (None).

Phn 3963 013v000

Page 834
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Description

MD Level The maintenance level of the MD (0-7).

MEG Parameters

MA ID The MA/MEG ID.

Format charString in the current release.

Name The MA/MEG name (43 characters).

Level The MEG Level (0-7).

Service The Service ID of the Ethernet service to which the MEG belongs.

CCM Interval The interval at which CCM messages are sent within the MEG.

Number of MEPs The number of MEPs that belong to the MEG.

Number of Local MEPs The number of local MEPs that belong to the MEG.

Number of MIPs The number of MIPs that belong to the MEG.

SOAM MEP Table

Parameters

MEP ID The MEP ID.

Interface Location The interface on which the service point associated with the MEP is located.

MEP Direction Up or Down.

MEP Active Indicates whether the MEP is enabled (true) or disabled (false).

MEP CCM TX Enable Indicates whether the MEP is configured to send CCMs (true or false).

CCM and LTM Priority The p-bit included in CCMs sent by the MEP (0-7).

MEP MAC Address The MAC address of the service point associated with the MEP.

MEP Lowest priority fault The lowest defect priority that can trigger alarm generation. Defects with a
alarm lower priority will not trigger alarms.

MEP Alarm on time The amount of time that defects must be present before an alarm is
generated, in msec intervals (250-1000).

MEP Alarm Clear Time The amount of time that defects must be absent before an alarm is cleared,
msec intervals (250-1000).

Sequence errors CCM The number of out-of-sequence CCM messages received.

Frames

CCM Messages TX The number of transmitted CCM messages.

RMEP Parameters

MepId The MEP ID of the local MEP paired with the remote MEP.

Rmep Id The remote MEP ID.

Phn 3963 013v000

Page 835
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Description

operState The operational state of the remote MEP.

OKorFail Time The timestamp marked by the remote MEP indicating the most recent CCM OK
or failure it recorded. If none, this field indicates the amount of time, in msec
intervals, since SOAM was activated.

MAC The MAC Address of the interface on which the remote MEP is located.

Rdi Displays the state of the RDI (Remote Defect Indicator) bit in the most recent
CCM received by the remote MEP:
• True – RDI was received in the last CCM.
• False – No RDI was received in the last CCM.

Port Status The Port Status TLV in the most recent CCM received from the remote MEP.
Reserved for future use.

Interface Status The Interface Status TLV in the most recent CCM received from the remote
MEP. Indicates the operational status of the interface (Up or Down).

Chassis ID Format Displays the address format of the remote chassis (in the current release, MAC
Address).

Chassis ID Displays the MAC Address of the remote chassis.

Mng Addr Domain Displays the BASE MAC address of the remote unit (the unit on which the
remote MEP resides).,

Displaying Detailed MEP Error Information (CLI)

To display the entire frame of the last CCM error message and the last CCM cross-connect error message received
by a specific local MEP, along with other detailed information, enter the following command in root view:
root> ethernet soam mep status general show meg-id <meg-id> mep-id <mep-
id> detailed yes
For example:

Phn 3963 013v000

Page 836
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

To display the same information without the last RX error CCM and fault messages, enter the following command
in root view:
root> ethernet soam mep status general show meg-id <meg-id> mep-id <mep-
id> detailed no
The Last RX error CCM message field displays the frame of the last CCM that contains an error received by the
MEP.
The Last RX Xcon fault message field displays the frame of the last CCM that contains a cross-connect error
received by the MEP.

Note
A cross-connect error occurs when a CCM is received from a remote MEP that has not been defined
locally.

Performing Loopback (CLI)

To set the interval between loopback message transmissions in a loopback session, enter the following command
in root view:
root> ethernet soam loopback interval set meg-id <meg-id> mep-id <mep-id>
interval <0-60000>
For example, the following command sets the loopback interval for MEP 25 on MEG 1 to 5 seconds:
root> ethernet soam loopback interval set meg-id 1 mep-id 25 interval
5000
To set the loopback message frame size and data pattern, enter the following command in root view:

Phn 3963 013v000

Page 837
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

root> ethernet soam loopback data set meg-id <meg-id> mep-id <mep-id>
size <size> pattern <pattern>
For example, the following command sets the loopback frame size to 128 and the pattern to zero for MEP 25 on
MEG 1 to 5 seconds:
root> ethernet soam loopback data set meg-id 1 mep-id 25 size 128 pattern
zeroPattern
To set the loopback priority bit size and drop-enable parameters, enter the following command in root view:
root> ethernet soam loopback prio set meg-id <meg-id> mep-id <mep-id>
prio <priority> drop <drop>
For example, the following command sets a priority bit size of 5 and enables frame dropping for MEP 25 on MEG 1
to 5 seconds:
root> ethernet soam loopback prio set meg-id 1 mep-id 25 prio 5 drop true
To set the loopback destination by MAC address, set the number of loopback messages to transmit and the
interval between messages, and initiate the loopback, enter the following command in root view:
root> ethernet soam loopback send meg-id <meg-id> mep-id <mep-id> dest-
mac-addr <dest-mac-addr> tx-num <tx-num> tx-interval <interval>
For example, the following command initiates a loopback session with the interface having MAC address
00:0A:25:38:09:4B. The session is configured to send 100 loopback messages at six-second intervals.
root> ethernet soam loopback send meg-id 1 mep-id 25 dest-mac-addr
00:0A:25:38:09:4B tx-num 100 tx-interval 6000
To set the loopback destination by MEP ID, set the number of loopback messages to transmit and the interval
between messages, and initiate the loopback, enter the following command in root view:
root> ethernet soam loopback send meg-id <meg-id> mep-id <mep-id> dest-
mep-id <dest-mac-addr> tx-num <tx-num> tx-interval <interval>
For example, the following command initiates a loopback session with the interface having MAC address
00:0A:25:38:09:4B. The session is configured to send 100 loopback messages at six-second intervals.
root> ethernet soam loopback send meg-id 1 mep-id 25 dest-mac-addr
00:0A:25:38:09:4B tx-num 100 tx-interval 6000

Note
If you initiate the loopback via MEP ID, the loopback will only be activated if CCMs have already been
received from the MEP. For this reason, it is recommended to initiate loopback via MAC address.

To display the loopback attributes of a MEP, enter the following command in root view:
root> ethernet soam loopback config show meg-id <meg-id> mep-id <mep-id>
For example:

Phn 3963 013v000

Page 838
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

To stop a loopback that is already in progress, enter the following command in root view:
root> ethernet soam loopback stop meg-id <meg-id> mep-id <mep-id>

Table 269 Loopback CLI Parameters

Parameter Input Type Permitted Values Description

meg-id Number 1-4294967295 The MEG ID of the MEG on which the loopback is
being configured or run.

mep-id Number 1-8191 The MEP ID of the MEP on which the loopback is
being configured or run.

interval Number 0-60000 The interval (in ms) between each loopback
message. Note that the granularity for this
parameter is 100 ms. If you enter a number that is
not in multiples of 100, the value will be rounded off
to the next higher multiple of 100. Also, the lowest
interval is 1000 ms (1 second). If you enter a smaller
value, it will be rounded up to 1000 ms.

size Number 64-1518 The frame size for the loopback messages. Note that
for tagged frames, the frame size will be slightly
larger than the selected frame size.

pattern Variable zeroPattern The type of data pattern to be sent in an OAM PDU
onesPattern Data TLV.

priority Number 0-7 The priority bit for tagged frames.

drop Boolean true true – Frame dropping is enabled.

false false – Frame dropping is disabled.

dest-mac-addr Six groups of The MAC address of the interface to which you want
two to send the loopback. If you are not sure what the
hexadecimal interface’s MAC address is, you can get it from the
digits Interface Manager by entering the platform if-
manager show interfaces command in root
view.

dest-mep-id Number 1-8191 The MEP ID of the interface to which you want to
send the loopback.

Phn 3963 013v000

Page 839
Chapter 22: Alarm Management and Troubleshooting (CLI) Configuring Service OAM (SOAM) Fault Management (FM) (CLI)

Parameter Input Type Permitted Values Description

tx-num Number 0-1024 The number of loopback messages to transmit. If

you enter 0, loopback will not be performed.

To display loopback results, enter the following command in root

view:root> ethernet soam loopback status show meg-id <meg-id> mep-id
<mep-id>
The following is a sample output for this command on MEG ID 127, MEP ID 1.

Phn 3963 013v000

Page 840
Chapter 22: Alarm Management and Troubleshooting (CLI) Working in CW Mode (Single or Dual Tone) (CLI)

Working in CW Mode (Single or Dual Tone) (CLI)

CW mode enables you to transmit a single or dual frequency tones, for debugging purposes.
To work in CW mode, enter the following command:
radio[x/x] modem tx-source set admin enable
Once you are in CW mode, you can choose to transmit in a single tone or two tones.
To transmit in a single tone, enter the following command in radio view:
radio[x/x] modem tx-source set mode one-tone freq-shift <freq-shift>
To transmit two tones, enter the following command in radio view:
radio[x/x] modem tx-source set mode two-tone freq-shift <freq-shift>
freq-shift2 <freq-shift>
To exit CW mode, enter the following command:
radio[x/x] modem tx-source set admin disable

Table 270 CW Mode CLI Parameters

Parameter Input Type Permitted Values Description

freq-shift Number 0-7000 Enter the frequency you want to

transmit, in KHz.

The following commands set a single-tone transmit frequency of 5050 KHz on radio interface 1, then exit CW mode
and return the interface to normal operation:
root> radio slot 2 port 1
radio[2/1] modem tx-source set admin enable
radio[2/1] radio[x/x] modem tx-source set mode one-tone freq-shift 5050
radio[2/1] modem tx-source set admin disable

Phn 3963 013v000

Page 841
Chapter 23: Maintenance Working in CW Mode (Single or Dual Tone) (CLI)

Chapter 23: Maintenance

This section includes:
• Temperature Ranges
• Troubleshooting Tips
• PTP 820C Connector Pin-outs
• PTP 820C LEDs
• PTP 820S Connector Pin-outs
• PTP 820S LEDs
• PTP 820 C-HP Connector Pin-outs
• PTP 820C-HP LEDs
• PTP 820E Connector Pin-outs
• PTP 820E LEDs
• PoE Injector Pin-outs

Phn 3963 013v000

Page 842
Chapter 23: Maintenance Temperature Ranges

Temperature Ranges

The following are the permissible unit temperature ranges for PTP 820C, PTP 820C-HP and PTP 820S.
• -33C to 55 – Temperature range for continuous operating temperature with high reliability.
• -45C to 60C – Temperature range for exceptional temperatures, tested successfully, with limited margins.
For PTP 820C, PTP 820S, and PTP 820E, an extreme temperature alarm (25) is raised if the unit’s internal
temperature goes above 100°C or below -40°C. The alarm is cleared when the temperature goes below 95°C or
above -35°C.
For PTP 820C-HP, an extreme temperature alarm (25) is raised if the unit’s internal temperature goes above 92°C
or below -40°C. The alarm is cleared when the temperature goes below 87°C or above -35°C.
To display the current unit temperature, see Configuring Unit Parameters.
• The permissible IDU humidity range is 5%RH to 100%RH

Troubleshooting Tips

Platform
If during or right after a software upgrade the message Your session has expired, please login
again appears and you cannot log in, it is recommended to refresh the Web EMS page (F5)
after completion of the upgrade. If pressing F5 does not help, clear the browser’s cache by
pressing Ctrl+Shift+Delete.

XPIC

• For dual-polarization and XPIC links, if one of the polarizations has significantly reduced performance, check to
make sure the antenna’s rectangular interface was replaced with a circular adaptor.
• For dual-polarization and XPIC links, the RSL should be similar for both polarizations. For XPIC links, the XPI
value should be similar for both polarizations; the difference should not be more than 2 dB.

Unit Protection
• When switchover takes place, a series of GARP packets are sent identifying the MAC address of the new
management interface. This enables the management device to immediately re-establish the management
connection. By default, three GARP packets are sent:
o The first GARP packet is sent immediately upon switchover.
o The second GARP packet is sent 500 ms after switchover.
o The third GARP packet is sent one second after switchover.

Phn 3963 013v000

Page 843
Chapter 23: Maintenance Temperature Ranges

The number of GARP packets is user-configurable. If you experience a delay in re-

establishing management, you can increase the number of GARP packets that are sent
upon switchover. The number of packets can be changed to any value from 0 (disabling the
feature) to 10. Packets are sent at intervals of
500 ms.
Use the following CLI command to change the number of GARP packets to be sent upon
switchover:

root>platform management protection debug set garp <0-10>

Use the following CLI command to show the current configuration of this parameter:
root>platform management protection debug show garp

Phn 3963 013v000

Page 844
Chapter 23: Maintenance PTP 820C Connector Pin-outs

PTP 820C Connector Pin-outs

Figure 465 PTP 820C Interfaces

Eth1/PoE - GbE Electrical+PoE/Optical

Table 271: PTP 820C Eth1/PoE Interface- RJ-45/SFP Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 845
Chapter 23: Maintenance PTP 820C Connector Pin-outs

Eth2 - GbE Electrical/Optical

Table 272 PTP 820C Eth2 Interface - RJ-45/SFP Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

MIMO Port
Table 273 PTP 820C MIMO Port - RJ-45/SFP pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 846
Chapter 23: Maintenance Troubleshooting Tips

Troubleshooting Tips

• For dual-polarization and XPIC links, if one of the polarizations has significantly reduced performance,
check to make sure the antenna’s rectangular interface was replaced with a circular adaptor.
• For dual-polarization and XPIC links, the RSL should be similar for both polarizations. For XPIC links, the XPI
value should be similar for both polarizations; the difference should not be more than 2 dB.
If during or right after a software upgrade the message Your session has expired, please login again appears and
you cannot log in, it is recommended to refresh the Web EMS page (F5) after completion of the upgrade. If
pressing F5 does not help, clear the browser’s cache by pressing Ctrl+Shift+Delete.MGT/PROT - Management (FE-
Standard) and Protection (FE-Non-Standard)

Table 274 PTP 820C MGT/PROT Interface - RJ-45 Pinouts

Pin no. Description

Protection - Non-Standard 100Base-T 4 Wire

1 TX+

2 TX-

3 RX+

6 RX-

Protection - Non-Standard 100Base-T 4 Wire

4 TX+

5 TX-

7 RX+

8 RX-

DC
The DC port is UL-60950 compliant, with a 2-pin connector.

Phn 3963 013v000

Page 847
Chapter 23: Maintenance Troubleshooting Tips

Figure 466 PTP 820C DC Port Connector

RSL Interface
PTP 820C uses a weather-proof BNC connector.

Note
The voltage at the RSL interface is 1.XX where XX is the RSL level. For example; 1.59V means an RSL
of -59 dBm. Note that the voltage measured at the RSL interface is not accurate and should be used
only as an aid).

Source Sharing
PTP 820C uses a TNC connector for source sharing. This connector is marked EXT/REF.

Phn 3963 013v000

Page 848
Chapter 23: Maintenance PTP 820C LEDs

PTP 820C LEDs

The PTP 820C provides the following LEDs to indicate the status of the unit's interfaces, and the unit as a whole:
• Electrical GbE Interface (RJ-45) LEDs
• Optical GbE Interface (SFP) LEDs
• Management FE Interface (RJ-45) LEDs
• Radio LED
• Status LED
• Protection LED

Electrical GbE Interface (RJ-45) LEDs

There are two LEDs next to each electrical (RJ-45) interface, a Green LED to the left of the interface and an Orange
LED to the right of the interface.
The Green LED indicates the port’s Admin state:
• Off - Admin is Disabled.
• Green – Admin is Enabled.
The Orange LED indicates the interface's Admin and cable connection status, and whether there is traffic on the
interface:
• Off- Admin is Disabled or no cable is connected to the interface.
• Orange – Admin is Enabled and a cable is connected to the interface.
• Blinking Orange – Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

Optical GbE Interface (SFP) LEDs

There is one Green LED next to each optical (SFP) GbE interface. The LED indicates the interface's Admin and cable
connection status, and whether there is traffic on the interface:
• Off - Admin is Disabled or no cable is connected to the interface..
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

Management FE Interface (RJ-45) LEDs

There are two LEDs next to the MGT (management) interface, a Green LED to the left of the interface and an
Orange LED to the right of the interface.
The Green LED indicates the port’s Admin state :
• Off - Admin is Disabled .

Phn 3963 013v000

Page 849
Chapter 23: Maintenance PTP 820C LEDs

• Green - Admin is Enabled .

• Blinking Green – Management traffic is passing through the interface.
If the MGT interface is being used for protection, the Orange LED indicates the status of the mate unit.:
• Off – The interface is not in an operational state (down).
• Orange – The interface is operational (up).
• Blinking Orange –Management traffic is passing through the interface.Radio LED
The Link LED is a three-color LED that indicates the status of the radio link:
• Off – The radio is off.
• Green - The power is on, and all carriers are operational (up).
• Orange - A signal degrade condition exists in at least one carrier.
• Red - A loss of frame (LOF) or excessive BER condition exists in at least one carrier.

Status LED
The Status LED indicates the status of the rmain board:
• Off – The power is off.
• Green - The power is on, and no alarms are raised on the motherboard.
• Red - The power is on, and one or more major or critical alarms are raised on the motherboard.
• Orange – The power is on, and one or more minor alarms or warnings are raised on the motherboard.

Protection LED
The Protection LED operates in a protected configuration to indicate the protection status:
• Orange - Protection is enabled, and the unit is in standby mode.
• Green - Protection is disabled or protection is enabled, and the unit is in active mode.
• Red – A protection alarm exists (cable disconnected, mismatch configuration, or mate communication not
working). Note that only the active unit will have a red LED.
• Off – Protection is not enabled

Phn 3963 013v000

Page 850
Chapter 23: Maintenance PTP 820C-HP Connector Pin-outs

PTP 820C-HP Connector Pin-outs

Figure 467: PTP 820C-HP Interfaces

Data Port 1 - GbE Electrical (RJ-45)

Table 275:PTP 820C-HP Data Port 1 – Pinouts
Pin Description
no.
1 BI_DA+ (Bi-directional pair +A)
2 BI_DA- (Bi-directional pair -A)
3 BI_DB+ (Bi-directional pair +B)
4 BI_DC+ (Bi-directional pair +C)
5 BI_DC- (Bi-directional pair -C)
6 BI_DB- (Bi-directional pair -B)
7 BI_DD+ (Bi-directional pair +D)
8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 851
Chapter 23: Maintenance PTP 820C-HP Connector Pin-outs

Management Port (FE-Standard) and Protection (FE-Non-

Standard)
276: PTP 820C-HP Management Interface - RJ-45 Pinouts
Pin no. Description
Management - Standard 100Base-T 4 Wire
1 TX+
2 TX-
3 RX+
6 RX-
Protection - Non-Standard 100Base-T 4 Wire
4 TX+
5 TX-
7 RX+
8 RX-

DC
The DC port is UL-60950 compliant, with a 2-pin connector.

Figure 468: PTP 820C-HP DC Port Connector

RSL Interface
PTP 820C-HP uses a dual-pin connector.

Phn 3963 013v000

Page 852
Chapter 23: Maintenance PTP 820C-HP Connector Pin-outs

Note
The voltage at the RSL interface is 1.XX where XX is the RSL level. For example; 1.59V means an RSL
of -59 dBm. Note that the voltage measured at the RSL interface is not accurate and should be used
only as an aid).

Source Sharing
PTP 820C-HP uses a TNC connector for source sharing. This connector is marked EXT/REF.

Phn 3963 013v000

Page 853
Chapter 23: Maintenance PTP 820C-HP LEDs

PTP 820C-HP LEDs

The PTP 820C-HP provides the following LEDs to indicate the status of the unit's interfaces, and the unit as a
whole:
• Electrical GbE Interface (RJ-45) LEDs
• Optical GbE Interface (SFP) LEDs
• Management FE Interface (RJ-45) LEDs
• Radio LED
• Status LED
• Protection LED

Electrical GbE Interface (RJ-45) LEDs

There are two LEDs next to each electrical (RJ-45) interface, a Green LED to the left of the interface and an Orange
LED to the right of the interface.
The Green LED indicates the port’s Admin state:
• Off – Admin is Disabled.
• Green – Admin is Enabled.
The Orange LED indicates the interface's Admin and cable connection status, and whether there is traffic on the
interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Orange - Admin is Enabled and a cable is connected to the interface.
• Blinking Orange - Admin is Enabled and a cable is connected to the interface, and
there is traffic on the interface.

Optical GbE Interface (SFP) LEDs

There is one Green LED next to each optical (SFP) GbE interface. The LED indicates the interface's Admin and cable
connection status, and whether there is traffic on the interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and
there is traffic on the interface.

Management FE Interface (RJ-45) LEDs

There are two LEDs next to the MGT (management) interface, a Green LED to the left of the interface and an
Orange LED to the right of the interface.
The Green LED indicates the port’s Admin state:
• Off – Admin is Disabled.
• Green – Admin is Enabled.
• Blinking Green – Management traffic is passing through the interface.
If the MGT interface is being used for protection, the Orange LED indicates the status of the mate unit:

Phn 3963 013v000

Page 854
Chapter 23: Maintenance PTP 820C-HP LEDs

• Off – The interface is not in an operational state (down).

• Orange – The interface is operational (up).
• Blinking Orange – The interface is operational, and there is traffic on the interface
(Tx, Rx, or both).

Radio LED
The Radio LED indicates the status of the radio link:
• Off – The radio is off; all carriers are Admin = Disabled in the Interface Manager.
• Green - The power is on, and all carriers are operational (up).
• Orange – A signal degrade condition exists on at least one carrier.
• Red - A loss of frame (LOF) or excessive BER condition exists on at least one carrier.

Status LED
The Status LED indicates the status of the main board:
• Off – The power is off.
• Green - The power is on, and no alarms are raised on the motherboard.
• Orange – The power is on, and one or more minor alarms or warnings are raised on
the motherboard.
• Red - The power is on, and one or more major or critical alarms are raised on the
motherboard.

Protection LED
The Protection LED operates in a protected configuration to indicate the protection status:
• Red – A protection alarm exists (cable disconnected, mismatch configuration, or mate
communication not working). Note that only the active unit will have a red LED.
• Orange -Protection is enabled, and the unit is in standby mode.
• Green - Protection is enabled, the unit is in active mode, and no protection alarms are
present.
• Off – Protection is not enabled.

Phn 3963 013v000

Page 855
Chapter 23: Maintenance PTP 820S Connector Pin-outs

PTP 820S Connector Pin-outs

Figure 469 PTP 820S Interfaces

Eth1/PoE - GbE Electrical+PoE/Optical

Table 277 PTP 820S Eth1/PoE Interface- RJ-45/SFP Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 856
Chapter 23: Maintenance PTP 820S Connector Pin-outs

Eth2 - GbE Electrical/Optical

Table 278 PTP 820S Eth2 Interface - RJ-45/SFP Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Eth3 - GbE Electrical/Optical

Table 279 PTP 820S Eth3/EXP Interface - RJ-45/SFP Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 857
Chapter 23: Maintenance PTP 820S Connector Pin-outs

MGT/PROT - Management (FE-Standard) and Protection (FE-

Non-Standard)
Table 280 PTP 820S MGT/PROT Interface - RJ-45 Pinouts

Pin no. Description

Management - Standard 100Base-T 4 Wire

1 TX+

2 TX-

3 RX+

6 RX-

Protection - Non-Standard 100Base-T 4 Wire

4 TX+

5 TX-

7 RX+

8 RX-

DC
The DC port is UL-60950 compliant, with a 2-pin connector.

Figure 470 PTP 820S DC Connector

RSL Interface
PTP 820S uses a weather-proof BNC connector.

Phn 3963 013v000

Page 858
Chapter 23: Maintenance PTP 820S LEDs

Note
The voltage at the RSL interface is 1.XX where XX is the RSL level. For example: 1.59V means an RSL
of -59 dBm. Note that the voltage measured at the RSL interface is not accurate and should be used
only as an aid).

PTP 820S LEDs

The PTP 820S provides the following LEDs to indicate the status of the unit's interfaces, and the unit as a whole:
• Electrical GbE Interface (RJ-45) LEDs
• Optical GbE Interface (SFP) LEDs
• Management FE Interface (RJ-45) LEDs
• Radio LED
• Status LED
• Protection LED

Electrical GbE Interface (RJ-45) LEDs

There are two LEDs next to each electrical (RJ-45) interface, a Green LED to the left of the interface and an Orange
LED to the right of the interface.
The Green LED indicates the port’s Admin state :
• Off - Admin is Disabled .
• Green - Admin is Enabled .
The Orange LED indicates the interface's Admin and cable connection status, and whether there is traffic on the
interface:
• Off – Admin is Disabled or no cable is connected to the interface.
• Orange – Admin is Enabled and a cable is connected to the interface.
• Blinking Orange – Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface..

Optical GbE Interface (SFP) LEDs

There is one Green LED next to each optical (SFP) GbE interface. The LED indicates the interface's Admin and cable
connection status, and whether there is traffic on the interface :
• Off - Admin is Disabled or no cable is connected to the interface .
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

Phn 3963 013v000

Page 859
Chapter 23: Maintenance PTP 820S LEDs

Management FE Interface (RJ-45) LEDs

There are two LEDs next to the MGT (management) interface, a Green LED to the left of the interface and an
Orange LED to the right of the interface.
The Green LED indicates the port’s Admin state :
• Off - Admin is Disabled.
• Green - Admin is Enabled .
• Blinking Green – Management traffic is passing through the interface.
If the MGT interface is being used for protection, the Orange LED indicates the status of the mate unit:
• Off – Admin is Disabled or no cable is connected to the interface..
• Orange – Admin is Enabled and a cable is connected to the interface .
• Blinking Orange – Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface .

Radio LED
The RadioLED indicates the status of the radio link:
• Green - The power is on, and all carriers are operational (up).
• Red - A Loss of Frame (LOF) condition exists in at least one carrier.
• Orange – A signal degrade condition exists on the carrier.
• Off – The radio is off; the carrier is Admin = Disabled in the Interface Manager.

Status LED
The Status LED indicates the status of the main board:
• Off – The power is off.
• Green - The power is on, and no alarms are raised on the motherboard.
• Red - The power is on, and one or more major or critical alarms are raised on the motherboard.
• Orange – The power is on, and one or more minor alarms or warnings are raised on the motherboard.

Protection LED
The Protection LED operates in a protected configuration to indicate the protection status:
• Red – A protection alarm exists (cable disconnected, mismatch configuration, or mate communication not
working). Note that only the active unit will have a red LED.
• Orange -Protection is enabled, and the unit is in standby mode.
• Green - Protection is enabled, the unit is in active mode, and no protection alarms are present.
• Off – Protection is not enabled.

Phn 3963 013v000

Page 860
Chapter 23: Maintenance PTP 820E Connector Pin-outs

PTP 820E Connector Pin-outs

There are three basic PTP 820E hardware versions with the following interface layouts:
• ESE – Two electrical Ethernet interfaces (Port 1 and Port 3) and one optical SFP cage that supports regular and
CSFP standards (Port 2).
• ESS – One electrical Ethernet interface (Port 1), an optical SFP cage that supports the regular SFP standard
(Port 2), and an optical SFP cage that supports regular and CSFP standards (Port 3).

•
• Note:PTP820E ESS requires System Release 9.0 or higher
• ESP – One electrical Ethernet interface for PoE and management (Port 1), an optical SFP cage that supports
regular and CSFP standards (Port 2), and an optical SFP cage that can be configured for 1G or 10G (Port 3).
Notes: PTP 820E ESP requires Release 9.7 or higher.
The following table summarizes the port distribution in each of these variants.

Table 281 PTP 820E Port Distribution Per Hardware Model

PTP 820E Port 1 Port 2 Port 3
Variant
ESE RJ-45: 10/100/1000BaseT SFP cage: SFP, CSFP RJ-45: 10/100/1000BaseT
1Gb/s Ethernet Traffic (Eth1) 1Gb/s Ethernet Traffic (Eth2 + Local management 1 Gb/s
+ PoE Eth3) Ethernet
ESS RJ45: 10/100/1000BaseT SFP cage: SFP SFP cage: SFP, CSFP
Local management + PoE 1Gb/s Ethernet Traffic (Eth1) 1Gb/s Ethernet Traffic (Eth2 +
1Gb/s Ethernet Traffic Eth3)
ESP RJ45: 10/100/1000BaseT SFP cage: SFP, CSFP SFP cage: SFP/SFP+
Local management + PoE 1Gb/s Ethernet Traffic (Eth2 + 1/10Gb/s Ethernet Traffic (Eth1)
Eth3)

Phn 3963 013v000

Page 861
Chapter 23: Maintenance PTP 820E Connector Pin-outs

PTP 820E Interfaces – ESE

Figure 471 PTP 820E Interfaces – ESE

• Port 1 (Eth1):
Electric: 10/100/1000Base-T RJ-45.
PoE or external DC support (adapter)
• Port 2
SFP cage which supports – Regular and CSFP standards
• Regular SFP provides Eth2
• CSFP (Dual BiDir SFP) provides Eth2 and Eth3
• Port 3 (MGT):
Electric: 10/100/1000Base-T RJ-45.
Management port (no traffic)
• Extension Port:
◦ XPIC and HSB source sharing (planned for future release)
◦ Direct connection to CPU by technician – see Error! Reference source not
found.
◦

Phn 3963 013v000

Page 862
Chapter 23: Maintenance PTP 820E Connector Pin-outs

PTP 820E Interfaces – ESP

Figure 472 PTP 820E Interfaces – ESP

Electric: 10/100/1000Base-T RJ-45.
Management port (no traffic)
PoE or external DC support (adapter)
• Port 2
SFP cage which supports – Regular and CSFP standards
• Regular SFP provides Eth2
• CSFP (Dual BiDir SFP) provides Eth2 and Eth3
• Port 3 (Eth1):
SFP cage which supports SFP+ standard
1G or 10G Eth traffic (user-configurable)
Note: If the port is configured for 1G, a regular SFP module (rather than SFP+) can be
used.
• Extension Port:
◦ XPIC and HSB (planned for future release)
◦ Direct connection to CPU by technician – see Error! Reference source not
found.

Eth1/PoE GbE Interface (RJ-45) (ESE only)

Table 282 PTP 820E Eth1/PoE Interface- RJ-45
Pin no. Description
1 BI_DA+ (Bi-directional pair +A)
2 BI_DA- (Bi-directional pair -A)

Phn 3963 013v000

Page 863
Chapter 23: Maintenance PTP 820E Connector Pin-outs

Pin no. Description

3 BI_DB+ (Bi-directional pair +B)
4 BI_DC+ (Bi-directional pair +C)
5 BI_DC- (Bi-directional pair -C)
6 BI_DB- (Bi-directional pair -B)
7 BI_DD+ (Bi-directional pair +D)
8 BI_DD- (Bi-directional pair -D)

Eth1 GbE Optical Interface (SFP) (ESS only)

Eth1 in ESS hardware versions is an SFP cage that supports the regular SFP standard.

Eth2/Eth3 GbE Optical Interface (SFP/CSFP)

Eth2/Eth3 is an SFP cage that supports regular and CSFP standards.

Eth1 10G Optical Interface (SFP+) (ESP only)

Eth1 is an SFP cage that supports the SFP+ standard. Eth1 can be configured by the user for 1G or 10G Ethernet
traffic.

MGT GbE Electrical Interface (RJ-45)

Table 283 PTP 820E MGT Interface - RJ-45/ Pinouts
Pin no. Description
1 BI_DA+ (Bi-directional pair +A)
2 BI_DA- (Bi-directional pair -A)
3 BI_DB+ (Bi-directional pair +B)
4 BI_DC+ (Bi-directional pair +C)
5 BI_DC- (Bi-directional pair -C)
6 BI_DB- (Bi-directional pair -B)
7 BI_DD+ (Bi-directional pair +D)
8 BI_DD- (Bi-directional pair -D)

EXT Port
This port is reserved for future use.

Phn 3963 013v000

Page 864
Chapter 23: Maintenance PTP 820E Connector Pin-outs

Power Adaptor
For configurations in which power is not provided via PoE, a special adaptor (PTP 820_Mini_Power_Adaptor) is
available that enables users to connect a two-wire power connector to the PoE port. This adaptor is located inside
of the gland. In such configurations, only one electrical GbE interface is available (MGT).

Figure 473: Two-Wire to PoE Port Power Adaptor

RSL Interface
PTP 820E uses a two-pin connection to measure the RSL level using standard voltmeter test leads:

Figure 474 RSL Pins

Phn 3963 013v000

Page 865
Chapter 23: Maintenance PTP 820E LEDs

PTP 820E LEDs

The PTP 820E provides the following LEDs to indicate the status of the unit's interfaces, and the unit as a whole:
• Eth1/PoE GbE Interface (RJ-45) LEDs (ESE only)
• Eth1 10G Optical Interface (SFP+) LEDs (ESP only)
• Eth2/Eth3 GbE Optical Interface (SFP/CSFP) LEDs
• MGT GbE Electrical Interface (RJ-45) LEDs
• Radio LED
• Status LED
• Protection LED

Eth1/PoE GbE Interface (RJ-45) LEDs (ESE only)

There are two LEDs next to each electrical (RJ-45) interface, a Green LED to the left of the interface and an Orange
LED to the right of the interface.
The Green LED indicates the interface’s Admin status:
• Off – Admin is Disabled.
• Green – Admin is Enabled.
The Orange LED indicates the interface's Admin and cable connection status, and whether there is traffic on the
interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Orange - Admin is Enabled and a cable is connected to the interface.
• Blinking Orange - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

Eth1 10G Optical Interface (SFP+) LEDs (ESP only)

Eth1 is an SFP cage that supports regular SFP and SFP+.
There is one Green LED to the left of the interface. The LED is for Eth1 and indicates the interface's Admin and
cable connection status, and whether there is traffic on the interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

Note: The LED does not indicate traffic on the interface (Blinking Green) in 10G mode.

Eth2/Eth3 GbE Optical Interface (SFP/CSFP) LEDs

Eth2/Eth3 is an SFP cage that supports regular and CSFP standards.

Phn 3963 013v000

Page 866
Chapter 23: Maintenance PTP 820E LEDs

• When Eth2/Eth3 is used with a regular SFP, it provides Ethernet port 2.

• When Eth2/Eth3 is used with CSFP, it provides two Ethernet ports: Ethernet port 2 and Ethernet port 3.

Note: The Web EMS displays Ethernet port 3 even if a regular SFP is used, and there is
no Ethernet port 3. You must avoid configuring Ethernet port 3 in this case.

On ESE and ESS hardware versions, there is one Green LED to the left of the interface and one Green LED to the
right of the interface. On ESP hardware versions, there are two LEDS to the left of the interface. The LED to the left
or the upper LED is for Eth2. When CSFP is used, the LED to the right or the lower LED is for Eth3; otherwise, it is
inactive.
Each LED indicates the interface's Admin and cable connection status, and whether there is traffic on the interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.

MGT GbE Electrical Interface (RJ-45) LEDs

There are two LEDs next to the MGT interface, a Green LED to the left of the interface and an Orange LED to the
right of the interface.
The Orange LED indicates the interface's Admin and cable connection status, and whether there is traffic on the
interface:
• Off - Admin is Disabled or no cable is connected to the interface.
• Green - Admin is Enabled and a cable is connected to the interface.
• Blinking Green - Admin is Enabled and a cable is connected to the interface, and there is traffic on the
interface.
The Green LED is not functional in this release.

Radio LED
The Radio LED indicates the status of the radio link:
• Off – The radio is off; the carrier is Admin = Disabled in the Interface Manager.
• Green - The power is on, and the carrier is operational (up).
• Orange – A signal degrade condition exists on the carrier.
• Red - A loss of frame (LOF) or excessive BER condition exists on the carrier.

Status LED
The Status LED indicates the status of the main board:
• Off – The power is off.
• Green - The power is on, and no alarms are raised on the motherboard.
• Orange - The power is on, and one or more minor alarms or warnings are raised on the motherboard.
• Red - The power is on, and one or more major or critical alarms are raised on the motherboard.

Phn 3963 013v000

Page 867
Chapter 23: Maintenance PoE Injector Pin-outs

Protection LED
Reserved for future use.

PoE Injector Pin-outs

Figure 475: PoE Injector Connectors

PoE Port
Table 284 PoE Injector PoE Port - RJ-45 Pinouts

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

Phn 3963 013v000

Page 868
Chapter 23: Maintenance PoE Injector LEDs

Data Port
Table 285 PoE Injector RJ-45 Data Port Supporting 10/100/1000Base-T

Pin no. Description

1 BI_DA+ (Bi-directional pair +A)

2 BI_DA- (Bi-directional pair -A)

3 BI_DB+ (Bi-directional pair +B)

4 BI_DC+ (Bi-directional pair +C)

5 BI_DC- (Bi-directional pair -C)

6 BI_DB- (Bi-directional pair -B)

7 BI_DD+ (Bi-directional pair +D)

8 BI_DD- (Bi-directional pair -D)

DC
One or two DC ports, depending on the PoE Injector model:
The available PoE Injector model is:
• PTP 820 PoE Injector all outdoor, redundant DC input, +24VDC suppor (part number: N000082L022A) –
PoE_Inj_AO_2DC_24V_48V – Includes two DC power ports with power input ranges of ±(18-60)V each.
These ports are UL-60950 compliant, with a 2-pin connector.

PoE Injector LEDs

• PWR1 (Bi-color LED)
o Green – Power available on PWR1 DC input
o Off – No power is available on PWR1 DC input.
• PWR2 (Bi-color LED)
o Green – Power available on PWR2 DC input,
o Off – No power is available on PWR2 DC input.
• PoE (Tri -color LED)
o Orange – No load is detected
o Green – Providing in-line power
o Blinking Red – Invalid/over-load
o Off – no power to the injector unit.

Radio LED
The Radio LED indicates the status of the radio link:

Phn 3963 013v000

Page 869
Chapter 23: Maintenance PoE Injector LEDs

• Off – The radio is off.

• Green - The power is on, and all carriers are operational (up).
• Orange - A signal degrade condition exists in at least one carrier.
• Red - A loss of frame (LOF) or excessive BER condition exists in at least one carrier.

Phn 3963 013v000

Page 870
 Chapter 24: Alarms List PoE Injector LEDs

Chapter 24: Alarms List

The following table lists all alarms used in the PTP 820C/S products.

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Framer digital loopback is User enabled framer digital

10 Alarm Warning Disable the framer digital loopback.
enabled. loopback.
Check connection to remote
No connection to remote server. servers.
Warning Remote server quality does not meet Check remote server’s status
11 Alarm NTP locked on local clock parameters in the unit’s “NTP
the minimum required to be chosen
configuration panel”.
by the NTP algorithm.

Event NTP locked on server

15 Indeterminate

Unit Temperature is out of

25 Alarm Warning
system specified limits.
Check/replace the power supply
Power supply output is too low.
connected to the RFU.
Power cable to the unit is defective.
26 Alarm Unit input voltage is too low. Warning Check/replace the power cable
Threshold value is not set
connected to the RFU.
correctly.
Set the threshold correctly.
Make sure the power supply
Power Supply output is too high. voltage is within the specification
27 Alarm Unit input voltage is too high. Warning
Threshold value not set correctly. range. 2) Adjust the threshold
value.

28 Event Unit warm reset. Indeterminate

Phn 3963 013v000

Page 871
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

29 Event Unit reset. Warning

PoE supply output is too low. Make sure the PoE voltage is within
30 Alarm POE input voltage is too low Warning
PoE cable to the unit is defective. the specification range.

Change Remote request was

31 Event Major
sent

Protection switchover due to

32 Event Major
remote request

Unit Redundancy and 4x4 MIMO

33 Alarm Major
cannot operate simultaneously.

At least one interface is not

Check the physical connections.
connected or configured to admin
Verify that the Admin state of all
LAG is not fully functional - LAG down.
100 Alarm Major the LAG members is up.
Degraded. If one of the members is radio it
Verify the operational state of all
might be in operational state down
radio members in the LAG.
due to channel fading

Check the physical connections and

administrative status on both sides
of the link of all interfaces that are
101 Alarm LAG operational state is down Critical The LAG group is not operational. members of the LAG Group.
Check the physical connections of
all interfaces that are members of
the LAG Group.

Wait for expiration of the loopback

102 Alarm Loopback is active Major Ethernet loopback is active. timeout, or manually disable the
loopback.

Slot X port XX is mirrored to Mirroring is enabled by user

103 Alarm Minor Disable mirroring.
slot Y port YY configuration.

Phn 3963 013v000

Page 872
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Reset the system.

System reset is required after the
120 Alarm Port speed mismatch Major Change the port speed back to the
port speed was changed.
previous value.

Failure of the radio/remote radio

interface which is monitored for Check adjacent local/remote radio
Auto-state-propagation is
150 Alarm Major automatic state propagation causes interface for failure conditions that
triggered
automatic shutdown of the cause automatic state propagation.
controlled interface.

Verify that the mate unit is up and

running.
Mate unit is absent/failure. Check the state of the protection
Protection communication is
200 Alarm Major Protection cable is disconnected. cable connection between the
down
units.
Unit failure.
Reset the mate unit
Replace the mate unit

201 Alarm Protection in Lockout State Major

Protection switchover due to Check the unit.

202 Event Major
local failure Look for current alarms.

Verify that the mate unit is up and

running.
Mate does not exist or cable
203 Alarm Mate does not exist Major Verify that the protection cable is
unplugged.
properly connected between the
units.

External Protection configured Remove External Protection or 1+1

204 Alarm HSB insufficient configuration Critical
together with 1+1 HSB. HSB configuration.

Phn 3963 013v000

Page 873
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Protection revertive mode - Identical configuration for the Ensure one (and only one) unit is
warning
205 Alarm insufficient configuration revertive-primary parameter. configured as the primary unit.

307 Event TDM interface is up Warning

308 Event TDM interface is down Warning

At both ends of the cable:

Cable disconnected. Check the cable connection.
401 Alarm Loss of Carrier Major Defective cable. Check the Admin state of the port.
External equipment failure. Replace the cable.
Check external equipment.

Ethernet interface is back to being Notification. Corrective action is

407 Event Ethernet interface is up Warning
operational. not required.

Set the Ethernet interface admin

User commanded the interface to
State to Up.
admin down.
Reconnect the Ethernet cable
408 Event Ethernet interface is down Warning Ethernet cable is disconnected.
Wait 30 seconds to allow the
Ethernet card is initializing.
Ethernet card to complete its init.
External equipment failure.
Check external equipment.

Phn 3963 013v000

Page 874
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check link performance via the

Web EMS Radio PM and Statistics
page and take corrective action
Fade in the link.
accordingly..
Defective IF cable.
Check IF cable and replace if
601 Alarm Radio excessive BER Major Fault in RFU. required.
Fault in RMC (Radio Modem Card). Replace RFU.
Interference on the link. Replace RMC (Radio Modem Card).
Remove source of interference or
change link frequency.

Configure same Link ID for both

sides of link via Web EMS Radio
Link ID is not the same at both sides
Parameters page.
of link.
602 Alarm Link ID mismatch Major Check if the radio is synched on
Radio has synched on the wrong
the correct peer radio (check:
peer radio.
channel frequency, antennae
direction).

Check link performance.

Fade in the link.
Check IF cable and replace if
Defective IF cable.
required.
Fault in RFU.
603 Alarm Radio loss of frame Critical Replace RFU.
Fault in RMC (Radio Modem Card).
Replace RMC (Radio Modem Card).
Different radio scripts at both ends
Make sure same script is loaded at
of the link.
both ends of the link.

Phn 3963 013v000

Page 875
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check link performance.

Fade in the link.
Check IF cable and replace if
Defective IF cable.
604 Alarm Radio signal degrade Minor required.
Fault in RFU.
Replace RFU.
Fault in RMC (Radio Modem Card).
Replace RMC (Radio Modem Card).

The radio interface is back to being

605 Event Radio interface is up Warning No action is required.
operational.

Radio interface is not operational:

If required, set the radio interface
User configured the radio interface
admin State to Up.
to admin Down.
Check if there is a reason for LOF /
606 Event Radio interface is down. Warning Loss of Frame (LOF) alarm is raised.
Excessive BER alarms.
Excessive BER alarm is raised.
Wait 30 seconds until the radio
Radio card has not completed its card finishes its init.
init.

If required, stop the frequency

607 Alarm Frequency scanner in progress Warning The frequency scanner is activated.
scanner process.

Reset the card.

801 Alarm Corrupted inventory file Critical The inventory file is corrupted Reinstall the software.
Replace the unit.

Reset the system.

802 Alarm Inventory file not found Warning The inventory file is missing Reinstall the software.
Replace the unit

Phn 3963 013v000

Page 876
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Verify remote SFP Tx laser power is

Remote SFP port Tx laser power is
SFP port RX power level is within range.
too low.
803 Alarm below the rx power level low Warning Check fiber type and length fit the
Fiber length is too long or fiber type
threshold installed SFP. If not, replace it with
doesn't fit the installed SFP.
an appropriate one.

SFP port RX power level is

804 Alarm above the rx power level high Warning Remote SFP Tx power is too high. Add attenuator on Rx side.
threshold

SFP port TX power level is

Check laser Bias current. If it is too
805 Alarm below the tx power level low Warning SFP transmit laser power is too low
low, replace SFP.
threshold

SFP port TX power level is Check laser Bias current and laser
806 Alarm above the tx power level high Warning SFP laser Tx power is too high. temperature values. If either of
threshold them is too high, replace SFP.
Default Activation Key
activated due to failure
807 Event Critical Corrupted Inventory

Activation Key Configuration

failed
808 Event Critical Corrupted Inventory

Disable demo mode from the

Demo mode has been activated by
901 Alarm Demo mode is active Warning Activation Key Configuration page
the user
in the Web EMS.

902 Event Demo mode is expired Warning

903 Event Demo mode is started Warning

904 Event Demo mode is stopped Warning

905 Event Activation key loading failure Major

Phn 3963 013v000

Page 877
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Activation key loaded

906 Event Warning
successfully

The current configuration does not

match the activation-key-enabled Go to the "Activation Key
feature set. Overview" page in the Web EMS to
48 hours after an "activation-key- display a list of features and their
907 Alarm Activation key violation Critical violation" alarm is raised, sanction activation key violation status.
mode is activated in which all alarms Install a new activation key that
except the activation key violation enables all features and capacities
alarm are cleared and no new alarms that you require.
are raised.

Disable demo mode and install a

Demo mode allowed period is about new valid activation key in the
908 Alarm Demo mode is about to expire Major
to end within 10 days “Activation Key Configuration”
page of the Web EMS.

Activation key validation has failed Make sure that the activation key
910 Alarm Activation key signature failure Major due to invalid product serial number matches the serial number of the
or activation key does not match. unit.

Activation key violation

911 Event Major
sanction is enforced

Essential internal activation key

Activation key components are
913 Alarm Major components are missing or Reinstall software
missing or corrupted
corrupted.

Apply a copy-to-mate command to

Radio protection configuration The configuration between the radio
1002 Alarm Major copy the configuration from the
mismatch protection members is not aligned
active radio to the standby radio.

Phn 3963 013v000

Page 878
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check the system for local failures.

Protection decision machine
Radio protection switchover - What checks? Check Radio
1006 Event Warning initiated switchover due to local
reason Parameters: Tx Level, Rx Level,
failure or user command
Modem MSE.

Insert the radio module.

Radio protection function is missing Replace a defective existing radio
1007 Alarm Radio protection no mate Major radio module, module defected or module.
disabled Make sure all radio interfaces are
enabled.

Remote switchover request

1008 Event Warning
was sent - reason

Radio protection lockout The user has issued a lockout

1009 Alarm Major Clear the lockout command
command is on command

LOC event on an Ethernet interface.

Ethernet Interface Group Check the system for local failures.
1010 Event Warning Protection group member was
protection switchover Check external equipment.
disabled or pulled out of the shelf.

Interface protection lockout is The user has issued a lockout

1011 Alarm Major If required, clear the lockout.
on command

Insert the interface module.

Interface protection no mate: Interface protection function is Replace a defective existing
1012 Alarm mate interface is missing or Major missing an interface module, module interface.
disabled is defective or disabled. Make sure all interfaces are
enabled.

1102 Event Software installation status: Warning

Phn 3963 013v000

Page 879
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

A software version has been

1105 Event New version installed Warning installed but system has not been
reset.

User approved download of

1111 Event Warning
software version file

1112 Event Software download status: Warning

1113 Event Missing SW components: Warning

Incomplete file set; missing Software bundle is missing

1114 Event Warning Get a complete software bundle
components components.

Configuration file backup

1150 Event Warning User command
generation started

Configuration file backup Backup file creation finished

1151 Event Warning
created successfully

Failure in configuration file System failed in attempt to create

1152 Event Warning
backup generation backup configuration file

Configuration successfully Configuration restore finished

1153 Event Warning
restored from file backup successfully

Configuration file system type

Failure in configuration System failed in attempt to restore mismatch
1154 Event Warning
restoring from backup file configuration from backup file Invalid or corrupted configuration
file

Restore operation cancelled because

Configuration restore operation of user command or execution of
1155 Event Warning Try again
cancelled another configuration management
operation

Phn 3963 013v000

Page 880
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

User issued command for

1156 Event Warning User command
transfer of configuration file

Configuration file transfer

1157 Event Warning Configuration file transfer successful
successful

Mark sure protocol details are

Configuration file transfer Communications failure.
1158 Event Warning properly configured.
failure File not found in server
Make sure file exists.

Configuration file transfer in

1159 Event Warning File transfer started
progress

CLI configuration script

1163 Event Warning User command
activation started

CLI Configuration script

1164 Event Warning
executed successfully

Verify script in the relevant line,

Syntax Error.
and run again.
1165 Event CLI Configuration script failed Warning Error returned by system during
Note that script may assume pre-
runtime
existing configuration.

1166 Event Unit info file transfer status: Warning

1167 Event Unit info file creation status: Warning

Configuration restore operation Restore operation started because

1169 Event Warning
started of user command

Download software package.

1201 Alarm Modem firmware file not found Critical Modem file is missing
Reset the system.

Modem firmware was not Modem firmware file is corrupted. Download software package.
1202 Alarm Critical
loaded successfully System failure. Reset the system.

Phn 3963 013v000

Page 881
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

1203 Event Modem watch-dog reset event Warning

Radio MRMC script LUT file is Download the specific radio MRMC
1301 Alarm Critical Damaged radio MRMC script LUT file
corrupted script LUT file

Radio MRMC script LUT file is Download the specific radio MRMC
1302 Alarm Critical Missing radio MRMC script LUT file
not found script LUT file

Radio MRMC script modem file Damaged radio MRMC script modem Download the specific radio MRMC
1304 Alarm Critical
is corrupted file script modem file

Radio MRMC script modem file Missing radio MRMC script modem Download the specific radio MRMC
1305 Alarm Critical
is not found file script modem file

Damaged Radio MRMC script LUT Download the specific radio MRMC
1308 Alarm Radio MRMC file is corrupted Critical
file RFU file

Radio MRMC RFU file is not Download the specific radio MRMC
1309 Alarm Major Missing radio MRMC RFU file
found RFU file

Radio errrror! Replace the radio hardware

1312 Alarm Major Damaged hardware module
MRMC script loading failed module

1313 Alarm MRMC RX profile below Major

threshold 1

1314 Alarm MRMC RX profile below Critical

threshold 2

Incompatible RFU TX RFU calibration tables require SW

1401 Alarm Major Upgrade IDU SW
calibration upgrade

1501 Alarm Remote communication failure Critical Fade in the link Check the link performance

1601 Alarm IF loopback Warning User enabled IF loopback Disable IF loopback

Phn 3963 013v000

Page 882
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check installation.
Reset the RMC (Radio Modem
Extreme temperature condition.
1602 Alarm IF synthesizer is unlocked. Critical Card) module.
HW failure.
Replace the RMC (Radio Modem
Card).

Check for obstruction in link path.

RSL is very low due to: Check the antennae alignment and
Weather conditions, obstruction in link planning.
Radio Receive Signal Level is antenna line of sight, antennae Recalculate the Path Loss and set
1610 Alarm Warning
below the configured threshold alignment. the threshold accordingly.
Configured threshold needs to be Check link settings - Tx Power and
adjusted.2. Tx Frequency.
Check for a hardware problem.

Actual transmitted signal level has

ATPC overridden: Tx level has
been at its maximum value for Correct the transmission levels. The
been equal to the Max Tx
1651 Alarm Warning longer than allowed. This is probably alarm will be cleared only upon
level for a longer time than
caused by a configuration error or manual clearing.
allowed
link planning error.

Correct the installation conditions.

Radio unit extreme Installation conditions. Verify that the product is operating
1697 Alarm Warning
temperature Defective RFU. according to specifications.
Replace the RFU.

Check/replace the power supply

Radio unit input voltage is too Power supply output is too low. connected to the RFU.
1698 Alarm Warning
low Power cable to RFU is defective. Check/replace the power cable
connected to the RFU.

Phn 3963 013v000

Page 883
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Radio unit input voltage is too

1699 Alarm Warning Power Supply output too high. Check power supply.
high

Reinitiate the FW download by

FW alignment interrupted, power
disabling and then enabling the
1700 Alarm Radio unit not aligned to IDU Critical disruption, ODU cable malfunction.
corresponding RFU port.
Damaged ODU.
Replace the ODU

Check cables and connectors.

Cable is not connected to radio card
1701 Alarm Cable open Major Replace Radio card.
or RFU.
Replace RFU.

Check cables and connectors.

1702 Alarm Cable short Major Physical short at the IF cable Replace Radio card.
Replace RFU.

Verify RFU software download

completed.
Check IF cable and connector.
Defective IF cable.
Verify that N-Type connector inner
IF cable not connected properly.
pin is not spliced.
1703 Alarm RFU communication failure Warning Defective RMC (Radio Modem Card).
Replace RMC.
Defective RFU.
Replace RFU.
RFU software download in progress.
For High Power RF Unit:
Check BMA connector on OCB
Check BMA connector on RFU.

Reset the RMC (Radio Modem

1704 Alarm RFU delay calibration failure 1 Warning Defective RFU Card) / RFU.
Replace RFU.

Phn 3963 013v000

Page 884
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Calibration cannot be completed due Enter delay calibration value

1705 Alarm RFU delay calibration failure 2 Warning
to notch detection manually.

Verify that the product is operating

Installation conditions. according to specifications.
1706 Alarm RFU extreme temperature Warning
Defective RFU. Correct the installation conditions.
Replace the RFU."

The RFU type does not support the Replace the RFU with an RFU type
RFU is incompatible with ABC
1707 Alarm Warning type of Multi-Carrier ABC the user that supports the configured Multi-
configuration
has configured. Carrier ABC type.

Check if problem repeats and if

RFU frequency was set
1708 Event Warning Defective RFU errors/alarms reported.
automatically
Replace RFU.

1709 Alarm RFU hardware failure 1 Critical Defective RFU. Replace RFU.

1710 Alarm RFU hardware failure 2 Critical Defective RFU. Replace RFU.

Check IF cable connectors.

IF cable connection. Verify that N-Type connector inner
1711 Alarm Low IF signal to RFU Major Defective RFU. pin is not spliced.

Defective RMC (Radio Modem Card). Replace RMC (Radio Modem Card).
Replace RFU.

Check IF cable and connectors.

Verify that N-Type connector inner
Low RX IF signal (140 MHz) from
1712 Alarm Low IF signal from RFU Warning pin is not spliced.
RFU.
Replace RMC (Radio Modem Card).
Replace RFU.

Phn 3963 013v000

Page 885
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Installation conditions. Check installation conditions.

1713 Alarm RFU PA extreme temperature Warning
Defective RFU. Replace RFU.

Defective IF cable/connector. Replace IF cable/connector.

1714 Alarm RFU power failure (12v) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1715 Alarm RFU power failure (1.5v) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1716 Alarm RFU power failure (24v) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1717 Alarm RFU power failure (6v pro) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1718 Alarm RFU power failure (6v SW) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1719 Alarm RFU power failure (-5v) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

Defective IF cable/connector. Replace IF cable/connector.

1720 Alarm RFU power failure (Vd) Major Defective RFU. Replace RFU.
Defective IDU. Replace IDU.

1721 Event RFU reset Major

Phn 3963 013v000

Page 886
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

1722 Alarm RFU loopback is active Major User has activated RFU loopback. Disable RFU loopback.

RFU mode changed to

1723 Event Indeterminate
Combined

1724 Event RFU mode changed to Diversity Indeterminate

1725 Event RFU mode changed to Main Indeterminate

At least one of the RFU's power Check the RFU cable connection.
1726 Alarm RFU power supply failure Major
supply voltages is too low. Replace the RFU.

Check antenna alignment & link

planning.
Check link settings (TX power, TX
1727 Alarm RFU RX level out of range Warning RSL is very low, link is down.
frequency).
Check antenna connections.
Replace local/remote RFU.

Check that the fault is not due to

rain/multi-path fading or lack of
LOS.
Improper installation.
Check link settings (TX power, TX
1728 Alarm RFU RX level path1 out of range Warning Fading event. frequency).
Defective RFU. Check antenna alignment.
Check antenna connections.
Replace local/remote RFU.

Phn 3963 013v000

Page 887
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check that the fault is not due to

rain/multi-path fading or lack of
LOS.
Improper installation.
Check link settings (TX power, TX
1729 Alarm RFU RX level path2 out of range Warning Fading event. frequency).
Defective RFU. Check antenna alignment.
Check antenna connections.
Replace local/remote RFU.

Defective RFU cable.

RFU cable not connected properly. Check RFU power supply.

Radio unit communication Defective RIC (Radio Interface Card). Check RFU cable and connectors.
1730 Alarm Critical
failure Defective RFU. Replace RIC (Radio Interface Card).
RFU initialization in progress. Replace RFU.
RFU powered off.

Check RFU cable and connectors.

Power is enabled but consumption is
1731 Alarm Power supply cable open Major If internal power supply is not in
lower than threshold.
use disable the power supply.

Check RFU cable and connectors.

Disconnect and Re-Connect the
Power is enabled but consumption RFU cable.
1732 Alarm Power supply cable short Major reached the threshold. Extract the RIC-D and re-insert it.
Physical short at the ETH cable. Restart the IDU.
Replace the RIC-D card or the PTP
820F IDU.

Phn 3963 013v000

Page 888
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Replace RFU.
At least one of the RFU synthesizers
1733 Alarm RFU synthesizer unlocked Major In XPIC mode, replace mate RFU as
is unlocked
well.

Replace RFU.
Defective RFU (the RFU cannot
1734 Alarm RFU TX level out of range Minor Intermediate solution - reduce TX
transmit the requested TX power)
power.

1735 Alarm RFU TX Mute Warning RFU Transmitter muted by user Unmute the RFU transmitter

IDU SW does not support this

1736 Alarm Major IDC SW does not support the RFU Upgrade IDC SW
type of RFU

1737 Event Card was extracted from slot Warning Card was extracted from slot NA

Card is down as a result of card Reset Card.

1738 Alarm Card is in Failure state Major
failure Check if slot was disabled.

There is no FPGA file found on the

1739 Alarm FPGA Firmware file not found Critical NA
Main Board for the card on the slot

Reset Card.
Download card firmware has Firmware download was
1740 Alarm Major Download software package.
failed unsuccessful.
Try to insert another Card.

1741 Event Card was inserted to slot Warning Card was inserted to slot NA

Card is in interconnection Card is down as a result of card Reset Card.

1742 Alarm Major
failure state interconnection failure Check if the slot was disabled.

Card is missing.
Insert Expected Card.
1743 Alarm Expected Card is missing in slot Major Expected Card Type configured on
Clear Expected Card Type.
empty slot.

Phn 3963 013v000

Page 889
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Reset.
This Card type is not supported The card is not on the Allowed Card
1744 Alarm Major Insert Card belongs to Allowed
in this slot Types list for this slot.
Card Types list.

1745 Event Card operational state is Down Indeterminate Card state was change to Down state NA

1746 Event Card operational state is Up Indeterminate Card state was change to Up state NA

Card operational state is Up Card state was change to Up state

1747 Event Indeterminate NA
with Alarms but with Alarms indication

Expected card type is different than Insert Expected Card.

1748 Alarm Unexpected Card Type in slot Minor
the actual card type Change Expected Card Type.

1749 Event Slot was Disabled Indeterminate The user Disabled slot NA

1750 Event Slot was Enabled Indeterminate The user Enabled slot NA

1751 Event Card on slot was Reset Indeterminate The user Reset slot NA

FAN Card was extracted from

1752 Event Warning FAN Card was extracted from slot
slot

1753 Event FAN failure Major

1754 Event FAN Card was inserted to slot Warning FAN Card was inserted to slot

FAN Card is missing. Insert FAN Card.

1755 Alarm FAN Card is missing in slot Critical
Slot enabled when empty. Disable slot.

Correct the installation conditions.

This alarm is non-operational Installation conditions. Verify that the product is operating
1756 Alarm and has been superseded by Major Defective unit. according to specifications.
Alarm 32002. Defective fan. Replace the fan card.
Replace the unit.

1757 Alarm FAN Card is in Failure state Major FAN Card is in Failure state Change FAN Card

Phn 3963 013v000

Page 890
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Power Supply was extracted Power Supply was extracted from Re-Insert the power supply back
1758 Event Warning
from slot slot into the slot.

Power Supply was inserted to

1759 Event Warning Power Supply was inserted to slot.
slot

Power Supply is missing.

1760 Alarm Power Supply is missing in slot Major Insert Power Supply.
Slot enabled when empty.

Make sure the power supply

System power supply voltage is
voltage is within the specification
1761 Alarm Over voltage Major higher than allowed.
range.
Threshold value is too low.
Check the value of the threshold.

Make sure the power supply

System power supply voltage is
voltage is within the specification
1762 Alarm Under voltage Major lower than allowed.
range.
Threshold value is too high.
Check the value of the threshold.

The Main board firmware is not

1763 Alarm Warning
found

Reset board.
Download Main Board Firmware download was
1764 Alarm Major Download software package.
firmware has failed unsuccessful.
Try to insert another board.

1765 Event Main Board was reset Warning

Make sure RFU is supported by SW

Unsupported RFU type.
version.
1766 Event RFU installation failure Warning IDU-RFU communications problem.
Check IDU-RFU cable.
RFU failure.
Replace RFU.

1767 Event RFU installation in progress Warning User command

Phn 3963 013v000

Page 891
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

RFU installation successfully

1768 Event Warning User command
completed

1770 Event Unit performing power-up. Major

Check the IF cable and connectors.

Verify that the N-Type/TNC
1771 Alarm RFU cable error. Major Errors in signal from IDU to XCVR. connector inner pin is not spliced.
Replace RMC.
Replace XCVR.

Check that the RMCs are in allowed

slots.
Signaling between RMCs (Radio
Populate the RMCs in different
1772 Alarm Radio XPIC sync loss Major Modem Cards) for XPIC functionality
allowed location in the chassis.
has failed
Replace RMC/s.
Replace chassis.

Check link performance.

Check IF cable, and replace if
The estimated radio BER (Bit Error
1773 Alarm Radio early warning. Warning required.
Rate) is above 10E-12.
Replace XCVR.
Replace RMC.

The hardware of the XCVR is OK, but Upgrade the XCVR software
RFU software download cannot
1774 Alarm Critical is it running with METRO radio application via XPAND-IP and then
be initiated.
application. reinitiate software download..

RFU software download is not Wrong type of XCVR, the XCVR

1775 Alarm Critical Replace the XCVR
possible. hardware is METRO.

RMC hardware failure of the clock

1776 Alarm RMC hardware failure. Major Replace the RMC.
distributor.

Phn 3963 013v000

Page 892
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Unmute the RFU transmitter or

1777 Event RFU TX Mute with timeout Warning RFU Transmitter muted by user.
wait for expiration of the timeout.

Replace RFU.
RFU power decreased due to Defective RFU (the RFU cannot
1778 Alarm Major Intermediate solution - reduce TX
PA temperature transmit the requested TX power).
power.

Make sure the required software

New installed software package does package include the running MRMC
1780 Event MRMC running script is deleted Warning not include the running MRMC radio radio script.
script Download and install the correct
software package.

New installed software package does Reset the radio carrier to reacquire
MRMC running script is
1781 Event Warning has an updated version of the the new updated MRMC radio
updated
running MRMC radio script script

2.5Gbps mismatch The card cannot function outside of Add the card to an ABC group, or
1782 Alarm Warning
configuration an ABC group in 2.5Gbps mode. change the Slot Section to 1Gbps.

Radio remote fault indication

1783 Alarm Minor
(RFI)

An internal hardware failure has Replace the card or unit which

1790 Alarm Hardware failure Critical
been detected by the system. reports hardware failure.

Interface is not operational Changes were made to platform due

1794 Alarm Warning Reset chassis
until chassis reset to user configuration

Check the cable connection.

Cable disconnected.
1800 Alarm T3 sync interface Loss of Carrier Major Disable the interface in the
Defective cable.
Interface Manager.

Phn 3963 013v000

Page 893
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check fan cable connection to the

RFU fan is disconnected.
RFU.
1975 Alarm RFU fan failure Major RFU fan HW failure.
Check/replace the fan.
RFU fan jammed.
Clear/clean the fan.

Wait for card to reboot.

TDM-LIC has rebooted and is Recent TDM-LIC card reset;
2001 Alarm Major Reset the TDM-LIC card.
not in service now System malfunction.
Replace card.

Reset the TDM-LIC.

TDM-LIC configuration Reset the Device.
2002 Alarm Major System malfunction.
mismatch Remove the TDM Configuration
and Re-Configure it again.

Reconnect cable.

Loss of Signal (LOS) on TDM- Check line cables.

2003 Alarm Major Cable is not properly connected.
LIC's front panel clock port Check external equipment.
Reset the TDM-LIC.

Communication with TDM-LIC

Reset the TDM-LIC.
2004 Alarm is disrupted in Host-Card Minor System malfunction
Replace card.
direction

Reset the TDM-LIC.

2005 Alarm TDM-LIC hardware failure Major System malfunction
Replace card.

Reset the TDM-LIC.

No communication with TDM- TDM-LIC to Host communication
2006 Alarm Major Reset the whole device.
LIC failure.
Replace card.

Phn 3963 013v000

Page 894
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check TDM service configuration

Jitter-buffer-overrun alarm on across the network.
2007 Alarm Major TDM service synchronization failure.
TDM service Check the loop timing/clock
recovery configuration.

Late-frame alarm on TDM TDM service failure or device Check TDM service configuration
2008 Alarm Warning
service synchronization problem. across the network.

Check network or configuration for

Loss-of-frames alarm on TDM Failure along the network path of
2009 Alarm Major errors in the network transport
service TDM service
side of the service

Payload size does not correspond to

Malformed-frames alarm on the defined value.
2010 Alarm Major Check TDM service configuration
TDM service Mismatch in PT value in RTP header
(if used)

Stray packets with wrong RTP

Misconnection alarm on TDM
2011 Alarm Major configurations are received and Check TDM service configuration
service
dropped.

Check the cable connectivity at

Cable is not properly connected.
both local and peer interfaces.
Alarm Indication Signal (AIS) on External equipment is faulty.
2012 Alarm Major Check external equipment.
TDM-LIC TDM port External equipment is not properly
Check configuration of the external
configured.
equipment.

Check the line interface

Line is not properly connected. connectivity
Loss Of Frame (LOF) on TDM-
2013 Alarm Major External equipment is faulty. Correct the TDM configuration.
LIC TDM port
Configuration problem. Check the equipment that feeds
the system

Phn 3963 013v000

Page 895
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check the line interface

Line is not properly connected. connectivity
Loss Of Multi-Frame (LOMF) on
2014 Alarm Major External equipment is faulty. Correct the TDM configuration.
TDM-LIC TDM port
Configuration problem. Check the equipment that feeds
the system

Loopback on TDM-LIC TDM

2015 Alarm Warning Loopback enabled. Disable loopback.
port

Cable is not properly connected.

Check the cable connectivity at
Loss Of Signal (LOS) on TDM-LIC Cable is faulty;
2016 Alarm Major both local and peer interfaces.
TDM port External equipment is faulty;
Check external equipment.
Defective TDM-LIC.

Check the cable connectivity at

Remote Alarm Indication (RAI) Cable is not properly connected.
2017 Alarm Minor both local and peer interfaces.
on TDM-LIC TDM port External equipment is faulty.
Check external equipment.

Enable relevant port.

E1/DS1 Unexpected signal on
2018 Alarm Warning Line is connected to a disabled port. Disconnect cable from relevant
TDM-LIC TDM port
port.

SSM received pattern change

2021 Event Warning No action is required.
was discovered

Reconnect line.

Excessive BER on TDM-LIC Line is not properly connected. Check line cables.
2022 Alarm Major
STM1/OC3 port External equipment is faulty. Check external equipment.
Power cycle the TDM-LIC.

Phn 3963 013v000

Page 896
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Check the cable connectivity at

Cable is not properly connected.
Loss Of Frame (LOF) on TDM- both local and peer interfaces.
2023 Alarm Major External equipment is faulty.
LIC STM1/OC3 port Check external equipment.
Wrong TDM configuration.
Reset the TDM-LIC.

Loopback on TDM-LIC
2024 Alarm Warning STM1/OC3 loopback enabled. Disable STM1/OC3 loopback.
STM1/OC3 port

Cable is not properly connected. Reconnect cable.

Loss Of Signal (LOS) on TDM-LIC External equipment is faulty. Check line cables.
2025 Alarm Critical
STM1/OC3 port Peer Equipment Configuration Check external equipment.
problem. Reset the TDM-LIC.

SFP is muted on TDM-LIC

2026 Alarm Warning The SFP interface has been muted. Set the interface to mute OFF.
STM1/OC3 port

SFP absent in TDM-LIC

2027 Alarm Critical SFP is not inserted properly. Insert the SFP.
STM1/OC3 port

Insert the SFP.

SFP failure on TDM-LIC SFP is not inserted properly.
2028 Alarm Critical Replace the SFP.
STM1/OC3 port Card is faulty.
Replace the card.

Insert the SFP.

SFP transmit failure on TDM-LIC SFP is not inserted properly.
2029 Alarm Critical Replace the SFP.
STM1/OC3 port Card is faulty.
Replace the card.

Install SFP properly.

Line is not properly connected.
Reconnect line.
Signal Degrade on TDM-LIC SFP is not properly installed.
2030 Alarm Minor Check line cables.
STM1/OC3 port SFP is faulty.
Check external equipment.
External equipment is faulty
Change Signal Degrade Threshold.

Phn 3963 013v000

Page 897
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

J0 misconfiguration. Make sure expected and received

J0 Trace Identifier Mismatch on Line is not properly connected. J0 identifiers match.
2031 Alarm Minor
TDM-LIC STM1/OC3 port SFP is not properly installed. Connect line cables properly.

External equipment is faulty. Install SFP properly.

SSM pattern received on TDM-

2032 Event Warning
LIC STM1/OC3 port changed

Check the cable connectivity at

Alarm Indication Signal (AIS) on Cable is not properly connected. both local and peer interfaces.
2033 Alarm Minor
TDM-LIC VC12/VT1.5 Local/Peer Configuration is incorrect. Check/Correct the configuration at
the local/peer.

Check the line cables.

Excessive BER on TDM-LIC Line is not properly connected. Fix the problem at the peer.
2034 Alarm Minor
VC12/VT1.5 External equipment is faulty. Change the Excessive BER
threshold.

Loopback on TDM-LIC Loopback enabled on TDM-LIC Disable loopback on TDM-LIC

2035 Alarm Warning
VC12/VT1.5 VC12/VC11. VC12/VC11.

Payload Mismatch Path (PLM)

Check/Correct the configuration at
2036 Alarm received on TDM-LIC Minor Incorrect VC12/VC11 configuration
the local/peer.
VC12/VT1.5

Remote Defect Indication (RDI) Fix the problem along the trail.
Alarm exists along the Trail.
2037 Alarm received on TDM-LIC Minor Check the cable connectivity at
Cable is not properly connected.
VC12/VT1.5 both local and peer interfaces.

Phn 3963 013v000

Page 898
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Make sure expected and receive J2

match
Signal Label Mismatch (SLM) J2 misconfiguration.
2038 Reconnect line.
Alarm received on TDM-LIC Minor Line is not properly connected.
Check line cables.
VC12/VT1.5 External equipment is faulty.
Check external equipment.
Reset the TDM-LIC.

Reconnect line.

Signal Degrade on TDM-LIC Line is not properly connected. Check line cables.
2039 Alarm Minor
VC12/VT1.5 External equipment is faulty. Check external equipment.
Reset the TDM-LIC.

Reconnect line.
Incorrect line is connected.
Unequipped on TDM-LIC Check line cables.
2040 Alarm Minor External equipment is faulty or
VC12/VT1.5 Check external equipment.
misconfigured.
Reset the TDM-LIC.

The configuration between the TDM- Apply a copy-to-mate command to

TDM-LIC card protection
2041 Alarm Major LIC card protection members is not copy the configuration from the
configuration mismatch
aligned required TDM-LIC to the other one

TDM-LIC card protection group The user has issued a lockout

2042 Alarm Minor Clear the lockout command
lockout command is on command

A member of TDM-LIC card TDM-LIC card is not installed in the

2043 Alarm Minor Install the missing TDM-LIC card
protection group is missing shelf

Phn 3963 013v000

Page 899
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

LOS alarm on a STM1 interface of

the TDM-LIC card protection group Check line cables.
TDM-LIC card protection switch member; Enable the TDM-LIC card protection
2044 Event Warning
over, priority A TDM-LIC card protection group group member or insert the
member was disabled or pulled out missing card into the shelf.
of the shelf

Timing not configured correctly.

Correct the timing configuration.
End-to-end timing is not
Correct the end-to-end timing
synchronized.
Loss Of Pointer (LOP) received problem.
2045 Alarm Minor External Equipment is faulty.
on TDM-LIC VC12/VT1.5 Check the external equipment.
Network service connectivity
Fix the network service problem.
problem.
Fix the interface and card problem.
Lower layer problem.

Path protection switch on TDM Failure along service primary path. Check errors along primary path
2046 Event Minor
service User command. Check local service configuration.

Primary path has been operational

Path protection revertive
2047 Event Minor for the duration of the defined WTR -
switch on TDM service
time

Reconnect line.
Loss of Signal on Line Interface Line is not properly connected.
2100 Alarm Critical Check line cables.
(LOS) on STM-1/OC-3 port. External equipment is faulty.
Check external equipment.

Reconnect line.
Loss of Frame on Line Interface Line is not properly connected.
2101 Alarm Major Check line cables.
(LOF) on STM-1/OC-3 port. External equipment is faulty.
Check external equipment.

Phn 3963 013v000

Page 900
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Alarm Indication Signal on Line Reconnect line.

Line is not properly connected.
2102 Alarm Interface (MS-AIS/AIS-L) Minor Check line cables.
External equipment is faulty.
received. Check external equipment.

Remote Defect Indication on Reconnect line.

2103 Alarm Line Interface (MS-RDI/RDI-L) Minor External equipment is faulty. Check line cables.
received. Check external equipment.

All channels in Multi Carrier ABC

Check link performance.
Loss of STM-1/OC-3 Frame on group are down.
2104 Alarm Major Check radio alarms for channel.
Radio Interface. Incorrect configuration on remote
Check configuration.
side.

Remote STM-1/OC-3 signal is missing

(LOS/LOF/MS-AIS/AIS-L on remote
MS-AIS/AIS-L on Radio STM-1/OC-3 interface).
2105 Alarm Minor Check remote equipment.
Interface detected. STM-1/OC-3 Channel removed due
to reduced radio capacity on remote
side.

MS-RDI/RDI-L on Radio
2106 Alarm Minor External equipment is faulty. Check remote equipment.
Interface detected.

2107 Alarm STM-1/OC-3 Loopback Warning Looping. Remove looping.

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2108 Alarm alarm (due to reduced radio Warning
Fading Check radio alarms for channel.
capacity).

2109 Alarm PRBS insertion. Warning PRBS insertion on STM-1/OC-3 card. Remove PRBS insertion.

SFP is not properly installed. Install SFP properly.

2110 Alarm SFP absent in STM-1/OC-3 port. Critical
SFP is faulty. Replace the card.

Phn 3963 013v000

Page 901
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Replace SFP or insert SFP if it is not

SFP Transmit Failure on STM-
2111 Alarm Critical SFP is faulty. inserted correctly.
1/OC-3 port.
Replace the card.

SFP is muted on STM-1/OC-3

2112 Alarm Warning SFP is muted by configuration. Remove muting.
port.

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2113 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2114 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2115 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2116 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2117 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2118 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

STM-1/OC-3 Channel Removed

Reduced capacity. Check link performance.
2119 Alarm alarm (due to reduced radio Warning
Fading. Check radio alarms for channel.
capacity).

Phn 3963 013v000

Page 902
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

LOS alarm on an STM-1/OC-3

interface.
STM-1/OC-3 Group protection Check line cables.
2120 Event Warning STM1-OC3 Group protection group
switchover Check external equipment.
member was disabled or pulled out
of the shelf.

Check link performance on all radio

channels in Multi Carrier ABC
group.
All channels in Multi Carrier ABC
2200 Alarm Multi Carrier ABC LOF. Critical Check radio alarms for channels in
group are down.
Multi Carrier ABC group.
Check configuration of Multi
Carrier ABC group.

Check link performance on all radio

One of the radio channels in the channels in Multi Carrier ABC group
Multi Carrier ABC group has a lower Check radio alarms for channels in
Multi Carrier ABC bandwidth is
2201 Alarm Major capacity than expected Multi Carrier ABC group
below the threshold
Minimum bandwidth threshold Check configuration of Multi
configuration is wrong Carrier ABC group Minimum
bandwidth threshold

Replace RMC.
Hardware failure between RMC and
2203 Alarm LVDS RX Error Slot 2. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2204 Alarm LVDS RX Error Slot 3. Major Replace TCC.
TCC cards.
Replace chassis.

Phn 3963 013v000

Page 903
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Replace RMC.
Hardware failure between RMC and
2205 Alarm LVDS RX Error Slot 4. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2206 Alarm LVDS RX Error Slot 5. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2207 Alarm LVDS RX Error Slot 6. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2208 Alarm LVDS RX Error Slot 7. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2209 Alarm LVDS RX Error Slot 8. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2210 Alarm LVDS RX Error Slot 9. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2211 Alarm LVDS RX Error Slot 10. Major Replace TCC.
TCC cards.
Replace chassis.

Replace RMC.
Hardware failure between RMC and
2212 Alarm LVDS RX Error Slot 12. Major Replace TCC.
TCC cards.
Replace chassis.

Phn 3963 013v000

Page 904
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

MC-ABC member has been Major The corresponding MC-ABC member Verify the proper functioning and
2213 Alarm disabled due to robustness has been temporarily disabled within connectivity of the cable and RF
reason the group. It was caused by unit.
consecutive RFU HW failures

Multi Carrier ABC Channel Id Compare Channel ID configuration

2219 Alarm Warning Configuration failure.
Mismatch Ch1. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2220 Alarm Warning Configuration failure.
Mismatch Ch2. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2221 Alarm Warning Configuration failure.
Mismatch Ch3. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2222 Alarm Warning Configuration failure.
Mismatch Ch4. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2223 Alarm Warning Configuration failure.
Mismatch Ch5. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2224 Alarm Warning Configuration failure.
Mismatch Ch6. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2225 Alarm Warning Configuration failure.
Mismatch Ch7. with remote side.

Multi Carrier ABC Channel Id Compare Channel ID configuration

2226 Alarm Warning Configuration failure.
Mismatch Ch8. with remote side.

Multi Carrier ABC Channel Id

2235 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch1.

Multi Carrier ABC Channel Id

2236 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch2.

Multi Carrier ABC Channel Id

2237 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch3.

Phn 3963 013v000

Page 905
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Multi Carrier ABC Channel Id

2238 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch4.

Multi Carrier ABC Channel Id

2239 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch5.

Multi Carrier ABC Channel Id

2240 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch6.

Multi Carrier ABC Channel Id

2241 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch7.

Multi Carrier ABC Channel Id

2242 Alarm Warning Admin state for channel is down. Enable admin state for channel.
Manual Disabled Ch8.

Check link performance on all

channels in Enhanced Multi Carrier
ABC group.
Enhanced Multi Carrier ABC All channels in Enhanced Multi
2250 Alarm Critical Check alarms for channels in
LOF Carrier ABC group are down
Enhanced Multi Carrier ABC group.
Check configuration of Enhanced
Multi Carrier ABC group.

Apply copy-to-mate command to

Protection configuration The configuration between the
2300 Alarm Major copy the configuration from the
mismatch! protected devices is not aligned.
required device to the other one.

The copy-to-mate command has just

2301 Event Copy to mate started Indeterminate This is a notification
begun!

The copy-to-mate command was

2302 Event Copy to mate completed Indeterminate This is a notification
completed.

User issued a command to reset the Wait until the reset cycle is ended
3000 Event Chassis was reset Warning
chassis. and the system is up and running.

Phn 3963 013v000

Page 906
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Front panel Ethernet ports cannot

Reset chassis to activate front
3001 Alarm Warning work when slot 12 is configured in Reset chassis.
panel Ethernet ports
10Gbps mode.

Front panel Ethernet port

Front panel Ethernet port cannot Configure the relevant capacity
3002 Alarm cannot function in current Warning
work in a mode other than 1Gbps. mode to 1 Gbps mode.
configured capacity mode

Multi Carrier ABC group is not Multi Carrier ABC group does not
Configure the relevant capacity
3003 Alarm functional in current configured Warning support the configured capacity
mode to 1 Gbps mode.
capacity mode mode.

Multi Carrier ABC group is not

Multi Carrier ABC group capacity
functional in current configured
3004 Alarm Warning mode is different than the Reset chassis.
capacity mode until chassis is
configured capacity mode.
reset

Card has one or more HW

4000 Alarm Critical One or more HW faults. Replace card.
failures

Card cannot function in The user set an expected card that

4001 Alarm Warning Change the Slot Section to 1Gbps.
2.5Gbps mode. does not support 2.5Gbps.

Card is not functional until

4002 Alarm Warning Slot is not in 10Gbps mode. Reset chassis.
chassis is reset

User blocked due to User blocked due to consecutive The user should wait few minutes
5000 Event Indeterminate
consecutive failure login failure login until it account will be unblock

ERPI is either in protection Either user "force switch" command Either clear force command or
5001 Alarm Minor
state or forced protection state or one of the ring links has failed recover the link

More than a single RPL is

5002 Alarm Warning RPL configuration is wrong. Reconfigure the RPL configuration.
configured in a ring

5003 Event LLDP topology change Warning New neighbor None

Phn 3963 013v000

Page 907
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

5004 Event Security log upload started Indeterminate Security log upload started

5005 Event Security log upload failed Indeterminate Security log upload failed

5006 Event Security log upload succeeded Indeterminate Security log upload succeeded

System is in sync force mode

5010 Alarm Warning User command
state

The sync-source quality level

5011 Event Major
was changed

System Synchronization Active Sync Source Failure and the Fix the Sync Source Failure.
5012 Alarm Critical
Reference in Holdover Mode clock unit enters holdover mode Provide an alternative sync source.

System sync reference T0

5013 Event Major
quality has changed

Set the outgoing clock source type

to System Clock in the Outgoing
The pipe interface clock-source For interfaces of a Pipe, the
Clock Table via Outgoing Clock view
5014 Alarm in signal-interface table is not Major outgoing clock source type must be
in the Web EMS or the platform
system-clock "System Clock".
sync interface config command in
the CLI.

The pipe is missing an edge Pipe Regenerator contains less than Configure a second interface for
5015 Alarm Major
interface 2 interfaces. the Pipe Regenerator.

Check both interfaces of the pipe

regenerator - admin and
Pipe interface operational state One or both of the Regenerator operational statuses.
5016 Alarm Major
is down Interfaces status is down. Check Ethernet cable
communication.
Make sure Radio Link is up.

Phn 3963 013v000

Page 908
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Fix the Pipe Regenerator

Pipe Regenerator configuration is
configuration.
5017 Alarm Pipe is invalid Major invalid or interface operational
Ensure both interfaces are
failure.
operational.

5018 Alarm 1588TC is not operational Major System Failure Reboot the unit

Check that the radio link

configuration have:

1588TC over the radio is not 1588TC over the radio is enabled but TC enabled on both sides
5019 Alarm Major
calibrated could not be calibrated Frequency lock UP on both sides
TC downstream at one side and
upstream on the other side

T3 Interface is configured in
5020 Alarm T3 interface at loopback mode Warning If required, disable the loopback.
loopback.

T4 Interface is configured in
5021 Alarm T4 interface at loopback mode Warning If required, disable the loopback.
loopback.

Security rsa key download Security rsa key download failed

5022 Event Indeterminate
failed

Security rsa key download Security rsa key download started

5023 Event Indeterminate
started

Security rsa key download Security rsa key download

5024 Event Indeterminate
succeeded succeeded

5025 Event Security rsa key install failed Indeterminate Security rsa key install failed

5026 Event Security rsa key install started Indeterminate Security rsa key install started

Security rsa key install Security rsa key download

5027 Event Indeterminate
succeeded succeeded

Phn 3963 013v000

Page 909
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

A connectivity failure in
5030 Alarm Minor Wrong link configurations. Check the link in the traffic path
MA/MEG

Check the links along the traffic

Invalid CCMs has been received.
path.
5031 Alarm Error CCM received Major MEP Id does not exist or a wrong
Check the configuration of the
interval was received in the CCM.
MEPs.

Remote mep MAC status not Remote MEP’s associated MAC is

5032 Alarm Minor Check remote Port Interface status
up reporting an error status

Check the SOAM configurations.

Remote Defect indication has been Check that all local MEPs are
5033 Alarm Mep Rdi received Minor
received from remote MEP configured correctly and enabled.
Check the service connectivity.

Check all the remote SOAM

configurations.
Remote mep CCMs are not The MEP is not receiving CCMs from
5034 Alarm Major Check that all remote MEPs are
received at least one of the remote MEPs
configured correctly and enabled.
Check the service connectivity.

CCM from another MAID or lower Check MA/MEG and MEP

5035 Alarm Cross Connect CCM received Major
MEG level have been received configurations

5036 Event 1588-BC port state changed Warning

1588-BC BMCA has been

5037 Event Warning
updated.

5038 Event 1588-BC outputs are squelched. Warning

1588-BC parent dataset has

5039 Event Warning
changed.

Phn 3963 013v000

Page 910
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

1588-BC UTC offset value

5040 Event Warning
changed.

1588-BC one of the leap

5041 Event Warning
seconds flags have changed.

1588-BC message interval

5042 Event Warning
change detected.

1588-BC announce message Check the message rate

5043 Alarm Major Misconfiguration of the peer system.
rate is below expected. configuration of the peer system.

1588-BC sync message rate is Check the message rate

5044 Alarm Major Misconfiguration of the peer system.
below expected. configuration of the peer system.

1588-BC delay request message Check the message rate

5045 Alarm Major Misconfiguration of the peer system.
rate is below expected. configuration of the peer system.

1588-BC performance is Restore the system clock

5046 Alarm degraded due to loss of system Critical Loss of system clock reference. synchronization to a PRC-traceable
clock reference. source.

Auto-state-propagation Remote system triggered auto-state- Resolve the problem on the

5047 Alarm Major
indication received propagation .remote system.

Auto state propagation Remote system triggered Auto state Resolve the problem on the remote
5048 Alarm Major
indication received propagation system

Master key mismatch cross

5100 Alarm Critical Master Key was not set correctly. Verify the Master Key.
over the link

No Master Key set, default Crypto module has been enabled,

5101 Alarm Warning Set the Master Key.
value used but no Master Key has been loaded.

Phn 3963 013v000

Page 911
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Validate the MSE on both sides of

Radio LOF on Tx/Rx direction.
the link.
The session key does not match
Validate the session key on both
5102 Alarm Payload Encryption failure Critical across the link.
sides of the link.
The AES admin setting does not
Validate the AES admin setting on
match across the link.
both sides of the link.

Key Exchange Protocol in

5104 Event progress, Traffic has been Indeterminate
blocked

Key Exchange Protocol initiated

5105 Event Indeterminate
by remote side

5107 Alarm FIPS Bypass Self-Test failed Critical Disk failure

Reboot the unit.

5108 Alarm Power On Self-Test Failed Critical System failure Check for faults.
Replace unit

5109 Alarm Main Board is not FIPS certified Critical Main Board used is not FIPS certified Use a FIPS-certified TCC.

5110 Alarm Radio card is not FIPS certified Major Radio Card used is not FIPS certified Use a FIPS-certified RMC.

Use different FIPS supported radio

5111 Alarm Radio crypto module fail Critical FIPS Radio Encryption Self-Test failed
card

No Payload Encryption Activation Insert suitable Activation Key and

5112 Alarm Radio Encryption not supported Major
Key inserted reboot the unit

Protection Pre-Shared-Key has Protection Pre-shared key was not Configure the Pre-shared key to a
5113 Alarm Major
the default value configured different value than the default

Security certificate download Security certificate download

5132 Event Indeterminate N/A
succeeded succeeded

Phn 3963 013v000

Page 912
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Security certificate download

5133 Event Indeterminate Security certificate download failed N/A
failed

Security certificate download

5134 Event Indeterminate Security certificate download started N/A
started

5222 Event Security CSR upload succeeded Indeterminate Security csr upload succeeded N/A

5223 Event Security CSR upload failed Indeterminate Security csr upload failed N/A

5224 Event Security CSR upload started Indeterminate Security csr upload started N/A

Try re-initiation of MIMO. If still

Faulty coaxial cable between master
fails:
and slave RFUs.
30007 Event Clock source sharing failure Critical Replace faulty coaxial cable and
Hardware failure in Master RFU.
reset Master RFU.
Hardware failure in Slave RFU.
Replace faulty RFU.

Make sure all cables between

master and slave are connected
Insufficient conditions for Insufficient conditions for MIMO.
31000 Alarm Critical (4x4 MIMO only).
MIMO Hardware failure.
Replace faulty units and check that
cables are plugged.

Unsuitable hardware for MIMO

operation requirements.
Dual carrier RFUs (2x2 and 4x4
MIMO). Make sure both RFUs are
31003 Alarm Unsuitable hardware for MIMO Critical
RFUs with MIMO bus interface (4x4 compatible for MIMO operation.
MIMO).
Clock source sharing capability (4x4
MIMO).

Phn 3963 013v000

Page 913
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Not all MIMO carriers are set to

Load same MIMO compatible radio
same radio script or script is not
script to all MIMO carriers.
compatible for MIMO.
Unsuitable software Set same TX and RX frequency on
31004 Alarm Critical Radio TX and RX frequency is not
configuration for MIMO all MIMO carriers.
identical on all MIMO carriers.
Disable XPIC, Multi radio and ATPC
XPIC or Multi radio or ATPC features
on all MIMO carriers.
are enabled.

Faulty coaxial cable between master Replace faulty coaxial cable and
Clock source sharing cable
31005 Alarm Critical and slave RFUs reset Master RFU.
unplugged
Mate does not exist Replace faulty RFU.

Radio script is incompatible to MRMC Script selected does not Set AFR Script in both Agg1 & Agg2
31100 Alarm Critical
AMCC support AMCC Group type/subtype carriers

Inconsistent MRMC script All members of a group must be Set the members to the
31101 Alarm Critical
between members configured to the same MRMC Script appropriate MRMC script

Radio TX/RX frequency is not Set same radio TX/RX frequency on

31102 Alarm Inconsistent radio frequency Critical
identical on all AMCC carriers all AMCC carriers

Agg1 did not complete Bring-up Drop both Agg1 & Agg2 into single
31103 Alarm Agg 1 failed Bring-up procedure Critical
successfully carrier mode (Pre-Init)

AMCC member have been set to Set AMCC member to adaptive

31104 Alarm Invalid ACM configuration Critical
fixed profile ACM profiles

Phn 3963 013v000

Page 914
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

MIMO script is not enabled on any Align MIMO script on all radio
radio member. members.
Different TX/RX frequency. Align same frequency on all radio
ATPC enabled. members.
AMCC/MIMO insufficient
31105 Alarm condition – configuration is not Critical XPIC enabled. Disable ATPC.
supported ACM mode (adaptive/Fixed) is not Disable XPIC.
the same. Align ACM mode.
Unit Redundancy enabled. Disable Unit Redundancy.
Platform not supported. Replace unit.

AMCC insufficient condition – Verify Master unit power.

31106 Alarm Critical Master unit failure.
Master unit failure. Replace hardware.

AMCC insufficient condition – Verify Slave unit power.

31107 Alarm Critical Slave unit failure.
Slave unit failure. Replace hardware.

Verify Data sharing cable

AMCC insufficient condition –
31108 Alarm Critical Data sharing cable failure. connected.
Data sharing cable failure.
Replace Data sharing cable.

Verify Mate communication cable

MIMO insufficient condition –
connected.
31109 Alarm Mate communication cable Critical Mate communication cable failure.
Replace Mate communication
failure.
cable.

Verify Source sharing cable

MIMO insufficient condition –
31110 Alarm Critical Source sharing cable failure. connected.
Source sharing cable failure.
Replace Source sharing cable.

Phn 3963 013v000

Page 915
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Master/Slave configuration
mismatch due to:
MIMO insufficient condition -
Different TX/RX frequency.
31111 Alarm Master/Slave configuration Critical Align Master/Slave configuration.
Different MIMO script ID.
mismatch
Different ACM mode
(adaptive/Fixed).

AMCC insufficient condition –

31112 Alarm Critical AMCC remote failure. Handle AMCC remote failure.
Remote failure

Align ASD script on all radio

ASD script is not enabled on any
members.
radio member.
Align same frequency on all radio
Different TX/RX frequency.
members.
AMCC/ASD insufficient ATPC enabled.
Disable ATPC.
31113 Alarm condition - configuration is not Critical XPIC enabled.
Disable XPIC.
supported ACM mode is not adaptive on any
Set ACM mode to adaptive on all
radio member.
radio members.
Unit Redundancy enabled.
Disable Unit Redundancy.
Platform not supported.
Replace platform.

SD script is not enabled on any radio Align SD script on all radio

member. members.
Different TX/RX frequency. Align same frequency on all radio
ATPC enabled. members.
AMCC/SD insufficient condition
31114 Alarm Critical
- configuration is not supported XPIC enabled. Disable ATPC.

ACM mode (adaptive/Fixed) is not Disable XPIC.

the same. Align ACM mode.
RFU not supported. Replace RFU.

Phn 3963 013v000

Page 916
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

Verify Source sharing cable

connected.
Replace Source sharing cable.
AMCC insufficient condition
31115 Alarm Critical Units alignment failure Verify Data sharing cable
Units alignment failure
connected.
Replace Data sharing cable.
Verify using correct SFPs.

XPIC configuration is not

31118 Alarm Critical XPIC MRMC script is not configured Set XPIC MRMC Script
supported

XPIC configuration failure in

31119 Alarm Warning XPIC remote failure Handle XPIC remote failure
remote

XPIC communication with mate Warning 1. The mate unit is 1. Check the cable between
unreachable. the two units.
unit is interrupted
2. In FIPS mode, possible 2. In FIPS mode, make sure
31120 Alarm mismatch between the that the same IPSec pre-
IPSec pre-shared keys shared key is configured
configured on the two on the two units.
units.

AMCC insufficient condition - Critical Radio Unit failure. 1. Verify radio unit power.
31121 Alarm
Radio unit failure. 2. Replace HW.

System Power Voltage lower than

32000 Alarm Under voltage Major
allowed.

System Power Voltage higher than

32001 Alarm Over voltage Major
allowed.

Phn 3963 013v000

Page 917
 Chapter 24: Alarms List PoE Injector LEDs

Alarm ID Type Description Severity Probable Cause Corrective Action Notes

System Temperature not in

32002 Alarm Major
allowed range.

User issued a command to reset the Wait until the reset cycle is ended
32003 Event Unit was reset. Warning
unit and the system is up and running

Anti-Theft Procedures have

33001 Event Indeterminate
been enabled

Anti-Theft Procedures have

33002 Event Indeterminate
been temporary disabled

Anti-Theft Sanction Mode 24 Return the equipment to the

33003 Alarm hours window has been Critical Watchdog timer countdown network
triggered

Return the equipment to the

Anti-Theft Sanction Mode is Equipment has been stolen
33004 Alarm Critical network
Active

Supported by PTP 820C and PTP 820S

(1) Supported by PTP 820C only

Phn 3963 013v000

Page 918
Glossary

Term Definition

ABC Adaptive Bandwidth Control

ABN Adaptive Bandwidth Notification

AC Alternating Current

ACAP Adjacent Channel Alternate Polarization

ACCP Adjacent Channel Co-Polarization

ACM Adaptive Coded Modulation

ACR Adaptive Clock Recovery

AES Advanced Encryption Standard

AFR Advanced Frequency Reuse

AGC Automatic Gain Control

AIS Alarm Indicating Signal

ALC Automatic Level Control

AMCC Advanced Multi-Carrier Configuration

ANSI American National Standards Institute

ARP Address Resolution Protocol

ASD Advanced Space Diversity

ASIC Application Specified Integrated Circuit

ASP Automatic State Propagation

AT Anti-Theft

ATPC Automatic Transmit Power Control

AUX Auxiliary Unit

BB Baseband

BBS Baseband Switching

BER Bit Error Rate

Phn 3963 013v000

Page I
Term Definition

BLSR Bidirectional Line Switch Ring

BNM Bandwidth Notification Message

BPDU Bridge Protocol Data Units

BWA Broadband Wireless Access

CBS Committed Burst Size

CCDP Co-Channel Dual Polarization

CCITT Comité Consultatif International de Télégraph et des Télécommunications (ITU)

CET Carrier-Ethernet Transport

CFM Connectivity Fault Management

CIR Committed Information Rate

CLI Command Line Interface

Clk Clock

CODEC Coder/Decoder

CoS Class of Service

DA Destination Address

DC Direct Current

DCB Diversity Circulator Block

DCC Data Communication Channel

DDM Digital Diagnostic Monitoring

DXC Digital Cross Connect

DSCP Differentiated Services Code Point

EBS Excess Burst Size

EIR Excess Information Rate

EMC Electromagnetic Compatibility

EOW Engineering Order Wire

EPROM Erasable Programmable Read Only Memory

ERPS G.8032 Ethernet Ring Protection Switching

Phn 3963 013v000

Page II
Term Definition

ESD Electrostatic Discharge

ESE Electrical SFP Electrical

ESP Electrical SFP SFP+ 10G

ESP Encapsulating Security Payload

ESS Electrical SFP SFP

ETH-BN Ethernet Bandwidth Notification

ETSI European Telecommunications Standards Institute

FCC Federal Communications Commission

FCS Frame Check Sequence

FTP File Transfer Protocol

GARP Gratuitous ARP

GbE Gigabit Ethernet

GFP Generic Framing Procedure

(Procedure for mapping of Ethernet traffic over a transport network)

GND Ground

GRE Generic Routing Encapsulation

GTP GPRS Tunneling Protocol

HBER High Bit Error Rate

HDLC High-level Data Link Control

HF High Frequency (3-30 MHz)

HSB Hot-Standby

HTTP Hypertext Transfer Protocol

HTTPS Secured Hypertext Transfer Protocol

IDC Indoor Controller

IF Intermediate Frequency

IFC IF Combining

Phn 3963 013v000

Page III
Term Definition

IPsec Internet Security Protocol

ISO International Organization for Standardization

ITU International Telecom. Union

ITU-R International Telecom. Union (former CCIR)

ITU-T International Telecom. Union (former CCITT)

IVM Inventory Module

LACP Link Aggregation Control Protocol

LAG Link Aggregation Group

LAN Local Area Network

LBER Low Bit Error Rate

LCAS Link Capacity Adjustment Scheme

LED Light Emitting Diode

LIU Line Interface Unit

LLDP Link Layer Discovery Protocol

LLF Link Loss Forwarding

LMS License Management System

LO Local Oscillator

LOC Loss of Carrier

LOF Loss of Frame

LOS Loss of Signal

LSI Large Scale Integration

LTE Long-Term Evolution

MAID Maintenance Association Identifier

MPLS Multi Protocol Label Switching

MA-ASP Management Safe Automatic State Propagation

MSTI MSTP Instance

MSP Multiplex Section Protection

MSTP Multiple Spanning Tree Protocol

Phn 3963 013v000

Page IV
Term Definition

MUX Multiplexer

NE Network Element

NMS Network Management System

NTP Network Time Protocol

OAM Operation Administration & Maintenance (Protocols)

OCB Outdoor Circulator Box

OHC OverHead Connections

OMT Orthogonal Mode Transducer

OOF Out of Frame

OPEX Operational Expenditure

PBB-TE Provider Backbone Bridge Traffic Engineering

PBS Peak Burst Rate

PC Personal Computer

PCB Printed Circuit Board

PDV Packed Delay Variation

PIR Peak Information Rate

PLL Phase Locked Loop

PM Performance Monitoring

PN Provider Network

PROM Programmable Read Only Memory

PSN Packet Switched Network

PTP Precision Timing Protocol

PWR Power

QoE Quality of Experience

QoS Quality of Service

Phn 3963 013v000

Page V
Term Definition

RBAC Role Based Access Control

RCVR Receiver

RDI Reverse Defect Indication

RF Radio Frequency

RIP Routing Information Protocol

RMON Ethernet Statistics

RPS Radio Protection Switching

RSA Rivest–Shamir–Adleman public-key cryptosystem

RSL Received Signal Level

RSSI Received Signal Strength Indicator

RSTP Rapid Spanning Tree Protocol

SAP Service Access Point

SDH Synchronous Digital Hierarchy

SDWRR Shaped Deficit Weighted Round Robin

SETS Synchronous Equipment Timing Source

SFTP Secure FTP

SLA Service Level Agreements

SNCP Simple Network Connection Protection

SNMP Simple Network Management Protocol

SNP Service Network Point

SNR Signal to Noise Ratio

SNTP Simple Network Time Protocol

SOH Section OverHead (ETSI)

SONET Synchronous Optical NETwork

SP Service Point

SSH Secured Shell (Protocol)

SSM Synchronization Status Message

STP Spanning Tree Protocol

SyncE Synchronous Ethernet

Phn 3963 013v000

Page VI
Term Definition

SVCE Service Channel Equipment

TC Traffic Class

TIM Trace Identifier Mismatch

TOH Transport OverHead (ANSI)

TOS Type Of Service

VC Virtual Container

VCO Voltage Controlled Oscillator

VCXO Voltage Controlled crystal Oscillator

VLSI Very Large Scale of Integration

WAN Wide Area Network

Web EMS Web-Based Element Management System

WFQ Weighted Fair Queue

WG Waveguide

WRED Weighted Random Early Detection

WRR Weighted Round Robin

XCVR Transceiver (Transmitter/Receiver)

XMTR Transmitter

XO Crystal Oscillator

XPD Cross Polar Differentiation

XPIC Cross Polarization Interference Cancellation

Phn 3963 013v000

Page VII