How a Linklamp visit runs: port photos, signoff, rollback

Your engineer stays in charge

The visit runs on your bridge call: Teams, Zoom or a phone bridge. Your engineer opens the change, watches links come up, and says when the visit is done. The person on site does not configure, re-address or reboot anything your engineer has not asked for.

Photos the ticket can use

Every labelled port is photographed before anything moves and again after, with its label tape in frame. A photo without a label only shows cords; a photo with the label ties a port to a row of your map, so your engineer can check a repatch from the thread.

If your client already labels ports, their scheme goes on the tape. If not, we propose one: SW1-23 for switch 1, port 23; A-09 for panel A, port 9. It follows common TIA-606 practice, which is a voluntary standard, not a legal requirement.

Rollback, when you want it

Say "keep the old switch mounted until signoff" and the replacement goes into a free rack unit beside it. If signoff fails, cords go back to the old switch, matching the before photos, and your engineer decides what happens next.

No port map? Trace first

Where labels are missing, the visit begins with a trace stage: each cord followed, both ends labelled, and the current port map written down. You get that map with the photos, and the repatch to your new layout can follow in the same window or a second one.

What lands in the ticket

Before and after photos of every labelled port, the traced map if there was one, the time on and off site, and close-out notes: anything unexpected, anything left as it was, and where the old switch went.