SIST ETS 300 377-2:1997

• Abstract:

  MOCS proforma for the Q3 LE configuration management specification.

• Status: Published
• Publication Date: 31-Oct-1997
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-1997
• Due Date: 01-Nov-1997
• Completion Date: 01-Nov-1997
• Ref Project: ETSI ETS 300 377-2 ed.1 (1995-11) - Q3 interface at the Local Exchange (LE) for configuration management of V5 interfaces and associated customer profiles; Part 2: Managed Objects Conformance Statement (MOCS) proforma specification

SIST ETS 300 377-2:1997 is the Slovenian version of ETS 300 377-2 from ETSI. It provides the Managed Object Conformance Statement (MOCS) proforma for the Q3 interface at the Local Exchange (LE) for configuration management of V5 interfaces and associated customer profiles. Suppliers and implementers use it to state, in a standard form, which managed object classes, packages, attributes, actions and notifications their implementation supports.

What does SIST ETS 300 377-2:1997 specify?

SIST ETS 300 377-2:1997 specifies the MOCS proforma for the base standard ETS 300 377-1. Its purpose is to identify the mandatory, conditional and optional elements of the information model used for Q3 configuration management of V5 interfaces and associated customer profiles.

The document is organized as a short front matter, then four clauses and one informative annex:

• Clause 1 gives the scope.
• Clause 2 lists the normative references.
• Clause 3 gives definitions, symbols and abbreviations.
• Clause 4 contains the conformance statements, arranged as one managed object class after another.
• Annex A is a bibliography.

Clause 4 is the practical core of the standard. It gives a proforma that suppliers can complete to declare support for each managed object class, including name bindings, packages, attributes, actions, notifications and parameters. The foreword also says users may freely reproduce the MOCS proforma in clause 4 for its intended purpose and may publish the completed MOCS.

What are the key requirements of SIST ETS 300 377-2:1997?

The standard is not a design specification for equipment behavior. SIST ETS 300 377-2:1997 is a conformance proforma: it tells a supplier what support information to declare, and how to mark it, for each managed object class in the Q3 information model.

How the conformance tables work

Clause 3 defines the table notation used throughout the proforma:

• m means mandatory.
• c means conditional.
• o means optional.
• x means prohibited.
• - means not applicable.

Clause 3 also defines the support column codes:

• Y implemented
• N not implemented
• lg ignored

In practice, this lets a supplier state exactly which parts of the model are implemented, and which are only present when a condition is met.

What each managed object class must cover

Clause 4 repeats the same structure for each managed object class. For every class, the supplier completes tables for:

• object class support
• feature support
• name bindings
• packages
• attributes
• attribute groups when present
• actions
• notifications
• parameters

That structure matters because it forces a consistent declaration of support across all parts of the management model, not just a yes/no statement.

Main object classes covered

Clause 4 contains statements for 20 managed object classes, including:

• v5Interface
• v5Ttp
• v5TimeSlot
• v5Provision
• commChannel
• isdnCommPath, pstnCommPath, bccCommPath, controlCommPath, protCommPath and linkControlCommPath
• v5ProtectionGroup and v5ProtectionUnit
• virtualAccessChannel, virtualPrimaryRateAccess, virtualBasicRateAccess, virtualAnalogueAccess and virtualLeasedAccess
• v5BearerChannelReservation and v5LeasedLineReservation

For a buyer or integrator, this is the list to check against the product’s actual management scope.

Conditional support depends on the system option

Many tables make support conditional on capabilities such as:

• configuration management support
• fault management support
• whether the information model is used for provisioning only
• V5.2 support
• line test facilities
• whether service profiles are assigned on a per-channel basis
• whether there is a remote digital section or performance parameters are monitored against a threshold

This matters because a product may legitimately support only part of the proforma, depending on the network role and option set.

Examples of the declared management content

The first class, v5Interface, includes mandatory items such as supportedProtocolVersion, serverV5Ttps and clientUserPorts, plus packages and notifications tied to object creation, deletion, attribute change, state change and relationship change.

Other classes focus on transport and access relationships. For example, commChannel and the commPath classes declare key pointers and identifiers that link channels, time slots and interfaces. The protection classes cover the relationship between a v5ProtectionGroup and a v5ProtectionUnit, including the switching and reporting behavior associated with protection.

Actions and notifications are part of the claim

