email
Sets a schedule and target list for automatic mailings of reports.
email { ( <report>
[ <object> ]
[ customer <name> | all ]
[ prefix <prefix> ] )
| ( trend <filename>
[ application <app-name> ] ) }
[ to <list> ]
schedule <minute> [ <hour> [ <date> [ <month> [ <day> ]]]]
no email [ <report> [ <object> ]]
- report--name of report to be e-mailed; can be one of the following (some reports, as indicated in the list, require a router name; the trend report requires a filename):
- application-delay
- application-delay-blackouts
- application-delay-poor
- application-delay-very-poor
- application-performance
- application-performance-blackouts
- application-traffic
- asn-traffic
- billing
- diagnostics
- diagnostics-brief
- distribution-all <router>
- distribution-all-weighted <router>
- distribution-named <router>
- distribution-named-weighted <router>
- distribution-sufficient <router>
- distribution-sufficient-weighted <router>
- executive-summary
- executive-summary-bgp
- executive-summary-bgp-weighted
- executive-summary-weighted
- measurements
- measurements-blackouts
- network-traffic
- network-traffic-summary
- observed
- observed-blackouts
- observed-poor
- observed-very-poor
- optimized <router>
- optimized-blackouts <router>
- outage-application-summary
- outage-link-summary
- outage-network-summary
- outage-prefix-summary
- prefix-load
- prefix-load-summary
- trend <filename>
- object--one of the following:
- name or IP address of router
- .qry or .tmp file for trend reports
- name--name of the customer for which the report is generated. The customer-specific prefix list will be used when generating such a report. If you use ‘all’ for the name, then reports for all defined customers will be sent.
- prefix--prefix in CIDR format (a.b.c.d /n); generates a report specific to this prefix
- list--list of recipient user IDs supported by the SMTP server (enclose in quotes if the list includes spaces)
- filename--name of .qry or .tmpl file that defines the trend to be published
- app-name--name of an application (e.g., http, icmp, ftp, sap, etc.). One way to see what applications have been found by CNA is to use the command show efc application.
- minute--number of minutes after the hour when the report is to be mailed; range: 0 through 59 (or * for every minute, or a comma-separated list of minutes, such as 5,25,45)
- hour--hour of the day when the report is to be mailed; range: 0 through 23, or * for every hour (or * for every hour, or a comma-separated list of hours, such as 10,22)
- date--day of the month when the report is to be mailed; range: 1 through 31, or * for every day of the month (or * for each date of the month, or a comma-separated list of dates, such as 1,15)
- month--month report is to be mailed; range: 1 through 12 (or * for every month, or a comma-separated list of months, such as 1,7)
- day--day of week when the report is to be mailed; range 0 through 7 (or * for every day of the week, or a comma-separated list of days, such as 0,3); 0 and 7 both mean Sunday
Must be in configuration mode (config), which requires privileged-level access, to set a schedule. One-time mailing of a report can be done with log-in level access.
Available for use multiple times in the configuration.
* for all schedule increments (except minute)
Use the email command to schedule automatic mailings of reports. You can set one schedule for each report; enter the command once for each.
You can also use this command directly from the command line (exec mode) to email reports immediately without needing to schedule it. In this case, you cannot use the schedule keyword.
Reports will be sent by the management module via the mail server defined by the smtp-server command. You should verify that the CNA management module’s eth0 interface has access to the mail server (SMTP servers typically listen on tcp port 25).
Use the no form of the command with no parameters to cancel all automatic e-mailing.
Use the no form of the command with a report name (and object type if required) to cancel a specific report schedule.
