Installs components from the staged software package.
software_update ‑install { ‑drive drive‑type [,drive‑type]... | { ‑component component:instruction [,component:instruction]... | ‑all {newerVersionOnly | alwaysInstall} } [{‑disruptive | ‑noDisruptive}] [‑ignoreCompatibilityChecking] [‑forceControllerShutdown [‑discardFbm] ] [‑ignoreBadSystemState] [‑ignoreOperationPoolDraining] [‑overridePreviousFailedUpdate] [‑ignoreExistingAlerts] } [‑suppressWarnings] [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}] [{‑outputformat | ‑o} { text | xml }] [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
Conflicts with the compatibility matrix
Non-optimal system state
Incomplete internal tasks
Previously failed update operations
Unresolved system alerts
By default, if any combination of the above conditions exists, the update operation fails. To override this default action, you can explicitly request to be prompted when one or more of these conditions are encountered. When prompted, you can choose whether to terminate the update operation or to proceed with the update operation.
Warning: Contact the Support Center before proceeding! Proceeding without their assistance could risk data loss. Continue?
Processes the staged software module only when it is newer than the existing module.
Processes the staged software module regardless of the version of the existing module. Only use this option if you have been instructed by the release notes, a My Oracle Support Knowledge article, or Oracle Customer Support.
Clears the flash-backed memory in the Controllers.
To use the ‑discardFbm option, you must also specify the ‑forceControllerShutdown option.
Takes all of the data paths offline and temporarily places the Oracle FS System in an inactive state.
Specifies the types of staged drive firmware to install. To get a list of the types of installed drive firmware, use the ‑list subcommand.
Instructs the software update process to proceed when hardware issues exist.
If a hardware issue is encountered during the update operation, you are prompted to confirm that you want the system to ignore the condition. To ignore the condition and to proceed with the update, enter y.
Both Pilots need to be online. If both Pilots are not online, the update fails.
Any hardware that is not online at the time of the installation is not upgraded until it is back online.
Instructs the software update process to proceed when a conflict with the settings in the compatibility matrix occurs.
If a conflict is encountered during the update operation, you are prompted to confirm that you want the system to ignore the condition. To ignore the condition and to proceed with the update, enter y.
Instructs the software update process to ignore any existing system alerts and to continue the update.
If unresolved system alerts are encountered during the update operation, you are prompted to confirm that you want the system to ignore the condition. To ignore the condition and to proceed with the update, enter y.
Instructs the software update process to proceed after waiting for a preset time period for internal tasks to complete, regardless of whether those tasks have completed within that period.
If internal tasks cannot be completed in time during the update operation, you are prompted to confirm that you want the system to ignore the condition. To ignore the condition and to proceed with the update, enter y.
Performs the software update with the data paths and the Oracle FS System remaining active. User applications can continue accessing the storage arrays without interruption.
Instructs the software update process to ignore any failures from a previous update attempt and to continue the update.
If a previous update failure is encountered during the update operation, you are prompted to confirm that you want the system to ignore the condition. To ignore the condition and to proceed with the update, enter y.
Instructs the system not to display any confirmation prompts when non-optimum conditions are encountered and, instead, to continue the specified operation.
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.