[foxboro] Mesh Configuration Change

List Gurus,

Not to wish bad luck on anybody, buy maybe someone has stepped in this
problem before and can relieve me of some of my current misery.  I have
a message in to TAC with this also, but this sounds like a weird one,
and there is no substitute for actually having experienced a problem.
Pain is a wonderful memory enhancer.

Background - We have an existing version 8.2 configuration with 6 V2
switches, 6 ZCP270 pairs, and 7 P92 workstations.  We are in the process
of upgrading the switches to 4 N1 platinum blades, and getting rid of 1
workstation in the configuration (was never installed - existed for
testing only).  These changes were made to the original configuration in
SysDef 2.8, and a new commit disk created.  The IIF.pkg file on this
commit disk had everything as DONE except for ASMON7 and ASMDW7 which
were PCHANG.  We also had one of the existing workstations with a failed
hard drive that had to be rebuilt from scratch, and I used the new
configuration (with everything set to NOTYET) to do that.  It hasn't
been re-installed yet to see how it works.

Problem 1 - The IP addresses for the workstations changed in the new
configuration, and I didn't catch that until a Day 1 install had been
done on three of the workstations.  The IP addresses did not get updated
by the Day 1 on the workstations, but I manually changed them, and
things seem to be working okay.

Question 1- Does a day 1 install using this new commit disk work okay if
I manually change the IP address, or is there something in the Foxboro
software bound to the original IP address?  Doing a Day 0 on these
workstations will be a lot of work and time, and is to be avoided if at
all possible.  Has anybody seen this before?

Problem 2 - The AW70 in the system after about a day of operation gets
the "MS Visual C++" errors and nothing works very well in Foxview.  This
workstation did this before doing a Day 1 to the new configuration, and
it has had QF1009948 loaded on it (which is supposed to fix this error),
with no impact.  This box has AIM*Historian and AIM*OPC server running
on it.

Question 2 - Is there anything else to look at as a potential initiator
of this error, or will I have to do a Day 0 on this box to hopefully
clear this up?  Any experience here?

As always, any help is appreciated.

Thanks,
=================================================
Gaylon Hicks
Tennessee Valley Authority, Browns Ferry Nuclear Plant
Mail Stop SAB-1B
PO Box 2000
Decatur, AL 35609
Phone:(256) 614-8386 Fax:(256) 729-2047
email gfhicks@xxxxxxx
FedEx Address: Shaw Road & Nuclear Plant Road, Athens, AL 35611
==================================================

NOTICE: This electronic message transmission contains information which
may be TVA SENSITIVE, TVA RESTRICTED or TVA CONFIDENTIAL. Any misuse or
unauthorized disclosure can result in both civil and criminal penalties.
If you are not the intended recipient be aware that any disclosure,
copying, distribution or use of the content of this information is
prohibited. If you have received this communication in error, please
notify me immediately by email and delete the original message.

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: