X

An Oracle blog about Ops Center

  • FAQ
    April 16, 2015

LDom versions

Guest Author

I saw a recent question about LDOM versions that come along with Oracle Solaris versions:

"I'm looking at upgrading some of my Control Domains to Oracle Solaris 11.2 SRU 8, which comes with LDoms 3.2. If I upgrade, will the new version be supported for migration?"

LDoms 3.2 is not yet supported by Ops Center, so if you start using it, you'll find that Ops Center won't know how to find migration targets for it.

If you're interested in which versions are supported, keep an eye on the Certified Systems Matrix; we'll add new versions there once they're certified.

EDIT: As Jay Lake pointed out in the comments, MOS Document 2014856.1 contains a workaround for this issue:

On all CDOMs in the pool, add the following line to /opt/sun/n1gc/etc/ldoms.properties:

archlist.LDMMGR.3.2=native,generic,migration-class1,sparc64-class1

Then restart the agent on the CDOM.

Repeat for all cdoms in pool.

EDIT 2: Ops Center 12.3 supports LDoms 3.2.

Join the discussion

Comments ( 5 )
  • guest Tuesday, April 28, 2015

    Meanwhile, hardware platform support tells us that we need to be on current firmware.

    For T5240, that is 7.4.8a. My understanding is that firmware / OS updates go together (or rather, there is a minimum firmware for a given SRU).


  • Owen Wednesday, May 6, 2015

    I'm looking into this. If the latest firmware requires the latest SRU, this could indeed be a problem, but I'm not sure if that's the case.


  • Owen Monday, May 11, 2015

    I've looked into this issue, and there isn't a direct connection between firmware and OS versions - so the latest firmware does not have a minimum SRU associated with it.


  • Jay Pike Friday, May 29, 2015

    It appears that a document just came out to address this issue: Doc ID 2014856.1


  • Owen Wednesday, June 17, 2015

    Yep, that MOS document does indeed contain a workaround, which I've added to the post. Thanks for the heads-up!


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.