Maintenance Constraints and Precautions

Overall Maintenance Constraints and Precautions

• During maintenance, if the following faults occur, rectify them according to the Troubleshooting Guide.
• If the active FusionInsight management node is powered off, an active/standby switchover is performed between FusionInsight management nodes and takes a period of time. During this period of time, FusionInsight Manager does not work, which does not affect the running of the cluster and services. However, the following problems may occur on iMaster NCE-Campus:
  • iMaster NCE-Campus cannot receive newly reported performance data, administrators cannot view performance data, and some monitoring data cannot be displayed on the iMaster NCE-Campus web UI.
  • Report data fails to be uploaded. Report statistics analysis data and terminal behavior statistics data cannot be displayed on the iMaster NCE-Campus web UI.
  • iMaster NCE-Campus cannot receive device login and logout logs, and administrators cannot view the logs.
  • iMaster NCE-Campus cannot receive newly reported device alarms, and administrators cannot view or clear alarms.
  • Administrators cannot upload device software packages or patches.
  • The device software fails to be upgraded.
  • The device configuration file fails to be uploaded during simplified deployment.
  • Configuration file management is unavailable.

    When configuring FusionInsight, you can set the switchover time between active/standby FusionInsight management nodes.

• To ensure the normal running of FusionInsight, ensure that the network packet loss rate is less than 0.5‰ or the node delay is within 5 ms. Otherwise, the following functions of iMaster NCE-Campus will be affected:
  • iMaster NCE-Campus cannot receive newly reported performance data, and administrators cannot view performance data.
  • iMaster NCE-Campus cannot receive device login and logout logs, and administrators cannot view the logs.
  • iMaster NCE-Campus cannot receive newly reported device alarms, and administrators cannot view or clear alarms.
  • Administrators cannot upload device software packages or patches.
  • The device software fails to be upgraded.
• To ensure service data reliability during running of iMaster NCE-Campus, ensure that both the primary and secondary GaussDB nodes work. If only one node is started, service data cannot be synchronized to the other node.
• To ensure the normal running of and access to iMaster NCE-Campus, ensure that the packet loss rate on a single link is less than 4%, the user-side network bandwidth is at least 4 Mbit/s, and the network delay is within 100 ms.

• During maintenance of iMaster NCE-Campus and devices, all time-related operations are performed based on the time of the iMaster NCE-Campus server. Ensure that the time of the iMaster NCE-Campus server is accurate.

Role Management

The role names under each tenant must be unique.

CLI Configuration Constraints and Precautions

• Pay attention to the following points when you use the CLI configuration function:
  1. The CLI configuration of a site may conflict with data configured on the GUI. To ensure that services run properly, you must use the CLI configuration function under the guidance of Huawei engineers.
  2. All the configuration data needs to be uniformly planned based on the networking.
  3. Currently, virtual interfaces (such as Eth-Trunk interfaces, loopback interfaces, and sub-interfaces) cannot be configured using the internet command in the CLI. After devices restart, configurations of virtual interfaces will be lost. Do not use the CLI to create interfaces on devices. Instead, perform operations on the web UI to create interfaces and modify interfaces using the CLI.
  4. The CLI delivers configurations to devices through commands, which is a supplementary to GUI-based configuration. The system does not check whether the commands to be delivered conflict with the configuration on the GUI. Therefore, you must check existing configurations on the GUI before delivering commands to devices. Otherwise, you may fail to achieve the expected result.
  5. If both the GUI- and CLI-based configurations have been delivered and you need to modify information on the GUI, you must check the commands to be delivered before modifying information on the GUI. Otherwise, you may fail to achieve the expected result.
  6. Passwords entered in the CLI configuration mode and imported to iMaster NCE-Campus are displayed in plain text.
  7. When you import commands using the CLI configuration mode, you are advised not to configure information on the GUI. This prevents configuration conflicts.
  8. In CLI configuration mode, do not deliver a command repeatedly. If you deliver a command repeatedly, iMaster NCE-Campus will not report an error.
  9. You can use the CLI configuration function to deliver commands multiple times. Only the commands delivered the last time take effect.
     1. Before you deliver commands again, compare them with the previously delivered commands to find unnecessary commands and commands that may cause conflicts.
     2. Click Delete in CLI to generate undo commands. Import the generated commands and deliver them to devices.
     3. Re-generate and deliver required commands.
  10. If CLI configuration commands fail to be delivered, iMaster NCE-Campus will report an error. However, iMaster NCE-Campus cannot display the delivery result (success or failure) of each command. If commands fail to be delivered, perform the following operations:
      1. Click Delete in CLI to generate undo commands. Import the generated commands and deliver them to devices.
      2. Check and modify incorrect parameters and re-generate commands. Import the generated commands and deliver them to devices.
  11. When you delete site information, iMaster NCE-Campus automatically deletes related information configured on the GUI, but does not delete the commands delivered through CLI configuration. You are advised to click Delete in CLI Configuration to generate undo commands and deliver them to devices before deleting site information.
  12. To modify the commands delivered to the device through the CLI, perform the following operations:
      • If the device cannot be restarted, perform the following operations:
        1. Deliver the relevant undo commands to the device through the CLI.
        2. Deliver new commands to the device using the CLI import function.
      • If the device can be restarted, perform the following operations without affecting services:
        1. Deliver the return command to the device using the CLI import function.
        2. Choose Design > Site Agile Deployment > Device Management from the main menu.
        3. Select the device to be reset, and click Reset to Deployment State.

           Devices will automatically restart after the deployment configurations are restored.

        4. After the device goes online, deliver new commands to the device using the CLI import function.