All MIBs › HH3C-OBJECT-INFO-MIB › hh3cObjectInfoValue
hh3cObjectInfoValue
Module: HH3C-OBJECT-INFO-MIB
OID (symbolic): HH3C-OBJECT-INFO-MIB::hh3cObjectInfoValue
OID (numeric): 1.3.6.1.4.1.25506.2.55.1.1.1.4
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-only
Description: 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[]'.
What is hh3cObjectInfoValue?
This object returns a generic, encoded answer to a query about some other MIB object's properties — for example, if the queried property type was "accessType" the value comes back as a code like "A2" meaning read-only, or if it was "dataType" a code like "T1" meaning INTEGER — with an empty string meaning no answer was found. Management tools use this generic lookup mechanism to programmatically discover metadata about arbitrary objects on the device without needing that information hard-coded in advance. For instance, querying about an object's access rights might return "A3", which this MIB's numbering decodes as read-write.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.55.1.1.1.4 snmpwalk -v2c -c public <target> HH3C-OBJECT-INFO-MIB::hh3cObjectInfoValue
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.55.1.1.1.4.1 snmpget -v2c -c public <target> HH3C-OBJECT-INFO-MIB::hh3cObjectInfoValue.1
Start monitoring H3C router/switch (SNMP object/capability discovery) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-OBJECT-INFO-MIB::hh3cObjectInfoValue OID value, configure state conditions and alerts, and monitor any H3C router/switch (SNMP object/capability discovery) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.25506 | hh3c | HH3C-OID-MIB |
| 1.3.6.1.4.1.25506.2 | hh3cCommon | HH3C-OID-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.25506.2.55 | hh3cObjectInfo | HH3C-OBJECT-INFO-MIB |
| 1.3.6.1.4.1.25506.2.55.1 | hh3cObjectInformation | HH3C-OBJECT-INFO-MIB |
| 1.3.6.1.4.1.25506.2.55.1.1 | hh3cObjectInfoTable | HH3C-OBJECT-INFO-MIB |
| 1.3.6.1.4.1.25506.2.55.1.1.1 | hh3cObjectInfoEntry | HH3C-OBJECT-INFO-MIB |
| 1.3.6.1.4.1.25506.2.55.1.1.1.4 | hh3cObjectInfoValue | HH3C-OBJECT-INFO-MIB |