I have spent some time searching the forum and other places for this answer .... but ...
Adding MIBS .... I have tried to add the MS-SQL mib and others only to have them fail with various paser errors. Can someone please either point me in the direction of where to locate mibs that work with NETXMS or explain why these errors occur.
I like NETXMS as it allows you to poll devices and store the results in SQL where a purpose built web page can be created from the results but this requires additional mib information.
Any help on how to compile mibs and the location of mibs that work with Netxms would be very helpful
many thanks in advance ;D
Could you please post error messages you get?
Best regards,
Victor
Many thanks for your assistance
Below are separate compiles of two mibs - both Microsoft - perfmib and mssql. The error line is also included. Does the netxms mib compiler need mibs in a different format? I am looking to monitor MSSQL, Apache Tomcat and IIS servers as well as Juniper Netscreens and HP equipment?
.\perfmib.txt
.\perfmib.txt: ERROR 003: Parser error - syntax error, unexpected LEFT_PAREN_SYM
, expecting OBJECT_TYPE_SYM in line 4354
Line 4354 is
ms-dhcp-MillisecondsPerPacket(Avg) OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The average time per packet taken by the DHCP server to send a response."
::= { dHCP-Server 4 }
.\mssql.txt
.\mssql.txt: ERROR 003: Parser error - syntax error, unexpected OCTET_SYM, expec
ting IMPLIED_SYM or UCASEFIRST_IDENT_SYM or LCASEFIRST_IDENT_SYM in line 353
Line 353 is the 2nd last line below
mssqlSrvConfigParamEntry OBJECT-TYPE
SYNTAX MssqlSrvConfigParamEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"mssqlSrvConfigParamTable entries. The SQL Server configuration
parameter name is used as the index value."
INDEX { OCTET STRING }
::= { mssqlSrvConfigParamTable 1 }
Hello!
Second error is definitely a bug in MIB compiler, I'll fix it. I\m not sure about first error - it's quite strange ta have parenthesis as part of object name, I'll check if it's allowed by standard.
As a workaround, for first error you can change object name from ms-dhcp-MillisecondsPerPacket(Avg) to ms-dhcp-MillisecondsPerPacket, and delete entire INDEX line for second error.
Best regards,
Victor