Snmp Alarms; Snmp; Table 19 Snmp Alarms, Possible Causes, And Recommended Actions - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
3. Limit the email notifications to a particular event class for an existing email notify
recipient, by removing one of the event classes:
no email notify recipient <email_address> class {failure | info}
4. Ensure that process-crash event notifications are sent in detail:
email notify recipient <email_address> detail
5. Remove the detail event notifications option and set notification type back to summarized:
no email notify recipient <email_address> detail

SNMP Alarms

This section describes the SNMP alarms that may reach you through an
Options (configurable).

SNMP

For Release 2.0.4, Media Flow Controller supports the Entity and Asset SNMP MIBs for
discovery, asset management, alarms, and traps; that is HOST-REOURCES, HOST-
RESOURCES-TYPES, IF, IP, IDP, and TCP MIBs. To view these MIBs, go to the Juniper
Networks Support Website.
Typically, SNMP uses UDP (User Datagram Protocol) ports 161 for the agent and 162 for the
manager. The Manager may send requests from any available port (source port) to port 161 in
the agent (destination port). The agent response is given back to the source port. The
Manager receives traps on port 162. The agent may generate traps from any available port.
See Table
Note! At this time, Media Flow Controller does not support provisioning over SNMP V3.
Table 19 SNMP Alarms, Possible Causes, and Recommended Actions
Event Name
(MIB/ stat Name)
Interface UP/Down
(cpu)
19, for information on SNMP traps, possible causes, and recommended actions.
Cause
The network interface on Media Flow Controller went
operationally UP or DOWN. This event could happen
because a wire was unplugged, faulty cable, loose
cabling, or network configuration issue. This event
causes high-availability to kick in and requests may be
forwarded to another Media Flow Controller or POP.
Configuring and Using Media Flow Controller Logs and Alarms
System Traps
email event name
Action
Check the network cables that go into the
NIC card and make sure that all cabling is
OK. Check the network configuration
between the switch/router and server.
Make sure that the interface speeds
match on the switch and router because
this mismatch could cause speed auto-
negotiation problems.
SNMP Alarms 237