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


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


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).
Typical Configuration Example

Typical Configuration Example

This topic provides an example to help administrators understand stateless computing.

Stateless Computing

This example shows how to use the eSight stateless computing function to separate server hardware from hardware attributes to automatically deploy and replace servers and migrate services without reconfiguring servers, implementing stateless computing. This function accelerates service configuration, improves maintenance efficiency, and reduces maintenance cost.

Background Information

A company has a large number of servers. To facilitate management, servers are grouped, and the server groups cooperate with each other to process tasks. Each time when a server fault or server expansion occurs, administrators need to manually replace the device and configure hardware (ensuring configuration consistency between the new and existing devices). Such type of configuration is tedious, error-prone, and time-consuming, greatly affecting company services. To resolve this problem efficiently, Huawei eSight offers the stateless computing function that abstracts physical servers into logical servers and virtualizes server configurations so that the configurations can be directly deployed to a new server after a server fault or migration occurs. This stateless computing function greatly reduces O&M costs and service migration cost.

Figure 9-14 shows the stateless computing process.

Figure 9-14 Stateless computing process


The configuration of a server needs to be migrated.

The source server is a blade server whose IP address is

The target server is a blade server whose IP address is

Both the source server and target server must be added to the stateless computing domain and must be of the same type.


  1. Create a resource pool.

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

    2. In the navigation tree, choose Stateless Computing.

    3. In the navigation tree, choose Repository > Pools to display the pool list.

      In the information display area on the right, you can click Create MAC Address Pool, Create WWPN Pool, Create WWNN Pool, or Create UUID Pool to open the corresponding page.

    4. Select a pool type by clicking the corresponding tab, and click Create.
    5. Set the pool name, start MAC address (or start WWPN, WWNN, or UUID), number of servers in the pool, and pool description.


      Name: Pool_01

      Start MAC address: 78-D7-52-CB-00-00

      Quantity: 500

    6. Click OK.

  2. Create an adapter.

    1. Click Adapters in the navigation area. The page for creating an adapter is displayed.
    2. Click Create.
      1. Set Name to CNA_01 and set Description.
      2. Select the adapter type CNA.
      3. Click Next and set the CNA model to MZ512.
      4. Click Next to create teaming and set the PF type, MAC address, and PF VLAN ID for each virtual port.
        1. Create a teaming.

          MZ512, MZ510, and MZ910 NICs support port bonding configuration through teaming. You can configure two physical ports (such as port0 and port1) as a logical port to increase downlink communication channels between switch modules and NICs and improve channel reliability.

        2. Click Create Teaming. The teaming creation page is displayed.
        3. Enter the name and description of a teaming in the Name and Description text boxes respectively.
        4. Configure ports for the teaming.

          Select either of the following port combinations:

          • Port0+Port1
          • Port2+Port3
          • Port0+Port1+Port2+Port3
        5. Select a working mode and the PF type and VLAN group for its virtual port.

          If the physical ports (ports 0, 1, 2, and 3) are virtualized through teaming, the PF type and VLAN group are displayed in the physical port configuration area.

          The teaming working mode can be Active-Backup, Balance, or LACP.

        6. Click OK.
      5. Configure the virtual port information.
        1. Set PF type.
        2. Set MAC address.
        3. Set PF vlan ID.
        4. Optional: Set VLAN Group.

          You can click Advanced for a virtual port, and set the minimum and maximum bandwidth for the PF.

    3. Click OK.

  3. Create a BIOS policy.

    1. Click BIOS Policies in the navigation area. The page for creating a BIOS policy is displayed.
    2. Click Create.
      1. Set Name to BIOS_01 and set Description.
      2. Click Next and set parameters.
      3. Click OK.

  4. Create a VLAN group.

    1. Click Add, open to the VLAN group creation page.
    2. Type the VLAN group name in the Name text box.
    3. Add members to the VLAN group.

    4. Click OK. The system displays a success message.

  5. Create a profile or group profile.

    1. Click Profiles in the navigation area. The page for creating a profile is displayed.
    2. Click Create.
    3. Set Name to Profile_01 and set Description.
    4. Select the profile type Blade server profile.
    5. Click Next and set UUID configuration mode to Inherit current configuration.
    6. Click Next and select the required BIOS policy BIOS_01.
    7. Click Next and select the required adapter.
      1. Select Select from the list.
      2. Select CNA_01.
      3. Select Mezz ID (ID of the mezzanine card to be associated).
    8. Click Next and view summary information of the profile.
    9. Click OK.

  6. Create the domain and activate it.

    1. In the navigation area, choose Domain Management > Domain.
    2. Click Add to create a blade domain.
      1. Set the device domain name to Domain001.
      2. Select the domain type Blade.
      3. In the Available Devices group box, select the server to be added, and add them to the Selected Devices group box.

        The server information is as follows:

        • IP Address:
        • Device Status: Faulty
        • Name: E9000-
        • Blade Slot: 1
      4. Click OK to configure the domain.
      5. Configure the 2X/3X switch module information.

      6. Configure the Fabric and Base planes.
        1. Set the working mode to Stack.
        2. Configure stacking ports.

        3. Set parameters in IP Address/User Configuration.

        4. Configure the uplink.
          1. Click Add below Uplink Configuration.
          2. Enter the uplink name and short description.
          3. Set the interface type to Eth Trunk.
          4. Set the negotiation type to Enable.
          5. Select a VLAN group.
          6. Configure the Ethernet trunk.

          7. Set the Ethernet trunk mode to Manual.
          8. Select Min. Active Links to 1.
          9. Click OK.

    3. Click OK.

      The domain management page is displayed.

    4. Click in the domain record to activate the domain.

  7. Associate the profile and activate it.


    Associate and activate the profile only after the domain is activated and the uplink configuration takes effect.

    1. Select the device domain Domain001

      Information about the devices in the domain is displayed.

    2. Click to go to the blade display page.
    3. Click in the row where the device to be associated resides.

      The Associate the Profile dialog box is displayed.

    4. Select the profile Profile_01 to be associated.
    5. Select the activation mode Now.
    6. Click OK to complete the association and activation.
    7. Optional: Migrate device profiles.

      When a server fault or server expansion occurs, you need to migrate device profiles.

      1. Click in the row where the device whose profile is to be migrated resides.

        The Migrate Profile dialog box is displayed.

      2. Select a target server.
      3. Select the activation mode Now.
      4. Click OK to associate the profile with the new server and activate it.

        The system displays a message indicating the profile migration success.

Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 313200

Downloads: 635

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