
Hello,
If a table element is declared as a particular type in the Entry and later declared as a different type in its declaration part, it is not given as an error by the libsmi tool.
For example, PppGzipStatusEntry ::= SEQUENCE { pppGzipStatusIfIndex INTEGER, pppGzipStatusRxIfWindowSize INTEGER, pppGzipStatusTxIfDecompressedDataSize Counter32 }
pppGzipStatusTxIfDecompressedDataSize OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { pppGzipStatusEntry 3 }
Here "pppGzipStatusTxIfDecompressedDataSize" is declared as Counter32 type in 'PppGzipStatusEntry' but later declared as INTEGER in its definition part. This should be given as an error. But libsmi tool doesn't check for these mistakes!!!!!
Kind Regards, Vivekanandan.V
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

Hi!
Vivekanandan> If a table element is declared as a particular type in Vivekanandan> the Entry and later declared as a different type in its Vivekanandan> declaration part, it is not given as an error by the Vivekanandan> libsmi tool.
Thank you! I've added an appropriate check. A freshly updated libsmi from the anonymous CVS repository should now report an error like...
RFC1269-MIB:353: type of `bgpPathAttrInterASMetric' in sequence and object type definition do not match
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
participants (2)
-
Frank Strauss
-
Vivekanandan V