ulsSysSpecRel2 0Ed9Rel

Site
VIMERCATE
Originators ULS 2.0

D.Spreafico
System Specification
SNMP Management Interface
Domain :
Division : WTD
Rubric :
Type : Specification
Distribution Codes Internal: External:
Approvals
G. Gariani
Name
App.
Name
App.
ED 09 RELEASED
8BW 03598 0000 DSZZA 1/ 182
SPECIFICATION
TABLE OF CONTENTS
HISTORY..................................................................................................................................................... 5
REFERENCED DOCUMENTS.................................................................................................................... 8
RELATED DOCUMENTS ........................................................................................................................... 8
PREFACE.................................................................................................................................................... 9
1 INTRODUCTION ................................................................................................................................ 10
1.1 Abbreviations ............................................................................................................................ 10
1.2 Glossary ..................................................................................................................................... 11
1.3 Scope.......................................................................................................................................... 11
2 OVERVIEW ........................................................................................................................................ 12
2.1 Functional Description ............................................................................................................. 12
2.2 Configurations........................................................................................................................... 12
3 EQUIPMENT DOMAIN ...................................................................................................................... 14
3.1 Overview .................................................................................................................................... 14
3.2 Allowed Equipment Types ....................................................................................................... 15
3.2.1 Shelves Equipment Types ................................................................................................... 15
3.2.2 Slots and Sub-slots Equipment Types................................................................................. 16
3.3 Remote Inventory Management............................................................................................... 18
3.4 Equipment Protection Switching Management...................................................................... 19
3.5 External Points Management ................................................................................................... 20
3.6 Management Functions ............................................................................................................ 21
3.6.1 Functional Objects Creation................................................................................................. 34
3.7 Supported Objects and Naming Rules ................................................................................... 35
4 TRANSMISSION INTERFACES (IFTABLE) ..................................................................................... 37
4.1 Management Functions ............................................................................................................ 37
4.2 SNMP Tables.............................................................................................................................. 38
4.2.1 Supported objects ................................................................................................................ 38
4.3 Naming Rules ............................................................................................................................ 38
5 SDH/PDH TRANSMISSION DOMAIN ............................................................................................... 40
R. Pellizzoni D. Spreafico
09 060918 ECO-00000xxxxx
G.Gariani D. Spreafico
08 060428 ECO-0000033183
R. Pellizzoni G.Gariani C. Pasqualini
01 040531
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
ULS 2.0
System Specification
SNMP Management Interface
09 RELEASED
8BW 03598 0000 DSZZA 2/ 182
5.2 Management Functions............................................................................................................ 44
6 ETHERNET TRANSMISSION DOMAIN............................................................................................ 60
6.2.1 Ethernet Physical Interface Management............................................................................ 63
6.2.2 Ethernet Port Management.................................................................................................. 67
6.2.3 GFP Provider Layer Management ....................................................................................... 71
6.2.4 GFP_T Management ........................................................................................................... 72
7 RADIO DOMAIN ................................................................................................................................ 74
7.3 Supported Objects and Naming Rules ................................................................................. 101
8 SUPPORT DOMAIN ........................................................................................................................ 104
8.1 Functional Description ........................................................................................................... 104
8.2 Management Functions.......................................................................................................... 109
9 COMMUNICATION AND ROUTING DOMAIN................................................................................ 129
10 OVERHEAD DOMAIN.................................................................................................................. 137
11 TEST DOMAIN ............................................................................................................................. 141
12 SDH/PDH PERFORMANCE MONITORING DOMAIN ................................................................ 145
13 SECURITY DOMAIN .................................................................................................................... 155
13.1 Functional Description (SNMP Interface) ............................................................................. 155
14 ALARMS ...................................................................................................................................... 161
14.1 Alarms Provided by Item HW................................................................................................. 161
14.2 Alarms Reported ..................................................................................................................... 165
14.2.1 Equipment Alarms ............................................................................................................. 165
14.2.2 Communication Alarms...................................................................................................... 166
14.3 Predefined ASAPs Severity ................................................................................................... 169
APPENDIX A CRAT TERMINAL ACCESS CONTROL ................................................................... 171
A.1 MENU ITEM FUNCTIONS........................................................................................................ 171
09 RELEASED
8BW 03598 0000 DSZZA 3/ 182
A.2 Functions View ........................................................................................................................ 176
09 RELEASED
8BW 03598 0000 DSZZA 4/ 182
HISTORY
Date Edition Comments

040504 Ed. 01 It. 1 Creation.
New features supported versus 1.1:
• IDU Scalable units
• Backup and Restore
• Received Automatic Control Status for FSO interface
• OffNormal object for abnormal conditions table.
The SNMP Optics-IM reference version for this release is the v2.17.
040531 Ed. 01 Rel. The SNMP Optics-IM reference version for this release is the v2.18.
The management of the status of the ODU Service Kit for FSO
configurations and of the allowed DS1 line lengths is supported.
The description of the management functions has been introduced.
041022 Ed. 02 It. 01 This release has been renamed from 1.2 to 2.0. It manages only AWY
Scalable (Restyling) product for ETSI market. Consequently any reference
to AWY Full Feature product has been removed. Other changes:
• Allowed equipment types (mnemonic)
• Frame structure configuration with Ethernet interfaces
• Allowed NE configuration types
• IP routing protocols supported
• Naming rules for tributaries and loopbacks
• V11 codirectional 64 kb/s and RS232 9,6 kb/s
041112 Ed. 02 Rel The following changes, highlighted by revision bars, are present in the
minutes of the review meeting (PM/RV 2/11/2004/2410):
• Removed any reference to management of DS1 and DS3 signal types.
• Management function F-1.1 and F-1.2 have been declared “supported”
(Y) and not “partially supported” (P). A note will specify: Supported on
the TPs managed in this release.
• Content and meaning of SW key have been inserted.
• The FPGAs and related versions have been inserted in the list of
software units.
• Abnormal condition: a note has been inserted in case of “Remote radio
Tx Mute” event type to explain that this event generates two abnormal
conditions : one locally and one remotely.
Furthermore, a change of requirements not known before the review
meeting has been managed: the ODU service kit and related management
is not supported anymore.
050125 Ed. 03 Rel The following changes, highlighted by revision bars, are listed in the
memorandum PM 3/12/2004/2410):
• Removed on opticsIME3pPITTPTable the ‘framed G.753’ value for
e3pPITTPSignalMode object.
• Inserted the indication of max entries for opticsIMOspfAreaTable.
• Added to opticsIMAuxiliaryPITTPBidTable new values for
opticsIMAuxiliaryPITTPBidType
Added on predefined ASAP Severity the ModFail alarm.

Added the FirmwareDownloadOnGoing alarm on ODU.
Summarizing alarms (on Housekeping output table) are specified
configuration dependent.
The document is not revised in a review meeting due to the publishing

modifications already agreed with the involved people.
050211 Ed. 04 It. 1 The SNMP Optics-IM reference version for this release is the v2.20.
The release managed is 2.0.1.
09 RELEASED
8BW 03598 0000 DSZZA 5/ 182
The new inserted features are:
• Frequency shifter management
• DS1/DS3 management (FCC features)
050415 Ed. 04 Rel. The following changes, highlighted by revision bars, are listed in the
memorandum PM 6/3/2005/2350/ds):
• The current document edition (Ed.4) is related to ULS 2.0.1 but also
to maintenance for ULS 2.0.0 and upper. The features not
supported by ULS 2.0.0 are specified (frequency shifter and DCC
features).
• F-48 (set polling timeout on rowStatus active) is not supported in
current release
• Delays to be inserted on manual static alignment have to be
included in the 0..31 range. Moreover: in a alignement only a value
(direct or indirect) has to be provided.
• Management funct. F-1.6 (Condition Rx Radio Frequency) and F-
1.7 (Request Rx Radio Frequency Range) are now supported to
allow a little modification of rx frequency using a shifter in a
predefined list.
• The ASAP of opticsIMGFPConfTable is defined with the ASAP of
opticsIMFrameTable
• opticsIMAlarmIncompatibleFrequencyRaise/Clear refer to
provisioned frequency not compatible with actual HW (freq not in
freRange) but also to shifter value not compatible with actual HW
(shifter value not in predefined list).
• Management funct. F-2.5 (Request FE MAU Jabber State) is no
longer supported.
• Ethernet loopbacks are no longer supported.
Other changes:
• The ClientSignalFail alarm is no longer supported (F-2.3 on
Ethernet Domain)
• The LBER alarm is no longer supported.
• The BatteryFail alarm is no longer supported.
• The F-1.141 (Condition Shifter Definition) management function is
allowed only to local managers.
• The radio link performance monitoring behaviour when Extension
unit is missing or switched off is defined.
The SNMP Optics-IM reference version for release 2.0.1 and upper is the
v2.20.
For release 2.0.0 the SNMP Optics-IM reference version is the v2.18.
050617 Ed. 05 It. 1 The SNMP Optics-IM reference version for this release is the v2.21.
The release managed is 2.0.2, but also to maintenance for ULS 2.0.0 and
ULS 2.0.1. The features not supported by ULS 2.0.0 and/or ULS 2.0.1 are
specified
Some mistakes are updated.
• new Power Supply ±24/±60 (M2460S and E2460S)
• New Allowed NE configuration types
• Input External Points on remote output external points
• Interleave exclusion
• Hop not intrusive BER measurement
• Intrusive BER (Intrusive Transmitted Power Control management)
• EOW party line enable/disable on NMS interfaces
• Free timed loop-back management
• Routing protocol RIP management
09 RELEASED
8BW 03598 0000 DSZZA 6/ 182
• Security SNMP v2
050624 Ed. 05 Rel. The following changes, highlighted by revision bars, are listed in the
revision review result document (8BW 03598 0000 DFZZA)
• The events that define the suspectInterval on BER measures are
inserted
• Activation of loopbacks limited on the time (free timed loop-back
management) are not stored on the NE database (to keep them
after NE Reset)
• Insert on ASAP definition the firmwareDownloadOnGoing alarm
• The root alarm for Switching criteria of Equipment Protection are
defined
050801 Ed. 06 It.1 The SNMP Optics-IM reference version for this release is the v2.21.
The release managed is 2.0.2, but without features inserted on Ed 5. Only
features related to security SNMP v2 are maintened
This release is related also for the maintenance for ULS 2.0.0 and ULS
2.0.1. The features not supported by ULS 2.0.0 and/or ULS 2.0.1 are
specified
• Security SNMP v2
Some mistakes are updated.
• added the firmwareDownloadOnGoing alarm on Main and Extention
Unit
• Insert on ASAP definition the firmwareDownloadOnGoing alarm
050829 Ed. 06 Rel The changes, highlighted by revision bars, are listed in the revision review
result document (8BW 03598 0000 DFZZA, Ed. 2).
Moreover some mistakes are updated (already inserted on Ed. 5, but
forgotten on Ed 6 It 1):
• new Power Supply ±24/±60 (M2460S and E2460S)
• New Allowed NE configuration types
060127 Ed. 07 It.1 The SNMP Optics-IM reference version for this release is the v2.21.
The release managed is 2.0.3, but is related also for the maintenance of
ULS 2.0.0 , ULS 2.0.1 and ULS 2.0.2.
The features not supported by ULS 2.0.0 and/or ULS 2.0.1 and/or ULS
2.0.2 are specified
Some mistakes the following items are updated.
• The check of the range within to move the Rx Frequency is
removed.
• The ‘incompatibleFrequency’ is raised also when Rx Frequency is
out of range
• The LinkIdentifier is no longer supported
• Appendix A (list of CT menus allowed on each user profile) is
updated according to Change Requests.
• The reporting of UEP alarm is changed
• Constraints about the SW Keys and E3/Ds3 plug-in configuration is
added.
060213 Ed. 07 Rel. The changes, highlighted by revision bars, are listed in the revision review
result document (8BW 03598 0000 DFZZA, Ed. 3).
Moreover the following items are inserted:
• A behaviour about the raise and clear of ‘incompatiblePTX’ alarm.
• The new behaviour of Lockout Spare EPS (disabling all RPS
functionalities).
• The user/pswd for ftp, telnet and pshell protocols are defined to
access to the NE.
060428 Ed. 08 Rel This edition is related to ULS release 2.0.4.
The new feature supported:
• ODU 32E1
09 RELEASED
8BW 03598 0000 DSZZA 7/ 182
Further explanation about the EPS Lockout spare command about the RPS
commands isabled.
Moreover some editorial mistakes are been corrected.
060918 Ed. 09 Rel This edition is related to ULS release 2.0.4.
• The new alarm ‘incompatibleShifter’ is added.
REFERENCED DOCUMENTS
[1] RFC 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types
[2] HW & SW Specification – 9400AWY Restyling New Generation PDH Radio Family (IDU, ODU
7&8GHz)
HSS/S056 – 8BW 03538 0000 DSZZA – Ed.01 2004.16.15 – Released
RELATED DOCUMENTS
[3] Optics-IM: Communication and Routing Domain (SNMP)
3AL 38806 0000 DSZZA
[4] Optics-IM: Support Domain (SNMP)

3AL 38806 0005 DSZZA
[5] Optics-IM: Equipment Domain (SNMP)

3AL 38806 0013 DSZZA
[6] Optics-IM: SDH/PDH Transmission Domain (SNMP)

3AL 38806 0014 DSZZA
[7] Optics-IM: SDH/PDH Performance Monitoring Domain (SNMP)

3AL 38806 0012 DSZZA
[8] Optics-IM: Radio Domain (SNMP)

3AL 38806 0015 DSZZA
[9] Optics-IM: Test Domain (SNMP)

3AL 38806 0017 DSZZA
[10] Optics-IM: Overhead Domain (SNMP)

3AL 38806 0018 DSZZA
[11] Optics-IM: Security Domain (SNMP)

3AL 38806 0004 DSZZA
[12] Optics-IM: List of SNMP Events

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

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

3AL 81428 0012 DSZZA
[15] SNMP Management Functions

Annex to Ethernet Physical Interface Management
3AL 81428 0012 DSZZA
09 RELEASED
8BW 03598 0000 DSZZA 8/ 182
[16] GFP-provider Layer Management
3AL 81428 0020 DSZZA

Annex to GFP-provider Layer Management Functional Specification
3AL 81428 0020 DSZZA
[18] Ethernet Port Management

3AL 81428 0016 DSZZA

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

3AL 81428 0014 DSZZA

Annex to Ethernet Performance Monitoring Functional Specification
3AL 81428 0014 DSZZA
PREFACE
This document provides the functional description of SNMP management interface of ULS (Urban Link
Split mount) Radio NE in the scope of Release 2.0.
09 RELEASED
8BW 03598 0000 DSZZA 9/ 182
1 INTRODUCTION
1.1 Abbreviations
– AIS Alarm Indication Signal
– ANSI American National Standards Institute
– APT Active Problem Table
– ASAP Alarm Severity Assignment Profile
– ATPC Automatic Transmit Power Control
– AVC Attribute Value Change
– BER Bit Error Ratio
– BBE Background Block Error
– CD Current Data
– CLA Common Loss Alarm
– EC Equipment Controller
– EFC Ethernet Flow Control
– EFD Event Forwarding Discriminator
– EOW Engineering Order Wire
– EPS Equipment Protection Switching
– ES Errored Second
– ETH ETHernet
– ETSI European Telecommunications Standards Institute
– EW Early Warning
– FCS Frame Check Sequence
– FD Frequency Diversity
– FE Fast Ethernet
– FSO Free Space Optics
– GFP Generic Frame Protocol
– HBER High Bit Error Ratio
– HD History Data
– HET Hetero frequency
– HS Hitless Switch
– HST Hot Stand-by
– IDU InDoor Unit
– IM Information Model
– IP Internet Protocol
– LAN Local Area Network
– LAPD Link Access Procedure on D-channel
– LBER Low Bit Error Ratio
– LOF Loss Of Frame
– LOS Loss Of Signal
– MAC Medium Access Control
– MAU Medium Attachment Unit
– MIB Management Information Base
– NE Network Element
– NMS Network Management system
– NSA Not Service Affecting
– NTP Network Time Protocol
– OC ODU Controller
– ODU OutDoor Unit
– OFS Out of Frame Second
– OH OverHead
– OS Operation System
– PDH Plesyochronous Digital Hierarchy
– PM Performance Monitoring
– PPI Plesyochronous Physical Interface
09 RELEASED
8BW 03598 0000 DSZZA 10/ 182
– PSU Power Supply Unit
– QoS Quality of Service
– RACS Received Automatic Control Status
– RAI Remote Alarm Indication
– RDI Remote Defect Indication
– RI Remote Inventory
– RPS Radio Protection Switching
– RPPI Radio Plesyochronous Physical Interface
– SA Service Affecting
– SD Space Diversity
– SDH Synchronous Digital Hierarchy
– SES Severely Errored Second
– TCA Threshold Crossing Alarm
– TD Threshold Data
– TDF Total Discarded Frames
– TPS Tx Protection Switching
– TRCF Total Received Correct Frames
– TRCO Total Received Correct Octets
– TRSEF Total Received Service Errored Frames
– TS Time Slot
– TTF Total Transmitted Frames
– TTO Total Transmitted Octets
– TTP Trail Termination Point
– UAS UnAvailable Second
– UAT UnAvailable Time
– ULS Urban Low capacity Split
– URU Underling Resource Unavailable
1.2 Glossary
The following convention is used in the support table of the management functions:
- Y the function is supported
- N the function is NOT supported
- P the function is Partially supported
1.3 Scope
The management functionalities described in this document cover the functionalities of ULS NE
supported at SNMP interface in the scope of Rel. 2.0.
The SNMP Optics-IM reference version for release 2.0.0 is the v2.18, for release 2.0.1 is the v2.20, for
release 2.0.2, 2.0.3 and 2.0.4 is the v2.21.
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.
09 RELEASED
8BW 03598 0000 DSZZA 11/ 182
2 OVERVIEW
ULS NE has the aim to multiplexer/demultiplexer the main tributaries (up to 16 E1/16 DS1 or 1 E3/1
DS3) with different modulation formats.
The following table resumes the relation among market, tributaries and modulation.
Market Tributary Modulation

ETSI 2xE1 4QAM
4xE1 4QAM / 16QAM
8xE1 4QAM /16QAM
16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
ANSI 4xDS1 4QAM
(note 1) 8xDS1 4QAM / 16QAM
16xDS1 4QAM / 16QAM
1xDS3 4QAM / 16QAM
Table: Markets, tributaries and modulations forecasted.
(note 1) Not supported on ULS 2.0.0
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:
• one radio channel (1+0 configurations);

• two radio channels (1+1 configurations).
09 RELEASED
8BW 03598 0000 DSZZA 12/ 182
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.
09 RELEASED
8BW 03598 0000 DSZZA 13/ 182
3 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 Scalable
units.
Main Scalable Unit Ch#1
Figure 1. Main Scalable IDU unit
Extension Scalable Unit Ch#0
Figure 2. Extension Scalable IDU unit
The Main Scalable Unit provides the external interfaces for the E1/E3/DS1/DS3 tributaries, user service
channel, housekeeping and summarizing alarms, NMS V11 and G703 interfaces and a telephone jack. It
contains the MONOM, the PQECRC and the Power Supply units. The MONOM unit manages 8E1/DS1
tributaries, the Mux/Demux and the cable interface functions. The PQECRC unit implements the
Equipment and IDU Controller functions. Optional 8xE1/DS1 or E3/DS3 or Data unit implementing
Ethernet interfaces (alternative between them) can be plugged onto this Main unit.
The Main unit is used both in 1+0 and 1+1 configurations.
The Extension Scalable Unit contains the MONOE, the Power Supply and the Hitless Switch units.
Optional 8xE1/DS1 or E3/DS3 unit (alternative between them) can be plugged onto this Extension unit.
The Extension unit is used only in 1+1 configurations.
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.
09 RELEASED
8BW 03598 0000 DSZZA 14/ 182
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 sub-
slots) 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 Allowed
Market Allowed Equipment Type Equipment
Scalable Position Equipment
Type Description Label
Configuration Type
(note 1) 1.1.0.0 IDU Main Scalable Shelf IDU-M IDU Ch#1
1+0 ODU-E
1+0 ETH ETSI ODU 1+0 4/16 QAM ETSI
(note 5)
(note 2) 1.2.0.0 ODU Ch#1
ODU-A
ANSI ODU 1+0 4/16 QAM ANSI
(note 4)
(note 1) 1.1.0.0 IDU Main Scalable Shelf IDU-M IDU Ch#1

ODU-E
ETSI ODU 1+0 4/16 QAM ETSI
(note 5)
1.2.0.0 ODU Ch#1
ODU-A
1+1 (note 4)
(note 3) (note 1) 1.3.0.0 IDU Extension Scalable Shelf IDU-E IDU Ch#0
ODU-E
ETSI ODU 1+0 4/16 QAM ETSI
(note 5)
1.4.0.0 ODU Ch#0
ODU-A
(note 4)
(note 1) The equipment types allowed for IDU shelf are market type independent.
(note 2) All the 1+0 configurations.
(note 3) All the 1+1 configurations.
09 RELEASED
8BW 03598 0000 DSZZA 15/ 182
(note 5) The Equipment Type ODU-E is compliant both for ODU 16E1 (mnemonic ODU-E of
Remote Inventory for ETSI market) and for ODU 32E1 (mnemonic ODU32E1 for
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 ODU32E1.
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
IDU-M
Position Allowed Equipment Type Allowed Equipment Label

Description Equipment
Type
1.1.1.0 Scalable Main Unit ±24 V Supply M24S IDU/MAIN Ch#1
Scalable Main Unit ±48/±60 V Range Supply M4860S
Scalable Main Unit ±24/±60 V Range Supply M2460S

(note 2)
1.1.1.1 8xE1/DS1 plug-in unit P8E1DS1 IDU/MAIN/<note 1> Ch#1
1xE3/DS3 plug-in unit P1E3DS3
2xEthernet plug-in Scalable unit P2DATAS

Table: Allowed board/plug-in types in IDU Scalable Main shelf
(note 1) The label is one of the following:
• E1, when the 8xE1/DS1 plug-in is provisioned and it configured to work in E1 mode
• DS1, when the 8xE1/DS1 plug-in is provisioned and it configured to work in DS1 mode.
Not supported on ULS 2.0.0.
• DS3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in DS3 mode
• DATA, when the 2xDATA plug-in is provisioned.
(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1
09 RELEASED
8BW 03598 0000 DSZZA 16/ 182
IDU-E
Position Allowed Equipment Type Allowed Equipment Label

Description Equipmen
t Type
1.3.1.0 Scalable Extension Unit ±24 Supply E24S IDU/EXT Ch#0
Scalable Extension Unit ±48/±60 V Range Supply E4860S
Scalable Extension Unit ±24/±60 V Range Supply E2460S

(note 2)
1.3.1.1 8xE1/DS1 plug-in unit P8E1DS1 IDU/EXT/<note 1> Ch#0
1xE3/DS3 plug-in unit P1E3DS3

Table: Allowed board/plug-in types in IDU Scalable Extension shelf
(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1
ODU
No slot can be defined inside the Electrical ODU.
09 RELEASED
8BW 03598 0000 DSZZA 17/ 182
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 (M24S, M4860S, M2460S)
• Extension Unit (E24S, E4860S, E2460S)
• Ethernet plug-in (P2DATAS)
• PDH Tributary optional plugs-in (P8E1DS1, P1E3DS3)
• ODU unit (ODU-E, ODU-A, ODU32E1)
For all the other equipment types the remoteInventoryStatus columnar object assumes the value
“unavailable”.
The RI data of each sub-components unit (i.e. MONOM in the IDU, MILOU in the ODU) won’t 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 isn’t possible to read the Remote Inventory information, a “Card Fail” alarm is declared.
09 RELEASED
8BW 03598 0000 DSZZA 18/ 182
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.
Parameter Type Value

Protection group type 1+1
Switching type Single ended
Restoration criteria Revertive/Non Revertive
Switching condition Equipment failures
Operator commands 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.
09 RELEASED
8BW 03598 0000 DSZZA 19/ 182
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):
Allowed Allowed Allowed Event

EventId Event description
1 Major Alarm OR of critical and mayor alarms
2 Minor Alarm OR of minor and warning alarms
3 Service Affecting Alarm OR of service affecting alarms
4 Line side LOS Alarm OR of PDH tributaries and Ethernet interfaces LOS alarms
5 Cable Loss IDU Alarm OR of cable loss IDU alarms
6 Radio Signal Fail Alarm OR of radio signal fail and HBER alarms
7 Local Defect Indication see [2] for the primitives
8 Remote NE Failure Indication see [2] 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:
Index Automatic Automatic

Configuration UserLabel ExternalState Polarity Criteria
Value Event EventId
Read- Read-
Read-only Read-only Read-only Read-only
write only
5 Fail IDU
All the 1+0
All the 1+1 on/ activeLow/ Fail ODU
6 automatic -1
off activeHigh Ch#1
Fail ODU
7 All the 1+1
Ch#0
09 RELEASED
8BW 03598 0000 DSZZA 20/ 182
3.6 Management Functions
The following table lists the Equipment management functions supported in this release (see [5]).
Equipment
Function Equipment SN Function Description

Configuration MP
If
This management function allows a managing system to request
F-2.1 Request Allowed Y the allowed equipment types for each equipment identified by the
Equipment Types 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
This management function allows a managing system to configure
F-2.2 Condition Equipment N the equipment type expected for an equipment position. This
Expected 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 Y the equipment type expected for an equipment position. This
Expected information is provided by means of equipment type identifier and
associated string.
Scope
Service Used
SNMP-GET on:
• equipmentExpectedTypeId
• equipmentExpected
F-2.4 Request Equipment Y the equipment type of the equipment physically present.
Actual Scope
Service Used
SNMP-GET on equipmentActual
This management function allows a managing system to
F-2.5 Condition N suspend/resume the use of an equipment. It applies to equipment
09 RELEASED
8BW 03598 0000 DSZZA 21/ 182
Administrative State objects representing slots/boards and sub-slots/daughter boards.
Putting an equipment in the “outOfService” state has the effect that
the functional objects supported by the board are released from
any service. Instead, putting an equipment in the “inService” state
has the effect that the functional objects supported by the board are
put into service.
Scope
Service Used
SNMP-SET on equipmentAdministrativeState
F-2.6 Request Administrative Y whether the equipment is in or out of service.
State Scope
Service Used
SNMP-GET on equipmentAdministrativeState
Note F-2.6: Default value: inService.

F-2.7 Condition ASAP Y the ASAP Pointer associated to an equipment position.
Pointer Scope
Service Used
SNMP-SET on equipmentAsapIndex
F-2.8 Request ASAP Pointer Y the ASAP Pointer associated to an equipment position.
Scope
Service Used
SNMP-GET on equipmentAsapIndex
F-2.9 Request Equipment Y the label associated to an equipment position.
Label Scope
Service Used
SNMP-GET on equipmentLabel
F-2.10 Request Affected N the functional objects which are in operational dependency with an
Objects List equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMAffectedObjectListTable
Service Used
SNMP-GET on affectedObjectInstanceId
Function Equipment Status SN Function Description

MP
If
This management function allows the managing system to request
F-2.11 Request Equipment Y the operational state of an equipment.
Operational State Scope
Service Used
SNMP-GET on equipmentOperationalState
09 RELEASED
8BW 03598 0000 DSZZA 22/ 182
Function Equipment SN Function Description
Notifications MP
If
This management function allows a managed system to report
F-2.12 Report Equipment Y equipment alarms.
Alarm 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
• opticsIMAlarmLowPowerRaise
• opticsIMAlarmLowPowerClear
• opticsIMAlarmStandByVersionMismatchRaise
• opticsIMAlarmStandByVersionMismatchClear
• opticsIMAlarmRemoteInventoryFailureRaise
• opticsIMAlarmRemoteInventoryFailureClear
• opticsIMAlarmRepeaterCableProblemRaise
• opticsIMAlarmRepeaterCableProblemClear
• opticsIMAlarmProvisioningMismatchRaise
• opticsIMAlarmProvisioningMismatchClear
Function Remote Inventory SN Function Description

MP
If
F-2.13 Request Remote Y the remote inventory data associated to an equipment.
Inventory Data Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteInventoryTable
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 23/ 182
SNMP-GET on:
• remoteInventoryStatus
• remoteInventoryCompanyIdentifier
• remoteInventoryMnemonic
• remoteInventoryCLEICode
• remoteInventoryPartNumber
• remoteInventorySoftwarePartNumber
• remoteInventoryFactoryIdentifier
• remoteInventorySerialNumber
• remoteInventoryDateIndentifier
• remoteInventoryDate
• remoteInventoryCustomerField
Function Tributary Ports SN Function Description

Impedance MP
If
F-2.14 Condition E1 Y the impedance used by E1 tributary ports (balanced 120 Ohm or
Tributary Ports Impedance unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-SET on opticsIMTribPortsImpedance
F-2.15 Request E1 Tributary Y the impedance used by E1 tributary ports (balanced 120 Ohm or
Ports Impedance unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-GET on opticsIMTribPortsImpedance
Equipment Protection
Function Creation/Deletion SN Function Description

MP
If
This management function allows a managing system to allocate
F-3.1 Create Equipment N an equipment protection group entry. The managing system has to
Protection Group 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
This management function allows a managing system to delete an
F-3.2 Delete Equipment N equipment protection group entry and related protection units.
09 RELEASED
8BW 03598 0000 DSZZA 24/ 182
Protection Group Scope
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRowStatus
object to “destroy” value
Function Configuration SN Function Description

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

Commands MP
If
This management function allows the managing system to
F-3.9 Allow/Inhibit Switch of N inhibit/allow a working equipment (main) to be switched to a
a Working Equipment 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
09 RELEASED
8BW 03598 0000 DSZZA 25/ 182
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)
F-3.10 Allow/Inhibit Switch Y inhibit/allow a protection equipment (spare) to provide protection in
of Protection Equipment the protection scheme. If the protection equipment was already
providing protection for a working one when the Inhibit Switch is
requested, then a forced switch is performed back to the working
position.
noRequest syntax to remove the lockout and allow the switch, both
addressed to the spare protection unit.
Scope
(on spare protection unit)
Service Used
(lockout or noRequest)
F-3.11 Initiate/Terminate Y initiate/terminate a manual switch from a working equipment to a
Manual Switch to Protection protection one. This command will fail if another working equipment
Equipment has already been switched when to the protection equipment (only
in case of 1:N) or if the protection equipment has a failure
condition.
This function involves the manualSwitch syntax to initiate the
switch, the noRequest syntax to terminate the manual switch, both
addressed to a main protection unit.
Scope
Service Used
(manualSwitch or noRequest)
F-3.12 Initiate/Terminate Y initiate/terminate a manual switch from a protection equipment
Manual Switch to a Working (spare) to a working one (main). This management function is
Equipment applicable only in case of 1+1 not revertive protection type. This
command will fail if the working equipment has a failure condition.
Scope
Service Used
(manualSwitch or noRequest)
F-3.13 Initiate/Terminate Y initiate/terminate a forced switch from a working equipment (main)
Forced Switch to Protection to a protection one (spare). If another working equipment has
Equipment 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
09 RELEASED
8BW 03598 0000 DSZZA 26/ 182
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
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
(forcedSwitch or noRequest)
F-3.14 Initiate/Terminate N initiate/terminate a forced switch from a protection equipment
Forced Switch to a Working (spare) to a working one (main). This management function is
Equipment applicable only in case of 1+1 not revertive protection type.
the noRequest syntax to terminate the switch, both addressed to
the spare protection unit.
Scope
Service Used
(forcedSwitch or noRequest)
Function Protection Status SN Function Description

MP
If
F-3.15 Request Equipment Y the operational state of an equipment protection scheme.
Protection Scheme Scope
Operational State OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionGroupOperationalState
F-3.16 Request Equipment Y the current state of an equipment protection unit.
Protection Status Scope
Service Used
SNMP-GET on:
• opticsIMEquipmentProtectionUnitSwitchCommand
• opticsIMEquipmentProtectionUnitSwitchCriteria
• opticsIMEquipmentProtectionUnitSwitchStatus
F-3.17 Request Equipment N the source of the equipment switching request. This management
Protection Switching Source function is applicable only in case of dual ended switching.
Scope
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionUnitSwitchRequestSource
09 RELEASED
8BW 03598 0000 DSZZA 27/ 182
This management function allows the managed system to report
F-3.18 Report Equipment N any protection switch event to the managing system, such as:
Protection Switch Event • 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:
• opticsIMEquipmentProtectionUnitSwitchCommand
• opticsIMEquipmentProtectionUnitSwitchCriteria
• opticsIMEquipmentProtectionUnitSwitchStatus
External Points
Function Input Point SN Function Description

Configuration MP
If
F-4.1 Condition External Y the user label associated to an external input point.
Input Point User Label Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-SET on inputPointUserLabel
F-4.2 Request External Input Y the user label associated to an external input point.
Point User Label Scope
Service Used
SNMP-GET on inputPointUserLabel
F-4.3 Request External Input Y the state of an external input point (“on” when the alarm is raised,
Point External State “off” otherwise).
Scope
Service Used
SNMP-GET on inputPointExternalState
F-4.4 Condition External Y the ASAP Pointer associated to an external input point.
Input Point ASAP Pointer Scope
Service Used
SNMP-SET on inputPointAsapIndex
F-4.5 Request External Input Y the ASAP Pointer associated to an external input point.
Point ASAP Pointer Scope
Service Used
SNMP-GET on inputPointAsapIndex
F-4.6 Condition External Y the polarity of an external input point.
Input Point Polarity Scope
09 RELEASED
8BW 03598 0000 DSZZA 28/ 182
Service Used
SNMP-SET on inputPointPolarity
F-4.7 Request External Input Y the polarity of an external input point.
Point Polarity Scope
Service Used
SNMP-GET on inputPointPolarity
Function Input Point Status SN Function Description

MP
If
F-4.8 Request External Input Y the operational state of an external input point.
Point Operational State Scope
Service Used
SNMP-GET on inputPointOperationalState

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

Configuration MP
If
F-4.10 Condition External Y the user label associated to an external output point.
Output Point User Label Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointUserLabel
F-4.11 Request External Y the user label associated to an external output point.
Output Point User Label Scope
Service Used
SNMP-GET on outputPointUserLabel
F-4.12 Condition External Y the external state in order to command a remote control interface
Output Point External State (“on” when the command is raised, “off” otherwise).
09 RELEASED
8BW 03598 0000 DSZZA 29/ 182
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
F-4.13 Request External Y the external state (on or off).
Output Point External State Scope
Service Used
SNMP-GET on outputPointExternalState
F-4.18 Condition External Y This management function allows a managing system to condition
Output Point 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
F-4.14 Request External Y the output criteria (manual or automatic). In automatic control the
Output Point Criteria external points are driven by defined events. In manual control they
are driven by the operator.
Scope
Service Used
SNMP-GET on outputPointCriteria
F-4.15 Condition External Y the polarity of an external output point.
Output Point Polarity Scope
Service Used
SNMP-SET on outputPointPolarity
F-4.16 Request External Y the polarity of an external output point.
Output Point Polarity Scope
Service Used
SNMP-GET on outputPointPolarity
F-4.19 Condition External Y the event type associated to an output point when the
Output Point Automatic outputPointCriteria object is set to “automatic”. This event type is
Event 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
09 RELEASED
8BW 03598 0000 DSZZA 30/ 182
F-4.20 Request External Y the event type associated to an output point when the
Output Point Automatic outputPointCriteria object is set to “automatic”.
Event Scope
Service Used
SNMP-GET on:
• outputPointAutomaticEventId
• outputPointAutomaticEvent
F-4.21 Request External Y the list of events that can be associated to the external output
Output Point Automatic points when an automatic management of an output point is active.
Events List Scope
OPTICSIM-EQPT-MIB: opticsIMOutputPointAllowedEventsTable
Service Used
SNMP-GET on outputPointAllowedEvent
Function Output Point Status SN Function Description

MP
If
F-4.17 Request External Y the operational state of an external output point entry.
Output Point Operational Scope
State OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointOperationalState

Configuration for MPIf
Remotization
N This management function allows a managing system to configure
F-4.22 Creation of the external input point (identified by inputPointIndex) to be
remotization of External remotized on external output point of a specified Ne (identified by
Input Point 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.
N This management function allows a managing system to delete the
F-4.23 Deletion of remotization of the external input point (identified by
remotization of External inputPointIndex).
Input Point Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-SET on inputPointRemotizationRowStatus columnar object
to ‘destroy’ value.
N This management function allows a managing system to request
F-4.24 Request Remotization the IP address of remote NE on which the external input point have
09 RELEASED
8BW 03598 0000 DSZZA 31/ 182
Destination to be remotized as output point.
Scope
OPTICSIM-EQPT-MIB:
Service Used
SNMP-GET on inputPointRemotizationDestination
Function Input Point for SN Function Description

Remotization Status MP
If
N This management function allows a managing system to request the
F-4.25 Request status of the last remotization of the input point information on the NE
Remotization Status identified by inputPointRemotizationDestination.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-GET on inputPointRemotizationStatus
F-4.26 Request time of the last remotization tried by the local agent.
Remotization Last Update Scope
Service Used
SNMP-GET on inputPointRemotizationLastUpdate
Function Input Point for SN Function Description

Remotization Manual MP
Control If
N This management function allows a managing system to trigger a
F-4.27 Condition Manual manual updating of the destination output point (‘updating’ value).
Remotization Scope
Service Used
SNMP-SET on inputPointManualRemotization

Configuration from MP
Remote Input Point If
N This management function allows a managing system to identify the
F-4.28 Creation of remote external input point which caracteristics have to be provided
Remote External Input on local output point (identified by outputPointIndex).
Point 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
09 RELEASED
8BW 03598 0000 DSZZA 32/ 182
‘createAndGo’ value.
N This management function allows a managing system to delete the
F-4.29 Deletion of Remote configuration of local external output point (identified by
External Input Point outputPointIndex) as remote input point
Scope
Service Used
SNMP-SET on remoteInputPointRowStatus columnar object to
‘destroy’ value.
F-4.30 Request Remote IP address of agent where the remote input point is physically present
Agent and the index of the remote input point on
opticsIMExternalInputPointTable.
Scope
Service Used
SNMP-GET on
• remoteInputPointAgent
• remoteInputPointIndex

from Remote Input Point MP
Status If
F-4.31 Request Last time of the last update received from the agent concerning the status
Update from Remote of the remote input point.
Scope
Service Used
SNMP-GET on remoteInputPointLastUpdate
09 RELEASED
8BW 03598 0000 DSZZA 33/ 182
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
Creation Rules
Created
6 opticsIMExternalInputPointEntry In all the configurations
7 opticsIMExternalOutputPointEntry
1 opticsIMAuxiliaryPITTPBidEntry
1 opticsIMEowDTMFTTPBidEntry
3 opticsIMPointToPointIPEntry
1 opticsIMCtUserTable In all the configurations.
Entry related to the default administrator
user.
(note 2)
1 or 2 opticsIMCoderTTPEntry 1 entry for in all the 1+0 configurations
1 or 2 opticsIMPdhFrameHopCurrentDataEntry 2 entries in all the 1+1 configurations
1 or 2 opticsIMLoopbackEntry [IDU cable loopback]
1 or 2 opticsIMLoopbackExtEntry [IDU cable loopback]
1 opticsIMFrameTTPEntry In all the configurations
2 ifMauEntry In all the 1+0 and 1+1 ETH configurations
2 ifAutoMauEntry
2 opticsIMMauExtEntry
4 opticsIMEthConfEntry
1 opticsIMGFPConfEntry
[RPS] In all the 1+1 configurations
1 opticsIMRadioProtectionGroupEntry
2 opticsIMRadioProtectionUnitEntry
1 opticsIMRadioRxStaticDelayEntry
[EPS]
1 opticsIMEquipmentProtectionGroupEntry
2 opticsIMEquipmentProtectionUnitEntry
[PM]
1 opticsIMPdhFrameLinkCurrentDataEntry
1 opticsIMTxProtectionGroupEntry In all the 1+1 HST configurations
2 opticsIMTxProtectionUnitEntry
1 or 2 opticsIMRadioPDHTTPBidEntry 1 entry in all the 1+0 configurations
1 or 2 opticsIMRadioFrequencyEntry 2 entries in all the 1+1 configurations
1 or 2 opticsIMRadioShifterEntry (note 1)
1 or 2 opticsIMRadioTxPowerEntry
1 or 2 opticsIMRadioTxMuteEntry
1 or 2 opticsIMRadioAnalogueMeasureEntry
2 or 4 opticsIMLoopbackEntry [ODU loopbacks] 2 entry in all the 1+0 configurations
2 or 4 opticsIMLoopbackExtEntry [ODU loopbacks] 4 entries in all the 1+1 configurations
(note 1) opticsIMRadioShifterEntry is not supported on ULS 2.0.0

(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1.
09 RELEASED
8BW 03598 0000 DSZZA 34/ 182
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 [13].
Table Entry
Supported Objects
(Table/Scalar) Indexes
Configuration Description
Value
opticsIMEqptMib
opticsIMEquipmentTable See the Allowed Equipment Type section.
equipmentExpectedTypeId
equipmentExpected
equipmentActual
equipmentAdministrativeState
equipmentOperationalState
equipmentAsapIndex
equipmentLabel
opticsIMRemoteInventoryTable See the Allowed Equipment Type and Remote
remoteInventoryStatus Inventory sections.
remoteInventoryCompanyIdentifier
remoteInventoryMnemonic
remoteInventoryCLEICode
remoteInventoryPartNumber
remoteInventorySoftwarePartNumber
remoteInventoryFactoryIdentifier
remoteInventorySerialNumber
remoteInventoryDateIdentifier
remoteInventoryDate
remoteInventoryCustomerField
opticsIMEquipmentProtectionGroupTable All the 1+1 EPS 4
opticsIMEquipmentProtectionGroupType
opticsIMEquipmentProtectionGroupRevertive
opticsIMEquipmentProtectionGroupOperational
State
opticsIMEquipmentProtectionUnitTable All the 1+1 EPS – Ch#1 4; 1
opticsIMEquipmentProtectionUnitChannelNum EPS – Ch#0 4; 0
ber
opticsIMEquipmentProtectionUnitType
opticsIMEquipmentProtectionUnitSwitchComm
and
opticsIMEquipmentProtectionUnitSwitchCriteria
opticsIMEquipmentProtectionUnitSwitchStatus
opticsIMExternalInputPointTable All 1..6
inputPointUserLabel
inputPointExternalState
inputPointPolarity
inputPointAsapIndex
inputPointOperationalState
09 RELEASED
8BW 03598 0000 DSZZA 35/ 182
Table Entry
Supported Objects
Value
opticsIMExternalOutputPointTable All External output points 1..4
outputPointUserLabel
outputPointExternalState Summarizing 5..7
outputPointPolarity (see the External
outputPointCriteria Points Management
outputPointOperationalState section)
outputPointAutomaticEventId
outputPointAutomaticEvent
opticsIMOutputPointAllowedEventsTable All See the External 1..8
outputPointAllowedEvent Points Management
section.
opticsIMTribPortsImpedance
opticsIMHousekeepingAlarmRaise
opticsIMHousekeepingAlarmClear
opticsIMAlarmReplaceableUnitProblemRaise
opticsIMAlarmReplaceableUnitProblemClear
opticsIMAlarmReplaceableUnitMissingRaise
opticsIMAlarmReplaceableUnitMissingClear
opticsIMAlarmReplaceableUnitTypeMismatchRai
se
opticsIMAlarmReplaceableUnitTypeMismatchCle
ar
opticsIMAlarmUnconfiguredEquipmentPresentR
aise
opticsIMAlarmUnconfiguredEquipmentPresentCl
ear
opticsIMAlarmVersionMismatchRaise
opticsIMAlarmVersionMismatchClear
opticsIMAlarmLanFailureRaise
opticsIMAlarmLanFailureClear
opticsIMAlarmStandByVersionMismatchRaise
opticsIMAlarmStandByVersionMismatchClear
opticsIMAlarmFirmwareDownloadOnGoingRaise
opticsIMAlarmFirmwareDownloadOnGoingClear
09 RELEASED
8BW 03598 0000 DSZZA 36/ 182
4 TRANSMISSION INTERFACES (IFTABLE)
The following table defines the transmission interface types supported and managed in the ifTable.
Interface Interface ifTable

Type Number ifDescr ifType ifSpeed
E1 Tx up to 16 E1 – PPI 18 (note 1) 2 048 000
E3 Tx up to 1 E3 – PPI 30 34 368 000
DS1 Tx (note 4) up to 16 DS1 - PPI 18 1 544 000
DS3 Tx (note 4) up to 1 DS3 -PPI 30 44 736 000
Ethernet Tx up to 2 Ethernet 6 10 000 000 / 100 000 000
39 168 000 (E3, 16E1)
19 584 000 (8 E1)
9 792 000 (4 E1)
4 896 000 (2 E1)
57 120 000 (DS3)
Radio PDH Frame
up to 2 PDH Radio 1 (other) (note 4)
(note 2)
28 560 000 (16DS1)
(note 4)
14 280 000 (8 DS1)
(note 4)
7 140 000 (4 DS1)
(note 4)
V11 64 64 000
Auxiliary (note 3) 1
G703 66 64 000
3 PPP 23 64 000
Management Interfaces 1 Local Ethernet 6 10 000 000 / 100 000 000
1 LAPD 77 38 400
(note 1) In IANAifType-MIB the “e1” value (19) is declared obsoleted. The RFC 2495 (see [1])
doesn’t distinguish between DS1 and E1and 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) ifSpeed object is set according to the frame structure configuration.
(note 3) ifSpeed object is set according to the auxiliary interface type configuration.
(note 4) Not supported on ULS 2.0.0.
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.

The managing system can request (SNMP-GET) the value of the following ifTable objects:
• ifDescr
• ifType
• ifSpeed
09 RELEASED
8BW 03598 0000 DSZZA 37/ 182
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 [13].
The following table provides the relationship between ifIndex value and associated proprietary extension
tables.
Interface ifTable Associated Associated

Type ifIndex Mib Table
Radio PDH 20101 opticsIMRadioTrsPdhMib opticsIMRadioPDHTTPBidTable
Frame 20100 opticsIMRadioTrsCommonMib opticsIMRadioFrequencyTable
opticsIMRadioShifterTable (note 4)
opticsIMRadioTxPowerTable
opticsIMRadioAnalogueMeasuresTable
opticsIMRadioTxMuteTable
E1 Tx 1yy01 or opticsIMTrsCommonMib opticsIME1pPITTPTable
1yy99 opticsIMPdhRAIInsertionTable
(note 1)
DS1 Tx (note 4) 1yy01 or opticsIMDs1pPITTPTable
1yy99
(note 1)
E3 Tx 10101 or opticsIME3pPITTPTable
10199
(note 3)
DS3 Tx (note 4) 10101 or opticsIMDs3pPITTPTable
10199
(note 3)
1xx01 mauMod ifMauTable
Ethernet Tx
(note 2) opticsIMEthNEMib opticsIMMauExtTable
Auxiliary 301 opticsIMOverheadMib opticsIMAuxiliaryPITTPBidTable
PPP-RF 1 opticsIMCommRouMib opticsIMPointToPointIPTable
PPP-V11 2
PPP-G703 3
Local Ethernet 100 opticsIMLocalEthernetTable
LAPD/F 200 - -
09 RELEASED
8BW 03598 0000 DSZZA 38/ 182
(note 1) yy = 01..16; 1yy01 in case of 1+0 configurations, 1yy99 in case of 1+1 configurations.
(note 2) xx = 17..18
(note 3) 10101 in case of 1+0 configurations, 10199 in case of 1+1 configurations.
09 RELEASED
8BW 03598 0000 DSZZA 39/ 182
5 SDH/PDH TRANSMISSION DOMAIN

1+1 Configurations Functional View
Tx Functional View
Aggregate Radio Ch#1

(source) (source)
<trib>-TX <trib>-RX MUX

(sink) (source) (source)

(source) (source)
Rx Functional View

(sink) (sink)
<trib>-TX <trib>-RX DEMUX

(source) (sink) (sink)
Aggregate Radio
(sink) Ch#0
(sink)
RPS hitless
A bi-directional EPS protection scheme is always supported in all the 1+1 configurations.
The mapping between the functional blocks indicated in the functional views above and SNMP MIB
tables is the following:
• <trib>-TX => opticsIME1pPITTPTable

opticsIME3pPITTPTable
opticsIMDS1pPITTPTable (note 1)
• <trib>-RX => opticsIME1PathTTPTable
opticsIME3PathTable
opticsIMDS1PathTTPTable (note 1)
• MUX, DEMUX => opticsIMFrameTTPTable
• Aggregate => opticsIMCoderTTPTable
• Radio => opticsIMRadioPDHTTPBidTable
N.B. SNMP tables are created only if necessary from management point of view.
09 RELEASED
8BW 03598 0000 DSZZA 40/ 182
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 and 4DS1 frame structure configurations cannot be associated to 16 QAM
modulation.
Market NE Allowed Frame

Type Configurations Structures
ETSI All the Radio configurations 8E1/DS1
twoE1, fourE1, eightE1
(without Ethernet interface)
All the Radio configurations 8E1/DS1 (with
twoE1, fourE1, eightE1, sixteenE1
Ethernet interface)
All the Radio configurations 16E1/DS1 twoE1, fourE1, eightE1, sixteenE1
All the Radio configurations E3/DS3 oneE3
ANSI All the Radio configurations 8E1/DS1
fourDS1, eightDS1
(note 1) (without Ethernet interface)
All the Radio configurations 8E1/DS1 (with fourDS1, eightDS1, sixteenDS1,
Ethernet interface) oneDS3
All the Radio configurations 16E1/DS1 fourDS1, eightDS1, sixteenDS1
All the Radio configurations E3/DS3 oneDS3
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.
Frame Structure NE
Functional Objects Created
Configuration Configurations
twoE1 All the Radio configurations 2 opticsIME1pPITTPEntry
8E1/DS1 or 16E1/DS1 2 opticsIMPdhRAIInsertionEntry (note 1)
2 opticsIME1PathTTPEntry
2 opticsIMPdhRAIInsertionEntry (note 2)
fourE1 All the Radio configurations 4 opticsIME1pPITTPEntry
eightE1 All the Radio configurations 8 opticsIME1pPITTPEntry
sixteenE1 All the Radio configurations 8 opticsIME1pPITTPEntry
8E1/DS1 (with Ethernet interface) 8 opticsIMPdhRAIInsertionEntry (note 1)
All the Radio configurations 16 opticsIME1pPITTPEntry
16E1/DS1 16 opticsIMPdhRAIInsertionEntry (note 1)
09 RELEASED
8BW 03598 0000 DSZZA 41/ 182
Frame Structure NE
Functional Objects Created
Configuration Configurations
oneE3 All the Radio configurations 1 opticsIME3pPITTPEntry
E3/DS3 1 opticsIME3PathTTPEntry
fourDS1 (note 1) All the Radio configurations 4 opticsIMDs1pPITTPEntry
8E1/DS1 or 16E1/DS1 4 opticsIMDs1PathTTPEntry
eightDS1 (note 3) All the Radio configurations 8 opticsIMDs1pPITTPEntry
8E1/DS1 or 16E1/DS1 8 opticsIMDs1PathTTPEntry
sixteenDS1 (note All the Radio configurations 8 opticsIMDs1pPITTPEntry
3) 8E1/DS1 (with Ethernet interface) 8 opticsIMDs1PathTTPEntry
All the Radio configurations 16 opticsIMDs1pPITTPEntry
16E1/DS1 16 opticsIMDs1PathTTPEntry
oneDS3 (note 3) All the Radio configurations 1 opticsIMDs3pPITTPEntry
E3/DS3 1 opticsIMDs3PathTTPEntry
N.B.: The naming of the objects above depend on the configuration. See the ifIndex values in the naming
rule section.
(note 1) pdhRAIInsertionSignalType object = e1pPI
(note 2) pdhRAIInsertionSignalType object = e1Path
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
Loopback Objects Created
Created
x pPITTP y opticsIMLoopbackEntry
(note 1) y opticsIMLoopbackExtEntry
x PathTTP y opticsIMLoopbackEntry
(note 1) y opticsIMLoopbackExtEntry
(note 1) y = up to 16 in case of E1 or DS1 (DS1 not on ULS 2.0.0), y = 1 in case of E3 or DS3 (DS3
not on ULS 2.0.0.
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.
DS1 Line Length Management (not supported on ULS 2.0.0)
In order to make easier the configuration of the line lenght from operator point of view, the manager has
to provide to the agent not the length expressed in feet but an integer value that identify the line length
range required by the operator.
The relationship between the integer value at SNMP interface and the line length range is described in
the following table.
09 RELEASED
8BW 03598 0000 DSZZA 42/ 182
‘opticsIMDs1Line
Range
Lenght’ value
0 0-133 ft
1 133-266 ft
2 266-399 ft
3 399-533 ft
4 533-655 ft
09 RELEASED
8BW 03598 0000 DSZZA 43/ 182
The following table lists the SDH/PDH Transmission management functions supported in this release
(see [6]).
N.B. The management functions related to the DS1/DS3 signal are not supported on ULS 2.0.0.
Generic Trail Termination Point Functions

MP
If
F-1.1 Request TTP ASAP Y the ASAP Pointer associated to a trail termination point.
Pointer 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 Y configure the ASAP Pointer associated to a trail termination point.
Pointer Scope
(xTTPBidTable)
Service Used
SNMP-SET on: xTTPBidAsapIndex columnar object
Note F-1.2: Supported on the TPs managed in this release.
Function TP Status SN Function Description

MP
If
F-1.3 Request TTP Y request the operational state of a trail termination point.
(xTTPBidTable)
Service Used
SNMP-GET on xTTPBidOperationalState columnar object
SDH Functions
Trail Termination Point

MPI
f
09 RELEASED
8BW 03598 0000 DSZZA 44/ 182
F-1.xx All the functions N
Function Notifications SN Function Description

MPI
f
Automatic Laser Shutdown
Functions SN Function Description

MPI
f
PDH Frame Functions
Function Configurations SN Function Description

MPI
f
F-2.1 Request Frame Y request the configuration of the frame structure.
Structure Configuration Scope
OPTICSIM-TRS-PDH-MIB:
opticsIMFrameStructureConfiguration
Service Used
SNMP-GET on the scalar object
This management function allows the managing system to set the
F-2.2 Condition Frame Y configuration of the frame structure.
Structure Configuration Scope
OPTICSIM-TRS-PDH-MIB:
Service Used
SNMP-SET on the scalar object
F-2.3 Request Link Identifier N request the value of the parameters related to the Link Identifier
Parameters 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
09 RELEASED
8BW 03598 0000 DSZZA 45/ 182
scalar object.
• The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
• The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMLinkldExpectedMode
• opticsIMLinkIdExpectedValue
• opticsIMLinkIdSentValue
F-2.4 Condition Link N condition the parameters related to the Link Identifier
Identifier Parameters management:
• The expected mode on the receiving NE
(opticsIMLinkldExpectedMode).
• The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
• The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-SET on:
• opticsIMLinkldExpectedMode
• opticsIMLinkIdExpectedValue
• opticsIMLinkIdSentValue
Note F-2.4: Allowed values: 0-15.
F-2.5 Condition BER Alarms N thresholds used to raise the highBER and lowBER alarms. Both
Thresholds these values must be included in the related allowed range. The
high BER threshold must be greater than the low BER one.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-SET on the following scalar objects:
• opticsIMHighBERThr
• opticsIMLowBERThr
F-2.6 Request BER Alarms N request the thresholds used to raise respectively a PDH highBER
Thresholds and lowBER alarms.
Scope
Service Used
• opticsIMHighBERThr
• opticsIMLowBERThr
F-2.7 Request BER Alarms N request the minimum and maximum values allowed for the
Thresholds Ranges thresholds used to raise the PDH highBER and lowBER alarms.
Scope
Service Used
• opticsIMHighBERMinThr
• opticsIMHighBERMaxThr
09 RELEASED
8BW 03598 0000 DSZZA 46/ 182
• opticsIMLowBERMinThr
• opticsIMLowBERMaxThr
F- 2.11 Request interleaving N This management function allows the managing system to
status request the status of interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB
Service Used
SNMP-GET on the following scalar object opticsIMInterleaving.
F- 2.12 Condition N This management function allows the managing system to
interleaving function enable/disable the interleaving functionality.
Scope
OPTICSIM-TRS-PDH-MIB
Service Used
SNMP-SET on the following scalar object opticsIMInterleaving.
F- 2.13 Condition EW alarm N This management function allows the managing system to set the
BER Thresholds BER threshold used to raise the EW alarm. This value must be
included in the allowed range.
Scope
Service Used
• opticsIMEWBERThr
F- 2.14 Request EW alarm N This management function allows the managing system to
BER Thresholds request the BER thresholds used to raise a EW alarm.
Scope
Service Used
• opticsIMEWBERThr
F- 2.15 Request EW alarm N This management function allows the managing system to
BER Thresholds Ranges request the minimum and maximum values allowed for the BER
thresholds used to raise EW alarm.
Scope
Service Used
• opticsIMEWBERMinThr
• opticsIMEWBERMaxThr

MPI
f
F-2.9 Report PDH Frame Y transmission alarms related to the PDH frame.
Alarms Scope
OPTICSIM-TRS-PDH-MIB: opticsIMFrameTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmLossOfFrameRaise
• opticsIMAlarmLossOfFrameClear
• opticsIMAlarmLinkIdentifierMismatchRaise
• opticsIMAlarmLinkIdentifierMismatchClear
F-2.10 Report PDH Coder Y transmission alarms related to the PDH coder.
Alarms Scope
09 RELEASED
8BW 03598 0000 DSZZA 47/ 182
OPTICSIM-TRS-PDH-MIB: opticsIMCoderTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmCableLOSRaise
• opticsIMAlarmCableLOSClear
• opticsIMAlarmHighBERRaise
• opticsIMAlarmHighBERClear
• opticsIMAlarmLowBERRaise
• opticsIMAlarmLowBERClear
PDH Tributaries Functions

MP
If
F-3.1 Request E1 Signal Y which processing mode is activated on an E1 signal.
Processing Mode Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
Service Used
SNMP-GET on e1pPITTPSignalMode
This management function allows a managing system to condition
F-3.2 Condition E1 Signal P the E1 signal processing mode. The allowed signal processing
Processing Mode 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 N whether a CRC indication (multiframe presence) is detected on a
Status E1 signal when the processing of a framed signal is activated.
Scope
opticsIME1PathTTPTable
Service Used
SNMP-GET on (respectively):
e1pPITTPFrameStatus
e1PathTTPFrameStatus
F-3.4 Request RAI Insertion Y the status of the RAI insertion in a E1 or DS3 framed signal.
Status Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMPdhRAIInsertionTable
Service Used
SNMP-GET on:
• pdhRAIInsertionSignalType
09 RELEASED
8BW 03598 0000 DSZZA 48/ 182
• pdhRAIInsertionStatus
Note F-3.4: Supported only on E1 signals (pPI and Path).

F-3.5 Condition RAI Insertion Y the RAI insertion inhibition in a E1 or DS3 framed signal, both
Status physical interface and path side. The status allowed are the
following:
• enabled
• inhibited
• forced
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMPdhRAIInsertionTable
Service Used
SNMP-SET on pdhRAIInsertionStatus
Note F-3.5: Supported only on E1 signals (pPI and Path). Values supported:
• enabled
• forced
F-3.8 Request E3 Signal Y which processing mode is activated on a E3 signal.
Service Used
SNMP-GET on e3pPITTPSignalMode
F-3.9 Condition E3 Signal Y the E3 signal processing mode. The allowed signal processing
Processing Mode 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 Signal Y which processing mode is activated on a DS1 signal.
OPTICSIM-TRS-COMMON-MIB: opticsIMDs1pPITTPTable
Service Used
SNMP-GET on ds1pPITTPSignalMode
F-3.11 Condition DS1 Signal Y the processing mode of a DS1 signal. The allowed signal
Processing Mode 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
F-3.12 Request DS3 Signal Y which processing mode is activated on a DS3 signal.
09 RELEASED
8BW 03598 0000 DSZZA 49/ 182
Service Used
SNMP-GET on ds3pPITTPSignalMode
F-3.13 Condition DS3 Signal Y the processing mode of a DS3 signal. The allowed signal
Processing Mode processing modes are:
• disabled
• unframed
• framed (G.704)
Scope
Service Used
SNMP-SET on ds3pPITTPSignalMode
F-3.14 Request DS1 Line Y the line coding of a DS1 signal.
Coding Scope
Service Used
SNMP-GET on ds1pPITTPLineCoding
F-3.15 Condition DS1 Line Y the line coding of a DS1 signal. The allowed values are the
Coding following:
• AMI
• B8ZS
Scope
Service Used
SNMP-SET on ds1pPITTPLineCoding
This management function allows a managing system to specify,
F-3.16 Condition Global DS1 N in one shot, the code for all the DS1 lines.
Line Coding Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs1LineCoding
Service Used
SNMP-SET on the scalar opticsIMAllDs1LineCoding
F-3.17 Request DS1 Line Y the length of a DS1 line. It provides information for Line Build Out
Length circuitry.
Scope
Service Used
SNMP-GET on ds1pPITTPLineLength
F-3.18 Condition DS1 Line Y the length of a DS1 line.
Length Scope
Service Used
SNMP-SET on ds1pPITTPLineLength
F-3.19 Condition Global DS1 N condition, in one shot, the length of all the DS1 lines.
Line Length Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs1LineLength
Service Used
SNMP-SET on the scalar object opticsIMAllDs1LineLength
F-3.25 Request DS1 Line Y the ranges of Ds1 line lengths allowed on NE.
Length Allowed Ranges Scope
OPTICSIM-TRS-COMMON-MIB:
opticsIMAllowedDS1LineLengthsTable
09 RELEASED
8BW 03598 0000 DSZZA 50/ 182
Service Used
SNMP-GET on
• allowedLineLengthId
• allowedLineLengthMin
• allowedLineLengthMax
F- 3.33 Request E1/DS1 AIS N This management function allows a managing system to request
Signal Type which AIS Signal type (allOnes or AllZeroes) is activated on an
E1 signal or on DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-GET on e1pPITTPAISSignalType
(opticsIME1pPITTPTable) or ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
F- 3.34 Condition E1/DS1 AIS N This management function allows a managing system to condition
Signal Type which AIS Signal type (allOnes or AllZeroes) is activated on an
E1 signal or on an DS1 signal.
Scope
Service Used
SNMP-SET on: e1pPITTPAISSignalType
(opticsIME1pPITTPTable) or ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
F- 3.35 Condition Global N This management function allows a managing system to
E1/DS1 AIS Signal Type 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.
F- 3.36 Request E1/DS1 pPI N This management function allows a managing system to request
AIS Insertion 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)
F- 3.37 Condition E1/DS1 pPI N This management function allows a managing system to
AIS Insertion 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).
E1/DS1 pPI AIS Insertion 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
09 RELEASED
8BW 03598 0000 DSZZA 51/ 182
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion
F- 3.39 Request E1/DS1 Path N This management function allows a managing system to request
AIS Insertion if insertion of AIS Signal is activated on 2 Mbit/s or 1,5 Mbit/s
path.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable
Service Used
SNMP-GET on e1PathTTPAISInsertion
(opticsIME1PathTTPTable) or ds1PathTTPAISInsertion
(opticsIMDS1PathTTPTable).
F- 3.40 Condition E1/DS1 N This management function allows a managing system to
Path AIS Insertion enable/disable the AIS Signal insertion for 2 Mbit/s or 1,5 Mbit/s
path.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable,
opticsIMDS1PathTTPTable.
Service Used
SNMP-SET on e1PathTTPAISInsertion
(opticsIME1PathTTPTable) or ds1PathTTPAISInsertion
(opticsIMDS1PathTTPTable).
E1/DS1 Path AIS Insertion condition, in one shot, the AIS Signal insertion for all the 2 Mbit/s
or 1,5 Mbit/s paths.
Scope
Service Used
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion.
F- 3.42 Request DS3 AIS N This management function allows a managing system to request
Signal Type which AIS Signal type (allOnes or blueSignal) is activated on an
DS3 signal. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPAISSignalType
F- 3.43 Condition DS3 AIS N This management function allows a managing system to condition
Signal Type which AIS Signal type (allOnes or blueSignal) is activated on an
DS3 signal. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPAISSignalType
F- 3.44 Condition Global DS3 N This management function allows a managing system to
AIS Signal Type 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
F- 3.45 Request DS3 pPI AIS N This management function allows a managing system to request
Insertion if insertion of AIS Signal is activated on 45 Mbit/s PDH trails. It is
applicable only on framed signal.
Scope
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 52/ 182
SNMP-GET on ds3pPITTPAISInsertion
F- 3.46 Condition DS3 pPI N This management function allows a managing system to
AIS Insertion 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.
pPI AIS Insertion condition, in one shot, the AIS Signal insertion for all the 45 Mbit/s
PDH trails. It is applicable only on framed signals.
Scope
Service Used
SNMP-SET on the scalar object opticsIMAllDs3pPIAISInsertion
F- 3.48 Request DS3 Path AIS N This management function allows a managing system to request
Insertion if insertion of AIS Signal is activated on 45 Mbit/s path. It is
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-GET on ds3PathTTPAISInsertion.
F- 3.49 Condition DS3 Path N This management function allows a managing system to
AIS Insertion enable/disable the AIS Signal insertion for 45 Mbit/s path. It is
Scope
Service Used
SNMP-SET on ds3PathTTPAISInsertion.
Path AIS Insertion condition, in one shot, the AIS Signal insertion for all the 45 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 N This management function allows a managing system to request
Signal Timing the time to wait before to insert an AIS signal (after failure
detection) and the time to wait to remove an AIS signal (after the
failure clear) on 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.
F- 3.52 Condition DS3 AIS N This management function allows a managing system to condition
Signal Timing the time to wait before to insert an AIS signal (after failure
detection) and the time to wait to remove an AIS signal (after the
failure clear) on a DS3 line. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPAISSignalTiming
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
09 RELEASED
8BW 03598 0000 DSZZA 53/ 182
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 N This management function allows a managing system to request
Parity Violation Monitoring if Parity Violation Monitoring Removing is enabled or disabled on
Removing 45 Mbit/s trail. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3pPITTPParityViolationMonitoringRemoving.
F- 3.55 Condition DS3 pPI N This management function allows a managing system to
Parity Violation Monitoring enable/disable the Parity Violation Monitoring Removing for 45
Removing Mbit/s trail. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3pPITTPParityViolationMonitoringRemoving.
pPI Parity Violation condition, in one shot, the Parity Violation Monitoring Removing
Monitoring Removing for all the 45 Mbit/s trails. It is applicable only on framed signals.
Scope
Service Used
opticsIMAllDs3pPIParityViolationMonitoringRemoving
F- 3.57 Request DS3 Path N This management function allows a managing system to request
Parity Violation Monitoring if Parity Violation Monitoring Removing is enabled or disabled on
Removing 45 Mbit/s path. It is applicable only on framed signal.
Scope
Service Used
SNMP-GET on ds3PathTTPParityViolationMonitoringRemoving.
F- 3.58 Condition DS3 Path N This management function allows a managing system to
Parity Violation Monitoring enable/disable the Parity Violation Monitoring Removing for 45
Removing Mbit/s path. It is applicable only on framed signal.
Scope
Service Used
SNMP-SET on ds3PathTTPParityViolationMonitoringRemoving.
Path Parity Violation condition, in one shot, the Parity Violation Monitoring Removing
Monitoring Removing for all the 45 Mbit/s paths. It is applicable only on framed signals.
Scope
Service Used
opticsIMAllDs3PathParityViolationMonitoringRemoving
F- 3.60 Request DS3 Idle N This management function allows a managing system to request
insertion and detection 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.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-GET on
09 RELEASED
8BW 03598 0000 DSZZA 54/ 182
• ds3pPITTPIdleInsertion
• ds3pPITTPIdleDetection
F- 3.61 Condition DS3 Idle N This management function allows a managing system to condition
insertion the idle insertion on an DS3 signal. It is applicable only on framed
signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPIdleInsertion
F- 3.62 Request DS3 Line N This management function allows a managing system to request
Bridge Status if this selected DS3 line is used to bridge and other DS3 line.
Scope
Service Used
SNMP-GET on
ds3pPITTPInputBridgeEnabled
F- 3.63 Condition DS3 Line N This management function allows a managing system to
Bridge 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
F- 3.64 Request E1/E3 N This management function allows a managing system to request
pseudo-random pattern if insertion of pseudo-random pattern is activated on tributary x
insertion (E1 or E3 signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
Service Used
SNMP-GET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable) or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
F- 3.65 Condition E1/E3 N This management function allows a managing system to condition
pseudo-random pattern the insertion of pseudo-random pattern on tributary x (E1 or E3
insertion signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
Service Used
SNMP-SET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable) or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
F-3.66 Request DS3 Line N This management function allows a managing system to request
Length the length of a DS3 line. It provides information for Line Build Out
circuitry.
Scope
Service Used
SNMP-GET on ds3pPITTPLineLength
F-3.67 Condition DS3 Line N This management function allows a managing system to condition
Length the length of a DS3 line.
09 RELEASED
8BW 03598 0000 DSZZA 55/ 182
Scope
Service Used
SNMP-SET on ds3pPITTPLineLength
F-3.68 Request DS3 Line N This management function allows a managing system to request
Length Allowed Ranges the ranges of Ds3 line lengths allowed on NE.
Scope
OPTICSIM-TRS-COMMON-MIB:
opticsIMAllowedDs3LineLengthsTable
Service Used
SNMP-GET on
• AllowedDs3LineLengthId
• AllowedDs3LineLengthMin

MP
If
F-3.20 Report PDH Physical Y transmission alarms related to PDH physical interfaces.
Interface Alarms Scope
opticsIMDs1pPITTPTable
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 transmission alarms related to PDH paths.
Alarms Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable
opticsIME3PathTTPTable
opticsIMDs1PathTTPTable
opticsIMDs3PathTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmAisRaise
• opticsIMAlarmAisClear
• opticsIMAlarmRemoteDefectIndicationRaise (E1 and DS3
only)
09 RELEASED
8BW 03598 0000 DSZZA 56/ 182
• opticsIMAlarmRemoteDefectIndicationClear (E1 and DS3
only)
F-3.22 Report PDH Loss N the loss of the PDH signals due to switch for protection of Fast
Alarm Due to Switch Ethernet signals.
Scope
Service Used
SNMP-TRAP:
• opticsIMPdhLossDueToSwitchRaise
• opticsIMPdhLossDueToSwitchClear
BER Measure Functions
Function SN Function Description

MP
If
This management function allows the managing system to create
F-3.30 Create BER Measure N a BER measure entry. The management system has to indicate in
Entry the creation request: the monitoring point which it is associated to
(indicated by means of ifIndex).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMBERMeasureTable
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
"createAndGo" value
This management function allows the managing system to delete
F-3.31 Delete BER Measure N a BER measure entry.
Entry Scope
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
"destroy" value
F-3.32 Request BER Measure N request the BER measure data related to the current observation
Data period.
Scope
Service Used
SNMP-GET on the following columnar objects:
• berMeasureElapsedTime
• berMeasureSuspectIntervalFlag
• berMeasureViolations
• berMeasureValue
09 RELEASED
8BW 03598 0000 DSZZA 57/ 182
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 [13].
Table Entry
Supported Objects
Value
opticsIMTrsCommonMib
opticsIME3pPITTPTable All the 1+0 E3 Tx port – Ch#1 10101
e3pPITTPSignalMode All the 1+1 E3 Tx port – Ch#Common 10199
e3pPITTPOperationalState
e3pPITTPAsapIndex
opticsIMDs3pPITTPTable (note 1) All the 1+0 DS3 Tx port – Ch#1 10101
ds3pPITTPSignalMode All the 1+1 DS3 Tx port – Ch#Common 10199
ds3pPITTPOperationalState
ds3pPITTPAsapIndex
opticsIME1pPITTPTable All the 1+0 E1 Tx ports – Ch#1 1xx01
e1pPITTPSignalMode (xx = 01..16)
e1pPITTPOperationalState All the 1+1 E1 Tx ports – Ch#Common 1xx99
e1pPITTPAsapIndex (xx = 01..16)
opticsIMDs1pPITTPTable (note 1) All the 1+0 DS1 Tx ports – Ch#1 1xx01
ds1pPITTPSignalMode (xx = 01..16)
ds1pPITTPLineCoding All the 1+1 DS1 Tx ports – Ch#Common 1xx99
ds1pPITTPLineLength (xx = 01..16)
ds1pPITTPOperationalState
ds1pPITTPAsapIndex
opticsIME3PathTTPTable All the 1+0 E3 Rx port – Ch#1 20101
e3PathTTPOperationalState All the 1+1 E3 Rx port – Ch#Common 20199
opticsIMDs3PathTTPTable (note 1) All the 1+0 DS3 Rx port – Ch#1 20101
ds3PathTTPOperationalState All the 1+1 DS3 Rx port – Ch#Common 20199
opticsIME1PathTTPTable All the 1+0 E1 Rx ports – Ch#1 2xx01
e1PathTTPOperationalState (xx = 01..16)
All the 1+1 E1 Rx ports – Ch#Common 2xx99
(xx = 01..16)
opticsIMDs1PathTTPTable (note 1) All the 1+0 DS1 Rx ports – Ch#1 2xx01
ds1PathTTPOperationalState (xx = 01..16)
All the 1+1 DS1 Rx ports – Ch#Common 2xx99
(xx = 01..16)
opticsIMPdhRAIInsertionTable All the 1+0 E1 Rx ports – Ch#1 1xx01;
pdhRAIInsertionSignalType e1pPI
pdhRAIInsertionStatus (xx = 01..16)
E1 Tx ports – Ch#1 2xx01;
e1Path
(xx = 01..16)
All the 1+1 E1 Rx ports – Ch#Common 1xx99;
e1pPI
(xx = 01..16)
09 RELEASED
8BW 03598 0000 DSZZA 58/ 182
Table Entry
Supported Objects
Value
E1 Tx ports – Ch#Common 2xx99;
e1Path
(xx = 01..16)
opticsIMAllowedDs1LineLenghtsTa All 0-133 ft 0
ble (note 1) 133-266 ft 1
allowedDs1LineLenghtMin 266-399 ft 2
allowedDs1LineLenghtMax 399-533 ft 3
allowedDs1LineLenghtId 533-655 ft 4
opticsIMTrsPdhMib
opticsIMFrameTTPTable All the 1+0 Radio port – Ch#1 20101
frameTTPOperationalState All the 1+1 Radio port – Ch#Common 20199
opticsIMCoderTTPTable All the 1+0 Radio port – Ch#1 20101
coderTTPOperationalState All the 1+1 Radio port – Ch#1 20101
Radio port – Ch#0 20100
opticsIMFrameStructureConfigur
ation
09 RELEASED
8BW 03598 0000 DSZZA 59/ 182
6 ETHERNET TRANSMISSION DOMAIN

This domain is significant only in case of Ethernet configurations. The Ethernet configurations are the
following:
• 1+0 8E1/DS1-ETH (PSU24 and PSU4860 and PSU2460)

• 1+1 HST 8E1/DS1-ETH (PSU24 and PSU4860 and PSU2460)
• 1+1 FD 8E1/DS1-ETH (PSU24 and PSU4860 and PSU2460).
In terms of Ethernet interface management the ULS supports the following functional layers:
• Ethernet Physical Interface Layer (MAU and ETY_T functional blocks, see [14])
• Ethernet Port Layer (ETH and EFC functional blocks, see [18])
• GFP Layer (GFP functional block, see [16].
Ethernet Physical Interface Layer
The Ethernet interfaces can be configured according to two different modalities: manual (or default type)
mode (auto-negotiation is disabled) or automatic mode (auto-negotiation is enabled). 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.
The following items resume the features supported by ULS in terms of Ethernet Physical interface
management:
• the rate (10 or 100 Mb/s) is always configurable independently from the modality (manual or
automatic)
• the directionality is always full-duplex (no carrier control mechanism is implemented to use the half-
duplex mode)
• 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.
Ethernet Port Layer
The following items resume the features supported by ULS in terms of Ethernet Port layer management:
• in case of incoming Ethernet traffic leading to exhaustion of buffers on input queues, PAUSE frames
are transmitted in order to slow down remote peer MAC layer. The Ethernet Flow Control (EFC) is
always active, both when the auto–negotiation is enabled and when it is disabled. Length of time
(number of Quanta) for which EFC asks to inhibit data frame transmission is not managed at SNMP
interface (fixed value not defined yet).
• in case of remote peer MAC layer without EFC feature, the overflow of the input queues is required
to lead 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 802.1Q
• Ethernet corrupted frames (Tx and Rx side independently) can be discarded or forwarded to the
addressed destination, according to the related SNMP manager request.
09 RELEASED
8BW 03598 0000 DSZZA 60/ 182
GFP Layer
The following items resume the features supported (or not supported) by ULS in terms of GFP
management:
• GFP payload extension header is fixed (linear extension header): two independent FE signals are
transported onto a single PDH path.
• GFP frame validity checks is not supported (optional FCS is not used)
• GFP defect handling and reporting procedures are not supported
• Rate limiting feature is not applicable to ULS NE
• Defects supported: Loss Of Frame (LOF) N.B. Only SDH is referenced as transport layer in [16], but
for ULS NE the transport layer is PDH.
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 Main ODU
MAU ETH-EFC ETH GFP MUX Aggregate Radio

(sink) (sink) (source) (source) (source) (source) (source) Ch#1
Aggregate Radio
(source) (source) Ch#0
Ext. ODU
Rx Functional View
Main/DATA Main ODU
MAU ETH-EFC ETH GFP DEMUX Aggregate Radio

(source) (source) (sink) (sink) (sink) (sink) (sink) Ch#1
Aggregate Radio
(sink) (sink) Ch#0
RPS hitless
Ext. ODU
N.B. MAU includes also the ETY_T functional block.
The mapping between the functional blocks indicated above and MIB tables is the following:
• MAU => ifMauTable, ifMauAutoNegTable, opticsIMMauExtTable

• ETH-EFC, ETH => opticsIMEthConfTable
09 RELEASED
8BW 03598 0000 DSZZA 61/ 182
• GFP => opticsIMGfpConfTable
Frame Structure Configuration with Ethernet interfaces
With the Fast Ethernet interfaces (100Base-T), the PDH transport capability is always less than the
maximum input bit rate, then a compression mechanism is supported by ULS NE, 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:
Frame Structure Number of FE Number of PDH

Configuration Tributaries
twoE1 <= 2 <= 1 E1
fourE1 <= 3 E1
eightE1 <= 7 E1
sixteenE1 <= 8 E1
oneE3 Not allowed
fourDS1 (note 1) <= 2 <= 3 DS1
eightDS1 (note 1) <= 7 DS1
sixteenDS1 (note 1) <= 8 DS1
oneDS3 (note 1) Not allowed
(note 2)
Obviously the maximum compression of the data signals is reached when the space of only one tributary
is reserved, the compression decreases if the space of more tributaries is reserved.
(note 2)
The space reserved for the data transport is 51,184 Mbit/s, using also the remaining in–frame space
(6,048 Mbit/s).
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.
In the same way the severity of alarms addressed to instances of opticsIMGFPConfTable is provided by
the ASAP configured for the instances (with the same ifIndex value or the only instance) of the
opticsIMFrameTTPTable.
09 RELEASED
8BW 03598 0000 DSZZA 62/ 182
The following table lists the Ethernet Transmission management functions supported in this release.
See [14] and [15].
6.2.1 Ethernet Physical Interface Management
Electrical Fast Ethernet - MAU Management

Activation/Deactivation MP
If
This function is used to retrieve MAU object status with 2 admitted
F-1.1 Request FE MAU Status Y 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
This function is used to explicitly activate (ifMauStatus =
F-1.6 Condition FE MAU Y “Operational”) or deactivate (ifMauStatus = “Shutdown") the MAU.
Status Scope
MAU-MIB: ifMauTable
Service Used
SNMP-SET on ifMauStatus
This function is used to retrieve the MAU Operational State.
F-1.7 Request FE MAU Y Scope
Operational State MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauMediaAvailable
Note F-1.7: Allowed values:
• available (3)
• notAvailable (4)

MP
If
This function is used to request FE MAU jack type. FE MAU always
F-1.2 Request FE MAU Jack N rely on rj45 (2) jack types.
Type Scope
MAU-MIB: ifJackTable
Service Used
SNMP-GET on ifJackType
This function is used to operate on FE MAU default type:
F-1.3 Condition FE MAU Y • dot3MauType10BaseTFD: 10BaseT full-duplex
Default Type • dot3MauType100BaseTxFD: 100BaseTx full-duplex
This operation can be performed only when the
ifAdminStatus/ifMauStatus of supporting Ethernet interface is down.
By default the 100BaseTx full-duplex operation
09 RELEASED
8BW 03598 0000 DSZZA 63/ 182
(“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.
This function is used to request FE MAU capability data with below
F-1.4 Request FE MAU Y retrieved information:
Capability Data • 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
This function is used to configure the ASAP Pointer associated to
F-1.8 Change FE MAU ASAP Y an Ethernet Interface.
Pointer Scope
OPTICSIM-ETHNE-MIB: opticsIMIfMauExtTable
Service Used
SNMP-SET on opticsIMifMauExtAsapIndex
This function is used to request the ASAP Pointer associated to an
F-1.9 Request FE MAU ASAP Y Ethernet Interface.
Pointer Scope
OPTICSIM-ETHNE-MIB: opticsIMIfMauExtTable
Service Used
SNMP-GET on opticsIMifMauExtAsapIndex
Function Notification SN Function Description

MP
If
This function is used to report a cLOS alarm.
F-1.5 Report FE MAU Alarm Y Scope
MAU-MIB: ifMauTable
Service Used
SNMP-TRAP on:
Electrical Fast Ethernet - Ety_T Management
09 RELEASED
8BW 03598 0000 DSZZA 64/ 182
MP
If
This function is used to enable (ifMauAutoNegAdminStatus =
F-2.1 Enable/Disable FE Y enabled) or disable (ifMauAutoNegAdminStatus = disabled) the
Auto-Negotiation auto-negotiation.
Scope
MAU-MIB: ifMauAutoNegTable
Service Used
SNMP-SET on ifMauAutoNegAdminStatus
This function is used to request the MAU auto-negotiation status.
F-2.2 Request FE MAU Auto- Y The retrieved information’s are:
Negotiation Status • 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 as:
• b10baseTFD (2) = 1
• b100baseTXFD (5) = 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
F-2.3 Restart FE Auto- Y default value: noRestart(2).
Negotiation Scope
Service Used
SNMP-SET on ifMauAutoNegRestart to restart(1)
This function is used to operate on the FE MAU capabilities
F-2.4 Condition FE MAU Y advertised during the auto-negotiation.
Auto-Negotiation Advertised The FE mode operations:
Capability • 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).
09 RELEASED
8BW 03598 0000 DSZZA 65/ 182
• 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) = ifMauAutoNegCapabilityBits corresponding bit
value.
• bFdxAPause(9) = ifMauAutoNegCapabilityBits corresponding bit
value.
• bFdxSPause(10) = ifMauAutoNegCapabilityBits corresponding bit
value.
• bFdxBPause(11) = ifMauAutoNegCapabilityBits corresponding bit
value.
• 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.
Scope
Service Used
SNMP-SET on ifMauAutoNegCapAdvertisedBits
Note F-2.4: Bits settable to 1:
• b10baseTFD(2)
• b100baseTXFD(5)
The other bits assume the ifMauAutoNegCapabilityBits corresponding bits values.
This function is used to retrieve the FE Jabber State.
F-2.5 Request FE MAU N Scope
Jabber State MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauJabberState
Optical Fast Ethernet - MAU Management
Not supported.
Optical Fast Ethernet - Ety_T Management
Not supported.
09 RELEASED
8BW 03598 0000 DSZZA 66/ 182
Gigabit Ethernet - MAU Management
Not supported.
Gigabit Ethernet - Ety_T Management
Not supported.
6.2.2 Ethernet Port Management
Local Ethernet Port Transmission Specification – Ety/Eth_A Management

MP
If
F-1.x All the functions N

MP
Activation/Deactivation If

MP
If
This function is used to configure Promiscuous mode when the
F-1.6 Condition Ety/Eth_A N Ethernet interface is deactivated.
Promiscuous Mode 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.
This function is used to read:
F-1.7 Request Ety/Eth_A Data P • the interface MTU;
• the interface speed;
• the interface mode (promiscuous/not promiscuous);
09 RELEASED
8BW 03598 0000 DSZZA 67/ 182
• 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.
This function allows to condition the handling of incoming errored
F-1.8 Condition Ety/Eth_A Y Ethernet frames over local Ethernet port complying with 2 possible
FCS Discard Errored Frames modes:
• “Monitoring and discarding handling mode” of incoming errored
Ethernet frames [Default Handling Mode];
• “Monitoring handling mode” of incoming Ethernet errored frames.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-SET on opticsIMEthFCSDiscardErroredFrames
This function allows to condition the Client Layer of an ISA NE local
F-1.9 Condition Ety/Eth_A N Ethernet Port in case of promiscuous mode complying with below
Ethernet Port Client Type 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
Remote Ethernet Port Transmission Specification – GFP/Eth_A Management
09 RELEASED
8BW 03598 0000 DSZZA 68/ 182
MP
If

If

MP
If
F-3.5 Request Gfp/Eth_A N • the status of an Ethernet Interface (enabled/disabled)
Ethernet Interface Status • 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
• ifLastChange
This function is used to configure Promiscuous mode when the
F-3.6 Condition Gfp/Eth_A N Ethernet interface is deactivated.
Promiscuous Mode Scope
IF-MIB: ifXTable
Service Used
SNMP-SET on ifPromiscuousMode
F-3.7 Request Gfp/Eth_A P • interface MTU;
Ethernet Configuration 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
09 RELEASED
8BW 03598 0000 DSZZA 69/ 182
• ifMtu
• ifPromiscuousMode
• ifPhysAddress
• ifConnectorPresent (fixed to FALSE)
• opticsIMEthFCSDiscardErroredFrames
• opticsIMEthClientType
Note F-3.7: Only object opticsIMEthFCSDiscardErroredFrames is supported.
This function allows to condition the handling of incoming errored
F-3.8 Condition Gfp/Eth_A Y Ethernet frames over a “GFP-based” remote Ethernet Port
FCS Discard Errored Frames 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
This function allows to condition the Client Layer of an ISA NE
F-3.9 Condition Gfp/Eth_A N “GFP-based” remote Ethernet Port (in promiscuous mode)
Ethernet Port Client Type complying with below possible modes:
• 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

MP
If
This function is used to condition the Ethernet framing used in
F-2.1 Condition Ethernet N transmission. The possible framing types
LLC/MAC Framing are:
• Ethernet V2;
• LLC/SNAP;
• 802.2/802.3.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 70/ 182
Service Used
SNMP-SET on opticsIMEthConfEncaps
This function is used to read the Ethernet framing used in
F-2.2 Request Ethernet N transmission. The possible framing types are:
LLC/MAC Framing • Ethernet V2;
• LLC/SNAP;
• 802.2/802.3.
Scope
Service Used
SNMP-GET on opticsIMEthConfEncaps
6.2.3 GFP Provider Layer Management

MP
If
Scope
F-1.x All the functions N IF-MIB: ifTable
TSDIM-TRS-MIB: opticsIMIfTable

If
Scope
F-1.x All the functions N IF-MIB: ifTable

MP
If
Scope
F-1.x All the functions N IF-MIB: ifTable, ifXTable
TSDIM-TRS-MIB: opticsIMIfTable
OPTICSIM-ETHNE-MIB: opticsIMGFPConfTable

MP
If
Scope
F-1.9 Report TSF alarm N OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMAlarmTsfRaise/Clear
Scope
F-1.10 Report LOF alarm Y OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 71/ 182
SNMP-TRAP:
• opticsIMAlarmLossOfFrameRaise/Clear
Scope
F-1.11 Report GTM alarm N OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMGfpAlarmGtmRaise/Clear
Scope
F-1.13 Report PLM alarm N OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMAlarmPlmRaise/Clear
Scope
F-1.23 Report DEGRADE N OPTICSIM-GFP-MIB: opticsIMGFPConfTable
alarm Service Used
SNMP-TRAP:
• opticsIMSdhConcDegradeRaise/Clear
6.2.4 GFP_T Management

MP
If
F- 2.1 Change GFP CSF N Scope
capability support OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-SET on opticsimGFPConfCsf with possible values:
• Disabled [Default Value]
• Bidir
• Unidir
F- 2.2 Request GFP CSF N Scope
capability support OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-GET on opticsimGFPConfCsf

MP
If
F- 2.3 Report GFP CSF N Scope
alarm OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMClientSignalFailRaise/Clear
09 RELEASED
8BW 03598 0000 DSZZA 72/ 182
The general naming rules for the Ethernet objects are defined in [13].
Table Entry
Supported Objects
Value
mauMod (from MAU-MIB)
ifMauTable All the 1+0 ETH DATA Tx ports – Ch#1 1xx01; 1
ifMauStatus All the 1+1 ETH (xx = 17..18)
ifMauMediaAvailable
ifMauDefaultType
ifMauAutoNegSupported
ifMauTypeListBits
ifMauAutoNegTable All the 1+0 ETH DATA Tx ports – Ch#1 1xx01; 1
ifMauAutoNegAdminStatus All the 1+1 ETH (xx = 17..18)
ifMauAutoNegConfig
ifMauAutoNegCapabilityBits
ifMauAutoNegCapAdvertisedBits
ifMauAutoNegCapReceivedBits
ifMauAutoNegRestart
opticsimEthNEMib
opticsIMMauExtTable All the 1+0 ETH DATA Tx ports – Ch#1 1xx01; 1
opticsIMMauExtAsapIndex All the 1+1 ETH (xx = 17..18)
opticsIMEthConfTable All the 1+0 ETH DATA Tx ports- Ch#1 1xx01

opticsIMEthFCSDiscardErroredFr All the 1+1 ETH (xx = 17..18)
ames All the 1+0 ETH DATA Rx ports- Ch#1 2xx01
All the 1+1 ETH (xx = 17..18)
opticsimGFPMib
opticsimGFPConfTable All the 1+0 ETH Radio port – Ch#1 29901
(only alarms are managed) All the 1+1 ETH
09 RELEASED
8BW 03598 0000 DSZZA 73/ 182
7 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.

Protection Group Type 1+1 hitless
Switching Type Single Ended
Restoration Criteria Revertive/Non Revertive
Switching Condition Signal Fail, HBER, , EW (note 1)
Priority Not Applicable
Operator Commands Lockout spare
(note 1) 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 HST configurations.
The following table defines the characteristics of the TPS protection scheme.

Protection Group Type 1+1
Switching Type Single Ended
Restoration Criteria Revertive / Non Revertive
Switching Condition Equipment failures Tx side
Operator Commands Lockout spare
The configuration of both these protection schemes is performed by the NE in conjunction with the
equipment provisioning process (declaration of boards).
09 RELEASED
8BW 03598 0000 DSZZA 74/ 182
Modulation
The modulation has to be considered a system parameter and then it must be configured (4 or 16 QAM)
with the same value on both the radio channels independently from the configuration.
When a managing system configures the modulation 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.
16 QAM modulation cannot be associated to 2E1 or 4DS1 frame structure configurations.

The allowed modulations are defined by a software key (Flash Card type).
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.
Radio transmission parameters in 1+1 HST configuration
In 1+1 HST configurations some radio transmission parameters must be configured with the same values
on both the radio channels. This assures that a transmission protection switch doesn’t affect the radio
transmission.
This behaviour is obtained in the following way:

• 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 HST configurations according to this behaviour are
described in the following table:
Parameter SNMP Table SNMP Object

Radio Frequency opticsIMRadioFrequencyTable radioTxFrequency
Tx Mute (Local/Remote) opticsIMRadioTxMuteTable opticsIMRadioManLocalTxMute
opticsIMRadioManRemoteTxMute
The ATPC parameters and the transmitted power (when the ATPC is disabled) have to be managed for
single channel.
Frequency Shifter Management (not supported on ULS 2.0.0)
The configuration of radio Tx frequency and radio Rx frequency is done by setting the radio Tx
frequency.
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 by ODU based on
frequency band (read from Remote Inventory).
09 RELEASED
8BW 03598 0000 DSZZA 75/ 182
In case the ODU is physically connected to PNU the list is sent by ODU to IDU and the
OpticsIMAllowedShifterEntry are created , one entry for each couple shifter value-central frequency
allowed and for each radio channel.
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.
Instead, if the ODU is not physically connected to PNU, in case of first configuration (commissioning
phase) the managing system is allowed to set the values for radioShifter and the radioCentralFrequency
objects without any constraint on opticsIMAllowedShifterTable.
Associated to each couple shifter value-central frequency (and based on frequency sub-band read from
Remote Inventory) 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).
In a few cases, the Rx frequency can be modified by the managing t inside the Rx frequency range
associated to couple shifter value-central frequency configured.
That’s just the same of the use a new shifter value not included in the predefined list.
To resume: the configuration of frequency parameters of a radio channel is done by setting in a first time
the couple ‘shifter value-central frequency’ (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-central frequency’ and Tx and Rx frequency values.
Shifter value- central frequency and Tx frequency have to be explitly configured by managing system,
while Rx frequency it is automatically calculated.
In case of IDU-ODU communication never activated , due to ODU never connected or never responding,
it’snt possible to configure shifter value (and central frequency) and Tx frequency.
In case of Shifter value (and central frequency) not configured, it’s 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), that’s allowed only to managers declared as “localct” in the related
MgrPollingManagerType object of the polling table.
An ‘IncompatibleFrequency’ alarm is raised in the following cases:

• when it’s configured a txFrequency value not included on the allowed Tx Frequency Range.
• when it’s configured a rxFrequency value not included on the allowed Rx Frequency Range.
• When it’s configured a shifter value-central frequency not included in the allowed list.
• When, on configuring a new ‘shifter value-central frequency’, the txFrequency is no longer
included on the new allowed txFrequencyRange.
An ‘IncompatibleShifter’ alarm is raised in the following cases:

• When it’s configured a shifter value-central frequency not supported by ODU installed (not
included in the allowed list known on ODU).
Tx Power Management
An ‘IncompatiblePTX’ alarm is raised on ODU in the following cases:

• when it’s configured a txPower value not included on the allowed Tx Power Range. That’s 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 send to ODU a SET-PTX request.
09 RELEASED
8BW 03598 0000 DSZZA 76/ 182
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
• The ‘incompatiblePTx’ alarm is cleared (if it is raised) on ODU in the following cases:
o on configuring an txPower (SNMP-SET on radioCurrentTxPower by F-1.20 management
function) included on the allowed Power range. The IDU send 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 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 [8]).
Radio Frequency

MP
If
F-1.1 Request Tx Radio Y the transmission radio frequency expressed in KHz.
Frequency Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioFrequencyTable
Service Used
SNMP-GET on radioTxFrequency
F-1.2 Condition Tx Radio Y condition the transmission radio frequency expressed in KHz.
Frequency Scope
Service Used
SNMP-SET on radioTxFrequency
F-1.3 Request Rx Radio Y the receive radio frequency expressed in KHz.
Frequency Scope
Service Used
SNMP-GET on radioRxFrequency
F-1.4 Request Tx Radio Y the minimum and maximum values allowed for the transmission
Frequency Range radio frequency, they are expressed in KHz.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 77/ 182
Service Used
SNMP-GET on:
• radioMinTxFrequency
• radioMaxTxFrequency
F-1.5 Condition Tx Radio N condition the minimum and maximum values allowed for the
Frequency Range transmission radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-SET on:
• radioMinTxFrequency
• radioMaxTxFrequency
F-1.6 Condition Rx Radio Y condition the receive radio frequency expressed in KHz.
Frequency Scope
Service Used
SNMP-SET on radioRxFrequency
Note F-1.6:Not supported on ULS 2.0.0
F-1.7 Request Rx Radio Y the minimum and maximum values allowed for the receive radio
Frequency Range frequency, they are expressed in KHz.
Scope
Service Used
SNMP-GET on:
• radioMinRxFrequency
• radioMaxRxFrequency
Note F-1.7:Not supported on ULS 2.0.0
F-1.8 Condition Rx Radio N condition the minimum and maximum values allowed for the
Frequency Range receive radio frequency, they are expressed in KHz.
Scope
Service Used
SNMP-SET on:
• radioMinRxFrequency
• radioMaxRxFrequency
This management function allows the managing system to check if
F-1.9 Request Return Code N Set operation on radio frequency is successful. If the Get operation
on Radio Frequency setting returns a value different than setNoError, then the Set operation on
radio frequency is unsuccessful and this value stays until a new
Set operation on radio frequency is performed. Otherwise, if the
Get operation returns setNoError, the above Set operation on radio
frequency is successful.
Scope
Service Used
SNMP-GET on radioReturnCodeFrequency
09 RELEASED
8BW 03598 0000 DSZZA 78/ 182
Tx Power and ATPC

MP
If
F-1.10 Request ATPC N if the ATPC capability is present or not.
Implemented Status Scope
OPTICSIM-RADIO-TRS-COMMON-MIB
Service Used
SNMP-GET on opticsIMRadioAtpcImplemented
F-1.11 Request ATPC Activity Y the status of the ATPC activity: enabled or disabled.
Scope
Service Used
SNMP-GET on radioAtpcEnabled
F-1.12 Condition ATPC Y condition the status of the ATPC activity: enabled or disabled.
Activity 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 Y the minimum and maximum values allowed for the transmitted
Range power used by ATPC device.
Scope
Service Used
SNMP-GET on:
• radioMinAtpcTxPower
• radioMaxAtpcTxPower
F-1.14 Condition ATPC Tx Y condition the minimum and maximum values allowed for the
Range transmitted power used by ATPC device.
Scope
Service Used
SNMP-SET on:
• radioMinAtpcTxPower
• radioMaxAtpcTxPower
Note F-1.14:The ATPC working range is set within the allowed ATPC range (F-1.29).
F-1.15 Request ATPC Rx P the low and extra low power thresholds values used by the ATPC
Power Thresholds device.
Scope
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 79/ 182
SNMP-GET on:
• radioAtpcLowPowerThr
• radioAtpcExtraLowPowerThr
Note F-1.15: Only Atpc low power threshold is supported.
F-1.16 Condition ATPC Rx Y low power threshold value used by the ATPC device. This value
Low Power Threshold must be included in the related allowed range.
Scope
Service Used
SNMP-SET on radioAtpcLowPowerThr
F-1.17 Request ATPC Low Y the minimum and maximum values allowed for the low power
Power Threshold Range threshold value used by ATPC device.
Scope
Service Used
SNMP-GET on:
• radioAtpcLowPowerMinThr
• radioAtpcLowPowerMaxThr
F-1.18 Request Tx Nominal Y the tx nominal power.
Power Scope
Service Used
SNMP-GET on radioTxNominalPower
F-1.19 Request Current Tx Y the value of the transmitted power when the ATPC is disabled and
Power no manual operation on transmitted power is active.
Scope
Service Used
SNMP-GET on radioCurrentTxPower
F-1.20 Condition Current Tx Y value of the transmitted power to be used by the local transmitter
Power when the ATPC is disabled and no manual operation on
transmitted power is active.
Scope
Service Used
SNMP-SET on radioCurrentTxPower
F-1.21 Request Tx Power Y the allowed range (minimum and maximum values) of the
Range transmitted power.
Scope
Service Used
SNMP-GET on:
• radioMinTxPower
• radioMaxTxPower
09 RELEASED
8BW 03598 0000 DSZZA 80/ 182
F-1.22 Request Manual N the status (active/not active) of a manual management of the
Operation Status on Tx transmitted power.
Power Scope
Service Used
SNMP-GET on radioManOpTxPower
This management function allows the managing system to initiate /
F-1.23 Initiate/Terminate a N terminate a manual management of the transmitted power.
Manual Operation on Tx Scope
Power OPTICSIM-RADIO-TRS-COMMON-MIB:
Service Used
SNMP-SET on radioManOpTxPower
F-1.24 Request Manual N the transmitted power level when a manual management of the
Operation Tx Power Level transmitted power is active.
Scope
Service Used
SNMP-GET on radioManOpTxPowerLevel
F-1.25 Condition Manual N transmitted power level when a manual management of the
Operation Tx Power Level transmitted power is active.
Scope
Service Used
SNMP-SET on radioManOpTxPowerLevel
F-1.26 Request Atpc N the ATPC direction identifier used in the equipment configurations
Direction Identifier in which all the radio channels transmit in the same direction.
Scope
Service Used
SNMP-GET on opticsIMRadioAtpcDirectionId
F-1.27 Condition Atpc N condition the ATPC direction identifier used in the equipment
Direction Identifier configurations in which all the radio channels transmit in the same
direction. The identifier provided is used both as expected value
(sink side) and as transmitted one (source side).
Scope
Service Used
SNMP-SET on opticsIMRadioAtpcDirectionId
F-1.29 Request Allowed Y the minimum and maximum values allowed for the ATPC device
ATPC Tx Range when allowed ATPC range and allowed RTPC range are different
(see F-1.21).
Scope
Service Used
SNMP-GET on:
• radioMinAllowedAtpcTxPower
09 RELEASED
8BW 03598 0000 DSZZA 81/ 182
• radioMaxAllowedAtpcTxPower
F-1.48 Request ATPC High N the status of the ATPC in high-power mode.
Power Status Scope
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-GET on:
• radioATPCHighPowerMode
• radioATPCHighPowerTimeout
• radioATPCHighPowerTimeoutEnabled
This management function allows the managing system to lock the
F-1.49 Condition ATPC in N ATPC in high-power mode.
High Power Mode Scope
Service Used
SNMP-SET on radioATPCHighPowerMode
This management function allows the managing system to enable
F-1.137 Condition ATPC N or to disable the ATPC with timeout
enabled with timeout Scope
Service Used
SNMP-SET on radioATPCHighPowerTimeoutEnabled

MP
If
This management function allows a managed system to report an
F-1.28 Report ATPC Identifier N ATPC Identifier Mismatch alarm.
Mismatch Alarm Scope
opticsIMRadioAtpcDirectionId
Service Used
SNMP-TRAP:
- opticsIMAlarmAtpcIdentifierMismatchRaise
- opticsIMAlarmAtpcIdentifierMismatchClear
Intrusive Tx Power Control

MP
If
F-1.110 Request Radio N the number of the radio channel associated to the information
Channel Number related to the management of the transmitted power during an
Intrusive BER measurement.
Scope
opticsIMIntrusiveTPCTable
09 RELEASED
8BW 03598 0000 DSZZA 82/ 182
Service Used
SNMP-GET on intrusiveTPCRadioChannelNumber
F-1.111 Request Intrusive N the minimum and maximum levels of the transmitted power allowed
Near End Tx Power Range during an Intrusive BER measurement activated on the Far End
NE.
Scope
Service Used
SNMP-GET on:
• intrusiveTPCNearEndMinTxPower
• intrusiveTPCNearEndMaxTxPower
F-1.112 Request Intrusive Far N the minimum and maximum levels of the transmitted power allowed
End Tx Power Range 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
This management function allows the CT physically connected to
F-1.113 Request Manual N Near End NE to request the status of the control of the transmitted
Operation Status on Far End power of the corresponding Far End radio channel (TRUE if the it is
Tx Power controlled by the CT, FALSE otherwise).
Scope
Service Used
SNMP-GET on intrusiveTPCFarEndControlled
This management function allows the CT physically connected to
F-1.114 Initiate/Terminate a N Near End NE to assume the complete control of the transmitted
Manual Operation on Far End power of the corresponding Far End radio channel.
Tx Power Scope
Service Used
SNMP-SET on intrusiveTPCFarEndControlled
F-1.115 Request Manual N the transmitted power level used by the corresponding Far End
Operation Tx Power Level radio channel when an intrusive BER measurement is active.
Scope
Service Used
SNMP-GET on intrusiveTPCFarEndManOpTxPowerLevel
F-1.116 Condition Manual N transmitted power level used by the corresponding Far End radio
Operation Tx Power Level channel when an intrusive BER measurement is active.
Scope
Service Used
SNMP-SET on intrusiveTPCFarEndManOpTxPowerLevel
09 RELEASED
8BW 03598 0000 DSZZA 83/ 182
Rx Gain

MP
If
F-1.30 Request Manual N the status (active/not active) of a manual management of the gain
Operation Status on Rx Gain level.
Scope
opticsIMRadioRxGainTable
Service Used
SNMP-GET on radioManOpRxGain
This management function allows the managing system to initiate
F-1.31 Initiate/Terminate N /terminate a manual management of the gain level.
Manual Operation on Rx Gain Scope
Service Used
SNMP-SET on radioManOpRxGain
F-1.32 Request Manual N the gain level used when a manual management of the gain level is
Operation Rx Gain Level active.
Scope
Service Used
SNMP-GET on: radioManOpRxGainLevel
F-1.33 Condition Manual N condition the gain level used when a manual management of the
Operation Rx Gain Level gain level is active.
Scope
Service Used
SNMP-SET on: radioManOpRxGainLevel
F-1.34 Request Rx Gain N the allowed range (minimum and maximum values) of the gain
Range level.
Scope
Service Used
SNMP-GET on:
• radioMinRxGain
• radioMaxRxGain
F-1.35 Request Manual N the gain level related to the diversity receiver and used when a
Operation Rx Diversity Gain manual management of the gain level is active.
Level This function is applicable only in case of Space Diversity
configuration.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 84/ 182
Service Used
SNMP-GET on radioManOpRxDivGainLevel
F-1.36 Condition Manual N condition the gain level related to the diversity receiver and used
Operation Rx Diversity Gain when a manual management of the gain level is active.
Level This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-SET on radioManOpRxDivGainLevel
Analogue Measurements
Function Analogue SN Function Description

Measurements MP
If
F-1.40 Request Radio Y the number of the radio channel associated to a analog measure.
Channel Number Scope
OPTICSIM-RADIO-TRS-SDH-MIB:
Service Used
SNMP-GET on analogueMeasuresRadioChannelNumber
F-1.41 Request Local Y the measurements of the local transmitted and received power
Analogue Measurements levels.
Scope
Service Used
SNMP-GET on:
- analogueMeasuresLocalTxPower
- analogueMeasuresLocalRxMainPower
F-1.42 Request Remote Y the measurements of the remote transmitted and received power
Analogue Measurements levels.
Scope
Service Used
SNMP-GET on:
- analogueMeasuresRemoteTxPower
- analogueMeasuresRemoteRxMainPower
F-1.43 Request Local N the measures of the local received power levels related to the
09 RELEASED
8BW 03598 0000 DSZZA 85/ 182
Diversity Analogue diversity receiver.
Measurement This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-GET on analogueMeasuresLocalRxDivPower
F-1.44 Request Remote N the measures of the remote received power levels related to the
Diversity Analogue diversity receiver.
Measurement This function is applicable only in case of Space Diversity
configuration.
Scope
Service Used
SNMP-GET on analogueMeasuresRemoteRxDivPower
Radio Protection Switching

MP
If
F-1.50 Request RPS Y the type of protection (1+1 or 1:N) and if the hitless capability is
Protection Group present or not.
Configuration Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on:
• opticsIMRadioProtectionGroupType
• opticsIMRadioProtectionGroupHitless
F-1.51 Request RPS Y the current automatic restoration criteria: restoration allowed
Criteria Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupRevertive
F-1.52 Condition RPS Y automatic restoration criteria from the spare channel to the main
Automatic Restoration one when the failure clears.
Criteria This function is applicable only in case of 1+1 protection group
type.
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionGroupRevertive
09 RELEASED
8BW 03598 0000 DSZZA 86/ 182
F-1.53 Request RPS N the privileged channel. This function is applicable only in case of
Privileged Channel 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupPrivilegedChannel
This management function allows a managing system to set up the
F-1.54 Condition RPS N privileged channel. This function is applicable only in case of 1:N
Privileged Channel protection group type.
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionGroupPrivilegedChannel
F-1.55 Request RPS Extra N the extra traffic status (enabled or disabled). This function is
Traffic applicable only in case of 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupExtraTraffic
F-1.56 Condition RPS Extra N enable/disable the extra traffic. This function is applicable only in
Traffic case of 1:N protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupExtraTraffic
F-1.57 Request RPS Y the type of a protection unit: main (protected) or spare (protecting).
Protection Unit Type Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
Service Used
SNMP-GET on opticsIMRadioProtectionUnitType
F-1.58 Request RPS N the priority of a protection unit. It is applicable only in case of 1:N
Protection Unit Priority protection group type.
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionUnitPriority
F-1.59 Condition RPS N the priority of the protection unit. It is applicable only in case of 1:N
Protection Unit Priority protection group type.
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionUnitPriority
F- 1.145 Request EW alarm N This management function allows a managing system to request
Rx Power Level the absolute Received Power Level used to raise an EW alarm.
Scope
opticsIMRxPowerLevelThresholdMngt
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 87/ 182
SNMP-GET on opticsIMRxPowerLevelThr scalar object.
F- 1.146 Condition EW alarm N This management function allows a managing system to condition
Rx Power Level the absolute Received Power Level used to raise an EW alarm.
Scope
Service Used
SNMP-SET on opticsIMRxPowerLevelThr
F- 1.147 Request EW alarm N This management function allows a managing system to request
Rx Power Level Range 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
F- 1.150 Request RPS Switch N This management function allows a managing system to request if
on EW alarm Status RPS switch occurs when EW alarm raised for Rx Power Level or
BER threshold crossing, for both. If RPS switch doesn’t occur when
EW alarm raised, the ‘disabled’ value is returned.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-GET on opticsIMRadioSwitchEWEnabled scalar object.
F- 1.151 Condition RPS N This management function allows a managing system to condition
Switch on EW alarm 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
F- 1.152 Request RPS Switch N This management function allows a managing system to request if
on lowBER alarm Status RPS switch occurs when lowBER alarm raised. If RPS switch
doesn’t occur when lowBER alarm raised, the ‘disabled’ value is
returned.
Scope
Service Used
SNMP-GET on opticsIMRadioSwitchLowBEREnabled scalar
object.
F- 1.153 Condition RPS N This management function allows a managing system to condition
Switch on lowBER alarm if RPS switch has to occur when lowBER alarm raised or not.
Scope
Service Used
SNMP-SET on opticsIMRadioSwitchLowBEREnabled

Commands MP
If
09 RELEASED
8BW 03598 0000 DSZZA 88/ 182
F-1.60 Allow/Inhibit Switch of N inhibit/allow a working channel (main) to be switched to a protection
a RPS Working Channel channel (spare). If the main channel was already switched when
the Inhibit Switch is requested, it is forced back to the working
position.
noRequest syntax to remove the lockout and allow the switch, both
Scope
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(lockout/noRequest)
F-1.61 Allow/Inhibit Switch of Y inhibit/allow a protection channel (spare) to provide protection in
RPS Protection Channel the protection scheme. If the protection channel was already
providing protection for a working one when the Inhibit Switch is
position.
noRequest syntax to remove the lockout and allow any switch, both
Scope
Service Used
(lockout/noRequest)
F-1.62 Initiate/Terminate Y initiate/terminate a manual switch from a working channel (main) to
Manual Switch to RPS the protection one (spare). This command will fail if another
Protection Channel working channel has already been switched to the protection
channel (only in case of 1:N) or if the protection channel is locked
or has an automatic switch request (SF, HBER, LBER, EW) active
present.
Scope
Service Used
(manualSwitch/noRequest)
F-1.63 Initiate/Terminate Y initiate/terminate a manual switch from a protection channel (spare)
Manual Switch to a RPS to a working one (main). This management function is applicable
Working Channel only in case of 1+1 not revertive protection type. This command will
fail if the working channel has an automatic switch request (SF,
HBER, LBER, EW) active present.
Scope
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 89/ 182
F-1.64 Initiate/Terminate Y initiate/terminate a forced switch from a working channel (main) to
Forced Switch to RPS a protection one (spare). If another working channel has already
Protection Channel been automatically or manually switched to the protection one
when the initiate command is received, it is switched back to its
working channel to allow the other working channel to be switched
to the protection one.
This function will fail if another working channel is already forced
switched to the protection one.
the noRequest syntax to terminate the forced switch, both
Scope
Service Used
(forcedSwitch/noRequest)
F-1.65 Initiate/Terminate N initiate/terminate a forced switch from a protection channel (spare)
Forced Switch to a RPS to a working one (main). This management function is applicable
Working Channel only in case of 1+1 not revertive protection type.
Scope
Service Used

MP
If
F-1.66 Request RPS Y the operational state of a radio protection scheme.
Operational State OPTICSIM-RADIO-SWTC-MIB:
Service Used
SNMP-GET on opticsIMRadioProtectionGroupOperationalState
F-1.67 Request RPS Y the current state of a radio protection unit.
Service Used
SNMP-GET on:
• opticsIMRadioProtectionUnitSwitchCommand
the current state of a radio protection unit.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 90/ 182
Service Used
SNMP-GET on:
• opticsIMRadioProtectionUnitSwitchCommand
• opticsIMRadioProtectionUnitSwitchCriteria
• opticsIMRadioProtectionUnitSwitchStatus
F-1.68 Request RPS N a status will indicate if there is any mismatch between the local and
Protection Mismatch Status far-end protection type (1+1/1:N).
Scope
Service Used
SNMP-GET on opticsIMRadioProtectionGroupMismatchStatus
Function Rx Static Delay SN Function Description

Configuration MP
If
This management function allows the managing system to trigger
F-1.69 Invoke Automatic Rx Y the start of an automatic static delay alignment procedure on a
Static Delay Procedure 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
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-SET on opticsIMRadioAutoRxStaticDelayAlignment
(aligning)
This management function allows the managing system to status of
F-1.70 Request Automatic Rx N the automatic static delay alignment procedure on a protection unit:
Static Delay Procedure aligning.
Status Scope
Service Used
SNMP-GET on opticsIMRadioAutoRxStaticDelayAlignment
F-1.71 Request Delays N the number of delays inserted by the automatic Rx static delay
Inserted by Automatic Rx alignment procedure on the direct and indirect ways.
Static Delay Procedure Scope
Service Used
SNMP-GET on:
• opticsIMRadioAutoRxStaticDelayDirectWay
• opticsIMRadioAutoRxStaticDelayIndirectWay
This management function allows the managing system to initiate
F-1.72 Initiate/Terminate Y or terminate a manual management of the Rx static delay.
Manual Management of Rx Scope
Static Delay OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-SET on opticsIMRadioManRxStaticDelay
F-1.73 Request Delays Y the number of delays inserted by a manual management of the Rx
09 RELEASED
8BW 03598 0000 DSZZA 91/ 182
Inserted by a Manual static delay on the direct and indirect ways.
Management of Rx Static Scope
Delay OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-GET on:
• opticsIMRadioManRxStaticDelayDirectWay
• opticsIMRadioManRxStaticDelayIndirectWay
•This management function allows the managing system to
F-1.74 Condition Delays in Y condition the number of delays inserted by a manual management
Manual Management of Rx of the Rx static delay on the direct and indirect ways.
Static Delay Scope
Service Used
SNMP-SET on:
• opticsIMRadioManRxStaticDelayDirectWay
• opticsIMRadioManRxStaticDelayIndirectWay
Note F-1.74: the opticsIMRadioManRxStaticDelayDirectWay and
opticsIMRadioManRxStaticDelayIndirectWay values must be included in the range 0..31
Function Rx Static Delay SN Function Description

Notification MP
If
This management function allows a managed system to report a
F-1.75 Report Alignment Y loss of alignment alarm. It is addressed to the involved radio
Alarm channel (identified by a radio protection unit).
Scope
Service Used
SNMP-TRAP:
- opticsIMAlarmLossOfAlignmentRaise
- opticsIMAlarmLossOfAlignmentClear
HST Transmission Protection Switching

MP
If
F-1.80 Request TPS Y the current automatic restoration criteria: restoration allowed
Criteria Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupRevertive
F-1.81 Condition TPS Y automatic restoration criteria from the spare transmission channel
Automatic Restoration to the main one when the failure clears.
Criteria Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-SET on opticsIMTxProtectionGroupRevertive
09 RELEASED
8BW 03598 0000 DSZZA 92/ 182
F-1.82 Request TPS Y the type of a protection unit: main (protected) or spare (protecting).
Protection Unit Type Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable
Service Used
SNMP-GET on opticsIMTxProtectionUnitType

Commands MP
If
F-1.83 Allow/Inhibit Switch of Y inhibit/allow a protection channel (spare) to provide protection in
TPS Protection Channel the protection scheme. If the protection channel was already
providing protection for the working one when the Inhibit Switch is
position.
noRequest syntax to remove the lockout and allow any switch, both
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
spare protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(lockout/noRequest)
F-1.84 Initiate/Terminate Y initiate/terminate a manual switch from a working channel (main) to
Manual Switch to TPS the protection one (spare). This command will fail if the protection
Protection Channel channel is locked or has an automatic switch request active
present.
Scope
main protection unit)
Service Used
F-1.85 Initiate/Terminate Y initiate/terminate a manual switch from a protection channel to a
Manual Switch to TPS working one. This management function is applicable only in case
Working Channel of 1+1 not revertive protection type. This command will fail if the
working channel has an automatic switch request active present.
Scope
Service Used
F-1.86 Initiate/Terminate Y initiate/terminate a forced switch from a working channel to a
09 RELEASED
8BW 03598 0000 DSZZA 93/ 182
Forced Switch to TPS protection one. If another working channel has already been
Protection Channel automatically or manually switched to the protection one when the
initiate command is received, it is switched back to its working
channel to allow the other working channel to be switched to the
protection one.
According to the NE type, this function will fail if protection channel
has a failure condition.
the noRequest syntax to terminate the forced switch, both
Scope
main protection unit)
Service Used
F-1.87 Initiate/Terminate N initiate/terminate a forced switch from a protection channel to a
Forced Switch to TPS working one. This management function is applicable only in case
Working Channel of 1+1 not revertive protection type.
Scope
Service Used

MP
If
F-1.88 Request TPS Y the operational state of a HST TPS protection scheme.
Operational State OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupOperationalState
F-1.89 Request TPS Y the current state of a TPS protection unit.
Service Used
SNMP-GET on:
• opticsIMTxProtectionUnitSwitchCommand
• opticsIMTxProtectionUnitSwitchCriteria
• opticsIMTxProtectionUnitSwitchStatus
This management function allows the managed system to report
F-1.90 Report TPS Protection N any protection switch event to the managing system, such as:
Switch Event • protection switching (forced, manual or automatic switch)
• protection release (release of forced, manual or automatic
switch)
• lockout, release lockout.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 94/ 182
Service Used
SNMP-TRAP (opticsIMProtectionSwitchReporting) on:
• opticsIMTxProtectionUnitSwitchCommand
• opticsIMTxProtectionUnitSwitchCriteria
• opticsIMTxProtectionUnitSwitchStatus
Common Loss Alarm

MP
If
F-1.100 Request CLA Activity N the status of the CLA procedure activity: enabled or disabled.
Scope
Service Used
SNMP-GET on opticsIMRadioCLAEnabled
F-1.101 Condition CLA N condition the status of the CLA procedure activity: enabled or
Activity disabled.
Scope
Service Used
SNMP-SET on opticsIMRadioCLAEnabled

