Networking and Systems, Haverford College Computing Center

 Morning Check Routines

This form is intended for internal use ONLY.
Use this form to check and report the status of services HCACC provides to the college community.


System Requirements

The majority of Morning Checks consists of checking to make sure that dial-in access is working. Thus, a modem and dial-in configuration will be needed to perform the routine. For information regarding dial-in access & setup proceedures click here.

In order for you to be able to check and verify that our VPN Services are running, you will need a VPN account, a computer that has our VPN software installed on it, and access to a DSL (or Haverford's wireless) network. For information regarding VPN access click here.

Morning Checks

Currently, morning checks consist of 6 routines:

  • Web Pages
  • PC Network Services
  • Macintosh Network Services
  • VPN Network Services
  • Additional Networking Services
  • UNIX Servers

Since we need to check both Macintosh & PC Services, dial-in will need to be performed on both platforms. This document will point out to you when you need to be connected to the dial-in network via a Macintosh or PC inorder to perform the required checks.

User Information

Before we begin, please provide us with your Haverford e-mail USER ID.

User ID
 

Web Pages

You can connect with either the Macintosh or the PC to perform these checks

Checking Web Pages consists of viewing the pages listed below and clicking on 2 to 3 links on that page to make sure they aren't broken links. * Useful when checking links that point to other servers.

Pages that need to be checked are :

Status Service

 OK 

 FAIL 

 DID NOT TEST 

  Haverford's Home Page  

  OK 

  FAIL 

  DID NOT TEST 

  Tripod - The TriCollege Online Library Catalog, if services are down contact Adam Brin @ 610-526-5294, and let Norm Medeiros (x1173) know.

  OK 

  FAIL 

  DID NOT TEST 

  Trilogy - The TriCollege Library WebServer for all library resources, if services are down contact Adam Brin @ 610-526-5294 and let Norm Medeiros (x1173) know.

  OK 

  FAIL 

  DID NOT TEST 

  Tricolib - The ColdFusion Server for the Trico Library.  Houses databases that TriCollege Campuses use.  If services are down contact Adam Brin @ 610-526-5294 and let Norm Medeiros (x1173) know.

  OK 

  FAIL 

  DID NOT TEST 

  Triptych - The TriCollege Library Online Image Archive, if services are down contact Adam Brin @ 610-526-5294 and let Norm Medeiros (x1173) know.

  OK 

  FAIL 

  DID NOT TEST 

  Blackboard, if services are unexpectedly down contact Adam Brin @ 610-526-5294 and notify Liz Evans @ Swarthmore (eevans1@swarthmore.edu, 601-328-8254).

  OK 

  FAIL 

  DID NOT TEST 

  The TriCollege Selection Guide Search for a course you'd like to take.

  OK 

  FAIL 

  DID NOT TEST 

  Haverford's Administartive Computing page

  OK 

  FAIL 

  DID NOT TEST 

  PingMontior Down Hosts List

  OK 

  FAIL 

  DID NOT TEST 

  WebMail Home Page

  OK 

  FAIL 

  DID NOT TEST 

  Haverford's WebMail (SquirrelMail) Service  (nisc30.haverford.edu or nisc31.haverford.eduCheck your mail to make sure the service is working.

  OK 

  FAIL 

  DID NOT TEST 

  Haverford's WebMail (EmuMail) Service  (nisc8.haverford.edu)  Check your mail to make sure the service is working.

  OK 

  FAIL 

  DID NOT TEST 

  Haverford's CPanel (CP2) Administration Interface Check to make sure the service is working. Use your CPanel UserName and Password.

  OK 

  FAIL 

  DID NOT TEST 

  Web Forum

  OK 

  FAIL 

  DID NOT TEST 

  Mailman (list.haverford.edu)

  OK 

  FAIL 

  DID NOT TEST 

  Automated Account Creation Website (accounts.haverford.edu)

  OK 

  FAIL 

  DID NOT TEST 

  Student's Web Pages

  OK 

  FAIL 

  DID NOT TEST 

  External Websites:  Slashdot.orgGoogle NewsAvert Alerts

 

FTP Access to the Storage & Webpublish Servers

This check should be performed from a non-Haverford Network (use our DSL line).

FTP to the storage & webpublish servers to make sure you can access them from off campus.  If you cannot obtain an external network connection, perform this test from the Haverford Campus network to make sure that they are, at least, accessible.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  FTP to storage.haverford.edu  

  OK 

  FAIL 

  DID NOT TEST  

  FTP to webpublish.haverford.edu  

 

Storage & Web

Check the links below from Matt's test web page.

These checks ensure that the data served from pluto actually works. These tests basically ensure that NFS-mounted volumes are available, and that the links to those volumes work.

  • /home/web is from ACC.
  • /web are links that point to a volume form NISC11 (Storage).
  • /users/ is from NISC11 (Storage) ??? I'm not exactly sure how /users/ is setup in the Netscape config. I believe that its from NISC11 (Storage) : /vol1/users.
Status Service

  OK 

  FAIL 

  DID NOT TEST 

  via /home/web/mnocifor  

  OK 

  FAIL 

  DID NOT TEST 

  via /web/mnocifor  

  OK 

  FAIL 

  DID NOT TEST 

  via /users/m/mnocifor/public_web  

 

PC Networking - The Network Neighborhood

To perform this check, you'll need to dial-in from a PC.

This check ensures that servers are accessible from the dial-in network. In addition to connecting to the servers listed below, you should also transfer a file to and from the server in order to confirm you have establised connectivity.

Check connectivity to the following servers:

Status Service

  OK 

  FAIL 

  DID NOT TEST 

  Accserver1  

  OK 

  FAIL 

  DID NOT TEST 

  Accserver2  

  OK  

  FAIL 

  DID NOT TEST 

  ACC Databases  

  OK 

  FAIL 

  DID NOT TEST 

  Accprinters  

  OK  

  FAIL 

  DID NOT TEST 

  Storage Server - log in using your e-mail passwd  

  OK  

  FAIL 

  DID NOT TEST 

  Webpublish Server - log in using your e-mail passwd  

 

Macintosh Networking - The AppleTalk Network

To perform this check, you'll need to dial-in from a Macintosh.

This check ensures that Macintosh File Servers are accessible from the dial-in network. In addition to connecting to the servers listed below, (If you can) you should also transfer a file to and from the server in order to confirm that you have established connectivity.

You will need to use the Chooser application to connect to the servers listed below. These servers are all located in the "HC ACC Services" AppleTalk Zone. If you are unfamilar with AppleTalk Networking see the Using Chooser with the Network document.

Unless otherwise noted, used your e-mail username & network password to login.

Check connectivity to the following servers:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  storage.haverford.edu - login using your e-mail passwd  

  OK 

  FAIL 

  DID NOT TEST  

  webpublish.haverford.edu - login using your e-mail passwd  

As you check AppleTalk Services, make sure the following servers ARE NOT viewable: www2, www.students.haverford.edu, Gopher Server. If any of those servers are viewable from the Chooser's file server list, notify hcnet-staff immediately.

 

Dial-in Access

In order to check Dial-in services you will need access to a computer that has a modem and a proper dial-in configuration. For information regarding dial-in access and setup procedures click here.

Check Dial-in service:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  Dial-in Access  

 

VPN Access

In order to check VPN Services, you will need a VPN account and access to a PC or Mac that has our VPN Software, and is on a DSL network. For more information about using our VPN Service to connect to Haverford's Network click here.

You can use the naked PC in Operations 204a to administer this test.

Check VPN service:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  VPN Access  

 

Wireless VPN Access

In order to check Wireless VPN Services, you will need a computer that has a copy of our VPN Software installed on it and is connected to Haverford's Wireless Network.  No special VPN Account is needed to access the Wireless VPN, however a valid Haverford or BrynMawr email username & password is neccessary. 

Use Vasantha's BrynMawr email account & passwd to perform two tests in one.  (See next test)

Check VPN service:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  Wireless VPN Access  

 

Wireless VPN Access for non-Haverford, TriCollege Users (BrynMawr Users)

In order to check Wireless VPN Access for BrynMawr users, you will need a computer that has a copy of our VPN Software installed on it and is connected to Haverford's Wireless Network as well as a valid BrynMawr email username & password is neccessary. 

Use Vasantha's BrynMawr email account & passwd to perform this test.

Check VPN service:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  Wireless VPN Access for BrynMawr Users 

 

Streaming Server

In the summer of 2004 we rolled out a new version of RealMedia's Helix Streaming Server. The server now has the ability to stream a wide variey of media formats. Below are some checks to test each of the different media we're now able to stream.

You'll need a recent version of RealPlayer to administer this test.

Check streaming media:

Status Service

  OK 

  FAIL 

  DID NOT TEST  

 RealMedia Streaming Media File from the Music Library (test.rm)  

  OK 

  FAIL 

  DID NOT TEST  

 Synchronized Multimedia Integration Language File from Claude (1-02.smil)  

  OK 

  FAIL 

  DID NOT TEST  

 RealMedia Streaming file (vivalaford.rm)  

  OK 

  FAIL 

  DID NOT TEST  

 MPEG Audio Stream, Layer III file (erik.mp3)  

  OK 

  FAIL 

  DID NOT TEST  

 Macromedia Flash Format File (timeline.swf)  

  OK 

  FAIL 

  DID NOT TEST  

 MPEG 1 System Stream File (bear23.mpg)  

 

Additional Services - List Proc

This check can be performed from any (?) mail client.

This check ensures that the List Proc Server is actively listening and processing requests.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  The List Proc   Compose a message to xyz@haverford.edu, verify that you (or someone on that list) receives this message...

 

Other Network Services - The Keyserver

This check should be performed by dialing-in with both a Macintosh & PC.

This checks ensures that the Keyserver is accessible from the dial-in network, and that keyed applications can be ran while dialed-in.

You will need a Keyed Application to run and see if connectivity with the Keyserver is possible (Photoshop or Claris HomePage).

Launch a Keyed Application. Confirm that the KeyAccess client "checks out" an available license and that the application runs without further intervention.

For more information about our KeyServer, see the Sassafras KeyServer Document page.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  The KeyServer  

 

Viruses Alerts:

This check can be performed from any network.

This check reports Network Associates current risk level. For more information about Network Associates risk levels please click here.

Service Status

AVERT Virus Alert

High-Outbreak 

High 

Medium-On-Watch 

Medium 

Low-Profiled 

Low 

N/A

Security HQ
Virus Advisory

High-Outbreak 

High 

Medium-On-Watch 

Medium 

Low-Profiled 

Low 

N/A

 

Checking the mail & smtp servers for black listing:

This check can be performed from any network.

These checks ensure that our mail server has not been placed on an SMTP black list.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  MS2 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST 

  drbcheck. Contact Matt if we appear on more than 3 black lists.

  OK 

  FAIL 

  DID NOT TEST  

  SMTP1 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST  

  SMTP2 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST  

  NISC3 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST  

  NISC4 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST  

  NISC14 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

  OK 

  FAIL 

  DID NOT TEST  

  NISC17 Spam Database Lookup. Report this test as FAIL if we appear on any lists (usually marked in red). Notify Matt if we appear on ANY lists.

 

Checking Sendmail & the MailScanner(s)

From: "Vasantha Narayanan" 
Subject: morning checks
Date: Wed, February 23, 2005 5:46 pm
To: rhinojos@smtp2.haverford.edu


During your morning checks, could you please check to see if sendmail is 
running with the -bd option on smtp1, smpt2, ms1, nisc4.

I'll write up about the other checks.  Also do, ps -ef | grep MailScanner 
on smtp1, nisc4 and smtp2 and make sure they are running.

I'll write everything in detail.

Thanks.

Vasantha


VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
Vasantha Narayanan
Networking and Systems                  email: vnarayan@haverford.edu
Haverford College, PA                   Phone: 
610-896-1110

Log into our mail scanners and execute the following commands:

  • ps -ef | grep sendmail
    Look for entries like the following:
        root 16346   213  0 10:16:51 ?        0:00 /usr/lib/sendmail -bd -ODeliveryMode=queueonly -OQueueDirectory=/smtp/inq -ORef
  • ps -ef | grep MailScanner
    Look for entries like the following:
        root 18111 21470  2 10:21:22 ?        0:01 /nsr/perl5.8.0/bin/perl -I/opt/MailScanner/lib /opt/MailScanner/bin/MailScanner
  • uptime
    Make sure the system hasn't rebooted itself. Look for an uptime greater than 6 or 10 hours
     10:21am  up 5 day(s),  6:55,  3 users,  load average: 8.65, 8.55, 7.67

Vasantha has provided the following document, MailSystem Overview, which provides further documentation about our complicated mail system.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  Sendmail & MailScanner(s) Status 

 

Stokes 204Y (Network Core) environment

This check requires you to walk into Stokes 204Y and simply check the temperature and humidity levels to make sure that they're within a certain "Recommended Operating Environment".

The "Recommended Operating Environment" is as follows:

  • Abmient temperature = 41°F - 105°F.
  • Relative humidity = 10% - 90% RH.

Note: the values above are from one type of equipment, we're making the assumption that the values above can be applied to the entire room.

If the environment values are outside the specifications, notify Gloria Davis @ Facilities Management and alert hcnet-staff.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  Stokes 204Y (Network Core) Environment Status 

 

DNS Timing

This check provides us with a letter grade representing how long it took to lookup www.haverford.edu.

If the response is less than an C-, there is a problem with NISC1 (its acting slower than usual).  What you really want to look at is the average response time for all name servers. If the response time is more than 20 milliseconds and the score is less than a C, then there is a problem.  To fix, kill the process in.named and restart it.

Status Service

  OK 

  FAIL 

  DID NOT TEST  

  DNS Timing for www.haverford.edu

 

UNIX Servers

You CANNOT access these via dial-in.

This check ensures that login access is available on our UNIX Servers, and the the servers are up and running. This check is not meant to be an exhaustive check of the servers, just a quick check to make sure they are available.

Telnet to the following servers:

Core Servers
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  ms2.haverford.edu (mail)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc11.haverford.edu (Storage)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc27.haverford.edu (WebPublish)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc19.haverford.edu (web server) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc18.haverford.edu (standby web server) 

  OK 

  FAIL 

  DID NOT TEST  

  acc.haverford.edu (NIS+ Master & FTP) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc25.haverford.edu (MySQL Server) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc20.haverford.edu (MailMan & Automated Account Creation Server) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc12.haverford.edu (Streaming Server) 

Mail Sub-System
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  smtp1.haverford.edu (mail scanner) 

  OK 

  FAIL 

  DID NOT TEST  

  smtp2.haverford.edu (mail scanner) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc3.haverford.edu (mail scanner) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc4.haverford.edu (mail scanner) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc14.haverford.edu (mail scanner) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc17.haverford.edu (mail scanner) 

WebMail Systems
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  nisc8.haverford.edu (EmuMail)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc31.haverford.edu (SquirrelMail)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc30.haverford.edu (standby SquirrelMail)  Use SSH. 

Older Systems
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  pluto.haverford.edu (Student Web Server & CGI) 

  OK 

  FAIL 

  DID NOT TEST  

  unixmail.haverford.edu  

  OK 

  FAIL 

  DID NOT TEST  

  trico.haverford.edu  

  OK 

  FAIL 

  DID NOT TEST  

  tripod.brynmawr.edu  

  OK 

  FAIL 

  DID NOT TEST  

  nisc1.haverford.edu (DHCP & DNS) 

Virus Update Systems
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  nisc23.haverford.edu (virus-update) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc24.haverford.edu (virus-update) 

Backup Systems
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  nisc16.haverford.edu (SAN Backups)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  backup.haverford.edu (NFS Backups)  No DNS entry, use temp IP 165.82.1.130

Other Systems
Status Service

  OK 

  FAIL 

  DID NOT TEST  

  nisc26.haverford.edu (LDAP)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  cp2.haverford.edu (CPanel Server)  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc13.haverford.edu 

  OK 

  FAIL 

  DID NOT TEST  

  nisc9.haverford.edu  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc15.haverford.edu (Isolated Network DHCP & DNS) 

  OK 

  FAIL 

  DID NOT TEST  

  nisc10.haverford.edu (Nessus Scanner)  Incorrect DNS entry, use temp IP 165.82.112.9

  OK 

  FAIL 

  DID NOT TEST  

  nisc33.haverford.edu  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc34.haverford.edu  Use SSH. 

  OK 

  FAIL 

  DID NOT TEST  

  nisc35.haverford.edu  Use SSH. 

 

Submit Results

Click the  button to submit the results of your morning checks.

Click the  if you would like to clear the values you've selected and restart the morning check proceedures.