Fs1 eis-nov-2014

EIS Installation Checklist for Oracle FS1 Flash Storage System

Customer:

TASK Number:

Technician:

Version EIS-DVD:

Date:

• It is recommend that the EIS web pages are checked for the latest version of this checklist prior to commencing the installation.

• It is assumed that the installation is carried out with the help of the current EIS-DVD. See EIS web pages for current information and status.

• 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 and not as a replacement for existing documentation.

• It is assumed that the installer has attended the appropriate training classes.• It is assumed that any Oracle server, to which the storage will be attached, has

been installed according to the appropriate EIS installation checklist.• This checklist can either be used when installing a new server with storage (in

conjunction with appropriate server checklist) or just ArrayStart when adding a FS1 System.

• While the FS1 System uses existing hardware, it is also an Engineered System and the installer should not make any changes to any component (e.g. changing any of the internal IP addresses).

• It is not intended that this checklist be handed over to the customer.• Feedback is welcome – refer to the last page of this checklist.

The following additional EIS Installation Checklists may be required:• Sun Rack II

Array Type Array-Serial# Array-Module Name

FS1-2

Oracle Internal and Approved Partners Only Page 1 of 13 Vn 1.0a Created: 19 Nov 2014

INFORMATION: ACRONYMS

CMACable Management Arm, a mechanical device that manages data and power cables for Controllers and Pilots that allow FS1 components to be moved into and out of their service positions.

DEDrive Enclosures – Just a Bunch Of Disks (JBOD) devices with up to 24 Hard Disk Drives.

IOM Input Output Module, the SAS interface to the Drive Enclosure.

PCUPower Cooling Units, a combination of a Power Supply and Fan into a single part.

PDUPower Distribution Unit, the rack component that distributes power from customer outlet to rack components.

USBUniversal Serial Bus, interface used for keyboard attachment for Pilots and Controllers.

PMIPrivate Management Interface, the network connections between Pilots and Controllers.

RU Rack Unit, 1.75” of vertical space in rack.

SAS Serial Attached SCSI, SCSI protocol used by FS1 systems.

Task Comment Check

PREPARATION

Read documentation according to the storage to be installed:• Release Notes• Hardware Installation Guide for Oracle

FS1 Flash Storage System,• Site Preparation Guide,• Rack Unpacking Instructions,• Oracle FS1 Flash Storage System SSF

Cabling Reference.

The documents referenced are located at:

http://docs.oracle.com/cd/E57980_01/index.htm

EIS Site-Audit Report complete? EISdoc V4:File EIS-DOCS-SiteAudit-FS1-2.odt

This is extremely critical for the following:

• Power connections inside the Rack.

• Location of FS1 components.

• Network connections

FAB/EIS-ALERT info reviewed?

EIS Installation Configuration Plan & Test Procedures Plan complete?

EISdoc V4:Use appropriate BUILD and TPP documentation.

The EIS TPP for the FS1 must be performed and completed after the install.



Task Comment Check

Determine the latest FS1-2SW version.

This will be required for the actions on page 11 of this checklist.

The FS1-2 Software/Firmware matrix is not currently available (November 2014). Work with the SR owner to obtain the latest available code for the installation.

Determine which Oracle FS1 Flash Storage System options have been ordered from the Sales Order.

Refer to the Sales Order. Determine if this will be not racked or the rack mounted option.

Non-Oracle rack to be used? • Must be EIA-310-D standard compliant.

• Must have adequate space for the following:• 2 Pilots = 1 RU each• 2 Controllers = 2 RUs each• X Performance DE = 2 RUs each• X Capacity DE = 4 RUs each

• Dual PDUs See the EIS Site-Audit Report for details.

Prepare for Delivery. The delivery company will contact the customer contact with delivery date and time details. The Oracle FSE should contact the customer to obtain that information when available.

Tools for Working with the FS1-2

Administration Tools:

• Workstation or laptop with PuTTY software• Ethernet cable

Physical Tools:

• LED headlamp or flashlight

Not Racked:• 12 mm wrench• Phillips screwdriver• 2 or more people capable of lifting 45 kilos / 99lbs over their

head or a genie lift.

Racked:

• A bag of necessary tools is attached to the rack as part of the contents of BOM.

The product documentation is available at: http://docs.oracle.com/cd/E57980_01/index.htm



Task Comment Check

UNPACKING

Oversee the delivery of the FS1-2. It is the responsibility of the delivery company to unpack and roll the rack into place into the data center. The Oracle FSE should be present for oversight to ensure that the delivery company follows proper procedure (e.g. doesn't roll it over a rough floor).

Save customer information packet called “System Record”.

There will be a customer information packet called “System Record” in a plastic bag attached to the front of the door panel. This packet will contain the labels with the system serial numbers that must be saved for entitlement purposes.

Verify delivery. • Inspect packaging for shipping damage

• Verify inventory packing list matches delivered items.

Acclimatise to inside ambient temperature.

Refer to EIS standard “Acclimatisation of Oracle Hardware Products”.

Unpack the FS1 system.

Note: If the customer is receiving more than one not racked FS1-2 at the same site boxes should be grouped according to system serial number. Do not unpack these boxes until you are ready to install to avoid mix and match of parts.

• Refer to unpacking instructions.

• Verify packing list with contents.

• Inventory and inspect all hardware for physical damage.

• Move FS1 into customer data center.

Verify all packing material has been removed, i.e. nothing is blocked.

Fans & air vents must be free to operate.


Task Comment Check

COMPONENT ASSEMBLY – NOT RACKED

The Not Racked option is for customer supplied racks. Racked system installations skip to the “FS1 System Power Up” section after completing Inter-Rack cabling if applicable.

Improve accessibility to rack. • Remove front and rear doors

• If possible, remove left and right side panels

Confirm Controllers have identical hardware. Physical inspection is only done externally.

Note: Both controllers have to be identical or one of them will not boot.

Confirm the following items via physical inspection:

• HBA cards and slots

• ESM Modules and slots

Component assembly and placement. Refer to the Hardware Installation Guide for Oracle FS1 Flash Storage System regarding the below:

It is critical that the components be reassembled in the same logical locations as was done in the manufacturing process. See box labels for this information.

• Sharing with other equipment

• Multiple racks

• Cable length limitations

• Pilots = 1U

• Controllers = 2U

• Performance Drive Enclosures = 2U

• Capacity Drive Enclosures = 4U

Attach World Wide node Number (WWnN) and System Serial Number (SSN) labels.

SSN:

• Top left inside Rack

• Front left side Rack near Pilots.

WWnN:

• Front of chassis on bottom Controller to the right of component SSN label.

Cabling Refer to the Hardware Installation Guide for Oracle FS1 Flash Storage System regarding the below:

• SAS cabling between Controllers and Drive Enclosures

• Power Cables

• Private Interface Cables

• Network cables

• Stress relief (CMAs)

• Secure data cables with velcro strips – do not use tie-wraps


Task Comment Check

Power Cabling. Some racks have sequencers that control order of output power to the components. Ensure the following power up sequence:

• Drive Enclosures

• Controllers

• MaxRep (if applicable)

• Pilots

Pilot Cabling. Perform pilot cabling to the below specifications:

• NET0 to other Pilot NET0

• NET1 to Controller NET3

• NET2 to other Pilot NETMGT

• NETMGT to other Pilot NET2

• SERMGT to other Pilot SERMGR via Null Modem cable

Controller Network and Serial ports See diagram below. Ports identified from left to right.

Controller Ports

Controller CablingPerform controller cabling to the below specifications:Management Ports:• SER MGT = unused• NET MGT = Connect to Opposite Controller’s Cluster Interconnect Network

port (↔)• Serial 0 = unused• Serial 1 = unused• Network = Connect to opposite Controller’s NET MGT

Network Ports:NET 3 = PMI connection to Pilot NET 1 (Controller 1 to Pilot 1, 2 to 2)• NET 2 = PMI connection to opposite Controller’s NET 2• NET 1 = NAS Host port• NET 0 = NAS Host port


Task Comment Check

Controller/Drive Enclosure cabling. Refer to the Hardware Installation Guide for Oracle FS1 Flash Storage System and the Oracle FS1 Flash Storage System SSF Cabling Reference. regarding the below:

• There are three types of SAS Cables:◦ Controller to Controller◦ Controller to IOM◦ IOM to IOM

• Balance Enclosures evenly across HBAs. The HBAs on Controller 1 connect to IOM 0 on the DEs. The HBAs on Controller 2 connect to IOM 1 on the DEs.

• IOM Port 0 is always the “ingress” IOM port to the DE. Ports 1 and 2 are always “egress” ports from the DE.

• A single HBA port can only support one string, which is a maximum of 5 DEs.

• A string is limited to 5 DEs. The DEs support the use of 3 IOM ports. No DE can be more than 3 hops from a controller HBA.

• IOMs in 2U (Performance) DEs are inverted making the port orientation the opposite when going left to right. IOMs in 4U (Capacity) and DEs are orientated the same.

• Use same SAS HBA slot/port from each Controller to the same DE string.

• Refer to the Build Map that is created by manufacturing and shipped with each not racked system. This is to be used in conjunction with the cable labels on the cables.


DRIVE ENCLOSURE CABLING DIAGRAM


Task Comment Check

FS1 SYSTEM POWER UP

Items below are specific to an Oracle supplied Rack; if your install involves non-Oracle Racks some comments may require adaptation on the part of the installer. Be extremely careful when working with PDUs that you do not power off any equipment already in production.

Attach the Rack Doors and Panels • Based on the type of door hinge, reassemble the hinges and reattach the doors.

• Reattach the door grounding straps on the rear door.

• Lock the front and back doors to the rack (optional).

Attach the Rack Side Panels. • Hang the top of the panel on the top of the rack frame and then latch the panel to close it. If the racks are bayed, you must only install the outer two panels.

• Secure the panel appropriately using one of the following options:• Engage the latch handle(s) and

snap the panel into place.• Screw the panels to the rack

frame at the top and bottom.• Lock both side panels (optional).

Position Rack into final location. • Lower levelling feet to data center floor (you will need a 12 mm wrench).

• Use a bubble level to adjust feet to make system level and plumb.

Connect FS1 to datacenter room power source.

• Ensure PDU circuit breakers are off.• Connect the PDUs to a facility power

source. If the facility's main circuit breakers are off, turn them on to supply power to the PDUs.

Pre-Power on checks. • Check all cables so there is no stress placed on other cables.

• Confirm redundant PCUs for each component go to different PDUs.

• Verify that all Drives (Pilot & DEs) and ESMs (Controller) did not become dislodged in shipping. Reseat as necessary.

• Connect laptop to pilot 1 NET3• Set laptop IP to 10.0.0.5


Task Comment Check

Power on system. Please refer to the Hardware Installation Guide for Oracle FS1 Flash Storage System for more details.• Turn on power switches for all DEs• Power on only one PDU and confirm

that each Pilot, Controller and DE has power.

• Power on second PDU.• Verify power up order, Drive

Enclosures should be first, Controllers second and then Pilots last.

Verify LEDs status. • Verify that the Fault LEDs are off.• Verify all Drive Enclosures and all

Controllers have unique IDs.

CONFIRM DE NUMBERING

The DE hardware has a DE ID label on the rear of the unit. The purpose of this label is to ensure the customer mounts and cables the DE as configured at the factory during Not Racked Installs. However, the DE ID display is configurable by the customer through the software. These labels are to be used during installation only, they should than be removed. At this point all references to DE numbering should be performed via the software.

• Lower DE numbers should be below higher DE numbers.

• This may be modified via GUI:From the System Tab, expand Hardware then select Drive Enclosures. In the main window, right click on the Drive Enclosure Then select Modify Chassis Display Number.

Racked systems may not have this label. When a racked system is powered on, the 7 segment display will show the DE ID. However they should still be lowest # on bottom and higher doing upwards.

The labels should be temporary labels and only come with Not Rack systems. The purpose is to allow the installer to properly identify the DE, by number, after its removed from the box. This is necessary so the DE can be installed in the correct physical location.

It would be advisable to wait until the machine is wired and powered on before removing the label. This allows the installer to verify the 7 segment display matches the label. If not, the system is wired incorrectly and can NOT be left in that state.

The wiring MUST be corrected before the installation is complete. It is not acceptable to simply change the DE number to match the location.

When powering on, if the DE numbers’s are out of order or do not match the temporary DE labels there is one of two problems:• The DEs are wired incorrectly, but

installed in the correct physical locations.

• The DEs are installed in the wrong order, but the wiring in actually correct.

The root cause MUST be identified. It is NOT acceptable to simply change the DE numbers to “look good”. The problem will not be solved. Use the FScli topology marksdb output to verify the DE wiring topology. Once the wiring is proven correct, the customer is free to modify the DE 7 segment displays as desired.


Task Comment Check

CONFIGURATION

Establish a temporary network between laptop and Pilot1.

Connect a cable to the Active Pilot.

• Default IP addresses:• 10.0.0.2 – Shared IP• 10.0.0.3 – pilot1 IP• 10.0.0.4 – pilot2 IP

• Confirm pilot1 default IP can be reached via “ping”.

If not already installed, download and Install GUI client to laptop.

• Point browser to 10.0.0.3• Go to Management Software and

download proper versions of GUI for platform being used.

• Install GUI and login with as default administrator:• Login: administrator• Password: pillar

Verify System Serial Number Verify System Serial Number displayed under System Information matches Rack Stickers and Sales Order.

Network settings. • If using DHCP, get Pilot MAC addresses

• If not using DHCP, manually update network settings after you have performed the TPP activity of testing a LUN. Leave the below as “default” until this activity is performed.• Shared IP address• Pilot IP addresses• Netmask• Gateway• NTP Server IP• Admin email address• Primary/Secondary DNS servers.

• Using the CMA, connect Pilots to customer LAN and confirm access.

Optional: upgrade to latest SW version. • The FS1-2 Software & version will have been obtained during the PREPARATION phase on page 3.

• If this FS1 system will use MaxRep, it is recommended that all systems run the same SW if possible.

Install GUI and CLI on customer system.

• Point browser at shared IP,• Download GUI and CLI that matches

customer platform,• Install GUI and CLI.


Task Comment Check

Update System Information. • System Name• Description• Location• Contact Name• Phone Number• Asset Number• Set NTP Server or System Time (In

the GUI click on System tab >> Global Settings >> SystemTime >> Actions, and then Modify.

• Confirm System Serial Number agrees between the GUI and on HW.

Set Controller Service Type. • Systems tab >>Hardware >> Controllers

• Right click on Controllers and select Modify Controller Service Type.

• Select Biased To SAN,• Select Restart and then select OK

Confirm Hardware: • From the System Tab, Expand HW, then select Controllers, right click on Controller 1. In new popup click on the individual components and compare with Controller 2.

• Confirm that each DE has the same drive type and capacity.

Note: This is not possible to do this for the pilots from the GUI.

Check the system status. The system status is displayed in the bottom left corner of the status bar of the GUI. A round green circle indicates that all hardware components in the Oracle FS1 system have successfully started and are operating normally.

Check for Administrator Actions/Alerts:

If there is an Administrator Action or Alert present, there will be a small flashing triangle on the bottom of the GUI screen, next to the System Status icon.

Resolve all Topology Validation Alerts before proceeding to Private Interface Validation Testing.

Perform FSCLI topology testing. Refer to the TPP for all validation testing.


Task Comment Check

VERIFY SERVICEABLE INSTALLATION

Verify browser access to FS1. This is performed by logging into the FS1 system.

Configure Call-Home. • Refer to the Section Configure Call-Home for ASR in the Oracle FS1-2 Flash Storage System Installation Guides.

• Contact SR owner to confirm.

Attach host cabling. • Host connections are made to Controller HBAs in slots 1/4/5.

• NET0 & NET1 are optional NAS connections.

Note: NAS is not available for this product at G.A.

Optional PDU connections (racked systems only):

Configure PDU monitoring Units – refer to the EIS installation checklist for Sun Rack II.

Task Comment Check

VERIFICATION & HANDOVER

Restart => everything OK? Restart system via GUI.

Perform Installation Assessment tests as described in the EIS Test Procedures Plan.

EISdoc V4 – completed during preparation of installation.

Inform the Customer that once the FS1 is included in a Support Contract that their Customer User Administrator (CUA) should configure the system for ASR:

• Refer to the Section Configure Call-Home for ASR and Activate ASR in the Oracle FS1-2 Flash Storage System Installation Guides.

• MOS Document ID 1329200.1 – How to Manage and Approve Pending ASR Assets in My Oracle Support.

Complete documentation and hand over to customer.

EISdoc V4:File EIS-DOCS-Operational Handover-Document.odt

Short briefing: on the configuration and basic FS1 Administration tasks are reviewed with customer.

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] .


https://support.oracle.com/rs?type=doc&id=1329200.1

Fs1 eis-nov-2014

Devices & Hardware