[IETFMIBS] MIB implementation

Guo Peter <Peter.Guo@grassvalley.com> Tue, 30 October 2012 05:19 UTC

Return-Path: <Peter.Guo@grassvalley.com>
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 3467021F855F for <ietfmibs@ietfa.amsl.com>; Mon, 29 Oct 2012 22:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 M0WaOcgV87kd for <ietfmibs@ietfa.amsl.com>; Mon, 29 Oct 2012 22:19:25 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id 040F621F8566 for <ietfmibs@ietf.org>; Mon, 29 Oct 2012 22:19:23 -0700 (PDT)
Received: from mail234-va3-R.bigfish.com (10.7.14.235) by VA3EHSOBE005.bigfish.com (10.7.40.25) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Oct 2012 05:19:22 +0000
Received: from mail234-va3 (localhost [127.0.0.1]) by mail234-va3-R.bigfish.com (Postfix) with ESMTP id 4081B7C020E for <ietfmibs@ietf.org>; Tue, 30 Oct 2012 05:19:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.85; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0410HT002.namprd04.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: PS0(zzc85fhzz1202h1d1ah1d2ahzz17326ah8275bh8275dhz2fh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh34h1155h)
Received-SPF: pass (mail234-va3: domain of grassvalley.com designates 157.56.240.85 as permitted sender) client-ip=157.56.240.85; envelope-from=Peter.Guo@grassvalley.com; helo=BL2PRD0410HT002.namprd04.prod.outlook.com ; .outlook.com ;
Received: from mail234-va3 (localhost.localdomain [127.0.0.1]) by mail234-va3 (MessageSwitch) id 1351574360790647_3363; Tue, 30 Oct 2012 05:19:20 +0000 (UTC)
Received: from VA3EHSMHS008.bigfish.com (unknown [10.7.14.237]) by mail234-va3.bigfish.com (Postfix) with ESMTP id B8B2A380049 for <ietfmibs@ietf.org>; Tue, 30 Oct 2012 05:19:20 +0000 (UTC)
Received: from BL2PRD0410HT002.namprd04.prod.outlook.com (157.56.240.85) by VA3EHSMHS008.bigfish.com (10.7.99.18) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 30 Oct 2012 05:19:20 +0000
Received: from BL2PRD0410MB350.namprd04.prod.outlook.com ([169.254.2.181]) by BL2PRD0410HT002.namprd04.prod.outlook.com ([10.255.99.37]) with mapi id 14.16.0233.002; Tue, 30 Oct 2012 05:19:19 +0000
From: Guo Peter <Peter.Guo@grassvalley.com>
To: "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Thread-Topic: MIB implementation
Thread-Index: Ac22XMyAF4LEx/rmS8+7n3xhudKc4g==
Date: Tue, 30 Oct 2012 05:19:19 +0000
Message-ID: <5DB1F9C75856284BB12FF7E1BD91F58002C78ED6@BL2PRD0410MB350.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [71.219.80.113]
Content-Type: multipart/mixed; boundary="_004_5DB1F9C75856284BB12FF7E1BD91F58002C78ED6BL2PRD0410MB350_"
MIME-Version: 1.0
X-OriginatorOrg: grassvalley.com
X-Mailman-Approved-At: Tue, 30 Oct 2012 00:29:32 -0700
Subject: [IETFMIBS] MIB implementation
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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 05:20:49 -0000

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."