MPR-E R2 1 SNMPSysSpec_Wind Profiled__it10

ALCATEL-LUCENT OPTICS DIVISION

WIRELESS TRANSMISSION PG

01 290212 G.Boiocchi

G. Gariani D.Spreafico

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

ED

1/61

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

3DB 18653 0000 DSZZA

It. 10 COMPANY CONFIDENTIAL

WT

01

Specific delivery for customer application

derived from

9500MPR-E 2.1

System Specification

SNMP Management Interface

COMPANY CONFIDENTIAL It.2

It. 10

2/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

INDEX

1 HISTORY ..................................................................................................................................................................... 3

2 SCOPE .......................................................................................................................................................................... 4

3 SECURITY MANAGEMENT ................................................................................................................................... 5

4 AGENT MANAGEMENT .......................................................................................................................................... 5

4.1 FUNCTIONAL DESCRIPTION ............................................................................................................................... 5 4.2 MANAGEMENT FUNCTIONS ............................................................................................................................... 5 4.3 SUPPORTED OBJECTS AND NAMING RULES ....................................................................................................... 6

5 MANAGER REGISTRATION .................................................................................................................................. 7

5.1 FUNCTIONAL DESCRIPTION ............................................................................................................................... 7 5.1.1 Automatic Manager Registration ..................................................................................................................... 7 5.1.2 Trusted Manager Registration .......................................................................................................................... 8

5.2 MANAGEMENT FUNCTIONS ............................................................................................................................... 9 5.3 SUPPORTED OBJECTS AND NAMING RULES ..................................................................................................... 10

6 RADIO ANALOGUE MEASUREMENTS ............................................................................................................. 12

6.1 FUNCTIONAL DESCRIPTION ............................................................................................................................. 12 6.2 MANAGEMENT FUNCTIONS ............................................................................................................................. 12 6.3 SUPPORTED OBJECTS AND NAMING RULES ..................................................................................................... 13

7 ETHERNET COUNTERS MONITORING ........................................................................................................... 15


8 RADIO QUALITY PERFORMANCE MONITORING (G.826) .......................................................................... 26


9 E1 INVENTORY MANAGEMENT ........................................................................................................................ 38

9.1 SUPPORTED OBJECTS AND NAMING RULES ..................................................................................................... 38

10 CROSS-CONNECTIONS INVENTORY ........................................................................................................... 39

10.1 FUNCTIONAL DESCRIPTION ............................................................................................................................. 39 10.1.1 MIB Overview for Cross-Connections management .................................................................................. 39 10.1.2 E1 Flows Cross-Connected (active E1) ..................................................................................................... 41 10.1.3 E1 Flows Cross-Connectable (spare E1) ................................................................................................... 43

10.2 SUPPORTED OBJECTS AND NAMING RULES ..................................................................................................... 46

11 ADDITIONAL PARAMETERS TO BE COLLECTED ................................................................................... 50

11.1 NE PARAMETERS ............................................................................................................................................ 50 11.2 RADIO PARAMETERS ....................................................................................................................................... 50

12 ANNEX 1: ELABORATED ETHERNET COUNTERS ................................................................................... 53

13 ANNEX 2: NAMING DESCRIPTION ................................................................................................................ 58

NTIAL

3/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA

COMPANY CONFIDENTIAL It. 10

1 HISTORY

Date Edition Comments 120410 Ed. 01 It. 2 Original document: 3DB 18379 0000 DSZZA ed. 01 It. 1

9500MPR-E 2.1 System Specification SNMP Management Interface Document profiled according to the specific WIND’ need to enable the collection of the Radio analogue measurements. The SNMP Optics-IM reference version for this release is the v4.14 Features included:

Agent management Manager registration Radio analogue measurements

300610 Ed. 01 It. 3 Addition of the following sections (To Be Completed): Ethernet Counters Monitoring Radio Quality Performance Monitoring (G.826)

060710 Ed.01 It. 4 Addition of Security, Trusted Managers and Elaborated Ethernet Counters management. Completion of the other sections.

190710 Ed.01 it. 5 Completion of the Elaborated Ethernet Counters: changed the unit of measurement (hundreds of Kbps) for TTO, added the TRCO definition. Added the Annex 2 to clarify the naming description.

191110 Ed.01 it. 6 Addition of the E1 Inventory section 301110 Ed.01 it. 7 Addition of details on E1 PM activation/de-activation and of

explanations about the objects naming rules 200111 Ed.01 it.8 Addition of Cross-Connection Inventory section. 270112 Ed.01 it.9 MIB version referred by this spec is v4.21. It is the one used by MPR 3.0.

The MIB objects referred in this spec are also supported by MPR 2.1. It is the same also for MPR 1.4 with the exception of the radioPDHTTPBidNetBandwidth object that is not supported by MPR 1.4. Changes of this iteration are pointed out by revision bars (in red): Cross-connection Inventory section: use cases not required by this customer application have been highlighted. Annex 1 section: Corrections of some editorial errors in the formulas. Annex 2 section: Additions of details about dimensioning of some MIB tables.

290212 Ed01 it.10 Addition of the “Additional Parameters to be Collected” section. Addition of the second optical user Ethernet port in section 7.3 for Ethernet Counters monitoring (supported only by MPR 3.0).


It. 10

4/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

2 SCOPE

This document provides the functional description of SNMP management interface of 9500MPR-E (Microwave Packet Radio-ETSI) Radio NE in the scope of Releases 1.4 (see exceptions highlighted in the History), 2.1 and 3.0. It is important to outline that Release 1.4 support only one type of ODU, the ODU 300, while Releases 2.1 and 3.0 support also the MPT ODU. Pay attention that different naming rules are used for the same objects when they are referred to ODU 300 and MPT (see the Naming Rules sections).

NTIAL

5/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


3 SECURITY MANAGEMENT

Community string values The Community names values to use to exchange SNMPv2c messages between manager and agent are hardcoded in the SNMP manager and agent and they are not modifiable. There are 3 different Communities, specific for each SNMP operation. The associated names are:

Write Community Name (SNMPv2 Set) : 'private' Read Community Name (SNMPv2 Get) : 'public' Trap Community Name (SNMPv2 Trap) : 'SNMP-trap'.

4 AGENT MANAGEMENT

4.1 Functional Description

The identification of the NE is provided in the tsdimNeInstallationType scalar object. The value of this object is: “9500MPR-E”. 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

The tsdimSdhNeLabel object is used to provide by managing system a label identifying the specific NE within the tsdimNeInstallationType value.

4.2 Management Functions

F- 40. Request NE Type This function allows a managing system to ask to a managed system its NE type. Scope This function permits to retrieve the NE type managed object. Service Used SNMP-GET on the tsdimNeInstallationType managed object

F- 28. Request NE Software Version This function allows a managing system to ask to a managed system its NE software version. Scope


It. 10

6/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

This function permits to retrieve the software version managed object. Service Used SNMP-GET on the sysDescr managed object

F- 44. Request NE Site Label This function allows a managing system to ask to a managed system information about the SDH NE label configuration. Scope This function permits to retrieve the SDH NE label managed object. Service Used SNMP-GET on the tsdimSdhNeLabel managed object

F- 59. Request NE Location 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

4.3 Supported Objects and Naming Rules

Scalar objects (system)

Objects

sysDescr sysLocation

Scalar objects (tsdimSnmpNEMib)

Objects

tsdimNeInstallationType tsdimSdhNeLabel

NTIAL

7/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


5 MANAGER REGISTRATION


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.

5.1.1 Automatic Manager Registration The Manager registration is performed via SNMP interface (SNMP-SET request on opticsIMMgrPollingInfoTable and tsdimEFDTable). The informations in the SNMP-SET request are based on the host’s information where the manager is located (IP-address, UDP port, depending on manager architecture, manager type). The indexes of the opticsIMMgrPollingInfoEntry and tsdimEFDEntry have to be in the range 1..10. This registration type is not stored in the persistent memory, so at NE restart the manager is in charge of a new ‘automatic registration’ (discovery NE disconnection manager side). By SNMP-GET request the manager is allowed to retrieve the associated entries on opticsIMMgrPollingInfoTable and tsdimEFDTable. The maximum number of managers registered to the NE is 10.

In the following the operational sequence that a manager has to follow in order to be registered. 1. In the creation request of opticsIMMgrPollingInfoEntry (F-7 function) the following informations are provided: Manager index (opticsIMMgrPollingIndex) in the range 1..10. Manager IP address as known at manager side (opticsIMMgrPollingIpAddress). UDP port of the local SNMP notification daemon application (opticsIMMgrPollingUdpPort). A timeout value (defined in seconds) to manage the ‘manager disconnection’ (opticsIMMgrPollingTimeOut).

The NE will declare the manager as disconnected when the this time-out plus 20 minutes will expire. Manager disconnection means that the manager is deleted both from the Polling and EFD table. Setting the opticsIMMgrPollingTimeOut to the maximum allowed value implies that the manager will remain connected for many years (of course if the NE doesn’t re-start).

