Skip to content

Smart Hands Services: On-Site Configuration Support Worldwide

By Reboot Monkey Team

Certified engineers performing Layer 2/3 configuration tasks inside your datacenter. OS installs, firmware updates, NIC setup, structured cabling, and BGP peering across 250+ cities in 190 countries.

Smart Hands Services: On-Site Configuration Support Worldwide

What Is a Smart Hands Service?

Smart hands is a professional on-site datacenter support service that places certified engineers inside third-party facilities to perform configuration-level infrastructure work. The key distinction from remote hands lies in scope: smart hands covers Layer 2 and Layer 3 work, including operating system installation, firmware lifecycle management, NIC driver configuration, structured cabling, VLAN tagging, BGP session setup, and SAN zoning. These tasks require physical presence and engineering judgment, not just the ability to press a power button. Reboot Monkey provides smart hands services as a vendor-neutral, facility-independent operator. Our engineers work inside Equinix, Digital Realty, NTT, CyrusOne, Coresite, and every other major colocation operator worldwide. We are not affiliated with any facility operator, and our engineers represent your interests exclusively. Approximately 28% of remote hands engagements escalate to smart hands once the scope is understood on-site. The cleaner the task specification before the visit, the fewer surprises on both sides.
  • Layer 2/3 configuration: OS installs, firmware updates, NIC config, VLAN tagging
  • Physical Layer 1 work included: structured cabling, cross-connect provisioning, rack builds
  • Vendor-neutral across Dell, HP/HPE, Cisco, Juniper, Arista, Supermicro, and Lenovo
  • Works inside any colocation facility worldwide, regardless of operator
  • Single contract, single point of contact across all facilities

Smart Hands vs Remote Hands: Knowing Which You Need

The difference between smart hands and remote hands is the level of engineering judgment required. Remote hands covers Layer 1 physical tasks: power cycling, cable identification, visual inspection, connecting a KVM console, and confirming LED status. These tasks are straightforward and can often be guided remotely over a phone call. Smart hands begins where remote hands ends. When the problem involves OS configuration, a firmware version mismatch, a misconfigured NIC driver, or a VLAN assignment that needs verifying against a switch CLI, you need a certified engineer on-site. Smart hands engineers do not just follow a checklist. They interpret state, spot anomalies, and make configuration decisions within the agreed scope. A practical rule: if the task requires logging into a device CLI, editing a configuration file, running a driver installer, or physically terminating fiber, you need smart hands. If the task is locating a cable and plugging it in, or cycling a power outlet, remote hands is likely sufficient. For ambiguous tasks, our ops team reviews the specification before scheduling and recommends the right tier.
  • Remote hands: Layer 1 physical tasks (power cycling, cable ID, visual checks)
  • Smart hands: Layer 2/3 configuration (OS install, firmware update, NIC config, BGP session setup)
  • 28% of remote hands engagements escalate to smart hands scope once on-site
  • Pre-engagement scope review prevents misclassification and delays
  • Both services available under a single Reboot Monkey contract

Layer 1: Physical Infrastructure

Physical layer work is part of most smart hands engagements because configuration tasks almost always require physical setup first. Engineers perform structured cabling installation using Cat6A UTP, OM4 multimode fiber, and OM5 wideband multimode fiber, terminating to patch panels and cross-connect frames. Cross-connect provisioning includes accessing the Main Meet Room (MMR) at colocation facilities, activating circuits via Letter of Authorization (LOA), and installing patch cords to customer or IX fabric. Rack and cage builds are executed to customer-specified configurations, including PDU selection, cable management, blanking panel installation, and rail-mounted equipment positioning.
  • Structured cabling: Cat6A, OM4 multimode, OM5 wideband multimode fiber
  • Cross-connect provisioning via LOA at MMR (Equinix, Digital Realty, Interxion)
  • Rack and cage builds to customer power, cooling, and access specifications
  • Hardware acceptance testing (HAT) with written documentation handoff

Layer 2: Data Link Configuration

Layer 2 configuration is among the most common smart hands workloads. Engineers assign 802.1Q VLAN IDs to customer switch ports, configure native VLANs, set up trunk ports for multi-VLAN uplinks, and apply Spanning Tree parameters (RSTP/MSTP). Work is performed across Cisco IOS-XE, Cisco NX-OS, Juniper JunOS, Arista EOS, and Cumulus Linux. Port channel and LACP configuration increases bandwidth between server and top-of-rack switch. Ethernet interface configuration covers speed negotiation from 1G through 100G, MTU settings (standard 1500 or jumbo frames at 9000), flow control, and duplex mode. Link status is verified post-configuration with no CRC errors confirmed before the engineer leaves. SAN zoning on Brocade and Cisco MDS fabric switches is treated as a high-complexity task. Engineers create zones, activate zone sets, and map HBA WWNs to storage array ports. Dual-sign-off with the customer is required before zone set activation.
  • VLAN tagging (802.1Q), trunk port setup, Spanning Tree (RSTP/MSTP) configuration
  • Port channels and LACP for multi-link redundancy and bandwidth aggregation
  • Ethernet interface configuration: 1G to 100G, MTU, flow control, duplex
  • SAN zoning on Brocade and Cisco MDS fabric (dual-sign-off before activation)

Layer 3: Network Configuration

Layer 3 smart hands work includes static IP assignment on server NICs, routing protocol configuration (BGP and OSPF), and BGP session setup at internet exchanges. Engineers configure subnet, gateway, DNS, and NTP settings directly on the server via SSH or out-of-band console (iDRAC, iLO). BGP session configuration matters at every major internet exchange. In Frankfurt, engineers configure sessions at DE-CIX, which operates a 3.5+ petabit ecosystem (per DE-CIX, 2025). In Amsterdam, at AMS-IX. In Vienna, at VIX. In Sao Paulo, at IX.br, which operates at over 22 terabits per second and connects more than 2,100 autonomous systems. Engagements cover route server submission, AS-path filter setup, BGP community configuration, and prefix-list validation, with post-configuration verification confirming no route leaks and correct AS_PATH integrity.
  • Static IP assignment, gateway, DNS, NTP configuration via SSH or out-of-band console
  • BGP session setup: DE-CIX (Frankfurt), AMS-IX (Amsterdam), IX.br (Sao Paulo, 22+ Tbps), VIX (Vienna)
  • OSPF internal routing configuration for multi-hub deployments
  • Firewall rules on Linux (UFW, iptables, nftables) and Windows Server environments

Operating System and Firmware Lifecycle

OS installation via USB media or out-of-band management (iDRAC virtual media, iLO virtual media) is the highest-frequency smart hands workload. Engineers boot from installer media, partition disks, configure network and hostname, and complete OS setup to a customer-defined baseline. Supported environments include Ubuntu Server 22.04 LTS and 24.04, CentOS 7/8, CentOS Stream 9, RHEL 8/9, Debian 11/12, Windows Server 2022, Proxmox VE, and KVM/libvirt. BIOS and UEFI configuration precedes OS installation on new or reconfigured hardware. Engineers set virtualization flags (VT-x, AMD-V), boot order, BMC settings, and Secure Boot or TPM requirements. Hardware coverage includes Dell PowerEdge (R660, R6715, R6625), HPE ProLiant (DL360 Gen11, DL580 Gen11), and Supermicro variants. Firmware updates span BIOS, NIC, SSD, and BMC components, covering Mellanox/NVIDIA ConnectX, Intel XXV710, and Broadcom NICs, plus iDRAC, iLO, and generic IPMI. Post-update verification confirms new firmware versions and validates no regressions. NIC driver installation for DPDK, SR-IOV, and RDMA workloads is validated with ethtool and iperf benchmarking.
  • OS install: Ubuntu 22.04/24.04, RHEL 8/9, CentOS, Debian, Windows Server 2022, Proxmox, KVM
  • BIOS/UEFI config: virtualization flags, boot order, BMC settings, Secure Boot, TPM
  • Firmware updates: BIOS, NIC (Mellanox, Intel, Broadcom), SSD, iDRAC/iLO/BMC
  • NIC driver install and validation for DPDK, SR-IOV, and RDMA workloads

Hardware Diagnostics and Acceptance Testing

