Scott,
Thanks for the feedback but I don't think I did a very good job of
explaining my fears. My biggest fear is that we lose the CSA Host
Workstation or the CSA database becomes not in sync (would run
check_db_sync). A search of this subject brings up an inquiry from
QUEIROLO, IGNACIO ESTEBAN on Sun 9/6/2015 9:53 AM about having to rebuild
the CSA database. It difficult to explain but as I have mentioned in some
other emails I have cloned a Production Node for use as a development and
testing Node. All changes are implemented on this development Node and
tested before they are re-implemented on the Production Node. We have
procedures in place to copy all changes "as implemented on the Production
Node" back to the development Node to maintain this clone status. There is
a defined set of SaveAlls, HLBL, display, etc. files that are backed up to
be copied to the development Node each time a change occurs. This has
worked very well for years but I never want to get into this ugly situation
of having to rebuild the CSA database, for whatever reason causes it.
Russ Boulay's response to Ignacio's inquiry was... "First be sure your CSA
database is in sync with the system by running check_db_sync. If that is
clean....then csa_save would save all CP's on the system to their individual
save folders." At this point I believe/hope our CSA database is in synch
with various CP files so I would think adding this csa_save command and
adding the resultant /user/fox/csa/save directory to the backup routine
would make life easier should we ever have the need to rebuild the CSA
database; no? Or am I missing something
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Landry, Scott
Sent: Wednesday, April 27, 2016 4:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Joe,
There are varying degrees of being "synced".
CSA's purpose is to ensure Compound Names are unique in a "system" and as
follows Block Names within a Compound are unique.
Decide who the master is , the testbed or the running system. In most
cases it's the running system.
To ensure "sync", perform an initialize, reboot and loadall on a
periodic basis with the "master saveall" for each CP and/or Integrator.
Regards,
Scott
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf
Of Joseph M. Riccardi [Joe@xxxxxxxxxxxxx]
Sent: Wednesday, April 27, 2016 3:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Thanks again Terry, I will follow through on those suggestions later today.
Early in the troubleshooting process I did find a patch of crud (does crud
conduct?) around the solder joints on the backside of SCSI board. So I
tried 2-3 other SCSI cards with no success so I brushed the crud off and put
it back in. And that is the odd point of this SCSI problem, as I changed
SCSI cards and cables and drives, the errors were different after each
change as you can see from the original email below.
At this point I am waiting for the replacement and just hoping to get some
feedback on the CSA_Save questions I have. Probably should have started a
new email thread...
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Terry Doucet
Sent: Wednesday, April 27, 2016 11:00 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Joe,
Other than re-seating all the RAM, checking (perhaps melting) the solder
joints for the external connectors and checking all capacitors for bulging
tops, I have nothing else to advise.
Terry
From: Joe@xxxxxxxxxxxxxinstalled.
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Date: Wed, 27 Apr 2016 10:45:04 -0700
Thanks Terry, that is where I am at right now. Already ordered a used
replacement so we can get it back on line but the Dell box was in
excellent condition since it came from a project that was cancelled,
never
It ran well for 2 years until it started acting up while doing aare
backup and then a restore to a different external drive last week. I
was hoping I could figure it out and keep it as a spare.
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A.
Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Terry Doucet
Sent: Wednesday, April 27, 2016 10:33 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Joe,
Try searching for the DELL model number on the web. Since these things
better boat anchors than processors, you just might find one for $25so.
or
I know of one user who went that route and the shipping was more thanproof that it still ran.
the cost of the computer, but he did find one. He loaded it at site
with some specific cards (A-B comms) from the existing PC, loaded it
all up with s/w then shut it down and kept it as a spare. Don't know
if he ever had to use it but he could get it running in less than 30
minutes (transferring cards, connecting cables, etc). He performed
monthly backups of the running station and loaded the spare, so he had
in case.
Terry
From: Joe@xxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems; now CSA_Save
Date: Wed, 27 Apr 2016 10:20:15 -0700
Hmmmmmm... No help troubleshooting SCSI problems. I guess I will
have to toss this AW70 Workstation, or maybe use it as a boat anchor.
Ordering a replacement...
Same site, same AW70 WinNT Node; different question... CSA_Save. I
built a clone Node for use as a development and testing Node,
disconnected from the production Node. We try to keep the 2 Nodes
in synch but I have always been concerned with the ICC workfiles and
the CPs getting out of synch. Is the CSA_Save utility intended to
be used as a preventative measure? If I understand how it works it
is useless once the ICC workfiles and the CPs are out of synch. My
plan has been to periodically run CSA_Save and back up those files,
just
A.Is this the intent of CSA_Save? If it is, I cannot see why thisin case? What am I missing?
procedure would not be in everyone's periodic maintenance procedure,
just
And I just want to make sure running it will not cause any problems
on existing host's CSA files.
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought
or measured with money; and that is sincerity and integrity." -
Donald
madman.Adamsthe following:
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph M.
Riccardi
Sent: Monday, April 25, 2016 1:25 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] SCSI problems
I forget everything is stripped of formatting and plain text is all
that make it through. If it helps to follow, the *s are separate
boot sequences and the o's are sequential lines following that
appear on the screen for that boot sequence...
As in...
* Blah, Blah, Blah...
o Blah, Blah, Blah...
o Blah, Blah, Blah...
* Blah, Blah, Blah...
o Blah, Blah, Blah...
o Blah, Blah, Blah...
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph M.
Riccardi
Sent: Monday, April 25, 2016 1:15 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] SCSI problems
AW70, WinNT, SCSI folks,
I have an old AW70, WinNT, P93 (Dell Optiplex GX240) that I cannot
get to boot to the external SCSI Winchester drive. Most of the
errors on boot up appear to be related to the SCSI
port/parts/equipment. I have swapped out everything I can think of
(various SCSI cards, internal and external SCSI cables, even
different external Winchester drives, the old and new models) but
still no success. However, depending on what I replace, I get
different boot errors, although I believe they are all related to
the SCSI components and/or the external SCSI Winchester drives. A
sampling of errors include but are not limited to
* Press <Ctrl><A> for SCSISelect T Utility. (Note: <Ctrl><A> doestime
nothing)
o Time-out failure during SCSI Inquiry Command!
o Rescanning for SCSI Devices...
o No SCSI Boot Device Found.
o SCSI BIOS not installed! (Note: What SCSI BIOS? F2 for setup
utility shows no BIOS settings)
* Press <Ctrl><A> for SCSISelect T Utility. (Note: <Ctrl><A> does
nothing)
o This time it shows . Slot Ch ID LUN Vendor Product
Size Synch (Note: On a good boot it would show the external drive
details but not now)
o Time-out failure during SCSI Inquiry Command!
o Rescanning for SCSI Devices...
o This time it shows . Slot(B1 or 81?) Ch(A) ID(B or 8?)
LUN(B or 8?) Vendor Product Size Synch Bus (Note: This
it gets a little further, but blurry so not clear if those Bs or 8s)8?)
* Press <Ctrl><A> for SCSISelect T Utility. (Note: <Ctrl><A> does
nothing)
o This time it shows . Slot Ch ID LUN Vendor Product
Size Synch Bus (Note: Nothing more)
* Press <Ctrl><A> for SCSISelect T Utility. (Note: <Ctrl><A> does
nothing)
o This time it shows . Slot(B1 or 81?) Ch(A) ID(B or 8?)
LUN(B or 8?) Vendor Product Size(17Gb) Synch(ASYN) Bus(B or
(Note: AAAAAAAH! It finally sees the drive)8?)
o Time-out failure during SCSI Inquiry Command!
o Rescanning for SCSI Devices...
o This time it shows . Slot(B1 or 81?) Ch(A) ID(B or 8?)
LUN(B or 8?) Vendor Product Size Synch (Note: This time it
does not see the drive, same boot cycle)
* Press <Ctrl><A> for SCSISelect T Utility. (Note: <Ctrl><A> does
nothing)
o This time it shows . Slot(B1 or 81?) Ch(A) ID(B or 8?)
LUN(B or 8?) Vendor Product Size(17Gb) Synch(ASYN) Bus(B or
(Note: AAAAAAAH! It sees the drive again but does not get any
further)
PS.. Not that it matters but they all mostly end with. Alert Cover
was previously removed. & strike F1 to retry boot, F2 for setup
utility
Many of the above boot sequences were repeated more than once as I
probably swapped parts and rebooted at least 2 dozen times last week.
Is there any methodical procedure or tool to troubleshoot a SCSI port?
Anything has to be better than swapping parts and rebooting like a
A.
Thanks for listening
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx <mailto:Joe@xxxxxxxxxxxxx>
"To give real service you must add something that cannot be bought
or measured with money; and that is sincerity and integrity." -
Donald
//www.freelists.org/list/foxboroAdams
____________________________________________________________________
__ ___ This mailing list is neither sponsored nor endorsed by
Schneider Electric (formerly The Foxboro Company). Use the info you
obtain here at your own risks. See the disclaimer at
www.thecassandraproject.org/disclaimer.html
foxboro mailing list:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=jointo subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leaveto unsubscribe:
______________________________________________________________________
___ This mailing list is neither sponsored nor endorsed by Schneider
Electric (formerly The Foxboro Company). Use the info you obtain here
at your own risks. See the disclaimer at
www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
______________________________________________________________________
___ This mailing list is neither sponsored nor endorsed by Schneider
Electric (formerly The Foxboro Company). Use the info you obtain here
at your own risks. See the disclaimer at
www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
