Maintenance and Monitoring (Management Plane)

Context

The power-on sequence is as follows: Turn on the power switch of the cabinet PDB, and then power on the devices from bottom to top based on the installation positions of the devices in the cabinet.

Procedure

1. Check the label on the power cable, find the power switch on the cabinet PDB that matches the power cable, and turn on the switch.
2. Plug in the 2288H V5 server.
3. Check the indicator status of the PSU to ensure that the server is powered on properly.

   Figure 3-3 shows the status indicator of the AC PSU.

   Figure 3-3 Status indicator of the AC PSU
   

   Table 3-4 describes the status indicator of the AC PSU.

   Table 3-4 Status description

   Name	Color	Status and Meaning
   PSU running status indicator	Green	On: The PSU is running properly. Blinking (0.5 Hz): The PSU is in the hibernation state and makes no output.
   	Red	On: The PSU is running inappropriately. NOTE: The PSU malfunctions possibly because: The PSU encounters an input overvoltage or undervoltage. The PSU encounters an output overvoltage or undervoltage. The PSU makes no output. A fan alarm or fault occurs.
   	Off	Off: There is no power supply.

Context

The power-on sequence is as follows: Turn on the power switch of the cabinet PDB, and then power on the devices from bottom to top based on the installation positions of the devices in the cabinet.

Procedure

Server

1. Check the label on the power cable, find the power switch on the cabinet PDB that matches the power cable, and turn on the switch.
2. Check the indicator status of the PSU to ensure that the server is powered on properly.

   For example: Figure 3-4 shows the status indicator of the AC PSU.

   Figure 3-4 Status indicator of the AC PSU
   

   Table 3-5 describes the status indicator of the AC PSU.

   Table 3-5 Status description

   Name	Color	Status and Meaning
   Indicator of PSU running	Green	Steady green: The power input and output are normal. Blinking green at 1 Hz: The input is normal, and the server is standby. The input is overvoltage or undervoltage. Blinking green at 4 Hz: The PSU firmware is being upgraded online.
   	Orange	Steady orange: The input is normal, but no power output is supplied due to overheat protection, overcurrent protection, short circuit protection, output overvoltage protection, or some component failures.
   	Off	No AC power is supplied.

Switch

1. Verify that the power cable of the switch is properly connected.
2. Check the label on the power cable, find the power switch on the cabinet PDB that matches the power cable, and turn on the switch.
3. Turn on the PSUs of the switch.
4. Check the switch after powering it on. Check the following items after powering on the switch:

   • Whether the sound of fans can be heard and air is exhausted from the air vent.

   • Whether the indicators on the switch, PSUs, and fan modules are in normal state. Normally, the SYS indicator on the switch and the STATUS indicators on the fan modules and PSUs are steady green.

Prerequisites

• The current PC can communicate properly with the server of the management plane and the services of the management plane are running properly.
• You have obtained the password for the current user.

Context

• The management plane provides only the admin user. This user has all permissions for all objects managed by the management plane. After you log in to the management plane for the first time, change the password as prompted to enhance security.
• Your PC's OS and browser must meet the following requirements:
  Table 3-6 Configuration requirements on the clients

  Configuration Item	Minimum Configuration Requirements
  Memory	4 GB or above
  Hard disk	Free hard disk: 8 GB or above
  OS	Windows 10 (32/64-bit)
  Browser	Recommended: Google Chrome 70 or later (32-bit or 64-bit) Firefox ESR 61.0.1 or later (32-bit or 64-bit) Compatible: Google Chrome 57 or later (32-bit or 64-bit) Firefox ESR 52 or later (32-bit or 64-bit)
  Resolution	1366 x 768 or higher; recommended resolution: 1920 x 1080

Procedure

1. Access the management plane at https://management plane IP address:18102, and click Enter.

   After iMaster NCE-Campus is enabled, you can only log in to the management plane using https://management plane IP address:18102.

   If iMaster NCE-Campus services are disabled, you can only use https://ER floating IP:31945 to log in to the management plane. If you want to enable iMaster NCE-Campus services, log in to the operating system as user sopuser. Switch ossadm user, and run the following commands to start the LVS service:

   . /opt/oss/manager/agent/bin/engr_profile.sh
   ipmc_adm -cmd restartapp -app LVSService

2. Enter the user name and password, and click Log In.
   • When you log in to the system in local mode, enter the user name admin and its password. To ensure system security, change your password upon first login and keep the new password safe.
   • When you log in to the management plane for the first time, the system prompts you to change the default password for the admin user. Perform operations as prompted. If the password for the admin user is lost, you can only restore the default password by reinstalling the management plane.
   • For security purposes, do not save your password in the browser.
   • If you enter the password for the admin user incorrectly five times consecutively within 10 minutes, the login IP address will be locked for 10 minutes.

Prerequisites

Power on the server.

Procedure

1. Use PuTTY to log in to the management node as user omm.
2. Run the following command to start the OMS:

   sh ${BIGDATA_HOME}/om-server/om/sbin/start-oms.sh

   If the following information is displayed, the OMS is successfully started:

   Warning: HA monitor has been running already. 
   start HA successfully.

3. Use PuTTY to log in to the other management node as user omm.
4. Run the following command to start the OMS:

   sh ${BIGDATA_HOME}/om-server/om/sbin/start-oms.sh

   If the following information is displayed, the OMS is successfully started:

   Warning: HA monitor has been running already. 
   start HA successfully.

5. In the address box of your browser, enter the FusionInsight Manager network address. The page can be displayed properly after the OMS automatically starts.
6. On the FusionInsight Manager home page, click next to the name of the cluster to be operated and select Start.

   In the displayed dialog box, click OK to start the cluster. Operation succeeded is displayed. Click Finish. The service starts successfully.

Prerequisites

• The current PC can communicate properly with service plane and the services of service plane are running properly.
• You have obtained the user name and password for login.

Context

• The OS and browser of your PC must meet the following requirements.
  Table 3-10 Configuration requirements

  Software Type	Requirements
  OS	Windows Server 2008, Windows 10 or later
  Browser	Google Chrome 57 or later
  Resolution	Recommended resolution: 1366 x 768 (px) or higher. Optimal resolution: 1920 x 1080 (px)

• The service plane provides the default admin user as the system administrator that has permissions on all resources. To ensure security of the service plane, change the password periodically and keep the new password secure. If the admin user enters incorrect passwords five times consecutively within 10 minutes, the login IP address will be locked for 10 minutes.

• If three accounts using the same IP address are locked within a 10-minute period, this IP address will be locked for 30 minutes.
• If the login of an IP address meets the IP address lockout conditions specified on the Account Policy page, this IP address will be locked.
• If the login of a local account meets the account lockout conditions specified on the Account Policy page, this account will be locked for 30 minutes by default.
• All users can log in to the system again after their accounts are automatically unlocked. Local users can also contact security administrators to unlock their accounts to log in again.

Procedure

