Posted Thu, 01 Jan 2015 06:00:00 GMT by Portal Admin

Q. I've run into the below attempting to import a MIB, but I don't see why it is thinking it's EOF:

    • 14:49:50 MIB[3]: Expected "{" (EOF): At line 18925 in C:\Program Files\InterMapper\InterMapper Settings\MIB Files\MIB.my.2
      14:49:50 MIB[3]: Bad object identifier: At line 18925 in C:\Program Files\InterMapper\InterMapper Settings\MIB Files\MIB.my.2
      14:49:50 MIB[3]: Bad parse of NOTIFICATION-TYPE: At line 18925 in C:\Program Files\InterMapper\InterMapper Settings\MIB Files\MIB.my.2

This is the part of the MIB in question: (Line 18925 is actually the INFORMATIONAL line)


--#SUMMARY "[nsei %d] bvci %d BVC Up"
--#ARGUMENTS {0,1}
--#STATE OPERATIONAL
--#SEVERITY INFORMATIONAL
::= { MibTraps 1067 }


A. When there is a MIB compilation error that complains about reading EOF, it usually means you have an unterminated quoted string. There is a malformed entry in the MIB. Note that the DESCRIPTION field for the 'starManagerRestart ' entry does not end with a ".

starManagerRestart NOTIFICATION-TYPE
OBJECTS { starTaskfacilityName, starTaskInstance, starTaskCard, starTaskCPU }
STATUS current
DESCRIPTION
"The identified manager task has been restarted..
--#SUMMARY "[System] Manager %s/%d restarted on %d/%d"
--#ARGUMENTS {0,1,2,3}
--#STATE OPERATIONAL
--#SEVERITY INFORMATIONAL
::= { starentTraps 1099 }


Replacing the second period after 'restarted' with a double-quote allows the MIB to compile (with possible exception of any missing imports).

You must be signed in to post in this forum.