Enterprise Installation Services (EIS)

_________________________________________________________________

EIS Standard For Cable Labelling and Routing

Introduction
The EIS standard for cable labelling specifies how to clearly label external cables between
Sun servers and storage / network in order to ease maintenance work.

Each cable is to be labelled at both ends with an identical, self-explanatory label. The
contents of the label are mandatory; the method of creating and attaching the label is a
STRONG recommendation.
Illustrative examples (photographs, etc.) are available on the EIS web.

If a customer has his own standard for cable labelling that is to be followed provided that it
meets with our requirements (identification of connections during maintenance work).

Cable Label Format

A cable label consists of two groups with up to five fields. These fields designate the cabinet,
insertion point, board, slot and port. A typical label on an E1000 server looks like this:

saturn SB2 SBus 1/0 Port 0

CAB4 sena01 IB A0

Explanation: One FC_AL cable runs from platform "saturn" (E10000), system board 2, Sbus
1, slot 0 (i.e., the third slot from the top) to cabinet 4, A5x00 with enclosure name "sena01",
interface board A, port 0.

An example on a SunFire 15/12K looks like:

pacific IO3 C3V0 Port 1

CAB4 brazil IB A0

Labelling Servers, Storage

In order to be able to easily identify servers and storage (where often the serial numbers are
well-hidden) a label should be clearly affixed to the box with the serial number and hostname
(or platform name) for a server or similar name for storage.
It is suggested that DYMO or similar sticky label be used in format:

<Name>: <Serial Number>

Standards: Documentation / V 2.9 1 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

How to Create the Labels (Recommendation)

Use a mechanical embossing device such as a Dymo to create labels, using the smallest font.
We suggest using 12mm wide labels. Insert the labels into the plastic covers described in the
appendix and use thin cable ties to fasten them to each end of the cable. This results in a
consistent and professional appearance.

Description of Individual fields

The numbering of ports, controllers or interface boards in storage units is generally specified
by the corresponding Sun hardware documentation. Since this is not always evident, we
recommend that you place corresponding adhesive labels on the hardware for clarification.

• For a host connection, the format is:

[cabinet] <system name> <board no.> <slot no.> <port no.>
• For a storage connection (photon), the format is:
[cabinet/rack] <insertion point> <board no.> <port no.>
See the table below for additional storage systems.
• For a network connection, use the name provided by the customer, that is, the network
name, plug number, or others.

Cabinet
The first part of the label denotes the cabinet or rack number.

Insertion point
Every device in a cabinet or rack has an insertion point number or a system name.

Board number
This is the number of the CPU/MEM board, IO board, system board or motherboard within
an insertion point. Use the number on the outside of the insertion point, such as:
• E4000: 0, 2, 4, 6 and 1, 3, 5, 7.
• E10000: use SBx where x is 0-15.
• SunFire 15K/12K: use IOx where x is 0-17.
• An A5000 has two IBs, marked A and B.
• Use the number 0 for everything with only a single system board, such as, for example,
SSA1xx.
Enter a * in this field for insertion points without identifiable boards.

Slot number
These are the Sbus or PCI slots on a system board or a motherboard. Use the number from
the legend visible on the outside of the board.
• The allowable content for an Exxx IO board is SB0, SB1 or SB2 for Sbus slots and bd for
every on-board device, such as, for example, an on-board SCSI.
• The SunFire 15K/12K only supports PCI cards. The slots are labelled C3V0, C3V1,
C5V0 and C5V1.

Standards: Documentation / V 2.9 2 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

Table with Host Connections

The following table shows the contents of the label fields for the various server types.

Server Type Field 1 Field 2 Field 3 Field 4

SF15K/12K Platfrm name IO<0-17> [C3V0 | C3V1 | C5V0 | C5V1] Port <n>
SunFire x800 Platfrm name IB<6-9> SLOT<0-7> Port <n>
E10000 Platfrm name SB<0-15> SBUS [0 | 1] / [0 | 1] Port <n>
PCI 0.0 | PCI 1.0 Port <n>
V1280 Host name Slot<0-5> Port <n>
V880 Host name Slot<0-9> Port <n>
RSC [TP | MODEM | SERIAL]
V480 Host name Slot<0-5> Port <n>
RSC [TP | MODEM | SERIAL]
280R Host name Slot<1-4> Port <n>
RSC [TP | MODEM | SERIAL]

