EIS Installation Checklist for Fujitsu M10 Servers 1

M10-1 / M10-4 / M10-4S

Customer:
Task Number:
Technician:
Version EIS-DVD:
Date:

• It is recommend that the EIS web pages are checked for the latest version of this checklist prior
to commencing the installation.
• It is assumed that the installation is carried out with the help of the current
EIS-DVD. See EIS web pages for current information and status.
• 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.
• For platform minimum Solaris requirements refer to table on page 28.
• For systems to be rack mounted the racks must be as defined in the system handbook for the
appropriate server.
• It is not intended that this checklist be handed over to the customer.
• Feedback is welcome – refer to the last page of this checklist.

The following additional EIS Installation Checklists will be required:

• Solaris 10 OS OR
• Solaris 11 OS,

Athena+ Processors
Starting April 2014, Fujitsu M10 Servers are delivered with new processors that have higher
speeds and some additional instructions. This only affects installation in the case of M10-4S with
mixed CPU configuration, see later in this document. The minimum firmware for these new
systems is XCP 2210.
Starting April 2015, Fujitsu M10-1 and M10-4 (not M10-4S!) can be ordered with 8 cores
SPARC64 X+ 3.7 GHz processors. In this case the minimum firmware is XCP 2250.

Unit as Appropriate (Master XSCF) Serial#

M10-1: S/N of unit
M10-4: S/N of unit
M10-4S (2 to 4 BBs): S/N of BB#00
M10-4S (5 to 16 BBs): S/N of XBBOX#80

1 Whilst Oracle refers to the Fujitsu M10 servers, Fujitsu call it the SPARC M10. Hence both terms will be met in
the marketing / service documentation.

Oracle Internal and Approved Partners Only Page 1 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

PREPARATION
For an overview of the activities carried out during the installation of this product via the
EIS Methodology, refer to the EIS-Deliverables page within the EIS website for the
Fujitsu M10-1, M10-4 & M10-4S Servers.
M10 documentation reviewed? It is important to review the product notes for the
http://docs.oracle.com/cd/E38160_01/ firmware version to be installed.
Current firmware is XCP 2353.
Note: All manuals listed below can be found See the Fujitsu M10 Series Documentation, select
under this location, please navigate to the one of the Fujitsu M10* User Manuals and
required documents. within that the Fujitsu M10/SPARC M10 Systems
Product Notes (XCP version 2353).
Installation planning. Read:
1. SPARC M10 Systems/SPARC Enterprise/PRIMEQUEST: COMMON INSTALLATION
PLANNING MANUAL
2. Specific SPARC M10 System Installation Guide. (M10-1 / M10-4 / M10-4S)
EIS Site-Audit Report complete? EISdoc V4:
File EIS-SiteAudit-Racked-Item.odt
EIS Installation Configuration Plan & Test EISdoc V4:
Procedures Plan complete? Use appropriate BUILD & TPP templates,
inserted into “Master” files (Chapter Servers):
EIS-BUILD-Server-FJM10.odt
EIS-TPP-Server-FJM10.odt
It is wise to ensure that the required system firmware update is available before
commencing the installation. It will be required for the actions on page 15 of this
checklist. You can also refer to MOS Document ID 1554086.1 (there may be a delay in
updating).
The system firmware updates can either found on EIS-DVD-ONE2 in directory
.../sun/patch/SYSFW/FJM10 or obtained from MOS:
1. Go to https://support.oracle.com/ & sign in,
2. Click on the Patches & Updates tab (on the top),
3. In the Patch Search box on the right side, click on Product or Family (Advanced)
4. There are 2 required fields:
• Product: select the correct product (currently the patch contents are identical):
Fujitsu M10-1, Fujitsu M10-4, Fujitsu M10-4S
• Release: select the latest3 version eg M10 XCP2360.
5. Click Search.
6. A new screen will appear with the Patch Search Results. Click on the Patch Name for
the SPARC M10 XCP20xx FIRMWARE which will be of the form 29494268.
7. Download the file – currently 102.6 MB in size.
8. The result will be a file of the form: p30061936_236000_Generic.zip. Unzipping
will produce a number of files; the firmware filename will be of the form:
BBXCP2360.tar.gz

2 XCP 2360 is on EIS-DVD ≥26SEP19; XCP 2353 is on EIS-DVD ≥25APR19.

3 The latest version is not necessarily at the end of the list!

Oracle Internal and Approved Partners Only Page 2 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
If PCI Expansion Box(es) will be installed, ensure that you have the required firmware
update available (required for actions on page 23).
File PCIBOX1310.tar.gz is on EIS-DVD-ONE ≥07DEC164 in the same directory as the
XCP: .../sun/patch/SYSFW/FJM10.
Do NOT use PCI Expansion Box firmware prior to 1130 – see EIS-ALERT #291.
If the required update is not available via the EIS-DVD, download the firmware from
MOS the same way as described for XCP on page 2. Select Fujitsu M10 PCI Expansion
Unit → PCIBOX XCP 1310.
FABs/EIS-ALERTs reviewed?
If name service (DNS, NIS...) used, ensure that
new hostnames, IP addresses etc. are correct on
name server.
The SPARC M10 Systems Installation Guide. Have this document available for on-site work.

Decide on PPAR installation method: 1. Use the pre-installed boot disk.

2. Install over network
3. Install from connected USB-DVD drive.
Double check that all conditions will be met to 1. Cooling,
start the installation. 2. Sufficient room for service,
3. Sufficient power,
4. Serial console connection,
5. XSCF admin Network connections,
6. PPAR network connections.

4 PCIBOX1310.tar.gz is on EIS-DVD 30MAY18.

Oracle Internal and Approved Partners Only Page 3 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

UNPACKING
Delivery complete?
Check for damage of the packaging. Report problems to local logistics.

Collect the provided system records. File away carefully!

Allow the system to acclimatise (power off) at Refer to EIS standard “Acclimatisation of Sun
the customer site. Servers & Storage”.
Collect packing material together for disposal.
Unpack outside data center to ensure no
contamination/dust is released inside
customer's controlled environment.
Verify all packing material has been removed, Fans & air vents must be free to operate.
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.

Verify adequate maintenance areas around the SPARC M10 Systems Installation Guide Chapter
system and proper placement of perforated 2.
floor tiles in raised floor data centers.
PREPARE ASSEMBLY/CABLING
Have the required documents ready. M10-1 or M10-4 or M10-4S Installation Guide
and
Installation guides and service manuals are SPARC M10-1 Service Manual
specific for M10-1, M10-4, M10-4S or
SPARC M10-4 / M10-4S Service Manual
and
PCI Expansion Unit for SPARC M10 Systems
Service Manual (if used).
Verify placement w.r.t. airflow & location of Fujitsu SPARC M10 requires airflow front to
air vents. back.

Environment Measurements: Verify that conditions are met.

• Temperature:.................C(F) SPARC M10 Systems Installation Guide Chapter
• Humidity:.......................% 2.5

Oracle Internal and Approved Partners Only Page 4 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

HARDWARE INSTALLATION & CABLING

The hardware installation steps are different depending on the type and number of Building
Blocks (BB), the use of Crossbar Boxes and the number of racks.
System with Crossbar Boxes (those with more than 4 BB) are delivered installed and wired in
racks. The others must be installed in racks and wired on-site.
Do not connect the power cables inside the rack(s) until that step is reached.
Ensure that customer provided racks are grounded at this time.
The following steps must be done AFTER Solaris is installed:
• Installation of third party HBAs.
• Connection of external SAS devices.
• Connection of external storage.
Use only one of the following sections of this table.
M10-1:
Install optional memory, follow configuration SPARC M10-1 Service Manual, Chapter 2.2.1
rules.
Install M10-1 into approved rack. SPARC M10-1
Installation Guide, Chapter 2.4, 3.4.1
Install M10 PCI expansion unit(s) (if any) into
SPARC M10-1
approved rack. Installation Guide, Chapter 2.4, 3.4.2
Install optional internal disks. SPARC M10-1 Service Manual, Chap 9

Install optional internal PCIe cards. SPARC M10-1 Service Manual, Chap 8
Strictly adhere to the I/O board configuration
provided in the EIS Installation Configuration
Plan.
Install optional PCI expansion components: PCI Expansion Unit for SPARC M10
Systems Service Manual:
Install PCIe cards.
Chapter 8
Install Link Card in M10-1.
Chapter 10
Connect the serial XSCF console cable. SPARC M10-1 Installation Guide, Chapter 4.1

