Media Flow Controller Configuration Tasks : Basic (System) Configurations : Email Notification Options

Email Notification Options
The email commands allow you to set email addresses for notifications for specified, pre-defined, events. You can also enable autosupport emails: when certain failures occur Juniper Networks support automatically receives an email. Additionally, you can specify return address and host for emails, set the mailhub and mailhub port, and sent a test email. See email for CLI details. Email class options are as follows:
failure events: process-crash, unexpected-shutdown.
info events: liveness-failure, process-exit, cpu-util-ok, cpu-util-high, disk-space-ok, disk-space-low. Note, these disk events are not cache related.
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.
smart-warning—Not supported in Release 2.0.2.
unexpected-shutdown—Unexpected system shutdown.
interface-up—An interface’s link state has changed to UP.*
interface-down—An interface’s link state has changed to DOWN.*
cpu-util-ave-high—Average CPU utilization has risen too high.
cpu-util-ave-ok—Average CPU utilization has fallen back to normal levels.
* Can be added to info events class (see below) with email notify event <event_name>.
Configuring Email (Fault) Notifications
1.
Configure who should receive email event notifications. The class option lets you simply choose a class of events for the specified recipients. The event option lets you add specified events to the info event class. The detail option only applies to process crash events; by default it is enabled.
email notify recipient <email_address> [class {[failure] [info]}] [detail]
email notify event <event_name>
2.
Set domain (default is configured ip domain-list), mailhub (SMTP server), mailhub-port, return address, and include or exclude (with no) the return host in email notifications (default is include). Note! The mailhub option must be sent for notifications to work.
email domain {<hostname> | <IP_address>}
email mailhub {<hostname> | <IP_address>}
email malhub-port <port_number>
email return-addr <username>
email return-host
3.
Disable or enable event emails sent to Juniper Networks for certain pre-configured events; default is enabled. Use no email autosupport enable to disable.
email autosupport enable
4.
Manage undeliverable emails. Use cleanup max-age to set when to permanently delete.
dead-letter enable [cleanup max-age <duration>]
5.
email send-test
6.
show email
Example:
test-vos (config) # email notify recipient bobo@example.com
test-vos (config) # email notify event disk-io-high
test-vos (config) # email domain example.com
test-vos (config) # email mailhub mailgate1.example.com
test-vos (config) # email mailhub-port 22
test-vos (config) # email return-addr support@example.com
test-vos (config) # email return-host
test-vos (config) # email autosupport enable
test-vos (config) # email dead-letter enable
test-vos (config) # show email
Mail hub: mailgate1.example.com
Mail hub port: 22
Domain: example.com
Return address: support@example.com
Include hostname in return address: yes
Dead Letter settings:
Save dead.letter files: yes
Dead letter max-age: (none)
Failure events for which emails will be sent:
process-crash: A process in the system has crashed
smart-warning: Smartd warnings
unexpected-shutdown: Unexpected system shutdown
Informational events for which emails will be sent:
liveness-failure: A process in the system was detected as hung
process-exit: A process in the system unexpectedly exited
cpu-util-ok: CPU utilization has fallen back to normal levels
cpu-util-high: CPU utilization has risen too high
disk-io-ok: Disk I/O per second has fallen back to acceptable levels
disk-io-high: Disk I/O per second has risen too high
disk-space-ok: Filesystem free space is back in the normal range
disk-space-low: Filesystem free space has fallen too low
netusage-ok: Network utilization has fallen back to acceptable levels
netusage-high: Network utilization has risen too high
memusage-ok: Memory usage has fallen back to acceptable levels
memusage-high: Memory usage has risen too high
cpu-util-ave-ok: Average CPU utilization has fallen back to normal levels
cpu-util-ave-high: Average CPU utilization has risen too high
paging-ok: Paging activity has fallen back to normal levels
paging-high: Paging activity has risen too high
Email notification recipients:
bobo@example.com (all events, in detail)
Autosupport emails
Enabled: yes
Recipient:
support@example.com
Mail hub:
mail.example.com
Events to send:
process-crash: A process in the system has crashed
liveness-failure: A process in the system was detected as hung
smart-warning: Smartd warnings
test-vos (config) #
To make these configurations using the Management Console, go to the System Config tab. Use the Faults page for email notifications; see System Config > Faults for details.

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.