[ANSS-netops] help with basalt, pls?

lynn.kaisan lynn.kaisan at noaa.gov
Mon Dec 29 15:44:30 UTC 2014


your english is fine!
i apologize for responding so late.  i was on tdy and this is my first 
day back in the office.
not much of a christmas season for me!

i am so grateful that the technical world is so willing to share their
expertise and knowledge with me.  i am very eager to try your suggestion.
at this point, i don't know what version firmware we have but will start
prodding this problem.  i feel confident that i am going in the right
direction with your help.
thank you very much.
On 12/19/2014 2:52 PM, Jaffet Martinez Pagan wrote:
> Hi:
> Excuse my English. I hope you can understand me.
> First:
> You have to do the upgrades. The actual firmware is 3.10 and update 
> the Linux version  is 2.6. Some old basalts have Linux 2.4. You have 
> to update to 2.6. Kinemetrics has a step by step process in the web 
> page.An incompatibility exists between this Rockhound version (v3.10) 
> and Linux 2.4, so you have to update to Linux 2.6. Go to the 
> kinemetrics web page in the wiki section:rock family section
> Second:
> If the problem continue you have to reprogramming the CF card. If you 
> can use a new CF is better. Please see the link: 
> http://www.cdwg.com/shop/products/Transcend-CF200I-Industrial-Grade-flash-memory-card-16-GB-CompactFlas/2431762.aspx?cm_mmc=email-_-Shipping_Conf-_-Body-_-Browse_Products
> I have replaced two of them. I am using industrial grade.
> I hope this can help you
>
>
> 2014-12-19 19:40 GMT-04:00 lynn.kaisan <lynn.kaisan at noaa.gov 
> <mailto:lynn.kaisan at noaa.gov>>:
>
>     thank you all!
>
>     i do appreciate your help.
>
>     very generous!
>     =================================
>
>     On 12/19/2014 1:26 PM, Merritt, Jonah wrote:
>>     Hello everybody,
>>
>>     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.
>>
>>     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.
>>
>>     It should be noted that if you are able to log into the Raven,
>>     you can successfully ping the Basalt.
>>
>>     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.
>>
>>     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.
>>
>>     Regards,
>>
>>
>>     Jonah Merritt
>>     US Geological Survey
>>     National Strong Motion Project
>>     345 Middlefield Rd. MS-977
>>     Menlo Park, CA 94025
>>     (650)329-5696 <tel:%28650%29329-5696> (office)
>>     (650)276-6579 <tel:%28650%29276-6579> (mobile)
>>     jmerritt at usgs.gov <mailto:jmerritt at usgs.gov>
>>
>>     On Fri, Dec 19, 2014 at 4:43 PM, Jacob Crummey <jcrummey at usgs.gov
>>     <mailto:jcrummey at usgs.gov>> wrote:
>>
>>         Hi Yolanda and Lynn,
>>
>>         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.
>>
>>         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?
>>
>>         -Jacob
>>
>>
>>
>>         On Dec 19, 2014, at 2:22 PM, Yolanda Prior <yprior at usgs.gov
>>         <mailto:yprior at usgs.gov>> wrote:
>>
>>         > Have any end users of the Basalt seen similar issues as
>>         Lynn below? Any
>>         > help for Lynn would be appreciated. Thanks!
>>         >
>>         > Yolanda Prior
>>         > Engineering Technician
>>         > Albuquerque Seismological Laboratory
>>         > (505) 846-5662 <tel:%28505%29%20846-5662>
>>         >
>>         >
>>         > -----Original Message-----
>>         > From: lynn.kaisan [mailto:lynn.kaisan at noaa.gov
>>         <mailto:lynn.kaisan at noaa.gov>]
>>         > Sent: Thursday, December 18, 2014 3:01 PM
>>         > To: yprior at usgs.gov <mailto:yprior at usgs.gov>
>>         > Subject: help with basalt, pls?
>>         >
>>         > happy holidays, yolanda,
>>         >
>>         > my name is lynn and i work at the pacific tsunami warning
>>         center.
>>         >
>>         > i am jumping into the maintenance of our kinemetrics
>>         equipment without any
>>         > training and we seem to have a lot of common problems
>>         amongst a few
>>         > stations.
>>         >
>>         > may i ask if you have had this experience?
>>         >
>>         > i went to three sites that were not transmitting seismic
>>         data.  at the
>>         > site, our IT guy found some settings on the modem template
>>         that seemed to
>>         > be the culprit.  things like too short tcp idle and timeout
>>         time settings.
>>         > another basalt lost its router setting.  after changing
>>         those fields, the
>>         > site would be happy and transmitting data for a couple
>>         months or weeks,
>>         > then...no data.  we are still able to "see" the modem
>>         (ravens) and the
>>         > received signal strength indicator is at acceptable levels.
>>         >
>>         > we use various models of the raven x modem.  our sites are
>>         metrozet or
>>         > basalt equipment, sometimes both.
>>         >
>>         > if you have any idea what to check, that would be great. 
>>         for one site,
>>         > the inject process had to be restarted but it was not the
>>         fix for the
>>         > other two...very weird.
>>         >
>>         > thanks yolanda.  i know i am asking a lot from you and i
>>         appreciate it.
>>         > _______________________________________________
>>         > ANSS-netops mailing list
>>         > ANSS-netops at geohazards.usgs.gov
>>         <mailto:ANSS-netops at geohazards.usgs.gov>
>>         > https://geohazards.usgs.gov/mailman/listinfo/anss-netops
>>
>>         _______________________________________________
>>         ANSS-netops mailing list
>>         ANSS-netops at geohazards.usgs.gov
>>         <mailto:ANSS-netops at geohazards.usgs.gov>
>>         https://geohazards.usgs.gov/mailman/listinfo/anss-netops
>>
>>
>
>
>     _______________________________________________
>     ANSS-netops mailing list
>     ANSS-netops at geohazards.usgs.gov
>     <mailto:ANSS-netops at geohazards.usgs.gov>
>     https://geohazards.usgs.gov/mailman/listinfo/anss-netops
>
>
>
>
> -- 
> Ing. Jaffet Martinez Pagán, EIT
> Puerto Rico Strong Motion Program
> Civil Engeneering Department
> Mayaguez Campus
> University of Puerto Rico
> 787-832-4040 x 3341
> Fax 787-831-2745

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/anss-netops/attachments/20141229/393a839b/attachment.html>


More information about the ANSS-netops mailing list