search cancel

Old IP's are reflecting in log files after DC migration, eventhough New IP's are updated in CFG files

book

Article ID: 229366

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We had a DC migration on Aug 15th 2021 in which our core CA-UIM servers IP got updated. After upgradation we have updated the new IP's in all the required Configuration files. While we are working on something else yesterday, we identified that in one the regional hub log file we could see old primary and failover IP's are reflecting.

150.xxx.x.xxx is old primary Hub 

150.xxx.xxx.xxx is old failover Hub

Environment

Release : 20.3

Component : UIM - HUB

Resolution

1. hub/robot version
Make sure you’re running hub v9.32HF1 or higher.
 
 
along with the latest robot version.
 
 
Hotfix site:
 
2. niscache
On the hubs / robots showing the old/wrong IPs I would recommend that you clear the niscache and reset the robot ids. Please first make sure that you’re not running hub v9.31 anywhere in your environment.
 
How to clear the niscache on an individual robot
 
 3. nas Name Services
Check to make sure that none of the OLD IPs show up under any hosts in the nas Name Services tab entries.