How does AgenPro2 deal with ASN.1 Macros in standard Mibs?

[Frank Fock]

Hi Martin,

All SMI constructs which are defined as
ASN.1 macros (e.g. OBJECT-TYPE, MODULE-IDENTITY, etc.)
are of course supported. The *definition* of such
macros written in ASN.1 sytnax (not SMI) is not
supported, because such definitions are not part of
the SMI language.

Other comments follow inline:

Loridon, Martin wrote:
> Hi,
> 
> I am currently experimenting with AgenPro2 evalution license. After 
> reading the FAQ.txt:
> 
> AgenPro 2 FAQ
> =============
> 
> Q: Why does AgenPro refuse to compile MIB modules
>    containing ASN.1 MACRO definitions like the RFC1155-MIB,
>    SNMPv2-SMI, SNMPv2-CONF, or SNMPv2-TC modules?
> 
> A: ASN.1 MACROS are *not* part of the SMIv1/v2 languages.
>    MACROS are used to define the SMI language with ASN.1
>    syntax. Thus, the modules above have to be treated as
>    non-compliant to the SMI rules. In order to make them
>    compliant, one has to remove all MACROs from the
>    modules.
> 
> I do not understand how the Mib compiler can deal with the macros like: 
> OBJECT-TYPE, MODULE-IDENTITY and many others.
> Those macros have to be removed from the standard mib so the mib can be 
> compiled and become a entity of the MIB repository.
> 
> Although in the proprietary MIB we can still mention macro IMPORTs from 
> standard mibs???
>

Yes, of course.

Regards,
Frank Fock