Information and Support

Definitely interesting.
I will be trying between tomorrow and Friday to get in touch with you directly using the chat to see if I can test few things I have in mind.
If this week is not possible then I have to ask you to postpone to the week of February 10, since I will be traveling next week

I am definitely interested in troubleshooting this as you came up with the conclusion that the MT3000 is somehow "WeLink intolerant" (joking of course) since there must be something which is triggering a different behavior.

Just for the sake of info the MT300 can only reach a 100Mbit connection while the MT3000 is able to go beyond that value till the nominal 2.5GB

Let me investigate first since that host must be available always

It seems you were able finally to assign it to the network 69
Would you share what solved it ?

I am trying to chat with you here in the forum, can you see it ?

I am seeing an inactive now so i bet you are doing so but cannot see it coming up online i.e. from that port the agent doesn't have the possibility to contact the DHCP server and/or have access to internet

@recalc
I keep seeing micro disconnections (those inactives you are receiving) which are not related to outages.

Even if they are lasting few seconds and are not more than 3 per day, they still are there and are not internet outages

OK, at least an explanation of why I was seeing it online :-)

I am assuming that to move your agent from one port to another port you are powering it off and once connected powering it on again, right ?

If you are referring to agent 131196, I do see it active and working properly.
Can you please explain a bit more what is wrong with moving it to a new network?

@recalc
I will continue to monitor your environment thru the agents and let you know

The 3 agents are recording a similar situation on Jan 13 at around 13:33 Chicago time but at the same time are not recording any type of outage.

Two different technologies (Windows, Openwrt) and three different versions (MT300 and MT3000 even if they both are openwrt are different in binaries) but they all:

• cannot identify an outage
• are monitoring inactives
• they disagree in some minor timing, which can be related to the way the three agents are connected to the LAN

So next question is: is it possible, without any specific detail, understand if all three agents are connected the same way within the LAN (different VLANs, directly connected to the router or thru a switch, different rules in the firewall)

A simple hand drawn picture is more than enough, as I said no company detail is needed, jsut trying to see where the problem is originated and why they behave in such a way.

Agent 131236

Agent 131232

Agent 129878

Hi,

I am trying to compare different behaviors within the same LAN and to do that I am asking if it would be possible to have all 3 agents 131236 (wash geek), 131232 (wash 2.5) and 129878 (wash) up and running.

For the moment I can say that both 131236 and 131232 are behaving in a similar way: i.e. they become inactive but NO outage.
Usually this means the problem has to be located within the LAN (your network, firewall or switching system) and not on the WAN (the ISP provider) but it is not always so crystal clear.

In short some data stops from being collected by the agent when it doesn't have access to our servers, but there is no evident "internet outage" recorded: this can happen for some of the reason that were commented at the beginning of this thread (cable, signal, etc.).

Let me know if 129878 can be powered on.

Stephan, can you access to this forum's chat ?
I am writing there ...

Yes sure

10am EST tomorrow could be ok for you ?

Sure, just let me know a convenient time for you

Let me know when you are back tomorrow and we try to continue from here or better from the chat

Did you leave also the wired connection or just removed it ???

From here we can see that the agent is stopping the wired and activating the wireless, just wondering if something else is happening at your site.
I thought the wireless provider was different from the wired, but just my assumption