Problem monitoring one server, it shows incorrect IP form UIM Database

[davidms]

Hi

I have a problem monitoring one server (cosifbi1), if we see the CONTROLLER Configuration it shows the correct IP (10.52.21.23), but if we serch the server from UIM Database, when we see the registry of this server it shows one incorrect IP,  This ip es of another server, when there is one event of  the cosiftbi1 it shows the ip incorrect, How can we correct this problem from the database?

We attach some evidence 

Could you help us please?

Best regard.

[Gregg Stillwell]

Few things to check. Verify ifconfig(or ipconfig) shows all the correct information on this robot. Also verify that the /etc/hosts does not have a bad entry for itself or reference the IP. And verify an reverse nslookup on both IP's (correct one and incorrect one) and hostname return correct data. I had this issue when DNS lookup on host returned a bad IP. Will see if there is  a KB.

[Gene Howard]

Making changes to the database will not help as they will be overwritten.
You can check the cm_computer_stsrem table for the cs_id field.
Then check the cm_device table for matching entries.
Then check the cm_device_attribute table to find out where the data was retrieved from.
You have something in your environment with the incorrect IP address, that some part of UIM is picking up.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Andrew Cooper]

David

We sometimes used to see a similar problem to this (especially multi-ip windows servers).

As Gene indicates fiddling with the DB directly is never a good idea (harsh experience speaking here) for this sort of thing.  What we found worked best especially multi ip devices is:

• specify the robot ip in the robot.cfg (rather than auto select)
• ensure dns record (both forward and reverse) math the name and ip that you are using
• shutdown the robot and in USM or AC delete the node (but allow rediscovery)
• wait about 10 minutes (can be shorter) but need to give time for UIM to propagate the change through the DB and back to the other component caches (like udm_manager)
• start the robot and see that it appears in AC/USM with the correct ip. wait for the change to propagate into the DB and check the cm_computer_system record.

Good luck, we had lots of "fun" purging the invalid ips from the system.

Note: do this when a discovery is not running so it is the robot hat is triggering the record to be placed in the db not discovery and finally ensure that the discovery dns is the same (or has the same information) as the dns used by the robot.

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------