test

Solaris 8 2/02 Release Notes Supplement for Sun Hardware

Chapter 3 Open Issues

StarOffice Support

The Sun StarOffice™ Knowledge Database is the current customer support resource for StarOffice 5.2. For more information, refer to:

http://www.sun.com/products/staroffice/support.html

Booting From Partitions Greater Than 2 Gbytes (BugID 1234177)

Due to PROM limitations, no sun4d and sun4m architectures boot from partitions greater than 2 Gbytes. These systems fail with the following message:


bootblk: can"t find the boot program

Note –

All sun4u architectures support booting from larger partitions.

One related bug (4023466) reports a problem with re-preinstall where the boot image for large disks creates root partitions greater than 2 Gbytes. System administrators are cautioned not to use re-preinstall on sun4d or on sun4m systems with large root disks (4 Gbytes and greater).

Network Drivers Installed by Default

The Computer Systems Installer CD automatically installs the Network Drivers from the Supplement CD. Drivers for the SunATM™, SunHSI/S, SunHSI/P, SunFDDI/S, and SunFDDI/P cards are now installed by default when the Solaris 8 2/02 operating environment is installed. Error messages might be displayed if you do not have some of the corresponding hardware installed. You can ignore these error messages.

Serial Parallel Controller Driver Does Not Support Dynamic Reconfiguration (BugID 4177805)

This spc driver does not support Dynamic Reconfiguration features in the Solaris 8 operating environment.

Booting a Sun Enterprise 10000 System in 32-Bit Mode (BugID 4348354)

Sun Enterprise 10000 systems with 64 Gbytes of memory cannot boot the Solaris 8 2/02 operating environment in 32-bit mode.

Some DVD and CD-ROM Drives Fail to Boot Solaris (BugID 4397457)

The default timeout value for the SCSI portion of the SunSwift PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of the Sun SCSI DVDROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems, which overwrite the SCSI timeout value via OBP.

Workaround for other platforms: use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as X1018A (SBus: F501-2739-xx) or X6540A (PCI: F375-0005-xx).

FDDI May Hang During Heavy Load (BugIDs 4485758, 4174861, 4486543)

The PCI FDDI card has known hardware problems related to DTXSUSP (DMA TX process suspend interrupt) and DRXSUSP (DMA RX process suspend interrupt) bits in the MAIN_CONTROL and MAIN_STATUS registers. These hardware bugs minimally affect FDDI functionality under normal conditions. However, under a very heavy TX or RX load, the card posts an unexpected interrupt. The system posts the error message, "Interrupt level 6 is not serviced". After 20 such errors, the pcipsy driver shuts down interrupt processing for the FDDI and hangs FDDI.

DR Commands Hang Waiting for rcm_daemon While Running ipc, vm, and ism Stress (BugID 4508927)

In rare cases when a quiesce of the Solaris operating environment fails to stop certain user threads, other user threads may not be restarted and remain in a stopped state. Depending on the threads affected, applications running on the domain may stop running and other DR operations may not be possible until the domain is rebooted.

Workaround: To avoid this problem, do not use DR to remove a board that contains permanent memory.

Monitor Goes Blank When Stop-A Is Pressed During Screen Lock (BugID 4519346)

The monitor may go blank if all of the following conditions occur:

Workaround: If your screen saver is enabled, choose any pattern other than "Blank Screen."

U-Code Does Not Reload After IFB Driver Unloaded (BugID 4532844)

At the command line login, systems with Expert3D or Expert3D-Lite cards may be unable to start a window system or dtlogin.

Workaround:

  1. Remotely log into the troubled system as superuser.

  2. Stop all ifbdaemon processes:

    # sh /etc/init.d/ifbinit stop

  3. Start all ifbdaemon processes:

    # sh /etc/init.d/ifbinit start

QFE May Panic the System During Heavy Load (BugIDs 4510631, 4517740)

In rare cases, Sun Fire 6800, 4810, 4800, or 3800 systems configured with multiple network interfaces may panic under a heavy traffic load. Also in rare cases, Sun Enterprise 10000 systems may panic under an extremely heavy network load.

SunScreen SKIP 1.1.1 Not Supported in Solaris 8 2/02 Operating Environment

If you have SunScreen™ SKIP 1.1.1 software currently installed on your system, you should remove the SKIP packages before installing or upgrading to the Solaris 8 2/02 operating environment. The packages you should remove are: SICGbdcdr, SICGc3des, SICGcdes, SICGcrc2, SICGcrc4, SICGcsafe, SICGes, SICGkdsup, SICGkeymg, SICGkisup.

ISDN — Supported in 32-bit Mode Only

ISDN does not support the Power Management™ suspend and resume features.

SunVTS 4.6 Issues

The following issues apply to the SunVTSTM 4.6 product.

New Features for This Release

The following tests, enhancements, and features have been added to the SunVTS 4.6 release:

Refer to the SunVTS 4.6 User's Guide and the SunVTS 4.6 Test Reference Manual for more details about these new features.

SunVTS End-of-Support Statements

SunVTS OPEN LOOK User Interface

The SunVTS OPEN LOOK user interface does not support the latest SunVTS features and will be discontinued when the OPEN LOOK environment is discontinued in the Solaris operating environment. The OPEN LOOK tests, sundials and sunbuttons, will be discontinued too. For full feature support, use the SunVTS CDE interface. Refer to the Solaris “End of Software Support Statements” section of the Solaris operating environment release notes for the latest end-of-support news.

SunVTS Online Testing

As of SunVTS 4.3, the SunVTS online testing capability that was initiated using the vtsui.online command is no longer available. The SUNWodu package that provides this online testing functionality is no longer provided.

Online diagnostic testing of Sun systems is now available through the Sun Management Center software using the Sun Management Center Hardware Diagnostic Suite add-on software. See http://www.sun.com/sunmanagementcenter for details.

Old SunVTS Message Format

In a future SunVTS version, the old message format and the VTS_OLD_MSG variable will no longer be supported. Update any scripts that rely on the old message format from SunVTS. Refer to the SunVTS 4.6 User's Guide for message format details.

SunVTS Stress Mode Option

In a future SunVTS version, the Stress Mode option that is available in the Test Execution dialog box will no longer be supported.

The sunpcitest Will Be Discontinued

In a future version of SunVTS the sunpcitest will be discontinued.

The isdntest Will Be Discontinued

In a future version of SunVTS, the isdntest will be discontinued.

The dpttest Will Be Discontinued

In a future version of SunVTS, the dpttest will be discontinued.

Possible Installation Problems

As described in the following paragraphs, you might encounter an installation problem when you attempt to install SunVTS with an installation program other than the pkgadd command.

Installation Problem: 32-bit Only Systems and Web Start 2.0 (BugID 4257539)

Web Start 2.0 may not install SunVTS on systems that do not have the Solaris 64-bit environment installed. Web Start 2.0 removes the SunVTS 32-bit packages when the SunVTS 64-bit packages cause the installation to suspend.

Workaround: Use the pkgadd command to install the 32-bit SunVTS packages as described in the SunVTS 4.6 User's Guide.

Installation Problem: Security and Web Start 2.0 (BugID 4362563)

When you install SunVTS using Web Start 2.0, you are not prompted to enable the Sun Enterprise Authentication MechanismTM (SEAM) Kerberos v5, SunVTS security feature. The installation defaults in a way that installs SunVTS without this high level of security. If you do not want the high-level security, there is no problem.

Workaround: To enable the high-level SEAM security, use the pkgadd command to install SunVTS packages as described in the SunVTS 4.6 User's Guide.

Installation Problem: Installation Directory With Web Start 2.0 Is Not User-Definable (BugID 4243921)

When you attempt to install SunVTS using Web Start 2.0, you are unable to change the directory where SunVTS is installed. SunVTS is installed in /opt.

Workaround: Use the pkgadd -a none command to install SunVTS in the directory of your choice, as described in the SunVTS 4.6 User's Guide.

Installation Recommendation: Perform Installations and Uninstallations Using the Same Program

If you install SunVTS using Web Start 2.0, you should also uninstall it using Web Start 2.0. If you install SunVTS with the pkgadd command, you should uninstall it with the pkgrm command.

