MIB Designer export patch change for brain-dead parsers?

[McWilliams, Gary]

Nope, that's my problem. I'll change that setting. However, it would still
be nice to be able to have the oid comments generated at the end of the
line. It's not a major issue though.


-----Original Message-----
From: Frank.Fock____t-online.de [mailto:Frank.Fock____t-online.de]
Sent: 12 March 2002 19:23
To: Gary McWilliams
Cc: agentpp-dl____agentpp.com
Subject: Re: MIB Designer export patch change for brain-dead parsers?


Gary,

You can deactivate the generation of the extra ASN.1 comments dynamically
created by MIB Designer in MIB Designer's preferences. This should avoid
any problems with parsers that cannot handle ASN.1 comments correctly.

This option is available in the current MIB Designer. But may be you have
different problem? May be you can explain it in more details then?

Thanks in advance,
Frank

Gary McWilliams wrote:

> Is there any update on this question (I have the same problem).
>
> Is this something that will (may be optional?) be included in a future
> release?
>
> -----Original Message-----
> From: Martin Janzen [mailto:janzen____pixelmetrix.com]
> Sent: 18 February 2002 11:38
> To: agentpp-dl____agentpp.com
> Subject: MIB Designer export patch change for brain-dead parsers?
>
> Hi!  I'm wondering whether it'd be possible to get a minor change in the
way
> in which MIB Designer writes exported MIBs.  The 1.7 version adds a
comment
> containing the numeric OID value, as follows:
>
>   tspEventPIDBandwidthAboveMaxThreshold NOTIFICATION-TYPE
>       OBJECTS      { ... }
>       STATUS       current
>       DESCRIPTION  "..."
>     -- 1.3.6.1.4.1.6768.6.4.5.0.1000 --  ::= { tspEventsV2 1000 }
>
> That's nice information to have; but I'd prefer to see this:
>
>   tspEventPIDBandwidthAboveMaxThreshold NOTIFICATION-TYPE
>       OBJECTS      { ... }
>       STATUS       current
>       DESCRIPTION  "..."
>       ::= { tspEventsV2 1000 }  -- 1.3.6.1.4.1.6768.6.4.5.0.1000 --
>
> Background: Some network management systems I've run into have broken MIB
> parsers, which don't seem to be aware that a second "--" is supposed to
> terminate a comment.  Therefore, the important bits are lost, resulting in
> lots of load errors, frustrated customers, etc.
>
> Yes, I know we should abuse NMS vendors who do this, and so help to rid
the
> world of this sort of thing; but in the meantime, putting the comment at
the
> end of the line would ensure that the MIB always works.
>
> Thanks in advance...
>



_____________________________________________________________________
This message has been checked on behalf of CCC Network Systems for all known
viruses by the MessageLabs Virus Control Centre.


________________________________________________________________________________________

The information in this Internet email is confidential and intended for the sole use of the addressee(s).  Access, copying, disclosure or re-use, in any way, of the information contained in this email by anyone other than the addressee(s) is unauthorised Internet communication and may not be secure.  

CCC Network Systems, Inc. accepts no legal responsibility for the content of the message.  Any opinions or views presented are solely the responsibility of the author and do not necessarily represent those of CCC Network Systems, Inc.

If you have received this email in error, please return it to postmaster at cccnetsys.com and the sender.

CCC Network Systems, Inc. may monitor the content of emails sent and received via its network in accordance with applicable legislation for the purposes of ensuring its compliance with its policies and procedures. 

This message has been checked on behalf of CCC Network Systems, Inc. for all known viruses by the MessageLabs Virus Control Centre; however, CCC Network Systems, Inc. do not warrant that it is virus-free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.agentpp.org/pipermail/agentpp/attachments/20020312/6ef75eff/attachment.htm