Prerequisites for Integrating GigaVUE V Series Nodes with NSX-T

This section describes the requirements and prerequisites for configuring the NSX-T. Refer to the following section for details.

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 .

Network Firewall Requirements for NSX-T

Following are the Network Firewall Requirements for GigaVUE V Series Node deployment.

Source Destination Source Port Destination Port Protocol Service Purpose

GigaVUE‑FM

NSX-T Manager

Any (1024-65535)

443

TCP

https

Allows GigaVUE-FM to communicate with vCenter and NSX-T.

vCenter

GigaVUE‑FM

GigaVUE V Series Node

Any (1024-65535)

8889

TCP

Custom API

Allows GigaVUE-FM to communicate with GigaVUE V Series Node

Administrator

GigaVUE-FM

Any (1024-65535)

443

TCP

https

Management connection to GigaVUE‑FM

22

ssh

Administrator

GigaVUE V Series Nodes

Not Applicable

22

 

ssh

Troubleshooting GigaVUE V Series Nodes.

GigaVUE‑FM

GigaVUE V Series Node

Any (1024-65535)

5671

TCP

Custom TCP

Allows GigaVUE-FM to receive the traffic health updates with GigaVUE V Series Node

Remote Source

GigaVUE V Series Node

Custom Port(VXLAN and UDPGRE),N/A for GRE

4789

UDP

VXLAN

Allows to UDPGRE Tunnel to communicate and tunnel traffic to GigaVUE V Series Nodes(Applicable for Tunnel Ingress option only)

N/A

IP 47

GRE

4754

UDP

UDPGRE

GigaVUE V Series Node

Tool/ GigaVUE HC Series instance

Custom Port(VXLAN),N/A for GRE

4789

UDP

VXLAN

Allows GigaVUE V Series Node to communicate and tunnel traffic to the Tool

N/A

IP 47

GRE

GigaVUE V Series Node

Tool/ GigaVUE HC Series instance

N/A

N/A

ICMP

echo Request

Allows V Series node to health check tunnel destination traffic (Optional)

echo Response

GigaVUE V Series Node

GigaVUE‑FM

Any (1024-65535)

5671

TCP

Custom TCP

Allows GigaVUE V Series Nodes to communicate the traffic health updates with GigaVUE‑FM

GigaVUE-FM

External Image Server URL

Any (1024-65535)

Custom port on web Server

TCP

http

Access to image server to image lookup and checks, and downloading the image

NSX-T Manager

vCenter

NSX-T Manager

GigaVUE-FM

Any (1024-65535)

443

TCP

http

When using GigaVUE-FM as the image server for uploading the GigaVUE V Series Image.

vCenter

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.

Required VMware Virtual Center Privileges

This section lists the minimum privileges required for the GigaVUE‑FM user in Virtual Center.

The following table lists the minimum required permissions for GigaVUE‑FM to manage the virtual center user with roles specified above.

Category

Required Privilege

Purpose

vApp

vApp application configuration

V Series Node Deployment

Virtual machine

Interaction

■   Power on
■   Power Off
V Series Node Deployment
Used to power on and power off GigaVUE V Series Node.