Fujitsu Siemens Computers SX series User Manual page 298

Functional scope, concepts and applications
These CoD-XSBs can only be used as CPU-XSBs. To permit dynamic disconnection of the
CoD-XSBs from the BS2000 partition later, no-obp-sb, no-mem-sb and no-io-sb must
be set for them. For details see the
Temporary releasing of CPU performance
The additional CPU performance added earlier can be released temporarily at any time by
disconnecting CPUs of XSB 00-1 or by removing XSB 00-1.
This CPU performance can then be used by the Solaris partition without any additional cost.
Cross-partition concept
A cross-partition concept for using the CPU performance should be implemented for the
customer. The following must be taken into consideration here:
When planning the procedures you must bear in mind that the peak-workload phases
in the partitions of the SX server must be sufficiently staggered.
The DR command interface offered in Solaris has script capability. CPU performance
can be added or released using a time-driven script (Cron job; for details please see the
Tasks application in PRIMEPOWER ServerView Suite) or on an event-driven basis (for
the options available see the manual "openSM2" [18]).
Online maintenance
In the information below it is assumed that XSB 00-0 fails. Similar maintenance scenarios
can be devised for the failure of another XSB.
The following situation results when XSB 00-0 fails:
New boot-XSB 01-0:
After XSB 00-0 fails the automatic recovery function means that Solaris is booted from
XSB 01-0 (secondary boot-XSB) which belongs to the other system board.
XSB 00-1 on system board 00 is still used.
The partition operates with reduced capacity, namely with 4 CPUs (3 BS2000 CPUs =
75%) and 8 GB of memory (6 GB of BS2000 main memory = 60%).
With the remaining resources, in terms of its RPF performance the partition corre-
sponds to the SX150-30C model.
Which of the three operating variants described below is selected until the BS2000 partition
is restored to 100% capacity depends on the resource requirements of the active applica-
tions and the minimum performance requirement.
298
section "Settings relevant to DR" on page
Dynamic Reconfiguration
321.
U41272-J-Z385-3-76