Messages related to configuration errors


		< Previous \| TOC \| Index \| Next >

Messages related to configuration errors

This section describes the configuration related errors that are displayed by the
vradmin -l printrvg command and the vradmin -l repstatus command. The Config Errors section appears in the output of the commands only if there are configuration errors in an RDS. The host variable in the error messages is the host name on which the error has occurred.

Note Sometimes, the Config Errors section in the printrvg command output may display multiple error messages separated by commas, for a specific host.

Message	Message definition
host: `Pri or Sec IP not available or vradmind not running`	The Primary IP or the Secondary IP address is not available, or the `vradmind` daemon on the host is not running or is running on a different port. Action: If it is a network problem, correct it. If `vradmind` server is not running on host, start it. If `vradmind` is running and network connection is fine, make sure that `vradmind` is using the same port, as `vradmind` on other hosts in the RDS. Use `vrport` command to check or set the ports.
host: disk group missing.	Host host does not have any disk group with the same name as that specified in the remote_dg attribute, of the Primary RLINK pointing to this host. Action: Make sure the `remote_dg` attribute of the Primary RLINK contains the correct remote disk group name. Use `vxprint` `-l` rlink_name to see the RLINK settings. If the disk group needs to be imported on host, and it hasn't been done, then import the disk group on host.
host: RLINK missing.	Primary RVG has an RLINK to host, but host does not have corresponding rlink to this Primary RLINK. Action: This error can occur due to the following reasons: One or more of the following attributes in the Primary RLINK is incorrect: remote_host, remote_dg, and remote_rlink. Make sure these attributes are correct. The corresponding Secondary RLINK on host is missing. To fix this, you can dissociate the Primary RLINK, delete it from the configuration, and then use `vradmin addsec` command to add host to the RDS.
host: RLINK dissociated.	Host host does have an RLINK corresponding to the Primary RLINK. However, it is not associated with the Secondary RVG. Action: Reassociate the RLINK to the Secondary RVG on host.
host: disk-group mismatch.	The remote_dg attribute of either the Primary RLINK or Secondary RLINK is incorrect. Action: Make sure the remote_dg attribute of the Primary RLINK contains the Secondary disk group name and the remote_dg attribute of the Secondary RLINK contains the Primary disk group name.
host: RLINK mismatch.	The remote_rlink attribute of either the Primary RLINK or Secondary RLINK is incorrect. Action: Make sure the remote_rlink attribute of the Primary RLINK contains the Secondary RLINK name and the remote_rlink attribute of the Secondary RLINK contains the Primary RLINK name.
host: host mismatch.	The local_host and/or remote_host attribute of either the Primary RLINK or Secondary RLINK is incorrect. Action: Make sure the value of the local_host attribute of the Primary RLINK is the same as that of the remote_host attribute value of the Secondary RLINK. Also make sure the value of the remote_host attribute of the Primary RLINK is the same as that of the local_host attribute of the Secondary RLINK.
host: Primary-Primary configuration.	The two Primary RVG RLINKs are pointing to each other. This situation will arise after the original Primary comes up after a Primary failover. Action: Use `vradmin fbsync` or `vradmin makesec` command to convert the original Primary to a Secondary.
host: multiple Primary error.	The same Secondary RVG has more than one Primary RVGs. Action: Check both Primary RVGs to verify which one is the intended Primary then do the following: Dissociate the Secondary RLINK pointing to the unwanted Primary RVG. Dissociate the Primary RLINK from the unwanted Primary RVG. Remove the disassociated RLINK(s) from the configuration.
host: two or more nodes on same host.	Two or more RVGs in the same RDS are located on the same host, host. This configuration is not supported. Action: Keep only one RVG on that host and remove the rest.
host: platform mismatch.	Replication is allowed only between hosts that are on the same platform. This is an invalid configuration.
No Primary RVG.	Ignore this error if it displays only for a few seconds and disappears. If the error persists, then the problem may be due to the Secondary not being able to determine its Primary because it has some configuration error, the Primary is not reachable, or it does not have any RLINK. Action: If the Secondary has an RLINK to a Primary, check to see if the Primary RVG and the corresponding Primary RLINK exist. If yes, make sure that `vradmind` is running on Primary and the network between Primary and Secondary is good. If everything is good, then run `vradmin` `-l` `printrvg` command on the Primary to see what type of configuration error is displayed. Correct the configuration error(s). If Primary RVG does not exist or the Secondary RVG does not have any RLINKs, then just remove the Secondary RVG.
host: Primary and Secondary have same disk-group ID.	This condition happens in the cases when the split mirrored plexes of the Primary volumes are exported without using the Disk Group split option and then imported on the Secondary with force option. Action: Contact Veritas Customer Support.
host: unknown	The configuration status is currently unknown. Action:
host: stale information	The configuration status may be stale. Action:
host: no data volume	This error can occur if one of the RVGs in the RDS does not have a data volume associated with it. Action: Create the appropriate data volume and associate it with the RVG.
host: network-protocol mismatch	The `protocol` attribute of the Primary RLINK is different from that of the Secondary RLINK. Action: Make sure the value of the `protocol` attribute for the Primary and Secondary RLINK is the same.
host: VVR-heartbeat-port mismatch	The `local_port` attribute setting for the Primary RLINK is different from that of the Secondary RLINK. Action: Make sure the value of the `local_port` attribute for the Primary and Secondary RLINK is the same.
host: unsupported VVR version in cross-version replication	The cross-version replication in VVR is only supported between two immediate major releases. Action: Upgrade the VVR version on the host host to the same VVR version as on the other hosts in the RDS.
host: no contact from Primary	This error can occur if the `vradmind` server on the Secondary host is unable to establish contact with the `vradmind` server on the Primary. This can be because the Primary RVG of this RDS cannot be found or the `vradmind` server is not running or is unreachable. Action: If the `vradmind` server is not running, start it.
host: vxconfigd disabled	The `vxconfigd` daemon is currently disabled on the host on which this error occurred. Action: Start the `vxconfigd` daemon.
host: volume-number mismatch	This error can occur if the number of volumes in the Primary and Secondary RVGs of the RDS are different. Action: Use `vradmin printvol` to find out which RVG has the extra data volumes and then either remove them from that RVG or associate corresponding data volumes for these extra data volumes to the other RVGs in the RDS.
host: volume-size mismatch	This error can occur if the sizes of some or all of the data volumes in the Primary and Secondary RVGs of the RDS do not match. Action: Use `vradmin printvol` to find out which data volumes have mismatching sizes and then use the `vradmin resizevol` command to correct the size mismatch error.
host: volume-name mismatch	This error can occur if some or all of the volumes in the Primary and Secondary RVGs of the RDS are not mapped correctly. Action: Use `vradmin printvol` to find out which data volumes are not mapped correctly and correct the mapping error. For more information, refer to the section Mapping the name of a Secondary data volume to a differently named Primary data volume.
host: Primary SRL missing	This error can occur if the Primary SRL was disassociated from the Primary RVG or is missing. Action: If the Primary SRL is missing, create it and associate it to the Primary RVG. If it was disassociated, re-associate it back to the Primary RVG.
host: Secondary SRL missing	This error can occur if the Secondary SRL was disassociated from the Secondary RVG or is missing. Action: If the Secondary SRL is missing, create it and associate it to the Secondary RVG. If it was disassociated, re-associate it back to the Secondary RVG.

Message

Message definition

host: Pri or Sec IP not available or vradmind not running

The Primary IP or the Secondary IP address is not available, or the vradmind daemon on the host is not running or is running on a different port.

Action: If it is a network problem, correct it. If vradmind server is not running on host, start it. If vradmind is running and network connection is fine, make sure that vradmind is using the same port, as vradmind on other hosts in the RDS. Use vrport command to check or set the ports.

host: disk group missing.

Host host does not have any disk group with the same name as that specified in the remote_dg attribute, of the Primary RLINK pointing to this host.

Action: Make sure the remote_dg attribute of the Primary RLINK contains the correct remote disk group name. Use vxprint -l rlink_name to see the RLINK settings. If the disk group needs to be imported on host, and it hasn't been done, then import the disk group on host.

host: RLINK missing.

Primary RVG has an RLINK to host, but host does not have corresponding rlink to this Primary RLINK.

Action: This error can occur due to the following reasons:

One or more of the following attributes in the Primary RLINK is incorrect: remote_host, remote_dg, and remote_rlink. Make sure these attributes are correct.
The corresponding Secondary RLINK on host is missing. To fix this, you can dissociate the Primary RLINK, delete it from the configuration, and then use vradmin addsec command to add host to the RDS.

host: RLINK dissociated.

Host host does have an RLINK corresponding to the Primary RLINK. However, it is not associated with the Secondary RVG.

Action: Reassociate the RLINK to the Secondary RVG on host.

host: disk-group mismatch.

The remote_dg attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the remote_dg attribute of the Primary RLINK contains the Secondary disk group name and the remote_dg attribute of the Secondary RLINK contains the Primary disk group name.

host: RLINK mismatch.

The remote_rlink attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the remote_rlink attribute of the Primary RLINK contains the Secondary RLINK name and the remote_rlink attribute of the Secondary RLINK contains the Primary RLINK name.

host: host mismatch.

The local_host and/or remote_host attribute of either the Primary RLINK or Secondary RLINK is incorrect.

