When I created the Data Center Infrastructure for Networking Engineers webinar, I wanted to reach these goals:

• Understand the data center acronym soup;
• Build a conceptual framework of the data center technologies and solutions.

Every now and then I get feedback from a happy attendee telling me how the webinar helped them. Here’s what I got earlier this month:

Want to become Captain Catalyst and save Princess Cattools from the Junipers tribe that invaded IOS Kingdom? Alexander Harsbo created an IOS Adventures game that will keep you busy should you get bored at the beach.

Enjoy ;)

In mid-May, I ran an onsite network automation workshop, and the manager organizing the workshop for his team invited me to a dinner with his peers. Not surprisingly, they wanted to hear about the topics covered in the workshop, and as soon as I mentioned Network-Infrastructure-as-Code several of them said “yes, that definitely needs to be covered.”

The EVPN in the Data Center book by Dinesh Dutt, the author of EVPN Technical Deep Dive webinar and member of ipSpace.net ExpertExpress team has finally been published. It’s kept safe behind NVIDIA regwall; you can also access it through the O’Reilly website.

So many things have happened since I wrote “this is what we’re going to do in 2018” blog post. We ran

• An automation course and a data center course, resulting in three new modules in the automation course, and over 20 hours of fresh content
• Three workshops, two of them brand new and resulting in material for VMware NSX Deep Dive and AWS Networking webinars (both coming in early autumn).

We also did a ton of webinars:

On Tuesday I had the last webinar in spring 2018. One more online course session and it will be time for long summer break. In the meantime, we’re already planning the autumn events:

• We’ll start with Lean Start in Network Automation workshop in Zurich, Switzerland, on August 30^th. Register here.
• Building Network Automation Solutions online course starts on September 20^th.

We also have the first webinars scheduled:

• We’ll start with two introductory webinars: SDDC 101 on August 28^th and SD-WAN Overview on September 4^th.
• The first session of technical deep dive into VMware NSX will be on September 11^th.
• Amazon Web Service Networking workshop was a huge success, and we’ll turn it into a webinar in early October.
• There will be an interesting math-focused webinar on October 8^th;
• Dinesh Dutt will talk about fabric troubleshooting in mid-November;

You can attend all these webinars with an ipSpace.net webinar subscription.

Stumbled upon “Is Tech News Fake” article by Tom Nolle. Here’s the gist of his pretty verbose text:

When readers pay for news, they get news useful to readers.  When vendors pay, not only do the vendors get news they like, the rest of us get that same story.  It doesn’t mean that the story being told is a lie, but that it reflects the view of an interested party other than the reader.

High-quality content is not cheap, so always ask yourself: who’s paying for the content… and if it’s not you, you may be the product.

Full disclosure: ipSpace.net is funded exclusively with subscriptions and online courses. Some of our guest speakers work for networking vendors, but we always point that out, and never get paid for that.

During last week’s SIGS Technology Conference I had a keynote presentation about the three paths of enterprise IT.

Unfortunately, the event wasn’t recorded, but you can view the presentation here. Contact me if you have any questions, or Irena if you'd like to have a similar keynote for your event.

One of my readers asked me a question that came up in his business strategy class:

Why did routers and switches end up being vertically integrated (the same person makes the hardware and the software)? Why didn't they go down the same horizontal path as compute (with Intel making chips, OEMs making systems and Microsoft providing the OS)? Why did this resemble the pre-Intel model of IBM, DEC, Sun…?

Simple answer: because nobody was interested in disaggregating them.

A while ago I found an interesting analysis of HTTP/2 behavior under adverse network conditions. Not surprisingly:

When there is packet loss on the network, congestion controls at the TCP layer will throttle the HTTP/2 streams that are multiplexed within fewer TCP connections. Additionally, because of TCP retry logic, packet loss affecting a single TCP connection will simultaneously impact several HTTP/2 streams while retries occur. In other words, head-of-line blocking has effectively moved from layer 7 of the network stack down to layer 4.

What exactly did anyone expect? We discovered the same problems running TCP/IP over SSH a long while ago, but then too many people insist on ignoring history and learning from their own experience.