RE: [libsmi] Need some help regarding with smidiff.

Hi,

Thanks for the reply.

I am using windows version of libsmi.

I downloaded the latest libsmi(windows version) from the below location and replaced with the old one with new libsmi-0.4.5.zip but the problem still exists.

ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/WIN32/libsmi-0.4.5.zip

Please see the attached two mibs with this email, These two mibs are imported an Unsigned64 object from CISCO-TC MIB.

Thanks, Raghavendra.

-----Original Message----- From: Frank Strauß [mailto:strauss@ibr.cs.tu-bs.de] Sent: Friday, February 02, 2007 9:16 PM To: rakrista@cisco.com Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] Need some help regarding with smidiff.

RAGHAVENDRA KRISTAM wrote:

Hi Libsmi Team,

If any MIB imported an Unsigned64 object from CISCO-TC MIB, no differences are getting even though differences exists when I use smidiff

for two mibs .

In remaining cases smidiff is working fine.

Please let me know how to solve this problem.

Ok, please get a fresh SVN update and try again.

Previously, SMIv2 modules that imported types that match a SPPI base type name have lead to severe errors and parsing has stopped. I've introduced a new level 5 warning for this case, and parsing continues, so that you should see subsequent output of parsers and smidiff results.

If the problem still exists, please send me a pair of files so that I can get a better understanding of the problem.

-frank

PS: Thanks also to Torsten, who investigated this error first and gave some hints regarding the SPPI/SMI conflict.