DLPAR memory problem 1

[charlieau]

I am using Aix 5.3 and HMC 6.1.

I want to add memory to one of the LPAR dynamically. Afterward, I got an error message from HMC and said that HMC cannot connect to the LPAR's RMC. Unless I restart the LPAR, the memory increased will not take effect.

I can increase memory dynamically in other LPARs in same machine without any problem.

Anyone can help me on this issue?

Thank you very much!!!

 

[p5wizard]

Make sure there is a working network connection between HMC and that LPAR.

Also sometimes recycling the rsct and rsct_rm daemons helps:

on the LPAR:

stopsrc -g rsct_rm
stopsrc -g rsct
(then wait a few seconds)
startsrc -g rsct
(the rsct_rm group starts automatically with rsct group)

HTH,

p5wizard

 

[khalidaaa]

check the rmc connectivity on that lpar!

man rmcctrl

http://publib.boulder.ibm.com/infoc...ic=/com.ibm.aix.cmds/doc/aixcmds4/rmcctrl.htm

One more thing. Can you ping the lpar from the HMC and visa versa?

Check DNS connectivity and network!

There is a command that you can run as well from the lpar itself to make sure that it can dlpar but i can't remember it for now!

i will come back to you on that later but you check first the above and let me know

Regards,
Khalid

 

[khalidaaa]

You are so fast p5wizard I couldn't have the time to see your comments

p5wizard, I think it is not recommended to use startscr and stopsrc for the RMC daemons isn't it? I think the recommendation is to use rmcctrl command instead! (I have an exam today on that so i'm going as per the manual correct me if i'm wrong please)

Any way, charlieau That's the command i told you about:

lspartition -dlpar

http://www.ibm.com/developerworks/eserver/articles/DLPARchecklist.html

Regards,
Khalid

 

[khalidaaa]

In case you couldn't open the first link (it has been renamed to this):

http://www-128.ibm.com/developerworks/eserver/articles/DLPARchecklist.html

Very nice tips on RMC and LPAR-to-HMC connectivity!

Regards,
Khalid

 

[p5wizard]

rmcctrl is IMHO just a high-level command (korn shell script) which runs the stop/startsrc low-level commands and more.

khalidaaa, you are probably correct that it is better to use the rmcctrl script instead of the stop/startsrc commands. If nothing else, it keeps you away from problems due to typing mistakes.


HTH,

p5wizard

 

[ogniemi]

I did many times p5wizard mentioned - it does the job.

 

[khalidaaa]

I just finished from the 180 exam and i passed (95%)

rmcctrl was recommended to use instead of startsrc/stopsrc in the course i attended last year.

any way, as ogniemi said, as long as it does the job, why not. But I think the recommendation was there for a reason!

This's what exactly written in the course manual:

Normally, you should not have to stop and restart the daemons. They are started from /etc/inittab and should work "out of the box"

To stop daemons:
/usr/sbin/rsct/bin/rmcctrl -z

To start daemons:
/usr/sbin/rsct/bin/rmcctrl -A

To enable the daemons for remote client connections (HMC to LPAR and visa versa):
/usr/sbin/rsct/bin/rmcctrl -p

If you're familiar with the System Resource Controller (SRC) you might be tempted to use stopsrc and startsrc commands to stop and start these daemons. Don't do it... use the rmcctrl commands instead.

Regards,
Khalid

 

[p5wizard]

[off topic]
congratulations Khalidaaa
[/off topic]

 

[khalidaaa]

[off topic]
Thanks p5wizard It is something that i was planning for a long time. Finally i had the time when i broke my leg
[/off topic]

 

[charlieau]

thanks all~