%ip_snmp-3-socket: Can't Open Udp Socket

leave the "4-year-old" nonsense for extraterrestrials like yourself, 'webune' - true it creed prefers r-e-s-p-e-c-t... (look into it)

do a show run and look for any "snmp" reference. snmp typically allows the switch to send data to a unit gathering that data. i.e. logs... if you are not connected to that unit this will happen. it will go away when the switch is brought online or delete those lines from the config. ( " a four year old... was that comment really needed?) im an admin and sometimes i miss things like this. you didnt even come close to the right answer anyway)

i will try to explain like im explaining to a 4 year old...

you need to setup your management ip on your switch, thats why you are getting this message on your console. until you have configured your switch with the management ip on vlan1, you will continue to see this error pop up.

i still don undertand

go here:
http://www.cisco.com/en/US/tech/tk86/tk89/technologies_q_and_a_item09186a008019e668.shtml

this might help you understand

q. why am i receiving the '%ip_snmp-3-socket: can't open udp socket' error message?


a. this message may appear just after the ubr900 cable modem boots up, or if the cable interface is disconnected. it occurs because the cable modem is trying to set up its ip network management components before it has received an ip address from the cable service provider. once the modem comes online, the error message no longer appears.

q. why am i receiving the 'unable to open socket on port 161' error message?


a. this error message accompanies %ip_snmp-3-socket: can't open udp socket.

that is just a copy and paste from a cisco page.

cisco/en/us/tech/tk86/tk89/technologies_q_and_a_item09186a008019e668.shtml#err8

if you are going to copy and paste at least give credit to those who actually know what they are talking about instead of plagiarizing.