14 Essential Network Troubleshooting Tools
At Interop ITX, troubleshooting expert Mike Pennacchi discussed the tools every network engineer needs.
At Interop ITX, troubleshooting expert Mike Pennacchi discussed the tools every network engineer needs.
CiscoLive starts today and so do my presentations. If you have ever wondered what I’m thinking about right prior to a presentation…. I am imagining a small and beautifully wrapped gift that I want to give to each and every person in the audience. That is what I am doing. I am “Focusing on the Gift”.
Have I always done that? LOL. Uh… no. But fortunately I don’t think my 2006 Networkers presentation on EIGRP is available on video. Otherwise I think I’d be truly embarrassed. Why? Because it was my first Networkers/CiscoLive presentation and I was beyond belief nervous. Worried if I’d do okay… worried if you were enjoying the session… oh the list goes on and on as to everything I was thinking and worried about.
And then I realized something. You know what? It really isn’t about me at all. I am just a vehicle. It is all about “The Gift”. So in 2007 I went out and bought a tiny little Christmas tree sized ornament of a perfectly wrapped gift box. Small enough that I could hide it up on the stage Continue reading
Recently I attended a workshop organised by the Open NFP organisation about Data Plane acceleration. The primary goal of the workshop was to get students and researchers (why was I there you may think) familiar with the P4 programming language.
P4 is a programming language created to simplify writing data planes for networking use cases. Recently the P4-16 spec was released and could be considered a mature version of the language.
Now I’m not a hardcore developer. I know my way around in Python, GoLang and C#, but I never wrote anything more low level like C. P4 is created a little bit like GoLang, where I do not mean it as comparison, but as an architecture. P4 is designed so you only need to focus on the actual networking features that you want to make available on the hardware you are programming it for. Then when you compile it, it will generate runtime code for your hardware. Or as the creators explain it:
At one level, P4 is just a simple language for declaring how packets are to be processed. At another level, P4 turns network system design on its head.
There is no need to worry on low Continue reading
![]() |
Fig 1.1-Sample Topology Cisco VSS Physical and Logical View |
Lately I’m looking more and more into Python, with respect to automation implementations useful for network engineers. In the learning process I’ve used different materials, like the excellent video trainings Python Programming for Network Engineers from David Bombal which are available free on Youtube.
This training in particular relies on a Ubuntu Docker image in order to support Python learning following interaction with Cisco devices in GNS3. Everything is great, just that the image doesn’t contain all necessary tools (like Paramiko, Netmiko, Ansible…). As you can guess, whenever you close / open the Project in GNS3, all the installed packages installed in the Ubuntu Docker image are gone.
Since we’re talking automation, I got bored to install the necessary tools everytime I wanted to start a new project or I had to close GNS3 for some reason. I’ve tried to find a Docker image that suits my needs, but I couldn’t (please point me to one if you know it).
So, I’ve build a Docker image, based on Ubuntu 16.04, which contains the necessary tools to start learning Python programming oriented for network engineers:
every expert in cryptography doesn't know thisOh, sure, you can find fringe wacko who also knows crypto that agrees with you but all the sane members of the security community will not.
This is an update to my original post that can be found here: LINK I just received an e-mail (below) in …
The post CCIE/CCDE NetVet Reception Rescheduled appeared first on Fryguy's Blog.
Back in April, we talked about a feature called Explicit Congestion Notification (ECN). We discussed how ECN is an end-to-end method used to converge networks and save money. Priority flow control (PFC) is a different way to accomplish the same goal. Since PFC supports lossless or near lossless Ethernet, you can run applications, like RDMA, over Converged Ethernet (RoCE or RoCEv2) over your current data center infrastructure. Since RoCE runs directly over Ethernet, a different method than ECN must be used to control congestion. In this post, we’ll concentrate on the Layer 2 solution for RoCE — PFC, and how it can help you optimize your network.
Certain data center applications can tolerate only little or no loss. However, traditional Ethernet is connectionless and allows traffic loss; it relies on the upper layer protocols to re-send or provide flow control when necessary. To allow flow control for Ethernet frames, 802.3X was developed to provide flow control on the Ethernet layer. 802.3X defines a standard to send an Ethernet PAUSE frame upstream when congestion is experienced, telling the sender to “stop sending” for a few moments. The PAUSE frame stops traffic BEFORE the buffer Continue reading
The post Worth Reading: The root of a robust Internet appeared first on rule 11 reader.
Recent push by Microsoft highlights need to keep container OS platforms tight.