Upgrade Solaris 11 Express to Solaris 11
Check Current Version
The important thing to notice here is snv_151a, which means that it is Solaris 11 Express.
# uname -a SunOS storage01 5.11 snv_151a i86pc i386 i86pc Solaris
# cat /etc/release Oracle Solaris 11 Express snv_151a X86 Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. Assembled 04 November 2010
Display the Current IPS Repositories
This will show you the repositories configured on your system.
# pkg publisher PUBLISHER TYPE STATUS URI solaris origin online http://pkg.oracle.com/solaris/release/
Configure the IPS Repository
If you don’t already have the repository configured you will need to configure it.
# pkg set-publisher -g http://pkg.oracle.com/solaris/release solaris
Update Packages
# pkg update WARNING: pkg(5) appears to be out of date, and should be updated before running update. Please update pkg(5) using 'pfexec pkg install pkg:/package/pkg' and then retry the update.
As it mentions we need to install the updated version of pkg to preceed with update installation.
# pkg install pkg Packages to update: 5 Create boot environment: Yes DOWNLOAD PKGS FILES XFER (MB) Completed 5/5 485/485 3.5/3.5 PHASE ACTIONS Removal Phase 1/58 Warning - directory /tmp/tmpw15nh0/usr/share/man/cat1m not empty or not expected during operation - contents preserved in /tmp/tmpw15nh0/var/pkg/lost+found/usr/share/man/cat1m-20120528T202140Z Removal Phase 58/58 Install Phase 199/199 Update Phase 465/465 PHASE ITEMS Package State Update Phase 10/10 Package Cache Update Phase 5/5 Image State Update Phase 2/2 A clone of solaris exists and has been updated and activated. On the next boot the Boot Environment solaris-1 will be mounted on '/'. Reboot when ready to switch to this updated BE.
Now we need to reboot into the new boot environment.
# reboot
Now lets run our updates.
# pkg update Packages to remove: 272 Packages to install: 207 Packages to update: 577 Create boot environment: Yes Create backup boot environment: No DOWNLOAD PKGS FILES XFER (MB) Completed 1056/1056 68642/68642 1042.2/1042.2 PHASE ACTIONS Removal Phase 29017/29017 Install Phase 72725/72725 Update Phase 72453/72453 PHASE ITEMS Package State Update Phase 1633/1633 Package Cache Update Phase 849/849 Image State Update Phase 2/2 A clone of solaris-1 exists and has been updated and activated. On the next boot the Boot Environment solaris-2 will be mounted on '/'. Reboot when ready to switch to this updated BE. The following unexpected or editable files and directories were salvaged while executing the requested package operation; they have been moved to the displayed location in the image: var/saf -> /tmp/tmpe27V3b/var/pkg/lost+found/var/saf-20120528T233642Z var/sadm/system/logs -> /tmp/tmpe27V3b/var/pkg/lost+found/var/sadm/system/logs-20120528T233642Z var/run -> /tmp/tmpe27V3b/var/pkg/lost+found/var/run-20120528T233642Z etc/saf/zsmon -> /tmp/tmpe27V3b/var/pkg/lost+found/etc/saf/zsmon-20120528T233642Z etc/saf -> /tmp/tmpe27V3b/var/pkg/lost+found/etc/saf-20120528T233642Z --------------------------------------------------------------------------- NOTE: Please review release notes posted at: http://www.oracle.com/pls/topic/lookup?ctx=E23824&id=SERNS ---------------------------------------------------------------------------
Another reboot to get into the new boot environment.
# reboot
Check Current Version
The “11.0″ is what we are looking for. You are now on the release version Solaris 11.
# uname -a SunOS storage01 5.11 11.0 i86pc i386 i86pc Solaris
# cat /etc/release Oracle Solaris 11 11/11 X86 Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Assembled 18 October 2011

Please keep in mind that this procedure is if you do not have the support repositories. If you have the support repositories you don’t need to use the release repository, just pkg update against the support repo. That said, you need to understand what will still be intact after your upgrade. For example alot of the samba configuration has changed so if your machine is previously joined to an Active Directory domain you will no longer be joined after the upgrade, that is a simple enough fix, networking also moved into svccfg, so I have run into situations (bonded vlans) which didn’t carry over properly and had to be torn down and built back up.
-matt