Configuring Firewall Ports
To gain access to the installation from a remote client such as JDBC or Actian Director through a firewall, four ports will require opening.
The discovery port is fixed at 16902 and can be queried using a browser (for example, http://masterhost:16902/) or at the command line (iimgmtsvr list) to find out the command port.
The GCC server and DAS server ports can also be found from the messages in the error log:
grep TCP_IP $II_SYSTEM/ingres/files/errlog.log | sed -e 's/^.*IIGC/IIGC/g' -e 's/,.*, port/ port/g'| sort -u
IIGCC port VH (27712).
IIGCD port VH7 (27719).
Further information on the GCC and GCD ports can be found in the
Connectivity Guide and the community document
Finding-and-Managing-Ingres-and-Vector-TCP-IP-Ports.
TCP/IP Routing for Edge Nodes
If there is no access to the master node and firewall ports cannot be opened, but there exists a “gateway host” such as a Hadoop edge node, then you may consider setting up TCP/IP tunneling on the gateway host to provide access to the master node through the gateway node. This can be setup using the Linux built in firewall or through TCP/IP proxy software such as Balance.
Alternatively, if you want users to log into the edge node and then run client software from there to access the rest of the cluster, then you should install the Vector Client Runtime on this edge node, and create a virtual node (vnode) to connect to the VectorH master node from here, with appropriate IP address and user credentials. After that is done, a user can log into the edge node and connect to VectorH by using the double colon remote vnode syntax like this:
sql <vnode name>::<database name>