Command and Technical Reference, Volume 2

splstdata

Purpose

splstdata - Displays configuration data from the System Data Repository (SDR) or system information for each node.

Syntax

|splstdata: |{-A | -n | -s | |-b | -a | -u | |-v | -g | -h | |-i | -d | -x}
: [-G] [{start_frame start_slot {node_count | rest} |
: -N node_group | -l node_list}]

splstdata: {-e | -f | -p | -X}

Flags

-A: Displays SDR accounting data.
-n: Displays SDR node data.
-s: Displays SDR node and dependent node switch data.
-b: Displays SDR boot/install data.
-a: Displays SDR LAN data only for nodes in the current system partition.
-u: Displays SDR /usr data.
-v: Displays volume group information. |
|-g: |Displays aggregate IP information associated with a particular |adapter.
-h: Displays hardware data for each node, as provided by the lscfg command.
-i: Displays network adapter data for each node, as provided by the netstat -n command.
-d: Displays file system data for each node, as provided by the df command.
-x: Displays node expansion data for node expansion units connected to the node(s) specified by this command. If no nodes are specified, the command displays data for all node expansion units in the current system partition. Node expansion units reside in the system partition that their associated node resides in, or in the default system partition if the node expansion unit is not connected to a node.
-G: Allows the specification of nodes to include one or more nodes outside of the current system partition.
-N node_group: Specifies a node group to be used for this operation. If -G is supplied, a global node group is used. Otherwise, a partitioned-bound node group is used.
-l node_list: Specifies a list of nodes to be used for this operation. Either specify a comma-delimited list of node numbers, or a file containing one line of data which is a comma-delimited list of node numbers. The file can also contain comment lines (preceded by a #) and lines that are all white space. If you use the node_list field, do not use the start_frame, start_slot, or node_count fields. (This is lowercase l, as in list.) |
|-e: |Displays SP object attributes and their values from the SDR. |
|-f: |Displays SDR frame data.
-p: Lists all information for the currently-applied system partition configuration (all active system partitions on the system). This includes the list of system partitions, plus information about each system partition.
-X: Displays node expansion information for node expansion units that are not connected to any node. When using -X you cannot specify the start_frame, start_slot, and node_count fields, or the -l or -N flags.

Operands

start_frame

Frame number of first node to be used for this operation. Specify a value between 1 and 128 inclusive. If start_frame, start_slot and node_count are not specified, the default is 1 1 rest. If start_frame is specified, start_slot and node_count must also be specified.

start_slot

Slot number of first node to be used for this operation. Specify a value between 1 and 16 inclusive.

Note:: The start_frame and start_slot must resolve to a node in the current system partition.

|node_count

|Number of nodes to be used for this operation. Node information is |provided for successive nodes within a frame. If the count of nodes |causes the nodes in a frame to be exhausted, the operation continues for nodes |in the next sequential frame. Specify a value between 1 and 512 |inclusive. If rest is specified, all the nodes from |start_frame start_slot to the end of your system are used.

|Note:: The node_count is considered to be within the current system |partition. |

Description

You can use the System Management Interface Tool (SMIT) to run the splstdata command. To use SMIT, enter:

smit list_data

and select the System Data Repository option for the information you want to see. To see system information for each node, enter:

smit config_data

and select the option for the information you want.

|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: |

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run splstdata using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Security

Use of the -x flag requires the user to have monitor permission to access information about hardware objects.

This command should be run only on the control workstation. You must be logged into the control workstation as root to execute this command.

Location

/usr/lpp/ssp/bin/splstdata

splstnodes

Purpose

splstnodes - Lists to standard output information about nodes.

Syntax

splstnodes: [-h] [-x] [ -G] [-d delimiter] [ -p str] [-s attr]
: [-t {standard | dependent}] [ -N node_group]
: [attr==value ...] [attr ...]

Flags

-h

Displays usage information.

-G

Removes system partition boundaries for this invocation. This causes the command to consider all nodes regardless of system partition.

-x

Inhibits the output of the header record.

-d delimiter

Forces the delimiter between tokens to be delimiter, where delimiter is any string value. If this flag is used, only one copy of the delimiter is used between tokens, even if the delimiter is a blank.

-p str

Prints the str string in place of an attribute that does not apply to the object being output. The default is to print two double quotes ('').

-s attr

Sorts the output by the value of the attr attribute.

-t

Restricts the query to a specific node type. The node type can be one of the following:

standard: Only SP nodes (nodes in a frame/slot) are considered for output.
dependent: Only dependent nodes are considered for output.

If the -t flag is not specified, the default is to consider both standard and dependent nodes for output.

-N node_group

Restricts the query to only the nodes in the node group specified by node_group. If node_group is a system node group, the -G flag is implied.

Operands

attr==value: Used to specify certain node objects to be returned. The attr token must be a valid attribute of one of the node classes in the System Data Repository (SDR) (Node or DependentNode). If attr exists in both node classes, the objects from each class will be considered, unless that class is excluded with the -t flag. The token value is the value of attr that objects must have to be returned by this invocation of the command.
attr: Used to specify the attributes to be returned as output of the command. It does not limit the node objects that are considered for output. If an attr argument is not specified, the node_number attribute is returned.

Description

Use this command to get configuration information about any node from the SDR. For a complete list of node attributes, see the Node and DependentNode classes in "The System Data Repository" appendix in PSSP: Administration Guide.

Not all of the attributes are applicable to each type of node.

You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:

smit list_extnodes

Environment Variables

The environment variable SP_NAME is used (if set) to direct this command to a system partition. The default is to use the default system partition when on the control workstation and the system partition of the node when on a node.

Standard Output

This command writes informational messages to standard output.

Standard Error

This command writes all error messages to standard error.

Exit Values

0: Indicates the successful completion of the command.
nonzero: Indicates that an error occurred.

Implementation Specifics

You must specify an attribute in order for it to be displayed in the output. The attribute in the sort option (-s flag) and the attributes in the form attr==value must be repeated in order for them to be displayed.

Location

/usr/lpp/ssp/bin/splstnodes

Examples

To list the node number of all wide node objects in the current system partition, enter:
```
splstnodes slots_used==2
```
You should receive results in the following output, if four wide nodes are in the system partition in slots 1, 3, 5, and 7:
```
node_number
1
3
5
7
```

To list the reliable_hostname attribute of SP nodes along with their node numbers and have the output sorted by node number, enter:

splstnodes -t standard -s node_number node_number reliable_hostname

You should receive results in the following output:

node_number reliable_hostname
 
1 k22n1.ppd.pok.ibm.com
3 k22n3.ppd.pok.ibm.com
5 k22n5.ppd.pok.ibm.com
7 k22n7.ppd.pok.ibm.com

To list the "wide nodes" in the system, regardless of system partition, enter:
```
splstnodes -G slots_used==2
```
You should receive results in output similar to the following:
```
node_number
1
3
5
7
19
21
23
```
To list the snmp_community_name attribute of any SP dependent nodes along with their node numbers, enter:
```
splstnodes -t dependent node_number snmp_community_name
```
If you have dependent nodes, you should receive output similar to the following:
```
node_number snmp_community_name
         8   mycomm
         2   yourcomm
```

splsuser

Purpose

splsuser - Lists the attributes of an SP user account.

Syntax

splsuser [-c | -f] name

Flags

-c: Displays the attributes for the user in colon-separated records.
-f: Displays the attributes for the user in stanza format.

Operands

name: Name of the user account you want to view.

Description

You can only list the information for one SP user at a time. Unlike the AIX lsuser command, the ALL option and the -a flag are not supported for this command.

If you specify this command with no flags, the information of the user appears in a sequential display of attribute and values.

You can use the System Management Interface Tool (SMIT) to run the splsuser command. To use SMIT, enter:

smit spusers

and select the Change/Show Characteristics of a User option.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run splsuser using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Location

/usr/lpp/ssp/bin/splsuser

Examples

To display the attributes of the user account rob in a colon-separated list, enter:
```
splsuser -c rob
```
You should receive output similar to the following:
```
#name:id:pgrp:groups:home:shell:gecos:login
 
rob:16416:1::/u/rob on k46s.hpssl.kgn.ibm.com:/bin/ksh::true
```

To display the attributes of the user account rob in stanza format, enter:

splsuser -f rob

You should receive output similar to the following:

rob:
        id=16416
        pgrp=1
        groups=
        home=/u/rob on k46s.hpssl.kgn.ibm.com
        shell=/bin/ksh
        gecos=
        login=true

spmgrd daemon

Purpose

spmgrd - Automates management and configuration required for extension nodes.

Syntax

spmgrd [-s | -l] -f filename -m [size | 0]

Flags

-s: Specifies that short tracing is to be turned on as part of initialization processing. This is used to capture trace events that occur during bring-up. The trace file is located in /var/adm/SPlogs/spmgr/spmgrd.log unless overridden. Short tracing does not include informational messages nor the content of messages exchanged with Simple Network Management Protocol (SNMP) agents. The default is for tracing to be turned off.
-l: Specifies that long tracing is to be turned on as part of initialization processing. This is used to capture trace events that occur during bring-up. The trace file is located in /var/adm/SPlogs/spmgr/spmgrd.log unless overridden. Long tracing includes informational messages and the content of messages exchanged with SNMP agents in addition to error messages. The default is for tracing to be turned off.
-f: Specifies the name of a trace file. The default trace file name is /var/adm/SPlogs/spmgr/spmgrd.log.
-m: Specifies the maximum trace file size in bytes. When 0 is specified, there is no maximum size. The default is 0.

Operands

None.

Description

The spmgrd daemon is part of the spmgr subsystem and can only be controlled using the System Resource Controller (SRC). This daemon acts as an SNMP Manager monitoring SNMP trap messages received from SNMP agents supporting dependent nodes. A trap message may contain state information about an attached dependent node or may request the transfer of configuration data for a dependent node supported by the sending SNMP agent. When requested by a trap message, spmgrd transfers configuration data to the requesting SNMP agent. The data transfer is in the form of an SNMP set-request message containing the SNMP object instantiations representing configuration aspects of the dependent node and the values to which the aspects are to be set. When a trap message indicates that a dependent node previously fenced from the switch network with the "automatic rejoin" option is now active, spmgrd will automatically issue an Eunfence command to trigger the appropriate unfence processing.

The spmgrd daemon keeps log messages in a default file or in a file specified by the filename variable if the -f flag is specified. When the size of the log file exceeds an optional user-specified maximum log file size, the spmgrd daemon rotates the log file by moving the old log file to another file as follows:

*   LogFile.3 is deleted.
*   LogFile.2 is moved to LogFile.3.
*   LogFile.1 is moved to LogFile.2.
*   LogFile.0 is moved to LogFile.1.
*   LogFile is moved to LogFile.0.
*   LogFile continues in LogFile.

The spmgrd daemon only runs on the control workstation.

The spmgrd daemon is controlled using the SRC. The spmgrd daemon is known to the SRC as the spmgr subsystem. Use the following SRC commands to manipulate the spmgr subsystem:

startsrc

Starts a subsystem, group of subsystems, or a subserver. Issuing the startsrc -s spmgr command causes the spmgrd daemon to be started. Any spmgrd switches must be set using the startsrc command -a switch and must be enclosed within double quotes ('').

stopsrc

Stops a subsystem, group of subsystems, or a subserver.

traceson

Enables tracing of a subsystem, group of subsystems, or a subserver. Long tracing is specified by using the -l switch.

tracesoff

Disables tracing of a subsystem, group of subsystems, or a subserver.

lssrc

Gets the status of a subsystem, group of subsystems, or a subserver. When the long form of the subsystem's status is requested, information provided by the spmgr subsystem includes:

Trace information:
- Whether tracing is on or off
- The name of the trace file
- The mode of tracing (long or short)
- The trace file size limit (if any)
Summary information about the traps received
The content and the completion status of the snmpinfo commands issued by the spmgrd daemon. The snmpinfo commands are issued internally to request the SNMP agent managing a dependent node to change the dependent node's administrative state (this occurs whenever an enadmin command is entered by a user). The snmpinfo command is also issued internally to send configuration data for a dependent node to the SNMP agent managing it (the request for configuration data is received in the form of a trap message).

Files

/var/adm/SPlogs/spmgr/spmgrd.log: Is the spmgrd trace file.
/usr/lpp/spp/config/spmgrd/ibmSPDepNode.my: Is the Management Information Base (MIB) file containing the ibmSPDepNode object group that defines dependent node configuration objects.
/usr/lpp/ssp/config/spmgrd/ibmSPDepNode.defs: Is the compiled ibmSPDepNode.my object file.
/etc/services: Contains a line, spmgrd-trap, that defines the User Datagram Protocol (UDP) port number over which trap messages are received from an SNMP agent supporting dependent nodes.

Implementation Specifics

This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP) ssp.spmgr file set.

