NonStop NS-Series Planning Guide (H06.04+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 System Hardware Overview
- 2 Installation Facility Guidelines
- 3 System Installation Specifications
- 4 Integrity NonStop NSSeries System Description
- NonStop System Primer
- NonStop Advanced Architecture
- NonStop Blade Complex
- Processor Element
- Duplex Processor
- Triplex Processor
- Processor Synchronization and Rendezvous
- Memory Reintegration
- Failure Recovery for Duplex Processor
- Failure Recovery for Triplex Processor
- ServerNet Fabric I/O
- System Architecture
- Modular Hardware
- NonStop S-Series I/O Hardware
- System Models
- Default Startup Characteristics
- Migration Considerations
- System Installation Document Packet
- 5 Modular System Hardware
- Modular Hardware Components
- Cabinets
- AC Power PDUs
- Modular Cabinet PDU Keepout Panel
- NonStop Blade Element
- Logical Synchronization Unit (LSU)
- LSU Indicator LEDs
- Processor Switch
- P-Switch Indicator LEDs
- Processor Numbering
- I/O Adapter Module (IOAM) Enclosure and I/O Adapters
- Fibre Channel Disk Module
- Tape Drive and Interface Hardware
- Maintenance Switch (Ethernet)
- Optional UPS and ERM
- System Console
- Enterprise Storage System
- Component Location and Identification
- NonStop S-Series I/O Enclosures
- Modular Hardware Components
- 6 System Configuration Guidelines
- Enclosure Locations in Cabinets
- Internal ServerNet Interconnect Cabling
- Cable Labeling
- Cable Management System
- Internal Interconnect Cables
- Dedicated Service LAN Cables
- Cable Length Restrictions
- Internal Cable Part Numbers
- NonStop Blade Elements to LSUs
- NonStop Blade Element to NonStop Blade Element
- LSUs to Processor Switches and Processor IDs
- Processor Switch ServerNet Connections
- Processor Switches to IOAM Enclosures
- FCSA to Fibre Channel Disk Modules
- FCSA to Tape Devices
- P-Switch to NonStop S-Series I/O Enclosure Cabling
- IOAM Enclosure and Disk Storage Considerations
- Fibre Channel Devices
- G4SAs to Networks
- Default Naming Conventions
- PDU Strapping Configurations
- 7 Example Configurations
- A Cables
- B Control, Configuration, and Maintenance Tools
- Support and Service Library
- System Console
- Maintenance Architecture
- Dedicated Service LAN
- IP Addresses
- Ethernet Cables
- SWAN Concentrator Restriction
- System-Up Dedicated Service LAN
- Dedicated Service LAN Links With One IOAM Enclosure
- Dedicated Service LAN Links to Two IOAM Enclosures
- Dedicated Service LAN Links With IOAM Enclosure and NonStop SSeries I/O Enclosure
- Dedicated Service LAN Links With NonStop S-Series I/O Enclosure
- Initial Configuration for a Dedicated Service LAN
- Operating Configurations for Dedicated Service LANs
- OSM
- System-Down OSM Low-Level Link
- AC Power Monitoring
- AC Power-Fail States
- C Guide to Integrity NonStop NSSeries Server Manuals
- Safety and Compliance
- Index
Integrity NonStop NS-Series System Description
HP Integrity NonStop NS-Series Planning Guide—529567-005
4-8
Memory Reintegration
°
Allow each PE to individually and deterministically respond to asynchronous
incoming interrupts and then to respond collectively as a single logical
processor.
°
Exchange software state information when performing operations that are
distributed across PEs; for example, memory reintegration, error handling, and
memory scrubbing.
•
Compare output from each PE. If identical, the output is transmitted over the
ServerNet fabrics. If the PE outputs are not the same, appropriate actions occur to
identify the errant one and to recover from the failure. Under some failure
conditions, it can be necessary to stop normal operations of the erring PE.
Memory Reintegration
Memory reintegration initiates processing in a PE whose operation has been stopped
because the NonStop Blade Element diverged or has been replaced. This reintegration
requires that all of the memory and processor states be copied from a functioning PE
to the target PE. Once the memory and processor state data is copied, rendezvous is
used to complete the reintegration. This entire reintegration operation is invisible to the
running applications.
Failure Recovery for Duplex Processor
Duplex processors have no single points of failure. Any single element of a duplex
processor might fail, but alternative paths exist for operation of user applications.
Failure of a complete NonStop Blade Element reduces the system to operation on the
running NonStop Blade Element. The failure of an LSU might take down the associated
logical processor, but in this event, the operating system activates the backup
processes in other logical processors. The system remains available to the
applications as if no failure occurred.
The errant processor is reset and then it is synchronized with the running one. If the
failure rate exceeds a predetermined threshold value within a period of time, the failing
processor is reset and held for repair action.
Failure Recovery for Triplex Processor
In triplex processors, each LSU has inputs from the three processor elements within a
logical processor. As with the duplex processor, the LSU keeps the three PEs in loose
lockstep. The LSU also checks the outputs from the three PEs. If outputs from one of
the PEs is not the same as the other two, the errant result is ignored, and the result
from the other two PEs is sent to the ServerNet fabrics. Reintegration works the same
as in the duplex processor. The number of PEs in a reintegration depends on the
conditions of the failure and the configuration of the hardware.
The failure of a NonStop Blade Element in a triplex processor reduces processor
operation to duplex. When the failing unit is replaced, the reintegration function










