
Hello List,
I get the following errors when I compile the attached MIB. Would anyone explain me what the severity 1 errors are?
Thanks, Bala
smilint -m -s -l 6 -i namelength-32 mailbody
mailbody:155: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:156: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:509: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:515: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:799: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:808: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:848: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:868: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:1265: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:1266: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:200: [1] {} unknown object identifier label `medGwyConfiguration' mailbody:525: [1] {} unknown object identifier label `medGwyGatewayControllerTable' mailbody:517: [2] {parent-row} row's parent node must be a table node mailbody:818: [1] {} unknown object identifier label `medGwyTermIdTable' mailbody:810: [2] {parent-row} row's parent node must be a table node mailbody:878: [1] {} unknown object identifier label `medGwyTerminationsTable' mailbody:870: [2] {parent-row} row's parent node must be a table node mailbody:1176: [3] {notification-object-access} object `medGwyTerminationId' of notification `medGwyInvalidTerminationId' must not be `not-accessible' mailbody:1211: [3] {notification-object-access} object `medGwyGatewayId' of notification `medGwyGatewayHandoff' must not be `not-accessible' mailbody:1211: [3] {notification-object-access} object `medGwyGatewayControllerId' of notification `medGwyGatewayHandoff' must not be `not-accessible' mailbody:1223: [3] {notification-object-access} object `medGwyTerminationId' of notification `medGwyProtocolError' must not be `not-accessible' mailbody:1304: [1] {} unknown object identifier label `medGwyCompliances' mailbody:456: [4] {group-membership} warning: node `medGwyGatewayRowStatus' must be contained in at least one conformance group mailbody:901: [4] {group-membership} warning: node `medGwyTerminationName' must be contained in at least one conformance group mailbody:911: [4] {group-membership} warning: node `medGwyTerminationAdminStatus' must be contained in at least one conformance group mailbody:936: [4] {group-membership} warning: node `medGwyTerminationOperStatus' must be contained in at least one conformance group mailbody:960: [4] {group-membership} warning: node `medGwyTerminationInterfaceIdentifier' must be contained in at least one conformance group mailbody:971: [4] {group-membership} warning: node `medGwyTerminationPropertyProfileId' must be contained in at least one conformance group mailbody:982: [4] {group-membership} warning: node `medGwyTerminationRowStatus' must be contained in at least one conformance group mailbody:1074: [4] {group-membership} warning: node `medGwyPropertyProfileProperty' must be contained in at least one conformance group mailbody:1084: [4] {group-membership} warning: node `medGwyTermPropertyProfileStatus' must be contained in at least one conformance group mailbody:1145: [4] {group-membership} warning: node `medGwyReceivedElement' must be contained in at least one conformance group mailbody:85: [5] {type-without-format} warning: type `MediaGatewayId' has no format specification mailbody:92: [5] {type-without-format} warning: type `MediaGatewayLinkId' has no format specification mailbody:99: [5] {type-without-format} warning: type `MediaGatewayTermId' has no format specification

Balasubramanian Pitchandi wrote:
Hello List,
I get the following errors when I compile the attached MIB. Would anyone explain me what the severity 1 errors are?
mailbody:155: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT [...]
The MIB module you attached does NOT lead to such smilint error messages. Maybe, you encapsulated the MIB module in your email in a way that is not supported by the smilint mail robot. Read the mail robot's help text for more details or install the libsmi software and run it locally.
participants (2)
-
Balasubramanian Pitchandi
-
Frank Strauß