Manager type (opticsIMMgrPollingManagerType) : eml (1) value for NMS system, localct (4) value for CT system. Both are valid for the present usage.

2. In the creation request of tsdimEFDEntry (tsdimEFDTable (F-1 and F-2) the following information are provided: Manager IP address as known at manager side (tsdimEFDDest) to send the notifications. UDP port of the local SNMP notification daemon application to send notifications (tsdimEFDPort). The index on the opticsIMMgrPollingInfoEntry of associated manager registered (tsdimEFDManagerIndex). For the other informations the default values are: tsdimEFDTrapId = ‘all’, tsdimEFDTrapObject = ‘all’,


It. 10

8/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

tsdimEFDLowestForwardedSeverity = ‘lowestSeverity’ (not supported), tsdimEFDIndeterminate = ‘true’. The registration in the tsdimEFDTable implies that the manager will receive all the SNMP TRAPs sent by the NE.

Option to avoid to receive unneeded TRAPs No TRAP will be sent to a manager if it is not registered in the tsdimEFDTable (even if registered in the opticsIMMgrPollingInfoTable).

5.1.2 Trusted Manager Registration The Manager registration is performed via SNMP interface (SNMP-SET request on opticsIMMgrPollingInfoTable). A trusted manager is identified by an index value included in the range 11..15. When an entry with an index value included in this range, is created by the manager, the agent as side effect will create the associated entry in the tsdimEFDTable. For the indexes in this range, the ‘polling mechanism’ is not implemented (the time-out value on opticsIMMgrPollingInfoEntry is not meaning) and the rows are stored in the persistent memory (at NE restart the rows are recreated from informations on persistent memory and not recreated by the manager). By SNMP-GET request the manager is allowed to retrieve the associated entries on opticsIMMgrPollingInfoTable and tsdimEFDTable. Up to 5 trusted managers can be registered in the NE.

In the following the operational sequence that a manager has to follow in order to be registered. In the creation request of opticsIMMgrPollingInfoEntry (F-7 function) the following information are provided: Manager index (opticsIMMgrPollingIndex) in the range 11..15. Manager IP address as known at manager side (opticsIMMgrPollingIpAddress). UDP port of the local SNMP notification daemon application (opticsIMMgrPollingUdpPort). The timeout value (opticsIMMgrPollingTimeOut) could be provided but not used by agent. The manager type (opticsIMMgrPollingManagerType) : remotect (5) value. As side effect an entry in tsdimEFDTable is created by the agent, with the following values: tsdimEFDIndex = opticsIMMgrPollingIndex tsdimEFDDest = opticsIMMgrPollingIpAddress tsdimEFDPort = opticsIMMgrPollingUdpPort tsdimEFDManagerIndex = opticsIMMgrPollingIndex tsdimEFDTrapId = ‘all’, tsdimEFDTrapObject = ‘all’, tsdimEFDLowestForwardedSeverity = ‘lowestSeverity’ (not supported), tsdimEFDIndeterminate = ‘true’.

NTIAL

9/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


The registration in the tsdimEFDTable implies that the manager will receive all the SNMP TRAPs sent by the NE. In addition, the agent will send to the trusted managers also the linkUp and linkDown (MIB-2) SNMP-TRAPs (they are not send to the managers registered in automatic way).


F- 7. Create Manager Polling Information This function allows a managing system to define its polling information Scope This function permits to create an object containing the information needed to manage the manager polling functionality. Service Used SNMP-SET on the following opticsIMMgrPollingInfoTable columnar object: - opticsIMMgrPollingIpAddress - opticsIMMgrPollingUdpPort - opticsIMMgrPollingTimeOut - opticsIMMgrPollingManagerType SNMP-SET on RowStatus columnar object to "createAndGo" value.

F- 8. Delete Manager Polling Information 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 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- 1. Create Event Report 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)


It. 10

10/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

- tsdimEFDPort (the UDP port of the managing system) - tsdimEFDTrapId - tsdimEFDTrapObject - tsdimEFDLowestForwardedSeverity - tsdimEFDIndeterminate - tsdimEFDManagerIndex SNMP-SET on RowStatus columnar object to "createAndWait" value. Note F-1 : tsdimEFDLowestForwardedSeverity object is not supported.

F- 3. Delete Event Report 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 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.


The SNMP tables (with the associated columnar objects) and the scalar objects to be supported are provided in the following tables. For each SNMP table the indexes values of all the supported entries are provided too.

opticsIMMgrPollingInfoTable (opticsIMCommRouMib)

Description Indexes Value

Creation rules

Automatic manager registration 1..10 By manager Trusted manager registration 11..15 By manager

NTIAL

11/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Supported Objects

Objects

opticsIMMgrPollingInfoTable opticsIMMgrPollingIpAddress opticsIMMgrPollingUdpPort opticsIMMgrPollingTimeOut opticsIMMgrPollingManagerType opticsIMMgrPollingRowStatus

tsdimEFDTable (tsdimSupportMib)


Creation rules

Automatic manager registration 1..10 By manager Trusted manager registration 11..15 By agent as side effect of the creation of

the associated opticsIMMgrPollingInfoEntry (with same index)

Supported Objects

Objects

tsdimEFDTable tsdimEFDDest tsdimEFDTrapId tsdimEFDTrapObject tsdimEFDPort tsdimEFDIndeterminate tsdimEFDOperStatus tsdimEFDRowStatus tsdimEFDManagerIndex


It. 10

12/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

6 RADIO ANALOGUE MEASUREMENTS


For each radio hop (radio channel) the following analogue measurements are supported:

Tx power (local and remote): it represents the power level at the transmitter output and it is an integer with associated measure unit expressed in decade of dBm;

Rx power (local and remote): it represents the power level at the receiver input and it is a negative integer with associated measure unit expressed in decade of dBm.

The time stamp of the reported measure must be performed by the manager.

Power values provided in case of anomalous conditions: In case of problem on the radio link, remote powers cannot be available locally, then the

value shall be -99.6 dBm. In case of failure on reading the register containing the power the value shall be -99.7 dBm. In case of communication problems inside the NE between MSS and ODU 300/MPT (i.e.

InternalCommunicationProblem, Cable Loss alarms) the value shall be -99.8 dBm. In case of mute status for the transmitter the value shall be -100 dBm (in 1+1 HSB radio

configuration 1 of the two transmitter is always in mute status). If the power level read is out of the allowed range, the value shall be -101 dBm. In case of alarms on the remote NE on one of the two radio channels in HSB configuration

(typically ICP, Cable Loss, Card Missing, Card Fail), the value shall be -127 dBm.


F- 1.40 Request Radio Channel Number 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 This management function allows the managing system to request the measurements of the local transmitted and received power levels. Scope

NTIAL

13/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


OPTICSIM-RADIO-TRS-COMMON-MIB: opticsIMRadioAnalogueMeasuresTable Service Used SNMP-GET on: - analogueMeasuresLocalTxPower - analogueMeasuresLocalRxMainPower

F- 1.42 Request Remote Analogue Measurements 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



opticsIMRadioAnalogueMeasuresTable (opticsIMRadioTrsCommonMib)

Radio Direction Configuration


1+0 ODU300 Radio port – Dir#x Ch#1

50x11 (x=3..8)

All the 1+1

ODU300 Radio port – Dir#x Ch#1

50x11 (x = 3,5,7)

Radio port – Dir#x Ch#0

50x01

ifIndex = 50xCP where:

X = Radio Direction = Slot number where the MD300 board is provisioned, it is the the Main board (from EPS protection point of view) in case of 1+1 radio configurations

