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

Michael MacFaden <mrm@vmware.com> Fri, 30 August 2013 01:44 UTC

Return-Path: <mrm@vmware.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E72411E8191 for <opsawg@ietfa.amsl.com>; Thu, 29 Aug 2013 18:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SflcX5Pbbxla for <opsawg@ietfa.amsl.com>; Thu, 29 Aug 2013 18:44:08 -0700 (PDT)
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [208.91.2.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3858211E815B for <opsawg@ietf.org>; Thu, 29 Aug 2013 18:44:08 -0700 (PDT)
Received: from sc9-mailhost2.vmware.com (sc9-mailhost2.vmware.com [10.113.161.72]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 2A93528AD9; Thu, 29 Aug 2013 18:44:08 -0700 (PDT)
Received: from zcs-prod-mta-2.vmware.com (zcs-prod-mta-2.vmware.com [10.113.163.64]) by sc9-mailhost2.vmware.com (Postfix) with ESMTP id 1E133B040E; Thu, 29 Aug 2013 18:44:08 -0700 (PDT)
Received: from zcs-prod-mta-2.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-2.vmware.com (Postfix) with ESMTP id 0A876E004E; Thu, 29 Aug 2013 18:44:08 -0700 (PDT)
Received: from zcs-prod-mbox-9.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-2.vmware.com (Postfix) with ESMTP; Thu, 29 Aug 2013 18:44:07 -0700 (PDT)
Date: Thu, 29 Aug 2013 18:44:07 -0700
From: Michael MacFaden <mrm@vmware.com>
To: Hirochika Asai <panda@hongo.wide.ad.jp>
Message-ID: <359743075.3699910.1377827047802.JavaMail.root@vmware.com>
In-Reply-To: <3C80E218-DCAD-4FAA-9F4C-BC8A3BED67D4@hongo.wide.ad.jp>
References: <521158A7.2090407@cisco.com> <52126061.2000008@cisco.com> <531716211.32859971.1376937482642.JavaMail.root@vmware.com> <52128177.9020600@cisco.com> <767970431.33038278.1376945535247.JavaMail.root@vmware.com> <521285FE.2020507@cisco.com> <E0251DFB-1D54-4442-89CD-C94ACCFB0F10@hongo.wide.ad.jp> <3C80E218-DCAD-4FAA-9F4C-BC8A3BED67D4@hongo.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.113.163.68]
X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC23 (Mac)/8.0.3_GA_5664)
Thread-Topic: VM-MIB: Proposal: Joe-2 (was Re: Comments on draft-asai-vmm-mib-04)
Thread-Index: n+cA8gdK3Fep2irw4Jj9fogQz7VrTA==
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] VM-MIB: Proposal: Joe-2 (was Re: Comments on draft-asai-vmm-mib-04)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 01:44:13 -0000

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