|
lSO/IEC
STANDARDIZED
ISP
PROFILE
11183-Z
First edition
1992-12-15
Information technology - International
Standardized Profiles AOMI n QSI
Management - Management
Communications -
Part 2:
CM&E/ROSE for AOMIZ - Enhanced
Management Communications
Technoiogies de / ‘information - Profils normalis& interna tionaux AOM I n
pour la gestion OS/ - Gestion de communication -
Partie 2: CM/SE/ROSE pour AOM72 - Gestion avancge de
communication
fieierence number
lSO/fEC ISP II 183--2:1992(E)
---------------------- Page: 1 ----------------------
ISQ/IEC ISP 11183-2: 1992 (E)
Page
Contents
................................................................................................ Vii
Introduction .
. . . . . . .L.s.*.m*.m. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1 Scope .* . . . . . . . . . . . . . . . . . . . . . .
................................. 1
1 .I General .
.......................... ........ ......................................................... 2
I .2 CMIP/ROSE PDUs support
....................................................... .............................................. 2
1.3 ChAlP functional units
........................................................................................ 2
1 .4 Position within the taxonomy
-3
1.5 Scenario .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .~.~.I.~. 3
2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <.
5
3 Definitions anef conventions . . . . . I.,. ”.,.,.
3.1 Base standard . -5
3.1 .I Definitions. . . . 5
3.1 .2 PICS definitions and conventions. . 5
3.2 Profile. . . 6
3.2. I Profile support requirement definitions . 6
3.2.2 ISPICS requirements list conventions . 6
3.2.3 Nesting rules in BSPICS requirements list . 7
3.3 CornmoE conditions list conventions . . . “. 8
. . . . . . . . . . . . . .I.
4 Abbreviations . . . . . . . . . . . . . Q -. “. . .s. “.-.~. ”.-. 9
5 Conformance to AOMl2 . . . . . . . . . . . . . . .,.s ”.,. 10
5.1 Conformance statement . 10
5.2 C3.A P conformance. . . IO
5.3 Association establishment and abort requirements . 1 1
5.4 ROSE conformance . . .
11
o ISO/IEC 1992
All rights ressrved. No pat? of this publication may be reproduced or utilized in any form or
by any means, electronic or mechanical, including photocopying and microfilm, without per-
mission in writing from the publisher.
lSO/IEC Copyright Office 8 Case Postale 56 * O-l-121 1 Genkve 20 * Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
Annex
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
A ISPICS Requirements List
.................................................. ....................... 13
A.1 Global statement of conformance
............................................................................................................... 13
A.2 Capabilities
Initiator/Responder capability . 13
A.2.1
14
ASN.1 EXTERNAL type parameters support .
A.2.2
14
...............................................................
A.2.3 CMIPUserlnfo parameter support
.............................................................. 16
A.2.4 CMIPAbortlnfo parameter support
......................................................................................... 16
A.25 Major capabilities
17
................................................................................................
A.3 Protocol parameters
17
System wide parameters .
A.3.1
21
........................................ ............................
A.3.2 Common protocol parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . .~. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
A.4 Protocol data units
...................................................... ................................................. 37
A.5 PDU parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
* A.6 Negotiation capabilities
........................... ............................................................ 99
A.7 Multi-layer dependencies
100
A.8 List of CMISE Service Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.9 List of ASN.l elements specified with “ANY DEFINED BY” type . . . . . . . . . .-. 101
.......................................................................................... 13
Table A.1 - Association initialisation
.................................................................................................. 13
Table A.2 - Association release
................................................. 14
Table A.3 - CMIPUserlnfo parameter support (in AARQapdu)
................................................. 15
Table A.4 - CMIPUserlnfo parameter support (in AAREapdu)
16
Table A.5 - CMIPAbortlnfo parameter support .
................................................................................................. 16
Table A.6 - Conformance claim
........................................................................... 16
Table A.7 - Additional functional unit support
....................................................................................... 17
Table A.8 - Scope parameter support
............................................................... 18
Table A.9 - Filterltem parameter support - (sending)
............................................................ 19
Table A.1 0 - Filterltem parameter support - (receiving)
20
Table A.1 1 - CMISFilter parameter support .
.......................................................................... 20
Table A.1 2 - CMISFilter complexity limitations
........................................................... 21
Table A.13a - Common parameter support - (sending)
......................................................... 22
Table A.13b - Common parameter support - (receiving)
........................................................... 23
Table A.14 - Protocol support for kernel CMIS services
Table A.15 - CMIP PDUs required to support M-ACTION service in the invoker role.2 4
Table A.16 - CMIP PDUs required to support M-ACTION service in the performer roie.2 5
.... 26
Table A.17 - CMIP PDUs required to support M-CANCEL-GET service in the invoker role
Table A.18 - CMIP PDUs required to support M-CANCEL-GET service in the performer role26
Table A.19 - CMIP PDUs required to support M-CREATE service in the invoker role. . .2 7
..... .28
Table A.20 - CMIP PDUs required to support M-CREATE service in the performer role.
Table A.21 - CMIP PDUs required to support M-DELETE service in the invoker role.2 9
......... 30
Table A.22 - CMIP PDUs required to support M-DELETE service in the performer role
............ 31
Table A.23 - CMIP PDUs required to support M-EVENT-REPORT in the invoker role
........ 32
Table A.24 - CMIP PDUs required to support M-EVENT-REPORT in the performer role
Table A.25 - CMIP PDUs required to support M-GET service in the invoker role. . .33
. . .
III
---------------------- Page: 3 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
............ .34
Table A.26 - CMIP PDUs required to support M-GET service in the performer role.
................. .35
Table A.27 - CMIP PDUs required to support M-SET service in the invoker role.
............. .36
Table A.28 - CMIP PDUs required to support M-SET service in the performer role.
37
Table A.29 - ROIV-m-Action (sending) .
38
Table A.30 - ROIV-m-Action (receiving) .
.................................................................... 39
Table A.31 - ROIV-m-Action-Confirmed (sending)
.................................................................. 40
Table A.32 - ROIV-m-Action-Confirmed (receiving)
.........
..................................................................... 40
Table A.33 - ROIV-m-Cancel-Get (sending)
..4 1
Table A.34 - ROIV-m-Cancel-Get (receiving) .
41
......................................................................................
Table A.35 - ROIV-m-Create (sending)
.................................................................................... 42
Table A.36 - ROIV-m-Create (receiving)
...................................................................................... 43
Table A.37 - ROIV-m-Delete (sending)
44
....................................................................................
Table A.38 - ROIV-m-Delete (receiving)
45
............................................................................
Table A.39 - ROIV-m-EventReport (sending)
45
..........................................................................
Table A.40 - ROIV-m-EventReport (receiving)
46
..........................................................
Table A.41 - ROIV-m-EventReport-Confirmed (sending)
46
........................................................
Table A.42 - ROIV-m-EventReport-Confirmed (receiving)
47
...........................................................................................
Table A.43 - ROIV-m-Get (sending)
......................................................................... ................ 48
Table A.44 - ROIV-m-Get (receiving)
................................................................. 49
Table A.45 - ROIV-m-LinkedReply-Action (sending)
..5 1
.............................................................
Table A.46 - ROIV-m-LinkedReply-Action (receiving)
..5 3
...............................................................
Table A.47 - ROIV-m-LinkedReply-Delete (sending)
............................................................... 54
Table A.48 - ROIV-m-LinkedReply-Delete (receiving)
..................................................................... 55
Table A.49 - RON-m-LinkedReply-Get (sending)
................................................................... 57
Table A.50 - ROIV-m-LinkedReply-Get (receiving)
..................................................... ................. 59
Table A.51 - ROIV-m-LinkedReply-Set (sending)
.................................... ................................ 61
Table A.52 - ROIV-m-LinkedReply-Set (receiving)
.63
(sending) .
Table A.53 - ROIV-m-Set
.................
........................................................................ 64
Table A.54 - RON-m-Set (receiving)
............................................... .......................... 65
Table A.55 - ROW-m-Set-Confirmed (sending)
.............................................. ......................... 66
Table A.56 - RON-m-Set-Confirmed (receiving)
..6 7
................................................................
Table A.57 - RORS-m-Action-Confirmed (sending)
................................................................ 68
Table A.58 - RORS-m-Action-Confirmed (receiving)
68
Table A.59 - RORS-m-Cancel-Get (sending) .
......................................................... .................. 68
Table A.60 - RORS-m-Cancel-Get (receiving)
............................................................... ..................... 69
Table A.61 - RORS-m-Create (sending)
.................................................................................. 69
Table A.62 - RORS-m-Create (receiving)
70
Table A.63 - RORS-m-Delete (sending) .
.................. 70
Table A.64 - RORS-m-Delete (receiving) .
........................................................ 71
Table A.65 - RORS-m-EventReport-Confirmed (sending)
...................................................... 71
Table A.66 - RORS-m-EventReport-Confirmed (receiving)
72
.........................................................................................
Table A.67 - RORS-m-Get (sending)
73
.......................................................................................
Table A.68 - RORS-m-Get (receiving)
74
.......................................................................
Table A.69 - RORS-m-Set-Confirmed (sending)
75
.....................................................................
Table A.70 - RORS-m-Set-Confirmed (receiving)
............................................................................ 76
Table A.71 - ROER-accessDenied (sending)
.......................................................................... 76
Table A.72 - ROER-accessDenied (receiving)
................................................... ............. 76
Table A.73 - ROER-classlnstanceConflict (sending)
............................................................... 77
Table A.74 - ROER-classlnstanceConflict (receiving)
................................................................. 77
Table A.75 - ROER-complexityLimitation (sending)
78
Table A.76 - ROER-complexityLimitation (receiving) .
............................................ 78
Table A.77 - ROER-duplicateManagedObjectlnstance (sending)
.......................................... 79
Table A.78 - ROER-duplicateManagedObjectlnstance (receiving)
.................. 79
Table A.79 - ROER-getListError (sending) .
80
Table A.80 - ROER-getListError (receiving) .
..8 1
..............................................................
Table A.81 - ROER-invalidArgumentValue (sending)
82
Table A.82 - ROER-invalidArgumentValue (receiving) .
82
Table A.83 - ROER-invalidAttributeValue (sending) .
iv
---------------------- Page: 4 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
Table A.84 - ROER-invalidAttributeValue (receiving) . . . . 83
Table A.85 - ROER-invalidFilter (sending) . 83
Table A.86 - ROER-invalidFilter (receiving) . 83
Table A.87 - ROER-invalidObjectlnstance (sending) . 84
Table A.88 - ROER-invalidObjectlnstance (receiving) . 84
Table A.89 - ROER-invalidscope (sending) . 84
Table A.90 - ROER-invalidscope (receiving) . 85
Table A.91 - ROER-missingAttributeValue (sending) . 85
Table A.92 - ROER-missingAttributeValue (receiving) . 85
Table A.93 - ROER-mistypedoperation (sending) . 86
86
Table A.94 - ROER-mistypedoperation (receiving) .
86
Table A.95 - ROER-noSuchAction (sending) .
87
Table A.96 - ROER-noSuchAction (receiving) .
.................................................................. 87
Table A.97 - ROER-noSuchArgument (sending) . . .
.................................................................. 88
Table A.98 - ROER-noSuchArgument (receiving) . .
.................................................................. 88
Table A.99 - ROER-noSuchAttribute (sending).
Table A. 100 - ROER-noSuchAttribute (receiving) . . . 89
.
Table A. 101 - ROER-noSuchEventType (sending) . 89
Table A. 102 - ROER-noSuchEventType (receiving . 89
)
....................
Table A.1 03 - ROER-noSuchlnvokeld (sending) . 90
Table A. 104 - ROER-noSuchInvokeld (receiving) . . 90
Table A. I05 - ROER-noSuchObjectClass (sending) . 90
Table A. 106 - ROER-noSuchObjectClass (receiving) . 91
Table A.1 07 - ROER-noSuchObjectlnstance (sending) . 91
Table A. 108 - ROER-noSuchObjectlnstance (receiving) . 91
Table A. 109 - ROER-noSuchReferenceObject (sending) . 92
Table A. 1 IO - ROER-noSuchReferenceObject (receiving) . 92
................................................................. 92
Table A. 111 - ROER-operationCancelled (sending)
Table A. 112 - ROER-operationCancelled (receiving) . 93
Table A. 113 - ROER-processingFailure (sending) . 93
Table A. 114 - ROER-processingFailure (receiving) . 94
Table A.1 15 - ROER-setListError (sending) . 95
Table A.1 16 - ROER-setListError (receiving) . 96
Table A.1 17 - ROER-syncNotSupported (sending) . 97
Table A. 118 - ROER-syncNotSupported (receiving) . 97
Table A. 119 - RORJ (sending) . 98
Table A. 120 - RORJ (receiving) . 98
Table A.1 21 - Negotiation capabilities . 99
Table A.1 22 - Rose association and operation class support . 99
................................................................... 99
Table A.123 - Presentation functional unit support
.......................................................................... 99
Table A.1 24 - Session functional unit support
........................................................................................ 100
Table A.125 - CMISE Service Errors
---------------------- Page: 5 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for
worldwide standardization. National bodies that are members of IS0 or
IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with. particular fields of technical activity. IS0 and IEC technical com-
mittees collaborate in fields of mutual interest. Other international organ-
izations, governmental and non-governmental, in liaison with IS0 and IEC,
also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, lSO/IEC JTC 1. In addition to developing International
Standards, lSO/IEC JTC 1 has created a Special Group on Functional
Standardization for the elaboration of International Standardized Profiles.
An International Standardized Profile is an internationally agreed,
harmonized document which identifies a standard or group of standards,
together with options and parameters, necessary to accomplish a function
or set of functions.
Draft International Standardized Profiles are circulated to national bodies
for voting. Publication as an International Standardized Profile requires ap-
proval by at least 75 % of the national bodies casting a vote.
International Standardized Profile lSO/IEC ISP 11183-2 was prepared with
the collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- OSI Implementors Workshop (OIW).
lSO/IEC ISP 11183 consists of the following parts under the general title
Information technology - International Standardized Profiles AOM 1 n OSI
Management - Management Communications:
- Part 1: Specification of ACSE, presentation and session protocols
for the use by ROSE and CMISE
- Part 2: CM/SE/ROSE for AOMIZ - Enhanced Management Com-
munica tions
- Part 3: CM/SE/ROSE for AOMl I - Basic Management Com-
munications
Annex A forms an integral part of this part of ISO/IEC ISP 11183.
---------------------- Page: 6 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
Introduction
This International Standardized Profile (ISP) is defined within the context of functional standardization, in
accordance with the principles specified by lSO/lEC TR 10000, “Framework and Taxonomy of International
Standardized Profiles ”. The context of Functional Standardization is one part of the overall field of Information
Technology (IT) standardization activities, covering base standards, profiles, and registration mechanisms. A
Profile defines a combination of base standards that collectively perform a specific well-defined function. Profiles
standardize the use of options and other variations in the base standards, and provide a basis for the
development of uniform, internationally recognized conformance test suites.
One of the most important roles for an ISP is to serve as the basis for the development (by organizations other
than IS0 and IEC) of internationally recognized tests and test centres. ISPs are produced not simply to
‘legitimize’ a particular choice of base standards and options, but to promote real system interoperability. The
development and widespread acceptance of tests based on this and other ISPs is crucial to the successful
realization of this goal.
The text for this part of lSO/IEC ISP 11183 was developed in close cooperation among the Network
Management Expert Groups of the three International OSI Workshops: NIST Workshop for implementors of OSI
(NIST OIW), the European Workshop for Open Systems (EWOS) and the OSI Asia-Oceania Workshop (AOW).
This ISP part is harmonized among these three Workshops and it was finally ratified by the Workshops’ plenary
assemblies.
This part of ISO/IEC ISP 11183 contains one normative annex : annex A, ISPICS Requirements List for AOM12.
The expression “International Standardized Profile” is replaced by the abbreviation “ISP” in the following clauses
and in the annex.
vii
---------------------- Page: 7 ----------------------
ISO/lEC ISP 11183-2: 1992 (E)
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARDIZED PROFILE ISO/IEC ISP 11183-2:1992(E)
Information technology - International Standardized
Profiles AOMI n OSI Management - Management
Communications -
Part 2:
CM&E/ROSE for AOMI 2 - Enhanced Management
Communications
1 Scope
1 .l General
This part of ISO/IEC ISP 11183 specifies how the OSI Common Management Information Service Element
(CMISE) combined with the OSI Remote Operation Service Element (ROSE) shall be used to provide the
complete set of operation and notification services to the CMISE-service-users of two end systems. It specifies
the CMIP/ROSE protocol features for the definition of the Enhanced Management Communications profile,
AOM12. This part of ISO/IEC ISP 11183 can be used together with the part 1 and any connection-mode
Transport profile to specify the complete communication requirements for systems management.
This part of ISO/IEC ISP 11183 defines the support level of all the OSI management communication features
needed by implementations. It specifies general purpose management communication capabilities by requiring
the support of all the CMIP functional units except the extended services functional unit. Other profiles may be
defined that provide a subset of capabilities specified here.
The support of the complete set of operation and notification services, and of the corresponding protocol
elements does not imply that all these features shall be used in all instances of communications. The selection of
the features depends on the needs and dynamic requirements of the CMISE-service-users who may choose
between :
application entity roles,
functional units,
operation/notification services,
optional parameters.
It only implies that a conforming implementation of the CMISE/ROSE services provider does not restrict the
capabilities of the CMISE-service-users and complies with the static CMIP requirements specified in ISO/IEC
9596-l and ISO/IEC 9596-2.
NOTES
1 The operations and notifications relate to managed objects. The specification and the support of these managed objects are outside
the scope of the profile AOM12.
2 This part of ISO/IEC ISP 11183 is based on ISO/IEC 9596-2: (SC21 N-7036: 2 June 1992).
---------------------- Page: 9 ----------------------
ISO/IEC ISP 11183-2: 1992 (E)
1.2 CMIP/ROSE PDUs support
An implementation conforming to the profile AOM12 shall be able to support the following PDUs:
ROIV-m-Action ROER-accessDenied
ROIV-m-Action-Confirmed ROER-classlnstanceConflict
ROIV-m-Create ROER-complexityLimitation
ROIV-m-Delete ROER-duplicateManagedObjectlnstance
ROIV-m-Get ROER-getListError
ROIV-m-Set ROER-invalidArgumentValue
ROIV-m-Set-Confirmed ROER-invalidAttributeValue
ROIV-m-Cancel-Get ROER-invalidFilter
ROIV-m-Event Report ROER-invalidObjectlnstance
ROIV-m-Event Report-Confirmed ROER-invalidscope
ROER-missingAttributeValue
ROIV-m-Linked-Reply-Action ROER-mistypedoperation
ROIV-m-Linked-Reply-Delete ROER-noSuchAction
ROIV-m-Linked-Reply-Get ROER-noSuchArgument
ROIV-m-Linked-Reply-Set ROER-noSuchAttribute
ROER-noSuchEventType
RORS-m-Action-Confirmed ROER-noSuchInvokeId
RORS-m-Create ROER-noSuchObjectClass
RORS-m-Delete ROER-noSuchObjectlnstance
RORS-m-Get ROER-noSuchReferenceObject
RORS-m-Set-Confirmed ROER-operationCancelled
RORS-m-Cancel-Get ROER-processingFailure
RORS-m-Event Report-Confirmed ROER-setListError
ROER-syncNotSupported
RORJ
1.3 CMIP functional units
The CMIP functional units are defined in ISO/IEC 9595 and ISO/IEC 9596-l. A conforming implementation shall
be able to support all of the CMIP functional units except the extended service functional unit as indicated by the
table A.7 in annex A of this part of lSO/IEC ISP 11183. However, on an individual association, if requested or
acc
...