Service 01 · Network infrastructure
Networks built to hold under pressure.
Enterprise, data center and tactical networks engineered by a CCIE-led, veteran-owned team that spent a decade keeping national-priority communications alive. Designed once, documented fully, defended by the engineers who built them.
steady state, all paths nominal, traffic on primary
A link dies, traffic pivots to diverse transport, and the network converges before anyone files a ticket. Illustrative.
- Years — national-priority comms
- 10+
- Capability domains
- 9
- Platform ecosystems
- 10
- CCIE Enterprise — on staff
- #62940
What we engineer
Nine domains. One discipline.
The same engineers carry a design from the campus core to a flyaway kit, so nothing is lost at the hand-offs between specialties.
- 01
Enterprise Networking
Campus, branch, and WAN architecture — routing, switching, segmentation, and lifecycle discipline.
- 02
Data Center Networking
Spine-leaf fabrics, EVPN/VXLAN, and interconnect designed for the workloads on top, not the SKU sheet.
- 03
Wireless
Surveyed, engineered Wi-Fi and point-to-point RF — designed from measurements, not floor plans.
- 04
Mobile Communications
Cellular and LEO bonded into redundant multi-WAN uplinks — Peplink-class transport for fleets, field teams, and platforms that move.
- 05
Tactical Networking
DDIL-ready, transport-diverse comms that treat disconnection as a design input, not a failure.
- 06
VPN Infrastructure
Site-to-site and remote access at scale — IPSec architectures, key management, and transport migrations.
- 07
Network Monitoring
Telemetry, flow analytics, and alerting tuned so the first sign of trouble isn't a user call.
- 08
Performance Testing
Baseline, load, and impairment testing that proves capacity claims before production traffic does.
- 09
Automation
Config pipelines, drift control, and infrastructure as code — the network as a system, not a set of devices.
Ten ecosystems, specified honestly
Cisco / Juniper / Arista / Aruba / Peplink / Fortinet / Palo Alto / Open Source / AWS / Azure
We specify what the mission needs, not what a partner program pays us to move.
Past performance
On the bench right now.
Client identities withheld by design. References available in conversation.
- NI-01In execution
SD-WAN / THEATER SCALE
Theater-level SD-WAN architecture
Cisco SD-WAN architecture and application-aware routing design for a theater-level air command — transport-diverse, policy-driven, and built for WAN conditions that are contested by default.
- NI-02In execution
HEALTHCARE / MIGRATION
900-bed hospital network migration
Access-layer modernization for a flagship academic medical center — legacy switching to Catalyst 9400/9300 on current IOS XE, tooling-driven config translation and validation, cutovers run against a hospital that never closes.
- NI-03Delivered
DATA CENTER / SECURITY
Data center firewall migration
Cisco ASA to Palo Alto migration for a defense contractor's data center — policy translation, staged cutover, and validation under change control.
- NI-04Delivered
VOICE / TRANSPORT
Enterprise voice transport migration
MPLS to IPSec migration of enterprise voice for a large defense contractor — with collaboration performance remediated in the same engagement.
Pedigree
Where the standard was set.
ETHRX’s network practice is led by a Marine Corps veteran and CCIE Enterprise architect who spent over a decade supporting senior leader communications for the Department of Defense, the Navy, Marine Corps, TSA, DHS and the Department of Energy: environments where a failing network was never an acceptable outcome. That standard is the baseline for every engagement we take.
Doctrine
Four rules we don't bend.
- 01
Engineering, not integration resale.
Every design is owned and defended by the engineer who built it — no channel margin deciding your architecture.
- 02
Documented and defensible.
Diagrams, configs, and rationale ship with the network. If we got hit by a bus, your network would not notice.
- 03
Designed for failure.
Every design assumes links die, power blips, and humans err — and is built to survive all three. You watched it converge at the top of this page.
- 04
Vendor-honest.
We specify what the mission needs across ten ecosystems — not what a partner program incentivizes us to move.
Related
- CapabilityWireless & Mobility
Secure connectivity that moves with the mission.
Explore - CapabilityAutomation & Orchestration
Infrastructure that builds, heals, and scales itself.
Explore - CapabilityTactical & Edge Communications
Comms that hold where the infrastructure doesn't.
Explore - ProductCHAOS — WAN Emulation
Our own T&E appliance — prove a design under impairment before production traffic does.
Explore
Next step
Built to hold. Proven under pressure.
Bring us an RFP, a napkin sketch, or a network that's already on fire. We work all three.
