If you run into any issues with DLPAR not working correctly try the steps below to restart the RMC service. We have seen this procedure work in the past to rectify the problem.
On the HMC command line, first check the DCaps value of the LPAR. If the value is DCaps “<0x0>” there is an issue with the RMC connection on that LPAR.
# lspartition -dlpar
<#1> Partition:<6*9117-MMA*xxxxxx, , 10.x.x.x>
Active:<0>, OS:<, , >, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<0> (DCaps value should look like a hex number “<0x2c5f>”)
On the LPAR run:
root@joe / # /usr/sbin/rsct/bin/rmcctrl -z (stops the daemons)
root@joe / # /usr/sbin/rsct/bin/rmcctrl -A (starts the daemons)
0513-071 The ctrmc Subsystem has been added.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 17891432.
root@joe / # /usr/sbin/rsct/bin/rmcctrl -p (enables daemons for remote client connections)
If DLPAR is still failing after running the steps above, run the command below to delete the RMC database and recreate the RMC configuration:
root@joe / # /usr/sbin/rsct/install/bin/recfgct
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 27918446.
NOTE: Wait 10 minutes then run below command to check (If IBM.DRM is active, issue may be resolved):
root@joe / # lssrc -a | grep rsct
ctrmc rsct 27918446 active
IBM.DRM rsct_rm 14549016 active
IBM.ServiceRM rsct_rm 29294750 active
IBM.CSMAgentRM rsct_rm 27983878 active
ctcas rsct inoperative
IBM.ERRM rsct_rm inoperative
IBM.AuditRM rsct_rm inoperative
IBM.LPRM rsct_rm inoperative
IBM.HostRM rsct_rm inoperative
As a note if this does not resolve your problem log a call with IBM so you can send them system logs/traces.
Technical Blog for System Administrator 