Event Actions
Path: Administration > Notification > Event Actions > options
Types of Notification
You can configure event actions to occur in response to an event or group of events. These actions notify users of the event in any of several ways:
- Active, automatic notification. The specified users or monitoring devices are contacted directly.
- E-mail notification
- SNMP traps
- Remote Monitoring Service
- Syslog notification
- Indirect notification
- Event log. If no direct notification is configured, users must check the log to determine which events have occurred
ReferenceYou can also log system performance data to use for device monitoring. Refer to the "Data log" section in the, "Information Logs" chapter of this manual.
- Queries (SNMP GETs)
Reference For more information, refer to the "SNMP" section in the, "Administration : Network Features" chapter of this manual. SNMP enables an NMS to perform informational queries. SNMPv1does not encrypt data before transmission. Configuring the most restrictive SNMP access type (READ) enables informational queries without the risk of allowing remote configuration changes.
Configuring Event Actions
Notification Parameters
For events that have an associated clearing event, you can also set the following parameters as you configure events individually or by group, as described in the next two sections. To access the parameters, click the receiver or recipient name.
| Parameter | Description |
|---|---|
| Delay x time before sending | If the event persists for the specified time, notification is sent. If the condition clears before the time expires, no notification is sent. |
| Repeat at an interval of x time | The notification is sent at the specified interval. |
| Up to x times | During an active event, the notification repeats for this number of times. |
| Until condition clears | The notification is sent repeatedly until the condition clears or is resolved. |
Configuring by Event
To define event actions for an individual event:
- Select the "Administration" tab, "Notification" on the top menu bar, and "by event" under "Event Actions" on the left navigation menu.
- In the list of events, review the marked columns to see whether the action you want is already configured. (By default, logging is configured for all events.)
- To view or change the current configuration, such as recipients to be notified by e-mail or paging, or Network Management Systems (NMSs) to be notified by SNMP traps, click the event name.
Note: If no Syslog server is configured, items related to Syslog configuration are not displayed.
ReferenceWhen viewing details of an events configuration, you can change the configuration, enable or disable event logging or Syslog, or disable notification for specific e-mail recipients or trap receivers, but you cannot add or remove recipients or receivers. To add or remove recipients or receivers, see the following:
ReferenceRefer to "Identifying Syslog Servers"section in this chapter.
ReferenceRefer to "E-mail Recipients"section in this chapter.
ReferenceRefer to "Trap Receivers"section in this chapter.
Configuring by Group
To configure a group of events simultaneously:
- Select the "Administration" tab, "Notification" on the top menu bar, and "by group" under "Event Actions" on the left navigation menu.
- Choose how to group events for configuration:
- Choose "Grouped by severity", and then select all events of one or more severity levels. You cannot change the severity of an event.
- Choose "Grouped by category", and then select all events in one or more pre-defined categories.
- Click "Next>>" to move from page to page for performing the following actions:
- Select event actions for the group of events.
- To choose any action except "Logging" (the default), you must first have at least one relevant recipient or receiver configured.
- If you choose "Logging" and have configured a Syslog server, select "Event Log" or "Syslog" (or both) on the next page.
- To choose any action except "Logging" (the default), you must first have at least one relevant recipient or receiver configured.
- Select whether to leave the newly configured event action enabled for this group of events or to disable the action.
- Select event actions for the group of events.
Active, Automatic, Direct Notification
E-mail Notification
Overview of Setup
Use the Simple Mail Transfer Protocol (SMTP) to send e-mail to up to four recipients when an event occurs.
To use the e-mail feature, define the following settings:
- The IP addresses of the primary and, optionally, the secondary Domain Name System (DNS) servers.
- The IP address or DNS name for "SMTP Server" and "From Address".
- The e-mail addresses for a maximum of four recipients.
ReferenceYou can use the "To Address" setting of the "recipients" option to send e-mail to a text-based pager.
SMTP
Path: Administration > Notification > E-mail > server
| Setting | Description |
|---|---|
| Local SMTP Server | The IPv4/ IPv6 address or DNS name of the local SMTP server. "NOTE" : This definition is required only when "SMTP Server" is set to "Local". |
| From Address | The contents of the From field in e-mail messages sent by the NMC: - In the format user@ [IP_address] (if an IP address is specified as Local SMTP Server) - In the format user@domain (if DNS is configured and the DNS name is specified as Local SMTP Server) in the e-mail messages. "NOTE" : The local SMTP server may require that you use a valid user account on the server for this setting. See the servers documentation. |
E-mail Recipients
Path: Administration > Notification > E-mail > recipients
Identify up to four e-mail recipients.
| Setting | Description |
|---|---|
| To Address | The user and domain names of the recipient. To use e-mail for paging, use the e-mail address for the recipients pager gateway account (for example, myacct100@skytel.com). The pager gateway will generate the page. To bypass the DNS lookup of the mail servers IP address, use the IP address in brackets instead of the e-mail domain name. For example use jsmith@[xxx.xxx.x.xxx] instead of jsmith@company.com. This option is useful when DNS lookups are not working correctly. "Note" : The recipients pager must be able to use text-based messaging. |
| E-mail Generation | Enables (by default) or disables sending e-mail to the recipient. |
| SMTP Server | Select one of the following methods for routing e-mail: "Local" : Through the NMCs SMTP server. This setting (recommended) ensures that the e-mail is sent before the NMCs 20-second time-out, and, if necessary, is retried several times. Also do one of the following: - Enable forwarding at the NMCs SMTP server so that the NMC can route e-mail to external SMTP servers. Typically, SMTP servers are not configured to forward e-mail. Check with the administrator of your SMTP server before changing the NMC configuration to allow forwarding. - Set up a special e-mail account for the NMC to forward e-mail to an external mail account. "Recipient" : Directly to the recipients SMTP server. With this setting, the NMC tries to send the e-mail only once. On a busy remote SMTP server, the time-out may prevent some e-mail from being sent. When the recipient uses the NMCs SMTP server, this setting has no effect. |
| Format | The long format contains Name, Location, Contact, IP address, serial number of the device, date and time, event code, and event description. The short format provides only the event description. |
| Language | Choose a language from the drop-down list and any mails will be sent in that language. Use of different languages is possible for different users. |
| User Name Password Confirm Password | If your mail server requires authentication, type your user name and password here. This step performs a simple authentication, not SSI. |
E-mail Test
Path: Administration>Notification>E-mail>test
Send a test message to a configured recipient.
SNMP Traps
Trap Receivers
Path: Administration > Notification > SNMP Traps > trap receivers
View trap receivers by NMS IP/Host Name. You can configure up to six trap receivers.
- To configure a new trap receiver, click "Add Trap Receiver".
- To modify or delete a trap receiver, first click the receiver IP address or host name to access the settings. (If you delete a trap receiver, all notification settings configured under Event Actions for the deleted trap receiver are set to the default values.)
- To specify the trap type for a trap receiver, select either the SNMPv1 or SNMPv3 radio button. For an NMS to receive both types of traps, configure two trap receivers for that NMS, one for each trap type.
| Item | Definition |
|---|---|
| Trap Generation | Enable (the default) or disable trap generation for this trap receiver. |
| NMS IP/Host Name | The IPv4/ IPv6 address or host name of this trap receiver. The default, 0.0.0.0, leaves the trap receiver undefined. |
| Language | Choose a language from the drop-down list. This option can differ from the UI and from other trap receivers. |
SNMPv1 Option
| Item | Definition |
|---|---|
| Community Name | The name (public by default) used as an identifier when SNMPv1 traps are sent to this trap receiver. |
| Authenticate Traps | When this option is enabled (the default), the NMS identified by the NMS IP/Host Name setting will receive authentication traps (traps generated by invalid attempts to log on to this device). To disable this ability, unmark the check box. |
SNMPv3 Option
Select the identifier of the user profile for this trap receiver. (To view the settings of the user profiles identified by the user names selectable here, choose "Network" on the top menu bar and "user profiles" under "SNMPv3" on the left navigation menu.)
ReferenceRefer to the "SNMPv3" section in this chapter for information on creating user profiles and selecting authentication and encryption methods.
SNMP Trap Test
Path: Administration > Notification > SNMP Traps > test
Last Test Result
The result of the most recent SNMP trap test. A successful SNMP trap test verifies only that a trap was sent, the test does not verify that the trap was received by the selected trap receiver. A trap test succeeds if all of the following are true:
- The SNMP version (SNMPv1 or SNMPv3) configured for the selected trap receiver is enabled on this device.
- The trap receiver is enabled.
- If a host name is selected for the To address, that host name can be mapped to a valid IP address.
To
Select the IP address or host name to which a test SNMP trap will be sent. If no trap receiver is configured, a link to the "Trap Receiver" configuration page is displayed.
Remote Monitoring Service
Path: Administration > Notification > Remote Monitoring
The Remote Monitoring Service (RMS) is an optional service that monitors your system from a remote operation center 24 hours a day, 7 days a week, and notifies you of device and system events.
Registration
To activate RMS for the NMC, select "Enable Remote Monitoring Service", choose between "Register Company and Device" and "Register Device Only", complete the form, and click "Send RMS Registration".
Use the "Reset Remote Monitoring Service Registration" check box to discontinue the service, whether permanently or temporarily (for example, if you are moving an NMC).
Syslog
Path: Logs > Syslog > options
The NMC can send messages to up to four Syslog servers when an event occurs. The Syslog servers record events that occur at network devices in a log that provides a centralized record of events.
Identifying Syslog Servers
Path: Logs > Syslog > servers
| Setting | Definition |
|---|---|
| Syslog Server | Uses IPv4/ IPv6 addresses or host names to identify from one to four servers to receive Syslog messages sent by the NMC. |
| Port | The user datagram protocol (UDP) port that the NMC will use to send Syslog messages. The default is 514, the UDP port assigned to Syslog. |
| Protocol | Choose between UDP and TCP. |
| Language | Choose the language for any Syslog messages. |
Syslog Settings
Path: Logs > Syslog > settings
| Setting | Definition |
|---|---|
| Message Generation | Enables (by default) or disables the Syslog feature. |
| Facility Code | Selects the facility code assigned to the NMCs Syslog messages (User, by default). NOTE : User best defines the Syslog messages sent by the NMC. Do not change this selection unless advised to do so by the Syslog network or system administrator. |
| Severity Mapping | Maps each severity level of NMC or Environment events to available Syslog priorities. Changing the mappings should not be needed. The following definitions are from RFC3164: "Emergency" : The system is unusable "Alert" : Action must be taken immediately "Critical" : Critical conditions "Error" : Error conditions "Warning" : Warning conditions "Notice" : Normal but significant conditions "Informational" : Informational messages "Debug" : Debug-level messages Following are the default settings for the "Local Priority" settings: "Severe" is mapped to "Critical" "Warning" is mapped to "Warning" "Informational" is mapped to "Info" NOTE: To disable Syslog messages, refer to the "Configuring Event Actions" section of this chapter. |
Syslog Test and Format Example
Path: Logs > Syslog > test
Send a test message to the Syslog servers configured through the servers option.
- Select a severity to assign to the test message.
- Define the test message, according to the required message fields
- The priority (PRI): the Syslog priority assigned to the messages event, and the facility code of messages sent by the NMC.
- The Header: a time stamp and the IP address of the NMC.
- The message (MSG) part:
- The TAG field, followed by a colon and space, identifies the event type.
- The CONTENT field is the event text, followed (optionally) by a space and the event code.
For example, "Test Syslog" is valid.
- The TAG field, followed by a colon and space, identifies the event type.