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/OT-83 Ooredoo Tunisia <p>Dear All,</p> <p>As discussed, the connector names need to be parsed exactly as defined in the FRS, and they should remain unique per project for both Nokia_RAN and Huawei_RAN.</p> <p>I have updated the FRS accordingly, and the finalized connector names are as follows (Which is generally parse under header “importerConnector”):</p> <p>• Huawei RAN: Huawei_RAN_Ooredoo_TUN<br/> • Nokia RAN: NSN_RAN_Ooredoo_TUN</p> <p>Currently, it is parsing as below:</p> <p>Huawei RAN: Huawei_M2000 (Snippet attached)<br/> Nokia RAN: Header is missing</p> <p>@Bassem Sabbagh, please advise if these names need to be revised and guide us further on this.</p> <p>Best regards,<br/> Indrasan</p> OT-83

Connector Name Should Be Parse As Available In FRS

Task Normal Closed Fixed Indrasan Yadav Indrasan Yadav AI_All_incidents Huawei_RAN_OO Nokia_RAN_OO Mon, 29 Sep 2025 11:12:03 +0300 Wed, 7 Jan 2026 11:23:58 +0200 Wed, 7 Jan 2026 10:50:52 +0200 Fri, 3 Oct 2025 00:00:00 +0300 0 5 0 minutes 4 days, 5 hours, 30 minutes <p>Dear <a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=bsabbagh" class="user-hover" rel="bsabbagh">Bassem Sabbagh</a>,</p> <p>I have created a common JIRA for this issue. Kindly assign an AI DEV resource to investigate and resolve it.</p> <p>Assigned to Ashutosh to define the WL ... WIP</p> <p>Both Huawei and NSN ran csv-outputs attached with suggested names.<br/> Note: I have only changed the existing importer connector nothing else.</p> <p>Hi Sandya,</p> <p>As discussed, the Importer ID and Importer Connector are still missing in almost all tables in the CSV output.</p> <p>XML shared.</p> <p>Hi Sandya,</p> <p>Please check the attached excel sheet where I have mentioned the parsing connector name and need to check where it is parsing incorrect.</p> <p>Sandhya to define the WL</p> <p>WL is half day.</p> <p>to be delivered in 14-10 the first half</p> <p>It is done , but as discussed with indrasan he said that upload the csv after fix all the issue related to jira <a href="http://jira.mobinets.com/jira/browse/OT-84" title="Nokia RAN Data Validation In Staging-DB" class="issue-link" data-issue-key="OT-84"><del>OT-84</del></a>.</p> <p>ticket to be assigned to Indrasan and CSVs to be shared with integration and to be loaded in SD</p> <p>csv-output shared with integration and uploaded in staging db.</p> <p>importor connector name is not mendatory for each csv , it is discussed with driss sir, and for addinfo or error alarm we are using the common code for each connector, there is error coming for others connector while i change the code for addinfo , we can fix it by change in each connnector seperatly.</p> <p>Dear @Sandya Sharma,</p> <p>Please find the validation remarks: (Green-Fixed, Blue-Ignore, without any colour-To be check)</p> <p>I consider the latest one Importer Id=’20251016091426_2025-10-16-09.14.26’</p> <p>Updated list (<a href="http://jira.mobinets.com/jira/browse/OT-83" title="Connector Name Should Be Parse As Available In FRS" class="issue-link" data-issue-key="OT-83"><del>OT-83</del></a> (Nokia RAN) is attached for your reference.</p> <p>to be fixed by 29-10</p> <p>csv output shared with integration</p> <p>Hi Sandya, could you please confirm if Integration has uploaded it? I am unable to find any email regarding this.</p> <p>As confirmed this is included in the CSV output which is shared for <a href="http://jira.mobinets.com/jira/browse/OT-84" title="Nokia RAN Data Validation In Staging-DB" class="issue-link" data-issue-key="OT-84"><del>OT-84</del></a>.</p> <p><a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=bsabbagh" class="user-hover" rel="bsabbagh">Bassem Sabbagh</a> in meantime please assign this to <a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=jthakur" class="user-hover" rel="jthakur">Jharna Thakur</a> to fix for Huawei RAN.</p> <p>Jharna to define the WL ... started on 4-11</p> <p>WIP and to be delivered by 5-11</p> <p>Done with this, will share the CSV output with the resolution for <a href="http://jira.mobinets.com/jira/browse/OT-85" title="Huawei RAN Data Validation In Staging-DB" class="issue-link" data-issue-key="OT-85"><del>OT-85</del></a>.</p> <p>CSVs are shared with integration</p> <p>Hi @Sandya Sharma,</p> <p>Please find latest validation feedback for Importer Connector for Nokia RAN:</p> <p>Consider Importer ID: 20251107090325_2025-11-07-09.03.25</p> <p>Still Importer Connector is not correct for below tables:</p> <p>CSV-Output Table Name<br/> NodeInterface<br/> RadioAntenna<br/> SubInterface<br/> ElementCell5g<br/> ElementCellRadioBandWidth<br/> ElementTrx<br/> LogicalInterface</p> <p>Please check the updated data and confirm.</p> <p>Hi @Sandya Sharma,</p> <p>Please find below validation feedback for latest importer id: 20251111023300_2025-11-11-02.33.00</p> <p>Still Importer Connector is not correct for below tables:</p> <p>CSV-Output Table Name<br/> NodeInterface<br/> SubInterface<br/> ElementCell5g<br/> ElementTrx</p> <p>WIP and to be fixed by 13-11</p> <p>CSV output shared with integration.</p> <p>1- Nokia RAN:</p> <p>Connector name is parsing OK in all possible tables except below which can be ignored:<br/> (II) Site<br/> (III) Error alarm</p> <p>2- Huawei RAN:</p> <p>Connector name is parsing OK in all possible tables except below:<br/> (II) Site<br/> (III) Error alarm<br/> (IV) Sub interface: Missing somewhere in table (To be check by <a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=jthakur" class="user-hover" rel="jthakur">Jharna Thakur</a></p> <p>Hi <a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=jthakur" class="user-hover" rel="jthakur">Jharna Thakur</a> please commit the code for connector name missing issue in Huawei RAN for table "Sub interface" as it is fixed now withing <a href="http://jira.mobinets.com/jira/browse/OT-45" title="Site Matching_Huawei RAN" class="issue-link" data-issue-key="OT-45"><del>OT-45</del></a> CSV output.</p> <p>Hi Jharna,</p> <p>The issue was initially identified in the Sub Interface table, where the importer connector was missing. You had fixed this earlier. However, while validating the latest data on the server using the importer ID 20251231015405_2025-12-31-01.54.05 (shared by Basant on 31-12-2025), I noticed that the importer connector issue is now appearing in additional tables as well either it is missing or incorrect 'Huawei_M2000'.</p> <p>The following tables are affected, even though they were previously fixed (except for Sub Interface):</p> <p>1- BATCH_ELEMENT_CELL_RADIO_BAND_WIDTH<br/> 2- BATCH_ELEMENT_GSM_CELL_MAIO<br/> 3- BATCH_ELEMENT_TRX<br/> 4- BATCH_ELEMENT_TRX_ARFCN<br/> 5- BATCH_IP_DATA<br/> 6- BATCH_LOGICAL_INTERFACE<br/> 7- BATCH_NETWORK_ELEMENT_DUMP<br/> 8- BATCH_NODE_INTERFACE<br/> 9- BATCH_RADIO_ANTENNA<br/> 10- BATCH_SUB_INTERFACE<br/> 11- BATCH_VIRTUAL_INTERFACE</p> <p>Kindly review and fix the importer connector issue for the above tables as well.</p> <p>XML and CSVs are generated with no issues on local laptop of Jharna ... it could be integration issue ... L2 to generate again the XML and share it for validation ...</p> <p>I have checked the staging database and the issues have now been resolved.<br/> Previously, the Omantel connector was executed instead of the Ooredoo Huawei RAN connector, which caused the discrepancy. This has been corrected.</p> <p>Now, issue has been fixed for both connector Nokia RAN (Already fixed earlier) &amp; Huawei RAN (Now fixed):</p> <p>Connector name is parsing OK in all possible tables except below which can be ignored:<br/> (II) Site<br/> (III) Error alarm</p> <p>2- Huawei RAN:</p> <p>Connector name is parsing OK in all possible tables except below:<br/> (II) Site<br/> (III) Error alarm</p> Actual End Wed, 7 Jan 2026 10:50:52 +0200 Actual Start Mon, 29 Sep 2025 00:00:00 +0300 Baseline End Fri, 3 Oct 2025 00:00:00 +0300 Baseline Start Fri, 3 Oct 2025 00:00:00 +0300 Customer Date of Baselining Mon, 29 Sep 2025 11:34:42 +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, 3 Oct 2025 00:00:00 +0300 Planned Start Fri, 3 Oct 2025 00:00:00 +0300 Rank 0|xtiqwp: Rank (Obsolete) 9223372036854775807 VTDirections