Powerline adaptor connection events in the logs
Powerline adaptor connection events in the logs
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
OK, I don't know if your are just not taking the time to read my posts, or just ignoring my description, so I will reiterate:
There is CONSTANT TRAFFIC across all three powerline devices, they are not going to sleep, hybernating or going into low power mode. (Hint: I also have power saving mode DISABLED on all devices)
NO upstream or downstream hosts connected to the powerline devices are being disconnected.
Its blindingly obvious from the logs that the Omada controller scans the network every 60 minutes, discovers all three devices, logs them as connected, then 8 mins later logs them as disconnected, showing traffic of 0 bytes.
I believe one of the ways the controller maintains the connection status of every device on the network is by monitoring the data transmitted/received from each host device. Since the powerline adapters are not true network hosts and simply pass through traffic from other hosts, the controller, after at timeout period, ASSUMES they are disconnected and INCORRECTLY records this disconnection event in the log. (Hint: They are NOT DISCONNECTED at this point)
The way the controller handles these adapters isn't right, it's generating incorrect information in the logs and needs fixing.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1248
Replies: 11
Voters 0
No one has voted for it yet.