Session-based / Flow-aware Load Balancing increases user control of traffic distribution amongst multiple monitoring tools, increasing output capacity while maintaining session integrity. Packets from a unique session flow will be balanced to the same tool port, always, using up to 10 balancing criteria, e.g. source and / or destination MAC address, EtherType, IP address, TCP/UDP port, and GTP TEID. Standard Load Balancing allows users to balance traffic based on up to ten criteria.
Extended Load Balancing expands the ten criteria to twenty-two. Balanced flow options extend to include the inner layer 3 and/or layer 4 headers inside encapsulated packets, including GTP and MPLS encapsulated traffic. This removes the need to de-encapsulate the packets before load balancing.
VSS' load balanced output prevents oversubscription/packet loss (eg. monitoring 10 GigE traffic with Gigabit tools), maintains session delivery consistency across multiple monitor ports, and ensures an even traffic distribution across a group of monitor ports based on session criteria
In addition to the above, load-balancing groups help maintain a network's high availability by building advanced redundancy into user defined load-balancing groups. Load Balancing Groups provide automatic user-defined responses to tool failure, enabling high-availability and redundancy for balanced monitor output streams. Load balancing groups allow users to define which monitor ports, and in what order, are included in each load balancing group, and how a load-balanced group will behave when one or more of the ports in the load-balanced group goes down or become unavailable.
User-defined options are available in all VSS Distributed TAPs, with additional inline support for the Protector Series of products. |
|
|
 |