Commands and Status MP
If
This management function allows the managing system to reset a
F-1.103 Invoke CLA Reset N 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 N the status of the CLA procedure: active or not active.
Procedure Status Scope
Service Used
SNMP-GET on opticsIMRadioCLAStatus

MP
If
This management function allows a managed system to report a
F-1.104 Report CLA Alarm N CLA alarm. It is addressed to an equipment object supporting the
09 RELEASED
8BW 03598 0000 DSZZA 95/ 182
radio transmit function.
Scope
Service Used
SNMP-TRAP:
- opticsIMAlarmCLARaise
- opticsIMAlarmCLAClear
Tx Mute

Commands and Status MP
If
F-1.120 Request Local Y the status of the local radio transmitter in terms of mute function:
Transmitter Mute Status • 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:
• opticsIMRadioManLocalTxMute
• opticsIMRadioAutoLocalTxMute
This management function allows a managing system to mute a
F-1.121 Condition Local Y local radio transmitter.
Transmitter Mute Status Scope
Service Used
SNMP-SET on opticsIMRadioManLocalTxMute
F-1.122 Request Remote P the status of the remote radio transmitter in terms of mute function:
Transmitter Mute Status • 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
• opticsIMRadioManRemoteTxMute
• opticsIMRadioAutoRemoteTxMute
Note F-1.122: Only a manual Tx mute can be monitored.
This management function allows a managing system to mute a
F-1.123 Condition Remote Y local radio transmitter.
Transmitter Mute Status Scope
09 RELEASED
8BW 03598 0000 DSZZA 96/ 182
Service Used
SNMP-SET on opticsIMRadioManRemoteTxMute
WST&Radio Service Channels Protections Switching

