Page tree

Contents

Use the set thresholdtrap command to enable the SNMP trap for CPU usage and to configure the trigger and reset values of the trap. The CPU usage trap is disabled by default. When you use this command to change the trigger and reset values, you enable the trap and the appliance sends and resets traps based on the configured values. When CPU usage of an appliance exceeds the trigger threshold for 15 seconds, the appliance sends a "CPU usage above threshold value" trap. After the appliance sends the "CPU usage above threshold value" trap, it sends a "CPU usage OK" trap when the CPU usage dips below the reset threshold.
Use the show thresholdtrap command to view the current settings of the CPU usage trap. Note that the CPU usage trap is disabled by default, and the trigger value is set at 100 and reset value at 0. For information about Infoblox SNMP traps, refer to the Infoblox NIOS Administrator Guide.

Syntax

set thresholdtrap {type} trigger {value} reset {value}

Argument Description
typeThe type of threshold trap. Enter CpuUsage to enable the CPU usage trap and set the trigger and reset values.
Valid values are: NetworkCapacity, DBObjects, Disk, Memory, Rootfs, CpuUsage, Reporting, ReportingVolume, FDUsage
value (for trigger)

The trigger value of the SNMP trap. When CPU usage exceeds this value, the appliance sends a "CPU usage above threshold value" trap.

value (for reset) The reset value of the SNMP trap. When CPU usage dips below this value, the appliance sends a "CPU usage OK" trap. Ensure that the reset value is smaller than the trigger value.

Example

Enabling the CPU usage trap and set the trigger and reset values

Infoblox > set thresholdtrap CpuUsage trigger 80 reset 71
Infoblox >

When CPU usage exceeds 80% of capacity for 15 seconds, the appliance sends the “CPU usage above threshold value” trap. The appliance sends the “CPU usage OK” trap when CPU usage dips below the reset value of 71.
Following is a sample SNMP output of this example:

2011-09-30 04:32:20 ib-10-35-107-9.infoblox.com [UDP: [10.35.107.9]:44183->[10.35.107.9]]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (50991) 0:08:29.91
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.7779.3.1.1.1.1.3.0
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.1.0 = STRING: "10.35.107.9"
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.3.0 = STRING: "cpu_usage"
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.6.0 = INTEGER: 100
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.7.0 = INTEGER: 80
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.8.0 = INTEGER: 71
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.11.0 = STRING: "CPU usage above threshold value."

2011-09-30 04:33:12 ib-10-35-107-9.infoblox.com [UDP: [10.35.107.9]:44183->[10.35.107.9]]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (56202) 0:09:22.02
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.7779.3.1.1.1.1.3.0
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.1.0 = STRING: "10.35.107.9"
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.3.0 = STRING: "cpu_usage"
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.6.0 = INTEGER: 5

SNMPv2-SMI::enterprises.7779.3.1.1.1.2.7.0 = INTEGER: 80
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.8.0 = INTEGER: 71
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.11.0 = STRING: "CPU usage OK."

This page has no comments.