When you have finished making configuration changes in the
nPartition Modify
action, this page gives you a chance to review the new configuration before
committing your changes. Information is provided under three tabs, described in the
following sections. You can visit the tabs in any order. You do not have to visit
each tab. You can revisit the same tab as many times as you like.
To complete the Modify nPartition action, click the
[Finish] button at the bottom of the page. This will apply your changes,
modifying the configuration of the nPartition.
If you decide not to make these changes to the nPartition, click the [Cancel]
button instead. You will return to the Modify
nPartition page. From there you can specify further changes or cancel the
entire action.
The following sections describe each of the tabs in this dialog.
Notes and Warnings Tab
This tab displays important information about the new configuration, including
steps that must or should be performed next, and warnings about potential issues
that you should understand. You should review the information in this tab
carefully before committing your changes. This tab is organized into the
following subsections, each of which will only be displayed if applicable to the
new configuration.
If you have modified the Hyper-Threading
setting for the nPartition, this section informs you that you must reboot the nPartition
for the change to take effect. Hyper-Threading can be enabled and
active.
Enabled means that Hyper-Threading will be
active on the next reboot of the nPartition.
Active means that each processor core in
the nPartition is simultaneously running multiple threads.
Required Next Steps
This section will be displayed if you are removing an active
cell from the nPartition. You will be given instructions for
performing a shutdown for reconfiguration. When the
nPartition reboots, the changes you have specified will take effect.
You can specify whether the nPartition should automatically reboot after the
shutdown for reconfiguration. If you select the option Boot
nPartition to system firmware user interface once modified, the
nPartition will be automatically booted to the user interface provided by
system firmware.
On PA-RISC systems the boot console handler will
provide the interface to specify the boot device.
On Itanium®-based
systems the EFI Boot Manager will provide the interface to specify
the boot device.
Notes and Warnings
If Partition Manager detected any high availability issues,
you will be referred to the HA Checks Tab for
further details.
If you have selected free cells to
be added to the nPartition, you will be reminded that these changes will not
take effect until a reboot for reconfiguration is
performed. You can continue to use the nPartition without these cells until it
is convenient to perform the reboot for reconfiguration.
If you have made changes to the configuration of interleaved
memory and cell local memory
(CLM), you will be reminded that these changes
will not take effect until the nPartition is rebooted. This does
not require a reboot for reconfiguration. You can continue
to use the nPartition with its present memory configuration until it is
convenient to reboot it.
Summary of Changes Tab
This tab displays each of the changes you have made to the configuration of this
nPartition, followed by the command that Partition Manager will use to modify the
nPartition when you click [Finish]. This command is displayed so that you
can verify that the correct options are being used to modify the nPartition, and
so that you can understand the relationship between Partition Manager options and
command options. For detailed information about command options, consult the
parmodify(1M)
manpage.
HA Checks Tab
This tab displays the results of the high availability
checks (HA checks) performed by Partition Manager. The results are summarized at the
top of the page, followed by the results of the individual checks.
The purpose of the high availability checks is to ensure that if some part of the
nPartition fails (such as a processor or a DIMM), the nPartition has adequate
resources to continue running. In some cases, high availability may not be a
concern (for example, if this nPartition will only be used for non-critical
applications, or for experimental or transient purposes).
If high availability is not a concern, you may ignore any warnings displayed under
this tab, and continue with the new configuration. However, if high availability
is a concern, you should reconfigure the nPartition to eliminate HA warnings. Use
the [Cancel] button to return to the Modify
nPartition page. From there you can specify further changes or cancel the
entire action.
List of Individual HA Checks
The DIMM configuration of each cell should include a
multiple of two echelons per cell.
This provides a performance improvement by doubling the cell's memory
bandwidth (compared to having only one echelon installed). This is required
for high availability; if one echelon fails, the cell
still has at least one functional echelon of memory.
At least two cells in the nPartition should be capable of being selected as
the core cell. This allows the nPartition to boot even
if the preferred core cell fails.
All cells should have at least two CPUs. This allows the cell to be active
even if one of the CPUs fails.
|