Sun Microsystems Solaris 7 Release Note

Sun Microsystems, Inc.
901 San Antonio Road
Palo Alto, CA 94303-4900
U.S.A

Solaris™ 7 5/99 Release Notes Supplement for Sun™ Hardware

Solaris 7 5/99

Includes Additional Release Notes and End-of­Support Statements for Solaris 7 5/99 Running on Sun Hardware Products
Part No.: 806-0278-10
May 1999, Revision A
Send comments about this document to:
docfeedback@sun.com
Copyright 1999 Sun Microsystems, Inc.,901San AntonioRoad,Palo Alto,California94303-4900 U.S.A. This product ordocumentis protectedbycopyright and distributedunder licenses restrictingits use, copying,distribution, and decompilation.
No part ofthis product ordocumentmay bereproducedin any formby any meanswithout prior writtenauthorization of Sunand its licensors, if any.Third-partysoftware, including fonttechnology, is copyrightedand licensed fromSun suppliers.
Parts of theproductmay bederivedfrom Berkeley BSDsystems, licensed fromthe University ofCalifornia. UNIX isa registered trademark in the U.S. andother countries, exclusivelylicensed through X/OpenCompany,Ltd.
Sun, Sun Microsystems,theSun logo,SunSoft,SunDocs, SunExpress,andSolaris are trademarks,registeredtrademarks, or servicemarks of Sun Microsystems, Inc.inthe U.S.andother countries.AllSPARCtrademarks are usedunderlicense andaretrademarks or registered trademarks of SPARCInternational, Inc. inthe U.S. andother countries. Productsbearing SPARCtrademarks are basedupon an architecture developed by SunMicrosystems,Inc.
The OPEN LOOKand Sun™ GraphicalUser Interface wasdeveloped by SunMicrosystems,Inc. foritsusers andlicensees.Sun acknowledges the pioneering effortsofXerox in researchinganddeveloping theconceptof visualorgraphical userinterfacesfor thecomputerindustry.Sun holds a non-exclusivelicense from Xerox to theXerox Graphical UserInterface, which licensealso covers Sun’slicensees who implementOPEN LOOK GUIs andotherwise comply withSun’s written licenseagreements.
RESTRICTED RIGHTS: Use,duplication, or disclosurebythe U.S.Governmentis subjecttorestrictions of FAR 52.227-14(g)(2)(6/87) andFAR
52.227-19(6/87), or DFAR252.227-7015(b)(6/95) and DFAR 227.7202-3(a). DOCUMENTATIONIS PROVIDED “ASIS” AND ALLEXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONSANDWARRANTIES,
INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY,FITNESS FORAPARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPTTOTHE EXTENTTHAT SUCH DISCLAIMERSARE HELD TOBE LEGALLYINVALID.
Copyright 1999 SunMicrosystems,Inc., 901SanAntonio Road,PaloAlto, Californie94303Etats-Unis. Tousdroitsréservés. Ce produit oudocumentest protégé par uncopyright et distribuéavec des licencesqui en restreignentl’utilisation,la copie,ladistribution, etla
décompilation. Aucune partiede ce produitoudocument nepeutêtre reproduite sousaucuneforme, parquelquemoyen quecesoit, sans l’autorisation préalable etécrite de Sunet de sesbailleurs de licence,s’il y ena. Le logicieldétenu par destiers, et quicomprendla technologie relativeaux policesdecaractères, est protégépar un copyrightet licencié pardes fournisseurs deSun.
Des parties dece produit pourrontêtredérivées des systèmesBerkeley BSD licenciéspar l’Université deCalifornie. UNIX estune marque déposée aux Etats-Uniset dans d’autrespayset licenciéeexclusivementpar X/OpenCompany,Ltd.
Sun, Sun Microsystems,lelogo Sun,SunSoft,SunDocs, SunExpress,etSolaris sont desmarques de fabriqueou des marquesdéposées,ou marquesde service,deSun Microsystems, Inc. auxEtats-Unis et dansd’autres pays. Toutesles marques SPARCsont utilisées souslicence et sont des marquesdefabrique oudesmarques déposées deSPARCInternational,Inc. auxEtats-Uniset dansd’autrespays. Les produitsportant les marques SPARCsont basés surune architecture développée parSun Microsystems, Inc.
L’interfaced’utilisationgraphique OPENLOOKet Sun™aété développéeparSun Microsystems,Inc.pour ses utilisateurset licenciés. Sun reconnaîtles efforts de pionniersde Xerox pourla recherche et ledéveloppement du conceptdes interfaces d’utilisationvisuelle ou graphique pour l’industrie del’informatique. Sun détientune licence nonexclusive de Xeroxsurl’interface d’utilisationgraphiqueXerox, cette licence couvrant également leslicenciés de Sunqui mettent enplace l’interface d’utilisationgraphique OPEN LOOKet qui enoutrese conformentaux licences écrites deSun.
CETTE PUBLICATIONEST FOURNIE"ENL’ETAT"ETAUCUNE GARANTIE, EXPRESSEOU IMPLICITE, N’ESTACCORDEE, YCOMPRIS DES GARANTIES CONCERNANTLA VALEURMARCHANDE, L’APTITUDEDE LAPUBLICATION A REPONDREA UNE UTILISATION PARTICULIERE,OU LE FAIT QU’ELLE NESOIT PASCONTREFAISANTEDE PRODUIT DETIERS. CE DENIDE GARANTIE NE S’APPLIQUERAIT PAS,DANS LA MESUREOU IL SERAITTENU JURIDIQUEMENT NULET NON AVENU.
Please
Recycle

Contents

1. Late Breaking News 1
Service Contract Upgrades to
Solaris 7 5/99 1 Unbundled Product Support 2 PC File Viewer Update 2 Documents on the Software Supplement for the Solaris 7 5/99 Operating
Environment for Sun Computer Systems CD 3 Product Name and Title Changes 4
Sun Microsystems Name Changes 4
Solaris Name Change 4
Solaris Server Intranet Extension Name Change 4 Flash PROM Update for 64-bit Operations 5
Flash PROM Update Multimedia AnswerBook CD 5 Sun Enterprise SyMON Software Available 6
Sun StorEdge A5000 6 Localized Packages on the Software Supplement for the Solaris 7 5/99 Operating
Environment for Sun Computer Systems CD 7
Japanese Localized Packages 7
German Localized Packages 9
Italian Localized Packages 9
Contents iii
French Localized Packages 9 Spanish Localized Packages 10 Swedish Localized Packages 10 Traditional Chinese Localized Packages 10 Simplified Chinese Localized Packages 12 Korean Localized Packages 13
2. End-of-Support Products 15
End-of-Support Products 15
Network Devices — BEC Device and be Driver 15 Graphics Devices—Discontinued Frame Buffers 15 PEX Graphics Library 16
Future End-of-Support Products 16
Sun4c-based Systems 16 SPARCstation Voyager 16 SPARC Xterminal 1 16
3. Open Issues 17
Prestoserve 2.4.2 — Patch Required 17 Booting From Partitions Greater Than
2-Gbytes (1234177) 18 SunFDDI Adapters Cannot Boot Sun4d Diskless Clients (4144414) 19 Quad Ethernet Controller—Dynamic Reconfiguration Not Supported 19 Serial Parallel Controller Driver 19
SerialParallelController DriverDoes NotSupportDynamic Reconfiguration
(4177805) 19
ISDN — Power Management Not Supported 20 /usr/ucblib/sparcv9 is Not Available (4114650) 20 SunScreen SKIP 1.1.1 Not Supported in Solaris 7 5/99 Operating Environment
20
iv Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Solstice SyMON Not Supported in Solaris 7 5/99 Operating Environment 21 SunVTS 3.2 Issues 21
New Features in This Release 21 SunVTS OPEN LOOK User Interface Support 22 Running SunVTS Online Diagnostics through Sun Enterprise SyMON 22 Disk Test (disktest) Mounting Issues 22 The SunVTS User Interface Disappears (4122829) 22 Some Devices Not Displayed Under Physical Mapping (4228489) 23
ShowMe TV 1.3 Known Problems 23
Software 23
PCMCIA Issues 24
If the PC ATA, pcata, module is modunloaded the system will appear to
hang (4096137) 24
The PCMCIA, pcic nexus, driver, does not support 3.3Volts PC Card
(4098998) 24
The PC ATA, pcata, disk driver crashes and hangs the system and causes a
memory leaks (4106401) 24
When booting Solaris 7 5/99 operating environment initially with 64-bit
kernel the device /dev/term/pc0, PC card serial driver, may not get created (4162969) 25
The PC ATA, pcata, driver panics the 64-bit kernel (4174177) 25
PC File Viewer Issues 25
Install in the /opt Directory 25 Known Bugs 25
Sun Remote System Control (RSC) Release Notes 26
What’s New in This Version 26 Hardware and Software Configurations Supported for RSC 27 Testing RSC Paging 28 Known Issues 29
Contents v
SunVTS Test for PGX32 Available 31 Copyright Notices 31
SunForum 2.0 Notices: 31
ShowMe TV 1.2.1 Notices: 31
Netscape Communicator Notices: 33
Sun Enterprise 10000 SSP 105684-04, 106281-01, and 106282-01 Notices: 33 Documentation Errata 34
PC launher Manpage 34
Platform Notes: The hme SunFastEthernet Device Driver Guide 35 Locale-Specific Bugs 35
SunForum BugID 4234195 35
ShowMe TV BugID 4234201 35
4. Sun Enterprise 10000 Server Open Issues 37
Sun Enterprise 10000 37
General Issues 37
Solaris 7 and Boot-Disk Partition Sizes 37
Operating Mode 38
Solaris 7 and the SSP 38
Documentation Errata 39
Known Bugs 40
Fixed Bugs 41 AP on the Sun Enterprise 10000 41
Installation Issues 41
General Issues 43
Known Bugs 45
Fixed Bugs 45 Dynamic Reconfiguration on the Sun Enterprise 10000 46
vi Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
General Issues 46 Known Bugs 49 DR and Inter-Domain Networks 51 Bugs Fixed 51
5. Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 53
AP on Sun Enterprise Servers 53
Installation Issues 54 General Issues 55 Known Bugs 56 Fixed Bugs 57
Dynamic Reconfiguration of Sun Enterprise 6x00, 5x00, 4x00, and 3x00
Systems 58 Supported Hardware 58
Firmware Notes 58 Software Notes 60 Known Bugs 63
Contents vii
viii Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CHAPTER
1

Late Breaking News

This manual provides the following information:
Late breaking news (this chapter)
End-of-support statements (chapter 2)
Open Issues (chapter 3)
This manual supplements the Solaris 7 5/99 Sun Hardware Platform Guide and the Solaris 7 5/99 Release Notes.

Service Contract Upgrades to the Solaris 7 5/99 Operating Environment

You may have received a Solaris Server Media Kit to upgrade systems to the Solaris 7 5/99 operating environment. Please note that your service contract entitles you to use only those products that apply to your original Solaris operating environment license. The following products, which may be in the media kit you received, are licensed solely to customers with the Solaris Easy Access Server 2.0 product or the Solaris™ Server Intranet Extension™ product, which was included as part of Sun Microsystems Computer Corporation's Solaris 2.6, Solaris 2.6 Hardware: 3/98, or Solaris 2.6 Hardware: 5/98 SPARC™ Server Media Kits:
Solstice™ AdminSuite™
Solstice AutoClient™
Solstice DiskSuite™
Solstice Data Backup Utility
Solstice PPP
TotalNET Advanced Server™
1
Java™ IDL
Solaris Management Console™
Sun™ WebServer™
Solstice Internet Mail Server™
Sun Directory Services
Solstice NFS Client™

Unbundled Product Support

If you are upgrading from an existing version of the Solaris operating environment and have installed unbundled products, either from Sun or from a different company, you must ensure that all those products are supported on the Solaris 7 5/99 operating environment prior to upgrading. Depending on the status of each unbundled product, you have three options for each unbundled product:
Verify that the existing version of the unbundled product is supported on the
Solaris 7 5/99 operating environment.
Acquire and install a new version of the unbundled product which is supported
on the Solaris 7 5/99 operating environment. Note that in this case you may need to remove the previous version of the unbundled product prior to upgrading to the Solaris 7 5/99 operating environment. See the unbundled product documentation for more details.
Remove the unbundled product prior to upgrading to the Solaris 7 5/99
operating environment.
For additional information contact the supplier of the unbundled product or your service provider or go to:
http://sunsolve.sun.com/sunsolve/pubpatches/patches.html

PC File Viewer Update

For updated information about PC file viewer, direct your browser to:
http://shop.sun.com/
From "Free Downloads" at this site, choose "PC file viewer".
2 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Documents on the Software Supplement for the Solaris 7 5/99 Operating Environment for Sun Computer Systems CD
Table 1-1 lists the documents available on the Supplement CD:
TABLE1-1 Documents on the Supplement CD
Path Comment
Docs/HWPG/EOS.html List of future end-of-support peripheral products Docs/HWPG/Hardware.ps Supported hardware matrices Docs/HWPG/HWPG_en.ps Solaris 7 5/99 Sun Hardware Platform Guide Docs/ODBC/
README.ODBC_en.html Docs/ShowMeTV1.2.1/UG_en.ps ShowMe™ TV™ 1.2.1 User’s Guide Docs/README_en.html/ Readme file for Solaris 7 5/99 Sun Computer
Readme file for ODBC
Systems Supplement CD
Note – The _en indicates an English language document. Other languages may be
indicated, depending on locale.
The Supplement CD also contains other documentation in AnswerBook™ packages and in man page packages. The documentation in AnswerBook packages can only be read through the AnswerBook2™ server software provided on the Solaris Documentation CD. Documents in the man page packages can only be read through the man command. Refer to the Solaris 7 5/99 Sun Hardware Platform Guide for details on installing these packages from the Supplement CD.
Chapter 1 Late Breaking News 3

Product Name and Title Changes

Sun Microsystems Name Changes

Earlier publications, documents, and software have included the names SunSoft™ and Sun Microsystems Computer Company or SMCC. Due to a Sun Microsystems reorganization, those names are no longer applicable.
For example, in some documents you may find references to a manual that was called SMCC Hardware Platform Guide. In this release, that document is now called Solaris 7 5/99 Sun Hardware Platform Guide. Another example is the supplement CD, which used to be called the SMCC Supplement CD, is now called the Solaris 7 5/99 Sun Computer Systems Supplement CD.

Solaris Name Change

This release of Solaris is called Solaris 7 instead of Solaris 2.7. As the Solaris product line continues to grow, this name change will make it easier for you to determine which products in the Solaris line you might want to use.
In Solaris 7, the transition to the new name change is in process. That means that you will still see references to Solaris 2.7, and even to Solaris 2.x.
The name of the core operating system has not changed. In this release, it is SunOS™ 5.7.

Solaris Server Intranet Extension Name Change

The new version of the Solaris™ Server Intranet Extension™ 1.0 product is named the Solaris™ Easy Access Server 2.0 product.
4 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Flash PROM Update for 64-bit Operations

Some sun4u systems need to be updated to a higher level of OpenBoot™ firmware in the flash PROM before they can run the 64-bit mode of the Solaris 7 5/99 operating environment. Systems that can only run the 32-bit mode (such as those in the sun4c, sun4d, and sun4m platform groups) do not require updated firmware to run Solaris 7 5/99 software.
The only systems that may require this flash PROM update are the following:
Ultra™ 1
Ultra 2
Ultra 450 and Sun™ Enterprise™ 450
Sun Enterprise 3000, 4000, 5000, and 6000 systems
See the Solaris 7 5/99 Sun Hardware Platform Guide for instructions for determining whether your system needs a flash PROM update and for instructions on performing that update.
For the Ultra and Ultra 2 systems, an antistatic wrist strap may be required for the update. If you need a wriststrap, send e-mail to strap@eng.sun.com

Flash PROM Update Multimedia AnswerBook CD

This CD provides video clips that illustrate how to perform steps involving hardware that are part of the procedures for updating the Flash PROM on some sun4u systems.
The video clips on this CD can be accessed several ways. Some software products are present on this CD to facilitate viewing of the videos directly from the CD. Do not use the AnswerBook2 server software or the ShowMe TV software on this CD to install these products permanently on a system. Instead, use the Solaris 7 5/99 Documentation CD to install AnswerBook2 server software and use the Supplement CD to install ShowMe TV software.
Note – The video clips on the Flash PROM Update Multimedia AnswerBook CD
have English language audio tracks. The volume level for the audio tracks is set to minimum. If you want to hear the English language audio track, you must adjust the audio level.
Chapter 1 Late Breaking News 5

Sun Enterprise SyMON Software Available

Sun Enterprise SyMON™ software is an open, extensible system monitoring and management solution that uses Java™ software protocol and Simple Network Management Protocol (SNMP) to provide an integrated and comprehensive enterprise-wide management of Sun products and their subsystems, components, and peripheral devices.
Sun Enterprise SyMON technology provides a solution to extend and enhance the management capability of Sun’s hardware and software solutions.
You can download Sun Enterprise SyMON software from:
http://www.sun.com/symon

Sun StorEdge A5000

For the latest firmware and patch information for the Sun StorEdge™ A5000, go to:
http://sunsolve1.Sun.COM
Click on SSA/A5000 Matrix under Free Services: Public Information.
6 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Localized Packages on the Software Supplement for the Solaris 7 5/99 Operating Environment for Sun Computer Systems CD

Japanese Localized Packages

CODE EXAMPLE 1-1 Japanese Localized Packages
Software Product Package Name Description
SunForum SUNWjadat Japanese (ja-EUC) SunForum
SUNWjpdat Japanese (ja-PCK) SunForum
Alternate Pathing SUNWjaap Japanese localization for Alternate
Pathing
Remote System Control SUNWjarsc Japanese (EUC) Remote System Control
SUNWjrscj Japanese (EUC) Remote System Control
GUI
ShowMe TV SUNWjasmt ShowMe TV Japanese (ja-EUC)
Localization Files
SUNWjpsmt ShowMe TV Japanese (ja-PCK)
Localization Files
SUNWjusmt ShowMe TV Japanese (ja-UTF8)
Localization Files
PC launcher SUNWjdpcv Japanese (Common) PC launcher help
SUNWjepcp Japanese (EUC) PC launcher message SUNWjppcp Japanese (PCK) PC launcher message SUNWjupcp Japanese (UTF-8) PC launcher message
Sun Gigagit Ethernet Adapter Driver
SUNWjegem Japanese (EUC) Sun Gigabit Ethernet
Adapter Driver Man Pages
SUNWjpgem Japanese (PCK) Sun Gigabit Ethernet
Adapter Driver Man Pages
Chapter 1 Late Breaking News 7
CODE EXAMPLE 1-1 Japanese Localized Packages (Continued)
Software Product Package Name Description
SUNWjugem Japanese (UTF-8) Sun Gigabit Ethernet
Adapter Driver Man Pages
SunFDDI SUNWjenfm Japanese (EUC) SunFDDI SBus Man
Pages
SUNWjepfm Japanese (EUC) SunFDDI PCI Man
Pages
SUNWjpnfm Japanese (PCK) SunFDDI SBus Man
Pages
SUNWjppfm Japanese (PCK) SunFDDI PCI Man
Pages
SUNWjunfm Japanese (UTF-8) SunFDDI SBus Man
Pages
SUNWjupfm Japanese (UTF-8) SunFDDI PCI Man
Pages
PC file viewer SUNWjepcv Japanese (EUC) PC File Format Viewer
SUNWjepcz Japanese (EUC) PC File Formats support
in CDE SUNWjppcv Japanese (PCK) PC File Format Viewer SUNWjppcz Japanese (PCK) PC File Formats support
in CDE SUNWjupcv Japanese (UTF-8) PC File Format Viewer SUNWjupcz Japanese (UTF-8) PC File Formats
support in CDE
SunVTS SUNWjpvtm Japanese (PCK) SunVTS Man Pages
SUNWjuvtm Japanese (UTF-8) SunVTS Man Pages SUNWjvtsm Japanese (EUC) SunVTS Man Pages
AnswerBook SUNWahwja Solaris 7 5/99 on Sun Hardware
Collection - Japanese
8 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

German Localized Packages

CODE EXAMPLE 1-2 German Localized Packages
Software Product Package Name Description
SunForum SUNWdedat German SunForum PC launcher SUNWdepcp PC launcher German messages PC file viewer SUNWdepcv PC File Viewer German messages
SUNWdepcz PC File Viewer German help and icons
ShowMe TV SUNWdesmt ShowMe TV German Localization Files

Italian Localized Packages

