3CC14055AAAADTBJA-Ed03 00

Site
VIMERCATE
NANTERRE

Originators
G. Gariani
T. Moore
D. Menanteau

LUX50 2.0

System Specification

SNMP Management Interface

Domain
Division
Rubric
Type
Distribution Codes
:
: WTD
:
: Specification
Internal: External:

03 04-12-01 APPLICABLE R. PELLIZZONI G. GARIANI - D. MENANTEAU
02 04-06-30 APPLICABLE R. PELLIZZONI D. MENANTEAU
01 04-02-20 APPLICABLE R. PELLIZZONI G. GARIANI - T. MOORE D. MENANTEAU
ED DATE CHANGE APPROVAL ORIGINATOR

Ed 03 2004/12/01 946LUX50 2.0 -System Specifications - SNMP Management Interface

APPLICABLE

A9400 3CC 14055 AAAA DT BJA

1/ 139

TABLE OF CONTENTS

HISTORY..................................................................................................................................................... 6
REFERENCED DOCUMENTS.................................................................................................................... 7
RELATED DOCUMENTS ........................................................................................................................... 7
PREFACE.................................................................................................................................................... 8
1 INTRODUCTION.................................................................................................................................. 9
1.1 Abbreviations .............................................................................................................................. 9
1.2 Glossary..................................................................................................................................... 10
1.3 Scope.......................................................................................................................................... 10
1.4 Remaining Open Points............................................................................................................ 10
2 OVERVIEW........................................................................................................................................ 11
2.1 Functional Description ............................................................................................................. 11
2.2 Configurations........................................................................................................................... 11
3 EQUIPMENT DOMAIN ...................................................................................................................... 13
3.1 Overview .................................................................................................................................... 13
3.2 Allowed Equipment Types ....................................................................................................... 17
3.2.1 Shelves Equipment Types ................................................................................................... 17
3.2.2 Slots and Sub-slots Equipment Types................................................................................. 18
3.3 Remote Inventory Management............................................................................................... 26
3.4 Equipment Protection Switching Management...................................................................... 27
3.5 External Points Management ................................................................................................... 27
3.6 Management Functions............................................................................................................ 28
3.6.1 Functional Objects Creation................................................................................................. 38
3.7 Supported Objects and Naming Rules ................................................................................... 40
4 TRANSMISSION AND MANAGEMENT INTERFACES (IFTABLE)................................................. 42
4.2 SNMP Tables.............................................................................................................................. 43
4.2.1 Supported objects................................................................................................................ 43
4.3 Naming Rules ............................................................................................................................ 43
5 SDH/PDH TRANSMISSION DOMAIN............................................................................................... 45
6 RADIO DOMAIN ................................................................................................................................ 62
7 SUPPORT DOMAIN........................................................................................................................... 85
7.3 Supported Objects and Naming Rules ................................................................................. 103
8 COMMUNICATION AND ROUTING DOMAIN................................................................................ 107


APPLICABLE


2/ 139

8.1 Functional Description........................................................................................................... 107
8.2 Management Functions.......................................................................................................... 107
9 OVERHEAD DOMAIN ..................................................................................................................... 114
10 TEST DOMAIN............................................................................................................................. 116
11 SDH/PDH PERFORMANCE MONITORING DOMAIN................................................................ 119
12 ALARMS ...................................................................................................................................... 128
12.1 Alarms Provided by Item HW................................................................................................. 128
12.2 Alarms Reported..................................................................................................................... 131
12.2.1 Equipment Alarms ............................................................................................................. 131
12.2.2 Communication Alarms...................................................................................................... 132
12.3 Predefined ASAP Severity ..................................................................................................... 133
APPENDIX A ODU DETAILED CHARACTERISTICS..................................................................... 135
A.1 ODU LX/UX Transceiver 7-8 GHz 4QAM............................................................................... 135
A.2 ODU LX/UX Transceiver 7-8 GHz 16QAM............................................................................. 135
A.3 ODU UX 13 GHz 4QAM with RTPC ........................................................................................ 136
A.4 ODU UX 13 GHz 4QAM without RTPC................................................................................... 136
A.5 ODU UX 13 GHz 16QAM......................................................................................................... 136
A.6 ODU UX 15 GHz standard power........................................................................................... 136
A.7 ODU UX 15 GHz high power................................................................................................... 136
A.8 ODU UX 15 GHz 4QAM with RTPC ........................................................................................ 137
A.9 ODU UX 18 GHz standard power........................................................................................... 137
A.10 ODU UX 18 GHz high power................................................................................................... 137
A.11 ODU UX 23 GHz 4QAM ........................................................................................................... 138
A.12 ODU UX 23 GHz 16QAM......................................................................................................... 138
A.13 ODU UX 25 GHz 4QAM ........................................................................................................... 138
A.14 ODU UX 25 GHz 16QAM......................................................................................................... 138
A.15 ODU UX 38 GHz 4QAM ........................................................................................................... 139
A.16 ODU UX 38 GHz 16QAM......................................................................................................... 139
A.17 ODU UX-Flat 11, 13, 15, 18, 23, 25, 38 GHz........................................................................... 139


APPLICABLE


3/ 139

LIST OF FIGURES

Figure 1 IDU Physical Layout for 1+0 and 1+0L configuration.................................................................. 13
Figure 2 IDU Physical Layout for 1+0 configuration with Service Channels Extension ............................ 13
Figure 3 IDU Physical Layout for 1+1 configuration without Mux Protection ............................................ 13
Figure 4 IDU Physical Layout for IDU 1+1 Mux Protection configurations with access cable .................. 13
Figure 5 IDU Physical Layout for IDU 1+1 Mux Protection configurations with access unit ..................... 14
Figure 6 (1+0) IDU..................................................................................................................................... 14
Figure 7 (1+1) IDU..................................................................................................................................... 14
Figure 8 (1+1) IDU with MUX protection through Access Unit .................................................................. 15
Figure 9 (1+0) ODU................................................................................................................................... 16
Figure 10 (1+1) ODU................................................................................................................................. 16
Figure 11 1+1 Configurations without MUX Protection Functional View................................................... 45
Figure 12 1+1 Configurations with MUX Protection Functional View........................................................ 45


APPLICABLE


4/ 139

LIST OF TABLES

Table 1 Forecast markets, tributaries and modulations ............................................................................ 11
Table 2 Supported Configurations............................................................................................................. 12
Table 3 Shelves Equipment Types............................................................................................................ 17
Table 4 ODU Allowed Equipment Types................................................................................................... 18
Table 5 Allowed board/plug-in types in (1+0) IDU Classic configuration .................................................. 18
Table 6 Allowed board/plug-in types in (1+0) IDU Light configuration...................................................... 19
Table 7 Allowed board/plug-in types in (1+0) IDU with Service Channels Extension configuration......... 19
Table 8 Allowed board/plug-in types in (1+1) IDU configuration............................................................... 20
Table 9 Allowed board/plug-in types in (1+1) IDU with Mux Protection configuration .............................. 21
Table 10 Allowed board types in ODU LX/UX 7-8 GHz ............................................................................ 22
Table 11 Allowed board types in ODU UX 13 GHz................................................................................... 22
Table 16 Allowed board types in ODU UX 38 GH..................................................................................... 24
Table 17 Allowed board types in ODU UX-Flat ......................................................................................... 25
Table 18 Tables and attributes restricted to IDU administrative state control........................................... 25
Table 19 Equipment Protection Schemes................................................................................................. 27
Table 20 Equipment Domain: Functional objects creation........................................................................ 39
Table 21 Equipment Domain: Naming rules.............................................................................................. 41
Table 22 Supported Transmission and Management Interface types in ifTable....................................... 42
Table 23 Transmission and Management Interfaces: Naming rules......................................................... 43
Table 24 Allowed Frame Structure Configurations ................................................................................... 46
Table 25 PDH Tributary objects to be created based on frame structure configuration........................... 46
Table 26 SDH/PDH Transmission Domain: Naming rules........................................................................ 61
Table 27 Radio Protection Switching Scheme characteristics.................................................................. 63
Table 28 Tx Protection Switching Scheme characteristics ....................................................................... 63
Table 29 Radio Transmission Parameters in 1+1 HSB Configuration...................................................... 64
Table 30 Radio Domain: Supported Objects and Naming rules ............................................................... 84
Table 31 Supported Configurations and Labels........................................................................................ 85
Table 32 Feature Key Limitations.............................................................................................................. 86
Table 33 Software Units index and label ................................................................................................... 87
Table 34 Abnormal Conditions Triggering Event Types............................................................................ 87
Table 35 Support Domain: Supported Objects and Naming rules .......................................................... 106
Table 36 Point to Point IP Interfaces Features ....................................................................................... 107
Table 37 Communication and Routing Domain: Supported Objects and Naming rules ......................... 113
Table 38 Overhead Domain: Supported Objects and Naming rules....................................................... 115
Table 39 Test Domain: Supported Objects and Naming rules................................................................ 118
Table 40 Performance Monitoring Point.................................................................................................. 119
Table 41 Performance Monitoring Domain: Supported Objects and Naming rules ................................ 127
Table 42 IDU Alarms ............................................................................................................................... 128
Table 43 IDU/MAIN Alarms ..................................................................................................................... 128
Table 44 IDU/EXT Alarms ....................................................................................................................... 129
Table 45 ODU Alarms ............................................................................................................................. 130
Table 46 Equipment Alarms Reported .................................................................................................... 131
Table 47 Communication Alarms Reported ............................................................................................ 132
Table 48 Predefined ASAP Severity for Communication Alarms............................................................ 133
Table 49 Predefined ASAP Severity for Equipment Alarms.................................................................... 134


APPLICABLE


5/ 139

HISTORY

Date Edition Comments
040220 Ed. 01 It. 00 Changed state to Applicable
040304 Ed. 01 It. 01 - Equipment domain: added an explanation concerning virtual rack
and consequent equipment position numbering
- Overhead domain: added 007 phone number value
040318 Ed. 01 It. 02 - Equipment domain: Replaced Allowed Equipment Type values
with values that are meaningful for the user, as they will appear as
they are in the managers.
- Equipment domain: IDU Main and EXT Position order has
changed (new Melodie policy). IDU Main is now at the top, and
extension at the bottom
040322 Ed. 01 It. 03 - Comm. & Routing Domain: added a restriction on OSPF area stub
flag (read-only & always on)
040426 Ed. 01 It. 04 Equipment Domain, table 21: Added EXT11 case which was
missing for Radio & Tx protection functional objects creation.
040519 Ed. 01 It. 05 - CONbb02777: Equipment Domain: changed Not Provisioned
string to Empty
- Equipment Domain, tables 7, 8 & 9: Changed ESC 4-Wire Audio
and E&Q to ESC 4-Wire Audio and E-Q due to CT restrictions on
& character
040629 Ed. 01 It. 06 - Changed Optics IM version to v2.18
- DCE mode for PPP NMS is now supported
- Split 1+0 configuration in 2: 1+0 classic and 1+0 light
- Split 1+1 HSB configurations in 2: 1+1 HSB SD (2 antennas) &
1+1 HSB (1 antenna)
- Section 3.2: Updated equipment position in tables from this
section so that there is no more ambiguity concerning their actual
value
- Section 4: Update ifIndex values for PPP & LAPD interfaces.
- Section 7 (feature key limitations): Fixed errors on
OutputPowerCh# label in provided examples.
- Section 7 (software management): Fixed an error on software
package handling: once upgraded, software can not be reverted to
previous version
- Appendix A9 & A10: Changed Tx Power limits to 16 & 24 dBm
(only integer values are supported with Melodie equipments)
040630 Ed. 02 It. 00 Changed state to Applicable
041007 Ed. 02 It. 01 - LUX50 Release 2.0
- TSAlo40071 (equipment protection group index: 4 (mux/demux
protection) instead of 1 (mux protection))
- TSAlo40406 (7/8 GHz: 21 dBm instead of 20.5 dBm)
- TSAlo40411 (OSPF area stub flag)
- TSAlo40418 (16QAM & 4x2Mbps)
- TSAlo40424 (loopback indexes & OIDs)
- Added a common frame interface index allowing support of IDU
cable loopbacks & PM on radio link
- Supported ODUs/duplexers: removed 15 GHz / 322 MHz (not
used), added 18 GHz / 1092.5 MHz (China)
- Updated frequency limits in Appendix A (incorrectly rounded)
- TSAlo40866 (updated ifIndexes according to new rules in order to
avoid conflicts between tributary 1 and radio channel 1)
- Aligned document structure with ULS 2.0 SNMP spec structure
- Imported function list tables from Doors extraction


APPLICABLE


6/ 139

041124 Ed. 02 It. 02 Updates after review:
- Removed equalizer inhibition which is no longer supported
- Added explanations on behavior against unrecognized remote
inventories
- Duplexer 1092.5 MHz is for ODU 18 GHz standard power only
- Updated Mux Protection functional view which was incorrect
- Fixed a low BER switching threshold value
- Functions F1.14 & F1.29 from radio domain are partially supported
- Updated max number of abnormal condition entries
- Added precision on loopback restrictions from remote managers
041201 Ed. 03 It. 00 - Appendix A.17: Added reference to UX-Flat 11 GHz which was
missing
- Section 3.2.1: Added an explanation concerning heterogeneous
ODU configurations
- Changed state to Applicable
REFERENCED DOCUMENTS
[1] RFC 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types
RELATED DOCUMENTS
[2] Optics-IM: Communication and Routing Domain (SNMP)
3AL 38806 0000 DSZZA
[3] Optics-IM: Support Domain (SNMP)
3AL 38806 0005 DSZZA
[4] Optics-IM: Equipment Domain (SNMP)
3AL 38806 0013 DSZZA
[5] Optics-IM: SDH/PDH Transmission Domain (SNMP)
3AL 38806 0014 DSZZA
[6] Optics-IM: SDH/PDH Performance Monitoring Domain (SNMP)
3AL 38806 0012 DSZZA
[7] Optics-IM: Radio Domain (SNMP)
3AL 38806 0015 DSZZA
[8] Optics-IM: Test Domain (SNMP)
3AL 38806 0017 DSZZA
[9] Optics-IM: Overhead Domain (SNMP)
3AL 38806 0018 DSZZA
[10] Optics-IM: List of SNMP Events
3AL 38897 0001 DSZZA
[11] Optics-IM: Operator Labels and Naming Rules (SNMP)
3AL 38806 0006 DSZZA


APPLICABLE


7/ 139

PREFACE

This document provides the functional description of SNMP management interface of LUX50 Radio NE
in the scope of Release 2.0.


APPLICABLE


8/ 139

1 INTRODUCTION
1.1 Abbreviations

AIS Alarm Indication Signal
ANSI American National Standards Institute
APT Active Problem Table
ASAP Alarm Severity Assignment Profile
ATPC Automatic Transmit Power Control
AVC Attribute Value Change
BER Bit Error Ratio
BBE Background Block Error
CD Current Data
CLA Common Loss Alarm
DCE Data Circuit-Terminating Equipment
DTE Data Terminal Equipment
EC Equipment Controller
EFD Event Forwarding Discriminator
EOW Engineering Order Wire
EPS Equipment Protection Switching
ES Errored Second
ETSI European Telecommunications Standards Institute
EW Early Warning
FD Frequency Diversity
FE Fast Ethernet
FSO Free Space Optics
HBER High Bit Error Ratio
HD History Data
HET Hetero frequency
HS Hitless Switch
HSB Hot Stand-by
IDU Indoor Unit
IM Information Model
IP Internet Protocol
LAN Local Area Network
LAPD Link Access Procedure on D-channel
LBER Low Bit Error Ratio
LOF Loss Of Frame
LOS Loss Of Signal
MCU Multiplexing and Control Unit
MDU Modulation/Demodulation Unit
MIB Management Information Base
NE Network Element
NMS Network Management system
NSA Not Service Affecting
NTP Network Time Protocol
OC ODU Controller
ODU Outdoor Unit
OFS Out of Frame Second
OH Overhead
OS Operation System
PDH Plesyochronous Digital Hierarchy
PM Performance Monitoring
PPI Plesyochronous Physical Interface
PSU Power Supply Unit
QoS Quality of Service


APPLICABLE


9/ 139

RAI Remote Alarm Indication
RDI Remote Defect Indication
RI Remote Inventory
RPS Radio Protection Switching
RPPI Radio Plesyochronous Physical Interface
SA Service Affecting
SCU Service Channel Unit
SD Space Diversity
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
TCA Threshold Crossing Alarm
TD Threshold Data
TPS Tx Protection Switching
TS Time Slot
TTP Trail Termination Point
UAS Unavailable Second
UAT Unavailable Time
ULS Urban Low capacity Split
URU Underling Resource Unavailable
1.2 Glossary
The following convention is used in the support table of the management functions:
- Y the function is supported
- N the function is NOT supported
- P the function is Partially supported
1.3 Scope
The management functionalities described in this document cover the functionalities of LUX50 NE
supported at SNMP interface in the scope of Rel. 2.0.
This specification relies on existing domain documentation (see Related Documents). The detailed
description of management functions and management information is provided in these documents. The
present specification refers to this generic specification and focuses on their application to LUX50 NE.
1.4 Remaining Open Points
None


APPLICABLE


10/ 139

2 OVERVIEW
946LUX50 NE split mount equipment has the aim to multiplex/demultiplex the main tributaries (16E1/E3)
with two modulation formats (4 and 16 QAM), related to ETSI market.
The table below summarizes the relationship among market, tributaries and modulation.

Market Tributary Modulation
2xE1 4QAM
4xE1 4QAM / 16QAM (note 1)
8xE1 4QAM /16QAM (note 2)
16xE1 4QAM / 16QAM (note 2)
ETSI
1xE3 + 1xE1 4QAM / 16QAM (note 2)
ANSI N/A N/A
Table 1 Forecast markets, tributaries and modulations
(note 1) 16QAM modulation with 4xE1 tributary is available with 16QAM LX/UX ODU and UX-Flat 7/8
GHz ODU only.
(note 2) Modulation type depends upon the ODU model. Excepted for UX-Flat ODU, it can not be
changed dynamically.
The Optics Info Model version to be used with 946LUX50 Release 2.0 NE is V2.20.
2.1 Functional Description
The main functions performed by IDU and ODU of 946LUX50 equipment are the following:
Multiplexer/Demultiplexer
The multiplexer function receives main tributaries (see Table 1) and generates a PDH frame.
The demultiplexer function receives a PDH frame and generates main tributaries.
Signal Protection switch (if any)
The function provides one protection channel for the main signal against channel-associated failures
for both hardware failures and temporary signals degradation or losses due to propagation effects
(e.g. rain) according to equipment configuration.
Radio
The function converts a radio frequency signal into an internal logic level signal, and vice versa
(RPPI). Specifically, the following functions are performed:
Modulation and Tx functions in the transmit side
Demodulation and Rx functions in the receive side
2.2 Configurations
946LUX50 NE can be made up with:
one channel (1+0 configurations);
two channels (1+1 configurations).


APPLICABLE


11/ 139

The 2+0 and N+1 configurations are not supported by this NE.
The table below provides the list of supported configurations.

Configuration Notes Supported
1+0 IDU classic Y
1+0 Light IDU light Y
1+0 with Service Channels
Extension
IDU classic only. IDU extension unit is dedicated to service
channels 3, 4 & 5 extension
Y
1+1 HSB
HSB without Space Diversity, without
multiplexer/demultiplexer protection
Y
1+1 HSB with MUX Protection
HSB without Space Diversity, with
Y
1+1 HSB SD
HSB with Space Diversity, without
Y
1+1 HSB SD with MUX
Protection
HSB with Space Diversity, with multiplexer/demultiplexer
protection
Y
1+1 FD
FD with single/double antenna, with/without different polar,
without multiplexer/demultiplexer protection
Y
1+1 FD with MUX Protection
FD with single/double antenna, with/without different polar,
with multiplexer/demultiplexer protection
Y
Table 2 Supported Configurations


APPLICABLE


12/ 139

3 EQUIPMENT DOMAIN
The NE configuration is described in the Support Domain section.
3.1 Overview
The 946LUX50 NE is made up with two different parts: the indoor and the outdoor part. They are
described hereafter from physical and management point of view.
Indoor Part:
The indoor part is made up with one shelf. This shelf can contain the following units, depending on the
chosen configuration:
Physical Layout: Figures 1 to 5 below provide an overview of the IDU physical layout for all the
available configurations.
IDU Main

Figure 1 IDU Physical Layout for 1+0 and 1+0L configuration
IDU Extension 1+0
(Service Channels)
IDU Main

Figure 2 IDU Physical Layout for 1+0 configuration with Service Channels Extension
IDU Extension 1+1 basic
IDU Main

Figure 3 IDU Physical Layout for 1+1 configuration without Mux Protection
IDU Extension
IDU Main
Access Cable
(with an empty slot)

Figure 4 IDU Physical Layout for IDU 1+1 Mux Protection configurations with access cable


APPLICABLE


13/ 139

IDU Extension
IDU Main
Access Unit

Figure 5 IDU Physical Layout for IDU 1+1 Mux Protection configurations with access unit
Layout from management point of view:
Based on the available IDU physical layouts shown above, Figures 6 to 8 below describe possible IDU
shelf layouts as they will be handled from management point of view.
- (1+0) IDU
- (1+0L) IDU
slot 1: Main Unit
slot 1: Main Unit

Figure 6 (1+0) IDU
- (1+0) IDU with Service Channels Extension
- (1+1) IDU FD
- (1+1) IDU HSB
- (1+1) IDU HSB-SD
slot 1: Main Unit
slot 2: Extension Unit
slot 1: Main Unit

Figure 7 (1+1) IDU


APPLICABLE


14/ 139

- (1+1) IDU FD with Mux Protection
- (1+1) IDU HSB with Mux Protection
- (1+1) IDU HSB-SD with Mux Protection
slot 1: Main Unit
slot 1: Main Unit
(Access Unit)

Figure 8 (1+1) IDU with MUX protection through Access Unit
The layout shown above corresponds to old 1+1 configurations with Mux protection, where tributary
access is realized through an Access unit, which is physically located between main and extension units.
In newer 1+1 configurations with Mux protection, as tributary access is realized through an access cable,
there is no access unit anymore. However, an empty slot can be left between main and extension units.
As access unit is not seen from management point of view, and in order to always use the same slot
number for extension unit, access unit, when present, is not treated as a slot, but is considered instead to
be part of Extension Unit within slot 2.
The Main Unit main functionalities are the following:
- E1/E3 tributaries connection accommodation,
- Multiplexing/demultiplexing function,
- Service channels insertion/extraction,
- Control of and interface with ODU Ch#1,
- Handling of requests coming from a manager (either OS or Craft terminal),
- Equipment management functions,
- Support for Software Key Unit (IDU classic only).
The Main unit is used with both 1+0 and 1+1 configurations.
The Extension Unit main functionalities are the following:
- E1/E3 tributaries connection accommodation for 1+1 configurations with Mux/Demux protection,
- Multiplexing/demultiplexing function for 1+1 configurations with Mux/Demux protection,


APPLICABLE


15/ 139

- Support for service channels 3, 4 & 5. Extension Unit can contain optional daughter-boards
dedicated to service channels 3 & 4 customization,
- Control of and interface with ODU Ch#0.
The Extension unit is used with all 1+1 configurations, as well as with 1+0 with extension configuration.
Outdoor part (ODU)
One single ODU type is managed in the Outdoor part, which is:
- ODU
The ODU type is implicitly defined by the NE configuration. Each ODU contains a control unit. It
implements the ODU Controller functions.
ODU

Figure 9 (1+0) ODU
ODU Ch#1 ODU Ch#0

Figure 10 (1+1) ODU


APPLICABLE


16/ 139

3.2 Allowed Equipment Types
This section provides information on the allowed equipment types for all the configurations supported by
946LUX50 NE.
As a side effect of the definition of the NE configuration, the agent has to create not only all the
structured equipments describing the related physical layout, but also all the contained equipments (slot
and sub-slots) with the related equipmentExpected values, providing this way the whole physical
description of the NE configuration defined.
Note 1: Allowed equipment types
In all tables inside this section, the values to be used in the MIB for allowedEquipmentType,
equipmentExpected and equipmentActual objects are defined in the Allowed Equipment Type column.
An additional column named Shortcut Label is provided, defining a shortcut label for each allowed
equipment type value. For writing convenience and concision, the shortcut labels are used in the rest of
the document when referring to a particular allowed equipment type value. They shall be replaced in the
implementation phase by the corresponding allowed equipment type value.
Note 2: Default value for allowed equipment types
In all tables within this section, when an equipment can be set by the operator, the default value for this
equipment type is indicated by a (*) mark within Shortcut Label column.
3.2.1 Shelves Equipment Types
The table below provides the shelves equipment types allowed for each supported NE configuration
(refer to support domain section for the list of supported configurations).

NE
Configuration
Shelf
positio
n
Allowed Equipment Type Shortcut Label
Eqpt
Expected
Settable
Equipmen
t Label
1+0 IDU 1+0 IDU10
1+0L IDU 1+0 Light IDU10L
1+0EXT
1.1.0.0
IDU 1+0 SC-Extension IDU10EXT
N IDU
all 1+0 1.2.0.0 See ODU Allowed Equipment Types table below Y ODU Ch#1

1+1FD
1+1HSB
1+1HSB-SD
IDU 1+1 IDU11
1+1FD-MP
1+1HSB-MP
1+1HSB-SD-MP
1.1.0.0
IDU 1+1 Mux Protection IDU11MP
N IDU
1.2.0.0 See ODU Allowed Equipment Types table below Y ODU Ch#1
all 1+1
1.3.0.0 See ODU Allowed Equipment Types table below Y ODU Ch#0
Table 3 Shelves Equipment Types


APPLICABLE


17/ 139

The table below provides the list of all allowed ODU Equipment Types:

ODU Allowed Equipment Types for Shelf positions 2 & 3
Allowed Equipment Type Shortcut Label
Empty EMPTY (*)
ODU LX/UX 7-8 GHz 4QAM ODU78G4Q
ODU LX/UX 7-8 GHz 16QAM ODU78G16Q
ODU UX 13 GHz 4QAM RTPC ODU13G4QR
ODU UX 13 GHz 4QAM no RTPC ODU13G4Q
ODU UX 13 GHz 16QAM ODU13G16Q
ODU UX 15 GHz Standard Power ODU15GSP
ODU UX 15 GHz High Power ODU15GHP
ODU UX 15 GHz 4QAM RTPC ODU15G4QR
ODU UX 18 GHz Standard Power ODU18GSP
ODU UX 18 GHz High Power ODU18GHP
ODU UX-Flat ODUUXFLAT
Table 4 ODU Allowed Equipment Types
Note concerning ODU provisioning with 1+1 configurations: ODU Ch#1 and Ch#0 (positions 2 & 3)
equipment types are interdependent. When ODU Ch#1 is provisioned, ODU Ch#0 is automatically
provisioned with the exact same equipment type, even in case of heterogeneous ODU configurations,
e.g. an UX ODU on Ch#1 and an UX-Flat ODU on Ch#0. In this case, UX-Flat ODU on Ch#0 is seen
from management point of view like a basic UX ODU (and therefore with the same characteristics: No
ATPC, fixed modulation, etc).
3.2.2 Slots and Sub-slots Equipment Types
The tables below provide the allowed equipment types for each slot inside each shelf type, and if the
equipment expected value is settable by the operator.
IDU

IDU10
Position Allowed Equipment Type
Shortcut
Label
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
IDU Main 4x2 Mbps MAIN4X2
1.1.1.0
IDU Main 34+2 Mbps MAIN34
Y IDU/MAIN Ch#1
1.1.1.1 IDU Power Supply IDUPSU N IDU/MAIN/PSU Ch#1
1.1.1.2 IDU Fan IDUFAN N IDU/MAIN/FAN Ch#1
1.1.1.3 Software Key Unit IDUSKU N IDU/MAIN/SKU
Table 5 Allowed board/plug-in types in (1+0) IDU Classic configuration


