Uptime – Zone Test

This test monitors the uptime of every zone on a Solaris virtual server.

Target of the test : A Solaris virtual server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every zone executing on the Solaris virtual server.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port number at which the specified host listens. By default, the port is NULL.
Connect Using	By default, this parameter is set to sudo. This indicates that, by default, this test uses the sudo command to connect to the Solaris virtual server and pull out metrics. If you want the test to use the pfexec command instead, select the pfexec option from the Connect Using drop-down.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Has system been rebooted	Indicates whether the zone has been rebooted during the last measurement period or not.	Boolean	If this measure shows 1, it means that the zone was rebooted during the last measurement period. By checking the time periods when this metric changes from 0 to 1, an administrator can determine the times when this zone was rebooted.
Uptime during the last measure period	Indicates the time period that the zone has been up since the last time this test ran.	Secs	If the zone 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 zone 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 zone 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.
Total uptime of the system	Indicates the total time that the zone has been up since its last reboot.	Mins	Administrators may wish to be alerted if a zone has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.

Note:

If a value less than a minute is configured as the test period of the Uptime - Zone test, then, the Uptime during the last measure period measure will report the value 0 for the zones until the minute boundary is crossed. For instance, if you configure the Uptime - Zone test to run every 10 seconds, then, for the first 5 test execution cyles (i.e., 10 x 5 = 50 seconds), the Uptime during the last measure period measure will report the value 0 for all zones; however, the sixth time the test executes (i.e, when test execution touches the 1 minute boundary), this measure will report the value 60 seconds for the zones. Thereafter, every sixth measurement period will report 60 seconds as the uptime of the zones. This is because, Unix-based operating systems report uptime only in minutes and not in seconds.