Exalytics X5 Nov 2016

EIS Installation Checklist for the
ORACLE® Exalytics X5-4 In-Memory Machine
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.
• 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.
• This checklist covers the Exalytics X5-4 Machine which is based on the Oracle
Server X5-4.
• The system is delivered with the Exalytics Base Image (based on Oracle® Linux)
pre-installed.
• The installation should be prepared using EISdoc V4.
• For systems to be rack mounted the racks must be as defined in the Oracle System
Handbook.
• It is not intended that this checklist be handed over to the customer.
• Feedback on issues with EIS content or product quality is welcome – refer to the
last page of this checklist.
Serial Number Hostname

Exalytics X5
Oracle Internal and Approved Partners Only Page 1 of 38 Vn 1.5 Created: 23 Nov 2016
ENGINEERED SYSTEMS ENTERPRISE SUPPORT TEAM EEST
If a Field Support Engineer (FSE) requires assistance while installing an Engineered
System, a streamlined method of engaging an Engineered Systems Enterprise
Support Team (EEST) engineer when the SR owner is not available is described
below.
The SR referred to is the installation SR.
An FSE would use this option if they are onsite and require immediate assistance
from EEST. This process is specifically for FSE Callbacks for hardware,
installation and Field Change Order (FCOs) support and should NOT be used by
ACS or partners.
The complete process is described in this Oracle-internal link under the Tasks tab.
Ensure that you understand the contents before going onsite.
Task Check
INSTALLATION OVERVIEW– EIS DELIVERABLES

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 Oracle Exalytics X86 In-Memory Machine.
MEMORY DIMM FAULT BEST PRACTICES

TSC are seeing many DIMMs being replaced in the field due to initial boot up and
Memory DIMM fault either due to Memory DIMM movement during shipping or
improper seating during memory upgrades.
If Memory DIMM faults are encountered during the installation or upgrade of any
engineered systems, please follow the "BEST PRACTICE" as supplied by the
hardware team.
Best Practice for resolving DIMM Faults during Installation or upgrade:
1. We (TSC) are recommending the reseating of Memory DIMMs when seeing
faults during installation or memory upgrades, as a first step.
2. If we see these failures outside of upgrades or rack installs, we don't want to take
the chance and risk of a second visit if they're truly failed Memory DIMMs. So
we recommend, in these instances, to simply replace the Memory DIMM. If the
replaced Memory DIMM experiences Training errors, then it might be prudent
to reseat the Memory DIMM.
Task Comment Check
PREPARATION
EIS Site-Audit Report complete? EISdoc V4:
File EIS-SiteAudit-Racked-Item.odt
The X5-4 server requires 3 rack-units
(RUs) of space.
EIS Installation Configuration Plan & EISdoc V4:
Test Procedures Plan complete? Use appropriate BUILD & TPP
templates, inserted into “Master” files
(Chapter Servers):
EIS-BUILD-Server-ExalyticsX5.odt
EIS-TPP-Server-Exalytics.odt
FABs/EIS-ALERTs reviewed?
Customer action: If name service IP addresses are required for both the
(DNS, NIS) in use, ensure that new platform & the ILOM Service Processor.
hostnames, IP addresses etc. have been
correctly entered on the name server.
The Exalytics In-Memory Machine is based upon the Oracle Server X5-4:
http://docs.oracle.com/cd/E56388_01/index.html
For reference the latest Oracle Exalytics Documentation library can be found
here: https://docs.oracle.com/cd/E62968_01/index.htm
EXALYTICS INSTALL IMAGE & OTHER DOWNLOADS
Early shipments of the Exalytics X5-4 servers were imaged with Exalytics
base image version 2.0.0.0_el5. However the X5-4 system requires the
2.0.0.0_el6 image for proper hardware support. If the server being installed
has the el5 image then the el6 image will need to be applied during the
installation. OS image 2.0.0.0_el6 is available by downloading V76311-
01.iso from the Oracle Software Delivery Cloud OSDC. This image is a 4.1
GB file and should be downloaded prior to going on-site so that it is
available for use.
Use the following steps to navigate through the Oracle Software Delivery
Cloud OSDC and download this image for use:
1. Connect to the Oracle Software Delivery Cloud (formerly E-Delivery)
located at: http://edelivery.oracle.com
2. Select the blue Sign In button. You will be asked to enter your Oracle
SSO (if you have an open session already signed on it will probably not
request the SSO again).
3. Accept the Export Restrictions agreement.
4. Do NOT switch to the “original” Oracle Software delivery Cloud.
5. In the Product field, enter: Exalytics In-Memory Software.
6. Click on Select Platform and select Linux x86-64.
7. The Selected Products window should show a single line for Exalytics
In-Memory Software – press the Continue button at the bottom right of
the screen.
8. In the next screen you should see a line that is pre-selected similar to
Exalytics In-Memory Software 2.0.0.0.0 for Linux x86-64, 17 files –
press the Continue button at the bottom right of the screen.
Task Comment Check
9. A Oracle Standard Terms and Restrictions pop-up will appear, scroll
to read the agreement and click the radio button I have reviewed and
accept the terms... then press the Continue button at the bottom right of
the window.
10. You will be presented with several available downloads. Click on the
link for V76311-01.iso Oracle Exalytics Base Image 2.0.0.0.el6 for
Linux x86-64 4.1 GB and save the file V76311-01.iso to your system for
use at the customer site.
If the system is re-imaged with the V76311-01.iso download then to fully
support the X5-4 hardware configuration patch 21258871 will also need to be
applied. This patch should be downloaded from MOS prior to going on-site
so it is available for application.
Re-imaged systems will also need to be patched to address bugid 19916135.
Download the following patch from MOS:
• Patch 21562067: EXALYTICS IMAGE 2.0.0.0EL6 SHOWS
CONSTANT PCI EEH BUSY MESSAGES.
All systems will require Version 2.3.3 or later of the Oracle Hardware
Management Package to ensure that the installed version is up to date (this is
to make sure the system is not affected by bugid 21962254 which can cause
the system to hang in the BIOS during a reboot). The latest OHMP package
should be downloaded from MOS. At the time this document was published
the latest version was 2.3.6 this is available via the following:
• Patch 23641814: Oracle HMP 2.3.6 for Oracle Linux 6
The Exalytics X5-4 is based upon the Oracle Server X5-4; at the time this
document was published the latest firmware release available for this
platform was SW 1.1.1. It is recommended that the latest system firmware
release be applied to the system at install time if it is not yet already applied.
X5-4 SW 1.1.1 (patch 22393676) is on EIS-DVD ≥20JUL16.
The patch should be obtained prior to going on-site for the installation and be
available to the engineer either on their laptop or on a USB flash-drive so
that it can be applied to the Exalytics server if needed.
The patch may also be obtained from MOS via the following:
• Oracle Server X5-4 SW 1.1.1 Firmware Patch 24297965.
Checklist of the downloads listed above that should be collected before going
on site and be available for use during the install:
• 2.0.0.0EL6 image V76311-01.iso
• Exalytics X5-4 Patch 21258871
• Exalytics 2.0.0.0el6 kernel update Patch 21562067
• Oracle HMP 2.3.6 for Oracle Linux Patch 23641814 (or later)
• ILOM/BIOS Firmware patch 24297965 (or later)
Task Comment Check
UNPACKING
Delivery complete?
Collect the white Customer Information File away carefully!
Sheets (CIS).
Allow the system to acclimatise (power Refer to EIS standard “Acclimatisation of
off) at the customer site. Oracle Hardware Products”.
Unpack outside data center to ensure no Collect packing material together for
contamination/dust is released inside disposal.
customer's controlled environment.
Verify all packing material has been Fans & air vents must be free to operate.
removed, i.e. nothing is blocked.
Gather excess parts, cables etc. in a
box.
Collect documentation together. Give to customer during handover.
Request licenses where required. Oracle or customer requests licenses
RACKMOUNTING – WHERE APPLICABLE

Always load equipment into a rack from the bottom upwards so that it will
not become top-heavy and tip over. Deploy the rack's anti-tilt bar to prevent
the rack from tipping during equipment installation.
Install one mounting bracket on each Sun Rack II 1042
side of the server. Sun Rack II 1242
The number of servers supported in a given 3rd Party ANSI/EIA 310-D-1992 or IEC
rack depend on the power & cooling available. 60927 compliant cabinet.
Install one slide-rail assembly to each Slide rail kits:
side of the rack. • X5-4: 371-4791.
Cable Management Arm 371-4812.
Slide the server into the rack. Ensure unobstructed airflow to the rear of
the units when cabling.
ASSEMBLY/CABLING
Note the serial numbers.
Distribute systems across power-sequencers considering failure-safety.
Connect grounding cables.
Environment Measurements:
temperature & humidity.
Label the cables clearly.
Use cable binders. Air filters must be easily accessible, thus
cables should not be laid too tightly.
ASSUMPTIONS
In an EIS installation the following assumptions are made:
• The root password for the Exalytics system OS and ILOM has been set to
welcome1 at the factory.
• EIS recommends that connections from the system to the customer's network
should not be made until recommended during the steps detailed in this
checklist. Connecting cables before power on could cause undesirable
interactions due to possible presence of a duplicate IP address in the Customer's
environment.
• The installing Engineer should have a laptop with the proper cables, adapters
and software utilities to allow for network connections to the Host and SP also
the serial connection to the ILOM's RJ45 serial port. A small desktop switch
may also be useful (but not required) to allow connections to both the ILOM and
Host network connections simultaneously during install.
• The Engineer performing these steps should have access to the customer's
network connection and configuration preferences/requirements. This will
include the IP addresses for all Ethernet and/or InfiniBand connections to be
configured, netmask/gateway settings, hostname, domainname, NTP and DNS
server addresses. This information should have been collected as part of the pre-
site checklist – also available via the EIS Installation Configuration Plan
(EISdoc V4).
Task Comment Check
ILOM SERVICE PROCESSOR (SP) CONFIGURATION

