All MIBs › CISCO-ERM-MIB › cermPolicyRisingThreshold
cermPolicyRisingThreshold
Module: CISCO-ERM-MIB
OID (symbolic): CISCO-ERM-MIB::cermPolicyRisingThreshold
OID (numeric): 1.3.6.1.4.1.9.9.510.1.3.2.1.7
Node type: OBJECT-TYPE
Type: CermThreshold
Access: read-write
Description: This object indicates the rising threshold value set for the threshold configuration entry.
Lets assume that system global threshold value (in percentage) for 'io' memory resource owner is set to 60% as minor rising threshold value, 70% as major rising threshold value and 90% as critical rising threshold value. When the total 'io' memory utilization exceeds the 60% threshold limit, a minor 'up' notification will be sent to relevant resource user(s). When the total 'io' memory utilization exceeds the 70% threshold limit, a major 'up' notification will be sent to relevant resource user(s). When it exceeds the 90% threshold limit, a critical 'up' notification will be sent to relevant resource user(s).
The rising threshold value is mandatory for any threshold configuration entry in the cermConfigPolicyResOwnerThreshTable.
What is cermPolicyRisingThreshold?
This is the rising threshold percentage configured within this policy's threshold entry, and per the MIB's own worked example, a device might configure 60 percent as the minor threshold, 70 percent as major, and 90 percent as critical for the same io memory resource, each tier configured as its own separate policy threshold entry. Because each severity tier requires its own separate rising-threshold entry rather than one entry with three levels, an admin building tiered alerting on one resource has to create multiple policy threshold rows, each with a different severity assignment and rising percentage. Following the example, crossing 60 percent io memory utilization would trigger this policy's minor-tier entry to send an up notification, while a separate policy entry set at 90 percent governs when the critical-tier alert fires.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.510.1.3.2.1.7 snmpwalk -v2c -c public <target> CISCO-ERM-MIB::cermPolicyRisingThreshold
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.510.1.3.2.1.7.1 snmpget -v2c -c public <target> CISCO-ERM-MIB::cermPolicyRisingThreshold.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.510.1.3.2.1.7.1 s <value>
Start monitoring Cisco routers and switches (Embedded Resource Manager) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-ERM-MIB::cermPolicyRisingThreshold OID value, configure state conditions and alerts, and monitor any Cisco routers and switches (Embedded Resource Manager) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB | CISCO-ERM-MIB |
| 1.3.6.1.4.1.9.9.510.1 | ciscoErmMIBObjects | CISCO-ERM-MIB |
| 1.3.6.1.4.1.9.9.510.1.3 | cermConfig | CISCO-ERM-MIB |
| 1.3.6.1.4.1.9.9.510.1.3.2 | cermConfigPolicyResOwnerThreshTable | CISCO-ERM-MIB |
| 1.3.6.1.4.1.9.9.510.1.3.2.1 | cermConfigPolicyResOwnerThreshEntry | CISCO-ERM-MIB |
| 1.3.6.1.4.1.9.9.510.1.3.2.1.7 | cermPolicyRisingThreshold | CISCO-ERM-MIB |