Prerequisites for Integrating V Series Nodes with NSX-T
The following are the prerequisites for integrating V Series nodes with NSX-T:
- VMware vCenter Standard Version must be 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 segment must be created in the NSX-T manager.
- NSX-T version must be
- ESXi hosts must have the minimum vCPU and memory resources.
- GigaVUE-FM version must be 5.10.01 or later.
- V Series 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 Node OVA image files can be downloaded from Gigamon Customer Portal.
Network Firewall Requirements
Following are the Network Firewall Requirements for V Series 2 node deployment.
|
Direction |
Type |
Protocol |
Port |
Source/Destination |
Purpose |
||||||||||||||||||||||||
|
GigaVUE‑FM |
|||||||||||||||||||||||||||||
|
Inbound |
|
TCP |
|
Administrator Subnet |
Management connection to GigaVUE‑FM |
||||||||||||||||||||||||
|
Outbound |
HTTPS |
TCP |
443 |
All ESXi hosts IP, vCenter IP and NSX-T manager IP |
In ESXi platform, it allows GigaVUE-FM to communicate with vCenter and all ESXi hosts to import the V Series OVA files. In NSX-T platform, it allows GigaVUE-FM to communicate with vCenter for inventory collection and NSX-T manager for vseries service insertion /registration. |
||||||||||||||||||||||||
|
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 |
|
|
|
Ingress Tunnel |
Allows to UDPGRE Tunnel to communicate and tunnel traffic to V Series nodes |
||||||||||||||||||||||||
|
Outbound |
Custom UDP Rule |
|
|
Tool IP |
Allows V Series node to communicate and tunnel traffic to the Tool |
||||||||||||||||||||||||
|
Outbound (optional) |
ICMP |
ICMP |
|
Tool IP |
Allows V Series node to health check tunnel destination traffic |
||||||||||||||||||||||||
Recommended Form Factor (Instance Types)
The form factor (instance type) 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 form factors 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 |
|---|---|---|---|
| Small | 4GB | 2vCPU | 8GB |
| Medium | 8GB | 4 vCPU | 8GB |
| Large | 16GB | 8 vCPU | 8GB |
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 |
||||||
|
Virtual machine |
Interaction
|
V Series Node Deployment V Series Node Deployment |
