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

Network Visibility - The Rise of the Aggregation Layer

August 22, 2019

aggregation network garland technology

Sole reliance on SPAN ports for network visibility and monitoring has been on the decline for years. IT teams have realized the inherent limitations of SPAN ports and have shifted towards the traditional 3-tiered approach to network visibility, Physical Layer TAPs, Network Packet Brokers, and Tools.

Tier 1: Physical Layer TAPs

Network Test Access Points (TAPs) are hardware tools that allow you to access and duplicate network traffic. TAPs supply full line rate traffic and are never oversubscribed or rate limited. In the traditional 2-tier approach, the egress traffic from the TAPs is sent directly to NPBs.

Tier 2: Network Packet Brokers

Network Packet Brokers (NPBs) are responsible for efficiently funneling data from network TAPs and SPAN ports to each tool.  NPB’s were originally designed to replicate traffic for multiple tools while reducing the volume of traffic to each tool, ensuring each tool operates as efficiently as possible.  This is typically done through a combination of aggregation, replication and L2-L4 filtering. The groomed, tool specific traffic is sent out for processing.

>> Download Now: Aggregation - Adding Value Back Into Your Network and Maximise ROI [Free whitepaper]

 

Tier 3: Tools

Tools are responsible for processing and characterizing traffic of interest.  Common tools are built for application performance monitoring, security, and data forensics.

No Aggregation to NPB

3-Tiered Visibility Fabric


This approach has provided, and continues to provide, pervasive network visibility. So why do we see the approach to network visibility fabrics changing?  This 3-tiered approach was originally intended to increase the efficiency of monitoring and security tools. Tools continue to be the most significant cost associated with network monitoring and are continually evolving to be more capable.  This has driven the evolution of the NPBs to be extremely complex devices. NPBs now offer advanced features including L2-L7 filtering/classification, deduplication, metadata generation, and SSL/TLS decryption. With the well documented explosion of data, the NPB cost per port should have rapidly declined. The price has come down, but the reduction is not proportional to the increased number of ports needed to monitor growing networks.  This leads to either ballooning budgets for security and monitoring, or an increase in blind spots within the network.

The increase in data and complexity of NPBs have pushed the market towards a 4-tiered approach.  This brings the rise of the aggregation layer.

New Approach: Aggregation Layer

Tier 1: TAPs

Tier 2: Aggregation – Aggregators are devices designed to increase efficiency and port utilization of NPBs.  Considering the NPB cost per port, can we justify a direct connection with 60% utilization? In some cases, maybe, but the justification gets more difficult as we move towards the edge where it is common to see utilizations <5%. Aggregators condense multiple streams of low utilization links down to as few as one or two ports on the NPB.  Aggregators also capable of pre-filtering traffic prior to sending out to NPB’s for advanced filtering.

Tier 3: NPBs

Tier 4: Tools

Aggregation to NPB

Figure 2. 4-Tiered Visibility Fabric


Aggregators improve ROI by reducing the cost of network visibility. Whether it’s a new install or an upgrade of existing infrastructure the addition of Aggregators leads to a more efficient use of costly NPBs.  Take a simplified example: If your current NPB has 50% utilization on all ports, adding an aggregator can potentially free up half of your NPB ports. This pushes out the time to purchase new NPBs or allows you to now monitor parts of your network that may have previously been neglected. A purpose-built Aggregator should not exceed $1k/100G interface, making it 50-75% less expensive than a full-featured NPB.  With the cost savings and improved efficiency, it’s easy to see why most networks have shifted, or will shift, to this 4-tiered approach.

Important considerations when purchasing an Aggregator:

  1. Support for multiple speeds and media types, including Cisco 40G/100G BiDi
  2.  High density 1U form factor
  3. Selective aggregation based L2-L4 criteria
  4. N:1, 1:N, and N:N port mapping
  5. Remote management options
  6. COST

Looking to add an aggregation solutions to your next 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 Aggregation maximizes network visibility and optimize network packet broker ports

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