Managing ZENworks for Servers 3 Alarms

Now that you understand the components that make up the ZENworks for Servers 3 alarm management system, you need to know how to begin managing alarms on your network. Alarm management is a process of enabling alarms, then monitoring for alarm conditions, handling the alarm situations, and deleting the alarms.

The following sections describe how to use the ZENworks for Servers 3 management console to enable alarms, disable alarms, understand alarm indicators, work with alarm views, manage alarms, perform actions on the alarms, and then remove alarms from the system.

Enabling and Disabling Alarms

The first task you must be familiar with when managing the ZENworks for Servers 3 alarm management system is how to enable and disable alarms. Alarm thresholds are associated with each managed server and segment. When an alarm threshold is exceeded, an alarm is generated.

Although server threshold alarms are enabled by default, segment threshold alarms are not. You need to use the ZENworks for Servers 3 management console to enable and configure the threshold alarms for your network.

Follow these steps in the management console to enable and disable the alarms for your managed servers and segments to best match your needs:

  1. Select the server or segment object for which you want to enable or disable alarms.

  2. Right-click the object and select Properties from the pop-up menu.

  3. Select the Segment Alarms property tab, shown in Figure 11.1.

    Figure 11.1. Segment Alarms property tab for a segment object in ConsoleOne.

    graphics/11fig01.gif

  4. Select the alarm you want to modify.

  5. Click the Edit button and an Edit Alarm dialog box appears.

  6. Select Enable to enable the alarm or Disable to disable the alarm.

  7. If you are enabling an alarm, set the threshold value.

  8. If you are enabling an alarm, you should also set the amount of time in the Sampling Interval field by which the threshold value must be exceeded to generate the alarm.

  9. Click OK to save your alarm setting and return to the Segment Alarms property tab.

Understanding Alarm Indicators

After enabling, disabling, and configuring the alarm thresholds for the managed servers and segments on you network, ZENworks for Servers 3 starts tracking, storing, and relaying network alarms as they occur. At this point, you need to become familiar with the different alarm indicators so that you can recognize and respond to the alarms as they occur.

The following sections discuss the different indicators that you can watch for when alarms are triggered on your network.

About Alarm Icons Anchored to the Affected Object

Alarms that are triggered with a critical, major, or minor severity are displayed in the ZENworks for Servers 3 management console in both the Atlas and Console views. When an alarm is triggered on a segment or server that is being managed by the ZENworks for Servers 3 alarm management system, an Alarm icon is anchored to the object. Therefore, as you browse through the ZENworks for Servers 3 namespace, watch out for Alarm icons.

Discussing the Ticker Tape Message on the Status Bar

You can also configure the ZENworks for Servers 3 alarm management system to display alarm messages on the management console's status bar. This option is on by default. If this option is on, the alarm management system displays a descriptive message on the status bar as it recognizes that an alarm has been triggered. This is another thing that you should keep an eye out for. The messages let you know which object is affected so that you can quickly find the problem and resolve it.

Information About the Audible Beep

The final alarm indicator is an audible beep that is sent to the management console. The alarm management system can be configured to force an audible beep on the management console when an alarm occurs. This is very useful if you are not actively browsing or looking for alarms. If you hear a beep on the management console, look for the Alarm icon on your server or segment objects and investigate the alarm.

Working with Alarm Views

Now that you understand the alarm indicators for which you should look and listen, you need to know how to use the views provided with ZENworks for Servers 3 to monitor and manage alarms. The ZENworks for Servers 3 management console gives you access to both active and historical data about alarms that are occurring or have occurred on your network.

You can define access restrictions to alarm data and management functions through ZENworks for Servers 3 role-based services. You can also modify the presentation of the alarm data displayed in the views by sorting and filtering on specific data elements.

The following sections discuss the different alarm views provided with ZENworks for Servers 3 and how to use them to monitor and manage alarms.

Monitoring Active Alarms

