eis installation checklist for the solaris 10 os

EIS Installation Checklist for the Solaris 10 OS

Customer:

TASK Number:

Technician:

Version EIS-DVD:

Date:

This checklist is to be used in conjunction with the appropriate server checklist. It is assumed that the installation is carried out with the help of the current

EIS-DVD. The idea behind this checklist is to help the installer achieve a "good" installation. It is assumed that the installer has attended the appropriate training classes. The installation should be prepared using EISdoc V4. It is assumed in this checklist that Solaris 10 (Update 9 or later) is used some

platforms may require later updates. If you are intending to install the server via JET, refer also to the JET checklist. It is not intended that this checklist be handed over to the customer. Feedback is welcome refer to the last page of this checklist.

Task Check

PREPARATIONView the Server checklist for the Platform Minimum Solaris Requirements and any additional patch requirements.

INFORMATION: ACCESS TO EIS-DVD CONTENTSWhen applying EIS Methodology content from the EIS-DVD is required.If a DVD drive is local to a Solaris 10 system, the EIS-DVD will be automounted and the contents available under /cdrom/eisdvd. Note that there are two EIS-DVDs for each release; general content is on EIS-DVD-ONE, additional content is on EIS-DVD-TWO. Hence during the installation it may be necessary to switch between DVDs.For systems with no local DVD (and no USB port to which a DVD drive could be attached), it is suggested that for the duration of the installation work that you copy the contents for the EIS-DVD via copy-dvd2sun.sh onto an available server on the network, share the contents and access via /net/. The copy action takes about 40 minutes if using a local DVD drive. The contents of EIS-DVD-TWO should be added to this via add-dvd2sun.sh.

In this checklist examples of EIS-DVD locations are of the form .../sun/patch/xxx and should be preceded by the appropriate path.

Oracle Internal and Approved Partners Only Page 1 of 14 Vn 1.4a Created: 23. Jan. 2014

Task Comment Check

BOOTING SERVER FROM PRE-INSTALLED O/SStandard installations carried out by manufacturing are as follows: Solaris 11.1 will have been installed by default. ZFS Root Filesystem will be default. Exception to above two: M4000 M9000 servers have Solaris 10 Entire

Distribution + OEM on UFS (due to CR 6522017). The onboard RAID (if available for the server) will not be active. Software mirroring will not have been set up. The system will have been patched and configured according to EIS methodology Before leaving the factory, the system will have been sys-unconfig'd. If you have set up a RAID configuration for the boot disk the pre-installed image

will have been lost.Booting From a Pre-Installed Disk ImageInitial server bootup:Upon initial boot, the server will ask the typical Solaris post-install configuration questions.

Answer as appropriate.

During the boot sequence you may see the following on the console:WARNING: emlxs0: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm,fcadm, or emlxadm is required.)

In this case you will (later) need the actions described on page 6.If this is a Customer Ready System (CRS) prepared server, you can probably go straight to the Explorer/Analysis section in the appropriate server checklist.

Once Solaris has booted up, log in and gain access to an EIS-DVD image.

Run setup-standard as user root:cd /sun/installsh setup-standard.sh

If this is a CRS-prepared system, take care not to change settings that customer specified!

Install following patches: Solaris patches Sun, Cacao 2.1 & SWUP

cd /cdrom/.../sunpatch-EIS /var/tmp

Reboot the server.You can now go straight to the Mass-Storage section on page 8.


Task Comment Check

SOLARIS-INSTALLATIONDecide whether to use ZFS or UFS for the boot disk. Refer to EIS Standard: Boot Disk Layout and your EIS Installation Configuration Plan (EISdoc V4).Specific to M8000 & M9000 Servers:Due to CR6522017, it is not recommended to use ZFS for the root file system on M8000 M9000 because it will prevent the use of DR for system boards.Specific to SPARC T3 & T4 Servers with Solaris 10 08/11 Update 10: Installing on Hardware RAID 1 or RAID 1E Mirrors with internal disks the system will probably hang during the first boot sequence see MOS Document ID 1363950.1. Refer to the EIS Checklist for T3 & T4 servers or the Sun Blade 6000 / 6048 Modular System (T3/T4 Blades) for the workaround.Specific to X86 servers:If it is intended to use SVM to mirror the boot disk, ensure that the starting cylinder of the Solaris partition is 1 (not 0). Refer to MOS Document ID 1007887.1.SPARC Server Specialities:If you intend to jumpstart the server via JET then follow the specific instructions both for setting up the install server and installing the SPARC client in the JET checklist.

If the architecture is sun4v:base_config_ClientArch=sun4v

Applicable to T1, T2, T3 & T4 servers.

If installing via JET:Start the installation via JET for each SPARC client.The boot command syntax is dependant on the method of allocation chosen.

haltboot net install

OR

boot net:dhcp install

(Note the space before & after the -)

If installing from local media:The GUI installation does not support installation of a system with a ZFS root file system. To install a system with a ZFS root, the system must be booted in text mode: boot cdrom - textor boot net - text

Boot from local CD/DVD:

boot cdrom

X86 Server SpecialitiesIf you intend to jumpstart the server via JET then follow the specific instructions both for setting up the install server and installing the x64/x86 client in the JET checklist.64-bit Solaris OS is required.

https://support.us.oracle.com/oip/faces/secure/km/BugDisplay.jspx?id=6522017&bugProductSource=Sunhttps://support.oracle.com/rs?type=doc&id=1007887.1https://support.oracle.com/rs?type=doc&id=1363950.1

Task Comment Check

If installing via JET: If using a console/keyboard attached,

during the memory check press F12. The system will now perform a PXE boot via the NIC.NOTE: The selected install method will show on the screen.

If using a serial or network attached device (e.g. laptop) to access the console, during the memory check press CTRL-N. The system will now perform a PXE boot via the NIC.

The J in the check boxes indicate the steps that JET would normally address.

A few steps will have to be carried out manually.

If installing from local media:Insert appropriate Solaris/X86 media and boot.

System should autoboot from CD/DVD after a certain timeout passes.

Actions Common to SPARC & X86 ServersOnce the suninstall dialogue starts:Recommended: Entire Distribution + OEM Pay attention to platform minimum Solaris

requirements!

Recommend: Do not install Power Management unless server has graphics device!

J

For systems with HW RAID / UFS:Normally you would not have a requirement to reserve slice 7 for SVM when using the built-in mirroring capability to mirror the boot disks.However, if the server is to be used as a node in a Sun Cluster environment you will need a slice for the local replicas. This can be placed on the HW-mirrored disk (e.g. slice 7).Install Solaris & reboot. JAfter reboot insert EIS-DVD. Log in as user root JIf EIS-DVD contents are available on a patch or install server via NFS, create a softlink to ease access:ln -s /net//export/install/sun /sun

Subsequently you can access the contents via /sun (instructions below assume using a physical EIS-DVD).Run setup-standard: cd /cdrom/.../sun/install

sh setup-standard.sh

Refer also to MOS Document ID 1006990.1 for importance of Explorer data & correct configuration.

J

Log out & back in to set environment. Alternative: . /.profile JInstall following patches: Solaris patches Sun, Cacao 2.1 & SWUP

cd /cdrom/.../sunpatch-EIS /var/tmp

J

https://support.oracle.com/rs?type=doc&id=1006990.1

Task Comment Check

Fix sendmail messages"My unqualified host name unknown"

(only if DNS not in use).

See MOS Document ID 1008734.1.Activate DNS or edit /etc/hosts and append a fully-qualified hostname e.g. .somewhere.com to the hostname IP-address entry.

Reboot the server. init 6

Required for: T5140/T5240: always. T5120/T5220/Netra 5220: only if

using the NIU 10gb port.

This is a performance tuning variable for the 10gb via xaui or the Atlas card.

Verify entry in /etc/system:set ip:ip_soft_rings_cnt=16

Note for T5220: The Release Notes for Solaris 10 10/09 Chapter 2 refers to the T5220 Huron stating to add ncp-threads-per-core=6 to the file /platform/sun4v/kernel/drv/ncp.conf to avoid a regression.Do NOT do this the issue was fixed before Update 9 released.T1000 / T2000 / T6300 only: At Customer's option, install the Logical Domains Manager Software.

LDoms Manager 1.2 is on EIS-DVD 08DEC10 in directory:.../sun/progs/LDomsPatch available under:.../sun/patch/LDoms/1.2The creation or installation of LDoms is outside the scope of an EIS installation Service for this server. If required refer to the EIS installation checklist for Logical Domains.

For old SPARC Systems (E250, 280R, V880, V480, V890 & V490):The Sun Remote System Control (RSC) 2.2.3 Software is available: from directory .../sun/progs/RSC/10 on EIS-DVD 15JAN14 OR Download Oracle "Patch" 1264451 and unzip & install from

rsc2.2.3_packages_s9.zip (suitable for Solaris 9 & Solaris 10).Apply patch 119381-06 either from EIS-DVD 15JAN14 OR from MOS.For SPARC systems with Sun 10-Gigabit Ethernet PCI-X Adapter only:For SPARC systems that have this (old) interface either: Install the Kirkwood Packages from EIS-DVD 15JAN14 OR Download Oracle "Patch" 10264155 and install the SUNWixge*

packages (but not the SUNWvld* from there).Apply patch 119610-05 either from EIS-DVD 15JAN14 OR from MOS.For SUN4V architecture only:At Customer's option, install the Oracle VM Server for SPARC 3.1 (LDoms 3.x) software.

The Oracle VM Server 3.1 software is on EIS-DVD 04SEP13 in directory:.../sun/progs/LDomsPatch 150817-xx for LDom 3.1 is available on the EIS-DVD in:.../sun/patch/LDoms/3.1The creation or installation of LDoms is outside the scope of an EIS installation Service for this server. If required refer to the EIS installation checklist for Oracle VM Server for SPARC.

http://docs.oracle.com/cd/E19329-01/https://support.oracle.com/rs?type=doc&id=1008734.1

Task Comment Check

UPDATE THE HBA FIRMWARE ON EMULEX HBASDuring the boot sequence you may see the following on the console:WARNING: emlxs0: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm,fcadm, or emlxadm is required.)

This indicates that the install OS or applied SRU includes updated the Emulex drivers but the firmware in the Emulex HBAs does not match. To perform this update, execute fcadm force-lip against each emlxs instance that reports the message.If these messages are not seen, skip this section & go to page 8.The information here is taken from the README of patch 145954-071.There will also be entries in the messages file:# grep emlx /var/adm/messages[...]13:56:09 host1 emlxs: [ID 349649 kern.info] [ 1.0340]emlxs1:WARNING:1540: Firmware update required. (A manual HBA reset or link reset (using luxadm or fcadm) is required.)

This procedure, while disruptive, will ensure that both driver and firmware are current. The force lip will temporarily disrupt I/O on the port. The disruption and firmware upgrade takes approximately 30-60 seconds to complete as seen from the example messages below. The example shows an update is needed for emlxs instance 0 (emlxs0) and emlxs instance 1 (emlxs1), which happen to correlate to the c1 and c2 controllers in this case.Use the following command to determine the controllers as shown:# fcinfo hba-portHBA Port WWN: 10000000c9e43860 OS Device Name: /dev/cfg/c1 Manufacturer: Emulex Model: LPe12000-S Firmware Version: 1.00a12 (U3D1.00A12) FCode/BIOS Version: Boot:5.03a0 Fcode:3.01a1 Serial Number: 0999BT0-1136000725 Driver Name: emlxs

