snmp traps and snmp_mgr

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

snmp traps and snmp_mgr

chandru
This is because snmp_mgr will only receive traps from one agent only. This
is the agent you would have specified in snmp_mgr:start  - It can be easily
extended to receive traps from multiple agents. I did it once and threw it
away cos no one in EEI was interested ;)

The crash you see is in the function snmp_mgr_misc:packet_loop/7

cheers,
Chandru

> -----Original Message-----
> From: Adrian John Cahill [mailto:cahill]
> Sent: 1 March 2001 16:11
> To: erlang-questions
> Subject: snmp traps and snmp_mgr
>
>
>
> Hi ,
>     I am trying to receive snmp traps using an erlang application. I
> have tried using the snmp_mgr:expect( id, any) function, this returns
> ok, for most of my requests, but when a trap is fired, the
> following is
> displayed in my 'erl interpreter'
>
> ** exited: {snmp_packet_got_other,{udp,
>                                       #Port<0.37>,
>                                       {143,239,159,221},
>                                       1070,
>                                       [48,
>                                        65,
>                                        2,
>                                        1,
>                                        1,
>                                        4,
>                                        6,
>                                        112,
>                                        117,
>                                        98,
>                                        108,
>                                        105,
>                                        99,
>                                        167,
>                                        52,
>                                        2,
>                                        1,
>                                        2,
>                                        2,
>                                        1,
>                                        0|...]}} **
>
> Could someone shed some light on this??  Is this the trap, as
> i can see
> no correllation between this, and what should have been sent
> back ?? So
> is it an error message??
>
> Am i not creating the trap correctly ?. I am creating the
> trap in a Java
> program / Agent .
>
> Tia Adrian
>



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

snmp traps and snmp_mgr

Ciaran Johnston
Does this hold for gets and sets also?

Ciaran.

Chandrashekhar Mullaparthi wrote:

>
> This is because snmp_mgr will only receive traps from one agent only. This
> is the agent you would have specified in snmp_mgr:start  - It can be easily
> extended to receive traps from multiple agents. I did it once and threw it
> away cos no one in EEI was interested ;)
>
> The crash you see is in the function snmp_mgr_misc:packet_loop/7
>
> cheers,
> Chandru
>
> > -----Original Message-----
> > From: Adrian John Cahill [mailto:cahill]
> > Sent: 1 March 2001 16:11
> > To: erlang-questions
> > Subject: snmp traps and snmp_mgr
> >
> >
> >
> > Hi ,
> >     I am trying to receive snmp traps using an erlang application. I
> > have tried using the snmp_mgr:expect( id, any) function, this returns
> > ok, for most of my requests, but when a trap is fired, the
> > following is
> > displayed in my 'erl interpreter'
> >
> > ** exited: {snmp_packet_got_other,{udp,
> >                                       #Port<0.37>,
> >                                       {143,239,159,221},
> >                                       1070,
> >                                       [48,
> >                                        65,
> >                                        2,
> >                                        1,
> >                                        1,
> >                                        4,
> >                                        6,
> >                                        112,
> >                                        117,
> >                                        98,
> >                                        108,
> >                                        105,
> >                                        99,
> >                                        167,
> >                                        52,
> >                                        2,
> >                                        1,
> >                                        2,
> >                                        2,
> >                                        1,
> >                                        0|...]}} **
> >
> > Could someone shed some light on this??  Is this the trap, as
> > i can see
> > no correllation between this, and what should have been sent
> > back ?? So
> > is it an error message??
> >
> > Am i not creating the trap correctly ?. I am creating the
> > trap in a Java
> > program / Agent .
> >
> > Tia Adrian
> >
>
> NOTICE AND DISCLAIMER:
> This email (including attachments) is confidential.  If you have received
> this email in error please notify the sender immediately and delete this
> email from your system without copying or disseminating it or placing any
> reliance upon its contents.  We cannot accept liability for any breaches of
> confidence arising through use of email.  Any opinions expressed in this
> email (including attachments) are those of the author and do not necessarily
> reflect our opinions.  We will not accept responsibility for any commitments
> made by our employees outside the scope of our business.  We do not warrant
> the accuracy or completeness of such information.


Loading...