vdsl-line-mib

很不错java的SNMP应用例子

VDSL-LINE-MIB DEFINITIONS ::= BEGIN

IMPORTS

MODULE-IDENTITY,
OBJECT-TYPE,
Gauge32,
Integer32,
Unsigned32,
NOTIFICATION-TYPE,
transmission                    FROM SNMPv2-SMI          -- [RFC2578]
ZeroBasedCounter64              FROM HCNUM-TC            -- [RFC2856]
TEXTUAL-CONVENTION,
RowStatus,
TruthValue                      FROM SNMPv2-TC           -- [RFC2579]
HCPerfValidIntervals,
HCPerfInvalidIntervals,
HCPerfTimeElapsed,



HCPerfIntervalThreshold,
HCPerfCurrentCount,
HCPerfIntervalCount             FROM HC-PerfHist-TC-MIB  -- [RFC3705]
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP              FROM SNMPv2-CONF         -- [RFC2580]
ifIndex                         FROM IF-MIB              -- [RFC2863]
SnmpAdminString                 FROM SNMP-FRAMEWORK-MIB; -- [RFC3411]

vdslMIB MODULE-IDENTITY
   LAST-UPDATED "200402190000Z" -- February 19, 2004
   ORGANIZATION "ADSLMIB Working Group"
   CONTACT-INFO "WG-email:  [e-mail]
          Info:      https://www1.ietf.org/mailman/listinfo/adslmib

          Chair:     Mike Sneed
                     Sand Channel Systems
          Postal:    P.O.  Box 37324
                     Raleigh, NC 27627-7324
                     USA
          Email:     [e-mail]
          Phone:     [phone]

          Co-editor: Bob Ray
                     PESA Switching Systems, Inc.
          Postal:    330-A Wynn Drive
                     Huntsville, AL 35805
                     USA
          Email:     [e-mail]
          Phone:     [phone] ext.  142

          Co-editor: Rajesh Abbi
                     Alcatel USA
          Postal:    2301 Sugar Bush Road
                     Raleigh, NC 27612-3339
                     USA
          Email:     [e-mail]
          Phone:     [phone]
        "
DESCRIPTION
    "The MIB module defining objects for the management of a pair
    of VDSL transceivers at each end of the VDSL line.  Each such
    line has an entry in an ifTable which may include multiple
    transceiver lines.  An agent may reside at either end of the
    VDSL line.  However, the MIB is designed to require no
    management communication between them beyond that inherent in
    the low-level VDSL line protocol.  The agent may monitor and
    control this protocol for its needs.



    VDSL lines may support optional Fast or Interleaved channels.
    If these are supported, additional entries corresponding to the
    supported channels must be created in the ifTable.  Thus a VDSL
    line that supports both channels will have three entries in the
    ifTable, one for each physical, fast, and interleaved, whose
    ifType values are equal to vdsl(97), fast(125), and
    interleaved(124), respectively.  The ifStackTable is used to
    represent the relationship between the entries.

    Naming Conventions:
        Vtuc -- (VTUC) transceiver at near (Central) end of line
        Vtur -- (VTUR) transceiver at Remote end of line
        Vtu  -- One of either Vtuc or Vtur
        Curr -- Current
        Prev -- Previous
        Atn  -- Attenuation
        ES   -- Errored Second.
        SES  -- Severely Errored Second
        UAS  -- Unavailable Second
        LCS  -- Line Code Specific
        Lof  -- Loss of Frame
        Lol  -- Loss of Link
        Los  -- Loss of Signal
        Lpr  -- Loss of Power
        xxxs -- Sum of Seconds in which xxx has occured
                (e.g., xxx = Lof, Los, Lpr, Lol)
        Max  -- Maximum
        Mgn  -- Margin
        Min  -- Minimum
        Psd  -- Power Spectral Density
        Snr  -- Signal to Noise Ratio
        Tx   -- Transmit
        Blks -- Blocks

    Copyright (C) The Internet Society (2004).  This version
    of this MIB module is part of RFC 3728: see the RFC
    itself for full legal notices."
       REVISION "200402190000Z" -- February 19, 2004
       DESCRIPTION "Initial version, published as RFC 3728."
   ::= { transmission 97 }

