KEY VISIBILITY ATTRIBUTES
Smart, drag-and-Drop, Intuitive GUI
Zero-Packet Loss Architecture
Overlapping Filter Rules Automatically Handled
by Visibility Engine
Multiple network links tool sharing (VLAN port tag)
Multiple network links tool sharing (MAC address)
Multi-path (multiple criteria for different data paths)
RESTful API* (Optional)
Role Based User Accounts
TACACS+, RADIUS Authentication
Event monitoring and Alarm Generation with SNMP Traps
Link Status Trap
Packet Counters and Statistics
WebUI for System Management
Packet Trimming* – Send only what security and monitoring tools need by cutting out the unnecessary information and reducing packet size
GRE Tunneling* – Encapsulate and de-encapsulate data. Origination and termination features.
Source Port Labeling with push P-Tag operation.
Optional Capabilities are hardware supported functionality that may require additional software licensing and may be provided with future software versions.
Three Stages of Filtering – Filter rules may be applied to ingress, dynamic, and/or egress traffic
Counter Comparison – Ingress, Dynamic, Egress
Max # of General & Custom Rules- 3K*
Max # of Source IP Rules (unicast)- 3K*
Max # of Destination IP Rules (unicast)- 3K*
Max # of Multicast IP Rules (No wildcard / masking capability)- 3K*
Priority Based Filtering (PBF) provides ACL-like logic when filtering traffic.
VLAN Tagging – Track packets easily by adding VLAN IDs to packets based on the source (ingress) port and remove them as they leave a packet broker via exit (egress) ports.
VLAN Tagging per Port
Aggregation – Consolidate incoming traffic to optimize port usage and simplify filtering:
– 1 : 1
– 1 : Many
– Many : 1
Many : Many*
Replication – Replicate traffic to multiple dynamic filters (ingress) or to multiple tools (egress)
Load Balancing – Distributes traffic across tool ports
Load balancing Standard (2 Tuple & 4 Tuple)*
Maximum Ports per Load Balancing Group- 128
Command Line Interface Management
Current Firmware has 1k rules limit imposed to allow non-packet-loss configuration switching.
Total amount of suported rules can be increased up to 3k – this will influence load balancing features (as rules share same memory with load balancing) and will result in possible packet loss when configuration changes. Exact rule consumption is hidden from user and only percentage is shown as any Intersections between filters & maps produce additional rules.
In order to create Many to Many Aggregation user shall create Many-to-One group and attach it to Load Balancing group and one-to-many group to egress ports.
Current firmware supports 2-tuple/4-tuple load balancing. TCP/UDP protocolrs will be added to the further firmware versions