Sparc Fjm12

EIS Installation Checklist for Fujitsu SPARC M12 Servers
M12-1 / M12-2 / M12-2S
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 27.
• 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,
Oracle Internal and Approved Partners Only Page 1 of 35 Vn 1.2.h Created: 6. May. 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 SPARC M12-1, M12-2 & M12-2S Servers.
Fujitsu SPARC M12 documentation Library It is important to review the product notes for the
reviewed? firmware version to be installed.
Current firmware is XCP 3060.
http://docs.oracle.com/cd/E86029_01/
In the Fujitsu SPARC M12 Documentation
Note: All manuals listed below can be found Library, select one of the Fujitsu SPARC M12*
under this location, please navigate to the User Manuals and within that the Product Notes
(XCP version 3060).
required documents.
Installation planning. Read:
1. SPARC M12 Systems: (Common) Installation Planning Manual
2. Specific SPARC M12 System (M12-1/M12-2 / M12-2S) Installation Guide.
It is important to have this document available for onsite work.
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-FJM12.odt
EIS-TPP-Server-FJM12.odt
FABs/EIS-ALERTs reviewed?
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 2241012.1 (there may be a delay in
updating).
The system firmware updates can either found on EIS-DVD-ONE1 in directory
.../sun/patch/SYSFW/FJM12 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 SPARC M12-1, Fujitsu SPARC M12-2 or Fujitsu SPARC M12-2S.
• Release: select the latest2 version eg M12 XCP3060.
5. Click Search.
6. A new screen will appear with the Patch Search Results. Click on the Patch Name for
the SPARC M12 XCP30xx FIRMWARE which will be of the form 29494267.
7. Download the file – currently 102.7 MB in size.
8. The result will be a file of the form: p29494267_306000_Generic.zip. Unzipping will
produce a number of files; the firmware filename will be of the form:
BBXCP3060tar.gz
1 XCP 3060 is on EIS-DVD ≥25APR19; XCP 3053 is on EIS-DVD ≥24OCT18.

2 The latest version is not necessarily at the end of the list!
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 ≥07DEC16 in the directory for the M10
XCP: .../sun/patch/SYSFW/FJM10. (FJM10 is intended here!)
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.
If name service (DNS, NIS...) used, ensure that
new hostnames, IP addresses etc. are correct on
name server.
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.
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 The M12-1, SPARC M12-2 or M12-2S
system and proper placement of perforated Installation Guide, Chapter 2.
floor tiles in raised floor data centers.
PREPARE ASSEMBLY/CABLING
Have the required documents ready. M12-1, M12-2 or M12-2S Installation Guide and
SPARC M12-1 or M12-2 / M12-2S Service
Start here: Manual and
http://docs.oracle.com/cd/E86029_01/ PCI Expansion Unit for SPARC M12/M10 Systems
then select the required M12 server and Service Manual (if used).
navigate from there.
Installation guides and service manuals are
specific for M12-1, M12-2, M12-2S.
Verify placement w.r.t. airflow & location of Fujitsu SPARC M12 requires airflow front to
air vents. back.
Environment Measurements: Verify that conditions are met.

• Temperature:.................C(F) SPARC M12 Systems Installation Guide Chapter
• Humidity:.......................% 2.5
Task Comment Check
HARDWARE INSTALLATION & CABLING

The hardware installation steps differ depending on the type and number of Building Blocks (BB):
• The M12-2S for up to 4 Building Blocks must be installed in racks and wired on-site.
• Systems with Crossbar Boxes (those with more than 4 BB) are delivered installed and wired in
racks.
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.
M12-1:
Install optional memory, follow configuration SPARC M12-1 Service Manual, Chapter 2.2.1
rules.
Install M12-1 into approved rack. SPARC M12-1
Installation Guide, Chapter 2.4, 3.4.1
Install M12 PCI expansion unit(s) (if any) into
SPARC M12-1
approved rack. Installation Guide, Chapter 2.4, 3.4.2
Install optional internal disks. SPARC M12-1 Service Manual, Chap 9
Install optional internal PCIe cards. SPARC M12-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 M12 / M10
Systems Service Manual:
Install PCIe cards.
Chapter 8
Install Link Card in M12-1. Chapter 10
Connect the serial XSCF console cable. SPARC M12-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 M12-1 Installation Guide
any) Installation Guide, Chapter 4.2
Slide the mode switch to “Service”.

