Re: RFC1850 - compilation error

Don Goodspeed <dgoodspe@EXCITE.COM> Fri, 12 September 2003 18:11 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07967 for <ospf-archive@LISTS.IETF.ORG>; Fri, 12 Sep 2003 14:11:39 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <19.00B79FCB@cherry.ease.lsoft.com>; Fri, 12 Sep 2003 14:11:43 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 54809564 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 12 Sep 2003 14:11:35 -0400
Received: from 207.159.120.57 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 12 Sep 2003 14:11:35 -0400
Received: by xmxpita.excite.com (Postfix, from userid 110) id C7D90B6DC; Fri, 12 Sep 2003 14:11:31 -0400 (EDT)
Received: from [64.47.48.10] by xprdmailfe14.nwk.excite.com via HTTP; Fri, 12 Sep 2003 14:11:31 EST
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: ID = ce00c10647f1b9e7db16a67db0936ee4
MIME-Version: 1.0
X-Sender: dgoodspe@excite.com
X-Mailer: PHP
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <20030912181131.C7D90B6DC@xmxpita.excite.com>
Date: Fri, 12 Sep 2003 14:11:31 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Don Goodspeed <dgoodspe@EXCITE.COM>
Subject: Re: RFC1850 - compilation error
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Divya,

You can try using -CT.  For more on smicng, contact Dave Perkins
at www.snmpinfo.com as he is the author of smicng.  These option
are also described in his book "Understanding SNMP MIBs" which
is where I looked.

-don

====================================================
Hi,

I'm getting the following compilation error in "compliance statements"
of RFC1850 (OSPF-TRAP-MIB). I'm using smicng and Fred Baker
said that the MIB compiled with it and that smicng could have changed
subsequently. Is anyone aware of an option in smicng that can suppress
this error? Any other suggestions?

-----------------------------------RFC1850--------------------------------------------
-- compliance statements

ospfTrapCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement "
MODULE -- this module
MANDATORY-GROUPS { ospfTrapControlGroup } <<<====


GROUP ospfTrapControlGroup <<<====
DESCRIPTION
"This group is optional but recommended for all
OSPF systems"


-----------------------------------ERROR----------------------------------------------
E: f(OSPF-TRAP-MIB.my), (470,21) Group "ospfTrapControlGroup" is both a
MANDATORY and conditional group for module "OSPF-TRAP-MIB"

Thanks,
-Divya

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!