Purpose	The SMTP mail queue holds email messages until they are successfully delivered. Use the clear smtp queue command to delete all such queued messages.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	clear smtp queue
Default	None
Guidelines	Messages are only in the mail queue for a very short time before the first attempt to deliver them. If you can see a message with show smtp queue, the message has not yet been successfully delivered. Use this command to delete all messages from the queue. After deleting the messages, this shows information about each message: the To and From fields, the size, and the age (time in the mail queue). Alternatively, you can retry all queued messages with smtp retry. Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP.
Sample	bstnA# clear smtp queue   To: juser@wwmed.com From:admin@wwmed.com Size:393.00 Age:5h has been deleted. To: juser@wwmed.com From:admin@wwmed.com Size:393.00 Age:5h has been deleted. To: juser@wwmed.com From:admin@wwmed.com Size:393.00 Age:19m has been deleted. To: juser@wwmed.com From:admin@wwmed.com Size:393.00 Age:18m has been deleted.   bstnA# clears four pending email messages.
Related Commands	smtp show smtp queue smtp retry show smtp status

Purpose	Use the optional description command to set a descriptive string for the current email-event role. An email event role is a configurable list of SNMP traps, along with a group of users who receive email notifications for those traps. This appears in the show command. Use the no form of the command to delete the description.
Mode	cfg-email-event
Security Role(s)	network-engineer or crypto-officer
Syntax	description text no description   text (1-255 characters) is your description. Surround the text with quotation marks ( ) if it contains any spaces.
Default(s)	Built-In for the default tech-support role None for new email event roles.
Guidelines	The description appears in the output for show email-event.
Sample	bstnA(cfg-email-event[noc3])# description support team at NOC3 specifies a description for the noc3 email event role.
Related Commands	email-event show email-event

Purpose	Use the email-event command to start defining a set of ARX events to be emailed, the conditions under which the switch sends the email(s), and any recipients who should receive them. This creates a profile, or role, for one or more users who require event notification. Use no email-event to remove an email event role.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	email-event role no email-event role   role (1-128 characters) is a name that you choose for this set of email events, trigger conditions, and mail recipients (for example, nocGroup).
Default	tech-support is a default email event role, shipped from the factory
Guidelines	Before an email-event can notify any users of system events, smtp must be configured for this ARX. This command places you in cfg-email-event mode, where you can access several commands that define the email event role. To enable groups of events at a time, use the group (cfg-email-event) command. You can also use this command to set thresholds or schedules for email notification (for example, send for every 3 occurrences of a group event, or once each week). You can enable individual events with the group ... event command, which can also override any default-threshold settings made for the events group. The mail-to (cfg-email-event) command chooses an email recipient for this set of events; enter this command once for each desired recipient. You can use the description (cfg-email-event) command to add an optional description to the email event configuration; this appears in the output of show email-event. Use enable (cfg-email-event) to enable all of the rules in this email event configuration. Notification does not begin until you enable the email event role. You can reuse the email-event command to define multiple email event roles. Email messages have a field in the SMTP header where you can set a severity level. SMTP servers can use this field for sorting and flagging incoming messages; the server at F5 Support is configured to use this field for prioritizing customer issues. Use the email-severity command to set the email severity for a given event. The show email-severity command shows event severities. To send a small test message to all configured email recipients, use the smtp test email-event command. After a successful test, you can use smtp welcome to send an introductory email to all of the recipients. This email delivery mechanism can be used together with standard SNMP-trap delivery. Use snmp-server traps to start setting up SNMP traps.
Samples	bstnA(cfg)# email-event noc3 bstnA(cfg-email-event[noc3])# ... creates an email event role named noc3.   bstnA(cfg)# no email-event testEmail removes an email event configuration.
Related Commands	mail-to (cfg-email-event) group (cfg-email-event) group ... event description (cfg-email-event) enable (cfg-email-event) smtp snmp-server traps smtp test email-event smtp welcome

