System information

1-32 AR Series Router Reference Manual
Software Release 2.0.1
C613-03018-00 REV A
The progress of mail messages can be monitored using the mail subsystem’s
debugging option, which is enabled or disabled with the commands:
ENABLE MAIL DEBUG
DISABLE MAIL DEBUG
Configuration Examples
The following procedures illustrate the steps required to configure the mail
subsystem and transmit email messages. It is assumed that IP has already been
enabled and correctly configured on the router.
To configure the mail subsystem:
1. Configure a DNS Server.
Configure the IP address of the DNS server that the mail subsystem will
use to resolve email addresses into IP addresses. Without a DNS server the
mail subsystem will not function.
SET IP NAMESERVER=192.168.5.3
2. Configure the mail host name.
Configure the host name used by the mail subsystem when
communicating with other mail systems. Normally this is the fully
qualified domain name of the router. Without a host name the mail
subsystem will not function.
SET MAIL HOSTNAME=ho1.company.com
3. Check the configuration.
Check that the mail subsystem is correctly configured and enabled.
SHOW MAIL
To send a file via email from the router’s command prompt:
1. Send the file as the body of a mail message.
Text format files (files with
.CFG
,
.SCP
and
.TXT
extensions) can be
transferred from the router to a remote user in the body of an email
message. For example, configuration scripts can be sent to a central host for
management and change control. In this example, the file
boot.cfg
is sent
to the network administrators email address [e-mail]:
MAIL TO=[e-mail] SUBJECT=”Boot script for
ho1.company.com” FILE=boot.cfg
2. Check the progress of the message.
The progress of the message as it is transmitted to the remote mail system
can be monitored using the command:
SHOW MAIL
To transmit messages automatically using the Trigger Facility:
1. Create a script to generate a mail message.
Create a script called
mailcpu.scp
using the router’s built-in editor that
sends a message to the network administrator:
EDIT mailcpu.scp