Active alarms are typically the most important type of alarm that you will encounter. Active alarms indicate that a problem is currently happening on either a monitored segment or a server. The ZENworks for Servers 3 Active Alarm view, shown in Figure 11.2, displays the following alarm statistics for all current alarms for the managed site.

  • Severity. Displays an Alarm icon that is color coded to indicate the level of alarm severity: Red = Critical, Magenta = Major, Yellow = Minor, Blue = Informational, and White = Unknown.

  • From. Specifies the network address of the device that sent the alarm to the alarm management system.

  • Summary. Displays a summary of the alarm event, including names, addresses, and other information about the alarm.

  • Owner. Specifies the person or group that is responsible for handling the alarm. SYSTEM is specified until an owner is set.

  • Received Time. Displays the date and time when the alarm management system received the alarm.

  • Type. Specifies the alarm's generic type description.

  • Category. Specifies the category of the trap-type object, identified from its MIB association.

Figure 11.2. Active Alarm view for a ZENworks for Servers site management object in ConsoleOne.

graphics/11fig02.jpg

For each of the alarms, the ZENworks for Servers 3 Active Alarm view displays the following alarm-specific data for the selected alarm (see Figure 11.2):

  • Alarm ID. Displays the alarm's object ID in the Alarm Manager database.

  • Alarm state. Displays the alarm's current status. This tells you whether the alarm is currently operational or not.

  • Alarm severity. Displays the alarm's severity: Severe, Major, Minor, Informational, or Unknown.

  • Generator Type. Displays the type of agent that activated the alarm.

  • Alarm category. Displays the category of the trap-type object, identified from its MIB association.

  • Alarm type. Displays the alarm's generic type description.

  • Source Address. Displays the address of the device that triggered the alarm.

  • Received at. Displays the time at which the alarm management system received the alarm from the agent.

  • Summary. Gives a descriptive summary of the alarm. This is one of the most useful statistics because the descriptions include node names and specific data about the alarm's nature.

  • Number of Variables. Lists the number of variables associated with the alarm.

Follow these steps from within the ZENworks for Servers 3 management console to access the Active Alarm view:

  1. Select the ZENworks for Servers 3 site object.

  2. Select View Active Alarms from the main menu in ConsoleOne. The Active Alarm view appears, as shown in Figure 11.2.

Displaying Alarm History

In addition to the currently active alarms, ZENworks for Servers 3 also enables you to view data about all archived alarms that have occurred on the network. The Alarm History view is very similar to the Active Alarm view. But the Alarm History view includes a Handled status field, shown in Figure 11.3, in addition to the same information about the alarms.

Figure 11.3. Alarm History view for a ZENworks for Servers 3 site management object in ConsoleOne.

graphics/11fig03.jpg

Follow these steps from within the ZENworks for Servers 3 management console to access the Alarm History view:

  1. Select the ZENworks for Servers site object.

  2. Select View Alarms History from the main menu in ConsoleOne. The Alarm History view appears, as shown in Figure 11.3.

Sorting Alarms

After bringing up either the Active Alarm or the Alarm History view on the management console, you can change the look of the view by sorting the alarms according to a specific criterion. This enables you to tailor the view to meet the needs of the problem you are trying to resolve or a report that you need to prepare.

The following list includes the most common criteria on which you may want to sort alarms and examples of when to use them:

  • Received Time. Received time is the default sort order. This enables you to see the alarms in the chronological order that they occurred. This is the most useful view in understanding the initial status of the network and when problems started occurring.

  • From. Sorting using From enables you to focus on the specific server or node that triggered the alarm. This is most useful when you are troubleshooting a server or router issue.

  • Severity. Sorting according to the severity enables you to focus on a specific level of error. Typically, you sort according to severity when you want to see only the most severe errors that are occurring and resolve them first.

  • Category. Sorting by category enables you to focus on specific trap types identified in the MIB. This sorting enables you to focus on a specific alarm. Use this if you are troubleshooting or monitoring a specific router or server issue where you know the specific SNMP trap you are looking for.

  • Type. Sorting by type can also be very useful to troubleshoot some specific issues. If you were watching for hard drive space problems, for example, you may sort by type and bring together all the volume out of disk space alarms.

Follow these steps from within the ZENworks for Servers 3 management console to sort the Active Alarm or the Alarm History view:

  1. Open the alarm view you want to sort.

  2. Select View Settings Sort from the main menu in ConsoleOne.

  3. From the Alarm Sorting dialog box, shown in Figure 11.4, select the criteria by which you want the alarms to be sorted.

    Figure 11.4. Alarm Sorting dialog box for a ZENworks for Servers 3 site management object in ConsoleOne.

    graphics/11fig04.jpg

  4. Select the sort order: Ascending or Descending.

  5. Click OK to save your setting. The alarm view should be sorted according to your selections.

Filtering Alarms

ZENworks for Servers 3 also enables you to filter on alarms according to specific criteria after you bring up either the Active Alarm or the Alarm History view on the management console. This gives you even greater control to customize the view to meet more specific needs of the problems you are trying to resolve or reports that you need to prepare.

Table 11.1 shows the available criteria and options that you may want to use to filter alarms in the Active Alarm or Alarm History view.

Table 11.1. Criteria Available on Which to Filter Alarm Views

CRITERIA

OPERATORS

VALUES

Severity

=(equals), !=(does not equal), > or <

SEVERE, MAJOR, MINOR, INFORMATIONAL.

Generator typ

=(equals) or !=(does not equal)

Only SNMP (unless you have additional alarm generator types on your network).

Alarm category

=(equals) or !=(does not equal)

Any one of the alarm categories available in the MIB that is, Antivirus-MIB, LANDesk-Alarm-MIB, NetWare-Server-Alarm-MIB, and so on.

Alarm type

=(equals) or !=(does not equal)

Any one of the alarm types provided on the alarm system that is, Threshold cache buffers, System: Trap NLM Loaded, and so on.

Source address

=(equals) or !=(does not equal)

IP address of the source on which to filter. This enables you to filter on a specific device.

From

=(equals), !=(does not equal), contains, starts with, or ends with

Full distinguished name of a ZENworks for Servers 3 management site server. This lets you filter on a single site if you are using site forwarding.

Alarm owner

=(equals), !=(does not equal), contains, starts with, or ends with

Full distinguished name of a user or group that is responsible for alarms. This could be used to view the alarms that you are currently responsible for.

Alarm summary

=(equals), !=(does not equal), contains, starts with, or ends with

Any text string that may equal, start, end, or be contained in the alarm summary string. If you were looking at lost connection issues, for example, you could filter on Lost Connection and use the contains operator.

Follow these steps from within the ZENworks for Servers 3 management console to filter the Active Alarm or the Alarm History view:

  1. Bring up the view that you want to filter.

  2. Select View Settings Filter from the main menu in ConsoleOne. The Alarm Filter dialog box, shown in Figure 11.5, appears.

    Figure 11.5. Alarm Filter dialog box for a ZENworks for Servers 3 site management object in ConsoleOne.

    graphics/11fig05.jpg

  3. Select the criteria by which you want the alarm management system to filter alarms from the drop-down list on the left.

  4. Select an appropriate operator, from Table 11.1, to use from the next drop-down list.

  5. Select an appropriate value from the third drop-down list, or specify a value if one is not provided.

  6. Specify how this specific filter relates to other statements you want to define. You can use the AND, OR, new row, delete row, and new group relationship criteria. This enables you to add multiple filters and groups of filters to the alarm view, as shown in Figure 11.5.

  7. If you defined relationship criteria in Step 6, repeat Steps 3 through 6.

  8. When you finish specifying filters, click the OK button. The filter is saved and the view is adjusted according to your criteria.

Viewing Alarm Summary

ZENworks for Servers 3 enables you to view a summary of the alarms for a managed site. The Alarm Summary view provides you with concise but complete data about the alarms that have occurred on your network over the past day, week, or month.

The following list breaks down the information displayed in the Alarm Summary view shown in Figure 11.6:

  • Severity Disposition. Displays a pie chart breaking out the alarms based on their severity. This information is useful to find out how many critical alarms your network is seeing. You can, for example, view this in terms of days, weeks, and months to determine whether your network is getting healthier or sicker.

  • Category Disposition. Displays a pie chart breaking out the alarms based on the alarms category. This information is useful to help you understand where your network may need to grow or where problems need to be resolved.

  • Owner Disposition. Displays a pie chart breaking out the alarms based on the owner of the service that triggered the alarm. This information is useful for helping you know where to begin troubleshooting issues.

  • State Disposition. Displays a pie chart that breaks down the alarms based on the state that they are in. This information helps you understand the duration of the alarms on your network. If the active state, for example, is the majority of the pie chart, you know that the alarms are active much of the time and the issues are much more severe.

  • Top Alarm Types. Displays a bar graph of the alarms that are triggered most often. This information helps determine which services are being affected most on your network.

  • Top Affected Nodes. Displays a bar graph of the nodes where alarms are triggered most often. This information helps determine which nodes and/or segments need the most attention in terms of growth and optimization.

  • Top Source Address. Displays a bar graph of the network addresses where alarms are triggered most often. This information enables you to understand on what segments, routers, and so on problems are occurring.

  • Arrival Rate. The arrival rate is a line graph that shows the number of active alarms based on a time interval. The arrival rate shows you the number of alarms that are active at any given time. This information is extremely useful to understand network issues that have to do with time. If you are getting numerous alarms at the same time in the morning, for example, you can look at when employees are arriving at work and logging in to the network. You may need additional hardware to handle the morning login or perhaps stagger the time employees can log in to the network.

Figure 11.6. Alarm Summary view for a ZENworks for Servers 3 site management object in ConsoleOne.

graphics/11fig06.jpg

The Alarm Summary page enables you to use the following options from the Alarm Summary view to customize what data is displayed:

  • Select Interval. The Select Interval drop-down menu enables you to view data collected from the last day, week, or month. This information is extremely important in giving you an understanding of how the network's status changes over a period of time.

  • Refresh Every. The Refresh Every check box instructs ZENworks to refresh the data every 10 seconds, 30 seconds, or 1 minute.

  • Customize. The Customize button enables you to configure what information is displayed in the Alarm Summary view. You can disable any of the statistics, and you can set the number of top alarm types, top affected nodes, and top source addresses to display in the bar graphs.

Managing Alarms

Now that you understand how to detect and view network alarms from the ZENworks for Servers 3 management console, you need to know how to manage them on large networks. This sort of management is especially important if numerous administrators are managing different aspects of the management site.

ZENworks for Servers 3 adds options to the alarm to enable you to assign, own, and handle alarms. This feature helps you keep track of who is responsible for what issues and which issues have been resolved.

After you select an alarm from the Active Alarm or the Alarm History view, you can manage the alarm by selecting one of the following options for it from the View menu in ConsoleOne:

  • Assign. The Assign option enables you to specify a person or group that is responsible for handling an alarm. When this option is set, other administrators know that they do not need to respond to it.

  • Own. When you select Own from the View menu of an alarm in ConsoleOne, the owner that is filed changes to the NDS name as which you are logged in. This lets other administrators know that you are handling this alarm. Therefore, they do not need to act on the alarm and they have a person to contact for estimated resolutions and so forth.

  • Handle. After someone has handled an alarm, you can select Handle, and the alarm is removed from the Active Alarm view. This removes the alarm from active issues that need resolving, enabling administrators to focus on current problems. But the alarm still shows up on the Alarm History view.

  • Note. You can use the Note option from the Active Alarm view menu to add any special comments or notes about the alarm. After a note has been added to an alarm, the alarm's icon changes to one with a small icon designating that the alarm has a special note attached to it. The note can be viewed in the alarm information pane when the alarm is selected.

  • Jump. You can select Jump from the Active Alarm view menu to jump directly to the object that triggered the alarm. This gives you faster access to the object to troubleshoot issues.

Setting Alarm Actions

One of the most powerful features of the ZENworks for Servers 3 alarm management system is its ability to perform actions automatically to help you manage alarms as they are triggered. You can use the ZENworks for Servers 3 management console to configure an alarm to automatically trigger an action when it occurs.

Alarm actions are configured through alarm dispositions. Follow these steps to access the Alarm Disposition page, shown in Figure 11.7, and to configure alarm actions in ConsoleOne:

  1. Select the ZENworks for Servers 3 site management object on which you want to configure alarm dispositions.

  2. Select the Alarm Disposition tab.

  3. Select the alarm you want to configure from the list.

  4. Click the Edit button to bring up the Edit Alarm Disposition dialog box.

Figure 11.7. Alarm Disposition tab for a ZENworks for Servers 3 site management object in ConsoleOne.

graphics/11fig07.jpg

ZENworks for Servers 3 has added a Sort button to the Alarm Disposition tab that enables you to define a template for ZENworks to use when sorting alarms. This capability is extremely useful to help you analyze and understand the nature of alarms that are occurring on your network. You could, for example, narrow down problem services by setting up a template to sort by the alarm type.

To set up a template to sort alarms, click the Sort button shown in Figure 11.7 to bring up the Template Sorting dialog box. From the Template Sorting dialog box you can define a sort template based on up to four of the following different criteria types:

  • Severity. Severity of the alarm.

  • Generator Type. Type of service that generated the alarm.

  • Category. The classification of the alarm.

  • Type. The specific type of the alarm.

The following sections discuss the actions to be performed when an alarm is triggered, and that are available from the Edit Alarm Disposition dialog box.

Sending Email Notification

The first available option from the Alarm Disposition dialog box is the capability to send an email notification to a user or group. It is very useful to be notified when critical alarms occur on the network.

Network administrators use this feature for various kinds of notification. Some have their SMTP mail servers configured to page them with the notification email when it is received.

Follow these steps to configure an email notification action for an alarm from the Edit Alarm Disposition dialog box in ConsoleOne:

  1. Select the SMTP Mail Notification tab, shown in Figure 11.8.

    Figure 11.8. SMTP Mail Notification tab of an alarm disposition for a site management object in ConsoleOne.

    graphics/11fig08.jpg

  2. Select the Notify through SMTP Mail option.

  3. In the SMTP Host text box, specify the IP address of the SMTP host server that handles incoming and outgoing email.

  4. In the From text box, specify the mail ID you want to use. This information is usually important for any additional automation on the back end.

  5. In the To text box, specify the mail IDs of the users or groups you want to notify when the alarm is triggered.

  6. In the Subject text box, specify the subject line you want to appear on the mail message that is sent. This information is also often important for additional automation on the back end. You can also add variables to the subject line by using a % sign in front of them. Table 11.2 lists variables that might be useful in the email Subject line.

  7. In the Message text box, specify the text message you want to appear in the body of the email that is sent. This message should include a description of what the alarm means. You can also add variables to the subject line by using a % sign in front of them. Table 11.2 lists variables that might be useful in the email body.

  8. Click the OK button to save your settings and return to the Alarm Dispositions tab.

Table 11.2. Available Variables for Use in the Subject and Message Options for SMTP Mail Notifications

VARIABLES

NAME

DESCRIPTION

a

Alarm ID

Identification number of the alarm as it is stored in the database

c

Affected Class

Class of the device that sent the alarm

o

Affected Object Number

Identification number, from the database, of the node that generated the alarm

s

Alarm Summary String

Message describing the alarm (same message that is displayed in the status bar ticker tape message)

t

Alarm Type String

Description of the alarm (same as the description in the Alarm Type element of the Alarm summary window)

v

Severity Number

Alarm severity level:

1 = Critical

2 = Major

3 = Minor

4 = Informational

Launching an Application

The next option available from the Alarm Disposition dialog box is the capability to launch an application. This option enables you to specify an NLM to be launched when an alarm is triggered on a server.

If your network utilization is too high, for example, you could launch an NLM that shuts down noncritical applications that normally consume high amounts of network bandwidth.

From the Edit Alarm Disposition dialog box in ConsoleOne, follow these steps to configure an external program to be launched when an alarm is triggered:

  1. Select the Launching Application tab, shown in Figure 11.9.

    Figure 11.9. Launching Application tab of an alarm disposition for a site management object in ConsoleOne.

    graphics/11fig09.jpg

  2. Select the Launch Application option.

  3. Specify the application path and filename in the Application Name text box.

  4. Specify any additional arguments in the Argument text box. You can use variables listed in Table 11.2 as parameters by preceding them with the % sign.

  5. Click the OK button to save your settings and return to the Alarm Dispositions tab.

NOTE

The Application Name field cannot exceed 126 characters in total length. The Argument field cannot exceed 119 characters in total length. The combined total of the Application Name and the Argument fields cannot exceed 139 characters in total length.


Forwarding the SNMP Trap

The next option available from the Alarm Dispositions dialog box is the capability to forward the SNMP trap to another management system. This option enables you to specify the IP address of another management station or server to which to forward the SNMP trap.

If you had another SNMP management system, for example, in addition to ZENworks for Servers 3, and wanted that system to receive the trap as well, you could send an SNMP trap to that management system, too.

From the Edit Alarm Disposition dialog box in ConsoleOne, follow these steps to configure an IP address to which the SNMP trap should be forwarded:

  1. Select the SNMP Trap Forwarding tab, shown in Figure 11.10.

    Figure 11.10. SMTP Trap Forwarding tab of an alarm disposition for a site management object in ConsoleOne.

    graphics/11fig10.jpg

  2. Enter the IP address of the server to which you want to forward the SNMP traps in the SNMP Target Address field.

  3. Click the Add button to add it to the list of targets.

  4. Click the OK button to save your settings and return to the Alarm Dispositions tab.

Forwarding the Alarm

The next option available from the Alarm Dispositions dialog box is the capability to forward the alarm to another ZENworks for Servers 3 management site. This option enables you to specify a ZENworks for Servers 3 management site name and hostname to which to forward the alarm.

From the Edit Alarm Disposition dialog box in ConsoleOne, follow these steps to configure another ZENworks for Servers management site to which the alarm should be forwarded:

  1. Select the Alarm Forwarding tab, shown in Figure 11.11.

    Figure 11.11. Alarm Forwarding tab of an alarm disposition for a site management object in ConsoleOne.

    graphics/11fig11.jpg

  2. Enter the ZENworks for Servers 3 management site name to which you want to forward the alarm in the Site Name field.

  3. Enter the ZENworks for Servers 3 site host name in the Site Host field.

  4. Click the Add button to add it to the list of targets.

  5. Click the OK button to save your settings and return to the Alarm Dispositions tab.

Additional Alarm Disposition Actions

The final options panel available from the Edit Alarm Disposition dialog box is the Other Configuration tab, shown in Figure 11.12. This tab enables you to configure the following actions to be performed when an alarm is triggered:

  • Archive. Stores the statistical data for the alarm instance in the Alarm Manager database on the management server. If you want to see the alarm in the Alarm History view, you need to select this option. It is on by default.

  • Show on Ticker Bar. Displays a message of the alarm on the ZENworks for Servers 3 management console status bar to silently notify the administrator of the most recent alarm.

  • Beep on Console. Sends an audible beep to the ZENworks for Servers 3 management console to notify the administrator that an alarm has been triggered.

Figure 11.12. Other Configuration tab of an alarm disposition for a site management object in ConsoleOne.

graphics/11fig12.jpg

