SNMP Agent MIB Reference
|
 |
 |
|
|
 |
 |
tuxTdomainMaster
Syntax
Access
Description
DisplayString is in format: LMID1[,LMID2]
The master identifier (LMID1) must correspond to the local machine for inactive applications. single-machine(1) mode applications (see tuxTdomainModel below) can set only the master logical machine identifier. Modifications to the tuxTdomainMaster value in an active multi-machine(2) application (see tuxTdomainModel below) have the following semantics.
Assuming current active master LMID A, current backup master LMID B, and secondary LMIDs C, D, ...., the following scenarios define the semantics of permitted changes to the tuxTdomainMaster object in a running multi-machine(2) mode application.
A,B -> B,A — Master migration from A to B. A,B -> A,C — Change backup master LMID designation to C.
Note that master migration can be either orderly or partitioned. Orderly migration takes place when the master machine is active and reachable. Otherwise, partitioned migration takes place. All newly established or re-established network connections verify that the two sites connecting share a common view of where the master machine is located. Otherwise, the connection is refused and an appropriate log message is generated.
The master and backup machines in an active application must always have a Tuxedo system release number greater than or equal to all other machines active in the application. The master and backup machines must be of the same release. Modifications to the tuxTdomainMaster object must preserve this relationship.
