Dear Team,
After further investigation, we noticed the following:
The source IP (10.132.70.1) is associated with the 5G-S1-U domain. but the VRF routing table on the source node shows that the destination IP is mapped under VRF = LTE-Media.
@Eyob Tatek, could you kindly check this configuration on your side?

Dear Team,

As mentioned by Eyob, we already have the route domain associated with the IP in the dump file. Therefore, for CoreElement, the route domain should be parsed directly from the dump file along with the IP data information.
Dear @Aurobinda Panda, kindly share this request with the AI Team.
BR,

ticket created for AI - OMAN-7263

we will check once concluded

Route domain data imported in NEP but still error of duplicate IP is not resolved

last status on this issue is that redundancy report is blank but HSRP IP is avaiable in IP data so we need to know next step to resolve duplicate IP case that is probably causing cloud on 4G

to check if the solution of LS-561 solved this issue.

@Eyob, Interface issue has been resolved for now. Kindly check.

The duplicate IP are now correctly represented in different VRF

Hi team, I've been following this LS-502 ticket closely as we are seeing a similar IP duplication issue in our current 5G-S1-U domain deployment. Since Eyob mentioned that the duplicate IPs are now correctly represented in different VRFs, I was wondering if this fix also accounts for the specific routing logic used in the updated 2026 frameworks, like those mentioned in this technical overview at http://guiadeleovegasargentina.com? I'm trying to determine if our issue is a pure configuration overlap or if we need to implement the same VRF mapping logic you used here to resolve the cloud on 4G. Thanks!