Core MIB

SNMP Agent MIB Reference

tuxTsrvrState

Syntax

INTEGER { active(1) |inactive(2) |migrating(3) |cleaning(4) |
restarting(5) |suspended(6) | partitioned(7) |dead(8) | invalid(10) }

Access

read-write

Description

The values for GET and SET operations are as follows:

A GET operation retrieves configuration and run-time information for the selected tuxTsrvrTbl instance(s). The following states indicate the meaning of a tuxTsrvrState returned in response to a GET request. States not listed are not returned.

active(1)

tuxTsrvrTbl instance is defined and active. The active(1) state is not an indication of whether the server is idle or busy. An active server with a non-0 length tuxTsrvrCurService object should be interpreted as a busy server, that is, one that is processing a service request.

inactive(2)

tuxTsrvrTbl instance is defined and inactive.

migrating(3)

tuxTsrvrTbl instance is defined and currently in a state of migration to the server group's secondary logical machine. The secondary logical machine is the one listed in tuxTgroupLMID object that does not match the tuxTgroupCurLMID object.

cleaning(4)

tuxTsrvrTbl instance is defined and currently being cleaned up after by the system due to an abnormal death. Note that restartable servers can enter this state if they exceed tuxTsrvrMaxgen starts/restarts within their tuxTsrvrGrace period.

restarting(5)

tuxTsrvrTbl instance is defined and currently being restarted by the system due to an abnormal death.

suspended(6)

tuxTsrvrTbl instance is defined and currently suspended, pending shutdown.

partitioned(7)

tuxTsrvrTbl instance is defined and active; however, the machine where the server is running is currently partitioned from the tuxTdomainMaster site.

dead(8)

tuxTsrvrTbl instance is defined, identified as active in the bulletin board, but currently not running due to an abnormal death. This state exists only until the BBL local to the server notices the death and takes action (restarting(5)|cleaning(4)).

SET: {active(1)|inactive(2)|dead(8)|invalid(10)}

A SET operation updates configuration and run-time information for the selected tuxTsrvrTbl instance. The following states indicate the meaning of a tuxTsrvrState set in a SET request. States not listed cannot be set.

active(1)

Activate the tuxTsrvrTbl instance. State change is allowed only when the server is in the inactive(2) state. (Servers in the migrating(3) state must be restarted by setting the tuxTgroupState to active(1).) Successful return leaves the object in the active(1) state.

inactive(2)

Deactivate the tuxTsrvrTbl instance. State change is allowed only when the server is in the active(1) state. Successful return leaves the object in the inactive(2) state.

dead(8)

Deactivate the tuxTsrvrTbl instance by sending the server a SIGTERM signal followed by a SIGKILL signal if the server is still running after 20 seconds. Note that by default, a SIGTERM signal causes the server to initiate orderly shutdown and the server becomes inactive even if it is restartable. If a server is processing a long running service or has chosen to disable the SIGTERM signal, then SIGKILL can be used and is treated by the system as an abnormal termination. State change is allowed only when the server is in the active(1) or suspended(6) state. Successful return leaves the object in the inactive(2), cleaning(4), or restarting(5) state.

invalid(10)

Delete tuxTsrvrTbl instance for application. State change is allowed only when the server is in the inactive(2) state. Successful return leaves the object in the invalid(10) state.