Step 5: Install and configure the host (Hyper-V)

You can install Microsoft Hyper-V Server on any server that meets the requirements for Lenovo XClarity Administrator.

Before you begin

If you intend to implement a high-availability environment, see Implementing high availability (Hyper-V) for more information about setting up the Microsoft Hyper-V cluster.

Ensure that the host meets the prerequisites that are defined in Hardware and software prerequisites.

Ensure that the host system is in the same network as the devices that you want to manage.

Ensure that you configure failover for the network adapters using the tools that are provided by the vendor who supplies the network adapters.

Important

You can setup XClarity Administrator on any system that meets the requirements for XClarity Administrator, including a managed server. If you use a managed server for the XClarity Administrator host:

You must implement either a virtually separate data and management network topology or a single data and management network topology.
You cannot use XClarity Administrator to apply firmware updates to that managed server. Even when only some of the firmware is applied with immediate activation, XClarity Administrator forces the target server to restart, which would restart XClarity Administrator as well. When applied with deferred activation, only some firmware is applied when the XClarity Administrator host is restarted.
If you use a server in a Flex System chassis, ensure that the server is set to automatically power on. You can set this option from the CMM web interface by clicking Chassis Management > Compute Nodes, then selecting the server, and selecting Auto Power for the Auto Power On Mode.

Procedure

To install Hyper-V locally on a managed server, you can use an externally powered DVD-ROM drive. To install Hyper-V remotely, use the remote-control function that is provided through the management controller on the managed server.

Complete the following steps to install and configure Hyper-V Server on the host.

Additional instructions are provided by Microsoft on the Install Hyper-V Server website.

To install Hyper-V locally:
Complete the following steps to access the managed server, and install Hyper-V locally.
1. Download the Microsoft Windows 2012 r2 image, and burn a DVD-ROM of the image.
2. Connect the console-breakout cable to the KVM connector on the server.
  Figure 1. Console breakout-cable and front bezel of a server
3. Attach an externally powered DVD-ROM drive, keyboard, mouse, and console to the console-breakout cable.
4. After inserting the DVD-ROM, power on the server.
5. From the splash screen, press F12, and select the device from which to boot the server (such as management controller: CD/DVD), and continue the installation process.
6. Complete the installation, ensuring that you configure an administrator password for the server.
7. When installation is complete, restart the server.
8. Optional: To support failover between redundant adapters, configure NIC teaming.
  For information about setting up NIC teaming in Microsoft 2012, see the NIC Teaming Overview website.
  Enable NIC teaming on the server:
  1. From Server Manager, click Local Server.
  2. In the Properties sections, set NIC Teaming to Enabled.
  Configure NIC teaming:
  1. From the NIC Teaming page, click the server.
  2. In the Teams section, click Tasks > New Team.
  3. Fill in the team name, and select the new adapters to include in the team.
  Note
  For this scenario, do not specify VLAN IDs at this point because it would apply VLAN tags to the host interface (and all packets would get the same tag). Because we are implementing a virtually separate management and data network, the VLAN tags (one set for data package and one set for management packets) must be applied to the virtual interfaces.
9. Add the Hyper-V feature to this server:
  1. From the Server Manager Dashboard, click Add roles and features.
  2. Ensure that the installation type is role-based or feature-based installation.
  3. Ensure that this server is selected.
  4. Select the Hyper-V server role, and click Next.
  5. Select the Ethernet adapter to create a virtual switch for the adapter.
  6. Continue through the wizard. When complete, click Install.
  7. Restart the server to apply the changes.
    When you log back in, the Hyper-V role is displayed in the server navigation pane of the Server Manager Dashboard.
10. From Virtual Switch Manager, create the virtual switch, and assign the virtual switch to the NIC team that you defined.
  1. From Administrative Tools, start Hyper-V Manager.
  2. Under Actions, click Virtual Switch Manager.
  3. Click Create Virtual Switch, and follow the wizard.
    Tip
    The adapter is listed under Connection Type as Microsoft Network Adapter Multiplexor Driver.
To install Hyper-V remotely:
Complete the following steps to access the managed server, and install ESXi remotely.
1. Download the Microsoft Windows 2012 r2 image, and burn a DVD-ROM of the image.
2. Start a remote control session to the server from the management-controller interface.
  1. Point a browser to the management-controller IP address for the server.
  2. Log on to the management-controller interface.
  3. From the System Status page, click Remote Console.
  4. Follow the instructions to start a remote-console session:
    Figure 2. Example of a remote-control session
3. Click Tools > Virtual Media.
4. Click Add Image, and browse to find the location of the .ISO image on the client workstation. Then, click Open to mount the image.
5. Click Tools > Power > On to start the server.
6. From the splash screen, press F12, and select the device from which to boot the server (such as management controller: CD/DVD), and continue the installation process.
7. When prompted to select a disk drive to install:
  - If you are installing to a local disk drive, select a disk drive with a minimum of 192 GB of space plus the size of the installation image.
  - If you are implementing a high-availability solution for XClarity Administrator, which uses the high-availability function that is provided by Hyper-V, see Implementing high availability (Hyper-V) for considerations about the storage to be chosen. You must set up that storage before you continue with the installation process.
8. When installation is complete, restart the server to see the IP address of the host.
9. Optional: To support failover between redundant adapters, configure NIC teaming.
  For information about setting up NIC teaming in Microsoft 2012, see the NIC Teaming Overview website.
  1. Enable NIC teaming on the server:
    1. From Server Manager, click Local Server.
    2. In the Properties sections, set NIC Teaming to Enabled.
  2. Configure NIC teaming:
    1. From the NIC Teaming page, click the server.
    2. In the Teams section, click Tasks > New Team.
    3. Fill in the team name, and select the new adapters to include in the team.
    Note
    For this scenario, do not specify VLAN IDs at this point because it would apply VLAN tags to the host interface (and all packets would get the same tag). Because we are implementing a virtually separate management and data network, the VLAN tags (one set for data package and one set for management packets) must be applied to the virtual interfaces.
10. Add the Hyper-V feature to this server:
  1. From the Server Manager Dashboard, click Add roles and features.
  2. Ensure that the installation type is role-based or feature-based installation.
  3. Ensure that this server is selected.
  4. Select the Hyper-V server role, and click Next.
  5. Select the Ethernet adapter to create a virtual switch for the adapter.
  6. Continue through the wizard. When complete, click Install.
  7. Restart the server to apply the changes.
    When you log back on, the Hyper-V role is displayed in the server navigation pane of the Server Manager Dashboard.
11. From Virtual Switch Manager, create the virtual switch, and assign the virtual switch to the NIC team that you defined.
  1. From Administrative Tools, start Hyper-V Manager.
  2. Under Actions, click Virtual Switch Manager.
  3. Click Create Virtual Switch, and follow the wizard.
    Tip
    The adapter is listed under Connection Type as Microsoft Network Adapter Multiplexor Driver.

Give documentation feedback