vdslLineMib    OBJECT IDENTIFIER ::= { vdslMIB 1 }
vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 }

--
-- textual conventions used in this MIB
--




VdslLineCodingType ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "This data type is used as the syntax for the VDSL Line
        Code.  Attributes with this syntax identify the line coding
        used.  Specified as an INTEGER, the three values are:

        other(1)  -- none of the following
        mcm(2)    -- Multiple Carrier Modulation
        scm(3)    -- Single Carrier Modulation"
    SYNTAX  INTEGER
        {
        other(1),
        mcm(2),
        scm(3)
        }

VdslLineEntity ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "Identifies a transceiver as being either Vtuc or Vtur.
        A VDSL line consists of two transceivers, a Vtuc and a
        Vtur.  Attributes with this syntax reference the two sides
        of a line.  Specified as an INTEGER, the two values are:

        vtuc(1)  -- central site transceiver
        vtur(2)  -- remote site transceiver"
    SYNTAX  INTEGER
        {
        vtuc(1),
        vtur(2)
        }

--
-- objects
--

vdslLineTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF VdslLineEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
        "This table includes common attributes describing
        both ends of the line.  It is required for all VDSL
        physical interfaces.  VDSL physical interfaces are
        those ifEntries where ifType is equal to vdsl(97)."
    ::= { vdslMibObjects 1 }




vdslLineEntry OBJECT-TYPE
    SYNTAX       VdslLineEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION  "An entry in the vdslLineTable."
    INDEX { ifIndex }
    ::= { vdslLineTable 1 }

VdslLineEntry ::=
    SEQUENCE
        {
        vdslLineCoding                 VdslLineCodingType,
        vdslLineType                   INTEGER,
        vdslLineConfProfile            SnmpAdminString,
        vdslLineAlarmConfProfile       SnmpAdminString
        }

vdslLineCoding OBJECT-TYPE
    SYNTAX       VdslLineCodingType
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "Specifies the VDSL coding type used on this line."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
    ::= { vdslLineEntry 1 }

vdslLineType OBJECT-TYPE
    SYNTAX       INTEGER
        {
        noChannel(1),         -- no channels exist
        fastOnly(2),          -- only fast channel exists
        interleavedOnly(3),   -- only interleaved channel exists
        fastOrInterleaved(4), -- either fast or interleaved channel
                              -- exist, but only one at a time
        fastAndInterleaved(5) -- both fast and interleaved channels
                              -- exist
        }
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "Defines the type of VDSL physical line entity that exists,
        by defining whether and how the line is channelized.  If









        the line is channelized,  the value will be other than
        noChannel(1).  This object defines which channel type(s)
        are supported.  Defined values are:

        noChannel(1)          -- no channels exist
        fastOnly(2)           -- only fast channel exists
        interleavedOnly(3)    -- only interleaved channel exists
        fastOrInterleaved(4)  -- either fast or interleaved channel
                              -- exist, but only one at a time
        fastAndInterleaved(5) -- both fast and interleaved channels
                              -- exist

        Note that 'slow' and 'interleaved' refer to the same
        channel.  In the case that the line is channelized, the
        manager can use the ifStackTable to determine the ifIndex
        for the associated channel(s)."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
    ::= { vdslLineEntry 2 }

vdslLineConfProfile OBJECT-TYPE
    SYNTAX       SnmpAdminString (SIZE(1..32))
    MAX-ACCESS   read-write
    STATUS       current
    DESCRIPTION
        "The value of this object identifies the row in the VDSL
        Line Configuration Profile Table, vdslLineConfProfileTable,
        which applies for this VDSL line, and channels if
        applicable.

        This object MUST be maintained in a persistent manner."
    DEFVAL       { "DEFVAL" }
    ::= { vdslLineEntry 3 }

vdslLineAlarmConfProfile OBJECT-TYPE
    SYNTAX       SnmpAdminString (SIZE(1..32))
    MAX-ACCESS   read-write
    STATUS       current
    DESCRIPTION
        "The value of this object identifies the row in the VDSL
        Line Alarm Configuration Profile Table,
        vdslLineAlarmConfProfileTable, which applies to this
        VDSL line, and channels if applicable.

        This object MUST be maintained in a persistent manner."
    DEFVAL       { "DEFVAL" }
    ::= { vdslLineEntry 4 }

vdslPhysTable OBJECT-TYPE



    SYNTAX       SEQUENCE OF VdslPhysEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
        "This table provides one row for each Vtu.  Each row
        contains the Physical Layer Parameters table for that
        Vtu.  VDSL physical interfaces are those ifEntries where
        ifType is equal to vdsl(97)."
    ::= { vdslMibObjects 2 }

vdslPhysEntry OBJECT-TYPE
    SYNTAX       VdslPhysEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION  "An entry in the vdslPhysTable."
    INDEX { ifIndex,
            vdslPhysSide }
    ::= { vdslPhysTable 1 }

VdslPhysEntry ::=
    SEQUENCE
        {
        vdslPhysSide                   VdslLineEntity,
        vdslPhysInvSerialNumber        SnmpAdminString,
        vdslPhysInvVendorID            SnmpAdminString,
        vdslPhysInvVersionNumber       SnmpAdminString,
        vdslPhysCurrSnrMgn             Integer32,
        vdslPhysCurrAtn                Gauge32,
        vdslPhysCurrStatus             BITS,
        vdslPhysCurrOutputPwr          Integer32,
        vdslPhysCurrAttainableRate     Gauge32,
        vdslPhysCurrLineRate           Gauge32
        }

vdslPhysSide OBJECT-TYPE
    SYNTAX       VdslLineEntity
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
        "Identifies whether the transceiver is the Vtuc or Vtur."
    ::= { vdslPhysEntry 1 }

vdslPhysInvSerialNumber OBJECT-TYPE
    SYNTAX       SnmpAdminString(SIZE (0..32))
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The vendor specific string that identifies the



        vendor equipment."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
    ::= { vdslPhysEntry 2 }

vdslPhysInvVendorID OBJECT-TYPE
    SYNTAX       SnmpAdminString (SIZE (0..16))
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The vendor ID code is a copy of the binary vendor
        identification field expressed as readable characters
        in hexadecimal notation."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
    ::= { vdslPhysEntry 3 }

vdslPhysInvVersionNumber OBJECT-TYPE
    SYNTAX       SnmpAdminString (SIZE (0..16))
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "The vendor specific version number sent by this Vtu
        as part of the initialization messages.  It is a copy
        of the binary version number field expressed as
        readable characters in hexadecimal notation."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
    ::= { vdslPhysEntry 4 }

vdslPhysCurrSnrMgn OBJECT-TYPE
    SYNTAX       Integer32 (-127..127)
    UNITS        "0.25dBm"
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "Noise Margin as seen by this Vtu with respect to its
        received signal in 0.25dB.  The effective range is
        -31.75 to +31.75 dB."
    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
     ::= { vdslPhysEntry 5 }

vdslPhysCurrAtn OBJECT-TYPE
    SYNTAX       Gauge32 (0..255)
    UNITS        "0.25dBm"
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
        "Measured difference in the total power transmitted by
        the peer Vtu and the total power received by this Vtu.
        The effective range is 0 to +63.75 dB."



    REFERENCE    "T1E1.4/2000-009R3, Part 1, common spec"
     ::= { vdslPhysEntry 6 }

vdslPhysCurrStatus OBJECT-TYPE
    SYNTAX       BITS
        {
        noDefect(0),
        lossOfFraming(1),
        lossOfSignal(2),
        lossOfPower(3),
        lossOfSignalQuality(4),
        lossOfLink(5),
        dataInitFailure(6),
        configInitFailure(7),
        protocolInitFailure(8),
        noPeerVtuPresent(9)
        }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Indicates current state of the Vtu line.  This is a
        bit-map of possible conditions.  The various bit
        positions are:

        0   noDefect             There are no defects on the line.

        1   lossOfFraming        Vtu failure due to not receiving