How to change the port used by VERITAS Volume Replicator (VVR).

Article:TECH10301  |  Created: 2001-01-23  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH10301
Article Type
Technical Solution

Environment

Issue



How to change the port used by VERITAS Volume Replicator (VVR).

Error



vxvm:vxio: port in use 1710

Solution



The above message may be received when trying to attach an rlink on either the secondary or primary system.

The port that is assigned for Volume Replicator use by default is 1710 in file:
    /etc/vx/sr_port
If that port is already being used or needs to be changed for any reason, this file can be edited to change the port number.

If the message is received trying to attach the secondary rlink, change the sr_port file on the primary. If the message is received trying to attach the primary rlink, change the sr_port file on the secondary.

Reboot any system on which /etc/vx/sr_port has been changed.

Steps to get the new port number to be recognized:

1. Detach the primary RLINK. (To avoid losing updates while the RLINK is detached, set a Primary checkpoint before detaching)
On the primary system, type:

    # vxprint -g <disk group> -F"%rvg" <primary rlink name>
    # vxrvg -g <disk group> -c <checkpoint name> checkstart <rvg name from above step>
    # vxrlink -g <disk group> det <primary rlink name>
    # vxrvg -g <disk group> checkend <rvg name from first line>

2. Modify the local_host attribute of the Secondary RLINK so that VVR will re-read the host information.
On the secondary system, type:

    # vxprint -g <disk group> -F"%local_host" <secondary rlink name>
    # vxrlink -g <disk group> det <secondary rlink name>
    # vxedit -g <disk group> set local_host=<local_host name from first step> <secondary rlink name>
    # vxrlink -g <disk group> att <secondary rlink name>

3. Change the remote_host attribute of the primary RLINK.
On the primary system, type:

    # vxprint -g <disk group> -F"%remote_host" <primary rlink name>
    # vxedit -g <disk group> set remote_host=<remote_host name from above step> <primary rlink name>

4. Attach the primary RLINK using the checkpoint created earlier. (This replays any updates that have occurred since the checkpoint was set, and reconciles the secondary image with the primary image.)
On the primary system, type:

    # vxrlink -g <disk group> -c <checkpoint name> att <primary rlink name>

If additional secondary RLINKs are to be modified, repeat steps 1 to 4 for each RLINK.

5. Detach the primary RLINK. (To avoid losing updates while the RLINK is detached, set a primary checkpoint before detaching)
On the primary system, type:

    # vxprint -g <disk group> -F"%rvg" <primary rlink name>
    # vxrvg -g <disk group> -c <checkpoint name> checkstart <rvg name from above step>
    # vxrlink -g <disk group> det <primary rlink name>
    # vxrvg -g <disk group> checkend <rvg name from first line>

6. Modify the local_host attribute of the primary RLINK so that VVR will re-read the host information.
On the primary, type:

    # vxprint -g <disk group> -F"%local_host" <primary rlink name>
    # vxedit -g <disk group> set local_host=<local_host name from above step> <primary rlink name>

7. Attach the primary RLINK using the checkpoint created earlier. (This replays any updates that have occurred since the checkpoint was set, and reconciles the secondary image with the primary image.)
On the primary system, type:

    # vxrlink -g <disk group> -c <checkpoint name> att <primary rlink name>

If additional primary RLINKs are to be modified, repeat steps 5 to 7 for each RLINK.


Legacy ID



235411


Article URL http://www.symantec.com/docs/TECH10301


Terms of use for this information are found in Legal Notices