test

Sun N1 System Manager 1.3 Discovery and Administration Guide

Replacing Managed Servers

This section describes how to replace a failed managed server in the N1 System Manager.

ProcedureTo Replace a Server

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Type the following command:


    N1-ok> stop server server force

    The managed server is shut down and powered off. See stop server in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

  3. Disconnect the manageable server from the rack.

  4. Remove the manageable server from the system.


    N1-ok> delete server server

  5. Connect the new manageable server.

    Follow the instructions in Sun N1 System Manager 1.3 Site Preparation Guide.

  6. Discover the replacement manageable server using your chosen method of discovery.

    Follow the instructions in Chapter 4, Discovering Manageable Servers.

    The replacement server is managed. See discover in Sun N1 System Manager 1.3 Command Line Reference Manual for details. You can now set up monitoring. See Supporting OS Monitoring and Enabling and Disabling Monitoring for details.

Troubleshooting

The discover command credential attributes are used for security. SSH, IPMI, and Telnet require a username and a password. SNMP requires that you input a valid value for the read security community string. If credentials are not specified, the discovery process uses the default credentials that were defined during installation. For default credentials, see Setting Up Manageable Servers in Sun N1 System Manager 1.3 Site Preparation Guide.

Discovery might fail due to stale SSH entries on the management server. If the discover command fails with an error message indicating that there are invalid credentials or SSH key changed: Cannot connect to host and no true security breach has occurred, remove the known_hosts file or the specific entry in the file that corresponds to the managed server. Then, retry the discover command. See To Update the ssh_known_hosts File in Sun N1 System Manager 1.3 Troubleshooting Guide for details.

The problem of stale SSH entries on the management server can be avoided if, during the n1smconfig configuration process, you modify SSH policies by accepting changed or unknown host keys. Accepting changed or unknown host keys carries a security risk but avoids the problem of stale SSH entries on the management server. For more information, see To Configure the N1 System Manager in Sun N1 System Manager 1.3 Installation and Configuration Guide.