@Virgo 

This has always been an 'issue' (i will not say problem, as it does not affect the operation of the network in any way), for as long as I've had the Omada setup, which is about 19 months.

The devices work perfectly, and do not reboot automatically etc. For example, currently the log says all three devices are disconnected, but they are not, I can access each device connected via the powerline adapters. I never have any network issues/dropouts.

There is a pattern to the events:

1) All three devices show connection events in the log

2) After 7 to 9 minutes, all three devices show disconnection events 

3) After approx 45 minutes, all three devices reconnect

4) etc.

To me, it looks like the controller is scanning the network each hour, when it finds the adapters and records them as connected in the logs. I suspect because they do not actually terminate or generate traffic (rather pass it through), the controller times out after 7-9 mins and logs them as disconnected.

  @Hank21 

The hibernation mode on the power line adapters is not the problem, they never hybernate because there is constant traffic over the connections, in addition to which I have power save/hybernation mode disabled on all devices.

One adapter connects to a Raspberry Pi used as an ADS-B receiver. I can connect to the web page on this device which shows a live map of all the aircraft in the area which updates every second. Even when viewing this page the powerline goes from connected to disconnected in the log.

Another adapter forms the uplink between two Omada switches and an Omada AP, so there is also constant traffic between these device.

So, as I said in my last post, I believe it's a problem with the controller 'assuming' they are disconnected because they are not network 'hosts' in the sense that they don't generate or terminate traffic, but rather pass through traffic between other hosts, and as such the controller is not recording their status correctly.

Tescophil wrote

  @Hank21 

 

The hibernation mode on the power line adapters is not the problem, they never hybernate because there is constant traffic over the connections, in addition to which I have power save/hybernation mode disabled on all devices.

 

One adapter connects to a Raspberry Pi used as an ADS-B receiver. I can connect to the web page on this device which shows a live map of all the aircraft in the area which updates every second. Even when viewing this page the powerline goes from connected to disconnected in the log.

 

Another adapter forms the uplink between two Omada switches and an Omada AP, so there is also constant traffic between these device.

 

So, as I said in my last post, I believe it's a problem with the controller 'assuming' they are disconnected because they are not network 'hosts' in the sense that they don't generate or terminate traffic, but rather pass through traffic between other hosts, and as such the controller is not recording their status correctly.

 

 

 

 

 

 

  @Tescophil Have had this problem in a small office using Powerline links .... Got rid of the powerline .... problem went away.   Do a test and send a 'keep alive' ping to one or more of the final devices, downstream of the Powerlines, every 15 to 30 seconds or so.  That will tell you if the powerlines are sleeping/

  @GaelForce 

I already know they are not sleeping/hybernating..., the only problem is with how the Omada controller software logs the device status, which is currently incorrect i.e. They are reported as disconnected, when they are in fact connected.. 90% of my event log consists of these connect/disconnect events. It's a bug, plane and simple....

Tescophil wrote

  @GaelForce 

I already know they are not sleeping/hybernating..., the only problem is with how the Omada controller software logs the device status, which is currently incorrect i.e. They are reported as disconnected, when they are in fact connected.. 90% of my event log consists of these connect/disconnect events. It's a bug, plane and simple....

  @Tescophil  NOT in the Omada controller.  It only reports what it can or cannot see so the fault lies with the Powerline links

  @GaelForce 

The power line adapters are constantly 'visible/connected' on the network, so if the Omada controller cannot 'see' the adapters, there is a problem.

Unless you a TP-Link engineer/developer I would ask that you don't make definitive statements about where the problem lies.

@Fae Can we raise a bug report for this ?

Tescophil wrote

  @GaelForce 

The power line adapters are constantly 'visible/connected' on the network, so if the Omada controller cannot 'see' the adapters, there is a problem.

 

Unless you a TP-Link engineer/developer I would ask that you don't make definitive statements about where the problem lies.

 

@Fae Can we raise a bug report for this ?

  @Tescophil The powerline units are are in place of a solid hardwired cable.  If you have a cable hardwired switch or access point on the system & operated by the controller then as long as the cable is intact then the controller can see the downstream devices.  If the cable is broken or disconnected then the controller reports that the downstream device is offline.  The controller does NOT report that the cable link is broken ... just device offline, which is precisely what the controller is supposed to do.  If your powerline devices break that connection then the controller is going to report that the downstream device is offline ... which is just what it is doing.

The controller does not know what a powerline adaptor is .... it considers it just a link (piece of cable) and if the link breaks ..... nuff said.