rfc1398-mib

很不错java的SNMP应用例子

               dot3StatsCarrierSenseErrors object.

               The precise meaning of the count represented by
               an instance of this object is implementation-
               specific.  In particular, an instance of this
               object may represent a count of transmission
               errors on a particular interface that are not
               otherwise counted."
     REFERENCE
               "IEEE 802.3 Layer Management"
     ::= { dot3StatsEntry 10 }


dot3StatsCarrierSenseErrors   OBJECT-TYPE
     SYNTAX    Counter
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "The number of times that the carrier sense
               condition was lost or never asserted when
               attempting to transmit a frame on a particular
               interface.

               The count represented by an instance of this
               object is incremented at most once per
               transmission attempt, even if the carrier sense
               condition fluctuates during a transmission
               attempt."
     REFERENCE
               "IEEE 802.3 Layer Management"
     ::= { dot3StatsEntry 11 }

-- { dot3StatsEntry 12 } is not assigned

dot3StatsFrameTooLongs   OBJECT-TYPE
     SYNTAX    Counter
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "A count of frames received on a particular
               interface that exceed the maximum permitted
               frame size.

               The count represented by an instance of this
               object is incremented when the frameTooLong
               status is returned by the MAC service to the
               LLC (or other MAC user). Received frames for
               which multiple error conditions obtain are,
               according to the conventions of IEEE 802.3
               Layer Management, counted exclusively according
               to the error status presented to the LLC."
     REFERENCE
               "IEEE 802.3 Layer Management"
     ::= { dot3StatsEntry 13 }



-- { dot3StatsEntry 14 } is not assigned


-- { dot3StatsEntry 15 } is not assigned

dot3StatsInternalMacReceiveErrors   OBJECT-TYPE
     SYNTAX    Counter
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "A count of frames for which reception on a
               particular interface fails due to an internal
               MAC sublayer receive error. A frame is only
               counted by an instance of this object if it is
               not counted by the corresponding instance of
               either the dot3StatsFrameTooLongs object, the
               dot3StatsAlignmentErrors object, or the
               dot3StatsFCSErrors object.

               The precise meaning of the count represented by
               an instance of this object is implementation-
               specific.  In particular, an instance of this
               object may represent a count of receive errors
               on a particular interface that are not
               otherwise counted."
     REFERENCE
               "IEEE 802.3 Layer Management"
     ::= { dot3StatsEntry 16 }

-- the Ethernet-like Collision Statistics group

-- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering

dot3CollTable   OBJECT-TYPE
     SYNTAX    SEQUENCE OF Dot3CollEntry
     ACCESS    not-accessible
     STATUS    mandatory
     DESCRIPTION
               "A collection of collision histograms for a
               particular set of interfaces."
     ::= { dot3 5 }


dot3CollEntry   OBJECT-TYPE
     SYNTAX    Dot3CollEntry
     ACCESS    not-accessible
     STATUS    mandatory
     DESCRIPTION
               "A cell in the histogram of per-frame
               collisions for a particular interface.  An
               instance of this object represents the
               frequency of individual MAC frames for which
               the transmission (successful or otherwise) on a
               particular interface is accompanied by a
               particular number of media collisions."
     INDEX     { dot3CollIndex, dot3CollCount }
     ::= { dot3CollTable 1 }



Dot3CollEntry ::= SEQUENCE {
     dot3CollIndex
          INTEGER,
     dot3CollCount
          INTEGER,
     dot3CollFrequencies
          Counter
}


dot3CollIndex   OBJECT-TYPE
     SYNTAX    INTEGER
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "The index value that uniquely identifies the
               interface to which a particular collision
               histogram cell pertains.  The interface
               identified by a particular value of this index
               is the same interface as identified by the same
               value of ifIndex."
     ::= { dot3CollEntry 1 }


dot3CollCount   OBJECT-TYPE
     SYNTAX    INTEGER (1..16)
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "The number of per-frame media collisions for
               which a particular collision histogram cell
               represents the frequency on a particular
               interface."
     ::= { dot3CollEntry 2 }


