Imposter syndrome is the topic du jour for blogs and podcasts, so I’m almost reluctant to write about it. However, I want to share something I realized about myself that breaks from the conversation at large about this popular subject.
As much as I love to call out a vendor on marketing nonsense, Ramesh Prabagaran, Director of Product Management at Cisco, made some compelling marketing statements about SD-WAN at Networking Field Day 19. In particular he said:
Deploying the new Cisco 9800-CL wireless controller is fast and easy, and by using the built-in workflows, a new wireless network can be deployed in only a few minutes. In this post, I’ll review how to deploy the virtual wireless LAN controller in VMware ESXi and stand up a very simple WLAN. We’ll also take a look at some potential gotchas and some noteworthy differences between how the new WLC is configured compared to the AireOS WLC.
Only a few years ago, Cisco tried their hand at a converged access wireless platform with, among other devices, the Cisco 5760 Wireless LAN Controller. To this day, I have nightmares about that box. It wasn’t fully functional, and it had huge code issues. Today, in spite of AireOS being a stable, highly functional, and well-known WLC platform, Cisco is trying it again with a range of WLCs in the 9300 and 9800 series.
However, will this brave attempt prove to have the same fate as the 5760?
This week I taught my last class as a part-time adjunct instructor at a community college. I’ve been there for six years – 12 consecutive semesters. Each term, alongside the actual curriculum, I incorporated my work experiences and lessons learned about the reality of working in IT. Making the class meaningful from a real-world perspective was very important to me.
For my very last class, I chose not to cover anything in the textbook or any of the bullets on the syllabus. Instead, I introduced my students to systems and network automation. What may seem old news to you and me was brand-new to my class, and I don’t believe this is the exception.
Recently I upgraded a customer’s wireless controllers to the latest Cisco 5520 WLCs, but because their environment had a mix of brand new access points and somewhat old ones, I had to use an outdated version of code that resulted in some weird client issues on the new APs.
Recently I was in the midst of setting up a simple two node Cisco ISE 22.214.171.1248 cluster and got to the stage when I registered the secondary node through the GUI of the primary. At that point, things wouldn’t work.
I’ve been an active part of the networking community on social media for only a few years. Before that I was a passive consumer of tweets, blogs, and videos. A previous manager inspired me to be more active, and very quickly after engaging directly with bloggers, podcasters, and engineers, the value of being an active participant became very clear to me.
Locating a wireless client in real time and viewing its location history in Cisco Prime Infrastructure is a little bit different with CMX than with MSE. In this post we’ll walk through the few steps to locate a wireless client among all your maps and then view its location history.
Not long ago, I needed to put a script together for a simple task, so I wrote something very brief in Python. When I say “wrote”, what I mean is I copied and pasted parts of scripts others had written and created some new monstrosity to get the job done.
Intent-based networking is a hot new topic in the networking industry right now, but what really is intent-based networking? Watch my video to find out more.
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.
Sometimes political, financial, or logistical hurdles determine how we solve networking problems. In these tricky situations we may not be able to solve the problem the way we’d prefer, but we still need to solve the problem.
In this post I’m going to look at how we can solve a WAN failover scenario when we have a default route learned from both of our service providers and a reachability problem via our primary ISP.
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.”
Cisco’s DMVPN Phase 3 protocol offers many benefits, but make sure you evaluate options before using OSPF. Read the rest of the article at Tech Target’s SearchNetworking site.
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.
There’s a new story being told in the networking industry. The CCIE isn’t what it used to be, and pursuing it doesn’t make as much sense as in years past. My initial response to this is simple: BALONEY.
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.
School’s out, but I can’t wait for the fall semester to start. I don’t even know what class I’ll be teaching, but I know it’ll be awesome, and it’s going to be the best class I’ve ever had.
How do I know this? A few reasons, actually.