APPLICABLE


18/ 139

IDU10L
Shortcut
Label
Equipment
Expected
Settable
Equipment Label
1.1.1.0 IDU Main Light 4x2 Mbps MAINL N IDU/MAIN Ch#1
Table 6 Allowed board/plug-in types in (1+0) IDU Light configuration

IDU10EXT
Shortcut
Label
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.1.1.0
Y IDU/MAIN Ch#1

1.1.2.0 IDU 1+0 Extension EXT10 N IDU/EXT Ch#0
1.1.2.1 IDU Power Supply IDUPSU N IDU/EXT/PSU Ch#0
1.1.2.2 IDU Fan IDUFAN N IDU/EXT/FAN Ch#0
Empty EMPTY (*)
ESC 64 kbps G.703 ESC64G703
ESC 4-Wire Audio and E-Q ESC4WA
ESC 64 kbps V11 ESC64V11
ESC 9600 or 2x4800 bps V11 ESCDAV11
1.1.2.3
Y IDU/EXT/ESC #3
Empty EMPTY (*)
1.1.2.4
Y IDU/EXT/ESC #4
Table 7 Allowed board/plug-in types in (1+0) IDU with Service Channels Extension configuration


APPLICABLE


19/ 139

IDU11
Shortcut
Label
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.1.1.0
Y IDU/MAIN Ch#1

1.1.2.0 IDU 1+1 Extension Basic EXT11 N IDU/EXT Ch#0
Empty EMPTY (*)
1.1.2.3
Y IDU/EXT/ESC #3
Empty EMPTY (*)
1.1.2.4
Y IDU/EXT/ESC #4
Table 8 Allowed board/plug-in types in (1+1) IDU configuration


APPLICABLE


20/ 139

IDU11MP
Shortcut
Label
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.1.1.0
Y (note 1) IDU/MAIN Ch#1

Empty EMPTY (*)
IDU 1+1 Extension 4x2 Mbps EXT4X2
1.1.2.0
IDU 1+1 Extension 34+2 Mbps EXT34
Y (note 1) IDU/EXT Ch#0
Empty EMPTY (*)
1.1.2.3
Y IDU/EXT/ESC #3
Empty EMPTY (*)
1.1.2.4
Y IDU/EXT/ESC #4
Table 9 Allowed board/plug-in types in (1+1) IDU with Mux Protection configuration
Note 1: IDU/MAIN Ch#1 and IDU/EXT Ch#0 choices are interdependent. Setting of IDU/MAIN Ch#1
value automatically sets the IDU/EXT Ch#0 value accordingly (there is a one to one mapping between
MAIN and EXT based on tributary setup value).


APPLICABLE


21/ 139

ODU
Note: Although the table below provides information for ODU Ch#1 (positions 1.2.*.*) only, exact same
rules apply for ODU Ch#0 (positions 1.3.*.*) as well.

ODU78G4Q ODU78G16Q
Position Allowed Equipment Type Shortcut Label
Equipment
Expected
Settable
Equipment Label
1.2.1.0 ODU Rx Unit ODURX N ODU/RX Ch#1
1.2.2.0 ODU Tx Unit ODUTX N ODU/TX Ch#1
1.2.3.0 ODU Cable Interface Unit ODUCIU N ODU/CIU Ch#1
1.2.4.0 ODU Power Supply Unit ODUPSU N ODU/PSU Ch#1
Empty EMPTY (*)
Duplexer 119 MHz LO Inf ODUDUP119I
Duplexer 119 MHz LO Sup ODUDUP119S
Duplexer 151.614 MHz LO Inf ODUDUP151I
Duplexer 151.614 MHz LO Sup ODUDUP151S
1.2.6.0
Other Duplexer ODUDUPOTHER
Y ODU/DUP Ch#1
1.2.7.0 RF Loopback Available ODURFLB N ODU/RFLB Ch#1
Table 10 Allowed board types in ODU LX/UX 7-8 GHz

ODU13G4QR ODU13G4Q ODU13G16Q
Equipment
Expected
Settable
Equipment Label
1.2.5.0 ODU Modem Unit ODUMDU N ODU/MDU Ch#1
Empty EMPTY (*)
1.2.6.0
Y ODU/DUP Ch#1
No RF Loopback ODUNORFLB (*)
1.2.7.0
RF Loopback Available ODURFLB
Y ODU/RFLB Ch#1
Table 11 Allowed board types in ODU UX 13 GHz


APPLICABLE


22/ 139

ODU15GSP - ODU15GHP ODU15G4QR
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.2.6.0
Y ODU/DUP Ch#1
1.2.7.0
Y ODU/RFLB Ch#1

ODU18GSP ODU18GHP
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
Duplexer 1092.5 MHz LO Inf ODUDUP1092I (**)
Duplexer 1092.5 MHz LO Sup ODUDUP1092S (**)
1.2.6.0
Y ODU/DUP Ch#1
1.2.7.0
Y ODU/RFLB Ch#1
Note: (**) Duplexer 1092.5 MHz is supported with ODU 18 GHz Standard Power (ODU18GSP) only. It is
not supported with ODU 18 GHz High Power (ODU18GHP).


APPLICABLE


23/ 139

ODU23G4Q - ODU23G16Q
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.2.6.0
Y ODU/DUP Ch#1
1.2.7.0
Y ODU/RFLB Ch#1

ODU25G4Q - ODU25G16Q
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.2.6.0
Y ODU/DUP Ch#1
1.2.7.0
Y ODU/RFLB Ch#1

ODU38G4Q ODU38G16Q
Equipment
Expected
Settable
Equipment Label
Empty EMPTY (*)
1.2.6.0
Other Duplexer (Note 1) ODUDUPOTHER
Y ODU/DUP Ch#1
1.2.7.0
Y ODU/RFLB Ch#1
Table 16 Allowed board types in ODU UX 38 GH
Note 1: Maximum frequency value can go up to 40 GHz when duplexer choice is ODUDUPOTHER. This
is required in order to be able to cover the special case of 700 MHz duplexers.


APPLICABLE


24/ 139

Although UX-Flat ODU does not physically contain an MDU board, it is handled from management point
of view like any other ODU UX in order to keep a consistent representation between both ODU product
lines. Therefore, ODUUXFLAT contains a fake ODU/MDU Ch#x sub-unit, which supports the
ODUUXFLAT remote inventory.

ODUUXFLAT
Equipment
Expected
Settable
Equipment Label
1.2.6.0 Duplexer UX-Flat ODUDUPUXFLAT N ODU/DUP Ch#1
1.2.7.0 RF Loopback Available ODURFLB N ODU/RFLB Ch#1
Table 17 Allowed board types in ODU UX-Flat
Use of IDU administrative state (c.f. F2-5) for NE configuration
In order to avoid inconsistency between some of the configuration parameters while configuring LUX50
NE, attribute equipmentAdministrativeState from opticsIMEquipmentTable for IDU shelf (position 1) is
used in a specific way in order to provide the NE with information concerning the status of the
configuration:
- When this attribute is set to outOfService, the current configuration parameters are considered to be
inconsistent, therefore indicating to the NE that the configuration should not be applied.
- When this attribute is set to inService, the NE considers that the configuration is complete and
consistent and tries to apply it to the equipment.
The table below provides the list of attributes / objects which can only be changed through this
mechanism:

Table Attribute(s) Domain
-
opticsIMNeConfigurationTypeId
opticsIMNeConfigurationType
Support
opticsIMEquipmentTable
equipmentExpectedTypeId
equipmentExpected
Equipment
Table 18 Tables and attributes restricted to IDU administrative state control


APPLICABLE


25/ 139

3.3 Remote Inventory Management
The Remote Inventory feature allows to store the information useful to identify the components of the
product.
From management point of view the Remote Inventory data is provided by the following equipment
types:
Main Unit (IDU/MAIN)
Extension Unit (IDU/EXT)
Software Key Unit (IDU/SKU)
for ODU types :ODU13G4QR, ODU13G4Q, ODU13G16Q, ODU15GSP, ODU15GHP, ODU15G4QR,
ODU18GSP, ODU18GHP, ODU23G4Q, ODU23G16Q, ODU25G4Q, ODU25G16Q, ODU38G4Q,
ODU38G16Q, ODUUXFLAT:
MDU unit (ODU/MDU)
for ODU types ODU78G4Q and ODU78G16Q:
ODU Rx Unit (ODU/RX)
ODU Tx Unit (ODU/TX)
ODU Cable Interface Unit (ODU/CIU)
ODU Power Supply Unit (ODU/PSU)
For all the other equipment types, the remoteInventoryStatus columnar object assumes that the value is
unavailable.
The information about the equipment type can be read from the remote inventory data (Unit mnemonic
field). All units must provide in their own remote inventory data this kind of information. It is used to
identify the actual equipment type and then, eventually, to raise an equipment mismatch alarm if the
equipment type retrieved from remote inventory data is different from the equipment expected provided
by the managers.
If the Remote Inventory information can not be read from the corresponding unit, a Remote Inventory
alarm is raised.
Behavior in case of unrecognized remote inventory:
When the remote inventory read from a particular unit does not match with the list of remote inventories
recognized by the IDU management software for this unit position, the basic rule concerning IDU
software behavior is to authorize all supported cases, mainly to prevent encountering blocking situations
when performing an upgrade from LUX12/LUX40 to LUX50. Still, a Provisioning Mismatch alarm is
raised on this unit in other to indicate that there is something wrong with it, although this alarm does not
prevent the units operational state to be activated.
Unrecognized Remote Inventory on IDU Main Unit: All NE configurations are authorized (e.g.
configurations with both IDU light and IDU classic. Cf. section 7.1)
Unrecognized Remote Inventory on ODU MDU unit or on ODU CIU unit: All ODU configurations
can be provisioned.


APPLICABLE


26/ 139

Unrecognized Remote Inventory on other units: No specific behavior.
Behavior in case of a provisioned UX-Flat ODU with an unreadable or unrecognized remote
inventory:
When an ODU is provisioned as an UX-Flat ODU, and when the MCU remote inventory is either
unreadable or unrecognized, the frequency and Tx power limits are set so that the entire range of
frequencies (for all frequency bands) and Tx power are authorized. Moreover, Rx frequency becomes
settable, as it is the case when duplexer is provisioned to Other Duplexer.
This specific behavior is due to the fact that in the case of UX-Flat ODUs, Tx power limits, frequency
limits and duplexer shift are deduced from the remote inventory value. Therefore, if these parameters
cannot be deduced from the remote inventory, the widest range of possible values is proposed to the
operator so that he can configure frequency and power by himself.
3.4 Equipment Protection Switching Management

One single EPS protection scheme is supported with all 1+1 MP configurations, covering simultaneously:
the protection for the PDH multiplexer functional block (Tx side)
the protection for the PDH demultiplexer functional block (Rx side)

The following table defines the characteristics of these protection schemes.

Parameter Type Value
Protection group type 1+1
Switching type Single ended
Restoration criteria Always non-revertive
Switching condition Equipment failures
Operator commands Lockout spare
Forced switch from main to spare
Manual switch from main to spare and vice versa
Table 19 Equipment Protection Schemes
The configuration for this protection scheme is performed by the NE in conjunction with the equipment
provisioning process (declaration of boards).
3.5 External Points Management
946LUX50 NE has the capability to monitor 8 input contacts (housekeeping alarms) and 1 output contact
(housekeeping control) through the IDU/MAIN board.
The polarity of each external point can not be configured through the SNMP management interface
(external points polarity is set through hardware swaps on IDU/MAIN MCU board).


APPLICABLE


27/ 139

3.6 Management Functions

The following tables list the Equipment management functions supported in this release (see [4]).

Equipment

Function Equipment
Configuration
SNM
PIf
Function Description
F- 2.1 Request Allowed
Equipment Types
Y This management function allows a managing system to request the
allowed equipment types for each equipment identified by the
associated equipment position. The information available are:
- list of allowed rack types (if the equipment is a rack)
- list of allowed shelves types (if the equipment is a subrack
(shelf))
- list of allowed board types (if the equipment is a slot)
- list of allowed module types (if the equipment is a subslot)
Scope
OPTICSIM-EQPT-MIB: opticsIMAllowedEquipmentTypesTable
Service Used
SNMP-GET on:
- allowedEquipmentTypeIndex
- allowedEquipmentType
F- 2.2 Condition
Equipment Expected
Y This management function allows a managing system to configure
the equipment type expected for an equipment position. This
equipment type is defined setting the identifier
(equipmentExpectedTypeId object) associated to the equipment type
string required (equipmentExpected object). As a side effect of this
operation the agent must set the equipmentExpected object with the
equipment type string associated to this identifier.
The identifier provided must be included in the list of the equipment
types identifiers allowed for that equipment position
(allowedEquipmentTypeIndex object).
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-SET on equipmentExpectedTypeId
F- 2.3 Request Equipment
Expected
equipment type expected for an equipment position. This information
is provided by means of equipment type identifier and associated
string.
Scope
Service Used
SNMP-GET on:
- equipmentExpectedTypeId
- equipmentExpected
Actual
equipment type of the equipment physically present.
Scope
Service Used
SNMP-GET on equipmentActual
F- 2.5 Condition
Administrative State
Y This management function allows a managing system to
suspend/resume the use of an equipment. It applies to equipment
objects representing slots/boards and sub-slots/daughter boards.
Putting an equipment in the outOfService state has the effect that
the functional objects supported by the board are released from any


APPLICABLE


28/ 139

service. Instead, putting an equipment in the inService state has
the effect that the functional objects supported by the board are put
into service.
Scope
Service Used
SNMP-SET on equipmentAdministrativeState
F- 2.6 Request
Administrative State
Y This management function allows a managing system to request
whether the equipment is in or out of service.
Scope
Service Used
SNMP-GET on equipmentAdministrativeState
Note F-2.6: Default value: inService.
F- 2.7 Condition ASAP
Pointer
the ASAP Pointer associated to an equipment position.
Scope
Service Used
SNMP-SET on equipmentAsapIndex
F- 2.8 Request ASAP
Pointer
ASAP Pointer associated to an equipment position.
Scope
Service Used
SNMP-GET on equipmentAsapIndex
Label
label associated to an equipment position.
Scope
Service Used
SNMP-GET on equipmentLabel
F- 2.10 Request Affected
Objects List
N This management function allows a managing system to request the
functional objects which are in operational dependency with an
equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMAffectedObjectListTable
Service Used
SNMP-GET on affectedObjectInstanceId

Function Equipment Status SNM
PIf
Operational State
Y This management function allows the managing system to request
the operational state of an equipment.
Scope
Service Used
SNMP-GET on equipmentOperationalState

Function Equipment
Notifications
SNM
PIf
F- 2.12 Report Equipment
Alarm
Y This management function allows a managed system to report
equipment alarms.
Scope
Service Used
SNMP-TRAP on:


APPLICABLE


29/ 139

- opticsIMAlarmReplaceableUnitProblemRaise
- opticsIMAlarmReplaceableUnitProblemClear
- opticsIMAlarmReplaceableUnitMissingRaise
- opticsIMAlarmReplaceableUnitMissingClear
- opticsIMAlarmReplaceableUnitTypeMismatchRaise
- opticsIMAlarmReplaceableUnitTypeMismatchClear
- opticsIMAlarmUnconfiguredEquipmentPresentRaise
- opticsIMAlarmUnconfiguredEquipmentPresentClear
- opticsIMAlarmFirmwareDownloadOnGoingRaise
- opticsIMAlarmFirmwareDownloadOnGoingClear
- opticsIMAlarmVersionMismatchRaise
- opticsIMAlarmVersionMismatchClear
- opticsIMAlarmInternalCommunicationProblemRaise
- opticsIMAlarmInternalCommunicationProblemClear
- opticsIMAlarmLanFailureRaise
- opticsIMAlarmLanFailureClear
- opticsIMAlarmBatteryFailRaise
- opticsIMAlarmBatteryFailClear
- opticsIMAlarmAndBatteryFailureRaise
- opticsIMAlarmAndBatteryFailureClear
- opticsIMAlarmBackplaneFailureRaise
- opticsIMAlarmBackplaneFailureClear
- opticsIMAlarmReceiverFailureRaise
- opticsIMAlarmReceiverFailureClear
- opticsIMAlarmLowPowerRaise
- opticsIMAlarmLowPowerClear
- opticsIMAlarmStandByVersionMismatchRaise
- opticsIMAlarmStandByVersionMismatchClear
- opticsIMAlarmRemoteInventoryFailureRaise
- opticsIMAlarmRemoteInventoryFailureClear
- opticsIMAlarmRepeaterCableProblemRaise
- opticsIMAlarmRepeaterCableProblemClear
- opticsIMAlarmProvisioningMismatchRaise
- opticsIMAlarmProvisioningMismatchClear

Function Remote Inventory SNM
PIf
F- 2.13 Request Remote
Inventory Data
remote inventory data associated to an equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteInventoryTable
Service Used
SNMP-GET on:
- remoteInventoryStatus
- remoteInventoryCompanyIdentifier
- remoteInventoryMnemonic
- remoteInventoryCLEICode
- remoteInventoryPartNumber
- remoteInventorySoftwarePartNumber
- remoteInventoryFactoryIdentifier
- remoteInventorySerialNumber
- remoteInventoryDateIndentifier
- remoteInventoryDate
- remoteInventoryCustomerField


APPLICABLE


30/ 139

Function Tributary Ports
Impedance
SNM
PIf
F- 2.XX. All the functions. N

Equipment Protection

Function Creation/Deletion SNM
PIf
F- 3.X. All the functions. N

Function Configuration SNM
PIf
Protection Group Type
type of protection (1+1 or 1:N).
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-GET on opticsIMEquipmentProtectionGroupType
F- 3.4 Condition
Equipment Automatic
Restoration Criteria
N This management function allows managing system to control the
automatic restoration criteria from the spare (protecting) equipment
to the main (protected) one when the failure clears.
Scope
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRevertive
Automatic Restoration
Criteria
current automatic restoration criteria: restoration allowed (revertive
mode) or inhibited (non-revertive mode).
Scope
Service Used
SNMP-GET on opticsIMEquipmentProtectionGroupRevertive
Protection Unit Type
type of an equipment protection unit: main (protected) or spare
(protecting).
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
Service Used
SNMP-GET on opticsIMEquipmentProtectionUnitType
F- 3.7 Request Radio
Channel Number
radio channel number (if any) associated to an equipment protection
unit.
Scope
Service Used
SNMP-GET on opticsIMEquipmentProtectionUnitChannelNumber

Function Operator
Commands
SNM
PIf
F- 3.9 Allow/Inhibit Switch
of a Working Equipment
N This management function allows the managing system to
inhibit/allow a working equipment (main) to be switched to a
protection equipment (spare). If the main equipment was already
switched when the Inhibit Switch is requested, it is forced back to the
working position.
This function involves the lockout syntax to inhibit the switch, the
noRequest syntax is used to remove the lockout and allow the


APPLICABLE


31/ 139

switch, both addressed to a main (working) protection unit.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable (on
main protection unit)
Service Used
SNMP-SET on opticsIMEquipmentProtectionUnitSwitchCommand
(lockout or noRequest)
F- 3.10 Allow/Inhibit
Switch of Protection
Equipment
Y This management function allows the managing system to
inhibit/allow a protection equipment (spare) to provide protection in
the protection scheme. If the protection equipment was already
providing protection for a working one when the Inhibit Switch is
requested, then a forced switch is performed back to the working
position.
noRequest syntax to remove the lockout and allow the switch, both
addressed to the spare protection unit.
Scope
spare protection unit)
Service Used
(lockout or noRequest)
F- 3.11 Initiate/Terminate
Manual Switch to
Protection Equipment
initiate/terminate a manual switch from a working equipment to a
protection one. This command will fail if another working equipment
has already been switched when to the protection equipment (only in
case of 1:N) or if the protection equipment has a failure condition.
This function involves the manualSwitch syntax to initiate the switch,
the noRequest syntax to terminate the manual switch, both
addressed to a main protection unit.
Scope
Service Used
(manualSwitch or noRequest)
Manual Switch to a
Working Equipment
initiate/terminate a manual switch from a protection equipment
(spare) to a working one (main). This management function is
applicable only in case of 1+1 not revertive protection type. This
command will fail if the working equipment has a failure condition.
Scope
Service Used
(manualSwitch or noRequest)
Forced Switch to
Protection Equipment
initiate/terminate a forced switch from a working equipment (main) to
a protection one (spare). If another working equipment has already
been automatically or manually switched to the protection one when
the initiate command is received, it is switched back to its working
equipment to allow the other working equipment to be switched to
the protection one.
This function will fail if another protected equipment is already forced


APPLICABLE


32/ 139

switched.
According to the NE type, this function will fail if the protection
equipment has a failure condition.
Scope
Service Used
(forcedSwitch or noRequest)
Forced Switch to a
Working Equipment
N
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the switch, both addressed to the
spare protection unit.
Scope
the noRequest syntax to terminate the switch, both addressed to a
main protection unit.
This management function allows the managing system to
initiate/terminate a forced switch from a protection equipment (spare)
to a working one (main). This management function is applicable
only in case of 1+1 not revertive protection type.
Service Used
(forcedSwitch or noRequest)

Function Protection Status SNM
PIf
Protection Scheme
Operational State
the operational state of an equipment protection scheme.
Scope
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionGroupOperationalState
Protection Status
the current state of an equipment protection unit.
Scope
Service Used
SNMP-GET on:
- opticsIMEquipmentProtectionUnitSwitchCommand
- opticsIMEquipmentProtectionUnitSwitchCriteria
- opticsIMEquipmentProtectionUnitSwitchStatus
Protection Switching
Source
N This management function allows the managing system to request
the source of the equipment switching request. This management
function is applicable only in case of dual ended switching.
Scope
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionUnitSwitchRequestSource
F- 3.18 Report Equipment
Protection Switch Event
N This management function allows the managed system to report any
protection switch event to the managing system, such as:
- protection switching (forced, manual or automatic switch)
- protection release (release of forced, manual or automatic
switch)
- lockout, release lockout.


APPLICABLE


33/ 139

Scope
Service Used
SNMP-TRAP opticsIMProtectionSwitchReporting on:
- opticsIMEquipmentProtectionUnitSwitchCommand
- opticsIMEquipmentProtectionUnitSwitchCriteria
- opticsIMEquipmentProtectionUnitSwitchStatus

External Points

Function Input Point
Configuration
SNM
PIf
F- 4.1 Condition External
Input Point User Label
the user label associated to an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-SET on inputPointUserLabel
F- 4.2 Request External
Input Point User Label
user label associated to an external input point.
Scope
Service Used
SNMP-GET on inputPointUserLabel
Input Point External State
state of an external input point (on when the alarm is raised, off
otherwise).
Scope
Service Used
SNMP-GET on inputPointExternalState
Input Point ASAP Pointer
the ASAP Pointer associated to an external input point.
Scope
Service Used
SNMP-SET on inputPointAsapIndex
Input Point ASAP Pointer
ASAP Pointer associated to an external input point.
Scope
Service Used
SNMP-GET on inputPointAsapIndex
Input Point Polarity
N This management function allows a managing system to configure
the polarity of an external input point.
Scope
Service Used
SNMP-SET on inputPointPolarity
Input Point Polarity
polarity of an external input point.
Scope
Service Used
SNMP-GET on inputPointPolarity


APPLICABLE


34/ 139

Function Input Point Status SNM
PIf
Input Point Operational
State
the operational state of an external input point.
Scope
Service Used
SNMP-GET on inputPointOperationalState

Notifications
SNM
PIf
F- 4.9 Report
Housekeeping Alarm
Y This management function allows a managed system to report an
alarm for a defect detected by an house-keeping interface.
The housekeepingAlarm is the probable cause used.
Scope
Service Used
SNMP-TRAP:
- opticsIMHousekeepingAlarmRaise
- opticsIMHousekeepingAlarmClear

Function Output Point
Configuration
SNM
PIf
Output Point User Label
the user label associated to an external output point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointUserLabel
Output Point User Label
user label associated to an external output point.
Scope
Service Used
SNMP-GET on outputPointUserLabel
Output Point External State
the external state in order to command a remote control interface
(on when the command is raised, off otherwise).
In this way a contact closure interface can be opened or closed, or a
logic level output can be changed to high or low.
Scope
Service Used
SNMP-SET on outputPointExternalState
Output Point External State
external state (on or off).
Scope
Service Used
SNMP-GET on outputPointExternalState
Output Point Criteria
N This management function allows a managing system to condition
the output criteria (manual, automatic or remoteInputPoint). In
automatic control the external points are driven by defined events. In
manual control they are driven by the operator. In remoteInputPoint
the external point is automatically managed by the agent with the
values assumed by the object of the associated remote input point.


APPLICABLE


35/ 139

Scope
Service Used
SNMP-SET on outputPointCriteria
Output Point Criteria
output criteria (manual or automatic). In automatic control the
external points are driven by defined events. In manual control they
are driven by the operator.
Scope
Service Used
SNMP-GET on outputPointCriteria
Note F- 4.14: Only manual criteria is supported
Output Point Polarity
the polarity of an external output point.
Scope
Service Used
SNMP-SET on outputPointPolarity
Output Point Polarity
polarity of an external output point.
Scope
Service Used
SNMP-GET on outputPointPolarity
Output Point Automatic
Event
the event type associated to an output point when the
outputPointCriteria object is set to automatic. This event type is
defined setting the identifier (outputPointAutomaticEventId object)
associated to the event type string required. As a side effect of this
configuration, the agent must set the outputPointAutomaticEvent
object with the vent type string associated to this identifier.
Scope
Service Used
SNMP-SET on outputPointAutomaticEventId
Event
event type associated to an output point when the
outputPointCriteria object is set to automatic.
Scope
Service Used
SNMP-GET on:
- outputPointAutomaticEventId
- outputPointAutomaticEvent
Events List
list of events that can be associated to the external output points
when an automatic management of an output point is active.
Scope
OPTICSIM-EQPT-MIB: opticsIMOutputPointAllowedEventsTable
Service Used
SNMP-GET on outputPointAllowedEvent


APPLICABLE


36/ 139

Status
SNM
PIf
Output Point Operational
State
the operational state of an external output point entry.
Scope
Service Used
SNMP-GET on outputPointOperationalState

Configuration for
Remotization
SNM
PIf

Function Input Point for
Remotization Status
SNM
PIf

Function Input Point for
Remotization Manual
Control
SNM
PIf

Configuration from Remote
Input Point
SNM
PIf

Function Output Point from
Remote Input Point Status
SNM
PIf


APPLICABLE


37/ 139

3.6.1 Functional Objects Creation

The following table defines the functional objects created by the agent when the equipmentExpectedId
object of an equipment entry is set to the value corresponding to the equipment type indicated. This
process is equipment expected value (label) dependent.
As general rule, the creation of the functional objects supported by more boards or daughter boards, is
performed only when all these boards and/or daughter boards have been created. The deletion of these
objects is performed when the first boards and/or daughter boards supporting them is deleted.

When no creation rule is provided, it means that the functional objects have to be created in all the
configurations and for each channel (if applicable).

Equipment
Expected
Functional Objects
Created
Creation Rules
8 opticsIMExternalInputPointEntry
1 opticsIMExternalOutputPointEntry

1 opticsIMLoopbackEntry IDU loopback
MAINL
MAIN4X2
MAIN8X2
MAIN16X2
MAIN34
3 opticsIMPointToPointIPEntry NMS Ports
MAIN4X2
MAIN8X2
MAIN16X2
MAIN34
1 opticsIMEowDTMFTTPBidEntry
1 opticsIMFrameTTPEntry MAINL
MAIN4X2
MAIN8X2
MAIN16X2
MAIN34
EXT4X2
EXT8X2
EXT16X2
EXT34
1 opticsIMCoderTTPEntry
1 opticsIMPdhFrameHopCurrentDataEntry

