[foxboro] Alarming: Message Manager 5.9

Dear Folks!
For a little while I tried to setup the "Message Manager 5.9" from Real 
Time Solution downloaded from the Cassandra's download area.
Unfortunately the installation is without significant success up to now. 
So I decided to ask for a little help...
The situation is a follows:

I created 2 servers called AG2501 for alarms and SG2501 for system alarms 
running on the 51 machine.

For testing them I built one compound with only one CIN generating State 
alarms. The CIN is changing its state every 5s an generates a state alarm 
PRIO 1 to GROUP 1.
In the Compounds GR1DV1 there's  integrated the AG2501 virtual device of 
the almsrvr.
After starting all of ready configured parts of the facility I got the 
following

Reaction of the PC Client in "Auto reconnect" Mode 
(c:\programme\gmvt\ato\msg)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
After clicking on the client softwares button to connect the Server the 
client responds as follows
In the status bar I can see 
   "Ready?. Host disconnected? Connecting" 
changing with 
   "Ready?. Connected to AG2501? Alarms cleared"

Sometimes the "connected" status is static for a few minutes, usually the 
changes are going on. 
Anyway there is indicated no alarm, not even if the client is connected 
for a while.


Reaction of the AW Client (/opt/almsrvr/almclient)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
No reaction, no almd<PID>.log in /opt/almsrvr/logs
Following the host clients description, the client should do the 
organisation with the connecting and connected PC clients
So my estimation is that the client should have to be seen by using ps -ef
But nothing happens in any case - I tested it several times, especially 
when the PC client seemed to be connected


Reaction of the AW Server ((/opt/almsrvr/almsrvr)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
after EG2501# ps -ef | grep alm there's shown
    root  6891     1  0 15:17:30 ?        0:01 /opt/almsrvr/almsrvr -a 
AG2501
    root  6892     1  0 15:17:30 ?        0:01 /opt/almsrvr/almsrvr -a 
SG2501
That seems to be ok

Only the at start time the files /opt/almsrvr/logs/almserv05.log and 
/opt/almsrvr/logs/almserv06.log will be created automatically. 
I tested the logging reaction with a once again start, although the servers are 
running and got the following messages
almserv05.log:
   msg -- ipc name already exists [AG2501]
   msg -- cs_activate error ?40

almserv06.log:
   msg -- ipc name already exists [SG2501]
   msg -- cs_activate error ?40

So I appreciate the logging is ok?but what is going wrong???
For further information please have a look to the description of the 
system's configuration below!


Thanks in advance for any information.

Mit freundlichem Gruß / Best Regards

Heinz-Peter Josten
GMVT mbH
mailto:Heinz-Peter.Josten@xxxxxxx

Im Hause
Arkema GmbH
Denzingerstr. 7
D-89312 Günzburg





In the following you'll find the configuration:

Our I/A-System Version is 6.3 based on an historical 51Series maschine 
named EG2501.
The momentary single client on Windows-XPpro PC (D89331G) is connected via 
ethernet 
using some HUBs and switches.
The Connection seems to be ok; e.g. FOX CAE and the daily backup is 
running satisfactorily


srvrdef.txt on AW51
- - - - - - - - - -
# Qid   ShmId   Hostname        Service                 Description
AG2501  18804   157.243.64.60   almserv05       EG2501 Alarmserver
SG2501  18805   157.243.64.60   almserv06       EG2501 Systemalarmserver


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
= = =
srvrdef.txt on clinet PC 
- - - - - - - - - - - - -
# Qid   ShmId   Hostname        Service                 Description
AG2501  18804   157.243.64.60   almserv05               EG2501 Alarmserver
SG2501  18805   157.243.64.60   almserv06               EG2501 
Systemalarmserver

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
= = =
/etc/inetd.conf (added & restarted using kill -HUP <inetd_PID>)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
almserv05  stream  tcp  nowait  root    /usr/sbin/tcpd  almclient -aAG2501 
-d5 -fALMSER
almserv06  stream  tcp  nowait  root    /usr/sbin/tcpd  almclient -aSG2501 
-d5 -fALMSER

(even -d5 did'nt brought success-theres no concrete statement of failures 
in logs)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
= = =
/etc/services
- - - - - - -
almserv05       1594/tcp
almserv06       1595/tcp
# Pogs User Message Service Port
pogsp1          1600/tcp


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
= = =
runsrvr
- - - -
/opt/almsrvr/almsrvr -a AG2501  > /opt/almsrvr/logs/almserv05.log 2>&1 &
/opt/almsrvr/almsrvr -a SG2501  > /opt/almsrvr/logs/almserv06.log 2>&1 &


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
= = =
/usr/fox/sysmgm/sysmon/destact.cfg
- - - - - - - - - - - - - - - - - -
Stopping sysmon_ech
Switching the historians name "eh2501" into the IPC-Alias name "SG2501". 
Then a restart of sysmon_ech
 
 
_______________________________________________________________________
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: