This section explains advisory notes for Hyper-V usage.
Operating Systems for which Parameters can be Set and the Prerequisites for Performing the Settings
Depending on the server virtualization software used, some restrictions may apply to the operating systems that parameters can be set for and the prerequisites for performing the settings.
For details, refer to the manual of server virtualization software.
VMware ESX Management
VMware ESX can be managed by SCVMM, but only VM host for Hyper-V can be managed when using SCVMM in Resource Orchestrator.
Management of Citrix(R) XenServer(R)
Citrix(R) XenServer(R) can be managed by Microsoft(R) System Center 2012 Virtual Machine Manager or a later version, but only VM hosts for Hyper-V can be managed when using SCVMM.
Attaching and detaching of disks
Data disks are connected to the L-Server as SCSI disks. They cannot be connected as IDE disks.
14 data disks are connected to the first SCSI card, and 15 data disks are connected to each of the second to fourth SCSI cards.
When changing the configuration, a maximum of up to four disks can be specified at one time. To perform addition of five or more disks, please perform an additional configuration change.
Adding data disks while the L-Server is operating is possible except when additional SCSI cards become necessary.
Second Generation Virtual Machines
Second generation virtual machines are not supported.
Even when the Hyper-V of the VM host in Resource Orchestrator is Windows Server 2012 R2, only first generation virtual machines are supported.
Snapshot
The Resource Orchestrator snapshot uses the checkpoint function of SCVMM. To collect snapshots, sufficient free space is necessary to create a difference disk on the storage destination of VM guest.
When connecting the VM management software using the path through disk, snapshot creation will fail.
Operation with snapshots collected is not recommended due to the following reasons:
When snapshots are collected, operation uses disk difference, and performance may deteriorate.
If a snapshot is created from a VM guest that has been moved between servers (migration), and the snapshot is restored to a different VM host, the status on SCVMM becomes "Stored" and the VM may not be able to be started. In this situation, it is necessary to return the VM guest to the VM host from which the snapshot was collected and then start it.
For combining of difference disks, it is necessary to delete not only all snapshots collected using Resource Orchestrator, but also all checkpoints created using VM management software. Combining of the disk is automatically performed by SCVMM, but depending on the status of the VM guest, the operation may take a long time, because it is only performed while the target VM guest is stopped.
Information
The snapshot function provided by server virtualization software records the disk from the last update. Consequently, when a disk failure occurs, the snapshot function becomes unavailable at the same time.
Snapshot can be used as a corrective measure for problems such as the following:
Example
For recovery when a problems occurs with the applied patch
For recovery when a problem occurs when changing operating system parameters
L-Server Parameter Details [General] Tab
When a guest OS that Hyper-V supports is specified for the OS type, a converged network adapter will be added to VM.
When another OS has been selected, an emulated network adapter will be added.
When using a converged network adapter, it is necessary to install a virtual guest service on the guest OS.
For details on virtual guest service installation, refer to the Help of SCVMM.
L-Server Parameter Details [Server] Tab
If an unsupported OS type is specified, there is a chance that installation may fail or the OS of the VM guest may not operate correctly.
Additionally, if an incorrect OS type is specified, there is a chance that image collection or L-Server creation for a specified image may fail, and a guest OS may start but hang while awaiting entry. This occurs because Microsoft's Sysprep cannot be processed correctly during personalization processing.
The OS types displayed in the list are the guest OSs which can be specified on the SCVMM management console.
Resource Orchestrator displays all guest OSs in the list in order not to limit user selection, however this does not mean that all guest OSs are supported by SCVMM.
Hyper-V does not support some server type settings such as number of CPUs depending on the OS type. When an incorrect OS type and server type are selected, operation is not guaranteed.
Additionally, even when a service pack is not listed in the OS type list, it may be necessary to install the service pack.
When a guest OS that Hyper-V supports is specified for the OS type, a converged network adapter will be added to VM.
When a different OS has been selected, an emulated network adapter will be added.
For details on the guest OSs supported by SCVMM, refer to the Help of SCVMM.
For details on the guest OSs supported by Hyper-V, refer to the following Microsoft web site.
Microsoft download web site
URL: http://technet.microsoft.com/en-US/library/cc794868(v=ws.10).aspx |
L-Server Parameter Details [Disk] Tab
When creating an L-Server or changing the configuration, a maximum of four disks can be specified at one time.
To perform addition of five or more disks, please perform an additional configuration change.
L-Server Parameter Details [Network] Tab
IP addresses can be automatically configured, on the following guest OSs on which the integrated services are installed.
Microsoft(R) Windows Server(R) 2012 R2
Microsoft(R) Windows Server(R) 2012
Microsoft(R) Windows Server(R) 2008 R2
Microsoft(R) Windows Server(R) 2008
Microsoft(R) Windows Server(R) 2003 R2
Microsoft(R) Windows Server(R) 2003
Microsoft(R) Windows(R) 8.1
Microsoft(R) Windows(R) 8
Microsoft(R) Windows(R) 7
Microsoft(R) Windows Vista(R)
DVD Disk Operations
DVD disk operations cannot be performed for L-Servers. When using a DVD, use VM management software functions.
Automatic Network Configuration with Intel PROSet for Blade Servers
The VLAN functions of Intel PROSet are not supported by Resource Orchestrator. Do not use the VLAN functions of Intel PROSet.
User Accounts used when logging in to the SCVMM server must belong to the Administrator's group of each managed server.
With SCVMM, NIC information of a managed server recognized once is not updated even if the NIC information is changed.
When changing the Intel PROSet settings of a managed server, use the following procedure to make SCVMM re-realize the NIC information:
Disable the virtual NIC of Intel PROSet using the Device Manager of the managed server (Hyper-V).
In the SCVMM management console of the admin server (SCVMM), right-click the target host, then select [Refresh].
Change the settings of Intel PROSet, and enable the virtual NIC using the Device Manager of the managed server (Hyper-V).
In the SCVMM management console of the admin server (SCVMM), right-click the target host, then select [Refresh].
If the information recognized by SCVMM is not reflected even after performing the above operations, follow the steps below to release and reconfigure Intel PROSet.
Cancel teaming settings for Intel PROSet on the managed server (Hyper-V).
In the SCVMM management console of the admin server (SCVMM), right-click the target host, then select [Refresh].
Reconfigure teaming settings for Intel PROSet on the managed server (Hyper-V).
In the SCVMM management console of the admin server (SCVMM), right-click the target host, then select [Refresh].
When setting "ALB" for the teaming mode of Intel PROSet, disable the RLB (Receive Load Balancing) function. This configuration is not supported by Hyper-V.
Do not disable NIC devices teamed using Intel PROSet.
Note
If this procedure is not performed correctly, automatic network configuration will fail.
Alive Monitoring Settings
In Resource Orchestrator, alive monitoring functions are enabled by using heartbeat function for Virtual machine resources on MSFC.
The default settings of heartbeat differ depending on the host OS versions. In Resource Orchestrator, if the alive monitoring settings are not specified during creation of L-Servers, the heartbeat settings are disabled, regardless of the default settings.
In order to enable the heartbeat function, enable the alive monitoring function of Resource Orchestrator first.
Information
When using the following OS, the MSFC functions corresponding to these settings are disabled.
Microsoft(R) Windows Server(R) 2008 R2
When using the following OS, the MSFC functions corresponding to these settings are enabled.
Microsoft(R) Windows Server(R) 2012 R2
Microsoft(R) Windows Server(R) 2012
Default Library Server of SCVMM
Do not delete the default library server and library share of SCVMM because it is used as a temporary storage area when creating virtual L-Servers.
Creating virtual L-Servers will fail if they are deleted.
Movement of Storage Areas
When using movement of storage areas, check the following advisory notes.
When disk resources are moved to a newly created Cluster Shared Volume (CSV) which has not yet been detected by Resource Orchestrator, the information of moved disk resources is reflected as follows:
The newly created CSV is detected as a virtual storage resource during regular update.
After being detected as virtual storage resources, the information of moved disk resources is reflected on Resource Orchestrator.
