18.4.1 Preparations

Preparations

For Physical L-Servers
For details, refer to the procedure in "D.2 Preparations for Servers" in the "Design Guide CE".
For Virtual L-Servers
For details, refer to the procedure for each VM type in "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE".

Point

When it meets the following conditions, IP address that has been allocated in a virtual machine can be taken into L-Server.

Virtualization software is VMware.
A power status of the virtual machine is "ON".
VMware Tools is act on the virtual machine and it detects its IP address.
Please confirm the following status on the virtualization software (vSphere Client).
- Check the [VMware Tools] label on the [Summary] tab shows [OK]
- [IP Addresses] label on the [Summary] tab shows an IP address configured for the virtual machine
Only the IPv4 address is set to NIC on the guest OS of a virtual machine. The IPv6 address is not set.
Note
Notice that if you add a NIC over the OS, IPv6 address might be allocated automatically.
Resource Orchestrator detects this virtual machine (Wait for about six minutes after starting the virtual machine).
The network resource meets the following conditions
- The network resource has registered in the resource pool that the user can access.
- Within the range of IP address of the network resource, IP address allocated in a virtual machine is included.
- NIC of a virtual machine is the same as VLAN ID of NIC of L-Server.
- By different VLAN ID, two or more network resources with same subnet address are not registered.
- In the environment which cannot acquire VLAN ID from a virtual machine, only one network resource including the range of IP address allocated in a virtual machine is registered in an accessible resource pool.
  The two or more network resources with the same range of an IP address should not make it exist in the above-mentioned case.
Note
By Resource Orchestrator, when the vSphere Distributed Switch (vDS) is used, VLAN ID cannot be acquired from a virtual machine. For details on setup of vDS, refer to "E.1.4 Network Preparations" in the "Design Guide CE" and the manual of virtual software.
VM host's network information is updated.
On the virtual software (vSphere Client), network information is updated in the following procedures. It should be done for all the VM hosts.
1. Click the [Hosts and Clusters] in the Inventory of category on the vSphere Client Click the VM host in the inventory on the vSphere Client
2. Select the VM host which updates information
3. Click the [Configuration] tab
4. Click the [Networking] link on the [Hardware] in the left side of the pain
5. Click the [Refresh] link on the top side of the pain and confirm to finish the update task
Reflect the current status into the Resource Orchestrator
Execute the following command on the admin server.
[Windows]
Installation_folder\SVROR\Manager\bin\rcxadm vmmgr refresh
[Linux]
/opt/FJSVrcvmr/bin/rcxadm vmmgr refresh

Setup

When linking configured physical servers with physical L-Servers
When linking a configured physical server to an L-Server, perform the following procedure:
1. Register Resources
  1. Register Storage Management Software
  2. Register Managed Servers
2. Register Resources in Resource Pools
  1. Register physical server resources in a server pool.
    In the [Register Resources] dialog for the server pool, check the [Display servers with OS installed] checkbox and specify a physical server with an OS installed.
  2. Register the disks that are connected to the physical server to be linked with the L-Server in a storage pool.
  3. Register address set resources.
    Specify the scope including MAC/WWN addresses being used by the configured physical server.
  4. Register network resources.
    Specify IP addresses not being used by the configured physical server or the virtual machine.
    When the IP address used for a configured physical server, a virtual machine, or other devices is included in the subnet address scope, specify the IP address in the "IP addresses to be excluded".
When linking configured virtual machines with virtual L-Servers
When linking a configured virtual machine to an L-Server, perform the following procedure:
1. Register Resources
  1. Register VM Management Software
  2. Register Managed Servers
2. Register Resources in Resource Pools
  1. Register VM host resources in a VM pool.
    The overcommit attribute of the VM pool where the VM host is registered is set to L-Server.
    For details on creating a VM pool for overcommit, refer to "Chapter 20 Resource Pool Operations".
  2. Register the virtual storage and disks that are used for a virtual machine to be linked with the L-Server in a storage pool.
    [Solaris Zones] [OVM for SPARC]
    When a VM host not managed with server management software is used, it is not necessary to register virtual storage and disk resources.
  3. Register network resources.
    - When the IP address assigned to the virtual machine is taken into L-Server [VMware]
    Specify IP addresses not being used by the configured physical server.
    The IP address used for a virtual machine is included within the subnet address scope.
    - Case other than the above
    Specify IP addresses not being used by the configured physical server or the virtual machine.
    When the IP address used for a configured physical server, a virtual machine, or other devices is included in the subnet address scope, specify the IP address in the "IP addresses to be excluded".
3. Management of an allocated IP address
  Please perform, when you take into L-Server the IP address allocated to the virtual machine.
  Please check whether the precondition is filled with reference to the "point" of "Preparations".
  For details on setup of management of an allocated IP address, refer to "Table 17.6 List of Items Specified in the Definition File" of "17.8.1 Installation".
Note
When the virtual storage and disk resources that are used for a virtual machine to be linked with the L-Server are not registered in a storage pool, the amount of resources cannot be managed in the storage pool. However, the amount of resources can be linked with virtual L-Servers. Disks created on the virtual storage can be operated by the virtual L-Server.

Confirmation

Perform the procedure described in "18.4.2 For Physical Servers" or "18.4.3 For Virtual Machines", and confirm the configured physical server or virtual machine linked to an L-Server, using the following procedure:

Confirmation from the GUI
Select the L-Server in the orchestration tree, display the [Resource Details] tab, and check the information is displayed in [Controlled resources] on the [Status] table.
In [Controlled resources], the following text strings are displayed.
- When [Server] is displayed
  A physical L-Server
  A server can be operated by a virtual L-Server
- When [Server,Storage] is displayed
  A server or storage can be operated by a virtual L-Server
- When [Server,Storage,Network] is displayed
  The virtual L-Server which manage the IP address with this product and can operate a server or storage.
Confirmation from the Command Line
Execute the rcxadm lserver show command and check that the scope of the controlled resources (ControlledResources) is displayed.
For details, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
For the scope of controlled resources, the following text strings are displayed.
- When "Server" is displayed
  A physical L-Server
  A server can be operated by a virtual L-Server
- When "Server,Storage" is displayed
  A server or storage can be operated by a virtual L-Server
- When [Server,Storage,Network] is displayed
  The virtual L-Server which manage the IP address with this product and can operate a server or storage.