IBM Books

Command and Technical Reference, Volume 2

spgetdesc

Purpose

spgetdesc - Obtains the description information from the nodes specified and, optionally, enters it into the SDR.

Syntax

spgetdesc
[-h] [ -u] [-c] [-f] {-a | -l node_list}

Flags

-h
Displays help information for this command (syntax message). If the command is issued with the -h flag then the syntax description is displayed to standard output and no other action is taken (even if other valid flags are entered along with the -h flag).

-u
Updates the description attribute in the SDR with the description information found.

-c
Outputs the description information in a colon delimited format. The output will be of the form:
"node_number:hostname:description"

for all nodes that successfully obtained the description information.

-f
Forces the command to obtain description information from the specified nodes regardless of the host responds value.

One of the following flags must be specified:

-a
Obtains description information from all nodes found in the SDR.

-l node_list
Indicates by node_list the SP nodes to obtain the description information from. The node_list is a comma-separated list of node numbers.

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

0
Successful completion

1
A nonterminal error occurred for 1 or more nodes. Processing continued for any remaining nodes.

2
A terminal error occurred and all processing was stopped.

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

  1. To obtain description information for all existing nodes enter:
    spgetdesc -a
    
  2. To obtain description information for nodes 3 & 4 and update the SDR, enter:
    spgetdesc -ul 3,4
    
  3. To obtain description information from all nodes in a colon delimited format, enter:
    spgetdesc -ac
    

spgrpname

Purpose

spgrpname - Displays the DCE group name for an SP Security Services group.

Syntax

spgrpname
{-h | default-group-name}

Flags

-h
Specifies that the command syntax is to be listed. If you specify this flag, any operand is ignored.

Operands

default-group-name
The predefined name of a service listed in the security services configuration file.

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

0
Indicates successful completion of the command.

1
Indicates that an error occurred.

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

  1. Displaying the DCE group name corresponding to the predefined default name sysctl-master, which the administrator has overridden:
    spgrpname sysctl-master
    root/sysctl
    
  2. Displaying the DCE group name corresponding to the predefined default name hm-admin, which the administrator has not overridden:
    spgrpname hm-admin
    hm-admin
    

sphardware

Purpose

sphardware - Directly launches the Hardware Perspective graphical user interface (GUI).

Syntax

sphardware
[-userProfile name] [-systemProfile name] [ -noProfile]
 
[-backgroundColor colorName]
 
[-foregroundColor colorName] [-fontFamily name]
 
[-fontSize size] [-fontBold] [-fontItalic] [-nosplash] [-h]

Flags

-userProfile name
Upon initialization, loads the specified user profile. If a user profile named "Profile" exists in the user's home directory, it will be loaded by default if the -userProfile flag is not specified.

-systemProfile name
Upon initialization, loads the specified system profile instead of the default system profile. The default system profile is named "Profile."

-noProfile
Upon initialization, does not read either profile.

-backgroundColor colorName
Overrides the background color specified by any profile or default with the specified color. Refer to Appendix A, "Perspectives Colors and Fonts" in PSSP: Command and Technical Reference for a list of valid color names.

-foregroundColor colorName
Overrides the foreground color specified by any profile or default with the specified color. Refer to Appendix A, "Perspectives Colors and Fonts" in PSSP: Command and Technical Reference for a list of valid color names.

-fontFamily name
Overrides any font family with the specified font. The list of valid family names is dependent on the X server. Refer to Appendix A, "Perspectives Colors and Fonts" in PSSP: Command and Technical Reference for a list of valid fonts.

-fontSize size
Overrides any font point size with the specified size. Valid values are 6-30 points.

-fontBold
Sets the font to bold.

-fontItalic
Sets the font to italics.

-nosplash
Does not display the splash screen before the Perspectives main window is displayed.

-h
Displays usage information on the options available for the command.
Note:
Most flags accepted by X will also be recognized. For example, -display displayname.

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:

SDR write
To create, modify, and delete node groups.

Hardware Monitor "VFOP"
To power on, power off and reset hardware objects (node, frames and switches).

