Headcount: The Latest in Hirings, Firings And Retirings for March 2017
Lenovo hires a former Intel executive; VMware's CTO moves to Asia.
Reaction: Mend, don’t end, the IETF
Is it time for the IETF to give up? Over at CircleID, Martin Geddes makes a case that it is, in fact, time for the IETF to “fade out.” The case he lays out is compelling—first, the IETF is not really an engineering organization. There is a lot of running after “success modes,” but very little consideration of failure modes and how they can and should be guarded against. Second, the IETF “the IETF takes on problems for which it lacks an ontological and epistemological framework to resolve.”
In essence, in Martin’s view, the IETF is not about engineering, and hasn’t ever really been.
The first problem is, of course, that Martin is right. The second problem is, though, that while he hints at the larger problem, he incorrectly lays it at the foot of the IETF. The third problem is the solutions Martin proposes will not resolve the problem at hand.
First things first: Martin is right. The IETF is a mess, and is chasing after success, rather than attending to failure. I do not think this is largely a factor of a lack of engineering skill, however—after spending 20 years working in the IETF, there Continue reading
Mac Flooding Attack , Port Security and Deployment Considerations
This article is the 4th in Layer 2 security series. We will be discussing a very common layer 2 attack which is MAC flooding and its TMtigation “Port Security MAC limiting” If you didn’t read the previous 3 articles; DHCP snooping, Dynamic ARP Inspection, and IP Source Guard; I recommend that you take a quick […]
The post Mac Flooding Attack , Port Security and Deployment Considerations appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
AT&T Advances 5G Strategy by Snapping Up Straight Path for $1.6B
The deal builds AT&T’s arsenal of millimeter wave spectrum.
MPLS Quiz
MPLS (Multi Protocol Label Switching) quiz ! Learn while assessing your knowledge. This quiz is part of the MPLS Review Questions of my new version of CCDE Workbook. There are more than two hundred questions in it and you can have it from the website directly (PDF version) or from Amazon (Hardcopy). This quiz helps for many certification exams […]
The post MPLS Quiz appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
AT&T’s ‘Nirvana Stack’ Uses ODL Rather than Contrail
The open source community derides projects that aren't truly open as 'faux-pen-source.'
Getting Started with NSX Load Balancing
In my conversations with customers and peers, load balancing is becoming an increasingly popular discussion. Why you may ask? Simple, load balancing is a critical component for most enterprise applications to provide both availability and scalability to the system. Over the last decade we have moved from bare metal servers to virtual servers and from manual deployment of operating systems to using tools like Chef, Puppet, vRA or other custom workflows. In addition to the movement towards virtualization and the API being the new CLI, we are also seeing a movement to Network Functions Virtualization (NFV) where Virtualized Network Functions (VNF) such as routing, VPN, firewalls, and load balancing are moving to software. The value of automation, SDN, and NFV has been proven in the largest networks today and this migration to software has proven to have tremendous ROI. Many companies also want to leverage the same cost effective models. To get us started, here are the most common questions:
- Does NSX provide load balancing? Yes, NSX has a feature set that addresses the most common deployment requirements for load balancing in enterprises today.
- Do you charge more for NSX Edge Load Balancing? No, NSX Load Continue reading
Five things we’ve learned about monitoring containers and their orchestrators
This is a guest post by Apurva Davé, who is part of the product team at Sysdig.
Having worked with hundreds of customers on building a monitoring stack for their containerized environments, we’ve learned a thing or two about what works and what doesn’t. The outcomes might surprise you - including the observation that instrumentation is just as important as the application when it comes to monitoring.
In this post, I wanted to cover some details around what it takes to build a scale-out, highly reliable monitoring system to work across tens of thousands of containers. I’ll share a bit about what our infrastructure looks like, the design choices we made, and tradeoffs. The five areas I’ll cover:
-
Instrumenting the system
-
Relating your data to your applications, hosts, and containers.
-
Leveraging orchestrators
-
Deciding what to data to store
-
How to enable troubleshooting in containerized environments
For context, Sysdig is the container monitoring company. We’re based on the open source Linux troubleshooting project by the same name. The open source project allows you to see every single system call down to process, arguments, payload, and connection on a single host. The commercial offering turns all this data into thousands of Continue reading