Hello,
at first thanks for your quick response.
I´m a little bit woried about the fact that it´s not allowed but maybe my previous post was just imprecise and misunderstanding. Because it´s very important for me to know i will be a little bit more precise this time.
MODULE IDENTITY 1 which is the toplevel OID registration under Enterprises is defined in its own Module (registration-mib) where only the MODULE IDENTITY is defined. MODULE IDENTITY 2 is also defined in its own Module (something-mib) which is registered under the private Enterprise OID defined in MODULE IDENTITY 1 so every Module has exactly one MODULE IDENTITY construct. But now I´m not sure any longer if this is allowed or not so please be so kind and tell me.
Best regards,
Henrik Puls
Fock, Frank wrote:
Aside from the fact, that libSMI should not cause a seg.fault, a SMIv2 MIB module must contain exactly one MODULE-IDENTITY construct. To have two, is not allowed by the SMI and that's probably why nobody has found the bug yet ;-)
On 02. Okt 2004, at 23:53, Henrik Puls wrote:
at first thanks for your quick response.
I´m a little bit woried about the fact that it´s not allowed but maybe my previous post was just imprecise and misunderstanding. Because it´s very important for me to know i will be a little bit more precise this time.
MODULE IDENTITY 1 which is the toplevel OID registration under Enterprises is defined in its own Module (registration-mib) where only the MODULE IDENTITY is defined. MODULE IDENTITY 2 is also defined in its own Module (something-mib) which is registered under the private Enterprise OID defined in MODULE IDENTITY 1 so every Module has exactly one MODULE IDENTITY construct. But now I´m not sure any longer if this is allowed or not so please be so kind and tell me.
This is allowed. --- And I get a little more concerned about the libsmi bug. :-) Could you please send me the MIB files that lead to the segfault in a private email?
participants (2)
-
Frank Strauß -
Henrik Puls