-
Get involved.
We want your input!
Apply for Membership and join the conversations about everything related to broadcasting.
After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
If you use a disposable or false email address, your registration will be rejected.
After your membership is approved, please take a minute to tell us a little bit about yourself.
https://www.radiodiscussions.com/forums/introduce-yourself.1088/
Thanks in advance and have fun!
RadioDiscussions Administrators
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
SAGE internet access setup?
- Thread starter TomZ
- Start date
See if you have the most recent version of the software (sagealertingsystems.com)
Installing that seemed to cure some problems with my units--
Also, you may need to set up all the static addresses in your "network" tab in the endecsetd program.
That part is over my head, but proved to be the key to get the box to talk to the internet for us.
(We brought in a guru).
Installing that seemed to cure some problems with my units--
Also, you may need to set up all the static addresses in your "network" tab in the endecsetd program.
That part is over my head, but proved to be the key to get the box to talk to the internet for us.
(We brought in a guru).
TomZ said:I'm stumped and an hour of Google hasn't helped me find the procedure to setup a new SAGE for internet access. I'm able to get there through the router on the LAN but I'm not finding a 'dummies' answer...
I can link to the ES2 file if that helps.
The entire manual for the 3644 is available online at www.sagealertingsystems.com. IIRC one of the menus available from the front panel is Network Setup. You can program the box for either DHCP or a static IP, but to reach the built-in web server (including the EAS logs) a static address works much better. As TomT stated, make sure you install the latest firmware (89.x) update, which among other things improves the box's network performance.
Here is my attempt at a "dummies" guide...
I am assuming you are setting this up at the studio, and I assume there are other computers plugged into the same network.
From one of your "internet" computers click START, RUN, and type CMD.exe (on Win XP) or Start, in the search bar type CMD and click the CMD.exe program it finds (on Vista/Win 7). This will open a little DOS window. Type IPCONFIG and hit enter. This will show you the network setting that computer is using to connect to the internet. The the numbers you're interested in are IPv4 address, Subnet Mask, and Default Gateway.
An example would be:
IPv4 address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
On the Endec, the Subnet Mask and the Default Gateway will be the same as the computer. The IP address will need to be different. Hopefully you have a list somewhere of unused IP addresses, otherwise you may just have to pick one between 1-254.
I would suggest something like 192.168.1.200 because odds are nobody is using one that high. Don't make your IP address and your Default Gateway the same, big no-no.
Hopefully that will get you going. If not you can message me and I'll be happy to help you out more.
I am assuming you are setting this up at the studio, and I assume there are other computers plugged into the same network.
From one of your "internet" computers click START, RUN, and type CMD.exe (on Win XP) or Start, in the search bar type CMD and click the CMD.exe program it finds (on Vista/Win 7). This will open a little DOS window. Type IPCONFIG and hit enter. This will show you the network setting that computer is using to connect to the internet. The the numbers you're interested in are IPv4 address, Subnet Mask, and Default Gateway.
An example would be:
IPv4 address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
On the Endec, the Subnet Mask and the Default Gateway will be the same as the computer. The IP address will need to be different. Hopefully you have a list somewhere of unused IP addresses, otherwise you may just have to pick one between 1-254.
I would suggest something like 192.168.1.200 because odds are nobody is using one that high. Don't make your IP address and your Default Gateway the same, big no-no.
Hopefully that will get you going. If not you can message me and I'll be happy to help you out more.
Thanks for your reply, LazyJ.
The link will produce an image of the screenshot showing ipconfig /all, the gui of the SAGE and also the router's user list.
I think I'm wrong in using the DNS numbers in the SAGE gui.. what say You?
I can administer it through TeamViewer but I'm wanting to directly access it over the web.
https://dl.dropbox.com/u/15067584/sage%20screenshot.JPG
The link will produce an image of the screenshot showing ipconfig /all, the gui of the SAGE and also the router's user list.
I think I'm wrong in using the DNS numbers in the SAGE gui.. what say You?
I can administer it through TeamViewer but I'm wanting to directly access it over the web.
https://dl.dropbox.com/u/15067584/sage%20screenshot.JPG
Your setup looks good. I'm not sure where you got the address in DNS #1, but I generally use the Gateway address as the DNS server #1. Then, for DNS #2 I use the Google public DNS (8.8.8.8). By using the gateway address in the DNS #1, it uses your ISP for DNS.
What type of "internet" access are you trying to achieve? Are you having trouble getting the IPAWS server to connect? If so, it could definitely be the DNS server.
What type of "internet" access are you trying to achieve? Are you having trouble getting the IPAWS server to connect? If so, it could definitely be the DNS server.
I do my weekly visit to another SAGE enabled site tomorrow and I'll take a peak at the router's settings...
This SAGE is available via the IP address.
https://dl.dropbox.com/u/15067584/sage%20screenshot%20kkcv.JPG
This SAGE is available via the IP address.
https://dl.dropbox.com/u/15067584/sage%20screenshot%20kkcv.JPG
Ok, so your wanting to look at the Endec's internal webpage via an external IP address? It looks like the second Endec you posted is probably the only thing connected at that internet connection. There was a discussion about this same issue a while back. I believe you have to port forward port 80 for your Endec. That way you can punch in your external IP and it will go to the Endec's webpage.
This may help...
http://radiodiscussions.com/smf/index.php?topic=198425.0
This may help...
http://radiodiscussions.com/smf/index.php?topic=198425.0
My SAGE received today's CAP test; but it sent one, too..... ???
What's the deal here?
Sent 09/03/12 11:05:25 Required Weekly Test, Sent from header RWT.
The Civil Authorities have issued a Required Weekly Test for all of Alabama, all of Arkansas, all of Iowa, all of Illinois, all of Kansas, all of Louisiana, all of Minnesota, all of Missouri, all of Mississippi, all of North Dakota, all of Nebraska, all of Oklahoma, all of South Dakota, all of Tennessee, all of Texas, and all of Wisconsin beginning at 11:05 am and ending at 12:05 pm (KKBS).
CAP Reference ID: [email protected],RWT_CDT_2012831252,2012-09-03T12:05:02-04:00
CAP Text: The Civil Authorities have issued a Required Weekly Test for all of Alabama, all of Arkansas, all of Iowa, all of Illinois, all of Kansas, all of Louisiana, all of Minnesota, all of Missouri, all of Mississippi, all of North Dakota, all of Nebraska, all of Oklahoma, all of South Dakota, all of Tennessee, all of Texas, and all of Wisconsin beginning at 11:05 am and ending at 12:05 pm (KKBS). Test Message IPAWS OPEN CAP EAS Feed Configuration Test Message
Received 09/03/12 11:05:17 Matched filter RWT, Received from CAP. Timed Relay. Alert received 09/03/12 11:05:43.
The Civil Authorities have issued a Required Weekly Test for all of Alabama, all of Arkansas, all of Iowa, all of Illinois, all of Kansas, all of Louisiana, all of Minnesota, all of Missouri, all of Mississippi, all of North Dakota, all of Nebraska, all of Oklahoma, all of South Dakota, all of Tennessee, all of Texas, and all of Wisconsin beginning at 11:05 am and ending at 12:05 pm (fromcap).
CAP Server: IPAWS
CAP Reference ID: [email protected],RWT_CDT_2012831252,2012-09-03T12:05:02-
What's the deal here?
The printout shows it is setup for Timed Relay - so that's what it did.
Yes sir.
was: SAGE internet access setup? now IPAWS OPEN failure logging....
Today's noise about server failure events...
Today's noise about server failure events...
Send sbe-eas mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://seven.pairlist.net/mailman/listinfo/sbe-eas
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sbe-eas digest..."
Today's Topics:
1. IPAWS OPEN down since 0821 PDT Saturday (Richard Rudman)
2. IPAWS OPEN failure update as of 0830 PDT 9/23 (Richard Rudman)
3. Re: IPAWS OPEN down since 0821 PDT Saturday (Jerry Mathis)
4. IPAWS OPEN is back up (Richard Rudman)
5. Re: IPAWS OPEN failure update as of 0830 PDT 9/23 (Will Robedee)
6. Re: IPAWS OPEN failure (Richard Rudman)
----------------------------------------------------------------------
Message: 1
Date: Sun, 23 Sep 2012 07:29:29 -0700
From: Richard Rudman <[email protected]>
Subject: [sbe-eas] IPAWS OPEN down since 0821 PDT Saturday
To: "SBE communication issues." <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; CHARSET=US-ASCII
I have positive confirmation from EAS clients in multiple states across the country that FEMA's IPAWS OPEN server has been offline since yesterday morning. I got emails from 25 EAS boxes in Southern California shortly after 0821.
As of 0730 PDT, IPAWS OPEN is still down, and no official explanation from FEMA about what happened and when the server will be back up.
Richard Rudman
CA EAS SECC Vice Chair
------------------------------
Message: 2
Date: Sun, 23 Sep 2012 08:40:04 -0700
From: Richard Rudman <[email protected]>
Subject: [sbe-eas] IPAWS OPEN failure update as of 0830 PDT 9/23
To: "SBE communication issues." <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; CHARSET=US-ASCII
> From FEMA:
Verizon had a major equipment failure which took the DHS primary and alternate servers off line for about 12 hours. After we complete the post-mortum, Antwane and his team will send you a report. The server was reported back up at 9:30 last night. The outage also affected our email so we could not send out a notice.
I sent a message back to FEMA that the IPAWS OPEN server is still not available for polling as of 0830 PDT today. Rebooting one EAS device I monitor did not resolve this.
A return message I just received says that IPAWS OPEN management is on site and working on the issue.
Richard Rudman
------------------------------
Message: 3
Date: Sun, 23 Sep 2012 11:47:21 -0500
From: Jerry Mathis <[email protected]>
Subject: Re: [sbe-eas] IPAWS OPEN down since 0821 PDT Saturday
To: "SBE EAS Exchange - a mail list for discussion about the Emergency
Alert System and other emergency communication issues."
<[email protected]>
Message-ID:
<CACQG-jT4S4m2Eqz8LhnrKGf9forpJQaF0q3x0qjTj0S1dW7gHg@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Ya gotta wonder if that will be the standard of care in case of a real
emergency.
--
Jerry Mathis
On Sun, Sep 23, 2012 at 9:29 AM, Richard Rudman <[email protected]> wrote:
> I have positive confirmation from EAS clients in multiple states across
> the country that FEMA's IPAWS OPEN server has been offline since yesterday
> morning. I got emails from 25 EAS boxes in Southern California shortly
> after 0821.
>
> As of 0730 PDT, IPAWS OPEN is still down, and no official explanation from
> FEMA about what happened and when the server will be back up.
>
> Richard Rudman
> CA EAS SECC Vice Chair
>
>
> _______________________________________________
> sbe-eas mailing list
> [email protected]
> http://seven.pairlist.net/mailman/listinfo/sbe-eas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/sbe-eas/attachments/20120923/e9b69be0/attachment-0001.html>
------------------------------
Message: 4
Date: Sun, 23 Sep 2012 13:41:08 -0700
From: Richard Rudman <[email protected]>
Subject: [sbe-eas] IPAWS OPEN is back up
To: "SBE communication issues." <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; CHARSET=US-ASCII
IPAWS OPEN came back up at 11:47:17 PDT.
We are waiting for word from FEMA on what happened and what can be done to keep this from happening again.
Richard Rudman
------------------------------
Message: 5
Date: Sun, 23 Sep 2012 23:42:42 -0500
From: "Will Robedee" <[email protected]>
Subject: Re: [sbe-eas] IPAWS OPEN failure update as of 0830 PDT 9/23
To: "'SBE EAS Exchange - a mail list for discussion about the
Emergency Alert System and other emergency communication issues.'"
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
So will they generate a public list of down times so we can report the
nature of the failure in our EAS logs? Or since a test wasn't missed, is
there no need to log the outage?
Will R
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Richard Rudman
Sent: Sunday, September 23, 2012 10:40 AM
To: SBE communication issues.
Subject: [sbe-eas] IPAWS OPEN failure update as of 0830 PDT 9/23
> From FEMA:
Verizon had a major equipment failure which took the DHS primary and
alternate servers off line for about 12 hours. After we complete the
post-mortum, Antwane and his team will send you a report. The server was
reported back up at 9:30 last night. The outage also affected our email so
we could not send out a notice.
I sent a message back to FEMA that the IPAWS OPEN server is still not
available for polling as of 0830 PDT today. Rebooting one EAS device I
monitor did not resolve this.
A return message I just received says that IPAWS OPEN management is on site
and working on the issue.
Richard Rudman
_______________________________________________
sbe-eas mailing list
[email protected]
http://seven.pairlist.net/mailman/listinfo/sbe-eas
!DSPAM:4090,505f2d6b251223136986249!
------------------------------
Message: 6
Date: Mon, 24 Sep 2012 06:13:14 -0700
From: Richard Rudman <[email protected]>
Subject: Re: [sbe-eas] IPAWS OPEN failure
To: "SBE communication issues." <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Will/Everyone:
The Broadcast Warning Working Group sent an email to the FCC people responsible for Part 11 yesterday asking what they expect to see regarding EAS log entries for CAP outages. Attaching the email I posted this email to your EAS log for last week and this week should cover things until we get more information on what happened, but the FCC is of course the final arbiter of that.
IPAWS OPEN Outage began at: 11:21 EDT
IPAWS OPEN Outage ended: 14:47 EDT
If we get word from the FCC about the logging issue Will raised it will first be posted on the EAS Forum list server [eas.radiolists.net]. We will then try to get it out to other EAS client information resources like this one.
We are also awaiting FEMA's after action report they promised us.
Richard Rudman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/sbe-eas/attachments/20120924/4743006d/attachment.htm>
------------------------------
_______________________________________________
sbe-eas mailing list
[email protected]
http://seven.pairlist.net/mailman/listinfo/sbe-eas
End of sbe-eas Digest, Vol 97, Issue 3
**************************************
My understanding is that you only need to make a note in your logs if you miss a weekly test. As long as you still get a weekly test from IPAWS this week, then it's not an issue that the server was down. Of course, it doesn't instill much confidence if the system can be killed that easily.
- Status
- This thread has been closed due to inactivity. You can create a new thread to discuss this topic.