Filter
Top Products
- When not performing admin LAN redundancy
Note
- For details about the network interface(s) used on the admin LAN, refer to "7.1 Network Configuration" in the "Design Guide
VE".
If an incorrect network interface is used, Resource Orchestrator will not be able to detect the correct admin LAN 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 BX900 server, as recognition of this server's admin LAN MAC address will
take time, error message number 61142 may be displayed.
In this case, after registration has been canceled, right-click the chassis on the server resource tree 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 correctly before registering the server again.
For details on the appropriate corrective action, refer to "Message number 61142" in "Messages".
- A server running a VM host can still be registered as a physical OS if its [Server OS category] 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.
- The same NIC cannot be selected for [Admin LAN (MAC address 1)] and [Admin LAN (MAC address 2)].
- For the following cases, after selecting [Disable MAC address 2] for [Admin LAN (MAC address 2)], the lowest numbered
NIC which is not used for [Admin LAN (MAC address 1)] is used for Admin LAN2.
- When using the HBA address rename setup service
- When performing admin LAN redundancy
3. Click <OK>.
The registered server will be displayed in the server 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 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 host name 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 OSs, 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 VE") 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 VE".
7.3.3 Registering LAN Switch Blades
To register a LAN switch blade, its enclosing chassis must be registered first.
Use the following procedure to register a LAN switch blade.
- 31 -