When configuring the RPV client, the following details are defined: The SMIT fast path to configure the RPV clients is  smitty rpvclient . The RPV server runs on the remote machine, one for each physical volume that is  being replicated. The RPV server can listen to many remote RPV clients on different  hosts to handle fallover. The RPV server is an instance of the kernel extension of the RPV device driver with  names such as rpvserver0, and is not an actual physical device. When configuring the RPV server, the following items are defined: A VG that consists of local PVs and RPVs. Strict rules apply to GMVGs to ensure that  you have a complete copy of the mirror at each site. For this reason, the superstrict  allocation policy is required for each logical volume in a GMVG. PowerHA SystemMirror Enterprise Edition also expects each logical volume in a  GMVG to be mirrored, and for asynchronous replication it requires AIX mirror pools.  GMVGs are managed by PowerHA and recognized as a separate class of resource  (GMVG Replicated Resources), so they have their own events. PowerHA verification  issued a warning if there are resource groups (RGs) that contain GMVG resources that  do not have the forced varyon flag set and if quorum is not disabled. The SMIT fast path to configure the RPV servers is  smitty rpvserver . PowerHA enforces the requirement that each physical volume that is part of a VG with  RPV clients has the reverse relationship defined. This, at a minimum, means that every  GMVG consists of two physical volumes on each site. One disk is locally attached, and  the other is a logical representation of the RPV. GLVM provides SMIT menus to create the GMVGs and the logical volumes. Although  they are not required because they perform the same function as the equivalent SMIT  menus in the background, they do control the location of the logical volumes to ensure  proper placement of mirror copies. If you use the standard commands to configure your  GMVGs, use the GLVM verification utility. GLYPH<129> The IP address of the RPV server. GLYPH<129> The local IP address (defines the network to use). GLYPH<129> The timeout. This field is primarily for the stand-alone GLVM option, as PowerHA  overwrites this field with the cluster’s  config_too_long  time. In a PowerHA cluster,  this is the worst case scenario because PowerHA detects problems with the remote  node before then. – RPV server GLYPH<129> The physical volume identifier (PVID) of the local physical volume. GLYPH<129> The IP addresses of the RPV clients (comma-separated). –  Geographically mirrored volume group (GMVG) – GLVM utilities – Network types: XD_data A network that can be used only for data replication. A  maximum of four XD_data networks can be defined.  Etherchannel is supported for this network type. This network  supports adapter swap, but not fallover to another node.  Heartbeat packets are also sent over this network. XD_ip An IP-based network that is used for participation in  heartbeating and client communication. Chapter 7. Geographical Logical Volume Manager configuration assistant  267