Go to next table (Power Up). Page 9.
Continued on next page
Task Comment Check
M12-2 OR M12-2S AS SINGLE UNIT:
Install optional memory, follow configuration SPARC M12-2/M12-2S Service Manual, Chapter
rules. 2.2.1
Install M12-2 into approved rack. SPARC M12-2 Installation Guide, Chapter 2.4, 3.3
Install M12 PCI expansion unit(s) (if any) into SPARC M12-2S Installation Guide, Chapter 2.4,
3.4
approved rack.
M12-2S only: set BB-ID switch to 00. SPARC M12-2S Installation Guide, Chapter 4.1
Install optional internal disks. SPARC M12-2/M12-2S Service Manual, Chapter

15
Install optional internal PCIe cards. SPARC M12-2/M12-2S Service Manual, Chapter
Strictly adhere to the I/O board configuration 12
Plan.
Install optional PCI expansion (if any) PCI Expansion Unit Service Manual:
components: Chapter 8
Install PCIe cards. Chapter 10
Install Link Card in M12 System.
Connect the serial XSCF console cable. SPARC M12-2 Installation Guide, Chapter 4.1
Connect the XSCF LAN cables. SPARC M12-2S Installation Guide, Chapter 5.1
Connect the GbE LAN cables.

Connect cables to the PCI Expansion Unit (if SPARC M12-2 Installation Guide, Chapter 4.2
any). SPARC M12-2S Installation Guide, Chapter 5.2
Slide the mode switch to “Service”.

Install optional PCI expansion (if any) PCI Expansion Unit for SPARC M12 / M10
components: Systems Service Manual:
Chapter 8
Install PCIe cards.
Chapter 10
Install Link Card in M12-2S.
Connect the serial XSCF console cable to SPARC M12-2S Installation Guide, Chapter 5.1
BB#00.
Connect the XSCF LAN cables to BB#00.
Connect the GbE LAN cables. Follow the EIS
Installation Configuration Plan provided.
Connect cables to the PCI Expansion Unit (if SPARC M12-2S Installation Guide, Chapter 5.2
any).
Slide all mode switches to “Service”.
Go to next table (Power Up). Page 9 of this checklist
Task Comment Check
M12-2S UP TO 4 BB (WITHOUT CROSSBAR BOXES)
Install optional memory, in all BBs, follow SPARC M12-2/M12-2S Service Manual, Chapter
configuration rules. 2.2.1
Install all M12-2S into approved rack. SPARC M12-2S Installation Guide, Chapter 2.4,
3.4.1
Install M12 PCI expansion unit(s) (if any) into
SPARC M12-2S Installation Guide, Chapter 2.4,
approved rack. 3.4.2
Set BB-ID switches as follows: SPARC M12-2S 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 M12-2S Installation Guide, Chapter 4.2
Connect the crossbar cables. SPARC M12-2S Installation Guide, Chapter 4.3 &
Verify that they are completely inserted. Appendix B
Install the Dual Cable between BB#0 and SPARC M12-2S Installation Guide, Chapter 4.2 &
BB#1. Appendix B

15
Strictly adhere to the I/O board configuration 12
Plan.
Install optional PCI expansion (if any) PCI Expansion Unit for SPARC M12 / M10
components: Systems Service Manual:
Chapter 8
Install PCIe cards.
Chapter 10
Install Link Card in M12-2S.
BB#00. Optionally install a second console
cable to BB#1.
Connect the XSCF LAN cables to BB#00 and
BB#01.
any).
Go to Section Power Up on Page 9 of this checklist.
Task Comment Check
PRE-INSTALLED M12-2S 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 M12-2S Installation Guide, Chapter 3.3.1
panels of the racks.
SPARC M12-2S Installation Guide, Chapter 3.3.2
Secure the rack(s).
Mechanically join racks (if dual racks).
Connect power to the racks(s). SPARC M12-2 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 M12-2M12-2 Service Manual, Chapter
configuration rules. 2.2.1.
Install M12 PCI expansion unit(s) (if any) into SPARC M12-2 Installation Guide, Chapter 3.4.2
approved rack.
Verify the BB-ID switches in left (or single) SPARC M12-2 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 M12-2/12-2 Service Manual, Chapter 4.1.
present):
Bottom BB: 08. Top BB: 15
Lower XB-BOX: 82
Upper XB-BOX: 83
Connect the XSCF interconnect cables (if 2 SPARC M12-2 Systems Installation Guide,
racks configuration). Chapter 4..2,
Appendix B
Connect the crossbar cables between racks (if 2 SPARC M12-2S Installation Guide, Chapter 4.3,
racks configuration). Appendix B
The cables come attached to the right rack.
Match port numbers and colours on cable
labels with ports in left rack.
15.4.
Strictly adhere to the I/O board configuration 12.
Plan.
Task Comment Check
Install optional PCI expansion units (if any) PCI Expansion Unit for SPARC M12/M10 Systems
components: Service Manual:
Chapter 8
• Install PCIe cards.
Chapter 10
• Install Link Card in M12-2S.
BB#80. Optionally install a second console
cable to BB#81.
Connect the XSCF LAN cables to BB#80 and
BB#81.
any).
Go to Section Power Up on Page 9 of this checklist.
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. For configurations with XB-BOXes.
Plug power to BB #00. 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 re-connect the
serial port to that unit.
Wait for the login prompt. login:
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 M12 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
configurations).
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 users3. 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
3 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.
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.
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:

Set hostname and domain name:

XSCF> sethostname bb#00 scf0-hostname
XSCF> sethostname -d company.com
Task Comment Check
Configuration of admin network(s) for 2 to 4 BB (no XB-BOX)
Admin network 0:
XSCF> setnetwork lan#0 -m 255.255.255.0 192.168.10.10

Set hostnames and domain name:

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

Set hostnames and domain name:

XSCF> sethostname xbbox#80 scf0-hostname
XSCF> sethostname xbbox#81 scf1-hostname
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
Task Comment Check
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
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 []: administrator@company.com
XSCF> setemailreport
Enable E-Mail Reporting? [no]: yes
E-mail Recipient Address []: administrator@company.com
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.
Task Comment Check
VERIFY / UPGRADE THE XSCF FIRMWARE

The XCP product notes detail the upgrade procedures:
Fujitsu SPARC M12/Product Notes (XCP version 3060) – to be found within any of the Fujitsu
SPARC M12 User Manual Sets.
Login as user eis-installer on admin network 0. ssh eis-installer@192.168.10.10
eis-installer@192.168.10.10's
The admin network should work at this time. password: password
Otherwise use the serial connection. XSCF>
Determine the installed firmware version – XSCF> version -c xcp

XSCF#0 (Active )
3021 is displayed. BB#00-XSCF#0 (Master)
Current build version is 3060. If an upgrade is XCP0 (Current): 3021
XCP1 (Reserve): 3021
not required, skip the update sequence. BB#01-XSCF#0 (Standby)
XCP0 (Current): 3021
The system firmware updates for the Fujitsu SPARC M12 servers can either be found on
EIS-DVD-ONE in directory .../sun/patch/SYSFW/FJM12 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).
EXAMPLE 1 Downloading a Version from an http Server
XSCF> getflashimage -u <user> http://imageserver/images/BBXCP30xx.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/BBXCP30xx.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/BBXCP30xx.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 30xx
Now update the firmware:
XSCF> flashupdate -c update -m xcp -s 30xx
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:
Mar 04 10:37:28 m12-2s-xscf.usan1 XSCF flashupdate[561]: XCP update has been
completed (XCP version=30xx)
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
XSCF have the same version.
XSCF> version -c xcp
Single BB:
BB#00-XSCF#0 (Master)
4 BB:
BB#00-XSCF#0 (Master)
BB#01-XSCF#0 (Standby)
BB#02-XSCF#0
BB#03-XSCF#0
More than 4BBs:
XBBOX#80-XSCF#0 (Master)
XBBOX#81-XSCF#0 (Standby)
BB#00-XSCF#0
BB#01-XSCF#0
etc..
Task Comment Check
CONFIGURE THE XSCF TO USE ASR

