Você está na página 1de 16

EIS Installation Checklist for Axiom AX300/AX500 to AX600

(Slammer Conversion 5.x)

Customer:
Sales Order Number:
CASE 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.
It is expected that the planning / preparation phase be carried out with the help of
EISdoc V4 (available from the EIS website).
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 only covers the hardware installation of the Pillar Slammer
conversion at Axiom Release R5.0 or higher. R5 does not currently support NAS,
so at this time this only covering SAN.
The Base WWN and Service Type of the existing Ax500 Slammers must be
obtained and provided to Oracle Manufacturing as part of the order for the
replacement Ax600 Slammers.
Determine Service Type. The Service Type is nas_optical, nas_copper, or
san. Release 5.x does not support NAS. If the current service type is nas_copper
or nas_optical, inform the account team, as the system cannot be converted at
Release 5.x).
The Axiom software Release to be used for the Slammer Conversion will be
provided by the Support Center.
This procedure assumes familiarity with Axiom hardware, software upgrade
procedures, Pillar CS software utilities, Slammer Console and accessing Axiom
documentation such as the Axiom Service Guide from the Axiom Pilot.
If a replacement SAN Slammer contains 8 Gb FC NIMs, the WWN of the external
FC port connections to the customer fabric will change. This may require some
reconfiguration of the external SAN. The WWN information is available in the
GUI after the Slammer conversion. If the SAN switch is using soft zoning, inform
the customer that switch re-zoning will need to be done and the SAN administrator
must be available to do the rezoning after the Slammer conversion.
If there is a FalconStor or similar appliance that encodes the model number for
LUN identification, make arrangements for reconfiguring these devices. The
Axiom returns the Axiom Model as ASCII Product Identification in Bytes 16-31
of the SCSI Inquiry response and this will change on the Slammer conversion.
The values for Bytes 16-31 are Axiom 500, which will change to Axiom 600.
It is not intended that this checklist be handed over to the customer.

Oracle Internal and Approved Partners Only Page 1 of 16 Vn 1.4 Created: 21. Dec. 2012
Slammer Type Slammer-Serial# Slammer-Module Name
e.g. SAN 4Gb w/iSCSI e.g. 2000000b08040360
e.g. SAN 4 Gb w/o iSCSI

Oracle Internal and Approved Partners Only Page 2 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check

PREPARATION
Refer to the Systems TSC website for the latest information:
http://pts-storage.us.oracle.com/products/axiom/index.shtml
Read Documentation: The documents referenced are to be found
either at:
Release 5.X Slammer Conversion
http://pts-
Ax500 to Ax600 document, storage.us.oracle.com/products/axiom/inde
The conversion instructions will be x.shtml
in the Release 5.3 Service Guide, http://www.oracle.com/technetwork/docu
which is available on the Axiom, mentation/oracle-unified-ss-193371.html
Advanced Hardware Installation or on the EIS web pages. Oracle intranet
Guide for Pillar Axiom 600, users should go to the "Useful Installation
Pillar Axiom 600 SSF Cabling Documents" link located under
"Miscellaneous" in the TOC. Oracle
Reference, Partner Network users should look for
Site Preparation Guide. "Useful Documentation" under "EIS
Miscellaneous".
Contact the Oracle Customer Support Provide the Oracle Customer Support
Center and open a Service Request for Center the following information: Axiom
Serial Number, Date and time of the
the activity. activity, description of activity.
EIS Site-Audit Report complete? EISdoc V4:
File EIS-DOCS-SiteAudit-Axiom.odt
EIS Installation Configuration Plan & EISdoc V4:
Test Procedures Plan complete? Use appropriate BUILD and TPP
documentation.
Obtain Slammer Cloning The replacement Ax600 Slammers must
Information: be manufactured with the same Base
WWN and service type as the existing
Ax500 Slammers.
This information is available from any log
set and from the output of the axiomcli
slammer -list details command.

Example:
$ axiomcli login -u pillar -p
<pillar admin password> <IP
Address of Axiom>
$ axiomcli slammer -list -details >
slammerinfo.txt
Slammer: /SLAMMER-01
Name: SLAMMER-01
Id: 2008000B080466E2
HardwareComponentStatus: NORMAL
ServiceType: SAN
SerialNumber: FA50590017
PartNumber: 1450-00035-01
Model: AX600

The ID is converted to the Base WWN by


changing the 4th and last digit to 0. In
the example shown, the Base WWN would
be 2000000B080466E0

Oracle Internal and Approved Partners Only Page 3 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Read the following notes before Release 5.x contains support for
proceeding: Ax500 and Ax600 Slammers. The use
of special conversion packages as in
Release 4.x is not required.
ALL existing Ax500 Slammers must
be replaced at the same time. The
Axiom will not boot with mixed
Ax500 and Ax600 Slammers.
If there are any upgrades required to Then access the Axiom summary screen at
support the new Slammer(s), or a code http://axiom_ip_address and download the
Pillar Axiom 600 Hardware Installation
upgrade is an option, upgrade the Guide and the Pillar Axiom 600 SSF
Axiom first. Cabling Reference documents.
IMPORTANT! The documents referenced are to be found
either at:
If you are upgrading to a Slammer 600
http://pts-
series 4 on an Axiom with R5 software storage.us.oracle.com/products/axiom/inde
the Axiom software must be at R5.3 or x.shtml
higher. http://www.oracle.com/technetwork/docu
mentation/oracle-unified-ss-193371.html
Tip: The series 4 Slammer has a
protruding power supply, Series 3 does or on the EIS web pages
not.
For an overview read the Release 5.X This procedure is in the Release 5.3
Slammer Conversion Ax500 to Ax600 version of the Service Guide (coming
shortly).
document procedure.
Required tools needed for installation: A workstation with a serial port [or
usb-serial conversion] that can operate
at 115,200 bits per second.
A 9 pin DIN crossover female to
female serial cable long enough to
work comfortably with the Slammer.
[This is an industry standard PC to PC
Serial crossover cable].
A Serial Terminal communications
package with basic VT100, Wyse50,
or similar terminal emulation. For
example: Microsoft/Hilgraeve
HyperTerm, open source PuTTY, etc.
PuTTY is recommended.
A power cable and power source for
powering on the replacement
Slammer before it is placed in the
Axiom rack.
Useful tools are available from:
http://pts-storage.us.oracle.com/products/axiom/index.shtml

Oracle Internal and Approved Partners Only Page 4 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check

UNPACKING
Delivery complete?
Perform a cable inventory. Ax500 uses the HSSDC type FC cables, but all
currently shipping Ax600 Slammers use SFP
type FC cables. This requires replacing all
cables between the Slammer and bricks with
new cables. This would either be SFP to
HSSDC copper hybrid or SFP to SFP copper
since the Ax500 didnt support optically
connected Bricks.

Allow the hardware to acclimatise Refer to the EIS standard


(power off) at the customer site. Acclimatisation of Sun Servers &
Storage
Unpack outside data center to ensure no Collect packing material together for
contamination/dust is released inside disposal. Verify that customer can
customer's controlled environment. dispose of packing material including
shipping crate during the pre-
installation kick-off meeting.
Refer to the Rack Unpacking
Instructions guide.
Verify all packing material has been Fans & air vents must be free to operate.
removed, i.e. nothing is blocked.

Oracle Internal and Approved Partners Only Page 5 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check

CLONING PROCESS / ADDING THE SLAMMER(S)


Axiom Slammers are identified by their If the WWN does not match, the
Base World Wide Name, which is replacement Slammer will be treated
as a new Slammer and the old
stored in the Slammer Chassis Slammer will be treated as "Missing"
Midplane. When a Slammer is which may prevent a system start up.
replaced, either as a service procedure The WWN/MAC Base Addr is stored
or as a Slammer upgrade, the in EEPROM located on the Slammer
replacement Slammer must have Midplane. There are two identical
exactly the same Base WWN in order to copies of this information, one for
each Slammer CU. The value must be
function. checked, and updated if necessary, on
both CUs.
Please see the Release 5.X Slammer
Conversion Ax500 to Ax600 document
procedure for an overview of the Base
WWN explained.
GATHERING SLAMMER BASE WWN
Verify the existing Slammer(s) Base Use axiomcli slammer list
WWN: details to obtain the WWN. The Base
WWN is obtained by converting the 4th
and last digit to zero in the CU WWN.
Example:
$ axiomcli login -u pillar -p
<pillar admin password> <IP
Address of Axiom>
$ axiomcli slammer -list -details >
slammerinfo.txt
Slammer: /SLAMMER-01
Name: SLAMMER-01
Id: 2008000B080466E2
HardwareComponentStatus: NORMAL
ServiceType: SAN
SerialNumber: FA50590017
PartNumber: 1450-00035-01
Model: AX600

The ID is converted to the Base WWN by


changing the 4th and last digit to 0. In
the example shown, the Base WWN would
be 2000000B080466E0
VERIFY THE WWN FOR THE REPLACEMENT SLAMMERS
Connect console cable and power on The replacement Slammer must not have
Slammer Controller Unit: any Private Management Interface (PMI)
Ethernet or Private Interconnect (PI) FC
cables connected to an Axiom.
A source of Slammer Power is required.
Only one Power Supply will need to be
connected at a time.
The Slammer CU may be connected to the
PDU on the Axiom using a spare power
cable, or it may be connected to a
convenient power source.

Oracle Internal and Approved Partners Only Page 6 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
The PC to PC Serial Crossover Cable The Slammer Console cable is a standard
will be referred to as a Console Cable. 9 pin DIN Serial to Serial Crossover
Cable. If the workstation does not have a
Serial port, a USB to Serial Converter is
required.
Connect the Console cable to the Set the Serial Port parameters to:
115,200 Bits/second
workstation serial port. 8 Bits per character
No Parity
No Flow Control.
Note: The method for this is dependent
on software used.
Set the Serial Terminal emulation See the help menu or online
software to capture all printable documentation for the specific Serial
Terminal emulation software.
characters to a log file.
Note: This file may be needed for
recovery.
Connect the Console Cable. Connect the Console Cable to the serial
port on the Private Interconnect Module
(PIM) on the rear of the Slammer CU.
The Slammer Console Cable must be
connected, with the terminal emulation
software set to capture output before the
CU is powered on.
Apply power to one Slammer CU, with Let the Controller Unit boot up and watch
the Console Cable attached and for the CU_GUID and CU_TYPE as the
CU boots. You may not be able to see it
recording all output. as the boot process scrolls fairly fast, but
this typically takes about 2-3 minutes.
CU_GUID=2008000b08040b42
CU_ID=0:1450-00132-30:0.E
CU_ADAPTER2_PN=1450-00138-21
CU_TYPE=san
Stop capture and view the output file. Look for the GU_GUID on the output file.
This is the Base WWN.
Verify that the CU_TYPE is correct.
Example: CU_GUID=2000000B080466E0
CU0 for this Slammer would be WWN
2008000B080466E2
CU1 for this Slammer would be WWN
2009000B080466E2
The CU_TYPE is the Slammer Service
Type. The only value supported for R5
conversions is san

Oracle Internal and Approved Partners Only Page 7 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Repeat the GUID (WWN/MAC) and If the WWN matches on both CUs
CU_TYPE verification for all of the and is the same as the Slammer to be
replaced, the Slammer Cloning is
replacement Slammers. correct. Proceed with the Slammer
replacement.
If the Base WWN does not match, the
Slammer was not cloned properly.
This can be corrected in the field by
proceeding to modify the Base WWN
as noted below.
If the CU_TYPE, or Service Type, is
not san do not attempt the Slammer
replacement. Notify the Oracle
Support Center.
READING THE SLAMMER BASE WWN
Connect console cable and power on The replacement Slammer must not
Slammer Controller Unit. have any Private Management
Interface (PMI) Ethernet or Private
Interconnect (PI) FC cables connected
to an Axiom.
A source of Slammer Power is
required.
Only one Power Supply will need to
be connected at a time.
The Slammer CU may be connected
to the PDU on the Axiom using a
spare power cable, or it may be
connected to a convenient power
source.
The PC to PC Serial Crossover Cable The Slammer Console cable is a standard
will be referred to as a Console Cable. 9 pin DIN Serial to Serial Crossover
Cable. If the workstation does not have a
Serial port, a USB to Serial Converter is
required.
Connect the Console cable to the Set the Serial Port parameters to:
115,200 Bits/second
workstation serial port. 8 Bits per character
No Parity
No Flow Control.
Note: The method for this is dependent
on software used.
Set the Serial Terminal emulation See the help menu or online
software to capture all printable documentation for the specific Serial
Terminal emulation software.
characters to a log file.
Note: This file may be needed for
recovery.

Oracle Internal and Approved Partners Only Page 8 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Apply power to one Slammer CU, with Wait until the microdms utility is running
the Console Cable attached and on the Slammer [microdms = micro
Diagnostic and Monitoring Service].
recording all output.
You should see the following output:
"microdms: fans and temps OK
after 30 secs in netboot"
" microdms: fans and temps OK
after 60 secs in netboot"

Slay the microdms service to prevent it Enter slay microdms


from resetting the CU after running in Note: Be sure to slay microdms before it
netboot for 90 seconds and to enable reaches:
the EEPROM utility. "microdms: fans and temps OK
after 90 secs in netboot"
If the microdms utility detects that it has
been running in netboot for 90 seconds, it
will reset the Slammer CU in an attempt to
recover from a failed boot. When using
the EEPROM utility, this must be disabled
by killing the microdms service.
Enter the EEPROM utility by typing "eeprom".
# eeprom
ID EEPROM UTILITY MENU, for eeprom format version 3
Select a FRU
------------------------------------
1 - Motherboard
2 - NIM (e.g. SAN/Gige)
3 - PIM (e.g. FCIM)
4 - Battery
5 - Fan 1 (left)
6 - Fan 2 (right)
7 - Power Supply 1 (top)
8 - Power Supply 2 (bottom)
9 - Midplane
10 - Display the eeprom format version this program supports
11 - EXIT program
------------------------------------
Enter selection:

Oracle Internal and Approved Partners Only Page 9 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Enter 9 to select the Midplane, and then select 1 to read the ID EEPROM,
then 0 to read the value.
Notes: The example shown is for a Slammer CU that has not been cloned
correctly, which will require modifying the Midplane with EEPROM before
the Slammer can be installed. New Slammers from manufacturing should
have a System Serial Number of ten 9s. This is not critical, as the Axiom
will update the SSN as it boots, but if the SSN is not all 9s, the Slammer may
have been installed in another Axiom and not properly re-initialized before
shipment. Please log any SSN that is not all 9s and report it to the Oracle
Support Center.
Enter selection: 9

This will display the next menu


FRU: Midplane
Select what to do
------------------------------------
1 - Read ID EEPROM
2 - Write ID EEPROM
--------------------------------------
Enter a 1 to read the ID EEPROM, then 0 to perform the read:

Enter selection: 1
Read the ID EEPROM now? yes=0, no=1: 0

This displays the content of the ID EEPROM:


ID PROM contents:
CRC: 0xeafc8be5
Format: 0x10003
Length: 0x100
Revision: 0.A
Assembly Number: 1450-00035-20
Serial Number: LC003570930390
Description: Midplane
WWN/MAC Base Addr: 0x2000000B080267d0 [this does not match, update is required]
Unit Part Number: 1400-00051-21
Unit Serial Number: LA70882151
Unit Model Type: Ax600(0x201), NIM Type: san(0x3) <<note that this NIM type is SAN
and the Model Type is Ax600
Vendor Unique: ################################
System Serial Number: 9999999999

If the Base WWN is correct, power off If the WWN matches on both CUs
this CU and move the Console cable to and is the same as the Slammer to be
replaced, the Slammer Cloning is
the other CU and repeat the EEPROM correct. Proceed with the Slammer
Read. replacement.
Important! Make sure the Base WWN If the Base WWN does not match
the slammer being replaced, modify
is exactly the same on both CUs of the the Midplane information with an
new Slammer and that it matches the EEPROM write to the WWN/MAC
BaseWWN of the slammer being Base Address field.
replaced. See the Modify Slammer Base
WWN section below.
If you are replacing more than a single
Slammer, repeat the entire process on
the remaining Slammers.

Oracle Internal and Approved Partners Only Page 10 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
MODIFY SLAMMER BASE WWN (CLONING A SLAMMER)
Slay the microdms service to prevent it Enter slay microdms
from resetting the CU after running in Note: Be sure to slay microdms before it
netboot for 90 seconds and to enable reaches:
the EEPROM utility. "microdms: fans and temps OK after 90
secs in netboot"
If the microdms utility detects that it has
been running in netboot for 90 seconds, it
will reset the Slammer CU in an attempt to
recover from a failed boot. When using
the EEPROM utility, this must be disabled
by killing the microdms service.
Perform these steps only if the WWN on the new Slammer is incorrect.
Enter the EEPROM utility by typing "eeprom". Enter 9 to select the
Midplane, then select 1 to write to the ID EEPROM, then 12 to enter the
correct WWN/MAC Base Address.
# eeprom
ID EEPROM UTILITY MENU, for eeprom format version 3
Select a FRU
--------------------------------
1 - Motherboard
2 - NIM (e.g. SAN/Gige)
3 - PIM (e.g. FCIM)
4 - Battery
5 - Fan 1 (left)
6 - Fan 2 (right)
7 - Power Supply 1 (top)
8 - Power Supply 2 (bottom)
9 - Midplane
10 - Display the eeprom format version this program supports
11 - EXIT program
-----------------------------------
Enter selection: 9 for Midplane
The next menu appears:
FRU: Midplane
Select what to do
-----------------------------------
1 - Read ID EEPROM
2 - Write ID EEPROM
-----------------------------------
Enter selection: 2 to write EEPROM
FRU: Midplane
Select 12 to write the WWN/MAC Address
Select a field
-----------------------------------
4 - Format
5 - Length
6 - Revision
7 - Assembly Number
8 - Serial Number
9 - Description
10 - Unit Part Number
11 - Unit Serial Number
12 - WWN/MAC Base Address
13 - Configuration Bytes
14 - Vendor Unique Field
15 - System Serial Number
99 - All Fields
-----------------------------------
Enter selection: 12 for WWN

Oracle Internal and Approved Partners Only Page 11 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Enter data for the WWN/MAC base Caution: Be careful and enter a 12 to
address field (64-bit): update the WWN/MAC Base Address.
Modifying any other field can result in an
inoperable Slammer.
Enter the 64 bit WWN/MAC Base Entering 12 will produce the menu prompt
Address value, without the "0x" prefix. to enter the new WWN.
The WWN must begin with a 2 and Enter data for the WWN/MAC base
have a zero for the fourth digit and the address field (64-bit): 2000000B080466E0
final digit. For example: The EEPROM utility will generate a
confirmation screen with your input and
2000000B080466E0 the rest of the fields to be written to the
Midplane:

serEEPROM will be written with the


following data: (Zeros usually mean the
field will not be written).
If converting formats the format, length,
and crc fields will also be updated.
ID PROM contents:
CRC: 0x96e538c1
Format: 0x10003
Length: 0x100
Revision: 0.A
Assembly Number: 1450-00035-20
Serial Number: LC003570930390
Description: Midplane
WWN/MAC Base Addr:
0x2000000B080466E0 (New value to be
written)
Unit Part Number: 1400-00051-21
Unit Serial Number: LA70882151
Unit Model Type: Ax600(0x201), NIM
Type: SAN (0x3)
Vendor Unique:
################################
System Serial Number: 9999999999

Write the ID EEPROM now? yes=0,


no=1:

The ID Prom contents displayed should Check all of this information before
show the new, correct value for the selecting "0" to write the EEPROM.
WWN.
Check the Unit Model Type and NIM
Type fields to make sure the Model
Type is Ax600 and the NIM Type is the
same as the Slammer being replaced.
Write the WWN to the ID EEPROM by Enter a 0 if all information is correct:
selecting a 0 at the confirmation Write the ID EEPROM now? yes=0,
prompt. no=1: 0

Oracle Internal and Approved Partners Only Page 12 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Read the EEPROM, to make sure this CU value has been updated.
Enter 9 to select the Midplane, then select 1 to write to the ID EEPROM,
then 0 to read the ID EEPROM. The EEPROM utility should indicate the
correct information:
# eeprom
ID EEPROM UTILITY MENU, for eeprom format version 3
Select a FRU
---------------------------------------
1 - Motherboard
2 - NIM (e.g. SAN/Gige)
3 - PIM (e.g. FCIM)
4 - Battery
5 - Fan 1 (left)
6 - Fan 2 (right)
7 - Power Supply 1 (top)
8 - Power Supply 2 (bottom)
9 - Midplane
10 - Display the eeprom format version this program supports
11 - EXIT program
---------------------------------------
Enter selection: 9 Enter 9 for Midplane
FRU: Midplane
Select what to do
---------------------------------------
1 - Read ID EEPROM
2 - Write ID EEPROM
---------------------------------------
Enter selection: 1 Enter 1 for Read
Then enter 0 to perform the read:
Read the ID EEPROM now? yes=0, no=1: 0
ID PROM contents:
CRC: 0x96e538c1
Format: 0x10003
Length: 0x100
Revision: 0.A
Assembly Number: 1450-00035-20
Serial Number: LC003570930390
Description: Midplane
WWN/MAC Base Addr: 0x2000000B080466E0
Unit Part Number: 1400-00051-21
Unit Serial Number: LA70882151
Unit Model Type: Ax600(0x201), NIM Type: SAN(0x3)
Vendor Unique: ################################
System Serial Number: 9999999999

Repeat the process on the other CU. Important: There are two separate copies
of the ID PROM information on the
Slammer Midplane.
The ID PROM contents must be exactly
the same as read from both CUs before
attempting to install the new Slammer.
After the ID Prom has been verified on If there are more Slammers to be replaced,
both CUs, proceed with the Slammer repeat the entire process on the next
Slammer.
replacement or upgrade.
Be careful to mark the Slammers so they
can be installed in exactly the same
positions in the rack as the removed
Slammers.

Oracle Internal and Approved Partners Only Page 13 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
REPLACEMENT OF THE SLAMMER OR UPGRADE
CAUTION: A Slammer weighs 94 lb For safe handling, use two people to
(42.6 kg). remove or install a Slammer. Failure to
observe this caution may be a violation of
local labour safety rules or regulations.
If there are multiple Slammers, mark The WWN should be on the shipping
each existing and new Slammer with containers for the new Slammers as well
as on a small label on the top of the
the WWN. chassis, but that label is not visible when
the Slammer is installed in the rack.
Place the Ax500 in Shutdown. Using the GUI client select Axiom Shut
down to place the Ax500 in Shutdown.
Remove AC Power from the existing The Pilot CUs and Bricks should be left
Slammers. powered on.

Remove the external data connections, Mark the external data connections so they
the PMI Ethernet and the PI Fibre can be put in the same ports on the new
Slammer.
Channel Cables from the Slammer(s).
If there are optional iSCSI NICs The new Slammer may arrive with iSCSI
installed in the NIMs, remove these and NICs installed in the Network Interface
Modules. If so, do not move the existing
install them onto the Ax600 Slammer. NICs to the new Slammers.
Remove the existing Slammers from
the rack.
Install the Ax600 Slammers.
Install the cabling per the Advanced Refer to:
Hardware Installation Guide for Pillar http://support-
Axiom 600 and the Pillar Axiom 600 portal.pillardata.com/csportal/techdocs/tec
SSF Cabling Reference. hpub.seam
Notes: All PI FC cables must be copper,
as the Ax500 did not support optical
cables for the internal fibre channel. The
one exception is that the two FC0 to FC2
Hot Wire cables between the CUs in the
Slammer on single Slammer systems can
be optical.
Audit the cabling to make sure all Make sure the FC3 to FS10 cable is
cables are in the correct position. attached correctly on each Slammer CU.
This is the input to the fibre channel
switch in the PIM. If not present, the
Axiom cannot boot.
Install the external data path cables. Note: On some Slammers, the FC ports on
the FC HBA are upside down.
Using the GUI, restart the Axiom. Monitor the boot process.

Verify System and Data Status Verify that the System Status is Green
and Normal.
Verify that there are no Administrator
Alerts.
Verify that all user data resources are
fully Online.

Oracle Internal and Approved Partners Only Page 14 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check
Notify Customer of System Changes. If the replacement Slammers have 8 Gb
FC Interfaces, the data port WWNs may
have changed. The GUI will display the
new WWNs for the Slammer Ports, or you
may use the axiomcli slammer list
details request to obtain the data path port
WWNs. This will require re-zoning on the
fibre switch if soft zoning is implemented.
Be sure to inform the customer.
Some SAN appliances such as FalconStor
may require reconfiguration to access the
LUNs. The ASCII Product Identification
field in bytes 16-31 of the SCSI Inquiry
response was Axiom 500 and has
changed to Axiom 600 with the
Slammer conversion.
Verify Private Interconnect with a Run PitMan in Diagnostic mode to check
PITMAN test. for errors in the cabling.
See the GUI Administrator Help and the
Standard Procedure R5.x PITMAN for
details.
Return all excess FRUs, cables, etc. to
the Service depot.

Oracle Internal and Approved Partners Only Page 15 of 16 Vn 1.4 Created: 21. Dec. 2012
Task Comment Check

COMPLETION Perform always!


Verify data access. Hosts/servers and their applications must
be able to access their LUNs.
Re-enable CallHome and Email Alert. Send a Test Call Home to make sure the
test Call Home is received successfully by
the Oracle Customer Support Center.
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. File EIS-DOCS-Operational Handover-
Document.odt
Short briefing: on the configuration and Familiarize the customer with the new R5
basic Axiom Administration tasks are GUI, as the layout and concepts are quite
different.
reviewed with customer.
Also familiarize the customer with the
HTTP simple status screen, that may be
accessed with a smart phone and that can
access the customer network.
Contact the Oracle Customer Support Close the Service Request if the procedure
Center and close the Service Request. is completed with success.

Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that
you always check the web pages for the latest version.

Comments & RFEs are welcome. Oracle staff should mail to EIS-SUPPORT_WW@oracle.com .
Partners should mail to: SUPPORT-PARTNER-QUESTIONS_WW_GRP@oracle.com .

Oracle Internal and Approved Partners Only Page 16 of 16 Vn 1.4 Created: 21. Dec. 2012