J06.10 Software Installation and Upgrade Guide

Falling Back to An Earlier Version of AF_UNIX
If fallback is required:
• If you start $ZPLS in a startup script using the SCF START SERVER command, modify startup
scripts to start $ZPLS using the SCF START SERVER command.
• If you use the STARTOSS utility to start OSS processes, modify the
target-volume.ZOSSINS.OSSINFIL file by changing the line
* SERVER #ZPLS
to
SERVER #ZPLS
NOTE: target-volume is normally $SYSTEM.
This ensures that the OSS Socket Local Server is started correctly as system load.
The OSS Monitor included in AF_UNIX Release 2 software adds database records for the local
server 2 (LS2) processes. If fallback is required, HP recommends that, after the system is no longer
running an RVU containing AF_UNIX Release 2, you delete these records using the SCF DELETE
SERVER command:
ASSUME $ZPMON DELETE SERVER
#ZLS00 DELETE SERVER #ZLS01
...
DELETE SERVER #ZLS15
If you fail to delete the database records:
• The SCF INFO SERVER command will show $ZLS00 through $ZLS15 as UNKNOWN servers
with no parameters.
• Attempts to START, STOP, or ALTER $ZLS00 through $ZLS15 will fail with the diagnostic
"Configuration contains invalid data".
For more information about AF_UNIX Release 2, see the Open System Services Programmer's
Guide.
CLuster I/O Module (CLIM) Software Compatibility
CLIMs with software associated with J06.05 are not compatible with RVUs of J06.06 and later
RVUs. However, if you are migrating from a J06.05 RVU to a J06.06 or later RVU, the software
upgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assured
because the RVU on the host is updated first, then, while the processors are halted, the CLIMs are
updated to the CLIM software version associated with this RVU. When the system is loaded, the
CLIM and the NonStop host are at the same level and are therefore compatible.
If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSM
Low-Level Link, OSM Service Connection or by entering:
SCF-> VERSION CLIM $ZZCIP.clim-name
If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat
subcommand by entering:
TACL>climcmd clim-name cat /etc/vproc
Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs
that are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) Compatibility
Reference for all CLIM and host RVU compatibility information.
See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshooting
tips about identifying an incompatibility in CLIM and host CIP software.
32 Installation, Migration, and Fallback Considerations for This RVU