pSeries 690 Hardware Management Console
|(HMC).
|
|
Purpose
spgetdesc - Obtains the description information from the nodes specified and, optionally, enters it into the SDR.
Syntax
Flags
"node_number:hostname:description"
for all nodes that successfully obtained the description information.
One of the following flags must be specified:
Operands
None.
Description
This command will obtain the description information from the nodes specified and, optionally, update the description attribute in the SDR Node class. Unless the -f flag is specified, the node's host_responds will be checked before it will attempt to dsh to the nodes and obtain their description information. This command requires that the user be authenticated to Kerberos using the k4init command. This command is primarily intended as a migration tool for obtaining description information from existing nodes. The description information will be obtained from new nodes when they are installed or customized.
|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 spgetdesc using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Output
The model information that is obtained will be printed to standard output as well as placed in the SDR.
Standard Error
This command writes error messages (as necessary) to standard error. Errors will be printed if any attempt to get the description information on a node is unsuccessful.
If the command does not run successfully it terminates with an error message and a nonzero return code. Messages will inform the user of the cause of the error. For a terminal error, no description information will be obtained. For a nonterminal error, no description information will be obtained for the node that had the error.
Exit Values
Security
You must have root privilege and write access to the SDR to run this command.
|You must have access to the AIX remote commands or the secure remote |commands 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/spgetdesc
Related Information
PSSP commands: dsh, k4init, SDRChangeAttrValues, SDRGetObjects
|AIX commands: rsh, uname
Examples
spgetdesc -a
spgetdesc -ul 3,4
spgetdesc -ac
Purpose
spgrpname - Displays the DCE group name for an SP Security Services group.
Syntax
Flags
Operands
Description
The spgrpname command displays the actual DCE group name that corresponds to the specified default-group-name, that is predefined in the security services configuration files.
Standard Output
Output consists of one line containing the DCE group name, when successful.
Standard Error
Output consists of error messages, when the command cannot complete successfully.
There are no unique consequences of command errors.
Exit Values
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP) (file set ssp.clients).
Prerequisite Information
The chapters on security in PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/spgrpname
Examples
spgrpname sysctl-master root/sysctl
spgrpname hm-admin hm-admin
Purpose
sphardware - Directly launches the Hardware Perspective graphical user interface (GUI).
Syntax
Flags
Operands
None.
Description
Use this command to launch the Hardware Perspective. From the Hardware Perspective, the user can monitor and manipulate objects within the SP system. The SP objects included in this Perspective are the control workstation, SP system and system partitions, nodes, dependent nodes, SP expansion I/O units, node groups, and frames and switches.
By default, the Hardware Perspective will display the CWS, System and Syspars pane and the Nodes pane. The CWS, System and Syspars pane contains all system partitions and indicates the current system partition. The Node pane contains all the nodes, dependent nodes and SP expansion I/O units in the current system partition.
The Node Groups and Frame and Switches panes can be added to the Hardware Perspective by using the Add Pane tool bar icon. Panes can be deleted from the window by using the Delete Pane tool bar icon.
When the command is invoked, preferences which define the look and layout of the sphardware window are prioritized in the following order:
Files
The Users Preferences are read from and saved to $HOME/.sphardware(User Profile Name).
The System Preferences are read from and saved to /usr/lpp/ssp/perspectives/profiles/$LANG/.sphardware(System Profile name).
The sphardware application resource file: /usr/lpp/ssp/perspectives/app-defaults/$LANG/Sphardware
|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 sphardware using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
Any user can run the sphardware command, although many actions in the Hardware Perspective require specific access to SP subsystems. The access depends on the type of security mechanism your SP system is using.
See the chapter on security in PSSP: Administration Guide for more information.
The following access is required to have complete use of the Hardware perspective:
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Prerequisite Information
For information on using the Hardware Perspective, see the online help and the "Using SP Perspectives" chapter in the PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/sphardware
Related Information
|The Hardware Perspective can also be accessed by using the SP |Perspectives Launch Pad. The perspectives command invokes |the Launch Pad. Other Perspectives windows can be launched by invoking |the following commands: spevent, spsyspar, and |spvsd.
Examples
sphardware
sphardware -foregroundColor chartreuse
sphardware &
Purpose
sphostnam - Enters host name configuration data for a node or series of nodes in the System Data Repository (SDR).
Syntax
Flags
Operands
Description
Execute this command during SP installation to specify which adapter type will determine the initial host name for your nodes. You can also use this command to indicate whether you want the long (fully qualified) or short form of a host name to be used.
You can use the System Management Interface Tool (SMIT) to run the sphostnam command. To use SMIT, enter:
smit node_data
and select the Hostname Information option.
Notes:
Security
You must have root privilege and write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/sphostnam
Examples
The following example selects the css0 adapter for the host name for a system with two frames and 32 nodes. The long form of the host name is to be used.
sphostnam -a css0 1 1 32
Purpose
sphrdwrad - Obtains hardware Ethernet addresses for SP nodes so they can be written to the System Data Repository.
Syntax
Flags
Operands
Description
Execute this command only at installation or when adding new frames or nodes. The spframe command must be run before this command so that frame information is already in the System Data Repository.
If you know your hardware Ethernet addresses, you can speed this process by putting the addresses in /etc/bootptab.info, as follows:
17 02608C2E48D9 19 02608C2D6712 21 02608C2E49A4 23 02608C2E48E2
If you do not know your hardware Ethernet addresses, use the sphrdwrad command to find them.
You can use the System Management Interface Tool (SMIT) to run the sphrdwrad command. To use SMIT, enter:
smit enter_data
and select the Get Hardware Ethernet Addresses option.
Notes:
Security
You must have root privilege and write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/sphrdwrad
Examples
To obtain Ethernet addresses for a new frame containing 8 nodes (4 wide nodes and 4 thin nodes), enter:
sphrdwrad 2 1 8
You should receive output similar to the following:
|Acquiring hardware Ethernet address for node 17 |Acquiring hardware Ethernet address for node 19 |Acquiring hardware Ethernet address for node 21 |Acquiring hardware Ethernet address for node 23 |Acquiring hardware Ethernet address for node 25 |Acquiring hardware Ethernet address for node 26 |Acquiring hardware Ethernet address for node 27 |Acquiring hardware Ethernet address for node 28 |Hardware ethernet address for node 17 is 02608C2D481C |Ping to default_route successful for node 17 |Hardware ethernet address for node 19 is 02608C2D78DF |Ping to default_route successful for node 19 |Hardware ethernet address for node 21 is 02608C2D93B3 |Ping to default_route successful for node 21 |Hardware ethernet address for node 23 is 02608C2D8C3C |Ping to default_route successful for node 23 |Hardware ethernet address for node 25 is 10005AFA22B9 |Ping to default_route successful for node 25 |Hardware ethernet address for node 26 is 10005AFA230A |Ping to default_route successful for node 26 |Hardware ethernet address for node 27 is 10005AFA2229 |Ping to default_route successful for node 27 |Hardware ethernet address for node 28 is 10005AFA2210 |Ping to default_route successful for node 28
|Purpose
|sphmcid - Stores the user ID and password required by
|the Hardware Monitor (hardmon) to establish a remote client session
|with the IBM pSeries 690 Hardware Management Console
|(HMC).
|
|
|Syntax
|sphmcid [-h] | |[host_name | ip_address |[user_id]]
|Flags
|
|Operands
|
|Description
|Use this command to store the user ID and password for the Hardware Monitor |to use when establishing a remote client session with an |HMC. The HMC is identified by its IP address or by its host name which will be |resolved to its IP address before storing. When running this command, |you will be prompted for the password to be stored with the specified user |ID. If the |sphmcid command is run with no user ID, it will return the user ID for the |specified IP address if one has been stored. If the command is run with |no IP address, it will return all IP addresses and user IDs that were |previously saved. To change an existing saved user ID or password |value, rerun the command with new values.
|Standard Input
|You must enter the password through standard input when prompted. |The password will not be displayed as you type it.
|Standard Output
|If the |sphmcid command is run with no user ID, the command will return the user ID |for the specified IP address to standard output.
|If the |sphmcid command is run with no operands, the command will return all stored |IP addresses and user IDs to standard output.
|Standard Error
|This command writes all error messages to standard error.
|Exit Values
|
|Security
|You must have root privilege to run this command.
|Restrictions
|The |sphmcid command may only be run on the control workstation.
|Implementation Specifics
|This command is part of the IBM Parallel System Support Programs (PSSP) |Licensed Program (LP) (file set ssp.basic).
|Location
|/usr/lpp/ssp/bin/sphmcid
|Examples
|
|sphmcid 9.10.11.12 hmc_admin
|You will be prompted to enter a password:
|Password:
|sphmcid 9.10.11.12
|You will be returned the stored user ID:
|9.10.11.12 hmc_admin
|
Purpose
spled - Displays SP node LCD or LED information in a graphical user interface.
Syntax
spled [-G] [-n title] [-p] [-r pollrate] [-b background color] [-l] [-h]
Flags
Operands
None.
Description
The spled command is an X Windows based application that displays the three digit seven segment light emitting diode (LED) or the two line by 16 character liquid crystal display (LCD) information found on the front of an SP node |or SP-attached server.
The spled application contains a menubar at the top of the window which contains one button, "Window." This button has one menu item which by default is labeled "Exit." Selecting this button will close the spled application.
Below the menubar is an area which by default contains a graphical representation of the frames and the SP nodes in those frames for the current system partition. If the -G flag is specified, all of the SP nodes |and SP-attached servers in the system will be shown in their respective frames.
The size of each node is represented by the number of slots it uses in the frame. A thin node occupies one slot; a wide node occupies two slots; and a high node occupies four slots.
Pressing mouse button one inside a frame will display the slot number of each node in that frame. Pressing mouse button two inside a frame will display the node number of each node in that frame.
For nodes that have an LCD:
Thin and wide nodes that contain an LCD may display "..." after some characters in the LCD. This indicates there is more LCD data available than can be shown. Pressing mouse button three in a frame containing nodes with an LCD displaying "..." will open a window displaying all of the LCD information available for those nodes.
Notes:
pSeries 690 configurations in logical
|partition (LPAR) mode, unique LCD values will be displayed specifically for
|the frame below the frame label, as well as node LCD values for each LPAR in
|the p690. For p690 configurations in SMP mode, LCD values will be
|displayed for the node.
Files
The spled application resource file: /usr/lpp/ssp/perspectives/app-defaults/$LANG/Spled.
Security
You must have Hardware Monitor "monitor" access to display the spled application.
Location
/usr/lpp/ssp/bin/spled
Examples
spled -n "My System"
spled -G
Purpose
splm - Views, gathers, archives, or collects log and system data.
Syntax
Flags
The splm command requires the -a flag and an argument to select a function to execute. It also requires a log table that contains records specifying target nodes and files or commands.
Operands
None.
Description
Use this command to execute a number of log management functions on a single host or a set of hosts in parallel. The splm functions are driven by a log table file that contains the target node designations and associated files, and the commands to execute. The table format follows:
# Comment line target nodes: file or command
The target node portion of a table stanza is a comma-delimited list with no blanks. The values in the list are interpreted as:
The -n flag ignores the target node portion of the table and only executes on the local node. The file or command portion of the stanza specifies either a command to execute that displays information to standard output, or a file that will be archived, collected, or viewed. File specification can take advantage of Tcl file globbing (similar to csh file globbing). If the file or command portion of the stanza refers to a command to be executed, it must be followed by a redirection and a path or file name. The information generated by the command will be redirected to the path or file name under the -d top level directory. Use > or >> following the command to redirect the output. The view option ignores the file or command destinations and displays the file's contents or command output to the executing node.
!,/tmp/nodelist,k47n10: /bin/errpt -a > errpt.output
k47n10,k47n15: /etc/filesystems etc/filesystems
This copies the file to the /etc subdirectory under the -d top level directory.
splm Functions
Archive: The archive function copies files and redirects command output as specified in the input table to the top level directory on each node. The -c flag then creates a compressed tar file of the data named /topdirectory/ node_name.tar.Z. The -r flag removes an archive by removing all files starting from the top level directory down.
Check: The check function can be used to check a table for errors.
Gather: The gather function moves archive or service tar files to a central location on the executing node. The -r option removes the archive or service collection on each remote node only after the tar file was successfully copied to the central location. If the node.tar.Z file is not found, the gather function will attempt to create one. Gathered tar files can be mailed or copied to a tape or disk device using the -o flag. If mailed, the files are first uuencoded. The -l flag specifies the file system on the local node where the tar files are to be gathered. The -l flag must be specified if the -s stagger flag is not used. The gather function makes two passes, if necessary. On the first pass, it allows each node to take up an equal amount of the central file system. If any nodes encounter errors, the gather function retries those nodes, one at a time, until the file system is full or all the nodes are copied. If gather is unsuccessful on any node, but a node .tar.Z file exists for that node in the central location, it is moved to node.tar.Z.old, and not sent to the output location. The -s stagger flag forces the fanout to 1, gathers the tar files one at a time, attempts to send the tar to the output location, then removes it from the local node. The -r flag cannot be used with -s. The default central location directory for stagger is /tmp.
Service: The service function first calls the AIX snap command to gather system data to the top level directory if the -p flag is used. The snap command creates a set of subdirectories based on the -p arguments. The additional data defined in the table data is then collected under the "other" subdirectory created by snap. If the -p flag is not used, the data will still be collected under the "other" subdirectory. If the -c flag is used, splm uses the snap -c command to create the tar.Z file. The -r flag can be used to remove service collections. splm calls snap -r which removes the tar file and all files under each snap subdirectory.
View: The view function displays the output of the command or contents of file entries in the input table to the local host.
Files
Security
The splm command consists of a client script and a server procedure which is executed by the Sysctl facility. Sysctl performs access authorization according to the configuration of security services on the server nodes.
To invoke the splm view function, the caller must be an authenticated user. The Sysctl AUTH callback is used to grant access. The splm server switches IDs from root to the authenticated user ID before executing the view function on the target node or nodes.
The archive, gather and service functions additionally require that the caller have a principal entry in the log management ACL: /etc/logmgt.acl. These functions use the Sysctl aclcheck procedure for granting access, and the splm server will execute as root on the target node or nodes. The principal needs to have logged in to the appropriate authentication service before running this command.
Restrictions
The command always generates output in English using the default C locale. It ignores the current operating locale.
Location
/usr/lpp/ssp/bin/splm
Related Information
AIX commands: compress snap, tar, uuencode
The PSSP: Administration Guide
Examples
splm -a archive -c -d /var/adm/archives -t /etc/tables/archive.tab
splm -a service -c -t /spdata/sys1/logtables/amd.tab -p g
splm -a gather -k service -t /spdata/sys1/logtables/amd.tab \
-l /tmp/amdproblem -o /dev/rmt0 -r
Purpose
splogd - Reports error logging, writes state changes, and calls user exits.
Syntax
splogd [-d] [-b] [-f file_name]
Flags
Operands
None.
Description
The SP logging daemon has the following functions:
The hwevents file contains state change actions that are to be performed by the splogd logging daemon. The fields are:
There are two special keywords for function. If function is SP_ERROR_LOG, error logging is performed provided that syslog is set up and AIX error logging is set up to perform SP logging. Refer to the setup_logd command for details.
If function is SP_STATE_LOG, these state changes that meet the statement's criteria are logged to /var/adm/SPlogs/spmon/splogd.state_changes.timestamp.
kill -HUP {splogd pid}
User Exit Arguments
When a user exit is called by splogd, the following arguments are passed:
Starting and stopping the splogd daemon
The splogd daemon is under System Resource Controller (SRC) control. It uses the signal method of communication in SRC. The splogd daemon is a single subsystem and not associated with any SRC group. The subsystem name is splogd. To start the splogd daemon, use the startsrc -s splogd command. This starts the daemon with the default arguments and SRC options. The splogd daemon is setup to be respawnable and be the only instance of the splogd daemon running on a particular node or control workstation. Do not start the splogd daemon from the command line without using the startsrc command to start it.
To stop the splogd daemon, use the stopsrc -s splogd command. This stops the daemon and does not allow it to respawn.
To display the status of the splogd daemon, use the lssrc -s splogd command.
If the default startup arguments need to be changed, use the chssys command to change the startup arguments or the SRC options. Refer to AIX Commands Reference and AIX General Programming Concepts: Writing and Debugging Programs for more information about daemons under SRC control and how to modify daemon arguments when under SRC.
To view the current SRC options and daemon arguments, use the odmget -q 'subsysname=splogd' SRCsubsys command.
Files
Location
/usr/lpp/ssp/bin/splogd
Related Information
Commands: setup_logd
The "System Monitor Variables, Display Types, and Attributes Appendix" in PSSP: Administration Guide
Examples
startsrc -s splogd
stopsrc -s splogd
lssrc -s splogd
lssrc -a
odmget -q 'subsysname=splogd' SRCsubsys
Purpose
splst_syspars - Returns the list of defined system partitions.
Syntax
splst_syspars [-n]
Flags
Operands
None.
Description
This command returns the list of the system partitions. The system partition names are in dotted decimal format unless -n is specified.
Location
/usr/lpp/ssp/bin/splst_syspars
Examples
splst_syspars
You should receive output similar to the following:
129.40.127.122 129.40.127.47
splst_syspars -n
You should receive output similar to the following:
k47sp1 k47s
Purpose
splst_versions - Returns information about the PSSP code version installed on nodes in the SP system.
Syntax
splst_versions [-G] [-l] [-e] [-n node_num] [-N node_group] [-t] [-h]
Flags
Operands
None.
Description
Use this command to return a list of PSSP code versions that are installed on the nodes in the current system partition. The PSSP version and release numbers, and modification level are included in the output. The fix level is not returned in the output. Node number 0 (zero) is considered the control workstation and is not evaluated as part of any system partition. The output is sorted in ascending order by version.
If the -t flag is omitted, there will be only one record for each version present. If the -t flag is used, there will be a record for each node.
Location
/usr/lpp/ssp/bin/splst_versions
Examples
prompt> splst_versions PSSP-2.4 PSSP-3.1
prompt> splst_versions -t 1 PSSP-2.4 5 PSSP-2.4 6 PSSP-2.4 9 PSSP-3.1
prompt> splst_versions -l -e PSSP-2.4 /* this case has mixed partitions */ PSSP-3.1
The following will be the output if only PSSP-2.4 exists in the system partition:
prompt> splst_versions -l -e PSSP-2.4 /* this case has only 2.4 in partition */
Purpose
splstadapters - Use this command to list information about adapters to standard output.
Syntax
Flags
If the -t flag is not specified, the default is to consider adapters relating to both standard and dependent nodes for output.
Operands
Description
Use this command to get configuration information about any adapter from the SDR. For a complete list of adapter attributes, see the Adapter and DependentAdapter classes in "The System Data Repository" appendix in PSSP: Administration Guide.
Not all of the attributes are applicable to each type of adapter.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit list_extadapters
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 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
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/splstadapters
Examples
splstadapters
You should receive output similar to the following:
node_number adapter_type 1 en0 1 css0 5 en0 5 css0
splstadapters -t standard -s node_number node_number netmask
You should receive output similar to the following:
1 255.255.255.192 3 255.255.255.192
splstadapters -G adapter_type==css0
You should receive output similar to the following:
node_number adapter_type 1 css0 5 css0 7 css0 9 css0 19 css0 23 css0