SMICng and the PacketCable/IPCablecom NCS Signaling MIB
Woundy, Richard <RWoundy <at> broadband.att.com>
2002-09-19 22:18:28 GMT
Folks,
I ran SMICng against the PacketCable/IPCablecom NCS Signaling MIB,
<http://www.ietf.org/internet-drafts/draft-schell-pktc-ipcdn-signaling-00.tx
t>.
Prior to compiling, I had to change the ææ and ÆÆ into double quotes
(throughout this MIB in particular), and had to fix the LAST-UPDATED time in
the MODULE-IDENTITY object. This MIB also had a special syntactical problem
with the binary DEFVAL's -- we have to define a binary number in the form
'11110000'B rather than just 11110000, per RFC 2578 section 11.1. These were
the original binary value syntax errors:
E: f(PKTC-SIG-MIB.mi2), (313,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (325,21) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (336,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (538,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (549,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (560,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (571,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (582,21) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (594,21) number too big (max is
(Continue reading)