Agent Operations

online

If the state of all local devices is read-write enabled (RW), the agent creates a lock file on the local host to indicate that the resource is online. This makes the devices writable for the application.

If one or more devices are write-disabled (WD), the agent runs a symrdf command to enable read-write access to the devices.

• For R2 devices in the SYNCHRONIZED state, the agent runs the symrdf failover command to make the devices writable.
• For R1 devices in the FAILED OVER or R1 UPDATED state, the agent runs the symrdf failback command to make the devices writable.
• For all devices in the PARTITIONED state, the agent runs the symrdf rw_enable command to make the devices writable.

• The agent runs the command only if the AutoTakeover attribute is set to 1 and if there are no dirty tracks on the local device. Dirty tracks indicate that an out-of-order synchronization was in progress when the devices became partitioned, rendering them inconsistent and unusable. If dirty tracks exist, the online entry point faults on timeout.

• For R1 devices in the UPDINPROG state, the agents waits for the devices to transition to the R1 UPDATED state before running a symrdf command.
• For R2 devices in the SYNCINPROG state, the agent waits for the devices to transition to the SYNCHRONIZED state before running a symrdf command.



---

Note    The agent does not run any commands if it detects that there is not enough time remaining for the entry point to complete the command. See To set the OnlineTimeout attribute for more information.

---

offline

Removes the lock file on the device. The agent does not run any SRDF commands because taking the resource offline is not indicative of the intention to give up the devices.

monitor

Verifies that the lock file exists. If the lock file exists, the monitor entry point reports the status of the resource as online. If the lock file does not exist, the monitor entry point reports the status of the resource as offline.

open

Removes the lock file on the host where the entry point is called. This prevents potential concurrency violation if the service group fails over to another node.

clean

Determines whether if it is safe to fault the resource if the online entry point fails or times out. The main consideration is whether a management operation was in progress when the online thread timed out and was killed, potentially leaving the devices in an unusable state.

info

Reports the device state to the VCS interface. This entry point can be used to verify the device state and to monitor dirty track trends.

action

Performs a symrdf update from the R2 side to merge any dirty tracks from the R2 to the R1.