Where actions exist, the supplier states support in confirmed and non-confirmed modes. Where notifications exist, the supplier indicates whether object creation, deletion, state change, relationship change or attribute value change notifications are supported, and what notification fields are present.

This is important in practice because management systems often depend on alarms, change notifications and remote actions for provisioning and troubleshooting.

What terms does SIST ETS 300 377-2:1997 define?

• configuration management - The set of packages in an object class that support creation, deletion and modification of instances of that class.
• fault management - Additional packages that support fault reporting, logging and similar fault handling functions.
• performance management - Additional packages that support traffic measurements and threshold reporting.
• MOCS - Managed Object Conformance Statement, the standard form used to declare conformance to a managed object class.
• AN - Access Network, the network side used in the related V5 interface standards.
• LE - Local Exchange, the exchange location for which the Q3 interface is specified here.
• TMN - Telecommunication Network Management, the management context used by the standard.

Who uses SIST ETS 300 377-2:1997?

SIST ETS 300 377-2:1997 is used by suppliers of implementations that claim conformance to the managed object classes in the Q3 interface specification. It is also used by telecom equipment vendors, network management system suppliers, test laboratories and acceptance teams who need a common way to record what a product supports.

In practice, it helps when:

• completing a conformance statement for a product
• checking whether a Local Exchange implementation fits a V5 management model
• comparing vendor support for managed object classes, packages and notifications
• preparing conformance tests or procurement checks for TMN-based management

What changed in SIST ETS 300 377-2:1997 from the previous edition?

SIST ETS 300 377-2:1997 corresponds to ETS 300 377-2 Edition 1 and is marked as identical to it.

Which standards are used with SIST ETS 300 377-2:1997?

Clause 2 names the standards used directly with this document:

• ETS 300 377-1 - the base Q3 interface specification that this part supports.
• ETS 300 324-2 - the PICS proforma for the V5.1 interface, referenced where V5.1-specific conditions apply.
• ETS 300 347-2 - the PICS proforma for the V5.2 interface, referenced where V5.2-specific conditions apply.
• ISO/IEC 9646-7 - the conformance testing methodology and framework part used for implementation conformance statements.

The foreword also lists related ETSI standards:

• ETS 300 376 - Q3 interface at the Access Network for configuration management of V5 interfaces and associated user ports.
• ETS 300 378 - Q3 interface at the Access Network for fault and performance management of V5 interfaces and associated user ports.
• ETS 300 379 - Q3 interface at the Local Exchange for fault and performance management of V5 interfaces and associated customer profiles.

Annex A adds bibliography entries for I-ETS 300 291, ITU-T Recommendation M.3100, ITU-T Recommendation X.721 | ISO/IEC 10165-2, and ITU-T Recommendation X.724.

What does the SIST ETS 300 377-2:1997 document contain?

The document contains a complete set of proforma tables for 20 managed object classes, with separate tables for object class support, feature support, name bindings, packages, attributes, actions and notifications. It also contains the symbol conventions used in those tables, including the meaning of the status and support codes.

For the reader, that means the document is mainly a structured checklist for conformance declaration, not a narrative specification of behavior. For testing or certification, the useful parts are the tables that show what support must be stated for each class and which items become mandatory when a condition is met.

SLOVENSKI STANDARD
01-november-1997
Signalizacijski protokoli in komutacija (SPS) - Vmesnik Q3 v krajevni centrali (LE)
za upravljanje in konfiguriranje vmesnikov V5 in pridruženih uporabniških profilov
- 2. del: Proformna specifikacija izjave o skladnosti objektov upravljanja (MOCS)
Signalling Protocols and Switching (SPS) - Q3 interface at the Local Exchange (LE) for
configuration management of V5 interfaces and associated customer profiles; Part 2:
Managed Objects Conformance Statement (MOCS) proforma specification
Ta slovenski standard je istoveten z: ETS 300 377-2 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 377-2
TELECOMMUNICATION November 1995
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03013.4
ICS: 35.100.70
TMN, information model, Q3 interface, LE, V5 interface, configuration, management, MOCS
Key words:
Signalling Protocols and Switching (SPS);
Q3 interface at the Local Exchange (LE)
for configuration management of V5 interfaces and
associated customer profiles;
Part 2: Managed Object Conformance Statement (MOCS)
proforma specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
*
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1995. All rights reserved.

Page 2
ETS 300 377-2: November 1995
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 377-2: November 1995
Contents
Foreword .7
Introduction.7
1 Scope .9
2 Normative references.9
3 Definitions, symbols and abbreviations.9
3.1 Definitions .9
3.2 Symbols .9
3.3 Abbreviations .10
4 Statements of conformance .11
4.1 Statement of conformance to managed object class v5Interface.11
4.1.1 Name bindings .11
4.1.2 Packages.11
4.1.3 Attributes .12
4.1.4 Attribute groups .13
4.1.5 Actions.13
4.1.6 Notifications.13
4.1.7 Parameters.14
4.2 Statement of conformance to managed object class v5Ttp .14
4.2.1 Name bindings .15
4.2.2 Packages.15
4.2.3 Attributes .16
4.2.4 Attribute groups .17
4.2.5 Actions.17
4.2.6 Notifications.17
4.2.7 Parameters.18
4.3 Statement of conformance to managed object class v5TimeSlot .18
4.3.1 Name bindings .19
4.3.2 Packages.19
4.3.3 Attributes .19
4.3.4 Attribute groups .20
4.3.5 Actions.20
4.3.6 Notifications.21
4.3.7 Parameters.21
4.4 Statement of conformance to managed object class v5Provision.21
4.4.1 Name bindings .22
4.4.2 Packages.22
4.4.3 Attributes .22
4.4.4 Attribute groups .23
4.4.5 Actions.23
4.4.6 Notifications.23
4.4.7 Parameters.24
4.5 Statement of conformance to managed object class commChannel .24
4.5.1 Name bindings .24
4.5.2 Packages.24
4.5.3 Attributes .25
4.5.4 Attribute groups .25
4.5.5 Actions.25
4.5.6 Notifications.26
4.5.7 Parameters.26
4.6 Statement of conformance to managed object class isdnCommPath.26
4.6.1 Name bindings .27
4.6.2 Packages.27

Page 4
ETS 300 377-2: November 1995
4.6.3 Attributes. 27
4.6.4 Attribute groups . 28
4.6.5 Actions . 28
4.6.6 Notifications . 28
4.6.7 Parameters . 29
4.7 Statement of conformance to managed object class pstnCommPath. 29
4.7.1 Name bindings. 29
4.7.2 Packages. 30
4.7.3 Attributes. 30
4.7.4 Attribute groups . 31
4.7.5 Actions . 31
4.7.6 Notifications . 31
4.7.7 Parameters . 31
4.8 Statement of conformance to managed object class bccCommPath . 31
4.8.1 Name bindings. 32
4.8.2 Packages. 32
4.8.3 Attributes. 32
4.8.4 Attribute groups . 33
4.8.5 Actions . 33
4.8.6 Notifications . 33
4.8.7 Parameters . 34
4.9 Statement of conformance to managed object class controlCommPath. 34
4.9.1 Name bindings. 34
4.9.2 Packages. 35
4.9.3 Attributes. 35
4.9.4 Attribute groups . 36
4.9.5 Actions . 36
4.9.6 Notifications . 36
4.9.7 Parameters . 36
4.10 Statement of conformance to managed object class protCommPath . 36
4.10.1 Name bindings. 37
4.10.2 Packages. 37
4.10.3 Attributes. 37
4.10.4 Attribute groups . 38
4.10.5 Actions . 38
4.10.6 Notifications . 38
4.10.7 Parameters . 39
4.11 Statement of conformance to managed object class linkControlCommPath. 39
4.11.1 Name bindings. 39
4.11.2 Packages. 40
4.11.3 Attributes. 40
4.11.4 Attribute groups . 41
4.11.5 Actions . 41
4.11.6 Notifications . 41
4.11.7 Parameters . 41
4.12 Statement of conformance to managed object class v5ProtectionGroup. 41
4.12.1 Name bindings. 42
4.12.2 Packages. 42
4.12.3 Attributes. 42
4.12.4 Attribute groups . 43
4.12.5 Actions . 43
4.12.6 Notifications . 43
4.12.7 Parameters . 43
4.13 Statement of conformance to managed object class v5ProtectionUnit . 44
4.13.1 Name bindings. 44
4.13.2 Packages. 44
4.13.3 Attributes. 45
4.13.4 Attribute groups . 45
4.13.5 Actions . 45
4.13.6 Notifications . 45
4.13.7 Parameters . 45
4.14 Statement of conformance to managed object class virtualAccessChannel . 46
4.14.1 Name bindings. 46

