3.4 Configuring Managed Resources

Configure the settings of managed servers and network devices for the switchover source and destination sites.

For details, refer to the following:

Registering Infrastructure Administrators
Refer to "3.1 Registering User Accounts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Creating Definition Files
Refer to "Appendix G Definition Files" in the "Setup Guide CE".
Registering Resources with Resource Orchestrator
Refer to "Chapter 5 Registering Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Installing Software and Registering Agents on VM Hosts
Refer to "8.2 Installing Software and Registering Agents on VM Hosts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Registering Resources to the Global Pool
Refer to "Chapter 14 Registering Resources in Resource Pools" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Creating L-Server Templates
Refer to "15.1.2 Creating" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Creating an L-Server for an Infrastructure Administrator
Refer to "L-Servers for Infrastructure Administrators" in "1.2.2 Configuring Resources" in the "Setup Guide CE".
Collecting and Registering Cloning Images
Refer to "17.5 Cloning Image Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Creating L-Platform Templates
Refer to "Chapter 8 Template" in the "User's Guide for Infrastructure Administrators CE".

For Disaster Recovery environments, configure as follows.

Common Configurations

For details on the items to match or to be different, between the switchover source and destination sites, refer to "Chapter 2 Design".
Register servers on the server tree in advance on the switchover destination site as well as on the switchover source site. It is also necessary to configure the BIOS settings on the registered server in advance. For details, refer to "8.2.7 Configuring BIOS Settings of Managed Servers" in the "Design Guide CE".
Configuration when physical L-Servers are switchover targets
This procedure is required for all switchover target physical L-Servers on which agents of Resource Orchestrator are installed.
- Installation of the first managed server on the switchover source site
  1. Install the agent of Resource Orchestrator on a managed server.
  2. Register the managed server to the resource tree on the admin server.
  3. Collect the following file from the managed server.
    [Windows]
    Installation_folder\Agent\StorageRM\Agent\etc\certificate\agent_keystore
    [Linux]
    /etc/opt/FJSVssagt/certificate/agent_keystore
- Installation of the second managed server on the switchover source site or the first and subsequent managed server on the switchover destination site
  1. Install the agent of Resource Orchestrator on a managed server.
  2. After the agent installation, overwrite "agent_keystore" with the data collected when the first managed server was installed on the switchover source site.
  3. Register the managed server to the resource tree on the admin server.
