WebEMS UserGuide RevB

TM
Evo XPAND IP+
Web Element Management

System (EMS)
User Guide

The information in this documentation is subject to change without notice and describes
only the product defined in the introduction of this documentation. This documentation is
intended for the use of Nera's customers only for the purposes of the agreement under
which the documentation is submitted, and no part of it may be reproduced or
transmitted in any form or means without the prior written permission of Nera.
The information or statements given in this documentation concerning the suitability,

capacity, or performance of the mentioned hardware or software products cannot be
considered binding but shall be defined in the agreement made between Nera and the
customer. However, Nera has made all reasonable efforts to ensure that the instructions
contained in the documentation are adequate and free of material errors and omissions.
Nera will, if necessary, explain issues that may not be covered by the documentation.
Nera's liability for any errors in the documentation is limited to the documentary correction
of errors.
NERA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR
FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES),
that might arise from the use of this documentation or the information in it. This
documentation and the product it describes are considered protected by copyright
according to the applicable laws.
EvoTM is a registered trademark of Nera Networks Singapore. Other product names

mentioned in this documentation may be trademarks of their respective companies, and
they are mentioned for identification purposes only.
Copyright © Nera Networks Singapore 2011. All rights reserved.

2 of 264 Web Element Management System (EMS) User Guide

Document History

Revision Date Summary of changes
Rev. A 03‐11‐2011 Initial Version
Rev. B 12‐04‐2012 Template Updated

Web Element Management System (EMS) User Guide 3 of 264

Table of Contents
1. GETTING STARTED ...................................................................................................................................... 11
1.1 LOGGING IN ..................................................................................................................................................... 11
1.2 SELECTING A SLOT ........................................................................................................................................ 11
1.2.1 MAIN VIEW EXAMPLES .............................................................................................................................. 12
1.2.2 AVAILABLE INTERFACES .......................................................................................................................... 13
1.3 BROWSER BEHAVIOR ................................................................................................................................... 14
2. QUICK REFERENCE ..................................................................................................................................... 15
2.1 FAULTS ............................................................................................................................................................. 15
2.1.1 CURRENT ALARMS ..................................................................................................................................... 15
2.1.2 EVENT LOG ................................................................................................................................................... 15
2.2 PMS & COUNTERS .......................................................................................................................................... 16
2.2.1 PM COMMANDS ........................................................................................................................................... 16
2.2.2 RMON COUNTERS ........................................................................................................................................ 16
2.2.3 TDM TRAILS .................................................................................................................................................. 17
2.2.4 ENHANCED TRAFFIC MANAGER ............................................................................................................. 17
2.2.5 E1 ..................................................................................................................................................................... 18
2.2.6 DS1 .................................................................................................................................................................. 19
2.2.7 STM1 ............................................................................................................................................................... 19
2.2.8 RADIO ............................................................................................................................................................. 20
2.3 CONFIGURATION ........................................................................................................................................... 25
2.3.1 GENERAL ....................................................................................................................................................... 25
2.3.2 ETHERNET SWITCH ..................................................................................................................................... 33
2.3.3 RADIO ............................................................................................................................................................. 38
2.3.4 INTERFACES.................................................................................................................................................. 43
2.3.5 PROTECTION ................................................................................................................................................. 51
2.3.6 TRAILS ............................................................................................................................................................ 53
2.4 SERVICE OAM ................................................................................................................................................. 54
2.4.1 MAID LIST...................................................................................................................................................... 54
2.4.2 MEP AND MIP LIST ...................................................................................................................................... 55
2.4.3 ADVANCED ................................................................................................................................................... 55
2.5 DIAGNOSTICS AND MAINTENANCE .......................................................................................................... 56
2.5.1 LOOPBACK .................................................................................................................................................... 56
2.5.2 CONFIGURATION MANAGEMENT ........................................................................................................... 58
2.5.3 SOFTWARE MANAGEMENT....................................................................................................................... 59
2.5.4 ODU DOWNLOAD......................................................................................................................................... 60
2.5.5 IFU-ODU INTERFACE MONITORING ........................................................................................................ 60

2.5.6 RESETS ........................................................................................................................................................... 61
2.5.7 FILE LIST ........................................................................................................................................................ 61
2.6 SECURITY ......................................................................................................................................................... 63
2.6.1 SECURITY CONFIGURATION..................................................................................................................... 63
2.6.2 USERS AND GROUPS ................................................................................................................................... 64
2.6.3 CSR FILE ......................................................................................................................................................... 64
2.6.4 CHANGE PASSWORD .................................................................................................................................. 65
3. SYSTEM ............................................................................................................................................................ 66
3.1 UNIT SYSTEM INFORMATION ..................................................................................................................... 66
3.2 SYSTEM DATE AND TIME............................................................................................................................. 67
3.2.1 CONFIGURING UNIT DATE AND TIME .................................................................................................... 67
3.2.2 CONFIGURING SYSTEM TIMING PROTOCOL (NTP) ............................................................................. 68
3.3 UNIT SERIAL AND PART NUMBERS ........................................................................................................... 69
3.4 LICENSING ....................................................................................................................................................... 70
3.4.1 VIEWING CURRENT LICENSE DETAILS .................................................................................................. 70
3.4.2 ENABLING LICENSED FEATURES ............................................................................................................ 70
3.4.3 WORKING WITH THE DEMO LICENSE .................................................................................................... 71
3.4.4 VIEWING LICENSED FEATURES ............................................................................................................... 71
3.4.5 VIEWING LICENSED USAGE ...................................................................................................................... 72
3.5 VIEWING SYSTEM APPLICATION FILES ................................................................................................... 73
4. FAULT MANAGEMENT................................................................................................................................ 74
4.1 CONFIGURING EXTERNAL ALARMS ......................................................................................................... 74
4.1.1 ALARM INPUT CONFIGURATION ............................................................................................................. 74
4.1.2 ALARM OUTPUT CONFIGURATION ......................................................................................................... 75
4.2 VIEWING CURRENT ALARMS ...................................................................................................................... 76
4.2.1 VIEWING ALARM DETAILS ....................................................................................................................... 76
4.3 VIEWING THE EVENT LOG ........................................................................................................................... 77
4.4 TRAPS CONFIGURATION .............................................................................................................................. 78
5. CONFIGURATION MANAGEMENT .......................................................................................................... 80
5.1 FTP ..................................................................................................................................................................... 80
5.1.1 CONFIGURING LOCAL FTP ........................................................................................................................ 80
5.1.2 CONFIGURING REMOTE FTP ..................................................................................................................... 81
5.2 UNIT INFO AND CONFIGURATION ARCHIVE MANAGEMENT ............................................................. 82
5.2.1 CREATING A UNIT INFORMATION ARCHIVE FILE .............................................................................. 83
5.2.2 UPLOADING A UNIT INFORMATION ARCHIVE FILE ........................................................................... 83
5.2.3 VIEWING UNIT INFORMATION ARCHIVE UPLOAD STATUS ............................................................. 83
5.2.4 BACKING UP UNIT ARCHIVES .................................................................................................................. 83
5.2.5 RESTORING UNIT ARCHIVES .................................................................................................................... 83
5.2.6 VIEWING ARCHIVE OPERATION STATUS .............................................................................................. 83

5.2.7 UPLOADING A CONFIGURATION ARCHIVE FILE ................................................................................. 84
5.2.8 VIEWING CONFIGURATION FILE UPLOAD STATUS ............................................................................ 84
5.2.9 DOWNLOADING A CONFIGURATION ARCHIVE FILE .......................................................................... 84
5.2.10 VIEWING CONFIGURATION FILE DOWNLOAD STATUS............................................................... 84
5.2.11 RESETS ..................................................................................................................................................... 84
5.3 SOFTWARE MANAGEMENT ......................................................................................................................... 86
5.3.1 IFU SOFTWARE MANAGEMENT ............................................................................................................... 86
5.3.2 ODU SOFTWARE MANAGEMENT ............................................................................................................. 90
6. PERFORMANCE MONITORING ................................................................................................................ 94
6.1 PM COMMANDS .............................................................................................................................................. 94
6.2 LINE PMS .......................................................................................................................................................... 96
6.2.1 E1 PMS ............................................................................................................................................................ 96
6.2.2 DS1 PMS.......................................................................................................................................................... 97
6.2.3 STM-1 PMS ..................................................................................................................................................... 98
6.3 RADIO PMS....................................................................................................................................................... 99
6.3.1 SIGNAL LEVEL PMS .................................................................................................................................... 99
6.3.2 AGGREGATE RADIO PMS ......................................................................................................................... 100
6.3.3 RADIO MRMC PMS ..................................................................................................................................... 101
6.3.4 RADIO MSE PMS ......................................................................................................................................... 102
6.3.5 RADIO XPI PMS ........................................................................................................................................... 103
6.4 TDM PMS ........................................................................................................................................................ 104
6.4.1 RADIO TDM CHANNEL PMS .................................................................................................................... 104
6.4.2 TDM TRAIL PMS ......................................................................................................................................... 105
6.5 ETHERNET STATISTICS............................................................................................................................... 106
6.5.1 FRAME ERROR RATE STATISTICS ......................................................................................................... 106
6.5.2 THROUGHPUT STATISTICS...................................................................................................................... 107
6.5.3 CAPACITY STATISTICS ............................................................................................................................. 108
6.5.4 UTILIZATION STATISTICS ....................................................................................................................... 109
6.5.5 ENHANCED TRAFFIC MANAGER STATISTICS .................................................................................... 110
6.5.6 RMON COUNTERS ...................................................................................................................................... 111
7. EQUIPMENT RESILIENCY ........................................................................................................................ 113
7.1 CONFIGURING THE PROTECTION TYPE ................................................................................................. 113
7.1.1 1+1 HSB PROTECTION ............................................................................................................................... 114
7.1.2 2+2 HSB PROTECTION ............................................................................................................................... 115
7.1.3 2+0 HSB PROTECTION ............................................................................................................................... 117
7.2 SPECIFYING ACTIVE AND STANDBY MODE.......................................................................................... 117
7.3 CONFIGURING SWITCHING CRITERIA .................................................................................................... 118
7.4 VIEWING MATE PARAMETERS ................................................................................................................. 119
7.5 MULTI-UNIT LAG.......................................................................................................................................... 120

8. RADIO FEATURES ....................................................................................................................................... 122
8.1 CONFIGURING RADIO PARAMETERS ...................................................................................................... 122
8.1.1 ENABLING AND DISABLING THE RADIO ............................................................................................. 122
8.1.2 SPECIFYING THE RADIO LINK ID ........................................................................................................... 122
8.1.3 CONFIGURING THE REMOTE RADIO IP ADDRESS ............................................................................. 123
8.2 FREQUENCY SETTINGS............................................................................................................................... 123
8.2.1 CONFIGURING TX AND RX FREQUENCIES .......................................................................................... 123
8.2.2 REMOTE RADIO FREQUENCY SETTINGS ............................................................................................. 124
8.2.3 ENABLING MAC HEADER COMPRESSION ........................................................................................... 125
8.2.4 ENABLING RSL DEGRADATION ALARMS............................................................................................ 126
8.3 MRMC SCRIPTS ............................................................................................................................................. 126
8.3.1 ASYMMETRIC SCRIPTS ............................................................................................................................ 127
8.3.2 REGULAR RADIO SCRIPTS....................................................................................................................... 128
8.3.3 ACM RADIO SCRIPTS ................................................................................................................................ 129
8.3.4 ACM ADAPTIVE POWER ........................................................................................................................... 130
8.3.5 ENABLING ALARMS ON MRMC PROFILE DEGRADATION ............................................................... 131
8.4 SETTING RADIO TRAFFIC PRIORITIES .................................................................................................... 132
8.5 POWER OPTIONS .......................................................................................................................................... 134
8.5.1 ATPC OVERRIDE ........................................................................................................................................ 134
8.5.2 GREEN MODE.............................................................................................................................................. 135
8.6 RADIO THRESHOLDS ................................................................................................................................... 136
8.6.1 RSL AND TSL THRESHOLDS .................................................................................................................... 136
8.6.2 MSE THRESHOLD ....................................................................................................................................... 137
8.6.3 XPI THRESHOLD......................................................................................................................................... 138
8.6.4 ETHERNET THROUGHPUT THRESHOLD............................................................................................... 138
8.6.5 ETHERNET CAPACITY THRESHOLD...................................................................................................... 138
8.6.6 ETHERNET UTILIZATION THRESHOLD ................................................................................................ 139
8.6.7 ETHERNET SHUTDOWN RX PROFILE THRESHOLD ........................................................................... 139
8.7 VIEWING RADIO STATUS ........................................................................................................................... 140
8.7.1 ODU STATUS ............................................................................................................................................... 140
8.7.2 MRMC STATUS ........................................................................................................................................... 141
8.7.3 CURRENT TX STATUS ............................................................................................................................... 142
8.7.4 CURRENT RX STATUS............................................................................................................................... 142
8.7.5 CURRENT REMOTE RX LEVEL................................................................................................................ 143
8.7.6 REMOTE RADIO STATUS .......................................................................................................................... 143
8.7.7 XPIC STATUS............................................................................................................................................... 144
8.8 MULTI CHANNEL ABC ................................................................................................................................ 144
8.8.1 ENABLING AND DISABLING MULTI CHANNEL ABC ......................................................................... 144
8.8.2 MULTI CHANNEL ABC TRAFFIC BLOCKING ....................................................................................... 145

8.8.3 SETTING MULTI CHANNEL ABC THRESHOLDS.................................................................................. 145
8.9 RADIO DIVERSITY........................................................................................................................................ 145
8.9.1 1+1 SPACE DIVERSITY .............................................................................................................................. 146
8.9.2 1+0 IF COMBINING DIVERSITY ............................................................................................................... 147
8.9.3 FREQUENCY DIVERSITY .......................................................................................................................... 150
9. INTERFACE CONFIGURATION ............................................................................................................... 152
9.1 LOCAL SYSTEM CONFIGURATION........................................................................................................... 152
9.1.1 IP CONFIGURATION .................................................................................................................................. 152
9.1.2 MANAGEMENT PORTS.............................................................................................................................. 153
9.2 NETWORK SYSTEM CONFIGURATION .................................................................................................... 154
9.3 AUXILIARY CHANNELS .............................................................................................................................. 156
9.3.1 WAYSIDE CHANNEL ................................................................................................................................. 156
9.3.2 USER CHANNEL ......................................................................................................................................... 157
9.3.3 EOW............................................................................................................................................................... 158
9.4 PORT CONFIGURATION .............................................................................................................................. 159
9.4.1 E1 PORTS ...................................................................................................................................................... 159
9.4.2 DS1 PORTS ................................................................................................................................................... 162
9.4.3 STM-1/OC-3 (T-CARD) PORTS .................................................................................................................. 164
9.5 ALL ODU ......................................................................................................................................................... 167
10. ETHERNET TRAFFIC ................................................................................................................................. 168
10.1 ETHERNET PORTS ........................................................................................................................................ 168
10.1.1 CONFIGURING ETHERNET PORTS ................................................................................................... 168
10.1.2 CONFIGURING AUTOMATIC STATE PROPAGATION ................................................................... 169
10.1.3 VIEWING ETHERNET PORT STATUS ............................................................................................... 171
10.2 LAG PORTS..................................................................................................................................................... 172
10.2.1 DEFINING A LAG PORT ...................................................................................................................... 172
10.3 CONFIGURING THE ETHERNET APPLICATION TYPE........................................................................... 176
10.3.1 SINGLE PIPE .......................................................................................................................................... 177
10.3.2 MANAGED SWITCH ............................................................................................................................. 177
10.3.3 METRO SWITCH ................................................................................................................................... 178
10.4 SWITCH CONFIGURATION ......................................................................................................................... 179
10.4.1 CHANGING THE ETHERNET APPLICATION TYPE ........................................................................ 179
10.4.2 CONFIGURING LAG LOAD BALANCING......................................................................................... 179
10.4.3 ASSIGNING PORT MEMBERSHIP ...................................................................................................... 180
10.5 RSTP................................................................................................................................................................. 181
10.5.1 CONFIGURING RSTP PRIORITY ........................................................................................................ 182
10.5.2 CONFIGURING ETHERNET PORTS TO SUPPORT RSTP ................................................................ 182
10.5.3 VIEWING RSTP STATUS ..................................................................................................................... 183
10.6 QOS AND RATE LIMITING .......................................................................................................................... 184

10.6.1 CONFIGURING PORT TRAFFIC PRIORITIES ................................................................................... 185
10.6.2 ADVANCED CLASSIFIER CONFIGURATION .................................................................................. 189
10.6.3 COPYING PORT PRIORITIES AND RATE LIMITING CONFIGURATION..................................... 197
10.7 ENHANCED TRAFFIC MANAGER .............................................................................................................. 197
10.7.1 PREPARING TO USE THE ENHANCED TRAFFIC MANAGER....................................................... 197
10.7.2 ENHANCED TRAFFIC MANAGER CLASSIFICATION .................................................................... 201
10.7.3 WRED ...................................................................................................................................................... 213
10.7.4 EGRESS SHAPER & SCHEDULER ...................................................................................................... 215
10.8 CFM (SERVICE OAM) ................................................................................................................................... 217
10.8.1 MAID LIST ............................................................................................................................................. 217
10.8.2 MEP & MIP LIST .................................................................................................................................... 226
10.8.3 PERFORMING MANUAL PING AND LINKTRACE OPERATIONS ................................................ 230
11. FREQUENCY SYNCHRONIZATION ........................................................................................................ 232
11.1 SYNCHRONIZATION INPUT AND OUTPUT INTERFACES .................................................................... 232
11.2 SYNCHRONIZATION SOURCES ................................................................................................................. 233
11.2.1 CONFIGURING SYSTEM SYNCHRONIZATION SOURCES............................................................ 233
11.2.2 CONFIGURING A SYNCHRONIZATION SOURCE REVERTIVE TIMER ...................................... 234
11.2.3 CONFIGURING PRC REGENERATOR MODE AND DIRECTION ................................................... 235
11.2.4 VIEWING CURRENT SYNCHRONIZATION SOURCES ................................................................... 235
11.3 CONFIGURING THE OUTGOING SIGNAL CLOCK .................................................................................. 236
11.3.1 CONFIGURING CLOCK SOURCES ..................................................................................................... 236
11.3.2 VIEWING SYNCHRONIZATION CLOCK SOURCES ........................................................................ 237
12. TDM TRAILS ................................................................................................................................................. 238
12.1 VIEWING THE TRAILS LIST ........................................................................................................................ 238
12.2 ADDING NEW TRAILS.................................................................................................................................. 239
12.3 ACTIVATING AND RESERVING TRAILS .................................................................................................. 241
12.4 CONFIGURING TRAIL OPERATIONAL STATUS ..................................................................................... 242
12.5 DELETING TRAILS........................................................................................................................................ 242
12.6 TDM TRAIL PATH PROTECTION (SNCP) .................................................................................................. 243
12.6.1 SNCP TRAIL CONFIGURATION ......................................................................................................... 243
12.6.2 SNCP SWITCHING CRITERIA ............................................................................................................. 243
12.7 TDM TRAILS AND CROSS-CONNECT ....................................................................................................... 244
12.7.1 XC TRAILS OVERVIEW ....................................................................................................................... 244
12.7.2 CROSS CONNECTION AT THE KLM LEVEL.................................................................................... 245
12.8 ALARM INDICATION SIGNAL (AIS) DETECTION AND SIGNALING .................................................. 246
13. SECURITY...................................................................................................................................................... 247
13.1 SECURITY CONFIGURATION ..................................................................................................................... 247
13.1.1 SECURING WEB ACCESS .................................................................................................................... 247
13.1.2 GENERATING CSR FILES .................................................................................................................... 248

13.1.3 GENERATING A SECURITY CERTIFICATE FROM A CSR FILE ................................................... 249
13.1.4 UPLOADING A PUBLIC KEY .............................................................................................................. 250
13.1.5 CONFIGURING THE SECURITY FILE NAME, TYPE AND FORMAT ............................................ 250
13.1.6 DOWNLOADING THE WEB SERVER AND CA CERTIFICATES.................................................... 251
13.1.7 ENABLING THE CA CERTIFICATE.................................................................................................... 252
13.1.8 CONFIGURING THE WEB PROTOCOL.............................................................................................. 252
13.2 SNMP ............................................................................................................................................................... 253
13.2.1 SETTING THE SNMP VERSION .......................................................................................................... 253
13.2.2 CONFIGURING SNMP READ/WRITE COMMUNITIES .................................................................... 253
13.2.3 CONFIGURING SNMPV3 SECURITY MODE .................................................................................... 254
13.2.4 CONFIGURING SNMPV3 AUTHENTICATION ................................................................................. 254
13.2.5 CONFIGURING SNMPV3 USER NAME AND PASSWORD ............................................................. 255
13.3 USER ACCESS CONTROL ............................................................................................................................ 255
13.3.1 ASSIGNING PRIVILEGES TO USERS................................................................................................. 255
13.3.2 CONFIGURING PASSWORD SECURITY ........................................................................................... 256
13.3.3 SUSPENDING INACTIVE USERS........................................................................................................ 257
13.4 USER MANAGEMENT .................................................................................................................................. 258
13.4.1 ADDING USERS .................................................................................................................................... 258
13.4.2 DELETING USERS ................................................................................................................................ 259
13.4.3 CHANGING USER PASSWORDS ........................................................................................................ 259
14. DIAGNOSTICS & MAINTENANCE........................................................................................................... 260
14.1 LOOPBACK ..................................................................................................................................................... 260
14.1.1 RADIO LOOPBACK .............................................................................................................................. 260
14.1.2 PDH LINE LOOPBACK ......................................................................................................................... 261
14.1.3 SDH LOOPBACK ................................................................................................................................... 262
14.2 IFU-ODU INTERFACE MONITORING ........................................................................................................ 263
15. APPENDIX...................................................................................................................................................... 264
15.1 FEATURE COMPATIBILITY CHART .......................................................................................................... 264


1. Getting started
1.1 Logging in
To start the web based management application:
1. Start your web browser.
2. Enter the URL of your Nera unit in the browser address bar, and press Enter to open the
Login window.
 The URL of your unit is http://yourIP, where yourIP is the IP address of the unit.
3. Enter your user name and password.
4. Click Apply to login.
1.2 Selecting a slot

After logging in, the Main view displays all of the unit’s populated slots.
Configuration and other operations are performed by clicking the menus on the left side of the page.
All operations will be performed on the selected slot, according to the available interfaces for each unit.
Note that for Multi Channel ABC configurations, protection, and extension units, available options will
vary according to the available interfaces and configured features for selected slot.
 For example, for units in Multi Channel ABC with TDM trails, you will only be able to configure
the trails from the Master unit.


1.2.1 Main view examples
Multi Channel ABC configuration
Single unit configuration


1.2.2 Available interfaces
1.2.2.1 Evo XPAND IP+
1.2.2.2 Evo XPAND IP+ Eth Only


1.3 Browser behavior
Evolution Web EMS doesn’t disable any innate browser functionality; however, some browser functions
will not function as expected.
 The browser’s Back button will load the page that was open before you logged into Evo Web
EMS.
Use Evo Web EMS’s navigation pane to select pages instead of the browser’s Back
button.
 Selecting Refresh from the browser’s menu or pressing F5 will not update the information on the
page; it will start a fresh Evo Web EMS session.
Use Evo Web EMS’s integrated Refresh buttons to update data changes.

2. Quick reference
2.1 Faults
2.1.1 Current alarms
To view current alarms:
Select Faults > Current alarms.
2.1.2 Event log

To view the event log:
Select Faults > Event log.


2.2 PMs & Counters
2.2.1 PM commands
To clear performance monitoring data:
Select PM & Counters > PM Commands.
2.2.2 RMON counters

To view and manage RMON counters:
Select PM & Counters >RMON.

2.2.3 TDM trails
To view TDM radio PM:
Select PM & counters > TDM trails.
2.2.4 Enhanced Traffic Manager

To view traffic statistics for a managed Ethernet queue:
Select PM & counters > Enhanced traffic manager > Queue#.

2.2.5 E1
To view E1 PM:
Select PM & counters > E1> Port#.


