Hello, guys!
Welcome to our community!
This post describes how to collect logs, including SMC2.0, MCU series, SC, TE&TX&DP, RP series, and RSE6500. When the issue occurs, the log is needed to collect and analyze. Now, please see below:
SMC2.0
Based on recorded objects, logs are classified into four types: operation logs, run logs, security logs, and user logs. Specifically, logs include system logs, device operation logs (not only for MCU, recording & streaming engine, SC, conference site, corporate directory server, and integrated NMS), conference log (both ongoing conference and historical conference logs), and user logs. Here MCU is short for multipoint control unit and CS for Switch Center.
View logs on the SMC2.0 web interface
Log in to the SMC2.0 web interface.
Choose System > Logs.
All logs are displayed.
Export logs on the SMC2.0 web interface
Click a tab and then Export. In the Export dialog box that is displayed, set Start date and End date and click Export.
When logs are full
Restrictions on the size of logs in the SQL Server database
The number of logs stored in the SQL Server database is checked in real time. If the number of logs reached 1.5 million, the latest 1 million logs are saved by default and the rest are backed up. By default, backup log files are stored in the installation path \SMC2.0\Bin\LogFiles4SMC\LogFiles4Backup\DeviceNlog{yyyyMMdd}.sdf. When the size of the backup log files reaches 10 GB, the system deletes the earliest backup log file to ensure that the size of the backup log files is smaller than 10 GB. If the system fails to delete a backup log file due to an exception, the alarm "The automatic log space management function is abnormal. Delete unnecessary backup log files." is generated. If this occurs, you need to manually delete the backup log file.
Restrictions on the size of debug logs in the memory
By default, the memory stores a maximum of 1 million logs within 24 hours. When the number of logs stored in the memory reaches the maximum or the storage duration for some logs reaches 24 hours, the earliest logs are deleted from the memory.
Restrictions on log data cached in the local SQL CE
The cached log data are stored in the installation path \SMC2.0\Bin\LogFiles4SMC\LogFiles4LocalDB\LogData4SmcLocalDBV5R2.sdf. By default, the SQL CE reserves 1 GB space for storing logs. The space is sufficient because the SQL Server database may not disconnect for a long time. When the disconnection time is long, service operations are invalid, and no logs will be generated.
SC
Log commands include the traceon command and commands for exporting and checking logs.
traceon command
Available on the command-line interface (CLI) in SSH mode
Function: used to enable logging so the SC can display log information on the CLI in real time
Format: traceon module module level level
The value options of module are ALL, BUSINESS, ACCESS, MEDIA, H323, SIP, BACKUP, and H323_STACK.
The value options of level are ERROR, WARN, INFO, and DEBUG.
Command for exporting logs
This command is provided by third-party (SMC) HTTPS interfaces.
Filter criteria include the logging start and end time and log category.
By default, logs are sorted in ascending order by time when they are exported.
Command for checking logs
This command is provided by third-party (SMC) HTTPS interfaces.
Filter criteria include the logging start and end time, log category, and log level.
By default, logs are sorted in ascending order by time when they are displayed.
MCU
Log analysis helps identify and solve issues.
MCU logs are classified into operation, debugging, system, and alarm logs, indicated by o, d, s and a respectively. Exported log files are in DAT format.
The following uses the log-20120919-231206-000o-slot1.dat file as an example.
log indicates that this file is a log file.
20120919 indicates the date when the log file is generated.
231206 indicates the time when the log file is generated.
000o indicates that the log is an operation log.
slot1 indicates that the log is about board slot 1.
Procedure
Log in to the MCU web interface.
Choose Settings > Maintenance.
Click the Export tab.
Click Export Logs.
RSE6500
Exporting Log Files Through the RSE Web Page
Open the web browser, enter the RSE IP address in the address box, and press Enter. On the login page that is displayed, enter the user name and password (the default user name and password are admin and Change_Me respectively).
If it is your first login, you are prompted to change the password before login.
Choose System > System Settings > Export > Log File. On the page for exporting log files, select log files to be exported and click Export Log.
The log files are exported to your local PC.
Exporting Log Files Through Command Lines (in Telnet or SSH Mode)
Con the FTP server by referring to the HUAWEI RSE6500 V100R001C00 Upgrade Guide.
If the FTP server has been configured, skip this step.
Open the CLI using SSH or Telnet, and enter the user name and password. The default user name and password are admin and Change_Me respectively. You are advised to change the password upon your first login.
Run the system-view ftp-server command to con the IP address of the FTP server.
RSE6500>system-view ftp-server
ftp server ip addr{ipv4/v6 address}[192.168.1.1]:192.168.26.3
ftp server port{1~65535}[21]:21
ftp server user name{string, min:1 max:256}[update]:rse
ftp server password{string, min:1 max:256}[******]:***
set config success!Run the upgrade export command, select 5 on the CLI for exporting log files, and press Enter.
The log files are exported into the root directory of the FTP server.
RSE6500>upgrade export
ftp server addr :192.168.26.3
ftp server port :21
ftp server username :rse
ftp server password :******
Export type:
4: config
5: log
11: edr
12: rse_location.zip(one key collect)
Please select type:5
FileName ProgressType ProgressPercent RSE6500_log.zip packet SUCCESS RSE6500_log.zip upload SUCCESS
export success!
TE&TX&DP
Your endpoint can store a maximum of 10000 log records. When the memory for recording logs is full, new logs can still be recorded by replacing the oldest one.
1. Choose Maintenance > Logs. On the Logs page, specify one or more of the following criteria to query logs:
Time: when the log is created
Log level: Information, Warning, Error, or All levels
Log type: Main control, WEB, UI, BSP, Audio, Video, Protocol, or All
2. Click Query.
RP series
Viewing Logs of the Web Interface
Logs of the web interface record all non-query events during the RP operation, including user activities and commands. The logs help you maintain the system, locate faults, and perform auditing tasks.
Log in to the web interface and choose Maintenance > Logs.
On the Logs page, click Export.
Click Save in the displayed dialog box.
Choose the folder to save the logs and click Save.
Open the exported logs.
Viewing Logs of the Remote Control UI
On the remote control UI, choose Advanced > Diagnosis > Logs.
View detailed information about logs or search for your desired logs.
Viewing Logs of the Touch Panel UI
All events that occur on the touch panel, including settings and modifications (for example, personalized settings only for the touch panel, such as conference, language, and version settings), connection results, and software installation, are recorded into logs. You can view these logs on the touch panel. You can also download the trace log file of the touch panel from the codecs web interface. The file records detailed touch panel logs, such as the information about interaction between the codecs and the touch panel and records of putting the touch panel in sleep mode and waking it up. These logs help you maintain and troubleshoot the touch panel as well as performing audits.
View logs on the touch panel.
Choose 
> Settings > Advanced Settings > Logs.
Download logs from the codecs web interface.
Choose System Settings > Installation and click Download logs of touch panel. Then follow onscreen instructions to save the log file to your computer.
Relation topic: The methods for collecting UC component logs
That is all, thanks for reading.
