 | ||
| Changing ports for VCS | ||
|---|---|---|
| Prev | About administering clusters | Next |
You can change some of the default ports for VCS and its components.
The following is a list of changes that you can make and information concerning ports in a VCS environment:
Changing VCS's default port.
Add an entry for a VCS service name In /etc/services file, for example:
vcs-app 3333/tcp # Veritas Cluster Server
Where 3333 in the example is the port number where you want to run VCS. When the engine starts, it listens on the port that you configured above (3333) for the service. You need to modify the port to the /etc/services file on all the nodes of the cluster.
You do not need to make changes for agents or HA commands. Agents and HA commands use locally present UDS sockets to connect to the engine, not TCP/IP connections.
You do not need to make changes for HA commands that you execute to talk to a remotely running VCS engine (HAD), using the facilities that the VCS_HOST environment variable provides. You do not need to change these settings because the HA command queries the /etc/services file and connects to the appropriate port.
For the Java Console GUI, you can specify the port number that you want the GUI to connect to while logging into the GUI. You have to specify the port number that is configured in the /etc/services file (for example 3333 above).
To change the default port
/etc/services.vcs-app 3333/tcp # Veritas Cluster Server
/etc/services file on all the nodes of the cluster.# netstat -an|grep 3333
*.3333 *.* 0 0 49152 0 LISTEN *.3333 *.* 0 0 49152 0 LISTEN