http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-502 L3 Support <p>it is found that IP is duplicated for Core Router &amp; Core Element.</p> LS-502

Routing Troubleshooting_Duplicated IP

Bug Normal Open Bug Unresolved Eyob Tatek Aurobinda Panda MS_OT Service_routing Wed, 9 Jul 2025 12:28:19 +0300 Wed, 18 Mar 2026 08:11:53 +0200 NEP Fri, 18 Jul 2025 00:00:00 +0300 0 5 0 minutes 1 day, 7 hours <p>Dear Team,<br/> After further investigation, we noticed the following:<br/> 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.<br/> @Eyob Tatek, could you kindly check this configuration on your side?</p> <p>Dear Team,</p> <p>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.<br/> Dear @Aurobinda Panda, kindly share this request with the AI Team.<br/> BR,</p> <p>ticket created for AI - OMAN-7263 </p> <p>we will check once concluded</p> <p>Route domain data imported in NEP but still error of duplicate IP is not resolved</p> <p>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</p> <p>to check if the solution of <a href="http://jira.mobinets.com/jira/browse/LS-561" title="OT | SubInterface available in IP Data missing in Subinterface report in NEP." class="issue-link" data-issue-key="LS-561"><del>LS-561</del></a> solved this issue.</p> <p>@Eyob, Interface issue has been resolved for now. Kindly check.</p> <p>The duplicate IP are now correctly represented in different VRF </p> <p>Hi team, I've been following this <a href="http://jira.mobinets.com/jira/browse/LS-502" title="Routing Troubleshooting_Duplicated IP" class="issue-link" data-issue-key="LS-502">LS-502</a> 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 <a href="http://guiadeleovegasargentina.com?" class="external-link" rel="nofollow">http://guiadeleovegasargentina.com?</a> 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&#33;</p> multi-level hierarchy [GANTT] Actual Start Wed, 9 Jul 2025 00:00:00 +0300 Baseline End Fri, 18 Jul 2025 00:00:00 +0300 Baseline Start Fri, 18 Jul 2025 00:00:00 +0300 Complexity Customer Date of Baselining Thu, 10 Jul 2025 11:51:45 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Fri, 18 Jul 2025 00:00:00 +0300 Planned Start Fri, 18 Jul 2025 00:00:00 +0300 REQUESTER Rank 0|xtio55: Rank (Obsolete) 9223372036854775807 VTDirections