Core MIB

SNMP Agent MIB Reference

tuxTmachineState

Syntax

INTEGER { active(1) | inactive(2) | partitioned(3) | invalid(4) | 
re-activate(5) | cleaning(7) }

Access

read-write

Description

The values for GET and SET operations are as follows:

GET: {active(1)|inactive(2)|partitioned(3)}

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

active(1)

tuxTmachineTable instance defined and active (administrative servers, that is, DBBL, BBL, and BRIDGE).

inactive(2)

tuxTmachineTable instance defined and inactive.

partitioned(3)

tuxTmachineTable instance defined, listed in accessible bulletin boards as active, but currently unreachable.

SET: {active(1)|inactive(2)|invalid(4)|re-activate(5)|cleaning(7)}

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

active(1)

Activate the tuxTmachineTable instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site as well as application servers configured to run on that site. State change is allowed only when the machine is in the inactive(2) state. Successful return leaves the object in the active(1) state.

inactive(2)

Deactivate the tuxTmachineTable instance. Necessary administrative servers such as the BBL and BRIDGE are stopped on the indicated site as well as application servers running on that site. State change allowed only when the machine is in the active(1) state and when no other application resources are active on the indicated machine. Successful return leaves the object in the inactive(2) state.

invalid(4)

Delete tuxTmachineTable instance for application. State change is allowed only when the machine is in the inactive(2) state. Successful return leaves the object in the invalid(4) state.

re-activate(5)

Activate the tuxTmachineTable instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site. State change is allowed only when the machine is in either the active(1) or inactive(2) state. Successful return leaves the object in the active(1) state.

cleaning(7)

Initiate cleanup/scanning activities on and relating to the indicated machine. If there are dead clients or servers on the machine, they are detected at this time. If the machine has been partitioned from the application master site, then global bulletin board entries for that machine are removed. This combination is allowed when the application is in the active(1) state and the tuxTmachineTable instance is in either the active(1) or partitioned(3) state. Successful return for a non-partitioned machine leaves the state unchanged. Successful return for a partitioned machine leaves the object in the inactive(2) state.

Note: State change to inactive(2) is allowed only for non-master machines. The master site administrative processes are deactivated through the tuxTdomain group.