DLPAR Operation Fails

From Wikistix

One cause of failed Dynamic LPAR (DLPAR) operations is duplicate ct_node_id's. This results in an apparent communications failure from the HMC when attempting DLPAR operations.

This can be caused usually by cloning AIX systems via alt_disk_install or other more obtuse means (eg. moving one half of a mirrored rootvg between nodes).

To check if this is the case, compare the 16 digit hexidecimal number in the first line of /etc/ct_node_id.

The ct_node_id is used by the following:

  • LPARs
  • Dynamic LPARs
  • HACMP-ES
  • HACMP-ES-CRM
  • PSSP
  • CSM
  • GPFS
  • VSD
  • RVSD
  • Oracle Parallel Server
  • Oracle 9i RAC

To assign a new ct_node_id, perform the following: 

# stopsrc -g rsct
0513-044 The ctrmc Subsystem was requested to stop.
# /usr/sbin/rsct/install/bin/uncfgct -n
# /usr/sbin/rsct/install/bin/cfgct
0513-071 The ctcas Subsystem has been added.
0513-071 The ctrmc Subsystem has been added.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 233648.

The following may be required to re-configure rsct, although in tests it has not been required. 

# /usr/sbin/rsct/bin/rmcctrl -z
# /usr/sbin/rsct/bin/rmcctrl -A
0513-071 The ctrmc Subsystem has been added.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 237814.
# /usr/sbin/rsct/bin/rmcctrl -p

After assigning a new ct_node_id, wait several minutes before trying the DLPAR operation. The HMC must re-synchronize its state before it will work.

If this is a new system install, and DLPAR operations fail, make sure that the csm.client fileset is installed: 

ksh$ lslpp -L csm.client | head -4
  Fileset                      Level  State  Type  Description (Uninstaller)
  ----------------------------------------------------------------------------
  csm.client                 1.4.1.0    C     F    Cluster Systems Management
                                                   Client

See Also

Retrieved from "https://www.stix.id.au/wiki/index.php?title=DLPAR_Operation_Fails&oldid=3607"