ED 07 RELEASED It 1

8BW 03598 0000 DSZZA 1/ 181




Site
VIMERCATE



Originators
D.Spreafico

ULS 2.0

System Specification

SNMP Management Interface

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








Approvals


Name
App.

G. Gariani

Name
App.






07 RELEASED It 1


8BW 03598 0000 DSZZA 2/ 181


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 ............................................................................................... 17
3.4 Equipment Protection Switching Management...................................................................... 18
3.5 External Points Management ................................................................................................... 19
3.6 Management Functions ............................................................................................................ 20
3.6.1 Functional Objects Creation................................................................................................. 33
3.7 Supported Objects and Naming Rules ................................................................................... 34
4 TRANSMISSION INTERFACES (IFTABLE) ..................................................................................... 36
4.1 Management Functions ............................................................................................................ 36
4.2 SNMP Tables.............................................................................................................................. 37
4.2.1 Supported objects................................................................................................................ 37
4.3 Naming Rules ............................................................................................................................ 37
5 SDH/PDH TRANSMISSION DOMAIN............................................................................................... 39
07 060213 ECO-0000029182
G.Gariani D. Spreafico
06 050829 ECO-0000023942
G.Gariani C. Pasqualini, D. Spreafico
01 040531
R. Pellizzoni G.Gariani C. Pasqualini
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
ULS 2.0
System Specification
SNMP Management Interface





07 RELEASED It 1


8BW 03598 0000 DSZZA 3/ 181


5.1 Functional Description ............................................................................................................. 39
5.2 Management Functions............................................................................................................ 43
5.3 Supported Objects and Naming Rules ................................................................................... 57
6 ETHERNET TRANSMISSION DOMAIN............................................................................................ 59
6.1 Functional Description ............................................................................................................. 59
6.2 Management Functions............................................................................................................ 62
6.2.1 Ethernet Physical Interface Management............................................................................ 62
6.2.2 Ethernet Port Management.................................................................................................. 66
6.2.3 GFP Provider Layer Management ....................................................................................... 70
6.2.4 GFP_T Management ........................................................................................................... 71
6.3 Supported Objects and Naming Rules ................................................................................... 72
7 RADIO DOMAIN................................................................................................................................ 73
7.1 Functional Description ............................................................................................................. 73
7.2 Management Functions............................................................................................................ 76
7.3 Supported Objects and Naming Rules ................................................................................. 100
8 SUPPORT DOMAIN ........................................................................................................................ 103
8.1 Functional Description ........................................................................................................... 103
8.2 Management Functions.......................................................................................................... 108
8.3 Supported Objects and Naming Rules ................................................................................. 123
9 COMMUNICATION AND ROUTING DOMAIN................................................................................ 128
9.1 Functional Description ........................................................................................................... 128
9.2 Management Functions.......................................................................................................... 128
9.3 Supported Objects and Naming Rules ................................................................................. 134
10 OVERHEAD DOMAIN.................................................................................................................. 136
10.1 Functional Description ........................................................................................................... 136
10.2 Management Functions.......................................................................................................... 136
10.3 Supported Objects and Naming Rules ................................................................................. 138
11 TEST DOMAIN............................................................................................................................. 140
11.1 Functional Description ........................................................................................................... 140
11.2 Management Functions.......................................................................................................... 140
11.3 Supported Objects and Naming Rules ................................................................................. 142
12 SDH/PDH PERFORMANCE MONITORING DOMAIN................................................................ 144
12.1 Functional Description ........................................................................................................... 144
12.2 Management Functions.......................................................................................................... 145
12.3 Supported Objects and Naming Rules ................................................................................. 152
13 SECURITY DOMAIN.................................................................................................................... 154
13.1 Functional Description (SNMP Interface) ............................................................................. 154
13.2 Management Functions.......................................................................................................... 157
13.3 Supported Objects and Naming Rules ................................................................................. 158
14 ALARMS ...................................................................................................................................... 160
14.1 Alarms Provided by Item HW................................................................................................. 160
14.2 Alarms Reported ..................................................................................................................... 164
14.2.1 Equipment Alarms ............................................................................................................. 164
14.2.2 Communication Alarms...................................................................................................... 165
14.3 Predefined ASAPs Severity ................................................................................................... 168
APPENDIX A CRAT TERMINAL ACCESS CONTROL ................................................................... 170
A.1 MENU ITEM FUNCTIONS........................................................................................................ 170




07 RELEASED It 1


8BW 03598 0000 DSZZA 4/ 181


A.2 Functions View........................................................................................................................ 175




07 RELEASED It 1


8BW 03598 0000 DSZZA 5/ 181


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.




07 RELEASED It 1


8BW 03598 0000 DSZZA 6/ 181


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.
The new inserted features are:
• 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




07 RELEASED It 1


8BW 03598 0000 DSZZA 7/ 181


• 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
The new inserted features are:
• 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.




07 RELEASED It 1


8BW 03598 0000 DSZZA 8/ 181


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
[16] GFP-provider Layer Management
3AL 81428 0020 DSZZA
[17] SNMP Management Functions
Annex to GFP-provider Layer Management Functional Specification
3AL 81428 0020 DSZZA




07 RELEASED It 1


8BW 03598 0000 DSZZA 9/ 181


[18] Ethernet Port Management
3AL 81428 0016 DSZZA
[19] SNMP Management Functions
Annex to Ethernet Port Management Functional Specification
3AL 81428 0016 DSZZA
[20] Ethernet Performance Monitoring
3AL 81428 0014 DSZZA
[21] SNMP Management Functions
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.




07 RELEASED It 1


8BW 03598 0000 DSZZA 10/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 11/ 181


– 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 and 2.0.3 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.




07 RELEASED It 1


8BW 03598 0000 DSZZA 12/ 181


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
2xE1 4QAM
4xE1 4QAM / 16QAM
8xE1 4QAM /16QAM
16xE1 4QAM / 16QAM
ETSI
1xE3 4QAM / 16QAM
4xDS1 4QAM
8xDS1 4QAM / 16QAM
16xDS1 4QAM / 16QAM
ANSI
(note 1)
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).




07 RELEASED It 1


8BW 03598 0000 DSZZA 13/ 181


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.





07 RELEASED It 1


8BW 03598 0000 DSZZA 14/ 181


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.




Figure 1. Main Scalable IDU unit




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.
Main Scalable Unit Ch#1
Extension Scalable Unit Ch#0




07 RELEASED It 1


8BW 03598 0000 DSZZA 15/ 181


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
Scalable
Configuration
Market
Type
Position
Allowed Equipment Type
Description
Allowed
Equipment
Type
Equipment
Label
(note 1) 1.1.0.0 IDU Main Scalable Shelf IDU-M IDU Ch#1
ETSI ODU 1+0 4/16 QAM ETSI ODU-E
1+0
1+0 ETH
(note 2)
ANSI
1.2.0.0
ODU 1+0 4/16 QAM ANSI
ODU-A
(note 4)
ODU Ch#1

(note 1) 1.1.0.0 IDU Main Scalable Shelf IDU-M IDU Ch#1
ETSI ODU 1+0 4/16 QAM ETSI ODU-E
ANSI
1.2.0.0
ODU 1+0 4/16 QAM ANSI
ODU-A
(note 4)
ODU Ch#1
(note 1) 1.3.0.0 IDU Extension Scalable Shelf IDU-E IDU Ch#0
ETSI ODU 1+0 4/16 QAM ETSI ODU-E
1+1
(note 3)
ANSI
1.4.0.0
ODU 1+0 4/16 QAM ANSI
ODU-A
(note 4)
ODU Ch#0

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

(note 4) Not supported on ULS 2.0.0






07 RELEASED It 1


8BW 03598 0000 DSZZA 16/ 181


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
Description
Allowed
Equipment
Type
Equipment Label
1.1.1.0 Scalable Main Unit ±24 V Supply
Scalable Main Unit ±48/±60 V Range Supply
Scalable Main Unit ±24/±60 V Range Supply
(note 2)
M24S

M4860S

M2460S
IDU/MAIN Ch#1
1.1.1.1 8xE1/DS1 plug-in unit
1xE3/DS3 plug-in unit
2xEthernet plug-in Scalable unit
P8E1DS1
P1E3DS3
P2DATAS
IDU/MAIN/<note 1> Ch#1
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.
• E3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in E3 mode
• DS3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in DS3 mode
Not supported on ULS 2.0.0.
• DATA, when the 2xDATA plug-in is provisioned.

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


IDU-E
Position Allowed Equipment Type
Description
Allowed
Equipmen
t Type
Equipment Label
1.3.1.0 Scalable Extension Unit ±24 Supply
Scalable Extension Unit ±48/±60 V Range Supply
Scalable Extension Unit ±24/±60 V Range Supply
(note 2)
E24S

E4860S

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 17/ 181


Table: Allowed board/plug-in types in IDU Scalable Extension 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.
• E3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in E3 mode
• DS3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in DS3 mode.
Not supported on ULS 2.0.0.

(note 2) Not supported on ULS 2.0.0 and ULS 2.0.1
ODU
No slot can be defined inside the Electrical ODU.

3.3 Remote Inventory Management
The Remote Inventory feature allows to store the information useful to identify the components of the
product.
From management point of view the Remote Inventory data will be provided by the following equipment
types:
• Main Unit (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)
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.





07 RELEASED It 1


8BW 03598 0000 DSZZA 18/ 181


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 Ch#1 is the channel active both for EPS and RPS protection schemes independently to RPS
command active.




07 RELEASED It 1


8BW 03598 0000 DSZZA 19/ 181


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
EventId
Allowed
Event
Allowed 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
Value
Configuration UserLabel ExternalState Polarity Criteria
Automatic
Event
Automatic
EventId
Read-only Read-only
Read-
write
Read-
only
Read-only Read-only
5 Fail IDU
6
All the 1+0
All the 1+1

Fail ODU
Ch#1
7 All the 1+1
on/
off
activeLow/
activeHigh
automatic
Fail ODU
Ch#0
-1





07 RELEASED It 1


8BW 03598 0000 DSZZA 20/ 181


3.6 Management Functions

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

Equipment

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 21/ 181


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
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-SET on equipmentAdministrativeState
F-2.6 Request Administrative
State
Y
This management function allows a managing system to request
whether the equipment is in or out of service.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-GET on equipmentAdministrativeState
Note F-2.6: Default value: inService.
F-2.7 Condition ASAP
Pointer
Y
This management function allows a managing system to configure
the ASAP Pointer associated to an equipment position.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-SET on equipmentAsapIndex
F-2.8 Request ASAP Pointer Y
This management function allows a managing system to request
the ASAP Pointer associated to an equipment position.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-GET on equipmentAsapIndex
F-2.9 Request Equipment
Label
Y
This management function allows a managing system to request
the label associated to an equipment position.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-GET on equipmentLabel
F-2.10 Request Affected
Objects List
N
This management function allows a managing system to request
the functional objects which are in operational dependency with an
equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMAffectedObjectListTable
Service Used
SNMP-GET on affectedObjectInstanceId

Function Equipment Status SN
MP
If
Function Description
F-2.11 Request Equipment
Operational State
Y
This management function allows the managing system to request
the operational state of an equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
Service Used
SNMP-GET on equipmentOperationalState





07 RELEASED It 1


8BW 03598 0000 DSZZA 22/ 181


Function Equipment
Notifications
SN
MP
If
Function Description
F-2.12 Report Equipment
Alarm
Y
This management function allows a managed system to report
equipment alarms.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentTable
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
MP
If
Function Description
F-2.13 Request Remote
Inventory Data
Y
This management function allows a managing system to request
the remote inventory data associated to an equipment.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteInventoryTable
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 23/ 181


SNMP-GET on:
• remoteInventoryStatus
• remoteInventoryCompanyIdentifier
• remoteInventoryMnemonic
• remoteInventoryCLEICode
• remoteInventoryPartNumber
• remoteInventorySoftwarePartNumber
• remoteInventoryFactoryIdentifier
• remoteInventorySerialNumber
• remoteInventoryDateIndentifier
• remoteInventoryDate
• remoteInventoryCustomerField

Function Tributary Ports
Impedance
SN
MP
If
Function Description
F-2.14 Condition E1
Tributary Ports Impedance
Y
This management function allows a managing system to configure
the impedance used by E1 tributary ports (balanced 120 Ohm or
unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-SET on opticsIMTribPortsImpedance
F-2.15 Request E1 Tributary
Ports Impedance
Y
This management function allows a managing system to request
the impedance used by E1 tributary ports (balanced 120 Ohm or
unbalanced 75 Ohm).
Scope
OPTICSIM-EQPT-MIB
Service Used
SNMP-GET on opticsIMTribPortsImpedance

Equipment Protection

Function Creation/Deletion SN
MP
If
Function Description
F-3.1 Create Equipment
Protection Group
N
This management function allows a managing system to allocate
an equipment protection group entry. The managing system has to
indicate in the creation request:
• the protection type (1+1 or 1:N)
• the mode of operation (revertive/non revertive)
The protection units to be created and their role are established by
the NE and cannot be assigned by the managing system.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRowStatus
object to “createAndGo” value
F-3.2 Delete Equipment N
This management function allows a managing system to delete an
equipment protection group entry and related protection units.




07 RELEASED It 1


8BW 03598 0000 DSZZA 24/ 181


Protection Group Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-SET on opticsIMEquipmentProtectionGroupRowStatus
object to “destroy” value

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

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 25/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 26/ 181


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
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
(on main protection unit)
Service Used
SNMP-SET on opticsIMEquipmentProtectionUnitSwitchCommand
(forcedSwitch or noRequest)
F-3.14 Initiate/Terminate
Forced Switch to a Working
Equipment
N
This management function allows the managing system to
initiate/terminate a forced switch from a protection equipment
(spare) to a working one (main). This management function is
applicable only in case of 1+1 not revertive protection type.
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the switch, both addressed to
the spare protection unit.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
(on spare protection unit)
Service Used
SNMP-SET on opticsIMEquipmentProtectionUnitSwitchCommand
(forcedSwitch or noRequest)

Function Protection Status SN
MP
If
Function Description
F-3.15 Request Equipment
Protection Scheme
Operational State
Y
This management function allows the managing system to request
the operational state of an equipment protection scheme.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionGroupTable
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionGroupOperationalState
F-3.16 Request Equipment
Protection Status
Y
This management function allows the managing system to request
the current state of an equipment protection unit.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
Service Used
SNMP-GET on:
• opticsIMEquipmentProtectionUnitSwitchCommand
• opticsIMEquipmentProtectionUnitSwitchCriteria
• opticsIMEquipmentProtectionUnitSwitchStatus
F-3.17 Request Equipment
Protection Switching Source
N
This management function allows the managing system to request
the source of the equipment switching request. This management
function is applicable only in case of dual ended switching.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
Service Used
SNMP-GET on:
opticsIMEquipmentProtectionUnitSwitchRequestSource




07 RELEASED It 1


8BW 03598 0000 DSZZA 27/ 181


F-3.18 Report Equipment
Protection Switch Event
N
This management function allows the managed system to report
any protection switch event to the managing system, such as:
• protection switching (forced, manual or automatic switch)
• protection release (release of forced, manual or automatic
switch)
• lockout, release lockout.
Scope
OPTICSIM-EQPT-MIB: opticsIMEquipmentProtectionUnitTable
Service Used
SNMP-TRAP opticsIMProtectionSwitchReporting on:
• opticsIMEquipmentProtectionUnitSwitchCommand
• opticsIMEquipmentProtectionUnitSwitchCriteria
• opticsIMEquipmentProtectionUnitSwitchStatus

External Points

Function Input Point
Configuration
SN
MP
If
Function Description
F-4.1 Condition External
Input Point User Label
Y
This management function allows a managing system to configure
the user label associated to an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-SET on inputPointUserLabel
F-4.2 Request External Input
Point User Label
Y
This management function allows a managing system to request
the user label associated to an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-GET on inputPointUserLabel
F-4.3 Request External Input
Point External State
Y
This management function allows a managing system to request
the state of an external input point (“on” when the alarm is raised,
“off” otherwise).
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-GET on inputPointExternalState
F-4.4 Condition External
Input Point ASAP Pointer
Y
This management function allows a managing system to configure
the ASAP Pointer associated to an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-SET on inputPointAsapIndex
F-4.5 Request External Input
Point ASAP Pointer
Y
This management function allows a managing system to request
the ASAP Pointer associated to an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-GET on inputPointAsapIndex
F-4.6 Condition External
Input Point Polarity
Y
This management function allows a managing system to configure
the polarity of an external input point.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 28/ 181


OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-SET on inputPointPolarity
F-4.7 Request External Input
Point Polarity
Y
This management function allows a managing system to request
the polarity of an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-GET on inputPointPolarity

Function Input Point Status SN
MP
If
Function Description
F-4.8 Request External Input
Point Operational State
Y
This management function allows the managing system to request
the operational state of an external input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointTable
Service Used
SNMP-GET on inputPointOperationalState

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

Function Output Point
Configuration
SN
MP
If
Function Description
F-4.10 Condition External
Output Point User Label
Y
This management function allows a managing system to configure
the user label associated to an external output point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointUserLabel
F-4.11 Request External
Output Point User Label
Y
This management function allows a managing system to request
the user label associated to an external output point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointUserLabel
F-4.12 Condition External
Output Point External State
Y
This management function allows a managing system to configure
the external state in order to command a remote control interface
(“on” when the command is raised, “off” otherwise).




07 RELEASED It 1


8BW 03598 0000 DSZZA 29/ 181


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
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointExternalState
F-4.13 Request External
Output Point External State
Y
This management function allows a managing system to request
the external state (on or off).
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointExternalState
F-4.18 Condition External
Output Point Criteria
Y This management function allows a managing system to condition
the output criteria (manual, automatic or remoteInputPoint). In
automatic control the external points are driven by defined events.
In manual control they are driven by the operator. In
remoteInputPoint the external point is automatically managed by
the agent with the values assumed by the object of the associated
remote input point.

Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointCriteria
F-4.14 Request External
Output Point Criteria
Y
This management function allows a managing system to request
the output criteria (manual or automatic). In automatic control the
external points are driven by defined events. In manual control they
are driven by the operator.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointCriteria
F-4.15 Condition External
Output Point Polarity
Y
This management function allows a managing system to configure
the polarity of an external output point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointPolarity
F-4.16 Request External
Output Point Polarity
Y
This management function allows a managing system to request
the polarity of an external output point.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointPolarity
F-4.19 Condition External
Output Point Automatic
Event
Y
This management function allows a managing system to configure
the event type associated to an output point when the
outputPointCriteria object is set to “automatic”. This event type is
defined setting the identifier (outputPointAutomaticEventId object)
associated to the event type string required. As a side effect of
this configuration, the agent must set the
outputPointAutomaticEvent object with the vent type string
associated to this identifier.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-SET on outputPointAutomaticEventId




07 RELEASED It 1


8BW 03598 0000 DSZZA 30/ 181


F-4.20 Request External
Output Point Automatic
Event
Y
This management function allows a managing system to request
the event type associated to an output point when the
outputPointCriteria object is set to “automatic”.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on:
• outputPointAutomaticEventId
• outputPointAutomaticEvent
F-4.21 Request External
Output Point Automatic
Events List
Y
This management function allows a managing system to request
the list of events that can be associated to the external output
points when an automatic management of an output point is active.
Scope
OPTICSIM-EQPT-MIB: opticsIMOutputPointAllowedEventsTable
Service Used
SNMP-GET on outputPointAllowedEvent

Function Output Point Status SN
MP
If
Function Description
F-4.17 Request External
Output Point Operational
State
Y
This management function allows the managing system to request
the operational state of an external output point entry.
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalOutputPointTable
Service Used
SNMP-GET on outputPointOperationalState

Function Input Point
Configuration for
Remotization
SN
MPIf
Function Description
F-4.22 Creation of
remotization of External
Input Point
N This management function allows a managing system to configure
the external input point (identified by inputPointIndex) to be
remotized on external output point of a specified Ne (identified by
IP address to be
provided).
Scope
OPTICSIM-EQPT-MIB:
opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-SET on inputPointRemotizationDestination
SNMP-SET on inputPointRemotizationRowStatus columnar object
to ‘createAndGo’ value.
F-4.23 Deletion of
remotization of External
Input Point
N This management function allows a managing system to delete the
remotization of the external input point (identified by
inputPointIndex).
Scope
OPTICSIM-EQPT-MIB:
opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-SET on inputPointRemotizationRowStatus columnar object
to ‘destroy’ value.
F-4.24 Request Remotization
N This management function allows a managing system to request
the IP address of remote NE on which the external input point have




07 RELEASED It 1


8BW 03598 0000 DSZZA 31/ 181


Destination to be remotized as output point.
Scope
OPTICSIM-EQPT-MIB:
opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-GET on inputPointRemotizationDestination

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

Function Input Point for
Remotization Manual
Control
SN
MP
If
Function Description
F-4.27 Condition Manual
Remotization
N This management function allows a managing system to trigger a
manual updating of the destination output point (‘updating’ value).
Scope
OPTICSIM-EQPT-MIB: opticsIMExternalInputPointRemotizationTable
Service Used
SNMP-SET on inputPointManualRemotization

Function Output Point
Configuration from
Remote Input Point
SN
MP
If
Function Description
F-4.28 Creation of
Remote External Input
Point
N This management function allows a managing system to identify the
remote external input point which caracteristics have to be provided
on local output point (identified by outputPointIndex).
The managing system has to provide the IP address of the agent
where the remote input point is physically present and the index
(remoteInputPointIndex) of the remote
opticsIMExternalInputPointTable.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteExternalInputPointTable
Service Used
SNMP-SET on
• RemoteInputPointAgent
• RemoteInputPointIndex
SNMP-SET on remoteInputPointRowStatus columnar object to




07 RELEASED It 1


8BW 03598 0000 DSZZA 32/ 181


‘createAndGo’ value.
F-4.29 Deletion of Remote
External Input Point
N This management function allows a managing system to delete the
configuration of local external output point (identified by
outputPointIndex) as remote input point
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteExternalInputPointTable
Service Used
SNMP-SET on remoteInputPointRowStatus columnar object to
‘destroy’ value.
F-4.30 Request Remote
Agent
N This management function allows a managing system to request the
IP address of agent where the remote input point is physically present
and the index of the remote input point on
opticsIMExternalInputPointTable.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteExternalInputPointTable
Service Used
SNMP-GET on
• remoteInputPointAgent
• remoteInputPointIndex

Function Output Point
from Remote Input Point
Status
SN
MP
If
Function Description
F-4.31 Request Last
Update from Remote
N This management function allows a managing system to request the
time of the last update received from the agent concerning the status
of the remote input point.
Scope
OPTICSIM-EQPT-MIB: opticsIMRemoteExternalInputPointTable
Service Used
SNMP-GET on remoteInputPointLastUpdate





07 RELEASED It 1


8BW 03598 0000 DSZZA 33/ 181


3.6.1 Functional Objects Creation

The following tables define the functional objects created by the agent as consequence of the equipment
provisioning process.

Functional Objects
Created
Creation Rules
6 opticsIMExternalInputPointEntry
7 opticsIMExternalOutputPointEntry
1 opticsIMAuxiliaryPITTPBidEntry
1 opticsIMEowDTMFTTPBidEntry
3 opticsIMPointToPointIPEntry
In all the configurations
1 opticsIMCtUserTable In all the configurations.
Entry related to the default administrator
user.
(note 2)
1 or 2 opticsIMCoderTTPEntry
1 or 2 opticsIMPdhFrameHopCurrentDataEntry
1 or 2 opticsIMLoopbackEntry [IDU cable loopback]
1 or 2 opticsIMLoopbackExtEntry [IDU cable loopback]
1 entry for in all the 1+0 configurations
2 entries in all the 1+1 configurations
1 opticsIMFrameTTPEntry In all the configurations
2 ifMauEntry
2 ifAutoMauEntry
2 opticsIMMauExtEntry
4 opticsIMEthConfEntry
1 opticsIMGFPConfEntry
In all the 1+0 and 1+1 ETH configurations
[RPS]
1 opticsIMRadioProtectionGroupEntry
2 opticsIMRadioProtectionUnitEntry
1 opticsIMRadioRxStaticDelayEntry
[EPS]
1 opticsIMEquipmentProtectionGroupEntry
2 opticsIMEquipmentProtectionUnitEntry
[PM]
1 opticsIMPdhFrameLinkCurrentDataEntry
In all the 1+1 configurations
1 opticsIMTxProtectionGroupEntry
2 opticsIMTxProtectionUnitEntry
In all the 1+1 HST configurations
1 or 2 opticsIMRadioPDHTTPBidEntry
1 or 2 opticsIMRadioFrequencyEntry
1 or 2 opticsIMRadioShifterEntry
1 or 2 opticsIMRadioTxPowerEntry
1 or 2 opticsIMRadioTxMuteEntry
1 or 2 opticsIMRadioAnalogueMeasureEntry
1 entry in all the 1+0 configurations
2 entries in all the 1+1 configurations
(note 1)
2 or 4 opticsIMLoopbackEntry [ODU loopbacks]
2 or 4 opticsIMLoopbackExtEntry [ODU loopbacks]
2 entry in all the 1+0 configurations
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.












07 RELEASED It 1


8BW 03598 0000 DSZZA 34/ 181



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)
Configuration Description
Indexes
Value
opticsIMEqptMib
opticsIMEquipmentTable
equipmentExpectedTypeId
equipmentExpected
equipmentActual
equipmentAdministrativeState
equipmentOperationalState
equipmentAsapIndex
equipmentLabel
See the Allowed Equipment Type section.
opticsIMRemoteInventoryTable
remoteInventoryStatus
remoteInventoryCompanyIdentifier
remoteInventoryMnemonic
remoteInventoryCLEICode
remoteInventoryPartNumber
remoteInventorySoftwarePartNumber
remoteInventoryFactoryIdentifier
remoteInventorySerialNumber
remoteInventoryDateIdentifier
remoteInventoryDate
remoteInventoryCustomerField
See the Allowed Equipment Type and Remote
Inventory sections.
opticsIMEquipmentProtectionGroupTable
opticsIMEquipmentProtectionGroupType
opticsIMEquipmentProtectionGroupRevertive
opticsIMEquipmentProtectionGroupOperational
State
All the 1+1 EPS 4
opticsIMEquipmentProtectionUnitTable
opticsIMEquipmentProtectionUnitChannelNum
ber
opticsIMEquipmentProtectionUnitType
opticsIMEquipmentProtectionUnitSwitchComm
and
opticsIMEquipmentProtectionUnitSwitchCriteria
opticsIMEquipmentProtectionUnitSwitchStatus
All the 1+1 EPS – Ch#1
EPS – Ch#0
4; 1
4; 0
opticsIMExternalInputPointTable
inputPointUserLabel
inputPointExternalState
inputPointPolarity
inputPointAsapIndex
inputPointOperationalState
All 1..6




07 RELEASED It 1


8BW 03598 0000 DSZZA 35/ 181



Table Entry
Supported Objects
(Table/Scalar)
Configuration Description
Indexes
Value
External output points

1..4

opticsIMExternalOutputPointTable
outputPointUserLabel
outputPointExternalState
outputPointPolarity
outputPointCriteria
outputPointOperationalState
outputPointAutomaticEventId
outputPointAutomaticEvent
All
Summarizing
(see the External
Points Management
section)
5..7
opticsIMOutputPointAllowedEventsTable
outputPointAllowedEvent
All See the External
Points Management
section.
1..8
opticsIMTribPortsImpedance
opticsIMHousekeepingAlarmRaise
opticsIMHousekeepingAlarmClear
opticsIMAlarmReplaceableUnitProblemRaise
opticsIMAlarmReplaceableUnitProblemClear
opticsIMAlarmReplaceableUnitMissingRaise
opticsIMAlarmReplaceableUnitMissingClear
opticsIMAlarmReplaceableUnitTypeMismatchRai
se
opticsIMAlarmReplaceableUnitTypeMismatchCle
ar
opticsIMAlarmUnconfiguredEquipmentPresentR
aise
opticsIMAlarmUnconfiguredEquipmentPresentCl
ear
opticsIMAlarmVersionMismatchRaise
opticsIMAlarmVersionMismatchClear
opticsIMAlarmLanFailureRaise
opticsIMAlarmLanFailureClear
opticsIMAlarmStandByVersionMismatchRaise
opticsIMAlarmStandByVersionMismatchClear
opticsIMAlarmFirmwareDownloadOnGoingRaise
opticsIMAlarmFirmwareDownloadOnGoingClear





07 RELEASED It 1


8BW 03598 0000 DSZZA 36/ 181


4 TRANSMISSION INTERFACES (IFTABLE)

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

ifTable
Interface
Type
Interface
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)
(note 4)
28 560 000 (16DS1)
(note 4)
14 280 000 (8 DS1)
(note 4)
Radio PDH Frame
(note 2)
up to 2 PDH Radio 1 (other)
7 140 000 (4 DS1)
(note 4)
V11 64 64 000
Auxiliary (note 3) 1
G703 66 64 000
3 PPP 23 64 000
1 Local Ethernet 6 10 000 000 / 100 000 000 Management Interfaces
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.
4.1 Management Functions

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 37/ 181



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
Type
ifTable
ifIndex
Associated
Mib
Associated
Table
opticsIMRadioTrsPdhMib opticsIMRadioPDHTTPBidTable Radio PDH
Frame
20101
20100
opticsIMRadioTrsCommonMib opticsIMRadioFrequencyTable
opticsIMRadioShifterTable (note 4)
opticsIMRadioTxPowerTable
opticsIMRadioAnalogueMeasuresTable
opticsIMRadioTxMuteTable
E1 Tx 1yy01 or
1yy99
(note 1)
opticsIME1pPITTPTable
opticsIMPdhRAIInsertionTable
DS1 Tx (note 4) 1yy01 or
1yy99
(note 1)
opticsIMDs1pPITTPTable
E3 Tx 10101 or
10199
(note 3)
opticsIME3pPITTPTable
DS3 Tx (note 4) 10101 or
10199
(note 3)
opticsIMTrsCommonMib
opticsIMDs3pPITTPTable
mauMod ifMauTable
Ethernet Tx
1xx01
(note 2)
opticsIMEthNEMib opticsIMMauExtTable
Auxiliary 301 opticsIMOverheadMib opticsIMAuxiliaryPITTPBidTable
PPP-RF 1
PPP-V11 2
PPP-G703 3
opticsIMPointToPointIPTable
Local Ethernet 100
opticsIMCommRouMib
opticsIMLocalEthernetTable
LAPD/F 200 - -




07 RELEASED It 1


8BW 03598 0000 DSZZA 38/ 181



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

(note 4) Not supported on ULS 2.0.0




07 RELEASED It 1


8BW 03598 0000 DSZZA 39/ 181


5 SDH/PDH TRANSMISSION DOMAIN
5.1 Functional Description
1+1 Configurations Functional View

Tx Functional View













Rx Functional View
















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)
opticsIMDS3pPITTPTable (note 1)
• <trib>-RX => opticsIME1PathTTPTable
opticsIME3PathTable
opticsIMDS1PathTTPTable (note 1)
opticsIMDS3PathTTPTable (note 1)
• MUX, DEMUX => opticsIMFrameTTPTable
• Aggregate => opticsIMCoderTTPTable
• Radio => opticsIMRadioPDHTTPBidTable

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

<trib>-RX
(source)
MUX
(source)
Aggregate
(source)
Radio
(source)
Aggregate
(source)
Radio
(source)
Ch#1
Ch#0
<trib>-TX
(sink)
Aggregate
(sink)
Radio
(sink)
Aggregate
(sink)
Radio
(sink)
RPS hitless
<trib>-RX
(sink)
DEMUX
(sink)
Ch#1
Ch#0
<trib>-TX
(source)




07 RELEASED It 1


8BW 03598 0000 DSZZA 40/ 181


(note 1) Not supported on ULS 2.0.0.






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
Type
NE
Configurations
Allowed Frame
Structures
All the Radio configurations 8E1/DS1
(without Ethernet interface)
twoE1, fourE1, eightE1
All the Radio configurations 8E1/DS1 (with
Ethernet interface)
twoE1, fourE1, eightE1, sixteenE1
All the Radio configurations 16E1/DS1 twoE1, fourE1, eightE1, sixteenE1
ETSI
All the Radio configurations E3/DS3 oneE3
All the Radio configurations 8E1/DS1
(without Ethernet interface)
fourDS1, eightDS1
All the Radio configurations 8E1/DS1 (with
Ethernet interface)
fourDS1, eightDS1, sixteenDS1,
oneDS3
All the Radio configurations 16E1/DS1 fourDS1, eightDS1, sixteenDS1
ANSI
(note 1)
All the Radio configurations E3/DS3 oneDS3

(note 1) Not supported on ULS 2.0.0

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
Configuration
NE
Configurations
Functional Objects Created
twoE1 All the Radio configurations
8E1/DS1 or 16E1/DS1
2 opticsIME1pPITTPEntry
2 opticsIMPdhRAIInsertionEntry (note 1)
2 opticsIME1PathTTPEntry
2 opticsIMPdhRAIInsertionEntry (note 2)
fourE1 All the Radio configurations
8E1/DS1 or 16E1/DS1
4 opticsIME1pPITTPEntry
4 opticsIMPdhRAIInsertionEntry (note 1)
4 opticsIME1PathTTPEntry
4 opticsIMPdhRAIInsertionEntry (note 2)
eightE1 All the Radio configurations
8E1/DS1 or 16E1/DS1
8 opticsIME1pPITTPEntry
8 opticsIMPdhRAIInsertionEntry (note 1)
8 opticsIME1PathTTPEntry
8 opticsIMPdhRAIInsertionEntry (note 2)
All the Radio configurations
8E1/DS1 (with Ethernet interface)
8 opticsIME1pPITTPEntry
8 opticsIMPdhRAIInsertionEntry (note 1)
8 opticsIME1PathTTPEntry
8 opticsIMPdhRAIInsertionEntry (note 2)
sixteenE1
All the Radio configurations
16E1/DS1
16 opticsIME1pPITTPEntry
16 opticsIMPdhRAIInsertionEntry (note 1)




07 RELEASED It 1


8BW 03598 0000 DSZZA 41/ 181


Frame Structure
Configuration
NE
Configurations
Functional Objects Created
16 opticsIME1PathTTPEntry
16 opticsIMPdhRAIInsertionEntry (note 2)
oneE3 All the Radio configurations
E3/DS3
1 opticsIME3pPITTPEntry
1 opticsIME3PathTTPEntry
fourDS1 (note 1) All the Radio configurations
8E1/DS1 or 16E1/DS1
4 opticsIMDs1pPITTPEntry
4 opticsIMDs1PathTTPEntry
eightDS1 (note 3)

All the Radio configurations
8E1/DS1 or 16E1/DS1
8 opticsIMDs1pPITTPEntry
8 opticsIMDs1PathTTPEntry
All the Radio configurations
8E1/DS1 (with Ethernet interface)
8 opticsIMDs1pPITTPEntry
8 opticsIMDs1PathTTPEntry
sixteenDS1 (note
3)
All the Radio configurations
16E1/DS1
16 opticsIMDs1pPITTPEntry
16 opticsIMDs1PathTTPEntry
oneDS3 (note 3) All the Radio configurations
E3/DS3
1 opticsIMDs3pPITTPEntry
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

(note 3) Not supported on ULS 2.0.0

Additionally, for each pPI and Path functional object created, the associated loopback objects are
created too, according to the schema described in the following table.

Tributary Objects
Created
Loopback Objects Created
x pPITTP
(note 1)
y opticsIMLoopbackEntry
y opticsIMLoopbackExtEntry
x PathTTP
(note 1)
y opticsIMLoopbackEntry
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.





07 RELEASED It 1


8BW 03598 0000 DSZZA 42/ 181



‘opticsIMDs1Line
Lenght’ value
Range
0 0-133 ft
1 133-266 ft
2 266-399 ft
3 399-533 ft
4 533-655 ft









07 RELEASED It 1


8BW 03598 0000 DSZZA 43/ 181


5.2 Management Functions

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

Function Configuration SN
MP
If
Function Description
F-1.1 Request TTP ASAP
Pointer
Y
This management function allows a managing system to request
the ASAP Pointer associated to a trail termination point.
Scope
OPTICSIM-TRS-xxxx-MIB: Trail Termination Point
(xTTPBidTable)
Service Used
SNMP-GET on xTTPBidAsapIndex columnar object
Note F-1.1: Supported on the TPs managed in this release.
F-1.2 Condition TTP ASAP
Pointer
Y
This management function allows a managing system to
configure the ASAP Pointer associated to a trail termination point.
Scope
OPTICSIM-TRS-xxxx-MIB: Trail Termination Point
(xTTPBidTable)
Service Used
SNMP-SET on: xTTPBidAsapIndex columnar object
Note F-1.2: Supported on the TPs managed in this release.

Function TP Status SN
MP
If
Function Description
F-1.3 Request TTP
Operational State
Y
This management function allows the managing system to
request the operational state of a trail termination point.
Scope
OPTICSIM-TRS-xxxx-MIB: Trail Termination Point
(xTTPBidTable)
Service Used
SNMP-GET on xTTPBidOperationalState columnar object

SDH Functions
Trail Termination Point

Function Configuration SN
MPI
f
Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 44/ 181


F-1.xx All the functions N



Function Notifications SN
MPI
f
Function Description
F-1.xx All the functions N


Automatic Laser Shutdown

Functions SN
MPI
f
Function Description
F-1.xx All the functions N


PDH Frame Functions

Function Configurations SN
MPI
f
Function Description
F-2.1 Request Frame
Structure Configuration
Y
This management function allows the managing system to
request the configuration of the frame structure.
Scope
OPTICSIM-TRS-PDH-MIB:
opticsIMFrameStructureConfiguration
Service Used
SNMP-GET on the scalar object
opticsIMFrameStructureConfiguration
F-2.2 Condition Frame
Structure Configuration
Y
This management function allows the managing system to set the
configuration of the frame structure.
Scope
OPTICSIM-TRS-PDH-MIB:
opticsIMFrameStructureConfiguration
Service Used
SNMP-SET on the scalar object
opticsIMFrameStructureConfiguration
F-2.3 Request Link Identifier
Parameters
N
This management function allows the managing system to
request the value of the parameters related to the Link Identifier
management:
• The expected mode on the receiving NE
(opticsIMLinkldExpectedMode).
If the disabled mode is selected the link identifier mismatch
detection is disabled. If the enabled mode is selected the
expected value is contained in the opticsIMLinkIdExpectedValue




07 RELEASED It 1


8BW 03598 0000 DSZZA 45/ 181


scalar object.
• The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
• The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMLinkldExpectedMode
• opticsIMLinkIdExpectedValue
• opticsIMLinkIdSentValue
F-2.4 Condition Link
Identifier Parameters
N
This management function allows the managing system to
condition the parameters related to the Link Identifier
management:
• The expected mode on the receiving NE
(opticsIMLinkldExpectedMode).
• The expected value on the receiving NE
(opticsIMLinkIdExpectedValue).
• The transmitted value on the transmitting NE
(opticsIMLinkldSentValue).
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMLinkIdMngt
Service Used
SNMP-SET on:
• opticsIMLinkldExpectedMode
• opticsIMLinkIdExpectedValue
• opticsIMLinkIdSentValue
Note F-2.4: Allowed values: 0-15.
F-2.5 Condition BER Alarms
Thresholds
N
This management function allows the managing system to set the
thresholds used to raise the highBER and lowBER alarms. Both
these values must be included in the related allowed range. The
high BER threshold must be greater than the low BER one.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-SET on the following scalar objects:
• opticsIMHighBERThr
• opticsIMLowBERThr
F-2.6 Request BER Alarms
Thresholds
N
This management function allows the managing system to
request the thresholds used to raise respectively a PDH highBER
and lowBER alarms.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMHighBERThr
• opticsIMLowBERThr
F-2.7 Request BER Alarms
Thresholds Ranges
N
This management function allows the managing system to
request the minimum and maximum values allowed for the
thresholds used to raise the PDH highBER and lowBER alarms.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMHighBERMinThr
• opticsIMHighBERMaxThr




07 RELEASED It 1


8BW 03598 0000 DSZZA 46/ 181


• opticsIMLowBERMinThr
• opticsIMLowBERMaxThr
F- 2.11 Request interleaving
status
N This management function allows the managing system to
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
interleaving function
N This management function allows the managing system to
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
BER Thresholds
N This management function allows the managing system to set the
BER threshold used to raise the EW alarm. This value must be
included in the allowed range.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-SET on the following scalar objects:
• opticsIMEWBERThr
F- 2.14 Request EW alarm
BER Thresholds
N This management function allows the managing system to
request the BER thresholds used to raise a EW alarm.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMEWBERThr
F- 2.15 Request EW alarm
BER Thresholds Ranges
N This management function allows the managing system to
request the minimum and maximum values allowed for the BER
thresholds used to raise EW alarm.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMBERThresholdMngt
Service Used
SNMP-GET on the following scalar objects:
• opticsIMEWBERMinThr
• opticsIMEWBERMaxThr

Function Notifications SN
MPI
f
Function Description
F-2.9 Report PDH Frame
Alarms
Y
This management function allows a managed system to report
transmission alarms related to the PDH frame.
Scope
OPTICSIM-TRS-PDH-MIB: opticsIMFrameTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmLossOfFrameRaise
• opticsIMAlarmLossOfFrameClear
• opticsIMAlarmLinkIdentifierMismatchRaise
• opticsIMAlarmLinkIdentifierMismatchClear
F-2.10 Report PDH Coder
Alarms
Y
This management function allows a managed system to report
transmission alarms related to the PDH coder.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 47/ 181


OPTICSIM-TRS-PDH-MIB: opticsIMCoderTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmCableLOSRaise
• opticsIMAlarmCableLOSClear
• opticsIMAlarmLossOfFrameRaise
• opticsIMAlarmLossOfFrameClear
• opticsIMAlarmHighBERRaise
• opticsIMAlarmHighBERClear
• opticsIMAlarmLowBERRaise
• opticsIMAlarmLowBERClear

PDH Tributaries Functions

Function Configuration SN
MP
If
Function Description
F-3.1 Request E1 Signal
Processing Mode
Y
This management function allows a managing system to request
which processing mode is activated on an E1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
Service Used
SNMP-GET on e1pPITTPSignalMode
F-3.2 Condition E1 Signal
Processing Mode
P
This management function allows a managing system to condition
the E1 signal processing mode. The allowed signal processing
modes are:
• disabled
• unframed
• framed (G.704)
• framed (G.704) ISDN PRA (ETS 300 233)
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
Service Used
SNMP-SET on e1pPITTPSignalMode
Note F-3.2: Only unframed and framed (G.704) modes are supported.
F-3.3 Request E1 Frame
Status
N
This management function allows a managing system to request
whether a CRC indication (multiframe presence) is detected on a
E1 signal when the processing of a framed signal is activated.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
opticsIME1PathTTPTable
Service Used
SNMP-GET on (respectively):
e1pPITTPFrameStatus
e1PathTTPFrameStatus
F-3.4 Request RAI Insertion
Status
Y
This management function allows a managing system to request
the status of the RAI insertion in a E1 or DS3 framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMPdhRAIInsertionTable
Service Used
SNMP-GET on:
• pdhRAIInsertionSignalType




07 RELEASED It 1


8BW 03598 0000 DSZZA 48/ 181


• pdhRAIInsertionStatus
Note F-3.4: Supported only on E1 signals (pPI and Path).
F-3.5 Condition RAI Insertion
Status
Y
This management function allows a managing system to condition
the RAI insertion inhibition in a E1 or DS3 framed signal, both
physical interface and path side. The status allowed are the
following:
• enabled
• 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
Processing Mode
Y
This management function allows a managing system to request
which processing mode is activated on a E3 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME3pPITTPTable
Service Used
SNMP-GET on e3pPITTPSignalMode
F-3.9 Condition E3 Signal
Processing Mode
Y
This management function allows a managing system to condition
the E3 signal processing mode. The allowed signal processing
modes are:
• disabled
• unframed
• framed (G.704) G.751
• framed (G.704) G.753
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME3pPITTPTable
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
Processing Mode
Y
This management function allows a managing system to request
which processing mode is activated on a DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs1pPITTPTable
Service Used
SNMP-GET on ds1pPITTPSignalMode
F-3.11 Condition DS1 Signal
Processing Mode
Y
This management function allows a managing system to condition
the processing mode of a DS1 signal. The allowed signal
processing modes are:
• disabled
• unframed
• framed (G.704) with 12 frames multiframe (Super Frame)
• framed (G.704) with 24 frames multiframe (Extended Super
Frame)
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs1pPITTPTable
Service Used
SNMP-SET on ds1pPITTPSignalMode
F-3.12 Request DS3 Signal
Processing Mode
Y
This management function allows a managing system to request
which processing mode is activated on a DS3 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable




07 RELEASED It 1


8BW 03598 0000 DSZZA 49/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 50/ 181


Service Used
SNMP-GET on
• allowedLineLengthId
• allowedLineLengthMin
• allowedLineLengthMax
F- 3.33 Request E1/DS1 AIS
Signal Type
N This management function allows a managing system to request
which AIS Signal type (allOnes or AllZeroes) is activated on an
E1 signal or on DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-GET on e1pPITTPAISSignalType
(opticsIME1pPITTPTable) or ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
F- 3.34 Condition E1/DS1 AIS
Signal Type
N This management function allows a managing system to condition
which AIS Signal type (allOnes or AllZeroes) is activated on an
E1 signal or on an DS1 signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-SET on: e1pPITTPAISSignalType
(opticsIME1pPITTPTable) or ds1pPITTPAISSignalType
(opticsIMDS1pPITTPTable).
F- 3.35 Condition Global
E1/DS1 AIS Signal Type
N This management function allows a managing system to
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
AIS Insertion
N This management function allows a managing system to request
if insertion of AIS Signal is activated on 2 Mbit/s or on 1,5 Mbit/s
PDH trails.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable
Service Used
SNMP-GET on e1pPITTPAISInsertion (opticsIME1pPITTPTable)
or ds1pPITTPAISInsertion (opticsIMDS1pPITTPTable)
F- 3.37 Condition E1/DS1 pPI
AIS Insertion
N This management function allows a managing system to
enable/disable the AIS Signal insertion for 2 Mbit/sor for 1,5
Mbit/s PDH trails.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable,
opticsIMDS1pPITTPTable.
Service Used
SNMP-SET on e1pPITTPAISInsertion (opticsIME1pPITTPTable)
or ds1pPITTPAISInsertion (opticsIMDS1pPITTPTable).
F- 3.38 Condition Global
E1/DS1 pPI AIS Insertion
N This management function allows a managing system to
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
OPTICSIM-TRS-COMMON-MIB
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 51/ 181


SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion
F- 3.39 Request E1/DS1 Path
AIS Insertion
N This management function allows a managing system to request
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
Path AIS Insertion
N This management function allows a managing system to
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).
F- 3.41 Condition Global
E1/DS1 Path AIS Insertion
N This management function allows a managing system to
condition, in one shot, the AIS Signal insertion for all the 2 Mbit/s
or 1,5 Mbit/s paths.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object opticsIMAllE1pPIAISInsertion or
opticsIMAllDS1pPIAISInsertion.
F- 3.42 Request DS3 AIS
Signal Type
N This management function allows a managing system to request
which AIS Signal type (allOnes or blueSignal) is activated on an
DS3 signal. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-GET on ds3pPITTPAISSignalType
F- 3.43 Condition DS3 AIS
Signal Type
N This management function allows a managing system to condition
which AIS Signal type (allOnes or blueSignal) is activated on an
DS3 signal. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPAISSignalType
F- 3.44 Condition Global DS3
AIS Signal Type
N This management function allows a managing system to
condition, in one shot, the AIS Signal Type (allOnes or
blueSignal) of all the DS3 lines. It is applicable only on framed
signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object opticsIMAllDS3AISSignalType
F- 3.45 Request DS3 pPI AIS
Insertion
N This management function allows a managing system to request
if insertion of AIS Signal is activated on 45 Mbit/s PDH trails. It is
applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 52/ 181


SNMP-GET on ds3pPITTPAISInsertion
F- 3.46 Condition DS3 pPI
AIS Insertion
N This management function allows a managing system to
enable/disable the AIS Signal insertion for 45 Mbit/s PDH trails. It
is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPAISInsertion.
F- 3.47 Condition Global DS3
pPI AIS Insertion
N This management function allows a managing system to
condition, in one shot, the AIS Signal insertion for all the 45 Mbit/s
PDH trails. It is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object opticsIMAllDs3pPIAISInsertion
F- 3.48 Request DS3 Path AIS
Insertion
N This management function allows a managing system to request
if insertion of AIS Signal is activated on 45 Mbit/s path. It is
applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-GET on ds3PathTTPAISInsertion.
F- 3.49 Condition DS3 Path
AIS Insertion
N This management function allows a managing system to
enable/disable the AIS Signal insertion for 45 Mbit/s path. It is
applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-SET on ds3PathTTPAISInsertion.
F- 3.50 Condition Global DS3
Path AIS Insertion
N This management function allows a managing system to
condition, in one shot, the AIS Signal insertion for all the 45 Mbit/s
paths. It is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object opticsIMAllDs3PathAISInsertion
F- 3.51 Request DS3 AIS
Signal Timing
N This management function allows a managing system to request
the time to wait before to insert an AIS signal (after failure
detection) and the time to wait to remove an AIS signal (after the
failure clear) on an DS3 line. It is applicable only on framed
signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
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
Signal Timing
N This management function allows a managing system to condition
the time to wait before to insert an AIS signal (after failure
detection) and the time to wait to remove an AIS signal (after the
failure clear) on a DS3 line. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPAISSignalTiming
F- 3.53 Condition Global DS3
AIS Signal Timing
N This management function allows a managing system to
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




07 RELEASED It 1


8BW 03598 0000 DSZZA 53/ 181


AIS signal (after the failure clear) for all the DS3 lines. It is
applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object opticsIMAllDS3AISSignalTiming
F- 3.54 Request DS3 pPI
Parity Violation Monitoring
Removing
N This management function allows a managing system to request
if Parity Violation Monitoring Removing is enabled or disabled on
45 Mbit/s trail. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-GET on ds3pPITTPParityViolationMonitoringRemoving.
F- 3.55 Condition DS3 pPI
Parity Violation Monitoring
Removing
N This management function allows a managing system to
enable/disable the Parity Violation Monitoring Removing for 45
Mbit/s trail. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPParityViolationMonitoringRemoving.
F- 3.56 Condition Global DS3
pPI Parity Violation
Monitoring Removing
N This management function allows a managing system to
condition, in one shot, the Parity Violation Monitoring Removing
for all the 45 Mbit/s trails. It is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object
opticsIMAllDs3pPIParityViolationMonitoringRemoving
F- 3.57 Request DS3 Path
Parity Violation Monitoring
Removing
N This management function allows a managing system to request
if Parity Violation Monitoring Removing is enabled or disabled on
45 Mbit/s path. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-GET on ds3PathTTPParityViolationMonitoringRemoving.
F- 3.58 Condition DS3 Path
Parity Violation Monitoring
Removing
N This management function allows a managing system to
enable/disable the Parity Violation Monitoring Removing for 45
Mbit/s path. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3PathTTPTable
Service Used
SNMP-SET on ds3PathTTPParityViolationMonitoringRemoving.
F- 3.59 Condition Global DS3
Path Parity Violation
Monitoring Removing
N This management function allows a managing system to
condition, in one shot, the Parity Violation Monitoring Removing
for all the 45 Mbit/s paths. It is applicable only on framed signals.
Scope
OPTICSIM-TRS-COMMON-MIB
Service Used
SNMP-SET on the scalar object
opticsIMAllDs3PathParityViolationMonitoringRemoving
F- 3.60 Request DS3 Idle
insertion and detection
N This management function allows a managing system to request
if idle insertion is activated on one direction and the status
(detection) of idle insertion on the other direction for an DS3
signal. It is applicable only on framed signal.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMAllDs3pPITTPTable
Service Used
SNMP-GET on




07 RELEASED It 1


8BW 03598 0000 DSZZA 54/ 181


• ds3pPITTPIdleInsertion
• ds3pPITTPIdleDetection
F- 3.61 Condition DS3 Idle
insertion
N This management function allows a managing system to condition
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
Bridge Status
N This management function allows a managing system to request
if this selected DS3 line is used to bridge and other DS3 line.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-GET on
ds3pPITTPInputBridgeEnabled
F- 3.63 Condition DS3 Line
Bridge
N This management function allows a managing system to
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
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPInputBridgeEnabled
F- 3.64 Request E1/E3
pseudo-random pattern
insertion
N This management function allows a managing system to request
if insertion of pseudo-random pattern is activated on tributary x
(E1 or E3 signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
opticsIME3pPITTPTable
Service Used
SNMP-GET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable) or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
F- 3.65 Condition E1/E3
pseudo-random pattern
insertion
N This management function allows a managing system to condition
the insertion of pseudo-random pattern on tributary x (E1 or E3
signal).
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable ,
opticsIME3pPITTPTable
Service Used
SNMP-SET on:
e1pPITTPPseudoRandSeqInsertion (opticsIME1pPITTPTable) or
e3pPITTPPseudoRandSeqInsertion (opticsIME3pPITTPTable).
F-3.66 Request DS3 Line
Length

N This management function allows a managing system to request
the length of a DS3 line. It provides information for Line Build Out
circuitry.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-GET on ds3pPITTPLineLength
F-3.67 Condition DS3 Line
Length
N This management function allows a managing system to condition
the length of a DS3 line.




07 RELEASED It 1


8BW 03598 0000 DSZZA 55/ 181


Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMDs3pPITTPTable
Service Used
SNMP-SET on ds3pPITTPLineLength
F-3.68 Request DS3 Line
Length Allowed Ranges

N This management function allows a managing system to request
the ranges of Ds3 line lengths allowed on NE.
Scope
OPTICSIM-TRS-COMMON-MIB:
opticsIMAllowedDs3LineLengthsTable
Service Used
SNMP-GET on
• AllowedDs3LineLengthId
• AllowedDs3LineLengthMin


Function Notifications SN
MP
If
Function Description
F-3.20 Report PDH Physical
Interface Alarms
Y
This management function allows a managed system to report
transmission alarms related to PDH physical interfaces.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
opticsIME3pPITTPTable
opticsIMDs1pPITTPTable
opticsIMDs3pPITTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmLossOfSignalRaise
• opticsIMAlarmLossOfSignalClear
• opticsIMAlarmLossOfFrameRaise
• opticsIMAlarmLossOfFrameClear
• 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
Alarms
Y
This management function allows a managed system to report
transmission alarms related to PDH paths.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1PathTTPTable
opticsIME3PathTTPTable
opticsIMDs1PathTTPTable
opticsIMDs3PathTTPTable
Service Used
SNMP-TRAP:
• opticsIMAlarmLossOfFrameRaise
• opticsIMAlarmLossOfFrameClear
• opticsIMAlarmAisRaise
• opticsIMAlarmAisClear
• opticsIMAlarmRemoteDefectIndicationRaise (E1 and DS3
only)




07 RELEASED It 1


8BW 03598 0000 DSZZA 56/ 181


• opticsIMAlarmRemoteDefectIndicationClear (E1 and DS3
only)
F-3.22 Report PDH Loss
Alarm Due to Switch
N
This management function allows a managed system to report
the loss of the PDH signals due to switch for protection of Fast
Ethernet signals.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIME1pPITTPTable
opticsIMDs1pPITTPTable
Service Used
SNMP-TRAP:
• opticsIMPdhLossDueToSwitchRaise
• opticsIMPdhLossDueToSwitchClear

BER Measure Functions

Function SN
MP
If
Function Description
F-3.30 Create BER Measure
Entry
N
This management function allows the managing system to create
a BER measure entry. The management system has to indicate in
the creation request: the monitoring point 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
F-3.31 Delete BER Measure
Entry
N
This management function allows the managing system to delete
a BER measure entry.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMBERMeasureTable
Service Used
SNMP-SET on berMeasureRowStatus columnar object to
"destroy" value
F-3.32 Request BER Measure
Data
N
This management function allows the managing system to
request the BER measure data related to the current observation
period.
Scope
OPTICSIM-TRS-COMMON-MIB: opticsIMBERMeasureTable
Service Used
SNMP-GET on the following columnar objects:
• berMeasureElapsedTime
• berMeasureSuspectIntervalFlag
• berMeasureViolations
• berMeasureValue









07 RELEASED It 1


8BW 03598 0000 DSZZA 57/ 181


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

For each table, according to the configuration the 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
(Table/Scalar)
Configuration Description
Indexes
Value
opticsIMTrsCommonMib
All the 1+0 E3 Tx port – Ch#1 10101 opticsIME3pPITTPTable
e3pPITTPSignalMode
e3pPITTPOperationalState
e3pPITTPAsapIndex
All the 1+1 E3 Tx port – Ch#Common 10199
All the 1+0 DS3 Tx port – Ch#1 10101 opticsIMDs3pPITTPTable (note 1)
ds3pPITTPSignalMode
ds3pPITTPOperationalState
ds3pPITTPAsapIndex
All the 1+1 DS3 Tx port – Ch#Common 10199
All the 1+0 E1 Tx ports – Ch#1

1xx01
(xx = 01..16)
opticsIME1pPITTPTable
e1pPITTPSignalMode
e1pPITTPOperationalState
e1pPITTPAsapIndex
All the 1+1 E1 Tx ports – Ch#Common

1xx99
(xx = 01..16)
All the 1+0 DS1 Tx ports – Ch#1

1xx01
(xx = 01..16)
opticsIMDs1pPITTPTable (note 1)
ds1pPITTPSignalMode
ds1pPITTPLineCoding
ds1pPITTPLineLength
ds1pPITTPOperationalState
ds1pPITTPAsapIndex
All the 1+1 DS1 Tx ports – Ch#Common

1xx99
(xx = 01..16)
All the 1+0 E3 Rx port – Ch#1 20101 opticsIME3PathTTPTable
e3PathTTPOperationalState
All the 1+1 E3 Rx port – Ch#Common 20199
All the 1+0 DS3 Rx port – Ch#1 20101 opticsIMDs3PathTTPTable (note 1)
ds3PathTTPOperationalState
All the 1+1 DS3 Rx port – Ch#Common 20199
All the 1+0

E1 Rx ports – Ch#1 2xx01
(xx = 01..16)
opticsIME1PathTTPTable
e1PathTTPOperationalState
All the 1+1 E1 Rx ports – Ch#Common 2xx99
(xx = 01..16)
All the 1+0

DS1 Rx ports – Ch#1 2xx01
(xx = 01..16)
opticsIMDs1PathTTPTable (note 1)
ds1PathTTPOperationalState
All the 1+1 DS1 Rx ports – Ch#Common 2xx99
(xx = 01..16)
E1 Rx ports – Ch#1

1xx01;
e1pPI
(xx = 01..16)
All the 1+0
E1 Tx ports – Ch#1

2xx01;
e1Path
(xx = 01..16)
opticsIMPdhRAIInsertionTable
pdhRAIInsertionSignalType
pdhRAIInsertionStatus
All the 1+1 E1 Rx ports – Ch#Common

1xx99;
e1pPI
(xx = 01..16)




07 RELEASED It 1


8BW 03598 0000 DSZZA 58/ 181


Table Entry
Supported Objects
(Table/Scalar)
Configuration Description
Indexes
Value
E1 Tx ports – Ch#Common 2xx99;
e1Path
(xx = 01..16)
opticsIMAllowedDs1LineLenghtsTa
ble (note 1)
allowedDs1LineLenghtMin
allowedDs1LineLenghtMax
allowedDs1LineLenghtId
All 0-133 ft
133-266 ft
266-399 ft
399-533 ft
533-655 ft
0
1
2
3
4

opticsIMTrsPdhMib
All the 1+0 Radio port – Ch#1 20101 opticsIMFrameTTPTable
frameTTPOperationalState
All the 1+1 Radio port – Ch#Common 20199
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMCoderTTPTable
coderTTPOperationalState
All the 1+1
Radio port – Ch#0 20100
opticsIMFrameStructureConfigur
ation



(note 1) Not supported on ULS 2.0.0.





07 RELEASED It 1


8BW 03598 0000 DSZZA 59/ 181


6 ETHERNET TRANSMISSION DOMAIN
6.1 Functional Description
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.




07 RELEASED It 1


8BW 03598 0000 DSZZA 60/ 181


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















Rx Functional View













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
Ch#1
Radio
(source)
MUX
(source)
GFP
(source)
ETH-EFC
(sink)
Aggregate
(source)
Aggregate
(source)
Radio
(source) Ch#0
Main
Main/DATA ODU
ODU Ext.
Ch#1
Radio
(sink)
GFP
(sink)
MAU
(source)
ETH-EFC
(source)
Aggregate
(sink)
Aggregate
(sink)
Radio
(sink)
Ch#0
Main
Main/DATA ODU
ODU Ext.
DEMUX
(sink)
RPS hitless
MAU
(sink)
ETH
(source)
ETH
(sink)




07 RELEASED It 1


8BW 03598 0000 DSZZA 61/ 181


• 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
Configuration
Number of FE

