ulsSysSpecRel2 1 2Ed01It01

All rights reserved.
Passing on and copying of this

document, use and communication of its contents, not
permitted without written authorization from Alcatel
ALCATEL-LUCENT
WIRELESS TRANSMISSION DIVISION
01 07-10-09
ED
DATE
CHANGE NOTE
G.Boiocchi
C.Pasqualini
APPRAISAL AUTHORITY
ORIGINATOR
ULS 2.1 (v.2.1.2)

System Specification
SNMP Management Interface
ED
WTD
01 It.01
COMPANY CONFIDENTIAL
3DB161760000DSZZA
1/207
INDEX...................................................................................................................................................................................2
PREFACE.............................................................................................................................................................................6
1
INTRODUCTION .......................................................................................................................................................7
1.1
1.2
1.3
OVERVIEW ................................................................................................................................................................9
2.1
2.2
ABBREVIATIONS ....................................................................................................................................................7
GLOSSARY .............................................................................................................................................................8
SCOPE ....................................................................................................................................................................8
FUNCTIONAL DESCRIPTION ...................................................................................................................................9

CONFIGURATIONS ..................................................................................................................................................9
EQUIPMENT DOMAIN ..........................................................................................................................................10

3.1
OVERVIEW ...........................................................................................................................................................10
3.2
ALLOWED EQUIPMENT TYPES .............................................................................................................................11
3.2.1 Shelves Equipment Types................................................................................................................................11
3.2.2 Slots and Sub-slots Equipment Types .............................................................................................................13
3.3
REMOTE INVENTORY MANAGEMENT ...................................................................................................................14
3.4
EQUIPMENT PROTECTION SWITCHING MANAGEMENT .........................................................................................14
3.5
EXTERNAL POINTS MANAGEMENT ......................................................................................................................15
3.6
MANAGEMENT FUNCTIONS..................................................................................................................................16
3.6.1 Functional Objects Creation ..........................................................................................................................31
3.7
SUPPORTED OBJECTS AND NAMING RULES .........................................................................................................32
All rights reserved. Passing on and copying of this

INDEX
TRANSMISSION INTERFACES (IFTABLE).......................................................................................................35

4.1
4.2
SNMP TABLES ....................................................................................................................................................36
4.2.1 Supported objects ...........................................................................................................................................36
4.3
NAMING RULES ...................................................................................................................................................36
SDH/PDH TRANSMISSION DOMAIN..................................................................................................................38

5.1
5.2
5.3
FUNCTIONAL DESCRIPTION .................................................................................................................................38

ETHERNET TRANSMISSION DOMAIN .............................................................................................................60

6.1
6.2
6.2.1 Ethernet Physical Interface Management.......................................................................................................65
6.2.2 Ethernet Port Management ............................................................................................................................75
6.2.3 Ethernet Transport Service Management.......................................................................................................79
6.3
RADIO DOMAIN......................................................................................................................................................83
7.1
7.2
7.3

SUPPORTED OBJECTS AND NAMING RULES .......................................................................................................114
SUPPORT DOMAIN ..............................................................................................................................................117

8.1
8.2
8.3
ED
WTD
FUNCTIONAL DESCRIPTION ...............................................................................................................................117

MANAGEMENT FUNCTIONS................................................................................................................................124
01
It.01
3DB161760000DSZZA
2/202
1AA 00014 0004 (9711) A4

COMMUNICATION AND ROUTING DOMAIN...............................................................................................147

9.1
9.2
9.3
10
FUNCTIONAL DESCRIPTION................................................................................................................................147
MANAGEMENT FUNCTIONS ................................................................................................................................149
OVERHEAD DOMAIN......................................................................................................................................158
10.1
10.2
10.3
11
TEST DOMAIN...................................................................................................................................................162
11.1
11.2
11.3
12
SDH/PDH PERFORMANCE MONITORING DOMAIN ..............................................................................167
12.1
12.2
12.3
13
ETHERNET PERFORMANCE MONITORING DOMAIN ..........................................................................178
13.1
13.2
13.3
14
SECURITY DOMAIN ........................................................................................................................................182
14.1
14.2
14.3
15
FUNCTIONAL DESCRIPTION (SNMP INTERFACE)...............................................................................................182

ALARMS .............................................................................................................................................................189
1AA 00014 0004 (9711) A4
15.1
ALARMS PROVIDED BY ITEM HW......................................................................................................................189
15.2
ALARMS REPORTED ...........................................................................................................................................194
15.2.1
Equipment Alarms....................................................................................................................................194
15.2.2
Communication Alarms............................................................................................................................196
15.3
PREDEFINED ASAPS SEVERITY .........................................................................................................................198
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
3/202
Date
Edition
071009 Ed. 01 It. 1

HISTORY
Comments
Creation.
The main features of this version (2.1.2) are the following:
ODU v1/v2 full compatibility (AWY 2.0.6 like);
NAT static (AWY 2.0.6 like);
1+1 option MUX EPS protection (RPS only);
Automatic Link Shutdown on Ethernet ports;
Time Slot management in E1#1 tributary frame.
The SNMP Optics-IM reference version for this release is the
v4.04.
The features implemented in this document release are referred to [5].
REFERENCED DOCUMENTS
[1] RFC 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types
[2] HW & SW Specification 9400 AWY New Generation PDH Radio Family
HSS/S056 8BW 03219 0000 DSCWA Ed.02, 2003.07.28
[3] HW & SW Specification 9400AWY Restyling New Generation PDH Radio Family (IDU, ODU
7&8GHz)
HSS/S056 8BW 03538 0000 DSZZA Ed.01 2004.06.15 Released
[4] HW & SW Specification 9400AWY Rel.2.1
HSS 3DB 16001 AAAA DSZZA Ed.01, 2005.06.15
[5] PDH Microwaves family 9400AWY R2.1 Network Element Road Map
3DB xxxxx AAAA FLZZA Ed.08, 2007.08.03
[6] 9400 AWY 2.1 (v.2.1.2) System Requirements Specification
3DB 16172 AAAA DSZZA Ed.01 It.01, 2007.10.05
RELATED DOCUMENTS
[7] Optics-IM: Communication and Routing Domain (SNMP)
3AL 38806 0000 DSZZA
[8] Optics-IM: Support Domain (SNMP)
3AL 38806 0005 DSZZA
[10] Optics-IM: SDH/PDH Transmission Domain (SNMP)

3AL 38806 0014 DSZZA
ED
WTD
01
It.01
3DB161760000DSZZA
4/202
1AA 00014 0004 (9711) A4
[9] Optics-IM: Equipment Domain (SNMP)

3AL 38806 0013 DSZZA

[11] Optics-IM: SDH/PDH Performance Monitoring Domain (SNMP)

3AL 38806 0012 DSZZA
[12] Optics-IM: Radio Domain (SNMP)
3AL 38806 0015 DSZZA
[13] Optics-IM: Test Domain (SNMP)
3AL 38806 0017 DSZZA
[14] Optics-IM: Overhead Domain (SNMP)
3AL 38806 0018 DSZZA
[15] Optics-IM: Security Domain (SNMP)
3AL 38806 0004 DSZZA
[16] Optics-IM: List of SNMP Events

3AL 38897 0001 DSZZA
[17] Optics-IM: Operator Labels and Naming Rules (SNMP)

3AL 38806 0006 DSZZA
[18] Ethernet Physical Interface Management

3AL 81428 0012 DSZZA
[19] SNMP Management Functions

Annex to Ethernet Physical Interface Management
3AL 81428 0012 DSZZA
[20] Ethernet Port Management

3AL 81428 0016 DSZZA

Annex to Ethernet Port Management Functional Specification
3AL 81428 0016 DSZZA
[22] Ethernet Performance Monitoring

3AL 81428 0014 DSZZA

Annex to Ethernet Performance Monitoring Functional Specification
1AA 00014 0004 (9711) A4
3AL 81428 0014 DSZZA
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
5/202
ED
WTD
01
It.01
3DB161760000DSZZA
6/202
1AA 00014 0004 (9711) A4
This document provides the functional description of SNMP management interface of ULS 2.1 (Urban
Link Split mount) Radio NE in the scope of Release 2.1.2.

PREFACE
1AA 00014 0004 (9711) A4

INTRODUCTION
1.1 Abbreviations
AIS
ANSI
APT
ASAP
ATPC
AVC
BER
BBE
CD
CLA
EC
EFC
EFD
EOW
EPS
ES
ETH
ETSI
EW
FCS
FD
FE
GFP
HBER
HD
HET
HS
HSB
IDU
IM
IP
LAN
LAPD
LBER
LOF
LOS
MAC
MAU
MIB
MTU
NE
NMS
NSA
NTP
OC
ODU
OFS
ED
NTIAL
WTD
Alarm Indication Signal

American National Standards Institute
Active Problem Table
Alarm Severity Assignment Profile
Automatic Transmit Power Control
Attribute Value Change
Bit Error Ratio
Background Block Error
Current Data
Common Loss Alarm
Equipment Controller
Ethernet Flow Control
Event Forwarding Discriminator
Engineering Order Wire
Equipment Protection Switching
Errored Second
ETHernet
European Telecommunications Standards Institute
Early Warning
Frame Check Sequence
Frequency Diversity
Fast Ethernet
Generic Frame Protocol
High Bit Error Ratio
History Data
Hetero frequency
Hitless Switch
Hot Stand-by
InDoor Unit
Information Model
Internet Protocol
Local Area Network
Link Access Procedure on D-channel
Low Bit Error Ratio
Loss Of Frame
Loss Of Signal
Medium Access Control
Medium Attachment Unit
Management Information Base
Maximum Transfer Unit
Network Element
Network Management system
Not Service Affecting
Network Time Protocol
ODU Controller
OutDoor Unit
Out of Frame Second
01
It.01
3DB161760000DSZZA
7/202
OH
OS
PDH
PM
PPI
PSU
QoS
RACS
RAI
RDI
RI
RPS
RPPI
SA
SD
SDH
SES
TCA
TD
TDF
TPS
TRCF
TRCO
TRSEF
TS
TTF
TTO
TTP
UAS
UAT
ULS
URU
OverHead
Operation System
Plesyochronous Digital Hierarchy
Performance Monitoring
Plesyochronous Physical Interface
Power Supply Unit
Quality of Service
Received Automatic Control Status
Remote Alarm Indication
Remote Defect Indication
Remote Inventory
Radio Protection Switching
Radio Plesyochronous Physical Interface
Service Affecting
Space Diversity
Synchronous Digital Hierarchy
Severely Errored Second
Threshold Crossing Alarm
Threshold Data
Total Discarded Frames
Tx Protection Switching
Total Received Correct Frames
Total Received Correct Octets
Total Received Service Errored Frames
Time Slot
Total Transmitted Frames
Total Transmitted Octets
Trail Termination Point
UnAvailable Second
UnAvailable Time
Urban Low capacity Split
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
ED
WTD
01
It.01
3DB161760000DSZZA
8/202
1AA 00014 0004 (9711) A4
The management functionalities described in this document cover the functionalities of ULS NE
supported at SNMP interface in the scope of Rel. 2.1.2.
The SNMP Optics-IM reference version for release 2.1.2 is the v4.04.
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 ULS
NE.

OVERVIEW
ULS NE has the aim to multiplexer/demultiplexer the main tributaries (up to 32 E1/DS1 (DS1 tributary
is not supported) or 1 E3/DS3 (not supported)) with different modulation formats.
The following table resumes the relation between tributaries and modulations.
Allowed
Equipment
Type
Market
Tributary
ODU v1
4/16
QAM
32 Mb
ETSI
ODU-E
2xE1
4xE1
8xE1
16xE1
32xE1
4 QAM
4 QAM
4 QAM
4 QAM
-
64 Mb
16 QAM
16 QAM
16 QAM
16 QAM
ODU v2
4 QAM
ODU v2
4/16
QAM
32 Mb
64 Mb
4 QAM
4 QAM
4 QAM
4 QAM
-
4 QAM
4 QAM
4/16 QAM
4/16 QAM
16 QAM
Table: Tributaries and modulations forecasted.
2.1 Functional Description

The main functions performed by IDU and ODU of ULS 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 Physical Interface (AWY)

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
ULS NE can be composed by:
1AA 00014 0004 (9711) A4
one radio channel (1+0 configurations);

two radio channels (1+1 configurations).
The 2+0 and N+1 configurations are not supported.

The complete list of the configurations supported in this release is provided in the Support domain.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
9/202
EQUIPMENT DOMAIN
The NE configuration is described in the Support Domain section.
3.1 Overview
The ULS NE is composed by two different parts: the indoor and the outdoor part. In the following they
are described from physical and management point of view.
Indooor Part (IDU)
The indoor part is composed by two units/shelves (see Figure 1 and 2): Main and Extension units.
Main Unit Ch#1

Figure 1. Main IDU unit
Extension Unit Ch#0
Figure 2. Extension IDU unit

The Main IDU Unit provides the external interfaces for the E1/E3/DS1/DS3 tributaries (E3/DS1/DS3
tributaries are not allowed in this release), user service channel, housekeeping and summarizing
alarms, audio channels, NMS V11 and G703 interfaces and a telephone jack. It contains the JBIDUM
and the Power Supply units. The JBIDUM unit manages 16E1/DS1 tributaries, the Mux/Demux, the
EPS protection (with the possibility to lock out this protection), the EC/RC interface, the IDU-ODU cable
interface functions and the NMS-V11 + NMS-G703. With the additional plug-in, up to 32E1/DS1
tributaries can be managed. Optional 16xE1/DS1 or E3/DS3 (not allowed in this release) or Data unit
implementing Ethernet interfaces (alternative between them) and one audio channels (+ Service
Channel) can be plugged onto this Main unit.
Outdoor Part (ODU)

According to the configuration type, one or two electrical ODU are managed in the Outdoor part.
Each ODU contains a PQECRC unit. It implements the ODU controller functions.
ED
WTD
01
It.01
3DB161760000DSZZA
10/202
1AA 00014 0004 (9711) A4
The Main IDU unit is used both in 1+0 and 1+1 configurations.
The Extension IDU Unit contains the JBIDUE (it contains Mux/Demux, the EPS and RPS protections
(with Hitless Switch) and IDU-ODU cable interface functions) and the Power Supply. Optional
16xE1/DS1 or E3/DS3 unit (alternative between them, but in this release, E3/DS3 is not supported)
can be plugged onto this Extension IDU unit.
The Extension IDU unit is used only in 1+1 configurations.

3.2 Allowed Equipment Types

This section provides information on the allowed equipment types for all the configurations supported
by ULS NE.
As effect of the definition of the NE configuration, the agent has to create not only all the structured
equipment describing the related physical layout, but also all the contained equipment (slot and subslots) with the related equipmentExpected value, providing in this way the whole physical description of
the NE configuration defined.
As consequence, the value of the equipmentExpected object is never settable by the managers.
In the following tables, the list of allowed equipment types for each physical position, includes the
whole set of possible types, but, according to the NE configuration defined by the managers, only one
value will be present in opticsIMAllowedEquipmentTypesTable for each physical position.
N.B. Both IDU and ODU shelves are numbered inside a virtual rack (equipmentPosition = 1). All the
IDUs, ODUs and contained positions will be numbered accordingly.
3.2.1 Shelves Equipment Types
The following table provides the shelves equipment types allowed for each supported NE configuration
(see support domain section for the list of supported configurations).
The shelves are numbered according to the following sequence rule:
IDU
Ch#1
ODU Ch#1
IDU
Ch#0
ODU Ch#0
NE
Configurati
on
Positio
n
1.1.0.0
1+0
1+0 ETH
(note 1)
1.2.0.0
1.1.0.0
1.2.0.0
1+1
(note 2)
1.3.0.0
1AA 00014 0004 (9711) A4
1.4.0.0
ED
NTIAL
WTD
01
It.01
Allowed
Allowed Equipment Type
Equipment
Description
Type
IDU Main Shelf
IDU32-M
ODU v1 1+0 4/16 QAM
32Mb
ODU v1 1+0 4/16 QAM
ODU-E
64Mb
(note 3)
ODU v2 1+0 4 QAM
ODU v2 1+0 4/16 QAM
IDU Main Shelf
IDU32-M
ODU v1 1+0 4/16 QAM
32Mb
ODU v1 1+0 4/16 QAM
ODU-E
64Mb
(note 3)
ODU v2 1+0 4 QAM
ODU v2 1+0 4/16 QAM
IDU Extension Shelf
IDU32-E
ODU v1 1+0 4/16 QAM
32Mb
ODU v1 1+0 4/16 QAM
ODU-E
64Mb
(note 3)
ODU v2 1+0 4 QAM
ODU v2 1+0 4/16 QAM
Equipmen
t
Label
IDU Ch#1
ODU
Ch#1
IDU Ch#1
ODU
Ch#1
IDU Ch#0
ODU
Ch#0
3DB161760000DSZZA
11/202
(note 2)
All the 1+1 configurations.
(note 3)
The Equipment Type ODU-E is compliant for ODU v1 32Mb (mnemonic ODU-E of
Remote Inventory), for ODU v1 64Mb (mnemonic ODU32-E of Remote Inventory), for ODU v2
4QAM (mnemonic ODU2-E of Remote Inventory) and for ODU v2 4/16QAM (mnemonic ODU232E of Remote Inventory) provided.
No equipment mismatch alarm is raised when the equipmentExpected is set to ODU-E and the
equipmemt type read from Remote Inventory is one of the following: ODU-E, ODU32-E, ODU2-E,
ODU2-32E.
ED
WTD
01
It.01
3DB161760000DSZZA
12/202

All the 1+0 configurations.
1AA 00014 0004 (9711) A4
(note 1)

3.2.2 Slots and Sub-slots Equipment Types

The following tables indicate the allowed equipment types for each slot inside each shelf type.
IDU
IDU32-M
Position

Description
Allowed
Equipment
Type
Equipment Label
1.1.1.0
Main Unit 48/60 V Range Supply
M4860-32
IDU/MAIN Ch#1
Main Unit 24/60 V Range Supply
M2460-32
16xE1/DS1 plug-in unit
P16E1DS1
4xGigabit Ethernet plug-in unit
P4DATASW
Audio channels+ Service Channel

(64Kb/s) plug-in unit
P-AC-SC
1.1.1.1
1.1.1.2
IDU/MAIN/<note 1>
Ch#1
IDU/MAIN/<note 2>
Ch#1
Table: Allowed board/plug-in types in IDU Main shelf

(note 1)
(note 2)
The label is one of the following:

E1, when the 16xE1/DS1 plug-in is provisioned and it configured to work in E1 mode
DATA, when the 4xDATA plug-ins are provisioned.
The label is the following:

AC-SC, when the audio channels+Service Channel plug-in is provisioned.
IDU32-E
Positio
n

Description
Allowed
Equipmen
t Type
Equipment Label
1.3.1.0
Extension Unit 48/60 V Range Supply
E4860-32
IDU/EXT Ch#0
Extension Unit 24/60 V Range Supply
E2460-32
16xE1/DS1 plug-in unit (note 1)
P16E1DS1
1AA 00014 0004 (9711) A4
1.3.1.1
IDU/EXT/<note 2>
Ch#0
Table: Allowed board/plug-in types in IDU Extension shelf

(note 1)
This plug-in is present in all 1+1 configurations, except in whithout EPS MUX
protection configurations.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
13/202
The label is the following:

ODU
No slot can be defined inside the Electrical ODU.
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 will be provided by the following
equipment types:
Main Unit
(M4860-32, M2460-32)
Extension Unit
(E4860-32, E2460-32)
Gigabit Ethernet plug-in
(P4DATASW)
PDH Tributary optional plugs-in
(P16E1DS1)
Audio channels, Service Channel plug-in
(P-AC-SC)
ODU unit
(ODU-E, ODU32-E, ODU2-E, ODU2-32E)

(note 2)
For all the other equipment types the remoteInventoryStatus columnar object assumes the value
unavailable.
The RI data of each sub-components unit (i.e., JBIDUM in the IDU, MILOU in the ODU) wont be seen
at SNMP management interface but only by means of factory tools.
Also the information about the equipment type can be read from the remote inventory data (Unit
mnemonic field). All the units must be provided in its own remote inventory data this type of
information. It is used to identify the actual equipment type and then, eventually, to provide an
equipment mismatch alarm, if the equipment type read from remote inventory data is different from
the equipment expected provided by the managers.
If it isnt possible to read the Remote Inventory information, a Card Fail alarm is declared.
3.4 Equipment Protection Switching Management

Just one EPS protection scheme is supported. It provides protection both of the PDH multiplexer and of
the demultiplexer functional blocks.
The following table defines the characteristics of this protection scheme.
ED
WTD
01
It.01
Value
1+1
Single ended
Revertive/Non Revertive
3DB161760000DSZZA
14/202
1AA 00014 0004 (9711) A4
Parameter Type
Protection group type

Switching type
Restoration criteria

Switching condition
Operator commands
Equipment failures
Lockout spare (note 1)
Forced switch from main to spare
Manual switch from main to spare and vice-versa
The configuration of this protection scheme is performed by the NE in conjunction with the equipment
provisioning process (declaration of boards).
(note 1) The Lockout spare command disables all RPS protection scheme functionality. In this case the
opticsIMRadioProtectionGroupOperationalState object of opticsIMRadioProtectionGroupEntry has to
be set to disabled value. The Ch#1 will be the channel active both for EPS and RPS protection
schemes.
3.5 External Points Management

ULS NE has the capability to monitor 6 input contacts (housekeeping alarms) and 4 output contacts
(housekeeping controls).
The polarity of each external point can be configured through the SNMP management interface.
External output points can be automatically controlled by the agent or manually used by the operator.
In the first case the event that controls the output state is assigned by the operator. The allowed events
are defined in the following table (outputPointAllowedEventId and outputPointAllowedEvent columnar
objects):
Allow
ed
EventI
d
1
2
3
Major Alarm
Minor Alarm
Service Affecting Alarm
Line side LOS Alarm
5
6
7
Cable Loss IDU Alarm

Radio Signal Fail Alarm
Local Defect Indication
Remote NE Failure
Indication
Allowed
Event
Allowed Event
description
OR of critical and mayor alarms
OR of minor and warning alarms
OR of service affecting alarms
OR of PDH tributaries and Ethernet interfaces LOS
alarms
OR of cable loss IDU alarms
OR of radio signal fail and HBER alarms
see [3] for the primitives
see [3] for the primitives
Also
the
summarizing
alarms
are
managed
via
SNMP
interface
using
the
opticsIMOutputExternalPointTable. They are managed according to the rules described in the
following table:
Inde
x
Valu
e
Configura
tion
UserLabel
1AA 00014 0004 (9711) A4
Read-only
5
All the 1+0

All the 1+1
6
ED
NTIAL
WTD
01
It.01
External
State
Readonly
on/
off
Polarity
Read-write
activeLow/
activeHigh
Criteria
Readonly
automati
c
Automatic
Event
Automatic
EventId
Read-only
Read-only
Fail IDU
Fail ODU
Ch#1
-1
3DB161760000DSZZA
15/202
Fail ODU
Ch#0
3.6 Management Functions

The following table lists the Equipment management functions supported in this release (see [9]).
Equipment
Function
Equipment SN Function Description
Configuration
M
P
If
F-2.1 Request Allowed
Y This management function allows a managing system to
Equipment Types
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
N This management function allows a managing system to
Equipment Expected
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
request the equipment type expected for an equipment
position. This information is provided by means of equipment
type identifier and associated string.
Scope
ED
WTD
01
It.01
3DB161760000DSZZA
16/202

All the 1+1
1AA 00014 0004 (9711) A4
1AA 00014 0004 (9711) A4

Service Used
SNMP-GET on:
equipmentExpectedTypeId
equipmentExpected
F-2.4 Request
request the equipment type of the equipment physically
Equipment Actual
present.
Scope
Service Used
SNMP-GET on equipmentActual
F-2.5 Condition
Administrative State
suspend/resume the use of an equipment. It applies to
equipment objects representing slots/boards and subslots/daughter boards.
Putting an equipment in the outOfService state has the effect
that the functional objects supported by the board are
released from any 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
request whether the equipment is in or out of service.
Administrative State
Scope
Service Used
SNMP-GET on equipmentAdministrativeState
Note F-2.6: Default value: inService.
F-2.7 Condition ASAP
Pointer
configure the ASAP Pointer associated to an equipment
position.
Scope
Service Used
SNMP-SET on equipmentAsapIndex
F-2.8 Request ASAP
request the ASAP Pointer associated to an equipment position.
Pointer
Scope
Service Used
SNMP-GET on equipmentAsapIndex
F-2.9 Request
Equipment Label
request the label associated to an equipment position.
Scope
Service Used
SNMP-GET on equipmentLabel
F-2.10 Request Affected
Objects List
request the functional objects which are in operational
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
17/202
Equipment SN
M
PIf
F-2.11 Request
Y
Equipment Operational
State
Function Description
This management function allows the managing system to
request the operational state of an equipment.
Scope
Service Used
SNMP-GET on equipmentOperationalState
Function
Notifications
Equipment SN Function Description

MP
If
F-2.12 Report
Y This management function allows a managed system to report
Equipment Alarm
equipment alarms.
Scope
Service Used
SNMP-TRAP on:
opticsIMAlarmReplaceableUnitProblemRaise
opticsIMAlarmReplaceableUnitProblemClear
opticsIMAlarmReplaceableUnitMissingRaise
opticsIMAlarmReplaceableUnitMissingClear
opticsIMAlarmReplaceableUnitTypeMismatchRaise
opticsIMAlarmReplaceableUnitTypeMismatchClear
opticsIMAlarmUnconfiguredEquipmentPresentRaise
opticsIMAlarmUnconfiguredEquipmentPresentClear
opticsIMAlarmFirmwareDownloadOnGoingRaise
opticsIMAlarmFirmwareDownloadOnGoingClear
opticsIMAlarmVersionMismatchRaise
opticsIMAlarmVersionMismatchClear
opticsIMAlarmInternalCommunicationProblemRaise
opticsIMAlarmInternalCommunicationProblemClear
opticsIMAlarmLanFailureRaise
opticsIMAlarmLanFailureClear
opticsIMAlarmBatteryFailRaise
opticsIMAlarmBatteryFailClear
opticsIMAlarmAndBatteryFailureRaise
opticsIMAlarmAndBatteryFailureClear
opticsIMAlarmBackplaneFailureRaise
opticsIMAlarmBackplaneFailureClear
opticsIMAlarmReceiverFailureRaise
opticsIMAlarmReceiverFailureClear
ED
WTD
01
It.01
3DB161760000DSZZA
18/202

Function
Status
1AA 00014 0004 (9711) A4
dependency with an equipment.

Scope
OPTICSIM-EQPT-MIB: opticsIMAffectedObjectListTable
Service Used
SNMP-GET on affectedObjectInstanceId

Function
Inventory
Remote SN Function Description

