EIS Installation Checklist for Entry Level-Servers

(Ultra-SPARC III, IIIi & IV)

Customer:
Sun Order Number:
CASE Number:
Technician:
Version EIS-DVD:
Date:

• It is assumed that the installation is carried out with the help of the current EIS-
DVD. See http://EIS/eisdvd for current information.
• The idea behind this checklist is to help the installer achieve a "good" Installation.
• For platform minimum Solaris requirements refer to table at the bottom of page 10.
• It is assumed that the installer has attended the appropriate training classes.
• For the installation of a cluster this Installation checklist is used together with the
checklist for Sun Cluster.
• Inserting Sun equipment into racks is not a documented Server Installation
Services deliverable and hence incurs extra charge. However, local countries may
make decisions on whether racking should be done without extra charge.
• 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.
• EIS recommends that the installation be prepared using WINGS (Workflow
Information Gathering System) – mandatory if used in a Sun Cluster.

Server 1 Server 2
Server Type
Serial Number
Hostname
Hostid

Task Comment Check

PREPARATION
FIN/FCO/EIS-ALERTs reviewed?
Power, network, grounding available?
All installation information available? Hostname. Interface names, IP
addresses, netmasks etc.
If name service (DNS, NIS) in use, ensure
that new hostnames, IP addresses etc. are
correct on name server.

Sun Internal and Approved Partners Only Page 1 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
UNPACKING
Delivery complete?
Collect the yellow system records. File away carefully!

Allow the system to acclimatise (power Refer to EIS standard “Acclimatisation of

off) at the customer site. Sun Servers & Storage”
Unpack outside data center to ensure no Collect packing material together for
contamination/dust is released inside disposal.
customer's controlled environment.
Verify all packing material has been Fans & air vents must be free to operate.
removed, i.e. nothing is blocked.
Gather excess parts, cables etc. in a box. Inform customer during handover.
Collect documentation together. Give to customer during handover.

Request licences where required. Sun / customer requests licences.

ASSEMBLY/CABLING
Note the serial numbers.
Assemble the (storage) racks (screw Connect fans if appropriate!
down the feet, mount stabiliser bars)...
Insert items into (storage) racks in a (lowest controller-ID at bottom,
logical way. sequentially numbered upwards).

See FIN# I0995-1 when inserting Sun Fire

280R/E220R/E420R into Sun Rack 900.
See FIN# I0990-1 re V880 & Sun Rack 900.
Distribute items across power-sequencers considering failure-safety.
Install "Cable Management Arm" if provided with server.
Connect grounding cables.
Ensure that all power cables and disks
are firmly seated.
Install cards for peripherals. Consider redundancy and performance
aspects.
V480/V490/V880/V890: If the internal Installing the second path will require
FC-loop multipath option was ordered that a cable be connected from the disk
backplane to a PCI fibre-channel host bus
but not installed, install it now. adapter installed in the system. Refer to
See also page 17. the system service manual for the
procedure.
Label the cables clearly.
Use cable binders. Air filters must be easily accessible, thus
cables should not be laid too tightly.

Sun Internal and Approved Partners Only Page 2 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
V440/N440 only: See SunAlert 57618 & FCO A0245-1.
On older systems do not use net0 See also (with SWAN access):
(usually ce0) onboard network port 0 if http://onestop/qco/v440/index_v440.shtm
at all possible – see page 15 for details. l
If not in use, then disable in the
EEPROM – see next page.
V480/V490 only:
When cabling the onboard Ethernet be
aware that ce0 runs at 33 MHz and ce1
at 66 MHz and hence it is probably
advisable to plan to use ce1 as the
primary interface for higher throughput.
Connect the data cables for external
storage AFTER the Solaris installation!

Sun Internal and Approved Partners Only Page 3 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Check

SYSTEM CONTROLLER CONFIGURATION – ALOM

Applicable to Sun Fire V125, V210, V215, V240, V245, V250, V440, V445 and Netra 210, 240 &
440 servers. For other servers go to page 9.
Before you can bring up the system, the ALOM needs to be configured correctly.
Before you can update the ALOM you must have Solaris installed on the system!
Hence if your server has a down-revved ALOM version and you require the features
of the latest ALOM, then you must configure the existing ALOM the best you can,
install Solaris (as in this checklist), update the ALOM (page 16) and then
reconfigure the latest ALOM for the features that are required.
These servers include a dedicated system controller (SC) for complete server
independence and maximum availability of server management. The SC is an
embedded PowerPC that provides the following functions:
• Environmental monitoring of the platform (such as temperatures, voltages,
fan speeds, and panel switches),
• Alert messages when problems occur,
• Remote control of system operations (boot, shutdown, and reboot of the
server's operating server, turning the server's power on and off, ASR
functionality, and upgrading the firmware).
You have three choices in setting up the SC. You can set it up serial management
only or network management using either DHCP or Static IP for the SC's address.
Connect the server (SER.MGT port) to a serial terminal or a terminal
emulator (PC or workstation) to display system messages.
Connect the data cables to the server, but do not connect the power cable yet.
Beware that there is a 60-second timeout “feature” of the console which can
catch you out if you are slow in attaching AC power and connecting to SER
MGT port, starting laptops, and starting the tip/hyperterminal connection.
If this does occur, enter #. which is the default escape sequence to return
from the console back to the ALOM prompt.
If you do not see an sc prompt at this stage press the ENTER key once & you
will probably see Solaris configuration prompts...
Connect the AC power cable to the server and examine the display for any
error messages.
The system controller (SC) runs on the 3.3v standby voltage. As soon as AC power is
connected to the system, the system controller immediately powers on, runs diagnostics, and
initialises the ALOM firmware.
After the system controller boots, Sample output:
access the ALOM command line ............................
interface through the serial management .
TTYD – - PASSED
port. TTYC – - PASSED
The sc prompt is displayed at the first time the MEMORY - - PASSED
MPC885 - - PASSED
system controller is booted. The default sc>
configuration provides an ALOM user account
called admin.

