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

[Demo] Protecting the Core with High Speed Load Balancing

May 25, 2017

Watch our new Demo on High Speed Load Balancing

I recently presented a demonstration for Palo Alto Network's Fuel User Group on the importance of implementing high speed (10G/40G/100G) load balance at the Core of the Network.

Prior to beginning the demo, we surveyed the group and asked, "What speeds are you running at the core of your network today?" The majority of the group is running at 10G, which is what I hear from our customers as well.

So while 40G and 100G are exciting to discuss, we are going to keep this demo for a 10G network circuit. 

Watch and see how simple load balancing can be at the network core.

Challenge of Migrating or Expanding Inline Security to the Core

  • High speed links with low utilization
  • Increased Network Speeds
  • Encrypted data

Solution Overview

In this demonstration video we will show 10G high speed load balancing that utilizes Garland Technology's EdgeLens® bypass TAP with Packet Broker in combination with Palo Alto Network's NGFW. This solution is for high speed links with low utilization.

Watch the Demo Now!

Need an Encryption Solution?

Your NGFW/IPS can identify and select encrypted SSL/TLS and SSH traffic and then decrypt and deliver via the Garland bypass TAP solution to forensics and compliance systems - secure and in real time. Want to learn more? Contact a Garland Technology network designer.

 

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations
Contact Us

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