Skip to content

Campus · WAN · SD-WAN · OT

Network infrastructure

A production network is not a shopping list of access switches. ianAsher designs the fabric, the WAN, and the ugly edges (plants, yards, oil-field sites) so applications stay up through a cutover.

Overview

Campus and data-center switching on Cisco Catalyst / Nexus and Arista EOS — leaf/spine when the traffic asks for it, collapsed core when it does not.

WAN, VPN, and SD-WAN chosen for the path, not the slide: ISR/Catalyst 8000, partner SD-WAN, or honest site-to-site when that is the right answer.

Segmentation, QoS, and multicast only where the application actually needs them. OT and SCADA stay off the office VLAN.

Documentation is part of the job: as-builts, change windows, and a named engineer who will still pick up after go-live.

Capabilities

  • Campus access, distribution, and core (PoE budgets, stacking, optics as line items)
  • WAN, SD-WAN, and industrial / oil-field networking
  • Routing (BGP, OSPF, and the IGP you already run) with resilience that matches the SLA
  • Segmentation, QoS, and multicast for voice, video, and plant traffic
  • IoT and SCADA-aware designs that do not flatten OT onto corporate Wi-Fi
  • As-built packages, lab validation, and cutover runbooks

Use cases

Texas campus refresh

IDF/MDF cleanup, Catalyst or EOS access, uplinks and optics quoted with the switch — not as a surprise.

Multi-site WAN

Branch, plant, and field locations with a WAN story that survives a fiber cut and a truck roll.

OT / oil-field

SCADA-adjacent networks, radios, and segmentation that keep pumps off the guest SSID.

Colo interconnect

Cross-connects and hybrid paths that make a Houston-area footprint feel like one environment.

Related catalog

Sample SKUs and sellable services in the categories that attach to this practice.

Full catalog →

Ready to scope this?

Design session or a written quote — same Montgomery bench.