Symantec logo

Displaying a specific RLINK

Use the vxprint -Pl command to display detailed information about the status of an RLINK. This command prints one record per RLINK. The following table lists the information displayed in the output.

To display detailed information about a specific RLINK:

# vxprint -g diskgroup -Pl rlink_name

Disk Group 

Name of the disk group. 

RLINK Name 

Name of the RLINK. 

Info 

timeout, packet_size, record_id, latency high, low marks and bandwidth_limit.  

State 

Displays utility state of the RLINK - active, stale, etc. 

synchronous, latencyprot, and srlprot 

The current configuration settings for the replication mode, the latency mode, and SRL protection. 

assoc 

The RVG to which the RLINK is associated. 

remote_host/IP_addr/port 

The name of the remote host for the RLINK, its IP address, and the port number. 

remote_dg 

The name of the disk group on the remote system. 

remote_dg_dgid 

The disk group ID assigned when the disk group was created on the remote system.  

remote_rvg_version 

The rvg_version of the remote RVG. 

remote_rlink 

The name of the corresponding RLINK on the remote host. 

remote_rlink_rid 

The record_id of the corresponding RLINK on the remote host. 

local_host/IP_addr/port 

The name of the local host, its IP address, and the port number it uses for communication to the remote host. 

protocol 

The transport protocol used by the RLINK for communicating between the hosts. The protocol can be either UDP/IP or TCP/IP.  

checkpoint 

Displays the checkpoint only if the Primary RLINK is attached using the checkpoint or the Secondary RLINK has been restored using the checkpoint. 

flags 

See Interpreting RLINK flag settings


  Note   To display all the RLINK names in a single column, issue the following command:
# vxrvg -g diskgroup [-1] getrlinks rvg_name


Interpreting RLINK flag settings

The following table lists the various flags that can appear in the flags field of the vxprint -Pl output.


  Note   The Primary and Secondary RLINKs are communicating only when the connected flag is on. However, replication is taking place only if the following set of flags is displayed:
write enabled attached consistent connected
In all other cases, a corrective action may be needed.


autosync 

The RDS is in the process of automatic synchronization. 

attached 

The RLINK is attached to the RVG. 

can_sync 

If the inconsistent and can_sync flags are set, there is enough information in the Secondary SRL volume to make the Secondary consistent again and capable of taking over. 

cant_sync 

The RLINK is inconsistent, and this Secondary needs a complete resynchronization before it can take over or replicate. 

connected 

The RLINK is connected to the corresponding RLINK on the remote host and replication can take place. 

consistent 

The state of the data volumes on the Secondary is suitable for takeover. 

dcm_logging 

DCM is in use, due to either autosync, failback sync, or an SRL overflow. 

detached 

The RLINK is stale and not taking part in replication. 

disabled 

The RLINK is not attached and is not replicating. 

disconnected 

The two RLINKs are not connected and are not replicating. 

enabled 

The RLINK is attached. If the connected flag is displayed, replication can take place. If the disconnected flag is displayed, replication is not taking place. 

fail 

An I/O error occurred while writing to a data volume on the Secondary. 

inconsistent 

The data in the Secondary volumes is not consistent and the Secondary cannot take over. 

needs_recovery 

State after an import or reboot. The vxrecover command clears this state. 

primary_paused 

The Primary RLINK has been paused and the RLINKs are not replicating. 

resync_started 

The resynchronization of the Secondary has been started. 

resync_paused 

The resynchronization has been started but is not currently active because of some problem. 

secondary_config_err 

There is a mismatch between the configuration of the volumes on the Primary and the Secondary - either a volume is missing on the Secondary or its length is not the same as that of the corresponding volume on the Primary. 

secondary_log_err 

An I/O error has occurred on the Secondary SRL; replication cannot continue until the SRL has been dissociated and a new one associated. 

secondary_paused 

The Secondary RLINK has been paused and the RLINKs are not replicating.