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).
Introduction to Stateless Computing

Introduction to Stateless Computing

The stateless computing function allows you to virtualize servers and separate server hardware from configuration information to implement quick, different configurations for various servers so that the servers can adapt to different service scenarios.

  • The stateless computing function applies to the following Huawei servers:

    Server Type

    Server Model

    Rack server

    RH2288H V3, RH1288 V3, RH2288 V3, RH5288 V3, RH5885V3C10, RH5885H V3, 1288H V5, 2288H V5, 2488 V5, 2488H V5, 5885H V5.

    Blade server

    E9000: CH121 V2, CH220 V2, CH221 V2, CH222 V2, CH242 V2, CH240 V2, CH242 V3, CH242 V5, CH226 V3, CH225 V3, CH121 V3, CH220 V3, CH222 V3, CH140 V3, CH121H V3, CH121 V5, CX310, CX210, CX220, CX920.

    High-density server

    XH620 V3, XH622 V3, XH628 V3, XH321 V3, XH321 V5.

You are advised to back up the database automatically as scheduled or manually when using the stateless computing function.

  • The following table lists the card types supported by stateless computing.

    Card Type

    Card Model

    HBA

    LPE12000, LPE12002, QLE2560, QLE2562, QLE2670, QLE2672, MZ220

    CNA

    MZ510, MZ512, MZ910, MZ710, MZ520, MZ522

    RAID controller card

    LSI SAS2308, LSI SAS2208, LSI SAS3008, LSI SAS3108, Avago SAS3408iMR, Avago SAS3004iMR, Avago SAS3508

NOTE:
  • For CX920 switches, the downlink Fabric plane supports MZ710 NICs and the Base plane supports LOM NICs.
  • Currently, stateless computing supports the following E9000 switch modules: CX310 (Fabric plane), CX920 (Fabric and Base planes), CX210 and CX220 (FC plane).

Application Scenario

  • Offline configuration

    The blade to be configured online is not inserted or is removed when you discover an E9000 server.

    Add the blade to the device collection, associate the blade with a profile, set Activation mode to Upon re-power-on, and insert the blade.

    NOTE:
    • Before configuring a device offline, check that the trap IP address of the server is correctly set so that the device can be discovered.
    • You can view the loading progress in the device list within 20 minutes after you add a device.
  • Profile migration

    The stateless computing function enables a profile to be migrated between any two chassis in a device collection or in a device group or between two domains.

    Powered-on devices can be manually migrated. After migration commands are run in eSight, the devices automatically power off, and their profiles are migrated to target devices.

  • Device replacement

    The stateless computing function enables the profile of a faulty device to be automatically delivered to a new device to implement rapid configuration.

    Before replacing a faulty device, ensure that the faulty device has the same hardware configuration as the new device and is associated with a profile.

    NOTE:
    • Before replacing a device, check that the trap IP address of the server is correctly set so that the device can be discovered.
    • You can view the loading progress in the device list within 20 minutes after you add a device.

Networking Requirements

Stateless computing supports the following networking types:

  • In-band networking

    In in-band batch deployment, eSight automatically mounts a small operating system to the virtual DVD-ROM drive of a device. When the device boots from the operating system, the operating system invokes a DHCP client to obtain the eSight service IP address. Then the device uses the obtained IP address to communicate with eSight for device configuration. When invoking a DHCP client to obtain the eSight service IP address, the device can obtain the IP address from the default subnet or a specified subnet. If the subnet from which the device obtains the eSight service IP address through a DHCP client does not contain a DHCP server, and eSight resides on the subnet, you can enable the DHCP service on the Service Settings page of eSight. For details about enabling the DHCP service, see Configuring the DHCP Service. To obtain the eSight service IP address from a subnet, perform the following procedure:

    1. Log in to the eSight server.
      NOTE:

      If eSight runs in active/standby mode, perform the procedure on both the active and standby nodes.

      • Windows

        Log in to the eSight server as the administrator user.

      • Linux

        Log in to the eSight server as the ossuser user.

    2. Open the vlan.conf file in eSight installation directory\AppBase\lib\resources\network.
    3. Change the values of VlanId and cfgVlanId according to the live network environment.

      The VlanId parameter applies to stateless computing.

      The cfgVlanId parameter applies to configuration deployment and firmware upgrade.

      NOTE:

      The value ranges of the VlanId and cfgVlanId parameters are [2, 4094].

  • Fully out-of-band networking

    In fully out-of-band batch deployment, eSight automatically mounts a small operating system to the virtual DVD-ROM drive of a device. When the device boots from the operating system, eSight sends iBMC instructions to the device for device configuration.

    NOTE:
    • The device's IP address must be reachable for it to connect to eSight.
    • The user must have permission on the IPMI for a device to connect to eSight.
    • The version of the iBMC must be 2.56 or later.

Northbound and Southbound Network Isolation Restrictions

Northbound and southbound network isolation does not apply to scenarios where eSight involves multiple subnets.

Northbound and southbound network isolation is to isolate the southbound and northbound IP addresses of eSight from each other. The northbound IP address is used to log in to eSight. The southbound IP address is used for eSight to communicate with servers.

  • Non-isolation scenario:

    Multiple NICs on the eSight server can communicate with servers properly.

    Support the in-band, out-of-band, and fully out-of-band networking modes.

  • Isolation scenario:

    Only one NIC on the eSight server can communicate with servers properly.

    • The IP addresses of the server management plane and server service plane are in the same network segment.

      Support the in-band, out-of-band, and fully out-of-band networking modes.

    • The IP addresses of the server management plane and server service plane are in different network segments.

      Support only the out-of-band and fully out-of-band networking modes.

Network Port Configuration Requirements

If the network port bound during eSight installation differs from the service network port of the eSight server, choose Tools > Multi-subnetwork Management Tool on the eSight Console to complete the configuration.

NOTE:
  • Windows: Log in to the eSight server as the Administrator user. Choose Tools > Multi-subnetwork Management Tool on the eSight Console to complete the configuration.
  • Linux: Log in to the eSight server as the ossuser user and run the following command to start the Multi-subnetwork Management Tool to complete the configuration:

    > export DISPLAY=Client IP address:0.0

    > cd eSight installation directory/mttools/tools

    > ./multi-subnetwork.sh

Process Guide

Quick Start under Process Guide allows you to complete common operations related to stateless computing by following a predefined process. The common operations include creating pools, adapters, basic input/output system (BIOS) policies, VLAN groups and profiles, and adding domains.

When stateless computing configuration is complete, back up the configuration immediately. Otherwise, if you restore the configuration by using the previous backup, the configuration on the eSight and stateless devices is inconsistent and profiles are repeatedly allocated. As a result, configuration conflicts occur in the stateless devices and services are affected.

Pools

You can click Create MAC Address Pool, Create WWPN Pool, Create WWNN Pool, and Create UUID Pool under Pools to create different types of pools for profiles to associate and use.

Adapters

You can click Create Adapter under Adapters to create adapters for profiles to associate and use.

BIOS Policies

You can click Create BIOS Policy under BIOS Policies to create BIOS policies for profiles to associate and use.

VLAN Group

You can choose VLAN Group in the navigation area and click Add on the page displayed to add a VLAN group providing VLANs required for profile creation, domain configuration, and uplink configuration.

Profiles

You can click Create Profile, Create Group Profile, and Create Template under Profiles to configure a single profile, a group profile, or a template for stateless devices to associate and use.

Domain Manager

You can click Add Domain under Domain Manager to quickly associate stateless devices with profiles/group profile and manage stateless devices.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 312973

Downloads: 635

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