H06.03 Software Installation and Upgrade Guide

Overview of Installing the H06.03 RVU
H06.03 Software Installation and Upgrade Guide—540066-002
1-5
OSM Low-Level Link and System Load
OSM Low-Level Link and System Load
The OSM Low-Level Link is updated to add a new System Load dialog box specifically
for H-series. You can save up to four alternate system load configurations in the OSM
Service Connection by using the Save as System Load Disk on either SCSI or FC
disks.
You must perform the OSM save configuration while the Integrity NonStop NS-series
server is running. After a configuration is saved, you can load the system using
mirrored disks without reviving. HP recommends that you use the OSM save
configuration feature for performing system loads.
OSM Client and Server-Based SPRs
For H06.03, the server-based OSM SPR is T0682 H01^AAE.
The three client-based OSM SPRs are dual-threaded for both G-Series and H-series:
•
T0632 G06 AAL (OSM Notification Director)
•
T0633 G06 AAL (OSM Low-Level Link)
•
T0634 G06 AAJ (OSM Console Tools)
Client installation instructions are included in the NonStop System Console Installer
Guide. All three OSM components are installed from the NonStop System Console
Installer CD, either from the master installer or individually from their own separate
installers. For new system consoles, OSM client components are already installed.
Using DSM/SCM for the H06.03 RVU
•
DSM/SCM for the H06.03 RVU
•
Public DLLs and DSM/SCM
•
DSM/SCM and OSS
•
Upgrading the DSM/SCM Client (Planner Interface) and the T6031H01 PVU
•
Installing a New H06.03 SUT Using DSM/SCM
•
Check or Alter the CONFTEXT File Before Installing an H06.03 SUT
DSM/SCM for the H06.03 RVU
•
The DSM/SCM H01 PVU (T6031H01) is supported for Integrity NonStop
NS-series servers only.
•
A new type of hardware platform and selectable option, TNS/E, for Integrity
NonStop NS-series servers has been added to the Planner Interface (PI) screens.
See the DSM/SCM User’s Guide for configuration information.
•
By default, DSM/SCM H01 PVU is configured to manage OSS files. Check that
OSS is configured and started if DSM/SCM is set to manage OSS files. If not, the
Apply can fail.