Displays attributes and values for a resource or a resource class.
To display the attributes and values for a resource:
lsrsrc [-s "selection_string"] [ -a │ -N { node_file │ "-" } ] [ -A p │ d │ b ] [-p property] [ -l │ -i │ -t │ -d │ -D delimiter ] [-x] [-h] [-TV] [resource_class] [attr…]
lsrsrc -r [-s "selection_string"] [ -a │ -N { node_file │ "-" } ] [ -l │ -i │ -t │ -d │ -D delimiter ] [-x] [-h] [-TV] [resource_class]
To display the attributes and values for a resource class:
lsrsrc -c [ -A p │ d │ b ] [-p property] [ -l │ -i │ -t │ -d │ -D delimiter ] [-x] [-a] [-h] [-TV] resource_class [attr…]
lsrsrc -C domain_name… [ -A p │ d │ b ] [-p property] [ -l │ -i │ -t │ -d │ -D delimiter ] [-x] [-h] [-TV] resource_class [attr…]
To display a list of all of the resource classes:
lsrsrc
The lsrsrc command displays the persistent and dynamic attributes and their values for a resource or a resource class.
Instead of specifying multiple node names in selection_string, you can use the -N node_file flag to indicate that the node names are in a file. Use -N "-" to read the node names from standard input.
For best performance, specify either the -A p flag or only persistent attributes as parameters.
Specify the -r flag to display only the resource handles associated with the resources for the specified resource class.
To display a list of the attributes and values for a resource class, specify the -c flag.
By default, the resource attributes and values are displayed in long format. Use the -t, -d, or -D flag to display the resources in table format or delimiter-formatted output.
If Cluster Systems Management (CSM) is installed on your system, you can use CSM defined node groups as node name values to refer to more than one node. For information about working with CSM node groups and using the CSM nodegrp command, see the CSM: Administration Guide and the CSM: Command and Technical Reference.
The lsrsrc command does not list any attributes that have a datatype defined as ct_none (Quantum, for example). RMC does not return attribute values for attributes that are defined as Quantum. To list attribute definitions, use the lsrsrcdef command.
The CT_MANAGEMENT_SCOPE environment variable determines the scope of the cluster. If CT_MANAGEMENT_SCOPE is not set, management domain scope is chosen first (if a management domain exists), peer domain scope is chosen next (if a peer domain exists), and then local scope is chosen, until the scope is valid for the command. The command runs once for the first valid scope it finds. For example, if a management domain and a peer domain both exist and CT_MANAGEMENT_SCOPE is not set, this command applies to the management domain. If you want this command to apply to the peer domain, set CT_MANAGEMENT_SCOPE to 2.
lsrsrc -p 0x0a
-s 'Name == "testing"'
-s 'Name ?= "test"'
Only persistent attributes may be listed in a selection string. For information on how to specify selection strings, see the RSCT: Administration Guide .
The user needs read permission for the resource_class specified in lsrsrc to run lsrsrc. Permissions are specified in the access control list (ACL) file on the contacted system. See the RSCT: Administration Guide for information about the ACL file and how to modify it.
If this environment variable is not set, local scope is used.
This command is part of the Reliable Scalable Cluster Technology (RSCT) fileset for AIX®.
When the -h flag is specified, this command's usage statement is written to standard output. All verbose messages are written to standard output.
All trace messages are written to standard error.
lsrsrc
The
output will look like this: class_name
"IBM.Association"
"IBM.Condition"
'IBM.EventResponse"
"IBM.Host"
"IBM.Ethernet"
"IBM.TokenRing"
...
lsrsrc -s "NumProcessors == 4" -A p -p 0 IBM.Host
The
output will look like this: Resource Persistent Attributes for: IBM.Host
resource 1:
Name = "c175n05.ppd.pok.ibm.com"
ResourceHandle = "0x4008 0x0001 0x00000000 0x0069684c 0x0d7f55d5 0x0c32fde3"
Variety = 1
NodeList = {1}
NumProcessors = 4
RealMemSize = 1073696768
lsrsrc -s 'Name == "c175n05.ppd.pok.ibm.com"' -A d IBM.Host
The
output will look like this: Resource Dynamic Attributes for: IBM.Host
resource 1:
ProcRunQueue = 1.03347987093142
ProcSwapQueue = 1.00548852941929
TotalPgSpSize = 65536
TotalPgSpFree = 65131
PctTotalPgSpUsed = 0.61798095703125
PctTotalPgSpFree = 99.3820190429688
PctTotalTimeIdle = 0
PctTotalTimeWait = 51.5244382399734
PctTotalTimeUser = 12.8246006482343
PctTotalTimeKernel = 35.6509611117922
PctRealMemFree = 66
PctRealMemPinned = 4
RealMemFramesFree = 173361
VMPgInRate = 0
VMPgOutRate = 0
VMPgFaultRate = 0
...
lsrsrc IBM.Processor Name Variety ProcessorType
The
output will look like this: Resource Persistent Attributes for: IBM.Processor
resource 1:
Name = "proc3"
Variety = 1
ProcessorType = "PowerPC_604"
resource 2:
Name = "proc2"
Variety = 1
ProcessorType = "PowerPC_604"
resource 3:
Name = "proc1"
Variety = 1
ProcessorType = "PowerPC_604"
resource 4:
Name = "proc0"
Variety = 1
ProcessorType = "PowerPC_604"
lsrsrc -c -A b -p 0 IBM.Condition
The output
will look like this: Resource Class Persistent and Dynamic Attributes for: IBM.Condition
resource 1:
ResourceType = 0
Variety = 0
# common node file
#
node1.ibm.com main node
node2.ibm.com main node
node4.ibm.com backup node
node6.ibm.com backup node
#
as input, enter: lsrsrc -s "NumProcessors >= 4" -N /tmp/common/node_file -t IBM.Host \
Name NumProcessors
The output will look like this: Resource Persistent Attributes for IBM.Host
Name NumProcessors
"node1.ibm.com" 4
"node2.ibm.com" 4