From: Kenneth Wygand (KWygand@customonline.com)
Date: Fri Apr 23 2004 - 11:47:23 GMT-3
Thanks for testing this out Yasser. The end result is now we all know
exactly how it works! Thanks for your input! :)
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"The only unattainable goal is the one not attempted."
-Anonymous
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Yasser Abdullah
Sent: Friday, April 23, 2004 10:35 AM
To: 'ccie2be'; 'Jonathan Hays'; ccielab@groupstudy.com
Subject: RE: Specifying SNMP Traps
Tim/Jonathan,
I just tested it, you are correct. Traps have to be explicitly enabled
with the 'snmp-server enable traps' command in order to be eligible to
be sent to a host. The host command can be used to filter unwanted
traps.
I stand corrected; sorry for the confusion I caused.
Thanks,
Yasser
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Friday, April 23, 2004 5:03 PM
To: Yasser Abdullah; 'Jonathan Hays'; ccielab@groupstudy.com
Subject: Re: Specifying SNMP Traps
Yasser,
I don't think the rtr will send the "config" traps. Here's why: the
config
trap is NOT enabled in a snmp-server enable trap command.
Contrary to what I originally thought, except for the default traps like
link-status and tty, unless all traps are enabled (by leaving off
specific
traps in the snmp-server enable trap command, only the traps explicitly
specified by the snmp-server enable traps command can be sent.
Here are my new conclusions:
use the snmp-server host to specify where to send traps and
1) if traps are included with the command, only those traps will be sent
but
only if they are enabled with the snmp-server enable trap command.
2) if no traps are explicitly included with the commands, all traps
enabled
with the snmp-server enable traps commands will be sent.
Therefore the snmp-server host command can be used to select a subset of
traps enabled by the snmp-server enable trap commands.
And, in the lab, based on your earlier post, if ONLY certain traps
should be
sent to a host and those traps don't include link-status, one must
remember
to explicitly disable the link-status traps on each active interface or
lose
all points for the snmp section.
Tim
----- Original Message -----
From: "Yasser Abdullah" <yasser@alharbitelecom.com>
To: "'Jonathan Hays'" <nomad@gfoyle.org>; <ccielab@groupstudy.com>
Sent: Friday, April 23, 2004 9:01 AM
Subject: RE: Specifying SNMP Traps
> Let us just ignore the tty for a second and consider the following:
>
> Snmp-server host 10.10.10.10 public bgp config
> Snmp-server enable traps bgp
>
> Would the router send host 10.10.10.10 config traps?
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Jonathan Hays
> Sent: Friday, April 23, 2004 3:40 PM
> To: ccielab@groupstudy.com
> Subject: RE: Specifying SNMP Traps
>
> you wrote:
> >-----Original Message-----
> >From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> >Behalf Of Yasser Abdullah
> >Sent: Friday, April 23, 2004 7:36 AM
> >To: 'ccie2be'; 'Tim Last'; 'Group Study'
> >Subject: RE: Specifying SNMP Traps
> >
> >
> >Yes, it is actually a term used to describe traps or informs.
> >
> >No, the type of traps doesn't need to be specified twice, at least
not
> >all. In your example, bgp, config and tty were specified in the host
> >command. However, this command alone doesn't automatically send
traps.
> >You need to activate the sending of traps by issuing the snmp-server
> >enable traps at least for one of the traps types.
> >
> >In the example below, you could have done with only one snmp-server
> >enable traps commands.
> >
> >snmp-server host 10.10.10.10 public config bgp tty
> >snmp-server enable traps config
> >
> >In this case, all hosts will get the config traps, but only host
> >10.10.10.10 will get the bgp and tty traps.
> >
> >Brgds,
> >
> >Yasser
> >
> = = =
>
> Sorry, but I disagree. See my example below. It is important to
actually
> implement these examples in your lab, rather than must assuming how
> things work from the documentation. The fact is that the IOS will
> automatically create the 'snmp-server enable traps tty' command. The
> documentation is a bit lax in this area.
>
>
> R2#sh run | include snmp
> R2#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> R2(config)#snmp-server host 10.10.10.10 public config bgp tty
> R2(config)#end
> R2#
> *May 9 15:59:27.173: %SYS-5-CONFIG_I: Configured from console by
> console
> R2#sh run | include snmp
> snmp-server enable traps tty
> snmp-server host 10.10.10.10 public tty config bgp
> R2#
>
> HTH,
>
> Jonathan
>
>
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:53 GMT-3