Business Community > Controllers > Remote logging Omada controller not include controller name
< Controllers

Remote logging Omada controller not include controller name

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

Remote logging Omada controller not include controller name

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Remote logging Omada controller not include controller name
Remote logging Omada controller not include controller name
2021-10-26 08:31:43
Model: OC200  
Hardware Version: V1
Firmware Version: 4.4.6

I configure controller to send remote logging to my server. However I have multiple OC200s , I can not know which logs sent from which controller because they all have the same information and the source is blank.

Do I need to configure any thing else ?

  0      
 
  0      
 
#1
Options
1 Reply
Re:Remote logging Omada controller not include controller name
2022-01-16 17:41:42

@3HIT logging is a BIG issue when considering TP-Link Hard/Software, it is mostly lacking detail, sometimes even whole events are "missed". So the fact you get a message at all should be considered a win, detail as to the who, why, where (ok...they got when) is a big issue TP-Link need to fix and quick, because this will cost them, people will go back to i.e. Ubi or Cisco (if you have the $$$)

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 582

Replies: 1

About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.