Hyper Converged Infrastructure (HCI/aSV)

Sangfor HCI and aSV provide a unified infrastructure combining compute, storage, networking, and built-in security to simplify deployment, operations, and services.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.1R1
Hyper Converged Infrastructure (HCI/aSV) {{ breadTitle }} User Manual HCI Platform Configuration Guide Advanced SNMP Settings
{{sendMatomoQuery("Hyper Converged Infrastructure (HCI/aSV)","SNMP Settings")}}

SNMP Settings

{{ $t('productDocDetail.updateTime') }}: 2026-01-05

Description

HCI can obtain configurations, status, and alerts of hosts in a cluster through a Simple Network Management Protocol (SNMP) trap, and push the information through the trap API to a third-party monitoring platform in the case of an alert.

If your company has deployed its own third-party monitoring platform, monitoring information (such as host information and platform alerts) on the virtualization platforms of different vendors needs to be collected uniformly and pushed through the trap API, so that issues can be handled in time.

Precautions

  1. You can only query physical resources in the SNMP management information base (MIB) that you are prompted to download on the page. If the target physical resources exist in the MIB but not in the actual environment, no results will be returned.

Type

Available Information

Baseboard management controller (BMC)

BMC information, Intelligent Platform Management Interface (IPMI) IP address, version, and firmware version

Motherboard

Manufacturer, model, serial number, and firmware version

CPU

Manufacturer, model, configuration, status, power, voltage, clock speed, number of cores, fan RPM, temperature, and so on

Memory

Manufacturer, serial number, slot location, capacity, and so on

SSD

Manufacturer, model, serial number, capacity, lifetime, status, firmware version, and so on

HDD

Manufacturer, model, serial number, capacity, status, firmware version, and so on

GPU

Manufacturer, model, serial number, number of cores, clock speed, capacity, firmware version, and so on

RAID card

Manufacturer, model, driver, status, and so on

HBA

Manufacturer, model, driver, firmware version, and so on

NIC

Manufacturer, model, speed, firmware version, and so on

Optical module

Model, specifications, firmware version, and so on

Power supply

Manufacturer, model, power, and so on

Fan

RPM, status, and so on

  1. SNMP transmission is optional. SNMP V1 and V2C traps cannot be encrypted, and you can view the information without this configuration item. If no SNMP trap is configured, the community of sangforpub is used for status checking by default. SNMP V3 traps can be encrypted, and you need to complete authentication and encryption before use.
  2. SNMP trap:

• You can configure up to three traps.

• SNMP trap configurations need to be stored persistently. They can be read by cluster nodes and modified only by the cluster controller.

• An SNMP trap does not guarantee the reliability of an alert notification. For SNMP V3, the INFORM protocol is used to tell whether a notification is pushed successfully.

  1. If the request interval is 5 seconds, the CPU overhead is less than 5%, and the memory overhead is less than 40 MB.
  2. The alert content is in JSON format. The alert message header specifies the cluster name, hostname, resource object name, and physical host IP address (if any).
  3. An alert notification is pushed within 10 seconds after an alert is generated.

Prerequisites

  1. The third-party monitoring platform has been configured to communicate with the cluster network.
  2. The SNMP MIB has been downloaded.

Steps

  1. Go to System > Port Management and enable the SNMP service.

  1. In the SNMP Transmission section, click Configure and set parameters to enable users to access HCI resources using an independent account, helping administrators understand the usage of physical resources in use. Select MD5 or SHA for Authentication Protocol and AES or DES for Encryption Algorithm.

  1. In the SNMP Trap section, click New and configure a trap.

• Remote IP/Port: The IP addresses or ports cannot conflict with each other if multiple traps are configured. Port 162 is used by default.

• Language: Select Simplified Chinese or English.

• SNMP Version: Select V1, V2C, or V3. SNMP V1 and V2C traps cannot be encrypted. For SNMP V3, you can set Username, Password, Encryption Algorithm, Private Key, Use Inform (you can select Yes to use INFORM to push notifications and tell whether they are pushed successfully), and Engine ID (which contains 10–64 hexadecimal numbers).