When you open ICC and you can see the Compounds listed, that is directly from
CSA
If yo select a compound and get that message you are seeing, that is because it
is a compound that it believes is not in a CP hosted by that AW
Windows machines can only edit CP's that they host.
Also if no CP's show when you select edit station, that is for the same reason.
Windows AW's can only edit CP's that they host, so that station doesn't believe
it host any.
Your procedures to move CP hosting did not go according to plan.
If you look on that AW and check d:/usr/fox/sp/IIF.pkg ....what are the
statuses of the packages....DONE, NOTYET, REINST ??
Also in same directory....the file sldb .....does it show correct hosting ??
_____________________________________________________________________________________
Russ Boulay | Schneider Electric | Process Automation | United
States | Support Engineering Manager
Phone: +1 508 446 1769 | Mobile: +1 508 446 1769
Email: russ.boulay@xxxxxxxxxxxxxxxxxxxxxx | Site:
https://support.ips.invensys.com ;| Address: Fairfield, California 94534
United States
*** Please consider the environment before printing this e-mail
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Terry Doucet
Sent: Wednesday, September 21, 2016 7:49 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Joe,
Removing any station from a system is always difficult in IA without doing a
complete Day0 install.
Not clear if you can get into a specific CP from the control configurator or
not. Are the CP's good in System Management?
If the CP's are good in SysMgmt but you cannot access them in the configurator,
you should be able to clean out a CP by copying the DB<LBUG>.init file into
DB<LBUG>.UC (checkpoint file) and rebooting the CP which initializes the CP
memory. Then hopefully you can access the CP in the control configurator.
When you are in the CP with the control configurator, INITIALIZE the CP which
will clear all the other files including the CSA files.
Terry
From: Joe@xxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Date: Wed, 21 Sep 2016 17:59:53 -0700
Scott,
Thanks for the advice but there is no emergency here...
We wanted to basically remove an AW70 from the Node and move its
hosting responsibilities to a different, existing AW70. I followed
the SysDef and Windows NT Upgrade Considerations manuals as best as I
could and all appeared to go smoothly, no errors. It looks like most
of it is there and not sure if the manuals missed something or I did.
Just looking to the expertise of this group, especially folks like
yourself, as we all do to help out with the 2 issues:
- When I open the CIO_Config it appears that all of the Compounds are
listed but when I pick one I get "CSA Error - CSgetcmpd Failed". The
CPs are empty and not even on line because I think I need to move the
Checkpoint files from the old AW70 to the new one to reboot them;
maybe? I was hoping to do a Load_All from the Save_All files and then
checkpoint them so the Checkpoint files are up to date.
- If I select the CIO_Station_Config there are no CPs listed. Is
that not just a missing cplns type file somewhere?
I want to perform a clean Load_All on the CPs, just not sure when/how
as nothing was mentioned in the manuals.
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, September 21, 2016 3:31 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Joe,
The Field Service organization as an internal Best Practices
bullet item typically requires our Service Engineers
to submit a upgrade/system plan doing significant alterations to a
customer system.
Do you have a organization that is capable of reviewing,
commenting and proctoring such installations ?
My old mentor John Duggar used to say "Poor planning on your part
does not constitute an Emergency on my part"
Regards,
Scott
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ [Russ.Boulay@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 21, 2016 5:06 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
That was quite the load of changes. So was old CP host checkpoint
files removed, rm_station run to remove former sict table entries. Is
CSA truly only running in one place now. There is a whole list of checks.
Sent from my iPhone
On Sep 21, 2016, at 2:48 PM, Joseph M. Riccardi <Joe@xxxxxxxxxxxxx> wrote:it next?
Russ, et al
Thanks for the lead on the cdrom setup... As part of the SysDef
changes, I also wanted to move a System Monitor, the CSA, the ICC,
and the CP Hosting to a different AW70. I think the SysDef changes
were easy enough and the
"5.2.1 Procedure to Move CSA between 70 Series Stations" per V6.1
Windows NT Upgrade Considerations Manual B0193XL also seemed to go
smoothly with no errors.
However, when I open the CIO_Config it appears that all of the
Compounds are listed but when I pick one I get "CSA Error -
CSgetcmpd Failed". And if I instead select a Station there are no CPs
listed.
Before starting I ran /opt/fox/ciocfg/api/save_all for all CPs on
the original AW70, copied them all to the new AW70, but when I run
/opt/fox/ciocfg/api/load_all for each CP the script just hangs forever.
Where did I go wrong; what did I miss?
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 Boulay, Russ
Sent: Tuesday, September 20, 2016 7:17 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and
commit
Disable I/A boot from red fox in control panel Reboot PC Install
appropriate
day0 cdrom for your version Run setup from cdrom From menu that's
appears select the commit option, or sub menu that gets you there
Make sure you are using a reconciled day 1 commit
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph M.
Riccardi
Sent: Tuesday, September 20, 2016 6:40 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Windows NT AW70 folks,
I revised the SysDef files and created a commit diskette. There are
a number of manuals describing the SysDef process up to and
including creating the commit diskette but I cannot find anything on
what to do with
I have done plenty of UNIX boxes (Config/Install_AW) but never abox.
WinNT
Anyone remember how to re-commit Windows NT AW70?
Thanks
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 A.
Adams
______________________________________________________________________
___ 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