dot3CollFrequencies   OBJECT-TYPE
     SYNTAX    Counter
     ACCESS    read-only
     STATUS    mandatory
     DESCRIPTION
               "A count of individual MAC frames for which the
               transmission (successful or otherwise) on a
               particular interface is accompanied by a
               particular number of media collisions."
     ::= { dot3CollEntry 3 }


      --  802.3 Tests

      -- The ifExtnsTestTable defined in RFC 1229 provides a common
      -- means for a manager to test any interface corresponding to
      -- a value of ifIndex.

      -- At this time, one well known test (testFullDuplexLoopBack) is
      -- defined in RFC 1229.  For ethernet-like interfaces, this test
      -- configures the MAC chip and executes an internal loopback
      -- test of memory and the MAC chip logic.  This loopback test can
      -- only be executed if the interface is offline.  Once the test
      -- has completed, the MAC chip should be reinitialized for network
      -- operation, but it should remain offline.

      -- If an error occurs during a test, the object ifExtnsTestResult
      -- (defined in RFC 1229) will be set to failed(7).  The following
      -- two OBJECT IDENTIFIERs may be used to provided more
      -- information as values for the object ifExtnsTestCode in
      -- RFC 1229:

dot3Errors             OBJECT IDENTIFIER ::= { dot3 7 }

                     -- couldn't initialize MAC chip for test
dot3ErrorInitError     OBJECT IDENTIFIER ::= { dot3Errors 1 }

                      -- expected data not received (or not
                      -- received correctly) in loopback test
dot3ErrorLoopbackError OBJECT IDENTIFIER ::= { dot3Errors 2 }

       -- Tests
        --  TDR Test

       -- Another test, specific to ethernet-like interfaces with the
       -- exception of 10BaseT and 10BaseF, is Time-domain Reflectometry (TDR).
       -- The TDR value may be useful in determining the approximate distance
       -- to a cable fault.  It is advisable to repeat this test to check for
       -- a consistent resulting TDR value, to verify that there is a fault.

dot3Tests   OBJECT IDENTIFIER ::= { dot3 6 }
dot3TestTdr OBJECT IDENTIFIER ::= { dot3Tests 1 }

       -- A TDR test returns as its result the time interval, measured
       -- in 10 MHz ticks or 100 nsec units, between the start of
       -- TDR test transmission and the subsequent detection of a
       -- collision or deassertion of carrier.  On successful completion
       -- of a TDR test, the appropriate instance of ifExtnsTestResult
       -- contains the OBJECT IDENTIFIER of the MIB object which
       -- contains the value of this time interval.


       --  802.3 Hardware Chipsets

       -- The object ifExtnsChipSet is provided in RFC 1229 to identify
       -- the MAC hardware used to communcate on an interface.  The
       -- following hardware chipsets are provided for 802.3:

  dot3ChipSets          OBJECT IDENTIFIER ::= { dot3 8 }
  dot3ChipSetAMD        OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
  dot3ChipSetAMD7990    OBJECT IDENTIFIER ::= { dot3ChipSetAMD 1 }
  dot3ChipSetAMD79900   OBJECT IDENTIFIER ::= { dot3ChipSetAMD 2 }

  dot3ChipSetIntel      OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
  dot3ChipSetIntel82586 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 1 }
  dot3ChipSetIntel82596 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 2 }
  dot3ChipSetSeeq       OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
  dot3ChipSetSeeq8003   OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 }

  dot3ChipSetNational      OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
  dot3ChipSetNational8390  OBJECT IDENTIFIER ::=
                                 { dot3ChipSetNational 1 }
  dot3ChipSetNationalSonic OBJECT IDENTIFIER ::=
                                 { dot3ChipSetNational 2 }

  dot3ChipSetFujitsu       OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
  dot3ChipSetFujitsu86950  OBJECT IDENTIFIER ::=
                                 { dot3ChipSetFujitsu 1 }
  dot3ChipSetFujitsu86960  OBJECT IDENTIFIER ::=
                                 { dot3ChipSetFujitsu 2 }

       -- For those chipsets not represented above, OBJECT IDENTIFIER
       -- assignment is required in other documentation, e.g., assignment
       -- within that part of the registration tree delegated to
       -- individual enterprises (see RFC 1155).

END