MP
If
F-1.xxx All the functions N
Shifter Definition Functions

M
PIf
F- 1.140 Request Allowed Y This management function allows a managing system to request
Shifter 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
F- 1.141 Condition Shifter Y This management function allows a managing system to configure
Definition 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 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
opticsIMRadioShifterTable
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 97/ 182
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 Y This management function allows a managing system to request
and Central Frequency the shifter value and related central frequency defined for a radio
channel. This information is provided by means of shifter identifier,
shifter value and central frequency
Scope
opticsIMRadioShifterTable
Service Used
• radioShifterId
• radioShifterValue
• radioShifterCentralFrequency
Analogue Points

MP
If
F-1. xxx All the functions N
Radio SPI Common Functions

MP
If
Radio SPI Urban Haul Functions

MP
If
Radio SPI Long Haul Functions
09 RELEASED
8BW 03598 0000 DSZZA 98/ 182
MP
If
Radio Frame Complementary Overhead Functions

MP
If
Radio SDH NE Functions
Function Synchronization SN Function Description

MP
If
Radio PDH Functions

MP
If
F-3.1 Request Radio Channel Y the number of the radio channel associated to the radioPDHTTP.
Number Scope
OPTICSIM-RADIO-TRS-PDH-MIB: opticsIMRadioPDHTTPBidTable
Service Used
SNMP-GET on radioPDHTTPBidRadioChannelNumber
F-3.2 Request Modulation Y the modulation type (4 or 16 QAM) supported by a radioPDHTTP.
Type Scope
Service Used
SNMP-GET on radioPDHTTPBidModulation
F-3.3 Condition Modulation Y the modulation type (4 or 16 QAM). According to the equipment
09 RELEASED
8BW 03598 0000 DSZZA 99/ 182
Type 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
F- 3.4 Request Equalizer N This management function allows a managing system to request
Status the status of equalizer (inhibited or activated) associated to
radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidEqualizerStatus
F- 3.5 Condition Equalizer N This management function allows a managing system to inhibit or
Status activate the equalizer associated to radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidEqualizerStatus
F-3.6 Request ASAP Pointer Y the ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-GET on radioPDHTTPBidAsapIndex
F-3.7 Condition ASAP Pointer Y the ASAP Pointer associated to a radioPDHTTP.
Scope
Service Used
SNMP-SET on radioPDHTTPBidAsapIndex

MP
If
F-3.8 Request TP Operational Y the operational state of a radioPDHTTP.
State Scope
Service Used
SNMP-GET on opticsIMRadioPDHTTPBidOperationalState
F-3.9 Request ODU Service N if the ODU Service Kit is connected to the transceiver. When this
Kit Status situation is detected an Abnormal Condition indication is generated.
Scope
Service Used
SNMP-GET on opticsIMRadioPDHTTPBidOduServiceKit

MP
09 RELEASED
8BW 03598 0000 DSZZA 100/ 182
If
F-3.10 Report Radio PDH Y transmission alarm related to a radioPDHTTP.
Alarms 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
- opticsIMAlarmHighBERRaise
- opticsIMAlarmHighBERClear
opticsIMAlarmLowBERRaise
- opticsIMAlarmLowBERClear
- opticsIMAlarmEarlyWarningRaise
- opticsIMAlarmEarlyWarningClear
- opticsIMAlarmPathDistortionRaise
- opticsIMAlarmPathDistortionClear
- opticsIMAlarmRadioDADERaise
- opticsIMAlarmRadioDADEClear
- opticsIMAlarmRingBrokeRaise
- opticsIMAlarmRingBrokeClear

The general naming rules for the Radio objects are defined in [13].
Table Entry
Supported Objects
(Table/Scalar/Trap) Indexes
Value
09 RELEASED
8BW 03598 0000 DSZZA 101/ 182
Table Entry
Supported Objects
Value
opticsIMRadioTrsCommonMib
opticsIMRadioFrequencyTable All the 1+0 Radio port – Ch#1 20101
radioTxFrequency All the 1+1 Radio port – Ch#1 20101
radioRxFrequency
radioMinTxFrequency
radioMaxTxFrequency
opticsIMRadioShifterTable (note 2) All the 1+0 Radio port – Ch#1 20101
radioShifterId
radioShifterValue All the 1+1 Radio port – Ch#1 20101
radioShifterCentralFrequency Radio port – Ch#0 20100
opticsIMAllowedShifterTable (note 2) All the 1+0 Radio port – Ch#1 xx01
allowedShifterValue (xx=01..50
allowedShifterCentralFrequency max)
All the 1+1 Radio port – Ch#1 xx01
(xx=01..50
max)
Radio port – Ch#0 xx00
(xx=01..50
max)
opticsIMRadioTxPowerTable All the 1+0 Radio port – Ch#1 20101
radioAtpcEnabled All the 1+1 Radio port – Ch#1 20101
radioMinAtpcTxPower
radioMaxAtpcTxPower
radioAtpcLowPowerThr
radioAtpcLowPowerMinThr
radioAtpcLowPowerMaxThr
radioTxNominalPower
radioTxCurrentPower
radioMinTxPower
radioMaxTxPower
radioMinAllowedAtpcTxPower
radioMaxAllowedAtpcTxPower
opticsIMRadioAnalogueMeasuresTable All the 1+0 Radio port – Ch#1 20101
analogueMeasuresRadioChannelNumber All the 1+1 Radio port – Ch#1 20101
analogueMeasuresLocalTxPower
analogueMeasuresLocalRxMainPower
analogueMeasuresRemoteTxPower
analogueMeasuresRemoteRxMainPower
opticsIMRadioTxMuteTable All the 1+0 Radio port – Ch#1 20101
opticsIMRadioManLocalTxMute All the 1+1 Radio port – Ch#1 20101
opticsIMRadioAutoLocalTxMute
opticsIMRadioManRemoteTxMute
09 RELEASED
8BW 03598 0000 DSZZA 102/ 182
Table Entry
Supported Objects
Value
opticsIMAlarmAtpcLoopProblemRaise
opticsIMAlarmAtpcLoopProblemClear
opticsIMAlarmHighBERRaise (note 1)
opticsIMAlarmHighBERClear (note 1)
opticsIMAlarmEarlyWarningRaise
opticsIMAlarmEarlyWarningClear
opticsIMAlarmRxDivFailRaise
opticsIMAlarmRxDivFailClear
opticsIMAlarmIncompatibleFrequencyRaise
opticsIMAlarmIncompatibleFrequencyClear
opticsIMAlarmIncompatiblePTXRaise
opticsIMAlarmIncompatiblePTXClear
opticsIMRadioTrsPdhMib
opticsIMRadioPDHTTPBidTable All the 1+0 Radio port – Ch#1 20101
radioPDHTTPBidRadioChannelNumber All the 1+1 Radio port – Ch#1 20101
radioPDHTTPBidModulation Radio port – Ch#0 20100
radioPDHTTPBidOperationalState
radioPDHTTPBidAsapIndex
opticsIMRadioSwtcMib
opticsIMRadioProtectionGroupTable All the 1+1 1
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless
opticsIMRadioProtectionGroupRevertive
opticsIMRadioProtectionGroupOperationalState
opticsIMRadioProtectionUnitTable All the 1+1 Ch#1 1; 1
opticsIMRadioProtectionUnitType
opticsIMRadioProtectionUnitSwitchCommand
Ch#0 1; 0
opticsIMRadioProtectionUnitSwitchCriteria
opticsIMRadioProtectionUnitSwitchStatus
opticsIMTxProtectionGroupTable All the 1+1 HST 1
opticsIMTxProtectionGroupRevertive
opticsIMTxProtectionGroupOperationalState
opticsIMTxProtectionUnitTable All the 1+1 HST Ch#1 1; 1
opticsIMTxProtectionUnitType Ch#0 1; 0
opticsIMTxProtectionUnitSwitchCommand
opticsIMTxProtectionUnitSwitchCriteria
opticsIMTxProtectionUnitSwitchStatus
opticsIMRadioRxStaticDelayTable All the 1+1 Ch#Common 1; 99
opticsIMRadioAutoRxStaticDelayAlignment
opticsIMRadioManRxStaticDelay
opticsIMRadioManRxStaticDelayDirectWay
opticsIMRadioManRxStaticDelayIndirectWay
(note 1) These alarm notifications are defined in the Radio domain but the related defects are detected
by the Main and Extension units (IDU).
09 RELEASED
8BW 03598 0000 DSZZA 103/ 182
8 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.0) the value of sysDescr is the following: V0200xx (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.
The following table provides the list of NE configurations supported in this release with the values of the
opticsIMAllowedNeConfigurationType and opticsIMAllowedNeConfigurationId objects .
‘OpticsIMAllowedNe ‘OpticsIMAllowedNe
Main Allowed
ConfigurationType’ ConfigurationId’
Configuration Types
value value
Undefined UNDEFINED 255
1+0 1+0 8E1/DS1 (PSU24) 1
1+0 8E1/DS1 (PSU4860) 2
1+0 8E1/DS1 (PSU2460) (note 1) 25
1+0 16E1/DS1 (PSU24) 3
1+0 16E1/DS1 (PSU4860) 4
1+0 16E1/DS1 (PSU2460) (note 1) 26
1+0 E3/DS3 (PSU24) 5
1+0 E3/DS3 (PSU4860) 6
1+0 E3/DS3 (PSU2460) (note 1) 27
1+0 8E1/DS1-ETH (PSU24) 7
1+0 8E1/DS1-ETH (PSU4860) 8
1+0 8E1/DS1-ETH (PSU2460) (note 1) 28
1+1 HST 1+1 HST 8E1/DS1 (PSU24) 9
1+1 HST 8E1/DS1 (PSU4860) 10
1+1 HST 8E1/DS1 (PSU2460) (note 1) 29
1+1 HST 16E1/DS1 (PSU24) 11
1+1 HST 16E1/DS1 (PSU4860) 12
1+1 HST 16E1/DS1 (PSU2460) (note 1) 30
09 RELEASED
8BW 03598 0000 DSZZA 104/ 182
‘OpticsIMAllowedNe ‘OpticsIMAllowedNe
Main Allowed
ConfigurationType’ ConfigurationId’
Configuration Types
value value
1+1 HST E3/DS3 (PSU24) 13
1+1 HST E3/DS3 (PSU4860) 14
1+1 HST E3/DS3 (PSU2460) (note 1) 31
1+1 HST 8E1/DS1-ETH (PSU24) 15
1+1 HST 8E1/DS1-ETH (PSU4860) 16
1+1 HST 8E1/DS1-ETH (PSU2460) (note 1) 32
1+1 FD 1+1 FD 8E1/DS1 (PSU24) 17
1+1 FD 8E1/DS1 (PSU4860) 18
1+1 FD 8E1/DS1 (PSU2460) (note 1) 33
1+1 FD 16E1/DS1 (PSU24) 19
1+1 FD 16E1/DS1 (PSU4860) 20
1+1 FD 16E1/DS1 (PSU2460) (note 1) 34
1+1 FD E3/DS3 (PSU24) 21
1+1 FD E3/DS3 (PSU4860) 22
1+1 FD E3/DS3 (PSU2460) (note 1) 35
1+1 FD 8E1/DS1-ETH (PSU24) 23
1+1 FD 8E1/DS1-ETH (PSU4860) 24
1+1 FD 8E1/DS1-ETH (PSU2460) (note 1) 36
Table: Supported NE configurations and labels

(note 1) Not supported on ULS 2.0.0 and ULS 2.0.1.
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.
‘opticsIMSwUnitIndex’ ‘opticsIMSwUnitLabel’
value string
1 EC
2 OC-R
3 FPGA-PONTO
4 FPGA-GAIA
5 FPGA-GAIA-EXT
6 FPGA-FENICE
09 RELEASED
8BW 03598 0000 DSZZA 105/ 182
7 FPGA-MEDUSA
8 FPGA-GAIA_AE
9 FPGA-GAIA-EXT_AE
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.
In both cases the EC downloads the correct OC software version. At the end of the download the alarms
above are cleared.
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, not dependent on the configuration.
Obviously the number of software unit used on EC to download each FPGA depends on the
configuration:
• Up to 6 in case of 1+0 configurations (EC, OC-R, GAIA, GAIA–AE, PONTO and MEDUSA only in
case of Ethernet configuration)
• Up to 9 in case of 1+1 configurations (EC, OC-R, PONTO, GAIA, GAIA–AE, GAIA-EXT, GAIA-EXT-
AE, FENICE and MEDUSA only in case of Ethernet configurations).
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.
Configuration Supported
‘sysName’
value
Frame structure Modulation
4E1DS1 4QAM 2E1 4QAM

4E1 4QAM
4DS1 (note 1) 4QAM
4E1DS1 4/16QAM 2E1 4QAM
4E1 4QAM or 16QAM
4DS1 (note 1) 4QAM
8E1DS1 4QAM 2E1 4QAM
4E1 4QAM
8E1 4QAM
4DS1 4QAM
8DS1 4QAM
8E1DS1 4/16QAM 2E1 4QAM
4E1 4QAM or 16QAM
8E1 4QAM or 16QAM
4DS1 (note 1) 4QAM
09 RELEASED
8BW 03598 0000 DSZZA 106/ 182
8DS1 (note 1) 4QAM or 16QAM
4QAM 2E1 4QAM
4E1 4QAM
8E1 4QAM
16E1 4QAM
1E3 4QAM
4DS1 (note 1) 4QAM
8DS1 (note 1) 4QAM
16DS1 (note 1) 4QAM
1DS3 (note 1) 4QAM
FULL FLEXIBLE 2E1 4QAM
4E1 4QAM or 16QAM
8E1 4QAM or 16QAM
16E1 4QAM or 16QAM
1E3 4QAM or 16QAM
4DS1 (note 1) 4QAM
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.
Exception to that is for all the configuration with plug-in E3/DS3 supported only in case of ‘4QAM’ and
‘FULL FLEXIBLE’ Software keys (only with Software keys the E3 frame structure is supported).
The following table provides the list of sysName values with the NE Configuration type supported for
each value.
‘sysName’
NE Configuration Type Supported
value
4E1DS1 4QAM 1+0 8E1/DS1 (PSU24)

4E1DS1 4/16QAM 1+0 8E1/DS1 (PSU4860)
8E1DS1 4QAM 1+0 8E1/DS1 (PSU2460) (note 1)
8E1DS1 4/16QAM 1+0 16E1/DS1 (PSU24)
1+0 16E1/DS1 (PSU4860)
1+0 16E1/DS1 (PSU2460) (note 1)
1+1 HST 8E1/DS1-ETH (PSU24)
1+1 HST 8E1/DS1-ETH (PSU2460) (note 1)
1+1 HST 8E1/DS1 (PSU24)
1+1 HST 8E1/DS1 (PSU4860)
1+1 HST 8E1/DS1 (PSU2460) (note 1)
1+1 HST 16E1/DS1 (PSU24)
1+1 HST 16E1/DS1 (PSU4860)
1+1 HST 16E1/DS1 (PSU2460) (note 1)
1+1 HST 8E1/DS1-ETH (PSU2460) (note 1)
1+1 FD 8E1/DS1 (PSU24)
1+1 FD 8E1/DS1 (PSU4860)
1+1 FD 8E1/DS1 (PSU2460) (note 1)
09 RELEASED
8BW 03598 0000 DSZZA 107/ 182
1+1 FD 16E1/DS1 (PSU24)
1+1 FD 16E1/DS1 (PSU4860)
1+1 FD 16E1/DS1 (PSU2460) (note 1)
1+1 FD 8E1/DS1-ETH (PSU24)
1+1 FD 8E1/DS1-ETH (PSU4860)
1+1 FD 8E1/DS1-ETH (PSU2460) (note 1)
4QAM All
FULL FLEXIBLE
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:
‘opticsIMOffNormalDescription’
Event Type
string
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
Local manual Tx mute
Remote radio Tx mute (manual) (note 1)
Remote manual Tx mute
Rx Static Delay manual operation Rx Static Delay manual operation
(note 1) This event triggers an abnormal condition both on the NE where the transmitter is squelched
and on the NE that require 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”.
09 RELEASED
8BW 03598 0000 DSZZA 108/ 182
The following table lists the Support management functions supported in this release (see [4]).
Function Event Reporting SN Function Description

Management MP
If
This function allows a managing system to initiate reporting of
F-1. Create Event Report Y 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.
This function allows a managing system to initiate reporting of
F-2. Activate Event Report Y 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.
This function allows a managing system to terminate reporting of
F-3. Delete Event Report Y 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.
This function allows a managing system to allow and inhibit the
F-4. Allow/Inhibit Event Y reporting of events to itself. Row status object is the one involved in
Report this management: its value "notInService" means "locked",
viceversa row status as "unlocked" means "active".
Scope
This function permits to lock or unlock the state of an EFD object.
Service Used
SNMP-SET on the tsdimEFDRowStatus columnar object inside
tsdimEFDTable.
This function allows a managing system to retrieve information
F-5. Request Event Report Y 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
09 RELEASED
8BW 03598 0000 DSZZA 109/ 182
SNMP-GET on the following tsdimEFDTable columnar objects:
- tsdimEFDTrapId
- tsdimEFDOperStatus
- tsdimEFDRowStatus
This function allows a managing system to modify information
F-6. Condition Event Report Y 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
This function allows a managed system to report events to the
F-7. Report Event Y managing system.
The event reports contain at least the following mandatory
information when applicable to the specific event:
- managedObjectClass
- managedObjectInstance
- notificationIdentifier: it has to be unique at a network element
level.
- eventTime with the accuracy of one second. In case of clear of
an alarm, it will be considered as the time at which the
corresponding clearing of the fault cause has been determined by
the defect filtering process.
- specificProblems (in case of clear of alarms it has the same
value as the one present in the event sent when the alarm was
raised)
- perceivedSeverity with the value cleared in case of clear of
alarms
N.B. The Event Type or Probable Cause (in case of alarm) is

defined as the SNMP identifier of the notification.
This function applies to all managed objects capable to notify

events.
Scope
This function permits to a managed system to send all the "very
urgent events" to the managing systems. The "very urgent events"
are the ones specified in the EFD objects. Moreover a managing
system could retrieve all the events form LOGs and APT objects.
Service Used
SNMP-TRAP the events are marked as "very urgent", otherwise
SNMP-GET (into LOG and/or APT objects from managing
system)
This function allows a managed system to report alert events to the
F-8. Report Alert Event N managing system.
The alert event reports contain at least the following mandatory
09 RELEASED
8BW 03598 0000 DSZZA 110/ 182
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
F-9. Request Alert Event N configuration of the alert notification mechanism.
Configuration 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
F-10. Condition Alert Event N of the alert notification mechanism.
Configuration Scope
This function permits to a managing system to modify data related
to the time and frequency counters used by managed system in
order to send an alert notification to the managing systems.
Service Used
- tsdimAlertNotifTimeOut
- tsdimAlertNotifFreqCount
Function Event Logging SN Function Description

Management MP
If
F-11. Request Maximum Y about the notification identifier used as a unique numbering in the
Notification Identifier Value 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
F-12. Request Log Status Y 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
F-13. Request Log Size Y logs provided by the managed system.
09 RELEASED
8BW 03598 0000 DSZZA 111/ 182
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
F-14. Inhibit/Allow Logging Y 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
F-15. Request Log Records P system one or a set of log records.
Scope
This function permits to retrieve the log records stored inside the
alarm and event logs depending on which logs are supported.
Service Used
SNMP-GET of the entries in the tsdimEventLogTable,
tsdimGenEventLog and tsdimAlarmLogTable managed tables.
Note F-15: tsdimGenEventLog is not supported.
This function allows a managed system to report log state change
F-16. Report Log State Y events to the managing system.
Change Scope
This function is used by managed system in order to communicate
to managing system all the logs operational state changing.
Service Used
SNMP-TRAP tsdimStateChangeNotification on the
tsdimLogTable
Function Alarm Severity SN Function Description

Management MP
If
F-17. Request Default ASAP Y about the default severity used.
Severity 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
This function allows a managing system to modify information
F-18. Condition Default Y about the used default severity.
ASAP 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
This function allows a managing system to retrieve the next index
F-19. Request Next ASAP Y value to use in free ASAP creation.
Index Scope
This function permits to retrieve the value of the index to be used in
09 RELEASED
8BW 03598 0000 DSZZA 112/ 182
the creation of the ASAP object.
Service Used
SNMP-GET on the tsdimAlarmSevProfileIndexNext scalar
object
This function allows a managing system to define different ASAP
F-20. Create Alarm Severity Y objects.
Profile Scope
This function permits to create an ASAP object.
Service Used
SNMP-SET on the following tsdimAlarmSevProfileTable
columnar object:
- tsdimAlarmSevProfileIndex
SNMP-SET on tsdimAlarmSevProfileRowStatus columnar
object to "createAndGo" value.
This function allows a managing system to terminate different
F-21. Delete Alarm Severity Y ASAP objects.
Profile Scope
This function permits to delete an ASAP object.
Service Used
This function allows a managing system to define different <alarm
F-22. Create Alarm Severity Y severity - probableCause> attributes inside an Alarm Severity
Profile object.
Scope
This function permits to create a couple of objects used to
associate a severity to a probableCause. The probableCause is
defined as trap OID.
Service Used
SNMP-SET on the following tsdimAlarmSevTable columnar
object:
- tsdimAlarmSevProfileIndex, this has to be equal to an index
already present in the tsdimAlarmSevProfileTable
- tsdimAlarmSevTrapId
- tsdimAlarmSevSeverity
- tsdimAlarmSevSeverityNotServAff
SNMP-SET on RowStatus columnar object to "createAndGo"
value.
This function allows a managing system to terminate different
F-23. Delete Alarm Severity Y alarm severity objects.
Scope
This function permits to delete an alarm severity object.
Service Used
This function allows to managing system to retrieve all the
F-24. Request Alarm Y information related to the ASAP objects both the predefined either
Severity 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
F-25. Condition ASAP User Y associated to an ASAP entry.
Label Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
Service Used
SNMP-SET on tsdimAlarmSevProfileUserLabel
09 RELEASED
8BW 03598 0000 DSZZA 113/ 182
This management function permits to request the User Label
F-26. Request ASAP User Y associated to an ASAP entry.
Label Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
Service Used
SNMP-GET on tsdimAlarmSevProfileUserLabel
Function Alarm Summary SN Function Description

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

Condition Management - MP
If
This function allows a managing system to request the status of the
F-78. Request Abnormal Y NE in terms of abnormal conditions.
Condition Status Scope
TSDIM-SUPPORT-MIB
Service Used
SNMP-GET on the opticsIMActiveAbnCond scalar object.
This function allows a managing system to request the list of
F-79. Request Abnormal Y objects that result in an abnormal condition.
Condition Affected Objects Scope
TSDIM-SUPPORT-MIB:
opticsIMAbnCondAffectedObjectsListTable
Service Used
SNMP-GET on the opticsIMAbnCondAffectedObjectInstanceId
columnar object.
This function allows a managing system to request the description
F-95. Request Abnormal Y of an abnormal (off normal) condition.
Condition Description 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 Software Y system its NE software version in order to couple it with the backup
Version file.
Scope
This function permits to retrieve the software version managed
09 RELEASED
8BW 03598 0000 DSZZA 114/ 182
object.
Service Used
SNMP-GET on the sysDescr managed object
This function allows a managing system to define the name of the
F-29. Condition Backup File Y backup file.
Name 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
F-30. Request Backup Y value of the managing system that has activated a backup
Manager Identifier 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
F-31. Condition Backup Y identifier value for backup operation. This will permit to have only
Manager Identifier 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
F-32. Condition Restore Y system the NE software version associated to the file that will be
Software Version 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
F-33. Condition Restore File Y restore file.
Name 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
F-34. Condition Restore Y identifier value for restore operation. This will permit to have only
Manager Identifier 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
F-35. Request Restore Y value of the managing system that has activated a restore
Manager Identifier operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMRestoreRequestorAddress
managed object
F-36. Request Restore State Y system the state of the restore operation.
09 RELEASED
8BW 03598 0000 DSZZA 115/ 182
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 in-progress
F-37. Condition Restore Y state of the restore operation. A managing system has to specify
State 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
F-38. Request Backup State Y Backup operation.
Scope
This function permits to get the Backup state scalar object.
Service Used
SNMP-GET on the opticsIMBackupState managed object
Function Agent Management SN Function Description

MP
If
F-40. Request NE Installation Y system its installation type (such as 4x4 board characteristic).
Type Scope
This function permits to retrieve the NE installation type managed
object.
Service Used
SNMP-GET on the tsdimNeInstallationType managed object
F-41. Request Board N system its board position inside the shelf.
Position Scope
This function permits to retrieve the NE board position managed
object.
Service Used
SNMP-GET on the tsdimBoardPosition managed object
F-42. Request Info-Model Y system which info-model version it supports.
Version Scope
This function permits to retrieve the NE Info-model version
managed objects.
Service Used
SNMP-GET on the tsdimInfoModelVersionMajor,
tsdimInfoModelVersionMinor and
tsdimInfoModelVersionMaintenance managed objects
F-44. Request SDH NE Label Y system information about the SDH NE label configuration.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 116/ 182
This function permits to retrieve the SDH NE label managed object.
Service Used
SNMP-GET on the tsdimSdhNeLabel managed object
F-45. Condition SDH NE Y system the SDH NE label object.
Label Scope
This function permits to set the SDH NE label managed object.
Service Used
SNMP-SET on the tsdimSdhNeLabel managed object
F-86. Request Manager List N 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
F-87. Condition Manager List N 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
F-48. Request Local Access Y system information about the Craft Terminal local access control
Control State state.
Scope
This function permits to retrieve the Craft Terminal local access
control state managed object.
Service Used
SNMP-GET on the tsdimLacState managed object
F-49. Condition Local Y system the object containing the information about the Craft
Access Control State 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
F-50. Request Local Access Y system information about the Craft Terminal local access control
Control Time Out Period time out period interval.
Scope
This function permits to retrieve the Craft Terminal local access
control time out period interval managed object.
Service Used
SNMP-GET on the tsdimLacNoResponseTimeOutPeriod
managed object
F-51. Condition Local Y system the object containing the information about the Craft
Access Control Time Out Terminal local access control time out period interval.
Period 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
09 RELEASED
8BW 03598 0000 DSZZA 117/ 182
F-58. Request NE Software Y system which is its software release.
Release Scope
This function permits to retrieve the NE software release.
Service Used
SNMP-GET on the sysDescr managed object
F-59. Request NE Location Y 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
F-60. Condition NE Location Y value of a managed system.
Scope
This function permits to modify the NE location.
Service Used
SNMP-SET on the sysLocation managed object
F-61. Request NE Y system which is its subrelease value.
SubRelease Scope
This function permits to retrieve the NE subrelease.
Service Used
SNMP-GET on the sysName managed object
Note F-61: Function used to request license key information.
This management function allow the managing system to request
F-62. Request NE Allowed Y the configurations allowed for the supported NE.
Configurations Scope
TSDIM-SNMPNE-MIB:
opticsIMAllowedNeConfigurationTypeTable
Service Used
SNMP-GET on opticsIMAllowedNeConfigurationType
F-63. Request NE Y the NE configuration type. This information is provided by means of
Configuration NE configuration type identifier and associated string.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on the scalar objects:
· opticsIMNeConfigurationTypeId
· opticsIMNeConfigurationType
This management function allows the managing system to define
F-64. Condition NE Y the NE configuration type. It is defined setting the identifier
Configuration (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 Y the market (ETSI or ANSI) in which the NE is used.
Scope
TSDIM-SNMPNE-MIB
09 RELEASED
8BW 03598 0000 DSZZA 118/ 182
Service Used
SNMP-GET on opticsIMMarket
This management function allows the managing system to define

F-66. Condition Market Y the market (ETSI or ANSI) in which the NE is used.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMMarket
F-96. Request Equipment Y the NE name (it specifies NE type, configuration, frequency,
Name modulation).
Scope
TSDIM-SNMPNE-MIB: opticsIMNeConfiguration
Service Used
SNMP-GET on opticsIMNeEquipmentName
Function Software Download SN Function Description

Management MP
If
F-67. Condition Server Y the (e.g. Ftp) Server information. This information is used by the
Information 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.
This management function allows a managing system to initiate a
F-68. Initiate a Downloading Y software downloading operation.
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.
09 RELEASED
8BW 03598 0000 DSZZA 119/ 182
Service Used
SNMP-SET on the following columnar objects of
opticsIMSwdlInitTable:
- opticsImSwdlInitForcedDownload
- opticsImSwdlInitSwPkgVersion
- opticsImSwdlInitSwPkgLabel
- opticsImSwdlInitDescrName
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"ActivecreateAndGo" value.
This management function has the aim to clean up the Download
F-69. Abort/Destroy a Y operation at Agent side.
Downloading Operation It could be used both to stop an in progress download and to
destroy the row occuped.
Scope
The managing system configures to Delete the
opticsImSwdlInitRowStatus.
Service Used
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"Destroy" value.
F-70. Request Downloading Y downloading information at configurable polling expiration.
Information Scope
The managing system can retrieve the Percentage, the Total
Number of Bytes, the Current SW Unit Version and Label of the in-
progress Software Download operation.
When terminated the managing system can retrieve the Result of
previous Software Download operation, during an in-progress
Software Download the Result takes the "underDownloading"
value.
Service Used
SNMP-GET on
- opticsIMSwdlPercentage,
- opticsIMSwdlTotalBytes,
- opticsIMSwdlCurrentSwUnitVersion,
- opticsIMSwdlCurrentSwUnitLabel,
- opticsImSwdlResult.
Function Software Package SN Function Description

Management MP
If
This function allows a managing system to activate a stand-by
F-71. Activate a Stand-by Y software version which is already stored on the managed system.
Software Version 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 previuosly active is updated by the
managed system with the "stand-by" value if it was in the
"activated" status, with the value "boot" if it was in the "committed"
one.
Scope
09 RELEASED
8BW 03598 0000 DSZZA 120/ 182
TSDIM-SUPPORT-MIB: opticsIMSwPackageTable
Service Used
SNMP-SET on opticsIMSwPackageCommand columnar object
(activation or forcedActivation syntax)
Note F-71: The commitment takes place implicitly together with the activation of a software version.
This function allows a managing system to request to the managed
F-72. Request Software Y system the result of a activation command (forced or not) on a
Version Activation Result 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
This function allows a managing system to commit the current
F-73. Commit an Active N active software version on the managed system. It cannot be
Software Version 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)
This function allows a managing system to request information
F-74. Request Software Y about the software package.
Package Information Scope
Service Used
- opticsIMSwPackageCommand
- opticsIMSwPackageState
- opticsIMSwPackageActivationDate
- opticsIMSwPackageLabel
- opticsIMSwPackageVersion
- opticsIMSwPackageOperationalState
F-75. Request Software Unit Y about software units included in a software package.
09 RELEASED
8BW 03598 0000 DSZZA 121/ 182
Information Scope
TSDIM-SUPPORT-MIB: opticsIMSwUnitTable
Service Used
- opticsIMSwUnitLabel
- opticsIMSwUnitVersion
- opticsIMSwUnitSize
This function allows a managing system to request a restart of the
F-76. NE Restart Request Y managed system, using the committed software version.
Scope
TSDIM-SUPPORT-MIB
Service Used
SNMP-SET on opticsIMNERestartRequest scalar object (restart
syntax is used)
F-94. Request Equipment N about software unit running on a board identified by its equipment
Software Unit Information position.
Scope
TSDIM-SUPPORT-MIB: opticsIMEqptSwUnitTable
Service Used
- opticsIMEqptSwUnitLabel
- opticsIMEqptSwUnitVersion
Function Time Management SN Function Description

MP
If
F-80. Request NE Current Y the current time of the NE. If NTP is enabled this function is not
Time supported.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMExternalTime
F-81. Condition NE Time Y condition the time of the NE. The agent makes it instantaneously its
new own time. If NTP is enabled this function is not supported.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMExternalTime
F-82. Request NTP Status Y the current status of the NTP (enabled/disabled).
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on opticsIMNTPStatus
F-83. Condition NTP Status Y enable/disable the NTP.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMNTPStatus
F-84. Request NTP Servers Y the addresses of the NTP servers (main and spare) and the related
09 RELEASED
8BW 03598 0000 DSZZA 122/ 182
Addresses and Reachability reachability.
Scope
TSDIM-SNMPNE-MIB
Service Used
- opticsIMMainNTPServerAddress
- opticsIMSpareNTPServerAddress
- opticsIMNTPServersReachabilityStatus
F-85. Condition NTP Servers Y condition the addresses of the NTP servers (main and spare).
Addresses Scope
TSDIM-SNMPNE-MIB
Service Used
- opticsIMMainNTPServerAddress
- opticsIMServerNTPServerAddress
Function Filtering SN Function Description

Management MP
If
This management function permits to condition the HD retrieval
F-89. Condition HD Retrieval Y Time. The parameters to be configured are:
Time · 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
This management function permits to create one Filter History Data

F-90. Create Filter History Y entry. The management system has to indicate in the creation
Data Entry request:
· its own IP Address
· its own UDP Port
Scope
Service Used
SNMP-SET on opticsIMFilterHDRowStatus columnar object to
"createAndGo" value
This management function permits to delete one Filter History Data
F-91. Delete Filter History Y 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).
09 RELEASED
8BW 03598 0000 DSZZA 123/ 182
Function EPS add on SN Function Description
Management MP
If
F-xx. All the functions N