Sun Internal and Approved Partners Only Page 4 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Check

V215 & V245 only:

On a small number of Sun Fire V215 and V245 systems, ALOM and SC
administration password was mistakenly set to "admin1" at pre-shipping,
where there should be no password set by default.
From Sun Alert 102719: to clear this, log in as user admin with password admin1 & set the
SC configuration to default values before setting a password as described below:
sc> setdefaults -ya
If this is the first time the system has sc> password
been powered on, use the password password: changing password for admin
Setting password for admin.
command to set the admin password. New password: <new-password>
You must set an admin password on the
SC otherwise you can not change any Re-enter new password: <new-password>
settings on the SC. sc>
Prior to ALOM 1.6 there was no default
password for user admin. With ALOM
1.6 on Vxx5 servers the default password
is the last 8 digits of the chassis serial
number.
From the command: showsc version -v
Advanced Lights Out Manager v1.6
SC Firmware version: 1.6.0
SC Bootmon version: 1.6.0
<snip>
Updating the ALOM version is done once Solaris is running (page 16).
Configure the SC network addresses.
You may configure the SC using the setupsc command. This will give you a
script driven setup of the SC. For an example dialogue see Appendix A on
page 26.
Then enable the new configuration by resetting the SC: resetsc -y
If desired, you can customise all of the ALOM configuration variables at
once by following the interactive questions in the script. To configure only
the network interface variables, press Return at each prompt until the
following prompt is displayed:
Do you wish to configure the enabled interfaces?(y)

Enter y or press Return to enable the network interface, or enter n to disable

it. This sets a value for the if_network variable.

Sun Internal and Approved Partners Only Page 5 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Check

NOTE: For the V215, V245 & V445 servers DHCP is set up as default, for
the other servers this is not the case.
Follow the interactive questions in the script. The script prompts you to set
values for the following variables:
if_modem (specify false)
netsc_dhcp Specifies if DHCP will be used for the SC IP address
netsc_ipaddr IP Address of the system controller
netsc_ipnetmask Netmask for the system controller subnet
netsc_ipgateway IP address of the gateway for the subnet
if_connection For connection via the network management port1.
When you have finished setting up the network interface variables, enter Control-Z to save
your changes and exit the setupsc script. If desired, you can finish configuring all of the
ALOM configuration variables. Before you can use your network configuration, you must
reset the ALOM.

Process for Manual Configuration

To configure the SC networking the following 5 parameters need to be set/verified:
netsc_ipnetmask Netmask for the system controller subnet
netsc_ipaddr IP Address of the system controller
netsc_ipgateway IP address of the gateway for the subnet
if_network Specifies whether the SC is on the network or not
netsc_dhcp Specifies if DHCP will be used for the SC IP address
if_connection For connection via the network management port1.
The command to set these variables is: setsc <variable_name> <value>
Example: setsc if_network true
Settings for Serial Management Only: setsc if_network false
No other setting is needed.
Settings for Static IP Addressing: setsc if_network true
setsc netsc_dhcp false
setsc netsc_ipnetmask <value>
setsc netsc_ipgateway <value>
setsc netsc_ipaddr < value>

Settings for DHCP IP Addressing: setsc if_network true

setsc netsc_dhcp true
setsc netsc_ipnetmask <value>
setsc netsc_ipgateway <value>
You can leave netsc_ipaddr blank.
If connecting via the net.mgt port, setsc if_connection <value>
if_connection must be set to telnet or
ssh.
Verify the parameters are correct. showsc
shownetwork
Enable the new configuration by resetsc -y
resetting the system controller.

1 The parameter if_connection is first available with ALOM 1.6. Default is ssh on V215, V245
& V445; otherwise none.

Sun Internal and Approved Partners Only Page 6 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Check

Note that if a workstation/laptop is available it is convenient to use two separate

windows when communicating with the server. Use one to connect to the SC (via
SER MGT or NET MGT) and a second window (via NET MGT) to connect to the
console (saves switching back & forth).
Once the reset has completed, log back From the “SC” window:
into the system controller using either Please login: admin
the management serial port or telnet (if password: <admin-password>
you configured the network interface)
or ssh (with ALOM 1.6).
Configure the system to run maximum
POST for the initial power up and
afterwards reset this to default.

Sun Internal and Approved Partners Only Page 7 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Check

Bringing up the System: Two-Window Method

For all ALOM versions...
Connect to the system console.
Output from POST, OpenBoot, and the
Solaris OS is displayed in the system
console using the network console on
the system controller.
Power on the server from a keyboard
using the ALOM software.
Then GOTO “Common Actions”
(below).
From the “console” window:
sc> console -f
The -f option to forces the console to be
attached to your session. Multiple users
can be connected to the console in read-
only view mode, but only one can be
attached in read-write interactive mode.
From the “SC” window:
sc> poweron
SC Alert: Host system has reset
sc>
The SC Alert message on the ALOM
console indicates that the system has reset.
Watch the system console window for
POST, OpenBoot and Solaris Boot output.

Bringing up the System: Single-Connection Method

For ALOM version 1.6 only....
Connect to the SC. Please login: admin
password: <admin-password>

If you are local to the system: sc> console -f

Enter #. to return to ALOM
Connect to the console and then press
the power button on the server.
If you are remote from the server: sc> poweron -c
SC Alert: Host system has reset
Power on the server from a keyboard
using the ALOM software and connect (uncertain that above response is correct...)
to the system console.
Output from POST, OpenBoot, and the Solaris
OS is displayed in the system console using the
network console on the system controller.

Common Actions
After you issue the poweron command, the CPU and memory controllers
initialise and eventually OpenBoot initialises. After a number of system
messages, you will see the ok prompt. The time this takes varies with the
amount of memory and number CPUs in your system.

Sun Internal and Approved Partners Only Page 8 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
PRE-SOLARIS-INSTALLATION – assumes connection to the console.
Please note that servers with OBP 4.15.1 & later have “Diag-ON” enabled
which may well result in a longer initial boot time. A large blue sticker on
the front of the server should draw attention to this new feature.
Power up the server in diag-mode. Perform complete test once!

