Juniper networks, built by hand or built as code.

I'm Bill Wester, an independent network engineer based in Washington State, with 25 years on Juniper, F5 and Infoblox and a co-developer of the Terraform provider for Juniper Apstra. I do the work myself, with old-school craftsmanship: careful, documented and done right the first time. You work directly with me, on US time and in plain English, with no hand-offs to someone you've never met.

Core practices

Hands-on Juniper

Firewalls, switches and routers, configured, fixed and migrated at the CLI.

  • Juniper SRXVPNs that won't come up, chassis clusters, upgrades, policy cleanup and firewall migrations onto SRX.
  • Juniper EX and QFXCampus and data center switching on EX and QFX, from Virtual Chassis to EVPN-VXLAN fabrics, Mist-managed or CLI.
  • Juniper MistThe whole Mist platform: wireless design, EX switching and campus fabrics, SRX WAN Assurance and Marvis.
  • Juniper MX and M seriesEdge, core and peering routing on MX, plus migrations off aging M series routers.

Apstra and infrastructure as code

The same networks, defined in Terraform, kept in Git and deployed through a pipeline.

  • Apstra and EVPN-VXLANData center fabrics designed and run through Apstra, automated with the Terraform provider I helped write.
  • Network automationTerraform, Ansible, Python and Go for networks, written by someone who has shipped a production Terraform provider.

Where this experience comes from

Also

Case study: a multi-gigawatt AI campus network, from an empty site

For Phase 1 of Galaxy Digital's Helios campus I built an Apstra-managed EVPN-VXLAN fabric deployed entirely from Terraform, automated Infoblox DDI, a Mist-managed out-of-band network, and diverse dark-fiber paths with Ciena.

How the Helios network was built

Field notes

Write-ups of real problems and how they were fixed, with client details removed.

Have a network problem, or a build coming up?

Most engagements start with a 30-minute call. Tell me what you're working on.

Get in touch