Hey Gregg,
Obviously, we do use a NOAAport for a bunch of stuff. If that goes down, we get the EMWIN feed, so that at least many text products get through. EMWIN has a socket connection which bypasses the uplink and keeps things "on the air" until NOAAport gets restored. I can say that much because somebody didn't like it when I routed it to the NOAAport feed from UNIDATA. 😉
We try to source from as close to the raw feed whenever we can for everything for just these reasons.
Gilbert On Jul 20, 2023, at 3:12 PM, Gregory Grosshans <address@hidden> wrote:
I'm always curious how the private sector obtains NWS data and inquire.
In years past the private sector actually could have a connection essentially to the NWSTG/GATEWAY (when it was in Silver Springs and I think it was the X.25 lines). So there have been instances when the dissemination of NWS products aren't going out over the SBN/NOAAPORT (for a variety of reasons in the past cases), and SPC will also disseminate a product again to the NWSTG/GATEWAY to reach as many customers as possible.
In a more recent instance, something was preventing the NCF from getting NWS products from the field (AWIPS), but NCF was getting products (e.g. METARS from the FAA) from the NWSTG/GATEWAY. So SPC also disseminated our products to the NWSTG/GATEWAY and then the products traversed to the NCF for uplink. The NWSTG/GATEWAY has connections to the FAA and the Air Force so sending products that way also ensures those to organizations get the data as well.
Thanks and have a great day, Gregg On Thu, Jul 20, 2023 at 3:01 PM Gilbert Sebenste < address@hidden> wrote: Hi Gregg,
My boss, Ryan is on this list; I cannot comment on the source, but if he wants to, it's his call.
As for your second question, I typically see about a 1-2 dB increase in signal quality and strength when they go to the backup uplink.
Gilbert Sebenste AllisonHouse, LLC On Jul 20, 2023, at 1:37 PM, Gregory Grosshans <address@hidden> wrote:
Hi Gilbert,
Thanks for the information. Does Allison House obtain GOES imagery from the NOAA Big Data Project (I think there is a new name for it), GRB, or both?
I'm sure NESDIS is communicating to the NWS they are taking the necessary steps to prevent another outpage from the same type of protocol mishap.
On another note, SBN related. It appears the receivers I have access to have different signal strengths from before the switch this morning and after the switch this morning. Do others notice the same?
Gregg On Thu, Jul 20, 2023 at 1:25 PM Gilbert Sebenste < address@hidden> wrote: Hi Gregg,
Thanks for this comment. It seemed odd to me, so it sounds like he got confused or something.
I knew that they routinely switch between the ANCF in CNCF, but usually they send out an external announcement as well before they do it under the header NOUS72 KNCF. Given all that happened, it's entirely possible that message didn't get through, either.
I can't speak for Pivotal Weather, but we (AllisonHouse) also were up. And you are correct, all of those sources were indeed unaffected by the SBN/NOAAport satellite image outage.
In any case, I'm still curious as to what happened the other day…and what they are trying to do to prevent that from happening again, or at least plan for future redundancy.
Gilbert On Jul 20, 2023, at 12:41 PM, Gregory Grosshans <address@hidden> wrote:
Hi Gilbert,
The response you received about the protocol was in regards to the GOES data outage over the SBN/NOAAPORT early in July that lasted 10+ hours. During that outage, those with GRB systems, connections to the PDA, and from my understanding the NESDIS operational cloud continued to have real-time GOES data. I did hear Pivotal Weather had GOES imagery during the outage but am unsure where they obtain the data, perhaps the GOES data is on the NOAA public cloud.
NCF did email an internal NWS list yesterday about the scheduled ANCF switch to the CNCF this morning, and it looks like the SBN switch to BMGS was scheduled for 1315Z. NCF routinely switches between the ANCF and CNCF.
Perhaps the NWS Network Control isn't on the mailing list that announces the ANCF/CNCF switches.
Gregg
On Thu, Jul 20, 2023 at 12:19 PM Gilbert Sebenste < address@hidden> wrote: I just got this from John at NWS Network Control (NCO): "There was a lot of chatter about this issue, and the most I got out of it was the following: "eventually we found that a routing protocol had stopped running on the GOES-R end of the traffic flow before it hits NWAVE. Once that protocol was brought up, the traffic started flowing again."
How it happened, in order to keep it from re-occurring again is the current focus. Sorry I don't have more info.
John"
So...networking issues. He also doesn't know why they went to the backup uplink this morning. they are now having issues with the main uplink.
Just another day at the NWS…
Gilbert Sebenste AllisonHouse, LLC
On Jul 20, 2023, at 12:01 PM, Gilbert Sebenste <address@hidden> wrote:
I have confirmed that they went to the backup uplink this morning. I am attempting to find the root cause of the issue with their main uplink.
Gilbert On Jul 20, 2023, at 10:04 AM, Gilbert Sebenste <address@hidden> wrote:
It looks like they went over to the backup uplink at 13:15Z. That uplink always has the strongest signal and best carrier-to-noise. The signal jumped another 1 dB or so at that time.
Gilbert I just called NCO again. due to technical difficulties, a ticket was not generated last night, but one is being generated right now. I also had them add that we are still down 50% (roughly 3 dB) on the carrier to noise.
Gilbert
So it looks like on that graph that Stonie sent out it never really recovered completely. I see my signal is down roughly 2.5-3dB compared to the “normal” average
I get. Are others seeing the same?
Jim Weber
address@hidden
Certified Broadcast Meteorologist
FOX 13 News
WTVT - TV
3213 West Kennedy Blvd.
Tampa, Florida 33609
Phone 813-870-9657
<image001.jpg>
I just called the NWS Network Control of Operations (NCO).
They were absolutely shocked when I showed them what happened today and what's happening right now. They said nobody called in about it and nobody at the NCF or the NCO noticed this. I'm literally the first person who saw it this afternoon.
And I figured that something this bad would be noticed immediately. And the guy at NCO said "yes, I thought we would've noticed that too!".
I can't tell you how frustrated I am right now...
Hi Gilbert,
On 7/18/23 18:41, Gilbert Sebenste wrote:
> Today, it's College Of DuPage, a cellular provider turned on
> 5G at the tower 500' feet from us and wrecked our once beautiful
> signal.
Ugh!
Michael Scott: NOoooooooo!!
By the way, it looks like all of the sites reporting summary Gap
stats had high numbers of Gap messages today:
The fact that everyone had high numbers means we can not conclusively say you actually need that filter, there is clearly something else going on at a larger scale. While the timing of that 5G tower going live is _super_ coincidental with
your issues, today's numbers for everyone is even **more** coincidental IMO.
I'm not arguing against getting a better filter if you need to, if it improves your signal it could be worth it. But I am VERY interested to see tomorrow's numbers... It's not solar interference season, (ponders) what could have caused
this??
re:
> I have begun the process of getting a much better 5G filter, and
> getting it installed.
Please share with everyone CCed specifics of the 5G filter you
go with including manufacturer, cost, relevant specs, and ordering
lead time.
Seconded, please and thank you!
University Corporation for Atmospheric Research
This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee(s). If you are not an addressee indicated in this message (or responsible for delivery of the message to an addressee),
you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments that does not relate
to the official business of Fox Corporation, or its subsidiaries must be taken not to have been sent or endorsed by any of them. No representation is made that this email or its attachments are without defect.
-- ******************** I'm primarily telecommuting. If you need to reach me, call my work cell 405-249-5310. ======================================================================== Email seems to be generating increasing inefficiencies in organizations. I learned from a manager a Stanford Computer Science professor no longer uses email for communication, but uses SNAIL mail, telephone calls, and person to person visits. I'm considering the same.
405-325-2462
Storm Prediction Center
120 David L. Boren Blvd, Suite 2330 Norman, OK 73072
-- ******************** I'm primarily telecommuting. If you need to reach me, call my work cell 405-249-5310. ======================================================================== Email seems to be generating increasing inefficiencies in organizations. I learned from a manager a Stanford Computer Science professor no longer uses email for communication, but uses SNAIL mail, telephone calls, and person to person visits. I'm considering the same.
405-325-2462
Storm Prediction Center
120 David L. Boren Blvd, Suite 2330 Norman, OK 73072
-- ******************** I'm primarily telecommuting. If you need to reach me, call my work cell 405-249-5310. ======================================================================== Email seems to be generating increasing inefficiencies in organizations. I learned from a manager a Stanford Computer Science professor no longer uses email for communication, but uses SNAIL mail, telephone calls, and person to person visits. I'm considering the same.
405-325-2462
Storm Prediction Center
120 David L. Boren Blvd, Suite 2330 Norman, OK 73072
|