![]() |
![]() |
![]() |
![]() |
![]() |
VVR uses the UDP and TCP transport protocols to communicate between the Primary and Secondary. This section lists the default ports used by VVR. VVR uses the following ports by default when replicating data using UDP:
VVR uses the following ports by default when replicating data using TCP.
Use the vrport(1M)
command to display, change or set the port numbers used by VVR. You may have to change the port numbers in the following cases:
To resolve a port number conflict with other applications.
To configure VVR to work in your firewall environment.
To configure VVR to work in your firewall environment when using UDP; to specify a restricted number of ports to replicate data between the Primary and the Secondary.
Use the vrport heartbeat
command to display the port number used by VVR, for heartbeats. To change the heartbeat port number on a host, specify the port number with the vrport
heartbeat
command. Use the vradmin
changeip
command to update the RLINKs with the new port information, and then restart the vxnetd
daemon on the required system for the changes to take effect.
To display the port number used for heartbeats
To change the port number used for heartbeats
To change the replication heartbeat port on seattle from 4145 to 5000
vrport
command to change the heartbeat port to 5000 on the required host.
vradmin changeip
command without the newpri and newsec attributes.
vxnetd
daemon.
vxnetd
daemon.
Follow the same steps to change the heartbeat port on secondary (london).
Note
VVR supports a configuration with different heartbeat port numbers on the primary and secondary.
To display the port number used by vradmind
, use the vrport
vradmind
command. To change the vradmind
port, specify the port number with the vrport
vradmind
command.
To display the port number used by vradmind
To change the port number used by vradmind
Note
You must restart the server
vradmind
for this change to take effect. Make sure you change the port number on all the hosts in the RDS.
To display the port numbers used by in.vxrsyncd
, use the vrport
vxrsyncd
command. To change the port numbers used by in.vxrsyncd
, specify the port number with the vrport
vxrsyncd
command.
To display the port number used by in.vxrsyncd
To change the port number used by in.vxrsyncd
Note
You must restart the server
in.vxrsyncd
for this change to take effect. Make sure you change the port number on all the hosts in the RDS.
Ports used to replicate data using UDP
To display the ports used to replicate data when using UDP, use the vrport
data
command. To change the ports used to replicate data when using UDP, specify the list of port numbers to use with the vrport
data
command.
Each RLINK requires one UDP port for replication. Specify an unused, reserved port number that is less than 32768 so that there is no port conflict with other applications. The number of ports specified must be equal to or greater than the number of RLINKs on the system.
Note
For systems using the TCP protocol for replication, you are not required to select any data port as the connection is established with the listener port on the remote host. The listener uses this port number which is numerically same as the UDP port used for heartbeat messages.
To display ports used to replicate data when using UDP
To change ports used to replicate data when using UDP
For a system configured with one RLINK, use the following command:
For a system configured with multiple RLINKs, you can specify either a range of port numbers or a list of port numbers or both.
To specify a range of port numbers, use the following command:
# vrport
data
port1, port2, portlow-porthigh, .....
# vrport
data 3400, 3405, 3500-3503, 5756-5760
Note
To use the new port information, execute
/usr/sbin/vxnetd
, and then pause and resume all RLINKs.