Patching with Solaris Live Upgrade

In my many travels to customers, I get asked about patching Solaris. One of the most common uses of Solaris Live Upgrade is to minimize downtime for patching. Upgrading to a newer Solaris release is a relatively infrequent activity in comparison to patching a system. Depending on the length of the maintenance window and the need to minimize downtime, patching an alternate boot environment may be an advantageous operations choice.



  • Create a new boot environment if you haven't already.

  • Patch the new boot environment

  • Boot from the new boot environment

  • Check your results for the changes and see if they are acceptable 


What a concept ! Patching a offline copy of a Operating System who would of thought! It's that easy!


Having a Alternate Boot Environment (ABE) to live upgrade or patch makes perfect sense. Don't you think?  With Solaris Live Upgrade you can take advantage of applying the patches in the background with little impact on what is running on the system. Therefore, who cares how long it takes!  The only downtime you have is to reboot!! 


As part of this exercise I wanted to test patching a ABE running Solaris 10 8/07, with Solaris Volume Manager (SVM), and Solaris Zones deployed, using the live upgrade feature in Solaris.


Note: In this case I already had a (ABE) from my previous blog entry Live Upgrade with Solaris Volume Manager (SVM) and Zones.


System Type Used in Test



  • SunFire 220R

  • 2/ 450MHZ USII Processors with 4mb of cache

  • 2048mb of memory

  • 2/ internal 18gb SCSI drive

  • Sun StorEdge D1000


Live Upgrade Commands Used or referenced in this exercise


lucreate(1M) – create a new boot environment
lustatus(1M)
– display status of boot environments
luupgrade(1M) – installs, upgrades, and performs other functions on software on a boot environment
luactivate(1M) – activate a boot environment
ludelete(1M) – delete a boot environment
lufslist(1M) – list configuration of a boot environment


Some notes on patching using the Live Upgrade method


Solaris Live Upgrade is not just limited to OS upgrades. In fact it can be used to manage downtime and risk when patching a system as well.


Because you are applying the patches to the inactive boot environment, patching has only minimal impact on the currently running environment. The production applications can continue to run as the patches get applied to the inactive environment. System Administrators can now avoid taking the system down to single-user mode, which is the standard practice for applying the Recommended Patch Clusters.


You can boot the newly patched environment, test your applications, and if you are not satisfied. Well! Just reboot to the original environment. With Solaris 10 8/07, patching Solaris Containers with Solaris Live Upgrade is very much supported. This can have a dramatic impact on decreasing downtime during patching.


Live Upgrade prerequisites when preparing to patch your systems.



  • I'm starting with a Solaris 10 8/07 release system, which was created by using Live Upgrade to create this ABE. See my previous blog on Live Upgrade with Solaris Volume Manager (SVM)  and Zones

  • Remember the required patches from the formerly Sun Infodoc 72099, now Sun InfoDoc 206844.
    This document provides information about the minimum patch requirements for a system on which Solaris Live Upgrade software will be used.

  • Asmention in my previous post,it is imperative that you ensure the target system meets these patch requirements before attempting to use Solaris Live Upgrade software on your system




Now you are ready to apply the Recommended Patch Cluster to the system.


Obtain the patches:


Access the Recommended Patch Cluster for Solaris 10 from sun.com/sunsolve.


This step typically involves downloading the file10_Recommended.zip (or 10_x86_Recommended.zip). For this example, assume you have downloaded it to /var/tmp. Then use the unzip command to uncompress the downloaded file to create the directory 10_Recommended containing all the patches.


The file 10_Recommended/CLUSTER_README will tell you to take the system to single user mode, and then use the install_cluster script. In this case, since I'm patching the inactive boot environment, I do not have to take the system to single user mode.  I also will be using a slightly different procedure to apply the patches. 


Note: You will not be using the install_cluster script.


Steps:


1). Verify the ABE your about to patch is not inactive, If not boot to the PBE before patching!! In this case the s10u3 is my PBE and the s10u4 is my ABE. I also shown below I ran a zoneadm list -cv to verify that my Solaris container/zone was running.


root@sunrise1 # lufslist s10u3
boot environment name: s10u3
This boot environment is currently active.

Filesystem fstype device size Mounted on Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/md/dsk/d0 ufs 13811814400 / logging
/dev/md/dsk/d1 swap 4255727616 - -
/dev/dsk/c1t9d0s4 ufs 36415636992 /zones logging
/dev/dsk/c1t2d0s0 ufs 36415636992 /solaris-stuff logging

root@sunrise1 # lufslist s10u4
boot environment name: s10u4
This boot environment will be active on next system boot.

Filesystem fstype device size Mounted on Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/md/dsk/d100 ufs 13811814400 / logging
/dev/md/dsk/d101 swap 4255727616 - -
/dev/dsk/c1t4d0s0 ufs 4289863680 /zones logging

root@sunrise1 # zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 zoneA running /zones/zoneA native shared


2). Make sure you are in the patch directory: 


root@sunrise1 # cd /var/tmp/10_Recommended

3). Patch the ABE or Inactive Boot Environment:


root@sunrise1 # luupgrade -n  s10u4 -s /var/tmp/10_Recommended -t 
`cat patch_order`

Validating the contents of the media </var/tmp/10_Recommended>.
The media contains 79 software patches that can be added.
Mounting the BE <s10u4>.
Adding patches to the BE <s10u4>.
Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Version of package SUNWcakr from directory SUNWcakr.v in patch 118918-24 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 118918-24 differs from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.us in patch 118918-24 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.v in patch 118833-36 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.v in patch 118833-36 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 118833-36 differs from the package installed on the system.
Version of package SUNWdrr from directory SUNWdrr.us in patch 118833-36 differs from the package installed on the system.
Version of package SUNWefc from directory SUNWefc.us in patch 118833-36 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.us in patch 118833-36 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcpc from directory SUNWcpc.v in patch 120011-14 differs from the package installed on the system.
Architecture for package SUNWiopc from directory SUNWiopc.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcpc from directory SUNWcpc.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWdrr from directory SUNWdrr.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWefc from directory SUNWefc.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWmcon from directory SUNWmcon in patch 121211-02 differs from the package installed on the system.
Version of package SUNWmcos from directory SUNWmcos in patch 121211-02 differs from the package installed on the system.
Version of package SUNWmcosx from directory SUNWmcosx in patch 121211-02 differs from the package installed on the system.
Version of package SUNWmctag from directory SUNWmctag in patch 121211-02 differs from the package installed on the system.
Done!

The following requested patches have packages not installed on the system
Package SUNWgzipS from directory SUNWgzipS in patch 120719-02 is not installed on the system. Changes for package SUNWgzipS
will not be applied to the system.
Package SUNWbzipS from directory SUNWbzipS in patch 126868-01 is not installed on the system. Changes for package SUNWbzipS
will not be applied to the system.
Package SUNWpmr from directory SUNWpmr in patch 119042-10 is not installed on the system. Changes for package SUNWpmr
will not be applied to the system.
Package FJSVdrdr from directory FJSVdrdr.us in patch 119042-10 is not installed on the system. Changes for package FJSVdrdr
will not be applied to the system.
Package SUNWcart200 from directory SUNWcart200.v in patch 118833-36 is not installed on the system. Changes for package SUNWcart200
will not be applied to the system.
Package SUNWkvmt200 from directory SUNWkvmt200.v in patch 118833-36 is not installed on the system. Changes for package SUNWkvmt200
will not be applied to the system.
Package SUNWust1 from directory SUNWust1.v in patch 118833-36 is not installed on the system. Changes for package SUNWust1
will not be applied to the system.
Package SUNWsmaS from directory SUNWsmaS in patch 120272-13 is not installed on the system. Changes for package SUNWsmaS
will not be applied to the system.
Package SUNWcart200 from directory SUNWcart200.v in patch 120011-14 is not installed on the system. Changes for package SUNWcart200
will not be applied to the system.
Package SUNWkvmt200 from directory SUNWkvmt200.v in patch 120011-14 is not installed on the system. Changes for package SUNWkvmt200
will not be applied to the system.
Package SUNWldomr from directory SUNWldomr.v in patch 120011-14 is not installed on the system. Changes for package SUNWldomr
will not be applied to the system.
Package SUNWldomu from directory SUNWldomu.v in patch 120011-14 is not installed on the system. Changes for package SUNWldomu
will not be applied to the system.
Package SUNWpmu from directory SUNWpmu in patch 120011-14 is not installed on the system. Changes for package SUNWpmu
will not be applied to the system.
Package SUNWust1 from directory SUNWust1.v in patch 120011-14 is not installed on the system. Changes for package SUNWust1
will not be applied to the system.
Package SUNWsmbaS from directory SUNWsmbaS in patch 119757-09 is not installed on the system. Changes for package SUNWsmbaS
will not be applied to the system.
Package SUNWapch2S from directory SUNWapch2S in patch 120543-09 is not installed on the system. Changes for package SUNWapch2S
will not be applied to the system.
Package SUNWmysqlS from directory SUNWmysqlS in patch 120292-01 is not installed on the system. Changes for package SUNWmysqlS
will not be applied to the system.
Package SUNWipged from directory SUNWipged in patch 120849-04 is not installed on the system. Changes for package SUNWipged
will not be applied to the system.

