Services

Design, prove it, then encode it.

Engagements are scoped around a failure mode or a build: a fabric, a service edge, a diverse path, or the automation that stops the next change from being typed by hand.

01

Data center fabrics

VXLAN BGP EVPN, multi-site fabrics, Nexus, and Cisco ACI. Migrations and anycast gateway designs that are rehearsed before the cutover window.

02

Service provider architecture

L2VPN and L3VPN, MP-BGP policy, traffic engineering, and customer handoff standards. Includes global service provider L2VPN service architecture.

03

Optical and path diversity

DWDM and optical transport read against the routed layer. Diverse spans, carrier diversity, and DR/BC so a single building or a single fiber is not the design.

04

Enterprise routing and edge

OSPFv2/v3, named EIGRP, BGP with route reflectors, DMVPN (IKEv1 and IKEv2, front-door VRFs), SD-WAN, and firewall policy that matches the traffic it is supposed to pass.

05

Industrial and OT networks

Segmentation between business and control systems along the Purdue model and ISA-95. High-availability designs for SCADA, DCS, and PLC connectivity, with change windows that respect uptime.

06

Network automation

Python and Netmiko, Ansible with Jinja, and REST APIs for Cisco ACI and SolarWinds. YAML as the source of truth, rendered configuration, and tests that run before a device is touched.

How an engagement usually runs

  1. Read the paths that exist today, including the one everyone hopes they will not need.
  2. Write the target design in plain language and in a lab topology.
  3. Where it will be repeated, put it in YAML and render the configuration.
  4. Leave diagrams, the source of truth, and a way to test the result.

Start with an email