Managed System IP address change

[khanand]

Running SIM 4.2 SP1

Some hosts showing unreachable via ping.

The hosts have recently had an IP address change, therefore according to SIM 'dead' SIM still shows old IP address.

Looks like SIM uses IP and not FQDN / netbios for ping check.

Is there anyway of making SIM automatically rediscover the new IP ?

[jim goodman]

You can try to do a re-identification of the system. I don't know if it supposed to dynamically update or not upon a reun of the identification task.

Typically - though I end up having to delete and rediscover the server to get the db to update.

- Jim

[Brent Seizer]

On the CMS server go to the home page and select the auomatic discovery section. Select the option that says to discover new systems as traps are encountered.

Also delete the systems from the list based on the OLD IP addresses. Even if the system is discovered under the new IP address, CMS will see this as a new and seperate system.

Until you delete the systems under their old IP address the CMS will still attempt top talk to that system under the old address.

If the system was listed in DNS ensure that DNS was updated with the new IP address.

[khanand]

Seems strange that the CMS will only use IP only for ping checks, I would have thought using the FQDN made more sense. Or at least have the ability to use both.

With over 1500 hosts, IP address changes are not out of the normal ...

If there is a way the change can be automated - please post ....

[Pat Wilson_1]

If the CMS used the FQDN for ping checks, then you would be doing that many DNS calls every time you performed the polling task(s). Since normally servers have fixed IP addresses this is not usually an issue, but I agree - with 1500 hosts, you are bound to have a few changes.

[Brent Seizer]

This becomes a matter of organization.
While servers typically have fixed IP addresses, it is sometimes neceessary to change their IP address because the server is being recycled and used for a new purposee.

In my case, I do not scan the entire subnet.
I have 4 subnets with a 255.255.255.0 mask. The server IP address is only allowed to fall within a very small portion of that subnet. The CMS server only scans this range, and not the entire subnet.

All my printers are among 8 subnets with a 255.255.254.0 mask. Again the printer IP address is only allowed to fall within a very small portion of that subnet, so I only scan those addresses.

All of this to say that you can narrow the number IP addresses that CMS has to ping if you group your servers and printers into a known group of addresses. This will make the discovery process faster, and not discover all of the other things you dont want to manage.