Re: [foxboro] Remove autostart of legacy servers?
- From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 21 Mar 2006 21:41:17 +1200
David,
Thanks for having a look.
I'm running 3.2 on this system. I've upgraded to 3.2.3 on another
network here a few months ago, and am waiting for some resolution on the
CARs I wrote before installing on the other two networks.
After our AIM* 3.2.3/OPC 3.3 upgrade on a similar smaller system (one
AW51E remote collector, one off platform AIM* instance on W2K server,
10K tags) I found:
1) histcfg is broken on the Solaris side
2) New OPC HDA server problems (OPC server is basically a wrapper for
AIMAPI as I understand it, so hard to tell if the problem is OPC or AIM*).
3) Task windows keep briefly flashing on the screen of the AIM* instance
machine, too fast to tell what process they are associated with.
Sometimes every few seconds. Again, hard to tell if OPC or AIM* related.
I'll try commenting out the AIMHISTORIAN line and rebooting to see how
it goes when I get a chance during a shut on the plant area or a quiet
time on the AW.
Regards,
Kevin FitzGerrell
Carter Holt Harvey, Ltd.
+64 27 460 9994
Hicks, David wrote:
> Kevin,
>
> The configuration all looks correct.
>
> The /etc/histlns and /etc/histlocs file can be changed by the running system
> also. If the OM has entries for another workstation hosting a historian it
> will dynamically add to this file. Assuming that all stations have been
> committed with the same committed install this would be an impossibility
> though.
>
> I am going to check to make sure, but I am reasonably sure that the
> histstart or the actual go_AIMHISTORIAN should only be launched by the
> workstation that is serving or hosting the historian. All other stations
> would use OM to get to the data from the historian through this workstation.
> I am still very confused on how you can have 2 ipchisti processes running,
> basically on the same node at the same time with the same historian instance
> name. This is troubling because there are safeguards built into the
> software to prohibit this. It may be because the historian instance is
> actually located on a seperate machine and not hosted or located directly on
> the node.
>
> All of the historian services, ie, histsend, histreceive, iocol should be
> controlled by the remote server (w2k machine). This is why I am reasonably
> sure that only the P101AW should be the only workstation actually starting
> historian services. AIMAPI is all that is required to get the data to the
> remote collector.
>
> What version of AIM AT is installed? Hopefully, V3.2.3.
>
> I will test this setup and get back with you, but if you may want to try
> commenting out the AIMHISTORIAN line in the /usr/fox/bin/fox_apps.dat file
> on the P401AW to see what results you get.
>
> Dave Hicks
> Invensys Systems, Inc
> david.hicks@xxxxxxxxxxxxxxxx
> -----Original Message-----
> From: Kevin FitzGerrell
> To: foxboro@xxxxxxxxxxxxx
> Cc: 'Dave Hicks '; "Hicks, David"@paradise.net.nz;
> david.hicks@xxxxxxxxxxxxxxxx
> Sent: 3/20/06 8:18 PM
> Subject: Re: [foxboro] Remove autostart of legacy servers?
>
> Dave,
>
> In answer to your questions:
>
>
>>On the remote collector machine (w2k server) in the configuration menu
>>is
>>the rtp, messages, reduction, and the other component configurations.
>
> I
>
>>do
>>not have access to an AIM historian machine at the moment, but in the
>>component configurations there is a tab for defining the local
>>collector
>>attributes and the remote collector attributes. This is where you
>
> would
>
>>define which station is the AW collector for the instance. It can be
>>defined by IP or name assuming it is in the host file.
>
>
> Right, I think I understand what you were asking for now. I'll put a
> copy of
> the configuration at the end of this email.
>
>
>>Have you gone back and looked to see if the /etc/histlns and
>>/etc/histlocs
>>files remain as you originally built them? Curious...
>
>
> Yes, these files remain. Committals have the potential to change these,
> but
> don't unless I've made sysdef changes that would cause them to be
> rewritten.
>
> Thanks for helping!
>
> Regards,
>
> Kevin FitzGerrell
> Carter Holt Harvey, Ltd.
> +64 27 460 9994
>
> Configuration follows (from the .inp file generated by histcsave run on
> the
> instance machine - w2k server):
>
> ## AIM*HISTORIAN CONFIGURATION:
> #
> 1 PUT AIMHIST puhs01 ARCHSIZE 10000000
> RTTIME = 86400
> MSGFILE = 1000000
> MAXPTS = 20000
> MAXCGENTS = 4000
> # Max # of points authorized for server machine. DO NOT SET THIS VALUE
> # MXSRVPTS = 20000
> MAXRGENTS = 4000
> MAXLOG = 1000000
> TRACKKEY = 4000
> MSGDEFS = 4000
> LRCCALC = NO
> DBPATH = ""
> EMAIL = ""
> LOGFILE_NAME = d:\aim\inst\historian.log
> STARTONBOOT = 1
> FHDESC = ""
> COMPRESS = NO
> REDUCLEVEL = 0
> PCTVALID = 0
> REDUCPHASE = 0
> REDPHASEUNIT = 3
> USEREDFILES = NO
> SCANPEAKS = NO
> REDFASTUNIT = 4
> REDMEDUNIT = 4
> REDSLOWUNIT = 5
> REDFASTINT = 1
> REDMEDINT = 8
> REDSLOWINT = 1
> IATIME = YES
> ENABLE_STUBS = NO
> TESTCKFACTOR = 1000
> MDEGETMETHOD = ALL
>
> #
> ## STATION CONFIGURATION:
> #
>
> #
> ## STATION :REALTIME_SERVER
> #
> 1 CREATE STATION REALTIME_SERVER
> ISIA = YES
> TYPE = REALTIME_SERVER
> PLATFORM = NT
> TZ = GMT
> DST = NO
> NODE = 1
> ISREMOTE = NO
> COLPORT = 44444
> CSTARTONBOOT = NO
> FOLLOWINSTON = NO
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 0
>
> #
> ## STATION :MESSAGE_SERVER
> #
> 1 CREATE STATION MESSAGE_SERVER
> ISIA = YES
> TYPE = MESSAGE_SERVER
> PLATFORM = NT
> TZ = GMT
> DST = NO
> NODE = 1
> ISREMOTE = NO
> COLPORT = 44444
> CSTARTONBOOT = NO
> FOLLOWINSTON = NO
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 0
>
> #
> ## STATION :puhs01
> #
> 1 CREATE STATION puhs01
> ISIA = YES
> TYPE = IA_RT_COLLECTOR
> PLATFORM = NT
> TZ = GMT
> DST = NO
> NODE = 1
> CIRCFILESIZE = 1000000
> BURSTINT = 0
> BURSTBTPCT = 10
> BURSTTTPCT = 90
> SENDPASSSECS = 0.2
> RECVPASSUPDS = 1000
> CONSLEEPSECS = 5
> ISREMOTE = NO
> COLPORT = 44444
> CSTARTONBOOT = YES
> FOLLOWINSTON = YES
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 500
>
> #
> ## STATION :puhc01
> #
> 1 CREATE STATION puhc01
> ISIA = YES
> TYPE = IA_RT_COLLECTOR
> PLATFORM = SOLARIS
> TZ = GMT
> DST = NO
> NODE = 1
> CIRCFILESIZE = 1000000
> BURSTINT = 0
> BURSTBTPCT = 10
> BURSTTTPCT = 90
> SENDPASSSECS = 0.2
> RECVPASSUPDS = 1000
> CONSLEEPSECS = 5
> ISREMOTE = YES
> HOSTNAME = P101AW
> COLPORT = 44444
> CSTARTONBOOT = YES
> FOLLOWINSTON = YES
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 500
>
> #
> ## STATION :puhc02
> #
> 1 CREATE STATION puhc02
> ISIA = YES
> TYPE = IA_RT_COLLECTOR
> PLATFORM = SOLARIS
> TZ = GMT
> DST = NO
> NODE = 1
> CIRCFILESIZE = 1000000
> BURSTINT = 0
> BURSTBTPCT = 10
> BURSTTTPCT = 90
> SENDPASSSECS = 0.2
> RECVPASSUPDS = 1000
> CONSLEEPSECS = 5
> ISREMOTE = YES
> HOSTNAME = P201AW
> COLPORT = 44444
> CSTARTONBOOT = YES
> FOLLOWINSTON = YES
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 500
>
> #
> ## STATION :puhc04
> #
> 1 CREATE STATION puhc04
> ISIA = YES
> TYPE = IA_RT_COLLECTOR
> PLATFORM = SOLARIS
> TZ = GMT
> DST = NO
> NODE = 1
> CIRCFILESIZE = 1000000
> BURSTINT = 0
> BURSTBTPCT = 10
> BURSTTTPCT = 90
> SENDPASSSECS = 0.2
> RECVPASSUPDS = 1000
> CONSLEEPSECS = 5
> ISREMOTE = YES
> HOSTNAME = P401AW
> COLPORT = 44444
> CSTARTONBOOT = YES
> FOLLOWINSTON = YES
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 500
>
> #
> ## STATION :puhc03
> #
> 1 CREATE STATION puhc03
> ISIA = YES
> TYPE = IA_RT_COLLECTOR
> PLATFORM = SOLARIS
> TZ = GMT
> DST = NO
> NODE = 1
> CIRCFILESIZE = 1000000
> BURSTINT = 0
> BURSTBTPCT = 10
> BURSTTTPCT = 90
> SENDPASSSECS = 0.2
> RECVPASSUPDS = 1000
> CONSLEEPSECS = 5
> ISREMOTE = YES
> HOSTNAME = P301AW
> COLPORT = 44444
> CSTARTONBOOT = YES
> FOLLOWINSTON = YES
> FOLLOWINSTOF = NO
> MINCOLCYCLE = 500
>
>
>
> _______________________________________________________________________
> 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: //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 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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
