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-4
Primary and Backup System Consoles Managing
One System
Because all servers are shipped with the same preconfigured IP addresses for MSP0,
MSP1, $ZTCP0, and $ZTCP1, you must change these IP addresses for the second
and subsequent servers before you can add them to the LAN.
Primary and Backup System Consoles Managing One System
This configuration is recommended. It is similar to the setup configuration, but for fault-
tolerant redundancy, it includes a second maintenance switch, backup system console,
and modem. The maintenance switches provide a dedicated LAN in which all nodes
use the same subnet.
The dedicated service LAN is normally connected to the operations LAN using a single
connection. If both sides of the dedicated service LAN connect directly to the
operations LAN, you must:
•
Enable Spanning Tree Protocol (STP) in switches or routers that are part of the
operations LAN.
•
Change the preconfigured IP address of the backup system console before you
add it to the LAN.
Note. A subnet is a network division within the TCP/IP model. Within a given network, each
subnet is treated as a separate network. Outside that network, the subnets appear as part of a
single network. The terms subnet and subnetwork are used interchangeably.
Caution. Networks with more than one path between any two nodes can cause loops that
result in message duplication and broadcast storms that can bring down the network. If a
second connection is used, refer to the documentation for the ProCurve 2524 maintenance
switch and enable STP in the maintenance switches. STP ensures only one active path at any
given moment between two nodes on the network. In networks with two or more physical paths
between two nodes, STP ensures only one active path between them and blocks all other
redundant paths.