EXT11 1 opticsIMCoderTTPEntry
1 opticsIMPdhFrameHopCurrentDataEntry

1 opticsIME3pPITTPEntry
1 opticsIME3PathTTPEntry
MAIN34
2 opticsIMLoopbackEntry E3/E1 tributary loopbacks
the last between:
(MAIN4X2 or MAIN8X2 or
MAIN16X2 or MAIN34),
(EXT4X2 or EXT8X2 or
EXT16X2 or EXT34)
[EPS]
1 opticsIMEquipmentProtectionGroupEntry
2 opticsIMEquipmentProtectionUnitEntry
1+1MP => Ch#0
1+1HSB-MP => Ch#0
1+1HSB-SD-MP => Ch#0
the last between:
(EXT11 or EXT4X2 or
EXT8X2 or EXT16X2 or
EXT34),
(ODU*)
[RPS]
1 opticsIMRadioProtectionGroupEntry
2 opticsIMRadioProtectionUnitEntry
[PM]
1 opticsIMPdhFrameLinkCurrentDataEntry
1+1 => Ch#0
1+1HSB => Ch#0
1+1HSB-SD => Ch#0
1+1MP => Ch#0
1+1HSB-MP => Ch#0


APPLICABLE


38/ 139

Equipment
Expected
Functional Objects
Created
Creation Rules
the last between:
(EXT11 or EXT4X2 or
EXT8X2 or EXT16X2 or
EXT34),
(ODU*)
1 opticsIMTxProtectionGroupEntry
2 opticsIMTxProtectionUnitEntry
1+1HSB => Ch#0
1+1HSB-MP => Ch#0
1 opticsIMRadioPDHTTPBidEntry
1 opticsIMRadioFrequencyEntry
1 opticsIMRadioTxPowerEntry
1 opticsIMRadioTxMuteEntry
1 opticsIMRadioAnalogMeasureEntry
1+0
1+0L
1+0EXT
1+1
1+1HSB
1+1HSB-SD
1+1MP
1+1HSB-MP
1+1HSB-SD-MP
ODU*
1 opticsIMLoopbackEntry ODU Loopback
ODURFLB 1 opticsIMLoopbackEntry RF Loopback
Table 20 Equipment Domain: Functional objects creation
Note Concerning Expected Equipment Notation for ODU in the table above:

- ODU* = ODU78G4Q ODU78G16Q ODU13G4QR ODU13G4Q ODU13G16Q ODU15GSP
ODU15GHP ODU15G4QR ODU18GSP ODU18GHP ODU23G4Q ODU23G16Q ODU25G4Q
ODU25G16Q ODU38G4Q ODU38G16Q ODUUXFLAT

- (ODU*) = (ODU78G4Q or ODU78G16Q or ODU13G4QR or ODU13G4Q or ODU13G16Q or
ODU15GSP or ODU15GHP or ODU15G4QR or ODU18GSP or ODU18GHP or ODU23G4Q or
ODU23G16Q or ODU25G4Q or ODU25G16Q or ODU38G4Q or ODU38G16Q or ODUUXFLAT)


APPLICABLE


39/ 139

3.7 Supported Objects and Naming Rules

The SNMP tables (with the columnar objects) and the scalar objects supported by this release are
provided in the following table.

For each table, according to the configuration, the index values of all the supported entries are provided
as well.
The general naming rules for the Equipment objects are defined in [11].

Table Entry
Supported Objects
(Table/Scalar)
Configuration
(note 1)
Description
Index
Value
opticsIMEqptMib
opticsIMEquipmentTable
equipmentExpectedTypeId
equipmentExpected
equipmentActual
equipmentAdministrativeState
equipmentOperationalState
equipmentAsapIndex
equipmentLabel
See the Allowed Equipment Types section.
opticsIMAllowedEquipmentTypesTable
allowedEquipmentType
See the Allowed Equipment Types section.
opticsIMRemoteInventoryTable
remoteInventoryStatus
remoteInventoryCompanyIdentifier
remoteInventoryMnemonic
remoteInventoryCLEICode
remoteInventoryPartNumber
remoteInventorySoftwarePartNumber
remoteInventoryFactoryIdentifier
remoteInventorySerialNumber
remoteInventoryDateIdentifier
remoteInventoryDate
remoteInventoryCustomerField
See the Allowed Equipment Types and
Remote Inventory sections.
opticsIMEquipmentProtectionGroupTable
opticsIMEquipmentProtectionGroupType
opticsIMEquipmentProtectionGroupRevertive
opticsIMEquipmentProtectionGroupOperationalState
1+1 MP EPS 4
opticsIMEquipmentProtectionUnitTable
opticsIMEquipmentProtectionUnitChannelNumber
opticsIMEquipmentProtectionUnitType
opticsIMEquipmentProtectionUnitSwitchCommand
opticsIMEquipmentProtectionUnitSwitchCriteria
opticsIMEquipmentProtectionUnitSwitchStatus
1+1 MP EPS Ch#1
EPS Ch#0
4; 1
4; 0
opticsIMExternalInputPointTable
inputPointUserLabel
inputPointExternalState
inputPointPolarity
inputPointAsapIndex
inputPointOperationalState
All External Input Points 1..8


APPLICABLE


40/ 139

Table Entry
Supported Objects
(Table/Scalar)
Configuration
(note 1)
Description
Index
Value
opticsIMExternalOutputPointTable
outputPointUserLabel
outputPointExternalState
outputPointPolarity
outputPointCriteria
outputPointOperationalState
All External Output
Points
1
opticsIMHousekeepingAlarmRaise
opticsIMHousekeepingAlarmClear
opticsIMAlarmReplaceableUnitProblemRaise
opticsIMAlarmReplaceableUnitProblemClear
opticsIMAlarmReplaceableUnitMissingRaise
opticsIMAlarmReplaceableUnitMissingClear
opticsIMAlarmReplaceableUnitTypeMismatchRaise
opticsIMAlarmReplaceableUnitTypeMismatchClear
opticsIMAlarmUnconfiguredEquipmentPresentRaise
opticsIMAlarmUnconfiguredEquipmentPresentClear
opticsIMAlarmProvisioningMismatchRaise
opticsIMAlarmProvisioningMismatchClear
opticsIMAlarmRemoteInventoryFailureRaise
opticsIMAlarmRemoteInventoryFailureClear
All
Table 21 Equipment Domain: Naming rules
(note 1) Configuration groups:
1+1 MP: 1+1HSB-MP / 1+1HSB-SD-MP / 1+1FD-MP


APPLICABLE


41/ 139

4 TRANSMISSION AND MANAGEMENT INTERFACES (IFTABLE)

The following table defines the transmission and management interfaces types supported and managed
in the ifTable.

ifTable
Interface Type
Interface
Number ifDescr ifType ifSpeed
E1 Port (Tx) up to 16 E1 PPI 18 (note 1) 2048000
E3 Port (Tx) up to 1 E3 PPI 30 34368000
E1 Path (Rx) up to 16 E1 Path 18 (note 1) 2048000
E3 Path (Rx) up to 1 E3 Path 30 34368000
39497142 (1 E3 + 1 E1, 16 E1)
19748571 (8 E1)
9874285 (4 E1)
Radio PDH Frame
(note 2)
up to 3 PDH Radio 1 (other)
4937142 (2 E1)
3 PPP 23 64000
Management interfaces
1 LAPD 77 38400
Table 22 Supported Transmission and Management Interface types in ifTable
(note 1) In IANAifType-MIB the e1 value (19) is declared obsolete. The RFC 2495 (see [1]) doesnt
distinguish between DS1 and E1 and requires to use for the ifType object, the ds1 value (18) for
both these types of interfaces. However this RFC is not included in Optics-IM. Ds1 and E1 signals will
be managed with a proprietary MIB.

(note 2) ifSpeed object is set according to the frame structure configuration.

The ifTable entries will be created by the agent as consequence of the provisioning process (frame
structure and auxiliary channel configuration).

The global number of interfaces (and therefore the value of ifNumber scalar object) depends on the
tributary types and number.

The managing system can request (SNMP-GET) the value of the following ifTable objects:
ifDescr
ifType
ifSpeed

SNMP-SET operation on ifType and ifSpeed objects is not supported.

The managing system can also request (SNMP-GET) the value of the ifNumber scalar object.


APPLICABLE


42/ 139

4.2 SNMP Tables
4.2.1 Supported objects
The Interfaces Group tables, columnar and scalar objects supported by this release are the following:
mib-2
ifTable
ifDescr
ifType
ifSpeed

ifNumber

4.3 Naming Rules

The general naming rule for the transmission interfaces is defined in [11].
The following table provides the relationship between ifIndex value and associated proprietary extension
tables.

N.B. Index values defined below are not related to the configuration. Refer to the corresponding naming
rules sections.

Interface
Type
ifTable
ifIndex
Associated
Mib
Associated
Table
opticsIMRadioTrsPdhMib opticsIMRadioPDHTTPBidTable Radio PDH
Frame
20101
20100
20199
(note 1)
opticsIMRadioTrsCommonMib opticsIMRadioFrequencyTable
opticsIMRadioTxPowerTable
opticsIMRadioAnalogueMeasuresTable
opticsIMRadioTxMuteTable
E1 Port (Tx) 1yy01
1yy99
(note 2)
opticsIME1pPITTPTable
E3 Port (Tx) 10101
10199
(note 2)
E1 Path (Rx) 2zz01
2zz99
(note 3)
opticsIME1PathTTPTable
E3 Path (Rx) 22101
22199
(note 3)
opticsIMTrsCommonMib
PPP-RF 1
PPP-NMS1 2
PPP-NMS2 3
opticsIMCommRouMib opticsIMPointToPointIPTable
LAPD/F 4 - -
Table 23 Transmission and Management Interfaces: Naming rules

(note 1) ifTable ifIndex 20199 is used in case of 1+1 configurations. This is a virtual interface which
purpose is to support all instances which are common to both radio interfaces 20101 and 20100, such as
IDU cable loopback and performance monitoring on a radio link.


APPLICABLE


43/ 139

(note 2) yy = 0116 (nx2Mbps configurations) or yy = 02 (34+2Mbps configurations). The channel
number (01 or 99) depends on the NE configuration: 99 is used with 1+1 MP configurations, 01 in case of
1+0 and 1+1 without Mux protection configurations.

(note 3) zz = 2136 (nx2Mbps configurations) or zz = 22 (34+2Mbps configurations). The channel
number (01 or 99) depends on the NE configuration: 99 is used with 1+1 MP configurations, 01 in case of
1+0 and 1+1 without Mux protection configurations.


APPLICABLE


44/ 139

5 SDH/PDH TRANSMISSION DOMAIN

1+1 Configurations Functional View

<trib>-Port
(sink)
<trib>-Path
(source)
MUX
(source)
Aggregate
(source)
Radio
(source)
Aggregate
(source)
Radio
(source)
Ch#1
Ch#0
Tx Functional View
<trib>-Port
(source)
<trib>-Path
(sink)
DEMUX
(sink)
Aggregate
(sink)
Radio
(sink)
Aggregate
(sink)
Radio
(sink)
Ch#1
Ch#0
Rx Functional View
RPS

Figure 11 1+1 Configurations without MUX Protection Functional View

<trib>-Port
(sink)
<trib>-Path
(source)
MUX
(source)
Aggregate
(source)
Radio
(source)
Aggregate
(source)
Radio
(source)
Ch#1
Ch#0
Tx Functional View
<trib>-Port
(source)
<trib>-Path
(sink)
DEMUX
(sink)
Aggregate
(sink)
Radio
(sink)
Aggregate
(sink)
Radio
(sink)
Ch#1
Ch#0
Rx Functional View
RPS
MUX
(source)
DEMUX
(sink)
EPS
EPS

Figure 12 1+1 Configurations with MUX Protection Functional View


APPLICABLE


45/ 139

The mapping between the functional blocks indicated in the functional views above and SNMP MIB
tables is the following:

<trib>-Port => opticsIME1pPITTPTable
<trib>-Path => opticsIME1PathTTPTable
opticsIME3PathTable
MUX & DEMUX => opticsIMFrameTTPTable
Aggregate => opticsIMCoderTTPTable
Radio => opticsIMRadioPDHTTPBidTable

N.B. SNMP tables are created only if necessary from management point of view.

Frame Structure Configuration
The type and number of PDH interfaces is defined by the F-2.2 function. The allowed frame structure
configuration list depends upon both software key features and IDU Main board type.

Frame Structures Supported by Software Key IDU Main Board
Type 2xE1 4xE1 8xE1 16xE1
MAINL (Note 1)
2x2 Mbits/s
4x2 Mbits/s
MAIN4x2 2x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
MAIN8x2 2x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
8x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
8x2 Mbits/s
MAIN16x2 2x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
8x2 Mbits/s
2x2 Mbits/s
4x2 Mbits/s
8x2 Mbits/s
16x2 Mbits/s
MAIN34 None None None 34+2 Mbits/s
Table 24 Allowed Frame Structure Configurations
Note 1: There is no software key in case of IDU Light. Therefore the only limitation for frame structure
configuration is the MAINL boards limitation, which is 4x2 Mbits/s.
Hereafter, the PDH tributary objects that must be created as a consequence of the frame structure
definition, are provided.

Frame Structure
Configuration
Functional Objects Created
twoE1
fourE1
eightE1
sixteenE1
oneE3
None. Related objects are created when MAIN34 is provisioned,
as there is no operator choice available in this case.
Table 25 PDH Tributary objects to be created based on frame structure configuration
Additionally, for each opticsIME1PathTTPEntry entry created, the associated (internal) loopback object is
created as well.


APPLICABLE


46/ 139

Coder Management
The way coder function is managed with LUX50 is compliant with optics IM definition (i.e. entirely located
in IDU), although it is in reality physically split in two parts, one being located in IDU, the other part being
located in ODU. Consequently, High BER alarm, cable LOS alarm and IDU cable loopback can be
properly attached to IDU. On the other hand, Low BER alarm is attached to opticsIMRadioPDHTTPBid
instead of opticsIMCoderTTP, as defined in reference document [5]. The purpose of this change is to
ensure that Low BER alarm is shown on ODU, which is where it is actually detected with Melodie,
although this is not correct from functional point of view.

Pseudo Random Sequence Insertion

Pseudo random sequence insertion remote control allows insertion of a pseudo random sequence at
transmission into one of the configured tributaries. This control is exclusive among tributaries, e.g. a
pseudo random sequence can be inserted into one single tributary at a time. The consequence of this
behavior is that activation of a pseudo random sequence insertion on a particular tributary automatically
disables previous pseudo random sequence insertion on another tributary, if any. This exclusivity
behavior is true as well between E3 tributary and additional E1 tributary in case of 34+2 Mbps
configuration. When a pseudo random sequence is inserted on a tributary, an abnormal condition is
raised on this tributary.

BER Measurement on tributaries

When a pseudo random sequence is inserted into a particular tributary, and when this tributary is looped
back on the remote NE, the BER value can be measured for this tributary at reception side. The
corresponding entry in BER measure table is automatically created by the NE when pseudo random
sequence insertion is activated, and automatically deleted when pseudo random sequence insertion is
deactivated. BER measures can be collected in the same manner on addition E1 in case of 34+2 Mbps
configuration.

BER Switching thresholds

In case of 1+1 configurations, the following protection switching thresholds on BER measure can be
configured with the following values. The same threshold values apply for both radio channels:

Early Warning BER threshold: 10
-11
, 10
-10
, 10
-9
, 10
-8
, 10
-7
, 10
-6
.
Low BER threshold: 10
-8
, 10
-7
, 10
-6
, 10
-5
, 10
-4
.
High BER threshold: 10
-6
, 10
-5
, 10
-4
, 10
-3
, 5x10
-3
.

The 3 BER threshold values must always comply with the following rule:

Early Warning BER threshold < Low BER threshold < High BER threshold

ASAP Management

The AsapIndex object is not supported on the <trib>PathTTP tables, therefore the severity of the alarms
addressed to instances of these tables must be provided by the ASAP configured on the associated
instance (with the same port identifier) of the corresponding <trib>pPITTP table.

In the same way, the severity of alarms addressed to instances of opticsIMCoderTTPTable must be
provided by the ASAP configured on the associated instance (with the same ifIndex value) of the
opticsIMRadioPDHTTPBidTable.

On the opposite, the severity of alarms addressed to instances of opticsIMFrameTTPTable must be
provided by the ASAP configured on the instance of the opticsIMRadioPDHTTPBidTable related to the
Ch#1.


APPLICABLE


47/ 139


The following table lists the SDH/PDH Transmission management functions supported in this release
(see [5]).

Generic Trail Termination Point Functions

PIf
F- 1.1 Request TTP ASAP
Pointer
ASAP Pointer associated to a trail termination point.
Scope
OPTICSIM-TRS-xxxx-MIB: Trail Termination Point (xTTPBidTable)
Service Used
SNMP-GET on xTTPBidAsapIndex columnar object
F- 1.2 Condition TTP ASAP
Pointer
the ASAP Pointer associated to a trail termination point.
Scope
Service Used
SNMP-SET on: xTTPBidAsapIndex columnar object

Function TTP Status SNM
PIf
F- 1.3 Request TTP
Operational State
the operational state of a trail termination point.
Scope
Service Used
SNMP-GET on xTTPBidOperationalState columnar object

SDH Management Functions

Trail Termination Point

PIf
F- 1.XX All the functions. N

Function Notifications SNM
PIf

Automatic Laser Shutdown

Functions SNM
PIf

PDH Frame Functions

Function Configurations SNM
PIf
F- 2.1 Request Frame
Structure Configuration
the configuration of the frame structure.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMFrameStructureConfiguration


APPLICABLE


48/ 139

Service Used
SNMP-GET on the scalar object
opticsIMFrameStructureConfiguration
F- 2.2 Condition Frame
Structure Configuration
Y This management function allows the managing system to set the
configuration of the frame structure.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMFrameStructureConfiguration
Service Used
SNMP-SET on the scalar object
F- 2.3 Request Link
Identifier Parameters
the value of the parameters related to the Link Identifier
management:
- The expected mode on the receiving NE
(opticsIMLinkldExpectedMode).
If the disabled mode is selected the link identifier mismatch
detection is disabled. If the enabled mode is selected the expected
value is contained in the opticsIMLinkIdExpectedValue scalar object.
- The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
- The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-GET on the following scalar objects:
- opticsIMLinkldExpectedMode
- opticsIMLinkIdExpectedValue
- opticsIMLinkIdSentValue
F- 2.4 Condition Link
Identifier Parameters
P This management function allows the managing system to condition
the parameters related to the Link Identifier management:
- The expected mode on the receiving NE
(opticsIMLinkldExpectedMode).
- The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
- The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-SET on:
- opticsIMLinkldExpectedMode
- opticsIMLinkIdExpectedValue
- opticsIMLinkIdSentValue
Note F-2.4: Allowed values: 0-31.
Note F-2.4: Link Identifier mismatch detection can not be disabled.
F- 2.5 Condition BER
Alarms Thresholds
thresholds used to raise the highBER and lowBER alarms. Both
these values must be included in the related allowed range. The high
BER threshold must be greater than the low BER one.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-SET on the following scalar objects:
- opticsIMHighBERThr
- opticsIMLowBERThr
F- 2.6 Request BER
Alarms Thresholds
the thresholds used to raise respectively a PDH highBER and


APPLICABLE


49/ 139

lowBER alarms.
Scope
Service Used
- opticsIMHighBERThr
- opticsIMLowBERThr
F- 2.7 Request BER
Alarms Thresholds Ranges
the minimum and maximum values allowed for the thresholds used
to raise the PDH highBER and lowBER alarms.
Scope
Service Used
- opticsIMHighBERMinThr
- opticsIMHighBERMaxThr
- opticsIMLowBERMinThr
- opticsIMLowBERMaxThr
F- 2.11 Request
interleaving status
the status of interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMInterleaving
Service Used
SNMP-GET on the following scalar object opticsIMInterleaving.
F- 2.12 Condition
interleaving function
enable/disable the interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMInterleaving
Service Used
SNMP-SET on the following scalar object opticsIMInterleaving.
F- 2.13 Condition EW alarm
BER Thresholds
BER threshold used to raise the EW alarm. This value must be
included in the allowed range.
Scope
Service Used
- opticsIMEWBERThr
F- 2.14 Request EW alarm
BER Thresholds
the BER thresholds used to raise a EW alarm.
Scope
Service Used
- opticsIMEWBERThr
BER Thresholds Ranges
the minimum and maximum values allowed for the BER thresholds
used to raise EW alarm.
Scope
Service Used
- opticsIMEWBERMinThr
- opticsIMEWBERMaxThr


APPLICABLE


50/ 139

PIf
F- 2.9 Report PDH Frame
Alarms
transmission alarms related to the PDH frame.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMFrameTTPTable
Service Used
SNMP-TRAP:
- opticsIMAlarmLossOfFrameRaise
- opticsIMAlarmLossOfFrameClear
- opticsIMAlarmLinkIdentifierMismatchRaise
- opticsIMAlarmLinkIdentifierMismatchClear
F- 2.10 Report PDH Coder
Alarms
transmission alarms related to the PDH coder.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMCoderTTPTable
Service Used
SNMP-TRAP:
- opticsIMAlarmCableLOSRaise
- opticsIMAlarmCableLOSClear
- opticsIMAlarmHighBERRaise
- opticsIMAlarmHighBERClear
- opticsIMAlarmLowBERRaise
- opticsIMAlarmLowBERClear

PDH Tributaries Functions

PIf
F- 3.1 Request E1 Signal
Processing Mode
which processing mode is activated on an E1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
Service Used
SNMP-GET on e1pPITTPSignalMode
F- 3.2 Condition E1 Signal
Processing Mode
Y This management function allows a managing system to condition
the E1 signal processing mode. The allowed signal processing
modes are:
- disabled
- unframed
- framed (G.704)
- framed (G.704) ISDN PRA (ETS 300 233)
Scope
Service Used
SNMP-SET on e1pPITTPSignalMode
Note F-3.2: Only unframed and disabled modes are supported.
F- 3.3 Request E1 Frame
Status
N This management function allows a managing system to request
whether a CRC indication (multiframe presence) is detected on a E1
signal when the processing of a framed signal is activated.
Scope
Service Used


APPLICABLE


51/ 139

SNMP-GET on (respectively):
e1pPITTPFrameStatus
e1PathTTPFrameStatus
F- 3.4 Request RAI
Insertion Status
status of the RAI insertion in a E1 or DS3 framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMPdhRAIInsertionTable
Service Used
SNMP-GET on:
- pdhRAIInsertionStatus
F- 3.5 Condition RAI
Insertion Status
the RAI insertion inhibition in a E1 or DS3 framed signal, both
physical interface and path side. The status allowed are the
following:
- enabled
- inhibited
- forced
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMPdhRAIInsertionTable
Service Used
SNMP-SET on pdhRAIInsertionStatus
F- 3.8 Request E3 Signal
Processing Mode
which processing mode is activated on a E3 signal.
Scope
Service Used
SNMP-GET on e3pPITTPSignalMode
F- 3.9 Condition E3 Signal
Processing Mode
the E3 signal processing mode. The allowed signal processing
modes are:
- disabled
- unframed
- framed (G.704) G.751
- framed (G.704) G.753
Scope
Service Used
SNMP-SET on e3pPITTPSignalMode
Note F-3.9: Only unframed and disabled modes are supported.
F- 3.10 Request DS1
Signal Processing Mode
which processing mode is activated on a DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs1pPITTPTable
Service Used
SNMP-GET on ds1pPITTPSignalMode
F- 3.11 Condition DS1
the processing mode of a DS1 signal. The allowed signal processing
modes are:
- disabled
- unframed
- framed (G.704) with 12 frames multiframe (Super Frame)
- framed (G.704) with 24 frames multiframe (Extended Super
Frame)
Scope
Service Used
SNMP-SET on ds1pPITTPSignalMode


APPLICABLE


52/ 139

F- 3.12 Request DS3
which processing mode is activated on a DS3 signal.
Scope
Service Used
SNMP-GET on ds3pPITTPSignalMode
F- 3.13 Condition DS3
the processing mode of a DS3 signal. The allowed signal processing
modes are:
- disabled
- unframed
- framed (G.704)
Scope
Service Used
SNMP-SET on ds3pPITTPSignalMode
F- 3.14 Request DS1 Line
Coding
line coding of a DS1 signal.
Scope
Service Used
SNMP-GET on ds1pPITTPLineCoding
F- 3.15 Condition DS1 Line
Coding
the line coding of a DS1 signal. The allowed values are the following:
- AMI
- B8ZS
Scope
Service Used
SNMP-SET on ds1pPITTPLineCoding
F- 3.16 Condition Global
DS1 Line Coding
N This management function allows a managing system to specify, in
one shot, the code for all the DS1 lines.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs1LineCoding
Service Used
SNMP-SET on the scalar opticsIMAllDs1LineCoding
Length
length of a DS1 line. It provides information for Line Build Out
circuitry.
Scope
Service Used
SNMP-GET on ds1pPITTPLineLength
Length
the length of a DS1 line.
Scope
Service Used
SNMP-SET on ds1pPITTPLineLength
DS1 Line Length
N This management function allows a managing system to condition,
in one shot, the length of all the DS1 lines.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs1LineLength
Service Used
SNMP-SET on the scalar object opticsIMAllDs1LineLength
Length Allowed Ranges
ranges of Ds1 line lengths allowed on NE.


APPLICABLE


53/ 139

Scope
OPTICSIM-TRS-COMMON-MIB:
opticsIMAllowedLineLengthsTable
Service Used
SNMP-GET on
- allowedLineLengthId
- allowedLineLengthMin
- allowedLineLengthMax
F- 3.33 Request E1/DS1 AIS
Signal Type
which AIS Signal type (allOnes or AllZeroes) is activated on an E1
signal or on DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-GET on e1pPITTPAISSignalType (opticsIME1pPITTPTable)
or ds1pPITTPAISSignalType (opticsIMDS1pPITTPTable).
F- 3.34 Condition E1/DS1
AIS Signal Type
which AIS Signal type (allOnes or AllZeroes) is activated on an E1
signal or on an DS1 signal.
Scope
Service Used
SNMP-SET on e1pPITTPAISSignalType (opticsIME1pPITTPTable)
or ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
E1/DS1 AIS Signal Type
in one shot, the AIS Signal Type (allOnes or AllZeroes) of all the E1
lines or for all the DS1 lines.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllE1AISSignalType,
opticsIMAllDS1AISSignalType
Service Used
SNMP-SET on the scalar object opticsIMAllE1AISSignalType or
opticsIMAllDS1AISSignalType.
F- 3.36 Request E1/DS1 pPI
AIS Insertion
N This management function allows a managing system to request if
insertion of AIS Signal is activated on 2 Mbit/s or on 1,5 Mbit/s PDH
trails.
Scope
Service Used
SNMP-GET on e1pPITTPAISInsertion (opticsIME1pPITTPTable) or
ds1pPITTPAISInsertion (opticsIMDS1pPITTPTable)
pPI AIS Insertion
N This management function allows a managing system to
enable/disable the AIS Signal insertion for 2 Mbit/sor for 1,5 Mbit/s
PDH trails.
Scope
opticsIME1pPITTPTable.
Service Used
SNMP-SET on e1pPITTPAISInsertion (opticsIME1pPITTPTable) or
ds1pPITTPAISInsertion
(opticsIMDS1pPITTPTable).
E1/DS1 pPI AIS Insertion
in one shot, the AIS Signal insertion for all the 2 Mbit/s or for all the
1,5 Mbit/s PDH trails.


APPLICABLE


