Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Error compiling MIB file Unitrends

Description

We are trying to compile a mib file from our Backup supplier. (unitrends)

When the compile operation is ran there are some error's showing up: "ERROR: Cannot find symbol"

I have tried contacting the Backup supplier but they reply to me to contact OpenNMS, because it seems to be a known issue.

Acceptance / Success Criteria

None

Attachments

2
  • 28 Jul 2016, 08:36 AM
  • 28 Jul 2016, 05:28 AM

Confluence content

mentioned on

Lucidchart Diagrams

Activity

Show:

Ruben Vanlommel July 28, 2016 at 9:09 AM

Thank you so much for your help.

Adding those lines did indeed resolve the UnitrendsSeverity error.

I will get back to Unitrends and ask them to look further into this. Now I have a bit more knowledge of what is going on with the file.

I'll post back the result, after speaking to Unitrends.

Cyrille Bollu July 28, 2016 at 9:00 AM

Based on the link I gave you (http://www.unitrends.com/documents/legacy-rs-ueb-admin-guide/content/lag/snmp_trap_conditions.htm) you might be able to fix the syntax errors by yourself.

For example the "UnitrendsSeverity" error might be resolved by adding the following text somewhere in the file before it is used:

UnitrendsSeverity ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The severity of the trap." SYNTAX INTEGER { fatal(1), warning(2), notice(3) }

But, really, that's a Unitrends error: this MIB doesn't comply with the RFC's (eg: RFC2578 and RFC2579) and would most propably not compile on any MIB complier.

Cyr

Ruben Vanlommel July 28, 2016 at 8:25 AM

Thanks for the info!

I'm completely new to mib files and have tried to read a bit about it here and there.

Would I be able to fix the syntax errors?
Unitrends refuse to help me, pointing the blame on the compiler of OpenNMS.
Even though I have presented them with a screenshot of MG-Soft Mib Compiler also failing to compile the MIB file.
It shows errors like "Table 'tablename' and Row 'rowname' should have same name prefix" & "Table 'tablename' and Row 'rowname' must use the same entry"

Ruben

Cyrille Bollu July 28, 2016 at 8:11 AM

Ok,

Sorry I didn't look really good.

In the end, the unitrends.mib seems broken: For example, the error related to UnitrendsSeverity (last error in your screenshot) is clearly an error in their MIB (ie: It has not been defined anywhere in the file or in an imported mib).

Addendum: I made some research, and I think this UnitrendsSeverity maps to the enterprises.21865.1.1.5 OID in the following document:http://www.unitrends.com/documents/legacy-rs-ueb-admin-guide/content/lag/snmp_trap_conditions.htm

Cyr

Ruben Vanlommel July 28, 2016 at 7:03 AM

Hi Cyrille,

We have already imported SNMPv2-TC, still it is not recognizing the "DisplayString" syntax.

Ruben

Details

Assignee

Reporter

Labels

Doc Backlog Status

Doc Backlog Grooming Date

Components

Affects versions

Priority

PagerDuty

Created July 28, 2016 at 5:28 AM
Updated September 21, 2021 at 6:21 PM

Flag notifications