IP SLA enabled devices

Unanswered Question
Nov 24th, 2008
User Badges:

I have re-installed the CW LSM3.0 and complete all the updates. However, IPM can only detects 1 device as IP SLA enabled devices while there are more than 50 devices detected as IP SLA enabled before the un-installation. Can anyone advise me on that?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Tue, 11/25/2008 - 06:41
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Make sure the reimported devices have the correct SNMP read-only community strings (or SNMPv3 credentials) configured in DCR. Additionally, make sure that you have configured IPM to auto-sync all devices from DCR.

jeeyishyuan Tue, 11/25/2008 - 23:56
User Badges:

Hi jclarke,


I have verified the SNMP RO community strings. All devices are also imported to IPM. However, I have only 1 IP SLA enabled device after the re-installation. Before that, I have more than 50. This also means that, I can only have 1 device to set as source device when creating collector. Any advice? Thanks!

Joe Clarke Thu, 11/27/2008 - 09:47
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Enable IPMSERVER debugging under IPM > Admin > Loglevel Settings. Then, remove all your devices from IPM, and re-add the devices from DCR (all done under IPM > Collector Mgmt > Devices). Then post the ipmprocess.log.

jeeyishyuan Fri, 11/28/2008 - 01:38
User Badges:

Remove is to delete All devices from IPM? Will it cause All Devices to be deleted from DCR too? How can I re-add the devices? Via the Add button under IPM?

Joe Clarke Fri, 11/28/2008 - 09:59
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

You did not enable debugging as I had instructed.

Joe Clarke Sun, 11/30/2008 - 21:19
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I am seeing multiple IP SLA capable devices in this log. Which devices are not showing up as valid IP SLA source devices?

jeeyishyuan Sun, 11/30/2008 - 18:44
User Badges:

Hi jclarke,


Another problem that I have encountered is a Tomcat error. I have tried to stop and start some IPM processes including Tomcat Monitor process but the problem remained unsolve. Hope to hear some advice from you too. Thank you very much!


Regards

YS



Joe Clarke Sun, 11/30/2008 - 21:17
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This is bug CSCsl37260 which is fixed in IPM 4.1. However, it is simply masking an error in your collector configuration. You have not done something correctly when configuring your collector. Typically, this means you did not select a source or target device.

jeeyishyuan Sun, 11/30/2008 - 21:22
User Badges:

Hi jclarke,


Thanks for your great response. But I still have another problem is the IPM has no any source device for me to select in the source device list. As requested, I have uploaded another ipmprocess.log file to show the debugging status. Can you advise me on that? Thanks



Attachment: 
Joe Clarke Sun, 11/30/2008 - 21:28
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

As I said in my previous reply, I see many devices that IPM is correctly discovering. For example, 10.11.251.2, 10.34.250.210, 10.34.250.193, and 10.34.250.226 are all properly discovered, and supported for IP SLA.


Is this LMS server integrated with ACS?

jeeyishyuan Sun, 11/30/2008 - 21:42
User Badges:

No ACS is integrated with the LMS server. Currently, I have all Devices listed in IPM Device list. However, there are no device listed under the source list to configure collector.


Two screen shots are attached to show the IPM device list and IPM source device list.


Regards

YS



Attachment: 
Joe Clarke Sun, 11/30/2008 - 21:56
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

There may be a problem with your IPM database. Shut down CiscoWorks Daemon Manager, then run:


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=ipm dmprefix=Ipm


Once the database is reinitialized, restart Daemon Manager, and try re-syncing devices from DCR.

jeeyishyuan Sun, 11/30/2008 - 23:36
User Badges:

Hi jclarke,


I have run the command as posted in your previous reply. But problem still remained unsolve. I have also attached the debugging ipmprocess.log while i am running and re-syncing the ipm database. Please advise.


Is this consider a bug in IPM?


Thanks and Regards

YS



Attachment: 
Joe Clarke Mon, 12/01/2008 - 06:33
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

At this point, I recommend you open a TAC service request so some live debugging, and database analysis can be done.

Actions

This Discussion