WAN documentation for every circuit, tunnel and failover path — OC Security Audit
WAN documentation

WAN documentation for every circuit, tunnel and failover path

Circuit IDs, bandwidth, static IP blocks, SLAs, support lines, VPN peers and failover tests, recorded before the next outage instead of during it.

Call the carrier with the circuit ID already in hand — OC Security Audit
When the internet goes down

Call the carrier with the circuit ID already in hand

The first question every ISP asks is the circuit ID. A circuit register answers it, along with the account, the demarc location and the escalation path.

Know your backup link works because you tested it — OC Security Audit
Failover you have tested

Know your backup link works because you tested it

A second circuit only helps if failover is designed, tested and written down. We document the design and the test results.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote documentation & audits
Why it matters

The connections that leave your building need records too

WAN documentation records every connection between your sites, the internet and the cloud: ISP circuits, SD-WAN or MPLS links, site-to-site VPN tunnels, private cloud connections and the failover design that holds them together. It is the part of IT documentation people reach for when the office is offline and every minute counts.

In many businesses this information lives in a billing portal, an old email from the installer and the memory of one person. When the circuit drops on a Saturday, nobody knows the circuit ID, which modem is which, or whether the backup link is supposed to take over. A short register fixes that.

WAN records connect to the rest of the network documentation: each circuit lands on a firewall interface, each tunnel protects subnets from the IP address plan, and each provider is a vendor record with a support contact.

Two network engineers discussing internet circuit details in a data center
Circuit register

What WAN documentation records for every ISP circuit

One row per circuit, per site. Keep it with the vendor record and the firewall it connects to.

FieldWhat to recordWhy it matters
Provider and accountCarrier name, account number reference, the contract holder in your companyThe carrier will only talk to an authorized contact
Circuit IDThe provider’s circuit or service ID exactly as printed on the bill or labelThe first question support asks
Type and bandwidthFiber, cable, fixed wireless, cellular; download and upload speed as contractedKnow whether slow speed is a fault or the contract
Handoff and demarcWhere the provider’s equipment ends (room, rack, device), handoff type and the firewall port it connects toThe on-site tech finds the right box and cable
IP addressingStatic block and gateway, or DHCP; which public IP maps to which serviceFirewall and DNS changes after an ISP move go smoothly
SLAUptime and repair commitments as written in the contract, and how to claim creditsHold the carrier to what you are paying for
Support and escalationSupport line, portal, ticket hours, and the next level when the first one stallsEscalate instead of waiting in a queue
Contract datesStart, term, renewal and notice date, monthly cost ownerAvoid auto-renewal surprises and plan upgrades
Sample

Sample circuit register: Harborview Dental Group

Two sites, three circuits. Provider names are generic and every ID is made up.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
CircuitSiteProviderCircuit IDBandwidthHandoffAddressingRole
WAN1-HQIrvine officeFiber ISP AHDG-FIB-0412500/500 MbpsProvider ONT, closet A → FW-HQ-01 port 1/29 static · 5 usable IPsPrimary
WAN2-HQIrvine officeCable ISP BHDG-CBL-0187300/20 MbpsCable modem, closet A → FW-HQ-01 port 2DHCP · 1 dynamic IPFailover
WAN1-S2Second officeCable ISP BHDG-CBL-0233300/20 MbpsCable modem, front closet → FW-S2-01 port 11 static IPPrimary · VPN to HQ

Each row links to the vendor record (support line, portal, contract renewal date) and to the firewall interface it terminates on. All names, IDs and figures are fictional.

Beyond the internet circuit

SD-WAN, MPLS, VPN and cloud links: what to document for each

Each WAN technology has a few details that matter most when something breaks.

01

SD-WAN

The orchestrator or dashboard, which sites are enrolled, the underlay circuits at each site, application steering and failover policies, and who has admin access to the controller.

02

MPLS

Carrier, site circuit IDs, the routing between your edge and the carrier (static or BGP, with AS numbers), class-of-service settings, and the carrier’s network operations contact.

03

Site-to-site VPN

Both peer addresses, the protected subnets on each side, IKE version, encryption and hashing settings, the shared-secret or certificate reference in the vault, and how the tunnel is monitored.

04

Private cloud connections

Dedicated links to a cloud provider (for example Azure ExpressRoute or AWS Direct Connect) or cloud VPN gateways: circuit or connection ID, the cloud networks reached, routing and redundancy. Cloud-side settings are covered on the cloud documentation page.

Sample

Sample VPN tunnel table