The ILOM on an Exalytics system is pre-configured with the following
network settings:
ipdiscovery=static
ipaddress=192.168.1.200
ipgateway=192.168.1.100
ipnetmask=255.255.255.0
Connect the Power Supplies to two separate PDUs supplying high-line AC
input (200-240V). The ILOM will begin to boot as soon as AC power is
applied.
Note: The Exalytics system is a four CPU configuration of the Oracle Server
X5-4 and requires high-line AC input (200-240V). If low-line AC input
(100-127V) is used the system will not power up.
CONFIGURING ILOM WITH THE CLI & A SERIAL CONNECTION
This section describes how to change the ILOM's default IP setting using the
CLI and a serial line connection.
Establish a serial connection to the SP E.g. When using a laptop start a terminal
Serial Management Port (SER MGT). interface to the serial port that is
The default serial port speed is 9600 baud connected to the ILOM SP.
with no flow control.
Alternatively you can use a network connection to the ILOM, configure your
laptop for the default network by using the following settings:
IP address: 192.168.1.10
Netmask: 255.255.255.0
Gateway: 192.168.1.100
then connect the laptop to net management port using a Cat 5 cable.
Log in to the ILOM SP. User = root
Pwd = welcome1
Set the working directory. cd /SP/network
Enter the following commands to The following are example values

specify a static Ethernet configuration. set pendingipaddress=129.144.82.26
set pendingipnetmask=255.255.255.0
Note that there are no spaces in the set pendingipgateway=129.144.82.254
command line structure. Replace the set pendingipdiscovery=static
set commitpending=true
example values with the customer set state=enabled
supplied values.
Note that the last command may require
several seconds to complete.
If you used the network connection to perform the above steps you will lose
connectivity to the ILOM when the new network settings take effect. You
will need to set the laptop to use an IP address within the new subnet that
was just set to make a network connection again.
Verify the changes. show /SP/network
cd /SP
Set the ILOM hostname to the name set hostname=exalytics0-sp
provided by the customer (exalytics0-sp
is an example value used here).
Task Comment Check
CHECKING THE SERIAL NUMBER AND SYSTEM IDENTIFIER

INFORMATION
This section details how to check that the system_identifier and serial
number information is set correctly in the ILOM.
Check and record the system's serial The serial number can be located on the
number. RFID Tag located at the front of the
server on the bottom leftmost corner.
Compare the physical serial number to the information stored in the ILOM.
The “/SYS product_serial_number” field should match the serial information
from the RFID Tag and the “SP system_identifier” field should show
“Oracle Exalytics X5-4 <System SN>”
To examine these settings:
-> show /SYS product_serial_number
/SYS
Properties:
product_serial_number = 1506NMH99D
-> show /SP system_identifier
/SP
Properties:
system_identifier = Oracle Exalytics X5-4 1506NMH99D
If the system_identifier is not set correctly set it manually:

-> set /SP system_identifier="Oracle Exalytics X5-4 1506NMH99D"
Set 'system_identifier' to 'Oracle Exalytics X5-4 1506NMH99D'
CONFIGURING THE SP'S CLOCK PROPERTIES VIA CLI

Refer to the Oracle Integrated Lights Out Manager 3.2 Information Library-
http://docs.oracle.com/cd/E37444_01
To examine the current settings:
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Wed Jul 1 19:23:24 2015
timezone = GMT (GMT)
uptime = 0 days, 02:59:29
usentpserver = disabled
If required, the time-zone can be changed from GMT (default) to EST (or
whichever time-zone is appropriate for the customer's location):
-> set /SP/clock timezone=EST
Task Comment Check
To manually set the ILOM clock property values:

-> set /SP/clock datetime=MMDDhhmmYYYY
Example:
-> set /SP/clock datetime=070115252015
Set 'datetime' to '070115252015' [Wed Jul 1 15:25:00 2015]
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Wed Jul 1 15:25:18 2015
timezone = EST (EST)
uptime = 0 days, 03:01:43
usentpserver = disabled
To synchronise the SP's clock property values with an NTP server set the
NTP server address (IP shown here is an example – use the Customer’s
preferred IP address) and enable usentpserver:
-> set /SP/clients/ntp/server/1 address=129.144.82.254
Set 'address' to '129.144.82.254'
-> set /SP/clock usentpserver=enabled

Set 'usentpserver' to 'enabled'
EXAMINING THE FIRMWARE/BIOS VERSIONS USING THE CLI

Display the ILOM version & build number using the ILOM version
command, shown is 3.2.5.10.a build 99931 (which requires updating):
-> version
SP firmware 3.2.5.10.a
SP firmware build number: 99931
SP firmware date: Fri May 15 22:22:13 EDT 2015
SP filesystem version: 0.2.10
PREPARING FOR THE UPDATE

When this document was written the latest available firmware version for the
Sun Server X5-4 was:
• SW 1.1.1: ILOM 3.2.6.20.a, BIOS 36.02.11.00, Build 110631
It is recommended that the very latest firmware available for the Oracle
Server X5-4 at the time of installation be applied. Check the MOS patch
download site and/or the latest EIS-DVD release to confirm what the latest
available release is at the time of deployment.
X5-4 SW 1.1.1 is on EIS-DVD ≥20JUL16.
If the ILOM & Build numbers displayed by the version command above
match the current version, then skip to section COMPLETING THE SP on
page 11.
If the system does not have this version of system firmware or later obtain
the required patch and update the system firmware so that it is current with
the latest release available.
Task Comment Check
Reset the service processor before beginning the flash upgrade. The host
must be powered off. Use one of the following methods:
• From the SP graphical web interface expand the ILOM Administration
link in the left column then select Maintenance. In the main panel select
the Reset SP tab. Then press the Reset SP button.
• From the CLI, use the following command: reset /SP
USING THE CLI TO UPDATE THE FIRMWARE / BIOS

Ensure that the OS on the platform is
shut down.
If the upgrade is to be performed via the CLI, a TFTP server is required to
be set up – see MOS Document ID 1004474.1. Copy the required firmware
file from the EIS-DVD to the TFTP server into the directory /tftpboot.
From the SP update the firmware (correct values need to be inserted):
Log in as any user with Administrator privileges.
Enter the following command to download the new ILOM firmware image:
->load -source tftpURL
For example (enter command on single line):

-> load -source tftp://xxx.xxx.xxx.xxx/ILOM-3_2_6_20_a_r110631-
Sun_Server_X5-4_X5-8.pkg
Refer to guide 820-1188-xx for more information.

The BIOS and SP firmware are updated & the SP will reset.
After the update is complete, log back ssh -l root <ip-addr-of-sp>
Pwd = <the-root-password>
in to the SP via ssh.
Verify the version to confirm that the update was successful:
-> version
SP firmware 3.2.6.20.a
SP firmware build number: 110631
SP firmware date: Sat Jun 11 03:00:40 EDT 2016
SP filesystem version: 0.2.10
USING THE GUI TO UPDATE THE FIRMWARE / BIOS

Log in to the ILOM SP as https://<SP-ipaddr>
Administrator to reach the ILOM User = root
webGUI. Only accounts with Pwd = welcome1
Administrator privileges are enabled to
upgrade the SP firmware.
Expand the ILOM Administration Enter location of the update file and
link in the left column then select select upload.
Maintenance. In the main panel select Select the Preserve existing
the Firmware Update tab. Then press configuration check-box to ensure you
do not lose the ILOM's current
the Enter Update Mode button. configuration then press the Start Update
button.
Task Comment Check
The final step of the upgrade will reboot the SP. After the update is
complete you will need to wait for the SP to complete it's reboot and then
log back in to the ILOM. Check the System Firmware Version reported in
the General Information section of the Summary page to confirm that the
update was successful.
COMPLETING THE SP
After completing the setup and -> exit
confirming the system firmware is up to
date, exit.
Connect the net management port of the If the customer network is not yet
system to the customer's management ready/available the connection can be
tested using a laptop as described earlier.
network at this time using a Cat 5 cable.
Test to confirm that the ILOM can be
accessed via the network by either
using ssh or a browser.
If the customer's management network does not allow for or cannot
accommodate a connection of the Engineer's laptop then do not yet connect
the ILOM to it. Configure the laptop with an address within the subnet
recently configured on the ILOM and perform the following steps while
connected to the ILOM with a network connection to the net management
port from the laptop.
Task Comment Check
POWERING ON & SETTING UP THE HOST

Using either a network connection via the customer's administration network
or a direct connection to the ILOM's net management port from a laptop use
a web browser to connect to the ILOM WebGUI using the configured IP
address.
Example: https://129.144.82.26
Log in to the ILOM using the root user User = root
and default password. Pwd = welcome1
Start the JAVA console KVMS. On the ILOM GUI expand the Remote
Control link in the left column then select
Redirection. In the main panel select
Launch Remote Console to bring up the
Remote Console Java application. (Note
that the “Use video redirection” button
should be selected)
CONFIGURING THE UNIVERSAL FIBER CARD MODE
The Exalytics X5-4 server has two Qlogic 16Gb FC / 10GbE dual-port FC/
FCoE LP PCIe Adapters installed. These Universal HBAs have two
operating protocol modes: Fiber Channel (FC) Only mode or Converged
Network Adapter (CNA) (or, FCoE) mode. The operating mode is
dependent upon the installed sfp+ modules and the mode setting of the card.
The mode setting on the card must match the type of sfp+ modules installed
(ie. if a pair of 10GbE FCoE modules are installed the card's mode must be
set to CNA, if a pair of 16 Gb FC modules are installed the card's mode must
be set to FC).
Note that the sfp+ modules are always installed in a matched pair, you cannot
mix two different sfp+ module types on the same PCIe adapter.
By default these cards are normally shipped with their mode set to CNA
however it is best practice to double-check the mode settings if the cards will
be used. If the cards are not going to be utilized at all then they can be left
set to their default modes and you may skip to the next section of powering
on the server.
If the customer will be installing 16Gb FC sfp+ modules to connect the card
to a SAN then the mode will need to be changed to FC. If the cards are to be
used as Ethernet devices then the mode settings should be checked to ensure
that they are properly set to CNA mode.
To change/check the mode settings the system will need to be brought up into
the UEFI setup menu. To do this the Boot Mode of the server needs to be set
to “UEFI” instead of the default “Legacy”.
Details on changing the Qlogic card's operating mode may be found in the
card's Installation Guide:
http://docs.oracle.com/cd/E24651_01/html/E24460/index.html
Task Comment Check
Set the system to boot to BIOS setup. On the ILOM GUI expand the Host
Management link in the left column then
select Host Control. In the main panel
pull down on the menu selection and
select BIOS as the next boot device and
then click Save.
Power on the server. Either physically depress power/standby
button located at the front top left corner
of the system or use the WebGUI and
expand the Host Management link in the
left column then select Power Control.
In the main panel select action Power On
and Save
MONITOR THE SERVER INITIALIZATION VIA THE CONSOLE
Due to the Exalytics system specific configuration (specifically the large
amount of system memory) it may take up to 15 minutes for the BIOS
initialization process to complete. While the BIOS performs it's initial start-
up a progress bar will be shown at the bottom of the screen and status codes
will be displayed to the bottom right. The initialization may reset and clear
the screen several times resetting the progress bar each time. This is normal.
If the system was set to boot to BIOS setup as described in the previous
section the server will automatically go to the BIOS setup screen (if you need
to enter the BIOS setup but did not set the next boot setting to automatically
go into the BIOS setup then press F2 when prompted to enter the BIOS
setup). If you do not need to set the Universal card mode then there is no
need to change any BIOS settings, exit the BIOS setup and skip to the next
section “Checking and re-imaging the server” on Page 14.
To get to the UEFI setup menu the system boot mode needs to be changed
from the default “Legacy”. In the BIOS setup screens use the arrow keys to
navigate to the “Boot” tab. In the main window the topmost entry should be
the option to change the Boot Mode. Press Enter and a pop-up will appear
to allow the setting to be changed, select UEFI then press Enter.
Then go into the IO tab and navigate to the “Add In Cards” section. For any
card that you need to check/change the settings you will need to enable the
UEFI driver enable setting. The Universal Fiber cards are in slots 8 and 11
use the arrow keys to select each that you need to change and press enter.
Then in the next screen press enter after highlighting the “PCI-E Option
ROM or UEFI Driver Enable” line. In the pop-up highlight “enabled” and
press Enter.
In the ILOM WebGUI go to the Host Control screen then select and save the
next boot device to be BIOS again. Then in the console screen press F10 to
save the configuration and exit. The system will reset and boot back into the
UEFI setup.
Task Comment Check
When the system comes back up you will be presented with the UEFI setup
screen. Use the arrow keys to navigate to the Advanced tab. In the main
panel there is a section entitled RunTime Uefi Drivers. Use the arrow keys
to navigate down to this section and at the bottom you will find four entries
for the four ports on the fiber cards. The cards will look and behave
differently in the UEFI setup menus depending upon the currently selected
mode.
If the card is configured for CNA mode then they should look like:
Port 1 - 7101674, Sun Storage 16Gb FC PCIe
Universal HBA, Qlogic
If the card is configured for FC mode then they should look like:
7101674, Sun Storage 16Gb FC PCIe Universal HBA,
QLogic 7023303 - 2100000E1E11CC80
The first two listed should be the card in PCIe slot 8 and the second two are
the card in slot 11.
For cards currently in CNA mode highlight and select the adapter Port 1 and
then in the next screen select Function Configuration. Then highlight the
Personality Setting option at the bottom and press enter. Highlight CNA to
set the card to network mode or highlight FC to set the mode for a SAN
connection, then press enter. Do this for each of the entries as needed.
For cards currently in FC mode highlight and select the adapter and then in
the next screen select Advanced Settings. Then highlight the Adapter
Personality option at the bottom and press enter. Highlight CNA to set the
card to network mode or highlight FC to set the mode for a SAN connection,
then press enter. Do this for each of the entries as needed.
After the modes have been set as needed the BIOS changes should be set
back to their default settings. Go back into the IO tab and navigate to the
Add In Cards section. For any card that enabled the UEFI driver enable
setting you should set it back to it's default of disabled. Then navigate to the
Boot tab and change the Boot Mode setting back to Legacy and then press
F10 to save and exit. The system will reset and re-initialize (Note that the
system requires the Boot Mode set to Legacy to boot properly. If the step to
set this back is skipped you may not be able to get the OS to boot properly).
Note: the steps above are based on an Exalytics X5-4 server with firmware
release 1.0.1 installed. The UEFI menus may differ slightly with different
firmware release versions. If the menus seen differ from the descriptions
above adjust your actions as needed.
CHECK THE PRE-INSTALLED IMAGE AND RE-IMAGE THE
SERVER WITH OS IMAGE 2.0.0.0_el6 IF NEEDED
After exiting from the BIOS setup allow the server to initialize and boot up
using the pre-installed OS image. As mentioned earlier in this document the
Exalytics X5-4 server requires the 2.0.0.0_el6 image for proper hardware
support. Check the Oracle Linux Server release at the login to see which OS
version is currently installed.
Task Comment Check
The following example shows what is expected from a system that has the
proper 2.0.0.0_el6 image already installed (note the “release 6.6”):
Oracle Linux Server release 6.6
Kernel 2.6.39-400.277.1.el6uek.x86_64 on an x86_64
localhost login:
If instead you see the following login screen then the system has the el5
image installed and a re-image will be needed:
localhost login:
If the server has the el6 image installed then re-imaging is not needed. Skip
to the next section “MONITOR OS BOOT AND LOGIN” on page 16.
If the server currently has the el5 image installed then the system will need to
be re-imaged. Using the previously downloaded V76311-01.iso file re-image
the installed OS with the proper version.
Using the remote console mount the ISO image:
Click KVMS in the upper left-hand corner of the console application and
select the first option “Storage”. A new window will pop-up entitled Storage
Devices. At the bottom-left of the window click Add... a window for
navigating the directory structure and choosing a file is presented. Navigate
to the directory that contains the V76311-01.iso file and highlight it in the
right-hand Files list. The file should appear in the Selection section below
and then click Select. You will now see the path to the selected file listed in
the Storage Devices window and it should be labeled as an ISO Image in the
Device Type column. Click on this listing, then click on the Connect button
at the bottom of the window. The file listing will now be in a gray bar and
some warnings in red lettering will show at the bottom. Click OK to close
the window.
With the virtual cdrom mounted to the system we can now set the system to
boot and install from this image.
In the ILOM GUI expand the Host Management link in the left column then
select Host Control. In the main panel pull down on the menu selection and
select CDROM as the Next Boot Device and then click Save. Then select
Power Control in the left column and select action Reset and Save.
The system will reset and boot from the cdrom image after re-initializing.
Task Comment Check
As mentioned previously the BIOS level initialization may take up to 15
minutes to complete. When it does finish the system will begin to boot from
the install image.
The first screen will present a “boot:” prompt, press enter.
You will then see an Oracle Linux 6 splash screen with boot options. The
default is the topmost option Install or upgrade an existing system. Make
sure this option is highlighted and press enter.
The installation will start and is “hands-free” no further interaction is
required. The install should take approximately 35 minutes to complete.
When the install completes the system will automatically reboot. When the
reboot occurs and the system initialization begins you may disconnect the
cdrom image mount.
Select KVMS - Storage in the remote console then click Disconnect at the
bottom of the Storage Devices window.
MONITOR THE OPERATING SYSTEM BOOT AND LOGIN
After the BIOS initialization finishes the OS will boot. The OS boot should
take approximately 3-4 minutes. When the OS finishes booting login as root
with the default password:
localhost login: root

Password: welcome1
The Exalytics X5-4 system's BIOS settings should be set so that the internal
OS disks are the first boot device. If after BIOS initialization the system
does not attempt to boot from the internal disk controller as a first choice the
Field Engineer should check to make sure the BIOS boot order is set
correctly.
Access the BIOS setup menu by pressing the F2 button when the system
presents the BIOS initialization screen and prompts you. Navigate to the
Boot screen and check the Legacy Boot Option Priority list at the bottom of
the screen. Make sure that the topmost boot option is the RAID controller it
should look like this: [RAID:PCIE2:(Bus 01 Dev 00)PCI RAID Adapter]. If
that is not the topmost boot option change the order so that it is. To save the
setting either press F10 or select Save Changes and Reset in the Exit screen.
The system should now boot normally.
SETUP NETWORK CONNECTION / MEMORY AND CPU CHECK
An Exalytics X5-4 system has twelve possible network ports that can be
configured for use. The Linux OS will assign the network ports as follows:
• eth0, eth1, eth2 and eth3 are the 10G fiber ports provided by the Niantic
cards in PCIe slots 3 and 5.
• eth4, eth5, eth6 and eth7 are the on-board 10G rj45 Ethernet ports.
• eth8, eth9, eth10 and eth11 are the ports on the Qlogic Gannymede
universal fiber cards in PCIe slots 8 and 11.
Task Comment Check
If you want to connect a laptop to the first onboard 10G Ethernet port you
will need to manually configure the port and restart the network service. The
Net0 port is configured as eth4. Edit the /etc/sysconfig/network-
scripts/ifcfg-eth4 file using vi (or similar file editor) and replace the file
contents with the following example (note that the HWADDR and UUID
lines should be taken from the current configuration file so that the
information is correct for the hardware):
DEVICE=eth4
HWADDR=XX:XX:XX:XX:XX:XX
TYPE=Ethernet
UUID=XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
IPADDR=192.168.1.11
NETMASK=255.255.255.0
GATEWAY=192.168.1.100
BOOTPROTO=static
IPV6INIT=no
ONBOOT=yes
HOTPLUG=no
Then restart the network service:

[root@exalytics0 ~]# service network restart
You may then connect a laptop to the net0 port of the system (depending on
your laptop's capabilities a crossover cable or small switch may be needed)
after configuring it for the same subnet as the Exalytics Host as described
previously for connecting to the ILOM net management port.
Be aware that if you are using the network connection for the following steps
you will lose your connection during the network configuration step. Using
the ILOM Java console is the preferred method of connection at that time.
Verify that all memory is present in Linux. The system is configured with
2.0TB of total memory (the MemTotal value output may vary slightly
between OS release versions):
[root@exalytics0 ~]# grep MemTotal /proc/meminfo
MemTotal: 2117892008 kB
Verify that all CPU cores are seen by Linux properly. The system is
configured with four 18-Core Intel Xeon E7-8895 V3 CPU Modules for a
total of 72 physical cores. By default Intel Hyper Threading is enabled so
that two threads per core are presented to the OS, so we should expect Linux
to recognize 144 processors.
[root@exalytics0 ~]# grep -c processor /proc/cpuinfo
144
If any memory or CPUs are missing from the system the faulted components
should be identified using the ILOM event logs and ILOM FMA.
Task Comment Check
INSTALLING HARDWARE OPTIONS

The Exalytics X5-4 server allows for the addition of a memory expansion to
maximize the installed memory capacity to 3.0 TB. If the memory expansion
is to be installed during the initial deployment then it should be physically
installed after the system has had the ILOM configured and the host has
performed it's initial OS boot. This is to confirm that the base hardware is
not showing any faults. If the system is presenting any fault condition
identify the issue and resolve it before proceeding further (if troubleshooting
assistance is needed contact the Oracle Support Center).
If there are no hardware options to install go to the next section "Cabling the
host" on page 19.
After confirming the base system is healthy (previous pages) halt the system:
[root@exalytics0 ~]# halt
When the OS has completely halted remove all AC input to the server and
pull the server out to it's service position within the rack (if necessary remove
any cable connections that have been made to the server). Attach an anti-
static wrist strap and remove the top cover.
If there is a memory upgrade to be installed then there should be quantity: 32
of 32 GB DIMMs which will allow for populating of all empty DIMM slots
within the system. This will result in the system having a total of 3.0 TB of
system memory.
Make sure that your anti-static wrist-strap is still attached and starting with
Memory Riser P0/MR0 (rightmost memory riser when seen from the front)
pull the riser straight up to remove it from the memory riser socket on the
system board. Place the riser on an anti-static mat.
Install the new DIMMs into the riser by aligning each DIMM with the empty
DIMM slots making sure to align the DIMM so that the notch matches the
key in the slot and then gently pressing the DIMM into the slot until the
ejector tabs lock the DIMM into place.
After confirming that all four new DIMMs are properly installed/seated into
the memory riser replace the riser into the memory riser slot from which it
was removed and push the riser in until it locks into place.
Repeat this process for all eight memory risers proceeding from right to left
until all of the new DIMMs are installed and there are no empty DIMM
sockets within the system.
After confirming that all components have been installed and seated properly
replace the top cover of the system and slide the system back into it's normal
operating position within the rack.
Re-attach any cables that had been removed back into the same locations
from which they were removed and then reconnect both AC power cords.
Task Comment Check
Power on the server by either physically depressing the power/standby button
located at the front top left corner of the system or by using the ILOM
WebGUI.
Monitor the system boot and confirm that no faults are logged. Login to the
system and if the memory expansion was installed verify that all 3.0 TB of
memory is present in Linux (the MemTotal value output may vary slightly
between OS release versions):
[root@exalytics0 ~]# grep MemTotal /proc/meminfo
MemTotal: 3176953256 kB
Task Comment Check
CABLING THE HOST

At this point the Host's network cables (on-board 10Gb, InfiniBand, 10Gb
Fiber) should be physically connected to their appropriate switches/panels so
that the network configuration may be completed according to the customer's
network requirements. For the 10Gb Ethernet connections confirm that the
preferred network ports are properly connected to the appropriate switch(es).
For InfiniBand connection to an Exadata see the recommended configuration
below.
EXADATA/BIG DATA CONNECTION RECOMMENDATIONS
For connection to an Exadata or Big Data System the IB cables from the 2-
port QDR InfiniBand HCA in the Exalytics Server should be connected to
leaf switches 1 and 2 of the Exadata or Big Data System. On an Exadata the
following ports on the leaf switches should be free and available for use:
Ports 5B, 6A, 6B, 7A, 7B, and 12A. For a Big Data Appliance ports 5A, 5B,
6A and 6B should be available. If these ports are not available then alternate
unused ports should be utilized.
Connect the IB cable from port 1 of the Exalytics InfiniBand card to an
available port on leaf switch 1 (the lower Sun Datacenter InfiniBand Switch).
Connect the IB cable from port 2 of the Exalytics InfiniBand card to an
available port on leaf switch 2 (the upper Sun Datacenter InfiniBand Switch).
For consistency it is recommended to use similar port locations for the
connection to each switch. Example:
• Connect the IB cable from Exalytics IB port 1 to leaf switch 1 port 5B.
• Then connect IB cable from Exalytics IB port 2 to leaf switch 2 port 5B.
Task Comment Check
SYSTEM ACTIVITIES
APPLY PATCH FOR EXALYTICS X5-4 SUPPORT
If the system was re-imaged using the downloaded 2.0.0.0_el6 image then
patch 21258871 must be applied to support the Exalytics X5-4 hardware
configuration. Use the following steps to apply this update.
If the system shipped with the pre-installed el6 image then this update will
already have been applied. Skip to the next step “UPDATE HARDWARE
MANAGEMENT PACKAGES” on page 21.
Patch file p21258871_2000_Linux-x86-64.zip should have been
downloaded during the Preparation activities on page 3. Transfer this file to
the Exalytics system. This can be done in a number of ways and it is up to
the on-site Engineer to choose the appropriate method depending on the
available resources. Recommended methods are copying from a USB stick
physically attached to the Exalytics system or using ftp/scp with a laptop
connected to the net0 port. Following are examples of two ways of
transferring this file to the server.
Example of transferring the file from a USB flash drive – physically insert
the flash drive into an empty USB slot, then:
[root@exalytics0 ~]# cd /
[root@exalytics0 /]# mkdir /usb
[root@exalytics0 /]# mount /dev/sdc1 /usb
[root@exalytics0 /]# cp /usb/p21258871_2000_Linux-x86-64.zip /tmp
[root@exalytics0 /]# umount /usb
To locate the proper device name (/dev/sdc1 above) use fdisk -l or check the
output of dmesg to see how the USB stick was attached by the OS when
connected.
On a new Exalytics X5-4 system installation a newly attached USB stick will
usually be /dev/sdc1.
An example of using scp on the Exalytics server to copy from a UNIX
system connected to the Exalytics net0 port:
[root@exalytics0 ~]# scp [email protected]:/tmp/ p21258871_2000_Linux-
x86-64.zip /tmp
[email protected]'s Password: *********
p21258871_2000_Linux-x86-64.zip 100% 799KB 799.0KB/s 00:00
Task Comment Check
After transferring the file to the /tmp directory of the server unzip the file
and use rpm to update the packages:
[root@exalytics0 ~]# cd /tmp
[root@exalytics0 tmp]# unzip -d /tmp/p21258871 p21258871_2000_Linux-x86-64.zip
Archive: p21258871_2000_Linux-x86-64.zip
creating: /tmp/p21258871/el6/
inflating: /tmp/p21258871/el6/exalytics-flash-2.0.0.0-6_el6.x86_64.rpm
inflating: /tmp/p21258871/el6/exalytics-scripts-2.0.0.0-11_el6.noarch.rpm
inflating: /tmp/p21258871/readme.txt
[root@exalytics0 tmp]# rpm -Fvh /tmp/p21258871/el6/*rpm
Preparing... ########################################### [100%]
1:exalytics-scripts ########################################### [ 50%]
postInstall (exalytics-scripts) 2 ...
[EXALYTICS_INFO:GENERAL] starting; Tue Aug 11 11:10:04 EDT 2015 ...
[EXALYTICS_INFO:GENERAL] Updating exalytics-node-config file to set
EXALYTICS_INSTALL_TYPE=BM ...
[EXALYTICS_INFO:GENERAL] SERVICE_DISABLEMENTS is missing, so adding default
value SERVICE_DISABLEMENTS=YES ...
[EXALYTICS_INFO:GENERAL] ECHO_INSTALL_COMPLETE_MSG is missing, so adding
default value ECHO_INSTALL_COMPLETE_MSG=YES ...
[EXALYTICS_INFO:GENERAL] finished; Tue Aug 11 11:10:05 EDT 2015
postInstall (exalytics-scripts) 2; done
2:exalytics-flash ########################################### [100%]
postInstall (exalytics-flash) 2 ...
[EXALYTICS_INFO:GENERAL] Updating exalytics-flash-config file to set
FLASH_INSTALL_TYPE=BM ...
postInstall (exalytics-flash) 2; done
preUninstall (exalytics-scripts) 1 ...
preUninstall (exalytics-scripts); nothing to do
preUninstall (exalytics-flash) 1 ...
preUninstall (exalytics-flash); nothing to do
The rpm query command can be used to confirm that the new versions of the
packages have been applied:
[root@exalytics0 tmp]# rpm -q exalytics-flash
exalytics-flash-2.0.0.0-6_el6.x86_64
[root@exalytics0 tmp]# rpm -q exalytics-scripts
exalytics-scripts-2.0.0.0-11_el6.noarch
UPDATE HARDWARE MANAGEMENT PACKAGES

