Operations | Monitoring | ITSM | DevOps | Cloud

Auvik and Cherwell recently co-hosted an information-packed webinar to answer some important network integration questions facing network managers: How do we get ahead of our workload and how do we know where to start? Let’s look at some of the key takeaways from the webinar (you can watch here) on how to move from a proactive to a reactive network operation model, how network integration solutions can help put out fires faster, and when to incorporate tools to automate processes.

IT events and technology conferences, once mind-bogglingly big in-person learning and networking opportunities, have certainly changed a lot since 2020. What started out as optimistic postponing for safety concerns quickly transformed into a new reality of virtual-only presentations and even total event redesigns due to the coronavirus pandemic. Now a year later, the outlook seems the same: another cycle of virtual-only events. We have to ask, “Is this the new future for conferences”?

Network diagrams are not only handy to have, but provide a vital look at the network topology for your team, your company, and your peace of mind. Let’s look at what a network diagram is, and why it’s so important. A network diagram is, simply put, a schematic or map of your existing network that illustrates the nodes and their connections. Network diagrams are very useful at mapping out your elements and device interactions, as well as illustrating different network topology types.

The importance of network documentation becomes very clear when you have to sit down and troubleshoot a network from top to bottom. Or when there’s a changing of the guard at your company. New management wants to see what you’re doing with your network. Or new IT staff need to be brought up to speed quickly.

As an IT professional, chances are you’ve come across the phrase Please Do Not Throw Sausage Pizza Away while hearing about protocols, network design, and implementation issues. How about Or Please Do Not Touch Steve’s Pet Alligator? If these ring a bell then you’re on the right track: These are smart memory aids linked to the seven layers of the Open System Interconnection (OSI) model.

Network infrastructure mapping tools that help you maintain up-to-date maps can be the difference between quickly diagnosing a problem or wasting hours of your time. Similarly, network maps can help everyone in your organization better understand and optimize a network you inherit. In many cases, however, network maps contain stale information or don’t exist at all.

Have you ever used the term bandwidth? Probably. Have you ever used the term network throughput? Maybe. Have you used them interchangeably? Most likely. So let’s see where we get these mixed up. Namely, let’s look at the key differences between network throughput and bandwidth. And while we’re at it, let’s cover the fundamentals of throughput and how to measure it, so you can keep your network flowing efficiently and cleanly.

When the Domain Name System (DNS) was created in 1983 I imagine its creator Paul Mockapetris and his team had no idea that nearly 40 years later our interconnected world would be so reliant on the very simple, but critical, DNS network service. I have a love-hate relationship with DNS. I love all of the memes I see about how “It’s always DNS”, but I hate that it’s also true—I always forget to check that DNS is working correctly when troubleshooting network issues!

Drawing a good network diagram isn’t hard to make, but it can be distressingly rare. Even network engineers with years of experience often draw network diagrams that are jumbled and hard to understand. As a network administrator responsible for the network, it’s vitally important you have a detailed understanding of your network topology. Without this information, even basic troubleshooting can be unnecessarily difficult.

Drawing a good network diagram isn’t hard to make, but it can be distressingly rare. Even network engineers with years of experience often draw network diagrams that are jumbled and hard to understand.