MP
If
F-2.13 Request Remote
Inventory Data
request the 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
Function Tributary Ports SN
Impedance
MP
If
F-2.14 Condition E1
Y
Tributary Ports
Impedance
F-2.15 Request E1
Tributary Ports
Impedance
1AA 00014 0004 (9711) A4
opticsIMAlarmLowPowerRaise
opticsIMAlarmLowPowerClear
opticsIMAlarmStandByVersionMismatchRaise
opticsIMAlarmStandByVersionMismatchClear
opticsIMAlarmRemoteInventoryFailureRaise
opticsIMAlarmRemoteInventoryFailureClear
opticsIMAlarmRepeaterCableProblemRaise
opticsIMAlarmRepeaterCableProblemClear
opticsIMAlarmProvisioningMismatchRaise
opticsIMAlarmProvisioningMismatchClear
ED
NTIAL
WTD
01
It.01
This management function allows a managing system to
configure the impedance used by E1 tributary ports (balanced
120 Ohm or unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-SET on opticsIMTribPortsImpedance
request the impedance used by E1 tributary ports (balanced
120 Ohm or unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-GET on opticsIMTribPortsImpedance
3DB161760000DSZZA
19/202
F-3.1 Create Equipment

Protection Group
F-3.2 Delete Equipment

Protection Group
Function Configuration
F-3.3 Request
Equipment Protection
Group Type
F-3.4 Condition
Equipment Automatic
Restoration Criteria
ED
WTD
01
It.01
SN Function Description
MP
If
allocate an equipment protection group entry. The managing
system has to indicate in the creation request:
the protection type (1+1 or 1:N)
the mode of operation (revertive/non revertive)
The protection units to be created and their role are
established by the NE and cannot be assigned by the
managing system.
Scope
OPTICSIM-EQPT-MIB:
opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRowStatus
object to createAndGo value
delete an equipment protection group entry and related
protection units.
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRowStatus
object to destroy value
MP
If
request the type of protection (1+1 or 1:N).
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on opticsIMEquipmentProtectionGroupType
Y 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
OPTICSIM-EQPT-MIB:
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRevertive
3DB161760000DSZZA
20/202

Function
Creation/Deletion
1AA 00014 0004 (9711) A4

F-3.5 Request
Equipment Automatic
F-3.6 Request
Unit Type
F-3.7 Request Radio

Channel Number
Function
Commands
Operator SN
MP
If
F-3.9 Allow/Inhibit
N
Switch of a Working
Equipment
1AA 00014 0004 (9711) A4
F-3.10 Allow/Inhibit
Switch of Protection
Equipment
ED
NTIAL
WTD
01
It.01

request the current automatic restoration criteria: restoration
allowed (revertive mode) or inhibited (non-revertive mode).
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on opticsIMEquipmentProtectionGroupRevertive
request the type of an equipment protection unit: main
(protected) or spare (protecting).
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
Service Used
SNMP-GET on opticsIMEquipmentProtectionUnitType
request the radio channel number (if any) associated to an
equipment protection unit.
Scope
Service Used
SNMP-GET
on
opticsIMEquipmentProtectionUnitChannelNumber
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 switch, both addressed to a main (working) protection
unit.
Scope
(on main protection unit)
Service Used
SNMP-SET
on
opticsIMEquipmentProtectionUnitSwitchCommand (lockout or
noRequest)
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.
the noRequest syntax to remove the lockout and allow the
switch, both addressed to the spare protection unit.
3DB161760000DSZZA
21/202
F-3.12
Initiate/Terminate
Manual Switch to a
Working Equipment
F-3.13
Initiate/Terminate
Forced Switch to
Protection Equipment
ED
WTD
01
It.01
3DB161760000DSZZA
22/202

1AA 00014 0004 (9711) A4
F-3.11
Initiate/Terminate
Manual Switch to
Protection Equipment
Scope
(on spare protection unit)
Service Used
SNMP-SET
on
opticsIMEquipmentProtectionUnitSwitchCommand (lockout or
noRequest)
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
SNMP-SET
on
opticsIMEquipmentProtectionUnitSwitchCommand
(manualSwitch or noRequest)
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.
both addressed to the spare protection unit.
Scope
Service Used
SNMP-SET
on
(manualSwitch or noRequest)
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 switched.
According to the NE type, this function will fail if the protection

F-3.14
Initiate/Terminate
Forced Switch to a
Working Equipment
Protection SN
MP
If
F-3.15 Request
Y
Scheme Operational
State
1AA 00014 0004 (9711) A4
Function
Status
F-3.16 Request
Status
F-3.17 Request
Switching Source
ED
NTIAL
WTD
01
It.01
equipment has a failure condition.

This function involves the forcedSwitch syntax to initiate the
switch, the noRequest syntax to terminate the switch, both
addressed to a main protection unit.
Scope
Service Used
SNMP-SET
on
(forcedSwitch or noRequest)
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.
addressed to the spare protection unit.
Scope
Service Used
SNMP-SET
on
(forcedSwitch or noRequest)
request the operational state of an equipment protection
scheme.
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET
on:
opticsIMEquipmentProtectionGroupOperationalState
request the current state of an equipment protection unit.
Scope
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionUnitSwitchCriteria
opticsIMEquipmentProtectionUnitSwitchStatus
request the source of the equipment switching request. This
management function is applicable only in case of dual ended
3DB161760000DSZZA
23/202

F-3.18 Report
Switch Event
switching.
Scope
Service Used
SNMP-GET
on:
opticsIMEquipmentProtectionUnitSwitchRequestSource
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.
Scope
Service Used
SNMP-TRAP opticsIMProtectionSwitchReporting on:
opticsIMEquipmentProtectionUnitSwitchCriteria
opticsIMEquipmentProtectionUnitSwitchStatus
External Points
Point SN Function Description
MP
If
F-4.1 Condition External Y This management function allows a managing system to
Input Point User Label
configure 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
request the user label associated to an external input point.
Scope
Service Used
SNMP-GET on inputPointUserLabel
Input Point External
request the state of an external input point (on when the
State
alarm is raised, off otherwise).
Scope
Service Used
SNMP-GET on inputPointExternalState
F-4.4 Condition External Y This management function allows a managing system to
Input Point ASAP Pointer
configure the ASAP Pointer associated to an external input
point.
ED
WTD
01
It.01
3DB161760000DSZZA
24/202
1AA 00014 0004 (9711) A4
Function
Input
Configuration


Input Point ASAP Pointer
F-4.6 Condition External

Input Point Polarity

Input Point Polarity
Function
Status
Scope
Service Used
SNMP-SET on inputPointAsapIndex
request the ASAP Pointer associated to an external input point.
Scope
Service Used
SNMP-GET on inputPointAsapIndex
configure the polarity of an external input point.
Scope
Service Used
SNMP-SET on inputPointPolarity
request the polarity of an external input point.
Scope
Service Used
SNMP-GET on inputPointPolarity
Input

MP
If
Y This management function allows the managing system to
Input Point Operational
request the operational state of an external input point.
State
Scope
Service Used
SNMP-GET on inputPointOperationalState

MP
If
F-4.9 Report
an alarm for a defect detected by an house-keeping interface.
Housekeeping Alarm
The housekeepingAlarm is the probable cause used.
Scope
Service Used
SNMP-TRAP:
opticsIMHousekeepingAlarmRaise
opticsIMHousekeepingAlarmClear
1AA 00014 0004 (9711) A4
Function
Input
Notifications
Function Output
Configuration
ED
NTIAL
WTD
01
It.01

MP
3DB161760000DSZZA
25/202

configure the user label associated to an external output
point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointUserLabel
request the user label associated to an external output point.
Output Point User Label
Scope
Service Used
SNMP-GET on outputPointUserLabel
F-4.12 Condition
configure the external state in order to command a remote
External Output Point
External State
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
request the external state (on or off).
Output Point External
State
Scope
Service Used
SNMP-GET on outputPointExternalState
F-4.18 Condition
P This management function allows a managing system to
condition
Criteria
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.
Scope
Service Used
SNMP-SET on outputPointCriteria
Note F-4.18: remoteInputPoint criteria is not supported.
Output Point Criteria
request the 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
ED
WTD
01
It.01
3DB161760000DSZZA
26/202

If
Y
1AA 00014 0004 (9711) A4
F-4.10 Condition
User Label

F-4.15 Condition
Polarity

Output Point Polarity
F-4.19 Condition
Automatic Event

Output Point Automatic
Event

Output Point Automatic
Events List
1AA 00014 0004 (9711) A4
Function
Status
Service Used
SNMP-GET on outputPointCriteria
configure the polarity of an external output point.
Scope
Service Used
SNMP-SET on outputPointPolarity
request the polarity of an external output point.
Scope
Service Used
SNMP-GET on outputPointPolarity
configure 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
request the event type associated to an output point when the
outputPointCriteria object is set to automatic.
Scope
Service Used
SNMP-GET on:
outputPointAutomaticEventId
outputPointAutomaticEvent
request the 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

MP
If
Output Point
request the operational state of an external output point entry.
Operational State
Scope
Service Used
ED
NTIAL
WTD
Output
01
It.01
3DB161760000DSZZA
27/202
Function
Input
Point SN
Configuration
for MPI
Remotization
f
F-4.22
Creation
of N
remotization of External
Input Point
F-4.23
Deletion
of
remotization of External
Input Point
F-4.24
Remotization
Destination
Request
configure the external input point (identified by
inputPointIndex) to be remotized on external output point of a
specified Ne (identified by IP address to be
provided).
Scope
OPTICSIM-EQPT-MIB:
opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-SET on inputPointRemotizationDestination
SNMP-SET on inputPointRemotizationRowStatus columnar
object to createAndGo value.
delete the remotization of the external input point (identified
by inputPointIndex).
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-SET on inputPointRemotizationRowStatus columnar
object to destroy value.
request the IP address of remote NE on which the external
input point have to be remotized as output point.
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on inputPointRemotizationDestination
Function Input Point

for
Remotization
Status
F-4.25
Request
Remotization Status
ED
WTD
01
It.01
3DB161760000DSZZA
28/202
1AA 00014 0004 (9711) A4
M
PIf
N This management function allows a managing system to request
the status of the last remotization of the input point information
on the NE identified by inputPointRemotizationDestination.
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on inputPointRemotizationStatus
F-4.26
Request N This management function allows a managing system to request
Remotization
Last
the time of the last remotization tried by the local agent.
Update
Scope

SNMP-GET on outputPointOperationalState

OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on inputPointRemotizationLastUpdate
Function Input Point
for
Remotization
Manual Control
F-4.27
Condition
Manual Remotization
M
PIf
N This management function allows a managing system to trigger
a manual updating of the destination output point (updating
value).
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-SET on inputPointManualRemotization
Function Output Point

Configuration
from
Remote Input Point
F-4.28 Creation of
Remote External Input
Point
F-4.29
Remote
Point
1AA 00014 0004 (9711) A4
F-4.30
Remote
ED
NTIAL
WTD
M
PIf
N This management function allows a managing system to identify
the remote external input point which caracteristics have to be
provided on local output point (identified by outputPointIndex).
The managing system has to provide the IP address of the agent
where the remote input point is physically present and the index
(remoteInputPointIndex) of the remote
opticsIMExternalInputPointTable.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteExternalInputPointTable
Service Used
SNMP-SET on
RemoteInputPointAgent
RemoteInputPointIndex
SNMP-SET on remoteInputPointRowStatus columnar object to
createAndGo value.
Deletion of N This management function allows a managing system to delete
External Input
the configuration of local external output point (identified by
outputPointIndex) as remote input point
Scope
Service Used
SNMP-SET on remoteInputPointRowStatus columnar object to
destroy value.
Request N This management function allows a managing system to request
Agent
the IP address of agent where the remote input point is
physically present and the index of the remote input point on
opticsIMExternalInputPointTable.
Scope
Service Used
SNMP-GET on
remoteInputPointAgent
01
It.01
3DB161760000DSZZA
29/202
ED
WTD
01
It.01
M
PIf
N This management function allows a managing system to request
the time of the last update received from the agent concerning
the status of the remote input point.
Scope
Service Used
SNMP-GET on remoteInputPointLastUpdate
3DB161760000DSZZA
30/202

Function Output Point

from Remote Input
Point Status
F-4.31 Request Last
Update from Remote
remoteInputPointIndex
1AA 00014 0004 (9711) A4

3.6.1 Functional Objects Creation

The following tables define the functional objects created by the agent as consequence of the
equipment provisioning process.
Functional Objects
Created
6 opticsIMExternalInputPointEntry
7 opticsIMExternalOutputPointEntry
opticsIMPointToPointIPEntry
(NMS-RF, NMS-V11 and NMS-G.703)
1 opticsIMEowDTMFTTPBidEntry
1 opticsIMEowPartyLineEntry
1 opticsIMAuxiliaryPITTPBidEntry
1 opticsIMCtUserTable
1AA 00014 0004 (9711) A4
1 or 2 opticsIMCoderTTPEntry
1 or 2 opticsIMPdhFrameHopCurrentDataEntry
1 or 2 opticsIMLoopbackEntry [IDU cable
loopback]
1 or 2 opticsIMLoopbackExtEntry [IDU cable
loopback]
1 opticsIMFrameTTPEntry
2 ifMauEntry
2 ifAutoMauEntry
2 opticsIMMauExtEntry
4 opticsIMEthConfEntry
[RPS]
1 opticsIMRadioProtectionGroupEntry
2 opticsIMRadioProtectionUnitEntry
1 opticsIMRadioRxStaticDelayEntry
[EPS] (note 1)
1 opticsIMEquipmentProtectionGroupEntry
2 opticsIMEquipmentProtectionUnitEntry
[PM]
1 opticsIMPdhFrameLinkCurrentDataEntry
1 opticsIMTxProtectionGroupEntry
2 opticsIMTxProtectionUnitEntry
1 or 2 opticsIMRadioPDHTTPBidEntry
1 or 2 opticsIMRadioFrequencyEntry
1 or 2 opticsIMRadioShifterEntry
1 or 2 opticsIMRadioTxPowerEntry
1 or 2 opticsIMRadioTxMuteEntry
1 or 2 opticsIMRadioAnalogueMeasureEntry
2 or 4 opticsIMLoopbackEntry [ODU loopbacks]
2 or 4 opticsIMLoopbackExtEntry [ODU loopbacks]
ED
NTIAL
WTD
01
It.01
Creation Rules
In all the configurations
Only when the P-AC-SC optional plug-in

is configured and only for the main
board.
In all the configurations.
Entry related to the default administrator
user.
1 entry for in all the 1+0 configurations
2 entries in all the 1+1 configurations
In all the configurations

In all the 1+0 and 1+1 ETH
configurations
In all the 1+1 configurations
In all the 1+1 HSB configurations

1 entry in all the 1+0 configurations
When an ODU v2 is discovered:

In the other cases:
3DB161760000DSZZA
31/202
Functional Objects
Created

(note 1)
The objects related to EPS protection will not be created when the 1+1 configurations
without EPS MUX protection will be chosen.
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 the indexes values of all the supported entries are provided too.
The general naming rules for the Equipment objects are defined in [17].
Table Entry
Supported Objects
(Table/Scalar)
Configuration
Description
Indexe
s
Value

Creation Rules
opticsIMEqptMib
ED
WTD
01
It.01
See the Allowed Equipment Type section.
See the Allowed Equipment Type and Remote

Inventory sections.
All the 1+1 (note 1) EPS
3DB161760000DSZZA
32/202
1AA 00014 0004 (9711) A4
opticsIMEquipmentTable
equipmentExpectedTypeId
equipmentExpected
equipmentActual
equipmentAdministrativeState
equipmentOperationalState
equipmentAsapIndex
equipmentLabel
opticsIMRemoteInventoryTable
remoteInventoryStatus
remoteInventoryCompanyIdentifier
remoteInventoryMnemonic
remoteInventoryCLEICode
remoteInventoryPartNumber
remoteInventorySoftwarePartNumber
remoteInventoryFactoryIdentifier
remoteInventorySerialNumber
remoteInventoryDateIdentifier
remoteInventoryDate
remoteInventoryCustomerField
opticsIMEquipmentProtectionGroupTa
ble
opticsIMEquipmentProtectionGroupType
opticsIMEquipmentProtectionGroupRevertiv
e
opticsIMEquipmentProtectionGroupOperati
onalState

Table Entry
Supported Objects
(Table/Scalar)
Configuration
Description
opticsIMEquipmentProtectionUnitTabl All the 1+1 (note 1) EPS Ch#1

e
EPS Ch#0
opticsIMEquipmentProtectionUnitChannelN
umber
opticsIMEquipmentProtectionUnitType
opticsIMEquipmentProtectionUnitSwitchCo
mmand
opticsIMEquipmentProtectionUnitSwitchCrite
ria
opticsIMEquipmentProtectionUnitSwitchStat
us
opticsIMExternalInputPointTable
All
inputPointUserLabel
inputPointExternalState
inputPointPolarity
inputPointAsapIndex
inputPointOperationalState
(note 1)
Indexe
s
Value
4; 1
4; 0
1..6
These objects are not supported in the 1+1 without EPS MUX protection configurations.
Table Entry
Supported Objects
(Table/Scalar)
1AA 00014 0004 (9711) A4
opticsIMExternalOutputPointTable
outputPointUserLabel
outputPointExternalState
outputPointPolarity
outputPointCriteria
outputPointOperationalState
outputPointAutomaticEventId
outputPointAutomaticEvent
opticsIMOutputPointAllowedEventsTable
outputPointAllowedEvent
ED
NTIAL
WTD
01
It.01
Configuratio
n
All
Indexe
Description
s
Value
External output points 1..4
Summarizing
5..7
(see the External
Points
Management
section)
All
See the External 1..8

Points
Management
section.
3DB161760000DSZZA
33/202
Description
Indexe
s
Value
opticsIMTribPortsImpedance
opticsIMHousekeepingAlarmRaise
opticsIMHousekeepingAlarmClear
opticsIMAlarmReplaceableUnitProblemRaise
opticsIMAlarmReplaceableUnitProblemClear
opticsIMAlarmReplaceableUnitMissingRaise
opticsIMAlarmReplaceableUnitMissingClear
opticsIMAlarmReplaceableUnitTypeMismatchRai
se
opticsIMAlarmReplaceableUnitTypeMismatchCle
ar
opticsIMAlarmUnconfiguredEquipmentPresentRa
ise
opticsIMAlarmUnconfiguredEquipmentPresentCl
ear
opticsIMAlarmVersionMismatchRaise
opticsIMAlarmVersionMismatchClear
opticsIMAlarmLanFailureRaise
opticsIMAlarmLanFailureClear
opticsIMAlarmBatteryFailRaise
opticsIMAlarmBatteryFailClear
opticsIMAlarmStandByVersionMismatchRaise
opticsIMAlarmStandByVersionMismatchClear
opticsIMAlarmFirmwareDownloadOnGoingRais
e
opticsIMAlarmFirmwareDownloadOnGoingClea
r
ED
WTD
01
It.01
3DB161760000DSZZA
34/202
1AA 00014 0004 (9711) A4
Configuratio
n

Table Entry
Supported Objects
(Table/Scalar)

TRANSMISSION INTERFACES (IFTABLE)
The following table defines the transmission interface types supported and managed in the ifTable.
Interface
Type
Interface
Number
ifDescr
E1 Tx
up to 32
E1 PPI
E3 Tx (note 2)
DS1 Tx (note 2)
DS3 Tx (note 2)
up to 1
up to 32
up to 1
E3 PPI
DS1 PPI
DS3 PPI
Gigabit Ethernet Tx
up to 4
gigabitEthernet
Radio PDH Frame

(note 3)
up to 2
PDH Radio
Auxiliary (note 4)
Management
Interfaces
V11
G703
PPP
Local Ethernet
LAPD
ifTable
ifType
ifSpeed
18
2 048 000
(note 1)
30
34 368 000
18
1 544 000
30
44 736 000
10 000 000 / 100 000
117
000/ 1000 000 000
78 336 000 (32E1)
39 168 000 (16E1)
1 (other)
19 584 000 (8 E1)
9 792 000 (4 E1)
4 896 000 (2 E1)
64
64 000
66
64 000
23
64 000
10 000 000 / 100 000
6
000
77
38 400
(note 1)
In IANAifType-MIB the e1 value (19) is declared obsoleted. 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 are managed with a proprietary MIB.
(note 2)
Not supported.
(note 3)
ifSpeed object is set according to the frame structure configuration.
(note 4)
ifSpeed object is set according to the auxiliary interface type configuration.
The ifTable entries will be created by the agent as consequence of the provisioning process (i.e. frame
structure and auxiliary channel configuration).
The global number of interfaces and then the value of ifNumber scalar object depends on the
tributaries type and number.
1AA 00014 0004 (9711) A4

The managing system can request (SNMP-GET) the value of the following ifTable objects:
ifDescr
ifType
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
35/202
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.
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 [17].
The following table provides the relationship between ifIndex value and associated proprietary
extension tables.
ifTable
ifIndex
20101
20100
E1 Tx
1yy01 or
1yy99
(note 1)
(note 2)
Gigabit Ethernet 1zz01
Tx
(note 3)
Auxiliary
301
PPP-RF
1
PPP-V11
2
PPP-G703
3
Local Ethernet
100
LAPD/F
200
ED
WTD
01
It.01
Associated
Mib
opticsIMRadioTrsPdhMib
opticsIMRadioTrsCommon
Mib
opticsIMTrsCommonMib
Associated
Table
opticsIMRadioPDHTTPBidTable
opticsIMRadioFrequencyTable
opticsIMRadioShifterTable
opticsIMRadioTxPowerTable
opticsIMRadioAnalogueMeasuresTab
le
opticsIMRadioTxMuteTable
opticsIME1pPITTPTable
opticsIMPdhRAIInsertionTable
mauMod
opticsIMEthNEMib
opticsIMOverheadMib
opticsIMCommRouMib
ifMauTable
opticsIMMauExtTable
opticsIMAuxiliaryPITTPBidTable
opticsIMPointToPointIPTable
opticsIMLocalEthernetTable
-
3DB161760000DSZZA
36/202
1AA 00014 0004 (9711) A4
Interface
Type
Radio PDH
Frame
1AA 00014 0004 (9711) A4

(note 1)
yy = 01..32; 1yy01 in case of 1+0 configurations, 1yy99 in case of 1+1
configurations.
(note 2)
The naming related to 1+0 configuration has to be used when a configuration 1+1
without EPS MUX protection is chosen.
(note 3)
ED
NTIAL
WTD
01
zz = 33..36
It.01
3DB161760000DSZZA
37/202
SDH/PDH TRANSMISSION DOMAIN

1+1 Configurations Functional View
Tx Functional View
<trib>-TX
(sink)
<trib>-RX
(source)
Aggregate
(source)
Radio
(source)
Ch#1
Aggregate
(source)
Radio
(source)
Ch#0
Aggregate
(sink)
Radio
(sink)
Ch#1
MUX
(source)
(note 1)

Rx Functional View
<trib>-RX
(sink)
<trib>-TX
(source)
DEMUX
(sink)
(note 1)
Aggregate
(sink)
Radio
(sink)
Ch#0
RPS hitless
ED
WTD
01
It.01
3DB161760000DSZZA
38/202
1AA 00014 0004 (9711) A4
A bi-directional EPS protection scheme is always supported in all the 1+1 configurations (except in
1+1 configurations without EPS MUX protection, see below).

1+1 Configurations Functional View without EPS MUX protection

In the 1+1 configurations without EPS MUX protection, the functional views are the following:
Tx Functional View
<trib>-TX
(sink)
MUX
(source)
<trib>-RX
(source)
Aggregate
(source)
Radio
(source)
Ch#1
Aggregate
(source)
Radio
(source)
Ch#0
Aggregate
(sink)
Radio
(sink)
Ch#1
Rx Functional View
<trib>-TX
(source)
<trib>-RX
(sink)
DEMUX
(sink)
Aggregate
(sink)
Radio
(sink)
Ch#0
RPS hitless
The mapping between the functional blocks indicated in the functional views above and SNMP MIB
tables is the following:
<trib>-TX
<trib>-RX
MUX, DEMUX
Aggregate
Radio
=>
=>
=>
=>
=>
opticsIME1PathTTPTable
opticsIMFrameTTPTable
opticsIMCoderTTPTable
1AA 00014 0004 (9711) A4
N.B. SNMP tables are created only if necessary from management point of view.
Frame Structure Configuration
The type and number of PDH interfaces (the frame structure configuration) are defined by the F-2.2
management function. According to the market type and NE configurations the allowed frame
structures are defined in the following table. They are impacted also by the content of the SW key
(Flash Card type).
Furthermore:
the 2E1 frame structure configurations cannot be associated to 16 QAM modulation;
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
39/202
Market
Type
ETSI
(note 1)
NE
Configurations
All the Radio configurations 16E1/DS1
(without Ethernet interface) (note 1)
(with Ethernet interface) (note 1)
(note 1)
All the Radio configurations E3/DS3
(note 1)
Allowed Frame
Structures
twoE1, fourE1, eightE1, sixteenE1
twoE1, fourE1, eightE1, sixteenE1,
thirty-twoE1
twoE1, fourE1, eightE1, sixteenE1,
thirty-twoE1
oneE3
The E3/DS3, DS1 tributaries, are not supported.
Hereafter, the supported frame structure configurations and the PDH tributaries objects that must be
created as a consequence of the frame structure definition and of the NE Configurations, are
provided.
NE
Frame Structure
Configuration
twoE1
fourE1
eightE1
sixteenE1
thirty-twoE1
Configurations
Functional Objects Created
All the Radio configurations 2 opticsIME1pPITTPEntry

16E1/DS1 or 32E1/DS1
2 opticsIMPdhRAIInsertionEntry
(note 4)
2 opticsIME1PathTTPEntry
(note 4)
(note 4)
(note 4)
16E1/DS1 (with Ethernet 16 opticsIMPdhRAIInsertionEntry
interface)
(note 3) (note 4)
32E1/DS1
(note 1)
(note 2)
(note 1)
(note 2)
(note 1)
(note 2)
(note 1)
(note 2)
(note 1)
(note 2)
(note 1)
(note 2)
N.B.: The naming of the objects above depends on the configuration. See the ifIndex values in the
naming rule section.
ED
WTD
01
It.01

the 4E1 frame structure configurations cannot be associated to 16 QAM modulation for ODU
v2 4/16QAM (incompatibleCapacity alarm will be raised).
3DB161760000DSZZA
40/202
1AA 00014 0004 (9711) A4

(note 1)
pdhRAIInsertionSignalType object = e1pPI
(note 2)
pdhRAIInsertionSignalType object = e1Path
(note 3)
In this case, the allowed configurations are: M GE 10/100/1000 Base T + N E1/DS1,
where M 4 and N 16.
(note 4)
DS1 signal is not supported.
Additionally, for each pPI and Path functional object created, the associated loopback objects are
created too, according to the schema described in the following table.
Tributary Objects
Created
y pPITTP
(note 1)
y PathTTP
(note 1)
Loopback Objects Created

y
y
y
y
opticsIMLoopbackEntry
opticsIMLoopbackExtEntry
opticsIMLoopbackEntry
opticsIMLoopbackExtEntry
(note 1)
y = up to 32 in case of E1 or DS1 (DS1 not supported), y = 1 in case of E3 or DS3
(E3/DS3 not supported).
ASAP Management
As the Asap Index object is not supported on the <trib>PathTTP tables, the severity of the alarms
addressed to instances of these tables is provided by the ASAP configured for 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 frameTTPTable and coderTTPTable is
provided by the ASAP configured for the associated instance (with the same ifIndex value for
coderTTPTable, related to Ch#1 for frameTTPTable) of the radioPDHTTPBidTable.
BER Measures Management
1AA 00014 0004 (9711) A4
A BER measure is marked as suspect (columnar object berMeasureSuspectIntervalFlag set to TRUE

value) in case of Loss of measurement data in the equipment. This happens if at least one of the
following conditions occurs in the collection period (from Create BER measure entry to request BER
Measure Data):
RUM (Replaceable Unit Missing) alarm on the equipment involved on BER measure.
RUP (Replaceable Unit Problem) alarm on the equipment involved on BER measure (if the
violation data are not accessible)
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
41/202
The following table lists the SDH/PDH Transmission management functions supported in this release
(see [10]).
Generic Trail Termination Point Functions
MP
If
F-1.1 Request TTP ASAP
Pointer
request the 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
Note F-1.1: Supported on the TPs managed in this release.
F-1.2 Condition TTP
ASAP Pointer
configure the ASAP Pointer associated to a trail termination
point.
Scope
Trail
Termination
Point
(xTTPBidTable)
Service Used
SNMP-SET on: xTTPBidAsapIndex columnar object
Note F-1.2: Supported on the TPs managed in this release.
Function TP Status
F-1.3 Request TTP
Operational State

MP
If
request the operational state of a trail termination point.
Scope
Trail
Termination
Point
(xTTPBidTable)
Service Used
SNMP-GET on xTTPBidOperationalState columnar object
F-1.xx All the functions
ED
WTD
01
It.01
MP
If
N
3DB161760000DSZZA
42/202
1AA 00014 0004 (9711) A4
SDH Functions
Trail Termination Point

Function Notifications
Automatic Laser Shutdown

Functions
PDH Frame Functions
Function Configurations
F-2.1 Request Frame
Structure Configuration
F-2.2 Condition Frame

Structure Configuration
F-2.3 Request Link

Identifier Parameters
1AA 00014 0004 (9711) A4
MP
If
N
ED
NTIAL
WTD
01
It.01
MP
If
N
MP
If
request the configuration of the frame structure.
Scope
OPTICSIM-TRS-PDH-MIB:
opticsIMFrameStructureConfiguration
Service Used
SNMP-GET
on
the
scalar
object
set the configuration of the frame structure.
Scope
Service Used
SNMP-SET
on
the
scalar
object
request 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
opticsIMLinkIdMngt
Service Used
SNMP-GET on the following scalar objects:
opticsIMLinkldExpectedMode
3DB161760000DSZZA
43/202
ED
WTD
01
It.01
3DB161760000DSZZA
44/202

1AA 00014 0004 (9711) A4
opticsIMLinkIdExpectedValue
opticsIMLinkIdSentValue
F-2.4 Condition Link
Identifier Parameters
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
opticsIMLinkIdMngt
Service Used
SNMP-SET on:
opticsIMLinkldExpectedMode
opticsIMLinkIdExpectedValue
opticsIMLinkIdSentValue
Note F-2.4: Allowed values: 0 31.
F-2.5 Condition BER
N This management function allows the managing system to
set the thresholds used to raise the highBER and lowBER
Alarms Thresholds
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
opticsIMBERThresholdMngt
Service Used
SNMP-SET on the following scalar objects:
opticsIMHighBERThr
opticsIMLowBERThr
F-2.6 Request BER
Alarms Thresholds
request the thresholds used to raise respectively a PDH
highBER and lowBER alarms.
Scope
Service Used
opticsIMHighBERThr
opticsIMLowBERThr
F-2.7 Request BER
Alarms Thresholds
request the minimum and maximum values allowed for the
thresholds used to raise the PDH highBER and lowBER
Ranges
alarms.
Scope
Service Used
opticsIMHighBERMinThr
opticsIMHighBERMaxThr

F- 2.11 Request
interleaving status
F- 2.12 Condition
interleaving function
F- 2.13 Condition EW
alarm BER Thresholds
F- 2.14 Request EW
F- 2.15 Request EW
Ranges
opticsIMLowBERMinThr
opticsIMLowBERMaxThr
request the status of interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB
Service Used
SNMP-GET
on
the
following
scalar
object
opticsIMInterleaving.
enable/disable the interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB
Service Used
SNMP-SET
on
the
following
scalar
object
opticsIMInterleaving.
set the BER threshold used to raise the EW alarm. This value
must be included in the allowed range.
Scope
Service Used
opticsIMEWBERThr
request the BER thresholds used to raise a EW alarm.
Scope
Service Used
opticsIMEWBERThr
BER thresholds used to raise EW alarm.
Scope
Service Used
opticsIMEWBERMinThr
opticsIMEWBERMaxThr
1AA 00014 0004 (9711) A4
MP
If
F-2.9 Report PDH Frame Y This management function allows a managed system to
Alarms
report transmission alarms related to the PDH frame.
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmLossOfFrameRaise
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
45/202
ED
WTD
01
It.01
3DB161760000DSZZA
46/202

1AA 00014 0004 (9711) A4
F-2.10 Report PDH

Coder Alarms
opticsIMAlarmLossOfFrameClear
opticsIMAlarmLinkIdentifierMismatchRaise
opticsIMAlarmLinkIdentifierMismatchClear
This management function allows a managed system to
report transmission alarms related to the PDH coder.
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmCableLOSRaise
opticsIMAlarmCableLOSClear
opticsIMAlarmHighBERRaise
opticsIMAlarmHighBERClear
opticsIMAlarmLowBERRaise
opticsIMAlarmLowBERClear
1AA 00014 0004 (9711) A4

PDH Tributaries Functions

MP
If
F-3.1 Request E1 Signal
Processing Mode
request which processing mode is activated on an E1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB:
Service Used
SNMP-GET on e1pPITTPSignalMode
F-3.2 Condition E1
Signal Processing Mode
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 framed (G.704) modes are supported.
F-3.3 Request E1 Frame
Status
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
SNMP-GET on (respectively):
e1pPITTPFrameStatus
e1PathTTPFrameStatus
F-3.4 Request RAI
Insertion Status
request the status of the RAI insertion in a E1 or DS3 framed
signal.
Scope
Service Used
SNMP-GET on:
pdhRAIInsertionSignalType
pdhRAIInsertionStatus
Note F-3.4: Supported only on E1 signals (pPI and Path).
F-3.5 Condition RAI
Insertion Status
condition the RAI insertion inhibition in a E1 or DS3 framed
signal, both physical interface and path side. The status
allowed are the following:
enabled
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
47/202
ED
WTD
01
It.01
3DB161760000DSZZA
48/202

1AA 00014 0004 (9711) A4
inhibited
forced
Scope
Service Used
SNMP-SET on pdhRAIInsertionStatus
Note F-3.5: Supported only on E1 signals (pPI and Path). Values supported:
enabled
forced
F-3.8 Request E3 Signal
Processing Mode
request which processing mode is activated on a E3 signal.
Scope
Service Used
SNMP-GET on e3pPITTPSignalMode
F-3.9 Condition E3
condition 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: the framed (G.704) G.753 value is not supported
F-3.10 Request DS1
request which processing mode is activated on a DS1 signal.
Scope
opticsIMDs1pPITTPTable
Service Used
SNMP-GET on ds1pPITTPSignalMode
F-3.11 Condition DS1
condition 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
1AA 00014 0004 (9711) A4

F-3.12 Request DS3


F-3.14 Request DS1 Line

Coding

Line Coding
F-3.16 Condition Global

DS1 Line Coding

Length

Line Length
ED
NTIAL
WTD
01
It.01

request which processing mode is activated on a DS3 signal.
Scope
Service Used
SNMP-GET on ds3pPITTPSignalMode
condition 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
request the line coding of a DS1 signal.
Scope
Service Used
SNMP-GET on ds1pPITTPLineCoding
condition the line coding of a DS1 signal. The allowed
values are the following:
AMI
B8ZS
Scope
Service Used
SNMP-SET on ds1pPITTPLineCoding
specify, in one shot, the code for all the DS1 lines.
Scope
opticsIMAllDs1LineCoding
Service Used
SNMP-SET on the scalar opticsIMAllDs1LineCoding
request the length of a DS1 line. It provides information for
Line Build Out circuitry.
Scope
Service Used
SNMP-GET on ds1pPITTPLineLength
condition the length of a DS1 line.
3DB161760000DSZZA
49/202

Length Allowed Ranges
F- 3.33 Request E1/DS1

AIS Signal Type
F- 3.34 Condition E1/DS1

AIS Signal Type
F- 3.35 Condition Global

E1/DS1 AIS Signal Type
ED
WTD
01
It.01
3DB161760000DSZZA
50/202

1AA 00014 0004 (9711) A4
F-3.19 Condition Global

DS1 Line Length
Scope
Service Used
SNMP-SET on ds1pPITTPLineLength
condition, in one shot, the length of all the DS1 lines.
Scope
opticsIMAllDs1LineLength
Service Used
SNMP-SET on the scalar object opticsIMAllDs1LineLength
request the ranges of Ds1 line lengths allowed on NE.
Scope
opticsIMAllowedDS1LineLengthsTable
Service Used
SNMP-GET on
allowedLineLengthId
allowedLineLengthMin
allowedLineLengthMax
request which AIS Signal type (allOnes or AllZeroes) is
activated on an E1 signal or on DS1 signal.
Scope
opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-GET
on
e1pPITTPAISSignalType
(opticsIME1pPITTPTable)
or
ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
condition 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).
condition, 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
Service Used
SNMP-SET on the scalar object opticsIMAllE1AISSignalType
or opticsIMAllDS1AISSignalType.
1AA 00014 0004 (9711) A4


pPI AIS Insertion

pPI AIS Insertion

E1/DS1 pPI AIS Insertion

Path AIS Insertion

Path AIS Insertion

E1/DS1 Path AIS
Insertion
ED
NTIAL
WTD
01
It.01

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)
enable/disable the AIS Signal insertion for 2 Mbit/sor for 1,5
Mbit/s PDH trails.
Scope
opticsIMDS1pPITTPTable.
Service Used
SNMP-SET on e1pPITTPAISInsertion (opticsIME1pPITTPTable)
or ds1pPITTPAISInsertion (opticsIMDS1pPITTPTable).
condition, in one shot, the AIS Signal insertion for all the 2
Mbit/s or for all the 1,5 Mbit/s PDH trails.
Scope
Service Used
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion
or opticsIMAllDS1pPIAISInsertion
request if insertion of AIS Signal is activated on 2 Mbit/s or
1,5 Mbit/s path.
Scope
opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable
Service Used
SNMP-GET
on
e1PathTTPAISInsertion
(opticsIME1PathTTPTable)
or
ds1PathTTPAISInsertion
(opticsIMDS1PathTTPTable).
enable/disable the AIS Signal insertion for 2 Mbit/s or 1,5
Mbit/s path.
Scope
opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable.
Service Used
SNMP-SET
on
e1PathTTPAISInsertion
(opticsIME1PathTTPTable)
or
ds1PathTTPAISInsertion
(opticsIMDS1PathTTPTable).
Mbit/s or 1,5 Mbit/s paths.
Scope
Service Used
3DB161760000DSZZA
51/202
F- 3.43 Condition DS3

AIS Signal Type

DS3 AIS Signal Type
F- 3.45 Request DS3 pPI

AIS Insertion

pPI AIS Insertion

DS3 pPI AIS Insertion
F- 3.48 Request DS3 Path

AIS Insertion
ED
WTD
01
It.01
3DB161760000DSZZA
52/202

1AA 00014 0004 (9711) A4
F- 3.42 Request DS3 AIS

Signal Type
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion

or opticsIMAllDS1pPIAISInsertion.
request which AIS Signal type (allOnes or blueSignal) is
activated on an DS3 signal. It is applicable only on framed
signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-GET on ds3pPITTPAISSignalType
condition 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
condition, in one shot, the AIS Signal Type (allOnes or
blueSignal) of all the DS3 lines. It is applicable only on
framed signals.
Scope
Service Used
SNMP-SET on the scalar object opticsIMAllDS3AISSignalType
request if insertion of AIS Signal is activated on 45 Mbit/s
PDH trails. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPAISInsertion
enable/disable the AIS Signal insertion for 45 Mbit/s PDH
trails. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPAISInsertion.
Mbit/s PDH trails. It is applicable only on framed signals.
Scope
Service Used
SNMP-SET on the scalar object opticsIMAllDs3pPIAISInsertion
request if insertion of AIS Signal is activated on 45 Mbit/s
path. It is applicable only on framed signal.
1AA 00014 0004 (9711) A4

Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-GET on ds3PathTTPAISInsertion.
Path AIS Insertion
enable/disable the AIS Signal insertion for 45 Mbit/s path. It
is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3PathTTPAISInsertion.
F- 3.50 Condition Global N This management function allows a managing system to
DS3 Path AIS Insertion
Mbit/s paths. It is applicable only on framed signals.
Scope
Service Used
SNMP-SET
on
the
scalar
object
opticsIMAllDs3PathAISInsertion
F- 3.51 Request DS3 AIS
Signal Timing
request 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 an DS3 line. It is applicable
only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPAISSignalTiming
Note F-3.51: The time waiting for the insertion and the removing AIS signal is 3 msec.
AIS Signal Timing
condition 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
Scope
Service Used
SNMP-SET on ds3pPITTPAISSignalTiming
F- 3.53 Condition Global N This management function allows a managing system to
DS3 AIS Signal Timing
condition, 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 signals.
Scope
Service Used
SNMP-SET
on
the
scalar
object
opticsIMAllDS3AISSignalTiming
F- 3.54 Request DS3 pPI
Parity Violation
request if Parity Violation Monitoring Removing is enabled or
Monitoring Removing
disabled on 45 Mbit/s trail. It is applicable only on framed
signal.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
53/202

DS3 pPI Parity Violation
Monitoring Removing
F- 3.57 Request DS3 Path

Parity Violation
Monitoring Removing

Path Parity Violation
Monitoring Removing

DS3 Path Parity Violation
Monitoring Removing
F- 3.60 Request DS3 Idle

insertion and detection
ED
WTD
01
It.01
3DB161760000DSZZA
54/202

1AA 00014 0004 (9711) A4

pPI Parity Violation
Monitoring Removing
Scope
Service Used
SNMP-GET on ds3pPITTPParityViolationMonitoringRemoving.
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.
condition, in one shot, the Parity Violation Monitoring
Removing for all the 45 Mbit/s trails. It is applicable only on
framed signals.
Scope
Service Used
SNMP-SET
on
the
scalar
object
opticsIMAllDs3pPIParityViolationMonitoringRemoving
request if 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.
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.
condition, in one shot, the Parity Violation Monitoring
Removing for all the 45 Mbit/s paths. It is applicable only on
framed signals.
Scope
Service Used
SNMP-SET
on
the
scalar
object
opticsIMAllDs3PathParityViolationMonitoringRemoving
request if idle insertion is activated on one direction and the
status (detection) of idle insertion on the other direction for
an DS3 signal. It is applicable only on framed signal.
1AA 00014 0004 (9711) A4


Idle insertion
F- 3.62 Request DS3

Line Bridge Status

Line Bridge
F- 3.64 Request E1/E3

pseudo-random pattern
insertion
F- 3.65 Condition E1/E3

pseudo-random pattern
insertion
ED
NTIAL
WTD
01
It.01
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-GET on
ds3pPITTPIdleInsertion
ds3pPITTPIdleDetection
condition the idle insertion on an DS3 signal. It is applicable
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPIdleInsertion
request if this selected DS3 line is used to bridge and other
DS3 line.
Scope
Service Used
SNMP-GET on
ds3pPITTPInputBridgeEnabled
configure 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
request if insertion of pseudo-random pattern is activated on
tributary x (E1 or E3 signal).
Scope
, opticsIME3pPITTPTable
Service Used
SNMP-GET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable)
or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
condition the insertion of pseudo-random pattern on
tributary x (E1 or E3 signal).
Scope
, opticsIME3pPITTPTable
3DB161760000DSZZA
55/202
ED
WTD
01
It.01
3DB161760000DSZZA
56/202
1AA 00014 0004 (9711) A4
MP
If
F-3.20 Report PDH
Y This management function allows a managed system to
Physical Interface Alarms
report transmission alarms related to PDH physical
interfaces.
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmLossOfSignalRaise
opticsIMAlarmLossOfSignalClear
opticsIMAlarmAisRaise
opticsIMAlarmAisClear
opticsIMAlarmRemoteDefectIndicationRaise (E1 and
DS3 only)
opticsIMAlarmRemoteDefectIndicationClear (E1 and
DS3 only)
Note F-3.20: The following SNMP-TRAP are referred only to PDH framed tributaries:
opticsIMAlarmLossOfFrameRaise/Clear
opticsIMAlarmRemoteDefectIndicationRaise/Clear
F-3.21 Report PDH Path
Y This management function allows a managed system to

