For starting the log, simply set logging level and click “Start new log”.
Then click “Stop logging” and “Download log” to download captured log to your PC.
This logging will run on VCS (operation on WebGUI to signal logging process to VCS), therefore you may close Web session and return back later to stop/download diagnostic log (not like netlog command where you had to have live SSH/Console session while logging).
The netlog command was an easy way to see live whats going on without having to wait, especially
if we were talking about sip-tls connections or of you wanted to check realtime it was _very_ helpful.
That is now gone. (I wonder if there is a temporary file on the vcs which could be grep´ed?)
With the right filters you could limit the output so you could just see what you needed to not get flooded.
That was perfekt!
I must say I am quite unhappy that the CLI - like netlog, like lacking xconf info for the b2bua, ... or also part of the root shell like lacking scp or ssh commands get removed/crippled, I think thats a bad direction - More power to the CLI!
the imp part is the new process is easy for TAC as well as customer to collect logs. Being a TAC engineer its easy to collect the logs with GUI rathern than going to CLI and running the commands and do the capture.Also its easier to explain the customer to collect the logs and send to TAC.
however i think seeing in real time also in the CLI captures, you will see very minimal information as the window scrolls so fast and you probably would be able to see couple of messages only.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.