1. Log in to the service plane at https://the service plane IP address:18008.
2. On the login page, enter the username and password.
   • If you have changed the initial password after login, keep the new password secure. If you forget the password of the admin user, you can reset the password only by reinstalling the service plane.
   • For security purpose, do not set the browser to remember the password.

3. Click Log In.

High Risk Operation

Contact Huawei technical support if you need to perform the following operations:

• Restart FusionInsight service components. This operation will interrupt controller services and cause data loss.
• Restart the FusionInsight OMS component. If this operation is performed, the FusionInsight cluster cannot be managed or maintained within a certain period of time.
• Stop FusionInsight service components. This operation is forbidden. Otherwise, controller services will be interrupted, causing data loss and feature failures.
• Stop Spark statistics collection tasks. This operation will interrupt controller services and cause data loss.
• Change the NTP, time, and time zone configurations of the FusionInsight cluster. If this operation is performed, the FusionInsight cluster may fail and service data may be lost.

Procedure

1. Log in to FusionInsight Manager.
2. On the FusionInsight Manager home page, click next to the name of the cluster to be operated and select Stop.
3. In the displayed window, enter the password of the current login administrator user and click OK.
4. In the displayed dialog box, click OK.

   After the system displays "Operation succeeded", click Finish. The cluster is successfully stopped.

5. Use PuTTY to log in to the active management node as user omm.
6. Run the following command to stop the active OMS:

   sh ${BIGDATA_HOME}/om-server/om/sbin/stop-oms.sh

   If the following information is displayed, the OMS is successfully stopped:

   stop HA successfully.

   The active/standby management node failover takes about three minutes.

7. Use PuTTY to log in to the standby management node as user omm.
8. Run the following command to stop the standby OMS:

   sh ${BIGDATA_HOME}/Bigdata/om-server/om/sbin/stop-oms.sh

   If the following information is displayed, the OMS is successfully stopped:

   stop HA successfully.

Prerequisites

The services and databases have been stopped. For details, see the related section in Stopping iMaster NCE-Campus.

Precautions

• If you run the shutdown command to shut down the OS, the server is automatically powered off. You do not need to manually power off the server.
• The power-off sequence is as follows: power off the devices from top to bottom based on the installation positions of the devices in the cabinet, and then turn off the power switch of the cabinet PDB.

Procedure

1. Log in to the iBMC web UI. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
2. Choose Power > Power Control.
3. On the Power Control page, click Power off. When a power-off message is displayed, click Yes.

   Forcible power-off may damage user programs or data that is not saved. Exercise caution when performing this operation.

Prerequisites

The services and databases have been stopped. For details, see the related section in Stopping iMaster NCE-Campus.

Precautions

• If you run the shutdown command to shut down the OS, the server is automatically powered off. You do not need to manually power off the server.
• The power-off sequence is as follows: power off the devices from top to bottom based on the installation positions of the devices in the cabinet, and then turn off the power switch of the cabinet PDB.

Context

Procedure

• If the iBMC version of the delivered device is 3.01.0.0 or later, or 5.00 or later, perform the following steps.
  1. Log in to the iBMC web UI. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. Choose System > Power.
  3. Click Power Control, on the Power Control page, click Power off. When a power-off message is displayed, click OK.

     Forcible power-off may damage user programs or data that is not saved. Exercise caution when performing this operation.

• If the iBMC version of the delivered device is earlier than 5.00, perform the following steps.
  1. Log in to the iBMC web UI. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. Choose Power > Power Control.
  3. On the Power Control page, click Power off. When a power-off message is displayed, click Yes.

     Forcible power-off may damage user programs or data that is not saved. Exercise caution when performing this operation.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Context

The management plane refreshes the status of nodes, services, and databases displayed on the page every 30 seconds.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. In the upper right corner of the page, check whether any resource in Nodes, Services, Relational Databases, and Redis Databases is abnormal.

   The number in red indicates the number of abnormal resources.

   Figure 3-7 Monitoring products
   
   • If the number of abnormal resources is 0, all resources of the product are normal.
   • If the number of abnormal resources is not 0, there are abnormal resources in the product.

     Click a number of abnormal resources to view details on the tab page for the resource type.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Precautions

For a service deployed in active/standby mode, the service runs only on the active node.

Context

The management plane periodically monitors resources of the system. Table 3-14 lists the monitoring intervals. The status of monitored objects on the page is refreshed every 30 seconds.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. On the Nodes tab page, view the usage of the CPU, virtual memory, physical memory, and disk partition. Refer to Table 3-15 to check the resource statuses. Alternatively, on the Nodes tab page, click a node name. On the page for node details, view the disk partition usage and the resource statuses of processes on the node.
   Figure 3-8 Monitoring nodes
   
   Table 3-15 Node resource status

   Object	State	Description	Measures
   Connection Status	Normal	The connection between the node and the management plane is normal.	N/A
   	Disconnected	The connection between the node and the management plane is abnormal.	Click the abnormal node and view the space usage and process status of each disk in the node on the details page. An alarm is reported if the node status is abnormal. Rectify the fault based on the alarm information.
   Database Status	--	The node does not have a database.	N/A
   	Partially Running	Some database instances on the node are not running.	An alarm is reported if the database status is abnormal. Rectify the fault based on the alarm information.
   	Not Running	All database instances on the node are stopped.	Some maintenance operations require that the database is not running. Determine whether the database is abnormal based on site requirements.
   	Running	The database instances on the node are running properly.	N/A
   	Unknown	The system cannot detect the database instance status on the node.	Collect related information and contact Huawei technical support.
   	Starting	All database instances on the node are being started.	If the service is in this state for a long time, contact Huawei technical support.
   	Stopping	All database instances on the node are being stopped.
   Service Status	Uninstalled	The node service is not installed.	Collect related information and contact Huawei technical support.
   	--	The node does not provide services.	N/A
   	Partially Running	Some processes on the node are not running.	On the Nodes tab page, click the node name. On the node details page, view the processes that are not running and determine whether the processes are abnormal based on site requirements.
   	Not Running	All services on the node are stopped.	Some maintenance operations require that the service is not running. Determine whether the service is abnormal based on site requirements.
   	Running	All services on the node are running.	N/A
   	Unknown	The system cannot detect the service status on the node.	An alarm is reported if the service status is abnormal. Rectify the fault based on the alarm information.
   	Faulty	Some services on the node are faulty.
   	Starting	All services on the node are being started.	The startup or stopping duration of a service does not exceed 1 minute. If the service is in this state for a long time, contact Huawei technical support.
   	Stopping	All services on the node are being stopped.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Context