The following requested patches are already installed on the system
Requested to install patch 120719-02 is already installed on the system.
Requested to install patch 121296-01 is already installed on the system.
Requested to install patch 118872-04 is already installed on the system.
Requested to install patch 120900-04 is already installed on the system.
Requested to install patch 121133-02 is already installed on the system.
Requested to install patch 119042-10 is already installed on the system.
Requested to install patch 126538-01 is already installed on the system.
Requested to install patch 118918-24 is already installed on the system.
Requested to install patch 119574-02 is already installed on the system.
Requested to install patch 119578-30 is already installed on the system.
Requested to install patch 126419-01 is already installed on the system.
Requested to install patch 126897-02 is already installed on the system.
Requested to install patch 118833-36 is already installed on the system.
Requested to install patch 122640-05 is already installed on the system.
Requested to install patch 125547-02 is already installed on the system.
Requested to install patch 125503-02 is already installed on the system.
Requested to install patch 120011-14 is already installed on the system.
Requested to install patch 120543-09 is already installed on the system.
Requested to install patch 119317-01 is already installed on the system.
Requested to install patch 120292-01 is already installed on the system.
Requested to install patch 120329-02 is already installed on the system.
Requested to install patch 124188-02 is already installed on the system.
Requested to install patch 121012-02 is already installed on the system.
Requested to install patch 118959-03 is already installed on the system.
Requested to install patch 124997-01 is already installed on the system.
Requested to install patch 119903-02 is already installed on the system.
Requested to install patch 121004-03 is already installed on the system.
Requested to install patch 120061-02 is already installed on the system.
Requested to install patch 118560-02 is already installed on the system.
Requested to install patch 121002-03 is already installed on the system.
Requested to install patch 124457-01 is already installed on the system.
Requested to install patch 123186-02 is already installed on the system.

The following requested patches do not update any packages installed on the system
Packages from patch 121211-02 are not installed on the system.

Checking patches that you specified for installation.

Done!

The following requested patches will not be installed because
they have been made obsolete by other patches already
installed on the system or by patches you have specified for installation.

0 All packages from patch 118731-01 are patched by higher revision patches.

1 All packages from patch 122660-10 are patched by higher revision patches.

2 All packages from patch 124204-04 are patched by higher revision patches.

The following requested patches will not be installed because
the packages they patch are not installed on this system.

0 Packages from patch 120849-04 are not installed on the system.

Approved patches will be installed in this order:

126868-01 118815-06 119254-45 120272-13 125369-12 119757-09

Preparing checklist for non-global zone check...

Checking non-global zones...

The following requested patches rejected on non-global zone.
Entire installation is possible but those patches
will not be installed on non-global zone.

Packages from patch 120849-04 are not installed on the system.

SUNWlu-zoneA: Packages from patch 120849-04 are not installed on the system.

This patch passes the non-global zone check.
126868-01 118815-06 119254-45 120272-13 125369-12 119757-09

Summary for zones:

Zone zoneA

Rejected patches:
120849-04
Patches that passed the dependency check:
126868-01 118815-06 119254-45 120272-13 125369-12 119757-09

Patching global zone
Adding patches...

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 126868-01 has been successfully installed.
See /a/var/sadm/patch/126868-01/log for details

Patch packages installed:
SUNWbzip

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 118815-06 has been successfully installed.
See /a/var/sadm/patch/118815-06/log for details

Patch packages installed:
SUNWesu
SUNWxcu4

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 119254-45 has been successfully installed.
See /a/var/sadm/patch/119254-45/log for details
Executing postpatch script...

Patch packages installed:
SUNWinstall-patch-utils-root
SUNWpkgcmdsu
SUNWswmt

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 120272-13 has been successfully installed.
See /a/var/sadm/patch/120272-13/log for details
Executing postpatch script...

Patch packages installed:
SUNWbzip
SUNWsmagt
SUNWsmcmd
SUNWsmmgr

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 125369-12 has been successfully installed.
See /a/var/sadm/patch/125369-12/log for details

Patch packages installed:
FJSVfmd
SUNWcsr
SUNWfmd
SUNWhea
SUNWmdb

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 119757-09 has been successfully installed.
See /a/var/sadm/patch/119757-09/log for details

Patch packages installed:
SUNWsmbac
SUNWsmbar
SUNWsmbau

Done!
Patching non-global zones...

Patching zone zoneA
Adding patches...

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 126868-01 has been successfully installed.
See /a/var/sadm/patch/126868-01/log for details

Patch packages installed:
SUNWbzip

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 118815-06 has been successfully installed.
See /a/var/sadm/patch/118815-06/log for details

Patch packages installed:
SUNWesu
SUNWxcu4

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 119254-45 has been successfully installed.
See /a/var/sadm/patch/119254-45/log for details
Executing postpatch script...

Patch packages installed:
SUNWinstall-patch-utils-root
SUNWpkgcmdsu
SUNWswmt

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Pkgadd failed. See /var/tmp/120272-13.log.23488 for details

Removing partially installed patch
Validating patches...

Loading patches installed on the system...

Done!
Patch patchaddInterrupt does not exist.

Checking patches that you specified for removal.

Done!

Approved patches will be removed in this order:

120272-13

Checking installed patches...

Backing out patch 120272-13...

Patch 120272-13 has been backed out.

Skipping patch 120272-13
Installation of patch number 120272-13 has been suspended.
ln: cannot create link SUNWbzip/pkginfo_mvd_23488: Read-only file system
mv: SUNWbzip/pkginfo: override protection 755 (yes/no)? yes
mv: cannot unlink SUNWbzip/pkginfo: Read-only file system
chmod: WARNING: can't change SUNWbzip/pkginfo
ln: cannot create link SUNWsmagt/pkginfo_mvd_23488: Read-only file system
mv: SUNWsmagt/pkginfo: override protection 755 (yes/no)? yes
mv: cannot unlink SUNWsmagt/pkginfo: Read-only file system
chmod: WARNING: can't change SUNWsmagt/pkginfo
ln: cannot create link SUNWsmcmd/pkginfo_mvd_23488: Read-only file system
mv: SUNWsmcmd/pkginfo: override protection 755 (yes/no)? yes
mv: cannot unlink SUNWsmcmd/pkginfo: Read-only file system
chmod: WARNING: can't change SUNWsmcmd/pkginfo
Executing postpatch script...

Patch packages installed:

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 125369-12 has been successfully installed.
See /a/var/sadm/patch/125369-12/log for details

Patch packages installed:
FJSVfmd
SUNWcsr
SUNWfmd
SUNWhea
SUNWmdb

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch 119757-09 has been successfully installed.
See /a/var/sadm/patch/119757-09/log for details

Patch packages installed:
SUNWsmbac
SUNWsmbar
SUNWsmbau

Done!
Unmounting the BE <⁞s10u4>.
The patch add to the BE <s10u4> completed.


In the above command line example, you'll identify which boot environment to patch,"s10u4", where the patches are located (the -s option and path argument), and patches to apply (the -t option followed by the patch ⁞numbers).


Note:  The argument to the -t option is placed in backquotes meaning the expression will be evaluated by the shell before sending the results (the list of patches) to the luupgrade(1M) command.


Indicate which boot environment is to be used the next time you reboot in this exercise, it's "s10u4".


root@sunrise1 # luactivate s10u4
WARNING: Boot environment <s10u4> is already activated.

Where s10u4 is the boot environment you want to make active. As you can see from the above output the s10u4 is already activated. The reason for this, is that when I created it, as shown in my previous blog entry Live Upgrade with Solaris Volume manager (SVM) and Zones I activated the ABE at that time. Otherwise I would have received the output similar to this.



The output of the luactivate(1M) command will look like the following:


\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
The target boot environment has been activated. It will be used when you reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands.
You MUST USE either the init or the shutdown command when you reboot. If you do not use either init or shutdown, the system will not boot
using the target BE.
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
In case of a failure while booting to the target BE, the following process needs to be followed to fallback to the currently working boot
environment:
1. Enter the PROM monitor (ok prompt).
2. Boot the machine to Single User mode using a different boot device (like the Solaris Install CD or Network). Examples:
At the PROM monitor (ok prompt): For boot to Solaris CD: boot cdrom -s For boot to network: boot net -s
3. Mount the Current boot environment root slice to some directory (like /mnt). You can use the following command to mount:
mount -Fufs /dev/dsk/c0t1d0s2 /mnt
4. Run <luactivate> utility with out any arguments from the current boot


Note the warning in the above about the proper command to use to reboot. You must use "init" or "shutdown".