C = Channel number (1 for Channel#1 or Main channel, 0 for Channel#0 or spare channel) P = Port number (always 1)

Releases : Rel.1.x, Rel.2.1


It. 10

14/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA



1+0 MPT Radio port – Dir#x.p Ch#1

(x=3..8 and p=1..4)

All the 1+1

MPT Radio port – Dir#x.p Ch#1

5xp1xp (x=y=3..8 p=1..3 q=2..4 P<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)

Radio port – Dir#x.p Ch#0

5xp0yq

ifIndex = 5XPCXP in case of 1+0 configuration and Main channel in 1+1 configurations ifIndex = 5XPCYQ in case Spare channel in 1+1 configurations Second and third digits (XP)always identify the Radio direction Fourth and fifth digits (XP) identify the Radio channel in 1+0 configuration, the Main one in 1+1 configurations Fourth and fifth digits (YQ) identify the Spare channel in 1+1 configurations Where:

X = Slot number of the MPT ACCESS board where the MPT is connected to (the Main one in case of 1+1 radio configurations)

P = Port number on the MPT ACCESS board where the MPT is connected to (the Main one in case of 1+1 radio configurations)

C = Channel number (1 for Channel#1 or Main channel, 0 for Channel#0 or spare channel) y = Slot number of the MPT ACCESS board where the Spare MPT is connected to (only in 1+1

radio configurations) Q = Port number on the MPT ACCESS board where the Spare MPT is connected to (only in

1+1 radio configurations) Releases : Rel.2.1

Supported Objects

Objects

opticsIMRadioAnalogueMeasuresTable analogueMeasuresRadioChannelNumber analogueMeasuresLocalTxPower analogueMeasuresLocalRxMainPower analogueMeasuresRemoteTxPower analogueMeasuresRemoteRxMainPower

NTIAL

15/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


7 ETHERNET COUNTERS MONITORING


For User Ethernet interfaces, the following Ethernet counters are supported:

RxTRCO (incoming, Rx) RxTRCF (incoming, Rx) RxTRSEF (incoming, Rx) RxTDF (incoming, Rx) RxTRCFUnicast (incoming, Rx) RxTRCFMulticast (incoming, Rx) RxTRCFBroadcast (incoming, Rx) TxTTO (outgoing, Tx) TxTTF (outgoing, Tx) TxTDF (outgoing, Tx) TxTRCFUnicast (outgoing, Tx) TxTRCFMulticast (outgoing, Tx) TxTRCFBroadcast (outgoing, Tx)

These counters take the form of free running counters that start from zero and increment up to a maximum integer value. All of these counters are 32-bit length counters, with the exception of the counters expressed in terms of number of bytes (octets) that are 64-bit length counters (TRCO, TTO).

For the Radio interfaces, the following Ethernet counters are supported:

1. at queue level, for each of the 5 queues devoted to manage Ethernet flows of each radio port: TCO (outgoing, Tx) TCF (outgoing, Tx) DiscardTCF (outgoing, Tx)

2. at aggregate port level TxTTO (outgoing, Tx)

It shall be the sum of the TCO values of all the Ethernet queues (queues from 1 to 5). TxTTF (outgoing, Tx)

It shall be the sum of the TCF values of all the Ethernet queues (queues from 1 to 5). TxTDF (outgoing, Tx) )

It shall be the sum of the DiscardTCF values of all the Ethernet queues (queues from 1 to 5).

Also these counters take the form of free running counters. All the frame counters are 32-bit length while the byte counters (TCO, TTO) are 64-bit length.

The definition of these counters is the following:

RxTRCO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including Ethernet header characters. It is related to the standard (rfc2233) contribution:


It. 10

16/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

o ifHCInOctects. RxTRCF:total number of Ethernet frames received by the Virtual Ethernet Interface.

It is related to the standard (rfc1493) contribution: o dot1dTpPortInFrames.

RxTRSEF: total number of errored frames. It is the sum of the following contributions: o dot3StatsAlignmentErrors (rfc2665):

a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check;

o dot3StatsFCSErrors (rfc2665): a count of frames received on a particular interface that are an integral number of octets in length, but do not pass the FCS check;

o dot3StatsFrameTooLongs (rfc2665): number of received Ethernet frames that exceed the MTU

o etherStatsFragments (rfc1757): o etherStatsUndersizePkts (rfc1757):

RxTDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.

It is related to the standard (rfc1213) contribution: o ifInDiscards.

RxTRCFUnicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet Interface.

It is related to the standard (rfc1213) contribution: o ifInUcastPkts.

RxTRCFMulticast: total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.

It is related to the standard (rfc2233) contribution: o ifHCInMulticastPkts.

RxTRCFBroadcast: total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.

It is related to the standard (rfc2233) contribution: o ifHCInBroadcastPkts.

TxTTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet header characters.

It is related to the standard (rfc2233) contribution: o ifHCOutOctects.

TxTTF: total number of Ethernet frames transmitted out by the interface. It is related to the standard (rfc1493) contribution:

o dot1dTpPortOutFrames. TxTDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer congestion.

It is related to the standard (rfc1213) contribution: o ifOutDiscards.

TxTRCFUnicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet Interface.

It is related to the standard (rfc2233) contribution: o ifHCOutUcastPkts.

TxTRCFMulticast: total number of good packets transmitted by this address that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.

It is related to the standard (rfc2233) contribution:

NTIAL

17/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


o ifHCOutMulticastPkts. TxTRCFBroadcast: total number of good packets transmitted by this address that were directed to the broadcast address.

It is related to the standard (rfc2233) contribution: o ifHCOutBroadcastPkts.

TCF: total number of Ethernet conforming frames accepted and transmitted out by the specific queue of the interface. DiscardTCF: total number of Discarded Ethernet conforming frames accepted by the specific queue of the interface. TCO: total number of Ethernet conforming octects accepted and transmitted out by the specific queue of the interface.

To read the Ethernet counters for the User Ethernet interfaces the related entries of the following tables must be read:

ethAggrMaintRxTable ethAggrMaintTxTable

For the Radio directions only the Tx counters are supported, then just the the entries of the ethAggrMaintTxTable must be read. To read the Ethernet counters for the Ethernet queues of each Radio direction the following table must be read:

ethAggrPerQueueMaintTable.

The entries of all these tables are created by the agent as consequence of the enabling of user Ethernet interface or as consequence of radio equipment provisioning phase. The managing systems can only retrieve the values of the Ethernet counters for each monitoring point. In case the agent cannot provide, for any reson, the counters values for the monitoring point requested by the managing system (GET-SNMP Request), the agent shall return in the GET-SNMP Response an error-status = ‘unavailableResource’ and an error-index=OID of the first counter not readeable’.

In the ethAggrPerQueueMaintTable, for each radio direction, each queue is identified (ethAggrPerQueueIndex) according to the associated traffic priority (see Supported Objects and Naming Rules section):

ethAggrPerQueueIndex = 1 for the traffic with lower priority. ethAggrPerQueueIndex = 5 for the traffic with higher priority.

No elaboration is provided by the NE on the Ethernet counters: they are read from the HW and provided to the managing system as they are. So the ‘delta’ between the counters value read in two different time must be provided by the manging system (while in case of Radio Quality PM (G.826)) it is provided by the NE itself according the the granularity period supported (see the related section)) . A roll-over of the physical counters must be managed by the managing system, hiding it to the operator.

In case of 1+1 radio configurations, two monitoring points are supported, one for each radio channel. For an operator point of view what is significant, in this case, is to know the values of the ethernet counters related to the active radio channel (active from EPS protection point of view).


It. 10

18/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

So to provide this, the managing system has to read the ethernet counters on both the radio channels and consider just the one related to the active one. It is necessary to read the counters also on the stand-by radio channel in order to use them as reference to count the ‘delta’ for the subsequent reading (if this channel becomes active, of course). To know which is the active radio channel (and then the stand-by one) for the EPS protection, the opticsIMEquipmentProtectionUnitSwitchStatus must be read. It is a columnar object of the opticsIMEquipmentProtectionUnitTable.


F-1.1 Request Incoming Aggregate This management function permits to request Incoming Aggregate maintenance counters and attributes:

TRCO TRCF TRCF_Unicast TRCF_Multicast TRCF_Broadcast TRSEF TDF RetrieveTime LastDiscontinuityTimeStamp

Scope OPTICSIM-ETHPM-MIB: ethAggrMaintRxTable Service Used SNMP-GET on - ethAggrMaintRxTRCO - ethAggrMaintRxTRCF - ethAggrMaintRxTRCFUnicast - ethAggrMaintRxTRCFMulticast - ethAggrMaintRxTRCFBroadcast - ethAggrMaintRxTRSEF - ethAggrMaintRxTDF - ethAggrMaintRxRetrievingTime - ethAggrMaintRxLastDiscontinuityTimeStamp Note F-1.1 : the RetrieveTime object is supported just in Rel. 2.1, it provides the NE time associated to the counters values read. The LastDiscontinuityTimeStamp attribute is never supported.

F-1.3 Request Outgoing Aggregate This management function permits to request Outgoing Aggregate maintenance counters and attributes:

NTIAL

19/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


TTO TTF TTF_Unicast TTF_Multicast TTF_Broadcast TDF RetrieveTime LastDiscontinuityTimeStamp

Scope OPTICSIM-ETHPM-MIB: ethAggrMaintTxTable Service Used SNMP-GET on - ethAggrMaintTxTTO - ethAggrMaintTxTTF - ethAggrMaintTxTTFUnicast - ethAggrMaintTxTTFMulticast - ethAggrMaintTxTTFBroadcast - ethAggrMaintTxTDF - ethAggrMaintTxRetrievingTime - ethAggrMaintTxLastDiscontinuityTimeStamp Note F-1.3: : the RetrieveTime object is supported just in Rel. 2.1, it provides the NE time associated to the counters values read. The LastDiscontinuityTimeStamp attribute is never supported.

F-3.16 Request Equipment Protection Status 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:

opticsIMEquipmentProtectionUnitSwitchStatus