The management plane monitors services of the system every 30 seconds. The status displayed on the page is refreshed every 30 seconds.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. Click the Services tab page and refer to Table 3-16 to check the service status. Alternatively, click the desired service instance name. On the page for service details, view the status of processes and other resources of the service.
   Figure 3-9 Monitoring services
   
   Table 3-16 Service status

   State	Description	Measures
   Partially Running	Some processes of the service are not running.	Click the name of the corresponding service instance. On the page for service details, view the processes that are not running, and determine whether the processes are abnormal based on site requirements.
   Not Running	All processes of the service are stopped.	Some maintenance operations require that the service is not running. Therefore, you need to determine whether the service is abnormal based on site requirements.
   Running	All processes of the service are running.	N/A
   Unknown	The system cannot detect the status of processes of the service.	An alarm is reported if the service status is abnormal. Rectify the fault based on the alarm information.
   Faulty	Some processes of the service are faulty.	An alarm is reported if the service status is abnormal. Rectify the fault based on the alarm information.
   Starting	All processes of the service are being started.	The startup or stopping duration of a service does not exceed 1 minute. If the service is in this state for a long time, contact Huawei technical support.
   Stopping	All processes of the service are being stopped.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Context

The management plane monitors processes of the system every 30 seconds. The status displayed on the page is refreshed every 30 seconds.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. On the Processes tab page, check the process status based on Table 3-17.
   Figure 3-10 Monitoring processes
   
   Table 3-17 Process status

   State	Description	Measures
   Not Running	The process is not running.	Some maintenance operations require that the processes are not running. Determine whether a process is abnormal based on site requirements. NOTE: For a process deployed in active/standby mode, the process runs only on the active node. If Service Status of the node whose process is not running is Normal, the process is normal.
   Running	The process is running.	N/A
   Unknown	The system cannot detect the process status.	Collect related information and contact Huawei technical support.
   Faulty	The process is faulty.	An alarm is reported if the process is faulty. Rectify the fault based on the alarm information.
   Starting	The process is being started.	If the service is in this state for a long time, contact Huawei technical support.
   Stopping	The process is being stopped.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Context

• The management plane monitors databases of the system every 60 seconds. The status displayed on the page is refreshed every 30 seconds.
• A relational database is created on the basis of a relational model for storing persistent data, such as the GaussDB 100 database. The management plane monitors the usage of the relational databases. This helps you to identify and rectify the insufficiency of the database space in a timely manner.
• A Redis database is a high-performance key-value database that stores cached status-related data. The management plane monitors the memory usage of the Redis databases so that you can identify and rectify insufficient memory space in a timely manner.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. Click the Relational Databases or Redis Databases tab page. Refer to Table 3-18 and Table 3-19 to check the database status.
   Figure 3-11 Monitoring relational databases
   
   Figure 3-12 Monitoring Redis databases
   
   Table 3-18 Database status table

   State	Description	Measures
   Not Running	The database is not running.	An alarm is reported if the database status is abnormal. Rectify the fault based on the alarm information.
   Unknown	The system cannot detect the database status.
   Running	The database on the node is running properly.	N/A

   Table 3-19 Database instance replication status

   State	Description	Measures
   Normal	The replication between the master and slave database instances is normal.	N/A
   Abnormal	The replication between the master and slave database instances is abnormal.	An alarm is reported if the database instance replication status is abnormal. Rectify the fault based on the alarm information.
   Full Synchronizing	The slave database instance is rebuilt, and all data of the master database instance is being forcibly synchronized to the slave database instance.	N/A
   --	The database instance is a single instance and does not have a master/slave relationship.	N/A

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Precautions

All processes of a product are displayed on the Processes tab page. Disabling a process may cause corresponding functions to become abnormal. Select processes to be disabled based on site requirements.

In a DR scenario, configure the process startup type only at the primary site, and the configuration will be synchronized to the secondary site.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product.
3. On the Processes tab page, select the processes and click a startup type based on Table 3-20. Perform operations as prompted.
   Table 3-20 Operation description

   Startup Type	Description
   Manual	The process does not start with the OS and can only be started manually.
   Automatic	The process automatically starts with the OS.
   Disabled	The process cannot be started.

   If the process startup type is changed to Manual or Automatic, the process status does not change. If the startup type is changed to Disabled, the process is stopped.

4. (Optional) To change the running status of processes, select the processes to be started or stopped, and click Start or Stop as required above the process list. Perform operations as prompted.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Context

Table 3-21 lists the default thresholds and resource objects that can be configured.

X indicates the value of Alarm Generation Threshold, Y indicates the value of Alarm Clearance Threshold, and N indicates the value of Number of Times Overloaded. Y must be less than X.

Precautions

In a DR scenario, the node and database monitoring thresholds of nodes of a product or NCE-OMP need to be modified at both the primary and secondary sites, and the monitoring thresholds must be consistent between the two sites. If they are inconsistent, alarms may be generated only at one site.

Procedure

1. On the management plane, choose Product > System Monitoring from the main menu.
2. In the upper left corner of the System Monitoring page, move the pointer to and select the product or NCE-OMP.
3. Click the tab where the resource object resides.
4. Click on the right of the page and set parameters.

Concepts

Table 3-22 lists the concepts related to backup and restore to give you a better understanding of these functions.

Principles

As shown in Figure 3-13, after the backup server is configured, you can back up the data of products and applications. The backup data is transferred to the backup server through a transfer protocol; for example, Secure File Transfer Protocol (SFTP). Different types of data can be backed up independently of one another.

If the data of the management plane or the service plane is missing or damaged, you can restore the corresponding data. Before restoring data of a certain type, ensure that its lower-layer data is normal. For example, before restoring the product data, ensure that the application data are normal. Figure 3-14 shows the dependency.

Figure 3-13 Principle of backup and restore

Advantages

• Flexibility and ease of use

  Function	Description
  Multi-dimensional backup	Data backup of instances, nodes, and products is supported.
  Multi-dimensional restoration	Data restoration of instances, nodes, and products is supported.
  Scheduled backup	Periodically scheduled data backup of products and the management plane is supported. Manual operations are not required.
  Easy operations	On the web client of the management plane, the backup and restore operations are easy, with clear guidance provided.

• Security and reliability

  Function	Description
  Secure transfer of backup data	Data is transferred over SFTP, and security measures are provided to ensure data security; for example, digital signatures are added to the backup data.
  Real-time task status display	The details of backup and restore tasks is displayed in real time in the task list.

• High performance

  Function	Description
  Concurrent backup	Backup tasks of different products can be executed at the same time.
  Time-specific restoration	Data can be restored to a specific time point.

Function Description

As shown in Figure 3-14, application, and data of a product and the management plane can be backed up and restored. Before restoring upper-layer data, ensure that its lower-layer data is normal. For example, before restoring the product data, ensure that the application data is normal. When you restore the database application or product application, the two types of restoration are independent of each other.

Figure 3-14 Backup and restore

Configuration Requirements

Local Default Backup Server

Distributed:

Third-party Server

If a third-party server is used as the backup server:

• You are advised to periodically clear the product data, and application data. Retain at least one latest backup file for each data type.
• NAT cannot be configured between the third-party backup server and the management plane.

Backup server requirements

