RE: converstion of a v2 notification to v1 trap

David Perkins <> Wed, 21 May 1997 07:35 UTC

Received: from cnri by id aa24338; 21 May 97 3:35 EDT
Received: from by CNRI.Reston.VA.US id aa02920; 21 May 97 3:35 EDT
Received: (from majordom@localhost) by (8.8.2/8.8.2) id DAA04553 for snmpv2-outgoing; Wed, 21 May 1997 03:19:20 -0400 (EDT)
Date: Wed, 21 May 97 00:21:20 pdt
From: David Perkins <>
Subject: RE: converstion of a v2 notification to v1 trap
X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc.
Message-ID: <>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Precedence: bulk


It looks like MOSY v7.2 is not doing the correct translation.
Here is what you get from SMICng v2.1.03:

-- MIB created 5/21/97 00:16:43, by
--   SMICng version 2.1.03(PRO)(MS-DOS32), February 12, 1997.


-- From file: "rfc2037.mi2"

            FROM SNMPv2-SMI-v1
    TDomain, TAddress, DisplayString, AutonomousType, RowPointer, 
            FROM SNMPv2-TC-v1
            FROM RFC-1212
            FROM RFC-1215;

... stuff deleted here

entConfigChange TRAP-TYPE
-- Reverse mappable trap
    ENTERPRISE entityMIBTraps
--  Status
--    mandatory
        "An entConfigChange trap is sent when the value of 
        entLastChangeTime changes. It can be utilized by an NMS to 
        trigger logical/physical entity table maintenance polls. 
        An agent must not generate more than one entConfigChange 
        'trap-event' in a five second period, where a 'trap-event' 
        is the transmission of a single trap PDU to a list of trap 
        destinations.  If additional configuration changes occur 
        within the five second 'throttling' period, then these 
        trap-events should be suppressed by the agent. An NMS should 
        periodically check the value of entLastChangeTime to detect 
        any missed entConfigChange trap-events, e.g. due to 
        throttling or transmission loss."
    ::= 1

... stuff deleted here



/, David T. Perkins
Date: 05/21/97, Time: 00:21:20