|pSeries 690 server or logical partition (LPAR). Close all HMC vterm
|sessions before running this command.
Purpose
sysparaid - Creates a layout for a new system partition configuration of an SP system.
Syntax
Flags
Operands
Description
Use this command to invoke the System Partitioning Aid, a tool for generating new system partition configuration layouts. |The sysparaid command is not valid on a system with an SP |Switch2 switch or on a switchless clustered enterprise server |system.
When invoked with the -i flag, it creates a switch-map file that will help the user to generate the input_file for creating a layout for a desired system partition configuration. When invoked with no flags or with the -s or -t flags, it attempts to partition the system according to the input requirement. If the attempt is unsuccessful, it will output appropriate error messages to the log and exit. If the attempt is successful and the -s flag is specified, the newly created layout will be saved at the desired location specified by the flag argument.
Prerequisite Information
The sysparaid command uses a set of built-in rules to create a layout for a desired system partition configuration. The following startup guidelines will help to generate an acceptable input to the command:
sysparaid -i -t spa_dir
This command places a spa.sysinfo file in the spa_dir if the -t flag is used; otherwise, it places it in the current directory. If an SDR is not present, issue the following command:
sysparaid -i -t spa_dir topology_file
where topology_file is the name of the topology file for the system to be partitioned.
Standard Input
This command requires an input file when invoked with no flag or the -s flag. The template for the input file can be found in /spdata/sys1/syspar_configs/bin .
Standard Output
Informational messages are written to standard output.
Standard Error
Error messages are written to standard error.
Output Files
This command creates spa.snapshot and spa.metrics under tmpdir (if specified) or under the current working directory. If the -s flag is specified and the attempt is successful, it creates the following under the layout directory:
When invoked with the -i flag, the command creates spa.sysinfo under tmpdir (if specified), or under the current working directory.
Security
Any user can run this command. Only users authorized to write to the system partitioning directory can save a generated layout under it.
Location
/usr/lpp/ssp/bin/sysparaid
Related Information
The spsyspar command provides the graphical user interface (GUI) for the System Partitioning Aid.
Examples
Number of Nodes in System: 32 Number of Frames in System: 2 Frame Type: tall Switch Type: HiPS Number of Switches in Node Frames: 2 Number of Switches in Switch Only Frames: 0 Node Numbering Scheme: switch_port_number Number of Partitions: 3 Partition Name: part1 Number of Nodes in Partition: 8 0 - 7 Partition Name: part2 Number of Nodes in Partition: 8 8 - 15 Partition Name: part3 Number of Nodes in Partition: 16 remaining_nodes
To use /tmp as the working directory, enter:
sysparaid -t /tmp inpfile
You should receive a message similar to the following:
A layout, for the desired system partition configuration or an equivalent, can be created. To save this layout, invoke the command again with -s option.
To save the layout for this configuration under /spdata/sys1/syspar_configs/2nsb0isb/config.8_8_16/layout.myconfig, enter:
sysparaid -s myconfig inpfile
To save the layout for this configuration under /tmp/custom/config1, enter:
sysparaid -s /tmp/custom/config1 inpfile
Number of Nodes in System: 87 Number of Frames in System: 6 Frame Type: tall Switch Type: SP Number of Switches in Node Frames: 6 Number of Switches in Switch Only Frames: 4 Node Numbering Scheme: switch_port_number Number of Partitions: 2 Partition Name: ProductionPartition Number of Nodes in Partition: 82 0 4 16 - 95 Partition Name: TestPartition Number of Nodes in Partition: 5 2 6 8 10 12
If you enter the sysparaid -s myconfig inpfile command, this configuration will be saved under /spdata/sys1/syspar_configs/6nsb4isb/config.12_84/layout.myconfig. Note that the nine unspecified switch port numbers have been allocated to one of the two system partitions.
Number of Nodes in System: 8 Number of Frames in System: 2 Frame Type: tall Switch Type: SP Number of Switches in Node Frames: 1 Number of Switches in Switch Only Frames: 0 Node Numbering Scheme: node_number Number of Partitions: 3 Partition Name: part1 Number of Nodes in Partition: 2 25 29 Partition Name: part2 Number of Nodes in Partition: 4 1 5 17 21 Partition Name: part3 Number of Nodes in Partition: 2 3 7
This input file for a particular SP system returned the location of an existing layout:
The layout for the desired/equivalent system partition configuration is under /spdata/sys1/syspar_configs/1nsb0isb/config.4_4_8/layout.2
switch_number switch_chip switch_port_number node_number
1 4 9 25
1 4 13 29
1 5 0 1
1 5 1 17
1 5 4 5
1 5 5 21
1 6 2 3
1 6 6 7
Number of Nodes in System: 32 Number of Frames in System: 2 Frame Type: tall Switch Type: NA Number of Switches in Node Frames: 0 Number of Switches in Switch Only Frames: 0 Node Numbering Scheme: switch_port_number Number of Partitions: 2 Partition Name: part1 Number of Nodes in Partition: 14 2 - 5 10 11 13 15 19 24 - 25 29 - 31 Partition Name: partition2 Number of Nodes in Partition: 18 remaining_nodes
To save the layout for this configuration under /spdata/sys1/syspar_configs/2nsb0isb/config.14_18/layout.myconfig, enter:
sysparaid -s myconfig inpfile
Purpose
s1term - Opens a connection to an SP node's S1 serial port.
Syntax
s1term [-G] [-w] frame_ID slot_ID
Flags
Operands
Description
Use this command to open a connection to the S1 serial port of the SP node contained in the slot specified by the frame_ID and slot_ID operands. The specified node must be in the current system partition unless the -G flag is also specified. By default, the connection is read only. As data arrives from the serial port, it is written to standard output. When the connection is read/write and standard input is a terminal, the terminal is placed in raw mode, that is, canonical processing is turned off in the terminal driver. As data is read from standard input, it is sent to the S1 serial port. Standard input and output can be files or pipes.
When the connection is read only, the command terminates upon receipt of a signal, usually generated by the terminal Interrupt key. When in read/write mode, the command terminates when either the termination character or End-of-File is read from standard input. The termination character is Ctrl-x by default. Another termination character can be used by setting the S1TERMESC environment variable to the octal (denoted by leading 0), decimal or hexadecimal (denoted by leading 0x) value of the desired termination character.
To execute this command, the user must be authorized to access the Hardware Monitor subsystem and, for the frame specified to the command, must be granted S1 permission. Since the Hardware Monitor subsystem uses SP authentication services, the user must execute the k4init command prior to executing this command. Alternatively, site-specific procedures can be used to obtain the tokens that are otherwise obtained by k4init.
|If you currently have a virtual terminal (vterm) session open
|through the Hardware Management Console (HMC) interface, the s1term
|command will fail when opening a console session to an IBM
|pSeries 690 server or logical partition (LPAR). Close all HMC vterm
|sessions before running this command.
Security
To execute the s1term command, you must be authorized to access the Hardware Monitor subsystem and must be granted "S1" permission for the hardware objects (frames, slots) specified in the command. Commands sent to hardware objects for which the user does not have "S1" permission are ignored.
Location
/usr/lpp/ssp/bin/s1term
Related Information
Commands: hmcmds, hmmon
Examples
s1term -w 12 8
s1term 9 2 > s1term.output
Purpose
tecad_pssp - Forwards PSSP events.
Syntax
Flags
Consult the TME 10 EIF User's Guide for the correct values of the other configuration parameters.
If an incorrect value is used, the default UNKNOWN is used.
Operands
None.
Description
The tecad_pssp command was designed to be executed by the PSSP Problem Management subsystem. It should not be executed by any other subsystem, since it depends on environment variables that are exported by the Problem Management daemon, pmand. Therefore, to forward PSSP events using the tecad_pssp command, you need to make a Problem Management subscription using either the SP Event Perspective, or using Problem Management directly. In either case, you should select tecad_pssp as the command to run for that subscription, and provide the appropriate parameters.
Prerequisite Information
Integrating TME 10 on the RS/6000 SP
Location
/usr/lpp/ssp/tecad_pssp
Related Information
Commands: pmandef, wtdumprl
Examples
This example creates event subscriptions using the pmandef command:
pmandef -s example1
-e "AnyResourceVariable;Any InstanceVector;AnyPredicate"
-c "$AGENT_PATH/tecad_pssp -l $CONF_PATH/tecad_pssp.cfg"
-r "AnyRearmPredicate"
-C "$AGENT_PATH/tecad_pssp -l $CONF_PATH/tecad_pssp.cfg"
-n 0
Purpose
ucfghsd - Makes a hashed shared disk unavailable.
Syntax
ucfghsd {-a | hsd_name...}
Flags
Operands
Description
This command unconfigures the already defined hashed shared disks. This command does not change the definition of the hashed shared disks; it makes the hashed shared disks unavailable on one node.
Security
You must be in the AIX bin group to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/ucfghsd
Related Information
Commands: cfghsd, defhsd, hsdatalst, lshsd, undefvsd
Examples
To unconfigure the hashed shared disk hsd1, enter:
ucfghsd hsd1
Purpose
ucfghsdvsd - Stops the virtual shared disks that comprise a hashed shared disk and makes the hashed shared disk and the virtual shared disks unavailable.
Syntax
ucfghsdvsd -a | {hsd_name...}
Flags
Operands
None.
Description
Use this command to unconfigure hashed shared disks and their underlying virtual shared disks. This command does not change the definition of the hashed shared disks and virtual shared disks; it just makes them unavailable to the node on which this command is run. The underlying virtual shared disks do not have to be in the stopped state for this command to work. The virtual shared disks will be stopped and then unconfigured.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit hsd_mgmt
and select the Unconfigure an HSD and its Underlying Virtual Shared Disks option.
Security
You must have access to the virtual shared disk subsystem via the sysctl service to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/ucfghsdvsd
Related Information
Commands: cfghsdvsd, ucfghsd, ucfgvsd
Examples
To unconfigure the hashed shared disk hsd1 and the virtual shared disks that comprise it, enter:
ucfghsdvsd hsd1
Purpose
ucfgvsd - Makes a virtual shared disk unavailable.
Syntax
ucfgvsd {-a | vsd_name ...}
Flags
Operands
Description
The ucfgvsd command unconfigures the specified virtual shared disks. This command does not change any virtual shared disk definitions. It moves virtual shared disks from the stopped state to the defined state.
If a configured hashed shared disk is using this virtual shared disk, you must first unconfigure the hashed shared disk before you unconfigure the virtual shared disk.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit vsd_mgmt
and select the Unconfigure a Virtual Shared Disk option.
Security
You must be in the AIX bin group to run this command.
Restrictions
If you have the Recoverable Virtual Shared Disk software installed and operational, do not use this command. The results may be unpredictable.
See PSSP: Managing Shared Disks.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/ucfgvsd
Related Information
Commands: cfgvsd, ctlvsd, lsvsd, preparevsd, resumevsd, startvsd, stopvsd, suspendvsd
Examples
To unconfigure the virtual shared disk vsd1vg1n1 in the stopped state, enter:
ucfgvsd vsd1vg1n1
Purpose
unallnimres - Deallocates Network Installation Management (NIM) resources from a NIM master to one or more NIM clients.
Syntax
unallnimres -h | -l node_list
Flags
Operands
None.
Description
Use this command to unallocate all NIM resources from a NIM client.
|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 unallnimres using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Error
This command writes error messages (as necessary) to standard error.
Exit Values
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).
Location
/usr/lpp/ssp/bin/unallnimres
Related Information
Commands: allnimres, setup_server
Examples
To unallocate boot/installation resources to boot/install client nodes 1, 3, and 5 from their respective boot/install servers, enter:
unallnimres -l 1,3,5
Purpose
undefhsd - Undefines a hashed shared disk.
Syntax
undefhsd hsd_name...
Flags
None.
Operands
Description
This command is used to remove a hashed shared disk by removing its definition from the system, including the special device files in /dev . The hashed shared disks must be unconfigured and in the defined state on all nodes in the system partition.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit delete_vsd
and select the Undefine a Hashed Shared Disk option.
Security
You must be in the AIX bin group and have write access to the SDR to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/undefhsd
Related Information
Commands: defhsd, hsdatalst
Examples
To delete the information associated with the hashed shared disk hsd1 from the SDR, enter:
undefhsd hsd1
Purpose
undefvsd - Undefines a virtual shared disk.
Syntax
undefvsd vsd_name ...
Flags
None.
Operands
Description
This command is used to remove virtual shared disk definition data from the System Data Repository (SDR) and any special device files from /dev for the given vsd_names on all the virtual shared disk nodes. The virtual shared disks must be unconfigured and in the defined state on all the virtual shared disk nodes.
You can use the System Management Interface Tool (SMIT) to run the undefvsd command. To use SMIT, enter:
smit delete_vsd
and select the Undefine a Virtual Shared Disk option.
Security
You must be in the AIX bin group to run this command.
You must have write access to the SDR to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/undefvsd
Related Information
Commands: defvsd
Examples
To delete the information associated with the virtual shared disk vsd1vg2n1 from the SDR, enter:
undefvsd vsd1vg2n1
Purpose
unfencevsd - Gives applications running on a node or group of nodes access to a virtual shared disk or group of virtual shared disks that were previously fenced from applications running on those nodes.
Syntax
|unfencevsd {-a | -v |vsd_name_list} {-n node_list |[-f] | -r}
Flags
Operands
None.
Description
Under some circumstances, the system may believe a node has become inoperable and may begin recovery procedures when the node is actually operational, but is cut off from communication with other nodes running the same application. In this case, the problem node must not be allowed to serve requests for the virtual shared disks it normally manages until recovery is complete and the other nodes running the application recognize the problem node as operational. The fencevsd command prevents the problem node from filling requests for its virtual shared disks. The unfencevsd command allows fenced nodes to regain access to the virtual shared disks.
This command can be run from any node.
Notes:
Security
You must be in the AIX bin group to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/unfencevsd
Related Information
Commands: fencevsd, lsfencevsd, lsvsd, updatevsdtab, vsdchgserver
Refer to PSSP: Managing Shared Disks for information on how to use this command in writing applications.
Examples
unfencevsd -v vsd1,vsd2 -n 5
unfencevsd -v vsd1,vsd2 -n 7 -f
Purpose
updatehsd - Lets you change the option in the System Data Repository (SDR) that prevents overwriting the Logical Volume Control Block (LVCB) for specified hashed shared disks.
Syntax
Flags
Operands
None.
Description
Use this command only on the control workstation.
The hashed shared disk name must be specified. You must choose either protect_lvcb or not_protect_lvcb. The hashed shared disk must be defined in the System Data Repository (SDR).
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit set_HSDdd_parms
|and select the Update Hashed Shared Disk Option or
smit hsd_mgmtd_parms
|and select the Set/Show HSD Device Driver Operational Parameters |followed by the Update Hashed Shared Disk Option.
Security
You must have access to the virtual shared disk subsystem via the sysctl service to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/updatehsd
Related Information
Commands: defhsd, lshsd, hsdatalst
Examples
To set the protect_lvcb option for hsdcont01 and hsdcont02, enter:
updatehsd -d hsdcont01,hsdcont02 -o protect_lvcb
Purpose
updatevsdnode - Changes IBM Virtual Shared Disk subsystem options in the System Data Repository (SDR).
Syntax
Flags
Buddy buffers are only used on the servers. On client nodes you may want to set max_buddy_buffers to 1.
Operands
None.
Description
Use updatevsdnode to change the specified values in the SDR for all nodes in node_list.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit vsd_mgmt
and select the Set/Show Virtual Shared Disk Device Driver Operational Parameters option or the Update IBM Virtual Shared Disk Device Driver Node Parameters option.
Security
You must have access to the virtual shared disk subsystem via the sysctl service to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/updatevsdnode
Related Information
Commands: lsvsd, vsdatalst, vsdnode
Examples
To increase the buddy buffer size to 48 maximum sized buddy buffers on node 3, enter:
updatevsdnode -n 3 -s 48
Purpose
updatevsdtab - Changes the IBM Virtual Shared Disk subsystem option to set cache or nocache in the System Data Repository (SDR).
Syntax
updatevsdtab {-v vsd_names | -a} {[ -o {cache | nocache}] [-s ]} [-f]
Flags
Operands
None.
Description
Use this command to update the SDR, if necessary. When a feature of the virtual shared disk in the SDR (such as cache/nocache option or the virtual shared disk size), is changed using the updatevsdtab command, the change will not take effect until the virtual shared disk is unconfigured and configured again.
If the -f flag is specified, the virtual shared disks involved will be reconfigured (using sysctl) on all nodes that are up and initially had these virtual shared disks configured.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit vsd_mgmt
and select the Set/Show IBM Virtual Shared Disk Device Driver Operational Parameters option or the Update IBM Virtual Shared Disk Options option.
Security
You must have access to the virtual shared disk subsystem via the sysctl service to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/updatevsdtab
Related Information
Commands: defvsd, updatevsdnode
Examples
updatevsdtab -a -o nocache
updatevsdtab -v USER1n3 -s
Purpose
|updauthfiles - Updates or creates (if necessary) the |.k5login, .klogin, and .rhosts |files on the control workstation and on all nodes in the system for which some |combination of DCE, K4, or Standard AIX are defined as authentication methods |or when no authentication methods are defined. | |
Syntax
updauthfiles [-h] [-I]
Flags
Operands
None.
Description
The updauthfiles command determines the authorization methods for the local host (control workstation or node) by reading the auth_root_rcmd attribute in the System Data Repository (SDR) |system partition object. If the specified |authorization method has been correctly configured and is running, it creates or updates the appropriate authorization file for Standard AIX, |Kerberos V4, and Kerberos V5 (using DCE principals). |If restricted root access (RRA) is enabled, the files will be |generated with no entries for root access from the nodes to the control |workstation or from the nodes to other nodes. If no authorization |methods (none) were selected, the authorization files will be |generated with no PSSP entries for the system partition.
The updauthfiles command copies the .klogin file from the /spdata/sys1/spsec directory to root's home directory when run on the control workstation. |If running on a node, it retrieves a copy of the |.klogin file |from the control workstation |unless restricted root access is activated, in which case the |.klogin file is generated at the node. The control workstation's authorization files are updated according to the union of all authentication methods in the system.
|If authorization methods or restricted root access settings have |recently changed, updauthfiles will add or delete PSSP-generated |entries from the authorization files to reflect the changes. Customer |added entries will be retained.
|If no authorization method (none) is selected, it cannot be |combined with any other authorization method on the system |partition.
An error message is generated and logged for any authorization file unable to be created or updated.
|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 updauthfiles using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Input
The command reads the .k5login, .klogin, and .rhosts files.
Standard Output
The command updates the .k5login, .klogin, and .rhosts files.
The command |may issue |a remote copy from a node to the control workstation to copy the .klogin file.
A log file is created in /var/adm/SPlogs/auth_install/log.
Exit Values
|Correction of errors is necessary to complete the process. Problems |relating to the creation of .rhost and |.k5login files should be corrected on the node, and the |command should be rerun. Problems due to copying the |.klogin file may need to be corrected on the control |workstation; then the command should be rerun on the node. |Problems relating to the creation of the .klogin file on the |control workstation or on the nodes when restricted root access is enabled, |should be fixed from wherever updauthfiles was run.
Security
You must have root privilege to run this command.
Related Information
Commands: rcp
Files: .rhost, .klogin, and .k5login
Location
/usr/lpp/ssp/bin/updauthfiles
Examples
To create the appropriate authorization files on the control workstation, enter:
/usr/lpp/ssp/bin/updauthfiles