It. 10

20/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA



ethAggrMaintRxTable (opticsIMEthPmMib)

Configuration Description Indexes Value

Creation rules

Electrical Ethernet User ports

7010x (x=1..4)

Optical Ethernet User port

70105

All

Second Optical Ethernet User port (available only in MPR 3.0)

70106

By agent as consequence of enabling of User Ethernet port.

The naming rule for entries of this table is the following: fIndex = 70SXX, where: S = Slot number of the Core board (the Main Core in case of protection)

XX = Port number

Supported Objects

Objects

ethAggrMaintRxTable ethAggrMaintRxTRCO ethAggrMaintRxTRCF ethAggrMaintRxTRSEF ethAggrMaintRxTDF ethAggrMaintRxRetrievingTime ethAggrMaintRxTRCFUnicast ethAggrMaintRxTRCFMulticast ethAggrMaintRxTRCFBroadcast

NTIAL

21/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


ethAggrMaintTxTable (opticsIMEthPmMib)


Creation rules

Electrical Ethernet User ports

7010x (x=1..4)

Optical Ethernet User port 70105

All

Second Opt. Ethernet User port (available only in MPR 3.0)

70106

By agent as consequence of enabling of Ethernet User port.

ODU300 50x11 (x=3..8)

By agent as consequence of radio equipment provisioning

1+0 radio conf.

MPT 5xp1xp (x=1, and p=5)

or (x=3..8, and p=1..4)


ODU300 50x11 50x01 (x=3,5,7)


1+1 radio conf.

RADIO PORT (TX

DIRECTION)

MPT 5xp1xp 5xp0yq (x=y=3..8, p=1..3 q=2..4 p<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)


The naming rule for entries of this table depends on the type of port. In case of Ethernet user ports: ifIndex = 70SXX, see ethAggrMaintRxTable naming rule. In case of Radio ports see Analog Measurements section.


It. 10

22/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Supported Objects

Objects

ethAggrMaintTxTable ethAggrMaintTxTTO ethAggrMaintTxTTF ethAggrMaintTxTDF ethAggrMaintTxRetrievingTime ethAggrMaintTxTTFUnicast (note 1) ethAggrMaintTxTTFMulticast (note 1) ethAggrMaintTxTTFBroadcast (note 1)

(note 1) not supported in case of radio direction interface.

NTIAL

23/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


ethAggrPerQueueMaintTable (opticsIMEthPmMib)


Creation rules

ODU300 50x11;n (x=3..8) (n=1..5)


1+0 radio conf.

MPT 5xp1xp;n (x=1 and p=5)

or (x=3..8 and p=1..4) (n=1..5)


ODU300 50x11;n 50x01;n (x=3,5,7) (n=1..5)


1+1 radio conf

Queue #n on Radio port

(n=1 for lower priority queue

up to n=5 for higher priority queue)

MPT 5xp1xp;n 5xp0yq;n (x=y=3..8, P=1..3 Q=2..4 P<q)

Or X=3,5,7 Y=x+1 P=1..4) Q=1..4) (n=1..5)


First index = ifIndex, see naming rule of Radio ports in Analog Measurements section. Second index = Ethernetv queue number.


It. 10

24/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Supported Objects

Objects

ethAggrPerQueueMaintTable ethAggrPerQueueIndex (index) ethAggrPerQueueMaintTCF ethAggrPerQueueMaintDiscardTCF ethAggrPerQueueMaintTCO ethAggrPerQueueMaintRetrievingTime

NTIAL

25/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


opticsIMEquipmentProtectionUnitTable (opticsIMEqptMib)


All the 1+1 Radio configurations with ODU300

Radio Interface Dir#x–Main Radio Interface Dir#x–Spare (x=3,5,7)

x2; x1 x2; y0 (x=3,5,7) (y=x+1) (note 2)

All the 1+1 Radio configurations with MPT

Radio Interface Dir#x.p–Main Radio Interface Dir#x.p–Spare

xp2; xp1 xp2; yq0 (x=y=3..8, p=1..3, q=2..4, q>p) or (x=3,5,7, y=x+1, p=1..4, q=1..4) note 2)

(note 2) EPU naming rule: [S2, SR] for ODU 300; [SP2, SMR] for MPT

S = Slot number of the associated board R = Role of the EPU: Main =1, Spare = 0 P = port number where the main board is attached (used only for Radio interface MPT-MS) M= port number where the spare board is attached (used only for Radio interface MPT-MS)

The x and y values reported in the table are related to the slot positions of the boards involved in the EPS protection schemes.

Supported Objects

Objects opticsIMEquipmentProtectionUnitTable opticsIMEquipmentProtectionUnitSwitchStatus


It. 10

26/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

8 RADIO QUALITY PERFORMANCE MONITORING (G.826)


Performance monitoring of radio hop and link sections are supported in the addressed releases, both with ODU 300 and MPTs ODU (OutDoor Unit). MPTs are managed only in 9500 MPR-E 2.1. The radio hop section quality monitoring is supported both in 1+0 and 1+1 radio configuration The radio link section quality monitoring is supported only in case of 1+1 radio configuration and when the Radio Protection Switching (RPS) is supported (in all the other cradio onfigurations hop and link sections provide the same quality), the related monitoring point follows the position of the EPS Rx switch. To resume:

1+0: 1 radio hop monitoring point 1+1: 1 radio link monitoring point, 2 radio hop monitoring points (one for each radio

channel). Both these types of PM support the same performance events (counters):

Errored Seconds Severly Errored Seconds Background Block Error Unavailable Seconds

These performance events are counted over fixed periods (named current data) and then, at the end of these periods, they are stored in registers (named history data) inside the NE. The following periods (named granularity periods) are supported:

15min registers that accumulate performance events over a fixed 15 minute period 24h registers that accumulate performance events over a fixed 24 hour period

Performance events are counted only if the monitoring for a given granularity period has been activated by a managing system. Activation/de-activation must be addressed independently to each monitoring point and granularity period. The starting time for the 15 minutes PM counters can be only the 0, 15, 30 and 45 minute of an hour. The starting time for the 24h PM counters can be only the midnight of a day. If the PM process is started in a time different from the allowed ones, the counting process is started, but the first period is marked with the suspect interval flag.

For this specific customer application, to support the Radio Hop PM the following table must be managed:

opticsIMPdhFrameHopCurrentDataTable (just for activatation/de-activation purpose) opticsIMPdhFrameHopHistoryDataTable

For this specific customer application, to support the Radio Link PM the following table must be managed:

opticsIMPdhFrameLinkCurrentDataTable (just for activatation/de-activation purpose)

NTIAL

27/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


opticsIMPdhFrameLinkHistoryDataTable

Current Data tables are used to store data related to 15 minutes and 24 h granularity periods. Each entry in these tables is identified by 2 indexes (see Suppported Objects and Naming rules section for details):

ifIndex: to identify the monitored resource (which radio hop or which radio link) pmPdhFrameHopCDIndex: to identify the granularity period (15 min or 24 h).

The status of each Current Data entry (activated/de-activated) is stored in permanent memory. The activation is obtained setting the RowStatus columnar object to the "active" value, the de-activation setting the RowStatus columnar object to the "notInService" value. In case of de-activation of a Current Data, all the related History Data are automatically deleted by the agent. In each current data entry, the xxxxNumSuppressedIntervals object provides the number of consecutive history data suppressed (if any) immediately before the current period.

History Data tables are used to store history data related to both 15 minutes and 24 h granularity periods. Each entry in these tables is identified by 3 indexes (see Suppported Objects and Naming rules section for details):

ifIndex: to identify the monitored resource (which radio hop or which radio link) pmPdhFrameHopCDIndex: to identify the granularity period (15 min or 24 h) pmPdhFrameHopHDPeriodEndTime: to identify the specific monitored period (96 periods are

stored in case of 15 minutes, 8 in case of 24h). History data are stored in volatile memory and then each time the NE restart, the History Data are lost. History data are also lost if the monitoring is de-activated. In case of all-zeroes counters (value of all the counters = 0), 15 minutes intervals are always suppressed (not stored in the history data table). Instead, the all-zeroes 24 hours intervals are never suppressed. In each history data entry, the xxxxNumSuppressedIntervals provides the number of consecutive history data suppressed immediately before the current history data. Then, if the entry related to a given interval is not stored (for 15 minutes) means that all the counters had zero value (no error).


Current Data Management All the functions below apply both to opticsIMPdhFrameHopCurrentDataTable and to opticsIMPdhFrameLinkCurrentDataTable.

F- 4.2 Activate CD Entry This management function permits to activate one CD entry.


It. 10

28/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>CurrentDataTable Service Used SNMP-SET on pm<Layer>CDRowStatus columnar object to "active" value

F- 4.14 Deactivate CD Entry This management function permits to deactivate one CD entry to stop the counters. Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>CurrentDataTable Service Used SNMP-SET on pm<Layer>CDRowStatus columnar object to "notInService" value

F- 4.8 Request Number of Suppressed Intervals This management function permits to request the Number of Suppressed Intervals. Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>CurrentDataTable Service Used SNMP-GET on pm<Layer>CDNumSuppressedIntervals

History Data Management All the functions below apply both to opticsIMPdhFrameHopHistoryDataTable and to opticsIMPdhFrameLinkHistoryDataTable.

F- 5.1 Request Elapsed Time This management function permits to request the elapsed time in the current interval. Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable Service Used SNMP-GET on pm<Layer>HDElapsedTime

F- 5.2 Request Granularity Period This management function permits to request the granularity period (15 min or 24 h). Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable Service Used SNMP-GET on pm<Layer>HDGranularityPeriod

F- 5.4 Request Number of Suppressed Intervals

NTIAL

29/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


This management function permits to request the Number of Suppressed Intervals. Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable Service Used SNMP-GET on pm<Layer>HDNumSuppressedIntervals

F- 5.5 Request Suspect Interval Flag This management function permits to request whether the History data is suspect or not. Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable Service Used SNMP-GET on pm<Layer>HDSuspectIntervalFlag

F- 5.7 Request PM Data Collection This management function permits to request PM Data Collection. The following counters can be retrieved: BBE ES SES UAS Scope OPTICSIM-PDH-PM-MIB: opticsIM<Layer>HistoryDataTable Service Used SNMP-GET on: - pm<Layer>HDBbe - pm<Layer>HDEs - pm<Layer>HDSes - pm<Layer>HDUas


It. 10

30/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA



opticsIMPdhFrameHopCurrentDataTable (opticsIMPdhPmMib)

Radio Configuration

Description Indexes Value Creation rules

1+0 15 min. – Dir#x Ch#1

ODU300 50x11;1 (x=3..8)

By agent as consequence of equipment provisioning

15 min. – Dir#x Ch#1

50x11;1 All the 1+1


ODU300

50x01;1

(x=3,5,7) By agent as consequence of equipment provisioning

1+0 24 h – Dir#x Ch#1

ODU300 50x11;2 (x=3..8)


24 h. – Dir#x Ch#1

50x11;2 All the 1+1

24 h – Dir#x Ch#0

ODU300

50x0y;2

(x=3,5,7) By agent as consequence of equipment provisioning

First index: ifIndex = see the naming rules defined in the Analogue Measurements section Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h

NTIAL

31/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Radio Configuration


1+0 15 min. – Dir#x Ch#1

MPT 5xp1xp;1 (x=1 and p=5)

or (x=3..8 and p=1..4)



5xp1xp;1 All the 1+1


MPT

5xp0yq;1

(x=y=3..8 p=1..3 q=2..4 p<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)


1+0 24 h – Dir#x Ch#1

MPT 5xp1xp;2 (x=1 and p=5)

or (x=3..8 and p=1..4)


24 h. – Dir#x Ch#1

5xp1xp;2 All the 1+1

24 h – Dir#x Ch#0

MPT

5xp0yq;2

x=y=3..8 p=1..3 q=2..4 p<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h

Supported Objects

Objects

opticsIMPdhFrameHopCurrentDataTable pmPdhFrameHopCDRowStatus pmPdhFrameHopCDNumSuppressedIntervals


It. 10

32/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

opticsIMPdhFrameHopHistoryDataTable (opticsIMPdhPmMib)

Radio Configuration


1+0 15 min. – Dir#x Ch#1

ODU300 50x11;1;period k (x=3..8, k=1..96)


50x11;1; period k

All the 1+1


ODU300

50x01;1; period k

(x=3,5,7 k=1..96)

1+0 24 h – Dir#x Ch#1

ODU300 50x11;2;period k (x=3..8, k=1..8)

24 h. – Dir#x Ch#1

50x11;2; period k

All the 1+1

24 h – Dir#x Ch#0

ODU300

50x01;2; period k

(x=3,5,7, k=1..8)

By agent when the related period of CDs is terminated

First index: ifIndex = see the naming rules defined in the Analogue Measurements section Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h Third index: period end time

NTIAL

33/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Radio Configuration


1+0 15 min. – Dir#x Ch#1

MPT 5xp1xp;1;period k (x=1 and p=5)

or (x=3..8 and p=1..4) (k=1..96)


5xp1xp;1; period k

All the 1+1


MPT

5xp0yq;1; period k

x=y=3..8 p=1..3 q=2..4 p<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4) (k=1..96)

1+0 24 h – Dir#x Ch#1

MPT 5xp1xp;2;period k (x=1 and p=5)

or (x=3..8 and p=1..4) k=1..8)

24 h. – Dir#x Ch#1

5xp1xp;2; period k

All the 1+1

24 h – Dir#x Ch#0

MPT

5xp0yq;2; period k

x=y=3..8 p=1..3 q=2..4 p<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4) k=1..8)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h Third index: period end time


It. 10

34/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Supported Objects

Objects

opticsIMPdhFrameHopHistoryDataTable pmPdhFrameHopHDElapsedTime pmPdhFrameHopHDGranularityPeriod pmPdhFrameHopHDNumSuppressedIntervals pmPdhFrameHopHDSuspectIntervalFlag pmPdhFrameHopHDSes pmPdhFrameHopHDUas pmPdhFrameHopHDBbe pmPdhFrameHopHDEs

opticsIMPdhFrameLinkCurrentDataTable (opticsIMPdhPmMib)

Radio Configuration Description Indexes Value Creation rules

15 min. – Dir#x Ch#Common

50x91;1;

All the 1+1

24 h – Dir#x Ch#Common

ODU300

50x91;2;

(x=3,5,7)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section, C=9 identifies the RPS active channel Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h

NTIAL

35/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA




5xp9xp;1;

All the 1+1


MPT

5xp9xp;2;

(x=y=3..8 p=1..3 q=2..4)

or (x=3,5,7 y=x-1 p=1..4 q=1..4)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section, C=9 identifies the RPS active channel Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h Supported Objects

Objects

opticsIMPdhFrameLinkCurrentDataTable pmPdhFrameLinkCDRowStatus pmPdhFrameLinkCDNumSuppressedIntervals

opticsIMPdhFrameLinkHistoryDataTable (opticsIMPdhPmMib)



50x91; 1; period k (k=1..96)

All the 1+1


ODU300

50x91; 2; period k (k=1..8)

(x=3,5,7)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section, C=9 identifies the RPS active channel, Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h Third index: period end time


It. 10

36/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA



5xp9xp; 1; period k (k=1..96)

All the 1+1


MPT-MS

5xp9xp; 2; period k (k=1..8)

(x=3..8 p=1..3)

or (x=3,5,7 p=1..4)


First index: ifIndex = see the naming rules defined in the Analogue Measurements section, C=9 identifies the RPS active channel Second index: granularity period = 1 in case of 15 min, 2 in case of 24 h Third index: period end time

NTIAL

37/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Supported Objects

Objects

opticsIMPdhFrameLinkHistoryDataTable pmPdhFrameLinkHDElapsedTime pmPdhFrameLinkHDGranularityPeriod pmPdhFrameLinkHDNumSuppressedIntervals pmPdhFrameLinkHDSuspectIntervalFlag pmPdhFrameLinkHDSes pmPdhFrameLinkHDUas pmPdhFrameLinkHDBbe pmPdhFrameLinkHDEs


It. 10

38/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

9 E1 INVENTORY MANAGEMENT

In order to know which are the E1 ports enabled, the e1pPITTPSignalMode object in opticsIME1pPITTPTable must be read. The rule to apply is the following:

Unframed => port enabled

Framed => port enabled

Disabled => port disabled


The SNMP table (with the associated columnar objects) and the scalar objects to be supported is provided in the following table. The indexes value of all the supported entries is provided too.

opticsIME1pPITTPTable (opticsIMTrsCommonMib)


Creation rules

E1 Incoming ports

60xyy (x = 3..8 yy = 01..32)

32 entries for each ‘P32E1DS1’ board

The naming rule for entries of this table is the following: 60xyy, where:

x = Slot number of the P32E1DS1 board (the Main board in case of EPS protection) yy = Port number

Supported Objects

Objects opticsIME1pPITTPTable e1pPITTPSignalMode

NTIAL

39/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


10 CROSS-CONNECTIONS INVENTORY


10.1.1 MIB Overview for Cross-Connections management

From a MIB point of view, cross-connections are performed by means of 3 different tables:

opticsIMETSInFlowTable

opticsIMETSOutFlowTable

opticsIMETSCrossConnectTable

Entries in opticsIMETSInFlowTable and opticsIMETSOutFlowTable identify the two physical interfaces (E1 port, Radio direction, Ethernet port) involved in the cross-connections. While entries in opticsIMETSCrossConnectTable establish the relationship between the associated opticsIMETSInFlowTable and opticsIMETSOutFlowTable .

