Reference record for OID 1.3.6.1.2.1.69.1.5.7.1.2

parent

1.3.6.1.2.1.69.1.5.7.1 (docsDevEvControlEntry)

node code

2

node name

docsDevEvReporting

dot oid

1.3.6.1.2.1.69.1.5.7.1.2

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevEvent(5) docsDevEvControlTable(7) docsDevEvControlEntry(1) docsDevEvReporting(2)}

iri oid

/iso/identified-organization/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

/iso/identified-organization/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

/iso/org/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

/iso/org/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

/iso/iso-identified-organization/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

/iso/iso-identified-organization/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevEvent/docsDevEvControlTable/docsDevEvControlEntry/docsDevEvReporting

iri by oid_info

/ISO/Identified-Organization/6/1/2/1/69/1/5/7/1/2

Description by circitor

Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily support
all options for all event classes, but at minimum must
allow traps and syslogging to be disabled. If the
local(0) bit is set, then log to the internal log, if the
traps(1) bit is set, then generate a trap, if the
syslog(2) bit is set, then send a syslog message
(assuming the syslog address is set).

Parsed from file DOCS-CABLE-DEVICE-MIB.mib
Module: DOCS-CABLE-DEVICE-MIB

Description by cisco_v1

Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily
support all options for all event classes but at
minimum must allow traps and syslogging to be
disabled.

If the local(0) bit is set, then log to the internal
log and update non-volatile store, for backward
compatibility with the original RFC 2669 definition.
If the traps(1) bit is set, then generate
an SNMP trap; if the syslog(2) bit is set, then
send a syslog message (assuming that the syslog address
is set). If the localVolatile(8) bit is set, then
log to the internal log without updating non-volatile
store. If the stdInterface(9) bit is set, then the
agent ignores all other bits except the local(0),
syslog(2), and localVolatile(8) bits. Setting the
stdInterface(9) bit indicates that RFC3413 and
RFC3014 are being used to control event reporting
mechanisms.

Description by oid_info

docsDevEvReporting OBJECT-TYPE
SYNTAX BITS {
local(0),
traps(1),
syslog(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily support
all options for all event classes, but at minimum must
allow traps and syslogging to be disabled. If the
local(0) bit is set, then log to the internal log, if the
traps(1) bit is set, then generate a trap, if the
syslog(2) bit is set, then send a syslog message
(assuming the syslog address is set)."
View at oid-info.com

Description by mibdepot

Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily
support all options for all event classes but at
minimum must allow traps and syslogging to be
disabled.

If the local(0) bit is set, then log to the internal
log and update non-volatile store, for backward
compatibility with the original RFC 2669 definition.
If the traps(1) bit is set, then generate
an SNMP trap; if the syslog(2) bit is set, then
send a syslog message (assuming that the syslog address
is set). If the localVolatile(8) bit is set, then
log to the internal log without updating non-volatile
store. If the stdInterface(9) bit is set, then the
agent ignores all other bits except the local(0),
syslog(2), and localVolatile(8) bits. Setting the
stdInterface(9) bit indicates that RFC3413 and
RFC3014 are being used to control event reporting
mechanisms.

Parsed from file rfc4639-DOCSIS-Cable-Device.mib.txt
Company: None
Module: DOCS-CABLE-DEVICE-MIB

Description by cisco

Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily
support all options for all event classes but at
minimum must allow traps and syslogging to be
disabled.

If the local(0) bit is set, then log to the internal
log and update non-volatile store, for backward
compatibility with the original RFC 2669 definition.
If the traps(1) bit is set, then generate
an SNMP trap; if the syslog(2) bit is set, then
send a syslog message (assuming that the syslog address
is set). If the localVolatile(8) bit is set, then
log to the internal log without updating non-volatile
store. If the stdInterface(9) bit is set, then the
agent ignores all other bits except the local(0),
syslog(2), and localVolatile(8) bits. Setting the
stdInterface(9) bit indicates that RFC3413 and
RFC3014 are being used to control event reporting
mechanisms.

Information by circitor

docsDevEvReporting OBJECT-TYPE
        SYNTAX BITS {
            local(0),
            traps(1),
            syslog(2)
        }
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
            "Defines the action to be taken on occurrence of this
             event class. Implementations may not necessarily support
             all options for all event classes, but at minimum must
             allow traps and syslogging to be disabled. If the
             local(0) bit is set, then log to the internal log, if the
             traps(1) bit is set, then generate a trap, if the
             syslog(2) bit is set, then send a syslog message
             (assuming the syslog address is set)."
        ::= { docsDevEvControlEntry 2 }

Information by cisco_v1

docsDevEvReporting OBJECT-TYPE
    SYNTAX OCTET STRING(SIZE(1..2))
        
        
        
        
        
        
        
        
        
        
        
    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "Defines the action to be taken on occurrence of this
        event class.  Implementations may not necessarily
        support all options for all event classes but at
        minimum must allow traps and syslogging to be
        disabled.
        
        If the local(0) bit is set, then log to the internal
        log and update non-volatile store, for backward
        compatibility with the original RFC 2669 definition.
        If the traps(1) bit is set, then generate
        an SNMP trap; if the syslog(2) bit is set, then
        send a syslog message (assuming that the syslog address
        is set).  If the localVolatile(8) bit is set, then
        log to the internal log without updating non-volatile
        store.  If the stdInterface(9) bit is set, then the
        agent ignores all other bits except the local(0),
        syslog(2), and localVolatile(8) bits.  Setting the
        stdInterface(9) bit indicates that RFC3413 and
        RFC3014 are being used to control event reporting
        mechanisms."
    ::= { docsDevEvControlEntry 2 }

Information by oid_info

Automatically extracted from RFC2669

Information by mibdepot

docsDevEvReporting OBJECT-TYPE
           SYNTAX BITS {
               local(0),
               traps(1),
               syslog(2),
               
               
               
               
               localVolatile(8),
               stdInterface(9)
           }
           MAX-ACCESS  read-write
           STATUS      current
           DESCRIPTION
               "Defines the action to be taken on occurrence of this
                event class.  Implementations may not necessarily
                support all options for all event classes but at
                minimum must allow traps and syslogging to be
                disabled.

                If the local(0) bit is set, then log to the internal
                log and update non-volatile store, for backward
                compatibility with the original RFC 2669 definition.
                If the traps(1) bit is set, then generate
                an SNMP trap; if the syslog(2) bit is set, then
                send a syslog message (assuming that the syslog address
                is set).  If the localVolatile(8) bit is set, then
                log to the internal log without updating non-volatile
                store.  If the stdInterface(9) bit is set, then the
                agent ignores all other bits except the local(0),
                syslog(2), and localVolatile(8) bits.  Setting the
                stdInterface(9) bit indicates that RFC3413 and
                RFC3014 are being used to control event reporting
                mechanisms."
           ::= { docsDevEvControlEntry 2 }

Information by cisco

docsDevEvReporting OBJECT-TYPE
    SYNTAX          BITS {
                        local(0),
                        traps(1),
                        syslog(2),
                        ignore3(3), 
                                    
                                    
                                    
                                    
                                    
                        ignore4(4),
                        ignore5(5),
                        ignore6(6),
                        ignore7(7),
                        localVolatile(8),
                        stdInterface(9)
                    }
    MAX-ACCESS      read-write
    STATUS          current
    DESCRIPTION
        "Defines the action to be taken on occurrence of this
        event class.  Implementations may not necessarily
        support all options for all event classes but at
        minimum must allow traps and syslogging to be
        disabled.

        If the local(0) bit is set, then log to the internal
        log and update non-volatile store, for backward
        compatibility with the original RFC 2669 definition.
        If the traps(1) bit is set, then generate
        an SNMP trap; if the syslog(2) bit is set, then
        send a syslog message (assuming that the syslog address
        is set).  If the localVolatile(8) bit is set, then
        log to the internal log without updating non-volatile
        store.  If the stdInterface(9) bit is set, then the
        agent ignores all other bits except the local(0),
        syslog(2), and localVolatile(8) bits.  Setting the
        stdInterface(9) bit indicates that RFC3413 and
        RFC3014 are being used to control event reporting
        mechanisms." 
    ::= { docsDevEvControlEntry 2 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6.1.2)

Internet Assigned Numbers Authority

Brothers (1)