Purpose	You can use the email-event feature to send emails to one or more users (possibly including F5 Support) for certain SNMP traps. A field in the SMTP-message header contains the severity for the message. This field is not shown in most email applications, but email servers can use it for prioritization. Use the email-severity command to modify the email severity for a particular event. Use no email-severity to revert to a default email severity.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	email-severity event-name level {normal | warn | minor | major | critical} no email-severity event-name   event-name (1-64 characters) identifies an event. An event corresponds to one SNMP trap, cataloged in the ARX SNMP Reference. Use a ? after the email-severity keyword for a full list of eligible email events (for example, email-severity ?). normal | warn | minor | major | critical sets the severity for the events email messages.
Default	Defaults vary for each event; use show email-severity all to see them.
Guidelines	To send SNMP traps in email, configure smtp and then set up at least one email-event role. Use this command to set a severity level for an events email messages. The severity level appears in a customized field in the SMTP header, X-ARX-Severity. SMTP servers can use this field for sorting and flagging messages; the SMTP server at F5 Support is configured to sort email messages by this setting. You can use this to prioritize your events for Customer Support. Each severity that you set with this command is system-wide; it applies to any email-event role that uses the event. Use show email-severity to show the current severities for one or more events.
Samples	bstnA(cfg)# email-severity auto-reboot level critical sets the email severity to critical for an auto-reboot event.   bstnA(cfg)# no email-severity disk-state resets the disk-state event to a normal severity.
Related Commands	show email-severity smtp email-event

Purpose	You can define one or more SNMP-trap events to be emailed to one or more users, as well as the thresholds for sending each event. One collection of events, thresholds, and users is called an email event role. Use the enable command to activate the current role. Use no enable to disable the current email event role.
Mode	cfg-email-event
Security Role(s)	network-engineer or crypto-officer
Syntax	enable no enable
Default(s)	Disabled
Guidelines	You must enable an email event role to activate it.
Samples	bstnA(cfg-email-event[noc3])# enable enables the current email event role, noc3.   bstnA(cfg-email-event[betaTest])# no enable disables the betaTest role.
Related Commands	email-event

Purpose	Use the from command to set the From field in all email messages from the ARX. Use no from to revert to the default From string.
Mode	cfg-smtp
Security Role(s)	network-engineer or crypto-officer
Syntax	from hostname@domain no from   hostname@domain is 1-132 characters (for example, admin@arx1000-B.nemed.com). Use only alphabetical characters (a-z and A-Z), numeric characters (0-9), - (dash), _ (underscore), and/or . (period).
Defaults	None
Guidelines	The string you set with this command appears in the header of all email messages, in the From field. Enter an email address that uses acceptable characters (listed above in Syntax). If there are any invalid characters, the CLI rejects the string with an error. To see the current setting for the From field, use the show smtp status command.
Samples	bstnA(cfg-smtp)# from aco_admin@acopia.wwmed.com sets the From field for all outgoing messages.   bstnA(cfg-smtp)# no from erases the From string and reverts to the default.
Related Commands	smtp

Purpose	You can define SNMP-trap events to be emailed to one or more users, as well as the thresholds for sending each event. One collection of events, thresholds, and users is called an email event role. Use the group command to add an entire group of events to an email event role. Use the no form to remove a group of events from a role.
Mode	cfg-email-event
Security Role(s)	network-engineer or crypto-officer
Syntax	group group-name [threshold-counter counter | threshold-interval time {minutes | hours | days}]   no group group-name [threshold-counter counter | threshold-interval time {minutes | hours | days}]   group-name is chassis, cifs, storage, metadata, nsck, policy, snapshot, stats-monitor, virtual-server, network, redundancy (for any chassis except the ARX-VE), or all. threshold-counter counter (optional, 1-128) sets a threshold based on the number of events that occur from this group. For example, threshold-counter 4 means that each event from this group triggers an email if it occurs 4 times. threshold-interval time {minutes | hours | days} (optional) sets a schedule for this group. For example, threshold-interval 1 days causes the system to accumulate traps throughout the day and, if there are any, send a single email describing all of them. All time calculations begin when you enter this configuration; if the threshold interval is 1 day, the switch sends the email at the current time of day.
Default	no groups enabled If you enable a group without setting any threshold, the default is threshold-counter 1.
Platforms	You cannot choose the redundancy group on the ARX-VE.
Guidelines	This command enables one group of events for the current email event role. Whenever the system reaches a threshold you set with this command, it sends an email to any or all mail-to (cfg-email-event) recipients. You can optionally use the group ... event command to configure a single event in the group, or to set a different threshold for a particular event. The system keeps a maximum of 128 events for any event group. This is a hard threshold, even if you use the threshold-interval option to create a time-based schedule. For example, suppose you configure the following: group cifs threshold-interval 7 days This sends an email every week. However, if 128 CIFS events occur before the week is over, the system delivers an interim email with those events. This resets the start time for the 7-day schedule: the ARX delivers the next set of CIFS events 7 days later, or after 128 more events, whichever comes first. If you use group ... event to add a specific event, the no group command for its group does not delete that event. For example, the following command sequence does not delete the warmstart event: group chassis event warmstart no group chassis
Samples	bstnA(cfg-email-event[noc3])# group chassis adds the group of chassis events to this email role. This command uses the default threshold; every chassis event triggers an email as soon as it happens.   bstnA(cfg-email-event[noc3])# group metadata threshold-counter 5 adds the group of metadata events to this email role. Every 5th metadata event triggers an email.   bstnA(cfg-email-event[noc3])# no group storage removes the storage event group. This prevents any storage-group events from triggering emails.
Related Commands	email-event group ... event

