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 SunSolve^SM web site at http://sunsolve.sun.com.

Localization Bugs

fr (French Locale): Manage Jobs - Set Schedule Menu Does Not Display Correctly (5033595)

Workaround: Enlarge the window horizontally.

After es-validate Is Run, Error Message Says Bad string for Server Hosts Definitions in domain-config.x (5022045)

There is no problem in the definitions in domain-config.x.

Workaround: Ignore the message.

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.

Some Mnemonics Do Not Work in Non-English Locales (5008434, 5040616, 5040617)

Using the mnemonic (shortcut) for the following operations might not work in some non-English locales:

• Create Object > Segment tab

• Manage Jobs > New Task

• Manage Jobs > Add Task

• Logging Setting

• PRM > Export Data > Save

Workaround: Use the mouse to perform the operation.

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 Netscape^TM 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:

• Netscape^TM 6.2.2

• Netscape 7.x

• Mozilla^TM

• Microsoft Internet Explorer

Netscape 4.6.x Displays Help Pages Incorrectly in Traditional Chinese Locale (zh_TW.UTF-8) (4880488)

Pages displayed by clicking the Help button in the Traditional Chinese locale (zh_TW.UTF-8) are garbled when using the Netscape version 4.6.x browser.

Workaround: To avoid this problem, specify a different default browser, such as Netscape 6.x or later.

Sun Fire Link Traditional Chinese Help Buttons Point to Incorrect Locale (4856610)

For Traditional Chinese users, some of the Sun Fire^TM Link Help buttons are displayed in Simplified Chinese. Help pages that are displayed in Simplified Chinese instead of Traditional Chinese include the Manage All Partitions and Manage Registered Nodes dialog boxes buttons.

Workaround: Use the Help button on the Fabric Details console to view the correct help pages. The Fabric Details console is the main graphical user interface (GUI) for Sun Fire Link.

Sun Management Center Bugs

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 does not get 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 Incorrectly Reports That a Successful Agent Update Has Failed (4994784)

The Job Manager user interface shows Failed for a successful agent update operation. When the agent update operation is performed using the Manage Jobs GUI (graphical user interface), the status of the operation is shown as successful or failed at two different levels.

• Summarized status: If the operation was attempted on multiple hosts and if it fails even on one of the hosts, the status of the entire Job is stated as Failed.

• Individual status: By clicking the View logs button in the GUI, you can view the status of the operation on the individual host.

• The upgrade was successful, but the SNMP port of the agent was changed as a result of agent upgrade that involves reinstall and reconfiguration.

• The upgrade was successful but the SNMP request timed out due to various other factors and the status was not communicated back successfully.

• The upgrade was successful, but the process took more than the 30–minute timeout set by the server for each individual host. As a result the server thread waiting for status update was terminated before the status report was initiated from the agent side.

Workaround: Use the View Logs tab of the server host details window to see the InstallServer.log on the server host. The details of the operation are available in /var/opt/SUNWsymon/install/agent-update.log of each target host on which the operation is performed.

Module Configuration Propagation (MCP) Does Not Work Through Firewall (4796734)

Module Configuration Propagation (MCP) reads and writes to the Sun Management Center web server through a single predefined port. The default port is 8080. If the web server sits behind a firewall, MCP has no problem reading from the web server, but will have a problem writing to the web server. Once the web server has established a connection with MCP, the server arbitrarily assigns a port to do its job. You cannot specify which port number the web server should assign.

Workaround: None.

Hardware Diagnostic Suite Software Bugs

Serial Port Break Sequence (4912141)

Testing the serial port on a system with an active terminal connection (TIP session) to a second system causes the second system to go to the OpenBoot PROM OK prompt. The break sequence is part of the test on the serial port. No notification is provided that a break sequence will be sent to the Sun Management Center console.

Workaround: If the second system has a keyswitch, set the keyswitch to the lock position to prevent the reaction of the break sequence. In addition, on the second system, type the following command before the test is run.

# kbd -a disable

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 non-critical 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 -aef | grep HWDS

Workaround: This error message can be ignored. The Hardware Diagnostic Suite starts correctly.

Slow Memory Leak Might Cause Sun Management Center 3.5 Update 1 to Crash (4852628)

When running multiple long-term processes on a server through the Hardware Diagnostic Suite console, a slow memory leak might occur. If additional free memory is not available on this server, Sun Management Center 3.5 Update 1 might crash and possibly dump core.

Workaround: None. The server must be restarted.

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 at the same time, you might encounter one or more of the following problems after the software has been running for a period of time:

• Data is not collected from agent machines

• Some report requests remain in a run state indefinitely

