Remote Scripting Using Ssh; Configuring Multiple Systems For Scripting - Sun Microsystems Fire V20z Management Manual

Remote Scripting Using SSH

Remote scripting to the SP is done by using a program called SSH. For example, as a
user on the UNIX machine client.company.com with the SP name sp.company.com,
you could execute a command on the SP from the UNIX client using the following
format:
# ssh sp.company.com command
Because the SSH server must authenticate the remote user, the user must either enter
a password, or a trusted-host relationship must exist, or the remote user's public key
must be installed on the SP.
If using trusted-host relationships for passwordless access, the SP must have a local
user of the same name as the remote user (or the remote user should be a member of
a directory service group that is mapped to a local SP administrative group).
You can also add your public key file instead of creating a trusted-host relationship
to be authenticated via SSH. Refer to
When configured for passwordless access, the SSH daemon on the SP allows the
remote user access to sp.company.com without a password, either for logging in, or
for issuing remote ssh commands from the command line or from a script.

Configuring Multiple Systems for Scripting

There are two ways to configure multiple SPs for scripting:
Execute the procedure to configure the client machine on which you will be
■
running scripts for each SP. Refer to
Scripting" on page
Set up the trust relationship or add your public key file on an initial machine and
■
use the autoconfiguration feature to duplicate the configuration on each of the
additional machines. Refer to
and "Adding Public Keys" on page
"Adding Public Keys" on page
"Configuring a Windows Client for
104.
"Creating Trusted-Host Relationships" on page 103
103.
Chapter 4 Further Management Information
103.
101