[Fwd: converstion of a v2 notification to v1 trap]
Kevin Baughman <klb@eng.paradyne.com> Mon, 19 May 1997 12:11 UTC
Received: from cnri by ietf.org id aa26241; 19 May 97 8:11 EDT
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa04899; 19 May 97 8:11 EDT
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id HAA19336 for snmpv2-outgoing; Mon, 19 May 1997 07:37:06 -0400 (EDT)
Message-ID: <337CC43A.253F@eng.paradyne.com>
Date: Fri, 16 May 1997 16:31:54 -0400
From: Kevin Baughman <klb@eng.paradyne.com>
Reply-To: klb@eng.paradyne.com
Organization: Paradyne
X-Mailer: Mozilla 3.0 (Win95; I)
MIME-Version: 1.0
To: snmpv2@tis.com
Subject: [Fwd: converstion of a v2 notification to v1 trap]
Content-Type: multipart/mixed; boundary="------------673F4BBE62A8"
Sender: owner-snmpv2@ex.tis.com
Precedence: bulk
Hi, I never got a response to this email. I'm not on the mailing list, so you'll have to respond directly to me. Thanks! -- Kevin Baughman ____ Paradyne, LG133 klb@eng.paradyne.com \ / 8545 126th Ave N Phone: (813) 530-8378 \/ Largo, FL 33773-2826 Fax: (813) 532-5244
--- Begin Message ---Hi, rfc2037 (entity mib) defines a entConfigChange notification (see below). When implementing this trap for a v1 agent, what should the enterprise be? entityMIBTraps, entityMIBTrapPrefix or something else? The reason I ask is that I think it should be entityMIBTraps, so that when a v2 agent converts this to a notification the result would be entityConfigChange. However, when the v2 mib is sent to mib-v2tov1@simple-times.org the result specifies entityMIBTrapPrefix. Using this, the conversion would result in an oid with *two* "0"s in it! Thanks, Kevin ======================================================== entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 } entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 } entConfigChange NOTIFICATION-TYPE STATUS current DESCRIPTION "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." ::= { entityMIBTrapPrefix 1 } ========================================================= -- automatically generated by mosy 7.2 #166 (yukinojo), do not edit! entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 } entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 } entConfigChange TRAP-TYPE ENTERPRISE entityMIBTrapPrefix DESCRIPTION "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 ================================================ -- Kevin Baughman ____ Paradyne, LG133 klb@eng.paradyne.com \ / 8545 126th Ave N Phone: (813) 530-8378 \/ Largo, FL 33773-2826 Fax: (813) 532-5244--- End Message ---
- converstion of a v2 notification to v1 trap Kevin Baughman
- [Fwd: converstion of a v2 notification to v1 trap] Kevin Baughman
- RE: converstion of a v2 notification to v1 trap David Perkins