Automatically monitor your Internet service and provider with alerts to problems
Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
  • 1 Votes
    5 Posts
    35 Views

    The IPs that are showing as LAN that should be ISP are 10.21.0.1, 10.5.0.1, and 10.101.1.34.

  • 0 Votes
    4 Posts
    165 Views

    Hi,

    When the agent first comes up, it may want to update its firmware so it would go through a several minutes long process of starting, checking, downloading the new firmware if needed, restarting, checking for new files as needed.

    If any of this was interrupted, it could lead to a problem, especially if this happened while it was writing its firmware.

    At one point, you saw the led flashing quickly then it settled into a slow flash which means that at that point, the slow flashing indicates it is now communicating with our network.

    I can see that it's seeing events and logging them.
    image.png

    I do see it going Inactive over and over again however and since I only see one outage, this means to me that it is unable to reach the Internet for x number of seconds on a regular basis.
    Inactive only happens if it has not checked in with our network for around 29 seconds or so.

    So it seems that it's up and running now and activated so please let us know if there are any other issues.

  • 0 Votes
    8 Posts
    349 Views

    @mshafrin

    I am assuming that your firewall is also your default gateway, if not then what follows could be incorrect.

    If I take a look at the hops recorded by all 3 SW agents (not only the one you mentioned) and the only HW agent, you will see that only the HW agent is having the first hop pointing to 192.168.1.1, the other ones go directly to an external IP without passing thru the firewall/gateway.

    So on one side either the Windows agents or the firewall is masking the direct hops or they are connected in a different way from the HW agent; I also saw that the 130435 was once connected in a different way since it had the same 192.168.1.1 that now doesnt show up again.

    In the end, what does it mean?
    If the agent cannot determine where the LAN ends and the provider begins there is no way to give you a correct report about where the outage was and IF it was a network outage or a problem related to cabling (provider's end of cabling).

    If the firewall is NOT your default gateway then it would be nice to understand a bit more about the LAN topology to help to troubleshoot it but so far I haven't seen a wrong behavior from the agents you have installed.

  • 0 Votes
    14 Posts
    522 Views

    Good to hear.

    Can you start a new post for the vendors if you don't mind, just in case someone else takes us up on the trial and will get confused in this question.

    In that post, we need a little info about how things are working and what the vendors need access to etc.