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

📄 rfc2981.mib

📁 wm PNE 3.3 source code, running at more than vxworks6.x version.
💻 MIB
📖 第 1 页 / 共 5 页
字号:
DISMAN-EVENT-MIB DEFINITIONS ::= BEGINIMPORTS    MODULE-IDENTITY, OBJECT-TYPE,    Integer32, Unsigned32,    NOTIFICATION-TYPE, Counter32,    Gauge32, mib-2, zeroDotZero         FROM SNMPv2-SMI    TEXTUAL-CONVENTION, RowStatus,    TruthValue                FROM SNMPv2-TC    MODULE-COMPLIANCE, OBJECT-GROUP,    NOTIFICATION-GROUP             FROM SNMPv2-CONF    sysUpTime                 FROM SNMPv2-MIB    SnmpTagValue              FROM SNMP-TARGET-MIB    SnmpAdminString           FROM SNMP-FRAMEWORK-MIB;dismanEventMIB MODULE-IDENTITY    LAST-UPDATED "200010160000Z"            -- 16 October 2000    ORGANIZATION "IETF Distributed Management Working Group"    CONTACT-INFO "Ramanathan Kavasseri                  Cisco Systems, Inc.                  170 West Tasman Drive,                  San Jose CA 95134-1706.                  Phone: +1 408 526 4527                  Email: ramk@cisco.com"    DESCRIPTION     "The MIB module for defining event triggers and actions     for network management purposes."-- Revision History       REVISION     "200010160000Z"            -- 16 October 2000       DESCRIPTION  "This is the initial version of this MIB.                    Published as RFC 2981"    ::= { mib-2 88 }dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }-- Management Triggered Event (MTE) objectsmteResource           OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }mteTrigger            OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }mteObjects            OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }mteEvent              OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }---- Textual Conventions--FailureReason ::= TEXTUAL-CONVENTION    STATUS      current    DESCRIPTION        "Reasons for failures in an attempt to perform a management        request.        The first group of errors, numbered less than 0, are related        to problems in sending the request.  The existence of a        particular error code here does not imply that all        implementations are capable of sensing that error and        returning that code.        The second group, numbered greater than 0, are copied        directly from SNMP protocol operations and are intended to        carry exactly the meanings defined for the protocol as returned        in an SNMP response.        localResourceLack       some local resource such as memory                                lacking or                                mteResourceSampleInstanceMaximum                                exceeded        badDestination          unrecognized domain name or otherwise                                invalid destination address        destinationUnreachable  can't get to destination address        noResponse              no response to SNMP request        badType                 the data syntax of a retrieved object                                as not as expected        sampleOverrun           another sample attempt occurred before                                the previous one completed"    SYNTAX      INTEGER { localResourceLack(-1),                          badDestination(-2),                          destinationUnreachable(-3),                          noResponse(-4),                          badType(-5),                          sampleOverrun(-6),                          noError(0),                          tooBig(1),                          noSuchName(2),                          badValue(3),                          readOnly(4),                          genErr(5),                          noAccess(6),                          wrongType(7),                          wrongLength(8),                          wrongEncoding(9),                          wrongValue(10),                          noCreation(11),                          inconsistentValue(12),                          resourceUnavailable(13),                          commitFailed(14),                          undoFailed(15),                          authorizationError(16),                          notWritable(17),                          inconsistentName(18) }---- Resource Control Section--mteResourceSampleMinimum OBJECT-TYPE    SYNTAX      Integer32 (1..2147483647)    UNITS       "seconds"    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION        "The minimum mteTriggerFrequency this system will        accept.  A system may use the larger values of this minimum to        lessen the impact of constant sampling.  For larger        sampling intervals the system samples less often and        suffers less overhead.  This object provides a way to enforce        such lower overhead for all triggers created after it is        set.        Unless explicitly resource limited, a system's value for        this object SHOULD be 1, allowing as small as a 1 second        interval for ongoing trigger sampling.        Changing this value will not invalidate an existing setting        of mteTriggerFrequency."    ::= { mteResource 1 }mteResourceSampleInstanceMaximum OBJECT-TYPE    SYNTAX      Unsigned32    UNITS       "instances"    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION        "The maximum number of instance entries this system will        support for sampling.        These are the entries that maintain state, one for each        instance of each sampled object as selected by        mteTriggerValueID.  Note that wildcarded objects result        in multiple instances of this state.        A value of 0 indicates no preset limit, that is, the limit        is dynamic based on system operation and resources.        Unless explicitly resource limited, a system's value for        this object SHOULD be 0.        Changing this value will not eliminate or inhibit existing        sample state but could prevent allocation of additional state        information."    ::= { mteResource 2 }mteResourceSampleInstances OBJECT-TYPE    SYNTAX      Gauge32    UNITS       "instances"    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "The number of currently active instance entries as        defined for mteResourceSampleInstanceMaximum."    ::= { mteResource 3 }mteResourceSampleInstancesHigh OBJECT-TYPE    SYNTAX      Gauge32    UNITS       "instances"    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "The highest value of mteResourceSampleInstances that has        occurred since initialization of the management system."    ::= { mteResource 4 }mteResourceSampleInstanceLacks OBJECT-TYPE    SYNTAX      Counter32    UNITS       "instances"    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "The number of times this system could not take a new sample        because that allocation would have exceeded the limit set by        mteResourceSampleInstanceMaximum."    ::= { mteResource 5 }---- Trigger Section---- CountersmteTriggerFailures OBJECT-TYPE    SYNTAX      Counter32    UNITS       "failures"    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "The number of times an attempt to check for a trigger        condition has failed.  This counts individually for each        attempt in a group of targets or each attempt for a        wildcarded object."    ::= { mteTrigger 1 }---- Trigger Table--mteTriggerTable OBJECT-TYPE    SYNTAX      SEQUENCE OF MteTriggerEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "A table of management event trigger information."    ::= { mteTrigger 2 }mteTriggerEntry OBJECT-TYPE    SYNTAX      MteTriggerEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "Information about a single trigger.  Applications create and        delete entries using mteTriggerEntryStatus."    INDEX       { mteOwner, IMPLIED mteTriggerName }    ::= { mteTriggerTable 1 }MteTriggerEntry ::= SEQUENCE {    mteOwner                            SnmpAdminString,    mteTriggerName                      SnmpAdminString,    mteTriggerComment                   SnmpAdminString,    mteTriggerTest                      BITS,    mteTriggerSampleType                INTEGER,    mteTriggerValueID                   OBJECT IDENTIFIER,    mteTriggerValueIDWildcard           TruthValue,    mteTriggerTargetTag                 SnmpTagValue,    mteTriggerContextName               SnmpAdminString,    mteTriggerContextNameWildcard       TruthValue,    mteTriggerFrequency                 Unsigned32,    mteTriggerObjectsOwner              SnmpAdminString,    mteTriggerObjects                   SnmpAdminString,    mteTriggerEnabled                   TruthValue,    mteTriggerEntryStatus               RowStatus}mteOwner OBJECT-TYPE   SYNTAX      SnmpAdminString (SIZE(0..32))   MAX-ACCESS  not-accessible   STATUS      current   DESCRIPTION        "The owner of this entry. The exact semantics of this        string are subject to the security policy defined by the        security administrator."    ::= { mteTriggerEntry 1 }mteTriggerName OBJECT-TYPE    SYNTAX      SnmpAdminString (SIZE (1..32))    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "A locally-unique, administratively assigned name for the        trigger within the scope of mteOwner."    ::= { mteTriggerEntry 2 }mteTriggerComment OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "A description of the trigger's function and use."    DEFVAL { ''H }    ::= { mteTriggerEntry 3 }mteTriggerTest OBJECT-TYPE    SYNTAX      BITS { existence(0), boolean(1), threshold(2) }    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "The type of trigger test to perform.  For 'boolean' and        'threshold'  tests, the object at mteTriggerValueID MUST        evaluate to an integer, that is, anything that ends up encoded        for transmission (that is, in BER, not ASN.1) as an integer.        For 'existence', the specific test is as selected by        mteTriggerExistenceTest.  When an object appears, vanishes        or changes value, the trigger fires. If the object's        appearance caused the trigger firing, the object MUST        vanish before the trigger can be fired again for it, and        vice versa. If the trigger fired due to a change in the        object's value, it will be fired again on every successive        value change for that object.        For 'boolean', the specific test is as selected by        mteTriggerBooleanTest.  If the test result is true the trigger        fires.  The trigger will not fire again until the value has        become false and come back to true.        For 'threshold' the test works as described below for        mteTriggerThresholdStartup, mteTriggerThresholdRising, and        mteTriggerThresholdFalling.        Note that combining 'boolean' and 'threshold' tests on the        same object may be somewhat redundant."    DEFVAL { { boolean } }    ::= { mteTriggerEntry 4 }mteTriggerSampleType OBJECT-TYPE    SYNTAX      INTEGER { absoluteValue(1), deltaValue(2) }    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "The type of sampling to perform.        An 'absoluteValue' sample requires only a single sample to be        meaningful, and is exactly the value of the object at        mteTriggerValueID at the sample time.        A 'deltaValue' requires two samples to be meaningful and is        thus not available for testing until the second and subsequent        samples after the object at mteTriggerValueID is first found        to exist.  It is the difference between the two samples.  For        unsigned values it is always positive, based on unsigned        arithmetic.  For signed values it can be positive or negative.        For SNMP counters to be meaningful they should be sampled as a        'deltaValue'.        For 'deltaValue' mteTriggerDeltaTable contains further        parameters.        If only 'existence' is set in mteTriggerTest this object has        no meaning."    DEFVAL { absoluteValue }    ::= { mteTriggerEntry 5 }mteTriggerValueID OBJECT-TYPE    SYNTAX      OBJECT IDENTIFIER    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "The object identifier of the MIB object to sample to see        if the trigger should fire.        This may be wildcarded by truncating all or part of the        instance portion, in which case the value is obtained        as if with a GetNext function, checking multiple values        if they exist.  If such wildcarding is applied,        mteTriggerValueIDWildcard must be 'true' and if not it must        be 'false'.        Bad object identifiers or a mismatch between truncating the        identifier and the value of mteTriggerValueIDWildcard result        in operation as one would expect when providing the wrong        identifier to a Get or GetNext operation.  The Get will fail        or get the wrong object.  The GetNext will indeed get whatever        is next, proceeding until it runs past the initial part of the        identifier and perhaps many unintended objects for confusing        results.  If the value syntax of those objects is not usable,        that results in a 'badType' error that terminates the scan.        Each instance that fills the wildcard is independent of any        additional instances, that is, wildcarded objects operate

⌨️ 快捷键说明

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