test

Solaris 7 11/99 Release Notes Supplement for Sun Hardware

Chapter 3 Open Issues

StarOffice Support

Sun's StarOffice Knowledge Database is the current customer support resource for StarOffice 5.1. For more information, refer to:

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

Spanish Server installt.html File References ODBC 2.11 (4278257)

The "Co-Packaged Software Topics: Contents" page of the Spanish (only) Server Web Start installation process contains a reference to ODBC 2.11. If you click on the ODBC 2.11 link, you receive the following error message:

File not found

ODBC 2.11 is not co-packaged with the Solaris 7 11/99 software release, and the reference should not appear on the page.

Workaround: Ignore the reference to ODBC 2.11 and do not click on the link.

Prestoserve 2.4.2 -- Patch Required

The Prestoserve 2.4.2 release will not function properly with the Solaris 7 11/99 software environment if the following workaround is not implemented. Here is a partial list of some of the platforms and hardware options that may be affected:

To Install the Prestoserve Patch

If you installed the Prestoserve 2.4.2 software and are using a platform or hardware option listed above, you must take the following steps to provide compatibility:

  1. Edit the /etc/system file by adding the following information: 

    set fas:fas_enable_sbus64 = 0

  2. Reboot your system.

    Caution - Caution -

    Failure to reboot your system can corrupt data.

