Applies To:

Show Versions Show Versions

Manual Chapter: Using Alerts
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

With Enterprise Manager as your network management appliance, you can create alerts to help you better maintain the health of your network. For example, you can create custom system alerts to notify you or others if a device becomes unreachable by Enterprise Manager, upon completion or failure of a software or hotfix installation, or if a device system clock differs from the Enterprise Manager clock.
You can apply alerts to individual devices, or to a device list. You can also create alerts for the Enterprise Management device itself, so that you can maintain the health of your management system.
Enterprise Manager can take actions on a wide variety of alerts that you can use in managing your F5 Networks® devices. The alerts that you can set include:
For systems that support statistics collection, you can create statistics data threshold alert instances for which you can specify how long a statistic is out of range before the system triggers an alert.
Important: Statistical data threshold alerts are available only for statistics stored locally on the Enterprise Manager system.
When you manage redundant systems, Enterprise Manager monitors the Active or Standby state of each peer device. The status icon in the Device list corresponds to the active/standby state of a device. When the status changes, the corresponding icon changes. However, if you want to immediately notify a user as soon as the active/standby status of a managed device changes, you can configure an alert.
If you take a device offline, or force it offline, the status icon in the Device list reflects those changes. However, if you want to immediately notify a user as soon as the offline or forced offline status of a managed device changes, you can figure an alert.
When Enterprise Manager cannot properly collect all configuration data from a device, but can still communicate with the device, the system changes the device status to Impaired.
For example, if you have an extremely long pool name, Enterprise Manager may truncate this name in its database. This does not affect the pool on the managed device, but it does affect how the pool is presented in Enterprise Manager. You can still perform management tasks on the device, however, because the configuration is not completely represented, the device status is marked Impaired.
You can create an alert that immediately notifies a user if the status of a managed device changes to Impaired so that the user can correct the situation.
If Enterprise Manager loses the connection to a managed device, the status icon in the Device list changes to indicate this problem.
Because Enterprise Manager authenticates itself to managed devices on the iControl port through a certificate that it creates when it first discovers a device in the network, there are a variety of reasons for a device to be unreachable. For example, the connection could be interrupted if the managed device is rebooting, or if someone closed the management port, or removed the management cable. It is also possible that a system clock differential between Enterprise Manager and a managed device caused the management certificate to expire.
In addition to monitoring the Device list, you can create an alert to send a notification when a device is unreachable, so the alert recipients can get the managed device back online. When configured, the system checks the connection every 10 minutes and triggers an alert if the device is unreachable.
Note: The device refresh interval takes precedence over the continuous checking done by this alert. That is, if the refresh interval is set higher than 10 minutes, this alert checks for a connection within the refresh interval.
Enterprise Manager can help you easily monitor certificates defined on managed devices in your network. In addition to providing a broad overview of device certificates in the certificate list, you can also create a certificate expiration alert to trigger when a certificate expires or is within a specific number of days of expiration.
When you define an alert for certification expiration, you can specify how many days in advance that you are notified, before the certificate expiration date occurs. We recommend that you select all possible thresholds for the alert (14 days, 7 days, 3 days, and 1 day from expiration) to ensure that you receive as many reminders as possible prior to certificate expiration.
When you start a software upgrade, hotfix installation, or attack signature installation task, you may not be able to monitor the status of the task. For example, if you start an upgrade on multiple devices, it may not be feasible to manually check to see if a particular device is upgraded.
In addition to viewing all tasks from the Task List and detailed information in the Task Properties screen to monitor progress, you can also create an software install completion or attack signature install completion alert to notify you or others when a specific device completes an upgrade or installation task.
When performing an upgrade, hotfix installation, or attack signature installation task on several devices, you may not be able to closely monitor each job. For example, if you start an upgrade on multiple devices, you may not be able to manually check to see if a particular installation or upgrade failed.
In addition to viewing all tasks from the Task List Screen and detailed information in the Task Properties screen to monitor progress, you can also create a software install failure or attack signature install failure alert to notify you or others if an upgrade or installation job fails. The user who receives the alert email can then investigate why the upgrade or installation failed, make corrections, and schedule a new task.
When Enterprise Manager adds a device to its managed Device list, it creates a certificate that it uses to authenticate itself to the managed device. If the system clock of Enterprise Manager and the managed device are not synchronized within 15 minutes of each other, the management certificate becomes invalid. An invalid certificate on a device can result in Enterprise Manager losing management privileges for that device.
To prevent this scenario, you can set a clock skew alert that checks the system clocks every 10 minutes and sends a notification if the Enterprise Manager and managed device system clocks are out of synch by a specific number of minutes. Then, the user who receives the alert can log on to the managed device and correct the system clock.
When you configure a rotating archive schedule, Enterprise Manager creates a device configuration at the interval you specified. Because this is an automated process, you may not know if the configuration archive was created properly.
You can create a rotating archive failure alert to notify you or others whenever a scheduled configuration archive process encounters an error. A user who receives an alert email can investigate why an archive was not created, or can manually create a configuration archive.
When you create alerts, you can specify delivery options for that alert. You can also set a certain recipients email address, or a remote syslog server, to receive notifications for all alerts by default. Once these are set, Enterprise Manager sends alert notifications to the default email address you specified, or to the remote syslog server, unless the alert is configured to notify another recipient. For information about for enabling alerting features, such as setting alert default options, and sending email messages or SNMP traps, see the Enterprise Manager Getting Started Guide.
To help maintain the health of the Enterprise Manager device, you can create system alerts to notify you when CPU, disk, or memory usage meets or exceeds a particular threshold.
Important: To successfully send alerts, Enterprise Manager must be configured to deliver locally generated email messages. For more information, see the Enterprise Manager Getting Started Guide.
1.
On the Main tab, expand Enterprise Management, and click Alerts.
The Device Alerts list screen opens.
2.
On the menu bar, click EM Alerts.
The EM Alerts screen opens.
3.
For the Conditions setting, select the check boxes for the metrics that you want to track with alerts.
The screen refreshes to display threshold fields for the conditions you selected.
5.
In the EM Alert Action area, for Action, select the type of action that you want Enterprise Manager to take when the values you specified for the thresholds are met or exceeded.
6.
Click Save Changes.
Note: Because the CPU or memory usage may spike repeatedly during certain Enterprise Management tasks, many alerts may be triggered, which could result in multiple emails, SNMP traps, syslog events, or alert history entries.
Creating an alert for a device or device list involves naming the alert, defining the alert condition, setting the alert action, and assigning the alert to one or more devices. You can do this from the New Alert screen.
1.
On the Main tab, expand Enterprise Management, click Alerts, and select Device Alerts.
The Device Alerts list screen opens.
2.
Above the alert list, click Create.
The New Alert screen opens.
3.
In the Name field, type a name for the alert, as you want it to appear in the Device Alerts screen.
Note: Once you create the alert, you cannot change the name.
4.
From the Alert Type list, select the alert condition.
Depending on the type you select, the screen may change to provide additional options.
5.
If the alert type requires a threshold, for the Condition setting, specify a threshold value.
6.
For the Action setting, select the check box next to each action that you want Enterprise Manager to take when the alert is triggered.
7.
If you selected the option to send an email, then for Email Recipient, you can use the default email recipient, or type the email address of a specific user:
To send an email to the default email recipient listed on the Alert Options screen, select the check the box next to the email.
8.
If you selected the option to log a remote syslog event, then for Syslog Server Address, you can use the default syslog server address, or type the server address of a different remote server:
To log an event on the default syslog server listed on the Alert Options screen, select the check box next to the default syslog server.
To log an event on an alternate server, clear the check box and type a new syslog server address in the field.
a)
For either the Devices or Device List setting, click a device or device list in the Available box to select it.
b)
Click the Move button (<<) to move the selected devices or device lists to the Assigned box.
10.
Click Finished.
The Device Alerts screen opens, and the new alert appears in the list.
The flexibility of alerts allows you to easily apply or remove existing alerts for specified devices or device lists. You can also change the alert actions or email recipients for an alert. From the Device Alerts screen, click the name of an alert to open the Alert Properties screen.
1.
On the Main tab, expand Enterprise Management, click Alerts, and select Device Alerts.
The Device Alerts list screen opens.
3.
Change any of the values in the Configuration, or add or remove devices and groups from the alert in the Alert Assignments area.
4.
Click Save Changes.
If you no longer need an alert, you can delete the alert using the Device Alerts screen. Once you remove an alert from the alert list, it no longer applies to any devices or groups that you assigned.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)