Re: [foxboro] FoxSelect problem
- From: "Boulay, Russ" <russ.boulay@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 26 Jul 2007 07:53:02 -0400
Delete the file .
Then recall foxselect.
Does the MACaddress match the running CP mac?
/opt/fox/bin/tools/fist CPNAME
Also,
arp -a on host of CP
Does MAC and IP match running CP
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Pablo Lioi
Sent: Thursday, July 26, 2007 7:37 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxSelect problem
=
Sean, =
Thanks for your answer. The ini file looks OK, the PSAP address of the
problematic CP contains the correct MAC address as seen in system
monitor
andthe leading and trailing digits match the other (working) stations in
the
system. =
At first there was a difference in the leading and trailing digits of
the
PSAP address of the non-communicating CP compared against the other
stations,and it looked as if there was a missing digit in the leading
part,
see the following: =
CP2712=3D5803-405-d-4930303030303000006cc000ea04600505040000
CP2711=3D4143-5c43-d-4930303030303000006cc000de6f72655c696e63
AB3003=3D4143-5c43-d-4930303031303100006cc000466f72655c696e63
(the problematic CP is the first in the list) =
, but after several refresh commands in foxselect, the ini file entry
changedto =
CP2712=3D4143-5c43-d-4930303030303000006cc000ea6f72655c696e63
Anyway, the CP is still not communicating with FoxSelect =
Regards =
Pablo =
------------------------------------------------------------------------
----
From: "Redmond, Sean S" <Sean.Redmond@xxxxxxxxxxxxxxxxxx>
Reply-To: foxboro@xxxxxxxxxxxxx
To: <foxboro@xxxxxxxxxxxxx>
Subject: Re: [foxboro] FoxSelect problem
Date: Thu, 26 Jul 2007 13:15:28 +1200
>Hi Pablo,
>
>>But FoxSelect can't access one of them (red cross
>over it, and doesn't refresh when double-clicked).
>
>Have you had a look at the foxselect ini file. It is in
>/opt/fox/wp/FoxSelect and has the name FSDMNAME.ini The ini file stores
>the address of the cps. This file might have become corrupt or perhaps
>had its file permission changed.=3D20
>
>Sean
>NZ Steel
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
>On Behalf Of Pablo Lioi
>Sent: Thursday, 26 July 2007 5:20 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: [foxboro] FoxSelect problem=3D20
>
>=3D20
>Hi everybody=3D20
>
>We have several FCP270 fault tolerant pairs in our Mesh network. All of
>them
>are working, can be accessed with IACC, communicate with Foxview and
>show in
>System monitor as healthy. But FoxSelect can't access one of them (red
>cross
>over it, and doesn't refresh when double-clicked). Before this problem
>started, we had been regurlarly using FoxSelect to access
>compounds/blocks
>inthis processor pair.=3D20
>
>We have already:=3D20
>
>-Checkpointed the processor from system manager=3D20
>
>-Checkpointed the processor from IACC=3D20
>
>-Rebooted the shadow processor from system manager.=3D20
>
>-Tried to access the processor with FoxSelect from the AW and all the
>WP's=3D20
>
>Any ideas?=3D20
>
>Thanks=3D20
>
>Pablo Lioi=3D20
>
>Systems Engineer=3D20
>
>TOTAL AUSTRAL=3D20
>
>ARGENTINA
>
>
>
>=3D0A=3D0ANOTICE - This message and any attached files may contain
informatio=3D
>n that is confidential and intended only for use by the intended
recipien=3D
>t. If you are not the intended recipient or the person responsible for
de=3D
>livering the message to the intended recipient, be advised that you
have =3D
>received this message in error and that any dissemination, copying or
use=3D
> of this message or attachment is strictly forbidden, as is the
disclosur=3D
>e of the information therein. If you have received this message in
error =3D
>please notify the sender immediately and delete the 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: //www.freelists.org/list/foxboro
>to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
>to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
------------------------------------------------------------------------
----
See what you're getting into...before you go there [1]
--- Links ---
1 http://g.msn.com/8HMAENUS/2734??PS=3D47575
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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:
