This section explains how to register resources with Resource Orchestrator.
Details | When Using Blade Servers (*1) | When Using Rack Mount or Tower Servers (*2) | When Using PRIMEQUEST (*3) | When Using Fujitsu M10/SPARC Enterprise (*3) |
|---|---|---|---|---|
Register VIOM | Yes | Yes (*4) | No | No |
Register VM management software | No | No | No | No |
Register server management software | No | No | No | No |
Register storage management software | Yes | Yes | Yes | Yes |
Register chassis | Yes | No | Yes | Yes (*5) |
Register admin LAN subnets (when there are multiple admin LAN subnets) | Yes | Yes | Yes | Yes |
Register managed servers (within chassis) | Yes | No | Yes | Yes (*5) |
Register managed servers | No | Yes | No | No |
Register LAN switch blades | Yes | No | No | No |
Configure VLANs for LAN switch blades manually | Yes (*6) | No | No | No |
Settings for the HBA address rename Setup Service | No | Yes (*7) | No | No |
Register virtual storage resources | Yes (*8) | No | No | |
Register disk resources | Yes (*9) | No | No | |
Register network resources | Yes | No | No | |
Register network device resources | Yes (*10) | No | No | |
Register Address Set Resources | Yes | No | No | |
Register physical image resources | Yes (*11) | No | No | |
Register virtual image resources | No | No | No | |
Configure power monitoring devices | Yes (*12) | No | Yes (*12) | |
Yes: Required
No: Not required
*1: PRIMERGY BX620 series servers can be used linked with physical L-Servers.
*2: PRIMERGY TX series and PRIMERGY RX100 series servers can be used linked with physical L-Servers.
*3: Configured physical servers can be used linked with physical L-Servers.
*4: Necessary when using rack mount servers which are supported by VIOM.
*5: Necessary when using SPARC Enterprise M4000/M5000/M8000/M9000 or FUJITSU M10-4S.
*6: Necessary when not using automatic configuration of LAN switch blade VLANs.
*7: Necessary when using rack mount servers which are not supported by VIOM.
*8: Necessary when using virtual storage resources such as RAID groups or aggregates.
*9: Necessary when using disk resources created in advance such as LUNs.
*10: Necessary when using firewalls, server load balancers, and L2 switches.
*11: Necessary when using images created in advance.
*12: Necessary when monitoring power consumption.
When Using Blade Servers
Registration of resources when creating a physical L-Server using a blade server is explained.
Register using the following procedure:
Register VIOM Coordination
Refer to "5.1 Registering VIOM Coordination" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Note
It is not necessary to register a VIOM server profile.
When creating a physical L-Server, VIOM server profiles are automatically created.
Register storage management software
When storage management software is registered, RAID groups or aggregates that were created during pre-setup preparations are automatically registered in Resource Orchestrator as virtual storage resources.
Execute the rcxadm storagemgr register command to register storage management software with Resource Orchestrator.
For details on the rcxadm storagemgr register command, refer to "5.17 rcxadm storagemgr" in the "Reference Guide (Command/XML) CE".
Note
If ETERNUS SF Storage Cruiser is specified as the storage management software, virtual storage resources and disk resources registered with ETERNUS SF Storage Cruiser will be recognized. Recognition targets are as follow.
Virtual storage resources
RAID groups
TPP
FTRP
Disk resources
Open volumes
TPV
FTV
LUN concatenated volumes and encrypted volumes will not be recognized.
Register chassis
Refer to "5.4.1 Registering Chassis" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register Managed Servers (within Chassis)
Refer to "5.4.2 Registering Blade Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When performing admin LAN NIC redundancy, check the [Use Admin LAN redundancy] checkbox in the [Register Server] dialog when registering the server.
When directly specifying an IP address during physical L-Server creation, do not configure the same IP address on a managed server.
An error will occur during the following operations, if there are managed servers configured with the same IP addresses as those allocated to physical L-Servers, in other than physical servers.
Create physical L-Servers
Starting of a physical L-Server for which only the configuration definition has been created
Note
When not using the default NIC, specify the NIC for admin LAN during the physical server registration.
For details, refer to the "[Apply Admin LAN NIC settings] checkbox" in "5.4.2 Registering Blade Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register LAN switch blades
Refer to "5.4.3 Registering LAN Switch Blades" and "5.13 Registering LAN Switches (L2 Switches)" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register network device resources
For details on how to register network device resources, refer to "5.7.2 Registering Network Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register power monitoring devices (when using devices)
Refer to "5.10 Registering Power Monitoring Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
To register a network resource or an address set resource, specify a resource pool when creating the resource.
Refer to "7.3 Registering Resources in Resource Pools".
When Using Something Other than a Blade Server
Registration of resources when creating a physical L-Server using a server other than a blade server is explained.
Register using the following procedure:
Register VIOM coordination or configure HBA address rename
When using rack mount servers which are supported by VIOM, manage them with VIOM.
Refer to "5.1 Registering VIOM Coordination" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using servers other than rack mount or tower servers, configure HBA address rename.
Refer to "5.5.2 HBA address rename Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register storage management software
Execute the rcxadm storagemgr register command.
For details on the rcxadm storagemgr register command, refer to "5.17 rcxadm storagemgr" in the "Reference Guide (Command/XML) CE".
When storage management software is registered, virtual storage resources and disk resources created in advance are automatically recognized.
Note
If ETERNUS SF Storage Cruiser is specified as the storage management software, virtual storage resources and disk resources registered with ETERNUS SF Storage Cruiser will be recognized. Recognition targets are as follow.
Virtual storage resources
RAID groups
TPP
FTRP
Disk resources
Open volumes
TPV
FTV
LUN concatenated volumes and encrypted volumes will not be recognized.
Register managed servers
Refer to "5.5.1 Registering Rack Mount or Tower Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When performing admin LAN NIC redundancy, check the [Use Admin LAN redundancy] checkbox in the [Register Server] dialog when registering the server.
When directly specifying an IP address during physical L-Server creation, do not configure the same IP address on a managed server.
An error will occur during the following operations, if there are managed servers configured with the same IP addresses as those allocated to physical L-Servers, in other than physical servers.
Create physical L-Servers
Starting of a physical L-Server for which only the configuration definition has been created
Register network device resources
For details on how to register network device resources, refer to "5.7.2 Registering Network Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register power monitoring devices (when using devices)
Refer to "5.10 Registering Power Monitoring Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
To register a network resource or an address set resource, specify a resource pool when creating the resource.
Refer to "7.3 Registering Resources in Resource Pools".