Possible Runtime Problems

The saiptest Device Does Not Display in the SunVTS UI (BugID 4482710, 4322468, 4313346)

The saiptest, which tests the serial asynchronous interface (SAI) card, does not show up in the SunVTS UI.

Workaround: Install the saip driver patch 109338 if you want to test the SAI device.

The env5test Fails (BugID 4493544, 4487110, 4508863)

A communication problem between the env5test and the picld daemon causes the env5test to fail.

Workaround: Before you start SunVTS, stop and start the picld daemon as shown in the following example:

# /etc/init.d/picld stop

# /etc/init.d/picld start

Note –

Once you stop and start the picld daemon, the problem is resolved until the system is rebooted, at which time you need to perform these commands again.

The cg6test Might Not Complete a Test Pass (BugID 4506219)

The cg6test for testing the CG6 frame buffer might not complete a test pass.

Workaround: Do not run the cg6test.

Possible env4test Problem (BugID 4516503)

The env4test might fail if you select the All Tests option in the Test Parameter Options dialog box.

Workaround: Do not select the All Tests option from the Test Parameter Options dialog box.

Possible sctest Problem (BugID 4526192)

If you run the sctest for an extended period of time, the ocfserv may core dump.

Workaround: Do not run sctest if this problem occurs.

Possible Problem of Not Detecting All Serial Ports (BugID 4523182)

If a system has additional serial devices installed other than the onboard serial(s), SunVTS might not detect all the devices.

env4test Documentation Error in Test Reference Manual (BugID 4530573)

There is an error in the SunVTS 4.6 Test Reference Manual in the environment test (env4test) chapter. Figure 22-1, env4test Test Parameter Options Dialog Box, shows an option called Reset Test. This option is not available in the 4.6 release.

ShowMe TV 1.3 Known Problems

ShowMe TV 1.3 software contains support for MPEG2 movie playback. Support was dropped for the Sun MediaCenter™ in ShowMe TV 1.3. Also, ShowMe TV 1.3 software contains a number of bug fixes over ShowMe TV 1.2.1. Here are some known problems:

PCMCIA Issues

The following bugs have been filed against PCMCIA device support in this Solaris release.

Known Bugs

System Appears to Hang When the PC ATA (pcata) Module Is modunloaded (BugID 4096137)

If there is a PCMCIA I/O card in a slot that has been accessed and the card driver is unloaded (as occurs during modunload -i 0 at the end of multi-user boot) the system appears to hang.

Workaround: Removing the card may bring the system back.

Booting the Solaris 8 Operating Environment Initially With a 64-bit Kernel May Not Create the Device /dev/term/pc0, PC Card Serial Driver (BugID 4162969)

When booting the Solaris 8 operating environment initially with a 64-bit kernel, the /dev/term/pc0 hardware device node for PC card serial device may not be created.

Workaround: Boot the system with the 32-bit kernel first, then reboot with the 64-bit kernel.

PC File Viewer Issues

Install in the /opt Directory

The Solaris 8 2/02 Sun Hardware Platform Guide provides installation instructions that might indicate that PC file viewer can be installed in a directory other than the default directory. The instructions are misleading. PC file viewer must be installed in the default (/opt) directory.

Known Bugs

Documentation Errata

The following documentation errors have been found in the Solaris 8 2/02 documents.

References to MPxIO Documentation

The Sun Enterprise 10000 SSP 3.5 User Guide, Sun Enterprise 10000 Dynamic Reconfiguration User Guide, and the Sun Enterprise 10000 DR Configuration Guide contain references to a document that is not available, namely the MPxIO Installation and Configuration Guide.

The MPxIO product is now called the Sun StorEdgeTM Traffic Manager. Information on installing and configuring the Sun StorEdge Traffic Manager is provided in the Sun StorEdgeTM Traffic Manager Software Installation and Configuration Guide, available on the Sun Network Storage Solutions website:

http://www.sun.com/storage/san

To access this document:

  1. Go to http://www.sun.com/storage/san and click the “Sun StorEdgeTM SAN3.0 release Software/Firmware Upgrades and Documentation” link.

  2. Sign on or register.

  3. Click the “Download STMS Install/Config Guide, Solaris/SPARC (.35 MB)” link.

