anchor.diff:  
   ### <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 vms`:
  +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`.
   
  -<pre id='term-bosh-vms' class='terminal'>
  -$ bosh vms
  -Acting as user 'director' on 'p-bosh'
  -Deployment 'cf-85fc9f0eb5a916dfaf82'
  +For example:
   
  -Director task 57
  +<pre class="terminal">
  +$ bosh -e prod -d mysql instances
  +...
  +Deployment 'mysql'
   
  -Task 57 done
  +Instance                    Process State  AZ  IPs
  +mysql/0123-abcd-4567ef89    running        -   10.244.0.6
  +mysql/abcd-0123-ef4567ab    running        -   10.244.0.2
   
  -+------------------------------------------------------------------------+---------+---------+-------------+--------------+
  -| VM                                                                     | State   | AZ      | VM Type     | IPs          |
  -+------------------------------------------------------------------------+---------+---------+-------------+--------------+
  -| clock_global/0 (cc0d1565-4cd9-4755-bf4d-6cee28c927be)                  | running | default | micro       | 10.85.19.95  |
  -| cloud_controller/0 (8044ba6e-eafc-4b9b-88dc-05bbad23b54b)              | running | default | medium.disk | 10.85.19.94  |
  -| cloud_controller_worker/0 (7c52315f-4511-4974-a219-0fa138014779)       | running | default | micro       | 10.85.19.102 |
  -| consul_server/0 (373ca095-743d-426f-8b0f-2ef81c342bed)                 | running | default | micro       | 10.85.19.96  |
  -| diego_brain/0 (28a95c33-d674-4574-b9bf-93a79b00a116)                   | running | default | small       | 10.85.19.109 |
  -| diego_cell/0 (b28456b5-2a4c-4864-ab03-34319bbe3d6d)                    | running | default | xlarge.disk | 10.85.19.103 |
  -| diego_cell/1 (0e98201b-e0b1-4bc4-bc67-a23445801a3c)                    | running | default | xlarge.disk | 10.85.19.104 |
  -| diego_cell/2 (7c52c961-07ba-4581-ad91-46c474523e36)                    | running | default | xlarge.disk | 10.85.19.107 |
  -| diego_database/0 (73f7482d-c0db-481a-8151-b6f90f83dc78)                | running | default | micro       | 10.85.19.92  |
  -| doppler/0 (9bab3c16-cb99-4c9a-bbb0-af7212d4989b)                       | running | default | micro       | 10.85.19.108 |
  -| ha_proxy/0 (941b9178-c1c4-4368-a89c-18e138922fd0)                      | running | default | micro       | 10.85.19.254 |
  -| loggregator_trafficcontroller/0 (92d8df76-9c03-4c0e-9cab-4bab132bce28) | running | default | micro       | 10.85.19.110 |
  -| mysql/0 (14929f8e-1f06-4755-9242-2e7935e86407)                         | running | default | large.disk  | 10.85.19.101 |
  -| mysql_monitor/0 (d917d44f-33e5-4ad2-8b1c-347b3c46b646)                 | running | default | micro       | 10.85.19.106 |
  -| mysql_proxy/0 (1f9372af-d8c9-4189-a95f-899ad1c0a27b)                   | running | default | micro       | 10.85.19.100 |
  -| nats/0 (ee37f28c-c7c4-4506-a19d-5992902daa29)                          | running | default | micro       | 10.85.19.97  |
  -| nfs_server/0 (91fc3c0f-40fb-4c7b-9cb5-8ca8dc68c967)                    | running | default | medium.mem  | 10.85.19.99  |
  -| router/0 (9f7cf9d4-b870-4ccc-9915-77c675261bd4)                        | running | default | micro       | 10.85.19.105 |
  -| uaa/0 (099e43d1-9dc5-4e27-b602-3beea8e40b3d)                           | running | default | medium.disk | 10.85.19.93  |
  -+------------------------------------------------------------------------+---------+---------+-------------+--------------+
  -
  -VMs total: 20
  +2 instances
  +...
   </pre>
   
  -You can see the full name of each VM in the `Job/index` column of the terminal output. Each full name includes:
  +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.
   
  -* An `/INDEX` suffix. For component processes that run on a single VM instance, INDEX is always 0. For processes running on multiple VMs, `INDEX` is a sequentially numbered value that uniquely identifies each VM.
  -
  -For any component, you can look for its prefix in the `bosh vms` output to find the full name of the VM or VMs that run it. In the example shown here, the full name of one of the three Diego Cell VMs is `diego_cell/2`.
  +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 an individual VM, run `bosh stop VM-NAME` for the component in your <%= vars.product_short %> deployment. 
  +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>
   
  -Use the full name of the component VM as listed in your `bosh vms` [terminal output](#term-bosh-vms), without the `/INDEX` at the end. 
  +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>
   
  -For example, the following command stops the Loggregator Traffic Controller VM:
  +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 stop loggregator_trafficcontroller
  -
  -Acting as user 'director' on deployment 'cf-85fc9f0eb5a916dfaf82' on 'p-bosh'
  -
  -You are about to stop loggregator_trafficcontroller/*
  -
  -Detecting deployment changes
  -----------------------------
  -Stop loggregator_trafficcontroller/*? (type 'yes' to continue): yes
  -
  -Performing 'stop loggregator_trafficcontroller/*'...
  -
  -Director task 58
  -  Started preparing deployment > Preparing deployment. Done (00:00:01)
  -
  -  Started preparing package compilation > Finding packages to compile. Done (00:00:00)
  -
  -  Started updating instance loggregator_trafficcontroller > loggregator_trafficcontroller/92d8df76-9c03-4c0e-9cab-4bab132bce28 (0) (canary). Done (00:00:07)
  -
  -Task 58 done
  -
  -Started   2017-03-21 17:24:28 UTC
  -Finished  2017-03-21 17:24:43 UTC
  -Duration  00:00:15
  -
  -loggregator_trafficcontroller/* stopped, VM(s) still running
  +$ bosh -e prod -d loggregator stop loggregator_trafficcontroller
   </pre>
   
  -To stop a specific instance of a VM, include the <code>/INDEX</code> at the end of its full name. 
  +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 only the third Diego Cell instance: 
  +For example, the following command stops the Loggregator Traffic Controller job on only one Diego cell instance: 
   
  -<pre class='terminal'>
  -$ bosh stop diego_cell/2
  +<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 `bosh start VM-NAME` for the component in your <%= vars.product_short %> deployment you wish to start. Use the full name of the component VM as listed in your `bosh vms` [terminal output](#term-bosh-vms), without the `/INDEX` at the end. 
  +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 start loggregator_trafficcontroller
  -Acting as user 'director' on deployment 'cf-85fc9f0eb5a916dfaf82' on 'p-bosh'
  -
  -You are about to start loggregator_trafficcontroller/*
  -
  -Detecting deployment changes
  -----------------------------
  -Start loggregator_trafficcontroller/*? (type 'yes' to continue): yes
  -
  -Performing 'start loggregator_trafficcontroller/*'...
  -
  -Director task 59
  -  Started preparing deployment > Preparing deployment. Done (00:00:02)
  -
  -  Started preparing package compilation > Finding packages to compile. Done (00:00:00)
  -
  -  Started updating instance loggregator_trafficcontroller > loggregator_trafficcontroller/92d8df76-9c03-4c0e-9cab-4bab132bce28 (0) (canary). Done (00:00:50)
  -
  -Task 59 done
  -
  -Started   2017-03-21 17:25:16 UTC
  -Finished  2017-03-21 17:26:15 UTC
  -Duration  00:00:59
  -
  -loggregator_trafficcontroller/* started
  +$ bosh -e prod -d loggregator start loggregator_trafficcontroller
   </pre>
   
  -To start a specific instance of a VM, include the <code>/INDEX</code> at the end of its full name. 
  +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 only the first Diego Cell instance: 
  +For example, the following command starts the Loggregator Traffic Controller job on one Diego cell instance:
   
   <pre class='terminal'>
  -$ bosh start diego_cell/0
  +$ bosh -e prod -d loggregator start loggregator_trafficcontroller/0123-abcd-4567ef89
   </pre>
  -
  -
  -
  
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: 
  This procedure uses the BOSH Command Line Interface (BOSH CLI). <%= vars.bosh_cli_link %>
  
  <%= vars.bosh2_sub %>
  
  ## <a id='startstop'></a>Stopping and Starting All <%= vars.product_short %> VMs
  
  This section describes how to stop and start all the VMs in your deployment.
  
  ### <a id='stop_all'></a> Stopping All <%= vars.product_short %> VMs
  
  To shut down all the VMs in your deployment, perform the following steps:
  
  1. Scale down the following jobs to one instance:
     * consul\_server
     * mysql
     <% if vars.product_name == 'CF' %>* etcd\_tls\_server<%else%><%end%>
  
  1. Run the following command for each of the deployments listed in the previous step:
    <pre>
    bosh -e MY-ENV -d MY-DEPLOYMENT stop --hard
    </pre>
    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 stop --hard
      </pre>
      This command stops all VMs in the specified deployment. The `--hard` flag instructs BOSH to delete the VMs but retain any persistent disks.
  
  ### <a id='start_all'></a> Starting All <%= vars.product_short %> VMs 
  
  