The EIS team has not been able to verify this functionality. 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 ≥5.6.1.3 (which is not currently available).
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.
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 M12 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 M12 XSCF. The XSCF> rastest -c test
registered contact will receive a *Test*
Service Request email to confirm the test
SR creation was successful.
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).
If desired (rarely used) configure the XSCF as XSCF> man setldap
XSCF> man setldapssl
client to an external authentication service. XSCF> man setad
There are 3 possibilities:
• LDAP
XSCF> showldap
• LDAP over SSL XSCF> showldapssl
XSCF> showad
• 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 M12-2S-
23-xyz-BB0 joe.sample@xyzbank.com
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
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 eis-installer@192.168.10.11
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.
We understand that all M12 servers will have XSCF> showcod
the license keys pre-installed at the factory –
verify this. Skip the next three 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 24

XSCF> showcod
In this example, 24 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 M12 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 4 physical partitions can be
configured on the SPARC M12-2S. Only one physical partition can be configured on the SPARC
M12-2, 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, 4 PSBs are assigned to PPAR0:
XSCF> setpcl -p 0 -a 0=00-0 1=01-0 2=02-0 3=03-0
Assign all available PSBs to PPAR0. In this example, 4 PSBs are assigned to PPAR0:
XSCF> addboard -c assign -p 0 00-0 01-0 02-0 03-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"
Task Comment Check
SUNVTS CPU/MEMORY TEST OF ENTIRE PLATFORM

SPARC M12 systems currently manufactured will be supplied pre-loaded with Solaris 11.3 and
SunVTS 8.1.0. This enables the testing of the entire platform with SunVTS with a minimum of
effort.
Unless the server has been stored for some time they will be in the following state:
• S11.3 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.
Set the terminal size
resize
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.
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
1310. 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 1310 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 1310 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: PCIBOX1310.tar.gz Do NOT use firmware prior to 1310 on the M12
systems.
Verify that the latest FW is ready to be XSCF> getflashimage -l
..
installed. PCIBOX1310.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 1310
Firmware update is started. (version=1310)
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.
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
XSCF> setpcl -p 1 -a 2=02-0
In this example, 2 PSBs are registered to
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.
ASSIGN CORE LICENCES
Remember: 1 socket → 12 cores
Example for M12-2: XSCF> setcod -p 0 -s cpu 24
Example for M12-2S, 3BB. XSCF> setcod -p 0 -s cpu 48

XSCF> setcod -p 1 -s cpu 24
In this example, we assign 48 cores to PPAR0
and 24 cores to PPAR1:
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 on/off. XSCF> man addpowerschedule
XSCF> showpowerschedule -a -m list
Power capping. Sets limitations for power XSCF> man setpowercapping

consumption. XSCF> showpowercapping
Power-up delay - sets the warm-up operation time XSCF> man setpowerupdelay
XSCF> showpowerupdelay
of the system and the wait time before start.
Memory mirroring. XSCF> man setupfru
XSCF> showfru -a
Optional PPAR configuration: XSCF> man setpcl