SSP 3.5 Installation Guide and Release Notes

Page 8: In the description of the snmpd memory leaks (Bug ID 4486454), you must be superuser on the main SSP to stop and start SSP daemons, not user ssp as indicated in the text.

Pages 75 and 99: The references to the Solaris 8 Installation Supplement are incorrect. Refer to the Solaris 8 Advanced Installation Guide for details.

eri(7d) Man Page

The eri(7d) man page incorrectly states that the eri.conf file is in the /kernel/drv/sparcv9/eri.conf file

The correct location is: /kernel/drv/eri.conf

Platform Notes: Sun GigaSwift Ethernet Driver

The English language version of the Platform Notes: Sun GigaSwift Ethernet Driver contains several errors that are corrected in the Japanese language version. The errors are as follows:

Netra T4/Netra T20 Issues

System Incorrectly Reports Removed Device Links (BugID 4418718)

When calling luxadm remove_device /dev/rdsk/c1t1d0s2, the system asks for confirmation and reports that the disk is spinning down and being taken offline. When the disk is removed, pressing Return causes the system to report that the device links are removed.

However, the device links are not removed. The disk can then be re-inserted and used without running the luxadm insert_device command. When the command is subsequently run, the system reports that no new devices were added and the following message is produced at the console:

bash-2.03# luxadm remove_device /dev/rdsk/c1t1d0s2 

 

WARNING!!! Please ensure that no filesystems are mounted on these device(s). 

All data on these devices should have been backed up. 

 

The list of devices which will be removed is: 

1: Device name: /dev/rdsk/c1t1d0s2 

Node WWN: 2000002037e367e4 

Device Type:Disk device 

Device Paths: 

/dev/rdsk/c1t1d0s2 

 

Please verify the above list of devices and 

then enter 'c' or <CR> to Continue or 'q' to Quit. [Default: c]:  

stopping: /dev/rdsk/c1t1d0s2....Done 

offlining: /dev/rdsk/c1t1d0s2....Done 

 

Hit <Return> after removing the device(s)  

 

Device: /dev/rdsk/c1t1d0s2 

Logical Nodes being removed under /dev/dsk/ and /dev/rdsk: 

c1t1d0s0 

c1t1d0s1 

c1t1d0s2 

c1t1d0s3 

c1t1d0s4 

c1t1d0s5 

c1t1d0s6 

c1t1d0s7 

 

Device: /dev/rdsk/c1t1d0s2 

Logical Nodes being removed under /dev/dsk/ and /dev/rdsk: 

c1t1d0s0 

c1t1d0s1 

c1t1d0s2 

c1t1d0s3 

c1t1d0s4 

c1t1d0s5 

c1t1d0s6 

c1t1d0s7 

 

bash-2.03# ls -l /dev/dsk/c1t1* 

lrwxrwxrwx 1 root root 70 May 4 19:07 /dev/dsk/c1t1d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:a 

lrwxrwxrwx 1 root root 70 May 4 19:07 /dev/dsk/c1t1d0s1 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:b 

 

bash-2.03# ls -l /dev/rdsk/c1t1* 

lrwxrwxrwx 1 root root 74 May 4 19:07 /dev/rdsk/c1t1d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:a,raw 

lrwxrwxrwx 1 root root 74 May 4 19:07 /dev/rdsk/c1t1d0s7 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:h,raw 

. 

. 

/* the following errors are caused by SUNWvts reprobe looking for said disk */ 

 

bash-2.03#  

8012 05/22/01 14:05:07 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address 

 

8012 05/22/01 14:05:41 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address 

 

8012 05/22/01 14:07:25 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address 

 

bash-2.03# luxadm insert_device 

Please hit <RETURN> when you have finished adding Fibre Channel Enclosure(s)/Device(s):  

 

Waiting for Loop Initialization to complete... 

No new device(s) were added!! 

 

To work around, enter the following when luxadm remove_device claims to have completed successfully:


# devfsadm -C -c disk

Not All USB Zip Drives Found (BugID 4453787)