This procedure is not necessary for physical L-Servers created using images collected after the procedure above which contain the "agent_keystore" of the collection source.
When no managed server with an agent of Resource Orchestrator installed is registered on the switchover destination site, copy the files in the following folder again from the manager of the switchover source site to that of the switchover destination site after installing the first managed server on the switchover source site.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\opt\FJSVssmgr\current\certificate\
[Linux Manager]
/etc/opt/FJSVrcvmr/opt/FJSVssmgr/current/certificate/
Regarding the following configurations, use the information that fits the environment on the switchover source and switchover destination site respectively.
[Windows Manager]
- Under Installation_folder\SVROR\Manager\etc\storage\emc
- Installation_folder\SVROR\Manager\etc\customize_data\storage_portset.rcxprop
- Under Installation_folder\Manager\etc\customize_data\fc_connection_pattern
[Linux Manager]
- Under /etc/opt/FJSVrcvmr/storage/emc
- /etc/opt/FJSVrcvmr/customize_data/storage_portset.rcxprop
- Under /etc/opt/FJSVrcvmr/customize_data/fc_connection_pattern
Information
Regarding the files to be stored in fc_connection_pattern
Specify the same file name in each site.
Describe the same definition for NUM_OF_FC and BOOT_FC_PORT in the files for each site.
Describe definitions for STORAGE_X of each file suitable for the storage units in each site.
For details on files to be stored in fc_connection_pattern, refer to "7.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
For network devices registered on the network tree, prepare identical devices and register them in advance on the switchover destination site.
When using an NS Appliance as a network device, the firewall setting information in the NS Appliance is inherited during switchover. However, the network device configuration information in the network tree of Resource Orchestrator is not inherited.
For this reason, create an NS Appliance on the switchover destination site as well, and register it as a network device beforehand.
For NS Appliance operation procedures refer to the "NS Option Instruction".
When using the auto-configuration function for network devices
Copy the files and folders below to the switchover destination site.
[Windows Manager]
- Installation_folder\SVROR\Manager\etc\customize_data\network_device_model.xml
- Installation_folder\SVROR\Manager\etc\scripts\
[Linux Manager]
- /etc/opt/FJSVrcvmr/customize_data/network_device_model.xml
- /etc/opt/FJSVrcvmr/scripts/
When using a NIC other than one in the default configurations of network auto-configuration, create a server NIC definition, and reflect it on the manager.
Create the same server NIC definition for the switchover destination site as the one for the switchover source site in advance, and reflect it on the manager.
Execute the rcxadm nicdefctl commit command, and reflect the created server NIC definition on the manager.
For details on server NIC definitions, refer to "15.13 Server NIC Definition" in the "Reference Guide (Command/XML) CE".
For details on the rcxadm nicdefctl commit command, refer to "5.15 rcxadm nicdefctl" in the "Reference Guide (Command/XML) CE".
For admin LAN subnets linked to the switchover target network resources, register the same subnet name and scope on the switchover destination site in advance.
For details on how to register admin LAN subnets, refer to "5.11 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For the Active-Standby operation, proceed with the switchover destination site installation before registering resources in the resource pool. When using the backup site for tasks with lower priority, proceed with the switchover destination site installation before performing switchover.
For the Active-Active operation, install both the switchover source site and switchover destination site.
The following customizations on the switchover source site, which are performed according to "Chapter 9 Post-Installation Procedures" in the "Setup Guide CE", need to be reflected on the switchover destination site before switchover.
Configure the backup site while setting up the environment, or reflect the settings as a part of switchover.
- "9.1 Settings for Sending Email"
- "9.2.2 Setting Application Process Settings"
- "9.2.3 Setting Application Process to be Used"
- "9.3 Customizing the Dashboard"
- "9.4 Setting the Host Names for Virtual Servers"
- "9.5 Setting the Method for Setting Resource Names"
- "9.6 Settings for the Overcommit Function"
- "9.7 Editing the Environment Setup File for the L-Platform API"
- "9.9 System Disk Settings for Physical L-Servers"
- "9.12 Editing the License Agreement"
- "9.13 Editing the User Agreement when Registering a User"
Back up the following files if they have been modified.
[Windows Manager]
- Installation_folder\RCXCFMG\config\command_config.xml
- Installation_folder\RCXCFMG\config\mail_config.xml
- Installation_folder\RCXCFMG\config\vsys_config.xml
- Installation_folder\RCXCTMG\Charging\conf\accounting.properties
- Installation_folder\RCXCTMG\MyPortal\config\application_process.properties
- Installation_folder\RCXCTMG\MyPortal\config\custom_config.xml
- Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml
- Installation_folder\RCXCTMG\MyPortal\config\license\create\default
- Installation_folder\RCXCTMG\MyPortal\config\license\reconfigure\default
- Installation_folder\RCXCTMG\MyPortal\config\license\return\default
- Installation_folder\RCXCTMG\SecurityManagement\conf\portal.properties
- Installation_folder\IAPS\F3FMihs\servers\FJapache\htdocs\sopdocs\pub\html\en\cRegApply_agreement.forUse_en.html
[Linux Manager]
- /etc/opt/FJSVcfmg/config/command_config.xml
- /etc/opt/FJSVcfmg/config/mail_config.xml
- /etc/opt/FJSVcfmg/config/vsys_config.xml
- /etc/opt/FJSVctchg/conf/accounting.properties
- /etc/opt/FJSVctmyp/config/application_process.properties
- /etc/opt/FJSVctmyp/config/custom_config.xml
- /etc/opt/FJSVctmyp/config/managerview_config.xml
- /etc/opt/FJSVctmyp/config/license/create/default
- /etc/opt/FJSVctmyp/config/license/reconfigure/default
- /etc/opt/FJSVctmyp/config/license/return/default
- /etc/opt/FJSVctsec/conf/portal.properties
- /var/opt/FJSVihs/servers/FJapache/htdocs/sopdocs/pub/html/en/cRegApply_agreement.forUse_en.html

