test

Sun N1 System Manager 1.2 Release Notes

Monitoring Issues

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, Support”s Notification) or do not use an apostrophe in the description.

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 may still display, which is a problem with the refresh feature.

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

A Misleading Create OS Job Status After Running Out of Disk Space on Management Server (6299790)

If a Create OS job is running and the management server 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.

Note –

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.

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.2 Administration Guide for further information.

Memory Threshold Values Are Not Updated Properly When OS Monitoring Agents are Upgraded by the agentupgrade Script (6330911)

If you upgrade the OS monitoring agents to the 1.2 release by using the agentupgrade script, the following memory threshold values are not updated properly:

This issue may put the associated provisionable servers in a “Failed Critical” state.

Workaround: After you upgrade the OS monitoring agents, use the set server or set group commands to change the threshold values on the servers.

Email Notifications Stop Being Sent After an OS Monitor Threshold Is Exceeded (6347039)

If an OS monitor threshold is exceeded, email notifications may stop being sent. This is an intermittent problem.

Workaround: Perform the following procedure on the management server.

  1. Shutdown N1 System Manager.


    # /etc/init.d/n1sminit stop

  2. For a Red Hat management server, change directory to /etc/opt/sun/cacao/modules.


    # cd /etc/opt/sun/cacao/modules

    For a Solaris management server, change directory to /etc/opt/SUNWcacao/modules.


    # cd /etc/opt/sun/SUNWcacao/modules

  3. Backup the XML files that need to be updated.


    # cp coreservicemodule.xml coreservicemodule.xml.save
# cp com.sun.hss.domain.xml com.sun.hss.domain.xml.save

  4. Remove the following lines from the coreservicemodule.xml file.

    <path-element>
     file:/opt/sun/n1gc/lib/activation.jar
   </path-element>
<path-element>
     file:/opt/sun/n1gc/lib/mail.jar
   </path-element>

  5. Remove the following lines from the com.sun.hss.domain.xml file.

    <path-element>
     file:/opt/sun/n1gc/lib/mailapi.jar
   </path-element>
   <path-element>
     file:/opt/sun/n1gc/lib/imap.jar
   </path-element>
   <path-element>
     file:/opt/sun/n1gc/lib/pop3.jar
   </path-element>
   <path-element>
     file:/opt/sun/n1gc/lib/smtp.jar
   </path-element>

  6. Add the following line to the com.sun.hss.domain.xml file.

    <path-element>
     file:/opt/sun/n1gc/lib/mail.jar
   </path-element>

  7. Start the N1 System Manager.


    # /etc/init.d/n1sminit start

Unable to Change a Server's agentssh Values (6347588)

Changing a server's agentssh value by using the set server command does not work.

Workaround: If you want to change a server's agentssh value, you must delete the server, discover it again, and use the add server command to set the agentssh value.

Cannot Set the fsusage.pctused Threshold on a Group of Servers (6347647)

Setting the fsusage.pctused threshold using the set group command does not work. For example:


N1-ok> set group test-systems threshold fsusage.pctused warninghigh=70 criticalhigh=80
Invalid value "fsusage.pctused".

Workaround: You must set the fsusage.pctused threshold on a single server by using the set server command. You can create an n1sh customized script to help automate this procedure for a large number of servers. See To Run a Script of N1 System Manager Commands in Sun N1 System Manager 1.2 Administration Guide for more information.

Resetting a Provisionable Server Makes the OS Health State Invalid Until the Server Information Is Refreshed (6351266)

After you reset (reboot) a provisionable server using the reset command or the Reset menu item in the browser interface, the server's OS resource health state changes to “Failed critical” until a refresh occurs after five to ten minutes. This happens even though the server's OS health state is good.

Workaround: After you reset a provisionable server, you can refresh the server using the set server refresh command, or wait five to ten minutes for the server's status to refresh automatically.