Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual page 238

Configuring and Using Media Flow Controller Logs and Alarms
Table 19 SNMP Alarms, Possible Causes, and Recommended Actions (Continued)
Event Name
(MIB/ stat Name)
Process Crashed
(procmgr)
Process Got Stuck
(procLivenessFailure)
Process Not Running
(procExit)
Unexpected
Shutdown
(unexpectedShutdow
n)
Disk Failure Warning
(smartError)
CPU Utilization High
(cpuUtilHigh)
Disk Space Low
(diskSpaceLow)
Paging High
(pagingActivityHigh)
238 SNMP Alarms
Cause
The Media Flow Controller process can restart if there
is a software problem. A core file is generated. This
event causes high-availability to kick in and requests
may be forwarded to another Media Flow Controller or
POP. The crashed Media Flow Controller process
should restart very quickly after which new
connections/requests are served. If the core Media
Flow Controller server process does not crash,
requests are served in a normal manner. For example,
if the management process restarts, requests are not
affected.
The Media Flow Controller is not serving out any more
requests. This event causes high-availability to kick in
and requests are forwarded to another Media Flow
Controller or POP. This Media Flow Controller may not
be able to recover.
The Media Flow Controller process is not serving out
any more requests. This event causes high-availability
to kick in and requests are forwarded to another Media
Flow Controller or POP. This Media Flow Controller
may not be able to recover.
The server may unexpectedly shutdown due to power
reasons. This is a highly unlikely event. This event
causes high-availability to kick in and requests are
forwarded to another Media Flow Controller or POP.
This Media Flow Controller may not be able to recover.
Hardware Resources Traps
One or more disks are issuing warnings that a disk
sector was corrupted, un-writeable, or unreadable.
Media Flow Controller still serves out requests from
other disks. If the ROOT disk is corrupted, the system
may not be functional and will need to be looked at.
The CPU utilization may be high due to increased
processing of requests, disk I/O, or some error. When
CPU utilization is high, Media Flow Controller
performance may be compromised. This event may be
transitory or permanent.
Disk space low may be reported on the ROOT disk
because logs may be taking too much of disk space.
This may cause the ROOT disk to un-writeable.
Memory utilization may be high on the Media Flow
Controller server. When this happens, Media Flow
Controller performance may be compromised.
Media Flow Controller Administrator's Guide
Escalate to Juniper Networks Support to
look at the core file. However, request
processing may proceed automatically
because the Media Flow Controller
process restarts on its own.
Processing may proceed automatically
because the Media Flow Controller
process restarts on its own; if it does not,
escalate to Juniper Networks Support to
diagnose the issue.
Processing may proceed automatically
because the Media Flow Controller
process restarts on its own; if it does not,
escalate to Juniper Networks Support to
diagnose the issue.
Check all power cables. Restart Media
Flow Controller and all process and
configurations restart normal operation.
Escalate to Juniper Networks Support to
diagnose the issue.
If high CPU utilization is permanent,
escalate to Juniper Networks Support to
look at the problem.
Upload access log, cache log, error logs
to a networked server and delete
unneeded logs from the Juniper Networks
server.
Escalate to Juniper Networks Support to
look at the problem.
Copyright © 2010, Juniper Networks, Inc.
Action