2.2.6 DS1
To view DS1 PM:
Select PM & counters > DS1> Port#.
2.2.7 STM1
Select PM & counters > STM‐1> Port#.

2.2.8 Radio
2.2.8.1 Signal level
To view signal level performance:
Select PM & counters > Radio> Signal level.
2.2.8.2 Aggregate
To view aggregate radio performance:
Select PM & counters > Radio > Aggregate.


2.2.8.3 MRMC
To view MRMC PM:
Select PM & counters > Radio > MRMC.
2.2.8.4 MSE
To view MSE PM:
Select PM & counters > Radio > MSE.


2.2.8.5 XPI
To view cross polarization interference performance:
Select PM & counters > Radio > XPI.
2.2.8.6 TDM channels

Select PM & counters > Radio > TDM channels > Channel#.

2.2.8.7 Ethernet
Frame error rate

To view Frame error rate performance:
Select PM & counters > Radio > Ethernet > Frame error rate.

Throughput
To view Throughput PM:
Select PM & counters > Radio > Ethernet > Throughput.


Capacity
To view Capacity PM:
Select PM & counters > Radio > Ethernet > Capacity.

Utilization
To view Ethernet utilization statistics:
Select PM & counters > Radio > Ethernet > Utilization.


2.3 Configuration
2.3.1 General
Unit parameters
To configure unit parameters:
Select Configuration > General > Unit parameters.


2.3.1.1 External alarms
To configure external alarms:
Select Configuration > General > External Alarms.


2.3.1.2 Management
To configure management settings:
Select Configuration > General > Management.
2.3.1.3 Traps configuration

To configure a trap manager
Select Configuration > General > Traps Configuration.


2.3.1.4 Licensing
To view current license information:
Select Configuration > General > Licensing.


2.3.1.5 NTP
To activate the NTP server:
Select Configuration > General > NTP.
2.3.1.6 IP table
To configure peer port settings:
Select Configuration > General > IP Table.


2.3.1.7 SNMP
To configure SNMP settings:
Select Configuration > General > SNMP.


2.3.1.8 All ODU
To enable All ODU support:
Select Configuration > General > All ODU.
2.3.1.9 Versions
IFU versions
To view IFU version information:

Select Configuration > General > Versions > IFU.

ODU versions
To view ODU version information:
Select Configuration > General > Versions > ODU.


2.3.2 Ethernet switch
2.3.2.1 Switch configuration
To con figure an Ethernet switch:
Select Configuration > Ethernet switch > Configuration.
2.3.2.2 STP protocol

To configure the STP protocol:
Select Configuration > Ethernet Switch> STP Protocol.

2.3.2.3 QoS and rate limiting
To configure Quality of service and traffic rate limiting:
Select Configuration > Ethernet Switch> QoS & rate limiting.


2.3.2.4 Enhanced traffic manager
Configuration and parameters

To enable the Enhanced Traffic Manager:
Select Configuration > Ethernet Switch> Enhanced Traffic Manager.


Classification
To enable Ethernet frames classification rules:
Select Configuration > Ethernet switch > Enhanced traffic manager > Classification.

WRED
To enable the Enhanced Traffic Manager’s WRED mechanism:
Select Configuration > Ethernet switch > Enhanced traffic manager > WRED.

Egress shaper and scheduler
To enable the enhanced egress shaping and scheduling:
Select Configuration > Ethernet switch > Enhanced traffic manager > Egress shaper
& scheduler.

2.3.3 Radio
2.3.3.1 Radio parameters
To configure radio setttings:
Select Configuration > Radio > Radio parameters.


2.3.3.2 Remote radio
To configure remote radio:
Select Radio > Remote radio.
2.3.3.3 Radio thresholds

To configure radio thresholds:
Select Radio > Radio thresholds.

2.3.3.4 MRMC
To configure MRMC scripts:
Select Configuration > Radio > MRMC.


2.3.3.5 Traffic priority
To configure radio traffic priority:
Select Configuration > Radio > Traffic priority.
2.3.3.6 ATPC
To configure ATPC:
Select Configuration > Radio > ATPC.


2.3.4 Interfaces
2.3.4.1 Ethernet ports
The Ethernet ports page, you can view and configure Ethernet port settings.
To configure an Ethernet port:
Select Configuration > Interfaces > Ethernet ports.


2.3.4.2 E1 ports
To configure E1 ports:
Select Configuration > Interfaces > E1 ports.


2.3.4.3 DS1 ports
To configure DS1 ports:
Select Configuration > Interfaces > DS1 ports.


2.3.4.4 STM-1 ports
To configure STM‐1 ports:
Select Configuration > Interfaces > STM1 Ports.
 Select OC‐3 Ports for a T1 board.


2.3.4.5 Wayside channel
To configure the Wayside channel:
Select Configuration > Interfaces > Wayside channel.
2.3.4.6 User channel

To configure the user channel:
Select Configuration > Interfaces > User channel.


2.3.4.7 EOW
The EOW page displays the EOW (Engineering Order Wire) channel status.
To configure the EOW channel:
Select Configuration > Interfaces > EOW.
2.3.4.8 AIS
To enable /disable AIS:
Select Configuration > Interfaces > AIS.


2.3.4.9 Synchronization
Sync source
To configure the sync source:
Select Configuration > Interfaces > Synchronization > Sync source.


Clock source
To configure the clock source:
Select Configuration > Interfaces > Synchronization > Clock source.


2.3.5 Protection
2.3.5.1 Protection parameters


2.3.5.2 Radio diversity
To enable and configure radio diversity:
Select Configuration > Protection >Radio diversity.
2.3.5.3 Multi-unit LAG

To enable multi‐unit LAG:
Select Configuration > Protection> Multi‐Unit LAG.

2.3.6 Trails
2.3.6.1 TDM trails
To configure TDM trails:
Select Configuration > Trails > TDM Trails.


2.4 Service OAM
2.4.1 MAID list
The MAID list table section displays details about each MAID.
To view a MAID’s details:
Select Service OAM > MAID List.


2.4.2 MEP and MIP list
To view the MEP and MIP list:
Select Service OAM > MEP and MIP list.
2.4.3 Advanced
2.4.3.1 Manual ping
You can also manually ping remote MEPs and MIPs.
To configure a manual ping:
Select Service OAM > Advanced > Manual ping.

2.4.3.2 Manual linktrace
To perform a manual linktrace:
Select Service OAM > Advanced > Manual linktrace.
2.5 Diagnostics and maintenance

2.5.1 Loopback
2.5.1.1 Radio
To configure radio loopback:
Select Diagnostics and maintenance > Loopback > Radio.


2.5.1.2 PDH line
To configure line loopback:
Select Diagnostics and maintenance > Loopback > PDH line.
2.5.1.3 SDH line

To configure loopback for an STM‐1 line:
Select Diagnostics > Loopback > SDH line.


2.5.2 Configuration management
To manage unit configuration files:
Select Diagnostics > Configuration management.


2.5.3 Software management
To manage unit software downloads, installation, upgrades, downgrades, and rollbacks:
Select Diagnostics > Software management.


2.5.4 ODU download
In ODU download page, you can initiate RFI downloads and view ODU software download status.
To initiate an ODU download:
Select Diagnostics >ODU download.
2.5.5 IFU-ODU interface monitoring

To view communication errors:
Select Diagnostics > IFU‐ODU interface monitoring.


2.5.6 Resets
To reset a specific slot:
Select Diagnostics > Resets.
2.5.7 File list

The File list page displays all application related files on the disk.
To view the list of files on the disk:

Select Diagnostics > File list.

2.6 Security
2.6.1 Security configuration
To configure system security:
Select Security>Security Configuration.


2.6.2 Users and groups
To manage users:
Select Security>Users and groups.
2.6.3 CSR file

To generate a CSR file:
Select Security>CSR file.


2.6.4 Change password
To change a user password:
Select Security>Change password.

3. System
3.1 Unit system information
The Unit Parameters page allows you to view and configure system information.
To configure unit parameters:
In the Unit parameters section:
1. In the System name field, enter a name for the node. (Optional)
 By convention, this is the node’s fully qualified domain name.
2. In the Slot label field, enter a name for the link.
 By convention, this is the name and slot label of the unit across the radio link.
3. In the Contact person field, enter the name of the person to be contacted when a problem
with the system occurs. (Optional)
4. In the System location field, enter the actual physical location of the node or agent.
(Optional)
5. In the Measurement system field, select the type of measurement you want the system to
use: Metric or Imperial.


The Unit parameters section includes a number of read‐only fields that are automatically generated by
the system, and settings that were configured on other pages.
 System up time shows how long the system has been operating continuously.
 IP address field displays the IP address that is configured in the Management window.
 System Description provides information about the Nera system.
 Voltage input displays the current input voltage.
 IFU temperature and ODU temperature display the current temperatures of the IFU and ODU.
3.2 System date and time

3.2.1 Configuring unit date and time
By default, the time & date are derived from the operating system clock. You can use the Unit
parameters page options to set new date and time values.
To set the unit’s date and time:
In the Date & Time configuration section:
1. Click the calendar to set the date
2. Click the time area to set the time.
3. Specify the hours and minutes offset from GMT.
 Offset from GMT is the Hours and Minutes offset of the time of day from Greenwich
Mean Time (GMT).


To configure Daylight Saving Time:
In the Daylight Saving Time section:
1. In the Start Date field, click the calendar to set the date when daylight saving time will
automatically be activated.
2. In the End Date field, click the calendar to set the date when daylight saving time will
automatically be terminated.
3. In the Offset field, specify the offset time, in hours, from GMT.
3.2.2 Configuring system Timing Protocol (NTP)

The NTP page allows you to view and set Network Timing Protocol parameters.
To activate the NTP server:
Select Configuration > General > NTP.


In the NTP Server Parameters section:
1. Enable or disable the NTP server.
 In the Admin field, select Enable.
2. Specify the IP address of the NTP server.
 In the Server IP field, enter the IP address of the NTP server.
 Status is a read‐only field that indicates whether the NTP server is Up or Down.
 Sync Server is a read‐only field that displays details about the NTP server with which the
system is currently synchronized. The values that can appear include:
IP of the remote NTP server
Local, if locked to the local element’s real‐time clock.
NA, when Admin is set to Disable and not synchronized with any clock.
 Poll Interval is a read‐only field that indicates the interval used by the NTP client to
maintain synchronization with the current NTP server.
3.3 Unit serial and part numbers

When requesting license upgrades and other services, you’ll be asked for the unit’s serial number.
To view IFU serial and part numbers:
In the IFU Serial/Part Numbers section:
 Serial number ‐ Indicates the IFU’s serial number.
 Part number ‐ Indicates the IFU’s part number.
To view ODU serial and part numbers:
In the ODU Serial/Part Numbers section:
 Serial number ‐ Indicates the ODU’s serial number.
 Part number ‐ Indicates the ODU’s part number.


3.4 Licensing
The Licensing page allows you to view and configure unit licenses and license types.
3.4.1 Viewing current license details

The Current License section displays details about the current license.
To view current license information:
In the Current License section:
 License type is a read‐only field that displays the current license type.
3.4.2 Enabling licensed features

The Current License section allows you to enter the license code that will enable licensed features.
To enable licensed features:
In the Current License section:
Enter the license code in the License code field.


3.4.3 Working with the demo license
The Demo License section allows you to enable the demo license, and displays the remaining time for an
activated demo license.
To enable or disable the demo license:
In the Demo License section:
Enable or disable the demo license.
 In the Demo admin field, select Enable to active the demo license.
 In the Demo admin field, select Disable to disable the demo license.
Demo timer is a read‐only field that displays the remaining time for demo mode.
3.4.4 Viewing licensed features

The License features section indicates which features are currently enabled.
To view license features:


In the License features section:
 ACM license is a read‐only field that displays indicates whether or not the ACM feature is
available.
 Switch application license is a read‐only field that displays the type of switch application
(Pipe, Switch, or Metro).
 Capacity is a read‐only field that displays the maximum capacity available for the radio.
 Network resiliency license is a read‐only field that indicates whether the resiliency
(RSTP/SNCP) feature is available.
 TDM capacity license is a read‐only field that indicates whether the TDM capacity license
is available. It limits the amount of TDM trails that can be mapped to a radio. If this license
is allowed, any radio script can be loaded but the number of trails is limited.
 TDM capacity value is a read‐only field that indicates the amount of TDM trail capacity
corresponding to the TDM capacity license.
 Synchronization Unit License is a read‐only field that indicates whether or not the
Synchronization Unit License (Synchronous Ethernet output) is allowed.
 Enhanced Traffic Manager License is a read‐only field that indicates whether the Enhanced
Traffic Manager is allowed.
 Asymmetrical Scripts License is a read‐only field that indicates whether asymmetric scripts
are enabled.
 Per usage license is a read‐only field that indicates if per usage license is enabled. Per
usage licensing allows unlimited usage of all features in the system, and generates a billing
report of the current usage.
3.4.5 Viewing licensed usage

The License features section indicates which features are currently enabled.
To view license usage:


In the Current usage section:
 Current script capacity – Indicates the allowed bandwidth.
 Current ACM mode – Indicates ACM mode status.
 Current Ethernet application – Indicates the configured Ethernet application type.
 Sync source – Indicates the sync source.
 STP protocol – Indicates the STP protocol status.
 Number of TDM trails in radio interface – Indicates the number of TDM trails.
 Enhanced Traffic Manager admin – Indicates the ETM status.
 Current asymmetrical script mode – Indicates the asymmetrical scripts status.
3.5 Viewing system application files

The File list page displays all application related files on the disk.
To view the list of files on the disk:
Select Diagnostics > File list.

4. Fault management
4.1 Configuring external alarms
The External Alarms page enables you to set up the external alarm system.
4.1.1 Alarm input configuration

You can define up to five independent alarm inputs.
To configure alarm input definitions:
In the Alarm Input section:
1. In the Admin field, enable or disable the alarm input.
 Select Enable to activate the alarm input, or Disable to deactivate.
2. In the Text field, specify a string to use as the alarm description.
 When an alarm input is raised, this text will appear as the alarm description text.
3. In the Severity field, specify the alarm input severity.
 When an alarm input is raised, the severity will be added to it.


4.1.2 Alarm output configuration
You can define a single alarm output.
To configure alarm input definitions:
In the Alarm Output section:
1. Enable or disable the alarm input.
 In the Admin field, select Enable to activate the alarm input, or Disable to deactivate.
2. In the Group field, specify the group of alarms that will trigger an alarm output:
 Communication ‐ Alarms related to traffic: radio, Ethernet line, TDM line
 Quality of Service ‐ Alarms related to QoS.
 Processing ‐ Alarms related to software: configuration, resets, corrupted files
 Equipment ‐ Alarms related to hardware, fan, ODU mute, power supply, and
inventory.
 Environmental ‐ Alarms relating to temperature.
 All groups ‐ All of the above groups.


4.2 Viewing current alarms
To view current alarms:
In the Current Alarms table:
 Date & Time ‐ The date and time the alarm was triggered appear in the column.
 Severity ‐ The color of the icon indicates the severity of the alarm.
 Module ‐ The module that generated the alarm.
 Description ‐ A description of the alarm.
4.2.1 Viewing alarm details

To view alarm details:


In the Current Alarms table:
Expand alarms in the list to view additional information.
 Click the + icon in the left column to open alarm details.
 Probable Cause – Displays the most likely cause of the alarm.
 Corrective Actions – Displays recommended actions to clear the alarm.
4.3 Viewing the event log

The Event log displays a list of historical events and alarm information.
The log shows the last 200 events and alarms that occurred. If the number of events/alarms exceeds
200, the oldest events/alarms will be removed.
To view the event log:
Select Faults > Event log.


In the Event Log table:
 # ‐ Indicates the number of the event/alarm.
 Date & Time ‐ Indicates the date and time the event/alarm was triggered.
 Severity ‐ Indicates the alarm severity.

 Module ‐ Indicates the module that generated the event/alarm.
 State ‐ Indicates the event/alarm status [Raised or Cleared].
 Description – Provides a description of the event/alarm.
To clear the event log:
Click Clear.
4.4 Traps configuration

The Trap manager page is used to configure trap forwarding parameters.
Each line in the Trap Managers table displays the setup for a manager defined in the system.
To configure a trap manager
1. Select Configuration > General > Traps Configuration.
2. Expand a trap manager.
 Click the + at the beginning of the line.


In the Trap Managers section:
1. Enable or disable the selected trap manager.
 Select Enable or Disable from the Traps admin field drop down list.
2. Specify the IP address to which traps will be sent.
 In the Trap manager field, enter the destination IP address.
3. Specify the manager's name.
 In the Manager name field, enter the manager’s name.
4. Specify the sending port.
 In the Trap port field, enter the number of the port through which traps will be sent.
5. Specify the SNMP community name.
 In the SNMP trap Community field, enter the SNMP community name.
6. Specify the heartbeat interval.
 In the Heartbeat period field, specify the number of minutes between generating
heartbeat traps.
7. Optionally, specify a message to be included with the trap.
 In the Trap CLLI field, enter free text that will be sent with the trap.
8. Specify trap forwarding criteria.
 In the Trap status change filter field, select On if you want a trap to be sent to the
manager you defined only when the most‐severe alarm of the unit changes.
For example, if the most severe status in the system is warning, and a new warning
alarm is raised, no trap will be sent (if you selected On for this option). On the
other hand, if the new alarm has the severity major, a trap will be sent to the
manager you defined.
 In the Send traps for alarms with severity field, select which severity levels of alarms
will be forwarded.

5. Configuration management
5.1 FTP
Before uploading or downloading configuration archives, you must define FTP settings.
5.1.1 Configuring local FTP

To configure FTP:
Select Diagnostics > Configuration management and click the FTP parameters link at
the bottom of the Configuration management window.
In the FTP parameters window:
1. Specify the FTP server host.
 In the Host IP field, enter the IP of the host where the archive is to be stored.
 In the Host path field, enter the path in the host (FTP directory) where the archive is to
be stored.
For the default FTP path use set // for Windows, or set / for Linux.
2. Specify the FTP mode.
 In the File transfer protocol field, select Ftp or Sftp.
3. Specify FTP login information.
 In the User name field, enter the user name for the FTP session.
 In the User password field, enter the password for the FTP session. If you use the
default user name (anonymous), use the host login for the password.
4 Click Apply to save your changes.

5.1.2 Configuring remote FTP
To configure remote FTP:
Select Diagnostics > Software management and click the FTP parameters link at the
bottom of the Software management window.
In the Remote server FTP parameters window:
1. Specify the FTP server host.
 In the Server IP address and path field, enter software update server URL, where the
software updates reside.
2. Specify FTP login information.
 In the User name field, enter the user name for the FTP session.
 In the User password field, enter the password for the FTP session. If you use the
default user name (anonymous), use the host login for the password.
3 Click Apply to save your changes.


5.2 Unit info and configuration archive management
In the Configuration management page, you can manage unit information and configuration archives.
To manage unit configuration files:


5.2.1 Creating a unit information archive file
To create a unit information archive file:
1. Select Diagnostics > Configuration management.
2. In the Unit Information section, click Create Archive.
5.2.2 Uploading a unit information archive file

To create a unit information archive file:
2. In the Unit Information section, click Upload Archive.
5.2.3 Viewing unit information archive upload status

To view archive upload status:
 In the Unit Information section, the Unit info upload status field indicates the current
upload status: Ready, In Progress, Success, or Failure.
5.2.4 Backing up unit archives

To backup unit archive files:
 Click Backup Selected Unit to backup archives for just the selected slot.
 Click Backup All Archives to backup archives for all the slots on the shelf.
5.2.5 Restoring unit archives

To restore unit archive files:
 Click Restore Selected Unit to backup archives for just the selected slot.
 Click Restore All Archives to backup archives for all the slots on the shelf.
5.2.6 Viewing archive operation status

To view archive operation status:
 The Archives operation status field indicates the current upload status: Ready, In
Progress, Success, or Failure.


5.2.7 Uploading a configuration archive file
To upload an archive file:
2. Click Upload Archive.
5.2.8 Viewing configuration file upload status

To view configuration file upload and download status:
 The Config upload status field indicates the current upload status: Ready, In Progress,
Success, or Failure.
5.2.9 Downloading a configuration archive file

To download an archive file:
2. Click Download Archive.
5.2.10 Viewing configuration file download status

To view configuration file upload and download status:
 The Config download status field indicates the current upload status: Ready, In Progress,
Success, or Failure.
5.2.11Resets
5.2.11.1 Restoring the factory default configuration
You can reset all of the IFUs to the default factory configuration.
To restore configuration settings to the shelf:
In the Set to factory default configuration section:
1. Click Activate to set all the units to the default configuration.
2. Click OK to reset the units or Cancel to return to the Configuration management window.


5.2.11.2 Resetting units
In the Resets page, you can perform a reset operation for a specific slot, or for all units on a shelf.
To reset a specific slot:
In the Reset a specific slot section:
Click Reset for the specific IFU.
To reset all units on a shelf:
In the Click to perform reset section:
 Click Shelf cold reset to reset all the IFUs.
 Click Extensions cold reset to reset only the extension IFUs.


5.3 Software management
5.3.1 IFU software management
In the Software management page, you can manage IFU software operations.
To manage unit software downloads, installation, upgrades, downgrades, and rollbacks:


5.3.1.1 Downloading software versions
To download a software upgrade:
1. Select Diagnostics > Software management.
2. In the New Version section, click Download to select an upgrade software package.
To download a software downgrade:
2. In the Old Version section, click Download to select a downgrade software package.
5.3.1.2 Viewing software download status

To view software download status:
The Download status field indicates the current download status: Ready, In Progress, Success, or
Failure.
To view the software download log:
2. Click the file icon next to the Download status field to view the download log.


5.3.1.3 Upgrading software versions
To upgrade unit software:
2. In the Installation Type section, specify the type of installation: Regular or Timed.
 For a timed installation, configure the installation timer.
Specify the number of minutes for timed software installation operation.
3. In the New Version section, click Upgrade Selected to upgrade selected slots, or Upgrade
All to upgrade all slots on the shelf.
5.3.1.4 Downgrading software versions

To downgrade unit software:
3. In the Old Version section, click Downgrade Selected to upgrade selected slots, or
Downgrade All to upgrade all slots on the shelf.
5.3.1.5 Rolling back a software installation

Rolling back an installation restores the units to the previous installation.
Note that rolling back is not the same as a downgrade. For example, you could rollback a downgrade
operation.
To rollback a software installation:
3. Click Rollback Selected to roll back only selected slots, or Rollback All to roll back the
installation for all slots on the shelf.


5.3.1.6 Viewing installation status
To view the software installation status:
The Install status fields indicate the current download status: Ready, In Progress, Success, or Failure.
 An Install status field will be displayed for each of the unit’s slots.
 For a timed installation, the Install status section will indicate the number of remaining
minutes until the installation operation.
 Note that cancelling a timed installation operation will not abort an installation that is
already in progress.
To view the software installation log:
2. Click the file icons next to the Install status fields to view the installation logs.
5.3.1.7 Viewing IFU version information

To view IFU version information:
Select Configuration > General > Versions > IFU.


In the IFU versions table:
 Package Name – Indicates the name of the software package.
 Target Device – Indicates the specific component that is contains the version.
 Running Version– Indicates the version that is currently running on the IFU.
 Installed Version– Displays IFU software files that were successfully installed.
 Upgrade Package– Displays IFU software files that were successfully downloaded to the
IFU, and are ready to be installed when IFU upgrade is executed.
 Downgrade Package– Displays IFU software files that were successfully downloaded to the
IFU, and are ready to be installed when IFU downgrade is executed.
5.3.2 ODU software management

In ODU download page, you can initiate RFI downloads and view ODU software download status.
5.3.2.1 Downloading software to the ODU

To initiate an ODU download:
In the ODU Software Download section:
Click Software Download.

5.3.2.2 Viewing ODU download status
To view ODU software download status:
In the ODU Software Download section:
 ODU software download status ‐ Displays the current state of ODU software download.
 ODU software download progress ‐ Displays the download progress.
5.3.2.3 ODU version information
Viewing installed ODU versions

ODU installed versions displays ODU software packages currently installed in the IFU, as part of the
overall software package.
To view installed ODU versions:

In the ODU installed versions table:
 Type indicates the ODU type.
 SW Version indicates the version of the installed ODU software.
 FW Version indicates the version of the installed ODU firmware.
Viewing running ODU versions

ODU running version displays the ODU type, and the software versions that are currently running on the
ODU.
To view ODU running versions:
In the ODU running versions section:
 ODU type indicates the ODU type.
 Software version indicates the software version currently on the ODU.

Viewing ODU upgrade and downgrade versions
ODU upgrade & downgrade versions displays ODU software packages successfully downloaded to the
IFU, and ready to be installed when ODU Software Download is executed.
To view ODU upgrade and downgrade versions:
In the ODU Upgrade & Downgrade section:
 Common version odu upgrade indicates the version of the ODU software upgrade
package.
 Common version odu downgrade indicates the version of the ODU software downgrade
package.

6. Performance monitoring
6.1 PM commands
The Performance Monitoring commands window enables you to clear all performance monitoring
measurements in the unit, except for RMON.
To clear performance monitoring data:
Select PM & Counters > PM Commands.
In the Click to Clear section:
Click Clear.
Many of the Performance Monitoring (PM) windows contain an option to display the PM data as a
graph.

To display a PM graph:
Click the graph icon at the top of the PM window.
In the Frames dropped section:
 Avg. Green – Displays the average green traffic in bytes per seconds (Bps) during the
report interval.
 Max Green ‐ Displays the peak green traffic for one second during the report interval.
 Avg. Yellow – Displays the average yellow traffic in Bps during the report interval.
 Max Yellow ‐ Displays the peak yellow traffic for one second during the report interval.
 Integrity ‐ Indicates whether the values received at that time and date 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.


6.2 Line PMs
6.2.1 E1 PMs
The E1 PM page contains a separate PM window for each E1 link in use.
You can set display to show PMs for the previous 24 hours in 15 min intervals, or for the past month in
daily intervals.
To view E1 PM:
Select PM & counters > E1> Port#.
In the E1 PM report:
 ES – Indicates the number of seconds during which errors occurred.
 SES – Indicates the number of severely errored seconds.
 UAS – Indicates the Unavailable Seconds value of the current interval. The value can be
between 0 and 900 seconds (15 minutes).
 BBE – Indicates the number of background block errors.


6.2.2 DS1 PMs
The DS1 PM page contains a separate PM window for each DS1 link in use.
daily intervals.
To view DS1 PM:
Select PM & counters > DS1> Port#.
In the DS1 Ports table:


6.2.3 STM-1 PMs
The STM‐1/OC‐3 PM page contains a separate PM window for each STM‐1/OC‐3 link in use.
daily intervals.
To view STM‐1/OC‐3 PM:
Select PM & counters > STM‐1> Port#.
In the STM‐1 PM report:


6.3 Radio PMs
6.3.1 Signal level PMs
The Signal Level PM report shows signal level performance.
daily intervals.
To view signal level performance:
In the PM report section:
 Min RSL – Indicates the minimum received level measured during the interval.
 Max RSL – Indicates the maximum received level measured during the interval.
 RSL Exceed #1 ‐ Displays the number of seconds the RSL threshold #1value was exceeded
during the current interval.
 RSL Exceed #2 ‐ Displays the number of seconds the RSL threshold #2 value was exceeded
during the current interval.
 Min TSL – Indicates the minimum transmitted level measured during the interval.
 Max TSL – Indicates the maximum transmitted level measured during the interval.
 TSL Exceed ‐ Displays the number of seconds the TSL threshold value was exceeded during
the current interval.

6.3.2 Aggregate radio PMs
The Aggregate PM report page displays tributary values measured for the previous 24 hours in 15 min
intervals, or for the past month in daily intervals.
To view aggregate radio performance:
Select PM & counters > Radio > Aggregate.
In the Aggregate PM report:


6.3.3 Radio MRMC PMs
The MRMC PM report displays Multi‐Rate Multi‐Constellation performance for the previous 24 hours in
15 min intervals, or for the past month in daily intervals.
To view MRMC PM:
Select PM & counters > Radio > MRMC.
In the MRMC PM report:
 Min Profile ‐ Indicates the minimum radio profile during the last interval.
 Max Profile ‐ Indicates the maximum radio profile during the last interval.
 Min BitRate (Mbps) ‐ Indicates the minimum total radio throughput (Mbps), delivered
during the last interval.
 Max BitRate (Mbps) ‐ Indicates the maximum total radio throughput (Mbps), delivered
during the last interval.
 Min number of allocated TDM VCs ‐ Indicates the minimum number of TDM voice
channels (E1/T1) delivered over the radio during the last interval.
 Max number of allocated TDM VCs ‐ Indicates the maximum number of TDM channels
(E1/T1) delivered over the radio during the last interval.


6.3.4 Radio MSE PMs
The MSE PM report displays the modem’s Minimum Square Error performance statistics for the previous
24 hours in 15 min intervals, or for the past month in daily intervals.
To view MSE PM:
Select PM & counters > Radio > MSE.
In the MSE PM report:
 Min MSE ‐ Indicates the minimum MSE in dB, measured during the last interval.
 Max MSE ‐ Indicates the maximum MSE in dB, measured during the last interval.
 MSE Exceed ‐ Indicates the number of seconds the MSE exceeded the threshold
(configured in the field below the table) during the last interval.


6.3.5 Radio XPI PMs
The XPI PM report displays the Cross Polarization Interference value for the previous 24 hours in 15 min
intervals, or for the past month in daily intervals.
To view cross polarization interference performance:
Select PM & counters > Radio > XPI.
In the XPI PM report:
 Min XPI ‐ Indicates the minimum XPI in dB, measured during the last interval.
 Max XPI ‐ Indicates the maximum XPI in dB, measured during the last interval.
 XPI Exceed ‐ Indicates the number of seconds the XPI exceeded the threshold (configured
in the field below the table) during the last interval.


6.4 TDM PMs
6.4.1 Radio TDM channel PMs
The TDM Channel report displays the unavailable seconds (UAS) of the expected E1/T1 trails on the
radio.
When ACM decreases, the capacity of the radio is reduced. Trails with insufficient bandwidth in the
radio link capacity may be dropped.
When a trail is dropped, its UAS counter will start counting the seconds for which the trail was not
serviced.
Select PM & counters > Radio > TDM channels > Channel#.
In the Channel PM report:


6.4.2 TDM trail PMs
End‐to‐end PM measurements are taken for TDM trails. This PM is based on BER measurement, and not
on code violation, which distinguishes it from line interface PMs.
The measurements are the same as those for line interfaces (ES, SES, UAS, BBE), but are based on BER
measurements.
PM for trails is measured in the following cases, and is maintained in the relevant IFUs:
 End point interfaces: trail end line interfaces
 Radio interfaces that perform SNCP
If TDM trail path protection is configured, the system performs measurement on both the primary and
secondary paths.
To display PMs for a trail:
1 Select PM & Counters >TDM trails.
2 Select a trail from the Trails List section.


6.5 Ethernet statistics
6.5.1 Frame error rate statistics
The Frame Error Rate report displays statistics of the Ethernet frame error rate (%) measured on the
radio Ethernet port.
To view Frame error rate performance:
Select PM & counters > Radio > Ethernet > Frame error rate.
In the Frame Error Rate PM report:
 Frame Error Rate (%) ‐ Indicates the percentage of received error frames relative to all
frames received by the radio Ethernet port.


6.5.2 Throughput statistics
The Throughput PM report displays radio Ethernet throughput statistics (excluding TDM traffic),
measured on the radio port.
To view Throughput PM:
Select PM & counters > Radio > Ethernet > Throughput.
In the Throughput PM report:
 Peak Throughput (bps) ‐ Indicates the maximum throughput measured during the last
interval.
 Average Throughput (bps) ‐ Indicates the average throughput measured during the last
interval.
 Throughput Exceed (Seconds) ‐ Indicates the number of seconds the throughput exceeded
the threshold (configured in the field below the table) during the last interval.


6.5.3 Capacity statistics
The Capacity PM report displays statistics of the Ethernet capacity, including Ethernet data and
overhead bytes, measured on the radio port.
To view Capacity PM:
Select PM & counters > Radio > Ethernet > Capacity.
In the Capacity PM report:
 Peak Capacity (bps) ‐ Indicates the maximum capacity measured during the last interval.
 Average Capacity (bps) ‐ Indicates the average capacity measured during the last interval.
 Capacity Exceed (Seconds) ‐ Indicates the number of seconds the throughput exceeded
the threshold during the last interval.


6.5.4 Utilization statistics
The Utilization PM report displays statistics of Ethernet utilization (%) measured on the radio port.
Ethernet utilization is a measurement of actual Ethernet throughput, relative to the potential Ethernet
throughput of the radio, excluding TDM channels.
Ethernet utilization during the last interval is displayed as one of five bins:
0‐20% | 20‐40% | 40‐60% | 60‐80% | 80‐100%
To view Ethernet utilization statistics:
Select PM & counters > Radio > Ethernet > Utilization.
In the Utilization PM report:
 Range of Peak Utilization (%) ‐ Indicates the maximum utilization measured during the last
interval.
 Range of Average Utilization (%) ‐ Indicates the average utilization measured during the
last interval.
 Utilization Exceed (Seconds) ‐ Indicates the number of seconds the value exceeded the
threshold during the last interval.


6.5.5 Enhanced Traffic Manager statistics
You can view a PM report for the Enhanced traffic manager of each queue. The report contains data
from the most recent report interval.
Each PM is measured per queue in Max/Avg format. Green traffic refers to frames that comply with the
configured Committed Information Rate (CIR). Yellow traffic refers to frames that exceed the configured
CIR but are below the configured Excess Information Rate (EIR).
To view traffic statistics for a managed Ethernet queue:
Select PM & counters > Enhanced traffic manager > Queue#.
In the Bytes passed section:
 Avg. Green – Displays the average green traffic in bytes per seconds (Bps) during the
report interval.
 Max Green ‐ Displays the peak green traffic for one second during the report interval.
 Avg. Yellow – Displays the average yellow traffic in Bps during the report interval.
 Max Yellow ‐ Displays the peak yellow traffic for one second during the report interval.


6.5.6 RMON counters
The RMON counters page displays values relating to the bridge performance. The counters are designed
to support:
 RFC 2819, RMON MIB
 RFC 2665, Ethernet‐like MIB
 RFC 2233, MIB II
 RFC 1493, Bridge MIB
The statistic counters are divided into ingress statistics and egress statistics.
6.5.6.1 Viewing RMON statistics

To reset RMON counters:
In the Running Counters section:
 Undersize frames received – Indicates frames shorter than 64 bytes
 Oversize frames received – Indicates frames longer than 1632 bytes
 Jabber frames received – Indicates the total number of frames received with a length of
more than 1632 bytes, but with an invalid FCS
 Fragments frames received – Indicates the total number of f frames received with a length
of less than 64 bytes, and an invalid FCS
 Rx error frames received – Indicates the total number of f frames received with Phy‐error
 FCS frames received – Indicates the total number of f frames received with CRC error, not
counted in "Fragments", "Jabber" or "Rx error" counters


 In Discard Frames – Counts good frames that cannot be forwarded due to lack of buffer
memory
 In Filtered Frames – Counts good frames that were filtered due to egress switch VLAN
policy rules
 Pause frames received– Indicates the number of flow‐control pause frames received
6.5.6.2 Resetting RMON counters

To reset RMON counters:
In the Running Counters section:
To reset a specific counter, click Clear at the top of the column.
To reset all counters, click Clear All at the bottom of the page.

7. Equipment resiliency
In the Protection parameters page, you can configure protection parameters.
To configure protection:
Select Configuration > Protection > Protection Parameters.
7.1 Configuring the protection type

In the Protection configuration section, you can configure the protection type.
To configure the protection type:
Select Configuration > Protection > Protection Parameters.


In the Protection Configuration section:
1. Select the type of protection.
 Select 1+1 HSB, 2+2 HSB, or 2+0 HSB from the Protection admin field drop down list.
 To disable protection, select Disable.
2. Click Apply to enable the selected protection type.
The Protection mode field indicates the current status of the unit: Active or Standby.
7.1.1 1+1 HSB protection

Protection is performed between the pairs of IFUs.
 In a protected configuration, the active unit is referred to as the main unit and the standby
IFU is referred to as the mate. At any given time one pair is active and the other is stand‐
by.
 During a switch over, the active unit becomes standby and the mate unit becomes active.
 Protection can be enabled for any pair of units on a shelf (1+2, 3+4, 5+6)
To enable protection:
 All IFUs must have the same hardware version (identical part numbers).
Verify part numbers by viewing the IFU Serial/Part numbers section on the
Configuration > General > Unit parameters page.
 All IFUs have the same software version.
Verify software versions by viewing the IFU versions table on the Configuration >
General > Versions > IFU page.
 All IFUs have the same license.
Verify license compatibility by selecting checking the License features section on the
Configuration > General > Licensing page.
 Every IFU has unique IP address, and that all addresses are within the same subnet.
Verify IP addresses by viewing the Local IP configuration section on the Configuration
> General > Management page.
 All IFUs are set to the same switch application type (Pipe / Managed / Metro).
Verify switch application type by viewing the Ethernet Application Type section on the
Configuration > Ethernet Switch > Switch Configuration page.
 All IFUs have the same Management mode (In band or OOB)
Verify IP addresses by viewing Type field in the Management Ports section on the
Configuration > General > Management page.
For In‐Band management, ensure that all IFUs have the same In‐Band VID.


 The IFUs are connected by dedicated protection ports.
Y‐Split cables must be used for Ethernet signals
ETH Cross Cable* (Protection Cable) is used to connect the protection ports of both
IFUs
Note: The IFU, which is connected to the ODU fed by the lower attenuation
channel of the RF coupler, is the IFU that should be selected as "Active“.
When protection is enabled:
 Accessing a mate IFU can only be done via the active IFU, either via its local IP address, or
via a floating IP address.
A floating IP address can be used to provide a single IP address that allows direct
access to the current active main unit. In a protection configuration, the floating IP
address is copied to mate, and applied to the standby unit.
Floating IP addresses are not supported by XPAND IP+ R1.
 Configure the mate parameters.
When the 2nd IFU is properly configured and connected, the IP and MAC addresses
should be displayed in the Mate parameters section
Click Open Mate link to configure the Mate parameters.
Click Copy To Mate to copy the active unit’s configuration to the standby unit. Note:
these parameters will not be copied:
MNG mode (In‐Band / OOB)
In‐Band VLAN
Switch mode
Licenses
 Configure the switching criteria.
Selecting On in the Protection lockout field will disable switching.
Selecting On in the Protection force switch field forces a switchover regardless of the
mate unit’s qualifying status.
Clicking Manual Switch will force a switch over only if the mate unit qualifies for active
status.
Incompatible features
 Multi Channel ABC
 XPIC

The 2+2 configuration consists of two pairs of IFUs.
The 2+2 configuration is possible only between the units in the main backplane in each shelf (slots 1‐2).
Using the other IFUs in the shelves (slots 3‐6) is not supported.
The two pairs are inserted into separate chassis and are connected by a protection cable between the
main IFUs in slot #1 only.
All four units must be configured to 2+2 HSB.
 The Master unit in a 2+2 configuration is the lower IFU in each pair. The master unit is
responsible for:

Sending and receiving traffic from/to the user through line interfaces.
Receiving protection information from mate (slave)
Sending/receiving protection information to second master – at any one time one
master is “decision” and the other is “report”.
 The Slave unit in a 2+2 configuration is the upper IFU in each pair. The slave unit is
responsible for:
Sending/receiving traffic from/to user through line interfaces.
Sending protection information to mate in shelf (master)
Slave units always behave as “report” (are told by master whether to be active or
stand‐by).
The principles of 2+2 operation are an extension of 1+1 protection:
When enabled:
 Locking, forcing protection is done from master units only
 Copy‐to‐mate operations are available separately in master units and slave units.
 The same criteria (interfaces LOS, LOC, LOF) are monitored and compared between active
and stand‐by units (Comparing is carried out by master units)
 All enabled interfaces of all four IFUs are monitored
 A missing slave unit is interpreted as LOS in its interfaces. A missing master is a “no mate”
condition During 2+2 operation
XPIC & 2+2 protection
 When configured as 2+2 HSB, the XPIC recovery mechanism is disabled.
The reason for this is that in case of a failure in a link, the system will switch to the
stand‐by pair instead of attempting to recover the link, as done in 2+0 XPIC.
 Radio scripts, radio Tx frequency, and radio Rx frequency can be changed only at the
master unit and will be changed automatically on the slave units
Should the change at the slave unit fail for any reason, configuration changes on the
master unit will be rolled back.
 Space and frequency diversity


While a standard 2+0 multi‐radio configuration protects against radio malfunction or failure, a 2+0 Multi
Channel ABC configuration with line protection adds protection for the line interfaces, guaranteeing no
single point of failure.
Multi Channel ABC with line protection is only available for adjacent pairs of IFUs in a nodal enclosure
(slots 1 and 2, 3 and 4, 5 and 6).
Selecting 2+0 HSB automatically configures Multi Channel ABC for the selected pair of units. The active
unit is the IFU that currently holds the line interfaces. This unit will be the Multi Channel ABC master
unit.
2+0 HSB radio blocking criteria:
 Minimum ACM point and enable/disable
 Radio Excessive BER enable/disable
 Radio Signal degrade enable/disable
 Block/unblock traffic from radio link
2+0 HSB automatic state propagation criteria
 Radio LOF
 Excessive BER
 1+1 HSB
 2+2 HSB
 2+0 Multi Channel ABC (without line protection)
7.2 Specifying active and standby mode

If a mate unit is configured, you can specify which unit is the active unit.
To specify the protection mode:
Select Configuration > Protection >Protection parameters.
In the Protection configuration section:
1. In the Protection mode field, select Active or Standby.
 If no mate is associated yet with the unit, the Protection mode field will be read‐only,
and the mode will be set to Active.
2. Click Apply to modify the protection mode.

7.3 Configuring switching criteria
In the Protection parameters page, you can specify the protection switch criteria.
To disable switching:
In the Protection commands section:
Enable or disable protection lockout.
 Select On or Off from the Protection lockout field drop down list.
To force a protection switch:
In the Protection force switch field, selecting On forces a protection switchover and then
freezes the protection state.
To manually switch protection:
Clicking Manual switch issues a switchover that will take affect when no other protection
related alarms are raised.
To enable radio excessive BER switching:


In the Protection switch criteria section:
Enable forced switchovers for specific types of alarms.
 Radio excessive BER – Select Enable to initiate a switchover when a radio excessive
BER alarm is raised. This option is only displayed when the MRMC script is regular or
ACM running in Fixed mode.
 External alarm #1 – Select Enable to initiate a switchover when external alarm #1 is
raised.
Note: Since Multi Channel ABC protects against radio channel failure by blocking
the defective radio, in 2+0 HSB, radio failure or excessive BER will not cause a
protection switchover.
7.4 Viewing mate parameters

The Protection parameters page displays the mate unit’s IP and MAC addresses, and provides a link to
open the mate unit management system.
To specify the mate unit:
In the Mate parameters section:
 Mate IP address ‐ Indicates the IP address of the mate unit.
 Mate MAC address ‐ Indicates the MAC address of the mate unit.
To open the mate unit’s management system:
Click Open mate.
To copy the main unit’s configuration settings to the mate unit:
1 Select Configuration > Protection > Protection parameters.
2 Click Copy to mate.
 Copy to mate status ‐ Indicates the status of the Copy to mate command.

7.5 Multi-unit LAG
Multi‐Unit LAG provides Ethernet line protection for the Gigabit Ethernet (GbE) electrical and optical
interfaces.
An external switch is connected to the HSB protected XPAND IP+ link by means of two static Link
Aggregation (LAG) ports. The external switch can be another XPAND IP+ IFU or any third party
equipment that supports static LAG protocol.
Multi‐Unit LAG is supported with any of the following protection features:
 1+1 HSB
 1+1 Space or frequency diversity
 2+2 HSB
 2+0 Multi Channel ABC with line protection
To enable multi‐unit LAG:
1. Enable protection.
 Each of the protection features listed above can work with Multi‐Unit LAG.
2. Enable a static LAG on the external switch.
3. Connect the external switch LAG interfaces to port 1 of the active and standby XPAND IP+
units respectively.
4. Connect Ethernet port 2 of the active XPAND IP+ unit to the Ethernet port 2 of the standby
XPAND IP+ unit.
5. Select Configuration > Protection> Multi‐Unit LAG to open the Multi‐Unit LAG page.
6. Enable Multi‐Unit LAG in the active XPAND IP+ unit.

In the Multi‐Unit LAG admin section:
1. Select Enable.
2. Click Apply.
Upon enabling, each IFU will perform the following configurations automatically in both active and
standby units:
 Enable port 2.
 Set a LAG on port 1 and port 2.
 Enable mirroring.
Multi‐unit LAG configuration notes
 Multi‐Unit LAG is available only for IFUs which are inserted in a shelf.
 Multi‐Unit LAG is only supported in Single Pipe mode.
 Multi‐Unit LAG is supported in both standalone and nodal configurations.
 Multi‐Unit LAG supports both electrical and optical interfaces.
 Note: As a constraint of the LAG protocol, both ports must have the same type of physical
interface (e.g., both optical or both electrical).

8. Radio features
The Radio menu allows you to configure radio parameters and thresholds.
8.1 Configuring radio parameters

8.1.1 Enabling and disabling the radio
To specify the radio link ID:
In the Configuration parameters section:
Enable or disable the radio.
 Select Enable or Disable from the Radio IF interface field drop down list.
The Radio IF operational status field indicates the current radio status.
8.1.2 Specifying the radio link ID

To specify the radio link ID:

Configure the radio link ID.
 In the Link ID field, enter the identification number of the link.
When working with an IFU that has the Link ID feature on one end and an IFU that
does not have this feature on the other end, set the Link ID to 1.
8.1.3 Configuring the remote radio IP address

To set the remote radio IP address:
In the Remote radio parameters section:
1. Configure the remote radio location.
 In the Remote IP address field, enter the IP address of the remote unit.
 In the Remote floating IP address field, enter the remote floating IP address.
2. Click Apply.
8.2 Frequency settings

8.2.1 Configuring Tx and Rx frequencies
To configure the Tx and Rx frequencies:


In the Frequency control section:
1. Specify the transmission radio frequency.
 In the Tx frequency field, enter the transmission radio frequency.
2. Specify the received radio frequency.
 In the Rx frequency field, enter the received radio frequency.
3. Optionally, check the Set also remote unit checkbox to apply these frequency settings to
the remote unit.
1. Enable or disable Tx muting.
 In the Mute Tx field, select Enable or Disable.
2. Specify the maximum operational Tx value.
 In the Max Tx level field, enter a number between 2‐20 as the maximum transmission
frequency.
8.2.2 Remote radio frequency settings

To configure remote radio frequency settings:
1. Set the maximum transmission level.
 In the Remote force max Tx level field, enter a number between 2‐20 as the transmit
level for the remote radio.
2. Set the ATPC receive level.
 In the Remote ATPC reference Rx Level field, enter a number between ‐‐70‐30 for the
ATPC Rx level.
3. Click Apply.

To unmute the remote unit transmitter output:
Click Force unmute.
8.2.3 Enabling MAC header compression

The Radio parameters page provides options to control the MAC header compression.
Compared with Fiber optics and other line base links, radio transmission has limited bandwidth.
Compression is required to improve available capacity utilization. MAC header compression can be used
as a supplement to the other compression without affecting traffic performance.
Nera’s proprietary MAC Header compression improves the effective throughput by up to 45%, without
affecting user traffic.
Capacity reached after header compression is in accordance with the Ethernet packet
length. Effectiveness is reduced if a high number of L2 flows are used.
To enable MAC header compression:


1. In the MAC header compression field, select Enable.
2. Click Apply.
8.2.4 Enabling RSL degradation alarms

This feature enables the generation of an alarm when the RSL level degrades below a user‐defined
threshold.
When enabled, an alarm is generated if the RSL level degrades below the nominal level minus the
degradation margin. The alarm is cleared when the RSL level returns to a level above this point.
To enable RSL degradation alarms:
1. In the RSL degradation alarm admin field, select Enable.
2. Configure the nominal level for the RSL degradation alarm.
 In the Nominal RSL level for RSL degradation alarm, enter the nominal level.
