Beruflich Dokumente
Kultur Dokumente
Customer:
Sales Order Number:
CASE Number:
Technician:
Version EIS-DVD:
Date:
This checklist describes the use of the Solaris 11 Text Installer and assumes that this
is available on a DVD (eg from the Solaris 11 media kit).
Oracle Internal and Approved Partners Only Page 1 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
PREPARATION
Ensure that the Release Notes for the Solaris version used have been read and
understood. The Oracle Solaris 11.1 documentation is available here:
http://docs.oracle.com/cd/E26502_01/
View the appropriate Server checklist for the Platform Minimum Solaris
Requirements and any additional patch requirements. Although the
documentation states that the minimum main memory requirement is 1Gb,
unofficial advice is to have at least 2Gb main memory.
Solaris 11.1 content can be obtained here1:
http://www.oracle.com/technetwork/server-storage/solaris11/downloads/
Or from the Oracle Software Delivery Cloud (formerly E-Delivery):
http://edelivery.oracle.com/
Select a Product pack: Oracle Solaris
Platform: Oracle Solaris on SPARC (64-bit) also valid for X86.
Then Oracle Solaris 11.1 Media Pack.
It is required that each system at the customer site has access to the 'release
repo' (repository) during system administration activities (updates etc.).
The choices are:
Connection via the Internet to http://pkg.oracle.com/solaris/release. This
works both for Solaris 11 11/11 and Solaris 11.1.
The customer downloads the specific release repo ISO image themselves
and performs whatever verification they have to do. They will need
some machine connected to the Internet and then the associated processes
to transfer the data into their 'dark sites'. The release repo ISO image can
be shared via the customer's local network. The procedure on how to
create and share a local Solaris 11 package repository is described in
document Copying and Creating Oracle Solaris 11.1 Package
Repositories
Oracle/partner staff obtain the release repo ISO image & the customer
trusts the image that they bring onto site on whatever media is required.
The repo ISO image can be shared via the customer's local network.
The size of the repository is approximately 7 Gb & is common to the
SPARC & X86 platforms. If it will be stored on the local system its
suggested to place it under directory /export/home/ips-repo (the EIS
scripts place the SRU here as well).
Note they should really only need to get the 'release repo' (repository) once
for each release because of the incremental additions the SRU ISO image
delivers.
Alternatively if the customer has valid support contract for the system and
the system has connectivity to the Internet the system can access the Oracle
Solaris 11 Support repository (as described on page 7).
1 OTN & the Oracle Software Delivery Cloud only offer Solaris 11.1. All releases of Solaris can be
found on MOS under Patches and Updates enter Solaris Operating System in the Product
field and select Oracle Solaris 11 Operating System from the Release field.
Oracle Internal and Approved Partners Only Page 2 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Oracle Internal and Approved Partners Only Page 3 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Oracle Internal and Approved Partners Only Page 4 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
In the Users Panel set the system root
password.
You will then be invited to create a user If you create this user account, root will be
account. The name must begin with a a role assigned to the user.
letter and can contain only letters and If no user account is created, root will be a
numbers. regular user.
The Installation Complete screen Select reboot (do not panic when the
appears. Welcome Screen briefly reappears).
Oracle Internal and Approved Partners Only Page 5 of 18 Vn 1.4 Created: 10. Jan. 2013
INFORMATION
ORACLE SOLARIS 11 REPOSITORIES
In order to be able to update the Solaris 11 OS you require access to:
The Solaris 11 Release Repository (release repo) for Solaris 11 11/11 or 11.1
depending on the OS that is installed AND
The Solaris 11 11/11 or 11.1 Support Repository Update (SRU).
This may be achieved in several ways:
1. If the customer has a valid support contract for the system being installed
(unlikely for a newly-delivered system) and the system has connectivity to the
Internet then the system can be configured to use the Oracle Solaris 11 Support
Repository. Refer to page 7.
2. If the new system has access to the Internet you can leave the default
configuration for the release repo and copy the current incremental SRU from
the EIS-DVD onto the local system. Refer to page 7.
3. If the customer has a copy of the release repo available either on the local
system or on his local network you can point the publisher to this and copy the
current incremental SRU from the EIS-DVD onto the local system suitable for
Secure Sites. Refer to page 8.
4. A variant on (3) is that the customer (with a Support Contract) also has the latest
SRU available on his local network possibly even integrated into his own
support repository. There are many possible variations to this scheme.
The first three possibilities are described on the following pages.
Factory Installation:
We understand that a system that has been pre-installed with Solaris 11 will have the
publisher set thus:
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release
solaris mirror online http://pkg-cdn1.oracle.com/solaris/release/
Fresh Installation:
By default the system is set to connect to the release repository made available by
Oracle on the Internet to customers:
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release
When the publishers are configured on a system there is a 'short hand' option (-p)
that allows for the publisher on the system to be configured based upon the actual
publisher's configuration (in terms of mirrors):
# pkg set-publisher -p http://pkg.oracle.com/solaris/release
Oracle Internal and Approved Partners Only Page 6 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
METHOD #1 Accessing the Oracle Solaris 11 Support Repository
This method is available if the customer has valid support contract for the
system and the system has connectivity to the Internet thus replacing the
system's use of the release/ stream from pkg.oracle.com. The
actions here are taken from https://pkg-register.oracle.com/help/
Go to http://pkg-register.oracle.com Valid Customer MOS Account required!
Oracle Internal and Approved Partners Only Page 7 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
METHOD #3 Using a local Solaris 11 Release Repository (No Internet)
Assuming connectivity to the Internet is not available:
On page 2 it is suggested how to obtain the 'Release Repo'. It is suggested to
mount the ISO file under /repo thus:
# mkdir /repo
# mount -F hsfs <full-path-to-repo> /repo
Consider adding an entry to /etc/vfstab so that the mount survives a reboot.
The /etc/vfstab entry would be something like:
<full-path-to-repo> - /repo hsfs - yes -
Remove the default mirror publisher for Solaris (if present):
# pkg set-publisher -M '*' solaris
Set the publisher to use the local 'release repo' repository in place of original:
# pkg set-publisher -G '*' -g file:///repo/repo solaris
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online file:///repo/repo/
Note that it is possible that the customer already has a local copy of the
release repository within the local network. If this is the case modify the
above steps accordingly.
Accessing the Incremental SRU
Now you need to add access to the current incremental SRU from the EIS-
DVD. A script2 is provided to unpack the SRU from the EIS-DVD, placing
the contents in directory /export/home/ips-repo/SRU. Ensure that EITHER
this directory does not exist or that it is empty.
The script provided on the EIS-DVD to unpack the SRU makes temporary
use of the mount point /mnt (for loopback). Ensure that /mnt is not in use.
Example showing that /mnt is in use (output abbreviated):
# mount | grep "/mnt on"
/mnt on /dev/lofi/1 read only/setuid/devices/rstchown/noglobal/..
The publisher is now pointing to the incremental SRU and the full repo.
Oracle Internal and Approved Partners Only Page 8 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
You can now install SunVTS from the # pkg install system/test/sunvts
repository:
Updating the System from the SRU
After the initial boot the system will have a single Boot Environment (BE)
called solaris:
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris NR / 2.88G static 2011-11-02 17:23
Run the command to update the system. # pkg update -v
Its suggested to run with the -v
(verbose) option:
NOTE: You may wish to give the new BE a specific name that shows with
SRU has been applied such as: sXXsruYY where XX reflects the Solaris
version and YY is the SRU number.
Example for Solaris 11 & SRU10: s11sru10
This means adding the --be-name option to the pkg update command:
# pkg update -v --be-name s11sru10
The examples below will change accordingly.
When the Update has Completed...
In most cases a new BE will have been created (here solaris-1). The R
(under Active) indicates that after the reboot that solaris-1 will be active.
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris N / 1.43M static 2011-11-02 17:23
solaris-1 R - 3.08G static 2011-11-25 18:37
Reboot the system into the new BE. # init 6
Then log in as user root or as the created
user & change to root: su - root
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris - - 9.71M static 2011-11-02 17:23
solaris-1 NR / 3.14G static 2011-11-25 18:37
Now you can see that BE solaris-1 is both currently active & will be after a
reboot.
If at some future point-in-time you wish to delete a BE that is no longer used:
# beadm destroy -Ff <name-of-BE-to-be-deleted>
Oracle Internal and Approved Partners Only Page 9 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
If you wish to go back to the previous BE (here solaris) then:
# beadm activate solaris
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris R - 2.84G static 2011-11-02 17:23
solaris-1 N / 198.63M static 2011-11-25 18:37
After the reboot solaris will be active.
Oracle Internal and Approved Partners Only Page 10 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Examine SunVTS log files under If errors occurred, investigate, correct &
/var/sunvts/logs. re-run to ensure a "clean" system.
Oracle Internal and Approved Partners Only Page 11 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Oracle Internal and Approved Partners Only Page 12 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
SYSTEM CONFIGURATION
Verify that required settings in See appropriate EIS storage installation
/etc/system have been made if external checklists.
mass storage has been attached.
Set up data volumes & filesystems The consultancy for data volumes (and their
setting up) is not part of ServerStart - belongs
according to customer requirements (if to additional services as sold by ACS.
purchased).
SPARC Server Specifics
Verify/set the OBP parameters for production:
auto-boot? = true
auto-boot-on-error? = true
Note that when using the eeprom command from Solaris 11 to set OBP
variables on SPARC/sun4v systems it appears to work, however the values
revert to their previous setting after a reset. see note on page 1.
Verify/set the NVRAM parameters for If NVRAM editor (nvedit) was used to
production: create boot aliases etc.
Oracle Internal and Approved Partners Only Page 13 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Finishing Off
Consider disabling remote ssh logins In /etc/ssh/sshd_config
(eg if enabled via setup-standard). See PermitRootLogin.
Reboot =>everything o.k?
Now return to the checklist from whence you came...
Oracle Internal and Approved Partners Only Page 14 of 18 Vn 1.4 Created: 10. Jan. 2013
INFORMATION
APPENDIX A UPDATE FROM SOLARIS 11 11/11 TO 11.1
A system running Solaris 11 11/11 at some stage the system has to be updated from
to Solaris 11.1 (possibly with SRUs for S11.1) in order that further SRUs for S11.1
can be applied in the future.
The actions described here are based on the article More Tips for Updating Your
Oracle Solaris 11 System from the Oracle Support Repository by Peter Dennis
(Solaris Engineering).
UPDATE PATHS
There are a number of pre-conditions to upgrading from Solaris 11/11 to 11.1:
Oracle Internal and Approved Partners Only Page 15 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Oracle Internal and Approved Partners Only Page 16 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Insert EIS-DVD-TWO then:
# cd /media/eisdvd/sun2/patch/11_1
# copy-sru2disk -extract -force -q
The force option is required so that you can unpack the SRU for Solaris 11.1
whilst the system is running Solaris 11 11/11 (the script has features to ensure
that you unpack the correct SRU). For this reason the current directory has to
be the one on the EIS-DVD where the SRU for Solaris 11.1 resides.
The current SRU will be unzipped into directory/export/home/ips-repo, the
resulting ISO file mounted via /mnt and the contents copied into directory
/export/home/ips-repo/SRU. The ISO file is then unmounted.
The copy-sru2disk command requires several minutes.
Now add the incremental SRU to the publisher:
# pkg set-publisher -g file:/export/home/ips-iso/SRU/repo solaris
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online file:///export/home/ips-iso/SRU/repo/
solaris origin online http://pkg.oracle.com/solaris/release/
The publisher is now pointing to the incremental SRU and the full repo.
Performing the Update
SPARC Platform Only (With Zones / Containers):
If you are running on a SPARC system and have any Oracle Solaris Zones
installed, you will need to perform this additional first step.
For each zone installed on the system, you will need to remove the
pkg:/system/ldoms/ldomsmanager package as follows:
# for z in `zoneadm list`; do zlogin $z pkg uninstall ldomsmanager; done
Update the rest of the system packages and reboot the system.
To update, we use the --accept flag to pkg update to agree to and accept
the terms of the licenses that are being updated. We also use the --be-name
flag to provide a new name to the boot environment that will be created (in
this example the new name is s11.1).
# pkg update --be-name s11.1 -accept
# reboot
Oracle Internal and Approved Partners Only Page 17 of 18 Vn 1.4 Created: 10. Jan. 2013
Task Comment Check
Update the rest of the system packages and reboot the system.
To update, we use the --accept flag to pkg update to agree to and accept
the terms of the licenses that are being updated. We also use the --be-name
flag to provide a new name to the boot environment that will be created (in
this example the new name is s11.1).
# pkg update --be-name s11.1 -accept
# reboot
Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that
you always check the web pages for the latest version.
Comments & RFEs are welcome. Oracle staff should mail to EIS-SUPPORT_WW@oracle.com .
Partners should mail to: SUPPORT-PARTNER-QUESTIONS_WW_GRP@oracle.com .
Oracle Internal and Approved Partners Only Page 18 of 18 Vn 1.4 Created: 10. Jan. 2013