Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Stopping and starting components of Cloud Lifecycle Management

This topic details the recommended order for stopping or starting virtual machines running Cloud Lifecycle Management components.

Note

Verify that all Cloud Lifecycle Management processes are stopped, before shutting down the virtual machines.

You must power off or power on the virtual machines in the following order.

One AR System server

Use the following stop and start order if you use the 4.x single AR System architecture. 

Stop order

You must power off the virtual machines in the following order:

  1. BMC Network Automation
  2. Mid Tier
  3. Atrium Web Registry 
  4. Cloud Portal and Database
  5. Platform Manager (OSGi)
  6. BMC Atrium Orchestrator
  7. BMC Server Automation and PXE

Start order

You must power on the virtual machines in the following order:

  1. BMC Server Automation and PXE
  2. BMC Atrium Orchestrator
  3. Platform Manager (OSGi)
  4. Cloud Portal and Database
  5. Atrium Web Registry
  6. Mid Tier
  7. BMC Network Automation

Two AR System servers

Use the following stop and start order if you still use the 2.1.x and 3.x Enterprise-AR and Cloud-AR architecture. 

Stop order

You must power off the virtual machines in the following order:

  1. BMC Network Automation
  2. Mid Tier
  3. Atrium Web Registry 
  4. Enterprise-AR 
  5. Platform Manager (OSGi)
  6. Cloud-AR
  7. BMC Atrium Orchestrator
  8. BMC Server Automation and PXE

Start order

You must power on the virtual machines in the following order:

  1. BMC Server Automation and PXE
  2. BMC Atrium Orchestrator
  3. Cloud-AR 
  4. Platform Manager (OSGi)
  5. Enterprise-AR 
  6. Atrium Web Registry
  7. Mid Tier
  8. BMC Network Automation

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*