AgenPro2.0 compiling a repository

[Frank Fock]

Hi Neil and Henning,

The SNMPv2-* MIBs are clumsy in many ways.
All alone their name is misleading. They should
have been named SMIv2-*! In addition, those MIBs
are not SMIv2 conform themselves. So, I had to
implement a hack to be able to parse those MIBs,
which is not very clean design (by the IETF).

Best regards,
Frank

Crumpton, Neil wrote:
> Hi Henning and Frank,
> 	I added a new MODULE-IDENTITY construct to the -TC file
> (qbTextualConventions) - this enabled me to compile this file into the
> repository along with the QUANTUMBEAM-GLOBAL-REG file. I am now able to
> compile the QUANTUMBEAM-MLINK-MIB.txt file but I have a few errors in this
> that I need to fix first.
> 
> Thank you for all your help in this. I am still a little confused as to why
> the SNMPv2-TC-rfc2579.txt file managed to compile. Hopefully Frank will be
> able to answer this.
> 
> Regards,
> Neil
> 
> -----Original Message-----
> From: Henning Eggers [mailto:henning.eggers____plath.de]
> Sent: 10 April 2003 09:39
> To: Crumpton, Neil; Frank.Fock____t-online.de
> Cc: agentpp-dl____agentpp.com
> Subject: Re: AgenPro2.0 compiling a repository
> 
> 
> Hi Neil, Moin Frank,
> 
> if you put the MODULE-IDENTY construct into you -TC file
> and then compile it into the repository you should be able to
> compile your other files, too, first GLOBAL-REG and then
> MLINK-MIB. Order is vital here.
> 
> Why does the RFC MIB not have a MODULE-IDENTITY?
> I guess that is an error which just no-one bothered to fix.
> Frank's MIB parser is quite strict and notices things which
> others don't - I found myself correcting RFC and Cisco modules
> in the past because MIB-Designer would not import them.
> 
> But thinking about it - how did SNMPv2-TC-rfc2579.txt compile
> into the repository, if it has an error? 
> Frank?
> 
> Ciao,
> Henning
> 
>  
> ---------------------------------------------------------------------------
> The information transmitted in this e-mail is intended only for the person
> or entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other use
> of, or taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited.  We do not accept
> responsibility for changes made to this message after it was sent.
> ---------------------------------------------------------------------------
> If you received this in error, please inform info at quantumbeam.com and delete
> the material from your computer.
>