Purpose	You can define one or more SNMP-trap events to be emailed to one or more users, as well as the thresholds for sending each event. One collection of events, thresholds, and users is called an email event role. Use the group ... event command to add one event to an email event role. Use the no form to remove an event from a role, or to revert its threshold to the group default.
Mode	cfg-email-event
Security Role(s)	network-engineer or crypto-officer
Syntax	group group-name event event-name [threshold-counter counter | threshold-interval time {minutes | hours | days}] no group group-name event event-name [threshold-counter counter | threshold-interval time {minutes | hours | days}]   group-name is chassis, cifs, storage, metadata, nsck, policy, snapshot, stats-monitor, virtual-server, network, redundancy (for any chassis except the ARX-VE), or all. event-name (1-64 characters) is one of the events in the group. Each of these corresponds to one SNMP trap, cataloged in the ARX SNMP Reference. Use a ? after the event keyword for a full list of events in this group (for example, group chassis event ?). threshold-counter counter (optional, 1-128) sets a threshold based on the number of times this event occurs. For example, threshold-counter 4 means that any four occurrences trigger an email. threshold-interval time {minutes | hours | days} (optional) sets a schedule for this event. For example, threshold-interval 1 days causes the system to accumulate instances of this event throughout the day and, if there are any, send a single email describing all of them. All time calculations begin when you enter this configuration; if the threshold interval is 1 day, the switch sends the email at the current time of day.
Default	All defaults are defined by the events group (see group (cfg-email-event)).
Platforms	You cannot choose the redundancy group on the ARX-VE.
Guidelines	This command enables one event for the current email event role. Whenever the system reaches its threshold for this event, it sends an email to any or all mail-to (cfg-email-event) recipients for this role. If you do not set any threshold for an event, its group threshold is used (as set by the group (cfg-email-event) command). The no form of the command disables the events threshold (so that the event defaults to the threshold for its group), or removes the event altogether. See the Samples, below.
Samples	bstnA(cfg-email-event[noc3])# group metadata event online threshold-counter 2 adds one metadata event, online, to this email role. The threshold is 2 events; the system sends an email for every second event that indicates that a metadata share is online.   bstnA(cfg-email-event[testteam])# group virtual-server event server-offline adds the server-offline event to email event role, testteam. The threshold defaults to whatever threshold is set for the virtual-server group.   bstnA(cfg-email-event[noc3])# no group metadata event online threshold-counter 2 reverts the online event to the default threshold. This default is defined by the metadata group.   bstnA(cfg-email-event[noc3])# no group chassis event cpu-status removes the cpu-status event from this email event role.
Related Commands	email-event mail-to (cfg-email-event) group (cfg-email-event)