The general naming rules for the Support domain objects are defined in [13].
Table Entry
Supported Objects
Description
Value
tsdimSupportMib
tsdimEFDTable Max 5 entries 1..N
tsdimEFDDest
tsdimEFDTrapId
tsdimEFDTrapObject
tsdimEFDPort
tsdimEFDLowestForwardedSeverity
tsdimEFDIndeterminate
tsdimEFDOperStatus
tsdimEFDRowStatus
tsdimEFDManagerIndex
tsdimAlarmLogTable Max 500 entries <time>;
tsdimAlarmLogProbableCause <notifId>
tsdimAlarmLogObjectClassIdentifier
tsdimAlarmLogObjectInstanceIdentifier
tsdimAlarmLogSeverity
tsdimAlarmLogSpecificProb
tsdimAlarmLogTime
tsdimEventLogTable Max 300 entries <time>;
tsdimEventLogEventType <notifId>
tsdimEventLogObjectClassIdentifier
tsdimEventLogObjectInstanceIdentifier
tsdimEventLogTime
tsdimLogTable 1..2
tsdimLogObjectClassIdentifier
tsdimLogAdminStatus
tsdimLogOperStatus
tsdimLogMaxSize
09 RELEASED
8BW 03598 0000 DSZZA 124/ 182
Table Entry
Supported Objects
Description
Value
tsdimAPTTable Max 60 entries <time>;
tsdimAPTAlarmProbableCause <notifId>
tsdimAPTAlarmObjectClassIdentifier
tsdimAPTAlarmObjectInstanceIdentifier
tsdimAPTAlarmSeverity
tsdimAPTAlarmSpecificProb
tsdimAPTAlarmTime
tsdimAlarmSevProfileTable ASAP#1 (predefined) 1
tsdimAlarmSevProfileRowStatus ASAP#2 (predefined) 2
tsdimAlarmSevProfileUserLabel
ASAP#3 (predefined) 3
ASAP#4 (predefined) 4
Free use ASAPs 5..N
(max 3 entries)
tsdimAlarmSevTable ASAP#1 (predefined) 1; <trapId>
tsdimAlarmSevSeverity ASAP#2 (predefined) 2; <trapId>
tsdimAlarmSevRowStatus
ASAP#3 (predefined) 3; <trapId>
tsdimAlarmSevSeverityNotServAff
ASAP#4 (predefined) 4; <trapId>
Free use ASAPs 5..N; <trapId>
(max 3 entries)
opticsIMSwdlInitTable 1
opticsIMSwdlInitForcedDownload
opticsIMSwdlInitSwPkgVersion
opticsIMSwdlInitSwPkgLabel
opticsIMSwdlInitDescrName
opticsIMSwdlInitRowStatus
opticsIMSwPackageTable 1..2
opticsIMSwPackageCommand
opticsIMSwPackageActivationResult
opticsIMSwPackageActivationDate
opticsIMSwPackageCurrentState
opticsIMSwPackageLabel
opticsIMSwPackageVersion
opticsIMSwPackageOperationalState
opticsIMSwUnitTable EC software unit 1; 1
opticsIMSwUnitLabel 2; 1
opticsIMSwUnitVersion
OC-R software unit 1; 2
opticsIMSwUnitSize
2; 2
FPGA-PONTO software unit 1; 3
2; 3
FPGA-GAIA software unit 1; 4
2; 4
FPGA-GAIA-EXT software unit 1; 5
2; 5
FPGA-FENICE software unit 1; 6
2; 6
FPGA-MEDUSA software unit 1; 7
2; 7
opticsIMAbnCondAffectedObjectListTable Max 50 entries 1..N
opticsIMAbnCondAffectedObjectInstanceId
opticsIMOffNormalDescription
09 RELEASED
8BW 03598 0000 DSZZA 125/ 182
Table Entry
Supported Objects
Description
Value
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
tsdimLacTable 1
tsdimLacState
tsdimLacNoResponseTimeOutPeriod
opticsIMAllowedNeConfigurationTypeTable Undefined configuration 255
opticsIMAllowedNeConfigurationType Scalable configurations 1..36
09 RELEASED
8BW 03598 0000 DSZZA 126/ 182
Table Entry
Supported Objects
Description
Value
tsdimSnmpAgtIpAddress (note 1)
tsdimSnmpAgtIpMask (note 1)
tsdimSnmpAgtUdpPort (note 1)
tsdimNeInstallationType
tsdimSdhNeLabel
tsdimInfoModelVersionMajor
tsdimInfoModelVersionMinor
tsdimInfoModelVersionMaintenance
opticsIMNeConfigurationType
opticsIMNeConfigurationTypeId
opticsIMMarket
opticsIMExternalTime
opticsIMNTPStatus
opticsIMMainNTPServerAddress
opticsIMSpareNTPServerAddress
opticsIMNTPServersReachabilityStatus
opticsIMAlarmLossOfSignalRaise
opticsIMAlarmLossOfSignalClear
opticsIMAlarmLossOfFrameRaise
opticsIMAlarmLossOfFrameClear
opticsIMAlarmAisRaise
opticsIMAlarmAisClear
opticsIMAlarmTransmitterFailureRaise
opticsIMAlarmTransmitterFailureClear
opticsIMAlarmTransmitterDegradedRaise
opticsIMAlarmTransmitterDegradedClear
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
09 RELEASED
8BW 03598 0000 DSZZA 127/ 182
Table Entry
Supported Objects
Description
Value
opticsIMFilterHistoryDataTable Entries created by the managers 1..N
opticsIMFilterHDBeginTimeInterval (max 10 entries)
opticsIMFilterHDEndTimeInterval
opticsIMFilterHDGranularityPeriod
opticsIMFilterHDRowStatus
(note 1) See Communication and Routing Domain for the Management Functions.
09 RELEASED
8BW 03598 0000 DSZZA 128/ 182
9 COMMUNICATION AND ROUTING DOMAIN

The maximum number of managers connected to the NE is 10.
N.B. The agent answers to the SNMP manager requests (GET and SET) only if the IP address of the
manager is already registered in the opticsIMMgrPollingInfoTable.
The association between Point-To-Point IP interface 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)
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.

The following table lists the Communication and Routing management functions supported in this release
(see [3]).
Function IP Routing SN Function Description

Management MP
If
This function allows a managing system to request the managed
F-1. Request IP Address P system address.
Configuration Scope
This function permits to retrieve the IP address, mask and UDP of
the managed system.
Service Used
SNMP-GET on the following scalar objects (defined in TSDIM-
SNMPNE-MIB):
- tsdimSnmpAgtIpAddress
- tsdimSnmpAgtIpMask
- tsdimSnmpAgtUdpPort
Note F-1: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
F-2. Request OSPF Y about the OSPF protocol routing information.
09 RELEASED
8BW 03598 0000 DSZZA 129/ 182
Configuration Scope
This function permits to retrieve the different OSPF Area
configurations.
Service Used
SNMP-GET on the following opticsIMOspfAreaTable columnar
objects:
- opticsIMOspfAreaId
- opticsIMOspfAreaIpAddress
- opticsIMOspfAreaIpMask
- opticsIMOspfAreaStubFlag
This function allows a managing system to define different IP static
F-3. Create IP Static Routing Y routing paths.
Information Scope
This function permits to create an IP static routing object.
Service Used
SNMP-SET on the following opticsIMIpStaticRoutingInfoTable
columnar object:
- opticsIMIpStaticIpAddress
- opticsIMIpStaticIpMask
- opticsIMIpStaticDefGateway
- opticsIMIpStaticInterfaceIndex
value.
This function allows a managing system to terminate different IP

F-4. Delete IP Static Routing Y routing path objects.
Information Scope
This function permits to delete an IP routing path object.
Service Used
This function allows a managing system to request different IP
F-5. Request IP Static Y static routing paths.
Routing Information Scope
This function permits to retrieve an IP static routing object.
Service Used
SNMP-GET on the following opticsIMIpStaticRoutingInfoTable
columnar object:
- opticsIMIpStaticIpAddress
- opticsIMIpStaticIpMask
- opticsIMIpStaticDefGateway
- opticsIMIpStaticInterfaceIndex
- opticsIMIpStaticRowStatus
F-6. Request Routing Y about all IP routing paths, both static and dynamic.
Information Scope
This function permits to retrieve data related to all IP routing path
objects.
Service Used
SNMP-GET on the following opticsIMIpRoutingTable columnar
objects:
- opticsIMIpRoutingDestIpAddress
- opticsIMIpRoutingDestIpMask
- opticsIMIpRoutingDefGateway
- opticsIMIpRoutingMetricValue
- opticsIMIpRoutingRouteAge
- opticsIMIpRoutingRouteType
- opticsIMIpRoutingProtocol
- opticsIMIpRoutingLocalPtpInterface
09 RELEASED
8BW 03598 0000 DSZZA 130/ 182
This function allows a managing system to condition the managed
F-12. Condition IP Address P 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):
- tsdimSnmpAgtIpAddress
- tsdimSnmpAgtIpMask
- tsdimSnmpAgtUdpPort
Note F-12: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
This function allows a managing system to define different OSPF
F-13. Create OSPF Area Y areas.
Scope
This function permits to create different OSPF Areas.
Service Used
SNMP-SET on the following opticsIMOspfAreaTable columnar
objects:
- opticsIMOspfAreaIpAddress
value.
This function allows a managing system to delete OSPF areas.

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

Management MP
If
This function allows a managing system to define its polling
F-7. Create Manager Polling Y information
Information Scope
This function permits to create an object containing the information
needed to manage the manager polling functionality.
Service Used
SNMP-SET on the following opticsIMMgrPollingInfoTable
columnar object:
- opticsIMMgrPollingIpAddress
- opticsIMMgrPollingUdpPort
09 RELEASED
8BW 03598 0000 DSZZA 131/ 182
- opticsIMMgrPollingTimeOut
- opticsIMMgrPollingManagerType
SNMP-SET on RowStatus columnar object to "createAndWait"
value.
This function allows a managing system to terminate its polling
F-8. Delete Manager Polling Y information object.
Information Scope
This function permits to delete a polling information object.
Service Used
This function allows a managing system to request its polling
F-9. Request Manager Y information.
Polling Information Scope
This function permits to retrieve its polling information object.
Service Used
SNMP-GET on the following opticsIMMgrPollingInfoTable
columnar object:
- opticsIMMgrPollingIpAddress
- opticsIMMgrPollingUdpPort
- opticsIMMgrPollingManagerType
- opticsIMMgrPollingRowStatus
This function allows a managing system to request its owns polled
F-10. Request Polled Y information.
Information Scope
This function permits to retrieve the polled information object
related to a particular Manager.
Each Manager could read its owns polled information, such as
each manager could have its owns NotificationId and Time
associated to it.
Service Used
SNMP-GET on the following opticsIMInfoPolledTable columnar
object:
- opticsIMInfoIndex
- opticsIMInfoLastAlarmNotificationId
- opticsIMInfoLastAlarmTime
- opticsIMInfoLastEventNotificationId
- opticsIMInfoLastEventTime
- opticsIMInfoLastGenEventNotificationId (if supported)
- opticsIMInfoLastGenEventTime (if supported)
F- 48. Condition Timeout N This function allows a managing system to change the polling
Polling timeout value.
Scope
This function permits to change the polling timeout value. This
operation is feasible also in case the RowStatus is "Active".
Service Used
SNMP-SET on the following opticsIMMgrPollingInfoTable columnar
object:
Function Local Ethernet SN Function Description

Management MP
If
This function allows a managing system to create a local ethernet
F-16. Create Local Ethernet N interface.
09 RELEASED
8BW 03598 0000 DSZZA 132/ 182
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on the following columnar objects:
- opticsIMLocalEthernetIpAddress
- opticsIMLocalEthernetIpMask
- opticsIMLocalEthernetIpRoutingProtocol
- opticsIMLocalEthernetOspfAreaPointer
value.
This function allows a managing system to delete a local ethernet
F-17. Delete Local Ethernet N interface.
Scope
Service Used
This function allows a managing system to activate a local ethernet
F-33. Activate Local Ethernet Y interface.
Scope
Service Used
SNMP-SET on RowStatus columnar object to "active" value.
This function allows a managing system to deactivate a local
F-34. Deactivate Local Y ethernet interface.
Ethernet Scope
Service Used
SNMP-SET on RowStatus columnar object to "nonInService"
value.
F-18. Request Local Ethernet Y about local ethernet interfaces.
Information Scope
Service Used
- opticsIMLocalEthernetMacAddress
This function allows a managing system to condition the
F-19. Condition Local Y parameters related to local ethernet interface.
Ethernet Information Scope
Service Used
Note F-19: Allowed values for routing protocol are: none, ospf.
Function Point-to-Point IP SN Function Description

Interface Management MP
If
09 RELEASED
8BW 03598 0000 DSZZA 133/ 182
This function allows a managing system to create a point-to-point
F-20. Create Point-To-Point N IP interface.
IP Interface Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
- opticsIMIpPointToPointIPType
- opticsIMIpPointToPointIPMode
- opticsIMIpPointToPointIPRoutingProtocol
- opticsIMIpPointToPointIPOspfAreaPointer
value.
This function allows a managing system to delete a point-to-point
F-21. Delete Point-To-Point N IP interface.
IP Interface Scope
Service Used
F-22. Request Point-To-Point Y about a point-to-point IP interface.
IP Information Scope
Service Used
- opticsIMPointToPointIPType
- opticsIMPointToPointIPMode
- opticsIMPointToPointIPRoutingProtocol
- opticsIMPointToPointIPOspfAreaPointer
- opticsIMPointToPointIPRemoteAddress
This function allows a managing system to condition the
F-23. Condition Point-To- Y parameters related to a point-to-point IP interface.
Point IP Information Scope
Service Used
SNMP-SET on the following opticsIMIpPointToPointIPTable
columnar objects:
- opticsIMPointToPointIPMode
- opticsIMPointToPointIPRoutingProtocol
- opticsIMPointToPointIPOspfAreaPointer
Note F-23: opticsIMPointToPointIPMode object can assumes only the values:
• RF: notUsed
• V.11: DTE/Asynchrnous (Codirectional)
• G.703: DTE/Asynchrnous (Codirectional).
Note F-23: Allowed values for routing protocol are: none, ospf.
This function allows a managing system to activate a point-to-point
F-24. Activate a Point-To- Y IP interface.
Point IP Interface Scope
Service Used
SNMP-SET on RowStatus columnar object to "active" value.
This function allows a managing system to deactivate a point-to-
F-25. Deactivate a Point-To- Y point IP interface.
Point IP Interface Scope
Service Used
SNMP-SET on RowStatus columnar object to "notInService"
value.
09 RELEASED
8BW 03598 0000 DSZZA 134/ 182
This function allows a managed system to report the alarms
F-26. Report Point-To-Point Y related t a point-to-point IP interface.
IP Interface Alarms 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.
This function allows a managing system to request the ASAP
F-27. Request Point-To-Point Y Pointer associated a point-to-point IP interface.
IP Interface ASAP Pointer Scope
Service Used
SNMP-GET on opticsIMIpPointToPointIPAsapPointer.
This function allows a managing system to condition the ASAP
F-28. Condition Point-To- Y Pointer associated a point-to-point IP interface.
Point IP Interface ASAP Scope
Pointer OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on opticsIMIpPointToPointIPAsapPointer.
Function LAPD Management SN Function Description

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

