MIB Designer export patch change for brain-dead parsers?

[Gary McWilliams]

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...

--
Martin Janzen
janzen at pixelmetrix.com


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com