Single host configuration for HMC-managed hosts

Edit online

This is the simplest IBM® Power® Virtualization Center configuration. In this configuration, you have a single host that acts as the management server and the managed host. This configuration is useful if you want to try PowerVC in your environment with a minimum amount of resources. These components are required, but PowerVC does not manage the networks, router, or workstation.

Single host configuration with NPIV attached storage

This figure shows a single Power Systems host being used as the management server in a PowerVC environment. It is connected to SAN storage through a single SAN switch. There are two network switches: one for data and one for the management network. There is an HMC in this environment as well.
Table 1. Components of this single host configuration
Component Description
Host There is one host in this sample that acts as both the PowerVC management server and the managed host. The host is managed by a Hardware Management Console. The host has a Virtual I/O Server on it as well as a second Red Hat® Enterprise Linux® virtual machine where PowerVC is installed and running.
Network It is best practice to have separate management and data networks, each with their own switches to isolate and secure the traffic, so that is what is shown here. For trial purposes, you could use a single network switch for both networks. The data network is backed by a Shared Ethernet Adapter on the Virtual I/O Server.
Storage There is a single storage provider that uses a single NPIV-capable SAN switch. The Virtual I/O Server on the host has access to the SAN using a Fibre Channel connection. The Linux virtual machine on the host has access to the SAN storage through the Virtual I/O Server using virtual Fibre Channel.
Virtual assets In this example, there are multiple virtual machines on the host apart from the Virtual I/O Server and the PowerVC virtual machine. There are three image volumes in the SAN; each contains an image that was captured using PowerVC. Virtual machines 3, 4, and 5 were the result of deploying those captured images. Virtual machine 1 was pre-existing on the host and was brought into PowerVC to be managed.

Refer to Planning for hosts, Planning for networks, and Planning for storage and the rest of the planning information for guidance on how to make the decisions you need to make to plan your own environment.

Single host configuration with vSCSI attached storage

This figure shows a single Power Systems host being used as the management server in a PowerVC environment. It is connected to SAN storage through a single SAN switch. There are two network switches: one for data and one for the management network. There is an HMC in this environment as well.
Table 2. Components of this single host configuration
Component Description
Host There is one host in this sample that acts as both the PowerVC management server and the managed host. The host is managed by a Hardware Management Console. The host has a Virtual I/O Server on it as well as a second Red Hat Enterprise Linux virtual machine where PowerVC is installed and running.
Network It is best practice to have separate management and data networks, each with their own switches to isolate and secure the traffic, so that is what is shown here. For trial purposes, you could use a single network switch for both networks. The data network is backed by a Shared Ethernet Adapter on the Virtual I/O Server.
Storage There is a single storage provider that uses a single virtual SCSI (vSCSI)-capable SAN switch. The Virtual I/O Server on the host has access to the SAN using a vSCSI connection. The Linux virtual machine on the host has access to the SAN storage through the Virtual I/O Server using vSCSI.
Important: Before using vSCSI on a host, you must set up zoning between all of the switches and that host. For information, see Planning for vSCSI storage.
Virtual assets In this example, there are multiple virtual machines on the host apart from the Virtual I/O Server and the PowerVC virtual machine. There are three image volumes in the SAN; each contains an image that was captured using PowerVC. Virtual machines 3, 4, and 5 were the result of deploying those captured images. Virtual machine 1 was pre-existing on the host and was brought into PowerVC to be managed.

Refer to Planning for hosts, Planning for networks, and Planning for storage and the rest of the planning information for guidance on how to make the decisions you need to make to plan your own environment.

Single host configuration with shared storage pool attached storage

This figure shows a single Power Systems host being used as the management server in a PowerVC environment. It is connected to SAN storage through a single SAN switch. There are two network switches: one for data and one for the management network. There is an HMC in this environment as well.
Table 3. Components of this single host configuration
Component Description
Host There is one host in this sample that acts as both the PowerVC management server and the managed host. The host is managed by a Hardware Management Console. The host has a Virtual I/O Server on it as well as a second Red Hat Enterprise Linux virtual machine where PowerVC is installed and running.
Network It is best practice to have separate management and data networks, each with their own switches to isolate and secure the traffic, so that is what is shown here. For trial purposes, you could use a single network switch for both networks. The data network is backed by a Shared Ethernet Adapter on the Virtual I/O Server.
Storage There is a single storage provider that uses a single virtual SCSI (vSCSI)-capable SAN switch. The Virtual I/O Server on the host has access to the SAN using a vSCSI connection. The Linux virtual machine on the host has access to the SAN storage through the Virtual I/O Server using vSCSI.
There is a single shared storage pool across all of the Virtual I/O Servers that use SAN storage. Volumes are created within the shared storage pool. The virtual machines on the host have access to the volumes in the shared storage pool through the Virtual I/O Server by using a vSCSI connection.
Important: Before using vSCSI on a host, you must set up zoning between all of the switches and that host. For information, see Planning for vSCSI storage.
Virtual assets In this example, there are multiple virtual machines on the host apart from the Virtual I/O Server and the PowerVC virtual machine. There are three image volumes in the SAN; each contains an image that was captured using PowerVC. Virtual machines 3, 4, and 5 were the result of deploying those captured images. Virtual machine 1 was pre-existing on the host and was brought into PowerVC to be managed.

Refer to Planning for hosts, Planning for networks, and Planning for storage and the rest of the planning information for guidance on how to make the decisions you need to make to plan your own environment.