anchor.diff:  
   The goal is to
   
  -* install the LAMP stack on your nervios instance
  -* install the Nagios server on your nervios instance
  +* install the LAMP stack on your nerviosXX instance
  +* install the Nagios server on your nerviosXX instance
   * configure Nagios to monitor servers in the pipeline
   * confirm that the pipeline is being monitored
   * test monitoring by halting one or more servers and observing the result
  -* expand monitoring to cover Apache Tomcat on the caraxx server, and Jenkins on hombrosxx..
  +* expand monitoring to cover Apache Tomcat on the cara1 server, and Jenkins on hombros1.
   * test the expanded monitoring
  +
  +NOTE: As of Spring 2017, due to server capacity issues, this lab will have many nerviosXX servers monitoring the main pipeline. Do not launch your own caraXX servers.
   
   === Steps
   WARNING: READ THIS ENTIRE LAB CAREFULLY BEFORE STARTING. IF YOU JUST LAUNCH INTO THE STEP BY STEP INSTRUCTIONS YOU WILL REGRET IT WHEN YOU GET A FEW PARAGRAPHS FURTHER. BE SURE YOU UNDERSTAND EVERYTHING.
  
positive.code: 
  Take a screen shot; combine it with your previous screen shot (e.g. in Powerpoint or as a PDF) and post to https://seis660.slack.com/messages/lab-06[Slack].
  
  Restart cara (vagrant up caraxx.) Confirm that monitoring shows it is up.
  
  You can change the speed with which Nagios detects a down server through a parameter change. At your option, research the https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/objectdefinitions.html#host[instructions] and do so.
  
  
negative.code: 
  Take a screen shot and post to Slack.
  
  Test that your monitoring is working correctly by asking the instructor to suspend the cara server (we may have to coordinate this with the class as everyone is looking at the same server; hopefully people will arrive at this point at different times.)
  
  In 5 minutes, you should see an error on the web portal, like this:
  
  