Skip to main content
Version: v1.5.x

Monitoring:Huawei switch

Collect and monitor the general indicators (availability, system information, port traffic, etc.) of Huawei switches.

Protocol Use: SNMP

Configuration parameter

Parameter nameParameter help description
Target HostMonitored IPV4, IPV6 or domain name. Note⚠️Without protocol header (eg: https://, http://)
Task NameIdentify the name of this monitoring. The name needs to be unique
PortPort of SNMP. The default is 161
SNMP VersionSNMP version to use
SNMP CommunityUsed in SNMP v1 and SNMP v2c, used to complete authentication in SNMP Agent, in string form. Group name includes "read" and "write", when performing SNMP query operation, "read" group name is used for authentication; when performing SNMP setting operation, "write" group name is used for authentication. When performing SNMP query operation, "read" group name is used for authentication; when performing SNMP setting operation, "write" group name is used for authentication.
SNMP usernameFor SNMP v3, MSG username
SNMP contextNameFor SNMP v3, used to determine the MIB view of the Context EngineID to the managed device
SNMP authPasswordFor SNMP v3, SNMP authentication passwords
authPassword EncryptionFor SNMP v3, SNMP authentication algorithm
SNMP privPassphraseFor SNMP v3, SNMP encrypted passwords
privPassword EncryptionFor SNMP v3, SNMP encrypted algorithm
TimeoutSet the timeout time when querying unresponsive data, in milliseconds, the default is 6000 milliseconds
IntervalsInterval time of monitor periodic data collection, unit: second, and the minimum interval that can be set is 30 seconds
DescriptionFor more information about identifying and describing this monitoring, users can note information here

Collection Metric

Since there are too many metrics that can be queried on Huawei switches, detailed metrics can be queried on Huawei MIB Query Platform.

This document only introduces the monitoring indicators queried in the monitor template.

Metric set: huawei_core

Metric NameMetric UnitMetric Help Description
ifIndexnoneInterface index. This value is greater than zero and globally unique.
ifDescrnoneA textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.
ifMtuoctetsThe size of the largest packet which can be sent/received on the interface. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.
ifSpeedbit/sAn estimate of the interface's current bandwidth. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interace's speed. For a sub-layer which has no concept of bandwidth, this object should be zero.
ifInOctetsoctetsThe total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifInDiscardsnoneThe number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifInErrorsnoneFor packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifOutOctetsoctetsThe total number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifOutDiscardsnoneThe number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifOutErrorsnoneFor packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
ifAdminStatusnoneThe desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
ifOperStatusnoneThe current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components.