IP-20 MIB Reference 11.9.5 Rev AD

MIB Reference
IP-20 Series
February 2022 | Rev AD

Release: 11.9.5
© Copyright 2022 by Ceragon Networks Ltd. All rights reserved.
MIB Reference for IP-20 Series, CeraOS 11.9.5
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.
Trademarks
Ceragon Networks® and CeraView® are trademarks of Ceragon Networks Ltd., registered in the United States
and other countries.
Ceragon® is a trademark of Ceragon Networks Ltd., registered in various countries.
CeraMap™, PolyView™, EncryptAir™, ConfigAir™, CeraMon™, EtherAir™, CeraBuild™, CeraWeb™, and
QuickAir™, 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 ("Open Source License"). Inasmuch that such software is being used, it is released under the Open
Source License, accordingly. The complete list of the software being used in this product including their
respective license and the aforementioned public available changes is accessible at:
Network element site: ftp://ne-open-source.license-system.com
NMS site: ftp://nms-open-source.license-system.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.
Intended Use/Limitation
Fixed point-to-point radio links for private networks.
Authorized to Use
Only entities with individual authorization from the National Regulator to operate the mentioned radio
equipment.
The equipment can be used in the following EU countries:
Austria (AT) - Belgium (BE) - Bulgaria (BG) - Switzerland/Liechtenstein (CH) - Cyprus (CY) - Czech Republic (CZ)
- Germany (DE) – Denmark (DK) - Estonia (EE) - Finland (FI) - France (FR) -Greece (GR) - Hungary (HU) -
Ireland (IE) – Iceland (IS) – Italy (IT) – Lithuania (LT) - Luxembourg (LU) – Latvia (LV) - Malta (MT) -
Netherlands (NL) - Norway (NO) - Portugal (PT) - Romania (RO) - Sweden (SE) - Slovenia (SI) - Slovak Republic
(SK) – United Kingdom (UK) – Spain (SP) – Poland (PL)
Page 2 of 103
Ceragon Proprietary and Confidential

Table of Contents
1. Private MIB reference ............................................................................................... 8
2. Standard MIB support ............................................................................................. 10
2.1 RFC-1213 (MIB II) ....................................................................................................................... 10
2.1.1 System parameters .................................................................................................................... 10
2.1.2 Interfaces ................................................................................................................................... 11
2.1.3 ifTable ........................................................................................................................................ 11
2.1.4 Other parameters and tables ..................................................................................................... 18
2.2 Multiple Spanning Tree Protocol (MSTP) ................................................................................... 18
2.3 Trap ID ........................................................................................................................................ 18
2.4 Trap Var-Bind ............................................................................................................................. 19
3. Common tasks ........................................................................................................ 21

3.1 Software management .............................................................................................................. 21
3.1.1 Downloading a software version ............................................................................................... 21
3.1.2 Upgrading the RFU software version ......................................................................................... 24
3.2 Configuration file management ................................................................................................. 26
3.2.1 System configuration FTP settings ............................................................................................. 26
3.2.2 Creating and uploading backup configuration archives ............................................................. 27
3.3 Enabling and configuring traps .................................................................................................. 28
3.3.1 Enabling trap administration ..................................................................................................... 28
3.3.2 Managing a trap ......................................................................................................................... 29
3.4 Viewing current alarms .............................................................................................................. 30
3.4.1 Alarm date and time .................................................................................................................. 30
3.4.2 Alarm severity ............................................................................................................................ 30
3.4.3 Alarm description ....................................................................................................................... 30
3.4.4 Probable cause ........................................................................................................................... 31
3.4.5 Corrective actions ...................................................................................................................... 31
3.5 Viewing event log ....................................................................................................................... 32
3.5.1 Event date and time ................................................................................................................... 32
3.5.2 Event severity............................................................................................................................. 32
3.5.3 Event description ....................................................................................................................... 32
3.5.4 Event state ................................................................................................................................. 33
3.6 Performance monitoring and counters ..................................................................................... 33
3.6.1 Clearing all performance counter data ...................................................................................... 33
3.7 Managing radio configuration ................................................................................................... 33
3.7.1 Setting the radio threshold ........................................................................................................ 33
3.7.2 Setting the traffic PM thresholds ............................................................................................... 34
Page 3 of 103

4. MIB Revision History ............................................................................................... 35

5. MIB error table (Reserved for future use) ................................................................ 36
6. Alarms .................................................................................................................... 37
Page 4 of 103

List of Tables
Table 1: MIB File Names and Versions .....................................................................................................8
Table 2: System Parameters ...................................................................................................................10
Table 3: System Object IDs .....................................................................................................................10
Table 4: Supported IfTables ...................................................................................................................11
Table 5: Standard IfXtable support ........................................................................................................12
Table 6: IfIndex Structure .......................................................................................................................13
Table 7: IfIndex “Format” Field Optional Values ....................................................................................13
Table 8: NG Interface Format IfIndex Structure .....................................................................................13
Table 9: IfIndex “Interface Functional Type” Field Optional Values.......................................................14
Table 10: IfIndex “Slot” Field Optional Values .......................................................................................15
Table 11: IfIndex “Port/Group” Field Optional Values ...........................................................................15
Table 12: NG Service Format Ifindex Structure ......................................................................................15
Table 13: Service Type ............................................................................................................................16
Table 14: IfIndex Examples .....................................................................................................................16
Table 15: Other Supported Networking Parameters .............................................................................18
Table 16: Trap Var-Bind Parameters ......................................................................................................19
Table 17: MIB Objects for Configuring FTP Parameters .........................................................................22
Table 18: Managing software versions MIB object ................................................................................23
Table 19: MIB objects for Checking IDU Software Status ......................................................................24
Table 20: Upgrading RFU software version MIB object .........................................................................25
Table 21: MIB objects for checking RFU software status .......................................................................26
Table 22: MIB objects for configuring FTP settings ................................................................................27
Table 23: Creating Configuration Archive MIB Object ...........................................................................27
Table 24: Uploading Archived Configuration MIB Object ......................................................................28
Table 25: Backup and Upload Status MIB Object ...................................................................................28
Table 26: Enabling Trap Administration .................................................................................................28
Table 27: Managing a trap .....................................................................................................................29
Table 28: Alarm date and time MIB object ............................................................................................30
Table 29: Alarm severity MIB object ......................................................................................................30
Table 30: Alarm Description MIB Object ................................................................................................30
Table 31: Probable Alarm Cause MIB Object .........................................................................................31
Table 32: Corrective Actions MIB Object ...............................................................................................31
Table 33: Event date and time MIB objects ...........................................................................................32
Table 34: Event severity MIB object .......................................................................................................32
Table 35: Event Description MIB Object ................................................................................................32
Page 5 of 103

Table 36: Event Current State MIB Object .............................................................................................33

Table 37: Setting RSL Threshold .............................................................................................................33
Table 38: Setting Traffic PM Thresholds.................................................................................................34
Table 39: Alarms .....................................................................................................................................37
Page 6 of 103

About This Guide

This document describes the IP-20 MIB and explains some of the commonly used objects
and tasks. This guide does not provide details about most of the MIB objects, which can be
found by looking at the MIB itself. This document is designed to be delivered as part of a .zip
file that includes:
• This MIB Reference Guide, in .pdf format.
• The actual MIB files, in .mib format.
• Lists of MIB objects, per product group, in .csv format.
• Diff files showing which MIB objects were added, removed, or modified since the last
CeraOS version, in .htm format.
This document applies to the following IP-20 products:
• IP-20F
• IP-20G
• IP-20GX
• IP-20N
• IP-20A
• IP-20LH
• Evolution IP-20LH
• IP-20C
• IP-20C-HP
• IP-20S
• IP-20E
• IP-20V
Page 7 of 103

1. Private MIB reference

The following table lists and describes the MIB files and file versions supported by
the IP-20 products in releases 11.9.5.
Table 1: MIB File Names and Versions

MIB File Name MIB File Description
Version
MWRM-NETWORK- 1.11.9.5 Networking related OIDs, including Ethernet

MIB switch configuration, forwarding, quality of
service (QoS), policing, control protocols, and
management.
MWRM-PM-MIB 1.11.9.5 Performance Monitoring OIDs for Ethernet and
radio.
MWRM-RADIO-MIB 1.11.9.5 Radio related OIDs, including RFU and radio
management, MRMC, radio group management
(HSB, ABC), header de-duplication, and frame
cut-through.
MWRM-TRAPS-MIB 1.11.9.5 Describes the IP-20 device-specific traps.
MWRM-UNIT-MIB 1.11.9.5 General platform-related OIDs, including alarm
and event services, NTP, license, software
version management, configuration
management, and security and access control.
MWRM-DEFS.MIB OID for microwave-radio (formerly in MMRM-
RADIO-MIB).
Note: Prior to CeraOS 10.7, the material in the MWRM-TRAPS-MIB file was
contained in the MWRM-NETWORK-MIB file.
You can display a list of entities in the private MIB from the Web EMS of the IP-20
unit:
1 From the Web EMS main menu, select Utilities > MIB Reference Guide. The
MIB Reference Table opens.
Page 8 of 103

MIB Reference Table in Web EMS

The MIB Reference Table is customized to the type of IP-20 or IP-50 product you
are using. There are several separate versions of the MIB Reference Table:
• IP-20N, IP-20A, Evolution IP-20LH
• IP-20N or IP-20A with TCC-U, IP-50C, IP-50E
• IP-20F, IP-20G, IP-20GX
• IP-20C, IP-20C-HP, IP-20S, IP-20E, IP-20V, IP-50S
Note: Even through the MIB Reference Table is customized to these product
groups, some of the entities listed in the Table may not be relevant to the
particular unit you are using. This may occur because of activation key
restrictions, minor differences between product types, or simply because a
certain feature is not used in a particular configuration. For example, the
column genEquipUnitShelfSlotConfigTable is relevant to IP-20GX but not IP-
20G.
• To search for a text string, enter the string in the Search field and press
<Enter>. Items that contain the string are displayed in yellow. Searches are
not case-sensitive.
• To save the MIB Reference Table as a .csv file, click Save to File.
Page 9 of 103

2. Standard MIB support

This chapter details the public MIB standards supported by the IP-20 MIB.
2.1 RFC-1213 (MIB II)

This section details the implementation of each area of the RFC-1213 standard
within the context of the IP-20 MIB.
2.1.1 System parameters

The table below details the legal values for each system parameter within
RFC-1213 from implementation within the IP-20 MIB.
Table 2: System Parameters

Parameter Access Description
sysDescr Read only A description of the network element.

sysUpTime Read only The time (in hundredths of a second) since the network
management portion of the system was last re-initialized
sysContact Read write The name of the contact person for this network element
sysName Read write An administratively assigned name for the network element.
By convention, this is the node's fully qualified domain name
sysLocation Read write The physical location of the network element of this node
The table below details the System Object IDs (sysObjectID) within the IP-20 MIB.
The sysObjectID is a unique identifier for the product type.
Table 3: System Object IDs

Product System Object ID SysDescr
IP-20 Products 1.3.6.1.4.1.2281.1.20 High capacity packet radio unit

Indoor Units 1.3.6.1.4.1.2281.1.20.1 High capacity packet radio
indoor shelf
IP-20N 1RU 1.3.6.1.4.1.2281.1.20.1.1 High capacity packet radio 1U
modular indoor shelf
IP-20A 1RU 1.3.6.1.4.1.2281.1.20.1.1.2
IP-20 Evolution LH 1RU 1.3.6.1.4.1.2281.1.20.1.1.4
IP-20N 2RU 1.3.6.1.4.1.2281.1.20.1.2 High capacity packet radio 2U
modular indoor shelf
IP-20A 2RU 1.3.6.1.4.1.2281.1.20.1.2.2
IP-20 Evolution LH 2RU 1.3.6.1.4.1.2281.1.20.1.2.4
IP-20G/GX Indoor Units 1.3.6.1.4.1.2281.1.20.1.3 High capacity packet radio 1U
indoor unit
Page 10 of 103

Product System Object ID SysDescr
IP-20G 1.3.6.1.4.1.2281.1.20.1.3.1 High capacity dual carrier

packet radio 1U indoor unit
IP-20GX 1.3.6.1.4.1.2281.1.20.1.3.2 High capacity semi-modular
IP-20F 1.3.6.1.4.1.2281.1.20.1.4.1 High capacity dual carrier
with STM1 module
IP-20C 1.3.6.1.4.1.2281.1.20.2.2 High capacity multi carrier
packet radio outdoor unit
IP-20C-HP 1.3.6.1.4.1.2281.1.20.2.2.8 High capacity, high power, long
haul packet radio all outdoor
unit
IP-20S 1.3.6.1.4.1.2281.1.20.2.2.2
IP-20E R1 1.3.6.1.4.1.2281.1.20.2.2.3
IP-20E R2 1.3.6.1.4.1.2281.1.20.2.2.4
IP-20E R2H 1.3.6.1.4.1.2281.1.20.2.2.7
IP-20E-R2H-ESP 1.3.6.1.4.1.2281.1.20.2.2.9 Includes 10GbE port.
IP-20V 1.3.6.1.4.1.2281.1.20.2.4.1
2.1.2 Interfaces
ifNumber - The number of network interfaces (regardless of their current state)
present on this system.
2.1.3 ifTable
The ifTable provides a list of all available interfaces to the application developer.
2.1.3.1 ifTable column supported

This section details ifTable support within the IP-20 MIB.
Table 4: Supported IfTables

MIB Name OID Notes
Ifindex 1.3.6.1.2.1.2.2.1.1
Ifdescr 1.3.6.1.2.1.2.2.1.2
Iftype 1.3.6.1.2.1.2.2.1.3
Ifspeed 1.3.6.1.2.1.2.2.1.5
Ifadminstatus 1.3.6.1.2.1.2.2.1.7
Ifoperstatus 1.3.6.1.2.1.2.2.1.8
Page 11 of 103

MIB Name OID Notes
Iflastchange 1.3.6.1.2.1.2.2.1.9
Ifindiscards 1.3.6.1.2.1.2.2.1.13
Ifinerrors 1.3.6.1.2.1.2.2.1.14
Ifoutdiscards 1.3.6.1.2.1.2.2.1.19
Ifouterrors 1.3.6.1.2.1.2.2.1.20
2.1.3.2 IfXTable
Table 5: Standard IfXtable support
MIB Name OID Notes

ifName 1.3.6.1.2.1.31.1.1.1.1
ifInMulticastPkts 1.3.6.1.2.1.31.1.1.1.2
ifInBroadcastPkts 1.3.6.1.2.1.31.1.1.1.3
ifOutMulticastPkts 1.3.6.1.2.1.31.1.1.1.4
ifOutBroadcastPkts 1.3.6.1.2.1.31.1.1.1.5
ifHCInOctets 1.3.6.1.2.1.31.1.1.1.6
ifHCOutOctets 1.3.6.1.2.1.31.1.1.1.10
ifHighSpeed 1.3.6.1.2.1.31.1.1.1.15
ifAlias 1.3.6.1.2.1.31.1.1.1.18
2.1.3.3 RMON – etherStatsTable
MIB Name OID Notes
etherStatsIndex 1.3.6.1.2.1.16.1.1.1.1
etherStatsOctets 1.3.6.1.2.1.16.1.1.1.4
etherStatsPkts 1.3.6.1.2.1.16.1.1.1.5
etherStatsBroadcastPkts 1.3.6.1.2.1.16.1.1.1.6
etherStatsMulticastPkts 1.3.6.1.2.1.16.1.1.1.7
etherStatsCRCAlignPkts 1.3.6.1.2.1.16.1.1.1.8
etherStatsUndersizePkts 1.3.6.1.2.1.16.1.1.1.9
etherStatsOversizePkts 1.3.6.1.2.1.16.1.1.1.10
etherStatsFragments 1.3.6.1.2.1.16.1.1.1.11
etherStatsJabbers 1.3.6.1.2.1.16.1.1.1.12
etherStatsPkts64Octest 1.3.6.1.2.1.16.1.1.1.14
Page 12 of 103