If four USB Iomega zip drives are attached, prtconf indicates that no driver is loaded after the system has booted. drvconf starts a system probe that finds only two of the four USB zip drives.

Running cat on the /dev/usb/hub0 file causes the system to add the two zip drives.

Workaround: Do not use more than two zip drives in the current release.

LOMlite2 reset-x Does Not Reset CPUs (BugID 4462131)

The LOMlite2 reset-x command does not currently reset the CPUs. Look for this functionality in a later revision of the OpenBoot PROM.

Sun Remote System Control 2.2 Release Notes

This document deals with Sun Remote System Control (RSC) 2.2 hardware and software issues. For complete information about using RSC, see the Sun Remote System Control (RSC) 2.2 User's Guide.

What's New in RSC 2.2

Several new features are available in RSC 2.2:

Before Installing Sun Remote System Control Software

RSC software is included as part of the default installation set for this Solaris Supplement CD. You should install RSC server components on a compatible Solaris server only; you can install the client software on any computer that meets the Solaris or Windows operating environment requirement. You must install and configure the RSC software before you can use RSC.

Important: Before upgrading from a previous version of RSC server software or reinstalling the software, log in to the server as superuser and back up your configuration data using the following commands:

# rscadm show > remote_filename

# rscadm usershow >> remote_filename

Use a meaningful file name that includes the name of the server that RSC controls. After installation, you can refer to this file to restore your configuration settings if necessary. Reverting to a previous version of RSC server software after installing version 2.2 is not recommended. However, if you do revert, you will need to restore your configuration information and also power cycle the server.

You can install the RSC 2.2 server software package, SUNWrsc, on:

You can install the RSC 2.2 client software packages on:

Installation on the Solaris operating environment places the Sun Remote System Control (RSC) 2.2 User's Guide in the location /opt/rsc/doc/locale/pdf/user_guide.pdf. Installation on the Windows operating environment places the User's Guide in the location C:\Program Files\Sun Microsystems\Remote System Control\doc\locale\pdf\user_guide.pdf.

The following sections describe Sun Remote System Control (RSC) 2.2 issues.

RSC General Issues

This section describes issues that affect RSC running on all platforms (Sun Enterprise 250, Sun Fire 280R, Sun Fire V880, and Sun Fire V480 servers):

Alert Messages May Be Delayed (BugID 4474273)

If the RSC variables page_enabled and mail_enabled are set to true and multiple alert messages are generated within a short interval, the first message is delivered in a timely fashion but each subsequent message issued during the interval is delayed by 3-4 minutes.

Keyswitch Position in RSC GUI Is Unknown When RSC Is on Battery Power (BugID 4492888)

When the RSC card is running on battery power, the keyswitch slot in the RSC GUI displays as a gray dot, and the mouse-over text on the keyswitch reads Current Keyswitch Position Unknown.

Wrong Information Provided on alerts.html (BugID 4522646)

When configuring the page_info1 or page_info2 fields, you may use any digit or the alphanumeric characters #, @, and , (comma) when specifying a pager phone number, but the PIN area may only contain digits (0-9). In the RSC GUI, the online help for this function is incorrect. For more information about how to configure RSC to work with a pager, refer to the Sun Remote System Control (RSC) 2.2 User's Guide.

rsc-console Will Switch to Tip Connection During Boot if diag-switch? Is Set to true (BugID 4523025)

If diag-switch? is set to true and you use the bootmode -u command to reboot your workstation, rsc-console will revert to the serial (tip) connection after Solaris restarts, even if you have previously redirected the console to RSC.

If this occurs, manually redirect the console ouput to RSC again after the reboot operation has completed. Refer to the Sun Remote System Control (RSC) 2.2 User's Guide for more information.

Power On From GUI/CLI Is Allowed, Yet Doesn't Work, With Keyswitch Turned to Off (BugID 4524277)

If the system's state changes from battery power to standby power and the keyswitch is in the off position, the RSC software should generate a warning that you cannot turn the system power back on when you issue a poweron command from either the CLI or the GUI. The RSC software should issue this warning. You need to move the keyswitch back into the on position.

If this happens, use the resetrsc command.

RSC bootmode -u Command Fails to Toggle the Console (BugID 4525310)

This intermittent problem has been observed on Sun Fire V880 servers running OpenBoot PROM version 4.4.6. Occasionally, the bootmode -u command fails to redirect the console to RSC. If this happens, use the resetrsc command.

OBP 4.4.3 Displays ERROR: RSC-Initiated Reset Instead of a Warning Message (BugID 4514863)

On servers running OpenBoot PROM software version 4.4.3, an RSC-initiated system reset produces the following message:


ERROR: RSC-initiated Reset

This message serves as a warning-level message only; no action is required.

RSC Restart Error on Japanese Windows 98 Systems

If you install the RSC client on the Japanese version of Microsoft Windows 98, RSC does not start again once you exit from the client and the javaw stack error appears, unless you reboot the system. This situation occurs only on the initial version of Windows 98, and does not happen on other versions of Microsoft Windows (95, 98 Second Edition, NT).

Workaround: Download and install the Microsoft IME98 Service Release 1 (IME98-SR1) from the Microsoft Website. The crash does not occur after IME98-SR1 has been installed.

RSC Issues for Sun Fire 280R, Sun Fire V880, and Sun Fire V480 Servers

This section describes issues that affect RSC running on Sun Fire 280R, Sun Fire V880, and Sun Fire V480 servers.

Removing and Installing the RSC Card

Caution – Caution –

Removing or installing the RSC card while the system has the AC power cord connected could damage your system or your RSC card. Only qualified service personnel should remove or replace the RSC card. Contact your qualified service representative to perform this service operation.

Before you follow the procedures in the Sun Fire 280R Server Service Manual or Sun Fire 880 Server Service Manual to remove or install the RSC card, perform this procedure to ensure that there is no AC power present in the system.

  1. Shut down and halt the system.

  2. With the system at the ok prompt, turn the keyswitch to the Off position.

    Standby power is still present in the system at this point.

  3. Disconnect all AC power cords from their back panel receptacles.

    This ensures that there is no standby power voltage present in the system.

  4. Follow the procedure you require in your service manual.

Additional RSC Alerts

RSC generates the following alerts on a Sun Fire 280R or Sun Fire V880 server when the RSC card begins battery use after a power interruption:

00060012: "RSC operating on battery power."

RSC generates the following alerts when the host system has shut down from RSC. The messages appear in the log history.

00040000: “RSC Request to power off host.”

00040029: “Host system has shut down.”

If you shut down the system using the keyswitch, or by using the OpenBoot PROM poweroff command, the above alert 00040029 is the only alert displayed.

These alerts are not documented in the Sun Remote System Control (RSC) 2.2 User's Guide.

Going from Battery to Standby, the Locator LED Will Turn On in the GUI (BugID 4524272; Sun Fire V480 Servers Only)

When the RSC hardware changes state from battery power to standby power, the Locator LED on the Sun Fire V480 appears illuminated in the GUI only. It does not illuminate on the system.

If this situation happens, use the resetrsc command.

RSC Issues for Sun Fire 280R Servers Only

This section describes issues that affect RSC running on Sun Fire 280R servers only. See the Sun Fire 280R Server Product Notes for other Sun Fire 280R server issues.

Soft Reset With xir Does Not Work Correctly (BugID 4361396, 4411330)

The xir command does not bring the server to the ok prompt as expected. This issue may have been resolved for your server type; see your hardware platform release notes.

Boot Sequence Sometimes Bypasses RSC (BugID 4387587)

In rare instances, the system may bypass the RSC card during startup. To check whether the system booted and is online, use the ping command to see if the card is alive, or log in using telnet or rlogin. If the system is not connected to the network, establish a tip connection to the system. (Be sure that console I/O is not directed to the RSC card.) Use the tip connection to view boot messages on the troubled system, or reboot the system. For help in diagnosing the problem, see your hardware Owner's Guide.

False Drive Fault Reported at Power On (BugID 4343998, 4316483)

When you power on the system, it may report a false internal drive fault that is recorded in the Sun Remote System Control (RSC) log history.