HBA Port WWN: 10000000c9e435fe OS Device Name: /dev/cfg/c2 Manufacturer: Emulex Model: LPe12000-S Firmware Version: 1.00a12 (U3D1.00A12) FCode/BIOS Version: Boot:5.03a0 Fcode:3.01a1 Serial Number: 0999BT0-1136000724 Driver Name: emlxs

When recording the controller numbers ensure that you ONLY choose Exlulex controllers (any Qlogic HBAs present will also show up in the above output).Start the update on the first controller (Emulex only!):# luxadm -e forcelip /dev/cfg/c1

1 Patch 145954-07 has since been OBSoleted by 149174-03.


Task Comment Check

You can look at the messages (which have wrapped-around below):# tail -f /var/adm/messages[...]15:11:34 host1 emlxs: [ID 349649 kern.info] [ 5.031F]emlxs1: NOTICE: 710: Link down.15:11:39 host1 emlxs: [ID 349649 kern.info] [13.02C0]emlxs1: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=20 fw=3)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0ECB]emlxs1: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.20a6 new=1.20a8 Update.)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0EEB]emlxs1: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.02a3 Update.)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0EFF]emlxs1: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.80x5 new=2.82a4 Update.)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0F0E]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI1: old=2.80n5 new=2.82a3 Update.)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0F1D]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.80x5 new=2.82a4 Update.)15:11:39 host1 emlxs: [ID 349649 kern.info] [ 3.0F2C]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.80x5 new=2.82a4 Update.)15:11:59 host1 emlxs: [ID 349649 kern.info] [ 3.0143]emlxs1: NOTICE:1521: Firmware download complete. (Status good.)15:12:04 host1 emlxs: [ID 349649 kern.info] [ 5.0549]emlxs1: NOTICE: 720: Link up. (4Gb, fabric, initiator)

Then repeat for the second controller (you can look at the messages again):# luxadm -e forcelip /dev/cfg/c2

You are advised to reboot the system as this stage since although the firmware is correctly updated the fcinfo hba-port command will continue to display the old version until rebooted.

# reboot


Task Comment Check

Testing CPU & Memory with SunVTSSunVTS 7.x (Solaris 10 Update 5 onwards)The SunVTS 7.x packages are installed by default with the SUNWCXall & SUNWCall Metaclusters into directory /usr/sunvts.File /usr/sun/README contains a description of SunVTS 7.x.It has been decided not to include /usr/sunvts/bin into PATH.Run SunVTS in System Exerciser mode.Run for as long as possible (suggestion: min. 1 hour). For large servers (M8000 / M9000) run overnight.

Change directory:cd /usr/sun/bin

To start SunVTS: TTY mode: ./startsunvts -t GUI mode: ./startsunvts -g

Examine log files in /var/sunvts/logs. If errors occurred, investigate, correct & re-run to ensure a "clean" system.

Task Comment Check

CONNECTING EXTERNAL MASS STORAGEIf no Sun external mass storage attached skip this page!

Connect external storage and label. (Pay attention to redundancy and performance aspects)

boot -rs If all FW has been upgraded boot into multi-user-mode!

External storage (also internal disks): install patches according to current patch matrix.

Various firmware under.../sun/patch/firmware

FW upgrade for all storage components (also internal disks).

FW Interface-Boards

FW Disks

See separate EIS storage checklists as appropriate.

Available from the EIS-Web or on the EIS-DVD.

Configure tape device driver if necessary for the specific tape and Solaris Vn.

M3000 M9000 Servers:Disable mpxio to the internal SAS disks. This avoids that they might appear under the virtual MPXIO controller.Either disable mpxio for the mpt driver or disable MPXIO for the internal controller(s).

# stmsboot -D mpt -d

or# stmsboot -d c0


Task Comment Check