Connect the XSCF LAN cables.

Connect the GbE LAN cables.
Install power cables.
Connect cables to the PCI Expansion Unit (if SPARC M10-1 Installation Guide
any) Installation Guide, Chapter 4.2

Slide the mode switch to “Service”.

Go to next table (Power Up). Page 9.

M10-4 OR M10-4S AS SINGLE UNIT:

Install optional memory, follow configuration SPARC M10-4/M10-4S Service Manual, Chapter
rules. 2.2.1

Oracle Internal and Approved Partners Only Page 5 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Install M10-4 into approved rack. SPARC M10-4 / SPARC M10-4S
Installation Guide, Chapter 2.4, 3.3.1
Install M10 PCI expansion unit(s) (if any) into
SPARC M10-4 / SPARC M10-4S
approved rack. Installation Guide, Chapter 2.4, 3.3.2
M10-4S only: set BB-ID switch to 00. SPARC M10-4S Installation Guide, Chapter 4.1

Install optional internal disks. SPARC M10-4/M10-4S Service Manual, Chapter

10
Install optional internal PCIe cards. SPARC M10-4/M10-4S Service Manual, Chapter
Strictly adhere to the I/O board configuration 8
provided in the EIS Installation Configuration
Plan.
Install optional PCI expansion (if any) PCI Expansion Unit for SPARC M10
components: Systems Service Manual:
Install PCIe cards. Chapter 8
Install Link Card in M10-1. Chapter 10
Connect the serial XSCF console cable. SPARC M10-4
Installation Guide, Chapter 4.1
Connect the XSCF LAN cables.
SPARC M10-4S
Connect the GbE LAN cables. Installation Guide, Chapter 5.1

Install power cables.

Connect cables to the PCI Expansion Unit (if SPARC M10-4
any) Installation Guide, Chapter 4.2
SPARC M10-4S
Installation Guide, Chapter 5.2
Slide the mode switch to “Service”.
Go to next table (Power Up). Page 9.

M10-4S UP TO 4 BB (WITHOUT CROSSBAR BOXES)

Install optional memory, in all BBs, follow SPARC M10-4/M10-4S Service Manual, Chapter
configuration rules. 2.2.1

Install all M10-4S into approved rack. SPARC M10-4S

Installation Guide, Chapter 2.4, 3.4.1
Install M10 PCI expansion unit(s) (if any) into
SPARC M10-4S
approved rack. Installation Guide, Chapter 2.4, 3.4.2
set BB-ID switches as follows: SPARC M10-4S Installation Guide, Chapter 4.1
Lowest BB in rack: 00
2nd lowest BB in rack: 01
3td lowest BB in rack: 02
4th lowest BB in rack: 03
Connect the XSCF interconnect cables. SPARC M10-4S Installation Guide, Chapter 4.2.1

Connect the crossbar cables. SPARC M10-4S Installation Guide, Chapter 4.2.2
Verify that they are completely inserted. + Appendix B

Install the Dual Cable between BB#0 and SPARC M10-4S Installation Guide, Chapter 4.2.2
BB#1. + Appendix B

Oracle Internal and Approved Partners Only Page 6 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Install optional internal disks. SPARC M10-4/M10-4S Service Manual, Chapter
10
Install optional internal PCIe cards. SPARC M10-4/M10-4S Service Manual, Chapter
Strictly adhere to the I/O board configuration 8
provided in the EIS Installation Configuration
Plan.
Install optional PCI expansion (if any) PCI Expansion Unit for SPARC M10
components: Systems Service Manual:
Install PCIe cards. Chapter 8
Install Link Card in M10-1. Chapter 10
Connect the serial XSCF console cable to SPARC M10-4S
BB#00. Optionally install a second console Installation Guide, Chapter 5.1
cable to BB#1.
Connect the XSCF LAN cables to BB#00 and
BB#01.
Connect the GbE LAN cables.
Follow the EIS Installation Configuration Plan
provided.
Install power cables.
Connect cables to the PCI Expansion Unit (if SPARC M10-4S
any) Installation Guide, Chapter 5.2

Slide all mode switches to “Service”.

Go to next table (Power Up). Page 9.

PRE-INSTALLED M10-4S IN 1 OR 2 RACKS

(5 to 16 BB with Crossbar Boxes)
Remove all power plugs to BBs, Crossbar Nothing should power up when the rack gets
Boxes, PCI extensions inside pre-installed power in the next steps.
rack(s).
Make sure the rack power cables are not
connected to the facility outlets at this time
(wall sockets).

Install rack power cables under the right side SPARC M10-4S
panels of the racks. Installation Guide, Chapter 3.3.1

SPARC M10-4S
Secure the rack(s). Installation Guide, Chapter 3.3.2

Mechanically join racks (if dual racks). SPARC M10-4S

Installation Guide, Chapter 3.3.3
Connect power to the racks(s). SPARC M10-4S Installation Guide, Chapter 2.8.
A dual power feed configuration is preferable. This will ground the rack for ESD purposes.
Install optional memory, in all BBs, follow SPARC M10-4/M10-4S Service Manual, Chapter
configuration rules. 2.2.1.

Oracle Internal and Approved Partners Only Page 7 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Install M10 PCI expansion unit(s) (if any) into SPARC M10-4S Installation Guide, Chapter 2.4,
approved rack. 3.4.2

Verify the BB-ID switches in left (or single) SPARC M10-4S Installation Guide, Chapter 4.1
rack:
Bottom BB: 00 .. Top BB: 07
Lower XB-BOX: 80
Upper XB-BOX: 81
Verify the BB-ID switches in right rack (if SPARC M10-4/M10-4S Service Manual, Chapter
present): 4.1.
Bottom BB: 08 .. Top BB: 15
Lower XB-BOX: 82
Upper XB-BOX: 83
Connect the XSCF interconnect cables (if 2 SPARC M10-4S Systems
racks configuration). Installation Guide, Chapter 4.3.1, Appendix B.5

Connect the crossbar cables between racks (if SPARC M10-4S Installation Guide, Chapter
2 racks configuration). 4.3.2, Appendix B.5
The cables come attached to the right rack.
Match port numbers and colours on cable
labels with ports in left rack.
Install optional internal disks. SPARC M10-4/M10-4S Service Manual, Chapter
10.
Install optional internal PCIe cards. SPARC M10-4/M10-4S Service Manual, Chapter
Strictly adhere to the I/O board configuration 8.
provided in the EIS Installation Configuration
Plan.
Install optional PCI expansion (if any) PCI Expansion Unit for SPARC M10
components: Systems Service Manual:
Install PCIe cards. Chapter 8
Chapter 10
Install Link Card in M10-1.
Connect the serial XSCF console cable to SPARC M10-4S Installation Guide, Chapter 5.3
BB#80. Optionally install a second console
cable to BB#81.
Connect the XSCF LAN cables to BB#80 and
BB#81.
Connect the GbE LAN cables.
Follow the EIS Installation Configuration Plan
provided.
Install power cables
Connect cables to the PCI Expansion Unit (if SPARC M10-4S Installation Guide, Chapter 5.2
any)
Slide all mode switches to “Service”.
Go to next table (power up). Page 9.

Oracle Internal and Approved Partners Only Page 8 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

POWER-UP
Open a serial connection to the Master XSCF. 9600bps/8/bits/no parity/1 stop bit/no flow
control
• For 1 - 4 BB configuration BB#00 will be
the Master.
• For configurations with XB-BOXes
XBBOX#80 will be the Master.
Plug power to XB-BOX #80 first. For configurations with XB-BOXes.

Plug power to BB #00 first. For configurations with 1-4 BB.

Plug power to the rest of the components in the Do this step immediately after the above.
rack(s).
Observe XSCF boot sequence on the serial The ready light on the XSCF should flash during
connection. the boot sequence, this will last for about 15
minutes!
Wait for the login prompt. The ready light on the XSCF should be steady at
this time and the master LED should be lit. If the
Master LED is lit on another BB or XB-BOX, re-
connect the serial port to that unit.

Oracle Internal and Approved Partners Only Page 9 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

INITIAL SERVICE PROCESSOR (XSCF) LOGIN, HW STATUS CHECK

