Purpose
spmkvgobj - Creates a new root volume group for a node or series of nodes in the System Data Repository (SDR).
Syntax
Flags
|If multiple physical volumes are specified, separate them by commas for |logical names and by colons for all other formats. Different formats |may be used for the different physical volumes except when using logical |names. The default is hdisk0.
Operands
Description
Use the spmkvgobj command to create a new root volume group on a node or group of nodes in the System Data Repository (SDR). When this command is run and the SDR is changed, setup_server must be run on the affected boot/install servers and affected nodes may need to be customized or installed to apply the changes. Certain volume group information such as mirroring and the pv_list may be updated using the spmirrorvg or spunmirrorvg commands.
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 Parallel System Support Programs (PSSP) Licensed Program (LP).
Location
/usr/lpp/ssp/bin/spmkvgobj
Related Information
Commands: spbootins, spchvgobj, spmirrorvg, sprmvgobj, spunmirrorvg
Examples
spmkvgobj -r rootvg2 -h \
ssar//567464736372821:ssar//67464736372821 -l 2,3
spmkvgobj -r rootvg2 -h 00-00-00-0,0:00-00-00-1,0:00-00-00-2,0 \
-c 2 -q false -i bos.obj.ssp.432 -l 7
Purpose
spmon - Operates the system controls and monitors system activity.
Syntax
Flags
All spmon commands require a -target parameter except those with -diagnostics, and -help parameters.
Turns the power on or off for the node, frame, or switch specified as the target. For example:
spmon -G -p off frame1 spmon -p off node16 spmon -G -p off frame2/switch spmon -G -p off frame11/switch2
|On systems that do not have a key mode switch, the spmon |-reset command produces a dump.
The mux setting must match the physical wiring of the switch clocks and requires a frame as its target. For a switch in node 17, use a frame as the target or frame/switchN for a switch in a switch-only frame.
For each switch, checks:
The tests are in dependent order. If any of these are unsuccessful, the subsequent tests do not run.
The -target flag is optional. Any parameter without a flag is assumed to be the target. You can also have multiple target-flags (-t), which are optional.
Operands
None.
Description
Any unique abbreviation of flags and keywords is acceptable.
Specify target_value with the hierarchical format (or tree structure). The format is:
/SP/frame/frameN/[nodeM|switch M]/variableX/value
You can use wildcards (*) to specify more than one target node or frame for the query command.
You can use aliases in place of fully qualified hierarchical target values. Aliases require less typing and may be more intuitive than the fully qualified targets. Leaving the leading slash (/) off the target indicates that it is an alias.
There are two formats for aliases:
You can include a variable and attribute after the alias.
The spmon command fails if any of the hardware targeted is not supported by the version of PSSP on the machine where the command was issued.
Security
System Control Mode: To execute the spmon command in System Control Mode you must be authorized to access the Hardware Monitor subsystem and must be granted "VFOP" permission for the hardware objects (frames, slots) specified in the command. Commands sent to hardware objects for which the user does not have "VFOP" permission are ignored.
Monitor Mode: To execute the spmon command in Monitor Mode you must be authorized to access the Hardware Monitor subsystem and must be granted Monitor permission for the hardware objects (frames, slots) specified in the command. State information is not returned for hardware objects for which the user does not have Monitor permission.
Location
/usr/lpp/ssp/bin/spmon
Related Information
The sphardware command launches a graphical user interface for monitoring and controlling an SP system.
Commands: hmcmds, hmmon
Examples
spmon -q -t /SP/frame/frame1/node1/keyModeSwitch/value 0
spmon node1/keyModeSwitch/value 0
spmon -L frame1/node1
You should receive output similar to the following:
_____________ | _ _ _ | | |_| |_| |_| | Frame 1, Node 1 | |_| |_| |_| | |_____________|
spmon -G -q -l frame*/switch*/mux/value /SP/frame/frame1/switch17/mux/value/0
spmon -M frame1/node*/powerLED/value 2 1
spmon -M -q -l frame1/node*/powerLED/value /SP/frame/frame1/node1/powerLED/value/1 /SP/frame/frame1/node3/powerLED/value/1 /SP/frame/frame1/node5/powerLED/value/1 /SP/frame/frame1/node7/powerLED/value/1 /SP/frame/frame1/node9/powerLED/value/1 /SP/frame/frame1/node10/powerLED/value/1 /SP/frame/frame1/node11/powerLED/value/1 /SP/frame/frame1/node12/powerLED/value/1 /SP/frame/frame1/node13/powerLED/value/1 /SP/frame/frame1/node14/powerLED/value/1 /SP/frame/frame1/node15/powerLED/value/1 /SP/frame/frame1/node16/powerLED/value/1 /SP/frame/frame1/node1/powerLED/value/2 /SP/frame/frame1/node1/powerLED/value/1
spmon -p off frame2/node3
If node3 on frame2 is outside the current system partition, enter:
spmon -G -p off frame2/node3
spmon -p off node19
spmon -k service node1
spmon -G -p off frame1
spmon -G -p off frame1/A
spmon -G -m i frame1
or
spmon -G -m i frame1/switch
spmon -G -m i frame10/switch4
Purpose
spmon_ctest - Verifies that the System Monitor component is configured correctly.
Syntax
spmon_ctest [-l log_file] [-q]
Flags
Operands
None.
Description
This command is designed to be run after installing the SP system to verify that the System Monitor is configured correctly. The test checks to make sure that the hardware is running, that it can be queried, and determines whether any node objects were created in the System Data Repository (SDR). The test also indicates whether the RS232 lines are connected properly.
A return code of zero indicates that the test completed as expected; otherwise it returns the number of errors. If you do not specify the -q flag, a message is displayed on standard output that indicates if the test was successful or not. In either case, the command returns 0 if successful, 1 if unsuccessful. If errors are detected, more detailed information is recorded in the log file. If you do not specify the -l flag, error messages are recorded in /var/adm/SPlogs/spmon_ctest.log.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit SP_verify
and select the System Monitor Configuration option.
You must run this test from a user who has monitor authority in /spdata/sys1/spmon/hmacls. The user must also have a nonexpired authentication ticket.
Refer to the "RS/6000 SP files and other technical information" section of PSSP: Command and Technical Reference for additional Kerberos information.
Files
Security
You must root privilege to run this command.
Location
/usr/lpp/ssp/bin/spmon_ctest
Related Information
Commands: CSS_test, jm_install_verify, jm_verify, SDR_test, SYSMAN_test, spmon_itest
Examples
To verify installation of the SP System Monitor, saving error messages in spmon.err in the current working directory, enter:
spmon_ctest -l spmon.err
Purpose
spmon_itest - Verifies that the System Monitor is installed and operational.
Syntax
spmon_itest [-l log_file] [-q]
Flags
Operands
None.
Description
This command is designed to be run after installing the SP system to verify that the System Monitor is installed correctly.
A return code of zero indicates that the test completed as expected; otherwise it returns the number of errors. If you do not specify the -q flag, a message is displayed on standard output that indicates if the tests were successful or not. In either case, the command returns 0 if successful, 1 if unsuccessful. If errors are detected, more detailed information is recorded in the log file. If you do not specify the -l flag, error messages are recorded in /var/adm/SPlogs/spmon_itest.log.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit SP_verify
and select the System Monitor Installation option.
Files
Security
You must have root privilege to run this command.
Location
/usr/lpp/ssp/bin/spmon_itest
Related Information
Commands: CSS_test, jm_install_verify, jm_verify, SDR_test, SYSMAN_test, spmon_ctest
Examples
To verify installation of the SP System Monitor, saving error messages in spmon.err in the current working directory, enter:
spmon_itest -l spmon.err
Purpose
spnkeyman_start - Conditionally starts the SP Per Node Key Management daemon on the control workstation, node, or stand-alone workstation. The command runs locally on the host where the daemon is to be started.
Syntax
Flags
None.
Operands
None.
Description
The spnkeyman_start command is used to conditionally start the key management daemon on a specific machine. When this command is executed the key management daemon spnkeymand is started.
The daemon will not be started if DCE has not been installed on the workstation. On the SP, the script will generally be run from rc.sp during re-boot. On a stand alone workstation, the script can be started with an inittab entry: nkeyman:2:once:/usr/lpp/ssp/bin/spnkeyman_start.
If DCE is configured on the control workstation after installation, it is necessary for the system administrator to start the daemon manually after the SP has been configured to use DCE.
The daemon requires:
If you need to stop the spnkeymand daemon, enter:
stopsrc -s spnkeyman
Standard Error
This command issues error messages to alert a system administrator to a problem.
Exit Values
Errors result in the SP Key Management daemon not running, and consequently the services that rely on SP Key Management to provide key files will ultimately be unsuccessful.
Security
You must have root privilege to run this command.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Prerequisite Information
The section on SP system security in PSSP: Administration Guide and IBM Distributed Computing Environment manuals set.
Location
/usr/lpp/ssp/bin/spnkeyman_start
Related Information
Commands: startsrc
Examples
To start the key management daemon, enter:
spnkeyman_start
Purpose
sprestore_config - Restores the system to a given system partitioning configuration as specified in the System Data Repository (SDR) which was previously archived.
Syntax
sprestore_config archive_file [-h]
Flags
Operands
Description
The sprestore_config command is valid only on systems with no switch or with an SP switch. |This command is not valid on a system with an SP Switch2 switch or |on a switchless clustered enterprise server system.
Use this command to restore the SDR from an archive file that was previously created with the SDRArchive command. In addition to restoring the SDR (using the SDRRestore command), the sprestore_config command also restores system partition-sensitive subsystems (for example, hats, hb, and hr) to their previous state. This command is most useful when recovering from an attempt to partition the SP (see the spapply_config command).
You can use the System Management Interface Tool (SMIT) to run the sprestore_config command. To use SMIT, enter:
smit syspar_restore
and enter (or select from a generated list) the name of the SDR archive from which to restore.
Notes:
Exit Values
Security
You must have root privilege to run this command. You must also have SDR write access for each partition you are restoring.
Related Information
Commands: SDRArchive, SDRRestore, spapply_config, spcustomize_syspar, spdisplay_syspar, spverify_config, syspar_ctrl
Files: nodelist, topology
Examples
To restore the SDR and the system-partition sensitive subsystems (for example, hats, hb, and hr) from the archive 'backup.95110.1620' which was previously created using the SDRArchive command, enter:
sprestore_config backup.95110.1620
Purpose
sprmuser - Removes a user account from the SP system.
Syntax
sprmuser [-i] [-p] [-r] name
Flags
Operands
None.
Description
The -i and -r options are unique to the SP system.
You can use the System Management Interface Tool (SMIT) to run the sprmuser command. To use SMIT, enter:
smit spusers
and select the Remove a User option.
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run sprmuser using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
You must have root privilege to run this command.
This command runs from the control workstation only.
Location
/usr/lpp/ssp/bin/sprmuser
Examples
sprmuser charlie
sprmuser -pr charlie
Purpose
sprmvgobj - Removes a root volume group for a node or series of nodes from the System Data Repository (SDR).
Syntax
Flags
Operands
Description
The sprmvgobj command is used to remove a root volume group on a node or group of nodes from the System Data Repository (SDR).
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 Parallel System Support Programs (PSSP) Licensed Program (LP).
Location
/usr/lpp/ssp/bin/sprmvgobj
Related Information
Commands: spbootins, spchvgobj, sprmvgobj
Examples
To remove a root volume group on nodes 2 and 3, enter:
sprmvgobj -r rootvg2 -l 2,3