Sun Management Center 4.0 Release Notes

Sun Management Center Bugs

Blank Left Panel in GUI With Java Web Console 3.1 (6716572)

With Java Web Console 3.1, the left panel in the first page of GUI goes blank.

Workaround: Use Java Web Console 3.0.2.

SPARC Objects in Java Console Connected to x86 Server Do Not Have Physical View (6621460)

The hardware monitoring in the Sun MC 4.0 release consists of the Physical and Logical view feature. However, this feature is available only when the managed nodes are being monitored through a SPARC server. This feature is not available for SPARC managed nodes which are being monitored through an x86 server.

Workaround: None.

/etc/project Must Be Edited Before Performing Setup of the Sun MC 4.0 Server (6620423)

The db-start command might fail during setup of the Sun MC 4.0 server. Many error messages are displayed. For example:


db-start failed

Or:


Parsing errors for the topology-license-d.x file

Workaround: Edit the /etc/project file before performing setup of the Sun MC 4.0 server. The database user is commonly allocated resources from the default project in the /etc/project file. Edit the applicable line of the /etc/project file to contain the following values:


default:3::::project.max-shm-memory=(priv,5368708912,deny)

The value is generally derived to be equal to one third of the total memory available on the system.

If a new project is created for the database user, then edit the applicable line of the new project.

When Only the ASM Add-on Is Installed View Logs Is Not Displayed (6620258)

The View Logs tab is visible only when the ASM add-on is installed on the agent and the server. If the ASM add-on does not detect the Config Reader for the agent platform, the View Logs tab is not displayed. The Config Reader is another add-on, like the ASM, which is specific to the hardware that the Sun MC agent is being installed on.

Workaround: Install the applicable add-ons on all platforms. For example:

For entry-level platforms like T2K, T1K, and Sun Blades, the ELP Config Reader must be installed to get full fledged functionality on both the server as well as agent node.

No Help Page for Product Registration Client Link in Web Console (6620205)

The Tools->Register accordion link starts the Product Registration Client program which enables customers to register their assets to Sun for better service and support. There is no Online Help present for this link in the Web Console.

Workaround: None.

Java Console Should be Started in the Foreground for the First Time (6618460)

When the Java Console is started for the first time on a Solaris or Linux machine using the es-start -c command, the script queries the user whether to launch the Product Registration Client. The script then waits for user input. The command does not wait for user input when used the second time onward. If the console is started in the background, the script will wait in the background for user input and the console will fail to start.

Workaround: Start the Java Console in the foreground for the first time. If the console has been started in the background, use the fg command to bring it to the foreground.

es-restore -c and es-restore -f Commands Fail (6617356)

The following error message is displayed:


Operation failed

Workaround: None.

Left Pane Is Not Visible on Windows (6607610)

When the login console appears on Windows, the left pane is not visible. The width of the pane is 0.

Workaround: Drag the scroll bar to increase the width of the pane.

Context Sensitive Help is Not Displayed in Solaris Container Manager 4.0 (6604224)

In the Web Console, the same help topic is displayed when you click on any link to the Solaris Container Manager Online Help in any Solaris Container Manager page.

Workaround: None. Once the help window is opened, the user can click on the desired topic.

Database Migration Issues While Upgrading from Sun MC 3.6.1 to 4.0 (6601078)

Starting the Java Console after migration of server from Sun MC 3.6.1 to Sun MC 4.0 fails. The following error message is displayed:


Unable to load console info

Workaround: Type the following commands:


# es-stop -A

# es-start -A

Cannot Create a New Resource Pool on the Node With Only One Free CPU For the New Pool (6599728)

When only one free CPU is available during resource pool creation on Internet Explorer on Windows XP systems, resource pool creation appears to fail. The following error message is displayed:


No CPUs available for creation of new resource pools. 
At least 1 CPU should be free or available to create a new Resource Pool 
or a new Dynamic Resource Pool.

