Installation guide

Note The x for CR 6411084, the SUNWcsr install or postinstall script, creates the correct link
only if name_service.xml is not a link le. If name_service.xml is already a symbolic link le,
as in the Solaris 10 Hardware 2 release, the x for CR 6411084 will not work.
After an upgrade from Solaris 10 Hardware 2 to the current Solaris 10 10/09 release, the
following message is displayed on the console or logged in the messages le:
Oct 23 12:18:45 vt2000a automount[301]: [ID 366266 daemon.error]
can’t read nis map auto_master: can’t communicate with ypbind - retrying
Also, the /network/nis/client:default service is oine.
Workaround: Choose one of the following workarounds:
Workaround 1: Before an upgrade, remove the /var/svc/profile/name_service.xml le.
Workaround 2: After an upgrade, change the /var/svc/profile/name_service.xml link
to the correct ns_<xxx>.xml le, based on the name service.
Upgrade Fails on System With Zones That Have Been
Installed But Not Booted
A non-global zone that has been installed but never booted or made ready prevents a system
from being upgraded correctly. No error message is displayed.
Workaround:
If such a zone is found, the zone should be made ready and then halted prior to starting the
upgrade. For example:
global# zoneadm -z myzone ready ; zoneadm -z myzone halt
Upgrading a Solaris 10 System with Non-Global Zones
to the Solaris 10 10/09 Release Might Cause the Local
File System Service to Fail (6428258)
Upgrading a Solaris 10 3/05 system or a Solaris 10 1/06 system to the Solaris 10 10/09 release
with non-global zones might cause the SMF service that mounts local le systems to fail in the
non-global zones. As a result, other services in the non-global zones might fail to start.
After upgrading a Solaris 10 system with non-global zones to the Solaris 10 10/09 release,
services might be in the maintenance state. For example:
Upgrade Issues and Bugs
Chapter 1 • Installation Issues 49