Service Used
SNMP-SET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable)
or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
F- 3.66p Create Time
Y This function allows to set the Time Slot number inside the E1
Slot number inside E1
tributary to transport the TMN.
Scope
tributary for TMN in
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
frame management
Service Used
SNMP-SET on e1pPITTPTimeSlotTMN.
F- 3.67p Request Time
Y This function allows to get the Time Slot number inside the
Slot number inside E1
E1 tributary to transport the TMN.
Scope
tributary for TMN in
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
frame management
Service Used
SNMP-GET on e1pPITTPTimeSlotTMN.
Note F-3.66p and F-3.67p: The default value is -1: it means the E1 tributary is not able to
transport the TMN. Only the E1#1 is able to transport the TMN in frame: the Time Slot number
can be chosen in the range 131 (the TS=16 is not allowed).

Alarms
F-3.22 Report PDH Loss

Alarm Due to Switch
report transmission alarms related to PDH paths.

Scope
opticsIMDs1PathTTPTable
opticsIMDs3PathTTPTable
Service Used
SNMP-TRAP:
opticsIMAlarmRemoteDefectIndicationRaise (E1 and
DS3 only)
opticsIMAlarmRemoteDefectIndicationClear (E1 and
DS3 only)
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
F-3.30 Create BER
Measure Entry
1AA 00014 0004 (9711) A4
F-3.31 Delete BER

Measure Entry
ED
NTIAL
WTD
01
It.01
MP
If
create a BER measure entry. The management system has to
indicate in the creation request: the monitoring point which it
is associated to (indicated by means of ifIndex).
Scope
opticsIMBERMeasureTable
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
createAndGo value
delete a BER measure entry.
Scope
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
destroy value
3DB161760000DSZZA
57/202

request the BER measure data related to the current
observation period.
Scope
Service Used
SNMP-GET on the following columnar objects:
berMeasureElapsedTime
berMeasureSuspectIntervalFlag
berMeasureViolations
berMeasureValue
Note F-3.32: berMeasureViolations is not supported.

F-3.32 Request BER

Measure Data
For each table, according to the configuration the indexes values of all the supported entries are
provided too.
The general naming rules for the SDH/PDH Transmission objects are defined in [17].
N.B. In the following table, when the configuration is 1+1 without EPS MUX protection, then the
indexes value are those one used for the All the 1+0 configuration, except for
opticsIMBERMeasureTable, opticsIMFrameTTPTable and opticsIMCoderTTPTable because they are
referred to radio port.
Supported Objects
(Table/Scalar)
Table Entry
Configura
tion
Description
Indexes
Value
opticsIMTrsCommonMib
e1PathTTPOperationalState
All the 1+0 E1 Tx ports Ch#1

All the 1+1 E1
Tx
ports
Ch#Common
All the 1+0 E1 Rx ports Ch#1
All the 1+1 E1
Rx
ports
Ch#Common
ED
WTD
01
It.01
All the 1+0 Radio port Ch#1

1xx01
(xx
01..32)
1xx99
(xx
01..32)
2xx01
(xx
01..32)
2xx99
(xx
01..32)
20101
20101
=
=
=
=
3DB161760000DSZZA
58/202
1AA 00014 0004 (9711) A4
e1pPITTPSignalMode
e1pPITTPOperationalState
e1pPITTPAsapIndex
e1pPITTPTimeSlotTMN

Supported Objects
(Table/Scalar)
Table Entry
Configura
tion
Description
berMeasureElapsedTime
Radio port Ch#0
berMeasureSuspectIntervalFlag
berMeasureValue
berMeasureRowStatus
opticsIMPdhRAIInsertionTable All the 1+0 E1 Rx ports Ch#1
pdhRAIInsertionSignalType
pdhRAIInsertionStatus
E1 Tx ports Ch#1
Rx
ports
All the 1+1 E1
Ch#Common
E1
Tx
ports
Ch#Common
Indexes
Value
20100
1xx01;
e1pPI
(xx
01..32)
2xx01;
e1Path
(xx
01..32)
1xx99;
e1pPI
(xx
01..32)
2xx99;
e1Path
(xx
01..32)
opticsIMAlarmLinkIdentifierMismatc
hRaise
opticsIMAlarmLinkIdentifierMismatc
hClear
opticsIMTrsPdhMib
frameTTPOperationalState
coderTTPOperationalState

All the 1+1 Radio
port
Ch#Common
Radio port Ch#0
20101
20199
20101
20101
20100
1AA 00014 0004 (9711) A4
opticsIMFrameStructureConfigurati
on
opticsIMLinkExpectedMode
opticsIMLinkExpectedValue
opticsIMLinkSentValue
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
59/202
ETHERNET TRANSMISSION DOMAIN

This domain is significant only in case of Ethernet configurations. The Ethernet configurations are the
following:
1+0
1+1 HSB
1+1 FD
16E1/DS1-ETH
16E1/DS1-ETH
16E1/DS1-ETH
(PSU4860, PSU2460)
(PSU4860, PSU2460)
(PSU4860, PSU2460).
The DS1 signal is not supported.

In terms of Ethernet interface management, the ULS supports the following functional layers:
Ethernet Physical Interface Layer (MAU and ETY_T functional blocks, see [18])
Ethernet Port Layer (ETH and EFC functional blocks, see [20])

Ethernet Physical Interface and Ethernet Port Layers

The Ethernet interfaces can be configured according to two different modalities: manual mode or
automatic mode (auto-negotiation is enabled, by default) by ifMauAutoNegAdminStatus object (see
new F-8.7p): these two modalities are valid only automatic mode for Gigabit Ethernet signals.
The ifMauAutoNegSupported object is set to true value.
In automatic mode a mechanism of auto-sensing (the auto-negotiation) of the parameters involved is
activated, these parameters are negotiated with the remote Ethernet interface.
auto-negotiation is always enabled only in case of Gigabit Ethernet signal;
the operator can plan one or a set of rates (10 and/or 100 and/or 1000 Mb/s) and to allow to
auto-negotiate them;
the directionality can be half or full-duplex (when the 10 and/or 100 Mb/s rates are chosen, the
directionality can be half or full duplex, when the 1000 Mb/s rate is chosen, the directionality is
always full-duplex);
when the auto-negotiation process fails or when the auto-negotiation parameters are changed,
the auto-negotiation restart command has to be performed in order to have new configured
parameters effective.
In manual mode, the ifMauTypeListBits object contains all the values for the rate and the
directionality allowed on the interface. The allowed values are:
b10baseTHD (10)
- rate 10 Mb/s half-duplex
b10baseTFD (11)
- rate 10 Mb/s full-duplex
b100baseTXHD (15)
b100baseTXFD (16)
ED
WTD
01
It.01
3DB161760000DSZZA
60/202
1AA 00014 0004 (9711) A4
The following items resume the features supported by ULS in terms of Gigabit Ethernet Physical
interface management:

The rate, the directionality and the Flow control are configurable with the following values:
F-7.11 (ifMauDefaultType)
with a specific value selected on ifMauTypeListBits.
F-8.8p (opticsIMEthDefaultPause)
disabled (0)
Flow Control disabled
asymmetric-PAUSE (1),
asymmetric Flow Control enabled
In automatic mode, the ifMauAutoNegCapabilityBits object contains all the values for the rate,
the directionality and the Flow control allowed on the interface. The allowed values are:
b10baseT (1)
b10baseTFD (2)
b100baseTX (4)
b100baseTXFD (5)
bFdxAPause (9)
- Asymmetric PAUSE for full-duplex links
b1000baseTFD (15)
The rate, the directionality and the Flow control are configurable with the following values:
F-8.3 (ifMauAutoNegCapAdvertisedBits) with a set of values selected
ifMauAutoNegCapabilityBits.
on
The auto-negotiation enabling (ifMauAutoNegAdminStatus set to true value) triggers the start of
the auto-negotiation process (to clarify, every time the auto-negotiation process is enabled (that is,
from manual to automatic mode), then the auto-negotiation is restarted automatically).
When the auto-negotiation process fails or when the auto-negotiation parameters are changed, the
auto-negotiation restart command has to be performed in order to have new configured parameters
effective (to clarify, first of all, the operator changes the parameters, pushes Apply button (the
parameters are not yet realized) and then, he has to push the Restart button to apply the parameters
really).
1AA 00014 0004 (9711) A4
The ifMauType (F-7.12p) contains or the result of the auto-negotiation process or the value of the
object ifMauType in case the auto-negotiation is not enabled.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
61/202
The QoS on Ethernet User ports is managed at NE level (for all Ethernet User port).
The QoS is always enabled.
The managing system is allowed to:
1. Assigning the specific queue on output port according to 802.1P priority bits on Ethernet packets
2. Assigning the specific queue on output port according to DiffServ priority bits on Ethernet packets
About the managing system:
the QoS is managed using a specific entry on opticsIMInFlowTable (with inFlowIndex = 1500)
and the inflowClassificationMode columnar object;
the managing system has to create the entry (F-2.x) with the parameters:
o
o

Ethernet User ports QoS management
inflowIndex = 1500
classificationMode set to:
0 for 802.1P priority classification
1 for DiffServ priority classification
Ethernet Port Layer
the Pause function is allowed only when the capability is full-duplex;
the Pause function can be supported in automatic or manual mode;
the Ethernet Flow Control (EFC) can be enabled or disabled; when it is enabled, PAUSE function
can be symmetric and asymmetric (IEEE 802.3x); the supported asymmetric case is related to
allowed Pause at transmission side, no allowed Pause at receiver side;
in case of remote peer MAC layer without EFC feature, the overflow of the input queues causes to
discard any further received MAC frames: a correct frame received and discarded because of an
input queues overflow, is not counted as a received frame;
total transparency towards the IEEE 802.1Q (VLAN management will be supported in future);
Ethernet corrupted frames (Tx and Rx side independently) can be discarded or forwarded to the
addressed destination, according to the related SNMP manager request.
ED
WTD
01
It.01
3DB161760000DSZZA
62/202
1AA 00014 0004 (9711) A4
The following items resume the features supported by ULS in terms of Gigabit Ethernet Port layer
management:

1+1 with Hitless Configurations Functional View

Ethernet plug-in can be provisioned in all the 1+0 and 1+1 with hitless configurations.
Tx Functional View
Main/DATA
MAU
(sink)
ETH-EFC
(sink)
ODU
Main
ETH
(source)
Aggregate
(source)
MUX
(source)
Aggregate
(source)
Ext.
Radio
(source)
Radio
(source)
Ch#1
Ch#0
ODU
Rx Functional View
Main/DATA
MAU
(source)
ETH-EFC
(source)
ETH
(sink)
Aggregate
(sink)
DEMUX
(sink)
Aggregate
(sink)
RPS hitless
N.B.
ODU
Main
Ext.
MAU includes also the ETY_T functional block.
Radio
(sink)
Radio
(sink)
Ch#1
Ch#0
ODU
The mapping between the functional blocks indicated above and MIB tables is the following:
MAU
ETH-EFC, ETH
=>
=>
ifMauTable, ifMauAutoNegTable, opticsIMMauExtTable

opticsIMEthConfTable
Frame Structure Configuration with Ethernet interfaces
1AA 00014 0004 (9711) A4
With the Gigabit Ethernet interfaces (100/1000 Base-T), the PDH transport capability is always less
than the maximum input bit rate, whereas in case of 10Base-T, the PDH transport capability can be
larger or smaller than the maximum input bit rate, according to the number of tributaries to be
transported.
Also when Ethernet signals have to be transported, the gross bit rate at the output of the Mux is
defined by the frame structure configuration (capacity) provided by the manager (i.e. 16xE1). Given a
gross bit rate, the following combinations of voice and data can be realized:
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
63/202
twoE1
fourE1
eightE1
sixteenE1
thirty-twoE1
oneE3
fourDS1
eightDS1
sixteenDS1
thirty-twoDS1
oneDS3
Number of
GE
4
(note
(note
(note
(note
(note
(note
(note
1)
1)
1)
1)
1)
1)

Frame Structure
Configuration
(Capacity)
Number of PDH
Tributaries
1 E1
3 E1
7 E1
7 or 15 E1
16 E1
Not allowed
3 DS1
7 DS1
7 or 15 DS1
16 DS1
Not allowed
2)
(note 1)
DS1, E3/DS3 signals are not supported.
(note 2)
The space reserved for the data transport is 51,184 Mbit/s, using also the remaining
inframe space (6,048 Mbit/s). not supported
ASAP Management
The severity of alarms addressed to instances of opticsIMEthConfTable is provided by the ASAP
configured for the associated instance (with the same ifIndex value for the line side instances, with the
same port identifier for the radio side instances) of the corresponding ifMauTable.
Automatic Link Shutdown
ED
WTD
01
It.01
3DB161760000DSZZA
64/202
1AA 00014 0004 (9711) A4
The F-8.4 (set) and F-8.5 (get) functions are supported in this release to shutdown the ethernet port;
the shutdown is really performed when one (or more) radio failure criteria happens; the default value
is the port shutdown is disabled.
This function is related to a single ethernet port; in our case, the four ethernet ports are linked to the
only radio port; when a criteria radio happens and the port shutdown is enabled, the behavior to
implement is that all the ethernet ports have to be put in shutdown.
When the radio criteria expires, then, all the four ethernet ports have to be enabled.


The following table lists the Ethernet Transmission management functions supported in this release.
See [18] and [19].
6.2.1 Ethernet Physical Interface Management
Electrical Fast Ethernet MAU Management
Function
Activation/Deactivation
F-1.1 Request FE MAU
Status
F-1.6 Condition FE MAU

Status

Operational State
MP
If
N This function is used to retrieve MAU object status with 2
admitted values depending of Activate state of the MAU:
Operational(3): the MAU is electrically switched on.
Shutdown(5): the MAU is electrically switched off.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauStatus
N This function is used to explicitly activate (ifMauStatus =
Operational) or deactivate (ifMauStatus = Shutdown) the
MAU.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-SET on ifMauStatus
N This function is used to retrieve the MAU Operational State.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauMediaAvailable
Note F-1.7: Allowed values:
available (3)
notAvailable (4)
1AA 00014 0004 (9711) A4

Jack Type

Default Type
ED
NTIAL
WTD
01
It.01
MP
If
N This function is used to request FE MAU jack type. FE MAU
always rely on rj45 (2) jack types.
Scope
MAU-MIB: ifJackTable
Service Used
SNMP-GET on ifJackType
N This function is used to operate on FE MAU default type:
dot3MauType10BaseTFD: 10BaseT full-duplex
dot3MauType100BaseTxFD: 100BaseTx full-duplex
This operation can be performed only when the
ifAdminStatus/ifMauStatus of supporting Ethernet interface is
3DB161760000DSZZA
65/202
Function Notification
F-1.5 Report FE MAU
Alarm
ED
WTD
01
It.01
MP
If
N This function is used to report a cLOS alarm.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-TRAP on opticsIMAlarmLossOfSignalRaise
SNMP-TRAP on opticsIMAlarmLossOfSignalClear
3DB161760000DSZZA
66/202

1AA 00014 0004 (9711) A4
down.
By
default
the
100BaseTx
full-duplex
operation
(dot3MauType100BaseTxFD) is assumed.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-SET on ifMauDefaultType
Note F-1.3: ifMauStatus is not currently included in ANNEX to Ethernet Physical Interface
Management Functional Specification.
N This function is used to request FE MAU capability data with
Capability Data
below retrieved information:
Whether auto-negotiation is supported;
The available MAU types (10BaseT/100BaseTX);
The actual default MAU type.
The available MAU types (see ifMauTypeListBits [2]) is defined
as:
b10baseTFD (11) = 1
b100baseTXFD (16) = 1
Other bits = 0
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on:
IfMauAutoNegSupported
IfMauTypeListBits
IfMauDefaultType
F-1.8 Change FE MAU
N This function is used to configure the ASAP Pointer associated
ASAP Pointer
to an Ethernet Interface.
Scope
OPTICSIM-ETHNE-MIB: opticsIMifMauExtTable
Service Used
SNMP-SET on opticsIMifMauExtAsapIndex
N This function is used to request the ASAP Pointer associated to
ASAP Pointer
an Ethernet Interface.
Scope
Service Used
SNMP-GET on opticsIMifMauExtAsapIndex
1AA 00014 0004 (9711) A4

Electrical Fast Ethernet Ety_T Management

F-2.1 Condition
Enabled/Disabled FE
Auto-Negotiation

Auto-Negotiation Status
F-2.3 Restart FE AutoNegotiation

ED
NTIAL
WTD
01
It.01
MP
If
N This function is used to enable (ifMauAutoNegAdminStatus =
enabled) or disable (ifMauAutoNegAdminStatus = disabled)
the auto-negotiation. This operation can be performed only
when the ifAdminStatus of supporting Ethernet interface is
down.
Scope
MAU-MIB: ifMauAutoNegTable
Service Used
SNMP-SET on ifMauAutoNegAdminStatus
N This function is used to request the MAU auto-negotiation
status. The retrieved informations are:
Whether or not the auto-negotiation is enabled
(ifMauAutoNegAdminStatus)
The current status of the auto-negotiation process
(ifMauAutoNegConfig)
The auto-negotiation capabilities supported by the local
(ifMauAutoNegCapabilityBits)
The auto-negotiation capabilities advertised by the local
(ifMauAutoNegCapAdvertisedBits)
The auto-negotiation capabilities advertised by the remote
(ifMauAutoNegCapReceivedBits)
The available IfMauAutoNegCapabilityBits is defined by NE

as:
b10baseTFD (2) = 1
bFdxPause(8) = 1 if Flow Control is supported (0
otherwise)
bFdxAPause(9) = 1 if Asymmetric Flow Control is
supported (0 otherwise)
bFdxSPause(10) = 0
bFdxBPause(11) = 0
Other bits = 0
Scope
Service Used
SNMP-GET on:
ifMauAutoNegAdminStatus
ifMauAutoNegConfig
ifMauAutoNegCapabilityBits
ifMauAutoNegCapAdvertisedBits
ifMauAutoNegCapReceivedBits
After the restart, the agent will reset the ifMauAutoNegRestart
to its default value: noRestart(2).
Scope
3DB161760000DSZZA
67/202
Scope
Service Used
SNMP-SET on ifMauAutoNegCapAdvertisedBits
ED
WTD
01
It.01
3DB161760000DSZZA
68/202

1AA 00014 0004 (9711) A4

Auto-Negotiation
Advertised Capability
Service Used
SNMP-SET on ifMauAutoNegRestart to restart(1)
This function is used to operate on the FE MAU capabilities
advertised during the auto-negotiation.
The FE mode operations:
Speed Negotiation: 10BASE-T full duplex mode,
b10baseTFD(2).
Speed Negotiation: 100BASE-TX full duplex mode,
b100baseTXFD(5).
Pause
operation:
PAUSE
for
full-duplex
links,
bFdxPause(8).
Pause operation: Asymmetric PAUSE for full-duplex links,
bFdxAPause(9).
Pause operation: Symmetric PAUSE for full-duplex links,
bFdxSPause(10).
Pause operation: Asymmetric and Symmetric PAUSE for
full-duplex links, bFdxBPause(11).
Advertised Capability Bits (IfMauAutoNegCapAdvertisedBits)
default values:
b10baseTFD(2) = 0.
b100baseTXFD(5) = 1.
bFdxPause(8)
=
corresponding bit value.
bFdxAPause(9)
=
bFdxSPause(10)
=
bFdxBPause(11)
=
Other bits = 0.
Checks
No bit in IfMauAutoNegCapAdvertisedBits can be set to 1
if the corresponding bit in ifMauAutoNegCapabilityBits is
0.
The manager should set to 1 either b10baseTFD(2) or
b100baseTXFD(5). That is, only one of speed negotiation
bits should be 1.
No PAUSE mode is configured by setting:
bFdxPause(8) = 0, bFdxAPause(9) = 0,
bFdxSPause(10) = 0, bFdxBPause(11) = 0.
Asymmetric PAUSE towards link partner is configured by
setting: bFdxPause(8) = 1, bFdxAPause(9) = 1,
bFdxSPause(10) = 0, bFdxBPause(11) = 0

Note F-2.4: Bits settable to 1:

b10baseTFD(2)
b100baseTXFD(5)
The other bits assume the ifMauAutoNegCapabilityBits corresponding bits values.
N This function is used to retrieve the FE Jabber State.
Jabber State
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauJabberState
Optical Fast Ethernet MAU Management
Not supported.
Optical Fast Ethernet Ety_T Management
Not supported.
Gigabit Ethernet MAU Management
Function
F-7.1 Request Electrical
GE MAU Status
F-7.2 Condition
Electrical GE MAU
Status

GE MAU Operational
State
S Function Description
N
M
PIf
Y This function is used to retrieve MAU object status with 2
admitted values depending of Activate state of the MAU:
Operational(3): the MAU is electrically switched on.
Shutdown(5): the MAU is electrically switched off.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauStatus
Y This function is used to explicitly activate (ifMauStatus =
Operational) or deactivate (ifMauStatus = Shutdown)
the MAU.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-SET on ifMauStatus
Y This function is used to retrieve the MAU Operational State.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauMediaAvailable
Note F-7.3: Allowed values:

available (3)
notAvailable (4)
1AA 00014 0004 (9711) A4
ED
NTIAL
WTD
01
It.01
S
N
M
PIf
3DB161760000DSZZA
69/202
F-7.10 Condition
Electrical GE MAU
Default Type
F-7.11 Change
Electrical GE MAU
Default Type

GE MAU Capability
Data
ED
WTD
01
It.01
This function is used to request Electrical GE MAU jack type.

GE MAU always relies on rj45 (2) jack types
Scope
MAU-MIB: ifJackTable
Service Used
SNMP-GET on ifJackType
This function is used to operate on Electrical GE MAU
default type with below admitted values:
dot3MauType10BaseTHD: 10BaseT half-duplex
dot3MauType100BaseTxHD: 100BaseTx half-duplex
dot3MauType100BaseTxFD: 100BaseTx full-duplex
[default value]
This operation can be performed only when the
ifAdminStatus/ifMauStatus of supporting Ethernet interface is
down.
Scope
MAU-MIB: ifMauTable
Service Used
This function is used to change Electrical GE MAU default
type with below admitted values:
dot3MauType10BaseTHD: 10BaseT half-duplex
dot3MauType100BaseTxHD: 100BaseTx half-duplex
dot3MauType100BaseTxFD: 100BaseT full-duplex
[default value]
Scope
MAU-MIB: ifMauTable
Service Used
The retrieved information is:
enabled Auto-negotiation Status
the available MAU types
the actual default MAU type (IfMauDefaultType)
The available MAU types (see ifMauTypeListBits [4]) is
defined by NE as:
b10baseTHD(10) = 1 10BASE-T half duplex mode
b10baseTFD(11) = 1 10BASE-T full duplex mode
b100baseTXHD(15) = 1 100BASE-TX half duplex
mode
b100baseTXFD(16) = 1 100BASE-TX full duplex mode
Other bits = 0
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on:
ifMauAutoNegSupported
ifMauTypeListBits
3DB161760000DSZZA
70/202

1AA 00014 0004 (9711) A4

GE MAU Jack Type

ifMauDefaultType
Note F-7.5: The following values: b10baseTHD(10), b100baseTXHD(15) arent currently
included in ANNEX to Ethernet Physical Interface Management Functional Specification.
F-7.6 Change Electrical
Y This function is used to configure the ASAP Pointer
associated to an Ethernet Interface.
GE MAU ASAP Pointer
Scope
Service Used
SNMP-SET on opticsIMifMauExtAsapIndex
Y This function is used to request the ASAP Pointer associated
GE MAU ASAP Pointer
to an Ethernet Interface.
Scope
Service Used
SNMP-GET on opticsIMifMauExtAsapIndex
F-7.12p Request
Y This function is used to request the operational type of the
Electrical GE MAU Type
MAU, as determined by either the result of the autonegotiation function or if the auto-negotiation is not enabled
or is not implemented for this MAU, by the value of the
object ifMauDefaultType.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on:
ifMauType
F-7.8 Report Electrical

GE MAU Alarm
S
N
M
PIf
Y
This function is used to report a cLOS alarm.

Scope
MAU-MIB: ifMauTable
Service Used
SNMP-TRAP on opticsIMAlarmLossOfSignalRaise
SNMP-TRAP on opticsIMAlarmLossOfSignalClear
F-7.9 Report Electrical
N Scope
GE URU Alarm
TSDIM-SNMPNE-MIB
Service Used
SNMP-TRAP on opticsIMAlarmUruRaise
SNMP-TRAP on opticsIMAlarmUruClear
Gigabit Ethernet Ety_T Management
1AA 00014 0004 (9711) A4
S
N
M
PIf
F-8.1 Report Electrical Y
GE
MAU
AutoNegotiation Status
ED
NTIAL
WTD
01
It.01
This function is used to request the MAU auto-negotiation
status. The retrieved informations are:
Whether or not the auto-negotiation is enabled
3DB161760000DSZZA
71/202
Note F-8.1: The following values:

b10baseT (1),
b100baseTX(4),
and the statement bFdxSPause(11) = 1 if Symmetric and Asymmetric Flow Control are
supported (0 otherwise) arent currently included in ANNEX to Ethernet Physical Interface
Management Functional Specification; bFdxAPause(9) = 1 and bFdxSPause(10) = 1 are
mutually exclusive.
F-8.2 Restart Electrical Y
After
the
restart,
the
agent
will
reset
the
GE Auto-Negotiation
ifMauAutoNegRestart to its default value: noRestart(2).
Scope
Service Used
SNMP-SET on ifMauAutoNegRestart to restart(1)
F-8.3
Condition P
This function is used to operate on Electrical GE MAU
Electrical GE MAU Autocapabilities advertised during the auto-negotiation.
ED
WTD
01
It.01
3DB161760000DSZZA
72/202

1AA 00014 0004 (9711) A4
(ifMauAutoNegAdminStatus)
The current status of the auto-negotiation process
(ifMauAutoNegConfig)
The auto-negotiation capabilities supported by the local
(ifMauAutoNegCapabilityBits)
The auto-negotiation capabilities advertised by the local
(ifMauAutoNegCapAdvertisedBits)
The auto-negotiation capabilities advertised by the
remote (ifMauAutoNegCapReceivedBits)
The available IfMauAutoNegCapabilityBits is defined by NE
as:
b10baseT (1) = 1
b10baseTFD (2) = 1
b100baseTX (4) = 1
b1000baseTFD (15) = 1
bFdxPause(8) = 1 if Flow Control is supported (0
otherwise)
bFdxAPause(9) = 1 if only Asymmetric Flow Control is
bFdxSPause(10) = 1 if Symmetric Flow Control is
bFdxBPause(11) = 1 if Asymmetric and Symmetric Flow
Control are supported (0 otherwise)
Other bits = 0
Scope
Service Used
SNMP-GET on:
ifMauAutoNegConfig
ifMauAutoNegCapAdvertisedBits
1AA 00014 0004 (9711) A4

Negotiation Advertised
Capability
The Electrical GE mode operations:

Speed Negotiation. Admitted values:
o 10BASE-T half duplex mode, b10baseT(1)
o 10BASE-T full duplex mode, b10baseTFD(2)
o 100BASE-TX half duplex mode, b100baseTX(4)
o 100BASE-TX full duplex mode, b100baseTXFD(5)
o 1000BASE-T full duplex mode,
b1000baseTFD(15) [Default Value]
Pause operation. Admitted values:
o PAUSE for full-duplex links, bFdxPause(8).
o Asymmetric PAUSE for full-duplex links,
bFdxAPause(9).
o Symmetric PAUSE for full-duplex links,
bFdxSPause(10).
o Asymmetric and Symmetric PAUSE for full-duplex
links, bFdxBPause(11).
default values:
b10baseT(1) = 0
b10baseTFD(2) = 0
b100baseTX(4) = 0
b100baseTXFD(5) = 0
b1000baseTFD(15) = 1
bFdxPause(8)
=
bFdxAPause(9)
=
bFdxSPause(10)
=
bFdxBPause(11)
=
Other bits = 0.
Checks
No bit in IfMauAutoNegCapAdvertisedBits can be set

to 1 if the corresponding bit in ifMauAutoNegCapabilityBits
is 0.

bFdxPause(8) = 0, bFdxAPause(9) = 0, bFdxSPause(10) =
0, bFdxBPause(11) = 0.
Asymmetric PAUSE towards link partner is

configured by setting: bFdxPause(8) = 1, bFdxAPause(9) =
1, bFdxSPause(10) = 0, bFdxBPause(11) = 0.
Symmetric PAUSE towards link partner is

Symmetric and Asymmetric PAUSE towards link

partner is configured by setting: bFdxPause(8) = 1,
bFdxAPause(9) = 0, bFdxSPause(10) = 0, bFdxBPause(11)
= 1.
Scope
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
73/202

Service Used
SNMP-SET on IfMauAutoNegCapAdvertisedBits
Note F-8.3: In this MF, the management of the speeds in half-duplex mode and the checks of
Pause function have been modified, related to the ANNEX to Ethernet Physical Interface
Management Functional Specification.
Only Asymmetric PAUSE is supported: the bFdxSPause(10) and bFdxBPause(11) are always set
to 0 value.
F-8.6. Change Electrical N
This function is used to change Electrical GE MAU
GE MAU Autocapabilities advertised during the auto-negotiation. The
Electrical GE mode operations:
Negotiation Advertised
Speed Negotiation. Admitted values:
Capability
o 10BASE-T full duplex mode, b10baseTFD(2)
o 100BASE-TX full duplex mode, b100baseTXFD(5)
o 1000BASE-T full duplex mode,
b1000baseTFD(15). [Default Value]
Pause operation. Admitted values:
o PAUSE for full-duplex links, bFdxPause(8).
o Asymmetric PAUSE for full-duplex links,
bFdxAPause(9).
o Symmetric PAUSE for full-duplex links,
bFdxSPause(10).
Asymmetric and Symmetric PAUSE for full-duplex
links, bFdxBPause(11).
default values:
b10baseTFD(2) = 0
b100baseTXFD(5) = 0
b1000baseTFD(15) = 1
bFdxPause(8)
=
bFdxAPause(9)
=
bFdxSPause(10)
=
bFdxBPause(11)
=
Other bits = 0.
Checks
No bit in IfMauAutoNegCapAdvertisedBits can be set

to 1 if the corresponding bit in ifMauAutoNegCapabilityBits
is 0.
The manager should set to 1 one of below 3 values:

b10baseTFD(2) or b100baseTXFD(5) or b1000baseTFD(15).
That is, only one of speed negotiation bits should be 1;

