Command and Technical Reference, Volume 2

spdisplay_config

Purpose

spdisplay_config - Displays system partition configuration information which can be used to partition an SP system.

Syntax

spdisplay_config: [-h] [ -R] [-d] [-c] [-n] [ config_dir [/layout_dir
: [/syspar_dir]] | fully_qualified_path_name]

Flags

-h: Displays usage information. If this command is issued with the -h flag, the syntax description is displayed to standard output and no other action is taken (even if other valid options are entered with the -h flag).
-R: Recursively displays information for all levels below the specified directory level.
-d: Displays the description file (layout.desc) for the specified layout. This flag is valid only if the specified directory (or any subdirectories below it if -R is specified) is a layout directory.
-c: Displays the customization file (custom) for the specified system partition. This flag is valid only if the specified directory (or any subdirectories below it if -R is specified) is a system partition directory.
-n: Displays the node list file (nodelist) for the specified system partition. This flag is valid only if the specified directory (or any subdirectories below it if -R is specified) is a system partition directory.

Operands

config_dir: Specifies the directory name for a configuration directory.
layout_dir: Specifies the directory name for a layout directory.
syspar_dir: Specifies the directory name for a system partition directory.
fully_qualified_path_name: Specifies the fully qualified directory path for a configuration directory, layout directory, or system partition directory.

Description

The spdisplay_config command is valid only on systems with no switch or with an SP Switch. This command is not valid on |a system with an SP Switch2 switch or on a switchless clustered |enterprise server system.

This command displays system partition information stored in the system partition information directory structure. Depending on the option and operand specified, the information displayed is at the configuration, layout, or system partition level. The output of this command is normally restricted to the SP on which it is executed. To display information for configurations applicable to SP systems other than the one on which it is executed, a fully qualified path name must be provided. This command does not display current system partition information (that function is provided with the splstdata command). If the command is issued without specifying a directory path name, the list of all valid configuration directories for the SP on which the command is running is displayed. If none of the file option flags (-c, -d, -n) are entered, the names of the files and subdirectories located on (and all levels below if -R is specified) the specified directory are displayed. If any of the file option flags are entered, the contents of the requested files are displayed instead.

Files

custom: Contains customization information for a partition (such as, partition name, IP address, code level, and so on).
layout.desc: Describes the node slot breakdown for a partitioning configuration (which nodes in which partition).
nodelist: Contains a list of switch node numbers contained in a system partition (used internally, not by end users).
topology: Contains the wiring configuration information for switch-to-switch and node-to-switch cabling in a switch network. This information is used during switch initialization.

Security

You must have root privilege to run this command.

Location

/usr/lpp/ssp/bin/spdisplay_config

Related Information

Commands: spapply_config, spcustomize_syspar, splstdata, spverify_config

Files: nodelist, topology

Examples

|To display all valid configurations for this SP, enter:

|spdisplay_config
| 
|config.16
|config.4_12
|config.4_4_4_4
|config.4_4_8
|config.8_8

|To display the list of layout directory names for a specific configuration |directory to standard output, enter:
```
|spdisplay_config config.8_8
| 
|layout.1
|layout.2
|layout.3
```
|To display the name of the file describing the layout and the list of |system partition directory names for a specific layout directory to standard |output, enter:
```
|spdisplay_config config.8_8/layout.2
| 
|layout.desc
|nodes.syspar
|syspar.1
|syspar.2
```

|To display the list of files located in a specific system partition |directory to standard output, enter:

|spdisplay_config config.8_8/layout.2/syspar.1
| 
|custom
|nodelist
|topology

|If the -c flag is also supplied, only the customization |information is displayed for that system partition. For example:

|spdisplay_config -c config.8_8/layout.2/syspar.1
| 
|custom:
|syspar-name:              c53s
|IP-address:               9.114.10.53
|primary-node:             5
|default-install-image:    bos.obj.ssp.421
|PSSP-code-level:          PSSP-2.4
|backup-primary-node:      6

|If the -n flag is supplied, only the list of nodes is |displayed for that system partition. For example:

|spdisplay_config -n config.8_8/layout.2/syspar.1
| 
|nodelist:
|switch node numbers:    0   1   4   5  10  11  14  15
|node numbers:           1   2   5   6  11  12  15  16

|All of the commands can be issued with the -R flag to |recursively display the information on the specified directory and all the |levels below it.

|To display the entire system partition information directory structure for |the config.8_8 configuration on this SP, enter:

