Apstra, Incorporated isn’t focused on new features, more advanced silicon, or some new widget. Instead, they’re offering a different way to look at networking. Apstra offers an early form of intent-driven networking that abstracts network programmability and allows network engineers to configure intent rather than device features. We expect the network to behave in a specific way, so we configure our intent accordingly. I was very excited to meet the Apstra team at Networking Field Day 13, and they didn’t disappoint.
In a couple weeks I’ll be headed to sunny San Jose for Networking Field Day 13. If you’re not familiar with Networking Field Day and other Field Day events, check out their website, YouTube channel, Twitter feed, and LinkedIn page. Tech Field Day does a great job bringing technology influencers, bloggers, and craft beer enthusiasts together with some of the biggest and newest names in the tech industry.
I’m particularly interested in Apstra’s presentation on Thursday afternoon. I recently wrote an article about intent-driven networking, something of particular interest to me, so I’m really interested to hear what they have to say about their platform, the Apstra Operating System, or AOS.
Over the last few weeks I’ve noticed a few tweets and blog posts regarding the immaturity of network automation methods and the danger in utilizing those methods in production networks. Though I agree that processes always have room to mature and that wiggling wires in a production environment always poses some risk, I believe this new emerging narrative in social media makes several assumptions that aren’t necessarily true.
Network engineers like redundancy. It’s not that we just want double of everything – we want the networks we design and manage to be super fast, super smart, and super resilient. In the LAN and in the data center we’ve been logically joining network switches using technologies such as Cisco StackWise, the Virtual Switching System and Virtual Port Channels with fabric extenders in order to consolidate control and data plane activities and provide greater fault tolerance, easier management and multichassis etherchannel for path redundancy. These are great benefits, but they can be reaped only by proper design. Otherwise, an engineer may introduce more risk into the network rather than make it more resilient.
This post is a short, sweet and to the point copy/paste resource for configuring Cisco’s Virtual Switching System.
This week’s post will cover basic information gathering and configuration of Cisco Nexus switches. I’ll be using the 5500 series as my example and covering the basics without getting into features such as fibre channel, VSANs and that sort of thing.
A brief overview of Cisco Nexus switches.