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

eSight V300R009C00 Operation Guide 10

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).
Automatic Configuration Migration

Automatic Configuration Migration

Automatic Configuration Migration Overview

The automatic configuration migration function of stateless computing separates server hardware and configurations, automatically migrates configurations to standby servers matched, and automatically activates the standby servers to run services.

The automatic configuration migration function applies to the following servers:

  • Blade servers
  • Rack servers
  • High-density servers

Process

Figure 9-10 shows the automatic configuration migration process.

Figure 9-10 Automatic configuration migration process

Overview

During automatic configuration migration, servers within the same automatic migration group can automatically migrate configurations to one another.

When creating an automatic migration group for failover, you can select multiple servers from different domains. Automatic migration groups are classified by failover triggering policies and are irrelevant to domains. During a failover, migration is automatically triggered. To avoid mismatching between devices and networks, failover does not allow automatic cross-domain migration.

NOTE:
  • An automatic migration group must contain a standby server that matches an active server whose configuration is to be migrated. Otherwise, the automatic migration fails.
  • The iBMC version for V3 servers must be V201 or later. Otherwise, eSight cannot find the best matched standby server during active and standby servers matching.

Active and Standby Servers Matching Rules

If any server within an automatic migration group meets the automatic migration conditions, eSight automatically checks for a standby server that matches this server and migrates the configuration of the active server to the standby server.

For rack servers and high-density servers, when matching active and standby servers, eSight queries a standby server that is of the same model as that of the active server for optimal matching. If eSight finds no standby server of the same model, eSight checks for a standby server that is of the same type as that of the active server:

  • If eSight finds a standby server of the same type, the matching is successful, and eSight starts migrating the configuration.
  • If eSight finds no standby server of the same type, the matching fails, and configuration migration is not implemented.

Figure 9-11 shows the active and standby servers matching process for blade servers.

Figure 9-11 Active and standby servers matching process for blade servers (1)

If a fault occurs in a blade server in an automatic migration group, and the automatic migration conditions are met, eSight automatically matches a standby blade server within the automatic migration group:

  • If the profile of the active server contains mezzanine module configuration:
    1. Checks whether standby servers in the same automatic migration group include blade servers:
      • If yes, eSight executes b.
      • If no, the matching fails, and the automatic configuration migration fails.
    2. Use the best matching rule (shown in Figure 9-12) to implement accurate matching.
      • If the matching is successful, eSight starts migrating the configuration from the active server to the matched standby server.
      • If the matching fails, eSight executes c.
    3. Checks whether a standby blade server of the same model as the active blade server exists among standby blade servers without mezzanine module configurations in the same automatic migration group:
      • If yes, the matching is successful, and eSight starts migrating the configuration from the active server to the matched standby server.
      • If no, eSight executes d.
    4. Select any standby blade server from the standby blade servers without mezzanine module configurations in the same automatic migration group and migrate the configuration from the active server to that standby server.
  • If the profile of the active server does not contain mezzanine module configuration:
    1. Checks whether standby servers in the same automatic migration group include blade servers:
      • If yes, eSight executes b.
      • If no, the matching fails, and the automatic configuration migration fails.
    2. Checks whether a standby blade server of the same model as the active blade server exists among standby blade servers without mezzanine module configurations in the same automatic migration group:
  • If yes, the matching is successful, and eSight starts migrating the configuration from the active server to the matched standby server.
  • If no, eSight selects a blade server that contains information about the fewest mezzanine modules from the same automatic migration group and starts migrating the configuration from the active server to that standby server.

During active and standby servers matching, if multiple standby blade servers contain mezzanine module configuration that is the same as that in the profile of the active blade server, eSight implements further accurate matching based on the process shown in Figure 9-12.

Figure 9-12 Active and standby servers matching process for blade servers (2)

eSight checks for a standby blade server that contains the same mezzanine module configuration as that in the profile of the active blade server within the same automatic migration group:

  • If no such standby blade server is found, the matching fails, and configuration is not migrated from the active blade server to the standby server.
  • If such standby blade servers are found, eSight selects a standby blade server based on the best matching rule and starts migrating configuration from the active blade server to the selected standby server.

    The best matching rule is as follows:

    1. eSight selects standby blade servers whose mezzanine module configuration is closest to that in the profile of the active blade server (there may be multiple standby blade servers whose mezzanine module configuration is equally close to that in the profile of the active blade server).
    2. If multiple standby blade servers are selected in step 1, eSight selects the one that contains the fewest number of mezzanine modules.

      Best matching enables more efficient use of server resources.

Example

Active blade server A meets the automatic migration conditions, and eSight starts matching a standby blade server. Table 9-20 lists the mezzanine module configuration of active and standby servers.

Table 9-20 Mezzanine module configuration of the active and standby server

Server

Mezzanine Module Configuration

Active server A

(A for short)

MEZZ1: HBA

MEZZ3: CNA

Standby server B

(B for short)

MEZZ1: HBA

MEZZ5: CNA

Standby server C

(C for short)

MEZZ1: HBA

MEZZ2: CNA

MEZZ3: CNA

Standby server D

(D for short)

MEZZ1: HBA

MEZZ3: CNA

Standby server E

(E for short)

A blade server with no mezzanine module configuration

Standby server F

(F for short)

Not a blade server

The active and standby servers matching process is as follows:

eSight checks for blade servers among all standby servers:

  • If eSight finds no blade server, the matching fails, and configuration migration is not implemented.
  • If eSight finds blade servers (servers B, C, D, and E in this example) (standby server F is eliminated), eSight checks whether the standby blade servers contain mezzanine module configuration:
    • If eSight detects that the standby servers B, C, and D contain mezzanine module configuration, eSight uses the best matching rule to find standby servers whose mezzanine module configuration is closest to that in the profile of the active blade server A out of standby servers B, C, and D.

      In this example, the mezzanine module configuration of standby servers C and D is equally close to that in the profile of the active server, and both servers C and D are selected. Standby server B does not contain MEZZ3 information as that in the active server and is eliminated. eSight compares standby servers C and D and selects the one that contains the fewest number of mezzanine modules.

      In this example, as shown in Table 9-20, the MEZZ1 and MEZZ3 configuration information of both servers C and D are the same as that of active server A, and server C contains an extra MEZZ2. If the configuration of the active server is migrated to server C, MEZZ2 on server C is idle, wasting resources. Therefore, eSight selects server D and migrates configuration to server D for more efficient use of server resources.

    • If no standby blade server contains mezzanine module configuration, eSight selects any standby blade server (for example, standby server E) that is of the same type as active server A and starts configuration migration.

Managing Automatic Migration Groups

You can centrally manage automatic migration groups. For example, you can create, view, or delete automatic migration groups.

Creating an Automatic Migration Group

You can create an automatic migration group.

Prerequisites

  • A domain exists.
  • The devices to be added to the automatic migration group are devices in the domain.

Context

Figure 9-13 shows how to create an automatic migration group.

Figure 9-13 Process of creating an automatic migration group

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Automatic Migration Group.

  3. You can click Create in the function pane to open the page for creating an automatic migration group.
  4. Create an automatic migration group.

    1. Configure basic information about the new automatic migration group.
      1. Type the group name.
      2. Select the group type. The options are Blade server, Rack server, and High-density server.
      3. Type the description of the group description.
    2. Select a device.
      1. Click Add. The Add Device page is displayed.
      2. In the navigation tree, choose Domain.

        In the Available Resources area, information about the device in domain is displayed.

      3. In the Available Resources area, select a device for the automatic migration group.

        The selected device is displayed in the Selected Resources area.

      4. Click OK.
    3. Select a migration condition.
      1. Click Add. The Add Migration Condition page is displayed.
      2. Select a migration condition.
      3. Click OK.

  5. Click OK.

    NOTE:

    After the automatic migration group is created, and the migration condition is triggered, eSight automatically searches for a standby device within the group and migrates the configuration of the faulty device to the standby device.

    If no device is matched from the standby devices, eSight rolls back the configuration and re-enables the faulty device. It is recommended that a standby device matching the active device be reserved in the automatic migration group for fast service recovery.

Viewing an Automatic Migration Group

You can view information about an automatic migration group.

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Automatic Migration Group.

  3. View the information about an automatic migration group.

    Information about an automatic migration group includes Name, Type, Number of Normal Devices, Number of Successfully Migrated Devices, Number of Devices Failing to Be Migrated, Number of Standby Devices, and Description.

    NOTE:

    If you want to change the name or description of an automatic migration group, click in the Operation column.

    1. View the information about devices in an automatic migration group.
      1. Select the automatic migration group whose device information is to be viewed.
      2. Click Device List.

        Device information includes Name, IP Address, Slot, Model, Status, and Associated Profile.

        If the group contains a device that has been migrated or experienced a migration failure, you must click in the Operation column and configure the device as a standby device or recover it to the normal state.

    2. View migration conditions.
      1. Select the automatic migration group whose migration conditions are to be viewed.
      2. Click Migration Condition.

        Migration conditions include Name, Level, and Impact Scope.

    3. View migration records.
      1. Select the automatic migration group whose migration records are to be viewed.
      2. Click Migration Task Record.

        Migration record information includes Production Device Name, Production Device IP Address, Target Device Name, Target Device IP Address, Migration Status, Migration Profile, Progress, Migration Condition, Details, Start Time, and End Time.

Deleting an Automatic Migration Group

You can delete an automatic migration group.

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Automatic Migration Group.

  3. Delete an automatic migration group.

    1. Select the automatic migration group to be deleted.
    2. Click Delete.
    3. Click OK. A success message is displayed.

  4. Click OK.

Managing Automatic Migration Conditions

You can centrally manage automatic migration conditions. For example, you can add, view, or delete automatic migration conditions.

Adding a Migration Condition

You can add a migration condition.

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Migration Condition Management.

  3. Add a migration condition.

    1. Click Add.

      The Add Migration Condition page is displayed.

    2. Select a migration condition.
    3. Click OK.

      A success message is displayed.

  4. Click OK.

Viewing an Automatic Migration Condition

You can view an automatic migration condition.

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Migration Condition Management.

  3. In the function pane, view basic information about an automatic migration condition.

    Basic information about an automatic migration condition includes Name, Level, and Impact Scope.

Deleting an Automatic Migration Condition

You can delete an automatic migration condition.

Procedure

  1. On the menu bar, choose Resource > Server.

  2. In the navigation tree, choose Stateless Computing > Configure Automatic Migration > Migration Condition Management.

  3. In the function pane, select the automatic migration condition to be deleted.
  4. Click Delete.

    A success message is displayed.

  5. Click OK.
Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 333857

Downloads: 667

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