AND USER CREATION
Detailed instructions for the following steps are given in the SPARC M10 Systems System
Operation and Administration Guide and Product Notes for XCP. There is no help command on
the XSCF, however you can press the TAB key twice to see the commands that are available to
you.
Manual pages are available e.g.: man adduser
Perform all the following steps on the master XSCF only.
1 to 4 BB: Master: BB#0, Standby: BB#1
5 to 16 BB: Master: XBBOX#80, Standby: XBBOX#81
All changes are automatically propagated to the standby and slave XSCFs (on multi BB configs).
At this time you should have a login prompt at the serial console of the master XSCF
(established on previous page).
Log in as user default. This can only be done login: default
when connected via a serial cable as described There is no password.
on previous page.
Move the mode switch on the master XSCF as The XSCF> shell prompt should appear.
prompted, follow instructions.
Alternately, log in as user admin. This will login: admin
only be possible if the system is fresh from the There is no password.
factory (no user created) but has the advantage
that the system can be set up remotely without
the need to move the mode switch. The XSCF> shell prompt should appear.

Change the password policy if desired. XSCF> showpasswordpolicy

XSCF> setpasswordpolicy

Create users5. XSCF> adduser eis-installer

XSCF> adduser <fieldeng-name>

Give users the appropriate privileges. Note that the privileges should given all at once,
you cannot add more privileges to existing ones.
XSCF> setprivileges eis-installer platadm useradm auditadm fieldeng mode
XSCF> setprivileges fieldeng fieldeng mode
etc..
Set passwords for the user accounts. XSCF> password eis-installer
XSCF> password <fieldeng-name>
You will be prompted for the passwords. etc..
Exit and login as user eis-installer. XSCF> exit
logout
login: eis-installer

Verify user settings. XSCF> showuser -l

5 The TSC lead engineers for these systems recommend that every SSE/FE should have their own account and
password. That way we can audit who does what. It is a security mistake to have a single Oracle-wide fieldeng
account. Each customer/site needs to establish the policy that fits their security goals. There is never a problem
logging in when you have physical access and can move the mode switch. You can login as default and set the
password as needed.

Oracle Internal and Approved Partners Only Page 10 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Verify the hardware configuration – this will XSCF> showhardconf -u
list all the hardware so that you can verify that
the system is delivered as expected.
Verify the status of all hardware. Investigate XSCF> showhardconf -M
any status other than “normal”. XSCF> showlogs -v error

Change autologout time (if desired) EIS recommends using the default value, but if
Default is 10 minutes, can be set between 1 you have to change:
and 255 minutes. The change is effective after XSCF> setautologout -s 60
XSCF> showautologout
re-login.

Oracle Internal and Approved Partners Only Page 11 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

MANDATORY XSCFU CONFIGURATION

All the following sections are mandatory unless otherwise specified.
In the following steps, we use these example values for IP addresses:
192.168.10.0: admin network 0
192.168.11.0: admin network 1 (optional but recommended)
169.254.1.0: Default SSCP network (XSCF-XSCF-BB)
192.168.10.1: Default gateway for admin network 0
192.168.11.1: Default gateway for admin network 1
10.20.30.1: Primary NTP server
10.20.40.1: Secondary NTP server
10.20.50.1: Primary Name Server
10.20.60.1: Secondary Name Server
Note: Admin network 0, Admin network 1 and the SSCP network must be 3 different
subnets.
Note: All ports on switches connecting to the XSCFU must be set to “autonegotiate”.
To avoid unnecessary waiting time, do not reboot the XSCF when prompted by the
various commands.
The XSCF will be rebooted at the end of the procedure, this will activate all previously
made settings.
login: eis-installer

Remove all already set up networks and routes.

XSCF> showroute -a
XSCF> setnetwork -r bb#00-lan#0
XSCF> setnetwork -r bb#00-lan#1

etc... remove all LANs that appear in the showroute output.

Note: The SSCP network is automatically configured with network 169.254.1.0.
Unless this subnet is used by the admin networks there is no need to change it. If this
needs to be changed, use:
XSCF> showsscp
XSCF> setsscp
CONFIGURATION OF ADMIN NETWORK(S) FOR SINGLE BB
Admin network 0:
XSCF> setnetwork bb#00-lan#0 -m 255.255.255.0 192.168.10.10
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.10.1 bb#00-lan#0

Admin network 1, optional recommended for redundancy:

XSCF> setnetwork bb#00-lan#1 -m 255.255.255.0 192.168.11.10
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.11.1 bb#00-lan#1

Set hostname and domain name:

XSCF> sethostname bb#00 scf0-hostname
XSCF> sethostname -d company.com

Continued on next page

Oracle Internal and Approved Partners Only Page 12 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Configuration of admin network(s) for 2 to 4 BB (no XB-BOX)
Admin network 0:
XSCF> setnetwork bb#00-lan#0 -m 255.255.255.0 192.168.10.11
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.10.1 bb#00-lan#0
XSCF> setnetwork bb#01-lan#0 -m 255.255.255.0 192.168.10.12
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.10.1 bb#01-lan#0
XSCF> setnetwork lan#0 -m 255.255.255.0 192.168.10.10

Admin network 1, optional recommended for redundancy:

XSCF> setnetwork bb#00-lan#1 -m 255.255.255.0 192.168.11.11
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.11.1 bb#00-lan#1
XSCF> setnetwork bb#01-lan#1 -m 255.255.255.0 192.168.11.12
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.11.1 bb#01-lan#1
XSCF> setnetwork lan#1 -m 255.255.255.0 192.168.11.10

Set hostnames and domain name:

XSCF> sethostname bb#00 scf0-hostname
XSCF> sethostname bb#01 scf1-hostname
XSCF> sethostname -d company.com

Configuration of Admin Network(s) for 5 to 16 BB (with XB-BOX)

Admin network 0:
XSCF> setnetwork xbbox#80-lan#0 -m 255.255.255.0 192.168.10.11
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.10.1 xbbox#80-lan#0
XSCF> setnetwork xbbox#81-lan#0 -m 255.255.255.0 192.168.10.12
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.10.1 xbbox#81-lan#0
XSCF> setnetwork lan#0 -m 255.255.255.0 192.168.10.10

Admin network 1, optional recommended for redundancy:

XSCF> setnetwork xbbox#80-lan#1 -m 255.255.255.0 192.168.11.11
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.11.1 xbbox#80-lan#1
XSCF> setnetwork xbbox#81-lan#1 -m 255.255.255.0 192.168.11.12
XSCF> setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g 192.168.11.1 xbbox#81-lan#1
XSCF> setnetwork lan#1 -m 255.255.255.0 192.168.11.10

Set hostnames and domain name:

XSCF> sethostname xbbox#80 scf0-hostname
XSCF> sethostname xbbox#81 scf1-hostname
XSCF> sethostname -d company.com

NAME SERVICE SET UP (RECOMMENDED)

DNS server(s) are not mandatory. Some commands may not work properly without DNS
being set up, therefore it is highly recommended to set up DNS.
XSCF> setnameserver -c del -a
XSCF> setnameserver -c add 10.20.50.1 10.20.60.1

XSCF IP PACKET FILTERING SET UP (OPTIONAL)

Some sites may require to filter incoming packets.
XSCF> man setpacketfilters

NETWORK TIME PROTOCOL (NTP) SET UP (RECOMMENDED)

XSCF> setntp -c del -a
XSCF> setntp -c add 10.20.30.1 10.20.40.1
XSCF> setntp -s client -c enable

Oracle Internal and Approved Partners Only Page 13 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
SSH SETUP
Allows secure access to the XSCFU via the admin network.
XSCF> setssh -q -y -c enable
XSCF> setssh -c genhostkey -q -y
XSCF> man setssh (for more security options)

CONFIGURE E-MAIL REPORT

Recommended, allows immediate warning when a problem occurs.
XSCF> setsmtp
Mail Server []: <ip_address_of_mail_server>
Port [25]:
Authentication Mechanism [none]:
Reply Address []: [email protected]
XSCF> setemailreport
Enable E-Mail Reporting? [no]: yes
E-mail Recipient Address []: [email protected]
Do you want to send a test mail now [no]? No

APPLY THE NETWORK SETUP

XSCF> applynetwork

Review all the displayed settings at this stage.

Continue? [y|n] :y

SET THE ALTITUDE

The altitude must be set to ensure that the internal temperature limits and fan speeds are
set according to the air density.
XSCF> setaltitude -s altitude=500
In this example, the altitude is set to 500 meters above sea level.
SET THE TIMEZONE
XSCF> settimezone -c settz -a to get a list of time zones
XSCF> settimezone -c settz -s Europe/Paris (example)
XSCF> man settimezone to get more options like summer time etc..
XSCF> setservicetag -c enable Enables the servicetag agents.