CODE EXAMPLE 1-3 Italian Localized Packages
Software Product Package Name Description
SunForum SUNWitdat Italian SunForum PC launcher SUNWitpcp PC launcher Italian messages PC file viewer SUNWitpcv PC File Viewer Italian messages
SUNWitpcz PC File Viewer Italain help and icons
ShowMe TV SUNWitsmt ShowMe TV Italian Localization Files

French Localized Packages

CODE EXAMPLE 1-4 French Localized Packages
Software Product Package Name Description
SunForum SUNWfrdat French SunForum PC launcher SUNWfrpcp PC launcher French messages PC file viewer SUNWfrpcv PC File Viewer French messages
SUNWfrpcz PC File Viewer French help and icons
ShowMe TV SUNWfrsmt ShowMe TV French Localization Files
Chapter 1 Late Breaking News 9

Spanish Localized Packages

CODE EXAMPLE 1-5 Spanish Localized Packages
Software Product Package Name Description
SunForum SUNWesdat Spanish SunForum PC launcher SUNWespcp PC launcher Spanish messages PC file viewer SUNWespcv PC File Viewer Spanish messages
SUNWespcz PC File Viewer Spanish help and icons
ShowMe TV SUNWessmt ShowMe TV Spanish Localization Files

Swedish Localized Packages

CODE EXAMPLE 1-6 Swedish Localized Packages
Software Product Package Name Description
SunForum SUNWsvdat Swedish SunForum PC launcher SUNWsvpcp PC launcher Swedish messages PC file viewer SUNWsvpcv PC File Viewer Swedish messages
SUNWsvpcz PC File Viewer Swedish help and icons
ShowMe TV SUNWsvsmt ShowMe TV Swedish Localization Files

Traditional Chinese Localized Packages

CODE EXAMPLE 1-7 Traditional Chinese Localized Packages
Software Product Package Name Description
SunForum SUNW5dat Traditional Chinese (zh_TW-BIG5) SunForum
SUNWhdat Traditional Chinese (zh_TW-EUC) SunForum
PC launcher SUNW5pcp PC launcher Traditional Chinese (zh_TW-BIG5)
messages
SUNWhcpcp PC launcher Traditional Chinese (common)
messages
10 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CODE EXAMPLE 1-7 Traditional Chinese Localized Packages (Continued)
Software Product Package Name Description
SUNWhdpcp PC launcher Traditional Chinese (zh_TW-EUC)
messages
PC file viewer SUNW5pcv PC File Viewer Traditional Chinese (zh_TW-BIG5)
messages
SUNWhcpcv PC File Viewer Traditional Chinese (common)
messages
SUNWhdpcv PC File Viewer Traditional Chinese (zh_TW-EUC)
messages
SUNW5pcz PC File Viewer Traditional Chinese (zh_TW-BIG5)
help andicons
SUNWhdpcz PC File Viewer Traditional Chinese (zh_TW-EUC)
help andicons
Remote System Control
SUNWhrsc Traditional Chinese (EUC) Remote System
Control
SUNWhrscj Traditional Chinese (EUC) Remote System
Control GUI
ShowMe TV SUNW5smt ShowMe TV Traditional Chinese (zh_TW-Big5)
Localization Files
Chapter 1 Late Breaking News 11

Simplified Chinese Localized Packages

CODE EXAMPLE 1-8 Simplified Chinese Localized Packages
Software Products Packaage Name Description
SunForum SUNWcdat Simplified Chinese (zh-EUC) SunForum PC launcher SUNWccpcp PC launcher SimplifiedChinese (common)
messages
SUNWcdpcp PC launcher SimplifiedChinese (zh-EUC)
messages
SUNWgpcp PC launcher SimplifiedChinese (zh-GBK)
messages
PC file viewer SUNWccpcv PC file viewer Simplified Chinese (common)
messages
SUNWcdpcv PC file viewer Simplified Chinese (zh-EUC)
messages
SUNWgpcv PC file viewer Simplified Chinese (zh-GBK)
messages
SUNWcdpcz PC file viewer Simplified Chinese (zh-EUC) help
and icons
SUNWgpcz PC file viewer Simplified Chinese (zh-GBK) help
and icons
Remote System Control
ShowMe TV SUNWcsmt ShowMe TV Simplified Chinese (zh-EUC)
SUNWcrsc Simplified Chinese (EUC) Remote System
Control
SUNWcrscj Simplified Chinese (EUC) Remote System
Control GUI
Localization Files
SUNWgsmt ShowMe TV Simplified Chinese (zh-GBK)
Localization Files
12 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Korean Localized Packages

CODE EXAMPLE 1-9 Korean Localized Packages
Software Product Package Name Description
SunForum SUNWkodat Korean SunForum PC launcher SUNWkcpcp PC launcher Korean (common) messages
SUNWkdpcp PC launcher Korean (ko) messages SUNWkupcp PC launcher Korean (ko.UTF-8) messages
PC file viewer SUNWkcpcv PC file viewer Korean (common) messages
SUNWkdpcv PC file viewer Korean (ko) messages SUNWkupcv PC file viewer Korean (ko.UTF-8) messages SUNWkdpcz PC file viewer Korean (ko) help and icons SUNWkupcz PC file viewer Korean (ko.UTF-8) help and icons
Remote System Control SUNWkrsc Korean (EUC) Remote System Control
SUNWkrscj Korean (EUC) Remote System Control GUI
ShowMe TV SUNWkosmt ShowMe TV Korean (ko-EUC) localization files
SUNWkusmt ShowMe TV Korean (ko-UTF-8) localization files
Chapter 1 Late Breaking News 13
14 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CHAPTER
2

End-of-Support Products

This chapter contains a list of the end-of-support products for the Solaris 7 release, including the Solaris 7 5/99 release.

End-of-Support Products

The following hardware and software products are no longer supported in this Solaris 7 5/99 release. For more information, contact your authorized Sun support provider.

Network Devices — BEC Device and be Driver

The BEC device and be driver are not supported in the Solaris 7 5/99 release.

Graphics Devices—Discontinued Frame Buffers

The following frame buffers are not supported in the Solaris 7 5/99 release.
MG1 (bwtwo)
MG2 (bwtwo)
CG2 (cgtwo)
CG4 (cgfour)
TC (cgeight)
ZX (leo)
TZX (leo)
15

PEX Graphics Library

The Solaris™ PEX™ graphics library and server extension are no longer supported in this Solaris 7 5/99 release.

Future End-of-Support Products

Support for the following products may be discontinued in future releases. For more information, contact your support provider.

Sun4c-based Systems

The following sun4c architecture systems and servers based on these systems may no longer be supported in future releases:
SPARCstation™ SLC, SPARCstation ELC, SPARCstation IPC, SPARCstation IPX, SPARCstation 1, SPARCstation 1+, and SPARCstation 2
Note – All hardware options (such as SCSI devices) and supported configurations
that are dependent upon the sun4c architecture may no longer be supported in future releases. A list of these options is included in the Supplement CD /docs directory in the file named EOS.html.

SPARCstation Voyager

SPARCstation™ Voyager™ systems may no longer be supported in future releases.

SPARC Xterminal 1

SPARC Xterminal™ 1 systems may no longer be supported in future releases.
16 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CHAPTER
3

Open Issues

Prestoserve 2.4.2 — Patch Required

The Prestoserve™ 2.4.2 release will not function properly with the Solaris 7 5/99 software environment if the workaround below is not implemented. Below is a partial list of some of the platforms and hardware options that may be affected:
Ultra™ 1 Creator Model 170E
Ultra 1 Creator3D Model 170E
Sun™ Enterprise™ 1 Model 170E
SunSwift™ SBus Adapter Card
If you installed Prestoserve 2.4.2 and are using a platform or hardware option listed above, you must do the following steps to provide compatibility:

1. Edit the /etc/system file and add the following information:

set fas:fas_enable_sbus64 = 0

2. Reboot your system.

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.
17
If you installed Prestoserve 2.4.2 and are using an Ultra 2 platform (200MHz or 300MHz), you must do the following steps to provide compatibility:

1. Edit the /etc/system file and add 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).
18 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

SunFDDI Adapters Cannot Boot Sun4d Diskless Clients (4144414)

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

Quad Ethernet Controller—Dynamic Reconfiguration Not Supported

The Quad Ethernet (QE) and Quad Ethernet Controller (QEC) must be configured with other non-Dynamic Reconfiguration (DR) boards. DR does not support QE and QEC on Sun Enterprise X000 platforms running the Solaris 7 5/99 operating environment or compatible versions.

Serial Parallel Controller Driver

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

Contact your service provider for availability of patch 106827-01. The patch is not available at the time of this release.
Chapter 3 Open Issues 19

ISDN — Power Management Not Supported

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

/usr/ucblib/sparcv9 is Not Available (4114650)

Any application requiring ucblib will not link or run with the 64-bit Solaris operating environment.
Workaround: No workaround is available at this time. Contact your authorized Sun support provider for more information.

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

If you have SunScreen™ SKIP 1.1.1 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:
SICGbdcdr
SICGc3des
SICGcdes
SICGcrc2
SICGcrc4
SICGcsafe
SICGes
SICGkdsup
SICGkeymg
SICGkisup
20 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

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

If you have Solstice SyMON currently installed on your system, you should remove the SyMON packages before installing or upgrading to the Solaris 7 5/99 operating environment. The packages you should remove are:
SUNWsyc
SUNWsye
SUNWsym
SUNWsyrt
SUNWsys
SUNWsyu
SUNWsyua
SUNWsyub
SUNWsyuc
SUNWsyud
SUNWsyue
SUNWsyuf
For information on the availability of Sun Enterprise SyMON 2.0, go to:
http://www.sun.com/servers/symon.html

SunVTS 3.2 Issues

The following issues apply to the SunVTS™ 3.2 product.

New Features in This Release

A new test called sunpcitest was added to support testing of the SunPCi plug-in PCI card.
Chapter 3 Open Issues 21

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.

Running SunVTS Online Diagnostics through Sun Enterprise SyMON

The SunVTS 3.2 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.
Example:
# /opt/SUNWvts/bin/vtsui.online -h hostname
For more information about running SunVTS in an online or offline environment, refer to the SunVTS 3.2 User’s Guide.

Disk Test (disktest) Mounting Issues

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

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.
22 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Example (starting the SunVTS CDE user interface):
# /opt/SUNWvts/bin/vysui

Some Devices Not Displayed Under Physical Mapping (4228489)

In some cases, some devices that are displayed under logical mapping are not displayed under physical mapping.
Workaround: Choose logical mapping in the SunVTS main window to select devices that do not come up under physical mapping.

