10-22-2018 11:13 AM
If you SSH into the AC-PRO you could view what it's reporting to the controller by typing:
From there you will want to look up the hostname or MAC address of the client(s) connected to see if there is any information reported for those. It will probably take some digging. I'm not too familiar with what it can and can't acknowledge on that port. If you see information for the particular wired client on that port I suppose it would just be down to the controller to know that information from parsing the inform and placing it in the topology.
10-22-2018 11:41 AM
Adam, thanks again for the reply!
I ran the mca-dump command. I found reference to the MAC in the section below. I found no references to the IP address or to the machine name. I have attached the complete output of mca-dump for your reference.
I agree with you. It does seem there is information in this command available about what is happening on the secondary port, and it is likely something with the controller not parsing it properly.
10-25-2018 01:26 PM - edited 10-25-2018 01:28 PM
No, my USG definitely tracks LAN clients usage.
I can view their statistics and deep packet inspection.
Switch not required.
10-25-2018 01:29 PM
Is this something which needs to be enabled @lucky644?
As you can see, no activity:
Without a Switch it does show USG at port (where USG the alias is of my .. USG)
10-25-2018 01:32 PM
"Okay, Ubiquiti wins. I replaced all my managed Dell switches with new UBNT gear. I now have Activity Up/Down data for all my connected devices, with one exception. None of my virtual machines are showing any data. The ESX server is physically connected to a US-48 switch, and the VMs are connected to a 'virtual switch' within ESX. Furthermore, another test machine is running on VMWare Workstation and it is not showing any activity either (network set to 'bridged' which emulates a physical connection).
Conclusion: UBNT has done something to stop tracking the up/down activity of machines that are not connected to UBNT gear. I am wondering if this activity tracking was at one time done through the USG, and they decided to have it done through their switch gear instead. "
@lucky644- To me this means you need a unifi switch to make it work. Also, when I didn't have a unifi switch I saw no stats and when I bought the 24 port 250w, all stats came into the controller then. So I think you need a UniFi switch.
10-25-2018 01:32 PM
Your image doesn't show up.
I don't think anything specific needs to be enabled, other than DPI.
Here are a couple of screenshots showing a LAN device.
As you can see, this wired client, only connected to a USG via a Linksys switch, definitely tracks usage.
It just doesn't show up on the 'devices' screen dashboard.
10-25-2018 01:34 PM - edited 10-25-2018 01:36 PM
I think the member is trying to see activity on the clients page. Not the DPI stats. I know that works with just the USG
I think this is what he is referrring too.
10-25-2018 01:37 PM
10-25-2018 01:41 PM
10-25-2018 01:47 PM - edited 10-25-2018 01:47 PM
@lucky644Exactly! This information used to be there when I ran a bunch of old Dell 6200 switches and a mix small consumer switches. A few releases back the information disappeared. The Dell switches were well past EOL, so I decided to replace with Ubnt switches. That brought the functionality back.
If I had to take a *guess*.... The 'old' way showed north-south traffic going through the WAN on the USG. Somewhere along the line, the decision was made to instead show east-west traffic across the LAN through the UBNT switches.
Perhaps the answer involves a much broader change.... Do we want this traffic to report ingress/egress traffic from a given device (ie: how much Internet bandwidth is it consuming)? Or do we want this traffic to report activity on the network port, inclusive of internal & external bound traffic? Of course my answer is, 'I want to see both'.
10-25-2018 01:48 PM
Also, I am just speculating as I am not a staff member or on the board.
Its also an Apple thing to do but a lot of companies are going away from 3rd party integration cause it causes so many issues. Its much easier to program when its all your own stuff. Hence why Apples ecosystem is terrible and getting worse. (that stupid speaker thing they make)
Again, they should take the time to figure it out but time is money. Also, this makes people go out and by more UniFi items...which means more money for the company. They are not completely stupid.
10-25-2018 01:50 PM
@verisarioc "Again, they should take the time to figure it out but time is money. Also, this makes people go out and by more UniFi items...which means more money for the company. They are not completely stupid."
Not if it causes people to leave the ecosystem for 'compatibility' reasons.
Also, a good way to lose customer good-will for anti-competitive business practices.