Running production and test 5.7 on same hcihostid?

We have been running on P5s and now have migrated TEST to P7s so I can share my observations that should be applicable to your situation.

For IBM AIX on both the IBM P5s and P7s one entry for a given hcihostid will work for both PROD and TEST for Cloverleaf 5.6rev2 and earlier.

It is my current understanding this is still true for cloverleaf 5.8 running under IBM AIX but we are not there yet so this is my assumption.

Other platfrms and operating systems don’t necessarily behave this way from conversations I’ve had with others but for IBM AIX it is all based off the serial number of the physical box returned by the hcihostid command or “uname -a”.

We purchased a TEST and PROD cloverleaf license but I use the same license file for both PROD and TEST to save me the greif of creating entries that are sometimes stuborn to get working, so I’ve always been doing what you are asking about.

I also have an entry in the license file for both physical boxes in one license file.

This is necessary if you vmotion to another physical box, which will allow you to run cloverleaf but if you cycle a process then it will not start if the license file does not also contain an entry for the hcihostid you just vmotioned to.

Here is the P7 license file I’m using in TEST cloverleaf that we mgirated from the P5s and when I migrate PROD to the P7 I will use the same exact entries.


#—————————————
# license keys for P570_mdahub4_c91b1d4c
#—————————————

FEATURE cl-pkg-cl hcilicmgrd 5.6 permanent uncounted D5C2BD2F26AA
[code]
#

---

# license keys for P570_mdahub4_c91b1d4c
#

---

FEATURE cl-pkg-cl hcilicmgrd 5.6 permanent uncounted D5C2BD2F26AA

Keep in mind that this will work ok as long as you have an unlimited thread license.  If you have a 120 thread license for Productiion and a 120 thread license for Test, I doubt you can have them both running on the same box.  And you can’t just switch to a single 240 thread license since the cost of prod threads are different than the cost of test threads.  [Perhaps I am the only one still out there with a limited thread license  :^(  ]

Craig:

Good point about the thread count limitation potentially being a concern.

Since we have an unlimited license, I didn’t think about that aspect.