test

Sun Management Center 3.6.1 Release Notes

Chapter 2 Runtime Issues

Issues include information that you should know about, such as, prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues. Bugs have tracking numbers shown in parentheses. For updates on bugs and for patches, see the SunSolveSM web site at http://sunsolve.sun.com.

Sun Management Center Bugs

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.

Help Button in Java Console Points to Sun Management Center 3.6 Document Collection (6413942)

When you click the Help button in the Java console, it points to Sun Management Center 3.6 Document Collection instead of Sun Management Center 3.6.1 Document Collection.

Workaround: For Java Console help, edit the sunmc.docs.path entry in the /var/opt/SUNWsymon/cfg/javaconsole.properties file as follows:

sunmc.docs.path=docs.sun.com/app/docs/coll/810.8?

For Web Console help, edit the sunmc.docs.path entry in the /opt/SUNWsymon/web/console/smwebconf/smwebconf.properties file as follows:

sunmc.docs.path=docs.sun.com/app/docs/coll/810.8?

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.

Image Creation for SPARC Systems Is Allowing X86/X64 Config Reader Add-on (6410846)

On Solaris SPARC systems, Agent Update allows you to create an image that contains the X86/X64 Config Reader add-on. However, this add-on will not be installed on Solaris SPARC systems.

Workaround: While creating images for Solaris SPARC systems, select only the add-ons that are applicable.

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.

Duplicate Entries in Sun Management Center Database (5051992)

Sun Management Center database can contain duplicate entries of hosts when one of the following scenarios occurs:

Workaround:

Follow these recommendations to avoid duplicate entries:

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.4 or compatible versions.

MCP Does Not Work With Zone Agents (6342054)

When a zone agent is used as the base agent, Module Configuration Propagation (MCP) does not work with zone agents. Propagating the configuration data from MCP to a zone agent also fails.

The following error messages are logged in taskreq.log when MCP propagation with zone agent as base fails.


Http error : HTTP/1.1 404 File not found: 
/var/opt/SUNWsymon/mcp/procmon-zoneagentbase/index.xml

The following error messages are logged in taskreq.log when MCP propagation to zone agent fails.


Operation mcp has failed on target:hostname:1161 Exception was thrown: 
/usr/bin/nawk: 
can't open file /var/opt/SUNWsymon/cfg/base-modules-d.dat.MCP

Workaround: Edit the /var/opt/SUNWsymon/zone-scripts-d.dat file of zone agent to include es-mcp-get and es-mcp-put script names.

MCP Does Not Propagate all the Module Parameters to the Agent on a Whole Root Zone (6420023)

Workaround: None.

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

Workaround: None.

Sun Management Center Does Not Discover Hosts When Filter Criteria Are of Platform Types With Given IP Address Range (6341225)

Run a Discovery request by specifying an IP range and selecting specific platform types. The request does not discover an object(s) if ALL the following conditions are true.

  1. Default port option is selected in the Discover request.

  2. Additional port to search on is also specified.

  3. Both the default and additional ports are occupied on the host(s) being searched.

Workaround: Create separate Discover requests for Default port and additional port, if you want check both default port and an additional port on the objects being discovered.

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.

Localization Bugs

Help Command in CLI Shows Incorrect Product Version (6408902)

The about and legal parameters of the help command in the command-line interface show the incorrect version of the product.

Workaround: None.

GUI Setup: Next Button Is Enabled on Performance Reporting Manager Setup Progress Panel (5029528)

Clicking the Next button while the Performance Reporting Manager database is being set up might cause errors.

Workaround: Do not click the Next button while the Performance Reporting Manager database is being configured.

Netscape 4.7.x Displays Pages Incorrectly in Simplified Chinese Locales (zh_CN.GBK and zh_CN.GB18030) (4864462)

The page text in the Simplified Chinese locales, zh_CH.GBK and zh_CN.BG18030, is garbled when viewed in the NetscapeTM version 4.7.x browser.

Workaround: Specify a different browser as your default browser. The following browsers are known to work correctly in these locales:

Volume System Monitoring (VSM) Bugs

Spaces in the OS Version are Misrepresented in the Rules Window (6344665)

If the OS version in the OS table includes a space, this space is misrepresented in the Rules window.

Workaround: Use ASCII characters to define OS version.

Web Console Throws Apache Server Error for OS Object Table (6330990)

If the OS objects are not initialized, the web console displays the error page.

Workaround: Use Java Console to display the data.

Container Names Having Multibyte Strings are Misrepresented in the Console (6343127)

Assume that multibyte strings are used in container names that are created using the Sun N1TM System Manager (N1SM) GUI. In this case, the container names are misrepresented in the Sun Management Center Console at the following places in the Host Details window:

1. Module Browser tab -> Hardware -> VSM module -> VSM object -> Container object -> Container Name in the Containers Table

