Building the Right Network
Andy Lapteff and Kevin Myers recorded an in-person AONE podcast episode while attending Tech Field Day NFD39. What started as a discussion about navigating relationships with networking vendors evolved into guidance on building the right network for the right reasons, and why many engineers begin with incorrect assumptions.
"Don't ask, 'What gear should I buy?' Ask, 'What problem am I solving?'"
That was one of Kevin's early impactful moments, establishing the foundation for the entire conversation.
Kevin explains that far too many networks are constructed backwards: prioritizing vendor relationships, equipment availability, or budgetary cycles rather than business objectives, technical specifications, and operational feasibility. He recommends engineers reverse their approach:
"Start with a blank sheet of paper. Design the network first. Then ask which vendor can support that design."
This perspective shift proves particularly valuable in modern networking, where SDN, cloud, whitebox, and overlay technologies have substantially broadened the design landscape.
The Multi-Vendor Balancing Act
Kevin addresses the complexities openly. Multi-vendor architectures can be necessary, though they carry costs.
"Every vendor you bring in adds a tax: on your time, your processes, your tooling, and your people."
The expense may prove justified when gaining essential features, licensing flexibility, or supply chain resilience. However, without proper automation, managing multiple vendors becomes operationally challenging. Kevin and Andy explore practical methods to manage this complexity using APIs, open standards, and tools like Ansible or Nornir.
They also examine the organizational challenge of transitioning operations teams from individualized "pet switch" approaches to standardized cattle-style management, noting this shift involves both culture and technology.
Whitebox: Buzzword or Business Advantage?
This episode provides whitebox networking fundamentals from someone with production experience at scale.
Kevin discusses:
- Why whitebox represents a strategic architectural choice beyond cost reduction
- How separating hardware from the network operating system enables flexibility
- Which organizations benefit most (ISPs, MSPs, large enterprises)
- Why whitebox isn't universally appropriate and warning signs your organization may not be ready
He also covers whitebox ROI calculations: perpetual licensing reductions to hardware lifecycle management. This reflects genuine field experience rather than theory.
Designing with Intent, Not Tradition
The essential insight: quality engineering means questioning defaults and declining purchases that don't align with actual network designs.
"The best engineers I know can explain not just what they did, but why they didn't do something else."
This episode suits any engineer who is:
- Building or redesigning networks
- Experiencing vendor lock-in or support challenges
- Investigating whitebox or SDN options
- Connecting business strategy with technical decisions
Whether commuting, installing equipment, or enjoying a quiet morning, this episode challenges preconceptions and strengthens design thinking.
Listen on Buzzsprout, Linktree, or your preferred podcast platform.**
Watch the video on YouTube.