controller ‑reenable

Re-enables a Controller that was previously excluded from the Oracle FS System due to failures.

SYNOPSIS

controller ‑reenable 
   [‑controller controller‑id‑or‑fqn]

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

DESCRIPTION

The Oracle FS System excludes a Controller from the cluster when the number of Controller failures reaches a predefined value. When running diagnostics, the counter can record an excessive number of Controller failures that do not correspond to actual failures. In some scenarios, the additional Controller failures might cause the Oracle FS System to fail the acceptance tests after FRU replacements.

Note: Only administrators with support roles are authorized to run controller ‑reenable command.

OPTIONS

‑controller: Specifies the fully qualified name (FQN) or unique identifier (ID) of the Controller to re-enable. If no FQN or ID is specified, all Controllers are re-enabled. Do not specify a Controller when leaving the other Controllers offline while recovering a faulted Controller.

EXAMPLE

Task

Oracle Customer Support re-enables a Controller that was previously repaired and tested. When the Controller is placed online in a production environment, the Oracle FS System marks the Controller as faulty. The Oracle Customer Support representative clears an incorrect health indicator and brings the Controller online.

Parameters

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

$ fscli controller -modifyAgentHaFlags ‑controller /⁠CONTROLLER-0 ‑clearWsCounter
$ fscli controller -reenable ‑controller /⁠CONTROLLER-0
$ fscli controller -rejoin ‑controller /⁠CONTROLLER-0