Location

/usr/lpp/ssp/bin/spmgrd

Related Information

Commands: enadmin, lssrc , startsrc, stopsrc, tracesoff , traceson

Examples

To start the spmgr subsystem (for example, the spmgrd daemon with short tracing on), enter:
```
startsrc -s spmgr -a'-s'
```
Use the traceson and tracesoff commands to control tracing after the spmgrd daemon is started.
```
traceson -ls spmgr (to turn on long tracing)
tracesoff -s spmgr (to stop tracing)
```
To stop the spmgr subsystem, enter:
```
stopsrc -s spmgr
```
To obtain the trace status and a list of snmpinfo commands issued by the spmgr subsystem since it was last activated, enter:
```
lssrc -ls spmgr
```

spmirrorvg

Purpose

spmirrorvg - Initiates mirroring on a node or set of nodes.

Syntax

spmirrorvg [-f] {start_frame start_slot {node_count | rest} | -l node_list}

Flags

-f: Forces the physical volume to be added to the specified volume group unless it is a member of another volume group in the Device Configuration Database or of a volume group that is active. If the volume group is varied off, and -f is specified, the physical volume will be added to the volume group.
-l node_list: Specifies a list of nodes for this operation. This list can be a single numeric node number, or a list of numeric node numbers separated by commas.

Operands

|start_frame

|Specifies the frame number of the first node to be used for this |operation. Specify a value between 1 and 128 inclusive. |

|start_slot

|Specifies the slot number of the first node to be used for this |operation. Specify a value between 1 and 16 inclusive.

|Note:: The start_frame and start_slot must resolve to a node in |the current system partition. |

|node_count

|Specifies the number of nodes to be used for this operation. The |node information is added for successive nodes within a frame. If the |count of nodes causes the nodes in a frame to be exhausted, the operation |continues for nodes in the next sequential frame. Specify a value |between 1 and 512 inclusive. If rest is specified, all the |nodes from start_frame start_slot to the end of your system are |used.

|Note:: The node_count is considered to be within the current system |partition. |

Description

The spmirrorvg command uses information found in the Volume_Group object to initiate mirroring on a node. If the number of requested copies is already achieved on the node, spmirrorvg exits. If the number of copies has not been achieved, the spmirrorvg command uses the pv_list attribute to extend the named volume group. After extending the volume group, spmirrorvg calls the AIX mirrorvg command to make two or three copies of the volume group. If not enough disks are specified in the pv_list to maintain strictness this command will exit. Quorum will be set according to the quorum attribute in the Volume_Group object. If the state of quorum changes as a result of running the spmirrorvg command, a message will be displayed that the node needs to be rebooted. The AIX commands bosboot and bootlist are run by spmirrorvg. bosboot updates the bootable image and bootlist sets the node bootlist to reflect multiple bootable logical volumes.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run spmirrorvg using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Exit Values

0: Indicates the successful completion of the command.
1: Indicates that a recoverable error occurred, some changes may have succeeded.
2: Indicates that an irrecoverable error occurred and no changes were made.

Security

|You must have root privilege and a valid Kerberos ticket to run this |command, or be running with the secure remote commands enabled.

Files

Log file created on node which contains AIX error messages if an error occurs during mirroring: /var/adm/SPlogs/sysman/mirror.out

Implementation Specifics

This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).

Location

/usr/lpp/ssp/bin/spmirrorvg

Related Information

Commands: spchvgobj, spunmirrorvg

Examples

To initiate mirroring on node 1 for the rootvg volume group enter:
```
spmirrorvg  -l 1
```
To initiate mirroring on a list of nodes enter:
```
spmirrorvg  -l 1,2,3
```

spmkuser

Purpose

spmkuser - Adds a new user account to the SP system.

Syntax

spmkuser [attribute =value ... ] name

Flags

None.

Operands

attribute=value: Pairs of the supported attributes and values as follows.
name: User login name. This name must follow the same rules enforced by the AIX mkuser command.

Supported Attributes and Values

id

ID of the user specified by the name operand.

pgrp

Principle group of the user specified by the name operand.

gecos

General information about the user.

groups

The secondary groups to which the user specified by the name operand belongs.

home

Host name of the file server where the home directory resides and the full path name of the directory. You can:

Specify a host and directory in the format host:path, just specify the directory and have the host default to a value set in the SMIT site environment panel or the spsitenv command. If this value has not been set, then the host will default instead to the local machine name, if you do not specify host explicitly.

login

Indicates whether the user specified by the name operand can log in to the system with the login command. This option does not change the /etc/security/user file. Instead, it alters the user password field in /etc/security/passwd.

shell

Program run for the user specified by the name operand at the session initiation.

Description

The -a flag is not supported. Except for home, the rules for the supported attributes and values correspond to those enforced by the AIX mkuser command.

All other attribute and value pairs are not supported.

The standard administrative AIX privileges do not apply to the SP users.

This command generates a random password for the user and stores it in /usr/lpp/ssp/config/admin/newpass.log. The root user has read and write permission to this file. It is the administrators responsibility to communicate this password to the new user and periodically delete the contents of this file.

You can use the System Management Interface Tool (SMIT) to run the spmkuser command. To use SMIT, enter:

smit spusers

and select the Add a User option.

Note:: The home directory must be in an exported file system before you can run this command.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run spmkuser 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 is run from the control workstation only.

Location

/usr/lpp/ssp/bin/spmkuser

Examples

Note

The following examples assume that the SP automounter function is configured and the following defaults are specified:

spsitenv command or SMIT panel
HOMEDIR_SERVER="svr1"
HOMEDIR_PATH="/home/filesvr1"
spmkuser.default file
In the user stanza:

group=staff
groups=staff
prog=/bin/ksh

Note
The following examples assume that the SP automounter function is configured and the following defaults are specified: spsitenv command or SMIT panel HOMEDIR_SERVER="svr1" HOMEDIR_PATH="/home/filesvr1" spmkuser.default file In the `user` stanza: group=staff groups=staff prog=/bin/ksh

To create a user account for baker using the defaults specified in the spmkuser.default file and the home directory specified in the SMIT site environment panel or spsitenv command:
```
spmkuser baker
```
To create a user account for charlie with a UID of 1234, a home directory of /u/charlie that is physically located at /home/charlie on hostx, the staff primary group and the dev , the test secondary groups, and the /bin/ksh default shell:
```
spmkuser id=1234 groups=dev,test home=hostx:/home/charlie
 
```

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]