A Prestoserve patch (#103043-08) that automatically adds the above information to the /etc/system file is available. If you prefer to make this change using the Prestoserve patch, contact your authorized Sun support provider. If you edit the /etc/system file as described above, you do not need the Prestoserve patch.

To Install the Prestoserve Patch on an Ultra 2 System

If you installed the Prestoserve 2.4.2 software and are using an Ultra 2 platform (200MHz or 300MHz), you must take the following steps to provide compatibility:

  1. Edit the /etc/system file by adding the following information: 

    set fas:fas_enable_sbus64 = 0

  2. Reboot your system.

  3. Use pkgadd to add the SUNWprsto package.

  4. Add the Prestoserve patch (103043-08).

    Note -

    If the above steps are not followed, your Ultra 2 system may panic.

Booting From Partitions Greater Than 2 Gbytes (1234177)

Due to PROM limitations, all sun4c, sun4d, and sun4m architectures will not boot from partitions greater than 2 Gbytes. These systems will 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 sun4c, sun4d, and sun4m systems with large root disks (4 Gbytes and greater).

SunFDDI Adapters Cannot Boot Sun4d Diskless Clients (4144414)

Sun4d diskless clients cannot be booted using SunFDDI(TM) adapters (FDDI/S 6.0 or FDDI/P 2.0) installed in servers running the Solaris 7 11/99 operating environment. If you intend using a Sun4d as a diskless client, deploy it in an ethernet section of your network.

Serial Parallel Controller Driver and Dynamic Reconfiguration

The Serial Parallel Controller driver does not support Dynamic Reconfiguration (4177805).

ISDN -- Supported in 32-bit Mode Only

ISDN does not support the Power Management(TM) suspend and resume features.

SunScreen SKIP 1.1.1 Not Supported in Solaris 7 11/99 Operating Environment

If you have the SunScreen(TM) SKIP 1.1.1 software currently installed on your system, you should remove the SKIP packages before installing or upgrading to the Solaris 7 operating environment. The packages you should remove are:

Solstice SyMON Not Supported in Solaris 7 11/99 Operating Environment

If you have Solstice(TM) SyMON(TM) currently installed on your system, you should remove the SyMON packages before installing or upgrading to the Solaris 7 11/99 operating environment. The packages you should remove are:

ShowMe TV 1.3 Known Problems

Software

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

SunVTS 3.4 Issues

The following issues apply to the SunVTS(TM) 3.4 product.

New Features for This Release

The following new tests were added to SunVTS 3.4:

SunVTS OPEN LOOK User Interface Support

The SunVTS OPEN LOOK user interface may not support the latest SunVTS features. For full feature support, use the SunVTS CDE or TTY interface. The SunVTS OPEN LOOK user interface will be sustained, but not enhanced, as long as OPEN LOOK is supported in the Solaris environment.

Possible Installation Problems

There are three possible installation problems that you might encounter when you attempt to install SunVTS with an installation program other than the pkgadd command.

Using Web Start 1.0 (4268929)

The installation fails on some systems when installing SunVTS with Web Start 1.0. The SunVTS diag device driver does not install properly and the installation fails.

Workaround: Use the pkgadd command to install SunVTS as described in the SunVTS 3.4 User's Guide.

Using Web Start 2.0 (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 3.4 User's Guide.

Fixed Installation Directory with Web Start 2.0 (4243921)

When you attempt to install SunVTS using Web Start 2.0 you are not able to change the directory where SunVTS is installed. SunVTS will be installed in /opt.

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

Running SunVTS Online Diagnostics Through Sun Enterprise SyMON

The SunVTS 3.4 online diagnostics feature (SUNWodu) is not accessible through the SyMON interface.

Instead, you can start SunVTS so it will run safely in an online environment by using the vtsui.online command.

For example:

# /opt/SUNWvts/bin/vtsui.online -h hostname

For more information about running SunVTS software in an online or offline environment, refer to the SunVTS 3.4 User's Guide.

StorEdge-A5XXX Device Group Changes

As of SunVTS 3.3, the way that StorEdge(TM) A5XXX devices are grouped in the SunVTS System Map (for logical mapping) changed. Prior to version 3.3, the enclosure was grouped under the SENA(n) group and the disks were grouped under the SCSI-Devices group. Now the enclosure and disks are both grouped under the StorEdge-A5XXX_enclosure_name group.

Disk Test (disktest) Mounting Issues

As of SunVTS 3.0 software, SunVTS disktest by default does not mount any mountable partitions. To have SunVTS software mount all partitions that contain a file system, set the environment variable BYPASS_FS_PROBE to 0 (zero), then start SunVTS software. For more details, refer to the disktest chapter in the SunVTS 3.4 Test Reference Manual.

Disk Test (disktest) Option File Note

Loading an option file that was created when BYPASS_FS_PROBE was set to 0 (zero) might not work if the BYPASS_FS_PROBE environment variable is no longer set to 0 (zero). Testing may fail with the following error: 

SUNWvts.disktest.8088 07/24/98 15:47:22 disktest c0t0d0
FATAL: "Couldn't get file system information on /disktest_c0t0d0s0, statvfs()
system call failure error: No such file or directory.

This error is caused when SunVTS software expects to use the predefined mount point names (/disktest_cntndnsn) that are created when BYPASS_FS_PROBE is set to 0 (zero), but these mount points do not exist while BYPASS_FS_PROBE is not set to 0 (zero).Workaround: Create two separate option files for the two different states of the BYPASS_FS_PROBE environment variable.

Physical Configuration Mapping Support

The Physical Mapping function is only supported on the systems where the configd program is supported. The configd program only supports Ultra Enterprise(TM) server and Ultra Desktop systems. The configd package must be installed at the default installation base directory.

To display physical mapping, click the physical mapping button in the SunVTS interface. This will result in a re-mapping of the entire set of testable devices and test settings. Changing the logical and physical view during a test session is not recommended because the previous system and test status will be reset.

The SunVTS User Interface Disappears (4122829)

In some cases, the SunVTS user interface disappears during a SunVTS test session. The SunVTS kernel is still active and the test session may continue to run.

Workaround: Restart the SunVTS user interface.

For example (starting the SunVTS CDE user interface):

# /opt/SUNWvts/bin/vtsui

Some Devices Not Displayed Under Physical Mapping (4228489)

Certain devices that appear under logical mapping are not displayed under physical mapping; therefore, these devices are not selectable for testing.

Workaround: Use logical mapping for testing such devices.

The enatest and socaltest Cannot Run at the Same Time (4065417)

When the SunVTS enatest is run concurrently with the socaltest, the enatest may fail.

Workaround: Do not select socaltest when enatest is selected and vice-versa.

The socaltest FATAL: Failed ioctl FCIO_DIAG_XRAM (4065420)

When the SunVTS socaltest is run concurrently with disktest, the socaltest may fail.

Workaround: Do not select socaltest when disktest is selected and vice-versa.

The socaltest Can Fail Under Heavy System Load (4213518)

Running socaltest with heavy system load might cause resource limitations that cause this test to fail.

Workaround: Do not run socaltest with a large number of instances and concurrency.

dpttest Test

Sun currently only supports 64 megabytes of cache on the SRC/P hardware RAID card. Therefore, if you chose to select a memory amount to check under DPTTEST, set the Check Memory item to 64M.

PCMCIA Issues

The following bugs have been filed against PCMCIA:

If the PC ATA (pcata) module is modunloaded the system will appear to hang (4096137)

Description: 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 will appear to hang. Sometimes removing the card will bring the system back.

Workaround: none

When Booting Solaris 7 11/99 operating environment initially with 64-bit kernel the device /dev/term/pc0, PC card serial driver, may not get created (4162969)

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

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

PC File Viewer Issues

Install in the /opt Directory

The Solaris 7 11/99 Sun Hardware Platform Guide provides installation instructions that may indicate that PC file viewer can be installed in a directory other than the default directory. PC file viewer must be installed in the default (/opt) directory.

Known Bugs

Sun Remote System Control (RSC) Release Notes

What's New in This Version

This version of Sun Remote System Control (RSC) includes bug fixes and a new environment variable, tpe_link_test. In addition, the RSC device Internet address has been added to email and pager alert messages.

If you have already installed a previous version of Remote System Control, back up your RSC configuration before installing this version, following the directions in Chapter 2 of the RSC User's Guide, and then restore them after installation when you run the RSC configuration script.

The tpe_link_test variable enables 10BASE-T Ethernet link integrity tests when set to true, the default. If you are using RSC in a hub that does not support Ethernet link integrity tests or that has them disabled, set this variable to false. Changes to this variable take effect after the next RSC reset. The tpe_link_test variable behaves similarly to the tpe-link-test? OBP environment variable, which is available on some SPARC platforms.

RSC and the local hub should have Ethernet link integrity tests enabled or disabled consistently. If this setting is not consistent, communication may not be possible.

Hardware and Software Configurations Supported for RSC

Supported Server

Sun Enterprise 250 server only, running the Solaris 7 or Solaris 2.6 5/98 operating environment.

The Sun Enterprise 250 flash PROM must be updated to version 3.7.7 or later before installing the RSC software. Failing to do so may cause server and RSC malfunctions. For update instructions and a downloadable image, see the Sun Enterprise 250 Supplement Web page at http://sunsolve2.Sun.COM/sunsolve/E250/flash.html. If you install RSC from the Sun Enterprise 250 Supplement CD, you can update the flash PROM as part of the installation process.

Supported GUI Clients

Sun JDK(TM) version 1.1.6 or a subsequent compatible version is required for GUI support on systems running the Solaris operating environment, and is included in the base Solaris 7 operating environment and the Sun Enterprise 250 Supplement CD.

Supported CLI Clients

Ethernet Support

RSC is designed to function in a 10BASE-T network, and the RSC Ethernet port should be connected to a hub operating at 10 Mbps. If RSC does not respond to an Ethernet request, the first thing to check is that connection is to a 10BASE-T hub.

Uninterruptible Power Supply (UPS)

An American Power Conversion SmartUPS 1000 with PowerChute plus 4.2.2 software was used for testing.

Paging Support

RSC paging requires that the customer's paging service adhere to the TAP protocol. Paging services in the Americas and Europe generally are TAP-compliant, but this is not necessarily so in other locales.

Testing RSC Paging

Due to the many variables associated with paging, Sun Microsystems strongly recommends that you test the RSC paging mechanism to insure that your configuration options are set correctly.

The easiest way to test that all the components associated with RSC paging are functioning properly is to use the rscadm send_event -c command. This command can be invoked from a UNIX shell and will initiate an RSC alert. If the RSC page_enabled flag is set to true, this alert will send a page to the recipients specified by the page_info1 and page_info2 environment variables.

If RSC fails to send a page, a message similar to the following will be added to the event log:

THU AUG 27 22:31:09 1998 sst4828: 00060006: "Failed to send page alert for recent event"

If RSC successfully transmits a page, no error message is added to the event log.

RSC can fail to send a page notification for the following reasons:

When a page fails, check that the following conditions are met:

  1. The modem dip switch and software configuration variables are set correctly.

  2. All the RSC page_variables (page_info1, page_info2, page_init1, page_init2, page_baud1, and page_baud2) are set correctly and match the settings for your paging service.

  3. Your paging service supports the TAP protocol. Check with the paging service to insure that you have the proper phone number and modem configuration parameters.

  4. Attempt to connect with the paging service manually. Refer to the "Troubleshooting Modem Problems" section in Appendix B of the RSC User's Guide for instructions on manually connecting to a TAP paging service.

Troubleshooting

In some cases, it might be desirable to extend the pause period to allow the modem to recognize the dial tone of the phone line. This can be accomplished on most modems by increasing the value in the S8 register. See documentation that came with your modem for more details.

Copyright Notices

The following copyright information may not have been included in the appropriate documents.

SunForum(TM) 2.0 Notices

  1. Copyright Data Connection Limited 1999. Data Connection\256 is a registered trademark of Data Connection Limited in the US and other countries.

  2. Copyright Teles Ag 1999.

ShowMe TV 1.3 Notices

Copyright\256 1993-1994 The Regents of the University of California. All rights reserved. Tous droits re'serve's.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and the Network Research Group at Lawrence Berkeley Laboratory.

  4. Neither the name of the University nor of the Laboratory may be used to endorse or promote products derived from this software without specific prior written permission.

Copyright 1990-1993 GROUPE BULL

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of GROUPE BULL not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. GROUPE BULL makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

GROUPE BULL disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness, in no event shall GROUPE BULL be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action, arising out of or in connection with the use or performance of this software.

Copyright 1992 by Stichting Mathematisch Centrum, Amsterdam, The Netherlands.

All Rights Reserved. Tous droits re'serve's.

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OR MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF IR IN CONNECTION WITH THE USE OF PERFORMANCE OF THIS SOFTWARE.

OpenGL is a trademark of Silicon Graphics.

Netscape Communicator Notices

Copyright 1999, Netscape Communications Corporation. All Rights Reserved. Tous droits re'serve's.

Sun Enterprise 10000 SSP Notices

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses.

Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS252.227-7013 and FAR 52.227-19.

Documentation Errata

The following errors in various documents have been reported.

Platform Notes: The hme SunFastEthernet Device Driver Guide

The Platform Notes: The hme SunFastEthernet Device Driver Guide lists the wrong default value for the adv_10fdx_cap parameter. The correct default value for this parameter is 1 for 10Mbit/sec full-duplex capable.See bug Id 4217150 for more information.