Adding a trusted host relationship is one way to allow for passwordless access and thus is a means for one-to-many scripting. Once a host equivalence relationship has been created with a client, users on that client can remotely execute commands on the Service Processor without being prompted for a password, provided one of the following conditions is met:
If the login is authorized by means of a directory service group mapping, the ssh command is executed as the proxy user on the Service Processor, either rmonitor, radmin, or rmanager.
Support is available for SSH protocol version 2 key types (RSA or DSA) only.
If DNS is enabled on the Service Processor, the client machine must be specified with its DNS name, not an IP address.
The Current Authentication displays above the table.
The Settings table contains the current trusted hosts configuration:
| Setting | Description |
|---|---|
| New Host | The hostname and IP address of the host with which the trust relationship will be created. |
| Public Key | The public host key of the specified host. |
| Host | The name and IP address of a host with which a trust relationship exists. |
Generating Host Keys
The hosts SSH install should generate the host keys. If it does not, follow these steps to manually generate the key pair:
NOTE: Use scp to copy the files to either /tmp
or to your home directory. The sp commands will then install the file specified
on the command line.
NOTE: If DNS is enabled on the Service Processor, you must specify the client that is used in the trust commands with the DNS name (not the IP).
Creating a Trusted Host Releationship
SM Console Usage:
To create a trusted host relationship, follow these steps:

SM Command Usage:
You can also use the trusted hosts subcommands to perform this function at the command line.
Creating the Initial Manager Account
Mapping Directory Service Groups