access: Administrators
Starts the Service Processor and platform diagnostics framework. You must execute this command before running any tests.
diags start
| Argument | Description |
|---|---|
| { --noplatform} | Specifies to start diagnostics on the Service Processor from the NFS mount without rebooting the platform into diags mode. |
After running this command you can immediately run Service Processor tests.
This command reboots the platform into diagnostics mode. This process may take
between 2 and 3 minutes to complete. You can begin running diagnostics on the
Service Processor while the platform diagnostics are loading. Wait approximately
1 minute for the diagnostic kernel to completely load on the platform before
running the platform diagnostics tests.
To check whether diagnostics tests are available to run, execute the diags get state command.
If the return from the command is that the platform is up and ready for diagnostics, then you can submit platform diagnostic tests for execution.
You can optionally start diagnostics on the Service Processor from the NFS mount without rebooting the platform into diags mode. This enables you to continue running the production operating system while simultaneously performing SP diagnostics testing. To do so, run the diags start command with the following option:
diags start --no platform
The platform state must be either off or OS Communicating. Refer to the platform get os state command for details about these states.
Return Codes
Following are the return values for this command:
| Code | Numeric Code | 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_InvalidArgument | 4 | One or more arguments were incorrect or invalid. |
| NWSE_NoPermission | 6 | Not authorized to perform this operation. |
| NWSE_NoRouteToHost | 13 | No route to host (network down). Occurs when CD diagnostics is unable to send a packet to the Service Processor on a specific port. |
| NWSE_InvalidOpForState | 22 | Invalid operation for current state. |
| NWSE_ServiceNotAvailable | 24 | Requested service is not available. Occurs when CD diagnostics is unable to send a packet to the Service Processor, is unable to determine that the Service Processor diagnostics was started properly, or CD diagnostics is running and the user attempts to run diagnostics on the Service Processor. |