If ntp was not configured, then you need to set the date now.
XSCF> setdate -s YYYY.MM.DD-hh:mm:ss
XSCF reboots (takes about 5 minutes).
XSCF> rebootxscf -a Only required if setdate was not performed in the
previous step.

Oracle Internal and Approved Partners Only Page 14 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

VERIFY / UPGRADE THE XSCF FIRMWARE

The XCP product notes detail the upgrade procedures:
Fujitsu M10/SPARC M10 Systems Product Notes (XCP version 2353) – to be found within any
of the Fujitsu M10 User Manuals.
Login as user eis-installer on admin network ssh eis-installer@ 192.168.10.10
[email protected]'s
0. The admin network should work at this password: password
time. XSCF>
Otherwise use the serial connection.
Determine the installed firmware version – XSCF> version -c xcp
XSCF#0 (Active )
2041 is displayed. BB#00-XSCF#0 (Master)
Current build version is 2353. If an upgrade is XCP0 (Current): 2041
XCP1 (Reserve): 2041
not required, skip the update sequence. BB#01-XSCF#0 (Standby)
XCP0 (Current): 2041
XCP1 (Reserve): 2041

The system firmware updates for the Fujitsu M10 servers can either be found on EIS-
DVD-ONE in directory .../sun/patch/SYSFW/FJM10 or obtained from MOS. Refer to
page 2 of this checklist.
The getflashimage command downloads a firmware image file to the XSCFU for use by the
flashupdate command. There are many options – we describe 3 examples here (see the
manpage for further details). Only the USB method is available when the installed firmware is
below XCP 2050.
EXAMPLE 1 Downloading a Version from an http Server
XSCF> getflashimage -u <user> http://imageserver/images/BBXCP23xx.tar.gz
Note: The path is relative to the user’s home directory.

EXAMPLE 2 Downloading a Version from an FTP Server

XSCF> getflashimage -u <user> ftp://imageserver/images/BBXCP23xx.tar.gz
Note: The path is relative to the user’s home directory.

EXAMPLE 3 Downloading From a USB Memory Stick

First copy the firmware image file to a memory stick (must be placed into a top-level directory
images on the memory stick) then: insert the USB stick into the XSCF port marked “maintenance
only”
XSCF> getflashimage file:///media/usb_msd/images/BBXCP23xx.tar.gz

Alternatively: Download by using the BUI instead of using CLI command

Menu → XSCF → maintenance → firmware update → XCP Import → select file → upload
(https service required, see optional configuration page 19).
Verify the new firmware file:
XSCF> version -c xcp -t
XSCF> flashupdate -c check -m xcp -s 20xx
Now update the firmware:
XSCF> flashupdate -c update -m xcp -s 20xx
The flashupdate command (which includes a reboot) takes about 20 minutes. Even when
the reboot has completed the second half of the flash update is still completing. The
progress of flashupdate is shown on the console – await the final message:
Jun 04 10:37:28 v4u-m3000a-xscf0-0-usan10 XSCF flashupdate[561]: XCP update has
been completed (XCP version=20xx)

Oracle Internal and Approved Partners Only Page 15 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
1. If power is lost during flashupdate you may have a corrupt XSCF.
2. If connection to the console is lost during flashupdate, try a ssh to the XSCFU and
login as eis-installer. If update still in progress you will see:
flashupdate now in progress.
please wait for flashupdate complete.
3. Wait until XSCF firmware reaches the ready state. This can be confirmed when the
READY LED of the XSCF remains lit, or the message
XSCF Initialize complete appears on the serial console.
4. Log in on to XSCF using a serial connection or LAN connection.
Verify that both banks (current/reserve) on all On systems with XBBOX:
XSCF have the same version. • XBBOX#80-XSCF#0 (Master)
XSCF> version -c xcp • XBBOX#81-XSCF#0 (Standby)
Single BB:
BB#00-XSCF#0 (Master)
XCP0 (Current): 2353
XCP1 (Reserve): 2353
4 BB:
BB#00-XSCF#0 (Master)
XCP0 (Current): 2353
XCP1 (Reserve): 2353
BB#01-XSCF#0 (Standby)
XCP0 (Current): 2353
XCP1 (Reserve): 2353
BB#02-XSCF#0
XCP0 (Current): 2353
XCP1 (Reserve): 2353
BB#03-XSCF#0
XCP0 (Current): 2353
XCP1 (Reserve): 2353
More than 4BB:
XBBOX#80-XSCF#0 (Master)
XCP0 (Current): 2353
XCP1 (Reserve): 2353
XBBOX#81-XSCF#0 (Standby)
XCP0 (Current): 2353
XCP1 (Reserve): 2353
BB#00-XSCF#0
XCP0 (Reserve): 2353
XCP1 (Current): 2353
BB#01-XSCF#0
XCP0 (Reserve): 2353
XCP1 (Current): 2353
etc..

Oracle Internal and Approved Partners Only Page 16 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

CONFIGURE THE XSCF TO USE ASR

ASR is supported with XCP 2070 and later.
The EIS team has verified this functionality with ASR manager 4.6, MOS 6.7 and XCP 2070.
Please report any issues found.
Configure the XSCF to use Auto Service Request (ASR) if the Customer has a configured and
operational ASR Manager system available. Platadm privileges are required for this operation.
The ASR Manager must be version ≥4.6.
Log in to the XSCF with platadm privileges. ssh -l eis-installer 192.168.10.10

Disable the SNMP agent: XSCF> setsnmp disable

setsnmp: Agent disabled

Add ASR Manager system as trap destination:

XSCF>setsnmp addtraphost -t v2 -s Community -p Port IP_Address
Where:
• community is the community string (default value is "public").
• Port is the SNMP listener port (Default value = 0; this should be changed to a non-
zero value such as 162, unless the customer needs to use a different port, in which case
the port needs to be changed on the ASR Manager system as well – see Section 4.12.2
of the ASR Installation and Operations Guide).
• IP_Address is the ASR Manager system IP.
Example: setsnmp addtraphost -t v2 -s public -p 162 xxx.xxx.xxx.xxx

Enable the SNMP agent: XSCF> setsnmp enable

setsnmp: Agent enabled

Enable SNMP v1v2: XSCF> setsnmp enablev1v2c community

Verify SNMP settings to make sure trap XSCF> showsnmp

Agent Status: Enabled
destination is set and SNMP is enabled: Agent Port: 161
System Location: Unknown
System Contact: Unknown
System Description:

ACTIVATE THE ASR ASSET (FROM THE ASR MANAGER SYSTEM)

For reference: the ASR documentation is found under http://www.oracle.com/asr
Log into the ASR Manager system as user Via ssh or rlogin.
root.
Activate the ASR Asset. (LAN#0 IP) Assuming that /opt/asrmanager/bin is in PATH:
An email will be sent to the registered ASR # asr activate_asset -i 192.168.10.10
manager user stating the ASR activation is
pending.
Confirm that the XSCF is activated. # asr list_asset

Disconnect from the ASR Manager system. # exit

COMPLETION OF ACTIVATION IN MOS

Log into My Oracle Support: https://support.oracle.com

Select the Systems tab.

Oracle Internal and Approved Partners Only Page 17 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
In the Assets frame on the Systems pane select ASR Status from the sort filter, then
select Pending from the All Statuses drop-down menu:

Click on the serial number of the M10 platform to move to the Manage Assets page.
Update the Contact Name if required in Asset Details section. Note: Only users
associated with the support identifier can be a contact.
Click the Approve button in the ASR status section to make ASR active. The registered
contact will then receive a Asset Status Change email stating that ASR is now active.
Send a test trap from the M10 XSCF. The XSCF> rastest -c test
registered contact will receive a *Test*
Service Request email to confirm the test
SR creation was successful.

Oracle Internal and Approved Partners Only Page 18 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

OPTIONAL ADMINISTRATION CONFIGURATION

The following steps will depend on the customer requirements. They can be performed at a later
stage, for example after PPAR creation and testing.
Refer to the XSCF user guide and command man pages for the detailed procedures.
When using hostnames instead of IP addresses ensure that they are fully qualified.
Login into XSCFU: login: eis-installer

Enable telnet if desired (insecure, not XSCF> settelnet -c enable

recommended).
XCP 2210 and newer: XSCF> man setldap
XSCF> man setldapssl
If desired (rarely used) configure the XSCF as XSCF> man setad
client to an external authentication service.
There are 3 possibilities:
XSCF> showldap
• LDAP XSCF> showldapssl
XSCF> showad
• LDAP over SSL
• Active Directory (always over SSL)
Set up https service to allow access to the XSCF with the BUI.
The example shows how to create a self signed certificate. See the sethttps man pages
for other methods of creating certificates.
XSCF> sethttps -c selfsign US California San-Francisco XyzBank ItDivision M10-
4S-23-xyz-BB0 [email protected]
Enter passphrase: qazwsx
Verifying -
Enter passphrase: qazwsx
XSCF> sethttps -c enable

To connect to the BUI , point browser to:

https://<ip-address-BB#0-LAN#0>
Login using the XSCF user credentials defined previously.
Setup SNMP for third party IT management XSCF> setsnmp / showsnmp
XSCF> setsnmpusm / showsnmpusm
software (Tivoli, HP OpenView, BMC Patrol XSCF> setsnmpvacm/showsnmpvacm
etc.).
Audit Administration is used to specify logging XSCF> showaudit
XSCF> setaudit
of access details, such as which users logged in XSCF> viewaudit
to XSCF, their login times, and the operations
that they executed. The audit policy mainly
defines whether auditing is enabled (default) or
disabled and the management method when
audit trail becomes full.
XSCF> rebootxscf -a

Oracle Internal and Approved Partners Only Page 19 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

FINAL STEPS, TESTS AND VERIFICATION

Login into XSCFU ssh eis-installer@<IP_of
master_XSCF>
Use ssh or console
login: eis-installer

Verify the routing and name service: XSCF> showroute -a

XSCF> showhostname -a
XSCF> shownameserver
XSCF> nslookup <some hostname>

Verify networking: XSCF> shownetwork -a

XSCF> showpacketfilters -a
XSCF> showsscp
XSCF> showtelnet
XSCF> showssh
XSCF> showhttps

Verify NTP / date / timezone / altitude: XSCF> showntp -a

XSCF> showdate
XSCF> showtimezone -c tz
XSCF> showaltitude

Verify error reporting: XSCF> showsmtp

XSCF> showemailreport
XSCF> showsnmp

Verify environment: XSCF> showenvironment temp

XSCF> showenvironment Fan

Verify hardware: XSCF> showhardconf -M

XSCF> showstatus
XSCF> showlogs -v error

Verify auditing: XSCF> showaudit

Verify connection to all configured admin addresses from the admin client:
ssh [email protected]
ssh [email protected]
ssh [email protected]
ssh [email protected]
ssh [email protected]
ssh [email protected]

Oracle Internal and Approved Partners Only Page 20 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

INSTALL COD LICENSES & ASSIGN THEM TO TEST PPAR

Every CPU core must be enabled by the Capacity On Demand (COD) system. The PPARs cannot
be booted without having CPU cores activated.
System shipped after October 8, 2013 should XSCF> showcod
have the core activation keys already installed
at the factory. Verify. Skip the next two steps
if keys are installed.
Add the CPU core activation key to the system. Copy-paste the core activation key
(inside quotes).
XSCF> addcodactivation "core activation key"
Above Key will be added, Continue?[y|n]: y

Verify the number of permits installed. XSCF> showcod

Assign the licenses, verify. XSCF> setcod -p 0 -s cpu 192

XSCF> showcod
In this example, 192 cores are assigned to
PPAR0. Assign all permits to PPAR0.
CONFIGURE A SINGLE PHYSICAL PARTITION FOR INITIAL TESTING
(skip this section for single BB systems)
Every SPARC M10 system cabinet is regarded as one system board (PSB). One or more system boards
are combined to configure a physical partition (PPAR).
When one PPAR is configured for each system board, up to 16 physical partitions can be configured on
the SPARC M10-4S. Only one physical partition can be configured on the SPARC M10-1/M10-4, hence
the following steps are not required for single BB systems.
Check the current PPARs XSCF> showboards -a

Unassign any PSB that is is not assigned to PPAR 0. In this example, PSB 01-0 02-0 and
03-0 are unassigned from whatever PPAR they are assigned to:
XSCF> deleteboard -c unassign 01-0 02-0 03-0
Register all available PSBs to PPAR0. In this example, 3 PSBs are assigned to PPAR0:
XSCF> setpcl -p 0 -a 0=00-0 1=01-0 2=02-0
Assign all available PSBs to PPAR0. In this example, 3 PSBs are assigned to PPAR0:
XSCF> addboard -c assign -p 0 00-0 01-0 02-0
Verify that all available PSBs are assigned to XSCF> showboards -a
PPAR0.
CONFIGURE PPAR0 FOR TESTING
Set the POST diag level to the highest available:
XSCF> setpparmode -y -p 0 -m diag=max

Set messaging to the most verbose available:

XSCF> setpparmode -y -p 0 -m message=max

Prevent PPAR from booting automatically:

XSCF> setpparparam -p 0 -s bootscript "setenv auto-boot? false"

Oracle Internal and Approved Partners Only Page 21 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

SUNVTS CPU/MEMORY TEST OF ENTIRE PLATFORM

SPARC M10 systems currently manufactured will be supplied pre-loaded with Solaris 11.2 and
SunVTS 7.0. This enables the testing of the entire platform with SunVTS with a minimum of
effort.
Systems sold currently require the following minimum:
• Solaris 10: SunVTS 7.0 PS18.1 or higher (patch 151265-03, on EIS-DVD ≥17SEP14).
• Solaris 11: VTS 7.18.1 or higher (included within Solaris 11.2 GA).
Unless the server has been stored for some time, staged or prepared by Customer Ready Systems
(CRS) they will be in the following state (subsequent production will use the contents of more
recent EIS-DVDs):
• S11.2 with most recent updates adopted by manufacturing.
• PPAR0 configured.
• OS installed to the default boot device: lowest numbered disk.
PPAR0 power on, POST & enter OBP. XSCF> poweron -p 0

Verify everything is powered and fans are rotating.

XSCF> showenvironment volt
XSCF> showenvironment Fan

Connect to console of PPAR 0. XSCF> console -p 0

(be patient, no output for a while).
Check aliases. ok devalias

Boot the test PPAR. ok boot

Login as root login: root

Run SunVTS and test CPU/memory for 2 Change directory:

cd /usr/sunvts/bin
hours.
To start SunVTS:
TTY mode: ./startsunvts -t
BUI mode: ./startsunvts -b
At conclusion of run, inspect the SunVTS log files under:
/var/opt/SUNWvts/logs/sunvts.info
Bring down test the PPAR. # init 0

Exit from console: ok #.

Check if any error were logged. XSCF> showlogs error

Investigate, open SR if unable to fix issue.

Oracle Internal and Approved Partners Only Page 22 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

FURTHER ACTIONS ON ENTIRE PLATFORM

If PCI Expansion Box(es) are installed, update firmware as required
Check the version of the firmware that is currently running. The current FW revision is
1220. If the version(s) is (are) current, go to sub-section CLEANING UP below.
XSCF> ioxadm -v list
Location Type FW Ver Serial Num Part Num State
PCIBOX#6004 PCIBOX - 2121236004 On
PCIBOX#6004/PSU#0 PSU - FEJD1212000651 CA01022-0750-D/ On
PCIBOX#6004/PSU#1 PSU - FEJD1212000669 CA01022-0750-D/ On
PCIBOX#6004/IOB IOBOARD 1220 PP123404T8 CA20365-B66X 008AG On
PCIBOX#6004/LINKBD BOARD - PP12340275 CA20365-B60X 001AA On
PCIBOX#6004/FANBP FANBP - PP123203NV CA20365-B68X 004AC On
BB#00-PCI#00 CARD 1220 PP1234026G CA20365-B59X 001AA On

In the above example the firmware is current (no update required).

The PCIBOX update can either be found on the XSCF> getflashimage …
EIS-DVD or obtained from MOS. Refer to Refer to page 15 for usage of the getflashimage
page 3 of this checklist. command.

Current update: PCIBOX1220.tar.gz Do NOT use firmware prior to 1130 – EIS-

ALERT #291.
Verify that the latest FW is ready to be XSCF> getflashimage -l
..
installed. PCIBOX1220.tar.gz

Update the FW of each PCI expansion units installed. Their name is found in the ioxadm
-v list output. The process will take about 20 minutes for each unit, wait for: Firmware
update has been completed.
XSCF> ioxadm -c update PCIBOX#6004 -s 1220
Firmware update is started. (version=1220)
Firmware update has been completed.

Verify: XSCF> ioxadm -v list

CLEANING UP
Power off the test PPAR. XSCF> poweroff -p 0

Reset to standard values:

XSCF> setpparmode -y -p 0 -m diag=min

Reset to standard values:

XSCF> setpparmode -y -p 0 -m message=normal

Unconfigure Physical Partition 0 that was setup for testing.

(skip this section for single BB systems)
Unassign all PSBs:
XSCF> deleteboard -c unassign 01-0 02-0 03-0
XSCF> showboards -a

De-assign all cores from test PPAR. XSCF> setcod -p 0 -s cpu 0

XSCF> showcod
Verify.
Remove all PSB from PPAR0 PCL. XSCF> setpcl -p 0 -r 0 1 2
XSCF> showpcl -a
In this example we remove LSB 0, 1 and 2
from the test PPAR PCL. Verify.

Oracle Internal and Approved Partners Only Page 23 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

SET UP CUSTOMER PPAR CONFIGURATION

CONFIGURE THE PPARS
(Skip this section for single BB systems)
Check the current PSBs, none should be XSCF> showboards -a
assigned at this time.
Register PSBs to PPARs. XSCF> setpcl -p 0 -a 0=00-0 1=01-0
In this example, 2 PSBs are registered to XSCF> setpcl -p 1 -a 2=02-0
PPAR0 and 1 PSB is registered to PPAR1.
You may register any PSB to any PPAR in case
the PSB should eventually become part of the
PPAR.
Assign PSBs to PPARs as specified in the EIS XSCF> addboard -c assign -p 0 00-0
01-0
Installation Configuration Plan.
XSCF> addboard -c assign -p 1 02-0
In this example, 2 PSBs are assigned to PPAR0
and 1 PSB is assigned to PPAR1
Verify that all available PSBs are assigned XSCF> showboards -a
correctly.
MIXED ATHENA / ATHENA+ CPU CONFIGURATIONS
(Skip this section for single BB systems)
If a PPAR is built with BBs that contain different CPU types or if future DR operations
due to a BB replacement or PPAR extension might produce a mixed configuration, then
the PPAR cpumode should be set to compatible.
The default value is auto.
Check for mixed Athena / Athena+ processors within each PPAR.
Athena CPU type: 0x10
Athena+ CPU type: 0x20
XSCF> showhardconf
CPU#0 Status:Normal; Ver:4142h; Serial:00321580; + Freq:3.000 GHz; Type:0x10;
CPU#0 Status:Normal; Ver:4142h; Serial:00020300; + Freq:3.700 GHz; Type:0x20;

Verify for each PPAR n XSCF> showpparmode -p n

Set for each PPAR n: XSCF> setpparmode -p n -m cpumode=compatible

ASSIGN CORE LICENCES

Remember: 1 socket → 16 cores
Example for M10-1: XSCF> setcod -p 0 -s cpu 16

Example for M10-4: XSCF> setcod -p 0 -s cpu 64

Example for M10-4S, 3BB. XSCF> setcod -p 0 -s cpu 128

XSCF> setcod -p 1 -s cpu 64
In this example, we assign 128 cores to PPAR0
and 64 cores to PPAR1:

Oracle Internal and Approved Partners Only Page 24 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
OPTIONAL CONFIGURATION
Check the EIS Installation Configuration if special configuration steps have been chosen
for this system. Do not change any of these unless agreed with the customer.
Power scheduling. Schedule for powering XSCF> man addpowerschedule
XSCF> showpowerschedule -a -m list
on/off.
Power capping. Sets limitations for power XSCF> man setpowercapping
XSCF> showpowercapping
consumption.
Power-up delay - sets the warm-up operation XSCF> man setpowerupdelay
XSCF> showpowerupdelay
time of the system and the wait time before
start.
Memory mirroring. XSCF> man setupfru
XSCF> showfru -a

Optional PPAR configuration: XSCF> man setpcl

XSCF> showpcl -a -v
• Degradation configuration policy (fru / psb /
system)
• mem and I/O disabling
Sector cache mode. XSCF> man setsectorcachemode
XSCF> showsectorcachemode

Disable automatic power saving – can increase XSCF> setpparmode -p 0 -m

elastic=off -y
performance at the cost of more power used.
Setting is for each PPAR.
POWER ON THE PPARS
XSCF> poweron -a

Oracle Internal and Approved Partners Only Page 25 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

OPTIONAL:
PPAR HARDWARE MIRRORING AND ALIAS SETTING
All actions here require that you are connected to the console of each PPAR.
Connect to the PPAR console. XSCF> console -p 0
XSCF> console -p 1
Do the following steps for every PPAR.
etc..
You may want to do this simultaneously on
all PPARs open multiple ssh sessions for
this.
MIRRORING THE PPAR SYSTEM DISKS VIA HW RAID
For ZFS boot using Solaris, EIS recommends that you use simple disks and allow ZFS to
create mirrored pools at the O/S level.
For UFS, EIS recommends that you create H/W RAID 1 volumes, presenting a single
redundant LUN to the operating system. This checklist describes how to mirror the boot
disk (RAID 1) using commands at the OBP level.
Hardware RAID for the internal disks must be set up before the OS is installed.
(setting up Hardware RAID destroys the disk contents).
Configuring additional internal disks can be done using the sas2ircu utility once the
operating system is installed (raidctl will not work!) – refer to page 31 of this checklist.
The required steps for a simple RAID 1 mirror are shown as example in the following
steps. Details can be found in the installation manual, chapter 12.2.
Commands entered are in bold characters.
ok probe-scsi-all
/pci@8800/pci@4/pci@0/pci@0/scsi@0 (this is the disks path)
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00
Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 500003942823fb38 SASAddress 500003942823fb3a PhyNum 0
Target b
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 500003940832182c SASAddress 500003940832182e PhyNum 1

Caution: The following steps will destroy all disk data!

ok select /pci@8800/pci@4/pci@0/pci@0/scsi@0 (copy disks path from above)
ok a b create-raid1-volume (use the targets shown above)
Target a size is 1169920000 Blocks, 598 GB
Target b size is 1169920000 Blocks, 598 GB
The volume can be any size from 1 MB to 571250 MB
What size do you want? [571250]
Volume size will be 1169920000 Blocks, 598 GB
Enter a volume name: [0 to 15 characters] HW-RAID1_root (chose name)
Volume has been created
ok show-volumes
Volume 0 Target 11e Type RAID1 (Mirroring)
Name HW-RAID1_root WWID 0f04bd661d804526
Optimal Enabled Background Init In Progress Data Scrub In Progress
2 Members 1169920000 Blocks, 598 GB
Disk 0
Primary Optimal
Target a TOSHIBA MBF2600RC 3706
Disk 1
Secondary Optimal

Oracle Internal and Approved Partners Only Page 26 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Target b TOSHIBA MBF2600RC 3706
{80} ok unselect-dev
{80} ok probe-scsi-all
/pci@8800/pci@4/pci@0/pci@0/scsi@0
FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00

Target 11e Volume 0 (target a and b have been replaced by target 11e)
Unit 0 Disk LSI Logical Volume 3000 1169920000 Blocks, 598 GB

Use the next 5 steps if you want to define own aliases, for example root-disk or root-
mirror.
Look at pre-set aliases:
{0} ok devalias
net00-3 /pci@8400/pci@4/pci@0/pci@a/network@0,1
net00-2 /pci@8400/pci@4/pci@0/pci@a/network@0
net00-1 /pci@8000/pci@4/pci@0/pci@9/network@0,1
net00-0 /pci@8000/pci@4/pci@0/pci@9/network@0
net /pci@8000/pci@4/pci@0/pci@9/network@0
cdrom /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/hub@2/cdrom@1/disk@0,0:a
disk00-7 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p7,0
disk00-6 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p6,0
disk00-5 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p5,0
disk00-4 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p4,0
disk00-3 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p3,0
disk00-2 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p2,0
disk00-1 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1,0
disk00-0 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0
disk /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0
virtual-console /virtual-devices@100/console@1

Locate disks:
ok show-disks
a) /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk
b) /iscsi-hba/disk
Set disk nvaliases, examples:
ok nvalias root-disk /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0
ok nvalias root-mirror /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1,0
etc..
Locate networks:
ok show-nets
a) /pci@8400/pci@4/pci@0/pci@a/network@0,1
b) /pci@8400/pci@4/pci@0/pci@a/network@0
c) /pci@8000/pci@4/pci@0/pci@9/network@0,1
d) /pci@8000/pci@4/pci@0/pci@9/network@0
Set network nvalias, examples:
ok nvalias net-prim pci@0,600000/pci@0/pci@1/pci@0/network@0
ok nvalias net-sec pci@0,600000/pci@0/pci@1/pci@0/network@0,1
etc..
Enable the aliases. ok use-nvramrc? true

