HP 3000 Manuals HP 3000 Manuals
Appendix A Error Messages
CI Error Messages
Following are the CI error messages associated with
SPU Switchover/XL:
--------------------------------------------------------------
10900
MESSAGE SPU SWITCHOVER/XL PRODUCT NOT INSTALLED ON THIS SYSTEM. (CIERR
10900)
CAUSE An SPUCONTROL, SWITCHBACK, or SWITCHOVER command was entered,
but the SPU Switchover/XL product was not installed on the
system.
ACTION Install the SPU Switchover/XL product, and make sure that the
SPUINFO configuration file is in the correct configuration
group.
--------------------------------------------------------------
10901
MESSAGE BOTH PARTNERS IN THE MIRRORED VOLUME SET !volset name MUST BE
PRESENT ON SYSTEM !sysname. (CIWARN 10901)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered, but the mirrored volume set indicated in the message
is missing one of the mirrored partners. Both partners in a
mirrored volume set must be present on the system before
volume sets can be switched.
ACTION Wait for the missing partner to mount on the specified system,
then reissue the command. If the user wishes to stop
mirroring for the volume set, enter the appropriate command to
suspend mirroring, close the volume set, and reenter the
command.
--------------------------------------------------------------
10902
MESSAGE SYSTEM NAME GREATER THAN 8 CHARACTERS. (CIERR 10902)
CAUSE A SWITCHOVER or SWITCHBACK command was entered with a system
name greater than 8 characters long. The maximum length
allowed for system names is 8 characters.
ACTION Reenter the command with the correct system names. To check
for the correct system names, do an SPUCONTROL SHOWSPU
command, or go to the SPU subsystem in SYSGEN and do a SHOW
command.
--------------------------------------------------------------
--------------------------------------------------------------
10903
MESSAGE TOSYSNAME MUST BE THE SYSTEM WHERE THIS COMMAND IS ENTERED.
(CIERR 10903)
CAUSE A SWITCHOVER or SWITCHBACK command was entered with a system
name that is incorrect. The tosysname parameter must be the
name of the system that the command is being entered on. The
SWITCHOVER and SWITCHBACK commands alway switch the volume
sets to the system that the command is being executed on.
ACTION Be sure that the SWITCHBACK or SWITCHOVER commands are
executed on the system the volume sets need to be switched to.
Perform an SPUCONTROL SHOWSPU command to find the correct name
of the system, then reissue the attempted command with the
correct system name.
--------------------------------------------------------------
10904
MESSAGE FROMSYSNAME MUST BE THE PARTNER SYSTEM NAME. (CIERR 10904)
CAUSE A SWITCHBACK or SWITCHOVER command was entered with an
incorrect system name. The fromsysname must be the name of
the partner system. The fromsysname is the name of the system
that the volume sets are being switched from.
ACTION Ensure that the SWITCHBACK or SWITCHOVER commands are executed
on the system that the volume sets need to be switched to.
Issue an SPUCONTROL STATUS command to find the names of the
systems in the SPUSO configuration. Reissue the command with
the correct system name.
--------------------------------------------------------------
10905
MESSAGE SYSTEMS SPECIFIED ARE NOT A HOME/ALTERNATE PAIR. (CIERR 10905)
CAUSE A SWITCHBACK or SWITCHOVER command was entered, but the
systems specified were not listed in the configuration file as
partner systems or the systems were not listed as equal
partners (for example, the "to" system may not be the
alternate system for the "from" system, but the "from" system
is the alternate system for the "to" system.)
ACTION Check the configuration file using the SHOW command in the SPU
subsystem of SYSGEN. Ensure that the systems are listed as
partners. If they are not, perform an APAIR command. If the
partners need to be equal, perform an APAIR command twice.
SWITCHBACK or SWITCHOVER commands cannot be performed until
SPUCONTROL SETUP and SPUCONTROL START commands have been
issued using the modified configuration file.
--------------------------------------------------------------
--------------------------------------------------------------
10906
MESSAGE NO SPUSO NAME FOR THIS SYSTEM. (CIERR 10906)
CAUSE An SPUCONTROL SHOWSPU command was entered, but the system has
not been given an SPU Switchover/XL system name yet.
ACTION Enter an SPU Switchover/XL name through the ASYSTEM command in
the SYSGEN utility SPU subsystem.
--------------------------------------------------------------
10907
MESSAGE SYSTEM !sysname NOT RESPONDING. THE ALTERNATE SYSTEM MUST BE
UP BEFORE THIS COMMAND CAN SUCCEED. (CIERR 10907)
CAUSE Communication between systems was attempted by the SPUCONTROL
SETUP command, but the partner system did not respond.
ACTION Check the partner system to ensure that it is up, and check
the connections between the two systems.
--------------------------------------------------------------
10908
MESSAGE SYSTEM !sysname NOT RESPONDING, COMMAND CONTINUED. (CIWARN
10908)
CAUSE Communication between systems was attempted by the SPUCONTROL
START or SPUCONTROL STOP commands, but the partner system did
not respond. Although the communication attempt failed, the
command continued to execute.
ACTION Check the partner system to ensure that it is up, and check
the connections between the two systems. If the system is not
up, a SWITCHOVER or a SWITCHBACK command can be executed,
based on the state of the switchable volume sets.
--------------------------------------------------------------
10909
MESSAGE OPEN FAILED ON SPUSO CONFIGURATION FILE. (CIERR 10909)
CAUSE Each SPU Switchover/XL command must open the configuration
file. The file does not exist or it is empty.
ACTION Configure the SPU Switchover/XL environment through SYSGEN,
and the necessary information will be added to the
configuration file.
--------------------------------------------------------------
10910
MESSAGE ERROR OCCURRED WHILE ACCESSING SPUSO CONFIGURATION FILE.
(CIERR 10910)
CAUSE Each SPU Switchover/XL command must read the information in
the configuration file. An error occurred while reading
information from the configuration file.
ACTION Run SYSGEN, enter the SPU subsytem and issue a SHOW command to
see the configuration file information. Ensure that the
information is correct. If it is not, reconfigure the SPU
Switchover/XL environment through SYSGEN.
--------------------------------------------------------------
--------------------------------------------------------------
10911
MESSAGE VALIDATION FAILED ON THE SPUSO CONFIGURATION FILE ON SYSTEM
!sysname. (CIERR 10911)
CAUSE An SPU Switchover/XL command was entered, but the SPU
Switchover/XL configuration file information was not valid.
The file may not have any system names, system pairs, or
volume sets listed.
ACTION Run SYSGEN, enter the SPU subsystem, and issue a SHOW command
to see the configuration file information. Issue this on both
systems to ensure that the information is the same. If it is
not, reconfigure the SPU Switchover/XL environment through
SYSGEN on one of the systems, and execute an SPUCONTROL SETUP
command on the system with the correct configuration file.
--------------------------------------------------------------
10912
MESSAGE FAILURE TO TRANSFER SPUSO CONFIGURATION FILE TO SYSTEM
!sysname. (CIERR 10912)
CAUSE An SPUCONTROL SETUP command was entered, but there was an
error while transferring the SPU Switchover/XL configuration
file to the alternate system.
ACTION Ensure that the alternate system is up. Run SYSGEN, get into
the SPU subsystem, and issue a SHOW command to see the
configuration file information. Ensure that the systems
listed are correct. If they are not, reconfigure the SPU
Switchover/XL environment through SYSGEN.
--------------------------------------------------------------
10913
MESSAGE THE SPUSO CONFIGURATION FILES ON BOTH SYSTEMS MUST BE
IDENTICAL. (CIERR 10913)
CAUSE An SPUCONTROL START, SWITCHBACK, or SWITCHOVER command was
entered, and the SPU Switchover/XL configuration file on the
home and alternate systems were compared. The comparison
failed.
ACTION Run SYSGEN, get into the SPU subsytem, and issue a SHOW
command to see the configuration file information on both
systems. On the system that has the correct version of the
configuration file, issue an SPUCONTROL SETUP command.
--------------------------------------------------------------
10914
MESSAGE SPUCONTROL SETUP WAS ALREADY EXECUTED. (CIERR 10914)
CAUSE An SPUCONTROL SETUP command was entered, but the SPU
Switchover/XL configuration file had not been changed since
the last SPUCONTROL SETUP command was issued.
ACTION If there has been a configuration file change, this command
must be executed on the system with the modified configuration
file. Otherwise, it was an inappropriate context for entering
the command; no action is required.
--------------------------------------------------------------
10915
MESSAGE SPUCONTROL SETUP MUST BE EXECUTED BEFORE EXECUTING THIS
COMMAND. (CIERR 10915)
CAUSE An SPUCONTROL START command was entered, but the SPU
Switchover/XL configuration file has been modified since the
last SPUCONTROL SETUP command was issued.
ACTION Enter an SPUCONTROL SETUP command first.
--------------------------------------------------------------
--------------------------------------------------------------
10916
MESSAGE UNABLE TO WRITE INFORMATION TO THE SPUSO CONFIGURATION FILE ON
SYSTEM !sysname. (CIERR 10916)
CAUSE An SPUCONTROL SETUP command was entered, but the configuration
file on the system indicated that the message could not be
updated with the "setup complete" information.
ACTION Check the configuration file on the system indicated through
SYSGEN. If the failure occurred on the partner system, check
the connections. Reenter the SPUCONTROL SETUP command.
--------------------------------------------------------------
10917
MESSAGE SPUCONTROL START WAS ALREADY DONE, COMMAND CONTINUED. (CIWARN
10917)
CAUSE Both systems are up and an SPUCONTROL START command was
entered. This is just a warning. The command continues and
starts the system status message.
ACTION No action is required.
--------------------------------------------------------------
10918
MESSAGE SPUCONTROL START WAS ALREADY EXECUTED. (CIERR 10918)
CAUSE Only one system was up and an SPUCONTROL START command was
entered. SPU Switchover/XL was already started through a
previous execution of the command.
ACTION None; the command should not have been entered a second time.
--------------------------------------------------------------
10919
MESSAGE SPUCONTROL START MUST BE EXECUTED ON SYSTEM !sysname BEFORE
EXECUTING THIS COMMAND. (CIERR 10919)
CAUSE An SPUCONTROL STOP, STATUS, SWITCHOVER, or SWITCHBACK command
was entered, but an SPUCONTROL START command, for the system
indicated, was not previously executed. SPU Switchover/XL is
not active.
ACTION Execute an SPUCONTROL START command before entering the
command. If an SPUCONTROL STOP command was done, do not do an
SPUCONTROL START command.
--------------------------------------------------------------
10920
MESSAGE UNABLE TO START THE HEART BEAT SIGNAL. (CIERR 10920)
CAUSE An SPUCONTROL START command was entered, but the heartbeat
signal on the system could not be started.
ACTION Check the connection and redo the command.
--------------------------------------------------------------
--------------------------------------------------------------
10921
MESSAGE SPUCONTROL STOP MUST BE EXECUTED BEFORE EXECUTING THIS
COMMAND. (CIERR 10921)
CAUSE An SPUCONTROL SETUP command was entered, but the SPU
Switchover/XL process was not stopped using the SPUCONTROL
STOP command.
ACTION Enter an SPUCONTROL STOP command, then reenter the SPUCONTROL
SETUP command.
--------------------------------------------------------------
10922
MESSAGE VOLUME SET !volsetname NOT CONNECTED TO SYSTEM !sysname.
(CIERR 10922)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered, but the volume set indicated in the message is not
mounted on the system indicated.
ACTION Run SYSGEN, get into the SPU subsystem, and issue a SHOW
command to see the list of volume set names. Issue a DSTAT
command at the system prompt, for the indicated system, and
compare the volume set name to those in the configuration
file. Check the disk drive connections to the system.
--------------------------------------------------------------
10923
MESSAGE BOTH HALVES OF THE SPLIT VOLUME SET !volsetname MUST BE ON THE
SYSTEM !sysname. (CIWARN 10923)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered, but half of the split volume set is missing; the back
half of the split volume set is missing, and it must be on the
system before volume sets can be switched.
ACTION Wait for the missing half of the volume set to mount on the
system and reenter the command.
--------------------------------------------------------------
10924
MESSAGE VOLUME SET !volsetname IS NOT CLOSED ON SYSTEM !sysname.
(CIERR 10924)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered, but the volume set indicated in the message was not
closed, with the VSCLOSE command, on the indicated system.
Volume sets must be closed before they can be switched between
systems.
ACTION Issue a VSCLOSE command on all volume sets to be switched and
reenter the command.
--------------------------------------------------------------
10925
MESSAGE NO VOLUME SETS SPECIFIED IN THE SPUSO CONFIGURATION FILE.
(CIWARN 10925)
CAUSE An SPUCONTROL STATUS command was entered, but there were no
volume sets specified in the configuration file.
ACTION If there were supposed to be volume sets listed, run SYSGEN,
get into the SPU subsystem, and issue a SHOW command to see
the configuration files information.
--------------------------------------------------------------
--------------------------------------------------------------
10926
MESSAGE ALL VOLUME SETS HOME TO SYSTEM !sysname WERE PREVIOUSLY
MOUNTED. (CIWARN 10926)
CAUSE A SWITCHBACK command was entered, but the volume sets home to
the system are already mounted on that system.
ACTION Issue an SPUCONTROL STATUS command to check where the SPU
Switchover/XL volume sets are currently mounted and where
their home systems are. If the volume sets are already
mounted on the current system, then no action is required. If
the volume sets required are home to the alternate system,
issue a SWITCHOVER command. Remember, for the SWITCHBACK and
SWITCHOVER commands, volume sets are switched to the system
that the command is executed on.
--------------------------------------------------------------
10927
MESSAGE ALL VOLUME SETS HOME TO THE ALTERNATE SYSTEM !sysname WERE
PREVIOUSLY MOUNTED. (CIWARN 10927)
CAUSE A SWITCHOVER command was entered, but the volume sets home to
the alternate system were already mounted on that system.
ACTION Issue an SPUCONTROL STATUS command to check where the SPU
Switchover/XL volume sets are currently mounted and where
their home systems are. If the volume sets are already
mounted on the current system, then no action is required.
Remember, for the SWITCHBACK and SWITCHOVER commands, volume
sets are switched to the system that the command is executed
on.
--------------------------------------------------------------
10928
MESSAGE UNABLE TO SWITCH VOLUME SETS. (CIWARN 10928)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered. While switching the volume sets an error occurred,
and none of the volume sets could be switched.
ACTION Issue a DSTAT command at the system prompt to ensure that all
the LDEVs in the volume sets indicated are in LONER or LOCKED
state on the current system and (if possible) on the alternate
system. Ensure that the LDEVs are connected to both systems.
Reenter the command.
--------------------------------------------------------------
10929
MESSAGE ONE OR MORE LDEVS IN VOLUME SET !volsetname ARE NOT
RESPONDING. (CIWARN 10929)
CAUSE An SPUCONTROL SETUP, SWITCHBACK, or SWITCHOVER command was
entered. One of the LDEVs in the volume set was not
responding; it may be powered off. Since one of the volume
sets was not responding, none of the volume sets were
switched.
ACTION Check the LDEVs in the volume set. Ensure that they are
powered on and that all connects are making contact to both
systems, then reenter the command.
--------------------------------------------------------------