If the error is reported by RSC, you should disregard the report if the system boots successfully to the Solaris operating environment. In most cases the erroneous fault does not reappear. You can verify the disk after the boot process by using the fsck utility.

Note –

Any disk drive error message reported by the Solaris operating environment is a real disk drive error.

If a disk fault is reported at the ok prompt and the system fails to boot to the Solaris operating environment, there may be a problem with the disk drive. Test the disk drive with the OpenBoot Diagnostics tests documented in the “Diagnostics, Monitoring, and Troubleshooting” chapter in the Sun Fire 280R Server Service Manual.

Command rscadm resetrsc Fails (BugID 4374090)

After a cold restart or after powering on the system, the RSC command rscadm resetrsc fails; this is a known condition. You need to reset the host system for the command to function correctly.

There are three ways you can reset the host. Use one of the following commands:

The RSC rscadm resetrsc command will now function correctly.

RSC Issue for Sun Fire V880 Servers Only

This section describes an issue that affects RSC running on Sun Fire V880 servers only.

Soft Reset With xir Does Not Work Correctly (BugID 4361396, 4411330)

The xir command does not bring the server to the ok prompt as expected. This issue may have been resolved for your server type; see your hardware platform release notes.

RSC Issues for Sun Enterprise 250 Servers Only

This section describes issues that affect RSC running on Sun Enterprise 250 servers only. See the Sun Enterprise 250 Server Product Notes for other Sun Enterprise 250 server issues.

Increased Number of RSC User Accounts Not Supported

Support for a maximum of 16 RSC user accounts has been added for RSC 2.2. However, Sun Enterprise 250 servers continue to be limited to four RSC user accounts because of hardware limitations.

Do Not Run OpenBoot PROM fsck Command From the RSC Console (BugID 4409169)

Do not issue the fsck command from the redirected RSC console.

Reset the system's input-device and output-device settings to ttya. Then reboot the system and access the system through its local console or terminal and execute the OpenBoot PROM fsck command directly.

Do Not Run OpenBoot PROM boot -s Command From the RSC Console (BugID 4409169)

The command boot -s does not work from the RSC console.

Reset the system's input-device and output-device settings to ttya. Then reboot the system and access the system through its local console or terminal and execute the boot -s command directly.

Change to the serial_hw_handshake Variable Requires a System Reboot (BugID 4145761)

In order for changes to the RSC configuration variable serial_hw_handshake to take effect, the server must be rebooted. This also affects the Enable Hardware Handshaking check box in the RSC graphical user interface. This limitation is not stated in the documentation.

Power Supply Alerts Display Incorrect Index in the GUI (BugID 4521932)

In the Sun Enterprise 250, the power supplies are numbered 0 and 1, but the RSC GUI refers to them as Power Supply 1 and Power Supply 2 in the event log and in alerts.

LOMlite 2 Release Notes

Adding the LOMlite2 Software

  1. Insert the Supplemental CD and change to the LOMlite 2.0 software directory:


    # cd /cdrom/cdrom0/Lights_Out_Management_2.0/Product

  2. Add the LOMlite 2.0 packages, responding y to all questions:


    # pkgadd -d . SUNWlomm SUNWlomr SUNWlomu

  3. Verify that the LOMlite 2.0 packages were installed:


    # pkgchk -v SUNWlomm SUNWlomr SUNWlomu

The LOMlite2 software is now installed. Continue by adding LOMlite2 Patch 110208 as described in the next section.

Adding LOMlite2 Patch 110208

Ensure you have the latest revision of Patch 110208 from SunSolve (revision -13 or later).

Note –

The LOMlite2 software does not function unless this patch is added.

  1. Confirm the base LOMlite2 firmware version.

    Type #. to change to the lom> prompt, then run version.


    #.
lom>version

LOM version:         v4.4-LW2+
LOM checksum:        387e
LOM firmware part#   258-7939-12
Microcontroller:     H8S/2148
LOM firmware build   Aug 30 2001 18:02:40
Configuration rev.   v1.2

lom>console

    The LOM firmware version must not be earlier than 4.5.

  2. Type console at the lom> prompt to return to the # prompt.

  3. Confirm that the device node is present (via PROM 4.2.4):


    # prtconf -V
