Hello
a) I concatenated our exchanged mails in the end
b) Traps are always send to a single client (10.140.20.69)
c) "and so on..." means: elements/parameters in SNMP v2 protocol e.g.. As in an
example
time
14:02:55.912422
source
10.93.112.14.32771
destination
10.140.20.69.162
.1.3.6.1.2.1.1.3(sysUpTime )
1246333
.1.3.6.1.6.3.1.1.4.1(snmpTrapOID)
.1.3.6.1.4.1.193.109.2.0.3(elnLinkUp)
.1.3.6.1.4.1.193.72.500.1.1.0 (param1...managedObjectClass) EAN
.1.3.6.1.4.1.193.72.500.1.2.0 (param2...managedObjectInstance)
EAN=10.93.112.14,EFN324xf,Port=1002.0.12
.1.3.6.1.4.1.193.72.500.1.3.0 (param3...sequenceNumber) 24
.1.3.6.1.4.1.193.72.500.1.4.0 (param4...perceivedSeverity) 1
.1.3.6.1.4.1.193.72.500.1.5.0 (param5...eventTime)
07_dc_01_11_0d_02_37_59_2b_00_00
.1.3.6.1.4.1.193.72.500.1.6.0 (param6...eventTypePem) 2
.1.3.6.1.4.1.193.72.500.1.7.0 (param7...probableCause) 65
d) client (10.140.20.69) is defined to work with SNMP v2 protocol
e) Reading FAQ "How can I get the agent to send an SNMPv1 (or SNMPv2c) trap?"
and an answer there:
"....It doesn't make any difference whether you use the v1-style API
call 'send_easy_trap()' or the v2-style 'send_v2trap()'.
What matters is the directive(s) in the snmpd.conf file.
If this file contains 'trapsink', then the agent will send an
SNMPv1 trap. If this file contains 'trap2sink', then the
agent will send an SNMPv2c trap. ...."
open/give to me the possibility to find the way how to solve my idea/problem.
Kind Regards,
ZELJKO MIHELCIC
Network Operations Center
-----Original Message-----
From: NetSNMP Mailbox [mailto:[email protected]] On Behalf Of Robert
Story
Sent: Dienstag, 28. Februar 2012 17:29
To: Zeljko Mihelcic
Cc: [email protected]; NetSNMP Mailbox
Subject: Re: command snmptrap (a command line interface) using SNMP v2
Please try to use the Reply feature of your mail app, instead of creating a new
message. The keeps the chain of messages together, making it easier for readers
to refer back to past messages.
On Tue, 28 Feb 2012 09:45:57 +0100 Zeljko wrote:
ZM> I'd like to use the command snmptrap to reach following scenarios
ZM>
ZM> Agent Client
ZM> (10.140.20.71) (10.140.20.69)
ZM> | |
ZM> snmptrap * | |
ZM> =========> | |
ZM> | Notification (SNMP v2) |
ZM> | ============================> |
ZM> | source ** |
ZM> | destination (10.140.20.69) |
ZM> | and so on... |
- snmptrap does not communicate with the agent, it sends traps directly to the
specified host.
- are you always sending traps to a single client? Or does "and so on..." mean
that you need to send the same trap to multiple clients?
ZM> * snmptrap -v 2c [COMMON OPTIONS] [-Ci] uptime trap-oid [OID
ZM> TYPE VALUE]... Note: there is no possibility to generate wanted
ZM> source with this command, i.e. Agent address (10.140.20.71) will be
ZM> always in source
This is true for all v2/v3 traps. We don't support spoofing the source address
in the udp packet.
Why not use v1 traps, which contain the 'agent' in the PDU itself (which can
easily be set via snmptrap)?
======================================= sent : Di 28.02.2012 09:46
=============================================================
Hello Mr.Robert Story
Here is more clearly written my problem...
I'd like to use the command snmptrap to reach following scenarios
Agent Client
(10.140.20.71) (10.140.20.69)
| |
snmptrap * | |
=========> | |
| Notification (SNMP v2) |
| ============================> |
| source ** |
| destination (10.140.20.69) |
| and so on... |
| |
| |
* snmptrap -v 2c [COMMON OPTIONS] [-Ci] uptime trap-oid [OID TYPE VALUE]...
Note: there is no possibility to generate wanted source with this command,
i.e. Agent address (10.140.20.71) will be always in source
** One of IP address from FTTH (fiber to the home) network
e.g. SmartMetro (10.93.50.111) or ECN (10.93.112.3)
Note: in the source should not be Agent address (10.140.20.71)
Kind Regards,
ZELJKO MIHELCIC
Network Operations Center
===================================== sent: Mo 27.02.2012 19:39
===============================================================
On Mon, 27 Feb 2012 17:03:34 +0100 Zeljko wrote:
ZM> I'd like to use the command snmptrap to reach following scenarios
ZM>
ZM> Agent Client
ZM> (10.140.20.71) (10.140.20.69)
ZM>
ZM> | |
ZM> | Notification (SNMP v2) |
ZM> | ============================> |
ZM> | source * |
ZM> | destination (10.140.20.69) |
ZM> | and so on... |
ZM> | |
ZM> | |
ZM>
ZM>
ZM> * One of IP address from FTTH (fiber to the home) network
ZM> e.g. SmartMetro (10.93.50.111) or ECN (10.93.112.3)
ZM> Note: in the source should not be Agent address (10.140.20.71)
What is actually generating the traps? You said you wanted a command line
interface to send traps, so I still don't understand where the agent comes in,
and why you can't simply use snmptrap to simulate the traps?
================================== sent: Mo 27.02.2012 17:04
==================================================================
Hello Mr.Robert Story
I'd like to use the command snmptrap to reach following scenarios
Agent Client
(10.140.20.71) (10.140.20.69)
| |
| Notification (SNMP v2) |
| ============================> |
| source * |
| destination (10.140.20.69) |
| and so on... |
| |
| |
* One of IP address from FTTH (fiber to the home) network
e.g. SmartMetro (10.93.50.111) or ECN (10.93.112.3)
Note: in the source should not be Agent address (10.140.20.71)
Kind Regards,
ZELJKO MIHELCIC
Network Operations Center
================================= sent: Mo 27.02.2012 16:39
===================================================================
On Fri, 24 Feb 2012 14:36:55 +0100 Zeljko wrote:
ZM> I'd like to work with net-snmp agent , i.e. using it to send traps
ZM> to the snmp manager with a command line interface on Linux Idea is
ZM> to simulate expected traps from FTTH (fiber to the home) network
ZM> build with different nodes (SmartMetro, LG Ericsson and Ericsson
ZM> family - ENC/EFN). SNMP protocol is version 2
Why do you want to use snmpd, instead of using snmptrap?
==================================sent: Fr 24.02.2012
14:37==================================================================
Dear
I'd like to work with net-snmp agent , i.e. using it to send traps to the snmp
manager with a command line interface on Linux
Idea is to simulate expected traps from FTTH (fiber to the home) network build
with different nodes (SmartMetro, LG Ericsson and Ericsson family - ENC/EFN).
SNMP protocol is version 2
Reading available documentations (Net-SNMP) following variants/possibilities
are points where I didn't find my solution:
a) snmptrap -v 1 [COMMON OPTIONS] [-Ci] destination enterprise-oid agent
generic-trap specific-trap uptime [OID TYPE VALUE]
b) snmptrap -v2c [COMMON OPTIONS] [-Ci] uptime trap-oid [OID TYPE VALUE]...
c) mapping/trap generator "send_easy_trap" vs "send_v2trap"
Could you help me with an idea how to reach this task ?
Kind Regards,
ZELJKO MIHELCIC
Network Operations Center
Ericsson
Freiburgstrasse 251
3018, Bern, Switzerland
Mobile +4179 328 91 90
[email protected]
www.ericsson.com
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
