[ScriptDaddy]

Has anyone ever come across a scenario where lspartition -dlpar reports the following:

<#4> Partition:<1, lpar1.lpardomain.com, 10.200.10.172>
Active:<0>, OS:<, >, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<0>

Yet still perform DLPAR operations.

I've followed the normal proceedure for restarting DLPAR, but it still reports the DCaps as <0x0>. Only step not taking is actually restarting the LPAR.

Bit of a strange one ... not come across it before, but have now managed to replicate it several times.

To be fair ... the HMC version is a little behind the latest release, so chances are it's something that has been picked up before and resolved.

Ben

[rvannoy]

Have you tried restarting the hmc? I had a similar problem in reverse when I created a new lpar and gave it the same IP as another LPAR that was down. I could not get rmc running on the client yet the lspartition -dlpar showed it was fine.

I rebooted the hmc and that fixed it.

[ScriptDaddy]

Yep ... restarted the HMC, only thing that hasn't been restarted is the LPAR.

Ben

[rvannoy]

Originally Posted by ScriptDaddy

Yep ... restarted the HMC, only thing that hasn't been restarted is the LPAR.

Ben

What release of the HMC LIC? And on a p4 or p5 platform? It sounds like something related to hostname resolution from the hmc, at least for that particular lpar. Strange that DLPAR still works though. Any possibility that the hostname and/or ip is aliased or duplicated to another host in DNS?