<br>Thanks for the advice, we will give that and the firmware upgrade a try and see if things improve.<br><br>Philip<br><br><div class="gmail_quote">On Wed, Dec 15, 2010 at 12:55 PM, Mark E Meremonte <span dir="ltr"><<a href="mailto:meremonte@usgs.gov">meremonte@usgs.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><font face="sans-serif" size="2">Phillip,</font>
<br>
<br><font face="sans-serif" size="2">Your problem sounds like a problem with
the RT-130's TCP/IP stack's inability to detect a down, then up, network
connection. I use to get this problem much in the early history
of the RT-130s. I got around it by enabling continuous IP device
power to the IP stack rather then toggle/auto. And, to this day,
I still always enable continuous IP device power as a matter of course
to prevent the possibility of it happening especially when there is a radio
in the IP link instead of a "hard" landline connection.</font>
<br>
<br><font face="sans-serif" size="2">Mark</font>
<br>
<br><font face="sans-serif" size="2">******************************************************************************<br>
Mark E. Meremonte Geophysicist
USGS/ANSS/NEIC<br>
<br>
U.S. Geological Survey Work: 303-273-8670 Cell:
303-478-5766<br>
MS 966, Box 25046 Email:
<a href="mailto:meremonte@usgs.gov" target="_blank">meremonte@usgs.gov</a><br>
Denver, CO 80225
Web: </font><a href="http://geohazards.cr.usgs.gov/" target="_blank"><font face="sans-serif" size="2">http://geohazards.cr.usgs.gov</font></a><font face="sans-serif" size="2"><br>
<br>
Ship: U.S. Geological Survey, 1711 Illinois St., Golden, CO 80401<br>
******************************************************************************</font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td><font color="#5f5f5f" face="sans-serif" size="1">From:</font>
</td><td><font face="sans-serif" size="1">Philip Crotwell <<a href="mailto:crotwell@seis.sc.edu" target="_blank">crotwell@seis.sc.edu</a>></font>
</td></tr><tr valign="top">
<td><font color="#5f5f5f" face="sans-serif" size="1">To:</font>
</td><td><font face="sans-serif" size="1"><a href="mailto:mwithers@memphis.edu" target="_blank">mwithers@memphis.edu</a></font>
</td></tr><tr>
<td valign="top"><font color="#5f5f5f" face="sans-serif" size="1">Cc:</font>
</td><td><div class="im"><font face="sans-serif" size="1"><a href="mailto:anss-netops@geohazards.usgs.gov" target="_blank">anss-netops@geohazards.usgs.gov</a></font>
</div></td></tr><tr valign="top">
<td><font color="#5f5f5f" face="sans-serif" size="1">Date:</font>
</td><td><font face="sans-serif" size="1">12/14/2010 16:34</font>
</td></tr><tr valign="top">
<td><font color="#5f5f5f" face="sans-serif" size="1">Subject:</font>
</td><td><div class="im"><font face="sans-serif" size="1">Re: [ANSS-netops] rtp2rtpd question</font>
</div></td></tr><tr valign="top">
<td><font color="#5f5f5f" face="sans-serif" size="1">Sent by:</font>
</td><td><font face="sans-serif" size="1"><a href="mailto:anss-netops-bounces@geohazards.usgs.gov" target="_blank">anss-netops-bounces@geohazards.usgs.gov</a></font></td></tr></tbody></table>
<br>
<hr noshade><div><div></div><div class="h5">
<br>
<br>
<br><tt><font size="2">I have not had much experience with rtp2rtpd except
between two<br>
computers on the same local subnet, so I haven't seen this exact<br>
problem. However, we have seen lots of cases where a link to a single<br>
station (cell modem) goes down and comes back up, but the rtp<br>
connection doesn't. Sometimes it comes back eventually (hours to days)<br>
and sometimes we have to go out and push the power button. We also end<br>
up with data gaps even in cases of very short outages that should not<br>
exceed the local buffer. Lots of weirdness I just don't understand.<br>
<br>
Any chance your issue was with the station to rtpd link instead of the<br>
rtp2rtpd link? Not that I have anything useful in that case other than<br>
sympathy but at least you aren't alone. :(<br>
<br>
Philip<br>
<br>
On Tue, Dec 14, 2010 at 11:23 AM, <<a href="mailto:mwithers@memphis.edu" target="_blank">mwithers@memphis.edu</a>> wrote:<br>
><br>
> We have rtpd running at a remote node and rtp2rtpd on that node transfering<br>
> the data to a central site via private microwave. Inclement
weather<br>
> frequently disrupts comm over the microwave link. During a recent<br>
> disruption, when comm was restored, rtp2rtpd was successfully transfering<br>
> data for some stations but not others. So I stopped and restarted
rtp2rtpd<br>
> and data transmission was restored. I don't see anything significant
in<br>
> the logs to suggest what the problem was. Has anyone running
rtp2rtpd<br>
> seen this sort of thing before and if so, what did you do to correct
it<br>
> so that you resume data transmission without manual intervention?<br>
><br>
> Mitch<br>
><br>
> Center for Earthquake Research and Information (CERI)<br>
> University of Memphis
Ph: 901-678-4940<br>
> Memphis, TN 38152
Fax: 901-678-4734<br>
><br>
> _______________________________________________<br>
> ANSS-netops mailing list<br>
> <a href="mailto:ANSS-netops@geohazards.usgs.gov" target="_blank">ANSS-netops@geohazards.usgs.gov</a><br>
> </font></tt><a href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops" target="_blank"><tt><font size="2">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</font></tt></a><tt><font size="2"><br>
><br>
_______________________________________________<br>
ANSS-netops mailing list<br>
<a href="mailto:ANSS-netops@geohazards.usgs.gov" target="_blank">ANSS-netops@geohazards.usgs.gov</a><br>
</font></tt><a href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops" target="_blank"><tt><font size="2">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</font></tt></a><tt><font size="2"><br>
</font></tt>
<br>
<br></div></div></blockquote></div><br>