<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Configure the network</title>
    <link>/en/setup/set-up-on-premises/before-you-install/configure-network/</link>
    <description>Recent content in Configure the network on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/setup/set-up-on-premises/before-you-install/configure-network/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Setup: Reserved ports</title>
      <link>/en/setup/set-up-on-premises/before-you-install/configure-network/ensure-ports-are-available/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/setup/set-up-on-premises/before-you-install/configure-network/ensure-ports-are-available/</guid>
      <description>
        
        
        
&lt;p&gt;The install_vertica script checks that required ports are open and available to Vertica. The installer reports any issues with identifier &lt;code&gt;N0020&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;You can also verify that ports required by Vertica are not in use by running the following command as the root user and comparing it with the ports required, as shown below:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ ss -atupn
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;firewall-requirements&#34;&gt;Firewall requirements&lt;/h2&gt;
&lt;p&gt;Vertica requires several ports to be open on the local network. Vertica does not recommend placing a firewall between nodes (all nodes should be behind a firewall), but if you must use a firewall between nodes, ensure the following ports are available:&lt;/p&gt;

&lt;table class=&#34;table table-bordered&#34; &gt;



&lt;tr&gt; 

&lt;th &gt;
Port&lt;/th&gt; 

&lt;th &gt;
Protocol&lt;/th&gt; 

&lt;th &gt;
Service&lt;/th&gt; 

&lt;th &gt;
Notes&lt;/th&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


22&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


sshd&lt;/td&gt; 

&lt;td &gt;

Required by &lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/admin-tools/&#34; title=&#34;OpenText&amp;amp;trade; Analytics Database Administration Tools provides a graphical user interface for managing the database.&#34;&gt;Administration tools&lt;/a&gt; and the &lt;a href=&#34;../../../../../en/mc/getting-started-with-mc/creating-cluster-using-mc/use-mc-cluster-installation-wizard/&#34;&gt;Management Console Cluster Installation&lt;/a&gt; wizard.&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


4803&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/spread/&#34; title=&#34;An open source toolkit used in OpenText&amp;amp;trade; Analytics Database to provide a high performance messaging service that is resilient to network faults.&#34;&gt;Spread&lt;/a&gt;&lt;/td&gt; 

&lt;td &gt;

Client connections&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


4803&lt;/td&gt; 

&lt;td &gt;


UDP&lt;/td&gt; 

&lt;td &gt;


Spread&lt;/td&gt; 

&lt;td &gt;


Daemon-to-daemon connections&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


4804&lt;/td&gt; 

&lt;td &gt;


UDP&lt;/td&gt; 

&lt;td &gt;


Spread&lt;/td&gt; 

&lt;td &gt;


Daemon-to-daemon connections&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5433&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


Vertica&lt;/td&gt; 

&lt;td &gt;


Vertica clients (vsql, ODBC, JDBC, etc)&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5433&lt;/td&gt; 

&lt;td &gt;


UDP&lt;/td&gt; 

&lt;td &gt;


Vertica&lt;/td&gt; 

&lt;td &gt;


Vertica Spread monitoring and MC cluster import&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5434&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


Vertica&lt;/td&gt; 

&lt;td &gt;


Intra- and inter-cluster communication. Vertica opens the Vertica client port +1 (5434 by default) for intra-cluster communication, such as during a plan. If the port +1 from the default client port is not available, then Vertica opens a random port for intra-cluster communication.&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5444&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


Vertica Management Console&lt;/td&gt; 

&lt;td &gt;


MC-to-node and node-to-node (agent) communications port. See &lt;a href=&#34;../../../../../en/mc/configuring-mc/changing-mc-or-agent-ports/#&#34;&gt;Changing MC or agent ports&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5450&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


Vertica Management Console&lt;/td&gt; 

&lt;td &gt;


Port used to connect to MC from a web browser and allows communication from nodes to the MC application/web server. See &lt;a href=&#34;../../../../../en/mc/getting-started-with-mc/connecting-to-mc/&#34;&gt;Connecting to Management Console&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


5554&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


&lt;a href=&#34;../../../../../en/admin/managing-db/node-management-agent/#&#34;&gt;Node Management Agent&lt;/a&gt;&lt;/td&gt; 

&lt;td &gt;


