EXTREME-SYSTEM-MIB :: extremeCpuAggregateUtilization

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEXTREME-SYSTEM-MIBextremeCpuAggregateUtilization

extremeCpuAggregateUtilization

Module: EXTREME-SYSTEM-MIB

OID (symbolic): EXTREME-SYSTEM-MIB::extremeCpuAggregateUtilization

OID (numeric): 1.3.6.1.4.1.1916.1.1.1.28

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The aggregate CPU utilization since the time the start started executing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1916.1.1.1.28
snmpwalk -v2c -c public <target> EXTREME-SYSTEM-MIB::extremeCpuAggregateUtilization

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1916.1.1.1.28.1
snmpget -v2c -c public <target> EXTREME-SYSTEM-MIB::extremeCpuAggregateUtilization.1

Start monitoring Extreme Networks switch/routing platform (common system objects, base MIB) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EXTREME-SYSTEM-MIB::extremeCpuAggregateUtilization OID value, configure state conditions and alerts, and monitor any Extreme Networks switch/routing platform (common system objects, base MIB) from a single console.

How to Use in IPNetwork Monitor

Select an Extreme Networks switch or wireless controller as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type extremeCpuAggregateUtilization into the Find box to locate it in the OID tree, then select it and click OK. It reports the aggregate CPU utilization since the switch started executing. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if CPU utilization exceeds 85%, a common warning threshold before sustained high load affects switching performance. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1916extremenetworksEXTREME-BASE-MIB
1.3.6.1.4.1.1916.1extremeAgentEXTREME-BASE-MIB
1.3.6.1.4.1.1916.1.1extremeSystemEXTREME-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.1.1.1extremeSystemCommonEXTREME-SYSTEM-MIB
1.3.6.1.4.1.1916.1.1.1.28extremeCpuAggregateUtilizationEXTREME-SYSTEM-MIB