ciscoworks&ACS integration

Unanswered Question
Mar 18th, 2008

We have ciscoworks LMS 2.6 working under ACS mode. It works fine. But sometimes when a L3 device add a new ip interface,even the device's old IP have been added in ACS, this device will appear in not configured in ACS report. Ask ACS admin add it in ACS, everything OK. But I don't think it is a good solution for such case, any other way to solve the root cause?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Joe Clarke Tue, 03/18/2008 - 20:53

As long as the device's IP address does not change in DCR, and is still valid in ACS, then the device should not appear in the Devices not in ACS report. What exactly are you doing when you add a new IP to a device?

ly633 Wed, 03/19/2008 - 00:41

Hi, Jclarke,

You are right, I find the management IP address in DCR is changed to the new ip, (ofcause, I have to break the connection between ciscoworks and ACS, then I can see this device in DCR),which is in 'not configured in ACS report'. Why this happens?

This time, we add one loopback ip address, then the management IP changed.

ly633 Thu, 03/20/2008 - 01:59

Any reply? I modify it yesterday in DCR to the ip in ACS, but it changed back today again.

Joe Clarke Thu, 03/20/2008 - 06:14

The management IP of a device can change if you are using discovery, and the resolution algorithm you have chosen finds a new address. For example, if you've chosen to resolve hostnames by name, then depending on how your DNS is configured, the management IP address (and hostname) can change depending on which interface of the device discovery sees first. If you want to use loopbacks (which is a good idea) set your resolution method to Resolve By Loopback, and make sure the IP on the loopback with the lowest ifIndex resolves to the proper hostname, and that hostname resolves back to the IP address that you want to use as your management address.

Actions

This Discussion