H3C-OBJECT-INFO-MIB
Imported Objects
Objects
13 total| Object Name |
|---|
h3cObjectInfoThis MIB is used to acquire information from the agent. Before a NMS takes some actions, it is not sure whether the agent supports it or not. This MIB is used to solve this problem. MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.55 |
h3cObjectInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.55.1 |
h3cObjectInfoTableMIB objects information query table. SEQUENCE OF H3cObjectInfoEntry .1.3.6.1.4.1.2011.10.2.55.1.1 |
h3cObjectInfoEntryThe entry of h3cObjectInfoTable. H3cObjectInfoEntry .1.3.6.1.4.1.2011.10.2.55.1.1.1 |
h3cObjectInfoOIDThe OID of the MIB object which is queried. If the user has no privilege accessing to the object referred by this OID, get operation on h3cObjectInfoValue will be failed. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.55.1.1.1.1 |
h3cObjectInfoTypeThe object's properties type to be queried. The queried result will be returned by h3cObjectInfoValue. The format of the result will be different according to different h3cObjectInfoType. Enumeration .1.3.6.1.4.1.2011.10.2.55.1.1.1.2 |
h3cObjectInfoTypeExtensionThe object's property type extension to be queried. This object's value is relative to the value of h3cObjectInfoType. OCTET STRING .1.3.6.1.4.1.2011.10.2.55.1.1.1.3 |
h3cObjectInfoValueReturn property value of the queried object. Zero length string is the default value of this object which means no value is returned. If the request is invalid, then the result should be the default value. If the value of h3cObjectInfoType is accessType, the rules below should be followed. 1) The returned value must have prefix 'A', and followed by some nonnegative integers. The format is like 'A2'. 2) The nonnegative integers and the meaning of them are as follow: 0 means 'not-accessible'. 1 means 'notification'. 2 means 'read-only'. 3 means 'read-write'. 4 means 'read-create'. 5 means 'write-only'. 6 means 'accessible-for-notify'. 7 means 'error'. --the above values are defined by standard protocol 101 means 'not implemented'. -- The queried node is not implemented by agent. 102 means 'unknown error'. -- Query failed for unknown reason. If the value of h3cObjectInfoType is dataType, the rules below should be followed. 1) The returned value must have prefix 'T', and followed by string which has format like 2), such as 'T1', the character '1' means INTEGER. 2) The following data types are defined in standard protocol, the values in brackets will be returned to indicate these data types. INTEGER(1) Integer32(2) Unsigned32(4) Gauge(6) Counter(7) Counter32(8) Counter64(9) TimeTicks(10) OCTET STRING(11) OBJECT IDENTIFIER(12) IpAddress(13) NetworkAddress(14) Opaque(15) BITS(16) If the value of h3cObjectInfoType is dataRange, the rules below should be followed. 1) The returned value must have prefix 'R', and followed by string which has the format like 2) to 5), such as 'R[1,1]'. 2) If h3cObjectInfoValue returns Integer32, the format is as followed. Suppose A is a MIB object. If SYNTAX of A is 'Integer32{1|2|3|5|6|7}', the format is 'R[1,3],[5,7]'. If SYNTAX of A is 'Integer32{1|3}', the format is 'R[1,1],[3,3]'. If SYNTAX of A is 'Integer32', the format is 'R[]' which means the default value range of Integer32 between -2147483648 and 2147483647. 3) The process of Counter, Counter32, Counter64, Unsigned32, Gauge32, INTEGER is the same as that of Integer32. 4) If SYNTAX of A is other types such as OCTET STRING, then this object returns default value 'R[]'. 5) If SYNTAX of A is 'BITS{a(0),b(1)}', the format is 'R[0,0],[1,1]'. If the value of h3cObjectInfoType is dataLength, the rules below should be followed. 1) The returned value must have prefix 'L', and followed by string which has the format like 2) to 4), such as 'L[6,6]'. 2) If SYNTAX of A is 'OCTET STRING(SIZE (6|10..255))', the format is 'L[6,6],[10,255]'. If SYNTAX of A is 'OCTET STRING', the format is like 'L[]' which means the default length of OCTET STRING between 0 and 65535. 3) If SYNTAX of A is BITS, the format of it is the same as OCTET STIRNG. But its unit is in bit, not in byte. 4) If SYNTAX of A is other types such as INTEGER and IpAddress, this object returns 'L[]'.ro OCTET STRING .1.3.6.1.4.1.2011.10.2.55.1.1.1.4 |
h3cObjectInfoMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.55.2 |
h3cObjectInfoMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.55.2.1 |
h3cObjectInfoMIBComplianceThe compliance statement for implementing ObjectInfo MIB. Unknown .1.3.6.1.4.1.2011.10.2.55.2.1.1 |
h3cObjectInfoMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.55.2.2 |
h3cObjectInfoTableGroupThe basic collection of h3cObjectInfo table objects. Unknown .1.3.6.1.4.1.2011.10.2.55.2.2.1 |
More MIBs from Huawei
Browse all HuaweiMIBs →The HUAWEI-MIB module provides a unified namespace for monitoring and managing generic system resources, interface statistics, and hardware telemetry across Huawei network devices. It serves as the foundational OID repository for retrieving standard operational data, including CPU utilization, memory usage, interface counters, and device status, required for comprehensive network management via SNMP.
Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.
The HUAWEI-XPON-MIB module enables Network Management Systems to monitor and configure GPON and EPON optical line terminals and optical network units, specifically tracking PON port status, optical power levels, bandwidth allocation, and subscriber session states.
SNMP MIB module
The HUAWEI-WLAN-CONFIGURATION-MIB facilitates the configuration and monitoring of Huawei Wireless LAN access point parameters, specifically managing AP port link profiles and broadcast suppression settings. This module enables administrators to enforce traffic control policies and optimize wireless network performance by adjusting switch profile associations and limiting broadcast traffic on specific ports.
The HUAWEI-XQoS-MIB enables configuration and real-time monitoring of Class Based QoS parameters on Huawei network devices, specifically tracking traffic classification rules, queue states, and policy enforcement metrics. This module facilitates granular control over bandwidth allocation and packet prioritization by exposing objects for policy definitions, interface queue depths, and dropped packet counters associated with QoS classes.