Business Community > All Threads > Devices disconnecting per event logs
< All Threads

Devices disconnecting per event logs

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

Devices disconnecting per event logs

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Devices disconnecting per event logs
Devices disconnecting per event logs
2023-12-18 22:22:07
Model: Omada Software Controller (Linux)  
Hardware Version: V1
Firmware Version: 5.13.22

I keep getting messages like the following:

 

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:8m connected, traffic: 98Bytes).

 

in the event logs of the Controller.  When I go to history of the device, it looks like this:

 

Start Time End Time Duration Download Upload

Dec 18, 2023 01:52:09 pm

Dec 18, 2023 02:00:39 pm

8m 30s

0 Bytes

98 Bytes

Dec 18, 2023 01:18:01 pm

Dec 18, 2023 01:23:09 pm

5m 8s

0 Bytes

0 Bytes

Dec 18, 2023 12:55:06 pm

Dec 18, 2023 01:00:32 pm

5m 26s

0 Bytes

0 Bytes

Dec 18, 2023 12:43:53 pm

Dec 18, 2023 12:48:57 pm

5m 4s

0 Bytes

0 Bytes

Dec 18, 2023 12:09:46 pm

Dec 18, 2023 12:15:17 pm

5m 30s

0 Bytes

0 Bytes

Dec 18, 2023 11:55:06 am

Dec 18, 2023 12:00:11 pm

5m 5s

0 Bytes

0 Bytes

Dec 18, 2023 11:35:36 am

Dec 18, 2023 11:40:34 am

4m 58s

0 Bytes

0 Bytes

Dec 18, 2023 10:55:03 am

Dec 18, 2023 11:06:53 am

11m 49s

0 Bytes

0 Bytes

Dec 18, 2023 10:27:20 am

Dec 18, 2023 10:32:13 am

4m 52s

0 Bytes

0 Bytes

Dec 18, 2023 10:04:16 am

Dec 18, 2023 10:11:06 am

6m 50s

0 Bytes

0 Bytes

 

This is a VM running on a server that is wired, so it shouldn't be disconnecting, and from what I can tell, it actually isn't disconnecting (but I am not sure how to be sure on that).  

 

Also, this is just an example, all of the devices seem to be logging this (FYI: tbcmc-acts-srv is the physical server):

 

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:8m connected, traffic: 98Bytes).

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 01:28:16  pm

tbcmc-admin-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 01:28:16  pm

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 01:05:46  pm

tbcmc-admin-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 01:05:46  pm

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 12:54:16  pm

tbcmc-admin-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:4m connected, traffic: 0Bytes).

Dec 18, 2023 12:53:46  pm

tbcmc-acts-srv was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:15m connected, traffic: 2.00KB).

Dec 18, 2023 12:38:46  pm

tbcmc-staff-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 12:20:46  pm

tbcmc-admin-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 0Bytes).

Dec 18, 2023 12:20:46  pm

tbcmc-acts-srv was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:56m connected, traffic: 17.86KB).

Dec 18, 2023 12:20:16  pm

 

The VM's are on a Ubuntu 22.04 server running using virt-manager.  

 

Any ideas what could be causing it?  It does appear that 2 VM's typically disconnect at roughly the same time, but the Omada Controller is also a VM (on the same physical server), and it seems to NEVER show as disconnected.

 

Any ideas/help is appreciated!

 

  0      
 
  0      
 
#1
Options
4 Reply
Re:Devices disconnecting per event logs
2023-12-19 05:59:14

@muzicman0 

 

Is there any block for the ports on the VM? Check the physical connection if there is a loop, and any wrong ACL settings.

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Devices disconnecting per event logs
2023-12-20 16:24:30

  @Virgo I am not sure what a block on the ports on the VM means.

 

Regarding physical connections, the Omada Controller and the other VM's are all hosted on the same physical server.  There are some ACL's, but nothing that blocks communication on the same VLAN.  Only routed traffic, and in this case, the Omada Controller and the VM's are all on the same VLAN.

 

One thing I noticed is that if I am actuvely pinging the device, the Omada logs don't show a disconnect.  It's almost as if the Omada thinks it has disconnected if it's not seeing some traffic after a while.  That's just a theory though.

 

I am in the middle of writing a script that will ping from one of the VM's and log any failures to see if I can correspond the failed pings (if any occure) to the log time stamps.  My suspician is though that there will be no failures logged though.

 

 

  0  
  0  
#3
Options
Re:Devices disconnecting per event logs
2023-12-20 17:13:57

These 2 lines are in the logs now, while I had an active ping going on with 0 packet loss:

 

tbcmc-admin-radius-vm is connected to tbcmc-gateway-gw on management_vlan network.

Dec 20, 2023 09:11:40  am

tbcmc-admin-radius-vm was disconnected from network "management_vlan" on tbcmc-gateway-gw(connected time:5m connected, traffic: 64.83KB).

Dec 20, 2023 09:05:45  am

 

So it appears at least like they are not actually disconnecting.  So why the log entries?

  0  
  0  
#4
Options
Re:Devices disconnecting per event logs
2023-12-21 02:27:38

  @muzicman0 

 

Maybe a topology identified issue? I encountered a issue before that my pfsense disconnected frequently and logs like:

Pfsense is connected to Switch on VL10_MAIN network. Sep 10, 2023 09:22:50 pm
Pfsense was disconnected from network "VL200_WORK" on Switch(connected time:145h22m connected, traffic: 248564.70MB).
Sep 10, 2023 09:50:46 pm
Pfsense was disconnected from network "VL100_MGMT" on Switch(connected time:145h22m connected, traffic: 248464.19MB).

 

And it is caused by the controller's current topology recognition mechanism. Typically, the controller considers a client to be part of a vlan. When the controller calculates the topology, every time based on the list of clients reported by the switch, it will see the pfsense as a client of VLAN 1 when it sends data to VLAN 1, and the next time the pfsense sends data to VLAN 10, it will again consider it as a client of VLAN 10, which leads the controller to think that pfsense has jumped from one vlan to another, thus generating these disconnect--connect related logs.

Just striving to develop myself while helping others.
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 412

Replies: 4

Related Articles
The number of logs is up to the limit - With Three devices and less than 4000 events in a day
1230 0
Thousands of event logs after upgrade
449 0
"The number of logs is up to the limit" alert messages
8831 0
Clearing event logs does not seem to be persistent
968 0
Omada Cloud event refresh issue
619 0
Blocked device
1447 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.