Libsmi June 2005

libsmi@ibr.cs.tu-bs.de

2 participants
3 discussions

Failing build from subversion repository
by Keith Dart 13 Dec '05

13 Dec '05

I obtained a subversion copy of libsmi, and try to build it (on two machines), I get the following: gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT parser-smi.lo -MD -MP -MF .deps/parser-smi.Tpo -c parser-smi.c -o parser-smi.o >/dev/null 2>&1 make[2]: *** No rule to make target `parser-smi.tab.h', needed by `scanner-smi.c'. Stop. make[2]: Leaving directory `/u01/home/kdart/src/libsmi/trunk/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/u01/home/kdart/src/libsmi/trunk' make: *** [all] Error 2 But I have flex and bison: 403 !$ bison --version bison (GNU Bison) 1.875 404 $ flex --version flex version 2.5.4 It looks like the Makefile does not include a rule for this, after all. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Keith Dart <kdart(a)kdart.com> public key: ID: F3D288E4 =====================================================================

2 1

smidump to convert into xml
by Antoine Roelens 15 Jun '05

15 Jun '05

Hello, I'm a new user and I especially use the smidump tool in order to convert MIB into XML. I encountered two problems: _ 1 : if want to export into a xml file with xml Schema structure I use the command line : smidump -f xml -o result.xml mib_file The problem is that in the xml file there are both DTD and Xml schema referenced. <?xml version="1.0"?> <!DOCTYPE smi SYSTEM "http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.dtd">  <smi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.ibr.cs.tu-bs.de/projects/nmrg/smi. xsd"> If I remove the line : <!DOCTYPE smi SYSTEM "http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.dtd"> the xml file is valid. _ 2 : If I want to execute the conversion of a MIB file like ENTITY-MIB containing a NOTIFICATION and this NOTIFICATION doesn't include object, the result in XML format is : <notifications> <notification name="entConfigChange" oid="1.3.6.1.2.1.47.2.0.1" status="current"> <objects> </objects> <description> An entConfigChange ....... </description> </notification> </notifications> And this is wrong according to the DTD or the XMl schema. The tag <objects> must contain at least on tag <object>. In the MIB NOTIFCATION-TYPE objects are optional. Thank you in advance for your help and for this tool Cheers Antoine

1 0

internal-other - An unspecified error occured
by Per Jessen 05 Jun '05

05 Jun '05

I ran smilint on the ZyXEL MIB which produces quite a few errors - but also a ton of these: ZYXEL-MIB.txt:74: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:77: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:85: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:89: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:97: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:101: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:109: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:112: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:122: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:133: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:141: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:144: {internal-other} syntax error, unexpected ACCESS The explanation of 'internal-other' asked that I submit a report. An unmodified version of what appears to be the most recent ZyXEL MIB is available here: http://jessen.ch/files/Zyxel.mib -- /Per Jessen, Zürich

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi June 2005