Is that a bird’s nest or is it spaghetti? Have you ever asked that question when looking into a IT wiring closet? At some point in your tenure as a network manager, you’ve likely been asked to inventory a network and create a network topology diagram.

For new networkers, Spanning Tree Protocol (STP) can be an intimidating topic. Many old-timers speak of spanning-tree in ominous tones, recounting the time when a “spanning-tree loop” brought down the network. Some managers strictly forbid anyone from changing anything related to the spanning tree, fearing a resulting service interruption. Some of the fear surrounding spanning trees is likely based on bad experiences, but some are based on ignorance—at least partly.

Let me start by saying that spanning tree is a Good Thing. It saves you from loops, which will completely shut down a network. But it has to be configured properly to work properly. I can’t count the number of times I’ve had a client call me, desperate with a terribly broken network, and I’ve responded, “Sounds like a spanning tree problem.” There are many ways things can go wrong with spanning tree. In this article, I’ve collected six of the recurring themes.

With numerous options available for network monitoring, finding the right fit for your business can be a daunting task. It’s essential to sift through the noise and focus on what truly matters: a solution that meets your organization’s specific needs. PeerSpot, an enterprise buying intelligence platform, offers valuable insights into how various solutions, including Auvik Network Monitoring, perform in the real world.

For DevOps and platform teams working with containers and Kubernetes, reducing downtime and improving security posture is crucial. A clear understanding of network topology, service interactions, and workload dependencies is required in cloud-native applications. This is essential for securing and optimizing the Kubernetes deployment and minimizing response time in the event of failure.

Choosing the right network monitoring tool is important for keeping your network running smoothly. But, when it comes to choosing the right tool, the decision often boils down to two primary options: open-source network monitoring and paid solutions. Each comes with its unique set of advantages and challenges, making the choice dependent on your specific needs and circumstances.

In RPKI, determining when exactly a ROA expires is not a simple question. In this post, BGP experts Doug Madory and Fastly’s Job Snijders discuss the difference between the expiration dates embedded inside ROAs and the much shorter effective expiration dates used by validators. Furthermore, we analyze how the behavior effective expiration dates change over time due to implementation differences in the chain of certificate authorities.

As the demand for cloud services continues to grow, ensuring security, compliance, and reliability remains paramount, especially for government entities and affiliated sectors. Megaport is meeting these critical needs with its recently expanded network in Canberra, providing robust and secure connectivity options for such users.

Imagine you are hosting a lavish buffet and have prepared a wide variety of dishes. It is a common tendency of some guests at dinner parties to pile their plates with food, leaving little for others to consume. To ensure that everybody receives a fair share of food and that the buffet doesn’t run out too quickly, you decide to implement a “plate size restriction” policy.