zxDslIpv6TrapHostMinEventLevel

ZTE-DSL-SYSCTRL-MIB · .1.3.6.1.4.1.3902.1004.3.1.14.2.1.6

Object

column r/w Enumeration
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.

Context

MIB
ZTE-DSL-SYSCTRL-MIB
OID
.1.3.6.1.4.1.3902.1004.3.1.14.2.1.6
Type
column
Access
readwrite
Status
current
Parent
zxDslIpv6TrapHostEntry
Table
zxDslIpv6TrapHostTable
Siblings
6

Syntax

Enumeration

Values & Constraints

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

Related Objects

Sibling Objects