ISP Circuit Turn-Up and Acceptance Testing
A carrier saying a circuit is active does not prove that it is ready for production. TechRunz coordinates the provider, site contact and network team, validates the physical and logical handoff, and records evidence before traffic is migrated.
Make the handoff measurable
Define ownership, evidence, acceptance limits, escalation and closeout before dispatching technicians or scheduling a service window.
Scope, prerequisites and ownership
Start with the carrier order, circuit ID, service address, committed rate, handoff type, connector, VLAN, IP block, routing method and demarcation location. Confirm whether the provider supplies optics, a managed router or only an Ethernet handoff. Record the provider activation contact and the party authorized to open tickets.
Before dispatch, verify rack space, power, grounding, patching, firewall port, supported optic or copper interface and out-of-band access. A circuit can be delivered correctly and still be unusable because the customer-side equipment, cabling or configuration is not ready.
- Carrier order and circuit ID
- Handoff, addressing and routing
- Demarcation and responsibility boundary
- Activation and escalation contacts
Field execution and change control
Photograph and label the demarcation without exposing account data. Record equipment status, interface speed and duplex, optical levels when available, patch path and link errors. Apply the approved WAN, static route, BGP, NAT, VPN or SD-WAN configuration through a documented maintenance plan.
Preserve the previous circuit and configuration until acceptance and rollback criteria are met. When replacing service, identify public DNS, allowlists, VPN peers, hosted services and third parties that depend on the old addresses.
- Physical and optical status
- Approved WAN configuration
- Dependent services and allowlists
- Rollback preserved until acceptance
| Checkpoint | Measure | Evidence |
|---|---|---|
| Physical handoff | Link, errors and optical status | Photos and interface output |
| Service profile | Addressing, route, MTU and rate | Configuration and provider order |
| Performance | Throughput, latency, jitter and loss | Timestamped test exports |
| Resilience | Failover and restoration behavior | Event log and monitoring record |
Testing and exception management
Test from an appropriate wired endpoint and distinguish internet speed tests from provider Ethernet service testing. Compare multiple flows, directions and times when the service profile requires it. Capture latency, jitter, loss, errors, negotiated speed, MTU behavior, DNS and critical application reachability.
If results miss the agreed limits, repeat with a controlled test path and document the time, endpoint, method and raw output. Open the carrier case with the circuit ID and evidence; avoid accepting a vague speed screenshot as the only record.
- Wired, controlled test path
- Throughput, latency, loss and MTU
- Application and DNS checks
- Reproducible provider evidence
Closeout and operational handoff
For dual circuits or cellular backup, test both planned and unplanned failover, route changes, session impact and restoration. Confirm monitoring sees the correct public address, link state and performance. Record any manual intervention needed.
Deliver addressing and routing records, demarcation photos, test exports, carrier tickets, configuration backup, failover observations and the accepted service date. Keep credentials, full account numbers and private keys out of public or broadly shared documents.
- Primary and backup failover
- Monitoring and alert verification
- Accepted exceptions and owner
- Protected as-built package
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Prepare
Confirm site access, contacts, scope, prerequisites and acceptance limits.
Execute
Follow the method of procedure and record changes as work proceeds.
Validate
Measure results, capture evidence and resolve or clearly document exceptions.
Handoff
Deliver records, ownership, recovery details and next actions to operations.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site, circuit and equipment identifiers
- Access, maintenance window and contacts
- Method of procedure and rollback
- Acceptance tests and evidence format
- Escalation and final ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is an online speed test enough to accept a circuit?
No. It is one observation; acceptance also needs handoff, addressing, errors, latency, loss, routing and application checks.
Who should open a carrier trouble ticket?
The authorized account contact or an agreed project owner should open it with the circuit ID and measured evidence.
Should the old circuit be disconnected immediately?
Keep it available until migration, dependencies and rollback criteria are satisfied when the project allows overlap.
Can TechRunz test an Ethernet private line?
Yes, with a test plan matched to the ordered service and coordinated endpoints.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.