Using the rpm -qa command check the current version of the OHMP
packages installed. If the version is below version 2.3.3 then it must be
updated.
[root@localhost tmp]# rpm -qa | grep hmp
oracle-hmp-tools-biosconfig-2.3.1.1-1.el6.x86_64
oracle-hmp-tools-2.3.1.1-1.el6.x86_64
oracle-hmp-hwmgmt-2.3.1.1-1.el6.x86_64
oracle-hmp-snmp-2.3.1.1-1.el6.x86_64
oracle-hmp-tools-ubiosconfig-2.3.1.1-1.el6.x86_64
oracle-hmp-libs-2.3.1.1-1.el6.x86_64
The above example shows that version 2.3.1 is currently installed and needs
to be updated. If the output shows that version 2.3.3 is already installed skip
to the next step “NETWORK SETUP” on page 25.
Using the same process as above transfer the Oracle HMP 2.3.6 patch file
p23641814_236_Generic.zip to the system (this file should have been
downloaded during the preparation activities on page 4). The following
example assumes that the patch file was transferred to the /tmp directory.
Task Comment Check
After transferring the file to the /tmp directory of the server unzip the file and
change to the /tmp/oracle-hmp-2.3.5.0/packages directory:
[root@localhost tmp]# unzip p23641814_236_Generic.zip
Archive: p23641814_236_Generic.zip
creating: oracle-hmp-2.3.6.0/
inflating: oracle-hmp-2.3.6.0/hmp-prerequisite-installation.txt
inflating: oracle-hmp-2.3.6.0/install.bin
inflating: oracle-hmp-2.3.6.0/hmp_schema.xsd
creating: oracle-hmp-2.3.6.0/packages/
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-snmp-2.3.6.0-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/elxocmcorelibs-10.6.144.21-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-tools-biosconfig-2.3.6.0-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/elxocmcore-10.6.144.21-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/mstflint-1.4-9.mlnx1.5.5r2.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/QConvergeConsoleCLI-1.1.03-22.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-tools-2.3.6.0-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-tools-firmware-check-2.3.6.0-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/elxflashOffline-10.6.144.21-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/ipmitool-1.8.12.4-0.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/ipmiflash-1.8.12.4-0.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/elxocmlibhbaapi-6.2.11.1-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-hwmgmt-2.3.6.0-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-tools-ubiosconfig-2.3.6.0-
1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-wdt-2.3.6.0-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/fm-2.3.5.0.0-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/packages/oracle-hmp-libs-2.3.6.0-1.el6.x86_64.rpm
inflating: oracle-hmp-2.3.6.0/hmp_manifest.xml
inflating: oracle-hmp-2.3.6.0/license.txt
inflating: oracle-hmp-2.3.6.0/readme.html
[root@localhost tmp]# cd /tmp/oracle-hmp-2.3.6.0/packages
Task Comment Check
Then use rpm to update the packages. The following nine packages should
be updated in this specific order (if this order is not followed errors about
package dependencies may be seen):
[root@localhost packages]# rpm -Uvh ipmiflash-1.8.12.4-0.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:ipmiflash ########################################### [100%]
[root@localhost packages]# rpm -Uvh ipmitool-1.8.12.4-0.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:ipmitool ########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-hwmgmt-2.3.6.0-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-hwmgmt ########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-snmp-2.3.6.0-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-snmp ########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-tools-2.3.6.0-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-tools ########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-tools-biosconfig-2.3.6.0-
1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-tools-biosco########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-tools-ubiosconfig-2.3.6.0-
1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-tools-ubiosc########################################### [100%]
[root@localhost packages]# rpm -Uvh oracle-hmp-libs-2.3.6.0-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:oracle-hmp-libs ########################################### [100%]
[root@localhost packages]# rpm -Uvh QConvergeConsoleCLI-1.1.03-22.x86_64.rpm
Preparing... ########################################### [100%]
1:QConvergeConsoleCLI warning:
/opt/QLogic_Corporation/QConvergeConsoleCLI/sfcli.properties saved as
/opt/QLogic_Corporation/QConvergeConsoleCLI/sfcli.properties.rpmsave
########################################### [100%]
Library 2.2 already installed at /usr/lib64/libHBAAPI.so.
[root@localhost packages]#
The following rpm query commands can be used to confirm that the new
versions of the packages have been applied:
[root@localhost packages]# rpm -qa | grep oracle-hmp
oracle-hmp-tools-2.3.6.0-1.el6.x86_64
oracle-hmp-snmp-2.3.6.0-1.el6.x86_64
oracle-hmp-libs-2.3.6.0-1.el6.x86_64
oracle-hmp-hwmgmt-2.3.6.0-1.el6.x86_64
oracle-hmp-tools-ubiosconfig-2.3.6.0-1.el6.x86_64
oracle-hmp-tools-biosconfig-2.3.6.0-1.el6.x86_64
[root@localhost packages]# rpm -q ipmiflash
ipmiflash-1.8.12.4-0.el6.x86_64
[root@localhost packages]# rpm -q ipmitool
ipmitool-1.8.12.4-0.el6.x86_64
[root@localhost packages]# rpm -q QConvergeConsoleCLI
QConvergeConsoleCLI-1.1.03-22.x86_64
Intentionally left blank
Task Comment Check
APPLY KERNEL UPDATE PATCH
If the system was re-imaged using the downloaded 2.0.0.0_el6 image then
patch 21562067 must also be applied to update the Kernel image to avoid
bugid 19916135.
If the system shipped with the pre-installed el6 image then this update will
already have been applied. Skip to the next step “CONFIGURE ILOM
SERIAL CONSOLE” on page 25.
This patch will update the kernel and then reboot the server.
Transfer the patch file p21562067_20000_Linux-x86-64.zip to the /tmp
directory and unzip it.
[root@localhost packages]# cd /tmp
[root@localhost tmp]# unzip p21562067_20000_Linux-x86-64.zip
Archive: p21562067_20000_Linux-x86-64.zip
creating: 21562067/patch/
inflating: 21562067/patch/ksplice-j79zj4o1.tar.gz
inflating: 21562067/patch/kernel-uek-debuginfo-common-2.6.39-
400.277.1.el6uek.x86_64.rpm
inflating: 21562067/patch/kernel-uek-2.6.39-400.277.1.el6uek.x86_64.rpm
inflating: 21562067/patch/kernel-uek-firmware-2.6.39-
400.277.1.el6uek.noarch.rpm
inflating: 21562067/patch/kernel-uek-devel-2.6.39-400.277.1.el6uek.x86_64.rpm
inflating: 21562067/patch/kernel-uek-debuginfo-2.6.39-
400.277.1.el6uek.x86_64.rpm
inflating: 21562067/patch/uptrack.tar.gz
inflating: 21562067/patch/kernel-uek-headers-2.6.39-
400.277.1.el6uek.x86_64.rpm
inflating: 21562067/patch/kernel-uek-doc-2.6.39-400.277.1.el6uek.noarch.rpm
inflating: 21562067/update_kernel.sh
inflating: readme.txt
Change to the patch directory and run the update_kernel.sh script:

[root@localhost tmp]# cd 21562067
[root@localhost 21562067]# ./update_kernel.sh
This script execution will proceed to reboot the host .Are you sure you want
to continue Y/N (Y/y -- to continue , N/n -- to exit):Y
updating the kernel
Preparing... ########################################### [100%]
1:kernel-uek-firmware ########################################### [ 14%]
2:kernel-uek-debuginfo-co########################################### [ 29%]
3:kernel-uek-debuginfo ########################################### [ 43%]
4:kernel-uek ########################################### [ 57%]
5:kernel-uek-headers ########################################### [ 71%]
6:kernel-uek-doc ########################################### [ 86%]
7:kernel-uek-devel ########################################### [100%]
uptrack/
uptrack/lib64/
uptrack/lib64/python2.4/
uptrack/lib64/python2.4/site-packages/
---cut---
package install info cut for brevity
---cut---
uptrack/ksplice-apply
uptrack/ksplice-undo
uptrack/regenerate-crontab
FATAL: Could not load /lib/modules/2.6.39-400.248.3.el6uek.x86_64/modules.dep:
No such file or directory
insmod: error inserting 'ksplice-j79zj4o1_qla2xxx-old.ko': -1 Operation not
permitted
Child exited with status 1
Error loading old code module ksplice_j79zj4o1_qla2xxx_old
The host will reboot now ......
Broadcast message from [email protected]

(/dev/pts/0) at 13:17 ...
The system is going down for reboot NOW!

[root@localhost 21562067]#
Task Comment Check
Please note: After applying the kernel update with patch 21562067 if the
/opt/exalytics/bin/exalytics_CheckSWProfile command is run the system
may report a failure for the kernel version check. This is a known issue due
to bugid 23533250. If this is seen the failure warning should be ignored.
The upgraded Kernel 2.6.39-400.277.1.el6uek.x86_64 is supported on the
Exalytics X5-4 system.
CONFIGURE ILOM SERIAL CONSOLE
After the system completes it's reboot login as root and configure the OS to
allow for console access via the ILOM CLI (refer to MOS Document ID
2117758.1 for more details on this procedure if needed)
Use vi (or you preferred text editor) to edit the /boot/grub/grub.conf file:
[root@exalytics0 ~]# vi /boot/grub/grub.conf
In this file there will be two lines that start with “kernel” add the following to
the end of each of these lines and then save the file (there should be a single
space between the last character of the kernel line and this entry):
console=ttyS0,9600n8 console=tty1
Then use vi to create the file /etc/init/ttyS0.conf with the following contents:
[root@exalytics0 ~]# vi /etc/init/ttyS0.conf
# ttyS0 - agetty
#
# This service maintains an agetty on /dev/ttyS0.
#
stop on runlevel [S016]
start on runlevel [2345] and stopped rc
respawn
exec /sbin/agetty -L 9600 ttyS0
After the next reboot the ILOM console will be accessible as needed.
NETWORK SETUP
After the physical cabling is completed and the rpms are updated execute the
network configuration script and answer the questions as prompted per the
customer's network requirements. The following example configures bonded
interfaces using the on-board 10G ports, the 10G QLogic Ganymede fiber
ports and an InfiniBand connection to an Exadata System. Note that the
script will prompt you to configure ports eth0 through eth7 together. These
are the Niantic fiber ports and the on-board rj45 ports. As detailed earlier the
Niantic card ports are eth0, eth1, eth2, and eth3 while the on-board ports are
eth4, eth5, eth6, and eth7. Make sure to select the correct ports depending on
the customer's requirements. If the Niantic ports need to be configured or
bonded separately from the on-board ports this will need to be done manually
after running the script the current script does not allow for separate
configuration of these ports.
[root@exalytics0 ~]# cd /opt/exalytics/bin
[root@exalytics0 bin]# ./exalytics_configure_network.sh
Network Configuration Script Version exalytics-scripts-2.0.0.0-11_el6.noarch
Do you want to configure InfiniBand for Exadata connection? (y/n) [n]: y
Configure bonding on all cards ? (y/n) [n]: y
Enter bond0 IP address:192.168.9.159
Use 192.168.9.159 for bond0 ip address (y/n) [y]: y
Task Comment Check
Enter bond0 netmask address:255.255.252.0
Use 255.255.252.0 for bond0 netmask (y/n) [y]: y
Do you want to configure 10G network (y/n) [n]: y
Configure bonding on eth0 eth1 eth2 eth3 eth4 eth5 eth6 eth7 or part of it?
(y/n) [n]: y
Configure bonding on all cards ? (y/n) [n]: n
Enter bond1 gateway address:10.152.223.1
Use 10.152.223.1 for bond1 gateway (y/n) [y]: y
Configure bonding on eth0 ? (y/n) [n]: n
Configure bonding on eth4 ? (y/n) [n]: y
Do you want to configure Ethernet network for QLogic Ganymede cards (y/n) [n]:
y
Configure bonding on eth10 eth11 eth8 eth9 or part of it? (y/n) [n]: y
Configure bonding on all cards ? (y/n) [n]: y
Enter bond3 gateway address:10.152.224.1
Use 10.152.224.1 for bond3 gateway (y/n) [y]: y
Do you want to configure hostname (y/n) [n]: y
Enter hostname:exalytics-x5-4-bur09-a
Use exalytics-x5-4-bur09-a for host_name (y/n) [y]: y
Enter domainname:us.oracle.com
Use us.oracle.com for domainname (y/n) [y]: y
Do you want to configure timezone (y/n) [y]: y
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
1) Africa
2) Americas
3) Antarctica
4) Arctic Ocean
5) Asia
6) Atlantic Ocean
7) Australia
8) Europe
9) Indian Ocean
10) Pacific Ocean
11) none - I want to specify the time zone using the Posix TZ format.
#? 2
Please select a country.
1) Anguilla 28) Haiti
2) Antigua & Barbuda 29) Honduras
3) Argentina 30) Jamaica
4) Aruba 31) Martinique
5) Bahamas 32) Mexico
6) Barbados 33) Montserrat
7) Belize 34) Nicaragua
8) Bolivia 35) Panama
9) Brazil 36) Paraguay
10) Canada 37) Peru
11) Caribbean Netherlands 38) Puerto Rico
12) Cayman Islands 39) St Barthelemy
13) Chile 40) St Kitts & Nevis
14) Colombia 41) St Lucia
15) Costa Rica 42) St Maarten (Dutch part)
16) Cuba 43) St Martin (French part)
17) Curacao 44) St Pierre & Miquelon
18) Dominica 45) St Vincent
19) Dominican Republic 46) Suriname
20) Ecuador 47) Trinidad & Tobago
21) El Salvador 48) Turks & Caicos Is
22) French Guiana 49) United States
23) Greenland 50) Uruguay
24) Grenada 51) Venezuela
Task Comment Check
25) Guadeloupe 52) Virgin Islands (UK)
26) Guatemala 53) Virgin Islands (US)
27) Guyana
#? 49
Please select one of the following time zone regions.
1) Eastern Time
2) Eastern Time - Michigan - most locations
3) Eastern Time - Kentucky - Louisville area
4) Eastern Time - Kentucky - Wayne County
5) Eastern Time - Indiana - most locations
6) Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties
7) Eastern Time - Indiana - Pulaski County
8) Eastern Time - Indiana - Crawford County
9) Eastern Time - Indiana - Pike County
10) Eastern Time - Indiana - Switzerland County
11) Central Time
12) Central Time - Indiana - Perry County
13) Central Time - Indiana - Starke County
14) Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties
15) Central Time - North Dakota - Oliver County
16) Central Time - North Dakota - Morton County (except Mandan area)
17) Central Time - North Dakota - Mercer County
18) Mountain Time
19) Mountain Time - south Idaho & east Oregon
20) Mountain Standard Time - Arizona (except Navajo)
21) Pacific Time
22) Pacific Standard Time - Annette Island, Alaska
23) Alaska Time
24) Alaska Time - Alaska panhandle
25) Alaska Time - southeast Alaska panhandle
26) Alaska Time - Alaska panhandle neck
27) Alaska Time - west Alaska
28) Aleutian Islands
29) Hawaii
#? 1
The following information has been given:
United States
Eastern Time
Therefore TZ='America/New_York' will be used.

Local time is now: Tue Aug 11 11:21:47 EDT 2015.
Universal Time is now: Tue Aug 11 15:21:47 UTC 2015.
Is the above information OK?
1) Yes
2) No
#? 1
You can make this change permanent for yourself by appending the line
TZ='America/New_York'; export TZ
to the file '.profile' in your home directory; then log out and log in again.
Here is that TZ value again, this time on standard output so that you
can use the /usr/bin/tzselect command in shell scripts:
Do you want to configure time server (y/n) [y]: y
Enter network time server:10.152.223.254
Use 10.152.223.254 for timeserver (y/n) [y]: y
Do you want to configure DNS(s) (y/n) [y]: y
Enter DNS:192.135.82.132
Use 192.135.82.132 for DNS (y/n) [y]: y
configure another DNS? (y/n) [n]: y
Enter DNS:130.35.249.41
Use 130.35.249.41 for DNS (y/n) [y]: y
configure another DNS? (y/n) [n]: n
echo 'Starting configuration changes'
service NetworkManager stop
chkconfig NetworkManager off
/bin/mkdir /tmp/exalytics.save
-----cut-----
*** network configuration changes are echoed to the screen ***
-----cut-----
Commit changes? (y/n) [n]: y
Starting configuration changes
Stopping NetworkManager daemon: [ OK ]
Task Comment Check
Shutting down interface eth0: [ OK ]
Shutting down interface eth4: [ OK ]
Shutting down loopback interface: [ OK ]
sed: can't read /etc/ofed/openib.conf: No such file or directory
Stopping NetworkManager daemon: [FAILED]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: Determining if ip address 192.168.9.159 is
already in use for device bond0...
[ OK ]
[ OK ]
[ OK ]
Bringing up interface eth0:
Determining IP information for eth0... failed; no link present. Check cable?
[FAILED]
Bringing up interface usb0: [ OK ]
Wait 30 secs to allow the network to settle ...
Testing Gateways if configured
[EXALYTICS_INFO:GENERAL] Successful connectivity test to 10.152.223.1
[EXALYTICS_INFO:GENERAL] Successful connectivity test to exalytics-x5-4-bur09-
a
[EXALYTICS_INFO:GENERAL] Successful connectivity test to exalytics-x5-4-bur09-
a.us.oracle.com
Shutting down ntpd: [FAILED]
12 Aug 13:26:07 ntpdate[12851]: step time server 10.152.223.254 offset
-0.144364 sec
Starting ntpd: [ OK ]
[root@exalytics0 bin]#
If this command is run from the console you may see some output while
bringing up bond0 complaining about the bonding driver options such as the
mtu setting. These messages can be safely ignored. Also note that the
Shutting down ntpd and NetworkManager steps will show [FAILED] when
run on a new system. You may also see [FAILED] notes for ports that are
not connected indicating no link is present. These results are normal and can
also be ignored.
The Exalytics system should now be accessible on the customer's network
and be able to communicate with the Database Server.
Confirm the ability to communicate with the Database Server using ping.
Request the IP address of DB Server from customer for testing – in this
example 192.168.9.201 is the address for one of the Exadata Database nodes'
IB connection:
[root@exalytics0 ~]# ping -c5 192.168.9.201
PING 192.168.9.201 (192.168.9.201) 56(84) bytes of data.
64 bytes from 192.168.9.201: icmp_seq=1 ttl=64 time=108 ms
64 bytes from 192.168.9.201: icmp_seq=2 ttl=64 time=0.094 ms
--- 192.168.9.201 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.048/21.757/108.518/43.380 ms
Task Comment Check
Check & set the date/time of the system using the date command as needed:
date <MMDDhhmmCCYY>
using the format: Month, Day, Hour, Minute, Century, Year. Example:
[root@exalytics0 ~]# date
Fri Jul 17 14:04:27 EDT 2015
[root@exalytics0 ~]# date 071714052015
Fri Jul 17 14:05:00 EDT 2015
[root@exalytics0 ~]#
Task Comment Check
FLASH ACCELERATOR CARD CONFIGURATION & SETUP

Check the system to ensure that all three Flash Accelerator cards are being
recognized:
[root@exalytics0 ~]# ls -lsa /dev/nvme?n1
0 brw-r----- 1 root disk 259, 0 Jul 17 11:33 /dev/nvme0n1
We should see the three NVMe devices listed. These are the three device
names that will be used to create the raid volume. If all cards are not being
reported check the ILOM for any logged faults then shutdown the system and
check the seating of all the cards to ensure they are properly installed then
boot and check again. If troubleshooting help is needed contact the Oracle
Support Center for assistance.
After confirming that the three Flash Accelerator cards are being recognized
by the OS configure and mount them using the configure_flash.sh script.
Note: The configure_flash.sh script allows for a --RAID5 configuration
option also but only the --RAID10 option should be used. This is due to
bugid 22050384 which can cause booting issues with a RAID 5
configuration.
[root@exalytics0 ~]# cd /opt/exalytics/bin
[root@exalytics0 bin]# ./configure_flash.sh --RAID10
[EXALYTICS_INFO:FLASH_CONFIG] Configuring flash for Exalytics
[EXALYTICS_INFO:FLASH_CONFIG] Configuring flash with RAID level 10
[EXALYTICS_INFO:FLASH_CONFIG] ***WARNING*** : This flash

