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 Blade Server BMC and OS Log Files

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.

NOTE:

If the blade server iBMC version is earlier than 2.0, BMC logs cannot be collected completely. Collect logs by using BMC IP addresses. For details, see Collecting OS Log Files.

Prerequisites

Conditions

  • A Huawei E9000 server is available.
  • 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.

  • For server Windows OS log collection, the WinRM service must be enabled on the target OS. For details, see 1 in Collecting OS Log Files.
  • When Windows OS logs are to be collected, the installation directory of InfoCollect cannot contain &[]. Otherwise, PowerShell will fail.
  • The InfoCollect directory has sufficient available disk space for storing collected log files.
  • The IP address of the MM910 on the target server must be pinged.

If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

Procedure

  1. Go to the InfoCollect_GUI folder. Figure 3-25 shows the files in the folder.

    Figure 3-25 Files in the InfoCollect_GUI folder

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

    The window shown in Figure 3-26 is displayed.

    Figure 3-26 Main window of InfoCollect

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

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

    Figure 3-27 E9000 log collection window

    Table 3-5 Parameter description

    Information

    Parameter

    Description

    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.

    SSH Port

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

  4. Enter the MM910 IP address, user name, and password of the target server, and click Connect.

    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, click SSH Proxy in the upper right corner. In the dialog box shown in Figure 3-4, select SSH Proxy, and set the parameters.

    Figure 3-28 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.

    Connect to the management module to obtain the available slot and switch module information. Slot numbers of available nodes are displayed in the Select Device area as shown in Figure 3-29.

    Figure 3-29 Obtaining device information

  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-30. Table 3-6describes OS and Local information parameters.

    Figure 3-30 Selecting a device

    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-31 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.
    Table 3-6 Parameter description

    Information

    Parameter

    Description

    OS (Linux)

    OS Type

    OS type of the target server.

    IP Address

    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 of the target server using the network port IP address.

    SSH/PS Port

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

    Rootpassword

    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.

    OS (Windows)

    OS Type

    OS type of the target server.

    IP Address

    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 of the target server using the network port IP address.

    SSH/PS Port

    The default value is 5985. This port must be consistent with the PowerShell remote management port of the target server OS.

    Rootpassword

    You do not need to set this parameter on the Windows OS. If you set this parameter, the error message "Do not set RootPassword if the value of OS Type is not Linux." is displayed.

    Local information

    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 Local information parameters only when collecting Windows OS logs.
    • Set User Name to an administrator (for example, root or Administrator) for collecting log files.
    • You can select multiple slot numbers to collect OS and BMC logs of multiple blade servers. The following uses Slot9 as an example.
    • 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.

  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-32. In the displayed dialog box, enter the local PC domain name/user name and password.

    Figure 3-32 Entering information
    NOTE:
    • 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.
    • To copy the settings in a row to the next row, click .

  7. Click Start.

    Log file collection starts. See Figure 3-33.

    Figure 3-33 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-34.

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

  8. Click Log directory.

    Log files are obtained.

Translation
Download
Updated: 2019-01-09

Document ID: EDOC1000093346

Views: 49329

Downloads: 4627

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