Re: [IETFMIBS] MIB implementation

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 30 October 2012 08:43 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C5021F845A for <ietfmibs@ietfa.amsl.com>; Tue, 30 Oct 2012 01:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.76
X-Spam-Level:
X-Spam-Status: No, score=-101.76 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhRHzTyoyw3V for <ietfmibs@ietfa.amsl.com>; Tue, 30 Oct 2012 01:43:28 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4990521F84EB for <ietfmibs@ietf.org>; Tue, 30 Oct 2012 01:43:28 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id A28E820BE3; Tue, 30 Oct 2012 09:43:22 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id qIwH9OpgSehs; Tue, 30 Oct 2012 09:43:22 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 341CB20A1F; Tue, 30 Oct 2012 09:43:22 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 661E4228C199; Tue, 30 Oct 2012 09:43:21 +0100 (CET)
Date: Tue, 30 Oct 2012 09:43:21 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Guo Peter <Peter.Guo@grassvalley.com>
Message-ID: <20121030084321.GA95415@elstar.local>
References: <5DB1F9C75856284BB12FF7E1BD91F58002C78ED6@BL2PRD0410MB350.namprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5DB1F9C75856284BB12FF7E1BD91F58002C78ED6@BL2PRD0410MB350.namprd04.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Subject: Re: [IETFMIBS] MIB implementation
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietfmibs>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2012 08:43:29 -0000

Hi,

you seem to have fairly basic questions related to the usage of SNMP
and I am not sure this is the right place to get help. But anyway, if
your device has network interfaces (very likely ;-), you should
implement the IF-MIB. This MIB module defines among other things the
OID 1.3.6.1.2.1.2.2.1.6. And note, you implement standard MIB objects
under the OID they are registered; no need to copy stuff into your
enterprise branch. Interoperability rests on the idea that everybody
implementing a standard MIB module like say the IF-MIB does it with
the same OIDs so that management applications can work with different
devices.

/js

On Tue, Oct 30, 2012 at 05:19:19AM +0000, Guo Peter wrote:
> Hello,
> 
> I am a developer for Grass Valley. Our registration for SNMP is  1.3.6.1.4.1.4947. I have a customer want to inquire about the MAC address of our device. He is trying to get the Physical address of the hardware using Get Request for the 1.3.6.1.2.1.2.2.1.6 and return nothing. Please see the screen capture and comments below. So my question is as a third party vendor we are normally only implementing MIB version 1(or MIB version 2) under our enterprise 1.3.6.1.4.1.4947 tree. So I don't see the iPhyAddress in our tree. So how should implement this for our customer? Or is the our responsibility to do? And is this field a mandatory field we had to implement? Where and how should I do that?
> 
> 
> 
> Regards, Peter Guo
> 
> Grass Valley Inc.
> 
> 
> 
> 
> 
> 
> "Here is what I have found so far - The SNMP configured devices are not replying to the SNMP-Get request for Mib 2 Interfaces. This is necessary for proper identification of connectivity. Spectrum uses the MAC address and compares it with the Switch ARP table to define where the device is connected. If the device is not responding to this OID request, Spectrum has no way to map it to the switch. This hinders fault isolation and troubleshooting. I have attached the results of a MIB 2 query. The device reports no results.  I would look to the engineering folks to see why the device does not respond to a MIB 2 query."
> 
> 


> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs


-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>