Table 14 Cabling principles (Slammer connection issues) (continued)
Cabling principle
Applicability
module (PIM) on the Slammer are labeled as FC ports. Thus, in
Pillar Axiom 300 systems, Bricks connect to FC1 through FC4 ports.
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.
ALL
Version 2 Slammer PIMs must have an external cable that
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.
ALL
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.
ALL
Table 15: Cabling principles (Brick connection issues)
defines the principles
pertinent to connecting Bricks within a Pillar Axiom 600 system.
Table 15 Cabling principles (Brick connection issues)
Cabling principle
Applicability
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 to a Brick are disconnected, all the Bricks
beneath it in the Brick string are disconnected from the string.
ALL
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.
ALL
Chapter 4 Connect Data Cables
Cabling Practices for the Pillar Axiom 600 System
89