While it might appear that the resource pool creation fails, the pool is in fact created.

Unable to Proceed with Dedicated CPU Allocation on Mozilla (6593548)

Workaround: Use Firefox and Internet Explorer browsers instead of Mozilla for dedicated CPU allocation.

Base Keys for Health Monitor Missing in the Browser Interface (6586121)

Workaround: Log in as root. Type the following commands:

  1. /usr/sbin/smcwebserver stop

  2. /usr/sbin/smcwebserver start

Newly Created Objects Without Description Display Incorrect Description (6585734)

Newly created objects without a description display the description of the existing objects.

Workaround: None.

Cannot Log in to Java Web Console-based Browser Interface (6581898)

Workaround: Type the following commands:

  1. /usr/sbin/smcwebserver stop

  2. /usr/sbin/smcwebserver start

Base Keys Missing For Some Available Modules (6562150)

Workaround: After installation type the following commands:

  1. /usr/sbin/smcwebserver stop

  2. /usr/sbin/smcwebserver start

Base Keys Missing for All Physical View and Logical View Properties in the Browser Interface (6561661)

Workaround: Log in as root. Type the following commands:

  1. /usr/sbin/smcwebserver stop

  2. /usr/sbin/smcwebserver start

Severity of Alarm for LED Info is Unclear (6559204)

It is not possible to determine if the alarm for LED Info is critical or of medium severity. The severity has not been documented as well.

No error message is displayed. The screen displays Yellow alarms which represent warning alarms in Sun MC, for all values other than ON, of LED alarms.

Workaround: None.

X86Config Reader Displays Black Splat for Sun Fire X2100 Machines (6546750)

After installing the x86 Config Reader on the Sun Fire X2100 systems, type es-start -c to open the Java Console. When you select the Module Browser, the x86 Config Reader is displayed under the Hardware tab. A black splat is displayed against LED Info even after running Sun MC 4.0 for over 24 hours.

Workaround: None.

Product Registration Client Launch and Usage

After any console installation the Product Registration Client is started with the es-start -c command for the first time. The scripts do not report any errors found by the Product Registration Client. The client will also not be restarted if the registration is not completed successfully.

Workaround: Restart the Product Registration Client by clicking on Tools -> Register. You could also use the Java Web Console-based browser interface Tools -> Register accordion link.

Messages Related to Product Registration Client Appear in English

Messages related to Product Registration Client startup and also Product Registration Client are not localized. You can start Product Registration Client as follows:

During Reconfiguration, es-guisetup Does Not Update the SNMP Port of the Agent (6372597)

Workaround: Use the es-config command to change the SNMP port of the agent.

In Netra 1290 Systems, Hardware Summary Table Is Not Present After Unconfiguring or Configuring a Disk (6395211)

Workaround: Close the Host Details window and open it. The Hardware Summary table will be displayed.

Physical View of System Is Set to Front View Irrespective of Current View (6396604)

In the Hardware tab of the Details window, the physical view of system is set to the front view irrespective of the current view. Also, the history shows only the front view.

Workaround: None.

After Agent Upgrade, Agent Values Are Not Updated Automatically for x86 & Linux Hosts (6410213)

When a Solaris x86 or Linux agent is upgraded either through the CLI/GUI installer or through Agent Update, the updated information is not automatically reflected in the topology.

Workaround: After the agent upgrade, modify the topology object manually.

Sun Management Center Services Cause cryptosvc Service to Log Errors During Boot or Reboot of the System (6334872)

When Sun Management Center services attempt to start after rebooting the system, they step onto cryptosvc service and kcfd daemon causing them to log errors in /var/adm/messages.

The following error messages might be displayed:


Oct  3 18:16:09 atqa32 lomv: 10/3/2005 23:16:9 GMT LOM time reference

Oct  3 18:16:13 atqa32 kcfd[106]: kcfd: elfsign_hash_mem_resident failed
to hash for /usr/lib/security/pkcs11_softtoken.so: sign or verify of ELF
object failed

