IP10G CeraWeb User Guide Version 6 7 March2011

Copyright © 2011 by Ceragon Networks Ltd. All rights reserved.

CeraWeb User Guide Version 6.7

March 2011


Ceragon Proprietary and Confidential Page 2 of 167

Notice

This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.

Registered TradeMarks

Ceragon Networks® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

TradeMarks

CeraMap™, PolyView™, EncryptAir™, ConfigAir™, CeraMon™, EtherAir™, and MicroWave Fiber™, are trademarks of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

Statement of Conditions

The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

Open Source Statement

The Product may use open source software, among them O/S software released under the GPL or GPL alike license ("GPL License"). Inasmuch that such software is being used, it is released under the GPL License, accordingly. Some software might have changed. The complete list of the software being used in this product including their respective license and the aforementioned public available changes is accessible on http://ne-open-source.licensesystem.com/.

Information to User

Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment.

http://ne-open-source.licensesystem.com/



Table of Contents

1. General ................................................................................................................... 7

1.1 Getting Started ........................................................................................................... 7

1.2 Resetting after configuration changes ......................................................................... 7

2. Main View ............................................................................................................... 9

3. Faults .................................................................................................................... 10

3.1 Current Alarms ......................................................................................................... 10

3.2 Event Log ................................................................................................................. 11

4. PM & Counters .................................................................................................... 12

4.1 PM graphs ............................................................................................................... 12

4.2 PM Commands ........................................................................................................ 13

4.3 RMON (Remote Monitoring) ..................................................................................... 13

4.4 TDM Trails ............................................................................................................... 14

4.5 Enhanced Traffic Manager ....................................................................................... 15

4.6 E1 ............................................................................................................................ 16

4.7 DS1 ......................................................................................................................... 17

4.8 STM-1/OC-3............................................................................................................. 18

4.9 Radio ....................................................................................................................... 19 4.9.1 Signal Level (RSL) ................................................................................................... 19 4.9.2 Aggregate ................................................................................................................ 20 4.9.3 MRMC ..................................................................................................................... 21 4.9.4 MSE ......................................................................................................................... 22 4.9.5 XPI Performance ...................................................................................................... 23 4.9.6 TDM Channels ......................................................................................................... 24 4.9.7 Ethernet ................................................................................................................... 25

4.9.7.1 Frame Error Rate ..................................................................................... 25 4.9.7.2 Throughput ............................................................................................... 26 4.9.7.3 Capacity ................................................................................................... 27 4.9.7.4 Utilization ................................................................................................. 29

5. Configuration ....................................................................................................... 31

5.1 General .................................................................................................................... 31 5.1.1 Unit Parameters ....................................................................................................... 31 5.1.2 External Alarms ........................................................................................................ 33

5.1.2.1 Alarm input configuration (up to five independent inputs) .......................... 33 5.1.2.2 Alarm output configuration (single output) ................................................. 33

5.1.3 Management ............................................................................................................ 34 5.1.3.1 IP Configuration........................................................................................ 34 5.1.3.2 Management Ports ................................................................................... 34

5.1.4 Traps Configuration .................................................................................................. 35 5.1.5 Licensing.................................................................................................................. 36

5.1.5.1 Current License ........................................................................................ 36 5.1.5.2 Demo License .......................................................................................... 37



5.1.5.3 License Features ...................................................................................... 37 5.1.6 NTP ......................................................................................................................... 38 5.1.7 IP Table ................................................................................................................... 39 5.1.8 SNMP ...................................................................................................................... 40

5.1.8.1 SNMP Parameters ................................................................................... 40 5.1.8.2 SNMP V3 User Settings ........................................................................... 40

5.1.9 All ODU .................................................................................................................... 41 5.1.10 Versions ................................................................................................................... 42

5.1.10.1 IDU Versions ............................................................................................ 42 5.1.10.2 RFU Versions ........................................................................................... 42

5.2 Ethernet Switch ........................................................................................................ 43 5.2.1 Switch Configuration ................................................................................................ 43 5.2.2 STP Protocol ............................................................................................................ 46 5.2.3 RSTP and Ring RSTP .............................................................................................. 47 5.2.4 QoS & Rate Limiting ................................................................................................. 48

5.2.4.1 Ingress Classifier ...................................................................................... 49 5.2.4.2 VLAN Pbits Priority Remap ....................................................................... 51 5.2.4.3 Egress Scheduler ..................................................................................... 51 5.2.4.4 Ingress Rate Limiting ................................................................................ 52 5.2.4.5 Advanced Classifier - VLAN-ID to Queue .................................................. 53 5.2.4.6 Advanced Classifier - IP-Pbits to Queue ................................................... 54 5.2.4.7 Advanced Classifier - VLAN-Pbits to Queue ............................................. 54 5.2.4.8 Advanced Classifier – Queue Weights ...................................................... 55 5.2.4.9 Advanced Classifier - Policer List .............................................................. 56 5.2.4.10 Advanced Classifier - Static MAC ............................................................. 56 5.2.4.11 Copy Ports Configuration .......................................................................... 57

5.2.5 Enhanced Traffic Manager ....................................................................................... 58 5.2.5.1 Preparing to use Enhanced Traffic Manager ............................................. 58 5.2.5.2 Configuration & Parameters ...................................................................... 60 5.2.5.3 Classification – Overview .......................................................................... 62 5.2.5.4 Classification – Default settings ................................................................ 63 5.2.5.5 Classification – First hierarchy .................................................................. 64 5.2.5.6 Classification - Second hierarchy .............................................................. 68 5.2.5.7 Classification - Third hierarchy .................................................................. 68 5.2.5.8 WRED ...................................................................................................... 72 5.2.5.9 Egress Shaper & Scheduler ...................................................................... 73

5.3 Radio ....................................................................................................................... 75 5.3.1 Radio Parameters .................................................................................................... 75

5.3.1.1 Status Parameters .................................................................................... 77 5.3.1.2 Frequency Control .................................................................................... 78 5.3.1.3 Configuration Parameters ......................................................................... 78 5.3.1.4 XPIC Parameters ..................................................................................... 79 5.3.1.5 Green Mode ............................................................................................. 79 5.3.1.6 Multi Radio ............................................................................................... 80

5.3.2 Remote Radio .......................................................................................................... 82 5.3.3 Radio Thresholds ..................................................................................................... 83 5.3.4 MRMC Configuration ................................................................................................ 84

5.3.4.1 MRMC Configuration ................................................................................ 84 5.3.4.2 Current TX ............................................................................................... 84 5.3.4.3 Current RX ............................................................................................... 85 5.3.4.4 MRMC Table ............................................................................................ 85 5.3.4.5 MRMC Table – ACM Scripts ..................................................................... 86

5.3.5 Traffic Priority ........................................................................................................... 88



5.3.6 ATPC ....................................................................................................................... 90

5.4 Interfaces ................................................................................................................. 91 5.4.1 Ethernet Ports .......................................................................................................... 91

5.4.1.1 Configuring a specific port ........................................................................ 92 5.4.1.2 Defining a LAG PORT .............................................................................. 94 5.4.1.3 Defining Fault Criteria ............................................................................... 96

5.4.2 E1 Ports ................................................................................................................... 97 5.4.2.1 Configuring the Line Coding ..................................................................... 97

5.4.3 Using an E1/T1 T-Card ............................................................................................ 98 5.4.4 DS1 Ports ................................................................................................................ 98 5.4.5 STM-1/OC-3 (T-Card) .............................................................................................. 98 5.4.6 Wayside Channel ................................................................................................... 101 5.4.7 User Channel ......................................................................................................... 102 5.4.8 EOW ...................................................................................................................... 103 5.4.9 AIS ......................................................................................................................... 103 5.4.10 Sync Source........................................................................................................... 104 5.4.11 Clock Source.......................................................................................................... 105

5.5 Protection ............................................................................................................... 106 5.5.1 Protection Parameters ............................................................................................ 106

5.5.1.1 Protection Configuration ......................................................................... 107 5.5.1.2 Mate Parameters .................................................................................... 107 5.5.1.3 Protection Switch Criteria ....................................................................... 107 5.5.1.4 Protection Commands ............................................................................ 107

5.5.2 Radio Diversity ....................................................................................................... 108 5.5.2.1 IF Combining Parameters ....................................................................... 108 5.5.2.2 Space Diversity 1+1 Baseband ............................................................... 109

5.6 Trails ...................................................................................................................... 111 5.6.1 Configuring TDM Trails .......................................................................................... 111

5.6.1.1 TDM Trails Configuration Notes .............................................................. 114 5.6.1.2 Connected Ports ..................................................................................... 115 5.6.1.3 Cross Connection at the KLM Level ........................................................ 116

6. Service OAM ...................................................................................................... 118

6.1 MAID List ............................................................................................................... 118 6.1.1 MAID List Columns ................................................................................................ 118 6.1.2 MAID List Operations ............................................................................................. 119 6.1.3 MAID List MEPs ..................................................................................................... 119 6.1.4 Local MEP ............................................................................................................. 120 6.1.5 CCM Configuration ................................................................................................. 121 6.1.6 Remote MEP.......................................................................................................... 121

6.1.6.1 Remote MEP Columns ........................................................................... 121 6.1.6.2 Remote MEP ping window ...................................................................... 122 6.1.6.3 Adding a new remote MEP ..................................................................... 122

6.1.7 Linktrace ................................................................................................................ 123

6.2 MEP & MIP List ...................................................................................................... 124 6.2.1.1 Ethernet Port columns ............................................................................ 124 6.2.1.2 Port MEPs columns ................................................................................ 124 6.2.1.3 Port MIPs columns ................................................................................. 124

6.2.2 Add MEP to Port .................................................................................................... 125 6.2.3 Add MIP to Port ...................................................................................................... 125

6.3 Advanced ............................................................................................................... 126



6.3.1 Manual Ping ........................................................................................................... 126 6.3.2 Manual Linktrace .................................................................................................... 127

7. Diagnostics & Maintenance ............................................................................. 128

7.1 Radio Loopback ..................................................................................................... 128

7.2 PDH Line Loopback ............................................................................................... 129

7.3 SDH Loopback ....................................................................................................... 129

7.4 Configuration Management .................................................................................... 130 7.4.1 Overview ................................................................................................................ 130 7.4.2 Uploading or downloading an archive ..................................................................... 131 7.4.3 Configuration Backup Management ........................................................................ 131 7.4.4 Archiving unit information ....................................................................................... 132 7.4.5 Configuring the FTP parameters ............................................................................. 132 7.4.6 Resetting the configuration ..................................................................................... 133 7.4.7 Viewing the archive status ...................................................................................... 133

7.5 Software Management ........................................................................................... 134

7.6 RFU Download ....................................................................................................... 135

7.7 IDU-RFU Interface Monitoring ................................................................................ 136

7.8 Resets ................................................................................................................... 136

7.9 File List .................................................................................................................. 137

8. Security .............................................................................................................. 138

8.1 Security Configuration ............................................................................................ 138

8.2 Users & Groups ..................................................................................................... 139

9. Appendix A – FibeAir IP-10 Alarms Table ...................................................... 141



1. General

This guide explains how to work with the FibeAir® IP-10 Web Based Management.

IP-10 management is used to perform configuration operations and obtain statistical and performance information related to the system.

For full functionality and feature availability, upgrade the IDU to the latest released software version. You can obtain the latest software version and release notes at Ceragon’s FTP site. For access to the site, contact [email protected].

1.1 Getting Started

To start the web based management application:

1 Start your web browser. 2 In the URL address field at the top, type http://yourIP, and press Enter,

whereby yourIP is the IP address of your FibeAir unit. The Login window is displayed.

3 Enter your user name and password, and click Apply. The Main View window appears:

Configuration and other operations are performed by clicking the menus on the left side of the page.

1.2 Resetting after configuration changes

Some changes that are made to the IP-10 configuration cannot be enabled until the IDUs are reset. The IDU reset process generally takes several minutes to complete. You can make all of the required changes to the IDU configuration

mailto:[email protected]



and then reset the IDU. This single reset executes all of the configurations that were changed. The following list contains some of the configuration changes that require resetting the IDU:

Updating or changing the license.

Configuring the MRMC table (modem script).

Changing the Ethernet application type. (From Single pipe to Managed or Metro switch.)

After performing one of these configuration changes, the warning icon is displayed next to the field to indicate that the IDU must be reset. The following figure shows the Switch Configuration window after the Single pipe Ethernet application type has been selected.

For more information about resetting the IDU, see Resets on page 136.



2. Main View

The Main view window displays the IDUs that are in the shelf.

You can click on one of the IDUs to make that slot active.

Click on a port. The configuration window for that port is displayed.

Click Refresh to update the window.



3. Faults

3.1 Current Alarms

Select the Current Alarms item to view a list of alarms that are active in the system.

For a full list of all of the IP-10 alarms, see Appendix A – FibeAir IP-10 Alarms Table on page 141.

Each line on the page displays a different alarm.

Click an alarm in the list to view Probable Cause and Corrective Action information for that alarm.

The following list is an explanation of the columns in the Current Alarms section.

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.

Probable Cause – The most likely cause of the alarm.

Corrective Actions – The recommended action(s) to take to resolve the cause of the alarm.



To send the alarm list to the printer, from the Internet Browser menu bar select File > Print.

To update the list, click Refresh.

3.2 Event Log

The event log is a list of historical events and alarm information.

The Event Log displays the last 200 events and alarms that occurred. If the number of events/alarms exceeds 200, the oldest events/alarms will be removed.

The following list is an explanation of the columns in the Event Log window.

# - Number of the event/alarm.

Date & Time - The date and time the event/alarm was triggered.

Severity - The color of the icon indicates the severity.

Module - The module that generated the event/alarm.

State - The event/alarm status (Raised, Cleared).

Description - A description of the event/alarm.

To clear the Event Log, click Clear.

To update the Event Log, click Refresh.

To print the Event Log, from the Internet Browser menu bar select File > Print.



4. PM & Counters

4.1 PM graphs

Many of the PM (Performance Monitoring) windows contain an option to display the PM data is a graph.

To display the PM graph:

From the top of the PM window, click . The PM graph is displayed.



4.2 PM Commands

The Performance Monitoring commands window enables you to clear all performance monitoring measurements in the unit, except for RMON.

4.3 RMON (Remote Monitoring)

The RMON counters display 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.

To reset a counter, click Clear at the top of the column.

To reset all counters, click Clear All.




To print the list, from the Internet Browser menu bar select File > Print.

4.4 TDM Trails

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 IDUs:

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 the TDM Trails PM:

From the Trails List section, select the TDM trail. The Performance Monitoring data is displayed in a new pane to the right of the Trails List section.

To update the TDM Trails PM, from the bottom of the TDM Trails PM data list click Refresh.

The following list explains the columns in the E1 PM Report.

ES is the number of seconds during which errors occurred.

SES is the number of severely errored seconds.

UAS is the Unavailable Seconds value of the current interval. The value can be between 0 and 900 seconds (15 minutes).

BBE is the number of background block errors.

The Integrity column indicates whether or not 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.



4.5 Enhanced Traffic Manager

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 CIR (Committed Information Rate). Yellow traffic refers to frames that exceed the configured CIR but are below the configured EIR (Excess Information Rate).

At the top of the page, select the Report Interval.

Avg. Green – Displays the average green traffic in bps (bytes per seconds) 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 (bytes per seconds) during the report interval.

Max Yellow - Displays the peak yellow traffic for one second during the report interval.

Integrity - indicates whether or not 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.



4.6 E1

The E1 page contains a separate PM window for each E1 link that is being used.

You can configure if the displayed PM data covers the last 24 hours, in 15 min intervals, or covers a month, with daily intervals.












4.7 DS1

The DS1 (T1) page contains a separate PM window for each DS1 link that is being used.

For Report Interval, you can select either every 15 minutes, or Daily for the list to include values for the entire day.

The following list explains the columns in the DS1 PM Report.










4.8 STM-1/OC-3

The STM-1 or OC-3 page contains a separate PM window for each STM-1/OC-3 link that is being used.

For Report Interval, you can select either every 15 minutes, or Daily for the list to include values for the entire day.











4.9 Radio

4.9.1 Signal Level (RSL)

The RSL Performance Report page displays received signal level values measured over the past 24 hours, in 15 min intervals, or the past month, daily intervals.


Min RSL values are the minimum received level measured during the interval.

Max RSL values are 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 values are the minimum transmitted level measured during the interval.

