Collecting verbose logging and uploading Management Center System Diagnostics
search cancel

Collecting verbose logging and uploading Management Center System Diagnostics

book

Article ID: 265239

calendar_today

Updated On:

Products

Management Center Management Center - VA

Issue/Introduction

Depending on the issue being reported, there may be instances where verbose logging needs to be enabled and uploaded alongside the complete system diagnostics (also known as SOS diagnostic data) from Management Center (MC).

This article can serve as a guide for configuring verbose logging and uploading SOS diagnostic data from MC.

  

Environment

Management Center running supported version ( 3.3.x or 4.1.x)

 

Resolution

Set the event-log level to debug logging as follows:

From Management Center CLI:

Run "event-log view configuration" to check the current log level settings.

Execute "event-log level 7" to configure the event-log level to debug.

Enable Debug Logging via the Management Center UI (distinct from event-log debugging):

Open your browser (e.g., Chrome, Firefox, Edge) and log in to the MC UI at port 8082.

Navigate to Administration > Settings > Diagnostics.

Adjust the logging levels for the top four categories—Main, Security, Networking, and Device Management—to "Debug."

If the issue relates to a specific device, enable the Device Plugins for the corresponding device.

Save the changes and activate them.

Screenshot as an example, particularly if the issue pertains to both MC and Content Analysis:

 
Note: Once SOS diagnostic been sent, set the event-log level and UI debug levels back to the previous settings.
 
 
Upload the SOS diagnostic data soon after the  issue has been replicated.  From privilege/enable mode, run the following commands Management Center CLI. 
 
# diagnostics service-info send <service_request_number>
 
If a device on your network blocks/prevent your Management Center to upload data to the case directly,   upload SOS diagnostic data to your internal server for you to upload manually to the case.   SOS diagnostic data can be uploaded to any file server that use  FTP, SCP or HTTP protocol.
 
# diagnostics service-info send url ftp://host:port/path username <username> password <password>
 
Host and port is either resolvable and reachable hostname or IP and port of your internal file server.
 
In the previous example, username and password are the username and password to authenticate to the server. If server does not require authentication, these values are not required.
 
Note:  Management Center CLI may misinterpret any special characters in password. If scenario applies, you must quote the <password> or; simply hit enter without  providing the <password> from same line. Management Center should  prompt you to enter your password obscurely (sample below)   
 
# diagnostics service-info send url ftp://x.x.x.x/mc username ftp_user password
   Value for 'password' (<string>): ***********
   ok
#
 
Note:  Soon after running above command,  MC should initiate the compilation of SOS diagnostic data internally which would take some time.  Once compilation completed , Management Center would initiate TCP handshake for the transfer.  
 
 
For more information about the diagnostics command, refer to Management Center documentation .