Purpose
lppdiff - Queries installed Licensed Program (LPs) on a group of hosts.
Syntax
Flags
Operands
Description
Use this command to query the status of installed LPs on a group of hosts. The output from each host is collected and identical results are compressed to show the names and a count of the hosts that had identical results.
The dsh command is used to execute the queries on the remote hosts. The lslpp command is used to get the status of the installed LPs on the remote hosts. The lslpp command is called on each host with the -l, -a, -c, and -q flags.
Output from the lppdiff command consists of one entry for each unique LP listing information about that LP. Each LP's entry is followed by a list of all hosts that have that LP installed. An LP is considered unique if any one of the components in its description differ from that of another. For example, consider two hosts that both have ssp.basic installed. On host 1, it is in the APPLY state and on host 2, it is in the COMMITTED state. These LPs are considered unique and, therefore, each will get its own set of output from lppdiff.
The flags for lppdiff are used to direct the dsh command to certain hosts and to control its behavior. See the dsh command for details on these flags and how to use them.
The fileset operand to lppdiff can be one of two things. It can either be all which queries and displays information about all LPs installed on the specified hosts, or it can be the name of a file set to query on the specified hosts. The "*" character can be used to specify multiple file sets. For example, lppdiff -Ga ssp.* queries any file sets starting with "ssp." on all hosts in the system.
|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 lppdiff 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 access to the AIX remote commands or the secure remote |commands to run this command.
|When restricted root access (RRA) is enabled, this command can only |be run from the control workstation.
Location
/usr/lpp/ssp/bin/lppdiff
Examples
|[c180s] [/]> lppdiff -a ssp.basic
|You should receive output similar to the following:
|---------------------------------------------------------------------- | Name Path Level PTF State Type Num |---------------------------------------------------------------------- |LPP: ssp.basic /etc/objrepos 3.4.0.0 COMMITTED I 4 |From: c180n01.ppd.pok.ibm.com c180n05.ppd.pok.ibm.com | c180n09.ppd.pok.ibm.com c180n10.ppd.pok.ibm.com |---------------------------------------------------------------------- |LPP: ssp.basic /usr/lib/objrepos 3.4.0.0 COMMITTED I 4 |From: c180n01.ppd.pok.ibm.com c180n05.ppd.pok.ibm.com | c180n09.ppd.pok.ibm.com c180n10.ppd.pok.ibm.com
|
|[c180s] [/]> lppdiff -w c180n01 X11.base* | |-------------------------------------------------------------------- | Name Path Level PTF State Type Num |-------------------------------------------------------------------- |LPP: X11.base.rte /etc/objrepos 4.3.3.25 COMMITTED I 1 |From: c180n01 |-------------------------------------------------------------------- |LPP: X11.base.smt /etc/objrepos 4.3.3.0 COMMITTED I 1 |From: c180n01 |-------------------------------------------------------------------- |LPP: X11.base.com /usr/lib/objrepos 4.3.3.0 COMMITTED I 1 | common |From: c180n01 |-------------------------------------------------------------------- |LPP: X11.base.lib /usr/lib/objrepos 4.3.3.25 COMMITTED I 1 |From: c180n01 |-------------------------------------------------------------------- |LPP: X11.base.rte /usr/lib/objrepos 4.3.3.25 COMMITTED I 1 |From: c180n01 |-------------------------------------------------------------------- |LPP: X11.base.smt /usr/lib/objrepos 4.3.3.0 COMMITTED I 1 |From: c180n01
|[c180s] [/]> lppdiff -Ga ssp.clients ssp.bogus | |---------------------------------------------------------------------- | Name Path Level PTF State Type Num |---------------------------------------------------------------------- |LPP: ssp.clients /etc/objrepos 3.4.0.0 COMMITTED I 4 |From: c180n01.ppd.pok.ibm.com c180n05.ppd.pok.ibm.com | c180n09.ppd.pok.ibm.com c180n10.ppd.pok.ibm.com |---------------------------------------------------------------------- |LPP: ssp.clients /etc/objrepos 3.4.0.0 COMMITTED I 4 |From: c180n01.ppd.pok.ibm.com c180n05.ppd.pok.ibm.com | c180n09.ppd.pok.ibm.com c180n10.ppd.pok.ibm.com |---------------------------------------------------------------------- |========================= Errors ===================================== |Error: /bin/lslpp: 0504-132 Fileset ssp.bogus not installed. |From: c180n01.ppd.pok.ibm.com c180n05.ppd.pok.ibm.com | c180n09.ppd.pok.ibm.com c180n10.ppd.pok.ibm.com |----------------------------------------------------------------------
|[c180s][/]> lppdiff -Gac ssp.clients ssp.bogus | |From:Name:Path:Level:PTF:State:Type:Num |c180n01.ppd.pok.ibm.com,c180n05.ppd.pok.ibm.com,c180n09.ppd.pok.ibm.com, |c180n10.ppd.pok.ibm.com:ssp.clients:/etc/objrepos:3.4.0.0::COMMITTED:I:4 |c180n01.ppd.pok.ibm.com,c180n05.ppd.pok.ibm.com,c180n09.ppd.pok.ibm.com, |c180n10.ppd.pok.ibm.com:ssp.clients:/usr/lib/objrepos:3.4.0.0:COMMITTED: | I:4 |From:Error |c180n01.ppd.pok.ibm.com,c180n05.ppd.pok.ibm.com,c180n09.ppd.pok.ibm.com, |c180n10.ppd.pok.ibm.com:/bin/lslpp: |0504-132 Fileset ssp.bogus not installed.
Purpose
lsauthpar - Lists and verifies the active remote command authentication methods for a system partition.
Syntax
lsauthpar [-h | [-c] [ -p partition] [-v]]
Flags
Operands
None.
Description
The lsauthpar command lists the remote command authentication methods that are active for the system partition. This command verifies the settings in the System Data Repository (SDR), reporting spurious settings; to make corrections use the chauthpar command.
This command also provides an option to check whether all nodes in the applicable system partition have the correct setting. No remote verification will occur, unless the SDR setting is valid.
|When verifying settings on running nodes using dsh via the |AIX rsh command to run lsauthent, the control workstation |and the nodes must have at least one common remote command authentication |method active. When this is not the case, verification will result in |errors reported by dsh or rsh. The AIX setting on the |nodes must be reset by the local root user issuing chauthent on each |node or by a reboot. No attempt is made to verify nodes that are |inaccessible.
|The lsauthpar command can also be run by dsh using |the secure remote command routine by setting the RCMD_PGM environment variable |to use "secrshell." See PSSP: Installation and |Migration Guide for more information on setting up the secure remote |command environment.
When you specify -v, this command uses the remote command facilities to obtain the settings from nodes in the system partition. Authorization to perform that task will be unsuccessful for any remote host that does not have at least one of the required remote command authentication methods active. If the command finds discrepancies, it will be necessary to execute the chauthent command on the indicated nodes or to re-boot the nodes, to enable client/server communication with them.
Environment Variables
The SP_NAME variable can be used to designate the applicable partition.
|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 lsauthpar using a secure |remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Output
When -v is omitted, output consists of the methods that are active for the system partition, in the order of precedence established when they were set. When the -c flag is specified, the output is a single line consisting of a colon-separated list of methods. Without the -c flag, each method is identified by a descriptive name on a separate line. When verification is specified, methods are displayed in colon-delimited format.
Standard Error
Output consists of error messages when the command cannot complete successfully and when discrepancies are found during verification.
Exit Values
Security
When the -v option is omitted, the lsauthpar command may be used by any user. Successful verification of the setting on a node requires the user to be authorized for remote command execution from the control workstation to that node.
Restrictions
When the -v option is specified, the command may be executed only on the control workstation.
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 the PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/lsauthpar
Examples
$lsauthpar Kerberos 5 Kerberos 4 Standard Aix
$lsauthpar -c -p 120.14.89.10 k4:std
$lsauthpar -v -p sp4partA Remote command authentication methods for the partition: k4:std No discrepancies were found.
$lsauthpar -p sp3p2 -v Remote command authentication methods for the partition: k5:k4:std lsauthpar: 0016-347 On sp3n13.abc.com the remote command authentication methods are incorrectly set to "std"
Purpose
lsauthpts - Lists and verifies the active trusted services authentication methods for a system partition.
Syntax
lsauthpts [-h | [-c] [-p partition] [-v]]
Flags
Operands
None.
Description
The lsauthpts command lists the trusted services authentication methods that are active for the system partition. This command always verifies the correctness of the setting in the System Data Repository, reporting spurious settings to the user, who can use the chauthpts command to make corrections.
This command also provides an option to check whether all nodes in the applicable system partition have the correct setting. No remote verification will occur, unless the SDR setting is valid.
|When verifying settings on running nodes using the AIX rsh |command via dsh to run lsauthts, the control workstation and |the nodes must have at least one common remote command authentication method |active. When this is not the case, verification will result in errors |reported by dsh.
|The lsauthpts command can also be run by dsh using |the secure remote command routine by setting the RCMD_PGM environment variable |to use "secrshell." See PSSP: Installation and |Migration Guide for more information on setting up the secure remote |command environment.
Environment Variables
The SP_NAME environment variable can be used to designate the applicable partition.
|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 lsauthpts using a secure |remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Standard Output
When -v is omitted, output consists of the methods that are active for the system partition, in the order of precedence established when they were set. When the -c flag is specified, the output is a single line consisting of a colon-separated list of methods. Without the -c flag, each method is identified by a descriptive name on a separate line. When verification is specified, methods are displayed in colon-delimited format.
Standard Error
Output consists of error messages when the command cannot complete successfully, and when discrepancies are found during verification.
When you specify -v, this command uses the remote command facilities to obtain the settings from nodes in the system partition. Authorization to perform that task will fail for any remote host that does not have at least one of the required remote command authentication methods active. If the command finds discrepancies, it will be necessary to execute the chauthts command on the indicated nodes, or to re-boot the nodes to enable client-server communication.
Exit Values
Security
When -v is omitted, the lsauthpts command may be used by any user. Successful verification of the setting on a node requires the user to be authorized for remote command execution from the control workstation to that node.
Restrictions
When the -v option is specified, the command may be executed only on the control workstation.
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 the PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/lsauthpts
Examples
$lsauthpts Compatibility
$lsauthpts -c -p 120.14.89.10 dce:compat
$lsauthpts -v Trusted services authentication methods for the partition: dce No discrepancies were found.
$lsauthpts -p sp3p2 -v Trusted services authentication methods for the partition: dce:compat lsauthpts: 0016-347 On sp3n13.abc.com the trusted services authentication methods are incorrectly set to "compat"
Purpose
lsauthts - Lists the active authentication methods for trusted services on a host.
Syntax
lsauthts [-h | -c]
Flags
Operands
None.
Description
The lsauthts command lists the authentication methods that are used by trusted services on the local host. Trusted services that support multiple methods will attempt to authenticate and authorize client requests using the methods in the order listed
Standard Input
The local settings are obtained from the /spdata/sys1/spsec/auth_methods file.
Standard Output
The long form of the output consists of a line for each authentication method that is active. The short form consists of one line with the methods separated by colons.
Standard Error
Output consists of error messages, when the command cannot complete successfully.
There are no unique consequences of command errors.
Exit Values
Security
The lsauthts command may be used by any user.
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 the PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/lsauthts
Examples
$lsauthts DCE
$lsauthts -c dce:compat
Purpose
lsfencevsd - Lists IBM Virtual Shared Disks that are fenced from access by nodes.
Syntax
lsfencevsd
Flags
None.
Operands
None.
Description
Use this command to display a map that shows which IBM Virtual Shared Disks are fenced from which nodes in the system or system partition.
Security
You must be in the AIX bin group to run this command.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/lsfencevsd
Related Information
Commands: fencevsd, unfencevsd
Examples
To display the map of fenced IBM Virtual Shared Disks in the system, enter:
lsfencevsd
The system displays a map similar to the following:
minor Fenced Nodes (13): 13 14 (14): 1 2
Purpose
lshacws - Gets the HACWS state of the control workstation.
Syntax
lshacws
Flags
None.
Operands
None.
Description
Use this command to print the current HACWS state of the control workstation. It prints to standard output a number string that indicates the HACWS state of the local host and whether the local host is part of an HACWS configuration.
This command 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 printed values and their defined HACWS state:
Prerequisite Information
Refer to PSSP: Administration Guide for information on the HACWS option.
Location
/usr/lpp/ssp/bin/lshacws
Related Information
Commands: sethacws
Subroutines: hacws_set, hacws_stat
Examples
The following lshacws command results indicate the node type:
lshacws Results: 32 - node is a backup and active control workstation Results: 16 - node is a backup and inactive control workstation Results: 2 - node is a primary and active control workstation Results: 1 - node is a primary and inactive control workstation Results: 0 - node is a control workstation but not an HACWS configuration Results: error occurs with exit value = 3 - node is not a control workstation
Purpose
lshsd - Displays configured hashed shared disks for a virtual shared disk and the characteristics.
Syntax
lshsd [-l | -s] [hsd_name ...]
Flags
Operands
Description
This command displays the configured hashed shared disks. If a list of hashed shared disks follow the flag then information about them is displayed. lshsd without any arguments or flag lists the names of all the hashed shared disks currently configured.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/lshsd
Related Information
Commands: cfghsd, ucfghsd, hsdatalst , updatehsd
Examples
lshsd
The system displays a message similar to the following:
hsd1 hsd2 hsd3 . . .
lshsd -l hsd1 hsd2
The system displays a message similar to the following:
HSD_name=hsd1 Stripe_size=32768 Hsd_minorno=1 numVsds=2
option=protectlvcb size_in_MB=40
vsd.rlv01
vsd.rlv02
HSD_name=hsd2 Stripe_size=32768 Hsd_minorno=1 numVsds=3
option=protectlvcb size_in_MB=40
vsd.rlv03
vsd.rlv04
vsd.rlv05
lshsd -s hsd1
The system displays a message similar to the following:
9 hsd parallelism
0 READ requests not at page boundary
0 WRITE requests not at page boundary
HSD_name=hsd1 Stripe_size=4096 HSD_minorno=1 numVSDs=2
option=protect_lvcb size_in_MB=40
number_read number_write vsd_name
16 16 vsdn01v1
16 16 vsdn02v1
Purpose
lskp - Lists Kerberos principals.
Syntax
lskp [ -h | -p | -s | -c | {name[.instance]|name. |.instance} ...]
Flags
Operands
Description
Use this command to list principals in the local Kerberos database, displaying for each the principal name and instance, the maximum ticket lifetime, and the expiration date. You can list the entire authentication database, an individual entry, all entries with a specified principal name, or all entries with a specified instance. Or you can list entries in different categories: all client (user) principals, all service principals, or all principals predefined by Kerberos.
Files
Standard Output
For each principal, the lskp command displays the principal identifier as name.instance (on a separate line if its length exceeds twenty characters), and the principal's attributes. The maximum ticket lifetime is the maximum period that a Ticket-Granting-Ticket issued to this principal will be valid. Any ticket lifetime up to this value can be requested using an option on the k4init command. The key version is an integer set to one when the principal is created and incremented each time the password is changed. The principal's expiration date is displayed in local time, based on the setting of the TZ environment variable.
Exit Values
Security
The lskp command can be run by the root user logged in on a Kerberos server host. It can be invoked indirectly as a Sysctl procedure by a Kerberos database administrator who has a valid ticket and is listed in the admin_acl.get file.
Location
/usr/kerberos/etc/lskp
Related Information
Commands: chkp, kadmin , kdb_edit, mkkp, rmkp , sysctl
Examples
lskp -p
You should receive output similar to the following:
krbtgt.ABC.DEF.GHI.COM
tkt-life: 30d key-vers: 1
expires: 2037-12-31 23:59
default tkt-life: 30d key-vers: 1
expires: 2037-12-31 23:59
changepw-kerberos tkt-life: 30d key-vers: 1
expires: 2037-12-31 23:59
K.M tkt-life: 30d key-vers: 1
expires: 2037-12-31 23:59
lskp joe.admin lisa
You should receive output similar to the following:
joe.admin tkt-life: 15d+08:46 key-vers: 1
expires: 2005-03-15 23:59
lisa tkt-life: 08:00 key-vers: 1
expires: 1997-06-09 23:59
Purpose
lsvsd - Displays configured virtual shared disks and their characteristics.
Syntax
lsvsd [-l] [-s] [-i] [ vsd_name...]
Flags
The state field can have one of the following values:
An asterisk (*) in front of any of these values indicates that the virtual shared disk has been fenced from this node.
This flag is not compatible with the -s flag.
The server_list of the virtual shared disk is listed.
The local logical operations are requests which were made by a process executing at the local node, whereas the remote logical operations were made by a process executing on a remote node. Client operations are those local logical requests that cannot be satisfied locally, and have to be sent to a remote node. Physical operations are those server operations which must be passed to the underlying disk device. Cache read hits are those server reads which do not require a device read, because the read operation was satisfied from the virtual shared disk cache.
This flag is not compatible with the -l flag.
Operands
Description
The lsvsd command displays information about virtual shared disks currently configured on the node on which the command is run. If a list of virtual shared disks follows the flags, information about those virtual shared disks is displayed. lsvsd with no arguments or flags lists the names of all the virtual shared disks currently configured on the node.
The lsvsd command displays information about both the configuration and the usage of a virtual shared disk.
You can use the System Management Interface Tool (SMIT) to run the lsvsd command. To use SMIT, enter:
smit vsd_mgmt
and select the Show All Managed Virtual Shared Disk Characteristics option.
Prerequisite Information
PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/lsvsd
Related Information
Commands: cfgvsd, ctlvsd, preparevsd, resumevsd, startvsd, stopvsd, suspendvsd, ucfgvsd, updatevsdnode, updatevsdtab
Examples
lsvsd
The system displays a message similar to the following:
vsd00 vsd01 . . .
lsvsd -l
The system displays a message similar to the following:
minor state server lv_major lv_minor vsd_name option size (MB) 83 STP -1 0 0 vsdn08v3 cache 20 84 STP -1 0 0 vsdn08v4 nocache 16
lsvsd -s
The system displays a message similar to the following:
lc-rd lc-wt rm-rd rm-wt c-rd c-wt p-rd p-wt h-rd br bw vsd_name
84 84 2858 169 0 0 348 253 2605 164 184 vsd.vsd1
0 0 0 0 0 0 0 0 0 0 0 vsd.rl01
0 0 0 0 0 0 0 0 0 0 0 vsd.rl02
node IP address 1 9.114.43.129 3 9.114.43.131 5 9.114.43.133 7 9.114.43.135 9 KLAPI[ 8] 10 9.114.43.138 11 KLAPI[ 10] 12 9.114.43.140 13 9.114.43.141 14 9.114.43.142 15 9.114.43.143 16 9.114.43.144
The following table spells out the names of the headers used in the
displays for the -l and -s options:
| Header | Meaning |
|---|---|
| minor | Virtual shared disk minor number |
| state | State of this virtual shared disk:active, stopped, suspended |
| server | Primary node for this virtual shared disk |
| lv major | Logical volume major number |
| lv minor | Logical volume minor number |
| vsd_name | Name of this virtual shared disk |
| option | Option:cache or nocache |
| lc-rd | Local logical reads |
| lc-wt | Local logical writes |
| rm-rd | Remote logical reads |
| rm-wt | Remote logical writes |
| c-rd | Client logical reads |
| c-wt | Client logical writes |
| p-rd | Physical reads |
| p-wt | Physical writes |
| h-rd | Reads from cache |
| br | Blocks read |
| bw | Blocks written |