MIB Name OID Notes
etherStatsPkts64Octest 1.3.6.1.2.1.16.1.1.1.15
etherStatsPkts65to127Octest 1.3.6.1.2.1.16.1.1.1.16
2.1.3.4 RMON – etherStatsHighCapacityTable

MIB Name OID Notes
EtherStatsHighCapacityOctets 1.3.6.1.2.1.16.1.7.1.4
2.1.3.5 ifIndex
The IfIndex has the following structure:
Table 6: IfIndex Structure

IfIndex (32 bit)
Bit # 31 (MSB) 30..28 27..0 (LSB)
Function Reserved = 0 Format Format dependent

structures
Bit Width 1 bit 3 bits 28 bits
Table 7: IfIndex “Format” Field Optional Values

Format Value 7..4 3 2 1 0
Function Reserved NG Service Format Reserved NG Interface Format Legacy
2.1.3.6 NG Interface Format
Table 8: NG Interface Format IfIndex Structure

IfIndex (32 bit)
Bit # 31 (MSB) 30…28 27…26 25…17 16…13 12…6 5…0 (LSB)
Function Reserved Format Interface Instance/Service Interface Functional Slot Port

=0 Functional Bundle ID Type (LSB)
Type (MSB)
Bit Width 1 bit 3 bits = 001 2 bits 9 bits 4 bits 7 bits 6 bits
Page 13 of 103

Table 9: IfIndex “Interface Functional Type” Field Optional Values

Interface Functional Type (6-bit)
Functional Type Value Function
0 N/A
1 Ethernet
2 Radio
3 Mng
4 Synch
5 PWE
6 TDM
7 STM-1/OC-3
8 PDC
9 FAN
10 Radio Unit (RFU) Interface
11 RFU-Based ABC Group
12 Enhanced ABC (Multiband)
13 MIMO
14 External Alarm
15 Group
16 Extension Port
17 Advanced Space Diversity
18 Space Diversity
19 XPIC
20 CPRI
21 XPIC State Diversity
22 Link Bonding
23-63 Reserved
Page 14 of 103

Table 10: IfIndex “Slot” Field Optional Values

Slot (7-bit)
Slot Value Function
Physical 0 Chassis
Slots
1 Slot-1
2 Slot-2
… …
50 PDC-1
51 PDC-2
55 Fan
62 Slot-62
63 Slot-63
Virtual 64 LAG
Slots
65 MR
66 CMR/ABC
67 XPIC
68 Radio Protection
69 PWE Protection
70 MIMO
71 Enhanced MC-ABC
72-126 Reserved
127 IVM
Table 11: IfIndex “Port/Group” Field Optional Values
Port Value 63 62 …. 2 1 0
Function Port-63 Port-62 …. Port-2 Port-1 N/A
2.1.3.7 NG Service Format
Table 12: NG Service Format Ifindex Structure
Bit # 31 (MSB) 30..28 27..24 23..12 11..7 6..4 (LSB) 3..0(LSB)

Function Reserved = 0 Format=3 Service type=1 Service Id Service Point id MEG Level Reserved=0
Bit Width 1 bit 3 bits = 011 4 bit 12 bits 5 bits 3bits 4 bits
Page 15 of 103

IfIndex (32 bit)
Table 13: Service Type
Service Type Value 15..2 1 0

Function Reserved Soam MEP N/A
• Service Id – Value from 1 to 4096

• Service Point id – Value from 1 to 32
• MEG level – Value from 1 to 7
Note: The instance is used according to the selected “Interface Functional Type”.
For example, if the “Interface Functional Type” is TDM STM-1, the instances
can be VC-12 (1..63) or VC-11 (1..84). If the “Interface Functional Type” is
TDM E1, the instances can be TS (time slots) 0..31.
2.1.3.8 Calculation of IfIndex

The IfIndex for NG (Format = 1) is calculated as follows:
• IfIndex (decimal) = 268435456 + (Instance * 131072) + (Interface-
Functional-Type * 8192) + (Slot * 64) + Port
• IfIndex (hex) = 0x10000000 + (Instance * 0x20000) (Interface-Functional-
Type * 0x2000) + (Slot * 0x40) + Port
Given NG IfIndex (Format = 1), the following will be calculated out of it:
• Instance = (IfIndex >> 16) and 0x7FF
• Interface-Functional-Type = (IfIndex >> 12) and 0xF
• Slot = (IfIndex >> 5) and 0x7F
• Port = IfIndexand 0x3F
2.1.3.9 IfIndex Examples
Table 14: IfIndex Examples
Functional Type Instance Slot/Port IfIndex (decimal) IfIndex (Hex)

Ethernet 0 1/1 268443713 0x10002041
Ethernet 0 1/2 268443714 0x10002042
Group 0 LAG/1 268447745 0x10003001
Group 0 MR/1 268456001 0x10005041
Group 0 MR/2 268456002 0x10005042
Management 0 1/1 268460097 0x10006041
Radio 0 1/1 268451905 0x10004041
TDM VC27 2/1 272023681 0x1036C081
Page 16 of 103

Page 17 of 103

2.1.4 Other parameters and tables

The following parameters and tables are answered by the CPU interface of the
network element.
Table 15: Other Supported Networking Parameters

Parameters Supported by IP-20 MIB
AT (atTable) Supported
IP Supported (also defined in RFC
2011)
ICMP Supported
TCP Supported (also defined in RFC
2012)
UDP Supported (also defined in RFC
2013)
2.2 Multiple Spanning Tree Protocol (MSTP)

IP-20N, IP-20A, IP-20F, IP-20G, IP-20GX, and IP-20LH support the following
standard MIBs for Multiple Spanning Tree Protocol (MSTP):
• IEEE8021-MSTP-MIB-201103230000Z
• IEEE8021-SPANNING-TREE-MIB-200810150000Z
These MIBs are derived from IETF BRIDGE_MIB (RFC-4188).
There are two additional MSTP related MIBs which are part of the private MIB,
since they are not defined as part of the standard MSTP MIB:
• genEquipProtocolsMstpGeneralAttributesTable
• genEquipProtocolsMstpCountersTable
For more details, refer to the MIB Reference Table. See Private MIB reference on
page 8.
2.3 Trap ID
The following table describes the Trap ID definition in NETWORK-MIB.
SNMP Version Trap type Name ID
V.1 Alarm / Event SNMPv1 Trap 2281.2000

V.1 heartbeat SNMPv1 Trap 2281.2001
V.2/3 Alarm / Event generalNGV3Trap 2281.11.2000
V.2/3 heartbeat heartbeatNGV3Trap 2281.11.2001
Page 18 of 103

2.4 Trap Var-Bind

Table 16: Trap Var-Bind Parameters
SNMP Trap type Name OID Comments
Version
V.2/3 Alarm / sysUpTime 1.3.6.1.2.1.1.3 The time (in

Event hundredths of a
second) since the
network management
portion of the system
was last re-initialized.
V.2/3 Alarm / snmpTrapOID 1.3.6.1.6.3.1.1.4.1 The authoritative
Event identification of the
notification currently
being sent (Trap ID).
V.1/2/3 Alarm / genEquipCurrentAlarmCounter 1.3.6.1.4.1.2281.10.3.1.2.1.1 Contains the
Event / information of a
heartbeat RAISED trap.
V.1/2/3 Alarm / genEquipCurrentAlarmRaisedTimeT 1.3.6.1.4.1.2281.10.3.1.2.1.2 Time the alarm was
Event raised.
V.1/2/3 Alarm / genEquipNetworkAgentIp 1.3.6.1.4.1.2281.10.2.3 Agent IP address (IP V4)
Event
V.1/2/3 Alarm / genEquipCurrentAlarmId 1.3.6.1.4.1.2281.10.3.1.2.1.3 Alarm ID.
Event For a complete list of
Alarm IDs, see Alarms
on page 37.
V.1/2/3 Alarm / genEquipCurrentAlarmDesc 1.3.6.1.4.1.2281.10.3.1.2.1.9 Description of the
Event alarm.
For a complete list of
alarms and their
descriptions, see
Alarms on page 37.
V.1/2/3 Alarm / genEquipCurrentAlarmIfIndex 1.3.6.1.4.1.2281.10.3.1.2.1.7 Interface index that
Event indicates where the
alarm occurred.
V.1/2/3 Alarm / genEquipCurrentAlarmInstance 1.3.6.1.4.1.2281.10.3.1.2.1.5 Alarm Instance.
Event For most alarms, this
parameter is not used
because this
information is reflected
in the ifindex.
Page 19 of 103

SNMP Trap type Name OID Comments

Version
V.1/2/3 Alarm / genEquipCurrentAlarmSeverity 1.3.6.1.4.1.2281.10.3.1.2.1.6 Severity of the current

Event alarm. Possible values
are:
- Indeterminate (0)
- Critical (1)
- Major (2)
- Minor (3)
- Warning (4)
- Cleared (5)
V.1/2/3 Alarm / genEquipCurrentAlarmState 1.3.6.1.4.1.2281.10.3.1.2.1.12 Indicates whether the
Event alarm is raised or
cleared. Possible values
are:
• Alarm cleared (0)
• Alarm raised (1)
• Event (2)
V.1/2/3 Alarm / genEquipCurrentAlarmUserText 1.3.6.1.4.1.2281.10.3.1.2.1.15 User-defined alarm
Event text. Does not need to
contain a value.
V.1/2/3 Alarm / genEquipTrapCfgMgrCLLI 1.3.6.1.4.1.2281.10.3.2.1.1.9 Configures the
Event / Common Language
heartbeat Location Identifier
(CLLI). Does not need to
contain a value.
V.1/2/3 Alarm / genEquipNetworkAgentIpV6 1.3.6.1.4.1.2281.10.2.7 Agent IP address (IP V6)
Event
V.1/2/3 Alarm / genEquipInventorySerialNumber 1.3.6.1.4.1.2281.10.1.2.10.1.1.6 The serial number of
Event the interface with the
alarm.
V.1/2/3 Alarm / genEquipCurrentAlarmModule 1.3.6.1.4.1.2281.10.3.1.2.1.8 The module of the
Event interface with the
alarm.
Page 20 of 103

3. Common tasks
The task descriptions in this chapter are presented from a functional perspective
and represent how the commands and parameters would be used according to a
common workflow.
Each task description contains a step by step procedure that explains how to use
the MIB objects to perform that task.
3.1 Software management
3.1.1 Downloading a software version
3.1.1.1 Software download procedural overview

This section describes the required procedure to download the software package
for the IP-20 unit.
To download and install a new software version:
2 Configure the FTP parameters using table genEquipMngSwFileTransferTable.
3 Download the desired software files with
genEquipMngSwOperationOperation command using download (1)
parameter. The new software files are added to the library.
4 Verify the download status in the genEquipMngSwFileTransferStatusResult
object, until status is download success (4).
The progress of the process (in percentage) can also be tracked using
genEquipMngSwFileTransferPercentageDone.
5 Install the genEquipMngSwOperationOperation command using install (2)
parameter. The software is installed in the system.
6 Verify the installation status in the genEquipMngSwInstallStatusResult object,
until status is installation success (4).
The progress of the process (in percentage) can also be tracked using
genEquipMngSwInstallPercentageDone.
◦ The IP-20 unit automatically resets and applies the changes to all modules.
Verify that the unit is using the downloaded version. The version numbers are
located in the genEquipMngSwIDUVersionsTabletable.
Page 21 of 103

3.1.1.2 Configuring FTP parameters

The new software versions are located on a remote FTP server. In order to
download a new software version, you must configure the parameters of this
server.
Table 17: MIB Objects for Configuring FTP Parameters

Parameter Function OID
genEquipMngSwFileTransferProtocol Chooses the protocol 1.3.6.1.4.1.2281.10.4.1.18.1.2

to be used (FTP, SFTP)
genEquipMngSwFileTransferUserName User name for access 1.3.6.1.4.1.2281.10.4.1.18.1.3
to the configuration
file location.
genEquipMngSwFileTransferPassword Password for the 1.3.6.1.4.1.2281.10.4.1.18.1.4
remote software
update server.
genEquipMngSwFileTransferAddress IP address of the 1.3.6.1.4.1.2281.10.4.1.18.1.5
external server where
from which software
version files are to be
taken.
genEquipMngSwFileTransferPath Location of the files in 1.3.6.1.4.1.2281.10.4.1.18.1.6
the external server.
3.1.1.3 Managing software

There are two commands that help you control the software versions: Download
and install.
The genEquipMngSwOperationOperation MIB object has four values which
execute four different commands:
• No action (0)
• Download (1) – download packages from the remote server.
• Install (2) –install the downloaded packages.
• Update backup (3) –Not supported
• Swap boot section (4) – Not supported
• Abort timer (5) – Not supported
Page 22 of 103

Table 18: Managing software versions MIB object

genEquipMngSwOperation Commands that can be executed to 1.3.6.1.4.1.2281.10.4.1.21.1

Operation manage software versions:
No action (0)
Download (1) – download packages from
the remote server.
install (2) –install the downloaded
packages.
update backup (3) – Not supported
Swap boot section (4) – Not supported
Abort timer (5) – Not supported
3.1.1.4 Checking software status

You can check the status of the most recent software download and installation.
The genEquipMngSwFileTransferStatusTable displays the following values to
indicate the file transfer status:
• Ready (0)
• download-started (1)
• verifying-download-files (2)
• Download-in-progress (3)
• download-success (4)
• download-failure (5)
• all-components-exist (6)
• version-incompatible-with-system (7)
• incomplete-file-set (8)
• component-unsupported-by-hw (9)
• corrupt-sw-files (10)
• missing-dependencies (11)
• download-cancelled (12)
The genEquipMngSwInstallStatusTable displays the following values to indicate
the software status:
• ready (0)
• installation-started (1)
• verifying-installation-files (2)
• installation-in-progress (3)
• installation-success (4)
• installation-partial-success (5)
• installation-failure (6)
• incomplete-sw-version (7)
Page 23 of 103

• cancelled-timed-installation (8)
Table 19: MIB objects for Checking IDU Software Status

genEquipMngSwFileTransferStatusResult Displays the status of the 1.3.6.1.4.1.2281.10.4.1.19.1.2

most recent software
download.
genEquipMngSwFileTransferPercentage Displays the progress of the 1.3.6.1.4.1.2281.10.4.1.19.1.3
Done file transfer operation, in
percentage
genEquipMngSwInstallStatusResult Displays the status of the 1.3.6.1.4.1.2281.10.4.1.20.1.2
most recent software
installation.
genEquipMngSwInstallPercentageDone Displays the progress of the 1.3.6.1.4.1.2281.10.4.1.20.1.3
installation operation, in
percentage.
3.1.2 Upgrading the RFU software version

Note: This procedure is not necessary for IP-20C, IP-20S, IP-20E, IP-20V, and
Evolution IP-20LH units. In these units, all the software modules are upgraded
via the installation process described above.
The software package that is downloaded also includes the necessary software to
upgrade the RFUs.
When upgrading the software version for the RFUs, each RFU must be upgraded
individually.
Upgrading the RFU and IDU are different procedures. When you upgrade the IDU,
the main unit automatically applies the necessary upgrade to all of the IDU
modules, but not to the RFU.
3.1.2.1 RFU software upgrade procedural overview

To install a new software version for the RFU:
1 If the RFU version is not included in the IDU’s installed software package,
download and install the desired relevant software files package (refer to
Downloading a software version on page 21).
The available versions are found in table genEquipRfuAvailableVersionsTable.
2 In order to install the RFU version for a specific slot Install and upgrade the
RFU the new software version use the genEquipRfuSwInstallOperation
genEquipRfuUploadSwCommand update version-from-bundle Upload SW (1)
command.
Page 24 of 103

3 In order to upgrade the RFU in a slot which has already been updated with the
correct version, use the genEquipRfuSwInstallOperation update- install-
existing-version (2) command.
The installed versions are found in table genEquipRfuInstalledVersionsTable.
Verify that the upgrade status in the genEqipRfuUploadSwStatus object. The
status begins as Load Start (2) and continues with Load Send Block (3).
4 Verify that the upgrade status has completed in the
genEquipRfuSwStatusCurrentState object. The status should be installation-
success Load Done (4).
Percentage compleed can also be monitored using
enEquipRfuSwStatusProgress.
5 Verify that the RFU is using the new software version. The version numbers
are located in the genEquipRfuRunningVersionsTable object.
6 Repeat steps 2-5 of this procedure for each RFU in the system as necessary.
3.1.2.2 Upgrading RFU software version

The genEquipRfuSwInstallOperation MIB object has the following values which
control the software upgrade for the RFU:
• No Operation (0) – performs no action
• Upload Swupdate version from bundle (1) – uploads newer packages to the
RFUupdates the RFU version in each slot and updates the RFU
• Install existing version (2) – updates the RFU with the version held at the slot
• Abort timer (3) – abort the time configured in the genEquipRfuSwInstallTimer
The genEquipRfuUploadSwCommand MIB object has two values which controls
the software upgrade for the RFU:
• Upload software (1) – uploads newer packages to the RFU
• No Operation (2) – performs no action
Table 20: Upgrading RFU software version MIB object

genEquipRfuSwInstallOperationgen RFU software installation operation to 1.3.6.1.4.1.2281.10.5.4.2.1.2

be performed.
No Operation (0)
Update-version-from-bundle (1)
Install-existing-version(2)
abort-timer(3)
EquipRfuUploadSwCommand This command initiates the software 1.3.6.1.4.1.2281.10.5.4.2.1.2
upload to the RFU 1.3.6.1.4.1.2281.10.5.3.1.2
Upload software (1)
No Operation (2)
Page 25 of 103

3.1.2.3 Checking RFU software status

You can check the status of the most recent software download and installation.
The genEquipRfuSwStatusCurrentState object displays one of five values to
indicate the RFU software upgrade status:
• Ready (0)
• verifying-files (1)
• transferring-files (2)
• installation-in-progress (3)
• installation-success (4)
• installation-failure (5)
You can use the Following tables to confirm which version of software for the RFU
is currently running:
Table 21: MIB objects for checking RFU software status

genEquipRfuAvailableVersionsTable Versions installed in the IDU’s software 1.3.6.1.4.1.2281.10.5.4.6

bundle. These versions can be installed in
slots
genEquipRfuInstalledVersionsTable Versions installed in each slot. These 1.3.6.1.4.1.2281.10.5.4.3
versions will be installed in RFUs when
needed
genEquipRfuRunningVersionsTable Actual versions running in each RFU. 1.3.6.1.4.1.2281.10.5.4.5
3.2 Configuration file management

The IP-20 MIB file enables you to view the current configuration of the IP-20 unit.
It also allows you to create backup files of the system configuration and upload
them to a FTP server. You can then download the archived backup file for later
use.
3.2.1 System configuration FTP settings

The archived system configurations are stored on a FTP server. The server saves
the file that contains the existing configuration. You can download the system
configuration file and install it on the desired system when necessary.
The FTP settings must be set in the MIB file before you can use the FTP server.
Software download FTP parameters are located in genEquipMngCfgFileTransferTable.
Page 26 of 103

Table 22: MIB objects for configuring FTP settings

genEquipMngCfgFileTransferProtocol Configures the protocol to be used 1.3.6.1.4.1.2281.10.4.2.11.1.2

(FTP, SFTP, HTTP, HTTPS)
genEquipMngCfgFileTransferUserName Configures the required user name 1.3.6.1.4.1.2281.10.4.2.11.1.3
for the FTP server.
genEquipMngCfgFileTransferPassword Configures the required password 1.3.6.1.4.1.2281.10.4.2.11.1.4
for the FTP server.
genEquipMngCfgFileTransferAddress Configures the host IP address of 1.3.6.1.4.1.2281.10.4.2.11.1.5
the FTP server.
genEquipMngCfgFileTransferPath Configures the path of the host 1.3.6.1.4.1.2281.10.4.2.11.1.6
directory on the FTP server.
genEquipMngCfgFileTransferFileName Configures the filename to be used 1.3.6.1.4.1.2281.10.4.2.11.1.7
in the server.
3.2.2 Creating and uploading backup configuration archives

To create a backup file which contains all the details of the current IP-20 configuration,
use genEquipMngCfgOperationOperation with a value of (1) Backup.
Table 23: Creating Configuration Archive MIB Object

genEquipMngCfgOperationOperation Executes the Backup system 1.3.6.1.4.1.2281.10.4.2.13.1.2

configuration commands:
Invalid-operation (0)
Backup (1)
3.2.2.1 Procedural overview of uploading a system configuration

This section describes the required procedure to save the current system
configuration of the IP-20 unit and export it to an FTP server.
To save and upload the current system configuration:
1 Verify the FTP settings.
2 Create the archive files of the current system configuration. The
genEquipMngCfgOperationOperation with Backup (1) command creates an
archive file. Up to three files can be stored, each identified by parameter
genEquipMngCfgOperationFileNumber.
3 Verify that the configuration file generation has succeeded in the
genEquipMngCfgBackupStatus object. The status should be download-success
(3).
Page 27 of 103

4 Upload the archive files to the FTP server with the

genEquipMngCfgOperationOperation with export (5) command.5 Verify that
the upload to the FTP server has succeeded in the
genEquipMngCfgFileTransferStatus object. The status should be download
success (4).
3.2.2.2 Exporting an archived configuration

To export an archived configuration of the IP-20 unit to an FTP server use
genEquipMngCfgOperationOperation with a value of (5) export.
Table 24: Uploading Archived Configuration MIB Object

genEquipMngCfgOperation Executes the Backup system 1.3.6.1.4.1.2281.10.4.2.13.1.2

Operation configuration commands:
Export (1)
3.2.2.3 Backup and Export status

The genEquipMngCfgFileTransferStatus and genEquipMngCfgUploadStatus
objects display that backup and upload status of the system configuration.
Table 25: Backup and Upload Status MIB Object

genEquipMngCfgBackupStatus Status of the configuration 1.3.6.1.4.1.2281.10.4.2.1

backup file to the unit.
genEquipMngCfgFileTransferStatus Status of uploading the 1.3.6.1.4.1.2281.10.4.2.21
configuration backup file to
the FTP server.
3.3 Enabling and configuring traps
3.3.1 Enabling trap administration

To change the setup for a trap, you must enable the administrative state for the
specific trap manager.
Table 26: Enabling Trap Administration

Index: genEquipTrapCfgMgrId
genEquipTrapCfgMgrAdmin Set to Enable (2) in order to 1.3.6.1.4.1.2281.10.3.2.1.1.2

configure a specific trap manager.
Page 28 of 103

3.3.2 Managing a trap

Trap manager configuration:
• Trap manager IP address to which the traps are sent.
• Port number that sends the trap.
• Name of the trap manager.
• Community name to trap forwarding.
• Period (in minutes) of the heartbeat trap.
• CLLI (Common Language Location Identifier) free text that is sent with the
trap.
Table 27: Managing a trap

Index: genEquipTrapCfgMgrId
genEquipTrapCfgMgrId The ID of the trap manager. User can 1.3.6.1.4.1.2281.10.3.2.1.1.1

define up to 4 independent trap
managers
genEquipTrapCfgMgrIP Configures the trap manager’s IP 1.3.6.1.4.1.2281.10.3.2.1.1.3
address.
genEquipTrapCfgMgrPort Configures the port that sends the 1.3.6.1.4.1.2281.10.3.2.1.1.4
trap for each manager.
genEquipTrapCfgMgrName Configures the name of the manager 1.3.6.1.4.1.2281.10.3.2.1.1.5
that receives the traps.
genEquipTrapCfgMgrCommunity Configures the name of the manager 1.3.6.1.4.1.2281.10.3.2.1.1.6
community that receives the traps.
genEquipTrapCfgMgrCLLI Configures the Common Language 1.3.6.1.4.1.2281.10.3.2.1.1.9
Location Identifier (CLLI).
genEquipTrapCfgMgrHeartbeatPeriod Configures the minute interval 1.3.6.1.4.1.2281.10.3.2.1.1.10
between each heartbeat.
Page 29 of 103

3.4 Viewing current alarms
3.4.1 Alarm date and time

You can view the date and time that an alarm was raised. There are two objects
that can be used for this parameter.
Table 28: Alarm date and time MIB object

genEquipCurrentAlarmRaisedTimeT Time the alarm was raised, 1.3.6.1.4.1.2281.10.3.1.2.1.2

in seconds since January 1,
1970 00:00 UTC
genEquipCurrentAlarmRaisedDateAn Time the alarm was raised, 1.3.6.1.4.1.2281.10.3.1.2.1.16
dTime in DateAndTime standard
format.
3.4.2 Alarm severity

You can view the alarm severity.
Table 29: Alarm severity MIB object

genEquipCurrentAlarmSeverity Severity of the current alarm: 1.3.6.1.4.1.2281.10.3.1.2.1.

Indeterminate (0) 6
Critical (1)
Major (2)
Minor (3)
Warning (4)
Cleared (5)
3.4.3 Alarm description

You can view the description of the alarm.
Table 30: Alarm Description MIB Object

genEquipCurrentAlarmDesc Description of the 1.3.6.1.4.1.2281.10.3.1.2.1.9

alarm.
Page 30 of 103

3.4.4 Probable cause

You can view the probable cause for the alarm.
Table 31: Probable Alarm Cause MIB Object

genEquipCurrentAlarmProbableCause Probable cause of the alarm. 1.3.6.1.4.1.2281.10.3.1.2.1.10
3.4.5 Corrective actions

You can view the recommended corrective actions to solve the problem that
caused the alarm.
Table 32: Corrective Actions MIB Object

genEquipCurrentAlarmCorrectiveActions Corrective actions that 1.3.6.1.4.1.2281.10.3.1.2.1.11

should be taken
Page 31 of 103

3.5 Viewing event log
3.5.1 Event date and time

You can view the date and time that an alarm or event was raised or cleared.
There are two objects that can be used for this parameter.
Table 33: Event date and time MIB objects

genEquipEventLogRaisedTimeT Time the item was added to 1.3.6.1.4.1.2281.10.3.3.1.1.2

the Event Log. This is given
in seconds since January 1,
1970 00:00 UTC
genEquipEventLogRaisedDateAndTi Time the item was added to 1.3.6.1.4.1.2281.10.3.3.1.1.13
me the Event Log, in
DateAndTime standard
format.
3.5.2 Event severity

You can view the event severity.
Table 34: Event severity MIB object

genEquipEventLogSeverity Severity of the current alarm or 1.3.6.1.4.1.2281.10.3.3.1.1.

event: 3
Indeterminate (0)
Critical (1)
Major (2)
Minor (3)
Warning (4)
Cleared (5)
3.5.3 Event description

You can view the description of the alarm or event.
Table 35: Event Description MIB Object

genEquipEventLogDesc Description of the 1.3.6.1.4.1.2281.10.3.3.1.1.5

alarm or event.
Page 32 of 103

3.5.4 Event state

You can view the current state of the alarm or event (raised or cleared).
Table 36: Event Current State MIB Object

genEquipEventLogState Current state of the alarm or event. 1.3.6.1.4.1.2281.10.3.3.1.1.6

• In case of alarm, 'cleard' or
'raised'.
• In case of event, 'event'.
3.6 Performance monitoring and counters

You can use the MIB file to configure and retrieve the performance monitoring
data of the IP-20 unit.
3.6.1 Clearing all performance counter data

You can use the genEquipPmClear command to clears the values for all of the
performance monitoring tables.
The Object ID is: 1.3.6.1.4.1.2281.10.6.3.1.
3.7 Managing radio configuration

You can use the MIB file to manage the radio configuration data of the unit.
3.7.1 Setting the radio threshold

This section explains how to set the Radio thresholds. After the thresholds are set,
the system records the number of seconds that each of them was exceeded.
Table 37: Setting RSL Threshold

genEquipPmRadioThresholdMSE Configures which PM table is accessed. 1.3.6.1.4.1.2281.10.6.3.4.5.1.1

genEquipPmRadioThresholdRSL1 Configures which interface or port is 1.3.6.1.4.1.2281.10.6.3.4.5.1.2
monitored.
genEquipPmRadioThresholdRSL2 Configures the time interval of the PM. 1.3.6.1.4.1.2281.10.6.3.4.5.1.3
GenEquipPmRadioThresholdTSL Percentage of received frames that 1.3.6.1.4.1.2281.10.6.3.4.5.1.5
contained errors.
genEquipPmRadioThresholdXPI Maximum Ethernet throughput 1.3.6.1.4.1.2281.10.6.3.4.3.1.1.4
measured during the last interval.
Page 33 of 103

3.7.2 Setting the traffic PM thresholds

This section explains how to set radio capacity, throughput, and utilization PM
thresholds. After the thresholds are set, the system records the number of
seconds that each of them was exceeded.
Table 38: Setting Traffic PM Thresholds

genEquipRadioCompNGCfgCapaci Configures the threshold for capacity 1.3.6.1.4.1.2281.10.7.5.4.1.1.6

tyPmThreshold PMs, in Mbps. The range of values is 0 to
4294967295. The default value for is
1000.
enEquipRadioCompNGCfgThroug Configures the threshold for throughput 1.3.6.1.4.1.2281.10.7.5.4.1.1.7
hputPmThreshold PMs, in Mbps. The range of values is 0 to
4294967295. The default value for is
1000.
genEquipRadioCompNGCfgUtiliza Configures the radio capacity utilization 1.3.6.1.4.1.2281.10.7.5.4.1.1.8
tionPmThreshold threshold, in % (1-100). The default
value for is 100.
Page 34 of 103

4. MIB Revision History

The following HTML files are included in a ZIP file with this MIB Reference:
• MIB_11.9_to_11.9.5_DIFF_IP-20N_IP-20A_IP-20LH.htm
• MIB_11.9_to_11.9.5_DIFF_IP-20N_IP-20A_TCC-U.htm
• MIB_11.9_to_11.9.5_DIFF_IP-20F_IP-20G_IP-20GX.htm
• MIB_11.9_to_11.9.5_DIFF_IP-20C_IP-20S_IP-20E_IP-20V.htm
These files list the MIB objects that were changed, added, or deleted from CeraOS
11.9 to CeraOS 11.9.5.
In each of these DIFF files, the column on the left displays the 11.9 version of the
object and the column on the right displays the 11.9.5 version of the object.
For rows in which the left column is empty, the object was added in CeraOS
11.9.5.
For rows in which the right column is empty, the object was removed in CeraOS
11.9.5.
Page 35 of 103

5. MIB error table (Reserved for future use)

If there are any errors related to the IP-20 unit, an errno is generated. Check the
errno description in the following table to find a textual description of the error.
The table contains two columns:
• Errno Fault Number – genEquipFaultErrno (OID 1.3.6.1.4.1.2281.10.3.4)
• Errno Description – genEquipFaultErrDescr (OID 1.3.6.1.4.1.2281.10.3.5)
Page 36 of 103

6. Alarms
The following table lists all alarms used in IP-20 products.
Table 39: Alarms

Alarm ID Name Type Group Description Severity Probable Cause Corrective Action
10 radio-digital-loopback Alarm Equipment Framer digital loopback Warning User enabled framer Disable the framer digital
is enabled. digital loopback. loopback.
11 ntp-local Alarm Communications NTP locked on local Warning The configured and Configure or enable another
clock enabled NTP servers are NTP server, one that is
all unreachable or reachable with sufficient
providing insufficient quality.
quality.
15 ntp-locked Event Communications NTP locked on server Indeterminate
251 main-board-extreme- Alarm Unit Temperature is out Warning
temperature-alarm of system specified
limits.
1
This alarm is only relevant for IP-20 all-outdoor products.
Page 37 of 103

26 main-board-low-voltage-alarm Alarm N/A Unit input voltage is too Warning 1. Power supply output 1. Check/replace the power
low. is too low. supply connected to the
2. Power cable to the RFU.
unit is defective. 2. Check/replace the power
3. Threshold value is cable connected to the
not set correctly. RFU.
3. Set the threshold
correctly.
27 main-board-high-voltage-alarm Alarm N/A Unit input voltage is too Warning 1. Power Supply output 1. Make sure the power
high. is too high. supply voltage is within
2. Threshold value not the specification range. 2)
set correctly. Adjust the threshold value.
28 main-board-warm-reset Event Unit warm reset. Indeterminate

29 main-board-cold-reset Event Unit reset. Warning
30 main-board-poe-low-voltage- Alarm POE input voltage is too Warning 1. PoE supply output is Make sure the PoE voltage is
alarm low too low. within the specification range.
2. PoE cable to the unit
is defective.
31 Event Change Remote request Major
was sent
32 Event Protection switchover Major
due to remote request
33 protection-mimo- Alarm Major Unit Redundancy and
misconfiguration-alarm MIMO 4x4 cannot
operate simultaneously.
Page 38 of 103

100 lag-degraded Alarm Equipment LAG is not fully Major 1. At least one interface 1. Check the physical
functional - LAG is not connected or connections.
Degraded. configured to admin 2. Verify that the Admin state
down. of all the LAG members is
2. If one of the up.
members is radio it 3. Verify the operational
might be in state of all radio members
operational state in the LAG.
down due to channel
fading
101 lag-down Alarm Equipment LAG operational state is Critical The LAG group is not 1. Check the physical
down operational. connections and
administrative status on
both sides of the link of all
interfaces that are
members of the LAG
Group.
2. Check the physical
connections of all
interfaces that are
members of the LAG
Group.
102 ethernet-loopback-active-alarm Alarm Equipment Loopback is active Major Ethernet loopback is Wait for expiration of the
active. loopback timeout, or manually
disable the loopback.
Page 39 of 103

103 port-mirroring-is-active Alarm Equipment Slot X port XX is Minor Mirroring is enabled by Disable mirroring.
mirrored to slot Y port user configuration.
YY
104 qos-mode-mismatch Alarm Processing System reset is required Major QoS mode has been Reset the system
after QoS mode has changed by user
been changed
110 lbg-degraded-alarm Alarm Equipment Link Bonding Group is Major Radio or Ethernet port Check the operational status of
not fully functional - associated with the LBG Radio or Ethernet ports
LBG degraded member is down
111 lbg-down-alarm Alarm Equipment Link Bonding Group Critical Radio or Ethernet ports Check the operational status of
operational state is associated with the LBG Radio or Ethernet ports
Down are down
112 lbg-chassis-reset-required- Alarm Equipment Chassis reset is required Warning 1. Link Bonding Group Reset the unit
alarm after Link Bonding was deleted.
group configuration was 2. Link Bonding Group
modified max bandwidth was
changed.
120 port-speed-mismatch-alarm Alarm Equipment Port speed mismatch Major System reset is required 1. Reset the system.
after the port speed was 2. Change the port speed
changed. back to the previous value.
Page 40 of 103

150 auto-state-propagation- Alarm Communications Auto-state-propagation Major Failure of the Check adjacent local/remote
interface-down-alarm is triggered radio/remote radio radio interface for failure
interface which is conditions that cause
monitored for automatic automatic state propagation.
state propagation causes
automatic shutdown of
the controlled interface.
200 protection-communication- Alarm Equipment Protection Major 1. Mate unit is 1. Verify that the mate unit is
down-alarm communication is down absent/failure. up and running.
2. Protection cable is 2. Check the state of the
disconnected. protection cable
3. Unit failure. connection.
4. In FIPS mode or IPsec 3. Reset the mate unit.
mode, a mismatch 4. Replace the mate unit.
between the IPsec 5. If IPsec/FIPS is enabled,
pre-shared keys verify the same pre-shared
configured on the key is configured on both
two units. units.
201 protection-lockout-alarm Alarm Equipment Protection in Lockout Major
State
202 protection-switch-command Event Equipment Protection switchover Major 1. Check the unit.
due to local failure 2. Look for current alarms.
Page 41 of 103

203 protection-mate-not-present- Alarm Equipment Mate does not exist Major Mate does not exist or 1. Verify that the mate unit is
alarm cable unplugged. up and running.
2. Verify that the protection
cable is properly
connected between the
units.
204 protection-hsb-insufficient- Alarm Equipment HSB insufficient Critical External Protection Remove External Protection or
alarm configuration configured together with 1+1 HSB configuration.
1+1 HSB.
205 protection-revertive-primary- Alarm Equipment Protection revertive warning Identical configuration for Ensure one (and only one) unit
insufficient-alarm mode - insufficient the revertive-primary is configured as the primary
configuration parameter. unit.
307 tdm-link-up Event Equipment TDM interface is up Warning
308 tdm-link-down Event Equipment TDM interface is down Warning
401 TrafficPhyLocAlarm Alarm Equipment Loss of Carrier Major 1. Cable disconnected. At both ends of the cable:
2. Defective cable. 1. Check the cable
3. External equipment connection.
failure. 2. Check the Admin state of
the port.
3. Replace the cable.
4. Check external equipment.
407 ethernet-link-up Event Equipment Ethernet interface is up Warning Ethernet interface is back Notification. Corrective action
to being operational. is not required.
Page 42 of 103

408 ethernet-link-down Event Equipment Ethernet interface is Warning 1. User commanded the 1. Set the Ethernet interface
down interface to admin admin State to Up.
down. 2. Reconnect the Ethernet
2. Ethernet cable is cable
disconnected. 3. Wait 30 seconds to allow
3. Ethernet card is the Ethernet card to
initializing. complete its init.
4. External equipment 4. Check external equipment.
failure.
601 radio-excessive-ber Alarm Communications Radio excessive BER Major 1. Fade in the link. 1. Check link performance via
2. Defective IF cable. the Web EMS Radio PM
and Statistics page and
3. Fault in RFU.
take corrective action
4. Fault in RMC (Radio accordingly..
Modem Card).
2. Check IF cable and replace
5. Interference on the if required.
link.
3. Replace RFU.
4. Replace RMC (Radio
Modem Card).
5. Remove source of
interference or change link
frequency.
Page 43 of 103

602 remote-link-id-mismatch Alarm Equipment Link ID mismatch Major 1. Link ID is not the 1. Configure same Link ID for
same at both sides of both sides of link via Web
link. EMS Radio Parameters
2. Radio has synched on page.
the wrong peer radio. 2. Check if the radio is
synched on the correct
peer radio (check: channel
frequency, antennae
direction).
603 radio-lof Alarm Communications Radio loss of frame Critical 1. Fade in the link. 1. Check link performance.
2. Defective IF cable. 2. Check IF cable and replace
3. Fault in RFU. if required.
4. Fault in RMC (Radio 3. Replace RFU.
Modem Card). 4. Replace RMC (Radio
5. Different radio scripts Modem Card).
at both ends of the 5. Make sure same script is
link. loaded at both ends of the
link.
604 radio-signal-degrade Alarm Communications Radio signal degrade Minor 1. Fade in the link. 1. Check link performance.
2. Defective IF cable. 2. Check IF cable and replace
3. Fault in RFU. if required.
4. Fault in RMC (Radio 3. Replace RFU.
Modem Card). 4. Replace RMC (Radio
Modem Card).
605 radio-link-up Event Equipment Radio interface is up Warning The radio interface is back No action is required.
to being operational.
Page 44 of 103

606 radio-link-down Event Equipment Radio interface is down. Warning Radio interface is not 1. If required, set the radio
operational: interface admin State to
1. User configured the Up.
radio interface to 2. Check if there is a reason
admin Down. for LOF / Excessive BER
2. Loss of Frame (LOF) alarms.
alarm is raised. 3. Wait 30 seconds until the
3. Excessive BER alarm radio card finishes its init.
is raised.
4. Radio card has not
completed its init.
607 rfu-frequency-scanner-in- Alarm Equipment Frequency scanner in Warning The frequency scanner is If required, stop the frequency
process progress activated. scanner process.
801 corrupted-file-card-failure Alarm Equipment Corrupted inventory file Critical The inventory file is 1. Reset the card.
corrupted 2. Reinstall the software.
3. Replace the unit.
802 file-not-found Alarm Equipment Inventory file not found Warning The inventory file is 1. Reset the system.
missing 2. Reinstall the software.
3. Replace the unit
Page 45 of 103

803 sfp-rx-power-level-low Alarm Equipment SFP port RX power level Warning 1. Remote SFP port Tx 1. Verify remote SFP Tx laser
is below the rx power laser power is too power is within range.
level low threshold low. 2. Check fiber type and
2. Fiber length is too length fit the installed SFP.
long or fiber type If not, replace it with an
doesn't fit the appropriate one.
installed SFP.
804 sfp-rx-power-level-high Alarm Equipment SFP port RX power level Warning Remote SFP Tx power is Add attenuator on Rx side.
is above the rx power too high.
level high threshold
805 sfp-tx-power-level-low Alarm Equipment SFP port TX power level Warning SFP transmit laser power Check laser Bias current. If it is
is below the tx power is too low too low, replace SFP.
level low threshold
806 sfp-tx-power-level-high Alarm Equipment SFP port TX power level Warning SFP laser Tx power is too Check laser Bias current and
is above the tx power high. laser temperature values. If
level high threshold either of them is too high,
replace SFP.
807 recovered-inventory-on-boot- Event Equipment Default Activation Key Critical Corrupted Inventory
event activated due to failure
808 recovered-inventory-on- Event Equipment Activation Key Critical Corrupted Inventory
running-event Configuration failed
901 demo-license-alarm Alarm Equipment Demo mode is active Warning Demo mode has been Disable demo mode from the
activated by the user Activation Key Configuration
page in the Web EMS.
902 license-demo-expired Event Equipment Demo mode is expired Warning
Page 46 of 103

903 license-demo-start-by-user Event Processing Demo mode is started Warning

904 license-demo-stop-by-user Event Processing Demo mode is stopped Warning
905 license-load-fail Event Equipment Activation key loading Major
failure
906 license-load-successful Event Equipment Activation key loaded Warning
successfully
907 license-violation-alarm Alarm Equipment Activation key violation Critical The current configuration 1. Go to the "Activation Key
does not match the Overview" page in the
activation-key-enabled Web EMS to display a list
feature set. of features and their
48 hours after an activation key violation
"activation-key-violation" status.
alarm is raised, sanction 2. Install a new activation key
mode is activated in that enables all features
which all alarms except and capacities that you
the activation key require.
violation alarm are
cleared and no new
alarms are raised.
908 demo-license-about-to-expire- Alarm Equipment Demo mode is about to Major Demo mode allowed Disable demo mode and install
alarm expire period is about to end a new valid activation key in
within 10 days the “Activation Key
Configuration” page of the
Web EMS.
Page 47 of 103

910 license-signature-failed-alarm Alarm Equipment Activation key signature Major Activation key validation Make sure that the activation
failure has failed due to invalid key matches the serial number
product serial number or of the unit.
activation key does not
match.
911 license-violation-runtime- Event Equipment Activation key violation Major
counter-expired sanction is enforced
913 license-bad-xml-file-alarm Alarm Equipment Activation key Major Essential internal Reinstall software
components are missing activation key
or corrupted components are missing
or corrupted.
1002 radio-protection-configuration- Alarm Equipment Radio protection Major The configuration Apply a copy-to-mate
mismatch configuration mismatch between the radio command to copy the
protection members is configuration from the active
not aligned radio to the standby radio.
1006 radio-protection-switchover- Event Equipment Radio protection Warning Protection decision Check the system for local
event switchover - reason machine initiated failures. What checks? Check
switchover due to local Radio Parameters: Tx Level, Rx
failure or user command Level, Modem MSE.
1007 radio-protection-no-mate Alarm Equipment Radio protection no Major Radio protection function 1. Insert the radio module.
mate is missing radio module, 2. Replace a defective
module defected or existing radio module.
disabled
3. Make sure all radio
interfaces are enabled.
Page 48 of 103

1008 radio-protection-remote- Event Equipment Remote switchover Warning

switch-request request was sent -
reason
1009 radio-protection-lockout Alarm Equipment Radio protection Major The user has issued a Clear the lockout command
lockout command is on lockout command
1010 ethernet-protection-switchover Event Equipment Ethernet Interface Warning 1. LOC event on an 1. Check the system for local
Group protection Ethernet interface. failures.
switchover 2. Protection group 2. Check external equipment.
member was disabled
or pulled out of the
shelf.
1011 interface-protection-lockout Alarm Equipment Interface protection Major 1. The user has issued a 1. If required, clear the
lockout is on lockout command lockout.
1012 interface-protection-no-mate Alarm Equipment Interface protection no Major Interface protection 1. Insert the interface
mate: mate interface is function is missing an module.
missing or disabled interface module, module 2. Replace a defective
is defective or disabled. existing interface.
3. Make sure all interfaces
are enabled.
1102 software-installation-status Event Processing Software installation Warning
status:
1105 software-new-version-installed Event Processing New version installed Warning A software version has
been installed but system
has not been reset.
Page 49 of 103

1111 software-user-confirmation- Event Processing User approved Warning

for-version download of software
version file
1112 software-download-status Event Processing Software download Warning
status:
1113 software-download-missing- Event Processing Missing SW Warning
components components:
1114 software-management- Event Processing Incomplete file set; Warning Software bundle is Get a complete software
incomplete-bundle missing components missing components. bundle
1118 software-mate-download- Event Processing Mate software Warning
status download status:
1119 software-mate-installation- Event Processing Mate software Warning
status installation status:
1150 backup-started Event Processing Configuration file Warning User command
backup generation
started
1151 backup-succeeded Event Processing Configuration file Warning Backup file creation
backup created finished successfully
1152 backup-failure Event Processing Failure in configuration Warning System failed in attempt
file backup generation to create backup
configuration file
1153 restore-succeeded Event Processing Configuration Warning Configuration restore
successfully restored finished successfully
from file backup
Page 50 of 103

1154 restore-failure Event Processing Failure in configuration Warning System failed in attempt 1. Configuration file system
restoring from backup to restore configuration type mismatch
file from backup file 2. Invalid or corrupted
configuration file
1155 restore-canceled Event Processing Configuration restore Warning Restore operation Try again
operation cancelled cancelled because of user
command or execution of
another configuration
management operation
1156 file-transfer-issued Event Processing User issued command Warning User command
for transfer of
configuration file
1157 file-transfer-succeeded Event Processing Configuration file Warning Configuration file transfer
transfer successful successful
1158 file-transfer-failure Event Processing Configuration file Warning 1. Communications 1. Mark sure protocol details
transfer failure failure. are properly configured.
2. File not found in 2. Make sure file exists.
server
1159 file-transfer-in-progress Event Processing Configuration file Warning File transfer started
transfer in progress
1163 cli-script-activation-started Event Processing CLI configuration script Warning User command
activation started
1164 cli-script-activation-succeeded Event Processing CLI Configuration script Warning
executed successfully
Page 51 of 103

1165 cli-script-activation-failure Event Processing CLI Configuration script Warning 1. Syntax Error. Verify script in the relevant
failed 2. Error returned by line, and run again.
system during Note that script may assume
runtime pre-existing configuration.
1166 unit-info-file-transfer-status- Event Processing Unit info file transfer Warning
changed status:
1167 unit-info-file-creation-status- Event Processing Unit info file creation Warning
changed status:
1169 restore-started Event Processing Configuration restore Warning Restore operation started
operation started because of user command
1201 file-missed Alarm Equipment Modem firmware file Critical Modem file is missing 1. Download software
not found package.
2. Reset the system.
1202 load-failed Alarm Equipment Modem firmware was Critical 1. Modem firmware file 1. Download software
not loaded successfully is corrupted. package.
2. System failure. 2. Reset the system.
1203 modem-wd-reset Event Equipment Modem watch-dog Warning
reset event
1301 fpga-file-currupt-alarm Alarm Equipment Radio MRMC script LUT Critical Damaged radio MRMC Download the specific radio
file is corrupted script LUT file MRMC script LUT file
1302 fpga-file-not-found-alarm Alarm Equipment Radio MRMC script LUT Critical Missing radio MRMC Download the specific radio
file is not found script LUT file MRMC script LUT file
1304 modem-script-file-corrupt- Alarm Equipment Radio MRMC script Critical Damaged radio MRMC Download the specific radio
alarm modem file is corrupted script modem file MRMC script modem file
Page 52 of 103

1305 modem-script-file-not-found- Alarm Equipment Radio MRMC script Critical Missing radio MRMC Download the specific radio
alarm modem file is not found script modem file MRMC script modem file
1308 rfu-file-corrupt-alarm Alarm Equipment Radio MRMC file is Critical Damaged Radio MRMC Download the specific radio
corrupted script LUT file MRMC RFU file
1309 rfu-file-not-found-alarm Alarm Equipment Radio MRMC RFU file is Major Missing radio MRMC RFU Download the specific radio
not found file MRMC RFU file
1312 script-loading-failed Alarm Equipment Radio errrror! Major Damaged hardware Replace the radio hardware
MRMC script loading module module
failed
1313 mrmc-profile-below-thresh1 Alarm Equipment MRMC RX profile below Major
threshold 1
1314 mrmc-profile-below-thresh2 Alarm Equipment MRMC RX profile below Critical
threshold 2
1315 rfu-logger-start Event Equipment RFU logger start Warning RFU logger started by Stop the RFU logger
user
1316 rfu-logger-stop Event Equipment RFU logger stop Warning RFU logger stopped by Stop the RFU logger
user
1401 incompatible-rfu-tx-calibration Alarm Equipment Incompatible RFU TX Major RFU calibration tables Upgrade IDU SW
calibration require SW upgrade
1501 remote-communication-failure Alarm Equipment Remote communication Critical Fade in the link Check the link performance
failure
1601 if-loopback Alarm Equipment IF loopback Warning User enabled IF loopback Disable IF loopback
Page 53 of 103

1602 lock-detect Alarm Equipment IF synthesizer is Critical 1. Extreme temperature 1. Check installation.
unlocked. condition. 2. Reset the RMC (Radio
2. HW failure. Modem Card) module.
3. Replace the RMC (Radio
Modem Card).
1610 rsl-degradation-threshold-out- Alarm Equipment Radio Receive Signal Warning RSL is very low due to: 1. Check for obstruction in
of-range Level is below the 1. Weather conditions, link path.
configured threshold obstruction in 2. Check the antennae
antenna line of sight, alignment and link
antennae alignment. planning.
2. Configured threshold 3. Recalculate the Path Loss
needs to be and set the threshold
adjusted.2. accordingly.
4. Check link settings - Tx
Power and Tx Frequency.
5. Check for a hardware
problem.
1651 atpc-override Alarm Communications ATPC overridden: Tx Warning Actual transmitted signal Correct the transmission levels.
level has been equal to level has been at its The alarm will be cleared only
the Max Tx level for a maximum value for longer upon manual clearing.
longer time than than allowed. This is
allowed probably caused by a
configuration error or link
planning error.
Page 54 of 103

1697 radio-unit-extreme- Alarm Equipment Radio unit extreme Warning 1. Installation 1. Correct the installation
temperature temperature conditions. conditions.
2. Defective RFU. 2. Verify that the product is
operating according to
specifications.
3. Replace the RFU.
1698 radio-unit-low-voltage Alarm Equipment Radio unit input voltage Warning 1. Power supply output 1. Check/replace the power
is too low is too low. supply connected to the
2. Power cable to RFU is RFU.
defective. 2. Check/replace the power
cable connected to the
RFU.
1699 radio-unit-high-voltage Alarm Equipment Radio unit input voltage Warning Power Supply output too 3. Check power supply.
is too high high.
1700 fw-download-failure Alarm Communications Radio unit not aligned Critical 1. FW alignment 1. Reinitiate the FW
to IDU interrupted, power download by disabling and
disruption, ODU then enabling the
cable malfunction. corresponding RFU port.
2. Damaged ODU. 2. Replace the ODU
1701 cable-open Alarm Equipment Cable open Major Cable is not connected to 1. Check cables and
radio card or RFU. connectors.
2. Replace Radio card.
3. Replace RFU.
Page 55 of 103

1702 cable-short Alarm Equipment Cable short Major Physical short at the IF 1. Check cables and
cable connectors.
2. Replace Radio card.
3. Replace RFU.
1703 communication-failure Alarm Equipment RFU communication Warning 1. Defective IF cable. 1. Verify RFU software
failure 2. IF cable not download completed.
connected properly. 2. Check IF cable and
3. Defective RMC (Radio connector.
Modem Card). 3. Verify that N-Type
4. Defective RFU. connector inner pin is not
spliced.
5. RFU software
download in 4. Replace RMC.
progress. 5. Replace RFU.
For High Power RF Unit:
1. Check BMA connector on
OCB
2. Check BMA connector on
RFU.
1704 delay-calibration-failure-1 Alarm Equipment RFU delay calibration Warning Defective RFU 1. Reset the RMC (Radio
failure 1 Modem Card) / RFU.
2. Replace RFU.
1705 delay-calibration-failure-2 Alarm Equipment RFU delay calibration Warning Calibration cannot be Enter delay calibration value
failure 2 completed due to notch manually.
detection
Page 56 of 103

1706 extreme-temp-cond Alarm Equipment RFU extreme Warning 1. Installation 1. Verify that the product is
temperature conditions. operating according to
2. Defective RFU. specifications.
2. Correct the installation
conditions.
3. Replace the RFU."
1707 radio-unit-abc-incompatible-rfu Alarm Equipment RFU is incompatible Warning The RFU type does not Replace the RFU with an RFU
with ABC configuration support the type of Multi- type that supports the
Carrier ABC the user has configured Multi-Carrier ABC
configured. type.
1708 freq-set-automatically Event Equipment RFU frequency was set Warning Defective RFU 1. Check if problem repeats
automatically and if errors/alarms
reported.
2. Replace RFU.
1709 hardware-failure-1 Alarm Equipment RFU hardware failure 1 Critical Defective RFU. Replace RFU.
1710 hardware-failure-2 Alarm Equipment RFU hardware failure 2 Critical Defective RFU. Replace RFU.
1711 low-if-signal-to-rfu Alarm Equipment Low IF signal to RFU Major 1. IF cable connection. 1. Check IF cable connectors.
2. Defective RFU. 2. Verify that N-Type
3. Defective RMC (Radio connector inner pin is not
Modem Card). spliced.
Modem Card).
4. Replace RFU.
Page 57 of 103

1712 no-signal-from-rfu Alarm Equipment Low IF signal from RFU Warning Low RX IF signal (140 1. Check IF cable and
MHz) from RFU. connectors.
2. Verify that N-Type
connector inner pin is not
spliced.
Modem Card).
4. Replace RFU.
1713 pa-extreme-temp-cond Alarm Equipment RFU PA extreme Warning 1. Installation 1. Check installation
temperature conditions. conditions.
2. Defective RFU. 2. Replace RFU.
1714 power-failure-12v Alarm Equipment RFU power failure (12v) Major 1. Defective IF 1. Replace IF
cable/connector. cable/connector.
3. Defective IDU. 3. Replace IDU.
1715 power-failure-1point5 Alarm Equipment RFU power failure (1.5v) Major 1. Defective IF 1. Replace IF
1716 power-failure-24v Alarm Equipment RFU power failure (24v) Major 1. Defective IF 1. Replace IF
Page 58 of 103

1717 power-failure-6v Alarm Equipment RFU power failure (6v Major 1. Defective IF 1. Replace IF
pro) cable/connector. cable/connector.
1718 power-failure-6v-sw Alarm Equipment RFU power failure (6v Major 1. Defective IF 1. Replace IF
SW) cable/connector. cable/connector.
1719 power-failure-minus-5v Alarm Equipment RFU power failure (-5v) Major 1. Defective IF 1. Replace IF
1720 power-failure-vd Alarm Equipment RFU power failure (Vd) Major 1. Defective IF 1. Replace IF
1721 reset-occurred Event Equipment RFU reset Major
1722 rfu-loopback-active Alarm Equipment RFU loopback is active Major User has activated RFU Disable RFU loopback.
loopback.
1723 rfu-mode-changed-to- Event Equipment RFU mode changed to Indeterminate
combined Combined
1724 rfu-mode-changed-to-diversity Event Equipment RFU mode changed to Indeterminate
Diversity
Page 59 of 103

1725 rfu-mode-changed-to-main Event Equipment RFU mode changed to Indeterminate

Main
1726 rfu-power-supply-failure Alarm Equipment RFU power supply Major At least one of the RFU's 1. Check the RFU cable
failure power supply voltages is connection.
too low. 2. Replace the RFU.
1727 rx-level-out-of-range Alarm Equipment RFU RX level out of Warning RSL is very low, link is 1. Check antenna alignment
range down. & link planning.
2. Check link settings (TX
power, TX frequency).
3. Check antenna
connections.
4. Replace local/remote RFU.
1728 rx-level-path1-out-of-range Alarm Equipment RFU RX level path1 out Warning 1. Improper installation. 1. Check that the fault is not
of range 2. Fading event. due to rain/multi-path
fading or lack of LOS.
3. Defective RFU.
3. Check antenna alignment.
4. Check antenna
connections.
Page 60 of 103

1729 rx-level-path2-out-of-range Alarm Equipment RFU RX level path2 out Warning 1. Improper installation. 1. Check that the fault is not
of range 2. Fading event. due to rain/multi-path
fading or lack of LOS.
3. Defective RFU.
3. Check antenna alignment.
4. Check antenna
connections.
1730 radio-unit-communication- Alarm Equipment Radio unit Critical 1. Defective RFU cable. 1. Check RFU power supply.
failure communication failure 2. RFU cable not 2. Check RFU cable and
connected properly. connectors.
3. Defective RIC (Radio 3. Replace RIC (Radio
Interface Card). Interface Card).
5. RFU initialization in
progress.
6. RFU powered off.
1731 power-supply-radio-unit-cable- Alarm Equipment Power supply cable Major Power is enabled but 1. Check RFU cable and
open open consumption is lower connectors.
than threshold. 2. If internal power supply is
not in use disable the
power supply.
Page 61 of 103

1732 power-supply-radio-unit-cable- Alarm Equipment Power supply cable Major 1. Power is enabled but 1. Check RFU cable and
short short consumption reached connectors.
the threshold. 2. Disconnect and Re-
2. Physical short at the Connect the RFU cable.
ETH cable. 3. Extract the RIC-D and re-
insert it.
4. Restart the IDU.
5. Replace the RIC-D card or
the IP-20F IDU.
1733 synthesizer-unlocked Alarm Equipment RFU synthesizer Major At least one of the RFU 6. Replace RFU.
unlocked synthesizers is unlocked 7. In XPIC mode, replace
mate RFU as well.
1734 tx-level-out-of-range Alarm Equipment RFU TX level out of Minor Defective RFU (the RFU 1. Replace RFU.
range cannot transmit the 2. Intermediate solution -
requested TX power) reduce TX power.
1735 tx-mute Alarm Equipment RFU TX Mute Warning RFU Transmitter muted Unmute the RFU transmitter
by user
1736 unknown-rfu-type Alarm Equipment IDU SW does not Major IDC SW does not support Upgrade IDC SW
support this type of RFU the RFU
1737 card-extracted-from-slot Event Equipment Card was extracted from Warning Card was extracted from NA
slot slot
1738 card-failure Alarm Equipment Card is in Failure state Major Card is down as a result of 1. Reset Card.
card failure 2. Check if slot was disabled.
Page 62 of 103

1739 card-fpga-fw-not-found Alarm Equipment FPGA Firmware file not Critical There is no FPGA file NA
found found on the Main Board
for the card on the slot
1740 card-fw-load-fail Alarm Equipment Download card Major Firmware download was 1. Reset Card.
firmware has failed unsuccessful. 2. Download software
package.
3. Try to insert another Card.
1741 card-inserted-to-slot Event Equipment Card was inserted to Warning Card was inserted to slot NA
slot
1742 card-intermediate-channel- Alarm Equipment Card is in Major Card is down as a result of 1. Reset Card.
failure interconnection failure card interconnection 2. Check if the slot was
state failure disabled.
1743 card-missing Alarm Equipment Expected Card is missing Major 1. Card is missing. 1. Insert Expected Card.
in slot 2. Expected Card Type 2. Clear Expected Card Type.
configured on empty
slot.
1744 card-not-supported-for-slot Alarm Equipment This Card type is not Major The card is not on the 1. Reset.
supported in this slot Allowed Card Types list 2. Insert Card belongs to
for this slot. Allowed Card Types list.
1745 card-state-is-down Event Equipment Card operational state is Indeterminate Card state was change to NA
Down Down state
1746 card-state-is-up Event Equipment Card operational state is Indeterminate Card state was change to NA
Up Up state
Page 63 of 103

1747 card-state-is-up-with-alarms Event Equipment Card operational state is Indeterminate Card state was change to NA
Up with Alarms Up state but with Alarms
indication
1748 card-unexpected Alarm Equipment Unexpected Card Type Minor Expected card type is 1. Insert Expected Card.
in slot different than the actual 2. Change Expected Card
card type Type.
1749 slot-disabled Event Equipment Slot was Disabled Indeterminate The user Disabled slot NA
1750 slot-enabled Event Equipment Slot was Enabled Indeterminate The user Enabled slot NA
1751 slot-reseted Event Equipment Card on slot was Reset Indeterminate The user Reset slot NA
1752 fan-card-extraction-event Event Equipment FAN Card was extracted Warning FAN Card was extracted
from slot from slot
1753 fan-card-failure-event Event Equipment FAN failure Major
1754 fan-card-insertion-event Event Equipment FAN Card was inserted Warning FAN Card was inserted to
to slot slot
Page 64 of 103

1755 fan-card-missing Alarm Equipment FAN Card is missing in Critical 1. FAN Card is missing. 1. Insert FAN Card.
slot 2. Slot enabled when 2. Disable slot.
empty.
17562 fan-extreme-temperature Alarm Equipment System Temperature Major 1. Installation 1. Correct the installation
not in allowed range. conditions. conditions.
2. Defective unit. 2. Verify that the product is
3. Defective fan. operating according to
specifications.
3. Replace the fan card.
4. Replace the unit.
1757 fan-failure Alarm Equipment FAN Card is in Failure Major FAN Card is in Failure Change FAN Card
state state
1758 pdc-card-extraction-event Event Equipment Power Supply was Warning Power Supply was Re-Insert the power supply
extracted from slot extracted from slot back into the slot.
1759 pdc-card-insertion-event Event Equipment Power Supply was Warning Power Supply was
inserted to slot inserted to slot.
1760 pdc-card-missing Alarm Equipment Power Supply is missing Major 1. Power Supply is Insert Power Supply.
in slot missing.
2. Slot enabled when
empty.
2
This alarm is only relevant for IP-20 split-mount products.
Page 65 of 103