Max TSL values are 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.


To update the list, from the bottom of the Signal Level PM Report click Refresh.

In the Thresholds Configuration area at the bottom of the value table, specify the value you want for the thresholds. The range of values appears at the end of the threshold line.

To apply any change you made to the Thresholds Configuration, click Apply.

To update the configured thresholds, from the Thresholds Configuration section click Refresh.


4.9.2 Aggregate

The Aggregate Performance Report page displays tributary values measured over the last 24 hours, in 15 min intervals, or the past month, daily intervals.







To update the Aggregate PM Report, click Refresh.




4.9.3 MRMC

The MRMC Performance Report page displays 15-minute or daily values of Multi-Rate Multi-Constellation performance.


Min Profile is the minimum radio profile during the last interval.

Max Profile is the maximum radio profile during the last interval.

Min BitRate (Mbps) is the minimum total radio throughput (Mbps), delivered during the last interval.

Max BitRate (Mbps) is the maximum total radio throughput (Mbps), delivered during the last interval.

Min Number of Allocated TDM VCs is the minimum number of TDM voice channels (E1/T1) delivered over the radio during the last interval.

Max Number of Allocated TDM VCs is the maximum number of TDM channels (E1/T1) delivered over the radio during the last interval.


To update the MRMC PM Report, click Refresh.



4.9.4 MSE

The MSE Performance Report page displays the modem’s Minimum Square Error performance statistics. The values are for every 15 minutes or daily.


Min MSE is the minimum MSE in dB, measured during the last interval.

Max MSE is the maximum MSE in dB, measured during the last interval.

MSE Exceed is the number of seconds the MSE exceeded the threshold (configured in the field below the table) during the last interval.


To update the list, from the bottom of the MSE PM Report click Refresh.

From the Threshold Configuration section:



MSE Threshold (dB) is the value that will be compared with the current MSE value, to calculate if the limit was exceeded.

To apply any change you made, click Apply.

To update the MSE Threshold Configuration, click Refresh.

4.9.5 XPI Performance

The XPI Performance page displays the Cross Polarization Interference value over 15 minutes or per day.


Min XPI is the minimum XPI in dB, measured during the last interval.

Max XPI is the maximum XPI in dB, measured during the last interval.

XPI Exceed is the number of seconds the XPI exceeded the threshold (configured in the field below the table) during the last interval.




To update the list, from the bottom of the XPI PM Report click Refresh.


XPI Threshold (dB) is the value that will be compared with the current XPI value, to calculate if the limit was exceeded.


To update the XPI Threshold Configuration, click Refresh.

4.9.6 TDM Channels

The TDM Channels page displays the unavailable seconds (UAS) of the expected E1/T1 trails on the radio.

When ACM decreases, the capacity of the radio is reduced, and several E1/T1 trails with not enough bandwidth in the radio link capacity may be dropped.

When an E1/T1 trail is dropped, its Radio-TDM UAS counter PM will start counting the seconds for which the E1/T1 trail was not serviced.

To update the TDM Channel PM Report, click Refresh.



4.9.7 Ethernet

4.9.7.1 Frame Error Rate

The Frame Error Rate Performance Report page displays statistics of the Ethernet frame error rate (%) measured on the radio Ethernet port.


Frame Error Rate (%) is the number of received error frames measured by the radio Ethernet port, relative to all frames received by the radio Ethernet port.


To update the Ethernet Frame Error Rate PM Report, click Refresh.



4.9.7.2 Throughput

The Throughput Performance Report page displays radio Ethernet throughput statistics (excluding TDM traffic), measured on the radio port.


Peak Throughput (bps) is the maximum throughput measured during the last interval.

Average Throughput (bps) is the average throughput measured during the last interval.

Throughput Exceed (Seconds) is the number of seconds the throughput exceeded the threshold (configured in the field below the table) during the last interval.




To update the list, from the bottom of the Throughput PM Report, click Refresh.


Throughput Threshold (Mbps) is the throughput value that will be compared with the current value, to calculate if the limit was exceeded.


To update the Throughput Threshold Configuration, click Refresh.

4.9.7.3 Capacity

The Capacity Performance Report page displays statistics of the Ethernet capacity (including Ethernet data and overhead bytes) measured on the radio port.




Peak Capacity (bps) is the maximum capacity measured during the last interval.

Average Capacity (bps) is the average capacity measured during the last interval.

Capacity Exceed (Seconds) is the number of seconds the throughput exceeded the threshold (configured in the field below the table) during the last interval.


To update the list, from the bottom of the Capacity PM Report, click Refresh.


Capacity Threshold (bps) is the capacity value that will be compared with the current value, to calculate if the limit was exceeded.


To update the Capacity Threshold Configuration, click Refresh.



4.9.7.4 Utilization

The Utilization Performance Report page 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:

1 0-20% 2 20-40% 3 40-60% 4 60-80% 5 80-100%




Range of Peak Utilization (%) is the maximum utilization measured during the last interval.

Range of Average Utilization (%) is the average utilization measured during the last interval.

Utilization Exceed (Seconds) is the number of seconds the value exceeded the threshold (configured in the field below the table) during the last interval.


To update the list, from the bottom of the Utilization PM Report, click Refresh.


Utilization threshold (%) is utilization threshold value, which must be configured in the bin resolution listed above.


To update the Utilization Threshold Configuration, click Refresh.



5. Configuration

5.1 General

5.1.1 Unit Parameters

This page allows you to view and define information for the IP-10 system.



(Optional) In the System name field, enter a name for the node. By convention, this is the node’s fully qualified domain name.

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.

The read-only IP address field displays the IP address that is configured in the Management window.

The read-only System Description field provides information about the FibeAir system.

(Optional) In the Contact person field, enter the name of the person to be contacted when a problem with the system occurs.

(Optional) In the System location field, enter the actual physical location of the node or agent.

The System up time field is read-only and shows how long the system has been operating continuously.

The read-only Voltage input field displays the current input voltage.

In the Measurement system field, select the type of measurement you want the system to use: Metric or Imperial.

The read-only IDU/RFU temperature fields display the current temperatures of the IDU and RFU.

In the Date & Time Configuration section, click the calendar to set the date, and click the time area to set the time.

Offset from GMT is the Hours and Minutes offset of the time of day from GMT (Greenwich Mean Time).

In the Daylight Saving Time section, you can configure the following options:

Start Date - the date when daylight saving time will automatically be activated.

End Date - the date when daylight saving time will automatically be terminated.

Offset (in hours) - the required offset time, in hours, when daylight saving time is activated.

In the IDU Serial/Part Numbers section, the following read-only information is displayed:

IDU serial/part number fields display the serial and part numbers of the IDU.

RFU serial/part number fields display the serial and part numbers of the RFU.


To update the information, click Refresh.



5.1.2 External Alarms

The External Alarms page enables you to set up the external alarm system.



5.1.2.1 Alarm input configuration (up to five independent inputs)

Configure the following information for each external alarm:

Admin sets the Alarm Input to Active (Enable) or Inactive (Disable).

Text is free text for the alarm description. When an alarm input is raised, this text will appear as the alarm description text.

Severity is used to configure the alarm's severity. When an alarm input is raised, the severity will be added to it.

5.1.2.2 Alarm output configuration (single output)

Admin sets the alarm input to active (Enable), inactive (Disable) disregarding current raised alarms and Test. The Test option sends a test message to activate all the external alarms.

Group is used to configure the group of alarms that will trigger an Alarm Output:

Communication - Alarms related to traffic: radio, Ethernet line, TDM line

Quality of Service

Processing - Alarms related to software: configuration, resets, corrupted files

Equipment - Alarms related to hardware, fan, RFU mute, power supply, and inventory.

Environmental - Alarms relating to temperature.

All groups - All of the groups above.



5.1.3 Management

The Management page enables you to define local and remote IP addresses and parameters.



5.1.3.1 IP Configuration

In the Local IP Configuration area, enter the IP address of the local unit, its subnet mask, and the default gateway. Additionally, enter the Floating IP address.

HW address displays the MAC address of the local unit.

In the Remote IP Configuration area, enter the IP address of the remote unit and its subnet mask.

Click Open Remote to open the remote unit's management page.

5.1.3.2 Management Ports

In the Management Ports area, for Number of ports, specify the number of ports that will be used for management data.

For Type, select the management mode of operation - Inband or Out of band.



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.

In-band Management refers to a method in which the network management software sends management packets through the same network it is managing. This differs from out-of-band management in which the network management software uses a different network (overlay network) to communicate with the managed elements.

For Capacity, select the bandwidth that will be allocated to the port(s).

For Auto negotiation, select On to activate the feature, or Off to disable it.

For Rate, select the bit rate you want for the port.

For Duplex, select Half or Full.

5.1.4 Traps Configuration

This page is used to configure traps sent from a Network Element to the NMS system.

Each line in the Trap Managers list displays the setup for a manager defined in the system.

To change the setup for a manager, click the plus box at the beginning of the line.

In the Traps admin field, select Enable to activate trap administration.

For Trap manager, specify the IP address to which traps will be sent.

For Manager name, specify the manager's name.

For Trap port, enter the number of the port through which traps will be sent.

For SNMP trap Community, specify the community name for trap forwarding.

For Heartbeat period (minutes) specify the period of the heartbeat trap.

For Trap CLLI, you can enter free text that will be sent with the trap.

For Trap status change filter, 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.

For Send traps for alarms with severity, select the severity level(s) to determine which types of alarms will be forwarded.

To select/clear all levels, click Select All.



5.1.5 Licensing

This page allows you to view and set IP-10 licensing information.



5.1.5.1 Current License

In the Current License area, the following options are available:

License type - Shows the current license type.

License code - The code you enter to allow usage of specific system features.



5.1.5.2 Demo License

In the Demo License area, the following options are available:

Demo admin - Use this option to activate the demo license.

Demo timer - Displays the elapsed time of the demo license.

5.1.5.3 License Features

In the License Features area, the following options are available:

ACM license - Indicates whether or not the ACM feature is available.

Switch application license - Displays the type of switch application (Pipe, Switch, or Metro).

Capacity -Displays the maximum capacity available for the radio.

Network resiliency license - Indicates whether or not the resiliency

(RSTP/SNCP) feature is available.

TDM capacity license - Indicates whether or not 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 - Indicates the amount of TDM trail capacity corresponding to the TDM capacity license.

Synchronization Unit License - Indicates whether or not the Synchronization Unit License (Synchronous Ethernet output) is allowed.

Enhanced Traffic Manager License – Indicates whether or not the Enhanced Traffic Manager is allowed.

Per usage license - Allows unlimited usage of all features in the system, and generates a billing report of the current usage.



5.1.6 NTP

This page allows you to view and set IP-10 Network Timing Protocol information.

For Admin, select Enable to activate the NTP client, or Disable to deactivate it.

For Server IP, enter the IP address of the NTP server.

Status shows the current condition of the NTP client, which can be Up or Down.

Sync Server shows the IP address of 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, if not synchronized with any clock (valid only when Admin is set to Disable).

Poll Interval is the interval used by the NTP client to maintain synchronization with the current NTP server.





5.1.7 IP Table

This page allows you to configure the characteristics of the peer port, which the local port of the element is connected to.

Each IDU port has its own IP table, allowing the configuration of the characteristics of the peer port to which it is connected.

For Peer MAC address, enter the MAC address of the peer port.

For Peer IP address, enter the IP address of the peer port.

For Peer Slot ID, enter the slot ID of the element (IDU) the peer port is located in. 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.

For Peer port Number, enter the peer port number.

For Peer Description, you can add a general description of the peer port.





5.1.8 SNMP

This page allows you to configure SNMP parameters.



5.1.8.1 SNMP Parameters

Configure the following parameters:

SNMP Version field - select V1 for SNMP V1, or V3 for SNMP V3.

SNMP read community - Enter the password for the SNMP read community.

SNMP write community - Enter the password for the SNMP write community.

5.1.8.2 SNMP V3 User Settings

In the SNMP V3 User Settings area, you can configure the following:

Security Mode - determines the SNMPv3 security mode, which can be:

No security

Authentication (default)

Authentication Privacy

Authentication Algorithm - valid only when security mode is not set to No security. The value can be MD5 or SHA.

User name - the SNMPv3 user name.

Password - if a security mode other than No security was selected, you will be prompted for a password, which has to be at least eight characters.



Click Change User Settings - to apply the SNMP V3 changes.

5.1.9 All ODU

This page allows you to activate support for the All ODU enclosure.

Select Enable for All ODU support, or Disable if your system is not configured as All ODU.



If you select Enable, the All ODU enclosure interface is activated, and the enclosure controller can then be powered to monitor fan failure alarms.

When the enclosure is enabled, 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).



5.1.10 Versions

The Versions pages summarize all installed and running versions of the IDU and RFU.

5.1.10.1 IDU Versions

Target Device - Specific component that is contains the version.

Running Version is the version that is currently running on the IDU.

Installed Version is IDU software files that were successfully installed.

Upgrade Package is IDU software files that were successfully downloaded to the IDU, and are ready to be installed when IDU upgrade is executed.

Downgrade Package is IDU software files that were successfully downloaded to the IDU, and are ready to be installed when IDU downgrade is executed.


5.1.10.2 RFU Versions



RFU Installed Versions - These are RFU software packages currently installed in the IDU, as part of the overall software package.

RFU Running Versions - These are software versions that are currently running on the RFU.

RFU Upgrade & Downgrade Versions - These are RFU software packages successfully downloaded to the IDU, and ready to be installed when RFU Software Download is executed.


5.2 Ethernet Switch

5.2.1 Switch Configuration

FibeAir IP-10 supports Single Pipe and Managed Switch configurations.

Single Pipe is the default option, and does not require a license configuring the IDU to Managed Switch requires a license.

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. This method allows QoS configuration. Other FE (10/100 mbps) interfaces are "functional" interfaces (WSC, Protection, Management).

Managed Switch is an 802.1Q VLAN-aware bridge, allowing L2 switching based on VLANs. Each traffic port can be configured as an "access" port or a "trunk" port, as follows:



Type VLANs Allowed Ingress Frames Allowed Egress Frames

Access Specific VLAN should be

associated with the access port

Only untagged frames (or frames

tagged with VID=0 ("Priority

Tagged")

Untagged

frames

Trunk

A range of VLANs or all VLANs

should be associated with the

trunk port

Only tagged frames Tagged frames

Hybrid

Specific VLAN is used for the

untagged frames

A range of VLANs are associated

with the tagged frames

Tagged and untagged frames Tagged frames

The Managed Switch method allows QoS configuration, and all Ethernet ports are allowed for traffic.

Metro Switch is an 802.1ad Provider Bridge, allowing Q-in-Q switching capabilities. Each traffic port can be assigned as a "Customer Network" port or a "Provider Network" port. The port attributes are listed in the following table:

Type VLANs Allowed Ingress Frames Allowed Egress Frames

Customer

Network

Specific S-VLAN should

be associated with the

customer network port

Untagged frames or tagged

(C-tag) frames

Untagged frames of

tagged (C-tag) frames

Provider

Network

A range of S-VLANs or all

S-VLANs should be

associated with the

provider network port

Only S-tagged frames, (in

accordance with the

configured "provider ether-

type", which is 0x88a8 by

default)

S-tagged frames,

carrying the configured

provider ether-type,

(0x88a8 by default)

S-Tag Ether type can be configured to one of the following values: 0x88a8 (default), 0x8100, 0x9100, or 0x9200.

In the Switch Configuration page, you can choose the Ethernet switching method.



Choose the method you want, as follows:

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.

LAG Load Balancing can be configured as Simple XOR or HASH.

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.

In the Unit allowed VIDs area, you can define VLANs for the managed switch, as follows:

1 In the Operation field, select the operation you want to perform for the VLANs:

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 In the Start VID and End VID fields, enter the VLAN start and end IDs. 3 In the Name field, specify a unique name for the VLAN. 4 Click Apply. The VLAN for the managed switch is defined.

The defined VLANs are summarized at the bottom of the window. The following columns are in this section:

VLAN ID – Specific ID for this VLAN.

Name – Configured name for the VLAN.

Status - Active or Passive

Member Ports - Lists which IDU ports allow this VLAN.


5.2.2 STP Protocol

This page allows you to configure STP parameters.

This option is available only when the system operates in the Managed or Metro Switch modes.

STP (Spanning Tree Protocol) 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.

Select the desired protocol, or Disable to deactivate the protocols.





5.2.3 RSTP and Ring RSTP

These windows enable you to configure RSTP and Ring RSTP parameters and view status information.

RSTP and Ring RSTP algorithms are designed to create loop-free topologies in any network design, which makes it sub-optimal to ring topologies.

The configurations of RSTP and Ring RSTP parameters are identical.

In the (Ring) RSTP Status area, the following information is provided:

Bridge ID - The ID of the bridge in the current monitored IDU.

Root ID - The ID of the root bridge.

Root Path Cost - The cost of the path from the current monitored IDU to the root bridge.

Bridge Role - The role of the bridge, which can be Root or Designated.

In the (Ring) RSTP Configuration area, you can configure the following:

Priority - The priority of the bridge, which is part of the bridge ID.

In the Ethernet Ports that Support (Ring) RSTP table, each interface in the IDU can be configured with the following RSTP parameters.



Priority - Configure the specific priority for this interface.

Path Cost - Configure the path cost for this port. The lower the value the more likely that port is used.

Edge port - This port is not part of the ring itself, and is used as a service access port. Non-edge ports are those that construct the ring.



5.2.4 QoS & 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).

The QoS flow is as follows:

Egress Port #yIngress Port #x

Calssifier

(4 Queues)

5 Policers

(Ingress

Rate

Limiting)

Queue

Controller

Shaper

(Egress rate

limiting)

Marker Scheduler



The QoS & Rate Limiting window contains three sections:

Interfaces - configure the QoS settings for each IDU interface port.

Advanced - configure specific QoS parameters. Clicking on a link opens a separate window.

Copy Ports Configuration - copies the QoS configuration of one interface port to a different interface port.

The Interface section window enables you to configure Quality of Service parameters for each Ethernet port. These parameters include:

Traffic Priorities

Egress Rate Limiting

Ingress Rate Limiting

5.2.4.1 Ingress Classifier

A frame ingressed to a port will be classified according to the following criteria:

1 First Criteria: MAC DA (Destination Address) based. A frame ingressed to a port, carrying a MAC DA that appears in the Static MAC table (see details below), will be classified, its VLAN Pbits will be overwritten (assuming the frame egress is tagged) according to the following options:

Disable - No MAC DA classification or VLAN Pbits will be overwritten (no marking).

Queue Decision - There will only be classification to queue. No marking.

VLAN Pbits Overwrite - Only VLAN Pbits will be overwritten (marked). Classification according to a lower criteria.

Queue Decision & VLAN Pbits Overwrite - Both classification and VLAN Pbits overwrite.



2 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 Pbits overwrite, assuming the frame egress is tagged) will be decided according to the VLAN ID to Queue table (see below), in accordance with the following options:

Disable - No VLAN ID classification or VLAN Pbits overwrite (marking).

Queue Decision - Only classification to queue. No marking.

VLAN Pbits Overwrite - Only VLAN Pbits overwrite (marking). Classification will be according to lower criteria.

Queue Decision & VLAN Pbits Overwrite - Both classification and VLAN Pbits overwrite.

3 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 Pbits - Classification according to VLAN Pbits. Queue is assigned according to the VLAN Pbits Priority Remap table (see below).

IP TOS - Classification according to IP TOS (IP precedence, or IP diffserv). Queue is assigned according to IP Pbits to Queue table (see below).

VLAN Pbits over IP TOS - Classification according to VLAN Pbits, if the ingress frame carries a VLAN and has an IP header.

IP TOS over VLAN Pbits - 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.

4 Default Classification - The default queue decision.

Classifier Tables (in the Advanced field)



5.2.4.2 VLAN Pbits Priority Remap

Single table per port. Allows you to remap VLAN-priority bit values 0-7, to any other preferable value in the range of 0-7. The number of table entries is eight (all CoS legal values).

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).

5.2.4.3 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, and the first queue is the Lowest Priority Queue.

The following scheduling schemes are supported:

Strict for all queues.

Strict for fourth queue, and HRR (Hierarchical Round Robin) 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.

Shaper - Determines the scheduler rate (egress rate limit). Select ON or OFF. The default is OFF.

Shaper Rate - The following rate steps are available:

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.

5.2.4.4 Ingress Rate Limiting

The Ingress Rate Limiting section of the QoS & Rate Limiting window determines the port ingress rate limit.

Attach Policer - Up to five policers per port can be configured, as follows:

The system supports a color blind leaky bucket scheme.

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-Data, TCP-Control, UDP, Non- UDP, Non-TCP-UDP, Queue1, Queue2, Queue3, Queue4.

Limit Exceed Action: Discard frame.





5.2.4.5 Advanced Classifier - VLAN-ID to Queue

Single table for all switches. Used to assign a queue to a frame, 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".



5.2.4.6 Advanced Classifier - IP-Pbits to Queue

Single table for all switches. Used 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. The number of table entries is:

IP Precedence configuration: 8 entries.

DiffServ configuration: 64 entries.

5.2.4.7 Advanced Classifier - VLAN-Pbits to Queue



Single table for all switches. Used to assign a queue to a frame, according to the frame’s Pbits (CoS), assuming the frame is tagged. The number of table entries is eight (all CoS legal values).

5.2.4.8 Advanced Classifier – Queue Weights

Each queue weight can be configured and is used by scheduler when the specific queue is part of HRR scheduling scheme. Queue weights can be configured in the range of 1-32, the higher the weight the higher the priority for that queue.

To configure the QoS queue weights:

1 From the Scheduler Queue drop-down menu, select one of the four QoS queues.

2 From the Weight drop-down menu, select the weight for that queue. 3 Click Apply. The queue weights are configured. 4 Click Refresh. The QoS current queue weights are displayed.



5.2.4.9 Advanced Classifier - Policer List

Click Policer List in the Advanced options area at the bottom of the QoS & Rate Limiting page.

This page enables you to add policy rules to a policer.

Operation - add or delete the policer.

Policer Name - assign a general purpose name for the policer. Note that the name cannot include spaces (you can use underscores instead).

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.

5.2.4.10 Advanced Classifier - Static MAC

Click Static MAC in the Advanced options area at the bottom of the QoS & Rate

Limiting page.

This table is used to load static MAC addresses to the forwarding table of the switch.

The static MACs are never flushed.



VLAN ID is 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.

Static MAC is the 48-bit MAC address, in octet format (xx:xx:xx:xx:xx:xx).

Forward to indicates which port the frame will be forwarded to.

Priority sets the classification and/or VLAN Pbits overwrite (marking), according to the QoS configurations (see QoS & Rate Limiting page above).

5.2.4.11 Copy Ports Configuration

The Copy Ports Configuration section is located at the bottom of the QoS & Rate Limiting for Slots page.

Since it is common to set QoS and rate limiting settings identically in several ports, this option can be used to copy the configurations from one port to another. This saves considerable time and prevents configuration errors.

Copy Priorities Configuration - Copies all Traffic Priorities using the ingress classifier.

Copy Rate Limiting Configuration - Copies the Policer configuration only.



5.2.5 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.

5.2.5.1 Preparing to use Enhanced Traffic Manager

This section describes how to prepare the system to enable the Enhanced Traffic Manager to minimize the impact on traffic. You must disable the egress shaper before you can use the Enhanced Traffic Manager. You should classify the in-band management traffic to ensure that the management signal is not affected.

To prepare to use the Enhanced Traffic Manager:

1 Disable the QoS egress shaper.

i From the navigation tree, select Configuration > Ethernet Switch > QoS & Rate Limiting. The QoS & Rate Limiting window is displayed.

ii Expand the radio port (Ethernet #8). The Traffic Priorities section is displayed.

iii From the Egress shaper drop down menu, select Off. iv Click Apply. The egress shaper is disabled.



2 Configure the classification of the in-band management signal.

i From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Classification. The CoS & Color Classification window is displayed.

ii From the 1st criterion, by in-band management VLAN Id drop-down menu, select Enable.

iii In VLAN Id, enter the VLAN Id for the in-band management signal. This value is configured in the Management Ports section of the Management window.

For more information about configuring the in-band management VLAN Id, see Management Ports on page 34.

iv From the Color drop-down menu, select classification color for the in-band management signal.

v In CoS, enter the CoS value 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.

vi Click Apply. The classification of the in-band management signal is configured.

3 If you are going to use the PTP (Precision Time Protocol) optimized transport feature, disable the Wayside channel.

i From the navigation tree, select Configuration > Interfaces > Wayside Channel. The Wayside Channel window is displayed.



ii From the Wayside admin drop-down menu, select Disable. iii Click Apply. The Wayside channel is disabled.

5.2.5.2 Configuration & Parameters

You can enable the Enhanced Traffic Manager and Precision Time Protocol features from the Configuration & Parameters window. This window also enables you to configure the size of the eight Enhanced Traffic Manager 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 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 the traffic on the radio port. For more information about preparing the system to use the Enhanced Traffic Manager, see Preparing to use Enhanced Traffic Manager on page 58.

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.

The Configuration section enables Enhanced Traffic Manager and Precision Time Protocol.

To enable Enhanced Traffic Manager and Precision Time Protocol:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Configuration & Parameters. The Configuration & Parameters window is displayed.

2 From the Enhanced Traffic Manager drop-down menu, select Enable. 3 From the Precision Time Protocol drop-down menu, select Enable. 4 To apply any change you made, click Apply. 5 To update the information, click Refresh.

PTP optimized transport mode and User Wayside channel are mutual exclusive features. You must disable the User Wayside channel before enabling the PTP optimized transport mode. For more information, see Wayside Channel on page 101.

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.

Changing queue size can impact traffic output.

To configure a priority queue:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Configuration & Parameters. The Configuration & Parameters window is displayed.

2 From the Queue Size priority queue drop-down menu, select the buffer size.

3 Repeat the previous step for all necessary priority queues. 4 To apply any change you made, click Apply. 5 To update the information, click Refresh.

5.2.5.3 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:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Classification.

2 From the First Hierarchy section, select Enable for the classification criteria. More than one criterion can be selected.



3 From the Second Hierarchy section, at the 1st criterion: by in-band management VLAN Id drop-down menu, select Enable.

4 From the Third Hierarchy section, select Enable for the classification criteria. More than one criterion can be selected.

5 Click Apply. The Ethernet frames classification rules are enabled.

5.2.5.4 Classification – Default 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 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Classification. The parameters for the default settings are located at the bottom of the window.

2 In the Default color drop-down menu, select Green or Yellow as the default frame color.

3 In Default CoS, enter the default Class of Service for frames. 4 Click CoS to Queue Classification. The CoS to Queue Classification

window is displayed.



5 Expand a CoS. Enter the new Queue index for that CoS. 6 Click Apply. The new queue index is configured for that CoS.

Each queue is a physical resource which can be assigned to accommodate frames of a specific (or several) CoS(s).

7 Repeat steps 5-6 for other CoS’s that need to be changed. Click Close. The CoS to Queue Classification window is closed.

8 In the CoS & Color Classification window, click Apply. The default classification settings are configured.

5.2.5.5 Classification – First hierarchy

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.



To configure traffic classification rules according to the source MAC Address:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Classification. The CoS & Color Classification window is displayed.

2 From the First Hierarchy section, click MAC Address Table. The MAC Address Table window is displayed.

3 From the Add New Entry section, configure the following parameters:

Row number – Number for this classification rule that is displayed in the # column.

MAC address – The source MAC address that is being classified.

CoS (Class of Service) – The traffic from this MAC address is designated with the configured CoS (0 – 7).

Color – The traffic from this MAC address is designated as Green (compliant) or Yellow (non-compliant).



Up to 16 separate MAC addresses can be configured.

4 Click Apply. The source MAC address classification rules are configured.

To configure traffic classification rules according to the UDP ports:


2 From the First Hierarchy section, click UDP Ports Table. The UDP Ports Table window is displayed.

3 From the Add New Entry section, configure the following parameters: Row number – Number for this classification rule that is displayed in

the # column. Source port – The source UDP port that is being classified. Destination port - The destination UDP port that is being classified. CoS (Class of Service) – The frames associated with this UDP port are

designated with the configured CoS (0 – 7). Color – The frames associated with this UDP port are designated as

Green (compliant) or Yellow (non-compliant).

Up to eight UDP port entries can be configured.

4 Click Apply. The UDP port classification rules are configured.

The following list contains sample UDP port configurations:

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.

The Known Multicast MAC Addresses Table contains a list of 66 destination MAC addresses which are reserved for network protocols use. You can classify the CoS and color of traffic that is being sent to one of the predefined multicast MAC addresses.

To configure traffic classification rules according to the known multicast MAC addresses:


2 From the First Hierarchy section, click Known Multicast MAC Addresses Table. The Known Multicast MAC Addresses Table window is displayed.

3 Expand the MAC address. 4 Configure the following parameters for that MAC address:

CoS (Class of Service) – The traffic to this MAC address is designated with the configured CoS (0 – 7).

Color – The traffic to this MAC address is designated as Green (compliant) or Yellow (non-compliant).

Validity – When Valid is selected, the classification rules are applied to frames that are sent to this destination MAC address.

5 Click Apply. The multicast MAC address classification rule is configured. 6 Repeat steps 3 - 5 for all the required destination MAC addresses.



5.2.5.6 Classification - Second hierarchy

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 in-band management traffic classification rule:


2 From the Second Hierarchy section, configure the following parameters:

VLAN Id – The VLAN identifier number of the in-band management VLAN.

Color – The traffic from the in-band management VLAN ID is designated as Green (compliant) or Yellow (non-compliant).

CoS (Class of Service) – The traffic from the in-band management VLAN ID is designated with the configured CoS (0 – 7).

3 Click Apply. The in-band management VLAN ID classification rule is configured.

5.2.5.7 Classification - Third hierarchy

The third hierarchy contains the classification rules that apply to the most general traffic parameters. The third hierarchy contains following classification criteria:

VLAN P-Bits to CoS

DSCP/TOS Bits to CoS

MPLS exp 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 From the Third Hierarchy section, click VLAN P-Bits to CoS and Color Classification Table. The VLAN P-Bits to CoS and Color Classification Table is displayed.

3 Expand the combination of 802.1P Priority bits and CFI/DEI bit values. The following list explains the columns in this window:

# - Number of the classification rule.

802.1 UP - The P-bits value for this classification rule. The range of options are 0 to 7.

CFI/DEI - The CFI/DEI value for this classification rule. The options are 0 or 1.

Class of Service - The configured CoS for this classification rule.

Color - The configured color for this classification rule.

4 Configure the following parameters for P-bits value:

CoS (Class of Service) – The traffic with this P-bits and CFI/DEI value is designated with the configured CoS (0 – 7).

Color – The traffic with this P-bits and CFI/DEI value is designated as Green (compliant) or Yellow (non-compliant).

5 Click Apply. The multicast VLAN P-Bits classification rule is configured. 6 Repeat steps 3 - 5 for other VLAN P-Bits that need to be configured.



Differentiated Service Code Point (DSCP) or Type of Service (TOS) is a 6 bit length field inside the IP datagram header carrying priority information.

The following figure describes the IPv4 datagram header format:

Classification by DSCP bits can be used for untagged frames as well as 802.1Q tagged and/or provider VLAN tagged frames.

The classifier also supports classification by Traffic Class (TC) of the IPv6. Whatever IP protocol version is used, the classifier extracts the adjacent field automatically.

To configure DSCP/TOC P-bits traffic classification rules:


2 From the Third Hierarchy section, click DSCP/TOS Bits to CoS and Color Classification Table. The DSCP/TOS Bits to CoS and Color Classification Table is displayed.

3 Expand the DSCP/TOS bits value. 4 Configure the following parameters for that DSCP/TOS value:

CoS (Class of Service) – The traffic with this DSCP/TOS bits value is designated with the configured CoS (0 – 7).

Color – The traffic with this DSCP/TOS bits value is designated as Green (compliant) or Yellow (non-compliant).

5 Click Apply. The DSCP/TOS classification rule is configured.



6 Repeat steps 3 - 5 for other DSCP/TOS bits values that need to be configured.

MPLS experimental bits are used to provide QoS capabilities by utilizing the bits set in the MPLS labels. The following figure shows the MPLS label format:

Classification by MPLS experimental bits is supported in both untagged and/or 802.1Q/provider tagged frames.

To configure MPLS experimental bits traffic classification rules:


2 From the Second Hierarchy section, click MPLS exp Bits to CoS and Color Classification Table. The MPLS experimental Bits to CoS and Color Classification Table is displayed.

3 Expand the MPLS experimental bits value. 4 Configure the following parameters for that MPLS experimental bits value:

CoS (Class of Service) – The traffic with this MPLS experimental bits value is designated with the configured CoS (0 – 7).

Color – The traffic with this MPLS experimental bits value is designated as Green (compliant) or Yellow (non-compliant).

5 Click Apply. The MPLS experimental bits classification rule is configured.



6 Repeat steps 3 - 5 for other MPLS experimental bits values that need to be configured.

5.2.5.8 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. For more information about using WRED with IP-10, see IP-10 Feature Description.

To enable Enhanced Traffic Manager for WRED:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > WRED. The WRED window is displayed.

2 From the WRED admin section, click Enable. The Enhanced Traffic Manager for WRED is enabled.

Each of the eight priority queues can be given a different WRED profile curve. This 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 rules:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > WRED. The WRED window is displayed.

2 Expand the WRED queue. The WRED Thresholds queue configuration pane is displayed.



3 Configure the following WRED parameters for the priority queue:

Green packets low threshold – Minimum throughput of green packets for this queue. When this value is reached, the system begins dropping green packets in this queue.

Green packets high threshold – Maximum throughput of green packets for this queue. After this value is reached, all green packets in this queue are dropped.

Green packets maximal drop percentage – Maximum percentage of dropped green packets for this queue.

Yellow packets low threshold - Minimum throughput of yellow packets for this queue. When this value is reached, the system begins dropping yellow packets in this queue.

Yellow packets high threshold - Maximum throughput of yellow packets for this queue. After this value is reached, all yellow packets in this queue are dropped.

Yellow packets maximal drop percentage - Maximum percentage of dropped yellow packets for this queue.

4 Click Apply. The MPLS experimental bits classification rule is configured. 5 Repeat steps 2 - 4 for other MPLS experimental bits values that need to be

configured.

5.2.5.9 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. For more information about using the Egress Shaper and Scheduler, see the IP-10 Feature Description Guide.

To enable Egress Shaper and Scheduler:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Egress Shaper & Scheduler. The Egress Shaper & Scheduler window is displayed.



2 From the Global Shaper admin section, click Enable. The Egress Shaper and Scheduler feature is enabled.

To configure Egress shaper and scheduler for the priority queues:

1 From the navigation tree, select Configuration > Ethernet Switch > Enhanced Traffic Manager > Egress Shaper & Scheduler. The Egress Shaper & Scheduler window is displayed.

2 From the Queue Configuration section, expand a priority queue. The Egress Shaper & Scheduler queue configuration pane is displayed.

3 Configure the following Egress shaper and scheduler parameters for the priority queue:

Priority – Egress priority for this queue. The queue with a higher priority egresses before a lower one regardless of WFQ weights.

WFQ weight – Sets the ratio for allowed bandwidth to queues with the same priority. Sample configuration - 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.

Shaper admin – When Enable is selected, the Egress shaper and scheduler configuration is used for this priority queue.



CIR – Committed Information Rate for this queue.

CBS – Committed Burst Size for this queue.

Line compensation –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.

5.3 Radio

The Radio menu includes the Radio Parameters and Radio Thresholds items.

5.3.1 Radio Parameters

The Radio Parameters window enables you to configure how the radio operates.



The explanation of how to configure the IF Combining parameters is discussed in the Radio Diversity section. For more information, see IF Combining Parameters on page 108.

This window also controls the MAC header compression feature. Radio transmission (compared with Fiber optics and other line base links) has limited bandwidth and compression is required to improve available capacity utilization. The benefit of using MAC header compression is that it can be used as a supplement to the other compression without affecting traffic performance.

Ceragon proprietary MAC Header compression improves the effective throughput by up to 45%, and does not affect user traffic.

MAC header compression is based on the following:

Dropping the Preamble + SFD + IFG saves 20 bytes.

Dropping the Ethernet type saves 2 bytes.

Adding a GFP header adds 4 bytes.

In addition:

Frequently repeating SA & DA are learned.



Learned DA & SA are not transmitted.

A short pointer is used instead of the original 12 bytes.

Effectiveness is reduced if a high number of L2 flows are used.

The capacity reached after header compression, in accordance with the Ethernet packet length, is as follows:

Ethernet Packet Size

Capacity after Compression

64 45%

96 29%

128 22%

256 11%

512 5%

5.3.1.1 Status Parameters

The Status Parameters section of the Radio Parameters window displays the status of the RFU.

To view the RFU status parameters:

1 From the navigation tree, select Configuration > Radio > Radio Parameters. The Radio Parameters window is displayed.

2 From the bottom of the Radio Parameters window, click Refresh. The current RFU status parameters are displayed in the Status Parameters section.

3 The RFU Installed Version section contains the following information:

RFU type - The RFU used in the system (1500HP, RFU-C, other).

Tx/Rx frequency separation - Read-only, Tx/Rx separation values.

Tx/Rx level - Read-only, current Tx/Rx level values.



MSE - Mean Square Error value, which quantifies the performance of the receiver.

XPI level - Read only, displays the current cross polarization interference value.

Defective blocks - Amount of blocks in which errors were detected. The larger the amount, the poorer the radio link quality.

4 To reset the counters in the Status Parameters section, from the bottom of the Radio Parameters window, click Clear Counters.

5.3.1.2 Frequency Control

To configure the Tx and Rx frequencies:


2 From the bottom of the Radio Parameters window, click Refresh. The current Tx and Rx frequencies are displayed in the Frequency Control section.

3 In Tx frequency, enter the transmission radio frequency. 4 In Rx frequency, enter the received radio frequency. 5 Select Set also remote unit, to configure the remote unit with the

identical radio frequency configuration. 6 From the bottom of the Radio Parameters window, click Apply. The Tx and

Rx frequencies are configured.

5.3.1.3 Configuration Parameters

To configure the radio parameters:


2 From the bottom of the Radio Parameters window, click Refresh. The current radio parameters are displayed in the Configuration Parameters section.



3 From the Radio IF interface drop-down menu, select one of the following options:

Enable – Activates the radio interface.

Disable – Deactivates the radio interface. Allows the user to enable/disable the radio interface.

Changing the Radio IF interface requires a system reset.

4 The Radio IF operational status field displays the current status of the radio interface.

5 From the Mute Tx drop-down menu select one of the following options:

Enable – Activates Tx muting.

Disable – Deactivates Tx muting.

6 In Max Tx level, enter the maximum operational Tx value. 7 In Link ID, enter the identification number of the link.

When working with an IDU that has the Link ID feature on one end and an IDU that does not have this feature on the other end, set the Link ID to 1.

8 From the MAC header compression drop-down menu select one of the following options:

Enable – Activates MAC header compression.

Disable – Deactivates MAC header compression.

9 From the bottom of the Radio Parameters window, click Apply. The radio parameters are configured.

5.3.1.4 XPIC Parameters

To view if XPIC is enabled:


2 From the bottom of the Radio Parameters window, click Refresh. The current radio parameters are displayed in the XPIC Parameters section.

5.3.1.5 Green Mode

You can enable Green Mode to reduce the amount of electricity that is used by the RFU.

To view the Green Mode parameters:


2 From the bottom of the Radio Parameters window, click Refresh. The current radio parameters are displayed in the Green Mode section.

Comment [YS1]: Need explanation for this

section



The following parameters are displayed in this section:

Green mode admin - Displays whether green mode is active or not.

Green mode ref rx level - Displays the current Ref Rx level.

5.3.1.6 Multi Radio

Multi-radio 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.

This feature is available only for IDUs which are inserted in a shelf.

Multi-radio cannot be used in tandem with the following features:

1+1 HSB

Space Diversity

Multi-radio 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).

You should ensure that the two radio links are using the same radio script in order for Multi-radio to perform at maximum efficiency.

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-radio 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.

To configure the Multi Radio settings:


2 From the bottom of the Radio Parameters window, click Refresh. The current radio parameters are displayed in the Multi Radio section.



All of the configuration options are only displayed after Multi-Radio is enabled.

3 From the Multi-Radio admin drop-down menu, select one of the following options:

Enable - Activates the Multi-radio feature. You must click Apply to display the other configuration options.

Disable – Deactivates the Multi-radio feature.

4 If necessary, click Apply. The Multi-radio is enabled and the Multi-radio configuration options are displayed.

5 When there is a problem with the IDU in slot #1, you should block traffic to that radio port. From the Block radio (slot #1) drop-down menu, select one of the following options:

On - Blocking traffic to radio port in slot #1. All traffic is sent to radio part in slot #2.

Off – Default setting, no traffic is blocked.

6 When there is a problem with the IDU in slot #2 you should block traffic to that radio port. From the Block radio (slot #2) drop-down menu, select one of the following options:

On - Blocking traffic to radio port in slot #2. All traffic is sent to radio part in slot #1.

Off – Default setting, no traffic is blocked.

7 From the Signal degrade admin drop-down menu, select one of the following options:

Enable - If a signal degrades below the configured threshold, the link is shut down.

Disable – The system does not make any changes if there is a signal degrade problem.

For more information on configuring the signal degrade threshold, see Radio Thresholds on page 83.

8 From the Excessive ber admin drop-down menu, select one of the following options:

Enable - If the BER (Bit Error Rate) exceeds the configured threshold, the link is shut down.

Disable – The system does not make any changes if there is a BER problem.

For more information on configuring the BER threshold, see Radio Thresholds on page 83.

9 Click Apply. The Multi-radio settings are configured.



5.3.2 Remote Radio

In this page, you can configure how the remote radio operates.

Remote communication - The current communication status of the remote unit.

Remote IP address - The IP address of the remote unit.

To open the remote radio configuration, click Open Remote.

Remote Rx level - The current Rx level of the remote unit.

Remote force max Tx level - Used to force the remote unit maximum transmit level.

Remote ATPC reference Rx Level - Used to configure the ATPC Rx level of the remote unit.

Remote floating IP address - Used to configure the remote floating IP address.

To unmute the remote unit transmitter output, click Force Unmute.





5.3.3 Radio Thresholds

In this page, you can configure radio threshold levels.

For Radio excessive BER threshold, click the drop-down list and select the level above which an excessive BER alarm is issued for errors detected over the radio link.

For Radio signal degrade threshold, select the level above which a Signal Degrade alarm is issued for errors detected over the radio link.

The Radio BER field is read-only and shows the value above which a BER alarm is issued for errors detected over the radio link.





5.3.4 MRMC Configuration

In this page, you can configure MRMC script parameters.

5.3.4.1 MRMC Configuration

MRMC Scripts 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.

Operational mode can be ACM Adaptive, ACM Fixed, Regular (non ACM radio script).

Min adaptive ACM profile is the minimum configured profile that will never be exceeded when ACM is active.

Max adaptive ACM profile is the maximum configured profile that will never be exceeded when ACM is active.

Adaptive Tx power admin displays is power admin is enabled. When enabled, the radio power is adjusted to the current profile that is being used.

5.3.4.2 Current TX

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.



5.3.4.3 Current RX

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.

5.3.4.4 MRMC Table

This table contains all available radio scripts.

Select the desired script and mode (regular or ACM).

When you expand the line of the selected script (by clicking the +) all available options for the selected script will appear.

For regular scripts, select a radio script that does not have an ACM prefix. Expand the line (by clicking the +), and then click Apply.



5.3.4.5 MRMC Table – ACM Scripts

ACM scripts can be distinguished from regular scripts by their ACM prefix. For ACM scripts, expand the line (by clicking the +).

Two options are available for ACM scripts:

ACM Fixed Mode - In this mode, the ACM engine will be disabled. To select a desired profile, expand the line (click the +), and choose the profile. The radio will use only the profile you selected.

ACM Adaptive Mode (shown in the page below) - In this mode, the radio will be adaptive, and the ACM engine will be enabled. To select a maximum profile, expand the line (click the +), and select the profile. The profile is the maximum that the ACM may reach, but never exceed.

When configuring ACM script with Adaptive Mode, you can determine whether or not the RFU power will be adaptive as well.

In the Adaptive Power admin field, enable or disable the capability to adapt the power.

In the Reference class field, configure the system reference class, which can be "Class-2/4/5B/6A" for ETSI, or “FCC” for FCC.



ACM can operate in one of two scenarios:

Increase capacity (increase throughput)

Increase availability

The first scenario is for customers with links of several E1s in a low class, and now want to use ACM to add Ethernet traffic with lower availability.

The second scenario is for customers who plan the link for a specific availability and capacity, but want lower capacity even in higher fades.

In the first scenario, the user will plan the link according to low class channel, and when the condition allows, the link will increase the modulation. This increase of modulation may require lowering the output power to decrease the non-linearity of the transmitter for the higher constellations.

Adaptive power options can be enabled or disabled. If disabled, the maximum Tx power in lower constellations is limited by the highest modulation. If enabled, the maximum Tx power in lower constellations is limited by the reference class configured, as listed in the following table.

Reference Class Configuration

Reference QAM

Class 2 4

Class 4 16

Class 5B 64

Class 6A 256

FCC 4

If the adaptive feature is used, a few critical dBs can be gained in the lower constellations.



5.3.5 Traffic Priority

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 enables you to configure whether TDM or Ethernet 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). For more information on configuring TDM traffic priority, see Configuring TDM Trails on page 111.

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. For more information on configuring Ethernet traffic priority:

QoS & Rate Limiting – see Advanced Classifier – Queue Weights on page 55.

Enhanced Traffic Manager – see Configuration & Parameters on page 60.

The following list details the priorities for the different Traffic Priority schemes:

High TDM over Ethernet (default)

iv TDM high priority v TDM low priority vi Ethernet

High Ethernet over TDM

i Ethernet high priority ii TDM high priority iii TDM low priority iv Ethernet low priority

High TDM over high Ethernet

i TDM high priority ii Ethernet high priority iii TDM low priority iv Ethernet low priority



To configure Traffic Priority:

1 From the Traffic priority scheme drop-down menu, select a Traffic Priority option.

2 In the High-priority Ethernet BW field, enter the available bandwidth for High-priority Ethernet traffic.

3 Click Apply. The Traffic Priority is configured.

The following 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.



5.3.6 ATPC

ATPC admin - To enable/disable the ATPC (Automatic Transmit Power Control) mechanism.

ATPC reference RSL - The RSL reference value for the ATPC mechanism.



5.4 Interfaces

5.4.1 Ethernet Ports

In this page, you can configure Ethernet port parameters.

The following list explains the columns in the Ethernet Ports window.

Operational Status is read-only and indicates whether or not the port is operating.

Enabled – A check mark indicates that this port is enabled.

Interface – Displays the port number.

Connector Type – Displays whether this port is using copper (RJ-45) cable or optical fiber.

Speed & Duplex – Displays some or all of the following parameters for this port:

Auto negotiation

Rate

Actual Rate

Actual Duplex

Function – Displays if this port is being used for Trunk, Access or Management.

For Metro Switches, displays is the port is being used for C/N, P/N or Management.

VLAN ID – Lists all the allowed VIDs for this port.

Learning – A check mark indicates that Port Learning is enabled.

Flow Control – Displays whether Flow Control is On or Off.



Service Type – Displays whether this port is a network or access point.

Automatic state propagation - This feature enables propagation of radio failures back to the line, to improve the recovery performance of resiliency protocols (such as xSTP). You can enable or disable this feature.

5.4.1.1 Configuring a specific port

In the Managed Switch, Metro Switch, or Single Pipe Ethernet Ports area, you can configure the parameters for a specific port on the IDU.

Single Pipe Ethernet Ports Configuration

In the Port admin field, select Enable if you want to activate the port.

In the Connector type field, select RJ 45 or Optical connector type.

In the Type field, the option depends on the Ethernet application, which may be from the following options:

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.

Managed Switch Ethernet Ports Configuration

For Default VLAN ID (not used in the single pipe switch application), enter the VLAN ID number.



For Auto Negotiation, select On if you want the system to control the flow of data.

Flow Control (only used for the single pipe switch configuration), select On or Off to activate or deactivate the traffic control mechanism.

Rate is read-only and displays the Ethernet rate.

Port service type - Define whether this port is a network or access port.

The Port service type is configured for the PolyView NMS. Ethernet services.

Single Pipe Ethernet Ports Configuration - Optical SFP Connector

For Duplex, displays full or half duplex.



5.4.1.2 Defining a LAG PORT

Click Create Lag port to define a LAG port group.

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.

There can be up to three LAG groups per IDU. 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 from different groups cannot be in the same LAG):

Ports 1-2 and 8 (GBE ports and radio)

Ports 3-7 (FE only ports)

To add or remove ports in the LAG group, select the desired port in the window. Ports selected for the LAG group are highlighted; and ports selected for deletion are cleared in the window.

The system will not allow selection of ports with different configurations (such ports will not be highlighted).

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.

A LAG port can be configured as “LAG #1, #2, #3”, since there can be up to three LAG ports in the system.

When a LAG is created by adding a first port to it, the LAG will automatically inherit all characteristics of the ports, except for the xSTP role (edge, non-



edge), and the path cost. The LAG will initially receive default values for those parameters.

In the Configuration page, the lag ports are listed in the Interface column.

In the Advanced line, you can click Allowed VIDs to assign VIDs to the LAG.

LAG Group Notes:

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.



5.4.1.3 Defining Fault Criteria

In the Fault Criteria area of the Ethernet Ports page, the following options allow you to determine which faults should be propagated back to the line.

Local LOF - When Automatic State Propagation is enabled, an LOF (Radio Loss of Frame) fault will always be propagated.

Link ID Mismatch - When Automatic State Propagation is enabled, a Radio Link ID mismatch fault will always be propagated.

MAC address ageing time - The aging time used by the MAC learning table

can be a value between 15 and 3825 seconds. The default value is 300 seconds.

Ethernet shutdown Rx profile threshold - When ACM adaptive mode is active, you can determine an Rx profile that will be considered a fault when the radio performance degrades below that profile.

Local Excessive BER - When an Excessive BER alarm is raised locally, it will be propagated as a fault.

Local LOC - When a Loss of Carrier alarm (only for optical GBE interface) is raised, it will be propagated as a fault.

Remote Fault - If any of the events described above occurs at the remote (remote fault), it will be propagated locally as a fault.





5.4.2 E1 Ports

In this page, you can configure E1 port parameters.

In the All Ports area at the top of the page, the parameters you can configure include the following:

Excessive BER threshold - Click the drop-down list and select the level above which an excessive BER alarm is issued for errors detected over the radio link.

Signal degrade threshold - Click the drop-down list and select the level above which a Signal Degrade alarm is issued for errors detected over the link.

5.4.2.1 Configuring the Line Coding

Line code 1-8 and 9-16 – Displays the T1 line coding, which can be B8ZS or AMI.



5.4.3 Using an E1/T1 T-Card

The T-Card is not a stand-alone entity within the IP-10 IDU. When inserted in the system, the new interfaces become integral interfaces of the IP-10.

As an example, if you insert a 16 x E1 T-Card in the IDU, no special menu will appear for it. Instead, E1s #17-32 will be added to the existing 1-16.

5.4.4 DS1 Ports

In this page, you can configure DS1 port parameters.

The parameters in this page are the same as those for the E1 Ports page above.

5.4.5 STM-1/OC-3 (T-Card)

The following diagram shows an IP-10 with an STM-1/OC-3 T-Card.

To configure the STM-1/OC-3 T-Card interface:

1 Click in the area of the STM-1/OC-3 interface, or, from the menus on the left side of the window, select Configuration, Interfaces, STM1 Ports (for an E1 board) or OC-3 Ports (for a T1 board). The following window appears:



2 Fill in the fields as follows:

i Configure parameters in the STM-1 Configuration section.

Port Admin - Select Enable to activate the interface, or Disable to deactivate it.

Mute Tx - Used to force mute or unmute the T-Card interface. If muted, the radio will still receive signals, but will not transmit any.

Outgoing signal clock source - the clock source used, which can be Internal clock, Loop, or STM-1 VC.

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



# LOF from Framer LOS from Optics Mode of Operation Clock Source

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 – The clock source that is currently set.

Synchronization VC - The VC channel that is used to synchronize the STM-1 interface.

AIS VC Signaling Admin - 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.

Line Tx Protection Mode - If you choose Normal, the system will behave regularly when configuring the system to 1+1 with the STM-1 card. The redundant STM-1 will not transmit signals unless the primary IDU 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 will actually function, will be decided by other equipment connected to it.

ii Configure parameters in the Trace Identifier (J0) section.

Received Trace Identifier - Read-only field. The received trace identifier, used to verify ongoing connection to the transmitter.

Transmit Trace Identifier - The trace identifier used to verify ongoing connection to the receiver.

Expected Trace Identifier - The trace identifier that will be used to verify ongoing connection to the remote side of the link.

Trace Identifier String Length - Can be between 1 and 15 characters.

iii Configure parameters in the Thresholds section.

Excessive BER Threshold - The value can be 1e-3, 1e-4, or 1e-5.

Signal Degrade Threshold - The value can be 1e-6, 1e-7, 1e-8, or 1e-9.



5.4.6 Wayside Channel

In this page, you can configure wayside channel parameters.

The parameters you can configure include:

Wayside admin - select Enable if you want to activate the channel.

Capacity - select Narrow or Wide for the wayside channel capacity.

Auto negotiation - select On if you want the system to control the data flow between the wayside channel and other ports activated in the system.

Duplex - select Full or Half duplex.

Rate - select the data rate for the port.



User Wayside channel and PTP optimized transport mode are mutual exclusive features. You should disable the PTP optimized transport mode before enabling the User Wayside channel. For more information, see Wayside Channel on page 101.



5.4.7 User Channel

In this page, you can configure user channel parameters.

Admin - To enable or disable the user channel.

Type - Two user channel types are available:

Asynchronous RS-232

Asynchronous V.11/X.21



5.4.8 EOW

This page displays the EOW (Engineering Order Wire) channel status.

5.4.9 AIS

This page is used to enable/disable AIS (Alarm Indication Signal) Line Detection.



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.

5.4.10 Sync Source

Synchronous Ethernet consists of the transport of a frequency timing reference through the Ethernet physical layer. It allows the receiving side of an Ethernet link to lock onto the physical layer clock of the received Ethernet signal, which was derived from a reference clock source. The receiver is therefore frequency-synchronized with the source.

IP-10 allows synchronization of the frequency of the outgoing Ethernet carrier signal with any existing TDM trail.

To configure the sync source:

1 Select Primary. 2 From the IDU that is displayed, click the interface type

(Line/STM-1/Radio) to select it as the synchronization source. 3 Select the interface number and click Apply.

Repeat the procedure for the secondary sync source.

If you choose an interface and then click Apply, the configuration will be cleared.

The Sync Parameters section enables you to set the amount of time before the unit reverts back to the primary sync source.

From the Sync source revertive timer field, enter the number of seconds that the unit waits before reverting to the primary sync source.



5.4.11 Clock Source

The Clock Source window configures the ports that output the clock source.

The Current Configuration section displays the clock source output for each interface.

You can configure each interface and select whether the clock source is based on a received sync source or the local internal IDU source.

To configure the clock source:

1 From the Clock Source Selection section, click on an interface (Line/STM-1/Radio). A clock source drop-down menu is displayed.

2 From the clock source drop-down menu, select the clock source.

E1 clock source - select the E1 port that outputs the clock source.

Ethernet Clock source - select how the clock source is calculated:

Local - internal

Sync - received from sync source

Radio - select the channel that outputs the clock source.

3 Click Apply. The clock source for that interface is configured.



5.5 Protection

5.5.1 Protection Parameters

In this page, you can configure IP-10 1+1 and 2+2 protection parameters.

In the Protection Admin field, Select 1+1 HSB, 2+2 HSB, or Disable, and click Apply.

The following illustration shows the IDU configuration for a 2+2 HSB system. The shield icon to the left of the IDUs indicates that they are in a Protected configuration.



The following sections appear when you select 1+1 HSB or 2+2 HSB.

5.5.1.1 Protection Configuration

Protection admin - Used to enable or disable 1+1 or 2+2 protection.

Protection mode - Shows if the unit is Active or Standby.

5.5.1.2 Mate Parameters

Mate IP address - the IP address of the mate unit.

Mate MAC address - the MAC address of the mate unit.

Open Mate - a link for opening the remote mate unit.

5.5.1.3 Protection Switch Criteria

External alarm #1 admin (enable/disable) - initiates a switchover when external alarm #1 is raised.

Radio excessive BER admin (enable/disable) - initiates 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.

5.5.1.4 Protection Commands

Protection Lockout - freezes the current protection state.

Protection force switch - forces a protection switchover and then freezes the protection state.

Copy to mate status - Indicates the status of the Copy to mate command.



Manual Switch - issues a switchover, which will take affect when no other protection related alarms are raised.

Copy to mate - copies all configurations to the mate unit (configuration synchronization between local and mate).



5.5.2 Radio Diversity

The Radio Diversity feature can be used with configurations that are using two antennas. There are two modes for using two antennas with a single system: 1+0 IF combining and 1+1 Space diversity.

1+1 Space diversity is a feature that enables the system to dynamically choose at every moment the best received signal between two radio carriers configured as 1+1 HSB. This allows data flow to be unaffected in the event of unwanted physical events affecting the radio channel, such as fading. It is implemented at the base-band level and thus requires no special RFU connections or upgrades. This feature is available only for IDUs which are inserted in a shelf.

1+0 (IFC - IF combining) is a feature for configurations that use two antennas with a single RFU-HP with two Rx ports and a single IDU. The selected signal line output is based upon the Rx signal at the RFU.

5.5.2.1 IF Combining Parameters

IF Combining parameters are located at the bottom of the Radio Parameters window. (Configuration > Radio > Radio Parameters)

To perform delay calibration:

Automatic - Click Calibrate. The system automatically calibrates the required delay between the signals from the main and diversity antennas.

Manual - From Delay calibration, enter the signal delay in nanoseconds. Click Apply.

RFU Mode - There are three options

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.

In order to use Combined mode, you must perform delay calibration.

RSL connector source - Select which antenna is the source for the external connector.

Main - The main antenna is selected.

Diversity - The diversity antenna is selected.

Rx level diversity - The Rx level of the diversity antenna.

Rx level combined - The Rx level of the combined signals.

Delay calibration - (Only used for Combined mode) The delay between the main and diversity signals in order that they are calibrated correctly to be combined.

Automatic delay calibration - Displays the system status of the automatic delay calibration feature.

Success - the system has successfully calibrated the signal delay

Failure - The system cannot automatically calibrate the signal delay.

No action - The system has not performed an automatic delay calibration.

Automatic delay calibration can only be performed when the system is error-free and there is no negative weather conditions.

5.5.2.2 Space Diversity 1+1 Baseband

This section explains how to configure the Radio Diversity feature for a 1+1 Baseband configuration.

The decision for the best signal line output is based upon performance of the modems.



Radio Diversity - Select Space diversity and click Apply, to enable the radio diversity feature.

The Diversity Status section contains the following fields:

Switch Counter - Displays the number of times that there was a switch between the main and standby IDUs

Receive radio traffic - Which RFU is providing the signal to the active IDU.

Operation mode - Displays whether Radio Diversity is enabled.

The Revertive mode feature enables the system to automatically revert to the local RFU after it has switched to the mate RFU. The Revertive Parameters section contains the following fields:

Revertive mode - Select Revertive to enable the system to revert back to the primary RFU.

Primary RFU - Select whether the Local or Mate is the primary RFU.

Revertive timer (seconds) - Configures the number of seconds that the system waits before reverting back to the primary RFU.

The system only reverts to the primary RFU when the signal contains no errors.

The Force Active section enables you to manually switch the active radio.

Switch Request button - Clicking Switch Request, sends to message to the system to switch to the opposite radio.

In a situation where the system does not allow you to switch radios using the Switch Request button, you can use the Force to radio option.

Force to radio - This command forces the system to switch to the selected option from the drop-down menu. Select one of the following options:



Local radio - When the Mate radio is active, select this option to force the system to switch radios.

Mate radio - When the Mate radio is active, select this option to force the system to switch radios.

Click Apply. The radios are switched.

5.6 Trails

5.6.1 Configuring TDM Trails

This page is used to configure the FibeAir® IP-10 Cross Connect (XC) system for operation.

FibeAir IP-10 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 IDUs placed together in a single chassis, for TDM traffic cross connect. The following figure displays a nodal enclosure that can contain up to six IP-10 IDUs:

Once the IDUs are linked through the common backplane (as shown in the photo above), the XC system is constructed by building trails.

To configure the trails for Cross-Connect operation:

1 Start the IP-10 Web Management application. The following web page is an example of the IP-10 IDUs that appear in a nodal configuration.



Trail building is only done via the Main IDU (Slot 1 at the bottom). However, you can select any other IDU to set other configuration parameters for all the other IDUs in the shelf.

2 On the left side of the main window, select Configuration > Trails > TDM Trails. Initially, the page that appears is empty.

3 Click Add, to create a new trail. The Add New Trail window appears. 4 To select the E1/T1 ports for the trail, in the Add New Trail window:

i Click the E1/T1 interface in any IDU ii Select the E1/T1, as shown in the example below.



iii For STM-1/OC-3 trails, the window appears as follows:



5 To select the VC number you want to assign to the trail:

Click the RF interface in any IDU, as shown in the example page above.

6 In the Add New Trail window, configure the new TDM trail. Configure the Protection options. If you want a secondary trail to cover the main trail if it fails, you must choose one of the following options:

Protected 1+1 - used for an SNCP protected trail, with permanent use of bandwidth in both paths.

Protected ABR - protected ABR (1:1), used 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, a second interface will appear in the Add New Trail window, as follows:

In the Trail ID field, enter the ID of the trail. This ID is used to ensure that the flow of data over the link matches the trail designations.

In the Trail Description field, enter a textual description of the trail for further identification purposes.

In the ACM Priority field, select High or Low. Adaptive Coding & Modulation employs the highest possible modulation during changing environmental conditions, which may be from QPSK to 256 QAM. If you select High for priority, the system will ensure that this trail is used to pass traffic when throughput for other trails is less efficient.

In the Reserved/Operational field, set the trail to Operational to enable its operation. If you want to define the trail, but keep it inactive for the time being, select Reserved.

5.6.1.1 TDM Trails Configuration Notes

For the trail to function properly, it must be configured accordingly on both sides of the link.

If a unit (IDU) 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 IDU can then function as a stand-alone unit, using a "default" E1/T1 configuration.

You can configure E1/T1 ports in the E1/T1 Ports page:



However, note that you do not enable the ports in this page.

The ports are enabled only in accordance with the trails that you configure, as described in this guide.

5.6.1.2 Connected Ports

The following is an example of connected trail ports and their system status.

Example of Trail List for the E1/T1 Interface



Example of Trail List for the STM-1/OC-3 Interface

5.6.1.3 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 (Command Line Interface), this is done by setting the interface type to STM1 instead of Line.

For example, for a trail between VC#1 in the radio and VC-12 #1 in the STM-1 interface of slot number one, you would use the following command:

add-trail id1 desc1 high operational unprotected 1 stm1 1 1 radio 1

As with other interface types, the number after the interface type represents the interface number.

For STM-1, this means which VC-12 to use. The KLM slot to be used corresponds to the VC number chosen, as specified in the ITU-T G.707 clause 7.3 standard.



The following table summarizes:

Thus, for example, interface number 35 corresponds to TS#35 in the above table, which is KLM address 252 (TU-3#2, TU-2#5, TU-12#2).



6. Service OAM

6.1 MAID List

MAID (Maintenance Association Identifier) is an identifier for a Maintenance Association, unique over the domain that CFM is to protect against the accidental concatenation of service instances. The MAID has two parts: the Maintenance Domain Name and the Short MA Name.

6.1.1 MAID List Columns

# is the domain number (internal number of the displayed function).

Status is the status of the current domain, which can be one of the following:

No MEPs - only MAID configured, no MEPs. This state is used for empty domains, before defining MEPs, or for a domain that contains only MIPs.

Monitoring - CFM (CCM) - proactive monitoring is running, no error found.

Failure - connectivity error in at least one MEP.

Domain name is the maintenance domain name.

Level is the maintenance domain level.

Association name is the maintenance domain association name.

VLAN ID is the identification # of the VLAN

Send CCM shows 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 is 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.

6.1.2 MAID List Operations

Click Add to add a new MAID.

In the Add Maid window, for Domain name specify the maintenance domain name.

Level is the maintenance domain level.

Association name is the maintenance domain association name.

VLAN ID is the MAID VLAN ID.

To delete a MAID, from the MAID list section mark the checkbox at the end of its line, and click Delete selected.

Click Apply to apply the changes.

Click Refresh to refresh the page.

6.1.3 MAID List MEPs



6.1.4 Local MEP

Local MEP Columns:

MEP ID - the local MEP ID.

Direction - MEP direction (up or down).

Ethernet port - the Ethernet port the MEP is located on.

MAC address - Ethernet protection MAC address.

Priority - the Pbit priority that the CCM message carries.

LDI - Local Defect Indication. If the value Yes, a + in the right corner of the table describes the reasons for this bug.

Connected - Local MEP connection status.

Add - add new local MEP.

Delete selected - delete the selected local MEP.

The following parameters can be configured from the Add MEP to Port window:

Ethernet port - Displays the selected port number on which the local MEP is located.

Local MEP ID - The ID of the MAID local MEP.

Level- Specify the MAID domain level.

VLAN ID - Specify the MAID VLAN.

Direction - The local MEP direction.

Priority - The Pbit priority that the CCM message carries.



6.1.5 CCM Configuration

The following options are available in the CCM Configuration section of the MAID List window:

Send CCM - Select Disable if you don't want continuity messages (CCM) sent over the specific MAID. Select Enable if you want continuity messages (CCM) sent over the MAID.

CCM Interval - Set the MAID time interval, which can be 1 second, 10 seconds, 1 Minute, or 10 Minutes.

6.1.6 Remote MEP

This section discusses the Remote MEP section of the MAID List window.

6.1.6.1 Remote MEP Columns

The following list explains the columns in the Remote MEP section of the MAID List window.

MEP ID - the remote MEP ID.

Actual MAC address - The MAC address of the remote MEP, which the local MEP recognizes.

Configured MAC address - Used when you decide to specify a selected MAC address for the remote MEP.

Status - The local MEP connection status.

Cross Check - Indicates if the current remote MEP was cross checked (pre-configured) or learned from incoming CCMs.

RDI - Remote Defect Indication.

Ping - Run ping (loopback) from the local MEP to a specific remote MEP ID by clicking the ping icon.

Automatic Linktrace – Displays 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.



6.1.6.2 Remote MEP ping window

Click the Ping to open the Remote MEP ping window.

The upper part of the window provides a short summary of the MAID and the remote MEP being pinged.

The lower part shows the ping success rate percentage (LBM packet transmission over the received LBR packets).

6.1.6.3 Adding a new remote MEP

From the Remote MEP section, click Add. The Add Remote MEP window is displayed.

Domain name - Maintenance domain name (appears automatically to prevent errors).

VLAN ID - MAID VLAN (appears automatically to prevent errors).

Remote MEP ID - the ID of the remote MEP.

Configured MAC Address - (Optional) You can configure a specific MAC address.



6.1.7 Linktrace

Mark a remote MEP checkbox (only one) and click Linktrace, to trace the link.

The upper part of the window provides a short summary of the MAID and the Remote MEP being traced.

In the Linktrace Hops table:

Reply TTL shows the hop number.

Mac Address shows the hop (MEP/MIP) MAC address.

Relay Action shows the hop LTM relay action.

You can click Ping to ping a particular hop.

Automatic Link-trace results appear 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.



6.2 MEP & MIP List

This page shows in which Ethernet port the user defined an MEP or MIP.

6.2.1.1 Ethernet Port columns

Ethernet Port - Shows the Ethernet port number.

MAC Address - Shows the Ethernet port MAC address.

Connector Type - Shows the Ethernet port connector type.

Function - Shows the Ethernet port function.

MEP or MIP Defined - When marked with a check indicates that you defined an MEP or MIP on this port.

6.2.1.2 Port MEPs columns

MEP ID - the local MEP ID.

Domain Name

Level

Association Name

VLAN ID

Direction - MEP direction (up or down).

Send CCM

CCM Interval

Priority

LDI

6.2.1.3 Port MIPs columns

Domain Name –

Level -



6.2.2 Add MEP to Port

Click the Add button to add new local MEPs on the port.

Ethernet port - The port you will be adding (appears automatically to prevent errors).

Local MEP ID - The ID of the local MEP (appears automatically to prevent errors).

Level - Select the MAID level.

VLAN ID - The MAID VLAN (appears automatically to prevent errors).

Direction - select the MEP direction (up or down).

Priority - Select the Pbit priority that the CCM message carries.

6.2.3 Add MIP to Port

Click the Add button to add MIPs from specific levels.

Ethernet port appears automatically to prevent errors.

For Level, select the MIP level.



6.3 Advanced

Under Service OAM in menu list on the left side of the window, click Advanced for additional MEP/MIP operations.

6.3.1 Manual Ping

Click the Manual Ping item to send a ping to the remote MEP/MIP.

MAC address is the target MEP/MIP MAC address.

Level is the MAID level.

VLAN ID is the ID of the VLAN.

Priority is the Pbit priority bit for the outgoing ETH-LBM packets.



6.3.2 Manual Linktrace

Click the Manual Linktrace item to send a linktrace command to the remote MEP/MIP.

MAC address is the target MEP/MIP MAC address.

Level is the MAID level.

VLAN ID is the ID of the VLAN.

Priority is the Pbit priority bit for the outgoing ETH-LTM packets.



7. Diagnostics & Maintenance

7.1 Radio Loopback

In this page, you can set the parameters for a radio loopback test.


Timeout - the amount of time you want the test to run.

IF loopback - select On if you want to perform an IF test.

RFU RF loopback - select On if you want to perform an RFU RF test.

To apply any change you made and start the test, click Apply.




7.2 PDH Line Loopback

In this page, you can set the parameters for a PDH loopback test.


Timeout - the amount of time you want the test to run.

# loopback - for each line interface, select On if you want to perform a loopback test, Off if you don't want to perform a test for that line, or Loopback towards radio to test the radio data flow.

To apply any change you made and start the test, click Apply.


7.3 SDH Loopback

In this page, you can set the parameters for an SDH loopback test.

Loopback timeout - the amount of time you want the test to run (in minutes).



Line Loopback - select Enabled if you want to perform a loopback test, or Disabled if you don't want to perform a test for that line.

7.4 Configuration Management

In this page, you can perform system configuration operations.

7.4.1 Overview

Uploading a configuration involves the following steps:

1 Create archive - This command creates a default archive in the target (IDU). The IDU configuration will first be copied to this location.

2 Upload Archive - Uploading the IDU configuration to the host PC.



7.4.2 Uploading or downloading an archive

Config download and upload status - Displays the current status of archive upload and download.

Click Upload Archive(s) to upload the system configuration archives to the server.

Click Download Archive(s) to download configuration archives from the server to the local system.

7.4.3 Configuration Backup Management

This section describes how to backup a configuration to an archive or to restore all or part of the system to a previously archived configuration.

There are four commands in this section that you can activate in this section. Click the command and a warning window is displayed to ensure that you want to continue with the selected action.

Backup All Archives - Creates an archive of the current configuration of all units on the shelf.

Backup Selected Unit - Creates an archive of the current configuration only for the selected slot.

Restore All Units - Restores the configuration settings of all units on the shelf to the archived configuration in the file.

Restore Selected Unit - Restores the configuration settings only for the selected slot to the archived configuration in the file.



7.4.4 Archiving unit information

You can use the Create Archive command in the Unit Information section to create an archive of the IDU unit information. This information is displayed in Configuration > General > Unit Parameters. The archive includes unit information for all the IDUs.

Click Create Archive. A warning window is displayed. Click OK to continue and create an archive file or Cancel to return to the Configuration Management window.

Unit info creation status - indicates whether or not the configuration file was created successfully.

Unit info upload status - indicates whether or not the configuration file was uploaded successfully from target to host.

7.4.5 Configuring the FTP parameters

From the bottom of the Configuration Management window, select FTP Parameters. The FTP Parameters window is displayed.

Host IP - IP of the host where the archive is to be stored.

Host path - 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.

User name - the user name for the FTP session.

User password - password for the FTP session. If you use the default user name (anonymous), use the host login for the password.

To apply changes you made, click Apply.




7.4.6 Resetting the configuration

You can reset all of the IDUs to the default factory configuration. In the Set to Default Configuration area:

Click Activate to set all the units to the default configuration.

A warning window is displayed. Click OK to reset the units or Cancel to return to the Configuration Management window.

7.4.7 Viewing the archive status

The Configuration Status window displays the most recent configuration management actions for each unit.

Click Unit Configuration Backup Information to display the Configuration Status window.

The Configuration Status window contains the following columns:

Slot Number –Number of the IDU.

Creation Time – Date and time that the archive was created.

Archive Size – Size of the archive file in Kb.

Last Operation – Most recent configuration operation that was performed.

Operation Time – Date and time of the most recent configuration operation that was performed.

Operation Status – The unit status for configuration operations.



7.5 Software Management

In this page, you can perform system software operations.

In the Software Management Status & Commands area:

Status download - last software download status.

Status install - last software installation status.

New Version:

Click Download to download newer packages from the remote server (without installation).

Click Upgrade to upgrade all installed or requested packages.

Click Rollback to undo the recent IDU application upgrade operation (one step back).

Packages are still upgraded after a rollback is applied to the IDU!

Rollback does not reverse a "downgrade" operation. To do so, use the "upgrade" command instead.

Old Version:

Click Download to download a package file for downgrade.

Click Downgrade to install all downloaded files (for downgrade). The downgraded version will be activated only after a cold reset.

From the bottom of the Configuration Management window, select FTP Parameters. The Remote Server FTP Parameters window is displayed.



Server IP address and path - remote software update server URL, where the software updates reside.

User name - login user name for the remote server.

User password - password for the remote server.

To apply changes you made, click Apply.


7.6 RFU Download

In this page, you can perform RFU software download.

To perform the download, click Software Download.

RFU software download status - shows the current state of RFU software download.

RFU software download progress - shows the download progress.



7.7 IDU-RFU Interface Monitoring

In this page, you can monitor the IDU-RFU traffic.

RFU receiver errors - monitors IDU-RFU interface errors detected by the RFU.

IDU receiver errors - monitors IDU-RFU interface errors detected by the IDU

7.8 Resets

In this page, you can perform a reset operation on some or all of the IDUs in the shelf.

Shelf cold reset - Resets all the IDUs

Extensions cold reset - Resets only the extension IDUs

Reset a specific slot - Resets a specific IDU.



7.9 File List

This page displays all application related files on the disk.



8. Security

8.1 Security Configuration

In this page, you can configure IP-10 security.

Upload public key status - The current status of the uploading process.

Upload Public Key- Click Upload Public Key to upload the public key of the element.

Download security status - The current status of the digital certificate download process.

Download certificate (button) - Click to download the Target certificate (WEB server digital certificate) or Target ca certificate (WEB CA digital certificate) to the element.

Download Certificate Parameters

Security file name - Name of the digital certificate file.

Security file type - The digital certificate type. The options include "Target certificate" for WEB server digital certificate, or "Target ca certificate" for WEB CA digital certificate.



Security file format - The format of the downloaded digital certificate. Options include “Pem” or “Der”.

WEB CA certificate - Select Enable if the downloaded file is “WEB CA digital certificate” or Disable if the file is "WEB server digital certificate".

Security Parameters

WEB Protocol - Determines whether the Web protocol is “HTTP” or “HTTPS” (Secured HTTP).

Telnet protocol admin - Allows you to enable or disable the telnet protocol.

Automatic logout period - The amount of minutes the system will wait for web activity before closing the management session.

FTP Parameters Link - Use this link to configure FTP parameters.



8.2 Users & Groups

This page displays the users and groups defined in the system.

Click Add User to create a new user to the element. The Add User window is displayed.

In the Add a user window, enter the following information:

User privilege - Can be one of the following:

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.

User name - The name you want the user to have.

Password - The password that will authenticate the user.

Expiration date – Click the calendar icon and select the expiration date for the user’s password.

Password Aging – Select the number of days for which a password is valid for this user.


To close the Add a user window, click Close.



9. Appendix A – FibeAir IP-10 Alarms Table

The following table lists IP-10 alarms and provides information about their possible causes and corrective actions.

Name ID Description Severity Origin Probable Cause Corrective Action

ext-in-alarm 101 %1 Indeterminate IDU User configured

Input problem.

Check source

description, and

correct accordingly.

Bridge-

configuration-

loss

201

Some bridge

configuration

may have been

lost during last

system reset.

Warning IDU

Power failure during

configuration

change.

Verify bridge

configuration.

eeprom-access-

failure 2201

Error in TDM

drawer type

detection

Major IDU

1 Inserted

drawer not

supported.

2 Hardware

error.

1 Make sure

drawer is

properly

inserted.

2 Power cycle the

system.

3 Replace drawer

excessive-ber 301

E1/DS1

excessive BER

on port #%1

Major IDU

1 Line is not

properly

connected.

2 External

equipment is

faulty.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Power cycle the

system.

loopback-

towards-line 302

E1/DS1

loopback

towards line on

port #%1

Major IDU

User configured

system to loopback

mode.

Cancel loopback

configuration.

loopback-

towards-radio 303

E1/DS1

loopback

towards radio

on port #%1

Major IDU

User configured

system to loopback

mode.

Cancel loopback

configuration.

loss-of-signal 304

E1/DS1 loss of

signal on port

#%1

Major IDU

1 Line is not

properly

connected.

2 External

equipment is

faulty.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Power cycle the

system.




Signal-degrade 305

E1/DS1 signal

degrade on port

#%1

Minor IDU

1 Line is not

properly

connected.

2 External

equipment is

faulty.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Power cycle the

system.

std-trap-link-

down 308

E1/DS1 link

down Indeterminate IDU

std-trap-link-up 307 E1/DS1 link up Indeterminate IDU

unexpected-

signal 306

E1/DS1

unexpected

signal on port

#%1

Warning IDU

1 Port is

disabled.

2 Line is

connected to a

disabled port.

1 Enable relevant

port.

2 Disconnect

cable from

relevant port.

Eth-clock-

source-signal-

failure

4001

Sync Ethernet

clock source

signal failure

Major IDU

1 Radio error

along the sync

path.

2 Invalid clock

signal at clock

source.

3 Configuration

error.

1 Make sure all

radio links are

errorless along

the path.

2 Make sure

source PDH

signal is being

received.

3 Re-check

synchronization

path

configuration.

Eth-loc-alarm 401

Ethernet loss of

carrier on port

#%1

Major IDU

1 FE cable

disconnected.

2 Defective FE

cable.

1 Check

connection of

FE cable.

2 Replace FE

cable.

Eth-tx-mute-

alarm 402

Ethernet Tx

mute override

on port #%1

Warning IDU

Radio

LOF/EXBER/Link ID

on local or remote

side (in pipe

application).

Check link.

gbe-loc-alarm 403

Gigabit Ethernet

loss of carrier

on port #%1

Major IDU

1 Cable is not

connected to

the port.

2 Cable is

defective.

1 Connect cable

to the port.

2 Replace cable.




gbe-sfp-alarm 404

Gigabit Ethernet

SFP not

inserted on port

#%1

Major IDU SFP is not inserted.

1 Check SFP

connector.

2 Replace fiber.

gbe-sfp-tx-

alarm 405

Gigabit Ethernet

SFP Tx fault on

port #%1

Major IDU SFP malfunction. Replace SFP.

gbe-tx-mute-

alarm 406

GBE Tx mute

override on port

#%1

Warning IDU

Radio

LOF/EXBER/Link ID

on local or remote

side.

Check link.

Std-trap-link-

down 408

Ethernet link

down Indeterminate IDU

Std-trap-link-up 407 Ethernet link up Indeterminate IDU

Fip-invalid-

protection-conf 5002

Floating IP is

enabled in a

system

configured to

1+0. An extra IP

address is being

unnecessarily

used.

Warning IDU

Protection admin is

"disabled" but

floating IP address

is configured (value

is different than

0.0.0.0).

Set floating IP

address to

0.0.0.0.

Or

Enable

protection.

floating-ip-filter-

lock-alarm 5001

Floating IP

locked to fixed

unit following

excessive

protection

switches

Major IDU

Constant protection

switches due to

permanent errors in

radio.

Perform protection

lockout.

File-load-error-

alarm 501

Firmware file

load error (%1) Critical IDU

1 Firmware file

is missing.

2 System error

on power up.

1 Move

Management to

port 2.

2 Download

firmware file.

3 Reset system.

File-not-found-

alarm 502

Firmware file

not found (%1) Critical IDU

Firmware file is

missing.

1 Download

firmware file.

2 Reset system.




Radio-

excessive-ber 601

Radio excessive

BER Major IDU

1 Fade in the

link.

2 Defective IF

cable.

3 Fault in RFU.

4 Fault in IDU.

1 Check link

performance.

2 Check IF cable,

and replace if

required.

3 Replace RFU.

4 Replace IDU.

radio-link-id-

mismatch 602

Link ID

mismatch Critical IDU

Link ID is not the

same at both sides

of link.

Configure same Link

ID for both sides of

link.

radio-lof 603 Radio loss of

frame Critical IDU

1 Fade in the

link.

2 Defective IF

cable.

3 Fault in RFU.

4 Fault in IDU.

5 Different radio

scripts at both

ends of the

link

1 Check link

performance.

2 Check IF cable,

and replace if

required.

3 Replace RFU.

4 Replace IDU.

5 Make sure

same script is

loaded at both

ends of the link

radio-signal-

degrade 604

Radio signal

degrade Minor IDU

1 Fade in the

link.

2 Defective IF

cable.

3 Fault in RFU.

4 Fault in IDU.

1 Check link

performance.

2 Check IF cable,

and replace if

required.

3 Replace RFU.

4 Replace IDU.

std-trap-link-

down 606 Radio link down Indeterminate IDU

std-trap-link-up 605 Radio link up Indeterminate IDU

alarms-file 701 Alarm file not

found. Major IDU

The alarm file was

deleted or is

corrupted.

Download alarm file.

cli-script-

download-failed 721

CLI

configuration

script download

failed.

Warning IDU Download failure. Retry download

procedure.




cli-script-

download-

succeeded

722

CLI

configuration

script

downloaded

successfully.

Warning IDU

cli-script-

executed 723

CLI

configuration

script activated.

Warning IDU

cli-script-

execution-failed 725

CLI

configuration

script failed.

Warning IDU

CLI configuration

script execution

failure.

1 Correct CLI

configuration

script.

2 Download

corrected script.

3 Execute script.

cli-script-

execution-

succeeded

724

CLI

configuration

script executed

successfully.

Warning IDU

cold-reset-event 702 Cold reset

event. Warning IDU

Cold reset

command was

issued.

Config-creation-

failed 703

Configuration

backup failed. Warning IDU

Retry configuration

creation.

Config-creation-

succeeded 704

Configuration

backup

succeeded.

Warning IDU

config-

download-failed 705

Configuration

file download

failed.

Warning IDU Download failure. Retry download

procedure

config-

download-

succeeded

706

Configuration

file download

succeeded.

Warning IDU

config-install-

failed 707

Configuration

restoring failed. Warning IDU

1 Corrupt file.

2 Internal SW

error.

1 Re-install file.

2 Download and

install file.

config-install-

succeeded 708

Configuration

restoring

succeeded.

Warning IDU

config-upload-

failed 709

Configuration

file upload

failed.

Warning IDU Retry upload

procedure.




config-upload-

succeeded 710

Configuration

file upload

succeeded.

Warning IDU

entity-init-fail-

alarm 711

SW error: entity

initialization

failure.

Major IDU SW error during

system initialization. Reset system.

entity-init-fail-

event 712

SW error: entity

%1 initialization

failure.

Major IDU SW error during

system initialization. Reset system.

extreme-

temperature 713

IDU extreme

temperature

conditions.

Warning IDU

The external

cooling/heating

system is not

operating.

Turn on external

cooling/heating

systems.

fan-failure 714 Fan failure. Minor IDU Defective fan unit. Replace fan unit.

general-

hardware-failure 715

General HW

failure %1. Critical IDU Defective HW.

1 Reset system.

2 Replace IDU.

kernel-backup 716 Backup kernel

is running. Minor IDU

The kernel

(/boot/uImage) is

corrupted or

missing.

Reinstall the SW.

low-input-

voltage 717

Low input

voltage. Warning IDU

Low input to the

system.

Check power supply

voltage.

lvds-backplane-

error-extn 729

Errors in TDM

backplane

channel in

connection with

main.

Major IDU

1 Extension or

main unit

equipment

failure.

2 Backplane

failure.

1 Reinsert unit.

2 Power-cycle

unit.

3 Replace unit.

4 Check

backplane.

lvds-backplane-

error-main 728

Errors in TDM

backplane

channel for

slot # %1.

Major IDU

1 Extension or

main unit

equipment

failure.

2 Backplane

failure.

1 Reinsert unit.

2 Power-cycle

unit.

3 Replace unit.

4 Check

backplane.

lvds-db-error 730

Errors in TDM

channel in

connection with

T-card.

Major IDU

1 IDU HW

failure.

2 T-card HW

failure.

1 Reinsert unit.

2 Power-cycle

unit.

3 Replace T-card.

4 Replace IDU.




Param-set-fail-

alarm 718

SW error:

parameter set

failed.

Warning IDU SW error.

1 Look in Alarm

Log for

matching Event.

2 In the Event:

Look for exact

parameter that

has failed.

3 Set the

parameter again

via the CLI. The

alarm is cleared

after reset.

Param-set-fail-

event 719

SW error:

parameter %1

set failed.

Major IDU SW error. Reset system.

Public-key-

upload-failed 726

Public key

upload failed. Warning IDU

Public-key-

upload-

succeeded

727

Public key

upload

succeeded.

Warning IDU

warm-reset-

event 720

Warm reset

event. Warning IDU

SW reset in the

system.

corrupt-

differential-

delay-values-

found-event

2502

Corrupt

differential delay

values found.

Major IDU

Inventory file was

found to be corrupt

upon system power

up.

1 Download

inventory file.

2 Reset system.

corrupted-file-

alarm 801

Inventory file

(%1) is

corrupted.

Critical IDU

1 Inventory file

is missing.

2 Inventory file

was found to

be corrupt

upon system

power up.

1 Download

inventory file.

2 Reset system.

file-not-found-

alarm 802

Inventory file

(%1) was not

found.

Critical IDU Inventory file is

missing.

1 Download

inventory file.

2 Reset system.




Lag-

degradation-

alarm

2701

Degraded

functionality in

LAG #%1.

Major IDU

1 Configuration

error.

2 Defective

Ethernet

cables or

cables

disconnected.

3 Fault in

external

equipment

1 Check LAG

physical

configuration in

both sides of

link.

2 Check cables

and replace if

required.

3 Replace IDU.

lag-loss-alarm 2702 LAG #%1 status

down. Critical IDU

Configuration error.

Defective Ethernet

cables or cables

disconnected.

Fault in external

equipment

Check LAG physical

configuration in both

sides of link.

Check cables and

replace if required.

Replace IDU.

demo-license-

about-to-expire-

alarm

908

Demo license is

about to expire

within 48 hours.

Major IDU Demo license

activated by user.

1 Terminate demo

license.

2 Activate

operational

license.

demo-license-

alarm 901 Demo license. Warning IDU

Demo license

activated by user.

1 Terminate demo

license.

2 Activate

operational

license.

license-demo-

expired 902

Demo license

expired. Warning IDU

Demo trial period

has ended. Obtain a valid license.

license-demo-

start-by-user 903

Demo license

started by user. Warning IDU

license-demo-

stop-by-user 904

Demo license

stopped by

user.

Warning IDU




license-load-fail 905 License load

failure %1. Warning IDU

1 Invalid serial

number -

license code

does not

match unit's

serial number.

2 License

version

mismatch.

1 Compare unit's

serial number

with license

serial number (3

left characters

of license code

with 3 right

characters of

Unit's serial).

2 Check code

license

generation

sequence.

3 Contact Tech

support.

license-load-

succesfull 906

License loading

succeeded. Warning IDU

license-

violation-alarm 907

License

violation %1. Warning IDU

Unit does not match

license feature set.

1 Check that the

code was

entered

correctly.

2 Call tech

support for new

license

generation.

license-

violation-

detected

909

License

violation

detected: %1.

Warning IDU

User configuration

doesn't match

licensed feature set

1 Fix configuration

to correspond to

loaded licenses.

2 Load proper

license.

bridge-xml-file-

alarm 1015 Warning IDU

cable-

disconnected-

alarm

1001

Mate IDU cable

is not

connected.

Major IDU

1 Cable is not

connected

between

protection

ports.

2 Cable is

connected to

wrong port.

3 Cable is

damaged.

1 Connect

Ethernet cable

to protection

port of both

IDUs.

2 Replace cable.




configuration-

mismatch-alarm 1002

Mate IDU

configuration

mismatch.

Major IDU

The configurations

of the IDUs are not

identical.

Apply "Copy to Mate"

from the desired IDU.

copy-to-mate-

completed-

event

1003 Copy to mate

completed. Warning IDU

copy-to-mate-

failure-event 1004

Copy to mate

failed. Warning IDU

Initiate another

Copy to Mate

command.

copy-to-mate-

started-event 1005

Copy to mate

started. Warning IDU

exc-ber-

change-remote-

tx-sent-event

1006

Request for

change remote

transmit on

radio BER.

Major IDU

Active Tx at local

side is not

transmitting.

1 Check the Tx

level of Active

unit.

2 Check if Active

unit was set to

Mute.

3 Check Active

unit's RFU.

force-switch-

alarm 1007

Protection force

switch. Major IDU

User command -

Force

Protection

Switch.

Clear Force

Switch

Command.

ipi-xml-file-

alarm 1008

Protection SW

activity fault. Warning IDU

SW fault in

synchronization of

databases.

Reset Standby unit.

lockout-alarm 1009 Protection

lockout. Major IDU

User issued

Protection Lockout

Clear Lockout

command

lof-change-

remote-tx-sent-

event

1010

Request for

change remote

transmit on

radio loss of

frame.

Warning IDU

1 Active Tx at

local side is

not

transmitting.

2 Fade in the

link path.

1 Check the Tx

level of Active

unit.

2 Check if Active

unit was set to

Mute.

3 Check Active

unit's RFU.

4 Check PM for

fade in link path.

manual-switch-

req-event 1011

Protection

manual switch

request.

Warning IDU User request to

perform local switch




mate-comm-

failure-alarm 1012

Mate IDU

communication

error.

Major IDU

1 IDU IP

addresses are

identical

2 IDU IP

subnets are

not identical.

3 In stand-alone

configuration:

protection

cable is not

properly

connected.

4 In stand-alone

configuration:

protection

cable is

damaged.

1 Check IP

address and

subnet definition

in both units.

2 In stand-alone

configuration:

check

Protection cable

connectivity.

3 In stand-alone

configuration:

replace

Protection

cable.

protection-

mode-changed-

event

1013

Protection mode

changed to %1

%2.

Warning IDU

sd-change-

remote-tx-sent-

event

1014

Request for

change remote

transmit on

radio signal

degrade.

Warning IDU

1 Link Fade.

2 Defective IF

cable.

3 RFU fault.

4 IDU fault.

1 Check link

performance.

2 Check IF cable.

3 Check RFU.

4 Check IDU.

download-failed 1101 Software

download failed. Warning IDU

1 There are no

valid packages

for download

at remote

server.

2

Communi

cation with

remote server

is down.

3 Remote server

access

credentials are

not valid.

4 Remote server

URL is not

valid.

download-

succeeded 1102

Software

download

succeeded.

Warning IDU




install-failed 1103

Software

package

installation

failed.

Warning IDU

1 There are no

valid packages

for installation

at local update

directory.

2 One or more

package has

unresolved

dependencies,

i.e. requires

another

package(s) to

be installed

first.

install-

succeeded 1104

Software

package

installation

succeeded.

Warning IDU

firmware-file-

missing-alarm 1201

Modem

firmware file not

found.

Critical IDU Modem file is

missing.

1 Download

Modem file.

2 Reset system.

firmware-load-

error-alarm 1202

Modem was not

loaded

successfully.

Critical IDU 1 File is corrupt.

2 System failure.

1 Download file.

2 Reset system.

modem-wd-

reset-event 1203

Modem WD

reset. Warning IDU

fpga-file-

currupt-alarm 1301

Radio script

(LUT) is corrupt. Critical IDU Faulty file.

Download radio script

LUT.

fpga-file-not-

found-alarm 1302

Radio script

(LUT) not found Critical IDU

File was not

downloaded to

system.

Download radio

script.

incompatible-

script-alarm 1303

Incompatible

script: %1 %2. Critical IDU

Incompatibility

between RFU and

loaded radio script.

1 Change RFU.

2 Change Radio

script.

modem-script-

file-corrupt-

alarm

1304 Radio script is

corrupt. Critical IDU File is corrupt. Download file.

modem-script-

file-not-found-

alarm

1305 Radio script not

found. Critical IDU File not found. Download file.

mrmc-file-

corrupt-alarm 1306

MRMC file is





mrmc-file-not-

found-alarm 1307

MRMC file not


radio-script-not-

supported-by-

hw-alarm

1310

radio script not

supported by

hardware.

Critical IDU

Configuration from

another system

loaded into F-series

hardware.

1 Change radio

script.

2 Make sure right

hardware is

installed.

Rfu-file-corrupt-

alarm 1308

RFU file is


Rfu-file-not-

found-alarm 1309

RFU file not


incompatible-

rfu-tx-calibration 1401

Incompatible

RFU TX

calibration.

Major RFU

RFU calibration

tables require IDC

SW upgrade.

Upgrade IDU SW.

system-reset-

required 2901

System reset

required to

apply

configuration

changes.

Warning IDU

1 Radio was

enabled and

user disabled

it.

2 Radio was

disabled and

user enabled it

1 Perform system

reboot.

2 Change relevant

configuration to

current value

Under-voltage-

condition-ps-1 2902

Under-voltage

conditions in

power

supply #1.

Major IDU

1 Power cable

disconnected.

2 Power supply

source failure.

3 Hardware

failure.

1 Connect power

supply cable.

2 Check power

supply source.

3 Replace IDU.

Under-voltage-

condition-ps-2 2903

Under-voltage

conditions in

power

supply #2.

Major IDU

1 Power cable

disconnected.

2 Power supply

source failure.

3 Hardware

failure.

1 Connect power

supply cable.

2 Check power

supply source.

3 Replace IDU.

radio-interface-

changed-by-

user-event

2801

Radio interface

is currently %1

by user

configuration.

Warning IDU User configuration

Enable the radio

interface if use of the

radio is desired

remote-

communication-

failure

1501

Remote

communication

failure.

Major IDU Fade in the link. Check link

performance.

if-loopback-

alarm 1601 IF loopback. Warning IDU

User enabled IF

loopback. Disable IF loopback.




lock-detect-

alarm 1602

IF lock

detection. Critical IDU

1 Extreme

temperature

condition.

2 HW failure.

1 Check

installation.

2 Reset IDU.

cable-open 1701 Cable open. Major IDU

Cable is not

connected to IDU or

RFU.

1 Check IF cable

and connectors.

2 Verify that N-

Type connector

inner pin is not

spliced.

3 Replace IDU.

4 Replace RFU.

cable-short 1702 Cable short. Major IDU Physical short at the

IF cable.

1 Check IF cable

and connectors.

2 Verify that N-

Type connector

inner pin is not

spliced.

3 Replace IDU.

4 Replace RFU.

communication-

failure 1703

RFU

communication

failure.

Warning IDU

1 Defective IF

cable.

2 IF cable not

connected

properly.

3 Defective IDU.

4 Defective

RFU.

5 RFU software

download in

progress.

6 Check IF cable

and connectors.

7 Verify that N-

Type connector

inner pin is not

spliced.

8 Replace IDU.

9 Replace RFU.

For High Power RF

Unit:

1 Check BMA

connector on

OCB.

2 Check BMA

connector on

RFU.

delay-

calibration-

failure-1

1704

RFU delay

calibration

failure 1.

Warning RFU Defective RFU.

1 Reset the

IDU/RFU.

2 Replace RFU.

delay-

calibration-

failure-2

1705

RFU delay

calibration

failure 2.

Warning RFU

Calibration cannot

be completed due

to notch detection.

Enter delay

calibration value

manually.




extreme-temp-

cond 1706

RFU extreme

temperature. Warning RFU

1 Installation

conditions.

2 Defective

RFU.

1 Check

installation

conditions.

2 Verify operation

as per product's

specs.

3 Replace RFU.

fan-failure 1707 RFU fan failure. Warning RFU

1 Defective /

non-existent

fan drawer.

2 Defective

RFU-to-fan

drawer

connection.

3 Defective

RFU.

1 Check RFU

connection to

BP.

2 Check that fans

are connected

to PS.

3 Replace RFU

BP cable.

4 Replace specific

fan or fan

drawer.

5 Replace RFU.

freq-set-

automatically 1708

Frequency was

set

automatically.

Warning RFU Defective RFU.

1 Check if

problem repeats

and if

errors/alarms

reported.

2 Replace ODU.

hardware-

failure-1 1709

RFU hardware

failure 1. Critical RFU Defective RFU. Replace RFU.

hardware-

failure-2 1710

RFU hardware

failure 2. Critical RFU Defective RFU. Replace RFU.

low-if-signal-to-

rfu 1711

Low IF signal to

RFU. Major RFU

1 IF cable

connection.

2 Defective

RFU.

3 Defective IDU.

1 Check IF cable

connectors.

2 Verify that N-

Type connector

inner pin is not

spliced.

3 Replace IDU.

4 Replace RFU.




No-signal-from-

rfu 1712

Low signal from

RFU. Warning IDU

No RX (140 MHz)

signal from RFU.

1 Check IF cable

and connectors.

2 Verify that N-

Type connector

inner pin is not

spliced.

3 Replace IDU.

4 Replace RFU.

For High Power RF

Unit:

Check BMA

connector center

pin is not spliced

both on RFU and

on OCB.

Pa-extreme-

temp-cond 1713

RFU PA

extreme

temperature.

Warning RFU

1 Installation

conditions.

2 Defective

RFU.

1 Check

installation

conditions.

2 Replace RFU

power-

decreased-due-

to-pa-

temperature

1737

Power

decreased due

to high

temperature.

Major ODU

1 Incorrect

installation.

2 Hardware

failure.

1 Check

installation

conditions.

2 Verify operation

as per product's

specs.

3 Replace RFU.

Power-failure-

12v 1714

RFU power

failure (12v). Major RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

Power-failure-

1point5 1715

RFU power

failure (1.5v). Major RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.




Power-failure-

24v 1716

RFU power

failure (24v). Major RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

Power-failure-

6v 1717

RFU power

failure (6v pro). Critical RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

Power-failure-

6v-sw 1718

RFU power

failure (6v SW). Major RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

Power-failure-

minus-5v 1719

RFU power

failure (-5v). Major RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

Power-failure-

vd 1720

RFU power

failure (Vd). Critical RFU

1 Defective IF

cable/connect

or.

2 Defective

RFU.

3 Defective IDU.

1 Replace IF

cable/connector.

2 Replace RFU.

3 Replace IDU.

reset-occurred 1721 RFU reset. Warning RFU

rfu-loopback-

active 1722 RFU loopback. Major RFU User action.

Disable RFU

loopback.

rfu-mode-

changed-to-

combined

1723

RFU mode

changed to

Combined.

Warning RFU

rfu-mode-

changed-to-

diversity

1724

RFU mode

changed to

Diversity.

Warning RFU

rfu-mode-

changed-to-

main

1725

RFU mode

changed to

Main.

Warning RFU




rfu-power-

supply-failure 1726

RFU power

supply failure. Major RFU

At least one of the

PSU voltages is too

low.

Replace RFU.

rx-level-out-of-

range 1727

Rx level out of

range. Warning RFU

RSL is very low

(typically below -80

dBm), link is down.

For RFU-C:

RSL is too low

(typically below -83

dBm) or RSL is too

high (typically

above -26 dBm).

1 Check antenna

alignment & link

planning.

2 Check link

settings (TX

power, TX freq).

3 Check antenna

connections.

4 Replace

local/remote

RFU.

rx-level-path1-

out-of-range 1728

RFU Rx level

path 1 out of

range.

Warning RFU

1 Improper

installation.

2 Fading event.

3 Defective

RFU.

1 Check that the

fault is not due

to rain/multi-

path fading or

lack of LOS.

2 Check link

settings (TX

power, TX freq).

3 Check antenna

alignment.

4 Check antenna

connections.

5 Replace

local/remote

RFU.

rx-level-path2-

out-of-range 1729

RFU Rx level

path 2 out of

range.

Warning RFU

1 Improper

installation.

2 Fading event.

3 Defective

RFU.

1 Check that the

fault is not due

to rain/multi

path fading or

lack of LOS.

2 Check link

settings (TX

power, TX freq).

3 Check antenna

alignment.

4 Check antenna

connections.

5 Replace

local/remote

RFU.




synthesizer-1-

unlocked 1730

Synthesizer 1

unlocked. Major RFU

1 Defective

RFU.

2 Defective

XPIC cable

connection.

1 Replace XPIC

cable.

2 Replace RFU.

synthesizer-2-

unlocked 1731

Synthesizer 2

unlocked. Major RFU

1 Defective

RFU.

2 Defective

XPIC cable

connection.

1 Replace XPIC

cable.

2 Replace RFU.

synthesizer-3-

unlocked 1732

Synthesizer 3

unlocked. Major RFU

1 Defective

RFU.

2 Defective

XPIC cable

connection.

1 Replace XPIC

cable.

2 Replace RFU.

synthesizer-

unlocked 1733

Synthesizer

unlocked. Major RFU

One of the RFU

synthesizers is

unlocked.

1 Replace RFU.

2 In XPIC mode,

replace mate

RFU as well.

tx-level-out-of-

range 1734

Tx level out of

range. Minor RFU

Defective RFU (the

RFU cannot

transmit the

requested TX

power).

1 Replace RFU.

2 Intermediate

solution -

reduce TX

power.

tx-mute 1735 Tx mute Warning RFU RFU Transmitter

muted by user.

Unmute the RFU

transmitter.

unknown-rfu-

type 1736

IDU SW does

not support this

type of RFU.

Major RFU IDC SW does not

support the RFU. Upgrade IDC SW.

upload-

firmware-

canceled

1801 RFU FW upload

cancelled. Warning RFU User action.

upload-

firmware-error 1802

RFU FW upload

error. Major RFU Retry upload.

upload-

firmware-failed 1803

RFU FW upload

failed. Major RFU Retry upload.

upload-

firmware-

succeeded

1804 RFU FW upload

succeeded. Warning RFU

upload-

software-

canceled

1901 RFU SW upload

cancelled. Warning RFU Retry upload.




upload-

software-error 1902

RFU SW upload

error. Warning RFU Retry upload.

upload-

software-failed 1903

RFU SW upload

failed. Warning RFU Retry upload.

upload-

software-started 1904

RFU SW upload

started. Warning RFU

upload-

software-

succeeded-

event

1905 RFU SW upload

succeeded. Warning RFU

cfm-failure 2001 Ethernet

services failure. Warning IDU

1 Local MEP

error

indication.

2 Remote MEP

error

indication.

3 Remote MEP

loss of

connectivity.

1 Check MAID

definitions.

2 Check remote

MEP definitions.

3 Check local

MEP definitions.

4 Run "CFM

traceroute" to

the remote

MEP, then

perform "CFM

ping" to each

MP

(Maintenance

Point) in order

to find the

broken point.

bp-lof-alarm 2301

TDM backplane

LOF for slot

#%1.

Critical IDU

1 Extension or

main unit

equipment

failure.

2 Backplane

failure.

1 Reinsert unit.

2 Power-cycle

unit.

3 Check

backplane.

communication-

lost-with-idu 2302

Communication

s lost with IDU

#%1.

Critical IDU

1 Extension or

main unit

equipment

failure.

2 Backplane

failure.

1 Re-insert unit.

2 Power-cycle

unit.

3 Check

backplane.

extraction-

detected 2303

IDU #%1

extraction

detected.

Warning IDU




idu-presence-

not-detected 2304

IDU #%1

presence not

detected.

Minor IDU

IDU with TDM trails

mapped to it was

extracted from

shelf.

1 Insert IDU in

shelf.

2 Delete relevant

TDM trails

insertion-

detected 2305

IDU #%1

insertion

detected.

Warning IDU

mate-version-

mismatch 2306

SW running

version

mismatch with

mate.

Major IDU

1 SW update

performed in

one unit only.

2 Units with

different SW

version

connected as

protection

mate

Perform SW update

to mate unit

protection-

admin-

mismatch

2307

Protection mode

mismatch for

IDU #%1, %2.

Minor IDU

1 Equipment

error in

extension IDU.

2 Backplane

communicatio

ns error.

1 Re-configure

XC settings.

2 Reset extension

unit.

3 Replace

extension unit

protection-

mode-mismatch 2308

Protection

activity error for

IDUs #%1, %2.

Major IDU

1 Backplane

communicatio

ns failure.

2 Equipment

failure in

extension

units.

1 Replace units,

one by one.

2 Check

backplane.

unit-version-

mismatch 2309

SW running

version

mismatch with

extension unit in

slot %1.

Major IDU

1 SW update

performed in

main unit only.

2 Units with

different SW

version

connected as

extensions.

Perform SW update

to relevant extension

unit.

heartbeat 2101 Heartbeat Indeterminate IDU

a2n-

initialization-

failure

2603

Access to

Network

initialization

failure.

Critical IDU

1 Equipment is

faulty.

2 SW/HW

versions

mismatch.

1 Power cycle the

system.

2 Check SW

versions




j0-mismatch 2612

J0 Trace

Identifier

Mismatch.

Minor IDU

1 Error in

remote optical

equipment

configuration.

2 Error in J0

expected

string

configuration.

3 Error in J0

length

configuration.

Check that remote

equipment sent J0

string and length

equals expected J0

configuration.

loopback-at-

stm1 2610

Loopback at

STM-1 line

interface.

Major IDU

User configured

loopback at STM-

1/OC-3 interface.

Cancel loopback

configuration.

mute-override 2608 STM-1/OC-3

mute override. Warning IDU

User configured

STM-1/OC-3

interface as silent.

Configure STM-1/OC-

3 interface to

transmit.

stm1-excessive-

ber 2605

STM-1/OC-3

excessive BER. Major IDU

1 Line is not

properly

connected.

2 Cable is faulty.

3 External

equipment is

faulty.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Power cycle the

system.

stm1-lof 2602 LOF in STM-

1/OC-3. Critical IDU

1 Line is not

properly

connected.

2 Cable is faulty.

3 Equipment is

faulty.

4 STM-1/OC-3

SFP not

attached.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Attach SFP.

5 Power cycle the

system.

stm1-los 2601 LOS in STM-

1/OC-3. Critical IDU

1 Line is not

properly

connected.

2 Cable is faulty.

3 Equipment is

faulty.

4 STM-1/OC-3

SFP not

attached.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Attach SFP

5 Power cycle the

system.




stm1-pll-

unlocked 2611

STM-1/OC-3

PLL unlocked. Critical IDU

Hardware failure in

STM-1/OC-3 card.

1 Power cycle the

system.

2 Replace

STM-1/OC-3

card

stm1-sfp-not-

detected 2604

STM-1/OC-3

SFP not

detected.

Major IDU

1 SFP not

inserted

properly.

2 Incompatible

SFP type.

3 Damaged SFP

1 Reconnect SFP.

2 Change SFP

stm1-sfp-tx-fault 2607 STM-1/OC-3

SFP Tx fault. Major IDU

1 SFP not

inserted

properly.

2 Damaged

SFP.

1 Reconnect SFP.

2 Change SFP.

stm1-signal-

degrade 2606

STM-1/OC-3

signal degrade. Minor IDU

1 Line is not

properly

connected.

2 Cable is faulty.

3 External

equipment is

faulty.

1 Reconnect line.

2 Check line

cables.

3 Check external

equipment.

4 Power cycle the

system.

stm1-sync-

clock-signal-

failure

2613

STM-1 clock

source signal

failure.

Major IDU

1 Clock source

configured

from wrong

VC.

2 Radio LOF or

equipment

failure along

the path of the

synchronizatio

n trail.

3 LOS or AIS at

the

synchronizatio

n source

interface in the

far end of the

trail.

1 Make sure the

configured VC is

the end-point of

the

synchronization

trail.

2 Check status of

synchronization

trail.

3 Check status of

clock source

interface.




extension-bp-lof 2402

TDM backplane

LOF in

connection with

main.

Critical IDU

1 Extension or

main unit

equipment

failure.

2 Backplane

failure.

1 Re-insert unit.

2 Power-cycle

unit.

3 Check

backplane

failure-in-one-

or-more-tdm-

trails

2403

Failure in one or

more TDM

trails.

Warning IDU

1 Network TDM

trail

configuration

error.

2 Signal failure

in TDM trail -

this may be

due to

equipment

failure or AIS

at the line

input.

3 Excessive

BER in TDM

trail.

4 Signal

degrade in

TDM trail.

Check TDM trails

status.

illegal-trail-

configuration 2415

Conflicting trails

are configured

in protected

IDUs %1 and

%2.

Warning IDU

Protection was

enabled in pair of

IDUs between

which trails were

previously

configured.

1 Erase relevant

trails.

2 Disable

protection in

pair.

invalid-trail-

status-change 2406

Invalid trail

status change

%1 in trail %2.

Major IDU

1 Trail end-point

failure

detected for

one or more

trails.

2 Trail end-point

failure cleared

for one or

more trails.

1 Perform reset in

end-point IDU if

exists.

2 Replace end-

point IDU.




trail-excessive-

BER-change 2407

Trail excessive

BER status

change %1 in

trail %2.

Major IDU

1 Trail excessive

BER detected

for one or

more trails.

2 Trail excessive

BER cleared

for one or

more trails.

Check links and

equipment alarms

along the TDM trail.

trail-id-

mismatch 2408

Trail ID

mismatch in at

least one trail.

Warning IDU

1 Trail ID

spelling

difference

between trail

ends.

2 Network TDM

trail

configuration

error.

3 Errors in

incoming

signal.

1 Check trail ID at

both ends of the

trail.

2 Check network

trail

configuration.

3 Check trail

performance

(BER) along the

trail path and fix

errored links if

needed.

trail-id-

mismatch-

change

2409

Trail ID

mismatch status

change %1 in

trail %2.

Warning IDU

1 Trail ID

mismatch

detected for

one or more

trails.

2 Trail ID

mismatch

cleared for

one or more

trails.

1 Check trail ID at

both ends of the

trail.

2 Check network

trail

configuration.

trail-protected-

forced-active 2410

Trail ID: %1,

path: %2 forced

active.

Warning IDU User command

force active.

Set force active to

"none" for this trail.

trail-protected-

switch 2411

Trail protection

switch

performed in

trail %1 due to

%2.

Warning IDU

1 Signal failure

along the

active trail's

path.

2 User issued

force active

command to

stand-by path.




trail-signal-

degrade-

change

2412

Trail signal

degrade status

change %1 in

trail %2.

Minor IDU

1 Trail signal

degrade

detected for

one or more

trails.

2 Trail signal

degrade

cleared for

one or more

trails.

Check links and

equipment alarms


trail-signal-

failure 0 Major

trail-signal-

failure-change 2414

Trail signal

failure status

change %1 in

trail %2.

Warning IDU

(1) Fade in a link

along the trail.

(2) Equipment

failure in a network

element along the

trail.

(3) Trail not

properly provisioned

along the path.

Check links,

equipment alarms

and trail configuration


trails-mapped-

to-inexistent-

interfaces

2413

Trails mapped

to inexistent

interfaces in

IDU #%1.

Warning IDU

1 One or more

components

were extracted

from the

system since

trails were

defined.

2 Radio scripts

have been

replaced by

narrower

scripts since

trails were

defined.

1 Replace missing

components

(IDUs, T-cards).

2 Make sure radio

scripts support

required number

of E1/DS1 trails

through radio.

3 Delete relevant

trails.

unsuccessful-

consecutive-

login-attempts

2501

Unsuccessful

consecutive

login attempts

for user %1.

Warning IDU User mistake or

security event.

Reset the user

account (only "secure

officer" or above user

types allowed).




insufficient-

config-for-xpic 3001

Insufficient

system

configurations

for XPIC

support.

Major IDU

1 Modem script

does not

support XPIC.

2 ODU does not

support XPIC.

3 The frequency

of both radios

is not equal.

4 Different type

of ODU.

5 Protection is

enabled.

6 One of the

IDUs HW does

not support

XPIC.

7 Different

scripts are

loaded in the

IDUs.

Check which

condition is lacking

and resolve it.

insufficient-

config-for-xpic-

event

3003

Condition for

XPIC not met:

0x%1

Warning IDU

xsm-event 3002 %1 Warning IDU

A change in the

XPIC recovery

mechanism took

place.

IP10G CeraWeb User Guide Version 6 7 March2011

Documents