bFdxPause(8) = 0, bFdxAPause(9) = 0, bFdxSPause(10) =
0, bFdxBPause(11) = 0.
Asymmetric PAUSE towards link partner is

ED
WTD
01
It.01
3DB161760000DSZZA
74/202
1AA 00014 0004 (9711) A4


Scope
Service Used
SNMP-SET on IfMauAutoNegCapAdvertisedBits
F-8.4. Change Remote
Y
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfExtTable
Client Fail Electrical GE
MAU consequent action
Service Used
SNMP-SET on opticsIMEthConfExtRemCsfMAUAction with
below values:
disabled (0) [default value]
transmitter_shutdown (1)
F-8.5. Request Remote
Y
Scope
Client Fail Electrical GE
OPTICSIM-ETHNE-MIB : opticsIMEthConfExtTable
Service Used
MAU consequent action
SNMP-GET on opticsIMEthConfExtRemCsfMAUAction
F-8.7p. Condition
Y
This function is used to enable (ifMauAutoNegAdminStatus
Electrical GE MAU Auto= enabled) or disable (ifMauAutoNegAdminStatus =
Negotiation
disabled) the auto-negotiation. This operation can be
performed only when the ifAdminStatus of supporting
Ethernet interface is down.
Scope
Service Used
SNMP-SET on ifMauAutoNegAdminStatus
F-8.8p. Condition
P
This function is used to enable the PAUSE function when the
PAUSE function for
auto-negotiation is disabled (manual mode). If the autoElectrical GE MAU with
negotiation is not enabled (or is not implemented for this
auto-negotiation
MAU), the value of this object (opticsIMEthDefaultPause)
disabled
determines the operational type of the Flow Control. A set
operation on this object will force the Flow Control into the
specified operating mode.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-SET on opticsIMEthDefaultPause
Note F-8.8p: symmetric-PAUSE (2) value for opticsIMEthDefaultPause is not supported.
F-8.9p. Request PAUSE
Y
This function is used to request the PAUSE function status
when the auto-negotiation is disabled (manual mode).
function for Electrical
GE MAU with autoScope
negotiation disabled
Service Used
SNMP-GET on opticsIMEthDefaultPause
1AA 00014 0004 (9711) A4
6.2.2 Ethernet Port Management

Local Ethernet Port Transmission Specification Ety/Eth_A Management
Function
Creation/Deletion
ED
NTIAL
WTD
01
It.01
MP
3DB161760000DSZZA
75/202
F-1.x All the functions
MP
If
N
MP
If
F-1.6 Condition Ety/Eth_A N This function is used to configure Promiscuous mode when the
Promiscuous Mode
Ethernet interface is deactivated.
Scope
IF-MIB: ifXTable
Service Used
SNMP-SET on ifPromiscuousMode to below values:
true(1) when the station accepts all packets/frames
transmitted on the media.
false(2) if this interface only accepts packets/frames that
are addressed to this station.
F-1.7 Request Ety/Eth_A
P This function is used to read:
Data
the interface MTU;
the interface speed;
the interface mode (promiscuous/not promiscuous);
the Ethernet local MAC address. In case the local MAC
address is not available the address will have the value
00:00:00:00:00:00;
the handling (over local Ethernet port) of incoming errored
Ethernet frames;
Client Layer of an ISA NE local Ethernet Port
Scope
IF-MIB: ifTable, ifXTable, opticsIMEthConfTable
Service Used
SNMP-GET on:
ifType
ifMtu
ifPromiscuousMode
ifPhysAddress
ifConnectorPresent (set to true)
opticsIMEthFCSDiscardErroredFrames
opticsIMEthClientType
Note F-1.7: Only object opticsIMEthFCSDiscardErroredFrames is supported.
F-1.8 Condition Ety/Eth_A N This function allows to condition the handling of incoming
errored Ethernet frames over local Ethernet port complying
FCS Discard Errored
with 2 possible modes:
Frames
Monitoring and discarding handling mode of incoming
errored Ethernet frames [Default Handling Mode];
Monitoring handling mode of incoming Ethernet errored
ED
WTD
01
It.01
3DB161760000DSZZA
76/202

Function
If
N
1AA 00014 0004 (9711) A4

F-1.9 Condition Ety/Eth_A

Ethernet Port Client Type
frames.
Scope
Service Used
SNMP-SET on opticsIMEthFCSDiscardErroredFrames
This function allows to condition the Client Layer of an ISA NE
local Ethernet Port in case of promiscuous mode complying
with below possible modes:
ETS Layer mode; [Default Mode is ISA NE Product Specific]
OR
Ethernet Switching Layer.
Scope
Service Used
SNMP-SET on opticsIMEthClientType
Local Ethernet Port Transmission Specification EFC Management

MP
If
N
Remote Ethernet Port Transmission Specification GFP/Eth_A Management

Function
Creation/Deletion
Function
1AA 00014 0004 (9711) A4
F-3.5 Request Gfp/Eth_A

Ethernet Interface Status
ED
NTIAL
WTD
01
It.01
MP
If
N
MP
If
N
MP
If
N This function is used to read:
the status of an Ethernet Interface (enabled/disabled)
The operational state of an Ethernet interface (up/down)
The time at which the interface entered its current
operational state.
Scope
IF-MIB: ifTable
Service Used
SNMP-GET on:
ifAdminStatus
ifOperStatus
3DB161760000DSZZA
77/202
ED
WTD
01
It.01
3DB161760000DSZZA
78/202

1AA 00014 0004 (9711) A4
ifLastChange
F-3.6 Condition
N This function is used to configure Promiscuous mode when the
Gfp/Eth_A Promiscuous
Ethernet interface is deactivated.
Mode
Scope
IF-MIB: ifXTable
Service Used
SNMP-SET on ifPromiscuousMode
F-3.7 Request Gfp/Eth_A
P This function is used to read:
Ethernet Configuration
interface MTU;
Data
interface speed;
The interface mode (promiscuous/not promiscuous);
The Ethernet local MAC address (ifPhysAddress). In case
the local MAC address is not available the address will
have the value 00:00:00:00:00:00;
the handling of incoming errored Ethernet frames over a
GFP-based remote Ethernet Port:
Monitoring and discarding handling mode is the unique
supported handling mode to be retrieved from ISA NE;
Client Layer of an ISA NE GFP-based remote
Ethernet Port.
Scope
IF-MIB: ifTable, ifXTable
Service Used
SNMP-GET on:
ifType
ifMtu
ifPromiscuousMode
ifPhysAddress
ifConnectorPresent (fixed to FALSE)
opticsIMEthFCSDiscardErroredFrames
opticsIMEthClientType
Note F-3.7: Only object opticsIMEthFCSDiscardErroredFrames is supported.
F-3.8 Condition
N This function allows to condition the handling of incoming
Gfp/Eth_A FCS Discard
errored Ethernet frames over a GFP-based remote Ethernet
Errored Frames
Port complying with 2 possible modes:
Monitoring and discarding handling mode of incoming
errored Ethernet frames [Default Handling Mode is ISA NE
Product Specific];
Monitoring handling mode of incoming Ethernet errored
frames.
Scope
Service Used
SNMP-SET on opticsIMEthFCSDiscardErroredFrames
F-3.9 Condition
N This function allows to condition the Client Layer of an ISA NE
GFP-based remote Ethernet Port (in promiscuous mode)
Gfp/Eth_A Ethernet Port
complying with below possible modes:
Client Type
ETS Layer mode; [Default Mode] OR

Ethernet Switching Layer.

Scope
Service Used
SNMP-SET on opticsIMEthClientType columnar object
Remote Ethernet Port Transmission Specification GFPpr/Eth_A Management
Not supported.
Remote Ethernet Port Transmission Specification LAPS/Eth_A Management
Not supported.
Ethernet MAC Termination Transmission Specification Eth_T Management
F-2.1 Condition Ethernet
LLC/MAC Framing
F-2.2 Request Ethernet

LLC/MAC Framing
MP
If
N This function is used to condition the Ethernet framing used in
transmission. The possible framing types
are:
Ethernet V2;
LLC/SNAP;
802.2/802.3.
Scope
Service Used
SNMP-SET on opticsIMEthConfEncaps
N This function is used to read the Ethernet framing used in
transmission. The possible framing types are:
Ethernet V2;
LLC/SNAP;
802.2/802.3.
Scope
Service Used
SNMP-GET on opticsIMEthConfEncaps
6.2.3 Ethernet Transport Service Management

Ethernet ETS InFlow ETC/ETS_A_Sk Management
1AA 00014 0004 (9711) A4
Function
Creation/Deletion
MP
If
F-2.1 Create Ethernet ETS N Scope:
OpticsIMETS-MIB: opticsIMETSInFlowTable,
InFlow
opticsIMETSInFlowIndexNext.
Services Used
SNMP-GET on opticsIMETSInFlowIndexNext.
SNMP-SET on:
_ opticsIMETSInFlowRowStatus to createAndWait value
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
79/202
F-2.x Create/Activate
Ethernet ETS InFlow
Index
opticsIMETSInFlowIndex set to opticsIMETSInFlowIndexNext.
Checks
IfAdminStatus of associated underlying hecks t interface
is requested to be up, and ethernet interface is
requested to be provisioned on promiscuous mode.
ifType is requested to be verified equal either to 6
(Ethernet-csmacd) or to 161 (ieee802adLag);
ED
WTD
01
It.01
3DB161760000DSZZA
80/202

1AA 00014 0004 (9711) A4
F-2.2 Delete Ethernet ETS

InFlow
_ opticsIMETSInFlowServiceType to ethernet value

_ opticsIMETSInFlowServiceID to index value of the associated
either ethernetEthernet or LAG
port
Index
opticsIMETSInFlowIndex set to opticsIMETSInFlowIndexNext.
Checks
IfAdminStatus of associated underlying ethernet interface
is requested to be up, and ethernet interface
is requested to be provisioned on promiscuous mode.
ifType is requested to be verified equal either to 6
(Ethernet-csmacd) or to 161 (ieee8023adLag);
ifPromiscuousMode is requested to be verified equal to
true value;
ifAdminStatus is requested to be verified equal to up.
Scope:
OpticsIMETS-MIB: opticsIMETSInFlowTable
Service Used
SNMP-SET on opticsIMETSInFlowRowStatus to destroy value.
Index
opticsIMETSInFlowIndex
Checks
All Classifier Criterias related to this ETS InFlow have been
already deleted.
Setting
This management function takes as effect the unbind of
opticsIMETSInFlowColorProfilePointer if
opticsIMETSInFlowColorProfilePointer is set with a non-zero
value.
Scope:
OpticsIMETS-MIB: opticsIMETSInFlowTable,
opticsIMETSInFlowIndexNext.
Services Used
SNMP-GET on opticsIMETSInFlowIndexNext.
SNMP-SET on:
_ opticsIMETSInFlowRowStatus to createAndGo value
_ opticsIMETSInFlowServiceType to ethernet value
_ opticsIMETSInFlowServiceID to index value of the associated
either Ethernet or LAG port
_ opticsIMETSInFlowClassificationMode

ifPromiscuousMode is requested to be verified equal to

true value;
ifAdminStatus is requested to be verified equal to up.
Note F-2.x: This function is used to manage InFlow for two different purposes:
QoS for User Ethernet port at NE level (just one entry for all the Ethernet ports). In this case
just the ClassificationMode object is used.
The following are not supported:
opticsIMETSInFlowServiceType to ethernet value
opticsIMETSInFlowServiceID to index value of the associated either Ethernet or LAG port.
Function
Activation/deactivation
F-2.x
Function Configuratin
F-2.x
Function Properties
F-2.x
MP
If
N Not supported
MP
If
N Not supported
MP
If
N Not supported

The general naming rules for the Ethernet objects are defined in [17].
Supported Objects
(Table/Scalar)
Table Entry
Configuration
Description
Indexes
Value
mauMod (from MAU-MIB)
1AA 00014 0004 (9711) A4
ifMauTable
ifMauStatus
ifMauType
(note 1)
ifMauMediaAvailable
ifMauDefaultType
ifMauAutoNegSupported
ifMauTypeListBits
ED
NTIAL
WTD
01
It.01
All the 1+0 ETH

All the 1+1 ETH
DATA Tx user ports 1xx01; 1

Ch#1
(xx = 33..36
for GE)
3DB161760000DSZZA
81/202
Table Entry
Configuration
ifMauAutoNegTable
All the 1+0 ETH
All the 1+1 ETH
ifMauAutoNegConfig
ifMauAutoNegCapAdvertisedBit
s
ifMauAutoNegRestart
Indexes
Value
Ch#1
(xx = 33..36
for GE)
Description
opticsIMEthNEMib
opticsIMifMauExtTable
opticsIMifMauExtAsapIndex
All the 1+0 ETH

All the 1+1 ETH
opticsIMEthConfTable
opticsIMEthDefaultPause
All the 1+0 ETH

All the 1+1 ETH
opticsIMEthConfExtTable
All the 1+0 ETH
opticsIMEthConfExtRemCsfMAU All the 1+1 ETH
Action
opticsimETSMib
opticsIMETSInFlowTable
All the 1+0 ETH
opticsIMETSInFlowServiceType
All the 1+1 ETH
opticsIMETSInFlowClassification
Mode
ED
WTD
01
User Ethernet ports

(for NE QoS)
1500
This object is supported only with Gigabit Ethernet signals.

The Pause function is not supported at radio side; the object is supported only for
It.01
3DB161760000DSZZA
82/202
1AA 00014 0004 (9711) A4
(note 1)
(note 2)
alarms.

Ch#1
(xx = 33..36
for GE)
DATA Tx user ports 1xx01
Ch#1
(xx = 33..36
for GE)
DATA Rx radio ports 29901
Ch#1
(note 2)
DATA Tx user ports 1xx01
Ch#1
(xx = 33..36
for GE)

Supported Objects
(Table/Scalar)

RADIO DOMAIN

Radio Protections
One RPS hitless protection scheme is supported in case of 1+1 configurations.
The following table defines the characteristics of the RPS protection scheme.
Parameter Type
Protection Group Type
Switching Type
Switching Condition
Priority
Operator Commands
(note 1)
Value
1+1 hitless
Single Ended
Revertive/Non Revertive
Signal Fail, HBER, EW (note 1)
Not Applicable
Lockout spare
Manual switch from main to spare and viceversa
Signal Fail and HBER switching criteria have the same priority.
If an EPS Lockout spare command is active, all RPS protection scheme functionality are disabled. In
this case the Ch#1 is the channel active both for EPS and RPS protection schemes independently to
RPS command active.
As a single, common RPS local switching function is supported, the management of the rx static delay
is performed at NE level and not for each radio channel. In case of EW switching conditions, the
switch is performed only if the two signals are aligned. The alignment condition is not necessary in
case of SF and HBER.
The delays to be inserted by a manual management of the rx static delay
(opticsIMRadioManRxStaticDelayDirectWay and opticsIMRadioManRxStaticDelayIndirectWay columnar
objects) must be included in the 0..31 range. The alignement is performed inserting a delay only in
one signal. Fot this reason, for each alignment command (F-1.74) only one delay (direct or indirect
way) different from 0 value has to be specified; the delay of the other way must be set to 0 value.
One TPS protection scheme is supported in case of 1+1 HSB configurations (except in 1+1 with EPS
MUX disabled).
The following table defines the characteristics of the TPS protection scheme.
1AA 00014 0004 (9711) A4
Parameter Type
Protection Group Type
Switching Type
Switching Condition
Operator Commands
ED
NTIAL
WTD
01
It.01
Value
1+1
Single Ended
Revertive / Non Revertive
Equipment failures Tx side
Lockout spare
Manual switch from main to spare and viceversa
3DB161760000DSZZA
83/202
Modulation
The modulation has to be considered a system parameter.
It must be configured (4 or 16 QAM) by the managing system with the same value on both the radio
channels independently from the radio configuration and the ODU type. This is true also in case of
1+1 radio mixed configurations with different ODU types.
When a managing system configures the modulation (by F-3.3), it addresses the associated request to
a specific radio channel, but the agent implicitly applies this configuration request not only to the
radio channel addressed by the request, but also to the other one.
Restrictions:
16 QAM modulation cannot be associated to 2E1 frame structure configurations for any ODU
type and to 4E1 frame structure for ODU v2 4/16 QAM.
The allowed modulations are defined by a software key (Flash Card type).

The configuration of both these protection schemes is performed by the NE in conjunction with the
equipment provisioning process (declaration of boards).
The following table shows the allowed modulation values and frame structure configuration values
supported by each ODU type.
Modulation
ODU type description

ODU v1 32Mb 4/16QAM
ODU v1 64Mb 4/16QAM
ODU v2 32Mb 4QAM
ODU v2 64Mb 4/16QAM
4QAM
16QAM
2E1, 4E1, 8E1, 16E1

2E1, 4E1, 8E1, 16E1
2E1, 4E1, 8E1, 16E1
2E1, 4E1, 8E1, 16E1
4E1, 8E1, 16E1

4E1, 8E1, 16E1, 32E1
-8E1, 16E1, 32E1
An IncompatibleModulation alarm is raised when an ODU receives a modulation value not

supported.
An IncompatibleCapacity alarm is raised when an ODU receives a frame structure configuration
value not supported.
In case the conditions for both alarm exist, then only IncompatibleModulation is raised.
Tx Mute
Tx Mute function is managed on radio link basis. Activation/deactivation requests of the Tx squelch
are addressed to a given NE (the local NE) and channel. According to the request, the command is
applied on the local or on the remote NE.
In 1+1 HSB configurations some radio transmission parameters must be configured with the same
values on both the radio channels. This assures that a transmission protection switch doesnt affect the
radio transmission.
This behaviour is obtained in the following way:
ED
WTD
01
It.01
3DB161760000DSZZA
84/202
1AA 00014 0004 (9711) A4
Radio transmission parameters in 1+1 HSB configuration

when a managing system configures one of the radio transmission parameters it addresses the
associated request to a specific radio channel
when the agent receives the request, implicitly, applies this configuration request not only to the
radio channel addressed by the request but also to the other one.
Radio transmission parameters managed in 1+1 HSB configurations according to this behaviour are
described in the following table:
Parameter
Radio Frequency
Tx Mute (Local/Remote)
SNMP Table
SNMP Object
radioTxFrequency
opticsIMRadioManLocalTxMute
opticsIMRadioManRemoteTxMute
The ATPC parameters and the transmitted power (when the ATPC is disabled) have to be managed for
single channel.
Frequency Shifter Management
The configuration of radio Tx frequency and radio Rx frequency is done by setting the radio Tx
frequency within a Tx frequency range allowed.
The NE automatically calculates the Rx frequency based on a shifter value (specific for the diplexer
installed on ODU).
Each ODU can manage only one shifter (fixed shifter) or a list of predefined shifter (flexible shifter),
but, due to the inability to read the shifter information from the diplexer Remote Inventory, the shifter
value (and the central frequency) to use in case of flexible shifter management is choosen by
managing system in a list of allowed shifter value and central frequency.
This list is known on ODU based on frequency band (read from Remote Inventory).
When the ODU is physically connected to IDU, the list can be known also on IDU and the
OpticsIMAllowedShifterEntry are created, one entry for each shifter parameter allowed related to a
radio channel on a radio direction.
Also in case of fixed shifter the list is managed (with only one entry) to allow shifter management
independent from ODU type.
The managing system chooses the shifter value to use setting the radioShifterId object on
opticsIMRadioShifterTable with the index value (allowedShifterId object index) of one entry of the
opticsIMAllowedShifterTable (F-1.141).
Instead, when the ODU is not physically connected to IDU, in case of first configuration
(commissioning phase) the managing system is allowed to provide the values for radioShifter and the
radioCentralFrequency objects without any constraint on opticsIMAllowedShifterTable.
In this case, to provide the radioShifter value, the (F-1.141) is used with the following:
radioShifterId = radioShifter + 10000.
To provide the radioCentralFrequency value, the (F-1.8) is used with the following:
radioMinRxFrequency = radioCentralFrequency.
1AA 00014 0004 (9711) A4
Based on frequency sub-band read from Remote Inventory and on Channel Spacing (configured by
managing system on radio capacity/modulation setting), the Tx frequency range is reported to allow
the radio TX frequency setting.
Rx frequency is calculated automatically by the NE using Tx frequency configured by the managing
system and the shifter value (fixed or configured by the managing system).
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
85/202
To resume: the configuration of frequency parameters of a radio channel is done by setting in a first
time the shifter value (by managing system for flexible shifter and the only value for fixed shifter) and
then the Tx frequency (and eventually the Rx frequency).
There are no default values for shifter value and Tx and Rx frequency values.
Shifter value and Tx frequency have to be explicitly configured by managing system, while Rx
frequency is automatically calculated.
Its applied a default value (7.000.000-40.000.000 KHz or maximum hardware range known by
ODU) for Tx frequency range to allow to configure in one shot all frequency parameters.
The configuration of shifter value-central frequency is allowed only on local station (during the
installaton phase), thats allowed only to managers declared as localct in the related
MgrPollingManagerType object of the polling table.

In few cases, the Rx frequency can be modified by the managing inside the Rx frequency range
associated to couple shifter value-central frequency configured.
Thats just the same of the use a new shifter value not included in the predefined list.
An IncompatibleFrequency alarm is raised in the following cases:

when it has been configured a txFrequency value not included on the allowed Tx Frequency
Range;
when it has been configured a rxFrequency value not included on the allowed Rx Frequency
Range;
when, on configuring a new shifter value, the txFrequency is no longer included on the new
allowed txFrequencyRange.
An IncompatibleShifter alarm is raised in the following cases:
when it has been configured a shifter value not supported by ODU installed (not included in
the allowed list supported by ODU).
Tx Power Management
ED
WTD
The incompatiblePTx alarm is cleared (if it is raised) on ODU in the following cases:
01
It.01
3DB161760000DSZZA
86/202
1AA 00014 0004 (9711) A4
An IncompatiblePTX alarm is raised on ODU in the following cases:

when its configured a txPower value not included on the allowed Tx Power Range. Thats
could happen:
o on configuring an txPower (SNMP-SET on radioCurrentTxPower by F-1.20
management function) not included on the allowed power range even if a Tx Power
value is forced on ODU side due to traffic impact. The IDU sends to ODU a SET-PTX
request;
o on configuring a new modulation type value (SNMP-SET on radioPDHTTPModulation
by F-3.3 management function) sent to ODU by a SET-Modulation and a SET-PTX
requests. On ODU the alarm is raised if the txPower (specified on the SET-PTX request)
is no longer included on the new allowed power range because the change of
modulation value causes a change of power range (known at ODU side) and even if a
Tx Power value is forced on ODU side due to traffic impact;

on configuring an txPower (SNMP-SET on radioCurrentTxPower by F-1.20

management function) included on the allowed Power range. The IDU sends to ODU a
SET-PTX request;
on configuring a new modulation type value (SNMP-SET on radioPDHTTPModulation
by F-3.3 management function) sent to ODU by a SET-Modulation and a SET-PTX
requests. On ODU the alarm is cleared if the txPower (specified on the SET-PTX
request) is now included on the new allowed power range because the change of
modulation value causes a change of power range (known at ODU side).

The following table lists the Radio management functions supported in this release (see [12]).
Radio Frequency
F-1.1 Request Tx Radio
Frequency
F-1.2 Condition Tx Radio

Frequency
F-1.3 Request Rx Radio

Frequency
1AA 00014 0004 (9711) A4
F-1.4 Request Tx Radio

Frequency Range
F-1.5 Condition Tx Radio

ED
NTIAL
WTD
01
It.01
MP
If
request the transmission radio frequency expressed in KHz.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
Service Used
SNMP-GET on radioTxFrequency
condition the transmission radio frequency expressed in KHz.
Scope
Service Used
SNMP-SET on radioTxFrequency
request the receive radio frequency expressed in KHz.
Scope
Service Used
SNMP-GET on radioRxFrequency
transmission radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-GET on:
radioMinTxFrequency
radioMaxTxFrequency
3DB161760000DSZZA
87/202
ED
WTD
01
It.01
3DB161760000DSZZA
88/202
1AA 00014 0004 (9711) A4
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
condition the receive radio frequency expressed in KHz.
Scope
Service Used
SNMP-SET on radioRxFrequency
F-1.7 Request Rx Radio
P This management function allows the managing system to
Frequency Range
receive radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-GET on:
radioMinRxFrequency
radioMaxRxFrequency
F-1.8 Condition Rx Radio
Frequency Range
receive radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-SET on:
radioMinRxFrequency
radioMaxRxFrequency
Note F-1.7 and F-1.8: these MFs are used only for the shifter management (in order to provide
central frequency value), with a different meaning regarding to his described goal. Furthermore,
they are partially supported, because only the radioMinRxFrequency set has to be implemented.
F-1.9 Request Return
Code on Radio Frequency
check if Set operation on radio frequency is successful. If the
setting
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

Frequency Range
1AA 00014 0004 (9711) A4

Service Used
SNMP-GET on radioReturnCodeFrequency
Tx Power and ATPC
MP
If
F-1.10 Request ATPC
Implemented Status
request if the ATPC capability is present or not.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB
Service Used
SNMP-GET on opticsIMRadioAtpcImplemented
F-1.11 Request ATPC
Activity
request the status of the ATPC activity: enabled or disabled.
Scope
Service Used
SNMP-GET on radioAtpcEnabled
F-1.12 Condition ATPC
Activity
condition the status of the ATPC activity: enabled or disabled.
ATPC can be enabled only if it is implemented in the
equipment.
Scope
Service Used
SNMP-SET on radioAtpcEnabled
F-1.13 Request ATPC Tx
Range
transmitted power used by ATPC device.
Scope
Service Used
SNMP-GET on:
radioMinAtpcTxPower
radioMaxAtpcTxPower
F-1.14 Condition ATPC Tx Y This management function allows the managing system to
Range
transmitted power used by ATPC device.
Scope
Service Used
SNMP-SET on:
radioMinAtpcTxPower
radioMaxAtpcTxPower
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
89/202
ED
WTD
01
It.01
3DB161760000DSZZA
90/202

1AA 00014 0004 (9711) A4
Note F-1.14:The ATPC working range is set within the allowed ATPC range (F-1.29).
F-1.15 Request ATPC Rx
Power Thresholds
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: Only radioAtpcLowPowerThr is supported.
F-1.16 Condition ATPC Rx Y This management function allows the managing system to set
Low Power Threshold
the 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 Y This management function allows the managing system to
Power Threshold Range
low power threshold value used by ATPC device.
Scope
Service Used
SNMP-GET on:
radioAtpcLowPowerMinThr
radioAtpcLowPowerMaxThr
F-1.18 Request Tx
Nominal Power
request the tx nominal power.
Scope
Service Used
SNMP-GET on radioTxNominalPower
F-1.19 Request Current
request the value of the transmitted power when the ATPC is
Tx Power
disabled and no manual operation on transmitted power is
active.
Scope
Service Used
SNMP-GET on radioCurrentTxPower
F-1.20 Condition Current
Y This management function allows the managing system to set
Tx Power
the value of the transmitted power to be used by the local
transmitter when the ATPC is disabled and no manual
1AA 00014 0004 (9711) A4

F-1.21 Request Tx Power

Range
F-1.22 Request Manual

Operation Status on Tx
Power
F-1.23 Initiate/Terminate
a Manual Operation on
Tx Power

Operation Tx Power
Level
F-1.25 Condition Manual

Operation Tx Power
Level
F-1.26 Request Atpc

Direction Identifier
ED
NTIAL
WTD
01
It.01
operation on transmitted power is active.

Scope
Service Used
SNMP-SET on radioCurrentTxPower
request the allowed range (minimum and maximum values) of
the transmitted power.
Scope
Service Used
SNMP-GET on:
radioMinTxPower
radioMaxTxPower
request the status (active/not active) of a manual management
of the transmitted power.
Scope
Service Used
SNMP-GET on radioManOpTxPower
initiate / terminate a manual management of the transmitted
power.
Scope
Service Used
SNMP-SET on radioManOpTxPower
request the transmitted power level when a manual
management of the transmitted power is active.
Scope
Service Used
SNMP-GET on radioManOpTxPowerLevel
This management function allows the managing system to set
the transmitted power level when a manual management of
the transmitted power is active.
Scope
Service Used
SNMP-SET on radioManOpTxPowerLevel
request the ATPC direction identifier used in the equipment
configurations in which all the radio channels transmit in the
same direction.
3DB161760000DSZZA
91/202
F-1.29 Request Allowed

ATPC Tx Range
F-1.48 Request ATPC

High Power Status
F-1.49 Condition ATPC in

High Power Mode
F-1.137 Condition ATPC

enabled with timeout
ED
WTD
01
It.01
3DB161760000DSZZA
92/202

1AA 00014 0004 (9711) A4
F-1.27 Condition Atpc

Direction Identifier
Scope
Service Used
SNMP-GET on opticsIMRadioAtpcDirectionId
condition 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
ATPC device when allowed ATPC range and allowed RTPC
range are different (see F-1.21).
Scope
Service Used
SNMP-GET on:
radioMinAllowedAtpcTxPower
radioMaxAllowedAtpcTxPower
request the status of the ATPC in high-power mode.
Scope
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-GET on:
radioATPCHighPowerMode
radioATPCHighPowerTimeout
radioATPCHighPowerTimeoutEnabled
lock the ATPC in high-power mode.
Scope
Service Used
SNMP-SET on radioATPCHighPowerMode
enable or to disable the ATPC with timeout.
Scope
Service Used
SNMP-SET on radioATPCHighPowerTimeoutEnabled

F-1.28 Report ATPC
Identifier Mismatch
Alarm
Intrusive Tx Power Control

Function
F-1.110 Request Radio
Channel Number
F-1.111 Request
Intrusive Near End Tx
Power Range
F-1.112 Request
Intrusive Far End Tx
Power Range
1AA 00014 0004 (9711) A4
MP
If
N This management function allows a managed system to report
an ATPC Identifier Mismatch alarm.
Scope
opticsIMRadioAtpcDirectionId
Service Used
SNMP-TRAP:
opticsIMAlarmAtpcIdentifierMismatchRaise
opticsIMAlarmAtpcIdentifierMismatchClear
ED
NTIAL
WTD
01
It.01
MP
If
request the number of the radio channel associated to the
information related to the management of the transmitted
power during an Intrusive BER measurement.
Scope
opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on intrusiveTPCRadioChannelNumber
request the minimum and maximum levels of the transmitted
power allowed during an Intrusive BER measurement activated
on the Far End NE.
Scope
Service Used
SNMP-GET on:
intrusiveTPCNearEndMinTxPower
intrusiveTPCNearEndMaxTxPower
request the minimum and maximum levels of the transmitted
power allowed on the corresponding Far End radio channel
during a BER measurement activated on the Near End NE.
Scope
Service Used
SNMP-GET on:
intrusiveTPCFarEndMinTxPower
intrusiveTPCFarEndMaxTxPower
3DB161760000DSZZA
93/202
F-1.114
Initiate/Terminate a
Manual Operation on
Far End Tx Power

Operation Tx Power
Level
F-1.116 Condition
Manual Operation Tx
Power Level
This management function allows the CT physically connected

to Near End NE to request the status of the control of the
transmitted power of the corresponding Far End radio channel
(TRUE if the it is controlled by the CT, FALSE otherwise).
Scope
Service Used
SNMP-GET on intrusiveTPCFarEndControlled
This management function allows the CT physically connected
to Near End NE to assume the complete control of the
transmitted power of the corresponding Far End radio
channel.
Scope
Service Used
SNMP-SET on intrusiveTPCFarEndControlled
request the transmitted power level used by the corresponding
Far End radio channel when an intrusive BER measurement is
active.
Scope
Service Used
SNMP-GET on intrusiveTPCFarEndManOpTxPowerLevel
This management function allows the managing system to set
the transmitted power level used by the corresponding Far
End radio channel when an intrusive BER measurement is
active.
Scope
Service Used
SNMP-SET on intrusiveTPCFarEndManOpTxPowerLevel


Operation Status on Far
End Tx Power
Rx Gain
MP
If
Operation Status on Rx
request the status (active/not active) of a manual management
of the gain level.
Gain
Scope
opticsIMRadioRxGainTable
Service Used
SNMP-GET on radioManOpRxGain
F-1.31 Initiate/Terminate N This management function allows the managing system to
ED
WTD
01
It.01
3DB161760000DSZZA
94/202
1AA 00014 0004 (9711) A4
1AA 00014 0004 (9711) A4

Manual Operation on Rx
Gain

Operation Rx Gain Level

Operation Rx Gain Level
F-1.34 Request Rx Gain

Range

Operation Rx Diversity
Gain Level

Operation Rx Diversity
Gain Level
ED
NTIAL
WTD
01
It.01
initiate /terminate a manual management of the gain level.

Scope
Service Used
SNMP-SET on radioManOpRxGain
request the gain level used when a manual management of
the gain level is active.
Scope
Service Used
SNMP-GET on: radioManOpRxGainLevel
condition the gain level used when a manual management of
the gain level is active.
Scope
Service Used
SNMP-SET on: radioManOpRxGainLevel
request the allowed range (minimum and maximum values) of
the gain level.
Scope
Service Used
SNMP-GET on:
radioMinRxGain
radioMaxRxGain
request the gain level related to the diversity receiver and used
when a manual management of the gain level is active.
This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-GET on radioManOpRxDivGainLevel
condition the gain level related to the diversity receiver and
used when a manual management of the gain level is active.
configuration.
Scope
Service Used
SNMP-SET on radioManOpRxDivGainLevel
3DB161760000DSZZA
95/202
ED
WTD
01
It.01
3DB161760000DSZZA
96/202

Function
Analogue SN Function Description
Measurements
MP
If
F-1.40 Request Radio
request the number of the radio channel associated to a
Channel Number
analog measure.
Scope
OPTICSIM-RADIO-TRS-SDH-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on analogueMeasuresRadioChannelNumber
F-1.41 Request Local
Analogue Measurements
request the measurements of the local transmitted and
received power levels.
Scope
Service Used
SNMP-GET on:
analogueMeasuresLocalTxPower
analogueMeasuresLocalRxMainPower
request the measurements of the remote transmitted and
received power levels.
Scope
Service Used
SNMP-GET on:
analogueMeasuresRemoteTxPower
analogueMeasuresRemoteRxMainPower
Diversity Analogue
request the measures of the local received power levels
Measurement
related to the diversity receiver.
configuration.
Scope
Service Used
SNMP-GET on analogueMeasuresLocalRxDivPower
Diversity Analogue
request the measures of the remote received power levels
Measurement
related to the diversity receiver.
configuration.
Scope
1AA 00014 0004 (9711) A4

Service Used
SNMP-GET on analogueMeasuresRemoteRxDivPower
Radio Protection Switching
F-1.50 Request RPS
Protection Group
Configuration
F-1.51 Request RPS

Automatic Restoration
Criteria
F-1.52 Condition RPS

Criteria
1AA 00014 0004 (9711) A4
F-1.53 Request RPS

Privileged Channel

Privileged Channel
ED
NTIAL
WTD
01
It.01
MP
If
request the 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:
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupRevertive
the 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
request the privileged channel. This function is applicable only
in case of 1:N protection group type.
Scope
Service Used
SNMP-GET
on
opticsIMRadioProtectionGroupPrivilegedChannel
N This management function allows a managing system to set
up the privileged channel. This function is applicable only in
case of 1:N protection group type.
Scope
3DB161760000DSZZA
97/202

Extra Traffic
F-1.57 Request RPS

Protection Unit Type
F-1.58 Request RPS

Protection Unit Priority

Protection Unit Priority
F- 1.145 Request EW
alarm Rx Power Level
ED
WTD
01
It.01
3DB161760000DSZZA
98/202

1AA 00014 0004 (9711) A4
F-1.55 Request RPS Extra

Traffic
Service Used
SNMP-SET
on
opticsIMRadioProtectionGroupPrivilegedChannel
request the 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
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
request the type of a protection unit: main (protected) or spare
(protecting).
Scope
opticsIMRadioProtectionUnitTable
Service Used
SNMP-GET on opticsIMRadioProtectionUnitType
request the priority of a protection unit. It is applicable only in
case of 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionUnitPriority
condition the priority of the protection unit. It is applicable
only in case of 1:N protection group type.
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionUnitPriority
request the absolute Received Power Level used to raise an
EW alarm.
Scope
1AA 00014 0004 (9711) A4

F- 1.146 Condition EW
F- 1.147 Request EW
Range
F- 1.150 Request RPS

Switch on EW alarm
Status
F- 1.151 Condition RPS

Switch on EW alarm
F- 1.152 Request RPS

Switch on lowBER alarm
Status
F- 1.153 Condition RPS

Switch on lowBER alarm
ED
NTIAL
WTD
01
It.01
opticsIMRxPowerLevelThresholdMngt
Service Used
SNMP-GET on opticsIMRxPowerLevelThr scalar object.
condition the absolute Received Power Level used to raise an
EW alarm.
Scope
Service Used
SNMP-SET on opticsIMRxPowerLevelThr
request the minimum and maximum values allowed for
absolute Received Power Level used to raise an EW alarm.
Scope
Service Used
SNMP-GET on following scalar object.
opticsIMRxPowerLevelMinThr
opticsIMRxPowerLevelMaxThr
request if 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
Service Used
SNMP-GET on opticsIMRadioSwitchEWEnabled scalar object.
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
Service Used
SNMP-SET on opticsIMRadioSwitchEWEnabled
request if RPS switch occurs when lowBER alarm raised. If RPS
switch doesnt occur when lowBER alarm raised, the disabled
value is returned.
Scope
Service Used
SNMP-GET on opticsIMRadioSwitchLowBEREnabled scalar
object.
condition if RPS switch has to occur when lowBER alarm raised
or not.
3DB161760000DSZZA
99/202
Operator SN
MP
If
N
Switch of a RPS Working
Channel
Switch of RPS Protection
Channel
Manual Switch to RPS
Protection Channel
ED
WTD
01
It.01
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.
the noRequest syntax to remove the lockout and allow the
switch, both addressed to a main protection unit.
Scope
opticsIMRadioProtectionUnitTable (on main protection
unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(lockout/noRequest)
inhibit/allow a protection channel (spare) to provide
protection in the 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.
the noRequest syntax to remove the lockout and allow any
Scope
opticsIMRadioProtectionUnitTable (on spare protection
unit)
Service Used
(lockout/noRequest)
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
3DB161760000DSZZA
100/202

Function
Commands
1AA 00014 0004 (9711) A4
Scope
Service Used
SNMP-SET on opticsIMRadioSwitchLowBEREnabled
1AA 00014 0004 (9711) A4

unit)
Service Used
(manualSwitch/noRequest)
Note F-1.62: LBER is not a RPS switch criteria.
F-1.63 Initiate/Terminate P This management function allows the managing system to
Manual Switch to a RPS
initiate/terminate a manual switch from a protection channel
Working Channel
This command will fail if the working channel has an
automatic switch request (SF, HBER, LBER, EW) active present.
Scope
unit)
Service Used
Note F-1.63: LBER is not a RPS switch criteria.
F-1.64 Initiate/Terminate Y This management function allows the managing system to
Forced Switch to RPS
initiate/terminate a forced switch from a working channel
(main) to a protection one (spare). If another working channel
Protection 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.
switch, the noRequest syntax to terminate the forced switch,
Scope
unit)
Service Used
(forcedSwitch/noRequest)
F-1.65 Initiate/Terminate N This management function allows the managing system to
initiate/terminate a forced switch from a protection channel
Forced Switch to a RPS
Working Channel
Scope
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
101/202
Protection SN
MP
If
F-1.66 Request RPS
Y
Protection Scheme
Operational State
F-1.67 Request RPS

Protection Status
F-1.68 Request RPS

Protection Mismatch
Status
Function Rx Static Delay SN

Configuration
MP
If
F-1.69 Invoke Automatic
Y
Rx Static Delay
Procedure
ED
WTD
01
It.01
request the operational state of a radio protection scheme.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupOperationalState
request the current state of a radio protection unit.
Scope
Service Used
SNMP-GET on:
opticsIMRadioProtectionUnitSwitchCommand
opticsIMRadioProtectionUnitSwitchCriteria
opticsIMRadioProtectionUnitSwitchStatus
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
trigger the start of an automatic static delay alignment
procedure on a protection unit (the aligning syntax must be
used). When the procedure has been completed, the agent
has to change the value back to the notAligning syntax.
Scope
opticsIMRadioRxStaticDelayTable
Service Used
SNMP-SET
on
opticsIMRadioAutoRxStaticDelayAlignment
3DB161760000DSZZA
102/202
1AA 00014 0004 (9711) A4
Function
Status


unit)
Service Used
1AA 00014 0004 (9711) A4

(aligning)
status of the automatic static delay alignment procedure on a
protection unit: aligning.
Scope
Service Used
SNMP-GET on opticsIMRadioAutoRxStaticDelayAlignment
F-1.71 Request Delays
Inserted by Automatic Rx
request the number of delays inserted by the automatic Rx
Static Delay Procedure
static delay alignment procedure on the direct and indirect
ways.
Scope
Service Used
SNMP-GET on:
opticsIMRadioAutoRxStaticDelayDirectWay
opticsIMRadioAutoRxStaticDelayIndirectWay
F-1.72 Initiate/Terminate Y This management function allows the managing system to
initiate or terminate a manual management of the Rx static
Manual Management of
Rx Static Delay
delay.
Scope
Service Used
SNMP-SET on opticsIMRadioManRxStaticDelay
F-1.73 Request Delays
Inserted by a Manual
request the number of delays inserted by a manual
Management of Rx Static
management of the Rx static delay on the direct and indirect
ways.
Delay
Scope
Service Used
SNMP-GET on:
opticsIMRadioManRxStaticDelayDirectWay
opticsIMRadioManRxStaticDelayIndirectWay
F-1.74 Condition Delays
in Manual Management
condition the number of delays inserted by a manual
of Rx Static Delay
management of the Rx static delay on the direct and indirect
ways.
Scope
Service Used
SNMP-SET on:
Note F-1.74: the opticsIMRadioManRxStaticDelayDirectWay and
opticsIMRadioManRxStaticDelayIndirectWay values must be included in the range 0..31
ED
01
It.01
F-1.70 Request
Automatic Rx Static Delay
Procedure Status
NTIAL
WTD
3DB161760000DSZZA
103/202
HSB Transmission Protection Switching

F-1.80 Request TPS
Criteria
F-1.81 Condition TPS

Criteria
F-1.82 Request TPS

Protection Unit Type

Function Rx Static Delay SN Function Description

Notification
MP
If
F-1.75 Report Alignment
Alarm
a loss of alignment alarm. It is addressed to the involved
radio channel (identified by a radio protection unit).
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmLossOfAlignmentRaise
opticsIMAlarmLossOfAlignmentClear
MP
If
Scope
opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupRevertive
the automatic restoration criteria from the spare transmission
channel to the main one when the failure clears.
Scope
Service Used
SNMP-SET on opticsIMTxProtectionGroupRevertive
request the type of a protection unit: main (protected) or spare
(protecting).
Scope
opticsIMTxProtectionUnitTable
Service Used
SNMP-GET on opticsIMTxProtectionUnitType
Operator SN Function Description

MP
If
ED
WTD
01
It.01
3DB161760000DSZZA
104/202
1AA 00014 0004 (9711) A4
Function
Commands
1AA 00014 0004 (9711) A4

Switch of TPS Protection

Channel
Manual Switch to TPS
Protection Channel
Manual Switch to TPS
Working Channel
Forced Switch to TPS
Protection Channel
ED
NTIAL
WTD
01
It.01
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.
the noRequest syntax to remove the lockout and allow any
Scope
opticsIMTxProtectionUnitTable (on spare protection
unit)
Service Used
SNMP-SET
on
opticsIMTxProtectionUnitSwitchCommand
(lockout/noRequest)
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
opticsIMTxProtectionUnitTable (on main protection
unit)
Service Used
SNMP-SET
on
initiate/terminate a manual switch from a protection channel
to a working one. 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 active present.
Scope
unit)
Service Used
SNMP-SET
on
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
3DB161760000DSZZA
105/202
Function
Status
Protection SN
MP
If
F-1.88 Request TPS
Y
Protection Scheme
Operational State
F-1.89 Request TPS

Protection Status
F-1.90 Report TPS
ED
WTD
01
It.01

request the operational state of a HSB TPS protection scheme.
Scope
Service Used
SNMP-GET on opticsIMTxProtectionGroupOperationalState
request the current state of a TPS protection unit.
Scope
Service Used
SNMP-GET on:
opticsIMTxProtectionUnitSwitchCriteria
opticsIMTxProtectionUnitSwitchStatus
This management function allows the managed system to
3DB161760000DSZZA
106/202
1AA 00014 0004 (9711) A4
Forced Switch to TPS
Working Channel
switched to the protection one.

According to the NE type, this function will fail if protection
channel has a failure condition.
switch, the noRequest syntax to terminate the forced switch,
Scope
opticsIMTxProtectionUnitTable (on main protection
unit)
Service Used
SNMP-SET
on
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
unit)
Service Used
SNMP-SET
on

Protection Switch Event
Common Loss Alarm

F-1.100 Request CLA
Activity
F-1.101 Condition CLA

Activity
1AA 00014 0004 (9711) A4
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.
Scope
Service Used
SNMP-TRAP (opticsIMProtectionSwitchReporting) on:
MP
If
N This management function allows the managing system
request the status of the CLA procedure activity: enabled
disabled.
Scope
Service Used
SNMP-GET on opticsIMRadioCLAEnabled
N This management function allows the managing system
condition the status of the CLA procedure activity: enabled
disabled.
Scope
Service Used
SNMP-SET on opticsIMRadioCLAEnabled
to
or
to
or
Function
Commands and Status
MP
If
F-1.103 Invoke CLA Reset N This management function allows the managing system to
reset a CLA active. The resetting syntax must be used. When
the reset has been completed, the agent has to change the
value back to the notResetting syntax.
Scope
Service Used
SNMP-SET on opticsIMRadioCLAReset (resetting)
F-1.105 Request CLA
request the status of the CLA procedure: active or not active.
Procedure Status
Scope
Service Used
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
107/202
F-1.104 Report CLA

Alarm
MP
If
N This management function allows a managed system to report
a CLA alarm. It is addressed to an equipment object
supporting the radio transmit function.
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmCLARaise
opticsIMAlarmCLAClear
Tx Mute
Function
Commands and Status
MP
If
Transmitter Mute Status
request the status of the local radio transmitter in terms of
mute function:
no squelch active
squelch active, required by the managing systems
squelch active, required automatically by the agent
squelch active for both the previous reasons
Scope
Service Used
SNMP-GET on the columnar objects:
opticsIMRadioAutoLocalTxMute
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
request the status of the remote radio transmitter in terms of
mute function:
no squelch active
squelch active, required by the managing systems
squelch active, required automatically by the agent
squelch active for both the previous reasons
ED
WTD
01
It.01
3DB161760000DSZZA
108/202
1AA 00014 0004 (9711) A4

SNMP-GET on opticsIMRadioCLAStatus

Scope
Service Used
opticsIMRadioAutoRemoteTxMute
Note F-1.122: Only a manual Tx mute can be monitored.
F-1.123 Condition
Y This management function allows a managing system to mute
Remote Transmitter Mute
a local radio transmitter.
Status
Scope
Service Used
SNMP-SET on opticsIMRadioManRemoteTxMute
WST&Radio Service Channels Protections Switching
Function
F-1.xxx All the functions
MP
If
N
Shifter Definition Functions

Function
F- 1.140 Request Allowed

Shifter
1AA 00014 0004 (9711) A4
F- 1.141 Condition Shifter

Definition
ED
NTIAL
WTD
01
It.01
S Function Description
N
M
PI
f
request the allowed shifter values and related central
frequency for each radio channel. These informations are
identified by a shifter identifier. The informations available
are:
lists of shifter values and associated central frequency

Scope
opticsIMAllowedShifterTable
Service Used
allowedShifterValue
allowedShifterCentralFrequency
configure the shifter value and consequently the central
frequency for a radio channel.
The shifter value and central frequency are defined setting the
shifter identifier (radioShifterId) associated to the shifter value
and central frequency required (radioShifterValue and
radioShifterCentralFrequency) As a side effect of this
operation the agent must be set the radioShifterValue and
3DB161760000DSZZA
109/202

related radioShifterCentralFrequency objects with the values

associated to this identifier. The identifier provided must be
included in the list of the shifter identifiers allowed for that
radio channel (allowedShifterId object).
Scope
Service Used
SNMP-SET on radioShifterId
Note F- 1.141: this management function is allowed only to managers declared as localct in
the related MgrPollingManagerType object of the polling table.
F- 1.142 Request Shifter
Value and Central
request the shifter value and related central frequency defined
Frequency
for a radio channel. This information is provided by means of
shifter identifier, shifter value and central frequency
Scope
Service Used
radioShifterId
radioShifterValue
radioShifterCentralFrequency
Analogue Points
Function
F-1. xxx All the functions
MP
If
N
Radio SPI Common Functions

Function
MP
If
N
Radio SPI Urban Haul Functions

Function
MP
If
N
Function
ED
WTD
MP
01
It.01
3DB161760000DSZZA
110/202
1AA 00014 0004 (9711) A4
Radio SPI Long Haul Functions

If
N
Radio Frame Complementary Overhead Functions
Function
MP
If
N
Radio SDH NE Functions

Function Synchronization SN Function Description
MP
If
N
Radio PDH Functions
1AA 00014 0004 (9711) A4
MP
If
F-3.1 Request Radio
Channel Number
request the number of the radio channel associated to the
radioPDHTTP.
Scope
OPTICSIM-RADIO-TRS-PDH-MIB:
Service Used
SNMP-GET on radioPDHTTPBidRadioChannelNumber
F-3.2 Request
Modulation Type
request the modulation type (4 or 16 QAM) supported by a
radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidModulation
F-3.3 Condition
Modulation Type
condition 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
Service Used
SNMP-SET on radioPDHTTPBidModulation
Note F-3.3: this management function is not allowed when the ODU 4QAM is provisioned.
F- 3.4 Request Equalizer N This management function allows a managing system to
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
111/202
F-3.6 Request ASAP

Pointer
F-3.7 Condition ASAP

Pointer
Function TP Status
F-3.8 Request TP
Operational State
F-3.9 Request ODU

Service Kit Status
ED
WTD
01
It.01
MP
If
request the operational state of a radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidOperationalState
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 radioPDHTTPBidOduServiceKit
3DB161760000DSZZA
112/202

F- 3.5 Condition
Equalizer Status
request the status of equalizer (inhibited or activated)

associated to radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidEqualizerStatus
inhibit or activate the equalizer associated to radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidEqualizerStatus
request the ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidAsapIndex
configure the ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidAsapIndex
1AA 00014 0004 (9711) A4
Status
1AA 00014 0004 (9711) A4

MP
If
F-3.10 Report Radio PDH Y This management function allows a managed system to report
Alarms
transmission alarm related to a radioPDHTTP.
Scope
Service Used
SNMP-TRAP:
opticsIMAlarmRxLOSRaise
opticsIMAlarmRxLOSClear
opticsIMAlarmRxDivFailRaise
opticsIMAlarmRxDivFailClear
opticsIMAlarmRxFailRaise
opticsIMAlarmRxFailClear
opticsIMAlarmDemLOSRaise
opticsIMAlarmDemLOSClear
opticsIMAlarmDemFailRaise
opticsIMAlarmDemFailClear
opticsIMAlarmModLOSRaise
opticsIMAlarmModLOSClear
opticsIMAlarmModFailRaise
opticsIMAlarmModFailClear
opticsIMAlarmTxLOSRaise
opticsIMAlarmTxLOSClear
opticsIMAlarmTxFailRaise
opticsIMAlarmTxFailClear
opticsIMAlarmAtpcLoopProblemRaise
opticsIMAlarmAtpcLoopProblemClear
opticsIMAlarmIncompatibleFrequencyRaise
opticsIMAlarmIncompatibleFrequencyClear
opticsIMAlarmIncompatiblePTXRaise
opticsIMAlarmIncompatiblePTXClear
opticsIMAlarmVcoExternalLOSRaise
opticsIMAlarmVcoExternalLOSClear
opticsIMAlarmLowBERRaise
opticsIMAlarmLowBERClear
opticsIMAlarmEarlyWarningRaise
opticsIMAlarmEarlyWarningClear
opticsIMAlarmPathDistortionRaise
opticsIMAlarmPathDistortionClear
opticsIMAlarmRadioDADERaise
opticsIMAlarmRadioDADEClear
opticsIMAlarmRingBrokeRaise
opticsIMAlarmRingBrokeClear
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
113/202
The general naming rules for the Radio objects are defined in [17].
Table Entry
Configuration
Description
Indexes
Value
opticsIMRadioTrsCommonMib
radioTxFrequency
radioRxFrequency
radioMinTxFrequency
radioMaxTxFrequency
radioMinRxFrequency
radioShifterId
radioShifterValue
radioShifterCentralFrequency
opticsIMAllowedShifterTable
allowedShifterValue
allowedShifterCentralFrequency
All the 1+0

All the 1+1
Radio port Ch#1 20101

All the 1+0
All the 1+1

All the 1+0
Radio port Ch#1 xx01

(xx=01..50
max)
(xx=01..50
max)
(xx=01..50
max)
All the 1+1
radioAtpcEnabled
radioMinAtpcTxPower
radioMaxAtpcTxPower
radioAtpcLowPowerThr
radioAtpcLowPowerMinThr
radioAtpcLowPowerMaxThr
radioTxNominalPower
radioCurrentTxPower
radioMinTxPower
radioMaxTxPower
radioMinAllowedAtpcTxPower
radioMaxAllowedAtpcTxPower
analogueMeasuresRadioChannelNumber
ED
WTD
01
It.01
All the 1+0

All the 1+1
All the 1+0

All the 1+1

3DB161760000DSZZA
114/202
1AA 00014 0004 (9711) A4
Supported Objects
(Table/Scalar/Trap)

1AA 00014 0004 (9711) A4

Supported Objects
(Table/Scalar/Trap)
analogueMeasuresLocalTxPower
analogueMeasuresLocalRxMainPower
analogueMeasuresRemoteTxPower
analogueMeasuresRemoteRxMainPower
opticsIMRadioAutoLocalTxMute
opticsIMAlarmAtpcLoopProblemRaise
opticsIMAlarmAtpcLoopProblemClear
(note 1)
(note 1)
opticsIMAlarmEarlyWarningRaise
opticsIMAlarmEarlyWarningClear
opticsIMAlarmRxDivFailRaise
(note 2)
opticsIMAlarmRxDivFailClear
(note 2)
opticsIMAlarmDemDivLOSRaise
(note 3)
opticsIMAlarmDemDivLOSClear
(note 3)
opticsIMAlarmVcoExternalLOSRaise (note 4)
opticsIMAlarmVcoExternalLOSClear (note 4)
opticsIMAlarmIncompatibleFrequencyRaise
opticsIMAlarmIncompatibleFrequencyClear
opticsIMAlarmIncompatiblePTXRaise
opticsIMAlarmIncompatiblePTXClear
opticsIMRadioTrsPdhMib
radioPDHTTPBidRadioChannelNumber
radioPDHTTPBidModulation
radioPDHTTPBidOperationalState
radioPDHTTPBidAsapIndex
opticsIMRadioSwtcMib
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless
opticsIMRadioProtectionGroupRevertive
opticsIMRadioProtectionGroupOperationalState
opticsIMRadioProtectionUnitType
opticsIMRadioProtectionUnitSwitchCommand
opticsIMRadioProtectionUnitSwitchCriteria
opticsIMRadioProtectionUnitSwitchStatus
opticsIMTxProtectionGroupRevertive
opticsIMTxProtectionGroupOperationalState
ED
NTIAL
WTD
01
It.01
Table Entry
Configuration
Indexes
Value
Description
All the 1+0

All the 1+1

All the 1+0

All the 1+1

All the 1+1
All the 1+1
Ch#1
1; 1
Ch#0
1; 0
All the 1+1 HSB
All the 1+1 HSB Ch#1
1; 1
3DB161760000DSZZA
115/202
opticsIMRadioAutoRxStaticDelayAlignment
opticsIMRadioManRxStaticDelay
Table Entry
Configuration
All the 1+1
Ch#0
Indexes
Value
1; 0
Ch#Common
1; 99
Description
(note 1)
These alarm notifications are defined in the Radio domain, but the related defects are
detected by the Main and Extension units (IDU).
(note 2)
The OIDs of these objects (1.3.6.1.4.1.637.54.1.10.1.1.5.17/18) are used for
incompatibleShifter alarm notifications.

Supported Objects
(Table/Scalar/Trap)
(note 3)
incompatibleModulation alarm notifications.
ED
WTD
01
It.01
3DB161760000DSZZA
116/202
1AA 00014 0004 (9711) A4
(note 4)
incompatibleCapacity alarm notifications.

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: ULS.
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
Then, for the current version (2.1) the value of sysDescr is the following: V0201xx (xx is the value of
the maintenance version).
During the commissioning phase, the operator must configure the opticsIMNeConfigurationTypeId
scalar objects in order to define the NE configuration. Only ETSI market is supported.
The following table provides the list of NE configurations supported in this release with the values of
the opticsIMAllowedNeConfigurationType and opticsIMAllowedNeConfigurationId objects.
OpticsIMAllowedNe
ConfigurationType
value
Main Allowed
Configuration Types
Undefined
UNDEFINED
Without P-AC- SC plug-in
With PSU4860 power supply
1+0
1+0 16E1/DS1
1+0 32E1/DS1
1+1 HSB
1+1
1+1
1+1
1+1
1+1 FD
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1
OpticsIMAllowed
Ne
ConfigurationId
value
255
1
2
With EPS MUX protection

4
5
7
8
1AA 00014 0004 (9711) A4
With P-AC- SC plug-in

1+0
ED
NTIAL
WTD
1+0 16E1/DS1
1+0 32E1/DS1
01
It.01
10
11
3DB161760000DSZZA
117/202

1+1 HSB
1+1
1+1
1+1
1+1
1+1 FD
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1
OpticsIMAllowed
Ne
ConfigurationId
value
13
14
16
17
Without P-AC-SC plug-in

1+0
1+0 16E1/DS1
1+0 32E1/DS1
49
50

OpticsIMAllowedNe
ConfigurationType
value
Main Allowed
Configuration Types

1+1 HSB
1+1
1+1
1+1
1+1
1+1 FD
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1

51
52
53
54
With P-AC-SC plug-in

1+0
1+0 16E1/DS1
1+0 32E1/DS1
55
56

1+1
1+1
1+1 FD
1+1
1+1
With P4DATASW plug-in
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1
1+0
1+0 16E1/DS1-GETH
1+1 HSB
1+1 FD
ED
WTD
1+1 HSB 16E1/DS1-GETH

1+1 FD 16E1/DS1-GETH
01
It.01

57
58
59
60
37

38
39
3DB161760000DSZZA
118/202
1AA 00014 0004 (9711) A4
1+1 HSB

OpticsIMAllowedNe
ConfigurationType
value
Main Allowed
Configuration Types
1+0
1+0 16E1/DS1-GETH
1+1 HSB
1+1 FD
1+0
1+0 16E1/DS1-GETH
1+1 HSB
1+1 FD
1+0
1+0 16E1/DS1-GETH
1+1 HSB
1+1 FD
1+1 HSB
40

41
42
67

68
69
70

71
72
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1
Without EPS MUX protection

73
74
75
76
1+1 HSB 16E1/DS1

77
1+1
1+1
1+1
1+1
1+1 FD
1AA 00014 0004 (9711) A4
OpticsIMAllowed
Ne
ConfigurationId
value

1+1 HSB
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
119/202
1+1 FD

1+1 HSB
1+1
1+1
1+1
1+1
1+1 FD
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1

81
82
83
84
HSB 16E1/DS1
HSB 32E1/DS1
FD 16E1/DS1
FD 32E1/DS1

85
86
87
88

1+1 HSB
1+1
1+1
1+1 FD
1+1
1+1
1+1 HSB
1+1 FD
1+1 HSB
1+1 FD
1+1 HSB
1+1 FD
1+1 HSB
1+1 FD
ED
WTD

01
It.01

89
90

91
92

93
94

95
96
3DB161760000DSZZA
120/202
1AA 00014 0004 (9711) A4
1+1 HSB 32E1/DS1

1+1 FD 16E1/DS1
1+1 FD 32E1/DS1
OpticsIMAllowed
Ne
ConfigurationId
value
78
79
80

OpticsIMAllowedNe
ConfigurationType
value
Main Allowed
Configuration Types

Table: Supported NE configurations and labels

N.B. When the data plug-in is present (P4DATASW), the foreseen maximum configuration is 16 E1
tributaries (the slot for the P16E1DS1 plug-in is occupied by the data plug-in).
N.B. The following OpticsIMAllowedNEConfigurationId values have been deleted because they were
referred to the PSUVAC power supply, which is not more supported:
from 19 to 36;
from 43 to 48;
and the following ones have been deleted because they were referred to the P2DATAS plug-in, which
is not supported:
3, 6, 9, 12, 15, 18;
from 61 to 66;
the deleted positions (36) have been left free to compliant the software requests;
but, the without EPS MUX protection configurations have been added, then the 1+1 configurations
are doubled and so the total configurations are 60 (even if the last configuration is numbered as 96).
The UNDEFINED configuration is the default one.
Software Management
The ULS control system is based on two control elements types:
Equipment Controller (EC)
It has in charge the control and the management of the virtual machine as a whole and also of
the IDU physical resources.
Radio ODU Controller (OC-R)
It has in charge the control and the management of the Radio ODU physical resources.
The ULS can hold two software packages (software versions). Each of them is composed by nine
software units (one for each control element type and one for each FPGA).
The association between software unit index and related label is indicated in the following table.
1AA 00014 0004 (9711) A4
opticsIMSwUnitIndex
value
1
2
3
4
5
6
7
8
9
opticsIMSwUnitLabel
string
EC
OC-R
FPGA-JGIDU (R2.0)
FPGA-JGIDU (R2.1)
FPGA-JGRPS
FPGA-GAIA
FPGA-GAIA-EXT
FPGA-MEDUSA
FPGA-DEDALO
The commitment of the activated version takes place implicitly together with the activation itself, so
that in case of restart events, the version used for rebooting is the active version. Since the stand-by
version is not automatically deleted, the system can be reverted back to the previously active version
via another switch request.
A software version mismatch alarm is detected and reported to the managing systems when the active
EC and OC versions are incompatible. In the same way, a stand-by software version mismatch alarm
is detected and reported when the stand-by EC and OC versions are incompatible.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
121/202
A firmware download on going alarm is reported to the managing systems on ODU Unit at the
beginning of the download of an OC software unit. At the end of the download the alarm is cleared.
In the same way, a firmware download on going alarm is reported on Main/Extension board at the
beginning of a download on one associated FPGA. The alarm will be cleared at the end of FPGA
download.
The number of software units for each software package involved in a download process from
managing system to EC is fixed, it is not dependent on the configuration.
Obviously the number of software unit used on EC to download each FPGA depends on the
configuration:
Up to 7, in case of 1+0 configurations (EC, OC-R, GAIA, GAIA-EXT, JGIDU (R2.0), JGIDU (R2.1),
and MEDUSA or DEDALO only in case of Ethernet configuration)
Up to 8, in case of 1+1 configurations (EC, OC-R, GAIA, GAIA-EXT, JGIDU (R2.0), JGIDU (R2.1),
JGRPS, and MEDUSA or DEDALO only in case of Ethernet configurations).

In both cases the EC downloads the correct OC software version. At the end of the download the
alarms above are cleared.
Software Keys
The limitations introduced by the Software key are coded in the sysName scalar object.
The following table provides the list of sysName values with the Configuration supported for each
value.
4E1 4QAM
4E1 4/16QAM
8E1 4QAM
8E1 4/16QAM
16E1 4QAM
16E1 4/16QAM
ED
WTD
01
It.01
Configuration Supported
Frame structure
Modulation
2E1
4E1
2E1
4E1
2E1
4E1
8E1
2E1
4E1
8E1
2E1
4E1
8E1
16E1
2E1
4E1
8E1
16E1
2E1
4E1
8E1
4QAM
4QAM
4QAM
4QAM or 16QAM
4QAM
4QAM
4QAM
4QAM
4QAM or 16QAM
4QAM or 16QAM
4QAM
4QAM
4QAM
4QAM
4QAM
4QAM or 16QAM
4QAM or 16QAM
4QAM or 16QAM
4QAM
4QAM or 16QAM
4QAM or 16QAM
3DB161760000DSZZA
122/202
1AA 00014 0004 (9711) A4
sysName
value

32E1 16QAM
16E1
32E1
4QAM or 16QAM
16QAM
N.B. Only E1 is supported.

The limitations introduced by the Software key are related only to frame structure and modulation
configuration.
There are no limits related to the NE Configuration type. Software key value and NE Configuration
type are independent.
Event Logging
The Log size is 800 records (500 for alarms, 300 for events). A wrapping mechanism is provided.
Abnormal Conditions
The triggering events for abnormal conditions are the following:
opticsIMOffNormalDescript
Event Type
ion
String (max 80 characters)
Forced switch (EPS, RPS, TPS)
Forced switch
Lockout (EPS, RPS, TPS)
Lockout
Loopbacks activation
Active
Local radio Tx mute (manual)
Local manual Tx mute
Local radio Tx mute (automatic)
Local automatic Tx mute
Remote radio Tx mute (manual)
Local manual Tx mute
(note 1)
Remote manual Tx mute
Rx
Static
Delay
manual
Rx Static Delay manual operation
operation
RDI alarm forced by manual RDI alarm forced by manual
operation for E1 framed tributary
operation (line side)
RDI alarm forced by manual RDI alarm forced by manual
operation for E1 framed tributary
operation (radio side)
1AA 00014 0004 (9711) A4
(note 1)
This event triggers an abnormal condition both on the NE where the transmitter is
squelched and on the NE that requires to the remote one to squelch the trasmitter. In the first case the
string used for the opticsIMOffNormalDescription object is Local manual Tx mute, in the second one
Remote manual Tx mute.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
123/202
Function Event Reporting SN Function Description

Management
MP
If
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
Y This function allows a managing system to initiate reporting of
Report
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
Y This function allows a managing system to allow and inhibit
the reporting of events to itself. Row status object is the one
Report
involved in this management: its value notInService means
locked, viceversa row status as unlocked means active.
Scope
ED
WTD
01
It.01
3DB161760000DSZZA
124/202

The following table lists the Support management functions supported in this release (see [8]).
1AA 00014 0004 (9711) A4
1AA 00014 0004 (9711) A4

F-5. Request Event

Report
F-6. Condition Event

Report
F-7. Report Event
ED
NTIAL
WTD
01
It.01
This function permits to lock or unlock the state of an EFD

object.
Service Used
SNMP-SET on the tsdimEFDRowStatus columnar object
inside tsdimEFDTable.
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:
tsdimEFDTrapId
tsdimEFDTrapObject
tsdimEFDOperStatus
tsdimEFDRowStatus
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
tsdimEFDTrapObject
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)
3DB161760000DSZZA
125/202
F-8. Report Alert Event
F-9. Request Alert Event

Configuration
F-10. Condition Alert

Event Configuration
ED
WTD
01
It.01
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)
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
Scope
This function permits to a managed system to send an alert
notification to the managing systems.
Service Used
SNMP-TRAP the tsdimAlertNotification events
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
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
3DB161760000DSZZA
126/202