Page 5
ETS 300 377-2: November 1995
4.14.2 Packages.46
4.14.3 Attributes .47
4.14.4 Attribute groups .48
4.14.5 Actions.48
4.14.6 Notifications.48
4.14.7 Parameters.49
4.15 Statement of conformance to managed object class virtualPrimaryRateAccess .50
4.15.1 Name bindings .50
4.15.2 Packages.50
4.15.3 Attributes .51
4.15.4 Attribute groups .52
4.15.5 Actions.52
4.15.6 Notifications.52
4.15.7 Parameters.53
4.16 Statement of conformance to managed object class virtualBasicRateAccess.54
4.16.1 Name bindings .54
4.16.2 Packages.54
4.16.3 Attributes .55
4.16.4 Attribute groups .56
4.16.5 Actions.56
4.16.6 Notifications.57
4.16.7 Parameters.57
4.17 Statement of conformance to managed object class virtualAnalogueAccess .58
4.17.1 Name bindings .58
4.17.2 Packages.58
4.17.3 Attributes .59
4.17.4 Attribute groups .60
4.17.5 Actions.60
4.17.6 Notifications.60
4.17.7 Parameters.61
4.18 Statement of conformance to managed object class virtualLeasedAccess .62
4.18.1 Name bindings .62
4.18.2 Packages.62
4.18.3 Attributes .63
4.18.4 Attribute groups .64
4.18.5 Actions.64
4.18.6 Notifications.64
4.18.7 Parameters.65
4.19 Statement of conformance to managed object class v5BearerChannelReservation .66
4.19.1 Name bindings .66
4.19.2 Packages.66
4.19.3 Attributes .67
4.19.4 Attribute groups .67
4.19.5 Actions.67
4.19.6 Notifications.68
4.19.7 Parameters.68
4.20 Statement of conformance to managed object class v5LeasedLineReservation.69
4.20.1 Name bindings .69
4.20.2 Packages.69
4.20.3 Attributes .70
4.20.4 Attribute groups .70
4.20.5 Actions.70
4.20.6 Notifications.70
4.20.7 Parameters.71
Annex A (informative): Bibliography.72
History.73

Page 6
ETS 300 377-2: November 1995
Blank page
Page 7
ETS 300 377-2: November 1995
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 2 of a multi-part standard as described below:
Part 1: "Q3 interface specification at the Local Exchange (LE) for configuration management of
V5 interfaces and associated customer profiles";
Part 2: "Managed Object Conformance Statement (MOCS) proforma specification";
The following standards are directly related to this ETS:
ETS 300 376: "Q3 interface at the Access Network (AN) for configuration management of V5 interfaces
and associated user ports";
ETS 300 378: "Q3 interface at the Access Network (AN) for fault and performance management of V5
interfaces and associated user ports";
ETS 300 379: "Q3 interface at the Local Exchange (LE) for fault and performance management of V5
interfaces and associated customer profiles".
Transposition dates
Date of adoption of this ETS: 17 November 1995
Date of latest announcement of this ETS (doa): 28 February 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1996
Date of withdrawal of any conflicting National Standard (dow): 31 August 1996
Introduction
The purpose of this Managed Object Conformance Statement (MOCS) proforma is to provide a
mechanism for a supplier of an implementation of a recommendation/standard which claims conformance
to a managed object class to provide conformance information, including management information, in a
standard form.
Page 8
ETS 300 377-2: November 1995
Blank page
Page 9
ETS 300 377-2: November 1995
1 Scope
This second part of ETS 300 377 provides the Managed Object Conformance Statement (MOCS)
proforma for the base standard ETS 300 377-1 [1]. It identifies the mandatory, conditional and optional
elements of the information model specified in ETS 300 377-1 [1].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 377-1 (1994): "Signalling Protocols and Switching (SPS); Q3 interface
at the Local Exchange (LE) for configuration management of V5 interfaces and
associated customer profiles; Part 1: Q3 interface specification".
[2] ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statements (PICS)
proforma".
[3] ETS 300 347-2 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.2 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statements (PICS)
proforma".
[4] ISO/IEC 9646-7: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
configuration management: Each object class contains packages supporting creation, deletion and
modification of instances of that object class. This is referred to as configuration management. In some
cases, these packages are conditional.
fault management: Some object classes contain packages, in addition to those specified for
configuration management, supporting fault reporting, logging, etc. This is referred to as fault
management. Typically, these packages are conditional.
performance management: Some object classes contain packages, in addition to those specified for
configuration management, supporting traffic measurements, reports when thresholds are exceeded, etc.
This is referred to as performance management. Typically, these packages are conditional.
3.2 Symbols
The following common notation is used for the tables in this ETS:
a first part of a table row
b second part of a table row
c third part of a table row
Page 10
ETS 300 377-2: November 1995
The following common notation, defined in ISO/IEC 9646-7 [4], is used for the "Status" column:
c conditional
m mandatory
o optional
x prohibited
- not applicable
The following common notation, defined in ISO/IEC 9646-7 [4], is used for the "Support" column:
lg the item is ignored (i.e., processed syntactically but not semantically)
N not implemented
Y implemented
- not applicable
The following symbolic abbreviations are used throughout the proforma tables:
v5Q(LE)-nb ccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)
informationModel(0) nameBinding(6)
v5Q(LE)-pkg ccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)
informationModel(0) package(4)
v5Q(LE)-att ccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)
informationModel(0) attribute(7)
v5Q(LE)-act ccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)
informationModel(0) action(9)
v5Q(LE)-not ccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)
informationModel(0) notification(10)
admin-nb ccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) nameBinding(6)
admin-pkg ccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) package(4)
admin-att ccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) attribute(7)
smi2-pkg joint-iso-ccitt ms(9) smi(3) part2(2) packages(4)
smi2-att joint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)
smi2-not joint-iso-ccitt ms(9) smi(3) part2(2) notification(10)
m3100-pkg ccitt recommendation m gnm(3100) informationModel(0) package(4)
m3100-att ccitt recommendation m gnm(3100) informationModel(0) attribute(7)
3.3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
LE Local Exchange
MOCS Managed Object Conformance Statement
TMN Telecommunication Network Management

Page 11
ETS 300 377-2: November 1995
4 Statements of conformance
Notwithstanding the provisions of the copyright Clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the MOCS proforma in this clause so that it can be used for its
intended purposes and may further publish the completed MOCS.
4.1 Statement of conformance to managed object class v5Interface
Table 1: Object class support
Index Managed object class template label Value of OBJECT IDENTIFIER for the class Status Support
1.1 v5Interface {ccitt(0) identified-organization(4) etsi(0) m
v5LeConfigurationManagement(377)
informationModel(0) managedObjectClass(3) 1}
The supplier of the implementation shall state whether or not all mandatory features of the object listed
above are supported in table 2.
Table 2: Feature support
Index Sub-Index Support
2.1 2.1.1 Is configuration management supported?
2.1.2 Are all mandatory features for configuration management
supported?
2.2 2.2.1 Is fault management supported?
2.2.2 Are all mandatory features for fault management supported?
4.1.1 Name bindings
The supplier of the implementation shall state which name bindings of the managed object class are
supported, in the "Support" and "Additional information" columns of table 3.
Table 3: Name binding support
Index Name binding Value of OBJECT Superior object class template label Status Support
template label IDENTIFIER
3.1a v5Interface - {v5Q(LE)-nb 1} managedElement AND SUBCLASSES m
managedElement
Table 3 (concluded): Name binding support
Status Support
Index Object Object Object Object Additional information
creation deletion creation deletion
3.1b c c
c: if 2.1.1 then m else -.
4.1.2 Packages
The supplier of the implementation shall state whether or not the packages specified by this managed
object of this class are supported, in table 4.
Packages of superclasses which are not applicable are listed in the package support table only. The
associated attributes, actions and notifications are not mentioned in the following tables.

Page 12
ETS 300 377-2: November 1995
Table 4: Package support
Index Package label Value of OBJECT IDENTIFIER Status Support
4.1 peerManagedElementPackage {v5Q(LE)-pkg 5} o
4.2 supportedByObjectListPackage {v5Q(LE)-pkg 7} c1
4.3 relationshipChangeNotificationPackage {v5Q(LE)-pkg 6} o
4.4 commonDeleteBehaviourPackage {v5Q(LE)-pkg 2} m
4.5 operationalStatePackage {m3100-pkg 19} o
4.6 v5availabilityStatusPackage {smi2-pkg 22} o
4.7 userLabelPackage {m3100-pkg 32} o
4.8 locationNamePackage {m3100-pkg 17} o
4.9 objectManagementNotificationsPackage {m3100-pkg 20} o
4.10 stateChangeNotificationsPackage {m3100-pkg 28} o
4.11 tmnCommunicationsAlarmInformationPackage {m3100-pkg 30} c2
4.12 alarmSeverityAssignmentPointerPackage {m3100-pkg 3} c2
4.13 packagesPackage {smi2-pkg 16} m
4.14 allomorphicPackage {smi2-pkg 17} o
c1: if the information model is not only used for provisioning then m else -.
c2: if 2.2.1 then m else -.
4.1.3 Attributes
The supplier of the implementation shall state whether or not the attributes specified by all the packages
instantiated in a managed object class definition are supported, in the "Support" and "Additional
information" columns of table 5. The supplier of the implementation shall indicate support for each of the
operations for each attribute supported.
Table 5: Attribute support
Index Attribute template label Value of OBJECT IDENTIFIER Status Support
5.1a v5InterfaceId {v5Q(LE)-att 34} m
5.2a peerManagedElementId {v5Q(LE)-att 25} c1
5.3a supportedProtocolVersion {v5Q(LE)-att 31} m
5.4a serverV5Ttps {v5Q(LE)-att 30} m
5.5a clientUserPorts {v5Q(LE)-att 14} m
5.6a operationalState {smi2-att 35} c2
5.7a availabilityStatus {smi2-att 33} c3
5.8a supportedByObjectList {m3100-att 40} c4
5.9a userLabel {m3100-att 50} c5
5.10a locationName {m3100-att 27} c6
5.11a objectClass {smi2-att 65} m
5.12a nameBinding {smi2-att 63} m
5.13a packages {smi2-att 66} m
5.14a allomorphs {smi2-att 50} c7
c1: if 4.1 then m else -. c4: if 4.2 then m else -. c7: if 4.14 then m else -.
c2: if 4.5 then m else -. c5: if 4.7 then m else -.
c3: if 4.6 then m else -. c6: if 4.8 then m else -.
Table 5 (continued): Attribute support
Status
Index SetByCreate Get Replace Add Remove SetToDefault
5.1b o m x x x x
5.2b m m m x x x
5.3b m m x x x x
5.4b x m x x x x
5.5b x m x x x x
5.6b x m x x x x
5.7b x m x x x x
5.8b m m x x x x
5.9b m m m x x x
5.10b m m m x x x
5.11b m m x x x x
5.12b m m x x x x
5.13b m m x x x x
5.14b m m x x x x
Page 13
ETS 300 377-2: November 1995
Table 5 (concluded): Attribute support
Support
Index SetByCreate Get Replace Add Remove SetToDefault Additional information
5.1c
5.2c
5.3c
5.4c
5.5c
5.6c
5.7c
5.8c
5.9c
5.10c
5.11c
5.12c
5.13c
5.14c
4.1.4 Attribute groups
There are no attribute groups specified for this managed object class.
4.1.5 Actions
The supplier of the implementation shall state whether or not the actions specified by all the packages
instantiated in a managed object of this class are supported, in the "Support" and "Additional information"
columns of table 6. The supplier of the implementation shall indicate support in terms on the confirmed
and non-confirmed modes.
Table 6: Action support
Index Action type template label Value of action type Status Support Additional information
identifier
6.1 setReciprocalPointer {v5Q(LE)-act 1} m
6.2 releaseReciprocalPointer {v5Q(LE)-act 2} m
6.3 restart {v5Q(LE)-act 14} m
6.4 systemStartup {v5Q(LE)-act 16} m
4.1.6 Notifications
The supplier of the implementation shall state whether or not the notifications specified by all the
packages instantiated in a managed object of this class are supported, in the "Support" and "Additional
information" columns of table 7. The supplier of the implementation shall indicate support in terms on the
confirmed and non-confirmed modes.
Table 7: Notification support
Support
Index Notification type Value of notification Status Confirmed Non- Additional information
template label type identifier confirmed
7.1a objectCreation {smi2-not 6} c1
7.2a objectDeletion {smi2-not 7} c1
7.3a attributeValueChange {smi2-not 1} c1
7.4a stateChange {smi2-not 14} c2
7.5a relationshipChange {smi2-not 12} c3
7.6a restartResult {v5Q(LE)-not 11} m
7.7a systemStartupResult {v5Q(LE)-not 12} m
c1: if 4.9 then m else -. c2 if 4.10 then m else -. c3 if 4.3 then m else -.

