6.1 Monitoring Server Health

Monitoring the health of your server can help prevent it from getting to a state in which your users cannot access the server or the data on it. Monitoring your server’s health involves the following tasks:

6.1.1 Monitoring Overall Server Health or the Health of a Specific Item

Using Novell Remote Manager, you can monitor the server’s overall health and the health of a specific item.

The server’s overall health is indicated by the color of the circle displayed next to the Server icon Description: Server's health status is good in the header frame for Novell Remote Manager. The following table lists and explains each health status that might be displayed.

Table 6-1 Server Health Status

Icon

Server Health Status

Explanation

Good

All parameters included in the server's health configuration list are good.

Suspect

The status of one or more of the parameters included in the server's health configuration list is suspect or has a minor problem.

Bad

The status of one or more of the parameters included in the server's health configuration list is bad or has a critical problem.

Lost connection

The connection to the server from Novell Remote Manager has been lost.

The server’s overall health is determined by items that are selected in the Include list on the detailed Server Health page as shown in Figure 6-1. By default, all items are selected.

If the status of any item that is selected in the Include list changes to yellow (suspect) or red (bad), the health status indicator light in the header frame changes to indicate there is a problem. If more than one item changes, the worst status indicates the server’s overall status. When the status for all items returns to green (good), then the health light indicator changes back to green (good).

The server’s health status, reported by the health status indicator, is updated every five seconds, but the graphic refreshes only if the status changes.

The Server Health page shows the health status (green/good, yellow/suspect, or red/bad) for all known components of the system, as well as current, peak, and maximum values. When an item is not selected in the Include column, it is not included when determining the overall server health and the values for Status, Current, Peak, and Max are not displayed.

Figure 6-1 Server Health Page

The following items are key indicators of your server’s health:

  • CPU Utilization (for each processor, if there is more than one)
  • Process Count
  • Available Memory
  • Physical, Swap, and Virtual Memory
  • LAN Collisions

In this release, you cannot change the thresholds for the Suspect and Critical values of these indicators. See the online help for each parameter to see the set thresholds.

To access the Health Monitoring page, click one of the following links:

  • Description: Server's health status is good Overall server health status indicator icon
  • Description: Health Monitor link in the header frame Health Monitor icon in the header frame
  • Diagnose > Health Monitor link in the navigation frame

6.1.2 Configuring the Items to Monitor

As stated in the previous section, the server’s overall health is determined by items that are selected in the Include list on the detailed Server Health page. By default, all of the items are selected.

Therefore, if you have a server that has specific parameters that you know will cause a suspect or bad status and you want to be notified only when other parameters have changed, you can remove the items with the suspect or bad parameters from the Include and Notify lists by deselecting them and clicking Apply Settings.

6.1.3 Configuring E-Mail Notification for Server Health Status

Rather than manually checking the status, you can configure Novell Remote Manager to send an e-mail to notify you when the server’s health status changes to any value other than green (good).

  1. Select the Notify check box for the item on the Server Health page.

  2. Specify the required information for e-mail notification in the /etc/opt/novell/httpstkd.conf file.

    You can edit this file via the link provided on the Configuration Options page.

  3. After changing the httpstkd.conf file, restart HTTPSTKD.

    Click the Restart HTTPSTKD button on the Configuration Options page or execute the following command in a console shell on the Linux server:

    rcnovell-httpstkd restart