I am trying to use the MIB compiler to compile publicly available APPC-MIB module, and the following definition seems to be raising the exception "illegal syntax for textual convention. Wrong entity, DisplayString in file ...".
SnaSenseData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate their display by a Management Station, sense
data objects in the MIB are represented as DisplayStrings of
size 8. Eight '0' characters indicates that no sense data
identifying an SNA error condition is available."
SYNTAX DisplayString (SIZE (8))
I have been able to open this MIB file with ManageEngine's MIB Browser tool, so I'm thinking that lexer hasn't properly dealt with valid syntax.
Comments: Sincere apologies for my ignorance, I am new to this. This RFC (2051) was referenced in another MIB I have been interested in loading, but as far as I can tell, this is unaltered from the original RFC which is loaded up on IETF.org. Are you saying that there could be some extraneous characters somewhere that could be causing the issue. I have tried looking for an authoritative source of MIB files on the ietf.org (or tools.ietf.org) and they all seem to be embedded in the text of the document. Have you got some advise as to where the proper files should be downloaded to ensure that I have the correct ones? Thanks in advance. Craig
SnaSenseData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate their display by a Management Station, sense
data objects in the MIB are represented as DisplayStrings of
size 8. Eight '0' characters indicates that no sense data
identifying an SNA error condition is available."
SYNTAX DisplayString (SIZE (8))
I have been able to open this MIB file with ManageEngine's MIB Browser tool, so I'm thinking that lexer hasn't properly dealt with valid syntax.
Comments: Sincere apologies for my ignorance, I am new to this. This RFC (2051) was referenced in another MIB I have been interested in loading, but as far as I can tell, this is unaltered from the original RFC which is loaded up on IETF.org. Are you saying that there could be some extraneous characters somewhere that could be causing the issue. I have tried looking for an authoritative source of MIB files on the ietf.org (or tools.ietf.org) and they all seem to be embedded in the text of the document. Have you got some advise as to where the proper files should be downloaded to ensure that I have the correct ones? Thanks in advance. Craig