LDoms and Maintenance Mode

 I got a few questions about how maintenance mode works with LDoms.

"I have a Control Domain that I need to do maintenance on. What does being put in maintenance mode actually do for a Control Domain?"

Maintenance mode is what you use when you're going to be shutting a system down, or otherwise tinkering with it, and you don't want Ops Center to generate incidents and notification of incidents. Maintenance mode stops new incidents from being generated, but it doesn't stop polling, or monitoring, the system and it doesn't prevent alerts.

"What does maintenance mode do with the guests on a Control Domain?"

If you have auto recovery set and the Control Domain is a member of a server pool of eligible systems, putting the Control Domain in maintenance mode automatically migrates guests to an available Control Domain.  When a Control Domain is in maintenance mode, it is not eligible to receive guests and the placement policies for guest creation and for automatic recovery won't select this server as a possible destination. If there isn't a server pool or there aren't any eligible systems in the pool, the guests are shut down.

You can select a logical domain from the Assets section to view the Dashboard for the virtual machine and the Automatic Recovery status, either Enabled or Disabled.

To change the status, click the action in the Actions pane.

"If I have to do maintenance on a system and I do not want to initiate auto-recovery, what do I have to do so that I can manually bring down the Control Domain (and all its Guest domains)?"

Use the Disable Automatic Recovery action.

"If I put a Control Domain into maintenance mode, does that also put the OS into maintenance mode?"

No, just the Control Domain server. You have to put the OS into maintenance mode separately.

"Also, is there an easy way to see what assets are in maintenance mode? Can we put assets into, or take them out of, maintenance mode on some sort of group level?"

You can create a user-defined group that will automatically include assets in maintenance mode. The docs here explain how to set up these groups. You'll use a group rule that looks like this:


We have two T3-1 blades and have 4 ldoms in each.The LUNS are shared.
We are able to migrate the guest ldoms manually from one blade to another.
We want to make sure that incase one blade goes down the guest ldoms in that blade migrate automatically to the other blade.

This did not happen once one of our blade got down. How do we accomplish this feature ?

Posted by Sunny on September 16, 2013 at 02:53 AM MDT #


Have you set up a Server Pool and configured the LDoms for automatic migration?

Here's a link to the Server Pools chapter: http://docs.oracle.com/cd/E27363_01/doc.121/e27511/ftr_server_pool_mgmt.htm

Posted by Owen on September 17, 2013 at 01:37 PM MDT #

I have a greenfield controldomain with ldoms running.
I need to do maintenance on this controldomain in the future and like to take advantage of the migration feature.
However, this controldomain is not in any server pool.
Can I add this controldomain to a existing server pool?
Thank you.

Posted by yun feng on October 03, 2013 at 03:35 AM MDT #

Yun Feng,

Yes, you can add hosts to an existing Server Pool. The Exploring Your Server Pools how-to explains how to do this. Here's a link to the relevant section:


Once it's added, you should be able to migrate LDoms within the Server Pool.

Posted by Owen on October 03, 2013 at 10:28 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed

This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you


« February 2015