|spdisplay_config -R config.8_8
| 
|layout.1:
|layout.1/layout.desc
|layout.1/nodes.syspar
|layout.1/syspar.1:
|layout.1/syspar.1/nodelist
|layout.1/syspar.1/topology
|layout.1/syspar.2:
|layout.1/syspar.2/nodelist
|layout.1/syspar.2/topology
|layout.2:
|layout.2/layout.desc
|layout.2/nodes.syspar
|layout.2/syspar.1:
|layout.2/syspar.1/custom
|layout.2/syspar.1/nodelist
|layout.2/syspar.1/topology
|layout.2/syspar.2:
|layout.2/syspar.2/custom
|layout.2/syspar.2/nodelist
|layout.2/syspar.2/topology
|layout.3:
|layout.3/layout.desc
|layout.3/nodes.syspar
|layout.3/syspar.1:
|layout.3/syspar.1/nodelist
|layout.3/syspar.1/topology
|layout.3/syspar.2:
|layout.3/syspar.2/nodelist
|layout.3/syspar.2/topology

|Another example to recursively display all of the customization information |for the config.8_8 on this SP follows:

|spdisplay_config -R -c config.8_8
| 
|layout.2/syspar.1/custom:
|syspar-name:              c53s
|IP-address:               9.114.10.53
|primary-node:             5
|default-install-image:    bos.obj.ssp.433
|PSSP-code-level:          PSSP-3.4
|backup-primary-node:      6
| 
|layout.2/syspar.2/custom:
|syspar-name:              c53sp1
|IP-address:               9.114.10.240
|primary-node:             7
|default-install-image:    bos.obj.ssp.433
|PSSP-code-level:          PSSP-3.4
|backup-primary-node:      8

|To display all valid configurations for an SP, specify the fully qualified |path name to its system partition information directory. For |example:
```
|spdisplay_config /spdata/sys1/syspar_configs/1nsb0isb
| 
|config.16
|config.4_12
|config.4_4_4_4
|config.4_4_8
|config.8_8
```

spethernt

Purpose

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

Attention

The spethernt command has been replaced by the spadaptrs command. See the spadaptrs command for more information.

Attention
The spethernt command has been replaced by the spadaptrs command. See the spadaptrs command for more information.

Syntax

spethernt: [-s {yes | no}] [-t {bnc | dix | tp}]
: [-d {full | half | auto}] [-f {10 | 100 | auto} ]
: {start_frame start_slot {node_count | rest} | -N node_group |
: -l node_list}starting_IP_address netmask default_route

Flags

-s yes | no: Indicates whether IP addresses should be skipped, as needed, when assigning IP addresses. If -s no is specified, no skipping occurs; each IP address assigned is equal to the previous address assigned plus one. If -s yes is specified, each IP address assigned is equal to the previous address assigned plus the difference in their respective node numbers.
-t bnc | dix | tp: Designates the Ethernet type. Use dix to designate a thick Ethernet. Use bnc to designate a thin Ethernet. Use tp to designate a twisted pair. The default is bnc. |
|-d full | half | auto: |Specifies the communication transfer as one way (half) or two way |(full). The default is half. |
|-f 10 | 100 | auto: |Specifies Ethernet speed in megabits (Mb/s). Specify 10 |for 10Mb per second or 100 for 100Mb per second. The default |is 10.
-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 and, when the |count of nodes causes the nodes in a frame to be exhausted, 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. |

starting_IP_address

Specifies the IP address or host name of the first node in this operation. IP addresses of subsequent nodes are created by incrementing the IP address for each node, depending on how the -s flag is set. Specify a valid IP address or host name.

Ensure that the combination of the starting IP address, the node count operand, and the -s flag do not result in the incrementing of the IP address to an IP address that is not valid.

Each IP address used in the operation must be resolved by the host command on the control workstation. |

|netmask

|Specifies the netmask for the SP Ethernet administrative LAN adapter |network. Specify a valid IP netmask. |

|default_route

|The default route that you enter is not the same as the default |route on the node. The route that you enter goes in the SDR Node |Class. It is the route over which the node communicates with its |boot/install server (for example, install, customize, and so on). The |default route must be a valid SP Ethernet administrative LAN adapter path to |the node's boot/install server and the control workstation.

|The default route on the node is the route it will use for its network |communications if there is no specific route to the destination. During |the boot process, this is set to the default route in the SDR. It can |be changed later on in the boot process or after the node is running, but |should not be changed permanently in the SDR. For FDDI, token ring, or |other Ethernet adapters, create the route in |firstboot.cust. In order for the route to remain set |after customization, also set the route up in /etc/inittab after the |line that runs rc.sp. For the switch, set the route up |in /etc/inittab after the line that runs |rc.switch.

Description

Execute this command during installation of the SP to identify the IP addresses, netmask, and default route associated with the SP Ethernet administrative LAN adapters of the nodes. If all your IP addresses are in the same block, run this command once. If you have "holes" in your IP addressing scheme, run this command once for each block of addresses you want to assign.

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

smit node_data

and select the SP Ethernet Information option.

Notes:

This command should be run only on the control workstation. You must be logged into the control workstation as root to execute this command.
After running this command, you must issue the syspar_ctrl -r command to refresh system partition-sensitive subsystems in each system partition where node customization was performed. Subsystems like hats, hb, and hr need to be refreshed whenever nodes or adapters are added or deleted.
Any changes made will not take effect on the nodes until they are customized.
This command automatically resets the initial hostname back to the reliable hostname in the SDR.

Security

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

Location

/usr/lpp/ssp/bin/spethernt

Related Information

Commands: syspar_ctrl

Examples

The following example adds SDR information for an |SP Ethernet administrative LAN adapter network of 15 nodes (frame 1 slot 1 to frame 1 slot 16 with the first node being a wide node and the rest of the nodes thin nodes all in a single system partition) with IP addresses from 129.33.32.1 to 129.33.32.15, a netmask of 255.255.255.0, and a default route of 129.33.32.200. The addresses are to be assigned to correspond with the nodes in the frame; for example, they do not increment the IP address of a wide node by 2 before assigning the IP address of the next node.

spethernt -s no 1 1 15 129.33.32.1 255.255.255.0 129.33.32.200

spevent

Purpose

spevent - Directly invokes the Event Perspective graphical user interface (GUI).

Syntax

