Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ Viewing and Configuring MRS Alarm Events/ Connecting an MRS Cluster to SNMP to Report Alarms
Updated on 2026-10-09 GMT+08:00

Connecting an MRS Cluster to SNMP to Report Alarms

In enterprise O&M scenarios, administrators often need to forward alarm and monitoring data from MRS clusters to a centralized NMS (such as Zabbix or Nagios) for unified monitoring and management across multiple systems. To view cluster alarms and monitoring metrics on a centralized platform, configure the Simple Network Management Protocol (SNMP) service on MRS Manager to proactively report cluster alarm data to your NMS.

Prerequisites

  • The ECS corresponding to the interconnected server must be in the same VPC as the Master nodes of the MRS cluster.
  • The Master nodes can access the IP address and specified port of the interconnected server.

Connecting an MRS Cluster to SNMP to Report Alarms

  1. Log in to MRS Manager and access the SNMP configuration page.

    For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.

    • MRS 3.x or later:
      1. Log in to FusionInsight Manager.
      2. Choose System > Interconnection > SNMP.
      3. Enable the SNMP service.
    • Versions earlier than MRS 3.x:
      1. Log in to MRS Manager and click System.
      2. In Configuration, enable Configure SNMP under Monitoring and Alarm.

  2. Set interconnection parameters based on Table 1.

    Table 1 Interconnection parameters

    Parameter

    Example Value

    Description

    Version

    V3

    Specifies the version of SNMP, which can be:

    • V2C: This is an earlier version with low security.
    • V3: This is a later version with higher security than SNMPv2c

    SNMPv3 is recommended.

    Local Port

    20000

    Specifies the local port. The default value is 20000. The value ranges from 1025 to 65535.

    Read Community Name

    -

    Specifies the read-only community name. This parameter is available only when Version is set to V2C.

    Write Community Name

    -

    Specifies the write community name. This parameter is available only when Version is set to V2C.

    Security Username

    test

    Specifies the SNMP security username. This parameter is available only when Version is set to V3.

    Authentication Protocol

    SHA

    Specifies the authentication protocol. This parameter is available only when Version is set to V3. SHA is recommended.

    Authentication Password

    -

    Specifies the authentication password. This parameter is available only when Version is set to V3.

    Confirm Password

    -

    Used to confirm the authentication password. This parameter is available only when Version is set to V3.

    Encryption Protocol

    AES256

    Specifies the encryption protocol. This parameter is available only when Version is set to V3. AES256 is recommended.

    Encryption Password

    -

    Specifies the encryption password. This parameter is available only when Version is set to V3.

    Confirm Password

    -

    Used to confirm the encryption password. This parameter is available only when Version is set to V3.

    • The value of Security Username cannot contain repeated strings with the unit length as a common factor of 64 (such as 1, 2, 4, and 8), for example, abab and abcdabcd.
    • The Authentication Password and Encryption Password must contain 8 to 16 characters, including at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters. The two passwords must be different. The two passwords cannot be the same as the security username or username spelled backwards.
    • For security purposes, periodically change the authentication password and encryption password when the SNMP protocol is used.
    • If SNMPv3 is used, a security user will be locked after five consecutive authentication failures within 5 minutes. The user will be automatically unlocked 5 minutes later.

  3. Click Create Trap Target in the Trap Target area. In the displayed dialog box, set the following parameters:

    • Target Symbol: specifies the trap target ID, which is the ID of the NMS or host that receives traps. The value consists of 1 to 255 characters, including letters or digits.
    • Target IP Address Mode (only for MRS 3.x or later): mode of the target IP address. The options are IPv4 and IPv6.
    • Target IP Address: specifies the target IP address, which can communicate with the management plane IP address of the management node.
    • Target Port: specifies the port receiving traps. The port number must be consistent with the peer end and ranges from 0 to 65535.
    • Trap Community Name: This parameter is available only when Version is set to V2C and is used to report the community name.

    Click OK.

    The Create Trap Target dialog box is closed.

  4. Click OK to save the SNMP settings.

    Verifying the configuration:

    • Trigger a test alarm on MRS Manager, and verify that the NMS receives the trap alarm.
    • Verify that alarms and monitoring data reported by the MRS cluster are visible on the NMS.
    • If no alarm is received, check network connectivity between the Master nodes and the IP address and port of the interconnected server.

FAQs

  • What should I do if the NMS cannot receive alarms from an MRS cluster?

    Check network connectivity between the Master nodes and the IP address and port of the interconnected server, ensure that SNMP version, port, security username, and password match the configurations on the NMS, and verify that the VPC settings are correct so that the interconnected server and Master nodes reside in the same VPC.

  • What should I do if the SNMPv3 security user is locked out?

    A security user is locked after 5 consecutive authentication failures within 5 minutes. The account automatically unlocks after 5 minutes. Verify that the authentication password and encryption password are correct to prevent account lockouts caused by repeated failed attempts.

  • How do I choose between SNMPv2c and SNMPv3?

    SNMPv3 is recommended because it provides user authentication and data encryption, ensuring high security. SNMPv2c relies solely on community names for authentication, posing security risks. Use SNMPv2c only if your NMS does not support SNMPv3.

Helpful Links