Alex 0181

Managed Object Model

DESCRIPTION

2/1551-LZA 104 102/6 Uen E

Copyright

© Ericsson AB 2011. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.These are shown in the document Trademark Information.

2/1551-LZA 104 102/6 Uen E | 2011-09-08

Contents

Contents

1 Introduction 1

1.1 Scope 1

1.2 Target Group 1

1.3 Main Changes 1

2 Management Information Model 2

2.1 Overview 2

2.2 MO Naming Conventions 3

2.3 MIM Concepts 4

2.4 Validation Rules 4

2.5 States of a Managed Object 5

2.6 MO Class Definitions 62.6.1 MO Class AccessControlEntry (manuallyCreated) 102.6.2 MO Class AccessControlList (manuallyCreated) 122.6.3 MO Class BFDSession (systemCreated) 132.6.4 MO Class Bridge (manuallyCreated) 142.6.5 MO Class CcBFDConfig (manuallyCreated) 142.6.6 MO Class CESChannel (manuallyCreated) 152.6.7 MO Class DHCPRelayServerGroup (manuallyCreated) 182.6.8 MO Class E1T1Interface (manuallyCreated) 202.6.9 MO Class Equipment (systemCreated) 212.6.10 MO Class EthernetInterface (manuallyCreated) 222.6.11 MO Class HDLCPWEChannel (manuallyCreated) 272.6.12 MO Class IPInterface (manuallyCreated) 302.6.13 MO Class IpRoute (manuallyCreated) 372.6.14 MO Class IpRoutePbr (manuallyCreated) 392.6.15 MO Class IpRouteSys (systemCreated) 402.6.16 MO Class LinkOAM (manuallyCreated) 412.6.17 MO Class LocalConnect (manuallyCreated) 432.6.18 MO Class LocalMEP (manuallyCreated) 462.6.19 MO Class ManualSAPair (manuallyCreated) 482.6.20 MO Class MeasuredMOClass 502.6.21 MO Class MeasurementCounters 512.6.22 MO Class MeasurementDefinition (systemCreated) 512.6.23 MO Class MEG (manuallyCreated) 522.6.24 MO Class ML-PPP (manuallyCreated) 552.6.25 MO Class PingMeasurement (manuallyCreated) 602.6.26 MO Class Policy (manuallyCreated) 622.6.27 MO Class PPP (manuallyCreated) 672.6.28 MO Class QosPolicy (manuallyCreated) 692.6.29 MO Class RemoteMEP (manuallyCreated) 782.6.30 MO Class RoutingPolicy (manuallyCreated) 79

2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.31 MO Class RoutingRule (manuallyCreated) 802.6.32 MO Class RoutingTable (systemCreated) 832.6.33 MO Class SecondaryIP (manuallyCreated) 842.6.34 MO Class Security (manuallyCreated) 852.6.35 MO Class STN (systemCreated) 862.6.36 MO Class SuperChannel (manuallyCreated) 902.6.37 MO Class SynchEthInterface (manuallyCreated) 922.6.38 MO Class Synchronization (systemCreated) 962.6.39 MO Class TGTransport (manuallyCreated) 982.6.40 MO Class TimeServer (manuallyCreated) 1022.6.41 MO Class TrafficManager (manuallyCreated) 1042.6.42 MO Class VirtualIPInterface (manuallyCreated) 1152.6.43 MO Class VLAN (manuallyCreated) 1162.6.44 MO Class VLANGroup (manuallyCreated) 119

Glossary 121

Reference List 123

2/1551-LZA 104 102/6 Uen E | 2011-09-08

Introduction

1 Introduction

This chapter outlines the scope, structure and intended target groups of thisdocument.

1.1 Scope

This document describes the Managed Object (MO) Model (MOM) for theSite Integration Unit (SIU 02) valid for the T11B software release. For furtherinformation about the SIU unit, see Reference [6].

It includes all MO classes and their attributes and counters (when available)for software implementing IRP version 5.5 of the MOM. Formats of thePerformance Management (PM) files used to transfer counters for storage andpost-processing are described in Reference [4].

A subset of the generic Site Transport Node (STN) for Radio Base Station(RBS) MOM with IRP version 5.5 are supported.

1.2 Target Group

The intended target groups for this document are:

• Radio Network Engineers.

• System Administrators.

• Field Technicians.

• Installation and Integration personnel.

• Site Engineers.

1.3 Main Changes

For information about the main changes in this Ericsson release, see Reference[2].

12/1551-LZA 104 102/6 Uen E | 2011-09-08


2 Management Information Model

This chapter describes the Management Information Model (MIM).

2.1 Overview

The MIM containment hierarchy and the cardinality constraints for the MOinstances are illustrated in the following aggregation view diagram.

Figure 1 MIM Aggregation View

The configurable use dependencies between the MO instances of the MIM aredescribed in the following diagram.

Note: Only one of the dependencies with an {xor} constraint can beconfigured.

2 2/1551-LZA 104 102/6 Uen E | 2011-09-08

Management Information Model

Figure 2 MIM Use Dependency View

Note: MO classes Security, ManualSAPair and Policy have been removedfrom this diagram as they have been deprecated. It is still possible toconfigure them, however they will have no effect.

2.2 MO Naming Conventions

Name conventions for MOs are restricted to a subset of the definition in 3GPPReference [7].

Each MO is identified with a Distinguished Name (DN) that expresses itscontainment hierarchy. The comma (,) is used as the delimiter betweenthe various levels of the DN. Each level is represented with a RelativeDistinguished Name (RDN). The RDNs in the MO model always consist of a<class_name>=<instance id>. This means that the class_name is not allowedto contain a comma (,), equals sign (=), or whitespace. All RDNs included in theMO hierarchy path must be specified. The name convention must be followedfor the MO-DN attribute.

Examples:

STN=0,Equipment=0

32/1551-LZA 104 102/6 Uen E | 2011-09-08


STN=0,TGTransport=TGSven,SuperChannel=3

DN prefix is not supported.

2.3 MIM Concepts

This section describes concepts of the MIM.

• SystemCreated MOsSystemCreated MOs are created by the node itself. They cannot becreated or deleted by the user (management system).

• ManuallyCreated MOsManuallyCreated MOs are user created and user deleted. ManuallyCreatedMOs are only allowed to aggregate ManuallyCreated MOs.

• AggregationAggregation is a special kind of associations - a whole/part relationshipwithin which one or more MO classes are parts (children) of a larger whole(parent). Aggregation is used to depict the containment associations. Thecontainment association is expressed through name bindings (MO-DN).

• Dependency (use)Conceptually, a use dependency is a dependency where the client MOrequires the presence of the supplier MO for its correct functioning. A usedependency depicts functional dependencies.

2.4 Validation Rules

The following list defines rules for considering a configuration valid atcommands commit (basic CM) or activate (bulk CM).

• Creation of child MO is only possible if also the parent MO has beencreated.

• Cardinality constraints are validated.

• The attribute instanceId must not be the same for any two MO instances ofthe same MO class and with the same parent MO.

• IPv4 addresses are validated in accordance to section 3.2.1.3 of IETF RFC1122 (Reference [8]). For example:

� Only class A, B and C addresses are allowed.

� Local host (including local network) addresses are not allowed.

� Broadcast addresses are not allowed.

� Internal host loopback addresses are not allowed.

4 2/1551-LZA 104 102/6 Uen E | 2011-09-08


• The address range defined by an IP address and subnet mask mustnot overlap any other configured address ranges in MO IPInterface orVirtualIPInterface.

• The attribute instanceId must not consist of the reserved word "ALL".

• Dependency attributes between MOs must refer to existing MO instancesif a dependency is defined. Dependency attributes are named with prefix"dep", for example the depEthernetInterface attribute of MO IPInterface.

• An MO instanceId (string(m)) shall not begin with _ (underscore), - (minus)or # (hashmark), shall not contain consecutive underscores "__" and cannotend with _ (underscore).

2.5 States of a Managed Object

The management state of an MO represents the instantaneous condition ofavailability and operability of the associated resource from the point of viewof management. Currently it is only the operability factor that is reflected byrelevant MOs.

The operability of an associated resource is described by the MOsoperationalState attribute, which has to possible values: "enabled" and"disabled".

• Enabled: The resource is partially or fully operable and available for use.

• Disabled: The resource is totally inoperable and unable to provide servicesto the users.

Operational state is used for MOs complying with at least one of the followingcriteria:

• Represents a functionality that may become inoperable.

• Can submit critical alarms.

• Has dependencies to other MOs needing to propagate operational stateto higher level MOs.

Conceptually an MO is disabled while at least one of the following criteria is true:

• The MO itself is inoperable.

• Vital child MOs are in the disabled state or have not been created.

• Vital supplier MOs with a use dependency is in the disabled state or havenot been created.

Conceptually an MO is in enabled state while all of the following criteria are true:

• The MO itself is partially or fully operable.

52/1551-LZA 104 102/6 Uen E | 2011-09-08


• Vital child MOs are enabled and have been created.

• Vital supplier MOs with a use dependency are enabled and have beencreated.

2.6 MO Class Definitions

This section describes each MO class and its attributes.

Each MO class is described in tables with fields as described below:

Name The name of the attribute.

CLI The supported Command Line Interface (CLI) accesstypes are as follows:

RO Read only – only the getMOAttribute command issupported.

R/W Read write – both the getMOAttribute and thesetMOAttribute commands are supported.All R/W attributes have a default value.

WO Write only – both getMOAttribute andsetMOAttribute commands are supported.At getMOAttribute the attribute value is a stringwith three asterisks (***) if the attribute is configured,otherwise the value is an empty string (“”), indicating thatthe attribute is not configured.

Type Data type and value range of attribute, using thefollowing base types:

6 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Enumerations A list of possible values delimited by slashes. Note thatthese enumerations can be represented using variouscoding schemes in solution sets other than the CLI.notSupported is a reserved word and not allowed as anenumeration value.

Integers Defined with a value range. For example, 0..63 whichrepresents all integers between 0 and 63.

If a value is entered with a leading zero "063", the nodewill interpret this as an octal value which is the same asdecimal 51.

Strings Textual values with possible lengths in accordance withthe range specified, for example, string 0..16 has up to16 useful characters.

(p) – used for most of the attributes with data type string.Valid characters are printable US ASCII except doublequotation marks(1) and semicolon:

whitespace ! # $ % & ‘ ( ) * + , � . / : 0–9 < = > ? @A–Z [ \ ] ^ _ a` –z { | } ~

(m) – used for attributes related to MO name and MOinstanceId. Valid characters:

0–9 A–Z a–z _ - [ ] #

(h) – used for representing hexadecimal values. Validcharacters:

0–9 A–F a–f

(1) CLI surrounding strings containing at least one whitespace character must be enclosedin double quotation marks.

IPv4Address An Internet Protocol version 4 address. Transmittedin the CLI as a string with dotted decimal notation,for example 10.0.0.1, but can use different codingschemes in the other solution sets. If the IPv4address isnotDefined, the value used is 0.0.0.0.

IPv4addressRange A short form that covers an Internet Protocol version4 subnet address with address mask. Transmitted inthe CLI as a string with CIDR (or slash) notation, forexample 192.168.0.0/24, but can use different codingschemes in other solution sets. IPv4addressRangeis an alternative address range specification. Forexample, 192.168.0.0/24 is the same as address range192.168.0.0–192.168.0.255. 24 means that the fixedpart of the range covers the 24 most significant bits ofthe IP address. If IPv4addressRange is notDefined, thenthe value used is 0.0.0.0/0.

72/1551-LZA 104 102/6 Uen E | 2011-09-08


IPv4subnetMask An Internet Protocol version 4 subnet mask. A subnetmask is used to determine which part of an IP addresspertains to the sub-network and which part pertainsto the host. The subnet mask is a 32-bit field used incombination with the IP address. Transmitted in the CLIas a string with dotted decimal notation, for example,255.255.255.0, but can use different coding schemes inother solution sets. If the IPv4subnetMask is notDefined,then the value used is 0.0.0.0.

MACAddress An MAC address in accordance with IEEE 802.3,formatted as a colon-separated list of hexadecimalvalues with one value for each octet, for example,00:0D:56:C0:9D:41.

Date Date defined as a string of 8 characters with the formatYYYYMMDD.

MO-DN Managed Object Distinguished Name. The MO-DN is astring(m) with 0..80 characters. Class names are casesensitive.

Example: STN=0,IPInterface=0,VirtualIPInterface=0

Signed integers Defined with a value range, for example, -10..50, whichrepresents all positive and negative integers between-10 and +50.

Time Time defined as a string of characters with the formatHH:MM:SS.

Default Value Specifies the default value for the attribute. If empty, nodefault value exists.

Note: For a number of attributes the value of DefaultValue will be declined as being not acceptable asconfigured value. This is to ensure that such attributesare given deliberately chosen values for example ifsome kind of uniqueness amongst values is required.

Restart Type The restart type indicates what type of restart occurswhen the attribute is changed. The SIU decides if arestart is needed, and at what level, and performsthe restart. The SIU can decide not to restart even ifspecified, but it is not allowed to restart if not specified.The supported values are as follows:

• <empty>No restart is performed when the attribute ischanged (can also be indicated by noRestart (no)).

• noRestart (no)

8 2/1551-LZA 104 102/6 Uen E | 2011-09-08


No restart is performed when the attribute ischanged (can also be indicated by an empty field).

• MORestart (mo)An MO restart is performed when the attribute ischanged. At MO restart the MO can stop providingits services for a longer or shorter time. MO alarmsare cleared and MO counters are reset at anMO restart. The SIU sends notifyClearedAlarmnotifications to indicate cleared alarms at MOrestart. Note that parent MOs and dependent MOsare not affected by an MO restart unless specificallymentioned.

• nodeRestart (node)The SIU restarts when the attribute is changed.The node stores persistent information. Alarmsare cleared and counters are reset at a noderestart. The SIU does not send notifyClearedAlarmnotifications to indicate cleared alarms at noderestart.

Description A description of how the attribute must be interpreted,including an attribute-specific validation rule (taggedRule:). Rules must be possible to validate. Attributesused in rules must be stated with attribute name andvalue.

Counters (when available) are presented in separate tables for each MO classand includes the following information:

Name The name of the counter attribute.

Position The counter position in a measurement report.

Type The following counter types are used for collectingmeasurement results:

• PEG - A counter that is increased by 1 at eachoccurrence of a specific activity.

• GAUGE - A counter that is increased or decreaseddepending on the activity in the system.

A counter is reset to 0 when the SIU is restarted.

Range Lowest and highest count for the counter.

Description A summary of what the counter monitors.

The operator can subscribe to performance data, that is all counters in alldefined MO classes. The counters are then compiled into files and pushed to

92/1551-LZA 104 102/6 Uen E | 2011-09-08


a central storage in OSS-RC. See Reference [4] for further information aboutmanaging the PM file collection.

2.6.1 MO Class AccessControlEntry (manuallyCreated)

MO class AccessControlEntry represents an element in anAccessControlList. The element contains a set of criteria for a packet, that allhave to be met to trigger the specified action for the packet.

2.6.1.1 MO Class AccessControlEntry Parameters

Table 1 MO class AccessControlEntry parameters

Name CLI Type DefaultValue

RestartType

Description

instanceId RO String(m)1..20

Instance identifier of the MO.Consists of an operator-defined name.

Rule: In the same instance of MOAccessControlList there cannot be twoinstances of MO AccessControlEntry withidentical values for the criteria attributes (1-6).

Priority R/W Integer0..511

0 mo (1)Entries are ordered and searched through by theimplementation according to this number where"0" is highest priority and "511" is lowest priority.

Rule: The priority must be unique among the MOAccessControlEntry instances in a given MOAccessControlList.

Tip: Make large gaps between priority numbersso that new entries can easily be defined andinserted wherever required in an existing MOAccessControlList.

Action R/W permit/deny

deny mo (1) The action that will be applied to packetsmatching the criteria in this entry.

criteriaSourceAddr

R/W String(p)3..31

any mo (1) Criteria 1: Source IP address in the packet. Theattribute value can be:

IPv4address/IPv4addressRange/"ANY"

ANY means any IPv4 address.

An IPv4addressRange is a subnet, for example192.168.0.0/24.

10 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 1 MO class AccessControlEntry parameters


RestartType

Description

criteriaDestinationAddr

R/W String(p)3..31

any mo (1) Criteria 2: Destination IP address in the packThe attribute value can be:



An IPv4addressRange is a subnet, for examp192.168.0.0/24.

criteriaProtocol R/W String(m)1..10

any mo (1) Criteria 3: Protocol selector specifying upperprotocol type. The attribute value can be:

protocolNumber/"ANY"protocolNumber = a number between 0 and 2

