Rolling Reload of NonStop Kernel Processors

Rolling Reload of NonStop Kernel Processors 2/18/04
Hewlett-Packard Development Company L.P. 7 of 7 CSSI Website
• Verify that all SLSA SACs are in the STARTED state, not STARTING.
Check the access from both fabrics and all processors configured for each SAC.
• Verify that there are no new OSM/TSM alarms.
• Perform similar checks for applications and other subsystems such as
ServerNet/FX and Telco-specific SACs.
• If necessary, verify the health of the applications.
• If necessary, verify that the updates have been installed and are active on this
processor.
• Verify that the time since the reload is about what was determined in the planning
phase (Section 2.5, Determine how much time is required for a rolling reload).
4.5 Verify and balance system after all processors are reloaded.
If necessary, verify that the updates have been installed and are active on all impacted
processors. Check that remote application processes have correctly handled the DOWN
and UP changes for the affected local processors. These steps are especially important if
the application includes network transactions or is part of an RDF configuration.
Rebalance the system and application as necessary.
5 Summary
You can use rolling reloads to avoid system loads in some situations, such as processor
upgrades and certain SPR installations. However, follow this document’s guidelines and
procedures when performing a rolling reload to minimize the chance of an outage. Take
your time, and if you have questions or concerns about rolling reloads, contact the GCSC
for assistance.