Since the newly patched ABE was already activated, I can now boot the ABE s10u4. Since this is SPARC system, and I have not made a entry in the eeprom or nvaliased the path to the new ABE I will boot the newly patch ABE as follows.


ok boot /pci@1f,4000/scsi@3/disk@1,0:a

Resetting ...

Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz), No Keyboard
OpenBoot 3.23, 2048 MB memory installed, Serial #14809682.
Ethernet address 8:0:20:e1:fa:52, Host ID: 80e1fa52.

Rebooting with command: boot /pci@1f,4000/scsi@3/disk@0,0:a
Boot device: /pci@1f,4000/scsi@3/disk@0,0:a File and args:
SunOS Release 5.10 Version Generic_127111-06 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
TSI: gfxp0 is GFX8P @ 1152x900
Hostname: sunrise1
checking ufs filesystems
/dev/rdsk/c1t2d0s0: is logging.
/dev/rdsk/c1t9d0s4: is logging.

sunrise1 console login:


Login into ABE and check the zone


root@sunrise1 # zoneadm list -cv
  ID NAME             STATUS     PATH                           BRAND    IP   
   0 global           running    /                              native   shared
   2 zoneA            running    /zones/zoneA                   native   shared

root@sunrise1 # zlogin -C zoneA
[Connected to zone 'zoneA' console]

# df -h
Filesystem size used avail capacity Mounted on
/ 33G 720M 32G 3% /
/dev 33G 720M 32G 3% /dev
/lib 13G 5.8G 6.7G 47% /lib
/platform 13G 5.8G 6.7G 47% /platform
/sbin 13G 5.8G 6.7G 47% /sbin
/usr 13G 5.8G 6.7G 47% /usr
proc 0K 0K 0K 0% /proc
ctfs 0K 0K 0K 0% /system/contract
mnttab 0K 0K 0K 0% /etc/mnttab
objfs 0K 0K 0K 0% /system/object
swap 4.6G 304K 4.6G 1% /etc/svc/volatile
fd 0K 0K 0K 0% /dev/fd
swap 4.6G 32K 4.6G 1% /tmp
swap 4.6G 40K 4.6G 1% /var/run
# uname -a
SunOS zoneA 5.10 Generic_127111-06 sun4u sparc SUNW,Ultra-60


Some things to remember!! 



On a running system, some files might change during or after the lucreate/luupgrade process. You might want those changes reflected in the new boot environment in order to synchronize the two systems. To address this, there is a synchronization mechanism that the luactivate command will automatically call. See the synclist(4) man page for more
information.


The luactivate can also be used to revert to the previous boot environment. In most cases this is very straightforward, but due to the adoption on x86 platforms of GRUB (the new boot loader for Solaris 10 1/06 and subsequent Solaris releases) there are some issues when reverting from a GRUB system to a pre-GRUB release. These are all explained in the Solaris Live Upgrade documentation referenced here.

You have now succeeded in using Live Upgrade to patch a Solaris 10 8/07 release.


Note that the reboot is the only downtime experienced using this upgrade method a very different situation than if you had done a standard install or standard upgrade.


One last and final note make sure that you dispose of a boot environment properly when you are finished with it. The proper way is to use the ludelete(1M) command. If you destroy the boot environment through some other mechanism (e.g. newfs, or rm -rf) you risk having a system that will not boot. 


Behind the scenes Solaris Live Upgrade is simply using the patchadd command. You could accomplish the same patching of the inactive boot environment by mounting it and using patchadd(1M) with the -R option. If you want to understand the behavior of patching using Solaris Live Upgrade, familiarize yourself with the patchadd(1M) command.


The Solaris 10 patchadd(1M) command is smart enough to order patches correctly, but Solaris 9 and earlier releases require patches to be in dependency order. Sun uses a command line similar to the above as part of the standard testing, so it makes sense to use a similar approach when you use Solaris Live Upgrade to patch - no matter what Solaris release you are patching


Until next time!!  Have fun with Solaris Live Upgrade!!

Comments:

We also are migrating towards patching with Live Upgrade.
Unfortunately, we have been using Sun's official patch tool, smpatch.
There's no way to use this with an ABE, no way to analyze the system
on the ABE and apply only the required
patches. The patch bundles will work, but it's a step backwards to start using
them. Analysis was the best feature of
smpatch, and it's gone now!

Posted by Gary Mills on April 25, 2008 at 01:23 PM EDT #

The real challenge is when the zone is on a SVM diskset or VxVM diskgroup, lucreate command will fail.

Posted by anonymous on April 27, 2008 at 08:43 AM EDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

mhuff

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today