Tunnel records show what each connection protects. Secrets stay in the vault; the table only points to them.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
TunnelLocal peerRemote peerProtected subnetsSettingsSecretMonitoring
VPN-HQ-S2FW-HQ-01 (WAN1-HQ)FW-S2-01 (WAN1-S2)10.20.0.0/16 ↔ 10.21.0.0/16IKEv2 · AES-256-GCMVault entry VPN-HQ-S2-PSKTunnel-down alert to IT
VPN-HQ-CLOUDFW-HQ-01 (WAN1-HQ)Cloud VPN gateway10.20.30.0/24 ↔ 10.50.0.0/22IKEv2 · AES-256-GCMVault entry VPN-HQ-CLD-PSKGateway health check

The non-overlapping prefixes (10.20, 10.21 and 10.50) come straight from the IP plan; overlapping subnets are a common reason a new tunnel will not route. All values are fictional.

Failover

Failover design and test records in four steps

STEP 1

Describe the design

Which circuit is primary, how failover is detected (link state, ping or SLA probe), what moves to the backup and what does not, and how traffic returns.

STEP 2

Plan the test

Pick a low-impact window, tell staff, list the checks: internet, phones, VPN to the second office, card terminals and cloud apps.

STEP 3

Record the result

Date, who tested, how long failover and failback took, what failed, and screenshots or log extracts as evidence.

STEP 4

Fix and repeat

Open a change record for each issue found, then retest. Keep every test record with the circuit register.

Sample entry (fictional): WAN1-HQ unplugged at 07:10. FW-HQ-01 moved traffic to WAN2-HQ; phones re-registered and VPN-HQ-S2 re-formed on the backup link. Card terminals needed a restart. Change record opened; retest scheduled.
Carrier escalation

A carrier escalation path your staff can follow

Outages rarely wait for business hours. Write the path down so anyone can start it.

For each provider, record the support line and portal, the hours of each support tier, the account PIN or verification method (as a vault reference, never in the document itself), and the next level to call when a ticket stalls, such as the account manager or the carrier’s escalation desk.

Add a short checklist for the caller: circuit ID, site address, demarc location, what the modem or ONT lights show, when the outage started, and whether the backup link took over. Log each outage with the ticket number and restore time. That log becomes evidence for SLA credit claims and for the next contract renewal.

Procedures like this belong with your other recovery steps; see runbooks and disaster-recovery documentation and our business continuity and disaster recovery services.

How we help

WAN documentation, reviewed or built for you

The IT Documentation Audit reviews your existing circuit records, VPN details and failover notes against the live firewall configuration and reports what is missing. The IT Documentation Build delivers the WAN circuit register, the tunnel table and the failover record, linked to your network diagram and firewall configuration documentation. Each package is $3,500 fixed, one-time; see IT documentation pricing.

Ali works on-site across Orange County and Southern California from Irvine, and remotely with multi-site businesses nationwide. Our work is read-only. If a failover test shows something to fix, IT Perfection can make the change.

Engineer typing on a laptop in front of a network rack
Related

Where to go next

Firewall configuration documentation

Rule base, NAT, remote-access VPN and configuration backups, each rule with a business reason and an owner.

Runbooks and disaster recovery

Step-by-step recovery procedures, restore order and contact trees that use the circuit register.

Ali Hassani, CISO, OC Security Audit
CISO-led

Guided by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali verifies each circuit against the firewall interface it lands on, so the register matches the cabling and not only the bill.

FAQ

Questions about WAN documentation

Where do we find our circuit ID?

It is usually on the monthly bill, the carrier’s online portal, a label on the modem or ONT, or the installation paperwork. We collect it from those sources during discovery and confirm it with the carrier record.

Should VPN shared secrets go in the WAN documentation?

No. The document should name the vault entry that holds the secret. Secrets belong in an encrypted vault with access logging, as described on our credential documentation page.

How often should we test WAN failover?

We suggest at least once a year, and after any change to circuits or firewall settings; adjust the schedule to your risk. What matters most is that each test is planned, recorded and followed up.

Do we need WAN documentation if we only have one office?

Yes. A single office still has at least one internet circuit, often a backup, and usually VPN connections to cloud services, vendors or remote staff. Those records shorten every outage.

Can you contact our carriers for us?

We gather and verify circuit details with your authorization, but your company stays the account holder. Carrier changes and repairs remain with your team, your MSP or IT Perfection.

Implementation partner

OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

IT Perfection managed IT
Network engineer holding a tablet in a server room

Be ready for the next internet outage

Tell us how many sites and circuits you have. Schedule a consultation and we will scope your WAN documentation on a 30-minute call.

Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.