GigaVUE V Series in VMware 

Prerequisites for Integrating V Series Nodes with vCenter

Few VMware vCenter versions are supported, with the GigaVUE V Series nodes hosted on ESXi hosts. Refer to the Release Notes for the hardware requirements on which VMware ESXi runs V Series Node.

Note:  To support internationalized characters in the VMware vCenter environment ensure that the vCenter character encoding is set to UTF-8.

The following are the prerequisites for integrating V Series nodes with ESXi:

  • VMware ESXi Standard Version must be either 6.7 u3 or 7.0.

  • VMware vCenter Server Version must be either 6.7 u3 or 7.0.

    Note:  Both VMware ESXi Standard Version and VMware vCenter Server Version must be same. For example. if the VMware ESXi Standard Version is 6.7 u3 , the VMware vCenter Server Version must also be 6.7 u3 .

  • ESXi hosts must have the minimum vCPU and memory resources.

  • GigaVUE-FM version 5.12.xx or later.

  • V Series 2.x device OVA image file.

  • All the target VMs must have VMware guest tools or Open VM tools if workload VMs is selected based on IP address.

  • Port number 8889 must be available for GigaVUE-FM to access V Series nodes.

The V Series 2 Node OVA image files can be downloaded from the Gigamon Customer Portal.

Network Firewall Requirements for ESXi

Following are the Network Firewall Requirements for V Series 2 node deployment.

Direction

Type

Protocol

Port

Source/Destination

Purpose

GigaVUE‑FM

Inbound
● HTTPS
● SSH

TCP
● 443
● 22

Administrator Subnet

Management connection to GigaVUE‑FM

Outbound

HTTPS

TCP

443

All ESXi hosts IP and vCenter IP

Allows GigaVUE‑FM to communicate with vCenter and all ESXi hosts and NSX-T managers to import the V Series OVA files

Outbound

Custom TCP Rule

TCP

8889

V Series 2 Node IP

Allows GigaVUE‑FM to communicate with V Series node

V Series 2 node

Inbound

Custom TCP Rule

TCP

8889

GigaVUE-FM IP

Allows GigaVUE‑FM to communicate with V Series node

Inbound
● UDP
● IP
● UDP (VXLAN)
● GRE
● UDPGRE
● 4789
● Protocol 47
● 4754

Ingress Tunnel

Allows to UDPGRE Tunnel to communicate and tunnel traffic to V Series nodes

Outbound

Custom UDP Rule

UDP (VXLAN)

VXLAN (default 4789)

Tool IP

Allows V Series node to communicate and tunnel traffic to the Tool

Outbound (optional)

ICMP

ICMP
● echo request
● echo reply

Tool IP

Allows V Series node to health check tunnel destination traffic

Recommended Instance Types for ESXi

The instance size of the V Series is configured on the OVF file and packaged as part of the OVA 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 ESXi hosts and the default size is Small.

Type

Memory

vCPU

Disk space

vNIC

Small

4GB

2 vCPU

8GB

1 Management interface,

1 Tunnel interface, and

8 vTAP interfaces

Medium

8GB

4 vCPU

Large

16GB

8 vCPU

Note: Refer to Support,  Sales, or Professional Services for deployment optimization.

Required VMware Virtual Center Privileges

This section lists the minimum privileges required for the GigaVUE-FM user in Virtual Center. You assign privileges to Virtual Center users by selecting Roles > Administration > Role, and then use the Edit Role dialog box in vCenter. Roles should be applied at the vSphere Virtual Center level and not the Data Center or Host levels.

The following table lists the minimum required permissions for GigaVUE-FM to manage the virtual center.

Category

Required Privilege

Purpose

Host

Configuration

  • Network Configuration

 

VSS Tapping

Inventory

  • Modify Cluster

Pin V Series Node to the host in cluster configurations. This prevents automatic migration.

Datastore

  • Allocate space

V Series Node Deployment

Distributed Switch

  • VSPAN Operation

VDS Tapping

Network

  • Assign network

  • Configure

V Series Node Deployment/VSS Tapping

