Purpose
SDRAddSyspar - Creates a new daemon using the System Resource Controller (SRC). The new daemon creates a subdirectory under the /spdata/sys1/sdr/partitions directory.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRAddSyspar IP_address
Flags
None.
Operands
Description
This command creates a new instance of the SDR daemon and passes it the IP address of the system partition. It does not perform all of the system management tasks involved in creating a system partition.
Security
You must have root privilege to run this command.
Location
/usr/lpp/ssp/bin/SDRAddSyspar
Examples
This command is for PSSP use only.
Purpose
SDRArchive - Archives the entire contents of the System Data Repository (SDR), except for the archives directory, for later retrieval.
| Attention |
|---|
|
Migration Note: Each new PSSP release may introduce new SDR classes and attributes. Use caution when using SDRArchive and SDRRestore to avoid overwriting new SDR classes and attributes. IBM suggests that after migration you do not execute SDRRestore from a back level system since it will overwrite any new SDR classes and attributes. |
Syntax
SDRArchive [append_string]
Flags
None.
Operands
Description
Use this command to tar the contents of the SDR and put the file in the /spdata/sys1/sdr/archives subdirectory. You might want to mount this directory from another machine or physical disk drive to protect against an error in the drive holding the SDR. The file name is backup.JULIANdate.HHMM.append_string, where JULIANdate.HHMM is a number or string uniquely identifying the date and time of the archive and append_string is the argument entered in the command invocation, if specified.
Security
You must have root privilege to run this command.
Restrictions
This command can be run only on the control workstation.
Location
/usr/lpp/ssp/bin/SDRArchive
Examples
To create an archive of the current SDR database called backup.{JULIANdate}.HHMM.mysdr, enter:
SDRArchive mysdr
Purpose
SDRChangeAttrValues - Changes attribute values of one or more objects.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRChangeAttrValues class_name [ attr==value ... ] attr=value ...
Flags
None.
Operands
Description
This command changes one or more attribute values in a specified object with certain other attribute values.
Exit Values
Security
You must have write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/SDRChangeAttrValues
Examples
This command is for PSSP use only.
Purpose
SDRClearLock - Unlocks a System Data Repository (SDR) class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRClearLock class_name
Flags
None.
Operands
Description
Use this command when a process that obtained a lock ends abnormally and does not unlock the class.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRClearLock
Examples
This command is for PSSP use only.
Purpose
SDRCreateAttrs - Creates new attributes for a System Data Repository (SDR) class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRCreateAttrs class_name attr=datatype ...
Flags
None.
Operands
Description
This command creates one or more new attributes for a target class.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateAttrs
Examples
This command is for PSSP use only.
Purpose
SDRCreateClass - Creates a partitioned class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRCreateClass class_name attr=datatype ...
Flags
None.
Operands
Description
This command creates a partitioned class and defines its attributes.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateClass
Examples
This command is for PSSP use only.
Purpose
SDRCreateFile - Reads the specified AIX file and puts it in the System Data Repository (SDR) under the specified SDR file name.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRCreateFile AIX_filename SDR_filename
Flags
None.
Operands
Description
This command creates a partitioned SDR file from an AIX file. Use SDRCreateSystemFile to create a system file. Use SDRRetrieveFile to retrieve the file.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateFile
Examples
This command is for PSSP use only.
Purpose
SDRCreateObjects - Creates new objects in a system class or a partitioned class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRCreateObjects class_name attr=value ...
Flags
None.
Operands
Description
This command creates one or more new objects. Not all attributes for an object need to be specified in this call; however, a subset of the attributes that uniquely identify this object must be entered at this time.
Exit Values
Security
You must have write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateObjects
Examples
This command is for PSSP use only.
Purpose
SDRCreateSystemClass - Creates a system class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRCreateSystemClass class_name attr=datatype ...
Flags
None.
Operands
Description
This command creates a system class and defines its attributes.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateSystemClass
Examples
This command is for PSSP use only.
Purpose
SDRCreateSystemFile - Creates a file that can be retrieved from any system partition.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive , SDRGetObjects, SDRListClasses , SDRListFiles, SDRRetrieveFile , SDR_test, and SDRWhoHasLock . |
Syntax
SDRCreateSystemFile AIX_filename SDR_filename
Flags
None.
Operands
Description
This command reads the AIX file and puts it in the repository under the SDR file name. Note that only ASCII files can be saved. Results are unpredictable if binary files are used with this command. Clients connected to any system partition can read this file.
Use SDRRetrieveFile to retrieve this file. If a system file and a partitioned file exist with the same name, the partitioned file will be returned from SDRRetrieveFile.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRCreateSystemFile
Examples
This command is for PSSP use only.
Purpose
SDRDeleteFile - Deletes the specified System Data Repository (SDR) file.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRDeleteFile SDR_filename
Flags
None.
Operands
Description
This command deletes the partitioned file SDR_filename, if it exists. If the SDR_filename partitioned file does not exist, it will delete the SDR_filename system file. This command will not delete both the partitioned file and the system file.
Exit Values
Security
You must have SDR administrator access to run this command.
Location
/usr/lpp/ssp/bin/SDRDeleteFile
Examples
This command is for PSSP use only.
Purpose
SDRDeleteObjects - Deletes objects from the System Data Repository (SDR).
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRDeleteObjects class_name [ attr==value ... ]
Flags
None.
Operands
Description
This command deletes one or more objects. All objects in the specified class with attribute values matching those specified are deleted. If no attr==value pairs are specified, this command will match all objects in the class and all objects will be deleted.
Exit Values
Security
You must have write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/SDRDeleteObjects
Examples
This command is for PSSP use only.
Purpose
SDRGetObjects - Sends contents of attributes in specified object to standard output.
Syntax
SDRGetObjects [-G] [ -x] [-q] [-d delimiter] class_name [attr==value ...] [attr ...]
Flags
Operands
Description
This command retrieves and sends to standard output attribute values in the specified objects.
Location
/usr/lpp/ssp/bin/SDRGetObjects
Examples
SDRGetObjects -G Adapter adapter_type==css0 node_number netaddr
You should receive output similar to the following:
node_number netaddr
1 129.40.102.129
3 129.40.102.131
5 129.40.102.133
6 129.40.102.134
7 129.40.102.135
8 129.40.102.136
9 129.40.102.137
10 129.40.102.138
11 129.40.102.139
12 129.40.102.140
13 129.40.102.141
14 129.40.102.142
15 129.40.102.143
16 129.40.102.144
SDRGetObjects -G Node reliable_hostname switch_node_number \
switch_chip_port
You should receive output similar to the following:
reliable_hostname switch_node_number switch_chip_port k3n01.hpssl.kgn.ibm.com 0 3 k3n03.hpssl.kgn.ibm.com 2 0 k3n05.hpssl.kgn.ibm.com 4 1 k3n06.hpssl.kgn.ibm.com 5 0 k3n07.hpssl.kgn.ibm.com 6 2 k3n08.hpssl.kgn.ibm.com 7 3 k3n09.hpssl.kgn.ibm.com 8 3 k3n10.hpssl.kgn.ibm.com 9 2 k3n11.hpssl.kgn.ibm.com 10 0 k3n12.hpssl.kgn.ibm.com 11 1 k3n13.hpssl.kgn.ibm.com 12 1 k3n14.hpssl.kgn.ibm.com 13 0 k3n15.hpssl.kgn.ibm.com 14 2 k3n16.hpssl.kgn.ibm.com 15 3
SDRGetObjects -G -x Node node_number hdw_enet_addr > /etc/bootptab.info
You should receive output similar to the following:
1 02608C2D58D2
3 10005AFA2375
4 10005AFA22CE
5 10005AFA22B2
6 10005AFA2410
7 10005AFA223F
8 10005AFA2417
9 02608C2DA0C7
11 02608C2D9F62
13 02608C2D9E75
15 10005AFA1B03
16 10005AFA2B9B
Purpose
SDRListClasses - Lists the class names in the System Data Repository (SDR).
Syntax
SDRListClasses
Flags
None.
Operands
None.
Description
This command outputs all of the class names (system and partitioned) currently defined in the SDR to standard output.
Location
/usr/lpp/ssp/bin/SDRListClasses
Examples
To list all classes in the SDR, enter:
|SDRListClasses
You will see output such as:
|Adapter |Aggregate_IP |CSS_Adapter_Info |CSS_Type |DependentAdapter |DependentNode |Dont_care_pool_list |EM_Condition |EM_Resource_Class |EM_Resource_ID |EM_Resource_Monitor |EM_Resource_Variable |EM_Structured_Byte_String |Frame |GMT_Global_smt_nds |GS_Config |HSD_Minor_Number |HSD_Table |JM_domain_info |JM_job_info |JM_node_usage |JM_server_nodes |Network |...
Purpose
SDRListFiles - Lists all of the files in the system file area first, then lists all of the files in the system partition area.
Syntax
SDRListFiles
Flags
None.
Operands
None.
Description
This command outputs all the system partition files first, then the system files.
Location
/usr/lpp/ssp/bin/SDRListFiles
Examples
To list all files in the SDR, enter:
SDRListFiles
You will see output such as:
expected.top.annotated.1 hats.machines.inst hats.machines.lst
Purpose
SDRMoveObjects - Moves objects from one system partition to another.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRMoveObjects source_syspar target_syspar class_name [attr== value ...]
Flags
None.
Operands
Description
This command moves any objects in class_name that match all of the attr==value pairs from the source_syspar to the target_syspar.
Exit Values
Security
You must have write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/SDRMoveObjects
Examples
This command is for PSSP use only.
Purpose
SDRRemoveSyspar - Removes all of the partitioned classes in the System Data Repository (SDR) associated with the system partition whose address is IP_address. It removes the daemon that serves this system partition using the System Resource Controller (SRC).
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRRemoveSyspar IP_address
Flags
None.
Operands
Description
This command deletes a system partition in the SDR. It does not perform all of the system management tasks involved in deleting a system partition.
Security
You must have root privilege to run this command.
Location
/usr/lpp/ssp/bin/SDRRemoveSyspar
Examples
This command is for PSSP use only.
Purpose
SDRReplaceFile - Replaces the specified System Data Repository (SDR) file with the specified AIX file.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRReplaceFile AIX_filename SDR_filename
Flags
None.
Operands
Description
This command searches first for a partitioned file, then for a system file, and replaces the first one found.
Exit Values
Security
You must have write access to the SDR to run this command.
Location
/usr/lpp/ssp/bin/SDRReplaceFile
Examples
This command is for PSSP use only.
Purpose
SDRRestore - Extracts the contents of the archived System Data Repository (SDR).
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
| Attention |
|---|
|
Migration Note: Each new PSSP release may introduce new SDR classes and attributes. Use caution when using SDRArchive and SDRRestore to avoid overwriting new SDR classes and attributes. IBM suggests that after migration you do not execute SDRRestore from a back level system since it will overwrite any new SDR classes and attributes. |
Syntax
SDRRestore archive_file
Flags
None.
Operands
Description
Use this command to remove the contents of the SDR and retrieve the archived contents of the archive_file. The archive_file must be in the /spdata/sys1/sdr/archives directory. Any new SDR daemons that represent partitions in the restored SDR are then started and any daemons that are not in the new SDR are stopped.
Security
You must have root privilege to run this command.
Restrictions
This command can be run only on the control workstation.
Location
/usr/lpp/ssp/bin/SDRRestore
Related Information
Commands: SDRArchive
Examples
To restore an archive of the SDR database called backup.{JULIANdate}.HHMM.mysdr, enter:
SDRRestore backup.{JULIANdate}.HHMM.mysdr
Purpose
SDRRetrieveFile - Retrieves the specified System Data Repository (SDR) file into an AIX file.
Syntax
SDRRetrieveFile SDR_filename AIX_filename
Flags
None.
Operands
Description
This command searches first for a partitioned file, then for a system file if a partitioned file was not found.
Location
/usr/lpp/ssp/bin/SDRRetrieveFile
Examples
This command is for PSSP use only.
Purpose
SDRScan - Scans the SDR database files of non-ASCII data.
Syntax
SDRScan [-q] [-f]
Flags
Operands
None.
Description
The SDRScan command scans the SDR database files for non-ASCII data. ASCII data is defined as all characters in the range '00'x to '7F'x. If non-ASCII data is found, a nonzero exit value is set. If the -q option is not specified, a message is displayed for each non-ASCII value found, indicating the SDR class and attribute in which the data was found, along with the entire record from the SDR database. If the -f option is specified, processing stops after the first non-ASCII value is found.
Files
Standard Output
All SDR objects containing non-ASCII data will be written to standard output.
Standard Error
Internal processing errors will be written to standard error.
Exit Values
Restrictions
The command can only be run on the control workstation.
If SDRScan encounters data in the SDR that was generated under a different locale, the results displayed may be unreadable in the current locale.
Implementation Specifics
This command is part of IBM Parallel System Support Programs (PSSP) Licensed Program (LP) ssp.basic file set.
Location
/usr/lpp/ssp/bin/SDRScan
Related Information
Commands: SDRValidateString
Examples
To scan the SDR for non-ASCII data, enter:
SDRScan
Purpose
SDRSetTsAuth - Updates the ts_auth_methods value in the Syspar Class.
| Attention |
|---|
|
The System Data Repository (SDR) commands are to be used by the IBM Parallel System Support Programs for AIX (PSSP) system management software. Use of these commands by a user can cause damage to system configuration data. Exceptions are: SDRArchive, SDRGetObjects, SDRListClasses, SDRListFiles, SDRRetrieveFile, SDR_test, and SDRWhoHasLock. |
Syntax
SDRSetTsAuth syspar_name ts_auth_methods
Flags
None.
Operands
Description
The SDRSetTSAuth command stops the SDR subsystem for the affected partition, modifies the Syspar class file, and restarts the subsystem.
Files
/spdata/sys1/sdr/partitions/syspar-ip-address/classes/Syspar
Standard Error
Output consists of error messages, when the command cannot complete successfully.
Exit Values
Security
You must be running on the control workstation with root privilege to run this command.
You must have write access to the SDR to run this command.
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/install/bin/SDRSetTsAuth
Examples
Setting the trusted services authentication methods for a partition:
#/usr/lpp/ssp/install/bin/SDRSetTsAuth partB dce:compat 0513-044 The stop of the sdr.partB Subsystem was completed successfully. 0025-041 waiting for 28324 to exit 0025-043 waiting for 28324 to exit, will kill -9 in 1 minute 0025-044 28324 has exited 0513-059 The sdr.part Subsystem has been started. Subsystem PID is 14562. #
Purpose
SDRValidateString - Checks a character string for valid input that can be written to the SDR.
Syntax
SDRValidateString [-q] string
Flags
Operands
Description
The SDRValidateString command verifies whether the input string to be written to the SDR is valid. If the string contains only ASCII characters, the command returns success indicating the string can be written to the SDR. ASCII characters are defined as any character in the range '00'x to '7F'x. If the string contains non-ASCII characters, the command returns either success or failure according to the following rules:
The attribute SDR_ASCII_only in the SP class determines if non-ASCII data is allowed to be written to the SDR. If this attribute value is true, only ASCII data is allowed; if it is false, non-ASCII data is allowed. You can query the values of the SP admin_locale and SDR_ASCII_only attributes by running the splstdata -e command.
Environment Variables
The NLS environment variables (such as LC_ALL, LC_CTYPE, LANG) affect the operation of this command.
Standard Error
When the -q flag is omitted, the command failure message is written to standard error.
Exit Values
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/SDRValidateString
Related Information
Commands: splstdata, spsitenv, SDRScan
Examples
/usr/lpp/ssp/bin/SDRValidateString -q "abc"
SDRValidateString: 0025-045 The string contains non-ASCII character data that cannot be written to the SDR.
Purpose
SDRWhoHasLock - Returns transaction ID of lock on specified class.
Syntax
SDRWhoHasLock class_name
Flags
None.
Operands
Description
The lock transaction ID returned from this command takes the form host_name:pid:session, where host_name is the long name of the machine running the process with the lock, pid is the process ID of the process that has the lock, and session is the number of the client's session with the System Data Repository (SDR).
Location
/usr/lpp/ssp/bin/SDRWhoHasLock
Examples
To find the transaction ID of the SDR client holding a lock on the Frame class, enter:
SDRWhoHasLock Frame
Purpose
seqfile - Creates node sequence files for system startup and shutdown using information in the System Data Repository (SDR).
Syntax
seqfile [-b]
Flags
Operands
None.
Description
seqfile uses information in the SDR to determine dependencies of SP nodes on /usr and, optionally, and boot/install servers, and to write the dependencies to standard output in the format of the node sequence files /etc/cstartSeq and /etc/cshutSeq.
/usr servers must shut down after and start before their clients. Boot-install servers must start before their clients. The node sequence files, /etc/cshutSeq and /etc/cstartSeq, have lines that describe these dependencies. The seqfile command eliminates the need for you to create these files from scratch. If the nodes in your system have sequencing dependencies in addition to those related to boot/install and /usr servers and clients, you can edit the output of seqfile to define those relationships.
seqfile defines only the nodes that have dependencies; if there are no /usr or boot/install dependencies, seqfile generates no output.
If you do not have a /etc/cstartSeq or /etc/cshutSeq file, the cstartup and cshutdown commands use seqfile to determine the default startup or shutdown sequence.
Files
The following files reside on the control workstation:
Security
You must have write access to the /etc/cstartseq and /etc/cshutseq directories to run this command.
Location
/usr/lpp/ssp/bin/seqfile
Related Information
Commands: cshutdown, cstartup
Examples
seqfile -b > /etc/cstartSeq
seqfile > /etc/cshutSeq
seqfile | more
Purpose
services_config - Configures designated services on nodes or the control workstation.
Syntax
services_config
Flags
None.
Operands
None.
Description
Use this command to configure SP services on the node or control workstation.
Standard Error
This command writes error messages (as necessary) to standard error.
Exit Values
Security
You must have root privilege to run this command.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Location
/usr/lpp/ssp/install/bin/services_config
Related Information
Commands: setup_server, spbootins
Examples
To configure the SP services on a node or the control workstation, enter:
services_config
Purpose
sethacws - Sets the HACWS state of the control workstation.
Syntax
sethacws state
Flags
None.
Operands
Description
Use this command to set the current HACWS state of the control workstation. It is valid only when issued on the control workstation. When the command is executed and the calling process is not on a control workstation, an error occurs.
Exit Values
The following are the valid state values and their defined control workstation state:
Security
You must have root privilege to run this command.
Prerequisite Information
Refer to PSSP: Administration Guide for information on the HACWS option.
Location
/usr/bin/sethacws
Related Information
Commands: lshacws
Subroutines: hacws_set, hacws_stat
Examples
sethacws 32
sethacws 16
sethacws 2
sethacws 1
sethacws 0
Purpose
setup_authent - Sets up a workstation to use SP Kerberos Version 4 authentication services.
Syntax
setup_authent
Flags
None.
Operands
None.
Description
The setup_authent command configures SP Kerberos Version 4 authentication services during SP installation on the control workstation and on other IBM RS/6000 workstations connected to an SP system. It is not executed on SP nodes, where authenticated client services are automatically installed. Executing this command invokes an interactive dialog, in which instructions for the various steps are displayed and various utility programs are invoked to accomplish the configuration.
There are several ways that setup_authent can configure these services. The method chosen is based on runtime choice, the combination of SP options installed on the workstation, and the contents of any predefined authentication configuration file that you have supplied.
Primary Server: When the local system is to be configured as the primary server, both ssp.clients and ssp.authent SP options must have been installed. You may supply the configuration files, /etc/krb.conf and /etc/krb.realms , or let the system create one that lists the local system as the sole authentication server in the local realm. This command creates the files used by the Kerberos Version 4 authentication and ticket granting services. These include the configuration files, the authentication database files, and the master key cache file. The server daemon, kerberos, is added to the inittab and started.
The administration of the Kerberos Version 4 authentication database is handled by the kadmind daemon, which is also added to inittab and started. The setup_authent command requires you to define the initial principal who administers the database. Access control list files are created containing this name, to be used by kadmind for authorization.
This command invokes k4init to log you in as this administrator, to define additional principals used by the SP Kerberos Version 4 authenticated services for monitoring and system administration. A server key file is created for use by the monitor commands, SP remote commands, and Sysctl remote command execution facility.
Backup Server: When the local workstation is to be configured as a secondary server, ssp.clients and ssp.authent must be installed. You must supply the configuration files, listing the local host as a slave server and some other workstation as the primary authentication server. The primary server must be configured and running and be available by standard TCP/IP connection to the local host.
You are required to authenticate your identity as the Kerberos Version 4 administrative user that you defined when you configured the primary server. The service principals for the local host are added to the primary database, and the server key file is created for them. Then the kpropd daemon is used in conjunction with the kprop command (executed remotely on the primary server) to copy the master database onto the local system. The server daemon, kerberos , is then added to the inittab and started.
Authentication Server: When the local host is to be configured only to provide Kerberos Version 4 authentication client services, just ssp.clients needs to be installed. As in the case of the slave server, you must supply the configuration files. In this case, however, the local host is not listed as a server. setup_authent simply requires the information to know how to get to the primary Kerberos Version 4 authentication server (already configured and accessible).
You are required to authenticate your identity as the Kerberos Version 4 administrative user that you defined when you configured the primary server. The service principals for the local host are added to the primary database, and the server key file is created for them.
Using AFS Authentication Services: When AFS Kerberos Version 4 authentication is to be configured, the local host must have already been established as either an AFS server or an AFS client. The CellServDB and ThisCell files are expected to exist in the /usr/vice/etc directory (or linked to that path). ssp.clients is the only required SP Kerberos Version 4 authentication option. When setup_authent finds these AFS configuration files on the local system, it allows you the choice of whether to use AFS Kerberos Version 4 authentication. If you choose not to use AFS, processing follows one of the other three variations described previously. When using AFS, you must supply an AFS user name and password that is a valid Kerberos Version 4 administrative ID in the local AFS cell. Then setup_authent creates the local service principals in the AFS database and creates a server key file for the SP Kerberos Version 4 authenticated services to use on the local host.
If you choose AFS Kerberos Version 4 authentication, you must do so for all workstations you configure with setup_authent , including the control workstation for your SP system.
You can reexecute setup_authent to change the configuration of your Kerberos Version 4 authentication services, but you add varying degrees of risk to system operations depending on how far you have progressed in the installation of the control workstation and nodes. Running it again on the control workstation prior to executing install_cw is not a problem. Reconfiguring a client workstation has little risk of disruption. A slave can be reconfigured provided the primary server is available. If the primary server must be reconfigured, all slave and client systems have to be reconfigured after the new primary server is up. If the control workstation is a Kerberos Version 4 authentication server, you have to recustomize any SP nodes previously booted, after running setup_authent.
Files
|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 setup_authent using a secure |remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
You must have root privilege to run this command. If you are running setup_authent on an active control workstation with DCE as the only Trusted Services authentication method, you must also have SDR write access.
Location
/usr/lpp/ssp/bin/setup_authent
Related Information
Commands: add_principal, ext_srvtab, kadmind, kdb_edit, kdb_init, kdb_util, kerberos, k4init, k4list, krb_conf, krb_realms, ksrvutil, kstash
Refer to the "RS/6000 SP files and other technical information" section of PSSP: Command and Technical Reference for additional Kerberos information.
Examples
See PSSP: Installation and Migration Guide.
Purpose
setup_CWS - Updates control workstation files and directories for installation tasks.
Syntax
setup_CWS [-h]
Flags
Operands
None.
Description
Use this command to update control workstation files and directories for installation tasks. This includes control workstation-specific Kerberos and other files. This command can only be run on the control workstation.
Standard Error
This command writes error messages (as necessary) to standard error.
Exit Values
Security
You must have root privilege and write access to the SDR to run this command.
If Kerberos V4 is configured, Kerberos V4 administrator privileges are required whenever you run setup_CWS following the addition or name change of a network interface on a node (defined by an Adapter or Aggregate_IP object in the SDR) or on the control workstation.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Location
/usr/lpp/ssp/bin/setup_CWS
Related Information
Commands: setup_server
Examples
To update the control workstation environment for installation, enter:
setup_CWS
Purpose
setup_logd - Sets up the logging daemon (splogd). This is called by installation scripts when the IBM RS/6000 control workstation is installed. It can also be run by root on a different workstation to have splogd spawned by the System Resource Controller (SRC).
Syntax
setup_logd
Flags
None.
Operands
None.
Description
To run the splogd logging daemon on a workstation other than the control workstation, install the ssp.clients option on that workstation and run setup_logd. You may want to do this so that:
By default the /spdata/sys1/spmon/hwevents file is set up to do error logging and state change logging for all frames. If you are installing splogd on a workstation besides the control workstation to call your own script, you should edit the /spdata/sys1/spmon/hwevents file, removing the entries for SP_STATE_LOG and SP_ERROR_LOG and add a call for your own script. Refer to the splogd command for instructions.
The setup_logd command performs the following steps:
If you do not want to perform any of the preceding steps on your workstation, do not run setup_logd. If you are only using splogd to call your own script, you might only want to do step 4 and step 5 (add splogd to SRC and /etc/inittab).
To run the logging daemon on a separate workstation, you must add the following to the /etc/environment file:
SP_NAME={control_workstation}
To move a subset of error logging off of the control workstation, edit /spdata/sys1/spmon/hwevents on the control workstation to define the subset that you want to monitor. Then stopsrc and startsrc the logging daemon on the control workstation to reread the hwevents file.
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
Security
You must have root privilege to run this command.
Location
/usr/lpp/ssp/bin/setup_logd
Related Information
Daemons: splogd
Refer to PSSP: Installation and Migration Guide for more information on setting up Hardware Monitor clients on separate workstations and the System Resource Controller.
Examples
startsrc -s splogd
stopsrc -s splogd
lssrc -s splogd
lssrc -a
odmget -q "subsysname=splogd" SRCsubsys
Purpose
setup_server - Configures a node or control workstation as a boot/install server.
Syntax
setup_server [-h]
Flags
Operands
None.
Description
Use this command to set up the node on which it is run as a boot/install server for client nodes as defined in the System Data Repository (SDR).
On a boot/install server, this command:
Creation of the Network Installation Management (NIM) lppsource resource on a boot/install server will result in setup_server creating a lock in the lppsource directory on the control workstation. The setup_server command calls mknimres which creates the lock.
|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 setup_server using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Error
This command writes error messages (as necessary) to standard error.
Exit Values
Security
You must have root privilege and write access to the SDR to run this command.
|You must be authorized to perform a dsh to the target |nodes. Therefore, your user ID must be in the appropriate authorization |file (.k5login, .klogin, or |.rhosts) on the target nodes or secure remote shell must be |enabled.
|If Kerberos V4 is configured, Kerberos V4 administrator privileges |are required whenever you run setup_server following the addition or |name change of a network interface on a node (defined by an Adapter or |Aggregate_IP object in the SDR) or on the control workstation unless using a |secure remote shell.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Location
/usr/lpp/ssp/bin/setup_server
Related Information
Commands: allnimres, create_krb_files, delnimclient, delnimmast, export_clients, mkconfig, mkinstall, mknimclient, mknimint, mknimmast, mknimres, setup_CWS, unallnimres
Examples
To prepare a boot/install server node, enter the following on that node:
setup_server
Purpose
|setupdce - Creates registry entries for DCE |clients. | |
Syntax
or
Flags
Operands
None.
Description
|The setupdce command is used to update the SDR with DCE |server's information and to register remote nodes in the DCE |database.
The command uses config.dce to register the remote nodes into the DCE database. It ensures that all of the nodes in system partitions that have DCE set as an authentication method are registered in the DCE database. Each remote node will have its self host machine principal and account created and 'ftp' and 'host' principal and account entries created for each of its adapters. Each time the command is run, all new nodes will be registered with all of their adapters. However, if new adapters are added to a node after setupdce has been run, those adapters will not be registered in the subsequent runs of setupdce.
When new adapters are added with a registered node, the kerberos.dce command should be run with the admin configuration option for that specific new adapter. Refer to DCE documentation for more information on the kerberos.dce command.
The -u flag causes the command to update the SDR with the appropriate server host names. If -u is used by itself, a check is made to ensure the server values are stored in the SDR; if they are not, the SDR is updated with the control workstation host names. The -s and -d flags can be used only with the -u flag. |Using the -u flag requires UNIX root authority; |otherwise, DCE cell administrator authority is required.
|This command can be run remotely for the -c and |-l parameters. To run the command remotely, set the |SP_NAME environment variable to the short host name of the appropriate SDR |daemon.
Files
|A Log file is created in /var/adm/SPlogs/auth_install/log.
Exit Values
Errors may cause some principals to not be created for some remote nodes. Once setupdce is run again without any errors, there will not be any unexpected problems because of earlier unsuccessful runs.
Identify the problems in updating the DCE registry, correct the problem, and rerun the command.
Security
The -u flag requires UNIX root user authority and write access to the SDR; otherwise DCE cell administrator authority is required.
Prerequisite Information
IBM Distributed Computing Environment for AIX: Administration Guide
PSSP: Installation and Migration Guide
Location
/usr/lpp/ssp/bin/setupdce
Related Information
Commands: config.dce, kerberos.dce
Examples
setupdce
setupdce -u -s abc.def.com -d ghi.jkl.com
setupdce -u