Purpose	The mail-server command identifies the next-hop email server for the ARX. Use no mail-server to delete the email server name.
Mode	cfg-smtp
Security Role(s)	network-engineer or crypto-officer
Syntax	mail-server ip-or-name no mail-server   ip-or-name (1-132 characters) identifies the mail server, either by IP address or DNS name (for example, 192.168.25.44 or mailServer3.myco.com).
Default	None
Guidelines	This is required for SMTP to function. This is the local mail server to deliver the ARXs email messages to the WAN. You must have a DNS server configured to use a DNS name in this command. Refer to the ip name-server documentation to configure a DNS server. To see the currently configured mail server, use the show smtp status command. To test the mail-server configuration, use the smtp test server command.
Important: The no mail server command disables all email deliveries.
Sample	bstnA(cfg-smtp)# mail-server email1.wwmed.com identifies the mail server.
Related Commands	smtp smtp test server ip name-server

Purpose	You can define one or more SNMP-trap events to be emailed to one or more users, as well as the thresholds for sending each event. One collection of events, thresholds, and users is called an email event role. Use the mail-to command to set one destination address for the current roles emails. Use the no mail-to command to remove an email recipient.
Mode	cfg-email-event
Security Role(s)	network-engineer or crypto-officer
Syntax	mail-to recipient no mail-to recipient   recipient (1-768 characters) is one email recipient (for example, juser@nemed.com).
Default	None
Guidelines	This sets a destination for all emails from this email event role; this address appears in the To field of the emails. You can enter this command multiple times, once for each recipient. At least five separate destinations are supported. A sample email appears in Figure 13.1 on page 13-15. You can use the ID (highlighted in the sample) to look up the trap in the ARX SNMP Reference.
Samples	bstnA(cfg-email-event[noc3])# mail-to juser@wwmed.com sets up one email recipient for the noc3 role. If a system event triggers a threshold, the system sends an email notification to juser@wwmed.com.   bstnA(cfg-email-event[noc3])# no mail-to ex@nemed.com removes an email recipient from the noc3 role.
Related Commands	email-event

Purpose	When the ARX fails to deliver an email message, it retries periodically. If the failures persist for too long, the ARX deletes the message. Use the maximum age command to determine the maximum amount of time to retry before deleting the message. Use no maximum age to return to the default.
Mode	cfg-smtp
Security Role(s)	network-engineer or crypto-officer
Syntax	maximum age days no maximum age   days (1-366) is the number of days to retry before deleting the message.
Default	4 (days)
Guidelines	The ARX retries a message every n minutes for the first two hours; you can use retry interval to set the value of n. The retry interval increases geometrically if the failures persist. After some number of days without success (set by this command, maximum age), the switch deletes the message from the mail queue. Use show smtp queue to view all messages currently in the mail queue. These are the messages that have failed and are being saved for retries. You can use smtp retry to retry all queued messages now. The clear smtp queue command deletes all the messages without sending them.
Samples	bstnA(cfg-smtp)# maximum age 30 keeps all failed emails for up to 30 days before deleting them.   bstnA(cfg-smtp)# no maximum age reverts to the default.
Related Commands	smtp retry interval smtp retry clear smtp queue

Purpose	When the ARX fails to deliver an email message, it waits for some number of minutes before retrying. Use the retry interval command to set the initial interval between retries. Use no retry interval to return to the default interval.
Mode	cfg-smtp
Security Role(s)	network-engineer or crypto-officer
Syntax	retry interval minutes no retry interval   minutes (1-119) is the number of minutes to wait between email retries.
Default	15 (minutes)
Guidelines	The ARX retries a message every n minutes for the first two hours; this command sets the value of n. The retry interval increases geometrically if the failures persist. After some number days without success (set by maximum age), the switch deletes the message from the mail queue. Use show smtp queue to view all messages currently in the mail queue. These are the messages that have failed and are being saved for retries. You can use smtp retry to retry all queued messages now. The clear smtp queue command deletes all the messages without sending them.
Samples	bstnA(cfg-smtp)# retry interval 10 sets a 10-minute interval.   bstnA(cfg-smtp)# no retry interval reverts to the default interval.
Related Commands	smtp maximum age show smtp queue smtp retry clear smtp queue

Purpose	You can define one or more SNMP-trap events to be emailed to one or more users, as well as the thresholds for sending each event. One collection of events, thresholds, and users can be applied to technicians with a certain role. Use the show email-event command to see the configuration for one or all email event roles.
Mode	(all)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show email-event {role-name | all}   role-name (1-128 characters) is one role (for example, tech-support). all selects all roles.
Guidelines	The output contains up to four tables per email event role. SMTP shows a summary of the SMTP settings for this ARX: From is used in the From field of all emails. You can set this with from (cfg-smtp). Local Mail Server is the SMTP server that is the next hop for all emails. You can set this with mail-server. Email Event describes the configuration of one email-event role: Role is the name of the email-event role, set with the email-event command. Description shows the optional description for this role. You can use the description (cfg-email-event) command to set (or change) this description. To is a comma-separated list of email recipients. You can add one with the mail-to (cfg-email-event) command. Admin State shows whether or not this role is enabled. Use enable (cfg-email-event) to enable the role. The next table only appears if at least one event group is defined. It contains one row per event group, with the following columns in each row: Group Name is set with the group (cfg-email-event) command. Threshold Counter is either a number or n/a. If this many events from the group occur, the system sends an email. This is set with the threshold-counter option in the above group command. Threshold Interval (every) is either time value (such as 2 hours or 7 days) or n/a. If any events from the group occur during this time, the system sends an email at the end of the time interval. This is set with the threshold-interval option in the group command.
Guidelines (Cont.)	The next table only appears if at least one individual event is defined. It contains one row per event, with the following columns in each row: Group Name is set with the group ... event command. Event Name is set with the same command. Threshold Counter is either a number or n/a. If this many instances of the event occur, the system sends an email. This is set with the threshold-counter option in the group ... event command. Threshold Interval (every) is either time value (such as 10 minutes or 12 hours) or n/a. If any instances of this event occur during this time, the system sends an email at the end of the time interval. This is set with the threshold-interval option in the group ... event command.
Samples	bstnA# show email-event all shows all email event roles. See Figure 13.2 on page 13-19 for sample output.   bstnA# show email-event noc3 shows the configuration for one email event role. See Figure 13.3 on page 13-20 for sample output.
Related Commands	email-event mail-to (cfg-email-event) description (cfg-email-event) group (cfg-email-event) group ... event enable (cfg-email-event) smtp from (cfg-smtp) mail-server

Purpose	You can set up SNMP-trap events to be emailed to one or more users, and you can use a separate command to set the severity of each events email message. The severity is expressed in a hidden field in the email header, which email servers can use for flagging and prioritizing email messages. Use the show email-severity command to see the severities for this switchs email events.
Mode	(all)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show email-severity {event-name | all | non-default}   event-name (1-64 characters) is one event (for example, module-failure). all shows all events. non-default shows any events that have a non-default severity.
Guidelines	The output is a table with two columns: Event Name and Severity. You can use the email-severity command to reset the severity.
Samples	bstnA# show email-severity all shows all email events and their current severity settings. See Figure 13.4 on page 13-21 for sample output.   bstnA# show email-severity non-default shows the email events whose severities have been reset. See Figure 13.5 on page 13-25 for sample output.   bstnA# show email-severity nvram-battery-failure shows the severity for a particular email event. See Figure 13.6 on page 13-25 for sample output.
Related Commands	email-severity email-event

Purpose	Use the show smtp queue command to see the email messages that are queued for delivery, if any.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show smtp queue
Guidelines	This command is used to see messages that failed delivery. email messages are in the queue for a very short time before they are sent out to the mail server; they stay in the queue longer if the delivery failed. Therefore, if all messages deliver on the first try, this command shows no messages in the queue. The output is a table with two rows per message. The top row contains the following fields: Status is pending, to indicate that the message is waiting for final delivery. From can be reset (for future emails) with from (cfg-smtp). Size is in bytes if no unit (K, M, G, or T) appears after the number. K is for KiloBytes (1024 bytes), M is for MegaBytes (1024*1024 bytes), and so forth. The bottom row contains two more fields: Time is when the message was created. To can be reset for future emails with to. The ARX retries a message every few minutes (set by retry interval) for the first two hours. This retry interval increases geometrically if the failures persist. After some days without success (set by maximum age), the switch deletes the message from the mail queue. You can use smtp retry to retry all queued messages now. The clear smtp queue command deletes all the messages without sending them.
	Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP.