Follow these steps to configure additional options for the alarm from the Edit Alarm Disposition dialog box in ConsoleOne:

  1. Select the Other Configuration tab (see Figure 11.12).

  2. Set the Archive option if you want to save the alarm to the Alarm Manager database.

  3. Set the Show on Ticker Bar option if you want a message to be displayed in the management console's status bar.

  4. Set the Beep on Console option if you want the alarm to send an audible beep to the management console.

  5. Click the OK button to save your settings and return to the Alarm Dispositions tab.

Deleting Alarms

The final task you need to be familiar with when managing ZENworks for Servers 3 alarms is how to remove them when you are completely finished with them. The alarms take up space in the Alarm Manager database until they are removed. If you do not consistently keep the alarms cleaned out of the database, the database can begin to take up an excessive amount of hard drive space.

The following sections discuss how to manually and automatically remove unwanted alarms from the Alarm Manager database.

Deleting Alarms from the Management Console

You can manually delete alarms from the Alarm Manager database by simply deleting them from the ZENworks for Servers 3 management console. This is the best way to delete an individual alarm. But if numerous alarms have occurred, this process could be too time-consuming. If you have numerous alarms, instead use the automatic alarm deletion method described in the next section.

Follow these steps to manually delete an alarm from the Alarm Manager database from the management console:

  1. Navigate to the server or segment object on which the alarm occurred.

  2. Open the Alarm History view to display the alarms.

  3. Select the alarm you want to delete.

  4. Select View Delete from the main menu and the alarm is deleted from the database.

Automating Alarm Deletion

The best way to handle the deletion of alarms is to automate the process by configuring the purge utility to delete the alarms for you. The purge utility is a Java application that runs on the server where the Alarm Manager database is stored.

The purge utility is controlled by a configuration file, AMPURGE.PROPERTY, which defines the criteria for selecting alarms to be purged as well as when to start purging alarms. The first step in using the purge utility to automatically delete alarms is to configure the criteria listed in Table 11.3 according to how long you need the alarms and when to start purging.

Table 11.3. Criteria for Purging Alarms Listed in the AMPURGE.PROPERTY File

CRITERIA SETTING

DESCRIPTION

SeverityInformationalPurgeWait

Specifies the number of days to wait before informational alarms are purged. The default is 7.

SeverityMinorPurgeWait

Specifies the number of days to wait before minor alarms are purged. The default is 7.

SeverityMajorPurgeWait

Specifies the number of days to wait before major alarms are purged. The default is 7.

SeverityCriticalPurgeWait

Specifies the number of days to wait before critical alarms are purged. The default is 7.

SeverityUnknownPurgeWait

Specifies the number of days to wait before unknown alarms are purged. The default is 7.

PurgeStartTime

Specifies the start time hour to begin the daily purge process. Valid values are from 0 (midnight) to 23 (11:00 p.m.).

AlarmPurgeService

Specifies whether to automatically run the purge process on a daily basis. You can specify either Yes (enable) or No (disable). Omitting this setting also disables it.

After configuring the criteria for purging alarms, you have two options. The first option is to wait for the start time that you specified the purge to begin. The second option is to manually start the purge process.

You may want to manually start the purge process because you turned off the automatic run by setting AlarmPurgeService to No, or because the database has grown too rapidly because of a network problem and you need to free up hard drive space.

Use the following command from the console of the server where the Alarm Manager database is stored to start the automatic purge process manually:

 java com.novell.managewise.am.db.purge.AutoPurgeManager  s  d <properties_file_directory> 

The properties_file_directory parameter should be replaced with the directory location where the AMPURGE.PROPERTY file is located.

NOTE

The purge process is highly memory- and CPU-intensive. Therefore, you should run the purge only during off hours or when it is truly needed for example, at night, on weekends, or if the server runs out of disk space.




Novell's ZENworks for Servers 3. Administrator's Handbook
Novell's ZENworks for Servers 3. Administrator's Handbook
ISBN: 789729865
EAN: N/A
Year: 2003
Pages: 137

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net