Step 1: Check Memory Utilization on Chassis Components
Purpose
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, you can use the jnxOperatingBuffer object to monitor memory usage on your router. (See Figure 18.)
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 memory utilization, you can type the object description (jnxOperatingBuffer) or the OID (.1.3.6.1.4.1.2636.3.1.13.1.11).
Action
To check memory utilization using the Juniper enterprise chassis MIB, from a management station that has access to the router, and using a tool such as Snmpwalk, enter the following commands:
user-bsd#snmpwalk[common arguments]hostname community object-id
user@host> show chassis routing-engine
Sample Output
user-nms % snmpwalk -Os -M /volume/~/mibs -m all tp1 public jnxOperatingBuffer
jnxOperatingBuffer.1.1.1.0 = Gauge32: 0
jnxOperatingBuffer.1.1.2.0 = Gauge32: 0
jnxOperatingBuffer.1.1.3.0 = Gauge32: 0
jnxOperatingBuffer.2.1.0.0 = Gauge32: 0
jnxOperatingBuffer.4.1.1.0 = Gauge32: 0
jnxOperatingBuffer.4.1.2.0 = Gauge32: 0
jnxOperatingBuffer.4.1.3.0 = Gauge32: 0
jnxOperatingBuffer.4.1.4.0 = Gauge32: 0
jnxOperatingBuffer.6.1.1.0 = Gauge32: 6
jnxOperatingBuffer.6.1.2.0 = Gauge32: 6
jnxOperatingBuffer.7.1.0.0 = Gauge32: 8
jnxOperatingBuffer.7.2.0.0 = Gauge32: 8
jnxOperatingBuffer.8.1.1.0 = Gauge32: 0
jnxOperatingBuffer.8.2.3.0 = Gauge32: 0
jnxOperatingBuffer.8.2.4.0 = Gauge32: 0
jnxOperatingBuffer.9.1.0.0 = Gauge32: 28
jnxOperatingBuffer.9.1.1.0 = Gauge32: 0
user-nms %snmpwalk -Os -M /volume/~/mibs -m all tp1 public jnxOperatingDescr
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
user@R1> show chassis routing-engine
Routing Engine status:
Temperature 28 degrees C / 82 degrees F
DRAM 256 MB
Memory utilization 28 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 6 percent
Interrupt 0 percent
Idle 94 percent
Model RE-5.0
Serial ID 1000431687
Start time 2003-11-20 11:42:04 PST
Uptime 63 days, 2 hours, 34 minutes, 4 seconds
Load averages: 1 minute 5 minute 15 minute
0.01 0.02 0.01
What It Means
The sample output shows the percentage of utilization for the FPC and Routing Engine. The first object, jnxOperatingBuffer, shows that the Routing Engine (9.1.0.0) has 28 percent memory utilization, the two CFEB processors are using 6 percent, and the FPCs have 8 percent memory utilization.
The second object, jnxOperatingDescr, provides a human readable description of the separate instances in the jnxOperatingBuffer object. For example, 1.1.0.0 represents the midplane, and 7.1.0.0 represents FPC @ 0/*/*.
The output for the show chassis routing-engine command shows similar information to that displayed in the output of the jnxOperatingBuffer object, with 28 percent memory utilization for the Routing Engine.