No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionServer Tools 2.0 InfoCollect User Guide 32

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Collecting OS Log Files

Collecting OS Log Files

Scenario

Collect Windows OS logs using InfoCollect.

Prerequisites

Conditions

  • A Huawei rack or high-density server is available.
  • PowerShell must be installed on the target OS and local PC 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.

  • The InfoCollect directory has sufficient available disk space for storing collected log files.
  • When Windows OS logs are to be collected, the installation directory of InfoCollect cannot contain &[]. Otherwise, PowerShell will fail.
  • The IP address of the service network port on the target server must be pinged.

Procedure

  1. To collect Windows OS logs, perform the following operations to check whether the WinRM service is enabled. To collect Linux OS logs, go to 2.

    1. Log in to the target Windows OS, and open PowerShell as an administrator.
    2. In PowerShell, run the following command to check whether the WinRM service is enabled:

      get-service winrm

      • If the WinRM service is in the Running state, the WinRM service is enabled, as shown in Figure 3-8.
        Figure 3-8 WinRM service enabled
        NOTE:

        The WinRM service is enabled on Windows Server 2012 and Windows Server 2016 by default.

      • If the WinRM service is in the stopped state, the WinRM service is not enabled. Perform 1.c to enable the WinRM service and perform 1.b again to check whether the WinRM service is enabled successfully.
    3. In PowerShell, run the following command to enable the WinRM service. During the service enabling process, press Enter if information is displayed, as shown in Figure 3-9.

      winrm quickconfig

      Figure 3-9 Enabling the WinRM service

  2. Go to the InfoCollect_GUI folder. Figure 3-10 shows the files in the folder.

    Figure 3-10 Files in the InfoCollect_GUI folder

  3. Right-click InfoCollect.exe and choose Run as administrator.

    The window shown in Figure 3-11 is displayed.

    Figure 3-11 Main window of InfoCollect

  4. Deselect BMC Info and select Windows in the OS Info area.

    The Windows OS log collection window is displayed, as shown in Figure 3-12. Table 3-2 describes the parameters.

    Figure 3-12 Windows OS log collection window
    Table 3-2 Parameter description

    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.

    SSH Port

    The default value is 22. It must be the same as the SSH port number of the target server.

    Root PassWord

    If you log in as a non-root user, you need to enter the password of the root user. This parameter is mandatory only for the Linux OS.

    Windows

    OS IP

    OS IP address of the target server.

    User Name

    OS administrator user name of the target server. The default value is Administrator.

    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.
    • During in-band log collection on Linux, the user password of the OS on the target server cannot contain double quotation marks ("). Otherwise, InfoCollect cannot collect logs.

  5. 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-13. If the local PC is not added to a domain, enter the host name/user name and password of the local PC. For details about the host name and domain information of the local PC, see Viewing the Host Name and Domain of the Local PC.

    Figure 3-13 Entering information

    InfoCollect V138 or later supports the proxy service. The requirements on the proxy server are as follows:

    • The proxy server must be a Linux host. The Red Hat and SUSE OSs are preferred.
    • The SSH server of the proxy server must be configured as follows to enable the forwarding function and enable the forwarding port externally.
      • Enable AllowTcpForwarding.
      • Enable GatewayPorts.

    To use the proxy service (which is supported only on Linux), click SSH Proxy in the upper right corner. In the dialog box shown in Figure 7 SSH Proxy, select SSH Proxy, and set the parameters.

    Figure 3-14 SSH Proxy

    The parameters are described as follows:

    • SSH Proxy IP: specifies the IP address of the proxy server.
    • Server Port: specifies the port number. The default value is 22.
    • User Name: specifies the user name.
    • Password: specifies the password.

  6. Click Start.

    Log file collection starts. See Figure 3-15.

    Figure 3-15 Collecting log files
    NOTE:
    • The log collection takes several minutes.
    • 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-16.

    Figure 3-16 Information indicating that log file collection is complete

  7. Click Log directory.

    Log files are obtained.

Translation
Download
Updated: 2019-01-09

Document ID: EDOC1000093346

Views: 50525

Downloads: 4645

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next