I know that I take a different approach to learning new things than most people. At least, I know my approach is different than the way people present them. The good news is that when I get something, I really get it. However, when looking at the juggernaut that is “Software-Defined X,” or even “programmability,” I know that I’m still a long, long way away from feeling like I have a handle on it.
When I wrote the previous blog post on some of the key “Open” terms were in programmability, I was overjoyed to find out that there were a few people who also had difficulty getting a grip on this too.
In other words, I’m not alone!
There is still a bewildering amount of information that I still need to learn, however, and it seems to me that if I resonated with a few people about these high-level topics, there are probably a few more who are curious about what lies beneath as well. Fortunately I work for a company (and with a lot of people) who have been willing to help me. Read More »
Tags: CLI, netconf, nexus, programmability, python, SDN
A subject very close to my heart at the moment is what skills I will need to have in order to support the Next Generation of Software Defined and Application Centric networks.
It is of no surprise that Networking like most other towers in IT has embraced abstraction as the way forward to provide levels of flexibility and agility never before seen in the Network.
What is perhaps a bit of a surprise, is the speed in which these new concepts are being developed and deployed. It seems like only last year terms like SDN were still viewed as “Way down the line” technologies. But here we are at the start of Q2 2014 and it seems like if you don’t already have an SDN plan you’re already behind.
So what skills will we need in order to design, support and deploy these new networks? Read More »
Tags: #ciscochampion, ACI, CLI, network engineer, Nexus 9000, software defined networks
The guys from No Strings Attached Show just published their podcast we sponsored featuring Jim Florwick yesterday and already the verdict is in: Jim Florwick is awesome.
For those of you who haven’t had the chance to download the podcast yet (What are you waiting for?! Download podcast) or you have a few extra minutes to scan a short blog to decide whether or not you want to download the podcast, I asked Jim what his key takeaways are when it comes to high density design.
Here are Jim Florwick’s 6 tips for HD network design (for the REAL meat, tune into the podcast):
- High density client environments are quite common with today’s users being very connected – today’s users are always connected. With planning, this can be managed quite successfully. Understand the limitations, be aware of how legacy requirements will affect the outcome, and set expectations accordingly. Efficiency is key and removing some of the blockers (legacy) first is essential.
- 802.11ac represents another quantum leap forward in technology and will eventually allow a much richer user experience. It is a transition that must be managed and balanced against your current mission requirements. Evaluate channel/bandwidth requirements carefully. Monitor the mix of client devices operating in your environment and update frequently. Read More »
Tags: 11ac, 802.11, 802.11ac, access point, antenna, bandwidth, Cisco, CLI, client environment, design guide, HD, high density, high density design, high density network, jim florwick, legacy requirements, Mhz, Network design, no strings attached show, OBSS requirement, podcast, RRM; DCA algorithm, technology, wireless design
“Boiled frog syndrome” refers to a fable that when you put a frog in hot water, it jumps out. However if you slowly heat up the water the frog is in, the frog will cook.
The number of features and associated CLI for networking equipment has increased gradually over the last 15+ years. Each feature is valuable in its own right, but the weight of all CLIs, all OSs, and all variations of deployment cannot be internalized by any human. The result: the concept of the über-CCIE is cooked.
The question is what displaces the CLI over time? It is argued by “good enough” network vendors that this complexity isn’t necessary. But considering most networking costs are operational costs, this argument can generally be discarded.
More articulate arguments are made by people who want to simplify overall network operations activities versus concentrating upon enhancements to CLI. Businesses don’t want to manage individual boxes; they would love to shed this complexity. Instead they would rather express their operational intents to their network, and let the network itself sort any box specific details.
Read More »
Tags: Autonomic, CLI, fex, OpenFlow, SDN