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

Re: No WSI feed from wsihcsn.unidata.ucar.edu to iita at 99082610 (fwd)

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: No WSI feed from wsihcsn.unidata.ucar.edu to iita at 99082610 (fwd)
  • Date: Thu, 2 Sep 1999 16:03:33 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Thu, 26 Aug 1999 13:20:07 -0600
From: Mike Schmidt <address@hidden>
To: David Himes <address@hidden>, address@hidden
    Steve A Drake <address@hidden>
Subject: Re: No WSI feed from wsihcsn.unidata.ucar.edu to iita at 99082610

All,

I agree with Dave's analysis -- while we did have a number of significant
disruptions in the last week related to network changes and upgrades,
they are not the current problem.  I'll be watching the wsi system
closely for system performance and related issues...

mike

On Aug 26,  9:48am, David Himes wrote:
> Subject: Re: No WSI feed from wsihcsn.unidata.ucar.edu to iita at 99082610
>
> ...  and as
> far as anyone can tell, it is not an SCD problem right now.  There have
> been several SCD problems over the past week that were major.
> Yesterday for at least two hours in the morning, the NETS group had
> router filters installed incorrectly that caused major problems for our
> networks.
>
> As far as I know, there is no problem occurring that can be called
> "network" problems.