FUJ00066911
FUJ00066911
IPC0041910
Peak Incident Management System
POA Deleted User -- Deleted Team
fTargeted At -- Unknown
{null
[DeletedContact
IClosed -- Initial
2/05/2000
(0
'M - Unable to sustain 2-way comms with 3 outlets
Date :30-Mar-2000 11:24:00 User:De1(04/03 Audrey Adams)
CALL PC0041910 opened
References entered are:-
Product Infras
target Release e:
po =
Background:
tn the pre ng down the software commit tail for COUNTER _CORE_IMM
411, there are 3 gateway y upgraded -
269230, 308226 and 333230.
IAll appear at this stage to exhibit the same symptom
1. Inbound communications from each outlet are succe:
2. All transactions are successfully r
3. The outlets do not appear on the non-polling reports
4. Outbound communications from the data centre fail
s with 3 outlets
cess of clo
unters that cannot be suce
ived
hese outlets have not produced a cash ai are
Icontinuing in the same CAP - as agreed between Stephen M
Jo' Donnell.
IResolution:
Itnergis, BT and ICL are working together to understand the root cause and
chen provide a resolution. To this end, SSC have produced a trace from each
n card and have provided these to Energis for urgent inve
unt this week (March 29, bj
ow and Bernadette
lem manager:
Woolaar
I PCO041910:Priority A:Call?ype 2 - Target 94/05/00 20:0
the call mber: Mike Woolgar
Defect
Hours spent since call received: 1
Date:30-Mar-2000 14:47:00 User:Michael Woolgar
FAD 269320 now pinging,
unknown... investigation will continue.
jother 2 FADS have had line kept open following inbound ca
Jone shot Software Downloads can be distributed to all 3
these will be committed out of hours.
investigations continuing reference root
although reason for resolution
use
Date:31-Max-2000 08:22:00 User:Michael Woolgar
software commits worked successfully overnight 30th/31st March.
Inow be able to do their Cash Accounting as normal.
rurther investigations continuing as to why 2 way comms
SC and net
unsuccessful. Traces
Jare with Energis, with SMC,
CALL PC0041910:Priority B:CaliType Z - Target 09/05/00 20:0!
ks involved
Date:31-Mar-2000 15:07:00 User:Michael Woolgar
IEnergis have been studying traces that we have supplied. They
conjunction with OSD Networks, arranged test traced
hey have accepted that they are seeing different patterns on
, compared with other live offices. They have taken traces away for
in depth di
sions with
Date :04-Ape-2000 13:18:00 Usor:Michael Woolgar
he fault for Wisbech now mysteriously disappeared allegedly without any
Jactivity from BT. I am pursuing this with Energis. The only existing two way
comms problem is therefore with FAD 333230 Nothampton. I have sent trace to
lsnergis and also OSD networks who will both monitor and attempt to
che fault and then take a further trace when it is working.( in order to
compare) .
However, I have tasked Energ
intermittent problem must be fixed.
resolve
resolve this in the long term, as any
Date:05-Apr-2000 13:28:00 User:Michael Woolgar
telephone conference call held on Tues 4th April. Various a¢
FUJ00066911
FUJ00066911
ning FAD tha
Br.
that by resetting the
FAD now working su
all single CLI,
identifying that they are on
2 way comms problem, between OSD Net
LI, the dual CLI disappeare
stery still exists as to why
ddenly become dual...followed by problem
again back to single CLI. BI
doing anything on these to make this happen.This is being pursued.
simlarly BT claim that it is a European Industry standard that dual CLI's
Jare/will become the norm. being pursued.
in the meantime, am investigating of Dual CLI's upon the Eicon driver.
Ithis currently will only ai I, hence longer term view is being
lsough
INow that all parties are aware of fault condit
these will be resolved more speedily.
lav
CALL PC0041910:Priority Cc Type 2 - Target 12/05/00 20:01
ce:14-Apr-2000 08:01:00 User:Michael Woolgar
uses the CLI to go from single t!
1 investigating as to wha uble
loresentation,
28-Apr-2000 09:16:00 User:Michael Woolgar
urrence of dual CLI in
eas are geared up to
are still awaiti
what is
accordingly.
g a further o
+ALL suppor’
to try
is and act
e cau:
12-May-2000 13:35:00 User:Michael Woolgar
before..
ed and will be monitored
hould it do so.
Date:06-Jun-2000 08:23:00 User:Michael Woolgar
he situation is still being monitored closely and awaiting any further
© trap the conditions and pi
recurrence, in order
Date:23-Jun-2000 10:10:00 User:Michael Woolgar
INo further occurences hence unable to produce evidence.Still being
jonitored
rgd
ate :06-Jul-2000 13:48:00 User:Michael Woolgar
swill p:
1 awaiting recurrence of problem
oduce an update as
Date:18-Jul-2000 10:26:00 User:Michael Woolgar
ure occurs by end of
s will mean 4 months
without any repeat
Date:31~Aug-2000 13:21:00 User:Michael Woolgar
las there has been no fu ident,despite continual monitoring,
now be closed.
iF} Response +
closed due to no further occurencies
[END OF REFERE
21452335
Responded to ¢ Completed
Hours spent since 3
the response was d
bate :06-Sep-2000 14:00:00 User:Del (04/03 Audrey Adams)
CALL PCO041910 closed: Category 15, Type Z
Hours since call received: 22.5 hours
Defect cause updated to 41:General - in Procedure
General - in Procedure
POA Deleted User -- Deleted Team
(version unspecified)
Deleted Team:
_106-Sep-2000 14:00 -- Del(04/03 Audrey Adams)