spevent: [-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 Event Perspective. The Event Perspective is a graphic vehicle for managing events and event definitions in the system.

This Perspective allows the user to interact with the Event Manager and the Problem Manager. The user can create event definitions, register or unregister event definitions, and delete event definitions. A properties dialog box is provided for viewing and editing the condition, the resource identifier, and other attributes of an event definition. The properties dialog box also provides users with the capability for creating new conditions. Event definitions are viewed and manipulated within system partition boundaries.

By default, the Event Definition pane displays all the event definitions in the current system partition. The user will be able to operate on the event definitions that have the same principal (Kerberos V4 or DCE) as the user.

When the command is invoked, preferences which define the look and layout of the spevent window are prioritized in the following order:

Command line options
User preferences profile
System preferences profile
Default values

Files

The Users Preferences are read from and saved to $HOME/.spevent(User Profile Name).

The System Preferences are read from and saved to /usr/lpp/ssp/perspectives/profiles/.spevent(System Profile name).

The spevent application resource file: /usr/lpp/ssp/perspectives/app-defaults/$LANG/Spevent

Security

Any user can run the spevent command, although many actions in the Event perspective require specific access to SP subsystems. The access depends on the type of security mechanism your SP system is using.

The minimum user requirements is Event Manager access in at least one partition. If these criteria are not met, the Event perspective displays a message and exits. See the chapter on security in PSSP: Administration Guide for more information.

The following access is required to have complete use of the Event perspective:

SDR write: To use Create and Delete Conditions.
Event Management: Event Management access is required to create or delete event definitions, view the event notification log, or create or modify conditions.
Problem Management: Problem Management access is required when you create or delete an event definition that contains an action.

Implementation Specifics

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

Prerequisite Information

For information on using the Event Perspective, see the online help and the "Using SP Perspectives" chapter in the PSSP: Administration Guide.

For information on the Event Management services, refer to "The Event Management subsystem" and "Using the Problem Management subsystem" chapters in PSSP: Administration Guide.

Location

/usr/lpp/ssp/bin/spevent

|Related Information

|You can also access the Event Perspective by using the SP Perspectives |Launch Pad. The perspectives command invokes the Launch |Pad. Other Perspectives may be launched by invoking the following |commands: sphardware, spsyspar, and |spvsd.

Examples

To invoke the spevent window, enter:
```
spevent
```
To bring up the Event Perspective using a specific user profile, enter:
```
spevent -userProfile myProfile
```

spframe

Purpose

spframe - Enters configuration data for a frame or series of frames and, optionally, set up the initial System Data Repository (SDR).

Syntax

|spframe: |[-p SP] [-r {yes|no}] |[-m] [-o] start_frame |frame_count starting_tty_port |

|spframe: |-p SAMI [-n |{starting_switch_port}] [-s |{s1tty}] [-r {yes|no}] |[-o] start_frame frame_count |starting_tty_port |

|spframe: |-p CSP [-n |{starting_switch_port}] [-r {yes|no}] |[-o] start_frame frame_count |starting_tty_port |

|spframe: |-p HMC -d {domain_name} |-i {list_of_HMC_IPaddresses}
|: |[-n {starting_switch_port}] |[-r {yes|no}] [-o] |frame_number |

Flags

|-d domain_name

|Indicates the identifier of the IBM

pSeries 690 server as it |is known to the Hardware Management Console (HMC). This flag is valid |only with -p HMC. |

|-i list_of_HMC_IPaddresses

|Indicates the IP addresses or host names of the HMC that controls the p690 |server for this non-SP frame. If redundant HMCs are used, the list |should be specified as multiple IP addresses or host names separated by commas |(","). The Hardware Monitor (hardmon) uses this list in the |order specified until it can establish a remote connection with an HMC. |This flag is valid only with -p HMC. |

|-m

|Indicates that the frames being added are multiple node switch board (NSB) |frames. These frames may contain one or more SP Switch2 NSBs. |This flag can be used only with the SP hardware protocol. To add a |multiple NSB frame, all nodes must be at PSSP 3.4 or later. |

|-n starting_switch_port

|Indicates the switch port number that connects the node that is in a |non-SP frame. If a frame count greater than one is specified, this |field indicates the starting switch port number in a range of contiguous |switch port numbers. This flag: |

|Cannot be used with -p SP
|Cannot be used with -p SAMI for SP Switch2 systems. |It can be used with -p SAMI on systems with no switch or with |the SP Switch.
|Cannot be used with -p CSP for SP Switch2 systems. |It can be used with -p CSP on systems with no switch or with |the SP Switch.
|Cannot be used with -p HMC for SP Switch2 systems. |It can only be specified for -p HMC on systems with no switch |or with the SP Switch if the attached server is not logically |partitioned. |

|Note:: "switch port number" is also known as "switch node number." |

|-o

|Allows frame numbers greater than 128. The maximum number of frames |that you can specify is 250. |

|-p hardware_protocol

|Indicates the hardware protocol of the nodes within the frame. |Valid hardware protocol values are: |

|SP: |Node in SP frame
|SP is also the protocol for SP frames that do not contain nodes, |for example, frames that contain ISB switches, NSB switches, and SP expansion |I/O units.
|SAMI: |RS/6000 S70, S7A, and S80 or pSeries 680
|CSP: |RS/6000 H80, M80, and pSeries 660 (6H0, 6H1, 6M1)
|HMC: |IBM pSeries 690 |

|The default is -p SP. |

|-r {yes|no}

|Indicates whether you want to reinitialize hardmon. If |this is the last or only time you are invoking this command during |installation, specify -r yes. If -r yes | is specified, the /spdata/sys1/spmon/hmacls file has the |default entries created.

|The default is -r no.

|Notes:

|IBM suggests that hardmon be reinitialized (-r yes |or hmreinit) after adding all SP protocol frames and before |additional non-SP protocol frames are added.
|As an alternative to setting the -r flag to yes, |you can execute hmreinit instead. |

|-s s1tty

|Indicates the s1 tty port for a single RS/6000 S80 or IBM

|pSeries 680 frame. If an s1 tty is specified, the frame count must be |one. If a hardware protocol (-p) of SAMI is specified |and the -s flag is not specified, an s1 tty value will be |generated by default with a tty value of one greater than the |starting_tty_port value. For example, if you enter:

|spframe -p SAMI 1 2 /dev/tty1

|the s1 tty value will be /dev/tty2 for frame 1 and |/dev/tty4 for frame 2.

|This flag is valid only for SAMI protocol frames (-p |SAMI).

Operands

|start_frame: |Specifies the frame number of the first frame to be used for this |operation. Specify a value between 1 and 128 inclusive. |
|frame_count: |Specifies the number of frames to be used for this operation. |Specify a value between 1 and 250 inclusive. Do not specify a frame |count with -p HMC. |
|starting_tty_port: |Specifies the device special file name of the tty port to be assigned to |the first frame on this operation. tty ports for subsequent frames are |assigned by incrementing the tty number for each frame. Specify the |full path of a valid tty device special file. Do not specify a |starting_tty_port with -p HMC.

Description

|Execute this command during the installation of the SP to identify |the connection of each frame to the control workstation. This command |needs to be executed at least once for each set of frame protocols being added |to the system, and once for each HMC protocol server. You can run this |command for several frames at once provided that they: |

|Are of the same protocol
|Are not HMC protocol servers
|Use consecutive information (frame numbers, tty connections, switch port |numbers, and so on, depending on frame protocol and system type) |

|The /etc/switch.info file is a means of specifying |to the configuration management code what the switch node number should be for |each node in an SP attached server. For SP attached servers that only |have a single node, you can still specify this through the spframe |command, which will write the data to the /etc/switch.info |file. For SP attached servers with multiple nodes (for example, logical |partitions), you must manually edit the /etc/switch.info file |in order to specify the switch node number for each of the multiple nodes in |the server. You must do this before running the spframe |command. The switch node number is required when attaching an SP Switch |or switchless system. It is optional for SP Switch2 or clustered |enterprise server systems.

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

smit enter_data

and select the SP Frame Information or non-SP Frame Information options.

Notes:

|For the p690 server, you must run the sphmcid command |before running the spframe command on the control workstation. |This must be done to obtain the HMC user ID and password that hardmon |requires to perform HMC operations.
This command should be run only on the control workstation. You must be logged into the control workstation as root to execute this command.
|IBM suggests that hardmon be reinitialized (-r |yes or hmreinit) after adding all SP protocol frames and before |additional non-SP protocol frames are added.
|To change the domain_name for a p690 server, specify the |-d flag. You must also specify -p HMC and |-i list_of_HMC_IPaddresses when changing the |domain_name.
|To change the list_of_HMC_IPaddresses for the p690 server, |specify the -i flag. You must also specify -p |HMC and -d domain_name when changing the |list_of_HMC_IPaddresses.

Security

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

Location

/usr/lpp/ssp/bin/spframe

Examples

The following example enters information for four frames (frame 1 to frame 4) and indicates that frame 1 is connected to /dev/tty1, frame 2 to /dev/tty2, and so on. The System Data Repository is to be initialized with this invocation of spframe.
```
spframe -r yes 1 4 /dev/tty1
```

|The following example enters non-SP information for two S80 servers |(frames 5 and 6). The first server has the following |characteristics:

|Frame Number:            5
|tty port for operator panel connection:    /dev/tty4
|tty port for serial terminal connection:   /dev/tty5
|switch port number:     14

|The second server has the following characteristics:

|Frame Number:            6
|tty port for operator panel connection:    /dev/tty6
|tty port for serial terminal connection:   /dev/tty7
|switch port number:     15

|To define these servers to PSSP and reinitialize the SDR, enter:

|spframe -r no -p SAMI -n 14 -s /dev/tty5 5 1 /dev/tty4
|spframe -r yes -p SAMI -n 15 -s /dev/tty7 6 1 /dev/tty6

|As an alternative, you can define these servers in one step by issuing |the following command:

|spframe -r yes -p SAMI -n 14 5 2 /dev/tty4

|To define multiple addresses for the p690, enter:

|spframe -p HMC -i 10.0.0.1,10.0.0.2 -d cpu001 -r yes 2

|The addresses can be in host name format. For example:

|spframe -p HMC -i hmc1.ppd.pok.ibm.com -d cpu001 2

|To enter information for one multiple NSB frame as frame 1 on |/dev/tty1 and reinitialize the SDR, enter:
```
|spframe -r yes -m 1 1 /dev/tty1
```

spget_syspar

Purpose

spget_syspar - Returns the IP address or name of the current system partition.

Syntax

spget_syspar [-n] [-d]

Flags

-n: Returns a host name instead of an address.
-d: Returns the name or IP address of the default system partition rather than the current system partition.

Operands

None.

Description

Use this command to display to standard output the IP address (in dotted decimal format) of the current or default system partition. The current system partition indicates the system partition to which System Data Repository (SDR) client requests are directed. The result is displayed in dotted decimal format unless -n is specified.

Restrictions

The -d flag will not work if the command is not issued on a control workstation or SP node.

Location

/usr/lpp/ssp/bin/spget_syspar

Examples

To display the IP address associated with the current system partition, enter:
```
spget_syspar
```
You should receive output similar to the following:
```
129.40.127.122
```
To display the name (host name alias of the control workstation) of the current system partition, enter:
```
spget_syspar -n
```
You should receive output similar to the following:
```
k47sp1
```

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