V Series Node Deployment

Resource

  • Assign virtual machine to resource pool

V Series Node Deployment

vApp

  • Import

  • vApp instance configuration

V Series Node Deployment

V Series Node Deployment

Virtual machine

Configuration

  • Add new disk

  • Add or remove device

  • Modify device settings

 

V Series Node Deployment

V Series Node Deployment/VSS Tapping

Interaction

  • Connect devices

  • Power on

  • Power off

 

V Series Node Deployment

V Series Node Deployment

V Series Node Deployment

Inventory

  • Create from existing

  • Remove

 

V Series Node Deployment

V Series Node Deployment

Provisioning

  • Clone virtual machine

 

V Series Node Deployment

Prerequisites for Integrating V Series Nodes with NSX-T

Refer to the Release Notes for the hardware requirements on which VMware NSX-T runs V Series Node.

The following are the prerequisites for integrating V Series nodes with NSX-T:

  • VMware vCenter Standard Version must be 6.7 u3, and 7.0 with the required privileges. Refer to Required VMware Virtual Center Privileges for more information on vCenter privileges.

  • Before deploying V Series nodes through GigaVUE-FM, Service segments must be created in the NSX-T manager.

  • NSX-T versions must be 2.5.1, 2.5.2, 3.0, 3.0.2, 3.1.2. If you have other versions, please contact Gigamon support.

Note:  NSX-T is different than the ESXi implementation for hosting the V Series OVA file on an image server. In that you need to have an image server to host the V Series image file. The default http port supported is 80. However, if the image server listens on any port other than the default http port then, the port number should be provided in the image URL. For example: If the image server listens on port 8080, then the image URL should be http://IP_Address:8080/path_to_ova .

  • GigaVUE-FM version 5.12.xx or later.

  • V Series 2.2 device OVA image file.

  • Port number 8889 must be available for GigaVUE-FM to access V Series nodes.

Note:  You cannot have both GigaVUE-VM and V Series node visibility solutions deployed on the same vCenter. 

The V Series 2.x Node OVA image files can be downloaded from the Gigamon Customer Portal.

Network Firewall Requirements for NSX-T

Following are the Network Firewall Requirements for V Series 2 node deployment.

Direction

Type

Protocol

Port

Source/Destination

Purpose

GigaVUE‑FM

Inbound
● HTTPS
● SSH

TCP
● 443
● 22

Administrator Subnet

Management connection to GigaVUE‑FM

Outbound

HTTPS

TCP

443

All ESXi hosts IP and vCenter IP

Allows GigaVUE‑FM to communicate with vCenter and all ESXi hosts and NSX-T managers to import the V Series OVA files

Outbound

Custom TCP Rule

TCP

8889

V Series 2 Node IP

Allows GigaVUE‑FM to communicate with V Series node

V Series 2 node

Inbound

Custom TCP Rule

TCP

8889

GigaVUE-FM IP

Allows GigaVUE‑FM to communicate with V Series node

Inbound
● UDP
● IP
● UDP (VXLAN)
● GRE
● UDPGRE
● 4789
● Protocol 47
● 4754

Ingress Tunnel

Allows to UDPGRE Tunnel to communicate and tunnel traffic to V Series nodes

Outbound

Custom UDP Rule

UDP (VXLAN)

VXLAN (default 4789)

Tool IP

Allows V Series node to communicate and tunnel traffic to the Tool

Outbound (optional)

ICMP

ICMP
● echo request
● echo reply

Tool IP

Allows V Series node to health check tunnel destination traffic

Recommended Instance Types for NSX-T

The instance size of the V Series is configured on the OVF file and packaged as part of the OVA 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 NSX-T hosts and the default size is Small.

Type

Memory

vCPU

Disk space

Recommended

Traffic Volume

Small

4GB

2 vCPU

8GB

upto 2G

Medium

8GB

4 vCPU

8GB

upto 4G

Large

16GB

8 vCPU

8GB

More than 4G

For more specific throughput information on specific applications, please contact Gigamon Support.