Infoblox Uptime Test

In most production environments, it is essential to monitor the uptime of critical network devices in the infrastructure. By tracking the uptime of each of the devices, administrators can determine what percentage of time a device has been up. Comparing this value with service level targets, administrators can determine the most trouble-prone areas of the infrastructure.

In some environments, administrators may schedule periodic reboots of their devices. By knowing that a specific device has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a device.

This Infoblox Uptime test monitors the uptime of critical network devices.

Target of the test : An Infoblox appliance

Agent deploying the test : An external agent

Outputs of the test : One set of results for the Infoblox appliance that is to be monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the Infoblox appliance for which this test is to be configured.

Timeout

Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 60 seconds.

Is Debug Enabled

By default, this flag is set to No. If you wish to obtain troubleshooting logs for this test, then, set this flag to Yes. The troubleshooting log with the naming convention <Component Name_Internal name of the test>.log will be created in the <eG_INSTALL_DIR>\agant\logs folder once the test starts reporting metrics.

Report Manager Time

By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the device in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running (i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Has the system been rebooted?

Indicates whether/not the system had rebooted.

 

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the reboot status of the Infoblox. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.

Total uptime of the system

Indicates the total time that the appliance has been up since its last reboot.

Minutes

This measure displays the number of years, months, days, hours, minutes and seconds since the last reboot. Administrators may wish to be alerted if a server has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.

Uptime during the last measure period

Indicates the time period that the server has been up since the last time this test ran.

Seconds

If the device has not been rebooted during the last measurement period and the agent has been running continuously, this value will be equal to the measurement period. If the server was rebooted during the last measurement period, this value will be less than the measurement period of the test. For example, if the measurement period is 300 secs, and if the server was rebooted 120 secs back, this metric will report a value of 120 seconds. The accuracy of this metric is dependent on the measurement period - the smaller the measurement period, greater the accuracy.

Is under maintenance?

Indicates whether/not the system is under maintenance.

 

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the above-mentioned Measure Values while indicating whether the device is under maintenance or not. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.