Skip navigation.

SNMP Agent MIB Reference

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

 


tuxTdomainState

Syntax

INTEGER { active(1) | inactive(2) | forcible-inactive(3) }

Access

read-write

Description

The values for GET and SET operations are as follows:

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

A GET operation retrieves configuration and run-time information for the tuxTdomain group. The following states indicate the meaning of a tuxTdomainState returned in response to a GET request. States not listed are not returned.

active(1)

tuxTdomain group is defined and the master machine is active.

inactive(2)

tuxTdomain group is defined and application is inactive.

SET: active(1)|inactive(2)|forcible-inactive(3)

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

active(1)

Activate administrative processes (DBBL, BBL, and so on) on the master machine. A state change is allowed only when the object is in the inactive(2) state. Successful return leaves the object in the active(1) state.

inactive(2)

Deactivate administrative processes (DBBL, BBL, and so on) on the master machine. A state change is allowed only when the object is in the active(1) state. Successful return leaves the object in the inactive(2) state. To do a complete shutdown of the application, you must first make all groups inactive. (See tuxTgroupState.) This state transition fails if any application servers or clients are still attached to the domain. To ignore any running clients or application servers, set to forcible-inactive(3) as explained below.

forcible-inactive(3)

Forcibly deactivate administrative processes (DBBL, BBL, and so on) on the master machine. Attached clients are ignored for the purpose of determining if shutdown should be allowed. State change is allowed only when the object is in the active(1) state. Successful return leaves the object in the inactive(2) state. You need to restart any clients before they can be used to process services after this state transition.

 

Skip navigation bar  Back to Top Previous Next