|
|
|
Reason:
This message is produced by the MIB compiler as it commences compilation of a MIB.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler at the end of compilation of a MIB. The return code is shown.
Return code values are:
0 - Compilation successful. No errors or warnings
4 - Compilation may be successful. At least one warning was found.
8 - Compilation failed. At least one error was found.
12 - Compilation aborted. A serious error or compiler failure occurred.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler at the end of compilation if any identifiers were found that exceeded 32 characters in length.
Individual warning messages were produced as each identifier was found. This message (an ERROR severity message) indicates how many were found.
This release of the MIB compiler does not support identifiers longer than 32 characters.
System Action:
Compilation is terminated.
This is an ERROR message.
User Action:
Examine the compiler messages for warnings about identifier length, and make the appropriate corrections to the MIB source.
Reason:
This message is produced by the MIB compiler if an error occurs parsing the supplied parameters. The error message from the SETVARS statement follows.
System Action:
Compilation is terminated.
User Action:
Report this error to your product support representative.
Reason:
This message is produced by the MIB compiler if a required parameter is omitted or has an invalid value.
System Action:
Compilation is terminated.
User Action:
Report this message to your product support representative.
Reason:
This message is produced by the MIB compiler if an input parameter has an invalid value.
System Action:
Compilation is terminated.
User Action:
Report this message to your product support representative.
Reason:
This message is produced by the MIB compiler if the input source line array variable has an invalid line count.
System Action:
Compilation is terminated.
User Action:
Report this message to your product support representative.
Reason:
This message is produced by the MIB compiler if an option in the IGNORE parameter is not recognized.
System Action:
The option is ignored. Other IGNORE options are recognized and honored.
User Action:
Remove or correct the invalid option.
Reason:
This message is produced by the MIB compiler if an entry in the IMPRENAME parameter is not valid.
The reason is shown.
System Action:
The entry is ignored. Other IMPRENAME entries are processed.
This message counts as an error.
User Action:
Remove or correct the invalid entry.
Reason:
This message is produced by the MIB compiler if an internal failure has occurred.
System Action:
Compilation is terminated.
User Action:
Report the error to your product support representative.
Reason:
This message is produced by the MIB compiler if an internal failure has occurred. It indicates that an execution stack traceback follows.
System Action:
None.
User Action:
Refer to message MC0090.
Reason:
This message is produced by the MIB compiler if an internal failure has occurred. It provides the name and value of an internal error information variable. Only non-null variables are displayed.
System Action:
None.
User Action:
Refer to message MC0090.
Reason:
This message is produced by the MIB compiler if an internal failure or fatal error has occurred. It provides the value and location of a source token. This information allows identification of the location in the source where the problem occurred.
System Action:
None.
User Action:
Refer to message MC0090.
Reason:
This message is produced by the MIB compiler if the first token found in the MIB source is not a valid identifier.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler if an OBJECT IDENTIFIER was found after the MIB module name and the syntax was invalid.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler if an OBJECT IDENTIFIER was found after the MIB module name.
The IGNORE=INITOID option was specified, resulting in this warning.
This is not recommended syntax. (Refer to RFC2578, section 3, second last paragraph.)
System Action:
Compilation continues. This message counts as a warning.
User Action:
None.
Reason:
This message is produced by the MIB compiler if an OBJECT IDENTIFIER was found after the MIB module name.
This is not recommended syntax. (Refer to RFC2578, section 3, second last paragraph.)
This error can be suppressed by specification of the INITOID option of the IGNORE compiler parameter.
System Action:
Compilation continues. This message counts as an error.
User Action:
Correct the MIB source, or specify the INITOID option of the IGNORE compiler parameter.
Reason:
This message is produced by the MIB compiler if the indicated token was expected in the source during processing of the initial DEFINITIONS statement.
The indicated token was not found.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message shows the MODULE name found by the MIB compiler. This name is the name specified on the DEFINITIONS BEGIN statement.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler when it did not find an END statement at the end of the MIB source.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it found further MIB source following the END statement.
This does not include comments.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler if the MIB module name is longer than 32 characters.
This version of the MIB compiler requires MIB module names to be no longer than 32 characters.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when an unrecognized statement is found.
The statement is not valid in a MIB. It may be a valid ASN.1 statement; however, the MIB compiler does not recognize it.
System Action:
Compilation continues with the next recognized statement. This statement counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a macro name was found that requires an identifier.
Identifiers in ASN.1 must start with a lower-case letter.
System Action:
Compilation continues with the next recognized statement. This statement counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a macro name was found that requires a type identifier.
Type identifiers in ASN.1 must start with an upper-case letter.
System Action:
Compilation continues with the next recognized statement. This statement counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when an ASN.1 statement that is unsupported by the MIB compiler is encountered.
The statement is not valid in a MIB. It may be a valid ASN.1 statement; however the ASN.1 subset that is acceptable in a MIB does not include it.
System Action:
Compilation continues with the next recognized statement. This statement counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when an apparent macro name was not found in an internal table.
System Action:
Compilation terminates.
User Action:
Report this to your product support representative.
Reason:
This message is produced by the MIB compiler when an internal field had an unrecognized value.
System Action:
Compilation terminates.
User Action:
Report this to your product support representative.
Reason:
This message is produced by the MIB compiler when it finds invalid source during the processing of an IMPORTS statement.
System Action:
Compilation continues with the next statement.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid source during the processing of an IMPORTS statement.
Either a comma (,) or the FROM keyword was expected at this point.
System Action:
Compilation continues with the next statement.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid source during the processing of an IMPORTS statement.
Either an identifier or a semicolon (;) was expected at this point.
System Action:
Compilation continues with the next statement.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated item during processing of an IMPORTS statement.
The indicated item has already been imported.
This version of the MIB compiler does not support qualified references to imported items. Therefore all imported items must be unique.
System Action:
Compilation continues. Other IMPORT items are processed.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it renames the module that the indicated item was to be imported from.
This occurs when a match is found in the IMPRENAME list.
System Action:
Compilation continues.
This message counts as a warning.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
None.
Reason:
This message is produced by the MIB compiler when it renames the module that the indicated item was to be imported from.
This occurs when the IMPORT/EXPORT exit renames the module name.
System Action:
Compilation continues.
This message counts as a warning.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
None.
Reason:
This message is produced by the MIB compiler when it tries to import the definition of an item from the Imports Database.
The module that the item was being imported from (or as renamed by the IMPRENAME option or the Import/Export exit) was not found on the database.
This means that the module (or MIB) has not been compiled or compilation failed, or that the module name was spelt incorrectly.
System Action:
Processing continues with the next IMPORT item or next statement.
This message counts as a warning.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it tries to import the definition of an item from the Imports Database.
The module that the item was being imported from (or as renamed by the IMPRENAME option or the Import/Export exit) did not contain a definition for the item.
System Action:
Processing continues with the next IMPORT item or next statement.
This message counts as a warning.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it tries to import the definition of an item from the Imports Database.
An error occurred while processing the Imports Database.
System Action:
Processing continues with the next IMPORT item or next statement.
This message counts as a warning.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Examine the log for related messages and report the error to your product support representative.
Reason:
This message is produced by the MIB compiler while parsing an IMPORT statement.
A MODULE name on the IMPORT statement was longer than 32 characters. This release of the MIB compiler does not support module names greater than 32 characters in length.
System Action:
Compilation terminates.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source as required and recompile.
You may need to alter the source for the referenced MIB to shorten its module name to less than 32 characters and compile that MIB as well.
Reason:
This message is produced by the MIB compiler when an internal function has returned an invalid code.
System Action:
Compilation terminates.
User Action:
Report this to your product support representative.
Reason:
This message is produced by the MIB compiler when it finds invalid source during the processing of an EXPORTS statement.
System Action:
Compilation continues with the next statement.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated item during processing of an EXPORTS statement.
The indicated item has already been marked as exported.
This version of the MIB compiler does not support qualified references to exported items. Therefore all exported items must be unique.
System Action:
Compilation continues. Other EXPORT items are noted.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid source during the processing of an EXPORTS statement.
Either a comma (,) or a semicolon (;) was expected at this point.
System Action:
Compilation continues with the next statement.
This message counts as an error.
NOTE: errors in an IMPORTS statement can cause other errors later in compilation due to missing definitions.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated type name declaration.
The indicated type name has already been declared (or imported).
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated OBJECT IDENTIFIER name declaration.
The indicated name has already been declared (or imported).
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while processing an OBJECT IDENTIFIER name declaration.
The token following OBJECT IDENTIFIER was not '::='.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while processing a MACRO definition statement.
This version of the MIB compiler does not support MACRO definitions. However, it parses the MACRO statement and attempts to match the declared macro with one that it understands for MIB compilation.
The indicated macro name was recognized. It has been defined.
System Action:
Compilation continues.
This message counts as a warning.
User Action:
None.
Reason:
This message is produced by the MIB compiler when it finds the end of the MIB source while processing a MACRO definition statement.
System Action:
Compilation is terminated.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while processing a MACRO definition statement.
This version of the MIB compiler does not support MACRO definitions. However, it parses the MACRO statement and attempts to match the declared macro with one that it understands for MIB compilation.
The indicated macro was not one that it recognized.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while processing a MACRO definition statement.
This version of the MIB compiler does not support MACRO definitions. However, it parses the MACRO statement and attempts to match the declared macro with one that it understands for MIB compilation.
The indicated macro name was recognized. However, the version of the MIB SMI had already been determined by previous definitions (for example, imported names). This macro definition was for a different version.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated definition.
The indicated name has already been declared. The type of declaration previously encountered is also shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a duplicated keyword while processing a declaration.
The duplicated keyword name is shown. The type of declaration and the name of the entity being declared are also shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds an invalid clause while processing a declaration.
The clause keyword name is shown. The type of declaration and the name of the entity being declared are also shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while processing a declaration.
The expected token name is shown. The type of declaration and the name of the entity being declared are also shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds missing clauses while processing a declaration.
The declaration type and name are shown. The missing clause name is also shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while processing a declaration.
The expected token is shown, along with the preceding token.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds the end of source while processing a declaration.
The clause being processed is shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while processing a declaration.
The expected token is shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds a pair of clauses that are mutually exclusive while processing a declaration.
The clause names are shown.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while processing a declaration.
The expected tokens are shown. At the indicated point, one of these tokens was expected.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when an internal routine is called with unexpected or invalid source.
The expected token is shown.
System Action:
Compilation is terminated.
User Action:
Report this error to your product support representative.
Reason:
This message is produced by the MIB compiler to indicate how many passes were required to resolve forward references in OBJECT IDENTIFIER declarations.
System Action:
Compilation continues.
User Action:
None.
Reason:
This message is produced by the MIB compiler when it finds a duplicated OBJECT IDENTIFIER name declaration.
The indicated name has already been declared (or imported).
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
An integer or identifier was expected. These are the only valid options at this point of an OBJECT IDENTIFIER declatation.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
It indicates one of the following:
- The name being declared was found in the list (recursive).
- A duplicated name was found in the list.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
A name was found in the reference list. However, the name had no (integer) following it, and this is only allowed as the first reference entry.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
A bracketed value following a name was found. The value inside the brackets must be an integer.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
A bracketed value following a name was found. The closing bracket following the integer was not found.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when it finds invalid syntax while parsing an OBJECT IDENTIFIER declaration.
An integer, identifier, or '}' was expected. These are the only valid options at this point of an OBJECT IDENTIFIER declaration.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while resolving OBJECT IDENTIFIER references.
This processing occurs after all MIB source has been read. All OBJECT IDENTIFIER declarations and references that had unnumbered names in the definition list are resolved by locating a declaration for the name.
If no declaration for the name can be found, then this error message is produced.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while resolving OBJECT IDENTIFIER references.
This processing occurs after all MIB source has been read. All OBJECT IDENTIFIER declarations and references that had unnumbered names in the definition list are resolved by locating a declaration for the name.
If a name was found, but it was itself not resolved, then this message will count it.
To prevent large numbers of error messages, this message simply indicates how many OBJECT IDENTIFIERs could not be resolved due to unresolved parents. This is because, typically, a single missing declaration can result in many other errors.
Actual undefined OBJECT IDENTIFIER names are reported by message MC6087. Generally, fixing the problems reported by those messages will eliminate this message.
System Action:
Compilation continues.
This message counts as an error.
User Action:
Correct errors indicated by message(s) MC6087 and this message should not appear.
Reason:
This message is produced by the MIB compiler when an internal procedure call passes invalid arguments.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal procedure call passes invalid arguments.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal procedure call passes invalid arguments.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while parsing an OBJECT IDENTIFIER declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when a duplicate declaration for the named type is found.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
The expected token is indicated.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a duplicate identifier is found while processing a type declaration.
This could be a SEQUENCE list or enumeration (named numbers) list.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
One of the shown tokens was expected. However, neither was found.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
At the indicated point, either a named value list, a SIZE clause, or a range specification was expected.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
The identified token was expected after the last-shown token.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a duplicate number is found in a named numbers list .
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a named number list entry has a numeric value of 0.
The use of 0 is strongly discouraged. Refer to RFC1212 (SMI v1) and RFC2578 (SMI v2).
System Action:
Compilation continues.
This message counts as a warning.
User Action:
Probably none. This message can be suppressed by use of the ENUM0 IGNORE compiler option.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
The indicated token is not a valid type name. Type names must be an identifier, and must start with an uppercase letter.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when the range of numbers in a range or SIZE clause is not valid.
At the indicated point, the end number is less than the start number.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a number in the indicated clause is too large.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler at the completion of type resolution. It indicates how many passes over the type table was required to completely resolve all type declarations.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler when an ASN.1 tag number was expected.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when the closing (right) square bracket after an ASN.1 tag number was expected and not found.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when a BITS MIB type reference was found.
The BITS MIB construct is not valid at this point.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
The BITS MIB construct must be followed by an opening brace and a list of bit names.
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler when invalid or unexpected syntax is found while processing a type declaration.
The BITS reference must not have a named bits list definition. (Normally, BITS references within a SEQUENCE are not valid; however, the BITSREF IGNORE option was specified for this compilation. In any case, references to the BITS MIB pseudotype cannot have a named bits list at this point.)
System Action:
Compilation continues with the next statement.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced by the MIB compiler while performing resolution of all type declarations.
The named type was not resolved. This could be due to a preceding error, such as an error in another type declaration, or a missing IMPORT definition.
System Action:
Compilation terminates after completing all type resolution.
This message counts as an error.
User Action:
Determine the reason why the type declaration was not resolved and correct it.
Reason:
This message is produced by the MIB compiler while performing resolution of all type declarations.
The indicated number of type declarations could not be resolved, due to the referenced type itself not being resolved.
This message simply indicates the number of types with this problem. Refer to preceding instances of message MC6160 to determine the parent type(s) that were not declared and why.
System Action:
Compilation terminates after completing all type resolution.
This message counts as an error.
User Action:
Correct the other unresolved types (messages MC6160).
Reason:
This message is produced by the MIB compiler while performing resolution of all type declarations.
A forward-declared type had a clause (as indicated). However, after resolution, the base type that this type was based on does not allow this clause.
System Action:
Compilation terminates after completing all type resolution.
This message counts as an error.
User Action:
Correct the type declaration.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while processing a type declaration.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while adding an imported type definition.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while adding an imported type definition.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while adding an imported type definition.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while adding an imported type definition.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler when an internal error occurs while adding an imported type definition.
System Action:
Compilation is terminated.
User Action:
Contact your product support representative.
Reason:
This message is produced by the MIB compiler at the end of resolution of all NOTIFICATION-TYPE definitions.
No errors were found.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler while performing resolution of all NOTIFICATION-TYPE definitions.
Resolution for the indicated NOTIFICATION-TYPE name failed. The following reasons are possible (the specific reason number is in the message):
1: The assigned value (after the ::=) had a syntax error.
2: The assigned value (after the ::=) was not resolved (as an OBJECT IDENTIFIER value).
3: An OBJECTS entry had a syntax error.
4: An OBJECTS entry could not be resolved as an OBJECT IDENTIFIER value.
System Action:
Compilation terminates after completing all NOTIFICATION-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all NOTIFICATION-TYPE definitions.
The message provides a summary count of the number of NOTIFICATION-TYPE definitions that could not be resolved for a specific reason.
The reason codes are explained in the help for message MC6680.
System Action:
Compilation terminates after completing all NOTIFICATION-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler at the end of resolution of all TRAP-TYPE definitions.
No errors were found.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler while performing resolution of all TRAP- TYPE definitions.
Resolution for the indicated TRAP-TYPE name failed. The following reasons are possible (the specific reason number is in the message):
1: The assigned ENTERPRISE value had a syntax error.
2: The assigned ENTERPRISE value was not resolved (as an OBJECT IDENTIFIER value).
3: A VARIABLES entry had a syntax error.
4: A VARIABLES entry could not be resolved as an OBJECT IDENTIFIER value.
System Action:
Compilation terminates after completing all TRAP-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler whilst performing resolution of all TRAP- TYPE definitions.
The message provides a summary count of the number of TRAP-TYPE definitions that could not be resolved for a specific reason.
The reason codes are explained in the help for message MC6780.
System Action:
Compilation terminates after completing all TRAP-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler at the end of resolution of all OBJECT- TYPE definitions.
No errors were found.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
Resolution for the indicated OBJECT-TYPE name failed. The following reasons are possible (the specific reason number is in the message):
1: The assigned OBJECT IDENTIFIER value (after the ::=) had a syntax error.
2: The assigned OBJECT IDENTIFIER value (after the ::=) was not resolved.
3: The assigned OBJECT IDENTIFIER value for this OBJECT-TYPE is not unique within all OBJECT-TYPE definitions in this MIB.
4: The assigned SYNTAX type definition had syntax errors. (This reason should never occur, and if it is found, the compilation will terminate immediately.)
5: The assigned SYNTAX type defnition was not resolved.
6: One of the INDEX entries had a syntax error (that is, it was not a valid OBJECT IDENTIFIER reference).
7: One of the INDEX entries could not be resolved as an OBJECT IDENTIFIER.
8: The AUGMENTS entry had a syntax error (that is, it was not a valid OBJECT IDENTIFIER reference).
9: The AUGMENTS entriey could not be resolved as an OBJECT IDENTIFIER.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The message provides a summary count of the number of OBJECT-TYPE definitions that could not be resolved for a specific reason.
The reason codes are explained in the help for message MC6880.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The indicated OBJECT-TYPE definition was not a root entry (that is, there were other OBJECT-TYPE definitions with OBJECT IDENTIFIER values that were a prefix of this one), but there were missing ancestor OBJECT-TYPE definitions.
For example, this OBJECT-TYPE could have an OBJECT IDENTIFIER value of 1.3.6.1.5.7.9 but no OBJECT-TYPE was found with a value of 1.3.5.1.5.7.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The indicated OBJECT-TYPE definition had no children defined (based on the OBJECT IDENTIFIER value assigned). However, the assigned type (the SYNTAX clause) was not a base type (or one derived from a base type).
For example, this entry had a type of SEQUENCE OF xxx.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The indicated OBJECT-TYPE definition had a type of SEQUENCE OF but did not have exactly one child OBJECT-TYPE (based on the OBJECT IDENTIFIER values).
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The indicated OBJECT-TYPE definition had a type of SEQUENCE but the number of child OBJECT-TYPE entries (based on the OBJECT IDENTIFIER values) did not match the number of elements defined in the SEQUENCE definition.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler while performing resolution of all OBJECT-TYPE definitions.
The indicated OBJECT-TYPE definition had children defined (based on the OBJECT IDENTIFIER value assigned). However, the assigned type (the SYNTAX clause) was a base type (or one derived from a base type).
For example, this entry had a type of INTEGER.
System Action:
Compilation terminates after completing all OBJECT-TYPE resolution.
This message counts as an error.
User Action:
Correct the error and recompile the MIB.
Reason:
This message is produced by the MIB compiler whenever an error or warning message is produced that can be tied to a specific MIB source position.
The message consists of a single '%' character, which will be positioned under the approximate location on a source line (which will precede this message, with a line number instead of a message prefix).
The error or warning message will follow this message.
NOTE: If mltiple errors or warnings are detected on the same source line, the source line is written once. Each error or warning will be preceded by this message with the appropriate source location. For example:
123456: mib source line here MC7001 % MC???? error description 1 (source...) MC7001 % MC???? error description 2 (line...)
System Action:
None.
User Action:
Review the error or warning message and the MIB source and correct it as required.
Reason:
This message is produced by the MIB compiler during EXPORT processing. It shows how many definitions of a specific type were exported.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the MIB compiler during IMPORT processing. It indicates that the requested item (item.module) could not be imported due to a database error.
The return code from the database handler is shown. An additional error message may also be produced with more information
System Action:
Processing continues.
This message counts as an error.
User Action:
Report this problem to your product support representative.
Reason:
This message is produced if the MIB compiler receives a non-zero return code from the IMPORT/EXPORT database interface handler initialization call.
The EXPORT/MPORT interface is disabled.
System Action:
Compilation proceeds. However, no external IMPORT requests can be honored.
This message counts as an error.
User Action:
Report this to your product support representative.
Reason:
This message is produced if the MIB compiler traps an error during processing of the IMPORT/EXPORT database interface handler initialization call.
The EXPORT/MPORT interface is disabled.
System Action:
Compilation proceeds. However, no external IMPORT requests can be honored.
This message counts as an error.
User Action:
Report this to your product support representative.
Reason:
This message is produced if the MIB compiler receives a non-zero return code from of the IMPORT/EXPORT database interface handler export initialization call.
EXPORT processing is not performed.
System Action:
EXPORT processing is not performed.
This message counts as an error.
User Action:
Report this to your product support representative.
Reason:
This message is produced if the MIB compiler receives an invalid return code from the IMPORT/EXPORT database interface handler.
The function and return code are shown.
System Action:
further EXPORT processing is not performed.
This message counts as an error.
User Action:
Report this to your product support representative.
Reason:
This message is produced if the MIB compiler is unable to recognize the type of definition being imported for the indicated item.
System Action:
IMPORT processing for the indicated item is not performed.
This message counts as an error.
User Action:
Report this to your product support representative.
Reason:
This message is produced if an internal error is detected in the MIB compiler.
System Action:
Compilation terminates.
User Action:
Report this error to your product support representative.
Reason:
This message is produced if the MIB compiler encounters an IMPORT request for an item that is in a module that the compiler regards as internal. However, the item was not found in the internal tables for that module.
This can occur when an item name is misspelt.
System Action:
The item is skipped and processing continues with the next item.
This message is regarded as a warning. However, errors are likely to occur later if the item is referenced.
User Action:
Correct the import name and recompile.
Reason:
This message is produced if the MIB compiler encounters an IMPORT request for an item that is in a module that the compiler regards as internal. The item was found; however, the compiler has already imported items that have set the SMI version. This item has a different SMI version.
The item, module, and current SMI version are displayed.
This can occur when IMPORT requests reference both SMI v1 modules (such as RFC1212-MIB) and SMI v2 modules (such as SNMPv2-SMI).
System Action:
The item is skipped and processing continues with the next item.
This message is regarded as an error.
User Action:
Correct the import list and recompile.
Reason:
This message is produced if an internal error is detected in the MIB compiler.
System Action:
Compilation terminates.
User Action:
Report this error to your product support representative.
Reason:
The MIB compiler detected a hex or binary string ('...'H or '...'B) that did not end before the end of the line.
The compiler does not support these strings crossing lines.
System Action:
Compilation is terminated.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
The MIB compiler detected a hex or binary string ('...'H or '...'B) with an invalid value.
A binary string ('...'B) must only have the characters 0 or 1 between the quotes. If it is being used in a context where a number is expected, it must not have more than 48 digits.
A hex string ('...'H) must only have the characters 0-9 and A-F (upper or lower case) between the quotes. If it is being used in a context where a number is expected, it must not have more than 12 digits.
System Action:
Compilation is terminated.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
The MIB compiler found a quoted string (opened with a single quote ') that did not have a 'B' or 'H' after the closing quote.
Only a B (meaning binary string) or H (meaning hex string) can be specified.
System Action:
Compilation is terminated.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
The MIB compiler found a quoted string (opened with a double quote ") that did not end before the end of the source.
System Action:
Compilation is terminated.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
The MIB compiler found a source character that it could not understand. The position and character are shown (including a hex expansion).
This can be caused by the use of an unsupported ASN.1 construct in the MIB source.
System Action:
Compilation is terminated.
This message counts as an error.
User Action:
Correct the MIB source and recompile.
Reason:
This message is produced if the MIB compiler has found an ASN.1 comment that has a closing delimiter '--' and the LINECMTS IGNORE option was specified. The comment is treated as ending at the end of the line.
Normally, an ASN.1 comment extends from the opening -- until either end-of-line, or a closing --.
Some MIB compilers do not recognize the closing -- and treat all comments as ending at the end of the line. Because of this, some MIB source has comments that contain embedded -- sequences (such as a comment like:
'------------------------'!).
System Action:
The comment is treated as being the rest of the source line.
This message counts as a warning.
User Action:
None. You may correct the MIB source if you wish.
Reason:
This message is produced if the MIB compiler has found an ASN.1 comment that has a closing delimiter '--', but is possibly invalid. The LINECMTS IGNORE option was not specified for this compilation.
The comment is treated as ending at the next '--' after the opening '--'.
If the comment is invalid (such as a line of '-----'), it is very likely that syntax errors will occur.
This message is issued to inform you of possible problems. It is issued once only for any source line.
Investigate the LINECMTS IGNORE option.
Normally, an ASN.1 comment extends from the opening -- until either end-of-line, or a closing --.
Some MIB compilers do not recognize the closing -- and treat all comments as ending at the end of the line. Because of this, some MIB source has comments that contain embedded -- sequences (such as a comment like:
'------------------------'!).
System Action:
The comment ends at the next '--' after the opening '--'.
This message counts as a warning.
User Action:
Depends on related messages for this source line.
Reason:
This message is produced if the MIB compiler has found an identifier in the source that exceeds 48 characters in length.
It is recommended that MIB identifiers not exceed 32 characters. MIBs have been found with longer identifiers, so this compiler accepts lengths up to 48.
However, longer lengths are not accepted.
This message is a warning, to allow compilation to proceed. However, if this message is issued, an error message is issued at the end of compilation showing how many long identifiers were found.
System Action:
None.
This message counts as a warning.
User Action:
Correct the identifier.
Reason:
This message is produced if the MIB compiler encounters an ASN.1 keyword that is not supported.
System Action:
Compilation terminates.
User Action:
Correct the MIB source to remove the unsupported syntax, and then recompile.
Reason:
This message is produced if an internal error is detected in the MIB compiler.
System Action:
Compilation terminates.
User Action:
Report this error to your product support representative.
Reason:
This message is produced if the MIB compiler encounters a fatal error condition. It indicates that all compilation processing is terminated. The ID of the message written when the problem was detected is displayed.
System Action:
Compilation terminates.
User Action:
Examine any previous errors (especially the noted ones) and correct them as required.
Reason:
This message is produced if the MIB compiler has an internal error condition. It indicates that all compilation processing is terminated. The ID of the message written when the problem was detected is displayed.
System Action:
Compilation terminates.
User Action:
Report this to your product support representative.
| Copyright © 2012 CA. All rights reserved. |
|