Title pageIntroductionParticipantsCONTENTS1. Overview2. Scope3. References4. Definitions5. Concepts of management information & managed objects6. Common models7. Generic definitionsAnnex A - Common managed objectsAnnex B - Allocation of managed object identifier values for IEEE Std 802.1F-1993Annex C - Registration of information objects within IEEE 802 standardsAnnex X - Allocation of object identifier valuesAnnex D - Guidelines for developers of LAN/MAN standardsThe Institute of Electrical and Electronics Engineers, Inc.345 East 47th Street, New York, NY 10017-2394, USACopyright © 1993 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 1993. Printed in the United States of AmericaISBN 1-55937-340-7 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Std 802.1F-1993 IEEE Standards for Local and Metropolitan Area Networks:Common Definitions and Procedures for IEEE 802 Management Information Sponsor Technical Committee on Computer Communicationsof theIEEE Computer Society Approved November 9, 1993 IEEE Standards Board Abstract: Management information and procedures applicable across the entire family of IEEE 802LAN/MAN standards within the architectural framework for LAN/MAN Management specified inIEEE Std 802-1990 are identified. Common management information, such as attributes to repre-sent MAC address and managed objects to represent configurable gauges, are specified. The needof developers of LAN/MAN management specifications for common procedures to develop, de-scribe, and register management information is addressed. Keywords: local area networks, management; metropolitan area networks, managementIEEE Standards documents are developed within the Technical Committees ofthe IEEE Societies and the Standards Coordinating Committees of the IEEE Stan-dards Board. Members of the committees serve voluntarily and without compensa-tion. They are not necessarily members of the Institute. The standards developedwithin IEEE represent a consensus of the broad expertise on the subject within theInstitute as well as those activities outside of IEEE that have expressed an interest inparticipating in the development of the standard.Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standarddoes 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 issubject to change brought about through developments in the state of the art and com-ments received from users of the standard. Every IEEE Standard is subjected toreview at least every five years for revision or reaffirmation. When a document ismore than five years old and has not been reaffirmed, it is reasonable to conclude thatits contents, although still of some value, do not wholly reflect the present state of theart. Users are cautioned to check to determine that they have the latest edition of anyIEEE 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 appropriatesupporting comments.Interpretations: Occasionally questions may arise regarding the meaning of por-tions of standards as they relate to specific applications. When the need for interpreta-tions is brought to the attention of IEEE, the Institute will initiate action to prepareappropriate responses. Since IEEE Standards represent a consensus of all concernedinterests, it is important to ensure that any interpretation has also received the concur-rence of a balance of interests. For this reason IEEE and the members of its technicalcommittees are not able to provide an instant response to interpretation requestsexcept 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 Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USAIEEE Standards documents are adopted by the Institute of Electrical and Electron-ics Engineers without regard to whether their adoption may involve patents on arti-cles, materials, or processes. Such adoption does not assume any liability to anypatent owner, nor does it assume any obligation whatever to parties adopting thestandards documents.iii Introduction (This introduction is not a part of IEEE Std 802.1F-1993, IEEE Standards for Local and Metropolitan Area Networks:Common Definitions and Procedures for IEEE 802 Management Information.) This standard is part of a family of standards for local and metropolitan area networks. The relationshipbetween the standard and other members of the family is shown below. (The numbers in the figure refer toIEEE standard numbers.)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 these technologies are as follows:• IEEE Std 802 † : Overview and Architecture. This standard provides an over-view to the family of IEEE 802 Standards. This standard formspart of the 802.1 scope of work.• IEEE Std 802.1B [ISO DIS 15802-2]: LAN/MAN Management. Defines an Open Systems Intercon-nection (OSI) management-compatible architecture, and ser-vice and protocol elements for use in a LAN/MANenvironment for performing remote management.• ISO/IEC 10038 [ANSI/IEEE Std 802.1D]: MAC Bridging. Specifies an architecture and protocol for theinterconnection of IEEE 802 LANs below the MAC serviceboundary.• IEEE Std 802.1E [ISO DIS 15802-4]: System Load Protocol. Specifies a set of services and protocolfor those aspects of management concerned with the loading ofsystems on IEEE 802 LANs. † The 802 Architecture and Overview Specification, originally known as IEEE Std 802.1A, has been renumbered as IEEE Std 802. Thishas been done to accommodate recognition of the base standard in