Whitebox switches make use of generic and generally inexpensive hardware along with a network operating system that can be purchased and installed separately. Often the hardware and software come from different vendors, and there are several reasons this practice is becoming more common especially in the data center. What I’m interested in lately is how this is relevant to the non-webscale enterprise.
I’ve been thinking a little bit about the Amazon S3 incident. Not really the incident, actually, but the responses to it. More than once I read something along the lines of “I’m sure that guy got fired” with regard to the engineer who entered the fatal command.
Sure, that’s kind of funny for a quick tweet or in the greater context of a blog post on change control, but for me, I’m not sitting at my desk shaking my head right now. Instead, I’m reminded about the times I did the exact same thing (on a much smaller scale) and will probably do it again.
About a thousand years ago, rather than configure routers, I taught high school English.
One day, instead of unpacking our favorite Shakespearean sonnet, I was sidetracked by a student who asked me how we know anything about electrons and how they orbit the nucleus of an atom. Apparently he asked his physics teacher the period before and got a pithy “electrons are the essence of a negativity.”
Tap everywhere. Tap everything. Trustworthy visibility is the key to network monitoring and security.
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.
Why aren’t our wired LANs more like WLANs? Wireless vendors have already been doing for years what switch manufacturers are only starting to get into in the last couple years. A rough comparison of a few attributes of typical wired and wireless networks shows striking differences in how we manage our LANs and WLANs.
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.
Being a good network engineer requires a strong technical skill set. In fact there’s an entire industry devoted to technical training in networking technologies. We know that persistent technical training is necessary to keep pace with constant changes in technology, so I’m sure we agree that technical proficiency is important for the network engineer. If you don’t have a deep understanding of how VPN technology works, you’ll have a very difficult time troubleshooting a site-to-site VPN without the help of some [unnamed] technical assistance center. But is that all that’s required for a successful career in networking?
Few fields require the continual professional development that IT does, but few fields offer the incredible rewards that a commitment to developing the skills of our trade can provide. Many factors come together to shape if, why, and how we advance in our field, and though I can speak only of my own experience, I believe the lessons I’ve learned from my journey so far may be of some value to others also on a similar path.
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.
How many times has one of your network projects come to a screeching halt (probably at 2am) because you didn’t have the right power plug or patch connector? Seems like such a trivial thing, but millions of dollars of equipment won’t do much more than look pretty in the racks until it’s all powered up and connected together.