Managing Cpu Element Resynchronization; Managing Cpu Element Bringup - NEC Express5800/320Ma Administrator's Manual

Managing CPU Element Resynchronization

On systems running Windows Server 2003 Standard Edition, a CPU element returning
to service must resynchronize with the functioning CPU element. A CPU element
requires resynchronization:
•
After bringing down and then bringing up a CPU element
•
After a transient CPU element error
•
After powering down a system and then powering it up
•
During online BIOS upgrade
During the resynchronization period, the system will not respond to network
connections. Therefore, it is important to set the timeout period and/or number of retries
for network applications to be large enough to prevent timeouts during
resynchronization. The length of the resynchronization period is proportional to the
amount of system memory configured.
By default, resynchronization occurs as soon as the CPU element that was taken out
of service is determined to be operational or the failed enclosure is replaced. However,
you can defer resynchronization to a more convenient time, such as an off-peak period.
See the ftSMC help for information about scheduling CPU bringup.

Managing CPU Element Bringup

You can specify two times of day at which to enable, or to which to defer, the return to
service of CPU elements that have been removed from service (shot). You use two
commands—Enable CpuBoard Bringup and Defer CpuBoard Bringup—which the
Windows Scheduler executes. Along with the commands, you specify two times of day:
one time when an offline CPU element can be brought up, and another time to which
CPU Bringup is deferred. See the ftSMC snapin Help for instructions in setting these
commands.
When Scheduler executes the commands, Enable CpuBoard Bringup changes the
CpuBringUpPolicy property under the Srabid driver to Enable Bringup. This setting
enables CPU elements that were removed from service to come back into service. It
also brings up any CPUs that are in the Removed from Service state for a reason of
Deferred BringUp, as long as they don't exceed the MTBF threshold.
When Scheduler executes the Defer CpuBoard Bringup command, it changes the
CpuBringUpPolicy property under the Srabid driver to Defer Bringup. With this setting,
if a CPU element is removed from service, the CPU elements come back into service
at different times.
For example, consider the situation in which Defer CpuBoard Bringup is scheduled for
every day at 8 a.m., and Enable CpuBoard Bringup is scheduled for every day at 9 p.m.
In this case, if any CPU element gets removed from service after 8 a.m., it will not be
System Startup and Shutdown
Operating and Monitoring Your System 2-3