Hi Joe,
Can I suggest ?
Did you test the ICC session with blank data base?
Can you test first Fix-all, then test the session, exit and again.
second load from diskette one by one Compond.
In each test, you can see the Chkpnt file size.
I think that the problem is the memory overload ( may be sequences
blk)
Hugo
> -----Mensaje original-----
> De: Joe Markham [SMTP:[EMAIL PROTECTED]]
> Enviado el: Jueves 12 de Octubre de 2000 15:11
> Para: 'Foxboro DCS Mail List'
> Asunto: RE: ICC Connection problems
>
> We have. We went back a couple of months. It has no effect on the problem.
> -JAM
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dusing, Lance
> Sent: Thursday, October 12, 2000 11:00 AM
> To: 'Foxboro DCS Mail List'
> Subject: RE: ICC Connection problems
>
>
> A test may be to use a loadall disk from a time before the conversion.
>
> Lance
>
>
>
> -----Original Message-----
> From: Joe Markham [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 12, 2000 9:30 AM
> To: Foxboro DCS Mail List (E-mail)
> Subject: ICC Connection problems
>
>
> I have a problem connecting to a CP10 with the ICC. I get a message
> indicating that the ICC failed to communicate with an error code of -23.
> The
> controller continues to run the process: the green light stays on, the
> red
> light stays off, and the SMDH indicates that there are no problems.
>
> TAC had us try the following:
> > Try this next:
> > 5AWB01# cd /usr/fox/sp/files
> >
> > 5AWB01# cp DB5CP101.init DB5CP101.UC
> > 5AWB01# cd /usr/fox/csa
> > 5AWB01# csa_fn reset 5CP101
> > 5AWB01#
> > Of course, substitute your letterbug for 5CP101. Now go to ICC and
> > MAINT, Initialize
> > Then reboot CP
> > Now MAINT, loadall
> > Checkpoint
> > Get out of ICC and then try to get back in to edit blocks.
>
> Of course, we had to do a general download to get all the FBMs running
> again.
>
>
> After this we can get into the CP for a minute or two, then the same
> failure
> happens again. We even tried swapping this CP10 with another one that we
> have. The problem was unchanged. TAC is stumped and has suggested
> replacing
> the CP again, but this just doesn't seem like a hardware problem to me.
>
> One other bit of info. We first noticed this problem about a month after
> we
> upgraded the host AW from a 51B to a 51E.
>
> Thoughts? Suggestions?
>
> -JAM
>
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
>
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due
> to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
>
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
>
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