3. Configure the degradation margin for the RSL degradation alarm.
 In the Margin for RSL degradation alarm, enter the margin.
4. Click Apply.
8.3 MRMC scripts

The MRMC table lists all available radio scripts.
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.
Note: The list of available scripts reflects licensed features. Only scripts within your
licensed capacity will be displayed. ACM and asymmetrical scripts will be available
if they are allowed by the current license configuration.

8.3.1 Asymmetric scripts
Transmit and receive levels can be either symmetric or asymmetric.
In symmetric scripts, bandwidth is identical in both Tx and Rx directions. However, since the traffic itself
is not symmetric, symmetric scripts often result in underutilized bandwidth, especially in the Tx
direction.
Asymmetric scripts allow you to optimize bandwidth utilization by providing at least 50% more capacity
to the downlink on the account of the uplink.
To view available asymmetric radio scripts:

In the MRMC table section:
Click Asymmetric.
Asymmetrical scripts configuration notes
 When using an asymmetric script, the remote end must be configured with a
complementary asymmetrical radio scheme.
 You’ll need to upgrade the uplink script (narrow TX, wide RX) at one end of the link, and
upgrade the downlink script (wide TX, narrow RX) at the other end of the link.
 Changing scripts requires a reset. To avoid loss of management to the remote site, it is
recommended to upgrade the remote site first.
 Asymmetrical scripts are not supported on XPAND IP+ R1.
 Asymmetrical scripts are not compatible with XPIC.
 In an asymmetric script, the bit rate field is replaced with separate Tx and Rx bit rate
fields.
8.3.2 Regular radio scripts

Regular scripts apply uniform transmit and receive rates that remain constant regardless of
environmental impact on radio operation.
To apply a regular radio script:
1. Specify which types of scripts to display: Normal or Asymmetric.
2. Click the + icon for a regular script (without the ACM prefix) to open the script
configuration options.
3. Click Apply.


8.3.3 ACM radio scripts
In ACM mode, a range of profiles determines Tx and Rx rates, allowing the radio to modify its transmit
and receive levels in response to environmental conditions.
The ACM TX profile is determined by the remote RX MSE performance.
The RX end is the one that initiates an ACM profile upgrade or downgrade.
To apply an ACM script:
1. Specify which types of scripts to display: Normal or Asymmetric.
2. Click the + icon of an ACM script (scripts with an ACM prefix) to open the script
configuration options.
3. 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 choose which profile to use according to the channel fading conditions.
For ACM Fixed Mode scripts:
1. Select the MRMC profile.
2. Click Apply.

For ACM Adaptive Mode scripts:
1. Specify the radio’s maximum allowed transmission frequency.
 In the Select Maximum ACM Profile section, select the maximum ACM profile.
2. Specify the radio’s minimum allowed transmission frequency.
 In the ACM Minimum Profile field, select the minimum ACM profile.
3. Specify whether the system should automatically align power usage to the current
bandwidth utilization.
 Select Enable or Disable from the Adaptive Power field drop down list.
 In the Reference Class field, specify class‐2/4/5B/6A for ETSI, or FCC for FCC.
4. Click Apply.
8.3.4 ACM adaptive power

When configuring an ACM script with Adaptive Mode, you can determine whether or not the ODU
power will be adaptive as well.
During fade conditions requiring a modulation drop, a constant power scheme cannot increase transmit
power to compensate for the signal degradation, further reducing capacity. Adaptive power dynamically
adjusts the power to the lowest transmit level for the current modulation.
 When disabled, the maximum Tx power in lower constellations is limited by the highest
modulation.
 When enabled, the maximum Tx power in lower constellations is limited by the reference
class.
To enable adaptive power:

In the MRMC Table section:
1. Select an ACM script.
1. Expand an ACM script to configure its options.
ACM scripts are indicated by the ACM prefix.
2. Enable or disable adaptive power.
 Select Enable or Disable from the Adaptive Power field drop down list.
3. Specify the adaptive power reference class.
 In the Reference Class field, select class‐2/4/5B/6A for ETSI, or FCC for FCC.
8.3.5 Enabling alarms on MRMC profile degradation

If the current radio script supports Adaptive Code Modulation (ACM), when enabled, traps can be
generated upon Tx ACM profile degradation below the user‐defined threshold.
To enable alarms on MRMC profile degrade:
In the MRMC configuration section:
1. Enable the MRMC profile degrade alarm.
 Select Enable from the Alarm generation on MRMC profile degrade field drop down
list.
2. Configure the threshold for MRMC profile degrade.
 In the Threshold for MRMC profile degrade alarm field, specify the profile above which
will generate the profile degrade alarm.
3. Enable or disable event and trap generation on ACM profile degrade.
 In the Alarm generation for MRMC profile degrade field, select Enable or Disable.

8.4 Setting radio traffic priorities
When using ACM and the available radio bandwidth is changing, it can become necessary to drop some
of the outgoing traffic. The Traffic Priority window lets you determine which type of traffic should be
dropped first.
The system distinguishes between four different types of traffic:
 High‐priority TDM trails
 Low‐priority TDM trails
 High‐priority Ethernet traffic
 Low‐priority Ethernet traffic
TDM traffic is configured in the TDM Trails window (Configuration > Trails > TDM Trails).
Ethernet traffic is prioritized according the priority of the QoS or Enhanced QoS queues. Ethernet traffic
from queues with a lower priority are dropped when there is not enough bandwidth.


These features should have identical configurations on both sides of the link:
 Each TDM trail should have the same priority.
 The High‐priority Ethernet Bandwidth should be the same.
 The queue priority schemes should be the same.
To configure radio traffic priority:
Select Configuration > Radio > Traffic priority.
In the Traffic priority section:
1. Specify the traffic priority scheme.
 In the Traffic priority scheme field, select a traffic priority scheme:
High TDM over Ethernet (default)
 TDM high priority
 TDM low priority
 Ethernet
High Ethernet over TDM
 Ethernet high priority
 Ethernet low priority
High TDM over high Ethernet
 Ethernet high priority
 Ethernet low priority


2. Specify the available bandwidth for high priority Ethernet traffic.
 The Current available capacity field displays the amount of current capacity, in Kbps.
 In the High‐priority Ethernet BW field, specify how much of your current capacity to
allocate for Ethernet bandwidth.
3. Click Apply to save configuration changes.
8.5 Power options

8.5.1 ATPC override
In the ATPC page, you can configure Automatic Transmit Power Control override settings.
To configure ATPC override:
In the ATPC Configuration section:
1. Enable or disable ATPC.
 In the ATPC admin field, select Enable or Disable.
2. Specify the default transmission signal level for ATPC override mode.
 In the ATPC override Tx level field, enter a number between ‐50 and 34 as the ATPC
override transmit level.
3. Specify the RSL reference value for the ATPC mechanism.
 In the ATPC reference RSL field, enter a number between ‐70 and 30 as the reference
value.
4. Specify the ATPC override timeout.
 In the ATPC timeout field, specify the number of seconds before overriding the
current Tx level with the ATPC override Tx level.
The ATPC timer counter field indicates the number of seconds remaining until
ATPC timeout.
5. Click Apply.

To cancel ATPC override:
In the ATPC Configuration section:
Click ATPC override cancel.
The cancel option aborts the current ATPC override for a radio that is transmitting at the ATPC override
Tx level. Following execution, the system goes back to normal ATPC operating mode.
8.5.2 Green mode

Note: When ATPC is enabled, Green Mode cannot be enabled
To configure radio Green mode:
In the Green mode section:
1. Enable or disable Green mode.
 In the Green mode admin field, select Enable or Disable.
2. Specify the Green mode reference level.
 In the Green mode ref rx level field, enter a number between ‐70 ‐30 as the Rx
reference.
3. Click Apply.


8.6 Radio thresholds
In the Radio thresholds page, you can configure radio threshold levels.
To configure radio thresholds:
Select Radio > Radio thresholds.
In the Radio Thresholds section:
1. Select the level above which an excessive BER alarm is issued for errors detected over the
radio link.
 In the Radio excessive BER threshold field, select the excessive BER threshold.
 The Radio BER field displays the current radio BER value.
2. Select the level above which a Signal Degrade alarm is issued for errors detected over the
radio link.
 In the Radio signal degrade threshold field, select the signal degrade threshold.
3. Click Apply.
8.6.1 RSL and TSL thresholds

To configure signal level thresholds:

In the Thresholds configuration section:
1. Configure the RSL exceed thresholds.
 In the RSL Threshold #1 field, specify the number of seconds below which RSL 1
exceeded seconds will be counted.
 In the RSL Threshold #2 field, specify the number of seconds below which RSL 2
exceeded seconds will be counted.
2. Configure the TSL threshold.
 In the TSL Threshold field, specify the number of seconds below which TSL exceeded
seconds will be counted.
3. Click Apply to save your changes.
4. Click Refresh to update the threshold values.
8.6.2 MSE threshold

To configure the MSE threshold:
Select PM & counters > Radio> MSE.
1. Configure the MSE threshold.
 In the MSE Threshold field, specify the number of seconds below which MSE exceeded
3. Click Refresh to update the threshold value.


8.6.3 XPI threshold
To configure the XPI threshold:
Select PM & counters > Radio> XPI.
1. Configure the XPI threshold.
 In the XPI Threshold field, specify the number of seconds below which XPI exceeded
8.6.4 Ethernet throughput threshold

To configure the throughput threshold:
Select PM & counters > Radio> Ethernet > Throughput.
1. Configure the throughput threshold.
 In the Throughput Threshold field, specify the throughput threshold (in Mbps), above
which will be counted as Throughput Exceeds seconds.
8.6.5 Ethernet capacity threshold

To configure the Ethernet capacity threshold:
Select PM & counters > Radio> Ethernet > Capacity.
1. Configure the capacity threshold.

 In the Capacity Threshold field, specify the capacity threshold (in bps), above which
will be counted as Capacity Exceeds seconds.
8.6.6 Ethernet utilization threshold

To configure the Ethernet utilization threshold:
Select PM & counters > Radio> Ethernet > Utilization.
1. Configure the utilization threshold.
 In the Utilization Threshold field, select the a range of utilized throughput, above
which will be counted as Utilization Exceeds seconds.
8.6.7 Ethernet shutdown Rx profile threshold

To shut down Ethernet traffic when it falls below the Rx threshold:


In the Fault criteria section:
1. Enable or disable Ethernet shutdown when the radio performance degrades below the
specified profile.
 In the Ethernet shutdown Rx profile threshold field, select the threshold profile.
Note: This option is only enabled if ACM adaptive mode is active.
8.7 Viewing radio status

8.7.1 ODU status
To view the ODU status parameters:
In the Status parameters section:
 ODU type – Indicates the ODU used in the system (e.g., ODU‐SP).
 Tx/Rx frequency separation – Displays Tx/Rx separation values.
 Tx/Rx level – Displays current Tx/Rx level values.
 MSE – Displays Mean Square Error value, which quantifies the performance of the
receiver.
 XPI level – Displays the current cross polarization interference value.
 Defective blocks – Indicates the number of blocks in which errors were detected. The
larger the amount, the poorer the radio link quality.

8.7.2 MRMC status
To view MRMC status:
In the MRMC configuration section:
 MRMC script – Displays the current selected radio script.
 Occupied bandwidth (MHz) – Displays the actual bandwidth occupied by the radio signal.
This should not be confused with Channel Spacing, which indicates the allocated
bandwidth for the RF channel.
If an asymmetrical script is enabled, this field will be replaced with separate Rx and Tx
occupied bandwidth status.
 Operational mode – Displays the ACM mode: ACM Adaptive, ACM Fixed, or Regular (non
ACM radio script).
 Min adaptive ACM profile – Indicates the minimum configured profile that will never be
exceeded when ACM is active.
 Max adaptive ACM profile – Indicates the maximum configured profile that will never be
exceeded when ACM is active.
 Adaptive Tx power admin – Indicates whether power admin is enabled. When enabled,
the radio power is adjusted to the current profile that is being used.


8.7.3 Current Tx status
The Current TX section displays ACM transmission settings
To view current Tx settings:
In the Current TX section:
 ACM adaptive profile – Indicates the current ACM profile used for transmission.
 QAM – Indicates the current modulation used for transmission.
 Bitrate – Indicates the current transmitted bit rate, in Mbps.
 Number of TDM channels – Indicates the number of TDM channels.
8.7.4 Current Rx status

The Current Rx section displays ACM received settings
To view current RX settings:
In the Current Rx section:
 ACM adaptive profile – Indicates the current ACM profile used by the receiver.
 QAM – Indicates the current modulation used by the receiver.
 Bitrate – Indicates the current receiving bit rate, in Mbps.
 Number of TDM channels – Indicates the number of TDM channels.

8.7.5 Current remote Rx level
To view the current remote Rx level:
 Remote Rx level – Indicates the current Rx level of the remote unit.
8.7.6 Remote radio status

To view remote radio status:
 Remote communication – Indicates the current communication status of the remote unit.
 Remote Rx level – Indicates the current Rx level of the remote unit.


8.7.7 XPIC status
XPIC enables two radio carriers to use the same frequency with a polarity separation between them by
adaptively subtracting from each carrier the interfering cross carrier at the proper phase and level, with
the ability to detect both streams even under the worst levels of cross polar discrimination interference
such as 10 dB.
To view XPIC status:
In the XPIC parameters section:
 XPI enabled – Indicates whether XPIC is enabled.
8.8 Multi Channel ABC

Multi Channel ABC enables two separate radio links to be shared by a single Ethernet port. This provides
an Ethernet link over the radio with double capacity, which still behaves as a single layer‐2 MAC. The
two separate radio links may be implemented using XPIC or separate frequencies.
Multi Channel ABC feature is applicable for Ethernet data only. For TDM, each link remains separate,
and users can decide to configure trails to either radio (or both, by using SNCP or ABR).
This feature is available only for IFUs which are inserted in a shelf.
 Ensure that the two radio links are using the same radio script in order for Multi Channel
ABC to perform at maximum efficiency.
Multi Channel ABC cannot be used in tandem with the following features:
 1+1 HSB
8.8.1 Enabling and disabling Multi Channel ABC

Multi Channel ABC configuration options are only displayed after Multi Channel ABC is enabled.
To enable Multi Channel ABC:
In the Multi Channel ABC section:
In the Multi Channel ABC admin field, select Enable, and then click Apply.

To disable Multi Channel ABC:
In the Multi Channel ABC admin field, select Disable.
8.8.2 Multi Channel ABC traffic blocking