Node Management Agent&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


6543&lt;/td&gt; 

&lt;td &gt;


UDP&lt;/td&gt; 

&lt;td &gt;


Spread&lt;/td&gt; 

&lt;td &gt;


Monitor-to-daemon connection&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


8443&lt;/td&gt; 

&lt;td &gt;


TCP&lt;/td&gt; 

&lt;td &gt;


HTTPS&lt;/td&gt; 

&lt;td &gt;


HTTPS service. To change the port, use &lt;a href=&#34;../../../../../en/sql-reference/config-parameters/general-parameters/#HTTPServerPortOffset&#34;&gt;HTTPServerPortOffset&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;



      </description>
    </item>
    
    <item>
      <title>Setup: Firewall considerations</title>
      <link>/en/setup/set-up-on-premises/before-you-install/configure-network/firewall-considerations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/setup/set-up-on-premises/before-you-install/configure-network/firewall-considerations/</guid>
      <description>
        
        
        &lt;p&gt;Vertica requires multiple ports be open between nodes. You may use a firewall (IP Tables) on Redhat/CentOS and Ubuntu/Debian based systems. Note that firewall use is not supported on SuSE systems and that SuSE systems must disable the firewall. The installer reports issues found with your IP tables configuration with the identifiers &lt;strong&gt;N0010&lt;/strong&gt; for (systems that use IP Tables) and &lt;strong&gt;N011&lt;/strong&gt; (for SuSE systems).&lt;/p&gt;
&lt;p&gt;The installer checks the IP tables configuration and issues a warning if there are any configured rules or chains. The installer does not detect if the configuration may conflict with Vertica. It is your responsibility to verify that your firewall allows traffic for Vertica as described in &lt;a href=&#34;../../../../../en/setup/set-up-on-premises/before-you-install/configure-network/ensure-ports-are-available/#&#34;&gt;Reserved ports&lt;/a&gt;.

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

The installer does not check NAT entries in iptables.

&lt;/div&gt;&lt;/p&gt;
&lt;p&gt;You can modify your firewall to allow for Vertica network traffic, or you can disable the firewall if your network is secure. Note that firewalls are not supported for Vertica systems running on SuSE.

&lt;div class=&#34;admonition important&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Important&lt;/h4&gt;
You may encounter the &lt;strong&gt;N0010&lt;/strong&gt; issue even when the firewall is disabled. If this occurs, you can workaround this issue and install Vertica by ignoring installer WARN messages. To do this, install (or update) with a failure threshold of FAIL. For example, &lt;code&gt;/opt/vertica/sbin/install_vertica --failure-threshold FAIL &amp;lt;other install options...&amp;gt;&lt;/code&gt;.
&lt;/div&gt;&lt;/p&gt;
&lt;h2 id=&#34;red-hat-and-centos-systems&#34;&gt;Red Hat and CentOS systems:&lt;/h2&gt;
&lt;p&gt;To disable the system firewall, run the following command as root or sudo:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;# systemctl mask firewalld
# systemctl disable firewalld
# systemctl stop firewalld
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;ubuntu-and-debian-systems&#34;&gt;Ubuntu and Debian systems&lt;/h2&gt;
&lt;p&gt;For details on how to configure iptables and allow specific ports to be open, see the platform-specific documentation for your platform:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Debian: &lt;a href=&#34;https://wiki.debian.org/iptables&#34;&gt;https://wiki.debian.org/iptables&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Ubuntu: &lt;a href=&#34;https://help.ubuntu.com/12.04/serverguide/firewall.html&#34;&gt;https://help.ubuntu.com/12.04/serverguide/firewall.html&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

Ubuntu uses the ufw program to manage iptables.

&lt;/div&gt;
&lt;p&gt;To disable iptables on Debian, run the following command as root or sudo:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;
$ /etc/init.d/iptables stop

$ update-rc.d -f iptables remove
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;To disable iptables on Ubuntu, run the following command:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ sudo ufw disable
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;suse-systems&#34;&gt;SuSE systems&lt;/h2&gt;
&lt;p&gt;The firewall must be disabled on SUSE systems. To disable the firewall on SuSE systems, run the following command:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;# /sbin/SuSEfirewall2 off
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
  </channel>
</rss>
