 |
 |
John, Excellent ideas! I had a short message back from AIS on this. Just a "thanks for the comment", no indication on the possibility of forwarding info to this list. On a related topic, I thought we had agreed that new postings to http://help.msu.edu/status/ should be copied to this list. But I see there were several updates last week on the webpage. Perhaps the "right people" haven't signed onto this idea yet? Maybe this could be a topic at today's NAG meeting? thank you -John LeTourneau, John wrote: >That would be a good start. > >What could be even better is if 1) all the MSU critical systems are defined, >e.g., SIS, email, the network, Advance 2) A status site is created for ALL >MSU critical systems (not just computer lab systems) 3) Information is >posted to the site whenever there is an incident, outage, denial of service >involving one of the systems 4) A message is sent to the NAG whenever >something is added to the status site. > >Something of this nature would be very helpful for us. It may not be able to >get a status out in real time, especially if you can't get to the site. But >after the network, or whatever, comes back on line we would have some real >information instead of word-of-mouth like what is being passed around on the >denial of service attack yesterday morning. > > -----Original Message----- >From: John Valenti [mailto:[log in to unmask]] >Sent: Tuesday, September 16, 2003 12:22 PM >To: [log in to unmask] >Subject: [Fwd: FW: Status on SIS outage: 9/15/03] > > << Message: FW: Status on SIS outage: 9/15/03 >> hi, > >This message was forwarded to me indirectly via our Director. This type >of information is always very helpful for my job. Would it be possible >to include the MSU network administrator's mailing list >([log in to unmask]) for future mailings of this type? I'm pretty sure >other campus administrators would also find this useful info. > >You might need to subscribe to the list to enable sending messages to it. > >thank you! >John Valenti >Systems Analyst, LIR > >