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

Re: 20000710: Addtional Failover requested for Michigan State

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20000710: Addtional Failover requested for Michigan State
  • Date: Mon, 10 Jul 2000 11:08:23 -0600 (MDT)
Hi James, 

Sorry to hear you are experiencing connectivity issues with Millersville.

By all means we can investigate a different/another failover site, nobody
wants to be without data.

Would you please do traceroutes to

redwood.atmos.albany.edu

weather.geo.uwm.edu

and

squall.atmos.uiuc.edu

to see how viable these choices are..

Please attach the results and we can go from there.

Thanks,

-Jeff
__________
Jeff Weber
Unidata/NWS-COMET Case Study Library
University Corp for Atmospheric Research

address@hidden
PH:303-497-8676   
URL--http://www.unidata.ucar.edu/staff/jweber
________________________________________________

On Mon, 10 Jul 2000, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >cc: address@hidden,
> >cc: address@hidden
> >From: James T Brown <address@hidden>
> >Subject: Addtional Failover ???
> >Organization: Michigan State
> >Keywords: 200007101340.e6ADeNT10583 IDD failover
> 
> IDD Support:
> 
> I help to maintain the LDM software and IDD node in
> the Department of Geography at Michigan State University.
> 
> Currently, we are configured with the following:
> 
>    Primary Feed:    sunset.meteor.wisc.edu
>    Failover Feed:   twister.millersv.edu
> 
> 
> This setup has been in place since approximately June, 1998
> when we switched the source of our primary feed from TWISTER
> to SUNSET.
> 
> This past weekend, we temporary lost connection with our
> primary site (sunset).  The LDM is configured to automatically
> switch to the failover, but a connection to "twister" proved
> fruitless.  The troubles with our connection to "sunset" 
> have since cleared and we have re-established our connection
> with our primary.  Upon checking the status of our failover
> site (twister) this Monday morning, I notice that we still
> can not communicate with that machine:
> 
> > cirrus{ldm} 32:% /usr/sbin/ping twister.millersv.edu
> > ICMP 13 Unreachable from gateway mae-east.voicenet.net (192.41.177.97)
> >  for icmp from cirrus (35.9.73.90) to twister.millersv.edu (166.66.44.84)
> > ICMP 13 Unreachable from gateway mae-east.voicenet.net (192.41.177.97)
> >  for icmp from cirrus (35.9.73.90) to twister.millersv.edu (166.66.44.84)
> 
> This often seems to be the norm.  The connection to "sunset"
> has been quite reliable, but during those times that we lose
> a connection with Wisconsin, we typically lose data due to
> an apparent poor connection with our failover site.
> 
> I am curious if it is possible for us to be configured with an
> additional or replacement failover site?  The agricultural growing 
> season is a critical time of year for our operations and we might 
> like a more reliable failover than what "twister" currently seems 
> to be providing.
> 
> Many thanks for consideration in this request.
> 
> Jim
>  
> 
> -- 
> ==========================================================
> James T. Brown   
> UNIX Systems Administrator
> Geography/Fisheries & Wildlife
> Michigan State University
> 
> email: address@hidden
> 
> 
> ------- End of Forwarded Message
> 
>