Action: Make sure the value of the local_host attribute of the Primary RLINK is the same as that of the remote_host attribute value of the Secondary RLINK. Also make sure the value of the remote_host attribute of the Primary RLINK is the same as that of the local_host attribute of the Secondary RLINK.

host: Primary-Primary configuration.

The two Primary RVG RLINKs are pointing to each other. This situation will arise after the original Primary comes up after a Primary failover.

Action: Use vradmin fbsync or
vradmin makesec command to convert the original Primary to a Secondary.

host: multiple Primary error.

The same Secondary RVG has more than one Primary RVGs.

Action: Check both Primary RVGs to verify which one is the intended Primary then do the following:

Dissociate the Secondary RLINK pointing to the unwanted Primary RVG.
Dissociate the Primary RLINK from the unwanted Primary RVG.
Remove the disassociated RLINK(s) from the configuration.

host: two or more nodes on same host.

Two or more RVGs in the same RDS are located on the same host, host. This configuration is not supported.

Action: Keep only one RVG on that host and remove the rest.

host: platform mismatch.

Replication is allowed only between hosts that are on the same platform. This is an invalid configuration.

No Primary RVG.

Ignore this error if it displays only for a few seconds and disappears. If the error persists, then the problem may be due to the Secondary not being able to determine its Primary because it has some configuration error, the Primary is not reachable, or it does not have any RLINK.

Action: If the Secondary has an RLINK to a Primary, check to see if the Primary RVG and the corresponding Primary RLINK exist. If yes, make sure that vradmind is running on Primary and the network between Primary and Secondary is good. If everything is good, then run
vradmin -l printrvg command on the Primary to see what type of configuration error is displayed. Correct the configuration error(s).

If Primary RVG does not exist or the Secondary RVG does not have any RLINKs, then just remove the Secondary RVG.

host: Primary and Secondary have same disk-group ID.

This condition happens in the cases when the split mirrored plexes of the Primary volumes are exported without using the Disk Group split option and then imported on the Secondary with force option.

Action: Contact Veritas Customer Support.

host: unknown

The configuration status is currently unknown.

Action:

host: stale information

The configuration status may be stale.

Action:

host: no data volume

This error can occur if one of the RVGs in the RDS does not have a data volume associated with it.

Action: Create the appropriate data volume and associate it with the RVG.

host: network-protocol mismatch

The protocol attribute of the Primary RLINK is different from that of the Secondary RLINK.

Action: Make sure the value of the protocol attribute for the Primary and Secondary RLINK is the same.

host: VVR-heartbeat-port mismatch

The local_port attribute setting for the Primary RLINK is different from that of the Secondary RLINK.

Action: Make sure the value of the local_port attribute for the Primary and Secondary RLINK is the same.

host: unsupported VVR version in cross-version replication

The cross-version replication in VVR is only supported between two immediate major releases.

Action: Upgrade the VVR version on the host host to the same VVR version as on the other hosts in the RDS.

host: no contact from Primary

This error can occur if the vradmind server on the Secondary host is unable to establish contact with the vradmind server on the Primary. This can be because the Primary RVG of this RDS cannot be found or the vradmind server is not running or is unreachable.

Action: If the vradmind server is not running, start it.

host: vxconfigd disabled

The vxconfigd daemon is currently disabled on the host on which this error occurred.

Action: Start the vxconfigd daemon.

host: volume-number mismatch

This error can occur if the number of volumes in the Primary and Secondary RVGs of the RDS are different.

Action: Use vradmin printvol to find out which RVG has the extra data volumes and then either remove them from that RVG or associate corresponding data volumes for these extra data volumes to the other RVGs in the RDS.

host: volume-size mismatch

This error can occur if the sizes of some or all of the data volumes in the Primary and Secondary RVGs of the RDS do not match.

Action: Use vradmin printvol to find out which data volumes have mismatching sizes and then use the vradmin resizevol command to correct the size mismatch error.

host: volume-name mismatch

This error can occur if some or all of the volumes in the Primary and Secondary RVGs of the RDS are not mapped correctly.

Action: Use vradmin printvol to find out which data volumes are not mapped correctly and correct the mapping error. For more information, refer to the section Mapping the name of a Secondary data volume to a differently named Primary data volume.

host: Primary SRL missing

This error can occur if the Primary SRL was disassociated from the Primary RVG or is missing.

Action: If the Primary SRL is missing, create it and associate it to the Primary RVG. If it was disassociated, re-associate it back to the Primary RVG.

host: Secondary SRL missing

This error can occur if the Secondary SRL was disassociated from the Secondary RVG or is missing.

Action: If the Secondary SRL is missing, create it and associate it to the Secondary RVG. If it was disassociated, re-associate it back to the Secondary RVG.


^ Return to Top	< Previous \| TOC \| Index \| Next >