1761 pdc-over-voltage Alarm Equipment Over voltage Major 1. System power supply 1. Make sure the power
voltage is higher than supply voltage is within
allowed. the specification range.
2. Threshold value is 2. Check the value of the
too low. threshold.
1762 pdc-under-voltage Alarm Equipment Under voltage Major 1. System power supply 1. Make sure the power
voltage is lower than supply voltage is within
allowed. the specification range.
2. Threshold value is 2. Check the value of the
too high. threshold.
1763 TCC-fpga-fw-not-found Alarm Equipment The Main board Warning
firmware is not found
1764 TCC-fw-load-fail Alarm Equipment Download Main Board Major Firmware download was 1. Reset board.
firmware has failed unsuccessful. 2. Download software
package.
3. Try to insert another
board.
1765 tcc-powerup-reset-event Event Equipment Main Board was reset Warning
1766 upload-software-failed Event Equipment RFU installation failure Warning 1. Unsupported RFU 1. Make sure RFU is
type. supported by SW version.
2. IDU-RFU 2. Check IDU-RFU cable.
communications 3. Replace RFU.
problem.
3. RFU failure.
Page 66 of 103

1767 upload-software-started Event Equipment RFU installation in Warning User command

progress
1768 upload-software-succeeded- Event Equipment RFU installation Warning User command
event successfully completed
1770 cable-lof-rfu Event Equipment Unit performing power- Major
up.
1771 cable-error-rfu Alarm Equipment RFU cable error. Major Errors in signal from IDU 1. Check the IF cable and
to XCVR. connectors.
2. Verify that the N-
Type/TNC connector inner
pin is not spliced.
3. Replace RMC.
4. Replace XCVR.
1772 xpic-data-los Alarm Equipment Radio XPIC sync loss Major Signalling between RMCs 1. Check that the RMCs are in
(Radio Modem Cards) for allowed slots.
XPIC functionality has 2. Populate the RMCs in
failed different allowed location
in the chassis.
3. Replace RMC/s.
4. Replace chassis.
1773 early-warning Alarm Communications Radio early warning. Warning The estimated radio BER 5. Check link performance.
(Bit Error Rate) is above 6. Check IF cable, and replace
10E-12. if required.
7. Replace XCVR.
8. Replace RMC.
Page 67 of 103

1774 sw-download-incompatible-rfu Alarm Equipment RFU software download Critical The hardware of the XCVR 1. Upgrade the XCVR
cannot be initiated. is OK, but is it running software application via
with METRO radio XPAND-IP and then
application. reinitiate software
download..
1775 hw-incompatible-rfu Alarm Equipment RFU software download Critical Wrong type of XCVR, the Replace the XCVR
is not possible. XCVR hardware is METRO.
1776 pll-rmc Alarm Equipment RMC hardware failure. Major RMC hardware failure of Replace the RMC.
the clock distributor.
1777 rfu-mute-with-timeout Event Equipment RFU TX Mute with Warning RFU Transmitter muted Unmute the RFU transmitter or
timeout by user. wait for expiration of the
timeout.
1778 rfu-power-decreased-due-to- Alarm Equipment RFU power decreased Major Defective RFU (the RFU 1. Replace RFU.
pa-temp due to PA temperature cannot transmit the 2. Intermediate solution -
requested TX power). reduce TX power.
1780 mrmc-running-script-deleted Event Equipment MRMC running script is Warning New installed software 1. Make sure the required
deleted package does not include software package include
the running MRMC radio the running MRMC radio
script script.
2. Download and install the
correct software package.
1781 mrmc-running-script-updated Event Equipment MRMC running script is Warning New installed software Reset the radio carrier to
updated package does has an reacquire the new updated
updated version of the MRMC radio script
running MRMC radio
script
Page 68 of 103

1782 radio-2_5gbps-mismatch- Alarm Equipment 2.5Gbps mismatch Warning The card can not function Add the card to an ABC group,
configuration configuration outside of an ABC group or change the Slot Section to
in 2.5Gbps mode. 1Gbps.
1783 remote-fault-indication Alarm Communication Radio remote fault Minor
indication (RFI)
1790 np-hw-failure Alarm Equipment Hardware failure Critical An internal hardware Replace the card or unit which
failure has been detected reports hardware failure.
by the system.
1794 interface-not-functional-until- Alarm equipment Interface is not Warning Changes were made to Reset chassis
reset operational until chassis platform due to user
reset configuration
1800 t3-loc-alarm Alarm Equipment T3 sync interface Loss of Major 1. Cable disconnected. 1. Check the cable
Carrier 2. Defective cable. connection.
2. Disable the interface in the
Interface Manager.
1975 radio-fan-failure Alarm Equipment RFU fan failure Major 1. RFU fan is 1. Check fan cable
disconnected. connection to the RFU.
2. RFU fan HW failure. 2. Check/replace the fan.
3. RFU fan jammed. 3. Clear/clean the fan.
Page 69 of 103

1976 second-bbi-hw-support-failure Alarm Equipment RFU2 in the RIC-D Major User is trying to set 1. Replace the TCC-U card
cannot be used in the Interface Type to with a model that supports
selected slot with the "Extension" but the TCC-U RFU2 in slots 7 and 8.
current TCC-U HW model does not support 2. Set the Interface Type to
version using RFU2 in Slot 7 or "Ethernet" or "RFU" to use
Slot 8. TCC-U port 7 or 8 as a
traffic port instead of RFU2
on the RIC-D.
3. Disable the Radio-Unit
admin.
2001 pwe3-pwc-s-card-reset Alarm Equipment TDM-LIC has rebooted Major 1. Recent TDM-LIC card 1. Wait for card to reboot.
and is not in service reset; 2. Reset the TDM-LIC card.
now 2. System malfunction. 3. Replace card.
2002 pwe3-pwc-s-config-mismatch Alarm Equipment TDM-LIC configuration Major System malfunction. 1. Reset the TDM-LIC.
mismatch 2. Reset the Device.
3. Remove the TDM
Configuration and Re-
Configure it again.
2003 pwe3-pwc-s-front-panel-clock- Alarm Equipment Loss of Signal (LOS) on Major Cable is not properly 1. Reconnect cable.
los TDM-LIC's front panel connected. 2. Check line cables.
clock port
4. Reset the TDM-LIC.
2004 pwe3-pwc-s-host-pw-lic-comm- Alarm Equipment Communication with Minor System malfunction 1. Reset the TDM-LIC.
disrupt TDM-LIC is disrupted in 2. Replace card.
Host-Card direction
Page 70 of 103

2005 pwe3-pwc-s-hw-failure Alarm Equipment TDM-LIC hardware Major System malfunction 1. Reset the TDM-LIC.
failure 2. Replace card.
2006 pwe3-pwc-s-pw-lic-host-comm- Alarm Equipment No communication with Major TDM-LIC to Host 1. Reset the TDM-LIC.
disrupt TDM-LIC communication failure. 2. Reset the whole device.
3. Replace card.
2007 pwe3-pws-s-jitter-buffer- Alarm Equipment Jitter-buffer-overrun Major TDM service 1. Check TDM service
overrun alarm on TDM service synchronization failure. configuration across the
network.
2. Check the loop
timing/clock recovery
configuration.
2008 pwe3-pws-s-late-frame Alarm Equipment Late-frame alarm on Warning TDM service failure or Check TDM service
TDM service device synchronization configuration across the
problem. network.
2009 pwe3-pws-s-loss-of-frames Alarm Equipment Loss-of-frames alarm on Major Failure along the network Check network or configuration
TDM service path of TDM service for errors in the network
transport side of the service
2010 pwe3-pws-s-malformed-frames Alarm Equipment Malformed-frames Major 1. Payload size does not Check TDM service
alarm on TDM service correspond to the configuration
defined value.
2. Mismatch in PT value
in RTP header (if
used)
Page 71 of 103

2011 pwe3-pws-s-misconnection Alarm Equipment Misconnection alarm on Major Stray packets with wrong Check TDM service
TDM service RTP configurations are configuration
received and dropped.
2012 pwe3-tdm-port-s-ais Alarm Equipment Alarm Indication Signal Major 1. Cable is not properly 1. Check the cable
(AIS) on TDM-LIC TDM connected. connectivity at both local
port 2. External equipment is and peer interfaces.
faulty. 2. Check external equipment.
3. External equipment is 3. Check configuration of the
not properly external equipment.
configured.
2013 pwe3-tdm-port-s-lof Alarm Equipment Loss Of Frame (LOF) on Major 1. Line is not properly 1. Check the line interface
TDM-LIC TDM port connected. connectivity
2. External equipment is 2. Correct the TDM
faulty. configuration.
3. Configuration 3. Check the equipment that
problem. feeds the system
2014 pwe3-tdm-port-s-lomf Alarm Equipment Loss Of Multi-Frame Major 1. Line is not properly 1. Check the line interface
(LOMF) on TDM-LIC connected. connectivity
TDM port 2. External equipment is 2. Correct the TDM
faulty. configuration.
3. Configuration 3. Check the equipment that
problem. feeds the system
2015 pwe3-tdm-port-s-loopback- Alarm Equipment Loopback on TDM-LIC Warning Loopback enabled. Disable loopback.
alarm TDM port
Page 72 of 103

2016 pwe3-tdm-port-s-los Alarm Equipment Loss Of Signal (LOS) on Major 1. Cable is not properly 1. Check the cable
TDM-LIC TDM port connected. connectivity at both local
2. Cable is faulty; and peer interfaces.
3. External equipment is 2. Check external equipment.
faulty;
4. Defective TDM-LIC.
2017 pwe3-tdm-port-s-rai Alarm Equipment Remote Alarm Minor 1. Cable is not properly 1. Check the cable
Indication (RAI) on connected. connectivity at both local
TDM-LIC TDM port 2. External equipment is and peer interfaces.
2018 pwe3-tdm-port-s-unexpected- Alarm Equipment E1/DS1 Unexpected Warning Line is connected to a 1. Enable relevant port.
signal-alarm signal on TDM-LIC TDM disabled port. 2. Disconnect cable from
port relevant port.
2021 pwe3-pwc-s-ssm-rx-changed Event Equipment SSM received pattern Warning No action is required.
change was discovered
2022 pwe3-stm1oc3-s-excessive-ber- Alarm Equipment Excessive BER on TDM- Major 1. Line is not properly 1. Reconnect line.
alarm LIC STM1/OC3 port connected. 2. Check line cables.
faulty.
4. Power cycle the TDM-LIC.
2023 pwe3-stm1oc3-s-lof-alarm Alarm Equipment Loss Of Frame (LOF) on Major 1. Cable is not properly 1. Check the cable
TDM-LIC STM1/OC3 connected. connectivity at both local
port 2. External equipment is and peer interfaces.
3. Wrong TDM 3. Reset the TDM-LIC.
configuration.
Page 73 of 103

2024 pwe3-stm1oc3-s-loopback- Alarm Equipment Loopback on TDM-LIC Warning STM1/OC3 loopback Disable STM1/OC3 loopback.
alarm STM1/OC3 port enabled.
2025 pwe3-stm1oc3-s-los-alarm Alarm Equipment Loss Of Signal (LOS) on Critical 1. Cable is not properly 1. Reconnect cable.
TDM-LIC STM1/OC3 connected. 2. Check line cables.
port 2. External equipment is 3. Check external equipment.
faulty.
3. Peer Equipment
Configuration
problem.
2026 pwe3-stm1oc3-s-mute- Alarm Equipment SFP is muted on TDM- Warning The SFP interface has Set the interface to mute OFF.
override-alarm LIC STM1/OC3 port been muted.
2027 pwe3-stm1oc3-s-sfp-absent- Alarm Equipment SFP absent in TDM-LIC Critical SFP is not inserted Insert the SFP.
alarm STM1/OC3 port properly.
2028 pwe3-stm1oc3-s-sfp-failure- Alarm Equipment SFP failure on TDM-LIC Critical 1. SFP is not inserted 1. Insert the SFP.
alarm STM1/OC3 port properly. 2. Replace the SFP.
2. Card is faulty. 3. Replace the card.
2029 pwe3-stm1oc3-s-sfp-tx-fail- Alarm Equipment SFP transmit failure on Critical 1. SFP is not inserted 1. Insert the SFP.
alarm TDM-LIC STM1/OC3 properly. 2. Replace the SFP.
port 2. Card is faulty. 3. Replace the card.
Page 74 of 103

2030 pwe3-stm1oc3-s-signal- Alarm Equipment Signal Degrade on TDM- Minor 1. Line is not properly 1. Install SFP properly.
degrade-alarm LIC STM1/OC3 port connected. 2. Reconnect line.
2. SFP is not properly 3. Check line cables.
installed.
3. SFP is faulty.
5. Change Signal Degrade
4. External equipment is Threshold.
faulty
2031 pwe3-stm1oc3-s-slm-alarm Alarm Equipment J0 Trace Identifier Minor 1. J0 misconfiguration. 1. Make sure expected and
Mismatch on TDM-LIC 2. Line is not properly received J0 identifiers
STM1/OC3 port connected. match.
3. SFP is not properly 2. Connect line cables
installed. properly.
4. External equipment is 3. Install SFP properly.
faulty.
2032 pwe3-stm1oc3-s-ssm-rx- Event Equipment SSM pattern received Warning
changed on TDM-LIC STM1/OC3
port changed
2033 pwe3-vc12vt15-s-ais-alarm Alarm Equipment Alarm Indication Signal Minor 1. Cable is not properly 1. Check the cable
(AIS) on TDM-LIC connected. connectivity at both local
VC12/VT1.5 2. Local/Peer and peer interfaces.
Configuration is 2. Check/Correct the
incorrect. configuration at the
local/peer.
Page 75 of 103

2034 pwe3-vc12vt15-s-excessive- Alarm Equipment Excessive BER on TDM- Minor 1. Line is not properly 1. Check the line cables.
ber-alarm LIC VC12/VT1.5 connected. 2. Fix the problem at the
2. External equipment is peer.
faulty. 3. Change the Excessive BER
threshold.
2035 pwe3-vc12vt15-s-loopback- Alarm Equipment Loopback on TDM-LIC Warning Loopback enabled on Disable loopback on TDM-LIC
alarm VC12/VT1.5 TDM-LIC VC12/VC11. VC12/VC11.
2036 pwe3-vc12vt15-s-rcv-plm-alarm Alarm Equipment Payload Mismatch Path Minor Incorrect VC12/VC11 Check/Correct the
(PLM) received on TDM- configuration configuration at the local/peer.
LIC VC12/VT1.5
2037 pwe3-vc12vt15-s-rcv-rdi-alarm Alarm Equipment Remote Defect Minor 1. Alarm exists along 1. Fix the problem along the
Indication (RDI) received the Trail. trail.
on TDM-LIC VC12/VT1.5 2. Cable is not properly 2. Check the cable
connected. connectivity at both local
and peer interfaces.
2038 pwe3-vc12vt15-s-rcv-slm-alarm Alarm Equipment Signal Label Mismatch Minor 1. J2 misconfiguration. 1. Make sure expected and
(SLM) received on TDM- 2. Line is not properly receive J2 match
LIC VC12/VT1.5 connected. 2. Reconnect line.
3. External equipment is 3. Check line cables.
2039 pwe3-vc12vt15-s-signal- Alarm Equipment Signal Degrade on TDM- Minor 1. Line is not properly 1. Reconnect line.
degrade-alarm LIC VC12/VT1.5 connected. 2. Check line cables.
faulty.
Page 76 of 103

2040 pwe3-vc12vt15-s-unequipped- Alarm Equipment Unequipped on TDM-LIC Minor 1. Incorrect line is 1. Reconnect line.
alarm VC12/VT1.5 connected. 2. Check line cables.
faulty or
misconfigured.
2041 pwe3-card-group-s-config- Alarm Equipment TDM-LIC card protection Major The configuration Apply a copy-to-mate
mismatch configuration mismatch between the TDM-LIC command to copy the
card protection members configuration from the
is not aligned required TDM-LIC to the other
one
2042 pwe3-card-group-s-lockout Alarm Equipment TDM-LIC card protection Minor The user has issued a Clear the lockout command
group lockout command lockout command
is on
2043 pwe3-card-group-s-no-mate Alarm Equipment A member of TDM-LIC Minor TDM-LIC card is not Install the missing TDM-LIC
card protection group is installed in the shelf card
missing
2044 pwe3-card-group-s-protection- Event Equipment TDM-LIC card protection Warning 1. LOS alarm on a STM1 1. Check line cables.
switch-evt switch over, priority interface of the TDM- 2. Enable the TDM-LIC card
LIC card protection protection group member
group member; or insert the missing card
2. A TDM-LIC card into the shelf.
protection group
member was disabled
shelf
Page 77 of 103

2045 pwe3-vc12vt15-s-lop-alarm Alarm Equipment Loss Of Pointer (LOP) Minor 1. Timing not 1. Correct the timing
received on TDM-LIC configured correctly. configuration.
VC12/VT1.5 2. End-to-end timing is 2. Correct the end-to-end
not synchronized. timing problem.
3. External Equipment is 3. Check the external
faulty. equipment.
4. Network service 4. Fix the network service
connectivity problem. problem.
5. Lower layer problem. 5. Fix the interface and card
problem.
2046 pwe3-tunnel-groups-s- Event Equipment Path protection switch Minor 1. Failure along service 1. Check errors along primary
protection-switch on TDM service primary path. path
2. User command. 2. Check local service
configuration.
2047 pwe3-tunnel-groups-s- Event Equipment Path protection Minor Primary path has been -
revertive-switch revertive switch on TDM operational for the
service duration of the defined
WTR time
2100 STM-1-OC-3-IN-LOS Alarm Equipment Loss of Signal on Line Critical 1. Line is not properly 1. Reconnect line.
Interface (LOS) on STM- connected. 2. Check line cables.
1/OC-3 port. 2. External equipment is 3. Check external equipment.
faulty.
2101 STM-1-OC-3-IN-LOF Alarm Equipment Loss of Frame on Line Major 1. Line is not properly 1. Reconnect line.
Interface (LOF) on STM- connected. 2. Check line cables.
1/OC-3 port. 2. External equipment is 3. Check external equipment.
faulty.
Page 78 of 103

2102 STM-1-OC-3-IN-MSAIS Alarm Equipment Alarm Indication Signal Minor 1. Line is not properly 1. Reconnect line.
on Line Interface (MS- connected. 2. Check line cables.
AIS/AIS-L) received. 2. External equipment is 3. Check external equipment.
faulty.
2103 STM-1-OC-3-IN-MSRDI Alarm Equipment Remote Defect Minor External equipment is 1. Reconnect line.
Indication on Line faulty. 2. Check line cables.
Interface (MS-RDI/RDI-
L) received.
2104 STM-1-OC-3-RX-LOS Alarm Equipment Loss of STM-1/OC-3 Major 1. All channels in Multi 1. Check link performance.
Frame on Radio Carrier ABC group are 2. Check radio alarms for
Interface. down. channel.
2. Incorrect 3. Check configuration.
configuration on
remote side.
2105 STM-1-OC-3-RX-MSAIS Alarm Equipment MS-AIS/AIS-L on Radio Minor 1. Remote STM-1/OC-3 Check remote equipment.
Interface detected. signal is missing
(LOS/LOF/MS-
AIS/AIS-L on remote
STM-1/OC-3
interface).
2. STM-1/OC-3 Channel
removed due to
reduced radio
capacity on remote
side.
2106 STM-1-OC-3-RX-RDI Alarm Equipment MS-RDI/RDI-L on Radio Minor External equipment is Check remote equipment.
Interface detected. faulty.
Page 79 of 103

2107 STM-1-OC-3-LOOPBACK Alarm Equipment STM-1/OC-3 Loopback Warning Looping. Remove looping.
2108 STM-1/OC-3-CHANNEL-1- Alarm Equipment STM-1/OC-3 Channel Warning 1. Reduced capacity. 1. Check link performance.
REMOVED Removed alarm (due to 2. Fading 2. Check radio alarms for
reduced radio capacity). channel.
2109 STM-1-OC-3-PBRS-INSERTION Alarm Equipment PRBS insertion. Warning PRBS insertion on STM- Remove PRBS insertion.
1/OC-3 card.
2110 STM-1-OC-3-SFP-NOT- Alarm Equipment SFP absent in STM- Critical 1. SFP is not properly 1. Install SFP properly.
DETECTED 1/OC-3 port. installed. 2. Replace the card.
2. SFP is faulty.
2111 STM-1-OC-3-SFP-TX-FAILURE Alarm Equipment SFP Transmit Failure on Critical 1. SFP is faulty. 1. Replace SFP or insert SFP if
STM-1/OC-3 port. it is not inserted correctly.
2. Replace the card.
2112 STM-1-OC-3-SFP-TX-MUTED Alarm Equipment SFP is muted on STM- Warning SFP is muted by Remove muting.
1/OC-3 port. configuration.
REMOVED Removed alarm (due to 2. Fading. 2. Check radio alarms for
Page 80 of 103

2120 STM1-OC3-GROUP-ACTIVITY- Event Equipment STM-1/OC-3 Group Warning 1. LOS alarm on an 1. Check line cables.
CHANGED protection switchover STM-1/OC-3 2. Check external equipment.
interface.
2. STM1-OC3 Group
protection group
member was disabled
shelf.
Page 81 of 103

2200 MC-ABC-Local-LOF Alarm Communications Multi Carrier ABC LOF. Critical All channels in Multi 1. Check link performance on
Carrier ABC group are all radio channels in Multi
down. Carrier ABC group.
2. Check radio alarms for
channels in Multi Carrier
ABC group.
3. Check configuration of
Multi Carrier ABC group.
2201 MC-ABC-local-cap-below Alarm Multi Carrier ABC Major 1. One of the radio 1. Check link performance on
bandwidth is below the channels in the Multi all radio channels in Multi
threshold Carrier ABC group has Carrier ABC group
a lower capacity than 2. Check radio alarms for
expected channels in Multi Carrier
2. Minimum bandwidth ABC group
threshold 3. Check configuration of
configuration is Multi Carrier ABC group
wrong Minimum bandwidth
threshold
2203 MC-ABC-Lvds-Error-Sl2 Alarm Equipment LVDS RX Error Slot 2. Major Hardware failure between 1. Replace RMC.
RMC and TCC cards. 2. Replace TCC.
3. Replace chassis.
3. Replace chassis.
Page 82 of 103

3. Replace chassis.
3. Replace chassis.
3. Replace chassis.
3. Replace chassis.
3. Replace chassis.
3. Replace chassis.
3. Replace chassis.
Page 83 of 103

3. Replace chassis.
2213 MC-ABC-robustness-member- Alarm Equipment MC-ABC member has Major The corresponding MC- Verify the proper functioning
disabled been disabled due to ABC member has been and connectivity of the cable
robustness reason temporarily disabled and RF unit.
within the group. It was
caused by consecutive
RFU HW failures
2219 MC-ABC-Ch-Id-Mismatch-Ch1 Alarm Equipment Multi Carrier ABC Warning Configuration failure. Compare Channel ID
Channel Id Mismatch configuration with remote side.
Ch1.
Ch2.
Ch3.
Ch4.
Ch5.
Page 84 of 103

Ch6.
Ch7.
Ch8.
Ch9.
Ch10.
2235 MC-ABC-Ch-Id-Disabled-Ch1 Alarm Equipment Multi Carrier ABC Warning Admin state for channel is Enable admin state for
Channel Id Manual down. channel.
Disabled Ch1.
Disabled Ch2.
Disabled Ch3.
Page 85 of 103

Disabled Ch4.
Disabled Ch5.
Disabled Ch6.
Disabled Ch7.
Disabled Ch8.
2250 CRB-Group-Entity Alarm communications Enhanced Multi Carrier Critical All channels in Enhanced 1. Check link performance on
ABC LOF Multi Carrier ABC group all channels in Enhanced
are down Multi Carrier ABC group.
2. Check alarms for channels
in Enhanced Multi Carrier
ABC group.
3. Check configuration of
Enhanced Multi Carrier
ABC group.
Page 86 of 103

2300 protection-configuration- Alarm Equipment Protection configuration Major The configuration Apply copy-to-mate command
mismatc mismatch! between the protected to copy the configuration from
devices is not aligned. the required device to the
other one.
2301 protection-copytomate-started Event Processing Copy to mate started Indeterminate The copy-to-mate This is a notification
command has just begun!
2302 protection-copytomate- Event Processing Copy to mate Indeterminate The copy-to-mate This is a notification
completed completed command was
completed.
3000 chassis-reset-event Event Equipment Chassis was reset Warning User issued a command Wait until the reset cycle is
to reset the chassis. ended and the system is up
and running.
3001 10gbps-mode-front-panel- Alarm Equipment Reset chassis to activate Warning Front panel Ethernet Reset chassis.
ports-unavailable front panel Ethernet ports cannot work when
ports slot 12 is configured in
10Gbps mode.
3002 slot-mode-front-panel-ports- Alarm Equipment Front panel Ethernet Warning Front panel Ethernet port Configure the relevant capacity
not-functional port cannot function in cannot work in a mode mode to 1 Gbps mode.
current configured other than 1Gbps.
capacity mode
3003 abc-mode-not-functional Alarm Equipment Multi Carrier ABC group Warning Multi Carrier ABC group Configure the relevant capacity
is not functional in does not support the mode to 1 Gbps mode.
current configured configured capacity
capacity mode mode.
Page 87 of 103

3004 abc-mode-not-functional-until- Alarm Equipment Multi Carrier ABC group Warning Multi Carrier ABC group Reset chassis.
reset is not functional in capacity mode is different
current configured than the configured
capacity mode until capacity mode.
chassis is reset
4000 hw-failure Alarm Equipment Card has one or more Critical One or more HW faults. Replace card.
HW failures
4001 slotsection-2_5gbps- Alarm Equipment Card can not function in Warning The user set an expected Change the Slot Section to
compatibility 2.5Gbps mode. card that does not 1Gbps.
support 2.5Gbps.
4002 slot-slotsection-10gbps-card- Alarm Equipment Card is not functional Warning Slot is not in 10Gbps Reset chassis.
not-functional until chassis is reset mode.
5000 failure-login-event Event Equipment User blocked due to Indeterminate User blocked due to The user should wait few
consecutive failure login consecutive failure login minutes until it account will be
unblock
5001 g8032-protection-switching- Alarm Processing ERPI is either in Minor Either link failure Fix the broken link in the ring
alarm protection state or happened in the ring or or release the force/manual
forced protection state force/manual command is command.
active.
5002 g8032-failure-of-protocol-pm- Alarm Processing More than a single RPL Warning RPL configuration is Reconfigure the RPL
alarm is configured in a ring wrong. configuration.
5003 lldp-topology-change Event Processing LLDP topology change Warning New neighbor None
5004 security-log-upload-started- Event Equipment Security log upload Indeterminate Security log upload
event started started
Page 88 of 103

5005 security-log-upload-failed- Event Equipment Security log upload Indeterminate Security log upload failed
event failed
5006 security-log-upload-succeeded- Event Equipment Security log upload Indeterminate Security log upload
event succeeded succeeded
5010 force-mode-alarm Alarm Equipment System is in sync force Warning User command
mode state
5011 sync-quality-change-event Event Equipment The sync-source quality Major
level was changed
5012 system-clock-in-holdover-mode Alarm Equipment System Synchronization Critical Active Sync Source Failure Fix the Sync Source Failure.
Reference in Holdover and the clock unit enters Provide an alternative sync
Mode holdover mode source.
5013 sync-T0-quality-change-event Event Equipment System sync reference Major
T0 quality has changed
5014 sync-pipe-invalid-interface- Alarm Equipment The pipe interface clock- Major For interfaces of a Pipe, Set the outgoing clock source
clock-source source in signal- the outgoing clock source type to System Clock in the
interface table is not type must be "System Outgoing Clock Table via
system-clock Clock". Outgoing Clock view in the
Web EMS or the platform sync
interface config command in
the CLI.
5015 sync-pipe-missing-edge Alarm Equipment The pipe is missing an Major Pipe Regenerator Configure a second interface
edge interface contains less than 2 for the Pipe Regenerator.
interfaces.
Page 89 of 103

5016 sync-pipe-interface-op-state- Alarm Equipment Pipe interface Major One or both of the 1. Check both interfaces of
down operational state is Regenerator Interfaces the pipe regenerator -
down status is down. admin and operational
statuses.
2. Check Ethernet cable
communication.
3. Make sure Radio Link is up.
5017 sync-pipe-invalid-pipe Alarm Equipment Pipe is invalid Major Pipe Regenerator 1. Fix the Pipe Regenerator
configuration is invalid or configuration.
interface operational 2. Ensure both interfaces are
failure. operational.
5018 sync-1588-tc-not-operational Alarm Equipment 1588TC is not Major System Failure Reboot the unit
operational
5019 sync-1588-tc-not-calibrated Alarm Sync 1588TC over the radio is Major 1588TC over the radio is Check that the radio link
not calibrated enabled but could not be configuration have:
calibrated 1. TC enabled on both sides
2. Frequency lock UP on both
sides
3. TC downstream at one
side and upstream on the
other side
5020 sync-T3-remote-loopback Alarm Equipment T3 interface at loopback Warning T3 Interface is configured If required, disable the
mode in loopback. loopback.
5021 sync-T4-analog-loopback Alarm Equipment T4 interface at loopback Warning T4 Interface is configured If required, disable the
mode in loopback. loopback.
Page 90 of 103

5030 soam-connectivity-failure Alarm Processing A connectivity failure in Minor Wrong link Check the link in the traffic
MA/MEG configurations. path
5031 soam-def-error-failure Alarm Processing Error CCM received Major 1. Invalid CCMs has 1. Check the links along the
been received. traffic path.
2. MEP Id does not exist 2. Check the configuration of
or a wrong interval the MEPs.
was received in the
CCM.
5032 soam-def-mac-failure Alarm Processing Remote mep MAC Minor Remote MEP’s associated Check remote Port Interface
status not up MAC is reporting an error status
status
5033 soam-def-rdi-failure Alarm Processing Mep Rdi received Minor Remote Defect indication 1. Check the SOAM
has been received from configurations.
remote MEP 2. Check that all local MEPs
are configured correctly
and enabled.
3. Check the service
connectivity.
5034 soam-remote-ccm-failure Alarm Processing Remote mep CCMs are Major The MEP is not 1. Check all the remote
not received receiving CCMs from at SOAM configurations.
least one of the remote 2. Check that all remote
MEPs MEPs are configured
correctly and enabled.
3. Check the service
connectivity.
Page 91 of 103

5035 soam-def-xcon-failure Alarm Processing Cross Connect CCM Major CCM from another MAID Check MA/MEG and MEP
received or lower MEG level have configurations
been received
5036 ptp-stream-state-change Event Processing 1588-BC port state Warning
changed
5037 ptp-bmca-update Event Processing 1588-BC BMCA has Warning
been updated.
5038 ptp-output-squelch Event Processing 1588-BC outputs are Warning
squelched.
5039 ptp-parent-data-set-change Event Processing 1588-BC parent dataset Warning
has changed.
5040 ptp-utc-offset-change Event Processing 1588-BC UTC offset Warning
value changed.
5041 ptp-leap-seconds-flag-change Event Processing 1588-BC one of the leap Warning
seconds flags have
changed.
5042 ptp-message-interval-change Event Processing 1588-BC message Warning
interval change
detected.
5043 ptp-message-rate-announce Alarm Processing 1588-BC announce Major Misconfiguration of the Check the message rate
message rate is below peer system. configuration of the peer
expected. system.
5044 ptp-message-rate-sync Alarm Processing 1588-BC sync message Major Misconfiguration of the Check the message rate
rate is below expected. peer system. configuration of the peer
system.
Page 92 of 103

5045 ptp-message-rate-delay-req Alarm Processing 1588-BC delay request Major Misconfiguration of the Check the message rate
message rate is below peer system. configuration of the peer
expected. system.
5046 ptp-no-syncE Alarm Processing 1588-BC performance is Critical Loss of system clock Restore the system clock
degraded due to loss of reference. synchronization to a PRC-
system clock reference. traceable source.
5047 soam-csf-rdi-alarm Alarm Processing Auto-state-propagation Major Remote system triggered Resolve the problem on the
indication received auto-state-propagation .remote system.
5048 lacp-port-out-of-sync-alarm Alarm processing LACP port out of Major LACP port was not Resolve the problem on the
collecting-distributing selected by the remote system
aggregator or partner is
out of sync
5100 mkey-mismatch Alarm Equipment Master key mismatch Critical Master Key was not set Verify the Master Key.
cross over the link correctly.
5101 mkey-no-exist Alarm Equipment No Master Key set, Warning Crypto module has been Set the Master Key.
default value used enabled, but no Master
Key has been loaded.
5102 general-encryption-failure Alarm Equipment Payload Encryption Critical 1. Radio LOF on Tx/Rx 4. Validate the MSE on both
failure direction. sides of the link.
2. The session key does 5. Validate the session key on
not match across the both sides of the link.
link. 6. Validate the AES admin
3. The AES admin setting on both sides of
setting does not the link.
match across the link.
Page 93 of 103

5104 kep-initiated Event Equipment Key Exchange Protocol Indeterminate

in progress, Traffic has
been blocked
5105 kep-remote-initiated Event Equipment Key Exchange Protocol Indeterminate
initiated by remote side
5107 bypass-self-test-alarm Alarm Equipment FIPS Bypass Self-Test Critical Disk failure
failed
5108 post-fail-alarm Alarm Equipment Power On Self-Test Critical System failure 1. Reboot the unit.
Failed 2. Check for faults.
3. Replace unit
5109 main-board-non-fips-alarm Alarm Equipment Main Board is not FIPS Critical Main Board used is not Use a FIPS-certified TCC.
certified FIPS certified
5110 radio-non-fips-alarm Alarm Equipment Radio card is not FIPS Major Radio Card used is not Use a FIPS-certified RMC.
certified FIPS certified
5111 aes-self-test-fail-alarm Alarm Equipment Radio crypto module fail Critical FIPS Radio Encryption Use different FIPS supported
Self-Test failed radio card
5112 hw-not-supported-alarm Alarm Equipment Radio Encryption not Major No Payload Encryption Insert suitable Activation Key
supported Activation Key inserted and reboot the unit
5113 ipsec-pre-shared-key-alarm Alarm Equipment IPSec Pre-Shared Key Major IPSec Pre-Shared Key was Configure the IPSec Pre-Shared
has the default value not configured Key to a different value than
the default
5132 security-certificate-download- Event Security Security certificate Indeterminate Security certificate N/A
success-event download succeeded download succeeded
Page 94 of 103

failed-event download failed download failed
started-event download started download started
5222 security-csr-upload-success- Event Security Security CSR upload Indeterminate Security csr upload N/A
event succeeded succeeded
5223 security-csr-upload-failed- Event Security Security CSR upload Indeterminate Security csr upload failed N/A
event failed
5224 security-csr-upload-started- Event Security Security CSR upload Indeterminate Security csr upload N/A
event started started
30007 Clock-source-sharing-failure- Event Equipment Clock source sharing Critical 1. Faulty coaxial cable 1. Try re-initiation of MIMO.
event failure between master and If still fails:
slave RFUs. 2. Replace faulty coaxial
2. Hardware failure in cable and reset Master
Master RFU. RFU.
3. Hardware failure in 3. Replace faulty RFU.
Slave RFU.
Page 95 of 103

31000 Insufficient-conditions-for- Alarm Equipment Insufficient conditions Critical 1. Insufficient 1. Make sure all cables
MIMO-alarm for MIMO conditions for MIMO. between master and slave
2. Hardware failure. are connected (MIMO 4x4
only).
3. In FIPS mode or IPsec
mode, a mismatch 2. Replace faulty units and
between the IPsec check that cables are
pre-shared keys plugged.
configured on the 3. If IPsec/FIPS is enabled,
two units. verify the same pre-shared
key is configured on both
units.
31003 Unsuitable-hardware-for- Alarm Communications Unsuitable hardware for Critical 1. Unsuitable hardware Make sure both RFUs are
MIMO-alarm MIMO for MIMO operation compatible for MIMO
requirements. operation.
2. Dual carrier RFUs
(MIMO 2x2 and 4x4).
3. RFUs with MIMO bus
interface (MIMO
4x4).
4. Clock source sharing
capability (MIMO
4x4).
Page 96 of 103

31004 Unsuitable-software- Alarm Communications Unsuitable software Critical 1. Not all MIMO carriers 1. Load same MIMO
configuration-for-MIMO-alarm configuration for MIMO are set to same radio compatible radio script to
script or script is not all MIMO carriers.
compatible for 2. Set same TX and RX
MIMO. frequency on all MIMO
2. Radio TX and RX carriers.
frequency is not 3. Disable XPIC, Multi radio
identical on all MIMO and ATPC on all MIMO
carriers. carriers.
3. XPIC or Multi radio or
ATPC features are
enabled.
31005 Clock-source-sharing-failure- Alarm Equipment Clock source sharing Critical 1. Faulty coaxial cable 1. Replace faulty coaxial
alarm cable unplugged between master and cable and reset Master
slave RFUs RFU.
2. Mate does not exist 2. Replace faulty RFU.
31100 AMCC-Incompatible-radio- Alarm Communications Radio script is Critical MRMC Script selected Set AFR Script in both Agg1 &
script-alarm incompatible to AMCC does not support AMCC Agg2 carriers
Group type/subtype
31101 AMCC-Inconsistent-MRMC- Alarm Communications Inconsistent MRMC Critical All members of a group Set the members to the
Script-alarm script between must be configured to the appropriate MRMC script
members same MRMC Script
31102 AMCC-Inconsistent-radio- Alarm Communications Inconsistent radio Critical Radio TX/RX frequency is Set same radio TX/RX
frequency-alarm frequency not identical on all AMCC frequency on all AMCC carriers
carriers
Page 97 of 103

31103 AMCC-Failed-To-Load-Alarm Alarm Communications Agg 1 failed Bring-up Critical Agg1 did not complete Drop both Agg1 & Agg2 into
procedure Bring-up successfully single carrier mode (Pre-Init)
31104 AMCC-Invalid-ACM- Alarm Communications Invalid ACM Critical AMCC member have been Set AMCC member to adaptive
Configuration-alarm configuration set to fixed profile ACM profiles
31105 AMCC-Mimo-not-supported- Alarm Equipment AMCC/MIMO Critical 1. MIMO script is not 1. Align MIMO script on all
alarm insufficient condition – enabled on any radio radio members.
configuration is not member. 2. Align same frequency on
supported 2. Different TX/RX all radio members.
frequency. 3. Disable ATPC.
3. ATPC enabled. 4. Disable XPIC.
4. XPIC enabled. 5. Align ACM mode.
5. ACM mode 6. Disable Unit Redundancy.
(adaptive/Fixed) is
7. Replace unit.
not the same.
6. Unit Redundancy
enabled.
7. Platform not
supported.
31106 AMCC-Master-failure-alarm Alarm Equipment AMCC insufficient Critical Master unit failure. 1. Verify Master unit power.
condition – Master unit 2. Replace hardware.
failure.
31107 AMCC-Slave-failure-alarm Alarm Equipment AMCC insufficient Critical Slave unit failure. 1. Verify Slave unit power.
condition – Slave unit 2. Replace hardware.
failure.
Page 98 of 103

31108 AMCC-Data-Sharing-cable- Alarm Equipment AMCC insufficient Critical Data sharing cable failure. 1. Verify Data sharing cable
disconnected-alarm condition – Data sharing connected.
cable failure. 2. Replace Data sharing
cable.
31109 AMCC-Prot-port-cable- Alarm Equipment MIMO insufficient Critical 1. Mate communication 1. Verify Mate
disconnected-alarm condition – Mate cable failure. communication cable
communication cable 2. In FIPS mode or IPsec connected.
failure. mode, a mismatch 2. Replace Mate
between the IPsec communication cable.
pre-shared keys 3. If IPsec/FIPS is enabled,
configured on the verify the same pre-shared
two units. key is configured on both
units.
31110 AMCC-Source-Sharing-cable- Alarm Equipment MIMO insufficient Critical Source sharing cable 1. Verify Source sharing cable
disconnected-alarm condition – Source failure. connected.
sharing cable failure. 2. Replace Source sharing
cable.
31111 AMCC-Master-Slave-config- Alarm Equipment MIMO insufficient Critical Master/Slave Align Master/Slave
mismatch-alarm condition - configuration mismatch configuration.
Master/Slave due to:
configuration mismatch 1. Different TX/RX
frequency.
2. Different MIMO
script ID.
3. Different ACM mode
(adaptive/Fixed).
Page 99 of 103

31112 AMCC-Remote-failure-alarm Alarm Equipment AMCC insufficient Critical AMCC remote failure. Handle AMCC remote failure.
condition – Remote
failure
31113 AMCC-Asd-not-supported- Alarm Radio AMCC/ASD insufficient Critical 1. ASD script is not 1. Align ASD script on all
alarm condition - enabled on any radio radio members.
4. XPIC enabled. 5. Set ACM mode to adaptive
5. ACM mode is not on all radio members.
adaptive on any radio
6. Disable Unit Redundancy.
member.
7. Replace platform.
6. Unit Redundancy
enabled.
7. Platform not
supported.
Page 100 of 103

31114 AMCC-SD-not-supported-alarm Alarm Radio AMCC/SD insufficient Critical 1. SD script is not 1. Align SD script on all radio
condition - enabled on any radio members.
4. XPIC enabled. 5. Align ACM mode.
5. ACM mode 6. Replace RFU.
(adaptive/Fixed) is
not the same.
6. RFU not supported.
31115 AMCC-Data-Sharing-failure- alarm Radio AMCC insufficient Critical Units alignment failure. 1. Verify Source sharing cable
alarm condition - Units connected.
alignment failure. 2. Replace Source sharing
cable.
3. Verify Data sharing cable
connected.
4. Replace Data sharing
cable.
5. Verify using correct SFPs.
Page 101 of 103

31118 AMCC-XPIC-not-supported- alarm Radio XPIC configuration is not Critical 1. XPIC MRMC script is 1. Set XPIC MRMC script
alarm supported not configured 2. Align same frequency on
2. Different TX/RX all radio members.
frequency. 3. Align same ACM mode.
3. ACM mode
(adaptive/fixed) is
not configured the
same.
31119 AMCC-XPIC-remote-failure- alarm Radio XPIC configuration Warning XPIC remote failure Handle XPIC remote failure
alarm failure in remote
31120 AMCC-XPIC-mate- Alarm Communications XPIC communication Warning 1. The mate unit is 1. Check the cable between
communication-failure-alarm with mate unit is unreachable. the two units.
interrupted 2. In FIPS or IPSec 2. In FIPS or IPSec mode,
mode, possible make sure that the same
mismatch between IPSec pre-shared key is
the IPSec pre-shared configured on the two
keys configured on units.
the two units.
31121 AMCC-Radio-unit-failure-alarm Alarm Communications AMCC insufficient Critical Radio Unit failure. 1. Verify radio unit power.
condition - Radio unit 2. Replace HW.
failure.
32000 unit-mgr-undervoltage-alarm Alarm Equipment Under voltage Major System Power Voltage
lower than allowed.
32001 unit-mgr-overvoltage-alarm Alarm Equipment Over voltage Major System Power Voltage
higher than allowed.
Page 102 of 103

32003 unit-mgr-unit-reset-event Event Management Unit was reset. Warning User issued a command Wait until the reset cycle is
to reset the unit ended and the system is up
and running
33001 anti-theft-enabled-event Event Management Anti-Theft Procedures Indeterminate
have been enabled
33002 anti-theft-temporary-disabled- Event Management Anti-Theft Procedures Indeterminate
event have been temporary
disabled
32004 unit-mgr-power-up-event Event Equipment Unit Performed Power Warning
up
33003 anti-theft-sanction-timer- Alarm Management Anti-Theft Sanction Critical Watchdog timer Return the equipment to the
countdown-alarm Mode 24 hours window countdown network
has been triggered
33004 anti-theft-sanction-mode- Alarm Management Anti-Theft Sanction Critical Equipment has been Return the equipment to the
entered-alarm Mode is Active stolen network
Page 103 of 103

IP-20 MIB Reference 11.9.5 Rev AD

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP-20 MIB Reference 11.9.5 Rev AD

Uploaded by

Copyright:

Available Formats

MIB Reference

February 2022 | Rev AD

Open Source Statement

Ceragon Proprietary and Confidential

3. Common tasks ........................................................................................................ 21

Ceragon Proprietary and Confidential

4. MIB Revision History ............................................................................................... 35

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

Table 36: Event Current State MIB Object .............................................................................................33

Ceragon Proprietary and Confidential

About This Guide

Ceragon Proprietary and Confidential

1. Private MIB reference

Table 1: MIB File Names and Versions

MWRM-NETWORK- 1.11.9.5 Networking related OIDs, including Ethernet

Ceragon Proprietary and Confidential

MIB Reference Table in Web EMS

Ceragon Proprietary and Confidential

2. Standard MIB support

2.1 RFC-1213 (MIB II)

2.1.1 System parameters

Table 2: System Parameters

sysDescr Read only A description of the network element.

Table 3: System Object IDs

IP-20 Products 1.3.6.1.4.1.2281.1.20 High capacity packet radio unit

Ceragon Proprietary and Confidential

Product System Object ID SysDescr

IP-20G 1.3.6.1.4.1.2281.1.20.1.3.1 High capacity dual carrier

2.1.3.1 ifTable column supported

Table 4: Supported IfTables

Ceragon Proprietary and Confidential

MIB Name OID Notes

Table 5: Standard IfXtable support

MIB Name OID Notes

2.1.3.3 RMON – etherStatsTable

MIB Name OID Notes

Ceragon Proprietary and Confidential

MIB Name OID Notes

2.1.3.4 RMON – etherStatsHighCapacityTable

Table 6: IfIndex Structure

Function Reserved = 0 Format Format dependent

Table 7: IfIndex “Format” Field Optional Values

2.1.3.6 NG Interface Format

Table 8: NG Interface Format IfIndex Structure

Function Reserved Format Interface Instance/Service Interface Functional Slot Port

Ceragon Proprietary and Confidential

Table 9: IfIndex “Interface Functional Type” Field Optional Values

Ceragon Proprietary and Confidential

Table 10: IfIndex “Slot” Field Optional Values

Table 11: IfIndex “Port/Group” Field Optional Values

2.1.3.7 NG Service Format

Table 12: NG Service Format Ifindex Structure

Bit # 31 (MSB) 30..28 27..24 23..12 11..7 6..4 (LSB) 3..0(LSB)

Ceragon Proprietary and Confidential

IfIndex (32 bit)

Table 13: Service Type

Service Type Value 15..2 1 0

• Service Id – Value from 1 to 4096

2.1.3.8 Calculation of IfIndex

2.1.3.9 IfIndex Examples

Table 14: IfIndex Examples

Functional Type Instance Slot/Port IfIndex (decimal) IfIndex (Hex)

Ceragon Proprietary and Confidential