# Configuring Shell Scripts

An administrator can make configuration changes for a single Service Processor by either using SSH to log in and run SM Commands or by connecting to the SM Console and changing values. For a multi-system environment in which configurations for all Service Processors must be synchronized, you can automate configuration changes.

As a Unix/Linux or Windows administrator, you can use SSH, trusted host relationships or public key authentication, the SM Commands, and Unix/Linux shell scripting to automate tasks that need to be performed on multiple Service Processors.

1. Set up your system for scripting.

Your server's remote scripting solutions depend on SSH (Secure SHell) for authentication and data encryption. If you do not already have SSH, you can obtain a free implementation, OpenSSH, available at www.openssh.org. The Service Processors allow the use of SSH v2 only.

2. Create a trusted host relationship or add your public key for SSH authentication.
In order to use SSH in a scripted environment such that you are not prompted for a password upon the execution of each command, establish a trusted host relationship between the machine from which the commands are sent and the Service Processor on which the commands are executed. This requires the prior creation of a manager-level user on the Service Processor.

You can also add a public key for SSH authentication, allowing you to log in via SSH and execute remote commands without being prompted for a password.

3. Configure your client for scripting.
You must configure the client machine on which you will be running scripts. Since Windows does not natively support the Service Processor trusted host relationship feature, scripting from a Windows client requires you to install a Unix/Linux-on-Windows toolset that supports SSH.

4. To create your scripts, use the examples that are provided in the sp/newisys/sm/commands/sample_scripts/scripts folder as a starting point.

Related Topics

Using the Service Processor SSH Console

Configuring the Client for Scripting

Configuring Multiple Systems for Scripting