Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI, Руководство администратора

Страница: 118 / 156

CHAPTER 5 CLI Commands Media Flow Manager Administrator’s Guide
118 email Copyright © 2010, Juniper Networks, Inc.
•
recipient <email_address>
—Add or delete (with
no
) an email address from the
list of addresses to send email notifications of (all enabled) events, and specify:
•
class
—Set event class. Each event type is classified as either
info
or
failure
.
The specified recipient(s) receives the intersection of the set of events specified
by this command, and the set of events specified overall with the
email notify
event <event_name>
command. See “email class," below, for more details.
•
detail
—Specify whether the emails this recipient is sent should be detailed or
summarized. Each email potentially has both a detailed and summarized form,
where the detailed form has a superset of the information. Default is enabled.
•
return-addr
—Set the username or fully-qualified return address from which email
notifications are sent. If the string provided contains an at (@) sign, it is considered fully-
qualified and is used as-is. Otherwise, it is considered just the username, and Media Flow
Controller appends
@<hostname>.<domain>
. The default is
do-not-reply
, but this can
be changed to
admin
or as desired in case something along the line doesn't like fictitious
addresses. Use
no email return-addr
to reset to default.
•
return-host
—Include the hostname in the return address for email notifications. This
only takes effect if the return address does not contain an at (@) sign. Default is include.
Use
no
to exclude hostname.
•
send-test
—Send a test email to all of the configured notification email recipients. This is
useful to make sure the configuration works without having to wait for an event to occur.
email event name
Email
event name
options are:
•
process-crash
—A process in the system has crashed.
•
process-exit
—A process in the system unexpectedly exited.
•
liveness-failure
—A process in the system was detected hung.
•
cpu-util-high
—CPU utilization has risen too high.
•
cpu-util-ok
—CPU utilization has fallen back to normal levels.
•
paging-high
—Paging activity has risen too high.
•
paging-ok
—Paging activity has fallen back to normal levels.
•
disk-space-low
—File system free space has fallen too low.
•
disk-space-ok
—File system free space is back in the normal range.
•
memusage-high
—Memory usage has risen too high.
•
memusage-ok
—Memory usage has fallen back to acceptable levels.
•
netusage-high
—Network utilization has risen too high.
•
netusage-ok
—Network utilization has fallen back to acceptable levels.
•
disk-io-high
—Disk I/O per second has risen too high.
•
disk-io-ok
—Disk I/O per second has fallen back to acceptable levels.
•
unexpected-shutdown
—Unexpected system shutdown.
•
interface-up
—An interface’s link state has changed to UP.*