OBP 4.2.4 2001/06/13 10:10
# prtconf | grep SUNW,lomv
                SUNW,lomv (driver not attached)

  4. Copy the patch to a temporary directory (/var/tmp).

    Confirm that the patch is present:


    # cd /var/tmp
# ls 
110208-13.zip

  5. Extract the patch:


    # unzip 110208-13.zip

  6. Apply the patch:


    # patchadd 110208-13
# reboot

  7. Confirm that the patch has been loaded:


    # modinfo | grep lomv

  8. To upgrade the firmware, type:


    # lom -G default

    When prompted, type C to continue.

    Note –

    This process takes several minutes. Do not turn off the system while the update is progressing.

  9. Press Return to redisplay the UNIX prompt.

    Note –

    If the system displays the ok prompt, type go to return to the UNIX prompt.

  10. Check the functionality by running the lom -a command:


    # lom -a
PSUs:
1 OK

Fans:
1 OK speed 90%
2 OK speed 86%
3 OK speed 75%

LOMlite configuration settings:
serial escape character=#
serial event reporting=default
Event reporting level=fatal, warning & information

Serial security=enabled
Disable watchdog on break=enabled
Automatic return to console=disabled
alarm3 mode=user controlled
firmware version=4.5
firmware checksum=1164
product revision=1.4
product ID=Netra T4
.
<truncated>
.
LOMlite led states:
1       on              Power
2       off             Fault
3       off             Supply A
4       off             Supply B
5       on              PSU ok
6       off             PSU fail
#

    The software is now installed and the system is ready for use.

Solstice DiskSuite and Alternate Pathing (BugID 4367639)

A segmentation fault error occurs when invoking the Solstice DiskSuiteTM 4.1.2 metatool on a Sun Enterprise 6000 system with Alternate Pathing 2.3 or 2.3.1 already installed and configured on a SPARCstorageTM Array 100 or SPARCstorage Array 200.

After invoking the metatool, the following message is displayed:


root@[/]>metatool &[1]     2569root@[/]>Initializing metatool... Done.Discovering drives and slices... metatool: Segmentation Fault

Workaround: Move /usr/lib/libssd.so.1 and /usr/lib/libap_dmd.so.1 to /usr/sadm/lib/lvm.

SunFDDI and Diskless Booting (BugID 4390228)

The SunFDDI PCI board (FDDI/P) does not support diskless booting. The SunFDDI SBus board (FDDI/S) supports diskless booting on sun4m and sun4u platforms only.

Multiple Sun GigaSwift Ethernet Cards May Hang System (BugID 4336400, 4365263, 4431409)

Your system may experience heavy CPU usage or may hang if more than two Sun GigaSwift Ethernet cards are installed.

System May Hang When the cpr Module Runs (BugID 4466393)

If you are running any version of the Solaris 8 software with an Expert3D or Expert3D-Lite card, you may experience problems after cpr runs.

Workaround: Install Patch 108576-15 or greater.

librt Objects Do Not Transition to Multi-User Mode (BugID 4479719)

SunVTS may fail in multi-user mode when semaphores are created improperly.

Workaround: Kill and restart picld after the machine reaches multiuser mode, but before running SunVTS:

# /etc/init.d/picld stop# /etc/init.d/picld start

Vulnerability in the ToolTalk Database Server Allows Root Access (BugID 4499995)

When the ToolTalk Database Server (/usr/openwin/bin/rpc.ttdbserverd) is enabled, remote and local attacks are possible. These attacks can potentially give root access to the system. Attacked systems can be identified by the presence of garbage files in the root directory that begin with an A.

Workaround: Remove the rpc.ttdbserverd line from the inetd.conf file. Disable the service by using the chmod a-x command on /usr/openwin/bin/rpc.ttdbserverd. Check with your Sun representative about future patches.

Invalid Warning During System Boot (BugID 4519441)

A warning message may appear when booting a Netra ct 800 or Sun BladeTM 100 system which reads:

invalid vector intr: number 0x7de, pil 0x0

This message is benign and can be ignored.