New and refurbished hardware needs systematic validation before production handoff. Reboot Monkey engineers run hardware acceptance testing (HAT) as part of every new deployment. POST verification is monitored via iDRAC/iLO console, with common failures (bad DIMM, CMOS issue, BIOS version) resolved on-site. Memory diagnostics run to a zero-error acceptance standard. Disk health checks use SMART monitoring and stress testing (fio, dd). Network validation confirms line-rate performance on all NICs with no CRC errors under iperf load. Thermal monitoring reviews sensor data and verifies correct airflow orientation before the engineer closes the engagement.
  • POST verification with on-site resolution (DIMM reseat, CMOS clear, BIOS update)
  • Memory diagnostics: BIOS-level or MemTest86, zero-error acceptance standard
  • Disk health: SMART monitoring and stress testing (fio, dd)
  • Network validation: iperf throughput, CRC error check under load
  • Thermal monitoring: sensor review and airflow orientation confirmed before handoff

Global Coverage: Where Reboot Monkey Smart Hands Operates

Reboot Monkey smart hands engineers operate across 250+ cities in 190 countries. Primary hubs with resident engineers are located in Sao Paulo, Frankfurt, London, Amsterdam, New York, Los Angeles, Dallas, Ashburn, Tokyo, and Singapore. Secondary hub expansion to Munich, Delhi, Seoul, Toronto, and Sydney is scheduled for 2026 to 2027. In North America, engineers serve major colocation metros including Ashburn (Northern Virginia), New York, Los Angeles, and Dallas. In APAC, the Tokyo hub serves Japan and surrounding markets at Equinix TY1 through TY5, Digital Realty, and NTT Data Towers facilities, while Singapore provides coverage for Southeast Asia. For facilities outside primary hub coverage, Reboot Monkey coordinates dispatch from the nearest hub or, where travel times are prohibitive, provides remote guidance with a customer-hired local engineer executing under Reboot Monkey direction. The 24/7 NOC provides continuous coordination. Priority-1 incidents carry a 4-hour on-site response SLA in deployed cities. Planned deployments are scheduled as 4-hour or 8-hour engineer blocks with advance booking.
  • 250+ cities across 190 countries with resident and dispatch engineers
  • Primary hubs: Sao Paulo, Frankfurt, London, Amsterdam, New York, Los Angeles, Dallas, Tokyo, Singapore
  • Expansion to Munich, Delhi, Seoul, Toronto, Sydney in 2026-2027
  • 24/7 NOC with 4-hour P1 response SLA in deployed cities
  • 4- or 8-hour engineer blocks available for planned deployments

How a Smart Hands Engagement Works

Every Reboot Monkey smart hands engagement follows a documented delivery workflow. The customer submits a request with facility, task scope, deadline, and SLA requirement. The ops coordinator confirms engineer availability and facility access authorization, then provides a time window and engineer contact details. Before the visit, the engineer receives a complete task specification, customer contact information, facility access credentials, equipment serial numbers, and any customer-provided documentation such as network diagrams or configuration files. On arrival, the engineer completes facility access control and executes the task per specification, documenting work in real time with photos, console outputs, and configuration snapshots. After task completion, the engineer validates the final state with the customer via phone or video. The final deliverable is a chain-of-proof documentation package: task completion checklist, configuration change log with before-and-after diffs, performance baseline data, firmware versions post-update, and a written summary delivered within 24 hours. This documentation supports change management requirements under SOC 2 CC6.4, PCI DSS 4.0, and ISO 27001:2022 A.7.
  • Step 1: Customer request with facility, scope, deadline, and SLA
  • Step 2: Ops coordinator confirms engineer availability and facility access
  • Step 3: Engineer briefed with task spec, access credentials, and customer docs
  • Step 4: On-site execution with real-time documentation (photos, console logs)
  • Step 5: Customer validation via phone or video before engineer departs
  • Step 6: Chain-of-proof report delivered within 24 hours (config diffs, firmware versions, photos)

Vendor-Neutral Engineering Across All Hardware and Network Platforms

