Specifications

284 IBM Flex System p260 and p460 Planning and Implementation Guide
Each partition must have access to a system console. Tasks such as operating
system installation, network setup, and certain problem analysis activities require
a dedicated system console. The POWER Hypervisor provides the virtual
console using a virtual TTY or serial adapter and a set of Hypervisor calls to
operate on it. Virtual TTY does not require the purchase of any additional
features or software, such as the PowerVM Edition features.
For Power Systems compute nodes, the operating system console can be
accessed from IBM Flex System Manager.
7.1.3 Preparing to use the IBM Flex System Manager for partitioning
FSM is used to create virtual servers on Power Systems compute nodes. This
function is one of many provided by FSM.
It is presumed that FSM is set up so that it is managing the Enterprise Chassis
that contains the Power Systems compute node on which the virtual servers is
created. For more details, see Chapter 6, “Management setup” on page 157.
If you have experience using the Integrated Virtualization Manager, HMC, or the
Systems Director Management Console to create logical partitions or virtual
servers on any POWER7 system, the process is similar.
Removing an existing configuration
All Power Systems compute nodes are delivered preinstalled with an operating
system. In addition, if a IBM PureFlex System configuration was ordered, there is
a configuration on the Power Systems compute nodes in the chassis. The virtual
servers that are already configured must be removed if you want to create a
custom configuration.
Virtual server name, processor, and memory settings
Before beginning the virtual server creation tasks in FSM, document the basic
information about the virtual servers to be defined (Table 7-2).
Table 7-2 Virtual server name, processor, and memory planning information
Virtual server name Processor/UnCap/Weight Memory
node1
vios1 1/Y/200 2 GB
vios2 1/Y/200 2 GB
lpar1 3/Y/100 4 GB