54/ 139

Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllE1pPIAISInsertion,
opticsIMAllDS1pPIAISInsertion.
Service Used
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion
F- 3.39 Request E1/DS1
Path AIS Insertion
insertion of AIS Signal is activated on 2 Mbit/s or 1,5 Mbit/s path.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable
Service Used
SNMP-GET on e1PathTTPAISInsertion (opticsIME1PathTTPTable)
or ds1PathTTPAISInsertion (opticsIMDS1PathTTPTable).
Path AIS Insertion
enable/disable the AIS Signal insertion for 2 Mbit/s or 1,5 Mbit/s
path.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable.
Service Used
SNMP-SET on e1PathTTPAISInsertion (opticsIME1PathTTPTable)
or ds1PathTTPAISInsertion (opticsIMDS1PathTTPTable).
E1/DS1 Path AIS Insertion
in one shot, the AIS Signal insertion for all the 2 Mbit/s or 1,5 Mbit/s
paths.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllE1pPIAISInsertion,
opticsIMAllDS1pPIAISInsertion
Service Used
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion.
F- 3.42 Request DS3 AIS
Signal Type
which AIS Signal type (allOnes or blueSignal) is activated on an DS3
signal. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPAISSignalType
F- 3.43 Condition DS3 AIS
Signal Type
which AIS Signal type (allOnes or blueSignal) is activated on an DS3
signal. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPAISSignalType
DS3 AIS Signal Type
in one shot, the AIS Signal Type (allOnes or blueSignal) of all the
DS3 lines. It is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3AISSignalType
Service Used
SNMP-SET on the scalar object opticsIMAllDS3AISSignalType
F- 3.45 Request DS3 pPI
AIS Insertion
insertion of AIS Signal is activated on 45 Mbit/s PDH trails. It is
applicable only on framed signal.
Scope


APPLICABLE


55/ 139

Service Used
SNMP-GET on ds3pPITTPAISInsertion
F- 3.46 Condition DS3 pPI
AIS Insertion
enable/disable the AIS Signal insertion for 45 Mbit/s PDH trails. It is
Scope
Service Used
SNMP-SET on ds3pPITTPAISInsertion.
DS3 pPI AIS Insertion
in one shot, the AIS Signal insertion for all the 45 Mbit/s PDH trails. It
is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPIAISInsertion
Service Used
SNMP-SET on the scalar object opticsIMAllDs3pPIAISInsertion
F- 3.48 Request DS3 Path
AIS Insertion
insertion of AIS Signal is activated on 45 Mbit/s path. It is applicable
only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-GET on ds3PathTTPAISInsertion.
F- 3.49 Condition DS3 Path
AIS Insertion
enable/disable the AIS Signal insertion for 45 Mbit/s path. It is
Scope
Service Used
SNMP-SET on ds3PathTTPAISInsertion.
DS3 Path AIS Insertion
in one shot, the AIS Signal insertion for all the 45 Mbit/s paths. It is
applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3PathAISInsertion
Service Used
SNMP-SET on the scalar object opticsIMAllDs3PathAISInsertion
F- 3.51 Request DS3 AIS
Signal Timing
time to wait before to insert an AIS signal (after failure detection) and
the time to wait to remove an AIS signal (after the failure clear) on an
DS3 line. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPAISSignalTiming
F- 3.52 Condition DS3 AIS
Signal Timing
the time to wait before to insert an AIS signal (after failure detection)
and the time to wait to remove an AIS signal (after the failure clear)
on a DS3 line. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPAISSignalTiming
DS3 AIS Signal Timing
in one shot, the time to wait before to insert an AIS signal (after
failure detection) and the time to wait to remove an AIS signal (after
the failure clear) for all the DS3 lines. It is applicable only on framed


APPLICABLE


56/ 139

signals.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3AISSignalTiming
Service Used
SNMP-SET on the scalar object opticsIMAllDS3AISSignalTiming
F- 3.54 Request DS3 pPI
Parity Violation Monitoring
Removing
Parity Violation Monitoring Removing is enabled or disabled on 45
Mbit/s trail. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPParityViolationMonitoringRemoving.
F- 3.55 Condition DS3 pPI
Removing
enable/disable the Parity Violation Monitoring Removing for 45
Mbit/s trail. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPParityViolationMonitoringRemoving.
DS3 pPI Parity Violation
Monitoring Removing
in one shot, the Parity Violation Monitoring Removing for all the 45
Mbit/s trails. It is applicable only on framed signals.
Scope
opticsIMAllDs3pPIParityViolationMonitoringRemoving
Service Used
opticsIMAllDs3pPIParityViolationMonitoringRemoving
F- 3.57 Request DS3 Path
Removing
Parity Violation Monitoring Removing is enabled or disabled on 45
Mbit/s path. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3PathTTPParityViolationMonitoringRemoving.
F- 3.58 Condition DS3 Path
Removing
enable/disable the Parity Violation Monitoring Removing for 45
Mbit/s path. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3PathTTPParityViolationMonitoringRemoving.
DS3 Path Parity Violation
Monitoring Removing
in one shot, the Parity Violation Monitoring Removing for all the 45
Mbit/s paths. It is applicable only on framed signals.
Scope
opticsIMAllDs3PathParityViolationMonitoringRemoving
Service Used
opticsIMAllDs3PathParityViolationMonitoringRemoving
F- 3.60 Request DS3 Idle
insertion and detection
idle insertion is activated on one direction and the status (detection)
of idle insertion on the other direction for an DS3 signal. It is
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used


APPLICABLE


57/ 139