Reboot Monkey engineers are certified across the hardware and network platforms that enterprise infrastructure teams actually deploy. On the server side, engineers work across Dell PowerEdge, HP/HPE ProLiant, Supermicro, Lenovo, and custom builds. On the network side, engineers are proficient across Cisco IOS-XE, Cisco NX-OS, Juniper JunOS, Arista EOS, and Cumulus Linux. Storage engineering covers Brocade and Cisco MDS SAN fabrics, NetApp FAS and FlashBlade, Pure Storage, Dell PowerVault, and HPE 3PAR. Customers are never constrained in their hardware or software choices. We do not push equipment or platform preferences because we have no vendor relationships to protect. Engineers undergo continuous training on new platforms, including AI accelerator integration with NVIDIA ConnectX-7 NICs and NVMe-oF storage fabrics.
  • Server certifications: Dell PowerEdge, HP/HPE ProLiant, Supermicro, Lenovo
  • Network OS: Cisco IOS-XE/NX-OS, Juniper JunOS, Arista EOS, Cumulus Linux
  • Storage: NetApp, Pure Storage, Dell PowerVault, HPE 3PAR, Brocade/Cisco MDS SAN fabric
  • No vendor affiliations. Engineers optimize for customer outcomes, not OEM relationships

Compliance and Security Controls for Smart Hands Engagements

Smart hands engineers operate inside regulated environments as a matter of course. All smart hands work is timestamped and documented with what was done, when, by whom, and what the outcome was. This audit trail supports change control requirements under PCI DSS 4.0 (applicable to payment card infrastructure), SOC 2 CC6.4 (physical access controls for Type II audits), and ISO 27001:2022 A.7 (physical and environmental security). Pre-engagement written authorization from the customer is required before any configuration change. Every Reboot Monkey engineer signs a non-disclosure agreement covering customer data, trade secrets, and facility security before their first engagement. Liability insurance is required. Engineers undergo criminal and employment history verification to the level specified by each facility's compliance program. Engineers are individually authorized by each colocation facility before accessing customer cages, including Equinix Smart Hands certification and Digital Realty badging. Work documentation is retained per customer contract terms, typically one to three years.
  • PCI DSS 4.0 change management documentation for payment infrastructure environments
  • SOC 2 CC6.4 physical access controls: timestamped logs, written authorization
  • ISO 27001:2022 A.7 physical security alignment: NDA, background checks, audit trail
  • Facility-level authorization required: Equinix Smart Hands, Digital Realty, and equivalents
  • Documentation retained 1 to 3 years per customer contract terms

Smart Hands Pricing Models

Reboot Monkey smart hands engagements are priced under three models depending on engagement volume and predictability. Per-incident pricing applies to ad-hoc, unplanned tasks: a single engagement is scoped, executed, documented, and billed. Block hours allow customers to pre-purchase 4- or 8-hour engineer blocks for planned deployments, reducing per-task friction and guaranteeing availability for specific maintenance windows. Retainer arrangements are structured for organizations with ongoing smart hands requirements across multiple facilities, providing priority access, a named account team, and volume-based pricing. Travel costs for engagements outside primary hub cities are stated separately. Contact the Reboot Monkey team for a quote based on your facility locations, task types, and volume.
  • Per-incident: ad-hoc engagements, single task, billed on completion
  • Block hours: pre-purchased 4- or 8-hour engineer blocks for planned deployments
  • Retainer: priority access, named account team, volume pricing for ongoing requirements
  • Travel costs stated separately for engagements outside primary hub cities

Why Use Reboot Monkey Instead of Facility-Provided Smart Hands?

Most colocation facilities offer hands-on support through their own operations teams. There are three structural reasons why Reboot Monkey delivers better outcomes for complex configuration work. Reboot Monkey engineers are certified infrastructure engineers, not facility generalists. Facility operations staff manage the building. They are not trained to configure BGP sessions or troubleshoot SAN fabrics. When a task requires Layer 2/3 expertise, facility baseline staff are often not equipped to deliver it. Reboot Monkey has no facility affiliation. A facility technician works for the datacenter operator. Their priorities are shaped by the facility's interests. Reboot Monkey works for you. When a cross-connect is delayed or a facility process adds friction, we escalate on your behalf. A single Reboot Monkey contract covers every facility in your estate. Hardware in Equinix Frankfurt, Digital Realty London, and NTT Tokyo is managed through one team. No per-facility onboarding, no separate vendor for each operator.
  • Tier 3 certified engineers vs. facility generalist staff for Layer 2/3 work
  • No facility affiliation: Reboot Monkey represents customer interests exclusively
  • Single contract covers every colocation facility in your global estate
  • Works inside Equinix, Digital Realty, NTT, CyrusOne, Coresite, and all other operators

