[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20020107: MSU: ** Network Troubles to my Primary Feed

Hi Jim, 

I do not know if you have contacted your upstream site admin:

Please see:

http://unidata.ucar.edu/projects/idd/sitelist.html

You will find that

Pete Pokrandt

address@hidden

maintains sunset. I personally know that sunset was up and down a bit last
week, as Pete was installing a CD burner, may or may not be part of your
problem, but I suspect it is, because his clock got off by over an hour
for awhile.

I suspect that sunset will be stable from here out, but please let me know
if this persists, and we can investigate further if need be.


Thank you

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Mon, 7 Jan 2002, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: address@hidden,
> >cc: address@hidden
> >From: James T Brown <address@hidden>
> >Subject: ** Network Troubles to my Primary Feed 
> >Organization: Michigan State University
> >Keywords: 200201071513.g07FD9N08339 IDD
> 
> IDD Support:
> 
> Over the past week, I have been experiencing some trouble 
> keeping a network connection to my primary IDD site at
> Wisconsin (sunset.meteor.wisc.edu).  The cron entry that
> is used to switch to the failover site:
> 
>    0,20,40 * * * * bin/ldmfail -p "sunset.meteor.wisc.edu" -f
> "squall.atmos.uiuc.edu"
> 
> 
> switches back and forth between my primary and failover
> nearly every hour.  Some example email subject headers
> from this morning:
> 
>    Switched LDM to failover feed     5:20
>    Switched back to primary feed     5:40
>    Switched LDM to failover feed     6:20
>    Switched back to primary feed     6:40
>    Switched LDM to failover feed     7:00
>    Switched back to primary feed     7:20
>    Switched LDM to failover feed     8:40
>    Switched back to primary feed     9:00
>    Switched LDM to failover feed     9:20
> 
> 
> 
> Trying to isolate the source of the problem, I have run the
> following commands:
> 
>    (primary)
> 
>       % ping -s -I 30 sunset.meteor.wisc.edu 64 20
>       PING sunset.meteor.wisc.edu: 64 data bytes
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=0.
> time=36. ms
>       ICMP Host Unreachable from gateway g3-0.msu4.mich.net
> (35.9.82.114)
>        for icmp from rockies (35.9.73.4) to sunset.meteor.wisc.edu
> (144.92.130.6)
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=3.
> time=34. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=4.
> time=34. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=7.
> time=35. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=8.
> time=34. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=9.
> time=34. ms
>       ICMP Host Unreachable from gateway g3-0.msu4.mich.net
> (35.9.82.114)
>        for icmp from rockies (35.9.73.4) to sunset.meteor.wisc.edu
> (144.92.130.6)
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=12.
> time=35. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=13.
> time=35. ms
>       ICMP Host Unreachable from gateway g3-0.msu4.mich.net
> (35.9.82.114)
>        for icmp from rockies (35.9.73.4) to sunset.meteor.wisc.edu
> (144.92.130.6)
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=16.
> time=34. ms
>       72 bytes from sunset.meteor.wisc.edu (144.92.130.6): icmp_seq=17.
> time=35. ms
> 
>       ----sunset.meteor.wisc.edu PING Statistics----
>       20 packets transmitted, 10 packets received, 50% packet loss
>       round-trip (ms)  min/avg/max = 34/34/36
> 
> 
> 
>    (failover)
> 
>       % ping -s -I 30 squall.atmos.uiuc.edu 64 20
>       PING squall.atmos.uiuc.edu: 64 data bytes
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=0.
> time=14. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=1.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=2.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=3.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=4.
> time=14. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=5.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=6.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=7.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=8.
> time=14. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=9.
> time=14. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=10.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=11.
> time=44. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=12.
> time=18. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=13.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=14.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=15.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=16.
> time=14. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=17.
> time=33. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=18.
> time=13. ms
>       72 bytes from squall.atmos.uiuc.edu (128.174.80.44): icmp_seq=19.
> time=63. ms
> 
>       ----squall.atmos.uiuc.edu PING Statistics----
>       20 packets transmitted, 20 packets received, 0% packet loss
>       round-trip (ms)  min/avg/max = 13/18/63
> 
> 
> 
> Recent entries from my "ldmd.log" file show:
> 
>    Jan 07 15:05:28 cirrus sunset[23530]: h_clnt_call:
> sunset.meteor.wisc.edu: FEEDME: time elapsed  51.597302
>    Jan 07 15:05:28 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> reclass: 20020107140436.442 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
>    Jan 07 15:05:28 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> OK
>    Jan 07 15:07:31 cirrus sunset[23530]: Connection reset by peer
>    Jan 07 15:07:31 cirrus sunset[23530]: Disconnect
>    Jan 07 15:08:01 cirrus sunset[23530]: run_requester:
> 20020107150712.776 TS_ENDT {{FSL|UNIDATA,  ".*"}}
>    Jan 07 15:08:02 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> reclass: 20020107150712.776 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
>    Jan 07 15:08:02 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> OK
>    Jan 07 15:09:32 cirrus sunset[23530]: Connection reset by peer
>    Jan 07 15:09:32 cirrus sunset[23530]: Disconnect
>    Jan 07 15:10:02 cirrus sunset[23530]: run_requester:
> 20020107150838.793 TS_ENDT {{FSL|UNIDATA,  ".*"}}
>    Jan 07 15:10:02 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> reclass: 20020107150838.793 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
>    Jan 07 15:10:02 cirrus sunset[23530]: FEEDME(sunset.meteor.wisc.edu):
> OK
> 
> 
> 
> 
> Sample output of "tracroute" to my primary site (during times of
> trouble):
> 
>    % traceroute sunset.meteor.wisc.edu
>    traceroute to sunset.meteor.wisc.edu (144.92.130.6), 30 hops max, 40
> byte packets
>     1  ns-rtr-s9-73.net.msu.edu (35.9.73.1)  1.195 ms  0.766 ms  0.755
> ms
>     2  agh-rtr-ge7.net.msu.edu (35.9.102.21)  0.699 ms  0.643 ms  0.641
> ms
>     3  com-rtr-ge33.net.msu.edu (35.9.102.53)  1.152 ms  1.080 ms  1.055
> ms
>     4  cc-rtr-ge15.net.msu.edu (35.9.101.13)  1.152 ms  1.038 ms  1.035
> ms
>     5  g3-0.msu4.mich.net (35.9.82.114)  0.481 ms !H * *
>     6  * * *
>     7  g3-0.msu4.mich.net (35.9.82.114)  0.592 ms !H * *
>     8  * * *
>     9  * * *
>    10  144.92.128.206 (144.92.128.206)  34.483 ms  34.112 ms  33.617 ms
>    11  sunset.meteor.wisc.edu (144.92.130.6)  34.771 ms  34.419 ms 
> 34.297 ms
> 
> 
> 
> Any suggestions?
> 
> 
> 
> Thanks.
> 
> 
> -Jim
> 
> 
> 
> 
>    
> 
> 
> 
> 
> -- 
> ==========================================================
> James T. Brown   
> UNIX Systems Administrator
> Geography/Fisheries & Wildlife
> Michigan State University
> 
> email: address@hidden
> 
> 
> ------- End of Forwarded Message
> 
> 

>From address@hidden Mon Jan  7 13:02:53 2002
>Subject: Re: ** Network Troubles to my Primary Feed 

In a previous message to me, you wrote: 

 >Pete:
 >
 >Thanks for running the traceroute in the opposite direction.
 >Once the network leaves my lab, it is pretty much out of my
 >control.   I will contact my campus network administrators 
 >to see if they can help isolate the problem.

Jim,

No problem. Yea, I'm in pretty much the same boat here. All
I can usually do is call our network ops and describe the
problem, see if they can reproduce it, and then they look
into it farther on down the line.


 >
 >I haven't noticed any other network problems so thought I 
 >would check with you first.  Hopefully, the campus gurus
 >can come up with something.

Good luck, let me know if there's anything else I can do.

Pete

--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+

>From address@hidden Wed Jan  9 08:25:44 2002
>To: Pete Pokrandt <address@hidden>
>CC: address@hidden, address@hidden
>Subject: Re: ** Network Troubles to my Primary Feed

Pete (and Unidata IDD Support):

Just wanted to send an update.

As of Wednesday (Jan 09) morning, my network connection 
to your site (sunset.meteor.wisc.edu) appears to have
stabilized.  Yesterday morning, packet loss was still
running between 50-60%, but this morning it is at 0%.

I'm am hoping the trouble has been resolved, but I will 
continue to monitor things.

Thanks.


-jim





> 
> 
> In a previous message to me, you wrote:
> 
>  >Pete:
>  >
>  >Thanks for running the traceroute in the opposite direction.
>  >Once the network leaves my lab, it is pretty much out of my
>  >control.   I will contact my campus network administrators
>  >to see if they can help isolate the problem.
> 
> Jim,
> 
> No problem. Yea, I'm in pretty much the same boat here. All
> I can usually do is call our network ops and describe the
> problem, see if they can reproduce it, and then they look
> into it farther on down the line.
> 
>  >
>  >I haven't noticed any other network problems so thought I
>  >would check with you first.  Hopefully, the campus gurus
>  >can come up with something.
> 
> Good luck, let me know if there's anything else I can do.
> 
> Pete
> 
> --
> +>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
> ^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
> ^ Systems Programmer               V Madison,         WI     53706    ^
> ^                                  V      address@hidden       ^
> ^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
> ^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+

-- 
==========================================================
James T. Brown   
UNIX Systems Administrator
Geography/Fisheries & Wildlife
Michigan State University

email: address@hidden