<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
thank you all!<br>
<br>
i do appreciate your help.<br>
<br>
very generous!<br>
=================================<br>
<div class="moz-cite-prefix">On 12/19/2014 1:26 PM, Merritt, Jonah
wrote:<br>
</div>
<blockquote
cite="mid:CAPTFOo07q+F6LevDDA4-OLPU0yR-OKjwTTBWA189UbdTTe561w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hello everybody,<br>
<br>
</div>
We are seeing the same issues! Jacob is correct...if you
reboot the Basalt (or Granite) it loses contact with the
gateway. This issue seems to have manifested itself more is
subsequent Linux updates (we are running 2.6 update 6). We
also almost exclusively use Raven XE or GX440 modems.<br>
<br>
What I have found that all is well after performing the
"netconfig" script and setting up NetWatcher. However, once
you reboot you loose all remote connectivity. If you get into
the Basalt locally via SSH and restart networking
(/etc/init.d/networking restart) all is well again....until
the datalogger reboots again. <br>
<br>
</div>
It should be noted that if you are able to log into the Raven,
you can successfully ping the Basalt.<br>
<div><br>
I have contacted KMI about this and it was suggested that the
problem resides with the modem and not the digitizer. I'm not
convinced that it's a Raven issue as we have used these for
several years without any significant issues. It was also
suggested that the NetWatcher ping address be something else
besides the gateway address....say 8.8.8.8. I did this without
any resolution. <br>
<br>
</div>
<div>We will be experimenting with this over the coming weeks,
but I suspect that it is an issue with the digitizer itself.
I'll keep the group posted.<br>
<br>
</div>
<div>Regards,<br>
</div>
<div><br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"><font face="arial, helvetica,
sans-serif">Jonah Merritt
<br>
US Geological Survey
<br>
National Strong Motion Project
<br>
345 Middlefield Rd. MS-977
<br>
Menlo Park, CA 94025
<br>
(650)329-5696 (office)
<br>
(650)276-6579 (mobile)
<br>
<a moz-do-not-send="true"
href="mailto:jmerritt@usgs.gov" target="_blank">jmerritt@usgs.gov</a> </font><br>
</div>
</div>
<br>
<div class="gmail_quote">On Fri, Dec 19, 2014 at 4:43 PM,
Jacob Crummey <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jcrummey@usgs.gov" target="_blank">jcrummey@usgs.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Yolanda and Lynn,<br>
<br>
I have seen some of our Basalts loose the router info,
specifically the gateway. I have yet to figure out what
is causing this. It seems to happen on boot. My guess is
the Basalt runs fine when initially set up and then if it
reboots, it looses the routing table.<br>
<br>
Lynn, what version and update of Linux are you using on
the Basalt? And are you using the net-watcher feature
that is set up in the netconfig?<br>
<span class="HOEnZb"><font color="#888888"><br>
-Jacob<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
On Dec 19, 2014, at 2:22 PM, Yolanda Prior <<a
moz-do-not-send="true" href="mailto:yprior@usgs.gov">yprior@usgs.gov</a>>
wrote:<br>
<br>
> Have any end users of the Basalt seen similar
issues as Lynn below? Any<br>
> help for Lynn would be appreciated. Thanks!<br>
><br>
> Yolanda Prior<br>
> Engineering Technician<br>
> Albuquerque Seismological Laboratory<br>
> (505) 846-5662<br>
><br>
><br>
> -----Original Message-----<br>
> From: lynn.kaisan [mailto:<a
moz-do-not-send="true"
href="mailto:lynn.kaisan@noaa.gov">lynn.kaisan@noaa.gov</a>]<br>
> Sent: Thursday, December 18, 2014 3:01 PM<br>
> To: <a moz-do-not-send="true"
href="mailto:yprior@usgs.gov">yprior@usgs.gov</a><br>
> Subject: help with basalt, pls?<br>
><br>
> happy holidays, yolanda,<br>
><br>
> my name is lynn and i work at the pacific tsunami
warning center.<br>
><br>
> i am jumping into the maintenance of our
kinemetrics equipment without any<br>
> training and we seem to have a lot of common
problems amongst a few<br>
> stations.<br>
><br>
> may i ask if you have had this experience?<br>
><br>
> i went to three sites that were not transmitting
seismic data. at the<br>
> site, our IT guy found some settings on the modem
template that seemed to<br>
> be the culprit. things like too short tcp idle
and timeout time settings.<br>
> another basalt lost its router setting. after
changing those fields, the<br>
> site would be happy and transmitting data for a
couple months or weeks,<br>
> then...no data. we are still able to "see" the
modem (ravens) and the<br>
> received signal strength indicator is at
acceptable levels.<br>
><br>
> we use various models of the raven x modem. our
sites are metrozet or<br>
> basalt equipment, sometimes both.<br>
><br>
> if you have any idea what to check, that would be
great. for one site,<br>
> the inject process had to be restarted but it was
not the fix for the<br>
> other two...very weird.<br>
><br>
> thanks yolanda. i know i am asking a lot from
you and i appreciate it.<br>
> _______________________________________________<br>
> ANSS-netops mailing list<br>
> <a moz-do-not-send="true"
href="mailto:ANSS-netops@geohazards.usgs.gov">ANSS-netops@geohazards.usgs.gov</a><br>
> <a moz-do-not-send="true"
href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops"
target="_blank">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br>
<br>
_______________________________________________<br>
ANSS-netops mailing list<br>
<a moz-do-not-send="true"
href="mailto:ANSS-netops@geohazards.usgs.gov">ANSS-netops@geohazards.usgs.gov</a><br>
<a moz-do-not-send="true"
href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops"
target="_blank">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>