T2000 Host name PCI E [0 – 2] Port <n>

PCI X [0 – 1] Port <n>
[TP | MODEM | SERIAL]
NET MGT | [0-3]
X4100 Host name PCI [0 – n] Port <n>
X4200 [TP | MODEM | SERIAL]
NET MGT | [0-3]

Standards: Documentation / V 2.9 3 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

Port number
Use the numbers visible on the device. For example, an QFE card has ports 0 - 3 (qfe0, qfe1,
qfe2 or qfe3), an FC-AL hub has ports 0 - 7 and an SOC card has ports A and B (SOCa,
SOCb).

Storage Connection
The following table shows the contents of the label fields for the various storage types.

StorEdge Type Field 1 Field 2 Field 3 Field 4

A5x00 CAB number Enclosure name IB <A|B><0|1>
A3x00 1*5 CAB number RAID A CTRLR <A|B> [IN|OUT]
A3x00 2*7 CAB number RAID <A|B> CTRLR <A|B> [IN|OUT]
A3x00 3*15 CAB number RAID <A|B|C> CTRLR <A|B> [IN|OUT]
A3x00FC 1*5 CAB number RAID A CTRLR <A|B>
A3x00FC 2*7 CAB number RAID <A|B> CTRLR <A|B>
A3x00FC 3*15 CAB number RAID <A|B|C> CTRLR <A|B>
FC_AL hub CAB number Hub <A|B>number
A1000 CAB number Tray number or "name" RAID A OUT
D1000 CAB number Tray number or "name" SCSI <A|B>
D2 CAB number Tray number or "name" SCSI <A|B>
S1 CAB number Tray number or "name" [IN|OUT]
D240 CAB number Tray number or "name" [LEFT|RIGHT] [IN|OUT]
T3WG CAB number T3 Hostname UNIT 1
T3ES CAB number T3 Hostname UNIT 1
CAB number T3 Hostname UNIT 2
SE3310 (JBOD) CAB number Tray number or "name" [A]|[B] [IN|OUT]
SE3310 (RAID) CAB number Tray number or "name" CH<0|1|2|3>
SE3900 (INDY) CAB number Hostname or IP Port number
SE6900 (INDY) CAB number Hostname or IP Port number

Note: If an A5x00 storage is switched on, the enclosure name is shown in the display, but it
is not visible if the device is switched off. Therefore, it is helpful to use a DYMO or similar
embossing device to create an adhesive label with the enclosure name and fasten it to the
device. The same applies to A3x00 (RDAC) controllers if there is more than one in the
cabinet. These patterns can be expanded if the customer uses his own label scheme for in-
house cables.

Standards: Documentation / V 2.9 4 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

Examples according to the table shown above:

• A5x00 storage: CAB3 sena01 IB A0

• FC_AL hub: CAB6 hub A6
• A3500 storage: CAB4 RAID B CTRLR A OUT
• A3500FC storage: CAB4 RAID B CTRLR A
• D1000 storage: CAB1 D1000#A SCSI A

Standards: Documentation / V 2.9 5 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

The SE99x0 storage has a unique serial number (but no names) and the nomenclature given
here is derived from the front panel of the unit:

Storage Type Field 1 Field 2 Field 3 Field 4

SE9910 CAB number SN#nnnnn CLUSTER 1 CH A-M
CAB number SN#nnnnn CLUSTER 2 CH A-M

NOTE: In the channel sequence A-M there is no channel "I".

Storage Type Field 1 Field 2 Field 3 Field 4

SE9960 CAB number SN#nnnnn CLUSTER 1 CH A-R
CAB number SN#nnnnn CLUSTER 2 CH A-R

NOTE: In the channel sequence A-R there are no channels "I" & "O".

Storage Type Field 1 Field 2 Field 3 Field 4

SE9970 CAB number SN#nnnnn CLUSTER 1 CH A-M[U|L]
CAB number SN#nnnnn CLUSTER 2 CH A-M[U|L]

