Open Ports in GigaVUE-FM
This appendix provides information about the open ports in GigaVUE-FM and also in the devices. Refer to the following sections:
Open Default Ports
The following table provides information about the default ports open in the firewall for GigaVUE-FM. The table is sorted by Protocol and then Port Number.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description | ||||||
|
80 |
HTTP |
GigaVUE-FM GUI |
Bidirectional traffic between Web Browser and GigaVUE-FM |
Used for redirecting the traffic internally to port 443. Note: You can choose to shut down port 80 for enhanced security. |
||||||
|
443 |
HTTPS |
GigaVUE-FM GUI |
Bidirectional traffic between Web Browser and GigaVUE-FM Bidirectional traffic between GigaVUE-FM and GigaVUE-VM. |
Used for normal GigaVUE-FM user interaction. |
||||||
|
389 |
LDAP |
AAA |
Bidirectional traffic between LDAP server and GigaVUE-FM |
Used for accessing and maintaining distributed directory information services over the Internet Protocol (IP) network. |
||||||
|
636 |
LDAP |
AAA |
Bidirectional traffic between LDAP server and GigaVUE-FM |
Used for secure LDAP protocol over SSL for accessing and maintaining distributed directory information services over the Internet Protocol (IP) network. |
||||||
|
1812/1813 1645/1646 |
Radius |
AAA |
Bidirectional traffic between Radius server and GigaVUE-FM |
Used for running the client/server protocol in the application layer. They can use either TCP or UDP as the transport protocol. |
||||||
|
49 |
TACACS |
AAA |
Bidirectional traffic between TACACS server and GigaVUE-FM |
Used for communicating with the authentication server in order to determine if you have access to the network. |
||||||
|
22 |
TCP |
SSH |
Bidirectional traffic between Putty and GigaVUE-FM |
|
||||||
|
514 |
TCP |
Logstash |
Unidirectional traffic from physical nodes to GigaVUE-FM |
Used for sending device log messages via SSL from devices to GigaVUE-FM. |
||||||
|
5672 |
TCP |
RabbitMq |
Unidirectional traffic from physical nodes to GigaVUE-FM |
Used for sending event notifications via SSL from devices to GigaVUE-FM. |
||||||
|
5671 |
TCP/SSL |
RabbitMq |
Unidirectional traffic from physical nodes to GigaVUE-FM |
Used for sending event notifications via SSL from devices to GigaVUE-FM. |
||||||
|
53 |
UDP |
DNS |
Bidirectional traffic between a DNS server and GigaVUE-FM |
Used to resolve Fully Qualified Domain Names (FQDNs). |
||||||
|
68 |
UDP |
DHCP |
Bidirectional traffic between GigaVUE-FM and DHCP server |
Used only if DHCP is enabled on the GigaVUE-FM appliance. |
||||||
|
123 |
UDP |
NTP |
Bidirectional traffic between a Network Time Protocol (NTP) server and GigaVUE-FM |
Used only if GigaVUE-FM is configured to use NTP. |
||||||
|
162 |
UDP |
SNMP |
Unidirectional traffic from managed appliances to GigaVUE-FM |
Used to process incoming traps sent from managed appliances to GigaVUE-FM. |
||||||
|
2055 |
UDP |
NetFlow |
Unidirectional traffic from managed Appliances to GigaVUE-FM |
Used for receiving NetFlow traffic. |
Open Ports for GigaVUE-FM Migration
The following table provides details about ports that must be open during GigaVUE-FM migration.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description |
||||||
|
443 |
HTTPS |
GigaVUE-FM GUI |
Bidirectional traffic between Web Browser and GigaVUE-FM |
Used for API and GUI access related operations. |
||||||
|
22 |
TCP |
SSH |
Bidirectional traffic between Putty and GigaVUE-FM |
Used for transferring configuration files between two instances of GigaVUE-FM. |
||||||
|
902 |
TCP/UDP |
ESXi Host |
Bidirectional traffic between VMware vCenter and ESXi hosts |
|
Open Ports for High Availability
The following table provides details about ports that must be open for GigaVUE-FM High Availability.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description | |||||||||
|
22 |
TCP |
SSH |
Bidirectional traffic between Putty and GigaVUE-FM |
|
|||||||||
|
80 |
TCP |
HTTP |
Bidirectional traffic between Web Browser and GigaVUE-FM |
Used for redirecting the traffic internally to port 443. Note: You can choose to shut down port 80 for enhanced security. |
|||||||||
|
443 |
TCP |
HTTPS |
Bidirectional traffic between Web Browser and GigaVUE-FM Bidirectional traffic between GigaVUE-FM and GigaVUE-VM. |
Used for normal GigaVUE-FM user interaction. |
|||||||||
|
514 |
TCP/UDP |
Shell/Syslog |
Unidirectional traffic from physical nodes to GigaVUE-FM |
Used for sending device log messages via SSL from devices to GigaVUE-FM. |
|||||||||
|
4369 |
TCP |
EPMD/RMQ |
Bidirectional traffic between RMQ members in cluster. |
Small additional process that runs alongside every RabbitMQ node and is used by the runtime to discover what port a particular node listens to. The port is then used by peer nodes. |
|||||||||
|
5671 |
TCP |
amqps |
Unidirectional traffic from physical nodes to GigaVUE-FM |
Used for sending event notifications via SSL from devices to GigaVUE-FM. |
|||||||||
|
9514 |
TCP |
Unknown |
Bidirectional traffic between a DNS server and GigaVUE-FM |
Used to resolve Fully Qualified Domain Names (FQDNs). |
|||||||||
|
25672 |
TCP |
RabbitMQ |
Bidirectional traffic between RMQ members in cluster. |
|
|||||||||
|
68 |
UDP |
DHCP |
Bidirectional traffic between GigaVUE-FM and DHCP server |
Used only if DHCP is enabled on the GigaVUE-FM appliance. |
|||||||||
|
162 |
UDP |
SNMP |
Unidirectional traffic from managed appliances to GigaVUE-FM |
Used to process incoming traps sent from managed appliances to GigaVUE-FM. |
Open Ports for Communication Between Members of GigaVUE-FM High Availability Cluster
The following table lists the ports that must be open for communication between the members of GigaVUE-FM High Availability cluster.
Note: These ports cannot be accessed by standalone GigaVUE-FM instances.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description |
|
8300 |
TCP |
Consul |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used To handle incoming requests from other agents. |
|
8301 |
TCP/UDP |
Consul |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used for inter-cluster communication over LAN. |
|
8302 |
TCP |
Consul |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used for inter-cluster communication over WAN. |
|
30865 |
TCP |
CSync2 |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used for Synchronization of files/directories across cluster. For example, Image files during GigaVUE-FM HA Upgrade. |
|
9300 |
TCP |
Elastic Search |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used for inter-cluster communication. |
|
27017 |
TCP |
MongoDB |
Bidirectional traffic between members in GigaVUE-FM cluster. |
Used for data replication across clusters and data access through GigaVUE-OS CLI. |
Open Ports in GigaVUE H Series Devices
The following table lists the open ports in GigaVUE-H series devices. GigaVUE-FM manages the devices using these open ports.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description |
|
22 |
SSH |
Device Management |
Bidirectional traffic between GigaVUE-FM and devices. |
Used for image download, configuration backup/restore operations |
|
80 |
HTTP |
Communication |
Bidirectional traffic between GigaVUE-FM and devices. |
Used for initial communication setup. Assumption is that HTTP redirect will be turned ON in all GigaVUE devices and FM will use HTTP(S) henceforth |
Open Ports in GigaVUE G Series Devices
The following table lists the open ports in GigaVUE-G series devices. GigaVUE-FM manages the devices using these open ports.
|
Port Number |
Protocol |
Service |
Traffic Direction |
Description |
|
22 |
SSH |
Device Management |
Bidirectional traffic between GigaVUE-FM and devices. |
Configuration backup/restore operations |
|
80 |
HTTP |
Communication |
Bidirectional traffic between GigaVUE-FM and devices. |
Used for initial communication setup. Assumption is that HTTP redirect will be turned ON in all GigaVUE devices and FM will use HTTP(S) henceforth |
|
443 |
HTTPS |
Communication |
Bidirectional traffic between GigaVUE-FM and devices. |
GigaVUE-FM to device communication |
