Differences

This shows you the differences between two versions of the page.

--- sysadmin:procedures:labs [2015/01/26 19:23] – kjohns23
+++ sysadmin:procedures:labs [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Lab Monitor Checklist ======
-===== Lab Inspection Procedure =====
-The lab monitors are expected to perform an inspection of their assigned labs three times a week. Please choose you inspection times such that they will not conflict with any scheduled labs. During your inspection of the lab, please check that all of the lab machines that are currently not being used by a student are functioning properly. If a student is sitting in front of a machine but not using it then skip the check of that machine. When you have completed your inspection of the labs please send a report as detailed below.
-===== Reporting problems with lab equipment =====
-If you find a piece of lab equipment that is broken, or otherwise needs attention from a System Administrator, then please open a ticket in the School of Computer Science Request Tracking system. This can most easily be done by sending an email to help@socs.uoguelph.ca (remember that the email must come from your @uoguelph.ca email address). Please include the following information in the ticket:
-  *Machine ID
-  *Location
-  *Description of Problem
-  *For SUNRays if the problem is not with the SUNRay itself please include the server that the unit is connected to along with the connection status code.
-  *Any other information that you think is relevant.
-===== Lab check report =====
-After every check of the computer labs, send an email to labstatus@socs.uoguelph.ca. This is a privately archived mailing list containing the lab monitors, system administrators, and the director. The purpose of this report is to provide us with a record of what you saw in the lab and when you saw it. If anything was to come up after you last walk though, this will allow us to place a time frame on the incident and act appropriately. Please include the following information on the lab report:
-  *Approximate time of you lab walk through
-  *Which labs you checked
-  *Ticket numbers of any tickets you created for this walk though.
-  *A brief description of anything that you observed that needs reporting yet doesn't require a ticket. (ie. Offensive language/pictures on the white boards)
-  *Indicate if you removed any offensive material or not
-  *If everything is fine indicate that as well.
-====== Lab Inspection Checklist ======
-===== All Labs =====
-  *Report any offensive messages or pictures in the lab, including which lab and roughly where it was (ie. written/drawn on a whiteboard, vs. a piece of paper taped to the wall etc.). Also indicate if you removed the message/image.
-  *Report any damage to lab equipment, furniture, walls, etc.
-  *Report any inappropriate behaviour that you observe (if it's really bad, call the campus police).
-  *Report any disgusting/greesy tables
-  *Throw out any small pieces of garbage that you find in the lab.
-  *Bring any items that you would consider to be "lost and found" to Deb Byart in Reynolds 114
-===== Thornbrough Labs =====
-  *Close any open floor covers. Please report any open covers in 2420 or 3401.
-===== Thornbrough 3401 =====
-Make sure that the projector is off.
-Make sure that the door is closed and locked
-Make sure that the lights are on (switches are beside the screen)
-Make sure that all of the floor covers are closed (report if you found any open, we want to know if any were opened, but we don't care which ones were opened, unless you see a pattern).
-===== Thornbrough 2418 =====
-  *Monitor and report any engineering or other non-SoCS students using the room.
-===== Thornbrough 2420 =====
-  *Make sure that 2421 (The room of Requirement) is locked.
-  *Make sure that the latching pins on both doors to the room are extended.
-  *Make sure that the board lights are off. The switch is to the left of the white board.
-  *Make sure that the room lights are on. The switches are to the right of the while board.
-  *Make sure that the screen is up. The switch is beside the light switches.
-  *Make sure that the projector is off.
-  *Monitor and report any engineering or other non-SoCS students using the room.
-===== Reynolds Labs =====
-  *Make sure that all of the doors to the labs are unlocked.
-====== Notes for Various Pieces of Equipment ======
-This should really be a series of separate articles, but they are put here for now for the reference of the Lab Monitors.
-===== SUNRays =====
-If the SUNRay is frozen at the booting screen press Stop+O or Ctrl+Pause+O (The letter O), to bring up the On Screen display. The on-screen display contains three vital stats about the SUNRay. It contains the information about the SUNRay itself on the left side of the screen, information about the SUNRay Server on the right of the screen, and a status code in the bottom right corner.
-Various error conditions shown by the OSD and how to address them:
-Left side has no IP Address. Usually this means that the unit doesn't have a network connection. Make sure that the network cable is plugged in.
-Right side doesn't have an IP Address. Most likely this means that the DHCP Relay has gone down (Thornbrough only).
-Both sides have IP addresses. This indicated a problem with the SUNRay Server. The status code will give more information (It's usually 26D in this situation).
-If you need to open a ticket for a failed SUNRay. Please include the following information (If applicable):
-The SUNRay's unit ID
-The Server that the SUNRay is connected to:
-.104.48.11 = Snape
-.104.48.12 = Dumbledore
-.104.48.13 = Potter
-.104.48.14 = Weasley
-.104.48.15 = Granger
-.104.48.16 = Longbottom
-The Status Code
-===== Macs =====
-If a Mac won't turn on check its power cord. They occasionally come unplugged.