SET UP VOLUME MANAGEMENT SOFTWAREZFS or SVM (UFS) may be used to manage the boot disks under Solaris 10.Boot Disk Mirroring with ZFSIf ZFS mirroring was specified at Solaris installation time, the following steps are NOT required since Solaris will manage this during the installation.The following example will create a ZFS mirror after Solaris installation.

Assumptions:c0t0d0 = rootdisk / bootdiskc1t0d0 = mirrordisk / mirrdisk

Use format on c1t0d0 and make slice 0 encompass the whole ZFS-bootdisk. Write out the label and gave the disk a unique Volume-Name (rootdisk, mirrdisk)

# format c1t0d0format> partitionpartition> 0

...

Create a single-disk root-ZPool into a two-way mirror:# zpool attach rpool c0t0d0s0 c1t0d0s0

This sets up the mirror and starts the resilvering.You can monitor its progress: # zpool status

Make c1t0d0 bootable:# cd /usr/platform/`uname -i`/lib/fs/zfs# installboot -F zfs bootblk /dev/rdsk/c1t0d0s0

Continue with Actions Common (below).Boot Disk Mirroring with Solaris Volume Manager SVMMirror the system disk. Refer to:

SVM: MOS Document ID 1011940.1 EIS-DVD: .../sun/tools/MISC/SVM

Update /etc/vfstabUpdate dump device on systems with SVM mirror the dumpdevice needs to be swap.

# dumpadm -d swap

Consider installing the metacheck script & activate via CRON.

On EIS-DVD under...sun/tools/MISC/SVM

Actions Common to Both ZFS & UFSSPARC only:

Set boot-device & diag-device to both sides of the mirror. See MOS Document ID 1010006.1.

If NVRAM editor (nvedit) was used ensure to setenv use-nvramrc? true

Suggested naming convention: Primary: rootdisk Secondary: rootmirror

Test booting using the new aliases.

https://support.oracle.com/rs?type=doc&id=1010006.1https://support.oracle.com/rs?type=doc&id=1011940.1

Task Comment Check

CONFIGURE AS DNS CLIENT (OPTIONAL)Normally the DNS client configuration will have been entered during the initial boot sequence. The instructions here are included in case the incorrect name service was selected (e.g. none).The domain names and IP addresses used below are examples the real values should be substituted. Be aware that you cannot configure more than three name servers or more than six search domains.Edit (create) file /etc/resolv.conf:Add the line domain to define the default domain name which will be appended to all hostnames without a domain.Add the line search with each domainname and lines nameserver for each name server.

Example:domain uk.oracle.comsearch uk.oracle.com us.oracle.com oraclecorp.com oracle.comnameserver 10.167.162.20nameserver 10.167.162.36nameserver 192.135.82.44

Edit file /etc/nsswitch.conf changing the entries for hosts: and ipnodes: both to contain: files dns

See file /etc/nsswitch.dns for examples of the hosts: and ipnodes: entries.Start the services needed to run the DNS client:# svcadm enable network/dns/client


Task Comment Check

CONFIGURE AS NTP CLIENT (OPTIONAL)The information in this section is taken from: Introduction to Oracle Solaris 11 Network Services, E28996, together with the blog from Jrg Mllenkamp.The domain names and IP addresses used below are examples the real values should be substituted.Jrgs advice (slightly abbreviated): I prefer to use 4 time servers. I think you could either use 1 or 4 ntp servers. Never use 2 don't use three, as when one fails, you have two time servers and as I said, never use two. Why? An old saying goes: You never know the time when you have two clocks. I suggest reading the pool.ntp.org website for choosing a pool as there are continental and country-wide pools as well that may result in a more precise time. Choosing a pool containing only servers near you can really influence the precision of the time. So for example when you are living in Germany, you would use 0.de.pool.ntp.org for example when you are living in the United states you would use 0.us.pool.ntp.org.Usually customers have their own NTP servers which should be used instead of the pool.ntp.org servers.Verify that each NTP server that is intended to be used is reachable (ntp.org servers may not be visible from the customers internal network):# ntpdate -q