Sample	bstnA# show smtp queue shows the queue of pending email messages, if any. See Figure 13.7 for sample output.
Related Commands	smtp to from (cfg-smtp) smtp retry show smtp status

Purpose	Use the show smtp status command to see the status of the most recent outbound email, as well as all SMTP-configuration settings.
Mode	(all)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show smtp status
Guidelines	SMTP Last Transfer shows the last email message that was collected for delivery. This is not the most-recent retry; it is the most-recent message (or test) that was generated. Last file is the file name and size for the attachment file. Status shows the status of the most-recent delivery: Success Delivered to mail-server Deferred means that the message has been added to the mail queue. Configuration error means that the configuration is missing some information. (see the SMTP Current Configuration section, below) Could not communicate with mailserver indicates a network problem, a DNS-configuration error, or an SMTP configuration error (such as the wrong name for mail-server). Message size exceeds limit means that the local mailserver did not accept the large attachment with the file. You must configure the mail server to allow very large email attachments. Unable to relay Insufficient disk space indicates that there is not enough disk space to add the message to the mail queue.
Guidelines (Cont.)	Error building mail header, SMTP error, Internal error mailing file, and Error uuencoding file are internal problems. Message Created is the time when the message was first generated. The remaining fields show the header for the email message. SMTP Current Configuration shows the configuration that is in effect. This configuration will be applied to current and future email messages. To can be set with to. From can be set with from (cfg-smtp). Via is the SMTP server that is the next hop for all emails. You can set this with mail-server. Retry Interval is the time between retries for messages in the mail queue. The ARX uses this interval for the first two hours, then starts using larger intervals if the failures persist. You can set this initial interval with the retry interval command. Maximum Age is maximum number of days to keep a message in the mail queue before deleting it. Use maximum age to set this value. Use show smtp queue to see any pending email messages. To send a test message, use smtp test message. If messages are failing, you can run smtp test server to test SMTP communication with the local email server.
Sample	bstnA# show smtp status shows the SMTP status for the current switch. See Figure 13.8 for sample output.
Related Commands	smtp to from (cfg-smtp) mail-server show smtp queue smtp test message smtp test server

Purpose	You can use the smtp welcome command to send an introductory email to all users of an email-event role. Use the show smtp welcome command to see the welcome message for this introductory email.
Mode	(all)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show smtp welcome
Guidelines	This command displays the welcome message that appears at the top of an smtp welcome email.
Sample	bstnA# show smtp welcome Welcome to the <EMAIL_EVENT_ROLE> role. The host <HOSTNAME> will send email to you based on the following events: shows the outline of the welcome message. The <EMAIL_EVENT_ROLE> variable is replaced by the roles name (set with email-event), and the <HOSTNAME> is replaced by the ARXs host name (set with hostname).
Related Commands	smtp welcome smtp email-event hostname

Purpose	The ARX uses the Simple Mail Transfer Protocol (SMTP) to send email messages to other machines. Use the smtp command to begin SMTP configuration. Use no smtp to erase all SMTP configuration parameters and disable email notifications.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	smtp no smtp
Default	no smtp
Guidelines	You must configure DNS for the SMTP service to work. See the instructions for ip name-server. You must have layer-2 and layer-3 connectivity to your server network(s) before DNS or SMTP can function. Use this command to enter cfg-smtp mode, where you set up the necessary parameters for email. You can use from (cfg-smtp) to set the From field in all out-bound emails (for example, From: hostname@domain). The mail-server command identifies the local mail server to be used as the next hop for mail messages. Use the to command to set one or more destinations for emails. If an email delivery fails, it retries at the frequency set by retry interval, up to a maximum number of days (maximum age). After the maximum age expires, the ARX deletes the message.
Guidelines: Testing and Debugging	To send a test message, use smtp test message reply-to with a local destination for the message. You can view any undelivered messages with the show smtp queue command. Use the smtp retry and clear smtp queue commands to manage this mail queue. If messages are consistently failing, you can run smtp test server to test SMTP communication with the local email server.
Guidelines: Applications for SMTP	After you finish configuring SMTP, you can configure certain system events to be delivered in email messages. Each event is analogous to an SNMP trap; see the ARX SNMP Reference for a full list of ARX Enterprise traps, including the traps that have email support. You can choose individual events or groups of them, one or more email recipients for the events, and thresholds (or a schedule) for sending the emails. All of these components can be assigned to technicians who perform a specific role. Use the email-event command to begin configuring one such role. You can create multiple roles by re-using this command. SMTP is also useful for sending collected diagnostics and other maintenance files over email. After you configure SMTP, use the collect command to collect and send diagnostics. You can also use copy smtp to send log files, reports, or other files that could be useful for maintenance.
Samples	bstnA(cfg)# smtp bstnA(cfg-smtp)# ... starts SMTP configuration.   bstnA(cfg)# no smtp deletes all SMTP configuration and disables email notifications.
Related Commands	ip name-server email-event collect copy smtp

Purpose	The SMTP mail queue holds email messages until they are successfully delivered. Use the smtp retry command to retry all queued messages at once.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	smtp retry
Default	None
Guidelines	This is particularly useful if there was a network problem between the ARX and the next-hop mail server (mail-server). After you fix the network problem, you can use this command to re send all queued messages. You can use show smtp queue to see the mail queue before and after the retry. As an alternative, you can use clear smtp queue to remove all messages from the queue. For each message that is successfully delivered to the mail server, Message sent appears after the command. For each failed delivery, Message deferred appears. When you change a parameter in cfg-smtp mode (see smtp) and then exit the mode, the ARX automatically retries all messages in the queue using the new parameters. There is no need to invoke this command under these circumstances. Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP.
Sample	bstnA# smtp retry retries all pending email messages, if there are any.
Related Commands	smtp show smtp queue show smtp status

Purpose	Use the smtp test email-event command to test an email-event configuration. This sends a test email to all configured recipients.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	smtp test email-event role-name   role-name (1-128 characters) is the role to test (for example, tech-support). Use show email-event all for a list of all configured email-event roles.
Default	None
Guidelines	Use this command to send an email message with a small test attachment. the message goes to all mail-to (cfg-email-event) recipients configured for the chosen email-event role. Use show email-event role-name to see all recipients for a given role. You can use this to verify the email-event configuration and SMTP setup. If the message is successfully delivered to the next-hop mail-server, a message appears similar to the following: Message sent to juser@wwmed.com,jqpublic@wwmed.com. An error appears if there is a delivery problem. In this case, you can use show smtp queue to see the test message in the mail queue. To retry the message (perhaps after correcting the network configuration), use smtp retry. Use clear smtp queue to remove all messages from the queue. If the delivery problems persist, you can run an SMTP diagnostic test, smtp test server, and send the output back to F5 for analysis. Note that the test message has a small attachment, so this does not test any errors that may come up with large attachments. An attachment from copy smtp or collect can be hundreds of MegaBytes. Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP. After a successful test, you can use the smtp welcome command to send a welcome message to all email recipients. This message informs the recipients of the events that will trigger email messages in the future.
Sample	bstnA# smtp test email-event noc3   Message sent to juser@wwmed.com,jqpublic@wwmed.com for role "noc3".   successfully sends a test message to the recipients of the noc3 email event. See Figure 13.9 for a sample email.
Related Commands	email-event mail-to (cfg-email-event) show email-event smtp show smtp queue smtp retry clear smtp queue smtp test server show smtp status smtp welcome

