This section explains error/warning messages regarding rcxdrcheck.
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/FJSVrcvmr/runtime/jruby/lib/native/i386-Linux/libjffi-1.0.so which might have disabled stack guard. The VM will try to fix the stack guard now. It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
This message is displayed when you attempt to load a 32-bit library in a 64-bit Java environment.
There is a possibility that the stack guard of the library has been disabled, so take corrective action.
As the stack guard settings of the library have been enabled, there is no need to take corrective action for this message.
ERROR: This type of DR switchover is not supported.
When "Active-Active operation method" is selected, this message is displayed in either of the following cases.
When performing the Active-Active operation, physical/virtual L-Server switchover and switchover per site cannot be performed.
Refer to the output message, and check the switchover method, the switchover operation method, and the command options. After that, execute the command again.
ERROR: The check tool cannot be processed because the temporary folder %temp% cannot be accessed. Please set the TEMP environment variable of current user correctly, then rerun the check tool.
When executing the command on Windows manager, this message is displayed for either of the following reasons.
Make the %temp% folder accessible on the Windows manager by setting a single folder path to the TEMP environment variable. After that, execute the command again.
ERROR: The specified value is invalid.
The numbers of the specified switchover method or the DR switchover operation method are not correct.
ERROR: Replication check of vmware datastores cannot be performed. Detail: vCLI is not installed or path of vCLI has not been set to environment variable.
VMware vSphere CLI (vCLI) is not installed, or the path has not been added to the PATH environment variable.
Check the following points regarding VMware vSphere CLI (vCLI).
ERROR: Storage resources on the switchover source site are not replicated.target=storage_name1(storageIP/LUN_ID),storage_name2(storageIP/LUN_ID)...
LUNs within the switchover scope: Replication of storage_name1(storageIP/LUN_ID),storage_name2(storageIP/LUN_ID)... has not been performed.
Take corrective action for each storage_name displayed in target.
For details on how to modify the definition file, refer to "3.5 Configuring for Limiting Switchover Scope".
ERROR: Virtual storage resources with additional numbers at the end of the name exist on the switchover source site.target=vs_name1,vs_name2...
There are virtual storage resources, vs_name1,vs_name2..., for which processing to avoid overlapped names is performed.
Modify the names of virtual storage resources displayed in "target", and ensure there are no virtual storage resources for which processing to avoid overlapped names is performed.
For details, refer to "E.1.3 Storage Preparations" in the "Design Guide CE".
ERROR: Output of rcxstorage not found.
The rcxstorage configuration file required for physical L-Server switchover (physical OS) or physical/virtual L-Server switchover (VM host/VM guest) has not been created.
Create the rcxstorage configuration file.
For details, refer to "3. Obtain the Storage Replication Information" in "4.1 Normal Operation".
ERROR: VM management software definition file not found.
The definition file of VM management software required for physical/virtual L-Server switchover (VM host/VM guest) has not been created.
Create the VM management software definition file.
For details, refer to "3. Create a definition file of VM management software [Physical/virtual L-Server switchover (VM host/VM guest)]" in "3.6 Creating Files Used for Switchover".
ERROR: VM pool definition file not found.
The VM pool definition file required for virtual L-Server switchover (VM guest) has not been created.
Create the VM pool definition file.
For details, refer to "4. Create a VM pool definition file [Virtual L-Server switchover (VM guest)]" in "3.6 Creating Files Used for Switchover".
ERROR: VM management software definition file exists.
The VM management software definition file exists.
Check the switchover method. For details, refer to "2.1 Switchover Methods".
When using virtual L-Server switchover (VM guest) or physical L-Server switchover (physical OS), delete the definition file of the VM management software.
ERROR: VM pool definition file exists.
The VM pool definition file exists.
Check the switchover method. For details, refer to "2.1 Switchover Methods".
When using physical/virtual L-Server switchover (VM host/VM guest) or physical L-Server switchover (physical OS), delete the VM pool definition file.
ERROR: Output of rcxstorage exists.
The rcxstorage configuration file exists.
Check the switchover method. For details, refer to "2.1 Switchover Methods".
When using virtual L-Server switchover (VM guest), delete the rcxstorage configuration file.
ERROR: Exported configuration information is out of date.
After the switchover information file is exported, operations requiring the output of the switchover information file again are being performed.
Execute the rcxmgrexport command again to collect the switchover information.
For details, refer to "B.1 rcxmgrexport".
ERROR: Resource names duplicated between sites. type=type. Conflicted resource names are displayed as follows.
Switchover Source Site: resource_name1, Switchover Destination Site: resource_name2
The resource type is type and the same name is set for the switchover target resource resource_name1 on the switchover source site and the resource resource_name2 on the switchover destination site.
Change the resource name on either the switchover source site or the switchover destination site so that no resource names are duplicated between the sites.
Example
ERROR: Resource names duplicated between sites. type=Folder. Conflicted resource names are displayed as follows. Switchover Source Site: /VMHostPool, Switchover Destination Site: /VMHostPool ERROR: Resource names duplicated between sites. type=Network. Conflicted resource names are displayed as follows. Switchover Source Site: /NetworkPoolDR/network1, Switchover Destination Site: /NetworkPool/network1 Switchover Source Site: /TenantA/TenantNetworkPool/network2, Switchover Destination Site: /TenantB/TenantNetworkPool/network2 ERROR: Resource names duplicated between sites. type=Usergroup. Conflicted resource names are displayed as follows. Switchover Source Site: monitor, Switchover Destination Site:monitor Switchover Source Site: test, Switchover Destination Site:test
ERROR: Network's VLAN ID overlapped between sites. Conflicted resource names are displayed as follows. Switchover Source Site: network_name1, Switchover Destination Site: network_name2
The VLAN ID of the network resource network_name1 on the switchover source site and the VLAN ID of the network resource network_name2 on the switchover destination site are the same.
Recreate the network resource on either the switchover source site or the switchover destination site so that no VLAN IDs for network resources are duplicated between the sites.
For details, refer to "14.3.1 Creating New Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Example
ERROR: Network's VLAN ID overlapped between sites. Conflicted resource names are displayed as follows. Switchover Source Site: /NetworkPoolDR/network1, Switchover Destination Site: /NetworkPool/network2 Switchover Source Site: /TenantA/TenantNetworkPool/network3, Switchover Destination Site: /TenantB/TenantNetworkPool/network4
ERROR: Server resources have not been registered on the destination site.target= server_name1,server_name2...
There are no switchover target server resources displayed in "target" on the switchover destination site.
Take one of the following corrective actions:
For details, refer to "1. Create the mapping definitions of physical servers [Physical L-Server switchover (physical OS), Physical/Virtual L-Server switchover (VM host/VM guest)]" in "3.6 Creating Files Used for Switchover".
ERROR: VM host resources have not been registered on the destination site.target= host1,host2...
The VM host resources displayed in "target" do not exist on the switchover destination site.
Take one of the following corrective actions:
For details, refer to "4. Create a VM pool definition file [Virtual L-Server switchover (VM guest)]" in "3.6 Creating Files Used for Switchover".
ERROR: Subnet of Admin LAN overlapped between sites. Conflicted resource names are displayed as follows.
Switchover Source Site: network_name1, Switchover Destination Site: network_name2
The admin LAN subnet of the network resource network_name1 on the switchover source site and the admin LAN subnet of the network resource network_name2 on the switchover destination site are the same.
Modify the settings of the network resource on either the switchover source site or the switchover destination site so that no admin LAN subnets for network resources are duplicated between the sites.
For details, refer to "5.11 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Example
ERROR: Subnet of Admin LAN overlapped between sites. Conflicted resource names are displayed as follows. Switchover Source Site: /NetworkPoolDR/network1, Switchover Destination Site: /NetworkPool/network2 Switchover Source Site: /TenantA/TenantNetworkPool/network3, Switchover Destination Site: /TenantB/TenantNetworkPool/network4
ERROR: Address set resources overlapped between sites. Conflicted resource names are displayed as follows.
Switchover Source Site: address_set_name1, Switchover Destination Site: address_set_name2
The address scope of the address set resource address_set_name1 on the switchover source site and the address scope of the address set resource address_set_name2 on the switchover destination site are the same.
Recreate the address set resource on either the switchover source site or the switchover destination site so that address scopes of MAC addresses and WWN address set resources do not overlap between the sites.
For details, refer to "14.6 Address Set Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Example
ERROR: Address set resources overlapped between sites. Conflicted resource names are displayed as follows. Switchover Source Site: /AddressPool/mac1, Switchover Destination Site: /AddressPool/mac2 Switchover Source Site: /TenantA/TenantAddressPool/wwn1, Switchover Destination Site: /TenantB/TenantAddressPool/wwn2
ERROR: Network devices have not been registered on the destination site.target= net_dev1,net_dev2...
The network device resources displayed in "target" do not exist on the switchover destination site.
Register the network device displayed in "target" in the network tree.
For details, refer to "5.7 Registering Network Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
ERROR: ROR version does not match between sites.
The version levels of the ROR CE managers are not the same between sites.
Take one of the following corrective actions:
ERROR: Location of ROR installation folder does not match between sites.
The installation folders of the ROR CE manager are not the same between sites.
Reconfigure the manager to configure the same installation folder as that of the switchover source site.
ERROR: Admin LAN IP address of the admin server does not match between sites. IP addresses of both sites are displayed as follows. Switchover Source Site: ip_address1, Switchover Destination Site: ip_address2
ip_address1, the admin LAN IP address of the admin server on the switchover source site and ip_address2, the admin LAN IP address of the admin server on the switchover destination site, are not the same.
Reconfigure the manager to use the same admin LAN IP addresses as that of the switchover source site.
Example
ERROR: Admin LAN IP address of the admin server does not match between sites. IP addresses of both sites are displayed as follows. Switchover Source Site:10.167.223.100, Switchover Destination Site: 10.167.223.101
ERROR: IP address of storage units conflicted between sites. Conflicted resource names are displayed as follows.
Switchover Source Site: storage_unit_name1, Switchover Destination Site: storage_unit_name2
The same IP address is configured for the storage unit storage_unit_name1 on the switchover source site and the storage unit storage_unit_name2 on the switchover destination site.
Re-create the IP address of the storage unit on either the switchover source site or the switchover destination site so that IP addresses of storage devices do not overlap between the sites.
Example
ERROR: IP address of storage units conflicted between sites. Conflicted resource names are displayed as follows. Switchover Source Site: storage_unit_name1, Switchover Destination Site: storage_unit_name2 Switchover Source Site: storage_unit_name3, Switchover Destination Site: storage_unit_name4
ERROR: IP address of servers conflicted between sites. Conflicted resource names are displayed as follows.
Switchover Source Site: server_name1, Switchover Destination Site: server_name2
The same values are configured for the admin LAN IP address used by the physical L-Server on the physical server server_name1 on the switchover source site and for the IP address used by the physical server server_name2 on the switchover destination site.
Perform the following procedure on the switchover destination site to ensure that the IP addresses of physical servers do not overlap between sites.
Example
ERROR: IP address of servers conflicted between sites. Conflicted resource names are displayed as follows. Switchover Source Site: server_name1, Switchover Destination Site: server_name2 Switchover Source Site: server_name3, Switchover Destination Site: server_name4
ERROR: Global addressset resource addrset is used by tenant_name1, tenant_name2...
The global attribute address set resource addrset is used for the tenant tenant_name1, tenant_name2....
Take one of the following corrective actions:
ERROR: Invalid file format, detail=The value of "rcxstorage_define" in the definition filefilepath not found.
The path configured for "rcxstorage_define" in the configuration file displayed in file_path cannot be found.
Confirm that the path configured for "rcxstorage_define" in the configuration file displayed in file_path is correct.
ERROR: Invalid file format, detail=The value of "rcxmgrexport_define" in the definition file file_path not found.
When executing the rcxdrcheck command, there is an error in an item checked when the -dir option is not specified.
The path configured for "rcxmgrexport_define" in the configuration file displayed in file_path cannot be found.
Confirm that the path configured for "rcxmgrexport_define" in the configuration file displayed in file_path is correct.
ERROR: Invalid file format, detail=The value of "salvage_define" in the definition file file_path not found.
The path configured for "salvage_define" in the configuration file displayed in file_path cannot be found.
Confirm that the path configured for "salvage_define" in the configuration file displayed in file_path is correct.
ERROR: Invalid file format, detail=The value of "DR Operation Method" in the definition file file_path is wrong.
There is an error in the item checked when automatic takeover of configuration files is enabled.
There is an error in the content configured for "DR Operation Method" in the configuration file displayed in file_path.
Confirm that one of the following values is correctly configured for "DR Operation Method" in the configuration file displayed in file_path.
For details on automatic takeover of configuration files, refer to "3.3 Manager Installation and Configuration".
ERROR: Invalid file format, detail=The value of "DR Operation Method" has not been set to the definition file file_path.
There is an error in the item checked when automatic takeover of configuration files is enabled.
There is no value configured for "DR Operation Method" in the configuration file displayed in file_path.
Confirm that one of the following values is correctly configured for "DR Operation Method" in the configuration file displayed in file_path.
For details on automatic takeover of configuration files, refer to "3.3 Manager Installation and Configuration".
ERROR: Invalid file format, detail=The value of "Config File Switchover" in the definition file file_path is wrong.
There is an error in the content configured for "Config File Switchover" in the configuration file displayed in file_path.
Confirm that the following value is correctly configured for "Config File Switchover" in the configuration file displayed in file_path.
For details on automatic takeover of configuration files, refer to "3.3 Manager Installation and Configuration".
ERROR: Disk resources have not been prepared on the switchover destination site.target=/pool1/disk1, /pool1/disk2,...
There is the following inconsistency between the switchover source and destination sites:
Disk resources disk1, disk2, ... which are linked to the virtual storage "vm-disk-vstorage" are configured as switchover targets.
Disk resources with the same name as disk1, disk2, ... do not exist in the ROR database.
Register the disk resources disk1, disk2, ... displayed for "target" on the switchover destination site.
For the registration procedure, refer to "Configuration when Performing Virtual L-Server Switchover (VM Guest)" in "3.4 Configuring Managed Resources".
WARNING: Invalid file format, detail=The value of "rcxstorage_define" has not been set to the definition file file_path.
There is an error in the item checked during physical server switchover (physical OS) or physical/virtual L-Server switchover (VM host/VM guest).
There is no value configured for "rcxstorage_define" in the configuration file displayed in file_path.
When the situation is either of the following cases, configure the path to the switchover information storage folder for "rcxstorage_define" in the configuration file displayed for file_path.
WARNING: Invalid file format, detail=The value of "rcxmgrexport_define" has not been set to the definition file file_path.
When executing the rcxdrcheck command, there is an error in an item checked when the -dir option is not specified.
There is no value configured for "rcxmgrexport_define" in the configuration file displayed in file_path.
When the situation is either of the following cases, configure the path to the switchover information storage folder for "rcxmgrexport_define" in the configuration file displayed for file_path.
For details on the rcxmgrexport command, refer to "B.1 rcxmgrexport".
WARNING: Invalid file format, detail=The value of "salvage_define" has not been set to the definition file file_path.
There is no value configured for "salvage_define" in the configuration file displayed in file_path.
For "salvage_define" in the configuration file displayed in the file_path, enter the path to be specified when using the rcxrecovery -salvage command.
For details on the rcxrecovery -salvage command, refer to "B.2 rcxrecovery".
WARNING: Auto switchover of configuration files has not been turned on.
There is no value configured for "Config File Switchover" in the configuration file displayed in file_path.
When enabling automatic takeover of configuration files, configure "config_file_switchover=true" for "Config File Switchover" in the configuration file displayed in file_path.
For details on automatic takeover of configuration files, refer to "3.3 Manager Installation and Configuration".
ERROR: Software ID prefix has not been changed properly.
Different values are not configured for the software ID prefixes of the two sites.
Execute the software ID batch conversion command, "cfmg_changesoftwareid", and then configure different software ID prefixes for each site.
For details, refer to "Appendix A Settings for Software ID Prefixes".
WARNING: Global network resource net is used by tenant_name1, tenant_name2...
The global attribute network resource net is used for the tenant tenant_name1, tenant_name2....
Take one of the following corrective actions:
For details, refer to "4.2.2 Locking the Resources and Exporting the Configuration Information [Switchover Source Site]".
WARNING: The location of image file folder is not set correctly.
When performing physical L-Server switchover (physical L-Server), the image file storage folder is not modified to "switchover_information_storage_folder\Image".
Configure "switchover_information_storage_folder\Image" for the image file storage folder of the physical L-Server, and replicate the folder to the switchover destination site. Execute the following command to modify the image file storage folder of the physical L-Server to "switchover_information_storage_folder\Image".
[Windows Manager]
>Installation_folder\SVROR\Manager\bin\rcxadm mgrctl stop <RETURN> >Installation_folder\SVROR\Manager\bin\rcxadm imagemgr set -attr imagedir=switchover_information_storage_folder\Image <RETURN> >Installation_folder\SVROR\Manager\bin\rcxadm mgrctl start <RETURN>
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl stop <RETURN> # /opt/FJSVrcvmr/bin/rcxadm imagemgr set -attr imagedir=switchover_information_storage_folder/Image <RETURN> # /opt/FJSVrcvmr/bin/rcxadm mgrctl start <RETURN>
For details, refer to "6.7 Changing the Image Folder Location" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
WARNING: Resource names duplicated between sites. type=type. Conflicted resource names are displayed as follows. Switchover Source Site: resource_name1, Switchover Destination Site: resource_name2
The resource type is type and the same name is set for the switchover target resource resource_name1 on the switchover source site and the resource resource_name2 on the switchover destination site.
When resource_name1 and resource_name2 are different resources, change the resource name on either the switchover source site or the switchover destination site so that resource names do not overlap between the sites.
Example
WARNING: Resource names duplicated between sites. type=VirtualStorage. Conflicted resource names are displayed as follows. Switchover Source Site: /StoragePool/datastore1, Switchover Destination Site: datastore1 Switchover Source Site: /TenantA/TenantStoragePool/datastore2, Switchover Destination Site: datastore2
WARNING: Resources have not been unregistered on switchover destination site.target= resource_name1,resource_name2
When performing switchover in Active-Active operation, the resource displayed in "target" is required for switchover, but registration from the resource pool in the switchover destination site is not canceled.
Unregister the resource shown in "target" from the resource pool in the switchover source site in advance.
WARNING: Server resources have not been registered on the destination site.target= server_name1,server_name2...
There are no switchover target server resources displayed in "target" on the switchover destination site.
When the server resources displayed for "target" are out of the switchover scope, no action is necessary.
When the server resources displayed for "target" are included in the switchover scope, perform one of the following corrective actions:
For how to limit the scope of switchover, refer to "2.4 Limitation of switchover scope and additional recovery".
For details on how to edit mapping definition files, refer to "1. Create the mapping definitions of physical servers [Physical L-Server switchover (physical OS), Physical/Virtual L-Server switchover (VM host/VM guest)]" in "3.6 Creating Files Used for Switchover".
WARNING: VM host resources have not been registered on the destination site.target= host1,host2...
The VM host resources displayed in "target" do not exist on the switchover destination site.
When the VM host resources displayed for "target" are out of the switchover scope, no action is necessary.
When the VM host resources displayed for "target" are included in the switchover scope, perform one of the following corrective actions:
For how to limit the scope of switchover, refer to "2.4 Limitation of switchover scope and additional recovery".
For details on how to edit the VM pool definition file, refer to "4. Create a VM pool definition file [Virtual L-Server switchover (VM guest)]" in "3.6 Creating Files Used for Switchover".