To Add the OS Monitoring Feature (Sun N1 System Manager 1.3 Discovery and Administration Guide)

Sun N1 System Manager 1.3 Discovery and Administration Guide

To Add the OS Monitoring Feature

This procedure describes how to add the OS monitoring feature on a server.

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

Note –

You can add the OS monitoring feature automatically as part of the load server or load group commands. See load server in Sun N1 System Manager 1.3 Command Line Reference Manual or load group in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

Before You Begin

Discover servers. See Chapter 4, Discovering Manageable Servers.
Load an OS if one is not already installed, see To Load an OS Profile on a Server or a Server Group in Sun N1 System Manager 1.3 Operating System Provisioning Guide and load server in Sun N1 System Manager 1.3 Command Line Reference Manual.

Steps

To add the OS monitoring feature, perform one of the following actions:
- If you have not added the base management feature, type the following command:
  
  Note –
  The SSH user account that is used in the following command must have root privileges on the remote machine.
  N1-ok> add server server feature osmonitor agentip agentip agentssh username/password
- If you have already added the base management feature, type the following command:
  
  Note –
  You cannot specify the agent IP or SSH credentials when adding OS monitoring support to a server that has base management support.
  N1-ok> add server server feature osmonitor
An Add OS Monitoring Support job starts.

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

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.

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 Failed Critical status clears 5-7 minutes after adding or upgrading the OS monitoring feature.

If no monitoring data is available for the server, see Monitoring Problems in Sun N1 System Manager 1.3 Troubleshooting Guide.

If the managed server's IP address changes, use the set server command again before enabling or disabling monitoring

Example 6–2 Adding the OS Monitoring Feature to Managed Servers Discovered by SP-Based Discovery

The following example shows how to add the OS monitoring feature to a server that had an OS installed prior to being discovered through SP-Based discovery.

N1-ok> add server 192.168.1.1 feature osmonitor 
agentip 192.168.10.10 agentssh admin/admin

The agentip parameter specifies the IP address of the managed server's data network interface to be monitored by the management server. The ssh user name admin and password admin are used for root access authentication.

The following example of the show command shows how to verify that the OS monitoring feature was added successfully to a server that had an OS installed prior to being discovered through its SP.

N1-ok> show server 192.168.1.1
Name        Hardware  Hardware Health Power  OS Usage  OS Resource Health
192.168.1.1 V20z      Good            On     Solaris   Good

See SP-Based Discovery for details about this method of discovering servers.

Example 6–3 Adding the OS Monitoring Feature to Servers Discovered by OS-Based Discovery

The following example shows how to add the OS monitoring feature to a server that had an OS installed before being discovered by OS-based discovery.

N1-ok> add server 192.168.1.1 feature osmonitor 
agentip 192.168.10.10 agentssh admin/admin

The following example of the show command shows how to verify that the OS monitoring feature was added successfully to a server that had an OS installed prior to being discovered by OS-based discovery.

N1-ok> show server 192.168.1.1
Name        Hardware  Hardware Health Power  OS Usage  OS Resource Health
192.168.1.1 V20z      Good            On     Solaris   Good

See OS-Based Discovery for details about this method of discovering servers.

Example 6–4 Scripting OS Monitoring Support

The following example script issues multiple add server feature commands on servers that do not have the base management feature support:

n1sh add server 10.0.0.10 feature=osmonitor agentip 10.0.0.110 agentssh root/admin &
n1sh add server 10.0.0.11 feature=osmonitor agentip 10.0.0.111 agentssh root/admin &
n1sh add server 10.0.0.12 feature=osmonitor agentip 10.0.0.112 agentssh root/admin &

Troubleshooting

Adding 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 managed server. Then, retry the add server feature osmonitor agentip 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.

Adding the OS monitoring feature will fail if you specify the agent IP or the SSH credentials in the add server feature osmonitor 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.