Prerequisites

• You have logged in to the management plane. For details, see Logging In to the Management Plane.
• You have planned and configured the backup server by following Backup Server Requirements. In addition, you have obtained the IP address of the backup server, the user name and password for transferring backup files using SFTP, and the storage path for backup files.

  In the distributed scenario, If no third-party backup server meets the requirements (for example, the third-party backup server cannot communicate with all iMaster NCE-Campus nodes, and data cannot be automatically backed up to the third-party backup server), you are advised to manually copy data from the local backup node to a third-party storage medium periodically to prevent data loss due to hard disk damage.

Context

• For details about the backup paths, see Table 3-26 and Table 3-27. Do not delete the backup files in the paths. Otherwise, no backup files are available for restoration.
  Table 3-26 Backup path of the OMP node

  Data	Path	Example Path on the Local Default Backup Server
  Applications and Data of the Management Plane	/root directory of the backup server user/path specified in the backup parameters/management/management/timestamp/node name	Distributed: /opt/backup/ftpboot/backup/management/management/20191119070005090/Management1 Compact: /opt/backup/ftpboot/backup/management/management/20191129070010333/Management

  Table 3-27 Backup file path of the service nodes

  Data	Path	Example Path on the Local Default Backup Server
  Database application	/root directory of the backup server user/path specified in the backup parameters/product name/static/timestamp/node name/DB	Distributed: /opt/backup/ftpboot/backup/NCECAMPUS/static/20191118230000546/DB_01/DB Compact: /opt/backup/ftpboot/backup/NCECAMPUS/static/20191202230001138/Common_Service/DB
  Product application	/root directory of the backup server user/path specified in the backup parameters/product name/static/timestamp/node name/APP	Distributed: /opt/backup/ftpboot/backup/NCECAMPUS/static/20191118232333974/NMS_01/APP Compact: /opt/backup/ftpboot/backup/NCECAMPUS/static/20191130230005926/Common_Service/APP
  Product data	/root directory of the backup server user/path specified in the backup parameters/product name/dynamic	Distributed: /opt/backup/ftpboot/backup/NCECAMPUS/dynamic/20191120220006667 Compact: /opt/backup/ftpboot/backup/NCECAMPUS/dynamic/20191203112551567

• A maximum of 10 backup servers can be added to the management plane, and the same backup files are saved on each backup server. When a backup server is abnormal, other backup servers can still provide backup files for restoration.
• When a backup server is added, the management plane authenticates the SFTP fingerprint between the backup server and the node to be backed up. If the authentication is not performed, iMaster NCE-Campus automatically configures fingerprint authentication for the backup server.
• Modifying or deleting a backup server does not erase data on it.

Precautions

• When the backup server transfers data over SFTP, the system performs SFTP fingerprint authentication when you verify the connectivity to the server. You can verify the SFTP fingerprint authentication information to improve the data security of the management plane. For details about how to obtain SFTP fingerprint authentication information, see How Do I Query SFTP Fingerprint Authentication Information?
• If the parameters of the backup server are changed, update the parameters in the Backup Server area and back up the application and data of the management plane again. Otherwise, the management plane cannot be backed up or restored. For details, see Manually Backing Up the Application and Data of the Management Plane.

Procedure

1. On the management plane, choose Backup and Restore > Configuration > Configure Backup Parameters from the main menu.
2. Set backup parameters.
   1. Configure the backup server parameters.
      1. In the Backup Server area, set parameters as follows Table 3-28.
         Table 3-28 Backup server parameters

         Parameter	Value
         Transmission Mode	SFTP.
         Backup Server IP Address	OMP_02 node: The Inter-node Communication IP Address. Third-party backup server: IP address instead of the floating IP address for transferring data between the backup server and all nodes through SFTP.
         Port	OMP_02 node: Port number of the backup server. The default value is 22, and the value range is 1 to 65535. Third-party backup server: Port number of the server, and the value range is 1 to 65535.
         Username	OMP_02 node: ftpuser. Third-party backup server: user with the SFTP permission.
         Password	OMP_02 node: password for the ftpuser user. Third-party backup server: password for the user with the SFTP permission.
         Backup Path	OMP_02 node: /opt/backup/ftpboot/backup. After the initial installation and commissioning, the data that is manually backed up for the first time is stored in /opt/backup/ftpboot/initdatabackup. Third-party backup server: SFTP shared directory for storing backup files. NOTE: The backup path must be a relative path under the default SFTP user directory. For example, if the OMP_02 node is used as the backup server by default, you only need to enter backup. The backup files are stored in the /opt/backup/ftpboot/backup directory on the OMP_02 node. Before configuring backup parameters, create a backup path on the backup server. For details, see How Do I Create a Backup Path for a Backup Server?

      2. Click .
      3. If the management plane detects that there are nodes where SFTP fingerprint authentication has not been performed, perform the operations as required:
         • (Recommended) If you click OK in the Warning dialog box, the management plane automatically performs the SFTP fingerprint authentication on the node.
         • If you click Cancel in the Warning dialog box, log in to each node where the SFTP fingerprint authentication has not been performed and manually perform authentication. For details, see How Do I Manually Authenticate the SFTP Fingerprint?

   2. Perform the following operations to change the default storage thresholds for the data backup files of products as required.

      On the Storage Strategy for the Product Data Backup Files area, set thresholds based on Table 3-29.

      Table 3-29 Threshold settings for backup files

      Task		Procedure
      Modify the storage thresholds for products.	Modify the thresholds one by one or in batches.	Select the products for which you want to configure the backup file storage threshold. Click Modify Product Threshold. In the dialog box that is displayed, configure the number of backup files and click Save.

   3. When the default storage threshold for the management plane backup files cannot meet actual requirements, perform the following operations to modify the storage strategy of the NCE-OMP backup files:

      1. In the Storage Strategy for the NCE-OMP Backup Files area, configure the number of back file copies.
      2. Click Save.

Follow-up Procedure

• If parameters on the backup server have changed, set the backup parameters again.
• After the password for the backup server is changed, back up the management plane again. For details, see Manually Backing Up the Application and Data of the Management Plane.

Typical Network Configuration Scenarios and Policies

Table 3-38 lists only the network configuration policies of each node (such as the hostname, network interface, IP address, and route). Perform other operations based on site requirements.

Context

Set the NIC usage according to the service scenario. In addition to the usages listed in the following tables, the following usages can be allocated to each IP address:

• Southbond2–Southbond10: If multiple southbound IP addresses of a single node need to be isolated on the live network, allocate different NIC usages for each southbound IP address, for example, Southbound and Southbound2.
• Northbond2–Northbond3: If multiple northbound IP addresses of a single node need to be isolated on the live network, allocate different NIC usages for each northbound IP address, for example, Northbound and Northbound2.
• Multiserver-Multiserver3: If the current floating IP address is abnormal, replace the floating IP address with the Multiserver IP address and log in to the web client.
  Table 3-39 Usage of network interfaces in the Distributed scenario

  Network Plane	NIC	NIC Usage	Involved Node	NOTE
  Management network	eth4	HardwareMgr	OMP	The NIC is used to monitor hardware alarms on iMaster NCE-Campus The eth4 NIC of the OMP node is used by default.
  Inter-node communication network	eth0	MANAGEIP	All nodes	The NIC is used by the OMP node to manage other nodes and for communication between service nodes.
  		Maintenance	Service nodes
  DR network	eth0:1	ACCESSIP	-	The NIC is used for communication between primary and secondary sites.
  Service network (The northbound and southbound networks are not isolated.)	eth2	Service, Northbound and access-external	NMS	The NIC is used for communication between the service node and OSS or used to log in to the OS.
  		floatingbase	Common_Service	The NIC is used to configure the fixed IP address of the floating IP address on the Common_Service node.
  		Northbound, external-access	Common_Service	The NIC is used to log in to the web client of the service plane with the floating IP address of the Common_Service node.
  		WEBMGMTIP	OMP	The NIC is used to log in to the web client of the management plane through the OMP node.
  		Southbound	TController_Driver01 TController_Driver02	The NIC is used for communication between the service node and southbound devices.
  Service network (The southbound and northbound networks are isolated, and the Manager and Controller are not isolated.)	eth3	Service, Northbound and access-external	For all nodes	The NIC is used for communication between the service node and OSS or used to log in to the OS.
  		floatingbase	Common_Service01 Common_Service02	The NIC is used to configure the fixed IP address of the floating IP address on the Common_Service node.
  		Northbound, external-access	Common_Service01 Common_Service02	The NIC is used to log in to the web client of the service plane with the floating IP address of the Common_Service node.
  		WEBMGMTIP	OMP	The NIC is used to log in to the web client of the management plane through the OMP node.
  	eth2	Southbound	TController_Driver01–TController_Driver02	The NIC is used for communication between the service node and southbound devices of the Controller.
  	eth5	Southbound	NMS	The NIC is used for communication between the service node and southbound devices of the Manager.
  Service network (The southbound and northbound networks are isolated, and the Manager and Controller are isolated.)	eth3	Service, Northbound and access-external	All nodes	The NIC is used for communication between the service node and OSS or used to log in to the OS.
  		floatingbase	Common_Service01 Common_Service02	The NIC is used to configure the fixed IP address of the floating IP address on the Common_Service node.
  		Northbound, external-access	Common_Service01 Common_Service02	The NIC is used to log in to the web client of the service plane with the floating IP address of the Common_Service node.
  		WEBMGMTIP	OMP	The NIC is used to log in to the web client of the management plane through the OMP node.
  	eth2	Southbound	TController_Driver01–TController_Driver02	The NIC is used for communication between the service node and southbound devices of the Controller.
  	eth5	Southbound	NMS	The NIC is used for communication between the service node and southbound devices of the Manager.
  Service network (IP+Optical)	eth3	Service, Northbound and access-external	All nodes	The NIC is used for communication between the service node and OSS or used to log in to the OS.
  		floatingbase	Common_Service01 Common_Service02	The NIC is used to configure the fixed IP address of the floating IP address on the Common_Service node.
  		Northbound, external-access	Common_Service01 Common_Service02	The NIC is used to log in to the web client of the service plane with the floating IP address of the Common_Service node.
  		WEBMGMTIP	OMP	The NIC is used to log in to the web client of the management plane through the OMP node.
  	eth2	Southbound	TController_Driver01 TController_Driver02	For the service nodes that communicate with the IP domain Controller southbound devices.
  	eth5	Southbound	NMS	For the service nodes that communicate with IP domain Manager southbound devices.
  	eth2	Southbound	TController_Driver01 TController_Driver02	For the service nodes that communicate with the transport domain Controller southbound devices.
  	eth5	Southbound	NMS	For the service nodes that communicate with the transport Manager southbound devices.

  Table 3-40 IP Usage Description

  IP Usage	Description	Usage Description
  HDmgmtbound	IP address of the hardware management network.	Floating IP address of the hardware management network, which is used to receive hardware alarms.
  HDmgmtFloatingBase	Basic fixed IP address of the floating IP address of the hardware management network.	Fixed IP address of the hardware management network.
  HAdisasterbound	Heartbeat IP address of the DR system.	Heartbeat IP address of the remote HA system, which is used to check whether the peer is running properly.
  PCEPdbs	Floating IP address of the DBS service cluster.	Floating IP address of the FusionInsight HD database.
  PCEPweb	Floating IP address of the WEB service cluster.	Floating IP address for accessing the FusionInsight HD WebUI.
  PCEPoms	Floating IP address of the OMS service cluster.	Floating IP address of the FusionInsight HD O&M management plane.
  JHS	Floating IP address of the JHS service cluster.	Floating IP address of the JHS service cluster.
  lvs-virtual-ip	Virtual IP address of the LVS service cluster.	Floating IP address of the interconnected LVS used by ODAE. (It is available in input.json.)
  PCEPlvs	Virtual IP address of the LVS service cluster.	Floating IP address of the interconnected LVS used by ODAE. (It is available on the ROC website and assigned to lvs-virtual-ip.)
  VimBound	Southbound IP address of the Vim service.	IP address for the Vim service to interconnect with the cloud service (such as FusionSphere and FusionStage) at the IaaS layer. VimBound on LCM indicates a floating IP address.
  Service	IP address of the platform service application.	External IP address of the service plane.
  INNER_ACCESS	Internal access.	Internal communication IP address of the service plane.
  Analyzer_SERVER_IP	Analyzer service IP address.	Floating IP address (eth0) for Analyzer node disaster recovery (active/standby).
  NMS_SERVER_IP	NMS service IP address.	Local IP address used by the Manager microservice.
  Southbound	IP address for southbound network communication.	IP address 1 for southbound access.
  Southbound2BaseIP	Basic fixed IP address of the floating IP address of southbound network 2.	Basic fixed IP address 2 for southbound access.
  BGPSouthBound	Floating IP address of the controller service southbound network.	Southbound floating IP address of IP Controller, which is used for communicating with devices.
  Southbound	IP address for southbound network communication.	IP address 1 for southbound access.
  LVS-VIP2	Floating IP address of LVS southbound network 2.	Southbound floating IP address of the LVS (load balancing) for connecting to NEs. This IP address is not used currently.
  LVS-VIP	Floating IP address of the LVS southbound network.	Southbound floating IP address of the LVS (load balancing) for connecting to NEs. (eth5)
  SouthboundBaseIP	Basic fixed IP address of the floating IP address of the southbound network.	Basic fixed IP address 1 for southbound access.
  Northbound	IP address for northbound network communication.	IP address 1 for northbound access.
  NorthboundBaseIP	Basic fixed IP address of the floating IP address of the northbound network.	Basic fixed IP address 1 for northbound access.
  AnalyzerCollector_SERVER_IP	IP address of the Analyzer collection service.	Floating IP address (eth0) for collector node disaster recovery (active/standby).
  ommha_heartbeat	Heartbeat IP address of the ommha service.	The local primary and secondary sites need to use OMM HA. This IP address is the heartbeat IP address of the OMM HA service between the primary and secondary sites.
  Data_Replication_IP	Data replication IP address	IP address used for data replication between the primary and secondary sites in a DR scenario.
  DRHEARTBEAT	Data replication/heartbeat IP address	Used for data replication and heartbeat detection between the primary and secondary sites in the DR scenario.
  globalBackendLBFloatIP	Floating IP address for inter-system communication	Used for internal services communication and services communication between the primary and secondary sites.