OBP v4.15.1 or later: Currently the V490 & V890 ship with
For OBP v4.15.1 or later PTS recommends the OBP v4.15.1 (or later).
keyswitch stay in the normal position unless no
output appears on the ttya (meaning possible
DOA). If DOA is suspected, the keyswitch
should then be placed in the diagnostics
position to verify there is no POST output to
the serial port to rule out wrong OBP parameter
settings or configured RSC. If an output is seen
then set the OBP variables back to the defaults.
Systems with OBP v4.15.1 or later with Other systems to also set:
keyswitch in normal mode only set the ok> setenv diag-level min
following parameter: ok> setenv diag-switch? false
ok> setenv auto-boot? false
PTS highly recommends the defaults are not changed, given that we now
have useful intelligent defaults.
ASR is automatically enabled with v4.15.1 (Diag-ON) or later and no longer
needs to be manually enabled.
The FIN# I1070-1 should be referenced for further information on the new
settings, commands, Service mode variable overrides and control.
Systems with OBP v4.15.1 and later, will be running POST out of the box
when powered on. It will take a lot longer to get to the initial "ok> "
prompt. Flashing of LED's and console status output is provided to indicate
POST is running and the system is not idle. Subsequent resets will not run
POST except on power cycles or hard errors.
If there is more than 1 interface: • For SunCluster 3.0 "false".
ok> setenv local-mac-address? True • For SunCluster 3.1 "true".
Default on Sun Fire V210, V240, V250 & (See checklist for SunCluster).
Netra 240.
Default is false for V440 & Netra 440.
Boot from CD-ROM or network. Single-User mode: boot cdrom -sv

Ensure devices are where expected. cd /dev/rdsk

ls -l c*s2
If NOT, fix & reboot (-s).
V440 & Hitachi 36/72Gb internal disk: • 116369-xx (36Gb)
Verify the firmware via format • 116370-xx (72Gb)
F/W PQ08 needs upgrade to PQ0B or
later.
Check F/W of boot device. If NOT OK, update

Change to Level 2. exit

Sun Internal and Approved Partners Only Page 9 of 26 Vn 1.49 Created: 22. Feb. 2007
 INFORMATION: PLATFORM MINIMUM SOLARIS REQUIREMENTS
Most Ultra III Entry Level Servers can operate with Solaris 8 HW 12/02 (or later) or
any version of Solaris 9 and 10. There are some exceptions:
Sun Fire V210/V240 (EnxS):
• Solaris 8 PSR1 also known as Solaris 8 HW 12/02.
• Solaris 9 update 3 also known as Solaris 9 4/03.
• Solaris 10 FCS.

Sun Fire V250 (2ptower):

• Solaris 8 PSR3 also known as Solaris 8 HW 07/03.
• Solaris 9 update 4 also known as Solaris 9 HW 08/03.
• Solaris 10 FCS.

Sun Fire V440 (Chalupa):

• Solaris 8 PSR3 also known as Solaris 8 HW 07/03.
• Solaris 9 update 5 also known as Solaris 9 HW 12/03.
• Solaris 10 FCS.

Netra 440 (Chalupa19):

• Solaris 8 PSR3 also known as Solaris 8 HW 07/03.
• Solaris 9 update 5 also known as Solaris 9 HW 12/03.
• Solaris 10 FCS.
• Firmware 4.17.1 or later.
• ALOM 1.5.3 or later

Sun Fire V490 (Sebring) & V890 (Silverstone) UltraSPARC IV:

• Solaris 8 PSR4 also known as Solaris 8 HW 02/02 or
• Solaris 9 update 6 also known as Solaris 9 HW 04/04.
• Solaris 10 FCS.
• Firmware 4.15.1 or later.
• RSC 2.2.2 or later.

Sun Fire V490 (Sebring) & V890 (Silverstone) UltraSPARC IV+ 1500 MHz:
• Solaris 9 Update 8 also known as Solaris 9 HW 09/05.
• Solaris 10 HW1.
• Firmware 4.18.2 or later.
• RSC 2.2.3 or later.

Sun Fire V125 (El Paso), V215/V245 (Seattle) & V445 (Boston)
• Solaris 9 9/05 HW Update 92 (Solaris 9/05 U8 is NOT supported).
• Solaris 10 Update 2 also known as Solaris 10 6/06 with EIS-DVD ≥26SEP06.

2 Solaris 9 9/05 HW U9 can be obtained from http://www.sun.com/software/solaris/releases.xml

Sun Internal and Approved Partners Only Page 10 of 26 Vn 1.49 Created: 22. Feb. 2007
 INFORMATION: ISSUE WITH SOLARIS 9U7 & IDE DVD-ROM DRIVES
Solaris 9 Update 7, also known as HW 09/04, has an affected version of patch
112954 built into it. When installing a server with certain IDE DVD-ROM drives
(such as the Toshiba ATAPI DVD-ROM as found on the V490, V890, V1280 &
E2900 servers) you may be affected by issues described in Sun Alert 57674.
Since this issue is solved in Solaris 9 Update 8 you are recommended to use this
media (or later).

Task Comments Server

1 2

BOOTING SOLARIS FROM A PRE-INSTALLED DISK IMAGE

Initial server bootup: Answer as appropriate.
Upon initial boot, the server will ask the
typical Solaris post-install configuration
questions.
If this is a CRS-prepared system, you can probably go straight to the
Explorer/Analysis section on page 25.
Once Solaris has booted up, log in and
gain access to an EIS-DVD image.
Run setup-standard as user root: If this is a CRS-prepared system, take care
cd /sun/install; sh setup-standard.sh not to change settings that customer
specified!
Update Solaris patches from EIS-DVD: cd /cdrom/.../sun/patch
cd <solarisVn>
• Recommended Cluster unpack-patches -r -q
• Additional Solaris Patches

