controller ‑modifyAgentHaFlags

Modifies the high availability (HA) settings for a Controller.

SYNOPSIS

controller ‑modifyAgentHaFlags 
   [‑controller controller‑id‑or‑fqn ]
   { [‑noWarmstart]
     [‑noFailover]
     [‑clearWsCounter]
     [‑debugMode]
   | ‑clearFlags
   }

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

When troubleshooting a Controller, an Oracle Customer Support representative might change one or more of the high availability (HA) settings. The HA flags modify the normal operating behaviors of the Controllers in the following ways:

The no warm start HA flag instructs the Oracle FS System to convert all attempts to perform a soft reboot (warmstart) into a Controller failure so that all resources are failed over to the peerController.
The no Failover HA flag instructs the Oracle FS System to prevent the Controller from failing when the warm start counter reaches a value of four. The clear HA flag undoes the no Failover HA flag.
The clear warm start HA flag instructs the Oracle FS System to clear the number of warm starts that have been recorded for the specified Controller.
The debug HA flag instructs the Oracle FS System to capture additional information that can assist Oracle Customer Support with troubleshooting the Controller.

Note: Do not run the controller ‑modifyAgentHAFlags command unless instructed to do so by Oracle Customer Support. Only administrators with support roles are authorized to run controller ‑modifyAgentHaFlags command.

OPTIONS

‑controller: Specifies the fully qualified name (FQN) or unique identifier (ID) of the Controller if you are resetting the Agent HA flags for a specific Controller. If no controller is specified, the HA flags are reset for all Controllers.
‑noWarmstart: Indicates that if the Oracle FS System attempts to perform a warmstart on the Controller, the warmstart attempt is re-initialized as a Controller failure. The Controller fails over to the peer. Then, the Controller attempts to re-initialize and fail back.
‑noFailover: Indicates that on the fourth attempt, the Oracle FS System will warm start the Controller instead of failing over the Controller to its peer.
‑clearWsCounter: Resets the warm start counter. If you clear the warm start counter for a Controller before the possibility of a fourth warm start occurring, the fourth warm start will not be converted into a Controller failure.
‑debugMode: Places the Controller in a debugging mode.
‑clearFlags: Clears all high availability (HA) indicators and returns the settings to the default values, including the warm start counter.
Note: The Oracle FS System maintains the failure history of the Controller on the Pilot. Clearing the warm start counter does not affect the failure history. To reset the failure history, run the controller ‑reenable command.

EXAMPLE

Task

For diagnostic purposes, Oracle Customer Support changes the high availability (HA) settings for a Controller. The Oracle Customer Support representatives sets a specific flag to prevent the Controller from failing over to the partner Controller.

Parameters

The name of the Controller preceded by a forward slash: /⁠CONTROLLER-0

$ fscli controller ‑modifyAgentHaFlags ‑controller /⁠CONTROLLER-0 ‑noFailover