Note: For protocol numbers, see Reference [

criteriaSourcePort

R/W String(m)1..11

any mo (1) Criteria 4: Source port number in the packetThe attribute value can be:

portNumber/”ANY”/portNumber = a number between 0 and 6553

ANY means this criteria is wildcarded.

Rule: If criteriaProtocol is NOT one of {"6" (TC"17" (UDP)} criteriaSourcePort must be "ANY

criteriaDestinationPort

R/W String(m)1..11

any mo (1) Criteria 5: Destination port number in the pacThe attribute value can be:

portNumber/”ANY”/portNumber = a number between 0 and 6553


Rule: If criteriaProtocol is NOT one of {"6"(TCP), "17" (UDP)} criteriaDestinationPort mube "ANY".

criteriaInterfaceDirection

R/W inout/in/out

inout mo (1) Criteria 6: Indicates the direction in which thpacket must be traversing the interface on whthis MO AccessControlList instance is used

(1) Change of attribute causes traffic impact a longer or shorter time.

112/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.1.2 MO Class AccessControlEntry Counters

Note: Reset of counters performed only at node restart.

Table 2 MO class AccessControlEntry counters

Name Position

Type Range Description

inPacketsHandled 1 PEG 0..264-1 The number of ingress packets triggered by theentry in the Access Control List.

outPacketsHandled 2 PEG 0..264-1 The number of egress packets triggered by theentry in the Access Control List.

2.6.2 MO Class AccessControlList (manuallyCreated)

MO class AccessControlList aggregates a set of MO classAccessControlEntry instances to form an access control list.

2.6.2.1 MO Class AccessControlList Parameters

Table 3 MO class AccessControlList parameters


RestartType

Description



Note: If more than one MO IPInterface instancerefers to a given MO AccessControlListinstance, counters will be common to all.

Rule: Among the contained MOAccessControlEntry instances, theremust not be two instances where the filter criteriaare identical (attributes criteraSourceAddr,criteriaDestinationAddr, criteriaProtocol,criteriaSourcePort, criteriaDestinationPort)and the direction criteria overlap (attributecriteriaInterfaceDirection).

2.6.2.2 MO Class AccessControlList Counters

No counters exist.

12 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.3 MO Class BFDSession (systemCreated)

MO class BFDSession represents an existing BFD session. Instances arecreated dynamically by the system, and allows the user to monitor state andstatistics on current BFD sessions.

2.6.3.1 MO Class BFDSession Parameters

Table 4 MO class BFDSession parameters


RestartType

Description


Instance identifier of the MO.The instance identifier string is a concatenatio1) the instanceId of the IPInterface instance(referred to by attribute localInterface), and2) the value of attribute nextHopAddress in thformat v_w_x_y/z).The two parts are separated by an "-".

localInterface RO MO-DN Reference to the MO IPInterface instance thaoriginates this session.

nextHopAddress

RO IPv4addressRange

IP address of next hop IP neighbor.

state RO init/up/down

The current state of the session.

remoteHeardFlag

RO true/false

Specifies the status of BFD packet receptionfrom the remote system. Specifically, it is set"true" if the local system is actively receiving Bpackets from the remote system, and is set to"false" if the local system has not received BFpackets recently (within the detection time) orthe local system is attempting to tear down thBFD session.

sessDiag RO Integer0..255

A diagnostic code specifying the local systemreason for the last transition of the session fro"up" to some other state.

sessUpTime RO String(m)1..25

The system time value on the most recentoccasion at which the session came "up". If nsuch "up" event exists, this attribute containsempty string.

sessLastDownTime

RO String(m)1..25

The system time value on the most recentoccasion at which the last time communicatiowas lost with the neighbor. If no such "down"event exists, this attribute contains an emptystring.

132/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.3.2 MO Class BFDSession Counters

Table 5 MO class BFDSession counters

Name Position


perfSessUpCount 1 PEG 0..264-1 The number of times this BFD session hasgone into the "up" state.

2.6.4 MO Class Bridge (manuallyCreated)

MO class Bridge represents an 802.1Q VLAN bridge.

2.6.4.1 MO Class Bridge Parameters

Table 6 MO class Bridge parameters


RestartType

Description



operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details: At least two MO VLAN instanceswith the depBridge attribute referencing to thisparticular MO Bridge instance have parent MOVLANGroup instance in the "enabled" state.

"disabled": the resource is totally inoperable andunable to provide service to the user.Details: Any of the "enabled" details are notfulfilled.

2.6.4.2 MO Class Bridge Counters

No counters exist.

2.6.5 MO Class CcBFDConfig (manuallyCreated)

MO class CcBFDConfig represents a BFD configuration that can be appliedon an MO IPInterface.

For further description of the configuration attributes, see the RFC referencesReference [11] and Reference [12].

14 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.5.1 MO Class CcBFDConfig Parameters

Table 7 MO class CcBFDConfig parameters


RestartType

Description


Instance identifier of the MO.

minimumTransmitInterval

R/W Integer10..60000

100 The desired transmit interval (in milliseconds)a BFD session.

minimumReceiveInterval


100 The desired receive interval (in milliseconds)a BFD session.

detectionMultiplier

R/W Integer1..10

5 The multiplier value for a BFD session.

sessionDownTransmitInterval


2000 The desired transmit interval (in milliseconds)a BFD session that is "down".

2.6.5.2 MO Class CcBFDConfig Counters

No counters exist.

2.6.6 MO Class CESChannel (manuallyCreated)

MO class CESChannel represents attributes for a CES Pseudo Wire Emulation(PWE) transport.

2.6.6.1 MO Class CESChannel Parameters

Table 8 MO class CESChannel parameters


RestartType

Description


Instance identifier of the MO.Unique name identifying the CES PWE chann

152/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details: CESChannel is not in LOPS state, anddepE1T1Interface is enabled, anddepIPInterface is enabled.

"disabled": the resource is totally inoperable andunable to provide service to user.Details: Any of the "enabled" details are notfulfilled.

depE1T1Interface

R/W Integer0..15

0 mo Instance number of an MO E1T1Interfaceinstance to which there is a use dependency.

Rule: The MO E1T1Interface instance must beof type "E1" or "T1".

Rule: An MO E1T1Interface instance is onlyallowed to be used by one, and only one,instance of MO CESChannel.

startTS R/W Integer1..31 (E1)/1..24 (T1)

1 mo The starting time slot.

endTS R/W Integer1..31 (E1)/1..24 (T1)

1 mo The ending time slot.

Rule: The value of endTS must be greater thanor equal to the value of startTS.

PWGW_IPAddress

R/W IPv4address

0.0.0.0 mo IP address of the PWGW node.

Rule: The combination of PWGW_IPAdress andPWGW_UDP_Port must be unique among allinstances of MO CESChannel.

Rule: 0.0.0.0 (notDefined) is not a valid value.

PWGW_UDP_Port

R/W Integer0..65535

0 mo Number of the remote UDP port to be used forPWE. The value "0" = notDefined.

Rule: The combination of PWGW_IPAdress andPWGW_UDP_Port must be unique among allinstances of MO CESChannel.

Rule: 0 (notDefined) is not a valid value.

16 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depIP_Interface R/W MO-DN <emptystring>

mo Reference (use dependency) to the IP interfaassigned for PWE traffic.

When a change to the IPAddress attribute ofMO referred to, is committed, the effect is thaduring the change taking effect, some framesmay be lost.

Rule: Must be set to reference either an instaof MO IPInterfaceor VirtualIPInterface.

STN_PWE_UDP_Port

R/W Integer0..65535

0 mo Number of the local UDP port to be used forPWE. The value "0" = notDefined.

Rule: The value of the STN_PWE_UDP_Porattribute must be unique among all instancesCESChannel.

Rule: 0 (notDefined) is not a valid value.

DSCP_PWE R/W Integer0..63

0 DSCP code for PWE channel between the SIand the PWGW.

jitterBufferDepth

R/W Integer1..255

10 mo Depth of jitter buffer in milliseconds.

Rule: This value shall be equal to or larger ththe packetizingLatency attribute.

Note: The total size of the jitter buffer is 2 x tparameter.

packetizingLatency

R/W Integer1..255

2 mo Packetizing latency in milliseconds.

Rule: The product of the packetizingLatencyattribute and number of TS must be at least 8

Note: The maximum value of the product ofpacketizingLatency attribute and number of Tdepends on the value of the MTU attribute fothe depIP_Interface.

consecPktsInSynch

R/W Integer0..232-1

2 mo The number of consecutive packets withsequential sequence numbers that are requireto exit the LOPS state.

consecPktsOutSynch

R/W Integer0..232-1

10 mo The number of consecutive packets withsequential sequence numbers that are requireto enter the LOPS state.

propagateCsErrors

R/W true/false

true mo Propagate AIS and RDI indications from the Pto the CS side.

172/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.6.2 MO Class CESChannel Counters

Table 9 MO class CESChannel counters

Name Position


cesMissingPkts 1 PEG 0..264-1 The number of missing packets (as detectedvia control word sequence number gaps).

cesJtrBfrUnderruns 2 PEG 0..264-1 The number of times a frame needed to beplayed out and the jitter buffer was empty.

cesJtrBfrOverruns 3 PEG 0..264-1 The number of packets that could not fit in thejitter buffer.

cesMisOrderDropped 4 PEG 0..264-1 The number of packets detected out of order(via control word sequence numbers), andcould not be re-ordered.

cesMalformedPkts 5 PEG 0..264-1 Number of packets detected with unexpectedsize, or bad headers' stack.

2.6.7 MO Class DHCPRelayServerGroup (manuallyCreated)

MO class DHCPRelayServerGroup represents attributes of a group of DHCPservers that are used by the hosts attached to IP interfaces that referencethis MO.

2.6.7.1 MO Class DHCPRelayServerGroup Parameters

Table 10 MO class DHCPRelayServerGroup parameters


RestartType

Description


Instance identifier of the MO.Unique name identifying the group of DHCPservers.

DHCPServerAddress_1

R/W IPv4address

0.0.0.0 IP address of a DHCP server in the group.

Rule: At least one of the attributesDHCPServerAddress_1-4 must have avalid "IPv4address" value.

Note: Defined DHCPServerAddress_1-4 shouldbe mutually exclusive.

18 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 10 MO class DHCPRelayServerGroup parameters


RestartType

Description

DHCPServerAddress_2

R/W IPv4address



Note: Defined DHCPServerAddress_1-4 shobe mutually exclusive.

DHCPServerAddress_3

R/W IPv4address




DHCPServerAddress_4

R/W IPv4address




2.6.7.2 MO Class DHCPRelayServerGroup Counters

Table 11 MO class DHCPRelayServerGroup counters

Name Position


PacketsReceivedFromClients 1 PEG 0..264-1 The number of packets received from clients.

PacketsSentToClients 2 PEG 0..264-1 The number of packets sent to clients.

PacketsSentToServers 3 PEG 0..264-1 The number of packets sent to servers.

PacketsReceivedFromServers 4 PEG 0..264-1 The number of packets received from servers

PacketsFromClientsDiscarded 5 PEG 0..264-1 The number of packets from clients that werediscarded.

PacketsFromServersDiscarded

6 PEG 0..264-1 The number of packets from servers that werediscarded.

192/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.8 MO Class E1T1Interface (manuallyCreated)

MO class E1T1Interface represents attributes of an interface to an E1/T1communications medium. An E1/T1 interface is used to connect the SIU toa base station or other node. One E1T1Interface instance represents onephysical interface (port).

2.6.8.1 MO Class E1T1Interface Parameters

Table 12 MO class E1T1Interface parameters


RestartType

Description

instanceId RO Integer0..15

Instance identifier of the MO.The physical interfaces on the SIU are markedfrom 0 to 15. An MO E1T1Interface withinstanceId = "0" is connected to the physicalinterface 0, instanceId = "1" to interface 1, andso on.

Rule: An MO E1T1Interface instance is onlyallowed to be used by a single instance of eitherMO CESChannel, PPP, or SuperChannel.

operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details: No critical alarm exists on the MO.

"disabled": the resource is totally inoperable andunable to provide service to users.Details: Any of the "enabled" details are notfulfilled.

type R/W E1/T1/E1_30/E1_unframed

E1 mo Type of the interface, that is, "E1", "E1_30","E1_unframed" or "T1".

Rule: A mix is allowed on groups based on 4interfaces. The groups are formed based oninstanceId, that is:0–3, 4–7, 8–11, and 12–15.

Rule: All four links in a group must be either "E1or "T1".

20 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 12 MO class E1T1Interface parameters


RestartType

Description

transmitClockSource

R/W localTiming/loopTiming

localTiming "localTiming": the internal clock is used assynchronization source for outgoing synch onE1T1Interface.

"loopTiming": incoming E1/T1 digital loops arused as synchronization source for outgoingsynch on the E1T1Interface.

Rule: All MO E1T1Interface instances withina group must have the same value of attributtransmitClockSource. The groups are formedbased on instanceId, that is:0–3, 4–7, 8–11, and 12–15.

receiveClockSource

R/W timingReference/notUsed

notUsed "timingReference": the port can be selected aclock source for synchronization.

"notUsed": the port cannot be selected as closource for synchronization.

Rule: The value "notUsed" should be used wthe attribute transmitClockSource = "localTimi

Note: Only valid if attribute transmitClockSouis defined as "loopTiming"

loopbackMode R/W off/system/line

off "system": egress traffic is looped back as ingrtraffic (will not go to the external interface).

"line": ingress traffic is looped back as egresstraffic (will not reach the internal interface).

2.6.8.2 MO Class E1T1Interface Counters

No counters exist.

2.6.9 MO Class Equipment (systemCreated)

MO class Equipment represents the attributes for the SIU hardware. It isused to manage hardware identification properties. Only one instance of MOEquipment exists.

212/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.9.1 MO Class Equipment Parameters

Table 13 MO class Equipment parameters


RestartType

Description

instanceId RO Integer Instance identifier of the MO.Always set to "0" as only one instance of this MOexists.

serialNumber RO String(p)0..13

Serial number of the product, including factorycode.

productRevision RO String(p)3..7

Revision of the product.

productNumber RO String(p)0..24

Product number.

manufacturingDate

RO String(p)8..8

Manufacturing date of the product.

productName RO SIU02/TCU02

Specifies what HW platform that is used.

2.6.9.2 MO Class Equipment Counters

No counters exist.

2.6.10 MO Class EthernetInterface (manuallyCreated)

MO class EthernetInterface represents attributes of an interface to an Ethernetcommunications medium. An Ethernet interface is used to connect the SIU toa LAN or a WAN. One EthernetInterface instance represents one physicalinterface (port).

2.6.10.1 MO Class EthernetInterface Parameters

Table 14 MO class EthernetInterface parameters


RestartType

Description


Instance identifier of the MO.Can be set to any user defined string (1-20characters).

22 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details: No critical alarm exists on the MO.

"disabled": the resource is totally inoperable aunable to provide service to users.Details: Any of the "enabled" details are notfulfilled.

MAC_Address RO MACAddress

MAC address of the interface.

port R/W SFP/Gigabit/WANGigabit /WANFastEthernet/FastEthernet

Gigabit mo (1)Determines which physical port that is used wmultiple HW interfaces are connected to the salogical port. The first four ports (portNumber0-3) have two different HW connection interfacone optical ("SFP") and one electrical ("Gigab

Rule: "SFP" can only be used when the attribportNumber is "0", "1", "2" or "3".

Note: Use only values "SFP" and "Gigabit".For the electrical interfaces (0-7), use the valu"Gigabit"; for the optical interfaces (0-3) use tvalue "SFP".

Note: The values "WANGigabit","WANFastEthernet", and "FastEthernet"are deprecated values kept for backwardscompatibility only. These values are functionaequivalent to the value "Gigabit".

232/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

mode R/W AUTO/10MBithalfduplex/10MBitfullduplex/100MBithalfduplex/100MBitfullduplex/gigabit/gigabitfullduplex

AUTO mo (1) Mode in which the interface must communicate,in accordance with IEEE 802.

Rule: If attribute port = "SFP", only"AUTO", "gigabit", "gigabitfullduplex" or"100MBitfullduplex" are possible values.

Rule: The value "gigabitfullduplex" can only beused when port = "SFP".

Rule: Only "100Mbitfullduplex" and "gigabit" arenegotiated when used as SynchEthInterfaceand mode = "AUTO".

Rule: Only "AUTO", "gigabit", or"100Mbitfullduplex" are valid values whenused as SynchEthInterface.

Rule: Only slave mode is negotiated when usedas SynchEthInterface and mode = "AUTO".

Rule: Gigabit full duplex interface speed will besupported without auto negotiation when mode= "gigabitfullduplex". The physical interface isforced to operate in gigabit full duplex mode.

Note: If "AUTO" is used, mode will be negotiatedand interface speed agreed will be utilizedregardless of the value of the port attribute.

currentMode RO noMode/10MBithalfduplex/10MBitfullduplex/100MBithalfduplex/100MBitfullduplex/gigabit/gigabithalfduplex/gigabitfullduplex

Mode in which the interface currentlycommunicates, in accordance with IEEE 802.

24 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

portNumber R/W Integer0..7

0 mo (1) Defines which physical port that is used. Thevalue is an integer in the range 0-7.

Rule: The value must be unique among all MEthernetInterface instances.

sendLinkAlarmAllowed

R/W true/false

true Determines if Link Down alarms should be seor not.

depTrafficManager

R/W MO-DN <emptystring>

mo (1) Reference (use dependency) to the trafficmanager assigned for the MO EthernetInterfinstance.The value <empty string> means that no traffmanager is used for this MO EthernetInterfainstance.

Rule: The attribute depTrafficManager can onrefer to an instance of MO TrafficManager.

Rule: The attribute depTrafficManager referreto cannot be referred from any other MO.

flowControl RO off/rx/tx/rxtx

Determines if flow control (PAUSE frames)should be activated or not.

"off" = PAUSE frames are disabled."rx" = PAUSE frames are enabled in RX direct"tx" = PAUSE frames are enabled in TX direct"rxtx" = PAUSE frames are enabled in bothdirections.

Rule: When LinkOAM is activated on an MOEthernetInterface instance, flowControl mustset to "off".

(1) Change of attribute causes traffic impact for longer or shorter time.

2.6.10.2 MO Class EthernetInterface Counters


Table 15 MO class EthernetInterface counters

Name Position


ifHCInOctets 1 PEG 0..264-1 The total number of octets received on theinterface, including framing characters

252/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


ifHCOutOctets 2 PEG 0..264-1 The total number of octets transmitted on theinterface, including framing characters

ifInErrors 3 PEG 0..264-1 The number of inbound packets that containederror preventing them from being deliverableto higher-layer protocol

ifOutErrors 4 PEG 0..264-1 The number of outbound packets that could notbe transmitted because of errors.

ifHCInUcastPkts 5 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, which werenot addressed to a multicast or broadcastaddress at this sub-layer.

ifHCOutUcastPkts 6 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere not addressed to a multicast or broadcastaddress at this sub-layer, including those thatwere discarded or not sent.

ifInDiscards 7 PEG 0..264-1 The number of inbound packets which werechosen to be discarded even though no errorshad been detected to prevent their beingdeliverable to a higher-layer protocol.

One possible reason for discarding such apacket could be to free up buffer space.

ifOutDiscards 8 PEG 0..264-1 The number of outbound packets which werechosen to be discarded even though no errorshad been detected to prevent their beingtransmitted.


ifHCInBroadcastPkts 9 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, which wereaddressed to a broadcast address at thissub-layer.

ifHCOutBroadcastPkts 10 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere addressed to a broadcast address at thissub-layer, including those that were discardedor not sent.

26 2/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


ifHCInMulticastPkts 11 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, whichwere addressed to a multicast address at thissub-layer.

For a MAC layer protocol, this includes bothGroup and Functional addresses.

ifHCOutMulticastPkts 12 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere addressed to a multicast address at thissub-layer, including those that were discardedor not sent.

For a MAC layer protocol, this includes bothGroup and Functional addresses.

ifInUnknownProtos 13 PEG 0..264-1 The number of frames received, via theinterface, which were discarded because of aunknown or unsupported protocol.

2.6.11 MO Class HDLCPWEChannel (manuallyCreated)

MO class HDLCPWEChannel represents attributes for an HDLC Pseudo WireEmulation (PWE) transport.

Note: This feature is deprecated in software releases T11A and T11B.

2.6.11.1 MO Class HDLCPWEChannel Parameters

Table 16 MO class HDLCPWEChannel parameters


RestartType

Description


Instance identifier of the MO.Unique name identifying the HDLC PWE chan

272/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details:

• The MO referenced by attributedepE1T1Interface is created and enabled, and

• The MO referenced by attribute depIP_Interfaceis created and enabled, and

• The PWGW_IPAddress attribute is defined, and

• The PWGW_UDP_Port attribute is defined, and

• The STN_PWE_UDP_Port attribute is defined.

"disabled": the resource is totally inoperable andunable to provide service to user.Details: Any of the "enabled" details are notfulfilled.

depE1T1Interface

R/W Integer0..216-1

216-1 mo Instance number of an MO E1T1Interfaceinstance to which there is a use dependency.

Rule: The MO E1T1Interface instance must beof type = "E1" or "T1".

Rule: An MO E1T1Interface instance is onlyallowed to be used by one, and only one,instance of MO HDLCPWEChannel.

Rule: An MO E1T1Interface instance used byHDLCPWEChannel is not allowed to be used byany instance of MO PPP or SuperChannel.

Rule: 216-1 (notDefined) is not a valid value.

startTS R/W Integer1..31 (E1)/1..24 (T1)

24 mo The starting time slot.

channelSize R/W Integer1..31 (E1)/1..24 (T1)

1 mo The HDLC PWE channel size.

Number of E1 or T1 time slots used for this PWEchannel.

Rule: The sum of the values for startTS andchannelSize attributes must not exceed "32" forE1 and "25" for T1.

28 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

PWGW_IPAddress

R/W IPv4address

0.0.0.0 mo IP address of the PWGW node.

Rule: The combination of PWGW_IPAdress aPWGW_UDP_Port must be unique among alinstances of MO HDLCPWEChannel.

Rule: A valid PWGW_IPAddress attribute mube set, where "0.0.0.0" (notDefined) is not a vvalue.

PWGW_UDP_Port

R/W Integer0, 2000..60000

0 mo Number of the remote UDP port to be used foPWE.

Rule: The combination of PWGW_IPAdress aPWGW_UDP_Port must be unique among alinstances of MO HDLCPWEChannel.

Rule: A valid PWGW_UDP_Port must be setwhere "0" (notDefined) and odd numbers arevalid values.


mo Reference (use dependency) to the IP interfaassigned for PWE traffic.

When a change to the attribute IPAddress ofMO referred to, is committed, frames can be lduring change over.

Rule: Must be set to reference either an instaof MO IPInterface or VirtualIPInterface.

STN_PWE_UDP_Port

R/W Integer0, 2000..60000

0 mo Number of the local UDP port to be used forPWE.

Rule: The STN_PWE_UDP_Port attributemust be unique among all instances of MOHDLCPWEChannel.

Rule: A valid STN_PWE_UDP_Port must bewhere "0" (notDefined) and odd numbers arevalid values.

DSCP_PWE R/W Integer0..63

0 DSCP code for the PWE channel between thSIU and the PWGW.

292/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.11.2 MO Class HDLCPWEChannel Counters

Table 17 MO class HDLCPWEChannel counters

Name Position


inHDLCFrames 1 PEG 0..264-1 The number of HDLC frames, excluding errorframes, received uplink by the PWE channelon the E1/T1 interface.

outHDLCFrames 2 PEG 0..264-1 The number of HDLC frames handled by thePWE channel downlink. This includes bothframes sent to the HDLC application anddiscarded frames

inHDLCFramesErrors 3 PEG 0..264-1 The number of uplink HDLC frames lost due toerrors (for example CRC errors).

outHDLCFramesLost 4 PEG 0..264-1 The number of lost downlink HDLC framesdue to missing IP packet at reassembly afterIP fragmentation.

outHDLCFramesDiscarded 5 PEG 0..264-1 The number of discarded downlink HDLCframes due to overflow in the send buffer.

inHDLCOctets 6 PEG 0..264-1 The number of octets received in the HDLCframes on the E1/T1 interface, includingheader, CRC and flags, but excluding errorframes.

outHDLCOctets 7 PEG 0..264-1 The number of octets sent in the HDLC frameson the E1/T1 interface, including header, CRCand flags.

inIPPackets 8 PEG 0..264-1 The number of UDP packets received from thePseudoWire GateWay (PWGW) at the remotesite (downlink).

outIPPackets 9 PEG 0..264-1 The number of UDP packets sent to PWGW atthe remote site (uplink).

inIPPacketsLost 10 PEG 0..264-1 The number of lost UDP packet from PWGW(downlink) based on sequence numbers ofpackets.

inIPOctets 11 PEG 0..264-1 The number of UDP payload octets receivedfrom the PWGW at the remote site (downlink).

outIPOctets 12 PEG 0..264-1 The number of UDP payload octets sent to thePWGW at the remote site (uplink).

2.6.12 MO Class IPInterface (manuallyCreated)

MO class IPInterface represents attributes of an interface to an IP stack.

30 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.12.1 MO Class IPInterface Parameters

Table 18 MO class IPInterface parameters


RestartType

Description


Instance identifier of the MO.For backwards compatibility, use the value "0the "primary" WAN Ethernet port.

Rule: The maximum amount of IPInterface Minstances + defaultGateway (defined) is 256 (to the maximum number of IpRouteSys).

operationalState

RO enabled/disabled


If the MO referenced by depLinkLayer is not aMO VLAN:

• No critical alarm exists on the MO, and

• The MO referenced by depLinkLayer is creaand enabled, and

• The primaryIP_Address attribute is defined,

• The primarySubNetMask attribute is defined

If the MO referenced by depLinkLayer is a MOVLAN:


• The MO VLANGroup which is the parent ofMO referenced by depLinkLayer is created aenabled, and.

• The primaryIP_Address attribute is defined,

• The primarySubNetMask attribute is defined


312/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

primaryIP_Address

R/W IPv4address

0.0.0.0 mo (1)Primary IP address of the interface.

When the primaryIP_Address attribute valueis changed, all MO instances which have adepIP_Interface attribute that refers to thisinstance will be affected. For details about theeffects, see the depIP_Interface attribute for eachof the affected MOs.

The following depending MO may beaffected by changed value of this attribute:STN, TGTransport, PingMeasurement,Synchronization, and CESChannel.


primarySubNetMask

R/W IPv4subnetMask

0.0.0.0 mo (1) Subnet mask used by the IP interface, as set byoperator.

Note: For ML-PPP the primarySubNetMaskshould be set to "255.255.255.252" (/30). If youhave a larger network, you will not be able toreach other hosts than the remote peer of theML-PPP interface.


MTU R/W Integer68..1500

1500 The MTU of the IP interface, as set by operator.

32 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

defaultGateway R/W IPv4address

0.0.0.0 Default gateway used by the IP interface, as sby the operator.

Rule: Can only be defined for one MOIPInterface instance. For all other MOIPInterface instances it must be set to "0.0.0.(notDefined).

Rule: The value of defaultGateway cannot beIP address belonging to the SIU.

Note: This attribute is retained for backwardscompatibility only. Consider using an IpRouteinstance instead of configuring defaultGatewa

Note: When defaultGateway is configured,an IpRouteSys instance will be created bythe system to represent the route via thedefaultGateway. This route will not be monitoby connectivity check even if depCcConfig isconfigured.

ipDefaultTTL R/W Integer0..255

64 Default value inserted into the Time_To_Livefield of the IP header of datagrams originatedthis entity, whenever a TTL value is not supplby the transport layer protocol.

trustDSCP R/W truefalse

true Defines whether the DSCP field of ingressdatagrams shall be trusted or not.

Note: For all traffic originated in the SIU, thevalue of the trustDSCP attribute is "true" andcannot be changed.

Note: trustDSCP is configured on MOIPInterface instances, but it acts at the ingresphysical port.

Rule: All MO IPInterface instances that areconnected (directly or via a VLAN) to the samMO EthernetInterface instance, must have thsame value for trustDSCP.

Rule: All MO IPInterface instances that areconnected to different MO ML-PPP instancesmust have the same value for trustDSCP.

332/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depLinkLayer R/W MO-DN STN=0,EthernetInterface=0

mo (1) Reference (use dependency) to the link layerassigned for the MO IPInterface instance.

Rule: The depLinkLayer attribute can onlyrefer to an instance of MO ML-PPP, VLAN orEthernetInterface.

Rule: Must not refer to the same link layer asthe depLinkLayer attribute of a MO VLANGroupinstance.

Rule: The IPInterface can reference anEthernetInterface or VLAN instance. A hybridconfiguration where some IPInterface instancesare directly connected to an EthernetInterfaceinstance and some IPInterface instances areconnected to the same EthernetInterface via aVLAN instance is not allowed.

Rule: The depLinkLayer attribute cannot refer toan instance of MO VLAN that has a non-emptydepBridge attribute value.

depTrafficManager


mo (1) Reference (use dependency) to the trafficmanager assigned for the MO IPInterfaceinstance.The value <empty string> means that no trafficmanager is used for this MO IPInterfaceinstance.

Rule: The depTrafficManager attribute can onlyrefer to an instance of MO TrafficManager.

Rule: If depTrafficManager is in use, anddepLinkLayer refers to an instance of MOVLAN, then all other MO IPInterface instancesreferring to MO VLAN instances on the sameMO EthernetInterface must refer to the sameinstance of MO TrafficManager.

depDHCPRelayServerGroup

R/W String(m)0..20

<emptystring>

mo (1) Instance id (use dependency) of an associatedMO DHCPRelayServerGroup instance.

depACL R/W MO-DN <emptystring>

mo (1) Reference (use dependency) to an instance ofMO AccessControlList. The ACL is used tofilter traffic on the interface.

Rule: Can refer to an instance of MOAccessControlList or contain <empty string>.

34 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depCcConfig R/W MO-DN <emptystring>

Reference (use dependency) to a ConnectivitCheck configuration.

Rule: The depCcConfig attribute must refer tan instance of MO CcBFDConfig or be equato <empty string>.

Rule: The depCcConfig attribute must beequal to <empty string> if the depLinkLayerattribute does not refer to an instance of MOEthernetInterface or VLAN.

Rule: When the depCcConfig attribute is notequal to <empty string>, connectivity checkis enabled and will monitor all instances ofMO IpRoute or IpRoutePbr that refer tothis IPInterface instance. Each individualIpRoute or IpRoutePbr instance can disableconnectivity check monitoring by using thedisableConnectivityCheck attribute.

Rule: When the depCcConfig attribute is equto <empty string>, connectivity check on thisinterface is disabled. The setting of the attribudisableConnectivityCheck on any IpRouteor IpRoutePbr instance that refers to thisIPInterface instance will be disregarded.

depRoutingPolicy


Reference (use dependency) to a Routing Poconfiguration.

Rule: Must refer to an instance of MORoutingPolicy or be equal to <empty string>

holdDownTimer R/W Integer0..300

0 The desired hold-down interval. The hold-dowinterval is the interval (in seconds) after the linlayer transitions from "down" to "up", until anystatic routes and policy based routes that useinterface will be reactivated.

Note: The link layer state may not be equal tthe linkLayer operationalState.


352/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.12.2 MO Class IPInterface Counters

Note: Reset counters at node restart. Reset of all counters, for dependingMOs belonging to the EthernetInterface except EthernetInterfacecounters, will also be performed when switching between layer 3 andlayer 2 (see also VLAN).

Table 19 MO class IPInterface counters

Name Position


ipIfStatsHCInReceives 1 PEG 0..264-1 The total number of input IP datagramsreceived, including those received in error.

ipIfStatsInHdrErrors 2 PEG 0..264-1 The number of input IP datagrams discardeddue to errors in their IP headers, includingversion number mismatch, other format errors,hop count exceeded, errors discovered inprocessing their IP options, and so on.

ipIfStatsInAddrErrors 3 PEG 0..264-1 The number of input IP datagrams discardedbecause the IP address in their IP header'sdestination field was not a valid address to bereceived at this entity. This count includesinvalid addresses (for example ::0). For entitiesthat are not IP routers and therefore do notforward datagrams, this counter includesdatagrams discarded because the destinationaddress was not a local address.

ipIfStatsInUnknownProtos 4 PEG 0..264-1 The number of locally addressed datagramsreceived successfully but discarded because ofan unknown or unsupported protocol.

ipIfStatsHCInDelivers 5 PEG 0..264-1 The total number of input datagramssuccessfully delivered to IP user-protocols(including ICMP).

ipIfStatsInDiscards 6 PEG 0..264-1 The number of input IP datagrams for whichno problems were encountered to preventtheir continued processing, but which werediscarded (for example for lack of buffer space).

Note: This counter does not includeany datagrams discarded while awaitingre-assembly.

ipIfStatsHCOutRequests 7 PEG 0..264-1 The total number of IP datagrams which localIP user_protocols (including ICMP) supplied toIP in requests for transmission.

36 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 19 MO class IPInterface counters

Name Position


ipIfStatsOutDiscards 8 PEG 0..264-1 The number of output IP datagrams for whichno problem was encountered to prevent theirtransmission to their destination, but whichwere discarded (for example for lack of bufferspace).

ipIfStatsHCInOctets 9 PEG 0..264-1 The total number of octets received in inputIP datagrams, including those received inerror. Octets from datagrams counted inipIfStatsInHCReceives MUST be counted her

ipIfStatsHCOutTransmits 10 PEG 0..264-1 The total number of IP datagrams that this entisupplied to the lower layers for transmission.

ipIfStatsHCOutOctets 11 PEG 0..264-1 The total number of octets in IP datagramsdelivered to the lower layers for transmission.

ipIfStatsHCInForwDatagrams 12 PEG 0..264-1 The number of input datagrams for which thisentity was not their final IP destination and fowhich this entity attempted to find a route toforward them to that final destination.

ipIfStatsHCOutForwDatagrams

13 PEG 0..264-1 The number of datagrams for which this entitywas not their final IP destination and for whichthis entity was successful in finding a path totheir final destination.

ipIfStatsInNoRoutes 14 PEG 0..232-1 The number of input IP datagrams discardedbecause no route could be found to transmitthem to their destination.

2.6.13 MO Class IpRoute (manuallyCreated)

MO class IpRoute represents attributes for one IP route in the IP routing table.MO IpRoute is contained in the MO class RoutingTable

2.6.13.1 MO Class IpRoute Parameters

Table 20 MO class IpRoute parameters


RestartType

Description



372/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

Active RO true/false

This MO IpRoute instance is active when thecorresponding IPInterface has operationalState= "enabled" and any corresponding connectivitycheck session indicates that the next hop isreachable.

destIpSubnet R/W IPv4addressRange

0.0.0.0/0 mo (1)The destination IP subnet that is reachableaccording to this MO IpRoute instance.

Note: If instances of MO IpRoute or IpRouteSyshave overlapping destIpSubnet the longest prefixmatching has priority.

Note: If two instances of MO IpRoute orIpRouteSys have identical destIpSubnet and thesame admDistance, only one will be used by thesystem.

Rule: 0.0.0.0/0 (notDefined) is not a valid value.

nextHopIpAddress

R/W IPv4address

0.0.0.0 mo (1) The IP address of the next-hop router for this IProute.

Rule: The value of nextHopIpAddress cannot bean IP address belonging to the SIU.

Note: The attribute value must be within exactlyone of the subnets defined by an instance of MOIPRouteSys.

Otherwise the IpRoute instance will have theattribute Active = "false".


forwardingInterface


The egress interface for traffic forwardedaccording to this IpRoute. The attribute currentlyonly has an informational purpose.

Note: This attribute will be updated to show theinterface that nextHopIpAddress is connectedto. If nextHopIpAddress is not within one ofthe subnets defined by an instance of MOIpRouteSys, forwardingInterface will be set to<empty string>.

38 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

routeType RO Static/Connected/Default

Static Just for information in the routing table listingCan only have value "Static"

admDistance R/W Integer0..64

1 mo (1) The relative distance to the destination whenusing this route.

disableConnectivityCheck

R/W true/false

false Indicates whether connectivity check for thisroute is disabled.

Note: If this attribute has the value "false",this route will be monitored by connectivitycheck, provided that the depCcConfig on theIPInterface instance referred to by attributeforwardingInterface refers to a connectivity chconfiguration.

If this attribute has the value "true", this routewill not be monitored by connectivity check,even when connectivity check is enabled on tforwardingInterface.


2.6.13.2 MO Class IpRoute Counters

No counters exist.

2.6.14 MO Class IpRoutePbr (manuallyCreated)

MO class IpRoutePbr is contained in MO class RoutingTable. MO classIpRoutePbr represents attributes for an IPv4 static route used in Policy BasedRouting. MO IpRoutePbr instances are used exclusively for Policy BasedRouting and are not included in the IPv4 routing table of the SIU.

2.6.14.1 MO Class IpRoutePbr Parameters

Table 21 MO class IpRoutePbr parameters


RestartType

Description



392/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 21 MO class IpRoutePbr parameters


RestartType

Description

active RO true/false

This MO IpRoutePbr instance is active when thecorresponding IPInterface has operationalState= "enabled" and any corresponding connectivitycheck session indicates that the next hop isreachable.

nextHopIpAddress

R/W IPv4address

0.0.0.0 mo The IP address of the next-hop router for this IProute.

Rule: The attribute value must be within exactlyone of the subnets defined by the attributesprimaryIP_Address and primarySubNetMask ofan MO IPInterface.

forwardingInterface

RO MO-DN The egress MO IPInterface instance for trafficforwarded according to this MO IpRoutePbrinstance.

The forwardingInterface contains a reference tothe instance of MO IPInterface under which thesubnet exists that nextHopIpAddress belongs to.

disableConnectivityCheck

R/W true/false

false Indicates whether connectivity check for thisroute is disabled.

Note: If this attribute has the value "false", thisroute will be monitored by connectivity check,provided that the depCcConfig on the egressMO IPInterface instance referred to by attributeforwardingInterface refers to a connectivity checkconfiguration.

If this attribute has the value "true", this route wilnot be monitored by connectivity check, evenwhen connectivity check is enabled on the egressMO IPInterface instance.

2.6.14.2 MO Class IpRoutePbr Counters

No counters exist.

2.6.15 MO Class IpRouteSys (systemCreated)

MO class IpRouteSys represents attributes for one system related IProute in the IP routing table. MO IpRouteSys is contained in the MO classRoutingTable

40 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.15.1 MO Class IpRouteSys Parameters

Table 22 MO class IpRouteSys parameters


RestartType

Description



Active RO true/false

This instance of MO IpRouteSys is active whthe corresponding MO IPInterface instance isenabled.

destIpSubnet RO IPv4addressRange

The destination IP subnet that is reachableaccording to this MO IpRouteSys instance.

nextHopIpAddress

RO IPv4address

If attribute routeType = "connected": IP addreof the MO IPInterface instance that this systecreated IP route describes.

If attribute routeType = "default": the configurdefaultGateway IP Address.

Note: This system created IP route willnot be monitored by connectivity check,even if connectivity check is enabled on theforwardingInterface.

forwardingInterface

RO MO-DN The egress interface for traffic forwardedaccording to this system created IP route.

routeType RO Static/Connected/Default

"Connected" is used for the IPInterface MOsare currently defined."Default" is used for the default gateway (ifdefined).

admDistance RO Integer0..1

The relative distance to the destination whenusing this system created IP route.Will be "0" for routeType = "connected" and "for routeType = "default".

2.6.15.2 MO Class IpRouteSys Counters

No counters exist.

2.6.16 MO Class LinkOAM (manuallyCreated)

MO class LinkOAM attached to EthernetInterface when LinkOAM is activated.

412/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.16.1 MO Class LinkOAM Parameters

Table 23 MO class LinkOAM parameters


RestartType

Description



activatedFeatures

R/W NONE/RLB_LE

NONE mo There are 4 LinkOAM features (RemoteLoopback, Unidirectional mode, Link Events andVariable retrieval). Currently, the SIU supportsnone of them, but will in later releases.

RLB_LE activates both the Remote Loopbackand Link Events features.

discoveryState RO FAULT_STATE/ACTIVE_SEND_LOCAL/PASSIVE_WAIT/SEND_LOCAL_REMOTE/SEND_LOCAL_REMOTE_OK/SEND_ANY

The current state of the Link OAM Discoveryprocess.

dteMode R/W PASSIVE/ACTIVE

PASSIVE mo Both "PASSIVE" and "ACTIVE" DTE mode issupported.

remoteDteInfo RO String(p)1..34

The first four bytes Vendor specific informationfollowed by the MAC address of the remote peerusing the following format:

"VSI:B1 B2 B3 B4MAC:XXXX.XXXX.XXXX"

maxPduRate R/W Integer1..10

10 Specifies the maximum OAMPDU rate(PDUs/second) for the particular Ethernetinterface.

Note: The minimum OAMPDU rate is always seto 1 PDU/second.

42 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.16.2 MO Class LinkOAM Counters

Table 24 MO class LinkOAM counters

Name Position


oamPduTransmitted 1 PEG 0..232-1 The total number of OAM PDUs transmitted.

oamPduReceived 2 PEG 0..232-1 The total number of OAM PDUs received.

2.6.17 MO Class LocalConnect (manuallyCreated)

MO class LocalConnect represents attributes of the Abis Local Connectivity(ALC) function. ALC is used to directly connect the speech path of two ends ofthe same call. Only one LocalConnect instance can be created.

2.6.17.1 MO Class LocalConnect Parameters

Table 25 MO class LocalConnect parameters


RestartType

Description



operationalMode

R/W monitor/enable

monitor Sets the operational mode of the ALC functioeither"monitor" mode (in order to only collectperformance management statistics) or"enable" mode (to switch calls locally).

codecPriorityList

R/W String(m)0..50

<emptystring>

Comma separated list of prioritized codecs. Vcodec list elements are: FR, EFR, HR, AMRFAMRHR and AMRWB. The most prioritized costarts the list whilst the least prioritized codecends the list. An <empty string> indicates nocodec preferences and this implicitly turn off tcodec matching functionality within the SIU no

tagModeConnMsgConnSA

R/W enabled/disabled

enabled Sets the tagging mode for tagging using 3GPTS 24.008 Connect message, InformationElement Connected Sub Address.

This tagging mode requires that the core netwrelays the IE Connected Sub Address withoudoing any modifications to the IE. At least onethe three tagging methods needs to be enablein order to have a working local switching feat

432/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 25 MO class LocalConnect parameters


RestartType

Description

tagModeSetupMsgUU


disabled Sets the tagging mode for tagging using 3GPPTS 24.008 Setup message, information ElementUser-User.

This tagging mode requires that the core networkrelays the IE User-User without doing anymodifications to the IE. At least one of the threetagging methods needs to be enabled to have aworking local switching feature.

tagModeSetupMsgCallSA


disabled Sets the tagging mode for tagging using 3GPPTS 24.008 Setup message, Information ElementCalling Sub Address.

This tagging mode requires that the core networkrelays the IE Calling Sub Address without doingany modifications to the IE. At least one of thethree tagging methods needs to be enabled inorder to have a working local switching feature.

observedTransmissionMode

RO terrestrial/satellite

Indicates if the Abis Upper connection is basedupon "terrestrial" or "satellite" transmission.

2.6.17.2 MO Class LocalConnect Counters

Table 26 MO class LocalConnect counters

Name Position


totalMoCalls 1 PEG 0..232-1 The number of all MO (Mobile Originated) callshandled by the SIU. Triggered when a Connectmessage is sent to a MS.

totalMtCalls 2 PEG 0..232-1 The number of all MT (Mobile Terminated) callshandled by the SIU. Triggered when a Connectmessage is sent from a MS.

totalLocalCalls 3 PEG 0..232-1 In ALC operationalMode "enabled": the numberof calls switched locally in the SIU.

In ALC operationalMode "monitor": the numberof candidate calls for local switching if theoperational mode would have been enabled.

44 2/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


handoverMaintained 4 PEG 0..232-1 In ALC operationalMode "enabled": the numbeof handovers within the SIU, that is, localswitching before and after the handover.

In ALC operationalMode "monitor": the numbeof handovers where local switching would havbeen possible if operational mode had beenenabled.

handoverOut 5 PEG 0..232-1 The number of handovers where local switchinis not maintained due to that the SIU is notable to match the target channel to one of thehandled target channels.

Note: This counter will also be updated forcases where the handover is within the SIUsite but the SIU lack information to identify thetarget channel.

handoverTotal 6 PEG 0..232-1 The total number of handovers forlocally switched calls. Triggeredwhen a HandoverCommand or anAssignmentCommand are sent to a MSinvolved in a locally switched call.

callsAccumulator 7 PEG 0..232-1 The callsAccumulator and callsScan countersare used to calculate the amount of calls, thatthe number of Erlang that are locally switchedThose counters are not event-driven as theother counters, but instead every 10th secondthe following pseudo-code is executed:ACCUMULATOR += number of call endscurrently being locally switchedSCAN +=1

Average Erlang is then calculated(manually or by OSS, not by the SIU)as a callsAccumulator/callsScan.

452/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


callsScan 8 PEG 0..232-1 The callsAccumulator and callsScan countersare used to calculate the amount of calls, that isthe number of Erlang that are locally switched.Those counters are not event-driven as theother counters, but instead every 10th secondthe following pseudo-code is executed:ACCUMULATOR += number of call endscurrently being locally switchedSCAN +=1

Average Erlang is then calculated(manually or by OSS, not by the SIU)as a callsAccumulator/callsScan.

suspendedOther 9 PEG 0..232-1 The number of calls where local switching haspermanently been suspended for any otherreason than handover out from the SIU site.For example, local switching is permanentlysuspended for a call at detection of eventssuch as call related supplementary services.

localSwitchedData 10 PEG 0..264-1 The total amount of octets (bytes) that areswitched locally. This counter is not updated inALC operationalMode "monitor".

2.6.18 MO Class LocalMEP (manuallyCreated)

MO class LocalMEP represents the SIUs own MEG End Point (MEP) withina Maintenance Entity Group (MEG).

2.6.18.1 MO Class LocalMEP Parameters

Table 27 MO class LocalMEP parameters


RestartType

Description



mepId R/W Integer1..8191

1 mo A MEP ID identifying a specific Maintenanceassociation End Point specified as an integer thais unique among all the MEPs in the same MEG.

Rule: The mepId must be unique in the MEG.

46 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 27 MO class LocalMEP parameters


RestartType

Description

depAttachmentPoint


mo Reference to an attachment point for the MOLocalMEP instance.

Rule: Must be an instance of MO VLAN.

Rule: It is not allowed to have twomaintenanceAssociation on the samelevel attached to MO VLAN instances whereattribute tagValue is the same.

pcpCcm R/W Integer0..7

7 The PCP priority value for CCMs transmittedthe MEP.

ccmTransmission

R/W enable/disable

enable If set to "enable" the MEP will generate CCMmessages.

alarmAllowed R/W true/false

false If set to "true", and the alarm condition isfulfilled (any of the defects bDefRdiCcm,bDefRemoteCcm, bDefErrorCcm, orbDefXconCcm is present) the MEP is allowedraise an alarm.

bDefRdiCcm RO true/false

Defect. A RemoteMEP is reported the RDI biits last CCM.

bDefRemoteCcm

RO true/false

Defect. The MEP is not receiving valid CCMsfrom at least one of the RemoteMEPs.

bDefErrorCcm RO true/false

Defect. The MEP has received at least oneinvalid CCM whose CCM Interval has not yettimed out.

bDefXconCcm RO true/false

Defect. The MEP has received at least one Cfrom either another MEG ID or a lower MEGLevel.

2.6.18.2 MO Class LocalMEP Counters

Table 28 MO class LocalMEP counters

Name Position


sequenceErrorsCcm 1 PEG 0..232-1 The total number of out-of-sequence CCMsreceived from all RemoteMEPs.

cciSentCcms 2 PEG 0..232-1 The total number of Continuity Checkmessages transmitted.

loopbackRepliesIn 3 PEG 0..232-1 The total number of valid, in-order LoopbackReplies received.

472/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 28 MO class LocalMEP counters

Name Position


loopbackRepliesInOutOfOrder 4 PEG 0..232-1 The total number of valid, out-of-orderLoopback Replies received.

loopbackRepliesBadMacServiceDataUnit

5 PEG 0..232-1 The total number of Loopback Repliesreceived whose mac_service_data_unit didnot match (except for the OpCode) that of thecorresponding LBM (20.2.3).

linktraceInUnExp 6 PEG 0..232-1 The total number of unexpected LTRs received.

loopbackRepliesOut 7 PEG 0..232-1 The total number of Loopback Repliestransmitted.

2.6.19 MO Class ManualSAPair (manuallyCreated)

MO class ManualSAPair (Manual Security Association Pair) is containedin the MO Security and corresponds to a pair of manually created SecurityAssociations (SAs), one for inbound and one for outbound traffic. Eachmanually created SA pair belongs to a certain policy with policyAction set to"protect".


2.6.19.1 MO Class ManualSAPair Parameters

Table 29 MO Class ManualSAPair parameters


RestartType

Description



saAutAlg R/W hmac-sha-1/null

hmac-sha-1 Authentication algorithm.

Rule: Authentication (saAutAlg) and encryption(saEAlg) must not use the "null" algorithm at thesame time.

saAutKey WO String(h)0/40

<emptystring>

Authentication key represented as a hexadecimastring.

Rule: If saAutAlg = "null", then saAutKey mustbe <empty string>. If saAutAlg = "hmac-sha-1",then length must be "40".

48 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

saEAlg R/W aes/3des/null

3des Encryption algorithm.

Rule: Authentication (saAutAlg) and encryptio(saEAlg) must not use the "null" algorithm at tsame time.

saEKey WO string(h)0/32/48

<emptystring>

Encryption key represented as a hexadecimastring.

Rule: If saEAlg = "aes", then saEKey length mbe "32". If saEAlg = "3des", then saEKey lengmust be "48". If saEAlg = "null", then saEKeymust be <empty string>.

saSPIIn R/W Integer0, 256..231

�1

notDefined Security Parameters Index for the inbound SAnotDefined is indicated by value 0. Value ran231�(232

�1) is reserved for future use.

Rule: notDefined is not a valid value.

Rule: saSPIIn values must be unique and nointerfere with saSPIOut values in the site node

saSPIOut R/W Integer0, 256–231

�1

notDefined Security Parameters Index for the outbound SnotDefined is indicated by value 0. Value ran231�(232

�1) is reserved for future use.

Rule: notDefined is not a valid value.

Rule: saSPIOut values must be unique and ninterfere with saSPIIn values in the site node.

492/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depSA_TunnelLocalInterface


Reference (usage dependency) to the IP interfaceassigned for an IPsec tunnel towards the securitygateway (saTunnelRemote). Implicitly thereference also gives the local IP address (of theouter IP header) to use for communication withthe security gateway.

When a change of this attribute or the IP addressattribute of the MO referred to, is commited, thenthe tunnel interface will be reconfigured to usethe new IP address.

Rule: The depSA_TunnellocalInterface must bean instance of one of the MO classes IPInterfaceor VirtualIPInterface.

Rule: <empty string> is not a valid value.

saTunnelRemote

R/W IPv4address

0.0.0.0 IP destination address for the IPsec tunnel outerIP header, that is, the IP address for the remotesecurity gateway.


2.6.19.2 MO Class ManualSAPair Counters

No counters exist.

2.6.20 MO Class MeasuredMOClass

MO class MeasuredMOClass represents attributes for the MO class beingmeasured. Each MeasuredMOClass instance contains a set of counters beingmeasured (MO MeasurementCounters).

2.6.20.1 MO Class MeasuredMOClass Parameters

Table 30 MO class MeasuredMOClass


RestartType

Description

instanceId N/A Integer0..216

�1Instance identifier of the MO.

measuredMO N/A String1..1024

MO class name of the instance monitored.

50 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.20.2 MO Class MeasuredMOClass Counters

No counters exist.

2.6.21 MO Class MeasurementCounters

MO class MeasurementCounters represents attributes for a counter beingmeasured. Each MeasurementCounters instance corresponds to one counter.

2.6.21.1 MO Class MeasurementCounters Parameters

Table 31 MO class MeasurementCounters parameters


RestartType

Description

instanceId N/A Integer0..216

�1Instance identifier of the MO.

Counter N/A String1..64

The name of the counter attribute, to bemeasured.

counterPosition N/A Integer1..32

Specifies the position in the data file of themeasurement report.

2.6.21.2 MO Class MeasurementCounters Counters

No counters exist.

2.6.22 MO Class MeasurementDefinition (systemCreated)

MO class MeasurementDefinition represents attributes for a measurementjob. The measurement results are collected in PM Measurement Result ReportFiles. Each MeasurementDefinition instance contains a set of MOs beingmeasured (MO MeasuredMOClass).

2.6.22.1 MO Class MeasurementDefinition Parameters

Table 32 MO class MeasurementDefinition


RestartType

Description

instanceId RO Integer 0 Instance identifier of the MO.

neIndex R/W Integer0..216

�10 no(1)

Network element index.

512/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 32 MO class MeasurementDefinition


RestartType

Description

filePrefix RO String(m)0..32

STN Prefix used in filenames for uploaded files.

granularityPeriod

RO 15 15 Number of minutes between the initiations of twosuccessive gatherings of measurement data.

reportPeriod R/W 15 60 no (1) Number of minutes between measurement reporuploads.

measurementActive

RO true/false

"true" if measurement reporting is activated.

(1) When this attribute is changed the resumePMMeasurements command must be executed to make it valid inthe PM measurements.

2.6.22.2 MO Class MeasurementDefinition Counters

No counters exist.

2.6.23 MO Class MEG (manuallyCreated)

MO class MEG represents a MEF 20 style Maintenance Entity Group (MEG).

2.6.23.1 MO Class MEG Parameters

Table 33 MO class MEG parameters


RestartType

Description



52 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

maintenanceDomainType

R/W no-name/dns-based/mac/character-string

no-name mo The Maintenance Domain can be specified eitby dns, mac or a character string.

"no-name" = No format specified, usuallybecause there is not (yet) a MaintenanceDomain. In this case, a zero-length OCTETSTRING for the Domain field is acceptable.

"dns-based" = (String(p) 1..43). Domain Namlike string, globally unique text string derived fa DNS name.

"mac" = MAC address + 2-octet (unsigned)integer. This MAC address will be displayed aMacaddress with "dot" as separation then the2-octets if these are not present SIU presets tas "0", example 12:23:34:45:67:78.0

"character-string" = (String(p) 1..43). RFC 25(Reference [14]) DisplayString, except that thcharacter codes 0-31 (decimal) are not used.

maintenanceDomain

R/W String(p)0..43

<emptystring>

mo Rule: If the attribute maintenanceDomainTypis set to:"no-name" this attribute should be <emptystring>;"dns-based" this attribute must have a formataccording to the DNS;"mac" this attribute must be a MAC address;"character-string" any string is allowed.

Rule: If attribute maintenanceDomainType isto "dns-based" the DNS name must be specifas in RFC 1035 (Reference [13]).

Rule: The maintenanceDomain attribute musunique for each MEG instance.

Rule: If attribute maintenanceDomainType is"no-name" the length of maintenanceDomainthe length of maintenanceAssociation shall beat most 44 and the maintenanceDomain lengmust be greater than or equal to 1.

532/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

maintenanceAssociationType

R/W primary-vid/string/integer

string mo The maintenanceAssociationType (MaintenanceAssociation; IEEE term for MEG) can be specifiedas "primary-vid" (vid = VLAN ID), "string", and"integer". This name must be unique within amaintenance domain.

"primary-vid" = Integer 0..4094.

"string" = String(p) 1..45.

"integer" = Integer 0..65535.

maintenanceAssociation

R/W String(p)1..45

<emptystring>

mo Rule: If attribute maintenanceAssociationTypeis set to:"primary-vid" this attribute should be VLAN IDspecified as an integer;"string" this attribute must be a string;"integer" this attribute must be an integer.

Note: If attribute maintenanceDomainType isnot "no-name" the length of maintenanceDomain+ the length of maintenanceAssociation shall beat most 44 and the maintenanceDomain lengthmust be greater than or equal to 1.

Note: It is not allowed to have two MEGs on thesame level where the underlying LocalMEPshave attribute depAttachmentPoint pointing toMO VLAN instances where attribute tagValue isthe same.

megType R/W Subscriber-MEG/UNI-MEG

Subscriber-MEG

mo The type of the MEG, either a "Subscriber-MEG"or a "UNI-MEG" (Link Level Service OAM).

Note: It is only possible to set attributeccmInterval to "3.33ms" if the attribute megTypeis "UNI-MEG".

54 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

ccmInterval R/W 3.33ms/10ms/100ms/1s/10s/1min/10min

1s The CCM (Continuity Check Message) intervabe used within the MEG.

Rule: It is only possible to set attributeccmInterval to "3.33ms" if the attribute megTyis "UNI-MEG".

level R/W Integer0..7

6 mo Thelevel is a mandatory attribute to indicate tnesting relationship between various MEGs.The level is embedded in each of the serviceOAM frames. Messages with a given level arprocessed by MEPs at the same level.

Rule: If a new maintenanceAssociation iscreated that is associated with an already presmaintenanceDomain the attribute level must bset to the same value (maintenanceDomain alevel are coupled).

Note: For "UNI-MEG" it is recommended to hMEG level at "0".

Note: It is not allowed to have twomaintenanceAssociation on the same levelattached to MO VLAN instances where attributagValue is the same.

2.6.23.2 MO Class MEG Counters

No counters exist.

2.6.24 MO Class ML-PPP (manuallyCreated)

MO class ML-PPP represents attributes for a multilink Point-to-Point Protocol(PPP) communication medium. ML-PPP is used to get an IP connection overa bundle of PPP links using E1/T1 physical lines. One ML-PPP instancerepresents a group of PPP links.

Note: If only one PPP link is defined, then the setting of the attributes startTSand endTS in MO PPP will cause a MO restart of the ML-PPP bundlewith a consequent reset of ML-PPP counters.

552/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.24.1 MO Class ML-PPP Parameters

Table 34 MO class ML-PPP parameters


RestartType

Description


Instance identifier of the MO.A unique name used to identify the ML-PPPbundle.

Rule: The MO ML-PPP instance cannot existunless an MO IPInterface instance, having adepLinkLayer attribute referring to the ML-PPPinstance, is created in the same session.

operationalState

RO enabled/disabled



• At least one MO PPP instance is created andenabled, and

• The attribute mlpppBundleStatus has the value"up".

"disabled": the resource is totally inoperable andunable to provide service to the user.Details: Any of the "enabled" details are notfulfilled.

mlpppBundleStatus

RO up/down/lost

Status of ML-PPP bundle according to:

"up": Connection has been established.

"down": Connection has never been establishedsince last reset.

"lost": Connection has been established sincelast reset, but is currently not established.

MRRU R/W Integer68..16383

1500 The MRRU(1) of the ML-PPP bundle. Defines thelargest packet size that the node may receive asset by the operator.

Note: MRRU should be greater than or equal tothe MTU of the peer node.

negotiatedMRRU

RO Integer0..216-1

The ML-PPP router's MRRU after negotiation.

56 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

pppLinkStatusInterval

R/W Integer0..50

10 Interval in tenth of seconds for time betweeninitiating checks of the PPP-link status in abundle by using Link Control Protocol (LCP)Echo-Request.

Rule: Usethe value "0" to indicate that the linstatus check is turned off.

pppLinkRetriesEcho

R/W Integer1..10

2 The number of non-acknowledged consecutivLCP echo requests before the link is to beconsidered dead.

pppLinkRetriesFrequency

R/W Integer5..50

5 Interval in tenth of seconds for time betweenpppLinkRetriesEcho.

pppLinkEstablishmentInterval

R/W Integer5..50

5 Interval in tenth of seconds for time betweenreattempts to establish a PPP link connection

pppLinkEstablishmentRetries

R/W Integer1..10

2 The number of consecutive link establishmenrequests before the link is to be considered de

addrControlFieldComp

R/W on/off

on Controls whether ACFC(2) is negotiated with tpeer ML-PPP router.

If the attribute is set to "off", the SIU will not trnegotiate ACFC.

protocolFieldComp

R/W on/off

on Controls whether PFC(3) is negotiated with thpeer ML-PPP router.

If the attribute is set to "off", the SIU will not tto negotiate PFC.

IPHCEnable R/W on/off

off Controls whether IP Header Compression (IPis negotiated with the peer ML-PPP router orIf the attribute is set to "off", the SIU will not tto negotiate IPHC.

Rule: Only one instance of MO ML-PPP canhave IPHC enabled.

572/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

IPHCStatus RO IPHCDisabled/IPHCNegSuccess/IPHCNegFail_NON_TCP_SPACE/IPHCNegFail_PeerReject

Status after IP header compression negotiation.Shows the result of the negotiation:

"IPHCDisabled": Negotiation succeededwithout IP header compression enabled in bothdirections.

"IPHCNegSuccess": IP header compressionnegotiation succeeded.

"IPHCNegFail_NON_TCP_SPACE": IP headercompression negotiation failed. The SIU andpeer router could not agree on a value forNON_TCP_SPACE.

"IPHCNegFail_PeerReject": IP headercompression negotiation failed. Peer routerrejected IP header compression duringnegotiation.

IPHC_F_MAX_PERIOD

R/W Integer1..1000

256 The maximum number of compressed packetsbetween sending of full headers. See section 2.1in RFC 3544 (Reference [9]).

IPHC_F_MAX_TIME

R/W Integer1..255

5 The maximum time (in seconds) betweensending of full headers. See section 2.1 in RFC3544 (Reference [9]).

IPHC_NON_TCP_SPACE

R/W Integer0..1023

1023 The only value requested and accepted during IPheader compression negotiation of a maximumcontext identifier in the space of context identifiersallocated for non-TCP. The value "0" implieshaving one context. See section 2.1 in RFC 3544(Reference [9]).

fragmentationThreshold

R/W Integer64..1506

1506 Max fragment size that is transmitted over thelink. This includes the information field and anypadding; but not the protocol (ML PID), address,control or FCS fields.

Note: If set greater than or equal to IP MTU+6,fragmentation will not occur

primaryDNS R/W IPv4address

0.0.0.0 This address is sent to the peer when requestedduring IPCP

secondaryDNS R/W IPv4address

0.0.0.0 This address is sent to the peer when requestedduring IPCP

58 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

negotiatedPeerIPAddress

RO IPv4address

The IP address negotiated for the ML-PPP peduring IPCP. Will be "0.0.0.0" if no address isnegotiated.

endpointDiscriminator

R/W localAddress/ipAddress

localAddress

If value is "localAddress", the STN_Nameattribute will be used. If value is "ipAddress",ML-PPP interface IP address will be used.

nullFragmentBurstsPeriod

R/W Integer0..1000

3 Determines sending of null fragments. If value"0", this feature is disabled; null fragments arnot sent.

If value is greater than 0, this feature isenabled; null fragment bursts are sent everynullFragmentBurstsPeriod milliseconds.

portNumber RO Integer1..4094

The port identifier assigned (by the system) tothis ML-PPP instance. To be used in "ping"command.

(1) Maximum Receive Reconstructed Unit(2) Address and Control Field Compression(3) Protocol Field Compression

2.6.24.2 MO Class ML-PPP Counters

Table 35 MO class ML-PPP counters

Name Position


ifHCInPkts 1 PEG 0..264-1 The number of packets delivered by theML-PPP sub-layer to a higher (sub-)layer.Packets received over the ML-PPP bundle aswell as packets received directly over a PPPlink are counted. Received link control protocpackets and IP control protocol packets arenot counted.

ifHCOutPkts 2 PEG 0..264-1 The total number of packets that higher-levelprotocols requested to be transmitted includinthose that were discarded or not sent.

592/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 35 MO class ML-PPP counters

Name Position


ifInErrors 3 PEG 0..264-1 The number of inbound packets that containederror preventing them from being deliverable tohigher-layer protocol.

Estimate on the number of packets lostby counting missing sequence number onreceived frames.

Errors that increments this counter:Frames lost during transmission,Frames received more out of sequence thanthe handled receive window.

ifInUnknownProtos 4 PEG 0..264-1 The number of frames received, via theinterface, which were discarded because of anunknown or unsupported protocol.

ifInDiscards 5 PEG 0..264-1 The number of inbound packets which werechosen to be discarded despite no errorshad been detected to prevent them beingdeliverable to a higher-layer protocol.

One possible reason for discarding sucha packet could be to free up buffer space.Another possible reason is that the ML-PPPbundle is in state "down" or "lost" when packetsarrive.


ifOutDiscards 7 PEG 0..264-1 The number of outbound packets which werechosen to be discarded despite no errorshad been detected to prevent their beingtransmitted.


Errors that increments this counter:Transmission links are overloaded,Transmission links are disabled.

2.6.25 MO Class PingMeasurement (manuallyCreated)

MO class PingMeasurement represents attributes for a measurement job,measuring connection quality by means of packet delay distribution (includingaverage and excessive delays) between the SIU and a defined host.

60 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.25.1 MO Class PingMeasurement Parameters

Table 36 MO class PingMeasurement parameters


RestartType

Description


Instance identifier of the MO.Unique name identifying the destination IP ho

pingDestination R/W IPv4address

0.0.0.0 mo IP address of the destination host.

pingDSCP R/W Integer0..63

0 mo DSCP code of the ECHO packet.


mo Reference (use dependency) to the IP interfaused for ping measurement. Implicitly thereference also gives the local IP address to ufor ping measurement.

When a change to this attribute or the IPAddrattribute of the MO referred to, is committed,then this MO will be configured to use the newIP address.

Rule: Must be set to reference either an instaof MO IPInterfaceor VirtualIPInterface.

pingInterval R/W Integer0..216

�1107 mo Number of milliseconds between echo reques

pingInterval = "0" means no ping is performed

pingPacketSize R/W Integer0..1472

0 mo Number of data octets to send.pingPacketSize = "0" indicates that only theIP header and ICMP echo request header areincluded in the ping packet (no data). To getstatistics (PM data), the size must be at leastbytes in order to carry a timestamp.

To avoid fragmentation of the ping packets, thIP header (20 octets) + ICMP header (8 octet+ pingPacketSize must not be greater than thMTU size of the IPInterface referred to.

pingTimeout R/W Integer4..216

�120 mo Number of milliseconds for ping timeout.

612/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.25.2 MO Class PingMeasurement Counters

Table 37 MO class PingMeasurement counters

Name Position


pingDelayAverage 1 GAUGE

0..232-1 The average delay of packets received,measured in tenths of milliseconds.

pingPacketCount 2 GAUGE

0..232-1 The number of packets received.

pingDelayCountLT25 3 GAUGE

0..232-1 The number of packets received in 0-25% ofpingTimeout.







pingDelayCountGT100 7 GAUGE

0..232-1 The number of packets not received or timedout.

2.6.26 MO Class Policy (manuallyCreated)

MO class Policy represents attributes for a named set of criteria with a policyaction that is applied to traffic flows with selection criteria matching those ofthe policy. MO class Policy is contained in MO class Security. Examplesof policy-controlled areas are IPsec, Access Control Lists (ACL) and firewallprotection. The Policy select criteria parameters (policySelCriteria) of thedefined set of Policy MO instances must be de-correlated by the OSS.


2.6.26.1 MO Class Policy Parameters

Table 38 MO Class Policy parameters


RestartType

Description


Instance identifier of the MO.Consists of an operator defined name.

62 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

policyPriority R/W Integer0–232

�10 mo Policies are ordered and searched through by

the IPsec implementation in accordance withnumber. 0 is highest priority and 232-1 is lowepriority.

Rule: policyPriority must be unique among thMO Policy instances.

Tip: Make large gaps between policyPrioritynumbers so that new policies can easily bedefined and inserted wherever required in anestablished sequence of policies.

policyDir R/W in/out/both

both mo Traffic direction for which this entry must takeeffect.

Rule: If policyAction is "protect" then policyDmust be set to "both".

policyAction R/W bypass/discard/protect

discard mo Actions that must be applied to packets fittingthis policy entry.

policySelCriteriaLocalAddr

R/W String(p)0, 3..31

<emptystring>

mo IP address of the local peer; part of the policyselection criteria. The attribute value can be:

IPv4address/IPv4address-IPv4address/IPv4addressRange/”ANY”ANY means any IPv4 address.

Rule: <empty string> is not a valid value

policySelCriteriaRemoteAddr

R/W String(p)0, 3..31

<emptystring>

mo IP address of the remote peer; part of the polselection criteria. The attribute value can be

IPv4address/IPv4address-IPv4address/IPv4addressRange/”ANY”ANY means any IPv4 address.

Rule: <empty string> is not a valid value

policySelCriteriaProtocol

R/W Integer0..255

0 mo Protocol selector specifying upper protocol typpart of the policy selection criteria.

Note: ANY is specified by value 0.

632/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

policySelCriteriaLocalPort

R/W String(m)0, 1..11

<emptystring>

mo Local port number; part of the policy selectioncriteria. The attribute value can be:portNumber/portNumber-portNumber/”ANY”/”OPAQUE”

portNumber = a number between 0 and 65535.

ANY means any port number between 0 and65535.

OPAQUE means that port number is not availablein the processed IP packet.

Logically ANY includes OPAQUE.

Rule: portNumber(end)< portNumber(start) isnot valid.

Rule: If policySelCriteriaProtocol is 0 (ANY) or 1(ICMP), then policySelCriteriaLocalPort must beANY.

Rule: If policySelCriteriaProtocol is NOT one of{0 (ANY), 1 (ICMP), 6 (TCP), 17 (UDP)}, thenpolicySelCriteriaLocalPort must be OPAQUE orANY.


64 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

policySelCriteriaRemotePort

R/W String(m)0, 1..11

<emptystring>

mo Remote port number; part of the policy selectcriteria. The attribute value can be:portNumber/portNumber-portNumber/”ANY”/”OPAQUE”

portNumber = a number between 0 and 6553

ANY means any port number between 0 and65535.

OPAQUE means that port number is not availain the processed IP packet.

Logically ANY includes OPAQUE.

Rule: portNumber(end)< portNumber(start) isnot valid.

Rule: If policySelCriteriaProtocol is 0 (ANY) o(ICMP), then policySelCriteriaRemotePort mube ANY.

Rule: If policySelCriteriaProtocol is NOT one{0 (ANY), 1 (ICMP), 6 (TCP), 17 (UDP)}, thenpolicySelCriteriaRemotePort must be OPAQUor ANY.


652/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depMandatoryManualSAPair

R/W String(m)0..20

<emptystring>

mo Instance ID (usage dependency) of themandatory associated ManualSAPair MO. Themandatory ManualSAPair is used for outboundtraffic. Both the mandatory ManualSAPair andthe optional ManualSAPair (if present) can beused for inbound traffic.

Rule: If policyAction is set to "protect", then thedepMandatoryManualSAPair value must not bean <empty string>.

Rule: If policyAction is set to "bypass" or"discard", then the depMandatoryManualSAPairvalue must be <empty string>.

depOptionalManualSAPair

R/W String(m),0..20

<emptystring>

mo Instance ID (usage dependency) of the optionalassociated ManualSAPair MO. The optionalManualSAPair is not used for outbound traffic.Both the mandatory ManualSAPair and theoptional ManualSAPair (if present) can be usedfor inbound traffic.

Rule: If depOptionalManualSAPair value isnot <empty string>, then policyAction must be"protect".

Rule: The depOptionalManualSAPair value musnot equal the depMandatoryManualSAPair value

2.6.26.2 MO Class Policy Counters

Table 39 MO class Policy counters

Name Position


inPacketsHandled 1 PEG 0..264-1 The number of inbound packets handled bythe policy.

outPacketsHandled 2 PEG 0..264-1 The number of outbound packets handled bythe policy.

inPacketsDiscarded 3 PEG 0..264-1 The number of inbound packets discardedbecause of the policy.

outPacketsDiscarded 4 PEG 0..264-1 The number of outbound packets discardedbecause of the policy.

66 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.27 MO Class PPP (manuallyCreated)

MO class PPP represents attributes for a PPP link communication medium.

2.6.27.1 MO Class PPP Parameters

Table 40 MO class PPP parameters


RestartType

Description



operationalState

RO enabled/disabled



• The MO referenced by attributedepE1T1Interface is created and enabled, a

• The attribute pppLinkStatus has the value "u

"disabled": the resource is totally inoperable aunable to provide service to the user.Details: Any of the "enabled" details are notfulfilled.

pppLinkStatus RO up/down/lost

Status of the PPP link according to:

"up": Connection has been established.

"down": Connection has never been establishsince last reset.

"lost": Connection has been established sincelast reset, but is currently not established.

depE1T1Interface

R/W Integer0..15

0 Instance number of an MO E1T1Interfaceinstance.

Rule: Only one PPP instance per E1T1Interfinstance is allowed.

Rule: An MO E1T1Interface instance used bPPP is not allowed to be used by any instancea MO SuperChannel or CESChannel.

Rule: The dependant MO E1T1Interfaceinstance must be of type = "E1", "T1", or"E1_unframed".

672/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 40 MO class PPP parameters


RestartType

Description

startTS R/W Integer1..24 (E1)/1..17 (T1)/0

0 mo The starting time slot when framed E1/T1 is used(ML-PPP). The value "0" (notDefined) is used for"E1_unframed".

Rule: If E1 is unframed, then ignore this attribute

endTS R/W Integer8..31 (E1)/8..24 (T1)/

24 mo The ending timeslot when framed E1/T1 is used(ML-PPP).

Rule: The value of endTS shall be at least 7 TShigher than the value of attribute startTS.

Rule: If E1 is unframed, then ignore this attribute

pppMRU R/W Integer68..16383

1506 Defines the largest frame that the node mayreceive, as set by the operator.

Note: The value of pppMRU should be greaterthan or equal to (MRRU+6). The 6 octets leaveroom for the ML-PPP protocol header.

negotiatedMRU RO Integer0..216-1

The ML-PPP router's MRU for this PPP link afternegotiation.

2.6.27.2 MO Class PPP Counters

Table 41 MO class PPP counters

Name Position


ifHCInOctets 1 PEG 0..264-1 The total number of octets received on theinterface, including framing characters butexcluding HDLC flags.

ifHCOutOctets 2 PEG 0..264-1 The total number of octets transmitted out ofthe interface, including framing characters butexcluding HDLC flags.

ifHCInPkts 3 PEG 0..264-1 The number of packets/frames, delivered bythis sub-layer to a higher (sub-)layer. ML-PPPframes as well as IP packets received directlyover the PPP link are counted.

Note: PPP does not distinguish betweendifferent types of packets/frames like forexample plain PPP and MLPPP.

68 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 41 MO class PPP counters

Name Position


ifHCOutPkts 4 PEG 0..264-1 The total number of packets/frames thathigher-level protocols requested be transmitteincluding those that were discarded or not sen

Note: PPP does not distinguish betweendifferent types of packets like for example plaPPP and MLPPP.

ifInErrors 5 PEG 0..264-1 The number of inbound packets/frames thatcontained error preventing them from beingdeliverable to higher-layer protocol.

Errors that increments this counter:Frame Check Sequence (FCS) errors,Frames less than four octets,Frames ending with a sequence of more thansix "1" bits,Frame or fragment longer than 1500 octets.


Errors that increments this counter:Frames with unknown or unsupported protocoFrames with unrecognized address or controlfields.

ifInDiscards 7 PEG 0..264-1 The number of inbound packets/frames whichwere chosen to be discarded even though noerrors had been detected to prevent their beindeliverable to a higher-layer protocol. Onepossible reason for discarding such a packetcould be to free up buffer space.

ifOutErrors 8 PEG 0..264-1 The number of outbound packets/frames thatcould not be transmitted because of errors.

ifOutDiscards 9 PEG 0..264-1 The number of outbound packets/frames whicwere chosen to be discarded even though noerrors had been detected to prevent their beintransmitted.


2.6.28 MO Class QosPolicy (manuallyCreated)

MO class QosPolicy represents attributes for three DSCP mapping functions

692/1551-LZA 104 102/6 Uen E | 2011-09-08


• DSCP to PCP value.

• DSCP to queue number.

• PCP/untagged to queue number.

2.6.28.1 MO Class QosPolicy Parameters

Note: Change of attributes in this MO class cause traffic impact a longer orshorter time.

Table 42 MO class QosPolicy parameters


RestartType

Description


0 Instance identifier of the MO.

dscp2pcp0 R/W Integer0..7

0 PCP value that DSCP value 0 is mapped to.

























70 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description





































712/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description





































72 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description































dscp2q0 R/W Integer1..8

8 Queue number that DSCP value 0 is mapped





732/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


8 Queue number that DSCP value 3 is mapped to.














6 Queue number that DSCP value 10 is mapped to





















74 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description





































752/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description





































76 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description















L2QosMappingType

R/W DSCP2Queue/Pcp2Queue

See Description

Defines which parameter (PCP or DSCP) shobe used for QoS. Only the bridged traffic isimpacted. For the routed traffic, DSCP is useda classification mechanism.

Default value: DSCP2Queue (if no MOQosPolicy is created) or Pcp2Queue (when ainstance of MO QosPolicy is created).

defaultPcp R/W Integer0..7

0 Default PCP value set by the system to theuntagged frames.

pcp2q0 R/W Integer1..8

1 Queue number where PCP value 0 is mapped











772/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


1 Queue number where PCP value 6 is mapped to


1 Queue number where PCP value 7 is mapped to

2.6.28.2 MO Class QosPolicy Counters

No counters exist.

2.6.29 MO Class RemoteMEP (manuallyCreated)

MO class RemoteMEP represents the remote MEG End Point (MEP) withina Maintenance Entity Group (MEG). The RemoteMEP maintains receivedinformation about other MEPs in the MEG.

2.6.29.1 MO Class RemoteMEP Parameters

Table 43 MO class RemoteMEP parameters


RestartType

Description



Rule: It is only allowed to have 150 RemoteMEPstotally for all configured MEGs.

mepId R/W Integer1..8191

8191 mo Maintenance association End Point Identifier ofthe RemoteMEP.

Rule: The mepId must be unique in the MEG.

78 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 43 MO class RemoteMEP parameters


RestartType

Description

state RO rMepIdle/rMepStart/rMepFailed/rMepOk

The operational state of the remote MEP statmachine. This state machine monitors thereception of valid CCMs from a remote MEP wa specific MEP ID. It uses a timer that expiresin 3.5 times the length of time indicated by thattribute ccmInterval timer for the MEG.

"rMepIdle"(1) = Momentary state during reset

"rMepStart"(2) = The timer has not expired sinthe state machine was reset, and no valid CChas yet been received.

"rMepFailed"(3) = The timer has expired, bothsince the state machine was reset, and sincevalid CCM was received.

"rMepOk"(4) = The timer has not expired sincvalid CCM was received.

failedOrOkTime RO String(m)1..20

The time at which the IFF Remote MEP statemachine last entered either the "rMepFailed""rMepOk" state. The time is stated as a stringcontaining Date and Time (UTC) in the forma1970-01-01 00:00:50.

macAddress RO MACAddress

MAC address of the remote MEP.

rdi RO true/false

If the RDI bit is activated ("true") the remote Mhas not received CCMs from at least one of itdefined remote MEPs.

2.6.29.2 MO Class RemoteMEP Counters

No counters exist.

2.6.30 MO Class RoutingPolicy (manuallyCreated)

MO class RoutingPolicy aggregates a set of MO class RoutingRule instancesto form a routing policy.

792/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.30.1 MO Class RoutingPolicy Parameters

Table 44 MO class RoutingPolicy parameters


RestartType

Description



2.6.30.2 MO Class RoutingPolicy Counters

No counters exist.

2.6.31 MO Class RoutingRule (manuallyCreated)

MO class RoutingRule represents an element in a RoutingPolicy. Theelement contains of a set of criteria for a packet, that all have to be met totrigger that the referenced IpRoutePbr is used for forwarding the packet.

2.6.31.1 MO Class RoutingRule Parameters

Table 45 MO class RoutingRule parameters


RestartType

Description



Rule: Among the attributes criteriaSourceAddr,criteriaDestinationAddr, criteriaProtocol,criteriaSourcePort, criteriaDestinationPort,criteriaPCP, and criteriaDSCP at least one mustbe different from "ANY".

priority R/W Integer0..511

0 mo Entries are ordered and searched through by theimplementation according to this number where"0" is highest priority and "511" is lowest priority.

Rule: The priority must be unique among theMO RoutingRule instances in a given MORoutingPolicy.

Tip: Make large gaps between priority numbersso that new entries can easily be definedand inserted wherever required in an existingRoutingPolicy.

80 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

depPrimaryRoute


mo Reference (use dependency) to an instance oMO IpRoutePbr that holds the primary routebe used if the criteria match.

Rule: This attribute must hold a valid referento an instance of MO IpRoutePbr.

Note: Only one of the MO IpRoutePbrinstances referenced by depPrimaryRoute andepSecondaryRoute are used at any time. If tdepPrimaryRoute is marked as "active", it wilbe used. When depPrimaryRoute is not markas "active", depSecondaryRoute will be used.none of the routes are marked as "active", thiMO RoutingRule instance will not be considefor matching.

depSecondaryRoute


mo Reference (use dependency) to an instance oMO IpRoutePbr that holds the secondary routo be used if the criteria match.

Rule: This attribute must contain a referencean instance of MO IpRoutePbr or be equal to<empty string>.

criteriaSourceAddr

R/W String(p)3..31

any Criteria 1: Source IP address in the packet. Tattribute value can be:




criteriaDestinationAddr

R/W String(p)3..31

any Criteria 2: Destination IP address in the packThe attribute value can be:




812/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

criteriaProtocol R/W String(m)1..10

any Criteria 3: Protocol selector specifying upperprotocol type. The attribute value can be:

protocolNumber/"ANY"protocolNumber = a number between 0 and 255

Note: For protocol numbers, see Reference [10]

criteriaSourcePort

R/W String(m)1..11

any Criteria 4: Source port number in the packet.The attribute value can be:

portNumber/portNumber-portNumber”ANY”/portNumber = a number between 0 and 65535.


Rule: portNumber(end) < portNumber(start) isnot a valid configuration.

Rule: If criteriaProtocol is NOT one of {"6" (TCP)"17" (UDP)} criteriaSourcePort must be "ANY".

criteriaDestinationPort

R/W String(m)1..11

any Criteria 5: Destination port number in the packetThe attribute value can be:

portNumber/portNumber-portNumber”ANY”/portNumber = a number between 0 and 65535.


Rule: portNumber(end) < portNumber(start) isnot a valid configuration.

Rule: If criteriaProtocol is NOT one of {"6"(TCP), "17" (UDP)} criteriaDestinationPort mustbe "ANY".

82 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

criteriaDSCP R/W String(m)1..5

any Criteria 6: Value of the DSCP field in the IPpacket. The attribute value can be:

DSCPvalue/"ANY"

DSCPvalue = a number between 0 and 63.

ANY means any DSCP value between 0 and

criteriaPCP R/W String(m)1..3

any Criteria 7: Value of the PCP field in the VLAtagged Ethernet frame carrying the IP packetThe attribute value can be:

PCPvalue/"ANY"

PCPvalue = a number between 0 and 7.

ANY means any PCP value between 0 and 7PCP is not available in the processed IP pack(no VLAN tag).

Note: criteriaPCP will be ignored for theRoutingPolicy referred to by attributedepRoutingPolicy in MO STN.

Rule: This criteria can only be used if the linklayer is VLAN. If criteriaPCP is not equal to "Athe containing RoutingPolicy can be referredto only by instances of MO IPInterface that uMO VLAN as link layer.

2.6.31.2 MO Class RoutingRule Counters

Table 46 MO class RoutingRule counters

Name Position


packetsHandled 1 PEG 0..264-1 The number of packets that have matched thiRouting Rule.

2.6.32 MO Class RoutingTable (systemCreated)

MO class RoutingTable is a container for the MO classes IpRouteSys andIpRoute. Only one instance of MO RoutingTable exists.

832/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.32.1 MO Class RoutingTable Parameters

Table 47 MO class RoutingTable parameters


RestartType

Description

instanceId RO Integer 0 Instance identifier of the MO.Always set to "0" as only one instance of this MOexists.

2.6.32.2 MO Class RoutingTable Counters

No counters exist.

2.6.33 MO Class SecondaryIP (manuallyCreated)

MO class SecondaryIP represents attributes for an additional IP address on anMO IPInterface in which it is contained.

Note: It is currently not recommended to use this functionality in a livenetwork.

2.6.33.1 MO Class SecondaryIP Parameters

Table 48 MO class SecondaryIP parameters


RestartType

Description



84 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 48 MO class SecondaryIP parameters


RestartType

Description

secondaryIP_Address

R/W IPv4address

0.0.0.0 no Secondary IP address on an MO IPInterface.

The attribute secondaryIP_Address must notequal to the attribute primaryIP_Address of MIPInterface.

When this attribute value is changed, all MOinstances, which have a depIP_Interface attribthat refers to this instance, are affected. Fordetails about the effect, see the depIP_Interfaattribute of the MOs in question

The following depending MO may beaffected by changed value of this attribute:STN, TGTransport, PingMeasurement,CESChannel, and Synchronization.

The secondaryIP_Address must not be equalthe primaryIP_Address of MO IPInterface.

Rule: 0.0.0.0 (notDefined) is not a valid value

secondarySubNetMask

R/W IPv4subnetMask

0.0.0.0 no Subnet mask.

Rule: 0.0.0.0 (notDefined) is not a valid value

2.6.33.2 MO Class SecondaryIP Counters

No counters exist.

2.6.34 MO Class Security (manuallyCreated)

MO class Security represents attributes for IPsec- and firewall-relatedfunctionality. When required, policies and security associations can be definedto protect communication in a generic way at the IP transport layer. TheSecurity MO contains policies (MO Policy) and security associations (MOManualSAPair).

Note: If an instance of the Security MO is configured on the node, then the"protection" mechanism (IPsec) is enabled even if no Policies and noManualSAPairs are defined. In this case, in accordance with IETFRFC framework, all inbound and outbound communication packetsare discarded.


852/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.34.1 MO Class Security Parameters

Table 49 MO class Security parameters


RestartType

Description

instanceId RO Integer 0 Instance identifier of the MO.Always set to "0" as only one instance of this MOexists.

2.6.34.2 MO Class Security Counters

Table 50 MO class Security counters

Name Position


ipsecInPacketDiscardNoPol 1 PEG 0..264-1 The number of inbound packets discardedbecause a matching policy is not found.

ipsecOutPacketDiscardNoPol 2 PEG 0..264-1 The number of outbound packets discardedbecause a matching policy is not found.

2.6.35 MO Class STN (systemCreated)

MO class STN represents the complete SIU, a network element that providesIP connectivity. Only one instance of MO STN exists.

2.6.35.1 MO Class STN Parameters

Table 51 MO class STN parameters


RestartType

Description

instanceId RO Integer 0 0 Instance identifier of the MO.Always set to "0" as only one instance of this MOexists.

operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use.Details: No critical alarm exists on the MO and

"disabled": the resource is totally inoperable andunable to provide service to users.Details: Any of the "enabled" details is notfulfilled.

86 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


node Reference (use dependency) to the IP interfaassigned for O&M traffic towards the OSS.Implicitly the reference also gives the local IPaddress to use for communication with the OS

When a change to the IPAddress attribute ofMO referred to, is committed, the effect is thaprior to the change taking effect, active SSH oSFTP sessions will be disconnected.

Rule: Must be set to <empty string> or refereeither an instance of MO IPInterface orVirtualIPInterface.

depLocalRoutingPolicy


Reference (use dependency) to an instance oMO RoutingPolicy.

IP packets originating from the SIU (on anyinstance of MO IPInterface or VirtualIPInterfawill be matched against the RoutingRules inthe referenced RoutingPolicy. If a match isfound, the packet will be routed according tothe IpRoutePbr referenced by the matchedRoutingRule. If no match is found, destinatiobased routing will be used.

Rule: Must refer to an instance of MORoutingPolicy or be equal to <empty string>

Rule: The MO RoutingPolicy instance referrmust not be referred by any other MO instanc

wakeUpRegistration

R/W IPv4address

0.0.0.0 no(1)IP address to which the SIU must send a wakeevent.

The value "0.0.0.0" (notDefined) means thatwake-up registration is turned off.

872/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

wakeUpEventInterval

R/W Integer0..10

1 Time in minutes between sending a wake-upevent to the wakeUpRegistration IP addressand stop sending when a subscribe operation isperformed. "0" means that sending of wake-upevent is turned off.

The first wake-up event, after a node start, mustbe sent before this timer expires first time.

Note: Change of value will take effect at nextstart of the function, that is when all subscribershave unsubscribed.

SW_PrimaryProductNumber

RO String(p)0..24

Primary SW product number. Product number ofcurrent running software.

SW_PrimaryProductRevision

RO String(p)3..6

Primary SW product revision. Product revision ocurrent running software.

SW_BackupProductNumber

RO String(p)0..24

SW product number of the backup SW. In theevent of startup failure, the SIU reverts to thisSW.

SW_BackupProductRevision

RO String(p)3..6

Backup SW product revision.

alarmSupervisionActive

RO true/false

"true" if alarm supervision is active, that is, thereis at least one active subscription.

DSCP_OperationAndMaintenance

R/W Integer0..63

0 DSCP code for O&M data between the SIU andthe OSS, excluding O&M file transfer.

DSCP_OM_FileTransfer

R/W Integer0..63

0 DSCP code for O&M file transfer between SIUand OSS. File transfer related to PM, Bulk CMand SW Session.

STN_PGW_KeepalivePeriod

R/W Integer1..100

1 no (2)Number of seconds between keep aliveprocedures sent from the SIU to the PGW.

STN_PGW_L2TP_MaxTransmissions

R/W Integer1..10

5 no (2) Maximum number of retransmissions ofL2TP control messages, including the originaltransmission, in accordance with the L2TP contromessage retransmission mechanism. This valueapplies to all control messages, including, forexample, the Setup Control Connection Requestmessage (SCCRQ) and the KeepAlive Hellomessage.

88 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

STN_PGW_L2TP_RetransmissionCap

R/W Integer1..10

4 no (2) Cap on the exponentially increasing intervalbetween retransmission of L2TP controlmessages [seconds], in accordance withthe L2TP control message retransmissionmechanism. This value applies to all controlmessages, including for example the SCCRQand the KeepAlive Hello message.

Rule: The value must be larger than,or equal to the value of attributeSTN_PGW_L2TP_InitialRetransmissionPerio

STN_PGW_L2TP_InitialRetransmissionPeriod

R/W Integer1..10

1 no (2) Initial period from the original transmission tofirst retransmission of L2TP control messages[seconds], in accordance with the L2TP contrmessage retransmission mechanism. This vaapplies to all control messages, including forexample the SCCRQ and the KeepAlive Hellomessage.

STN_Name R/W String(m)0..200

<emptystring>

no (2) Network-unique name for the SIU.

Rule: This attribute must contain a unique honame and must be defined if an instance of MML-PPP exists.

Rule: When ML-PPP or Abis/IP are used, thelength is restricted to 18 characters.

restartReason RO spontaneousReset/orderedReset/SW_Upgrade/pushButtonReset/powerOn/CM_Config/autoRollback

Defines the reason for the last restart.

systemClockTimeServer

R/W IPv4address

0.0.0.0 IP address to the time server to be used forsynchronization of the system clock.

892/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

STN_systemClockUDP_Port

R/W Integer0..65535

123 Number of the local UDP port to be used forsynchronization of the system clock.

Note: Only valid if attribute systemClockTimeSeverType is set to "NTP" (the remote port is fixedto 123).

contactWithFileServer

RO true/false

"true" if latest attempt to upload a PM filesucceeded or no attempt to upload a PM file hasyet been performed.

systemClockUDP_Port_General_PTP

R/W Integer0..65535

320 Number of the local and remote UDP port to beused for PTP general messages.

Note: Only valid if attribute systemClockTimeSeverType is set to "PTP".

systemClockUDP_Port_Event_PTP

R/W Integer0..65535

319 Number of the local and remote UDP port to beused for PTP event messages.

Note: Only valid if attribute systemClockTimeSeverType is set to "PTP".

systemClockTimeServerType

R/W notDefined/PTP/NTP

NTP Indicates if the system clock is synchronizedusing an NTP server or a PTP server.

(1) Change of value takes effect at next start of the function, that is, when all subscribers have unsubscribed.(2) Change of value will take effect the next time a control connection is established.

2.6.35.2 MO Class STN Counters

Table 52 MO class STN counters

Name Position


CPU_Load 1 GAUGE

0..100 CPU load of the main processor (%).

failedPMUploads 2 PEG 0..216-1 The number of failed attempts to upload PMfiles.

2.6.36 MO Class SuperChannel (manuallyCreated)

MO class SuperChannel represents attributes for a super channel. A superchannel is a set of several contiguous time slots on an E1/T1 interface, used

90 2/1551-LZA 104 102/6 Uen E | 2011-09-08


together as a wideband connection on Abis lower. MO SuperChannel iscontained in a MO TGTransport.

2.6.36.1 MO Class SuperChannel Parameters

Table 53 MO class SuperChannel parameters


RestartType

Description



operationalState

RO enabled/disabled



• The MO referenced by attributedepE1T1Interface is created and enabled.


depE1T1Interface

R/W Integer0..216

�1216�1 mo Instance number of an MO E1T1Interface

instance to which there is a usage dependenc

Rule: An MO E1T1Interface instance is onlyallowed to be used by one, and only one,instance of MO SuperChannel.

Rule: 216�1 (notDefined) is not a valid value.

Rule: The dependant MO E1T1Interfaceinstance must be of type "E1" or "T1".

Note: The type attribute of the referencedE1T1Interface should have value "E1", evenin locations where T1 is the standard for TDMtransmission. The value "E1_30" is only forbackwards compatibility and should not be usfor new installations. The configuration of whitime slots to use is controlled from the BSC.

912/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.36.2 MO Class SuperChannel Counters

Table 54 MO class SuperChannel counters

Name Position


SC_FramesLostDownlink 1 PEG 0..264-1 The number of frames discarded by the SCbuffer (downlink). Discard is caused by, forexample, temporary overload.

SC_FramesDownlink 2 PEG 0..264-1 The total number of frames handled by the SCbuffer (downlink), including both discarded andsent.

SC_FramesUplink 3 PEG 0..264-1 The number of frames received by the SCbuffer (uplink) excluding error frames.

SC_InOctets 4 PEG 0..264-1 The number of ingress octets received,corresponding to the number of ingress framesreceived excluding error frames.

SC_OutOctets 5 PEG 0..264-1 The number of egress octets sent,corresponding to the number of egress framessent.

SC_InError 6 PEG 0..264-1 The number of ingress frames discarded dueto errors in the frame, for example malformedheader or FCS mismatch.

2.6.37 MO Class SynchEthInterface (manuallyCreated)

MO class SynchEthInterface represents the Synchronous Ethernet function.

2.6.37.1 MO Class SynchEthInterface Parameters

Table 55 MO class SynchEthInterface parameters


RestartType

Description



depEthernetInterface


no Reference (use dependency) to the instance ofMO EthernetInterface assigned for sync traffic.

Rule: An MO EthernetInterface instance isonly allowed to be used by one, and only one,instance of SynchEthInterface.


92 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

ssmQLoption R/W option-1/option-2

option-1 no Indicates the type of Synchronization StatusMessage (SSM) option used in the network.

"option-1" refers to synchronization networksdesign for Europe."option-2" refers to the synchronization netwodesign for U.S.

See attribute ssmQL for more information.

Rule: All instances of MO SynchEthInterfacmust have the same value.

ssmQLmode R/W QL-enabled/QL-disabled

QL-enabled no Indicates whether SSM is enabled ("QL-enableor not ("QL-disabled") on the interface.

Rule: All instances of MO SynchEthInterfacmust have the same value.

932/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

ssmQL RO String6..10

notDefined no Indicates the type of Quality Level (QL) on thissynchronization source. The value dependson the configured SSM option; see attributessmQLoption in MO Synchronization.

For synchronization sources not supporting SSMprocessing, it is possible to force the qualitylevel to a fixed provisioned value. See attributessmOverride.

For Europe ("option-1") the following values areavailable:QL-PRCQL-SSU-AQL-SSU-BQL-EEC1QL-DNU.

For U.S. ("option-2") the following values areavailable:QL-PRSQL-STUQL-ST2QL-TNCQL-EEC2QL-SMCQL-DUS.

The value "notDefined" means that the externalsynchronization Ethernet source is not yetdefined. This value will change when a validstatus message is received or configured(forced).

The value "QL-FAILED" means that a failure hasoccurred in the synchronization source or in theEthernet link towards the synchronization source

94 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

ssmQLminimum

R/W String6..8

<emptystring>

no Indicates the minimum QL value allowed for tinterface. The value depends on the configurSSM option, see attribute ssmQLOption in MOSynchronization.

For Europe ("option-1") the following values aavailable:QL-PRC (highest)QL-SSU-AQL-SSU-BQL-EEC1QL-DNU (lowest).

For U.S. ("option-2") the following values areavailable:QL-PRS (highest)QL-STUQL-ST2QL-TNCQL-EEC2QL-SMCQL-DUS (lowest).


Rule: If the QL is lower than this value a switto the next available Synchronization Ethernesource will be performed.

See attribute ssmQL for more information.

ssmOverride R/W String0..8

<emptystring>

no With this attribute it is possible to force the qualevel to a fixed provisioned value.

Rule: The value depends on the configuredSSM option, see attribute ssmQLoption in MOSynchronization.

Rule: An <empty string> is not a valid valuewhen attribute ssmQLmode = "QL-disabled".

For Europe ("option-1") the following values aavailable:QL-PRCQL-SSU-AQL-SSU-BQL-EEC1QL-DNU.

For U.S. ("option-2") the following values areavailable:QL-PRSQL-STUQL-ST2QL-TNCQL-EEC2QL-SMCQL DUS

952/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.37.2 MO Class SynchEthInterface Counters

No counters exist.

2.6.38 MO Class Synchronization (systemCreated)

MO class Synchronization represents attributes for time synchronizationwith the RBS. MO Synchronization contains a set of time servers (MOTimeServer) that can be used for synchronization. Only one instance of MOSynchronization exists.

2.6.38.1 MO Class Synchronization Parameters

Table 56 MO class Synchronization parameters


RestartType

Description

instanceId RO Integer 0 0 Instance identifier of the MO.Always set to "0" as only one instance of this MOexists.

TS_STN_SynchStatus

RO synchronized/notSynchronized

The current synchronization state of the SIU thatindicates if it can supply synchronization.

TS_UsedTimeServer

RO String(m)0..20

Name of the time server the SIU currently usesfor synchronization, that is, the instanceId of ancreated instance of MO TimeServer.

Note: Only valid if synchType = "timeServer"

calibrationExpireDate

RO Date Oscillator calibration expiry date.

96 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

synchType R/W timeServer/notDefined/clockInput/E1T1/synchE/none

nodDefined Type of external synchronization source.

"notDefined": the external synchronizationsource is not yet defined

"none": the SIU does not supply synchronizat

Rule: If attribute synchType = "timeServer" thmust exist an instance of MO TimeServer toa valid configuration.

Rule: If attribute synchType = "E1T1" there mexist at least one instance of MO E1T1Interfawith attribute receiveClockSource set to"timingReference".

Rule: If attribute synchType = "synchE"there must exist at least one instance of MOSynchEthInterface.

DSCP_Synchronization

R/W Integer0..63

0 DSCP code for synchronization data betweenSIU and the time server.

Note: Only valid if attribute synchType ="timeServer"

Note: When using time server (NTP/PTP)over satellite this value should be set to "46".NTP/PTP packets shall also be assignedDSCP=46 in the time server. This might requa co-located router to paint the packets with tproper DSCP=46 value if the time server not hthe capability to directly assign DSCP values.

972/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


mo Reference (use dependency) to the instance ofMO IPInterface or VirtualIPInterface assignedfor communication towards the time servers(sync traffic).

Rule: <empty string> is not a valid value whenattribute synchType = "timeServer".

usedSynchSource

RO MO-DN The synchronization source that thesynchronization function currently is using.MO-DN reference to the instanceId of either aninstance of MO E1T1Interface , TimeServer orSynchEthInterface.

The attribute is valid when attribute synchType= "timeServer", "E1T1" or "synchE". If not, thisattribute is represented as an empty string.

2.6.38.2 MO Class Synchronization Counters

Table 57 MO class Synchronization counters

Name Position


TS_NoTS_Reselections 1 PEG 0..264-1 The number of performed time serverre-selections to valid IP addresses (not0.0.0.0), regardless of whether the new timeserver answered.

Note: Only valid if attribute synchType ="timeServer".

2.6.39 MO Class TGTransport (manuallyCreated)

MO class TGTransport represents attributes for the transport function betweena BSC and one TG in a BTS. Each instance of a TGTransport MO contains aset of super channels (MO SuperChannel).

98 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.39.1 MO Class TGTransport Parameters

Table 58 MO class TGTransport parameters


RestartType

Description


Instance identifier of the MO.Unique name, used to identify the MOTGTransport instance. The instanceId assignis a concatenation of the STN_Name (MOSTN) and a number separated by a hyphen (corresponding to the BSC TG identification.

operationalState

RO enabled/disabled



• At least one MO SuperChannel instance iscreated and enabled, and

• The attribute STN_PGW_LinkStatus has va"up", and

• The MO IPInterface, referenced by attributedepIP_Interface, is enabled


PGW_IP_Address

R/W IPv4address

0.0.0.0 no(1)IP address of the PGW.

Rule: The value of attribute PGW_IP_Addresmust be the same in all MO TGTransportinstances.

992/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 58 MO class TGTransport parameters


RestartType

Description


mo Reference (use dependency) to the IP interfaceassigned for Abis traffic to the BSC. Implicitly thisreference also gives the local IP address to usefor communication with the BSC.

When a change to the IPAddress attribute ofthe MO referred to, is committed, then the effectis that prior to the change taking effect, activeTraffic channels will be closed down.

Rule: Must refer to an instance of either MOIPInterface or VirtualIPInterface.

Rule: The value of attribute depIP_Interface musbe the same in all MO TGTransport instances.

STN_PGW_LinkStatus

RO up/down/lost

Status of primary control channel.

"up": Connection established.

"down": Connection not established since lastreset.

"lost": Connection established since last reset,but not currently established.

overloadThreshold

RO Integer0..10000

Threshold for reporting packet loss, measured inhundredths of a percentage point. The attributereflects the configuration made by the BSC.

overloadReportInterval

R/W Integer1..10

1 Number of seconds between overload reportssent to the BSC if over overloadThreshhold.

DSCP_L2TP_CP

R/W Integer0..63

0 DSCP code for L2TP control connection betweenthe SIU and the BSC.

(1) Traffic channels are re-established, which can cause temporary service degradation

100 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.39.2 MO Class TGTransport Counters

Table 59 MO class TGTransport counters

Name Position


inAbisOctets 1 PEG 0..264-1 The number of octets received from the BSC.

The counter counts transport session packetsthat is, control connection messages are notincluded.

The octets counter counts the load contributeby transport session packets at the IP level,that is, each packet increments the counterwith the length of the entire IP packet, includinthe IP header.

outAbisOctets 2 PEG 0..264-1 The number of octets sent to the BSC.

The counter counts Transport Session packetthat is, control connection messages are notincluded.

The octets counter counts the load contributeby Transport Session packets at the IP level,that is, each packet increments the counterwith the length of the entire IP packet, includinthe IP header.

inAbisPackets 3 PEG 0..264-1 The number of L2TP transport session packereceived from the BSC, excluding controlconnection messages.

outAbisPackets 4 PEG 0..264-1 The number of L2TP transport session packesent to the BSC, excluding control connectionmessages.

inAbisPacketsErrors 5 PEG 0..264-1 The number of L2TP packets received withchecksum errors.

inAbisPacketsLost 6 PEG 0..264-1 The number of out of sequence or lost L2TPtransport session packets received from theBSC.

1012/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 59 MO class TGTransport counters

Name Position


uplinkLAPDFramesDiscarded 7 PEG 0..264-1 The number of uplink LAPD frames discardedbecause there is no active transport session tocarry frames with the relevant SAPI value.

This can be, for example, when the connectionto the BSC is completely or partly lost, or inoverload situations when the BSC has throttleddown traffic and reconfigured the SIU to throwframes.

downlinkLAPDFramesDiscarded

8 PEG 0..264-1 The number of downlink LAPD framesdiscarded because there is no MOSuperChannel instance configured to carryframes with the relevant TEI value.

This can be caused by configuration faults.

2.6.40 MO Class TimeServer (manuallyCreated)

MO class TimeServer represents attributes for a time server. MO TimeServeris contained in MO Synchronization.

2.6.40.1 MO Class TimeServer Parameters

Table 60 MO class TimeServer parameters


RestartType

Description



TS_Priority R/W Integer0..232

�10 The priority of the MO TimeServer instance. The

MO TimeServer instance with lowest priorityvalue and a working NTP connection must beused first for synchronization.

Tip: Make large gaps between priority numbersso that new MO TimeServer instances can easilybe defined and inserted wherever required in thepriority order.

Rule: Priority must be unique.

102 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 60 MO class TimeServer parameters


RestartType

Description

TS_IP_Address R/W IPv4address

0.0.0.0 mo IP address of the time server to be used forsynchronization.

Rule: Must be unique among instances of MOTimeServer.

Rule: "0.0.0.0" (notDefined) is not a valid valu

STN_TS_UDP_Port

R/W Integer0..65535

123 Number of the local UDP port to be used forsynchronization.

Note: Only valid if attribute timeServerType ="NTP". (The remote port is fixed to "123").

TS_UDP_Port_General_PTP

R/W Integer0..65535

320 Number of the local and remote UDP port to bused for PTP general messages.

Note: Only valid if attribute timeServerType ="PTP".

TS_UDP_Port_Event_PTP

R/W Integer0..65535

319 Number of the local and remote UDP port to bused for PTP event messages.

Note: Only valid if attribute timeServerType ="PTP".

timeServerType R/W NTP/PTP

NTP Indicates if the time server is configured for Nor PTP synchronization.

Rule: It is not allowed to mix between "NTP""PTP" types in MO TimerServer.

2.6.40.2 MO Class TimeServer Counters

Table 61 MO class TimeServer counters

Name Position


TS_TimeOffset_1 1 GAUGE

0..264-1 The time offset (in microseconds) that 1% of thnumber of NTP packets/PTP measurementsreceived during the granularity period fallbelow.


0..264-1 The time offset (in microseconds) that10% of the number of NTP packets/PTPmeasurements received during the granularityperiod fall below.

1032/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 61 MO class TimeServer counters

Name Position



0..264-1 The time offset (in microseconds) that50% of the number of NTP packets/PTPmeasurements received during the granularityperiod fall below.

TS_NoPkts 4 PEG 0..264-1 The total number of NTP packets or used PTPmeasurements received during the granularityperiod.

TS_RoundTripDelay_50 5 GAUGE

0..264-1 Indicates that 50% of received NTPpackets/PTP measurements during thegranularity period have a roundtrip delay( in microseconds) that is less thanTS_RoundTripDelay_50.

2.6.41 MO Class TrafficManager (manuallyCreated)

MO class TrafficManager represents attributes of a traffic manager thatmanages the contained queues and a bit rate limit.

104 2/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.41.1 MO Class TrafficManager Parameters

Table 62 MO class TrafficManager parameters


RestartType

Description



Rule: A given MO TrafficManager instance cbe referenced only by one of the following item

• ONE instance of MO EthernetInterface, or

• ONE instance of MO IPInterface that refersdirectly to an instance of MO EthernetInterfaor

• ONE instance of MO IPInterface that refersan instance of MO ML-PPP, or

• ALL instances of MO IPInterface that referinstances of MO VLAN on the same instancMO EthernetInterface.

Rule: On a given MO EthernetInterface, thecan only be references to MO TrafficManagefrom one type of MO, either EthernetInterfacor IPInterface.

schedulerMeanRate

R/W Integer0..232

�10 mo (1)

The maximal mean rate in kilobits/sec of thetraffic shaping scheduler in the egress directioof the interface. This parameter applies to allpackets.

Depending on whether the TrafficManagerinstance is referenced by an MO IPInterfaceMO EthernetInterface, IP headers (and payloare counted or also Ethernet headers are coun

If the value is either "0" or above the bit rate othe physical interface, then there is effectivelyno rate limit and the scheduler will use the fubandwidth of the physical interface.

If the value is non-zero, the scheduler will limthe servicing of this queue-set to, at most, thirate as a mean value.

1052/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description

schedulerMaxBurstSize

R/W Integer0..232

�10 mo (1) The maximum burst size in bytes of the traffic

shaping scheduler in the egress direction of theinterface. This parameter applies to all packets.

Depending on whether the TrafficManagerinstance is referenced by an MO IPInterfaceor MO EthernetInterface, IP headers (andpayload) are counted or also Ethernet headersare counted.

Rule: For an MO TrafficManagerinstance, if schedulerMeanRate > "0",schedulerMaxBurstSize must be greater than,or equal to, the largest MTU size among all theMO instances having a dependency to this MOTrafficManager instance. ("MTU" is 1522 for MOEthernetInterface instances).

diffServAlgDropQThreshold_1

R/W Integer0..232

�18192 mo (1) The maximum depth, in bytes, of queue 1,

beyond which all newly arriving packets aredropped. That is, the applied algorithmic droppeis of the normal tail-drop type. The value "0"designates "no Threshold".The queue must be large enough to hold severapackets if the source is bursty, but not larger thanthe maximum allowed delay based on configuredWAN bandwidth.

diffServMinRateRelative_1

R/W Integer-1,0..1000

0 mo (1) The minimum rate that the scheduler allocatesto queue 1, relative to schedulerMeanRate, inunits of ‰ (per mille).

This queue has strict priority over other queues.

Rule: Can only have value "-1" (strict priority).

Rule: The sum of all diffServMinRateRelative_nmust not exceed "1000". ( "-1" is not includedin sum).

106 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


R/W Integer0..232


beyond which all newly arriving packets aredropped. That is, the applied algorithmic dropis of the normal tail-drop type. The value "0"designates "no Threshold".The queue must be large enough to hold sevepackets if the source is bursty, but not larger tthe maximum allowed delay based on configuWAN bandwidth.



0 mo (1) The minimum rate that the scheduler allocateto queue 2, relative to schedulerMeanRate, inunits of ‰ (per mille).

If the value is "0", then no minimum rate isspecified. For other values, the schedulerensures the servicing of the queue to at leastrate.

Rule: Cannot have value "-1" (never strict poli

Rule: The sum of all diffServMinRateRelativemust not exceed "1000". ( "-1" is not includedin sum).


R/W Integer0..232



1072/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description



0 mo (1) The minimum rate that the scheduler allocates toqueue 3, relative to schedulerMeanRate, in unitsof ‰ (parts per thousand).

If the value is "0", then no minimum rate isspecified. For other values, the schedulerensures the servicing of the queue to at least thisrate.

Rule: Cannot have value "-1" (never strict policy)



R/W Integer0..232









108 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


R/W Integer0..232





0 mo (1) The minimum rate that the scheduler allocatequeue 5, relative to schedulerMeanRate, in unof ‰ (parts per thousand).


Rule: Cannot have value "-1" (never strict poli



R/W Integer0..232



1092/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description








R/W Integer0..232









110 2/1551-LZA 104 102/6 Uen E | 2011-09-08




RestartType

Description


R/W Integer0..232





0 mo (1) The minimum rate that the scheduler allocatequeue 8, relative to schedulerMeanRate, in unof ‰ (parts per thousand).



depQosPolicy R/W MO-DN <emptystring>

mo (1) Reference (use dependency) to the MOQosPolicy instance assigned for the MOTrafficManager.

Rule: Can only refer to an instance of MOQosPolicy.

Rule: When an instance of MO QosPolicyexists, the depQosPolicy must refer to thisQoSPolicy MO


See Reference [5] for recommended formulas when computing the value ofdiffServAlgDropQThreshold_x.

2.6.41.2 MO Class TrafficManager Counters


1112/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 63 MO class TrafficManager counters

Name Position


diffServAlgDropOctets_1 1 PEG 0..264-1 The number of octets dropped due to queueoverflow for queue 1.Depending on whether the MO TrafficManagerinstance is referenced by an MO IPInterface orEthernetInterface, IP headers (and payload)are counted or also Ethernet headers arecounted.

diffServAlgDropPkts_1 2 PEG 0..264-1 The number of packets dropped due to queueoverflow for queue 1.







112 2/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


diffServAlgDropOctets_5 9 PEG 0..264-1 The number of octets dropped due to queueoverflow for queue 5.Depending on whether the MO TrafficManageinstance is referenced by an MO IPInterface oEthernetInterface, IP headers (and payload)are counted or also Ethernet headers arecounted.








1132/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


tmOutOctets_1 17 PEG 0..264-1 The number of octets transmitted on queue 1,including framing characters.Depending on whether the MO TrafficManagerinstance is referenced by an MO IPInterface orEthernetInterface, IP headers (and payload)are counted or also Ethernet headers arecounted.

tmOutpackets_1 18 PEG 0..264-1 The number of packets transmitted on queue 1.









114 2/1551-LZA 104 102/6 Uen E | 2011-09-08



Name Position


tmOutOctets_6 27 PEG 0..264-1 The number of octets transmitted on queue 6including framing characters.Depending on whether the MO TrafficManageinstance is referenced by an MO IPInterface oEthernetInterface, IP headers (and payload)are counted or also Ethernet headers arecounted.

tmOutpackets_6 28 PEG 0..264-1 The number of packets transmitted on queue





2.6.42 MO Class VirtualIPInterface (manuallyCreated)

MO class VirtualIPInterface represents attributes of a virtual interface to anIP stack.

1152/1551-LZA 104 102/6 Uen E | 2011-09-08


2.6.42.1 MO Class VirtualIPInterface Parameters

Table 64 MO class VirtualIPInterface parameters


RestartType

Description



IP_Address R/W IPv4address

0.0.0.0 mo (1)IP address of the virtual IP interface.

The IP address is considered belonging to a /32subnet.

When this attribute changes value, all MOinstances, which have a depIP_Interface attributethat refers to this instance, are affected. Seedetails about the effect under the depIP_Interfaceattribute of the MOs in question.

Note: The following depending MO may beaffected by changed value of this attribute:STN, TGTransport, PingMeasurement,Synchronization, and CESChannel.



2.6.42.2 MO Class VirtualIPInterface Counters

No counters exist.

2.6.43 MO Class VLAN (manuallyCreated)

MO class VLAN represents attributes for a VLAN interface within aVLANGroup. It is a layer 2 interface in terms of the OSI networking model.

2.6.43.1 MO Class VLAN Parameters

Table 65 MO class VLAN parameters


RestartType

Description


Instance identifier of the MO

116 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 65 MO class VLAN parameters


RestartType

Description

tagValue R/W Integer0..4094

1 mo (1)The VLAN tag value to be used on this MO VLinstance.

Rule: The attribute tagValue cannot be the saon two MO VLAN instances on the same MOEthernetInterface.

Rule: The tagValue "0" is used by the systemand cannot be used in an MO VLAN instance

tagged R/W true/false

true mo (1) Determines if the egress Ethernet frames willhave a VLAN tag or not.

Rule: Only one MO VLAN instance per MOEthernetInterface instance can have thisattribute set to "false".

Rule: The tagged attribute must have value"false" if attribute tagValue = "1"

depBridge R/W MO-DN <emptystring>

mo (1) Identifies the MO Bridge instance the VLANconnected to. If empty, the VLAN is terminateon the MO EthernetInterface referenced by tcontainer VLANGroup.

Rule: All MO VLAN instances referencing tosame MO Bridge instance shall have the samvalue for the tagValue attribute.

Rule: No MO IPInterface instance can havea depLinkLayer value pointing to a MO VLANinstance having a non-empty depBridge attribvalue.

Note: If only one single MO VLAN instanceconnects via the depBridge attribute to a MOBridge instance, the traffic received on thatVLAN is discarded.


2.6.43.2 MO Class VLAN Counters

Note: Reset counters at node restart. Reset of all counters, for dependingMOs belonging to the EthernetInterface except EthernetInterfacecounters, will also be performed when switching between layer 3 andlayer 2 (see also IPInterface).

1172/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 66 MO class VLAN counters

Name Position


ifHCInOctets 1 PEG 0..264-1 The total number of octets received on theinterface, including framing characters

ifHCOutOctets 2 PEG 0..264-1 The total number of octets transmitted on theinterface, including framing characters

ifInErrors 3 PEG 0..264-1 The number of inbound packets that containederror preventing them from being deliverableto higher-layer protocol


ifHCInUcastPkts 5 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, which werenot addressed to a multicast or broadcastaddress at this sub-layer.

ifHCOutUcastPkts 6 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere not addressed to a multicast or broadcastaddress at this sub-layer, including those thatwere discarded or not sent.

ifInDiscards 7 PEG 0..264-1 The number of inbound packets which werechosen to be discarded even though no errorshad been detected to prevent their beingdeliverable to a higher-layer protocol.One possible reason for discarding such apacket could be to free up buffer space.

ifOutDiscards 8 PEG 0..264-1 The number of outbound packets which werechosen to be discarded even though no errorshad been detected to prevent their beingtransmitted.One possible reason for discarding such apacket could be to free up buffer space.

ifHCInBroadcastPkts 9 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, which wereaddressed to a broadcast address at thissub-layer.

ifHCOutBroadcastPkts 10 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere addressed to a broadcast address at thissub-layer, including those that were discardedor not sent.

118 2/1551-LZA 104 102/6 Uen E | 2011-09-08


Table 66 MO class VLAN counters

Name Position


ifHCInMulticastPkts 11 PEG 0..264-1 The number of packets, delivered by thissub-layer to a higher (sub-) layer, whichwere addressed to a multicast address atthis sub-layer. For a MAC layer protocol, thisincludes both Group and Functional addresse

ifHCOutMulticastPkts 12 PEG 0..264-1 The total number of packets that higher-levelprotocols requested be transmitted, and whichwere addressed to a multicast address at thissub-layer, including those that were discardedor not sent. For a MAC layer protocol, thisincludes both Group and Functional addresse


2.6.44 MO Class VLANGroup (manuallyCreated)

The MO class VLANGroup is a container for MO class VLAN. It also defineswhich link layer (Ethernet interface) all VLAN's within the VLANGroup areconnected to.

2.6.44.1 MO Class VLANGroup Parameters

Table 67 MO class VLANGroup parameters


RestartType

Description



operationalState

RO enabled/disabled

"enabled": the resource is partially or fullyoperable and available for use."disabled" : the resource is totally inoperableunable to provide service to users.

depLinkLayer R/W MO-DN STN=0,EthernetInterface=0

mo Reference (use dependency) to the link layerassigned for the MO VLANGroup instance.

Rule: Can only refer to an instance of MOEthernetInterface .

2.6.44.2 MO Class VLANGroup Counters

No counters exist.

1192/1551-LZA 104 102/6 Uen E | 2011-09-08


120 2/1551-LZA 104 102/6 Uen E | 2011-09-08

Glossary

Glossary

See Reference [1].

1212/1551-LZA 104 102/6 Uen E | 2011-09-08


122 2/1551-LZA 104 102/6 Uen E | 2011-09-08

Reference List

Reference List

Ericsson documents

[1] Glossary

[2] Library Changes

[3] Command Descriptions

[4] User Guide, Operation and Maintenance

[5] User Guide, Site Router

[6] SIU 02 Description

Other documents

[7] 3GPP TS 32.300 V6.2.0 Configuration Management (CM); Nameconvention for Managed Objects

[8] Requirements for Internet Hosts - Communication Layers, RFC 1122

[9] IP Header Compression over PPP, RFC 3544

[10] Assigned Internet Protocol Numbers

[11] Bidirectional Forwarding Detection, RFC 5880

[12] BFD for IPv4 and IPv6 (Single Hop), RFC 5881

[13] Domain Names - Implementation and Specification, RFC 1035

[14] Textual Conventions for SMIv2, RFC 2579

1232/1551-LZA 104 102/6 Uen E | 2011-09-08

http://www.3gpp.org/ftp/Specs/html-info/32300.htm

http://www.3gpp.org/ftp/Specs/html-info/32300.htm

http://tools.ietf.org/html/rfc1122


http://www.iana.org/assignments/protocol-numbers

http://tools.ietf.org/html/draft-ietf-bfd-base-11

http://tools.ietf.org/html/draft-ietf-bfd-v4v6-1hop-11



Alex 0181

Documents

Transcript of Alex 0181