Veritas Storage Foundation 5.1 SP1 Cluster File System Release Notes (5900-1509, April 2011)

vradmin syncvol command compatibility with IPv6 addresses

(2075307)

The vradmin syncvol command does not work with the compressed form of IPv6

addresses. In IPv6 environments, if you run the vradmin syncvol command and

identify the target host using compressed form of the IPv6 address, the command

fails with following error message:

# vradmin -s -full syncvol vol1 fe80::221:5eff:fe49:ad10:dg1:vol1

VxVM VVR vradmin ERROR V-5-52-420 Incorrect format for syncvol.

Also, if you run the vradmin addsec command and you specify the Secondary

host using the compressed IPv6 address, the vradmin syncvol command also

fails – even if you specify the target as hostname.

Workaround: When you use the vradmin addsec and vradmin syncvol

commands, do not specify compressed IPv6 addresses; instead, use hostnames.

Interrupting the vradmin syncvol command may leave volumes

open (2063307)

Interrupting the vradmin syncvol command may leave volumes on the Secondary

site in an open state.

Workaround: On the Secondary site, restart the in.vxrsyncd daemon. Enter the

following:

# /etc/init.d/vxrsyncd.sh stop

# /etc/init.d/vxrsyncd.sh start

SFCFS 5.0MP3 Rolling Patch 2 required for replication between

5.0 MP3 and 5.1 SP1 (1800600)

In order to replicate between Primary sites running SFCFS 5.0 MP3 and Secondary

sites running SFCFS 5.1 SP1, or vice versa, you must install the SFCFS 5.0MP3

Rolling Patch 2 on the nodes using 5.0MP3. This patch resolves several outstanding

issues for replicating between versions.

In an IPv6-only environment RVG, data volumes or SRL names

cannot contain a colon

Issue: After upgrading VVR to an IPv6-only environment in 5.1 release, vradmin

commands may not work when a colon is specified in the RVG, data volume(s)

and/or SRL name. It is also possible that after upgrading VVR to an IPv6-only

Storage Foundation Cluster File System Release Notes

Known issues