N.B. The Event Type or Probable Cause (in case of alarm) is

defined as the SNMP identifier of the notification.
1AA 00014 0004 (9711) A4
perceivedSeverity with the value cleared in case of

clear of alarms
1AA 00014 0004 (9711) A4

Function Event Logging SN

Management
MP
If
F-11. Request Maximum Y
Notification Identifier
Value
F-12. Request Log Status
F-13. Request Log Size
F-14. Inhibit/Allow
Logging
F-15. Request Log

Records
ED
NTIAL
WTD
01
It.01

tsdimAlertNotifTimeOut
tsdimAlertNotifFreqCount
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.
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
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
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.
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
3DB161760000DSZZA
127/202
ED
WTD
01
It.01
3DB161760000DSZZA
128/202

Function Alarm Severity SN Function Description

Management
MP
If
F-17. Request Default
Y This function allows a managing system to retrieve
ASAP Severity
information about the default severity used.
Scope
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
Y This function allows a managing system to modify information
ASAP Severity
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
Y This function allows a managing system to retrieve the next
ASAP Index
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
Y This function allows a managing system to define different
Severity Profile
ASAP objects.
Scope
This function permits to create an ASAP object.
Service Used
SNMP-SET on the following tsdimAlarmSevProfileTable
columnar object:
tsdimAlarmSevProfileIndex
1AA 00014 0004 (9711) A4
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
Y This function allows a managed system to report log state
Change
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
1AA 00014 0004 (9711) A4

F-21. Delete Alarm

Severity Profile
F-22. Create Alarm

Severity
F-23. Delete Alarm

Severity
F-24. Request Alarm

Severity
F-25. Condition ASAP

User Label
F-26. Request ASAP User

Label
ED
NTIAL
WTD
01
It.01
SNMP-SET
on
tsdimAlarmSevProfileRowStatus
columnar object to createAndGo value.
This function allows a managing system to terminate different
ASAP objects.
Scope
This function permits to delete an ASAP object.
Service Used
value.
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
createAndGo value.
alarm severity objects.
Scope
This function permits to delete an alarm severity object.
Service Used
value.
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.
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
This management function permits to request the User Label
associated to an ASAP entry.
Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
3DB161760000DSZZA
129/202
Function
Abnormal SN Function Description
Condition Management - MP
If
F-78. Request Abnormal Y This function allows a managing system to request the status
Condition Status
of the NE in terms of abnormal conditions.
Scope
TSDIM-SUPPORT-MIB
Service Used
SNMP-GET on the opticsIMActiveAbnCond scalar object.
F-79. Request Abnormal Y This function allows a managing system to request the list of
Condition Affected
objects that result in an abnormal condition.
Objects
Scope
TSDIM-SUPPORT-MIB:
opticsIMAbnCondAffectedObjectsListTable
Service Used
SNMP-GET on the opticsIMAbnCondAffectedObjectInstanceId
columnar object.
F-95. Request Abnormal Y This function allows a managing system to request the
Condition Description
description of an abnormal (off normal) condition.
Scope
TSDIM-SUPPORT-MIB:
opticsIMAbnCondAffectedObjectsListTable
Service Used
SNMP-GET on the opticsIMOffNormalDescription columnar
object.
Function Backup and SN Function Description
Restore Management
MP
If
F-28. Request NE
Y This function allows a managing system to ask to a managed
system its NE software version in order to couple it with the
Software Version
backup file.
Scope
This function permits to retrieve the software version managed
ED
WTD
01
It.01
3DB161760000DSZZA
130/202

Function Alarm Summary SN Function Description

Management
MP
If
F-27. Request Active
Problems Table
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
1AA 00014 0004 (9711) A4
Service Used
SNMP-GET on tsdimAlarmSevProfileUserLabel
1AA 00014 0004 (9711) A4

F-29. Condition Backup

File Name
F-30. Request Backup

Manager Identifier
F-31. Condition Backup

Manager Identifier
F-32. Condition Restore

Software Version

File Name

Manager Identifier
F-35. Request Restore

Manager Identifier
ED
NTIAL
WTD
01
It.01
object.
Service Used
SNMP-GET on the sysDescr managed object
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
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
This function allows a managing system to define its proper
identifier value for backup 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 opticsIMBackupRequestorAddress
managed object
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
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
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
This function allows a managing system to request the
identifier value of the managing system that has activated a
3DB161760000DSZZA
131/202

State
F-38. Request Backup

State
Function
Management
ED
WTD
01
It.01
3DB161760000DSZZA
132/202
1AA 00014 0004 (9711) A4
Agent SN Function Description

MP
If
F-40. Request NE
Installation Type
system 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-36. Request Restore

State
restore operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMRestoreRequestorAddress
managed object
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
This function allows a managing system to change the inprogress 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
This function allows a manager system to retrieve the state of
the Backup operation.
Scope
This function permits to get the Backup state scalar object.
Service Used
SNMP-GET on the opticsIMBackupState managed
object
1AA 00014 0004 (9711) A4

F-41. Request Board

Position
F-42. Request InfoModel Version
F-44. Request SDH NE

Label
F-45. Condition SDH NE

Label
F-86. Request Manager

List
F-87. Condition
Manager List
F-48. Request Local

Access Control State
ED
NTIAL
WTD
01
It.01

system 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
system 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
system information about the SDH NE label configuration.
Scope
This function permits to retrieve the SDH NE label managed
object.
Service Used
SNMP-GET on the tsdimSdhNeLabel managed object
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
system 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
system the object containing the information about the
ManagerList.
Scope
This function permits to set the ManagerList managed object.
Service Used
SNMP-SET on the opticsImNEOwnsByMgr managed
object
system information about the Craft Terminal local access
control state.
Scope
This function permits to retrieve the Craft Terminal local
access control state managed object.
3DB161760000DSZZA
133/202
F-50. Request Local

Access Control Time Out
Period
F-51. Condition Local

Access Control Time Out
Period
F-58. Request NE
Software Release
F-59. Request NE
Location
F-60. Condition NE
Location
F-61. Request NE
SubRelease
ED
WTD
01
It.01
3DB161760000DSZZA
134/202

1AA 00014 0004 (9711) A4

Access Control State
Service Used
SNMP-GET on the tsdimLacState managed object
system 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
system 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
system 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
system which is its software release.
Scope
This function permits to retrieve the NE software release.
Service Used
SNMP-GET on the sysDescr managed object
system which is its location value.
Scope
This function permits to retrieve the NE location.
Service Used
SNMP-GET on the sysLocation managed object
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
system which is its subrelease value.
Scope
This function permits to retrieve the NE subrelease.
1AA 00014 0004 (9711) A4

Service Used
SNMP-GET on the sysName managed object
Note F-61: Function used to request license key information.
F-62. Request NE
Y This management function allow the managing system to
Allowed Configurations
request the configurations allowed for the supported NE.
Scope
TSDIM-SNMPNE-MIB:
opticsIMAllowedNeConfigurationTypeTable
Service Used
SNMP-GET on opticsIMAllowedNeConfigurationType
F-63. Request NE
Configuration
request the NE configuration type. This information is
provided by means of NE configuration type identifier and
associated string.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on the scalar objects:
opticsIMNeConfigurationTypeId
opticsIMNeConfigurationType
F-64. Condition NE
Configuration
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
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMNeConfigurationTypeId
F-65. Request Market
request the market (ETSI or ANSI) in which the NE is used.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMMarket
F-66. Condition Market
F-96. Request
Equipment
Name
ED
NTIAL
WTD
01
It.01

define the market (ETSI or ANSI) in which the NE is used.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMMarket
request the NE name (it specifies NE type, configuration,
frequency, modulation).
Scope
TSDIM-SNMPNE-MIB: opticsIMNeConfiguration
Service Used
3DB161760000DSZZA
135/202
ED
WTD
01
It.01
3DB161760000DSZZA
136/202
1AA 00014 0004 (9711) A4
Function
Software SN Function Description
Download Management MP
If
F-67. Condition Server
Information
configure 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
initiate a software downloading operation.
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

SNMP-GET on opticsIMNeEquipmentName
1AA 00014 0004 (9711) A4

F-69. Abort/Destroy a
Downloading Operation
F-70. Request
Downloading
Information
ActivecreateAndGo value.
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 occupied.
Scope
The managing system configures to Delete the
opticsImSwdlInitRowStatus.
Service Used
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
Destroy value.
request 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 inprogress Software Download the Result takes the
underDownloading value.
Service Used
SNMP-GET on
opticsIMSwdlPercentage,
opticsIMSwdlTotalBytes,
opticsIMSwdlCurrentSwUnitVersion,
opticsIMSwdlCurrentSwUnitLabel,
opticsImSwdlResult.
Function
Software SN Function Description
Package Management
MP
If
F-71. Activate a StandY This function allows a managing system to activate a stand-by
by Software Version
software version which is already stored 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.
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 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
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
137/202
ED
WTD
01
It.01
3DB161760000DSZZA
138/202

1AA 00014 0004 (9711) A4
object (activation or forcedActivation syntax)

Note F-71: The commitment takes place implicitly together with the activation of a software
version.
F-72. Request Software
Y This function allows a managing system to request to the
Version Activation Result
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
N This function allows a managing system to commit the current
Software Version
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)
Y This function allows a managing system to request
Package Information
information about the software package.
Scope
Service Used
opticsIMSwPackageCommand


Unit Information
F-76. NE Restart Request
F-94. Request
Equipment Software Unit
Information
opticsIMSwPackageState
opticsIMSwPackageActivationDate
opticsIMSwPackageLabel
opticsIMSwPackageVersion
opticsIMSwPackageOperationalState
This function allows a managing system to request
information about software units included in a software
package.
Scope
TSDIM-SUPPORT-MIB: opticsIMSwUnitTable
Service Used
opticsIMSwUnitLabel
opticsIMSwUnitVersion
opticsIMSwUnitSize
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)
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
1AA 00014 0004 (9711) A4
Function
Management
Time SN Function Description

MP
If
F-80. Request NE
Current Time
request 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
request the current status of the NTP (enabled/disabled).
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
139/202
F-84. Request NTP

Servers Addresses and
Reachability
F-85. Condition NTP

Servers Addresses
Function
Management
ED
WTD
01
It.01
3DB161760000DSZZA
140/202
1AA 00014 0004 (9711) A4
Filtering SN Function Description

MP
If
F-89. Condition HD
Y This management function permits to condition the HD
Retrieval Time
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
Note F-89: opticsIMFilterHDStartByOS is not supported
F-90. Create Filter
Y This management function permits to create one Filter History
History Data Entry
Data entry. The management system has to indicate in the

F-83. Condition NTP

Status
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMNTPStatus
enable/disable the NTP.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMNTPStatus
request the addresses of the NTP servers (main and spare)
and the related reachability.
Scope
TSDIM-SNMPNE-MIB
Service Used
opticsIMMainNTPServerAddress
opticsIMSpareNTPServerAddress
opticsIMNTPServersReachabilityStatus
condition the addresses of the NTP servers (main and spare).
Scope
TSDIM-SNMPNE-MIB
Service Used
opticsIMServerNTPServerAddress

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
Y This management function permits to delete one Filter History
History Data Entry
Data entry.
Scope
Service Used
SNMP-SET on opticsIMFilterHDRowStatus columnar object to
destroy value
Note: The History Data filtering functions hereafter described are applicable to all HD objects.
This note is referred to all the filtering management functions (from F-89 to F-91).
Function EPS
Management
add
on SN Function Description
MP
If
F-xx. All the functions
N

The general naming rules for the Support domain objects are defined in [17].
Supported Objects
(Table/Scalar/Trap)
Table Entry
Description
Indexes
Value
1AA 00014 0004 (9711) A4
tsdimSupportMib
tsdimEFDTable
tsdimEFDDest
tsdimEFDTrapId
tsdimEFDTrapObject
tsdimEFDPort
tsdimEFDOperStatus
tsdimEFDRowStatus
tsdimEFDManagerIndex
ED
NTIAL
WTD
01
It.01
Max 5 entries
1..N
3DB161760000DSZZA
141/202
tsdimAlarmSevTable
tsdimAlarmSevSeverity
tsdimAlarmSevRowStatus
tsdimAlarmSevSeverityNotServAff
opticsIMSwdlInitTable
opticsIMSwdlInitForcedDownload
opticsIMSwdlInitSwPkgVersion
opticsIMSwdlInitSwPkgLabel
opticsIMSwdlInitDescrName
opticsIMSwdlInitRowStatus
ED
WTD
01
It.01
Description
Max 500 entries
Max 300 entries
Indexes
Value
<time>;
<notifId>

tsdimAlarmLogTable
tsdimAlarmLogProbableCause
tsdimAlarmLogObjectClassIdentifier
tsdimAlarmLogObjectInstanceIdentifier
tsdimAlarmLogSeverity
tsdimAlarmLogSpecificProb
tsdimAlarmLogTime
tsdimEventLogTable
tsdimEventLogEventType
tsdimEventLogObjectClassIdentifier
tsdimEventLogObjectInstanceIdentifier
tsdimEventLogTime
tsdimLogTable
tsdimLogObjectClassIdentifier
tsdimLogAdminStatus
tsdimLogOperStatus
tsdimLogMaxSize
tsdimAPTTable
tsdimAPTAlarmProbableCause
tsdimAPTAlarmObjectClassIdentifier
tsdimAPTAlarmObjectInstanceIdentifier
tsdimAPTAlarmSeverity
tsdimAPTAlarmSpecificProb
tsdimAPTAlarmTime
tsdimAlarmSevProfileTable
tsdimAlarmSevProfileRowStatus
tsdimAlarmSevProfileUserLabel
Table Entry
<time>;
<notifId>
1..2
Max 100 entries
<time>;
<notifId>
ASAP#1 (predefined)
ASAP#2 (predefined)
ASAP#3 (predefined)
ASAP#4 (predefined)
Free use ASAPs
(max 3 entries)
ASAP#1 (predefined)
ASAP#2 (predefined)
ASAP#3 (predefined)
ASAP#4 (predefined)
Free use ASAPs
(max 3 entries)
1
2
3
4
5..N
1; <trapId>
2; <trapId>
3; <trapId>
4; <trapId>
5..N;
<trapId>
1
3DB161760000DSZZA
142/202
1AA 00014 0004 (9711) A4
Supported Objects
(Table/Scalar/Trap)

Supported Objects
(Table/Scalar/Trap)
opticsIMSwPackageTable
opticsIMSwPackageCommand
opticsIMSwPackageActivationResult
opticsIMSwPackageActivationDate
opticsIMSwPackageCurrentState
opticsIMSwPackageLabel
opticsIMSwPackageVersion
opticsIMSwPackageOperationalState
opticsIMSwUnitTable
opticsIMSwUnitLabel
opticsIMSwUnitVersion
opticsIMSwUnitSize
Table Entry
Description
EC software unit
OC-R software unit
FPGA-JGIDU (R2.0) software
unit
FPGA-JGIDU (R2.1) software
unit
FPGA-JGRPS software unit
FPGA-GAIA software unit
FPGA-GAIA-EXT software unit
1AA 00014 0004 (9711) A4
FPGA-MEDUSA software unit

(Fast Ethernet)
FPGA-DEDALO software unit
(Gigabit Ethernet)
opticsIMAbnCondAffectedObjectListTabl Max 50 entries
e
opticsIMAbnCondAffectedObjectInstanceId
opticsIMOffNormalDescription
ED
NTIAL
WTD
01
It.01
Indexes
Value
1..2
1; 1
2; 1
1; 2
2; 2
1; 3
2; 3
1; 4
2; 4
1; 5
2; 5
1; 6
2; 6
1; 7
2; 7
1; 8
2; 8
1; 9
2; 9
1..N
3DB161760000DSZZA
143/202
Table Entry
Indexes
Value
Description

Supported Objects
(Table/Scalar/Trap)
opticsIMEFDAllEvents
opticsIMEFDAllTraps
opticsIMEFDAllObjects
tsdimObjectCreationNotification
tsdimObjectDeletionNotification
tsdimAVCNotification
tsdimStateChangeNotification
opticsIMSwdlServerAddress
opticsIMSwdlServerPort
opticsIMSwdlServerUserId
opticsIMSwdlServerPassword
opticsIMSwdlServerRootDir
opticsIMSwdlPercentage
opticsIMSwdlTotalBytes
opticsIMSwdlCurrentSwUnitVersion
opticsIMSwdlCurrentSwUnitLabel
opticsIMSwdlResult
opticsIMNERestartRequest
opticsIMBackupFilename
opticsIMBackupRequestorAddress
opticsIMBackupState
opticsIMRestoreSWVersion
opticsIMRestoreFilename
opticsIMRestoreRequestorAddress
opticsIMRestoreState
opticsIMActiveAbnCond
system
sysDescr
sysLocation
sysName
tsdimSnmpNEMib
ED
WTD
01
It.01
Undefined configuration
Configurations
255
1..72
(note 2)
3DB161760000DSZZA
144/202
1AA 00014 0004 (9711) A4
tsdimLacTable
tsdimLacState
tsdimLacNoResponseTimeOutPeriod
opticsIMAllowedNeConfigurationTypeT
able
opticsIMAllowedNeConfigurationType
1AA 00014 0004 (9711) A4

Supported Objects
(Table/Scalar/Trap)
Table Entry
Description
Indexes
Value
tsdimSnmpAgtIpAddress
(note 1)
tsdimSnmpAgtIpMask
(note 1)
tsdimSnmpAgtUdpPort
(note 1)
tsdimNeInstallationType
tsdimSdhNeLabel
tsdimInfoModelVersionMajor
tsdimInfoModelVersionMinor
tsdimInfoModelVersionMaintenance
opticsIMNeConfigurationType
opticsIMNeConfigurationTypeId
opticsIMMarket
opticsIMExternalTime
opticsIMNTPStatus
opticsIMSpareNTPServerAddress
opticsIMNTPServersReachabilityStatus
opticsIMAlarmRemoteDefectIndicationRaise
opticsIMAlarmRemoteDefectIndicationClear
opticsIMAlarmCableLOSRaise
opticsIMAlarmCableLOSClear
opticsIMAlarmRxLOSRaise
opticsIMAlarmRxLOSClear
opticsIMAlarmRxFailRaise
opticsIMAlarmRxFailClear
opticsIMAlarmTxFailRaise
opticsIMAlarmTxFailClear
opticsIMAlarmDemLOSRaise
opticsIMAlarmDemLOSClear
opticsIMAlarmDemFailRaise
opticsIMAlarmDemFailClear
opticsIMAlarmTCARaise
opticsIMAlarmTCAClear
opticsIMAlarmUnavailableTimeRaise
opticsIMAlarmUnavailableTimeClear
opticsIMAlarmLossOfAlignmentRaise
opticsIMAlarmLossOfAlignmentClear
opticsIMAlarmPPPFailRaise
opticsIMAlarmPPPFailClear
opticsIMAlarmRemoteNEFailureRaise
opticsIMAlarmRemoteNEFailureClear
opticsIMCommonPmMib
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
145/202
Description
Indexes
Value
1..N
Entries created by the
opticsIMFilterHDBeginTimeInterval
managers (max 10 entries)
opticsIMFilterHDEndTimeInterval
opticsIMFilterHDGranularityPeriod
opticsIMFilterHDRowStatus
(note 1)
See Communication and Routing Domain for the Management Functions.
(note 2)
Indeed, the allowed configurations are 48; the missing configurations (24) are those
related to the PSUVAC power supply, which is not more supported in this release; to be compliant to
the release 2.1.1 from this point of view, it has been preferred to maintain the global number of the
configurations (72, as in release 2.1.2), managing the missing configurations.
ED
WTD
01
It.01
3DB161760000DSZZA
146/202

Table Entry
1AA 00014 0004 (9711) A4
Supported Objects
(Table/Scalar/Trap)

COMMUNICATION AND ROUTING DOMAIN

The association between Point-To-Point IP interface type and supported modes are indicated in the
following table.
Point-To-Point IP Interfaces
Type
Supported Modes
RF
Not used
V.11
DTE
Asynchronous (Codirectional)
G.703
DTE
Asynchronous (Codirectional)
E1/DS1
(note 1)
(note 1)
Mode supported only for framed E1#1 tributary.
All these entries in the opticsIMPointToPointIPTable will be created by the agent as consequence of the
equipment provisioning phase (see Equipment Domain). The managing systems can only
activate/deactivate these interfaces.
Also the entry of the opticsIMLocalEthernetTable will follow the same behaviour. The managing
systems can only activate/deactivate this interface.
The entry related to the backbone OSPF area is automatically created by the agent as consequence of
the equipment provisioning phase and cannot be deleted.
SNMP Manager management
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.
There are 2 different ways for a manager to be registered:
1AA 00014 0004 (9711) A4
Automatic creation of a row into the opticsIMMgrPollingInfoTable (F-7 function of

Communication&Routing Domain) and tsdimEFDTable (F-1 and F-2 of Support Domain)
without operator intervention.
The row into opticsIMMgrPollingInfoTable is created using the first free index in the range
1..10 specified by manager.
These rows are constantly updated (deleted/recreated using an other index) on
connection/disconnection events and are not stored in the persistent memory.
A polling mechanism is implemented both on managing system and on NE in order to
discover connection/disconnection manager-agent events.
In the creation request for opticsIMMgrPollingInfoTable the following information are provided:
o Manager IP address as known at manager side (opticsIMMgrPollingIpAddress).
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
147/202
o
o
UDP port of the local SNMP notification daemon application. For an Alcatel manager
this is the SNMP port of the specific proxi-manager (opticsIMMgrPollingUdpPort).
A timeout value to manage the polling mechanism (opticsIMMgrPollingTimeOut).
The manager type that is in registration (opticsIMMgrPollingManagerType) : eml (1)
value for NMS system, localct (4) or remotect (5) values for CT system. These values are
used to trigger the polling mechanism start.
In the creation request for tsdimEFDTable the following information are provided:
o Manager IP address as known at manager side (tsdimEFDDest) to send the
notifications.
o UDP port of the local SNMP notification daemon application to send notifications. For
an Alcatel manager this is the SNMP port of the specific proxi-manager (tsdimEFDPort).
o The
index
on
opticsIMMgrPollingInfoTableof
manager
registered
(tsdimEFDManagerIndex).
o The other informations are fixed values:
tsdimEFDTrapId = all,
tsdimEFDTrapObject = all,
tsdimEFDLowestForWardedSeverity = lowestSeverity,
tsdimEFDIndeterminate = true.

Manual creation of a row into the opticsIMMgrPollingInfoTable and tsdimEFDTable: trusted

manager.
The informations for the creation request are provided directly from operator and sent to NE
by the http interface.
In the NE, the rows are created using the first free index in the range 1..10.
The polling mechanism is not implemented and the rows are stored in the persistent memory
(at NE restart the rows are recreated from information on persistent memory and not recreated
by the manager).
NE side, the rows on opticsIMMgrPollingInfoTable and tsdimEFDTable are created using:

o Manager IP address (opticsIMMgrPollingIpAddress, tsdimEFDDest).
o UDP
port
of
the
local
SNMP
notification
daemon
application
(opticsIMMgrPollingUdpPor, tsdimEFDPort).
o The
manager
type
that
have
to
be
registered
as
persistent
(opticsIMMgrPollingManagerType) : nml (2).
Not provided by operator.
When a manager is registered as type nml, the registration information is written to
the permanent memory (flash card) so that it can be automatically restored (reregistered) after a reboot. The polling mechanism is not started.
o The timeout value (opticsIMMgrPollingTimeOut) can be set to any non zero value.
This timeout value for managers registered as type nml is ignored by the NE (no
polling mechanism).
o The
index
on
opticsIMMgrPollingInfoTable
of
manager
registered
(tsdimEFDManagerIndex).
ED
WTD
01
It.01
3DB161760000DSZZA
148/202
1AA 00014 0004 (9711) A4
The following informations are provided by manager:

o Manager IP address
o UDP port of the local SNMP notification daemon

The other informations for tsdimEFDTable are fixed values:

tsdimEFDTrapId = all,
tsdimEFDTrapObject = all,
tsdimEFDLowestForWardedSeverity = lowestSeverity,
tsdimEFDIndeterminate = true.
TMN in frame
In SRS document has been described in details the management of the TMN in frame; briefly, it
consists to insert a 64 Kb/s signal as network management signal (NMS or TMN) to transmit remotely
this type of information along the E1#1 route (only the E1#1 tributary is enabled to do this; the
limitation is due to the hardware implementation (asic PEGASO)) in one of the time slots (the operator
chooses the time slot in the range 131 (but 16 (reserved slot))).
This AWY release is based on new MIB version (4.04) to support this feature; a specific object has
been introduced.
Regarding the previous one (AWY 2.1.1), the F-1.145 and F-1.146 MFs (in the RADIO DOMAIN) are
not more supported; the new functions are labeled F-3.36p e F-3.37p introduced in SDH/PDH
TRANSMISSION DOMAIN (the new object e1pPITTPTimeSlotTMN for the new feature belongs to the
mentioned domain, but the functionality is referred to the COMMUNICATION AND ROUTING
DOMAIN).
No alarm is required.

The following table lists the Communication and Routing management functions supported in this
release (see [7]).
1AA 00014 0004 (9711) A4
Function
IP
Management
Routing SN Function Description

MP
If
F-1. Request IP Address
P This function allows a managing system to request the
Configuration
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):
tsdimSnmpAgtIpMask
tsdimSnmpAgtUdpPort
Note F-1: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
F-2. Request OSPF
Configuration
information about the OSPF protocol routing information.
Scope
This function permits to retrieve the different OSPF Area
configurations.
Service Used
SNMP-GET on the following opticsIMOspfAreaTable
columnar objects:
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
149/202
F-4. Delete IP Static

Routing Information
F-5. Request IP Static

Routing Information
F-6. Request Routing

Information
ED
WTD
01
It.01
3DB161760000DSZZA
150/202

1AA 00014 0004 (9711) A4
F-3. Create IP Static

Routing Information
opticsIMOspfAreaId
opticsIMOspfAreaIpAddress
opticsIMOspfAreaIpMask
opticsIMOspfAreaStubFlag
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
createAndGo value.
IP routing path objects.
Scope
This function permits to delete an IP routing path object.
Service Used
value.
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:
opticsIMIpStaticRowStatus
information about 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
1AA 00014 0004 (9711) A4

opticsIMIpRoutingRouteType
opticsIMIpRoutingProtocol
opticsIMIpRoutingLocalPtpInterface
F-12. Condition IP
P This function allows a managing system to condition the
Address
managed system address.
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):
tsdimSnmpAgtIpMask
tsdimSnmpAgtUdpPort
Note F-12: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
F-13. Create OSPF Area
Y 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:
createAndGo value.
F-14. Delete OSPF Area
Y 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
Y This function allows a managing system to condition
Area
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 SN Function Description
Polling Management
MP
If
F-7. Create Manager
Y This function allows a managing system to define its polling
Polling Information
information
Scope
This function permits to create an object containing the
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
151/202
F-9. Request Manager

Polling Information
F-10. Request Polled

Information
F- 48. Condition Timeout

Polling
ED
WTD
01
It.01
3DB161760000DSZZA
152/202

1AA 00014 0004 (9711) A4
F-8. Delete Manager

Polling Information
information needed to manage the manager polling

functionality.
Service Used
SNMP-SET
on
the
following
opticsIMMgrPollingInfoTable columnar object:
opticsIMMgrPollingIpAddress
opticsIMMgrPollingUdpPort
opticsIMMgrPollingTimeOut
opticsIMMgrPollingManagerType
createAndWait value.
This function allows a managing system to terminate its
polling information object.
Scope
This function permits to delete a polling information object.
Service Used
value.
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:
opticsIMMgrPollingRowStatus
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)
This function allows a managing system to change the polling
timeout value.
1AA 00014 0004 (9711) A4

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:
- opticsIMMgrPollingTimeOut
Function Local Ethernet SN Function Description

Management
MP
If
F-16. Create Local
N This function allows a managing system to create a local
Ethernet
ethernet interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on the following columnar objects:
opticsIMLocalEthernetIpAddress
opticsIMLocalEthernetIpMask
opticsIMLocalEthernetIpRoutingProtocol
opticsIMLocalEthernetOspfAreaPointer
createAndGo value.
F-17. Delete Local
N This function allows a managing system to delete a local
ethernet interface.
Ethernet
Scope
Service Used
value.
F-33. Activate Local
Y This function allows a managing system to activate a local
Ethernet
ethernet interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object to active
value.
F-34. Deactivate Local
Y This function allows a managing system to deactivate a local
Ethernet
ethernet interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object
to
nonInService value.
F-18. Request Local
Ethernet Information
information about local ethernet interfaces.
Scope
Service Used
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
153/202
ED
WTD
01
It.01
3DB161760000DSZZA
154/202

1AA 00014 0004 (9711) A4
opticsIMLocalEthernetMacAddress
Y This function allows a managing system to condition the
Ethernet Information
parameters related to local ethernet interface.
Scope
Service Used
Note F-19: Allowed values for routing protocol are: none, ospf.
Function
Point-to-Point SN Function Description
IP
Interface MP
Management
If
F-20. Create Point-ToN This function allows a managing system to create a point-toPoint IP Interface
point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
opticsIMIpPointToPointIPType
opticsIMIpPointToPointIPMode
opticsIMIpPointToPointIPRoutingProtocol
opticsIMIpPointToPointIPOspfAreaPointer
createAndGo value.
F-21. Delete Point-ToN This function allows a managing system to delete a point-toPoint IP Interface
point IP interface.
Scope
Service Used
value.
F-22. Request Point-ToY This function allows a managing system to request
Point IP Information
information about a point-to-point IP interface.
Scope
Service Used
opticsIMPointToPointIPType
opticsIMPointToPointIPMode
opticsIMPointToPointIPRoutingProtocol
opticsIMPointToPointIPOspfAreaPointer
opticsIMPointToPointIPRemoteAddress
F-23. Condition PointY This function allows a managing system to condition the
1AA 00014 0004 (9711) A4

To-Point IP Information
parameters related to a point-to-point IP interface.

Scope
Service Used
SNMP-SET
on
the
following
opticsIMIpPointToPointIPTable columnar objects:
Note F-23: opticsIMPointToPointIPMode object can assumes only the values:
RF: notUsed
V.11: DTE/Asynchronous (Codirectional)
G.703: DTE/Asynchronous (Codirectional) or E1#1 tributary.
Note F-23: Allowed values for routing protocol are: none, ospf.
F-24. Activate a PointY This function allows a managing system to activate a point-toTo-Point IP Interface
point IP interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object to active
value.
F-25. Deactivate a
Y This function allows a managing system to deactivate a pointPoint-To-Point IP
to-point IP interface.
Scope
Interface
Service Used
notInService value.
F-26. Report Point-ToY This function allows a managed system to report the alarms
Point IP Interface Alarms
related t a point-to-point IP interface.
Scope
Service Used
SNMP-TRAP on:
opticsIMAlarmLossOfSignalRaise/Clear
opticsIMAlarmPPPFailRaise/Clear
Note F-26: LOS for G.703 NMS interface (DTE and asynchronous modes only) and PPP fail
alarms.
F-27. Request Point-ToY This function allows a managing system to request the ASAP
Point IP Interface ASAP
Pointer associated a point-to-point IP interface.
Pointer
Scope
Service Used
SNMP-GET on opticsIMIpPointToPointIPAsapPointer.
F-28. Condition PointY This function allows a managing system to condition the
To-Point IP Interface
ASAP Pointer associated a point-to-point IP interface.
ASAP Pointer
Scope
Service Used
SNMP-SET on opticsIMIpPointToPointIPAsapPointer.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
155/202

Function
Management
LAPD SN Function Description

MP
If
F-xx All the functions
N
Function
IP
Management
Tunnel SN Function Description

MP
If
N
Function CLNP
Management
Tunnel SN Function Description

MP
If
N

The general naming rules for the Communication and Routing objects are defined in [17].
Supported Objects
(Table/Scalar/Trap)
Table Entry
Description
Indexes
Value
opticsIMCommRouMib
ED
WTD
01
It.01
Entries created by the managers 1..N

(max 10 entries)
Entries created as consequence

of managers actions
(max 10 entries)
1..N
3DB161760000DSZZA
156/202
1AA 00014 0004 (9711) A4
opticsIMMgrPollingInfoTable
opticsIMMgrPollingRowStatus
opticsIMInfoPolledTable
opticsIMInfoIndex
opticsIMInfoLastAlarmNotificationId
opticsIMInfoLastAlarmTime
opticsIMInfoLastEventNotificationId
opticsIMInfoLastEventTime
opticsIMInfoLastGenEventNotificationId
opticsIMInfoLastGenEventTime
1AA 00014 0004 (9711) A4

Supported Objects
(Table/Scalar/Trap)
opticsIMOspfAreaTable
opticsIMOspfAreaId
opticsIMOspfAreaRowStatus
opticsIMLocalEthernetTable
opticsIMLocalEthernetRoutingProtocol
opticsIMLocalEthernetRowStatus
opticsIMPointToPointIPTable
opticsIMPointToPointIPType
opticsIMPointToPointIPRemoteAddress
opticsIMPointToPointIPRowStatus
opticsIMPointToPointIPAsapIndex
opticsIMIpStaticRoutingInfoTable
opticsIMIpStaticRowStatus
opticsIMIpRoutingInfoTable
opticsIMIpRoutingDestIpMask
opticsIMIpRoutingDefGateway
opticsIMIpRoutingMetricValue
opticsIMIpRoutingRouteAge
opticsIMIpRoutingRouteType
opticsIMIpRoutingProtocol
opticsIMIpRoutingLocalPtpInterface
ED
NTIAL
WTD
01
It.01
Table Entry
Indexes
Value
Entries created by the managers 0 = backbone
(max 1+3 entries)
1..N
Description
RF
V.11
G.703
1
2
3
Entries created by the managers <IP address>
Entries created by the agent on

