MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 138 (ciscoEntityAlarmMIB). 1 (ciscoEntityAlarmMIBObjects). 1 (ceAlarmDescription). 2 (ceAlarmDescrTable). 1 (ceAlarmDescrEntry). 2 (ceAlarmDescrSeverity)
OID : 1.3.6.1.4.1.9.9.138.1.1.2.1.2
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoEntityAlarmMIB. ciscoEntityAlarmMIBObjects. ceAlarmDescription. ceAlarmDescrTable. ceAlarmDescrEntry. ceAlarmDescrSeverity
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.9.9.138.1.1.2.1.2
Module CISCO-ENTITY-ALARM-MIB (CISCO)
NomceAlarmDescrSeverity
Accesreadwrite
Statuscurrent
DescriptionThis object specifies the severity associated with the alarm type. An implementation may chose to not allow dynamic severity assignment, in which case it would restrict access to this object to be read-only. If an implementation allows dynamic severity assignment, then a management client can revert to the default severity by writing the value '0' to this object. There exists a class of systems that should implement dynamic severity assignment. For example, consider a DSLAM (Digital Subscriber Loop Access Multiplexor) designed for both the central office and pedestal environments. A 'pedestal' is typically a dark-green metal box mounted on a concrete or stone foundation in which carrier-class companies house equipment. The central office typically controls the temperature and humidity of the environment, reducing reliance on a system's fans. Thus, the customer probably has a desire to reduce the severity of alarms indicating the failure of a fan. However, a pedestal environment has a much greater reliance on a system's fans. Thus, the customer probably has a desire to increase the severity of alarms indicating the failure of a fan.
SyntaxeAlarmSeverityOrZero (CISCO-ENTITY-ALARM-MIB)