Configuring SNMP, Faults, and Logging (Web Interface)
147
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (Web Interface)
•
Domain name override—Use a hostname or IP address to set the domain name
from which emails are to appear to come (provided that the return address is not
already fully-qualified). This is used in conjunction with the system hostname to form
the full name of the host from which the email appears to come. The rules are as
follows:
a.
If an email domain is specified using this command, it is always used. If the
hostname has any dots in it, everything to the right of the first dot is stripped and
the email domain is appended.
b.
Otherwise, if the hostname has dots in it, it is used as is.
If not set, the currently-active system domain name is used. This can come either from
the resolver configuration, or from state dynamically instantiated by DHCP.
•
Return address—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 does not like fictitious addresses.
2.
Select or de-select these options:
•
Include hostname in return addr—Include (or do not include by un-checking) the
hostname in the return address for email notifications. This only takes effect if the return
address does not contain an at (@) sign.
•
Enable autosupport notifications—Enable or disable (by un-checking) the sending of
email to vendor autosupport when certain failures occur.
•
Enable SMTP authentication—Enable (by checking) or disable SMPT authentication for
fault reporting. If enabled, also enter information to these text boxes:
•
Username—Set a username for SMTP authentication of emails.
•
Password—Set a password for SMTP authentication of emails; if no password is
set, the user is prompted for the password.
Note!
As of Release 2.0.4 the only
authentication method supported is "LOGIN", which sends the password in the
clear (base64); so users should be aware that this involves some security risk.
3.
Click Apply to complete Fault notification configuration, Cancel to revert to existing
configuration.
4.
Click Save at the top of the page to make changes persistent across reboots.
Notify Recipients
View and delete recipients for stats alarms. See
Figure 28
. See also
email class Options
.
1.
View this information on configured notify recipients:
•
Email—Address of configured recipient.
•
Detail—Whether or not this recipient is sent detailed or summarized emails. Each
email potentially has both a detailed and summarized form, where the detailed form
has a superset of the information.
•
Infos—Whether or not this recipient receives Info class emails.
•
Failures—Whether or not this recipient receives Failure class emails.
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...