managers GET request
<IP address>
3DB161760000DSZZA
157/202

One auxiliary and one EOW interface are supported by ULS NE. The related entries will be created by
the agent during the provisioning phase (see Equipment domain).
The default value for the opticsIMAuxiliaryPITTPBidType columnar object is disabled. The supported
values for this object are the following:
v11Contradir64Kb
g703-64Kb
v11Codir64Kb
v11Asynch9600b
v11Asynch4800b
v28Asynch9600b
v28Asynch4800b

10 OVERHEAD DOMAIN

The following table lists the Overhead management functions supported in this release (see [14]).
EOW Phonic Parameters
Phonic SN Function Description
MP
If
F-1.1 Request EOW
Phone Number
request the phone number associated to an Engineering
Order Wire.
Scope
OPTICSIM-OH-MIB: opticsIMEowDTMFTTPBidTable
Service Used
SNMP-GET on: opticsIMEowDTMFTTPBidPhoneNumber
F-1.2 Condition EOW
Phone Number
condition 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/User channel 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)/User channel and the port identifier
(identified
by
opticsIMPointToPointIPId
of
opticsIMPointToPointIPTable).
ED
WTD
01
It.01
3DB161760000DSZZA
158/202
1AA 00014 0004 (9711) A4
Function EOW
Parameters

Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-SET on: opticsIMEowPartyLineEnabled
Note F-1.3: This function is supported to allow the enable/disable of the EOW party line feature
on User channel port.
F- 1.4 Request EOW
Party Line
request if the Engineering Order Wire party line feature on
NMS port is enabled or disabled.
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-GET on: opticsIMEowPartyLineEnabled
Auxiliary Interfaces
MP
If
F-1.10 Request Auxiliary Y This management function allow the managing system to
Interface Type
request the auxiliary interface type.
Scope
OPTICSIM-OH-MIB: opticsIMAuxiliaryPITTPBidTable
Service Used
SNMP-GET on: opticsIMAuxiliaryPITTPBidType
F-1.11 Condition
Auxiliary Interface Type
condition the auxiliary interface type.
Scope
Service Used
SNMP-SET on: opticsIMAuxiliaryPITTPBidType
F-1.13 Request Auxiliary Y This management function allows a managing system to
request the ASAP Pointer associated to the auxiliary interface.
ASAP Pointer
Scope
Service Used
SNMP-GET on opticsIMAuxiliaryPITTPBidAsapIndex
F-1.14 Condition
configure the ASAP Pointer associated to the auxiliary
Auxiliary ASAP Pointer
interface.
Scope
Service Used
SNMP-SET on opticsIMAuxiliaryPITTPBidAsapIndex
1AA 00014 0004 (9711) A4
Function TP Status
MP
If
F-1.15 Request Auxiliary Y This management function allows the managing system to
request the operational state of the auxiliary interface.
Operational State
Scope
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
159/202
MP
If
F- 1.12 Report Auxiliary
Physical Interface Alarms
transmission alarms related to auxiliary physical interfaces.
Scope
Service Used
SNMP-TRAP:
Note F-1.12: LOS for G.703 64kb/s.

F- 1.16 Request Auxiliary

Connection Status
Service Used
SNMP-GET on opticsIMAuxiliaryPITTPBidOperationalState
request if the auxiliary interface is involved in OH cross
connection (0 value indicates no cross connection on
auxiliary port; values different from 0 indicates that auxiliary
port is involved on cross connection).
Scope
Service Used
SNMP-GET
on:
opticsIMAuxiliaryPITTPBidCrossConnectIdentifier
Overhead Bytes
F- XX. All the functions.

Function TP Status
F- XX. All the functions.
ED
WTD
01
It.01
MP
If
N
MP
If
N
3DB161760000DSZZA
160/202
1AA 00014 0004 (9711) A4


The general naming rules for the Overhead objects are defined in [17].
Supported Objects
(Table/Scalar/Trap)
Table Entry
Configuratio
n
Description
Indexes
Value
opticsIMOverheadMib
opticsIMEowDTMFTTPBidTable
All
opticsIMEowDTMFTTPBidPhoneNumber
opticsIMAuxiliaryPITTPBidTable
All
opticsIMAuxiliaryPITTPBidType
opticsIMAuxiliaryPITTPBidAsapIndex
opticsIMAuxiliaryPITTPBidOperationalStat
e
opticsIMEowPartyLineTable
All
opticsIMEowPartyLineEnabled
EOW port
Auxiliary port
301
EOW on V.11
NMS port
1;
nms-v11;
1 (note 1)
1AA 00014 0004 (9711) A4
(note 1)
The NMS-V11 port (number 1) has to be intend as auxiliary interface; in this case, it is
referred to user channel.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
161/202

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.
Only the entries related to RF loopback are created according also to the ODU/s type discovered.
In case of ODU v2 type, the entry related to the RF loopback has not to be created.
In this way, the manager cannot activate this RF loopback on ODU v2 type.
In 1+1 configurations, each ODU supportes his own specific loopbacks according to ODU type.
In case of ODU substitution, the RF loopback entries have to be deleted/created according to the new
ODU type.
If no ODU/s are connected, all the loopback entries (also the RF) have to be created. When a ODU v2
is connected, then the RF loopback entries have to be deleted.

11 TEST DOMAIN
The loopback points supported are the following:

IDU
Near-End Tributary Loopback Line Local only for E3/DS3

This loopback can be activated on each PDH tributary (Tx side).
According to the frame structure configuration, this loopback refers to instances of the following
table: opticsIME1pPITTPTable (currently, only E1 tributaries are supported).
Far-End Tributary Loopback Internal

This loopback can be activated on each PDH tributary (Rx side) of the Far-End NE.
According to the frame structure configuration, this loopback refers to instances of the following
table: opticsIME1PathTTPTable (currently, only E1 tributaries are supported). This type of
loopback can be activated/deactivated only by a manager connected to the Far-End NE. A
manager directly connected to the NE (Near-End NE) can only read the status of this loopback.
Far-End tributary loopback cannot be activated if the remote transmitter is squelched (remote
Tx mute active).
Near-End IDU Cable Loopback Line Local only

This loopback can be activated on instances of opticsIMCoderTTPTable.
Near-End ODU Cable Loopback Line Local only

This loopback can be activated on instances of opticsIMRadioPDHTTPBidTable. In order to
distinguish this loopback point from the Internal RF one, the loopbackPointAdditionalDefinition
object has to be used.
(note 1)
Near-End RF Loopback Line Local only
This loopback can be activated on instances of opticsIMRadioPDHTTPBidTable. In order to
distinguish this loopback point from the Internal ODU Cable one, the
loopbackPointAdditionalDefinition object has to be used.
ED
WTD
01
It.01
3DB161760000DSZZA
162/202
1AA 00014 0004 (9711) A4
ODU

N.B. The loopbacks types defined as Local only can be requested only by managers declared as
local act in the related MgrPollingManagerType object of the polling table.
The modality of work of all of these types of loopbacks is Loop-And-Continue.
Not supported in case an ODU v2 (4QAM or 4/16QAM) is provisioned.
(note 1)

The following table lists the Test management functions supported in this release (see [13]).
F-1 Request Loopback
Configuration
F-2 Condition Loopback

Activation
1AA 00014 0004 (9711) A4
F-3 Request NearEnd/Far-End Loopback

Type
F-4 Request Loopback

Timer Configuration
ED
NTIAL
WTD
01
It.01
MP
If
request 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:
loopbackPointObjectInstance
loopbackDirectionality
loopbackPointAdditionalDefinition
loopbackBehaviour
loopbackActivation
activate a loopback test.
Scope
Service Used
SNMP-SET on:
loopbackActivation
request if 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:
loopbackNEType
loopbackAllowedManager
N This management function allow the managing system to
request the activation date (if loopback is yet activated) and
the time during the loopback stays active.
Scope
3DB161760000DSZZA
163/202

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

F-5 Condition Loopback

Timeout
Service Used
SNMP-GET on:
SNMP-GET on:
loopbackActivationDate
loopbackTimeoutPeriod
This management function allow the managing system to
configure the timer for loopback activation.
Scope
Service Used
SNMP-SET on loopbackTimeoutPeriod
opticsIMTestMib
opticsIMLoopbackTable
loopbackPointObjectInstance
loopbackDirectionality
loopbackPointAdditionalDefinition
loopbackBehaviour
loopbackActivation
opticsIMLoopbackExtTable
loopbackNEType
loopbackAllowedManager
The general naming rules of the Test objects are defined in [17]. The following tables provides the list
of loopback points, with the associated characteristics, supported in the current release.
1+0 Configurations
ED
WTD
01
It.01
TP
Index
1xx01
(note 1)
1yy01
(note 2)
20101
2xx01
(note 1)
2yy01
(note 2)
20101
NE
Type
Additional
Def.
nearEnd <trib>
Port#xx
<trib>
Port#yy
nearEnd IDU Cable
farEnd
<trib>
Port#xx
<trib>
Port#yy
nearEnd ODU Cable
Directionali
ty
externalLine
externalLine
externalLine
internal
internal
externalLine
3DB161760000DSZZA
164/202
1AA 00014 0004 (9711) A4
Loopbac
Object Instance
k
TP
Table
Table
Indexes
1; 1..16 opticsIME1pPITTPTable
(note 6)
1; 36..51 opticsIME1pPITTPTable
(note 6)
1; 17
1; 18..33 opticsIME1PathTTPTable
(note 6)
1; 52..67 opticsIME1PathTTPTable
(note 6)
1; 34

1; 35
(note 5)
1;
101..132 (note 6)
(note 4)
RF
2zz01
nearEnd <trib>
(note 3)
Port#zz
(note 1)
xx= 01..16
(note 2)
yy= 17..32
(note 3)
zz= 01..32
(note 4)
This loopback cannot be activated/deactivated by the manager.
(note 5)
Not supported when the ODU v2 is provisioned.
externalLine
internal
(note 6)
This TPTable with this TP Index is valid also in 1+1 without EPS MUX protection
configuration.
1+1 Configurations
1AA 00014 0004 (9711) A4
Loopback
Table
Indexes
Common;
1..16
Common;
36..51
Common;
18..33
Common;
52..67
Common;
101..132
(note 4)
1; 17
1; 34
1; 35
(note 5)
0; 17
0; 34
0; 35
Object Instance
TP
Table
NE
Additional
TP
Type
Def.
Index
nearEnd <trib>
1xx99
(note 1)
Port#xx
1yy99
<trib>
(note 2)
Port#yy
2xx99
farEnd
<trib>
(note 1)
Port#xx
2yy99
<trib>
(note 2)
Port#yy
2zz99
nearEnd <trib>
(note 3)
Port#zz
internal
internal
internal
nearEnd IDU Cable

nearEnd ODU Cable
RF
externalLine
externalLine
externalLine
20100
20100
nearEnd IDU Cable

nearEnd ODU Cable
RF
externalLine
externalLine
externalLine
(note 2)
yy= 17..32
(note 3)
zz= 01..32
(note 4)
This loopback cannot be activated/deactivated by the manager.
WTD
externalLine
20101
20101
xx= 01..16
ED
externalLine
(note 1)
NTIAL
Directionali
ty
01
It.01
3DB161760000DSZZA
165/202
ED
WTD
01
It.01
3DB161760000DSZZA
166/202
1AA 00014 0004 (9711) A4

(note 5)
Not supported when the ODU v2 is provisioned.

12 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 with hitless configurations (in all
the other configurations hop and link sections provide the same quality), the related monitoring point
follows the position of the EPS Rx switch.
In 1+1 with hitless configuration if the Extension unit is missing or switched off, and also in case the
EPS lockout is active, then the radio link section and the hop section of the main signal provide the
same quality (in this case the EPS switch is active on the main channel due to the missing of spare
channel and the primitives to use for performance monitoring are taken from Pegaso2 ASIC (when the
working mode is R2.0) or JGIDU FPGA (when the working mode is R2.1) on Main unit).
Both these types of PM support the same counters:
Errored Seconds
Severly Errored Seconds
Background Block Error
Unavailable Seconds
The primitive used in ULS NE for the hop section quality monitoring is the Reed-Solomon (RS) decoder
(block size: 2040 bits). The following table provides, for each frame structure, the main features useful
to define a SES.
Gross bit rate

[MHz]
RS Blocks
number/sec.
SES Threshold
(note 1)
32E1
78,336
16E1
39,168
8E1
19,584
4E1
9,792
2E1
4,896
38400
19200
9600
4800
2400
11520
5760
2880
1440
720
(note 1) According to ITU-T G.826 a second is declared Severely Errored Second if it is a second
period with one or more than 30 % of errored blocks or at least one defect.
The link section quality monitoring is obtained using the same primitive and then the same counters of
the hop section active from RPS point of view.
The list of monitoring points is given in the following table.
PM Point
TP Table
opticsIMPdhFrameHopCurrentDataTable
1AA 00014 0004 (9711) A4
opticsIMPdhFrameLinkCurrentDataTable
TP index
20101
20100
20199
Configuration
All the configurations
All the 1+1 configurations
All the 1+1 configurations
All the entries related to the performance monitoring 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 monitoring.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
167/202

The following tables list the PM management functions supported in this release (see [11]).
SDH Performance Monitoring Measurement Collection

Function
F-x.xx All the functions
MP
If
N

The all-zeroes 15 minutes intervals are always suppressed. By convention, the value assumed by
xxxSuppressedIntervals columnar objects to indicate all-zeroes suppression is (2^32)-1. Instead, the
all-zeroes 24 hours intervals are not suppressed (xxxSuppressedIntervals = 0).
PDH Frame Performance Monitoring Measurement Collection
Current Data
=>
opticsIMPdhFrameHopCurrentDataTable
opticsIMPdhFrameLinkCurrentDataTable
History Data
=>
opticsIMPdhFrameHopHistoryDataTable
opticsIMPdhFrameLinkHistoryDataTable
Threshold Data
=>
opticsIMPdhFrameHopThresholdDataTable
opticsIMPdhFrameLinkThresholdDataTable
Function Creation of PDH SN Function Description

Frame
and
Tributary MP
Current Data
If
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 (pmPdh<Layer>CDIndex), which
indicates the granularity period of the counter (15 min or 24
h) (please refer to [14] for the corresponding values of the CD
index)
Scope
OPTICSIM-PDH-PM-MIB:
opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on the following columnar objects (optionally):
pmPdh<Layer>CDMaxSuppressedIntervals
pmPdh<Layer>CDThresholdDataInstance
ED
WTD
01
It.01
3DB161760000DSZZA
168/202
1AA 00014 0004 (9711) A4
All the functions below apply to:
1AA 00014 0004 (9711) A4

pmPdh<Layer>CDAsapIndex
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object
to createAndGo value
Function Configuration of SN Function Description
PDH Frame and tributary MP
Current Data Mode
If
F-4.3 Request Elapsed
Y This management function permits to request the elapsed time
Time
in the current interval.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDElapsedTime
Note F-4.3: Elapsed time is measured in seconds.
F-4.4 Request
Y This management function permits to request the granularity
Granularity Period
period (15 min or 24 h).
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDGranularityPeriod
F-4.5 Condition Max
N This management function permits to condition the maximum
Suppressed Interval
number of intervals which can be suppressed.
Scope
Service Used
SNMP-SET on pmPdh<Layer>CDMaxSuppressedIntervals
F-4.6 Request Max
Y This management function permits to request the Max
Suppressed Interval
Suppressed Interval.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDMaxSuppressedIntervals
F-4.8 Request Number of Y This management function permits to request the Number of
Suppressed Intervals
Suppressed Intervals.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDNumSuppressedIntervals
F-4.9 Request Suspect
Y This management function permits to request whether the
Interval Flag
current data is suspect or not.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDSuspectIntervalFlag
F-4.10 Reset Suspect
N This management function permits to reset the Suspect Interval
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
169/202
F-4.13 Reset PM Data

Collection
F-4.2 Activate CD Entry
F-4.14 Deactivate CD
Entry
ED
WTD
01
It.01
3DB161760000DSZZA
170/202

F-4.11 Request Start By

OS
Flag.
Scope
Service Used
SNMP-SET
to
default
value
on
pmPdh<Layer>CDSuspectIntervalFlag
This management function permits to identify the
Management System which started the measurement.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDStartByOS
This management function permits to reset to 0 the PM Data
Collection. The following counters can be reset:
BBE
ES
SES
UAS
Scope
Service Used
SNMP-SET to default Value on:
- pmPdh<Layer>CDSes
- pmPdh<Layer>CDUas
- pmPdh<Layer>CDBbe
- pmPdh<Layer>CDEs
This management function permits to activate one CD entry.
It can be used:
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.
Scope
Service Used
to active value
This management function permits to deactivate one CD entry
to stop the counters.
Scope
Service Used
to notInService value
1AA 00014 0004 (9711) A4
Interval Flag

F-4.16 Condition CD
Asap Pointer
F-4.17 Request CD Asap

Pointer
This management function permits to set the ASAP Pointer

related to a Threshold cross alarm of a CD entry.
Scope
Service Used
SNMP-SET on pmPdh<Layer>CDAsapIndex
This management function permits to request the ASAP Pointer
related to a Threshold cross alarm of a CD entry.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDAsapIndex
Function Request of PDH SN Function Description

Frame
and
Tributary MP
Current Data
If
F-4.12 Request PM Data
Y This management function permits to Request PM Data
Collection
Collection. The following counters can be retrieved:
BBE
ES
SES
UAS
Scope
Service Used
SNMP-GET on:
- pmPdh<Layer>CDSes
- pmPdh<Layer>CDUas
- pmPdh<Layer>CDBbe
- pmPdh<Layer>CDEs
1AA 00014 0004 (9711) A4
Function Release of PDH SN Function Description

Frame
and
Tributary MP
Current Data
If
F-4.15 Delete CD Entry
N This management function permits to delete one CD entry.
Scope
Service Used
to destroy value
Function Report of PDH SN Function Description
Frame and Tributary PM MP
Alarms
If
F-4.18 Report CD Alarms Y This management function permits to report TCA and UAT
alarms.
Scope
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
171/202
Function Request of PDH SN Function Description

Frame
and
Tributary MP
ED
WTD
01
It.01
3DB161760000DSZZA
172/202


PDH
Frame
and MP
Tributary History Data
If
F-5.1 Request Elapsed
Y This management function permits to request the elapsed time
Time
in the current interval.
Scope
opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDElapsedTime
F-5.2 Request
Y This management function permits to request the granularity
Granularity Period
period (15 min or 24 h).
Scope
Service Used
SNMP-GET on pmPdh<Layer>HDGranularityPeriod
F-5.4 Request Number of Y This management function permits to request the Number of
Suppressed Intervals
Suppressed Intervals.
Scope
Service Used
SNMP-GET on pmPdh<Layer>HDNumSuppressedIntervals
F-5.5 Request Suspect
Y This management function permits to request whether the
Interval Flag
History data is suspect or not.
Scope
Service Used
SNMP-GET on pmPdh<Layer>HDSuspectIntervalFlag
F-5.6 Request Start By
N This management function permits to identify the
Management System which started the measurement.
OS
Scope
Service Used
SNMP-GET on pmPdh<Layer>HDStartByOS
1AA 00014 0004 (9711) A4
Service Used
opticsIMAlarmThresholdCrossRaise
opticsIMAlarmThresholdCrossClear
opticsIMAlarmUnavailableTimeRaise
opticsIMAlarmUnavailableTimeClear

History Data
F-5.7 Request PM Data
Collection
If
Y
This management function permits to Request PM Data

Collection. The following counters can be retrieved:
BBE
ES
SES
UAS
Scope
Service Used
SNMP-GET on:
- pmPdh<Layer>HDBbe
- pmPdh<Layer>HDEs
- pmPdh<Layer>HDSes
- pmPdh<Layer>HDUas
1AA 00014 0004 (9711) A4
Function Creation of PDH SN Function Description

Frame
and
Tributary MP
Threshold Data
If
F-6.1 Create Threshold
Y This management function permits to allocate one Threshold
Data Entry
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 opticsIMPdh<Layer>ThrIndexNext).
Scope
opticsIMPdh<Layer>ThresholdDataTable
Service Used
SNMP-GET on opticsIMPdh<Layer>ThrIndexNext
SNMP-SET on pmPdh<Layer>RowStatus columnar object to
createAndGo value
PDH
Frame
and MP
Tributary Threshold Data If
F-6.3 Condition PM
Y This management function permits to assign thresholds to PM
Thresholds Assignment
counters.
The thresholds are assigned setting, in the relative CD, the
Threshold Data Instance providing the Threshold values.
Scope
Service Used
SNMP-SET on pmPdh<Layer>CDThresholdDataInstance
F-6.4 Request PM
Y This management function permits to request the assignment
Thresholds Assignment
of thresholds to PM counters.
Scope
Service Used
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
173/202
F-6.6 Request PM
Thresholds
F-6.9 Condition
Threshold Data User
Label
F-6.10 Request
Threshold Data User
Label
ED
WTD
01
It.01
SNMP-GET on pmPdh<Layer>CDThresholdDataInstance
This management function permits to configure the thresholds
for PM counters.
The high and low thresholds for the following counters can be
set:
BBE
ES
SES
Scope
Service Used
SNMP-SET on
- pmPdh<Layer>BbeHighThr
- pmPdh<Layer>BbeLowThr
- pmPdh<Layer>EsHighThr
- pmPdh<Layer>EsLowThr
- pmPdh<Layer>SesHighThr
- pmPdh<Layer>SesLowThr
This management function permits to request the thresholds
for PM counters.
The high and low thresholds for the following counters can be
read:
BBE
ES
SES
Scope
Service Used
SNMP-SET on
- pmPdh<Layer>BbeHighThr
- pmPdh<Layer>BbeLowThr
- pmPdh<Layer>EsHighThr
- pmPdh<Layer>EsLowThr
- pmPdh<Layer>SesHighThr
- pmPdh<Layer>SesLowThr
This management function permits to configure the User Label
associated to a Threshold Data entry.
Scope
Service Used
SNMP-SET on pmPdh<Layer>UserLabel
This management function permits to request the User Label
associated to a Threshold Data entry.
Scope
3DB161760000DSZZA
174/202

1AA 00014 0004 (9711) A4
F-6.5 Condition PM
Thresholds

Service Used
SNMP-GET on pmPdh<Layer>UserLabel
Function Release of PDH SN Function Description
Frame
and
Tributary MP
Threshold Data
If
F-6.8 Delete Threshold
Y This management function permits to delete one Threshold
Data Entry
Data entry.
Scope
Service Used
SNMP-SET on pmPdh<Layer>RowStatus columnar object to
destroy value

The general naming rules for the SDH/PDH Performance Monitoring objects are defined in [17].
Supported Objects
(Table/Scalar/Trap)
Table Entry
Configuration
Description
Indexes
Value
1AA 00014 0004 (9711) A4
opticsIMPdhPmMib
opticsIMPdhFrameHopCurrentDataTa
ble
pmPdhFrameHopCDElapsedTime
pmPdhFrameHopCDGranularityPeriod
pmPdhFrameHopCDMaxSuppressedInterva
ls
pmPdhFrameHopCDNumSuppressedInterv
als
pmPdhFrameHopCDSuspectIntervalFlag
pmPdhFrameHopCDThresholdDataInstance
pmPdhFrameHopCDSes
pmPdhFrameHopCDUas
pmPdhFrameHopCDBbe
pmPdhFrameHopCDEs
pmPdhFrameHopCDRowStatus
pmPdhFrameHopCDAsapIndex
opticsIMPdhFrameHopHistoryDataTa
ble
pmPdhFrameHopHDElapsedTime
pmPdhFrameHopHDGranularityPeriod
ED
NTIAL
WTD
01
It.01
All
15 min. Ch#1
All the 1+1
15 min. Ch#0
All
24 h Ch#1
All the 1+1
24 h Ch#0
All
15 min. Ch#1
20101;
1
20100;
1
20101;
2
20100;
2
20101;
1;
period x
(x=1..9
6)
3DB161760000DSZZA
175/202
opticsIMPdhFrameHopThresholdData
Table
pmPdhFrameHopSesHighThr
pmPdhFrameHopSesLowThr
pmPdhFrameHopBbeHighThr
pmPdhFrameHopBbeLowThr
pmPdhFrameHopEsHighThr
pmPdhFrameHopEsLowThr
pmPdhFrameHopRowStatus
opticsIMPdhFrameLinkCurrentDataTa
ble
pmPdhFrameLinkCDElapsedTime
pmPdhFrameLinkCDGranularityPeriod
pmPdhFrameLinkCDMaxSuppressedInterval
s
pmPdhFrameLinkCDNumSuppressedInterva
ls
pmPdhFrameLinkCDSuspectIntervalFlag
pmPdhFrameLinkCDThresholdDataInstance
pmPdhFrameLinkCDSes
pmPdhFrameLinkCDUas
pmPdhFrameLinkCDBbe
pmPdhFrameLinkCDEs
pmPdhFrameLinkCDRowStatus
pmPdhFrameLinkCDAsapIndex
opticsIMPdhFrameLinkHistoryDataTa
ble
pmPdhFrameLinkHDElapsedTime
pmPdhFrameLinkHDGranularityPeriod
ED
WTD
01
It.01
Configuration
Description
All the 1+1
15 min. Ch#0
All
24 h Ch#1
All the 1+1
24 h Ch#0
All
15 min
All the 1+1

All the 1+1
All the 1+1
Indexes
Value
20100;
1;
period x
(x=1..9
6)
20101;
2;
period x
(x=1..8)
20100;
2;
period x
(x=1..8)
1..3
(note 1)
24 h
4..6
(note 2)
15 min.
Ch#Common
24 h Ch#Common
20199;
1
20199;
2
15 min.
Ch#Common
20199;
1;
period x
(x=1..9
6)
3DB161760000DSZZA
176/202

pmPdhFrameHopHDNumSuppressedInterv
als
pmPdhFrameHopHDSuspectIntervalFlag
pmPdhFrameHopHDSes
pmPdhFrameHopHDUas
pmPdhFrameHopHDBbe
pmPdhFrameHopHDEs
Table Entry
1AA 00014 0004 (9711) A4
Supported Objects
(Table/Scalar/Trap)
1AA 00014 0004 (9711) A4

Supported Objects
(Table/Scalar/Trap)
Table Entry
Configuration
pmPdhFrameLinkHDNumSuppressedInterva All the 1+1

ls
pmPdhFrameLinkHDSuspectIntervalFlag
pmPdhFrameLinkHDSes
pmPdhFrameLinkHDUas
pmPdhFrameLinkHDBbe
pmPdhFrameLinkHDEs
opticsIMPdhFrameLinkThresholdData All
Table
pmPdhFrameLinkSesHighThr
pmPdhFrameLinkSesLowThr
pmPdhFrameLinkBbeHighThr
pmPdhFrameLinkBbeLowThr
pmPdhFrameLinkEsHighThr
pmPdhFrameLinkEsLowThr
pmPdhFrameLinkRowStatus
Description
24 h Ch#Common
Indexes
Value
20199;
2;
period x
(x=1..8)
15 min
1..2
(note 1)
24 h
3..4
(note 3)
(note 1)
index value 1 is reserved for default entry not modifiable by managing system.
(note 2)
(note 3)
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
177/202

The following counters, only for gigabit ethernet data plug-in, which are managed in this release, are:
TRCO (incoming, Rx)
TRCF (incoming, Rx)
TRSEF (incoming, Rx)
TDF
(incoming, Rx)
TTO
(outgoing, Tx)
TTF
(outgoing, Tx)
The supported aggregate counters definitions are the following:
TRCO (Total Received Correct Octets): total number of octects of Ethernet frames received
correctly by the Virtual Ethernet Interface, including Ethernet header characters.
TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly by
the Virtual Ethernet Interface.
TRSEF (Total Received Service Errored Frames): it is the sum of three contributions:
o

13 ETHERNET PERFORMANCE MONITORING DOMAIN
dot3StatsAlignmentErrors:
a count of frames received on a particular interface that are not an integral number of
octets in length and do not pass the FCS check;
dot3StatsFCSErrors:
a count of frames received on a particular interface that are an integral number of
octets in length, but do not pass the FCS check (note 1);
dot3StatsFrameTooLongs:
number of received Ethernet frames that exceed the MTU
TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be
discarded due to buffer congestion.
TTO (Total Trasmitted Octets): total number of octets of Ethernet frames transmitted out by the
Virtual Ethernet Interface, including Ethernet header characters.
TTF (Total Trasmitted Frames): total number of Ethernet frames transmitted out by the Virtual
Ethernet interface.
ED
WTD
Only the dot3StatsFCSErrors contribution is considered for this counter.
01
It.01
3DB161760000DSZZA
178/202
1AA 00014 0004 (9711) A4
(note 1)


Ethernet Performance Monitoring Measurement Collection
Function
F-x.xx All the functions
Ethernet Counters
Function
F-1.1 Request Incoming
Aggregate
1AA 00014 0004 (9711) A4
MP
If
N Not supported
MP
If
P This management function permits to request Incoming
Aggregate maintenance counters and attributes:
TRCO
TRCF
TRCF_Unicast
TRCF_Multicast
TRCF_Broadcast
TRSEF
TDF
RetrieveTime
LastDiscontinuityTimeStamp
Scope
OPTICSIM-ETHPM-MIB: ethAggrMaintRxTable
Service Used
SNMP-GET on
- ethAggrMaintRxTRCO
- ethAggrMaintRxTRCF
- ethAggrMaintRxTRCFUnicast
- ethAggrMaintRxTRCFMulticast
- ethAggrMaintRxTRCFBroadcast
- ethAggrMaintRxTRSEF
- ethAggrMaintRxTDF
- ethAggrMaintRxRetrievingTime
- ethAggrMaintRxLastDiscontinuityTimeStamp
Note F-1.1: The TRCF_Unicast, TRCF_Multicast and TRCF_Broadcast are not supported: they are
substituted by the only TRCF counter (it is the sum of the others three).
TRSEF counter: it is the sum of three contributions, but we consider only the dot3StatsFCSErrors
contribution.
The RetrieveTime attribute is useful to count the time since the start of the counters reading
(note 1).
The LastDiscontinuityTimeStamp attribute is not supported.
F-1.3 Request Outgoing
P This management function permits to request Outgoing
Aggregate
Aggregate maintenance counters and attributes:
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
179/202

TTO
TTF
TTF_Unicast
TTF_Multicast
TTF_Broadcast
TDF
RetrieveTime
LastDiscontinuityTimeStamp
Scope
OPTICSIM-ETHPM-MIB: ethAggrMaintTxTable
Service Used
SNMP-GET on
- ethAggrMaintTxTTO
- ethAggrMaintTxTTF
- ethAggrMaintTxTTFUnicast
- ethAggrMaintTxTTFMulticast
- ethAggrMaintTxTTFBroadcast
- ethAggrMaintTxTDF
- ethAggrMaintTxRetrievingTime
- ethAggrMaintTxLastDiscontinuityTimeStamp
Note F-1.3: The TTF_Unicast, TTF_Multicast and TTF_Broadcast are not supported: they are
substituted by the only TTF counter (it is the sum of the others three).
The TDF (outgoing) counter is not supported.
The RetrieveTime attribute is useful to count the time since the start of the counters reading
(note 1).
The LastDiscontinuityTimeStamp attribute is not supported.
ED
WTD
01
It.01
3DB161760000DSZZA
180/202
1AA 00014 0004 (9711) A4
(note 1)
The two RetrieveTime attributes are referred to Tx and Rx direction, but the time
indication has to be the same: they represent, in fact, the NE time.


The general naming rules for the Ethernet Performance Monitoring objects are defined in [17].
Supported Objects
(Table/Scalar/Trap)
Table Entry
Configuration
Description
Indexes
Value
opticsIM-EthPM-MIB
ethAggrMaintRxTable
ethAggrMaintRxTRCO
ethAggrMaintRxTRCF
ethAggrMaintRxTRSEF
ethAggrMaintRxTDF
ethAggrMaintRxRetrievingTime
ethAggrMaintTxTable
ethAggrMaintTxTTO
ethAggrMaintTxTTF
ethAggrMaintTxRetrievingTime
Only
with Line port
P4DATASW
(Rx direction)
plug-in
Radio port
(Rx direction)
1xx01
(xx=33..36)
29901
Only
with Line port
P4DATASW
(Tx direction)
plug-in
Radio port
(Tx direction)
1xx01
(xx=33..36)
29901
1AA 00014 0004 (9711) A4
The naming rules are the same ones of the Ethernet Transmission Domain.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
181/202
The NE can be accessed from a managing system by the SNMP v2/v1 protocol (see 14.1 for details)
or by a telnet, ftp and pshell protocols.
The access by telnet protocol is allowed only to the user telnet with the password telnet-init.
The access by ftp protocol is allowed only to the user ftp with the password ftp.
The access by pshell protocol is allowed only to the user pshell with the password pshell-init.
No user management (creation users, deletion users, change password) is supported for telnet, ftp
and pshell protocols.
14.1 Functional Description (SNMP Interface)

14 SECURITY DOMAIN
The functions described in this section are used to configure the Security domain for SNMP v2
functionalities.
An user is identified by a username and password. Each user is associated to a predefined profile.
NE scratch behaviour
At installation time (NE scratch),
provisioning, are created.
The initial defaults accounts are:
a) Username: initial
Password: adminadmin
Profile:
administrator
b) Username: Craftperson
Password: craftcraft
Profile:
craftPerson
two predefined default user accounts, to be used for initial

(opticsIMCtUserId)
(opticsIMCtUserPassword)
(opticsIMCtUserRights)
(opticsIMCtUserId)
(opticsIMCtUserPassword)
(opticsIMCtUserRights)
The change of the password of these users is strongly suggested.

