Hmmm, if they used routers that would allow a simple program to be embedded, the router could ping one of your servers and it could log the pings. Good record for when the customer went down. And – the best part – ping has payload capability, so you could embed a good ID number that would depend on NAT or anything else. You could have your server alert you if ET was not phoning home.
From: Jerry Richardson via Af Sent: Thursday, November 20, 2014 1:04 PM To: af@afmug.com Subject: Re: [AFMUG] Network Monitoring in the 2010's Right… Was pinging 8.8.8.8 last night – 174ms. Pinged 8.8.4.4 – 12ms. From: Af [mailto:af-boun...@afmug.com] On Behalf Of Travis Johnson via Af Sent: Thursday, November 20, 2014 11:57 AM To: af@afmug.com Subject: Re: [AFMUG] Network Monitoring in the 2010's Then every time Google's DNS goes down, all of your customers will be calling... LOL Travis On 11/20/2014 12:52 PM, Chuck McCown via Af wrote: As determined by DHCP adds a horrible layer of complexity for a cheap and simple device. How about ping to 8.8.8.8? From: Josh Luthman via Af Sent: Thursday, November 20, 2014 12:41 PM To: af@afmug.com Subject: Re: [AFMUG] Network Monitoring in the 2010's Red/green light for successful DNS and ping to a server determined by DHCP Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Nov 20, 2014 at 1:05 PM, Chuck McCown via Af <af@afmug.com> wrote: What would be the determining factor? Ping DNS server OK? From: Jason McKemie via Af Sent: Thursday, November 20, 2014 11:03 AM To: af@afmug.com Subject: Re: [AFMUG] Network Monitoring in the 2010's A red/green led would probably suffice for this purpose. On Thu, Nov 20, 2014 at 12:01 PM, Gino Villarini via Af <af@afmug.com> wrote: We need a “device” that plugs between router and internet connection with a big screed that says Internet OK! Or Internef BAD… filter out calls with customer having issues with wifi Gino A. Villarini President Aeronet Wireless Broadband Corp. www.aeronetpr.com @aeronetpr From: "af@afmug.com" <af@afmug.com> Reply-To: "af@afmug.com" <af@afmug.com> Date: Thursday, November 20, 2014 at 1:47 PM To: "af@afmug.com" <af@afmug.com> Subject: Re: [AFMUG] Network Monitoring in the 2010's *An app for my phone? Yuck *Something that pushes to cutomers letting them know we're having issues? Yuck *Something that let's the customer verify their particular service is good/not? That'd be great! *Web portal for billing, easy peasy Why a node fails probably won't be detectable by a machine - in some cases it's difficult for a person to narrow it down (radio, connectors, cables, ethernet, surge, etc) but I'd like to see ideas on this of course. I use/suggest an outgoing message. IF the customer is having issues and they do call us, they hear we're having issues and hang up. This means that we're not telling 100 people there are issues when 25 are effecting ending up with 75 calls next month saying we owe them a credit when they had nothing to do with an outage. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Nov 20, 2014 at 12:43 PM, Sterling Jacobson via Af <af@afmug.com> wrote: What I really want is an integrated system that isn't stuck in the 90's. I want the customer to have an app on their phone that tells them when their network is having issues and why. I want it to also remind them to pay their bill and provide a lazy/easy way to do that. I want that same system to have an engineer app that tells us when nodes fail and why. So if a node goes down and it's important, it should show up on my phone and I can take action. One of those actions would be to message to outage impacted customers the ETA to fix etc. Emails from Cacti don't count.
