Mib Designer 1.8.6

[Frank.Fock____t-online.de]

Hi Dave,

Dave Barratt schrieb:
> Yes thats it...
> 
> Another 'bug' is sometimes the last item is a list of
> oids disappears.  This
> doesn't happen when the node is a parent only when its a
> child.  It doesn't
> seem to happen reliably though....
> 
Could please explain what you exactly mean by
"list of oids"? A list of object names, for example in
a group?

> I've been using the tool alot this week & one enhancement
> which would be
> nice to the ability to copy, drag & drop whole tables.  I
> have alot of
> tables that are basically similar & a feature like this
> would speed things
> up for me.  I find myself dropping into a text editor to
> just copy & paste
> the table & then modifying it to then load back into the
> Designer tool.
> 
OK, tables can already be moved at once using the Drag&Drop
feature. I will try to add the copying too, for the
next release.

> Another is in the parser to show all error messages in
> the log rather than
> just the first one the parser encounters.
> 
Of course, this would be nice, however it is rather costly
to implement because the parser has to guess the correct
syntax in order to be able to proceed to the next error.

Nevertheless, this feature will definitly come with the 
2.0 release.

Best regards,
Frank

> Dave
> 
> ----- Original Message ----- 
> From: "Frank Fock" <Frank.Fock____t-online.de>
> To: "Dave Barratt" <dave____thedrums.freeserve.co.uk>
> Cc: <agentpp-dl____agentpp.com>
> Sent: Wednesday, April 30, 2003 8:59 AM
> Subject: Re: Mib Designer 1.8.6
> 
> 
> > It's like you wrote, the "File\Export MIBs..." ignores
> the
> > setting in the Preferences. That's not what one would
> expect
> > and thus I will change (fix) it. An update should be
> available
> > on Friday.
> >
> > Best regards,
> > Frank
> >
> > Dave Barratt wrote:
> > > Thanks Frank that's fixed it as long as you choose
> the 'export current
> mib &
> > > save as text' button.  Going through the Export MIBs
> dialog from
> File\Export
> > > Mib doesn't have the same effect of sorting by oid. 
> Could be a bug.  I
> use
> > > this route cause I need the mib in plain text with no
> tabs & in SMIv1
> (our
> > > in-house compiler is a bit flaky!).
> > > Dave
> > >
> > > ----- Original Message ----- 
> > > From: "Frank Fock" <Frank.Fock____t-online.de>
> > > To: "Dave Barratt" <dbarratt____codimatech.com>
> > > Cc: <agentpp-dl____agentpp.com>
> > > Sent: Tuesday, April 29, 2003 8:54 PM
> > > Subject: Re: Mib Designer 1.8.6
> > >
> > >
> > >
> > >>Hi Dave,
> > >>
> > >>Please disable (uncheck) the following check boxes
> > >>in the Edit>>Preferences dialog (General>>MIB
> Generation):
> > >>
> > >>"Preserve original order of parsed MIB objects"
> > >>"Order generated MIB objects by their type first"
> > >>
> > >>Please let me know if the problem does not disappear
> then!
> > >>
> > >>Best regards,
> > >>Frank
> > >>
> > >>Dave Barratt wrote:
> > >>
> > >>>Hi,
> > >>>I have problems compiling the text export output
> from Mib Designer with
> > >>>our in-house Mib compiler because it doesn't always
> order the Mib in
> > >>>'lexicographical' or sequencial order.  For an
> example see below...
> > >>>
> > >>>segSecPort1 OBJECT IDENTIFIER      ::= {
> expHisSegSeconds 7 }
> > >>>segSecBroadcast OBJECT IDENTIFIER  ::= {
> expHisSegSeconds 2 }
> > >>>segSecIcmp OBJECT IDENTIFIER  ::= { expHisSegSeconds
> 5 }
> > >>>
> > >>>Is there any way of getting output to be like
> below?
> > >>>
> > >>>segSecBroadcast OBJECT IDENTIFIER  ::= {
> expHisSegSeconds 2 }
> > >>>segSecIcmp OBJECT IDENTIFIER  ::= { expHisSegSeconds
> 5 }
> > >>>segSecPort1 OBJECT IDENTIFIER      ::= {
> expHisSegSeconds 7 }
> > >>>
> > >>>Dave Barratt
> > >>>Developer
> > >>>Codima Technologies - redefining the art of network
> management
> > >>>E-mail:  dbarratt at codimatech.com
> <mailto:dbarratt____codimatech.com>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> >
> >
> >
> 
> 
>