Table of Contents
Advertisement
Chapter 4 Connect Data Cables
Table 16 Cabling principles (Brick connection issues) (continued)
Cabling principle
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 maintaining a predictable
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.
Table 17: Cabling principles (Mixing Brick types)
be followed when mixing Brick types in strings within a Pillar Axiom 600 system.
Table 17 Cabling principles (Mixing Brick types)
Cabling principle
Brick strings may contain combinations of FC RAID Bricks, FC
Expansion Bricks, SATA Bricks (version 2), and SSD Bricks.
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 to enhance supportability.
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 System
Applicability
ALL
NEW
NEW
defines the principles that must
Applicability
ALL
ALL
ALL
ALL
ALL
99
Advertisement
Table of Contents
