Using Live partition mobilty is a real pain reliever when you need to get some downtime, in order to upgrade your pseries’ firmware , for example .

(if you’re not familiar with LPM migration , here is a visual example, but please, first, cut the volume off, this « music » can get into your hear pretty quickly otherwise 🙂 ) :

Got trouble?

…But sometimes after a LPM operation you may encounter unexpected behaviour, like a failed NIM operation initiated by your NIM master, which worked like a charm  few minutes ago!

You will experience connection problems to your nim master, because your cpu_id attribute changes from a LPM migration to another. But NIM stores it in its database when the niminit operation is performed, and never changes it after that. That’s where the trouble is.

Because every time you migrate your LPAR, the CPU_ID changes (Kind of a problem when licensed applications use this CPU_ID to calculate its license, and check if you purchased your product..).

You can check this by issuing a simple uname -m on the client and a lsnim on the NIM server :

 root@lpar# uname -m


root@nimserver# lsnim -l lpar | grep cpuid
cpuid = 00CF55C64C00

What are the options then ?

You’ve got three options (maybe more) :

  • execute the niminit command on your client:

# niminit -a name=$lpar -a master=$nim_master -a connect=nimsh
  • Force the cpuid on the NIM server :

# nim -Fo change -a cpuid=[NEW_CPUID] ClientName 
  • a more permanent solution : Disable the client CPU ID validation from the NIM master

Client CPU ID validation can be managed on the NIM master by using the validate_cpuid attribute.

To disable client CPU ID validation, set the attribute validate_cpuid=no on the NIM master:

nim -o change -a validate_cpuid=no master
Attention: The value of the validate_cpuid attribute should not be changed while operations are being performed on NIM clients because it could potentially disrupt client communications for active machines.


Share Button
NIM operations don’t work after a Live Partition Mobility? Update your NIM client’s CPU_ID !
Taggé sur :        

Laisser un commentaire