Here after the relationship between these tables is shown.


It. 10

40/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

ETSInFlowTable

ETSInFlowServiceID ETSInFlowRowStatus ETSInFlowCrossConnectIdentifier

ETSInFlowIndex

ETSOutFlowTable

ETSOutFlowServerID ETSOutFlowRowStatus ETSOutFlowCrossConnectIdentifier

ETSOutFlowIndex

ETSCrossConnectRowStatus

ETSCrossConnectIndex ETSCrossConnectInFlowIndex ETSCrossConnectOutFlowIndex

ETSCrossConnectTable

Other MIB tables are necessary to properly perform the inventory of cross-connections. When needed, they will be indicated in the next sections.

NTIAL

41/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


10.1.2 E1 Flows Cross-Connected (active E1)

Used Radio Bandwidth

The bandwidth already used to transport the E1 flows already cross-connected on a given radio direction, can be computed by a managing system knowing two values.

The first is the bandwidth globally available for the Cross-connection of E1 flows (net bandwidth), that is a consequence of the configured Modem Profile. The second is the bandwidth not yet used and then available for new cross-connections. Of course they are the same before of provisioning of any cross-connection on the addressed interface.

The bandwidth used to transport the E1 flows already cross-connected is the difference between these two values.

The bandwidth globally available for Cross-connection of E1 flows is available in the MIB in the radioPDHTTPBidNetBandwidth columnar object (radioPDHTTPBidTable). The bandwidth not yet used and then available for new new cross-connections is available in the radioPDHTTPBidAvailableBandwidth columnar object (radioPDHTTPBidTable).

Radio directions - Number of active E1

In order to compute the number of E1 flows already cross-connected towards a given interface (a radio direction) identified by its ifIndex value (e.g. 50311), the following procedure should be followed:

Get of all the entries in opticsIMETSInFlowTable. If present, the entry with index=1500 mustn’t be taken into account (it is not related to a cross-connected flow).

Get of all the entries in opticsIMETSOutFlowTable.

The number of E1 flows cross-connected on that interface is provided by the sum of:

o The number of opticsIMETSInFlowEntry having the opticsIMETSInFlowServiceID object equal to the ifIndex of the addressed interface (e.g. 50311) and having the opticsIMETSInFlowCrossConnectIdentifier with a value different from zero.

o The number of opticsIMETSOutFlowEntry having the opticsIMETSOutFlowServerID object equal to the ifIndex of the addressed interface (e.g. 50311) and having the opticsIMETSOutFlowCrossConnectIdentifier with a value different from zero.

Used Ethernet Bandwidth – NOT REQUIRED


It. 10

42/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

The bandwidth used to transport the E1 flows already cross-connected on a given Ethernet port, can be computed by a managing system knowing two values.

The first is the bandwidth globally available for the Cross-connection of E1 flows. The second is the bandwidth not yet used and then available for new cross-connections. Of course they are the same before of provisioning of any cross-connection on the addressed interface.

The bandwidth used to transport the E1 flows already cross-connected is the difference between these two values. The bandwidth globally available for Cross-connection of E1 flows is available in the MIB in the ifMauType columnar object (ifMauTable). This object contains either the result of the auto-negotiation process (the OID of the object under dot3MauType OID related to the autonegotiation result) or the value of the object ifMauDefaultType in case the auto-negotiation is not enabled. The bandwidth not yet used and then available for new cross-connections is available in the opticsIMEthAvailableBandwidth columnar object (opticsIMEthConfTable).

E1 boards - Number of active E1 – NOT REQUIRED

In order to compute the number of E1 ports belonging to a given P32E1DS1 board, that have been already cross-connected, the following procedure should be followed:

Get of all the entries in opticsIMETSInFlowTable. If present, the entry with index=1500 mustn’t be taken into account (it is not related to a cross-connected flow).

The number of E1 flows belonging to the board that has been already cross-connected is provided by:

o the number of opticsIMETSInFlowEntry having the opticsIMETSInFlowServiceID object set to one of the ifIndex of the ports of the addressed P32E1DS1 board (e.g. 603xx, where xx=01..32), and having the opticsIMETSInFlowCrossConnectIdentifier with a value different from zero.

NTIAL

43/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


10.1.3 E1 Flows Cross-Connectable (spare E1)

Radio directions in Static Modulation or in Adpative Modulation with CAC enabled - number of spare E1

The number of E1 flows that can be cross-connected over a given radio direction, can be computed by a managing system knowing the bandwidth not yet used, then available for new new cross-connections, and the bandwidth used by an E1 service flow (TDM2TDM or TDM2ETH) when it is cross-connected over a radio direction.

The bandwidth used by a TDM2TDM and by a TDM2ETH service flow are different. Then, for a given available bandwidth, the number of E1 managed as a TDM2TDM service and the number of E1 managed as a TDM2ETH service can be different.

The number of spare TDM2TDM service flow can be obtained taking the integer part of the result of the division between the bandwidth not yet used (available bandwidth) and the bandwidth used by an TDM2TDM service flow.

The same in case of TDM2ETH service, of course the bandwidth used by a TDM2ETH service flow must be used. As defined above, the bandwidth not yet used and then available for new new cross-connections is present in the radioPDHTTPBidAvailableBandwidth columnar object (radioPDHTTPBidTable). The bandwidth used by a TDM2TDM service flow is different according to the type of ODU used:

in case of radio directions equipped with MD300 and ODU 300 is equal to 2,2852 Mbit/s in case of radio directions equipped with MPT-ACC and MPT-HC or MC is equal to 2,1667

Mbit/s The bandwidth used by a TDM2ETH service flow is different according to the type of ODU used and to the presence of RTP protocol:

in case of radio directions equipped with MD300 and ODU 300 and with differential clock recovery (and then with RTP) is equal to 2,2570 Mbit/s

in case of radio directions equipped with MPT-ACC and MPT-HC or MC and with differential clock recovery (and then with RTP) is equal to 2,2579 Mbit/s

N.B. Only TDM2ETH service with differential clock recovery has been considered.

To simplify the management it is possible, of course, to consider just one bandwidth, disregarding the ODU type and the service type. In this case the bandwidth used by a TDM2TDM servce flow with an ODU 300 (the maximum one) should be used. To know if adaptive modulation is enabled or not, the adaptiveModulationMode columnar object (opticsIMAdaptiveModulationTable) must be read (true => enabled, false => disabled).


It. 10

44/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Radio directions in Adpative Modulation with CAC disabled- Number of spare E1 NOT REQUIRED CAC can be disabled in adaptive modulation only in case of radio direction equipped with MD300 and ODU 300. If the Wind application uses the radio bandwidth associated to the 16QAM as maximum bandwidth for the E1 flows, the bandwidth not yet used and present in the radioPDHTTPBidAvailableBandwidth columnar object, cannot be used to compute the number of spare E1. In fact, this object contains the available bandiwidth to reach the bandwidth associated to 64QAM modulation and not the one associated to 16QAM. To compute this available bandwidth, the net bandwidth associated to 16 QAM must be known. This bandwith is not available in the MIB. It depends on the Channel Spacing. For each supported Channel Spacing this bandwidth must be hardcoded in the managing system. The values are the following:

7 MHz => 20, 358 Mbit/s 14 MHz => 42,118 Mbit/s 28 MHz => 85, 638 Mbit/s

To choose the net bandwidth associated to the channel spacing configured, the channel spacing must be read from the MIB. The channel spacing is available in the radioPDHTTPBidChannelSpacing columnar object (opticsIMRadioPDHTTPBidTable). Then the available bandwidth is the difference between the available bandwidth read from the radioPDHTTPBidAvailableBandwidth (that is referred to 64 QAM) and the net bandwidth associated to the configured channel spacing, determined before.

The number of spare TDM2ETH service flow can be obtained taking the integer part of the result of the division between the available bandwidth and the bandwidth used by an TDM2ETH service flow (see above).

Ethernet ports - Number of spare E1- NOT REQUIRED

The number of E1 flows that can be cross-connected over a given Ethernet port, can be computed by a managing system knowing the bandwidth not yet used, then available for new new cross-connections, and the bandwidth used by an TDM2ETH service flow.

The number of spare TDM2ETH service flow can be obtained taking the integer part of the result of the division between the bandwidth not yet used (available bandwidth) and the bandwidth used by an TDM2ETH service flow. As already defined, the bandwidth not yet used and then available for new new cross-connections is present in the opticsIMEthAvailableBandwidth columnar object (opticsIMEthConfTable). The bandwidth used by an TDM2ETH service flow when cross-connected over an Ethernet port is equal to 2,5450 Mbit/s. N.B. Only TDM2ETH service with differential clock recovery has been considered.

E1 boards - Number of spare E1- NOT REQUIRED

NTIAL

45/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


The number of E1 flows belonging to a given P32E1DS1 baord that can be cross-connected (spare E1), is provided by the difference between the total number of ports (32) and the number of E1 already cross-connected (see above).


It. 10

46/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA


The SNMP table (with the associated columnar objects) and the scalar objects to be supported is provided in the following table. The indexes value of all the supported entries is provided too.

opticsIMRadioPDHTTPBidTable (opticsIMRadioTrsPdhMib)




50x11 (x=3..8)


50x11 All the 1+1

ODU300


50x01

x = 3,5,7




5xp1xp (x=1 and p=5)

or (x=3..8 and p=1..4)


5xp1xp All the 1+1

MPT

Radio port – Dir#x.p Ch#0 5xp0yq

(x=y=3..8 p=1..3 q=2..4 P<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)

In case of 1+1 radio configurations, the radio direction is identified by the main radio channel (Ch#1) .

NTIAL

47/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Supported Objects

Objects

opticsIMRadioPDHTTPBidTable radioPDHTTPBidAvailableBandwidth radioPDHTTPBidNetBandwidth

opticsIMETSInFlowTable (opticsimETSMib)


All E1 flows 1..N (N=128*6*2+1

Supported Objects

Objects

opticsIMETSInFlowTable opticsIMETSInFlowServiceID opticsIMETSInFlowCrossConnectIdentifier

opticsIMETSOutFlowTable (opticsimETSMib)


All E1 flows 1..N (N=128*6*2)

Supported Objects

Objects

opticsIMETSOutFlowTable opticsIMETSOutFlowServerID opticsIMETSOutFlowCrossConnectIdentifier

opticsIMAdaptiveModulationTable (opticsIMRadioTrsPdhMib)


It. 10

48/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA




50x11 (x=3..8)

1+1 HSB ODU300 Radio port – Dir#x Ch#1

50x11 (x = 3,5,7




5xp1xp (x=1 and p=5) or (x=3..8 and p=1..4)


5xp1xp All the 1+1

MPT

Radio port – Dir#x.p Ch#0 5xp0yq

(x=y=3..8 p=1..3 q=2..4 P<q)

or (x=3,5,7 y=x+1 p=1..4 q=1..4)

Supported Objects

Objects

opticsIMAdaptiveModulationTable adaptiveModulationMode

Scalar objects (opticsIMRadioTrsCommonMib)

Objects

opticsIMRadioAtpcDirectionId

NTIAL

49/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


opticsIME1pPITTPTable (opticsIMTrsCommonMib) – NOT REQUIRED See E1 Inventory section.

ifMauTable (MAU-MIB) – NOT REQUIRED


All Electrical Ethernet User ports on Core board

7010y; 1 (y = 1..4)

All Optical Ethernet User ports on Core board

70105; 1

Supported Objects – NOT REQUIRED

Objects

ifMauTable ifMauType

opticsIMEthConfTable (opticsimEthNEMib) – NOT REQUIRED


CORE-ENH Electrical Ethernet User Tx ports

7010x (x = 1..4)

CORE-ENH Optical Ethernet User ports

70105

Supported Objects – NOT REQUIRED

Objects

opticsIMEthConfTable opticsIMEthAvailableBandwidth


It. 10

50/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

11 ADDITIONAL PARAMETERS TO BE COLLECTED

11.1 NE Parameters

Parameter: NE Name MIB object: tsdimSdhNeLabel scalar object (in tsdimSnmpNEMib MIB) or sysName scalar object (in system MIB). They contain the same value. See section 4.1 and F-44 in section 4.2.

Parameter: NE SW Release MIB object: sysDescr scalar object (in system MIB). See section 4.1 and F-28 in section 4.2.

11.2 Radio Parameters

The list of radio channels provisioned can be retrieved reading the entries in the opticsIMRadioPDHTTPBidTable (opticsIMRadioTrsPdhMib MIB). Each entry represents a radio channel. The 1+0 radio configuration is defined by a single radio channel, the 1+1 radio configurations are composed by two radio channels. So in case of 1+1 radio configurations, two entries are present in the opticsIMRadioPDHTTPBidTable: one for the Main radio channel and one for the Spare (protection) radio channel. The naming rules for opticsIMRadioPDHTTPBidTable has been defined in section 10.2 In case of 1+1 radio configurations, the main channel is identified as Ch#1, the spare (or protection) channel as Ch#0.

Slot and Slot Protection associated to each radio channel can be obtained by the ifIndex value of these entries, according to following rules:

ODU 300, 1+0 configuration and Main channel for 1+1 configurations naming rule = 50x11 (identified by the value 1 as fourth digit (50x11)) Slot = x

ODU 300, Spare/Protection channel in case of 1+1 configurations

naming rule = 50x01 (identified by the value 0 as fourth digit (50x01)) Slot Protection= x

MPTs, 1+0 configuration and Main channel for 1+1 configurations

naming rule = 5xp1xp (identified by the value 1 as fourth digit (5xp1xp)) Slot & Port= xp

MPTs, Spare/Protection channel for 1+1 configurations

NTIAL

51/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


naming rule = 5xp0yq (identified by the value 0 as fourth digit (5xp0yq)) Slot & Port Protection= yq

Each of the following parameters is provisioned per each radio direction, so in case of 1+1 radio just the entry related to the Main channel (Ch#1) must be considered.

Parameter: Channel Spacing (both in Static and Adaptive Modulation) MIB object: opticsIMRadioPDHTTPBidTable / radioPDHTTPBidChannelSpacing (in opticsIMRadioTrsPdhMib MIB)

Parameter: Modulation (in Static Modulation only) MIB object: opticsIMRadioPDHTTPBidTable / radioPDHTTPBidModulation (in opticsIMRadioTrsPdhMib MIB)

Parameter: Capacity (Net Bandwidth in Static Modulation) MIB object: opticsIMRadioPDHTTPBidTable / radioPDHTTPBidNetBandwidth (in opticsIMRadioTrsPdhMib MIB)

Parameter: Adaptive Modulation mode MIB object: opticsIMAdaptiveModulationTable / adaptiveModulationMode (in opticsIMRadioTrsPdhMib MIB) adaptiveModulationMode = 'true' if adaptive modulation is enabled, ‘false’ if the static modulation is enabled.

Parameter: Min Modulation (in Adaptive Modulation only) MIB object: different objects must be used depending on the ODU type:

ODU 300: opticsIMAdaptiveModulationTable / adaptiveModulationSchemeRange (in opticsIMRadioTrsPdhMib MIB). adaptiveModulationSchemeRange is a string and contains all the modulations provisioned, it can assume one of the following values:

o " 4 QAM / 16 QAM / 64 QAM " o " 4 QAM / 16 QAM "

So the minimum modulation is always 4 QAM. MPTs : opticsIMAdaptiveModulationTable / adaptiveModulationSupported (in

opticsIMRadioTrsPdhMib MIB). adaptiveModulationSupported is a bit map, each bit is associated to a modulation. Bits set to 1 represent the modulations provisioned, within this set the minimum modulation has to be considered.

Parameter: Max Modulation (in Adaptive Modulation only) MIB object: different objects must be used depending on the ODU type:

ODU 300: opticsIMAdaptiveModulationTable / adaptiveModulationSchemeRange (in opticsIMRadioTrsPdhMib MIB). Based on the values above for the Min Modulation, the maximum modulation can be either 64 QAM or 16 QAM.


It. 10

52/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

MPTs : opticsIMAdaptiveModulationTable / adaptiveModulationSupported (in opticsIMRadioTrsPdhMib MIB) As above, bits set to 1 represent the modulations provisioned, within this set the maximum modulation has to be considered.

Parameter: Min Capacity (Min Net Bandwidth in Adaptive Modulation with CAC enabled) MIB object: opticsIMRadioPDHTTPBidTable / radioPDHTTPBidNetBandwidth (in opticsIMRadioTrsPdhMib MIB).

Parameter: Max Capacity (Max Net Bandwidth in Adaptive Modulation with CAC enabled) MIB object: Not Available.

Parameter: Output Power Mode MIB object: opticsIMRadioTxPowerTable / radioAtpcEnabled (in opticsIMRadioTrsCommonMib MIB). radioAtpcEnabled = “true” if ATPC is enabled, “false” if ATPC is disabled (and then RTPC is enabled).

Parameter: Remote IP Address MIB object: opticsIMPointToPointIPTable / opticsIMPointToPointIPRemoteAddress (in opticsIMCommRouMib MIB).

Parameter: XPIC XPIC is not supported by MPR 3.0 and previous releases.

NTIAL

53/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


1112 ANNEX 1: ELABORATED ETHERNET COUNTERS

These are the formulas for Ethernet Statistics data retrieval and elaborated counter, on

‐ 1) Aggregate Tx table for Ethernet flows over radio,

‐ 2) Queues for Ethernet flows over radio

‐ 3) Aggregate Tx and Rx tables for Ethernet flows over USER access ports

according to current MIB naming.

Note: ∆value means (valuet−value

t−1 ), always not null or positive value (in case to add the proper

overflow value)

The availability of these measurements, applied to a typical MPR cluster, provides the following details at network level:


It. 10

54/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

1TDM

1TDM +2+ 4

23GHz

1+0 8x216QAM

NO005

1TDM + 2+ 4

NO003

NO044

NO009

1TDM + 2+ 41TDM + 2+ 4

1TDM + 2+ 4

1TDM + 2+ 4

2TDM + 2+ 4

1TDM + 2+ 4

2TDM + 4+ 3

23GHz1+0 8x216QAM

26GHz

1+1 18x216QAM

18GHz

1+1 18x216QAM 23GHz

1+0 8x216QAM

18GHz

1+0 8x216QAM

Ethernet flows example:I/O flows from user accessTraffic on Back directionTraffic on Haul direction

NTIAL

55/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Elaborated Ethernet over Radio : per aggregate

Reference table is ethAggrMaintTxTable (1.3.6.1.4.1.637.54.1.25.4.11), indexing by radio direction.

TTO

Rate (100 Kbps) is the rate of transmitted good bytes in hundreds of Kbps

ΔTTO(Bytes) x 8

TTORate

(100 Kbps)= ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

Δt (s) x 10002

TDF

Ratio is the percentage of packets dropped by the forwarding process due to lack of resources

ΔTDF TDF

Ratio = ------------------------

ΔTTF + ΔTDF

where: • TTO=ethAggrMaintTxTTO (1.3.6.1.4.1.637.54.1.25.4.11.1.1);

• TDF=ethAggrMaintTxTDF (1.3.6.1.4.1.637.54.1.25.4.11.1.3);

• TTF=ethAggrMaintTxTTF (1.3.6.1.4.1.637.54.1.25.4.11.1.2).


It. 10

56/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

Elaborated Ethernet over Radio : per queues (optional)

For queues: i [1..5] . Reference table is: ethAggrPerQueueMaintTable (1.3.6.1.4.1.637.54.1.25.4.39),

indexing by radio direction.

ΔTCOi

(Bytes) x 8 x 10

TCOi

Rate (100 Kbps)= ………………………

Δt (s) x 10002

ΔDiscardTCF i

x 100

DiscardTCFi

Ratio

=………………………….

ΔTCFi

+ ΔDiscardTCFi

where: • TCO=ethAggrPerQueueMaintTCO (1.3.6.1.4.1.637.54.1.25.4.39.1.7 );

• DiscardTCF=ethAggrPerQueueMaintDiscardTCF (1.3.6.1.4.1.637.54.1.25.4.39.1.5 );

• TCF=ethAggrPerQueueMaintTCF (1.3.6.1.4.1.637.54.1.25.4.39.1.3 ).

NTIAL

57/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Elaborated Ethernet counters for user access ports

Reference table is ethAggrMaintTxTable (1.3.6.1.4.1.637.54.1.25.4.11), indexing by IFMau

(Core=7010x)

TTO

Rate (100 Kbps) is the rate of transmitted good bytes in hundreds of Kbps

ΔTTO(Bytes) x 8 x 10

TTORate

(100 Kbps)= ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

Δt (s) x 10002

TxTDF


ΔTxTDF x 100 TxTDF

Ratio = ------------------------

ΔTTF + ΔTxTDF

where: TTO=ethAggrMaintTxTTO (1.3.6.1.4.1.637.54.1.25.4.11.1.1);

TxTDF=ethAggrMaintTxTDF (1.3.6.1.4.1.637.54.1.25.4.11.1.3);

TTF=ethAggrMaintTxTTF (1.3.6.1.4.1.637.54.1.2. 1.25.4.11.1.2).

TRCORate

(100 Kbps) is the rate of received good bytes in hundreds of Kbps

ΔTRCO(Bytes) x 8 x 10

TRCORate

(100 Kbps)= ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

Δt (s) x 10002

RxTDF


ΔRxTDF x 100 RxTDF

Ratio = ------------------------

ΔTRCF + ΔRxTDF

where: TRCO=ethAggrMaintRxTRCO

RxTDF=ethAggrMaintRxTDF

TRCF=ethAggrMaintRxTRCF


It. 10

58/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

1113 ANNEX 2: NAMING DESCRIPTION

MSS-8 consists of a subrack with 9 physical slots:

Slot 1 is reserved to the Core-E Main Controller. Slot 2 is reserved to the Optional Spare Core-E Controller. Slot 9 is reserved to the Fans. Slots 3 to 8 are reserved to the units: Line-PDH unit or ASAP unit or Modem unit (to interface

ODU300) or MPT Access Peripheral unit (to interface the MPT-HC or MPT-MC). Slot 8 can be equipped also with the optional AUX peripheral unit.

The maximum number od ODU 300 is 6, this means up to 6 radio directions in 1+0, up to 3 in 1+1. The maximum number od MPT Access peripheral is 6, each of them with up to 2 MPTs connected. This means up to 12 radio directions in 1+0, up to 6 in 1+1. One radioPDHTTPBidEntry and one opticsIMAdaptiveModulationEntry are present in the MIB per each radio direction.

Slot 1 Slot 2

Slot 9 Slot 3 Slot 4

Slot 5 Slot 6

Slot 7 Slot 8

MSS-4 consists of a subrack with 5 physical slots:

Slot 1 is reserved to the Core-E Main Controller. Slot 2 is reserved to the Optional Spare Core-E Controller. Slot 5 is reserved to the Fans. Slots 3 and 4 are reserved to the units: Line-PDH unit or Modem unit (to interface ODU300) or

MPT Access Peripheral unit (to interface the MPT-HC or MPT-MC). Slot 4 can be equipped also with the optional AUX peripheral unit.

The maximum number od ODU 300 is 2, this means up to 2 radio directions in 1+0, up to 1 in 1+1. The maximum number od MPT Access peripheral is 2, each of them with up to 2 MPTs connected. This means up to 4 radio directions in 1+0, up to 2 in 1+1. One radioPDHTTPBidEntry and one opticsIMAdaptiveModulationEntry are present in the MIB per each radio direction.

Slot 1 Slot 2

Slot 5 Slot 3 Slot 4

NTIAL

59/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


Different ODU Types Three types of ODU are available, as shown in the Figure below.

The ODU300 is identified by a number indicating the slot number in the MSS, where the Modem unit is installed. The MPT-HC or MPT-MC is identified by two digits:

the first digit indicating the slot number in the MSS, where the MPT Access unit is installed the second digit indicating the enabled Ethernet port in the MPT Access unit (from 1 to 4).

Radio Interfaces naming rules Radio interfaces are identified by a radio direction and by one or two radio channels. In 1+0 configuration, just one radio channel is used for a given radio direction. In 1+1 configurations, to provide protection, two radio channels are used for a given radio direction. Different naming rules are used for ODU 300 and MPT-HC/MC: ODU 300: 5XXCP

XX: it identifies the Radio Direction, it is the MSS Slot number where the MSS board that provides the connection to the ODU is equipped. In case of 1+1 radio configuration, the radio direction is identified by the board with the Main role in the protection, then the one equipped in the slots 3, 5, 7

C: it identifies the the radio Channel number o 1: in 1+0 configuration and in case of Main unit in 1+1 configurations o 0: in case of Spare unit in 1+1 configurations

P: it identifies the Port number (always 1)


It. 10

60/61 WT

01 ED

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts,

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

1AA

000

14 0

004

(97

11)

A4

3DB 18653 0000 DSZZA

MPTs: 5XPCYQ

XP: it identifies the Radio Direction, X is the MSS Slot number where the MSS board that

provides the connection to the MPT is equipped, P is the port number on the MSS board that provides the physical connection to the MPT In case of 1+1 radio configuration, X the radio direction is identified by the board/port with the Main role in the protection

C: it identifies the the radio Channel number o 1: in 1+0 configuration and in case of Main unit in 1+1 configurations o 0: in case of Spare unit in 1+1 configurations

YQ: it provides the identification of the radio channel in terms of MSS board (slot) and port that provides the connection to the MPT. In case of 1+0 configuration and main unit (Ch#1) in 1+1: Y=X and Q=P

Ethernet Interfaces naming rules The general naming rule for the Ethernet interfaces is the following: 7SSPP, where:

SS: it identifies the slot where the board that provides the Ethernet interface is equipped PP: it identifies the Ethernet port

User Etherent interfaces are present and managed only on the Core-E controller board.

NTIAL

61/61

ED 01

WT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts, n

ot

perm

itted

with

out

writ

ten

auth

oriz

atio

n fr

om A

lcat

el

1AA

000

14 0

004

(97

11)

A4

3DB 18379 0000 DSZZA


END OF DOCUMENT

Documents

MPR-E R2 1 SNMPSysSpec_Wind Profiled__it10