Prerequisites

• You have logged in to the management plane. For details, see Logging In to the Management Plane.
• The network interface to be added to the management plane exists on the VM.
• In a DR scenario, the DR relationship must be deleted as follows before you configure the network interfaces:
  • For a product node, the primary and secondary site products must be separated. For details, see Separating the Primary and Secondary Site Products.
  • If the product node and the management node are the same node, the DR relationship between the primary and secondary sites must be deleted. For details, see Deleting the DR System. For details about how to check that the management node and product node are the same node, see How Do I Determine the Deployment Mode of Nodes?
  • For the management node, the DR relationship between the primary and secondary sites must be deleted. For details, see Deleting the DR System.

Precautions

• In a Distributed scenario, after iMaster NCE-Campus is installed, you need to add the eth4 network ports on the OMP_01 and OMP_02 nodes on the management network so that the management plane can manage the IP address of the hardware management network of the OMP nodes.
• When a network interface is deleted, its IP address will be deleted, and the network interface will be removed from the management plane. However, the network interface on the VM will not be deleted.
• If MCZKService is deployed on the OMP node, MCZKService will be automatically restarted during the network interface configuration.
  • During the restart of MCZKService, the services monitored by MCZKService are also restarted and become temporarily unavailable. After the restart, the services become available again.
  • During the restart, the service plane may report the Failed to connect ZooKeeper alarm because MCZKService is stopped, which is normal. After the restart, the service plane automatically clears this alarm.
• If you configure the network interface of the management node, the system automatically restarts OMMHAService on all nodes. If you configure the network interface of a product node, the system automatically restarts OMMHAService on all nodes of the product. During the restart of OMMHAService, the services monitored by OMMHAService are also restarted and become unavailable temporarily. After the restart, the services become available again. If OMMHAService is not deployed on the management node or the product node, restart is not involved.
• If the product services are not in the Running state, after a network interface is added or deleted, the product services will be automatically started.

  If a network interface without IP address is added or deleted, the system does not need to start product services.

• In a DR scenario, if you configure a network interface of the secondary site, do not select Automatically start the product services after the configuration in the Warning dialog box.

• In a DR scenario, configure network interfaces at the primary site and then perform the same configurations at the secondary site to ensure that the network interface configurations at the primary and secondary sites are consistent.
• If any OMP node is faulty, restore the node first. Otherwise, network interfaces cannot be configured. For details, see "Management Node Faults" in Troubleshooting Guide.

• After a network interface is configured, historical backup files of the application and data of the management plane, OS of the OMP node, OS of the product nodes, database applications, product applications, and product data will become invalid. A scheduled task for backing up the application and data of the management plane will be automatically created.

  Backup operations occupy system resources. On the management plane choose Backup and Restore > Configuration > Configure Scheduled Backup Task from the main menu to modify the start time of the scheduled backup task, if the execution time of the task is in busy hours.

Procedure

1. On the management plane, choose Maintenance > Network Configuration > Configure NIC from the main menu.
2. On the Configure NIC page, perform operations as prompted.
   • If you want to perform other configuration operations that need to restart product services after configuring the network interfaces, do not select Automatically start the product services after the configuration in the Warning dialog box. In this case, after the configuration, the product services will not be automatically started, preventing the product services from being restarted for several times.
   • In a DR scenario, if you are configuring the network interfaces at the secondary site, do not select Automatically start the product services after the configuration in the Warning dialog box, preventing the product services of the secondary site from being restarted and causing the product to become dual-active.

3. In a DR scenario, re-establish the DR relationship as follows after configuring network interfaces:
   • After configuring the network interface of a product node, connect the primary and secondary site products. For details, see Connecting the Primary and Secondary Site Products.
   • If the product node and the management node are the same node, after configuring the network interface of the node, re-establish the DR relationship between the primary and secondary sites. For details, see Configuring the DR System.
   • After configuring the network interface of the management node, re-establish the DR relationship between the primary and secondary sites. For details, see Configuring the DR System.

Prerequisites

• You have obtained the destination network, subnet mask, and gateway of the route.
• You have logged in to the management plane. For details, see Logging In to the Management Plane.

Precautions

• Do not delete the route used for connecting to the management when deleting a route of the management node. Otherwise, you cannot log in to the management plane.
• If there are two routes with the same destination address, you need to manually delete the unnecessary route on the Configure Route page. Otherwise, the network connection to the destination address is abnormal.

Procedure

1. On the management plane, choose Maintenance> Network Configuration > Configure Route from the main menu.
2. In the Select node and query route area, select the nodes with routes to be configured.
3. Click Query.
4. In the Configure route area, modify, add, or delete routes for the selected nodes. For details, see Table 3-41.
   Table 3-41 Configuring routes

   Task	Operation
   Modifying routes	If NIC Name is -, the node has the default route. If the default route exists, you can modify it but cannot add other default routes for the node. IP addresses of the same protocol (IPv4 or IPv6) have only one default route. Select and modify a route. To modify the default route, select the corresponding records whose NIC Name is -, and configure Gateway/Next Hop. To modify a non-default route, select the desired network interface from the NIC Name drop-down list based on the planning information, and configure Destination Network, Subnet Mask/Prefix Length, and Gateway/Next Hop. Click Apply. NOTE: Clicking Reset will clear all unsaved configurations on the page and will restore the configurations to the state before you select nodes and query routes. In the Confirm dialog box, click Yes. The related task is created successfully. Click Task List to view the task execution status. If the task execution fails, rectify the fault based on the task details.
   Adding routes	If no default route is available or new routes need to be added, perform the following operations: Click Add Route. Select nodes with routes to be added. To add a default route, select Default Route and configure Gateway/Next Hop. To add a non-default route, select the desired network interface from the NIC Name drop-down list, and configure Destination Network, Subnet Mask/Prefix Length, and Gateway/Next Hop. Click OK. In the Confirm dialog box, click Yes. The related task is created successfully. Click Task List to view the task execution status. If the task execution fails, rectify the fault based on the task details.
   Deleting routes	If routes are no longer necessary, delete them to save resources. Select the desired routes and delete them. To delete default routes, select the desired routes, and click Delete Route. To delete non-default routes, select one or more desired routes and click Delete Route. In the Warning dialog box, click OK. The related task is created successfully. Click Task List to view the task execution status. If the task execution fails, rectify the fault based on the task details. NOTE: Do not delete the route used for connecting to the management plane when deleting a route of the management node. Otherwise, you cannot log in to the management plane.

