OID reference

zxDslIpv6TrapHostMinEventLevel

1.3.6.1.4.1.3902.1004.3.1.14.2.1.6

Description

The min event level that a reciever expects.If the actual event level is more serious then this value,the event will be sent to Event Reciever. For example,if this value is warning(4),all the events that the level in cleared(0),critical(1),major(2),minor(3), warning(4) will be sent,but notification(5) will not be sent…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.1004.3.1.14.2.1 (zxDslIpv6TrapHostEntry)
Node code
6
Node name
zxDslIpv6TrapHostMinEventLevel
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.1004.3.1.14.2.1.6
URN notation
urn:oid:1.3.6.1.4.1.3902.1004.3.1.14.2.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3902 1004 3 1 14 2 1 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxDsl(1004) zxDslSysctrlMib(3) zxDslSysctrlObjects(1) zxDslIpv6Objects(14) zxDslIpv6TrapHostTable(2) zxDslIpv6TrapHostEntry(1) zxDslIpv6TrapHostMinEventLevel(6)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/1004/3/1/14/2/1/6
  • /ISO/Identified-Organization/6/1/4/1/3902/1004/3/1/14/2/1/6
  • /ISO/3/6/1/4/1/3902/1004/3/1/14/2/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zxEnterpriseMib/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/vendor-objects/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/vendor-objects/zte/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/identified-organization/dod/internet/private/vendor-objects/zxEnterpriseMib/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/org/dod/internet/private/enterprise/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/org/dod/internet/private/enterprise/zte/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/org/dod/internet/private/enterprise/zxEnterpriseMib/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • /iso/org/dod/internet/private/enterprises/3902/zxDsl/zxDslSysctrlMib/zxDslSysctrlObjects/zxDslIpv6Objects/zxDslIpv6TrapHostTable/zxDslIpv6TrapHostEntry/zxDslIpv6TrapHostMinEventLevel
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
notification

Enumerated values

ValueName
0cleared
1critical
2major
3minor
4warning
5notification

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: zxDslIpv6TrapHostIpAddr.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3902.1004.3.1.14.2.1.6

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

zxDslIpv6TrapHostMinEventLevel  OBJECT-TYPE
        SYNTAX INTEGER {
                     cleared(0),
                     critical(1),
                     major(2),
                     minor(3),
                     warning(4),
                     notification(5)
                    }
        MAX-ACCESS read-create
        STATUS current
        DESCRIPTION
            "The min event level that a reciever expects.If the actual event 
            level is more serious then this value,the event will be sent to 
            Event Reciever. For example,if this value is warning(4),all the 
            events that the level in cleared(0),critical(1),major(2),minor(3),
            warning(4) will be sent,but notification(5) will not be sent.
            
            The event levels are defined in ITU-T X.733.            
            
           -   cleared: The Cleared severity level indicates the clearing of 
            one or more previously reported alarms. This alarm clears all 
            alarms for this managed object that have the same Alarm type,
            Probable cause and Specific problems (if given).  
            Multiple associated notifications may be cleared by using 
            the Correlated notifications parameter (defined below).
            This Recommendation | International Standard does not require that
            the clearing of previously reported alarms be reported.  
            Therefore, a managing system cannot assume that the absence of
            an alarm with the Cleared severity level means that the condition
            that caused the generation of previous alarms is still present.  
               Managed object definers shall state if, and under which 
            conditions, the Cleared severity level is used.
            
           -  critical: The Critical severity level indicates that a service 
             affecting condition has occurred and an immediate corrective action
             is required.  Such a severity can be reported, for example, when 
             a managed object becomes totally out of service and its capability 
             must be restored. 
             
           -   major: The Major severity level indicates that a service 
            affecting condition has developed and an urgent corrective action 
            is required.  Such a severity can be reported, for example, when 
            there is a severe degradation in the capability of the managed 
            object and its full capability must be restored. 
            
           -   minor: The Minor severity level indicates the existence of 
            a non-service affecting fault condition and that corrective action 
            should be taken in order to prevent a more serious (for example, 
            service affecting) fault. Such a severity can be reported, 
            for example, when the detected alarm condition is not currently 
            degrading the capacity of the managed object. 
                        
           -   warning: The Warning severity level indicates the detection of 
            a potential or impending service affecting fault, before any 
            significant effects have been felt. Action should be taken to 
            further diagnose (if necessary) and correct the problem in order 
            to prevent it from becoming a more serious service affecting fault.               

            -  notification: The notification severity level indicates that 
            only a infomation to be report and it is either a fault or 
            a potential fault. 

            "
        DEFVAL { notification }
        ::= { zxDslIpv6TrapHostEntry 6 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The min event level that a reciever expects.If the actual event level is more serious then this value,the event will be sent to Event Reciever. For example,if this value is warning(4),all the events that the level in cleared(0),critical(1),major(2),minor(3), warning(4) will be sent,but notification(5) will not be sent. The event levels are defined in ITU-T X.733. - cleared: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same Alarm type, Probable cause and Specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter (defined below). This Recommendation | International Standard does not require that the clearing of previously reported alarms be reported. Therefore, a managing system cannot assume that the absence of an alarm with the Cleared severity level means that the condition that caused the generation of previous alarms is still present. Managed object definers shall state if, and under which conditions, the Cleared severity level is used. - critical: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported, for example, when a managed object becomes totally out of service and its capability must be restored. - major: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported, for example, when there is a severe degradation in the capability of the managed object and its full capability must be restored. - minor: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported, for example, when the detected alarm condition is not currently degrading the capacity of the managed object. - warning: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault. - notification: The notification severity level indicates that only a infomation to be report and it is either a fault or a potential fault.

Sources for this description

ZTE MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ZTE MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

zxDslIpv6TrapHostMinEventLevel · currentZTE MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: zxDslIpv6TrapHostMinEventLevel

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zxDslIpv6TrapHostMinEventLevel",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "cleared",
    "(",
    "0",
    ")",
    ",",
    "critical",
    "(",
    "1",
    ")",
    ",",
    "major",
    "(",
    "2",
    ")",
    ",",
    "minor",
    "(",
    "3",
    ")",
    ",",
    "warning",
    "(",
    "4",
    ")",
    ",",
    "notification",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The min event level that a reciever expects.If the actual event level is more serious then this value,the event will be sent to Event Reciever. For example,if this value is warning(4),all the events that the level in cleared(0),critical(1),major(2),minor(3), warning(4) will be sent,but notification(5) will not be sent. The event levels are defined in ITU-T X.733. - cleared: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same Alarm type, Probable cause and Specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter (defined below). This Recommendation | International Standard does not require that the clearing of previously reported alarms be reported. Therefore, a managing system cannot assume that the absence of an alarm with the Cleared severity level means that the condition that caused the generation of previous alarms is still present. Managed object definers shall state if, and under which conditions, the Cleared severity level is used. - critical: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported, for example, when a managed object becomes totally out of service and its capability must be restored. - major: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported, for example, when there is a severe degradation in the capability of the managed object and its full capability must be restored. - minor: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported, for example, when the detected alarm condition is not currently degrading the capacity of the managed object. - warning: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault. - notification: The notification severity level indicates that only a infomation to be report and it is either a fault or a potential fault. \"",
    "DEFVAL",
    "{",
    "notification",
    "}",
    "::=",
    "{",
    "zxDslIpv6TrapHostEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "cleared",
            0
          ],
          [
            "critical",
            1
          ],
          [
            "major",
            2
          ],
          [
            "minor",
            3
          ],
          [
            "warning",
            4
          ],
          [
            "notification",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The min event level that a reciever expects.If the actual event level is more serious then this value,the event will be sent to Event Reciever. For example,if this value is warning(4),all the events that the level in cleared(0),critical(1),major(2),minor(3), warning(4) will be sent,but notification(5) will not be sent. The event levels are defined in ITU-T X.733. - cleared: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same Alarm type, Probable cause and Specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter (defined below). This Recommendation | International Standard does not require that the clearing of previously reported alarms be reported. Therefore, a managing system cannot assume that the absence of an alarm with the Cleared severity level means that the condition that caused the generation of previous alarms is still present. Managed object definers shall state if, and under which conditions, the Cleared severity level is used. - critical: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported, for example, when a managed object becomes totally out of service and its capability must be restored. - major: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported, for example, when there is a severe degradation in the capability of the managed object and its full capability must be restored. - minor: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported, for example, when the detected alarm condition is not currently degrading the capacity of the managed object. - warning: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault. - notification: The notification severity level indicates that only a infomation to be report and it is either a fault or a potential fault."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "notification"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3902)

Xianlin Luo

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3902.1004.3.1.14.2.1.1 zxDslIpv6TrapHostIpAddr00
1.3.6.1.4.1.3902.1004.3.1.14.2.1.2 zxDslIpv6TrapHostSnmpVer00
1.3.6.1.4.1.3902.1004.3.1.14.2.1.3 zxDslIpv6TrapHostCommunity00
1.3.6.1.4.1.3902.1004.3.1.14.2.1.4 zxDslIpv6TrapHostIsZteNmsSever00
1.3.6.1.4.1.3902.1004.3.1.14.2.1.5 zxDslIpv6TrapHostEventType00
1.3.6.1.4.1.3902.1004.3.1.14.2.1.30 zxDslIpv6TrapHostRowStatus00