Alternatively the IP address cane be specified.Create the ntp.conf file:# cd /etc/inet# cp ntp.client ntp.conf

Edit the ntp.conf file make site specific changes as needed.Replace the following commented lines:# server server_name1 iburst# server server_name2 iburst# server server_name3 iburst

by your appropriate NTP servers, e.g.:server 0.pool.ntp.orgserver 1.pool.ntp.orgserver 2.pool.ntp.orgserver 3.pool.ntp.org

Also deactivate the line with multicastclient 224.0.1.1 by inserting a comment sign (#) in column one.

The ntp daemon doesn't synchronize time when the time offset between time on the client and the time on the server is too large. Thus forcing a time sync is a good idea:# ntpdate 0.pool.ntp.org 3 Apr 13:46:49 ntpdate[1183]: step time server 205.233.73.201 offset -7200.059798 sec

Start the ntpd daemon:# svcadm enable ntp

http://www.pool.ntp.org/http://www.c0t0d0s0.org/archives/7453-Configuring-an-NTP-client-in-Solaris-11.htmlhttp://docs.oracle.com/cd/E26502_01/pdf/E28996.pdf

Task Comment Check

To test enter:# ntpq -p

A successful sync may need 15-30 minutes (but the command can still be used to see whether the NTP client is already working).A "*" will only appear at the front of one of the output lines after quiet some time.


Task Comment Check

SYSTEM CONFIGURATIONVerify that required settings in/etc/system have been made if external mass storage has been attached.

See appropriate EIS storage installation checklists.

Set up data volumes & filesystems according to customer requirements (if purchased).

The consultancy for data volumes (and their setting up) is not part of an EIS Server installation it belongs to ARS/DCRS.

Update /etc/vfstab as required.

SPARC SERVER SPECIFICS

Verify/set the OBP parameters for production:

auto-boot? = trueauto-boot-on-error? = true

Verify/set the NVRAM parameters for production:

setenv use-nvramrc? true

If NVRAM editor (nvedit) was used to create boot aliases etc.

Consider setting the OBP password:eeprom security-mode=commandChanging PROM password:New password: Retype new password:

Suggested to improve security. Since the system can always be booted the root user can always reset the OBP password without knowing the old one.

X86 SERVER SPECIFICS

Enable the system for crash-dump:

Set kmdb flag by appending -k to the kernel line in the following sequence in file /boot/grub/menu.lst#------------------------------------title Solaris 10 5/09 kmdb for debugroot (hd0,0,a)kernel /platform/i86pc/multiboot -kmodule /platform/i86pc/boot_archive#------------------------------------

IMPORTANT: If kernel /platform/i86pc/multiboot -k

does not work then use:kernel /platform/i86pc/multiboot kmdb

for ZFS boot:/boot/grub/menu.lst

See MOS Document ID 1003085.1.

Bug 6553399: kmdb changed to -k in Solaris 10 5/08 Update5.

NETWORKINGConfigure additional (static) network interfaces. Install any required unbundled network software. Patches are available in:

../sun/patch/network

For each additional network interface:1. Enter the interface name into a new

file /etc/hostname. where net-name is the interface such as hme1 or e1000g0,

2. Ensure that the interface name and its IP address are in the /etc/hosts file.

If system has multiple network interfaces and should NOT act as a router:

# touch /etc/notrouter

https://support.oracle.com/rs?type=doc&id=1003085.1

Task Comment Check

Set up /etc/defaultrouter according to customer requirements.A reboot will be required to effect the above configuration activities.COMPLETIONConsider disabling remote ssh logins (eg if enabled via setup-standard).

In /etc/ssh/sshd_config

See PermitRootLogin.

Reboot =>everything o.k?

Now return to the checklist from whence you came...

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 [email protected] .Partners should mail to: [email protected] .


eis installation checklist for the solaris 10 os

Documents