Challenge: Adding additional aggregation
Adding more visibility into network traffic should be a goal for any IT organization. However, challenges like limited rack space, ever-growing port fees, and port limitations on core infrastructure and the cost of monitoring and security tools often make it easier said than done. As a result, IT leaders are left to find the most cost-effective ways to increase the number of monitored links in their network designs.
Using TAP Aggregation to improve efficiency
TAP Aggregation provides additional options for streamlining network traffic and adding value to your existing tools and packet brokers. Here are three common use cases:
AggregatorTAPs can be used to aggregate traffic streams down to one monitoring port to feed directly into the monitoring and security tools. This frees up high demand ports to add additional visibility to the tool, increasing the value to the solution.
Another advantage to aggregating traffic on a TAP link, is providing the same traffic to two tools. This provides additional visibility when multiple tools are needed in a solution.
Instead of feeding two tap ‘breakout’ ports into an aggregation layer. Aggregating the tapped links into the packet broker or aggregation layer further reduces the number of ports, allowing you to add more links to improve visibility, while streamlining high volumes of network traffic.
When designing with AggregatorTAPs note:
• AggregatorTAPs include portable 2:1, 1/2 rack 1U 4:1 (SPAN 8:1), or 1U / 2U modular TAPs 8:4 or 24:12 aggregation.
• While deploying TAP Aggregation, utilization on the network link must be <50%
• TAPs are set to Aggregation mode rather than tap 'Breakout' mode