Purpose
You can monitor CPU utilization using the Juniper specific enterprise chassis MIB and the standard system application MIB (RFC 2287, Definitions of System-Level Managed Objects for Applications).
From a management station that has access to the router, and using a tool such as Snmpwalk, follow these steps:
The enterprise-specific chassis MIB provides information about the router and its components. Within the chassis MIB, the jnxMIBs branch contains one main subbranch, jnxBoxAnatomy, which in turn contains a section, jnxOperatingTable. Within jnxOperatingTable, and under the jnxOperatingEntry, you can use the jnxOperatingCPU object to monitor the CPU on your router. (See Figure 20.)
Figure 20: Chassis MIB Tree
After each object description is a value in parenthesis, such as (1). This value can be used to enter an OID for the specific object. For example, to gather information on the CPU, you can type the object description (jnxOperatingCPU) or the OID (.1.3.6.1.4.1.2636.3.1.13.1.8).
To check CPU utilization using the Juniper Networks enterprise chassis MIB, from a management station that has access to the router, and using a tool such as Snmpwalk, enter the following command:
user-nms % snmpwalk -Os -M /volume/~/mibs -m all tp1 public jnxOperatingCPU jnxOperatingCPU.1.1.1.0 = Gauge32: 0 jnxOperatingCPU.1.1.2.0 = Gauge32: 0 jnxOperatingCPU.1.1.3.0 = Gauge32: 0 jnxOperatingCPU.2.1.0.0 = Gauge32: 0 jnxOperatingCPU.4.1.1.0 = Gauge32: 0 jnxOperatingCPU.4.1.2.0 = Gauge32: 0 jnxOperatingCPU.4.1.3.0 = Gauge32: 0 jnxOperatingCPU.4.1.4.0 = Gauge32: 0 jnxOperatingCPU.6.1.1.0 = Gauge32: 224 jnxOperatingCPU.6.1.2.0 = Gauge32: 224 jnxOperatingCPU.7.1.0.0 = Gauge32: 2 jnxOperatingCPU.7.2.0.0 = Gauge32: 2 jnxOperatingCPU.8.1.1.0 = Gauge32: 0 jnxOperatingCPU.8.2.3.0 = Gauge32: 0 jnxOperatingCPU.8.2.4.0 = Gauge32: 0 jnxOperatingCPU.9.1.0.0 = Gauge32: 6 jnxOperatingCPU.9.1.1.0 = Gauge32: 0 user-nms % snmpwalk -Os -M /volume/~/mibs -m all tp1 public jnxOperatingDesc jnxOperatingDescr.1.1.1.0 = midplane jnxOperatingDescr.1.1.2.0 = midplane jnxOperatingDescr.1.1.3.0 = midplane jnxOperatingDescr.2.1.0.0 = Power Supply A jnxOperatingDescr.4.1.1.0 = Left Tray front fan jnxOperatingDescr.4.1.2.0 = Left Tray second fan jnxOperatingDescr.4.1.3.0 = Left Tray third fan jnxOperatingDescr.4.1.4.0 = Left Tray fourth fan jnxOperatingDescr.6.1.1.0 = CFEB Internet Processor IIv1 jnxOperatingDescr.6.1.2.0 = CFEB Internet Processor IIv1 jnxOperatingDescr.7.1.0.0 = FPC @ 0/*/* jnxOperatingDescr.7.2.0.0 = FPC @ 1/*/* jnxOperatingDescr.8.1.1.0 = PIC: 4x OC-3 SONET, MM @ 0/0/* jnxOperatingDescr.8.2.3.0 = PIC: 1x Tunnel @ 1/2/* jnxOperatingDescr.8.2.4.0 = PIC: 1x G/E, 1000 BASE-SX @ 1/3/* jnxOperatingDescr.9.1.0.0 = Routing Engine jnxOperatingDescr.9.1.1.0 = Routing Engine PCMCIA Card
The sample output shows the percentage CPU utilization on router, tp1. The Routing Engine (9.1.0.0) has 6 percent CPU utilization, the two CFEB Internet Processors IIv1 (6.1.1.0 and 6.1.2.0) have 22 percent each, and the FPCs (7.1.0.0 and 7.2.0.0) have 2 percent each. Components with a value of zero indicate that the information is either unavailable or inapplicable.
The output for the jnxOperatingDesc object provides a description of the separate instances in the jnxOperatingCPU object. For example, 9.1.0.0 represents the Routing Engine.
The standard system application MIB (RFC 2287, Definitions of System-Level Managed Objects for Applications), describes a set of managed objects that are restricted to information that can be determined from the system itself. The object sysApplElmtRunCPU provides information about applications and associated elements that have run or are currently running on the host system. (See Figure 21.)
Figure 21: System Application MIB Tree
To check CPU utilization per process, from a management station that has access to the router, and using a tool such as Snmpwalk, enter the following command:
use-nms % snmpwalk -Os -M /volume/~/mibs -m all tp1 public sysApplElmtRunCPU sysApplElmtRunCPU.0.0.0 = Timeticks: (278) 0:00:02.78 sysApplElmtRunCPU.0.0.2 = Timeticks: (487) 0:00:04.87 sysApplElmtRunCPU.0.0.3 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.4 = Timeticks: (1742) 0:00:17.42 sysApplElmtRunCPU.0.0.5 = Timeticks: (13899) 0:02:18.99 sysApplElmtRunCPU.0.0.6 = Timeticks: (79) 0:00:00.79 sysApplElmtRunCPU.0.0.7 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.8 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.9 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.10 = Timeticks: (2229) 0:00:22.29 sysApplElmtRunCPU.0.0.11 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.12 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.116 = Timeticks: (25) 0:00:00.25 sysApplElmtRunCPU.0.0.2023 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.2131 = Timeticks: (1103) 0:00:11.03 sysApplElmtRunCPU.0.0.2160 = Timeticks: (1599) 0:00:15.99 sysApplElmtRunCPU.0.0.2161 = Timeticks: (4) 0:00:00.04 sysApplElmtRunCPU.0.0.2174 = Timeticks: (1168) 0:00:11.68 sysApplElmtRunCPU.0.0.2324 = Timeticks: (1738) 0:00:17.38 sysApplElmtRunCPU.0.0.16781 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.18311 = Timeticks: (0) 0:00:00.00 sysApplElmtRunCPU.0.0.26827 = Timeticks: (2) 0:00:00.02 sysApplElmtRunCPU.3.1.1 = Timeticks: (483) 0:00:04.83 sysApplElmtRunCPU.3.2.2163 = Timeticks: (33548776) 3 days, 21:11:27.76 sysApplElmtRunCPU.3.3.2185 = Timeticks: (1314) 0:00:13.14 sysApplElmtRunCPU.3.4.2194 = Timeticks: (5282) 0:00:52.82 sysApplElmtRunCPU.3.7.2168 = Timeticks: (20380) 0:03:23.80 sysApplElmtRunCPU.3.9.2169 = Timeticks: (6703) 0:01:07.03 sysApplElmtRunCPU.3.12.2172 = Timeticks: (337) 0:00:03.37 sysApplElmtRunCPU.3.13.2173 = Timeticks: (36) 0:00:00.36 sysApplElmtRunCPU.3.14.2164 = Timeticks: (39783) 0:06:37.83 sysApplElmtRunCPU.3.15.2175 = Timeticks: (4206) 0:00:42.06 sysApplElmtRunCPU.3.16.2165 = Timeticks: (18) 0:00:00.18 sysApplElmtRunCPU.3.17.2176 = Timeticks: (61) 0:00:00.61 sysApplElmtRunCPU.3.19.2177 = Timeticks: (25) 0:00:00.25 sysApplElmtRunCPU.3.20.2178 = Timeticks: (200) 0:00:02.00 sysApplElmtRunCPU.3.21.2179 = Timeticks: (38) 0:00:00.38 sysApplElmtRunCPU.3.23.2188 = Timeticks: (3175) 0:00:31.75 sysApplElmtRunCPU.3.25.2186 = Timeticks: (44774) 0:07:27.74 sysApplElmtRunCPU.3.26.2180 = Timeticks: (17) 0:00:00.17 sysApplElmtRunCPU.3.27.2181 = Timeticks: (48950) 0:08:09.50 sysApplElmtRunCPU.3.30.2187 = Timeticks: (11) 0:00:00.11 sysApplElmtRunCPU.3.31.2184 = Timeticks: (93) 0:00:00.93 sysApplElmtRunCPU.3.34.2171 = Timeticks: (80) 0:00:00.80 sysApplElmtRunCPU.3.35.2047 = Timeticks: (1585) 0:00:15.85 sysApplElmtRunCPU.3.36.2189 = Timeticks: (30) 0:00:00.30 sysApplElmtRunCPU.3.37.2191 = Timeticks: (326) 0:00:03.26 sysApplElmtRunCPU.5.5.7495 = Timeticks: (24721) 0:04:07.21 sysApplElmtRunCPU.5.6.2167 = Timeticks: (936) 0:00:09.36 sysApplElmtRunCPU.5.6.26829 = Timeticks: (1) 0:00:00.01 sysApplElmtRunCPU.5.8.26828 = Timeticks: (25) 0:00:00.25 sysApplElmtRunCPU.5.28.2182 = Timeticks: (29234) 0:04:52.34 sysApplElmtRunCPU.5.29.2183 = Timeticks: (21) 0:00:00.21 user-nms % snmpwalk -Os -M /~/mibs -m all tp1 public sysApplElmtRunName sysApplElmtRunName.0.0.0 = (swapper) sysApplElmtRunName.0.0.2 = (pagedaemon) sysApplElmtRunName.0.0.3 = (vmdaemon) sysApplElmtRunName.0.0.4 = (bufdaemon) sysApplElmtRunName.0.0.5 = (syncer) sysApplElmtRunName.0.0.6 = (netdaemon) sysApplElmtRunName.0.0.7 = (if_pfe) sysApplElmtRunName.0.0.8 = (if_pfe_listen) sysApplElmtRunName.0.0.9 = (cb_poll) sysApplElmtRunName.0.0.10 = (vmuncachedaemon) sysApplElmtRunName.0.0.11 = (scs_housekeeping) sysApplElmtRunName.0.0.12 = (if_pic_listen) sysApplElmtRunName.0.0.116 = mfs sysApplElmtRunName.0.0.2023 = pccardd sysApplElmtRunName.0.0.2131 = cron sysApplElmtRunName.0.0.2160 = /sbin/watchdog sysApplElmtRunName.0.0.2161 = /usr/sbin/tnetd sysApplElmtRunName.0.0.2174 = /usr/sbin/tnp.sntpd sysApplElmtRunName.0.0.2324 = (peer proxy) sysApplElmtRunName.0.0.16781 = /usr/libexec/getty sysApplElmtRunName.0.0.18311 = /usr/sbin/xntpd sysApplElmtRunName.0.0.26827 = telnetd sysApplElmtRunName.3.1.1 = /sbin/preinit sysApplElmtRunName.3.2.2163 = /usr/sbin/chassisd sysApplElmtRunName.3.3.2185 = /usr/sbin/dfwd sysApplElmtRunName.3.4.2194 = /sbin/dcd sysApplElmtRunName.3.7.2168 = /usr/sbin/snmpd sysApplElmtRunName.3.9.2169 = /usr/sbin/mib2d sysApplElmtRunName.3.12.2172 = /usr/sbin/apsd sysApplElmtRunName.3.13.2173 = /usr/sbin/vrrpd sysApplElmtRunName.3.14.2164 = /usr/sbin/alarmd sysApplElmtRunName.3.15.2175 = /usr/sbin/pfed sysApplElmtRunName.3.16.2165 = /usr/sbin/craftd sysApplElmtRunName.3.17.2176 = /usr/sbin/sampled sysApplElmtRunName.3.19.2177 = /usr/sbin/ilmid sysApplElmtRunName.3.20.2178 = /usr/sbin/rmopd sysApplElmtRunName.3.21.2179 = /usr/sbin/cosd sysApplElmtRunName.3.23.2188 = /usr/sbin/fsad sysApplElmtRunName.3.25.2186 = /usr/sbin/irsd sysApplElmtRunName.3.26.2180 = /usr/sbin/nasd sysApplElmtRunName.3.27.2181 = /usr/sbin/fud sysApplElmtRunName.3.30.2187 = /usr/sbin/rtspd sysApplElmtRunName.3.31.2184 = /usr/sbin/smartd sysApplElmtRunName.3.34.2171 = /usr/sbin/inetd sysApplElmtRunName.3.35.2047 = syslogd sysApplElmtRunName.3.36.2189 = /usr/sbin/spd sysApplElmtRunName.3.37.2191 = /usr/sbin/eccd sysApplElmtRunName.5.5.7495 = /usr/sbin/rpd sysApplElmtRunName.5.6.2167 = /usr/sbin/mgd sysApplElmtRunName.5.6.26829 = mgd: (mgd) (user)/dev/ttyp0 sysApplElmtRunName.5.8.26828 = -cli sysApplElmtRunName.5.28.2182 = /usr/sbin/ppmd sysApplElmtRunName.5.29.2183 = /usr/sbin/lmpd
The sample output shows the number of centi-seconds of total system CPU resources consumed by a particular process. For example, the chassis process (chassisd, 3.2.2163) has consumed 3 days, or 33,548,776 centi-seconds of total system CPU resources.
The sysApplElmtRunName object retrieves the name of the OID. For example, sysApplElmtRunCPU.3.2.2163 represents the chassis process.