Page 14
ETS 300 377-2: November 1995
Table 7 (concluded): Notification support
Index Sub-index Notification field Value of object Status Support Additional information
name label identifier of attribute
type associated with
field
7.1b 7.1.1 sourceIndicator {smi2-att 26} o
7.1.2 attributeList {smi2-att 9} o
7.1.3 notificationIdentifier {smi2-att 16} o
7.1.4 correlatedNotifications {smi2-att 12} o
7.1.5 additionalText {smi2-att 7} o
7.1.6 additionalInformation {smi2-att 6} o
7.2b 7.2.1 sourceIndicator {smi2-att 26} o
7.2.2 attributeList {smi2-att 9} o
7.2.3 notificationIdentifier {smi2-att 16} o
7.2.4 correlatedNotifications {smi2-att 12} o
7.2.5 additionalText {smi2-att 7} o
7.2.6 additionalInformation {smi2-att 6} o
7.3b 7.3.1 sourceIndicator {smi2-att 26} o
7.3.2 attributeIdentifierList {smi2-att 8} o
7.3.3 AttributeValueChange {smi2-att 10} m
Definition
7.3.4 notificationIdentifier {smi2-att 16} o
7.3.5 correlatedNotifications {smi2-att 12} o
7.3.6 additionalText {smi2-att 7} o
7.3.7 additionalInformation {smi2-att 6} o
7.4b 7.4.1 sourceIndicator {smi2-att 26} o
7.4.2 attributeIdentifierList {smi2-att 8} o
7.4.3 stateChangeDefinition {smi2-att 28} m
7.4.4 notificationIdentifier {smi2-att 16} o
7.4.5 correlatedNotifications {smi2-att 12} o
7.4.6 additionalText {smi2-att 7} o
7.4.7 additionalInformation {smi2-att 6} o
7.5b 7.5.1 sourceIndicator {smi2-att 26} o
7.5.2 attributeIdentifierList {smi2-att 8} o
7.5.3 relationshipChange {smi2-att 20} m
Definition
7.5.4 notificationIdentifier {smi2-att 16} o
7.5.5 correlatedNotifications {smi2-att 12} o
7.5.6 additionalText {smi2-att 7} o
7.5.7 additionalInformation {smi2-att 6} o
4.1.7 Parameters
There are no parameters specified for the configuration management in this managed object class.
4.2 Statement of conformance to managed object class v5Ttp
Table 8: Object class support
Index Managed object class template label Value of OBJECT IDENTIFIER for the class Status Support
8.1 v5Ttp {ccitt(0) identified-organization(4) etsi(0) m
v5LeConfigurationManagement(377)
informationModel(0) managedObjectClass(3) 2}
The supplier of the implementation shall state whether or not all mandatory features of the object listed
above are supported in table 9.
Table 9: Feature support
Index Sub-Index Support
9.1 9.1.1 Is configuration management supported?
9.1.2 Are all mandatory features for configuration management
supported?
9.2 9.2.1 Is fault management supported?
9.2.2 Are all mandatory features for fault management supported?

