Monitoring Issues

Cannot Initialize OS Monitoring Because of an Old SSH Key Entry for a Given IP (6208006)

OS monitoring support cannot be initialized when redeploying to a provisionable server where the IP address is the same IP address assigned in a previous deployment. An IpUnreachableException is generated. This occurs because the /.ssh/known_hosts file contains the original deployment IP address.

Workaround: Log in to the management server as root, and either edit the /.ssh/known_hosts file and remove the ssh key entry for the server, or remove the /.ssh/known_hosts file.

Update Job Creation Error Message Does Not Provide Adequate Information (6230630)

If you attempt to load a Red Hat Linux update onto a server installed with the Solaris OS, the Sun N1 System Manager will initiate the Update job. This Update job will fail.

Workaround: Make sure that the update is compatible with the installed OS. You can view a provisionable server's OS by using the show server command, and you can view the OS type for an OS update by using the show update command.

The unmonitored and unknown Filters are Unavailable for the show server Command (6240297)

The unmonitored and unknown filter values for a server's utilization (OS Resource monitoring) do not work. Specifically, the following commands are unavailable:

N1-ok> show server utilization=unmonitored
N1-ok> show server utilization=unknown

Workaround: There is no workaround.

Unable to Filter Using the Hardware Health Monitor Value Unmonitored (6240368)

Issuing the show server health=unmonitored command returns no server list, even if servers are in the Unmonitored state.

Workaround: No workaround available.

Apostrophe Cannot Be Used in Notification Description (6242713)

The create notification command fails if an apostrophe is used for the description attribute.

Workaround: Escape the apostrophe with another apostrophe (for example, Paul”s Notification) or do not use an apostrophe in the description.

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

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

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

OS Resource Health Status Polling is not Updated According to the User-Specified Polling Value (6287040)

When OS monitoring is stopped on a provisionable server and subsequently restarted, the OS status is not updated until 10 minutes later, even when the user-specified polling value is less than 10 minutes.

Workaround: No workaround available.

OS Resource Health Status Not Updated in Browser Interface (6291223)

If the provisionable server's network interface is unavailable, the OS resource health status in the browser interface should change to unreachable on the next refresh interval. Currently, this status does not change.

By default, the network and refresh intervals are set to 10 minutes when the N1 System Manager software is installed. If the network and refresh intervals are different, then the OS resource health and network status will be updated at different intervals. This in turn causes different results to display when the provisionable server's data network interface is unreachable, and the network polling interval is lower than the OS resources refresh interval.

The network status is updated in the server's detail page in the browser before it is updated in the main server page. Because of these differences, the OS resource health status in the server main page changes to “unreachable” on the next OS resources refresh interval (default value: 10 minutes).

Workaround: Use the show server server name command to view the OS resource health status.

Misleading Job Status “Running” or “Complete” (6299790)

If a Create OS job is running and the system runs out of disk space, the job status shows “running”. When disk space is cleaned up, and the N1 System Manager is restarted, the job status changes to “complete” even though the Create OS job has failed.

The failed job's state will remain shown as “complete” and cannot be corrected.

Workaround:

1. Free up at least 3 Gbytes of disk space.

2. Stop and restart the N1 System Manager.

3. Resubmit the Create OS operation.

Filesystem Monitoring Works Only With ext3 Filesystems on Linux Servers (6308686)

Filesystem monitoring does not work on a Linux provisionable server with a non-ext3 filesystem, even though the appropriate OS monitoring support has been added. Only ext3 filesystems can be monitored on Linux servers with the N1 System Manager.

Workaround: Reinstall the provisionable server with an OS profile that creates an ext3 filesystem.

OS Resource Health Monitoring Enforces a Five-Minute Minimum Refresh Interval (6311946)

Because the OS health monitoring agent caches the monitoring data every 5 minutes, setting the OS resource refresh interval to less than 5 minutes may retrieve existing cached data and have no apparent effect, which could lead to invalid conclusions of reported monitoring data.

Workaround: Set the OS resources monitoring interval to at least 5 minutes.

Installation of the OS Monitoring Feature Will Hang if the File System Device Name is More Than 20 Characters (6317401)

The OS Monitoring install job will time out and fail if the file system device name on the provisionable server is more than 20 characters in length. OS resource monitoring will not be available in this situation. This issue occurs most often on provisionable servers on which the logical volume management (LVM) feature of the operating system is being used. OS resource monitoring will not be available in this situation.

The Base management feature can still be added to the provisionable server, but not the OS monitoring feature.

Workaround: Make sure that the file system device name is within the 20 character limit.

Management Support Features Do Not Work Because hostinstall.pl is Not Correctly Generated for Some Networks (6317747)

If the provisioning network uses the IP address form x0.0.0.y (10.0.0.34) and if hostname resolution fails, the hostinstall.pl script will not be correctly generated and the script will not be able to contact the management server to configure the provisionable server. This issue affects both the add server server feature osmonitor and add server server feature basemanagement commands.

Workaround: Manually add the x0.0.0.y form IP to the hostinstall.pl script on the management server. On a Red Hat management server, edit the /var/opt/sun/scs/web/pub/hostinstall.pl file. On a Solaris management server, edit the /var/opt/SUNWscs/web/pub/hostinstall.pl file.

Line 33 should look like:

my @CSHostAddrs  = ( 'ns1m','172.20.48.120' );

Add the IP address to the list:

my @CSHostAddrs  = ( 'ns1m','172.20.48.120','10.0.0.1' );

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 Queuing Behavior in Sun N1 System Manager 1.1 for further information.