test

Sun N1 System Manager 1.2 Administration Guide

ProcedureTo Upgrade the OS Monitoring Feature on a Server

This procedure describes how to upgrade the OS monitoring feature on a server. This procedure is necessary after upgrading the N1 System Manager from a previous release, for provisionable servers on which the previous version of the OS monitoring feature is still installed. This procedure is for individual servers. You can upgrade the OS monitoring feature on multiple servers at once. See Chapter 2, Upgrading the Sun N1 System Manager Software and Provisionable Server Management Agents, in Sun N1 System Manager 1.2 Installation and Configuration Guide for details.

Note –

If the server was freshly installed using the load server or load group commands from the latest version of the N1 System Manager, and the feature subcommand was used, this procedure is not necessary.

Use the add server feature osmonitor command with the upgrade keyword to upgrade a provisionable server to a new version from the existing base management feature and OS monitoring feature.

If you submit add server feature commands by using a script, see Example 5–1 for an example.

Before You Begin
Steps

  1. Log in to the N1 System Manager.

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

  2. To upgrade the OS monitoring feature, type the following command:


    N1-ok> add server server feature osmonitor upgrade

    An Modify OS Monitoring Support job starts. Note that this command also upgrades the base management feature.

    See add server in Sun N1 System Manager 1.2 Command Line Reference Manual for details about command syntax.

  3. Track the Add OS Monitoring Support job to completion.

    After the job completes successfully, the Servers table on the System Dashboard tab appears with values for OS Usage and OS Resource Health.

    Verify that the OS monitoring feature is supported by issuing the show server command. Output for the server appears with the OS Monitoring Supported value as OK one of the following sets of commands on the provisionable server.

    Note –

    It can take 5-7 minutes before all OS monitoring data is fully initialized. You may see that CPU idle is at 0.0%, which causes a Failed Critical status with OS usage. This should clear up within 5-7 minutes after adding or upgrading the OS monitoring feature.

Troubleshooting

Upgrading the OS monitoring feature might fail due to stale SSH entries on the management server. If the add server feature osmonitor agentip command fails and no true security breach has occurred, remove the known_hosts file or the specific entry in the file that corresponds to the provisionable server. Then, retry the add server feature osmonitor agentip command. If the management server is running Linux, the known_hosts file is at /root/.ssh/known_hosts. If the management server is running the Solaris OS, the known_hosts file is at /.ssh/known_hosts.

Upgrading the OS monitoring feature will fail if you specify the agent IP or the SSH credentials in the add server feature osmonitor upgrade command when running it on servers that already have the base management feature support. To solve this problem, issue the add server feature osmonitor command without specifying values for the agent IP or for the SSH credentials.