• Degradation configuration policy (fru / psb / XSCF> showpcl -a -v
system)
• mem and I/O disabling
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
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 30 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 System Operation and Administration Guide, Chapter
14.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 20.00.10.00
Target a
Unit 0 Disk TOSHIBA AL13SEB600AL14SE 3702 1172123568 Blocks, 600 GB
SASDeviceName 500003942823fb38 SASAddress 500003942823fb3a PhyNum 0
Target b
Unit 0 Disk TOSHIBA AL13SEB600AL14SE 3702 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 (choose 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 AL13SEB600AL14SE 3702
Task Comment Check
Disk 1
Secondary Optimal
Target b TOSHIBA AL13SEB600AL14SE 3702
{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 20.00.10.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
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.
Task Comment Check
COMPLETION
Verify / correct environment. ok devalias
ok printenv
Return to XSCF (if required). ok #.

XSCF>
INFORMATION: PLATFORM MINIMUM SOFTWARE REQUIREMENTS

The minimum Solaris requirements is a follows:
• Oracle Solaris 10 Update 11 (HW 01/13).
OVM 3.2 or later must be installed even if no LDOMs are used
OR
• Oracle Solaris 11.1 SRU11.1.21.4.1
Preferred is Oracle Solaris 11.3 with SRU 17.5 (EIS-DVD 24FEB17) or later.
• Firmware XCP 3021 for M12-2 and M12-2S
• Firmware XCP 3030 for M12-1
The latest XCP firmware is recommended. Normally, only the 2 most recent releases of XCP
firmware are actively supported; currently this is XCP 3060 and XCP 3053.
EIS strongly recommends that the most recent update of the required operating system together
with the latest EIS-DVD are used.
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 M12 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 (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 29), there are
several possible methods for installing the PPARs including:
• Install each PPAR from Solaris DVD using a USB local drive.
The MOS Document equivalent of M10’s 1553734.1 does not yet exist.
• 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 3060 Product Notes (via the M12 Documentation Library) to ensure that the
Solaris Installation meets the minimum requirements.
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 30.
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
Task Comments Check
ADDITIONAL ACTIONS
Optionally configure the NTP client. Follow Template in /etc/inet/ntp.client. Copy into
customer's site policy. /etc/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 utility4 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
ORACLE FLASH ACCELERATOR F320 PCIE CARDS
Solaris 11.3 SRU17 (minimum) is required to support the F320 card.
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
4 SAS2IRCU_P20 (20.00.00.04) for Solaris only is available on ≥EIS-DVD 19JUL17.
Task Comments Check
Confirm that the expected number of drives are visible to Solaris (example below is from a
server with 2 NVMe 3.2 TB drives off a PCIe NVMe switch card):
# nvmeadm list -v
SUNW-NVME-1
PCI Vendor ID: 0x144d
Serial Number: S2LHNA0HC05240
Model Number: MS1PC2DD3ORA3.2T
Firmware Revision: KPYABR3Q
Number of Namespaces: 1
SUNW-NVME-2
PCI Vendor ID: 0x144d
Serial Number: S2LHNA0HC05239
Model Number: MS1PC2DD3ORA3.2T
Firmware Revision: KPYABR3Q
Number of Namespaces: 1
Decoding the firmware version appears to be complex:

• KPYA8R3Q translates to FW CS2.6.
• KPYABR3Q translates to FW CS2.9 (shown in the example above).
• KPYAGR3Q translates to FW CS3.3.1.
FIRMWARE VERIFICATION & UPDATE
See the Oracle Flash Accelerator F320 PCIe Card Documentation Library
Check the Firmware Revision value in the nvmeadm list -v output above against the
patch Readme to determine if an update is required:
• P26758830 3.2TB NVME (F320 AIC/3.2TB SFF) SW 1.3 Firmware (FW CS3.6)5.
Unzipping the patch creates directory Firmware which includes an HTML Readme
file.
The patch is available on EIS-DVD-ONE in .../sun/patch/firmware/FLASH.
If an update is required follow the instructions in the Oracle Flash Accelerator F320 PCIe
Card and 3.2TB NVMe SSD Product Notes, Section Update the NVMe Storage Drive
Firmware.
Reboot the PPAR.
8-PORT 12GBPS SAS-3 HBA (EXTERNAL)
Refer to Fujitsu M12: Firmware for the Various Hardware Components used on Fujitsu
M12..
The MOS Document equivalent of M10’s 2047847.1 does not yet exist.
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
5 SW 1.3 for the F320 card is available on EIS-DVD ≥18OCT17; SW 1.2 is available on EIS-DVD 26APR17 to
30AUG17.
Task Comment Check
FINAL WORK ON THE XSCFU

Snapshot Method I:
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.
Task Comment Check
Give users the appropriate privileges. Note XSCF> setprivileges super-admin
platadm useradm auditadm fieldeng mode
that the privileges should given all at once (not XSCF> setprivileges less-super-admin
cumulative). fieldeng
The mode privilege allows to change to service etc.
mode, with appropriate password.
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
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
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 EIS-SUPPORT_WW_GRP@oracle.com .

Partners should mail to: SUPPORT-PARTNER-QUESTIONS_WW_GRP@oracle.com .

Sparc Fjm12

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sparc Fjm12

Uploaded by

Copyright:

Available Formats

EIS Installation Checklist for Fujitsu SPARC M12 Servers

M12-1 / M12-2 / M12-2S

The following additional EIS Installation Checklists will be required:

1 XCP 3060 is on EIS-DVD ≥25APR19; XCP 3053 is on EIS-DVD ≥24OCT18.

Collect the provided system records. File away carefully!

Collect documentation together. Give to customer during handover.

Environment Measurements: Verify that conditions are met.

HARDWARE INSTALLATION & CABLING

Connect the XSCF LAN cables.

Slide the mode switch to “Service”.

Continued on next page

Install optional internal disks. SPARC M12-2/M12-2S Service Manual, Chapter

Connect the GbE LAN cables.

Slide the mode switch to “Service”.

Install optional internal disks. SPARC M12-2/M12-2S Service Manual, Chapter

Go to Section Power Up on Page 9 of this checklist.

PRE-INSTALLED M12-2S IN 1 OR 2 RACKS

Task Comment Check

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

INITIAL SERVICE PROCESSOR (XSCF) LOGIN, HW STATUS CHECK

Change the password policy if desired. XSCF> showpasswordpolicy

Create users3. XSCF> adduser eis-installer

Verify user settings. XSCF> showuser -l

MANDATORY XSCFU CONFIGURATION

Remove all already set up networks and routes.

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

Admin network 1, optional recommended for redundancy:

Set hostname and domain name:

Continued on next page

Admin network 1, optional recommended for redundancy:

Set hostnames and domain name:

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

Admin network 1, optional recommended for redundancy:

Set hostnames and domain name:

NAME SERVICE SET UP (RECOMMENDED)

XSCF IP PACKET FILTERING SET UP (OPTIONAL)

CONFIGURE E-MAIL REPORT

APPLY THE NETWORK SETUP

Review all the displayed settings at this stage.

SET THE ALTITUDE

VERIFY / UPGRADE THE XSCF FIRMWARE

Determine the installed firmware version – XSCF> version -c xcp

EXAMPLE 2 Downloading a Version from an FTP Server

EXAMPLE 3 Downloading From a USB Memory Stick

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

CONFIGURE THE XSCF TO USE ASR

Disable the SNMP agent: XSCF> setsnmp disable

Add ASR Manager system as trap destination:

Enable the SNMP agent: XSCF> setsnmp enable

Enable SNMP v1v2: XSCF> setsnmp enablev1v2c community

Verify SNMP settings to make sure trap XSCF> showsnmp

ACTIVATE THE ASR ASSET (FROM THE ASR MANAGER SYSTEM)

Disconnect from the ASR Manager system. # exit

COMPLETION OF ACTIVATION IN MOS

Select the Systems tab.

OPTIONAL ADMINISTRATION CONFIGURATION

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

To connect to the BUI , point browser to:

FINAL STEPS, TESTS AND VERIFICATION

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

Verify networking: XSCF> shownetwork -a

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

Verify error reporting: XSCF> showsmtp

Verify environment: XSCF> showenvironment temp