Management MP
If
Function CLNP Tunnel SN Function Description

Management MP
If

The general naming rules for the Communication and Routing objects are defined in [13].
09 RELEASED
8BW 03598 0000 DSZZA 135/ 182
Table Entry
Supported Objects
Description
Value
opticsIMCommRouMib
opticsIMMgrPollingInfoTable Entries created by the managers 1..N
opticsIMMgrPollingIpAddress (max 10 entries)
opticsIMMgrPollingUdpPort
opticsIMMgrPollingTimeOut
opticsIMMgrPollingManagerType
opticsIMMgrPollingRowStatus
opticsIMInfoPolledTable Entries created as consequence of 1..N
opticsIMInfoLastAlarmNotificationId managers actions
opticsIMInfoLastAlarmTime (max 10 entries)
opticsIMInfoLastEventNotificationId
opticsIMInfoLastEventTime
opticsIMInfoLastGenEventNotificationId
opticsIMInfoLastGenEventTime
opticsIMOspfAreaTable Entries created by the managers 0 = backbone
opticsIMOspfAreaIpAddress (max 1+3 entries) 1..N
opticsIMOspfAreaIpMask
opticsIMOspfAreaStubFlag
opticsIMOspfAreaRowStatus
opticsIMLocalEthernetTable 1
opticsIMLocalEthernetIpAddress
opticsIMLocalEthernetIpMask
opticsIMLocalEthernetRoutingProtocol
opticsIMLocalEthernetOspfAreaPointer
opticsIMLocalEthernetRowStatus
opticsIMPointToPointIPTable RF 1
opticsIMPointToPointIPType V.11 2
opticsIMPointToPointIPMode
G.703 3
opticsIMPointToPointIPRoutingProtocol
opticsIMPointToPointIPOspfAreaPointer
opticsIMPointToPointIPRemoteAddress
opticsIMPointToPointIPRowStatus
opticsIMPointToPointIPAsapIndex
opticsIMIpStaticRoutingInfoTable Entries created by the managers <IP address>
opticsIMIpStaticIpMask
opticsIMIpStaticDefGateway
opticsIMIpStaticInterfaceIndex
opticsIMIpStaticRowStatus
opticsIMIpRoutingInfoTable Entries created by the agent on <IP address>
opticsIMIpRoutingDestIpMask managers GET request
opticsIMIpRoutingDefGateway
opticsIMIpRoutingMetricValue
opticsIMIpRoutingRouteAge
opticsIMIpRoutingRouteType
opticsIMIpRoutingProtocol
opticsIMIpRoutingLocalPtpInterface
09 RELEASED
8BW 03598 0000 DSZZA 136/ 182
10 OVERHEAD DOMAIN

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

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

Parameters MP
If
F-1.1 Request EOW Phone Y the phone number associated to an Engineering Order Wire.
Number Scope
OPTICSIM-OH-MIB: opticsIMEowDTMFTTPBidTable
Service Used
SNMP-GET on: opticsIMEowDTMFTTPBidPhoneNumber
This management function allow the managing system to condition
F-1.2 Condition EOW Phone Y the phone number associated to an Engineering Order Wire.
Number Scope
OPTICSIM-OH-MIB: opticsIMEowDTMFTTPBidTable
Service Used
SNMP-SET on: opticsIMEowDTMFTTPBidPhoneNumber
F- 1.3 Condition EOW Party N This management function allows the managing system to
Line enable/disable the Engineering Order Wire party line feature on
NMS port.
The managing system has to provided in the request the index of
EOW table (identified by ifIndex), the port type of NMS port (nms-
v11 or nms-g703) and the port identifier (identified by
opticsIMPointToPointIPId of opticsIMPointToPointIPTable).
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-SET on: opticsIMEowPartyLineEnabled
F- 1.4 Request EOW Party N This management function allows the managing system to request
Line if the Engineering Order Wire party line feature on NMS port is
09 RELEASED
8BW 03598 0000 DSZZA 137/ 182
enabled or disabled.
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-GET on: opticsIMEowPartyLineEnabled
Auxiliary Interfaces

MP
If
F-1.10 Request Auxiliary Y the auxiliary interface type.
Interface Type Scope
OPTICSIM-OH-MIB: opticsIMAuxiliaryPITTPBidTable
Service Used
SNMP-GET on: opticsIMAuxiliaryPITTPBidType
This management function allow the managing system to condition
F-1.11 Condition Auxiliary Y the auxiliary interface type.
Interface Type Scope
Service Used
SNMP-SET on: opticsIMAuxiliaryPITTPBidType
F-1.13 Request Auxiliary Y the ASAP Pointer associated to the auxiliary interface.
ASAP Pointer Scope
Service Used
SNMP-GET on opticsIMAuxiliaryPITTPBidAsapIndex
F-1.14 Condition Auxiliary Y the ASAP Pointer associated to the auxiliary interface.
ASAP Pointer Scope
Service Used
SNMP-SET on opticsIMAuxiliaryPITTPBidAsapIndex

MP
If
F-1.15 Request Auxiliary Y the operational state of the auxiliary interface.
Service Used
SNMP-GET on opticsIMAuxiliaryPITTPBidOperationalState
F- 1.16 Request Auxiliary N This management function allows the managing system to request
Connection Status 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
09 RELEASED
8BW 03598 0000 DSZZA 138/ 182
Service Used
SNMP-GET on: opticsIMAuxiliaryPITTPBidCrossConnectIdentifier

MP
If
F- 1.12 Report Auxiliary Y This management function allows a managed system to report
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.
Overhead Bytes

MP
If
F- XX. All the functions. N

MP
If
F- XX. All the functions. N

The general naming rules for the Overhead objects are defined in [13].
Table Entry
Supported Objects
Value
opticsIMOverheadMib
opticsIMEowDTMFTTPBidTable All EOW port 1
opticsIMEowDTMFTTPBidPhoneNumber
09 RELEASED
8BW 03598 0000 DSZZA 139/ 182
Table Entry
Supported Objects
Value
opticsIMAuxiliaryPITTPBidTable All Auxiliary port 301
opticsIMAuxiliaryPITTPBidType
opticsIMAuxiliaryPITTPBidAsapIndex
opticsIMAuxiliaryPITTPBidOperationalState
09 RELEASED
8BW 03598 0000 DSZZA 140/ 182
11 TEST DOMAIN

The functions described in this section are used to control and monitor the test operations. All the entries
related to the loopbacks tables will be created by the agent as consequence of the equipment
provisioning phase (see Equipment Domain). The managing systems can only activate/deactivate the
loopbacks.
The 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 one of the
following tables: opticsIME1pPITTPTable, opticsIME3pPITTPTable, opticsIMDs1pPITTPTable
(note 1) or opticsIMDs3pPITTPTable (note 1).
• 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 one of the
following tables: opticsIME1PathTTPTable, opticsIME3PathTTPTable, opticsIMDs1PathTTPTable
(note 1) or opticsIMDs3PathTTPTable (note 1).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.
ODU
• 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.
• 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.
N.B. The loopbacks types defined as “Local only” can be requested only by managers declared as
“localct” in the related MgrPollingManagerType object of the polling table.
The modality of work of all of these types of loopbacks is Loop-And-Continue.

The following table lists the Test management functions supported in this release (see [9]).
09 RELEASED
8BW 03598 0000 DSZZA 141/ 182
MP
If
F-1 Request Loopback Y the chracteristics (TP to be tested, direction and behaviour of the
Configuration 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
This management function allow the managing system to activate a
F-2 Condition Loopback Y loopback test.
Activation Scope
Service Used
SNMP-SET on loopbackActivation
This management function allow the managing system to request if
F-3 Request Near-End/Far- Y the loopback is referred to the Near-End or Far-End NE and the
End Loopback Type 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
F-4 Request Loopback Timer N the activation date (if loopback is yet activated) and the time during
Configuration the loopback stays active.
Scope
Service Used
SNMP-GET on:
SNMP-GET on:
• loopbackActivationDate
• loopbackTimeoutPeriod
This management function allow the managing system to configure
F-5 Condition Loopback N the timer for loopback activation.
Timeout Scope
Service Used
SNMP-SET on loopbackTimeoutPeriod
09 RELEASED
8BW 03598 0000 DSZZA 142/ 182
The Test SNMP tables, columnar and scalar objects supported by this release are the following:
opticsIMTestMib
opticsIMLoopbackTable
loopbackPointObjectInstance
loopbackDirectionality
loopbackPointAdditionalDefinition
loopbackBehaviour
loopbackActivation
opticsIMLoopbackExtTable
loopbackNEType
loopbackAllowedManager
The general naming rules of the Test objects are defined in [13]. The following tables provides the list of
loopback points, with the associated characteristics, supported in the current release.
1+0 Configurations
Loopback Object Instance

NE
Table TP TP Additional Def. Directionality
Type
Indexes Table Index
1; 1..16 opticsIME1pPITTPTable 1xx01 nearEnd <trib> Port#xx externalLine
opticsIMDS1pPITTPTable (note 5) (note 1)
1; 1 opticsIME3pPITTPTable 10101 <trib> Port#1 externalLine
1; 17 opticsIMCoderTTPTable 20101 nearEnd IDU Cable externalLine
1; 18..33 opticsIME1PathTTPTable 2zz01 farEnd <trib> Port#xx internal
opticsIMDS1PathTTPTable (note 5) (note 1)
1; 18 opticsIME3PathTTPTable 20101 <trib Port#1 internal
1; 34 opticsIMRadioPDHTTPBidTable 20101 nearEnd ODU Cable externalLine
1; 35 RF externalLine
1; opticsIME1PathTTPTable 2zz01 nearEnd <trib> Port#xx internal

101..116 opticsIMDS1PathTTPTable (note 5) (note 1)
(note 2)
1; 101 opticsIME3PathTTPTable 20101 <trib> Port#1 internal
(note 2) opticsIMDS3PathTTPTable (note 5)
(note 1) xx= 01..16
(note 2) This loopback cannot be activated/deactivated by the manager.
((note 5) Not supported on ULS 2.0.0
1+1 Configurations
Loopback Object Instance

NE
Table TP TP Additional Def. Directionality
Type
Indexes Table Index
Common; opticsIME1pPITTPTable 1xx99 nearEnd <trib> Port#xx externalLine
1..16 opticsIMDS1pPITTPTable (note 5) (note 1)
09 RELEASED
8BW 03598 0000 DSZZA 143/ 182
Common; opticsIME3pPITTPTable 10199 <trib> Port#1 externalLine
1 opticsIMDS3pPITTPTable (note 5)
Common; opticsIME1PathTTPTable 2zz99 farEnd <trib> Port#xx internal
Common; opticsIME3PathTTPTable 20199 <trib Port#1 internal

18 opticsIMDS3PathTTPTable (note 5)
Common; opticsIME1PathTTPTable 2zz99 nearEnd <trib> Port#xx internal

(note 2)
Common; opticsIME3PathTTPTable 20199 <trib> Port#1 internal
101 opticsIMDS3PathTTPTable (note 5)
(note 2)

(note 1) xx= 01..16
(note 2) This loopback cannot be activated/deactivated by the manager.
09 RELEASED
8BW 03598 0000 DSZZA 144/ 182
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.
Only from ULS 2.0.3: in 1+1 with hitless configuration if the Extension unit is missing or switched off, 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 Pegaso FPGA 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.
E3 16E1 8E1 4E1 2E1 DS3 16DS1 8DS1 4DS1

Gross bit rate 39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140
[MHz]
RS Blocks 19200 19200 9600 4800 2400 28000 14000 7000 3500
number/sec.
SES Threshold 5760 5760 2880 1440 720 8400 4200 2100 1050
(note 1)
(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.
N.B. Frame structure DS3, 16DS1, 8DS1, 4DS1 are not supported on ULS 2.0.0
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
Configuration
TP Table TP index
opticsIMPdhFrameHopCurrentDataTable 20101 All the configurations
20100 All the 1+1 configurations
opticsIMPdhFrameLinkCurrentDataTable 20199 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.
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).
09 RELEASED
8BW 03598 0000 DSZZA 145/ 182
The following tables list the PM management functions supported in this release (see [7]).
SDH Performance Monitoring Measurement Collection

MP
If
F-x.xx All the functions N
PDH Frame Performance Monitoring Measurement Collection

All the functions below apply to:
• Current Data => opticsIMPdhFrameHopCurrentDataTable

opticsIMPdhFrameLinkCurrentDataTable
• History Data => opticsIMPdhFrameHopHistoryDataTable

opticsIMPdhFrameLinkHistoryDataTable
• Threshold Data => opticsIMPdhFrameHopThresholdDataTable

opticsIMPdhFrameLinkThresholdDataTable
Function Creation of PDH SN Function Description

Frame and Tributary Current MP
Data If
This management function permits to allocate one CD entry. The
F-4.1 Create CD Entry N 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
• pmPdh<Layer>CDAsapIndex
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object to
"createAndGo " value
09 RELEASED
8BW 03598 0000 DSZZA 146/ 182
Function Configuration of SN Function Description
PDH Frame and tributary MP
Current Data Mode If
This management function permits to request the elapsed time in
F-4.3 Request Elapsed Time Y the current interval.
Scope
Service Used
SNMP-GET on pmPdh<Layer>CDElapsedTime
Note F-4.3: Elapsed time is measured in seconds.
This management function permits to request the granularity period
F-4.4 Request Granularity Y (15 min or 24 h).
Period Scope
Service Used
SNMP-GET on pmPdh<Layer>CDGranularityPeriod
This management function permits to condition the maximum
F-4.5 Condition Max N number of intervals which can be suppressed.
Suppressed Interval Scope
Service Used
SNMP-SET on pmPdh<Layer>CDMaxSuppressedIntervals
This management function permits to request the Max Suppressed
F-4.6 Request Max Y Interval.
Suppressed Interval Scope
Service Used
SNMP-GET on pmPdh<Layer>CDMaxSuppressedIntervals
This management function permits to request the Number of
F-4.8 Request Number of Y Suppressed Intervals.
Suppressed Intervals Scope
Service Used
SNMP-GET on pmPdh<Layer>CDNumSuppressedIntervals
This management function permits to request whether the current
F-4.9 Request Suspect Y data is suspect or not.
Interval Flag Scope
Service Used
SNMP-GET on pmPdh<Layer>CDSuspectIntervalFlag
This management function permits to reset the Suspect Interval
F-4.10 Reset Suspect Interval N Flag.
Flag Scope
Service Used
SNMP-SET to default value on
pmPdh<Layer>CDSuspectIntervalFlag
This management function permits to identify the Management
F-4.11 Request Start By OS N 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
F-4.13 Reset PM Data Y Collection. The following counters can be reset:
Collection • BBE
09 RELEASED
8BW 03598 0000 DSZZA 147/ 182
• 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.
F-4.2 Activate CD Entry Y 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
"active" value
This management function permits to deactivate one CD entry to
F-4.14 Deactivate CD Entry Y stop the counters.
Scope
Service Used
"notInService" value
This management function permits to set the ASAP Pointer related
F-4.16 Condition CD Asap Y to a Threshold cross alarm of a CD entry.
Pointer Scope
Service Used
SNMP-SET on pmPdh<Layer>CDAsapIndex
This management function permits to request the ASAP Pointer
F-4.17 Request CD Asap Y related to a Threshold cross alarm of a CD entry.
Pointer Scope
Service Used
SNMP-GET on pmPdh<Layer>CDAsapIndex
Function Request of PDH SN Function Description

Data If
This management function permits to Request PM Data Collection.
F-4.12 Request PM Data Y The following counters can be retrieved:
Collection • BBE
• ES
• SES
• UAS
Scope
Service Used
SNMP-GET on:
09 RELEASED
8BW 03598 0000 DSZZA 148/ 182
– pmPdh<Layer>CDSes
– pmPdh<Layer>CDUas
– pmPdh<Layer>CDBbe
– pmPdh<Layer>CDEs
Function Release of PDH SN Function Description

Data If
This management function permits to delete one CD entry.
F-4.15 Delete CD Entry N Scope
Service Used
"destroy" value
Function Report of PDH SN Function Description

Frame and Tributary PM MP
Alarms If
This management function permits to report TCA and UAT alarms.
F-4.18 Report CD Alarms Y Scope
Service Used
• opticsIMAlarmThresholdCrossRaise
• opticsIMAlarmThresholdCrossClear
• opticsIMAlarmUnavailableTimeRaise
• opticsIMAlarmUnavailableTimeClear

PDH Frame and Tributary MP
History Data If
This management function permits to request the elapsed time in
F-5.1 Request Elapsed Time Y the current interval.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDElapsedTime
This management function permits to request the granularity period
F-5.2 Request Granularity Y (15 min or 24 h).
Period Scope
Service Used
SNMP-GET on pmPdh<Layer>HDGranularityPeriod
This management function permits to request the Number of
F-5.4 Request Number of Y Suppressed Intervals.
Suppressed Intervals Scope
Service Used
SNMP-GET on pmPdh<Layer>HDNumSuppressedIntervals
This management function permits to request whether the History
F-5.5 Request Suspect Y data is suspect or not.
Interval Flag Scope
09 RELEASED
8BW 03598 0000 DSZZA 149/ 182
Service Used
SNMP-GET on pmPdh<Layer>HDSuspectIntervalFlag
This management function permits to identify the Management
F-5.6 Request Start By OS N System which started the measurement.
Scope
Service Used
SNMP-GET on pmPdh<Layer>HDStartByOS
Function Request of PDH SN Function Description

Frame and Tributary History MP
Data If
This management function permits to Request PM Data Collection.
F-5.7 Request PM Data Y The following counters can be retrieved:
Collection • BBE
• ES
• SES
• UAS
Scope
Service Used
SNMP-GET on:
– pmPdh<Layer>HDBbe
– pmPdh<Layer>HDEs
– pmPdh<Layer>HDSes
– pmPdh<Layer>HDUas
Function Creation of PDH SN Function Description

Frame and Tributary MP
Threshold Data If
This management function permits to allocate one Threshold Data
F-6.1 Create Threshold Data Y entry. The management system has to indicate in the creation
Entry request the index for the threshold data entry, which the
management system has previously got from the agent (GET on
opticsIMPdh<Layer>ThrIndexNext).
Scope
OPTICSIM-PDH-PM-MIB:
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 Tributary MP
Threshold Data If
This management function permits to assign thresholds to PM
F-6.3 Condition PM Y counters.
Thresholds Assignment The thresholds are assigned setting, in the relative CD, the
Threshold Data Instance providing the Threshold values.
09 RELEASED
8BW 03598 0000 DSZZA 150/ 182
Scope
Service Used
SNMP-SET on pmPdh<Layer>CDThresholdDataInstance
This management function permits to request the assignment of
F-6.4 Request PM Thresholds Y thresholds to PM counters.
Assignment Scope
Service Used
SNMP-GET on pmPdh<Layer>CDThresholdDataInstance
This management function permits to configure the thresholds for
F-6.5 Condition PM Y PM counters.
Thresholds 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
F-6.6 Request PM Thresholds Y 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
F-6.9 Condition Threshold N associated to a Threshold Data entry.
Data User Label Scope
Service Used
SNMP-SET on pmPdh<Layer>UserLabel
This management function permits to request the User Label
F-6.10 Request Threshold N associated to a Threshold Data entry.
Data User Label Scope
Service Used
09 RELEASED
8BW 03598 0000 DSZZA 151/ 182
SNMP-GET on pmPdh<Layer>UserLabel
Function Release of PDH SN Function Description

Frame and Tributary MP
Threshold Data If
This management function permits to delete one Threshold Data
F-6.8 Delete Threshold Data Y entry.
Entry Scope
Service Used
SNMP-SET on pmPdh<Layer>RowStatus columnar object to
"destroy" value
09 RELEASED
8BW 03598 0000 DSZZA 152/ 182
The general naming rules for the SDH/PDH Performance Monitoring objects are defined in [13].
Table Entry
Supported Objects
Value
opticsIMPdhPmMib
opticsIMPdhFrameHopCurrentDataTable All 15 min. – Ch#1 20101; 1
pmPdhFrameHopCDElapsedTime All the 1+1 15 min. – Ch#0 20100; 1
pmPdhFrameHopCDGranularityPeriod
All 24 h – Ch#1 20101; 2
pmPdhFrameHopCDMaxSuppressedIntervals
pmPdhFrameHopCDNumSuppressedIntervals All the 1+1 24 h – Ch#0 20100; 2
pmPdhFrameHopCDSuspectIntervalFlag
pmPdhFrameHopCDThresholdDataInstance
pmPdhFrameHopCDSes
pmPdhFrameHopCDUas
pmPdhFrameHopCDBbe
pmPdhFrameHopCDEs
pmPdhFrameHopCDRowStatus
pmPdhFrameHopCDAsapIndex
opticsIMPdhFrameHopHistoryDataTable All 15 min. – Ch#1 20101; 1;
pmPdhFrameHopHDElapsedTime period x
pmPdhFrameHopHDGranularityPeriod (x=1..96)
pmPdhFrameHopHDNumSuppressedIntervals All the 1+1 15 min. – Ch#0 20100; 1;
pmPdhFrameHopHDSuspectIntervalFlag period x
pmPdhFrameHopHDSes (x=1..96)
pmPdhFrameHopHDUas All 24 h – Ch#1 20101; 2;
pmPdhFrameHopHDBbe period x
pmPdhFrameHopHDEs (x=1..8)
All the 1+1 24 h – Ch#0 20100; 2;
period x
(x=1..8)
opticsIMPdhFrameHopThresholdDataTable All 15 min 1..3
pmPdhFrameHopSesHighThr (note 1)
pmPdhFrameHopSesLowThr
pmPdhFrameHopBbeHighThr
pmPdhFrameHopBbeLowThr 24 h 4..6
pmPdhFrameHopEsHighThr (note 2)
pmPdhFrameHopEsLowThr
pmPdhFrameHopRowStatus
opticsIMPdhFrameLinkCurrentDataTable All the 1+1 15 min. – Ch#Common 20199; 1
09 RELEASED
8BW 03598 0000 DSZZA 153/ 182
Table Entry
Supported Objects
Value
pmPdhFrameLinkCDElapsedTime All the 1+1 24 h – Ch#Common 20199; 2
pmPdhFrameLinkCDGranularityPeriod
pmPdhFrameLinkCDMaxSuppressedIntervals
pmPdhFrameLinkCDNumSuppressedIntervals
pmPdhFrameLinkCDSuspectIntervalFlag
pmPdhFrameLinkCDThresholdDataInstance
pmPdhFrameLinkCDSes
pmPdhFrameLinkCDUas
pmPdhFrameLinkCDBbe
pmPdhFrameLinkCDEs
pmPdhFrameLinkCDRowStatus
pmPdhFrameLinkCDAsapIndex
opticsIMPdhFrameLinkHistoryDataTable All the 1+1 15 min. – Ch#Common 20199; 1;
pmPdhFrameLinkHDElapsedTime period x
pmPdhFrameLinkHDGranularityPeriod (x=1..96)
pmPdhFrameLinkHDNumSuppressedIntervals All the 1+1 24 h – Ch#Common 20199; 2;
pmPdhFrameLinkHDSuspectIntervalFlag period x
pmPdhFrameLinkHDSes (x=1..8)
pmPdhFrameLinkHDUas
pmPdhFrameLinkHDBbe
pmPdhFrameLinkHDEs
opticsIMPdhFrameLinkThresholdDataTable All 15 min 1..2
pmPdhFrameLinkSesHighThr (note 1)
pmPdhFrameLinkSesLowThr
pmPdhFrameLinkBbeHighThr
pmPdhFrameLinkBbeLowThr 24 h 3..4
pmPdhFrameLinkEsHighThr (note 3)
pmPdhFrameLinkEsLowThr
pmPdhFrameLinkRowStatus
(note 1) index value ‘1’ is reserved for default entry not modifiable by managing system.
09 RELEASED
8BW 03598 0000 DSZZA 154/ 182
13 SECURITY DOMAIN
N.B. Security features are not supported on ULS 2.0.0 and ULS 2.0.1.
The NE can be accessed from a managing system by the SNMP protocol (see [13.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.
13.1 Functional Description (SNMP Interface)

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) an user is created on opticsIMCtUserTable with opticsIMCtUserId =

‘initial, opticsIMCtUserRights = 1 (administrator) and opticsIMCtUserPassword = ‘initialing’. The change
of the password of this administrator user 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).
Reset NE behaviour
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 recreate as
before the NE reset.
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/his 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 can’t add or
remove operators, he/she can’t do backup and restore.
This user profile is related only to OS system and so not stored on MIB NE. To manage NE the
opportune menu items are enabled/disabled according to table on APPENDIX A.
09 RELEASED
8BW 03598 0000 DSZZA 155/ 182
• 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 can’t 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 can’t 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 can’t 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 can’t 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
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 User profile ‘opticsIMCtUserRights’ value

administrator administrator
operator operator
craftPerson constructor
viewer viewer
User authentication
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
09 RELEASED
8BW 03598 0000 DSZZA 156/ 182
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. It’is 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 ( see APPENDIX A for details on CT
interface).
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
There are 2 different behaviour for resource access control policy on SNMP v2:
• 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). It’s 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).
On APPENDIX A the list of authorized functions for each profile is defined.
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).
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.
See APPENDIX A for details.
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 ot to destroy, for instance) to any user on the NE if it don’t 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
[11].
09 RELEASED
8BW 03598 0000 DSZZA 157/ 182
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 SN Function Description

Management MP
If
Function VACM SN Function Description

Management MP
If
Function SNMPv2 SN Function Description

Security Management MP
If
F-44 Condition New User Y This management function allows the managing system to create a new
Creation 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 Y This management function allows the managing system to delete an
Deletion user profile in the managed system.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”userDeletion”>
_ opticsIMUserUsername: <operator username>
F-46 Condition Password Y This management function allows the managing system to require the
Verification 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 Y This management function allows the managing system to change the
Password changed By password related to the operator
09 RELEASED
8BW 03598 0000 DSZZA 158/ 182
Function SNMPv2 SN Function Description
Security Management MP
If
User that is executing the request.
Scope
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”changePasswordByUser”>
_ opticsIMUserPassword: <old operator password>
_ opticsIMCorollaryPassword: <new operator password>
F-48 Condition For Y This management function allows the managing system to change the
Password changed By password related to an operator .
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 Username Y This management function allows the managing system to get the list of
List all usernames admitted in the
managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMCtUserTable
Service Used
SNMP-GET-NEXT on
_ opticsIMCtUserId
_ opticsIMCtUserRights

Supported Objects Table Entry

(Table/Scalar/Trap)
Description Indexes Values
opticsIMSecurityMIB
opticsIMCtUserTable
opticsIMCtUserId Max 25 entries 1..N (note 1)
opticsIMCtUserPassword
opticsIMCtUserRights
opticsIMCtRowStatus
09 RELEASED
8BW 03598 0000 DSZZA 159/ 182
opticsIMUserOperationTable
opticsIMUserOperationOperation Only one entry 1
opticsIMUserUsername
opticsIMUserPassword
opticsIMCorollaryUsername
opticsIMCorollaryPassword
opticsIMCtUserRights
(note 1) index value ‘1’ is reserved for default user ‘initial’.
09 RELEASED
8BW 03598 0000 DSZZA 160/ 182
14 ALARMS
14.1 Alarms Provided by Item HW

