Devices disconnecting per event logs
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 |
|||
Dec 18, 2023 01:18:01 pm |
Dec 18, 2023 01:23:09 pm |
|||
Dec 18, 2023 12:55:06 pm |
Dec 18, 2023 01:00:32 pm |
|||
Dec 18, 2023 12:43:53 pm |
Dec 18, 2023 12:48:57 pm |
|||
Dec 18, 2023 12:09:46 pm |
Dec 18, 2023 12:15:17 pm |
|||
Dec 18, 2023 11:55:06 am |
Dec 18, 2023 12:00:11 pm |
|||
Dec 18, 2023 11:35:36 am |
Dec 18, 2023 11:40:34 am |
|||
Dec 18, 2023 10:55:03 am |
Dec 18, 2023 11:06:53 am |
|||
Dec 18, 2023 10:27:20 am |
Dec 18, 2023 10:32:13 am |
|||
Dec 18, 2023 10:04:16 am |
Dec 18, 2023 10:11:06 am |
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!