Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Restrict ports for vIDM Postgres cluster deployed via vRSLCM (79163)

Last Updated: 5/20/2020Categories: TroubleshootingTotal Views: 3135Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

The purpose of this article is to restrict the ports required for PostgreSQL clustering to only the cluster nodes. Short description of the ports usage:

Ports

Description

5432

Postgres connections

9999

Pgpool-II connections

9898

PCP process connections

9000

Watchdog connections

9694

For receiving watchdog's heartbeat signal

Resolution

To restrict the ports, follow below steps:

Note: Perform on all nodes

Create a file name post, use the command:

vi /usr/local/horizon/conf/iptables/post

Add the below content in the file created in step1:

POST_tcp_all=""
POST_tcp_vapp="5432 9999 9000 9898 9694"

POST_udp_all=""

POST_udp_vapp=""

Provide the required permissions to enable.post file, use the commands:

touch /usr/local/horizon/conf/flags/enable.post

chmod 644 /usr/local/horizon/conf/flags/enable.post

Ensure the file has read/write access, use the command:

Example:
# ls -lat usr/local/horizon/conf/flags/enable.post
-rw-r--r-- 1 root root 0 Apr 28 18:25 /usr/local/horizon/conf/flags/enable.post

Open the file iptables.conf,using the command:

vi /usr/local/horizon/conf/iptables.cfg

Replace the line:

IPTABLE_tcp_all=" 5432 9999 9000 9898 9694 443 80"

with

IPTABLE_tcp_all="443 80"

Open the file ipRedirect.sh,using the command:

vi /usr/local/horizon/scripts/ipRedirect.sh

Replace the below line:

IP=`/sbin/ip -o -f inet addr show dev ${IFC} | awk ‘{ print $4 }‘| sed -e ‘s/\/.*$//’`

with

IP=`/sbin/ip -o -f inet addr show dev ${IFC} | grep -v secondary | awk '{ print $4 }'| sed -e 's/\/.*$//'`

Run the command to update the iptables:

 /usr/local/horizon/scripts/updateiptables.hzn

To verify if the ports are open only to the required cluster nodes:

iptables -L -n --line-numbers | grep :<port>

Example:

#iptables -L -n --line-numbers | grep :5432

15 ACCEPT tcp -- Node1 0.0.0.0/0 tcp dpt:5432 ctstate NEW,ESTABLISHED
16 ACCEPT tcp -- Node2 0.0.0.0/0 tcp dpt:5432 ctstate NEW,ESTABLISHED
17 ACCEPT tcp -- Node3 0.0.0.0/0 tcp dpt:5432 ctstate NEW,ESTABLISHED
15 ACCEPT tcp -- Node1 0.0.0.0/0 tcp spt:5432 ctstate ESTABLISHED
16 ACCEPT tcp -- Node2 0.0.0.0/0 tcp spt:5432 ctstate ESTABLISHED
17 ACCEPT tcp -- Node3 0.0.0.0/0 tcp spt:5432 ctstate ESTABLISHED

Note: Use this command for the other ports to confirm the same.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Content 3.22.1 for Android リリースのお知らせ (79224)

KB
•
VMware Intelligent Hub 20.04.1 for iOS リリースのお知らせ (79195)

KB
•
CRSVC-11528：「デバイス削除」などのデバイス管理操作が断続的に失敗する (79114)

KB
•
Workspace ONE SDK 20.4 for Android リリースのお知らせ (79124)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Identity Manager

VMware Aria Suite Lifecycle

Related Versions:

VMware vRealize Suite Lifecycle Manager 8.x

VMware vRealize Suite Lifecycle Manager 8.1.x

VMware Identity Manager 3.0

Take Our Survey

Support Assistant