Prerequisites

• You have logged in to the management plane. For details, see Logging In to the Management Plane.
• Databases of the product with floating IP address to be changed are running properly. For details, see Monitoring Databases.
• A floating IP address can be configured only for nodes of the same type. For details about how to check the node type, see Monitoring Databases.
• In a DR scenario, the DR relationship must be deleted as follows before you configure the floating IP address:
  • For a product node, the primary and secondary site products must be separated. For details, see Separating the Primary and Secondary Site Products.
  • If the product node and the management node are the same node, the DR relationship between the primary and secondary sites must be deleted. For details, see Deleting the DR System. For details about how to check that the management node and product node are the same node, see How Do I Determine the Deployment Mode of Nodes?
  • For the management node, the primary and secondary site products must be deleted. For details, see Deleting the DR System.

Precautions

• The floating IP address on which services depend has been configured to be undeletable to prevent service exceptions caused by misoperations. If you select the floating IP address, the Delete button is dimmed, indicating that the floating IP address cannot be deleted.
• After you change the floating IP address, the product services will be automatically restarted by default.
• If MCZKService is deployed on the OMP node, MCZKService will be automatically restarted during the floating IP address configuration. During the restart, the service plane may report the Failed to connect ZooKeeper alarm because MCZKService is stopped, which is normal. After the restart, the service plane automatically clears this alarm.
• If the new and old floating IP addresses belong to different network segments, the fixed IP address need to be changed accordingly to ensure that the floating IP address and the fixed IP address are in the same network segment. There is no requirement on the change sequence.
• If any OMP node is faulty, restore the node first. Otherwise, floating IP addresses cannot be configured. For details, see "Management Node Faults" in Troubleshooting Guide.
• After a floating IP address is configured, historical backup files of the application and data of the management plane, OS of the OMP node, OS of the product nodes, database applications, product applications, and product data will become invalid. A scheduled task for backing up the application and data of the management plane will be automatically created.

  Backup operations occupy system resources. On the management plane, choose Backup and Restore > Configuration > Configure Scheduled Backup Task from the main menu to modify the start time of the scheduled backup task, if the execution time of the task is in busy hours.

Procedure

1. On the management plane, choose Maintenance > Network Configure > Configure Floating IP Address from the main menu.
2. On the Configure Floating IP Address page, perform operations as prompted.
   • After configuring the floating IP addresses, if you want to perform other configuration operations that need to restart product services , do not select Automatically start the product services after configuring the floating IP address in the Warning dialog box. In this case, after the configuration, the product services will not be automatically started, preventing the product services from being repeatedly restarted.
   • In a DR scenario, if you are configuring the floating IP addresses at the secondary site, do not select Automatically start the product services after configuring the floating IP address in the Warning dialog box, preventing the product services of the secondary site from being restarted and causing the product to become dual-active.
   • If OMMHA is deployed and a floating IP address has been configured for a node of the service plane, you need to add or delete a floating IP address on the node for the new floating IP address, that is, the IP address of the service plane, to take effect. For details, see Modifying Configuration Parameters After a Floating IP Address Is Added or Deleted.

3. In a DR scenario, re-establish the DR relationship as follows after configuring the floating IP address:
   • After configuring the floating IP address for a product node, connect the primary and secondary site products. For details, see Connecting the Primary and Secondary Site Products.
   • If the product node and the management node are the same node, after configuring the floating IP address for the node, re-establish the DR relationship between the primary and secondary sites. For details, see Configuring the DR System (Manual Switchover).
   • After configuring the floating IP address for the management node, re-establish the DR relationship between the primary and secondary sites. For details, see Configuring the DR System (Manual Switchover).

Follow-up Procedure

Manually back up the OS of the management node, OS of product nodes, database applications, product applications, and product data. For details, see Backing Up the Management Plane and Backing Up Products.

Prerequisites

To configure server alarm reporting, ensure that iBMC can communicate with the service distribution plane.

You have logged in to the server controller card. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?

Context

Hardware alarms are monitored by the management module of the server controller card. Through the default communication IP address (configured by EasySuite) of the hardware monitoring module, the OMP node communicates with the iBMC, which helps the management plane receive hardware alarms.

Procedure

• If the iBMC version of the delivered device is 5.00 or later, perform the following steps.
  1. On the iBMC GUI, choose Maintenance > Alarm Settings. Click Trap Notification, and complete related operations by referring to Table 3-42 and click Save.
     Table 3-42 Trap function settings

     Task	Procedure
     Modifying Trap Function	Set Trap Function to Enable.
     Modifying Trap Version	Select SNMPv3.
     Modifying SNMPv3 User	Set this parameter to the username used by the controller card to report alarms to the alarm server.
     Modifying Trap Mode	2288H V5: Set this parameter to OID. 2288X V5/TaiShan: Set this parameter to Precise Alarm (recommended).
     Modify Include Alarm Severities	The recommended options include Minor.

  2. In the Trap Server and Message Format area, click Edit of a row. Complete related operations by referring to Table 3-43 and click Save.
     Table 3-43 Configure Trap Server and Packet Format

     Task	Procedure
     Modify Current Status	Set this parameter to Enable.
     Modify Trap Server Address	Set this parameter to the internal floating IP address 1 of the service distribution plane configured during installation. You can also run the ifconfig eth1:1 or ifconfig bond1:1 command on the server to obtain this IP address.
     Modify Port	Set this parameter to 30085.
     Modify Message Delimiter	Select ;.
     Select Message Content	Select Time, Sensor Name, Severity, Event Code, and Event Description.
     Modify Display Keyword in Message	Select Yes in the Display Keywords in Message area.

