Re: [OPSAWG] VM-MIB: Proposal: Joe-2 (was Re: Comments on draft-asai-vmm-mib-04)

[Hirochika Asai <[e-mail]>]

Yes, I agree that the MIB module shouldn't preclude adding any functionalities.
So we'd better not to have the virtual IPMI object in the MIB in order not to
prevent adding them from developers.

Best regards,
Hirochika


On Aug 30, 2013, at 10:44 AM, Michael MacFaden <[e-mail]> wrote:

> Asai-san writes:
>> But let me ask to the list about the virtual IPMI implementation.
>>> Does anybody know such other implementations of the virtual IPMI?
>>> If there are, we may need to take into account them.
>> I couldn't find any other implementations of the virtual IPMI, so my
>> opinion is that we do not need an object related to the virtual IPMI
>> or something like it.  If you find any, I'd like you to let me know.
> 
> I'm not aware of either a virtualized or just pass-through access to IPMI
> hardware in VMware products or I'd have been happily usig it many times 
> over to allow me to test ESXi SNMP agent RFC 2790 implementation in a VM[1]
> 
> If there are none, lets just make sure the MIB module doesn't preclude
> adding that...
> 
> Regards,
> Mike
> 
> [1] 
> $ esxcfg-info | grep Product Name
>      |----Product Name.............................................IBM System x3200 M2 -[4368AC1]-
> # diagnostics report
> $/bin/snmpd -S
> INFO: fetching sensors...
> record id: 8, length: 42, type: 2 entity: 7 instance: 1
> record id: 9, length: 35, type: 2 entity: 7 instance: 1
> record id: 14, length: 37, type: 2 entity: 3 instance: 1
> record id: 15, length: 37, type: 2 entity: 20 instance: 1
> record id: 17, length: 36, type: 2 entity: 23 instance: 1
> record id: 18, length: 37, type: 2 entity: 7 instance: 1
> record id: 20, length: 42, type: 2 entity: 7 instance: 1
> record id: 21, length: 40, type: 2 entity: 7 instance: 1
> record id: 22, length: 40, type: 2 entity: 7 instance: 1
> record id: 29, length: 40, type: 2 entity: 23 instance: 1
> record id: 34, length: 39, type: 2 entity: 3 instance: 1
> record id: 36, length: 34, type: 2 entity: 7 instance: 1
> record id: 60, length: 41, type: 2 entity: 4 instance: 2
> record id: 61, length: 41, type: 2 entity: 4 instance: 1
> record id: 62, length: 41, type: 2 entity: 4 instance: 4
> record id: 63, length: 41, type: 2 entity: 4 instance: 5
> record id: 64, length: 41, type: 2 entity: 4 instance: 6
> record id: 65, length: 41, type: 2 entity: 4 instance: 7
> record id: 66, length: 41, type: 2 entity: 4 instance: 8
> record id: 74, length: 41, type: 2 entity: 4 instance: 3
> record id: 75, length: 38, type: 2 entity: 21 instance: 1
> record id: 76, length: 38, type: 2 entity: 21 instance: 2
> record id: 77, length: 41, type: 2 entity: 21 instance: 3
> record id: 78, length: 41, type: 2 entity: 21 instance: 4
> record id: 79, length: 38, type: 2 entity: 21 instance: 5
> record id: 80, length: 37, type: 2 entity: 0 instance: 1
> INFO: sensor sweep completed, using total of 11 sensor entries in sdr
> [0] name: VRD Status, inst: 1, type: POWER, status: D_Normal, errors: 0
> [1] name: PS 1 Status, inst: 1, type: POWER, status: D_Normal, errors: 0
> [2] name: PS 2 Status, inst: 2, type: POWER, status: D_Normal, errors: 0
> [3] name: PS Overspec, inst: 5, type: POWER, status: D_Normal, errors: 0
> [4] name: Fan 1 Tach, inst: 1, type: FAN, status: D_Normal, errors: 0
> [5] name: Fan 2 Tach, inst: 2, type: FAN, status: D_Normal, errors: 0
> [6] name: Fan 3 Tach, inst: 3, type: FAN, status: D_Normal, errors: 0
> [7] name: PS 1 Fan Fault, inst: 3, type: FAN, status: D_Normal, errors: 0
> [8] name: PS 2 Fan Fault, inst: 4, type: FAN, status: D_Normal, errors: 0
> [9] name: CPU Status, inst: 1, type: CPU, status: D_Normal, errors: 0
> [10] name: CPU OverTemp, inst: 1, type: CPU, status: D_Normal, errors: 0
> INFO: report complete
> 

-- 
Hirochika Asai <[e-mail]>, The University of Tokyo