Ok - I think you guys have figured it out and have helped me understand this better. By following your suggestions to model the device manually, I got the message:
--- Error discovering the device at 172.19.222.221. This device has responded to an ICMP ping request, but not to an SNMP request. Probable causes for SNMP failure: *The device may not be responding to SNMP requests. If the device is busy with network traffic, SNMP requests could be ignored. *Timeout and Retry values could be too low. Increase and try again. *Community name "public" may be incorrect. SNMP devices will not respond to SNMP requests if the Community Name is not valid for the device. *Check the device for Access Lists. If the device has an Access List, your machine will have to be added to receive SNMP requests. *For Site or Branch Manager versions of SPECTRUM, the total device counter may be at maximum level. --- The problem is that I am sending this as a trap but the device, a PC in this case, doesn't have an SNMP listener on it. So, spectrum can't contact it. I guess spectrum needs to do a handshake? Once I turned on the listener, things work as desired. Thanks for your help! ________________________________ From: HUNGERFORD, CLIFF [AG/1000] [mailto:[email protected]] Sent: Friday, April 03, 2009 10:52 AM To: spectrum Cc: spectrum Subject: RE: [spectrum] trap based discovery Steve, Couple of other things to check, in the order of most likely to least likely: Does the Community name Spectrum will use to contact the device match what's on the device itself? In other words, it sounds like you have Spectrum set up to accept any traps with the Community Name of 'public,' but Spectrum will use a separate community name as defined in the Tools -->Utilities -->Discovery --> New Discovery tool. There should be some community names in there. Spectrum will try them in the order listed. The next thing I'd check is that the device itself doesn't have an access list that excludes the SpectroSERVER's IP address/Community Name. Lastly, and least likely, I would recommend checking your Thread Information (under the SpectroSERVER Control tab), to make sure that you aren't maxed out on your Notification threads, and have some Notification Latency, but since you can see the traps in the VNM, I don't think that's a problem. If none of those are the issue, then I'm stumped. Cliff From: Steve Kato [mailto:[email protected]] Sent: Friday, April 03, 2009 12:40 PM To: HUNGERFORD, CLIFF [AG/1000] Subject: RE: [spectrum] trap based discovery Yes - I have the correct community name. I am using net-snmp to do the tests. My test trap is: snmptrap -v 1 -c public 172.19.222.121 1.3.6.1.4.1.1234 "" 6 1 "" 1.3.6.1.4.1.1234.1 s "test trap" ________________________________ From: HUNGERFORD, CLIFF [AG/1000] [mailto:[email protected]] Sent: Friday, April 03, 2009 10:32 AM To: spectrum Subject: RE: [spectrum] trap based discovery Steve, I don't think you've missed anything; it should work. I assume you've already checked the SNMP Community name, to make sure that the devices are sending what Spectrum is expecting. I'm doing it here with three different SNMP ports. Works like a charm. From: Steve Kato [mailto:[email protected]] Sent: Friday, April 03, 2009 12:09 PM To: spectrum Subject: [spectrum] trap based discovery Hi - I have set up trap based continuous discovery and enabled unmanaged trap handling but do not get any new devices when I send a trap from a new device. I can see the traps coming in going to the VNM events, but I thought trap based continuous discovery would automatically create a new model under New Devices. Any hints? Is there some configuration I'm missing? Steve Kato Recreational Equipment Inc. (REI) http://www.rei.com <http://www.rei.com/> email: [email protected] phone: 253-437-7309 * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
