The technician reading your ticket is standing in a cold, loud room, in front of forty identical black boxes, wearing gloves, holding a tablet. They cannot see your monitoring. They do not know your naming scheme. They have another six tickets after yours.
Every ambiguity you leave becomes a phone call, a delay, or the wrong cable being unplugged. This part is how to not do that.
The one principle
Write instructions that can be followed by someone competent who knows nothing about your systems.
That is the whole discipline. Not dumbed down — the technician is skilled, often far more skilled with hardware than you are. But context-free. They know racks, cables, screws and connectors. They do not know that srv-web-11 is the one that matters, or that "the storage box" means the 4U at the bottom.
The two failure modes that follow from ignoring this are worth naming, because they are the ones that actually happen. Ambiguity, where the instruction is unclear and the technician either guesses or calls you. And under-specification, where you assume a step is obvious and it is not, so the job comes back half-done.
The ticket template
Every remote hands request should have these sections. Not all of them will have content every time, but the headings stop you forgetting one.
SUBJECT: [action] on [device] at [cabinet] / [U position]
LOCATION
Facility: DC1, 123 Example Road
Cage / suite: Cage 14
Cabinet: ROW-C RACK-07 (label on door: "C07")
U position: U37 (numbered from the bottom; U1 is the lowest)
Front or rear: REAR
Identifying: ID LED is lit and flashing blue, front and rear
DEVICE
Hostname: srv-web-11
Make/model: Dell PowerEdge R650, 1U
Service tag: ABC1234
Asset label: on the pull-out tab, front right
WHAT I NEED DONE
1. ...
2. ...
3. ...
WHAT I DO NOT WANT TOUCHED
...
HOW I WILL VERIFY
...
IF SOMETHING IS DIFFERENT FROM THIS DESCRIPTION
Stop and contact me. Do not improvise. I am on <phone> until <time>.
ESCALATION / URGENCY
Production impact: yes/no. Target: within N hours.
Four of those sections do disproportionate work.
Front or rear. Say it explicitly, every time. Almost all work is at the rear; almost all descriptions unconsciously assume the front. And when you say left or right, say as viewed from the rear — a rear-facing observer's left is the front-facing observer's right, and this exact confusion unplugs the wrong power cord.
The ID LED. From Part 4: light it before you file the ticket. ipmitool ... chassis identify 300 turns "the third one down" into "the one flashing blue". If the BMC is unreachable, fall back on the service tag or asset label, and say where the label physically is.
What I do not want touched. The most valuable line in the ticket, and the one people leave out. "Do not disturb any other cable in this cabinet. If a cable must be moved to gain access, photograph it first and put it back exactly as found."
Stop and contact me. Explicitly give permission to stop. Without it, a conscientious technician facing a situation that does not match your description will try to make it work, and that is where damage happens.
Standard job: rack and cable a new server
This is the big one and it is a smart hands job, not remote hands — it needs judgement and hardware skill. Everything in Parts 1 through 5 shows up here.
SUBJECT: Install and cable 1x Dell R650 in ROW-C RACK-07 at U20-U20
LOCATION
Cage 14, ROW-C RACK-07, U20 (1U). Numbered from the bottom.
HARDWARE
Shipment: tracking 1Z999..., delivered <date>, marked "ATTN: Cage 14"
Contents: 1x Dell PowerEdge R650 (1U) + ReadyRails sliding rail kit
2x C13-C14 power cords (1x blue, 1x red)
2x 2m SFP28 passive DAC
1x 2m Cat6A patch lead (grey)
Service tag on the box: ABC1234
MECHANICAL
1. Install the sliding rails at U20, front and rear posts.
Square-hole rack; cage nuts as required by the kit.
2. Rack the server at U20. Confirm the front bezel sits flush and the
rails travel freely through their full extension.
3. Fit the cable management arm supplied with the kit.
4. Leave a service loop on all rear cables so the server can be pulled
fully forward without unplugging anything.
POWER (two cords — they must go to DIFFERENT PDUs)
5. Blue cord: PSU1 -> PDU-A, outlet A14.
6. Red cord: PSU2 -> PDU-B, outlet B14.
** Both cords must NOT be in the same PDU. **
7. Engage the retention clips on both outlets.
DATA
8. DAC 1: server NIC port 1 (left port as viewed from the REAR)
-> switch sw-c07-01, port Et14
9. DAC 2: server NIC port 2 (right port as viewed from the REAR)
-> switch sw-c07-02, port Et14
MANAGEMENT
10. Cat6A grey: the RJ45 labelled "iDRAC" on the server rear
-> switch mgmt-sw-01, port 14
This is the small dedicated port, NOT one of the four LOM ports.
LABELLING
11. Label both ends of every cable with the far end, e.g.
server end of DAC1: "-> sw-c07-01 Et14"
switch end of DAC1: "-> srv-web-14 p1"
POWER ON
12. Power the server on at the front button. Confirm both PSU LEDs are
green and the front status LED is not amber.
PHOTOS PLEASE
13. Rear of the server showing all five cables seated.
14. PDU-A outlet A14 and PDU-B outlet B14, labels visible.
15. Front of the rack showing the server at U20 with the bezel on.
DO NOT
Do not disturb any other equipment or cabling in this cabinet.
If anything does not match the above, stop and call me.
The things that make that ticket work: every port has a name, every cable has a colour, the A/B constraint is stated twice, the management port is distinguished from the data ports explicitly (Part 4's dedicated-versus-shared distinction, expressed as a physical instruction), and the photos let you verify all of it without trusting anybody's memory.
Ask for photos on every install. It costs the technician thirty seconds and it is the only durable record of how the cabinet was left.
Standard job: patch a port
Short, but the same rules apply.
SUBJECT: Patch panel PP-01 port 14 -> switch sw-c07-01 port Et22
Cage 14, ROW-C RACK-07. REAR of cabinet.
1. Take a 1m LC-LC duplex singlemode (yellow) patch lead from the
spares bin in this cabinet.
2. Connect patch panel PP-01, port 14 -> switch sw-c07-01, port Et22.
3. Clean both ends before insertion.
4. Label both ends.
5. Photograph the panel and the switch port.
Do not remove or move any existing lead. If port 14 is already occupied,
STOP and tell me what is in it — do not unplug it.
That last paragraph exists because "patch port 14" and "port 14 already has something in it" is a very common collision, and without an instruction the technician has to guess whether the existing lead is stale or live.
The fibre-cleaning line is not fussiness. From Part 3: a fingerprint on a ferrule is enough to kill a 100 Gb link.
Standard job: reseat
The most common ticket there is, and the least likely to go wrong — provided you say which end.
SUBJECT: Reseat DAC on srv-web-11 NIC port 1
Cage 14, ROW-C RACK-07, U37. REAR. ID LED is lit (flashing blue).
1. Locate the DAC in server NIC port 1 (left as viewed from the REAR).
It should be labelled "-> sw-c07-01 Et14".
2. Unplug it at the SERVER end only. Wait 10 seconds. Plug it back in
firmly until it clicks.
3. Tell me the link LED state on the server port before and after.
4. If there is still no link, repeat at the SWITCH end (sw-c07-01,
port Et14) and tell me again.
I am watching the switch port; I will confirm within 30 seconds of each step.
Note the sequencing — one end at a time, with a report between. If you ask for both ends at once and it comes back working, you have learned nothing about which end was faulty.
Standard job: power cycle at the PDU
This is rung 3 of the ladder from Part 4, and it has a specific trap.
SUBJECT: Full power cycle of srv-db-03 at the PDU (BMC unresponsive)
Cage 14, ROW-C RACK-07, U12. REAR.
The BMC is not answering, so I cannot do this myself and the ID LED
is NOT lit. Identify by the service tag XYZ5678 on the front pull-tab.
This server is DUAL-CORDED. BOTH cords must be removed for this to work.
1. Confirm the two cords for this server: PDU-A outlet A06 (blue)
and PDU-B outlet B06 (red). Both are labelled "srv-db-03".
2. Unplug BOTH cords.
3. Wait 30 seconds. (Less than this and standby power does not drain,
which is the whole point of the exercise.)
4. Plug both back in, blue to A06 and red to B06.
5. Confirm both PSU LEDs come up green.
Do not use the front power button. I need standby power removed.
Two things there are the whole reason this ticket exists in this form. Both cords, because removing one from a redundant machine changes nothing. And thirty seconds, because the objective is draining standby power to clear the BMC, and a quick out-and-in does not do it.
Standard job: read me the state
The cheapest and most underused request. When you have no out-of-band access at all, a technician's eyes are a diagnostic instrument.
SUBJECT: Report physical status of srv-db-03
Cage 14, ROW-C RACK-07, U12. Service tag XYZ5678.
Please report, front and rear:
1. Front status LED: off / green / flashing amber / solid amber?
2. Any text on the front LCD panel? Photograph it if present.
3. Both PSU LEDs at the rear: green / amber / off? Which is which?
4. Both NIC link LEDs: lit? flashing? dark?
5. Are the fans audibly spinning?
6. Photograph the front and the rear.
No action needed — I only need the observations.
An amber PSU LED and a photographed LCD reading a fault code will frequently tell you exactly what is wrong before you have opened a hardware support case, and it costs one short ticket.
What not to ask for
Three categories, and knowing them saves you a rejected ticket and some embarrassment.
Do not ask them to diagnose. "Can you see why it's not working?" is not a task. Give them observations to make and steps to take. They do not know what "working" looks like for your system.
Do not ask them to touch your data or your configuration. They do not log into your servers. If a job needs a login, that is your side of the demarc — figuratively as well as literally. Where a technician does need console access during, say, a firmware recovery, that is arranged explicitly with credentials scoped to the task, not assumed.
Do not ask for anything ambiguous about identity. "The server that's broken", "the new one", "the third from the top". Use the U position, the hostname, the service tag, and the ID LED.
And one thing to be careful with rather than avoid: anything that risks other equipment. Moving a bundle to get access, removing a blanking panel, sliding a machine forward on rails in a densely cabled cabinet. Those are fine to ask for, but say explicitly what may be disturbed and ask for before-and-after photographs.
Shipping hardware in
A related process that goes wrong more often than the technical work.
Most facilities require advance notice of an inbound shipment, with a ticket giving the tracking number, the expected date, the number of packages and the destination cage. Without it, the loading dock may refuse delivery or the boxes may sit in a receiving area nobody told you about.
Mark the boxes with your company name and cage number, not just an address. Say in the ticket whether you want them unboxed and staged, or left sealed. And ask them to record the service tags of what arrived and photograph any physically damaged packaging before it is opened — that is the evidence you need if a machine turns out to be dead on arrival.
Storage of packaging and empty boxes is usually charged or prohibited. Say what should happen to the cardboard.
Verify everything
Every ticket ends with your verification, and the point is to check the result, not the report.
- After a rack and cable: BMC pings on the management VLAN,
lldpctlshows the expected switch and port on both NICs, both PSUs report present and drawing power, and the photographs show A and B outlets. - After a patch: the link comes up and optical Rx power is in range. From Part 4 — if you are graphing DOM, you can see the level, not just the up/down.
- After a reseat: the switch port counter stops incrementing errors, not merely that the link is up.
- After a power cycle: the machine boots and
ipmitool ... sel elistshows the power event where you expect it.
And after any physical work in a cabinet, glance at the cabinet's total power draw on the PDUs. An unexpected change means something was plugged in or unplugged that you did not ask about.
The one-line summary
Write for a skilled person who knows nothing about your systems. Cabinet, U position, front or rear, and the ID LED. Name every port and every outlet. State the A/B constraint explicitly. Say what must not be touched, give explicit permission to stop, ask for photographs, and verify the result yourself rather than trusting the report.
Next up: Part 8 — the cheat sheet, which is every number, connector and command in this series on one page.