Adding the feature might fail due to stale SSH entries on the management server. If the add server server-name feature osmonitor agentip command fails and no true security breach has occurred, remove the /root/.ssh/known_hosts file or the specific entry in the file that corresponds to the provisionable server. Then, retry the add command.
Additionally, adding the OS monitoring feature to a server that has the base management feature might fail. The following job output shows the error:
Repeat attempts for this operation are not allowed.
This error indicates that SSH credentials have previously been supplied and cannot be altered. To avoid this error, issue the add server feature osmonitor command without agentssh credentials. See To Add the OS Monitoring Feature for instructions.
N1-ok> show job 61 Job ID: 61 Date: 2005-08-16T16:14:27-0400 Type: Modify OS Monitoring Support Status: Error (2005-08-16T16:14:38-0400) Command: add server 192.168.2.10 feature osmonitor agentssh root/rootpasswd Owner: root Errors: 1 Warnings: 0 Steps ID Type Start Completion Result 1 Acquire Host 2005-08-16T16:14:27-0400 2005-08-16T16:14:28-0400 Completed 2 Run Command 2005-08-16T16:14:28-0400 2005-08-16T16:14:28-0400 Completed 3 Acquire Host 2005-08-16T16:14:29-0400 2005-08-16T16:14:30-0400 Completed 4 Run Command 2005-08-16T16:14:30-0400 2005-08-16T16:14:36-0400 Error Results Result 1: Server: 192.168.2.10 Status: -3 Message: Repeate attempts for this operation are not allowed. |
If you tried to install the OS monitoring agents as described in To Add the OS Monitoring Feature and OS monitoring data did not appear, verify that the OS monitoring feature was installed, as follows:
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. At that point, OS monitoring data should be available for the provisionable server by using the show server server command.
Use the grep command and try to see if indeed the agents themselves were successfully installed.
To verify the Solaris feature, type the following commands:
# pkginfo |grep n1sm sparc: SUNWn1smsparcag-1-2 solx86: SUNWn1smx86ag-1-2 # ps -ef |grep -i esd root 23817 1 0 19:57:59 ? 0:01 esd - init agent -dir /var/opt/SUNWsymon -q |
To verify the Linux feature, type the following commands:
# rpm -qa | grep n1sm-linux-agent # ps -ef | grep -i esd root 1940 1 0 Jan28 ? 00:00:14 esd - init agent -dir /var/opt/SUNWsymon -q |