ShowMe TV 1.3 Known Problems

Software

ShowMe TV 1.3 contains support for MPEG2 movie playback. Support was dropped for the SunMedia Center in ShowMe TV 1.3. Also, ShowMe TV 1.3 contains a number of bug fixes over 1.2.1. Here is a list of some known problems:
There are various minor problems with playing MPEG1/2 files: zoom does not
work on some frame-buffers, the position indicator is not accurate enough, the frame by frame step back function does not work.
You can not switch between CIF and QCIF H.261 streams (i.e. regular resolution,
or 352x288 size frames, and low resolution,or 176x244 size frames) on non_Ultra systems.
Mixing Asian and ASCII characters in one line of text can confuse the input/
output functions in ShowMe TV. In particular, if a user sets up a transmission in which the transmission name and/or the hostname contain Asian characters, then saving/recovering these parameters to/from the .showmetv-programs­<hostname> configuration file might not work correctly.
The Receiver’s buttons and menus contain incorrect text in locales other than
English (bug id# 4210702).
Chapter 3 Open Issues 23

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

The PCMCIA, pcic nexus, driver, does not support 3.3Volts PC Card (4098998)

Description: The PCMCIA, pcic nexus, driver does not support 3.3V on devices. Cards that are 3.3V and 3.3V/5V will not work properly (seems to hang the system).
Workaround: none

The PC ATA, pcata, disk driver crashes and hangs the system and causes a memory leaks (4106401)

Description: Most attempts to insert/remove and use PCMCIA cards will crash or hang the machine. If it does not crash the machine it can cause memory leaks or create situations where other modules will not load.
Workaround: none
24 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
When booting Solaris 7 5/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 Solaris 7 5/99 operating environment initially with 64­bit kernel, /dev/term/pc0 hardware device node for PC card serial device may not be created.
Workaround: Boot the system up with 32-bit kernel first, then reboot with 64-bit kernel.

The PC ATA, pcata, driver panics the 64-bit kernel (4174177)

Description: Inserting the PC card after system init panics the 64-bit Solaris. Booting the 32-bit Solaris and accessing the card will not panic the system. The PC ATA driver is not a 64-bit driver.
Workaround: none

PC File Viewer Issues

Install in the /opt Directory

The Solaris 7 5/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

Backdrop image is not displayed in PowerPoint97 document (4159447)
Cannot display non-standard fonts in PowerPoint97 (4159448)
Excel graph/table in PowerPoint97 document is not displayed (4159449)
Chapter 3 Open Issues 25
Can not display scaled font, colored text, italic-underlined text in PowerPoint97
(4159450, 4159451, 4159452)
Copy and Paste of certain files into a text editor results in * (asterisks) instead of
actual text (4165089)
Searching does not work for multi-byte (tch, ko) in PC file viewer (4151774)
Wrong string is reversed in PC file viewer search on Japanese locales (4171815)
Cannot display TCH Word95 saved in Word97 or PowerPoint97 formats in
zh.TW.BIG5 locale (4150413)

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 OBP environment variable named "tpe-link-test?", 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.
The following bugs have been fixed since the November 16, 1998 release:
4172574: The CLI reported a DC Power Failure when the host was powered off.
4152840: RSC shell commands did not query for confirmation before resetting the
host system.
4170986: The GUI "Set Date/Time" dialog box displayed 0:00:00 when time
changed to noon and midnight. This is an invalid time format.
4173022: The escape sequence for exiting from the RSC console did not work if
the escape_char variable was set to "^?".
26 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
4175561: When connected to the server’s console through RSC, a paste operation
of over 336 characters into the window connected to RSC could hang the console connection. A reset of RSC was required to recover.

Hardware and Software Configurations Supported for RSC

Supported Server:

Sun Enterprise(tm) 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 systems running the Solaris 7 operating environment
Sun systems running the Solaris 2.6 5/98 operating environment
Systems running the Microsoft Windows 95 operating environment
Systems running the Microsoft Windows 98 operating environment
Systems running the Windows NT Workstation operating environment
Sun JDK 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. The required version for the Solaris 2.6 operating environment is available at http://www.sun.com/solaris/java. Sun JDK is included in the install package for Windows clients.

Supported CLI Clients:

ASCII character terminals
Systems running ASCII terminal emulation software
Systems with telnet client software
Chapter 3 Open Issues 27

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.

SunVTS:

To run the SunVTS test for RSC on systems running the Solaris 2.6 5/98 operating environment, you must install the unbundled rsctest package. This package is available for download from the RSC Web page at http://sunsolve2.sun.com/ sunsolve/E250_RSC/, and is also provided on the Sun Enterprise 250 Supplement CD. The rsctest package is already included in SunVTS version 3.0 and later.

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 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"
28 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
If RSC successfully transmits a page, no error message is added to theevent log. RSC can fail to send a page notification for the following reasons:
1. It failed to communicate with the modem.
2. It failed to contact the paging service specified by the page_info1 or page_info2
variable.
3. A failure occurred while RSC was communicating with the paging service TAP
server.
When a page fails, check the following:

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

2. That all the RSC page_variables (page_info1 and 2, page_init1 and 2, and page_baud1 and 2) are set correctly and match the settings for your paging service.
3. Insure that 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 themodem to recognize the dial tone of the phone line. This can be accomplishedon most modems by increasing the value in the S8 register. See documentation that came with your modem for more details.

Known Issues

1. 4151918: The RSC subtests do not provide adequate failure information.

2. 4171924: The RSC GUI occasionally reports invalid exceptions when you Logout or Exit.

3. 4168266: Heavy use of UNIX tcsh shell commands in an RSC console session may stop RSC from responding to requests. Killing the tcsh shell restores RSC to normal behavior.
4. 4167862: A loghistory error is reported when the "index -n" value you specify is greater than the number of lines in the buffer
Chapter 3 Open Issues 29

5. 4171929: RSC sometimes reports a fan failure erroneously after a thermal shutdown.

6. 4145761: An RSC reset is required for changes to the serial_hw_handshake variable (or "Enable Hardware Handshaking" setting in the GUI) to take effect, but should not be required.
7. 4167651: RSC default configuration settings for pagers do not match modem configuration settings suggested in documentation.

8. 4171431: The GUI event log output differs from the CLI loghistory output.

9. 4170988: The RSC GUI Back button for the first instance of Help does not return you to the previous view.
10. 4172337: The error message displayed for an attempted third telnet or fifth user session needs improvement.
11. 4162419: In the Windows operating environment, the RSC GUI goes to the background when you cancel an operation after an error message.

12. 4158400: The message "[Loaded DTD html32 in 142ms]" appears when the RSC Help file is displayed.

13. 4151674: Clicking on "Set RSC Date and Time" sometimes displays a duplicate image of the "Set RSC Date and Time" option just above the option list, and below the "RSC for <hostname>" title.
14. 4159618: A GUI reset request and the resulting reset event are recorded in the incorrect order in the RSC event log.
15. 4159562: The telnet connection resets intermittently when you try to connect to the RSC console from the GUI.
16. 4159564: The Java Runtime Environment (JRE) may crash in the Windows 95 operating environment when you modify an RSC user account.
17. 4172331: In the RSC GUI Serial Port settings, there is a typo in the error message for Invalid IP Address.
18. 4159135: The RSC GUI has no option which shows the information returned by the CLI shownetwork command.
19. 4157854: Sometimes when a thermistor displays a warning in the Environmental Status window and you refresh the screen, the warning is mistakenly displayed for a different thermistor. Another refresh corrects this problem.
20. 4216814: Pressing Return in the GUI login screen fails to advance input focus to the next entry field.
30 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

SunVTS Test for PGX32 Available

The PGX32 VTS package is currently not bundled with SUNWvts. For version 3.2 refer to Patch #107732. This patch has been incorporated in the S7 5/99 Supplemental CD in the Patch directory.

Copyright Notices

The following copyright information was not included in the Software Supplement for the Solaris 7 5/99 Operating Environment for Sun Computer Systems CD.

SunForum 2.0 Notices:

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

2. Copyright Teles Ag 1999

ShowMe TV 1.2.1 Notices:

Copyright® 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.
Chapter 3 Open Issues 31
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
32 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
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 105684-04, 106281-01, and 106282-01 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.
Chapter 3 Open Issues 33
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.

PC launcher Manpage

The sdtpcaction.conf manpage was left out of the manpage packages. Here is the content of the manpage (bug ID 4230365):
NAME
sdtpcaction.conf - sdtpcaction configuration file
FILE FORMAT
The format of this file is as follows.
VERSION : 1.0 SOLARIS_HOST: Host name of Solaris DEFAULT : default PC_TYPE PC_HOST : Host name for PC PC_TYPE : SunPC | SoftWindows | RemotePC
Optional:
PC_HOME : Directory shared by PC and Solaris. Can be
used if for security reason the user does not
want to map unix home directory to PC. INITIALIZATION_COMMAND: command to initialize PC emulator CLIENT_NAME: ICCCM client name of PC emulator window
These records are stored for each Solaris hostname.
FILES
$HOME/.dt/.sdtpcaction.conf PC Proxy configuration file
34 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

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.

Locale-Specific Bugs

SunForum BugID 4234195

In Helpful Information for WebStart installation, a link to the SunForum html file is broken. This problem can be seen in German, French, Italian, Spanish, and Swedish languages for the Desktop Configuration.
If it’s linked correctly, the following information is displayed: SunForum 2.0: SunForum is a suite of collaborative tools based on the International
Telecommunications Union (ITU) T.120 standards. SunForum consists of a Share Application program, a Shared Whiteboard application, File Transfer utility and a Chat Utility.
Requirements for SunForum 2.0: You need to allocate about 11 MB of disk space to this product.

ShowMe TV BugID 4234201

In "Co-Packaged Software Topics: Contents" for WebStart installation lists wrong version for ShowMe TV. ShowMe TV 1.2.1 is included in this release, not ShowMe TV 1.3. This problem can be seen in German, French, Italian, Spanish, and Swedish languages for the Desktop Configuration.
Chapter 3 Open Issues 35
36 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CHAPTER
4

Sun Enterprise 10000 Server Open Issues

Sun Enterprise 10000 Server

This chapter contains general issues, known bugs, patches, and notes about the Solaris 7 5/99 release on the Sun Enterprise 10000 server.

General Issues

Alternate Pathing (AP) 2.2 and Dynamic Reconfiguration (DR) are supported in the Solaris 7 release. Inter-Domain Networks (IDNs) are not supported. Upgrades from the Solaris 2.3 or Solaris 2.4 operating environments to the Solaris 7 operating environment are not supported.
Note – Before beginning the fresh install or upgrade procedures, you must install
the SSP patches described in “Solaris 7 and the SSP” on page 38.
The Solaris 7 Operating Environment and Boot­Disk Partition Sizes
If you are upgrading the operating environment from the Solaris 2.6 operating environment to the Solaris 7 operating environment and you used the partition layout suggested in the SMCC Hardware Platform Guide Solaris 2.6, the partitions may
37
not be large enough for the upgrade to succeed. For instance, the /usr partition must be at least 653 megabytes. If /usr is smaller than the size needed to perform the upgrade, suninstall uses the Dynamic Space Reallocation (DSR) mode to reallocate the space of the disk partitions.
DSR may calculate a partition layout which is not acceptable for some systems. For instance, DSR may select partitions that appear to DSR as being unused (non-UFS partitions which may contain raw data or other types of file systems). If DSR selects a used partition, data loss may occur. Therefore, you must know the current status of the partitions DSR wants to use before you allow DSR to continue with the reallocation of the disk partitions.
After DSR presents an acceptable layout and you choose to proceed with the reallocation, DSR will adjust the affected file systems, and the upgrade will continue. However, if you cannot constrain the layout so that it is acceptable for your needs, then you may need to manually repartition the boot device, or you may have to perform a fresh install.

Operating Mode

On the Sun Enterprise 10000, you can check whether a domain is running in 32-bit or in 64-bit mode by using the following command:
domain_name# isainfo -k sparcv9
The returned value, sparcv9, indicates that the domain is running the 64-bit operating mode; otherwise, the domain is running in 32-bit mode.
You can also use another command, isalist, to check the operating mode; however, the return value, sparcv9+vis, differs from the return value of the isainfo -k command. The values are synonymous. They both indicate that the domain is running in 64-bit mode.

Solaris 7 and the SSP

SSP 3.1 is the first SSP release to support Solaris 7. If you are installing Solaris 7 on a domain or upgrading a domain’s current Solaris operating environment, you must have SSP 3.1 installed on the SSP. SSP 3.0 does not support Solaris 7 on a domain. In addition, before you perform the fresh install or upgrade of the Solaris 7 software on an Sun Enterprise 10000 domain, the SSP must have Patch-ID 105684-04. This patch is on your Sun Computer Systems Supplements CD.
38 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Note – If the CD contains the latest version the patch, indicated by a higher-
numbered suffix, use that patch instead of the patch number indicated in this section.

Patch-ID 105684-04

Description: OBP/download_helper needs to support 2.7 BugIDs fixed with this patch: 4078459 4083870 4084325 4097230 4102171 4118746
4137422 4146592

Patch-ID 106281-01

Description: SSP 3.1 sys_id -m doesn't work in year 2000 or after
(Y2K bug)
BugIDs fixed with this patch: 4105569

Patch-ID 106282-01

Description: SSP 3.1 Hostview suppresses trap messages after 1999 BugIDs fixed with this patch: 4108443

Documentation Errata

This section contains errors in the documentation that pertains to the Solaris operating environment on the Sun Enterprise 10000 server.

Fresh Install Procedure

In the “Solaris 7 5/99 on the Sun Enterprise 10000 Server” chapter of the Sun Hardware Platform Guide Solaris 7 5/99, the Fresh Install procedure points the reader to the “Setting up the SSP as a Boot Server” section if the domain in question already exists. The procedure should, however, point the reader to the “Updating the OpenBoot PROM” section.
The Fresh Install procedure is not intended to be used for installations in which the domain already has an eeprom.image file associated with it on the SSP. Note that if you have removed the domain by using the domain_remove(1M) command, you
Chapter 4 Sun Enterprise 10000 Server Open Issues 39
will need to perform all of the procedures in the Fresh Install section to recreate the eeprom.image. If the eeprom.image already exists, refer to the “Performing an Upgrade” section.

OBP Variables

Before you perform the boot net command from the OBP prompt (ok), you must verify that the local-mac-address? variable is set to false, which is the factory default. If it is set to true, you must ensure that this value is an appropriate local configuration.
Caution – If local-mac-address? is set to true, it may prevent the domain from
successfully booting over the network.
In a netcon(1M) window, you can use the following command at the OBP prompt to display the values of the OBP variables:
ok printenv
To Set the local-mac-address? Variable
If the variable is set to true, use the setenv command to set it to false.
ok setenv local-mac-address? false

Solaris Version Names

The version name for the Solaris operating environment changed in Sun publications with the release of Solaris 7 5/99; however, the version name in the code did not change. Thus, you should use 2.7 wherever the procedures call out for the version number of the operating system. For instance, in the “Creating a New Domain” procedure in the Fresh Install section, you should use 2.7 for the version name, as in the following example:
ssp# domain_create -d domain_name -b board_numbers -o 2.7 -p platform_name
40 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Known Bugs

There are no Sun Enterprise 10000-specific bugs known to exist in the Solaris 7 5/99 release.

Fixed Bugs

This section lists important bugs that have been fixed. Minor bugs are not included. Each entry includes a 7-digit BugID assigned by Sun to aid in bug-tracking and a one-line description of the bug.
4110199 – /etc/init.d/cvc Implementation, Packaging Inconsistent

AP on the Sun Enterprise 10000

Alternate Pathing (AP) 2.2 is the first release of AP that is supported on Sun Enterprise 10000 domains running the Solaris 7 5/99 operating environment.
Note – AP 2.2 is the first AP release to support Solaris 7 5/99.
AP enables you to define and control alternate physical paths to peripheral devices, adding increased availability and a level of fault recovery to your server. If a physical path to a device becomes unavailable, an alternate path can be used. For more information, see the Sun Enterprise Server Alternate Pathing 2.2 User’s Guide in the Solaris 7 5/99 on Sun Hardware Collection AnswerBook.
Note – At the time of this printing, AP 2.2 Beta is not compatible with any version
of Sun Enterprise Volume Manager™ (SEVM).

Installation Issues

If you are upgrading from the Solaris 2.5.1 or 2.6 to Solaris 7 5/99 operating environments and have AP 2.0 or 2.1 and Solstice™ DiskSuite™ 4.0 or 4.1 (SDS) on your system, you must upgrade to AP 2.2 and SDS 4.2. This section contains an overview of the entire process, which requires you to use several sections from different publications. You should ensure that you have the following publications before you start the upgrade:
Chapter 4 Sun Enterprise 10000 Server Open Issues 41
Solaris 7 5/99 Beta Release Notes Supplement for Sun Hardware (available in printed
form in your Solaris 7 5/99 Media Kit)
Solaris 7 5/99 Sun Hardware Platform Guide, (available in printed form in your
Solaris 7 5/99 Media Kit or in AnswerBook2 format on the Sun Hardware Supplements CD)
Sun Enterprise Server Alternate Pathing User’s Guide (available in AnswerBook2
format on the Sun Hardware Supplements CD in your Solaris 7 5/99 Media Kit)
Solstice DiskSuite 4.2 User ’s Guide (available in AnswerBook2 format from
http://docs.sun.com or from your SDS Media Kit)
Solstice DiskSuite 4.2 Installation and Product Notes (available in AnswerBook2
format from http://docs.sun.com or from your SDS Media Kit)
Caution – You must follow the sequence given here to successfully complete the
upgrade.
In general, you will perform the following tasks:
Unconfigure SDS 4.0 or 4.1.
Remove AP 2.0 or 2.1.
Upgrade to the Solaris 7 5/99 operating environment.
Install AP 2.2.
Install and reconfigure SDS 4.2.
Specifically, you must perform the following tasks:
1. Read “Performing an Upgrade of AP” in “Alternate Pathing 2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide.
2. Commit any uncommitted AP metadevices (see Step 1 in “To Upgrade AP” in “Alternate Pathing 2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide).
3. Deconfigure SDS (see steps 1 through 8 in “How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1” in the Solstice DiskSuite 4.2 Installation and Product Notes).
Caution – Do not install Solaris 7 5/99 at this time.
4. Perform steps 3 through 5 in “To Upgrade AP” in “Alternate Pathing 2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide).
Note – For this beta release, you must remove the SUNWapap package as part of
Step 3a in “To Upgrade AP” in the Solaris 7 5/99 Sun Hardware Platform Guide .
42 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
5. Upgrade to Solaris 7 5/99 (see Step 6 in “To Upgrade AP” in “Alternate Pathing
2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide).
6. Follow steps 6 through 9 in “To Upgrade AP” in “Alternate Pathing 2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide).
7. Install SDS 4.2, then restore it (see Step 10 in “To Upgrade AP” in “Alternate Pathing 2.2 on the Sun Enterprise 10000” in the Solaris 7 5/99 Sun Hardware Platform Guide and steps 10 through 16 in “How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1” in Chapter 1 of the Solstice DiskSuite 4.2 Installation and Product Notes).

General Issues

This section contains general issues that involve AP on the Sun Enterprise 10000 server. You should read this section before you attempt to install or configure AP.

Supported Devices

The following devices are supported by the AP software on Sun Enterprise servers:
SPARCstorage™ Arrays recognized by AP using the pln, soc, and ssd ports
Sun™ StorEdge™ A5000 recognized by AP using sf, soc, and ssd ports
SunFastEthernet™ 2.0 (hme)
SunFDDI™ 5.0 (nf) SAS (Single-Attach Station) and DAS (Dual-Attach Station)
SCSI-2/Buffered Ethernet FSBE/S and DSBE/S ( le)
Quad Ethernet (qe)
Sun™ Quad FastEthernet™ (qfe)
Sun GigabitEthernet 2.0 (ge)
The following table lists which network devices are supported in which releases:
TABLE4-1 Supported Network Devices
AP 2.0 AP 2.1 AP 2.2
Solaris 2.5.1 hme, le, nf, bf, hi,
qe, qfe
Solaris 2.6 (5/98) N/A ge, hme, le, nf, qe,
Solaris 7 5/99 N/A N/A ge,hme, le, nf, qe,
Chapter 4 Sun Enterprise 10000 Server Open Issues 43
N/A N/A
N/A
qfe, vge
qfe

SunFDDI Devices

AP 2.2 validation tests were performed on SunFDDI (revision 6.0). If you install this device, you must use the revision level that was tested, unless a higher revision level exists. In addition, you must install all of the available patches for this device. Refer to http://www.sunsolve.sun.com for more information about the patches.

Sun StorEdge A3000

The Sun StorEdge A3000 supports failover capabilities that are similar to those provided by AP. Because of this, AP does not support the Sun StorEdge A3000. See that product’s documentation for more information about its failover support.

Sun StorEdge A5000

AP supports the Sun StorEdge A5000 for this release.

Sun StorEdge A7000

AP 2.2 does not support the Sun StorEdge A7000 for this release.

Software Compatibility

The following figures show the possible combinations of SSP, AP, and Solaris software you can install on a Sun Enterprise server. Note that the Sun Enterprise 10000 can have any combination of domains with the operating environment and software listed on the right of the figures. The version of the Solaris operating environment on the SSP and the version on the domain do not need to match.
Note – In the following figures, “base only” means no AP and no DR, unless
otherwise noted. Mainly, “base only” refers to a domain that has only the Solaris operating environment installed. In addition, some of the scenarios below are possible only if you install a patch, or a set of patches, on the SSP or on the domain. For more information about what patch, or patches, refer to the patch descriptions at http://sunsolve.sun.com.
44 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
SSP
SSP 3.0 AP 2.0 Solaris 2.5.1
FIGURE 4-1 SSP 3.0, AP 2.0, and Solaris 2.5.1 on the Sun Enterprise 10000
Up to five domains running:
• Solaris 2.5.1 with or without AP 2.0 and DR
SSP
SSP 3.1* AP 2.1 Solaris 2.5.1
* Requires patch 105684 for Solaris 7
FIGURE 4-2 SSP 3.1, AP 2.1, Solaris 2.5.1, Solaris 2.6 3/98, Solaris 2.6 5/98, and Solaris 7
Up to eight domains running:
• Solaris 2.5.1* with or without AP 2.0 and DR
• Solaris 2.6 3/98 (base only)
• Solaris 2.6 5/98 with or without AP 2.1 and DR
• Solaris 7 (base only)
* Requires patch 105029-11
on the Sun Enterprise 10000
SSP
SSP 3.1* AP 2.2 Solaris 2.5.1
* Requires patch 105684 for Solaris 7
FIGURE 4-3 SSP 3.1, AP 2.2, AP 2.1, Solaris 2.5.1, Solaris 2.6 3/98, Solaris 2.6 5/98, Solaris
Up to eight domains running:
• Solaris 2.5.1* with or without AP 2.0 and DR
• Solaris 2.6 3/98 (base only)
• Solaris 2.6 5/98 with or without AP 2.1 and DR
• Solaris 7 (base only)
• Solaris 7 3/99 (base only)
• Solaris 7 5/99 with or without AP 2.2 and DR
* Requires patch 105029-11
7, Solaris 7 3/99, and Solaris 7 5/99 on the Sun Enterprise 10000

Known Bugs

There are no known bugs in this release of AP.
Chapter 4 Sun Enterprise 10000 Server Open Issues 45

Fixed Bugs

This section contains the synopses and Sun BugID number of the more important bugs that have been fixed since the AP 2.1 release (Solaris 2.6 5/98). This list does not include all of the fixed bugs.
4126743 – AP disk autofailover hangs on simultaneous multi-pathgroup failures (this bug was fixed by BugID 4136249).
4126897 – Domain panics when there are no AP database and metadevice entry in /etc/vfstab.
4136249 – I/O’s to SEVM RAID volumes hang after AP autofailover. 4141438 – mhme interface hangs under heavy use of network. 4143514 – FDDI with AP hangs with heavy use of network. 4147674 – AP causes ifconfig to hang on a mutex. 4153152 – apconfig works as an ordinary user. 4161396 – AP 2.x needs capability to work with GEM. 4163270 – netstat of network ap network meta interface shows no tallies. 4166620 – snoop of AP meta network interface stops snooping after switch. 4170818 – If you run the $<callouts nadb macro, or fm2’s “callout ts” command, you
see thousands of qenable timeouts in the timeshare callout table. 4180055 – Accessing an AP’d metadisk with a failed active alternate panics. 4180702 – Messages from swap.c are not internationalized. 4183581 – apboot disk causes coredump when disk is the same as the current boot
disk. 4185154 – GigabitEnthernet stress test hangs. 4188418 – It is possible for a hard disk error to go undetected by Veritas [SEVM]. 4195441 – AP2.0 ap_daemon doesn’t communicate with AP2.2. 4226867 – ap_reboot_host fails for photon in mixed AP versions. 4228731 – Non-existent network interfaces not marked as detached after reboot.
46 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Dynamic Reconfiguration on the Sun Enterprise 10000

Release notes and other technical information in this section apply only to the Solaris 7 5/99 version of Sun Enterprise 10000 Dynamic Reconfiguration (DR).

General Issues

This section contains general issues that involve DR on the Sun Enterprise 10000 server. You should read this section before you attempt to install or configure DR.

dr-max-mem Utility

The way dr-max-mem is used has changed since the Solaris 2.5.1 release. Please see the appropriate section of the Solaris 7 5/99 version of the Sun Enterprise 10000 Dynamic Reconfiguration User's Guide for a detailed description of this important OBP variable.

DR and Bound User Processes

For the Solaris 7 5/99 operating environment, DR no longer automatically unbinds user processes from CPUs that are being detached. Users are now required to perform this operation themselves before initiating a DR Detach sequence. The DR Drain operation will fail if CPUs are found with bound processes.

Nonpageable Memory Location

For the Solaris 7 5/99 operating environment, the location of nonpageable memory (that is, OBP and kernel memory), the kernel cage, resides in the highest physical address space, which generally is on the highest-numbered system board in the domain. The direction of growth of this area is from highest to lowest physical addresses. Exceptions to this rule do exist. Always use drshow(1M) to verify a board’s memory state.
Chapter 4 Sun Enterprise 10000 Server Open Issues 47

Kernel Cage Location

For the Solaris 7 5/99 operating environment, the location of the kernel cage changed from the lowest numbered system board(s) to the highest numbered board(s). However, some customers require the kernel cage to be located on the lowest numbered system board. If you have this requirement, you can apply Patch 105873-08, as a minimum level, on the SSP to change the location of the cage. Refer to the Patch README file for instructions on how to install the patch. You can obtain the patch from http://sunsolve.corp.sun.com or from your local service provider.

DR and Tape Drives

For the Solaris 7 5/99 operating environment, the st driver, which has been considered DR unsafe in the past, is now DR safe. The driver now waits for existing I/O requests to complete before the drive is suspended.

DR and SunFDDI

If your Sun Enterprise 10000 server contains any SunFDDI™ SBus Adapter 5.0 interfaces and you plan to use DR, you must install Sun Patch 104572-05, or the highest revision level available. You can obtain this patch at the following Web site:
http://sunsolve.corp.sun.com

DR and the Sun StorEdge A3000

Dynamic Reconfiguration of Sun™ StorEdge™ A3000 arrays on the Sun Enterprise 10000 running the Solaris 2.6 operating environment requires RAID Manager 6.01.00, or later, for correct operation.

DR and the Sun StorEdge A5000

DR will be supported on systems configured with Sun StorEdge A5000 devices and the latest StorEdge A5000 patch. Contact your service provider for more information on how to obtain the patch.
For I/O boards connected to the A5000, you must ensure that the FC-AL disk firmware version is ST19171FC 0413 or newer version. For more information, refer to the following Web site:
http://sunsolve2.Sun.COM/sunsolve/Enterprise-dr/
48 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

DR and pln and soc Drivers

If you are using pln and/or soc drivers on your server, you must ensure that the parameters are properly set in the /etc/system file. The file should include the following two entries, exactly as the appear in the example.
set pln:pln_enable_detach_suspend=1 set soc:soc_enable_detach_suspend=1

Quiesce Test

On a large system, the quiesce-test command cfgadm -x quiesce-test sysctrl0:slotnumber may run as long as a minute or so. During this time no messages are displayed if cfgadm does not find incompatible drivers. This is normal behavior.

Known Bugs

This section contains the known bugs in the Sun Enterprise 10000 DR feature of the Solaris 7 5/99 release.

DR Abort Detach May Not Resume All Detached Disks (4010910)

If a DR detach operation fails to detach an sd device and the controller has sd devices that have already been detached, the abort-detach operation does not resume (that is, re-attach) those devices that share the same controller instance and that have already been detached. This situation rarely occurs. The most likely time for it to happen is if the disk drive firmware is locked up.
Workaround: None

dr_daemon Does Not Find Veritas Device Usage (4011123)

Veritas software usage of disks is not displayed by DR applications in their device­usage displays.
Workaround: None
Chapter 4 Sun Enterprise 10000 Server Open Issues 49
disks(1M) Command Preens Controller Entries and Corrupts the Sun StorEdge A3000 Device Tree (4096048)
The Solaris disks(1M) command preens or deletes symbolic link entries when disk devices are no longer present in an Enterprise 10000 domain. If you have dynamically reconfigured the devices so that they are no longer present, the Symbios-managed device tree and the Solaris-managed device tree can become inconsistent.
Workaround: You must obtain the proper patch from SunSolve or from your service representative. This patch contains fixes that ensure persistent node names under the Solaris operating environment when StorEdge A3000 devices are dynamically reconfigured out of a given Enterprise 10000 domain. The patch ensures that when the same array is brought back into the domain, it inherits the same node name it originally had, thereby maintaining data availability without having to modify system mount points or user application configurations. You must ensure that you do not perform reconfiguration reboot operations (boot -r) in a domain when A3000 devices are present on the system boards.

Cannot Drain and/or Detach Sun Enterprise Server System Boards that Host QFE Cards (4231845)

The configuration of a boot server for Solaris 2.5.1-based x86 clients results in the execution of rpld daemons. These daemons maintain an active (open) reference to all network devices, whether or not such devices are in use. These active references prevent DR operations from detaching these devices.
Workaround: Remove or rename the /rplboot directory, then shut down and restart NFS with these commands:
# sh /etc/init.d/nfs.server stop # sh /etc/init.d/nfs.server start

Sonoma Daemon Cannot Be Suspended (4100212)

The presence of Sonoma daemons (rdaemon) prevent a DR Detach operation from completing if the operating environment must be quiesced (that is, suspended and resumed) to detach non-pageable memory.
50 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Workaround: Temporarily disable the daemon before the DR operation, then restart the daemon after the DR operation by using the following command:
# sh /etc/rc2.d/S90amon stop # sh /etc/rc2.d/S90amon start

Unable to Drain Sysboards in Solaris 7 and dr_daemon Segmentation Faults (4229238)

After numerous iterations through a failure handling condition within the DR daemon, the daemon can encounter a segmentation violation (that is, a core dump). Note that this condition occurs during an error handling flow (that is, a DR operation failure).
Workaround: Restart the DR applications on the SSP.

DR and Inter-Domain Networks

The Inter-Domain Network (IDN) software is not supported in this release. However, IDN messages may appear during DR detach operations. If you see any IDN-related messages you can safely ignore them.

Bugs Fixed

The following important bugs have been fixed since the last release of DR. This list does not include minor bugs, nor does it include those bugs that were fixed in patches.
4083412 – socal and sf need to support DETACH/SUSPEND/RESUME 4090750 – DR panics during detach when dr-max-mem set is high. 4067860 – SUNWcsr on upgrading from Solaris 2.5.1 8/97 to Solaris 2.6 5/98 creates
duplicate majors in name_to_major. 4131197 – dr_daemon core dumps with Solaris 2.6 5/98 release. 4133607 – DR operations with mem_board_interleave_ok cause problems. 4134357 – availrmem is not being reduced during Sun Enterprise 10000 memory
detach. 4135366 – Sun StorEdge A3000 patch has been changed.
Chapter 4 Sun Enterprise 10000 Server Open Issues 51
4136544 – Getting “flusher thread” hang during DR drain with official -20 KU patch.
52 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
CHAPTER
5

Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues

AP on Sun Enterprise Servers

This section contains the release notes for Alternate Pathing (AP) 2.2 on all Sun Enterprise servers, except the Sun Enterprise 10000. See “AP on the Sun Enterprise 10000” for information about the Enterprise 10000 server.
Note – AP 2.2 is the first release of AP that supports Solaris 7 5/99.
AP enables you to define and control alternate physical paths to peripheral devices, adding increased availability and a level of fault recovery to your server. If a physical path to a device becomes unavailable, an alternate path can be used. For more information, see the Sun Enterprise Server AP User’s Guide in the Solaris 7 5/99 on Sun Hardware Collection AnswerBook2™.
Note – At the time of this printing, AP 2.2 Beta is not compatible with any version
of Sun Enterprise Volume Manager™ (SEVM).

Installation Issues

If you are upgrading from the Solaris 2.6 operating environment to the Solaris 7 5/99 operating environment and have AP 2.1 and Solstice™ DiskSuite™ 4.0 or 4.1 (SDS) on your system, you must upgrade to AP 2.2 and SDS 4.2. This section
53
contains an overview of the entire process, which requires you to use several sections from different publications. You should ensure that you have the following publications before you start the upgrade:
Solaris 7 5/99 Beta Release Notes Supplement for Sun Hardware (available in printed
form in your Solaris 7 5/99 Media Kit)
Solaris 7 5/99 Sun Hardware Platform Guide, (available in printed form in your
Solaris 7 5/99 Media Kit or in AnswerBook2 format on the Sun Hardware Supplements CD)
Sun Enterprise Server Alternate Pathing User’s Guide (available in AnswerBook2
format on the Sun Hardware Supplements CD in your Solaris 7 5/99 Media Kit)
Solstice DiskSuite 4.2 User ’s Guide (available in AnswerBook2 format from
http://docs.sun.com or from your SDS Media Kit)
Solstice DiskSuite 4.2 Installation and Product Notes (available in AnswerBook2
format from http://docs.sun.com or from your SDS Media Kit)
Caution – You must follow the sequence given here to successfully complete the
upgrade.
In general, you will perform the following tasks:
Unconfigure SDS 4.0 or 4.1.
Remove AP 2.1.
Upgrade to the Solaris 7 5/99 operating environment.
Install AP 2.2.
Install and reconfigure SDS 4.2.
Specifically, you must perform the following tasks:

1. Read “Performing an Upgrade of AP” in the Solaris 7 5/99 Sun Hardware Platform Guide.

2. Commit any uncommitted AP metadevices (see Step 1 in “To Upgrade AP” in the Solaris 7 5/99 Sun Hardware Platform Guide).
3. Deconfigure SDS (see steps 1 through 8 in “How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1” in the Solstice DiskSuite 4.2 Installation and Product Notes).
Caution – Do not install Solaris 7 5/99 at this time.
4. Remove the current AP configuration (see Step 3 in “To Upgrade AP” in the Solaris 7 5/99 Sun Hardware Platform Guide).
5. Upgrade to Solaris 7 5/99 (see Step 4 in “To Upgrade AP” in the Solaris 7 5/99 Sun Hardware Platform Guide).
54 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
6. Upgrade to AP 2.2 (see Step 5 in “To Upgrade AP” in the Solaris 7 5/99 Sun Hardware Platform Guide).
7. Install SDS 4.2, then restore it (see Step 6 in “To Upgrade AP” in the Solaris 7 5/ 99 Sun Hardware Platform Guide and steps 10 through 16 in “How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1” in Chapter 1 of the Solstice DiskSuite 4.2 Installation and Product Notes).

General Issues

This section contains general issues that involve AP on Sun Enterprise servers. Read this section before you attempt to install or configure AP.

Supported Devices

The following devices are supported by the AP software on Sun Enterprise servers:
SPARCstorage™ Arrays recognized by AP using the pln,soc, and ssd ports
Sun™ StorEdge™ A5000 recognized by AP using sf, socal, and ssd ports
SunFastEthernet™ 2.0 (hme)
SunFDDI™ 5.0 (nf) SAS (Single-Attach Station) and DAS (Dual-Attach Station)
SCSI-2/Buffered Ethernet FSBE/S and DSBE/S ( le)
Quad Ethernet (qe)
Sun™ Quad FastEthernet™ (qfe)
Sun GigabitEthernet 2.0 (ge)
The following table lists which devices are supported in which releases:
TABLE5-1 Supported Network Devices
AP 2.0 AP 2.1 AP 2.2
Solaris 2.5.1 hme, le, nf, bf, hi,
qe, qfe
Solaris 2.6 (5/98) N/A ge, hme, le, nf, qe,
Solaris 7 5/99 N/A N/A ge,hme, le, nf, qe,
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 55
N/A N/A
N/A
qfe, vge
qfe

SunFDDI and GigabitEthernet Devices

AP 2.2 validation tests were performed on SunFDDI (revision 6.0) and GigabitEthernet (revision 2.0). If you install either of these devices, you must use the revision level that was tested, unless a higher revision level exists. In addition, you must install all of the available patches for these devices. Refer to http://www.sunsolve.sun.com for more information about the patches.

Sun StorEdge A3000

The Sun StorEdge A3000 supports failover capabilities that are similar to those provided by AP. Because of this, AP does not support the Sun StorEdge A3000. See that product’s documentation for more information about its failover support.

Sun StorEdge A5000

AP supports the Sun StorEdge A5000 for this release.

Sun StorEdge A7000

AP 2.2 does not support the Sun StorEdge A7000 for this release.

Software Compatibility

The following lists includes the possible combinations of AP and Solaris software you can install on a Sun Enterprise server.
Solaris 2.6 5/98 with AP 2.1 and DR
Solaris 7 with AP 2.2 and DR
Solaris 7 5/99 with AP 2.2 and DR

Known Bugs

The following bugs are known to exist in the Beta version of AP 2.2:
56 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Fixed Bugs

This section contains the synopses and Sun BugID number of the more important bugs that have been fixed since the AP 2.1 release (Solaris 2.6 5/98). This list does not include all of the fixed bugs.
4126743 – AP disk autofailover hangs on simultaneous multi-pathgroup failures (this bug was fixed by BugID 4136249).
4126897 – Domain panics when there are no AP database and metadevice entry in /etc/vfstab.
4136249 – I/O’s to SEVM RAID volumes hang after AP autofailover. 4141438 – mhme interface hangs under heavy use of network. 4143514 – FDDI with AP hangs with heavy use of network. 4147674 – AP causes ifconfig to hang on a mutex. 4153152 – apconfig works as an ordinary user. 4161396 – AP 2.x needs capability to work with GEM. 4163270 – netstat of network ap network meta interface shows no tallies. 4166620 – snoop of AP meta network interface stops snooping after switch. 4170818 – If you run the $<callouts nadb macro, or fm2’s “callout ts” command, you
see thousands of qenable timeouts in the timeshare callout table. 4180055 – Accessing an AP’d metadisk with a failed active alternate panics. 4180702 – Messages from swap.c are not internationalized. 4183581 – apboot disk causes coredump when disk is the same as the current boot
disk. 4185154 – AP GigabitEthernet stress test hands. 4188418 – It is possible for a hard disk error to go undetected by Veritas [SEVM]. 4195441 – AP2.0 ap_daemon doesn’t communicate with AP2.2. 4228731 – Non-existent network interfaces not marked as detached after reboot.
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 57

Dynamic Reconfiguration of Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems

These release notes provide the latest information on Dynamic Reconfiguration (DR) functionality for Sun Enterprise 6x00, 5x00, 4x00, and 3x00 systems running update version 5/99 of the Solaris 7 product line from Sun Microsystems. For more information on Sun Enterprise Server Dynamic Reconfiguration, refer to the Dynamic Reconfiguration User’s Guide for Sun Enterprise 3x00/4x00/5x00/6x00 Systems.
The 5/99 update includes support for CPU/Memory boards on Sun Enterprise 6x00, 5x00, 4x00, and 3x00 systems.

Supported Hardware

Before proceeding, ensure the system supports dynamic reconfiguration. If you see the following message on your console or in your console logs, the hardware is of an older design and not suitable for dynamic reconfiguration.
Hot Plug not supported in this system
Supported I/O boards are listed in the “Solaris 7 5/99” section on the web site
http://sunsolve5.sun.com/sunsolve/Enterprise-dr/
I/O board type 2 (graphics), type 3 (PCI), and type 5 (graphics and SOC+) are not currently supported.

Firmware Notes

FC-AL Disk Arrays or Internal Drives

For Sun StorEdge A5000 disk arrays or for internal FC-AL disks in the Sun Enterprise 3500 system, the firmware version must be ST19171FC 0413 or later. For more information, refer to the “Solaris 7 5/99” section at the web site:
http://sunsolve5.sun.com/sunsolve/Enterprise-dr/
58 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

PROM Updates for CPU and I/O Boards

Users of Solaris 7 5/99 software who wish to use dynamic reconfiguration must be running CPU PROM version 3.2.22 (firmware patch ID 103346-22) or later. This firmware is available from the web site. See “How To Obtain Firmware” on page 59.
Older versions of the CPU PROM may display the following message during boot:
Firmware does not support Dynamic Reconfiguration
Caution – CPU PROM 3.2.16 and earlier versions do not display this message,
although they do not support dynamic reconfiguration of CPU/memory boards.
To see your current PROM revision, enter .version and banner at the ok
prompt. Your display will be similar to the following:
ok .version Slot 0 - I/O Type 1 FCODE 1.8.22 1999/xx/xx 19:26 iPOST 3.4.22 1999/xx/xx 19:31 Slot 1 - I/O Type 1 FCODE 1.8.22 1999/xx/xx 19:26 iPOST 3.4.22 1999/xx/xx 19:31 Slot 2 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 3 - I/O Type 4 FCODE 1.8.22 1999/xx/xx 19:27 iPOST 3.4.22 1999/xx/xx 19:31 Slot 4 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 5 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 6 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 7 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 9 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 11 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 12 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 Slot 14 - CPU/Memory OBP 3.2.22 1999/xx/xx 19:27 POST 3.9.22 1999/xx/xx 19:31 ok banner 16-slot Sun Enterprise E6500 OpenBoot 3.2.22, 4672 MB memory installed, Serial #xxxxxxxx. Ethernet address 8:0:xx:xx:xx:xx, Host ID: xxxxxxxx.

How To Obtain Firmware

For information about updating your firmware, refer to the “Solaris 7 5/99” section at the web site.
http://sunsolve5.sun.com/sunsolve/Enterprise-dr/
At this site, you will find information on how to:
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 59
Download the DR-capable PROM firmware
Upgrade the PROM
If you cannot use the web site, contact your Sun support service provider for assistance.

Software Notes

Enabling Dynamic Reconfiguration

In the /etc/system file, two variables must be set to enable dynamic reconfiguration and an additional variable must be set to enable the removal of CPU/memory boards.
1. Log in as root.
2. To enable dynamic reconfiguration, edit the /etc/system file and add the following lines to the /etc/system file:
set pln:pln_enable_detach_suspend=1 set soc:soc_enable_detach_suspend=1
3. To enable the removal of a CPU/memory board, add this line to the /etc/system file:
set kernel_cage_enable=1
Setting this variable enables the memory unconfiguration operation.
4. Reboot the system to put the changes into effect.

Quiesce Test

On a large system, the quiesce-test command (cfgadm -x quiesce-test sysctrl0:slotnumber) may run as long as a minute or so. During this time no messages are displayed if cfgadm does not find incompatible drivers. This is normal behavior.
60 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Disabled Board List

If a board is on the disabled board list, an attempt to connect the board may produce an error message:
# cfgadm -c connect sysctrl0:slotnumber cfgadm: Hardware specific failure: connect failed: board is disabled: must override with [-f][-o enable-at-boot]
To override the disabled condition, use the force flag (-f) or the enable option
(-o enable-at-boot) with the cfgadm command:
# cfgadm -f -c connect sysctrl0:slotnumber
# cfgadm -o enable-at-boot -c connect sysctrl0:slotnumber
To remove all boards from the disabled board list, set the disabled-board-list
variable to a null set with the system command:
# eeprom disabled-board-list=
If you are at the OpenBoot prompt, use this OBP command instead to remove all
boards from the disabled board list:
OK set-default disabled-board-list
For further information about the disabled-board-list setting, refer to the section “Specific NVRAM Variables” in the Platform Notes: Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Systems, part number 805-4454.

Disabled Memory List

For information about the OBP disabled-memory-list setting, refer to the section “Specific NVRAM Variables” in the Platform Notes: Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Systems, part number 805-4454.
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 61

Unloading Detach-Unsafe Drivers

If it is necessary to unload detach-unsafe drivers, use the modinfo(1M) line command to find the module IDs of the drivers. You can then use the module IDs in the modunload(1M) command to unload detach-unsafe drivers.

Interleaved Memory

A memory board or CPU/memory board that contains interleaved memory cannot be dynamically unconfigured.
To determine if memory is interleaved, use the prtdiag command or the cfgadm command.
To permit DR operations on CPU/memory boards, set the NVRAM memory-interleave property to min.
For related information about interleaved memory, see “Memory Interleaving Set Incorrectly After a Fatal Reset, Bug-ID 4156075” on page 63 and “DR: Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory, Bug ID 4210234” on page 65.

Self-test Failure During a Connect Sequence

If the error “cfgadm: Hardware specific failure: connect failed: firmware operation error” is displayed during a DR connect sequence, remove the board from the system as soon as possible. The board has failed self-test, and removing the board avoids possible reconfiguration errors that can occur during the next reboot.
If you want to immediately retry the failed operation, you must first remove and reinsert the board, because the board status does not allow further operations.

Dynamic Reconfiguration Feature in Sun Enterprise SyMON Software

As noted in the Dynamic Reconfiguration User ’s Guide for Sun Enterprise 3x00/4x00/ 5x00/6x00 Systems, Sun Enterprise SyMON system monitoring and management software supports dynamic reconfiguration. However, the user’s guide listed the wrong reference. The correct reference is Sun Enterprise SyMON 2.0.1 Supplement for Sun Enterprise Midrange Servers, part number 806-0649.
62 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

Known Bugs

cfgadm -v Not Working Properly, bug-ID 4149371

Category: RFE The memory test should give occasional indications that it is still running. During a
long test, the user cannot easily determine that the system is not hanging. Workaround: Monitor system progress in another shell or window, using
vmstat(1M), ps(1), or similar shell commands.

Memory Interleaving Set Incorrectly After a Fatal Reset, Bug-ID 4156075

Category: Bug Memory interleaving is left in an incorrect state after a Sun Enterprise X500 server
encounters a Fatal Reset. Subsequent DR operations fail. The problem only occurs on systems with memory interleaving set to min.
Workarounds: Two choices are listed below.
To clear the problem after it occurs, manually reset the system at the OK prompt.
To avoid the problem before it occurs, set the NVRAM memory-interleave
property to max. This causes memory to be interleaved whenever the system is booted. However, you may find this option to be unacceptable, as a memory board containing interleaved memory cannot be dynamically unconfigured. See “DR: Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory, Bug ID 4210234” on page 65.

vmstat Output Is Incorrect After Configuring Processors, Bug-ID 4159024

Category: Bug
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 63
vmstat shows an unusually high number of interrupts after configuring CPUs. With vmstat in the background, the interrupt field becomes abnormally large (but this
does not indicate a problem exists). In the last row in the example below, the interrupts (in) column has a value of 4294967216:
# procs memory page disk faults cpu r b w swap free re mf pi po fr de sr s6 s9 s1 -- in sy cs us sy id 0 0 0 437208 146424 0 1 4 0 0 0 0 0 1 0 0 50 65 79 0 1 99 0 0 0 413864 111056 0 0 0 0 0 0 0 0 0 0 0 198 137 214 0 3 97 0 0 0 413864 111056 0 0 0 0 0 0 0 0 0 0 0 286 101 200 0 3 97
0 0 0 413864 111072 0 110000001004294967216 43 6800100
Workaround: Restart vmstat.

POST System Board Status Displays Only 1 of the 2 Failing CPUs, Bug-ID 4200513

Category: Bug If two CPUs on a single board fail before reporting to the master CPU, the POST
system status display lists one CPU as failing, but the second CPU may not be listed at all.
Workaround: None.
64 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999

DR: Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory, Bug ID 4210234

Category: RFE Cannot unconfigure a CPU/Memory board that has interleaved memory. To unconfigure and subsequently disconnect a CPU board with memory or a
memory-only board, it is necessary to first unconfigure the memory. However, if the memory on the board is interleaved with memory on other boards, the memory cannot currently be unconfigured dynamically.
Memory interleaving can be displayed using the prtdiag or the cfgadm commands.
Workaround: Shut down the system before servicing the board, then reboot afterward. To permit future DR operations on the CPU/memory board, set the NVRAM memory-interleave property to min. See also “Memory Interleaving Set Incorrectly After a Fatal Reset, Bug-ID 4156075” on page 63 for a related discussion on interleaved memory.

DR: Cannot Unconfigure a CPU/Memory Board That Has Permanent Memory, Bug ID 4210280

Category: RFE To unconfigure and subsequently disconnect a CPU board with memory or a
memory-only board, it is necessary to first unconfigure the memory. However, some memory is not currently relocatable. This memory is considered permanent.
Permanent memory on a board is marked “permanent” in the cfgadm status display:
# cfgadm -s cols=ap_id:type:info Ap_Id Type Information ac0:bank0 memory slot3 64Mb base 0x0 permanent ac0:bank1 memory slot3 empty ac1:bank0 memory slot5 empty ac1:bank1 memory slot5 64Mb base 0x40000000
In this example, the board in slot3 has permanent memory and so cannot be removed.
Workaround: Shut down the system before servicing the board, then reboot afterward.
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 65

cfgadm Disconnect Fails When Running Concurrent cfgadm Commands, Bug-ID 4220105

Category: Bug If a cfgadm process is running on one board, an attempt to simultaneously
disconnect a second board fails. A cfgadm disconnect operation fails if another cfgadm process is already running
on a different board. The message is:
cfgadm: Hardware specific failure: disconnect failed: nexus error during detach: address
Workaround: Do only one cfgadm operation at a time. If a cfgadm operation is running on one board, wait for it to finish before you start a cfgadm disconnect operation on a second board.

Fatal Reset on init 5 After DR Operations, Bug-ID 4220852

Category: Bug After DR operations have been run, an attempt to power down a system with the
init 5 command may cause a fatal reset. Workaround: Reset the system, then power it off by entering the command
power-off at the ok prompt.

Cannot Drain And/or Detach Sun Enterprise Server Boards That Host QFE Cards, Bug-ID 4231845

When a server is configured as a boot server for Solaris 2.5.1-based x86 clients, it has several rpld jobs running, whether or not such devices are in use. These active references prevent DR operations from detaching these devices.
Workaround: To perform a DR detach operation:
1. Remove or rename the /rplboot directory.
2. Shut down NFS services with this command:
# sh /etc/init.d/nfs.server stop
66 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
3. Perform the DR detach operation.
4. Restart NFS services with this command:
# sh /etc/init.d/nfs.server start
Chapter 5 Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Open Issues 67
68 Solaris 7 5/99 Release Notes Supplement for Sun Hardware • May 1999
Loading...