Re: [foxboro] /rem/r0 File system error? - Problem resolved

David,

The two problems *are* related, I believe.

If you run fist (/opt/fox/bin/tools/fist) on your AW and then again on
your CP, they should have the same Network Identifer (PSAP) address. If
the AW boots up without the proper information in
/usr/fox/exten/config/loadable.cfg, it assumes that it is in a standlone
mode and uses the network identifier of 000001, so it cannot talk to the
CP (or any other station), nor can the CP talk to the AW to make the
boot request.

Duc

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: Thursday, November 15, 2007 11:19 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] /rem/r0 File system error? - Problem resolved

Duc,

I'm glad you got the problem resolved.  I never equated our CP boot=20
problem, with your remote mount problem.

I can see where we might have run IA_config to screw our system up as=20
well, but I don't know if that's what happened or not.

Later,
David


PS
Don't forget the Southeastern I/A Users group meeting in Birmingham,=20
AL 2/12 and 2/13 2008.  Everyone is welcome.

 
 
_______________________________________________________________________
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: