The MIB definition for the table "ocStbHostSystemTempTable" is provided below.  
 I generated the system temp table code using the mib2c tool with the MfD 
configuration file.  I was assuming each standalone table would have one 
"index" field which represents the row number assigned in the table, but this 
system temp table has two indices defined for it in the MIB file as the "INDEX" 
value (see BOLD below).  One index is the expected "ocStbHostSystemTempIndex" 
value and the other is the "hrDeviceIndex" which seems to be related to the 
"hrDeviceTable" table defined in the HostResources MIB.  

Based on the "ocStbHostSystemTempTable" MIB table definition (shown below), 
then what is the relationship between these two indices?  How do I implement 
the  "ocStbHostSystemTempTable"?  How do I interpret the meaning of a MIB table 
which has two indices?  Must I implement the "hrDeviceTable" and then somehow 
use that table information for implementing the "ocStbHostSystemTempTable" 
table?
 

System Temp Table shown below:

--
-- Host system resources
--

ocStbHostSystemObjects  OBJECT IDENTIFIER ::= { ocStbHostStatus 3 }


ocStbHostSystemTempTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF OcStbHostSystemTempEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains the temperature sensors of the 
            ocStbHost."
    ::= { ocStbHostSystemObjects 1 }

ocStbHostSystemTempEntry OBJECT-TYPE
    SYNTAX      OcStbHostSystemTempEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "Conceptual row of a temperature sensor device associated 
            with a Host Resource device (e.g., DVR) of the ocStbHost."
    INDEX { hrDeviceIndex, ocStbHostSystemTempIndex } 
    ::= { ocStbHostSystemTempTable 1 }

OcStbHostSystemTempEntry::= SEQUENCE { 
        ocStbHostSystemTempIndex        Unsigned32,
        ocStbHostSystemTempDescr        SnmpAdminString,
        ocStbHostSystemTempValue        Integer32,
        ocStbHostSystemTempLastUpdate   TimeStamp
    }

ocStbHostSystemTempIndex OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "The identifier of the temperature sensor for the 
            corresponding hrDeviceIdx."
    ::= { ocStbHostSystemTempEntry 1 }

ocStbHostSystemTempDescr OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The text containing information about the temperature 
            sensor."
    ::= { ocStbHostSystemTempEntry 2 }

ocStbHostSystemTempValue OBJECT-TYPE
    SYNTAX      Integer32
    UNITS       "celsius"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The temperature measured by the sensor.
            If the temperature sensor does not report a 
            value, this object indicates a value of 0."
    ::= { ocStbHostSystemTempEntry 3 }

ocStbHostSystemTempLastUpdate OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The value of sysUpTime of the last time this value
            was measured by the ocStbHost.
            A value 0 means the temperature value is invalid."
    ::= { ocStbHostSystemTempEntry 4 }


       
---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo! 
FareChase.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to