Monitoring The Sfm Status; Display The Sfm Summary Status - Juniper JUNOS - NETWORK OPERATION GUIDE REV1 Network Operation Manual

The SFMs are hot-removable and hot-insertable. Inserting or removing an SFM
causes a brief interruption in forwarding performance (about 500 ms) as the Packet
Forwarding Engine reconfigures the distribution of packets across the remaining
SFMs.

Monitoring the SFM Status

To monitor the SFM status, follow these steps:
1. Display the SFM Summary Status on page 349
Steps To Take
2. Display the SFM LED Status at the Command Line on page 351
3. Check the SFM LED Status on the Faceplate on page 351
4. Display the SFM Environmental Status on page 351
Step 1: Display the SFM Summary Status
To display the SFM summary status, use the following JUNOS software
Action
command-line interface (CLI) command:
Sample Output
user@host> show chassis sfm
Temp
Slot State
The command output displays the SFM slot number: 0 , 1 , 2 , or 3 . The output also
What it Means
displays the operating status of each SFM as Online , Offline , or Empty .
In the sample output, the root cause of the SFM1 failure may be an FPC problem.
The command output displays the temperature of air passing by the SFM, in
degrees Centigrade. It displays the SFM CPU usage, including the total percentage
used by the SFM processor and the percentage used for interrupts.
The command output also displays the percentage of memory usage, including the
total DRAM available to the SFM processor, in megabytes (MB), and the percentage
of heap space (dynamic memory) being used by the SFM processor. Heap utilization
greater than 80 percent can indicate a software problem (memory leak). The output
shows the percentage of buffer space being used by the SFM processor for buffering
internal messages.
user@host> show chassis sfm
CPU Utilization (%)
(C)
0 Online 41
1 Offline --- Hard FPC error ---
2 Online 43
3 Online 44
Memory Utilization (%)
Total Interrupt DRAM (MB) Heap
2 0 64
2 0 64
2 0 128
Chapter 26: Monitoring the SFMs
Buffer
16 46
16 46
7 46
!
Monitoring the SFM Status
349