Use the following procedure to install required software and register a server Agent.
After Agent registration, the physical OS or VM host on which the Agent was installed will be displayed in the resource tree. Usually, a server Agent is automatically registered during server registration. In that case, this procedure can be skipped.
It is not necessary to re-install an already-setup operating system, required software, or Agent. Simply skip the steps that were already performed.
Install the operating system
Install the operating system on the managed server.
Set up the Admin LAN.
Set the Admin LAN IP address that was chosen for this server in "3.2.2 IP Addresses (Admin LAN)", as well as its corresponding network mask and default gateway.
Using storage devices in multi-path configurations
Install a multi-path driver. For VM hosts, use the one provided by default by either the operating system or virtualization software, when one is available.
When using SAN boot together with the HBA address rename function, the number of paths to be used should be set to the "HBA ports" option of the HBA address rename function (refer to step 2 in "6.2.2 Configuring HBA address rename").
The server is automatically restarted using a multi-path configuration.
Note
The server name (computer name for Windows or Hyper-V systems or a system node name for Linux, Solaris, VMware or Xen systems) defined during OS installation should be set according to the following guidelines.
[Windows/Hyper-V]
Enter no more than 63 characters, including alphanumeric characters, underscores ("_") or hyphens ("-").
The server name cannot be composed solely of numbers.
[Linux/VMware/Xen]
Enter no more than 64 characters, including alphanumeric characters as well as the following symbols.
"%", "+", ",", "-", ".", "/", ":", "=", "@", "_", "~"
[Solaris]
Enter no more than 24 characters, including alphanumeric characters, underscores ("_") or hyphens ("-").
As the computer name [Windows] or the system node name [Linux/VMware] is also used as the server's host name, it is recommended to use only the characters prescribed by RFC (Request For Comment) 952:
Alphanumeric characters
Hyphens, ("-")
Periods, (".") [Linux]
It is recommended not to use duplicate names for physical OS's, VM hosts and VM guests. Otherwise, Resource Coordinator VE commands will not function properly.
Install required software
Install the software packages that are required for a managed server.
Refer to "1.1.2.2 Required Software" of the "ServerView Resource Coordinator VE Installation Guide" for information on required software.
Install the Resource Coordinator VE Agent
Refer to "2.2 Agent Installation" of the "ServerView Resource Coordinator VE Installation Guide".
Register the Agent
Register the Agent from the RC console while the target server is running.
In the RC console resource tree, right-click the target server, and select [Registration]-[Agent] from the popup menu.
The [Agent registration] dialog is displayed.
Select the server OS type (physical OS, VM host).
For a Physical OS
Select "Windows/Linux".
For a VM host
Select "VM host", and enter the VM host login account information.
This login account information will be used by Resource Coordinator VE to control and communicate with the registered VM host.
For a SPARC Enterprise server
"Solaris" is selected by default. This option cannot be changed.
Enter the name of a user account with administrative authority over this VM host.
Enter the password of the above VM host user account.
Click the <OK> button.
The Admin Server starts to monitor and display server Information obtained from the agent.
Note
If a server on which an Agent was registered is shown as "unknown" in the resource tree, refer to "15.3 "unknown" Server Status" in the "ServerView Resource Coordinator VE Operation Guide" to fix its status.
When a server Agent is registered on a VM host, all VM guests running on that VM host are also registered automatically. Whenever a VM guest is created, modified, deleted or moved on a registered VM host, the changes are automatically updated in the resource tree.
The VM guest name displayed in the RC console is either the VM name defined in its virtualization software or the hostname defined in the guest OS.
The timing at which the hostname of a guest OS is detected and displayed varies according its virtualization software.Refer to "A.3 Functional Differences between Products" for details.
When registering a server on which the Agent was installed, it is necessary to either reboot the server or restart its "Deployment service" (explained in the "5.2 Agent" section) after server registration. This step has to be done before running any image operation (system image backup or cloning image collection).
For information on re-starting Agents, refer to the "5.2 Agent"section.
A server running a VM host can still be registered as a physical OS if its selected Server OS category is set to "Windows/Linux". A VM host server that was mistakenly registered as a physical OS should be deleted and re-registered as a VM host.
