IBM RS/6000 SP, Problem Determination Manual

Page: 145 / 316

This soft copy for use by IBM employees only.
Chapter 5. System Partitioning
This chapter describes System Partitioning in a way that will enable the reader
to understand how all the key components fit together, and give an
understanding of how to carry out problem determination based on this
information.
The way in which the RS/6000 SP can be partitioned is dependent on the
topology of the High Performance Switch, and so this is where the topic is
started after a brief introduction. Even in those instances where the High
Performance Switch is not installed, System Partitioning follows the topology of
what it would expect to see if a High Performance Switch was installed in each
frame. It is essential that the reader fully understands the information laid out in
the previous chapter on the High Performance Switch before beginning to read
the following details about System Partitioning.
5.1 Scope, Rules, and Limitations
It is important to understand which components are affected by System
Partitioning before carrying out any of the associated procedures. In this way
you can prevent many of the problems that you might otherwise encounter.
In addition, it may be of assistance in deciding whether System Partitioning is
suitable for the environment or what is the most suitable configuration to choose.
5.1.1 Scope of System Partitioning
The following components of the POWERparallel System Support Programs are
affected by System Partitioning:
• High Performance Switch
•
The Heartbeat
• System Data Repository (SDR)
•
Job Manager
These topics will be dealt with individually in far greater detail later in the
chapter, but it is worth noting that all these components maintain a completely
separate and non-interfering environment in each partition that you set up. The
reorganization of these subsystems is largely managed by the scripts that are
provided in POWERparallel System Support Programs Version 2.1 that can be
run from the SMIT screens for System Partitioning. You can use the following
SMIT fastpath, for example:
# smit syspar
Many components remain systemwide and are not affected by System
Partitioning. These components continue to be administered in exactly the same
manner both before and after setting up the partitions. Some examples are:
•
Kerberos
•
User Management
•
Accounting

Copyright IBM Corp. 1996
125