Number of PDH
Tributaries
twoE1 <= 1 E1
fourE1 <= 3 E1
eightE1 <= 7 E1
sixteenE1
<= 2
<= 8 E1
oneE3 Not allowed
fourDS1 (note 1) <= 3 DS1
eightDS1 (note 1) <= 7 DS1
sixteenDS1 (note 1) <= 8 DS1
oneDS3 (note 1)
(note 2)
<= 2
Not allowed
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 1) Not supported on ULS 2.0.0.
(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.








07 RELEASED It 1


8BW 03598 0000 DSZZA 62/ 181


6.2 Management Functions

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

Function
Activation/Deactivation
SN
MP
If
Function Description
F-1.1 Request FE MAU Status Y
This function is used to retrieve MAU object status with 2 admitted
values depending of Activate state of the MAU:
• Operational(3): the MAU is electrically switched on.
• Shutdown(5): the MAU is electrically switched off.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauStatus
F-1.6 Condition FE MAU
Status
Y
This function is used to explicitly activate (ifMauStatus =
“Operational”) or deactivate (ifMauStatus = “Shutdown") the MAU.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-SET on ifMauStatus
F-1.7 Request FE MAU
Operational State
Y
This function is used to retrieve the MAU Operational State.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauMediaAvailable
Note F-1.7: Allowed values:
• available (3)
• notAvailable (4)

Function Configuration SN
MP
If
Function Description
F-1.2 Request FE MAU Jack
Type
N
This function is used to request FE MAU jack type. FE MAU always
rely on rj45 (2) jack types.
Scope
MAU-MIB: ifJackTable
Service Used
SNMP-GET on ifJackType
F-1.3 Condition FE MAU
Default Type
Y
This function is used to operate on FE MAU default type:
• dot3MauType10BaseTFD: 10BaseT full-duplex
• dot3MauType100BaseTxFD: 100BaseTx full-duplex
This operation can be performed only when the
ifAdminStatus/ifMauStatus of supporting Ethernet interface is down.
By default the 100BaseTx full-duplex operation




07 RELEASED It 1


8BW 03598 0000 DSZZA 63/ 181


(“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.
F-1.4 Request FE MAU
Capability Data
Y
This function is used to request FE MAU capability data with below
retrieved information:
• Whether auto-negotiation is supported;
• The available MAU types (10BaseT/100BaseTX);
• The actual default MAU type.
The available MAU types (see ifMauTypeListBits [2]) is defined as:
• b10baseTFD (11) = 1
• b100baseTXFD (16) = 1
• Other bits = 0
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on:
• IfMauAutoNegSupported
• IfMauTypeListBits
• IfMauDefaultType
F-1.8 Change FE MAU ASAP
Pointer
Y
This function is used to configure the ASAP Pointer associated to
an Ethernet Interface.
Scope
OPTICSIM-ETHNE-MIB: opticsIMIfMauExtTable
Service Used
SNMP-SET on opticsIMifMauExtAsapIndex
F-1.9 Request FE MAU ASAP
Pointer
Y
This function is used to request the ASAP Pointer associated to an
Ethernet Interface.
Scope
OPTICSIM-ETHNE-MIB: opticsIMIfMauExtTable
Service Used
SNMP-GET on opticsIMifMauExtAsapIndex

Function Notification SN
MP
If
Function Description
F-1.5 Report FE MAU Alarm Y
This function is used to report a cLOS alarm.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-TRAP on:
• opticsIMAlarmLossOfSignalRaise
• opticsIMAlarmLossOfSignalClear

Electrical Fast Ethernet - Ety_T Management

Function Configuration SN Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 64/ 181


MP
If
F-2.1 Enable/Disable FE
Auto-Negotiation
Y
This function is used to enable (ifMauAutoNegAdminStatus =
enabled) or disable (ifMauAutoNegAdminStatus = disabled) the
auto-negotiation.
Scope
MAU-MIB: ifMauAutoNegTable
Service Used
SNMP-SET on ifMauAutoNegAdminStatus
F-2.2 Request FE MAU Auto-
Negotiation Status
Y
This function is used to request the MAU auto-negotiation status.
The retrieved information’s are:
• Whether or not the auto-negotiation is enabled
(ifMauAutoNegAdminStatus)
• The current status of the auto-negotiation process
(ifMauAutoNegConfig)
• The auto-negotiation capabilities supported by the local
(ifMauAutoNegCapabilityBits)
• The auto-negotiation capabilities advertised by the local
(ifMauAutoNegCapAdvertisedBits)
• The auto-negotiation capabilities advertised by the remote
(ifMauAutoNegCapReceivedBits)
The available IfMauAutoNegCapabilityBits is defined 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
MAU-MIB: ifMauAutoNegTable
Service Used
SNMP-GET on:
• ifMauAutoNegAdminStatus
• ifMauAutoNegConfig
• ifMauAutoNegCapabilityBits
• ifMauAutoNegCapAdvertisedBits
• ifMauAutoNegCapReceivedBits
F-2.3 Restart FE Auto-
Negotiation
Y
After the restart, the agent will reset the ifMauAutoNegRestart to its
default value: noRestart(2).
Scope
MAU-MIB: ifMauAutoNegTable
Service Used
SNMP-SET on ifMauAutoNegRestart to restart(1)
F-2.4 Condition FE MAU
Auto-Negotiation Advertised
Capability
Y
This function is used to operate on the FE MAU capabilities
advertised during the auto-negotiation.
The FE mode operations:
• Speed Negotiation: 10BASE-T full duplex mode, b10baseTFD(2).
• Speed Negotiation: 100BASE-TX full duplex mode,
b100baseTXFD(5).
• Pause operation: PAUSE for full-duplex links, bFdxPause(8).
• Pause operation: Asymmetric PAUSE for full-duplex links,
bFdxAPause(9).
• Pause operation: Symmetric PAUSE for full-duplex links,
bFdxSPause(10).




07 RELEASED It 1


8BW 03598 0000 DSZZA 65/ 181


• 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
MAU-MIB: ifMauAutoNegTable
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.
F-2.5 Request FE MAU
Jabber State
N
This function is used to retrieve the FE Jabber State.
Scope
MAU-MIB: ifMauTable
Service Used
SNMP-GET on ifMauJabberState

Optical Fast Ethernet - MAU Management
Not supported.

Optical Fast Ethernet - Ety_T Management
Not supported.





07 RELEASED It 1


8BW 03598 0000 DSZZA 66/ 181


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

Function Creation/Deletion SN
MP
If
Function Description
F-1.x All the functions N

Function
Activation/Deactivation
SN
MP
If
Function Description
F-1.x All the functions N

Function Configuration SN
MP
If
Function Description
F-1.6 Condition Ety/Eth_A
Promiscuous Mode
N
This function is used to configure Promiscuous mode when the
Ethernet interface is deactivated.
Scope
IF-MIB: ifXTable
Service Used
SNMP-SET on ifPromiscuousModeto below values:
• true(1) when the station accepts all packets/frames transmitted on
the media.
• false(2) if this interface only accepts packets/frames that are
addressed to this station.
F-1.7 Request Ety/Eth_A Data P
This function is used to read:
• the interface MTU;
• the interface speed;
• the interface mode (promiscuous/not promiscuous);




07 RELEASED It 1


8BW 03598 0000 DSZZA 67/ 181


• the Ethernet local MAC address. In case the local MAC address
is not available the address will have the value 00:00:00:00:00:00;
• the handling (over local Ethernet port) of incoming errored
Ethernet frames;
• Client Layer of an ISA NE local Ethernet Port
Scope
IF-MIB: ifTable, ifXTable, opticsIMEthConfTable
Service Used
SNMP-GET on:
• ifType
• ifMtu
• ifPromiscuousMode
• ifPhysAddress
• ifConnectorPresent (set to true)
• opticsIMEthFCSDiscardErroredFrames
• opticsIMEthClientType
Note F-1.7: Only object opticsIMEthFCSDiscardErroredFrames is supported.
F-1.8 Condition Ety/Eth_A
FCS Discard Errored Frames
Y
This function allows to condition the handling of incoming errored
Ethernet frames over local Ethernet port complying with 2 possible
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
F-1.9 Condition Ety/Eth_A
Ethernet Port Client Type
N
This function allows to condition the Client Layer of an ISA NE local
Ethernet Port in case of promiscuous mode complying with below
possible modes:
• ETS Layer mode; [Default Mode is ISA NE Product Specific] OR
• Ethernet Switching Layer.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-SET on opticsIMEthClientType

Local Ethernet Port Transmission Specification – EFC Management

Function Configuration SN
MP
If
Function Description
F-6.x All the functions N

Remote Ethernet Port Transmission Specification – GFP/Eth_A Management

Function Creation/Deletion SN Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 68/ 181


MP
If
F-3.x All the functions N


Function
Activation/Deactivation
SN
MP
If
Function Description
F-3.x All the functions N

Function Configuration SN
MP
If
Function Description
F-3.5 Request Gfp/Eth_A
Ethernet Interface Status
N
This function is used to read:
• the status of an Ethernet Interface (enabled/disabled)
• The operational state of an Ethernet interface (up/down)
• The time at which the interface entered its current operational
state.
Scope
IF-MIB: ifTable
Service Used
SNMP-GET on:
• ifAdminStatus
• ifOperStatus
• ifLastChange
F-3.6 Condition Gfp/Eth_A
Promiscuous Mode
N
This function is used to configure Promiscuous mode when the
Ethernet interface is deactivated.
Scope
IF-MIB: ifXTable
Service Used
SNMP-SET on ifPromiscuousMode
F-3.7 Request Gfp/Eth_A
Ethernet Configuration Data
P
This function is used to read:
• interface MTU;
• 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
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-GET on:
• ifType




07 RELEASED It 1


8BW 03598 0000 DSZZA 69/ 181


• ifMtu
• ifPromiscuousMode
• ifPhysAddress
• ifConnectorPresent (fixed to FALSE)
• opticsIMEthFCSDiscardErroredFrames
• opticsIMEthClientType
Note F-3.7: Only object opticsIMEthFCSDiscardErroredFrames is supported.
F-3.8 Condition Gfp/Eth_A
FCS Discard Errored Frames
Y
This function allows to condition the handling of incoming errored
Ethernet frames over a “GFP-based” remote Ethernet Port
complying with 2 possible modes:
• “Monitoring and discarding handling mode” of incoming errored
Ethernet frames [Default Handling Mode is ISA NE Product
Specific];
• “Monitoring handling mode” of incoming Ethernet errored frames.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-SET on opticsIMEthFCSDiscardErroredFrames
F-3.9 Condition Gfp/Eth_A
Ethernet Port Client Type
N
This function allows to condition the Client Layer of an ISA NE
“GFP-based” remote Ethernet Port (in promiscuous mode)
complying with below possible modes:
• ETS Layer mode; [Default Mode] OR
• Ethernet Switching Layer.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
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

Function Configuration SN
MP
If
Function Description
F-2.1 Condition Ethernet
LLC/MAC Framing
N
This function is used to condition the Ethernet framing used in
transmission. The possible framing types
are:
• Ethernet V2;
• LLC/SNAP;
• 802.2/802.3.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 70/ 181


OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-SET on opticsIMEthConfEncaps
F-2.2 Request Ethernet
LLC/MAC Framing
N
This function is used to read the Ethernet framing used in
transmission. The possible framing types are:
• Ethernet V2;
• LLC/SNAP;
• 802.2/802.3.
Scope
OPTICSIM-ETHNE-MIB: opticsIMEthConfTable
Service Used
SNMP-GET on opticsIMEthConfEncaps

6.2.3 GFP Provider Layer Management

Function Creation/Deletion SN
MP
If
Function Description
F-1.x All the functions N
Scope
IF-MIB: ifTable
TSDIM-TRS-MIB: opticsIMIfTable

Function
Activation/Deactivation
SN
MP
If
Function Description
F-1.x All the functions N
Scope
IF-MIB: ifTable

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

Function Notification SN
MP
If
Function Description
F-1.9 Report TSF alarm N
Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMAlarmTsfRaise/Clear
F-1.10 Report LOF alarm Y
Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 71/ 181


SNMP-TRAP:
• opticsIMAlarmLossOfFrameRaise/Clear
F-1.11 Report GTM alarm N
Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMGfpAlarmGtmRaise/Clear
F-1.13 Report PLM alarm N
Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMAlarmPlmRaise/Clear
F-1.23 Report DEGRADE
alarm
N
Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMSdhConcDegradeRaise/Clear

6.2.4 GFP_T Management

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

Function Notification SN
MP
If
Function Description
F- 2.3 Report GFP CSF
alarm
N Scope
OPTICSIM-GFP-MIB: opticsIMGFPConfTable
Service Used
SNMP-TRAP:
• opticsIMClientSignalFailRaise/Clear





07 RELEASED It 1


8BW 03598 0000 DSZZA 72/ 181



6.3 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 Ethernet objects are defined in [13].

Table Entry
Supported Objects
(Table/Scalar)
Configuration Description
Indexes
Value
mauMod (from MAU-MIB)
ifMauTable
ifMauStatus
ifMauMediaAvailable

ifMauDefaultType
ifMauAutoNegSupported
ifMauTypeListBits
All the 1+0 ETH
All the 1+1 ETH
DATA Tx ports – Ch#1

1xx01; 1
(xx = 17..18)
ifMauAutoNegTable
ifMauAutoNegAdminStatus
ifMauAutoNegConfig
ifMauAutoNegCapabilityBits
ifMauAutoNegCapAdvertisedBits
ifMauAutoNegCapReceivedBits
ifMauAutoNegRestart
All the 1+0 ETH
All the 1+1 ETH
DATA Tx ports – Ch#1

1xx01; 1
(xx = 17..18)
opticsimEthNEMib
opticsIMMauExtTable
opticsIMMauExtAsapIndex

All the 1+0 ETH
All the 1+1 ETH
DATA Tx ports – Ch#1

1xx01; 1
(xx = 17..18)
All the 1+0 ETH
All the 1+1 ETH
DATA Tx ports- Ch#1

1xx01
(xx = 17..18)
opticsIMEthConfTable
opticsIMEthFCSDiscardErroredFr
ames All the 1+0 ETH
All the 1+1 ETH
DATA Rx ports- Ch#1

2xx01
(xx = 17..18)
opticsimGFPMib
opticsimGFPConfTable
(only alarms are managed)
All the 1+0 ETH
All the 1+1 ETH
Radio port – Ch#1 29901







07 RELEASED It 1


8BW 03598 0000 DSZZA 73/ 181


7 RADIO DOMAIN
7.1 Functional Description
Radio Protections
One RPS hitless protection scheme is supported in case of 1+1 configurations.

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

Parameter Type Value
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
Forced switch from main to spare
Manual switch from main to spare and vice-versa

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

Parameter Type Value
Protection Group Type 1+1
Switching Type Single Ended
Restoration Criteria Revertive / Non Revertive
Switching Condition
Equipment failures Tx side
Operator Commands Lockout spare
Forced switch from main to spare
Manual switch from main to spare and vice-versa
The configuration of both these protection schemes is performed by the NE in conjunction with the
equipment provisioning process (declaration of boards).




07 RELEASED It 1


8BW 03598 0000 DSZZA 74/ 181




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




07 RELEASED It 1


8BW 03598 0000 DSZZA 75/ 181


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.

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.


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 76/ 181


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

7.2 Management Functions

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

Radio Frequency

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 77/ 181


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

Tx Power and ATPC

Function Configuration SN
MP
If
Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 78/ 181


F-1.10 Request ATPC
Implemented Status
N
This management function allows the managing system to request
if the ATPC capability is present or not.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB
Service Used
SNMP-GET on opticsIMRadioAtpcImplemented
F-1.11 Request ATPC Activity Y
This management function allows the managing system to request
the status of the ATPC activity: enabled or disabled.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on radioAtpcEnabled
F-1.12 Condition ATPC
Activity
Y
This management function allows the managing system to
condition the status of the ATPC activity: enabled or disabled.
ATPC can be enabled only if it is implemented in the equipment.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-SET on radioAtpcEnabled
F-1.13 Request ATPC Tx
Range
Y
This management function allows the managing system to request
the minimum and maximum values allowed for the transmitted
power used by ATPC device.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on:
• radioMinAtpcTxPower
• radioMaxAtpcTxPower
F-1.14 Condition ATPC Tx
Range
Y
This management function allows the managing system to
condition the minimum and maximum values allowed for the
transmitted power used by ATPC device.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
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
Power Thresholds
P
This management function allows the managing system to request
the low and extra low power thresholds values used by the ATPC
device.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on:
• radioAtpcLowPowerThr
• radioAtpcExtraLowPowerThr
Note F-1.15: Only Atpc low power threshold is supported.
F-1.16 Condition ATPC Rx
Low Power Threshold
Y
This management function allows the managing system to set the
low power threshold value used by the ATPC device. This value
must be included in the related allowed range.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 79/ 181


OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-SET on radioAtpcLowPowerThr
F-1.17 Request ATPC Low
Power Threshold Range
Y
This management function allows the managing system to request
the minimum and maximum values allowed for the low power
threshold value used by ATPC device.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on:
• radioAtpcLowPowerMinThr
• radioAtpcLowPowerMaxThr
F-1.18 Request Tx Nominal
Power
Y
This management function allows the managing system to request
the tx nominal power.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on radioTxNominalPower
F-1.19 Request Current Tx
Power
Y
This management function allows the managing system to request
the value of the transmitted power when the ATPC is disabled and
no manual operation on transmitted power is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on radioCurrentTxPower
F-1.20 Condition Current Tx
Power
Y
This management function allows the managing system to set the
value of the transmitted power to be used by the local transmitter
when the ATPC is disabled and no manual operation on
transmitted power is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-SET on radioCurrentTxPower
F-1.21 Request Tx Power
Range
Y
This management function allows the managing system to request
the allowed range (minimum and maximum values) of the
transmitted power.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on:
• radioMinTxPower
• radioMaxTxPower
F-1.22 Request Manual
Operation Status on Tx
Power
N
This management function allows the managing system to request
the status (active/not active) of a manual management of the
transmitted power.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on radioManOpTxPower




07 RELEASED It 1


8BW 03598 0000 DSZZA 80/ 181


F-1.23 Initiate/Terminate a
Manual Operation on Tx
Power
N
This management function allows the managing system to initiate /
terminate a manual management of the transmitted power.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-SET on radioManOpTxPower
F-1.24 Request Manual
Operation Tx Power Level
N
This management function allows the managing system to request
the transmitted power level when a manual management of the
transmitted power is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on radioManOpTxPowerLevel
F-1.25 Condition Manual
Operation Tx Power Level
N
This management function allows the managing system to set the
transmitted power level when a manual management of the
transmitted power is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-SET on radioManOpTxPowerLevel
F-1.26 Request Atpc
Direction Identifier
N
This management function allows the managing system to request
the ATPC direction identifier used in the equipment configurations
in which all the radio channels transmit in the same direction.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB
Service Used
SNMP-GET on opticsIMRadioAtpcDirectionId
F-1.27 Condition Atpc
Direction Identifier
N
This management function allows the managing system to
condition the ATPC direction identifier used in the equipment
configurations in which all the radio channels transmit in the same
direction. The identifier provided is used both as expected value
(sink side) and as transmitted one (source side).
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB
Service Used
SNMP-SET on opticsIMRadioAtpcDirectionId
F-1.29 Request Allowed
ATPC Tx Range
Y
This management function allows the managing system to request
the minimum and maximum values allowed for the ATPC device
when allowed ATPC range and allowed RTPC range are different
(see F-1.21).
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxPowerTable
Service Used
SNMP-GET on:
• radioMinAllowedAtpcTxPower
• radioMaxAllowedAtpcTxPower
F-1.48 Request ATPC High
Power Status
N
This management function allows the managing system to request
the status of the ATPC in high-power mode.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-GET on:




07 RELEASED It 1


8BW 03598 0000 DSZZA 81/ 181


• radioATPCHighPowerMode
• radioATPCHighPowerTimeout
• radioATPCHighPowerTimeoutEnabled
F-1.49 Condition ATPC in
High Power Mode
N
This management function allows the managing system to lock the
ATPC in high-power mode.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-SET on radioATPCHighPowerMode
F-1.137 Condition ATPC
enabled with timeout
N
This management function allows the managing system to enable
or to disable the ATPC with timeout
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioATPCHighPowerTable
Service Used
SNMP-SET on radioATPCHighPowerTimeoutEnabled

Function Notifications SN
MP
If
Function Description
F-1.28 Report ATPC Identifier
Mismatch Alarm
N
This management function allows a managed system to report an
ATPC Identifier Mismatch alarm.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioAtpcDirectionId
Service Used
SNMP-TRAP:
- opticsIMAlarmAtpcIdentifierMismatchRaise
- opticsIMAlarmAtpcIdentifierMismatchClear

Intrusive Tx Power Control

Function SN
MP
If
Function Description
F-1.110 Request Radio
Channel Number
N
This management function allows a managing system to request
the number of the radio channel associated to the information
related to the management of the transmitted power during an
Intrusive BER measurement.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on intrusiveTPCRadioChannelNumber
F-1.111 Request Intrusive
Near End Tx Power Range
N
This management function allows the managing system to request
the minimum and maximum levels of the transmitted power allowed
during an Intrusive BER measurement activated on the Far End
NE.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:




07 RELEASED It 1


8BW 03598 0000 DSZZA 82/ 181


opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on:
• intrusiveTPCNearEndMinTxPower
• intrusiveTPCNearEndMaxTxPower
F-1.112 Request Intrusive Far
End Tx Power Range
N
This management function allows the managing system to request
the minimum and maximum levels of the transmitted power allowed
on the corresponding Far End radio channel during a BER
measurement activated on the Near End NE.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on:
• intrusiveTPCFarEndMinTxPower
• intrusiveTPCFarEndMaxTxPower
F-1.113 Request Manual
Operation Status on Far End
Tx Power
N
This management function allows the CT physically connected to
Near End NE to request the status of the control of the transmitted
power of the corresponding Far End radio channel (TRUE if the it is
controlled by the CT, FALSE otherwise).
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on intrusiveTPCFarEndControlled
F-1.114 Initiate/Terminate a
Manual Operation on Far End
Tx Power
N
This management function allows the CT physically connected to
Near End NE to assume the complete control of the transmitted
power of the corresponding Far End radio channel.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-SET on intrusiveTPCFarEndControlled
F-1.115 Request Manual
Operation Tx Power Level
N
This management function allows the managing system to request
the transmitted power level used by the corresponding Far End
radio channel when an intrusive BER measurement is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-GET on intrusiveTPCFarEndManOpTxPowerLevel
F-1.116 Condition Manual
Operation Tx Power Level
N
This management function allows the managing system to set the
transmitted power level used by the corresponding Far End radio
channel when an intrusive BER measurement is active.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMIntrusiveTPCTable
Service Used
SNMP-SET on intrusiveTPCFarEndManOpTxPowerLevel

Rx Gain

Function Configuration SN Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 83/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 84/ 181


configuration.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioRxGainTable
Service Used
SNMP-SET on radioManOpRxDivGainLevel



Analogue Measurements

Function Analogue
Measurements
SN
MP
If
Function Description
F-1.40 Request Radio
Channel Number
Y
This management function allows a managing system to request
the number of the radio channel associated to a analog measure.
Scope
OPTICSIM-RADIO-TRS-SDH-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on analogueMeasuresRadioChannelNumber
F-1.41 Request Local
Analogue Measurements
Y
This management function allows the managing system to request
the measurements of the local transmitted and received power
levels.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on:
- analogueMeasuresLocalTxPower
- analogueMeasuresLocalRxMainPower
F-1.42 Request Remote
Analogue Measurements
Y
This management function allows the managing system to request
the measurements of the remote transmitted and received power
levels.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on:
- analogueMeasuresRemoteTxPower
- analogueMeasuresRemoteRxMainPower
F-1.43 Request Local
Diversity Analogue
Measurement
N
This management function allows the managing system to request
the measures of the local received power levels related to the
diversity receiver.
This function is applicable only in case of Space Diversity
configuration.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on analogueMeasuresLocalRxDivPower




07 RELEASED It 1


8BW 03598 0000 DSZZA 85/ 181


F-1.44 Request Remote
Diversity Analogue
Measurement
N
This management function allows the managing system to request
the measures of the remote received power levels related to the
diversity receiver.
This function is applicable only in case of Space Diversity
configuration.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioAnalogueMeasuresTable
Service Used
SNMP-GET on analogueMeasuresRemoteRxDivPower

Radio Protection Switching

Function Configuration SN
MP
If
Function Description
F-1.50 Request RPS
Protection Group
Configuration
Y
This management function allows a managing system to request
the type of protection (1+1 or 1:N) and if the hitless capability is
present or not.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on:
• opticsIMRadioProtectionGroupType
• opticsIMRadioProtectionGroupHitless
F-1.51 Request RPS
Automatic Restoration
Criteria
Y
This management function allows a managing system to request
the current automatic restoration criteria: restoration allowed
(revertive mode) or inhibited (non-revertive mode).
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on opticsIMRadioProtectionGroupRevertive
F-1.52 Condition RPS
Automatic Restoration
Criteria
Y
This management function allows managing system to control the
automatic restoration criteria from the spare channel to the main
one when the failure clears.
This function is applicable only in case of 1+1 protection group
type.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-SET on opticsIMRadioProtectionGroupRevertive
F-1.53 Request RPS
Privileged Channel
N
This management function allows a managing system to request
the privileged channel. This function is applicable only in case of
1:N protection group type.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on opticsIMRadioProtectionGroupPrivilegedChannel




07 RELEASED It 1


8BW 03598 0000 DSZZA 86/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 87/ 181


F- 1.147 Request EW alarm
Rx Power Level Range
N This management function allows a managing system to request
the minimum and maximum values allowed for absolute Received
Power Level used to raise an EW alarm.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRxPowerLevelThresholdMngt
Service Used
SNMP-GET on following scalar object.
• opticsIMRxPowerLevelMinThr
• opticsIMRxPowerLevelMaxThr
F- 1.150 Request RPS Switch
on EW alarm Status
N This management function allows a managing system to request if
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
Switch on EW alarm
N This management function allows a managing system to condition
if RPS has to occur when EW alarm raised for Rx Power Level or
BER threshold crossing (‘enabledBEROnly’ or
‘enabledRxPowerOnly’ value), for both (‘enabledBoth’ value) or if
RPS Switch has not to occur for EW alarm (‘disabled’ value).
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-SET on opticsIMRadioSwitchEWEnabled
F- 1.152 Request RPS Switch
on lowBER alarm Status
N This management function allows a managing system to request if
RPS switch occurs when lowBER alarm raised. If RPS switch
doesn’t occur when lowBER alarm raised, the ‘disabled’ value is
returned.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-GET on opticsIMRadioSwitchLowBEREnabled scalar
object.
F- 1.153 Condition RPS
Switch on lowBER alarm
N This management function allows a managing system to condition
if RPS switch has to occur when lowBER alarm raised or not.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-SET on opticsIMRadioSwitchLowBEREnabled

Function Operator
Commands
SN
MP
If
Function Description
F-1.60 Allow/Inhibit Switch of
a RPS Working Channel
N
This management function allows the managing system to
inhibit/allow a working channel (main) to be switched to a protection
channel (spare). If the main channel was already switched when
the Inhibit Switch is requested, it is forced back to the working
position.
This function involves the lockout syntax to inhibit the switch, the
noRequest syntax to remove the lockout and allow the switch, both
addressed to a main protection unit.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 88/ 181


OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on main protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(lockout/noRequest)
F-1.61 Allow/Inhibit Switch of
RPS Protection Channel
Y
This management function allows the managing system to
inhibit/allow a protection channel (spare) to provide protection in
the protection scheme. If the protection channel was already
providing protection for a working one when the Inhibit Switch is
requested, then a forced switch is performed back to the working
position.
This function involves the lockout syntax to inhibit the switch, the
noRequest syntax to remove the lockout and allow any switch, both
addressed to the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on spare protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(lockout/noRequest)
F-1.62 Initiate/Terminate
Manual Switch to RPS
Protection Channel
Y
This management function allows the managing system to
initiate/terminate a manual switch from a working channel (main) to
the protection one (spare). This command will fail if another
working channel has already been switched to the protection
channel (only in case of 1:N) or if the protection channel is locked
or has an automatic switch request (SF, HBER, LBER, EW) active
present.
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
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on main protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(manualSwitch/noRequest)
F-1.63 Initiate/Terminate
Manual Switch to a RPS
Working Channel
Y
This management function allows the managing system to
initiate/terminate a manual switch from a protection channel (spare)
to a working one (main). This management function is applicable
only in case of 1+1 not revertive protection type. This command will
fail if the working channel has an automatic switch request (SF,
HBER, LBER, EW) active present.
This function involves the manualSwitch syntax to initiate the
switch, the noRequest syntax to terminate the manual switch, both
addressed to the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on spare protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(manualSwitch/noRequest)
F-1.64 Initiate/Terminate
Forced Switch to RPS
Protection Channel
Y
This management function allows the managing system to
initiate/terminate a forced switch from a working channel (main) to
a protection one (spare). If another working channel has already
been automatically or manually switched to the protection one
when the initiate command is received, it is switched back to its
working channel to allow the other working channel to be switched
to the protection one.




07 RELEASED It 1


8BW 03598 0000 DSZZA 89/ 181


This function will fail if another working channel is already forced
switched to the protection one.
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the forced switch, both
addressed to a main protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on main protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(forcedSwitch/noRequest)
F-1.65 Initiate/Terminate
Forced Switch to a RPS
Working Channel
N
This management function allows the managing system to
initiate/terminate a forced switch from a protection channel (spare)
to a working one (main). This management function is applicable
only in case of 1+1 not revertive protection type.
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the switch, both addressed to
the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
(on spare protection unit)
Service Used
SNMP-SET on opticsIMRadioProtectionUnitSwitchCommand
(forcedSwitch/noRequest)

Function Protection Status SN
MP
If
Function Description
F-1.66 Request RPS
Protection Scheme
Operational State
Y
This management function allows the managing system to request
the operational state of a radio protection scheme.
Scope
OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on opticsIMRadioProtectionGroupOperationalState
F-1.67 Request RPS
Protection Status
Y
This management function allows the managing system to request
the current state of a radio protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
Service Used
SNMP-GET on:
• opticsIMRadioProtectionUnitSwitchCommand
This management function allows the managing system to request
the current state of a radio protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioProtectionUnitTable
Service Used
SNMP-GET on:
• opticsIMRadioProtectionUnitSwitchCommand
• opticsIMRadioProtectionUnitSwitchCriteria
• opticsIMRadioProtectionUnitSwitchStatus
F-1.68 Request RPS
Protection Mismatch Status
N
This management function allows the managing system to request
a status will indicate if there is any mismatch between the local and
far-end protection type (1+1/1:N).
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 90/ 181


OPTICSIM-RADIO-SWTC-MIB:
opticsIMRadioProtectionGroupTable
Service Used
SNMP-GET on opticsIMRadioProtectionGroupMismatchStatus



Function Rx Static Delay
Configuration
SN
MP
If
Function Description
F-1.69 Invoke Automatic Rx
Static Delay Procedure
Y
This management function allows the managing system to trigger
the start of an automatic static delay alignment procedure on a
protection unit (the “aligning” syntax must be used). When the
procedure has been completed, the agent has to change the value
back to the “notAligning” syntax.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-SET on opticsIMRadioAutoRxStaticDelayAlignment
(aligning)
F-1.70 Request Automatic Rx
Static Delay Procedure
Status
N
This management function allows the managing system to status of
the automatic static delay alignment procedure on a protection unit:
aligning.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-GET on opticsIMRadioAutoRxStaticDelayAlignment
F-1.71 Request Delays
Inserted by Automatic Rx
Static Delay Procedure
N
This management function allows the managing system to request
the number of delays inserted by the automatic Rx static delay
alignment procedure on the direct and indirect ways.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-GET on:
• opticsIMRadioAutoRxStaticDelayDirectWay
• opticsIMRadioAutoRxStaticDelayIndirectWay
F-1.72 Initiate/Terminate
Manual Management of Rx
Static Delay
Y
This management function allows the managing system to initiate
or terminate a manual management of the Rx static delay.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-SET on opticsIMRadioManRxStaticDelay
F-1.73 Request Delays
Inserted by a Manual
Management of Rx Static
Delay
Y
This management function allows the managing system to request
the number of delays inserted by a manual management of the Rx
static delay on the direct and indirect ways.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-GET on:
• opticsIMRadioManRxStaticDelayDirectWay
• opticsIMRadioManRxStaticDelayIndirectWay
F-1.74 Condition Delays in Y
•This management function allows the managing system to
condition the number of delays inserted by a manual management




07 RELEASED It 1


8BW 03598 0000 DSZZA 91/ 181


Manual Management of Rx
Static Delay
of the Rx static delay on the direct and indirect ways.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
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
Notification
SN
MP
If
Function Description
F-1.75 Report Alignment
Alarm
Y
This management function allows a managed system to report a
loss of alignment alarm. It is addressed to the involved radio
channel (identified by a radio protection unit).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMRadioRxStaticDelayTable
Service Used
SNMP-TRAP:
- opticsIMAlarmLossOfAlignmentRaise
- opticsIMAlarmLossOfAlignmentClear

HST Transmission Protection Switching

Function Configuration SN
MP
If
Function Description
F-1.80 Request TPS
Automatic Restoration
Criteria
Y
This management function allows a managing system to request
the current automatic restoration criteria: restoration allowed
(revertive mode) or inhibited (non-revertive mode).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupRevertive
F-1.81 Condition TPS
Automatic Restoration
Criteria
Y
This management function allows managing system to control the
automatic restoration criteria from the spare transmission channel
to the main one when the failure clears.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-SET on opticsIMTxProtectionGroupRevertive
F-1.82 Request TPS
Protection Unit Type
Y
This management function allows a managing system to request
the type of a protection unit: main (protected) or spare (protecting).
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable
Service Used
SNMP-GET on opticsIMTxProtectionUnitType





07 RELEASED It 1


8BW 03598 0000 DSZZA 92/ 181


Function Operator
Commands
SN
MP
If
Function Description
F-1.83 Allow/Inhibit Switch of
TPS Protection Channel
Y
This management function allows the managing system to
inhibit/allow a protection channel (spare) to provide protection in
the protection scheme. If the protection channel was already
providing protection for the working one when the Inhibit Switch is
requested, then a forced switch is performed back to the working
position.
This function involves the lockout syntax to inhibit the switch, the
noRequest syntax to remove the lockout and allow any switch, both
addressed to the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
spare protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(lockout/noRequest)
F-1.84 Initiate/Terminate
Manual Switch to TPS
Protection Channel
Y
This management function allows the managing system to
initiate/terminate a manual switch from a working channel (main) to
the protection one (spare). This command will fail if the protection
channel is locked or has an automatic switch request active
present.
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
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
main protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(manualSwitch/noRequest)
F-1.85 Initiate/Terminate
Manual Switch to TPS
Working Channel
Y
This management function allows the managing system to
initiate/terminate a manual switch from a protection channel to a
working one. This management function is applicable only in case
of 1+1 not revertive protection type. This command will fail if the
working channel has an automatic switch request active present.
This function involves the manualSwitch syntax to initiate the
switch, the noRequest syntax to terminate the manual switch, both
addressed to the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
spare protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(manualSwitch/noRequest)
F-1.86 Initiate/Terminate
Forced Switch to TPS
Protection Channel
Y
This management function allows the managing system to
initiate/terminate a forced switch from a working channel to a
protection one. If another working channel has already been
automatically or manually switched to the protection one when the
initiate command is received, it is switched back to its working
channel to allow the other working channel to be switched to the
protection one.
According to the NE type, this function will fail if protection channel
has a failure condition.
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the forced switch, both




07 RELEASED It 1


8BW 03598 0000 DSZZA 93/ 181


addressed to a main protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
main protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(forcedSwitch/noRequest)
F-1.87 Initiate/Terminate
Forced Switch to TPS
Working Channel
N
This management function allows the managing system to
initiate/terminate a forced switch from a protection channel to a
working one. This management function is applicable only in case
of 1+1 not revertive protection type.
This function involves the forcedSwitch syntax to initiate the switch,
the noRequest syntax to terminate the switch, both addressed to
the spare protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable (on
spare protection unit)
Service Used
SNMP-SET on opticsIMTxProtectionUnitSwitchCommand
(forcedSwitch/noRequest)

Function Protection Status SN
MP
If
Function Description
F-1.88 Request TPS
Protection Scheme
Operational State
Y
This management function allows the managing system to request
the operational state of a HST TPS protection scheme.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionGroupTable
Service Used
SNMP-GET on opticsIMTxProtectionGroupOperationalState
F-1.89 Request TPS
Protection Status
Y
This management function allows the managing system to request
the current state of a TPS protection unit.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable
Service Used
SNMP-GET on:
• opticsIMTxProtectionUnitSwitchCommand
• opticsIMTxProtectionUnitSwitchCriteria
• opticsIMTxProtectionUnitSwitchStatus
F-1.90 Report TPS Protection
Switch Event
N
This management function allows the managed system to report
any protection switch event to the managing system, such as:
• protection switching (forced, manual or automatic switch)
• protection release (release of forced, manual or automatic
switch)
• lockout, release lockout.
Scope
OPTICSIM-RADIO-SWTC-MIB: opticsIMTxProtectionUnitTable
Service Used
SNMP-TRAP (opticsIMProtectionSwitchReporting) on:
• opticsIMTxProtectionUnitSwitchCommand
• opticsIMTxProtectionUnitSwitchCriteria
• opticsIMTxProtectionUnitSwitchStatus





07 RELEASED It 1


8BW 03598 0000 DSZZA 94/ 181


Common Loss Alarm

Function Configuration SN
MP
If
Function Description
F-1.100 Request CLA Activity N
This management function allows the managing system to request
the status of the CLA procedure activity: enabled or disabled.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-GET on opticsIMRadioCLAEnabled
F-1.101 Condition CLA
Activity
N
This management function allows the managing system to
condition the status of the CLA procedure activity: enabled or
disabled.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-SET on opticsIMRadioCLAEnabled

Function Operator
Commands and Status
SN
MP
If
Function Description
F-1.103 Invoke CLA Reset N
This management function allows the managing system to reset a
CLA active. The “resetting” syntax must be used. When the reset
has been completed, the agent has to change the value back to the
“notResetting” syntax.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-SET on opticsIMRadioCLAReset (resetting)
F-1.105 Request CLA
Procedure Status
N
This management function allows the managing system to request
the status of the CLA procedure: active or not active.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-GET on opticsIMRadioCLAStatus

Function Notifications SN
MP
If
Function Description
F-1.104 Report CLA Alarm N
This management function allows a managed system to report a
CLA alarm. It is addressed to an equipment object supporting the
radio transmit function.
Scope
OPTICSIM-RADIO-SWTC-MIB
Service Used
SNMP-TRAP:
- opticsIMAlarmCLARaise
- opticsIMAlarmCLAClear




07 RELEASED It 1


8BW 03598 0000 DSZZA 95/ 181



Tx Mute

Function Operator
Commands and Status
SN
MP
If
Function Description
F-1.120 Request Local
Transmitter Mute Status
Y
This management function allows a managing system to request
the status of the local radio transmitter in terms of mute function:
• no squelch active
• squelch active, required by the managing systems
• squelch active, required automatically by the agent
• squelch active for both the previous reasons
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxMuteTable
Service Used
SNMP-GET on the columnar objects:
• opticsIMRadioManLocalTxMute
• opticsIMRadioAutoLocalTxMute
F-1.121 Condition Local
Transmitter Mute Status
Y
This management function allows a managing system to mute a
local radio transmitter.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxMuteTable
Service Used
SNMP-SET on opticsIMRadioManLocalTxMute
F-1.122 Request Remote
Transmitter Mute Status
P
This management function allows a managing system to request
the status of the remote radio transmitter in terms of mute function:
• no squelch active
• squelch active, required by the managing systems
• squelch active, required automatically by the agent
• squelch active for both the previous reasons
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxMuteTable
Service Used
SNMP-GET on the columnar objects:
• opticsIMRadioManRemoteTxMute
• opticsIMRadioAutoRemoteTxMute
Note F-1.122: Only a manual Tx mute can be monitored.
F-1.123 Condition Remote
Transmitter Mute Status
Y
This management function allows a managing system to mute a
local radio transmitter.
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioTxMuteTable
Service Used
SNMP-SET on opticsIMRadioManRemoteTxMute

WST&Radio Service Channels Protections Switching




07 RELEASED It 1


8BW 03598 0000 DSZZA 96/ 181



Function SN
MP
If
Function Description
F-1.xxx All the functions N




Shifter Definition Functions

Function SN
M
PIf
Function Description
F- 1.140 Request Allowed
Shifter
Y This management function allows a managing system to request
the allowed shifter values and related central frequency for each
radio channel. These informations are identified by a shifter
identifier. The informations available are:
• lists of shifter values and associated central frequency
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMAllowedShifterTable
Service Used
SNMP-GET on the columnar objects:
• allowedShifterValue
• allowedShifterCentralFrequency
F- 1.141 Condition Shifter
Definition
Y This management function allows a managing system to configure
the shifter value and consequently the central frequency for a radio
channel.
The shifter value and central frequency are defined setting the
shifter identifier (radioShifterId) associated to the shifter value and
central frequency required (radioShifterValue and
radioShifterCentralFrequency) As a side effect of this operation the
agent must be set the radioShifterValue and 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
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioShifterTable
Service Used
SNMP-SET on radioShifterId
Note F- 1.141: this management function is allowed only to managers declared as “localct” in the related
MgrPollingManagerType object of the polling table.
F- 1.142 Request Shifter Value
and Central Frequency
Y This management function allows a managing system to request
the shifter value and related central frequency defined for a radio
channel. This information is provided by means of shifter identifier,




07 RELEASED It 1


8BW 03598 0000 DSZZA 97/ 181


shifter value and central frequency
Scope
OPTICSIM-RADIO-TRS-COMMON-MIB:
opticsIMRadioShifterTable
Service Used
SNMP-GET on the columnar objects:
• radioShifterId
• radioShifterValue
• radioShifterCentralFrequency

Analogue Points

Function SN
MP
If
Function Description
F-1. xxx All the functions N


Radio SPI Common Functions

Function SN
MP
If
Function Description
F-2.xx All the functions N


Radio SPI Urban Haul Functions

Function SN
MP
If
Function Description
F-2.xx All the functions N


Radio SPI Long Haul Functions

Function SN
MP
If
Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 98/ 181


F-2.xx All the functions N

Radio Frame Complementary Overhead Functions

Function SN
MP
If
Function Description
F-2.xx All the functions N


Radio SDH NE Functions

Function Synchronization SN
MP
If
Function Description
F-2.xx All the functions N


Radio PDH Functions

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 99/ 181


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

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

Function Notifications SN
MP
If
Function Description
F-3.10 Report Radio PDH
Alarms
Y
This management function allows a managed system to report
transmission alarm related to a radioPDHTTP.
Scope
OPTICSIM-RADIO-TRS-PDH-MIB: opticsIMRadioPDHTTPBidTable
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 100/ 181


SNMP-TRAP:
- opticsIMAlarmRxLOSRaise
- opticsIMAlarmRxLOSClear
- 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
7.3 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 Radio objects are defined in [13].

Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
opticsIMRadioTrsCommonMib
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioFrequencyTable
radioTxFrequency
radioRxFrequency
radioMinTxFrequency
radioMaxTxFrequency
All the 1+1
Radio port – Ch#0 20100




07 RELEASED It 1


8BW 03598 0000 DSZZA 101/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioShifterTable (note 2)
radioShifterId
radioShifterValue
radioShifterCentralFrequency
All the 1+1
Radio port – Ch#0 20100
All the 1+0 Radio port – Ch#1

xx01
(xx=01..50
max)
Radio port – Ch#1 xx01
(xx=01..50
max)
opticsIMAllowedShifterTable (note 2)
allowedShifterValue
allowedShifterCentralFrequency
All the 1+1
Radio port – Ch#0 xx00
(xx=01..50
max)
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioTxPowerTable
radioAtpcEnabled
radioMinAtpcTxPower
radioMaxAtpcTxPower
radioAtpcLowPowerThr
radioAtpcLowPowerMinThr
radioAtpcLowPowerMaxThr
radioTxNominalPower
radioTxCurrentPower
radioMinTxPower
radioMaxTxPower
radioMinAllowedAtpcTxPower
radioMaxAllowedAtpcTxPower
All the 1+1
Radio port – Ch#0 20100
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioAnalogueMeasuresTable
analogueMeasuresRadioChannelNumber
analogueMeasuresLocalTxPower
analogueMeasuresLocalRxMainPower
analogueMeasuresRemoteTxPower
analogueMeasuresRemoteRxMainPower
All the 1+1
Radio port – Ch#0 20100
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioTxMuteTable
opticsIMRadioManLocalTxMute
opticsIMRadioAutoLocalTxMute
opticsIMRadioManRemoteTxMute
All the 1+1
Radio port – Ch#0 20100
opticsIMAlarmAtpcLoopProblemRaise
opticsIMAlarmAtpcLoopProblemClear
opticsIMAlarmHighBERRaise (note 1)
opticsIMAlarmHighBERClear (note 1)
opticsIMAlarmEarlyWarningRaise
opticsIMAlarmEarlyWarningClear
opticsIMAlarmIncompatibleFrequencyRaise
opticsIMAlarmIncompatibleFrequencyClear
opticsIMAlarmIncompatiblePTXRaise
opticsIMAlarmIncompatiblePTXClear

opticsIMRadioTrsPdhMib
All the 1+0 Radio port – Ch#1 20101
Radio port – Ch#1 20101
opticsIMRadioPDHTTPBidTable
radioPDHTTPBidRadioChannelNumber
radioPDHTTPBidModulation
radioPDHTTPBidOperationalState
radioPDHTTPBidAsapIndex
All the 1+1
Radio port – Ch#0 20100
opticsIMRadioSwtcMib




07 RELEASED It 1


8BW 03598 0000 DSZZA 102/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
opticsIMRadioProtectionGroupTable
opticsIMRadioProtectionGroupType
opticsIMRadioProtectionGroupHitless
opticsIMRadioProtectionGroupRevertive
opticsIMRadioProtectionGroupOperationalState
All the 1+1

1
Ch#1 1; 1 opticsIMRadioProtectionUnitTable
opticsIMRadioProtectionUnitType
opticsIMRadioProtectionUnitSwitchCommand
opticsIMRadioProtectionUnitSwitchCriteria
opticsIMRadioProtectionUnitSwitchStatus
All the 1+1
Ch#0 1; 0
opticsIMTxProtectionGroupTable
opticsIMTxProtectionGroupRevertive
opticsIMTxProtectionGroupOperationalState
All the 1+1 HST 1
Ch#1 1; 1 opticsIMTxProtectionUnitTable
opticsIMTxProtectionUnitType
opticsIMTxProtectionUnitSwitchCommand
opticsIMTxProtectionUnitSwitchCriteria
opticsIMTxProtectionUnitSwitchStatus
All the 1+1 HST
Ch#0 1; 0
opticsIMRadioRxStaticDelayTable
opticsIMRadioAutoRxStaticDelayAlignment
opticsIMRadioManRxStaticDelay
opticsIMRadioManRxStaticDelayDirectWay
opticsIMRadioManRxStaticDelayIndirectWay
All the 1+1 Ch#Common

1; 99

(note 1) These alarm notifications are defined in the Radio domain but the related defects are detected
by the Main and Extension units (IDU).

(note 2) Not supported on ULS 2.0.0







07 RELEASED It 1


8BW 03598 0000 DSZZA 103/ 181


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.

8.1 Functional Description

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 .

Main Allowed
Configuration Types
‘OpticsIMAllowedNe
ConfigurationType’
value
‘OpticsIMAllowedNe
ConfigurationId’
value
Undefined
UNDEFINED 255
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
1+0 8E1/DS1-ETH (PSU2460) (note 1) 28
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
1+1 HST 16E1/DS1 (PSU2460) (note 1) 30




07 RELEASED It 1


8BW 03598 0000 DSZZA 104/ 181


Main Allowed
Configuration Types
‘OpticsIMAllowedNe
ConfigurationType’
value
‘OpticsIMAllowedNe
ConfigurationId’
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 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
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’
value
‘opticsIMSwUnitLabel’
string
1 EC
2 OC-R
3 FPGA-PONTO
4 FPGA-GAIA
5 FPGA-GAIA-EXT
6 FPGA-FENICE
7 FPGA-MEDUSA




07 RELEASED It 1


8BW 03598 0000 DSZZA 105/ 181


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
2E1 4QAM
4E1 4QAM
4E1DS1 4QAM
4DS1 (note 1) 4QAM
2E1 4QAM
4E1 4QAM or 16QAM
4E1DS1 4/16QAM
4DS1 (note 1) 4QAM
2E1 4QAM
4E1 4QAM
8E1 4QAM
4DS1 4QAM
8E1DS1 4QAM
8DS1 4QAM
2E1 4QAM
4E1 4QAM or 16QAM
8E1 4QAM or 16QAM
4DS1 (note 1) 4QAM
8E1DS1 4/16QAM
8DS1 (note 1) 4QAM or 16QAM




07 RELEASED It 1


8BW 03598 0000 DSZZA 106/ 181


2E1 4QAM
4E1 4QAM
8E1 4QAM
16E1 4QAM
1E3 4QAM
4DS1 (note 1) 4QAM
8DS1 (note 1) 4QAM
16DS1 (note 1) 4QAM
4QAM
1DS3 (note 1) 4QAM
2E1 4QAM
4E1 4QAM or 16QAM
8E1 4QAM or 16QAM
16E1 4QAM or 16QAM
1E3 4QAM or 16QAM
4DS1 (note 1) 4QAM
8DS1 (note 1) 4QAM or 16QAM
16DS1 (note 1) 4QAM or 16QAM
FULL FLEXIBLE
1DS3 (note 1) 4QAM or 16QAM

(note 1) Not supported on ULS 2.0.0


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’
value
NE Configuration Type Supported
1+0 8E1/DS1 (PSU24)
1+0 8E1/DS1 (PSU4860)
1+0 8E1/DS1 (PSU2460) (note 1)
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 (PSU4860)
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 (PSU24)
1+1 HST 8E1/DS1-ETH (PSU4860)
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)
4E1DS1 4QAM
4E1DS1 4/16QAM
8E1DS1 4QAM
8E1DS1 4/16QAM
1+1 FD 16E1/DS1 (PSU24)




07 RELEASED It 1


8BW 03598 0000 DSZZA 107/ 181


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
FULL FLEXIBLE
All

(note 1) Not supported on ULS 2.0.0


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:

Event Type
‘opticsIMOffNormalDescription’
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
Remote radio Tx mute (manual) (note 1)
Local manual Tx mute
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”.








07 RELEASED It 1


8BW 03598 0000 DSZZA 108/ 181


8.2 Management Functions

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

Function Event Reporting
Management
SN
MP
If
Function Description
F-1. Create Event Report

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 109/ 181


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

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

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 110/ 181


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
F-9. Request Alert Event
Configuration
N
This function allows a managing system to retrieve the
configuration of the alert notification mechanism.
Scope
This function permits to a managing system to retrieve data related
to the time and frequency counters used by managed system in
order to send an alert notification to the managing systems.
Service Used
SNMP-GET on the following scalar objects:
- tsdimAlertNotifTimeOut
- tsdimAlertNotifFreqCount
F-10. Condition Alert Event
Configuration
N
This function allows a managing system to modify the configuration
of the alert notification mechanism.
Scope
This function permits to a managing system to modify data related
to the time and frequency counters used by managed system in
order to send an alert notification to the managing systems.
Service Used
SNMP-SET on the following scalar objects:
- tsdimAlertNotifTimeOut
- tsdimAlertNotifFreqCount

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 111/ 181


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

Function Alarm Severity
Management
SN
MP
If
Function Description
F-17. Request Default ASAP
Severity
Y
This function allows a managing system to retrieve information
about the default severity used.
Scope
This function permits to retrieve the default severity used in case is
not defined a specific ASAP object for a certain probableCause.
Service Used
SNMP-GET on the tsdimAlarmSevDefault scalar object
F-18. Condition Default
ASAP Severity
Y
This function allows a managing system to modify information
about the used default severity.
Scope
This function permits to modify the default severity used in case is
not defined a specific ASAP object for a certain probableCause.
Service Used
SNMP-SET on the tsdimAlarmSevDefault scalar object
F-19. Request Next ASAP
Index
Y
This function allows a managing system to retrieve the next index
value to use in free ASAP creation.
Scope
This function permits to retrieve the value of the index to be used in




07 RELEASED It 1


8BW 03598 0000 DSZZA 112/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 113/ 181


F-26. Request ASAP User
Label
Y
This management function permits to request the User Label
associated to an ASAP entry.
Scope
TSDIM-SUPPORT-MIB: tsdimAlarmSevProfileTable
Service Used
SNMP-GET on tsdimAlarmSevProfileUserLabel

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

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

Function Backup and
Restore Management
SN
MP
If
Function Description
F-28. Request NE Software
Version
Y
This function allows a managing system to ask to a managed
system its NE software version in order to couple it with the backup
file.
Scope
This function permits to retrieve the software version managed




07 RELEASED It 1


8BW 03598 0000 DSZZA 114/ 181


object.
Service Used
SNMP-GET on the sysDescr managed object
F-29. Condition Backup File
Name
Y
This function allows a managing system to define the name of the
backup file.
Scope
This function permits to set the file name object.
Service Used
SNMP-SET on the opticsIMBackupFilename managed object
F-30. Request Backup
Manager Identifier
Y
This function allows a managing system to request the identifier
value of the managing system that has activated a backup
operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMBackupRequestorAddress managed
object
F-31. Condition Backup
Manager Identifier
Y
This function allows a managing system to define its proper
identifier value for backup operation. This will permit to have only
one operation at time.
Scope
This function permits to set the identifier object.
Service Used
SNMP-SET on the opticsIMBackupRequestorAddress managed
object
F-32. Condition Restore
Software Version
Y
This function allows a managing system to set to a managed
system the NE software version associated to the file that will be
restored.
Scope
This function permits to set the restore file software version
managed object.
Service Used
SNMP-SET on the opticsIMRestoreSWVersion managed object
F-33. Condition Restore File
Name
Y
This function allows a managing system to define the name of the
restore file.
Scope
This function permits to set the file name object.
Service Used
SNMP-SET on the opticsIMRestoreFilename managed object
F-34. Condition Restore
Manager Identifier
Y
This function allows a managing system to define its proper
identifier value for restore operation. This will permit to have only
one operation at time.
Scope
This function permits to set the identifier object.
Service Used
SNMP-SET on the opticsIMRestoreRequestorAddress managed
object
F-35. Request Restore
Manager Identifier
Y
This function allows a managing system to request the identifier
value of the managing system that has activated a restore
operation.
Scope
This function permits to retrieve the identifier object.
Service Used
SNMP-GET on the opticsIMRestoreRequestorAddress
managed object
F-36. Request Restore State Y
This function allows a managing system to ask to a managed
system the state of the restore operation.




07 RELEASED It 1


8BW 03598 0000 DSZZA 115/ 181


Scope
This function permits to retrieve the state of a restore operation.
Service Used
SNMP-GET on the opticsIMRestoreState managed object
F-37. Condition Restore
State
Y
This function allows a managing system to change the in-progress
state of the restore operation. A managing system has to specify
the following states:
- "downloading" state,
- "present" state when the file has been successfully transferred; in
case of Sub SNMP NE supporting Restore in one phase, the NE
implicitly set this state to "apply",
- "apply" state to communicate to the Agent that it has to apply the
restore file, applicable only to stand-alone SNMP NE supporting
Restore in two-phases.
The "absent" value is set by Agent as default value.
Scope
This function permits to modify the state of a restore operation.
Service Used
SNMP-SET on the opticsIMBackupState managed object
F-38. Request Backup State Y
This function allows a manager system to retrieve the state of the
Backup operation.
Scope
This function permits to get the Backup state scalar object.
Service Used
SNMP-GET on the opticsIMBackupState managed object

Function Agent Management SN
MP
If
Function Description
F-40. Request NE Installation
Type
Y
This function allows a managing system to ask to a managed
system its installation type (such as 4x4 board characteristic).
Scope
This function permits to retrieve the NE installation type managed
object.
Service Used
SNMP-GET on the tsdimNeInstallationType managed object
F-41. Request Board
Position
N
This function allows a managing system to ask to a managed
system its board position inside the shelf.
Scope
This function permits to retrieve the NE board position managed
object.
Service Used
SNMP-GET on the tsdimBoardPosition managed object
F-42. Request Info-Model
Version
Y
This function allows a managing system to ask to a managed
system which info-model version it supports.
Scope
This function permits to retrieve the NE Info-model version
managed objects.
Service Used
SNMP-GET on the tsdimInfoModelVersionMajor,
tsdimInfoModelVersionMinor and
tsdimInfoModelVersionMaintenance managed objects
F-44. Request SDH NE Label Y
This function allows a managing system to ask to a managed
system information about the SDH NE label configuration.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 116/ 181


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
Label
Y
This function allows a managing system to set to a managed
system the SDH NE label object.
Scope
This function permits to set the SDH NE label managed object.
Service Used
SNMP-SET on the tsdimSdhNeLabel managed object
F-86. Request Manager List N
This function allows a managing system to ask to a managed
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
This function allows a managing system to set to a managed
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
Control State
Y
This function allows a managing system to ask to a managed
system information about the Craft Terminal local access control
state.
Scope
This function permits to retrieve the Craft Terminal local access
control state managed object.
Service Used
SNMP-GET on the tsdimLacState managed object
F-49. Condition Local
Access Control State
Y
This function allows a managing system to set to a managed
system the object containing the information about the Craft
Terminal local access control state.
Scope
This function permits to set the Craft Terminal local access control
state managed object.
Service Used
SNMP-SET on the tsdimLacState managed object
F-50. Request Local Access
Control Time Out Period
Y
This function allows a managing system to ask to a managed
system information about the Craft Terminal local access control
time out period interval.
Scope
This function permits to retrieve the Craft Terminal local access
control time out period interval managed object.
Service Used
SNMP-GET on the tsdimLacNoResponseTimeOutPeriod
managed object
F-51. Condition Local
Access Control Time Out
Period
Y
This function allows a managing system to set to a managed
system the object containing the information about the Craft
Terminal local access control time out period interval.
Scope
This function permits to set the Craft Terminal local access control
time out period interval managed object.
Service Used
SNMP-SET on the tsdimLacNoResponseTimeOutPeriod
managed object




07 RELEASED It 1


8BW 03598 0000 DSZZA 117/ 181


F-58. Request NE Software
Release
Y
This function allows a managing system to ask to a managed
system which is its software release.
Scope
This function permits to retrieve the NE software release.
Service Used
SNMP-GET on the sysDescr managed object
F-59. Request NE Location Y
This function allows a managing system to ask to a managed
system which is its location value.
Scope
This function permits to retrieve the NE location.
Service Used
SNMP-GET on the sysLocation managed object
F-60. Condition NE Location Y
This function allows a managing system to modify the location
value of a managed system.
Scope
This function permits to modify the NE location.
Service Used
SNMP-SET on the sysLocation managed object
F-61. Request NE
SubRelease
Y
This function allows a managing system to ask to a managed
system which is its subrelease value.
Scope
This function permits to retrieve the NE subrelease.
Service Used
SNMP-GET on the sysName managed object
Note F-61: Function used to request license key information.
F-62. Request NE Allowed
Configurations
Y
This management function allow the managing system to request
the configurations allowed for the supported NE.
Scope
TSDIM-SNMPNE-MIB:
opticsIMAllowedNeConfigurationTypeTable
Service Used
SNMP-GET on opticsIMAllowedNeConfigurationType
F-63. Request NE
Configuration
Y
This management function allows the managing system to request
the NE configuration type. This information is provided by means of
NE configuration type identifier and associated string.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on the scalar objects:
· opticsIMNeConfigurationTypeId
· opticsIMNeConfigurationType
F-64. Condition NE
Configuration
Y
This management function allows the managing system to define
the NE configuration type. It is defined setting the identifier
(NeConfigurationTypeId object) associated to the NE configuration
type string required (NeConfigurationType object). As a side effect
of this operation the agent must set the NeConfigurationType
object with the configuration type string associated to this identifier.
The identifier provided must be included in the list of the allowed
NE configuration type identifiers.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on opticsIMNeConfigurationTypeId
F-65. Request Market Y
This management function allows the managing system to request
the market (ETSI or ANSI) in which the NE is used.
Scope
TSDIM-SNMPNE-MIB




07 RELEASED It 1


8BW 03598 0000 DSZZA 118/ 181


Service Used
SNMP-GET on opticsIMMarket

F-66. Condition Market Y
This management function allows the managing system to define
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
Name
Y
This management function allows the managing system to request
the NE name (it specifies NE type, configuration, frequency,
modulation).
Scope
TSDIM-SNMPNE-MIB: opticsIMNeConfiguration
Service Used
SNMP-GET on opticsIMNeEquipmentName

Function Software Download
Management
SN
MP
If
Function Description
F-67. Condition Server
Information
Y
This management function allows a managing system to configure
the (e.g. Ftp) Server information. This information is used by the
Client to connect the Server during a Software Download
Operation.
Scope
The managing system configures:
- the Server Address;
- the Server Port;
- the Server UserId;
- the Server Password;
- the Root Directory where the Software Package to be
downloaded is stored on the Server.
Service Used
SNMP-Set on opticsImSwdlServerAddress,
opticsImSwdlServerPort, opticsImSwdlServerPassword,
opticsImSwdlServerRootDir Scalar Objects.
F-68. Initiate a Downloading
Operation
Y
This management function allows a managing system to initiate a
software downloading operation.
Only one downloading operation can be performed at the same
time.
This operation can be performed only if the NE is not restoring the
MIB database that is if the opticsIMRestoreState has the value
"absent" or "present".
Upon activation of rowStatus the opticsIMswdlStatusIndicator is
changed to Downloading.
N.B. It is up to the agent the single Download running check.
Scope
The managing system configures:
1. The identifier of the new software release (SW Package
Version, Sw Package Label and Descriptor Name) to be delivered
to the managed system;
2. an optional flag (ForcedDowndload) which indicates whether the
version indicated by the identifier of the new software release has
to be loaded entirely regardless of the fact that some software units
may already be present in the NE.




07 RELEASED It 1


8BW 03598 0000 DSZZA 119/ 181


Service Used
SNMP-SET on the following columnar objects of
opticsIMSwdlInitTable:
- opticsImSwdlInitForcedDownload
- opticsImSwdlInitSwPkgVersion
- opticsImSwdlInitSwPkgLabel
- opticsImSwdlInitDescrName
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"ActivecreateAndGo" value.
F-69. Abort/Destroy a
Downloading Operation
Y
This management function has the aim to clean up the Download
operation at Agent side.
It could be used both to stop an in progress download and to
destroy the row occuped.
Scope
The managing system configures to Delete the
opticsImSwdlInitRowStatus.
Service Used
SNMP-SET on opticsImSwdlInitRowStatus columnar object to
"Destroy" value.
F-70. Request Downloading
Information
Y
This management function allows a managing system to request
downloading information at configurable polling expiration.
Scope
The managing system can retrieve the Percentage, the Total
Number of Bytes, the Current SW Unit Version and Label of the in-
progress Software Download operation.
When terminated the managing system can retrieve the Result of
previous Software Download operation, during an in-progress
Software Download the Result takes the "underDownloading"
value.
Service Used
SNMP-GET on
- opticsIMSwdlPercentage,
- opticsIMSwdlTotalBytes,
- opticsIMSwdlCurrentSwUnitVersion,
- opticsIMSwdlCurrentSwUnitLabel,
- opticsImSwdlResult.

Function Software Package
Management
SN
MP
If
Function Description
F-71. Activate a Stand-by
Software Version
Y
This function allows a managing system to activate a stand-by
software version which is already stored on the managed system.
It cannot be performed while the NE is downloading a database,
that 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




07 RELEASED It 1


8BW 03598 0000 DSZZA 120/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 121/ 181


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

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 122/ 181


Addresses and Reachability reachability.
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-GET on the following scalar objects:
- opticsIMMainNTPServerAddress
- opticsIMSpareNTPServerAddress
- opticsIMNTPServersReachabilityStatus
F-85. Condition NTP Servers
Addresses
Y
This management function allows the managing system to
condition the addresses of the NTP servers (main and spare).
Scope
TSDIM-SNMPNE-MIB
Service Used
SNMP-SET on the following scalar objects:
- opticsIMMainNTPServerAddress
- opticsIMServerNTPServerAddress

Function Filtering
Management
SN
MP
If
Function Description
F-89. Condition HD Retrieval
Time
Y
This management function permits to condition the HD retrieval
Time. The parameters to be configured are:
· the OS which has collected the HD
· the Begin Time
· the End Time
· the GranularityPeriod
Scope
OPTICSIM-COMMONPM-MIB: opticsIMFilterHistoryDataTable
Service Used
SNMP-SET on
- opticsIMFilterHDStartByOS
- opticsIMFilterHDBeginTimeInterval
- opticsIMFilterHDEndTimeInterval
- opticsIMFilterHDGranularityPeriod
Note F-89: opticsIMFilterHDStartByOS is not supported

F-90. Create Filter History
Data Entry
Y
This management function permits to create one Filter History Data
entry. The management system has to indicate in the creation
request:
· its own IP Address
· its own UDP Port
Scope
OPTICSIM-COMMONPM-MIB: opticsIMFilterHistoryDataTable
Service Used
SNMP-SET on opticsIMFilterHDRowStatus columnar object to
"createAndGo" value
F-91. Delete Filter History
Data Entry
Y
This management function permits to delete one Filter History Data
entry.
Scope
OPTICSIM-COMMONPM-MIB: opticsIMFilterHistoryDataTable
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).




07 RELEASED It 1


8BW 03598 0000 DSZZA 123/ 181





Function EPS add on
Management
SN
MP
If
Function Description
F-xx. All the functions N




8.3 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 Support domain objects are defined in [13].

Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
Value
tsdimSupportMib
tsdimEFDTable
tsdimEFDDest
tsdimEFDTrapId
tsdimEFDTrapObject
tsdimEFDPort
tsdimEFDLowestForwardedSeverity
tsdimEFDIndeterminate
tsdimEFDOperStatus
tsdimEFDRowStatus
tsdimEFDManagerIndex
Max 5 entries 1..N
tsdimAlarmLogTable
tsdimAlarmLogProbableCause
tsdimAlarmLogObjectClassIdentifier
tsdimAlarmLogObjectInstanceIdentifier
tsdimAlarmLogSeverity
tsdimAlarmLogSpecificProb
tsdimAlarmLogTime
Max 500 entries <time>;
<notifId>
tsdimEventLogTable
tsdimEventLogEventType
tsdimEventLogObjectClassIdentifier
tsdimEventLogObjectInstanceIdentifier
tsdimEventLogTime
Max 300 entries <time>;
<notifId>
tsdimLogTable
tsdimLogObjectClassIdentifier
tsdimLogAdminStatus
tsdimLogOperStatus
tsdimLogMaxSize
1..2




07 RELEASED It 1


8BW 03598 0000 DSZZA 124/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
Value
tsdimAPTTable
tsdimAPTAlarmProbableCause
tsdimAPTAlarmObjectClassIdentifier
tsdimAPTAlarmObjectInstanceIdentifier
tsdimAPTAlarmSeverity
tsdimAPTAlarmSpecificProb
tsdimAPTAlarmTime
Max 60 entries <time>;
<notifId>
ASAP#1 (predefined) 1
ASAP#2 (predefined) 2
ASAP#3 (predefined) 3
ASAP#4 (predefined) 4
tsdimAlarmSevProfileTable
tsdimAlarmSevProfileRowStatus
tsdimAlarmSevProfileUserLabel
Free use ASAPs
(max 3 entries)
5..N
ASAP#1 (predefined) 1; <trapId>
ASAP#2 (predefined) 2; <trapId>
ASAP#3 (predefined) 3; <trapId>
ASAP#4 (predefined) 4; <trapId>
tsdimAlarmSevTable
tsdimAlarmSevSeverity
tsdimAlarmSevRowStatus
tsdimAlarmSevSeverityNotServAff
Free use ASAPs
(max 3 entries)
5..N; <trapId>
opticsIMSwdlInitTable
opticsIMSwdlInitForcedDownload
opticsIMSwdlInitSwPkgVersion
opticsIMSwdlInitSwPkgLabel
opticsIMSwdlInitDescrName
opticsIMSwdlInitRowStatus
1
opticsIMSwPackageTable
opticsIMSwPackageCommand
opticsIMSwPackageActivationResult
opticsIMSwPackageActivationDate
opticsIMSwPackageCurrentState
opticsIMSwPackageLabel
opticsIMSwPackageVersion
opticsIMSwPackageOperationalState
1..2
1; 1 EC software unit
2; 1
1; 2 OC-R software unit
2; 2
1; 3 FPGA-PONTO software unit
2; 3
1; 4 FPGA-GAIA software unit
2; 4
1; 5 FPGA-GAIA-EXT software unit
2; 5
1; 6 FPGA-FENICE software unit
2; 6
1; 7
opticsIMSwUnitTable
opticsIMSwUnitLabel
opticsIMSwUnitVersion
opticsIMSwUnitSize
FPGA-MEDUSA software unit
2; 7
opticsIMAbnCondAffectedObjectListTable
opticsIMAbnCondAffectedObjectInstanceId
opticsIMOffNormalDescription
Max 50 entries 1..N




07 RELEASED It 1


8BW 03598 0000 DSZZA 125/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
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
tsdimLacState
tsdimLacNoResponseTimeOutPeriod
1
Undefined configuration 255 opticsIMAllowedNeConfigurationTypeTable
opticsIMAllowedNeConfigurationType
Scalable configurations 1..36




07 RELEASED It 1


8BW 03598 0000 DSZZA 126/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
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




07 RELEASED It 1


8BW 03598 0000 DSZZA 127/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
Value
opticsIMFilterHistoryDataTable
opticsIMFilterHDBeginTimeInterval
opticsIMFilterHDEndTimeInterval
opticsIMFilterHDGranularityPeriod
opticsIMFilterHDRowStatus
Entries created by the managers
(max 10 entries)
1..N

(note 1) See Communication and Routing Domain for the Management Functions.









07 RELEASED It 1


8BW 03598 0000 DSZZA 128/ 181


9 COMMUNICATION AND ROUTING DOMAIN
9.1 Functional Description

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
DTE V.11
Asynchronous (Codirectional)
DTE G.703
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.

9.2 Management Functions

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

Function IP Routing
Management
SN
MP
If
Function Description
F-1. Request IP Address
Configuration

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 129/ 181


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
F-3. Create IP Static Routing
Information
Y
This function allows a managing system to define different IP static
routing paths.
Scope
This function permits to create an IP static routing object.
Service Used
SNMP-SET on the following opticsIMIpStaticRoutingInfoTable
columnar object:
- opticsIMIpStaticIpAddress
- opticsIMIpStaticIpMask
- opticsIMIpStaticDefGateway
- opticsIMIpStaticInterfaceIndex
SNMP-SET on RowStatus columnar object to "createAndGo"
value.

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 130/ 181


F-12. Condition IP Address P
This function allows a managing system to condition the managed
system address.
Scope
This function permits to condition the IP address, mask and UDP of
the managed system.
Service Used
SNMP-SET on the following scalar objects (defined in TSDIM-
SNMPNE-MIB):
- tsdimSnmpAgtIpAddress
- tsdimSnmpAgtIpMask
- tsdimSnmpAgtUdpPort
Note F-12: tsdimSnmpAgtIpMask and tsdimSnmpAgtIpUdpPort objects are not supported.
F-13. Create OSPF Area Y
This function allows a managing system to define different OSPF
areas.
Scope
This function permits to create different OSPF Areas.
Service Used
SNMP-SET on the following opticsIMOspfAreaTable columnar
objects:
- opticsIMOspfAreaIpAddress
- opticsIMOspfAreaIpMask
- opticsIMOspfAreaStubFlag
SNMP-SET on RowStatus columnar object to "createAndGo"
value.

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

Function Manager Polling
Management
SN
MP
If
Function Description
F-7. Create Manager Polling
Information
Y
This function allows a managing system to define its polling
information
Scope
This function permits to create an object containing the information
needed to manage the manager polling functionality.
Service Used
SNMP-SET on the following opticsIMMgrPollingInfoTable
columnar object:
- opticsIMMgrPollingIpAddress
- opticsIMMgrPollingUdpPort




07 RELEASED It 1


8BW 03598 0000 DSZZA 131/ 181


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

Function Local Ethernet
Management
SN
MP
If
Function Description
F-16. Create Local Ethernet N
This function allows a managing system to create a local ethernet
interface.




07 RELEASED It 1


8BW 03598 0000 DSZZA 132/ 181


Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on the following columnar objects:
- opticsIMLocalEthernetIpAddress
- opticsIMLocalEthernetIpMask
- opticsIMLocalEthernetIpRoutingProtocol
- opticsIMLocalEthernetOspfAreaPointer
SNMP-SET on RowStatus columnar object to "createAndGo"
value.
F-17. Delete Local Ethernet N
This function allows a managing system to delete a local ethernet
interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on RowStatus columnar object to "destroy" value.
F-33. Activate Local Ethernet Y
This function allows a managing system to activate a local ethernet
interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on RowStatus columnar object to "active" value.
F-34. Deactivate Local
Ethernet
Y
This function allows a managing system to deactivate a local
ethernet interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on RowStatus columnar object to "nonInService"
value.
F-18. Request Local Ethernet
Information
Y
This function allows a managing system to request information
about local ethernet interfaces.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-GET on the following columnar objects:
- opticsIMLocalEthernetMacAddress
- opticsIMLocalEthernetIpAddress
- opticsIMLocalEthernetIpMask
- opticsIMLocalEthernetIpRoutingProtocol
- opticsIMLocalEthernetOspfAreaPointer
F-19. Condition Local
Ethernet Information
Y
This function allows a managing system to condition the
parameters related to local ethernet interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMLocalEthernetTable
Service Used
SNMP-SET on the following columnar objects:
- opticsIMLocalEthernetIpAddress
- opticsIMLocalEthernetIpMask
- opticsIMLocalEthernetIpRoutingProtocol
- opticsIMLocalEthernetOspfAreaPointer
Note F-19: Allowed values for routing protocol are: none, ospf.

Function Point-to-Point IP
Interface Management
SN
MP
If
Function Description




07 RELEASED It 1


8BW 03598 0000 DSZZA 133/ 181


F-20. Create Point-To-Point
IP Interface
N
This function allows a managing system to create a point-to-point
IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on the following columnar objects:
- opticsIMIpPointToPointIPType
- opticsIMIpPointToPointIPMode
- opticsIMIpPointToPointIPRoutingProtocol
- opticsIMIpPointToPointIPOspfAreaPointer
SNMP-SET on RowStatus columnar object to "createAndGo"
value.
F-21. Delete Point-To-Point
IP Interface
N
This function allows a managing system to delete a point-to-point
IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on RowStatus columnar object to "destroy" value.
F-22. Request Point-To-Point
IP Information
Y
This function allows a managing system to request information
about a point-to-point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-GET on the following columnar objects:
- opticsIMPointToPointIPType
- opticsIMPointToPointIPMode
- opticsIMPointToPointIPRoutingProtocol
- opticsIMPointToPointIPOspfAreaPointer
- opticsIMPointToPointIPRemoteAddress
F-23. Condition Point-To-
Point IP Information
Y
This function allows a managing system to condition the
parameters related to a point-to-point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
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.
F-24. Activate a Point-To-
Point IP Interface
Y
This function allows a managing system to activate a point-to-point
IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on RowStatus columnar object to "active" value.
F-25. Deactivate a Point-To-
Point IP Interface
Y
This function allows a managing system to deactivate a point-to-
point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on RowStatus columnar object to "notInService"
value.




07 RELEASED It 1


8BW 03598 0000 DSZZA 134/ 181


F-26. Report Point-To-Point
IP Interface Alarms
Y
This function allows a managed system to report the alarms
related t a point-to-point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-TRAP on:
- opticsIMAlarmLossOfSignalRaise/Clear
- opticsIMAlarmPPPFailRaise/Clear
Note F-26: LOS for G.703 NMS interface (DTE and asynchronous modes only) and PPP fail alarms.
F-27. Request Point-To-Point
IP Interface ASAP Pointer
Y
This function allows a managing system to request the ASAP
Pointer associated a point-to-point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-GET on opticsIMIpPointToPointIPAsapPointer.
F-28. Condition Point-To-
Point IP Interface ASAP
Pointer
Y
This function allows a managing system to condition the ASAP
Pointer associated a point-to-point IP interface.
Scope
OPTICSIM-COMMROU-MIB: opticsIMPointToPointIPTable
Service Used
SNMP-SET on opticsIMIpPointToPointIPAsapPointer.

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


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


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



9.3 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 Communication and Routing objects are defined in [13].





07 RELEASED It 1


8BW 03598 0000 DSZZA 135/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Description
Indexes
Value
opticsIMCommRouMib
opticsIMMgrPollingInfoTable
opticsIMMgrPollingIpAddress
opticsIMMgrPollingUdpPort
opticsIMMgrPollingTimeOut
opticsIMMgrPollingManagerType
opticsIMMgrPollingRowStatus
Entries created by the managers
(max 10 entries)
1..N
opticsIMInfoPolledTable
opticsIMInfoLastAlarmNotificationId
opticsIMInfoLastAlarmTime
opticsIMInfoLastEventNotificationId
opticsIMInfoLastEventTime
opticsIMInfoLastGenEventNotificationId
opticsIMInfoLastGenEventTime
Entries created as consequence of
managers actions
(max 10 entries)
1..N
opticsIMOspfAreaTable
opticsIMOspfAreaIpAddress
opticsIMOspfAreaIpMask
opticsIMOspfAreaStubFlag
opticsIMOspfAreaRowStatus
Entries created by the managers
(max 1+3 entries)

0 = backbone
1..N
opticsIMLocalEthernetTable
opticsIMLocalEthernetIpAddress
opticsIMLocalEthernetIpMask
opticsIMLocalEthernetRoutingProtocol
opticsIMLocalEthernetOspfAreaPointer
opticsIMLocalEthernetRowStatus
1
RF 1
V.11 2
opticsIMPointToPointIPTable
opticsIMPointToPointIPType
opticsIMPointToPointIPMode
opticsIMPointToPointIPRoutingProtocol
opticsIMPointToPointIPOspfAreaPointer
opticsIMPointToPointIPRemoteAddress
opticsIMPointToPointIPRowStatus
opticsIMPointToPointIPAsapIndex
G.703 3
opticsIMIpStaticRoutingInfoTable
opticsIMIpStaticIpMask
opticsIMIpStaticDefGateway
opticsIMIpStaticInterfaceIndex
opticsIMIpStaticRowStatus
Entries created by the managers <IP address>
opticsIMIpRoutingInfoTable
opticsIMIpRoutingDestIpMask
opticsIMIpRoutingDefGateway
opticsIMIpRoutingMetricValue
opticsIMIpRoutingRouteAge
opticsIMIpRoutingRouteType
opticsIMIpRoutingProtocol
opticsIMIpRoutingLocalPtpInterface
Entries created by the agent on
managers GET request
<IP address>








07 RELEASED It 1


8BW 03598 0000 DSZZA 136/ 181


10 OVERHEAD DOMAIN
10.1 Functional Description

One auxiliary and one EOW interface are supported by ULS NE. The related entries will be created by
the agent during the provisioning phase (see Equipment domain).

The default value for the opticsIMAuxiliaryPITTPBidType columnar object is ‘disabled’. The supported
values for this object are the following:
• v11Contradir64Kb
• g703-64Kb
• v11Codir64Kb
• v11Asynch9600b
• v11Asynch4800b
• v28Asynch9600b
• v28Asynch4800b

10.2 Management Functions

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

EOW Phonic Parameters

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 137/ 181


enabled or disabled.
Scope
OPTICSIM-OH-MIB: opticsIMEowPartyLineTable
Service Used
SNMP-GET on: opticsIMEowPartyLineEnabled

Auxiliary Interfaces

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

Function TP Status SN
MP
If
Function Description
F-1.15 Request Auxiliary
Operational State
Y
This management function allows the managing system to request
the operational state of the auxiliary interface.
Scope
OPTICSIM-OH-MIB: opticsIMAuxiliaryPITTPBidTable
Service Used
SNMP-GET on opticsIMAuxiliaryPITTPBidOperationalState
F- 1.16 Request Auxiliary
Connection Status
N This management function allows the managing system to request
if the auxiliary interface is involved in OH cross connection (‘0’
value indicates no cross connection on auxiliary port; values
different from ‘0’ indicates that auxiliary port is involved on cross
connection).
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 138/ 181


OPTICSIM-OH-MIB: opticsIMAuxiliaryPITTPBidTable
Service Used
SNMP-GET on: opticsIMAuxiliaryPITTPBidCrossConnectIdentifier

Function Notification SN
MP
If
Function Description
F- 1.12 Report Auxiliary
Physical Interface Alarms
Y This management function allows a managed system to report
transmission alarms related to auxiliary physical interfaces.
Scope
OPTICSIM-OH-MIB: opticsIMAuxiliaryPITTPBidTable
Service Used
SNMP-TRAP:
• opticsIMAlarmLossOfSignalRaise
• opticsIMAlarmLossOfSignalClear
Note F-1.12: LOS for G.703 64kb/s.

Overhead Bytes

Function Configuration SN
MP
If
Function Description
F- XX. All the functions. N


Function TP Status SN
MP
If
Function Description
F- XX. All the functions. N



10.3 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 Overhead objects are defined in [13].

Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
opticsIMOverheadMib
opticsIMEowDTMFTTPBidTable
opticsIMEowDTMFTTPBidPhoneNumber
All EOW port 1




07 RELEASED It 1


8BW 03598 0000 DSZZA 139/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
opticsIMAuxiliaryPITTPBidTable
opticsIMAuxiliaryPITTPBidType
opticsIMAuxiliaryPITTPBidAsapIndex
opticsIMAuxiliaryPITTPBidOperationalState
All Auxiliary port 301







07 RELEASED It 1


8BW 03598 0000 DSZZA 140/ 181


11 TEST DOMAIN
11.1 Functional Description

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.
(note 1) Not supported on ULS 2.0.0
The modality of work of all of these types of loopbacks is Loop-And-Continue.

11.2 Management Functions

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





07 RELEASED It 1


8BW 03598 0000 DSZZA 141/ 181


Function Configuration SN
MP
If
Function Description
F-1 Request Loopback
Configuration
Y
This management function allow the managing system to request
the chracteristics (TP to be tested, direction and behaviour of the
loopback) and the activation status (active or not active) of the
loopback.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-GET on:
• loopbackPointObjectInstance
• loopbackDirectionality
• loopbackPointAdditionalDefinition
• loopbackBehaviour
• loopbackActivation
F-2 Condition Loopback
Activation
Y
This management function allow the managing system to activate a
loopback test.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-SET on loopbackActivation
F-3 Request Near-End/Far-
End Loopback Type
Y
This management function allow the managing system to request if
the loopback is referred to the Near-End or Far-End NE and the
type of managers that can require the loopback activation.
This function will be used when a loopbacks management on radio
link base is supported.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackExtTable
Service Used
SNMP-GET on:
• loopbackNEType
• loopbackAllowedManager
F-4 Request Loopback Timer
Configuration
N
This management function allow the managing system to request
the activation date (if loopback is yet activated) and the time during
the loopback stays active.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-GET on:
SNMP-GET on:
• loopbackActivationDate
• loopbackTimeoutPeriod
F-5 Condition Loopback
Timeout
N
This management function allow the managing system to configure
the timer for loopback activation.
Scope
OPTICSIM-TEST-MIB: opticsIMLoopbackTable
Service Used
SNMP-SET on loopbackTimeoutPeriod







07 RELEASED It 1


8BW 03598 0000 DSZZA 142/ 181


11.3 Supported Objects and Naming Rules
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

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

1;
101..116
(note 2)
opticsIME1PathTTPTable
opticsIMDS1PathTTPTable (note 5)

2zz01
(note 1)
<trib> Port#xx internal
1; 101
(note 2)
opticsIME3PathTTPTable
opticsIMDS3PathTTPTable (note 5)
20101
nearEnd
<trib> Port#1 internal


(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

Object Instance Loopback
Table
Indexes
TP
Table
TP
Index
NE
Type
Additional Def. Directionality
Common;
1..16
opticsIME1pPITTPTable
opticsIMDS1pPITTPTable (note 5)
1xx99
(note 1)
nearEnd <trib> Port#xx externalLine




07 RELEASED It 1


8BW 03598 0000 DSZZA 143/ 181


Common;
1
opticsIME3pPITTPTable
opticsIMDS3pPITTPTable (note 5)
10199 <trib> Port#1 externalLine
Common;
18..33
opticsIME1PathTTPTable
opticsIMDS1PathTTPTable (note 5)

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

20199
farEnd
<trib Port#1 internal
Common;
101..116
(note 2)
opticsIME1PathTTPTable
opticsIMDS1PathTTPTable (note 5)

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

20199
nearEnd
<trib> Port#1 internal
1; 17 opticsIMCoderTTPTable 20101 nearEnd IDU Cable externalLine
1; 34 ODU Cable externalLine
1; 35
opticsIMRadioPDHTTPBidTable 20101 nearEnd
RF externalLine


0; 17 opticsIMCoderTTPTable 20100 nearEnd IDU Cable externalLine
0; 34 ODU Cable externalLine
0; 35
opticsIMRadioPDHTTPBidTable 20100 nearEnd
RF externalLine

(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





07 RELEASED It 1


8BW 03598 0000 DSZZA 144/ 181


12 SDH/PDH PERFORMANCE MONITORING DOMAIN
12.1 Functional Description

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
[MHz]
39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140
RS Blocks
number/sec.
19200 19200 9600 4800 2400 28000 14000 7000 3500
SES Threshold
(note 1)
5760 5760 2880 1440 720 8400 4200 2100 1050

(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
TP Table TP index
Configuration
20101 All the configurations opticsIMPdhFrameHopCurrentDataTable
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).





07 RELEASED It 1


8BW 03598 0000 DSZZA 145/ 181


12.2 Management Functions

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

SDH Performance Monitoring Measurement Collection

Function SN
MP
If
Function Description
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
Frame and Tributary Current
Data
SN
MP
If
Function Description
F-4.1 Create CD Entry N
This management function permits to allocate one CD entry. The
management system has to indicate in the creation request:
1) the monitoring point which it is associated to (indicated by
means of ifIndex)
2) the CD index (pmPdh<Layer>CDIndex), which indicates the
granularity period of the counter (15 min or 24 h) (please refer to
[14] for the corresponding values of the CD index)
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on the following columnar objects (optionally):
• pmPdh<Layer>CDMaxSuppressedIntervals
• pmPdh<Layer>CDThresholdDataInstance
• pmPdh<Layer>CDAsapIndex
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object to
"createAndGo " value







07 RELEASED It 1


8BW 03598 0000 DSZZA 146/ 181


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




07 RELEASED It 1


8BW 03598 0000 DSZZA 147/ 181


• ES
• SES
• UAS
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET to default Value on:
– pmPdh<Layer>CDSes
– pmPdh<Layer>CDUas
– pmPdh<Layer>CDBbe
– pmPdh<Layer>CDEs
F-4.2 Activate CD Entry Y
This management function permits to activate one CD entry.
It can be used:
• in case the CD is deactivated by the Agent (e.g. if TD pointer
does not point to an existing TD) to activate it.
• in case CD has been stopped by the Network Management
System, by means of F-4.14, to restart it.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object to
"active" value
F-4.14 Deactivate CD Entry Y
This management function permits to deactivate one CD entry to
stop the counters.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object to
"notInService" value
F-4.16 Condition CD Asap
Pointer
Y
This management function permits to set the ASAP Pointer related
to a Threshold cross alarm of a CD entry.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on pmPdh<Layer>CDAsapIndex
F-4.17 Request CD Asap
Pointer
Y
This management function permits to request the ASAP Pointer
related to a Threshold cross alarm of a CD entry.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-GET on pmPdh<Layer>CDAsapIndex

Function Request of PDH
Frame and Tributary Current
Data
SN
MP
If
Function Description
F-4.12 Request PM Data
Collection
Y
This management function permits to Request PM Data Collection.
The following counters can be retrieved:
• BBE
• ES
• SES
• UAS
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-GET on:




07 RELEASED It 1


8BW 03598 0000 DSZZA 148/ 181


– pmPdh<Layer>CDSes
– pmPdh<Layer>CDUas
– pmPdh<Layer>CDBbe
– pmPdh<Layer>CDEs

Function Release of PDH
Frame and Tributary Current
Data
SN
MP
If
Function Description
F-4.15 Delete CD Entry N
This management function permits to delete one CD entry.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on pmPdh<Layer>CDRowStatus columnar object to
"destroy" value

Function Report of PDH
Frame and Tributary PM
Alarms
SN
MP
If
Function Description
F-4.18 Report CD Alarms Y
This management function permits to report TCA and UAT alarms.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
• opticsIMAlarmThresholdCrossRaise
• opticsIMAlarmThresholdCrossClear
• opticsIMAlarmUnavailableTimeRaise
• opticsIMAlarmUnavailableTimeClear

Function Configuration of
PDH Frame and Tributary
History Data
SN
MP
If
Function Description
F-5.1 Request Elapsed Time Y
This management function permits to request the elapsed time in
the current interval.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDElapsedTime
F-5.2 Request Granularity
Period
Y
This management function permits to request the granularity period
(15 min or 24 h).
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDGranularityPeriod
F-5.4 Request Number of
Suppressed Intervals
Y
This management function permits to request the Number of
Suppressed Intervals.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDNumSuppressedIntervals
F-5.5 Request Suspect
Interval Flag
Y
This management function permits to request whether the History
data is suspect or not.
Scope




07 RELEASED It 1


8BW 03598 0000 DSZZA 149/ 181


OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDSuspectIntervalFlag
F-5.6 Request Start By OS N
This management function permits to identify the Management
System which started the measurement.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>HistoryDataTable
Service Used
SNMP-GET on pmPdh<Layer>HDStartByOS

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

Function Creation of PDH
Frame and Tributary
Threshold Data
SN
MP
If
Function Description
F-6.1 Create Threshold Data
Entry
Y
This management function permits to allocate one Threshold Data
entry. The management system has to indicate in the creation
request the index for the threshold data entry, which the
management system has previously got from the agent (GET on
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

Function Configuration of
PDH Frame and Tributary
Threshold Data
SN
MP
If
Function Description
F-6.3 Condition PM
Thresholds Assignment
Y
This management function permits to assign thresholds to PM
counters.
The thresholds are assigned setting, in the relative CD, the
Threshold Data Instance providing the Threshold values.




07 RELEASED It 1


8BW 03598 0000 DSZZA 150/ 181


Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-SET on pmPdh<Layer>CDThresholdDataInstance
F-6.4 Request PM Thresholds
Assignment
Y
This management function permits to request the assignment of
thresholds to PM counters.
Scope
OPTICSIM-PDH-PM-MIB: opticsIMPdh<Layer>CurrentDataTable
Service Used
SNMP-GET on pmPdh<Layer>CDThresholdDataInstance
F-6.5 Condition PM
Thresholds
Y
This management function permits to configure the thresholds for
PM counters.
The high and low thresholds for the following counters can be set:
• BBE
• ES
• SES
Scope
OPTICSIM-PDH-PM-MIB:
opticsIMPdh<Layer>ThresholdDataTable
Service Used
SNMP-SET on
– pmPdh<Layer>BbeHighThr
– pmPdh<Layer>BbeLowThr
– pmPdh<Layer>EsHighThr
– pmPdh<Layer>EsLowThr
– pmPdh<Layer>SesHighThr
– pmPdh<Layer>SesLowThr
F-6.6 Request PM Thresholds Y
This management function permits to request the thresholds for PM
counters.
The high and low thresholds for the following counters can be read:
• BBE
• ES
• SES
Scope
OPTICSIM-PDH-PM-MIB:
opticsIMPdh<Layer>ThresholdDataTable
Service Used
SNMP-SET on
– pmPdh<Layer>BbeHighThr
– pmPdh<Layer>BbeLowThr
– pmPdh<Layer>EsHighThr
– pmPdh<Layer>EsLowThr
– pmPdh<Layer>SesHighThr
– pmPdh<Layer>SesLowThr
F-6.9 Condition Threshold
Data User Label
N
This management function permits to configure the User Label
associated to a Threshold Data entry.
Scope
OPTICSIM-PDH-PM-MIB:
opticsIMPdh<Layer>ThresholdDataTable
Service Used
SNMP-SET on pmPdh<Layer>UserLabel
F-6.10 Request Threshold
Data User Label
N
This management function permits to request the User Label
associated to a Threshold Data entry.
Scope
OPTICSIM-PDH-PM-MIB:
opticsIMPdh<Layer>ThresholdDataTable
Service Used




07 RELEASED It 1


8BW 03598 0000 DSZZA 151/ 181


SNMP-GET on pmPdh<Layer>UserLabel

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





07 RELEASED It 1


8BW 03598 0000 DSZZA 152/ 181


12.3 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 SDH/PDH Performance Monitoring objects are defined in [13].

Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
opticsIMPdhPmMib
All 15 min. – Ch#1 20101; 1
All the 1+1 15 min. – Ch#0 20100; 1
All 24 h – Ch#1 20101; 2
opticsIMPdhFrameHopCurrentDataTable
pmPdhFrameHopCDElapsedTime
pmPdhFrameHopCDGranularityPeriod
pmPdhFrameHopCDMaxSuppressedIntervals
pmPdhFrameHopCDNumSuppressedIntervals
pmPdhFrameHopCDSuspectIntervalFlag
pmPdhFrameHopCDThresholdDataInstance
pmPdhFrameHopCDSes
pmPdhFrameHopCDUas
pmPdhFrameHopCDBbe
pmPdhFrameHopCDEs
pmPdhFrameHopCDRowStatus
pmPdhFrameHopCDAsapIndex
All the 1+1 24 h – Ch#0 20100; 2
All 15 min. – Ch#1 20101; 1;
period x
(x=1..96)
All the 1+1 15 min. – Ch#0 20100; 1;
period x
(x=1..96)
All 24 h – Ch#1 20101; 2;
period x
(x=1..8)
opticsIMPdhFrameHopHistoryDataTable
pmPdhFrameHopHDElapsedTime
pmPdhFrameHopHDGranularityPeriod
pmPdhFrameHopHDNumSuppressedIntervals
pmPdhFrameHopHDSuspectIntervalFlag
pmPdhFrameHopHDSes
pmPdhFrameHopHDUas
pmPdhFrameHopHDBbe
pmPdhFrameHopHDEs
All the 1+1 24 h – Ch#0 20100; 2;
period x
(x=1..8)
15 min 1..3
(note 1)
opticsIMPdhFrameHopThresholdDataTable
pmPdhFrameHopSesHighThr
pmPdhFrameHopSesLowThr
pmPdhFrameHopBbeHighThr
pmPdhFrameHopBbeLowThr
pmPdhFrameHopEsHighThr
pmPdhFrameHopEsLowThr
pmPdhFrameHopRowStatus
All
24 h 4..6
(note 2)
opticsIMPdhFrameLinkCurrentDataTable All the 1+1 15 min. – Ch#Common 20199; 1




07 RELEASED It 1


8BW 03598 0000 DSZZA 153/ 181


Table Entry
Supported Objects
(Table/Scalar/Trap)
Configuration Description
Indexes
Value
pmPdhFrameLinkCDElapsedTime
pmPdhFrameLinkCDGranularityPeriod
pmPdhFrameLinkCDMaxSuppressedIntervals
pmPdhFrameLinkCDNumSuppressedIntervals
pmPdhFrameLinkCDSuspectIntervalFlag
pmPdhFrameLinkCDThresholdDataInstance
pmPdhFrameLinkCDSes
pmPdhFrameLinkCDUas
pmPdhFrameLinkCDBbe
pmPdhFrameLinkCDEs
pmPdhFrameLinkCDRowStatus
pmPdhFrameLinkCDAsapIndex
All the 1+1 24 h – Ch#Common 20199; 2
All the 1+1 15 min. – Ch#Common 20199; 1;
period x
(x=1..96)
opticsIMPdhFrameLinkHistoryDataTable
pmPdhFrameLinkHDElapsedTime
pmPdhFrameLinkHDGranularityPeriod
pmPdhFrameLinkHDNumSuppressedIntervals
pmPdhFrameLinkHDSuspectIntervalFlag
pmPdhFrameLinkHDSes
pmPdhFrameLinkHDUas
pmPdhFrameLinkHDBbe
pmPdhFrameLinkHDEs
All the 1+1 24 h – Ch#Common 20199; 2;
period x
(x=1..8)
15 min 1..2
(note 1)
opticsIMPdhFrameLinkThresholdDataTable
pmPdhFrameLinkSesHighThr
pmPdhFrameLinkSesLowThr
pmPdhFrameLinkBbeHighThr
pmPdhFrameLinkBbeLowThr
pmPdhFrameLinkEsHighThr
pmPdhFrameLinkEsLowThr
pmPdhFrameLinkRowStatus
All
24 h 3..4
(note 3)

(note 1) index value ‘1’ is reserved for default entry not modifiable by managing system.

(note 2) index value ‘4’ is reserved for default entry not modifiable by managing system.

(note 3) index value ‘3’ is reserved for default entry not modifiable by managing system.






07 RELEASED It 1


8BW 03598 0000 DSZZA 154/ 181


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.





07 RELEASED It 1


8BW 03598 0000 DSZZA 155/ 181



• 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




07 RELEASED It 1


8BW 03598 0000 DSZZA 156/ 181



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




07 RELEASED It 1


8BW 03598 0000 DSZZA 157/ 181


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.


13.2 Management Functions

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

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

Function SNMPv2
Security Management
SN
MP
If
Function Description
F-44 Condition New User
Creation
Y This management function allows the managing system to create a new
user profile in the managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”userCreation”>
_ opticsIMCorollaryUsername: <admin username>
_ opticsIMCorollaryPassword: <admin password>
_ opticsIMUserUsername: <new username>
_ opticsIMUserPassword: <password of the new user>
_ opticsIMUserRights: <user rights>
F-45 Condition User
Deletion
Y This management function allows the managing system to delete an
user profile in the managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”userDeletion”>
_ opticsIMCorollaryUsername: <admin username>
_ opticsIMCorollaryPassword: <admin password>
_ opticsIMUserUsername: <operator username>
F-46 Condition Password
Verification
Y This management function allows the managing system to require the
verification of the content of the
password field.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”checkPassword”>
_ opticsIMUserUsername: <operator username>
_ opticsIMUserPassword: <operator password>
_ opticsIMCtUserRights: <fulfilled with 0 (zero)>
F-47 Condition For
Password changed By
Y This management function allows the managing system to change the
password related to the operator




07 RELEASED It 1


8BW 03598 0000 DSZZA 158/ 181


Function SNMPv2
Security Management
SN
MP
If
Function Description
User that is executing the request.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”changePasswordByUser”>
_ opticsIMUserUsername: <operator username>
_ opticsIMUserPassword: <old operator password>
_ opticsIMCorollaryPassword: <new operator password>
F-48 Condition For
Password changed By
Administrator
Y This management function allows the managing system to change the
password related to an operator .
The operation is made by an operator with Administrator profile rights.
Scope
OPTICSIM-SECURITY-MIB: opticsIMUserOperationTable
Service Used
SNMP-SET on
_ opticsIMUserOperationOperation: <”changePasswordByAdmin”>
_ opticsIMUserUsername: <operator username>
_ opticsIMUserPassword: <new operator password>
_ opticsIMCorollaryUsername: <admin username>
_ opticsIMCorollaryPassword: <admin password>
F-49 Request Username
List
Y This management function allows the managing system to get the list of
all usernames admitted in the
managed system.
Scope
OPTICSIM-SECURITY-MIB: opticsIMCtUserTable
Service Used
SNMP-GET-NEXT on
_ opticsIMCtUserId
_ opticsIMCtUserRights


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

Table Entry Supported Objects
(Table/Scalar/Trap)
Description Indexes Values
opticsIMSecurityMIB
opticsIMCtUserTable
opticsIMCtUserId
opticsIMCtUserPassword
opticsIMCtUserRights
opticsIMCtRowStatus
Max 25 entries 1..N (note 1)




07 RELEASED It 1


8BW 03598 0000 DSZZA 159/ 181


opticsIMUserOperationTable
opticsIMUserOperationOperation
opticsIMUserUsername
opticsIMUserPassword
opticsIMCorollaryUsername
opticsIMCorollaryPassword
opticsIMCtUserRights
Only one entry 1


(note 1) index value ‘1’ is reserved for default user ‘initial’.





07 RELEASED It 1


8BW 03598 0000 DSZZA 160/ 181


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
Affecting
Evaluation
Equipment
Type
Equipmen
t
Expected
Alarm
Description
1+0 1+1
Cable Loss IDU SA
SAac
(note 3)
Card Fail SA
SAac
(note 2)
Equipment Mismatch SA
SAac
(note 2)
E1 RDI egressing (Rx side) (note 1) NSA NSA
E1 RDI ingressing (Tx side) (note 1) NSA NSA
High BER SA
SAac
(note 3)
Housekeeping Alarm NSA NSA
Lan Failure NSA NSA
Link Identifier Mismatch SA SA
Loss of Frame of PDH tributary
ingressing (Tx side) (note 1)
SA SA
Loss of Frame of PDH tributary
egressing (Rx side) (note 1)
SA SA
Loss of Frame of PDH signal Radio
side
SA
SAac
(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
(DTE and Asynchronous mode only)
NSA NSA
Low BER NSA NSA
PDH-AIS egressing (Rx side) SA SA
PDH-AIS ingressing (Tx side) SA SA
PPP IP Fail NSA NSA
Main Scalable Unit ±24 V Supply

Main Scalable Unit ±48/±60 V
Range Supply

Main Scalable Unit ±24/±60 V
Range Supply

M24S

M4860S


M2460S




TCA on Hop Section SA
SAac
(note 3)




07 RELEASED It 1


8BW 03598 0000 DSZZA 161/ 181


Service
Affecting
Evaluation
Equipment
Type
Equipmen
t
Expected
Alarm
Description
1+0 1+1
TCA on Link Section (note 3) - SA
UAT on Hop Section SA
SAac
(note 3)
UAT on Link Section (note 3) - SA
Firmware Download in progress
NSA NSA

Service
Affecting
Evaluation
Equipment
Type
Equipmen
t
Expected
Alarm
Description
1+0 1+1
Cable Loss IDU -
SAac
(note 3)
Card Fail -
SAac
(note 2)
Card Missing -
SAac
(note 2)
Equipment Mismatch -
SAac
(note 2)
E1 RDI egressing (Rx side) (note 1) - NSA
E1 RDI ingressing (Tx side) (note 1) - NSA
High BER -
SAac
(note 3)
Link Identifier Mismatch - SA
Loss of Alignment - NSA
Loss of Frame of PDH tributary
ingressing (Tx side) (note 1)
- SA
Loss of Frame of PDH tributary
egressing (Rx side) (note 1)
- SA
Loss of Frame of PDH signal Radio
side
-
SAac
(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
(DTE and Asynchronous mode only)
- NSA
Low BER - NSA
PDH-AIS egressing (Rx side) - SA
PDH-AIS ingressing (Tx side) - SA
TCA on Hop Section -
SAac
(note 3)

Extension Scalable Unit ±24 V
Supply

Extension Scalable Unit ±48/±60
V Range Supply

Extension Scalable Unit ±24/±60
V Range Supply




E24S


E4860S


E2460S



TCA on Link Section - SA




07 RELEASED It 1


8BW 03598 0000 DSZZA 162/ 181


Service
Affecting
Evaluation
Equipment
Type
Equipmen
t
Expected
Alarm
Description
1+0 1+1
UAT on Hop Section -
SAac
(note 3)
UAT on Link Section - SA
Unconfigured Equipment - NSA
Firmware Download in progress
NSA NSA
Unconfigured Equipment (note 4) - NSA

Service
Affecting
Evaluation
Equipment
Type
Equipmen
t
Expected
Alarm
Description
1+0 1+1
Card Fail SA SA
Card Missing SA SA
Client Signal Fail egressing (Rx side) NSA NSA
Loss of Signal on Ethernet port (link
down)
SA SA
Loss of GFP on Ethernet port
egressing (Rx side)
SA SA

Ethernet unit

P2DATAS
Unconfigured Equipment (note 5) NSA NSA
Card Fail SA
SAac
(note 2)
Card Missing SA
SAac
(note 2)
Equipment Mismatch SA
SAac
(note 2)
Loss of Signal of PDH tributary SA SA

8xE1/DS1 plug-in unit

1xE3/DS3 plug-in unit



P8E1DS1

P1E3DS3

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




07 RELEASED It 1


8BW 03598 0000 DSZZA 163/ 181


ODU Alarms

Service Affecting
Evaluation
Equipment
Type

Equipment
Expected

Alarm
Description 1+0
1+1
FD
1+1
HST
ATPC Loop NSA NSA NSA
Card Fail SA SAac SAac
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
(note 2)
SA NSA SAac
Modulation Function Failure (note 7) SA NSA SAac
ODU not responding (note 1) SA SAac SAac
Provisioned Frequency incompatible with
actual HW
SA SAac SAac
Provisioned Tx Power incompatible with
actual HW
NSA NSA NSA
Receiving Function Failure (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

ODU ETSI

ODU ANSI

ODU-E

ODU-A
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”.
(note 8) Only in the 1+1 configurations with Hitless Switch.




07 RELEASED It 1


8BW 03598 0000 DSZZA 164/ 181


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
Description
Notification Type
(Mib)
Table/Scalar
(Mib)
Index
Value
Equipment
Label
Remote NE Failure
Indication
RemoteNEFailure
(tsdimSnmpNEMib)
EquipmentTable
(opticsIMEqptMib)
1.1.0.0
Housekeeping Alarm HousekeepingAlarm
(opticsIMEqptMib)
ExternalInputPoint
(opticsIMEqptMib)
1..6
Card Fail ReplaceUnitProblem
(opticsIMEqptMib)
1.1.1.0
1.1.1.1

1.2.0.0
1.3.1.0
1.3.1.1

1.4.0.0
MAIN Ch#1
MAIN/<(note 1)>
Ch#1
ODU Ch#1
EXT Ch#0
EXT/<(note 1)>
Ch#0
ODU Ch#0
Card Missing ReplaceUnitMissing
(opticsIMEqptMib)
1.1.1.1

1.3.1.0
1.3.1.1
MAIN/<(note 1)>
Ch#1
EXT Ch#0
EXT/<(note 1)>
Ch#0
Equipment Mismatch ReplaceUnitTypeMismatch
(opticsIMEqptMib)
1.1.1.0
1.1.1.1

1.2.0.0
1.3.1.0
1.3.1.1

1.4.0.0
MAIN Ch#1
MAIN/<(note 1)>
Ch#1
ODU Ch#1
EXT Ch#0
EXT/<(note 1)>
Ch#0
ODU Ch#0
Lan Failure LanFailure
(opticsIMEqptMib)
EquipmentTable
(opticsIMEqptMib)
1.1.1.0 MAIN Ch#1

ODU not responding InternalCommunicationProbl EquipmentTable 1.2.0.0 ODU Ch#1




07 RELEASED It 1


8BW 03598 0000 DSZZA 165/ 181


Objects
Alarm
Description
Notification Type
(Mib)
Table/Scalar
(Mib)
Index
Value
Equipment
Label
em
(opticsIMEqptMib)
1.4.0.0 ODU Ch#0
Software Version
Mismatch
VersionMismatch
(opticsIMEqptMib)
1.2.0.0
1.4.0.0
ODU Ch#1
ODU Ch#0
Stand-by Software
Version Mismatch
StandByVersionMismatch
(opticsIMEqptMib)
1.2.0.0
1.4.0.0
ODU Ch#1
ODU Ch#0
Unconfigured Equipment UnconfiguredEquipmentPre
sent
(opticsIMEqptMib)
1.1.1.0

1.1.0.0
1.3.1.0
1.4.0.0
MAIN/Plug-in
Ch#1
EXT Ch#0
EXT/Plug-in
Ch#0
ODU Ch#0
Firmware Download in
progress
FirmwareDownloadOnGoing
(opticsIMEqptMib)
(opticsIMEqptMib)
1.1.1.0
1.3.1.0
1.2.0.0
1.4.0.0
MAIN Ch#1
EXT Ch#0
ODU Ch#1
ODU Ch#0

(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)
•E3, when the 1xE3/DS3 plug-in is provisioned and it configured to work in E3 mode
•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
Alarm
Description
Notification Type
(Mib)
Table/Scalar
(Mib)
Index
Value
Loss of 64 kbit/s G.703
Auxiliary Signal
LossOfSignal
(tsdimSnmpNEMib)
AuxiliaryPITTPBidTable
(opticsIMOverheadMib)
301
Cable Loss IDU CableLOS
(tsdimSnmpNEMib)
High BER HighBER
(opticsIMRadioTrsCommonMib)
Loss of Frame of PDH signal
Radio side
LossOfFrame
(tsdimSnmpNEMib)
CoderTTPTable
(opticsIMTrsPdhMib)

20101
20100
E1 RDI ingressing (Tx side) E1pPITTPTable
(opticsIMTrsCommonMib)
1xx01 or
1xx99
(xx=1..16)
(note 1)
E1 RDI egressing (Rx side)
RemoteDefectIndication
(tsdimSnmpNEMib)
E1PathTTPTable
(opticsIMTrsCommonMib)
2xx01 or
2xx99
(xx=1..16)
(note 2)
Loss of Frame of PDH
tributary ingressing (Tx side)
LossOfFrame
(tsdimSnmpNEMib)
Loss of Signal of PDH
tributary
LossOfSignal
(tsdimSnmpNEMib)
PDH-AIS ingressing
(Tx side)
opticsIMAlarmAis
(tsdimSnmpNEMib)
E1pPITTPTable
(opticsIMTrsCommonMib)
Ds1pPITTPTable (note 3)
(opticsIMTrsCommonMib)
E3pPITTPTable
(opticsIMTrsCommonMib)
1xx01 or
1xx99
(xx=1..16)
(note 1)




07 RELEASED It 1


8BW 03598 0000 DSZZA 166/ 181


Objects
Ds3pPITTPTable (note 3)
(opticsIMTrsCommonMib)
Loss of Frame of PDH
tributary egressing (Rx side)
LossOfFrame
(tsdimSnmpNEMib)
PDH-AIS egressing
(Rx side)
opticsIMAlarmAis
(tsdimSnmpNEMib)
E1PathTPTable
(opticsIMTrsCommonMib)
E3PathTTPTable
(opticsIMTrsCommonMib)
Ds1PathTTPTable (note 3)
(opticsIMTrsCommonMib)
Ds3PathTTPTable (note 3)
(opticsIMTrsCommonMib)
2xx01 or
2xx99
(xx=1..16)
(note 2)

Loss of GFP on Ethernet port
egressing (Rx side)
LossOfFrame
(tsdimSnmpNEMib)
GfpConfTable
(opticsIMGFPMib)
29901
Loss of Signal on Ethernet
port (link down)
LossOfSignal
(tsdimSnmpNEMib)
ifMauTable
(mauMod)
11701;1
11801;1
TCA on Hop Section TCA
(tsdimSnmpNEMib)
UAT on Hop Section UnavailableTime
(tsdimSnmpNEMib)
PdhFrameHopCurrentDataT
able
(opticsIMPdhPmMib)
20101; 1
20101; 2
20100; 1
20100; 2
TCA on Link Section TCA
(tsdimSnmpNEMib)
UAT on Link Section UnavailableTime
(tsdimSnmpNEMib)
PdhFrameLinkCurrentDataT
able
(opticsIMPdhPmMib)
20199; 1
20199; 2
Loss of 64kbit/s G.703 NMS
Signal (DTE and
Asynchronous mode only)
LossOfSignal
(tsdimSnmpNEMib)
3
PPP IP Fail PPPFail
(tsdimSnmpNEMib)
PointToPointIPTable
(opticsIMCommRouMib)
1
2
3
ATPC Loop AtpcLoopProblem
(opticsIMRadioTrsCommonMib)
Early Warning EarlyWarning
(opticsIMRadioTrsCommonMib)
Provisioned Frequency (or
shifter value) incompatible
with actual HW
IncompatibleFrequency
(opticsIMRadioTrsCommonMib)
Provisioned Tx Power
incompatible with actual HW
IncompatiblePTX
(opticsIMRadioTrsCommonMib)
Receiving Function Failure RxFail
(tsdimSnmpNEMib)
Transmission Function
Failure
TxFail
(tsdimSnmpNEMib)
RadioPDHTTPBidTable
(opticsIMRadioTrsPdhMib)
20101
20100

Demodulation Function
Failure
DemFail
(tsdimSnmpNEMib)
Loss of Signal for the
Modulation Function
ModLOS
(tsdimSnmpNEMib)
Modulation Function Failure ModFail
(tsdimSnmpNEMib)
RadioPDHTTPBidTable
(opticsIMRadioTrsPdhMib)

20101
20100

Loss of Alignment LossOfAlignment
(tsdimSnmpNEMib)
RxStaticDelayTable
(opticsIMRadioSwtcMib)
1; 99

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





07 RELEASED It 1


8BW 03598 0000 DSZZA 167/ 181


(note 3) Not supported on ULS 2.0.0





07 RELEASED It 1


8BW 03598 0000 DSZZA 168/ 181


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
Alarms
ASAP#2
No Remote
Alarms
ASAP#3
All
Alarms
ASAP#4
Notification Type
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






07 RELEASED It 1


8BW 03598 0000 DSZZA 169/ 181






Communication Alarms

Primary
Alarms
ASAP#2
No Remote
Alarms
ASAP#3
All
Alarms
ASAP#4
Notification
Type
Config.
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
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





07 RELEASED It 1


8BW 03598 0000 DSZZA 170/ 181


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 Read-only mode (only for GET operations) or in the mode specified
case by case.


A.1 MENU ITEM FUNCTIONS

Administrator
Construc
tor
Operator
CraftPerso
n
Viewer
Configuration
Menu
LCT
RCT
&
NM
NM LCT
RCT
&
NM
LCT RCT LCT
RCT
&
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
Etherne
t
Full Full Read Only Full Read Only
IP Full Full Read Only Full Read Only
Network
Config.
Routing Read Only Read Only Read Only Read Only Read Only
System Setting Full Full Read Only Full Read Only




07 RELEASED It 1


8BW 03598 0000 DSZZA 171/ 181


Administrator
Construc
tor
Operator
CraftPerso
n
Viewer
Configuration
Menu
LCT
RCT
&
NM
NM LCT
RCT
&
NM
LCT RCT LCT
RCT
&
NM
Type&M
arket
Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Capacity
&Modulat
ion
Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Impeden
ce
Full
Not
Supported
Not Supported Full Not Supported
Tributary
Conf
Full
Not
Supported
Not Supported Full Not Supported
Criteria
Radio
prot.
Full
Not
Supported
Not Supported Full Not Supported
Criteria
Mux/De
mux prot.
Full
Not
Supported
Not Supported Full Not Supported
Criteria
HST Tx
prot.
Full
Not
Supported
Not Supported Full Not Supported
ATPC
enable
Full
Not
Supported
Not Supported Full Not Supported
RTPC-
Nominal
Power
Read
Only
Not
Supported
Not Supported
Read
Only
Not Supported
RTPC-Tx
Power
Full
Not
Supported
Not Supported Full Not Supported
Shifter Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Tx Freq. Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Rx Freq. Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Local
conf.
Full
Read
Only
Not
Supported
Not Supported Full
Read
Only
Not Supported
Quick
Config.
(note
1)
OSPF Ful
Not
Supported
Not Supported Ful Not Supported




07 RELEASED It 1


8BW 03598 0000 DSZZA 172/ 181


Administrator
Construc
tor
Operator
CraftPerso
n
Viewer
Configuration
Menu
LCT
RCT
&
NM
NM LCT
RCT
&
NM
LCT RCT LCT
RCT
&
NM
IP static Ful
Not
Supported
Not Supported Ful Not Supported
NMS RF Ful
Not
Supported
Not Supported Ful Not Supported
NMS
V11
Ful
Not
Supported
Not Supported Ful Not Supported
NMS
G703
Ful
Not
Supported
Not Supported Ful Not Supported
Ethernet Ful
Not
Supported
Not Supported Ful Not Supported
RCT NM
Users
manag.
Full
Full
Not
Sup
port
ed
Not
Supported
Not Supported
Not
Supported
Not Supported
RCT NM RCT NM RCT NM
Profile
Manag.
Change
passwo
rd
Full
Full
Not
Sup
port
ed
Not
Supported
Full
Full
Not
Supp
orted
Full Full
Full
Not
Sup
port
ed
(note 1) If LAC not granted the ‘Quick Configuration’ menu is Not-Supported.




07 RELEASED It 1


8BW 03598 0000 DSZZA 173/ 181



Diagnosis
Menu
Administrat
or
Constru
ctor
Operator CraftPerson Viewer

LCT
&
RCT
NM
NM
LCT
&
RCT
NM
LCT RCT
LCT
&
RCT
NM
Full
Full
(note1)
Full
Full
(note 1)
Full

Full
Read
Only
Log
Browsing
Read
Only
Read
Only
Read Only Read Only Read Only
Performanc
e Data
-
Read
Only
Read
Only
- Read Only - - Read Only
Remote
Inventory
Read Only
Read
Only
Read Only Read Only Read Only
Abnormal
Condition
Read Only
Read
Only
Read Only Read Only Read Only
Summary
Block
Read Only
Read
Only
Read Only Read Only Read Only
Current
Configuratio
n View
Read Only
Read
Only
Read Only Read Only Read Only
(note 1) On NM the AS functionality are partially supported (some buttons on the screen are disabled).





07 RELEASED It 1


8BW 03598 0000 DSZZA 174/ 181



(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).
(note 2) These features are Not-Supported if LAC is not granted.
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
(note 2) Full Not Supported Not Supported Full Not Supported
Mib
Management
(note 2)
Full Not Supported Not Supported Full Not Supported
SW Key Read Only Read Only Read Only Read Only Read Only




07 RELEASED It 1


8BW 03598 0000 DSZZA 175/ 181



Administrator Constructor Operator CraftPerson Viewer
SW
Download
Menu
LCT&RCT&NM NM LCT&RCT&NM LCT&RCT LCT&RCT&NM
Server
Access
Configuration
(note 1)
Full Full Not Supported Full Not Supported
Init SW
Download
(note 1)
Full Full Not Supported Full Not Supported
SW Status
Full Full ReadOnly Full ReadOnly
(note 1) In case of LAC not granted this feature is Not-Supported.

A.2 Functions View

Administrator Constructor Operator CraftPerson Viewer
Equipment
LCT&RCT&NM NM LCT&RCT&NM LCT&RCT LCT&RCT&NM
Equipment
Type
Read Only Read Only Read Only Read Only Read Only
User Label Read Only Read Only Read Only Read Only Read Only
Alarm Profile Full Full Full Full Read Only
Remote
Inventory
Read Only Read Only Read Only Read Only Read Only






07 RELEASED It 1


8BW 03598 0000 DSZZA 176/ 181


Administrator Constructor Operator CraftPerson Viewer
External
Points
(IN/OUT)
LCT&RCT&NM NM LCT&RCT&NM LCT&RCT LCT&RCT&NM
User
Label
Full Full Full Full Read Only
Polarity Full Full Read Only Full Read Only Input
Alarm
Profile
Full Full Full Full Read Only
User
Label
Full Full Full Full Read Only
Polarity Full Full Read Only Full Read Only
External
State
Full Full Read Only Full Read Only
Criteria Full Full Read Only Full Read Only
Output
Event Full Full Read Only Full Read Only

Administrator Constructor Operator CraftPerson Viewer
Line Interface
LCT&RCT&NM NM
LCT&
RCT&NM
LCT&RCT LCT&RCT&NM
NMS Interfaces (Alarm
Profile)
Full Full Full Full Read Only
Signal
Mode
Full Full Read Only Full Read Only
Line RAI
Insertion
Full Full Full Full Read Only
Radio RAI
Insertion
Full Full Full Full Read Only
E1
Alarm
Profile
Full Full Full Full Read Only
Signal
Mode
Full Full Read Only Full Read Only
Line
Coding
Full Full Read Only Full Read Only
Line
Length
Full Full Read Only Full Read Only
DS1
Alarm
Profile
Full Full Full Full Read Only




07 RELEASED It 1


8BW 03598 0000 DSZZA 177/ 181


Administrator Constructor Operator CraftPerson Viewer
Line Interface
LCT&RCT&NM NM
LCT&
RCT&NM
LCT&RCT LCT&RCT&NM
Signal
Mode
Full Full Read Only Full Read Only
DS3
Alarm
Profile
Full Full Full Full Read Only
Status Full Full Full Full Read Only
Tx-FCS
Discard
Error
Frames
Full Full Read Only Full Read Only
Rx-FCS
Discard
Error
Frames
Full Full Read Only Full Read Only
DATA-
Configuration

Alarm
Profile
Full Full Full Full Read Only
Default
Rate
Full Full Read Only Full Read Only
Auto
Negotiation
Status
Full Full Read Only Full Read Only
Capability
Advertised
Full Full Read Only Full Read Only
DATA-Auto
Negotiation

Restart Full Full Read Only Full Read Only





07 RELEASED It 1


8BW 03598 0000 DSZZA 178/ 181



Administrator Constructor Operator
Craft
Person
Viewer
Performance Monitoring
LCT&
RCT
NM NM
LCT&
RCT
NM
LCT&
RCT
LCT&
RCT
NM
Threshold Tables Full Full Read Only Full Read Only
Configuration Full Full Full Full Read Only
Start
(note 1)
Full Full Full Full Not Supported
Stop
(note 1)
Full Full Full Full Not Supported
Refresh
(note 2)
Full Full Full Full Full
Reset
(note 1)
Full Full Full Full Not Supported
Collect
(note 2)
- Full Full - Full - - Full
CD
Counters
Management
Archiving - Full Full - Full - -
Not
Supported
HD Counters Management Read Only Read Only Read Only
Read
Only
Read Only
(note 1) In case of LAC not granted this feature is Not-Supported.
(note 2) Also in case of LAC not granted this feature is accessible in Full mode.




07 RELEASED It 1


8BW 03598 0000 DSZZA 179/ 181



Administrator Constructor Operator CraftPerson Viewer
Radio
LCT
RCT&
NM
NM
LCT&
RCT&NM
LCT RCT
LCT&
RCT&NM
Tx Local
Mute
Full Full Read Only Full Read Only
Tx Remote
Mute
Full Full Read Only Full Read Only Configuration
Alarm Profile Full Full Full Full Read Only
Tx Value Full Full Read Only Full Read Only
Rx Value Full Read Only Read Only Full Read Only Frequency
Shifter Full
Read
Only
Read Only Read Only Full
Read
Only
Read Only
RTPC Tx Power Full Full Read Only Full Read Only
Enabling Full Full Full Full Read Only
Range Full Full Read Only Full Read Only ATPC
Threshold Full
Full
Read Only Full Read Only
Interval Full Full Full Full Full
Sample
Time
Full Full Full Full Full
File
Management
Full Full Full Full Full
Power
Measurement
(note 1)
Start Full Full Full Full Full
(note 1) Also in case of LAC not granted this feature is accessible in Full mode.




07 RELEASED It 1


8BW 03598 0000 DSZZA 180/ 181



Administrator Constructor Operator CraftPerson Viewer
Protection Schemes
LCT&
RCT&NM
NM
LCT&
RCT&NM
LCT&
RCT
LCT&
RCT&NM
Scheme
Configuration
Full Full Read Only Full Read Only
Mux/Demux
Protection
Commands Full Full Read Only Full Read Only
Scheme
Configuration
Full Full Read Only Full Read Only
Commands Full Full Read Only Full Read Only
Static Delay-
Manual
Operation
Full Full Read Only Full Read Only
Radio
Protection
Static Delay-
Automatic
(note 1)
Full Full
Not
Supported
Full Read Only
Scheme
Configuration
Full Full Read Only Full Read Only
HST
protection
Commands Full Full Read Only Full Read Only
(note 1) In case of LAC not granted this feature is Not-Supported.





07 RELEASED It 1


8BW 03598 0000 DSZZA 181/ 181



Administrator Constructor Operator CraftPerson Viewer
Loopback
LCT
RCT&
NM
NM
LCT&
RCT&
NM
LCT RCT
LCT&
RCT&NM
IDU CABLE Full Read Only Read Only Read Only Full
Read
Only
Read Only
ODU CABLE Full Read Only Read Only Read Only Full
Read
Only
Read Only
RF Full Read Only Read Only Read Only Full
Read
Only
Read Only
E1/DS1-Tx NE
E3/DS3-Tx NE
Full Full Read Only Full Read Only
E1/DS1-Rx FE
E3/DS3-Rx FE
Full Full Read Only Full Read Only
Loopback
Config.
E1/DS1-Rx NE
E3/DS3-Rx NE
Read Only Read Only Read Only Read Only Read Only