BUG: Changing IP of existing device does not update monitors
BUG:
Service monitors (TCP port checks) do NOT get updated properly when you change a device's IP after the device has been added to OM8.
I confirmed this two ways:
1. The original device I scanned (1.2.3.4) was pingable and had 21,80,443,3389 open
2. The device IP I changed to (1.2.3.5) after the fact only has port 25 and 80 open, yet the monitors still show port 21, 443, 3389 as "available" and up.
3. I checked the MySQL DB, and in the table opmanagerdb.managedobject, the entries under NAME and PARENTKEY still have the old (1.2.3.4) IP in them. So, I am guessing that they are ACTUALLY monitoring 1.2.3.4 instead of 1.2.3.5
Service monitors (TCP port checks) do NOT get updated properly when you change a device's IP after the device has been added to OM8.
I confirmed this two ways:
1. The original device I scanned (1.2.3.4) was pingable and had 21,80,443,3389 open
2. The device IP I changed to (1.2.3.5) after the fact only has port 25 and 80 open, yet the monitors still show port 21, 443, 3389 as "available" and up.
3. I checked the MySQL DB, and in the table opmanagerdb.managedobject, the entries under NAME and PARENTKEY still have the old (1.2.3.4) IP in them. So, I am guessing that they are ACTUALLY monitoring 1.2.3.4 instead of 1.2.3.5
Topic Participants
Mike
roshini philip
opmanager_support
gabrielme
Jeremy Cooper