Oct  3 18:16:13 atqa32 kcfd[106]: kcfd: elfsign_hash_mem_resident failed
to hash for /usr/lib/security/pkcs11_softtoken.so: sign or verify of ELF
object failed

Oct  3 18:16:13 atqa32 esd[1949]: libpkcs11:
/usr/lib/security/pkcs11_softtoken.so signature verification failed. See
cryptoadm(1M). Skipping this plug-in.

Oct  3 18:16:13 atqa32 esd[1949]: libpkcs11:
/usr/lib/security/pkcs11_softtoken.so signature verification failed. See
cryptoadm(1M). Skipping this plug-in.

Oct  3 18:16:13 atqa32 cfgserver[1949]: syslog   Oct 03 18:16:13
cfgserver     Unable to get pkcs session. Can not initialize snmp engine

Oct  3 18:16:13 atqa32 cfgserver[1949]: syslog   Oct 03 18:16:13
cfgserver     *** terminating execution ***

Workaround: Before rebooting the system, stop all Sun Management Center services using es-stop -A. When the system reboots, all services will start without errors.

(Solaris 10) Sun Management Center Services Are Stopped During Boot (6336538)

On Solaris 10 systems, Sun Management Center agent services are stopped during boot.

The following error messages might be displayed:


Oct 12 09:19:59 atqa33 metadata[6245]: [ID 985908 daemon.alert] syslog

Oct 12 09:19:59 metadata      {received software termination signal}

Oct 12 09:19:59 atqa33 metadata[6245]: [ID 122441 daemon.alert] syslog

Oct 12 09:19:59 metadata      *** terminating execution ***

Oct 12 09:19:59 atqa33 event[27957]: [ID 652029 daemon.alert] syslog

Oct 12 09:19:59 event         {received software termination signal}

Oct 12 09:19:59 atqa33 event[27957]: [ID 721961 daemon.alert] syslog

Oct 12 09:19:59 event         *** terminating execution ***

Oct 12 09:19:59 atqa33 agent[28990]: [ID 651061 daemon.alert] syslog

Oct 12 09:19:59 agent         {received software termination signal}

Oct 12 09:19:59 atqa33 agent[28990]: [ID 891934 daemon.alert] syslog

Oct 12 09:19:59 agent         *** terminating execution ***

Workaround: Before rebooting the system, stop the services using es-stop -A. In this case, error messages are not logged into the syslog file.

Individual Users Are Not Added to the ACL of the Server Support Module (4843429)

If you delete the esadm group from the ACLs of the agent and then add individual users to the ACL of the agent, the user is not automatically added to the ACL of the server support module. Because the server support module is not updated with the user, the server support module does not allow enabling or disabling of the Performance Reporting Manager. This message is displayed:


Unable to enable/disable PRM data collection on an agent with new user

Workaround: Add the esadm group to the ACL of the agent and then add the individual users to the esadm group.

Sun Management Center Console Login Screen Does Not Accept Keyboard Input on Linux Machine With JDK 1.5 (6294368)

Workaround 1: Follow these steps:

  1. Minimize the login screen and restore.

  2. Type the input in the field that has the active cursor.

  3. Position the cursor in the next field.

  4. Minimize the login screen and restore.

  5. Type the input in that field.

Workaround 2: Use JDK 1.6 or compatible versions.

When Filter Criteria Exclude Single or Multiple OS, Sun Management Center Discovers Those OS Machines (6403422)

Workaround: None.

Platform Type List in the Filter Criteria Contains Wrong Entries for Zone and x86-generic-pc (6419443)

Workaround: None.

Java Exceptions Are Thrown in Manage Jobs Dialog (6346065)

Workaround: Task creation may fail when CST service is running. Use es-stop -x to stop CST service.

probeServer Does Not Return All Messages Written to stdout After it Finishes an adhoccommand on ppc (6415353)

Workaround: Put sleep of two to three seconds in the called script.