This notification contains the opaque type for the temperatureName of the sensor which has failed. This notification contains the opaque type for the fanName of the fan which has failed. This notification contains the opaque type for the keyDescription of the Feature Key that is pending expiration or has expired.
This notification contains the opaque type for the updateServiceName of the update service that has failed. This notification contains the opaque type for raidID of the drive which has changed state. The connectionURL configured is returned when the notification is triggered. The resetcounters command resets cumulative email monitoring counters. The reset affects global counters as well as per host counters. The reset does not affect the counters on messages in the delivery queue related to retry schedules.
Cisco AsyncOS allows you to perform operations on messages in the email queue. You can delete, bounce, suspend, or redirect messages in the email queue. You can also locate, remove, and archive older messages in your queue. If particular recipients are not being delivered or to clear the email queue, use the deleterecipients command.
The deleterecipients command allows you to manage the email delivery queue by deleting specific recipients waiting for delivery. Recipients to be deleted are identified by either the recipient host that the recipient is destined for, or the message sender identified by the specific address given in the Envelope From line of the message envelope.
Alternately, you can delete all messages in the delivery queue all active recipients at once. Matches to recipient hosts and senders must be identical string matches. Wild cards are not accepted. The deleterecipients command returns the total number of messages deleted.
In addition, if a mail log subscription IronPort text format only is configured, the message deletion is logged as a separate line. The appliance gives you various options to delete recipients depending upon the need. The following example show deleting recipients by recipient host, deleting by Envelope From Address, and deleting all recipients in the queue.
Similar to the deleterecipients command, the bouncerecipients command allows you to manage the email delivery queue by hard bouncing specific recipients waiting for delivery. Message bouncing follows regular bounce message configuration as specified in the bounceconfig command. The bouncerecipients command returns the total number of messages bounced. Recipients to be bounced are identified by either the destination recipient host or the message sender identified by the specific address given in the Envelope From line of the message envelope.
Alternately, all messages in the delivery queue can be bounced at once. The redirectrecipients commands allow you to redirect all messages in the email delivery queue to another relay host. Please note that redirecting recipients to a host or IP address that is not prepared to accept large volumes of SMTP mail from this host will cause messages to bounce and possibly result in the loss of mail. The CLI does not display a warning if you redirect mail to such a domain.
Check the SMTP route for the receiving domain before redirecting messages. Use the showrecipients command to show messages from the email delivery queue by recipient host or Envelope From address.
You can also show all messages in the queue. The following example shows messages in the queue for all recipient hosts. To temporarily suspend email delivery for maintenance or troubleshooting, use the suspenddel command.
The suspenddel command puts Cisco AsyncOS into suspended delivery state. This state is characterized by the following:. The suspenddel command lets open outbound connections close, and it stops any new connections from opening. The suspenddel command commences immediately, and allows any established connections to successfully close.
Use the resumedel command to return to regular operations from the suspended delivery state. The resumedel command returns Cisco AsyncOS to normal operating state after using the suspenddel command. To temporarily suspend all listeners from receiving email, use the suspendlistener command.
While receiving is suspended, the system does not accept connections to the specific port of the listener. This behavior has changed in this release of AsyncOS. In previous releases, the system would accept connections, respond with the following responses and disconnect:. The resumelistener command returns Cisco AsyncOS to normal operating state after using the suspendlistener command. Recipients and hosts that are scheduled for later delivery can be immediately retried by using the delivernow command.
The delivernow command allows you to reschedule email in the queue for immediate delivery. All domains that are marked down and any scheduled or soft bounced messages are queued for immediate delivery.
The delivernow command can be invoked for all recipients or specific recipients in the queue scheduled and active. When selecting specific recipients, you must enter the domain name of the recipients to schedule for immediate delivery. The system matches the entire string for character and length. You can manually pause the work queue portion of message processing using the workqueue command.
For example, assume that you wanted to change the configuration of an LDAP server configuration while many messages are in the work queue.
Perhaps you want to switch from bouncing to dropping messages based on an LDAP recipient access query. Or perhaps you want to pause the queue while you manually check for the latest anti-virus scanning engine definition files via the antivirusupdate command. The workqueue command allows you to pause and resume the work queue to stop processing while you perform other configuration changes. When you pause and resume the work queue, the event is logged.
For example. Sometimes older messages remain in the queue because they could not be delivered. You may want to remove and archive these messages. Use the oldmessage CLI command to display the oldest non-quarantine message on the system.
You can then optionally use the removemessage to safely remove the message for the given message ID. This command can only remove messages that are in the work queue, retry queue, or a destination queue.
If the message is in none of these queues, it cannot be removed. You can also use the archivemessage[mid] CLI command to archive the message for a given message ID into an mbox file in the configuration directory. You cannot use the oldmessage command to get the message ID for a message in a quarantine. However, if you know the message ID, you can show or archive the specified message.
Since the message is not in the work queue, retry queue, or a destination queue, you cannot remove the message with the removemessage command. The findevent CLI command simplifies the process of tracking messages within the system using the onbox mail log files. The findevent CLI command allows you to search through the mail logs for a particular message by searching for a message ID or a regular expression match against the subject header, envelope sender or envelope recipient.
You can display results for the current log file, all the log files, or display log files by date. When you view log files by date, you can specify a date or a range of dates. After you identify the message you want to view logs for, the findevent command displays the log information for that message ID including splintering information split log messages, bounces and system generated messages.
Please note:. Use the snmpconfig command to enable and configure SNMP monitoring for the appliance. These version 3 requests must include a matching passphrase. By default, version 1 and 2 requests are rejected. If enabled, version 1 and 2 requests must have a matching community string. Use the latest available MIB files. Hardware sensors conforming to the Intelligent Platform Management Interface Specification IPMI report information such as temperature, fan speed, and power supply status.
It is a good idea to poll for the hardware status and identify possible hardware failures before they become critical. Temperatures within 10 per cent of the critical value may be a cause for concern. For information such as the number of power supplies and the range of operating temperatures for your appliance , see the hardware guide for your model. For the location of hardware guides, see Documentation.
Status change traps are sent when the status changes. Fan Failure and high temperature traps are sent every 5 seconds. The other traps are failure condition alarm traps — they are sent once when the state changes healthy to failure. For example, on C appliances , traps are sent if the following thresholds are reached:. To see the available traps and threshold values on your appliance , run the snmpconfig command from the command-line interface.
Note that failure condition alarm traps represent a critical failure of the individual component, but may not cause a total system failure. For example, a single fan or power supply can fail on an appliance with multiple fans or power supplies and the appliance will continue to operate.
SNMP provides the ability to send traps, or notifications, to advise an administration application an SNMP management console, typically when one or more conditions have been met. Traps are network packets that contain data relating to a component of the system sending the trap.
Traps are generated when a condition has been met on the SNMP agent in this case, the appliance. To enable and configure SNMP traps, use the snmpconfig command. To specify multiple trap targets: when prompted for the trap target, you may enter up to 10 comma separated IP addresses.
The community string public is entered for GET requests from versions 1 and 2. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. Updated: March 25, The raw number of messages, recipients, and bounce recipients that the appliance is processing in the email pipeline The hourly rate of message delivery or message bounces based on the last one-minute, five-minute, or fifteen-minute period Monitoring system resources.
Examples: Fan failure Update failure Abnormally high appliance temperature Managing email within the pipeline. Examples: Deleting recipients in the queue Redirecting messages to another host Clear the queue by deleting recipients or redirecting the messages Suspend or resume email receiving, delivery, or work queue processing Locate specific messages Reading the Available Components of Monitoring Reading the Event Counters Reading the System Gauges Reading the Rates of Delivered and Bounced Messages Reading the Event Counters Counters provide a running total of various events in the system.
Counters increment each time an event occurs and are displayed in three versions: Reset Since the last counter reset with the resetcounters command Uptime Since the last system reboot Lifetime Total through the lifetime of the appliance The following table lists the available counters and their description when monitoring the appliance.
Note This is the entire list. The displayed counters vary depending on which display option or command you choose.
Use this list as a reference. Table 1. Recipients Received Recipients on all received messages. Generated Bounce Recipients Recipients for which bounces have been generated by the system and inserted into the delivery queue.
Rejection Rejected Recipients Recipients that have been denied receiving into the delivery queue due to the Recipient Access Table RAT , or unexpected protocol negotiation including premature connection termination. Dropped Messages Messages that have been denied receiving into the delivery queue due to a filter drop action match or have been received by a Sinkhole queuing listener. Queue Soft Bounced Events Number of soft bounce events — a message that soft bounces multiple times has multiple soft bounce events.
Completion Completed Recipients Total of all hard bounced recipients, delivered recipients, and deleted recipients. Expired Hard Bounces Message recipients that have exceeded the maximum time allowed in the delivery queue or the maximum number of connection attempts. Filter Hard Bounces Recipient delivery has been preempted by a matching filter bounce action.
Other Hard Bounces An unexpected error during message delivery or a message recipient was explicitly bounced via the bouncerecipients command. Delivered Recipients Message successfully delivered to a recipient. Deleted Recipients Total of message recipients explicitly deleted via the deleterecipients command or was a Global Unsubscribe Hit. Global Unsubscribe Hits Message recipient was deleted due to a matching global unsubscribe setting.
Reading the System Gauges Gauges show the current utilization of a system resource such as memory, disk space, or active connections. The displayed gauges will vary depending upon which display option or command you choose. Table 2. Resource Conservation A value between 0 and 60 or Connections Gauges Current Inbound Connections Current inbound connections to the listener interfaces. Current Outbound Connections Current outbound connections to destination mail servers.
Queue Gauges Active Recipients Message recipients in the delivery queue. Unattempted Recipients A subcategory of Active Recipients. Attempted Recipients A subcategory of Active Recipients. Messages in Work Queue The number of messages waiting to be processed by alias table expansion, masquerading, anti-spam, anti-virus scanning, message filters, and LDAP queries prior to being enqueued.
Messages in Quarantine The unique number of messages in any quarantine, plus messages that have been released or deleted but not yet acted upon. Destinations in Memory The number of destinations domains in memory. Kilobytes Used Queue storage used in kilobytes. Kilobytes in Quarantine Queue storage used for quarantined messages. Kilobytes Free Queue storage remaining in kilobytes. Reading the Rates of Delivered and Bounced Messages All rates are shown as the average rate an event occurs per hour at the specific point in time the query is made.
The displayed rates will vary depending upon which display option or command you choose. Table 3. Rates Statistic Description Messages Received Rate of messages inserted into the delivery queue per hour. Recipients Received Rate of the number of recipients on all messages inserted into the delivery queue per hour. Soft Bounced Events Rate of the number of soft bounce events per hour. Completed Recipients Rate of the total of all hard bounced recipients, delivered recipients and deleted recipients.
Hard Bounced Recipients Rate of the total of all DNS hard bounces, 5XX hard bounces, filter hard bounces, expired hard bounces and other hard bounces per hour. Delivered Recipients Rate of messages successfully delivered to a recipient per hour.
Table 4. Last counter reset Displays the last time the counters were reset. System status Online, offline, receiving suspended, or delivery suspended. Oldest Message Displays the oldest message waiting to be delivered by the system. Features Displays any special features installed on the system by the featurekey command. Example mail3. The counter will be reset if the connection is eventually dropped.
Monitoring the Status of a Mail Host If you suspect delivery problems to a specific recipient host or you want to gather information on a Virtual Gateway address, the hoststatus command displays this information. Table 5. Oldest Message The age of the oldest active recipient in the delivery queue for this domains. Last Activity This field is updated each time a message delivery is attempted to that host. Table 6. Last Activity Same definition as global hoststatus field of the same name — tracked per Virtual Gateway address.
Recipients This field also corresponds to the same definition as the global hoststatus command. Last 5XX error This field contains the most recent 5XX status code and description returned by the host. Determining the Make-up of the Email Queue To get immediate information about the email queue and determine if a particular recipient host has delivery problems — such as a queue buildup — use the tophosts command.
Active Recipients 2. Connections Out 3. Delivered Recipients 4. The target host address on your appliance to poll with 'hostname' or 'x. The -l option configures authentication and encryption features to be used. This is a string from 1 to 32 octets of length. Should be configured in the same way at both SNMP entities trying to communicate.
The -a option is to set Authentication.
0コメント