ISO/IEC 10742:1994
(Main)Information technology - Telecommunications and information exchange between systems - Elements of management information related to OSI Data Link Layer standards
Information technology - Telecommunications and information exchange between systems - Elements of management information related to OSI Data Link Layer standards
Provides the specification of management information within an Open System related to those operations of the OSI Data Link Layer specified by the specifications in this document.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Éléments de l'information de gestion liés aux normes de la couche de liaison de données OSI
General Information
Relations
Overview
ISO/IEC 10742:1994 - Information technology - Telecommunications and information exchange between systems - Elements of management information related to OSI Data Link Layer standards - specifies the management information model for the OSI Data Link Layer. It defines the set of managed object classes, their relationships and attributes, and the action-type operations available to systems management for Data Link Layer functions. The standard is focused on information definitions (what to manage) rather than on how management is implemented.
Key topics
- Managed object definitions and hierarchy
- Core objects include the Data Link Subsystem, Data Link Entity, Data Link Service Access Point (DLSAP), LAPB Data Link Entity, MAC and LLC related managed objects (e.g., SLP machines, connections, initial-value objects).
- GDMO and ASN.1 modules
- Uses GDMO templates (Guidelines for the Definition of Managed Objects) and provides an ASN.1 module to represent management information syntactically.
- Attributes, relationships and operations
- Specifies attribute types, relationship attributes and allowed action operations for OSI systems management in accordance with the Structure of Management Information.
- Conformance
- Defines conformance requirements to ISO/IEC 10742 and protocol-specific conformance criteria.
- Normative and informative references
- Cross-references ISO/IEC OSI management and layering standards (e.g., ISO 7498-1, ISO/IEC 10165 series, ISO/IEC 8802-2/3), ASN.1, and related Data Link protocols such as LAPB and LLC.
- Annexes
- Includes object identifier allocation, IEEE 802.1 common models, ASN.1 modules, shorthand object descriptions and usage examples.
Applications
- Network equipment vendors and firmware developers implementing OSI-compliant Data Link protocols (LAPB, LLC, MAC) use this standard to expose consistent management information.
- Network management system (NMS) designers and systems integrators use the managed object definitions to model Data Link Layer state, events and configuration within management consoles.
- Standards bodies and implementers referencing GDMO/ASN.1 representations for interoperability testing and conformance validation.
- Telecommunications and enterprise network architects who require a formalized management information model for Data Link Layer monitoring, fault reporting and configuration.
Who should use it
- Telecom and networking engineers, NMS developers, protocol implementers, and compliance/test laboratories working with OSI Data Link Layer management and device interoperability.
Related standards
- ISO 7498-1 (OSI reference model)
- ISO/IEC 10165 series (Structure of Management Information)
- ISO/IEC 8802-2, ISO/IEC 8802-3 (LLC, MAC/CSMA/CD)
- ISO/IEC 8824 (ASN.1)
- ISO/IEC 11575 (Protocol mappings for OSI Data Link Service)
Keywords: ISO/IEC 10742:1994, OSI Data Link Layer management, managed objects, GDMO, ASN.1, LAPB, LLC, MAC, DLSAP, network management.
Standards Content (Sample)
INTERNATIONAL lSO/IEC
STANDARD 10742
First edition
1994-08-01
Information technology -
Telecommunications ’and information
exchange between Systems - Elements
of management information related to OSI
Data Link Layer Standards
Technologies de I ’informa tion - T6kkommunica tions et khange
d ‘in forma tion en tre sys tbmes - L%men ts de I ’informa tion de ges tion lies
aux normes de Ia couche de liaison de donnees OSI
Reference number
ISO/1 EC 10742: 1994(E)
o ISOAEC
ISOAEC 10742 : 1994 (E)
Page
Contents
Foreword
iv
..........................................................................................................................................
Introduction
................................................................................................................................................
1 Scope
.......................................................................................................................
2 Normative references
..................................................................
2.1 Identical Recommendations I International Standards
.
2.2 Paired Recommendations I International Standards equivalent in technical content. .
.....................................................................................................................
2.3 Additional references
3 Definitions .
3.1 Basic reference model .
................................................................................................................
3.2 Management framework
...................................................................................................
3.3 Systems Management Overview
..................................................................
3.4 Common Management Information Service Definition
3.5 Information Model .
............................................................................................................................................
3.6 GDMO
....................................................................................................................................
4 Abbreviations
....................................................................
5 Elements of Data Link Layer Management Information
............................................................................................................
5.1 Managed Object Hierarchy
.................................................................................
5.2 Common Data Link Layer GDMO definitions
...................................................................................
5.3 The Data Link Subsystem managed Object
IO
............................................................................................
5.4 The Data Link Entity managed Object
...................................................................
5.5 The Data Link Service Access Point managed Object
..................................................................................
5.6 The LAPB Data Link Entity managed Object
.............................................................
5.7 The LAPB Single Link Protocol Machine managed Object
........................................................ 15
5.8 The LAPB Single Link Protocol Connection managed Object
.................................. 22
5.9 The LAPB Single Link Protocol Connection Initial Values managed Object
.................................................................................
5.10 The MAC Data Link Entity managed Object
...........................................................................................................
5.11 The MAC managed Object
..................................................................................
5.12 The LLC Data Link Entity managed Object
......................................................
5.13 The LLC Connectionless Protocol Machine managed Object
.................................................. 29
5.14 The LLC Connection-mode Protocol Machine managed Object
6 ASN.l module .
....................................................................................................................................
7 Conformance
.............................................................................. 33
7.1 Conformance requirements to ISO/IEC 10742
.................................................................................
7.2 Protocol specific conformance requirements
Annexes
A Allocation of Object Identifiers .
................................................................. 36
B IEEE 802.1 F Common Models and Generic Definitions
B.l Introduction .
B.2 Common Models .
...............................................................................................
8.2.1 Resource Type Managed Object
B.2.2 MACAddress Attribute .
....................................................................................
8.2.3 EWMA Metric Monitor Managed Object
.......................................................................................................................
B.3 Generic Definitions
B.3.1 Managed Objects .
..................................................................................................................................
B.3.2 Packages
................................................................. 43
B.3.3 Use of Quality Of Service (QOS) Alarm Notification
...........................................................................................................
B.4 Common Managed Objects
....................................................................................... 44
B.4.1 The ResourceTypeld managed Object
....................................................................................................
8.4.2 The Scanner managed Object
.46
B.4.3 The Exponentially Weighted Moving Average Metric Monitor managed Object. .
...............................................................................................................................
B.5 ASN.l Module
....................................................................................
C Shorthand Description of Managed Objects
...............................................................................
D Examples of the use of Relationship Attributes
....................................................................................................................................................
Index
0 ISO/IEC 1994
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any
fotm or by any means, electronie or mechanicai, inciuding photocopying and microfilm, without Permission in
writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1 211 Geneve 26 l SwitzerOand
Printed in Switzerland
ii
ISOAEC 10742 : 1994 (E)
o lSO/IEC
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized System for worldwide
standardization. National bodies that are members of ISO or IEC patticipate in the
development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with
ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the
joint technical committee are circulated to national bodies for voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
International Standard ISO/IEC 10742 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology.
.I part of this Inte rnational Standard. Annexes C
Annexes A and B form an integra
and D are for information only.
. . .
Ill
ISOAEC 10742 : 1994 (E) o ISOAEC
Introduction
This document is intended to become one of a set of International Standards
produced to facilitate the interconnection of open Systems. The set of International
Standards covers the Services, protocols and management information required to
achieve such interconnection.
This International Standard is positioned with respect to other related
Specifications by the layers defined in the ßeference Mode/ for Open System
Interconnection (ISO 7498). In particular, it is concerned with the definition of Data
Link Layer management information.
INTERNATIONAL STANDARD OISOAEC
ISO/IEC 10742 : 1994 (E)
Information technology -
Telecommunications and
information exchange between Systems -
Elements of management information related to OSI
Data Link Layer Standards
1 Scope
This International Standard provides the specification of management information within an Open System related
to those operations of the OSI Data Link Layer specified by the specifications in this document. Specifics on how
Data Link layer management is accomplished is beyond the scope of this International Standard. Data Link Layer
management is defined by specifying:
l the managed Object class definition of Data Link Layer Managed Objects following guidelines put forth by the
Structure of Management Information (ISO/IEC 10165)
the relationship of the Managed Objects and attributes to both the Operation of the layer and to other objects
and attributes of the layer, and
the action type operations on the attributes of Data Link Layer Managed Objects that are available to OSI
Systems Management.
2 Normative references
The following Recommendations and International Standards contain provisions which, through reference in this
text, constitute provisions of this Recommendation I International Standard. At the time of publication, the
editions indicated were valid. All Recommendations and Standards are subject to revision, and Parties to
agreements based on this Recommendation I International Standard are encouraged to investigate the possibility
of appjying the most recent editions of the Recommendations and Standards listed below. Members of IEC and
ISO maintain Registers of currently valid International Standards. The Telecommunication Standardization
Bureau of the ITU maintains a list of the currently valid ITU-T Recommendations.
2.1 ldentical Recommenciations I International Standards
- ITU-T Recommendation X.200( 1993) 1 ISO 7498-1: 1994, Information technology - Open Systems
Interconnection ßeference Model: Basic ßeference Model.
- CCITT Recommendation X.701(1992) I ISO/IEC 10040: 1992, Information technology - Open Systems
Interconnection - Systems management overview.
- CCITT Recommendation X.720( 1992) I lSO/IEC 10165-1: 1993, Information technology - Open Systems
Interconnection - Structure of management information: Management Information Mode/.
- CCITT Recommendation X.721(1992) I ISO/IEC 10165-2: 1992, Information technology - Open Systems
Interconnection - Structure of management information: Definition of Management Information.
- CCITT Recommendation X.722( 1992) I ISO/IEC 10165-4: 1992, Information technology - Open Systems
Interconnection - Structure of management information: Guidelines for the definition of managed objects.
ISOIIEC 10742 : 1994 (E) 0 ISOAEC
- ITlJ-T Recommendation X.723( 1993) l ISOAEC 1016551994, Information technology - Open Systems
Interconnection -Structure of Management Information: Generic management information.
- CCITT Recommendation X.730( 1992) I ISOAEC 10164-1: 1993, Information technology - Open Systems
Interconnection - Systems management: Object management function.
- CCITT Recommendation X.731(1992) I ISO/IEC 10164-2: 1993, Information technology - Open Systems
Interconnection - Systems management: State management function.
- CCITT Recommendation X.732( 1992) I ISOAEC 10164-3: 1993, Information technology - Open Systems
Interconnection - Systems management: Attributes for representing relationships.
- CCITT Recommendation X.733( 1992) I ISOAEC /IO1 64-4: 1992, Information technology - Open Systems
Interconnection - Systems management: Alarm reporting function.
- CCITT Recommendation X.734(1992) I ISO/IEC 10164-5: 1993, Information techno/ogy - Open Systems
Interconnection - Systems management: Event report management function.
- CCITT Recommendation X.735( 1992) I ISOAEC 10164-6: 1993, Information technology -Open Systems
lnterconnection - Systems management: Log control function.
2.2 Paired Recommendations I International Standards equivalent in technical content
- CCITT Recommendation X.700 (1992), Management Framework for Open Systems Interconnection (OSI) for
CCITT Applica tions.
ISO 7498 - 4: 1989, Information Processing Systems - Open Systems Interconnection - Basic ßeference Model
- Management framework.
- CCITT Recommendation X.212( 1988), Data link Service definition for open Systems interconnection for CCITT
applica tions.
ISOAEC 8886: 1992, Information technology - Telecommunications and informa tion exchange between Systems
- Data link Service definition for Open Systems Interconnection.
- CCITT Recommendation X.208( 1988), Specification of abstract Syntax notation one (ASN. 1).
ISOAEC 8824:1990, Information technology - Open Systems Interconnection - Specification of the Abstract
Syntax Notation One (ASN. 1).
- CCIlT Recommendation X.710 (1991), Common Management Information Service Definition for CCITT
Applica tions.
ISO/1 EC 9595: 1991, Information technology - Open Systems Interconnection - Common management
informa tion Service definition.
- CCITT Recommendation X.711 (1991), Common Management Information Protocol Specification for CCITT
Applica tions.
ISO/1 EC 9596- 1: 1991, Information technology - Open Systems Interconnection - Common management
information protocol - Patt 1: Specification.
2.3 Additional references
- ITU-T Recommendation X.25 (1993), Interface between data terminal equipment (DTE) and data circuit-
terminating equipment (DCE) for terminals operating in the packet mode and connected to public data networks
by dedica ted circuit.
lSO/lEC 10742 : 1994 (E)
0 ISO/IEC
ISO 7776: 1986, Information processing Systems - Data communications - High-level data link control
procedures - Description of the X.25 LA PB-compatible DTE data link procedures.
- ISO 8802-2: 1989, Information processing Systems - Local area networks - Logical link control.
- ISO/IEC 8802-3: 1993, Information technology - Local and metropolitan area networks - Carrier Sence multiple
access with collision detection (CSMAKD) access method and physical layer specifications.
- ISO/IEC 11575, Information Technology - Telecommunications and Information Exchange Between Systems -
Protocol Mappings for the OS1 Data Link Service.
3 Definitions
3.1 Basic reference model
This International Standard makes use of the following terms defined in ITU-T Ret X.200 1 ISO/IEC 7498-1
Data Link Layer
a)
open System
W
(N)-entity
C)
(N)-protocol
d)
(N)-Service access Point
3.2 Management framework
This International Standard makes use of the following terms defined in CCITT Ret X.700 1 ISO/IEC 7498-4
Managed Object
a)
3.3 Systems Management Overview
This International Standard makes use of the following terms defined in CCITT Ret X.701 1 ISO/IEC 10040.
Managed Object class
a)
Notification
b)
3.4 Common Management Information Service Definition
This International Standard makes use of the following terms defined in CCITT Ret X.710 1 ISO/IEC 9595.
Attribute
a)
3.5 Information Model
This International Standard makes use of the following terms defined in CCITT Ret X.720 1 ISO/IEC 10165-1.
Attribute Type
a)
[Behaviour
W
Containment
C)
ISO/IEC 10742 : 1994 (E) 0 ISO/IEC
Distinguished Name
d)
lnheritance
e)
Name Binding
fl
Package
9)
Parameter
hl
Relative Distinguished Name
.
Subclass
J)
Superclass
W
3.6 GDMO
This International Standard makes use of the following terms defined in CCITT Ret X.722 1 ISOAEC 10165-4
Managed Object Class Definition
a)
Template
b)
4 Abbreviations
Within the Managed Object definitions and GDMO templates the following abbreviations are used in the
standard-name element of a document-identifier when making references to other documents.
CCITT Rec. X.721 I ISO/IEC 10165-2
DMI
CCITT Rec. X.723 I ISO/IEC 10165-5
GMI
This International Standard makes use of the following Symbols and abbreviations.
CSMAKD Carrier sense multiple access with collision detection
DL Data Link
DLE Data Link Entity
Data Link Layer
DLL
Data Link Management
DLM
Data Link Service Access Point
DLSAP
DMI Definition of Management Information
EWMA Exponentially Weighted Moving Average
GDMO Guidelines for the Definition of Managed Objects
GMI Generic Management Information
IVMO Initial Value Managed Object
Logical Link Control
LLC
Media Access Control
MAC
MLP Multi Link Protocol
MO Managed Object
NSAP Network Service Access Point
PLE Packet Level Entity
Service Access Point
SAP
Single Link Protocol
SLP
0 ISO/IEC ISOAEC 10742 : 1994 (E)
5 Elements of Data Link Layer Management Information
5.1 Managed Object Hierarchy
5.1 .l Summary of managed objects
The following set of common managed objects are defined in this International Standard for the OS1 Data Link
Layer:
The Data Link Subsystem managed Object (datalinksubsystem) (see 5.3, page 9).
a)
The Data Link Entity managed Object (datalinkEntity) (see 5.4, page 10). (This managed Object is never
W
instantiated.)
The Data Link Service Access Point managed Object (dLSAP) (see 5.5, page 11).
The LAPB Data Link Entity managed Object (IAPBDLE) (see 5.6, page 12).
d)
The LAPB Single Link Protocol Machine managed Object (sLPPM) (see 5.7, page 14).
e)
The LAPB Single Link Protocol Connection managed Object (SLPConnection) (see 5.8, page 15).
f )
The LAPB Single Link Protocol Connection Initial Values managed Object (sLPConnectionlVM0) (see 5.9,
Cl)
page 22).
The Mac Data Link Entity managed Object (mACDLE) (see 5.10, page 23).
hl
The MAC managed Object /mAC) (see 5.11, page 24). (This managed Object is never instantiated.)
The LLC Data Link Entity managed Object (ILCDLE) (see 5.12, page 27).
j)
The LLC Connectionless Protocol Machine managed Object (ILCCLPM)(see 5.13, page 28). (This
k)
managed Object is never instantiated.)
The LLC Connection-mode Protocol Machine managed Object (ILCCOPM) (see 5.14, page 29). (This
1)
managed Object is never instantiated.)
The Resource Typeld managed Object (resourceTypeld) (see annex B)
m>
The Scanner managed Object (Scanner) (see annex B)(This managed Object is never instantiated.)
n>
The Exponentially Weighted Moving Average Metric Monitor managed Object (eWMAMetricMonitor) (see
0)
annex B)
These Managed Objects represent OSI Managements view of those elements of an Open System which support
the OSI Data Link Service subject to OSI management operations. Other MOs may be defined under Data Link
Subsystem using these generic specifications.
5.12 Containment hierarchy
The containment hierarchy is illustrated in figure 1. Managed objects which tan have multiple instances are
illustrated by shadowed (multiple) boxes. These objects are defined in detail in the following clauses of this
International Standard.
0 ISO/IEC
ISOAEC 10742 : 1994 (E)
datalinkSubsystem
I
ILCDLE 1
I
I I I
dLSAP
Figure 1 - Data Link Layer Containment Hierarchy
The datalink Subsystem MO is subordinate to the System MO. The LAPB DLE, MAC DLE and LLC DLE MOs
represent protocol- and media-specific communication entities.
The SLP PM MO represents the Operation of the protocol machine for the Single-link procedures specified in ISO
7776. The MAC, LLC CL PM and LLC CO PM MOs are generic managed objects from which MAC-specific and
LLC-specific protocol machine managed objects tan be derived, e.g. for CSMAKD MAC specified in ISO/IEC
8802-3, and for LLC Type 1 and LLC Type 2 protocol Operation specified in ISO 8802-2. The SLP Connection
MO represent the management view of connections established using the SLP.
51.3 Relationships
5.1.3.1 General
The use of relationship attributes is illustrated by examples in annex D. The following describes the individual
relationships in more detail.
5.1.3.2 DLE
There is a relationship between a ‘DLE’ MO (i.e. an LAPB, LLC and MAC DLE MO) and the MO representing the
underlying Service provider. This is represented by the attribute ProviderEntityNames inherited from the generic
datalinkEntity MO. This is a read-write attribute which allows a manager to configure which entities are to be
used to provide Services to this entity. For example, a LAPB DLE MO might be configured with the local
distinguished name of a Ph-Entity MO or an LLC DLE MO with the name of a MAC DLE MO (e.g. one containing
a CSMAKD MAC MO).
Additionally, a ‘DLE’ MO has a IocalSapNames attribute inherited from GMI:communicationsEntity. This is a read-
only attribute which contains the local distinguished name(s) of SAP MO(s), representing the Point at which
Services are provided to the entity. For example, in a LAPB DLE MO IocalSapNames might contain the name of a
Ph-SAP MO or, in an LLC DLE MO, the name of a dLSAP MO contained in a MAC DLE MO.
The SN-SetviceProvider attribute of the Network layer Linkage and X25PLE-DTE MOs contains the local
distinguished name of a ‘DLE’ MO.
0 ISO/IEC
ISOIIEC 10742 : 1994 (E)
5.1.3.3 dlSAP
There is a relationship between a dlSAP MO and the managed objects that represent the (Network layer) user
entities that are using the SAP. This is represented by the UserEntityNames attribute inherited from GMI:sapl.
For example, in an dlSAP MO contained in an LAPB DLE MO, UserEntityNames might contain the distinguished
name of an X25PLE-DTE MO.
The SN-SAP attribute of the Network layer Linkage and X25PLE-DTE MOs contains the distinguished name of a
dlSAP MO.
5.1.3.4 sLPConnection
There is a relationship between an sLPConnection MO and the MO representing the underlying Ph-Connection.
This represented by the attribute underlyingConnectionNames inherited from GMI:singlePeerConnection.
5.1.4 Minimum Event Filtering Capabilities
The Data Link Layer management definitions embodied in this International Standard imply the frequent, and
possibly excessive, generation of notifications during regular layer Operation. These notifications are especially
useful for effective fault management, where they facilitate the tracing and pinpointing of error situations. To
avoid the excessive dissemination of these event reports under normal operating conditions, it is advisable for a
managed System to have, as a minimum, the capability to perform discrimination based upon:
The Source managed Object class.
a)
The Object identifier values in the probable Cause and specif ic Problems field of communication a ,larms.
W
5.1.5 Use of Optional Fields
Where reference is made in this International Standard to ASN.l Syntax defined in DMI or GMI, only the following
fields shall be employed.
1) Those which are not OPTIONAL in the ASN.l Syntax.
2) Those which are OPTIONAL, but whose use is explicitly required by this International Standard.
3) Those which are OPTIONAL, but whose ASN.l type is SET OF ManagementExtension.
The use of any other fields is prohibited.
ISOAEC 10742 : 1994 (E)
0 ISO/IEC
5.2 Common Data Link Layer GDMO definitions
-- Behaviours
commonCreationDeletion-B BEHAVIOUR
DEFINED AS
Managed Object class imports the ISO/IEC 101652 objectcreation
and/or objectDeletion notifications. Used as follows:
objectcreation - Generated whenever an instance of the managed
Object class is created. Implernentations may optionally
include the sourcelndicator Parameter in the notification.
If creation occured as a result of internal Operation of
the resource, the value ‘resourceOperation’ is used. If
creation occured in response to a management Operation, the
value ‘managementoperation’ is used. A value of ‘unknown’
may be returned if it is not possible to determine the Source
of the Operation. None of the other optional Parameters are
used.
objectDeletion - Generated whenever an instance of the managed
Object class is deleted. Implernentations may optionally
include the sourcelndicator Parameter in the notification.
If deletion occured as a result of internal Operation of
the resource, the value ‘resourceOperation’ is used. If
deletion occured in response to a management Operation, the
value ‘managementOperation’ is used. A value of ‘unknown’
may be returned if it is not possible to determine the Source
of the Operation. None of the other optional Parameters are
used.;
commonStateChange-B BEHAVIOUR
DEFINED AS
Managed Object class imports the ISO/IEC 101652 statechange
notification. Used to report the changes to the operationalstate
attribute, and where present, the administrativestate attribute. A
Single Parameter set is included in the State Change definition field.
Only the (mandatory) attributeld and (optional) newAttributeValue
Parameters are used.;
-- Attribute Groups
timers ATTRIBUTE GROUP
-- Empty group definition. Timer attributes are added to the group in
-- package definitions.
DESCRIPTION The group of all timer attributes;
REGISTERED AS {DLM.agoi timers(1));
0 ISO/IEC ISOAEC 10742 : 1994 (E)
5.3 The Data Link Subsystem managed Object
-- There shall be exactly one of these managed objects within a System.
-- lt exists to provide a Container for all managed objects in a System
-- that relate to the Operation of the Datalink layer.
-0
-- The datalinksubsystem managed Object tan not be created or deleted
-0
explicitly by management Operation. lt exists inherently in a System;
-0
created and deleted as part of System Operation.
datalinksubsystem MANAGED OBJECT CLASS
DERIVED FROM “GMl ”:subsystem;
CHARACTERIZED BY datalinkSubsystem-P PACKAGE
ATTRIBUTES
“GMI ”:subsystemld
INITIAL VALUE DLM.datalinkSubsystemld-Value
GET;;;
REGISTERED AS {DLM.moi datalinkSubsystem(1));
-- Name Bindings
-- IMPORT “GMl ”:subsystem-System NAME BINDING
0 ISO/IEC
ISOAEC 10742 : 1994 (E)
5.4 The Data Link Entity managed Object
-- The generic DLE MO from which protocol- and media-specific DLE MOs
-0
may be derived.
datalinkEntity MANAGED OBJECT CLASS
DERIVED FROM “GMI ”:communicationsEntity;
CHARACTERIZED BY datalinkEntity-P PACKAGE
BEHAVIOUR
commonCreationDeletion-B,
commonStateChange-B;
ATTRIBUTES
ProviderEntityNames REPLACE-WITH-DEFAULT
GET-REPLACE;
ATTRIBUTE GROUPS
“DMI ”:state
“DMI ”:operationalState;
NOTIFICATIONS
“DMI ”:objectCreation,
“DMI ”:objectDeletion,
“DMI ”:stateChange;;;
REGISTERED AS {DLM.moi datalinkEntity(2));
-- Name Bindings
-- IMPORT “GMl ”:communicationsEntity-subsystem NAME BINDING
datalinkEntity-datalinkSubsystem-Management NAME BINDING
SUBORDINATE OBJECT CLASS datalinkEntity AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS datalinksubsystem AND SUBCLASSES;
WITH ATTRIBUTE “GMI ”:communicationsEntityld;
BEHAVIOUR datalinkEntity-datalinkSubsystem-Management-B BEHAVIOUR
DEFINED AS
The name binding which applies when a datalinkEntity managed Object (or
an instance of a subclass of the datalinkEntity MO class) tan be created by
management as a subordinate Object of the datalinksubsystem
managed Object (or subclass), and deleted by management.;;
CREATE;
DELETE ONLY-IF-NO-CONTAINED-OBJECTS;
REGISTERED AS {DLM.nboi datalinkEntity-datalinkSubsystem-Management(l)};
-- Attributes
ProviderEntityNames ATTRIBUTE
WITH ATTRIBUTE SYNTAX DLM.GroupObjects;
MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;
BEHAVIOUR providerEntityNames-B BEHAVIOUR
DEFINED AS
The distinguished names of provider entity managed objects.
The managed objects that represent the entities to be used to
provide Services to this entity.;;
REGISTERED AS {DLM.aoi providerEntityNames(1 l)};
0 ISO/IEC ISO/IEC 10742 : 1994 (E)
5.5 The Data Link Service Access Point managed Object
-- The dLSAP managed Object class is used to represent a Service access
-- Point at which Services are provided by a DLE to the user entity.
-- Instances of the dLSAP managed Object class are contained within
-0
instances of subclasses derived from the datalinkEntity managed Object
-0
class. Constraints on the number of contained dLSAP MOs and any
-0
specific semantics of the attributes are given as patt of the definition
-0
of the containing DLE managed Object class.
-- A dLSAP managed Object may be created and deleted explicitly by
-- management Operation or created and deleted automatically as part of
-0
System Operation, e.g. when a user of the Data Link layer Service
-- requests and is granted use of the Service. The mechanism by which
-- this happens is a local matter and not subject to OSI Standardisation.
dLSAP MANAGED OBJECT CLASS
DERIVED FROM “GMI ”:sapl;
REGISTERED AS {DLM.moi dLSAP(13));
-- Name Bindings
-- IMPORT “GMI ”:sapl-communicationsEntity NAME BINDING
dLSAP-datalinkEntity-Management NAME BINDING
SUBORDINATE OBJECT CLASS dLSAP AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS datalinkEntity AND SUBCLASSES;
WITH ATTRIBUTE “GMI ”:sapld;
BEHAVIOUR dLSAP-datalinkEntity-Management-B BEHAVIOUR
DEFINED AS
The name binding which applies when a dLSAP managed Object (or
an instance of a subclass of the dLSAP MO class) tan be created
by management as a subordinate Object of a datalinkEntity managed
Object (or subclass), and deleted by management.;;
CREATE;
DELETE ONLY-IF-NO-CONTAINED-OBJECTS;
REGISTERED AS {DLM.nboi dLSAP-datalinkEntity-Management(2));
ISO/IEC 10742 : 1994 (E)
0 ISO/IEC
5.6 The LAPB Data Link Entity managed Object
-- There may be multiple instances of the IAPBDLE managed Object in a
-0
System. Systems not supporting the LAPB Data Link procedures defined
-0
in IS 7776 are not required to support the IAPBDLE and contained
DD.
.managed objects.
-0
-- The IAPBDLE managed Object has a conditional mlp Package. There may
-- be multiple instances of IAPBDLE MO in a System, both with and without
-- the mlp Package. For those instances in which the package is absent,
-- the mlp procedures do not apply and the IAPBDLE MO may contain at
-0
most one sLPPM MO. For those instances in which the package is
-- present, the mlp procedures do apply and the IAPBDLE MO may contain
-- multiple instances of sLPPM MO.
-0
-- A IAPBDLE MO may contain at most one dLSAP MO. The value of the
-0
sapl Address attribute is of no significance. The cardinality of the
-0
UserEntityNames attribute is limited to one.
-0
-0
A IAPBDLE MO may be created and deleted explicitly by
-0
management Operation or created and deleted automatically as
-- patt of System Operation.
-0
-- When the IAPBDLE MO is operable, the operationalstate shall
-0
have the value ‘enabled ’; otherwise it shall have the value ‘disabled ’.
-- Transitions of operationalstate shall be reported using the
-0
statechange notification.
IAPBDLE MANAGED OBJECT CLASS
DERIVED FROM datalinkEntity;
CONDITIONAL PACKAGES
mLP-P PRESENT IF IAPBDLE supports mlp procedures,
mT2-P PRESENT IF IAPBDLE supports mlp procedures and mT2 timer.;
REGISTERED AS {DLM.moi IAPBDLE(3));
-- Packages
mLP-P PACKAGE
BEHAVIOUR mLP-P-B BEHAVIOUR
DEFINED AS
Additional properties of an IAPBDLE MO, present when mlp procedures supported.;;
ATTRIBUTES
mT1Timer REPLACE-WITH-DEFAULT
GET-REPLACE,
mT3Timer REPLACE-WITH-DEFAULT
GET-REPLACE;
ATTRIBUTE GROUPS
timers
mT1 Timer
mT3Timer;
REGISTERED AS {DLM.poi mLP-P(1));
mT2-P PACKAGE
BEHAVIOUR mT2-P-B BEHAVIOUR
DEFINED AS
Additional properties present when mT2 timer is supported.;;
ATTRIBUTES
mT2Timer REPLACE-WITH-DEFAULT
GET-REPLACE;
ATTRIBUTE GROUPS
timers
mT2Timer;
REGISTERED AS (DLM.poi mT2-P(5));
ISOAEC 10742 : 1994 (E)
0 ISO/IEC
-- Attributes
mT1Timer ATTRIBUTE
DERIVED FROM “GMI ”:timer;
BEHAVIOUR mTlTimer-B BEHAVIOUR
DEFINED AS
Value of the ISO 7776 Parameter MTI (lost frame timer).
Unit is seconds.;;
REGISTERED AS {DLM.aoi mTlTimer(l2));
mT2Timer ATTRIBUTE
DERIVED FROM “GMI ”:timer;
BEHAVIOUR mT2Timer-B BEHAVIOUR
DEFINED AS
Value of the ISO 7776 Parameter MT2 (group busy timer).
Unit is seconds.;;
REGISTERED AS {DLM.aoi mT2Timer(l3)};
mT3Timer ATTRIBUTE
DERIVED FROM “GMI ”:timer;
BEHAVIOUR mT3Timer-B BEHAVIOUR
DEFINED AS
Value of the ISO 7776 Parameter MT3 (mlp reset confirmation
timer). Unit is seconds.;;
REGISTERED AS (DLM.aoi mT3Timer(l4));
0 ISO/IEC
ISO/IEC 10742 : 1994 (E)
5.7 The LAPB Single Link Protocol Machine managed Object
-- The sLPPM managed Object represents the Operation of the LAPB Data
-0
Link layer protocol machine described in IS 7776 over a Single physical
-0
link. An sLPPM managed Object may contain at most one sLPConnection
-0
MO and one or more sLPConnectionlVM0.
-0
-- An sLPPM MO may be created and deleted explicitly by
-0
management Operation or created and deleted automatically as
-- part of System Operation.
-- When the sLPPM MO is operable, the operationalstate shall
-9
have the value ‘enabled ’; otherwise it shall have the value ‘disabled ’.
-- Transitions of operationalstate shall be reported using the
-0
statechange notification.
sLPPM MANAGED OBJECT CLASS
DERIVED FROM “GMI ”:coProtocolMachine;
CHARACTERIZED BY sLPPM-P PACKAGE
BEHAVIOUR
commonCreationDeletion-B,
commonStateChange-B;
ATTRIBUTE GROUPS
“DM I ”:state
“DMI ”:operationalState;
ACTIONS
“GMI ”:activate,
“GMI ”:deactivate;
NOTIFICATIONS
“DMI ”:objectCreation,
“DMI ”:objectDeletion,
“DMI ”:stateChange;;;
REGISTERED AS {DLM.moi sLPPM(4));
-- Name Bindings
-0
IMPORT “GMl ”:coProtocolMachine-entity NAME BINDING
sLPPM-IAPBDLE-Management NAME BINDING
SUBORDINATE OBJECT CLASS sLPPM AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS IAPBDLE AND SUBCLASSES;
WITH ATTRIBUTE “GMI ”:coProtocolMachineld;
BEHAVIOUR sLPPM-IAPBDLE-Management-B BEHAVIOUR
DEFINED AS
The name binding which applies when a sLPPM managed Object (or
an instance of a subclass of the sLPPM MO class) tan be created
by management as a subordinate Object of a IAPBDLE managed
Object (or subclass), and deleted by management.;;
CREATE;
DELETE ONLY-IF-NO-CONTAINED-OBJECTS;
REGISTERED AS (DLM.nboi sLPPM-IAPBDLE-Management(3));
0 ISO/IEC
ISO/IEC 10742 : 1994 (E)
5.8 The LAPB Single Link Protocol Connection managed Object
-- The sLPConnection managed Object represents the local view of a
-- connection between LAPB DLEs over a Single physical link.
-- An sLPConnection MO is created automatically as part of System
-- Operation.
-- An sLPConnection MO may be deleted automatically as patt of System
-0
Operation or may be deleted as a result of the deactivate or delete
-- management
-0
operations. An sLPConnectionlVM0 may be used as the Source of
-- initial values of attributes of an slpConnection MO.
sLPConnection MANAGED OBJECT CLASS
DERIVED FROM “GMI ”:singlePeerConnection;
CHARACTERIZED BY
commonSLPConnection-P,
sLPConnection-P;
CONDITIONAL PACKAGES
t3-P PRESENT IF Optional Timer T3 of ISO 7776 is supported.;
REGISTERED AS {DLM.moi sLPConnection(5));
-- Packages
commonSLPConnection-P PACKAGE
BEHAVIOUR
commonCreationDeletion-B;
ATTRIBUTES
interfaceType REPLACE-WITH-DEFAULT
DEFAULT VALUE DLM.interfaceTypeDefault -- dTE
GET-REPLACE,
k REPLACE-WITH-DEFAULT
GET-REPLACE,
nl REPLACE-WITH-DEFAULT
GET-REPLACE,
n2 REPLACE-WITH-DEFAULT
GET-REPLACE,
sequenceModulus REPLACE-WITH-DEFAULT
GET-REPLACE,
tlTimer REPLACE-WITH-DEFAULT
GET-REPLACE,
t2Timer REPLACE-WITH-DEFAULT
GET-REPLACE,
t4Timer REPLACE-WITH-DEFAULT
GET-REPLACE;
ATTRIBUTE GROUPS
timers
tlTimer
t2Timer
t4Timer;
NOTIFICATIONS
“DMI ”:objectCreation,
“DMI ”:objectDeletion;
.
-0
not registered
sLPConnection-P PACKAGE
BEHAVIOUR
commonDeactivateConnection-B,
commonStateChange-B,
fRMRReceivedCommunicationsAlarm-B;
ATTRIBUTES
fCSErrorsReceived GET,
fRMRsReceived GET,
ISOAEC 10742 : 1994 (E) 0 ISO/IEC
fRMRsSent GET,
iFrameDataOctetsReceived GET,
iFrameDataOctetsSent GET,
i FramesReceived G ET,
iframessent GET,
pollsReceived GET,
rEJsReceived GET,
rEJsSent GET,
rNRsReceived GET,
rNRsSent GET,
sABMsReceived GET,
sABMsSent GET,
sLPProtocolState GET,
timesT1 Expired GET;
ATTRIBUTE GROUPS
“GMI ”:counters
fCSErrorsReceived
fRMRsReceived
fRMRsSent
iFrameDataOctetsReceived
iFrameDataOctetsSent
iFramesReceived
iframessent
pollsReceived
rEJsReceived
rEJsSent
rNRsReceived
rNRsSent
sABMsReceived
sABMsSent
timesT1 Expired,
“DM I ”:state
sLPProtocolState;
ACTIONS
“GMI ”:deactivate;
NOTIFICATIONS
“DMI ”:communicationsAlarm
fRMR;
-- Note: The fRMR Parameter is carried
-0
as additionallnformation in the communicationsAlarm.
.
-0
not registered
l
t3-P PACKAGE
BEHAVIOUR t3-P-B BEHAVIOUR
DEFINED AS
Present if the optional Timer T3 is supported.;;
ATTRIBUTES
t3Timer REPLACE-WITH-DEFAULT
GET-REPLACE,
timesT3Expired
GET;
ATTRIBUTE GROUPS
“GMI ”:counters
timesT3Expired,
timers
t3Timer;
REGISTERED AS {DLM.poi t3-P(2));
-- Behaviours
commonDeactivateConnection-B BEHAVIOUR
DEFINED AS
Managed Object class imports the ISO/IEC 10165-5 deactivate
0 ISO/IEC
action. The deactivate action Causes the connection to be terminated.
The termination should occur as rapidly as practical, but no particular
time constraints are implied. Typically, this action simulates a disconnect
request received across the Service interface. If a more rapid means for
terminating the connection exists, then this should be used.
The termination shall occur in conformance to the protocol Standard.
The Managed Object remains in existente after completion of
the deactivate action. lt is subsequently deleted when the connection is
terminated, in the same way as if the connection had been terminated by
other means. A deactivate action may fail (with the ProcessingFailure
response) if it is temporarily not possible to terminate the connection.;
fRMRReceivedCommunicationsAlarm-B BEHAVIOUR
DEFINED AS
Managed Object imports the ISO/IEC 10165-2 communicationsAlarm
notification. Used to report the following conditions:
fRMRReceived - A FRMR frame is received. The received
FRMR frame is reported as additionallnformation in the
notification, using the fRMR Parameter. The significance
subparameter shall be set as described above.
The probablecause Parameter is set to the
value
communicationsProtocolError.
The value DLM.fRMRReceived shall be reported in the
specificProblems Parameter. In addition, the reason why the frame
was sent is also returned in specificProblems. Values are specified
in the DLM ASN.l module for
controlFieldUndefinedOrUnimplemented,
infoFieldLengthGreaterThanMaximum, invalidNR, formatError,
and nonspecific.
The perceivedseverity Parameter is set to the value Minor. A
subsequent communicationsAlarm with a perceivedseverity value of
Cleared is not generated. No other Parameters are used.;
sLPConnection-sLPPM-Automatic-B BEHAVIOUR
DEFINED AS
The name binding which applies when an sLPConnection managed
Object (or an instance of a subclass of the sLPConnection MO class)
is created automatically by the Operation of the System as a
subordinate Object of an sLPPM managed Object
(or subclass), and deleted automatically.
The creation of an instance of an sLPConnection MO (or subclass)
using this name binding may reference an instance of the
sLPConnectionlVM0 (or subclass). The means by which an instance
(if any) of the sLPConnectionlVM0 are identified are a local matter.
When this occurs, some of the initial values of the attributes of the
instance of the sLPConnection MO may be supplied by the values of
the attributes in the specified instance of sLPConnectionlVM0.
However any such value may be overridden by a value supplied by
local means (for example across an internal interface). Where values
are supplied by the IVMO, the initial value of an attribute of the
sLPConnection MO shall be the value of the corresponding attribute
in the sLPConnectionlVM0 (that is, which has the same attribute
template label). The naming attribute of the sLPConnection MO is
assigned a value according to local mechanisms.;
sLPConnection-sLPPM-Management-B BEHAVIOUR
DEFINED AS
The name binding which applies when an sLPConnection managed
0 ISO/IEC
ISOAEC 10742 : 1994 (E)
Object (or an instance of a subclass of the sLPConnection MO class)
which is a subordinate Object of an sLPPM managed Object (or
subclass), tan be deleted by management.;
-- Name Bindings
sLPConnection-sLPPM-Automatic NAME BINDING
SUBORDINATE OBJECT CLASS sLPConnection AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS sLPPM AND SUBCLASSES;
WITH ATTRIBUTE “GMI ”:connectionld;
BEHAVIOUR sLPConnection-sLPPM-Automatic-B;
REGISTERED AS (DLM.nboi sLPConnection-sLPPM-Automatic(4));
sLPConnection-sLPPM-Management NAME BINDING
SUBORDINATE OBJECT CLASS sLPConnection AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS sLPPM AND SUBCLASSES;
WITH ATTRIBUTE “GMI ”:connectionId;
BEHAVIOUR
sLPConnection-sLPPM-Automatic-B,
sLPConnection-sLPPM-Management-B;
DELETE ONLY-IF-NO-CONTAINED-OBJECTS;
REGISTERED AS {DLM.nboi sLPConnection-sLPPM-Management(S));
-- Attributes
fCSErrorsReceived ATTRIBUTE
DERIVED FROM “GMI ”:nonWrapping64BitCounter;
BEHAVIOUR fCSErrorsReceived-B BEHAVIOUR
DEFINED AS
Counter. Total number of frames received with a bad frame
check.;;
REGISTERED AS (DLM.aoi fCSErrorsReceived(l5));
fRMRsReceived ATTRIBUTE
DERIVED FROM “GMl ”:nonWrapping64BitCounter;
BEHAVIOUR fRMRsReceived-B BEHAVIOUR
DEFINED AS
Counter. Total number of FRMR frames received.;;
REGISTERED AS {DLM.aoi fRMRsReceived(1));
fRMRsSent ATTRIBUTE
DERIVED FROM “GMI ”:nonWrapping64BitCounter;
BEHAVIOUR fRMRsSent-B BEHAVIOUR
DEFINED AS
Counter. Total number of FRMR frames sent.;;
REGISTERED AS {DLM.aoi fRMRsSent(2));
iFrameDataOctetsReceived ATTRIBUTE
DERIVED FROM “GMI ”:nonWrapping64BitCounter;
BEHAVIOUR iFrameDataOctetsReceived-B BEHAVIOUR
DEFINED AS
Counter. Total number of data octets received in I frames.
Only data octets in new I
...
Frequently Asked Questions
ISO/IEC 10742:1994 is a standard published by the International Organization for Standardization (ISO). Its full title is "Information technology - Telecommunications and information exchange between systems - Elements of management information related to OSI Data Link Layer standards". This standard covers: Provides the specification of management information within an Open System related to those operations of the OSI Data Link Layer specified by the specifications in this document.
Provides the specification of management information within an Open System related to those operations of the OSI Data Link Layer specified by the specifications in this document.
ISO/IEC 10742:1994 is classified under the following ICS (International Classification for Standards) categories: 35.100.20 - Data link layer. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO/IEC 10742:1994 has the following relationships with other standards: It is inter standard links to ISO/IEC 10742:1994/Amd 2:1996, ISO/IEC 10742:1994/Amd 1:1995, ISO/IEC 10742:1994/Amd 3:1996; is excused to ISO/IEC 10742:1994/Amd 3:1996, ISO/IEC 10742:1994/Amd 2:1996, ISO/IEC 10742:1994/Amd 1:1995. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase ISO/IEC 10742:1994 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...