Installation guide
Upgrading a Solaris Trusted Extensions System That is
Congured with Labeled Zones
Solaris systems that are congured with Solaris Trusted Extensions use non-global zones.
Upgrading these systems is the same as upgrading a Solaris system that uses zones, and has the
same issues.
■
ZFS Zones– Solaris systems with ZFS zones cannot currently be upgraded. For Solaris
Trusted Extensions systems with ZFS zones, the alternative is to recreate the zones. To
recreate the zones, perform these steps:
1. First, back up all the data using the tar -T command.
2. Then delete the zones.
3. Upgrade the system and recongure all the zones.
4. After all the zones are congured, restore all the data.
■
NFSv4 domain– After upgrade, when you bring up each labeled zone, you will be prompted
for the NFSv4 domain. To avoid this prompt, before upgrade add the correct
NFSMAPID_DOMAIN value in the /etc/default/nfs le in each labeled zone. For more
information, see CR 5110062.
■
Live Upgrade– The following bug aects Live Upgrade of Solaris systems with zones:
■
“lucreate and lumake Commands Fail to Create a Copy of a Non-Global Zone Which Is
Not in Running State (6659451)” on page 46
These bugs will also aect the Live Upgrade of systems that are congured with Solaris
Trusted Extensions. The workarounds are also the same.
■
Name Service– If your system was congured at install time to use a name service that is
dierent from the name service being used during upgrade, then the global zone may use the
correct name service after boot.
For example, if you specied NIS as the name service to use during system install, but the
system was later converted to be an LDAP client, the luactivate boot can revert to using
NIS as the name service for the global zone. This is due to CR 6569407.
The workaround is to adjust the name_service.xml symbolic link in the /var/svc/profile
directory to point to the correct xml le corresponding to the name service currently in use.
For example, if NIS was specied as the name service during install, then name_service.xml
will be a symbolic link to ns_nis.xml. If the system was subsequently converted to being an
LDAP client, and LDAP was the name service in use during Live Upgrade, then run the
following command:
# ln -fs ns_ldap.xml name_service.xml
This should be done before starting Live Upgrade or before running the lucreate
command. However, if you did not run this command before lucreate, then perform the
following steps after running the luactivate command:
BeforeYou Begin
Chapter 1 • Installation Issues 21