• If the iBMC version of the delivered device is earlier than 5.00, perform the following steps.
  1. On the iBMC GUI, choose Alarm & SEL > Alarm Setting. Complete related operations by referring to Table 3-44 and click Save.
     Table 3-44 Alarm trap notification settings

     Task	Procedure
     Modifying Trap Notification Settings	Set Trap Function to ON.
     Modifying Trap Version	Select SNMPv3.
     Modifying SNMPv3 User	Set this parameter to the username used by the controller card to report alarms to the alarm server.
     Modifying Trap Mode	2288H V5: Set this parameter to OID. 2288X V5/TaiShan: Set this parameter to Precise Alarm (recommended).
     Modify Include Alarm Severities	The recommended options include Minor.

  2. In Configure Trap Server and Packet Format, click of a row. Complete related operations by referring to Table 3-45 and click Save.
     Table 3-45 Configure Trap Server and Packet Format

     Task	Procedure
     Modify Current Status	Set this parameter to ON.
     Modify Trap Server Address	Set this parameter to the internal floating IP address 1 of the service distribution plane configured during installation. You can also run the ifconfig eth1:1 or ifconfig bond1:1 command on the server to obtain this IP address.
     Modify Trap Port	Set this parameter to 30085.
     Modify Message Delimiter	Select ;.
     Modify Select Message Content	Select Time, Sensor Name, Severity, Event Code, and Event Description.
     Modify Display Keyword in Message	Select Display Keyword in Message.

  If the iBMC versions of the delivered devices are different, some operations on the iBMC WebUI are correspondingly different. Perform the following operations to view the iBMC version information.

  1. Log in to the iBMC web UI. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. View the iBMC version information.
     • If the iBMC version is 3.01.0.0 or later, on the iBMC homepage, view iBMC Firmware Version in the Device Info area.
     • If the iBMC version is 5.00 or later, on the iBMC homepage, view iBMC Version in the Device Info area.
     • If the iBMC version is earlier than 5.00, on the iBMC homepage, view iBMC Firmware Version in the Basic Info area.

Follow-up Procedure

• If the iBMC version of the delivered device is 5.00 or later, perform the following steps.
  1. Log in to the controller card. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. Choose Maintenance > Alarm Settings, and click Trap Notification.
  3. In the Trap Server and Message Format area, click Test in the row with Current Status set to Enabled.

     If the message Operation Successful is displayed, the hardware alarms for Huawei servers are successfully configured.

• If the iBMC version of the delivered device is earlier than 5.00, perform the following steps.
  1. Log in to the controller card. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. Choose Alarm & SEL > Alarm Setting to access the Alarm Setting window.
  3. In Configure Trap Server and Packet Format, click Test in the row with Current Status set to ON.

     If the message Success is displayed, the hardware alarms for Huawei servers are successfully configured.

  If the iBMC versions of the delivered devices are different, some operations on the iBMC WebUI are correspondingly different. Perform the following operations to view the iBMC version information.

  1. Log in to the iBMC web UI. For details, see How Do I Use an iBMC IP Address to Remotely Log In to the Server?
  2. View the iBMC version information.
     • If the iBMC version is 3.01.0.0 or later, on the iBMC homepage, view iBMC Firmware Version in the Device Info area.
     • If the iBMC version is 5.00 or later, on the iBMC homepage, view iBMC Version in the Device Info area.
     • If the iBMC version is earlier than 5.00, on the iBMC homepage, view iBMC Firmware Version in the Basic Info area.

Prerequisites

To configure server alarm reporting, ensure that FusionCompute can communicate with the service distribution plane.

You have logged in to FusionCompute. For details, see How Do I Log In to FusionCompute?

Procedure

1. In the navigation pane of FusionCompute, click . The System page is displayed.
2. Choose System > Connect To > SNMP Mgt. Station. The SNMP Mgt. Station page is displayed.
3. Set FusionCompute alarm forwarding parameters by referring to Table 3-46 and click Save.
   Table 3-46 FusionCompute alarm forwarding parameters

   Task	Procedure
   Name	Set this parameter to FC_alarm.
   SNMP Version	Select SNMPv3.
   Maintenance Port	Set this parameter to 30085.
   IP Address	Set this parameter to the internal floating IP address 1 of the service distribution plane configured during installation. You can also run the ifconfig eth1:1 or ifconfig bond1:1 command on the server to obtain this IP address.
   Security Username	Set this parameter to FC_admin.
   Authentication Protocol	Select HMAC-SHA.
   Authentication Password	Set this parameter to the authentication password for the FC_admin user.
   Confirm Authentication Password
   Privacy Password	Set this parameter to the encryption password for the FC_admin user.
   Confirm Privacy Password
   Timeout Duration	Retain the default value.
   Privacy Protocol	Retain the default value.

   Set the authentication password and encryption password for the FC_admin user to different values.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Precautions

In a DR scenario, you need to configure the server alarm receiving parameters at the primary site based on the server of the primary site, and configure the parameters at the secondary site based on the server of the secondary site.

Procedure

1. On the management plane, choose Infrastructure > Hardware Management > Configure Server Alarm Receiving Parameters from the main menu.
2. On the Configure Alarm Reporting Parameters page, complete related operations by referring to Table 2-1.
   Table 3-47 Server alarm reporting parameters

   Parameter	Description
   IP Address	iMana/iBMC IP address.
   Server Type	Set this parameter to RH2288H V2/V3/V5/TaiShan 200 (Model 2280).
   SNMP Username	Set this parameter to the alarm reporting user.
   Authentication Password	SNMP authentication password. Enter the login password for the alarm reporting user.
   Encryption Password	SNMP encryption password. Enter the SNMPv3 encryption password of the alarm reporting user.

   • By default, the Administrator user of the 2288H V5/TaiShan alarm node functions as the SNMP user, and the login password of the Administrator user functions as the authentication password and the encryption password at the same time. If an alarm message is displayed indicating that the two passwords are the same, confirm the risk and continue.
   • You are advised to use a dedicated SNMP user on the 2288H V5/TaiShan for alarm reporting. When an alarm is reported, the management plane connects to the server using the SNMP user. If the login user is reused, the login user may be locked after the user login password is changed. If you need to add an alarm reporting user, add the user by referring to How Do I Add an Alarm Reporting User (Rack Server)? and set different authentication and encryption passwords for the user.

Follow-up Procedure

If the parameters on the hardware server have changed, reset the alarm receiving parameters.

Prerequisites

You have logged in to the management plane. For details, see Logging In to the Management Plane.

Precautions

In a DR scenario, you need to configure the FusionCompute alarm receiving parameters at the primary site based on the server of the primary site, and configure the parameters at the secondary site based on the FusionCompute of the secondary site.

Procedure

1. On the management plane, choose Infrastructure > Hardware Management > Configure Server Alarm Receiving Parameters from the main menu.
2. On the Set Server Alarm Receiving Parameters page, complete related operations by referring to Table 3-48.
   Table 3-48 FusionCompute alarm receiving parameters

   Parameter	Description
   IP Address	Set this parameter to the VRM floating IP address.
   Server Type	Select FusionCompute.
   SNMP Username	Set this parameter to FC_admin. The value of this parameter must be the same as the value of Security Username set in Modifying FusionCompute Alarm Forwarding Parameters.
   Authentication Password	SNMP authentication password. Enter the authentication password for the FC_admin user. For details about the password, see Virtualization-Layer User List.
   Encryption Password	SNMP encryption password. Enter the encryption password for the FC_admin user. For details about the password, see Virtualization-Layer User List.

3. Manually clear all alarms on FusionCompute.
   1. Log in to FusionCompute. For details, see How Do I Log In to FusionCompute?
   2. In the navigation pane of FusionCompute, click . On the Monitoring page, choose Monitoring > Alarm > Alarms.
   3. On the Real-Time Alarms page, check whether alarms exist. If alarms exist, click Clear to manually clear them.