NonStop S-Series System Expansion and Reduction Guide
Table Of Contents
- NonStop S-Series System Expansion and Reduction Guide
- What’s New in This Guide
- About This Guide
- 1 The Resizing Process
- 2 Planning System Expansion
- 3 Planning System Reduction
- 4 Reducing a System Online
- 1.Prepare the Donor System for Reduction
- 2.Record Information About the Donor System
- 3.Prepare Both ServerNet Fabrics
- 4.Inventory Enclosures to Be Removed
- 5.Prepare and Stop Devices and Processes
- 6.Ensure Devices and Processes Are Stopped
- 7.Delete Devices and Processes If Necessary
- 8.Prepare Enclosures for Removal
- 9.Finish the Reduction
- 10.Remove Other Cables From Powered-Off Enclosures
- 11.Physically Remove Enclosures From the System
- Adding Enclosures to Another System
- 5 Reducing a System Offline
- 6 Expanding a System Online
- Preparation for Online Expansion
- 1.Prepare Target System for Expansion
- 2.Record Information About Target System
- 3.Prepare Target System for Addition of Block
- 4.Save Current Target System Configuration
- 5.Copy SP Firmware File From the Target System to the System Console
- 6.Finish Gathering Information
- 7.Connect a System Console to the Enclosure
- 8.Change Group Number of Enclosure to 01
- 9.Power On Enclosure
- 10.Verify Connection Between System Console and Enclosure
- 11.Configure System Console and Enclosure
- 12.Verify SP Firmware Is Compatible
- 13.Update SP Firmware in Enclosure If Necessary
- 14.Configure Topology of Enclosure If Necessary
- 15.Power Off Enclosure
- 16.Repeat Steps 6 Through 15 If Necessary
- 17.Assemble Enclosures Into a Block
- 18.Change Group Numbers of Block to Fit Target System
- 19.Disconnect System Console From Block
- 20.Power On Added Block
- 21.Cable Block to Target System
- 22.Verify Resized Target System
- 23a.Update Firmware and Code in Block (Using TSM)
- 23b.Update Firmware and Code in Block (Using OSM)
- 24.Reload Processors in Block If Necessary
- 25.Verify Operations in Added Block
- 26.Configure CRUs in Added Block
- 7 Troubleshooting
- A Common System Operations
- Determine the Processor Type
- Determine the ServerNet Fabric Status
- Determine the Product Versions of the OSM Client Software
- Determine the Product Version of the TSM Client Software
- Move the System Console
- Stop the OSM or TSM Low-Level Link
- Start a Startup TACL Session
- Start the OSM or TSM Low-Level Link
- Start the OSM Service Connection or TSM Service Application
- B ServerNet Cabling
- C Checklists and Worksheets
- D Stopping Devices and Processes
- Safety and Compliance
- Glossary
- Index
Troubleshooting
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
7-16
Storage Subsystem Event Messages
Storage Subsystem Event Messages
The symbolic name of each of these events begins with ZSTO-EVT:
Event
Number Name (ZSTO-EVT) Description (page 1 of 2)
1026 -ADAPTER-AUTO-FAILED Autoconfiguration of an adapter failed.
This event is usually preceded by storage
subsystem event 1025 (failed to access
$ZCNF).
1027 -ADAPTER-AUTO-RETRY Waiting for a resource that is blocking auto-
configuration of an adapter.
1028 -CRU-INSERTED Hardware insertion event sent from the
configuration utility process ($ZCNF).
1029 -CRU-REMOVED Hardware deletion event sent from the
configuration utility process ($ZCNF).
1030 -WRONG-CRU-INSERTED Hardware insertion event received does not
match the configuration information in the
system configuration database.
1031 -CRU-CONFIGURED CRU configuration successfully added to the
system configuration database.
1032 -CRU-INIT CRU initialization succeeded.
1033 -CRU-INIT-FAILED CRU initialization failed.
The event contains the error number
returned from the support function used. This
function is offered by the SCSI Interface
Module (SIFM) or by Extensible I/O (XIO).
1034 -POST-COMPLETE Power-on self-test of CRU succeeded.
1035 -POST-FAILED Power-on self-test of CRU failed.
1037 -INVALID-CRU Not enough information available to
determine:
•
What type of CRU was inserted
•
How to configure that CRU
1040 -UNSUPPORTED-CRU CRU inserted that is not supported by the
storage subsystem.
1041 -CRU-OWNERSHIP CRU cannot be configured by the storage
subsystem. The slot where the CRU was
inserted is already configured by another
subsystem.
1042 -CRU-DELETED CRU configuration deleted from the system
configuration database.