This section explains how to register a rack mount or tower server.
Figure 5.3 Status Transition Diagram for Managed Servers
Use the following procedure to register rack mount or tower servers.
In the ROR console server resource tree, right-click [Server Resources], and select [Register]-[Server] from the popup menu.
The [Register Server] dialog is displayed.
To use this feature, the following settings must first be defined:
Enter items differ depending on whether the [Register agent] checkbox is selected, as described below.
If this checkbox is checked, agents will be registered after server registration.
If this checkbox is not checked, registration of agents will not be performed, so register agents after server registration when necessary.
Without Agent Registration
Physical server name
Remote management controller
IP address
User ID
Password
Association with server management software (ServerView)
Enable/Disable
SNMP Community
Admin LAN
IP address
MAC address (NIC1)
For physical L-Servers, specify the MAC address of the second specified NIC decided in "9.1.1 Admin LAN Network Design" in the "Design Guide CE".
SAN Boot/Admin LAN Redundancy
[Use Admin LAN redundancy] checkbox
MAC address (NIC2)
For physical L-Servers, specify the MAC address of the second specified NIC decided in "9.1.1 Admin LAN Network Design" in the "Design Guide CE".
Automatic registration of agents is not performed after server registration. After registering servers, register agents as required.
If registering agents, register agents after checking the product name is displayed in the General Area of [Resource Details] tab.
Executing [Update] acquires the latest information.
With Agent Registration
Physical server name
Remote management controller
IP address
User ID
Password
Association with server management software (ServerView)
Enable/Disable
SNMP Community
Admin LAN
IP address
Admin LAN Redundancy
[Use Admin LAN redundancy] checkbox
MAC address (NIC2)
For physical L-Servers, specify the MAC address of the second specified NIC decided in "9.1.1 Admin LAN Network Design" in the "Design Guide CE".
OS
Type
Agents are automatically registered after server registration is completed.
Enter a name to assign to this physical server.
Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-").
Enter the IP address of this server's remote management controller.
Enter the ID of a remote management controller user account with administrative authority over this server.
Enter up to 16 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
Enter the password of the above remote management controller user account.
Enter up to 16 characters, including alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
This field can be omitted if no password has been set for this user account.
For PRIMERGY BX servers
Select [Enable] and enter an [SNMP Community].
For servers other than PRIMERGY servers
Select [Disable].
By default, [Enable] is selected.
Enter the SNMP community that was set on this server.
Either select "public" or enter an arbitrary string.
Enter a string of up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Enter the IP address used by this server on the admin LAN.
Enter the MAC address of this server's admin LAN network interface.
Enter a MAC address in either one of the following two formats: hyphen-delimited ("xx-xx-xx-xx-xx-xx"), or colon-delimited ("xx:xx:xx:xx:xx:xx").
MAC addresses will be automatically detected when the [Register agent] checkbox is selected.
Check this when performing redundancy for the NIC on the admin LAN.
Enter the MAC address of the second admin LAN network interface. This network interface is to be used by the HBA address rename setup service, or to enable admin LAN redundancy on the registered server.
Enter a MAC address in either one of the following two formats: hyphen-delimited ("xx-xx-xx-xx-xx-xx"), or colon-delimited ("xx:xx:xx:xx:xx:xx").
This field can be omitted in the following cases.
- When not using the HBA address rename setup service
- When not using GLS for admin LAN redundancy on the managed server
- For a spare server whose primary servers are not using admin LAN redundancy
Check this when performing redundancy for the NIC on the admin LAN.
Enter the MAC address of the second admin LAN network interface. This network interface will be used to enable admin LAN redundancy on the registered server.
Enter a MAC address in either one of the following two formats: hyphen-delimited ("xx-xx-xx-xx-xx-xx"), or colon-delimited ("xx:xx:xx:xx:xx:xx").
This field can be omitted in the following cases.
- When not using GLS for admin LAN redundancy on the managed server
- For a spare server whose primary servers are not using admin LAN redundancy
This option is displayed if the target server runs a physical OS or VM host.
Select the appropriate server OS category (Physical OS or VM host).
Selecting [VM Host] activates the user ID and password input fields. Those refer to the user name and password entered during installation of this VM host.
Select the server OS category depending on whether the relevant server is used on a physical OS or a 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 Orchestrator to control and communicate with the registered VM host.
Enter the user ID to log in to the VM host. Specify a user ID that has VM host administrator authority.
Enter the password of the user to log in to the VM host.
Note
For details about the network interface(s) used on the admin LAN, refer to "9.1.1 Admin LAN Network Design" in the "Design Guide CE".
If an incorrect network interface is used, Resource Orchestrator will use a wrong MAC address for the admin LAN.
An admin LAN IP address is required even when registering a spare server.
Enter an IP address that does not conflict with the IP address of any other managed server on the admin LAN.
A server running a VM host can still be registered as a physical OS if its [Category] of [Server OS] is set to [Windows/Linux]. (For Windows Server 2008, etc.)
A VM host server that was mistakenly registered as a physical OS should be deleted and re-registered as a VM host.
When registering rack mount servers on which VMware ESXi is operating, select [Disable] for [Association with server management software (ServerView)] even when using PRIMERGY servers.
After registering the server, clear the [Register agent] checkbox and register the agent after registration of the server is complete.
Click <OK>.
The registered server will be displayed in the server resource tree.
Note
After registering the server, please verify that the information registered for the remote management controller is correct. This can be verified by trying out power operations (from Resource Orchestrator) against that server. Refer to "Chapter 14 Power Control" in the "User's Guide VE" for details on power operations.
When using HBA address rename setup service, please confirm that the registered server can boot properly using the HBA address rename setup service.
If the server cannot be booted properly, ensure that the specified MAC address (NIC2) is correct.
When an 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 server resource tree.
The VM guest name displayed in the ROR console is either the VM name defined in its server virtualization software or the host name defined in the guest OS.
The timing at which the hostname of a guest OS is detected and displayed varies according its server virtualization software. For details, refer to "D.3 Functional Differences between Products" in the "Design Guide VE".
It is recommended not to use duplicate names for physical OS's, VM hosts and VM guests. If duplicated names are used, those resources cannot be managed from the command-line.
When registering a server on which the agent was installed, it is necessary to either reboot the server or restart its related services (explained in the "2.2 Starting and Stopping the Agent" in the "Operation Guide CE") after server registration. This step has to be done before running any image operation (system image backup or cloning image collection).
For details on how to restart the agent, refer to "2.2 Starting and Stopping the Agent" in the "Operation Guide CE".