configuration script will remove any existing RAID arrays, as well
as remove any partitions on any flash drives and will create a new
RAID array across all these flash drives. This will result in ALL
DATA BEING LOST from these drives.
Do you still want to proceed with this flash configuration script?
(yes/no) yes
[EXALYTICS_INFO:FLASH_CONFIG] Warning response was : yes
[EXALYTICS_INFO:FLASH_CONFIG] The machine has flash drivers
installed.
[EXALYTICS_INFO:FLASH_CONFIG] This machine has 3 flash cards
[EXALYTICS_INFO:FLASH_CONFIG] Flash cards appear to be healthy
---cut---
*** flash device configuration changes are echoed to the screen ***
---cut---
[EXALYTICS_INFO:FLASH_CONFIG] Creating RAID array: /dev/md0, using
devices : /dev/md1 /dev/md2 /dev/md3 /dev/md4 /dev/md5 /dev/md6
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
[EXALYTICS_INFO:FLASH_CONFIG] RAID device created : /dev/md0.
mke2fs 1.43-WIP (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=128 blocks, Stripe width=768 blocks
146415616 inodes, 585661056 blocks
29283052 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
Task Comment Check
17873 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736,
1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872,
71663616, 78675968, 102400000, 214990848, 512000000, 550731776
Allocating group tables: done

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
[EXALYTICS_INFO:FLASH_CONFIG] Flash mounted at /u02
[EXALYTICS_INFO:FLASH_CONFIG] RAID config complete and
/etc/mdadm.conf updated.
[EXALYTICS_INFO:FLASH_CONFIG] Updated /etc/fstab
See /var/log/exalytics/exalytics.log for more details
[root@localhost bin]#
Verify that the new volume mounted properly using the df command. You
should see output similar to the following (note that the sizes reported may
differ depending upon the options used):
[root@exalytics0 ~]# df -h | grep /u02
/dev/md0 2.2T 201M 2.1T 1% /u02
Then check on the status of the md device that was created. Use the mdadm
command to output it's details:
[root@exalytics0 ~]# mdadm -D /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Tue Aug 11 13:41:04 2015
Raid Level : raid0
Array Size : 2342644224 (2234.12 GiB 2398.87 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Tue Aug 11 13:41:04 2015

State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : exalytics-x5-4-bur09-a:0 (local to host exalytics-x5-4-

bur09-a)
UUID : 1c3c4fd0:40d02419:1643b423:493342ef
Events : 0
Number Major Minor RaidDevice State

0 9 1 0 active sync /dev/md1
The system should report output similar to the above example.
Task Comment Check
To check the progress of resyncing of the md devices you can cat the
/proc/mdstat file. This will show you each of the md devices and their
resync status/progress:
[root@exalytics0 ~]# cat /proc/mdstat
Personalities : [raid1] [raid0]
md0 : active raid0 md6[5] md5[4] md4[3] md3[2] md2[1] md1[0]
2342644224 blocks super 1.2 512k chunks
md6 : active raid1 nvme2n1p4[1] nvme1n1p1[0]

390571968 blocks super 1.2 [2/2] [UU]
resync=DELAYED
bitmap: 3/3 pages [12KB], 65536KB chunk

390572032 blocks super 1.2 [2/2] [UU]
resync=DELAYED

390572032 blocks super 1.2 [2/2] [UU]
resync=DELAYED

390571968 blocks super 1.2 [2/2] [UU]
resync=DELAYED

390571968 blocks super 1.2 [2/2] [UU]
resync=DELAYED

390572032 blocks super 1.2 [2/2] [UU]
[==>..................] resync = 13.6% (53365632/390572032)
finish=26.3min speed=212905K/sec
unused devices: <none>

For the RAID10 configuration each of the mirrors will take about 40 minutes
to synchronize. The mirrors will resync one at a time in turn and show
“resync=DELAYED” until they start. The system may be rebooted while the
volumes are resyncing.
Task Comment Check
Finally use the exalytics_CheckFlash.sh script to check the health of each
flash card. We should see three flash drives reported as Healthy:
[root@exalytics0 bin]# /opt/exalytics/bin/exalytics_CheckFlash.sh
Checking Exalytics Flash Drive Status
cardindex=0
cIndex=0
Driver version not available
Supported number of flash drives detected (3)
Flash card 1 :
Slot number: 6
Overall health status : GOOD
Capacity (in bytes) : 1600321314816
Firmware Version : SUNW-NVME-1 PCI Vendor ID: 8086 Serial Number:
CVMD520500GT1P6NGN Model Number: INTEL SSDPEDME016T4S Firmware
Revision: 8DV1RA12 Number of Namespaces: 1
cardindex=1
cIndex=1
Devices: /dev/nvme0n1p1 /dev/nvme0n1p4 /dev/nvme0n1p3
/dev/nvme0n1p2
Flash card 2 :
Slot number: 7
CVMD518200121P6NGN Model Number: INTEL SSDPEDME016T4S Firmware
cardindex=2
cIndex=2
/dev/nvme1n1p3
Flash card 3 :
Slot number: 10
CVMD520600TT1P6NGN Model Number: INTEL SSDPEDME016T4S Firmware
cardindex=3
cIndex=3
/dev/nvme2n1p1
Raid Array Info (/dev/md0):

/dev/md0: 2234.12GiB raid0 6 devices, 0 spares. Use mdadm --detail
for more detail.
Summary:
Healthy flash drives : 3
Broken flash drives : 0
Pass : Flash card health check passed
[root@exalytics0 bin]#
Task Comment Check
This completes the setup and configuration of the Exalytics Server. Perform
a reboot of the system and monitor to confirm a successful boot:
[root@exalytics0 ~]# reboot
After a successful reboot login and test the network connection one more
time as described above to ensure that the configuration is being activated
correctly at boot time.
Also check that the flash cards are being mounted automatically at boot time
by using the df -h command to check to see that /u02 is mounted as shown in
the above example.
If you had the ILOM's net management port connected to your laptop during
the setup make sure to connect it to the customer's management network
using a Cat 5 cable. Confirm that the customer can reach both the ILOM and
the host from a client on their network.
Task Comment Check
CONFIGURE THE SERVER TO USE ASR

Due to the following bugs:
• Bug 21565893 - asr does not work in exalytics release2(linux6.6)
• Bug 21645584 - asr scripts use incorrect path to ipmitool in 2.0.0.0el6 image
ASR cannot currently be configured for use during an Exalytics X5-4 installation.
The following section is included for completeness but the steps will not complete
successfully until these bugs are fixed. DO NOT attempt ASR configuration until
these issues are addressed.
When these bugs are fixed an updated EIS checklist will be released including the
necessary updates so that ASR can be setup successfully during installation.
Do NOT proceed with ASR Configuration!
Go to Section Handover on page 38.
Configure the System to use Auto Service Request (ASR) if the Customer has a
configured and operational ASR Manager system (formerly known as “SASM
host”) available. For further information refer to the Oracle Auto Service Request
ASR Manager User's Guide Release 5.3 for Linux and Solaris E18475-36 (or later).
Exalytics specific ASR setup install steps are detailed in Chapter 9 of the Oracle®
Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4 X4-4 and X5-4
Release 2.0 Part Number E63850-02:
https://docs.oracle.com/cd/E62968_01/doc.1/e63850/asr.htm#sthref84
For this server there are four steps:
1. Set up ASR on the Host.
2. Configure Telemetry Sources.
3. Activating the ASR Asset on the ASR Manager system.
4. Completion of activation in MOS.
CONFIGURE THE /ETC/INITTAB FILE
Add the following line to the /etc/inittab file using your favorite editor:
[root@exalytics0 ~]# cd /opt/exalytics/asr
[root@exalytics0 asr]# vi /etc/inittab
emh1:345:respawn:/opt/exalytics/asr/bda_mon_hw_asr.pl -server
Execute the init q command to initialize and start the bda_mon server:
[root@exalytics0 asr]# init q
CONFIGURE TELEMETRY SOURCES

Use the client to configure ASR destinations by using the instructions that are
available from the following command that you execute from the
/opt/exalytics/asr directory:
[root@exalytics0 asr]#./bda_mon_hw_asr.pl -help
Configure ILOM telemetry by running the following command:

[root@exalytics0 asr]# ./setup_asr_ilom.pl -host <IP-addr-of-ASR-
Manager>
Task Comment Check
Configure Exalytics host machine telemetry by running the following
command:
[root@exalytics0 asr]# ./bda_mon_hw_asr.pl -set_snmp_subscribers \
type=asr,host=<IP-addr-of-ASR-Manager>,fromip=<IP-addr-of-Host>
ACTIVATE THE ASR ASSETS (VIA ASR MANAGER SYSTEM)

Log into the ASR Manager system as Via ssh or rlogin.
user root.
Activate the ASR Asset for the Host. Assuming that /opt/asrmanager/bin is in
PATH:
# asr activate_asset -i <IP-of-Host>
-h <Hostname-of-Exalytics-server>
# asr activate_asset -i <IP-of-SP>
Activate the ASR Asset for the SP.
Confirm that they are activated. # asr report
The ASR registration user will receive

an email with report results. Confirm
that the SP & Host are activated (as
appropriate).
Disconnect from the ASR manager. # exit
COMPLETION OF ACTIVATION IN MOS

Log into My Oracle Support: https://support.oracle.com
In the My Oracle Support Dashboard, click the More... tab. Then select
Settings from the menu.
In the Settings pane on the left of the window, select Assets (located under
the administrative submenu). For your Support Identifier, select ASR Status
from the sort filter, then select Pending from the All Statuses drop-down
menu:
Approve Pending assets either via the Asset Toolbar or via Asset Details:
Task Comment Check
Activate via Asset Toolbar
Click the asset's serial number to display a toolbar with following options:
• Assign Contact: select this option to assign a contact to the asset. Only
users associated with the support identifier can be a contact.
• Change Address: select this option to update the asset's physical location.
• Approve - for assets that are Pending, click Approve to enable ASR for
the asset.
• Other Actions: you can also perform other actions such as Activate (for
an inactive asset), Deactivate (for an active asset), or Deny (for a
pending request).
Activate via Asset Details
At the bottom of the Asset pane there is a Show Asset Details option. Click
an asset's serial number and then the Show Asset Details to update
information about the asset. Required fields for ASR asset activation are
indicated by an asterisk *.
Task Comment Check
HANDOVER
Perform Installation Assessment tests as EISdoc V4 – completed during preparation
described in the EIS Test Procedures of installation.
Plan.
Complete documentation and hand over EISdoc V4:
to customer. EIS-DOCS-Operational Handover-
Document.odt
Short briefing: the configuration. Review with the customer.
Complete documentation and hand over Confirm with the ACS engineer who will
to Oracle ACS. be completing the software install that
they are aware of the network
configuration that was used and that they
are able to access the system.
Note that if ACS will be re-configuring the
system with a virtualized install for the
customer they will be responsible for the
reconfiguration of all network, storage,
and flash devices on the host. During the
EIS install we still perform the installation
as if a “bare-metal” installation will be
used so that all of the hardware can be
confirmed to be in proper working order
but when ACS re-images the system for
virtualization all of the previous host level
configuration will be lost. This is normal
and the ACS team will handle any
configurations necessary after the
handover.
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] .

Exalytics X5 Nov 2016

Uploaded by

Copyright:

Available Formats

Exalytics X5 Nov 2016

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

Exalytics X5 Nov 2016

Uploaded by

Copyright:

Available Formats

EIS Installation Checklist for the

ORACLE® Exalytics X5-4 In-Memory Machine

Serial Number Hostname

INSTALLATION OVERVIEW– EIS DELIVERABLES

MEMORY DIMM FAULT BEST PRACTICES

Request licenses where required. Oracle or customer requests licenses

RACKMOUNTING – WHERE APPLICABLE

ILOM SERVICE PROCESSOR (SP) CONFIGURATION

Enter the following commands to The following are example values

CHECKING THE SERIAL NUMBER AND SYSTEM IDENTIFIER

-> show /SP system_identifier

If the system_identifier is not set correctly set it manually:

CONFIGURING THE SP'S CLOCK PROPERTIES VIA CLI

To manually set the ILOM clock property values:

-> show /SP/clock

-> set /SP/clock usentpserver=enabled

EXAMINING THE FIRMWARE/BIOS VERSIONS USING THE CLI

PREPARING FOR THE UPDATE

USING THE CLI TO UPDATE THE FIRMWARE / BIOS

For example (enter command on single line):

Refer to guide 820-1188-xx for more information.

USING THE GUI TO UPDATE THE FIRMWARE / BIOS

POWERING ON & SETTING UP THE HOST

localhost login: root

Then restart the network service:

INSTALLING HARDWARE OPTIONS

Task Comment Check

CABLING THE HOST

UPDATE HARDWARE MANAGEMENT PACKAGES

Intentionally left blank

Change to the patch directory and run the update_kernel.sh script:

Broadcast message from [email protected]

The system is going down for reboot NOW!

The following information has been given:

Therefore TZ='America/New_York' will be used.

--- 192.168.9.201 ping statistics ---

FLASH ACCELERATOR CARD CONFIGURATION & SETUP

[EXALYTICS_INFO:FLASH_CONFIG] ***WARNING*** : This flash

Allocating group tables: done

Update Time : Tue Aug 11 13:41:04 2015

Chunk Size : 512K

Name : exalytics-x5-4-bur09-a:0 (local to host exalytics-x5-4-

Number Major Minor RaidDevice State

The system should report output similar to the above example.

md6 : active raid1 nvme2n1p4[1] nvme1n1p1[0]

md5 : active raid1 nvme2n1p3[1] nvme1n1p3[0]

md4 : active raid1 nvme2n1p2[1] nvme0n1p3[0]

md3 : active raid1 nvme2n1p1[1] nvme0n1p2[0]

md2 : active raid1 nvme1n1p4[1] nvme0n1p1[0]

md1 : active raid1 nvme1n1p2[1] nvme0n1p4[0]

unused devices: <none>

Raid Array Info (/dev/md0):

CONFIGURE THE SERVER TO USE ASR

CONFIGURE TELEMETRY SOURCES

Configure ILOM telemetry by running the following command:

ACTIVATE THE ASR ASSETS (VIA ASR MANAGER SYSTEM)

The ASR registration user will receive

COMPLETION OF ACTIVATION IN MOS

Comments & RFEs welcome. Oracle staff should mail to [email protected] .

You might also like

[EXALYTICS_INFO:FLASH_CONFIG] WARNING : This flash