Changes the operational state of the topology of the Backend SAS Interconnect.
topology ‑modify [‑disparityThreshold disparity‑errors‑per‑hour] [{‑manualMode | ‑noManualMode}] [ ‑clearStatistics [‑controller controller‑id‑or‑fqn [, controller‑id‑or‑fqn]... ] ] [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}] [{‑outputformat | ‑o} { text | xml }] [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
Increase or decrease the number of disparity errors that are allowed.
Disable the diagnostics that automatically run on the topology so that Oracle Customer Support can run their tests.
Clear the statistics that are already captured for one or both of the Controllers.
Sets the number of disparity errors that are allowed each hour.When the threshold number is reached, the system generates system alerts and logs events.
Instructs the system to stop the automatic management of the Backend SAS Interconnect.
Resumes the automatic management of the Backend SAS Interconnect.
Clears the topology performance and usage statistics for the specified Controller. If you do not specify a Controller, this option clears the statistics for both Controllers.
Specifies the fully qualified name (FQN) or the unique identifier (ID) of a Controller.
The following global options can be used for fully formed fscli commands:
The command completes successfully.
The command returns with an error.
The session times out.
Inspects the validity of the command syntax, not the semantics. Used to test the structure of a command without running the command. Does not determine whether errors would be produced if you issue a structurally correct command with the input provided.
Directs the CLI to prompt you to supply a session key when you issue the command. The CLI displays Sessionkey: as the prompt. To obtain a session key, log in with the ‑returnKey option specified. After the session is established, the session key is displayed in STDOUT. If you request a session key, the ‑sessionkey option is required syntax for all commands that are issued in a given session. In environments with more than one Oracle FS System, the session key is used to determine to which Oracle FS System to direct the command for validation. Session keys are also used to establish two or more CLI sessions when using a shared administrator account.