[56448] in Hotline Meeting
Part 2, RE: Chris
daemon@ATHENA.MIT.EDU (Joan M. Cyr)
Mon Sep 17 11:58:52 2001
Message-Id: <200109171558.LAA11350@melbourne-city-street.mit.edu>
Date: Mon, 17 Sep 2001 12:00:10 -0400
To: iggy@MIT.EDU
From: "Joan M. Cyr" <jcyr@MIT.EDU>
Cc: LARUGSI@MIT.EDU, hotline@MIT.EDU, iggy@MIT.EDU, vdist-repl@MIT.EDU,
3help@MIT.EDU, cg@MIT.EDU
Mime-Version: 1.0
Content-Type: multipart/alternative;
types="text/plain,text/html";
boundary="=====================_12908902==_.ALT"
--=====================_12908902==_.ALT
Content-Type: text/plain; charset="us-ascii"
Alicia...
I had a chance to talk to Dave (JCI) regarding this issue. If you read below,
you will see the reason why he had trouble finding the jack. One of the first
emails about this trouble, which is shown below, identifies the jack as
1-142-84-2. The subject of the email directly below correctly identifies the
jack as 1-142-48 (PORT #2).
It seems that Chris provided the incorrect jack information on this trouble to
begin with, and that is the reason why Dave could not find the jack.
Please remind your team to double check the info they provide to the
helpdesk.
This will help us shoot the troubles faster and get the customer back in
service.
Dave did ask me to pass on some crucial info about this area....he said the
reason that jack went into trouble is because whoever installed it installed
too much extra cable (service loop presumably) possibly in order to work the
jack outside, and then coiled and shoved the cable into the wall, pinching the
cable and forcing the faceplate on. He said most of the new jacks in this
area
are like this, and a few others he looked at that haven't been reported yet
are
not working for the same reason. There is too much extra "service loop" cable
and it's pinched behind the forced-on jack faceplates.
Thanks.....
Joni
----------------------
>X-Sender: ajames@hesiod
>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2
>Date: Mon, 17 Sep 2001 08:40:47 -0400
>To: vdist-trb@mit.edu, 3help@mit.edu
>From: Antoinette Browne <ajames@MIT.EDU>
>Subject: Re: Case 232381: Utp Jack 1-142-48 (PORT #2)
>Cc: LARUGSI@mit.edu, hotline@mit.edu
>
>
>
>Hi Chris,
>
>
>The JCI technician would like you to check this location again.
>He went out and could not find a jack with label in room 1-142.
>If you could use one of the PC numbers to reference where the
>jack is, it would make it a lot easier for JCI to locate the jack.
>
>
>
>Thanks
>Toni Browne
>
>>>
>
>At 03:50 PM 9/13/01 +0000, vdist-trb@MIT.EDU wrote:
>>3HELP,
>>
>>Please have JCI fix jack# 1-142-84-2 located in the back of the Athena
>cluster. The connection seems to cut out if the cable is inserted in a
>certain way.
>>
>>-Chris
>>
>>
>>[Comment (cggriffi, 09/13/2001 15:50:09)]
>>
>>===================================================== ==============
>>Please retain the case reference in the subject line for future replies
>>connected with this case.
>>
>
Joni
--=====================_12908902==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
Alicia...<br>
<br>
I had a chance to talk to Dave (JCI) regarding this issue. If you
read below, you will see the reason why he had trouble finding the
jack. One of the first emails about this trouble, which is shown
below, identifies the jack as
1-142-<font color="#FF0000">84</font><font color="#000000">-2. The
subject of the email directly below correctly identifies the jack as
1-142-</font><font color="#FF0000">48</font><font color="#000000"> (PORT
#2). <br>
<br>
It seems that <u>Chris provided the incorrect jack information on this
trouble to begin with</u>, and <u>that</u> is the reason why Dave
could not find the jack.<br>
<br>
Please remind your team to double check the info they provide to the
helpdesk. This will help us shoot the troubles faster and get the
customer back in service.<br>
<br>
Dave did ask me to pass on some crucial info about this area....he said
the reason that jack went into trouble is because whoever installed it
installed too much extra cable (service loop presumably) possibly
in order to work the jack outside, and then coiled and shoved the cable
into the wall, pinching the cable and forcing the faceplate on. He
said most of the new jacks in this area are like this, and a few others
he looked at that haven't been reported yet are not working for the same
reason. There is too much extra "service loop" cable and
it's pinched behind the forced-on jack faceplates.<br>
<br>
Thanks.....<br>
<br>
Joni<br>
----------------------<br>
>X-Sender: ajames@hesiod<br>
>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 <br>
>Date: Mon, 17 Sep 2001 08:40:47 -0400<br>
>To: vdist-trb@mit.edu, 3help@mit.edu<br>
>From: Antoinette Browne <ajames@MIT.EDU><br>
>Subject: Re: Case 232381: Utp Jack 1-142-48 (PORT #2)<br>
>Cc: LARUGSI@mit.edu, hotline@mit.edu<br>
><br>
><br>
><br>
>Hi Chris,<br>
><br>
><br>
>The JCI technician would like you to check this location again.<br>
>He went out and could not find a jack with label in room
1-142.<br>
>If you could use one of the PC numbers to reference where the <br>
>jack is, it would make it a lot easier for JCI to locate the
jack.<br>
><br>
><br>
><br>
>Thanks<br>
>Toni Browne<br>
><br>
>>><br>
><br>
>At 03:50 PM 9/13/01 +0000, vdist-trb@MIT.EDU wrote:<br>
>>3HELP,<br>
>><br>
>>Please have JCI fix jack# 1-142-84-2 located in the back of the
Athena<br>
>cluster. The connection seems to cut out if the cable is
inserted in a<br>
>certain way.<br>
>><br>
>>-Chris<br>
>><br>
>><br>
>>[Comment (cggriffi, 09/13/2001 15:50:09)]<br>
>><br>
>>=====================================================
==============<br>
>>Please retain the case reference in the subject line for future
replies<br>
>>connected with this case.<br>
>> <br>
> </font><br>
<br>
Joni
</html>
--=====================_12908902==_.ALT--