URU alarms are not supported.
Legenda:
• SA = always Service Affecting
• SAac = Service Affecting when the alarm is present on the active channel, Not Service Affecting
when it is present on the stand-by channel
• NSA = always Not Service Affecting
Service
Equipmen Affecting
Equipment Alarm
t Evaluation
Type Description
Expected
1+0 1+1
SAac
Cable Loss IDU SA
Main Scalable Unit ±24 V Supply M24S (note 3)
SAac
Card Fail SA
Main Scalable Unit ±48/±60 V M4860S (note 2)
Range Supply SAac
Equipment Mismatch SA
(note 2)
Main Scalable Unit ±24/±60 V M2460S
E1 RDI egressing (Rx side) (note 1) NSA NSA
Range Supply
E1 RDI ingressing (Tx side) (note 1) NSA NSA
SAac
High BER SA
(note 3)
Housekeeping Alarm NSA NSA
Lan Failure NSA NSA
Link Identifier Mismatch SA SA

Loss of Frame of PDH tributary
SA SA
ingressing (Tx side) (note 1)
SA SA
egressing (Rx side) (note 1)
Loss of Frame of PDH signal Radio SAac
SA
side (note 3)
Loss of Signal of PDH tributary SA SA
Loss of 64kbit/s G.703 Auxiliary Signal NSA NSA

Loss of 64kbit/s G.703 NMS Signal
NSA NSA
(DTE and Asynchronous mode only)
Low BER NSA NSA
PDH-AIS egressing (Rx side) SA SA
PDH-AIS ingressing (Tx side) SA SA
PPP IP Fail NSA NSA

SAac
TCA on Hop Section SA
(note 3)
09 RELEASED
8BW 03598 0000 DSZZA 161/ 182
Service
Equipmen Affecting
Equipment Alarm
t Evaluation
Type Description
Expected
1+0 1+1
TCA on Link Section (note 3) - SA

SAac
UAT on Hop Section SA
(note 3)
UAT on Link Section (note 3) - SA
Firmware Download in progress NSA NSA
Service
Equipmen Affecting
Equipment Alarm
t Evaluation
Type Description
Expected
1+0 1+1
SAac
Cable Loss IDU -
Extension Scalable Unit ±24 V E24S (note 3)
Supply SAac
Card Fail -
(note 2)
Extension Scalable Unit ±48/±60 E4860S SAac
V Range Supply Card Missing -
(note 2)
SAac
Extension Scalable Unit ±24/±60 E2460S Equipment Mismatch -
(note 2)
V Range Supply
E1 RDI egressing (Rx side) (note 1) - NSA
E1 RDI ingressing (Tx side) (note 1) - NSA

SAac
High BER -
(note 3)
Link Identifier Mismatch - SA
Loss of Alignment - NSA

- SA
ingressing (Tx side) (note 1)
- SA
egressing (Rx side) (note 1)
Loss of Frame of PDH signal Radio SAac
-
side (note 3)
Loss of Signal of PDH tributary - SA
Loss of 64kbit/s G.703 Auxiliary Signal - NSA

Loss of 64kbit/s G.703 NMS Signal
- NSA
(DTE and Asynchronous mode only)
Low BER - NSA
PDH-AIS egressing (Rx side) - SA
PDH-AIS ingressing (Tx side) - SA

SAac
TCA on Hop Section -
(note 3)
TCA on Link Section - SA
09 RELEASED
8BW 03598 0000 DSZZA 162/ 182
Service
Equipmen Affecting
Equipment Alarm
t Evaluation
Type Description
Expected
1+0 1+1
SAac
UAT on Hop Section -
(note 3)
UAT on Link Section - SA
Unconfigured Equipment - NSA

Firmware Download in progress NSA NSA
Unconfigured Equipment (note 4) - NSA
Service
Equipmen Affecting
Equipment Alarm
t Evaluation
Type Description
Expected
1+0 1+1
Card Fail SA SA
Ethernet unit P2DATAS
Card Missing SA SA
Client Signal Fail egressing (Rx side) NSA NSA

Loss of Signal on Ethernet port (link
SA SA
down)
Loss of GFP on Ethernet port
SA SA
egressing (Rx side)
Unconfigured Equipment (note 5) NSA NSA
SAac
Card Fail SA
8xE1/DS1 plug-in unit P8E1DS1 (note 2)
SAac
Card Missing SA
1xE3/DS3 plug-in unit P1E3DS3 (note 2)
SAac
Equipment Mismatch SA
(note 2)
Loss of Signal of PDH tributary SA SA
Unconfigured Equipment (note 5) NSA NSA
(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 detectd on Extension Scalable Unit but reported on IDU Main Scalable Shelf.
(note 5) This alarm is detectd on plug-in unit but reported on Main or Extension Scalable Unit
(according to the Unit on which the module is plugged).
09 RELEASED
8BW 03598 0000 DSZZA 163/ 182
ODU Alarms
Service Affecting
Evaluation
Equipment Equipment Alarm
1+1 1+1
Type Expected Description 1+0
FD HST
ATPC Loop NSA NSA NSA
ODU ETSI ODU-E
Card Fail SA SAac SAac
ODU ANSI ODU-A
Demodulation Function Failure (note 4) SA SAac SAac
Early Warning (note 8) - NSA NSA
Equipment Mismatch SA SAac SAac

Loss of Signal for the Modulation Function
SA NSA SAac
(note 2)
Modulation Function Failure (note 7) SA NSA SAac
ODU not responding (note 1) SA SAac SAac

Provisioned Frequency incompatible with
SA SAac SAac
actual HW
Provisioned Shifter incompatible with
SA SAac SAac
actual HW
Provisioned Tx Power incompatible with
NSA NSA NSA
actual HW
Receiving Function Failure (note 3) SA SAac SAac
Software Version Mismatch NSA NSA NSA
Stand-by Software Version Mismatch NSA NSA NSA
Transmission Function Failure (note 5) SA NSA SAac
Unconfigured Equipment (note 6) NSA NSA NSA

Firmware Download in progress NSA NSA NSA
N.B.: The active channel must be referred to the RPS, except for the transmission alarms in 1+1 HST
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”.
(note 4) Demodulation Function Failure represents the “synchronization missing at receive side alarm”.
(note 5) Transmission Function Failure represents the “transmitted power alarm”.
(note 6) Only for ODU Ch#0 in 1+1 configurations.
(note 7) Modulation Function Failure represents the “synchronization missing at transmission side
alarm”.
09 RELEASED
8BW 03598 0000 DSZZA 164/ 182
(note 8) Only in the 1+1 configurations with Hitless Switch.
14.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.
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.
14.2.1 Equipment Alarms

Objects
Alarm Notification Type
Table/Scalar Index Equipment
Description (Mib)
(Mib) Value Label
Remote NE Failure RemoteNEFailure EquipmentTable 1.1.0.0
Indication (tsdimSnmpNEMib) (opticsIMEqptMib)
Housekeeping Alarm HousekeepingAlarm ExternalInputPoint 1..6
(opticsIMEqptMib) (opticsIMEqptMib)
Card Fail ReplaceUnitProblem EquipmentTable 1.1.1.0 MAIN Ch#1
(opticsIMEqptMib) (opticsIMEqptMib) 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
Card Missing ReplaceUnitMissing 1.1.1.1 MAIN/<(note 1)>
(opticsIMEqptMib) Ch#1
1.3.1.0 EXT Ch#0
1.3.1.1 EXT/<(note 1)>
Ch#0
Equipment Mismatch ReplaceUnitTypeMismatch 1.1.1.0 MAIN Ch#1
(opticsIMEqptMib) 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
Lan Failure LanFailure 1.1.1.0 MAIN Ch#1
09 RELEASED
8BW 03598 0000 DSZZA 165/ 182
Objects
Table/Scalar Index Equipment
Description (Mib)
(Mib) Value Label
(opticsIMEqptMib)
ODU not responding InternalCommunicationProbl EquipmentTable 1.2.0.0 ODU Ch#1
em (opticsIMEqptMib) 1.4.0.0 ODU Ch#0
(opticsIMEqptMib)
Software Version VersionMismatch 1.2.0.0 ODU Ch#1
Mismatch (opticsIMEqptMib) 1.4.0.0 ODU Ch#0
Stand-by Software StandByVersionMismatch 1.2.0.0 ODU Ch#1
Version Mismatch (opticsIMEqptMib) 1.4.0.0 ODU Ch#0
Unconfigured Equipment UnconfiguredEquipmentPre 1.1.1.0 MAIN/Plug-in
sent Ch#1
(opticsIMEqptMib) 1.1.0.0 EXT Ch#0
1.3.1.0 EXT/Plug-in
1.4.0.0 Ch#0
ODU Ch#0
Firmware Download in FirmwareDownloadOnGoing 1.1.1.0 MAIN Ch#1
progress (opticsIMEqptMib) 1.3.1.0 EXT Ch#0
1.2.0.0 ODU Ch#1
1.4.0.0 ODU Ch#0

• DS1, when the 8xE1/DS1 plug-in is provisioned and it configured to work in DS1 mode
(Not supported on ULS 2.0.0)
• DS3, when the 1xE3/DS3 plug-in is provisioned and it is configured to work in DS3
mode. (Not supported on ULS 2.0.0)
• DATA, when the 2xDATA plug-in is provisioned.
14.2.2 Communication Alarms

Objects
Table/Scalar Index
Description (Mib)
(Mib) Value
Loss of 64 kbit/s G.703 LossOfSignal AuxiliaryPITTPBidTable 301
Auxiliary Signal (tsdimSnmpNEMib) (opticsIMOverheadMib)
Cable Loss IDU CableLOS CoderTTPTable 20101
(tsdimSnmpNEMib) (opticsIMTrsPdhMib) 20100
High BER HighBER
(opticsIMRadioTrsCommonMib)
Loss of Frame of PDH signal LossOfFrame
Radio side (tsdimSnmpNEMib)
E1 RDI ingressing (Tx side) RemoteDefectIndication E1pPITTPTable 1xx01 or
(tsdimSnmpNEMib) (opticsIMTrsCommonMib) 1xx99
(xx=1..16)
(note 1)
E1 RDI egressing (Rx side) E1PathTTPTable 2xx01 or
(opticsIMTrsCommonMib) 2xx99
(xx=1..16)
(note 2)
Loss of Frame of PDH LossOfFrame E1pPITTPTable 1xx01 or
tributary ingressing (Tx side) (tsdimSnmpNEMib) (opticsIMTrsCommonMib) 1xx99
Loss of Signal of PDH LossOfSignal Ds1pPITTPTable (note 3) (xx=1..16)
09 RELEASED
8BW 03598 0000 DSZZA 166/ 182
Objects
tributary (tsdimSnmpNEMib) (opticsIMTrsCommonMib) (note 1)
PDH-AIS ingressing opticsIMAlarmAis E3pPITTPTable
(Tx side) (tsdimSnmpNEMib) (opticsIMTrsCommonMib)
Ds3pPITTPTable (note 3)
(opticsIMTrsCommonMib)
Loss of Frame of PDH LossOfFrame E1PathTPTable 2xx01 or
tributary egressing (Rx side) (tsdimSnmpNEMib) (opticsIMTrsCommonMib) 2xx99
PDH-AIS egressing opticsIMAlarmAis E3PathTTPTable (xx=1..16)
(Rx side) (tsdimSnmpNEMib) (opticsIMTrsCommonMib) (note 2)
Ds1PathTTPTable (note 3)
Ds3PathTTPTable (note 3)
Loss of GFP on Ethernet portLossOfFrame GfpConfTable 29901
egressing (Rx side) (tsdimSnmpNEMib) (opticsIMGFPMib)
Loss of Signal on Ethernet LossOfSignal ifMauTable 11701;1
port (link down) (tsdimSnmpNEMib) (mauMod) 11801;1
TCA on Hop Section TCA PdhFrameHopCurrentDataT 20101; 1
(tsdimSnmpNEMib) able 20101; 2
UAT on Hop Section UnavailableTime (opticsIMPdhPmMib) 20100; 1
(tsdimSnmpNEMib) 20100; 2
TCA on Link Section TCA PdhFrameLinkCurrentDataT 20199; 1
(tsdimSnmpNEMib) able 20199; 2
UAT on Link Section UnavailableTime (opticsIMPdhPmMib)
(tsdimSnmpNEMib)
Loss of 64kbit/s G.703 NMS LossOfSignal PointToPointIPTable 3
Signal (DTE and (tsdimSnmpNEMib) (opticsIMCommRouMib)
Asynchronous mode only)
PPP IP Fail PPPFail 1
(tsdimSnmpNEMib) 2
3
ATPC Loop AtpcLoopProblem RadioPDHTTPBidTable 20101
(opticsIMRadioTrsCommonMib) (opticsIMRadioTrsPdhMib) 20100
Early Warning EarlyWarning
(opticsIMRadioTrsCommonMib)
Provisioned Frequency (or IncompatibleFrequency
shifter value) incompatible (opticsIMRadioTrsCommonMib)
with actual HW
Provisioned shifter value RxDivFail
incompatible with actual HW (opticsIMRadioTrsCommonMib)
Provisioned Tx Power IncompatiblePTX
incompatible with actual HW (opticsIMRadioTrsCommonMib)
Receiving Function Failure RxFail
(tsdimSnmpNEMib)
Transmission Function TxFail
Failure (tsdimSnmpNEMib)
Demodulation Function DemFail RadioPDHTTPBidTable 20101
Failure (tsdimSnmpNEMib) (opticsIMRadioTrsPdhMib) 20100
Loss of Signal for the ModLOS
Modulation Function (tsdimSnmpNEMib)
Modulation Function Failure ModFail
(tsdimSnmpNEMib)
Loss of Alignment LossOfAlignment RxStaticDelayTable 1; 99
(tsdimSnmpNEMib) (opticsIMRadioSwtcMib)
09 RELEASED
8BW 03598 0000 DSZZA 167/ 182
(note 1) 1xx01 in case of 1+0 configurations, 1xx99 in case of 1+1 configurations.
(note 2) 20101 in case of 1+0 configurations, 20199 in case of 1+1 configurations.
09 RELEASED
8BW 03598 0000 DSZZA 168/ 182
14.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).
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.
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
Equipment Alarms
Primary No Remote All

Alarms Alarms Alarms
Notification Type ASAP#2 ASAP#3 ASAP#4
SA NSA SA NSA SA NSA
HousekeepingAlarm WAR WAR MIN MIN MAJ MAJ
InternalCommunicationProblem MAJ MIN MAJ MIN MAJ MIN
LanFailure MIN MIN WAR WAR MIN MIN
RemoteNEFailure NAL NAL NAL NAL WAR WAR
ReplaceableUnitMissing MAJ MIN MAJ MIN MAJ MIN
ReplaceableUnitProblem MAJ MIN MAJ MIN MAJ MIN
ReplaceableUnitTypeMismatch MAJ MIN MAJ MIN MAJ MIN
StandByVersionMismatch MIN MIN MIN MIN MIN MIN
UnconfiguredEquipmentPresent WAR WAR WAR WAR WAR WAR
VersionMismatch MIN MIN MIN MIN MIN MIN
FirmwareDownloadOnGoing MIN MIN MIN MIN MIN MIN
09 RELEASED
8BW 03598 0000 DSZZA 169/ 182
Communication Alarms
Primary No Remote All

Notification Alarms Alarms Alarms
Config. ASAP#2 ASAP#3 ASAP#4
Type
SA NSA SA NSA 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

IncompatibleShifter (RxDivFail)
MAJ MIN MAJ MIN MAJ MIN
(note 1)
IncompatiblePTX WAR WAR WAR WAR WAR WAR
LossOfAlignment 1+1 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
(note 1) RxDivFail is the correct notification type, but the sw realizes a translation and then to CT, the
label IncompatibleShifter is shown.
09 RELEASED
8BW 03598 0000 DSZZA 170/ 182
APPENDIX A CRAT TERMINAL ACCESS CONTROL
A user is identified by a username and password.

A Graphical User Interface (CT) provides User login procedures (with the Show Equipment action) with
the username displayed on the sceen and the clear-text password not displayed on the screen. After 3
number of consecutive unsuccessful NE login attempts, the CT interface closes unsuccessful the login
procedure. To access to the NE a new Show Equipment action must be performed.
In case of LAC granted (Local Access Control is allowed) in the following paragraph the list of supported
features for each user profile and for Local or Remote access is showen.
The Local access means Local CT (LCT, by F Interface). The Remote access means Remote CT (RCT)
or NMS (NM).
For each functionality on user profile: Full indicates that the related screen is visible both for SET and
GET operation; Read Only indicates that the related screen is visible, but only for GET operations (to
see the MIB objects); Not Supported indicates that the related screen is not visible.
Instead, in case of LAC not granted (Local Access Control is not allowed) all features, if
supported, are allowed in the same way of Viewer profile (Read-only or Not Supported mode)
if not differently specified.
A.1 MENU ITEM FUNCTIONS
Construc CraftPerso
Administrator Operator Viewer
tor n
Configuration
Menu
RCT RCT RCT
LCT & NM LCT & LCT RCT LCT &
NM NM NM
Alarm Severities Full Full Full Full Read Only
NE Time Full Full Full Full Read Only
Local Full Full Read Only Full Read Only
NTP Full Full Full Full Read Only
Network Etherne
Full Full Read Only Full Read Only
Config. t
IP Full Full Read Only Full Read Only
Routing Read Only Read Only Read Only Read Only Read Only
System Setting Full Full Read Only Full Read Only
09 RELEASED
8BW 03598 0000 DSZZA 171/ 182
Construc CraftPerso
tor n
Configuration
Menu
RCT RCT RCT
NM NM NM
NEType Read Not Read

Quick Full Not Supported Full Not Supported
&Market Only Supported Only
Config.
Capacity
Read Not Read
&Modulat Full Not Supported Full Not Supported
Only Supported Only
ion
Impeden Not
Full Not Supported Full Not Supported
ce Supported
Tributary Not
Conf Supported
Criteria
Not
Radio Full Not Supported Full Not Supported
Supported
prot.
Criteria
Not
Mux/De Full Not Supported Full Not Supported
Supported
mux prot.
Criteria
Not
HST Tx Full Not Supported Full Not Supported
Supported
prot.
ATPC Not
enable Supported
RTPC-
Read Not Read
Nominal Not Supported Not Supported
Only Supported Only
Power
RTPC-Tx Not
Power Supported
Read Not Read

Shifter Full Not Supported Full Not Supported
Only Supported Only
Read Not Read

Tx Freq. Full Not Supported Full Not Supported
Only Supported Only
Read Not Read

Rx Freq. Full Not Supported Full Not Supported
Only Supported Only
Local Read Not Read

conf. Only Supported Only
Not
OSPF Ful Not Supported Ful Not Supported
Supported
09 RELEASED
8BW 03598 0000 DSZZA 172/ 182
Construc CraftPerso
tor n
Configuration
Menu
RCT RCT RCT
NM NM NM
Not
IP static Ful Not Supported Ful Not Supported
Supported
Not
NMS RF Ful Not Supported Ful Not Supported
Supported
NMS Not
Ful Not Supported Ful Not Supported
V11 Supported
NMS Not
Ful Not Supported Ful Not Supported
G703 Supported
Not
Ethernet Ful Not Supported Ful Not Supported
Supported
RCT NM
Not
Users Not Not
Full Sup Not Supported Not Supported
manag. Full Supported Supported
port
Profile ed
Manag. RCT NM RCT NM RCT NM
Change Not Not
Not Not
passwo Full Sup Full Full Full Sup
Full Supported Full Supp Full
rd port port
orted
ed ed
09 RELEASED
8BW 03598 0000 DSZZA 173/ 182
Diagnosis Administrat Constru
Operator CraftPerson Viewer
Menu or ctor
LCT LCT LCT

& NM & NM & NM
NM LCT RCT
RCT RCT RCT
Full Full Full Read

Full Full Full
(note1) (note 1) Only
Log Read Read

Read Only Read Only Read Only
Browsing Only Only
Performanc Read Read

- - Read Only - - Read Only
e Data Only Only
Remote Read
Read Only Read Only Read Only Read Only
Inventory Only
Abnormal Read
Condition Only
Summary Read
Block Only
Current
Read
Configuratio Read Only Read Only Read Only Read Only
Only
n View
(note 1) On NM the AS functionality are partially supported (some buttons on the screen are disabled).
09 RELEASED
8BW 03598 0000 DSZZA 174/ 182
Administrator Constructor Operator CraftPerson Viewer
Supervision
Menu
LCT&RCT&NM NM LCT&RCT&NM LCT&RCT LCT&RCT&NM
Access State
(note 1) Full Full Full Full Not Supported
Restart NE
Full Not Supported Not Supported Full Not Supported
Mib
Management
Full Not Supported Not Supported Full Not Supported
SW Key Read Only Read Only Read Only Read Only Read Only
(note 1) For Administratior, Constructor, Operator and Craftperson user profile the Access State feature
is allowed in Full mode also if LAC is not granted (to require the LAC granted).
09 RELEASED
8BW 03598 0000 DSZZA 175/ 182
SW
Download
Menu
Server
Access
Configuration Full Full Not Supported Full Not Supported
Init SW
Download
Full Full Not Supported Full Not Supported
SW Status
Full Full ReadOnly Full ReadOnly
A.2 Functions View

Equipment
Equipment
Read Only Read Only Read Only Read Only Read Only
Type
User Label Read Only Read Only Read Only Read Only Read Only
Alarm Profile Full Full Full Full Read Only
Remote
Inventory
09 RELEASED
8BW 03598 0000 DSZZA 176/ 182
External
Points
(IN/OUT)
User
Full Full Full Full Read Only
Label
Input Polarity Full Full Read Only Full Read Only
Alarm
Profile
User
Label
Polarity Full Full Read Only Full Read Only
External
Output Full Full Read Only Full Read Only
State
Criteria Full Full Read Only Full Read Only
Event Full Full Read Only Full Read Only
Line Interface
LCT&
LCT&RCT&NM NM LCT&RCT LCT&RCT&NM
RCT&NM
NMS Interfaces (Alarm

Profile)
Signal
Mode
Line RAI
Insertion
E1
Radio RAI
Insertion
Alarm
Profile
Signal
Mode
Line
Coding
DS1
Line
Length
Alarm
Profile
09 RELEASED
8BW 03598 0000 DSZZA 177/ 182
Line Interface
LCT&
LCT&RCT&NM NM LCT&RCT LCT&RCT&NM
RCT&NM
Signal
Mode
DS3
Alarm
Profile
Status Full Full Full Full Read Only
Tx-FCS
Discard
Error
DATA-
Frames
Configuration
Rx-FCS
Discard
Error
Frames
Alarm
Profile
Default
Rate
Auto
Negotiation Full Full Read Only Full Read Only
DATA-Auto Status
Negotiation
Capability
Advertised
Restart Full Full Read Only Full Read Only
09 RELEASED
8BW 03598 0000 DSZZA 178/ 182
Craft
Administrator Constructor Operator Viewer
Person
Performance Monitoring
LCT& LCT& LCT& LCT&

NM NM NM NM
RCT RCT RCT RCT
Threshold Tables Full Full Read Only Full Read Only
Configuration Full Full Full Full Read Only

Start
Full Full Full Full Not Supported
Stop
Refresh
CD Full Full Full Full Full
Counters (note 1)
Management Reset
Collect
- Full Full - Full - - Full
(note 1)
Not
Archiving - Full Full - Full - -
Supported
Read
HD Counters Management Read Only Read Only Read Only Read Only
Only
(note 1) Also in case of LAC not granted this feature is accessible in Full mode.
09 RELEASED
8BW 03598 0000 DSZZA 179/ 182
Radio
RCT& LCT& LCT&
LCT NM LCT RCT
NM RCT&NM RCT&NM
Tx Local
Mute
Tx Remote
Configuration Full Full Read Only Full Read Only
Mute
Alarm Profile Full Full Full Full Read Only
Tx Value Full Full Read Only Full Read Only
Frequency Rx Value Full Read Only Read Only Full Read Only
Read Read
Shifter Full Read Only Read Only Full Read Only
Only Only
RTPC Tx Power Full Full Read Only Full Read Only
Enabling Full Full Full Full Read Only
ATPC Range Full Full Read Only Full Read Only

Full
Threshold Full Read Only Full Read Only
Interval Full Full Full Full Full

Sample
Power Full Full Full Full Full
Time
Measurement
File
(note 1) Full Full Full Full Full
Management
Start Full Full Full Full Full
(note 1) Also in case of LAC not granted this feature is accessible in Full mode.
09 RELEASED
8BW 03598 0000 DSZZA 180/ 182
Protection Schemes
LCT& LCT& LCT& LCT&
NM
RCT&NM RCT&NM RCT RCT&NM
Scheme
Configuration
Mux/Demux
Protection
Commands Full Full Read Only Full Read Only
Scheme
Configuration

Radio
Protection Static Delay-
Manual Full Full Read Only Full Read Only
Operation
Static Delay-
Not
Automatic Full Full Full Read Only
Supported
(note 1)
Scheme
Configuration
HST
protection
(note 1) In case of LAC not granted this feature is Not-Supported.
09 RELEASED
8BW 03598 0000 DSZZA 181/ 182
Loopback
LCT&
RCT& LCT&
LCT NM RCT& LCT RCT
NM RCT&NM
NM
Read
IDU CABLE Full Read Only Read Only Read Only Full Read Only
Only
Read
ODU CABLE Full Read Only Read Only Read Only Full Read Only
Only
Read
RF Full Read Only Read Only Read Only Full Read Only
Loopback Only
Config. E1/DS1-Tx NE
E3/DS3-Tx NE
E1/DS1-Rx FE
E3/DS3-Rx FE
E1/DS1-Rx NE
E3/DS3-Rx NE
09 RELEASED
8BW 03598 0000 DSZZA 182/ 182

ulsSysSpecRel2 0Ed9Rel

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ulsSysSpecRel2 0Ed9Rel

Caricato da

Copyright:

Formati disponibili

Site

Originators ULS 2.0

SNMP Management Interface

RELATED DOCUMENTS ........................................................................................................................... 8

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

Date Edition Comments

Added on predefined ASAP Severity the ModFail alarm.

The document is not revised in a review meeting due to the publishing

[4] Optics-IM: Support Domain (SNMP)

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

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

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

[8] Optics-IM: Radio Domain (SNMP)

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

[10] Optics-IM: Overhead Domain (SNMP)

[11] Optics-IM: Security Domain (SNMP)

[12] Optics-IM: List of SNMP Events

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

[14] Ethernet Physical Interface Management

[15] SNMP Management Functions

[17] SNMP Management Functions

[18] Ethernet Port Management

[19] SNMP Management Functions

[20] Ethernet Performance Monitoring

[21] SNMP Management Functions

Market Tributary Modulation

2.1 Functional Description

• Signal Protection switch (if any)

• Radio Physical Interface (AWY)

• one radio channel (1+0 configurations);

Indooor Part (IDU)

Main Scalable Unit Ch#1

Figure 1. Main Scalable IDU unit

Extension Scalable Unit Ch#0

Figure 2. Extension Scalable IDU unit

Outdoor Part (ODU)

3.2.1 Shelves Equipment Types

(note 1) 1.1.0.0 IDU Main Scalable Shelf IDU-M IDU Ch#1

(note 2) All the 1+0 configurations.

(note 3) All the 1+1 configurations.

(note 4) Not supported on ULS 2.0.0

3.2.2 Slots and Sub-slots Equipment Types

Position Allowed Equipment Type Allowed Equipment Label

1.1.1.0 Scalable Main Unit ±24 V Supply M24S IDU/MAIN Ch#1

Scalable Main Unit ±48/±60 V Range Supply M4860S

Scalable Main Unit ±24/±60 V Range Supply M2460S

1.1.1.1 8xE1/DS1 plug-in unit P8E1DS1 IDU/MAIN/<note 1> Ch#1

1xE3/DS3 plug-in unit P1E3DS3

2xEthernet plug-in Scalable unit P2DATAS

(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1

Position Allowed Equipment Type Allowed Equipment Label

1.3.1.0 Scalable Extension Unit ±24 Supply E24S IDU/EXT Ch#0

Scalable Extension Unit ±48/±60 V Range Supply E4860S

Scalable Extension Unit ±24/±60 V Range Supply E2460S

1.3.1.1 8xE1/DS1 plug-in unit P8E1DS1 IDU/EXT/<note 1> Ch#0

1xE3/DS3 plug-in unit P1E3DS3

(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1

No slot can be defined inside the Electrical ODU.

• Main Unit (M24S, M4860S, M2460S)

• Extension Unit (E24S, E4860S, E2460S)

• Ethernet plug-in (P2DATAS)

• PDH Tributary optional plugs-in (P8E1DS1, P1E3DS3)