Linklamp

Dearborn, MI ยท switch swaps and repatching for MSPs

Hands at the rack in Dearborn while your engineer runs the cutover.

Describe the switch swap or repatch. We draw the visit back, then email a proposal with duties, exclusions, price and a proposed time.

  • Your port map followed row by row
  • Every labelled port photographed, before and after
  • Done when your engineer signs off
Try one:
Port map optional, paste rows

What comes back

Your closet, drawn from your words: the ports and the label each photo will carry, what the person on site does, where your engineer signs off, and what the visit will not touch. This is a worked example.

Example · dental office, 24-port PoE swap

Dental office, 48126: swap the 24-port PoE switch, repatch to your 24-row map, photograph every labelled port, done when Dana signs off on Teams.

Site
Dental office, Dearborn, MI 48126
Port map
24 rows from you
Replacement
shipping, pre-configured
Old switch
keep it on site
Signoff
Dana on Teams
Access
Office manager has the key
U1SW1 · Replacement switch · 24-port PoE · pre-configured

Every lamp is unlit. They light when Dana confirms on the bridge, on the day.

  • phones 1-8 · PoE
  • APs 9-12 · PoE
  • workstations 13-20
  • printer 21
  • x-ray sensor PC 22
  • firewall uplink 23
  • unused 24
  • Top bar: PoE device

SW1-23firewall uplink

Before
After

Proposed label, after common TIA-606 practice (voluntary). If your client already has a scheme, we use theirs. The tape is in frame in both photos, so the ticket shows which port moved where.

Outside this visit

  • Switch configuration and VLANs Dana, your engineer

    Your engineer keeps configuration, firmware and acceptance. The person on site cables, powers and photographs; they change no settings unless your engineer asks them to type a command at the console.

Not in any visit: New circuits or outlets, anything on the fire alarm system, new cable runs (priced separately only when you ask), and switch configuration.

Why these lines sit where they do

The run-sheet

On siteDana, remote

  1. 01
    On site

    Arrive inside the client window; office manager has the key. Check in on the bridge on Teams.

    Dana, remote

    Dana joins on Teams and opens the change.

  2. 02
    On site

    Photograph the closet, then every labelled port before anything moves.

    Dana, remote

    Dana gets the before photos in the ticket thread.

  3. 03
    On site

    Unmount the old switch, mount the replacement in its place, power it.

    Dana, remote

    Dana confirms the new switch is up on management.

  4. 04
    On site

    Repatch row by row to your 24-row map.

    Dana, remote

    Dana watches links come up as cords move.

  5. SignoffDana confirms, remotely
    • phones 1-8 up and powered
    • APs 9-12 up and powered
    • workstations 13-20 have link
    • printer 21 has link
    • x-ray sensor PC 22 has link
    • firewall uplink 23 up

    Lit by Dana, on the day. Nothing below this line happens until then.

  6. 05
    On siteRollback, only if needed

    If signoff fails: remount the old switch and move the cords back, matching the before photos.

    Dana, remote

    Dana calls the rollback.

  7. 06
    On site

    Photograph every labelled port after; label the old switch and leave it on site. Leave close-out notes.

    Dana, remote

    Dana gets the after photos and notes for the ticket and closes the change.

What MSPs ask before sending a stranger to the rack

Who keeps the configuration?

Your engineer, from the bridge. The person on site cables, powers, labels and photographs, and changes no settings unless your engineer reads out a console command. How a visit runs

What do the photos show?

Each labelled port, before and after, with the tape in frame, so a repatch can be checked against your map from the ticket. The photo standard

What is not part of the visit?

New outlets or circuits, anything on the fire alarm system, and new cable drops, which the proposal prices separately or leaves out. Where the lines sit