Prevent automatic boot then reset to ok setenv auto-boot? false

ok reset-all
activate the nvram stored aliases.
COMPLETION
Verify / correct environment. ok devalias
ok printenv

Return to XSCF (if required). ok #.

XSCF>

Oracle Internal and Approved Partners Only Page 27 of 38 Vn 1.3.b Created: 25. Sep. 2019
 INFORMATION: PLATFORM MINIMUM SOFTWARE REQUIREMENTS
The minimum Solaris requirements is a follows:
• Oracle Solaris 10 Update 11 (HW 01/13).
OVM 3.0 or later must be installed even if no LDOMs are used
OR
• Oracle Solaris 11.1 SRU1.4 EIS-DVD ≥ 28NOV12.
• Firmware XCP 2041 for systems with Athena processors.
• Firmware XCP 2210 for systems with Athena+ processors (from April 2014).
• Firmware XCP 2250 for M10-1 and M10-4 with 8 cores SPARC64 X+ 3.7 GHz
processors (from April 2015).
The latest XCP firmware is recommended. Normally, only the 2 most recent releases of XCP
firmware are actively supported; currently this is XCP 2353 and XCP 2352.
EIS strongly recommends that the most recent update of the required operating system together
with the latest EIS-DVD are used.

Oracle Internal and Approved Partners Only Page 28 of 38 Vn 1.3.b Created: 25. Sep. 2019
 INFORMATION: ACCESS TO DVD CONTENTS
