HI,
And what Frank's text below means is that you cannot import ObjectSyntax into a MIB module.
A little history.... When the first version of the SNMP framework was being developed, it was believed that the Internet protocols would soon need to be replaced by the OSI protocols. The ASN.1 notation was used to define the format of messages OSI protocol messages, and it was choosen for the purpose for defining the format of SNMP messages. However, message format was only one part of the framework. Another part of the framework was a language to define management information. In database terms, this is the data dictionary or schema language. Well, it turns out that the 1988 version of ASN.1 had a macro capability to allow a new language to be created. This new language would be used to define management information accessed by the management protocol. Unfortunately, ASN.1 was not well understood, and macros and other definitions created were incorrect. The problems were ignored, and the macros defined in the ASN.1 modules found in RFCs 2578, 2579, and 2580 are mostly valid ASN.1, but don't do what what most readers think they do. They are used to define the schema lanaguage for defining management information. A set of definitions is contained in a MIB module of this schema language.
Now, this approach of "boot straping" a new language by using an existing language that contained extension capabilities is something that has been around in computer science for a long time. However, in this case, this approach has resulted in much confusion, and it appears that you are another victim.
Please share with us what are you planning on doing with the imported "ObjectSyntax" type definition. When so, then I'm sure that someone would be able to help you.
On Wed, 22 Dec 2004, [ISO-8859-1] Frank Strau� wrote:
On 22.12.2004, at 11:36, miksiu wrote:
Standard MIB SNMPv2-CONF has a import clause:
IMPORTS ObjectName, NotificationName, ObjectSyntax FROM SNMPv2-SMI;
and then during ObjectSyntax is imported, there is an error (CheckImport function returns a value 1), because cannot import ObjectSyntax and I don't know why. Maybe this is unimportant. Please, short answer.
Your assumption, that SNMPv2-CONF is a (Standard) MIB is wrong. It is part of the SMIv2 language definition, not an application of the language.
Regards, /david t. perkins