⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2358.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
   interface should implement is dependent on the maximum speed   supported on the interface.  The EtherLike-MIB etherCompliance   compliance statement applies to all Ethernet-like interfaces whose   maximum supported speed is 10 Mbit/sec or less.  There are no   implementation differences. Similarly, the EtherLike-MIB   ether100MbsCompliance compliance statement applies to all Ethernet-   like interfaces whose maximum supported speed is 100Mbit/sec.   An interface that is capable of operating at 100Mbit/sec MUST   implement the ether100MbsCompliance compliance statement, even if it   is currently operating at a lower speed.  Counters in the   ether100MbsCompliance compliance statement that only apply to 100   Mbit interfaces would simply not increment when the interface is   operating at a lower speed.Flick & Johnson             Standards Track                     [Page 6]RFC 2358         MIB for Ethernet-like Interface Types         June 19983.2.7.  Specific Interface MIB Objects   The following table provides specific implementation guidelines for   applying the interface group objects to ethernet-like media.     Object     ifIndex                    Each ethernet-like interface is                                represented by an ifEntry.  The                                dot3StatsTable in this MIB module is                                indexed by dot3StatsIndex. The interface                                identified by a particular value of                                dot3StatsIndex is the same interface as                                identified by the same value of ifIndex.     ifDescr                    Refer to [12].     ifType                     Refer to section 3.2.6.     ifMtu                      1500 octets.     ifSpeed                    The current operational speed of the                                interface in bits per second. For                                current ethernet-like interfaces, this                                will be equal to 1,000,000 (1 million),                                10,000,000 (10 million), or 100,000,000                                (100 million). If the interface                                implements auto-negotiation,                                auto-negotiation is enabled for this                                interface, and the interface has not yet                                negotiated to an operational speed, this                                object SHOULD reflect the maximum speed                                supported by the interface.  Note that                                this object MUST NOT indicate a doubled                                value when operating in full-duplex                                mode.  It MUST indicate the correct                                line speed regardless of the current                                duplex mode.  The correct object to use                                to determine the duplex mode of the                                interface is the ifMauType object in the                                802.3 MAU MIB.     ifPhysAddress              Refer to section 3.2.5.     ifAdminStatus              Write access is not required.  Support                                for 'testing' is not required.Flick & Johnson             Standards Track                     [Page 7]RFC 2358         MIB for Ethernet-like Interface Types         June 1998     ifOperStatus               The operational state of the interface.                                Support for 'testing' is not required.                                The value 'dormant' has no meaning for                                an ethernet-like interface.     ifLastChange               Refer to [12].     ifInOctets                 The number of octets in valid MAC frames                                received on this interface, including                                the MAC header and FCS.     ifInUcastPkts              Refer to [12].     ifInDiscards               Refer to [12].     ifInErrors                 The sum for this interface of                                dot3StatsAlignmentErrors,                                dot3StatsFCSErrors,                                dot3StatsFrameTooLongs,                                dot3StatsInternalMacReceiveErrors and                                dot3StatsSymbolErrors.     ifInUnknownProtos          Refer to [12].     ifOutOctets                The number of octets transmitted in                                valid MAC frames on this interface,                                including the MAC header and FCS.     ifOutUcastPkts             Refer to [12].     ifOutDiscards              Refer to [12].     ifOutErrors                The sum for this interface of:                                dot3StatsSQETestErrors,                                dot3StatsLateCollisions,                                dot3StatsExcessiveCollisions,                                dot3StatsInternalMacTransmitErrors and                                dot3StatsCarrierSenseErrors.     ifName                     Locally-significant textual name for the                                interface (e.g. lan0).     ifInMulticastPkts          Refer to [12].     ifInBroadcastPkts          Refer to [12].     ifOutMulticastPkts         Refer to [12].Flick & Johnson             Standards Track                     [Page 8]RFC 2358         MIB for Ethernet-like Interface Types         June 1998     ifOutBroadcastPkts         Refer to [12].     ifHCInOctets               64-bit versions of counters.  Required     ifHCOutOctets              for ethernet-like interfaces that are                                capable of operating at 20Mbit/sec or                                faster, even if the interface is                                currently operating at less than                                20Mbit/sec.     ifHCInUcastPkts            64-bit versions of packet counters.     ifHCInMulticastPkts        Support for these counters is not     ifHCInBroadcastPkts        required for the interface types     ifHCOutUcastPkts           supported by this MIB.  They are only     ifHCOutMulticastPkts       required for interfaces capable of     ifHCOutBroadcastPkts       operating at 640Mbit/sec or faster.                                Note that a future revision of this                                document may support faster interfaces,                                and therefore may require support for                                these counters.     ifLinkUpDownTrapEnable     Refer to [12].  Default is 'enabled'     ifHighSpeed                The current operational speed of the                                interface in millions of bits per                                second. For current ethernet-like                                interfaces, this will be equal to 1, 10,                                or 100.  If the interface implements                                auto-negotiation, auto-negotiation is                                enabled for this interface, and the                                interface has not yet negotiated to an                                operational speed, this object SHOULD                                reflect the maximum speed supported by                                the interface. Note that this object                                MUST NOT indicate a doubled value when                                operating in full-duplex mode.  It MUST                                indicate the correct line speed                                regardless of the current duplex mode.                                The correct object to use to determine                                the duplex mode of the interface is the                                ifMauType object in the 802.3 MAU MIB.     ifPromiscuousMode          Refer to [12].     ifConnectorPresent         This will normally be 'true'.     ifAlias                    Refer to [12].     ifCounterDiscontinuityTime Refer to [12].Flick & Johnson             Standards Track                     [Page 9]RFC 2358         MIB for Ethernet-like Interface Types         June 1998     ifStackHigherLayer         Refer to section 3.2.1.     ifStackLowerLayer     ifStackStatus     ifRcvAddressAddress        Refer to section 3.2.4.     ifRcvAddressStatus     ifRcvAddressType3.3.  Relation to the 802.3 MAU MIB   Support for the mauModIfCompl compliance statement of the MAU-MIB   [14] is REQUIRED for Ethernet-like interfaces.  This MIB is needed in   order to allow applications to determine the current MAU type in use   by the interface.  The MAU type indicates not only the media type in   use, but also indicates whether the interface is operating in half-   duplex or full-duplex mode.  Implementing this MIB module without   implementing the MAU-MIB would leave applications with no standard   way to determine the duplex mode of the interface.3.4.  Mapping of IEEE 802.3 Managed Objects   IEEE 802.3 Managed Object         Corresponding SNMP Object   oMacEntity    .aMACID                          dot3StatsIndex or                                     IF-MIB - ifIndex    .aFramesTransmittedOK            IF-MIB - ifOutUCastPkts +                                              ifOutMulticastPkts +                                              ifOutBroadcastPkts    .aSingleCollisionFrames          dot3StatsSingleCollisionFrames    .aMultipleCollisionFrames        dot3StatsMultipleCollisionFrames    .aFramesReceivedOK               IF-MIB - ifInUcastPkts +                                              ifInMulticastPkts +                                              ifInBroadcastPkts    .aFrameCheckSequenceErrors       dot3StatsFCSErrors    .aAlignmentErrors                dot3StatsAlignmentErrors    .aOctetsTransmittedOK            IF-MIB - ifOutOctets    .aFramesWithDeferredXmissions    dot3StatsDeferredTransmissions    .aLateCollisions                 dot3StatsLateCollisions    .aFramesAbortedDueToXSColls      dot3StatsExcessiveCollisions    .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors    .aCarrierSenseErrors             dot3StatsCarrierSenseErrors    .aOctetsReceivedOK               IF-MIB - ifInOctets    .aFramesLostDueToIntMACRcvError  dot3StatsInternalMacReceiveErrors    .aPromiscuousStatus              IF-MIB - ifPromiscuousMode    .aReadMulticastAddressList       IF-MIB - ifRcvAddressTable    .aMulticastFramesXmittedOK       IF-MIB - ifOutMulticastPkts    .aBroadcastFramesXmittedOK       IF-MIB - ifOutBroadcastPktsFlick & Johnson             Standards Track                    [Page 10]RFC 2358         MIB for Ethernet-like Interface Types         June 1998    .aMulticastFramesReceivedOK      IF-MIB - ifInMulticastPkts    .aBroadcastFramesReceivedOK      IF-MIB - ifInBroadcastPkts    .aFrameTooLongErrors             dot3StatsFrameTooLongs    .aReadWriteMACAddress            IF-MIB - ifPhysAddress    .aCollisionFrames                dot3CollFrequencies    .acAddGroupAddress               IF-MIB - ifRcvAddressTable    .acDeleteGroupAddress            IF-MIB - ifRcvAddressTable    .acExecuteSelfTest               dot3TestLoopBack   oPHYEntity    .aSQETestErrors                  dot3StatsSQETestErrors    .aSymbolErrorDuringCarrier       dot3StatsSymbolErrors   The following IEEE 802.3 managed objects have been removed from this   MIB module as a result of implementation feedback:   oMacEntity     .aFramesWithExcessiveDeferral     .aInRangeLengthErrors     .aOutOfRangeLengthField     .aMACEnableStatus     .aTransmitEnableStatus     .aMulticastReceiveStatus     .acInitializeMAC   Please see [15] for the detailed reasoning on why these objects were   removed.4.  Definitions   EtherLike-MIB DEFINITIONS ::= BEGIN       IMPORTS           MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,           Counter32, mib-2, transmission               FROM SNMPv2-SMI           MODULE-COMPLIANCE, OBJECT-GROUP               FROM SNMPv2-CONF           ifIndex, InterfaceIndex               FROM IF-MIB;       etherMIB MODULE-IDENTITY           LAST-UPDATED "9806032150Z"  -- June 3, 1998           ORGANIZATION "IETF 802.3 Hub MIB Working Group"           CONTACT-INFO               "WG E-mail: hubmib@hprnd.rose.hp.com             To subscribe: hubmib-request@hprnd.rose.hp.comFlick & Johnson             Standards Track                    [Page 11]RFC 2358         MIB for Ethernet-like Interface Types         June 1998                    Chair: Dan Romascanu                   Postal: LANNET Ltd.                           Atidum Technology Park, Bldg. 3                           Tel Aviv 61131                           Israel                      Tel: +972 3 645 8414                   E-mail: dromasca@lannet.com                  Editor: John Flick                  Postal: Hewlett-Packard Company                          8000 Foothills Blvd. M/S 5556                          Roseville, CA 95747-5556                          USA                     Tel: +1 916 785 4018                     Fax: +1 916 785 3583                  E-mail: johnf@hprnd.rose.hp.com

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -