This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial technical
data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable
by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
its affiliates. All rights reserved.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
This software or hardware and documentation may provide access to or information on content, products
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.
Ce logiciel
sont concédés sous licence et soumis à des restrictions d’utilisation et de divulgation. Sauf disposition de
votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier,
breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous
quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie
inverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des
logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs,
Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui en
faire part par écrit.
Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des EtatsUnis, ou à toute entité qui délivre la licence de ce logiciel ou l’utilise pour le compte du Gouvernement des
Etats-Unis, la notice suivante s’applique :
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial technical
data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable
by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City,
CA 94065.
et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils
Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des
informations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné à être utilisé dans des applications à
risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce
logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre
toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son
utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute
responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type
d’applications.
Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom
mentionné peut correspondre à des marques appartenant à d’autres propriétaires qu’Oracle.
Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens
donnant accès à des contenus, des produits et des services émanant de tiers. Oracle Corporation et ses
affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services
émanant de tiers. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour
responsables des pertes subies, des coûts occasionnés ou des dommages causés par l’accès à des
contenus, produits ou services tiers, ou à leur utilisation.
3
Page 4
Table of Contents
Preface
Chapter 1 Before You Begin
Pillar Axiom 600 Series Components...................................... 21
This guide is for data center system administrators and Professional
consultants who install Oracle’s Pillar Axiom Storage System that come with
most components already installed in Pillar racks. We assume that you
understand how to perform the following actions:
●Assemble hardware components
●Connect the components to the LAN and to power circuits
●Use a graphical user interface (GUI) in a web browser
This guide explains how to perform the following actions:
●Position and stabilize a populated rack in the data center
●Create rack bays
●Install hardware components.
●Connect the system to inlet power and to the networks
●Turn on the system
●Perform initial configuration
Services
●Add additional Brick storage enclosures and Slammer storage controllers to
expand an existing Oracle Pillar Axiom 600 system
Before You Read This Guide
Being familiar with certain other technical documentation for Oracle’s Pillar
Axiom 600 helps you succeed in the use of this guide.
Before you install Oracle’s Pillar Axiom 600 system, you should be familiar with
certain basic characteristics of the environment in which you intend to install the
system.
15
Page 16
Preface
To review those basic environmental characteristics, refer to the following
resources that you completed earlier with the assistance
representative:
●
Site Preparation Survey
●
Storage Requirements Survey
In addition to this guide, review the late-breaking information described in the
Pillar Axiom Customer Release Notes
information that was not available at the time this guide was published, including:
●Errata for technical documents (including this guide).
●Network requirements.
●Known issues.
●Various notations on the operation of Oracle’s Pillar Axiom 600 system.
. That information includes important
of your Pillar
There is also additional documentation in the
Reference
Slammers in various configurations.
guide, which includes detailed information on the cabling of Bricks and
How This Guide Is Organized
This guide provides procedural and reference information to install the various
components within an Oracle Pillar Axiom 600 system, power it on, and perform
the initial configuration.
To perform any upgrade, you must contact the Pillar World Wide Customer
Support Center. Upgrade procedures are beyond the scope of this guide.
The guide is divided into seven chapters and three appendices:
●Chapter 1 provides information on the Oracle Pillar Axiom 600 system
components, equipment and tools required by the customer for the
installation process, and safety notices.
●Chapter 2 provides information on setting up the rack, component
placement plans for various system configurations, and installing mounting
rails for the Slammers, the Bricks, and the Pilot.
Pillar Axiom 600 SSF Cabling
●Chapter 3 provides information on the installation of power distribution units
(PDUs), Slammers, Bricks, and the Pilot.
●Chapter 4 provides information on the data cable connections within the
Oracle Pillar Axiom 600 system.
16
Page 17
Preface
●Chapter 5 provides information on the power cable connections within the
Oracle Pillar Axiom 600 system.
●
Chapter 6 provides information on the final steps to complete the
installation. This includes procedures on powering on the system, verifying
the status of various LEDs, attaching bezels on the system components,
and attaching rack doors and panels.
●Chapter 7 provides information on how to access the Pillar Axiom Storage
Services Manager GUI and to perform the initial configuration.
●Appendix A provides information on the various LED codes and what they
indicate.
●Appendix B summarizes all warning and caution notices in various languages.
●Appendix C provides reference information on the hardware specifications
for the Oracle Pillar Axiom 600 system and its various components.
●Appendix D provides information on adding additional Bricks to an Oracle
Pillar Axiom 600 system and the associated cabling of those Bricks.
●Appendix E provides information on adding additional Slammers to an
Oracle Pillar Axiom 600 system and the associated cabling of those
Slammers.
Related Documentation
Table 1 Additional information resources for all systems
DescriptionTitle and part number
The definitions of terms found in the Oracle Pillar Axiom 600
documentation.
An introduction to the hardware and software architecture of
an Oracle Pillar Axiom 600 system.
Removal and insertion instructions for field replaceable units
(FRUs).
Pillar Axiom Glossary
Pillar Axiom System Architecture
Overview
Pillar Axiom 600 Service Guide
Cabling instructions for Bricks and Slammers within a Pillar
rack.
Pillar Axiom 600 SSF Cabling
Reference
17
Page 18
Preface
Table 1 Additional information resources for all systems (continued)
DescriptionTitle and part number
Any late breaking information regarding the Oracle Pillar
Axiom 600 systems.
Access Documentation
Technical documentation (including
administration guides) for Oracle’s Pillar Axiom 600 storage system is available
from several sources.
Pillar Axiom
Storage Services
Manager
Pillar Axiom HTTP
access
InternetCustomer support portal (http://support-portal.pillardata.com/
Log in to your Pillar Axiom system. Navigate to the
area in the Pillar Axiom Storage Services Manager and
select the
Documentation
For Pillar Axiom systems running release 5.0 (and higher)
software, point your browser to http://
documentation.php, where
or the public IP address of your system.
csportal/login.seam).
Pillar Axiom Customer Release
Notes
installation, service, cabling, integration, and
Support
link.
system-name-IP
system-name-IP
is the name
/
Log in and click
Product CD-ROMInsert the Technical Documentation CD-ROM (came with
your Pillar Axiom system) into the CD player and open the
DocMenu PDF.
Tip: To search all technical documents on the CD-ROM,
click
Typographical Conventions
Documents
Search all PDFs
in the top right corner.
in the left navigation pane.
18
Page 19
Preface
Table 2 Typography to mark certain content
ConventionMeaning
italics
Within normal text, words in italics indicate:
●A reference to a book title.
●New terms and emphasized words.
●Command variables.
monospaceIndicates one of the following, depending on the context:
●The name of a file or the path to the file.
●
Output
line.
monospace
(bold)
>Indicates a menu item or a navigation path in a graphical
...
Input
provided by an administrator on the command line.
user interface (GUI). For example, “Click
LUNs
” means to click the
page in the graphical user interface (GUI).
Used within an expression of a navigation path or within a
cascading menu structure. The ellipsis indicates that one
or more steps have been omitted from the path or menu
structure. For example, in the
Actions
implies that one or more menu items have been omitted.
>
displayed by the system on the command
Storage
...
>
Data Protection
Clone LUNs
>
Create
link on the
Groups
>
Volume Groups
menu structure, the
>
Clone
Storage
>
...
Pillar Contacts
Table 3 Contacts at Pillar Data Systems
For help with...Contact...
Error messages,
usage questions, and
other support issues
US and Canada:
Europe: +800 PILLAR FS (+800 74 55 27 37)
Asia Pacific: +1-408-518-4515
South Africa: +0 800 980 400
877-4PILLAR (1-877-474-5527)
19
Page 20
Preface
Table 3 Contacts at Pillar Data Systems (continued)
For help with...Contact...
Have your system serial number ready.
support@pillardata.com
Pillar Customer Support (http://support-
portal.pillardata.com/csportal/login.seam)
Training (custom or
packaged)
Professional services
and inquiries
Sales and general
contact information
Documentation
improvements and
resources
Training and Education (http://www.pillardata.com/
support-education/training/)
globalsolutions@pillardata.com
Global Solutions (http://www.pillardata.com/support/
professional-services/)
Company contacts (http://www.pillardata.com/company/
contact)
docs@pillardata.com
Technical documents (http://www.pillardata.com/
techdocs) (Log in with your username and
password, and
select Documents.)
20
Page 21
Chapter 1
Before You Begin
CHAPTER
1
Before You Begin
Pillar Axiom 600 Series Components
Pillar Axiom 600 systems contain a specific combination of the components listed
in the following table:
Table 4 Pillar Axiom 600 series components
Product nameModel and description
Brick storage
enclosures
●BRX 1000S7—Brick,SATA,13 x 1TB,7200 RPM
drives,RoHS
●BRX 2000S7—Brick,SATA,13 x 2TB,7200 RPM
drives,RoHS
Table 4 Pillar Axiom 600 series components (continued)
Product nameModel and description
●PDU 500-3P16A—230V, 16A, IEC; (230/400)
Racks●RACK500-42U—42U cabinet assembly with doors
Note: The following Pillar Axiom 600 components
are no longer available for new systems:
●BRX 500-160A7
●BRX 500-250A7
●BRX 500-73F15R
●BRX 500-73F15E
●BRX 500-400A7
●BRX 500-500A7
●BRX 500-750A7
●BRX 500-146F15R
●BRX 500-146F15E
●BRX 300-F15E
●BRX 450-F15E
continue to be supported but
●BRX 300F15R
●BRX 450F15R
●BRX 2000S5
●SLM 600 (Series 1, Series 2)
Pillar Axiom 600 Series Components22
Page 23
Chapter 1
Before You Begin
Customer-Supplied Equipment and Tools
Before starting the installation of a Pillar Axiom 600 system, be sure you have
needed equipment and tools installed or available.
Table 5 Required tools
ToolPurposeIllustration
1/4 inches (7 millimeters)
flat-tip screwdriver
Adjustable wrench, 6
inches (15 centimeters)
#1 and #2 Phillips-head
screwdrivers
Socket wrench with a 1/2inches (13millimeters)
socket
Adjust leveling feet.
Adjust leveling feet.
Remove and secure Pillar
Axiom 600 hardware
components.
Connect two racks.
the
Offset box wrench, 13/32
inches (10 millimeters)
Torx® T20 screwdriverAttach rail assemblies to
Torx® T30 screwdriverConnect two racks.
Wire cuttersCut tie wraps.
Note: These tools are not included with the Pillar Axiom 600
Work with adjustable
mounting rail assemblies.
the vertical channels and
secure hardware
components to the rails.
system.
To install a Pillar Axiom 600 system you need to have the following equipment
and supplies available or installed before you start the installation of the system:
Customer-Supplied Equipment and Tools23
Page 24
Chapter 1
Before You Begin
Table 6 Required equipment and supplies
On hand?ItemPurpose
At least two power sources on
independent circuits with
appropriate
connectors for the
voltage and amperage ratings
Copper Ethernet switch with
two open 10/100 ports
Two Category 5 100BaseT
cables
For each NAS Slammer, two to
four GbE capable (copper or
optical) cables
For each NAS Slammer, a
copper or optical Ethernet
switch with at least two open
GbE ports
For each SAN Slammer, two to
four SAN Fiber-optic cables
Provide power to the PDUs.
Pillar Axiom 600 systems
require redundant power
supplies from two PDUs on
separate input circuits.
Connect Pilot management
ports to the Ethernet LAN.
Connect Pilot management
ports to the Ethernet switch.
Connect NAS Slammer network
data ports to the LAN.
Each NAS Slammer has four
network data ports. At least one
port for each Slammer control
unit (CU) must be connected.
Connect SAN Slammer data
ports to the fabric.
For each SAN Slammer, two to
four open ports on the SAN fabric
Each SAN Slammer has four
data ports. At least one port for
each Slammer CU must be
connected.
Workstation on the same LAN
as the Pilot and with a
supported browser
Connect to the Pillar Axiom
Storage Services Manager to
carry out the final installation
tasks.
Customer-Supplied Equipment and Tools24
Page 25
Chapter 1
Before You Begin
Safety Notice Conventions
Hazard signal words conform to the American National
(ANSI) Z535.4-2002 meanings. This guide uses the following conventions for
safety notices:
Caution
Warning
Danger
Important! To emphasize a point, to remind you of something, or to indicate
potential problems in the outcome of the in-process task.
A set of important safety notices apply throughout this guide. Read them before
working on a Pillar Axiom 600 system.
Related concepts
•
Safety Statements
Related references
•
Caution Notices
•
Warning Notices
Indicates a potentially hazardous situation that, if not
avoided, may result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in death or serious
Indicates an imminently hazardous situation that, if not
avoided, will result in death or serious
Standards Institute
injury.
injury.
Safety Notice Conventions25
Page 26
Chapter 2
Set Up the Rack
CHAPTER
2
Set Up the Rack
About Component Inspection
Each Pillar Axiom 600 system is built to a customer's specifications and shipped
in a single shipment. Check the components you received against the packing
slip (or bill of lading), which lists everything that was shipped. If any components
are missing, call 1-877-4PILLAR (474-5527) and report what was not included in
your shipment. Note how many pallets or containers you received, in case the
missing components are in a container that simply has not yet arrived.
Caution
Caution
A Brick weighs up to 65 pounds (29.5 kilograms). For safe
handling, use two people to lift it.
A Slammer weighs 94 pounds (42.6 kilograms). For safe
handling, use two people to lift it.
Caution
After you remove the components from their packaging, inspect them for any
damage that may have occurred during shipping. If there is any damage:
1Check your Terms of Sale to see who notifies the carrier.
2Notify the carrier or the Pillar World Wide Customer Support Center, as
appropriate, within 72 hours.
Before you handle a component, make sure that you have
taken electrostatic discharge (ESD) precautions:
●The minimum requirement is an anti-static wrist strap
connected to a hard ground. Pillar recommends that
you remove components from their packaging and
place them on an ESD-qualified table that is equipped
with ground points for wrist straps.
●Static charges can build up rapidly on rolling carts. If
you transport a hardware component by cart, ground
the cart with a drag chain on an ESD floor. If there is
no ESD cart available or ESD floor, ground yourself
before you touch a component that has been
transported on a cart.
About Component Inspection26
Page 27
Chapter 2
Set Up the Rack
3Record all damage.
4Call the Pillar
World Wide Customer Support Center to open a service
request for future insurance claims.
Tip: Check the packing materials to verify that you have retrieved all the small
parts before recycling.
Important! Pillar Axiom 600 system components are compatible with racks that
are compliant to the EIA-310-D standard. Pillar Axiom 600 Slammers and Bricks
may not install successfully into a rack that is not EIA-310-D compliant. We
recommend that Pillar racks be used to install Pillar Axiom 600 hardware
components. When using non-Pillar racks, do not use Telco two-post racks.
Instead, use a four-post rack that can support the weight load of a Pillar
Axiom 600 system. Additionally, be sure the non-Pillar rack has square mounting
holes in the vertical channels. Round mounting holes are not acceptable.
Illustrations show a Pillar Axiom 600 42U rack or parts of it. If you have a nonPillar rack, it should be similar.
About Component Inspection27
Page 28
Chapter 2
Set Up the Rack
Rack Position
The following figure illustrates a floor plan
for new rack installations. The space
around the rack (or bay, if you have multiple racks) is needed to perform the
installation tasks safely.
Figure 1 Floor plan for rack installation
Legend
1 Back of unit
2 60 inches (152 centimeters)
3 96 inches (244 centimeters)
4 36 inches (91 centimeters)
5 139 inches (353 centimeters)
About Multiple Rack Connections
If you are installing more than one rack, make sure that the racks are leveled
that they align correctly before you attach the baying plates. If you do not have
multiple Pillar racks, you can skip this section and proceed to adjust the leveling
legs.
Related tasks
•
Adjust the Leveling Legs
so
Rack Position28
Page 29
Chapter 2
Set Up the Rack
Prepare the Racks
To create a bay of Pillar racks, first remove the adjacent (inner) side panels from
each rack (see the following figure) and move the racks into position. You will
route the cables directly from one rack to the other through the open sides of the
racks because the cables are not long enough to route through a raised floor.
Figure 2 Sample 42U side panels
Legend
1 Side panel, one on each side
2 Latches
1If locked, unlock the side panel using the supplied keys.
2Unlatch the side panel by:
●Pushing the release button, or
●Lifting the release handles.
3Remove the side panel and set it aside.
Rack Position29
Page 30
Chapter 2
Set Up the Rack
4Position the racks so that their open sides abut and their front sides are flush.
Attach the Connection Bracket
The connection bracket provides extra rigidity
to the bay.
Important! Make sure that at least one of the racks is not anchored so you can
adjust its position while you attach them together.
1Locate the two adjacent frame corners at the top and at the back of two
racks that are to be connected.
Figure 3 Location of frame corners
Legend
1 Front
2 Top rear frame corner
3 Second rack, inside view
4 Threaded screw holes
5 Looking up into top rear frame corner, with a second rack moved close for
attachment
2Place the connection bracket into the frame corner.
Rack Position30
Page 31
Chapter 2
Set Up the Rack
Figure 4 Connection bracket installation
Legend
3Insert an M8 hex screw through the hole in one of the bracket corners.
4Loosely screw the M8 screw
5Insert an M8 hex screw through one of the other corner holes in the bracket
and loosely screw it into the threaded hole in the frame.
6Repeat Step 5 for the other two corner holes.
7Tighten the screws after all the bay connections are in place.
Attach the Baying Plates
Baying plates bind two Pillar racks together at the roof and bottom of the rack.
1 Frames
2 Baying connection bracket
3 M8 hex screws
into the threaded hole in the frame.
Tip: Use the stabilizer plate in conjunction with the baying kit that comes with
each rack.
Rack Position31
Page 32
Chapter 2
Set Up the Rack
1At the front of each rack roof, use a T30 Torx® screwdriver to remove the
two adjacent Torx-head screws and set them aside.
2
Place a baying plate over the two holes.
Figure 5 Roof baying plate attachment
Legend
1 Roof baying plates
2 M12 Torx screws
3Insert a Torx screw (from Step 1) into each plate hole.
4Re-seat the Torx screws loosely.
Repeat Steps 1 through 4 for the two holes at the back of the roof.
5
6At the bottom of the adjacent rack sides, remove the anti-tip brackets, if
any, and unscrew the anchor bolts.
Rack Position32
Page 33
Chapter 2
Set Up the Rack
Figure 6 Adjacent anchor bolts at the front of the racks
Legend
1 Anchor bolts
7Hold the baying plate across the two anchor-bolt holes and loosely replace
the anchor bolts.
8Repeat Steps 6 and 7 in the back
9Use the socket wrench to tighten the connection bracket screws.
10Use the T30 Torx-head screwdriver to tighten the top baying plate screws.
11Use the 3/4-inches (19-millimeters) open-end wrench to tighten the bottom
baying plate anchor bolts.
Related tasks
•
Install a Stabilizer Plate (Optional)
Adjust the Leveling Legs
of the racks.
Racks have built-in leveling legs at each corner. Adjust these legs so they are in
firm contact with the floor and the rack is level. If the rack connects to others,
adjust the legs so the racks are at the same height and can be bolted together.
Rack Position33
Page 34
Chapter 2
Set Up the Rack
1Turn each leveling leg clockwise to lower the feet until they touch the floor.
Use a 1/4-inches (7-millimeters) flat-tip screwdriver in the slot at the top of
the leg.
Figure 7 Rack leveling
Legend
1 Caster brackets
2 Leveling legs are pre-installed in each caster bracket.
leg locations
2Use a 3/4-inches (19-millimeters) open-end wrench on the bottom of the
legs to jack up the rack. Raise the rack until it is level with all the casters off
the floor.
Figure 8 Leveling
leg adjustment
Legend
Rack Position34
1 Caster brackets
2 Slot in the leveling leg for a screwdriver
Page 35
Chapter 2
Set Up the Rack
Note: If you connect racks in a bay it is more important that the racks be at
the same height than level so that you can bolt them together.
About Rack Stability
After you move the rack to its final position and adjust
it to keep it from shifting when you install the components.
You can use any combination of the following actions to stabilize the rack:
●Attach anti-tip brackets and secure them to the floor.
●Attach a stabilizer plate and secure it to the floor.
●Install a seismic stabilization system.
Important! If the rack will be part of a bay of racks, attach the rack to the bay
before you install stabilizer plates or some other seismic stabilization system.
Related tasks
•
Install the Anti-Tip Brackets
•
Install a Stabilizer Plate (Optional)
About Anti-Tip Brackets
One stabilization option is to install the anti-tip brackets that are included with the
system. Before you install the anti-tip brackets, consider:
the legs, you must stabilize
●If you intend to bay the rack with another Pillar rack, you must use baying
plates on connecting corners. Baying plates prevent the use of anti-tip
brackets so you must stabilize the bay with stabilization plates.
●Make sure that the rack is in its final position before you secure anti-tip
brackets to the floor.
●Anti-tip brackets may require a sub-floor tie-down system if the floor has
removable panels.
●For solid floors, drill holes into the floor and use appropriate anchor bolts to
secure the anti-tip brackets.
Important! If you intend to install an optional stabilizer plate, do not install the
front anti-tip brackets.
Rack Position35
Page 36
Chapter 2
Set Up the Rack
Install the Anti-Tip Brackets
1Screw the anchor bolt into the bottom outside corner of the rack frame until
the bolt is seated.
Figure 9 Attach anchor bolts to rack
2Slide the bracket fingers into the anchor bolt pocket as illustrated in the
following figure.
Figure 10 Position
Legend
anti-tip brackets
1 Anti-tip bracket fingers2 Anchor bolt
Rack Position36
Page 37
Chapter 2
Set Up the Rack
3Position the anti-tip bracket so that it points away from the rack and is
parallel to the sides.
4
Adjust the anchor bolt so that it is finger-tight against the anti-tip bracket,
and secure the anti-tip bracket to the floor.
Figure 11 Secure anti-tip brackets to the floor
5Repeat Step 1 through Step 4 for all four corners.
About Stabilizer Plate Installation
At the front of the rack, you can install an optional stabilizer plate instead of antitip brackets. Stabilizer plates
which must be removed in order to install a stabilizer plate. You cannot use antitip brackets in a bay because the anchor bolts are used to hold the baying plates
in place. Therefore you should use stabilizer plates for racks in a bay.
Also note that if you have removable floor panels, you must bolt the stabilizer
plates through to the solid sub-floor.
Install a Stabilizer Plate (Optional)
Use stabilizer plates to provide greater stability than anti-tip brackets for the Pillar
Axiom 600 system.
provide greater stability than anti-tip brackets,
1Place the stabilizer plate at the front of the rack with the short side up.
Rack Position37
Page 38
Chapter 2
Set Up the Rack
2While adjusting the leveling legs to raise or lower the rack, align the holes in
the short side with the holes in the rack frame.
3
Insert an M8 bolt into each hole in the short side of the stabilizer plate.
4Use the hex wrench to tightly bolt the stabilizer plate to the rack.
Figure 12 Stabilizer plate attached to the rack base and floor
Legend
1 M12 (or larger) floor bolts
2 M8 allen-head bolts
5Secure the stabilizer plate to the floor with bolts and washers that are
appropriate for the type of floor.
Important!
The floor bolts must be no smaller than M12 in size.
Rack Position38
Page 39
Chapter 2
Set Up the Rack
About Component Placement
For non-Pillar racks, all component rails must be installed
components into the racks.
Pillar racks come with the component rails pre-installed. If you have Pillar racks,
you can install the components right away.
Install the component rails according to the component placement diagrams for
your system configuration. Install them in the order of:
●First, Pilot rails near the bottom of the rack, 2U above the PDUs.
●Second, Slammer rails above the Pilot rails.
●Third, Brick rails above the Slammer rails.
Caution
If you are building a rack that only contains Bricks, you should still start from the
bottom.
Some Pillar Axiom 600 components weigh over 65
pounds (29.5 kilograms). Make sure all rail components
tightly secured before loading the components to prevent
damage and injury.
before loading
are
Note: The physical location of the components in the Pillar Axiom 600 rack can
vary if the system is installed in the field. Always check the cables at the back of
the rack to validate the physical location of each Brick.
Note: After a new installation or a Brick upgrade, the physical and logical name
of a new Brick might not be the same. To avoid potential confusion, Pillar
recommends that you change the logical name of the Brick to match the physical
name.
Related concepts
•
About Component Placement for One Slammer and SATA Bricks
•
About Component Placement for One Slammer and FC Bricks
•
About Component Placement for Two or Three Slammers and FC Bricks
•
About Component Placement for Four Slammers and 64 Bricks
Configuration Limits for a Pillar Axiom 600 System
The minimum configuration of the Pillar Axiom 600 system is:
About Component Placement39
Page 40
Chapter 2
Set Up the Rack
●One Pilot
●One Slammer
●
One Brick
The maximum configuration of the Pillar Axiom 600 system is:
●One Pilot
●Four Slammers
●64 Bricks
Table 7 defines the maximum configuration limits for a Pillar Axiom 600 system.
The maximum number of Bricks that a Pillar Axiom 600 system can support
depends on the number of Slammers in the system. The maximum
configurations are given in terms of width (the number of strings), depth (the
number of Bricks for each string), and the maximum number of Bricks that the
system supports.
Table 7 Configuration limits for a Pillar Axiom 600 system
Number of
Slammers
14832
28864
38864
416864
Maximum
number of
strings
Maximum
number of Bricks
in a string
Maximum
number of Bricks
in the system
Brick storage enclosures can contain Fibre Channel (FC), Serial ATA (SATA), or
solid state drives (SSDs), depending upon the type of RAID controllers.Table 8
further classifies the configuration
limits by the type of Bricks in the Pillar
Axiom 600 system. The maximum number of a specific Brick (SATA, FC, or
SSD) allowed in the Pillar Axiom 600 system also depends on the number of
Slammers in the system.
About Component Placement40
Page 41
Chapter 2
Set Up the Rack
Table 8 Brick configuration limits for the Pillar Axiom 600 system
Number of
Slammers
132328
2643216
3643216
4643232
Maximum
number of SATA
Bricks
Maximum
number of FC
Bricks
Maximum
number of SSD
Bricks
For single-Slammer Pillar Axiom 600 configurations, the minimum number of
Bricks is one. However, for mixed configurations, the minimum number of Bricks
is three, as outlined below:
●
For a mix of FC and SATA (or SSD) Bricks: 2 SATA (or SSD) + 1 FC or 2
FC + 1 SATA (or SSD).
●For a mix of SSD and SATA Bricks: 2 SATA + 1 SSD or 2 SSD + 1 SATA.
Pillar Axiom 600 systems support up to 32 FC Bricks, or 64 SATA Bricks, or 32
SSD Bricks or any combination of these three types, provided there are no more
than 64 total Bricks, 32 FC Bricks or 32 SSD Bricks in the system.
Important! Contact the Pillar World Wide Customer Support Center for any newly
available, time-sensitive information regarding cabling. Also, refer to the
Axiom Customer Release Notes
for the latest system configurations.
About Component Placement for One Slammer and SATA Bricks
Pillar Axiom 600 systems with one Slammer support up to 32 SATA Bricks.
The figure above illustrates how the Pillar Axiom 600 system components are
mapped into 42U racks for the following configuration:
●1 Pilot
●1 Slammer
Pillar
●32 SATA Bricks (Pillar Axiom 600 systems)
About Component Placement41
Page 42
Chapter 2
Set Up the Rack
Figure 13 42U racks containing one Slammer and up to 32 SATA Bricks
Legend
Note: The physical Brick names used above are for illustration
1 Reserved for PDU cable routing2 Rack unit (RU) locators
and indicate the
physical location of the Brick in the rack. The actual names or logical names, as
seen in the Pillar Axiom Storage Services Manager, can be different. The logical
location or numbering of each Brick is determined during the installation and
follows the scheme Brick001, Brick002, Brick003, and so on.
Note: Filler panels should be mounted wherever an airflow path short-circuit
could exist. Filler panels should be mounted on the front rails to fill any spaces
below the Pilot or the lowest Pillar Axiom 600 component in the rack. Single
Phase PDUs are mounted on the rear rails so that there are filler panels in the
front. Three-phase PDUs are mounted on the front rails so that there is no need
for the filler panels or the 2U of space above them.
Any components that are not installed must be replaced with filler panels.
About Component Placement42
Page 43
Chapter 2
Set Up the Rack
Note: 2U of space is reserved above the PDUs for cable routing. The number
and type of PDUs depends
on the power supply. If more PDUs are needed, or
when you need to add additional components into the rack (such as adding
another Slammer), then everything has to move up to make room, keeping
the 2U of reserved space, and moving any Bricks displaced at the top to the next
rack.
Note: In a system that is configured for the maximum number of Bricks, connect
the additional racks to the first rack before you install and cable the hardware
components.
Related references
•
Cabling Practices for the Pillar Axiom 600 System
Related tasks
•
Rename the Bricks
About Component Placement for One Slammer and FC Bricks
Pillar Axiom 600 systems with one Slammer support up to 15 Fibre Channel (FC)
Bricks.
Install the hardware components in the rack as shown in the following figure. Any
components that are not installed must be replaced with filler panels.
The figure below illustrates how the Pillar Axiom 600 system components are
mapped into a fully loaded 42U rack for the following configuration:
●1 Pilot
●1 Slammer
●15 FC Bricks
About Component Placement43
Page 44
Chapter 2
Set Up the Rack
Figure 14 Fully loaded 42U rack for one Slammer and 15 FC Bricks
Legend
Note: The physical Brick names used above are for illustration
1 Reserved for PDU cable routing
2 Rack unit (RU) locators
and indicate the
physical location of the Brick in the rack. The actual names or logical names, as
seen in the Pillar Axiom Storage Services Manager, can be different. The logical
location or numbering of each Brick is determined during the installation and
follows the scheme Brick001, Brick002, Brick003, and so on.
Note: Filler panels should be mounted wherever an airflow path short-circuit
could exist. Filler panels should be mounted on the front rails to fill any spaces
below the Pilot or the lowest Pillar Axiom 600 component in the rack. Single
Phase PDUs are mounted on the rear rails so that there are filler panels in the
front. Three-phase PDUs are mounted on the front rails so that there is no need
for the filler panels or the 2U of space above them.
About Component Placement44
Page 45
Chapter 2
Set Up the Rack
Note: 2U of space is reserved above the PDUs for cable routing. The number
and type of PDUs depends
when you need to add additional components into the rack (such as adding
another Slammer), then everything has to move up to make room, keeping the
2U of reserved space, and moving any Bricks displaced at the top to the next rack.
Related concepts
•
About Component Placement for Two or Three Slammers and FC Bricks
•
About Component Placement for Four Slammers and 64 Bricks
Related references
•
Cabling Practices for the Pillar Axiom 600 System
Related tasks
•
Rename the Bricks
on the power service. If more PDUs are needed, or
About Component Placement for Two or Three Slammers and FC Bricks
Pillar Axiom 600 systems with two or three Slammers support up to 32 FC Bricks.
Note: This topic applies only to Pillar Axiom 600 systems.
Install the hardware components in the rack as shown in the following figure. This
figure illustrates how the Pillar Axiom 600 system components are mapped into
fully loaded 42U racks for the following configuration:
●1 Pilot
●3 Slammers
●32 FC Bricks
About Component Placement45
Page 46
Chapter 2
Set Up the Rack
Figure 15 Fully loaded 42U racks for three Slammers and 32 FC Bricks
Note: The physical Brick names used above are for illustration
and indicate the
physical location of the Brick in the rack. The actual names or logical names, as
seen in the Pillar Axiom Storage Services Manager, can be different. The logical
location or numbering of each Brick is determined during the installation and
follows the scheme Brick001, Brick002, Brick003, and so on.
Note: Filler panels should be mounted wherever an airflow path short-circuit
could exist. Filler panels should be mounted on the front rails to fill any spaces
below the Pilot or the lowest Pillar Axiom 600 component in the rack. Single
Phase PDUs are mounted on the rear rails so that there are filler panels in the
front. Three-phase PDUs are mounted on the front rails so that there is no need
for the filler panels or the 2U of space above them.
Note: Any components that are not installed must be replaced with filler panels.
Also, 2U of space is reserved above the PDUs for cable routing. Three-phase
PDUs already have 2U of space and do not need the cable routing space. The
number and type of PDUs depends on the power service. If more PDUs are
needed, or when you need to add additional components into the rack (such as
adding another Slammer), everything has to move up to make room, keeping the
2U of reserved space and moving any Bricks displaced at the top to the next rack.
If only two Slammers are being installed, replace Slammer 3 with two filler panels.
About Component Placement46
Page 47
Chapter 2
Set Up the Rack
Note: In a system that is configured for the maximum number of Bricks, connect
the additional racks to the first rack before you install and cable
components.
Related concepts
•
About Component Placement for Four Slammers and 64 Bricks
•
Sample Power Cabling for One Slammer and Three Bricks
Related references
•
Cabling Practices for the Pillar Axiom 600 System
Related tasks
•
Rename the Bricks
the hardware
About Component Placement for Four Slammers and 64 Bricks
Pillar Axiom 600 systems with four Slammers support up to 64 Serial ATA
(SATA) Bricks, or a combination of up to 32 FC Bricks and 32 SATA Bricks in a
mixed system.
Note: This topic applies only to Pillar Axiom 600 systems.
Install the components in the rack as shown in the following figure, which
illustrates how the Pillar Axiom 600 system components are mapped into a fully
loaded 42U racks for the maximum configuration of:
●1 Pilot
●4 Slammers
●64 Bricks
About Component Placement47
Page 48
Chapter 2
Set Up the Rack
Figure 16 Fully loaded 42U racks for four Slammers and 64 Bricks
Important! In the above configuration, make sure Fiber Channel
(FC) and serial
ATA (SATA) Bricks are loaded in the cabinet so that the power load on the PDU
is correct. The illustration assumes a 230 V power supply.
Note: The physical Brick names used above are for illustration and indicate the
physical location of the Brick in the rack. The actual names or logical names, as
seen in the Pillar Axiom Storage Services Manager, can be different. The logical
location or numbering of each Brick is determined during the installation and
follows the scheme Brick001, Brick002, Brick003, and so on.
Note: The Brick names used above are for illustration; actual names, as seen in
the Pillar Axiom Storage Services Manager, may be different.
Note: Any components that are not installed must be replaced with filler panels.
Also, 2U of space is reserved above the PDUs for cable routing. The number and
type of PDUs depends on the power supply. If more PDUs are needed, then
everything has to move up to make room, keeping the 2U of reserved space, and
moving any Bricks displaced at the top to the next rack.
When using SATA Bricks, the preceding configuration can use as few as two
Slammers. Replace the empty spaces for the missing Slammers with filler panels.
When you install the Bricks, work from the bottom of the rack toward the top. If
you have additional racks of Bricks, install those Bricks from the top down in the
additional racks.
About Component Placement48
Page 49
Chapter 2
Set Up the Rack
Note: In a system that is configured for the maximum number of Bricks, connect
the additional racks to the first rack before you install and cable
components.
Related concepts
•
About Component Placement for Two or Three Slammers and FC Bricks
Related references
•
Cabling Practices for the Pillar Axiom 600 System
Related tasks
•
Rename the Bricks
Pilot Rail Kit Parts
Verify that the rail kit contains all the parts listed in the table.
Before installing a pair of Pilot rack rails, make sure you have:
the hardware
●One Pilot rail kit with rails and scopes pre-attached
●#20 Torx wrench
●Socket wrench
Pilot rails are 2U rack rail assemblies that contain the following parts:
Table 9 Pilot rail kit parts
ComponentDrawing (not to scale)Quantity
Pilot rail kits
1475-00036-xx
1450-00037-xx
Pilot rail scopes
2525-00093-xx
2525-00095-xx
One left-right pair
One left-right pair
About Component Placement49
Page 50
Chapter 2
Set Up the Rack
Table 9 Pilot rail kit parts (continued)
ComponentDrawing (not to scale)Quantity
10-32 Hex nuts for
attaching scopes to rails
2500-01051-xx
Rack mount spacers
2500-01065-xx
Rack mount nut bar
2526-00106-xx
10-32 x 1/2 inch Torx
head (#20) screws
2500-01071-xx
Eight
Four
Two
12
Install a Pair of Pilot Mounting Rails
1Hang the scope hook
shown in the following figure:
About Component Placement50
in the appropriate hole at the back of the rack, as
Page 51
Chapter 2
Set Up the Rack
Figure 17 Scope hook attachment
Legend
1 Vertical rail at back of rack
2 Rack unit (RU) 32
3 Scope hook
4 Bottom holes for each unit
5 RU 31
In the preceding figure, two labeled rack units, 31 and 32, are shown at the
back of the rack.
The bottom of unit 31 is just out of sight below its bottom hole.
●
●
The scope hook is one-and-a-half units above the bottom of the rail.
●When you place the hook in the middle of unit 32, the bottom of the
rail lines up with the bottom of unit 31.
●A 2U Pilot rail would fill units 31-32 in the preceding illustration.
2At the front of the rack, slide the rail scopes until the rail reaches the holes
at the front.
The rail flange goes in front of the rack mount holes, and the four-hole
spacer bar goes behind, as shown in the figure in the next step.
About Component Placement51
Page 52
Chapter 2
Set Up the Rack
3While keeping the rail horizontal, fit the four-hole spacer bar into the four
square rack holes that span the boundary between
rail is to occupy.
The following figure shows positioning a spacer for units 35 and 36.
Figure 18 Positioning spacer bar
the two units that this
Legend
1 Rack unit boundary
About Component Placement52
Page 53
Chapter 2
Set Up the Rack
Figure 19 Pilot rail front attachment
Legend
1 Back
2 Four-hole spacer bars
3 Front
4 Slider lock nuts
4Use two 10-32 Torx Washer Head screws to secure the rail through the
rack into the two center holes in the spacer bar.
top and bottom holes are use to secure the Pilot control units to the rack.
The
5At the back of the frame, place a spacer on a 10-32 Torx Washer Head
screw and screw it through the hole in the frame and into the rail under the
scope hook.
Install the second screw the same way. Ensure that the spacer is centered
inside the rack's square mounting hole.
6Repeat Steps 1 through 5 for the other side rail.
7Tighten the four slider lock nuts that attach each rail scope to the rail.
Slammer Rail Kit Parts
Verify that the rail kit contains all the parts listed in the table below.
About Component Placement53
Page 54
Chapter 2
Set Up the Rack
To install a pair of Slammer rails, you need:
●One Slammer rack rail kit with rails
and scopes pre-attached
●#20 Torx wrench
●Socket wrench
Slammer rails are 4U rack rail assemblies that contain the following parts:
Table 10 Slammer rail kit parts
ComponentDrawing (not to scale)Quantity
Slammer rails
1475-00024-xx
1475-00025-xx
Slammer rail scopes
2525-00093-xx
1 left-right
pair
1 left-right
pair
2525-00095-xx
10-32 Hex nuts for
attaching scopes to
rails
2500-01051-xx
Rack mount spacers
2500-01065-xx
10-32 x 1/2 inch Torx
Washer Head screws
2500-01071-xx
8
8
10
About Component Placement54
Page 55
Chapter 2
Set Up the Rack
Install a Pair of Slammer Mounting Rails
1Hang the scope hook
in the appropriate hole at the back of the rack, as
shown below. These rail scopes are always used for components that take
up at least two rack units.
Figure 20 Scope hook attachment
Legend
1 Rack unit 32
2 Rack unit 31
3 Vertical rail at back of rack
4 Scope hook
5 Bottom holes for each unit
In the preceding figure, two labeled rack units, 31 and 32, are shown at the
back of the rack.
●The bottom of unit 31 is just out of sight below its bottom hole.
●
The scope hook is one-and-a-half units above the bottom of the rail.
About Component Placement55
Page 56
Chapter 2
Set Up the Rack
2At the front of the rack, slide the rail scopes until the rail reaches the holes
at the front.
3While keeping the rail horizontal, place a spacer on a #20 Torx screw and
screw it through the bottom hole in the front frame and into the rail.
See the next figure.
Repeat this step for the hole above it (but not the top hole, which is for
securing the Slammer).
4Secure the screws at the back, under the scope hook.
5Repeat Steps 1 through 4 for the other side rail.
Figure 21 Slammer rails installed in rack
●When you place the hook in the middle of unit 32, the bottom of the
rail lines up with the bottom of unit 31.
●
A 4 U Slammer rail would fill units 31-34 in the above illustration.
Legend
1 Back
2 Front
3 Slider lock nuts
6Tighten the four slider lock nuts that attach each rail scope to the rail.
About Component Placement56
Page 57
Chapter 2
Set Up the Rack
Brick Rail Kit Parts
Verify that the rail kit contains all the parts listed in the table below.
To install a pair of 2U rack rails, you
need:
●One Brick rail kit with rails and scopes pre-attached
●#20 Torx wrench
●Socket wrench
Brick rails are 2U rack rail assemblies that contain the following parts:
Table 11 Brick rail kit parts
ComponentDrawing (not to scale)Quantity
Brick rails
1450-00022-xx
1450-00023-xx
Brick rail scopes
2525-00093-xx
1 left-right pair
1 left-right pair
2525-00095-xx
10-32 Hex nuts for
attaching scopes to rails
2500-01051-xx
Rack mount spacers
2500-01065-xx
About Component Placement57
8
4
Page 58
Chapter 2
Set Up the Rack
Table 11 Brick rail kit parts (continued)
ComponentDrawing (not to scale)Quantity
10-32 x 1/2 inch Torx
head (#20) screws
2500-01071-xx
Related tasks
•
Install a Pair of Brick Mounting Rails
Install a Pair of Brick Mounting Rails
1Hang the scope hook in the appropriate hole at the back of the rack, as
shown below. These rail scopes are always used for components that take
up at least two rack units.
10
About Component Placement58
Page 59
Chapter 2
Set Up the Rack
Figure 22 Scope hook attachment
Legend
1 Vertical rail at back of rack
2 Rack unit 32
3 Scope hook
4 Bottom holes for each unit
5 Rack unit 31
In the preceding figure, two labeled rack units, 31 and 32, are shown at the
back of the rack.
The bottom of unit 31 is just out of sight below its bottom hole.
●
●
The scope hook is one-and-a-half units above the bottom of the rail.
●When you place the hook in the middle of unit 32, the bottom of the
rail lines up with the bottom of unit 31.
●A 2U Brick rail would fill units 31-32 in the above illustration.
2At the front of the rack, slide the rail scopes until the rail reaches the holes
at the front.
3While keeping the rail horizontal, place a spacer on a #20 Torx screw and
screw the Torx screw through the center hole in the front frame and into the
rail.
About Component Placement59
Page 60
Chapter 2
Set Up the Rack
See the next figure.
Repeat this step for the other center screw in the front and for the screws at
the back, under the scope hook. The square hole in the front is at the top on
the left side and at the bottom on the right side. These square
securing the Brick. Use only the round holes to secure the rails into the rack.
Figure 23 2U rack rails installed in rack
holes are for
Legend
1 Back
2 Front
3 Slider lock nuts
4Repeat Steps 1 through 3 for the other side rail.
5Tighten the four slider lock
nuts that attach each rail scope to the rail.
Related references
•
Brick Rail Kit Parts
Related tasks
•
Install a Brick Storage Enclosure
About Component Placement60
Page 61
Chapter 3
Install Components
CHAPTER
3
Install Components
About Power Distribution Unit Installation
Mount power distribution units (PDUs) in the bottom units of the rack. The onephase PDUs mount on the rear rack rails while the 2U three-phase PDUs mount
on the front rails. The default configuration places up to four 1U 220V, 30A PDUs
at the bottom of the rack.
Prerequisites:
●A 1U or 2U PDU
●Torx T20 screw driver
●Four snap-in cage nuts (for square mounting holes) or four clip-on cage
nuts (for round mounting holes)
●Four 10-32 x 1/2" Torx Washer Head screws
Important! We strongly recommend that you use Pillar Axiom 600 PDUs. If you
install non-Pillar PDUs, they must meet the PDU specification described in the
Pillar Axiom Site Preparation Survey
Important! If the external power supplied to the Pillar Axiom 600 is 208V instead
of 230V, the number of components that can be powered by a single PDU is
reduced. Because of the lower voltage of 208V circuits, use of this connection
type lowers the number of Bricks that can be placed in a rack. Pillar recommends
using 230V circuits instead.
Tip: Use a voltmeter to verify the voltage of the available power. The Pillar
Axiom 600 PDUs support multiple ranges of voltage and the current rating on the
PDU breakers varies with the external available power. The external available
power determines the number of Pillar Axiom 600 components that can be
connected to the PDU port groups or circuit breakers (CB). If the voltage of the
input power into the PDU is lower than the nominal rating of the PDU, the current
rating on the breakers is decreased to compensate the lower voltage of the
available power. For example, a 15A breaker on a 230V PDU is rated at 12A if
the voltage of the input available power into the PDU is 208V.
and in the hardware specifications appendix.
About Power Distribution Unit Installation61
Page 62
Chapter 3
Install Components
Related concepts
•
About Pillar Axiom 600 Hardware Specifications
Install a 1U PDU
1Choose one of the following options:
●For square mounting holes, snap a 10-32 snap-in cage nut into the
bottom and 3rd hole of each vertical rail.
Figure 24 Snap-in cage nut
●For round mounting holes, clip one 10-32 clip-on cage nut into the
bottom and 3rd holes of each channel in
the pair. (Pillar Axiom 600
systems are not shipped with clip-on cage nuts.)
2Insert the PDU into the rack, as shown below.
There are no rails for a PDU.
About Power Distribution Unit Installation62
Page 63
Chapter 3
Install Components
Figure 25 Securing a 1U PDU in the bottom of a rack
Note: This image is for illustration purposes only. Your hardware
component might look
different.
3Align the ears of the PDU to the four cage nuts.
4Insert a 10-32 x 1/2 inch screw through the top and bottom holes in the right
and left ears of the PDU and into the cage nuts.
Figure 26 An installed PDU at the bottom of the rack
Legend
Important! Do not plug the PDU into a power
complete and ready
1 10-32 x 1/2 inch screws
2 Rack unit (RU) marker
supply until the rack is
for startup.
5Secure both screws tightly.
About Power Distribution Unit Installation63
Page 64
Chapter 3
Install Components
6Repeat this procedure to install any other 1U PDUs.
Install a 2U PDU
1Depending
on the type of rack mounting holes, choose one of:
●For square mounting holes, snap a 10-32 snap-in cage nut into the
bottom and seventh hole of each vertical rail.
Figure 27 Snap-in cage nut
●For round mounting holes, clip one 10-32 clip-on cage nut into the
bottom and seventh holes of each channel in
the pair. (Pillar
Axiom 600 systems are not shipped with clip-on cage nuts.)
2Align the slots in the PDU ears to the four cage nuts.
Figure 28 2U PDU layout and ear locations
Legend
About Power Distribution Unit Installation64
1 Front of PDU2 PDU ears on left side
3 PDU ears on right side
Page 65
Chapter 3
Install Components
Note: This image is for illustration purposes only. Your hardware
component might look
3Insert a 10-32 x 1/2 inch screw through the bottom hole in the right and left
ears of the PDU and into the cage nuts. Secure both screws tightly.
4Repeat Step 3 for the top holes in both ears.
Important! Until you are instructed to do so, do not plug the PDU into an
inlet power supply.
5Repeat this procedure to install any other 2U PDUs.
different.
About Power Distribution Unit Installation65
Page 66
Chapter 3
Install Components
Install a Pilot Management Controller
Installation of the Pilot control units at the bottom of the rack, just above the
power distribution
as possible.
Required tools:
●Torx T20 screw driver
●Antistatic wrist strap
units (PDUs), is efficient and makes future expansion as easy
Warning
Warning
1Put on an antistatic wrist strap, ground strap, or heel strap and attach the
grounding wire to ground.
2From the front of the rack, place the back side of the first Pilot CU on the
bottom mounting rails and slide the CU into place.
Important! When sliding a Pilot CU into the rack, keep the CU level to avoid
bending the rail supports.
3Insert the second Pilot CU above the first CU, as shown in the following figure:
Ensure that component distribution in the rack is balanced.
Follow the hardware placement map to ensure
Uneven distribution can cause hazardous instability. The
rack must have stabilization plates or anti-tip brackets
installed so the rack does not tip when you install a
component.
Mounting rail assemblies must be used to support and
secure a Pilot in the rack. The mounting ears of a Pilot
control unit (CU) by themselves
of the Pilot.
cannnot support the weight
this balance.
Install a Pilot Management Controller66
Page 67
Chapter 3
Install Components
Figure 29 Insertion of the upper Pilot CU
Note: This image is for illustration purposes only. Your hardware
component might look
different.
4Use a 10-32 Torx screw through the hole in each Pilot CU ear and tighten
the screw securely using a #20 Torx wrench.
Important! Do not plug the Pilot chassis into a PDU until instructed to do so.
Warning
Never block the inlet and outlet holes in the chassis
components. Sufficient air circulation is required for
the components to operate properly
and to avoid a fire
hazard. Do not push objects of any kind into the
ventilation holes. Such action could result in fire or
electrical shock. Keep all liquids away from hardware
components.
Install a Pilot Management Controller67
Page 68
Chapter 3
Install Components
Pilot Versions
There are several versions of Pilot control units (CUs) available.
Figure 34 illustrate the different versions of the Pilot:
Figure 30 Pilot CU (1450–00259–XX) (Back view)
Legend
1 Serial port
2 USB flash memory drive inserted into the lower USB port
3 Ethernet ports
Figure 30 to
4 Management port
Pilot Versions68
Page 69
Chapter 3
Install Components
Figure 31 Pilot CU (1450–00179–XX) (Back view)
Legend
Figure 32 Pilot CU (1450–00164–XX) Intel
Legend
1 Pilot power switch4 Management port
2 Ethernet port (ETH1)5 USB port
3 Ethernet port (ETH0)
1 Back view of a Pilot CU4 USB port
2 Front view of a Pilot CU5 Ethernet port (ETH0)
3 Ethernet port (ETH1)6 Management port
Pilot Versions69
Page 70
Chapter 3
Install Components
Figure 33 Pilot CU (1450–00170–XX) MSI, non-RoHS
Legend
Figure 34 Pilot CU (1450-00268-XX and 1030-00005-XX)
1 Back view of a Pilot CU4 Ethernet port (ETH1)
2 USB port5 Management port
3 Ethernet port (ETH0)6 Front view of a Pilot CU
Legend
Pilot Versions70
1 Back view of a Pilot CU5 Ethernet port (ETH1)
2 Serial port6 SVC Ethernet port for direct connection to the Pilot
3 USB port7 Management port
4 Ethernet port (ETH0)8 Front view of a Pilot CU
Page 71
Chapter 3
Install Components
Install a Slammer Storage Controller
Install the Slammers above the Pilot near the bottom of the rack.
Required
●Torx T20 screw driver
●Antistatic wrist strap
1Put on an antistatic wrist strap, ground strap, or heel strap and attach the
2From the front side of the rack, set the back of the Slammer onto the
tools:
Caution
Warning
grounding wire to ground.
mounting rails and slide the Slammer into place.
A Slammer weighs 94 pounds (42.6 kilograms). For safe
handling, use two people to lift it.
Ensure that component distribution in the rack is balanced.
Follow the hardware placement map to ensure
Uneven distribution can cause hazardous instability. The
rack must have stabilization plates or anti-tip brackets
installed so the rack does not tip when you install a
component.
this balance.
Leave about one inch (2.5 centimeters) of clearance between the Slammer
ears and the vertical channels.
Important! When sliding the Slammer into the rack, keep the Slammer level
to avoid bending the rail supports, which would cause difficulty when
inserting a component below.
Install a Slammer Storage Controller71
Page 72
Chapter 3
Install Components
Figure 35 Insertion of a Slammer
3Put a spacer on a 10-32 x 1/2 inch Torx screw, then insert the screw
through the hole in the ear on the left side of the Slammer.
4
Push the Slammer so that its ears and the spacers rest against the vertical
channels, then start the Torx screws with your fingers.
5Use a #20 Torx wrench to secure the screws to the rack.
Note: This step only keeps the Slammer in place; the screws provide no
other support.
6Repeat Steps 3 through 5 for the right side of the Slammer.
7(Pillar Axiom 600 systems only) If you have a two, three, or four Slammer
system, install the remaining Slammers now.
Important! Do not apply power to the Slammers until instructed to do so.
Related references
•
Cable Length Limits for SAN Fibre Channel Connections
Install a Slammer Storage Controller72
Page 73
Chapter 3
Install Components
Install the Slammer Batteries
Slammer batteries are shipped separately.
Ensure the
1
The
Install Before Date
battery is past the
Customer Support Center.
2Remove the front cover (bezel).
If the bezel is not attached, skip to Step 5.
3Press the Slammer ejector tabs on the bezel to unlock them.
4Lift both ejector tabs to disengage the bezel from the rack.
Figure 36 Slammer bezel removal
Install Before Date
Install Before Date
on the Slammer batteries have not expired.
is printed on the label on top of the battery. If a
, contact the Pillar World Wide
Legend
1 Ejector tab
2 Button
3 Disengage the bezel from the rack
5Insert the batteries into the Slammer, but do not secure them until you
complete the installation.
Tip: When you secure them, they start to discharge as they preserve data
in memory. Because there is no
data to preserve, you should wait until you
are ready to power on the system before securing the batteries.
Install the Slammer Batteries73
Page 74
Chapter 3
Install Components
Figure 37 Slammer battery insertion
Note: This image is for illustration purposes only. Your hardware
component might look
different.
Install the Slammer Batteries74
Page 75
Chapter 3
Install Components
Install a Brick Storage Enclosure
When you install the Bricks, work from the bottom of the rack toward the top. If
you have additional racks of Bricks, install those Bricks from the top down in the
additional
Required tool: Torx T20 screw driver, tie wraps, and velcro ties.
Note: Brick storage enclosures are packaged and shipped separately from the
Pillar Axiom 600 system.
1Put on an antistatic wrist strap, ground strap, or heel strap and attach the
2At the front of the rack, insert the Brick onto the mounting rack rails and
racks.
grounding wire to ground.
slide into place.
Caution
A Brick weighs up to 65 pounds (29.5 kilograms). For
safe handling, use two people to lift it.
Important!
When you slide the component into the rack, keep the Brick
level to avoid bending the rail supports, which would cause difficulty when
inserting a component below.
Figure 38 Insertion of a Brick
Install a Brick Storage Enclosure75
Page 76
Chapter 3
Install Components
3Use two 10-32 Torx screws (one on each side) and a Torx T20 driver to
secure the Brick ears to the rack.
Important! Use care as you install the screws on the right to avoid
damaging
bezel.
Figure 39 Brick ears
the printed circuit, which provides power and signals to the Brick
Legend
1 Printed circuit assembly
2 10-32 Torx screw
4Inspect the drives to ensure each drive is flush and securely seated.
Securely seat the drives by:
●Fully opening the cam latch on the drive carrier.
●Pressing the drive carrier into the Brick chassis until it stops.
●Closing the cam latch until it snaps shut to engage the drive with the
Brick midplane.
Figure 40 Brick front with the bezel removed
Note: This image is for illustration purposes only. Your hardware
component might look different.
5Verify that the digit setting on the Brick Enclosure Services (ES) module
used to set the identity of the Brick is set correctly before powering on the
Brick.
Install a Brick Storage Enclosure76
Page 77
Chapter 3
Install Components
6If you have multiple Bricks, install them all now, even those that require
additional racks.
7
Verify that the digit setting of the Brick is in the proper position. The digit
setting must be set to 0 for all Serial ATA (SATA), solid state drive (SSD),
and Fiber Channel RAID (FCR) Bricks and to 1 for all Fiber Channel
Expansion (FCE) Bricks.
8Ensure that both the power switches that are on the power distribution units
(PDUs) are in the OFF position.
9When connecting the color coded Wye power cables, ensure that each
Brick gets a power feed from two separate PDUs.
10Connect the FC cables as indicated in the wiring diagrams included in the
Pillar Axiom 600 SSF Cabling Reference
and power on the Bricks.
Related concepts
•
About Power Cabling
Related tasks
•
Set the Identity of Bricks
•
Power On the System
•
Connect Power Cables
•
Install a Pair of Brick Mounting Rails
•
Add a New Brick Storage Enclosure
Install a Brick Storage Enclosure77
Page 78
Chapter 3
Install Components
Set the Identity of Bricks
1Locate the digital
push button at the top of the face of the Enclosure
Services (ES) module.
This figure identifies the location of the digital push button, which is used to
set the Brick ID.
Figure 41 ES module location
Legend
Set the Identity of Bricks78
1 Pull tab5 Dial settings
2 Screw6 Digital push button
3 LEDs7 ES module
4 Brick back
Page 79
Chapter 3
Install Components
The digit setting of the Brick is visible in the center of the digital push button
and identifies the type of Brick.
2
Verify that the digit setting on the Brick Enclosure Services (ES) module is
set correctly for the Brick before powering on the Brick.
Important! The digit setting for all Bricks (SATA, SSD, and FC RAID) is preset to 0. The digit setting for the FC Expansion Brick is pre-set to 1.
However, the digit setting must always be verified during installation.
Otherwise, the Pillar Axiom 600 system cannot bring the Brick online.
3If the digit setting is not set correctly, push the button using a sharp object,
such as the end of a paper clip or a small screwdriver to set the Brick ID.
The top button ( - ) decrements the counter and the bottom button ( + )
increments the counter.
Important! Do not change the digit settings while the Brick is powered on.
Related tasks
•
Install a Brick Storage Enclosure
Set the Identity of Bricks79
Page 80
Chapter 3
Install Components
Replace a Brick Storage Enclosure
You can replace existing Bricks with new Bricks within
must migrate the volumes to the new Bricks because clones are not migrated
with the parent volumes when Bricks are replaced.
1Delete the clones of existing volumes in the Bricks that must be replaced.
2Create a minimum of one new Storage Domain.
3Add the new Bricks to the Pillar Axiom 600 system.
4Accept the newly added Bricks into the new Storage Domain.
5Verify that the capacity from the new Bricks has been added successfully in
the Pillar Axiom 600 system.
6If the Bricks that must be added are in the existing primary Storage Domain,
make sure you add a minimum of two Bricks of the same Storage Class to
a single new Storage Domain before you promote the new Storage Domain
to primary.
Important! Before making a Storage Domain primary or migrating data to a
new Storage Domain, add all the Bricks to the new Storage Domain. Failure
to do so may cause performance issues because the Pillar Axiom 600
system might not be able to stripe the data across the appropriate number
of Bricks for the Quality of Service (QoS) and Storage Class.
a storage domain. You
7Make the new Storage Domain primary.
When the new Storage Domain is made primary, the persistence VLUN is
migrated from the old primary Storage Domain to the new primary Storage
Domain. The migration uses Bricks in the following order: serial ATA
(SATA), Fiber channel (FC), and solid state drive (SSD).
8Migrate all the volumes on the old Bricks to the desired Storage Class in the
new Storage Domain.
Tip: For minimum impact to system performance, migrate one volume at a
time.
9Use the storage allocation CLI axiomcli storage_allocation
command to ensure that all volumes have been migrated from the old
Bricks that must be replaced.
Replace a Brick Storage Enclosure80
Page 81
Chapter 3
Install Components
Important! If you are replacing Bricks in the default or primary Storage
Domain, use the storage
command to ensure that the persistence volume is not on the Bricks that
must be powered down. The persistence volume must be on the Bricks in
the new primary Storage Domain.
A system alert is posted to confirm the removal of the Brick from the Pillar
Axiom 600 system configuration.
10After verifying that all volumes, including the system configuration,
persistence, and volumes have been migrated, power off all the Bricks in
the old Storage Domain.
11Verify all storage and make sure that all the volumes are online before
disconnecting and removing the old Bricks from the system configuration.
Note: The Pillar Axiom 600 system does not allow Bricks to be removed if
any resources are allocated on that Brick. If there are problems while
removing the Bricks, contact the Pillar World Wide Customer Support
Center for assistance.
allocation CLI axiomcli storage_allocation
12Select and remove the old Storage Domain.
Note: The Pillar Axiom 600 system does not allow Storage Domains to be
removed if any resources are allocated on that Storage Domain. If there are
problems while removing the old Storage Domain, contact the Pillar World
Wide Customer Support Center for assistance.
Related concepts
About Adding Bricks to a Storage Domain
•
Related tasks
Move a Volume to Another Storage Domain
•
•
Set a Storage Domain as the Primary
•
Accept a Brick
•
Create a Storage Domain
•
Add a New Brick Storage Enclosure
•
Verify a Newly Added Brick
•
Delete All Clone LUNs
Delete All Clone LUNs
When a collection of Clone LUNs that are derived from a common source LUN
are no longer needed, you can delete the entire collection.
When you delete a collection of clones that have a common parent LUN, the
system determines the most efficient and quickest order of deletion.
Replace a Brick Storage Enclosure81
Page 82
Chapter 3
Install Components
1From the
2Select the parent LUN of all of the Clone LUNs that you want to delete.
3Choose
4When prompted to confirm the deletion, click OK.
Accept a Brick
When you add a Brick storage enclosure to an existing Pillar Axiom system, your
acceptance of the Brick allows the system to add the storage provided by the
Brick to the existing storage pool.
Prerequisites:
Configure
Actions
tab, click
>
Delete Clones
Storage
.
>
SAN
>
LUNs
.
Result:
The system displays the Delete Clones dialog with a list of all the clones
that will be deleted.
●The Pillar Axiom system is in a Normal state.
●The Brick has been cabled correctly according to the wiring diagrams in the
Pillar Axiom 600 SSF Cabling Reference
.
●Both RAID controllers of the Brick have been powered on.
Note: After you power on a Brick, the system updates the Brick firmware.
This update can take up to 15 minutes.
●A system alert exists that states that a Brick has been added to the system.
Typically, you respond to the system alert by either accepting or rejecting the
newly added Brick. If you delete the system alert and, as a consequence, do not
accept the Brick, you can perform the
Accept Brick
action at a later time. This
action mirrors the functionality of the Accept Brick alert.
The Brick to be accepted can be a new one from Pillar Manufacturing or an
existing one from a different Pillar Axiom system. A Brick from a different system
is referred to as a
1From the
foreign
Monitor
Brick.
tab, click
Hardware
>
Bricks
.
2Choose
3(Optional) Select a domain from
Replace a Brick Storage Enclosure82
Actions
>
Accept Brick
.
Storage Domain
drop-down list.
Page 83
Chapter 3
Install Components
This list is active only when additional Storage Domains exist.
4(Optional) Replace
the default logical name for this newly added Brick with
a name of your own choosing.
5To accept the Brick into the system, click OK.
Result:
While the Brick is being integrated into the system, the status of the Brick
changes from red to yellow to green. Also, the overall status of a foreign
Brick is displayed as Foreign.
When the system completes the integration process, the system performs
the following additional actions:
●Generates a “Brick Accepted” event.
●Changes the health status of the Brick from Warning to Normal.
●Removes all system alerts that are related to the Brick addition.
Note: If any system alerts remain, contact the Pillar World Wide
Customer Support Center.
The Brick is now fully integrated into the Pillar Axiom system.
You can now begin utilizing the additional capacity provided by the newly added
Brick. The
Monitor
>
Hardware
>
Bricks
overview screen shows this capacity and the
Storage Domain to which the Brick is assigned.
Create a Storage Domain
Storage Domains allow you to assign logical volumes to a specific collection of
Bricks. Such assignments can be made to reduce contention among volumes, to
implement different levels of security for those volumes, or both. Storage
Domains allow administrators, for example, to partition storage for specific users
or departments in a public or private cloud storage environment.
When you create a Storage Domain for regular use, we recommend that you
assign the following minimum number of Bricks to that domain:
●Two serial ATA (SATA) or solid state device (SSD) Bricks
●Three Fibre Channel (FC) Bricks
When you need to replace one or more Bricks in an existing domain, you
typically would create a new Storage Domain, assign Bricks to it, and then move
the logical volumes from the existing domain to the newly created domain. In this
Replace a Brick Storage Enclosure83
Page 84
Chapter 3
Install Components
scenario, you can create the new domain without any Bricks with the purpose of
assigning the Bricks later.
In the above scenario, if you are replacing
Domain, for the new domain, we recommend that you have
Bricks in the current primary Storage
at least
two Bricks of
the same Storage Class, in the following order of preference:
●First, SATA.
●If not SATA, then FC.
●If not FC, then SSD.
Note: We recommend a minimum of two Bricks of the same Storage Class to
ensure that the Persistence VLUN, which contains the system configuration
information, retains double redundancy.
A non-primary Storage Domain can contain only one Brick of any Storage Class.
Important! If you place only a single Brick of the lowest Storage Class in the new
non-primary domain and the domain is promoted to primary, the redundancy of
the Persistence VLUN reverts to single redundancy.
1From the
2Choose
Configure
Actions
>
tab, click
Manage Storage Domains
Groups
>
Storage Domains
.
.
3On the Storage Domains tab, click
Create
Result:
A new row in the Storage Domains table appears.
4In the blank Storage Domain field, enter the name of the new domain.
5Click
OK
.
The new Storage Domain now appears in the list of domains.
After you create the Storage Domain, assign one or more Bricks to the domain
so you can locate logical volumes in the domain. The number of Bricks that you
add to a domain directly affects the performance of that domain.
About Adding Bricks to a Storage Domain
The impact of adding a Brick to a Pillar Axiom system depends on whether
administrator defined Storage Domains exist.
.
Replace a Brick Storage Enclosure84
Page 85
Chapter 3
Install Components
Table 12 Effect of Storage Domains on Brick additions
Do
administrator
defined
Storage
Domains exist?
NoThe system checks the system serial number (SSN) of the Brick
Impact
to verify whether the SSN is applicable to this Pillar Axiom
system. How the system responds to this check depends
applicability of the SSN:
●Applicable. The Brick is a new one from the factory. The
system automatically adds the new Brick to the default
Storage Domain.
●Not applicable. The Brick is from some other Pillar Axiom
system. The system prompts you to accept the
Brick.
on the
foreign
YesThe system prompts you to perform one of the following actions:
●Add the Brick to one of the listed Storage Domains.
●Create a new Storage Domain with this Brick as the initial
member.
Note: Under certain circumstances, the system might
automatically add this Brick to the primary domain, which can
happen if the system has been unable to migrate the system
data into the primary Storage Domain.
Based on the current Quality of Service (QoS) settings of the
various logical volumes and their associated clone repositories,
the system might notify you of any recommended data migrations.
For best performance, you should add Bricks to Storage Domains in quantities
that are sufficient to support the default number of RAID groups for each Storage
Class and QoS.
For information about how
Hardware Installation Guide
to add Bricks to a system, refer to the
for your system.
Pillar Axiom
Replace a Brick Storage Enclosure85
Page 86
Chapter 3
Install Components
Set a Storage Domain as the Primary
Circumstances can arise in which you might want
to transfer the Persistence
VLUN, which contains the system configuration data, from the current primary
Storage Domain to a different domain.
Prerequisites:
●A non-primary Storage Domain.
●The following lists the minimum recommended number of Bricks in the
order of preference:
○First, two serial ATA (SATA).
○Second, two Fibre Channel (FC).
○Third, two solid state device (SSD).
Note: If you have more than one Storage Class in the non-primary Storage
Domain, the Pillar Axiom storage system migrates to SATA, if that class is
available. If SATA is not available, the system migrates to FC, if that class
is available. If SATA and FC are not available, the system migrates to SSD.
When the non-primary Storage Domain becomes the primary domain, the
previous primary domain loses its primary status and the system migrates the
system data to the new primary domain. The administrator cannot cancel this
special data migration.
1From the
Configure
tab, click
Groups
>
Storage Domains
.
2Highlight the Storage Domain that you want to become the new primary
domain and choose
Actions
>
Set as Primary Storage Domain
.
3To set the non-primary Storage Domain as the new primary domain, click
OK
.
Result:
The systems begins migrating all system configuration and persistence data
to the new primary domain.
Important! After you click
Replace a Brick Storage Enclosure86
OK
, you cannot cancel this data migration.
Page 87
Chapter 3
Install Components
Important! After promoting a non-primary Storage Domain to primary, you
verify that the volume named PERSISTENCE has been moved to the Bricks in
the new primary domain. To verify proper migration, use the axiomcli
storage_allocation command provided by the Pillar Axiom CLI application.
When executing this command, include the -brick and -list options. For
more information, refer to the
Pillar Axiom CLI Reference Guide
Move a Volume to Another Storage Domain
Move a logical volume to another Storage Domain when you want to remove the
Bricks on which the volume resides or reassign those Bricks to another Storage
Domain.
The Storage Domain to which you want to reassign the logical volume must
contain sufficient free capacity of the appropriate Storage Class to hold the
logical volume.
Note: Assigning logical volumes and Bricks to a Pillar Axiom Storage Domain
must be performed as separate actions.
should
.
Tip: To avoid performance issues caused by Brick striping, move the Bricks to
the Storage Domain before you move any volumes.
1From the
2Choose
Configure
Actions
>
tab, click
Manage Storage Domains
Groups
>
Storage Domains
.
.
3On the Volumes tab, click the Storage Domain for the logical volume that
you want to reassign.
Result:
A drop-down list appears in the Storage Domain column.
4In the Storage Domain drop-down list, choose the Storage Domain to which
you want to reassign the logical volume.
5Click
OK
.
Result:
One of the following will occur:
●If the operation is successful, the system begins a background task to
migrate the volume to the new Storage Domain. Also, the system
releases and reconditions the storage in the previous domain.
●If the operation is unsuccessful, the system does not migrate the
volume but instead displays an appropriate error dialog:
Replace a Brick Storage Enclosure87
Page 88
Chapter 3
Install Components
○The target domain does not contain any Bricks in the appropriate
Storage Class. To resolve, add to the target domain one or more
Bricks of the appropriate Storage
Class.
○The target domain has insufficient free capacity in the
corresponding Storage Class. To resolve, remove unneeded
volumes that consume capacity on the Bricks of that Storage
Class.
Replace a Brick Storage Enclosure88
Page 89
Chapter 4
Connect Data Cables
CHAPTER
4
Connect Data Cables
About Cabling a Pillar Axiom 600 System
The Pillar Axiom 600 system is a scalable storage system that consists of a Pilot
management controller, at least one Slammer storage controller, and some
number of Brick storage enclosures depending upon your system model.
Cabling the Pillar Axiom 600 systems consists of two parts:
●Front-end cabling, which involves connecting the Slammer to the
customer's data network, and connecting the Pilot to the customer's
management network. The Pilot connection uses Ethernet. The Slammer
cable connections to the data network uses Fiber Channel (FC) or Ethernet,
depending on the Slammer.
●Back-end cabling, which involves cabling the Storage System Fabric (SSF),
sometimes referred to as the private interconnect, or simply PI, and the
private management interface (PMI).
Pillar Axiom 600 systems transmit data among its hardware components (Bricks,
Slammers, and the Pilot) through the SSF and PMI cabling.
The SSF cables provide the inter and intra-cabling connections between the
Bricks and the Slammers to support all data traffic, the cross connections among
the Slammer control units (CUs), and the cross connections among the Brick CUs.
The fast Ethernet network between the Pilot and the Slammers in a Pillar
Axiom 600 system is called the PMI. The PMI also includes the cross
connections between the Slammer CUs as well as the cross connections
between the Pilot CUs. These cross connections between the Pilot CUs permit
each CU to monitor the heartbeat of the other CU. The heartbeat connection
allows the passive Pilot CU to induce a failover, if the active Pilot CU fails.
The Pilot has no physical connection to the user data and, therefore, no cable
connection exists between the Pilot and the Bricks.
Bricks are connected together in Brick strings. The Brick at the head of the string
connects to the Slammer. Each of the other Bricks in the string connect to the
previous Brick in the string. A Brick that is higher in a string is one that is closer
to the Slammer or head of the string. A Brick that is lower in a string is one that is
further from the Slammer or the head of the string.
About Cabling a Pillar Axiom 600 System89
Page 90
Chapter 4
Connect Data Cables
Figure 42 provides a symbolic illustration of the Brick connections
within a Pillar Axiom 600 system.
Figure 42 Brick connections in strings
in a string
Legend
1 Brick connections to Slammer or to Bricks higher in the string
2 Brick connections to other Bricks lower in the string
Figure 43 provides a symbolic illustration of the back-end
6 Brick strings, in which Bricks are connected to each other and the Brick at the
head of the string is connected to the Slammer
About Cabling a Pillar Axiom 600 System91
Page 92
Chapter 4
Connect Data Cables
Cable Handling Tips
High speed data optic cables are delicate
plug ends and connectors are also sensitive to dirt and contaminants. Follow
these tips when handling cables.
●Do not bend the cables beyond its minimum bend radius (MBR). MBR is the
tightest bend that the cable can safely tolerate during or after installation.
The MBR for all data cables is two inches (5.1 cm).
●If you do not know the MBR, do not bend the cable to a radius of less than
two inches (5.1 cm). Also, the permanent bend radius of the cable is usually
larger than the temporary bend radius.
●Do not pull any cable or plug with a force exceeding five inches (12.7 cm.).
●Do not use force or rock the connector from side to side or up and down to
remove the connector because this action can damage the socket.
●Do not pull the cables using a mechanical device. If you need to pull a
cable, pull by hand.
●Leave some slack in the cables to allow insertion and removal of connectors.
●String cables with service loops so that it is possible to remove FRUs
without removing the cables.
and can easily be damaged. The cable
●Use only soft velcro or equivalent ties for routing or grouping cables. Do not
use hard plastic ties or other hard cinching type of wraps. Using hard plastic
ties can cause performance degradation and cable damage.
●Ensure no damage occurs during cable routing by not leaving cables
exposed in high traffic areas.
●Do not set any hardware components or other objects on top of the cables.
●Do not let the cables get pinched by closed doors or door lock hardware.
●Do not twist the cables.
●Do not wrap the fiber optic cables around your hands, arms, or shoulders,
as this may result in causing sharp bends or a small coiling radius. This can
also impart a twist to the cable upon uncoiling.
●Do not install cables in such a way that they are supported by other cables
or any other SSF cables.
Cable Handling Tips92
Page 93
Chapter 4
Connect Data Cables
●Support Fiber Channel (FC) cables such that they are not supported by
their connectors.
●Do not plug the high-speed
serial data cables (HSSDC) into the small form
factor pluggable (SFP) ports. Do not plug the SFP cables or transceivers to
the HSSDC ports. Either of these actions may cause damage to the plug
and connector.
●Use both hands to disconnect the connector in a module overly populated
with cables and connectors. Do not disturb or deflect other plugs or cables
during the removal operation.
Caution
To disconnect the cables from the HSSDC2 connectors,
carefully hold the cable connector and, while
pushing the
connector gently into the socket, press the latch on the top
of the connector to unlatch it. Merely grasping the latch or
jerking and pulling at the connector will not fully disengage
the connector but will damage the connector.
Caution
To disconnect the cables from the SFP connectors, carefully
grasp the cable connector and, while pushing
the connector
gently into the socket, press the latch on the bottom of the
connector to unlatch it. Then, gently pull the connector
straight out to release the connector with the cable
Important! SFP sockets have the latch on the top and the bottom in the private
interconnect module (PIM) and at the bottom on the Brick. Be careful when
connecting or disconnecting the SFP connectors.
Cable Handling Tips93
Page 94
Chapter 4
Connect Data Cables
Clean Fiber Optic Cables
Follow these tips to clean fiber optic cables.
Keep the end caps of the plugs installed whenever the plug is not installed.
●
●Have a fiber optic cable cleaning kit available while handling fiber optic
cables. A fiber optic cable cleaning kit includes the following items:
○Lint-free wipes
○Isopropyl alcohol (IPA)
○Special fiber optic cleaning swabs
○Canned pressurized air
Tip: Pre-moistened fiber optic wipes may be substituted for the wipes and IPA.
1To clean a fiber optic plug, blow away any dust particles from the connector
surface (particularly the sides and end face of the connector) using canned
pressurized air. Hold the nozzle of the optical duster approximately two
inches (5.08 centimeters) away from the connector and provide three to five
short blasts of air. Fold a wipe in half and place the wipe on a hard surface.
Moisten the wipe with isopropyl alcohol. Hold the face of the cable
connector to the wipe and slide it gently across the moistened area in one
sweeping move.
2To clean a fiber optic connector receptacle, blow away any dust particles
from the inside surface of the connector (particularly the inside walls of the
alignment sleeve) using canned pressurized air. Hold the nozzle of the
optical duster approximately two inches (5.08 centimeters) away from the
connector and provide three to five short blasts of air. Moisten the end of a
swab with isopropyl alcohol and insert the swab into the cable receptacle.
Move the swab in and out two or three times and then remove it and
discard. Dry the inside of the receptacle by holding canned pressurized air
approximately two inches (5.08 centimeters) away from the end and provide
three to five short blasts of air.
Important! Never reuse swabs.
Clean Fiber Optic Cables94
Page 95
Chapter 4
Connect Data Cables
Cabling Practices for the Pillar Axiom 600 System
Follow these fundamental rules and guidelines
for cabling Fiber Channel (FC),
Serial ATA (SATA), and Solid State Drive (SSD) Bricks in a Pillar Axiom 600
system.
All cabling rules and guidelines are categorized into three categories based on
the Pillar Axiom 600 system used. Cabling practices are also categorized based
on their impact on the system in case of non-compliance.
ALL: Rules that apply
to all Pillar Axiom 600
systems include:
Cabling requirements: Stringent requirements for the
system to work. Non-negotiable and integral to the
system design.
Cabling
rules: Stringent rules indicating functional
limitations of the system. If these rules are not followed,
the system is considered unsupported.
Cabling guidelines: Guidelines or best practices unless
circumstances prevent strict adherence to these
cabling guidelines.
NEW: Rules that apply
to new Pillar
Axiom 600 systems
and can be applied to
Manufacturing practices: Documented procedures
followed by Pillar operations for new systems that allow
each Pillar Axiom 600 system to be configured in a
consistent manner.
all Pillar Axiom 600
systems include:
FIELD: Rules that
apply to Pillar
Axiom 600 systems in
the field include:
Field practices: Practices that attempt to optimize high
availability, performance, troubleshooting and customer
requirements. However, field best practices cannot
override cabling rules that apply to all systems. Pertain
to Pillar Axiom 600 systems that exist in the field and
whose system configurations have evolved over time
due to numerous configuration modifications.
exceptions in Table 15: Cabling principles (Slammer
issues) that apply to the Slammer control unit (CU) connections in
single Slammer systems.
Pillar Axiom 600 systems that include any version 1 Bricks or any
version 1 PIMs must use only copper connections.
All new Pillar Axiom 600 systems (shipped after January 31,
2011) have version 2 Bricks and use optical connections.
Pillar Axiom 600 systems are cabled according to the cabling
diagrams in the
Use cables that are appropriate for the type of Brick and other
hardware components on the Pillar Axiom 600 system. For more
information, see the
Pillar Axiom systems that are upgraded in the field might have a
Brick string configuration that is different from a Pillar Axiom
system built in the factory, especially when systems are upgraded
non-disruptively. However, rules that apply to all systems always
apply to systems upgraded in the field.
Pillar Axiom 600 SSF Cabling Reference
Pillar Axiom 600 SSF Cabling Reference.
connection
.
ALL
NEW
ALL
ALL
FIELD
Table 14: Cabling principles (system size related issues) defines the influence of
system size or configuration
Table 14 Cabling principles (system size related issues)
on the cabling of the Pillar Axiom 600 system.
Cabling principleApplicability
Pillar Axiom 600 systems with one Slammer have a maximum of
four Brick strings.
Pillar Axiom 600 systems with two or three Slammers have a
maximum of eight Brick strings.
Pillar Axiom 600 systems with four Slammers have a maximum of
16 Brick strings, but may be configured with eight Brick strings.
However, it is recommended
Bricks are configured with 16 Brick strings.
that systems using more than 32
ALL
ALL
ALL
Cabling Practices for the Pillar Axiom 600 System96
Page 97
Chapter 4
Connect Data Cables
Table 14 Cabling principles (system size related issues) (continued)
Cabling principleApplicability
In Pillar Axiom 600 systems with two Slammers, the Brick at the
head of the string must be connected to Slammer 1 and Slammer
2.
In Pillar Axiom 600 systems with three
the head of the string must be connected to Slammer 1 or
Slammer 3, and to Slammer 2.
In Pillar Axiom 600 systems with four Slammers, the Bricks at the
head of the string must be connected to Slammer 1 or Slammer 2
and to Slammer 3 or Slammer 4.
Pillar Axiom 600 systems with more than 48 Bricks must use all
optical connections. Contact the Pillar World Wide Customer
Support Center to upgrade any Pillar Axiom system with more
than 32 FC Bricks (version 2). If Bricks are added later, a recabling may be necessary to ensure that there are no more than
eight Bricks on any Brick string.
Pillar Axiom systems that are upgraded by adding an additional
Slammer can run with the same number of Brick strings from the
prior configuration. However, if Bricks are added later, a recabling may be necessary to ensure that there are no more than
eight Bricks on any Brick string.
Slammers, the Bricks at
ALL
ALL
ALL
ALL
FIELD
Table 15: Cabling principles (Slammer connection issues) defines the principles
The Brick at the head of the string must connect to two Slammer
ports on different Slammer control units (CUs).
In Pillar Axiom 500 and
connected to FS ports on Slammers, never to the FC ports. In
Pillar Axiom 300 systems, all ports on the private interconnect
module (PIM) on the Slammer are labeled as FC ports. Thus, in
Pillar Axiom 300 systems, Bricks connect to FC1 through FC4 ports.
Cabling Practices for the Pillar Axiom 600 System97
Bricks at the head of the string connect to ports on different
Slammer CUs. For example: The Brick CU0 FC2 port must
connect to a Slammer CU0 PIM; The Brick CU1 FC2 port must
connect to a Slammer CU1 PIM.
Version 2 Slammer PIMs must have an external
connects each FC3 port to an FS10 port in the PIM on that CU.
This external cable connection is in addition to those required for
version 1 PIMs.
Slammer to Slammer and Slammer to Brick connections have
either all copper or all optical connections. Single Slammer
systems connect Slammer ports FC0 and FC2 from CU0 to CU1
and CU1 to CU0. Only these links may be optical when the rest of
the system is connected with copper cables.
cable that
ALL
ALL
ALL
Table 16: Cabling principles (Brick connection issues) defines the principles
pertinent to connecting Bricks within a Pillar Axiom
Each Brick in the Brick string connects to the previous Brick in the
string. The Brick at the head of the string connects to Slammer
ports. The cable connections in a Brick string are serial. Thus, if
one or more cables
beneath it in the Brick string are disconnected from the string.
The FC2 port in a Brick is the input port. The Brick at the head of
the string connects port FC2 on the Brick to ports on different
Slammer CUs. For Bricks that are not at the head of the string,
the Brick CU0 FC2 port must connect to the CU0 FC1 port of the
next Brick, higher in the string. Similarly, the CU1 FC2 port must
connect to the CU1 FC1 port of the next Brick higher in the string.
The FC0 port of each Brick CU must connect to the FC3 port of
the other CU in the same Brick. The two FC0 to FC3 connections
on each Brick are cross-over connections.
Cabling Practices for the Pillar Axiom 600 System98
The FC1 port is Brick is the output port. The FC1 port on each
Brick CU is either left empty or connects to the FC2 port of the
same CU of the next Brick lower in the string.
FC RAID Bricks and SSD Bricks use Slammer ports in the same
order as SATA Bricks. This cabling scheme fosters balance
among the Brick strings while
assignment of Bricks to strings. A given Brick should always be
on a specific string with specific Slammer ports.
Cable labels on both ends of the cables are used to indicate port
connections for all cables.
maintaining a predictable
ALL
NEW
NEW
Table 17: Cabling principles (Mixing Brick types) defines the principles that must
be followed
Table 17 Cabling principles (Mixing Brick types)
when mixing Brick types in strings within a Pillar Axiom 600 system.
Cabling principleApplicability
Brick strings may contain combinations of FC RAID Bricks, FC
Expansion Bricks, SATA Bricks (version 2), and SSD Bricks.
ALL
SATA (version 1) Bricks must not be in the same string as an FC
RAID Brick or a SATA Brick (version 2) or an SSD Brick. This
guideline is strongly recommended
Existing Pillar Axiom systems may not meet this guideline.
Contact the Pillar World Wide Customer Support Center for
guidance.
A Brick string may contain up to eight SATA Bricks (version 1 or
version 2), but they cannot be mixed. This guideline is strongly
recommended to enhance supportability.
A Brick string may contain up to four FC RAID Bricks (version 1),
each of which may optionally be connected to an FC Expansion
Brick. A Brick string may include up to eight FC Bricks (version 2).
A Brick string may contain up to two SSD Bricks. However, it is
recommended that only one SSD Brick is placed on a Brick string.
Cabling Practices for the Pillar Axiom 600 System99
to enhance supportability.
ALL
ALL
ALL
ALL
Page 100
Chapter 4
Connect Data Cables
Table 18: Cabling principles (FC Expansion Bricks) defines the principles that
must be followed when
cabling FC Expansion Bricks in strings within a Pillar
Axiom 600 system.
Table 18 Cabling principles (FC Expansion Bricks)
Cabling principleApplicability
FC RAID Bricks (version 1) can be configured alone or in pairs of
one FC RAID Brick (version 1) and one FC Expansion Brick
(version 1). FC RAID Bricks (version 2) do not support
FC Expansion Bricks.
FC Expansion Bricks are connected
using the J0, J1, and PNet ports. One FC Expansion Brick is
supported with one FC RAID Brick (version 1). For more
information, see
Pillar Axiom 600 SSF Cabling Reference.
to FC RAID Bricks (version 1)
.
ALL
ALL
Table 19: Cabling principles (Brick order in strings) defines the order in which
different Bricks are placed in the string within a Pillar
Table 19 Cabling principles (Brick order in strings)
Axiom 600 system.
Cabling principleApplicability
The functionality or performance of Bricks is not affected by their
relative position in a Brick string.
Factory manufacturing practice
string position followed by FC Bricks, and then SATA Bricks.
places SSD Bricks at the head of
ALL
NEW
When adding Bricks to an existing system, attach the new Brick to
the last Brick on a string.
Note: The practice of adding Bricks to the last Brick on the string
is recommended for non-disruptive upgrades and for existing
customer systems. The goal in the field must be to perform nondisruptive upgrades, if at all possible.
FIELD
Table 20: Cabling principles (Brick balance in strings) defines the balance that
must be maintained
between the various Brick types in the Brick strings within a
Pillar Axiom 600 system.
Cabling Practices for the Pillar Axiom 600 System100
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.