Business Community > WiFi > Generating Wifi Network Usage Reports -- OC200?
< WiFi

Generating Wifi Network Usage Reports -- OC200?

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

Generating Wifi Network Usage Reports -- OC200?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Generating Wifi Network Usage Reports -- OC200?
Generating Wifi Network Usage Reports -- OC200?
2020-04-13 14:04:58
Model: OC200  
Hardware Version: V1
Firmware Version: 1.2.1 Build 20191126 Rel.59455 3.2.5

I was browsing the specs for the new Deco X60 Mesh system, and I noticed one of the "features" was monthly network usage reports.  I really like the OC200 but the default statistics views are rather limiting.

 

I would love to be able to setup automatic usage reports (daily, weekly, monthly) that generate an HTML or PDF report (ideally which are pro-actively emailed to me on a fixed schedule).

 

Or some additional ways to visualized and slice up the data in the OC200 dashboard.  I haven't tried to SSH or other to the OC200, I assume it is just a small linux box running the controller / logging the data.

 

Is it possible to download the raw data (or query the DB it is in) so I can generate my own reports?

 

Thanks,

Jonathan

  0      
 
  0      
 
#1
Options
5 Reply
Re:Generating Wifi Network Usage Reports -- OC200?
2020-04-13 14:51:14

Hmmm,

 

Trying to SSH to the OC200.  I've enabled "SSH Login" and restarted the OC200.  I've also tried enabling "Layer 3 Accessibility" although this should not be needed as my SSH clinet is on the same local subnet.

 

OC200 is 192.168.1.200

SSH Client is 192.168.1.221

 

I've tried Win10 command line ssh (e.g. ssh 192.168.1.200) and Putty.  In both cases I get connection refused.  But I can ping the OC200 just fine.

 

C:\>ssh 192.168.1.200
ssh: connect to host 192.168.1.200 port 22: Connection refused

 

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=4ms TTL=64
Reply from 192.168.1.200: bytes=32 time=4ms TTL=64
Reply from 192.168.1.200: bytes=32 time=6ms TTL=64
Reply from 192.168.1.200: bytes=32 time=8ms TTL=64

 

I do not have a management VLAN enabled.  My SSH client is a wireless STA hosed by one of the connected EAP225's (not that this should matter).

 

Suggestions?

 

Thanks,

Jonathan

  0  
  0  
#2
Options
Re:Generating Wifi Network Usage Reports -- OC200?
2020-04-13 16:04:45 - last edited 2020-04-13 16:07:30

@JSchnee21, the SSH setting refers to EAPs, not to the OC200. If you enable »SSH Login«, you can connect to EAPs using ssh. Same is true for Mgmt VLAN: it is related to EAPs only, not to the OC200 itself.

 

In order to query the mongod database for raw data you would need to run Omada SW controller.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#3
Options
Re:Generating Wifi Network Usage Reports -- OC200?
2020-04-13 16:22:14

Ahhh,

 

That's why it's not working -- that's unfortunate.  I was also wondering what the second Ethernet port is for (that prompted me to pull the manual)

 

I've also figured out how to at least display stats for 30 days (vs 24 hours) at a time using the OC200 web interface -- (RTFM dummy -- me)

 

-Jonathan

  0  
  0  
#4
Options
Re:Generating Wifi Network Usage Reports -- OC200?
2020-04-13 16:56:52 - last edited 2020-04-13 16:57:43

 

JSchnee21 wrote

I was also wondering what the second Ethernet port is for (that prompted me to pull the manual)

 

The second port of OC200 is very useful if you use a Mgmt VLAN and want to adopt a new EAP (powered through its PoE adapter) which has not yet been configured to use the Mgmt VLAN. It's also helpful for plugging in a service laptop on customer's sites for configuration.

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#5
Options
Re:Generating Wifi Network Usage Reports -- OC200?
2020-12-25 00:44:10

@R1D2 

 

Merry Christmas and a Happy and healthy new year. Sorry to pick up on this old thread.

 

I am in possession of Qty 2 of OC300 and what I had seen few days ago was that both ports were bridged. In that case, how is one port good to talk to a new out of box AP on untagged management vlan and second on the production tagged Management VLAN?

 

Maybe you had meant that since the switch ports that  connect the production APs have all vlans tagged including the management vlan (after AP has been enrolled and its management vlan changed to tagged) and then any new AP can be connected to the controller port (which is always untagged). But then same can be done with a spare port on POE switch(es) with it set for native  vlan to be the management vlan and user vlans to be tagged (or just an untagged management vlan only).

 

I like to connect both ports to two switches in the core network (like a resilient stack of two non-POE core switches) with either cross-stack ports set up in a active / backup LAG or simply two untagged management vlan ports with STP to do its magic (or maybe set one port to have high STP port cost).

 

Thanks

 

 

 

 

 

 

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 7

Replies: 0

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.