04-20-2007 10:24 AM
I cannot add a new collector to my IPM configuration. I get the error message:
AddCollErr
REASON: Response Timed Out
Recently I've stopped and deleted old collectors and targets. I only have 2 collectors running.
I'm using LMS 2.6, IPM 2.6 on a Windows 2003 Server.
Solved! Go to Solution.
04-20-2007 12:56 PM
While you can certainly reinitialize the IPM database with:
ipm dbclean
This may be as simple as a bad read-write community string (or SNMP credential) for the source device. You might try starting a sniffer trace filtering on all SNMP traffic to your source device when trying to add the collector, and see if anything obvious stands out.
04-20-2007 10:52 AM
You might want to try this:
1. Stop all IPM processes.
2. Goto
3. Modify the parameters in the ipm.env file -
IPM_SNMP_TIMEOUT=10
IPM_SNMP_RETRIES=5
4. Start all IPM processes
5. Retry to see if the problem still exists.
Hopefully increasing the timeouts help.
04-20-2007 12:51 PM
No joy!
Is there a procedure to cleanse/rebuild the IPM database?
04-20-2007 12:56 PM
While you can certainly reinitialize the IPM database with:
ipm dbclean
This may be as simple as a bad read-write community string (or SNMP credential) for the source device. You might try starting a sniffer trace filtering on all SNMP traffic to your source device when trying to add the collector, and see if anything obvious stands out.
04-20-2007 11:11 PM
Thanks Joe! That really did the trick. There've been so many changes over the last few months to the overall Topology of the network that I think re-initializing the IPM Database was the best option. Adding new devices and collectors is real quick now. Thank You I really appreciate the help and your quickness to respond to our posts on this Forum.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide