When the platform is in the Communicating state (in which the OS is communicating with the SP), if the platform drivers are uninstalled, the SP remains in the Communicating state even though it can no longer communicate with the platform.
Refer to “Platform Get OS State Subcommand” on page 142 for a list of possible states.
Return Codes
TABLE F-15 lists the return codes for this subcommand.
TABLE F-15 Return Codes for Subcommand platform set os state
Return Code | ID | Description |
|
|
|
NWSE_Success | 0 | Command successfully completed. |
NWSE_InvalidUsage | 1 | Invalid usage: bad parameter usage, conflicting |
|
| options specified. |
NWSE_RPCTimeout | 2 | Request was issued, but was not serviced by the |
|
| server. RPC procedure timed out and the request |
|
| may or may not have been serviced by the server. |
NWSE_RPCNotConnected | 3 | Unable to connect to the RPC server. |
NWSE_NoPermission | 6 | Not authorized to perform this operation. |
NWSE_Busy | 9 | Device or resource is busy. |
NWSE_FileError | 18 | File open, file missing, or a read or write error |
|
| occurred. |
NWSE_InvalidOpForState | 22 | Invalid operation for current state. |
|
|
|
Platform Set OS State Boot Subcommand
Description: This command serves as an alias for the subcommand
platform set os state reboot and only functions when the platform power state is off.
Format
Command format:
platform set os state boot
Appendix F Platform Commands 145
