Re: [foxboro] network locked
- From: dirk.pauwels@xxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 5 May 2009 10:38:02 +0200
I'll compare the result from an ifconfig -a next time I have this problem
like Duc suggests and try stopping and starting the interface. Strange
thing is it happens to all of the unix stations, not just one of them.
The local VT100 works fine, also the stations continue to work fine, no
blue fields.
I'm investigating another possible cause for the moment, Global IT has an
EPO server scanning all connections to the LAN, and since our unix
stations are also connected to the business lan, the ports may get blocked
by the scanning or after the scanning took place for some reason. We took
out the unix stations' IP adresses in the EPO servers scanlist so they
won't get scanned anymore, see what happens....
Thanks for the help guys,
Dirk Pauwels - DCS/MOC coordinator
Engineering dept.
Hexion Specialty Chemicals
E mail: dirk.pauwels@xxxxxxxxxx
T. +32.(0)3.570.95.97
F. +32.(0)3.570.16.09
Mob. +32.(0)497.428.300
Maks Wilde <mwilde@xxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/05/2009 20:00
Please respond to
foxboro@xxxxxxxxxxxxx
To
foxboro@xxxxxxxxxxxxx
cc
Subject
Re: [foxboro] network locked
Dirk,
Did you have local access to the stations? I have experienced the same
problems on a 6.3 system where the station ran out of processes (eg:
cannot
open a new VT100).
The station would appear to run fine, except no new process or connection
could be started. You can run "sar -v 1 2" to see the number of processes
and "ps" (with options) to investigate.
If it's only a connection problem, you should try stopping and starting
the
secondary ethernet interface locally and see if it that resolves the
problem.
Hope this helps,
Maks Wilde
>
>
_______________________________________________________________________
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:
