Sunday, January 12, 2014

www.decsinfotech.com | www.clickuwant.com

AIX - lspath

To Check the missing or failed paths by issuing this command:

root@mohisrv:/root# lspath | awk '{print $1,$NF}' |sort |uniq -c
18 Enabled fscsi0
6 Enabled fscsi1
12 Failed fscsi1

If there are some failed paths, maybe you should try to re-enable them (quick and painless, can’t do no harm)  with this one-liner

root@mohisrv:/root# lspath|grep Failed | awk '{print "chpath -l "$2" -s enable -p "$3}'|ksh
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
paths Changed
root@lpar:/root# lspath | awk '{print $1" " $NF}' |sort |uniq -c
 18 Enabled fscsi0
 18 Enabled fscsi1

www.decsinfotech.com | www.clickuwant.com



HMC Command Line Help

Commands by Task:
Activate CoD Advanced Functions - chvet
Activate On/Off CoD resources - chcod
Activate partition - chsysstate
Activate system profile - chsysstate
Add memory to a partition - chhwres
Add processors to a partition - chhwres
Change the number of Utility CoD processors - chcod
Create LPAR - mksyscfg
Create LPAR profile - mksyscfg
Create system profile - mksyscfg
Deactivate all On/Off CoD processors - chcod
Deactivate all On/Off CoD resources - chcod
Delete LPAR - rmsyscfg
Delete LPAR profile - rmsyscfg
Delete system profile - rmsyscfg
Display activation code generation information - lsvet
Display activation history log - lsvet
Enter a Capacity on Demand (CoD) code - chcod
Fast power off the managed system - chsysstate
Get LPAR state - lssyscfg
Hard partition reset - chsysstate
List all partitions in a managed system - lssyscfg
List all systems managed by the HMC - lssyscfg
List CoD capacity information - lscod
List CoD code generation information - lscod
List CoD history log - lscod
List HMC remote access settings - lshmc
List HMC network settings - lshmc
List HMC VPD information - lshmc
List HMC version - lshmc
List I/O resources for a managed system - lshwres
List Licensed Internal Code levels - lslic
List LPAR profile properties - lssyscfg
List LPAR properties - lssyscfg
List managed system properties - lssyscfg
List memory resources - lshwres
List On/Off CoD billing information - lscod
List processor resources - lshwres
List reference code entries - lsrefcode
List system profile properties - lssyscfg
List virtual I/O resources for a managed system - lshwres
Modify LPAR profile properties - chsyscfg
Modify LPAR properties - chsyscfg
Modify managed system properties - chsyscfg
Modify system profile properties - chsyscfg
Move a physical I/O slot from one partition to another -                                                                             chhwres
Move memory from one partition to another - chhwres
Move processors from one partition to another - chhwres
Power off the managed system - chsysstate
Power on the managed system - chsysstate
Re-IPL the managed system - chsysstate
Remove a physical I/O slot from a partition - chhwres
Remove memory from a partition - chhwres
Remove processors from a partition - chhwres
Set a Utility CoD processor minute usage limit - chcod
Soft partition reset - chsysstate
Update Licensed Internal Code - updlic
Validate a system profile - chsysstate


Commands by Name:
asmmenu - launch the ASM interface

bkconsdata - back up critical HMC data

bkprofdata - back up profile data for the managed-system

chaccfg - change access control configuration
chcod - perform Capacity on Demand (CoD) operations
enter a CoD code
activate an amount of CoD resources
change the number of Utility CoD processors
deactivate all On/Off CoD processors
deactivate all On/Off CoD resources
set a Utility CoD processor minute usage limit

chhmc - change HMC configuration information

chhmcusr - change HMC user attribute

chhwres - change system memory and processor resources
add memory to a partition
add processors to a partition
move memory from one partition to another
move processors from one partition to another
remove memory from a partition
remove processors from a partition
chkmedia - check media readiness

chled - change LED

chlparutil - change utilization data collection settings

chsacfg - change Service Agent configuration

chsvcevent - update serviceable events on the HMC

chsyscfg - change system configuration
modify LPAR properties
modify LPAR profile properties
modify managed system properties
modify system profile properties
 
chsyspwd - change system password

chsysstate - change system state
activate partition
activate system profile
fast power off the managed system
hard partition reset
power off the managed system
power on the managed system
re-IPL the managed system
soft partition reset
chvet - activate Capacity on Demand advanced funtions
enter an activation code

cpdump - copy dumps

cpsysplan - copy system plan

defsysplanres - define system plan resource

deploysysplan - deploy system plan

dump - perform dump operation

getdump - get dump

getupgfiles - get upgrade files

hmcshutdown - shut down the HMC

hmcwin - proide screen capture on the HMC

installios - install the Virtual I/O Server

logssh - log ssh command usage

lpar_netboot - retrieve MAC address and physical location code from network adapters for a partition or instruct a partition to network boot

lpcfgop - perform a partition configuration image operation

lsaccfg - list access control configuration information

lscod - list Capacity on Demand resources for a managed system
list CoD capacity information
list CoD code generation information
list CoD history log
list On/Off CoD billing information
lsdump - lists dump information

lshmc - List HMC Configuration Information
list HMC remote access settings
list HMC network settings
list HMC VPD information
list HMC version
lshmcusr - list HMC user information

lshwinfo - list environmental information

lshwres - list the hardware resources of a managed system
determine DRC indexes for physical I/O slots
determine memory region size
list I/O resources for a managed system
list memory resources
list processor resources
list virtual I/O resources for a managed system
 
lsled - list LEDs

lslic - list Licensed Internal Code (LIC) levels
list LIC levels active on a managed system
list LIC levels available in a repository
 
lslock - list lock information

lslparutil - list utilization data

lsmediadev - list storage media devices

lsrefcode - list reference code entries for partitions or managed systems
list reference code entries for all partitions
list reference code entries for a managed system
 
lssacfg - list Service Agent configuration information

lssvcevents - list console or serviceable events

lssyscfg - list system configuration information
 
get LPAR state
list all partitions in a managed system
list all systems managed by the HMC
list LPAR profile properties
list LPAR properties
list managed system properties
list system profile properties
 
lssysconn - list system connections

lssysplan - list system plans

lssysplanres - list system plan resources
lvet - list Capacity on Demand advanced functions
display activation code generation information
display activation history log

migrcfg - migrate configuration

mkaccfg - create access control object

mahmcusr - create an HMC user

mksyscfg - create system configuration
create LPAR profile
create system profile
 
mksysconn - create system connection

mksysplan - make system plan file

mkvterm - open a virtual terminal session

monhmc - monitor HMC subsystems and system resources

pedbg - Product Engineering debug tools

pesh - provide PE Shell access

rmaccfg - remove access control object

rmhmcusr - remove an HMC user

rmlock - remove lock

rmlparutil - remove utilization data

rmprofdata - remove profile data

rmsyscfg - remove system configuration
delete LPAR
delete LPAR profile
delete system profile
 
rmsysconn - remove system connection

rmsysplan - remove system plan

rmsysplanres - remove system plan resource

rmvterm - close a vertual terminal session

rsthwres - restore hardware resources

rstprofdata - restore profile data

rstupgdata - restore upgrade data

saveupgdata - save upgrade data

sendfile - transfer file from the HMC to a remote system

startdump - start dump

updhmc - update code on the HMC

updlic- update Licensed Internal Code (LIC)
retrieve, install, activate updates
retrieve and install updates
remove the last update
change LIC update control to HMC
change LIC update control to operating system

viosvrcmd - issue virtual I/O server command


4.0 Using the Managed System


Powering On the Managed System
Use the chsysstate command to power on the managed system. This power on option is similar to a “White Button" power on. Enter the following:

chsysstate -r sys -m <managed system> -o on
Powering Off the Managed System
Use the chsysstate command to power off the managed system. This can be done in two ways.
To power off a managed system normally, type the following:
chsysstate -r sys -m <managed system> -o off
You can also perform a fast power off (operator panel function 8) of a managed system. To do this, type the following command:
chsysstate -r sys -m <managed system> -o off  --immed
Updating Licensed Internal Code
Use the updlic command to retrieve, install, and activate Licensed Internal Code on a managed system. Use the -q parameter to determine if the update is disruptive.
To determine if the latest CPC update from IBM Retain is disruptive:
updlic -m <managed system> -o a -t cpc -l latest -r ibmretain -q
To change LIC update control on the managed system from HMC to operating system:
updlic -m <managed system> -o o

Listing HMC Current Configuration
Use the lshmc command to list the current remote access settings, network settings, version, and Vital Product Data (VPD) information for the HMC.
To list the remote access settings for ssh, websm, and http:
lshmc -r
To list the HMC hostname and network IP address:
lshmc -n -F hostname,ipaddr
To list the HMC Vital Product Data (VPD) information:
lshmc -v
Display the HMC version information:
lshmc -V
Listing all Systems Managed by the HMC
Use the lssyscfg command to list system configuration and managed system MTMS information. To list the properties of all systems managed by this HMC, enter the following:
lssyscfg -r sys
To list only the user-defined names, model types, serial numbers, and states for all of the systems managed by this HMC, enter:
lssyscfg -r sys -F name,type_model,serial_num,state --header
Note that after executing this command, <type_model> concatenated with * then with <serial_num> represents the MODEL-TYPE*SERIAL, or MTMS, for the managed system.
Listing a Managed System's Properties
To list a specific managed system's properties, enter:
lssyscfg -r sys -m <managed system>


Modifying the Managed System Properties
Use the chsyscfg command to change the properties of a managed system. The following example shows how to change the managed system's user-defined name and power off policy:
chsyscfg -r sys -m <managed system> –i "new_name=newsys1,power_off_policy=0"
Valid attributes, specified with the –i flag, include:
new_name
power_on_side
power_off_policy
power_on_speed
service_lpar_id
power_on_speed_override
service_lpar_name

Instead of entering configuration information on the command line with the -i flag, the information can be placed in a file and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
Listing Reference Codes for a Managed System or Partition
Use the lsrefcode command to list SRC entries for a managed system or partition. Entries may be filtered by lpar name or lpar id.
To list the last 10 SRC entries for the managed system:
lsrefcode -m <managed system> -r sys -n 10
To list the current SRC entry for each partition on the managed system:
lsrefcode -m <managed system> -r lpar

Display the last 50 SRC entries for partition p1:
lsrefcode -m <managed system> -r lpar -n 50   --filter "lpar_names=p1"
Restarting the Managed System
To restart the managed system, enter:
chsysstate -r sys -m <managed system> -o off  --immed --restart

Listing Licensed Internal Code Levels for a Managed System
Use the lslic command to list the LIC levels (cpc or power) on a partition or managed system that have been installed, activated, and accepted. You may also list available levels in a repository.
To list current CPC LIC levels on a managed system:
lslic -m <managed system> -t cpc
To list available POWER LIC levels in a repository:
lslic -m <managed system> -t power -r <repository>
Listing Capacity on Demand Information for a Managed System
Use the lscod command to list memory and processor Capacity on Demand information for a managed system, including capacity, code generation, and CoD history logs for Capacity Upgrade on Demand (CUoD) and On/Off Capacity on Demand (OOCoD). More CoD operations are covered in 10.0 CLI: Performing Capacity on Demand (CoD) Operations.
To list On/Off CoD processor capacity information:
lscod -m <managed system> -t cap -r proc -c onoff
To list CUoD memory activation code generation information:
lscod -m <managed system> -t code -r mem -c cuod
To list the Capacity on Demand history log:
lscod -m <managed system> -t hist
To Display On/Off Capacity on Demand memory billing information:
lscod -m <managed system> -t bill -r mem -c onoff

9.0 Listing Hardware Resources

The lshwres command, which lists the hardware resources of a managed system, can be used to display I/O, virtual I/O, processor, and memory resources.
Listing I/O Resources for a Managed System
Use the following commands to list:
I/O units on the managed system
lshwres -m <managed system> -r io --rsubtype unit
I/O buses on the managed system
lshwres -m <managed system> -r io --rsubtype bus
I/O slots on the managed system
lshwres -m <managed system> -r io --rsubtype slot
All partitions participating in an I/O pool and all slots assigned to an I/O pool
lshwres -m <managed system> -r io --rsubtype iopool
Tagged I/O for i5/OS (OS/400) partitions
lshwres -m <managed system> -r io --rsubtype taggedio
Listing Processor Resources
Use the following commands to list processor information for:
The managed system
lshwres -m <managed system> -r proc --level sys
Partitions
lshwres -m <managed system> -r proc --level lpar
The shared pool
lshwres -m <managed system> -r proc --level pool

Listing Virtual I/O Resources for a Managed System
Use the following commands to list:
Virtual Ethernet adapters
lshwres -m <managed system> -r virtualio --rsubtype eth --level lpar
System level virtual Ethernet information
lshwres -m <managed system> -r virtualio --rsubtype eth --level sys
Virtual OptiConnect pool information
lshwres -m <managed system> -r virtualio --rsubtype virtualopti --level lpar
HSL OptiConnect pool information
lshwres -m <managed system> -r virtualio --rsubtype hslopti --level lpar
Virtual serial adapters
lshwres -m <managed system> -r virtualio --rsubtype serial --level lpar
Virtual serial servers with open connections
lshwres -m <managed system> -r virtualio --rsubtype serial --level openserial
Virtual SCSI adapters
lshwres -m <managed system> -r virtualio --rsubtype scsi --level lpar
Partition-level virtual slot information
lshwres -m <managed system> -r virtualio --rsubtype slot --level lpar
Virtual slot information
lshwres -m <managed system> -r virtualio --rsubtype slot --level slot
Listing Memory Resources
Use the following commands to list:
Memory information for a managed system
lshwres -m <managed system> -r mem --level sys
Memory information for partitions
lshwres -m <managed system> -r mem --level lpar



10.0 Performing Capacity on Demand (CoD) Operations

Entering a Capacity on Demand Code
To enter an CoD code:
chcod -o e -m <managed system> -k <CoD code>
Activating an Amount of On/Off CoD Resources
To activate an amount of On/Off CoD memory for a certain number of days:
chcod -m <managed system> -o a -c onoff -r mem -q <quantity of resources> -d <number of days>
Changing the Number of Utility CoD Processors
To decrease the number of Activated Utility CoD processors:
chcod -m <managed system> -o a -c utility -r proc -q <quantity of processors>
Deactivating all On/Off CoD Processors
To deactivate all On/Off CoD processors:
chcod -m <managed system> -o d -c onoff -r proc
Deactivating all On/Off CoD Resources
To deactivate all On/Off CoD resources:
chcod -m <managed system> -o d -c onoff -r mem
Setting a Utility CoD Processor Minute Usage Limit
To set a Utility CoD processor minute usage limit::
chcod -m <managed system> -o s -c utility -r proc -l <number of processor minutes>
Activating Capacity on Demand (CoD) Advanced Functions
CoD advanced functions include Advanced POWER Virtualization and Endterprise Enablement. CoD advanced functions are sometimes referred to as Virtualization Engine systems technologies. To enter an activation code:
chvet -m <managed system> -o e -k <activation code>
Displaying Activation Code Generation Information
To display activation code generation information:
lsvet -m <managed system> -t code
Displaying the Activation History Log
To display activation history log:
lsvet -m <managed system> -t hist

5.0 Working with LPARs

Creating LPARs
Use the mksyscfg command to create a partition.
The following is an example of how to create an AIX/Linux partition:
mksyscfg -r lpar -m <managed system> –i "lpar_id=2,name=aixlinux_lpar2,profile_name=prof1, lpar_type=aixlinux,boot_mode=norm, desired_procs=1,min_procs=1, max_procs=1,min_proc_units=0.1, desired_proc_units=0.5,max_proc_units=0.5, proc_type=shared,sharing_mode=cap,desired_mem=400, min_mem=400, max_mem=400,auto_start=1, power_ctrl_lpar_ids=0,io_slots=553713666/65535/1"
The following is an example of how to create an i5/OS (OS/400) partition:
mksyscfg -r lpar -m <managed system> –i "lpar_id=3,name=os400_lpar3,profile_name=prof1, lpar_type=os400, desired_procs=1,min_procs=1,max_procs=1, min_proc_units=0.1,desired_proc_units=0.5, max_proc_units=0.5,proc_type=shared, sharing_mode=cap,desired_mem=400, min_mem=400, max_mem=400,auto_start=1,power_ctrl_lpar_ids=0, io_slots=553713699/65535/1, load_source_slot=553713699, console_slot=553713699,min_interactive=0, desired_interactive=0, max_interactive=0"
Valid attributes, specified with the –i flag, include:
name
desired_proc_units
min_proc_units
lpar_id
max_proc_units
ecs_slot
profile_name
lpar_io_pool_ids
sni_windows
lpar_type
io_slots
alt_console_slot
cluster_id
boot_mode
sni_device_ids
sharing_mode
max_virtual_slots
console_slot
desired_procs
auto_start
sni_config_mode
min_procs
power_ctrl_lpar_ids
alt_load_source_slot
max_procs
virtual_opti_pool_id
virtual_serial_adapters
desired_mem
hsl_opti_pool_id
load_source_slot
min_mem
min_interactive
virtual_scsi_adapters
max_mem
desired_interactive
uncap_weight
proc_type
max_interactive
virtual_eth_adapters
lnstead of entering configuration information on the command line with the -i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
Listing All Partitions in a Managed System
Use the lssyscfg command to list all partitions in a managed system. To do this, enter:
lssyscfg -r lpar -m <managed system>
To list only the names, IDs, and states of all partitions in a managed system, enter:
lssyscfg -r lpar -m <managed system> -F name,lpar_id,state --header
Listing LPAR Properties
Use the lssyscfg command to list the properties of a specific partition. Type the following:
lssyscfg -r lpar -m <managed system> --filter "lpar_ids=<partition ID>"
Note that the partition name can be specified instead of the partition ID by using the lpar_names filter in place of the lpar_ids filter. Also, more than one partition may be specified in the filter list.
For information on using the lshwres command to list a partition's I/O, virtual I/O, processor, and memory resources, see Listing Hardware Resources.
Getting the LPAR State
Use the lssyscfg command to display the state of a partition. Type the following:
lssyscfg -r lpar -m <managed system> --filter "lpar_names=<partition name>" -F state
Note that the partition ID can be specified instead of the partition name by using the lpar_ids filter in place
of the lpar_names filter. Also, more than one partition may be specified in the filter list.

Modifying LPAR Properties
Use the chsyscfg command to modify the properties of a partition. The following example shows how to change a partition’s cluster ID:
chsyscfg -r lpar -m <managed system> -i "lpar_id=l,cluster_id=3"
Valid attributes, specified with the –i flag, are:
new_name
name | lpar_id
default_profile
cluster_id
Instead of entering configuration information on the command line with the -i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
Activating a Partition
Use the chsysstate command to activate a partition. Type the following:
chsysstate -r lpar -m <managed system> -o on -n <partition name> -f <partition profile name>
The partition ID can be specified instead of the partition name by using the --id parameter instead of the -n parameter.
Using a Soft Partition Reset
Use the chsysstate command to perform a soft reset of a partition. Type the following:
chsysstate -r lpar -m <managed system> -o reset -n <partition name>
The partition ID can be specified instead of the partition name by using the --id parameter instead of the -n parameter.
Using a Hard Partition Reset
Use the chsysstate command to perform a hard reset of a partition. Type the following:
chsysstate -r lpar -m <managed system> -o off --id <partition ID>
The partition name can be specified instead of the partition ID by using the -n parameter instead of the --id parameter.
Deleting an LPAR
Use the rmsyscfg command to remove a partition. Type the following:

rmsyscfg -r lpar -m <managed system> -n <partition name>
This command removes the specified partition and all of its associated partition profiles from the specified managed system. The partition’s profiles are also removed from any system profiles that contain them.
The partition ID can be specified instead of the partition name by using the --id parameter instead of the -n parameter.

7.0 Working with LPAR Profiles

Creating an LPAR Profile
Use the mksyscfg command to create a partition profile. The following is an example of how to create a partition profile:
mksyscfg -r prof -m <managed system> -i
"name=prof3,lpar_id=2,boot_mode=norm, sfp_surveillance=1,desired_procs=2, min_procs=1,max_procs=2,min_proc_units=0.1, desired_proc_units=0.5,max_proc_units=0.5, proc_type=shared,sharing_mode=cap, desired_mem=400,min_mem=400,max_mem=400, auto_ipl=1,power_ctrl_lpar_ids=0, io_slots=553713666/65535/1"
Valid attributes, specified with the -i flag, include:
name
lpar_id | lpar_name
power_ctrl_lpar_ids
desired_procs
min_procs
max_procs
desired_mem
min_mem
max_mem
proc_type
uncap_weight
sharing_mode
load_source_slot
alt_load_source_slot
console_slot
alt_console_slot
ecs_slot
min_proc_units
desired_proc_units
max_proc_units
lpar_io_pool_ids
io_slots
boot_mode
sfp_surveillance
sni_windows
virtual_opti_pool_id
hsl_opti_pool_id
min_interactive
desired_interactive
max_interactive
max_virtual_slots
virtual_eth_adapters
virtual_scsi_adapters
virtual_serial_adapters
sni_config_mode
sni_device_ids
auto_ipl


The profile name (name) and the partition (lpar_id or lpar_name) must be specified. Instead of entering configuration information on the command line with the -i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
Listing LPAR Profile Properties
Use the lssyscfg command to list a partition profile. Type the following:
lssyscfg -r prof -m <managed system> -–filter
"lpar_names=<partition name>, profile_names=<profile name>"
Use the --filter parameter to specify the partition for which partition profiles are to be listed, and to specify which profile names to list. While the filter can only specify a single partition, it can specify multiple profile names for that partition.
Note that the partition ID can be specified instead of the partition name by using the lpar_ids filter in place of the lpar_names filter.
Modifying LPAR Profile Properties
Use the chsyscfg command to modify a partition profile’s properties. The following example shows how to change prof1's memory amounts:
chsyscfg -r prof -m <managed system> -i
"name=prof1,lpar_name=lpar3,min_mem=256,
max_mem=512,desired_mem=512"
Valid attributes, specified with the -i flag, include:
name
lpar_name | lpar_id
new_name
desired_procs
min_procs
max_procs
desired_mem
min_mem
max_mem
proc_type
uncap_weight
sharing_mode
load_source_slot
alt_load_source_slot
console_slot
alt_console_slot
ecs_slot
min_proc_units
desired_proc_units
max_proc_units
lpar_io_pool_ids
io_slots
boot_mode
sfp_surveillance
sni_windows
virtual_opti_pool_id
hsl_opti_pool_id
min_interactive
desired_interactive
max_interactive
max_virtual_slots
virtual_eth_adapters
virtual_scsi_adapters
virtual_serial_adapters
sni_config_mode
sni_device_ids
auto_ipl
power_ctrl_lpar_ids
Instead of entering configuration information on the command line with the -i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
Deleting an LPAR Profile
Use the rmsyscfg command to remove a partition profile. Type the following:
rmsyscfg -r prof -m <managed system> -n <profile name> -p <partition name>
The partition ID can be specified instead of the partition name by using the --id parameter in place of the -p parameter


8.0 Working with System Profiles

Creating a System Profile
Use the mksyscfg command to create a system profile. In the following example, the user is making a system profile named sysprof1, with partition profile prof1 for partition lpar1 and partition profile prof1 for partition lpar2.
mksyscfg -r sysprof -m <managed system> –i "name=sysprof1,\"lpar_names=lpar1,lpar2\", \"profile_names=prof1,prof1\""
Partition IDs can be specified instead of partition names when creating a system profile. This is done by using the lpar_ids attribute instead of the lpar_names attribute.
Instead of entering configuration information on the command line with the-i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
Activating a System Profile
Use the chsysstate command to activate a system profile. Type the following:
chsysstate -r sysprof -m <managed system> -o on -n <system profile name>
Validating a System Profile
Use the chsysstate command to validate a system profile. Type the following:
chsysstate -r sysprof -m <managed system> -n <system profile name> - -test
To validate a system profile, then activate that system profile if the validation is successful, type the following:
chsysstate -r sysprof -m <managed system> -o on -n <system profile name> - -test
Deleting a System Profile
Use the rmsyscfg command to remove a system profile. Type the following:
rmsyscfg -r sysprof -m <managed system> -n <system profile name>
Listing System Profile Properties
Use the lssyscfg command to list a system profile’s properties. Type the following:
lssyscfg -r sysprof -m <managed system> --filter "profile_names=<system profile name>"
To list all system profiles for the managed system, type the following:

lssyscfg -r sysprof -m <managed system>
Modifying System Profile Properties
Use the chsyscfg command to modify system profile properties. In the following example, the user is adding profiles prof1 for partition lpar3 and prof2 for partition lpar4 to system profile sysprof1:
chsyscfg -r sysprof -m <managed system> -i "name=sysprof1,\"lpar_names+=lpar3,lpar4\",
\"profile_names+=prof1,prof2\""
Valid attributes, specified with the –i flag, include:
new_name
profile_names
lpar_names | lpar_ids
name
Instead of entering configuration information on the command line with the-i flag, the information can instead be placed in a file, and the filename specified with the -f flag.
For more information about the valid attributes listed in this command example, refer to the Command Attributes table.
6.0 Performing DLPAR Operations

Use the chhwres command to to perform dynamic logical partitioning (DLPAR) operations on running partitions. DLPAR operations can be performed for memory, physical I/O slots, and processor resources.
Memory
Memory can be dynamically added to a partition, removed from a partition, or moved from one partition to another. In the following commands, the quantity of memory to be added, removed, or moved must be specified with the -q flag. This quantity is in megabytes, and must be a multiple of the memory region size for the managed system.
Determining Memory Region Size
To see what the memory region size is for the managed system, enter this command:
lshwres -r mem -m <managed system> –-level sys -F mem_region_size
The value returned is the memory region size in megabytes.
Adding Memory to a Partition
To add memory to a partition, enter this command:
chhwres -r mem -m <managed system> -o a -p <partition name> -q <quantity>
Removing Memory from a Partition
To remove memory from a partition, enter this command:
chhwres -r mem -m <managed system> -o r -p <partition name> -q <quantity>
Moving Memory from One Partition to Another
To move memory from one partition to another partition, enter this command:
chhwres -r mem -m <managed system> -o m -p <source partition name> -t <target partition name> -q <quantity>
Physical I/O Slots
A physical I/O slot can be dynamically added to a partition, removed from a partition, or moved from one partition to another. In the following commands, the DRC index of the I/O slot to be added, removed, or moved must be specified with the -s flag.
Note that only one physical I/O slot can be added, removed, or moved at a time.
Determining DRC Indexes for Physical I/O Slots
To see the DRC indexes for all of the physical I/O slots that are on the managed system, enter this command:
lshwres -r io --rsubtype slot -m <managed system>
The DRC index for each slot is returned via the drc_index attribute.
Adding a Physical I/O Slot to a Partition
To add a physical I/O slot to a partition, enter this command:
chhwres -r io -m <managed system> -o a -p <partition name> -s <DRC index>
Removing a Physical I/O Slot from a Partition
To remove a physical I/O slot from a partition, enter this command:
chhwres -r io -m <managed system> -o r -p <partition name> -s <DRC index>
Moving a Physical I/O Slot from One Partition to Another
To move a physical I/O slot from one partition to another partition, enter this command:
chhwres -r io -m <managed system> -o m -p <source partition name> -t <target partition name> -s <DRC index>

Processors
Processing resources can be dynamically added to a partition, removed from a partition, or moved from one partition to another. These processing resources depend on the type of processors used by the partitions:
For partitions using dedicated processors, processing resources are dedicated processors.
For partitions using shared processors, processing resources include virtual processors and processing units.
Note: Currently, AIX/Linux partitions using shared processors do not support processor DLPAR operations.
In the following commands, for partitions using dedicated processors, the quantity of processors to be added, removed, or moved are specified with the --procs flag.
For partitions using shared processors, the quantity of virtual processors to be added, removed, or moved are also specified with the --procs flag. The quantity of processing units to be added, removed, or moved are specified with the --procunits flag. Both of these flags can be specified, but only one is required.
Note that the quantity of processing units must be multiplied by 100 for the command. For example, to add, remove, or move .5 processing units, specify a quantity of 50.
Adding Processors to a Partition
To add processors to a partition using dedicated processors, enter this command:
chhwres -r proc -m <managed system> -o a -p <partition name> --procs <quantity>
To add processors to a partition using shared processors, enter this command:
chhwres -r proc -m <managed system> -o a -p <partition name> --procs <quantity> --procunits <quantity>
Removing Processors from a Partition
To remove processors from a partition using dedicated processors, enter this command:
chhwres -r proc -m <managed system> -o r -p <partition name> --procs <quantity>
To remove processors from a partition using shared processors, enter this command:
chhwres -r proc -m <managed system> -o r -p <partition name> --procs <quantity> --procunits <quantity>
Moving Processors from One Partition to Another
To move processors from a partition using dedicated processors to another, enter this command:
chhwres -r proc -m <managed system> -o m -p <source partition name> -t <target partition name> --procs <quantity>
To move processors from a partition using shared processors to another, enter this command:
chhwres -r proc -m <managed system> -o m -p <source partition name> -t <target partition name> --procs <quantity> --procunits <quantity>
Processing resources can also be moved between partitions using dedicated processors and partitions using shared processors. To move processing resources from a partition using dedicated processors to a partition using shared processors, specify the quantity of processors using the --procs flag. This quantity is converted to processing units (by multiplying the quantity by 100) by the HMC for the target partition.
To move processing resources from a partition using shared processors to a partition using dedicated processors, specify the quantity of processing units (which must be a multiple of 100) using the --procunits flag. This quantity is converted to processors (by dividing the quantity by 100) by the HMC for the target partition. The --procs flag cannot be specified in this case.

www.decsinfotech.com | www.clickuwant.com


#Display all LPAR's
lslpars
lshmc –n (lists dynamic IP addresses served by HMC)
lssyscfg –r sys –F name,ipaddr (lists managed system attributes)
lssysconn –r sys (lists attributes of managed systems)
lssysconn –r all (lists all known managed systems with attributes)
rmsysconn –o remove –ip <ipaddr from lssysconn

lspartition -dlpar

# Display I/O locations
lshwres -r io --rsubtype slot -m Server-9117-570-SN10CC2BE --filter "lpar_names=AHE_NBAXA374"

# Display available CPU units:
lshwres -r proc -m Server-9117-570-SN100C94F --level sys

# Display status of managed system
lsled -m Server-9117-570-SN100C90F -r sa -t phys

# Display status of LPAR's on managed system
lsrefcode -r lpar -m "Server-9117-570-SN104635C"
lsled -m Server-9117-570-SN100C90F -r sa -t virtuallpar
get_cec_state -m "NGPS07 101EDFC"

# Display ip address of Managed system as it relates to HMC
lssyscfg -r sys -F ipaddr name

# Display lpar & its state.
lssyscfg -r lpar -m Server-9117-570-SN100C94F -F name,state

# Open terminal session to LPAR
mkvterm -m Server-9117-570-SN100C90F -p AHE_NBAXA530
mkvterm -m "7040-681*027222A" -p ODCS_NBAXA002

**** Hit enter, then ~. to disconnect from vterm ****

# Close open terminal session to LPAR
rmvterm -m Server-9117-570-SN100C90F -p AHE_NBAXA530
rmvterm -m "7040-681*027222A" -p ODCS_NBAXA002

# Clear up dynamic lpar misconfigurations
rsthwres -r proc -m Server-9117-570-SN1046D7E

# AIX shutdown LPAR
chsysstate -m Server-9117-570-SN100C90F -r lpar -o osshutdown -n AHE_NBAXA530 --immed
chsysstate -m 10A42ED AHEPS24 -r lpar -o osshutdown -n AHE_NBAXA221 --immed

# Power off managed system
chsysstate -n NGPS07 101EDFC -r sys -o off

# Power off partition
chsysstate -m Server-9117-570-SN100C90F -r lpar -n AHE_NBAXA530 -o shutdown
chsysstate -m 10A534D AHEPS35 -r lpar -n AHE_NBAXA535 -o shutdown

# Power on all LPAR's on frame:
for i in `lsled -m Server-9117-570-SN103D7EA -r sa -t virtuallpar|cut -c 21-33|grep COKE`; do
chsysstate -m Server-9117-570-SN103D7EA -r lpar -o shutdown --immed -n $i
sleep 5
done

# Power on managed system
chsysstate -m Server-9117-570-SN100C90F -r sys -o on
chsysstate -m 10A42ED AHEPS24 -r lpar -o on

# Power on LPAR, profile
chsysstate -m Server-9117-570-SN100C90F -r lpar -o on -n AHE_NBAXA528 -f AHE_NBAXA528_PROFILE
chsysstate -r sysprof -m 10A42ED AHEPS24 -o on -n AHE_NBAXA221 -f AHE_NBAXA221
chsysstate -n NGPS07 101EDFC -r sys -o on -c lpar -b std

# Power on all LPAR's on frame:
for i in `lsled -m Server-9117-570-SN103D8EA -r sa -t virtuallpar|cut -c 21-33|grep COKE`; do
chsysstate -m Server-9117-570-SN103D8EA -r lpar -o on -n $i -f $i\_PROFILE
sleep 30
done

# Power off lpar's all frame's now ...
for host in `lssyscfg -r sys -F name`; do
for lpar in `lsrefcode -r lpar -m $host -F lpar_name |grep AHE`; do
chsysstate -m $host -r lpar -o shutdown --immed -n $lpar
sleep 2
done
done

# Power on all lpar's all frames to SMS
for host in `lssyscfg -r sys -F name`; do
for lpar in `lsrefcode -r lpar -m $host -F lpar_name |grep AHE`; do
chsysstate -m $host -r lpar -o on -b sms -n $lpar -f $lpar\_PROFILE
sleep 2
done
done

# Delete all partitions from server(ignoring full system config profile)
for i in `lsled -m Server-9117-570-SN103DCEA -r sa -t virtuallpar|cut -c 21-33|grep COKE`; do
rmsyscfg -r lpar -m Server-9117-570-SN103DCEA -n $i
sleep 5
done

# Display Managed System attributes:
lssyscfg -r sys -m 'Server-9117-570-SN100C90F'

# Display LPAR attributes:
lssyscfg -r lpar -m 'Server-9117-570-SN100C90F'

# Display HW drawers
lshwres -r io --rsubtype unit -m 'Server-9117-570-SN100C90F'
lshwres -m '106D90C AHEPS16' -r slot

# Display DRC index and CEC NAME
lshwres -r io --rsubtype slot -m 'Server-9117-570-SN100C90F' -F drc_index,drc_name|grep E6A

# Create LPAR profile #1
mksyscfg -r lpar -m Server-9117-570-SN103DCEA -i \ "name=COKE_NBAXA550,profile_name=COKE_NBAXA550_PROFILE,lpar_env=aixlinux,min_mem=12288, \
desired_mem=12288,max_mem=49152,proc_mode=ded,min_procs=2,desired_procs=2,max_procs=16, \
conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \
\"io_slots=21010002//1,21010001//1,2101000C//1,21030013//1,21030018//1,21010017//1\""

# Create LPAR profile #2
mksyscfg -r lpar -m Server-9117-570-SN103DCEA -i \ "name=COKE_NBAXA552,profile_name=COKE_NBAXA552_PROFILE,lpar_env=aixlinux,min_mem=12288, \
desired_mem=12288,max_mem=49152,proc_mode=ded,min_procs=2,desired_procs=2,max_procs=16, \
conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \ \"io_slots=21020002//1,21010003//1,2101000E//1,21030012//1,21020017//1,21030017//1\""

# Create LPAR profile #3
mksyscfg -r lpar -m Server-9117-570-SN103DCEA -i \ "name=COKE_NBAXA556,profile_name=COKE_NBAXA556_PROFILE,lpar_env=aixlinux,min_mem=12288, \ desired_mem=12288,max_mem=49152,proc_mode=ded,min_procs=2,desired_procs=2,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \ \"io_slots=2101000A//1,2102000A//1,2103000A//1,21010019//1,21020019//1,21030019//1\""

# Create LPAR profile #4
mksyscfg -r lpar -m Server-9117-570-SN103D7EA -i \ "name=COKE_NBAXA557,profile_name=COKE_NBAXA557_PROFILE,lpar_env=aixlinux,min_mem=12288, \ desired_mem=12288,max_mem=49152,proc_mode=ded,min_procs=2,desired_procs=2,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \
\"io_slots=2101001A//1,2102001A//1,2104001A//1,2101000B//1,2102000B//1,2104000B//1\""

# Create LPAR profile #5
mksyscfg -r lpar -m Server-9117-570-SN100C90F -i \
"name=AHE_NBAXA542,profile_name=AHE_NBAXA542_PROFILE,lpar_env=aixlinux,min_mem=4096, \ desired_mem=4096,max_mem=49152,proc_mode=ded,min_procs=1,desired_procs=1,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \ \"io_slots=21040002//1,21040017//1,21010014//1,21020014//1,21030014//1,2103000F//1\""

# Create LPAR profile #6
mksyscfg -r lpar -m Server-9117-570-SN100C90F -i \
"name=AHE_NBAXA543,profile_name=AHE_NBAXA543_PROFILE,lpar_env=aixlinux,min_mem=4096, \ desired_mem=4096,max_mem=49152,proc_mode=ded,min_procs=1,desired_procs=1,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \ \"io_slots=21010015//1,21020015//1,21040015//1,21040010//1,21040003//1,21040018//1\""

# Create LPAR profile #7
mksyscfg -r lpar -m Server-9117-570-SN100C90F -i \
"name=AHE_NBAXA544,profile_name=AHE_NBAXA544_PROFILE,lpar_env=aixlinux,min_mem=4096, \ desired_mem=4096,max_mem=49152,proc_mode=ded,min_procs=1,desired_procs=1,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \ \"io_slots=2101000F//1,2102000F//1,21030002//1,21020012//1,21010011//1,21010016//1\""

# Create LPAR profile #8
mksyscfg -r lpar -m Server-9117-570-SN103DCEA -i \ "name=COKE_NBAXAXXX,profile_name=COKE_NBAXAXXX_PROFILE,lpar_env=aixlinux,min_mem=12288, \ desired_mem=12288,max_mem=49152,proc_mode=ded,min_procs=2,desired_procs=2,max_procs=16, \ conn_monitoring=0,auto_start=0,sharing_mode=keep_idle_procs,boot_mode=norm, \
\"io_slots=21010010//1,21020010//1,21030003//1,21010012//1,21010013//1,21010018//1\""

# Modify existing LPAR name
chsyscfg -r lpar -m Server-9117-570-SN100C90F -i "name=AHE_NBAXA530,
new_name=AHE_LPAR3"

# Modify existing Partition profile name
chsyscfg -r prof -m Server-9117-570-SN10462DC -i "name=BBSUB_NBAXA679_PROFILE,lpar_name=BBSUB_NBAXA679,new_name=BBSUB_NBAXA671_PROFILE"

# Modify existing Partition profile configuration:
chsyscfg -r prof -m Server-9117-570-SN10E08BE -i "name=COKE_NBAXA553_PROFILE,lpar_name=COKE_NBAXA553,min_mem=12288,desired_mem=12288"
# Add Adapter to Partition profile
chsyscfg -m Server-9117-570-SN104A2F0 -r prof -i "name=USLXVIOD4_PROFILE,lpar_name=USLXVIOD4,io_slots+=2101000A//1"
# Create partition using VIO SCSI/Ethernet:
mksyscfg -m Server-9117-570-SN104A2F0 -r lpar -i "profile_name=USLXSWU25_PROFILE,name=USLXSWU25,lpar_env=aixlinux,all_resources=0,min_mem=2048,desired_mem=4096,max_mem=4096,min_num_huge_pages=0,desired_num_huge_pages=0,max_num_huge_pages=0,proc_mode=shared,min_proc_units= 0.2,desired_proc_units=0.4,max_proc_units=0.6,min_procs=1,desired_procs=1,max_procs=1,sharing_mode=cap,uncap_weight=0,io_slots=none,lpar_io_pool_ids=none,max_virtual_slots=100,\"virtual_scsi_adapters=74/client/5/USLXVIOD4/74/1,44/client/3/USLXVIOD2/44/1\",virtual_eth_adapters=20/0/101//0/1,hca_adapters=none,boot_mode=norm,conn_monitoring=0,auto_start=0,power_ctrl_lpar_ids=none,work_group_id=none,redundant_err_path_reporting=0"
# Modify existing partition definition
chsyscfg -r prof -m Server-9117-570-SN100C90F -i "conn_monitoring=0,auto_start=0,name=AHE_NBAXA543_PROFILE,lpar_name=AHE_NBAXA543"
# VIO configuration example for SCSI adapter modification:
chsyscfg -m Server-9117-570-SN104A2F0 -r prof -i "name=USLXSWU24_PROFILE,lpar _name=USLXSWU24,\"virtual_scsi_adapters=74/client/5/USLXVIOD4/74/1,44/client/3/USLXVIOD2/44 /1\""
Legend
Blue: Power5
Red: Power4

www.decsinfotech.com | www.clickuwant.com

AIX Devices

List all devices on a system
lsdev

List all disk devices on a system (Some other devices are: adapter,driver, logical volume, processor)
lsdev -Cc disk

To verify the processor capacity
prtconf -c (64bit/32bit)

List all customized (existing) device classes (-P for complete list)
lsdev -C -r class

Remove hdisk5
rmdev -dl hdisk5

Get device address of hdisk1
getconf DISK DEVNAME hdisk1 or bootinfo -o hdisk1

Get the size (in MB) of hdisk1
getconf DISK SIZE hdisk1 or bootinfo -s hdisk1

Find the slot of a PCI Ethernet adapter
lsslot -c pci -l ent0

Find the (virtual) location of an Ethernet adapter
lscfg -l ent1

Find the location codes of all devices in the system
lscfg

List all MPIO paths for hdisk0
lspath -l hdisk0

Find the WWN of the fcs0 HBA adapter
lscfg -vl fcs0 |grep Network

Temporarily change console output to /console.out
swcons /console.out (Use swcons to change back.)

To Identify the Parent Device
lsdev -Cc disk -l hdisk1 -F parent

To Identify the Predefined Device Line number
lsdev -Cc disk -l hdisk28 -F PdDvLn

To Check the device status
lsdev -Cc disk -l hdisk1 -S A -F status

To get information about dar1 devices
odmget -q 'name = dar1 AND attribute = all_controller' CuAt
odmget -q 'PdDvLn = disk/fdar/array' HACMPdisktype
odmget -q 'name = hdisk7 AND PdDvLn = disk/fdar/array' CuDv

To Remove Devices
rmdev -l fcs1 (or) rmdev -l fcs1 -R (along with all the child devices)

Command to extract snap.pax.z
zcat ../snap.pax.Z |pax -rf -

To Check no of processors on the system
lscfg |grep proc

To know the parent devices
server1: lsdev -Cl hdisk0 -F parent
scsi0
server1: lsdev -Cl scsi0 -F parent
pci12
server1: lsdev -Cl pci12 -F parent
pci3
server1: lsdev -Cl pci3 -F parent
sysplanar0

To lists devices owned by an adapter
lsdev -p scsi0

www.decsinfotech.com | www.clickuwant.com


1. HMC Version
hscroot@hmc> lshmc -V
Version: 3
Release: 3.2
HMC Build level 20040827.1
2. Network configuration of the HMC
hscroot@hmc> lshmc -n
3. Reboot the HMC
power4 + power5/6/7:
hscroot@hmc> hmcshutdown -t now -r
4. How to change the HMC password (of user hscroot)
power4 + power5/6/7:
hscroot@hmc> chhmcusr -u hscroot -t passwd
Enter the new password:
Retype the new password:
5. Show Available Filesystem Space
power5/6/7:
hscroot@hmc> monhmc -r disk -n 0
Filesystem
1K-blocks
Used Available Use% Mounted on
/dev/sda2
16121184
4958484 10343788 33% /
udev
517300
156
517144
1% /dev
/dev/sda3
6040320
1341736
4391744 24% /var
/dev/sda7
8056524
154132
7493140
3% /dump
/dev/sda8
38669964
203056 36502564
1% /extra
It's just the same as you would expect from the UNIX command df.
LPAR Management: Status Information
1. LPAR Status
That's how you get an overview of all systems controlled by your HMC:
power4:
hscroot@hmc> lslpars
power5/6/7:
hscroot@hmc> lssyscfg -r sys -F name:serial_num:state
pserver1:656D24A:Operating
pserver2:656FFFF:Operating
The format string 'lpar_id:name:serial_num:state' also tells you the serial number of the systems. You can omit the field
'serial_num' if you don't need to know.
However, for every system from the list above you get the LPAR overview as shown below:
hscroot@hmc> lssyscfg -m pserver -r lpar -F name:state
Example:
hscroot@hmc> lssyscfg -m pserver1 -r lpar -F name:state
mylpar1:Running
mylpar2:Running
mylpar3:Not Activated
Don't know where to start? Find the managed system to an LPAR with a query:
hscroot@hmc> for m in $(lssyscfg -r sys -F name); do echo $m ; lssyscfg -r lpar -m $m -F name:stat
2. Show Status and LED/LCD Display of an LPAR
power4:
hscroot@hmc> lssyscfg -r lpar -m pserver -n mylpar
power5/6/7:
hscroot@hmc> lsrefcode -m pserver -r lpar --filter "lpar_names=mylpar" -F lpar_name:refcode
You can even see the history of LED codes. Just use -n <NUM> for the last NUM codes. For example, if you want to see the last 5
LED codes of an LPAR type
hscroot@hmc> lsrefcode -m pserver -r lpar --filter "lpar_names=mylpar"
mylpar:
mylpar:0c33
mylpar:
mylpar:0539
mylpar:0538
-n 5 -F lpar_name:refcode
... and for the status LEDs:
hscroot@hmc> lsled -m pserver -r sa -t virtuallpar --filter ""lpar_names=mylpar""
3. Show Status and LED/LCD Display of a Systems Running in FullPartitionMode
power4:
hscroot@hmc> lssyscfg -r sys -n pserver
4. Overview LPAR IDs
power5/6/7:
hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:serial_num:state | sort -n
1:vioserver1:Running
2:vioserver2:Running
3:mylpar1:Not Activated
4:mylpar2:Running
5:mylpar3:Running
6:mylpar4:Running
7:mylpar5:Running
8:mylpar6:Running
9:mylpar7:Running
10:mylpar8:Not Activated
5. Overview Connection State
Are all service processors connected to my HMC?
hscroot@hmc> lssysconn -r all -F type_model_serial_num:ipaddr:state | sort
9117-570*65AE18C:172.16.255.253:Connected
9117-570*65AE18C:172.16.254.255:Connected
9117-570*65AE2AC:172.16.255.254:Connected
9117-570*65AE2AC:172.16.254.254:Connected
9117-570*650D70D:172.16.255.252:Connected
9117-570*650D70D:172.16.253.255:Connected
9117-570*650D71D:172.16.254.253:Connected
9117-570*650D71D:172.16.255.251:Connected
9131-52A*065F7BB:172.16.253.254:Connected
9131-52A*065F8BA:172.16.254.252:Connected
The link to the name of the managed system is the serial number - not the IP address! The IP addresses listed above are mounted
on the service processor's private NIC and managed by the integrated DHCP server of the HMC.
6. Show a List of All I/O Adapters
The command below will show a list of all adapters physically plugged into a Managed System:
power5/6/7:
hscroot@hmc> lshwres -r io -m pserver --rsubtype slot --filter -F lpar_name:drc_name:description
null:U78C0.001.DBJC357-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC357-P2-C2:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-T3:RAID Controller
vios2:U78C0.001.DBJC357-P2-C8-T7:Generic XT-Compatable Serial Controller
vios2:U78C0.001.DBJC357-P2-C5:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-C6:Ethernet controller
vios2:U78C0.001.DBJC357-P2-C9-T2:PCI-E SAS Controller
vios2:U78C0.001.DBJC357-P2-C9-T1:PCI-E SAS Controller
null:U78C0.001.DBJC373-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC373-P2-C2:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-T3:RAID Controller
vios1:U78C0.001.DBJC373-P2-C8-T7:Generic XT-Compatable Serial Controller
vios1:U78C0.001.DBJC373-P2-C5:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-C6:Ethernet controller
vios1:U78C0.001.DBJC373-P2-C9-T2:PCI-E SAS Controller
vios1:U78C0.001.DBJC373-P2-C9-T1:PCI-E SAS Controller
A leading "none" indicates that the adapter is not assigned to an LPAR. To show a list of all I/O adapters owned by a specific LPAR
use the "--filter" modifier:
power5/6/7:
hscroot@hmc> lshwres -r io -m pserver --rsubtype slot -F lpar_name:drc_name:description --filter "lpar
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
7. Overview DLPAR status
power5/6/7:
hscroot@hmc> lspartition -dlpar
<#0> Partition:<6*9117-MMB*656D24A, mylpar1.unixwerk.de, 111.111.15.66>
Active:<0>, OS:<AIX, 5.3, 5300-09-08-1036>, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<512>
<#1> Partition:<2*9117-MMB*656D24A, vios1.unixwerk.de, 111.111.15.65>
Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<52
<#2> Partition:<1*9117-MMB*656D24A, vios2.unixwerk.de, 111.111.15.64>
Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<51
<#3> Partition:<3*9117-570*656FFFF, mylpar2.unixwerk.de, 111.111.226.4>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb,
<#4> Partition:<1*9117-570*656FFFF, mylpar3.unixwerk.de, 111.111.226.2>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb,
<#5> Partition:<1*9133-55A*650D71D, mylpar7.unixwerk.de, 111.111.0.26>
Active:<1>, OS:<AIX, 5.3, 5300-09-03-0918>, DCaps:<0x2f>, CmdCaps:<0xb,
<#6> Partition:<4*9117-570*656FFFF, mylpar4.unixwerk.de, 111.111.226.5>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb,
0xb>, PinnedMem:<1707>
0xb>, PinnedMem:<884>
0xb>, PinnedMem:<406>
0xb>, PinnedMem:<967>
A value <1> for Active: should be fine.
LPAR Management: Operations
1. Soft Reset of an LPAR
power4:
hscroot@hmc> chsysstate -m pserver -r lpar -n mylpar -o reset
power5/6/7:
hscroot@hmc> chsysstate -r lpar -m pserver -o shutdown -n mylpar
2. Soft Reset of a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -n pserver -r sys -o reset
3. Hard Reset of an LPAR
power4:
hscroot@hmc> chsysstate -m pserver -r lpar -n mylpar -o off
power5/6/7:
hscroot@hmc> chsysstate -r lpar -m pseries -o shutdown -n mylpar --immed
4. Hard Reset of a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -n pserver -r sys -o off
5. Virtual Console
That's how you get a connection to an LPAR's serial console:
power4 + power5/6/7:
hscroot@hmc> mkvterm -m pserver -p mylpar
If your system is running in FullSystemPartition-Mode you connect with a command like this:
hscroot@hmc> mkvterm -m pserver
You can escape from the console connection by typing ~~. (twice tilde followed by a dot)
If you cannot connect to the serial console and you get an error message instead:
All available virtual terminal sessions have been opened and are in use.
To force a new open session, perform a Close Terminal Session operation
which frees up the session.
there is still another active connection to this console. You can close this connection with:
power4 + power5/6/7:
hscroot@hmc> rmvterm -m pserver -p mylpar
If you're not sure which managed system belongs to an LPAR you could walk through the vtmenu:
hscroot@hmc> vtmenu
Retrieving name of managed system(s) . . .
----------------------------------------------------------
Managed Systems:
----------------------------------------------------------
1) pserver1
2) pserver2
3) pserver3
Enter Number of Managed System.
(q to quit): 1
----------------------------------------------------------
Partitions On Managed System: pserver1
----------------------------------------------------------
1)
mylpar1
Running
2)
mylpar2
Running
3)
mylpar3
Running
4)
mylpar4
Running
5)
mylpar5
Running
Enter Number of Running Partition (q to quit):
Just enter a number and you will be connected to the console of the corresponding LPAR.
6. Activation of an LPAR
power4:
hscroot@hmc> chsysstate -r lpar -m pserver -o on [ -f myprofile ] -n mylpar
power5/6/7:
hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -n mylpar
7. How to Boot an LPAR into SMS Menu
power4:
You have to create an additional profile. In this profile set the boot mode to 'sms'. We call the profile mysmsprofile. Then start
the LPAR with this profile:
hscroot@hmc> chsysstate -r lpar -m pserver -o on -f mysmsprofile -n mylpar
With new HMCs a special profile is not any longer needed. The profile's boot mode can be overwirtten with -b:
hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -b sms -n mylpar
The same way the LPAR can be bootet into the Open Firmware prompt (Bootmode: 'of'):
hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -b of -n mylpar
8. How to Power on a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -o on -r sys -n pserver -c full
9. Bring the key switch to position NORMAL
This might be necessary on some power5 HMCs when an LPAR does not properly boot after issuing the power on command above.
You might see a message like this:
0514-440 cfgcon: failed to create log file: check path name, permissions, and available space
When seeing this you can only access diag mode or boot the LPAR in singleuser mode. This command sets the key switch back to
normal position:
power5/6/7:
hscroot@hmc> chsysstate -r lpar -o chkey -k norm -n mylpar -m pserver
LPAR Configuration
1. Change an LPAR's Name
Let's say we have these five LPARs defined on a managed system:
hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:barney:Running
4:mylpar2:Running
5:mylpar3:Running
Now we want to change the name of LPAR 3 from barney to mylpar1:
power5/6/7:
hscroot@hmc> chsyscfg -r lpar -m pserver -i "name=barney,new_name=mylpar1"
We check and see that the name of LPAR 3 indeed has changed to mylpar1:
hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:mylpar1:Running
4:mylpar2:Running
5:mylpar3:Running
2. Rename a Managed System
This would change the name of the manages system pserver to pserver1:
power5/6/7:
hscroot@hmc> chsyscfg -r sys -m pserver -i "new_name=pserver1"
3. DLPAR: Increase the Number of Processing Units of an LPAR
To assign 8 additonal processing units to an LPAR run the following command:
power5/6/7:
hscroot@hmc> chhwres -r proc -m pserver -o a -p mylpar --procunits 8
www.decsinfotech.com | www.clickuwant.com

