Powerline adaptor connection events in the logs

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Powerline adaptor connection events in the logs

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Powerline adaptor connection events in the logs
Powerline adaptor connection events in the logs
2022-05-31 10:19:50 - last edited 2022-06-02 08:53:54
Model: OC200  
Hardware Version: V1
Firmware Version: 1.15.2 Build 20220323 Rel.60717

As part of my network I have 3x TP-LINK AV1000 (TL-PA717) powerline adapters, used where I cannot get Ethernet cable where I need it. These work perfectly, however, the logs on mu OC200 controller are full of these events:

 

Constant connect/disconnect events for all the adapters.

 

One of the adapters connects to a Raspberry PI which is active 24/7, and the other forms the uplink/downlink between two JetStream Omada switches, which is also active 24/7.

 

All this is doing is filling up the logs with unnecessary (and incorrect) events, making it more difficult to pick out 'real' information. This must just be an oversight in the software somewhere. These devices are unusual as they have no IP address/hostname and apparently pass no traffic, it would help if they were handled more gracefully by the system.

 

So, can we please show the correct connection status of these adapters in the logs, and get rid of all the incorrect connect/disconnect events ?

 

Phil.

 

 

  0      
  0      
#1
Options
11 Reply
Re:Powerline adaptor connection events in the logs
2022-06-01 10:03:53

  @Tescophil 

 

Looking at your screenshot it doesn't look like this disconnection and reconnection is happening very often, since roughly when did this problem start?
Is the actual powerline device working properly? Is there something like a reboot schedule set up?


Were there any changes to the settings before or after the log was generated?
Is it possible that the physical connection is not making good contact?


You can observe the problem for a while and see if it recurs consistently.

 

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Powerline adaptor connection events in the logs
2022-06-01 11:56:34

  @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.

 

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 11:46:41  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 11:46:41  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 11:46:41  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:9m connected, traffic: 0Bytes).

Jun 01, 2022 10:58:04  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 10:56:34  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 10:55:34  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 10:43:39  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 10:43:39  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 10:43:39  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 09:56:34  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 09:55:34  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 09:55:04  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 09:42:41  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 09:42:41  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 09:42:41  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:9m connected, traffic: 0Bytes).

Jun 01, 2022 08:55:34  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 08:55:04  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 08:54:34  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 08:41:45  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 08:41:45  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 08:41:45  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 07:54:04  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 07:53:04  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 07:53:04  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 07:40:49  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 07:40:49  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 07:40:49  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 06:52:34  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 06:52:34  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 06:52:04  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 06:39:49  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 06:39:49  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 06:39:49  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:9m connected, traffic: 0Bytes).

Jun 01, 2022 05:52:33  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:8m connected, traffic: 0Bytes).

Jun 01, 2022 05:51:33  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 05:50:33  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 05:38:55  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 05:38:55  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 05:38:55  am

Powerline 3 was disconnected from network "Internal" on SW 1 - Garage(connected time:9m connected, traffic: 0Bytes).

Jun 01, 2022 04:51:33  am

Powerline 2 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 04:50:03  am

Powerline 1 was disconnected from network "Internal" on SW 1 - Garage(connected time:7m connected, traffic: 0Bytes).

Jun 01, 2022 04:49:33  am

Powerline 1 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 04:39:04  am

Powerline 2 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 04:39:04  am

Powerline 3 is connected to SW 1 - Garage on Internal network.

Jun 01, 2022 04:39:04  am

 

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.

 

 

  0  
  0  
#3
Options
Re:Powerline adaptor connection events in the logs
2022-06-02 07:55:16 - last edited 2022-06-02 08:53:54

Dear @Tescophil ,

 

Tescophil wrote

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.

 

Your guess is right. The problem is caused by the Powerline adapter's hibernation mechanism.


Powerline products have an automatic hibernation mode, when the wired connected client if the network cable is disconnected or wirelessly connected client no traffic through the PLC device (for example, your wired connected computer went into hibernation), after more than a few minutes, the powerline devices will automatically enter hibernation mode.

 

In this case, powerline adapters will not interact with the front device, and will not send packets to the gateway.

The controller will naturally assume that this device is disconnected.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  1  
  1  
#4
Options
Re:Powerline adaptor connection events in the logs
2022-06-02 08:53:43 - last edited 2022-06-02 08:54:55

  @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.

 

 

 

 

 

 

  0  
  0  
#5
Options
Re:Powerline adaptor connection events in the logs
2022-06-02 12:22:13

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/

  1  
  1  
#6
Options
Re:Powerline adaptor connection events in the logs
2022-06-02 13:23:15

  @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....

  0  
  0  
#7
Options
Re:Powerline adaptor connection events in the logs
2022-06-02 18:01:39

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

  0  
  0  
#8
Options
Re:Powerline adaptor connection events in the logs
2022-06-03 04:51:57

  @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 ?

  0  
  0  
#9
Options
Re:Powerline adaptor connection events in the logs
2022-06-03 08:11:20

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.

  0  
  0  
#10
Options
Re:Powerline adaptor connection events in the logs
2022-06-03 08:52:51

  @Tescophil 

literally, it's not considered as a bug. just like what the hank said. hibernation. if not traffic is passing, it goes to sleep and cut the connection. same thing happens to whateveer the wireless/wired device. 

my cell, when i don't use that, it'll cut the power to save battery. or it will drain so fast and dead in a few hours. 

it cannot be regarded as a bug. you get bothered by this, uncheck the notification for disconnection/connection. sometimes, it does not matter that much. it is not very helpful log and takes up your log sys. 

ScReW yOu gUyS. I aM GOinG hoMe. —————————————————————— For heaven's sake, can you write and describe your issue based on plain fact, common logic and a methodologic approach? Appreciate it.
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 1304

Replies: 11

Related Articles