Monitoring Issues

This section describes known monitoring issues.

OS Monitoring Status Does Not Change Back to “Good” State (6483181)

If you change an OS monitoring threshold value that moves the current monitoring status from Warning to Good, the status is not consistently updated in the N1 SM interface.

Workaround: On the management server, refresh the server's monitoring information:

n1-ok> set server server-name refresh

OS Monitoring Threshold Violations Are Not Being Sent (6433480)

The OS monitoring agent outbound interface might not match the user specified agentip. If uname -n on the target server does not resolve to agentip, the agent will not send traps to N1 System Manager over the agentip interface and the system will not restart upon reboot.

Workaround: Before adding the OS monitoring (osmonitor) feature, ensure that on the target server, the primary host name always resolves to the agentip IP address, which will be used to add the OS monitoring feature. Verify that uname -n always returns this host name, even upon reboot. Then, add the OS monitoring feature.

Jobs That Are Queued But Not Running Are Shown in the Job Detail as “Not Started” (6318398)

When the total job load is high enough to prevent the next job in the queue from running, the Job Details screen shows the running jobs' status as “running,” and the status for other jobs is shown as “Not Started.” The queued jobs will run after one or more of the running jobs have completed and the total job load is low enough to allow the next job in the queue to run.

See Job Queueing in Sun N1 System Manager 1.3 Discovery and Administration Guide for further information.

Clock Icon Representing Running Jobs Remains After Jobs Finish (6258571)

Even after all jobs are finished running, the clock icon next to the servers in the View Selector section might still display due to a problem with the refresh feature.

Workaround: Click the Refresh button or press F5 to refresh the browser interface.