access: Administrators, Managers
Restores selected settings of the Service Processor to the default factory configuration.
Service Processor configuration files are stored within the /pstore directory. Upon boot-up, the Service Processor copies these configuration files from /pstore to /etc whenever the files are missing from /etc. Resetting the Service Processor to its default configuration is accomplished by deleting the configuration files in the /pstore directory. A reboot of the Service Processor is necessary for the Service Processor reset to take effect. By default, the Service Processor will reboot 60 seconds after the sp reset to default-settings command executes, unless the -nowait option is specified, in which case the reboot occurs immediately.
access: manager
sp reset to default-settings {-a | --all} {-c | --config}
{-n | --network} {-s | --ssh} {-u | --users}
{-W | --nowait}
| Argument | Description |
|---|---|
| {-a | --all} | Resets all Service Processor settings to their default
configuration. When the Service Processor reboots, settings are reset
to their default values. This option also includes events and ipmi settings
(files are deleted immediately). |
| {-c | --config} | Resets other system configuration settings to their default configuration. When the Service Processor reboots, system settings are reset to their default values. |
| {-n | --network} | Resets network settings to their default configuration. When the Service Processor reboots, it has no network capabilities or hostname. Its NFS mounts will fail, and you will not be able to log into the Service Processor remotely via ssh or the SM Console. Set up the network configuration for the Service Processor via the Operator Panel to restore network functions. Set the hostname for the Service Processor in order to refer to the SP by name and set up the resolv.conf file in order to refer to other systems by name instead of dotted-quad IP addresses. This option deletes all the network files in /pstore. |
| {-s | --ssh} | Resets SSH settings to their default configuration. When the Service Processor reboots, new ssh public and private keys are generated. Using ssh to access the Service Processor from a remote system that had previously logged into the SP causes a failure with a message about the "Remote Host Identification" changing because the ssh key on the Service Processor has changed. The remote system will have to delete its ssh public key entry for the SP in order to ssh into the Service Processor successfully. This option deletes all the files in /pstore/ssh/. |
| {-u | -- users} |
Resets user authentication settings to their default configuration. When the Service Processor reboots, all user accounts will have been deleted and you will not be able to ssh into the Service Processor. You will have to log in to the Service Processor via the SM Console and create an initial manager account and then create new user accounts for the Service Processor. |
| [-W | --nowait] | Reboots the Service Processor immediately. |
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_NoPermission | 6 | Not authorized to perform this operation. |
| NWSE_NoMemory | 8 | Insufficient memory. |
| NWSE_Busy | 9 | Device or resource is busy. |
| NWSE_RPCConnected | 11 | RPC client already connected. |
| NWSE_RPCConnRefused | 12 | RPC connection refused. |
| NWSE_NoRouteToHost | 13 | No route to host (network down). |
| NWSE_HostDown | 14 | Host is down. |
Notes