If the Solaris 10 KU-36 patch was not
previously installed and active, you
must reboot the system and repeat the
previous step to complete the patching.
If using Sun Update Connection
Software (Solaris 10 U1 onwards),
update the appropriate patches.
If using J2SE Software, update the
patches.
When using EIS-DVD ≥27FEB07.
IMPORTANT: This will be necessary if
Solaris 10U3 or lower were installed.
cd /cdrom/.../sun/patch
cd SWUP/<solarisVn>
unpack-patches -r -q
cd /cdrom/.../sun/patch
cd J2SE/5.0
unpack-patches -r -q

You can now go straight to the Mass-Storage section on page 19.

Sun Internal and Approved Partners Only Page 11 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
SOLARIS-INSTALLATION
Install according to the WINGS "Server/Domain Standard" document.
If you intend to jumpstart the server via If the client(s) to be installed requires that
JET then follow the specific the boot image on the install server is
pre-patched, apply such patches now.
instructions both for setting up the
install server and installing the SPARC
client in the JET checklist.
If installing via JET: halt
boot net – install
Start the installation via JET for each
SPARC client. OR

The boot command syntax is dependant boot net:dhcp – install

on the method of allocation chosen. (Note the space before & after the “-”)

If installing from local media: boot cdrom

boot from local CD/DVD.

Once the suninstall dialogue starts: Recommend: Do not install Power J J
Entire Distribution + OEM Management unless server has graphics
• Pay attention to platform minimum Solaris device!
requirements!
Recommend combine /, /usr & /opt See EIS Standard: “Boot Disk Layout” J J
into slice 0.
/var can be located in a separate slice;
there must be sufficient space for at
least 2 crash-dumps (2 GB?).
Primary swap partitions 2 GB.
V480/V490 only:
When configuring the onboard Ethernet
be aware that ce0 runs at 33 MHz and
ce1 at 66 MHz and hence it is probably
advisable to configure ce1 as the
primary interface for higher throughput.
For systems with HW RAID: EXCEPTION: for a V440 server with
Normally you would not have a Solaris 8 placing the local replicas on a
HW-mirrored internal disk is not
requirement to reserve slice 7 for SVM supported – does work for Solaris 9 & 10.
when using the built-in mirroring See Infodoc 77518
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. J J
After reboot insert EIS-DVD. Log in as user root J J

Sun Internal and Approved Partners Only Page 12 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
Run setup-standard: J J
cd /cdrom/.../sun/install; sh setup-standard.sh
• Be sure to select option to install SAN Foundation Suite.
Refer also to Infodoc 87881 for importance of explorer data & correct configuration.
Logout & back in to set environment. Alternative: . /.profile J J
V880/V890: flashupdate the backplane. EIS-DVD: sun/patch/firmware.
• 117814 for V880/V890.
Confirm current F/W via
luxadm display FCloop
This patch is independent of the Solaris
See patch README for available version. Follow the special instructions in
firmware release e.g.: patch README carefully.
Unbundled Release: DPM_922A
Install Solaris patches: cd /cdrom/.../sun/patch J J
cd <solarisVn>
• Recommended Cluster unpack-patches -r -q
• Additional Solaris Patches

If the Solaris 10 KU-36 patch was not When using EIS-DVD ≥27FEB07.
previously installed and active, you IMPORTANT: This will be necessary if
must reboot the system and repeat the Solaris 10U3 or lower were installed.
previous step to complete the patching.
If using Sun Update Connection cd /cdrom/.../sun/patch/SWUP
cd <solarisVn>
Software (Solaris 10 U1 onwards), unpack-patches -r -q
install the appropriate patches.
If using J2SE Software, update the cd /cdrom/.../sun/patch
cd J2SE/5.0
patches. unpack-patches -r -q

Solaris 8: Verify entry in /etc/system EIS-ALERT#22

set TS:ts_sleep_promote=1
Apply all SAN patches. • .../sun/patch/SAN J J
(Solaris 8 & 9 only). • .../sun/patch/SAN/8 (9)
REBOOT (reconfigure). touch /reconfigure
init 6
For Netra servers consult the TSC (PTS) web pages within SWAN for the
list of required point patches: http://systems-tsc/twiki/bin/view/Products
Point Patches are not stored on the EIS-DVD – see
http://sunsolve.sun.com/point – follow patch install instructions carefully.
Fix sendmail messages See Infodoc 18075.
"My unqualified host name unknown" Activate DNS or edit /etc/hosts &
/etc/inet/ipnodes and append a fully-
(if DNS not in use). qualified hostname e.g.
<hostname>.somewhere.com to the
hostname IP-address entry.
Ensure that /etc/hosts &
/etc/inet/ipnodes are synchronised
EXCEPT that /etc/hosts must not have
any IPv6 entries (see man ipnodes).

Sun Internal and Approved Partners Only Page 13 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
Solaris 8 & 9 only: See FIN 100271.
Install the cediag software. Run cediag On EIS-DVD:
once manually to accept the license. cd .../sun/tools/cediag
For legal reasons the customer must Follow the README.
accept the license (not the installer).
Determine if the system is affected by Sun Alert 102139 (likely to affect
only Sun Fire V440/V480/V490 & Netra 440):
% iostat -E
sd0 Soft Errors: 8 Hard Errors: 0 Transport Errors: 0
Vendor: <vendor name> Product: ODD-DVD SD-C2732 Revision: 1051 Serial
No:
Size: 0.53GB <529838080 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 8 Predictive Failure Analysis: 0

If you see SD-C2732 & the firmware See patch 120364 on EIS-DVD:
level is 1051 then you must upgrade the .../sun/patch/firmware
firmware.
Update flashprom (OBP) on server:
• 108673 Netra T1 System PROM.
• 109082 Ultra 80 & E420R.
• 118323 Sun Blade 1000/2000, Sun Fire 280R and Netra T4 OBP.
• 111952 Netra X1.
• 121688 Sun Fire V880/V890 Flash PROM Update.
• 121689 Sun Fire V480/V490 Flash PROM Update.
• 121690 Sun Fire V445 (EIS-DVD 31OCT06).
• 121685 Sun Fire V440 & Netra 440 (EIS-DVD 12DEC06).
• 121683 Sun Fire V210/240.
• 121692 Sun Fire V215/V245.
• 121691 Sun Fire V125.
• 117365 Sun Fire V250.