AIX Commands

AIX OS Commands:

To find the HMC IP from LPAR
/usr/sbin/rsct/bin/rmcdomainstatus -s ctrmc

To check more than 2MB files under /var
find /var/ -xdev -size +2048 -ls | sort -r

To check the processes which are used by /var filesystem
fuser -cdfxV /var

To check the RAID level of the hdisk
lsattr -El hdisk3 | grep raid

To check 15 most cpu utilized processes
ps -ef |egrep -v "STIME| $LOGNAME" |sort +3 -r| head -n 15

To find the microcode of the system
lsmcode

To check machine S.No
lsconf |grep -i machine

To find the firmware version of AIX
lscfg -vp| grep -p Platform

To check the eth media speed
entstat -d en0 |grep "Media Speed"

To check the status of Link Line
netstat -v en0 |grep -p "Specific Statistics"

To find the MAC address of the eth
netstat -ia

To find the virtual location of an ethernet adapter
lscfg -l ent1

To Check Failed Login
who -a /etc/security/failedlogin

Find the version of AIX that is running
oslevel, osleve -s

List all attributes of system
getconf -a

bootinfo and getconf can return much of the same information, getconf
returns more and has the grepable -a option.

Find the level of firmware on a system
invscout

List all attributes for the kernel \device"
lsattr -El sys0

To check the kernel version on AIX
ls -al /unix,

which_fileset /usr/lib/boot/unix_64,
lslpp -h bos.mp64

Print a \dump" of system information
prtconf

To View Only Configuration File Directives ( uncommented lines of a config file )
grep -v "^#" /path/to/config/file
(or)
sed '/ *#/d; /^ *$/d' /path/to/file

To find UNIX / Linux command for particular task
apropos -r 'remove file'

To Linux Find Out Virtual Memory PAGESIZE
getconf PAGESIZE

To Identify the Firmware level
lsmcode,
lsmcode -A,
lsmcode -d fcs0

Determining the program that caused the core dump
strings corefilename |grep _=
(or)
lquerypv -h corefilename 6b0 64

 

AIX Boot Path Enablement (Thanks to IBM.com)

 

Question

This technote discusses an enhancement to AIX to allow setting specific paths to boot from.

Answer

In AIX 6.1 TL 6 (6100-06-00) a new feature was added to allow a system administrator to specify which paths would be used to boot from in a multipath environment. This was added by APAR IZ72620 (PTF U838753). The feature was also added to AIX 7.
BOOTLIST OUTPUT
The bootlist will now print the path ID of each path on output:

# bootlist -om normal
hdisk0 blv=hd5 pathid=0
hdisk0 blv=hd5 pathid=1

In this example there are two paths to the boot disk.


SETTING THE BOOTLIST
To set the bootlist to specific paths, list each path on the command line:

# bootlist -m normal hdisk0 blv=hd5 pathid=0 pathid=1
or
# bootlist -m normal hdisk0 blv=hd5 pathid=0,1

Using this method paths can be ignored or deleted from the boot list. This may be necessary if there are more than 5 paths to a boot device, as the Open Firmware for pSeries systems only allows 5 devices (or paths) maximum in the boot list. For example if there are 8 paths to a boot disk, there is a 3 out of 8 chance that the multipath device driver will pick a path not in the boot list. If that happens the boot will most likely hang with an LED 554 "UNKNOWN BOOTDISK" error.

Path ordering is also maintained in the bootlist. If a user wishes to have paths 2, then 1, then 0 searched or booted from, using "pathid=2,1,0" will follow this ordering during the boot.


LIMITING COMMANDS TO A SINGLE PATH ID
Additionally, pathing commands such as rmpath, mkpath, lspath, etc have been enhanced to add the "-i" flag. This flag will limit the command to only use that path ID.

# lspath -i 0
Enabled hdisk0 fscsi0
Enabled hdisk1 fscsi0


DISPLAYING A PATH ID
The "-t" argument has also been added to the lspath command to allow the user to see the path IDs.

# lspath -t
Enabled hdisk0 fscsi0 0
Enabled hdisk0 fscsi1 1
Enabled hdisk1 fscsi0 0
Enabled hdisk1 fscsi1 1

or, to list out all the paths to a specific disk:

# lspath -t -l hdisk0
Enabled hdisk0 fscsi0 0
Enabled hdisk0 fscsi1 1

The path ID is the last digit of the output.

www.decsinfotech.com | www.clickuwant.com

www.decsinfotech.com | www.clickuwant.com

NIM Server Build

1) Identify Resources
            lppsource – 3 GB per Version or Release level of AIX
            SPOT – 200 MB Per Version or Release level of AIX
            Server – Lots of disk.  Start with 3 GB per client + 3 GB per level of AIX.
            Clients
            Network Interfaces
            bosinst.data – install from scratch, migration
            image.data – optional
2) Create NIM VG and File system
smitty mkvg à create exportvg
smitty crfs à create /export file system (large file enabled JFS, or JFS2)
You may or may not want to create additional filesystems for other NIM resources
Typically:
            lppsources: /export/aix_level (e.g. aix_520)
            SPOT: /export/aixlevel_SPOT  (e.g. aix520_SPOT)
            Images: /export/images   (used for mksysb images)
You will need to add the images directory to /etc/exports with root access from your LPARs.  Be sure to run exportfs –a to recreate the /etc/xtab file
Other resources: /export/nim  (e.g. bosinst.data …)
3) Create NIM Server
Install the following filesets if not already on the NIM master
  bos.sysmgt.nim.client  
  bos.sysmgt.nim.master  
  bos.sysmgt.nim.spot    
Configure primary network and start the NIM daemons
smitty nim --> Configure the NIM Environment --> Advanced Configuration --> Initialize NIM Master Only
         Configure Network Installation Management Master Fileset
                         Type or select values in entry fields.
                 Press Enter AFTER making all desired changes.
                                                                                                 [Entry Fields]
* Network Name                                                                          [PublicTokenRing]
* Primary Network Install Interface                                                [tr0]                    +
  Allow Machines to Register Themselves as Clients?                    [yes]                   +
  Alternate Port Numbers for Network Communications
       (reserved values will be used if left blank)
    Client Registration                                                                 []                         #
    Client Communications                                                          []                         #
F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command      F7=Edit                F8=Image
F9=Shell            F10=Exit            Enter=Do
Create/Define NIM lppsource and SPOT:
Do this for each level of AIX being used.
smitty nim --> Configure the NIM Environment  --> Advanced Configuration --> Create NIM Basic Installation resources --> Create a LPPSOURCE and SPOT --> Select the master
                      Create Basic Installation Resources
                      Type or select values in entry fields.
               Press Enter AFTER making all desired changes.
