GigaVUE V Series in OpenStack
This section describes the requirements and prerequisites for configuring the GigaVUE Cloud Suite for OpenStack. Refer to the following section for details.
| Minimum Compute Requirements for OpenStack |
| Recommended Instance Type for OpenStack |
| GigaVUE V Series in OpenStack |
| Network Requirements |
Minimum Compute Requirements for OpenStack
In OpenStack, flavors set the vCPU, memory, and storage requirements for an image. Gigamon recommends that you create a flavor that matches or exceeds the minimum recommended requirements listed in the following tables.
Requirements for V Series 1
|
Compute Instances |
vCPU |
Memory |
Disk Space |
Description |
|
G-vTAP Agent |
2 vCPU |
4GB |
N/A |
Available as rpm or Debian package. Instances can have a single vNIC or dual vNICs configured for monitoring the traffic. |
|
G-vTAP OVS Agent |
N/A |
N/A |
N/A |
Available as rpm or Debian package. |
|
G-vTAP Controller |
1 vCPU |
4GB |
8GB |
Based on the number of agents being monitored, multiple controllers will be required to scale out horizontally. |
|
V Series Node |
2 vCPU |
3.75GB |
20GB |
NIC 1: Monitored Network IP; Can be used as Tunnel IP NIC 2: Tunnel IP (optional) NIC 3: Management IP |
|
V Series Controller |
1 vCPU |
4GB |
8GB |
Based on the number of GigaVUE V Series nodes being monitored, multiple controllers will be required to scale out horizontally |
|
GigaVUE‑FM |
2 vCPU |
16GB |
2x 40GB |
GigaVUE‑FM must be able to access the controller instance for relaying the commands. Use a flavor with a root disk and an ephemeral disk each of minimum 40GB. |
Requirements for V Series 2
|
Compute Instances |
vCPU |
Memory |
Disk Space |
Description |
|
G-vTAP Agent |
2 vCPU |
4GB |
N/A |
Available as rpm or Debian package. Instances can have a single vNIC or dual vNICs configured for monitoring the traffic. |
|
G-vTAP Controller |
1 vCPU |
4GB |
8GB |
Based on the number of agents being monitored, multiple controllers will be required to scale out horizontally. |
|
V Series Node |
2 vCPU |
3.75GB |
20GB |
NIC 1: Monitored Network IP; Can be used as Tunnel IP NIC 2: Tunnel IP (optional) NIC 3: Management IP |
|
V Series Proxy |
1 vCPU |
4GB |
8GB |
Based on the number of GigaVUE V Series nodes being monitored, multiple controllers will be required to scale out horizontally |
|
GigaVUE‑FM |
4 vCPU |
8GB |
40GB |
GigaVUE‑FM must be able to access the controller instance for relaying the commands. Use a flavor with a root disk of minimum 40GB and an ephemeral disk of minimum 41GB. |
Recommended Instance Type for OpenStack
The instance size of the V Series is configured and packaged as part of the qcow2 image file. The following table lists the available instance types and sizes based on memory and the number of vCPUs for a single V series node. Instances sizes can be different for V Series nodes in different OpenStack VMs and the default size is Small.
|
Type |
Memory |
vCPU |
Disk space |
vNIC |
|---|---|---|---|---|
|
Small |
4GB |
2 vCPU |
8GB |
1 Management interface, 1 to 8 Tunnel interfaces |
|
Medium |
8GB |
4 vCPU |
||
|
Large |
16GB |
8 vCPU |
Network Firewall Requirements for OpenStack
|
Direction |
Ether Type |
Protocol |
Port |
CIDR |
Purpose |
|---|---|---|---|---|---|
|
GigaVUE-FM |
|||||
|
Inbound |
HTTPS |
TCP |
443 |
Any IP address |
Allows users to connect to the GigaVUE-FM GUI. |
|
Inbound |
IPv4 |
UDP |
53 |
Any IP address |
Allows GigaVUE-FM to communicate with standard DNS server |
|
G-vTAP Controller |
|||||
|
Inbound |
IPv4 |
TCP |
9900 |
GigaVUE-FM IP address |
Allows GigaVUE-FM to communicate with G-vTAP Controllers |
|
G-vTAP Agent |
|||||
|
Inbound |
IPv4 |
TCP |
9901 |
G-vTAP Controller IP address |
Allows G-vTAP Controllers to communicate with G-vTAP Agents |
|
V Series Proxy |
|||||
|
Inbound |
IPv4 |
TCP |
8890 |
GigaVUE-FM IP address |
Allows GigaVUE-FM to communicate with GigaVUE V Series Proxys. |
|
V Series 2 Node |
|||||
|
Inbound |
Custom TCP Rule |
TCP(6) |
8889 |
GigaVUE V Series Proxy IP address |
Allows GigaVUE V Series Proxys to communicate with GigaVUE V Series nodes |
|
GRE Traffic |
|||||
|
Inbound |
Custom Protocol Rule |
GRE (47) |
47 |
Any IP address |
Allows mirrored traffic from G-vTAP Agents to be sent to GigaVUE V Series nodes using the L2 GRE or VXLAN tunnel |
|
Outbound |
Custom Protocol Rule |
GRE (47) |
47 |
Any IP address |
Allows monitored traffic from GigaVUE V Series nodes to be sent to the monitoring tools using the L2 GRE or VXLAN tunnel |
|
VXLAN Traffic |
|||||
|
Inbound |
Custom UDPRule |
UDP |
Default port is 4789 and can be any port |
Any IP address |
Allows mirrored traffic from G-vTAP Agents to be sent to GigaVUE V Series nodes using the VXLAN tunnel |
|
Outbound |
Custom UDPRule |
UDP |
Default port is 4789 and can be any port |
Any IP address |
Allows monitored traffic from GigaVUE V Series nodes to be sent to the monitoring tools using the VXLAN tunnel |
Note: The Security Group Rules table lists only the ingress rules. Make sure the egress ports are open for communication. Along with the ports listed in the Security Group Rules table, make sure the suitable ports required to communicate with Service Endpoints such as Identity, Compute, and Cloud Metadata are also open.
Network Requirements
The following table lists the recommended requirements to setup the network topology.
|
Network |
Purpose |
|
Management |
Identify the subnets that GigaVUE‑FM uses to communicate with the GigaVUE V Series nodes and controllers. |
|
Data |
Identify the subnets that receives the mirrored tunnel traffic from the monitored instances. In data network, if a tool subnet is selected then the V Series node egress traffic on to the destinations or tools. |