Power Cycle.

Sun Internal and Approved Partners Only Page 14 of 26 Vn 1.49 Created: 22. Feb. 2007
V440/N440 Only: Possibly Disabling Onboard Network Port 0 – Sun Alert
57618 /101548
Only older systems may be affected – the following is an extract from Sun Alert
57618/101548 (FCO A0245-1) to determine if your system may be affected.
Systems manufactured after November 1, 2004 had the correction integrated into the
boards – but see footnote3.
The new board was "phased-in" into manufacturing starting 1st November 2004.
This means that between that date up to approx. 21st January 2005 systems were built
having a mixture of affected and non-affected motherboards. Systems manufactured
approximately after January 21, 2005 are not affected.
Boards with the following dash level markings are not affected:
For Sun Fire V440:
540-5418-07 (FRU)
- 501-6344-10 (Manufacturing part number)
- 270-6344-07 (Fab level)
or
540-6336-01 (FRU)
- 501-6910-01 (Manufacturing part number)
- 270-6344-07 (Fab level)

For Netra 440:

540-5919-06 (or higher) [F] Motherboard Assy, Netra 440, N42
-501-6910-01 (or higher) Motherboard

To identify an affected system, use the prtfru(1M) command or physically look at

the motherboard part number information. Example output from the prtfru(1M)
command is shown below:
/frutree/chassis/MB?Label=MB
/frutree/chassis/MB?Label=MB/system-board (container)
SEGMENT: SD
/ManR
/ManR/Fru_Description: ASSY,A42,MOTHERBOARD
/ManR/Manufacture_Loc: Sriracha,Chonburi,Thailand
/ManR/Sun_Part_No: 5016344 <----------
/ManR/Sun_Serial_No:
/ManR/Vendor_Name: Celestica
/ManR/Initial_HW_Dash_Level: 10 <---------
/ManR/Initial_HW_Rev_Level: 51
/ManR/Fru_Shortname: A42_MB
/SpecPartNo: 885-0060-09

The lines noted in bold above should be concatenated to form the full manufacturing
part number. In the example above, the motherboard part number should be read as
501-6344-10 and therefore is not affected. If the output of the prtfru(1M) command
showed the motherboard part number to be 501-6910-01 (or later), it would also be
not affected.

3A number of Sun Fire V440 systems manufactured between 1st November 2004 and approx 21st
January 2005 have FRU information programmed indicating they are 501-6344-09 motherboard,
however they have the fix integrated at the Fab level as follows:
540-5418-06 (FRU)
- 501-6344-09 with a deviation label "WO_30188"
- 270-6344-07 (Fab Level)
These exceptions will have output from the prtfru(1M) command indicating they are 501-6344-09. All
motherboards with this revision should be physically inspected for a sticker label indicating
"WO_30188". If this label is present, then this motherboard is not affected and should not be
replaced. Conversely, if the sticker label is not present and the motherboard is identified as 501-6344-
09, then it is affected and should be replaced.

Sun Internal and Approved Partners Only Page 15 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
V440/N440 Only: Disabling Onboard Network Port 0 – Sun Alert 57618/101548
V440/N440: If you have an affected motherboard and you are not using net0
(usually ce0) onboard network port 0 (see previous page), then disable in the
EEPROM using the following procedure (from SunAlert 57618/101548 /
FCO A0245-1) to install an NVRAM script at the OBP “ok” prompt:
ok nvedit
0: probe-all install-console banner
1: " /pci@1c,600000/network@2" $delete-device drop
2:
^C
Type "Ctrl-C" to exit nvedit as shown above. Then continue with:
ok nvstore
ok setenv use-nvramrc? true
use-nvramrc? = true
ok reset-all

Task Comment Server

1 2
UPDATING ALOM FIRMWARE
Applicable to systems listed on page 4.
Determine the ALOM version. ALOM 1.6.3 on EIS-DVD 27FEB074.
The firmware files are on the EIS-DVD For V215/V245/V445:
ALOM_1.6.3_fw_hw8.tar.gz
in .../sun/patch/firmware/ALOM.
For other systems:
Or from www.sun.com/download: ALOM_1.6.3_fw_hw0.tar.gz
=> Systems Administration
=> Systems Management
=> ALOM (Advanced....)
Log into Solaris as user root. Log in via network interface and NOT
the SER.MGT port and the console!
Create directory cd /usr/platform/`uname -i`/lib
mkdir images
cd images
Copy the correct compressed tarball (eg
from EIS-DVD) into this directory.
Unpack the tarball and follow the gzcat ALOM_1.6*.tar.gz | \
tar xBpf -
remaining instructions in the README
file.
This process took about 20 minutes on a V240 server.....
The commands to update the firmware display the progress of the update
(both on Solaris terminal and the SC console)..

4 The ALOM 1.6 files are on EIS-DVDs 26SEP06 to 30JAN07.

Sun Internal and Approved Partners Only Page 16 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task
Continuing with RSC, LOM, SunVTS
For V880, 480R, Sun-Blade-1000, Sun- EIS-DVD:
Fire-280R, Netra-T4: ...sun/tools/ELS
Perform online validation.
Consider configuring the RSC card
(applies to 280R, V480 - V890).
Consider configuring the Lights-out-
Management (LOM).
LOM is appropriate for:
• Sun Fire V100 & V120
• Netra X1, Netra 120, Netra 20 (T4)
• Netra T1 AC200 & DC200
• Netra t1 Model 100 & 105
• Netra t1400 & 405
Consider configuring multipathing of
any internal drives with STMS if a
second path is available.
Note: This procedure will configure
multipathing globally on all FC ports.
If this is not desired, please consult the • stmsboot -l x <--- where "x" is
documentation on how to enable STMS
on a per-port basis. The Sun StorEdge
Traffic Manager documentation is
available at http://docs.sun.com
Sun Internal and Approved Partners Only
Comment Server
1 2
See EIS-DVD:
.../sun/docs/MISC/RSC-setup.txt
RSC packages are in .../sun/progs/RSC
RSC patches are in .../sun/patch/RSC.
See EIS-DVD:
../sun/docs/MISC/LOM-setup.txt
For Solaris 8&9:
• In /kernel/drv/scsi_vhci.conf, enable
MPXIO by changing
mpxio-disabled="yes";
to
mpxio-disabled="no";
the controller number of the first path
• stmsboot -l y <--- where "y is the
controller number of the second path
The previous two commands will show
you the STMS names for the internal
disks. The STMS name should be the
same for both paths to a disk. The t
(target) value will be the node WWN of
the disk.
• Modify /etc/vfstab to point the
affected filesystems to the correct
devices based on the output of
stmsboot -l.
• stmsboot -e
• and reboot.
For Solaris 10:
• In /kernel/drv/fp.conf, enable
MPXIO by changing
mpxio-disabled="yes";
to
mpxio-disabled="no";
• stmsboot -e
• and reboot (stmsboot should prompt).
Further information in Infodoc 80141.
Page 17 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
RUNNING SUNVTS
Solaris 10: See Solaris 10 DVD “Extra Value”
Install SunVTS 6.x version appropriate directory for the packages.
to the Solaris distribution.
Solaris 10: cd .../sun/patch/SunVTS/6.1
or (6.x...)
Patch SunVTS 6.x (if patch available). unpack-patches -r -q

Solaris 8 & 9: SunVTS 5.1 packages are on the Solaris

Install SunVTS 5.1 packages.
SunVTS Vn 5.1 preferable and
supports Solaris 8 02/02 upwards and
all Solaris 9 releases.
Solaris 8 requires XML packages!
Solaris 8 & 9:
Patch SunVTS 5.1
Supplementary CD for Solaris 8 12/02
upwards& Solaris 9 09/02 upwards.
For Solaris 8 you MUST install the
packages SUNWlxml & SUNWlxmlx
from the same CD BEFORE the VTS
packages.
Patch is on the EIS-DVD:
.../sun/patch/SunVTS/5.1

Run stress test CPU/MEM. To start SunVTS: sunvts -t

• Test Execution
• Verbose Enabled

When test window has ended, stop VTS Run for as long as possible (suggestion:
tests cleanly to save the report in file min. 2 hours). Save a copy of test
/var/opt/SUNWvts/logs/sunvts.info results (sunvts.info).

Examine SunVTS log file. If errors occurred, investigate, correct &

re-run to ensure a "clean" system.

Sun Internal and Approved Partners Only Page 18 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task
CONNECTING EXTERNAL MASS STORAGE
If no Sun external mass storage attached skip this page!
Install StorADE software.
Patch StorADE software (if available).
Connect external storage and label.
If Ultra-SCSI-III host adapters are
present install the SUNWqus drivers.
Example: X6758/Jasper card – supports D1, S1
& SE3310 storage.
If SUNWqus installed, apply patch &
REBOOT.
Dual-hosted SCSI-arrays: modify
/kernel/drv/glm.conf or scsi-initiator-id
boot -rs
External storage (also internal disks):
install patches according to current
patch matrix.
FW upgrade for all storage components
(also internal disks).
See separate EIS storage checklists as
appropriate.
Use StorADE to test external mass
storage as appropriate.
Configure tape device driver if
necessary for the specific tape and
Solaris Vn.
Sun Internal and Approved Partners Only
Comment Server
1 2
EIS-DVD:
.../sun/progs/StorADE
EIS-DVD:
.../sun/patch/StorADE
(Pay attention to redundancy and performance
aspects)
EIS-DVD: ../sun/progs/SUNWqus
Available for Solaris 8 & 9
EIS-DVD: ../sun/patch/SUNWqus
Available for Solaris 8 & 9
Infodoc: 20704
If all FW has been upgraded boot into multi-
user-mode!
Various firmware on EIS-DVD under
.../sun/patch/firmware
FW Interface-Boards
FW Disks
Available from the EIS-Web or on the EIS-
DVD.
If ArrayStart purchased...
Page 19 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
SET UP VOLUME MANAGEMENT SOFTWARE
Veritas VxVM Software (Version 4.x)
With VxVM 4.x it is no longer mandatory to have a rootdg. Therefore you
can use SVM for the rootmirror and VxVM4.x for the shared devices (this
removes the complexity of VxVM encapsulation).
VxVM 4.1 onwards: Ensure that at least 1.1 GB free space is available in the
root filesystem (for running the installer).
Install VxVM packages. With VxVM 4.1 use the installer from the
storage_foundation or installvm script from Veritas Volume Manager
directory.).
• Install: VRTSvlic VRTSvxvm VRTSvmman
• Optional for 4.x: VRTSvmdoc VRTSob VRTSvmpro VRTSfspro VRTSobgui
VRTSmuob VRTSalloc VRTSddlpr
Patch from the EIS-DVD. From EIS-DVD: /sun/patch/veritas

Logout & back in to pick up VxVM Alternative: . /.profile

binary paths.
Apply VxVM license. # vxlicinst -k <license key>

Consider disabling hot relocation. Infodoc: 17840

