IEEE 802 3 1-2013 en Management Information Base (MIB) Definitions for Ethernet (IEEE Computer Society)《以太网用管理信息库(MIB)定义的IEEE标准》.pdf

1、Reference numberISO/IEC/IEEE 8802-3-1:2015(E)IEEE 201INTERNATIONAL STANDARD ISO/IEC/IEEE8802-3-1Information technology Management Information Base (MIB) Definitions for Ethernet Part 3-1: Technologies de linformation Base dinformation de gestion Dfinitions pour lEthernet Partie 3-1: First edition201

2、5-08-01ISO/IEC/IEEE 8802-3-1:2015(E) COPYRIGHT PROTECTED DOCUMENT IEEE 2015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in wr

3、iting from ISO, IEC or IEEE at the respective address below. ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 3, rue de Varemb 3 Park Avenue, New York CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA Tel. + 41 22 749 01 11 Switzerl

4、and E-mail stds.iprieee.org Fax + 41 22 749 09 47 E-mail inmailiec.ch Web www.ieee.org E-mail copyrightiso.org Web www.iec.ch Web www.iso.org Published in Switzerland ii IEEE 2015 All rights reservedISO/IEC/IEEE 8802-3-1:2015(E) IEEE 2015 All rights reserved iiiForeword ISO (the International Organi

5、zation 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 resp

6、ective 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 informat

7、ion technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a c

8、onsensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE admi

9、nisters the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft

10、 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. Attention is called to the possibility that implementation of this standa

11、rd may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a

12、license may be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in

13、any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the

14、IEEE Standards Association. ISO/IEC/IEEE 8802-3-1 was prepared by the LAN/MAN Standards Committee of the IEEE Computer Society (as IEEE 802.3.1:2013). It was adopted by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunication and information exchange betw

15、een systems, in parallel with its approval by the ISO/IEC national bodies, under the “fast-track procedure” defined in the Partner Standards Development Organization cooperation agreement between ISO and IEEE. IEEE is responsible for the maintenance of this document with participation and input from

16、 ISO/IEC national bodies. g3g3g3IEEE Standard for Management Information Base (MIB) Definitions for Ethernet Sponsored by the LAN/MAN Standards Committeeg3IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Societyg3IEEE Std 802.3.1-2013(Revision ofIEEE Std 802.3.1-2011) ,(6WG 5HYLVLRQRI,(6

17、WG ,(6WDQGDUGIRU 0DQDJHPHQW,QIRUPDWLRQ%DVH 0,% HILQLWLRQVIRU(WKHUQHW6SRQVRU/$10$16WDQGDUGV +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center.,62,( Access transmission systems on metal

18、lic access cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Functional requirements.4IEEE Std 802, IEEE Standard for Local and Metropolitan Area NetworksArchitecture and Overview.5,6IEEE Std 802.1D, IEEE Standard for Local and Metropolitan Area NetworksMedia Access Control (MAC) Bridg

19、es.IEEE Std 802.1AB-2009, IEEE Standard for Local and Metropolitan Area NetworksStation and Media Access Control Discovery.IEEE Std 802.3, IEEE Standard for Ethernet.IEEE Std 802.9a-1995, IEEE Standards for Local and Metropolitan Area NetworksSupplement to Integrated Services (IS) LAN Interface at t

20、he Medium Access Control (MAC) and Physical (PHY) LayersSpecification of IsLAN16-T. IETF RFC 1213, Management Information Base for Network Management of TCP/IP-based internets: MIB-II, McCloghrie, K., and Rose, M., Mar. 1991.7IETF RFC 1516, Definitions of Managed Objects for IEEE 802.3 Repeater Devi

21、ces, McMaster, D., and McCloghrie, K., Sept. 1993.IETF RFC 2119, Keywords for use in RFCs to Indicate Requirement Levels, Bradner, S., Mar. 1997.IETF RFC 2434, Guidelines for Writing an IANA Considerations Section in RFCs, Narten, T. and Alvestrand, H., Oct, 1998.IETF STD 58 (RFC 2578), Structure of

22、 Management Information Version 2 (SMIv2), McCloghrie, K., Perkins, D., and Schoenwaelder, J., Apr. 1999.IETF STD 58 (RFC 2579), Textual Conventions for SMIv2, McCloghrie, K., Perkins, D., and Schoenwaelder, J., Apr. 1999.IETF STD 58 (RFC 2580), Conformance Statements for SMIv2, McCloghrie, K., Perk

23、ins, D., and Schoenwaelder, J., Apr. 1999.3ANSI publications are available from the American National Standards Institute (http:/www.ansi.org/).4ETSI publications are available from the European Telecommunications Standards Institute (http:/www.etsi.org/).5IEEE publications are available from The In

24、stitute of Electrical and Electronics Engineers (http:/standards.ieee.org/).6The IEEE standards or products referred to in this clause are trademarks of The Institute of Electrical and Electronics Engineers, Inc.7IETF documents (i.e., RFCs) are available for download at http:/www.rfc-archive.org/.,6

25、2,(however, the range of configurations may be very large, with several modules entering one slot, or one module covering several slots.non-trivial repeater: A repeater as defined by IEEE Std 802.3 having multiple ports.Path Coding violations: In IEEE Std 802.3, the path layer coding violations coun

26、t is based on block errors and not on BIP-8 errors; i.e., it is incremented only once for each B3 byte that indicates incorrect parity, regardless of the number of bits in error. Note that Section 8.4.5.1 of ANSI T1.231-1997 allows either path BIP-8 errors or path block errors to be used for the pat

27、h layer error count.repeater system: A managed entity compliant with this standard and incorporating at least one managed IEEE 802.3 repeater.repeater-unit: The portion of a repeater that is inboard of its Physical Medium Attachment (PMA)/Physical Signaling Sublayer (PLS) or PMA/Physical Coding Subl

28、ayer (PCS).Signal Label Mismatch: This defect is called Payload Label Mismatch (PLM) in IEEE Std 802.3. It is reported by setting both the sonetPathSignalLabelMismatch bit in the appropriate instance of sonetPathCurrentStatus (defined in IETF RFC 3592) and the etherWisPathPLM bit in the correspondin

29、g instance of etherWisPathCurrentStatus.stack: A scalable system in which modularity is achieved by interconnecting a number of different systems.9The IEEE Standards Dictionary Online subscription is available at http:/www.ieee.org/portal/innovate/products/standard/standards_dictionary.html.,62,(&,(

30、 ( ,($OOULJKWVUHVHUYHG,(67 ,(67$1$5)250$1$*(0(17,1)250$7,218 &RSULJKW,($OOULJKWVUHVHUYHGSTS-Path Remote Defect Indication: IEEE Std 802.3 mandates the use of ERDI-P (Enhanced Remote Defect Indication-Path) defined in ANSI T1.231-1997 to signal remote server defects (triggered by path AIS or path LOP

31、) and remote payload defects (triggered by Payload Label Mismatch or Loss of Codegroup Delineation). IETF RFC 3592 defines the one-bit RDI-P (Remote Defect Indication-Path), which signals remote server detects (i.e., path AIS and path LOP) only. An implementation of the MIB module defined in Clause

32、12 of IEEE Std 802.3.1-2013 sets the sonetPathSTSRDI bit in the appropriate instance of sonetPathCurrentStatus when it receives an ERDI-P server defect indication from the remote end. Both ERDI-P payload defects and ERDI-P server defects are reported in the object etherWisFarEndPathCurrentStatus.sys

33、tem: An entity compliant with one or more Management Information Base (MIB) modules of this standard.system interconnect segment: An internal segment allowing interconnection of ports belonging to different physical entities into the same logical managed repeater, bridge, or other system. Examples o

34、f implementation might be backplane busses in modular hubs, or chaining cables in stacks of bridges/switches. It is not uncommon for such segments to be a proprietary implementation.trivial repeater-unit: An isolated port that can gather statistics.,62,(&,( ( ,($OOULJKWVUHVHUYHG%$6( 0,% (),17,216)25

35、7+(51(7,(67&RSULJKW,($OOULJKWVUHVHUYHG 9$EEUHYLDWLRQVACK acknowledgeAIS Alarm Indication SignalARP address resolution protocolASCII American Standard Code for Information InterchangeAtn attenuationBER bit error ratioBIP bit interleaved parityBW bandwidthCO central officeCPE customer premises equipm

36、entCRC cyclic redundancy checkDTE data terminal equipmentEFM Ethernet in the First MileEFMCu EFM copperELTE Ethernet line termination equipmentEPON Ethernet passive optical networkERDI-P enhanced remote defect indicationpathFCS frame check sequenceFEC forward error correctionGDMO Guidelines for Defi

37、nition of Managed ObjectsGMII gigabit media independent interfaceIANA Internet Assigned Numbers AuthorityIETF Internet Engineering Task ForceIFG inter-frame gapITU International Telecommunication UnionLAN local area networkLCD Loss of Codegroup DeliniationLLC logical link controlLLDP logical link di

38、scovery protocolLLDPDU logical link discovery protocol data unitLLID logical link identifierLOP Loss of PointerLTE line termination equipmentMAC media access controlMAU medium attachment unitMb/s megabit per secondMDI medium dependent interfaceMDIO management data input/outputMII media independent i

39、nterfaceMP2PE multipoint-to-point emulationMPCP multipoint control protocolMPCPDU multipoint control protocol data unitMTU maximum transmission unitNMS network management system,62,(&,( ( ,($OOULJKWVUHVHUYHG,(67 ,(67$1$5)250$1$*(0(17,1)250$7,2110 &RSULJKW,($OOULJKWVUHVHUYHGOAM operations, administra

40、tion, and maintenanceOAMPDU operations, administration, and maintenance protocol data unitOID object identifierOLT optical line terminalOMP optical multipointONU optical network unitOSI Open Systems InterconnectionP2MP point-to-multipointP2PE point-to-point emulationPAF PME aggregation functionPBO p

41、ower back-offPCS physical coding sublayerPD powered devicePDU protocol data unitPHY Physical Layer entityPLM Payload Label MismatchPMA physical medium attachmentPMD physical medium dependentPME physical medium entityPON passive optical networkPSD power spectral densityPSE power sourcing equipmentRFC

42、 Request for CommentsROM read-only-memoryRS reconciliation sublayerRTT round-trip timeSDH Synchronous Digital HierarchySLA service level agreementSLD start of LLID delimiterSMIv2 structure of management information version 2SNMP simple network management protocolSNR signal-to-noise ratioSONET Synchronous Optical NetworkTCPAM trellis coded pulse amplitude modulationTDM time division multiplexingTDMA time division multiple accessTLV type/length/valueTQ time quantaWAN wide area networkWDM wavelength division multiplexingWIS WAN interface sublayer,62,(&,( ( ,($OOULJKWVUHVHUYHG