Hardmon Monitor serial
To network boot nodes and open a tty window to a node.

Hardmon Monitor monitor
To display node LCD and LED.

Event Management
To monitor objects in a pane and display dynamic attributes in object notebooks. |

|PSSP cshutdown and cstartup commands access
|To shutdown or start up nodes using the cshutdown or |cstartup commands.

CWS root commands
To fence or unfence nodes and to Estart the switch. |

|Remote commands
|You must have access to the AIX remote commands or the secure remote |commands to run commands on nodes.

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

  1. To invoke the sphardware window, enter:
    sphardware
    
  2. To force sphardware to display text in chartreuse, regardless of what is set in the preference files, enter:
    sphardware -foregroundColor chartreuse
    
  3. To start the sphardware window in the background, enter:
    sphardware &
    

sphostnam

Purpose

sphostnam - Enters host name configuration data for a node or series of nodes in the System Data Repository (SDR).

Syntax

|
|sphostnam
|[-a adapter_name | -P |physical_location_code] ...
 
[-f {long | short}] {start_frame start_slot
 
{node_count | rest} | -N node_group | -l node_list}

Flags

|-a adapter_name
|Specifies the name of the adapter. Valid adapter names are: |enn (Ethernet), fin (FDDI), |trn (token ring), and cssn (switch), where |n is the logical device number assigned to the adapter by AIX. |You cannot specify an adapter type (an adapter name without the logical device |number, such as en, fi, ti, or |css). If neither -a nor -P are |specified, the command will default to using the SP Ethernet administrative |local area network (LAN) adapter for the node. |

|-P physical_location_code
|Indicates the physical location of the adapter to be used to derive the |host name for the specified nodes. This flag cannot be specified with |the -a flag. If neither -a nor |-P are specified, the command will default to using the SP |Ethernet administrative LAN adapter for the node.

-f
Specifies which form of the host name is to be used. Specify long if you want the host name to be the fully qualified host name and short if you want to use the short form of the host name. If -f is not specified, the default is long.

-N node_group
Specifies a node group to be used for this operation. This node group must be bound to the current system partition.

-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.)

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

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:

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

  2. Any changes made will not take effect on the nodes until they are customized.

  3. |This command uses all of the characters before the first period as |the short host name for the initial_hostname of a node. For example, if |the long host name of a node is |"c60n10.ppd.pok.ibm.com", "c60n10" is the short |host name for that node.

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

sphrdwrad

Purpose

sphrdwrad - Obtains hardware Ethernet addresses for SP nodes so they can be written to the System Data Repository.

Syntax

sphrdwrad
{start_frame start_slot {node_count | rest} |
 
-N node_group | -l node_list}

Flags

|-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 the lowercase l, as in |list.

-N node_group
Specifies a node group to be used for this operation. This node group must be bound to the current system partition.

rest
Indicates that, beginning with the node determined by start_frame and start_slot, all the rest of the nodes should be used for this operation.

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 in the next sequential frame. Specify a value between 1 and |512 inclusive.
|Note:
The node_count is considered to be within the current system |partition. |

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:

Create a file named /etc/bootptab.info (if it does not already exist), listing your SP nodes by node number (or frame, slot) followed by a blank and the hardware Ethernet address. The first token represents the node and the second token represents the hardware address. The file should look similar to this:
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:

  1. The nodes should be physically powered on (but logically powered off) when you run this command.

  2. The LEDs change values while this command is running.

  3. You should not have a tty open to any of the nodes to be used for this command.

  4. If the addresses are not found in /etc/bootptab.info, the sphrdwrad command takes a few minutes to run, and the addresses are obtained from the nodes in parallel.

  5. Any nodes specified will be powered off to acquire the Ethernet addresses. The nodes remain in the powered off state, even after the addresses are received.

  6. If you are adding a node, only the new node needs to be specified because any selected nodes will be powered off.

  7. To avoid possible file system damage, you should always shut down a node cleanly before powering it off. You can do this by using the cshutdown command or by using the SHUTDOWN/POWER OFF option in the System Monitor Graphical User Interface.

  8. |A ping test will be performed from the Ethernet adapter to the |node's boot/install server if the hardware addresses are obtained from |the nodes. The ping test is performed on Common Hardware Reference |Platform (CHRP) nodes only. If the hardware addresses are obtained from |/etc/bootptab.info, no ping test is performed. The |results will be displayed to standard output.

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

  10. If you are using a bootptab.info file, you must only place nodes in the current partition in the file. If you have multiple partitions, you must update the bootptab.info file and run sphrdwrad for each partition.

Security

You must have root privilege and write access to the SDR to run this command.

Note:
If there is no hardware addressess file, then you must also have hardmon monitor, VFOP, and serial access 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

|sphmcid

|Purpose

|sphmcid - Stores the user ID and password required by |the Hardware Monitor (hardmon) to establish a remote client session |with the IBM e(logo)server pSeries 690 Hardware Management Console |(HMC). | |

|Syntax

|sphmcid [-h] | |[host_name | ip_address |[user_id]]

|Flags

|

|-h
|Displays usage information. |

|Operands

|

|host_name
|Specifies the host name of the HMC.

|ip_address
|Specifies the IP address of the HMC.

|userid
|Specifies the user ID that hardmon will use to establish a remote |client session with the HMC.

|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

|

|0
|Indicates the successful completion of the command.

|1
|Indicates that no user ID information exists for the specified IP |address.

|2
|Indicates that the command could not store the user ID and |password. |

|3
|Indicates that the host name and IP address input could not be |resolved. |

|4
|Indicates that the file access permission was altered. |

|5
|Indicates a syntax error. |

|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

|

  1. |To store the user ID and password for an HMC, enter:
    |sphmcid 9.10.11.12 hmc_admin

    |You will be prompted to enter a password:

    |Password:
  2. |To query the user ID stored for an HMC, enter:
    |sphmcid 9.10.11.12

    |You will be returned the stored user ID:

    |9.10.11.12   hmc_admin
    |

spled

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

|-G
|Displays LED or LCD information for SP nodes and SP-attached servers in |all system partitions.

-n title
Sets the window title.

-p
Output the process ID to standard output.

-r pollrate
Sets the time increment to poll for LCD or LED updates. The default is to poll every 5 seconds. IBM suggests that you not change this value.

-b background color
Sets the background color.

-l
Changes the "Window" menu bar item labeled "Exit" to "Close."

-h
Displays usage information on the options available for the command.

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:

  1. A node in the process of having the microcode on its supervisor card updated will not be displayed in the window.

  2. |For IBM e(logo)server 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

  1. To start spled and set the window title to "My System" enter:
    spled -n "My System"
    
  2. To start spled and display all of the nodes in a multiple partition system, enter:
    spled -G
    

splm

Purpose

splm - Views, gathers, archives, or collects log and system data.

Syntax

splm
[-a archive] [-cny] [-d dir] [-f fanout] [-h] [-t table]

splm
[-a archive] [-d dir] [-f fanout] [-h] [-n] [-r] [-t table] [-y]

splm
[-a check] [-h] [-n] [-t table]

 

splm
[-a gather] [-d dir] [-f fanout] [-h] [-k type] [-l cfs]
 
[-o loc] [-r] [-s] [-t table] [-y]

splm
[-a service] [-cny] [-d dir] [-f fanout] [-h] [-p ipts ] [-t table]

splm
[-a service] [-d dir] [-f fanout] [ -h] [-n] [-r] [-t table] [-y]

splm
[-a view] [-h] [-n] [-t table]

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.

-a action
Specifies the function to perform: archive, check, gather, service, or view.

-c
Creates a compressed tar file. For the archive function, this will be a tar starting the -d dir flag. For service collections, /usr/sbin/snap -c -d dir will be called to create the tar file. The tar file will be named node.tar.Z.

-d dir
Specifies the path where the archive or service collection will be stored on each node. The archive default is /var/adm/archives. The service default is /tmp.

-f fanout
Sets the maximum fanout value which determines how many nodes will execute in parallel. The default is 32. Any number between 1-32 can be used.

-h
Displays usage information.

-k type
For the gather function only, this flag indicates whether a service collection or archive is being collected.

-l cfs
Specifies the path on the local node where the archive or service collections should be gathered.

-n
Ignores the node designation in the input table and executes all entries on the local node only.

-o loc
Specifies the device or mail location where to direct tar files.

-p opts
Accepts a string of characters representing option parameters for calling snap collection. Each character relates to a category of system data to be collected. Valid characters are: a, A, D, f, g, G, k, l, n, p, s, S, t.

-r
Removes archive or service on each node. Exclusive with -s flag.

-s
Staggers collection to a mail location or device.

-t
Specifies the input table of nodes and commands.

-y
Appends the yymmdd timestamp subdirectory to the per node directory.

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:

  1. If the value begins with a slash (/), it is a file containing a list of node names, one per line.
  2. If the value is an exclamation point (!), it refers to the local host.
  3. Any string not matching 1 or 2, is interpreted as a node name.

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.

  1. To specify the local node, nodes listed in the /tmp/nodelist file and node k47n10, and archive or collect errpt output from those nodes to the errpt.output file under the top level directory, enter:
    !,/tmp/nodelist,k47n10:  /bin/errpt -a > errpt.output
    
  2. To archive or collect /etc/filesystems file to a subdirectory on nodes k47n10 and k47n15, enter:
    k47n10,k47n15: /etc/filesystems  etc/filesystems
    

    This copies the file to the /etc subdirectory under the -d top level directory.

    Note:
    The -d top level directory is always appended with a subdirectory named arch_table_name for archives, or srvc_table_name for service collections.

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

/etc/splm.allow
Restricts table commands that can be executed.

/etc/logmgt.acl
Acl file for archive, gather, and service functions.

