test

Sun Management Center 4.0 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

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.

Performance Reporting Manager Software Bugs

One Hour Data Is Not Plotted in the Graph for Custom Time Selection (6619000)

The Performance Reporting Manager graphs can be generated for a user specified time range. In the Sun MC 4.0 release Performance Reporting Manager graphs, if the lower bound of the range and the time at which the data was generated are the same, the point is not displayed.

Workaround: Include an additional interval of half an hour or one hour at the lower bound.

For example, if there is hourly data for a certain property starting at 5.30, 6.30 and so on till 11.30, and if the graph is requested for the range between 6.30 and 10.30, the graph does not include the data point at 6.30. However, if the range is between 6.00 and 10.00, all the points are correctly plotted.

perftool Process Does Not Run When Performance Reporting Manager Is Incrementally Installed (6615241)

Incremental Performance Reporting Manager installation in a whole root zone does not configure the Performance Reporting Manager agent module.

Workaround: Modify the /var/opt/SUNWsymon/cfg/zone-modules-d.dat file.

Seven Days Performance Reporting Manager Reports Generation Takes a Lot of Time for 10 Data Properties (6611541)

When the number of agents being monitored and size of performance data is high, say over 100, generation of reports for the data of the last seven days takes very long. Seven days is the time limit from the current date till which the historical data at the smallest detail level is retained in the database. The smallest detail level is hourly. So, this report requires the database to retrieve the largest amount of data. The data size increases when the number of data properties requested for are more. Eight days also puts the same amount of stress on the database, since it retrieves data for seven days.

Beyond eight days, the historical data is retained at daily, weekly, and monthly intervals. Hence report generation for time ranges of over eight days is faster.

Workaround: When the number of agents is high, reduce the time limit for hourly data from seven days to five days .

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

Zone Creation Operation Does Not Show All the Physical Networks (6813833)

The first step “Provide Zone Creation Attributes” in the zone creation wizard has a drop-down list to specify the network interfaces. This drop-down list has only the network interfaces that have been plumbed.

Zone Creation Fails When Resource Pool Is a Dedicated CPU Pool (6618997)

When the zone creation wizard is launched from a Host's context, the resource pool selection screen is displayed. If there is at least one running zone created with a dedicated CPU on the target, the pool list displays it's SUNWtmp pool for selection. Zone creation fails when the SUNWtmp pool is selected. Temporary pools are created as a result of dedicated CPU configuration and cannot be shared by two zones. The following error message is displayed:


Below are the log file contents of the zone you have entered. 
autoboot: No such property type usage: set = Sets property values. 
For resource type ... there are property types ...:

Workaround: Specify the dedicated CPU number or do not select a SUNWtmp pool for zone creation.

Whole Root Zone Migration Fails (6608767)

Whole root zone migration, including branded zone migration fails. Zone migration and copy, with contents, for a whole root zone might result in the following errors:

In addition to these errors, the following issues might also occur:

Workaround: Ensure that the following conditions are complete:

Zone Creation Does Not Display Privileges Selection Screens For Branded Zones (6600424)

The zone creation wizard consists of a screen to enter the default and optional privileges for zone configuration in the Solaris 10 11/06 and Solaris 10 8/07 releases. This screen is not displayed for branded zones.

Workaround: Modify the zone privileges using the Zone Properties page. The zone might need to be rebooted if the privileges are updated.

Alarm Created on a Project is Not Reflected at the Zone Level (6513203)

Install Solaris Container Manager 4.0 along with all the patches and create zones. Select any one of the rows of a default project of the newly created zones. When you click on Alarm Thresholds and create an alarm, the alarm is propagated on the left window pane but is not reflected on the zone which causes this alarm.

Workaround: None.

Unable to View Logs of the Renamed Zone (6512003)

When you type the new name of a renamed zone and click the Zone Log button, the following error message is displayed:


Zone Log Contents 
Below are the log file contents of the zone you have entered.
tail: cannot open input

This error indicates that the zone name is not valid. When you type the original name of the zone before it was renamed and click the Zone Log button, the following warning message is displayed:


Zone updated successfully
Zone updated successfully  
Configuring zone with the following attributes: 
zonename lzdeluth2  
Zone Rename successful.  
zoneadm: zone 'del2': WARNING: hme0:1: 
no matching subnet found in netmasks(4) for 10.12.174.155; 
using default of 255.0.0.0

Workaround: None.

Inconsistency While Renaming a Zone (6510926)

Rename a newly created zone and save the new name. Go to the resource Pool default page and the renamed zone is not reflected in the zone list. When you click on the zone, whose rename is not reflected, a new page is displayed. The right panel of this page is blank. The tree on the left panel is not expanded.

After renaming the zone, do not collapse the tree in the left panel. Refresh the system. The renamed zone is displayed on the right panel, but is not displayed under pool_default in the left panel.

Workaround: None.

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.