From: Mingzhou Nie (mnie@yahoo.com)
Date: Tue Oct 15 2002 - 23:40:38 GMT-3
Just realized that I made a mistake in my reply. the
"%IP_SNMP-3-SOCKET: can't open UDP socket " message is only shown up
when no interface has ip address configured. There was a thread a
couple of months ago regarding this and I answered it.
So eanble snmp-server host w/o snmp-server community is fine.
--- Mingzhou Nie <mnie@yahoo.com> wrote:
> You don't really have to. w/o "snmp-server community" line, port 161
> is
> not opened and most likely you will get complaint like this.
>
> %IP_SNMP-3-SOCKET: can't open UDP socket 161
>
> Also note that the community in "snmp-server host" can be anything.
> To
> send out a trap, you really don't need a community. But the trap PDU
> still requires it to fill out the field.
>
> Ming
>
> --- Ayman Hamza <ayhamza@cisco.com> wrote:
> > Dear all;
> >
> > In the configuration shown in the URL below:
> >
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/1218ea1/3550scg/swadmin.htm#xtocid72
> >
> > For me it's very clear except for one thing :
> >
> >
> > Should I configure the global config mode command
> >
> > snmp-server community <community-string> {rw|ro}
> >
> > for the community used for the MAC-notification trap used in the
> > command:
> >
> > snmp-server host <ip> {traps|informs} version <version> <community>
> > mac-notification
> >
> > Appreciating any comments !
> >
> > Best wishes;
> > Ayman
>
>
> =====
> Mingzhou Nie, CCIE #10342
>
> __________________________________________________
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
=====
Mingzhou Nie, CCIE #10342
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:47 GMT-3