When applying EIS Methodology it is necessary to be able to install a server and access the
contents of the EIS-DVD. The M10 servers do not have a local DVD reader. There are a number
of options:
• Attach a USB DVD drive to the server. The server can boot from Solaris media thus the
server can be installed. Once Solaris is installed and the EIS-DVD inserted into the drive it
will be automounted and the contents available under /cdrom/eis-dvd. This method is not
suitable when installing large numbers of servers (does not scale).
Note that controller numbers will be allocated at the time of the installation and they will not
vary after that, however be aware that the controller numbers will be different from
installations that did not have a DVD drive attached. The numbering depends on the probe
order of the I/O slots so it will vary according to platform.
• Run the Java™ Remote Console application from a system equipped with a DVD drive or the
appropriate ISO image (KVMS). Beware that access to DVD contents by this method can be
slow.
• For Solaris 10 installations set up an install server – e.g. Using the Jumpstart Enterprise
Toolkit (JET) – refer to the EIS Installation Checklist for JET. This enables multiple servers
to be installed in parallel.
• For the duration of the installation work, copy the contents for the EIS-DVD via copy-
dvd2sun.sh onto an available server & share the contents and access via
/net/<IP-of-server>. If using JET, this can be done on the install server. The copy action
takes about 40 minutes if using the local DVD drive.
• Remote storage (XCP2260 onwards) enables connections from logical domains to the
following media:
• Media inserted into the CD/DVD drive mounted in a terminal.
• ISO image on a terminal.
In this checklist example of EIS-DVD locations are of the form .../sun/patch/xxx and should be
preceded by the appropriate path.

INFORMATION: ADVICE ON PPAR OS INSTALLATION METHODS

Unless you intend using the pre-installed disk image on each PPAR (see page 30), there are
several possible methods for installing the PPARs including:
• Install each PPAR from Solaris DVD using a USB local drive.
The drive must be connected to the front of a BB – see MOS Document ID 1553734.1.
• Install Solaris 10 PPAR using an install server (e.g. via JET). This requires the availability of
an install server provided by customer or an engineer's laptop (in those countries where laptops
are used as install servers AND the Customer permits introduction of a laptop into the data
center).
• Install Solaris 11 PPAR using public or local Solaris repository.
Refer to the XCP 2330 Product Notes to ensure that the Solaris Installation meets the minimum
requirements.

Oracle Internal and Approved Partners Only Page 29 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comments Check

BOOTING PPAR FROM A PRE-INSTALLED DISK IMAGE

Standard installations carried out by manufacturing are as follows:
• Solaris 11.x will have been loaded.
• The root file system will be ZFS.
• The on-board RAID (if available) will not be active.
• The system will have been patched and configured according to EIS methodology
• Before leaving the factory, the system will have been “sys-unconfig'd” and the SP set back to
defaults.
If you have set up a HW-RAID configuration for the boot disk the pre-installed image will be lost.
Initial bootup: Answer as appropriate.
Upon initial boot, the server will ask the
typical Solaris post-install configuration
questions.
Go to the Addition Actions section on page 31.

Task Comments Check

SOLARIS-INSTALLATION (for each PPAR)

Go to the appropriate Solaris OS checklist:
• EIS Installation Checklist for the Solaris 10 OS OR
• EIS Installation Checklist for the Solaris 11 OS

Oracle Internal and Approved Partners Only Page 30 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comments Check

ADDITIONAL ACTIONS
Optionally configure the NTP client. Follow Template in /etc/inet/ntp.client. Copy into /etc/
customer's site policy. inet/ntp.conf and modify as appropriate.
Do not use the XSCFU as NTP server. For NTP configuration details see MOS
Document ID 1010136.1.
Confirm that all relevant FABs have been performed on the PPAR.
If HW RAID is used, you must install the sas2ircu utility to allow management and
troubleshooting of HW RAID volumes.
The utility6 is available on EIS-DVD-ONE in .../sun/tools/SAS.
Alternatively obtain the latest sas2ircu utility from the AVAGO web site:
http://docs.avagotech.com/support/download-search enter sas2ircu into the Keyword
field and press Search. Expand the Management Software and Tools tab.
Unzip the file and copy e.g.:
SAS2IRCU_P20_Solaris_only/sas2ircu_solaris_sparc_rel/sas2ircu to /usr/sbin
Verify that HW volumes and disks show as expected:
# sas2ircu 0 display
# sas2ircu 1 display
SUN FLASH ACCELERATOR F40 & F80 PCIE CARDS
Sun Flash Accelerator F40 PCIe Card Documentation Library
Sun Flash Accelerator F80 PCIe Card Documentation Library
If either of these cards are installed in the system, you must install the corresponding
ddcli utility (in the MOS patch) to allow firmware upgrade, management and
troubleshooting:
• p250589727 Software Update SW2.0 for F40 PCIe Card (FW 13.05.10.01). Unzip
the patch and cd to F40_SW2.0.1/Solaris-Sparc/Tool. Then unzip file
solaris_sparc-ddcli_112.05.25.00.zip and copy ddcli into directory /usr/sbin.
• p250589818 Software Update SW2.0 for F80 PCIe Card (FW 13.05.11.01). Unzip
the patch and cd to F80_SW2.0.1/Solaris-Sparc/Tool. Then unzip file
solaris_sparc-ddcli_112.05.25.00.zip and copy ddcli into directory /usr/sbin.
Patches are available on EIS-DVD-ONE in .../sun/patch/firmware/FLASH.
Verify that cards show as expected via command: /usr/sbin/ddcli
Verify firmware rev. against the file found in the FW directory of the unpacked patch,
unzip file, select 2. Update Flash Package if required.

6 SAS2IRCU_P20 (20.00.00.04) for Solaris only is available on ≥EIS-DVD 19JUL17.

7 SW 2.0 for the F40 card is available on EIS-DVD ≥07DEC16.
8 SW 2.0 for the F80 card is available on EIS-DVD ≥07DEC16.

Oracle Internal and Approved Partners Only Page 31 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comments Check
ORACLE FLASH ACCELERATOR F160/F320 PCIE CARDS
We are informed that VTS will recognize NVME drives and uses diskmediatest to test
these drives (minimum version of SunVTS for NVME drives is 7.0ps19). You can also
use tools like vdbench, diskomizer to exercise NVME drives.
DISPLAY THE NVME LOGICAL DEVICES
The nvmadm command will have been installed with Solaris 11.3 groups solaris-large-
server & solaris-small-server but not with group solaris-minimal server. To verify its
available:
# pkg list nvme-utilities
NAME (PUBLISHER) VERSION IFO
system/storage/nvme-utilities 0.5.11-0.175.3.0.0.29.0 i--
In the above example the package is available. If it is not, install via:
# pkg install system/storage/nvme-utilities

