One of the most challenging aspects when studying for the CCDE practical is to find scenarios to practice with. It’s difficult to find a scenario that has enough background information, requirements and constraints to emulate the experience of the real practical. Writing a full scale scenario is very time consuming and challenging. You have to find a good story, make it believable and challenging enough. The scenario must also be somewhat realistic.
I’m happy to announce that my friend Martin Duggan has released a new scenario for the CCDE practical. Martin and I studied for the CCDE together and passed on the same day. Martin is well known in the industry and holds a CCIE in RS and works as a network architect at AT&T. He is a Cisco Press author and has authored the CCIE RS Practice Labs Bundle. I have been a technical reviewer for this scenario and based on my experience this is one of the best quality scenarios I’ve seen.
These are some of the things that I think Martin has done really well to make this scenario as realistic as possible.
Background information – The scenario contains more background information than some of the other Continue reading
It's Take 2 for the open source switching project.
Just in time for Hallo’ween, the lucky thirteenth post in the BGP code dive series. In this series, we’re working through the Snaproute Go implementation of BGP just to see how a production, open source BGP implementation really works. Along the way, we’re learning something about how larger, more complex projects are structured, and also something about the Go programming language. The entire series can be found on the series page.
In the last post in this series, we left off with our newly established peer just sitting there sending and receiving keepalives. But BGP peers are not designed just to exchange random traffic, they’re actually designed to exchange reachability and topology information about the network. BGP carries routing information in updated, which are actually complicated containers for a lot of different kinds of reachability information. In BGP, a reachable destination is called an NLRI, or Network Layer Reachability Information. Starting with this code dive, we’re going to look at how the snaproute BGP implementation processes updates, sorting out NLRIs, etc.
When you’re reading through code, whether looking for a better understanding of an implementation, a better understanding of a protocol, or even to figure out “what went wrong” on Continue reading
Over 90% of Microsoft's servers are based on OCP.
CenturyLink becomes a major fiber player.
ECOMP is involved too, of course.
(Cue the Halloween music)
Welcome to my crypt. This is the Docker crypt keeper speaking and I’ll be your spirit guide on your journey through the dangerous and frightening world of IT applications. Today you will learn about 5 spooky application stories covering everything from cobweb covered legacy processes to shattered CI/CD pipelines. As these stories unfold, you will hear how Docker helped banish cost, complexity and chaos.
Splunk was on a mission to enable their employees and partners across the globe to deliver demos of their software regardless of where they’re located in the world, and have each demo function consistently. These business critical demos include everything from Splunk security, to web analytics and IT service intelligence. This vision proved to be quite complex to execute. At times their SEs would be in customer meetings, but their demos would sometimes fail. They needed to ensure that each of their 30 production demos within their Splunk Oxygen demo platform could live forever in eternal greatness.
To ensure their demos were working smoothly with their customers, Splunk uses Docker Datacenter, our on-premises solution that brings container management and deployment services to the enterprise via an integrated platform. Images are Continue reading