NOTE: In the channel sequence A-M there is no channel "I".

NOTE: Additionally there is U(pper) and L(ower) Port.

Storage Type Field 1 Field 2 Field 3 Field 4

SE9980 CAB number SN#nnnnn CLUSTER 1 CH A-M[U|L]
CAB number SN#nnnnn CLUSTER 2 CH A-M[U|L]

NOTE: In the channel sequence A-R there are no channels "I" & "O".
NOTE: Additionally there is U(pper) and L(ower) Port.

Standards: Documentation / V 2.9 6 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

Limitations of the Cable Labelling Standard

It has been pointed out that in the above examples platform names (E10000) and names of
A5x00 storage could also change, thus rendering the cable labels useless. If there are
concerns about this one suggestion is to use serial numbers in place of platform names etc.
However, it is not unknown for hardware items (storage or even complete servers) to be
exchanged and thus the serial numbers would change.

Cable Routing
It is part of a high-quality installation to route the cables to the server and storage in a tidy
way. This must be consistent with ease of access to FRUs etc. on the server such as fan trays
and filters.

For an E10000 server attachment points are provided in the frame so that the data cables can
be neatly bundled and attached on a per-board basis. The cables should not be too tight
(example photograph in the EIS web). Velcro strips can be used to neatly hold bundles of
cables together. In the event that a fan tray of filter has to be exchanged, the engineer has
only to cut the cable tie and subsequently replace it.

For a Sun Fire 15K / 12K the situation is more problematical. The I/O slots are higher up the
frame compared to the E10000 and there seem to be no specific attachment points. There is a
horizontal bar below the I/O boards to which one could attach cable ties. It is suggested that
one carefully routes the data cables to run straight down from the I/O cards. They should be
grouped together and attached to the horizontal slotted bar with Velcro cable ties so that they
can be easily moved if needed. Velcro ties should also be used to keep the groups of data
cables neatly tied together. This recommendation should create less stress on the cables,
especially those near the center.

Standards: Documentation / V 2.9 7 Print date: 13. Jun. 2006

 Enterprise Installation Services (EIS)
_________________________________________________________________

Appendix: Label Tubing and Cable Tie Types Suppliers:

This appendix describes the recommended tools for producing EIS cable labels.
Prices mentioned here are given in good faith but are not guaranteed.

We recommend that you use 12-mm-DYMO tapes and 13-mm-tubing. We also recommend
that you use plastic tape rather than paper tape. Paper tape is sufficient for labels within
tubing but is not satisfactory for labels used for marking servers and other cabinets.

Label Maker
There are a wide range of labellers available from companies such as DYMO.
The labeller should be capable of writing two lines across the label (small font).
A low-price example is LetraTag Part No. 11944, 11946. Price: US $49.99.
You may be happier with a better model!!!
White plastic tape ½” (12 mm) LetraTagTapes Part No. 91331. Price: US $6.99.
See http://www.dymo.com.

Tubing for Labels

Helafix HCR12 (13mm) 25m Part No. 525-13003. Price (approx): US $55.
See http://www.HellermannTyton.de/ht/content/d/katalog/product/German/743.html

Tubing Cutter
Helafix HCT2 (13mm) Part No. 525-00013. Price (approx): US $120.00.
See http://www.HellermannTyton.de/ht/content/d/katalog/product/German/896.html

Cable Ties (to attach label/tubing to cables)

Length approx. 4” (100mm); width approx. 0.1” (2.5mm)
Thomas & Betts TY100-18 (or similar)

Grip Ties (Velcro Fasteners)

Length approx. 11” (200mm); width 0.5” (12mm) blue (or black)
HellermannTyton Part No. GT.50X11_P2-6
See http://www.execpc.com/industrialelectronics/tyton/tyt10.htm
or Thomas & Betts, Part No. FO-200-40-6
See http://www.TNB.com.

NOTES:
• In AMER contact at HellermannTyton is Mr. Todt Fries, Tel +1 414 355 1130.
• Another supplier in USA is EIS Inc. (no connection!) http://www.eis-inc.com.

© 2004 Sun Enterprise Services

Standards: Documentation / V 2.9 8 Print date: 13. Jun. 2006