Confirm that the expected number of drives are visible to Solaris (example below is
from a server with 2 NVMe cards):
# nvmeadm list -v
SUNW-NVME-1
PCI Vendor ID: 8086
Serial Number: CVMD543600HD1P6NGN
Model Number: INTEL SSDPEDME016T4S
Firmware Revision: 8DV1RA12
Number of Namespaces: 1
SUNW-NVME-2
PCI Vendor ID: 8086
Serial Number: CVMD543100K01P6NGN
Model Number: INTEL SSDPEDME016T4S
Firmware Revision: 8DV1RA12
Number of Namespaces: 1

Oracle Internal and Approved Partners Only Page 32 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comments Check
FIRMWARE VERIFICATION & UPDATE
Oracle Flash Accelerator F160 PCIe Card and 1.6 TB NVMe SSD Documentation
Library
XCP2260 is the minimum required level. PCI expansion unit firmware minimum
version 1210 (if used in in unit). Oracle Solaris 11.2 SRU 14 or later.
You can refer to Integration of an Flash Accelerator F160 NVMe Card (Aura 3 NVMe)
at a glance, MOS Document ID 2077216.1.
Examine the firmware with the command nvmeadm list -v. The above examples
shows 8DV1RA13 – upgrade if currently below.
The three Fujitsu M10 RA P3X00 FW patches 21683464, 21683470 & 2163474 are
identical; the file 8DV1RA13_8B1B012E_signed.bin has been extracted from them &
is available on EIS-DVD ≥07DEC16 in the same directory as the FJM10 XCP updates.
Determine the controller numbers with NVMe drives e.g. via:
# echo | format
6. c1t1d0 <INTEL-SSDPEDME016T4S-8DV1 cyl 63589 alt 2 hd 256 sec 192>
/pci@307/pci@1/nvme@0/disk@1
/dev/chassis/SYS/RCSA/PCIE4/NVME/disk
7. c14t1d0 <INTEL-SSDPEDME016T4S-8DV1 cyl 63589 alt 2 hd 256 sec 192>
/pci@30f/pci@1/nvme@0/disk@1
/dev/chassis/SYS/RCSA/PCIE15/NVME/disk

To perform the updates for the above example:

# fwupdate update nvme-controller-firmware -n c1 -f \
8DV1RA13_8B1B012E_signed.bin
# fwupdate update nvme-controller-firmware -n c14 -f \
8DV1RA13_8B1B012E_signed.bin

Oracle Flash Accelerator F320 PCIe Card and 3.2 TB NVMe SSD Documentation
Library
XCP2320 is the minimum required level.
PCI expansion unit firmware minimum version 1210 (if used in in unit).
Oracle Solaris 11.3 SRU 10 or later, no patch available for M10 at this time
Reboot the PPAR.

Oracle Internal and Approved Partners Only Page 33 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comments Check
8-PORT 12GBPS SAS-3 HBA (EXTERNAL)
Refer to Fujitsu M10: Firmware for the Various Hardware Components used on Fujitsu
M10 (MOS Document ID 2047847.1).
To verify the firmware version examine output of the following command:
# prtconf -v

Check for:
name='ModelName' type=string items=1 dev=none
value='ORCL-EXT-SAS3'
.. followed by
name='firmware-version' type=string items=1 dev=none
value='4.0.0.0'
The minimum firmware is: 06.00.02.00
Obtain the firmware and instructions to update the HBA(s):
Oracle Storage 12 Gb/s SAS PCIe HBA, External

Oracle Internal and Approved Partners Only Page 34 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

FINAL WORK ON THE XSCFU

Snapshot Method I: (This method is not available below XCP 2050)
For the purposes of capturing the configuration of the entire platform following an EIS
installation the convention is to run snapshot on the XSCF and send the results to the
PPAR via SSH.
XSCF> snapshot -a -L F -t user@<IP-of-PPAR>:/var/sun/name-of-XSCFU

If user is root, then make sure that file /etc/ssh/sshd_config contains (on the PPAR) the
line: PermitRootLogin yes
Snapshot Method II:
Save the snapshot on USB stick. USB stick must be inserted in the XSCF USB port
marked “Maintenance Only” on the rear side.
XSCF> snapshot -a -L F -d usb0
Snapshot Method III: Use the BUI to collect the snapshot
Menu → XSCF → maintenance → snapshot
Select BB ID: “all”
Select log set: “full log”
Choose Transfer Method: Browser, the browser will save the file
(https service required, see optional config. 19)
Save the XSCF setting information
Connect a USB device to a USB port on the XSCF unit panel (rear panel) of the master
XSCF:
XSCF> dumpconfig file:///media/usb_msd/backup-file.txt
or
XSCF> dumpconfig ftp://server/backup/backup-file.txt
Enable automatic power-up of PPARs after Move all the keyswitches to the secure position.
recovering from a power failure.
Allow the PPARs to automatically return to their previous state after recovering from a
power failure. Run the following command:
XSCF> showpparmode -p 0
XSCF> showpparmode -p 1
etc..
XSCF> setpparmode -y -p 0 -m guestboot=on
XSCF> setpparmode -y -p 1 -m guestboot=on
etc..
Create users for customer administrators. (names are examples)
XSCF> adduser super-admin
You cannot use the following user account XSCF> adduser less-super-admin
names, as they are reserved for system use: XSCF> adduser ...
root, bin, daemon, adm, operator, nobody,
sshd, rpc, rpcuser, ldap, apache, ntp, admin,
and default.

Oracle Internal and Approved Partners Only Page 35 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check
Give users the appropriate privileges. Note XSCF> setprivileges super-admin
platadm useradm auditadm fieldeng
that the privileges should given all at once (not mode
cumulative). XSCF> setprivileges less-super-admin
The mode privilege allows to change to service fieldeng
mode, with appropriate password. etc.

Set passwords for the user accounts. XSCF> password super-admin

XSCF> password less-super-admin
You will be prompted for the passwords. etc..
Exit and login as user super-admin. XSCF> exit
logout
login: super-admin

Disable user eis-installer XSCF> disableuser eis-installer

Verify user settings. XSCF> showuser -l

Oracle Internal and Approved Partners Only Page 36 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

EXPLORER & ANALYSIS FOR THE PPARs

Run explorer on each PPAR. It is important that the system’s serial number is in the
Explorer configuration.
# explorer

Run ORAS/CLI (from EIS-DVD) locally to cd /sun/tools/ORAS

sh run-oras.sh
analyse each Explorer file.
Examine the results. Examine the resulting report:
If necessary repair & repeat Explorer/ORAS cd /var/tmp/ORAS
sequence. more *EIS.Report.txt

Set the diag switch to its default value. # eeprom "diag-switch?"=false

Enable autoboot. # eeprom "auto-boot?"=true

Reboot => everything ok? # init 6

Upload the Explorer file(s) to the Oracle proactive directory.

If the newly-installed system has connectivity to the Internet:
# curl -T <filename to upload> -o <logfile> -u <SSO login> \
https://transport.oracle.com/upload/proactive/

Note the trailing / is required or the upload will fail.

Above is for Solaris 11; on Solaris 10 systems replace curl above by: /opt/SUNWexplo/
bin/solaris/curl.sparc
Check the <logfile> after the upload completes to see any errors recorded.

Alternatively, to upload the Explorer file from a non-Solaris system (Windows, Linux or
Max OS X) use the Filezilla Client.
1. Required settings (under File then Site Manager):
Host: transport.oracle.com
Port: (leave empty)
Protocol: FTP - File Transfer Protocol
Encryption: Require implicit FTP over TLS
Logon Type: Ask for password (best option)
User: <SSO login> (usually your personal Oracle email address)
Transfer Mode: Passive (In the transfer settings tab)
2. Select the proactive directory on transport, note that you will not see anything in this
directory.
3. Upload the local files to the proactive directory.
The Explorer output file is normally in directory:
• SRV4 (Solaris 10): /opt/SUNWexplo/output
• IPS (Solaris 11): /var/explorer/output
The filename is of the form explorer.<hostid>.<hostname>-<date>.tar.gz

Oracle Internal and Approved Partners Only Page 37 of 38 Vn 1.3.b Created: 25. Sep. 2019
 Task Comment Check

HANDOVER
Perform Installation Assessment tests as EISdoc V4 – completed during preparation of
described in the EIS Test Procedures Plan. installation.

Complete documentation and hand over to EISdoc V4:

customer. File EIS-DOCS-Operational-Handover-
Document.odt
Short briefing: the configuration.

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 welcome. Oracle staff should mail to [email protected] .

Partners should mail to: [email protected] .

Oracle Internal and Approved Partners Only Page 38 of 38 Vn 1.3.b Created: 25. Sep. 2019