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

Control, Configuration, and Maintenance Tools
HP Integrity NonStop NS-Series Planning Guide—529567-005
B-8
IOAM ME Firmware
ServerNet adapters and one ServerNet switch board. (See I/O Adapter Module (IOAM)
Enclosure and I/O Adapters on page 5-16.)
Each IOAM connects directly to a p-switch and contains a single ME that resides within
the ServerNet switch board, along with the ServerNet fabric interconnect.
The I/O functional elements include Fibre Channel ServerNet adapters (FCSAs), Fibre
Channel storage devices (disk or tape) or Gigabit 4-port Ethernet ServerNet adapters
(G4SA). The storage or transport protocols used in the ServerNet adapters are
irrelevant to the maintenance architecture. Maintenance aspects of the Fibre Channel
disk modules are handled indirectly via the FCSAs.
The fabric functional element is a redundant ServerNet IPC interconnect medium that
interconnects both the processor and the I/O functional elements. This interconnection
medium provides diagnostic capabilities via the p-switches and ServerNet cables.
The diagram in Maintenance Architecture on page B-6 depicts each of the functional
elements containing at least one ME. Any of the functional elements shown can and
usually are composed of multiple functional elements of the same type. For example,
the fabric element includes two p-switch interconnect modules, each of which has an
ME and connects to either the X or the Y ServerNet fabric.
IOAM ME Firmware
When the ME firmware is executing within a ServerNet switch installed in an IOAM
enclosure, it initializes, controls, and monitors all of its local functional elements for its
parent module, module 2 or 3. No direct hardware connection exists between the two
ServerNet switches installed in an IOAM enclosure, so the ME firmware on a given
IOAM has no hardware responsibilities in terms of its peer IOAM.
Unlike the ME firmware executing in a p-switch, the ME firmware in an IOAM does not
execute in a primary versus secondary status.
Processor Functional Element
In the NonStop advanced architecture (NSAA), a logical processor is a distribution of
physical processor elements (PEs), each of which resides within a separate physical
module. (See NonStop Blade Complex on page 4-2.) The logical processor
maintenance entity is relegated to the halted state services or standard millicode
software running on a given set of PEs that makes up one logical processor.
The ME firmware in each p-switch only interacts with a logical processor via ServerNet
using the SMIP ServerNet-based communication protocol to send command requests
to a logical processor and respond to command requests from a logical processor. The
p-switch ME firmware does not have any data regarding the number of PEs per
NonStop Blade Element, NonStop Blade Elements per NonStop Blade Complex, or the
LSUs.










