Business Community > WiFi > changing log level in Omada controller
< WiFi

changing log level in Omada controller

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

changing log level in Omada controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
changing log level in Omada controller
changing log level in Omada controller
2019-03-20 07:36:48 - last edited 2019-05-10 09:24:41
Model: AP500  
Hardware Version:
Firmware Version:

Hello,

 

is it possible to change the log level in Omada Controller ?

 

There are not enough informations in logs to handle issues.

Has someone an idea ?

 

Thanks a lot

  2      
 
  2      
 
#1
Options
10 Reply
Re:changing log level in Omada controller
2019-03-22 17:04:59 - last edited 2019-05-10 09:24:41

Did not see your post, but have just asked the same. Does need to be more informative logging, its very thin.

  0  
  0  
#2
Options
Re:changing log level in Omada controller
2020-04-14 01:17:33

@gabber242 

 

Hello,

 

Are you getting logs to a remote server [syslog etc] ? I am trying to setup remote logging but logs aren't showing up in Graylog [gettings logs from freenas/raspberrypi etc].

The controller [on ubuntu] is on the same subnet as the graylog server and using ports above 1024 like 1514 etc.

 

Thanks

  0  
  0  
#3
Options
Re:changing log level in Omada controller
2020-04-14 12:49:26 - last edited 2020-04-14 12:53:44

@Fizz1234, the standard port for syslog is UDP or TCP port 514, but not 1514.

 

If you want to use another port, you have to configure the syslog daemon. In UNIX/Linux rsyslog it's done this way (for UDP):

 

# provides UDP syslog reception
module(load="imudp")
input(type="imudp" port="1514")
 

This works for me (except that Omada controller uses UTC timestamps, but that's another story).

 

 

Syslog:

 

Apr 14 14:40:29 hn systemd[1]: Starting System Logging Service...
Apr 14 14:40:29 hn systemd[1]: Started System Logging Service.

Apr 14 12:43:00 - Omada[Controller] EAP225-Outdoor(AC-84-C6-XX-YY-ZZ) restarted
Apr 14 12:43:50 - Omada[Controller] EAP225-Outdoor(AC-84-C6-XX-YY-ZZ) connected to LAN
Apr 14 12:43:24 - Omada[Controller] EAP225-Outdoor(AC-84-C6-XX-YY-ZZ) changed LAN IP and mask to 192.168.7.219/255.255.255.0
 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#4
Options
Re:changing log level in Omada controller
2020-04-14 14:55:05

@R1D2 

Thanks.

 

I'm using graylog, so i tried both ports (had to create firewall rules to nat 514 to 1514 for the graylog listener) but still the logs never never show up.

 

I will keep digging, may be with some luck this works.

  0  
  0  
#5
Options
Re:changing log level in Omada controller
2020-04-14 21:35:39

@Fizz1234, could be firewall settings. Does your server have a route back to the host running Omada controller? Modern systems often require this to prevent spoofing. Check with netcat or wireshark whether UDP packages are forwarded or dropped by the firewall after reception but before reaching the syslog daemon.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#6
Options
Re:changing log level in Omada controller
2020-04-14 22:08:45

@R1D2 

Thanks for the suggestion.

 

Will take a look today and update you folks.

  0  
  0  
#7
Options
Re:changing log level in Omada controller
2020-04-14 22:10:31
While i have you here, can i just run the omada controller install script again from the official ziptar download to update my Linux omada controller? Do i need to stop the controller before updating?
  0  
  0  
#8
Options
Re:changing log level in Omada controller
2020-04-14 23:31:10 - last edited 2020-04-14 23:32:42

@Fizz1234, I don't use the official version, but AFAIK you have to stop, uninstall and re-install Omada controller if running on Linux.

I prefer my deb-package which does all this automatically, that's why I made the community version.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#9
Options
Re:changing log level in Omada controller
2020-10-30 14:30:38 - last edited 2020-10-30 14:34:50

Recently I've tested Zyxel Nebula SDN and I'm actually an Aruba engineer.

 

I'd like to return to the subject - lack of logging in Omada SDN.

 

I'd love to see in Events:
1. Initial signal strength client connected with (not just Channel).
As currently there's no way to troubleshoot specific wireless client retrospectively.

 

2. TX/RX Retries and signal graphs per client (not just per AP), as Aruba Instant has.

Optionally, just TX/RX Retries entries in Client tab.


3. Roaming events (and descision reason = why?) between APs and Band Steering within single AP.
For now I just see client is at 5Ghz channel and, vois-la, next minute it is on 2.4Ghz

 

4. Disconnect reason (there's bunch of codes for that in 802.11).

 

 

  1  
  1  
#10
Options
Re:changing log level in Omada controller
2020-11-06 13:51:50

@R1D2 

 

Where can I found your community version ? Does it run on Ubuntu ? I guess it does since it's a deb package.

 

Do you intend to keep it for the upcoming releases ?

 

Sorry for so many questions  

  0  
  0  
#11
Options

Information

Helpful: 2

Views: 5086

Replies: 10

Related Articles
 Omada 3.2.14 - Change log level
650 0
Omada Controller Log/Event/Client is not working (no entry at all)
3023 0
How to log in to controller locally
2335 0
 Again changing functionality in Omada Controller and new ER8411
680 0
 How to log into a gateway from the ISP but "managed by omada controller"?
3567 0
 Insufficient detail OMADA Cloud Controller log
641 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.