Further this initial user, the manager is allowed to create/delete users belonging to the predefined
profiles. The manager is prohibited from creating a user with username that already exists.
The manager is allowed also to change user password (own or of all user by administrator).
All the security SNMP v2 informations (username/password/profile for each user) are stored on NE
database. After the NE reset, these informations are not lost and the opticsIMCtUserEntry are
recreated as before the NE reset.
ED
WTD
01
It.01
3DB161760000DSZZA
182/202
1AA 00014 0004 (9711) A4
Reset NE behaviour

User predefined profiles

The predefined profile are:
Administrator
(both for OS interface and CT/MibBrowser interface)
He/she can do everything on the NE.
He/she can manage security features (to add/remove users or to change own password and of
all users).
Constructor
(only for OS interface)
He/she can do everything on the NE also to access to the Manager List by-passing the RM
chekcs, but he/she has disabled some administration functions: for examples he/she cant add
or remove operators, he/she cant do backup and restore.
This user profile is related only to OS system and so not stored on MIB NE.
Operator
(both for OS interface and CT/MibBrowser interface)
He/she has in charge the operation at network level, not at radio site.
He/she cant add or remove users. He/she can change only own user password.
He/she cannot manage network configuration, only for NTP Configuration, due to dangerous
isolation of NE.
He/she cant do quick configuration, backup/restore, restart NE. Also the provisioning of
equipment is not supported and the operations that require the operator presence on the radio
site.
craftPerson
(only for CT/MibBrowser interface)
He/she has in charge the installation and the maintenance at radio site.
He/she can do everything on NE system, but he/she cant add or remove users. He/she can
change only own user password.
Viewer (both for OS interface and CT/MibBrowser interface)

He/she can only explore the NE.
He/she cant add or remove users. He/she can change own user password
All user predefined profiles can be connected to NE by a F interface (local serial interface) or by a
remote interface.
Mapping user profiles on MIB values
1AA 00014 0004 (9711) A4
The predefined user profiles used on ULS 2.0 NE for SNMP v2 security functionalities are the same for
SNMP v3 security functionalities.
The opticsIMCtUserRights columnar object on opticsIMCtUserTable represents the profile for each user
on SNMP v2.
The following table provides a mapping between the predefined user profiles (as seen on Graphical
User Interface) used for ULS 2.0 NE (the same as defined on SNMP v3) and the values of the
opticsIMCtUserRights object on SNMP v2.
Predefined
profile
administrator
operator
craftPerson
viewer
ED
NTIAL
WTD
01
It.01
User opticsIMCtUserRights
value
administrator
operator
constructor
viewer
3DB161760000DSZZA
183/202
An user is identified by a username. The username identifies an user on NE without ambiguity.

The authentication of the user (username existing on NE and password check ) is performed on NE
from manager requesting the password verification (F-46). Both MIBBrowser interface and CT
interface can perform the user authentication.
The NE rejects username and passwords that do not meet specified complexity parameters.
These complexity parameters are:
Password length: the length must not be less than six (6) characters under any circumstances
and must not be less than eight (8) characters for administrator user profile. Moreover the
password length must not be more than 20 characters.
Password composition: the password must be composed of full ASCII characters set
(UPPER/lower case, numeric and special characters).
Username length: the length must not be more than 20 characters.
System Access control

User authentication
The system access control (access to whole NE) is performed in 2 ways, both supported together on
the NE:
Allowing access to NE only to those managers identified by an IP address already registered in

the opticsIMMgrPollingInfoTable (see 9.1 for details). This check is independent from user
authentication. Itis performed on NE for each manager (MIBBrowser or CT or OS interfaces).
Allowing access to NE only to those users that are identified and authenticated. This check is
performed on the managing system by a login procedure.
Resource Access control

The access control to the NE MIB (resources) from a user (authenticated by username and password) is
dependent from his user profile
the access to security tables is checked on NE agent (managed system): the management
functions F-44 (creation new user), F-45 (deletion user) and F-48 (change user password)
require that the user that executes the operation has the administrator associated profile.
For that, the access control to security tables (opticsIMCtUserTable) is ensured both from a
MIBbrowser interface and from a Craft Terminal interface
the access control to the other MIB tables for each profile is not defined on managed system
(NE agent). Its the managing system (the manager) that defines for each user profile the list of
authorized functions enabling or not the related Graphycal User Interface (menu item or
button).
The access control to NE from a Craft Terminal interface is ensured to all MIB tables on NE.
No access control instead for MIBBrowser interface (only for security tables).
ED
WTD
01
It.01
3DB161760000DSZZA
184/202
1AA 00014 0004 (9711) A4
There are 2 different behaviour for resource access control policy on SNMP v2:

NMS behaviour
There is no system access control to NE from a NMS interface. The login procedure on NMS GUI is
related only to access to NMS system.
The resource access control from a NMS interface is ensured to all MIB tables on NE
enabling/disabling related menu item on GUI .
Craft Terminal behaviour
The system access control to NE from a Craft Terminal interface is ensured by a login procedure.
The resource access control from a Craft Terminal interface is ensured to all MIB tables on NE
enabling/disabling related menu item on GUI.
MIBBrowser behaviour
From a MIBBrowser interface, the system acces control is not performed (no login procedure).
Instead, the resource access control is related only to opticsIMCtUserTable. In this way, a MIBBrowser
user cannot access (to modify or to destroy, for instance) to any user on the NE if it doesnt know an
administrator username/password, but can access without control to the other MIB tables (after
manager registration).
Access to security MIB
The opticsIMCtUserTable is not accessible directly by managing system (only to retry all username).
The opticsIMUserOperationTable is used to filter all the security related accesses to
opticsIMCtUserTable.
The SNMP SET operations on opticsIMUserOperationTable are used as a trigger of actual operation
made on opticsIMCtUserTable.
For each Management Function (F-44 to F-49) involving opticsIMUserOperationTable the side affect
(performed by agent) versus opticsIMCtUserTable and the related SNMP return codes are described in
[15].
To
avoid
concurrent
operations
on
opticsIMCtUserTable
only
one
entry
on
opticsIMUserOperationTable is supported. The agent has in charge the entry deletion on
opticsIMUserOperationTable after the end of the operation on opticsIMCtUserTable.

Function USM
Management
SN
M
PIf
N
SN
M
PIf
N
Function SNMPv2
SN
Security Management M
PIf

Function VACM
Management
1AA 00014 0004 (9711) A4
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
185/202
WTD
01
It.01
3DB161760000DSZZA
186/202
1AA 00014 0004 (9711) A4
ED

Function SNMPv2
SN
PIf
F-44 Condition New
User Creation
create a new user profile in the managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <userCreation>
_ opticsIMCorollaryUsername: <admin username>
_ opticsIMCorollaryPassword: <admin password>
_ opticsIMUserUsername: <new username>
_ opticsIMUserPassword: <password of the new user>
_ opticsIMUserRights: <user rights>
F-45 Condition User
Deletion
delete an user profile in the managed system.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <userDeletion>
_ opticsIMUserUsername: <operator username>
F-46 Condition
Password Verification
require the verification of the content of the
password field.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <checkPassword>
_ opticsIMUserPassword: <operator password>
_ opticsIMCtUserRights: <fulfilled with 0 (zero)>
F-47 Condition For
Password changed By
change the password related to the operator that is executing
User
the request.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation:
<changePasswordByUser>
_ opticsIMUserPassword: <old operator password>
_ opticsIMCorollaryPassword: <new operator password>
F-48 Condition For
change the password related to an operator .
Password changed By

Function SNMPv2
SN
PIf
Administrator
The operation is made by an operator with Administrator
profile rights.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation:
<changePasswordByAdmin>
_ opticsIMUserPassword: <new operator password>
F-49 Request
Y This management function allows the managing system to get
Username List
the list of all usernames admitted in the
managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMCtUserTable
Service Used
SNMP-GET-NEXT on
_ opticsIMCtUserId
_ opticsIMCtUserRights

Supported Objects
(Table/Scalar/Trap)
Table Entry
Description
Indexes Values
1AA 00014 0004 (9711) A4
opticsIMSecurityMIB
opticsIMCtUserTable
Max 25 entries
opticsIMCtUserId
opticsIMCtUserPassword
opticsIMCtUserRights
opticsIMCtRowStatus
opticsIMUserOperationTable Only one entry
opticsIMUserOperationOperation
opticsIMUserUsername
opticsIMUserPassword
opticsIMCorollaryUsername
opticsIMCorollaryPassword
opticsIMCtUserRights
ED
NTIAL
WTD
01
It.01
1..N
(note 1)
3DB161760000DSZZA
187/202
ED
WTD
01
It.01
3DB161760000DSZZA
188/202
1AA 00014 0004 (9711) A4

(note 1)
index value 1 and 2 are reserved for default user (1 for initial, 2 for
Craftperson).

15 ALARMS
15.1 Alarms Provided by Item HW
URU alarms are not supported.
Legenda:
SA
SAac
NSA
=
=
=
always Service Affecting

Service Affecting when the alarm is present on the active channel,
Not Service Affecting when it is present on the stand-by channel
always Not Service Affecting
Service Affecting Evaluation
Equipment
Type
Equipment
Expected
Main Unit 48/60 V M4860-32

Range Supply
Main Unit 24/60 V M2460-32
Range Supply
Alarm
Description
Cable Loss IDU
SA
Card Fail
SA
Equipment Mismatch
SA
1AA 00014 0004 (9711) A4
E1 RDI egressing (Rx

side) (note 1)
E1 RDI ingressing (Tx
side) (note 1)
ED
WTD
01
It.01
1+1
SAac
(note 3)
SAac
(note 2)
SAac
(note 2)
SA
SA
NSA
NSA
NSA
NSA
NSA
NSA
High BER
SA
SAac
(note 3)
SA
Housekeeping Alarm
NSA
NSA
NSA
Lan Failure
NSA
NSA
NSA
Battery Failure (note 6)
SA
NSA
SA
Link Identifier Mismatch
SA
SA
SA
SA
SA
SA
SA
SA
SA
SA
SAac
(note 3)
SAac
(note 3)
SA
SA
SA
NSA
NSA
NSA
Loss of Frame of PDH

tributary ingressing (Tx
side) (note 1)
tributary egressing (Rx
side) (note 1)
signal Radio side
Loss of Signal of PDH
tributary
Loss of 64kbit/s G.703
Auxiliary Signal
NTIAL
1+0
1+1w/o
EPS
MUX
protec.
SAac
(note 3)
NSA
NSA
NSA
NMS Signal
(DTE and Asynchronous COMPANY CONFIDENTIAL
3DB161760000DSZZA
189/202
Equipment
Type
Equipment
Expected
Alarm
Description
1+0
1+1
1+1w/o
EPS
MUX
protec.
mode only)
Loss of 64kbit/s V.11
Auxiliary Signal
Loss of 64kbit/s V.11
NMS Signal
(codirectional mode
only)
PDH-AIS egressing (Rx
side)
PDH-AIS ingressing (Tx
side)
NSA
NSA
NSA
NSA
NSA
NSA
SA
SA
SA
SA
SA
SA
PPP IP Fail
NSA
NSA
NSA
TCA on Hop Section
SA
SAac
(note 3)
SAac
(note 3)
TCA on Link Section

(note 3)
SA
SA
UAT on Hop Section
SA
SAac
(note 3)
SAac
(note 3)
SA
SA
NSA
NSA
NSA
UAT on Link Section

(note 3)
Firmware Download in
progress


Equipmen
t Expected
Extension Unit 48/60 E4860-32

V Range Supply
Extension Unit 24/60 E2460-32
V Range Supply
Alarm
Description
Cable Loss IDU
Card Fail
Card Missing
Equipment Mismatch
E1 RDI egressing (Rx

side) (note 1)
E1 RDI ingressing (Tx
side) (note 1)
ED
WTD
01
It.01
1+0
1+1
SAac
(note
SAac
(note
SAac
(note
SAac
(note
3)
2)
2)
2)
1+1w/o
EPS
MUX
protec.
SAac
(note 3)
SAac
SAac
SAac
NSA
NSA
3DB161760000DSZZA
190/202
1AA 00014 0004 (9711) A4
Equipment
Type

Equipment
Type
Equipmen
t Expected
High BER
SAac
(note 3)
1+1w/o
EPS
MUX
protec.
SA
(note 3)
SA
SA
Loss of Alignment
NSA
NSA
SA
SA
SA
SA
SAac
(note 3)
SAac
(note 3)
SA
SA
NSA
NSA
NSA
NSA
SA
SA
SA
SA
TCA on Hop Section
SAac
(note 3)
SAac
(note 3)
TCA on Link Section
SA
SA
UAT on Hop Section
SAac
(note 3)
SAac
(note 3)
UAT on Link Section
SA
SA
NSA
NSA
NSA
NSA
NSA
Card Fail
SA
SA
SA
Card Missing
SA
SA
SA
Equipment Mismatch
SA
SAac
(note 2)
SA
Loss of Signal on
Ethernet port (link down)
SA
SA
SA
Loss of data frame
SA
SA
SA
Alarm
Description
1+0

side) (note 1)
tributary egressing (Rx
side) (note 1)
signal Radio side
tributary
Auxiliary Signal
NMS Signal
(DTE and Asynchronous
mode only)
PDH-AIS egressing (Rx
side)
PDH-AIS ingressing (Tx
side)
Unconfigured
Equipment
(note 4)
Firmware Download in
progress
1AA 00014 0004 (9711) A4
Gigabit Ethernet unit
ED
NTIAL
WTD
01
It.01
P4DATASW
1+1
3DB161760000DSZZA
191/202
Equipment
Type
Equipmen
t Expected
Alarm
Description
1+0
1+1
1+1w/o
EPS
MUX
protec.
synchronization (Rx side)
16xE1/DS1 plug-in unit
P16E1DS1
Unconfigured
Equipment
(note 5)
NSA
Card Fail
SA
Card Missing
SA
Equipment Mismatch
SA

tributary
Unconfigured
Equipment
(note 5)
Audio
channels
+ P-AC-SC
Service Channel plug-in
unit
NSA
SAac
(note 2)
SAac
(note 2)
SAac
(note 2)
NSA
SA
SA
SA
SA
SA
SA
NSA
NSA
NSA
Card Fail
NSA
NSA
NSA
Card Missing
NSA
NSA
NSA

ED
WTD
01
It.01
3DB161760000DSZZA
192/202
1AA 00014 0004 (9711) A4
Unconfigured
Equipment
NSA
NSA
NSA
(note 5)
(note 1)
Only in case of framed tributaries.
(note 2)
The active channel must be referred to the EPS protection.
(note 3)
The active channel must be referred to the RPS protection.
(note 4)
This alarm is detected on Extension Unit, but reported on IDU Main Shelf.
(note 5)
This alarm is detected on plug-in unit, but reported on Main or Extension Unit
(according to the Unit on which the module is plugged).
(note 6)
In 1+1 configurations, the two battery are in protections between them: in normal
condition, one battery supplies one channel, when one of the two is fail, the other one supplies also
the channel which has the battery failure.

ODU Alarms
Equipment Equipment
Type
Expected
ODU ETSI
ODU-E
Service Affecting
Evaluation
1+1
w/o
1+1 1+1
1+0
MUX
FD
HSB
EPS
prot.
Alarm
Description
ATPC Loop
NSA
NSA
NSA
NSA
Card Fail
SA
SAac
SAac
SAac
Demodulation Function Failure

(note 4)
SA
SAac
SAac
SAac
Early Warning (note 8)
NSA
NSA
NSA
Equipment Mismatch
SA
SAac
SAac
SAac
Loss of Signal for the Modulation

Function (note 2)
SA
NSA
SAac
SAac
Modulation Function Failure (note 7)
SA
NSA
SAac
SAac
ODU not responding (note 1)
SA
SAac
SAac
SAac
SA
SAac
SAac
SAac
SA
SAac
SAac
SAac
SA
SAac
SAac
SAac
SA
SAac
SAac
SAac
NSA
NSA
NSA
NSA
Receiving Function Failure (note 3)
SA
SAac
SAac
SAac
Software Version Mismatch
NSA
NSA
NSA
NSA
Stand-by Software Version Mismatch
NSA
NSA
NSA
NSA
Transmission Function Failure (note 5)
SA
NSA
SAac
SAac
Unconfigured Equipment (note 6)
NSA
NSA
NSA
NSA
Firmware Download in progress
NSA
NSA
NSA
NSA
Provisioned Shifter incompatible with

actual HW
Provisioned Frequency incompatible with
actual HW
Provisioned Modulation incompatible
with actual HW
Provisioned Capacity incompatible with
actual HW
Provisioned Tx Power incompatible with
actual HW
1AA 00014 0004 (9711) A4
N.B.: The active channel must be referred to the RPS, except for the transmission alarms in 1+1
HSB configurations (for these alarms the active channel must be referred to TPS).
(note 1)
This alarm represents a communication problem with the ODU (i.e. IDU-ODU cable
failure, ODU missing, ODU power problem).
(note 2)
Loss of Signal for the Modulation Function represents the missing of data at the cable
input of the ODU.
(note 3)
Receiving Function Failure represents the received power alarm.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
193/202
Demodulation Function Failure represents the synchronization missing at receive side

Transmission Function Failure represents the transmitted power alarm.
Only for ODU Ch#0 in 1+1 configurations.
Modulation Function Failure represents the synchronization missing at transmission
Only in the 1+1 configurations with Hitless Switch.
15.2 Alarms Reported

The following tables provide the list of all the alarm types supported in this release with the notification
type used to report the alarm and the object that identify the resource generating the alarm itself.
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 Alarms 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 Cross Alarm (TCA), the 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.

(note 4)
alarm.
(note 5)
(note 6)
(note 7)
side alarm.
(note 8)
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 alarms traps.
15.2.1 Equipment Alarms

Notification Type
(Mib)
Remote NE Failure RemoteNEFailure

Indication
(tsdimSnmpNEMib)
Housekeeping Alarm
HousekeepingAlarm
(opticsIMEqptMib)
Card Fail
ReplaceUnitProblem
(opticsIMEqptMib)
ED
WTD
01
It.01
Objects
Index
Value
1.1.0.0
Table/Scalar
Equipment
(Mib)
Label
EquipmentTable
(opticsIMEqptMib)
ExternalInputPoint 1..6
(opticsIMEqptMib)
EquipmentTable
1.1.1.0 MAIN Ch#1
(opticsIMEqptMib) 1.1.1.1 MAIN/<(note 1)>
Ch#1
1.1.1.2 MAIN/<note
2>
Ch#1
1.2.0.0 ODU Ch#1
1.3.1.0 EXT Ch#0
1.3.1.1 EXT/<(note 1)>
3DB161760000DSZZA
194/202
1AA 00014 0004 (9711) A4
Alarm
Description

Alarm
Description
Notification Type
(Mib)
Card Missing
ReplaceUnitMissing
(opticsIMEqptMib)
Equipment Mismatch
ReplaceUnitTypeMismatch
(opticsIMEqptMib)
Lan Failure
Table/Scalar
(Mib)
LanFailure
(opticsIMEqptMib)
Battery Failure
BatteryFailure
(opticsIMEqptMib)
ODU not responding
InternalCommunicationPr EquipmentTable
oblem
(opticsIMEqptMib)
(opticsIMEqptMib)
Software
Version VersionMismatch
Mismatch
(opticsIMEqptMib)
Stand-by
Software StandByVersionMismatch
Version Mismatch
(opticsIMEqptMib)
Unconfigured
UnconfiguredEquipmentPr
Equipment
esent
(opticsIMEqptMib)
Firmware Download in FirmwareDownloadOnGo

progress
ing
(opticsIMEqptMib)
1AA 00014 0004 (9711) A4
(note 1)
ED
WTD
1.1.1.0 MAIN Ch#1

1.2.0.0 ODU Ch#1
1.4.0.0 ODU Ch#0
1.2.0.0
1.4.0.0
1.2.0.0
1.4.0.0
1.1.1.0
ODU Ch#1
ODU Ch#0
ODU Ch#1
ODU Ch#0
MAIN/Plug-in
Ch#1
1.1.0.0 EXT Ch#0

1.3.1.0 EXT/Plug-in
Ch#0
1.4.0.0 ODU Ch#0
1.1.1.0 MAIN Ch#1
1.1.1.1 MAIN/DATA
1.2.0.0 ODU Ch#1
1.3.1.0 EXT Ch#0
1.4.0.0 ODU Ch#0

empty, when no plug-in is configured
DATA, when the 4xDATA (Gigabit Eth.) plug-in is provisioned.
(note 2)
NTIAL
Objects
Index
Equipment
Value
Label
Ch#0
1.4.0.0 ODU Ch#0
1.1.1.1 MAIN/<(note 1)>
Ch#1
1.1.1.2 MAIN/<note
2>
Ch#1
1.3.1.0 EXT Ch#0
1.3.1.1 EXT/<(note 1)>
Ch#0
1.1.1.0 MAIN Ch#1
1.1.1.1 MAIN/<(note 1)>
Ch#1
1.2.0.0 ODU Ch#1
1.3.1.0 EXT Ch#0
1.3.1.1 EXT/<(note 1)>
Ch#0
1.4.0.0 ODU Ch#0
1.1.1.0 MAIN Ch#1
01

It.01
3DB161760000DSZZA
195/202
15.2.2 Communication Alarms

Alarm
Description
Notification Type
(Mib)
Loss of 64 kbit/s G.703 LossOfSignal

(tsdimSnmpNEMib)
Auxiliary Signal
Loss of 64 kbit/s V.11
Auxiliary Signal
Cable Loss IDU
CableLOS
(tsdimSnmpNEMib)
High BER
HighBER
(opticsIMRadioTrsCommonMib
)
Loss of Frame of PDH LossOfFrame
signal Radio side
(tsdimSnmpNEMib)
E1 RDI ingressing (Tx side) RemoteDefectIndication
(tsdimSnmpNEMib)
E1 RDI egressing (Rx side)

side)
tributary
PDH-AIS ingressing
(Tx side)
tributary egressing (Rx side)
PDH-AIS egressing
(Rx side)
LossOfFrame
(tsdimSnmpNEMib)
LinkIdentifierMismatch
(opticsIMTrsCommonMib)
Loss
of
data
frame
synchronization (Rx side)
Loss of Signal on Ethernet
port (link down)
LossOfFrame
(tsdimSnmpNEMib)
LossOfSignal
(tsdimSnmpNEMib)
ED
WTD
01
It.01
LossOfSignal
(tsdimSnmpNEMib)
opticsIMAlarmAis
(tsdimSnmpNEMib)
LossOfFrame
(tsdimSnmpNEMib)
opticsIMAlarmAis
(tsdimSnmpNEMib)
Objects
Table/Scalar
(Mib)
AuxiliaryPITTPBidTable
(opticsIMOverheadMib)
Index
Value
301
CoderTTPTable
(opticsIMTrsPdhMib)
20101
20100

empty, when no plug-in is configured

AC-SC, when the audio channels+ Service Channel plug-in is provisioned.
E1pPITTPTable
1xx01 or
(opticsIMTrsCommonMib) 1xx99
(xx=1..3
2)
(note 1)
E1PathTTPTable
2xx01 or
(xx=1..3
2)
(note 2)
E1pPITTPTable
1xx01 or
(xx=1..3
2)
(note 1)
E1PathTPTable
2xx01 or
(xx=1..3
2)
(note 2)
FrameTTPTable
20101 or
(opticsIMTrsPdhMib)
20199
(note 2)
EthConfTable
29901
(opticsIMEthNEMib)
ifMauTable
11701;1
(mauMod)
11801;1
3DB161760000DSZZA
196/202
1AA 00014 0004 (9711) A4

TCA on Hop Section
TCA
(tsdimSnmpNEMib)
UAT on Hop Section
UnavailableTime
(tsdimSnmpNEMib)
TCA on Link Section
TCA
(tsdimSnmpNEMib)
UAT on Link Section
UnavailableTime
(tsdimSnmpNEMib)
Loss of 64kbit/s G.703 LossOfSignal
NMS Signal (DTE and (tsdimSnmpNEMib)
Asynchronous mode only)
Loss of 64kbit/s V.11 NMS
Signal (codirectional only)
PPP IP Fail
PPPFail
(tsdimSnmpNEMib)
ATPC Loop
Early Warning
1AA 00014 0004 (9711) A4
Provisioned Frequency (or

shifter value) incompatible
with actual HW
Provisioned shifter value
incompatible with actual
HW
Provisioned
modulation
value incompatible with
actual HW
Provisioned capacity value
HW
Provisioned
Tx
Power
HW
Receiving Function Failure
Transmission
Function
Failure
Demodulation
Function
Failure
Loss of Signal for the
Modulation Function
Modulation
Function
Failure
Loss of Alignment
ED
NTIAL
WTD
01
It.01
Objects
PdhFrameHopCurrentDat
aTable
(opticsIMPdhPmMib)
PdhFrameLinkCurrentDat
aTable
(opticsIMPdhPmMib)
PointToPointIPTable
(opticsIMCommRouMib)
20101; 1
20101; 2
20100; 1
20100; 2
20199; 1
20199; 2
1
2
3
AtpcLoopProblem
RadioPDHTTPBidTable
20101
(opticsIMRadioTrsCommonMib (opticsIMRadioTrsPdhMib) 20100
)
EarlyWarning
)
IncompatibleFrequency
)
RxDivFail
)
DemDivLOS
(opticsIMRadioTrsCommonMib)
VcoExternalLOS
(opticsIMRadioTrsCommonMib)
IncompatiblePTX
)
RxFail
(tsdimSnmpNEMib)
TxFail
(tsdimSnmpNEMib)
DemFail
(tsdimSnmpNEMib)
ModLOS
(tsdimSnmpNEMib)
ModFail
(tsdimSnmpNEMib)
LossOfAlignment
(tsdimSnmpNEMib)
RadioPDHTTPBidTable
20101
(opticsIMRadioTrsPdhMib) 20100
RxStaticDelayTable
(opticsIMRadioSwtcMib)
1; 99
3DB161760000DSZZA
197/202
(note 2)
20101 in case of 1+0 configurations and 1+1 configuration without MUX EPS
protection, 20199 in case of 1+1 configurations.
15.3 Predefined ASAPs 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 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 general rule, the severity for 1+0 configurations is obtained using the SA severity also for the NSA
one (if they are different). The only exception is the LossOfSignal probable cause; infact, in this case,
different severity must be used for LOS of the PDH tributaries (SA) and of the auxiliary and NMS
signals (NSA).

(note 1)
1xx01 in case of 1+0 configurations and 1+1 configuration without MUX EPS
protection, 1xx99 in case of 1+1 configurations.
ASAP#1 (No Alarm) is not reported in these tables: the severity of all the notification types (probable
causes) is always NAL independently from the service dependency (SA and NSA).
The sum of alarms with CRITICAL or MAJOR severity is reported on LED MAJ on the front panel.
The sum of alarms with MINOR severity is reported on LED MIN on the front panel.
The alarms with WARNING severity are not reported on any LED on the front panel.
ED
WTD
01
It.01
3DB161760000DSZZA
198/202
1AA 00014 0004 (9711) A4
Legenda:
ETH: only in Ethernet configurations (1+0, 1+1)
1+1: only in 1+1 configurations
NAL: Non ALarm
MAJ: MAJor
MIN: MINor
WAR: WARning
1AA 00014 0004 (9711) A4

Equipment Alarms
Notification Type
Primary
Alarms
ASAP#2
SA
NSA
No Remote
Alarms
ASAP#3
SA
NSA
All
Alarms
ASAP#4
SA
NSA
HousekeepingAlarm
WAR
WAR
MIN
MIN
MAJ
MAJ
InternalCommunicationProble
m
MAJ
MIN
MAJ
MIN
MAJ
MIN
LanFailure
MIN
MIN
WAR
WAR
MIN
MIN
BatteryFailure
MIN
MIN
MIN
MIN
MIN
MIN
RemoteNEFailure
NAL
NAL
NAL
NAL
WAR
WAR
ReplaceableUnitMissing
MAJ
MIN
MAJ
MIN
MAJ
MIN
ReplaceableUnitProblem
MAJ
MIN
MAJ
MIN
MAJ
MIN
ReplaceableUnitTypeMismatc
h
MAJ
MIN
MAJ
MIN
MAJ
MIN
StandByVersionMismatch
MIN
MIN
MIN
MIN
MIN
MIN
UnconfiguredEquipmentPrese
nt
WAR
WAR
WAR
WAR
WAR
WAR
VersionMismatch
MIN
MIN
MIN
MIN
MIN
MIN
FirmwareDownloadOnGoing
MIN
MIN
MIN
MIN
MIN
MIN
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
199/202
Notification
Type
Config.
Primary
Alarms
ASAP#2
SA
NSA
No Remote
Alarms
ASAP#3
SA
NSA
All
Alarms
ASAP#4
SA
NSA
Ais
NAL
NAL
NAL
NAL
MAJ
MIN
AtpcLoopProblem
MIN
MIN
WAR
WAR
MIN
MIN
CableLOS
MAJ
MIN
MAJ
MIN
MAJ
MIN
DemFail
MAJ
MIN
MAJ
MIN
MAJ
MIN
EarlyWarning
NAL
NAL
WAR
WAR
WAR
WAR
HighBER
MIN
WAR
MIN
WAR
MIN
WAR
IncompatibleFrequency
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
MAJ
MIN
IncompatiblePTX
WAR
WAR
WAR
WAR
WAR
WAR
LinkIdentifierMismatch
MAJ
MIN
MAJ
MIN
MAJ
MIN
MIN
MIN
MIN
MIN
MIN
MIN
LossOfFrame
MAJ
MIN
MAJ
MIN
MAJ
MIN
LossOfSignal
MAJ
MIN
MAJ
MIN
MAJ
MIN
ModLOS
MAJ
MIN
MAJ
MIN
MAJ
MIN
PPPFail
MIN
WAR
MIN
WAR
MIN
WAR
RemoteDefectIndication
NAL
NAL
NAL
NAL
WAR
WAR
RxFail
MAJ
MIN
MAJ
MIN
MAJ
MIN
ThresholdCross
MAJ
MIN
MAJ
MIN
MAJ
MIN
TxFail
MAJ
MIN
MAJ
MIN
MAJ
MIN
UnavailableTime
MAJ
MIN
MAJ
MIN
MAJ
MIN
ModFail
MAJ
MIN
MAJ
MIN
MAJ
MIN
IncompatibleShifter
(RxDivFail) (note 1)
IncompatibleModulation
(DemDivLOS) (note 2)
IncompatibleCapacity
(VcoExternalLOS) (note 3)
LossOfAlignment
1+1

Communication Alarms
ED
WTD
01
It.01
3DB161760000DSZZA
200/202
1AA 00014 0004 (9711) A4
(note 1)
RxDivFail is the correct notification type, but the sw realizes a translation and then to
CT, the label IncompatibleShifter is shown.
1AA 00014 0004 (9711) A4

(note 2)
DemDivLOS is the correct notification type, but the sw realizes a translation and then to
CT, the label IncompatibleModulation is shown.
(note 3)
VcoExternalLOS is the correct notification type, but the sw realizes a translation and
then to CT, the label IncompatibleCapacity is shown.
ED
NTIAL
WTD
01
It.01
3DB161760000DSZZA
201/202
ED
WTD
01
It.01
3DB161760000DSZZA
202/202
1AA 00014 0004 (9711) A4

END OF DOCUMENT

ulsSysSpecRel2 1 2Ed01It01

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ulsSysSpecRel2 1 2Ed01It01

Hochgeladen von

Copyright:

Verfügbare Formate

All rights reserved.

Passing on and copying of this

ULS 2.1 (v.2.1.2)

FUNCTIONAL DESCRIPTION ...................................................................................................................................9

EQUIPMENT DOMAIN ..........................................................................................................................................10

All rights reserved. Passing on and copying of this

TRANSMISSION INTERFACES (IFTABLE).......................................................................................................35

SDH/PDH TRANSMISSION DOMAIN..................................................................................................................38

FUNCTIONAL DESCRIPTION .................................................................................................................................38

ETHERNET TRANSMISSION DOMAIN .............................................................................................................60

FUNCTIONAL DESCRIPTION .................................................................................................................................83

SUPPORT DOMAIN ..............................................................................................................................................117

FUNCTIONAL DESCRIPTION ...............................................................................................................................117

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

COMMUNICATION AND ROUTING DOMAIN...............................................................................................147

FUNCTIONAL DESCRIPTION (SNMP INTERFACE)...............................................................................................182

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

[10] Optics-IM: SDH/PDH Transmission Domain (SNMP)

1AA 00014 0004 (9711) A4

[9] Optics-IM: Equipment Domain (SNMP)

All rights reserved. Passing on and copying of this

[11] Optics-IM: SDH/PDH Performance Monitoring Domain (SNMP)

[16] Optics-IM: List of SNMP Events

[17] Optics-IM: Operator Labels and Naming Rules (SNMP)

[18] Ethernet Physical Interface Management

[19] SNMP Management Functions

[20] Ethernet Port Management

[21] SNMP Management Functions

[22] Ethernet Performance Monitoring

[23] SNMP Management Functions

1AA 00014 0004 (9711) A4

3AL 81428 0014 DSZZA

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

Alarm Indication Signal

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

Table: Tributaries and modulations forecasted.

2.1 Functional Description

Radio Physical Interface (AWY)

1AA 00014 0004 (9711) A4

one radio channel (1+0 configurations);

The 2+0 and N+1 configurations are not supported.

The NE configuration is described in the Support Domain section.

Main Unit Ch#1

All rights reserved. Passing on and copying of this

Figure 1. Main IDU unit

Extension Unit Ch#0

Figure 2. Extension IDU unit

Outdoor Part (ODU)

1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this

3.2 Allowed Equipment Types

1AA 00014 0004 (9711) A4

All the 1+1 configurations.

All rights reserved. Passing on and copying of this

All the 1+0 configurations.

1AA 00014 0004 (9711) A4