Specifications

W W W.EXTREMENETW ORKS.COM 3
SMARTMatch
A SMARTMatch policy addresses the requirement for
grouping multiple generic packet match rules.
A SMARTMatch rule allows:
- The filtering of tunnels, flows, or packets based on
configured n-tuple parameters
- The configuration of a set of actions - forward to an
egress destination or drop, Sample Flows, and Export
IPFIX metadata on tunnels/ flows/ packets identified by
the n-tuple match
A SMARTMatch rule supports flex-match, which allows
detection of specific regex or hex patterns in flows and
packets. Optionally, such flows or packets can be dropped
or forwarded to a configured egress. A flex match can be
pre-defined as a SMARTmatch alias and used within a rule.
A rule can include up to four aliases. In the vPB, masking
as an action is supported.
Virtual Packet Broker and Virtual TAP Specifications
The table below shows the specifications for the
qcow2 image. The KVM hypervisor on which the qcow 2
image is deployed must meet these requirements.
Extreme vPacket Broker
Specifications
Hypervisor KVM
KVM Hypervisor Requirements
CPU: 2 vCPU
RAM: 4GB
HDD: 16 GB
vNICs: 5
Driver: e10 0 0
Operating System
Cent OS release 7.2
Linux kernel version 3.10.0 -
123.el7.x86 64 or higher
Supported
CLI
REST
SNMP
Figure 2: Virtual Packet Broker Deployment Architecture