Storage Location of Switchover Target Resources for Tenant Switchover

Store the following switchover target resources in the tenant.
- Address set resources
- L-Servers for infrastructure administrators
It is recommended to store the following switchover target resources in the tenant.
- Cloning images
  When performing tenant switchover with the images stored in the global pool, images which never been deployed are not switched over.
- Network resources
  When performing tenant switchover with the resources stored in the global pool, those resources are locked. Consequently, deployment using the network resources in other tenants cannot be performed in the switchover source site.

Creation of Information on L-Platform Templates for Active-Active Operation

Configure attributes of information on L-Platform templates as follows.

Table 3.2 Attributes to Configure for L-Platform Template Information
L-Platform Template Information	Attributes Shown As "Tenant"
Software information	Tenant information
Image information	Tenant information
Segment information	Tenant information
L-Platform template information	Tenant information

For details of information on L-Platform templates, refer to "7.4 Items to Set for Each Type of L-Platform Template Information" in the "User's Guide for Tenant Administrators CE".

Configurations when an L-Server Linked with a Configured Virtual Machine (VMware) is the Switchover Target

When L-Servers linked with configured virtual machines (VMware) are switchover targets, it is necessary to modify the configurations regarding the UUIDs of VM guests before performing switchover. Modify configurations following the descriptions in the VMware section in "Configuration Requirements for VM Guest Switchovers" in "9.2.1 Configuration Requirements" in the "Design Guide VE".

Configuration When Performing Virtual L-Server Switchover (VM Guest)

The advisory notes regarding performing virtual L-Server switchover (VM guest) are given below.

Set up the VM host on both the switchover source and destination sites.
Do not configure VM hosts on physical L-Servers.
Before performing switchover, perform the following preparations for the switchover destination site in order to be able to mount the replicated LUNs on the correct VM hosts. It is necessary to mount the replicated LUNs on the VM host connected with the images stored in each VM host registered in the VM pool used by L-Servers in the LUNs, or in VM hosts connected with the images stored in the LUNs.
- When using FC or iSCSI connection disks
  Configure the zoning and mapping settings so that the replicated LUNs can be referred to from the VM hosts.
- When using NAS connection disks
  - Operate the network links or the storage software so that the replicated LUNs can be mounted on the VM hosts.
  - Prepare the NFS connection information files that describe the information (NFS server addresses and NFS paths) for mounting each replicated LUN (datastore) in the following format. Use this file during the switchover procedure. For details, refer to "4.2 Switchover between Sites Using the Disaster Recovery Function".
    Datastore name, IP address or FQDN, NFS path
    Example
    storage_X,192.168.3.230,/nfs/data

[VMware]

Do not use multibyte characters for datastore names.
When using distributed virtual switches, the connections between the virtual machines and the port group of the distributed virtual switches in the switchover destination site cannot be restored. After switchover, configure the settings again.
When editing the destination VM files of the virtual machines through direct operation of VM management software, edit all VM files to deploy on the datastore in which the system disks or data disks of the virtual machines are located.
When editing the destination VM file through direct operation of VM management software, edit the VM file for a template (cloning image) to deploy in the datastore.
Only a datastore used by the switchover target L-Servers or cloning images can be mounted in the VM host, during the switchover procedure. When mounting a replicated datastore other than the above, manually mount it after switchover.
Once disks are deleted from a virtual machine in the switchover source site, any snapshots of the virtual machine taken before deletion of disks cannot be used on the switchover destination site. Therefore, you should delete old snapshots and take new ones after deleting disks from a virtual machine.
If snapshots taken before deletion of disks are not deleted, there will be the following effects on the switchover destination site:
- Unavailable snapshots consume disk resources.
- If the usage charge calculation function is enabled in the accounting settings, the usage charges for unavailable snapshots are calculated in the same way as available snapshots.