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.


MIB Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
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).
Using the MIB to Upgrade the Device

Using the MIB to Upgrade the Device


You can use the MIB to upgrade a device remotely.

The following MIB objects are used to remotely upgrade a device.



MIB File









This example uses the MIB Browser as the NMS software to illustrate the operations. If you use other NMS software, refer to documentation of the specified software.

Pre-configuration Tasks

Before using the MIB to upgrade a device, complete the following tasks:

  • Connecting the device to the NMS through Simple Network Management Protocol (SNMP)
  • Setting parameters for the MIB Browser and connecting it to the device
  • Compiling MIB files using the MIB Compiler and loading the MIB files
  • Configuring a file server to save the system software for device upgrade and ensuring that the device has reachable routes to the file server (FTP server is used as an example, and the system software has been stored in the working directory of the file server)
  • Ensuring that the storage space of the device is sufficient for storing the system software (the upgrade will fail if the storage space is insufficient)


  1. Load the system software to the device.

    You can complete software upload using huaweiFlhOpEntry. The operations are as follows:

    1. Search for the MIB object huaweiFlhOpEntry. You can search for an object in the MIB tree. However, it is difficult to find an object when a large number of MIB files are imported to the MIB Browser. In this case, press Ctrl+F, as shown in Figure 3-22.
      Figure 3-22  Searching for a MIB object
    2. Perform multiple variable bindings. Create a table instance first.
      Figure 3-23  Creating a table instance
    3. Specifies the table instance ID, for example, 1. When specifying an instance ID, ensure that the instance ID is not used by other instances.
      Figure 3-24  Specifying the table instance ID
    4. Delete unnecessary subnodes from the table and set values for the remaining subnodes. After the operations are complete, the interface shown in Figure 3-25 is displayed.

      To delete or set a subnode, right-click the subnode and choose an operation from the displayed shortcut menu.

      Figure 3-25  Setting the table instance

    5. After setting the table instance, change Get to Set and click Set to upload the system software
    6. Check the operating status using hwFlhOperStatus. Right-click hwFlhOperStatus and choose Walk, as shown in Figure 3-26.

      Figure 3-26  Checking the operating status

      If the operating status is displayed as , the system software is successfully uploaded.

  2. Set the startup file.

    After the system software is uploaded to the device, you must specify the system software as the next startup file. You can use hwSysReloadScheduleEntry in the HUAWEI-SYS-MAN-MIB file to complete the setting:

    1. Search for the object hwSysReloadScheduleEntry. You can search for the object in the MIB tree or press Ctrl+F.
    2. Perform multiple variable bindings. Create a table instance and specify the instance ID. Delete unnecessary subnodes from the table and set values for the remaining subnodes. The detailed operations are similar to those of huaweiFlhOpEntry. After the operations are complete, the interface shown in Figure 3-27 is displayed.

      Figure 3-27  Setting the table instance

      You can query the value of hwSysReloadImage using the hwSysImageName subnode of hwSysImageTable. Right-click hwSysImageName and choose Walk to query the index of the system software, as shown in Figure 3-28.
      Figure 3-28  Querying the system software index
      Figure 3-29 shows the query result.
      Figure 3-29  Query result the system software index

    3. After setting parameters for the table instance, switch Get to Set.
    4. Click Set and check the result using hwSysReloadImage. Right-click hwSysReloadImage and choose Walk. If the result shown in is displayed, the system software for next startup is changed to
  3. Restart the device.

    Restart the device to make the startup file take effect. You can restart the device using hwSysReboot.
    1. Search for the object hwSysReboot. You can search for the object in the MIB tree or press Ctrl+F.
    2. Enter the single node setting interface. hwSysReboot is a single node object. Right-click the object and choose Set from the displayed shortcut menu.
      Figure 3-30  Entering the single node setting interface
    3. Set the restart range.
      In the dialog box that is displayed, set the restart range to rebootWholeRoute(2), indicating that all the devices are restarted, as shown in Figure 3-31.
      Figure 3-31  Setting the restart range

      Numbers 1, 2, and 3 in this figure indicate the sequence in which operations are performed.

    4. After the configurations are complete, click in the upper left corner of the dialog box.

  4. Verify the configuration. After the device is restarted, query the device version using sysDescr to check whether the upgrade succeeds.
    1. Search for the object sysDescr. You can search for the object in the MIB tree or press Ctrl+F.
    2. Right-click sysDescr and choose Walk.

      Figure 3-32  Querying the device version
      The result shown in Figure 3-33 indicates that the upgrade succeeds.
      Figure 3-33  Query result of the device version

Updated: 2019-06-05

Document ID: EDOC1000097213

Views: 128093

Downloads: 688

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