Purpose
ha_vsd - Starts and restarts the Recoverable Virtual Shared Disk subsystem. This includes configuring virtual shared disks and hashed shared disks as well as activating the recoverability subsystem.
Syntax
ha_vsd [reset]
Flags
None.
Operands
Description
Use this command to start the IBM Recoverable Virtual Shared Disk software after you install it, or, with the reset option, to stop and restart the program.
Exit Values
Security
You must have root privilege and write access to the SDR to run this command.
Implementation Specifics
This command is part of the IBM Recoverable Virtual Shared Disk option of PSSP.
Prerequisite Information
See PSSP: Managing Shared Disks.
Location
/usr/lpp/csd/bin/ha_vsd
Related Information
Commands: ha.vsd, hc.vsd
Examples
To stop the Recoverable Virtual Shared Disk subsystem and restart it, enter:
ha_vsd reset
Purpose
ha.vsd - Queries and controls the activity of the rvsd daemon of the Recoverable Virtual Shared Disk subsystem.
Syntax
Flags
None.
Operands
The Recoverable Virtual Shared Disk subsystem must be restarted for this operand to take effect.
The Recoverable Virtual Shared Disk subsystem must be restarted for this operand to take effect.
Once debugging is turned on and the Recoverable Virtual Shared Disk subsystem has been restarted, ha.vsd trace should be issued to turn on tracing.
Use this operand under the direction of your IBM service representative.
Note: the default when the node is booted is to have standard output and standard error routed to the console. If debugging is turned off standard output and standard error will be routed to /dev/null and all further trace messages will be lost. You can determine if debug has been turned on by issuing ha.vsd qsrc. If debug has been turned on the return value will be:
action = "2"
This operand is only meaningful after the debug operand has been used to send standard output and standard error to the console and the Recoverable Virtual Shared Disk subsystem has been restarted.
Description
Use this command to display information about the Recoverable Virtual Shared Disk subsystem, to change the number of nodes needed for quorum, and to change the status of the subsystem.
You can start the Recoverable Virtual Shared Disk subsystem with the IBM Virtual Shared Disk Perspective. Type spvsd and select actions for virtual shared disk nodes.
Exit Values
Security
You must have write access to the SDR to run this command. You must have root privilege to issue the debug, quorum, refresh, reset, start, stop, trace, mksrc, and rmsrc subcommands.
Implementation Specifics
This command is part of the Recoverable Virtual Shared Disk option of PSSP.
Prerequisite Information
See PSSP: Managing Shared Disks.
Location
/usr/lpp/csd/bin/ha.vsd
Related Information
Commands: ha_vsd, hc.vsd
Examples
ha.vsd reset
The system returns the messages:
Waiting for the rvsd subsystem to exit. rvsd subsystem exited successfully. Starting rvsd subsystem. rvsd subsystem started PID=xxx.
ha.vsd quorum 5
The system returns the message:
Quorum has been changed from 8 to 5.
ha.vsd query
The system displays a message similar to the following:
Subsystem Group PID Status
rvsd rvsd 18320 active
rvsd(vsd): quorum= 7, active=1, state=idle, isolation=member,
NoNodes=10, lastProtocol=nodes_failing,
adapter_recovery=on, adapter_status=up,
RefreshProtocol has never been issued from this node,
Running function level 3.1.0.0.
where:
Purpose
hacws_verify - Verifies the configuration of both the primary and backup High Availability Control Workstation (HACWS) control workstations.
Syntax
hacws_verify
Flags
None.
Operands
None.
Description
Use this command to verify that the primary and backup control workstations are properly configured to provide HACWS services to the SP system. The hacws_verify command inspects both the primary and backup control workstations to verify the following:
Both the primary and backup control workstations must be running and capable of executing remote commands via the AIX rsh command.
The system administrator should run the hacws_verify command after HACWS is initially configured. After that, the hacws_verify command can be run at any time.
Exit Values
Security
| Restricted Root Access |
|---|
|
As of PSSP 3.2, you have the option of running your SP system with an enhanced level of security. With the restricted root access (RRA) option enabled, PSSP does not internally issue rsh and rcp commands as a root user from a node. Also, PSSP does not automatically grant authorization for a root user to issue rsh and rcp commands from a node. If you enable this option, some procedures might not work as documented. For example, to run HACMP, an administrator must grant the authorizations for a root user to issue rsh and rcp commands that PSSP otherwise grants automatically. See the "Planning for security" chapter in IBM RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment for a description of this function and a complete list of limitations. |
Prerequisite Information
Refer to PSSP: Administration Guide for additional information on the HACWS option.
Location
/usr/sbin/hacws/hacws_verify
Related Information
PSSP commands: install_hacws, spcw_addevents
AIX commands: rsh
Examples
To verify the HACWS configuration, enter:
/usr/sbin/hacws/hacws_verify
Purpose
haemcfg - Compiles the Event Management objects in the System Data Repository (SDR) and places the compiled information into a binary Event Management Configuration Database (EMCDB) file
Syntax
haemcfg [-c] [-n]
Flags
Operands
None.
Description
The haemcfg utility command builds the Event Management Configuration Database (EMCDB) file for a system partition. If no flags are specified, the haemcfg command:
To place the new EMCDB into production, you must shut down and restart all of this system partition's Event Manager daemons: the daemon on the control workstation and the daemon on each of the system partition's nodes. When the Event Management daemon restarts, it copies the EMCDB from the staging directory to the production directory. The name of the production EMCDB is /etc/ha/cfg/em. syspar_name.cdb.
If you want to test a new EMCDB, IBM recommends that you create a separate system partition for that purpose.
You must create a distinct EMCDB file for each system partition on the IBM RS/6000 SP. To build an EMCDB file, you must be executing on the control workstation and you must set the SP_NAME environment variable to the appropriate system partition name before you issue the command.
Before you build or replace an EMCDB, it is advisable to issue the haemcfg command with the debugging flags.
The -c flag lets you check the validity of the Event Management data that resides in the SDR. This data was previously loaded through the haemloadcfg command. If any of the data is not valid, the command writes an error message that describes the error.
When the -c flag is processed, the command validates the data in the SDR, but does not create a new EMCDB file and does not update the EMCDB version string in the SDR.
The -n flag lets you build a test EMCDB file in the current directory. If anything goes wrong with the creation of the new file, the command writes an error message that describes the error.
When the -n flag is processed, the command uses the data in the SDR to create a test EMCDB file in the current directory, but it does not update the EMCDB version string in the SDR. If any of the data in the SDR is not valid, the command stops at the first error encountered.
If you specify both flags on the command line, the haemcfg command performs the actions of the -c flag.
After you have checked the data and the build process, issue the haemcfg command without any flags. This builds the new EMCDB file, places it in the /spdata/sys1/ha/cfg directory, and updates the EMCDB version string in the SDR.
Files
Standard Output
When the command executes successfully, it writes the following informational messages:
Reading Event Management data for partition syspar_name CDB=new_EMCDB_file_name Version=EMCDB_version_string
Standard Error
This command writes error messages (as necessary) to standard error.
Errors can result from causes that include:
For a listing of the errors that the haemcfg command can produce, see PSSP: Message Reference.
Exit Values
Security
You must have write access to the SDR to run this command.
To place an EMCDB file for a system partition into the /spdata/sys1/ha/cfg directory, you must be running with an effective user ID of root on the control workstation. Before running this command, you must set the SP_NAME environment variable to the appropriate system partition name.
Restrictions
To place an EMCDB file for a system partition into the /spdata/sys1/ha/cfg directory, you must be running with an effective user ID of root on the control workstation. Before running this command, you must set the SP_NAME environment variable to the appropriate system partition name.
If you run the haemcfg command without any flags, the command stops at the first error it encounters. With the -c flag on, the command continues, letting you obtain as much debugging information as possible in one pass. To reduce your debugging time, therefore, run the command with the debugging flags first.
Implementation Specifics
This command is part of RS/6000 Cluster Technology (RSCT), which is included with the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Prerequisite Information
For a general overview of configuring Event Management, see "The Event Management subsystem" chapter of PSSP: Administration Guide.
For a description of the SDR classes and attributes that are related to the EMCDB, see IBM RS/6000 Cluster Technology: Event Management Programming Guide and Reference.
Location
/usr/sbin/rsct/bin/haemcfg
Related Information
Commands: haemloadcfg
Examples
haemcfg -c
If there are any errors in the data, the command writes appropriate error messages.
To fix the errors, replace the data in the SDR. For more information, see the haemloadcfg command.
haemcfg -n
If there are any problems in creating the file, the command writes appropriate error messages.
haemcfg
In response, the command creates a new EMCDB file, places it in the staging directory as /spdata/sys1/ha/cfg/em.syspar_name.cdb, where syspar_name is the name of the current system partition, and updates the EMCDB version string in the SDR.