2. Module Manager tab -> VSM module -> Rules -> Attribute Name list

Workaround: Sun Management Center does not support multibyte strings in data fields. Hence, use ASCII characters for container names to integrate Sun Management Center with N1SM.

Hardware Diagnostic Suite Software Bugs

Hardware Diagnostic Suite enctest Might Not Report Power Supply Status (4908213)

A full Hardware Diagnostic Suite test on the enclosure for a Sun StorEdge D1000 might still report a noncritical error, such as a pulled power supply cable, even after the problem has been fixed.

Workaround: Restart the Sun Management Center agent connected to the Sun StorEdge D1000 system.

Incorrect Error Message Displayed if JAVA_HOME Path Is Set to Value Longer Than 80 Characters (4854768)

If the JAVA_HOME path is set to a value longer than 80 characters, the following incorrect error message is displayed:


Could not start Hardware service

You can check that the Hardware Diagnostic Suite is running by typing:


% ps -ef | grep HWDS

Workaround: Ignore this error message. The Hardware Diagnostic Suite starts correctly.

Hardware Diagnostic Suite Runs Improperly Inside a Local Zone (6337001)

Hardware Diagnostic suite is expected to run only inside a global zone. Due to a bug in the setup scripts of Sun Management Center, Hardware Diagnostic Suite runs improperly inside a local zone.

Workaround: Do not run the Hardware Diagnostic Suite inside a local zone.

Performance Reporting Manager Software Bugs

Problem With Java Service Causes Performance Reporting Manager to Fail to Collect Agent Data (4855306)

If 15 or more Performance Reporting Manager report requests are scheduled to run simultaneously, you might encounter one or more of the following problems after the software has been running for a period of time:

For some of the previously mentioned problems, the console might display the following error message when you launch the Manage Jobs GUI:


Task Service is not available

Similarly, for some of these problems, the console might display the following error message when you launch the Report Manager GUI:


Report Service is not available

Workaround: When you encounter this problem, stop and restart your server components. Type the following commands:


# es-stop -A


# es-start -A

To avoid this problem, do not schedule more than 15 report requests to run simultaneously. Space the run time of scheduled requests over a period of time. For example, if you have 20 requests required to run every hour, split the requests into two separate batches, each containing 10 requests. Schedule the batches to run at 15–minute intervals. Do not schedule the batches to run simultaneously.

Alarms Reports Not Filtered Correctly When All Hosts Option Is Selected (4788475)

Alarms logged against agent machines are not filtered correctly in Alarms Reports when the All Hosts option is selected and a filter is specified.

When the All Hosts option is selected along with a filter, the specified filter criteria are applied to all the alarms that are logged for all the hosts. The filtered alarms are returned in the report output. Additionally, the report includes any Agent Not Responding alarms and Host Not Responding alarms from all monitored hosts. The specified filter criteria are not applied to such alarms.

Workaround: This problem can be avoided by explicitly specifying host names for Alarms reports. Choose from the following workarounds:

Service Availability Manager Software Bugs

Empty Cell Values for IMAP4 Modules on x86 Systems (5032172)

Rows added to the Service Measurement table of the Service Element for IMAP4 and Synthetic Transaction for IMAP4 modules come up with empty (zero) cell values. Adding rows after these modules have been unloaded and reloaded fails with the following message:


Row with following index exists:nnn

The bug might cause the Service Element for IMAP4 and Synthetic Transaction for IMAP4 modules to fail on x86 systems.

Workaround: Ensure that a Synthetic Transaction for IMAP4 module is loaded on a SPARC agent host to monitor IMAP services running on x86. The loaded module needs to be configured to probe the IMAP service on the x86 system.

Modify Service Object Dialog Box Might Not Accept Characters on Microsoft Windows 2000 Systems (4738717)

The Modify Service Object dialog box on a Microsoft Windows 2000 system might not accept characters in certain text fields when you are running the Java runtime environment, version 1.3.1 to version 1.4.0. When you attempt to change the service type value from the default of HTTP, characters provided for the Hostname and Instance text fields are not accepted.

Note –

This problem does not occur if you are running the Java runtime environment version 1.4.1.

Workaround: Before using the Modify Service Object dialog box, install the Java runtime environment version 1.4.1 on Microsoft Windows 2000 systems.

Solaris Container Manager Bugs

CLI Installation of Sun Management Center Is Not Translated

If you use the command line interface (CLI) version of the Sun Management Center installation, it is only available in English language. This version is not translated. The English language aspect does not affect the installation process or functionality.

Workaround: To perform the installation in your locale, use the GUI installation (es-guiinst) and setup (es-guisetup).

Utilization Graph Image Titles and Headings Appear in English Language

If you choose a locale other than English, the title and headings of the Utilization Graph image appear in English language. These values are not localized.

SPARC: Extended Accounting Feature Is Disabled in Solaris 8 Release

The Extended Accounting feature is disabled in Container Manager on systems that run the Solaris 8 OS. As a result, the Extended Accounting Data (Exacct) column of the CSV file for a container on a Solaris 8 system will be null.

Some Projects in the /etc/project Database Might Not Be Discovered by Container Manager

If a project in an agent host's /etc/project database has the same project ID as a project in the Sun Management Center database but has a different project name, then the project will not be discovered by Container Manager. A unique project ID across all hosts in the same server context is a Container Manager requirement.

You should not use the projadd command to create projects. Use only Container Manager to manage projects.

Workaround: Delete the nondefault project that was created by the projadd command from the agent host's /etc/project database and create the container by using the New Container wizard in Container Manager.

Security Privilege Error Messages Are Incomplete

Error messages displayed during failure of creation, modification, or deletion of Zone, Pool, or Project are incomplete and do not provide enough details. Following are the error messages you might encounter:

Workaround: If you encounter any of the previous errors, refer to the profile recommendations that follow. Before this, ensure that the user is a valid Sun Management Center user and has the necessary administration privileges (part of esadm, esdomadm groups).

Ensure that the user is associated with the necessary profiles by running the following command:

$ profiles <username>

Following are the necessary profiles:

If you find the necessary profiles missing, run the following command (as the superuser) and modify the profiles associated with a user:

# usermod -P "<comma separated list of necessary profiles>" <username>

If any profile does not exist on the system, add the missing entries in the following format to the prof_attr file in the /etc/security directory.

Pool Management:::Resource pool management profile:help=RtPoolMgmt.html

Project Management:::Manage Solaris projects:auths=solaris.project.read,solaris.project.write;help=RtProjManagement.html

Run the following command to find if the user is a part of the local access user list for the SCM module.

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -s

If user is not part of the access list, run the following command:

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -l <user_name>

Agent Performance Becomes Degraded or Unresponsive (6247892)

An agent has crashed leaving scm-container* files in the /var/opt/SUNWsymon/cfg/ directory. When the agent restarts, it might not perform in an optimal manner. This condition might identify itself by the following error message:

Insufficient security privilege to complete the operation.

You can determine the state of the processes on the agent by typing the following command:

% ps -eaf | grep esd

Workaround: To improve performance, type the following commands:

  1. Become superuser.

    % su -

  2. Stop the agent.

    # /opt/SUNWsymon/sbin es-stop -a

  3. Delete the state files.

    # rm /var/opt/SUNWsymon/cfg/scm-container*

  4. Restart the agent.

    #/opt/SUNWsymon/sbin/es-start -a

Java Web Console Does Not Restart After Reboot (6252233)

Following a server reboot, the Java Web Console does not start automatically.

To start the Java Web Console, type the following commands:

  1. Become superuser.

    % su -

    Type root password.

  2. Restart the Java Web Console.

    # /usr/sbin/smcwebserver restart

  3. Ensure that Java Web Console restarts in the future.

    # /usr/sbin/smcwebserver enable

Workaround: None.

Zone Creation Fails When Invalid Locale Is Selected (6259233)

If an invalid locale is selected from the Locale drop-down menu in the New Zone wizard, zone creation fails. The Locale drop-down menu might contain invalid locale values.

To determine valid locales, go to “Supported Locales” in International Language Environments Guide.

Workaround: Choose a valid locale from the Locale drop-down menu in the New Zone wizard. If you are unsure of a locale value, select C for the English locale.

Tool Tip Displayed Instead of Alarm Badge (6219617)

If an alarm condition exists, the tool tip of the alarm badge might appear instead of the alarm badge itself.

If you navigate to another pane, then return to the alarmed object's icon, the badge on the icon is correctly displayed.

Workaround: None.

Exception Might Occur When Clicking the Browser Back Button (6241424)

When you click the browser back button, Container Manager might throw an exception. The browser back button is not supported in this release.

To recover from this exception, go to https://server_name:6789/containers and navigate to the appropriate page.

Workaround: None.

Some Processes Owned by User nobody Are Not Moved to a Container (5011290)

On the Solaris 9 Operating System, some processes, for example, the JavaTM application run by user nobody, are not moved to a container because of a bug in the newtask command.

Workaround: Start the applications that are run by user nobody in the appropriate container by using the newtask command.


# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Using nscd as a Match Expression Causes Host to Hang (4975191)

If you use one of the following match expressions when creating a container definition and subsequently activate it, the agent host hangs:

Workaround: Start the nscd process in the appropriate project by using the newtask command:


# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Agent Hosts Missing After Reinstalling or Running Setup of Server Layer (4964051)

If you plan to reinstall the Sun Management Center software on the server layer, be sure to save the data when uninstalling. Similarly, if you run setup again on the server layer, be sure to answer No when asked if you want to recreate the database. Otherwise, agent hosts previously discovered might be missing from the database if the data was not saved and you then reinstall or set up again on the server layer.

Workaround: If hosts are missing after you reinstall or rerun setup, restart the Sun Management Center agent on the hosts by doing the following procedure:

  1. Log in to agent system.

  2. Become superuser.

    % su -

  3. Stop the Sun Management Center agent by typing:


    # /opt/SUNWsymon/sbin/es-stop -a

  4. Start the Sun Management Center agent by typing:


    # /opt/SUNWsymon/sbin/es-start -a

zlogin -C Is Required After Creating a Zone (6388082)

To access a zone that is present in other physical machine, type zlogin -C <zone-name> from the global zone and set up the zone.

In the Name Server field of zone creation, type the name server value followed by IP address. For example, the value in the Name Server field could be ns1.sun.com (10.255.255.255).

Add-On Config Readers Bugs

es-validate Command Reports Inconsistent Version Numbers Between English and Other Language Installations (6331558)

Localization packages for Entry-Level Platform (ELP), Netra, Desktop/Workstation, and Workgroup Server add-on software are not updated in this release because no change is needed since the two previous releases.

Workaround: None.

PICL Might Not Interpret Some System Configuration Changes on Low-End and Midrange Systems (6243759)

This issue occurs in the ELP, Netra, and Desktop/Workstation config readers.

On Netra 240/440/T4, Sun Blade 100, and Sun Fire V240 servers that use Solaris 10 software, Platform Information and Control Library (PICL) might not interpret some system configuration changes after initialization, such as the bge1-bge3 drivers. The instances for these drivers are reflected in the output of the prtconf -v command but not in the output of the prtpicl -v command.

Workaround: Realign PICL with the prtconf utility by issuing the svcadm restart picl command.

Netra Bugs

PICL Daemon Must Be Restarted After Dynamic Reconfiguration (6247392)

After a dynamic reconfiguration (DR) operation with the cfgadm command on a system board with Solaris 10, several values in the config reader tables are either not displayed, or are displayed as '--'. The following config reader table entries are affected:

The Hardware Summary and Physical View are also affected. The values for the Hardware Summary are displayed as '--' and the Physical View does not display the graphics for the system.

Workaround:

Restart the PICL daemon after a DR operation with the following commands:

For Solaris 8 and 9 systems:

% /etc/init.d/picld stop

% /etc/init.d/picld start

For Solaris 10 systems:

% svcadm restart svc:/system/picl:default

PICL Daemon Must Be Restarted After Dynamic Reconfiguration of DC PSU Type D142 on Netra 1280 Servers (6247392)

The PICL daemon is not updated after a DC PSU Type D142 is dynamically reconfigured on Netra 1280 servers.

Workaround: Restart the PICL daemon after a DR operation with the following commands:

For Solaris 8 and 9 systems:

% /etc/init.d/picld stop

% /etc/init.d/picld start

For Solaris 10 systems:

% svcadm restart svc:/system/picl:default

DC Power Supply Fields A and B Reversed (6277372)

Reports for the DC Power supply fields A and B are incorrectly reversed. If A is faulty and B is OK, Sun Management Center reports that B is faulty and that A is OK and vice versa.

Workaround: None.

Internal Devices Not Detected During Dynamic Reconfiguration Operations (6326558)

Internal devices such as disk and network are not detected during the removal process of DR operations on Solaris 10 systems.

Workaround: Restart the PICL daemon after a DR operation with the following command:

% svcadm restart picl

The workaround might not enable the agents that run on Solaris 10 systems to detect when the removal, insertion, or reconfigure operations of internal devices (disks, network) occurred.

Workgroup Server Bugs

Selecting the Alarm Tab on Sun Fire V880 and Sun Fire V480 Servers Causes Alarm Alert Messages (6317433)

On Sun Fire V880 and Sun Fire V480 servers with two objects, an Alarm Alert message similar to the following appears when you select the Alarm Tab on the discovered object.

The following alert message might be displayed:

Unable to get event management information from agent. Agent was busy or down. Will default to local event manager.

Most likely, this alert message is incorrect and the agent is working properly.

Clicking OK causes the alarm tab table to default to local event management. If the detail window of the discovered object is closed and opened again, clicking the alarm tab causes the same alert message to be displayed.

Workaround: None.

Incorrect Processor Type in Hardware Rules Table of Sun Fire V890 Servers on Solaris 10 (6318026)

Sun Fire V890 servers are shipped with UltraSparc-IV processors. However, the Property column of the Hardware Rules table incorrectly displays “Correctable Memory Error, Ultra Sparc III” and “I/O Correctable Error, Ultra Sparc III” as the processor type.

Workaround: None.