HH3C-OBJECT-INFO-MIB

All MIBs › HH3C-OBJECT-INFO-MIB

Organization: Hangzhou H3C Tech. Co., Ltd.

Last Updated: 2004-12-27

Category: Device Management, Vendor: H3C/HH3C

Description: HH3C MIB providing object information and metadata for managed objects on H3C devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HH3C-OBJECT-INFO-MIB?

HH3C-OBJECT-INFO-MIB is an H3C (Huawei-3Com) enterprise MIB that provides generic object/capability information about the managed agent, rather than operational telemetry. It exposes a small set of objects an NMS can query to determine, before attempting a configuration change, whether the device's SNMP agent actually supports a particular managed object or feature. Its value is therefore in configuration-safety/capability discovery rather than in monitoring hardware or software status such as uptime, temperature, or CPU load. It sits alongside the large family of other HH3C-prefixed enterprise MIBs on H3C devices, acting as a helper module the NMS consults before touching those other MIBs. It is typically used internally by H3C-aware network management software rather than polled directly by administrators for health monitoring. Engineers can download the HH3C-OBJECT-INFO-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HH3C-OBJECT-INFO-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

H3C (Huawei-3Com) routers and switches

Monitoring Examples

hh3cObjectInformation is the module's primary object, used by a management application to check whether the agent recognizes and supports a given managed object before issuing a configuration request against it. This is a capability-discovery mechanism rather than a runtime health indicator, so there is no meaningful ongoing 'anomaly' to detect from polling it repeatedly. Its practical use is a one-time or occasional support check ahead of a configuration operation, not continuous monitoring.

Imported Objects

From HH3C-OID-MIB

hh3cCommon

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
hh3cObjectInfo	1.3.6.1.4.1.25506.2.55			This 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.
hh3cObjectInformation	1.3.6.1.4.1.25506.2.55.1
hh3cObjectInfoTable	1.3.6.1.4.1.25506.2.55.1.1		not-accessible	MIB objects information query table.
hh3cObjectInfoEntry	1.3.6.1.4.1.25506.2.55.1.1.1		not-accessible	The entry of hh3cObjectInfoTable.
OID hh3cObjectInfoOID	1.3.6.1.4.1.25506.2.55.1.1.1.1	OBJECT IDENTIFIER	not-accessible	The 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 hh3cObjectInfoValue will be failed.
INT hh3cObjectInfoType	1.3.6.1.4.1.25506.2.55.1.1.1.2	INTEGER	not-accessible	The object's properties type to be queried. The queried result will be returned by hh3cObjectInfoValue. The format of the result will be different according to different hh3cObjectInfoType.
OCT hh3cObjectInfoTypeExtension	1.3.6.1.4.1.25506.2.55.1.1.1.3	OCTET STRING	not-accessible	The object's property type extension to be queried. This object's value is relative to the value of hh3cObjectInfoType.
OCT hh3cObjectInfoValue	1.3.6.1.4.1.25506.2.55.1.1.1.4	OCTET STRING	read-only	Return 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 hh3cObjectInfoType 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 hh3cObjectInfoType 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 hh3cObjectInfoType 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 hh3cObjectInfoValue 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 hh3cObjectInfoType 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[]'.
hh3cObjectInfoMIBConformance	1.3.6.1.4.1.25506.2.55.2
hh3cObjectInfoMIBCompliances	1.3.6.1.4.1.25506.2.55.2.1
hh3cObjectInfoMIBCompliance	1.3.6.1.4.1.25506.2.55.2.1.1			The compliance statement for implementing ObjectInfo MIB.
hh3cObjectInfoMIBGroups	1.3.6.1.4.1.25506.2.55.2.2
hh3cObjectInfoTableGroup	1.3.6.1.4.1.25506.2.55.2.2.1			The basic collection of hh3cObjectInfo table objects.

RFC description

Allows NMS to query agent object support information before executing management operations on H3C devices.

Start monitoring H3C router/switch (SNMP object/capability discovery) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HH3C-OBJECT-INFO-MIB

What Is HH3C-OBJECT-INFO-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description