Posted: September 21, 2012 19:09 by dominaf
First, allow me to put this into the proper context, as previous posts were wrongly interpreted. This has nothing to do with the PC Platform, or any specific platform for that matter. And actually, in this case we are the platform -- we are writing the porting layer between the RI Stack and our platform.
Is there a document that indicates which OC-STB-HOST-MIB objects the RI Stack itself will be implementing?
There are some MIBs that, upon examination of the RI Stack source, we see RI has implemented (though there are bugs with some as noted at the bottom of this post).
There are other OC-STB-HOST-MIB objects that we believe would be impossible to implement within the platform, or even within our porting layer and therefore need to be implemented within the RI Stack itself. The problem is, they're not there. We need confirmation that the RI Stack will be implementing these MIBs:
You can ignore the ocStbEasMessage* objects Susmita asked about. They belong in the RI Stack, and are already there. (The info isn't available below that.)
Additionally, we do not fully understand the intent behind the MIBs under the ocStbHostSystemLogging branch, and as such we are not clear at what level they are expected to be implemented. This branch includes the following MIBs:
According to the MIB spec: -- The Host System Logging table. -- -- This table is used as an event logging table shared by the system -- and applications. Note that network-related events are still -- recorded in the ocStbHostSystemLoggingEventTable. The Host adds an -- event by adding a conceptual row to the end of the table; -- Once the table 'fills' by reaching -- ocStbHostSystemLoggingSize, adding a new event causes the oldest -- conceptual row to be removed.
But what is "the system"? Is this the RI Stack plus any apps? Or does "the system" include the porting layer and platform all the way down to the lowest layer of drivers? If it includes the platform, that would be imposing a lot on the platform. I suspect this is supposed to apply only to the RI Stack (and above), but am not certain, so please confirm that the RI Stack will implement these ocStbHostSystemLogging MIBs.
Finally, here are the MIBs that are already implemented in the RI Stack, with bugs as noted:
ocStbHostSoftwareApplicationInfoTable (multiple columns: NameString, VersionNumber, Status, OrganizationId, ApplicationId)
ocStbHostCCAppInfoTable (multiple Columns: Index, Type, Name, Version, Page)