Table of Contents

Related Documents

05-iFIST Configuration Management and Log Download Configuration Examples

Title	Size	Download
05-iFIST Configuration Management and Log Download Configuration Examples	1.33 MB

H3C iFIST

Configuration Management and Log Download Configuration Examples

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.

Contents

Introduction· 1

Prerequisites· 1

Example: Performing configuration management and log download· 1

Network configuration· 1

Software versions used· 2

Analysis· 2

Restrictions and guidelines· 2

Procedure· 3

Logging in to iFIST· 3

Using the configuration management feature· 5

Using the log download feature· 10

Verifying the configuration· 12

Verifying configuration management 12

Verifying log download· 14

Introduction

This following information describes how to complete configuration management and log download via iFIST. iFIST supports importing and exporting server configuration as well as downloading various types of logs. iFIST interacts with HDM to obtain HDM, BIOS, and RAID configuration files. It supports downloading server OS logs, SDS logs, system logs, storage controller logs, drive logs, server component SN information, and drive SMART information. The Web interface is intuitive and provides a simpler workflow.

Prerequisites

This document is not restricted to specific software or hardware versions. Procedures and information in the examples might be slightly different depending on the software or hardware version of the device.

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of configuration management and log download on iFIST.

Example: Performing configuration management and log download

Network configuration

As shown in Figure 1, the IP address of the PC can reach the HDM management IP address of the server. This setup allows you to access HDM for the server via the PC client, and then access iFIST through the KVM remote console from HDM. Then, you can perform configuration management and log download through iFIST. In this example, the server is H3C UniServer R5300 G6.

· HDM:

¡ HDM management IP address: 172.15.38.196/176

¡ Default username: admin

¡ Default password: Password@_

· User PC:

¡ IP address: 192.168.11.10/16

¡ Operating system: Windows 10

Figure 1 Network diagram

Software versions used

This configuration example was created and verified on HDM-2.98, BIOS-5.48, and iFIST-1.42.

Analysis

Access iFIST from the KVM remote console from HDM and use iFIST to manage server configuration and download logs.

Restrictions and guidelines

Follow these restrictions and guidelines when you manage server configuration and download logs:

· Configuration management

¡ In the current software version, only USB flash drives formatted by using the FAT32 or NTFS file system support configuration import and export.

¡ The PMC storage controller does not support the import and export of RAID configuration.

¡ The configuration management feature needs to cooperate with HDM. Only HDM-1.11.25 and later versions support configuration management.

¡ Support for ACS configuration varies by device model. For more information, see the iFIST Web interface.

¡ Before importing the RAID or BIOS configuration file, make sure the server model and component configuration in the configuration file is consistent with the actual configuration. The hardware configuration includes storage controller models and drive numbers and slots. Make sure the storage controller is in RAID mode before you import RAID configuration.

¡ Before you import HDM configuration, make sure the device model is the same. First delete the comment statements for the user configuration information in the configuration file, and then change the user password into a plaintext password.

¡ Make sure the bonding mode setting in the HDM configuration file to import is consistent with the bonding mode setting on the target server.

¡ Before you import the RAID configuration, make sure the old RAID information on the drives is cleared. If you fail to do so, the drives will be marked as foreign, which will causes RAID configuration failure. To avoid RAID configuration import failure, clear the existing RAID configuration from the BIOS before you import RAID configuration.

¡ If a configuration item is deleted or does not exist in the HDM configuration file to import, that configuration item on the server will remain unchanged after the import.

¡ Before you export RAID configuration, make sure the storage controller is initialized.

¡ Before you export RAID configuration, make sure logical drives of the RAID controller are in normal state, and no scaling, migration, rebuilding, or erasing operations are performed.

· Log download

¡ To avoid log download failure, make sure the HDM Web interface does not perform log download before you download logs from iFIST.

¡ Support for log types depends on the device model. For more information, see the iFIST Web interface.

Procedure

Logging in to iFIST

1. Open the browser on the PC and enter HDM management IP address 172.15.38.196 in the address bar to access the HDM login page, as shown in Figure 2. Enter the default username admin and password Password@_ on the HDM login page, click Sign in.

Figure 2 HDM login page

The Dashboard page opens, as shown in Figure 3.

Figure 3 Dashboard page

2. As shown in Figure 4, click Start in the Quick access area to launch the KVM remote console. For more information about the KVM remote console, see H3C Servers HDM2 User Guide.

Figure 4 KVM remote console

3. Select Power > Force System Reset from the KVM menu to restart the server, as shown in Figure 5.

Figure 5 Restarting the server

4. After the server completes initialization, it enters the boot interface. Once the boot process finishes, it automatically enters iFIST, as shown in Figure 6.

Figure 6 BIOS boot Interface

The iFIST home page opens, as shown in Figure 8.

Figure 7 iFIST home page

Using the configuration management feature

1. On the iFIST home page, select Configuration Management to access the configuration management page, as shown in Figure 8.

Figure 8 Configuration Management page

2. Select one or multiple types of configuration to be exported. If you select RAID and the server has multiple storage controllers, select the target storage controller. This example exports the HDM configuration file. Select HDM for the Select type field, select the target storage device, and then click Export, as shown in Figure 9.

Figure 9 Exporting the configuration

3. In the dialog box that opens, click OK. To avoid export failure, make sure no other operations are performed during the export.

Figure 10 Confirming configuration export

4. Wait patiently as instructed. The export state will change from Not started to Exporting, as shown in Figure 11. The export of the HDM configuration file will take several minutes.

Figure 11 Waiting for the configuration to be exported

5. After the configuration is exported, the export state changes to Completed and the page prompts a successful HDM configuration export and displays the name of the exported configuration file, as shown in Figure 12. The configuration export from iFIST finishes.

Figure 12 Configuration file exported

6. Select the type of the configuration to be imported in the Import Configuration area. Select a storage device, and then select a configuration file in the storage device, and then click Import, as shown in Figure 13. This example imports HDM configuration.

Figure 13 Importing the configuration

7. In the dialog box that opens, click OK. The method for the imported configuration to take effect depends on the component type. Perform operations as instructed.

Figure 14 Confirming configuration import

8. Then, wait patiently as instructed. The export state will change from Not started to Importing, as shown in Figure 15. The Import of the configuration file will take several minutes.

Figure 15 Waiting for configuration import

9. After the configuration is imported, the import state changes to Completed and the page prompts a successful HDM configuration import and displays the name of the imported configuration file, as shown in Figure 16. The configuration import from iFIST finishes.

Figure 16 Configuration file imported

Using the log download feature

1. On the iFIST home page, select Download Logs to access the log download page, as shown in Figure 17.

Figure 17 Download Logs page

2. Select the types of logs to download, select the target USB flash drive, and then click Start download. This example downloads the OS log, as shown in Figure 18.

Figure 18 Selecting log types

3. In the dialog box that opens, click OK.

Figure 19 Confirming log download

The Download result area page will display the download progress and result. If the download fails, an error message will appear. If the log type contains many log messages, the download will take longer. The log download from iFIST finishes when all states change to Download succeeded or Download failed.

Figure 20 Log download result

Verifying the configuration

Verifying configuration management

1. Verify the exported configuration file exported to the USB drive, as shown in Figure 21.

Figure 21 Viewing the exported configuration file (partial)

2. After the HDM configuration file is exported, remove user 1 from the user list on the User Accounts page, as shown in Figure 22. Import the configuration file that is just exported. The User Accounts page restores to the configuration of the configuration file, as shown in Figure 23.

Figure 22 Removing a user from HDM