anchor.diff:  
   Also `bosh deploy` will stop at `Binding existing deployment` stage since it is not able to communicate with unresponsive agent:
   
  -<pre class="terminal">
  -bosh deploy
  +<pre class="terminal wide">
  +$ bosh deploy
   
   ..snip...
   
  
positive.code: Next: [Automatic repair with Resurrector](resurrector.html)
  
  Previous: [Process monitoring with Monit](vm-monit.html)
  
negative.code: 
  cck determined that `i-914c046a` VM was missing. Possible options are:
  
  1. `Skip for now`: the Director will not try to resolve this problem right now
  
  2. `Recreate VM`: the Director will just create new VM, deploy specified releases according to deployed manifest and finally start release jobs
  
      Note on current behaviour: cck will not wait for all release job processes to start.
  
  3. `Delete VM reference`: the Director will not create new VM in its place. If cck is run again, it will not report that VM is missing since it's not expected to exist. Running `bosh deploy` after cck will backfill missing VMs.
  
  In the above example options 3 was picked and VM reference was deleted.
  
  ---
  ### <a id="not-responsive-vm"></a> VM is not responsive (unresponsive agent)
  
  Assuming there was a deployment with a VM, somehow Agent is no longer responding to the Director. In this situation `bosh vms` will report VM's agent as `unresponsive agent`:
  
  <pre class="terminal wide">
  $ bosh vms simple-deployment --details
  
  Deployment `simple-deployment'
  
  