This section explains how to register managed servers.
The following features are available for managed servers.
Without a registered agent
HBA address rename settings
Cloning image deployment
Being allocated as a spare server for the Auto-Recovery of other servers
Allocation of a spare server for Auto-Recovery
VLAN settings on LAN switch blades
With a registered agent
HBA address rename settings
Backup and restore of system images
Cloning image deployment
Being allocated as a spare server for the Auto-Recovery of other servers (only applicable when using VMware HA)
Server hardware monitoring
Automatic detection and monitoring of VM configurations (both VM hosts and VM guests)
Network Map display of VM resources (blade servers only): VM hosts, VM guests and virtual switches
Allocation of a spare server for Auto-Recovery
VLAN settings on LAN switch blades
Note
If a managed server whose agent was registered appears as "unknown" on the resource tree, refer to "15.3 "unknown" Server Status" in the "ServerView Resource Coordinator VE Operation Guide" to resolve any issue that this server may be experiencing.
To register a blade server (PRIMERGY BX series) or PRIMERGY Partition Model, its enclosing chassis must be registered first.
When using VIOM for I/O virtualization, VIOM server profiles should be registered in advance according to the procedure described in "6.1.1.1 Registering VIOM Server Profiles".
To register servers other than PRIMERGY BX servers, refer to "6.1.3.2 Registering Rack Mount or Tower Servers".
Figure 6.1 Status Transition Diagram for Managed Servers
Use the following procedure to register blade servers and PRIMERGY Partition Model servers:
In the RC console resource tree, right-click an unregistered server blade or partition in the target chassis, and select [Register]-[Server] from the popup menu.
The [Register Server] dialog is displayed.
In the [Register Server] dialog, enter the following items.
Enter a name to assign to this physical server.
Enter up to 15 characters, including alphanumeric characters and hyphens ("-"). This name should start with an alphabet character.
Enter the IP address used by this server on the admin LAN.
When IP address is displayed
Entering an admin LAN (IP address) is not required.
Agents are automatically registered.
Note
- If ServerView Agent (mandatory software) is not running, "Message number 67231" will be displayed. In this case, server registration succeeds but the agent is not registered.
- If the admin LAN (IP address) of servers not running a physical OS or a VM host are displayed, old information may have been being displayed. After cancelling the registration, right-click the chassis on the resource tree and select [Update] from the popup menu to request an update of hardware properties. The IP address is updated to the correct value (it takes several seconds to obtain the information and to update).
When IP address is not displayed
Enter the IP address of this server's admin LAN network interface.
The Agent will not be registered automatically, but can be manually registered after server registration if necessary. After registering servers, register agents as required.
Information
When a physical OS and VM host are running on this server, the admin LAN (IP address) may be obtained automatically.
After cancelling the registration, right-click the chassis on the resource tree and select [Update] from the popup menu to request an update of hardware properties.
If the IP address is not shown after going through the above procedure, set it by manually entering the IP address manually and registering the server.
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 name and password input fields. Those refer to the user name and password entered during installation of this 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.
Enter the user name to log in to the VM host. Specify a user name 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 "3.2.1 Network Configuration".
If an incorrect network interface is used, Resource Coordinator VE will not be able to detect the correct IP address from the operating system running on the target server.
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.
When registering a newly-mounted PRIMERGY BX 900 server, the recognition of this server's admin LAN MAC address may take time and cause registration failures (showing error Message number 61142).
In such cases, after the registration has failed, right-click the target server and select [Update] from the popup menu to request an update of hardware properties. This will update the MAC address to the correct value. This may also take a few minutes to obtain hardware information and update internal properties.
Confirm that the correct MAC address is displayed for this server in the [Resource Details] tab before registering the server again.
A server running a VM host can still be registered as a physical OS if its 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.
Click <OK>.
The registered server will be displayed under the resource tree.
Note
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 resource tree.
The VM guest name displayed in the RC console is either the VM name defined in its server 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 server virtualization software. For details, refer to "A.3 Functional Differences between Products".
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 "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.
This section explains how to register a rack mount or tower server.
Figure 6.2 Status Transition Diagram for Managed Servers
Use the following procedure to register rack mount and tower servers:
In RC console resource tree, right-click "Server Resources", and select [Register]-[Server] from the popup menu.
The [Register Server] dialog is displayed.
In the [Register Server] dialog, enter the following items.
Input items differ depending on whether the "Register agent" checkbox is selected, as described below. If selected, Resource Coordinator VE will attempt to detect and register agents after server registration. Otherwise, agents will not be detected, but can later be registered if required.
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 as necessary.
Without Agent registration
Physical server name
Remote Management Controller
IP address
User name
Password
Server management software (ServerView)
Association with server management software (ServerView)
SNMP community
Admin LAN
IP address
MAC address (NIC1)
SAN Boot/Admin LAN Redundancy
MAC address (NIC2)
Automatic registration of agents is not performed after server registration. After registering servers, register agents as required.
With Agent registration
Physical server name
Remote Management Controller
IP address
User name
Password
Server management software (ServerView)
Association with server management software (ServerView)
SNMP community
Admin LAN
IP address
Server OS
Category
Admin LAN redundancy
MAC address (NIC2)
Agents are automatically registered after server registration is completed.
Enter a name to assign to this physical server.
Enter up to 15 characters, including alphanumeric characters and hyphens ("-"). This name should start with an alphabet character.
Enter the IP address of this server's remote management controller.
Enter the name 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 servers
Select "Enable" and enter a SNMP community name.
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 up to 32 characters, including 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" option is selected.
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.
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 name and password input fields. Those refer to the user name and password entered during installation of this 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.
Enter the user name to log in to the VM host. Specify a user name that has VM host administrator authority.
Enter the password of the user to log in to the VM host.
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.
Note
For details about the network interface(s) used on the admin LAN, refer to "3.2.1 Network Configuration".
If an incorrect network interface is used, Resource Coordinator VE 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 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.
Click <OK>.
The registered server will be displayed under the resource tree.
Note
After registering the agent, please verify that the information registered for the remote management controller is correct. This can be verified by trying out power operations (from Resource Coordinator VE) against that server. Refer to "Chapter 6 Power Control" in the "ServerView Resource Coordinator VE Operation Guide" 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 boot properly, make sure 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 resource tree.
The VM guest name displayed in the RC console is either the VM name defined in its server 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 server virtualization software. For details, refer to "A.3 Functional Differences between Products".
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 "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.
This section explains the method for registering SPARC Enterprise servers.
Use the following procedure when registering SPARC Enterprise servers:
In RC console resource tree, right-click "Server Resources", and select [Register]-[SPARC Enterprise] from the popup menu.
The [Register SPARC Enterprise] dialog is displayed.
In the [Register SPARC Enterprise] dialog, enter the following items.
Physical server name
"Register agent" checkbox
Remote Management Controller (XSCF)
IP address
User name
Password
SNMP community
Admin LAN
IP address
With Agent registration
Server OS
Category
Enter a name to assign to this physical server.
Enter up to 15 characters, including alphanumeric characters and hyphens ("-"). This name should start with an alphabet character.
Without Agent registration
Automatic registration of agents is not performed after server registration.
After registering servers, register agents as required.
With Agent registration
Agents are automatically registered after server registration is completed.
Enter the IP address of this server's remote management controller (XSCF).
Enter the name of a XSCF user account with administrative authority over this server.
Enter up to 31 characters, including alphanumeric characters, underscores ("_"), or hyphens ("-"). This name should start with an alphabet character.
This user should have "platadm" privileges for XSCF.
Enter the password of the above XSCF user account.
Enter up to 32 characters, including alphanumeric characters and any of the following symbols.
"!", "@", "#", "$", "%", "^", "&", "*", "[", "]", "{", "}", "(", ")", "-", "+", "=", "~", ",", ">", "<", "/", "'", "?", ";", ":"
Enter the SNMP community that was set on this server's remote management controller (XSCF).
Either select "public" or enter an arbitrary string.
Enter up to 32 characters, including alphanumeric characters, underscores ("_"), and hyphens ("-").
Enter the IP address used by this server on the admin LAN.
"Solaris" is selected by default. This option cannot be changed.
Click <OK>.
The registered server will be displayed under the resource tree.
Note
After registering the agent, please verify that the information registered for the remote management controller is correct. This can be verified by trying out power operations (from Resource Coordinator VE) against that server. Refer to "Chapter 6 Power Control" in the "ServerView Resource Coordinator VE Operation Guide" for details on power operations.
