ISO/IEC 15802-2:1995
(Main)Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Common specifications — Part 2: LAN/MAN management
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Common specifications — Part 2: LAN/MAN management
Defines an Open System Interconnection (OSI) management-compatible architecture, and service and protocol elements for use in a LAN/MAN environment for the purpose of performing remote management of LAN-based or MAN-based devices.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Spécifications communes — Partie 2: Gestion de LAN/MAN
General Information
Standards Content (Sample)
INTERNATIONAL
ISOAEC
STANDARD
15802-2
ANSMEEE
Std 802.1 B
First edition
1995-03- IO
Information technology -
Telecommunications and information
exchange between Systems - Local and
metropolitan area networks - Common
specifications -
Part 2:
LAN/MAN management
Technologies de I’information - Ttikcommunications et khange
d ’information entre systemes - Rkseaux locaux et m&ropolitains -
Spkcifications communes -
Partie 2: Gestion de LAN/MAN
Reference number
lSQ/lEC 15802-2:%995(E)
NW/IEEE
Std 802.IB, 1995 edition
---------------------- Page: 1 ----------------------
Abstract: Services and protocol elements that permit the exchange of management information
between stations attached to ISOAEC Standard local and metropolitan area networks are defined.
The Standard includes the specification of managed objects that permit the Operation of the protocol
elements to be remotely managed. In addition, an architecture for Station discovery and the dynam-
ic control of event forwarding is defined. Services and protocols that support Station discovery and
the dynamic control of event forwarding are defined.
Keywords: event forwarding; local area networks, management; metropolitan area networks,
management
The Institute of Electrical and Electronics Engineers, Inc.
345 East 47th Street, New York, NY 10017-2394, USA
Copyright 0 1995 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 1995. Printed in the United States of America.
ISBN 1-55937-501-9
No part of this publication may be reproduced in any form, in an electronie re trie val System or o therwise, withou t the Prior
written permission of the publisher.
March IO, 1995 SH94259
---------------------- Page: 2 ----------------------
International Standard ISO/lEC 15802-2 : 1995
ANSUIEEE Std 802.1 B, 1995 edition
(Incorporating ANSVIEEE Stds 802.1 B-l 992 and 802.1 k-l 993)
Information technology-
Telecommunications and information
exchange between systems-
Local and metropolitan area networks-
Common specifications-
Part 2: LAN/MAN management
Sponsor
Technical Committee on Computer Communications
of the
IEEE Computer Society
Adopted as an International Standard by the
International Organization for Standardization
and by the
International Electrotechnical Commission
- American National Standard
Published by
The Institute of Electrical and Electronics Engineers, Inc.
---------------------- Page: 3 ----------------------
International Standard ISO/IEC 15802-2: 1995
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 participate 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.
In 1994, ANWIEEE Std 802.1B-1992 was adopted by ISOLEC JTC 1, as draft International Standard
ISO/IEC DIS 15802-2. A further revision was subsequently approved by ISO/IEC JTC 1 in the form of this
new edition, which is published as International Standard ISO/IEC 15802-2: 1995.
International Organization for StandardizationDnternational Electrotechnical Commission
Case postale 56 l CH-121 1 Geneve 20 l Switzerland
---------------------- Page: 4 ----------------------
Foreword to International Standard ISOAEC 15802-2 : 1995
This International Standard is part of a family of International Standards for Local and Metropolitan Area
Networks. The relationship between this International Standard and the other members of the family is
shown below. (The numbers in the figure refer to ISO Standard numbers.)
8802-2 Logical Link Control
10038 Media Access Control (MAC) Bridges
Data
Link
Layer
8802-5
8802-6 8802-7
8802-3 8802-4
Medium
Medium Medium Medium
Medium
Access
Access Access
Access Access
-------------
------------- ------------- ------------- -------------
8802-5
8802-6 8802-7
8802-3 8802-4 P hysical
Physical
P hysical P hysical P hysical Physical Layer
This family of International Standards deals with the Physical and Data Link layers as defined by the ISO
Open Systems Interconnection Basic Reference Model (ISO 7498 : 1984). The access Standards define five
types of medium access technologies and associated physical media, each appropriate for particular applica-
tions or System objectives. Other types are under investigation.
The International Standards defining the access technologies are as follows:
ISO/IEC 8802-3 [ANSUIEEE Std 802.3, 1993 Edition], a bus utilizing CSMA/CD as the access
4
method.
b) ISO/IEC 8802-4 [ANSUIEEE Std 802.4-19901, a bus utilizing token passing as the access method.
ISO/IEC 8802-5 [ANSUIEEE Std 802.5-19921, a ring utilizing token passing as the access method.
C>
d) ISO/IEC 8802-6 [ANSUIEEE Std 802.6, 1994 Edition], a dual bus utilizing distributed queuing as
the access method.
ISO 8802-7, a ring utilizing slotted ring as the access method.
e>
ISO/IEC TR 8802-1 provides an overview of the LAN/MAN Standards, along with details of their document
numbering.
ISO/IEC 8802-2 [ANWIEEE Std 802.2, 1994 Edition], Logical Link Control, is used in conjunction with
the medium access Standards to provide the data link layer Service to network layer protocols.
ISO/IEC 10038 [ANWIEEE Std 802. lD, 1993 Edition], Media Access Control (MAC) bridges, specifies an
architecture and protocol for the interconnection of IEEE 802 LANs below the level of the logical link con-
trol protocol.
ISO/IEC 15802-2 [ANSUIEEE Std 802.1B, 1995 Edition], LAN/MAN Management, defines an Open
Systems Interconnection (OSI) management-compatible architecture, and Services and protocol elements for
use in a LAN/MAN environment for performing remote management.
ISOAEC 15802-4 [ANSUIEEE Std 802.1E, 1994 Edition], System Load Protocol, specifies a set of Services
and protocol for those aspects of management concerned with the loading of Systems in ISO/IEC LAN/
MAN environments.
The main body of the International Standard serves for both the ISO/IEC 15802-2 : 1994 and IEEE Std
802. lB, 1995 Edition Standards. ISO and IEEE each have a unique foreword.
. . .
111
---------------------- Page: 5 ----------------------
ANSIIIEEE Std 802.1 B, 1995 Edition
IEEE Standards documents are developed within the Technical Committees of the
IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Board. Members of the committees serve voluntarily and without compensation.
They are not necessarily members of the Institute. The Standards developed within
IEEE represent a consensus of the broad expertise on the subject within the Institute
as well as those activities outside of IEEE that have expressed an interest in partici-
pating in the development of the Standard.
Use of an IEEE Standard is wholly voluntary. The existente of an IEEE Standard
does not imply that there are no other ways to produce, test, measure, purchase, mar-
ket, or provide other goods and Services related to the scope of the IEEE Standard.
Furthermore, the viewpoint expressed at the time a Standard is approved and issued is
subject to Change brought about through developments in the state of the art and
comments received from users of the Standard. Every IEEE Standard is subjected to
review at least every five years for revision or reaffirmation. When a document is
more than five years old and has not been reaffirmed, it is reasonable to conclude that
its contents, although still of some value, do not wholly reflect the present state of the
art. Users are cautioned to check to determine that they have the latest edition of any
IEEE Standard.
Comments for revision of IEEE Standards are welcome from any interested Party,
regardless of membership affiliation with IEEE. Suggestions for changes in docu-
ments should be in the form of a proposed Change of text, together with appropriate
supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of portions
of Standards as they relate to specific applications. When the need for interpretations
is brought to the attention of IEEE, the Institute will initiate action to prepare appro-
priate responses. Since IEEE Standards represent a consensus of all concerned inter-
ests, it is important to ensure that any interpretation has also received the concurrence
of a balance of interests. For this reason IEEE and the members of its technical com-
mittees are not able to provide an instant response to interpretation requests except in
those cases where the matter has previously received formal consideration.
Comments on Standards and requests for interpretations should be addressed to:
Secretary, IEEE Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855- 133 1
USA
1 IEEE Standards documents may involve the use of patented technology. Their 1
approval by the Institute of Electrical and Electronics Engineers does not mean that
using such technology for the purpose of conforming to such Standards is authorized
by the patent owner. It is the Obligation of the user of such technology to obtain all
necessary permissions.
---------------------- Page: 6 ----------------------
Foreword to ANWIEEE Std 802.1 B, 1995 Edition
(This foreword is not a part of ANSUIEEE Std 802. lB, 1995 Edition.)
This Standard is part of a family of Standards for local and metropolitan area networks. The relationship
between the Standard and other members of the family is shown below. (The numbers in the figure refer to
IEEE Standard numbers .)
802.2 LOGICAL LINK CONTROL
DATA
802.1 BRIDGING
LINK
LAYER
802.3 802.4 802.5 802.6 802.12
MEDIUM MEDIUM MEDIUM MEDIUM MEDIUM
ACCESS ACCESS ACCESS ACCESS ACCESS
802.3 802.4 802.5 802.6 802.12
PHYSICAL
PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL LAYER
* Formerly IEEE Std 802.1A.
This family of Standards deals with the Physical and Data Link layers as defined by the International Organi-
zation for Standardization (ISO) Open Systems Interconnection Basic Reference Model (ISO 7498 : 1984).
The access Standards define several types of medium access technologies and associated physical media,
each appropriate for particular applications or System objectives. Other types are under investigation.
The Standards defining the technologies noted above are as follows:
l IEEE Std 802l: Overview and Architecture. This Standard provides an over-
view to the family of IEEE 802 Standards. This document
forms part of the 802.1 scope of work.
l ANSUIEEE Std 802.1B LAN/MAN Management. Defines an Open Systems
[ISO/IEC 15802-21: Interconnection (OSI) management-compatible architecture,
and Services and protocol elements for use in a LAN/MAN
environment for performing remote management.
l ANWIEEE Std 802.1D MAC Bridging. Specifies an architecture and protocol for the
[ISO/IEC 100381: interconnection of IEEE 802 LANs below the MAC Service
boundary.
l ANWIEEE Std 802.1E System Load Protocol. Specifies a set of Services and protocol
[ISO/IEC 15802-41: for those aspects of management concerned with the loading of
Systems on IEEE 802 LANs.
‘The 802 Architecture and Overview Standard, originally known as IEEE Std 802.1 A, has been renumbered as IEEE Std 802. This has
been done to accommodate recognition of the base Standard in a family of Standards. References to IEEE Std 802.1A should be consid-
ered as references to IEEE Std 802.
---------------------- Page: 7 ----------------------
l ANSIAEEE Std 802.2 [ISO/IEC 8802-21: Logical Link Control
l ANSUIEEE Std 802.3 [ISO/IEC 8802-31: CSMA/CD Access Method and Physical Layer Specifications
l ANSUIEEE Std 802.4 [ISO/IEC 8802-41: Token Bus Access Method and Physical Layer Specifications
l ANSUIEEE Std 802.5 [ISO/IEC 8802-5 : Token Ring Access Method and Physical Layer Specifications
l ANSUIEEE Std 802.6 [ISO/IEC 8802-6 : Distributed Queue Dual Bus Access Method and Physical
Layer Specifications
l IEEE Std 802.9: Integrated Services (1s) LAN Interface at the Medium Access
Control (MAC) and Physical (PHY) Layers
l IEEE Std 802.10: Interoperable LAN/MAN Security, Currently approved.
Secure Data Exchange (SDE)
In addition to the family of Standards, the following is a recommended practice for a common Physical
Layer technology:
l IEEE Std 802.7: IEEE Recommended Practice for Broadband Local Area
Networks
The following additional working groups have authorized Standards projects under development:
l IEEE 802.11: Wireless LAN Medium Access Control (MAC) Sublayer and
Physical Layer Specifications
l IEEE 802.12: Demand Priority Access Method/Physical Layer Specifications
Conformance test methodology
An additional Standards series, identified by the number 1802, has been established to identify the
conformance test methodology documents for the 802 family of Standards. Thus the conformance test
documents for 802.3 are numbered 1802.3, the conformance test documents for 802.5 will be 1802.5, and so
on. Similarly, ISO will use 18802 to number conformance test Standards for 8802 Standards.
ANWIEEE Std 15802-2 : 1995 Edition
This document defines Services and protocol elements that permit the exchange of management information
between stations attached to IEEE 802 local and metropolitan area networks. The Standard includes the spec-
ification of managed objects that permit the Operation of the protocol elements to be remotely managed.
The reader of this Standard is urged to become familiar with the compl ete family of Standards.
---------------------- Page: 8 ----------------------
This Standard contains state-of-the-art material. The area covered by this Standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and
to incorporate new related material. Information on the current revision state of this and other IEEE 802
Standards may be obtained from
Secretary, IEEE Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855- 133 1
USA
IEEE 802 committee working documents are available from
IEEE Document Distribution Service
AlphaGraphics #35 Attn: P. Thrush
10201 N. 35th Avenue
Phoenix, AZ 8505 1
USA
vii
---------------------- Page: 9 ----------------------
Participants
The following is a list of participants in the Network Management effort of the IEEE Project 802 Working
Group at the time of 802.1B ’s approval. Voting members at the time of publication are marked with an aster-
isk (*). Those who were participants at the time of 802.1k ’s approval are marked with a dagger 0.
William P. Lidinsky, Chair*~
Tony Jeffree, Chair; Network Management Task Group *f
Fumio Akashi Kathy de Graaf Ronald Presti?
Paul D. Amer Rich Graham Ron L. G. Printe
Charles Arnold Michael A. Grave1 Maurice Qureshit
Naharaj Arunkumar Andrew Greent Nigel Ramsden
Floyd Backes*-/- Sharam Hakimi*t Rich Rehberg
Ann B allard Jeanne Haneyt Jim Reinstedler
Richard Bantel Mogens Hansen Trudy Reusser
Robert Barrett*t Harold Harrington Eduard Rocher
David Bartolini John Hart* t Paul Rosenblum* t
Sy Bederman Mike Harveyt Paul Ruocchio*f-
Amatzia Ben-Artzipf Bob Herbst Tom Rutt* t
Anthony Berentt Long Huangt John Salter
Orna Berry*t Jack R. Hung Alan Sarsby
Robert Bledsoe Thomas Hytry Susan Schanning
Kwame Boakye Jay Israel Mick Seaman*t
Laura Bridge*? Jan-Olof Jemnemo* t Gerry Segal*t
Brian Brown/- Albert Juandyt Rich Seifert*?
Juan Bulnes George Kajost Steve Senum*t
Fred Burg Ram Kedlaya Himanshu Shah*t
Peter Carbone Ha1 Keen*t Howard Sherry
Alan Chambers* t Alan Kirby Wu-Shi Shung
Ken Chapman Kimberly Kirkpatrick W. Earl Smith* “f
Alice Chen Steve Kleiman Mike Soha
Michael Chernick Yoav Kluger-t Dan Stokesberry
Jade Chien James Kristaft Lennart Swartz
Steve Cooper* “f Hans Lackner* “f Kenta Takumi
Jim Corrigan H. Eugene Latham Elysia Chiaw-Meng Tan
Paul Cowell*t Choon Lee? Robin Tasker* t
Mike Coy ’f Chao-yu Liang Angus Telfer
Andy Davis*t Bing Liao Dave Thompson
Peter Dawe George Lin* t Geoff Thompsont
S tan Degen Mike Lumpkin Nathan Tobol
Frank Deignan Andy Luque Wendel1 Turner
Desh Deshpande Phi1 Magnuson Peter Videcrantz* t
Ron Dhondy Joseph E. Masseryt Donald G. Vincent?
Mike Dickerson Bruce McClure Paul Wainright
Kurt Dobbins Tom McGowan Trevor Warwickt
Eiji Doi Margaret A. Merrick Scott Wasson
Barbara J. Don Carlos Jim Montrose Bob Watson
David Dyer-Bennet Jerry 0’ Keefe Richard Watson*
Walter Eldon Alan Oppenheimer* t Daniel Watts
Eldon D. Feist Richard Patti*t Alan Weissberger
Len Fishler*t Dave T. Perkinst Deborah Wilbert
Kevin Flanagan Roger Pfister Bert Williamst
Bill Futral* t Thomas L. Phinney Jerry A. Wyattt
Lionel Geretz*t Clive Philbrick Amnon Yacoby*t
Richard Gilbert* t John Pickens* Igor Zhovnirovsky
Harry Gold? David Piscitello
Carolyn Zimmer* t
Pat Gonia Daniel Pitt Nick Zucchero
Vencat Prasad* t
Additional participants in the development of 802. lk included the following
Sai Boeker Mike Dickerson
Brian J. Phillips
Bonnie B. Hromis
. . .
Vlll
---------------------- Page: 10 ----------------------
The following persons were on the balloting committee of 802.1B. Those who also balloted 802. lk are
marked with an asterisk.
W. B. Adams*
R. Juvonen D. Rosich*
D. Aelmore*
K. H. Kellermayr* V Rozentouler
H. Alkhatib
G. C. Kessler* D. J. Rypka
K. Athul* R. W. Klessig D. Sanford
J. D. Brock
J. Y. Lee* R. Sankar
P. Campbell* F. C. Lim
J. G. Sanz
B. J. Casey* R. S. Little* B. P. Schanning*
A. Castaldo
J. Loo C. Scheel
K. Chon* D. C. Loughry* N. Schneidewind
R. Ciciliani N. C. Lew* G. D. Schumacher
M. H. Coden* w. Lu* J. R. Schwab*
R. Crowder* G. Luderer A. S. Sethi*
L. F. M. De Moraes J. F. P Luhukay* D. A. Sheppard*
A. M. Dunn A. J. Luque* L. Sintonen
P. Eastman* K. G. McDonald H. P. Soloman*
L. G. Egan W. McDonald* C. M. Stillebroer*
J. E. Emrich* R. H. Miller* F. J. Strauss*
P. H. Enslow* D. S. Millman* E. Sykas*
C. Fan* C. B. M. Mishra* A. N. Tantawy
J. W. Fendrich* K. Mori* P. Thaler
H. C. Folts* G. Moseley G. 0. Thompson*
H. A. Freeman* A. C. Nigam B. A. Trent*
1. Fromm* E. S. Nolley* R. Tripi*
G. Fullerton* D. O ’Mahony* M. Uchida*
P. Fung C. Oestereicher* L. D. Umbaugh*
R. Gagliano* Y. Oh* C. M. Weaver, Jr.
W. W. Garman A. J. Pins* D. F. Weir*
1. Ghansah IJ. W. Pooch* A. J. Weissberger
P. Gonia* V. Punj* R. Wenig*
A. W. Hathaway A. Putnins* E. J. Whitaker*
P. L. Hutton T. L. D. Regulinski* P. A. Willis*
R. J. Iliff G. S. Robinson* J. A. Wyatt
A. A. Jeffree* P. T. Robinson* 0. Yuen*
J. R. Johnson W. Zhao
In addition to those indicated above, the following persons were on the balloting committee of 802.1 k:
R. M. Amy G. Lau E. J. Reilly
W. E. Ayen D. B. McIndoe R. Rosenthal
M. Diaz W. H. L. Moh F. ROSS
J. Gonzalez Sanz J. E. Montague C. Spurgeon
C. Guarnieri D. T. Perkins J. T. Vorhies
L. M. Lam J. Pickens A. D. Waren
I? K. Piele
ix
---------------------- Page: 11 ----------------------
When the IEEE Standards Board approved 802.1B on September 17, 1992, it had the following
membership:
Marco W. Migliaro, Chair Donald C. Loughry, Vice Chair
Andrew G. Salem, Secretary
Dennis Bodson Donald N. Heirman Don T. Michael*
Paul L. Borrill Ben C. Johnson L. John Rankine
Clyde R. Camp Walter J. Karplus Wallace S. Read
Donald C. Fleckenstein Ivor N. Knight Ronald H. Reimer
Jay Forster* Joseph L. Koepfinger* Gary S. Robinson
David F. Franklin Irving Kolodny Martin V Schneider
Ramiro Garcia D. N. “Jim” Logothetis Terrance R. Whittemore
Thomas L. Hannan Lawrence V. McCall Donald W. Zipse
*Member Emeritus
liaisons:
Also included are the following nonvoting IEEE Standards Board
Satish K. Aggarwal
James Beall
Richard B. Engelman
David E. Soffrin
Stanley 1. Warshaw
Kristin M. Dittmann
IEEE Standards Project Editor
When the IEEE Standards Board approved 802.lk on June 17, 1993, it had the following membership:
Wallace S. Read, Chair Donald C. Loughry, Vice Chair
Andrew G. Salem, Secretary
Gilles A. Baril Ben C. Johnson Don T. Michael*
Clyde R. Camp Walter J. Karplus Marco W. Migliaro
Donald C. Fleckenstein Lorraine C. Kevra L. John Rankine
Jay Forster* E. G. “Al” Kiener Arthur K. Reilly
David F. Franklin Ivor N. Knight Ronald H. Reimer
Ramiro Garcia Joseph L. Koepfinger* Gary S. Robinson
Donald N. Heirman D. N. “Jim” Logothetis Leonard L. Tripp
Jim Isaak Donald W. Zipse
*Member Emeritus
Also included are the following nonvoting IEEE Standards Board liaisons:
Satish K. Aggarwal
James Beall
Richard B. Engelman
David E. Soffrin
Stanley 1. Warshaw
Kristin M. Dittmann
IEEE Standards Project Editor
IEEE Std 802.1B-1992 was approved by the American National Standards Institute on February 23, 1993.
IEEE Std 802.1k-1993 was approved by the American National Standards Institute on January 4, 1994.
---------------------- Page: 12 ----------------------
Contents
PAGE
CLAUSE
1
1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
.......................................................
3.1 Definitions related to local and metropolitan area networks
4
.................................................................................................
3.2 Logical Link Control definitions
4
..............................................................................................
3.3 Basic Reference Model definitions
4
..........................................................................................
3.4 Management Framework definitions
4
...............................................................................
3 5 Systems Management Overview definitions
............................ 4
3.6 Structure of Management Information (SMI) Information Model definitions
................................................ 5
3.7 Common Management Information Service (CMIS) definitions
5
....................................................................
3.8 Abstract Syntax Notation One (ASN.l) definitions
.................................... 5
3.9 Guidelines for the Definition of Managed Objects (GDMO) definitions
5
..................................................................................................
3.10 Conformance testing definitions
5
...............................................................................
3.11 Terms defined in this International Standard
6
........................................................................................................
3.12 Acronyms and abbreviations
7
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. LANRMAN Management and Systems Management
8
5. Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
.......................................................................................................
5.1 Management communication
10
.............................................................
5.2 Management information and management operations
12
..................................................................................................
5.3 Relationship with CMISKMIP
13
.........................................................................
5.4 Relationship with other management protocols
13
6. Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
...............................................................................................
6.1 LAN/MAN Management Service
13
........................................................................
6.2 Convergence function and convergence Service
16
...............................
6.3 Relationship between LMMS Services and the managed Object boundary
18
7. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
.......................................................................................................................
7.1 LMMP definition
18
.................................................................................
7.2 Use of underlying Services by the LMMP
19
................................................................................................
7.3 Convergence protocol definition
30
......................................................................................
7.4 Use of underlying Services by the CPE
32
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8. LAN/MAN Management managed Object defmitions
32
8.1 Overview of managed Object structure .
33
.......................................................
8.2 LAN/MAN Management managed Object class definition
34
...................................................................................
8.3 Specific CPE Info managed Object class
34
8.4 Resource Type ID managed Object class .
35
8.5 Access class table entry managed Object class definition .
................................................... 37
8.6 Notification type table entry managed Object class definition
xi
---------------------- Page: 13 ----------------------
CLAUSE PAGE
8.7 Event report destination table entry managed Object class definition . 38
8.8 Data definitions for the LMM managed objects . 39
Event forwarding and access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.
9.1 Event forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.2 Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Conformance
..................................................................................................................... 44
10.1 Static conformance
...................................................................... 45
10.2 Protocol implementation conformance Statement
............................................................................................................... 45
10.3 Dynamit conformance
11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Discovery and dynamic control of event forwarding
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.1 Scope
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.