• Report requests cannot be scheduled as desired

• Grouping task requests cannot be scheduled as desired

• The Report Manager GUI cannot be launched

• The Manage Jobs GUI cannot be launched

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 at the same time. 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 at the same time.

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:

• When generating an Alarms report for a single host, either select the host name by providing the hostname:port, or select the host name from the Sun Management Center topology view.

• When generating an Alarms report for multiple hosts, either provide the different host names as hostname:port in a comma–separated list, or select the multiple host names from the Sun Management Center topology view.

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 not work on x86 systems.

Workaround: Make sure 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.

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.

Sun Enterprise 6500/5500/4500/3500 Server Bugs

Tape Drive Errors Might Be Displayed When Running Config Reader (4846230)

If you run the Sun Management Center Config Reader on a system with an IBM LT0 tape library attached, the following tape error might be displayed at intervals:

Periodic head cleaning required.

Workaround: Ignore the error messages. The tape library and Sun Management Center software continue to run.

Sun Fire 15K/12K Systems Bugs

Platform View Updates Slowly Following addboard With SMS CLI (4997917)

After you perform an addboard operation at the command line in System Management Services (SMS), you might need to wait 10 minutes to update the corresponding Sun Management Center Platform view.

Workaround: Wait up to 10 minutes for the Platform view to be updated.

Platform Icon Might Not Be Visible on Right Panel of Sun Management Center Console (4864183)

After you create a Sun Fire High-End (15K/12K) platform object, the platform icon view, which is located on the right panel of the Sun Management console, might not be visible.

Workaround: Choose from the following two workarounds:

• If you have no need to use the platform icon, use the hierarchy that is located on the left panel of the Sun Management Center console for navigation.

• If you prefer that the platform icon is visible, use the following command to copy the icon file into the appropriate directory:

  # cp /opt/SUNWsymon/classes/base/console/cfg/topoimages \ sf15000-platform-xlarge.gif /var/opt/SUNWsymon/cfg/deviceimages \ Starcat-sf15000-platform-xlarge.gif

  ---

  Note –

  The new file name is different from the original file name.

  The backslash (\) is a UNIX token that indicates a continuation of the command line.

  ---

Move Board Dialog Box Does Not Indicate Completion of Operation With Sun Fire High-End (15K/12K) Systems (5029907)

After performing a Move Board operation in the graphical user interface (GUI), you can track its status in the progress section of the Move Board dialog. However, there might be instances when an operation is successful but does not display a completion message.

Workaround: Use either the GUI or command-line interface (CLI) to verify whether the operation has completed.

• GUI – Close the Move Board dialog box and open the Show Status dialog box to view any messages related to the operation. The message No status from the agent indicates that the operation has completed.

• CLI – The output of this command executed on the SC tells you whether the operation has completed:

  % ps -ef | grep moveboard

Confirmation Dialog Boxes for Domain DR Operations Can Be Edited (5027103)

The following domain DR operations result in confirmation dialog boxes that can be edited:

• Detach, Attach

• Unassign, Assign

• Power On, Power Off

Workaround: Editing the contents of these dialog boxes does not affect Sun Management Center 3.5 functionality. Click the OK or Cancel button.

Domain Views Might Display Erroneous Domain ID Status for High-End (15K/12K) Systems (5028738)

With Sun Fire 15K/12K systems, the Domain view for a slot board sometimes displays an erroneous domain ID. When a slot board is listed in the ACL list with a given domain ID n, that domain ID n remains even after the board has been unassigned from the domain in that view.

Workaround: To determine the correct domain ID, check the Platform view, rather than the Domain view.

Sun Fire Midrange Systems Bugs

Power Off Option Not Available for System Controller (4978501)

When you press mouse button 3 on a system controller (SC) listed in the Platform Administration -> Slots -> SC table, the menu does not provide a power off option.

Workaround: Use the command-line interface (CLI) to power off the system controller.

Power On and Power Off Option Not Available for Power Supplies (4979650)

When you press mouse button 3 on a power supply listed in the Platform Administration -> Slots -> Power Supply table, the menu does not provide a power on/power off option.

Workaround: Use the command-line interface (CLI) to power on or off the power supply.

Node Names in CPU and I/O Boards Tables Display Incorrectly After Hot-Plug Operation (4989067)

The node names in the Platform Administration -> Slots -> CPU table and I/O Boards table are missing after a hot-plug operation.

Workaround: Use the Refresh button to refresh the table and display the correct values.

No Error Message on Status Window That WPCI Board Cannot Be Dynamically Reconfigured (4989685)

If you try a dynamic reconfiguration (DR) operation on the Sun Fire Link peripheral component interconnect (WPCI) Board in the DR module -> Attachment Points -> WPCI Board table, the status window does not show an error message that you cannot dynamically reconfigure that WPCI board.

Workaround: Use the command-line interface (CLI) to dynamically reconfigure the WPCI board.

Use Logical IP Address to Create Platform Administration Agent When Logical Address Is Set (4992956)

If a logical Internet Protocol (IP) address is already set in the system controller using the setupplatform -p sc command, you need to use a logical IP address when you set up the system controller in the Platform Administration module. Otherwise, you see a black splat and all the tables in the Platform Administration module are empty.

Workaround: Use the showplatform -p sc command to check whether the system controller has a logical IP address already set. If so, set up the logical IP address for the system controller in the Platform Administration module.

Sun Fire Link Bugs

Using Sun Fire Link With Network Address Translation (4948690)

To use the Sun Management Center with Sun Fire Link in a Network Address Translation (NAT) environment, you must first install a patch.

Workaround: Choose a patch according to the version of Solaris that you are running:

• Solaris 8 Platform: Patch 116164

• Solaris 9 Platform: Patch 116162

Sun Fire Link Dialog Boxes Might Display Erroneous Information (4984273)

When using the Sun Fire Link graphical user interface (GUI) with Sun Fire midrange systems, you might encounter unexpected behavior. Dialog boxes sometimes do not close when you click the OK button. Status messages in dialog boxes might sometimes reflect outdated information.

Workaround: If you encounter this behavior, use the command-line interface (CLI) instead of the GUI for up-to-date status information.

Node Failure During Link Bring-Up Might Cause Sun Management Center Console and Fabric Details Windows to Freeze (4857941)

If a node fails after a cluster has been configured but before all the links have been powered up, the Sun Management Center console and Fabric Details windows might freeze.

Workaround: Apply a patch according to the version of Solaris that you are running:

• Solaris 8 Platform: Patch 116164–02

• Solaris 9 Platform: Patch 116160–01 and 116162–01

Striping Level 1 for Sun Fire Link Switch Configuration Not Supported (4858050)

If you select a striping level of 1 for a Sun Fire Link Switch configuration, the striping level is automatically upgraded to a 2. However, that level is not reflected in the Fabric Details window of the Sun Management Center console.

Workaround: Apply a patch according to the version of Solaris that you are running:

• Solaris 8 Platform: Patch 116164–02

• Solaris 9 Platform: Patch 114995–02 and 1161612–01

Sun Management Center Is Slow to Update Link Status When a Cluster Node Goes Down (4644785)

If a cluster node goes down while the link status is being displayed in the Fabric Details window, the Sun Management Center console might not update the status of the affected links for an hour or more. Moreover, if the cluster node is restored, and the links are re–established, the Fabric Details window might continue to display the links as down.

Workaround: Apply a patch according to the version of Solaris that you are running:

• Solaris 8 Platform: Patch 116164–01

• Solaris 9 Platform: Patch 116162–01

Sun Fire Link Interconnect Fabric Name Is Not Updated When a New Fabric Is Loaded (4771624)

If you unload and stop a fabric and then load another fabric with a different name, the Sun Fire Link (SFL) object icon that is displayed in the Sun Management Center console window retains the name of the removed fabric. However, the Fabric icon label shows the name of the new fabric.

Workaround: After unloading and stopping the fabric that you want to replace, delete the corresponding composite object.

Manage Registered Nodes Menu Option Might Not Be Displayed (4855259)

If you access the fabric icon pop-up menu by pressing mouse button 3 from within the Sun Management Center Fabric Details window, the Manage Registered Nodes menu option might not be displayed.

Workaround: Use the Fabric menu to select the Manage Registered Nodes option instead.

Switch Physical View or Logical View Alarm Color Not Shown (4855551)

When an alarm is triggered in the Sun Fire Link switch module, the switch physical view or logical view (PV/LV) does not show the alarm color.

Workaround: You can view the correct alarm colors in the module's browser and the alarms table.

Scroll Bar Not Displayed on Right Side of Fabric Details Window (4856536)

The Fabric Details window does not include a scroll bar in the large icon view of the Chassis & Links perspective. The scroll bar should always be displayed when the image is larger than the Fabric Details window. The scroll bar enables you to view all the nodes in a large partition.

Workaround: While in the Chassis & Links perspective, change from the large icon view to the small icon view. The scroll bar is displayed. Then change back to the large icon view. The scroll bar stays displayed.

Changing to the Nodes & Routes perspective from the large icon Chassis & Links perspective also displays the scroll bar. However, when you change back to the large icon Chassis & Links perspective, the scroll bar is no longer available.

