Preparations
Physical L-Server
For details, refer to the procedure in "D.2 Preparations for Servers" in the "Design Guide CE".
Virtual L-Server
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 all of the following conditions, an IP address that has been allocated in a virtual machine can be imported to L-Server.
The virtualization software is VMware.
The power status of the virtual machine is "ON".
VMware Tools is operating on the virtual machine and it detects its IP address.
Confirm the following on the virtualization software (vSphere Client).
That the [VMware Tools] label on the [Summary] tab shows [OK]
That the [IP Addresses] label on the [Summary] tab shows an IP address configured for the virtual machine
Only an IPv4 address is set for the NIC on the guest OS of a virtual machine.
Check that an IPv6 address has not been set.
Note
Note that if you add a NIC from the OS, an IPv6 address might be allocated automatically.
Resource Orchestrator detects the virtual machine
After the virtual machine is powered on, wait for six minutes.
The network resource meets all of the following conditions
The network resource has been registered in a resource pool that the user can access.
The IP address allocated to the virtual machine is included within the range of IP addresses of the network resource.
The VLAN ID of the virtual machine is the same as that of the L-Server.
Multiple network resources with same subnet address are not registered with different VLAN IDs.
In environments where VLAN IDs cannot be acquired from virtual machines, only one network resource including the range of IP addresses allocated to a virtual machine is registered in an accessible resource pool.
In this case, ensure that there are not multiple network resources with the same range of IP addresses.
Note
By Resource Orchestrator, when vSphere Distributed Switch (vDS) is used, VLAN IDs cannot be acquired from virtual machines.
For details on the setup of vDS, refer to "E.1.4 Network Preparations" in the "Design Guide CE" and the manual of virtual software.
The VM host's network information has been updated.
On the virtual software (vSphere Client), network information is updated using the following procedure.
This should be done for all the VM hosts.
Click the [Hosts and Clusters] in the Inventory of category on the vSphere Client.
Select the VM host to update the information for.
Click the [Configuration] tab.
Click the [Networking] link on the [Hardware] in the left side of the pane.
Click the [Refresh] link on the top side of the pane and confirm to finish the update task
Reflect the current status of the VM management software on Resource Orchestrator
Execute the following command on the admin server.
[Windows Manager]
>Installation_folder\SVROR\Manager\bin\rcxadm vmmgr refresh <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm vmmgr refresh <RETURN> |
Setup
Register the resources of configured physical servers and VM hosts to Resource Orchestrator.
When linking configured physical servers with physical L-Servers
When linking a configured physical server to an L-Server, perform the following procedure:
Register Resources
Register Storage Management Software
Register Managed Servers
Register Resources in Resource Pools
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.
Register the disks that are connected to the physical server to be linked with the L-Server in a storage pool.
Register address set resources.
Specify the scope including MAC/WWN addresses being used by the configured physical server.
Register network resources.
Specify the subnet address and subnet mask that includes the IP address used by the physical server to be linked with the L-Server.
For details, refer to "14.3 Network Resources" and "14.3.1 Creating New Network Resources".
Note
Do not include the IP address planned to be used by the L-Server to be linked with a physical server in [Exclusion IP range]. If such an IP address is included, it will not be imported.
When linking configured virtual machines with virtual L-Servers
When linking a configured virtual machine to an L-Server, perform the following procedure:
Register Resources
Register VM Management Software
Register Managed Servers
Register Resources in Resource Pools
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".
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 (Solaris 10)] [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.
Register network resources.
Specify the subnet address and subnet mask that includes the IP address used by the virtual machine to be linked with the L-Server.
For details, refer to "14.3 Network Resources" and "14.3.1 Creating New Network Resources".
Note
When importing the IP address assigned to the virtual machine to an L-Server [VMware]
Do not include the IP address planned to be used by the L-Server to be linked with a virtual machine in [Exclusion IP range]. If such an IP address is included, it will not be imported.
Management of an allocated IP address
Perform this when you import the IP address allocated to the virtual machine to an L-Server.
Refer to the "Point" of "Preparations" and check that the prerequisites are met.
For details on setup of management of an allocated IP address, refer to "Table 17.17 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
Physical L-Server
A virtual L-Server that can operate a server
When [Server,Storage] is displayed
A virtual L-Server that can operate a server or storage
When [Server,Storage,Network] is displayed
A virtual L-Server with an IP address managed using Resource Orchestrator that 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
Physical L-Server
A virtual L-Server that can operate a server
When [Server,Storage] is displayed
A virtual L-Server that can operate a server or storage
When [Server,Storage,Network] is displayed
A virtual L-Server with an IP address managed using Resource Orchestrator that can operate a server or storage
