NonStop Operations Guide for H-Series and J-Series RVUs

NS1200 server, or NS1000 server. Or it can refer to a NonStop server blade in a NonStop
BladeSystem, NonStop NS2200 series system, NS2100 system, or NS2000 series system.
Blade
The term “blade” is used differently in different NonStop systems:
• In NonStop BladeSystems, NonStop server blades house the microprocessors and are mounted
inside c7000 enclosures.
• In NonStop NS16000 series and NS14000 series systems, a NonStop Blade Element (NSBE)
consists of a chassis, processor board containing two to four PEs, memory, I/O interface
board, midplane, optics adapters, fans, and power supplies. The OSM Service Connection
displays the Blade Complex object. A Blade Complex houses two NSBEs (in a duplex, or
DMR system) or three NSBEs (in a triplex, or TMR system) in each enclosure. A Blade Complex
consists of up to four logical processors and their associated LSUs.
• In NonStop NS2400 series, NS2300, NS2200 series, NS2100, NS2000 series, NS1200,
and NS1000 systems, a NonStop Blade Element (NSBE) is an HP Integrity server adapted
for use as a Blade Element. A Blade Element contains the processor elements, power supplies,
fan assemblies, and firmware. NonStop NS2400 series, NS2300, NS2200 series, NS2100,
and NS2000 series systems can include two or four Blade Elements. NonStop NS1200 and
NS1000 systems can include up to eight Blade Elements.
In NonStop NS2400 series, NS2300, NS2200 series, NS2100, and NS2000, NS1200,
and NS1000 systems, the OSM Service Connection displays the Blade Complex object, and
there is one Blade Element per Blade Complex. The OSM Service Connection uses the Blade
Complex to hierarchically differentiate between each Blade Element in NonStop NS2400
series, NS2300, NS2200 series, NS2100, NS2000 series, NS1200, and NS1000 systems.
Recording Your System Configuration
As a system operator, you need to understand how your system is configured so you can confirm
that the hardware and system software are operating normally. If problems do occur, knowing
your configuration allows you to pinpoint problems more easily. If your system configuration is
corrupted, documentation about your configuration is essential for recovery. You should be familiar
with the system organization, system configuration, and naming conventions.
Several methods are available for researching and recording your system configuration:
• Maintaining records in hard-copy format
• Using the OSM Service Connection or the OSM System Inventory Tool to inventory your system
In the OSM Service Connection tree pane, select the System object. From the View pane
drop-down menu, select Inventory to display a list of the system’s hardware resources. Click
Save to save this list to a Microsoft Excel file.
The OSM System Inventory Tool allows you to inventory multiple systems in a single action
and save the data to a Microsoft Excel file. For more information, see the online help available
within the OSM System Inventory Tool.
• Using SCF to list objects and devices and to display subsystem configuration information
For information on forms available that can help you record your system configuration, refer to the
appropriate planning guide for your NonStop system.
Using SCF to Determine Your System Configuration
You can use SCF commands to configure and control the objects (lines, controllers, processes, and
so on) belonging to each subsystem running on a NonStop NS-series system or NonStop
BladeSystem. You also use SCF to display information about subsystems and their objects.
Recording Your System Configuration 39