Since traffic is distributed between both carriers at layer 1 level, a failure in one of the radio links may
cause all Ethernet frames to be affected. Therefore, Multi Channel ABC performs actions to ensure
graceful degradation in the case of a failure.
You can configure a link to be blocked, so that the transmitter does not distribute data to this link and
the receiver ignores it when combining.
By default, blocking is disabled.
To enable traffic blocking:
1. Enable traffic blocking for slot #1.
 In the Block radio (slot #1) field, select On. All traffic is sent to radio part in slot #2.
2 Enable traffic blocking for slot #2:
 In the Block radio (slot #2) field, select On. All traffic is sent to radio part in slot #1.
8.8.3 Setting Multi Channel ABC thresholds

You can configure the Multi Channel ABC to shut down links when they drop below configured
thresholds.
To configure Multi Channel ABC thresholds:
1. Enable or disable shutting down the link if it drops below the signal degrade threshold.
 In the Signal degrade admin field, select Enable or Disable.
2. Enable or disable shutting down the link if it drops below the excessive BER threshold.
 In the Excessive BER admin field, select Enable or Disable.
3. Click Apply to save your settings.
8.9 Radio diversity

The Radio diversity feature can be used with configurations that are using two antennas. It is
implemented at the base‐band level and thus requires no special ODU connections or upgrades.
There are two modes for using two antennas with a single system: 1+0 IF combining and 1+1 Space
diversity.

8.9.1 1+1 space diversity
1+1 Space diversity is a feature that enables the system to dynamically choose the best received signal
between two radio carriers (configured as 1+1 HSB) at every moment. This allows data flow to be
unaffected by unwanted physical events affecting the radio channel, such as fading.
The decision for the best signal line output is based upon performance of the modems.
8.9.1.1 Enabling radio diversity

To enable radio diversity:
In the Radio diversity section:
In the Radio diversity type field, select Space diversity and click Apply.
8.9.1.2 Viewing radio diversity status

To view the diversity status:
In the Diversity status section:
 Switch Counter ‐ Displays the number of times that there was a switch between the main
and standby IFUs
 Receive radio traffic – Indicates which ODU is providing the signal to the active IFU.
 Operation mode ‐ Displays whether Radio diversity is enabled.
8.9.1.3 Configuring revertive parameters

The Revertive mode feature enables the system to automatically revert to the local ODU after it has
switched to the mate ODU.
To automatically revert to the local ODU after it has switched to the mate ODU:

In the Revertive parameters section:
1. Enable the system to revert back to the primary ODU
 In the Revertive mode field, select Revertive.
2. Specify the primary ODU.
 In the Primary ODU field, select Local or Mate.
3. Specify the delay for reverting back to the primary ODU.
 In the Revertive timer field, enter the number of seconds for the system to wait before
reverting.
4. Click Apply.
8.9.1.4 Manually switching the active radio

The system only reverts to the primary ODU when the signal contains no errors. If the system does not
allow you to switch radios using the Switch Request button, you can use the Force to radio option to
manually switch the active radio.
To manually switch the active radio:
In the Force active section:
 Request the system to switch radios.
Click Switch Request to send a message to the system to switch to the opposite
radio.
 Force the system to switch radios.
In the Force to radio field, select Local radio or Mate radio.
8.9.2 1+0 IF combining diversity

1+0 (IFC ‐ IF combining) is a feature for configurations that use two antennas with a single ODU with two
Rx ports and a single IFU. The selected signal line output is based upon the Rx signal at the ODU.
To enable the radio IF interface:

Enable or disable the radio IF interface.
 Select Enable or Disable from the Radio IF interface field drop down list.
Note: Changing the Radio IF interface requires a system reset.
The Radio IF operational status field displays the current status of the radio interface.


8.9.2.1 IF combining parameters
When enabled, IF Combining parameters are located at the bottom of the Radio Parameters window.
To configure IF combining parameters:
Select Configuration > Radio > Radio Parameters.
In the If combining parameters section:
1. Specify the delay calibration mode.
 For Automatic delay calibration, click Calibrate. The system automatically calibrates
the required delay between the signals from the main and diversity antennas.
Automatic delay calibration can only be performed when the system is error‐free
and there are no negative weather conditions.
The Automatic delay calibration field displays the system status of the automatic
delay calibration feature.
 Success –Indicates that the system has successfully calibrated the signal delay
 Failure –Indicates that the system cannot automatically calibrate the signal
delay.
 No action –Indicates that the system has not performed an automatic delay
calibration.
 For Manual delay calibration, in the Delay calibration field, enter the number of
nanoseconds to delay between the main and diversity signals.
Manual delay is used only for Combined mode.
2. Select the ODU mode.
 In the ODU mode field select Main, Diversity, or Combined.
Main ‐ Only the main antenna signal is selected.
Diversity ‐ Only the diversity antenna signal is selected.
Combined ‐ The best signal from both antennas is selected.
 To use Combined mode, you must perform delay calibration.


3. Select which antenna is the source for the external connector.
 In the RSL connector source field, select either Main or Diversity.
Main ‐ The main antenna is selected.
Diversity ‐ The diversity antenna is selected.
Rx level diversity – Indicates the Rx level of the diversity antenna.
Rx level combined – Indicates the Rx level of the combined signals.
8.9.3 Frequency diversity

Frequency diversity is built on top of regular 1+1 HSB, and provides an additional layer of protection:
 1+1 HSB protects against hardware failure.
 Frequency diversity protects against fading, multipath in dispersive channel, and
interferences that may occur in the radio channel.
Frequency diversity is based on the fact that two radio channels which are separated by using different
frequencies are different enough in their physical characteristics that a fade affecting one frequency is
very unlikely to affect the other frequency.
 Both active and standby units transmit the same radio frame at the same time using
different frequencies.
 Both IFUs in a 1+1 HSB pair receive a radio signal from across the link.
 The baseband signal from the standby IFU is sent towards the active IFU at all times. The
active IFU therefore receives two signals; one from its own radio and another from its
mate’s radio.
 The active unit performs as a “master” for hitless switching. It chooses between the two
data streams based on data quality and early stress indications received from the radio.
 The switching mechanism is revertive. If no failure is found in any channel, data will be
taken from the master radio.
 The master radio is always the unit acting as “active” in the 1+1 HSB configuration.
 The chosen radio stream is sent normally towards the system’s switching fabric and line
interfaces.

8.9.3.1 Enabling frequency diversity
To enable frequency diversity:
In the Radio diversity section:
1. In the Radio diversity type field, select Frequency diversity.
2. Click Apply.
Configurable options after enabling frequency diversity:
 Frequency diversity enabled/disabled (to be operational, 1+1 HSB must be enabled as
well)
 Revertive mode enable/disable
 Primary radio for revertive switches
 Revertive timer
 Switching commands
 Force to radio
 Manual switch
 Clear switch counter command


9. Interface configuration
9.1 Local system configuration
The Management page enables you to define local and remote IP addresses and parameters.
9.1.1 IP configuration
In the Local IP Configuration section, configure the IP address of the IFU. In the Remote IP Configuration
section, configure the IP address and subnet mask for the remote site.
To configure local IP settings:
In the Local IP Configuration section:
1. Enter the IP address of the local unit, its subnet mask, and the default gateway.
2. Enter the Floating IP address.
 The floating IP address provides a single IP address for direct access to the current
active main unit.
HW address is a read‐only field that displays the MAC address of the local unit.
To configure remote IP settings:
 Select Configuration > General > Management.
In the Remote IP Configuration section:
1. Enter the IP address of the remote unit and its subnet mask.
2. Click Open Remote to open the remote unit's management page.


9.1.2 Management ports
To configure management ports settings:
In the Management ports section:
1. Specify the number of ports that will be used for management data.
 In the Number of ports field, specify the number of ports.
The IFU has three ports for local management: Port 7, Port 6 and Port 5. You may
enable none or up to 3 ports.
2. Configure the management mode of operation
 Select In‐band or Out of band from the Type field drop down list.
In‐band management refers to a method in which the network management
software sends management packets through the same network it is managing.
Out‐of‐band management uses an overlay network to communicate with the
managed elements.
In the In‐band Management VLAN ID field, specify the VLAN ID that will be used to
manage the unit, when the In‐band management type is used.
Out‐of‐band management uses the Wayside Channel (WSC) for management
access to the IFUs in the network. An external switch using some form of STP
should be used to obtain resilient management access and resolve management
loops.
3. Allocate bandwidth to the specified ports.
 In the Capacity field, select the bandwidth that will be allocated to the port(s).


4. Enable or disable auto negotiation.
 Select On or Off from the Auto negotiation field drop down list.
5. Specify the port bit rate.
 In the Rate field, select the bit rate you want for the port.
6. Specify the port duplex.
 Select Half or Full from the Duplex field drop down list.
7. Specify whether to block management frames towards the line interface.
 Select Enable or Disable from the Block management frames field drop down list.
 This option applies only if the Ethernet application types is configured as Single Pipe.
8. Click Apply.
9.2 Network system configuration

The IP table page allows you to configure the characteristics of the peer port, which the local port of the
element is connected to.
Each IFU port has its own IP table, allowing the configuration of the characteristics of the peer port to
which it is connected.
To configure peer port settings:
Select Configuration > General > IP Table.


In the IP Table section:
1 Expand a port to open its IP table.
 Click the + at the beginning of the line.
2. Specify the peer MAC address.
 In the Peer MAC address field, enter the MAC address of the peer port.
3. Specify the peer IP address.
 In the Peer IP address field, enter the IP address of the peer port.
4. Specify the peer slot ID.
 In the Peer slot ID field, enter the slot ID of the IFU where the peer port is located.
The slot can be from 0 to 6, where 0 is used when the other side is a standalone
unit, and 1‐6 are used for the other side’s XC slot IDs.
5. Specify the peer port number.
 In the Peer port number field, enter the peer port number.
6. Optionally, add a description of the peer port.
 In the Peer description field, add a general description of the peer port.
7. Configure the LLDP protocol for the selected port.
 Select Disable, Enable transmit only, Enable receive only, or Enable receive and
transmit from the LLDP admin drop down list.
Enable transmit only
LLDP agent will transmit LLDP frames on this port and it will not update
information about the remote systems.
Enable receive only
LLDP agent will receive, but it will not transmit LLDP frames on this port.
Enable receive and transmit LLDP agent will transmit and receive LLDP frames on
this port.
Disable (default)
LLDP agent will not transmit or receive LLDP frames on this port.
8. Click Apply to save your configuration settings.

9.3 Auxiliary channels
9.3.1 Wayside channel
In the Wayside channel page, you can enable and configure wayside channel settings.
Wayside channel and PTP optimized transport mode are mutually exclusive features. You should disable
the PTP optimized transport mode before enabling the Wayside channel.
To configure the Wayside channel:
Select Configuration > Interfaces > Wayside channel.
In the Wayside channel configuration section:
1. Enable or disable the channel.
 In the Wayside admin field, select Enable if you want to activate the channel.
2. Specify channel capacity.
 In the Capacity field, select Narrow or Wide.
3. Enable or disable auto negotiation.
 In the Auto negotiation field, select On or Off.
Selecting On allows the system to control the data flow between the wayside
channel and other ports activated in the system.
4. Specify the duplex mode.
 In the Duplex field, select Full or Half duplex.
5. Specify the port rate.
 In the Rate field, select the data rate for the port.
6. Click Apply.


9.3.2 User channel
In the User channel page, you can enable and configure user channel settings.
To configure the user channel:
Select Configuration > Interfaces > User channel.
In the User channel configuration section:
1. Enable or disable the user channel.
 In the Admin field, select Enable or Disable.
2. Specify the channel type.
 In the Type field, select a channel.
Asynchronous RS‐232
Asynchronous V.11/X.21
3. Click Apply.


9.3.3 EOW
The EOW page displays the EOW (Engineering Order Wire) channel status.
To configure the EOW channel:
Select Configuration > Interfaces > EOW.
In the EOW configuration section:
 Admin – Indicates whether EOW is enabled or disabled.


9.4 Port configuration
9.4.1 E1 ports
In the E1 ports page, you can configure E1 port parameters.
To configure E1 ports:


9.4.1.1 Using an E1/T1 T-card
The T‐Card is not a stand‐alone entity within the XPAND IP+ IFU. When inserted in the system, the new
interfaces become integral interfaces of the XPAND IP+.
As an example, if you insert a 16 x E1 T‐Card in the IFU, no special menu will appear for it. Instead, E1s
#17‐32 will be added to the existing 1‐16.
9.4.1.2 Viewing configured E1 ports

To view E1 ports:
In the E1 Ports table:
 Enabled – Indicates whether the port is enabled.
 Interface – Indicates the port number.
 Priority – Indicates the port priority.
 Current BER – Indicates the current BER level.
9.4.1.3 Configuring E1 port thresholds

To configure port thresholds:

In the All ports section:
radio link.
 In the Excessive BER threshold field, select a value from the drop down list.
link.
 In the Signal degrade threshold field, select a value from the drop down list.
3. Click Apply.
In the Line coding section:
 Line code 1‐8 and 9‐16 – Display the T1 line coding, which can be B8ZS or AMI.


9.4.2 DS1 ports
In the DS1 ports page, you can configure DS1 port parameters.
To configure DS1 ports:
9.4.2.1 Viewing configured DS1 ports

To view DS1 ports:

In the DS1 Ports table:
 Interface – Indicates the port number.
 Priority – Indicates the port priority.
 Current BER – Indicates the current BER level.
9.4.2.2 Configuring DS1 port thresholds

To configure port thresholds:
In the All ports section:
radio link.
 In the Excessive BER threshold field, select a value from the drop down list.
link.
 In the Signal degrade threshold field, select a value from the drop down list.
3. Click Apply.
In the Line coding section:
 Line code 1‐8 and 9‐16 – Display the T1 line coding, which can be B8ZS or AMI.


9.4.3 STM-1/OC-3 (T-card) ports
The purpose of the STM‐1/OC‐3 interface is to provide an interface for up to 63 E1s inside a standard
channelized STM‐1 signal, or 84 DS1s for OC‐3 channels.
Each E1/DS1 is transported by a VC‐12 container (or DS‐1 in VC‐11), which behaves like a regular line
interface. TDM trails can be configured ending in VC‐11/12 in the same manner as they are configured
for E1/DS1 interfaces.
The STM‐1/OC‐3 T‐card includes a LED that indicates the status of the interface:
 Critical or major severity alarm raised: RED
 Minor or warning severity alarm raised: YELLOW
 No SFP detected or STM‐1/OC‐3 interface disabled: OFF
 Otherwise the LED is GREEN
9.4.3.1 Configuring STM-1 ports

To configure the STM‐1/OC‐3 T‐card interface:
 Select OC‐3 Ports for a T1 board.
In the STM‐1 Configuration section:
1. Enable or disable the port.
 Select Enable or Disable from the Port Admin field drop down list.
2. Enable or disable the mute Tx option on the interface.
 Select Mute or Unmute from the Mute Tx field drop down list.
 If muted, the radio will still receive signals, but will not transmit any.


3. Specify the outgoing signal clock source.
 Select Internal clock, Loop, or STM‐1 VC from the Outgoing signal clock source field
drop down list.
The clock source and the clock source status may be different when the
configuration does not match the current clock source in use, due to the signal
failures listed below.
If you choose Internal Clock (the default option), the quality will be SMC/SEC (ITU‐
T G.813).
If you choose Loop (CDR mode), the signal clock source will be taken in accordance
with the following table:
# LOF from framer LOS from optics Mode of operation Clock source
1 LOF LOS Free run/holdover Local clock
2 LOF NO LOS Free run/holdover Local clock
3 NO LOF LOS N/A Local clock
4 NO LOF NO LOS Lock mode (loop timing) CDR
If you choose STM‐1 VC, the signal will be synchronized to the signal clock derived
from a TDM trail. The clock will be taken from the first VC‐12 configured in the
STM‐1 port.
There is no web support for this, but there is a way to change the VC source
through the CLI using the following commands:
cd interfaces/sdh/stm1/get sync‐vc (shows the VC that the system will use as the
clock and sync)
Set sync‐vc XX (XX = VC number).
 Clock source status – Indicates the current clock source.
4. Specify the VC channel that is used to synchronize the STM‐1 interface.
 In the Synchronization VC field, specify the VC channel.
5. Enable or disable AIS VC signaling.
 Select Enable or Disable from the AIS VC Signaling Admin field drop down list.
When enabled, if a signal failure at the trail outgoing from the STM‐1 interface
occurs, the system will signal AIS at the VC level (AIS‐V) in the V5 byte of the
overhead.
6. Configure the behavior of the transmitting line in a 1+1 HSB configuration.
 Select Normal or Uni‐direction MSP from the Line Tx protection mode field drop down
list.
In Normal mode the stand‐by signal is silenced. The redundant STM‐1 will not
transmit signals unless the primary IFU performs a switch due to a failure.
Choose Uni‐direction MSP when the system is configured for 1+1 with STM‐1
cards. Both cards will transmit, and the decision of which one will actually function
will be decided by other equipment connected to it.
7. Click Apply to save your configuration changes.

To configure STM‐1 trace identifiers:
In the Trace Identifier section:
1. Configure the string used as the transmitted STM‐1/OC‐3 signal J0 trace identifier.
 Transmitted field, specify the trace identifier used to verify ongoing connection to the
receiver.
2. Configure the J0 trace identifier signal that is expected to be received on the STM‐1/OC‐3
interface.
 Expected field, specify the trace identifier that will be used to verify ongoing
connection to the remote side of the link.
3. Configure the length of the STM‐1/OC‐3 signal J0 trace identifier.
 Select a string length from the String Length field drop down list.
 Received ‐ Indicates the J0 trace identifier signal that was received on the on the STM‐
1/OC‐3 interface.
9.4.3.2 Configuring STM-1 thresholds

To configure STM‐1 thresholds:
In the Thresholds section:
radio link.
 Select the threshold value from the Excessive BER field the drop down list. The value
can be 1e‐3, 1e‐4, or 1e‐5.
link.
 Select the threshold value from the Signal degrade field the drop down list. The value
can be 1e‐6, 1e‐7, 1e‐8, or 1e‐9.
3. Click Apply.


9.5 All ODU
The All ODU page allows you to activate support for the All ODU enclosure.
When enabled, the enclosure controller can then be powered to monitor fan failure alarms.
 External Alarm Input #1 becomes an output, which together with 3.3V is used to drive the
enclosure’s electronic board.
 External Alarm Input #2 is set with a specific text & severity, and is used to monitor any
enclosure fan failure, and to raise an alarm for it (polarity change was required to adapt it
to the enclosure behavior).
To enable All ODU support:
Select Configuration > General > All ODU.
In the All ODU section:
Enable or disable the All ODU interface.
 Select Enable to activate the ALL ODU enclosure interface.
 Select Disable to disable the ALL ODU enclosure interface.


10. Ethernet traffic
10.1 Ethernet ports
The Ethernet ports page, you can view and configure Ethernet port settings.
10.1.1 Configuring Ethernet ports

In the Managed Switch, Metro Switch, or Single Pipe Ethernet Ports area, you can configure the
parameters for a specific port on the IFU.
1. Select Configuration > Interfaces > Ethernet ports.
2. Expand a port in the list to open its configuration options.
 Click the + icon in the left column to open port configuration.
In the Ethernet ports configuration section:
3 Enable or disable the port.
 In the Port admin field, select Enable or Disable.
4. Specify the connector type.
 In the Connector type field, select RJ 45 or Optical.
5 Specify the port type.
 In the Type field, the option depends on the Ethernet application:
Single Pipe is not a valid field.
Managed Switch ‐ option can be Access, Trunk or Hybrid.
Metro Switch ‐ option can be Customer Network or Provider Network.


6 Specify the default VLAN ID.
 In the Default VLAN ID field, enter the VLAN ID number.
This option isn’t applicable for Single pipe applications.
7 Enable or disable auto negotiation.
 In the Auto Negotiation field, select On if you want the system to control the flow of
data.
8 Activate or deactivate the traffic control mechanism.
 In the Flow control field, select On or Off.
Flow control is only used for the single pipe switch configuration.
9 Specify the port service type.
 In the Port service type field, select Service network point or Service access point.
10 Click Apply.
10.1.2 Configuring automatic state propagation

Automatic state propagation enables propagation of radio failures back to the line, to improve the
recovery performance of resiliency protocols (such as xSTP).
The feature allows the user to configure which criteria will force GbE port (or ports in case of “remote
fault”) to be muted / shut down, to allow the network find alternative paths.
In Single Pipe mode, upon radio failure, Ethernet port 1 is muted when configured as “optical” or
shutdown when configured as electrical.
In Managed Switch or Metro Switch mode, the switch’s Radio port (Ethernet port 8) is forced to be
disabled Ethernet port 8 port cannot be muted, but only disabled in both directions.
In 2+0 Multi Channel ABC mode, Automatic State Propagation can be triggered upon a failure in a single
IFU or upon a failure in both IFUs. This behavior is determined by user configuration.
It is recommended to configure both ends of the link to the same “Automatic State Propagation” ("GbE
Tx Mute Override") configuration.
If the link uses in‐band management, when the port is muted or shut down, management distributed
through the link might be lost. If this occurs, the unit will not be manageable. The unit will only become
manageable again when the port is un‐muted or enabled.

To configure automatic state propagation for an Ethernet port:
In the Automatic state propagation field underneath the ports table:
Enable or disable Automatic state propagation.
 Select Enable or Disable from the Automatic state propagation field drop down list.
In the Fault criteria section:
Specify which faults should be propagated back to the line.
1. Enable or disable Ethernet shutdown when the radio performance degrades below the
specified profile.
 In the Ethernet shutdown Rx profile threshold field, select the profile.
This option is only enabled if ACM adaptive mode is active.
2. Specify whether local excessive BER will be propagated as a fault.
 In the Local Excessive BER field, select Enable or Disable.
3. Specify whether a Loss of Carrier alarm will be propagated as a fault.
 In the Local LOC field, select Enable or Disable.
Relevant only for optical GbE interfaces in single pipe applications.
4. Enable or disable these settings for remote interfaces.
 In the Remote Fault field, select Enable or Disable.
5. Click Apply.
When Automatic State Propagation is enabled:
 Radio Loss of Frame faults will always be propagated.
Local LOF will be set to Enable.
 Radio link ID mismatch faults will always be propagated.
Link ID Mismatch will be set to Enable.


10.1.3 Viewing Ethernet port status
The Ethernet ports table displays the configuration settings for each port.
To view Ethernet port status:
In the Ethernet ports table:
 Operational status – Indicates whether the port is Up or Down.
A check mark indicates that this port is enabled.
An X indicates that the port is disabled.
 Interface – Displays the port number.
 Connector type – Displays whether this port is using copper (RJ‐45) cable or optical fiber.
 Speed & duplex – Displays available parameters regarding rate and duplex:
Auto negotiation – Indicates whether auto‐negotiation is enabled for the port.
Rate – Indicates the configured rate for the port.
Actual rate – Indicates the actual rate for the port.
Actual duplex – Indicates whether actual duplex is Half or Full.
 Function – Displays whether the port is being used for Trunk, Access, or Management.
For Metro switches – Indicates whether the port is being used for C/N, P/N, or
Management.
 VLAN ID – Displays all allowed VIDs for this port.
 Learning – A check mark indicates that Port learning is enabled. An X indicates that Port
learning is disabled.
 Flow control – Displays whether Flow control is On or Off.
 Service type – Displays whether this port is a network or access point.

10.2 LAG ports
10.2.1 Defining a LAG port
Link aggregation allows the user to group several ports into a single logical channel bound to a single
MAC address. Traffic sent to the ports in such a group is distributed through a load balancing function.
The group is called a LAG.
 Only traffic ports (including radio port) can belong to a LAG
 Management ports / WSC ports cannot be grouped in a LAG
 LAG is supported in IFUs configured as Managed or Metro switch
 LAG is not supported in a Single Pipe mode
 All ports in a LAG must be in the same IFU (same switch)
 There may be up to 3 LAGs per IFU
 A LAG may contain from 1 to 5 physical ports
 LAGs are virtual ports that do not permanently exist in the system
 When a LAG is created, it will automatically inherit all the ports’ characteristics, except for
the following:
xSTP role (edge, non‐edge)
Path cost
 The LAG will initially receive default values for these parameters
 Dynamic Link Aggregation (LACP) is not supported
Grouping ports in a LAG
 Ports 1‐2 (GBE ports) and ports 3‐7 (FE only ports) cannot be in the same LAG group even
if the GBE ports are configured as 100Mbps.
 Radio port (port 8) may be in a LAG with the GBE ports only.
The following settings must be identical on all LAG ports:
 QoS configuration (Classification Criteria, Port ReMap table, Egress Scheduler)
 Speed (data rate)
 Type (access/trunk or CN/PN)
 interface (electrical/optical)
 Full Duplex
 Auto‐Negotiation
 VLANs
 Port Learning State
Ports with different settings will not be added to the LAG.
Note: ports with CFM MEP/MIPs will not be added to a LAG, which may have its own MEP/MIPs.


Parameters that cannot be configured on ports that are already grouped in a LAG:
 Admin status
 Flow control
 Ingress rate limiting Policer name
 Shaper (egress rate limiting)
 Peer port parameters
MAC address
IP address
Slot ID
Port number
Description
To define a LAG port:
2. Click the Create LAG port button underneath the ports table.
In the Create new LAG port window:
1. Select ports to include in the LAG.
 Ports selected for the LAG group are highlighted; and ports selected for deletion are
cleared in the window.
 Only traffic ports (including a radio port) can belong to a LAG group. The following
groups of ports can be in the same LAG
Ports 1‐2 and 8 (GBE ports and radio)
Ports 3‐7 (FE only ports)
 The system will not allow selection of ports with different configurations (such ports
will not be highlighted).
 Ports from different groups cannot be in the same LAG:
 For GBE LAG groups, both interfaces must be of the same type (electrical/optical).
 A radio port can be in a LAG with either electrical or optical line ports.
 All ports in a LAG group must be of the same data rate (10, 100, or 1000 Mbps).


 A GBE LAG group may include the radio port.
 The configurations must be identical in all ports before adding them to the LAG logical
port.
2. In the LAG port to create field, select a name for the LAG port.
 A LAG port can be configured as “LAG #1, #2, #3”, since there can be up to three LAG
ports in the system.
3. Click Apply.
10.2.1.1 Configuring a LAG port

2. Expand a LAG port in the list to open its configuration options.
In the Ethernet ports configuration section:
3 Enable or disable the port.
 In the Admin field, select Enable or Disable.
4 Specify the port type.
 In the Type field, the option depends on the Ethernet application:
Single Pipe is not a valid field.
Managed Switch ‐ option can be Access, Trunk or Hybrid.
Metro Switch ‐ option can be Customer Network or Provider Network.
5 Enable or disable auto negotiation.
 In the Auto Negotiation field, select On if you want the system to control the flow of
data.
6 Specify the Ethernet rate.
 In the Ethernet rate field, select the rate for the port.
7 Enable or disable port learning.
 In the Learning field, select Enable or Disable.
8 Specify the port service type.
 In the Port service type field, select Service network point or Service access point.
9 Click the Allowed VIDs link below the port configuration options to assign VIDs to the LAG.

10.2.1.2 Configuring allowed LAG port VIDs
In the Ethernet allowed VIDs window, you can specify which VIDs are allowed for the LAG port.
To assign VIDs to a LAG port:
1 Select Configuration > Interfaces > Ethernet ports.
2. Expand a LAG port in the list to open its configuration options.
3. Click the Allowed VIDs link below the port configuration options.
In the Operations section:
1 Specify the operation to perform.
 In the Operation field, select:
Set ‐ to add the VLANs to the database.
Remove ‐ to remove the VLANs from the database.
Change name ‐ to change the VLAN name you specified previously.
Disable ‐ to suspend usage of the VLAN you specified.
Enable ‐ to activate the VLAN you specified.
2. Specify the start and end VLAN IDs.
 In the Start VID and End VID fields, enter the VLAN start and end IDs.
3. Click Apply.
The Ethernet‐allowed VIDs table displays the allowed VLANs for each LAG port.


10.2.1.3 Removing ports from a LAG
Ports removed from a LAG will keep the existing port parameters, but will be initially disabled in order to
prevent loops.
In addition, when the last port is removed from a LAG, the LAG will be deleted. Therefore it is necessary
to remove all MEP/MIPs from a LAG before removing the last port.
To remove ports in the LAG group:
2. Expand a port in the list to open its configuration options.
3. Click the Add or Remove ports from LAG port link below the port configuration options.
 Ports removed from a LAG will remain with their existing parameters, but will be
initially disabled to prevent loops.
 Deselecting all ports will clear the entire LAG port.
10.3 Configuring the Ethernet application type

Nera XPAND IP+ supports Single Pipe, Managed, and Metro switch configurations.
 Single Pipe is the default option, and does not require a license.
 Configuring the IFU to Managed switch or Metro switch requires a license.
To enable an Ethernet switch:
1. Select Configuration > Ethernet Switch > Switch Configuration.


2. Select the Ethernet application type:
 Single pipe ‐ Ethernet switching is disabled, whereby only a single Ethernet interface is
used for traffic and the unit operates as a point‐to‐point microwave Ethernet radio.
 Managed switch ‐ Ethernet switching is enabled and all the ports are used for traffic.
 Metro switch ‐ This method is the same as Managed switch, but must be enabled to
use Ethernet Q‐in‐Q provider switch.
3. Click Apply.
10.3.1 Single pipe

Single (Smart) Pipe is the default method, which allows only a single GBE interface for traffic (optical
GBE‐SFP or Electrical GBE, 10/100/1000 mbps). Traffic originating from any GBE interface will be sent
directly to the radio and vice versa.
 The Single Pipe method allows QoS configuration. Other FE (10/100 mbps) interfaces are
"functional" interfaces (WSC, Protection, Management).
Single pipe configuration
 Only one ingress port can be used: Port 1 (Opt. or Elec.) or Port 3 (RJ45)
 When one is enabled the other is disabled
 No need to configure VID membership
10.3.2 Managed switch

Managed Switch is an 802.1Q VLAN‐aware bridge, allowing L2 switching based on
VLANs. Traffic port can be configured as access, trunk, or hybrid ports.
Allowed egress
Type VLANs Allowed ingress frames
frames
Only untagged frames (or frames
Specific VLAN should be
Access tagged with VID=0 ("Priority Untagged frames
associated with the access port
Tagged")
A range of VLANs or all VLANs
Trunk should be associated with the trunk Only tagged frames Tagged frames
port
Specific VLAN is used for the
untagged frames
Hybrid Tagged and untagged frames Tagged frames
A range of VLANs are associated
with the tagged frames


Managed switch configuration
The Managed Switch method allows QoS configuration, and all Ethernet ports are allowed for traffic.
 Select Interfaces > Ethernet ports.
 Expand a port to open its configuration options.
 In the Port admin field, enable the port.
 In the Type field, configure the port type as Trunk, Access, or Hybrid.
 In the Unit allowed VIDs table, assign allowed port membership.
10.3.3 Metro switch

Metro Switch is an 802.1ad Provider Bridge, allowing Q‐in‐Q switching capabilities.
Traffic ports can be assigned as Customer Network or Provider Network ports.
Allowed egress
Type VLANs Allowed ingress frames
frames
Specific S-VLAN should be
Customer Untagged frames or tagged (C- Untagged frames of
associated with the
Network tag) frames tagged (C-tag) frames
customer network port
A range of S-VLANs or all Only S-tagged frames, (in S-tagged frames,
Provider S-VLANs should be accordance with the configured carrying the configured
Network associated with the "provider ether-type", which is provider ether-type,
provider network port 0x88a8 by default) (0x88a8 by default)
 Customer Network frames are encapsulated with a 2nd VLAN (S‐VLAN) and forwarded to a
PN port
 PN ports transport multiple encapsulated networks, each associated with a unique S‐VLAN
 CN ports remove the S‐VLAN towards a Customer interface
 S‐Tag Ether type can be configured to one of the following values: 0x88a8 (default),
0x8100, 0x9100, or 0x9200.
CN port configuration
 In the Type field, configure the port type as Customer Network.
 Configure the allowed S‐VLAN IDs.
 Enable port learning.


PN port configuration
 In the Type field, configure the port type as Provider Network.
 Configure the allowed S‐VLAN IDs
 Enable port learning.
 Set the Provider Port EtherType to S‐Tag.
10.4 Switch configuration

10.4.1 Changing the Ethernet application type
When the application type is enabled, in the Switch Configuration page allows you to modify the
Ethernet application type, and to configure Ethernet switch parameters.
To modify the Ethernet application type:
Select Configuration > Ethernet Switch > Switch Configuration.
In the Ethernet application type section:
Select or modify the application type: Single pipe, Managed switch, or Metro switch.
Note: Changing switch modes requires a reset
10.4.2 Configuring LAG load balancing

To configure the LAG load balancing method:


In the LAG load balancing section:
Specify the LAG load balancing method.
 Select Simple XOR for demos or lab test or HASH for real traffic.
Simple XOR performs XOR on the last three bits of the packet source MAC address (SA)
and the destination MAC address (DA), and according to the result, selects the link to
be used in the LAG.
The HASH mechanism distributes flows across multiple egress ports in a LAG. It uses a
proprietary scrambling function, and uses the last three bits (LSBs) of the DA, SA. This
means that two flows with the same three LSB bits, but different MSB bits, will still go
to the same port. Thus, the HASH will simply distribute more evenly.
10.4.3 Assigning port membership

To assign VLAN IDs to a port:
In the Unit allowed VIDs section:
1 Select the operation you want to perform for the VLANs.
 In the Operation field, select:
Set ‐ to add the VLANs to the database.
Remove ‐ to remove the VLANs from the database.
Change name ‐ to change the VLAN name you specified previously.
Disable ‐ to suspend usage of the VLAN you specified.
Enable ‐ to activate the VLAN you specified.
3. Define a unique name for the VLAN.
 In the Name field, enter the VLAN name.
4. Click Apply to save your VLAN definitions.
The defined VLANs are summarized at the bottom of the window.
 VLAN ID – Displays the specific ID for this VLAN.
 Name – Displays the configured name for the VLAN.
 Status – Indicates whether the VLAN is Active or Passive.
 Member Ports ‐ Lists which IFU ports allow this VLAN.


10.5 RSTP
The STP protocol page allows you to configure STP parameters.
This option is available only when the system operates in the Managed or Metro switch modes.
Spanning Tree Protocol (STP) ensures a loop‐free topology for any bridged LAN. Spanning Tree allows a
network design to include spare (redundant) links for automatic backup paths, needed for cases in
which an active link fails. The backup paths can be included with no danger of bridge loops, or the need
for manual enabling/disabling of the backup links.
Bridge loops must be avoided since they result in network “flooding”.
You can choose between the Fast Ring RSTP and the standard RSTP protocols as defined in IEEE 802.1D.
To configure the STP protocol:
Select Configuration > Ethernet Switch> STP Protocol.
In the STP Protocol section:
1. Specify the STP protocol.
 Select RSTP or Ring RSTP to enable STP.
 Select Disable to disable STP.
2. Click Apply.


10.5.1 Configuring RSTP priority
Configuring (Ring) RSTP priority allows you to determine the root bridge, providing more control over
the spanning tree path design.
There are two options for determining the root bridge:
1. The IFU with the lowest priority.
2. The IFU with the lowest MAC address.
The system first checks the priority field. If priority is configured for all of the RSTP IFUs, the root bridge
will be the IFU with the lowest priority.
If the system is unable to determine which IFU has the lowest priority – if the priority isn’t set for all of
the RSTP IFUs, or the priority is the same for all the IFUs – the root bridge will be the IFU with the lowest
MAC address.
You can avoid this by configuring priority for the path IFUs.
To specify the (Ring) RSTP root bridge:
Select Configuration > Switch> (Ring) RSTP.
In the (Ring) RSTP Configuration section:
Specify the bridge priority.
 In the Priority field, enter a number between 0 and 61440, in multiples of 4096 [4096,
8192, 12,288, etc.].
 By default the IFU priority is set to 32768. Enter a lower priority for the IFU that you wish
to serve as the root bridge.
10.5.2 Configuring Ethernet ports to support RSTP

In the Ethernet Ports that Support (Ring) RSTP table, each interface in the IFU can be configured to
support RSTP.
To configure supporting Ethernet ports for RSTP:
Select Configuration > Ethernet Switch> (Ring) RSTP.


In the Ethernet ports that support (Ring) RSTP section:
1. Expand a port to open its configuration options.
 Click the + icon next to the port number to open port configuration.
2. Configure the specific priority for the selected interface.
 In the Priority field, enter a number between 0‐240.
3. Configure the path cost for this port.
 In the Path cost field, enter a number between 1 and 200000000. The lower the value,
the more likely that port is used.
4. Specify whether the port is an edge port for the RSTP path.
 In the Edge port field, select Yes to enable the port as an edge port.
Non edge ports are used as service access ports that construct the ring.
5. Click Apply.
10.5.3 Viewing RSTP status

The RSTP and Ring RSTP windows enable you to view status information and to configure RSTP
parameters.
The configurations of RSTP and Ring RSTP parameters are identical.
To view RSTP status:
Select Configuration > Ethernet Switch> (Ring) RSTP.


The (Ring) RSTP Status section displays the current RSTP status information:
 Bridge ID – Displays the ID of the bridge in the current monitored IFU.
 Root ID – Displays the ID of the root bridge.
 Root Path Cost – Displays the cost of the path from the current monitored IFU to the root
bridge.
 Bridge Role – Displays the role of the bridge: Root or Designated.
10.6 QoS and rate limiting

The QoS feature allows you to configure classification and scheduling to ensure packets are forwarded
and discarded according to their priority.
QoS can be configured for all switch methods: Single pipe, Managed switch, and Metro switch.
To configure Quality of service and traffic rate limiting:


The QoS & rate limiting window contains three sections:
 Interfaces table
Summarizes the current rate limiting settings for the selected port.
 Advanced classifier links
Advanced QoS parameters that you can apply to ports.
 Copy ports configuration
Copies the QoS configuration of one interface port to a different interface port.
10.6.1 Configuring port traffic priorities

In the Traffic priorities section, specify the ingress classification settings, configure egress
shaping and scheduling, and attach policers to the port.
To configure traffic priorities for an Ethernet port:
1. Select Configuration > Ethernet Switch> QoS & rate limiting.
2. Expand a port to configure its classification and rate limiting settings.
 Click the + icon next to each port to view its details.


10.6.1.1 Ingress classifier
In the Ingress classifier section, apply classification settings to the port.
A frame ingressed to a port will be classified according to four levels of criteria.
To apply classification priorities to a port:
2. Expand a port to configure its traffic priorities.
In the Ingress classifier section:
3. Define the first criteria: MAC DA based.
 A frame ingressed to a port, carrying a MAC Destination Address (DA) that appears in
the Static MAC table, will be classified, its VLAN P‐bits will be overwritten (assuming
the frame egress is tagged) according to one of these options:
Disable ‐ No MAC DA classification or VLAN P‐bits will be overwritten. No marking.
Queue decision ‐ There will only be classification to queue. No marking.
VLAN P‐bits overwrite ‐ Only VLAN P‐bits will be overwritten (marked).
Classification according to a lower criteria.
Queue Decision & VLAN P‐bits overwrite ‐ Both classification and VLAN P‐bits
overwrite.
4. Define the second criteria: VLAN ID based.
 If the first criteria is not fulfilled (whether it is disabled, or the ingress frame does not
carry a MAC DA that appears in the Static MAC table), classification and/or marking
(VLAN P‐bits overwrite, assuming the frame egress is tagged) will be decided
according to classification options defined in the VLAN ID to queue table.
Disable ‐ No VLAN ID classification or VLAN P‐bits overwrite (marking).
Queue decision ‐ Only classification to queue. No marking.
VLAN P‐bits overwrite ‐ Only VLAN P‐bits overwrite (marking). Classification will be
according to lower criteria.
Queue decision & VLAN P‐bits overwrite ‐ Both classification and VLAN P‐bits
overwrite.


5. Define the third criteria.
 If both the first and second criteria are not fulfilled (whether they are both disabled,
or the ingress frame does not carry a MAC DA or VLAN ID that appears in the tables), it
will be classified according to the following configuration:
VLAN P‐bits ‐ Classification according to VLAN P‐bits. Queue is assigned according
to the VLAN P‐bits priority remap table.
IP TOS ‐ Classification according to IP TOS (IP precedence, or IP diffserv). Queue is
assigned according to IP P‐bits to queue table.
VLAN P‐bits over IP TOS ‐ Classification according to VLAN P‐bits, if the ingress
frame carries a VLAN and has an IP header.
IP TOS over VLAN P‐bits ‐ classification according to IP TOS, if the ingress frame
carries a VLAN and has an IP header.
Port (Default) ‐ If any of the above criteria is not fulfilled, the default classification
will be assigned to the ingress frame.
6. Specify the default classification.
 In the Default classification field, select which criteria should be used as the default
queue decision.
10.6.1.2 Egress scheduler

The Egress scheduler section of the QoS & Rate Limiting window determines how frames are output
from the queues.
 The fourth queue is the highest priority queue.
 The first queue is the lowest priority queue.
The following scheduling schemes are supported:
 Strict for all queues.
 Strict for fourth queue, and Hierarchical Round Robin (HRR) for third, second, and first
queues.
 Strict for fourth and third queues, and HRR for second and first queues.
 HRR for all queues.
In the HRR scheduling scheme, a weight is assigned to each queue, so that frames egress from the
queues according to their assigned weight, to avoid "starvation" of lower priority queues. In addition,
frames will egress in a "mixed" manner, to avoid "bursts" of frames from the same queue.
Each queue weight can be configured, and the weight will be used by the scheduler when the specific
queue is part of the HRR scheduling scheme.
The queue weight is a value between 1 and 32, and is configured via the queue weights table. The
default queue weights are 8,4,2,1.


To define how frames are output from the queues:
2. Expand a port to configure its rate limiting.
In the Egress rate limiting section
1. Enable or disable the egress shaper.
 In the Egress shaper field, select ON or OFF. The default is OFF.
2. Specify the scheduler rate.
 In the Shaper rate field, enter the Kb per second for the egress rate limit. The value
should be in steps of 64K for values less than 1 Mbps; 1M steps for values between 1
Mbps and 100 Mbps; and 10M steps for values between 100 Mbps and 1000 Mbps.
For 64 Kbps <= Rate <= 960 Kbps, in steps of 64 Kbps.
For 1000 Kbps <= Rate <= 100,000 Kbps, in steps of 1000 Kbps.
For 100,000 Kbps < Rate <= 1,000,000 Kbps, in steps of 10,000 Kbps.
10.6.1.3 Ingress rate limiting

The Ingress rate limiting section of the QoS & rate limiting window determines the port ingress rate
limit.
To specify the port ingress rate limit:
2. Expand a port to configure its rate limiting.


In the Ingress rate limiting section:
Select a policer to attach to the port.
 In the Attach policer field, specify which policer to attach to the port.
Up to five policers can be configured for each port.
Each policer has the following parameters:
 CIR ‐ Committed Information Rate.
 Rate limiting resolution:
For 64 Kbps <= CIR <= 960 Kbps, in steps of 64 Kbps
For 1000 Kbps <= CIR <= 100,000 Kbps, in steps of 1000 Kbps
For 100,000 Kbps < CIR <= 1,000,000 Kbps, in steps of 10,000 Kbps
 CBS ‐ Committed Burst Size.
 CBS is CIR‐dependent, and should be configured in bytes:
For 64 Kbps <= CIR <= 960 Kbps, 0 < CBS <= 273,404 bytes.
For 1000 Kbps <= CIR <= 100,000 Kbps, 0 < CBS <= 132,585 bytes.
For 100,000 Kbps < CIR <= 1,000,000 Kbps, 0 < CBS <= 4,192,668 bytes.
 Data type
 Rate can be limited based on the following data types:
None (no limiting)
Unknown unicast |Unknown multicast
Broadcast | Multicast | Unicast
Management | ARP | TCP‐Control
UDP | Non‐ UDP | Non‐TCP‐UDP
Queue1 | Queue2 | Queue3 | Queue4.
10.6.2 Advanced classifier configuration

10.6.2.1 Remapping VLAN P-bits priority
Remapping a table can be used to scale down some port priorities (for example, from 7:0 to 3:0), while
at same time scaling up some port priorities (for example, from 7:0 to 7:4), or to ensure that specific
priorities are reserved for specific purposes, by initially remapping all frames away from reserved
priorities (for example, from 7:0 to 4:0, protecting priorities 7:5).

10.6.2.2 VLAN-ID to queue

The VLAN ID to queue page allows you to assign a frame to a queue according to the frame’s VLAN‐ID.
The number of table entries depends on the number of VLANs that have a queue allocation definition.
By default, VLANs do not have a pre‐determined queue allocation.
To assign VLANs to queues according to VLAN ID:
2. Click VLAN ID to queue link in the Advanced section at the bottom of the QoS & rate
liming page.
In the Operation section:
1. Specify the operation type.
 In the Operation field, select Add or Delete.
3. Assign the frame to a queue.

 In the Queue field, specify to which queue to assign the frame.
4. Click Apply.
10.6.2.3 IP-P-bits to queue

The IP p‐bits to queue page allows you to assign a queue to a frame according to the frame’s IP priority
bits (IP‐Precedence or Diffserv), assuming the frame is an IP packet.
To assign a queue to a frame according to the frame’s IP priority bits:
2. Click the IP P‐bits to queue link in the Advanced section at the bottom of the QoS & rate
liming page.


In the IP priority options section:
1 Specify the IP type.
 IP Precedence configuration: 8 entries.
 DiffServ configuration: 64 entries.
2. Click Apply.
In the QoS IP P‐bits to Queue section:
1 Assign a queue to each IP priority bit.
2. Click Apply.
10.6.2.4 VLAN-P-bits to queue

The VLAN P‐bits to queue page allows you to assign a queue to a frame according to the frame’s P‐bits
(CoS), assuming the frame is tagged.
To assign a queue to a frame according to the frame’s priority bits:
2. Click the VLAN P‐bits to queue link in the Advanced section at the bottom of the QoS &
rate liming page.
In the QoS VLAN P‐bits to Queue section:
1. Assign a queue to each IP priority bit.
2. Click Apply.


10.6.2.5 Queue weights
The Queue weight page allows you to assign weights to each queue.
Queue weight is used by scheduler when the specific queue is part of HRR scheduling scheme.
To configure the QoS queue weights:
2. Click the Queue weights link in the Advanced section at the bottom of the QoS & rate
liming page.
In the Scheduler queue weight section:
1. Select a queue.
 In the Queue drop‐down menu, select one of the four QoS queues.
2. Specify the weight for the selected queue.
 In the Weight drop‐down menu, select the weight for that queue.
Queue weights can be configured in the range of 1‐32.
The higher the weight, the higher the priority for that queue.
3. Click Apply to save your configuration settings.
In the Qos queue weight table:
Click Refresh to display the current queue weights.
10.6.2.6 Attaching policers to a port
Adding policers to the policers list

The Policer list page enables you to add policy rules to a policer.
It is possible to configure up to five policy rules per policer.
When a policer definition is completed, it can be associated with any port, by attaching its name to the
port. This will enforce all policy rules of the policer on the port.
If a policer is attached to a port, you can use the detach command to remove the policer (and all its
policy rules) from the port.

To add a policer
2. Click the Policer list link in the Advanced section at the bottom of the QoS & rate liming
page.
In the Policer operations section:
2. Specify the policer name.
 In the Policer name field, enter a name for the policer.
Note that the name cannot include spaces – you can use underscores instead.
Viewing the policers list

To view the policers list:
page.
In the Policer list table:
 Policer name – Identifies the policer.
 Attached ports – Indicates to which ports the policer is attached.

Configuring policers
To configure policer parameters:
page.
In the QoS Policer list table:
1. Select a policer from the list and click its + icon to expand the policer details.
3. Specify the class name.
 In the Class name field, enter in a class name for the policer.
4. Specify the traffic type.
 In the Traffic type field, select the type of traffic to which the policer can be applied.
5. Specify the CIR.
 In the CIR field, enter in the CIR steps, in Kbps.
6. Specify the CBS.
 In the CBS field, enter in the number of bytes.
7. Click Apply.


10.6.2.7 Static MAC
The Static MAC table is used to load static MAC addresses to the forwarding table of the switch.
To define the static MAC table:
2. Click the Static MAC link in the Advanced section at the bottom of the QoS & rate liming
page.
In the Static MAC configuration section:
2. Specify the VLAN ID.
 In the VLAN ID field, enter the ID of the frame.
Each frame is attached with a VLAN ID.
Frames are learned and filed in the static MAC table under their VLAN ID.
3. Specify the static MAC address.
 In the Static MAC field, enter in the 48‐bit MAC address, in octet format
(xx:xx:xx:xx:xx:xx).
The static MACs are never flushed.
4. Specify to which port the frame should be forwarded.
 In the Forward to field, select the destination port.
5. Specify the classification and/or VLAN P‐bits overwrite (marking).
 In the Priority field, select a priority level.
6. Click Apply.
In the Qos Static MAC table:
 VLAN ID – Indicates the ID of the frame.
 Static MAC – Indicates the 48‐bit MAC address.
 Forward – Indicates which port the frame will be forwarded to.
 Priority – Indicates the priority level according to the QoS configurations.

10.6.3 Copying port priorities and rate limiting configuration
Since it is common to set QoS and rate limiting settings identically in several ports, the Copy Ports
Configuration option can be used to copy the configurations from one port to another. This saves
considerable time and prevents configuration errors.
To copy port configuration:
In the Copy Ports Configuration section:
1. Select the source port.
 Select the port from the Source port field drop down list.
2. Select the destination port.
 Select the port from the Destination port field drop down list.
3. Specify the copy operation to be performed.
 Copy priorities configuration ‐ Copies all traffic priorities using the ingress classifier.
 Copy rate limiting configuration ‐ Copies the policer configuration only.
10.7 Enhanced Traffic Manager

The windows in this section enable you to configure the parameters for the Enhanced Traffic Manager
(Enhanced QoS).
The Enhanced Traffic Manager feature applies to the egress traffic on the Radio port (where the
bottleneck is located). All the other ports function as usual.
A specific license is required to use the Enhanced Traffic Manager feature.
10.7.1 Preparing to use the Enhanced Traffic Manager

This section describes how to prepare the system to enable the Enhanced traffic manager to minimize
the impact on traffic.
In preparation for using the Enhanced traffic manager, you must disable to QoS egress shaper. You
should also classify the in‐band management traffic to ensure that the management signal is not
affected.
Additionally, if you are going to use the Precision Time Protocol (PTP) optimized transport feature,
disable the Wayside channel as well.


10.7.1.1 Classifying in-band management traffic
To configure the classification of the in‐band management signal:
In the Management ports section:
1. Select the management mode of operation
 Select In‐band or Out of band from the Type field drop down list
2. For In‐band Management VLAN ID, specify the VLAN. ID that will be used to manage the
unit, when the In‐band management type is used.
3. Click Apply.
10.7.1.2 Enabling Precision Time Protocol (PTP)

The Configuration & parameters window enables you to configure Precision Time Protocol features.
Precision Time Protocol (PTP) optimized transport feature is a special channel with low Packet Delay
Variation (PDV). This feature is essential for timing synchronization protocols e.g. IEEE 1588 and using
the sync features.
This protocol carries the signal for the sync clock and enabling PTP separates this signal (2 Mbps) from
the Traffic Manager signal.
To enable Enhanced Traffic Manager and Precision Time Protocol:
Select Configuration > Ethernet switch > Enhanced traffic manager > Configuration
& parameters.


In the Configuration section:
1. Enable the Enhanced traffic manager.
 In the Enhanced Traffic Manager field, select Enable.
2. Enable Precision Time Protocol.
 In the Precision Time Protocol field, select Enable.
3. Click Apply.
10.7.1.3 Disabling the wayside channel

PTP optimized transport mode and Wayside channel are mutual exclusive features. You must disable the
Wayside channel before enabling the PTP optimized transport mode.
To disable the wayside channel:
1. Select Configuration > Interfaces > Wayside channel.
2. In the Wayside admin field, select Disable.
3. Click Apply to disable the Wayside channel.


10.7.1.4 Configuring ETM priority queues
The Configuration & parameters window enables you to configure the size of the eight Enhanced Traffic
Manager queues.
Enhanced Traffic Manager supports eight priority queues of configurable buffer size and you can
configure the buffer size of each queue independently. The Queue Size section enables you to configure
the buffer size of the priority queues.
The maximum bandwidth of all the traffic queues is 4 Mbps.
When you enable the Enhanced Traffic Manager, radio port egress traffic scheduling and shaping are
performed in the Enhanced Traffic Manager module. Thus there are configuration changes that are
performed on the egress shaper and scheduler:
 Egress shaper must be disabled in the switch. Instead, egress shapers per priority queue
can be configured in the Enhanced Traffic Manager windows.
 Egress scheduler in switch will be degenerated to ‘All queues strict mode’. Instead, the
enhanced scheduler (based on WFQ algorithm) will be used in the enhanced QoS module.
This configuration will be performed automatically upon activating the Enhanced Traffic
Manager.
Enabling Enhanced QoS affects traffic on the radio port.
Changing queue size can impact traffic output.
To configure a priority queue:
Select Configuration > Ethernet switch > Enhanced traffic manager > Configuration
& parameters.


In the Queue size section:
1. Specify the buffer size for each queue.
 In the Queue size field for each queue, select the buffer size.
2. Click Apply.
10.7.1.5 Disabling the QoS egress shaper

To disable the QoS egress shaper:
1. Select Configuration > Ethernet switch > QoS & rate limiting to open the QoS & rate
limiting window.
2. Expand the radio port (Ethernet #8) to open the port configuration options.
In the Egress rate limiting section:
1. In the Egress shaper field, select Off.
2. Click Apply.
10.7.2 Enhanced Traffic Manager classification

10.7.2.1 Classification overview
The classifier is a basic element of each Enhanced Traffic Manager mechanism. Each frame is given a
Class of Service (CoS) and color (based on MEF 10.2 recommendations). Green frames refer to traffic
that complies with the configured CIR. Yellow frames exceed the CIR, but are still less than the
configured CBS.
Users can define several criteria that classify Ethernet frames. All the classification criteria are divided
into three hierarchies from the most specific to the general.


To enable Ethernet frames classification rules:
In the First hierarchy section:
1. Enable first hierarchy classification.
 In the First hierarchy section, select Enable for the classification criteria.
More than one criterion can be selected.
To enable all first hierarchy criteria, mark the Enable all checkbox.
To disable all first hierarchy criteria, mark the Disable all checkbox.
2. Enable second hierarchy classification.
 In the Second hierarchy section, at the 1st criterion: by in‐band management VLAN Id
field, select Enable.
3. Enable third hierarchy classification.
 In the Third hierarchy section, select Enable for the classification criteria.
More than one criterion can be selected.
To enable all first hierarchy criteria, mark the Enable all checkbox.
To disable all first hierarchy criteria, mark the Disable all checkbox.
4. Click Apply.

10.7.2.2 Default classification settings
You can configure the default frame color and CoS for all unclassified frames. Additionally, you can
change the queuing hierarchy of the CoS settings. The preconfigured setting for the CoS queuing
hierarchy is that CoS 0 has the highest priority and CoS 7 has the lowest.
To configure the default classification rule settings:
1. Select Configuration > Ethernet switch > Enhanced traffic manager > Classification.
2. Specify the default frame color.
 In the Default color field, select Green or Yellow.
3. Specify the default Class of Service.
 In the Default CoS field, enter the default Class of Service for frames.
4. Click CoS to Queue classification.


5. Expand a CoS.
6. Enter the new Queue index for that CoS.
 Each queue is a physical resource which can be assigned to accommodate frames of a
one or more CoS values.
7. Click Close to close the CoS to Queue classification window.
8. In the CoS & Color classification window, click Apply.
10.7.2.3 First hierarchy classification

The first hierarchy contains the classification rules that apply to the most specific traffic parameters. The
first hierarchy contains following classification criteria:
 Source MAC address
 UDP ports
 Known destination multicast MAC addresses
Any or all of these criteria can be used to classify the CoS for the frames.
Classification by source MAC address

Up to 16 separate MAC addresses can be configured.
To configure traffic classification rules according to the source MAC Address:
2. In the First hierarchy section, click Source MAC address to open the MAC addresses
configuration window.


In the Add new entry section:
1. Specify the number to be displayed in the # column.
 In the Row number field, select the number for this classification rule.
2. Specify the source MAC address.
 In the MAC address field, enter the MAC address that is being classified.
3. Specify the Class of Service.
 In the CoS field, select the traffic from this MAC address is designated with the
configured CoS (0 – 7).
4. Specify the traffic color.
 In the Color field, select the traffic from this MAC address is designated as Green
(compliant) or Yellow (non‐compliant).
5. Click Apply.
Classification by UDP ports

Up to eight UDP port entries can be configured.
To configure traffic classification rules according to the UDP ports:
2. In the First hierarchy section, click UDP ports table to open the UDP s ports configuration
window.


In the Add new entry section:
1. Specify the number to be displayed in the # column.
 In the Row number field, select the number for this classification rule.
2. Specify the source port.
 In the Source port field, enter the number of the source UDP port that is being
classified.
3. Specify the destination port.
 In the Destination port field, enter the number of the destination UDP port that is
being classified.
5. Specify whether the frames associated with this UDP port are designated as Green
(compliant) or Yellow (non‐compliant)
 In the Color field, select Green or Yellow.
6. Click Apply.
UDP port configurations recommendations:
 To specify classification by UDP source port only, you should configure the Destination
port parameter to 0.
 To specify classification by UDP destination port only, you should configure the Source
port parameter to 0.
 When you configure both the Source and Destination ports parameters contain non‐zero
values, the classification rule only applies to frames that match both the Source and
Destination ports.
Classification by known multicast MAC address

You can classify the CoS and color of traffic that is being sent to one of the predefined multicast MAC
addresses.
The Known multicast MAC addresses table contains a list of 66 destination MAC addresses which are
reserved for network protocols use.
To configure traffic classification rules according to the known multicast MAC addresses:
2. In the First hierarchy section, click Known Multicast MAC addresses table to open the
Known Multicast MAC addresses configuration window.

In the Known multicast MAC addresses window:
1. Expand a MAC address.
 Click the + icon next to a listed MAC address to view its details.
4. Specify whether the classification rules are applied to frames that are sent to this
destination MAC address.
 In the Validity field, select Valid or Not valid.
5. Click Apply.
10.7.2.4 Second hierarchy classification

The second hierarchy contains a classification rule according to in‐band management VLAN ID.
This classification rule is used to give high priority to the in‐band management frames in order to
prevent loss of the management signal on the remote sites.

To configure the classification of the in‐band management signal:
In the Second hierarchy section:
1. Enable in‐band management by VLAN ID.
 In the 1st criterion, by in‐band management VLAN ID field, select Enable.
2. Specify the in‐band management VLAN ID.
 In the VLAN ID field, enter the VLAN ID for the in‐band management signal.
This value is configured in the Management Ports section of the Management
window.
3. Specify the classification color for the in‐band management signal.
Green ‐ The in‐band management signal complies with the CIR.
Yellow ‐ The in‐band management signal complies with the EIR.
4. Specify the CoS value for the in‐band management signal.
 In the CoS field, enter a number between 0‐7 as the CoS value.
5. Click Apply to save the in‐band management signal classification configuration settings.
10.7.2.5 Third hierarchy classification

The third hierarchy contains the classification rules that apply to the most general traffic parameters.
The third hierarchy contains three classification criteria:
 VLAN P‐Bits to CoS

 DSCP/TOS Bits to CoS
 MPLS exp Bits to CoS

VLAN P-bits to CoS
The first classification rule in the third hierarchy manages the outgoing traffic according to the VLAN P‐
bits value that already exists on the frame.
You can configure the CoS and frame color of the traffic according to the P‐bits and CFI value of each
frame.
There are two CFI options for each P‐bit and a total of 16 classification rules according to the VLAN P‐
bits.
To configure VLAN P‐bits traffic classification rules:
2. In the Third hierarchy section, click VLAN P‐Bits to CoS and color classification table to
open the VLAN P‐bits to CoS configuration window.

In the VLAN P‐bits to CoS window:
1. Expand the combination of 802.1P Priority bits and CFI/DEI bit values.
 # ‐ Indicates the number of the classification rule.
 802.1 UP ‐ Indicates the P‐bits value for this classification rule. The range of options is
0 to 7.
 CFI/DEI ‐ Indicates the CFI/DEI value for this classification rule. The options are 0 or 1.
 Class of Service ‐ Indicates the configured CoS for this classification rule.
 Color ‐ Indicates the configured color for this classification rule.
4. Click Apply.


DSCP/TOS Bits to CoS
Differentiated Service Code Point (DSCP) or Type of Service (TOS) is a 6 bit length field inside the IP
datagram header carrying priority information.
IPv4 datagram header format
Classification by DSCP bits can be used for untagged frames, as well as 802.1Q tagged or provider VLAN
tagged frames. The classifier also supports classification by Traffic Class (TC) of the IPv6.
Whichever IP protocol version is used, the classifier extracts the adjacent field automatically.
To configure DSCP/TOC P‐bits traffic classification rules:
2. In the Third hierarchy section, click DSCP/TOS bits to CoS and color classification table to
open the DSCP/TOS bits to CoS configuration window.
In the DSCP/TOS bits to CoS window:
1. Expand a classification rule.
 Click the + icon for a selected rule to view its details.

4. Click Apply.
MPLS exp Bits to CoS

MPLS experimental bits are used to provide QoS capabilities by utilizing the bits set in the MPLS labels.
MPLS label format:
Classification by MPLS experimental bits is supported in both untagged and 802.1Q/provider tagged
frames.
To configure MPLS experimental bits traffic classification rules:
2. In the Third hierarchy section, click MPLS exp bits to CoS and color classification table to
open the MPLS exp bits to CoS configuration window.


In the MPLS exp bits to CoS window:
1. Expand a classification rule.
 Click the + icon for a selected rule to view its details.
4. Click Apply.
10.7.3 WRED
Weighted Random Early Detect (WRED) mechanism can increase capacity utilization of TCP traffic by
eliminating the phenomenon of global synchronization. Global synchronization occurs when TCP flows
that share bottleneck conditions receive loss indications at the same time. This can result in periods
during which link bandwidth utilization drops significantly as a consequence of simultaneous falling to
‘slow start’ of all the TCP flows.
To enable the Enhanced Traffic Manager’s WRED mechanism:
In the WRED admin section:
1. Click Enable.
2. Click Apply.


The WRED profile curve describes the probability of randomly dropping packets as the specific queue
uses more bandwidth.
You can configure a separate WRED profile curve for each priority queue. Additionally, you can configure
different weights for yellow (non‐compliant) and green (compliant) packets so that the system drops
yellow packets first.
To configure WRED traffic classification thresholds:
In the WRED thresholds section:
1. Expand the WRED queue.
 Click the + icon for a selected queue to view its details.
2. Define the queue level point that the mechanism should start checking if to drop the
frame.
 In the Green packets low threshold field, specify the minimum throughput of green
packets for this queue.
When this value is reached, the system begins dropping green packets in this
queue.
3. Define the queue level of occupancy point that the WRED must drop all arriving green
frames.
 In the Green packets high threshold field, specify the maximum throughput of green
After this value is reached, all green packets in this queue are dropped.
4. Define the maximum green drop probability (in percent based units).
 In the Green packets maximal drop percentage field, enter


5. Define the queue level point that the mechanism should start checking if to drop the
frame
 In the Yellow packets low threshold field, specify the minimum throughput of yellow
When this value is reached, the system begins dropping yellow packets in this
queue.
6. Define the queue level of occupancy point that the WRED must drop all arriving yellow
frames.
 In the Yellow packets high threshold field, specify the maximum throughput of yellow
After this value is reached, all yellow packets in this queue are dropped.
7. Define the maximum yellow drop probability (in percent based units).
 In the Yellow packets maximal drop percentage, specify the maximum percentage of
dropped yellow packets for this queue.
8. Click Apply.
10.7.4 Egress shaper & scheduler

The Egress shaper feature is used to shape the traffic profile sent to the radio. The Enhanced Traffic
Manager enables you to configure an Egress shaper for each priority queue.
When using the Enhanced Traffic Manager feature, the egress scheduler uses the Weighted Fair Queue
(WFQ) algorithm instead of Weighted Round Robin (WRR).
Each priority queue is assigned a strict priority between 1 and 4 (4=High; 1=Low). WFQ weights are used
to partition bandwidth between the queues of the same priority.
To enable the enhanced egress shaping and scheduling:
& scheduler.
In the Global Shaper admin section:
Click Enable.

To configure Egress shaper and scheduler for the priority queues:
& scheduler.
In the Queue configuration section:
1. Expand a priority queue.
 Select a queue and click the + icon to view its details.
2. Specify the Egress priority for this queue.
 In the Priority field, enter the a number between 1‐4 as the priority.
The queue with a higher priority egresses before a lower one regardless of WFQ
weights.
3. Specify the ratio for allowed bandwidth to queues with the same priority.
 In the WFQ weight field, enter a number between 1 and 15 to set the WFQ weight.
For example: if queue 5 has a WFQ weight of 4, and queue 7 has a WFQ weight of
8. Under congestion conditions, queue 7 would be allowed to transmit twice as
much bandwidth as queue 5.
4. Enable or disable the Egress shaper and scheduler for this priority queue.
 In the Shaper admin field, select Enable or Disable.
5. Specify the Committed Information Rate for this queue.
 In the CIR field, enter the number of Kbps to be allocated for CIR.
6. Specify the Committed Burst Size for this queue.
 In the CBS field, enter the number of bytes to be allocated for CBS.


7. Specify the queue line compensation.
 In the Line compensation field, enter the number of bytes that is compensated in the
shaper credits counting for the Inter‐Frame Gap (IFG) and the preamble + SFD fields
between the two consecutive Ethernet frames.
The default value is 20 bytes which is the number of bytes used for IFG + preamble
+ SFD according to the Ethernet standard.
You may want the Egress shaper to count in L2 by setting line compensation to 0. You can also “punish”
short frame senders for the overhead they cause in the network by increasing the line compensation
above 20 bytes.
10.8 CFM (Service OAM)

10.8.1 MAID list
10.8.1.1 Viewing MAID list status and details
The MAID list table section displays details about each MAID.
To view a MAID’s details:


In the MAID list section:
 # ‐ Indicates the domain number (internal number of the displayed function).
 Status ‐ Indicates the status of the current domain:
No MEPs – Indicates that no MEPs are configured yet for the selected MAID. This state
is used for empty domains, before defining MEPs, or for a domain that contains only
MIPs.
Monitoring ‐ CFM (CCM) – Indicates that proactive monitoring is running, no error
found.
Failure – Indicates a connectivity error in at least one MEP.
 Domain name ‐ Displays the maintenance domain name.
 Level ‐ Indicates the maintenance domain level.
 Association name ‐ Displays the maintenance domain association name.
 VLAN ID ‐ Displays the identification # of the VLAN
 Send CCM ‐ Displays the CCM status:
Disable ‐ no continuity (CCM) frames are sent from the local MEP to remote MEPs.
Enable ‐ continuity (CCM) frames are sent from the local MEP to remote MEPs.
 CCM interval ‐ Indicates the (periodic) time interval during which CCM messages are sent.
Valid values include 1Sec, 10Sec, 1Min, and 10Min.
Click the + in each MAID entry for more options.
10.8.1.2 Adding MAIDs

To add a new MAID:
1. Select Service OAM > MAID List.
2. Click Add to open the Add MAID configuration window.


In the Add Maid window:
1. Specify the maintenance domain name.
 In the Domain name field, enter the name of the maintenance domain.
2. Specify the maintenance domain level.
 In the Level field, select the maintenance domain level.
3. Specify the maintenance domain association name.
 In the Association name field, enter the maintenance domain association name.
4. Specify the MAID VLAN ID.
 In the VLAN ID field, enter a number between 1‐4090 as the MAID VLAN ID.
5. Click Apply to add the MAID.
10.8.1.3 Deleting MAIDs

To delete MAIDs:
In the MAID list table section:
1 Mark the checkbox of each MAID you wish to remove.
2 Click the Delete selected button at the bottom of the page.
3 Click OK to confirm the deletion.
10.8.1.4 Managing local MEPs
Viewing local MEPs

The Local MEP section displays details for all the local MEPs that are configured for the selected MAID.
To view local MEPs:
Select Service OAM > MAID list, and select a MAID from the list.
In the Local MEP section:
 Local MEP ID – Indicates the ID of the MAID local MEP.
 Ethernet port – Displays the selected port number on which the local MEP is located.
 MAC address – Displays Ethernet protection MAC address.
 Priority – Indicates the P‐bit priority that the CCM message carries.
 LDI ‐ Local Defect Indication.
If the value is Yes, click the + in the right corner of the table to view the reasons for
this bug.
 Connected – Indicates the connection status of the local MEP.
 Priority ‐ The P‐bit priority that the CCM message carries.

Adding local MEPs
You can define additional local MEPs for the selected MAID.
To add a local MEP:
Click the Add button underneath the list of local MEPs to open the Add MEP window.
In the Add MEP to port window:
1. Specify the port number where the local MEP is located.
 In the Ethernet port field, enter the port number of the local MEP.
2. Specify the MEP ID.
 In the Local MEP ID field, enter a number between 1‐8191 for the MEP ID.
3. Specify the MAID domain level.
 In the Level field, select the MAID domain level.
 In the VLAN ID field, enter a number between 1‐4090 for the VLAN ID.
5. Specify the MEP direction.
 In the Direction field, select either Up or Down.
6. Specify the P‐bit priority for the CCM message.
 In the Priority field, select the P‐bit priority.
7. Click Apply to add the MEP.


Deleting local MEPs
To delete a MEP from a port:
1 Mark the checkbox of each MEP you wish to remove.
2 Click the Delete selected button underneath the list of local MEPs.
10.8.1.5 Managing remote MEPs
Viewing remote MEPs

The Remote MEP section displays details for all the remote MEPs that are configured for the selected
MAID.
To view remote MEPs:
Select Service OAM > MAID List and select a MAID from the list.
In the Remote MEP section:
 MEP ID – Displays the remote MEP ID.
 Actual MAC address – Indicates the MAC address of the remote MEP, which the local MEP
recognizes.
 Configured MAC address – Indicates the configured MAC address
Used when you decide to specify a selected MAC address for the remote MEP.
 Status – Indicates the remote MEP connection status.
 Cross Check – Indicates whether current remote MEP was cross checked (pre‐configured)
or learned from incoming CCMs.
 RDI – Indicates the Remote Defect Indication status.
 Ping – Allows you to ping (run a loopback) from the local MEP to a specific remote MEP ID.
 Automatic Linktrace – Indicates whether Automatic Linktrace is enabled for this MEP.
 The checkbox column is used to delete the selection or issue a linktrace (ETH‐LT)
command from the local MEP to the current remote MEP.


Adding remote MEPs
To add a remote MEP:
Click the Add button underneath the Remote MEP list to open the Add Remote MEP
configuration window.
The upper part of the window displays a short summary of the MAID where the remote
MEP is being added.
 MAID <ID #> ‐ Indicates the ID of the selected MAID.
In the bottom part of the Add Remote MEP window, define the new MEP.
 In the Remote MEP ID field, enter a number between 1‐8191 as the remote MEP ID.
2. Specify the MEP’s MAC address.
 In the Configured MAC address field, specify a selected MAC address for the remote
MEP. (Optional)


Deleting remote MEPs
To delete a remote MEP:
2 Click the Delete selected button underneath the list of port MEPs.
3 Click OK to confirm the deletion.
Remote ping
You can ping remote MEPs.
To perform a remote ping:
Click the Ping icon for any MEP in the list to open the Remote ping window.
The upper part of the window provides a short summary of the MAID.
The Ping to section provides a short summary of the remote MEP being pinged.
 Remote MEP ID – Displays the remote MEP ID.
 Remote MAC address – Indicates the MAC address of the remote MEP, which the local
MEP recognizes.
The ping success rate percentage is displayed at the bottom of the window.
 The success rate is the percentage of LBM packet transmission over the received LBR
packets.

Remote linktrace
You can perform a linktrace for any of the MAID’s remote MEPs.
To perform a remote linktrace:
1. Check the checkbox of the MEP that you wish to trace.
 Note that you can only trace one MEP at a time.
2. Click the Linktrace selected button underneath the Remote MEP list.
The Linktrace result section provides a short summary of the MAID and the Remote MEP
being traced.
 From ‐ Indicates the ID and MAC address of the source of the trace.
 To ‐ Indicates the ID and MAC address of the destination of the trace.
 Priority – Indicates the P‐bit priority that the CCM message carries.


Linktrace results are displayed at the bottom of the page.
The table is refreshed automatically every fixed period of time (configurable, set to 15 min by default),
displaying the last updated date and time.
 Reply TTL ‐ Displays the hop number.
 Mac address ‐ Displays the hop (MEP/MIP) MAC address.
 Relay action ‐ Displays the hop LTM relay action.
Click Ping to perform a ping on the returned linktrace hops or results.
10.8.1.6 Enabling automatic linktrace

To configure automatic linktrace for a MAID:
In the Automatic linktrace parameters section:
1. Specify the number of seconds for the linktrace interval.
 In the Automatic linktrace interval fields, enter a number between 60 and 3600 as the
interval.
2. Click Apply to enable the automatic linktrace.
10.8.1.7 Configuring CCM

Continuity check messages (CCM) are heartbeat messages sent by the MAID’s MEPs to confirm
connectivity with the other MAID entities. When enabled, the settings will be applied to all MEPs and
MIPs in the selected MAID.
To configure CCM:
In the CCM configuration section:
1. Enable or disable sending CCM messages.
 In the Send CCM field, select Enable to allow continuity messages to be sent over the
MAID.
 Select Disable if you don't want continuity messages (CCM) sent over the selected
MAID.
2. Configure the message interval.
 In the CCM Interval field, select the CCM interval.
 The interval can be 1 second, 10 seconds, 1 minute, or 10 minutes.
3. Click Apply to confirm the configuration settings.


10.8.2 MEP & MIP list
10.8.2.1 Viewing MAID Ethernet ports
The Ethernet ports section displays details for all the selected MAID Ethernet ports.
To view Ethernet port details:
1 Select Service OAM > MEP and MIP list.
In the Ethernet ports section:
 Ethernet port – Displays the Ethernet port number.
 MAC address – Displays the Ethernet port MAC address.
 Connector type – Displays the Ethernet port connector type.
 Function – Displays the Ethernet port function.
 MEP or MIP defined – Indicates with a check indicates that you defined an MEP or MIP on
this port.
10.8.2.2 Viewing port MEPs

The Port MEPs section of the MEP and MIP list displays details for all the selected MAID Ethernet port
MEPs.
To view port MEPs:
Select Service OAM > MEP & MIP list and select an Ethernet port.


In the Port MEPs section:
 Local MEP ID – Indicates the ID of the MAID local MEP.
 Direction‐ Indicates the MEP direction: Up or Down.
 Send CCM ‐ Displays the CCM status:
Disable ‐ no continuity (CCM) frames are sent from the local MEP to remote MEPs.
Enable ‐ continuity (CCM) frames are sent from the local MEP to remote MEPs.
 CCM interval ‐ Indicates the (periodic) time interval during which CCM messages are sent.
Valid values include 1Sec, 10Sec, 1Min, and 10Min.
 Priority ‐ The P‐bit priority that the CCM message carries.
 LDI ‐ Local Defect Indication.
If the value is Yes, click the + in the right corner of the table to view the reasons for
this bug.
10.8.2.3 Adding MEPs to a port

To add a MEP to a port:
Click the Add button underneath the list of port MEPs.


In the Add MEP to port window:
1. Specify the port number where the local MEP is located.
 In the Ethernet port field, enter the port number of the local MEP.
 In the Local MEP ID field, enter the ID of the MAID local MEP.
3. Specify the MAID domain level.
 In the Level field, select the MAID domain level.
5. Specify the MEP direction.
 In the Direction field, select Up or Down.
6. Specify the P‐bit priority for the CCM message.
 In the Priority field, select the P‐bit priority.
10.8.2.4 Deleting MEPs from a port

To delete a MEP from a port:
2 Click the Delete selected button underneath the list of port MEPs.
10.8.2.5 Viewing port MIPs
The Port MIPs section of the MEP and MIP list displays details for all the selected MAID
Ethernet port MIPs.
To view port MIPs:
In the Port MIPs section:


10.8.2.6 Adding MIPs to a port
To add a MIP to a port:
Click the Add button underneath the list of port MIPs to open the Add MIP to port
window.
In the Add MIP to port window:
1 Specify which Ethernet port where you’ll be adding a MIP.
 In the Ethernet port field, enter the [Name | Number] of the Ethernet port.
2 Specify the MIP level.
 In the Level field, select the MIP level.
3 Click Apply to add the MIP.
Deleting MIPs from a port

You can delete MIPs from a port.
To delete a MIP from a port:
1. Mark the checkbox of each MIP you wish to remove.
2. Click the Delete selected button underneath the list of port MIPs.


10.8.3 Performing manual ping and linktrace operations
10.8.3.1 Manual ping
You can also manually ping remote MEPs and MIPs.
To configure a manual ping:
Select Service OAM > Advanced > Manual ping.
In the Manual Ping Parameters section:
1. Specify the MAC address
 In the MAC address field, enter the target MEP/MIP MAC address.
2. Select the MAID level.
 In the Level field, select the MAID level.
3. Specify the VLAN ID
4. Specify the P‐bit priority.
 In the Priority field, select the P‐bit priority bit for the outgoing ETH‐LTM packets.
5. Click Apply.


10.8.3.2 Manual linktrace
To perform a manual linktrace:
Select Service OAM > Advanced > Manual linktrace.
In the Manual linktrace parameters section:
1. Specify the MAC address
 In the MAC address field, enter the target MEP/MIP MAC address.
2. Select the MAID level.
 In the Level field, select the MAID level.
3. Specify the VLAN ID
4. Specify the P‐bit priority.
 In the Priority field, select the P‐bit priority bit for the outgoing ETH‐LTM packets.
5. Click Apply.

11. Frequency synchronization
Synchronization can be used to synchronize network elements.
Frequency signals can be taken from the specified synchronization sources. Network synchronization is
achieved by transporting the frequency timing references to related network interfaces.
11.1 Synchronization input and output interfaces

The input and output interfaces vary for different hardware releases.
Available synchronization input and output interfaces

Hardware Available interfaces as frequency Available interfaces as frequency
type input (reference sync source) output
XPAND IP+  TDM trails  E1/DS1 interfaces
R2  E1/DS1 interfaces  STM-1/OC-3 signal
 STM-1/OC-3 signal  STM-1/OC-3 VC-11/12s
 STM-1/OC-3 VC-11/12s  Radio channels
 Radio channels  Gigabit Ethernet interfaces
XPAND IP+  TDM trails  E1/DS1 interfaces
R3  E1/DS1 interfaces  STM-1/OC-3 signal
 STM-1/OC-3 signal  STM-1/OC-3 VC-11/12s
 STM-1/OC-3 VC-11/12s  Radio channels
 Radio channels  Gigabit Ethernet interfaces
 Gigabit Ethernet interfaces
XPAND IP+  Radio channels  Radio channels
Eth Only R3  Gigabit Ethernet interfaces  Gigabit Ethernet interfaces

11.2 Synchronization sources
11.2.1 Configuring system synchronization sources
To configure a synchronization source:
In the Sync Source Configuration section:
1. Specify the interface type.
 Select an interface from the displayed IFU.
2. Specify the priority for the selected synchronization source.
 Select a priority level from the Sync source priority field drop down list.
Note: No two interfaces may have the same priority.
3. Assign a quality level to a synchronization source.
 In the Quality field, apply a quality level to the selected source.
Quality options include Automatic, g811, ssu‐a, ssu‐b, g813‐8262, and Do not use.
 This option allows the system to select the source with the highest quality as the
current synchronization source.
4. Click Apply.


At any given moment, only one of these sources is active; the clock is taken from the active source onto
all other appropriately configured interfaces.
Restrictions for frequency distribution configuration:
 Synchronization source interfaces must not be assigned to a TDM trail, unless the “tdm
trail” interface is used. In this case, a pre‐existing trail must be configured.
 An interface can either be used as a synchronization source or can take its signal from the
system reference, but not both, except for SDH interfaces which allow local loop timing.
 If no interface is configured as a synchronization source, no interfaces may take its
outgoing clock from the reference.
 If at least one interface is currently taking its outgoing clock from the reference, the
synchronization source cannot be removed.
 The clock taken from a line interface (E1/DS1, SDH, VC‐11/12, Ethernet) cannot be
conveyed to another line interface in the same IFU.
 The clock taken from a radio channel cannot be conveyed to another radio channel in the
same radio.
 In each IFU, only one line interface at the main board and only one at the T‐card can take
its outgoing clock from the reference clock at any given time. All other interfaces in the
same board must make use of the local clock.
11.2.2Configuring a synchronization source revertive timer

To configure a synchronization source:
In the Sync Parameters section:
1. Specify the sync source timeout.
 In the Sync source revertive timer field, specify the number of seconds before timing
out a synchronization source.
2. Click Refresh to update configuration changes.

11.2.3 Configuring PRC regenerator mode and direction
Note: PRC regenerator mode is available only for R3 hardware releases, and can only be
enabled for Single Pipe applications.
To configure PRC regenerator mode:
1. Enable or disable PRC regenerator mode.
 In the Sync source regenerator admin field, select Enable or Disable.
2. Specify the PRC regenerator mode direction.
 In the Frequency transport direction for electrical GBE field, select Line to radio or
Radio to line.
3. Click Refresh to update configuration changes.
11.2.4 Viewing current synchronization sources

To view configured synchronization sources:
In the Current Sync Sources table:
 # ‐ Indicates the number of the synchronization sources. There can be up to eight
synchronization sources.
 Valid – Indicates whether the configuration is valid.
 Slot Number – Indicates the slot number of the synchronization source.
 Interface Type – Indicates the interface type.
 Interface Index – Indicates the priority of the synchronization source.

 Quality – Indicates the synchronization source quality.
 Status – Indicates the status of the synchronization source.
 Transmitted SSM value – Indicates the SSM value derived from the clock source.
11.3 Configuring the outgoing signal clock

The Clock Source window configures the ports that output the clock source.
For each type of interface, you can specify whether the clock source is based on a received sync source
or the local internal IFU source.
11.3.1 Configuring clock sources

To configure the clock source:


In the Clock source selection section:
1. Select an interface.
 Click an interface in the displayed IFU to configure its clock source.
For a radio interface, select an available channel.
For an STM‐1 interface, select the VC.
2 Specify how the clock source is calculated.
 Sync options in the Clock source sync field vary according to the selected interface.
For radio interfaces, select the radio channel.
For line interfaces, select the port number.
For Ethernet interfaces, select Local for internal, or Sync if the clock source is
received from the sync source.
For STM‐1 interfaces, select Internal to use the local clock source, Loop to sync
between the selected interface and the output destination, Sync to use the sync
source as the outgoing clock source value, and STM‐1/ OC/3 VC to use one of the
VC channels as the clock source value.
11.3.2 Viewing synchronization clock sources

To view configured clock sources:
In the Current configuration table:
 Interface – Indicates the type of interface.
 Configuration – Indicates whether the interface is configured for synchronization input or
output.
 Clock source – Indicates the source of its outgoing signal clock.
None – Indicates that a clock source has not been configured for this interface.
Local clock: Causes the interface to generate its signal from a local oscillator, unrelated
to the system reference frequency.
Synchronization reference: Causes the interface to generate its signal from the system
reference clock, which is taken from the synchronization source.

12. TDM trails
The Trails page is used to configure the Nera XPAND IP+ Cross Connect (XC) system for operation.
Nera XPAND IP+ Cross Connect system serves as a node in a microwave radio network. The system is
designed to comply with requirements of a node in a network that aggregates several sites (downlinks)
into a radio pipe (uplink). It can also be deployed in a mesh network configuration.
The system consists of up to six IFUs placed together in a single chassis, for TDM traffic cross connect. A
nodal enclosure can contain up to six XPAND IP+ IFUs.
Once the IFUs are linked through the common backplane, the XC system is constructed by building trails.
Trail building is only done via the main IFU (Slot 1 at the bottom). However, you can select any other IFU
to set other configuration parameters for all the other IFUs in the shelf.
12.1 Viewing the trails list

To view the trails list:
In the TDM Trails List table:
 ID – Indicates the trail ID.
 Description – Indicates the trail description.
 Interface #1 and Interface #2 – Indicate the trail end points.
 Alarms status – Indicates the severity of the trail’s most severe alarm.
 ACM priority ‐ Indicates the priority for which trails will be dropped first from radio links
when bandwidth is reduced.
 Operational status ‐ Indicates whether the selected trail is Operational or Reserved.
 Protected – Indicates if the trail is protected.


12.2 Adding new trails
To add a new trail:
1. Select Configuration > Trails > TDM Trails.
2. Click the Add button underneath the trails list to open the Add new trail window.


In the Add new trail window:
1. Select the first interface for the trail.
 The interface can be a line (E1/DS1 or STM‐1/OC‐3 VC‐11/12) interface or radio
interface in the system that isn’t used by any other TDM trails.
 For IFUs in a 1+1 configuration, TDM trails can contain interfaces in only one of the
IFUs.
2. Select the second interface.
 Interfaces 1 and 2 cannot be in the same radio or IFU.
3. Specify the trail ID.
 In the Trail ID field, enter a 15‐character string which identifies the trail.
This string cannot include spaces.
4. Specify the trail description.
 In the Trail description field, enter a 30‐character string to describe the trail.
The trail description is provided to help users identify the trail. It is not used by the
system.
5. Specify the ACM priority.
 Select High or Low from the ACM priority field drop down list.
ACM priority determines which trails will be dropped first from radio links when
bandwidth is reduced (in ACM).
6. Specify the trail operational state.
 Select Operational or Reserved from the Reserved/Operational field drop down list.
Operational trails occupy bandwidth and pass traffic. Reserved trails do not, but
they are saved in the database, and new trails cannot be configured to these
interfaces.
7. If you want a secondary trail to cover the main trail if it fails, configure the trail protection
options.
 Unprotected trails are point‐to‐point. Protected trails allow traffic from two different
paths to be chosen.
 Select Protected 1+1 for an SNCP protected trail, with permanent use of bandwidth in
both paths.
 Select Protected ABR for an SNCP protected trail with better use of the radio capacity
in the unused path.
If you chose Protected 1+1 or Protected ABR, you’ll be asked to select a third
interface that will function as the end point for the secondary path.

TDM trails configuration notes
 Up to 180 TDM trails can be configured. Note that a path‐protected trail counts as two
trails.
 Trails must be configured accordingly on both sides of the link.
 If an IFU is disconnected from the nodal enclosure and ceases to function as part of the
shelf configuration, the removal will be acknowledged as an alarm.
 The IFU can then function as a stand‐alone unit, using a "default" E1/T1 configuration.
12.3 Activating and reserving trails

To set the operational status of selected trails:

In the Activate and Reserve Trails section:
1 Specify the trail status.
 Select Operational or Reserved from the Status field drop down list.
2 Click Set Selected.
12.4 Configuring trail operational status

To set the operational status of all trails:
In the Activate and Reserve Trails section:
1 Specify the trail status.
 Select Operational or Reserved from the Status field drop down list.
2 Click Set All.
12.5 Deleting trails

To delete selected trails:
In the TDM Trails List table:
1. Select the trails that you wish to delete.
2. Mark the checkbox of each trail that you wish to include in the delete operation.
3. Click the Delete Selected button below the trail list.
To delete all trails:
1. Select Configuration > Trails > TDM Trails.
2. Click the Delete All button below the trail list.


12.6 TDM trail path protection (SNCP)
Path‐protected trails are a special case of TDM trails, in which not two but three interfaces are
configured. It is used in order to protect traffic from any failure along its end‐to‐end path.
12.6.1 SNCP trail configuration

SNCP trails differ from unprotected trails in the roles of their interfaces:
 Interface 1: The end‐point interface. Outgoing traffic is split between interfaces 2 and 3.
 Interface 2: The primary interface; it will be initially active.
 Interface 3: The secondary interface; it will be initially standby.
12.6.2 SNCP switching criteria

Traffic will switch from the currently active interface to the standby interface in the following cases:
 Signal failure
Note: When line interfaces (STM‐1) are used along a TDM trail path, AIS detection
must be enabled for SNCP to work properly.
 User command to force traffic to the standby interface
Note: Forcing traffic will cause the selected interface to become active (even if its
signal fails) until the user cancels this setting (revertive mode is not supported at
this stage).
To configure switch timeout for revertive protected trails:
In the Switch timeout for revertive protected trails section:
Configure the revertive switch timeout.
 In the Trails revertive switch timeout field, specify the number of seconds.


12.7 TDM trails and cross-connect
XPAND IP+ provides the capability for the user to map any pair of interfaces in order to created TDM
trails. Interfaces may be the following:
 E1/DS1 line ports: Ports 1‐16 are available in the lower SCSI connector; ports 17‐32 are
available in the upper one (if a T‐card is installed in the XPAND IP+).
 VC‐11/12 in STM‐1 line port: Available as a T‐card.
 Radio VCs: Each radio in the system has designated “channels”, each of which can carry a
duplex TDM signal. These channels are called “VCs” and in addition to the TDM signal they
carry extra data used for monitoring.
Note: Radio VCs are proprietary and do not conform to SDH VCs. They are terminated at line
interfaces.
After a trail is created the following takes place:
 TDM traffic (E1/DS1) is exchanged between the two interfaces.
 Line interfaces are enabled (if no trails are assigned to them, they are disabled).
 The trail is monitored in order to raise indications and measure PMs.
The switching fabric is located in the main unit. Therefore, a failure in this unit will cause all TDM traffic
to fail unless the main unit is protected.
12.7.1 XC trails overview

 XC Trails can be configured only via Main unit
 All Trails are transported through main unit(s)
 When Protection is enabled, configure trails to go via the Active unit
 (XC Trails are automatically created on the STBY unit)
 T‐Cards (TDM / SDH) are not hot‐swappable, do not extract / insert card when IFU is
powered up
 Radio VCs must be identical on both sides of the radio link
 Creating a TDM trail automatically activates the corresponding TDM port, therefore an
alarm will display next to the relevant T‐Card accommodating the activated port(s)
 XC trails can be configured between:
Radio to Line
Line to Radio
Radio to Radio
 Maximum number of trails (SNCP – Protected Ring) = 180
 Maximum number of trails per Radio = 84


12.7.2 Cross connection at the KLM level
Cross connection at the KLM level operates the same way as that for E1s.
When a trail is defined, you can choose one of the interfaces to be an STM‐1 VC‐12. Note that in the CLI,
this is done by setting the interface type to STM1 instead of Line.
 For example, this command adds a trail between VC#1 in the radio and VC‐12 #1 in the
STM‐1 interface of slot number one:
add-trail id1 desc1 high operational unprotected 1 stm1 1 1 radio 1
KLM table


12.8 Alarm Indication Signal (AIS) detection and signaling
If enabled, a signal failure is generated at the corresponding trail, which will cause the far end not to
receive a signal (including trail ID indications). The trail status will show “signal failure”. In addition, an
indication is sent to the relevant interface.
This is not a system alarm, since the problem originates elsewhere in the network.
To enable /disable AIS:
Select Configuration > Interfaces > AIS.
In the AIS line detection admin section:
1. Enable or disable AIS line detection.
 Select Enable or Disable.
2. Click Apply.

13. Security
13.1 Security configuration
To configure system security:
13.1.1 Securing web access

To configure HTTPS web protocol:
1 Create a CSR file, upload it and provide it to the Certificate Authority or certificate
generator.
2 Configure the certificate file name, type, and format for each certificate that you wish to
download.
3 Download the certificate to the NE.
4 Download the CA certificate to the NE (optional).
5 Enable the CA certificate (optional).
6 Set the web‐protocol parameter to HTTPS.

To configure HTTPS without certificates:
1 Upload the unit’s public key.
2 Set the web‐protocol parameter to HTTPS.
13.1.2 Generating CSR files

To generate a CSR file:
In the CSR File Creation section:
1. Specify the CSR file parameters.
Enter a “.” for any parameters that you wish to leave blank.
 In the Country name field, enter the two‐letter ISO code for the country where the
organization is location.
 In the State or Province name field, enter the state/region where the organization is
located.
 In the Locality Name field, enter the city where the organization is located.
 In the Organization name field, enter the legal name of the organization.
 In the Organizational unit name field, enter the division of the organization handling
the certificate.
 In the State or Province name field, enter the state or region where the organization is
located.
 In the Common name field, enter the identify name of the element in the network
(e.g. IP address).


 In the Email address field, enter an email address used to contact your organization.
The common name could be network IP or the FQDN of the element.
2. Click Create CSR file.
13.1.3 Generating a security certificate from a CSR file

To generate a certificate from a CSR file from the CSR text only:
1. Select Security>CSR file.
2. Click the View CSR file link at the bottom of the page.
3. Copy it to paste into a CSR generator and give it to a certificate generator or the Certificate
Authority.
To generate a certificate from a CSR file via upload:


In the CSR Upload section:
1. Specify the CSR file to upload and click Apply.
 In the Security file name field, specify the name of the CSR file.
2. When the Upload CSR file status field indicates “Ready”, click Upload File.
3. Give the CSR file to a certificate generator or the Certificate Authority.
13.1.4Uploading a public key

Server authentication is based on the unit’s public key. Uploading the public generates the IFU’s digital
certificate.
 Uploads are performed using FTP/SFTP.
 The public key file will be in PEM format.
To upload a public key:
In the Upload Public Key Status & Command section:
Click Upload Public Key.
The Upload public key status field indicates the upload status.
 The upload status values are: Ready, In‐progress, Success, and Failed.
 The default status is Ready.
13.1.5 Configuring the security file name, type and format

To configure the security certificate file name, type, and format:


In the Download Certificate Parameters section:
1. Define the security certificate.
 In the Security file name field, enter a name for the certificate.
 In the Security type field, select the file type.
Valid file type values are either: Target Certificate for WEB server digital
certificate, or Target CA certificate for WEB CA digital certificate.
 In the Security type format field, select the file format.
Valid file formats are PEM and DER.
13.1.6Downloading the web server and CA certificates

A certificate should be renewed whenever the old one expires.
The expiration date is customer driven. It’s usually a compromise between how often you want to
repeat this process and how long a customer feels comfortable in leaving it unchanged.
Some customers configure certificates to expire after several months, while others renew certificates
every 1‐2 years.
To download the web and/or CA certificate:
In the Download Certificate Status & Command section:
Click Download Certificate.
The Download security status field indicates the upload status.
 The download status values are: Ready, In‐progress, Success, and Failed.
 The default status is Ready.


13.1.7 Enabling the CA certificate
Determine whether to include the CA certificate into the web configuration definitions. This is an
optional configuration and is recommended for adapting the web interface to all the web browsers
applications.
To enable the CA certificate:
In the Download Certificate Parameters section:
1. Enable or disable the CA certificate.
 Select Enable if the downloaded file is a WEB CA digital certificate.
 Select Disable if the file is "WEB server digital certificate".
2. Restart the web server to apply the new certificate.
13.1.8 Configuring the web protocol

Prerequisites for HTTPS access:
 The security certificate must be downloaded to the IFU.
 The certificate’s public key must be compatible with the IFU’s private key.
To configure the web protocol:
In the Security Parameters section:
1. Specify the web protocol.
 Select HTTPS for secure web access.
Note: This parameter is NOT copied when a copy to mate operation is initiated. This is
for security reasons: an unsecured unit should not be able to override security
parameters of secured unit.

To enable or disable Telnet:
1. Enable or disable the Telnet protocol.
 Select Enable or Disable from the Telnet protocol field drop down list.
2. Click Apply.
13.2 SNMP
The SNMP page allows you to configure SNMP settings.
13.2.1 Setting the SNMP version

To configure the SNMP version:
Select Configuration>General>SNMP.
In the SNMP Parameters section:
Specify the SNMP version.
 In the SNMP version field, select V1, V2c, or V3.
13.2.2 Configuring SNMP read/write communities

To configure SNMP read/write communities:

In the SNMP Parameters section:
1. Specify the SNMP read and write communities.
 In the SNMP read community field, enter the password for the SNMP read
community.
 In the SNMP write community field, enter the password for the SNMP write
community.
2. Click Apply.
13.2.3 Configuring SNMPv3 security mode

In the SNMP V3 user settings section, specify V3 security mode and authentication.
To configure SNMPv3 security mode:
In the SNMP V3 User Settings section:
1. Specify the security mode.
 In the Security mode field, select the SNMPv3security mode:
No security
Authentication (default)
Authentication privacy
2. Click Change User Settings to apply the SNMP V3 changes.
13.2.4 Configuring SNMPv3 authentication

To configure SNMPv3 authentication:

1. Specify the authentication algorithm.
 In the Authentication algorithm field, select either MDS or SHA.
This field is only configurable if security mode is not set to No security.
13.2.5 Configuring SNMPv3 user name and password

To configure SNMPv3 user names and passwords:
1. Specify the V3 user name and password.
 In the User name field, enter the SNMPv3 user name.
 In the Password field, enter the SNMPv3 password.
This field is only configurable if security mode is not set to No security.
SNMPv3 passwords must be at least eight characters.
13.3 User access control

13.3.1 Assigning privileges to users
User permissions are determined by group: you grant permissions to a user by assigning the user to one
of the pre‐defined groups.
To assign a user to a group:
1. Select Security>Users and groups.
2. Click the Add User button underneath the Users list to define a new user.
To modify privileges for an existing user, select the user from the list.

e
In the Add a user window:
Specify the user group.
 Select a group from the User privilege drop down list:
Viewer ‐This user cannot configure parameters, but only view them.
Operator‐This user can configure all parameters in the system, except for security‐
related parameters (such as adding privilege groups).
Admin‐This user has all Operator privileges, as well as the ability to add new users.
Tech (technician) ‐ Has all Admin privileges, as well as access to the Linux OS shell.
13.3.2 Configuring password security

 Password strength is enforced; passwords must comply with the following rules:
Be at least 8 characters long
Include both numbers and letters (or spaces, symbols, etc.)
Include both uppercase and lowercase letters
When calculating the number of character classes, upper‐case letters used as the first
character and digits used as the last character of a password are not counted
A password cannot be repeated within the past 5 password changes
 Password aging: users will be prompted do change passwords after a configurable amount
of time
 When new users log in for the first time, the system shall force them to change their
password
 Mandatory change of password at first time login can be enabled and disabled upon user
configuration. It is enabled by default.
To configure user password settings:
1. Select Security>Users and groups.

1. Specify the user password settings.
 In the Expiration date field, click the calendar icon and select the expiration date for
the user’s password.
 In the Password aging field, select the number of days for which a password is valid for
this user.
2. Click Apply.
13.3.3 Suspending inactive users

To suspend inactive users:
1. Configure the auto logout timeout.
 In the Communication inactivity timeout field, specify the number of minutes before
automatically suspending an inactive user.
2. Click Apply.


13.4 User management
13.4.1Adding users
In the Users and Groups page, you can add users to the system.
To add a new user:
1. Select Security > Users and groups.
1. Specify the user group.
 In the User privilege field, select which group:
Viewer ‐ This user cannot configure parameters, but only view them.
Operator ‐ This user can configure all parameters in the system, except for
security‐related parameters (such as adding privilege groups).
Admin ‐ This user has all Operator privileges, as well as the ability to add new
users.
Tech (technician) ‐ Has all Admin privileges, as well as access to the Linux OS shell.
2. Define the user login parameters.
 In the User name field, enter a user name for the user.
 In the Password field, enter a password that will authenticate the user.
3. Specify the user password settings.
 In the Expiration date field, click the calendar icon and select the expiration date for
the user’s password.
 In the Password aging field, select the number of days for which a password is valid for
this user.
4. Click Apply to add the new user.


13.4.2 Deleting users
In the Users and Groups page, you can delete users from the system.
To delete a new user:
1. Select Security > Users and groups.
In the Users table:
1. Mark the checkbox next to each user that you wish to delete.
2. Click the Delete selected button underneath the Users list.
13.4.3 Changing user passwords

To change a user password:
Select Security>Change password.
In the Change your password section:
1 Enter your old password in the Old password field.
2 Enter your new password in the New password field.
3 Re‐enter your new password in the New password field.
3. Click Change password.

14. Diagnostics & maintenance
14.1 Loopback
14.1.1 Radio loopback
In the Radio loopback page, you can set the parameters for a radio loopback test.
To configure radio loopback:
Select Diagnostics and maintenance > Loopback > Radio.
In the Radio Loopback section:
1. Configure the loopback timeout.
 In the Timeout field, specify the number of minutes before timing out a loopback
operation.
2. Active or deactivate IF loopback.
 Select On or Off from the IF loopback drop down list.
3. Active or deactivate ODU RF loopback.
 Select On or Off from the ODU RF loopback drop down list.
4. Click Apply.


14.1.2 PDH line loopback
In the PDH line loopback page, you can set the parameters for a PDH loopback test.
To configure line loopback:
Select Diagnostics and maintenance > Loopback > PDH line.
In the Line Loopback section:
1. Configure the loopback timeout.
 In the Timeout field, specify the number of minutes before timing out a loopback
operation.
2. Specify which ports to include in the loopback operation.
 For each interface, select Loopback towards radio or Off from the State field drop
down list.
3. Click Apply.


14.1.3SDH loopback
In the SDH line loopback page, you can set the parameters for an SDH loopback test.
To configure loopback for an STM‐1 line:
Select Diagnostics > Loopback > SDH line.
In the STM‐1 loopback window:
1. Specify the loopback timeout.
 In the Loopback timeout field, enter a number between 0‐1440 to specify the number
of minutes you want the test to run.
2. Enable or disable line loopback.
 In the Line loopback field, select Enabled if you want to perform a loopback test, or
Disabled if you don't want to perform a test for that line.
3. Click Apply to save your settings.


14.2 IFU-ODU interface monitoring
In the IFU‐ODU interface monitoring page, you can monitor the IFU‐ODU traffic.
To view communication errors:
Select Diagnostics > IFU‐ODU interface monitoring.
In the IFU‐ODU Communication errors section:
 ODU receiver errors – Indicates the number of ODU interface errors.
 IFU receiver errors – Indicates the number of IFU interface errors.
To clear IFU error counters:
1. Select Diagnostics > IFU‐ODU interface monitoring.
2. Click Clear IFU errors.


15. Appendix
15.1 Feature compatibility chart
Applications matrix
Protection ACM ring XPIC Multi Space Frequency 2+2
Chann diversity diversity
el
ABC
1+1 HSB - yes Ring no No Yes Yes Yes
convergence
> 50ms
2+2 HSB yes Yes Ring Yes Yes (no no no -
convergence (no LCAS)
> 50ms XRSM)
ACM yes - Yes yes yes No No Yes
Frequency yes No Ring no no no - No
diversity convergence
> 50ms
Space yes no Ring no no - no No
diversity convergence
> 50ms
Multi No yes yes yes - no No Yes (no
Channel LCAS)
ABC
Ring Ring yes - yes yes Ring Ring Ring
convergence convergence convergence convergence
> 50ms > 50ms > 50ms > 50ms
XPIC No Yes yes - yes No No Yes
(no XRSM)


WebEMS UserGuide RevB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WebEMS UserGuide RevB

Uploaded by

Copyright:

Available Formats

Web Element Management

The information or statements given in this documentation concerning the suitability,

EvoTM is a registered trademark of Nera Networks Singapore. Other product names

Copyright © Nera Networks Singapore 2011. All rights reserved.

2 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 3 of 264

4 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 5 of 264

6 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 7 of 264

8 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 9 of 264

10 of 264 Web Element Management System (EMS) User Guide

1.2 Selecting a slot

Web Element Management System (EMS) User Guide 11 of 264

Single unit configuration

12 of 264 Web Element Management System (EMS) User Guide

1.2.2.2 Evo XPAND IP+ Eth Only

Web Element Management System (EMS) User Guide 13 of 264

14 of 264 Web Element Management System (EMS) User Guide

2.1.2 Event log

Web Element Management System (EMS) User Guide 15 of 264

2.2.2 RMON counters

16 of 264 Web Element Management System (EMS) User Guide

2.2.4 Enhanced Traffic Manager

Web Element Management System (EMS) User Guide 17 of 264

18 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 19 of 264

20 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 21 of 264

2.2.8.6 TDM channels

22 of 264 Web Element Management System (EMS) User Guide

Frame error rate

Web Element Management System (EMS) User Guide 23 of 264

24 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 25 of 264

26 of 264 Web Element Management System (EMS) User Guide

2.3.1.3 Traps configuration

Web Element Management System (EMS) User Guide 27 of 264

28 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 29 of 264

30 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 31 of 264

32 of 264 Web Element Management System (EMS) User Guide

2.3.2.2 STP protocol

Web Element Management System (EMS) User Guide 33 of 264

34 of 264 Web Element Management System (EMS) User Guide

Configuration and parameters

Web Element Management System (EMS) User Guide 35 of 264

36 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 37 of 264

38 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 39 of 264

2.3.3.3 Radio thresholds

40 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 41 of 264

42 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 43 of 264

44 of 264 Web Element Management System (EMS) User Guide

Web Element Management System (EMS) User Guide 45 of 264

46 of 264 Web Element Management System (EMS) User Guide

2.3.4.6 User channel

Web Element Management System (EMS) User Guide 47 of 264