Modify file /etc/init.d/vxvm-recover to disable Method (6) in the Infodoc.
vxrelocd & enable vxsparecheck.
Encapsulate boot disk using sequence This procedure does exactly what
below. vxinstall and vxdiskadm would do, but
is preferred as it requires less user
interaction and is more easily scripted. In
both cases you will still need to follow
the vxmksdpart step.
Encapsulate: With VxVM 4.x it is no longer
# vxconfigd -r reset -m disable mandatory to have the rootdisk in rootdg.
# vxdctl init Substitute the name of the diskgroup
# vxdctl enable which will contain the rootdisk for
# rm /etc/vx/reconfig.d/state.d/install-db <vxvm_bootdg>.
# vxencap -g <vxvm_bootdg> -c
rootdisk=<cxtxdx>
# shutdown -i6 -g0 -y
Initialise the rootmirror disk:
# vxdisksetup -i <cxtxdx>
Add the disk to the diskgroup containing the boot disk:
# vxdg -g <vxvm_bootdg> adddisk rootmirror=<cxtxdxs2>
Mirror the boot disk:
# vxmirror -g <vxvm_bootdg> rootdisk rootmirror

Sun Internal and Approved Partners Only Page 20 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
Ensure that there are underlying partitions on the rootmirror.
Use vxmksdpart to create the underlying partitions on the rootmirror disk
where they are not already present. The rootvol will already have a
partition but it may be necessary to create partitions for the remaining
volumes that have been mirrored onto the rootmirror disk. Ensure that you
use the correct slice number and appropriate 'tag' and 'flag' values. e.g. For
/export on the rootmirror disk that uses a sub-disk rootmirror-04, partition 6
could be created using;
# vxmksdpart -g <vxvm_bootdg> rootmirror-04 6 0x00 0x00
See Internal InfoDoc 74898 for a explanation on using vxmksdpart and
prtvtoc(1m) for the list of valid tags and flags.
Solaris Volume Manager SVM (SDS)
If required: install SDS + patch.
If required edit the file Not required for Solaris 10 because
/kernel/drv/md.conf and change the newdevices will be created dynamically
"nmd" field from nmd=128 to whatever SunSolve FAQ 2085 / Item 9
amount is needed (e.g. 255). Then boot -r to build the new devices.
Not required for Solaris 10 because
newdevices will be created dynamically
Mirror the system disk. SDS: Infodoc 28196
SDS templates: .../sun/tools/MISC/SDS
Update /etc/vfstab
Update dump device. dumpadm

Consider installing the metacheck On EIS-DVD under

script & activate via CRON. ...sun/tools/MISC/SDS

Task Comment Server

1 2
COMMON ACTIONS
Set boot-device & diag-device to both Suggested naming convention:
sides of the mirror. See Infodoc 11854. • Primary: rootdisk
If NVRAM editor (nvedit) was used • Secondary: rootmirror
ensure to setenv use-nvramrc? true
Test booting using the new aliases.

Sun Internal and Approved Partners Only Page 21 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
SET UP HW MIRRORING ON BOOT DISKS ON SUN FIRE V440
V440 only (see NOTE below): Example:
/usr/sbin/raidctl -c c1t0d0 c1t1d0
where c1t0d0 is the primary disk & c1t1d0 the secondary.
NOTE: The onboard hardware RAID 1 functionality of the SunFire V440
works with Sun Cluster 3.x provided that Solaris 9 or 10 patches are
installed from the EIS-DVD. No current support with Solaris 8.
SET UP HW MIRRORING ON BOOT DISKS ON SUN FIRE V215/245/445

Placeholder – more to come

Sun Internal and Approved Partners Only Page 22 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
SYSTEM CONFIGURATION
If VxFS is required install the packages. VxFS version 4.0 or higher assumed.
VxFS: Patch from EIS-DVD as ../sun/patch/veritas/<Vn>
required.
VxFS: Install license
If PowerPath or other product requiring See SRDB 42768.
extra stack space is installed correct the E.g. For PowerPath change:
lwp_default_stksize=0x4000
entry in /etc/system after VxFS to:
installation. lwp_default_stksize=0x6000

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 SunCS ARS/DCRS or SunSS ArrayStart
purchased).
Update /etc/vfstab as required. Consider enabling filesystem logging (default
with Solaris 9 09/04 onwards).
These are particularly applicable to those
Verify/set the NVRAM parameters for
servers that support Automatic System
production (OBP prior to v4.15.1):
Recovery (ASR) e.g. V880, V480,
eeprom diag-device=<boot device> V440...
eeprom diag-switch?=true Customer should be aware of
eeprom diag-level=max implications of ASR in particular
eeprom auto-boot?=true regarding boot times.
eeprom auto-boot-on-error?=true
eeprom post-trigger=all-resets Many settings apply to all servers.
eeprom obdiag-trigger=all-resets
PTS recommends the Diag-ON default settings for This is for systems
normal mode with v4.15.1 and later: with OBP V4.15.1
(Diag-ON) or higher.
eeprom diag-device=<boot device>
eeprom diag-switch?=false Examples. V490 &
eeprom diag-script=normal V890.
eeprom diag-level=max
eeprom verbosity=normal
eeprom service-mode?=false
eeprom diag-trigger=”power-on-reset error-reset” See FIN# I1070-1 (as
eeprom auto-boot?=true on page 9 of this
eeprom auto-boot-on-error?=true checklist).
eeprom error-reset-recovery=sync

Verify/set the NVRAM parameter for This way if the system hangs the
production: watchdog timer will time out and perform
eeprom error-reset-recovery=sync an "XIR" bringing the system to the OK>
prompt. Then the "error-reset-recovery"
Ensure following entry in /etc/system: will take over and allow a core file to be
set watchdog_enable=1 taken.
Verify/set the NVRAM parameters for If the OBP supports this variable e.g.
production: V100/V120.

eeprom watchdog-reboot?=true

Sun Internal and Approved Partners Only Page 23 of 26 Vn 1.49 Created: 22. Feb. 2007
 Task
