anchor.diff:    <pre class="terminal">
     $ find /var/tempest/workspaces/default/deployments -name cf-*.yml
     </pre>
  -  Then run `bosh deployment` to select a specific deployment: 
  -  <pre class="terminal">
  -  $ bosh deployment PATH-TO-CF-DEPLOYMENT-YML
  -  </pre>
  -  For example:
  -  <pre class="terminal">
  -  $ bosh deployment /var/tempest/workspaces/default/deployments/cf-85fc9f0eb5a916dfaf82.yml
  -  Deployment set to '/var/tempest/workspaces/default/deployments/cf-85fc9f0eb5a916dfaf82.yml' 
  -  </pre>
   
   1. Run the following command:
  -  <pre class="terminal">
  -  $ bosh start
  +  <pre>
  +  bosh -e MY-ENV -d MY-DEPLOYMENT start
     </pre>
  -  This command starts all VMs in the deployment. When complete, the command outputs an `all jobs started` message.
  +  Replace the text above with the following:
  +  * `MY-ENV`: the alias you set for the BOSH Director.
  +  * `MY-DEPLOYMENT`: the name of your deployment.
  +
  +    For example:
  +    <pre class="terminal">
  +    $ bosh -e prod -d mysql start
  +    </pre>
  +    This command starts all VMs in the specified deployment.
   
   1. If you require [high availability](../concepts/high-availability.html) in your deployment, scale up all instance groups to the original or desired counts.
   
  
positive.code: ---
  
  <strong><%= modified_date %></strong>
  
  This topic describes stopping and starting the component virtual machines (VMs) that make up a <%= vars.first_product_name %> deployment. 
  
  
negative.code: 
  ### <a id='get-names'></a>Find the Names of Your <%= vars.product_short %> Virtual Machines ##
  
  You need the full names of the VMs to stop and start them using the BOSH CLI. To find full names for the VMs running each component, run `bosh -e MY-ENV instances`, replacing `MY-ENV` with the alias you set for your BOSH Director. To filter the list of instances by deployment, run `bosh -e MY-ENV -d MY-DEPLOYMENT instances`.
  
  For example:
  
  <pre class="terminal">
  $ bosh -e prod -d mysql instances
  ...
  Deployment 'mysql'
  
  Instance                    Process State  AZ  IPs
  mysql/0123-abcd-4567ef89    running        -   10.244.0.6
  mysql/abcd-0123-ef4567ab    running        -   10.244.0.2
  
  2 instances
  ...
  </pre>
  
  You can see the full name of each VM in the `Instance` column of the terminal output. Each full name includes:
  
  * A prefix indicating the component function of the VM.
  
  * An identifier string specific to the VM.
  
  For any component, you can look for its prefix in the `bosh instances` output to find the full name of the VM or VMs that run it.
  
  ### <a id='stop'></a>Stopping an Individual <%= vars.product_short %> VM##
  
  To stop a job, run the following command for the component in your <%= vars.product_short %> deployment, replacing `MY-ENV` with the alias you set for your BOSH Director and `MY-DEPLOYMENT` with the name of the deployment:
  <pre>bosh -e MY-ENV -d MY-DEPLOYMENT stop VM-NAME</pre>
  
  To delete the instance that contains the job, run the following command for the component in your <%= vars.product_short %> deployment:
  <pre>bosh -e MY-ENV -d MY-DEPLOYMENT stop VM-NAME --hard</pre>
  
  Use the full name of the component VM as listed in your `bosh instances` [terminal output](#term-bosh-vms) without the unique identifier string.
  
  For example, the following command stops the Loggregator Traffic Controller job:
  
  <pre class='terminal'>
  $ bosh -e prod -d loggregator stop loggregator_trafficcontroller
  </pre>
  
  To stop a specific instance of a job, include the identifier string at the end of its full name.
  
  For example, the following command stops the Loggregator Traffic Controller job on only one Diego cell instance: 
  
  <pre class="terminal">
  $ bosh -e prod -d loggregator stop loggregator_trafficcontroller/0123-abcd-4567ef89
  </pre>
  
  To delete the VM, include `--hard` at the end of the command. This command does not delete persistent disks.
  
  For example, the following command deletes a specific Loggregator Traffic Controller instance:
  
  <pre class="terminal">
  $ bosh -e prod -d loggregator stop loggregator_trafficcontroller/0123-abcd-4567ef89 --hard
  </pre>
  
  ### <a id='start'></a>Starting an Individual <%= vars.product_short %> VM ##
  
  Run the following command for the component in your <%= vars.product_short %> deployment you wish to start, replacing `MY-ENV` with the alias you set for your BOSH Director and `MY-DEPLOYMENT` with the name of the deployment. Use the full name of the component VM as listed in your `bosh vms` [terminal output](#term-bosh-vms) without the unique identifier string.
  
  <pre>bosh -e MY-ENV -d MY-DEPLOYMENT start VM-NAME</pre>
  
  The following example command starts the Loggregator Traffic Controller VM:
  
  <pre class="terminal">
  $ bosh -e prod -d loggregator start loggregator_trafficcontroller
  </pre>
  
  To start a specific instance of a VM, include the identifier string at the end of its full name.
  
  For example, the following command starts the Loggregator Traffic Controller job on one Diego cell instance:
  
  <pre class='terminal'>
  $ bosh -e prod -d loggregator start loggregator_trafficcontroller/0123-abcd-4567ef89
  </pre>
  