I read a lot of discussions about complexity in networking and IT today that include a large amount of FUD. Topics range from “we’ll all lose our jobs because abstraction” to “you can’t fix complexity” to “welcome robot overlords” ;-) Complexity is something that may be easy to move, even easier and to increment, hard to remove. For a clear definition of complexity read Navigating Network Complexity by Jeff Tantsura and Russ White.
White boxes and their impact on enterprise networking is a hot topic today, with many point of views. The last update from Dave Temkin, VP of Network Architecture ad Netflix, put more gasoline on the flames: **Update April 2018: the original tweet was deleted, the message was: Super proud of my team - today they removed the last “big expensive router” from our network; no more Cisco ASR or Juniper MX.
Today I passed exam 2V0-642 to update my VCP5-DCV and got VCP6-NV (NSX v6.2) I’ll share here what I used to prepare the exam. Learning Path I passed exam VCP5-DCV in 2015. At the time I expected to work more with datacenter technology and I needed a more in-depth knowledge of how virtualization works. After a couple of years I needed to pay the vendor tax a.
When a customer calls with a problem or request I often see a chance to investigate a technology, learn something new or apply random skills to find a creative solution. This time is about an ASA, customer noticed too much traffic on the Internet facing interface. Syslog, Netflow, bandwidth monitoring and any other useful tools are totally missing, only the old good CLI to help. The MVP We can get a list of all active connections from ASA with
In episode 13 of the Network Collective podcast around minute 26 Jordan Martin asks: Aren’t we all just following a trend? The discussion topic is how to mentor juniors in a learning path to grow their skills and be experts eventually. The question can be translated as: Are we creating fake (IT) news/trends or is it just (excessive) nerd enthusiasm? Bloggers, events, news Tech professional read every day about some new technologies promising to change the way we work, live and play.
This week I’ve attended the Network Automation Seminar organized by Reiss Romoli. The speaker was the great Ivan Pepelnjiak! I was happy to meet Ivan again after NFD16. At the event I joined old and new friends: Andrea, Nicola, Paolo and Tiziano. Are these networkers or programmers? ;) @ioshints @adainese @nmodena @ReissRomoli @Paolo_Lucente #networking pic.twitter.com/RwjX6h2Mng — Gian Paolo (@gp_ifconfig) October 19, 2017 Content is king In two days Ivan presented tools, solutions, concepts and a lot of use cases of network automation.
Day two of NFD16 with Cisco. The presentation was split in two parts. First part for Intersight, second part for Tetration. I’ll post here just a few thoughts about Intersight. Merakify all the servers! What’s Cisco Intersight? If you’re familiar with cloud-managed devices like Meraki the concept is quite similar. A Cisco server runs the Device Connector client that links to a central management portal that runs on Cisco DC SaaS.
Automation is today a word that can be both scaring and exciting at the same time. The scary part is often related to the question: will robots steal my job? Federico Pistono says that’s ok. We read articles about how many jobs will not exist anymore soon, and sometimes how new jobs will be create to support automation. The most advanced analysts try to predict how a society can survive with massive unemployment.
I read this post on Ivan’s blog this morning and as often happens it made me think. The key point is: figure out what your most pressing problem is. Who should do that? Let’s analyze the roles involved in a typical SMB or enterprise. Vendors Vendors have just one target: sell their products. They can’t really customize the product to every business needs so they try to convince the customer the problem their product solve is the problem you have.
Day two of NFD16 started with Apstra and their intent-based networking system. Intent concept is not as broad as SDN but still vendors have different views of this meaning. According to Apstra an intent is “the definition of the expected outcome”. The sum of the intents of a network is the source of truth. Read Sasha Ratkovic blog post about the definition of Intent Based Networking. The checklist he suggest can be very useful to compare different solutions and spot intent washing strategies.