Verify/set the NVRAM parameters for
production:
eeprom use-nvramrc?=true
As appropriate: touch /etc/notrouter
Set up /etc/defaultrouter according to
customer requirements.
Configure additional network interfaces. Ensure appropriate network patches are
Sun's recommendation is to leave
Ethernet auto-negotiation ON for
interfaces and switches (default).
If the customer environment requires "forced"
network settings use bundled driver.conf file,
ce.conf template or (if no driver.conf file)
adapt template for /etc/init.d/S68net-tune and
create link to /etc/rc2.d.
Install the CPU Diagnostics Monitor.
See Sun Alert 101256.
Consider disabling remote root logins
(if enabled).
Consider setting the OBP password:
eeprom security-mode=command
Changing PROM password:
New password: <enter here>
Retype new password: <repeat>
Reboot =>everything OK?
Sun Internal and Approved Partners Only Page 24 of 26
Comment Server
1 2
If NVRAM editor (nvedit) was used to
create boot aliases etc.
Solaris 9 & before only; with Solaris 10
onwards the default is routing disabled.
installed:
.../sun/patch/network
Normally you should NOT require this
task – defaults usually suffice!
If required, search for bundled
driver.conf files, e.g.:
find /kernel /platform -name bge.conf
find /kernel /platform -name e1000g.conf
Template for ce.conf & S68net-tune
available on:
EIS-DVD: .../sun/tools/network
EIS-ALERT#61
EIS-DVD: .../sun/tools/CDM
UltraSPARC-III & IV & IV+!
In /etc/default/login
See CONSOLE.
Suggested to improve security.
NOTE: Since the system can always be
booted the root user can always reset the
OBP password without knowing the old
one.
Vn 1.49 Created: 22. Feb. 2007
 Task Comment Server
1 2
EXPLORER (INSTINFO) & VERIFICATION
Run explorer with the instinfo option. explorer -i

Run Griffon (from EIS-DVD) locally cd /cdrom/.../sun/tools

cd Griffon
to analyse the explorer output file. sh run-griffon.sh
Examine the results. Examine the resulting report:
If necessary repair & repeat more /tmp/griffon_report.txt
explorer/Griffon sequence.
Mail explorer file to:
EMEA: explorer-database-emea@sun.com
APAC: explorer-database-apac@sun.com
AMER: explorer-database-americas@sun.com
The explorer output file is normally in directory /opt/SUNWexplo/output with filename
explorer.<hostid>.<hostname>-<date>.tar.gz
If e-mail from customer site not possible please transport file to your office & send the e-
mail from there.
Level 0 backup of system disk. To tape, filesystem or other system.

Task Comment Server

1 2
HANDOVER
Short briefing: the configuration.
Perform acceptance tests: If WINGS was used to plan the
• Boot system from primary disk. installation perform installation
verification tests as described in the
• Force system panic5.
WINGS “Server Tests” document(s).
• Boot system (from secondary mirror
if present). If WINGS was not used, the actions on
• Confirm crashdump was collected the left are to be followed.
successfully (then remove the dump).
• Disk access check.
• Network Access Check.

Short briefing: procedure for opening Hand over telephone number for
calls. warranty customers.

If temporary licenses have been Temporary licenses should only have

installed then draw customer's attention been installed if customer can provide
proper proof of purchase.
to this fact!
Complete documentation and hand over WINGS
to customer.
Obtain customer sign-off. WINGS

5 If graphics head is attached issue STOP-A otherwise use send [break].

Then at OBP: ok> sync

Sun Internal and Approved Partners Only Page 25 of 26 Vn 1.49 Created: 22. Feb. 2007
APPENDIX A – Example Dialogue from setupsc Command (ALOM 1.6)
This example is from the dialogue when running the setupsc command on a V240
server after the ALOM had been upgraded from version 1.5.3 to 1.6.
sc> setupsc
Entering Interactive setup mode. To exit and discard changes to that point, use Ctrl-C or to exit and
save changes to that point, use Ctrl-Z.
Do you wish to configure the enabled interfaces [y]? y
Should the SC network interface be enabled [n]? n
Should the SC interface connection type be set [telnet]? telnet
Do you wish to configure the network interface [y]? y
Should the SC use DHCP to obtain its network configuration [n]? n
Enter the SC IP address [100.100.100.100]? 100.100.100.100
Enter the SC IP netmask [255.255.255.0]? 255.255.255.0
Enter the SC IP gateway address [100.100.100.100]? 100.100.100.100
Should the TPE link test be enabled [y]? y
Do you wish to configure the managed system interface [y]? y
What level of SC events should be reported to the managed system where valid settings are 0 (none),
1 (critical), 2 (critical and major) and 3 (critical, major and minor) [2]? 2
What action should the SC invoke if the OS is hung. The available options are 'none', 'xir' or 'reset'
where an xir will attempt to collect diagnosis data before invoking a reset [xir]? xir
How many seconds should be allowed for an XIR to complete (maximum timeout of 10800s) [900]?
900
Do you wish to configure the network management interfaces [y]? y
Enter the number of mail servers to configure [0]? 0
Do you wish to configure the SC parameters [y]? y
Enter any customer data for this platform (maximum of 40 characters) []?
Enter the console session escape sequence (2 characters). The first character can be any printable
characters or control-A through control-Y except for control-C, control-D, control-H, control-J, or
control-M. The second character must be a ".". [#.]? #.
Enter level of events to be displayed over the CLI where valid settings are 0 (none), 1 (critical), 2
(critical and major) and 3 (critical, major and minor) [2]? 2
Should powerstate memory be enabled [y]? y
Should poweron sequencing be enabled [y]? y
Enter the SC cli prompt (maximum of 16 characters) [sc]? sc
Enter the SC CLI timeout in seconds (maximum of 10000s) [0]? 0
Should password entry echo '*'s [y]? y
Your ALOM configuration profile has been successfully completed. To activate your network
configuration, please reset the SC.
sc>

Copies of the checklists are available under http://EIS/checklists or on the EIS-DVD.

Comments & RFEs are welcome. Please use ServiceDesk (Search Problem/Service & enter "EIS")
or mail to EIS-DESK@sun.com if no SWAN access available – typically for a partner.

Sun Internal and Approved Partners Only Page 26 of 26 Vn 1.49 Created: 22. Feb. 2007