[TOP]                                                                         [Entry Fields]
* Resource SERVER                                                   master
* Input device for installation images                             [cd0]                   +
    (specify the device on the resource server)
* LPP_SOURCE Name                                              [aix_520]
* LPP_SOURCE Directory                                         [/export/aix_520]    +
  Create new file system for LPP_SOURCE?               [no]                      +
  File system SIZE (MB)                                            [650]                     #
  VOLUME GROUP for new file system                      [/exportvg]             +
* SPOT Name                                                          [AIX52_SPOT]
* SPOT Directory                                                     [/export/aix52_SPOT]    +
  Create new file system for SPOT?                           [no]                    +
  File system SIZE (MB)                                           [350]                    #
  VOLUME GROUP for new file system                     [exportvg]              +
  Remove all newly added NIM definitions                  [no]                    +
  and filesystems if any part of this
  operation fails?
[BOTTOM]
F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command      F7=Edit               F8=Image
F9=Shell            F10=Exit             Enter=Do
Define NIM Clients:
The client systems need to be defined in the /etc/hosts file prior to these installation steps.  Do this for every NIM Client.
smitty nim --> Configure the NIM Environment --> Advanced Configuration --> Define NIM Clients Machines --> Add a NIM client
                                  Define a Machine
                 Type or select a value for the entry field.
               Press Enter AFTER making all desired changes.
                                                                 [Entry Fields]
* Host Name of Machine                              [mohisystem]
    (Primary Network Install Interface)
F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit              F8=Image
F9=Shell            F10=Exit              Enter=Do
4) Load all of AIX CD filesets into lppsources for every level of AIX supported:
smitty bffcreate --> select cd
               Copy Software to Hard Disk for Future Installation
                   Type or select values in entry fields.
              Press Enter AFTER making all desired changes.
                                                                                [Entry Fields]
* INPUT device / directory for software                         /dev/cd0
* SOFTWARE package to copy                                 [all]                   +
* DIRECTORY for storing software package                [/export/aix_520]
  DIRECTORY for temporary storage during copying     [/tmp]
  EXTEND file systems if space needed?                    yes                    +
  Process multiple volumes?                                      yes                    +
F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit               F8=Image
F9=Shell            F10=Exit              Enter=Do
5) Download fixes from IBM to a temporary directory, like /export/aix520/fixes.  Unzip the fixes.  Use “smitty bffcreate” to copy fixes from /export/aix520/fixes to /export/aix_520/installp/ppc.  You may need to run “inutoc .” in the /export/aix_520 directory.
6) Update the NIM Server with the latest fixes
smitty update_all -->install device = /export/aix_520 -->
           
               Update Installed Software to Latest Level (Update All)

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

                                                                                 [Entry Fields]
* INPUT device / directory for software                         /export/aix_520
* SOFTWARE to update                                            _update_all
  PREVIEW only? (update operation will NOT occur)     no                     +
  COMMIT software updates?                                      no                     +
  SAVE replaced files?                                               yes                    +
  AUTOMATICALLY install requisite software?              yes                    +
  EXTEND file systems if space needed?                     yes                    +
  VERIFY install and check file sizes?                         no                     +
  DETAILED output?                                                  no                     +
  Process multiple volumes?                                       yes                    +
  ACCEPT new license agreements?                           yes                    +
  Preview new LICENSE agreements?                         no                     +



F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit              F8=Image
F9=Shell            F10=Exit              Enter=Do 

7) *** Critical Step ***   Update the SPOT
smitty nim --> Perform NIM administration tasks -->  Manage Resources à
Perform operations on NIM resources à Select the SPOT from list à Select update_all from the list à
                                Customize a SPOT
Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[Entry Fields]
* Resource Name                                                 52spot
Fixes (Keywords)                                                 update_all
* Source of Install Images                                     [aix520]                +
Expand file systems if space needed?                   yes                    +
Force                                                                  no                     +

installp Flags
PREVIEW only? (install operation will NOT occur)   no                     +
COMMIT software updates?                                   no                     +
SAVE replaced files?                                            yes                    +
AUTOMATICALLY install requisite software?           yes                    +
OVERWRITE same or newer versions?                   no                     +
VERIFY install and check file sizes?                      no                     +


F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command      F7=Edit                F8=Image
F9=Shell            F10=Exit              Enter=Do
8) Create bosinst.data for install and migration.  The install will be used for mksysb installs or from scratch installs.
cp /var/adm/ras/bosinst.data /export/nim/bosinst.migrate
cp /var/adm/ras/bosinst.data /export/nim/bosinst.install
Edit the bosinst files
control_flow:
    CONSOLE = Default
    INSTALL_METHOD = migrate   ( or  “overwrite”  for mksysb installs or new installs)
    PROMPT = yes
    EXISTING_SYSTEM_OVERWRITE = no   (Yes for mksysb or install)
    INSTALL_X_IF_ADAPTER = yes
    RUN_STARTUP = no   (do you want Install Assistant at boot?)
    RM_INST_ROOTS = no
    ERROR_EXIT =
    CUSTOMIZATION_FILE =
    TCB = yes   (ALWAYS have this as yes)            
    INSTALL_TYPE =
    BUNDLES =
    SWITCH_TO_PRODUCT_TAPE =
    RECOVER_DEVICES = Default
    BOSINST_DEBUG = no
    ACCEPT_LICENSES = yes  (always have this as yes)
    INSTALL_64BIT_KERNEL = yes  (default is no.  Turn to yes if the machine is 64 bit capable)
    INSTALL_CONFIGURATION =
    DESKTOP = CDE
    INSTALL_DEVICES_AND_UPDATES = yes
    IMPORT_USER_VGS = yes
    ENABLE_64BIT_KERNEL = yes (default is no, turn to yes if 64 bit capable)
    CREATE_JFS2_FS = yes  (default is no, turn to yes)
    ALL_DEVICES_KERNELS = yes
    GRAPHICS_BUNDLE = yes
    DOC_SERVICES_BUNDLE = yes
    NETSCAPE_BUNDLE = yes
    HTTP_SERVER_BUNDLE = no
    KERBEROS_5_BUNDLE = no
    SERVER_BUNDLE = yes
    ALT_DISK_INSTALL_BUNDLE = yes  (default is no, you will want this)
    REMOVE_JAVA_118 = no 

Define the bosinst.data files as a resource.  Do once for each file
Smitty nim --> perform NIM administration tasks --> Manage resources --> define a resource --> select bosinst_data
                               Define a Resource

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

                                                             [Entry Fields]
* Resource Name                                      [bosinst_migrate]
* Resource Type                                       bosinst_data
* Server of Resource                                 [master]                +
* Location of Resource                               <t/nim/bosinst.migrate]  /
  Comments                                                []

  Source for Replication                             []                      +


  
F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit               F8=Image
F9=Shell            F10=Exit              Enter=Do
9) Create other network interface resources
Smitty nim --> perform NIM administration tasks --> manage networks --> define a network --> Select network type
                               Define a Network

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

                                                             [Entry Fields]
* Network Name                                       [privateTokenRing]
* Network Type                                        eth
* Network IP Address                               [10.10.16.0]
* Subnetmask                                         [255.255.255.0]
  Default Gateway for this Network             [10.10.16.1]
  Other Network Type                                                      +
  Comments                                           []



F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit               F8=Image
F9=Shell            F10=Exit              Enter=Do

10) On Clients, Initialize NIM environment
Install bos.sysmgt.nim.client  
Define the system as a NIM client
smitty nim_client  --> configure Network Installation  Manager client fileset
            Configure Network Installation Management Client Fileset

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[TOP]                                                             [Entry Fields]
* Machine Name                                             [napoli]
* Primary Network Install Interface                    [en0]                   +
* Host Name of Network Install Master              [nim-server]

  Hardware Platform Type                                 chrp
  Kernel to use for Network Boot                        [up]                    +
  Ethernet Interface Options
    Network Speed Setting                                 []                      +
    Network Duplex Setting                                []                      +
  Comments                                                   [44P in India Office]
  Alternate Port Numbers for Network Communications
       (reserved values will be used if left blank)                           
    Client Registration                                       []                       #
    Client Communications                                []                       #
[BOTTOM]

F1=Help             F2=Refresh          F3=Cancel           F4=List
Esc+5=Reset     F6=Command       F7=Edit               F8=Image
F9=Shell            F10=Exit              Enter=Do                         
You are now ready to do NIM Tasks.
Other NIM Server Notes
The NIM server must be at the highest level of AIX in the NIM environment.
When fixes are required by a system, the following steps should be taken.
1) Download the fixes to a temporary directory.
2) Use “smitty bffcreate” to add them to the appropriate lppsource
You may need to run “inutoc .” in the directory to recreate the table of contents file
3) On the NIM Server, do a “smitty update_all” using the lppsource as the installation device
4) Update the SPOT for the lppsource
5) Update the NIM Client