/spdata/sys1/logtables/*
Contains sample tables for service collections.

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

  1. To create an archive based on the entries in the /etc/tables/logs.tab table and to create a compressed tar file and have the archive under directory /var/adm/archives/arch_logs.tab, enter:
    splm -a archive -c -d /var/adm/archives -t /etc/tables/archive.tab
    
  2. To create a service collection of entries in the /spdata/sys1/logtables/amd.tab table and have snap include general system information, enter:
    splm -a service -c -t /spdata/sys1/logtables/amd.tab -p g
    
  3. To gather the service collections in Example 2, remove the collection on each node, and copy the gathered data to tape device rmt0, enter:
    splm -a gather -k service -t /spdata/sys1/logtables/amd.tab \
              -l /tmp/amdproblem -o /dev/rmt0 -r
    

splogd daemon

Purpose

splogd - Reports error logging, writes state changes, and calls user exits.

Syntax

splogd [-d] [-b] [-f file_name]

Flags

-d
Turns debugging on.

-b
Starts the daemon in the background from the command line.

-f file_name
Names an input file to use to define what logging is to be done and what user exits should be called. The default file is /spdata/sys1/spmon/hwevents.

Operands

None.

Description

The SP logging daemon has the following functions:

error logging
Reports SP hardware errors to both the syslog and the AIX error log.

state change logging
Writes SP hardware state changes to a file.

user exits
Calls a user exit when a state change occurs.

The hwevents file contains state change actions that are to be performed by the splogd logging daemon. The fields are:

frame
Specifies a frame number (1-n) or * for all frames.

slot
Specifies the following:

variable
Specifies a hardware variable (for example, nodePower, temp, LED7SegA).

operator
Specifies how to compare the value. Acceptable values are: =, <, >, and !=.

value
Specifies the value of the variable to match with the operator wildcard (*), or a partial match with the wildcard at the end (23*).

time
Specifies if the function should be called at startup, when the state changes, or both times. Valid options are startup, change, or both.

function
Specifies the program to call when an event occurs.

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.

Note:
To close the current state_changes.timestamp and open a new one, send a SIGHUP signal to splogd. For example,
kill -HUP {splogd pid}

User Exit Arguments

When a user exit is called by splogd, the following arguments are passed:

  1. A c or s depending on whether this call is for a change of state or to provide the startup values for the variables being monitored.
  2. For each variable being reported, the following arguments are passed:
    1. Frame number.
    2. Node number.
    3. Variable name. Refer to the "System Monitor Variables, Display Types, and Attributes Appendix" of PSSP: Administration Guide for a list of variables.
    4. Value of the variables. Boolean variables are expressed as TRUE or FALSE, integers as decimal strings, and floating-point values as floating-point strings.

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

/spdata/sys1/spmon/hwevents
File that describes what logging is performed and what user exits are called.

/var/adm/SPlogs/spmon/splogd.state_changes.timestamp
File where state changes are recorded.

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

  1. To start the splogd daemon, enter:
    startsrc -s splogd
    
  2. To stop the splogd daemon, enter:
    stopsrc -s splogd
    
  3. To display the status of the splogd daemon, enter:
    lssrc -s splogd
    
  4. To display the status of all the daemons under SRC control, enter:
    lssrc -a
    
  5. To display the current SRC options and daemon arguments for the splogd daemon, enter:
    odmget -q 'subsysname=splogd' SRCsubsys
    

splst_syspars

Purpose

splst_syspars - Returns the list of defined system partitions.

Syntax

splst_syspars [-n]

Flags

-n
Returns a list of host names instead of addresses.

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

  1. To display the IP addresses associated with all the defined system partitions on the SP, enter:
    splst_syspars
    

    You should receive output similar to the following:

    129.40.127.122
    129.40.127.47
    
  2. To display the names of all the defined system partitions on the SP, enter:
    splst_syspars -n
    

    You should receive output similar to the following:

    k47sp1
    k47s
    

splst_versions

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

-G
Causes the command to look at all system partitions rather than just the current system partition (but not the control workstation).

-l
Returns the latest PSSP version for the nodes that are the target of the command.

-e
Returns the earliest PSSP version for the nodes that are the target of the command.

-n node_num
Returns the PSSP code version for node_num. Use node_num 0 to specify the control workstation.

-N node_group
Returns a list of PSSP versions for node_group. If -G is supplied, a global node group is used. Otherwise, a partitioned-bound node group is used.

-t
Returns the node number and PSSP version in two columns.

-h
Displays usage information.

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

  1. To list each PSSP version represented in the current system partition, enter:
    prompt> splst_versions
     
    PSSP-2.4
    PSSP-3.1
    
  2. To list each node in the system partition and its PSSP code version, enter:
    prompt> splst_versions -t
     
    1 PSSP-2.4
    5 PSSP-2.4
    6 PSSP-2.4
    9 PSSP-3.1
    
  3. To list the earliest and latest PSSP code versions in a system partition, enter:
    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 */
    

splstadapters

Purpose

splstadapters - Use this command to list information about adapters to standard output.

Syntax

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

Flags

-h
Displays usage information.

-G
Removes system partition boundaries for this invocation. This flag 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 attribute attr.

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

standard
Indicates that only adapters relating to SP nodes (nodes in a frame/slot) will be considered for output.

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

dependent
Indicates that only adapters on dependent nodes will be considered for output.

Operands

attr==value
Specifies certain adapter objects to be returned. The attr token must be a valid attribute of one of the adapter classes in the System Data Repository (SDR) (Adapter or DependentAdapter). If attr exists in both adapter classes, 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
Specifies the attributes to be returned as output of the command. It does not limit the adapter objects that are considered for output. If an attr argument is not specified, the node_number and adapter_type attributes are returned.

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

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/splstadapters

Examples

  1. To list the node_number and adapter_type attributes for all adapter objects in the current system partition, enter:
    splstadapters
    

    You should receive output similar to the following:

    node_number adapter_type
    1 en0
    1 css0
    5 en0
    5 css0
    

  2. To list the netmask attribute of SP adapters along with their node numbers and have the output sorted by node number, enter:
    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
    
  3. To list the "css0" adapters in the system, regardless of system partition, enter:
    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
    


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