Purpose	Use the smtp test message command to send a test email message.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	smtp test message [reply-to user@domain]   user@domain (optional, 1-256 characters) is an email destination for the test-message reply.
Default	reply-to user@domain defaults to the setting of the to command if you omit the option.
Guidelines	Use this command to send an email message with a small test attachment to an SMTP server at F5. This tests the SMTP configuration settings and the network connection to the local email server. You can use this to verify the SMTP setup. The message is delivered to the next-hop mail-server. An error appears if there is a delivery problem. In this case, or if no reply email arrives for 15 minutes or more, you can use show smtp queue to see the test message in the mail queue. Also, check the email filter at the destination mailbox. To retry the message (perhaps after correcting the network or filter configuration), use smtp retry. Use clear smtp queue to remove all messages from the queue. If the delivery problems persist, you can run an SMTP diagnostic test, smtp test server, and send the output back to F5 for analysis. Note that the test message has a small attachment, so this does not test any errors that may come up with large attachments. An attachment from copy smtp or collect can be hundreds of MegaBytes. Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP.
Sample	bstnA# smtp test message reply-to jsmith@wwmed.com   sends a test message to an SMTP server at F5. If the delivery succeeds, the F5 server will send a reply to jsmith@wwmed.com.
Related Commands	smtp to show smtp queue smtp retry clear smtp queue smtp test server show smtp status

Purpose	At the advice of F5 personnel, use the smtp test server command to test the SMTP-layer connection to the email server.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	smtp test server
Default	None
Guidelines	This command runs a series of STMP queries against the next-hop mail-server. After you enter this command, the CLI shows the detailed results of this test. Run the test when you see email delivery problems. If the SMTP queue has undelivered messages in it (show smtp queue), or if smtp test message fails, you should run this test. Send the results back to F5 for further diagnosis.
Sample	bstnA# smtp test server tests the connection to the next-hop email server. See Figure 13.10 for sample output.
Related Commands	smtp show smtp queue smtp test message

Purpose	Use the smtp welcome command to send an introductory email message to all users in an email-event configuration. The introductory message informs the recipients of the types of system events they will be receiving through email.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	smtp welcome [role-name]   role-name (optional, 1-128 characters) is the role to receive the email message (for example, noc_7). Use show email-event all for a list of all configured email-event roles.
Default	role-name defaults to all roles if you omit it. That is, the command sends a welcome message to all users in all email-event roles.
Guidelines	Use this command to send an introductory email message to the recipients of email events. the message goes to all mail-to (cfg-email-event) recipients configured for the chosen email-event role (or all roles, if no specific role was selected). Use show email-event role-name to see all recipients for a given role. If the message is successfully delivered to the next-hop mail-server, a message appears similar to the following: Message sent to juser@wwmed.com,jqpublic@wwmed.com. Use show smtp status to see details on the most-recent message delivery, and to view the current configuration for SMTP. If the message fails, you can use smtp test email-event to test the email-event configuration and SMTP setup. The email contains a welcome message and two tables to outline the types of events that the recipient can expect in email messages. The top table shows event groups, and the bottom table contains individual events that will trigger an email. The show smtp welcome command shows the format of the welcome message.
Sample	bstnA# smtp welcome noc3   Message sent to to jqpublic@wwmed.com.   successfully sends a welcome message to the recipients of the noc3 email event. See Figure 13.11 for a sample email.
Related Commands	email-event mail-to (cfg-email-event) show email-event smtp test email-event clear smtp queue smtp test server show smtp status show smtp welcome

Purpose	Use the to command to set destination address(es) for emails from the ARX. Use the no to command to revert to the default destination.
Mode	cfg-smtp
Security Role(s)	network-engineer or crypto-officer
Syntax	to destination-list no to   destination-list (1-1024 characters) is a comma-separated list of email recipients (for example, juser@nemed.com or jqpublic@wwmed.com,juser@nemed.com). Surround this field with quotation marks if it contains any spaces.
Default	e-support@f5.com
Guidelines	This sets the destination(s) for emails from the ARX; these addresses appear in the To field of the emails. These addresses only apply to emails from collect, copy smtp, and smtp test message. Each email-event role has its own set of email recipients, configured with the mail-to (cfg-email-event) command. The default address sends messages back to Technical Support at F5. For most running systems, this default is appropriate. You can use this command to test email notifications, or to send email to one or more different support organizations. To change any address in the list, re-run this command with an entirely new list of addresses. To see the current email destination(s), use the show smtp status command.
Samples	bstnA(cfg-smtp)# to juser@das1.wwmed.com,e-support@f5.com sets two destinations for all outgoing messages.   bstnA(cfg-smtp)# no to resets the destination back to the default.
Related Commands	smtp show smtp status copy smtp collect