Empty Grey Box Might Be Displayed in Fabric Details Window for Chassis & Links Perspective (4856884)

In the Sun Management Center Fabric Details window, when you are in the Chassis & Links perspective, an empty grey box might be displayed in the following instances:

• Before you have added a switch to a newly created partition object

• After you have deleted the last switch from a single partition when unconfiguring the fabric

Workaround: Apply the appropriate patch.

• Solaris 8 Platform: Patch 116164–02

• Solaris 9 Platform: Patch 116162–01

Fabric Manager Remote Shared Memory Proxy Has Memory Leak (4863270)

The Sun Fire Link Fabric Manager Remote Shared Memory (WRSM) proxy leaks memory when the proxy receives an event from the kernel system event notification daemon, syseventd(1M).

Workaround: For the Solaris 8 or Solaris 9 platform, apply patch 114786–02.

Data Missing From Route Properties Window (4771419)

When displaying route properties data in a Fabric Details context, some data might be missing from the To and From fields of the table.

Workaround: None.

Bug That Applies to Sun Fire High-End (15K/12K) Systems and Sun Fire Link Systems

Attempts to Remove a Node From Sun Fire High-End (15K/12K) Chassis Might Fail When Chassis Has Multiple Nodes in the Same Partition (4856525)

When a Sun Fire High-End (15K/12K) chassis has two or more nodes configured into the same partition, attempts to remove the nodes from the partition might fail if that chassis is the only chassis with multiple nodes in that partition. This problem is caused by the need to create memory mapping aliases when multiple nodes from a chassis are configured into the same partition. This aliasing is done independently by every chassis that contributes multiple nodes to a common partition. When you remove all but one of a chassis's nodes from a partition, the aliasing created for that chassis will become invalid.

For example, say you have a partition consisting of three nodes:

xc1-a, xc1-b, xc2-a

where xc1 and xc2 are two Sun Fire High-End (15K/12K) systems.

If you remove either xc1-a or xc1-b from the partition, the memory map aliasing for the xc1 system becomes invalid.

However, if the partition includes two or more chassis that contribute multiple nodes, the memory map aliasing created for the second chassis compensates for the loss of aliasing in the first chassis. This compensation allows continued use of the partition.

For example, say you have a partition consisting of four nodes:

 
xc1-a, xc1-b, xc2-a, xc2-b

If you remove either xc1-a or xc1-b from the partition, the memory map aliasing for the xc1 system becomes invalid. However, the aliasing for chassis xc2 remains valid. The partition can continue operation.

Workaround: For the Solaris 8 platform, apply patch 116160–01.

Workgroup Servers (High-End Entry Servers) Issue

Sun Ultra 5 Workstation Might Identify Itself as Sun Ultra 10 Workstation After Upgrade With Agent Update Utility

If you use the Agent Update utility to update the Sun Management Center 3.5 agent on a Sun Ultra^TM 5 workstation, the workstation might identify itself as a Sun Ultra 10 workstation after the upgrade. As a result, the icon and physical view for the Sun Ultra 5 display in Sun Management Center windows as a Sun Ultra 10.

Workaround: To correct the problem, complete the following steps:

1. At the system prompt, type the following command to stop the Sun Management Center agent:

   # es-stop -a

2. Change to the following directory:

   # cd /var/opt/SUNWsymon/platform

3. In the platform prop file, change the UltraModel=10 entry to UltraModel=5.

4. Type the following command to start the Sun Management Center agent:

   # es-start -a

Workgroup Servers (High-End Entry Servers) Bug

Some Platform Types Not Available in Discover Objects Menu (4822174)

When you perform a discovery request and choose to discover platforms by platform type, the available platforms appear in a drop-down menu. This drop-down menu is located under the Filters tab in the New Discovery Request dialog box.

The drop–down menu does not include entries for the following Sun Enterprise Ultra servers:

• Sun Enterprise Ultra 2

• Sun Enterprise Ultra 5

• Sun Enterprise Ultra 10

Workaround: If you need to perform a discovery request for any of the preceding Sun Enterprise Ultra servers, perform the request manually.

Sun StorEdge A5x00 and T3 Arrays Bugs

A5x00 Module Does Not Populate Tables With Values (4973319)

Sun Management Center 3.5 Update 1 requires the latest SUNWluxop patch.

Workaround: For systems with A5x00 storage, download and apply the patch for the SUNWluxop package.

• Solaris 6 Platform: No patch available

• Solaris 7 Platform: Patch 107473-07 or later

• Solaris 8 Platform: Patch 111413-12 or later

• Solaris 9 Platform: Patch 113043-06 or later