Smart Hands: Frequently Asked Questions

What is the difference between smart hands and remote hands?

Remote hands covers Layer 1 physical tasks: power cycling, cable identification, visual inspection, and connecting KVM consoles. Smart hands covers Layer 2/3 configuration work: OS installation, firmware updates, NIC driver configuration, VLAN tagging, BGP session setup, and SAN zoning. These tasks require a certified engineer on-site making configuration decisions, not just following a physical checklist. If the task involves logging into a device CLI or editing a configuration file, it is a smart hands task.

Which operating systems does Reboot Monkey install?

Reboot Monkey engineers install Ubuntu Server 22.04 LTS and 24.04, CentOS 7/8, CentOS Stream 9, RHEL 8/9, Debian 11/12, Windows Server 2022, Proxmox VE, and KVM/libvirt. OS installation is performed via USB media or out-of-band management (iDRAC virtual media, iLO virtual media). Contact us if your required OS is not listed.

What certifications do Reboot Monkey smart hands engineers hold?

Reboot Monkey Tier 3 engineers hold certifications and hands-on experience across Dell PowerEdge, HP/HPE ProLiant, Supermicro, and Lenovo server platforms. Network proficiency covers Cisco (IOS-XE, NX-OS), Juniper (JunOS), Arista (EOS), and Cumulus Linux. Engineers are individually authorized by each colocation facility they work in, including Equinix Smart Hands certification and Digital Realty badging.

Does Reboot Monkey work inside any datacenter or only specific facilities?

Reboot Monkey is a facility-independent operator. Our engineers work inside any colocation facility worldwide, including Equinix, Digital Realty, NTT, CyrusOne, Coresite, Interxion, Ascenty, Teraco, and all other major operators. We are not affiliated with any facility operator. Our engineers complete each facility's individual access authorization process before their first visit.

What is included in the smart hands documentation package?

Every Reboot Monkey smart hands engagement produces a chain-of-proof documentation package: a task completion checklist, configuration change log with before-and-after diffs, performance baseline data, firmware version confirmation, pre and post photographs, and a written summary. The full package is delivered within 24 hours of task completion. This documentation supports audit requirements under PCI DSS 4.0, SOC 2 CC6.4, and ISO 27001:2022 A.7.

What is the response time for a smart hands request?

Priority-1 incidents carry a 4-hour on-site response SLA in cities where Reboot Monkey has deployed engineers. Non-urgent deployment tasks are typically scheduled within 24 hours. Planned deployments can be booked as 4-hour or 8-hour engineer blocks in advance, guaranteeing availability for specific maintenance windows. Response times in secondary markets depend on engineer dispatch from the nearest hub.

Can Reboot Monkey configure BGP sessions at internet exchanges?

Yes. BGP session configuration at internet exchanges is a core smart hands workload. Reboot Monkey engineers configure BGP peering at DE-CIX in Frankfurt, AMS-IX in Amsterdam, IX.br in Sao Paulo (which operates at 22+ terabits per second and connects more than 2,100 autonomous systems), VIX in Vienna, LINX in London, and JPIX in Tokyo, among others. Engagements include route server submission, AS-path filter setup, BGP community configuration, and prefix-list validation.

What compliance frameworks does Reboot Monkey's smart hands process support?

Reboot Monkey's smart hands delivery processes align with PCI DSS 4.0 (change management documentation for payment infrastructure), SOC 2 CC6.4 (physical access controls for Type II audits), and ISO 27001:2022 A.7 (physical and environmental security). All work is timestamped, all changes are documented, and all engagements require prior written authorization from the customer before any configuration is made.

Request a Quote