SNMP-GET on
- ds3pPITTPIdleInsertion
- ds3pPITTPIdleDetection
F- 3.61 Condition DS3 Idle
insertion
the idle insertion on an DS3 signal. It is applicable only on framed
signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPIdleInsertion
Bridge Status
this selected DS3 line is used to bridge and other DS3 line.
Scope
Service Used
SNMP-GET on
ds3pPITTPInputBridgeEnabled
Bridge
the input bridge for DS3 lines.
The managing system has to provided for each DS3 line if the bridge
is enabled is or disabled. If the enabled value is setted, than an
other DS3 line (equipment dependent, identified by notApplicable
value on same object) is bridged onto this selected line. The
notApplicable value is used to identifie the DS3 line to bridge.
Scope
Service Used
SNMP-SET on ds3pPITTPInputBridgeEnabled
F- 3.64 Request E1/E3
pseudo-random pattern
insertion
Y This management function allows a managing system to request if
insertion of pseudo-random pattern is activated on tributary x (E1 or
E3 signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
Service Used
SNMP-GET on e1pPITTPPseudoRandSeqInsertion
(opticsIME1pPITTPTable) or e3pPITTPPseudoRandSeqInsertion
(opticsIME3pPITTPTable).
F- 3.65 Condition E1/E3
pseudo-random pattern
insertion
the insertion of pseudo-random pattern on tributary x (E1 or E3
signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
Service Used
SNMP-SET on e1pPITTPPseudoRandSeqInsertion
(opticsIME1pPITTPTable) or e3pPITTPPseudoRandSeqInsertion
(opticsIME3pPITTPTable).

PIf
F- 3.20 Report PDH
Physical Interface Alarms
transmission alarms related to PDH physical interfaces.
Scope
opticsIMDs1pPITTPTable


APPLICABLE


58/ 139

Service Used
SNMP-TRAP:
- opticsIMAlarmLossOfSignalRaise
- opticsIMAlarmLossOfSignalClear
- opticsIMAlarmAisRaise
- opticsIMAlarmAisClear
- opticsIMAlarmRemoteDefectIndicationRaise (E1 and DS3 only)
- opticsIMAlarmRemoteDefectIndicationClear (E1 and DS3 only)
F- 3.21 Report PDH Path
Alarms
transmission alarms related to PDH paths.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable
opticsIMDs1PathTTPTable
opticsIMDs3PathTTPTable
Service Used
SNMP-TRAP:
- opticsIMAlarmAisRaise
- opticsIMAlarmAisClear
- opticsIMAlarmRemoteDefectIndicationRaise (E1 and DS3 only)
- opticsIMAlarmRemoteDefectIndicationClear (E1 and DS3 only)
F- 3.22 Report PDH Loss
Alarm Due to Switch
N This management function allows a managed system to report the
loss of the PDH signals due to switch for protection of Fast Ethernet
signals.
Scope
Service Used
SNMP-TRAP:
- opticsIMPdhLossDueToSwitchRaise
- opticsIMPdhLossDueToSwitchClear

BER Measure Functions

Function SNM
PIf
F- 3.30 Create BER
Measure Entry
Y This management function allows the managing system to create a
BER measure entry. The management system has to indicate in the
creation request: the monitoring point (indicated by means of
ifIndex).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMBERMeasureTable
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
"createAndGo" value
F- 3.31 Delete BER
Measure Entry
Y This management function allows the managing system to delete a
BER measure entry.
Scope
Service Used
SNMP-SET on berMeasureRowStatus columnar object to "destroy"
value
F- 3.32 Request BER Y This management function allows the managing system to request


APPLICABLE


59/ 139

Measure Data the BER measure data related to the current observation period.
Scope
Service Used
SNMP-GET on the following columnar objects:
- berMeasureElapsedTime
- berMeasureSuspectIntervalFlag
- berMeasureViolations
- berMeasureValue


as well.
The general naming rules for the SDH/PDH Transmission objects are defined in [11].

Table Entry
Supported Objects
(Table/Scalar)
Configuration
(note 1)
Description
Index
Value
opticsIMTrsCommonMib
1+0 / 1+1 E3 Tx port - Ch#1 10101 opticsIME3pPITTPTable
e3pPITTPSignalMode
e3pPITTPOperationalState
e3pPITTPAsapIndex
e3pPITTPPseudoRandSeqInsertion
1+1 MP E3 Tx port - Ch#Common 10199
1+0 / 1+1 E1 Tx port - Ch#1 1xx01 (note 2) opticsIME1pPITTPTable
e1pPITTPSignalMode
e1pPITTPOperationalState
e1pPITTPAsapIndex
e1pPITTPPseudoRandSeqInsertion
1+1 MP E1 Tx port - Ch#Common 1xx99 (note 2)
1+0 / 1+1 E3 Rx port - Ch#1 22101 opticsIME3PathTTPTable
e3PathTTPOperationalState 1+1 MP E3 Rx port - Ch#Common 22199
1+0 / 1+1 E1 Rx port - Ch#1 2zz01 (note 3) opticsIME1PathTTPTable
e1PathTTPOperationalState 1+1 MP E1 Rx port - Ch#Common 2zz99 (note 3)
Radio port Ch#1 20101
E3 Rx port - Ch#1 22101 1+0
E1 Rx port - Ch#1 2zz01 (note 3)
E3 Rx port - Ch#1 22101
1+1
E1 Rx port - Ch#1 2zz01 (note 3)
E3 Rx port - Ch#Common 22199
opticsIMBERMeasureTable
berMeasureElapsedTime
berMeasureSuspectIntervalFlag
berMeasureViolations
berMeasureValue
berMeasureRowStatus
1+1 MP
E1 Rx port - Ch#Common 2zz99 (note 3)
opticsIMAlarmLinkIdentifierMismatchR
aise
opticsIMAlarmLinkIdentifierMismatchC
lear
All


APPLICABLE


60/ 139

Table Entry
Supported Objects
(Table/Scalar)
Configuration
(note 1)
Description
Index
Value
opticsIMTrsPdhMib
1+0 / 1+1 Radio port Ch#1 20101
opticsIMFrameTTPTable
frameTTPOperationalState
1+1 MP
1+0 Radio port ODU Ch#1 20101
Radio port ODU Ch#1 20101
opticsIMCoderTTPTable
coderTTPOperationalState
1+1 / 1+1 MP
Radio port ODU Ch#0 20100
opticsIMLinkExpectedMode
opticsIMLinkExpectedValue
opticsIMLinkSentValue
opticsIMHighBERThr
opticsIMHighBERMinThr
opticsIMHighBERMaxThr
opticsIMLowBERThr
opticsIMLowBERMinThr
opticsIMLowBERMaxThr
opticsIMEWBERThr
opticsIMEWBERMinThr
opticsIMEWBERMaxThr
All
Table 26 SDH/PDH Transmission Domain: Naming rules
1+0: 1+0 / 1+0L / 1+0EXT
1+1: 1+1HSB / 1+1HSB-SD / 1+1FD
(note 2) xx = 01..16 for nx2Mbps configurations xx = 02 for 34+2Mbps configurations.
(note 3) zz = 21..36 for nx2Mbps configurations zz = 22 for 34+2Mbps configurations.


APPLICABLE


61/ 139

6 RADIO DOMAIN
Frequency setting
Nominal case: The configuration of Radio Tx frequency and Radio Rx frequency is done by setting the
Radio Tx frequency value. The NE automatically calculates the Rx Frequency based on duplexer shift
value and LO Inf/Sup information, known from equipment configuration.
Special case: When the duplexer choice is "ODUDUPOTHER" in the equipment configuration, Rx
frequency is managed independently from Tx Frequency, and then becomes settable.
The list of allowed frequency values is provided in [APPENDIX A].
Transmit power setting
The list of allowed transmit power values is provided in [APPENDIX A].
ATPC
When provisioned IDU Main is an IDU Classic, and ODUs are UX-Flat ODUs, ATPC feature is
supported. In all other cases, ATPC feature is not supported.
When ATPC function is enabled, the ATPC max value can be configured on a per channel basis. The
ATPC min value is always set to the minimum Tx power value supported by the ODU (depends on ODU
model) and the feature key, and therefore cannot be configured.
ATPC Rx low power threshold can be configured (integer value in the range [-102 dBm .. 22 dBm]). The
same value applies for both channels in case of 1+1 configurations.
ATPC general behavior is the following:
When measured Rx Power level is below ATPC Rx low power threshold, Tx power is increased
When measured Rx Power level is in the range [ATPC Rx low power threshold .. ATPC Rx low
power threshold + 4 dBm], Tx power is left untouched
When measured Rx Power level is above (ATPC Rx low power threshold + 4 dBm), Tx power is
decreased
ATPC Rx extra-low power threshold is not supported.
ATPC High power mode is not supported.


APPLICABLE


62/ 139

Radio Protections
One RPS hitless protection scheme is supported with all the 1+1 configurations. One TPS protection
scheme is supported in case of 1+1 HSB configurations.

The following table defines the characteristics of the RPS protection scheme.

Protection Group Type 1+1 hitless
Switching Type Single Ended
Restoration Criteria Non Revertive
Switching Condition Signal Fail, HBER, LBER, EW
Priority Not Applicable
Operator Commands
Lockout spare
Manual switch from main to spare (and vice versa)
Table 27 Radio Protection Switching Scheme characteristics
The following table defines the characteristics of the TPS protection scheme.

Protection Group Type 1+1
Switching Type Single Ended
Restoration Criteria Revertive / Non Revertive (note 1)
Switching Condition Equipment failures Tx side
Operator Commands
Lockout spare
Manual switch from main to spare (and vice versa)
Table 28 Tx Protection Switching Scheme characteristics
Note 1: TPS restoration criteria can be revertive or non-revertive, depending on the type of configuration:
Revertive: 1+1HSB, 1+1HSB-MP
Non-Revertive: 1+1HSB-SD, 1+1HSD-SD-MP
The configuration of both RPS and TPS protection schemes is performed by the NE in conjunction with
the equipment provisioning process (declaration of boards).
Early Warning switching threshold on received power level
In case of 1+1 configurations, the early warning switching threshold on received power level can be
configured. The allowed range for this threshold is [-99 dBm..60 dBm]. Only integer values are
supported. The same threshold level applies for both radio channels.

Modulation

Modulation has to be considered a system parameter and therefore has to be configured (4 or 16 QAM)
with the same value on both radio channels, independently from the configuration. The list of ODUs
having a modifiable modulation parameter or having a fixed 4 or 16 QAM modulation type is provided in
[APPENDIX A].

Modulation and Tx bit rate value can be interdependent. For instance, 16QAM modulation can not be
used when Tx bit rate is set to 2 Mbits/s. Tx bit rate value has priority upon modulation value, which
means that when Tx bit rate is set to 2 Mbits/s, modulation is automatically forced to 4QAM.


APPLICABLE


63/ 139

When a managing system configures the modulation, the request is addressed to a specific radio
channel. However, the agent implicitly applies this configuration to both radio channels.
Radio transmission parameters in 1+1 HSB configurations

With 1+1 HSB configurations, the radio frequency must be configured with the same values on both radio
channels. This ensures that a transmission protection switch doesnt affect the radio transmission.

This coupling is true for frequency setting, while it is not for transmit power. Some antennas configuration
are built using an asymmetric coupler. In order to compensate as much as possible the coupler
attenuation on stand-by channel versus main channel, the transmit power may be adjusted separately on
the 2 channels.

This behavior is obtained in the following way:
when a managing system configures one of the radio frequency parameters, it addresses the
associated request to a specific radio channel
when the agent receives the request, implicitly, applies this configuration on both radio channels.
Radio parameters managed in 1+1 HSB configuration according to this behavior are described in the
following table:

Parameter SNMP Table SNMP Object
Radio Frequency opticsIMRadioFrequencyTable radioTxFrequency
Tx Mute (Local) opticsIMRadioTxMuteTable opticsIMRadioManLocalTxMute
Table 29 Radio Transmission Parameters in 1+1 HSB Configuration


APPLICABLE


64/ 139


The following table lists the Radio management functions supported in this release (see [7]).

Radio PDH/SDH Common Management Functions

Radio Frequency

PIf
F- 1.1 Request Tx Radio
Frequency
the transmission radio frequency expressed in KHz.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioFrequencyTable
Service Used
SNMP-GET on radioTxFrequency
F- 1.2 Condition Tx Radio
Frequency
Y This management function allows the managing system to condition
the transmission radio frequency expressed in KHz.
Scope
Service Used
SNMP-SET on radioTxFrequency
F- 1.3 Request Rx Radio
Frequency
the receive radio frequency expressed in KHz.
Scope
Service Used
SNMP-GET on radioRxFrequency
F- 1.4 Request Tx Radio
Frequency Range
the minimum and maximum values allowed for the transmission
radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-GET on:
- radioMinTxFrequency
- radioMaxTxFrequency
F- 1.5 Condition Tx Radio
Frequency Range
N This management function allows the managing system to condition
the minimum and maximum values allowed for the transmission
radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-SET on:
- radioMinTxFrequency
- radioMaxTxFrequency
F- 1.6 Condition Rx Radio
Frequency
the receive radio frequency expressed in KHz.
Scope
Service Used


APPLICABLE


65/ 139

SNMP-SET on radioRxFrequency
F- 1.7 Request Rx Radio
Frequency Range
the minimum and maximum values allowed for the receive radio
frequency, they are expressed in KHz.
Scope
Service Used
SNMP-GET on:
- radioMinRxFrequency
- radioMaxRxFrequency
F- 1.8 Condition Rx Radio
Frequency Range
the minimum and maximum values allowed for the receive radio
frequency, they are expressed in KHz.
Scope
Service Used
SNMP-SET on:
- radioMinRxFrequency
- radioMaxRxFrequency
F- 1.9 Request Return Code
on Radio Frequency
setting
Y This management function allows the managing system to check if
Set operation on radio frequency is successful. If the Get operation
returns a value different than setNoError, then the Set operation on
radio frequency is unsuccessful and this value stays until a new Set
operation on radio frequency is performed. Otherwise, if the Get
operation returns setNoError, the above Set operation on radio
frequency is successful.
Scope
Service Used
SNMP-GET on radioReturnCodeFrequency

Tx Power and ATPC

PIf
F- 1.10 Request ATPC
Implemented Status
Y This management function allows the managing system to request if
the ATPC capability is present or not.
Scope
opticsIMRadioAtpcImplemented
Service Used
SNMP-GET on opticsIMRadioAtpcImplemented
F- 1.11 Request ATPC
Activity
the status of the ATPC activity: enabled or disabled.
Scope
Service Used
SNMP-GET on radioAtpcEnabled
F- 1.12 Condition ATPC
Activity
the status of the ATPC activity: enabled or disabled. ATPC can be
enabled only if it is implemented in the equipment.
Scope


APPLICABLE


66/ 139

Service Used
SNMP-SET on radioAtpcEnabled
F- 1.13 Request ATPC Tx
Range
the minimum and maximum values allowed for the transmitted power
used by ATPC device.
Scope
Service Used
SNMP-GET on:
- radioMinAtpcTxPower
- radioMaxAtpcTxPower
F- 1.14 Condition ATPC Tx
Range
P This management function allows the managing system to condition
the minimum and maximum values allowed for the transmitted power
used by ATPC device.
Scope
Service Used
SNMP-SET on:
- radioMinAtpcTxPower
- radioMaxAtpcTxPower
Note F- 1.14: radioMinAtpcTxPower is not supported
F- 1.15 Request ATPC Rx
Power Thresholds
P This management function allows the managing system to request
the low and extra low power thresholds values used by the ATPC
device.
Scope
Service Used
SNMP-GET on:
- radioAtpcLowPowerThr
- radioAtpcExtraLowPowerThr
Note F- 1.15: radioAtpcExtraLowPowerThr is not supported
F- 1.16 Condition ATPC Rx
Low Power Threshold
low power threshold value used by the ATPC device. This value
must be included in the related allowed range.
Scope
Service Used
SNMP-SET on radioAtpcLowPowerThr
F- 1.17 Request ATPC Low
Power Threshold Range
the minimum and maximum values allowed for the low power
threshold value used by ATPC device.
Scope
Service Used
SNMP-GET on:
- radioAtpcLowPowerMinThr
- radioAtpcLowPowerMaxThr
F- 1.18 Request Tx Nominal
Power
the tx nominal power.
Scope


APPLICABLE


67/ 139

Service Used
SNMP-GET on radioTxNominalPower
F- 1.19 Request Current Tx
Power
the value of the transmitted power when the ATPC is disabled and
no manual operation on transmitted power is active.
Scope
Service Used
SNMP-GET on radioCurrentTxPower
F- 1.20 Condition Current
Tx Power
value of the transmitted power to be used by the local transmitter
when the ATPC is disabled and no manual operation on transmitted
power is active.
Scope
Service Used
SNMP-SET on radioCurrentTxPower
F- 1.21 Request Tx Power
Range
the allowed range (minimum and maximum values) of the
transmitted power.
Scope
Service Used
SNMP-GET on:
- radioMinTxPower
- radioMaxTxPower
F- 1.22 Request Manual
Operation Status on Tx
Power
the status (active/not active) of a manual management of the
transmitted power.
Scope
Service Used
SNMP-GET on radioManOpTxPower
F- 1.23 Initiate/Terminate a
Manual Operation on Tx
Power
N This management function allows the managing system to initiate /
terminate a manual management of the transmitted power.
Scope
Service Used
SNMP-SET on radioManOpTxPower
F- 1.24 Request Manual
Operation Tx Power Level
the transmitted power level when a manual management of the
transmitted power is active.
Scope
Service Used
SNMP-GET on radioManOpTxPowerLevel
F- 1.25 Condition Manual
Operation Tx Power Level
N This management function allows the managing system to set the
transmitted power level when a manual management of the
transmitted power is active.
Scope


APPLICABLE


68/ 139

Service Used
SNMP-SET on radioManOpTxPowerLevel
F- 1.26 Request Atpc
Direction Identifier
the ATPC direction identifier used in the equipment configurations in
which all the radio channels transmit in the same direction.
Scope
opticsIMRadioAtpcDirectionId
Service Used
SNMP-GET on opticsIMRadioAtpcDirectionId
F- 1.27 Condition Atpc
Direction Identifier
the ATPC direction identifier used in the equipment configurations in
which all the radio channels transmit in the same direction. The
identifier provided is used both as expected value (sink side) and as
transmitted one (source side).
Scope
Service Used
SNMP-SET on opticsIMRadioAtpcDirectionId
F- 1.29 Request Allowed
ATPC Tx Range
P This management function allows the managing system to request
the minimum and maximum values allowed for the ATPC device
when allowed ATPC range and allowed RTPC range are different
(see F-1.21).
Scope
Service Used
SNMP-GET on:
- radioMinAllowedAtpcTxPower
- radioMaxAllowedAtpcTxPower
- radioATPCHighPowerTimeoutEnabled (v2.18)
Note F- 1.29: radioATPCHighPowerTimeoutEnabled is not supported
F- 1.48 Request ATPC High
Power Status
the status of the ATPC in high-power mode.
Scope
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-GET on:
- radioATPCHighPowerMode
- radioATPCHighPowerTimeout
F- 1.49 Condition ATPC in
High Power Mode
N This management function allows the managing system to lock the
ATPC in high-power mode.
Scope
Service Used
SNMP-SET on radioATPCHighPowerMode
F- 1.137 Condition ATPC
enabled with timeout
N This management function allows the managing system to enable or
to disable the ATPC with timeout
Scope
Service Used
SNMP-SET on radioATPCHighPowerTimeoutEnabled


APPLICABLE


69/ 139

PIf
F- 1.28 Report ATPC
Identifier Mismatch Alarm
N This management function allows a managed system to report an
ATPC Identifier Mismatch alarm.
Scope
Service Used
SNMP-TRAP:
- opticsIMAlarmAtpcIdentifierMismatchRaise
- opticsIMAlarmAtpcIdentifierMismatchClear

Intrusive Tx Power Control Management

Function SNM
PIf
F- 1.XXX All the functions. N

Rx Gain

PIf

Analogue Measurements

Function Analogue
Measurements
SNM
PIf
Channel Number
number of the radio channel associated to a analog measure.
Scope
OPTICSIM-RADIO-TRS-SDH-MIB:
Service Used
SNMP-GET on analogueMeasuresRadioChannelNumber
F- 1.41 Request Local
the measurements of the local transmitted and received power
levels.
Scope
Service Used
SNMP-GET on:
- analogueMeasuresLocalTxPower
- analogueMeasuresLocalRxMainPower
the measurements of the remote transmitted and received power
levels.
Scope
Service Used
SNMP-GET on:
- analogueMeasuresRemoteTxPower
- analogueMeasuresRemoteRxMainPower
F- 1.43 Request Local N This management function allows the managing system to request


APPLICABLE


70/ 139

Diversity Analogue
Measurement
the measures of the local received power levels related to the
diversity receiver.
This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-GET on analogueMeasuresLocalRxDivPower
Diversity Analogue
Measurement
the measures of the remote received power levels related to the
diversity receiver.
This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-GET on analogueMeasuresRemoteRxDivPower

Radio Protection Switching

PIf
F- 1.50 Request RPS
Protection Group
Configuration
type of protection (1+1 or 1:N) and if the hitless capability is present
or not.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on:
F- 1.51 Request RPS
Criteria
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupRevertive
F- 1.52 Condition RPS
Criteria
automatic restoration criteria from the spare channel to the main one
when the failure clears.
This function is applicable only in case of 1+1 protection group type.
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionGroupRevertive
F- 1.53 Request RPS
Privileged Channel
privileged channel. This function is applicable only in case of 1:N
protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupPrivilegedChannel
Privileged Channel
N This management function allows a managing system to set up the
privileged channel. This function is applicable only in case of 1:N
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless


APPLICABLE


71/ 139

Scope
Service Used
SNMP-SET on opticsIMRadioProtectionGroupPrivilegedChannel
F- 1.55 Request RPS Extra
Traffic
extra traffic status (enabled or disabled). This function is applicable
only in case of 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupExtraTraffic
Extra Traffic
enable/disable the extra traffic. This function is applicable only in
case of 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupExtraTraffic
F- 1.57 Request RPS
type of a protection unit: main (protected) or spare (protecting).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
Service Used
SNMP-GET on opticsIMRadioProtectionUnitType
F- 1.58 Request RPS
Protection Unit Priority
priority of a protection unit. It is applicable only in case of 1:N
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionUnitPriority
Protection Unit Priority
the priority of the protection unit. It is applicable only in case of 1:N
Scope
SNMP-SET on opticsIMRadioProtectionUnitPriority
This management function allows a managing system to request the
absolute Received Power Level used to raise an EW alarm.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRxPowerLevelThresholdMngt
Service Used
SNMP-GET on opticsIMRxPowerLevelThr scalar object.
F- 1.146 Condition EW
alarm Rx Power Level
the absolute Received Power Level used to raise an EW alarm.
Scope
Service Used
SNMP-SET on opticsIMRxPowerLevelThr
Rx Power Level Range
minimum and maximum values allowed for absolute Received
Power Level used to raise an EW alarm.
Scope
Service Used
Rx Power Level
Y


APPLICABLE


72/ 139

Service Used
SNMP-GET on following scalar object.
F- 1.150 Request RPS
Switch on EW alarm Status
RPS switch occurs when EW alarm raised for Rx Power Level or
BER threshold crossing, for both. if RPS switch doesnt occur when
EW alarm raised, the disabled value is returned.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioSwitchEWEnabled
Service Used
SNMP-GET on opticsIMRadioSwitchEWEnabled scalar object.
Switch on EW alarm
N This management function allows a managing system to condition if
RPS has to occur when EW alarm raised for Rx Power Level or BER
threshold crossing (enabledBEROnly or enabledRxPowerOnly
value), for both (enabledBoth value) or if RPS Switch has not to
occur for EW alarm (disabled value).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioSwitchEWEnabled
Service Used
SNMP-SET on opticsIMRadioSwitchEWEnabled
F- 1.152 Request RPS
Switch on lowBER alarm
Status
RPS switch occurs when lowBER alarm raised. if RPS switch
doesnt occur when lowBER alarm raised, the disabled value is
returned.
Scope
opticsIMRadioSwitchLowBEREnabled
Service Used
SNMP-GET on opticsIMRadioSwitchLowBEREnabled scalar object.
Switch on lowBER alarm
N This management function allows a managing system to condition if
RPS switch has to occur when lowBER alarm raised or not.
Scope
opticsIMRadioSwitchLowBEREnabled
Service Used
SNMP-SET on opticsIMRadioSwitchLowBEREnabled

Function Operator
Commands
SNM
PIf
of a RPS Working Channel
inhibit/allow a working channel (main) to be switched to a protection
channel (spare). If the main channel was already switched when the
Inhibit Switch is requested, it is forced back to the working position.
noRequest syntax to remove the lockout and allow the switch, both
Scope
(on main protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(lockout/noRequest)
of RPS Protection Channel
inhibit/allow a protection channel (spare) to provide protection in the
- OpticsIMRxPowerLevelMinThr
- OpticsIMRxPowerLevelMaxThr


APPLICABLE


73/ 139

protection scheme. If the protection channel was already providing
protection for a working one when the Inhibit Switch is requested,
then a forced switch is performed back to the working position.
noRequest syntax to remove the lockout and allow any switch, both
Scope
(on spare protection unit)
Service Used
(lockout/noRequest)
Manual Switch to RPS
Protection Channel
initiate/terminate a manual switch from a working channel (main) to
the protection one (spare). This command will fail if another working
channel has already been switched to the protection channel (only in
case of 1:N) or if the protection channel is locked or has an
automatic switch request (SF, HBER, LBER, EW) active present.
Scope
Service Used
(manualSwitch/noRequest)
Manual Switch to a RPS
Working Channel
initiate/terminate a manual switch from a protection channel (spare)
to a working one (main). This management function is applicable
only in case of 1+1 not revertive protection type. This command will
fail if the working channel has an automatic switch request (SF,
HBER, LBER, EW) active present.
Scope
Service Used
Forced Switch to RPS
Protection Channel
initiate/terminate a forced switch from a working channel (main) to a
protection one (spare). If another working channel has already been
automatically or manually switched to the protection one when the
initiate command is received, it is switched back to its working
channel to allow the other working channel to be switched to the
protection one.
This function will fail if another working channel is already forced
switched to the protection one.
the noRequest syntax to terminate the forced switch, both addressed
to a main protection unit.
Scope
Service Used


APPLICABLE


74/ 139

(forcedSwitch/noRequest)
Forced Switch to a RPS
Working Channel
initiate/terminate a forced switch from a protection channel (spare) to
a working one (main). This management function is applicable only
in case of 1+1 not revertive protection type.
Scope
Service Used

PIf
F- 1.66 Request RPS
Protection Scheme
Operational State
the operational state of a radio protection scheme.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupOperationalState
F- 1.67 Request RPS
Protection Status
the current state of a radio protection unit.
Scope
Service Used
SNMP-GET on:
opticsIMRadioProtectionUnitSwitchCommand
This management function allows the managing system to request
the current state of a radio protection unit.
Scope
Service Used
SNMP-GET on:
F- 1.68 Request RPS
Protection Mismatch
Status
N This management function allows the managing system to request a
status will indicate if there is any mismatch between the local and
far-end protection type (1+1/1:N).
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupMismatchStatus

Function Rx Static Delay
Configuration
SNM
PIf

Function Rx Static Delay
Notification
SNM
PIf

- opticsIMRadioProtectionUnitSwitchCommand
- opticsIMRadioProtectionUnitSwitchCriteria
- opticsIMRadioProtectionUnitSwitchStatus


APPLICABLE


75/ 139

HST Transmission Protection Switching

PIf
F- 1.80 Request TPS
Criteria
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupRevertive
F- 1.81 Condition TPS
Criteria
automatic restoration criteria from the spare transmission channel to
the main one when the failure clears.
Scope
Service Used
SNMP-SET on opticsIMTxProtectionGroupRevertive
type of a protection unit: main (protected) or spare (protecting).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable
Service Used
SNMP-GET on opticsIMTxProtectionUnitType

Function Operator
Commands
SNM
PIf
of TPS Protection Channel
inhibit/allow a protection channel (spare) to provide protection in the
protection scheme. If the protection channel was already providing
protection for the working one when the Inhibit Switch is requested,
then a forced switch is performed back to the working position.
noRequest syntax to remove the lockout and allow any switch, both
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(lockout/noRequest)
Manual Switch to TPS
Protection Channel
initiate/terminate a manual switch from a working channel (main) to
the protection one (spare). This command will fail if the protection
channel is locked or has an automatic switch request active present.
Scope
Service Used
Manual Switch to TPS
Working Channel
initiate/terminate a manual switch from a protection channel to a
working one. This management function is applicable only in case of
F- 1.82 Request TPS


APPLICABLE


76/ 139

1+1 not revertive protection type. This command will fail if the
working channel has an automatic switch request active present.
Scope
Service Used
Forced Switch to TPS
Protection Channel
initiate/terminate a forced switch from a working channel to a
protection one. If another working channel has already been
automatically or manually switched to the protection one when the
initiate command is received, it is switched back to its working
channel to allow the other working channel to be switched to the
protection one.
According to the NE type, this function will fail if protection channel
has a failure condition.
the noRequest syntax to terminate the forced switch, both addressed
to a main protection unit.
Scope
Service Used
Forced Switch to TPS
Working Channel
initiate/terminate a forced switch from a protection channel to a
working one. This management function is applicable only in case of
1+1 not revertive protection type.
Scope
Service Used

PIf
F- 1.88 Request TPS
Protection Scheme
Operational State
the operational state of a HST TPS protection scheme.
Scope
Service Used
SNMP-GET on opticsIMTxProtectionGroupOperationalState
the current state of a TPS protection unit.
Scope
Service Used
SNMP-GET on:
F- 1.89 Request TPS
Protection Status
- opticsIMTxProtectionUnitSwitchCommand


APPLICABLE


77/ 139

- opticsIMTxProtectionUnitSwitchCriteria
- opticsIMTxProtectionUnitSwitchStatus
F- 1.90 Report TPS
Protection Switch Event
N This management function allows the managed system to report any
protection switch event to the managing system, such as:
Scope
Service Used
SNMP-TRAP (opticsIMProtectionSwitchReporting) on:

Common Loss Alarm

PIf

Function Operator
Commands and Status
SNM
PIf

PIf

Tx Mute

Function Operator
Commands and Status
SNM
PIf
F- 1.120 Request Local
Transmitter Mute Status
status of the local radio transmitter in terms of mute function:
Scope
Service Used
SNMP-GET on the columnar objects:
F- 1.121 Condition Local
Y This management function allows a managing system to mute a
local radio transmitter.
Scope
Service Used
SNMP-SET on opticsIMRadioManLocalTxMute
status of the remote radio transmitter in terms of mute function:
- protection switching (forced, manual or automatic switch)
- protection release (release of forced, manual or automatic
switch)
- lockout, release lockout.
- opticsIMTxProtectionUnitSwitchCommand
- opticsIMTxProtectionUnitSwitchCriteria
- opticsIMTxProtectionUnitSwitchStatus
- no squelch active
- squelch active, required by the managing systems
-
- squelch active, required automatically by the agent
squelch active for both the previous reasons
- opticsIMRadioManLocalTxMute
- opticsIMRadioAutoLocalTxMute
- no squelch active


APPLICABLE


78/ 139

- squelch active, required by the managing systems
- squelch active, required automatically by the agent
- squelch active for both the previous reasons
Scope
Service Used
F- 1.123 Condition Remote
N This management function allows a managing system to mute a
local radio transmitter.
Scope
Service Used
SNMP-SET on opticsIMRadioManRemoteTxMute

WST&Radio Service Channels Protections Switching

SNM
PIf

Function Operator
Commands
SNM
PIf

PIf

Analogue Points

Function SNM
PIf
Function Descrition
N

Shifter Definition Functions

Function Function Descrition

Radio SPI Common Functions

PIf

Function TP Status SNM
PIf

SNM
PIf
SNMP-GET on the columnar objects:
- opticsIMRadioManRemoteTxMute
- opticsIMRadioAutoRemoteTxMute
Function Configuration
F- 1.XXX All the functions.

SNM
PIf
Function Notification


APPLICABLE


79/ 139

Radio SPI Urban Haul Functions

Function SNM
PIf

Radio SPI Long Haul Functions

SNM
PIf
F- 2.xx All the functions N

Radio Frame Complementary Overhead Functions

SNM
PIf
N

PIf

PIf

Radio SDH NE Functions

Function Synchronization SNM
PIf

Radio PDH Functions

PIf
Channel Number
number of the radio channel associated to the radioPDHTTP.
Scope
OPTICSIM-RADIO-TRS-PDH-MIB: opticsIMRadioPDHTTPBidTable
Service Used
SNMP-GET on radioPDHTTPBidRadioChannelNumber
F- 3.2 Request Modulation
Type
modulation type (4 or 16 QAM) supported by a radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidModulation
F- 3.3 Condition
Modulation Type
the modulation type (4 or 16 QAM). According to the equipment
configuration, a change of the modulation of one radio channel can
imply an implicit automatic change also of the modulation of all the
other radio channels. This behaviour will be defined in the product
external specifications.
Scope

Function
Function Configurations
F- 2.XX All the functions.


APPLICABLE


80/ 139

Service Used
SNMP-SET on radioPDHTTPBidModulation
F- 3.4 Request Equalizer
Status
status of equalizer (inhibited or activated) associated to
radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidEqualizerStatus
F- 3.5 Condition Equalizer
Status
N This management function allows a managing system to inhibit or
activate the equalizer associated to radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidEqualizerStatus
F- 3.6 Request ASAP
Pointer
ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidAsapIndex
F- 3.7 Condition ASAP
Pointer
the ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidAsapIndex

Function TP Status Function Description
F- 3.8 Request TP
Operational State
the operational state of a radioPDHTTP.
Scope
Service Used
SNMP-GET on opticsIMRadioPDHTTPBidOperationalState
F- 3.9 Request ODU
Service Kit Status
N This management function allows the managing system to request if
the ODU Service Kit is connected to the transceiver. When this
situation is detected an Abnormal Condition indication is generated.
Scope
Service Used
SNMP-GET on opticsIMRadioPDHTTPBidOduServiceKit

PIf
F- 3.10 Report Radio PDH
Alarms
transmission alarm related to a radioPDHTTP.
Scope
- opticsIMAlarmRxLOSRaise
- opticsIMAlarmRxLOSClear
- opticsIMAlarmDemLOSRaise
SNM
PIf
Service Used
SNMP-TRAP:
- opticsIMAlarmRxFailRaise
- opticsIMAlarmRxFailClear


APPLICABLE


81/ 139

- opticsIMAlarmDemLOSClear
- opticsIMAlarmDemFailRaise
- opticsIMAlarmDemFailClear
- opticsIMAlarmModLOSRaise
- opticsIMAlarmModLOSClear
- opticsIMAlarmModFailRaise
- opticsIMAlarmModFailClear
- opticsIMAlarmTxLOSRaise
- opticsIMAlarmTxLOSClear
- opticsIMAlarmTxFailRaise
- opticsIMAlarmTxFailClear
- opticsIMAlarmAtpcLoopProblemRaise
- opticsIMAlarmAtpcLoopProblemClear
- opticsIMAlarmIncompatibleFrequencyRaise
- opticsIMAlarmIncompatibleFrequencyClear
- opticsIMAlarmIncompatiblePTXRaise
- opticsIMAlarmIncompatiblePTXClear
- opticsIMAlarmVcoExternalLOSRaise
- opticsIMAlarmVcoExternalLOSClear
- opticsIMAlarmHighBERRaise
- opticsIMAlarmHighBERClear
- opticsIMAlarmLowBERRaise
- opticsIMAlarmLowBERClear
- opticsIMAlarmEarlyWarningRaise
- opticsIMAlarmEarlyWarningClear
- opticsIMAlarmPathDistortionRaise
- opticsIMAlarmPathDistortionClear
- opticsIMAlarmRadioDADERaise
- opticsIMAlarmRadioDADEClear
- opticsIMAlarmRingBrokeRaise
- opticsIMAlarmRingBrokeClear


APPLICABLE


82/ 139



as well.
The general naming rule for the Radio objects is defined in [11].

Table Entry
Supported Objects
(Table/Scalar)
Configuration
Description
Index
Value
opticsIMRadioTrsCommonMib
1+0 Radio port Ch#1 20101
radioTxFrequency
radioRxFrequency
radioMinTxFrequency
radioMaxTxFrequency
radioMinRxFrequency
radioMaxRxFrequency
20100
radioReturnCodeFrequency
1+1
Radio port Ch#0
Radio port Ch#1 20101 radioAtpcImplemented
radioAtpcEnabled
radioMinAtpcTxPower
radioMaxAtpcTxPower
radioAtpcLowPowerThr
radioAtpcLowPowerMinThr
radioAtpcLowPowerMaxThr
radioTxNominalPower
radioCurrentTxPower
radioMinTxPower
radioMaxTxPower
1+1
Radio port Ch#0
analogueMeasuresRadioChannelNumber
analogueMeasuresLocalTxPower
analogueMeasuresLocalRxMainPower
1+1
opticsIMRadioManLocalTxMute
opticsIMRadioAutoLocalTxMute
1+1
opticsIMAlarmLowBERClear
opticsIMAlarmHighBERRaise (note 2)
opticsIMAlarmHighBERClear (note 2)
opticsIMAlarmEarlyWarningRaise
opticsIMAlarmEarlyWarningClear
opticsIMAlarmIncompatibleFrequencyRaise
opticsIMAlarmIncompatibleFrequencyClear
opticsIMAlarmIncompatiblePTXRaise
opticsIMAlarmIncompatiblePTXClear
All

(note 1)
20100
1+0
opticsIMAlarmLowBERRaise


APPLICABLE


83/ 139

Table Entry
Supported Objects
(Table/Scalar)
Configuration
(note 1)
Description
Index
Value
opticsIMRadioTrsPdhMib
opticsIMRadioPDHTTPBidTable
radioPDHTTPBidRadioChannelNumber
radioPDHTTPBidModulation
radioPDHTTPBidOperationalState
radioPDHTTPBidAsapIndex
1+1
opticsIMRadioSwtcMib
opticsIMRadioProtectionGroupTable
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless
opticsIMRadioProtectionGroupRevertive
opticsIMRadioProtectionGroupOperationalState
1+1 1
Ch#1 1; 1 opticsIMRadioProtectionUnitTable
opticsIMRadioProtectionUnitType
opticsIMRadioProtectionUnitSwitchCommand
opticsIMRadioProtectionUnitSwitchCriteria
opticsIMRadioProtectionUnitSwitchStatus
1+1
Ch#0 1; 0
opticsIMTxProtectionGroupTable
opticsIMTxProtectionGroupRevertive
opticsIMTxProtectionGroupOperationalState
1+1 HSB 1
Ch#1 1; 1 opticsIMTxProtectionUnitTable
opticsIMTxProtectionUnitType
opticsIMTxProtectionUnitSwitchCommand
opticsIMTxProtectionUnitSwitchCriteria
opticsIMTxProtectionUnitSwitchStatus
1+1 HSB
Ch#0 1; 0
Table 30 Radio Domain: Supported Objects and Naming rules
1+0: 1+0 / 1+0L / 1+0EXT
1+1: 1+1HSB / 1+1HSB-SD / 1+1FD / 1+1HSB-MP / 1+1HSB-SD-MP / 1+1FD-MP
1+1 HSB: 1+1HSB / 1+1HSB-SD / 1+1HSB-MP / 1+1HSB-SD-MP
(note 2) These alarm notifications are defined in the Radio domain but the related defects are
detected by the Main and Extension units (IDU).


APPLICABLE


84/ 139

7 SUPPORT DOMAIN

The support domain includes the management of: agent, event reporting, event logging, alarms, alarms
summary, backup and restore, software download, software package and NE time.

Agent Management

The identification of the NE is provided in the tsdimNeInstallationType scalar object. The value of this
object is: LUX50.

The identification of the software version of the NE is provided in the sysDescr object. It is a 9 bytes
string, defined in the following way:
sysDescr [1] is a V (upper case)
sysDescr [2,3] represents the major version
sysDescr [4,5] represents the minor version
sysDescr [6,7] represents the maintenance version
During the commissioning phase, the operator must configure the opticsIMNeConfigurationTypeId scalar
objects in order to define the NE configuration.
The following table provides the list of NE configurations supported in this release with the values of the
opticsIMAllowedNeConfigurationType and opticsIMAllowedNeConfigurationId objects.

Allowed Configuration Type Description
OpticsIMAllowedNe
ConfigurationType
value
OpticsIMAllowedNe
ConfigurationId
value
Undefined UNDEFINED 0
1+0 1+0 1
1+0 Light 1+0L 7
1+0EXT 2
1+1 Hot Standby 1+1HSB 3
1+1 Hot Standby, Space Diversity 1+1HSB-SD 8
1+1 Frequency Diversity 1+1FD 4
1+1 Hot Standby, Mux-Demux Protected 1+1HSB-MP 5
1+1 Hot Standby, Space Diversity, Mux-Demux
Protected
1+1HSB-SD-MP 9
1+1 Frequency Diversity, Mux-Demux Protected 1+1FD-MP 6
1+0 with Service Channels Extension
Table 31 Supported Configurations and Labels
The undefined allowed configuration type is the default configuration.

When an IDU Light is used in a NE, the maximum possible configuration is 1+0 (see sysName content
below). In this case the only allowed configuration type for the NE configuration is 1+0L: the NE creates
entries number 0 and 7 only.

When an IDU Classic is used in a NE, all configurations are authorized, except the 1+0L configuration
(entry number 7).

When the IDU type (e.g. Light or Classic) is unknown, either because the remote inventory cannot be
read or because it is not recognized, all NE configurations are authorized.


APPLICABLE


85/ 139

Feature Key Limitations
The limitations introduced by the feature key or by the IDU light are coded in the sysName scalar object.
Rules for coding are the following:

- sysName is a string composed by an enumeration of definitions
- Each definition is separated by a space character,
- Each definition is composed by a name, followed by the sign equality =, followed by a list of values.
- Values are either :
- an enumeration of choices, separated by commas ,
- the special string ---, meaning that no values are available.
Provision for future extension: when a definition has an unknown name, this definition must be ignored
but all the other definitions are valid.

Definition name Semantics Possible
values
Conf
Maximum allowed configuration. Limit
given by the IDU type (classic or light).
1+0
1+1
Conf=1+0
Rate Maximum allowed bite rate.
2x2
4x2
8x2
16x2,34+2
----
Rate=16x2,34+2
Rtpc
Configuration of receive power below
the maximum receive power allowed.
yes
no
---
Rtpc=yes
Mod Maximum modulation type allowed.
4
16
---
Mod=4
OutputPowerCh#1
Range of allowed values for Transmit
power of the main channel. Min and
Max transmit powers are expressed in
dBm.
<min>,<max> -11,20
OutputPowerCh#0
Range of allowed values for Transmit
power of the spare channel. Min and
Max transmit powers are expressed in
dBm.
<min>,<max> -11,20
Example
Table 3 Feature Key Limitations 2

Note : limitations of frequency ranges can be specified in feature key for Melodie LUX12 and LUX40 but
have never been used. Therefore, no frequency limitation is checked with LUX50

Example of SysName content for Classic IDU with its software key:
Conf=1+1 Rate=16x2,34+2 Rtpc=no Mod=16 OutputPowerCh#1=-10,10
OutputPowerCh#0=-10,10
SysName content for Classic IDU without software key (predefined content):
Conf=1+1 Rate=--- Rtpc=--- Mod=--- OutputPowerCh#1=--- OutputPowerCh#0=---

SysName content for Light IDU with integrated software key (predefined content):
Conf=1+0 Rate=4x2 Rtpc=yes Mod=4 OutputPowerCh#1=-127,127 OutputPowerCh#0=---


APPLICABLE


86/ 139

Software Management

From management point of view, the LUX50 control system is based on one control element type: the
Equipment Controller (EC). It has in charge the control and management of the virtual machine as a
whole, as well as of the IDU physical resources.

The LUX50 can hold two software packages (software versions). Each of them is composed by one
software unit (EC control element type).
The association between software unit index and related label is indicated in the following table.

opticsIMSwUnitIndex value opticsIMSwUnitLabel string
1 EC
Table 3 Software Units index and label 3

The commitment of the activated version takes place implicitly together with the activation itself, so that
in case of restart events, the version used when rebooting is the active version. Since the stand-by
version is automatically deleted, the system can not be reverted back to the previously active version,
except by performing a new software download with the previous version.
Event Logging

The Log size is 200 records (125 for alarms, 75 for events). A wrapping mechanism is provided.

Abnormal Conditions

The triggering events for abnormal conditions are the following:

Event Type
Forced switch (EPS, RPS, TPS)
Loopbacks activation
Local radio Tx mute (manual)
Local radio Tx mute (automatic)
Pseudo random sequence insertion
Lockout (EPS, RPS, TPS)
Table 34 Abnormal Conditions Triggering Event Types


APPLICABLE


87/ 139


The following table lists the Support management functions supported in this release (see [3]).

Function Event Reporting
Management
SNM
PIf
F- 1. Create Event Report

Y This function allows a managing system to initiate reporting of
events to the specified address.
Scope
This function permits to create an EventForwardingDiscriminator
managed object.
Service Used
SNMP-SET on the following tsdimEFDTable columnar objects:
- tsdimEFDDest (the IP address of the managing system)
- tsdimEFDPort (the UDP port of the managing system)
- tsdimEFDTrapId
- tsdimEFDTrapObject
- tsdimEFDLowestForwardedSeverity
- tsdimEFDIndeterminate
- tsdimEFDManagerIndex
SNMP-SET on RowStatus columnar object to "createAndWait"
value.
F- 2. Activate Event Report Y This function allows a managing system to initiate reporting of
events to the specified address after a communication lost.
Scope
This function permits to activate an EventForwardingDiscriminator
managed object. The EventForwardingDiscriminator managed object
has to be activate in case it has been put out of service by managed
system because of communication lost.
Service Used
SNMP-SET to "active" value on the RowStatus columnar object
in tsdimEFDTable managed table.
F- 3. Delete Event Report Y This function allows a managing system to terminate reporting of
events to the specified address.
Scope
This function permits to delete an EventForwardingDiscriminator
managed object.
Service Used
SNMP-SET on RowStatus columnar object to "destroy" value.
F- 4. Allow/Inhibit Event
Report
Y This function allows a managing system to allow and inhibit the
reporting of events to itself. Row status object is the one involved in
this management: its value "notInService" means "locked", viceversa
row status as "unlocked" means "active".
Scope
This function permits to lock or unlock the state of an EFD object.
Service Used
SNMP-SET on the tsdimEFDRowStatus columnar object inside
tsdimEFDTable.
F- 5. Request Event Report Y This function allows a managing system to retrieve information about
one or more reporting destinations related to different group of
events
Scope
This function permits to retrieve data related to one or more EFD
objects.
Service Used
SNMP-GET on the following tsdimEFDTable columnar objects:


APPLICABLE


88/ 139

- tsdimEFDTrapId
- tsdimEFDOperStatus
- tsdimEFDRowStatus
F- 6. Condition Event
Report
Y This function allows a managing system to modify information about
one or more reporting destinations related to different group of
events
Scope
This function permits to modify data related to one or more EFD
objects.
Service Used
SNMP-SET on the following tsdimEFDTable columnar objects:
- tsdimEFDTrapId
F- 7. Report Event Y This function allows a managed system to report events to the
managing system.
The event reports contain at least the following mandatory
information when applicable to the specific event:
- managedObjectClass
- managedObjectInstance
- notificationIdentifier: it has to be unique at a network element
level.
- eventTime with the accuracy of one second. In case of clear of
an alarm, it will be considered as the time at which the
corresponding clearing of the fault cause has been determined by
the defect filtering process.
- specificProblems (in case of clear of alarms it has the same value
as the one present in the event sent when the alarm was raised)
- perceivedSeverity with the value cleared in case of clear of
alarms

N.B. The Event Type or Probable Cause (in case of alarm) is
defined as the SNMP identifier of the notification.

This function applies to all managed objects capable to notify events.
Scope
This function permits to a managed system to send all the "very
urgent events" to the managing systems. The "very urgent events"
are the ones specified in the EFD objects. Moreover a managing
system could retrieve all the events form LOGs and APT objects.
Service Used
SNMP-TRAP the events are marked as "very urgent", otherwise
SNMP-GET (into LOG and/or APT objects from managing
system)
F- 8. Report Alert Event N This function allows a managed system to report alert events to the
managing system.
The alert event reports contain at least the following mandatory
information:
- notificationIdentifier: it is the notification identifier of the last event
emitted
- eventTime: it is the time of the last event emitted


APPLICABLE


89/ 139

Scope
This function permits to a managed system to send an alert
notification to the managing systems.
Service Used
SNMP-TRAP the tsdimAlertNotification events
F- 9. Request Alert Event
Configuration
N This function allows a managing system to retrieve the configuration
of the alert notification mechanism.
Scope
This function permits to a managing system to retrieve data related
to the time and frequency counters used by managed system in
order to send an alert notification to the managing systems.
Service Used
- tsdimAlertNotifTimeOut
- tsdimAlertNotifFreqCount
F- 10. Condition Alert Event
Configuration
N This function allows a managing system to modify the configuration
of the alert notification mechanism.
Scope
This function permits to a managing system to modify data related to
the time and frequency counters used by managed system in order
to send an alert notification to the managing systems.
Service Used
- tsdimAlertNotifTimeOut
- tsdimAlertNotifFreqCount

Function Event Logging
Management
SNM
PIf
F- 11. Request Maximum
Notification Identifier Value
Y This function allows a managing system to retrieve information about
the notification identifier used as a unique numbering in the event
creations.
Scope
This function permits to retrieve the allowable maximum notification
identifier number.
Service Used
SNMP-GET on the tsdimMaxNotificationId scalar object.
F- 12. Request Log Status Y This function allows a managing system to retrieve the status of the
logs provided by the managed system.
Scope
This function permits to retrieve the administrative and operational
states of the alarm and event logs inside a managed system.
Service Used
SNMP-GET on the following columnar objects of the
tsdimLogTable
- tsdimLogObjectClassIdentifier (the type of log, alarm or event
logs)
- tsdimLogAdminStatus
- tsdimLogOperStatus
F- 13. Request Log Size Y This function allows a managing system to retrieve the size of the
logs provided by the managed system.
Scope
This function permits to retrieve the maximum size of the alarm and
event logs inside a managed system
Service Used
SNMP-GET on the following columnar objects of the
tsdimLogTable
- tsdimLogMaxSize


APPLICABLE


90/ 139

F- 14. Inhibit/Allow Logging Y This function allows a managing system to allow or inhibit the
logging of the notification raised by managed system, both alarms
and events.
Scope
This function permits to modify the administrative status of the log
objects.
Service Used
SNMP-SET of the tsdimLogAdminStatus columnar object inside
the tsdimLogTable.
F- 15. Request Log
Records
P This function allows a managing system to request to the managed
system one or a set of log records.
Scope
This function permits to retrieve the log records stored inside the
alarm and event logs depending on which logs are supported.
Service Used
SNMP-GET of the entries in the tsdimEventLogTable,
tsdimGenEventLog and tsdimAlarmLogTable managed tables.
Note F-15: tsdimGenEventLog is not supported.
F- 16. Report Log State
Change
Y This function allows a managed system to report log state change
events to the managing system.
Scope
This function is used by managed system in order to communicate to
managing system all the logs operational state changing.
Service Used
SNMP-TRAP tsdimStateChangeNotification on the
tsdimLogTable

Function Alarm Severity
Management
SNM
PIf
F- 17. Request Default
ASAP Severity
the default severity used.
This function permits to retrieve the default severity used in case is
not defined a specific ASAP object for a certain probableCause.
Service Used
SNMP-GET on the tsdimAlarmSevDefault scalar object
F- 18. Condition Default
ASAP Severity
Y This function allows a managing system to modify information about
the used default severity.
Scope
This function permits to modify the default severity used in case is
not defined a specific ASAP object for a certain probableCause.
Service Used
SNMP-SET on the tsdimAlarmSevDefault scalar object
F- 19. Request Next ASAP
Index
Y This function allows a managing system to retrieve the next index
value to use in free ASAP creation.
Scope
This function permits to retrieve the value of the index to be used in
the creation of the ASAP object.
Service Used
SNMP-GET on the tsdimAlarmSevProfileIndexNext scalar object
F- 20. Create Alarm
Severity Profile
Y This function allows a managing system to define different ASAP
objects.
Scope
This function permits to create an ASAP object.
Service Used
SNMP-SET on the following tsdimAlarmSevProfileTable
columnar object:
Scope


APPLICABLE


91/ 139

- tsdimAlarmSevProfileIndex
SNMP-SET on tsdimAlarmSevProfileRowStatus columnar object
to "createAndGo" value.
F- 21. Delete Alarm
Severity Profile
Y This function allows a managing system to terminate different ASAP
objects.
Scope
This function permits to delete an ASAP object.
Service Used
F- 22. Create Alarm
Severity
Y This function allows a managing system to define different <alarm
severity - probableCause> attributes inside an Alarm Severity Profile
object.
Scope
This function permits to create a couple of objects used to associate
a severity to a probableCause. The probableCause is defined as
trap OID.
Service Used
SNMP-SET on the following tsdimAlarmSevTable columnar
object:
- tsdimAlarmSevProfileIndex, this has to be equal to an index
already present in the tsdimAlarmSevProfileTable
- tsdimAlarmSevTrapId
- tsdimAlarmSevSeverity
- tsdimAlarmSevSeverityNotServAff
SNMP-SET on RowStatus columnar object to "createAndGo"
value.
F- 23. Delete Alarm
Severity
Y This function allows a managing system to terminate different alarm
severity objects.
Scope
This function permits to delete an alarm severity object.
Service Used
F- 24. Request Alarm
Severity
Y This function allows to managing system to retrieve all the
information related to the ASAP objects both the predefined either
the free ones.
Scope
This functions permits to retrieve one or more <severity -
probableCause> couples of objects related to one or more ASAP
objects.
Service Used
SNMP-GET on tsdimAlarmSevTable managed table.
F- 25. Condition ASAP User
Label
Y This management function permits to configure the User Label
associated to an ASAP entry.
Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
Service Used
SNMP-SET on tsdimAlarmSevProfileUserLabel
F- 26. Request ASAP User
Label
Y This management function permits to request the User Label
associated to an ASAP entry.
Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
Service Used
SNMP-GET on tsdimAlarmSevProfileUserLabel


APPLICABLE


92/ 139

Function Alarm Summary
Management
F- 27. Request Active
Problems Table
Y This function allows a managing system to ask to a managed system
the list of all active alarms collects by the managed system.
Scope
This function permits to retrieve all the active alarms stored inside
activeProblemTable managed object.
Service Used
SNMP-GET on the tsdimAPTTable managed object

Function Abnormal
Condition Management
SNM
PIf
F- 78. Request Abnormal
Condition Status
Y This function allows a managing system to request the status of the
NE in terms of abnormal conditions.
Scope
TSDIM-SUPPORT-MIB
Service Used
SNMP-GET on the opticsIMActiveAbnCond scalar object.
Condition Affected Objects
Y This function allows a managing system to request the list of objects
that result in an abnormal condition.
Scope
TSDIM-SUPPORT-MIB: opticsIMAbnCondAffectedObjectsListTable
Service Used
SNMP-GET on the opticsIMAbnCondAffectedObjectInstanceId
columnar object.
Condition Description
N This function allows a managing system to request the description of
an abnormal (off normal) condition.
Scope
TSDIM-SUPPORT-MIB: opticsIMAbnCondAffectedObjectsListTable
Service Used
SNMP-GET on the opticsIMOffNormalDescription columnar object.

Function Backup and
Restore Management
SNM
PIf
F- 28. Request NE Software
Version
its NE software version in order to couple it with the backup file.
Scope
This function permits to retrieve the software version managed
object.
Service Used
SNMP-GET on the sysDescr managed object
F- 29. Condition Backup
File Name
N This function allows a managing system to define the name of the
backup file.
Scope
This function permits to set the file name object.
Service Used
SNMP-SET on the opticsIMBackupFilename managed object
F- 30. Request Backup
Manager Identifier
N This function allows a managing system to request the identifier
value of the managing system that has activated a backup operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMBackupRequestorAddress managed
object
F- 31. Condition Backup
Manager Identifier
N This function allows a managing system to define its proper identifier
value for backup operation. This will permit to have only one
SNM
PIf


APPLICABLE


93/ 139

operation at time.
Scope
This function permits to set the identifier object.
Service Used
SNMP-SET on the opticsIMBackupRequestorAddress managed
object
F- 32. Condition Restore
Software Version
N This function allows a managing system to set to a managed system
the NE software version associated to the file that will be restored.
Scope
This function permits to set the restore file software version
managed object.
Service Used
SNMP-SET on the opticsIMRestoreSWVersion managed object
File Name
N This function allows a managing system to define the name of the
restore file.
Scope
This function permits to set the file name object.
Service Used
SNMP-SET on the opticsIMRestoreFilename managed object
Manager Identifier
N This function allows a managing system to define its proper identifier
value for restore operation. This will permit to have only one
operation at time.
Scope
This function permits to set the identifier object.
Service Used
SNMP-SET on the opticsIMRestoreRequestorAddress managed
object
F- 35. Request Restore
Manager Identifier
N This function allows a managing system to request the identifier
value of the managing system that has activated a restore operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMRestoreRequestorAddress managed
object
F- 36. Request Restore
State
N This function allows a managing system to ask to a managed system
the state of the restore operation.
Scope
This function permits to retrieve the state of a restore operation.
Service Used
SNMP-GET on the opticsIMRestoreState managed object
State
N This function allows a managing system to change the in-progress
state of the restore operation. A managing system has to specify the
following states:
- "downloading" state,
- "present" state when the file has been successfully transferred; in
case of Sub SNMP NE supporting Restore in one phase, the NE
implicitly set this state to "apply",
- "apply" state to communicate to the Agent that it has to apply the
restore file, applicable only to stand-alone SNMP NE supporting
Restore in two-phases.
The "absent" value is set by Agent as default value.
Scope
This function permits to modify the state of a restore operation.
Service Used
SNMP-SET on the opticsIMBackupState managed object
F- 38. Request Backup
State
N This function allows a manager system to retrieve the state of the
Backup operation.
Scope


APPLICABLE


94/ 139

This function permits to get the Backup state scalar object.
Service Used
SNMP-SET on the opticsIMBackupState managed object

Function Agent
Management
SNM
PIf
F- 40. Request NE
Installation Type
its installation type (such as 4x4 board characteristic).
Scope
This function permits to retrieve the NE installation type managed
object.
Service Used
SNMP-GET on the tsdimNeInstallationType managed object
F- 41. Request Board
Position
its board position inside the shelf.
Scope
This function permits to retrieve the NE board position managed
object.
Service Used
SNMP-GET on the tsdimBoardPosition managed object
F- 42. Request Info-Model
Version
which info-model version it supports.
Scope
This function permits to retrieve the NE Info-model version managed
objects.
Service Used
SNMP-GET on the tsdimInfoModelVersionMajor,
tsdimInfoModelVersionMinor and
tsdimInfoModelVersionMaintenance managed objects
F- 44. Request SDH NE
Label
information about the SDH NE label configuration.
Scope
This function permits to retrieve the SDH NE label managed object.
Service Used
Y This function allows a managing system to set to a managed system
the SDH NE label object.
Scope
This function permits to set the SDH NE label managed object.
Service Used
SNMP-SET on the tsdimSdhNeLabel managed object
F- 86. Request Manager
List
information about the ManagerList, i.e. the list of manager owner of
NE.
Scope
This function permits to retrieve the ManagerList managed object.
Service Used
SNMP-GET on the opticsImNEOwnsByMgr managed object
F- 87. Condition Manager
List
N This function allows a managing system to set to a managed system
the object containing the information about the ManagerList.
Scope
F- 48. Request Local
Access Control State
information about the Craft Terminal local access control state.
SNMP-GET on the tsdimSdhNeLabel managed object
F- 45. Condition SDH NE
Label
This function permits to set the ManagerList managed object.
Service Used
SNMP-SET on the opticsImNEOwnsByMgr managed object
Scope


APPLICABLE


95/ 139

This function permits to retrieve the Craft Terminal local access
control state managed object.
Service Used
SNMP-GET on the tsdimLacState managed object
F- 49. Condition Local
Access Control State
the object containing the information about the Craft Terminal local
access control state.
Scope
This function permits to set the Craft Terminal local access control
state managed object.
Service Used
SNMP-SET on the tsdimLacState managed object
information about the Craft Terminal local access control time out
period interval.
Scope
This function permits to retrieve the Craft Terminal local access
control time out period interval managed object.
Service Used
SNMP-GET on the tsdimLacNoResponseTimeOutPeriod
managed object
F- 51. Condition Local
Access Control Time Out
Period
the object containing the information about the Craft Terminal local
access control time out period interval.
Scope
This function permits to set the Craft Terminal local access control
time out period interval managed object.
Service Used
SNMP-SET on the tsdimLacNoResponseTimeOutPeriod
managed object
F- 58. Request NE Software
Release
which is its software release.
Scope
This function permits to retrieve the NE software release.
Service Used
SNMP-GET on the sysDescr managed object
F- 59. Request NE Location Y This function allows a managing system to ask to a managed system
which is its location value.
Scope
This function permits to retrieve the NE location.
Service Used
SNMP-GET on the sysLocation managed object
F- 60. Condition NE
Location
Y This function allows a managing system to modify the location value
of a managed system.
Scope
This function permits to modify the NE location.
Service Used
SNMP-SET on the sysLocation managed object
F- 61. Request NE
SubRelease
which is its subrelease value.
Scope
This function permits to retrieve the NE subrelease.
Service Used
SNMP-GET on the sysName managed object
Note F-61: Function used to request license key information.
F- 62. Request NE Allowed
Configurations
Y This management function allow the managing system to request
the configurations allowed for the supported NE.
F- 50. Request Local
Access Control Time Out
Period


APPLICABLE


96/ 139

Scope
TSDIM-SNMPNE-MIB:
opticsIMAllowedNeConfigurationTypeTable
Service Used
SNMP-GET on opticsIMAllowedNeConfigurationType
F- 63. Request NE
Configuration
the NE configuration type. This information is provided by means of
NE configuration type identifier and associated string.
Scope
TSDIM-SNMPNE-MIB: opticsIMNeConfiguration
Service Used
SNMP-GET on the scalar objects:
F- 64. Condition NE
Configuration
Y This management function allows the managing system to define the
NE configuration type. It is defined setting the identifier
(NeConfigurationTypeId object) associated to the NE configuration
type string required (NeConfigurationType object). As a side effect of
this operation the agent must set the NeConfigurationType object
with the configuration type string associated to this identifier.
The identifier provided must be included in the list of the allowed NE
configuration type identifiers.
Scope
Service Used
SNMP-SET on opticsIMNeConfigurationTypeId
F- 65. Request Market N This management function allows the managing system to request
the market (ETSI or ANSI) in which the NE is used.
Scope
Service Used
SNMP-GET on opticsIMMarket
F- 66. Condition Market N This management function allows the managing system to define the
market (ETSI or ANSI) in which the NE is used.
Scope
Service Used
SNMP-SET on opticsIMMarket

Function Software
Download Management
SNM
PIf
F- 67. Condition Server
Information
the (e.g. Ftp) Server information. This information is used by the
Client to connect the Server during a Software Download Operation.
Scope
The managing system configures:
- the Server Address;
- the Server Port;
- the Server UserId;
- the Server Password;
- the Root Directory where the Software Package to be
downloaded is stored on the Server.
Service Used
SNMP-Set on opticsImSwdlServerAddress, opticsImSwdlServerPort,
opticsImSwdlServerPassword, opticsImSwdlServerRootDir Scalar
Objects.
F- 68. Initiate a Y This management function allows a managing system to initiate a


APPLICABLE


97/ 139

Downloading Operation software downloading operation.
Only one downloading operation can be performed at the same time.
This operation can be performed only if the NE is not restoring the
MIB database that is if the opticsIMRestoreState has the value
"absent" or "present".
Upon activation of rowStatus the opticsIMswdlStatusIndicator is
changed to Downloading.
N.B. It is up to the agent the single Download running check.
Scope
The managing system configures:
1. The identifier of the new software release (SW Package Version,
Sw Package Label and Descriptor Name) to be delivered to the
managed system;
2. an optional flag (ForcedDowndload) which indicates whether the
version indicated by the identifier of the new software release has to
be loaded entirely regardless of the fact that some software units
may already be present in the NE.
Service Used
SNMP-SET on the following columnar objects of
opticsIMSwdlInitTable:
- opticsImSwdlInitForcedDownload
- opticsImSwdlInitSwPkgVersion
- opticsImSwdlInitSwPkgLabel
- opticsImSwdlInitDescrName
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"ActivecreateAndGo" value.
F- 69. Abort/Destroy a
Downloading Operation
Y This management function has the aim to clean up the Download
operation at Agent side.
It could be used both to stop an in progress download and to destroy
the row occuped.
Scope
The managing system configures to Delete the
opticsImSwdlInitRowStatus.
Service Used
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"Destroy" value.
F- 70. Request
Downloading Information
downloading information at configurable polling expiration.
Scope
The managing system can retrieve the Percentage, the Total
Number of Bytes, the Current SW Unit Version and Label of the in-
progress Software Download operation.
When terminated the managing system can retrieve the Result of
previous Software Download operation, during an in-progress
Software Download the Result takes the "underDownloading" value.
Service Used
SNMP-GET on
- opticsIMSwdlPercentage,
- opticsIMSwdlTotalBytes,
- opticsIMSwdlCurrentSwUnitVersion,
- opticsIMSwdlCurrentSwUnitLabel,
- opticsImSwdlResult.

Function Software Package
Management
SNM
PIf
F- 71. Activate a Stand-by
Software Version
Y This function allows a managing system to activate a stand-by
software version which is already stored on the managed system. It
cannot be performed while the NE is downloading a database, that


APPLICABLE


98/ 139

is if the opticsIMRestoreState object has the value "downloading".
If a forced activation is required, the stand-by software version is
activated also if it is the same as the active software version.
The function can apply only on a stand-by version. Upon a
successful completion of the function the managed system updates
the state of the addressed software version with the value
"activated" or "committed" according to the way of working of the
NE. The software version previuosly active is updated by the
managed system with the "stand-by" value if it was in the "activated"
status, with the value "boot" if it was in the "committed" one.
Scope
TSDIM-SUPPORT-MIB: opticsIMSwPackageTable
Service Used
SNMP-SET on opticsIMSwPackageCommand columnar object
(activation or forcedActivation syntax)
F- 72. Request Software
Version Activation Result
Y This function allows a managing system to request to the managed
system the result of a activation command (forced or not) on a
software version.
The error code managed are listed hereafter:
- 'download in progress': if a stand-by version try to be activated
when a download operation is in-progress.
- 'only one memory bank full': if there is only one software version
inside the managed element (i.e. no stand-by version).
- 'software release corrupted': if the check on software release to
be activated fails.
- 'switch not allowed by the NE state': if the activation of a new
version may leave the managed system in an inconsistent state (for
instance if the data base cannot be reverted to an old format and no
other data are available).
- 'software unit missing': If the managed system is equipped with
one or more boards whose software image is not available on the
NE.
- 'swReleaseCorrupted': if the operationalState of the stand-by
software version is "disabled".
Scope
Service Used
SNMP-GET on opticsIMSwPackageActivationResult columnar
object
F- 73. Commit an Active
Software Version
N This function allows a managing system to commit the current active
software version on the managed system. It cannot be performed
while the NE is downloading a database, that is if the
opticsIMRestoreState object has the value "downloading".
The commit function can apply only on an active version. When the
commitment is performed, the active software version is used as the
boot version for a spontaneous restart in case of crash or restart.
Upon a successful completion of the function the managed system
updates the the state of the software version with the value
"committed".
Scope
Service Used
SNMP-SET on opticsIMSwPackageCommand columnar object
(commit syntax)
Package Information
Y This function allows a managing system to request information about
the software package.
Scope


APPLICABLE


99/ 139

Service Used
- opticsIMSwPackageCommand
- opticsIMSwPackageState
- opticsIMSwPackageActivationDate
- opticsIMSwPackageLabel
- opticsIMSwPackageVersion
- opticsIMSwPackageOperationalState
Unit Information
software units included in a software package.
Scope
TSDIM-SUPPORT-MIB: opticsIMSwUnitTable
Service Used
- opticsIMSwUnitLabel
- opticsIMSwUnitVersion
- opticsIMSwUnitSize
F- 76. NE Restart Request Y This function allows a managing system to request a restart of the
managed system, using the committed software version.
Scope
TSDIM-SUPPORT-MIB
Service Used
SNMP-SET on opticsIMNERestartRequest scalar object (restart
syntax is used)
F- 94. Request Equipment
Software Unit Information
N This function allows a managing system to request information about
software unit running on a board identified by its equipment position.
Scope
TSDIM-SUPPORT-MIB: opticsIMEqptSwUnitTable
Service Used
- opticsIMEqptSwUnitLabel
- opticsIMEqptSwUnitVersion

Function Time
Management
SNM
PIf
F- 80. Request NE Current
Time
the current time of the NE. If NTP is enabled this function is not
supported.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMExternalTime
F- 81. Condition NE Time Y This management function allows the managing system to condition
the time of the NE. The agent makes it instantaneously its new own
time. If NTP is enabled this function is not supported.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMExternalTime
F- 82. Request NTP Status Y This management function allows the managing system to request
the current status of the NTP (enabled/disabled).
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMNTPStatus
F- 83. Condition NTP
Status
enable/disable the NTP.


APPLICABLE


100/ 139

Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMNTPStatus
F- 84. Request NTP Servers
Addresses and
Reachability
the addresses of the NTP servers (main and spare) and the related
reachability.
Scope
TSDIM-SNMPNE-MIB
Service Used
- opticsIMMainNTPServerAddress
- opticsIMSpareNTPServerAddress
- opticsIMNTPServersReachabilityStatus
F- 85. Condition NTP
Servers Addresses
the addresses of the NTP servers (main and spare).
Scope
TSDIM-SNMPNE-MIB
Service Used
- opticsIMMainNTPServerAddress
- opticsIMServerNTPServerAddress

Function Filtering
Management
SNM
PIf
F- 89. Condition HD
Retrieval Time
Y This management function permits to condition the HD retrieval
Time. The parameters to be configured are:
the OS which has collected the HD
the Begin Time
the End Time
the GranularityPeriod
Scope
OPTICSIM-COMMONPM-MIB: opticsIMFilterHistoryDataTable
Service Used
SNMP-SET on
- opticsIMFilterHDStartByOS
- opticsIMFilterHDBeginTimeInterval
- opticsIMFilterHDEndTimeInterval
- opticsIMFilterHDGranularityPeriod
F- 90. Create Filter History
Data Entry
Y This management function permits to create one Filter History Data
entry. The management system has to indicate in the creation
request:
its own IP Address
its own UDP Port
Scope
Service Used
SNMP-SET on opticsIMFilterHDRowStatus columnar object to
"createAndGo" value
F- 91. Delete Filter History
Data Entry
Y This management function permits to delete one Filter History Data
entry.
Scope
Service Used
SNMP-SET on opticsIMFilterHDRowStatus columnar object to
"destroy" value


APPLICABLE


101/ 139

Function EPS add on
Management
SNM
PIf
F- 92. Request EPS
configuration status
N This management function permits to retrieve the information about
EPS
(Equipment Protection Switching) configuration
of the board. When the ISA board does not support plugable
access cards, this management function simply reports whether or
not the ISA is in EPS protected.
When the ISA board supports plugable access cards, this
management function reports whether the ISA board is EPS
protected and both the main and spare boards are equipped with the
same kind of access
card.
Scope
TSDIM-SNMPNE-MIB: opticsimEpsConfStatus
Service Used
SNMP-GET on opticsimEpsConfStatus object
F- 93. Request EPS role N This management function permits to retrieve the role (i.e. main or
spare) of the active board. If the opticsimEpsConfStatus is false, this
object always report the role main.
Scope
TSDIM-SNMPNE-MIB: opticsimEpsActiveRole
Service Used
SNMP-GET on opticsimEpsActiveRole object
F- 97. Request ISA Access
Card
N This management function permits to retrieve the kind of access
card that is equipped on an ISA board.
If the ISA board is EPS protected, this management function reports
the access card that is equipped on
the main board.
If the ISA board does not support plugable access cards, the
default value unknown (i.e. 0) is returned.
If the ISA board supports plugable access card, but it does not
know the card that is plugged, the default
value unknown (i.e. 0) is returned.
The value 1 is reserved to report that no access card is equipped.
The other values (>1) are used to report the kind of access card that
is equipped. The semantics of the
reported value is product specific and will be documented in the
product external specification.
Scope
TSDIMSNMPNEMIB: opticsimIsaAccess
Service Used
SNMPGET on opticsimIsaAccess object


APPLICABLE


102/ 139


as well.
The general naming rule for the Support domain objects is defined in [11].

Table Entry
Supported Objects
(Table/Scalar/Trap) Description
Index
Value
tsdimSupportMib
tsdimEFDTable
tsdimEFDDest
tsdimEFDTrapId
tsdimEFDTrapObject
tsdimEFDLowestForwardedSeverity
tsdimEFDManagerIndex
tsdimEFDPort
tsdimEFDIndeterminate
tsdimEFDOperStatus
tsdimEFDRowStatus
Max 10 entries 1..N
tsdimAlarmLogTable
tsdimAlarmLogProbableCause
tsdimAlarmLogObjectClassIdentifier
tsdimAlarmLogObjectInstanceIdentifier
tsdimAlarmLogSeverity
tsdimAlarmLogSpecificProb
tsdimAlarmLogTime
Max 125 entries 1..N
tsdimEventLogTable
tsdimEventLogEventType
tsdimEventLogObjectClassIdentifier
tsdimEventLogObjectInstanceIdentifier
tsdimEventLogTime
Max 75 entries 1..N
tsdimLogTable
tsdimLogObjectClassIdentifier
tsdimLogAdminStatus
tsdimLogOperStatus
tsdimLogMaxSize
1..2
tsdimAPTTable
tsdimAPTAlarmProbableCause
tsdimAPTAlarmObjectClassIdentifier
tsdimAPTAlarmObjectInstanceIdentifier
tsdimAPTAlarmSeverity
tsdimAPTAlarmSpecificProb
tsdimAPTAlarmTime
Max 142 entries 1..N
ASAP#1 (predefined) 1
tsdimAlarmSevProfileTable
tsdimAlarmSevProfileRowStatus
tsdimAlarmSevProfileUserLabel
Free use ASAPs (max 3 entries) 5..N
ASAP#1 (predefined) 1; <trapId>
tsdimAlarmSevTable
tsdimAlarmSevSeverity
tsdimAlarmSevRowStatus
tsdimAlarmSevSeverityNotServAff
Free use ASAPs (max 3 entries) 5..N; <trapId>


APPLICABLE


103/ 139

Table Entry
Supported Objects
Index
Value
opticsIMSwdlInitTable
opticsIMSwdlInitForcedDownload
opticsIMSwdlInitSwPkgVersion
opticsIMSwdlInitSwPkgLabel
opticsIMSwdlInitDescrName
opticsIMSwdlInitRowStatus
1
opticsIMSwPackageTable
opticsIMSwPackageCommand
opticsIMSwPackageActivationResult
opticsIMSwPackageActivationDate
opticsIMSwPackageState
opticsIMSwPackageLabel
opticsIMSwPackageVersion
opticsIMSwPackageOperationalState
1..2
1; 1
opticsIMSwUnitVersion
opticsIMSwUnitSize
EC software unit
2; 1
opticsIMAbnCondAffectedObjectListTable
opticsIMAbnCondAffectedObjectInstanceId
Max 14 entries (3 protection switches,
6 loopbacks, 2 manual Tx mute, 2
automatic Tx mute, 1 pseudo random
sequence insertion)
1..N
opticsIMEFDAllEvents
opticsIMEFDAllTraps
opticsIMEFDAllObjects

tsdimObjectCreationNotification
tsdimObjectDeletionNotification
tsdimAVCNotification
tsdimStateChangeNotification

opticsIMSwdlServerAddress
opticsIMSwdlServerPort
opticsIMSwdlServerUserId
opticsIMSwdlServerPassword
opticsIMSwdlServerRootDir
opticsIMSwdlPercentage
opticsIMSwdlTotalBytes
opticsIMSwdlCurrentSwUnitVersion
opticsIMSwdlCurrentSwUnitLabel
opticsIMSwdlResult

opticsIMNERestartRequest

opticsIMActiveAbnCond

system
sysLocation
sysName

opticsIMSwUnitTable
opticsIMSwUnitLabel
sysDescr


APPLICABLE


104/ 139

Table Entry
Supported Objects
Index
Value
tsdimSnmpNEMib
tsdimLacTable
tsdimLacState
tsdimLacNoResponseTimeOutPeriod
1
Undefined configuration 0
Scalable configurations (IDU light) 7
opticsIMAllowedNeConfigurationTypeTable
opticsIMAllowedNeConfigurationType
Scalable configurations (IDU classic) 1..6; 8..9
tsdimSnmpAgtIpAddress (note 1)
tsdimSnmpAgtIpMask (note 1)
tsdimSnmpAgtUdpPort (note 1)
tsdimNeInstallationType
tsdimSdhNeLabel
tsdimInfoModelVersionMajor
tsdimInfoModelVersionMinor
tsdimInfoModelVersionMaintenance
opticsIMExternalTime
opticsIMNTPStatus
opticsIMMainNTPServerAddress
opticsIMSpareNTPServerAddress
opticsIMNTPServersReachabilityStatus

opticsIMAlarmLossOfSignalRaise
opticsIMAlarmLossOfSignalClear
opticsIMAlarmAisRaise
opticsIMAlarmAisClear
opticsIMAlarmCableLOSRaise
opticsIMAlarmCableLOSClear
opticsIMAlarmRxFailRaise
opticsIMAlarmRxFailClear
opticsIMAlarmTxFailRaise
opticsIMAlarmTxFailClear
opticsIMAlarmModLOSRaise
opticsIMAlarmModLOSClear
opticsIMAlarmModFailRaise
opticsIMAlarmModFailClear
opticsIMAlarmDemLOSRaise
opticsIMAlarmDemLOSClear
opticsIMAlarmDemFailRaise
opticsIMAlarmDemFailClear
opticsIMAlarmTCARaise
opticsIMAlarmTCAClear
opticsIMAlarmUnavailableTimeRaise
opticsIMAlarmUnavailableTimeClear
opticsIMAlarmPPPFailRaise
opticsIMAlarmPPPFailClear


APPLICABLE


105/ 139

Table Entry
Supported Objects
Index
Value
opticsIMCommonPmMib
opticsIMFilterHistoryDataTable
opticsIMFilterHDStartByOS
opticsIMFilterHDBeginTimeInterval
opticsIMFilterHDEndTimeInterval
opticsIMFilterHDGranularityPeriod
opticsIMFilterHDRowStatus
Entries created by the manager
(max 10 entries)
1..N
Table 3 Support Domain: Supported Objects and Naming rules 5
(note 1) See Communication and Routing Domain for the management functions.


APPLICABLE


106/ 139

8 COMMUNICATION AND ROUTING DOMAIN

The maximum number of managers connected to the NE is 10.

N.B. The agent answers to the SNMP manager requests (GET and SET) only if the IP address of the
manager is already registered in the opticsIMMgrPollingInfoTable.

The association between Point-To-Point IP interface index, related type and supported modes are
indicated in the following table.

Point-To-Point IP Interfaces
Type Supported Modes
RF Not used
DTE
DCE V.11 (#1)
Asynchronous (Co-directional)
DTE
DCE V.11 (#2)
Asynchronous (Co-directional)
Table 3 Point to Point IP Interfaces Features 6
All these entries in the opticsIMPointToPointIPTable will be created by the agent as a consequence of
the equipment provisioning phase (see Equipment Domain).
The managing systems can:
deactivate these interfaces.
activate these interfaces in one of the available modes.

The only supported routing protocol is OSPF. One single OSPF area is supported. The OSPF area
cannot be a backbone area.

The following table lists the Communication and Routing management functions supported in this release
(see [2]).

Function IP Routing
Management
SNM
PIf
F- 1. Request IP Address
Configuration

P This function allows a managing system to request the managed
system address.
Scope
This function permits to retrieve the IP address, mask and UDP of
the managed system.
Service Used
SNMP-GET on the following scalar objects (defined in TSDIM-
SNMPNE-MIB):
- tsdimSnmpAgtIpAddress
- tsdimSnmpAgtIpMask
- tsdimSnmpAgtUdpPort
Note F-1: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
F- 2. Request OSPF
Configuration
Y This function allows a managing system to request information
about the OSPF protocol routing information.
Scope
This function permits to retrieve the different OSPF Area


APPLICABLE


107/ 139

configurations.
Service Used
SNMP-GET on the following opticsIMOspfAreaTable columnar
objects:
- opticsIMOspfAreaId
- opticsIMOspfAreaIpAddress
- opticsIMOspfAreaIpMask
- opticsIMOspfAreaStubFlag
Y This function allows a managing system to define different IP static
routing paths.
Scope
This function permits to create an IP static routing object.
Service Used
SNMP-SET on the following opticsIMIpStaticRoutingInfoTable
columnar object:
- opticsIMIpStaticIpAddress
- opticsIMIpStaticIpMask
- opticsIMIpStaticDefGateway
- opticsIMIpStaticInterfaceIndex
value.

F- 4. Delete IP Static
Routing Information
Y This function allows a managing system to terminate different IP
routing path objects.
Scope
This function permits to delete an IP routing path object.
Service Used
F- 5. Request IP Static
Routing Information
Y This function allows a managing system to request different IP static
routing paths.
Scope
This function permits to retrieve an IP static routing object.
Service Used
SNMP-GET on the following opticsIMIpStaticRoutingInfoTable
columnar object:
- opticsIMIpStaticIpAddress
- opticsIMIpStaticIpMask
- opticsIMIpStaticDefGateway
- opticsIMIpStaticInterfaceIndex
- opticsIMIpStaticRowStatus
F- 6. Request Routing
Information
all IP routing paths, both static and dynamic.
Scope
This function permits to retrieve data related to all IP routing path
objects.
Service Used
SNMP-GET on the following opticsIMIpRoutingTable columnar
objects:
- opticsIMIpRoutingDestIpAddress
- opticsIMIpRoutingDestIpMask
- opticsIMIpRoutingDefGateway
- opticsIMIpRoutingMetricValue
- opticsIMIpRoutingRouteAge
- opticsIMIpRoutingRouteType
- opticsIMIpRoutingProtocol
- opticsIMIpRoutingLocalPtpInterface
F- 12. Condition IP Address P This function allows a managing system to condition the managed
system address.
F- 3. Create IP Static
Routing Information


APPLICABLE


108/ 139

Scope
This function permits to condition the IP address, mask and UDP of
the managed system.
Service Used
SNMP-SET on the following scalar objects (defined in TSDIM-
SNMPNE-MIB):
- tsdimSnmpAgtIpAddress
- tsdimSnmpAgtIpMask
- tsdimSnmpAgtUdpPort
F- 13. Create OSPF Area N This function allows a managing system to define different OSPF
areas.
Scope
This function permits to create different OSPF Areas.
Service Used
SNMP-SET on the following opticsIMOspfAreaTable columnar
objects:
- opticsIMOspfAreaIpAddress
value.

F- 14. Delete OSPF Area N This function allows a managing system to delete OSPF areas.
Scope
This function permits to delete OSPF Areas.
Service Used
SNMP-SET on RowStatus columnar object of the
opticsIMOspfAreaTable to "destroy" value.
F- 15. Condition OSPF Area Y This function allows a managing system to condition information
about the OSPF area protocol routing information.
Scope
This function permits to condition the different OSPF Area
configurations.
Service Used
SNMP-SET on the following opticsIMOspfAreaTable columnar
objects:

Function Manager Polling
Management
SNM
PIf
F- 7. Create Manager
Polling Information
Y This function allows a managing system to define its polling
information
Scope
This function permits to create an object containing the information
needed to manage the manager polling functionality.
Service Used
SNMP-SET on the following opticsIMMgrPollingInfoTable
columnar object:
- opticsIMMgrPollingIpAddress
- opticsIMMgrPollingUdpPort
- opticsIMMgrPollingTimeOut
- opticsIMMgrPollingManagerType
SNMP-SET on RowStatus columnar object to "createAndWait"
value.
F- 8. Delete Manager Y This function allows a managing system to terminate its polling
Note F-12: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.


APPLICABLE


109/ 139

Polling Information information object.
Scope
This function permits to delete a polling information object.
Service Used
Y This function allows a managing system to request its polling
information.
Scope
This function permits to retrieve its polling information object.
Service Used
SNMP-GET on the following opticsIMMgrPollingInfoTable
columnar object:
- opticsIMMgrPollingIpAddress
- opticsIMMgrPollingUdpPort
- opticsIMMgrPollingManagerType
- opticsIMMgrPollingRowStatus
F- 10. Request Polled
Information
Y This function allows a managing system to request its owns polled
information.
Scope
This function permits to retrieve the polled information object related
to a particular Manager.
Each Manager could read its owns polled information, such as each
manager could have its owns NotificationId and Time associated to
it.
Service Used
SNMP-GET on the following opticsIMInfoPolledTable columnar
object:
- opticsIMInfoIndex
- opticsIMInfoLastAlarmNotificationId
- opticsIMInfoLastAlarmTime
- opticsIMInfoLastEventNotificationId
- opticsIMInfoLastEventTime
- opticsIMInfoLastGenEventNotificationId (if supported)
- opticsIMInfoLastGenEventTime (if supported)
F- 48. Condition Timeout
Polling
Y This function allows a managing system to change the polling
timeout value.
Scope
This function permits to change the polling timeout value. This
operation is feasible also in case the RowStatus is "Active".
Service Used
SNMP-SET on the following opticsIMMgrPollingInfoTable columnar
object:

Function Local Ethernet
Management
SNM
PIf
F- XX. All the functions. N

Function Point-to-Point IP
Interface Management
F- 20. Create Point-To-
Point IP Interface
N This function allows a managing system to create a point-to-point IP
interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on the following columnar objects:
F- 9. Request Manager
Polling Information
SNM
PIf


APPLICABLE


110/ 139

- opticsIMIpPointToPointIPType
- opticsIMIpPointToPointIPMode
- opticsIMIpPointToPointIPRoutingProtocol
- opticsIMIpPointToPointIPOspfAreaPointer
value.
N This function allows a managing system to delete a point-to-point IP
interface.
Scope
Service Used
F- 22. Request Point-To-
Point IP Information
a point-to-point IP interface.
Scope
Service Used
- opticsIMPointToPointIPType
- opticsIMPointToPointIPMode
- opticsIMPointToPointIPRoutingProtocol
- opticsIMPointToPointIPOspfAreaPointer
- opticsIMPointToPointIPRemoteAddress
F- 23. Condition Point-To-
Point IP Information
P This function allows a managing system to condition the parameters
related to a point-to-point IP interface.
Scope
Service Used
SNMP-SET on the following opticsIMIpPointToPointIPTable
columnar objects:
- opticsIMPointToPointIPMode
- opticsIMPointToPointIPRoutingProtocol
- opticsIMPointToPointIPOspfAreaPointer
Note F-23: Routing Protocol conditioning is not supported (can only be OSPF).
F- 24. Activate a Point-To-
Point IP Interface
Y This function allows a managing system to activate a point-to-point
IP interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object to "active" value.
F- 25. Deactivate a Point-
To-Point IP Interface
Y This function allows a managing system to deactivate a point-to-
point IP interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object to "notInService"
value.
F- 26. Report Point-To-
Point IP Interface Alarms
Y This function allows a managed system to report the alarms related
t a point-to-point IP interface.
Scope
Service Used
SNMP-TRAP on:
- opticsIMAlarmLossOfSignalRaise/Clear
- opticsIMAlarmPPPFailRaise/Clear
Note F-26: PPP fail alarm only.

F- 21. Delete Point-To-Point
IP Interface


APPLICABLE


111/ 139

F- 27. Request Point-To-
Point IP Interface ASAP
Pointer
Y This function allows a managing system to request the ASAP
Pointer associated a point-to-point IP interface.
Scope
Service Used
SNMP-GET on opticsIMIpPointToPointIPAsapPointer.
F- 28. Condition Point-To-
Point IP Interface ASAP
Pointer
Y This function allows a managing system to condition the ASAP
Pointer associated a point-to-point IP interface.
Scope
Service Used
SNMP-SET on opticsIMIpPointToPointIPAsapPointer.

Function LAPD
Management

SNM
PIf

SNM
PIf
SNM
PIf

Function IP Tunnel
Management

Function CLNP Tunnel
Management


APPLICABLE


112/ 139


as well.

The general naming rule for the Support domain objects is defined in [11].

Table Entry
Supported Objects
Index
Value
opticsIMMgrPollingInfoTable
opticsIMMgrPollingIpAddress
opticsIMMgrPollingUdpPort
opticsIMMgrPollingTimeOut
opticsIMMgrPollingManagerType
opticsIMMgrPollingRowStatus
Entries created by the managers
(max 10 entries)
1..N
opticsIMInfoPolledTable
opticsIMInfoLastAlarmNotificationId
opticsIMInfoLastAlarmTime
opticsIMInfoLastEventNotificationId
opticsIMInfoLastEventTime
opticsIMInfoLastGenEventNotificationId
opticsIMInfoLastGenEventTime
Entries created as consequence of
managers actions
(max 10 entries)
1..N
opticsIMOspfAreaTable
opticsIMOspfAreaIpAddress
opticsIMOspfAreaIpMask
opticsIMOspfAreaStubFlag
opticsIMOspfAreaRowStatus
1 entry 1
RF 1
2
opticsIMPointToPointIPTable
opticsIMPointToPointIPType
opticsIMPointToPointIPMode
opticsIMPointToPointIPRoutingProtocol
opticsIMPointToPointIPOspfAreaPointer
opticsIMPointToPointIPRemoteAddress
opticsIMPointToPointIPRowStatus
opticsIMPointToPointIPAsapIndex
V11 #2 3
opticsIMIpStaticRoutingInfoTable
opticsIMIpStaticIpMask
opticsIMIpStaticDefGateway
opticsIMIpStaticInterfaceIndex
opticsIMIpStaticRowStatus
Entries created by the managers
(max 10 entries)
<IP address>
opticsIMIpRoutingInfoTable
opticsIMIpRoutingDestIpMask
opticsIMIpRoutingDefGateway
opticsIMIpRoutingMetricValue
opticsIMIpRoutingProtocol
opticsIMIpRoutingLocalPtpInterface
opticsIMIpRoutingRouteAge
opticsIMIpRoutingRouteType
Entries created by the agent on
managers GET requests
<IP address>
opticsIMCommRouMib
V11 #1
Table 3 Communication and Routing Domain: Supported Objects and Naming rules 7


APPLICABLE


113/ 139

9 OVERHEAD DOMAIN

According to the configuration, up to five auxiliary interfaces and one EOW interface are supported by
LUX50 NE. No auxiliary interface is managed through SNMP interface. The related entries will be
created by the agent, according to the NE configuration, during the provisioning phase (see Equipment
domain).

EOW phone number must follow a dedicated numbering policy, which is the following:
Additional auxiliary interfaces are entered in opticsIMEquipmentTable during the provisioning phase as a
reminder, as no other information is available from Remote Inventories.

EOW interface is not available in case of 1+0 configuration with Light IDU.
- Value range for phone number value is 011..999
- Phone number can not contain more than one 0 digit (e.g. 020, 400 are forbidden values).
- Only exception to the above rules is value 007, which is used to indicate that phone number is
disabled.

The following table lists the Overhead management functions supported in this release (see [9]).
EOW Phonic Parameters

PIf
F- 1.1 Request EOW Phone
Number
the phone number associated to an Engineering Order Wire.
Scope
OPTICSIM-OH-MIB: opticsIMEowDTMFTTPBidTable
Service Used
SNMP-GET on: opticsIMEowDTMFTTPBidPhoneNumber
the phone number associated to an Engineering Order Wire.
Scope
OPTICSIM-OH-MIB: opticsIMEowDTMFTTPBidTable
Service Used
SNMP-SET on: opticsIMEowDTMFTTPBidPhoneNumber
F- 1.3 Condition EOW Party
Line
enable/disable the Engineering Order Wire party line feature on
NMS port.
The managing system has to provided in the request the index of
EOW table (identified by ifIndex), the port type of NMS port (nms-
v11 or nms-g703) and the port identifier (identified by
opticsIMPointToPointIPId of opticsIMPointToPointIPTable).
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-SET on: opticsIMEowPartyLineEnabled
F- 1.4 Request EOW Party
Line
the Engineering Order Wire party line feature on NMS port is
enabled or disabled.
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
F- 1.2 Condition EOW
Phone Number


APPLICABLE


114/ 139

Service Used
SNMP-GET on: opticsIMEowPartyLineEnabled

Auxiliary Interfaces

PIf

PIf

PIf

Overhead Bytes

PIf

PIf


as well.
The general naming rule for the Overhead objects is defined in [11].

Table Entry
Supported Objects
(Table/Scalar/Trap) Configuration Description
Index
Value
opticsIMOverheadMib
opticsIMEowDTMFTTPBidTable
opticsIMEowDTMFTTPBidPhoneNumber
All except 1+0L EOW port 1
Table 38 Overhead Domain: Supported Objects and Naming rules


APPLICABLE


115/ 139

10 TEST DOMAIN

The functions described in this section are used to control and monitor the test operations. All the entries
related to the loopbacks tables will be created by the agent as consequence of the equipment
provisioning phase (see Equipment Domain). The managing systems can only activate/deactivate the
loopbacks.

The supported loopback points are the following:

IDU
Near-End Tributary Loopback Internal
This loopback can be activated on each PDH tributary (Rx side).
According to the frame structure configuration, this type of loopback refers to instances of
opticsIME1PathTTPTable or opticsIME3PathTTPTable.
Tributary loopbacks are exclusive: only one tributary loopback can be activated at a time (when a
tributary loopback is activated, previously activated loopback on another tributary, if any, is
automatically deactivated by the NE). This behavior also applies between E3 and auxiliary E1 in
34+2Mbps configurations.
Near-End IDU Cable Loopback Line Local only
This loopback can be activated on instances of opticsIMCoderTTPTable.

ODU
Near-End ODU Cable Loopback Line Local only
This loopback can be activated on instances of opticsIMRadioPDHTTPBidTable.
Near-End RF Loopback Line Local only
This loopback can be activated on instances of opticsIMRadioPDHTTPBidTable, if, according to
equipment provisioning, the RF loopback is allowed.
N.B. Loopback types defined as Local only can be activated only by managers directly connected to
the NEs F interface. In other words, these loopback types can be activated a by local craft terminal, but
cannot be activated by remote craft terminal and OS.
The modality of work of all of these types of loopbacks is Loop-And-Continue.


APPLICABLE


116/ 139


The following table lists the Test management functions supported in this release (see [8]).

Function Configuration Function Description
F- 1 Request Loopback
Configuration
the chracteristics (TP to be tested, direction and behaviour of the
loopback) and the activation status (active or not active) of the
loopback.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-GET on:
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-SET on loopbackActivation
F- 3 Request Near-End/Far-
End Loopback Type
the loopback is referred to the Near-End or Far-End NE and the type
of managers that can require the loopback activation.
This function will be used when a loopbacks management on radio
link base is supported.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackExtTable
Service Used
SNMP-GET on:
SNM
PIf
- loopbackPointObjectInstance
- loopbackDirectionality
- loopbackPointAdditionalDefinition
- loopbackBehaviour
- loopbackActivation
F- 2 Condition Loopback
Activation
Y This management function allows the managing system to activate a
loopback test.
- loopbackNEType
- loopbackAllowedManager


APPLICABLE


117/ 139

The Test SNMP tables, columnar and scalar objects supported by this release are the following:

opticsIMTestMib

opticsIMLoopbackTable
loopbackPointObjectInstance
loopbackDirectionality
loopbackPointAdditionalDefinition
loopbackBehaviour
loopbackActivation

The general naming rules of the Test objects are defined in [11]. See the Functional Description
paragraph for the application to LUX50 NE. The following tables provides the list of loopback points, with
the associated characteristics, supported in the current release.

Object Instance Configu
-ration
Loopback
Tables
Indexes
TP Table TP Index
NE
Type
Additional
Def.
Directio-
nality
IDU
1;
1..16
opticsIME1PathTTPTable 2zz01
(note 2)
near
end
<trib> Port#xx
(note 2)
Internal 1+0 /
1+1
1;
1
opticsIME3PathTTPTable 22101 near
end
<trib> Port#1 Internal
1..16
opticsIME1PathTTPTable 2zz99
(note 2)
near
end
<trib> Port#xx
(note 2)
Internal 1+1 MP
Common;
1
opticsIME3PathTTPTable 22199 near
end
<trib> Port#1 Internal
1+0 1;
17
opticsIMCoderTTPTable 20101 near
end
IDU Cable External
Line
1+1 /
1+1 MP
Common;
17
opticsIMCoderTTPTable 20199 near
end
IDU Cable External
Line
ODU
1;
18
opticsIMRadioPDHTTPBidTable 20101 near
end
ODU Cable External
Line
All
1;
19
end
RF (note 3) External
Line
18
end
ODU Cable External
Line
1+1 /
1+1 MP
0;
19
end
RF (note 3) External
Line
(note 1)
Common;
0;
Table 39 Test Domain: Supported Objects and Naming rules
1+0: 1+0 / 1+0L / 1+0EXT
1+1: 1+1HSB / 1+1HSB-SD / 1+1FD
(note 2) xx = 01..16 / zz = 21..36 for nx2Mbps configurations xx = 2 / zz = 22 for 34+2Mbps
configurations.
(note 3) Availability of this loopback depends on provisioned ODU RF Loopback.


APPLICABLE


118/ 139

11 SDH/PDH PERFORMANCE MONITORING DOMAIN

Performance monitoring of the radio hop and link sections are supported in the current release. The link
section quality monitoring can be activated only in case of 1+1 configurations (in all the other
configurations hop and link sections provide the same quality), the related monitoring point follows the
position of the EPS switch.

Both types of PM support the same kinds of counters:
Errored Seconds
Severely Errored Seconds
Background Block Error
Unavailable Seconds

The table below provides the list of monitoring points:

PM Point
TP Table TP Index
Configuration
All the configurations opticsIMPdhFrameHopCurrentDataTable
20100 All the 1+1 configurations
opticsIMPdhFrameLinkCurrentDataTable 20199 All the 1+1 configurations
20101
Table 40 Performance Monitoring Point
All the entries related to the performance monitoring tables will be created by the agent as a
consequence of the equipment provisioning phase (see Equipment Domain). The managing systems can
only activate/deactivate the monitoring.

The following tables list the PM management functions supported in this release (see [6]).

SDH Performance Monitoring Measurement Collection

Function Creation of SDH
Current Data Entry
SNM
PIf

Function Configuration of
SDH Current Data Mode
SNM
PIf

Function Request of SDH
Current Data
SNM
PIf

Function Release of SDH
Current Data Entry
SNM
PIf
N

SDH History Data
SNM
PIf

F- XX. All the functions.


APPLICABLE


119/ 139

Function Request of SDH
History Data
SNM
PIf

Function Creation of SDH
Threshold Data Entry

SDH Threshold Data
SNM
PIf

Function Release of SDH
SNM
PIf

Function Report of SDH
Alarms
SNM
PIf

PDH Frame and Tributary Performance Monitoring Measurement Collection
All the functions below apply to:
opticsIMPdhFrameLinkCurrentDataTable
opticsIMPdhFrameLinkHistoryDataTable
opticsIMPdhFrameLinkThresholdDataTable

Function Creation of PDH
Frame and Tributary
Current Data Entry
SNM
PIf
F- 4.1 Create CD Entry N This management function permits to allocate one CD entry. The
management system has to indicate in the creation request:
1) the monitoring point which it is associated to (indicated by means
of ifIndex)
2) the CD index (pm<Layer>CDIndex), which indicates the
granularity period of the counter (15 min or 24 h)
Scope
OPTICSIM-PDH-PM-MIB: opticsIM<Layer>CurrentDataTable
Service Used
SNMP-SET on the following columnar objects (optionally):
SNMP-SET on pm<Layer>CDRowStatus columnar object to
"createAndGo " value

PDH Frame and Tributary
Current Data Mode
SNM
PIf
F- 4.3 Request Elapsed Y This management function permits to request the elapsed time in the
SNM
PIf
Current Data => opticsIMPdhFrameHopCurrentDataTable
History Data => opticsIMPdhFrameHopHistoryDataTable
Threshold Data => opticsIMPdhFrameHopThresholdDataTable
- pm<Layer>CDMaxSuppressedIntervals
- pm<Layer>CDThresholdDataInstance
- pm<Layer>CDAsapIndex


APPLICABLE


120/ 139

Time current interval.
Scope
Service Used
SNMP-GET on pm<Layer>CDElapsedTime
Note F-4.3: Elapsed time is measured in seconds.
F- 4.4 Request Granularity
Period
Y This management function permits to request the granularity period
(15 min or 24 h).
Scope
Service Used
SNMP-GET on pm<Layer>CDGranularityPeriod
F- 4.5 Condition Max
Suppressed Interval
N This management function permits to condition the maximum
number of intervals which can be suppressed.
Scope
Service Used
SNMP-SET on pm<Layer>CDMaxSuppressedIntervals
F- 4.6 Request Max
Suppressed Interval
Y This management function permits to request the Max Suppressed
Interval.
Scope
Service Used
SNMP-GET on pm<Layer>CDMaxSuppressedIntervals
F- 4.8 Request Number of
Suppressed Intervals
Y This management function permits to request the Number of
Suppressed Intervals.
Scope
Service Used
SNMP-GET on pm<Layer>CDNumSuppressedIntervals
F- 4.9 Request Suspect
Interval Flag
Y This management function permits to request whether the current
data is suspect or not.
Scope
Service Used
SNMP-GET on pm<Layer>CDSuspectIntervalFlag
F- 4.10 Reset Suspect
Interval Flag
N This management function permits to reset the Suspect Interval
Flag.
Scope
Service Used
SNMP-SET to default value on pm<Layer>CDSuspectIntervalFlag
F- 4.11 Request Start By
OS
N This management function permits to identify the Management
System which started the measurement.
Scope
Service Used
SNMP-GET on pm<Layer>CDStartByOS
F- 4.13 Reset PM Data
Collection
Y This management function permits to reset to 0 the PM Data
Collection. The following counters can be reset:
Scope
Service Used
- BBE (note 1)
- ES
- SES
- UAS


APPLICABLE


121/ 139

SNMP-SET to default Value on:
pm<Layer>CDSes
pm<Layer>CDUas
pm<Layer>CDBbe (note1)
pm<Layer>CDEs
(note 1) not available for <Layer>="Ds3"
Y This management function permits to activate one CD entry.
It can be used:
Scope
Service Used
SNMP-SET on pm<Layer>CDRowStatus columnar object to "active"
value
F- 4.14 Deactivate CD Entry Y This management function permits to deactivate one CD entry to
stop the counters.
Scope
Service Used
"notInService" value
F- 4.16 Condition CD Asap
Pointer
Y This management function permits to set the ASAP Pointer related
to a CD entry.
Scope
Service Used
SNMP-SET on pm<Layer>CDAsapIndex
F- 4.17 Request CD Asap
Pointer
Y This management function permits to request the ASAP Pointer
related to a CD entry.
Scope
Service Used
SNMP-GET on pm<Layer>CDAsapIndex

Function Request of PDH
Frame and Tributary
Current Data
SNM
PIf
F- 4.12 Request PM Data
Collection
Y This management function permits to Request PM Data Collection.
The following counters can be retrieved:
Scope
Service Used
SNMP-GET on:
pm<Layer>CDSes
pm<Layer>CDUas
pm<Layer>CDBbe (note 1)
pm<Layer>CDEs

F- 4.2 Activate CD Entry
-
- in case the CD is deactivated by the Agent (e.g. if TD pointer
does not point to an existing TD) to activate it.
in case CD has been stopped by the Network Management
System, by means of F-4.14, to restart it.
- BBE (note 1)
- ES
- SES
- UAS


APPLICABLE


122/ 139

Function Release of PDH
Frame and Tributary
Current Data Entry
SNM
PIf
Scope
Service Used
"destroy" value

Function Report of PDH
Frame and Tributary PM
Alarms
SNM
PIf
F- 4.18 Report of CD
Alarms
Y This management function permits to report TCA and UAT Alarms.
Scope
Service Used

History Data
SNM
PIf
F- 5.1 Request Elapsed
Time
Y This management function permits to request the elapsed time in the
current interval.
Scope
OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable
Service Used
SNMP-GET on pm<Layer>HDElapsedTime
F- 5.2 Request Granularity
Period
Y This management function permits to request the granularity period
(15 min or 24 h).
Scope
Service Used
SNMP-GET on pm<Layer>HDGranularityPeriod
F- 5.4 Request Number of
Suppressed Intervals
Y This management function permits to request the Number of
Suppressed Intervals.
Scope
Service Used
SNMP-GET on pm<Layer>HDNumSuppressedIntervals
F- 5.5 Request Suspect
Interval Flag
Y This management function permits to request whether the History
data is suspect or not.
Scope
Service Used
SNMP-GET on pm<Layer>HDSuspectIntervalFlag
F- 5.6 Request Start By OS N This management function permits to identify the Management
System which started the measurement.
Scope
Service Used
SNMP-GET on pm<Layer>HDStartByOS

F- 4.15 Delete CD Entry N This management function permits to delete one CD entry.
- opticsIMAlarmThresholdCrossRaise
- opticsIMAlarmThresholdCrossClear
- opticsIMAlarmUnavailableTimeRaise
- opticsIMAlarmUnavailableTimeClear


APPLICABLE


123/ 139

Function Request of PDH
Frame and Tributary
History Data
SNM
PIf
F- 5.7 Request PM Data
Collection
Y This management function permits to request PM Data Collection.
The following counters can be retrieved:
Scope
Service Used
SNMP-GET on:
pm<Layer>HDBbe (note 1)
pm<Layer>HDEs
pm<Layer>HDSes
pm<Layer>HDUas

Function Creation of PDH
Frame and Tributary
SNM
PIf
F- 6.1 Create Threshold
Data Entry
N This management function permits to allocate one Threshold Data
entry. The management system has to indicate in the creation
request the index for the threshold data entry, which the
management system has previously got from the agent (GET on
opticsIM<Layer>ThrIndexNext).
Scope
OPTICSIM-PDH-PM-MIB: opticsIM<Layer>ThresholdDataTable
Service Used
SNMP-GET on opticsIM<Layer>ThrIndexNext
SNMP-SET on pm<Layer>RowStatus columnar object to
"createAndGo " value

Threshold Data
SNM
PIf
F- 6.3 Condition PM
Thresholds Assignment
N This management function permits to assign thresholds to PM
counters.
The thresholds are assigned setting, in the relative CD, the
Threshold Data Instance providing the Threshold values.
Scope
Service Used
SNMP-SET on pm<Layer>CDThresholdDataInstance
F- 6.4 Request PM
Thresholds Assignment
Y This management function permits to request the assignment of
thresholds to PM counters.
Scope
Service Used
SNMP-GET on pm<Layer>CDThresholdDataInstance
F- 6.5 Condition PM
Thresholds
Y This management function permits to configure the thresholds for
PM counters.
The high and low thresholds for the following counters can be set:
- BBE (note 1)
- ES
- SES
- UAS

- BBE (note 1)
- ES


APPLICABLE


124/ 139

- SES
Scope
Service Used
SNMP-SET on
pm<Layer>BbeHighThr (note 1)
pm<Layer>BbeLowThr (note 1)
pm<Layer>EsHighThr
pm<Layer>EsLowThr
pm<Layer>SesHighThr
pm<Layer>SesLowThr
The high and low thresholds for the following counters can be read:
Scope
Service Used
SNMP-SET on
pm<Layer>BbeHighThr (note 1)
pm<Layer>BbeLowThr (note 1)
pm<Layer>EsHighThr
pm<Layer>EsLowThr
pm<Layer>SesHighThr
pm<Layer>SesLowThr
(note 1) not available for <layer>="Ds3"
F- 6.9 Condition Threshold
Data User Label
N This management function permits to configure the User Label
associated to a Threshold Data entry.
Scope
Service Used
SNMP-SET on pm<Layer>UserLabel
F- 6.10 Request Threshold
Data User Label
N This management function permits to request the User Label
associated to a Threshold Data entry.
Scope
Service Used
SNMP-GET on pm<Layer>UserLabel

Function Release of PDH
Frame and Tributary
SNM
PIf
F- 6.8 Delete Threshold
Data Entry
N This management function permits to delete one Threshold Data
entry.
Scope
Service Used
SNMP-SET on pm<Layer>RowStatus columnar object to "destroy"
value
F- 6.6 Request PM
Thresholds
Y This management function permits to request the thresholds for PM
counters.
-
- BBE (note 1)
- ES
SES


APPLICABLE


125/ 139

For each table the index values of all the supported entries are provided too.
The general naming rules for the SDH/PDH Performance Monitoring objects are defined in [11].

Table Entry
Supported Objects
Index
Value
opticsIMPdhPmMib
15 min. Ch#1 20101; 1
All the 1+1 15 min. Ch#0 20100; 1
All 24 h Ch#1 20101; 2
opticsIMPdhFrameHopCurrentDataTable
pmPdhFrameHopCDElapsedTime
pmPdhFrameHopCDGranularityPeriod
pmPdhFrameHopCDMaxSuppressedIntervals
pmPdhFrameHopCDNumSuppressedIntervals
pmPdhFrameHopCDSuspectIntervalFlag
pmPdhFrameHopCDThresholdDataInstance
pmPdhFrameHopCDSes
pmPdhFrameHopCDUas
pmPdhFrameHopCDBbe
pmPdhFrameHopCDEs
pmPdhFrameHopCDRowStatus
pmPdhFrameHopCDAsapIndex
All the 1+1 24 h Ch#0 20100; 2
All 15 min. Ch#1 20101; 1
period x
(x=1..96)
All the 1+1 15 min. Ch#0 20100; 1
period x
(x=1..96)
All 24 h Ch#1 20101; 2
period x
(x=1..8)
opticsIMPdhFrameHopHistoryDataTable
pmPdhFrameHopHDElapsedTime
pmPdhFrameHopHDGranularityPeriod
pmPdhFrameHopHDNumSuppressedIntervals
pmPdhFrameHopHDSuspectIntervalFlag
pmPdhFrameHopHDSes
pmPdhFrameHopHDUas
pmPdhFrameHopHDBbe
pmPdhFrameHopHDEs
All the 1+1 24 h Ch#0 20100; 2
period x
(x=1..8)
opticsIMPdhFrameHopThresholdDataTable
pmPdhFrameHopSesHighThr
pmPdhFrameHopSesLowThr
pmPdhFrameHopBbeHighThr
pmPdhFrameHopBbeLowThr
pmPdhFrameHopEsHighThr
pmPdhFrameHopEsLowThr
pmPdhFrameHopRowStatus
All 1..2
All


APPLICABLE


126/ 139

Table Entry
Supported Objects
Index
Value
All the 1+1 15 min. Ch#Common 20199; 2 opticsIMPdhFrameLinkCurrentDataTable
pmPdhFrameLinkCDElapsedTime
pmPdhFrameLinkCDGranularityPeriod
pmPdhFrameLinkCDMaxSuppressedIntervals
pmPdhFrameLinkCDNumSuppressedIntervals
pmPdhFrameLinkCDSuspectIntervalFlag
pmPdhFrameLinkCDThresholdDataInstance
pmPdhFrameLinkCDSes
pmPdhFrameLinkCDUas
pmPdhFrameLinkCDBbe
pmPdhFrameLinkCDEs
pmPdhFrameLinkCDRowStatus
pmPdhFrameLinkCDAsapIndex
All the 1+1 24 h Ch#Common 20199; 2
All the 1+1 15 min. Ch#Common 20199; 2
period x
(x=1..96)
opticsIMPdhFrameLinkHistoryDataTable
pmPdhFrameLinkHDElapsedTime
pmPdhFrameLinkHDGranularityPeriod
pmPdhFrameLinkHDNumSuppressedIntervals
pmPdhFrameLinkHDSuspectIntervalFlag
pmPdhFrameLinkHDSes
pmPdhFrameLinkHDUas
pmPdhFrameLinkHDBbe
pmPdhFrameLinkHDEs
All the 1+1 24 h Ch#Common 20199; 2
period x
(x=1..8)
opticsIMPdhFrameLinkThresholdDataTable
pmPdhFrameLinkSesHighThr
pmPdhFrameLinkSesLowThr
pmPdhFrameLinkBbeHighThr
pmPdhFrameLinkBbeLowThr
pmPdhFrameLinkEsHighThr
pmPdhFrameLinkEsLowThr
pmPdhFrameLinkRowStatus
All the 1+1 1..2
Table 41 Performance Monitoring Domain: Supported Objects and Naming rules


APPLICABLE


127/ 139

12 ALARMS
12.1 Alarms Provided by Item HW

URU alarms are not supported.

Legenda:
SA = always Service Affecting
NSA = always Not Service Affecting
SAac = Service Affecting when the alarm is present on the active channel, Not Service
Affecting when it is present on the stand-by channel
IDU Alarms

Service Affecting
Evaluation
Equipment
Expected
Alarm Description
1+1 1+1MP
IDU10
IDU10L
IDU10EXT
IDU11
Unconfigured Equipment SA
Equipment Type
1+0
IDU
IDU11MP
SA SA
Table 42 IDU Alarms
IDU/MAIN Alarms

Service Affecting
Evaluation Equipment Type
1+0 1+1 1+1MP
Card Fail (replaceable unit problem) SA SA SAac
Equipment Mismatch NSA NSA NSA
Provisioning Mismatch NSA NSA NSA
Remote inventory failure NSA NSA NSA
Link Identifier Mismatch SA SA SA
Loss of Signal of PDH tributary (Tx
side)
SA SA SAac
PDH-AIS egressing (Rx side) SA SA SAac
PDH-AIS ingressing (Tx side) SA SA SAac
PPP IP Fail NSA NSA NSA
Housekeeping Alarm NSA NSA NSA
Main Unit:

IDU main Light

IDU Main Classic 4x2Mbs

IDU Main Classic 8x2Mbs

IDU Main Classic
16x2Mbs

IDU Main Classic
34+2Mbs

MAINL

MAIN4X2

MAIN8X2

MAIN16X2

MAIN34
NSA NSA
Equipment
Expected
Alarm Description
High BER SA SAac SAac

IDUFAN
(note 1)
Card Fail NSA NSA NSA
Feature key missing (see Unit
missing) (note 3)
SA SA SA
Feature key modified (see
provisioning mismatch)
SA SA
Software Key IDUSKU
Remote inventory failure NSA NSA
Power Supply IDUPSU Card Fail NSA
Note 2: SKUs are on IDU Main classic only, not IDU Main light.
Fan
(note 2)
SA
NSA
Table 4 IDU/MAIN Alarms 3
Note 1: FANs are on IDU Main classic only, not IDU Main light.
Note 3: Service will be off 24h after the beginning of the alarm.


APPLICABLE


128/ 139

IDU/EXT Alarms

Service Affecting
Evaluation Equipment Type
Equipment
Expected
Alarm Description
1+0 1+1 1+1MP
Unit Missing NSA SAac SAac (*1)
Card Fail (replaceable unit problem) NSA SA SAac (*1)
Equipment Mismatch NSA SA SA (*1)
Provisioning mismatch NSA NSA NSA
Remote inventory failure NSA NSA NSA
Link Identifier Mismatch - SA SA (*1)
Loss of Signal of PDH tributary (Tx
side)
- - SAac (*1)
PDH-AIS egressing (Rx side) - - SAac (*1)
PDH-AIS ingressing (Tx side) - - SAac (*1)
Extension Unit:

IDU Extension Basic

IDU Extension Classic
4x2Mbs

8x2Mbs

16x2Mbs

34Mbs

EXT11

EXT4X2

EXT8X2

EXT16X2

EXT34

High BER - SAac SAac
Fan IDUFAN Card Fail NSA NSA NSA (*1)
Power Supply IDUPSU Card Fail NSA NSA NSA
ESC #3 ESC64G703
ESC4WA
ESC64V11
ESC64V28
ESCDAV11
ESCDAV28
ESC#4 ESC64G703
ESC4WA
ESC64V11
ESC64V28
ESCDAV11
ESCDAV28
Table 44 IDU/EXT Alarms
(*1) : all IDU Extensions except IDU Extension Basic.


APPLICABLE


129/ 139

ODU Alarms

Service Affecting
Evaluation
Equipment
Type
Equipment
Expected
Alarm Description
1+0 1+1 FD 1+1 HSB
Card Fail SA SAac SAac
Unit missing SA SAac SAac
Equipment Mismatch SA SAac SAac
Provisioning Mismatch SA SA SA
Remote Inventory Missing NSA NSA NSA
Cable Loss IDU SA SAac SAac
Low BER NSA NSA NSA
Early Warning NSA NSA NSA
Loss of Signal for the Modulation
Function
SA NSA SAac
Modulation Function Failure SA NSA SAac
Loss of Signal for the Demodulation
Function
SA NSA SAac
Demodulation Function Failure SA SAac SAac
Provisioned Frequency incompatible
with actual HW
SA SAac SAac
Provisioned Tx Power incompatible with
actual HW
NSA NSA NSA
Receiving Function Failure SA SAac SAac
ODU ODU78G4Q
ODU78G16Q

ODU13G4QR
ODU13G4Q
ODU13G16Q

ODU15GSP
ODU15GHP
ODU15G4QR

ODU18GSP
ODU18GHP

ODU23G4Q
ODU23G16Q

ODU25G4Q
ODU25G16Q

ODU38G4Q
ODU38G16Q

ODUUXFLAT
Transmission Function Failure SA NSA SAac
Table 45 ODU Alarms


APPLICABLE


130/ 139

12.2 Alarms Reported

The following table provides all the alarm types supported in this release along with the notification type
used to notify the alarm and the object that identifies the resource generating the alarm.

Items to point out:

No transmission alarm is reported on ifTable, the related alarms are reported on the associated
extension tables (see section 4).

The Equipment Label field defined in the Equipment Alarm tables (IDU and ODU are omitted in
these tables for abbreviation purpose) for each slot and sub-slot, has to be used as specific
problem field of each notification (tsdimAlarmSpecProblem) sent on entries of the
opticsIMEquipmentTable.
Concerning the Threshold Crossing Alarms (TCA), indication of which counter has crossed the
threshold has to be provided in the specificProblem parameter of the related alarm trap, using
the OID of the counter.

Prefixes opticsIM/tsdim and opticsIMAlarm are omitted in the Notification Type and Table/Scalar
columns.
The Notification Type column refers to both raise and clear notifications.

12.2.1 Equipment Alarms

Objects
Alarm Description Notification Type (Mib) Table/Scalar
(Mib)
Index
Value
Equipment
Label
Housekeeping Alarm HousekeepingAlarm
(opticsIMEqptMib)
ExternalInputPoint
(opticsIMEqptMib)
1..8
Card Fail ReplaceableUnitProblem
(opticsIMEqptMib)
1.1.1.0
1.1.1.1
1.1.1.2
1.1.2.0
1.1.2.1
1.1.2.2
1.2.0.0
MAIN Ch#1
EXT/PSU Ch#0
1.3.0.0
MAIN/PSU Ch#1
MAIN/FAN Ch#1
EXT Ch#0
EXT/FAN Ch#0
ODU Ch#1
ODU Ch#0
Card Missing ReplaceableUnitMissing
(opticsIMEqptMib)
1.1.1.3
1.1.2.0
1.2.0.0
1.3.0.0
MAIN/SKU
EXT Ch#0
ODU Ch#1
ODU Ch#0
Equipment Mismatch ReplaceableUnitTypeMismatch
(opticsIMEqptMib)
1.1.1.0
1.1.2.0
1.2.0.0
1.3.0.0
MAIN Ch#1
EXT Ch#0
ODU Ch#1
ODU Ch#0
Provisioning Mismatch ProvisioningMismatch
(opticsIMEqptMib)
1.1.1.0
1.1.1.3
1.1.2.0
1.1.2.3
1.1.2.4
1.2.0.0
1.3.0.0
MAIN Ch#1
MAIN/SKU
EXT Ch#0
EXT/ESC #3
EXT/ESC #4
ODU Ch#1
ODU Ch#0
Remote Inventory Failure RemoteInventoryFailure
(opticsIMEqptMib)
1.1.1.0
1.1.1.3
1.1.2.0
1.2.0.0
1.3.0.0
MAIN Ch#1
MAIN/SKU
EXT Ch#0
ODU Ch#1
ODU Ch#0
Unconfigured Equipment UnconfiguredEquipmentPresent
(opticsIMEqptMib)
EquipmentTable
(opticsIMEqptMib)
1.1.0.0 IDU
Table 4 Equipment Alarms Reported 6


APPLICABLE


131/ 139

12.2.2 Communication Alarms

Objects
Alarm Description Notification Type (Mib)
Table/Scalar (Mib) Index Value
Cable LOS IDU CableLOS
(tsdimSnmpNEMib)
High BER HighBER
(opticsIMRadioTrsCommonMib)
CoderTTPTable
[tsdimSnmpNEMib)
20101
20100
Loss of Signal of PDH
tributary
LossOfSignal
(tsdimSnmpNEMib)
PDH-AIS ingressing (Tx side) Ais
(tsdimSnmpNEMib)
E1pPITTPTable
(opticsIMTrsCommonMib)
1xx01 or
1xx99
E3pPITTPTable
(xx = 01..16)
(note 1)
PDH-AIS egressing (Rx side) Ais
(tsdimSnmpNEMib)
E1PathTPTable
E3PathTPTable
2zz01 or
2zz99
(zz = 21..36)
(note 1)
Link Identifier Mismatch LinkIdentifierMismatch
FrameTTPTable
20101
20100
TCA on Hop Section TCA
(tsdimSnmpNEMib)
UAT on Hop Section UnavailableTime
(tsdimSnmpNEMib)
PdhFrameHopCurrentDataTable
(opticsIMPdhPmMib)
20101; 1
20101; 2
20100; 1
20100; 2
TCA on Link Section TCA
(tsdimSnmpNEMib)
UAT on Link Section UnavailableTime
(tsdimSnmpNEMib)
PdhFrameLinkCurrentDataTable
(opticsIMPdhPmMib)
20199; 1
20199; 2
PPP IP Fail PPPFail
(tsdimSnmpNEMib)
PointToPointIPTable
(opticsIMCommRouMib)
1
2
3
Low BER LowBER
Early Warning EarlyWarning
Provisioned Frequency
incompatible with actual HW
IncompatibleFrequency
Provisioned Tx Power
incompatible with actual HW
IncompatiblePTX
Receiving Function Failure RxFail
(tsdimSnmpNEMib)
Transmission Function
Failure
TxFail
(tsdimSnmpNEMib)
Loss of Signal for the
Demodulation Function
DemLOS
(tsdimSnmpNEMib)
Demodulation Function
Failure
DemFail
(tsdimSnmpNEMib)
Loss of Signal for the
Modulation Function
ModLOS
(tsdimSnmpNEMib)
Modulation Function Failure ModFail
(tsdimSnmpNEMib)
RadioPDHTTPBidTable
(opticsIMRadioTrsPdhMib)
20101
20100
Table 4 Communication Alarms Reported 7
(note 1) Index value must be chosen according to the NE configuration. See the naming rules.


APPLICABLE


132/ 139

12.3 Predefined ASAP Severity

The following tables provide the content of the four predefined ASAPs. As the notification types (probable
causes) included in the predefined ASAPs are configuration-dependent, the Config. column defines the
configurations in which the probable cause must be included.
If no indication is provided, this means that the probable cause must be included in all the configurations.

The severity defined in the following tables concerns the 1+1 configurations (when needed, the severity
for SA and NSA is different).
As a general rule, the severity for 1+0 configurations is obtained using the SA severity also for the NSA
one (if they are different).

ASAP#1 (No Alarm) is not showed in these tables: the severity of all notification types (probable causes)
is always NAL independently from service dependency (SA and NSA).

Legenda:
NAL: Non Alarm
MAJ: MAJor
MIN: MINor
WAR: WARning

Communication Alarms

Primary Alarms
ASAP#2
No Remote
Alarms
ASAP#3
All Alarms
ASAP#4 NotificationType Config.
SA NSA SA NSA SA NSA
Ais NAL NAL NAL NAL MAJ MIN
CableLOS MAJ MIN MAJ MIN MAJ MIN
DemFail MAJ MIN MAJ MIN MAJ MIN
DemLOS MAJ MAJ MAJ MAJ MAJ MAJ
EarlyWarning NAL NAL WAR WAR WAR WAR
HighBER MIN WAR MIN WAR MIN WAR
IncompatibleFrequency MAJ MIN MAJ MIN MAJ MIN
IncompatiblePTX WAR WAR WAR WAR WAR WAR
LinkIdentifierMismatch MAJ MIN MAJ MIN MAJ MIN
MAJ MAJ MIN
LowBER NAL NAL WAR WAR WAR WAR
ModLOS MAJ MIN MAJ MIN MAJ MIN
ModFail MAJ MAJ MAJ MAJ MAJ MAJ
PPPFail MIN MIN MIN MIN MIN MIN
RxFail MAJ MIN MAJ MIN MAJ MIN
TCA MAJ MIN MAJ MIN MAJ MIN
TxFail MAJ MIN MAJ MIN MAJ MIN
UnavailableTime MAJ MIN MAJ MIN MAJ MIN
LossOfSignal MIN MAJ MIN
Table 48 Predefined ASAP Severity for Communication Alarms


APPLICABLE


133/ 139

Equipment Alarms

Primary Alarms
ASAP#2
All Alarms
ASAP#4 Notification Type Config.
SA SA NSA SA NSA
HousekeepingAlarm MAJ WAR WAR MIN MIN MAJ
ReplaceableUnitMissing MAJ MIN MAJ MIN MAJ MIN
ReplaceableUnitProblem MAJ MIN MAJ MIN MAJ MIN
ReplaceableUnitTypeMismatch MAJ MIN MAJ MIN MAJ MIN
UnconfiguredEquipmentPresent WAR WAR WAR WAR WAR WAR
RemoteInventoryFailure MIN MIN MIN MIN MIN MIN
ProvisioningMismatch MAJ MIN MAJ MIN MAJ MIN
No Remote
AlarmsASAP#3
NSA
Table 49 Predefined ASAP Severity for Equipment Alarms


APPLICABLE


134/ 139

APPENDIX A ODU DETAILED CHARACTERISTICS
A.1 ODU LX/UX Transceiver 7-8 GHz 4QAM
Remote Inventory: 3CC08952AAxx
Settable Power
Level
Modulation RF Loopback
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
No 4QAM Yes 24 24 119 Tx < Rx 7100 8500
Rx < Tx 7100 8500
126 Tx < Rx 7100 8500
Rx < Tx 7100 8500
151,614 Tx < Rx 7100 8500
Rx < Tx 7100 8500
154 7100 8500
Rx < Tx 7100 8500
160 Tx < Rx 7100 8500
Rx < Tx 7100 8500
161 Tx < Rx 8500 7100
7100 Rx < Tx 8500
7100 8500
Rx < Tx 7100 8500
305,56 Tx < Rx 7100 8500
7100 Rx < Tx 8500
311,32 Tx < Rx 7100 8500
Rx < Tx 7100 8500
Tx Fmax
(MHz)
Tx < Rx
182 Tx < Rx
A.2 ODU LX/UX Transceiver 7-8 GHz 16QAM
Remote Inventory: 3CC08952ABxx
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx Fmin
(MHz)
Tx Fmax
(MHz)
No 16QAM Yes 21 21 119 Tx < Rx 7100 8500
Rx < Tx 7100 8500
Tx < Rx 7100 126 8500
8500 Rx < Tx 7100
151,614 Tx < Rx 7100 8500
Rx < Tx 7100 8500
154 Tx < Rx 7100 8500
Rx < Tx 7100 8500
160 Tx < Rx 7100 8500
Rx < Tx 7100 8500
161 Tx < Rx 7100 8500
Rx < Tx 7100 8500
182 Tx < Rx 7100 8500
Rx < Tx 7100 8500
305,56 Tx < Rx 7100 8500
Rx < Tx 7100 8500
311,32 Tx < Rx 7100 8500
Rx < Tx 7100 8500
Tx / Rx
Order


APPLICABLE


135/ 139

A.3 ODU UX 13 GHz 4QAM with RTPC
Remote Inventory: 3CC11737xxxx
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Yes 4QAM Optional 5 25 266 Tx < Rx 12751.75 12978.25
Rx < Tx 13017.75 13244.25
A.4 ODU UX 13 GHz 4QAM without RTPC
Remote Inventory: 3CC08879AAxx
Settable Power
Level
Modulation
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
No 4QAM Optional 25 25 266 Tx < Rx 12751.75 12978.25
Rx < Tx 13017.75 13244.25
RF Loopback
Pmin
(dBm)
A.5 ODU UX 13 GHz 16QAM
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Yes 16QAM Optional 1 21 12751.75 266 Tx < Rx 12978.25
Rx < Tx 13017.75 13244.25
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
A.6 ODU UX 15 GHz standard power
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 14950.75 15213.25
420 Tx < Rx 14502.75 14940.25
Rx < Tx 14922.75 15360.25
490 Tx < Rx 14404.75 14856.25
Rx < Tx 14894.75 15346.25
728 Tx < Rx 14502.75 14618.25
Rx < Tx 15230.75 15346.25
A.7 ODU UX 15 GHz high power
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 14950.75 15213.25
420 Tx < Rx 14502.75 14940.25
Rx < Tx 14922.75 15360.25
490 Tx < Rx 14404.75 14856.25
Rx < Tx 14894.75 15346.25
728 Tx < Rx 14502.75 14618.25
Rx < Tx 15230.75 15346.25


APPLICABLE


136/ 139

A.8 ODU UX 15 GHz 4QAM with RTPC
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Yes 4QAM Optional -6 24 315 Tx < Rx 14635.75 14898.25
Rx < Tx 14950.75 15213.25
420 Tx < Rx 14502.75 14940.25
Rx < Tx 14922.75 15360.25
490 Tx < Rx 14404.75 14856.25
Rx < Tx 14894.75 15346.25
728 Tx < Rx 14502.75 14618.25
Rx < Tx 15230.75 15346.25
Settable Power
Level
A.9 ODU UX 18 GHz standard power
Settable Power
Level
Modulation
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 18921.75 19158.25
1008 Tx < Rx 17703.75 18678.25
Rx < Tx 18711.75 19686.25
1010 Tx < Rx 17701.75 18678.25
Rx < Tx 18711.75 19698.25
1092,5 Tx < Rx 17727.50 18580.00
Rx < Tx 18820.00 19672.50
1560 Tx < Rx 17701.75 18138.25
Rx < Tx 19261.75 19698.25
RF Loopback
A.10 ODU UX 18 GHz high power
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 18921.75 19158.25
1008 Tx < Rx 17703.75 18678.25
Rx < Tx 18711.75 19686.25
1010 Tx < Rx 17701.75 18678.25
Rx < Tx 18711.75 19698.25
1560 Tx < Rx 17701.75 18138.25
Rx < Tx 19261.75 19698.25


APPLICABLE


137/ 139

Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Rx < Tx 23009.75 23598.25
1197 Tx < Rx 21204.75 22398.25
Rx < Tx 22401.75 23595.25
1200 Tx < Rx 21201.75 22398.25
Rx < Tx 22401.75 23598.25
1232 Tx < Rx 21201.75 22366.25
Rx < Tx 22433.75 23598.25
Tx Fmax
(MHz)

Remote Inventory: 3CC12755xxxx or 3CC12756xxxx
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 23009.75 23598.25
1197 Tx < Rx 21204.75 22398.25
Rx < Tx 22401.75 23595.25
1200 Tx < Rx 21201.75 22398.25
Rx < Tx 22401.75 23598.25
1232 Tx < Rx 21201.75 22366.25
Rx < Tx 22433.75 23598.25
Shifter
(MHz)

Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 25557.75 26452.25
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Rx < Tx 25557.75 26452.25
Tx Fmax
(MHz)


APPLICABLE


138/ 139


APPLICABLE


139/ 139

Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Yes 4QAM Optional -14 16 1260 Tx < Rx 37060 38176
Rx < Tx 38320 39436
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Rx < Tx 38319.75 39436.25
A.17 ODU UX-Flat 11, 13, 15, 18, 23, 25, 38 GHz
Remote Inventory: xxx
Settable Power
Level
Pmin
(dBm)
Pmax
(dBm)
Shifter
(MHz)
Tx / Rx
Order
Tx Fmin
(MHz)
Tx Fmax
(MHz)
Yes
4QAM &
16QAM
Yes
Provided
by Remote
Inventory
Provided
by Remote
Inventory
Provided by
Remote
Inventory
Provided by
Remote
Inventory
Provided by
Remote
Inventory
Provided by
Remote
Inventory

3CC14055AAAADTBJA-Ed03 00

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3CC14055AAAADTBJA-Ed03 00

Uploaded by

Copyright:

Available Formats

Site

You might also like