[25674] in Hotline Meeting

home help back first fref pref prev next nref lref last post

RE:WHOI problem

daemon@ATHENA.MIT.EDU (jjmorey@MIT.EDU)
Wed Nov 23 07:29:13 1994

From: jjmorey@MIT.EDU
To: hotline@MIT.EDU
Date: Wed, 23 Nov 1994 07:28:57 EST


------- Forwarded Message

Received: from MIT.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA20422; Tue, 22 Nov 94 17:42:46 EST
Received: from BIGREDONE.MIT.EDU by MIT.EDU with SMTP
	id AA20066; Tue, 22 Nov 94 17:42:33 EST
Message-Id: <9411222242.AA20066@MIT.EDU>
Date: Tue, 22 Nov 94 17:42:49
From: burke@MIT.EDU (Jerry Burke)
To: "Naomi B. Schmidt" <nschmidt@MIT.EDU>
Subject: Re: How should this have been handled?
Cc: op@MIT.EDU, dcns-cluster@MIT.EDU

Hi Naomi,


I have to get more history:

But we have an escalation process:

If it is not a hardware repair nor a hacked system. We refer to ops. The 
network help-desk should not be involved in this at all, since this is 
(WHOI's) their own supported network. I believe ops should handle this 
one, since they (WHOI) are setup in a special way.

I don't know why it did not get to ops. I will find out.

I reported to op. This evening, it is in hotline and will remain open 
until ops let's us know the resolution.


                                Thanks, Jerry

To: burke@MIT.EDU, kim@MIT.EDU
Subject: How should this have been handled?
Date: Tue, 22 Nov 1994 11:26:44 EST
From: "Naomi B. Schmidt" <nschmidt@MIT.EDU>


It sounds like Eric moved a workstation, which he probably shouldn't 
have. 
But then (at least as he tells it) he was given a run-around between 
hotline,
system support, and network folks.  How should we have handled this so 
that
he didn't go to OLC as a last resort?  Or did he just misunderstand what 
we
were telling him?

                        Naomi

- ------- Forwarded Message

Received: from MIT.MIT.EDU by po6.MIT.EDU (5.61/4.7) id AA05382; Tue, 22 
Nov 94 11:07:51 EST
Received: from PEARL.WHOI.EDU by MIT.EDU with SMTP
        id AA00386; Tue, 22 Nov 94 11:07:39 EST
Received: by pearl.whoi.edu.whoi.edu (4.1/SMI-4.1)
        id AA09839; Tue, 22 Nov 94 11:07:35 EST
Date: Tue, 22 Nov 94 11:07:35 EST
From: eric@pearl.whoi.edu.whoi.edu (Eric Cunningham)
Message-Id: <9411221607.AA09839@pearl.whoi.edu.whoi.edu>
To: jjmorey@MIT.EDU
Subject: Re: Hardware Problem?
Cc: hotline@MIT.EDU, nschmidt@MIT.EDU, ecunningham@whoi.edu


> I was notified by OLC that someone from WHOI had called them 
> about a system that was moved and that the system was having 
> problems coming back up.  From the description it sounds like
> the same problem you where having with menhaden in Oct.  Are
> you aware of this situation?  And any problems with the Hardware
> or software at WHOI in the future, need to be called into the 
> Athena hardware hotline 253-1410 not OLC. 

This is the same problem that first I reported in October re:
menhaden.  The system is up now, but because I need to include
new gateway info in menhaden's local rc.net, I still have the
problem that any software downloads/upgrades wipe my local changes
and require that I re-edit my local file.  Since this is a 
maintenance headache that can be avoided (simply, I thought) I'm 
still trying to get the correct gateway info in place at MIT so
software downloads will include the info needed by menhaden to 
boot automatically w/out my having to edit anything (like it used 
to be before menhaden was moved). 

The only reason OLC was dragged into this was because I couldn't
get anywhere w/hotline since it is net folks' problem and they
offer no solution for this since it is felt to be system support
folks' problem; system support folk say to wait for a future
software release.  Someone along the line suggested I use OLC for
this.  So, I think I've involved just about everyone there is at
this point!

- ------- End of Forwarded Message

------- End of Forwarded Message


home help back first fref pref prev next nref lref last post