FusionServer Tools V2R2 InfoCollect User Guide 22

FusionServer Tools InfoCollect
V2R2
User Guide
Issue 22
Date 2017-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Issue 22 (2017-09-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
User Guide Contents
Contents
1 Overview......................................................................................................................................... 1
1.1 Functions and Features................................................................................................................................................... 1
1.2 Specifications..................................................................................................................................................................1
1.3 Precautions for Using InfoCollect.................................................................................................................................. 4
2 Preparations.................................................................................................................................... 5
2.1 Installing InfoCollect...................................................................................................................................................... 5
2.2 Uploading the Software Package....................................................................................................................................5
3 Using InfoCollect (GUI)............................................................................................................. 10

3.1 Collecting Rack and High-Density Server Log Files................................................................................................... 10
3.1.1 Overview................................................................................................................................................................... 10
3.1.2 Collecting BMC Log Files........................................................................................................................................ 10
3.1.3 Collecting OS Log Files............................................................................................................................................ 15
3.2 Collecting E9000 Server Log Files.............................................................................................................................. 20
3.2.1 Overview................................................................................................................................................................... 20
3.2.2 Collecting Management Module Log Files............................................................................................................... 21
3.2.3 Collecting Blade Server BMC and OS Log Files......................................................................................................27
3.2.4 Collecting Switch Module Log Files.........................................................................................................................36
4 Using InfoCollect (CLI).............................................................................................................. 46

4.1 Collecting Windows Log Files..................................................................................................................................... 46
4.2 Collecting Linux Log Files...........................................................................................................................................50
5 OS Log Collection Items............................................................................................................ 56

5.1 Log Collection Items of Windows................................................................................................................................56
5.2 Log Collection Items of Linux..................................................................................................................................... 59
6 FAQs...............................................................................................................................................68
6.1 No messages Log File in a Linux Log Package........................................................................................................... 68
6.2 No OS Log file in a Windows Log Package.................................................................................................................68
6.3 Failure of Collecting BMC Log Files...........................................................................................................................68
7 Obtaining Help............................................................................................................................ 71
7.1 Making Preparations Before Contacting Huawei......................................................................................................... 71
7.2 Obtaining Help from Huawei Support Website............................................................................................................71
Issue 22 (2017-09-30) Huawei Proprietary and Confidential ii

User Guide 1 Overview
1 Overview
1.1 Functions and Features

FusionServer Tools InfoCollect (InfoCollect for short) is used to collect server log files for
locating server faults.
InfoCollect collects the following log files:

l Rack and high-density server BMC log files
l Linux OS log files of servers
l Windows OS log files of servers
l Management module log files of E9000
l Switch module log files of E9000
1.2 Specifications
l Table 1-1 lists the OSs supporting InfoCollect.
l Table 1-2 and Table 1-3 list the InfoCollect specifications.
Table 1-1 OSs supporting InfoCollect

OS Version InfoCollect (GUI) InfoCollect (CLI)
Windows Windows 7 (32- √ √

bit/64-bit)
Windows 8 (32- √ √
bit/64-bit)
Windows 10 (64-bit) √ √
Windows Server √ √
2003 (32-bit/64-bit)
2008 (32-bit/64-bit)
Issue 22 (2017-09-30) Huawei Proprietary and Confidential 1

OS Version InfoCollect (GUI) InfoCollect (CLI)
2012 (64-bit)
SUSE Linux SLES 11.1 to SLES × √

Enterprise Server 12.1 (64-bit)
(SLES)
Red Hat Enterprise RHEL 6.4 to RHEL × √

Linux (RHEL) 7.3 (64-bit)
CentOS CentOS 6.4 to × √

CentOS 7.3 (64-bit)
Ubuntu Ubuntu 14.04, × √

14.10, and 16.04
(64-bit)
NOTE
l √ indicates that an item is supported, and × indicates that an item is not supported.
l You need to run InfoCollect as an administrator on Windows 10.
Table 1-2 InfoCollect specifications for collecting OS log files
Feature Specifications
Supported products Huawei V2, V3 and V5 servers
Server Linux OS log file Supported mainstream Linux 64-bit operating systems
collection (OSs):
l RHEL 6.4 to 7.3
l SLES 11.1 to 12.1
l CentOS 6.4 to 7.3
l Ubuntu 14.04, 14.10, and 16.04
Server Windows OS log file Supported Windows OSs:

collection l Windows Server 2008 (32-bit/64-bit)
l Windows Server 2012
l Windows Server 2012 R2
Table 1-3 InfoCollect specifications for collecting BMC, management module, and switch
module log files
Supported products Huawei V2, V3 and V5 servers

BMC log file collection Supported rack and high-density servers:

l Rack servers, for example, RH2288H V3
l High-density servers, for example, XH628 V3
Management module log file Supported management modules of blade servers:

collection MM910
Switch module log file Supported switch modules of E9000 blade servers:
collection l CX110/CX111
l CX210/CX220
l CX310/CX311/CX312/CX320
l CX710
l CX910/CX911/CX912/CX913/CX915/CX916/CX920
NOTE
l To collect BMC logs of blade servers, use the E9000 management module IP address.
l FusionServer Tools-InfoCollect-V126 and later versions do not support the collection of E6000
management module logs. To collect E6000 management module logs, use FusionServer Tools-
InfoCollect-V125 and earlier versions. Select E6000 MM from the Target drop-down list box, and
enter the MM610 or MM620 IP address, administrator user name, and password, as shown in Figure
1-1.

Figure 1-1 Collecting E6000 management module logs
1.3 Precautions for Using InfoCollect

l Only qualified personnel can use this tool. To obtain the latest version, visit Support E.
l Before using InfoCollect, introduce this tool to the customer.
l Before performing any maintenance operations by using InfoCollect, obtain written
authorization from the customer. Unauthorized operations are forbidden.
l Before transmitting fault locating data out of the customer's network, obtain written
authorization from the customer.
l Use InfoCollect in accordance with the local applicable laws and regulations.
l After fault diagnosis, delete local log files.
l After fault diagnosis, delete local log files. Before using InfoCollect, you are advised to
back up key data.

User Guide 2 Preparations
2 Preparations
2.1 Installing InfoCollect

1. Download the software package.
Download the latest InfoCollect package from FusionServer Tools.
2. Verify software package integrity.
On the download page, click to obtain the digital certificate, and click to
download the software. For details about how to obtain the verification tool and method,
see Software Digital Signature (OpenPGP) Validation Tool.
3. The InfoCollect tool is free of installation and can be used directly after you decompress
the software package.
NOTICE
If InfoCollect is used on a Windows OS, the InfoCollect path cannot contain ;. Otherwise, you
cannot run InfoCollect.
2.2 Uploading the Software Package

Procedure
NOTICE
Server Linux OS log file collection: You need to upload the InfoCollect_Linux.tar.gz file to
the server Linux OS through Xftp. The path for storing the uploaded file cannot contain
spaces.
Step 1 Double-click Xshell.exe.

The Xshell client is accessed.

Step 2 Run the following command to connect to the server Linux OS:
ssh IP address of the server Linux OS
The SSH User Name window is displayed, as shown in Figure 2-1.
Figure 2-1 SSH User Name
Step 3 Enter the user name of the server Linux OS, and click OK.
The SSH User Authentication window is displayed, as shown in Figure 2-2.

Figure 2-2 SSH User Authentication
Step 4 Enter the password corresponding to the user name of the server Linux OS, and click OK.
The connection to the server Linux OS starts.
The server Linux OS is successfully connected, as shown in Figure 2-3.
Figure 2-3 Connection succeeded

Step 5 Click .
The SSH User Authentication window is displayed, as shown in Figure 2-4.
Figure 2-4 SSH User Authentication
Step 6 Enter the password in Step 4, and click OK.

The main window of Xftp is displayed.
Step 7 Find the location of the InfoCollect_Linux.tar.gz file on the local PC, and select the
uploading path on the server Linux OS (the /home directory is recommended), as shown in
Figure 2-5.
Figure 2-5 Selecting the uploading path

Step 8 Drag the InfoCollect_Linux.tar.gz file from the left pane to the right pane.
The file uploading starts. When the InfoCollect_Linux.tar.gz file is displayed in the right
pane, the file is uploaded successfully, as shown in Figure 2-6.
Figure 2-6 Uploading succeeded
NOTE
l Server Windows OS log file collection: You can use the network sharing function or a tool such as a
USB flash drive to upload the InfoCollect_Windows.zip file to the server Windows OS (drive D is
recommended).
l BMC, management module, and switch module log file collection: You only need to run the
InfoCollect.exe tool on the local console (which refers to the laptop running Windows of a service
engineer). For details about BMC log file collection, see Collecting Rack and High-Density
Server Log Files. For details about management module and switch module log file collection, see
Collecting E9000 Server Log Files.
----End

User Guide 3 Using InfoCollect (GUI)
3 Using InfoCollect (GUI)
3.1 Collecting Rack and High-Density Server Log Files
3.1.1 Overview
Run InfoCollect on a Windows PC or server and collect server BMC and OS logs. Ensure that
the IP addresses of the BMC and OS are pingable.
l Table 1-2 lists the OSs supported by this tool for log collection.
l Table 1-3 lists the rack and high-density servers supported by this tool for BMC log
collection.
l The BMC log files collected by using InfoCollect are the same as the log files collected
by running the BMC one-click collection commands. For details, see One-Click Info
Collection in the BMC help.
l For details about the OS log items that can be collected, see OS Log Collection Items.
NOTE
BMC and OS logs can be collected at the same time. The following describes how to collect them
separately.
3.1.2 Collecting BMC Log Files
Scenario
Collect BMC log files of a remote server using the local console (which refers to the laptop
running Windows of a service engineer).
Prerequisites
Conditions
l A Huawei rack or high-density server is available.
l The InfoCollect directory has sufficient available disk space for storing collected log
files.
l The target server is pinged.

Procedure
Step 1 Go to the InfoCollect_GUI folder. Figure 3-1 shows the files in the folder.
Figure 3-1 Files in the InfoCollect_GUI folder
Step 2 Double-click the InfoCollect.exe to collect log information.

The window shown in Figure 3-2 is displayed. Table 3-1 describes BMC Info parameters.
Figure 3-2 Main window of InfoCollect

Table 3-1 Parameter description

Information Parameter Description
BMC Info BMC IP BMC IP address of the target server.
User Name BMC user name of the target server. The default
value is root.
Password Password for logging in to the BMC of the target

server using the network port IP address.
SSH Port The default value is 22. It must be the same as the
SSH port number of the target server.
Step 3 Deselect OS Info, and enter the BMC IP address, user name, and password in the BMC Info
area.
The BMC log collection window is displayed, as shown in Figure 3-3.
Figure 3-3 Window for BMC log file collection

NOTE
l Set User Name to an administrator (for example, root) for collecting log files.
l By default, you need to set only the BMC IP address, user name, and password for the InfoCollect
tool. If advanced settings are required, you need to modify the SystemConfig.ini file (for
professional users) in the FusionServer Tools-InfoCollect-V125\InfoCollect_GUI\config
directory. Figure 3-4 shows the SystemConfig.ini file.
Figure 3-4 SystemConfig.ini file
Step 4 Click Start.

Log file collection starts. See Figure 3-5.

Figure 3-5 Collecting log files
NOTE
l The log collection takes several minutes.

l To stop the collection, click Stop.
After the log files are successfully collected, the message collect log successfully
is displayed, as shown in Figure 3-6.

Figure 3-6 Information indicating that log file collection is complete
Step 5 Click Log directory.

Log files are obtained.
----End
3.1.3 Collecting OS Log Files
Scenario
Collect Windows OS logs using InfoCollect.
Prerequisites
Conditions
l A Huawei rack or high-density server is available.
l PowerShell must be installed on the target OS and the PowerShell remote service must
be enabled for Windows log collection.
You can run the Enable-PSRemoting -Force command to enable the service on the
PowerShell screen. If the PowerShell remote service is disabled, you can only collect
Windows logs by using the CLI.
files.

l When Windows OS logs are to be collected, the installation directory of InfoCollect

cannot contain &[]. Otherwise, PowerShell will fail.
Procedure

The window shown in Figure 3-8 is displayed.

Step 3 Deselect BMC Info and select Windows in the OS Info area.
The Windows OS log collection window is displayed, as shown in Figure 3-9. Table 3-2
describes the parameters.
Figure 3-9 Windows OS log collection window

OS Parameter Description
Linux OS IP OS IP address of the target server.
User Name OS administrator user name of the target server.

The default value is root.
Password Password for logging in to the OS the target

server.
Windows OS IP OS IP address of the target server.

The default value is Administrator.

OS Parameter Description
Password Password for logging in to the OS the target

server.
PowerShell Port The default value is 5985. This port must be

consistent with the PowerShell remote
management port of the target server OS.
Local IP Address The default value is Auto select. The IP address

needs to be on the same network segment as that
of the target server OS.
Local User Name Domain name or user name of the local PC.
Local Password Password corresponding to the local PC user

name.
NOTE
Set User Name to an administrator (for example, root or Administrator) for collecting log files.
Step 4 Enter the OS IP address, user name, and password of the target server, and the domain name/
user name and password of the PC, as shown in Figure 3-10.
Figure 3-10 Entering information

Step 5 Click Start.

NOTE



----End
3.2 Collecting E9000 Server Log Files
3.2.1 Overview
Run InfoCollect on a Windows PC or server and collect server management module, OS, and
switch module logs. Ensure that the IP addresses of the management module, OS, and switch
module are pingable.
l Table 1-2 lists the OSs supported by this tool for log collection.
l Table 1-3 lists the servers whose management module and switch module logs can be
collected using this tool.
l The management module log files collected by using InfoCollect are the same as the log
files collected by running the one-click collection commands of the management
module. For details, see Information Collection in the management module help.
l For details about the OS log items that can be collected, see OS Log Collection Items.

l Table 3-3 lists the E9000 switch module log files that can be collected and commands
used to collect logs.
Table 3-3 Switch module log files

File Command Description
diag-info.txt display diagnostic- Display information

information diag-info.txt
diagnostic_information.zip collect diagnostic Diagnosis log file

information
log.log - Operation log
diag.log - Run log
NOTE
Management module, OS, and switch module logs can be collected at the same time. The following
describes how to collect them separately.
3.2.2 Collecting Management Module Log Files
Scenario
Collect management module log files of a remote server using the local console (which refers
to the laptop running Windows of a service engineer).
Prerequisites
Conditions
l A Huawei E9000 server is available.
files.
l Collect the log files of management modules during off-peak hours to minimize the
impact on services.
Procedure


Step 3 In the Select Device Type area, select E9000.

The E9000 server log collection window is displayed, as shown in Figure 3-15. Table 3-4
describes the parameters in the MM910 area.
Figure 3-15 E9000 log collection window

MM910 MM IP Management module IP address of the target

server.
User Name Management module user name of the target

server. The default value is root.
Password Password for logging in to the management

module of the target server using the network port
IP address.

NOTE
l Set User Name to an administrator (for example, root) for collecting log files.
l By default, you need to set only the management module IP addresses, user names, and passwords
for the InfoCollect tool. If advanced settings are required, you need to modify the SystemConfig.ini
file (for professional users) in the FusionServer Tools-InfoCollect-V125\InfoCollect_GUI\config
directory. Figure 3-16 shows the SystemConfig.ini file.
Figure 3-16 SystemConfig.ini file
Step 4 Enter the MM910 IP address, user name, and password of the target server, and click
Connect.
Connect to the management module to obtain the available slot and switch module
information, as shown in Figure 3-17.

Figure 3-17 Obtaining device information
Step 5 Select MM1 MM2 and click Start.


NOTE



----End
3.2.3 Collecting Blade Server BMC and OS Log Files
Scenario
Collect blade server BMC and OS logs using InfoCollect. A Windows OS is used as an
example.
Prerequisites
Conditions
l PowerShell must be installed on the target OS and the PowerShell remote service must
be enabled for Windows log collection.
You can run the Enable-PSRemoting -Force command to enable the service on the
PowerShell screen. If the PowerShell remote service is disabled, you can only collect
Windows logs by using the CLI.
l When Windows OS logs are to be collected, the installation directory of InfoCollect
cannot contain &[]. Otherwise, PowerShell will fail.

files.
Procedure





server.


IP address.
Connect.
information. Slot numbers of available nodes are displayed in the Select Device area as shown
in Figure 3-23.

Step 5 In the Select Device area, select the slot number of the node whose OS logs are to be
collected, as shown in Figure 3-24. Table 3-6 describes OS and Local information
parameters.

Figure 3-24 Selecting a device

OS (Linux) OS Type OS type of the target server.
IP Address OS IP address of the target server.

The default value is root.
Password Password for logging in to the OS of the target

SSH/PS Port The default value is 22. It must be the same as the
OS (Windows) OS Type OS type of the target server.
IP Address OS IP address of the target server.

The default value is Administrator.
Password Password for logging in to the OS of the target


SSH/PS Port The default value is 5985. This port must be

consistent with the PowerShell remote
management port of the target server OS.
Local Local IP Address The default value is Auto select. The IP address
information needs to be on the same network segment as that
of the target server OS.
Local User Name Domain name or user name of the local PC.
Local Password Password corresponding to the local PC user

name.
NOTE
l Set Local information parameters only when collecting Windows OS logs.

l Set User Name to an administrator (for example, root or Administrator) for collecting log files.
l You can select multiple slot numbers to collect OS and BMC logs of multiple blade servers. The
following uses Slot9 as an example.
l If the slot numbers in the Select Device area are deselected and only the slot numbers in the OS area
are selected, only blade server OS logs will be collected.
Step 6 Set OS Type to Windows, enter the OS IP address, user name, and password of the target
server and the PowerShell remote management port number, and click Local information, as
shown in Figure 3-25. In the displayed dialog box, enter the local PC domain name/user
name and password.

Figure 3-25 Entering information
NOTE
l After a slot number is selected, the row containing the OS settings of the node is selected by default
in the OS area. To delete the settings in a row, click delete.
l To copy the settings in a row to the next row, click .
Step 7 Click Start.


NOTE



----End
3.2.4 Collecting Switch Module Log Files
Scenario
Collect switch module log files of a remote server using the local console (which refers to the
laptop running Windows of a service engineer).
Prerequisites
Conditions
files.

Procedure




server.


IP address.

Connect.
information, as shown in Figure 3-31.
Step 5 Select the slot number of the switch module whose logs are to be collected, as shown in
Figure 3-32. Table 3-8 describes Config switch parameters.

Figure 3-32 Selecting a device

Config switch User Name Switch module administrator user name of the
target server. The default value is admin.
Password Password for logging in to the switch module of

the target server.
IP Switch module IP address of the target server.
NetMask Switch module subnet mask of the target server.
Gateway Switch module gateway of the target server.
NOTE
Set User Name to an administrator (for example, admin) for collecting log files.
Step 6 Click Config switch.

The Config Switch dialog box is displayed, as shown in Figure 3-33.

Figure 3-33 Config Switch
Step 7 Enter the user name for whom the logs are to be collected and the corresponding password,
and click Query.
The dialog box shown in Figure 3-34 is displayed.
Figure 3-34 Dialog box
The system automatically obtains the switch module IP address, subnet mask, and gateway, as
shown in Figure 3-35.

Figure 3-35 Automatically obtaining information
NOTE
You can manually enter the new IP address and subnet mask in the Config Switch dialog box and click
Config to change the IP address and subnet mask.
Step 8 Click OK and close the Config Switch dialog box.

The switch module log collection window is displayed, as shown in Figure 3-36.

Figure 3-36 Switch module log collection window
Step 9 Click Start.


NOTE

The log file collection is successful if the message collect log successfully is
displayed. See Figure 3-38.


----End

User Guide 4 Using InfoCollect (CLI)
4 Using InfoCollect (CLI)
4.1 Collecting Windows Log Files
Scenario
Collect Windows log files of a server.
Prerequisites
Conditions
l A Huawei V2, V3 or V5 server is available.
l The InfoCollect_Windows.zip file has been uploaded to the target server.
l You have logged in to Windows as an administrator.
l You have backed up key data, and checked the CPU usage, memory usage, and available
disk space to ensure that InfoCollect is operating properly.
Procedure
Step 1 Decompress the InfoCollect_Windows.zip file, as shown in Figure 4-1.
Figure 4-1 Decompressing the InfoCollect_Windows.zip file
Step 2 Go to the FusionServer Tools-InfoCollect-V125\InfoCollect-Windows\InfoCollect-

Windows directory, as shown in Figure 4-2.

Figure 4-2 Going to the FusionServer Tools-InfoCollect-V125\InfoCollect-Windows

\InfoCollect-Windows directory
Step 3 (Optional) Modify the config.ini configuration file to specify the log files to be collected, as
shown in Figure 4-3.
Figure 4-3 config.ini configuration file
Change the value of flag to specify whether to collect a log file. InfoCollect collects all log
files by default, as shown in Figure 4-4.
Figure 4-4 Modifying the config.ini configuration file
NOTE
You are advised to check the log files to be collected. If you do not want to collect a log file, set flag to
no.
Step 4 Right-click the infoCollect.bat file in the FusionServer Tools-InfoCollect-

V125\InfoCollect-Windows\InfoCollect-Windows directory and choose Run as
administrator from the shortcut menu, as shown in Figure 4-5.

Figure 4-5 Choosing Run as administrator
The collection of Windows log files starts. Figure 4-6 shows collection process information.
NOTE
The collection process will last several minutes.
Figure 4-6 Collection process information
After log file collection is complete, the information shown in Figure 4-7 is displayed.

NOTE
l If the information shown in Figure 4-8 is displayed after log file collection is complete, manually
collect crash files to your local computer.
l Crash files are large. You need to manually collect crash files for fault diagnosis.
Figure 4-8 Crash file information
Step 5 Confirm that all log files are collected based on the content of the filelist.txt file in Figure
4-9.
You can filter the collected log files and then compress them into a package.

Figure 4-9 Content of the filelist.txt file
NOTE
You are advised to compress log files before sending them to Huawei for analysis.
----End
4.2 Collecting Linux Log Files
Scenario
Collect Linux log files of a server.

NOTICE
Do not directly decompress the InfoCollect_Linux.tar.gz tool package of the Linux version
on a Windows OS. Otherwise, the tool cannot collect logs because the lack of execution
permission.
Prerequisites
Conditions
l A Huawei V2, V3 or V5 server is available.
l The InfoCollect_Linux.tar.gz file has been uploaded to the target server.
l You have logged in to Linux as a user with an ID of 0, for example, root.
l You have backed up key data, and checked the CPU usage, memory usage, and available
disk space to ensure that InfoCollect is operating properly.
NOTE
Run the whoami and id commands on the OS. In Figure 4-10, the current user is root and its user ID is
0.
Figure 4-10 Querying user information
Procedure
Step 1 Confirm that the InfoCollect_Linux.tar.gz file has been uploaded to the server Linux OS. For
details, see Uploading the Software Package.
Step 2 Run the following command to go to the directory where the InfoCollect_Linux.tar.gz file is
located, as shown in Figure 4-11.
cd
Figure 4-11 Going to the directory where the file is located
Step 3 Run the following command to decompress the collection tool package, as shown in Figure
4-12 and Figure 4-13.
tar -zxvf InfoCollect_Linux.tar.gz

Figure 4-12 Decompressing the collection tool package
Figure 4-13 Decompressing the collection tool package
Step 4 Run the following command to go to the InfoCollect_Linux directory, as shown in Figure
4-14.
cd InfoCollect_Linux

Figure 4-14 Going to the InfoCollect_Linux directory
Step 5 Run the following command to grant the operation permission on all files in the
InfoCollect_Linux directory to the user:
chmod +x *
Step 6 (Optional) Run the following command to modify the config.ini file to specify the log files to
be collected, as shown in Figure 4-15.
Figure 4-15 Modifying the config.ini file
NOTE
You are advised to check the content of the log files to be collected. You can edit the flag column to
determine whether a log file is to be collected. yes indicates that the log file is to be collected. no
indicates that the log file is not to be collected. By default, all log files are to be collected.
Step 7 Run the following command to collect log files, as shown in Figure 4-16.
./infoCollect.sh

Figure 4-16 Executing the Linux collection script
NOTE
The collection process will last several minutes.
The log collection is successful if the message shown in Figure 4-17 is displayed.
Figure 4-17 Message indicating that the log collection is successful
NOTE
l If the information shown in Figure 4-18 is displayed after log file collection is complete, manually
collect crash files to your local computer.
l Crash files are large. Manually collect crash files for fault diagnosis if necessary.
Figure 4-18 Crash file information
Step 8 Confirm that all log files are collected based on the content of the filelist.txt file in Figure
4-19.

You can filter the collected log files and then compress them into a package.
Figure 4-19 Content of the filelist.txt file
NOTE
l You are advised to compress log files before sending them to Huawei for analysis.
l The maximum log file collection duration of InfoCollect is 20 minutes by default.
----End

User Guide 5 OS Log Collection Items
5 OS Log Collection Items
5.1 Log Collection Items of Windows

InfoCollect_Windows.zip provides the one-click log file collection function for the server
Windows OS. Table 5-1 lists the content of the log files that can be collected.
Table 5-1 Windows log files and collection commands

Module File Command Description
Common version.txt - InfoCollect version and

release time
filelist.txt - List of collected files
CPU cpuinfo.txt wmic cpu list full CPU information
Disk physicaldisk.txt wmic diskdrive list full Physical disk information
logicaldisk.csv wmic logicaldisk list full Logical disk information
volume.csv wmic volume list full Volume information
cdrom.txt wmic cdrom list full DVD drive information
diskquota.txt wmic diskquota list full New Technology File

System (NTFS) volume
management information
partition.txt wmic partition list full Partition information

es3000_v2.txt HioInfo.exe -d deviceID ES3000 V2 PCIe SSD

HioBadblock.exe -d information
deviceID
HioEcinfo.exe -d deviceID
HioLabel.exe -d deviceID
HioLog.exe -d deviceID
HioLogdump.exe -d
deviceID -n controllerID
HioRwReg.exe -d -
deviceID -s registerAddress
HioTemperature.exe -d
deviceID
es3000 v3.txt hioadm.exe info -d ES3000 V3 NVMe PCIe

device=nvme0,hioadm.exe SSD information
info
hioadm.exe info -d
device=nvme,hioadm.exe
info -
shioadm.exe info -d
device=nvme,hioadm.exe
info -a
hioadm.exe log -d
device=nvme0,hioadm.exe
info -a
Driver drivers.txt wmic sysdriver list full Names of all module

drivers
drivernodes.txt devcon.exe drivernodes * Details about all module

drivers
driverquery.csv driverquery /v Driver list, including driver

names and dates
Mainboard csproduct.csv dmidecode Product model list
baseboard.csv lspci Mainboard model list
bioslist.csv wmic bios list full BIOS information
Memory memorychip.txt /proc/meminfo DIMM information
memphysical.cs mcelog --client Maximum memory

v capacity supported by the
mainboard
devicememorya dmidecode -t memory List of device memory

ddress.txt addresses
memcache.txt free Cache list

dmachannel.txt hwdiag -t mem -d DMA channel list
pagefile.txt wmic pagefile list full Page file list
NIC ipconfig.txt ipconfig /all IP addresses and MAC

addresses of NICs
nic.txt wmic nic list full NIC list
nicconfig.txt wmic nicconfig list full NIC configuration
netlogin.txt wmic netlogin list full Network login list
netclient.txt wmic netclient list full Network client list
netprotocol.txt wmic netprotocol list full Network protocol

information
ntdomain.txt wmic ntdomain list full Server domain information
RAID sashbalog.txt sas3flash command LSI SAS2308 or LSI

controller combinations SAS3008 controller card
card log file
sasraidlog.txt storcli command LSI SAS2208 or LSI

combinations SAS3108 controller card
log file
System pciInfo.txt devcon.exe find pci * PCI device list
systeminfo.txt systeminfo System information,

including the OS version
and patch information
irq.txt wmic irq list full IRQ list
loadorder.txt wmic loadorder list full Load order list
timezone.txt wmic timezone list full Time zone list
systemslot.txt wmic systemslot list full System slot list
systemenclosure wmic systemenclosure list Chassis list

.txt full
process.txt wmic process list full Process list
osinfo.csv wmic os get OS version
computersystem wmic computersystem list Device name list

.txt full
environment.txt wmic environment list full Environment variable list
startup.txt wmic startup list full Boot service list

querystate.txt sc query state= all Information about all

services
winevt xcopy %SystemRoot% System log file

\System32\winevt
logs xcopy %SystemRoot% System log file

\Logs
WindowsUpdate copy %SystemRoot% System update log file

.log \WindowsUpdate.log
hwids.txt devcon.exe hwids * IDs of all PCI devices
classes.txt devcon.exe classes Types of all PCI devices
resources.txt devcon.exe resources * Resources of all PCI

devices
status.txt devcon.exe status * Status of all PCI devices
msinfo.txt msinfo32 /report msinfo.txt Overall view of hardware,

system components, and
software environment
dumplist.txt Dump file list on Windows Dump file list
runlog.txt Tool running records Tool running records
Log files that are copied separately -
Dump memory.dmp %SystemRoot% Complete dump file

\MEMORY.DMP
minidump %SystemRoot%\Minidump Compact dump file

\
NOTE
l The number and content of collected log files slightly vary according to the Windows version, but all
log files collected are listed in Table 5-1.
l In the es3000v2.txt of disk module, the value of deviceID is the given ES3000 V2 object, such as 0,
1; the value of controllerID is the given controller serial number, such as 1, 1; the value of
registerAddress is the specified register address, such as 0x2400, 0x2310.
l You can customize the log information to be collected by editing the config.ini file in the tool
directory. The runlog.txt file in system specifies the default log information to be collected and does
not need to be customized.
5.2 Log Collection Items of Linux

InfoCollect_Linux.tar.gz provides the one-click log file collection function for the server
Linux OS. Table 5-2 lists the content of the log files that can be collected.

Table 5-2 Linux log files and collection commands

Module Log File Command Description
Common version.txt - InfoCollect version and

release time
filelist.txt - List of collected files
BIOS version_bios.txt dmidecode -t bios BIOS version
BMC fru.txt ipmitool fru list Field replaceable unit

(FRU) information
bmc_lan.txt ipmitool lan print 1 BMC NIC information
mc_info.txt ipmitool mc info BMC version
sensor.csv ipmitool sensor list All sensor information
sdr.csv ipmitool sdr list Sensor data record (SDR)

log file
sel.csv ipmitool sel elist BMC system event log

(SEL)
version_cpld.txt ipmitool raw0x30 0x90 CPLD version

0x08 0 2 0x00 0x10
time.txt BMC time bios time OS BMC, BIOS, and OS time

time
CPU cpuinfo.txt cat /proc/cpuinfo CPU model and frequency
cpu_dmidecode. dmidecode -t processor CPU information obtained

txt by running the dmidecode
command
Disk disk_smart.txt smartctl -a /dev/sd* Self-Monitoring, Analysis

smartctl -a --device=sat and Reporting Technology
+megaraid,0 /dev/sd* (SMART) information
about all disks
smartctl -a --
device=megaraid,
0 /dev/sd*
hwdiag -t disk -s
sys_block.txt ls -l /sys/block/sd* Hard disk names
parted_disk.txt parted /dev/sda print Partition information of

physical hard disks
hwdiag_hdd.txt hwdiag -t disk -d Hard disk scores offered by

iBMA (applicable only to
an OS running iBMA)

es3000_v2.txt hio_info -d -- ES3000 V2 PCIe SSD

device=hioa,/dev/hio* information
hio_label -d --
device=hioa,/dev/hio*
hio_log -d --
hio_temperature -d --
es3000_v3.txt modinfo nvme ES3000 V3 NVMe PCIe

hioadm info -d SSD information
device=nvme0,hioadm info
hioadm info -d
device=nvme,hioadm info -
s
hioadm info -d
device=nvme,hioadm info -
a
hioadm log -d
device=nvme0,hioadm info
-a
Mainboard dmidecode.txt dmidecode Hardware information
lspci.txt lspci Peripheral Component

Interconnect (PCI) device
list
lspci -xxx -vvv -t Detailed PCI device

information
lspci -xxxx -vvv -b Bus-related PCI and

interrupt request (IRQ)
device information
NIC lspci_eth.txt lspci |grep Ethernet NIC list
ifconfig.txt ifconfig -a Configurations of all NICs
/etc/modprobe.d /etc/modprobe.d/ NIC configuration file
ethtool.txt ethtool ethX NIC settings
ethtool -i ethX
ethtool -S ethX
ethtool -g ethX
ethtool -k ethX

/etc/sysconfig/ cp /etc/sysconfig/network/* NIC configuration files on

network/* SLES
/etc/sysconfig/ cp /etc/sysconfig/network- NIC configuration files on

network- scripts/* RHEL
scripts/*
netstat.txt netstat -i -n Network port status
netstat -avn
netstat -s
netstat -rvn
mezz_info.tar.gz /bin/date collect_info/network.txt:

NIC information.
/usr/bin/uptime
mezz.log: running log of
dmidecode mezz_collect.sh.
biosdecode
lspci -tv
ifconfig -a
/sbin/ip link show
/sbin/route -n
ethtool -i ethX
ethtool ethX
ethtool -a ethX
ethtool -l ethX
ethtool -d ethX
ethtool -e ethX
ethtool -S ethX
ethtool -g ethX
ethtool -k ethX
/sbin/lspci -xxx -s
XX:XX.X
lspci -vvvv -xxx -s

XX:XX.X
/bin/netstat -nlp
/bin/netstat -nr

/bin/netstat -i
/sbin/arp -v
/usr/sbin/iptables -t
filter -nvL
x86tool -r pci/
bXX:XX.X-0xXXXXX+4-
bX
Host bus lspci_fc.txt lspci |grep Fibre Fibre Channel (FC) models
adapter
(HBA) firmware_fc.txt cat /sys/class/scsi_host/ FC HBA firmware
host*/fwrev information
driver_fc.txt cat /sys/class/scsi_host/ FC HBA driver information

host*/lpfc_drvr_version
wwpn.txt cat /sys/class/fc_host/host*/ FC HBA World Wide Port

port_name Name (WWPN)
information
Driver lsmod.txt lsmod Loaded module

information
modinfo.txt modinfo Driver information of a

specific module
Memory meminfo /proc/meminfo Memory information
mem_ecc.txt mcelog --client Memory error checking and

correcting (ECC)
information (empty by
default)
memory_dmidec dmidecode -t memory Physical memory

ode.txt information
memory_free.txt free Used and available memory

space
hwdiag_mem.txt hwdiag -t mem -d Memory diagnosis data

offered by iBMA
(applicable only to an OS
running iBMA)
RAID sashbalog.txt sas2flash LSI SAS2308 or LSI

controller SAS3008 controller card
card log file
sasraidlog.txt storcli LSI SAS2208 or LSI

SAS3108 controller card
log file

System runlog InfoCollect run log file
/var/log/secure cp /var/log/secure* Security log files
/var/log/mcelog cp /var/log/mcelog* Log files required for

locating machine check
exceptions (MCEs)
/var/log/message cp /var/log/message* General system log files
/var/log/cron /var/log/cron* Customized task log files
/var/log/boot.log /var/log/boot.log .log file that records

information about the
current startup process
/var/log/ /var/log/boot.msg .msg file that records

boot.msg information about the
current startup process
/var/log/ /var/log/boot.omsg Log file that records

boot.omsg information about the
previous startup process
/etc/syslog.conf /etc/syslog.conf Configuration file of the

syslogd process
/etc/resolv.conf /etc/resolv.conf Configuration file of the

network proxy
/etc/hosts /etc/hosts Host information
/etc/services /etc/services OS boot service

information
/etc/sysctl.conf /etc/sysctl.conf System kernel parameter

configuration file,
involving network
functions, for example,
forwarding
/etc/inittab /etc/inittab Initialization, involving

system configuration
/etc/ntp.conf /etc/ntp.conf Network Time Protocol

(NTP) configuration file
/etc/ntp/step- /etc/ntp/step-tickers NTP configuration file

tickers
/etc/ntp/ /etc/ntp/ntpservers NTP server list

ntpservers
/etc/yp.conf /etc/yp.conf ypbind configuration file
/etc/fstab /etc/fstab File system list

/proc/interrupts /proc/interrupts Number of interrupts
/proc/ /proc/filesystems Current file system list

filesystems
/etc/exports /etc/exports Network File System

(NFS) server configuration
/proc/self/maps /proc/self/maps Virtual address space of

processes
/proc/self/smaps /proc/self/smaps Memory usage of each

process
/proc/self/ /proc/self/numa_maps Memory usage of the numa

numa_maps process
/proc/iomap /proc/iomap Memory space address

segment mapping to I/O
ports
/proc/ioports /proc/ioports Distribution of I/O ports in

use
/proc/swaps /proc/swaps Swap partition information
/proc/slabinfo /proc/slabinfo Kernel information
/proc/locks /proc/locks Locked processes
/proc/modules /proc/modules All modules
/proc/mounts /proc/mounts Mounted devices
/proc/version /proc/version Kernel version
/proc/stat /proc/stat Kernel and system statistics
/proc/schedstat /proc/schedstat Kernel information about

the schedstat process
/proc/zoneinfo /proc/zoneinfo Kernel time zone

information
/proc/config.gz /proc/config.gz Configuration files of the

proc file system
/proc/kallsyms proc/kallsyms Kernel debugging files
/proc/mtrr /proc/mtrr Memory Type Range

Register (MTRR)
information
/proc/vmstat /proc/vmstat Virtual memory status
/proc/buddyinfo /proc/buddyinfo Memory fragment

information

/proc/cmdline /proc/cmdline Kernel startup CLI

information
/proc/devices /proc/devices Device drivers
/proc/diskstats /proc/diskstats Hard disk status
/proc/iomem /proc/iomem Physical address allocation
/proc/dma /proc/dma Direct memory access

(DMA) channel
information
/boot/config* /boot/config* Kernel configuration files
/etc/grub.conf /etc/grub.conf Grand Unified Boot Loader

(GRUB) configuration file
/boot/grub/ /boot/grub/device.map Boot device mapping

device.map information
/boot/grub/ /boot/menu.lst Boot menu file

menu.lst
dump_list.txt du -ah /var/crash/ Crash file list
dmesg.txt dmesg Dmesg file
/ /root/.bash_history Historical commands

root/.bash_histor executed
y
command_log.tx df -liT Available disk space

t
mount Mounting information
/usr/bin/last -xF | grep Reboot records

"reboot\|shutdown\|runlevel
\|system"
nfsstat -cnrs NFS service status
lsof List of opened files
ulimit -a System resource

restrictions
ipcs -a Status of communication

facilities between processes
ipcs -l Shared information

memory
sysctl -a Sysctl settings and kernel

parameters in /proc/sys
uptime Operating duration

uname -a Kernel information
ps auwx List of all processes
last Historical login user

records
hostid Login user IDs
/bin/rpm -qa List of installed software
printenv Environment variables
hostname Host names
SLES nts_$ supportconfig (SLES) Log file collection package

(hostname)_$ for fault diagnosis on SLES
(time).tbz
nts_$ supportconfig (SLES) Verification code of the log

(hostname)_$ file collection package for
(time).tbz.md5 fault diagnosis on SLES
RHEL sosreport-$ sosreport (RHEL) Log file collection package

(hostname)_$ for fault diagnosis on
(time).tar.xz RHEL
sosreport-$ sosreport (RHEL) Verification code of the log

(hostname)_$ collection suite for fault
(time).tar.xz.md diagnosis on the RHEL OS
5
NOTE
l The number and content of collected log files slightly vary according to the Linux version, but all
log files collected are listed in Table 5-2.
l The InfoCollect tool invokes a large number of system commands, such as ipmitool and smartctl. If
the related software has not been installed, certain log information cannot be collected.
l The bash_history command collects historical command information for fault diagnosis. Collect the
information unless necessary. You can modify the config.ini file to disable command information
collection or manually delete the collected command information after collection and then compress
the files into a package.
l The sosreport and supportconfig commands are log file collection commands that come with the
OS. The collected log files are used for in-depth fault diagnosis. Run the commands only when
necessary. You can modify the config.ini file to disable log file collection or manually delete the log
files after collection and then compress the files into a package.
l You can modify the config.ini file in the InfoCollect directory to specify the log files to be collected.
l mezz_info.tar.gz contains NIC information about the E9000. Although duplicate information is
collected, the collected information is helpful for E9000 operation.

User Guide 6 FAQs
6 FAQs
6.1 No messages Log File in a Linux Log Package

l Fault symptom: There is no messages file in a Linux log package.
l Fault cause: The InfoCollect version is V101 or V100.
l Solution: Use InfoCollect of the latest version to collect Linux log files.
6.2 No OS Log file in a Windows Log Package

l Fault symptom: There is no OS log file (for example, no file in the winevt folder) in a
Windows log package.
l Fault cause: The InfoCollect version is V100.
l Solution: Use InfoCollect of the latest version to collect Windows log files.
6.3 Failure of Collecting BMC Log Files

l Fault symptom: The error message Log file is not found, please try
collect again later.Upload file to device fail, please
check space is enough or not. is displayed during server BMC log file
collection.
l Fault cause: The available space of the BMC is insufficient. As a result, the collected log
files cannot be stored.
l Solution: Clear /tmp on the BMC as follows:
Step 1 Log in to the BMC CLI over Secure Shell (SSH). See Figure 6-1.

User Guide 6 FAQs
Figure 6-1 Logging in to the BMC CLI over SSH
Step 2 Click Connect.

The Enter Password window is displayed. Enter the BMC password, as shown in Figure
6-2.
Figure 6-2 Entering the BMC password
Step 3 Click OK.

The /tmp directory is displayed. View the files in the directory, as shown in Figure 6-3.
Figure 6-3 Going to /tmp
Step 4 Run the following command to clear /tmp. See Figure 6-4.
rm
NOTE
/tmp is a temporary folder, and all files in /tmp can be deleted.
Figure 6-4 Deleting files from /tmp

User Guide 6 FAQs
Step 5 Use InfoCollect to collect BMC log files again.
----End

User Guide 7 Obtaining Help
7 Obtaining Help
7.1 Making Preparations Before Contacting Huawei

If a fault persists during routine maintenance or troubleshooting, contact Huawei technical
support.
You are advised to make the following preparations before contacting Huawei technical
support.
l Collecting Fault Information
– You need to collect the following information:
n User name and address
n Contact name and telephone number
n Time when the fault occurred
n Fault symptom
n Device type and software version
n Measures taken after the fault occurred and results
n Fault severity and expected rectification deadline
l Preparing for Debugging
When you seek technical support, Huawei technical support may assist you in collecting
more fault information or even rectifying the fault. Before seeking technical support,
prepare spare server parts, screwdrivers, screws, serial cables, network cables, and other
necessary objects.
7.2 Obtaining Help from Huawei Support Website

Huawei provides timely and efficient technical support through local branch offices, the
secondary technical support system, telephone technical support, remote technical support,
and onsite technical support.
The technical support system of Huawei includes:

l Technical support department at Huawei headquarters
l Technical support centers in local branch offices
l Huawei enterprise service website (http://e.huawei.com)

User Guide 7 Obtaining Help
l Customer service center

NOTE
You can also find the latest product manual by entering the keyword in the Search text box in the upper
right corner on the page.


FusionServer Tools V2R2 InfoCollect User Guide 22

Uploaded by

Copyright:

Available Formats

FusionServer Tools V2R2 InfoCollect User Guide 22

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FusionServer Tools V2R2 InfoCollect User Guide 22

Uploaded by

Copyright:

Available Formats

FusionServer Tools InfoCollect

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 22 (2017-09-30) Huawei Proprietary and Confidential i

3 Using InfoCollect (GUI)............................................................................................................. 10

4 Using InfoCollect (CLI).............................................................................................................. 46

5 OS Log Collection Items............................................................................................................ 56

Issue 22 (2017-09-30) Huawei Proprietary and Confidential ii

1.1 Functions and Features

InfoCollect collects the following log files:

Table 1-1 OSs supporting InfoCollect

Windows Windows 7 (32- √ √

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 1

OS Version InfoCollect (GUI) InfoCollect (CLI)

SUSE Linux SLES 11.1 to SLES × √

Red Hat Enterprise RHEL 6.4 to RHEL × √

CentOS CentOS 6.4 to × √

Ubuntu Ubuntu 14.04, × √

Table 1-2 InfoCollect specifications for collecting OS log files

Supported products Huawei V2, V3 and V5 servers

Server Windows OS log file Supported Windows OSs:

Supported products Huawei V2, V3 and V5 servers

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 2

BMC log file collection Supported rack and high-density servers:

Management module log file Supported management modules of blade servers:

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 3

Figure 1-1 Collecting E6000 management module logs

1.3 Precautions for Using InfoCollect

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 4

2.1 Installing InfoCollect

2.2 Uploading the Software Package

Step 1 Double-click Xshell.exe.

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 5

Figure 2-1 SSH User Name

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 6

Figure 2-2 SSH User Authentication

The server Linux OS is successfully connected, as shown in Figure 2-3.

Figure 2-3 Connection succeeded

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 7

Figure 2-4 SSH User Authentication

Step 6 Enter the password in Step 4, and click OK.

Figure 2-5 Selecting the uploading path

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 8

Figure 2-6 Uploading succeeded

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 9

3 Using InfoCollect (GUI)

3.1 Collecting Rack and High-Density Server Log Files

3.1.2 Collecting BMC Log Files

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 10

Figure 3-1 Files in the InfoCollect_GUI folder

Step 2 Double-click the InfoCollect.exe to collect log information.

Figure 3-2 Main window of InfoCollect

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 11

Table 3-1 Parameter description

BMC Info BMC IP BMC IP address of the target server.

Password Password for logging in to the BMC of the target

Figure 3-3 Window for BMC log file collection

Issue 22 (2017-09-30) Huawei Proprietary and Confidential 12

Figure 3-4 SystemConfig.ini file