Page 15
ETS 300 377-2: November 1995
4.2.1 Name bindings
The supplier of the implementation shall state which name bindings of the managed object class are
supported, in the "Support" and "Additional information" columns of table 10.
Table 10: Name binding support
Index Name binding Value of OBJECT Superior object class template label Status Support
template label IDENTIFIER
10.1a v5Ttp - managedElement {v5Q(LE)-nb 2} managedElement AND SUBCLASSES m
Table 10 (concluded): Name binding support
Status Support
Index Object Object Object Object Additional information
creation deletion creation deletion
10.1b c c
c: if 9.1.1 then m else -.
4.2.2 Packages
The supplier of the implementation shall state whether or not the packages specified by this managed
object of this class are supported, in table 11.
Packages of superclasses which are not applicable are listed in the package support table only. The
associated attributes, actions and notifications are not mentioned in the following tables.
Table 11: Package support
Index Package label Value of OBJECT IDENTIFIER Status Support
11.1 neSpecificPointerPackage {v5Q[LE)-pkg 4} o
11.2 v5AvailabilityStatusPackage {v5Q[LE)-pkg 8} o
11.3 commonDeleteBehaviourPackage {v5Q[LE)-pkg 2} m
11.4 operationalStatePackage {m3100-pkg 19} m
11.5 administrativeStatePackage {smi2-pkg 14} m
11.6 supportableClientListPackage {m3100-pkg 27} o
11.7 ttpInstancePackage {m3100-pkg 31} m
11.8 createDeleteNotificationPackage {m3100-pkg 10} m
11.9 stateChangeNotificationPackage {m3100-pkg 28} o
11.10 attributeValueChangeNotificationPackage {m3100-pkg 4} o
11.11 crossConnectionPointerPackage {m3100-pkg 11} -
11.12 characteristicInformationPackage {m3100-pkg 7} o
11.13 networkLevelPackage {m3100-pkg 18} -
11.14 tmnCommunicationsAlarmInformationPackage {m3100-pkg 30} c
11.15 alarmSeverityAssignmentPointerPackage {m3100-pkg 3} c
11.16 packagesPackage {smi2-pkg 16} m
11.17 allomorphicPackage {smi2-pkg 17} o
c: if 9.2.1 then m else -.
Page 16
ETS 300 377-2: November 1995
4.2.3 Attributes
The supplier of the implementation shall state whether or not the attributes specified by all the packages
instantiated in a managed object class definition are supported, in the "Support" and "Additional
information" columns of table 12. The supplier of the implementation shall indicate support for each of the
operations for each attribute supported.
Table 12: Attribute support
Index Attribute template label Value of OBJECT IDENTIFIER Status Support
12.1a assocV5Interface {v5Q(LE)-att 8} m
12.2a linkId {v5Q(LE)-att 21} m
12.3a blockingStatus {v5Q(LE)-att 13} m
12.4a supportedByObjectList {m3100-att 40} m
12.5a neSpecificPointer {v5Q(LE)-att 22} c1
12.6a operationalState {smi2-att 35} m
12.7a availabilityStatus {smi2-att 33} c2
12.8a upstreamConnectivityPointer {m3100-att 49} m
12.9a administrativeState {smi2-att 31} m
12.10a supportableClientList {smi2-att 39} c3
12.11a tTPId {m3100-att 48} m
12.12a downstreamConnectivityPointer {m3100-att 19} m
12.13a characteristicInformation {m3100-att 8} c4
12.14a objectClass {smi2-att 65} m
12.15a nameBinding {smi2-att 63} m
12.16a packages {smi2-att 66} m
12.17a allomorphs {smi2-att 50} c5
c1: if 11.1 then m else -. c4: if 11.12 then m else -.
c2: if 11.2 then m else -. c5: if 11.17 then m else -.
c3: if 11.6 then m else -.
Table 12 (continued): Attribute support
Status
Index SetByCreate Get Replace Add Remove SetToDefault
12.1b x m x x x x
12.2b m m m x x x
12.3b m m x x x x
12.4b m m x x x x
12.5b m m x x x x
12.6b x m x x x x
12.7b x m x x x x
12.8b o m x x x x
12.9b m m m x x x
12.10b m m x x x x
12.11b o m x x x x
12.12b o m x x x x
12.13b m m x x x x
12.14b m m x x x x
12.15b m m x x x x
12.16b m m x x x x
12.17b m m x x x x
Page 17
ETS 300 377-2: November 1995
Table 12 (concluded): Attribute support
Support
Index SetByCreate Get Replace Add Remove SetToDefault Additional information
12.1c
12.2c
12.3c
12.4c
12.5c
12.6c
12.7c
12.8c
12.9c
12.10c
12.11c
12.12c
12.13c
12.14c
12.15c
12.16c
12.17c
4.2.4 Attribute groups
There are no attribute groups specified for this managed object class.
4.2.5 Actions
The supplier of the implementation shall state whether or not the actions specified by all the packages
instantiated in a managed object of this class are supported, in the "Support" and "Additional information"
columns of table 13. The supplier of the implementation shall indicate support in terms on the confirmed
and non-confirmed modes.
Table 13: Action support
Index Action type template label Value of action type Status Support Additional information
identifier
13.1 checkLinkId {v5Q(LE)-act 13} c
c: if v5.2 then m else -.
4.2.6 Notifications
The supplier of the implementation shall state whether or not the notifications specified by all the
packages instantiated in a managed object of this class are supported, in the "Support" and "Additional
information" columns of table 14. The supplier of the implementation shall indicate support in terms on the
confirmed and non-confirmed modes.
Table 14: Notification support
Support
Index Notification type Value of notification Status Confirmed Non- Additional information
template label type identifier confirmed
14.1a objectCreation {smi2-not 6} m
14.2a objectDeletion {smi2-not 7} m
14.3a attributeValueChange {smi2-not 1} c1
14.4a stateChange {smi2-not 14} c2
14.5a shutdownRejected {v5(LE
...