system ‑restart

Stops the data paths, writes the data from the Controller memory to permanent storage, and then returns the Oracle FS System to its normal operational state.

SYNOPSIS

system ‑restart 
   { [‑overridePinnedData]
     [‑overrideDisabledControllers]
     [‑overrideOperationPoolDraining]
     [‑overrideStateCheck]
     [‑serviceType {san | nas | sanBias | nasBias}]
     [‑resetModePages]
   | [‑emergencyClearFbm]
   | [‑emergencyPreserveFbm]
   }

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

DESCRIPTION

Important! Before issuing a restart command, halt all I/O operations to avoid the possibility that data is written to cache but not to disk (pinned data) when the Oracle FS System shuts down and restarts. Run the system ‑conservativeMode command to flush all data to storage before issuing a restart command.

During a system restart, the Oracle FS System stops servicing protocols and proceeds to a shutdown state where it continues to monitor system status and issues system alerts, and performs Call‑Home if required. As soon as the shutdown completes successfully, the system begins a complete system startup sequence.

If the shutdown portion of the restart process fails for any reason, the system is placed in a shutdown failed status and will not restart. Data access may be available depending on the failure. If assistance is required, contact Oracle Customer Support.

CAUTION

The system ‑restart ‑overridePinnedData command may be used to restart a system that has a Pinned Data condition. However, running this command discards all Pinned Data, which may result in data integrity issues for LUNs. This option should not be used without first attempting to clear the Pinned Data condition. Unless the Pinned Data is on volumes where the data can be recreated quickly and easily, do not use this option before attempting to resolve the cause. If you have Pinned Data, you should attempt to resolve the internal PI fabric or storage subsystem condition before you ever use this override option. If the resolution of the PI/Storage is successful, the system will flush the Pinned Data to storage and remove the related Alerts. If assistance is needed, contact Oracle Customer Support.

The system ‑restart ‑serviceType command may be used to change the service type of your system. The service type is specified on your Sales Order and System Information Documents. Do not attempt to change the Service type to one that is NOT specified on your System Information Documents.

If you have a disabled Controller, run the system ‑restart ‑overrideDisabledController command to force the Oracle FS System to restart in a single Controller configuration.

Note: Only administrators with primary administrator, admin1, or support roles are authorized to run the system -restart command. Only administrators with support roles are authorized to run the emergencyClearFbm or emergencyPreserveFbm options of the system -restart command.

OPTIONS

‑emergencyClearFbm: Indicates that the Oracle FS System will restart without attempting to recover cached data. This option discards all data in the Flash Memory on the controller. Use only if instructed to do so by an Oracle Customer Support representative.

Note: Only administrators with support roles are authorized to run the emergencyClearFbm option of the system -restart command.
‑emergencyPreserveFbm: Specifies that the Oracle FS System retain all data and configuration information in the Flash Memory on the controllers, but will force an immediate shutdown and restart. Use only as instructed to do so by an Oracle Customer Support representative.

Note: Only administrators with support roles are authorized to run the emergencyPreserveFbm option of the system -restart command.
‑overrideDisabledControllers: If there is a disabled Controller the system does not perform a normal shutdown. This option allows the system to be restarted. The status of the disabled Controller may or may not change on the resulting restart.
‑overrideOperationPoolDraining: Restarts the Oracle FS System without completing any pending management operations.
‑overridePinnedData: If there is pinned data, it does not stop the process of restarting the system. The pinned data that cannot be written to physical storage is discarded.
Important! Contact Oracle Customer Support to resolve any issues with the Backend SAS Interconnect, a storage condition, or both, which might be causing the pinned data. Clearing pinned data guarantees that host data is deleted permanently.
‑overrideStateCheck: Ignore the state of the system and continue with the restart operation.
‑resetModePages: Requests that the mode pages be reloaded on all of the drives. If an administrator has disabled the reload mode pages flag, the system ignores the ‑resetModePages option.
Note: A drive mode page contains changeable values that are stored on a drive as part of the drive firmware. Do not reload or reset drive mode pages unless you are instructed to do so by Oracle Customer Support. Reloading or resetting drive mode pages increases the time that is needed to restart or to shut down the system.
‑serviceType: Specifies the type of protocol support the Oracle FS System provides. Valid values: san, nas, sanBias, or nasBias. The correct Service Type for your system is specified on the Sales Order and the System Customer Information Documents and should not be changed. If the installed hardware in the Controllers does not allow the changed Service Type, the system will not boot. Modify the service type only as instructed by Oracle Customer Support.

EXAMPLE

Task

Restart the Oracle FS System.

Parameters

None.

$ fscli system -restart