<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2975524&amp;fmt=gif">
BLOG

Network Architect’s Guide to Ensuring Network Monitoring Visibility

December 10, 2015

The days of solving network problems by purchasing more bandwidth, extra storage or new servers are over. As network traffic demands increase rapidly, these traditional approaches to resolving network issues become costlier and more inefficient. Network architects are tasked with redesigning the network so that network monitoring is more agile. When your CIO tells you there have been performance concerns and you need to track down the root cause, what are you going to say?

What steps do you need to take to ensure monitoring visibility in your network?

You have two options. Under traditional network designs, you would tell the CIO that you need to work with IT to build a new network access point in the problem area—which could take days. If you design your network with visibility in mind, you could have a network analyzer hooked up in an hour. When it comes to designing architectures for efficient network monitoring, it all comes down to visibility with network TAPs.

Visibility is the Key to Root-Cause Analysis

When the network was compact—just a few appliances for security and minimal servers to take care of web traffic—monitoring wasn’t such an issue. However, traffic demands are forcing networks to become bigger and more complicated and it’s up to you to keep the design in check. If visibility isn’t top-of-mind from the start, network monitoring will be a tall task down the road.

Root-cause analysis is the main goal of network monitoring systems. Visibility is the most important factor in root-cause analysis because without access to every bit, byte and packet, there’s no way to determine where things are going wrong.

The only way to ensure visibility is to design the network with access points at key locations. Deploying network TAPs throughout the network is the visibility answer you need.

What Network TAPs Can Do for Network Monitoring 

Network architects can gain favor with security professionals by implementing network TAPs to ensure appliances can do their jobs effectively. But what about network monitoring? Network architects must implement network TAPs throughout their designs to make troubleshooting more convenient.

Deploying purpose-built network TAPs makes it easy for network analyzers to be plugged in at key points in the network, drastically reducing mean time-to-detection and mean time-to-repair. If you’re looking to gain points with your CIO, make sure network TAPs are an integral part of your network design so that when issues are reported, root-cause analysis can be quick and efficient without the hassles of makeshift access point creation.

The only question left to answer—where should network TAPs be placed to ensure easy network monitoring processes? If you want to learn more about proper network TAP placement to ensure monitoring visibility, download the Planned Visibility: Network Architecture Tips for Supporting Security and Monitoring Tools from the Start.

Don’t let your CIO down by telling them they’ll have to wait a few days to even start the root-cause analysis process. Access the white paper and learn how to use network TAPs to create a network architecture designed for modern demands.

Looking to add Network TAPs solution to your security deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do!

Network TAPS 101 Basics for IT Security engineers

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations

Heartbeats Packets Inside the Bypass TAP

If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.

If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.

While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.

Some of you may have noticed a flaw in the logic behind this solution!  You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.

Glossary

  1. Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.

  2. Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.

  3. Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.

NETWORK MANAGEMENT | THE 101 SERIES