[OT-85] Huawei RAN Data Validation In Staging-DB Created: 29/Sep/25  Updated: 13/Jan/26  Due: 30/Nov/25  Resolved: 13/Jan/26

Status: Closed
Project: Ooredoo Tunisia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Indrasan Yadav Assignee: Indrasan Yadav
Resolution: Fixed Votes: 1
Labels: AI_All_incidents, Huawei_RAN_OO
Remaining Estimate: 30 minutes
Time Spent: 2 weeks, 2 days, 5 hours, 40 minutes
Original Estimate: Not Specified

Customer:
Ooreedo Tunisia
Planned Start:
Planned End:
Actual Start:
Actual End:
Date of Baselining:

 Description   

Dear @Jharna Thakur,

As I requested to @Basant Kumar yesterday to generate the XML for Huawei RAN and upload the CSV output on staging DB (IMPORTERID='20251015115622_2025-10-15-11.56.22'), after upload done I checked the data on staging DB.

Could you please review the following points identified during data validation in the staging database for Huawei RAN:

1. Counts Verified (OK):

The data count is correct for the following tables:
Cabinet, Shelf, Slot, BSC, eNodeB, SRAN, RNC, Site, Role2G, Role3G.

2. Counts Not OK (Incomplete Data Uploaded):

The data count is incomplete for the following tables:
Boards, Error Alarms, Network Elements Dump, AddInfos.

3. No Data Uploaded:

The following tables currently have no data uploaded:
eNodeB Bandwidths, GSM Cell MAIO, IP Data, Loopback Interface, 4G Cell, Net Status, 2G Cell, 3G Cell, TRX, Radio Antenna, Sub Interfaces, 3G Carrier, TRX ARFCN, Virtual Interfaces, Cell Radio Bandwidths, Cell Tracking Area.

4. Extra Data Observed:

Extra/unexpected data is appearing in the following table:
Node Interfaces.

5. Importer Connector:

The importer connector is still not appearing as per given in FRS as mentioned in OT-83. You may coordinate with @Sandya Sharma to resolve this issue.

6. Remaining Validation Points:

The remaining common points for confirmation have already been raised under OT-84 (being handled by Sandya).

Thank you,
Indrasan



 Comments   
Comment by Bassem Sabbagh [ 17/Oct/25 ]

Integration has to generate anew xml and validate the data in SD ... no work from AI dev so far

Comment by Bassem Sabbagh [ 27/Oct/25 ]

there is one property missing in the conf file and shared by Jharna ... integration to add the missing property and regenerate the XML and upload the CSVs

Comment by Indrasan Yadav [ 28/Oct/25 ]

Dear @Jharna Thakur,

Please the count validation comments on the staging DB related to the initial issues.

Importer ID: 20251027105108_2025-10-27-10.51.08

Note: Detailed validation feedback for each table will be shared once the review is completed.

1. Counts Verified (OK):

The data count is correct for the following tables:

Except highlighted one remains are fixed.

Cabinet, Shelf, Slot, BSC, eNodeB, SRAN (NOK-No data updated), RNC (NOK-No data updated), Site, Role2G, Role3G.

2. Counts Not OK (Incomplete Data Uploaded):

The data count is incomplete for the following tables:

Except highlighted one remains are fixed.

Boards (NOK-count seems higher), Error Alarms (NOK-No data updated), Network Elements Dump, AddInfos.

3. No Data Uploaded:

Except highlighted one remains are fixed.

The following tables currently have no data uploaded:
eNodeB Bandwidths, GSM Cell MAIO, IP Data (NOK-No data updated), Loopback Interface (NOK-No data updated), 4G Cell, Net Status (NOK-No data updated), 2G Cell, 3G Cell, TRX, Radio Antenna, Sub Interfaces, 3G Carrier, TRX ARFCN, Virtual Interfaces, Cell Radio Bandwidths, Cell Tracking Area.

4. Extra Data Observed:

Extra/unexpected data is appearing in the following table:
Node Interfaces (OK).

5. Importer Connector: (As discussed @Jharna Thakur, It will be taking care by @Sandya Sharma)

Thank you
Indrasan

Comment by Jharna Thakur [ 05/Nov/25 ]

I have verified and found no differences between my locally generated CSVs and the ones shared from the server. thus, I've mailed to integration to upload the CSVs in Db

Comment by Indrasan Yadav [ 06/Nov/25 ]

Hi @Jharna Thakur,

Please find below the data validation summary on the Staging DB, based on the latest CSV upload shared by @Basant Kumar.

1. Counts OK in the below tables:
(I) BSC
(II) RNC
(III) BTS
(IV) NodeB
(V) eNodeB
(VI) SRAN
(VII) Role2G
(VIII) Role3G
(IX) Role4G
(X) Cabinet
(XI) Shelf
(XII) Radio Antenna
(XIII) 2G Cell
(XIV) 3G Cell
(XV) 4G Cell
(XVI) IP

2. Counts Not OK in the below tables:

(I) Board – 18,170 boards are getting parsed extra, while their parent Node / Cabinet / Shelf are not parsed
(II) Sites – Showing 6388, whereas expected as per static sheet is 6527

3. No data updated in below table:

(I) Loopback Interface

4. Tables where some header fields have blank values which should be parsed:

Table Name Missing / Blank Fields
Role3G: Operator / Parent RNC
Role2G: BTS / Operator (Header missing)
IP Data: Node ID / Dumps Path (blank at some places)
Radio Antenna: Supplier
4G Cell: MCC / MNC / Supplier
ENodeB: MCC / MNC / Operator
RNC: MCC / MNC / Operator
BSC: MCC / MNC / Operator
Node Cabinet: Node Type
Node Shelf: Cabinet Index / Node ID
Node Board: Dumps missing somewhere / Node ID
Node Slot: Dumps Path missing in few entries / Node ID / Node Type

Thank you
Indrasan

Comment by Jharna Thakur [ 07/Nov/25 ]

WL- 1.5 Days

Comment by Bassem Sabbagh [ 07/Nov/25 ]

WIP and to be delivered by 10-11 the first half

Comment by Bassem Sabbagh [ 10/Nov/25 ]

CSVS to be shared with integration to load them in SD by today

Comment by Jharna Thakur [ 10/Nov/25 ]

CSVs are shared with integration

Comment by Indrasan Yadav [ 12/Nov/25 ]

Hi @Jharna Thakur,

Please find below validation remarks for latest CSV uploaded by @Basant Kumar against previous raised issue,

Consider Importer ID: 20251110014851_2025-11-10-01.48.51

Table Name Missing / Blank Fields
Role3G: Operator 12-11: Still same / Parent RNC
Role2G: BTS 12-11: Fixed / Operator (Header missing) 12-11: Still same

Note: As we discussed this will be fix once you will fix the issue for OT-110

Regarding Importer Connector where still issue persist and it should be fix once the issue related to OT-110 will be fix:

CSV-Output Table Name
ElementCellRadioBandWidth
ElementTrx
GSMCell MAIO
NetworkElementDump

Regards,
Indrasan

Comment by Jharna Thakur [ 13/Nov/25 ]

Dear Indrasan Yadav, As discussed, the columns operator and importerConnector are not available in the DB because they are not defined in the model class on the server side. Although these columns appear in the CSV output, the issue should be resolved once the updated code is deployed on the server.

Comment by Bassem Sabbagh [ 13/Nov/25 ]

Patch should be released and deployed ... Indrasan to validate

Comment by Indrasan Yadav [ 17/Nov/25 ]

Dear @Basant Kumar,

Please generate Huawei RAN XML on .102 and upload the CSV output for same on S-DB.

Regards,
Indrasan

Comment by Indrasan Yadav [ 26/Dec/25 ]

1- All data are available in staging DB correct except the table count "Node interface" where count seem very high (Count is same in CSV output & S-DB, it means issue is in generation) which to be check by Jharna Thakur.

2- Importer connector is missing some where in table "sub interface"
3- Importer connector is available in table "Radio antenna" but in query it is not finding due to spelling wrong of "ImporterConnector" it is "importorconnector" in radio antenna. (Last O should be replaced with E in word importer)

Comment by Indrasan Yadav [ 29/Dec/25 ]

All the above points have been fixed in the CSV output received on 26-12-2025 for the micro site issue (JIRA: OT-45).

Once the file is uploaded to S-DB, I will verify the changes.
The upload to S-DB is currently pending due to the latest AI patch release, which is awaiting confirmation from Dr. Khaled. Once the patch is released, I will request the integration team to deploy it on .102, after which I will ask Jharna to share the same CSV output with the integration team for uploading to S-DB.

Comment by Indrasan Yadav [ 30/Dec/25 ]

Latest AI patch has been deployed on .120 & requested to Basant to generate XML & CSV on server and share to me for validation and I validated for same, now issue has been fixed for point 3 but not fixed for point 1 & 2 due to code not committed for same. (Locally it is fixed we will commit the code & to be check on server for same)

Jharna Thakur, please commit the code for point 1 & 2.

Comment by Jharna Thakur [ 30/Dec/25 ]

code committed

Comment by Indrasan Yadav [ 02/Jan/26 ]

Hi Jharna,

Earlier, the issue was only with the Node Interface table, where the count was mismatched. That issue is now resolved, and the count for the Node Interface table looks correct.

However, the following issues have now appeared, which were previously fixed:
Importer ID: "20251231015405_2025-12-31-01.54.05"

Below are the current issues identified during validation:

1- Boards count mismatch – Currently showing 129,061, whereas it should be 110,351.
2- Importer connector issue – I have reverted the related changes in OT-83.
3- Dump path missing in some records under the IP Data / Board table.
4- Node ID is missing in the Cabinet / Shelf / Board tables.
5- Start RU “-1” is appearing again in the Shelf table, which was already fixed in the previous cycle.
6- Supplier information is missing in Radio Antenna / 4G Cell tables.
7- MCC–MNC is parsing incorrectly (showing value 0) in 4G Cell / eNodeB / RNC / BSC tables.
8-Technology is not parsing for all nodes in SRAN, which was fixed last week but has reappeared.
9- Operator field is missing in eNodeB / Role3G / Role2G / RNC / BSC tables.
10- Also to be check the header "elementNodeId" in table "radioantenna" which is available in CSV output but missing in XML.

Comment by Bassem Sabbagh [ 06/Jan/26 ]

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 ...

Comment by Jharna Thakur [ 07/Jan/26 ]

I have checked the staging database and the issues have now been resolved.
Previously, the Omantel connector was executed instead of the Ooredoo Huawei RAN connector, which caused the discrepancy. This has been corrected.

Comment by Indrasan Yadav [ 07/Jan/26 ]

All highlighted issues have now been fixed as I validated the data on staging-DB, except point no. 10, which will be addressed under OT-45 as confirmed by Jharna.

Comment by Indrasan Yadav [ 09/Jan/26 ]

The missing header elementNodeId is now available in the radio antenna table.

Jharna Thakur, please proceed with committing the code for the same.

Comment by Jharna Thakur [ 12/Jan/26 ]

code committed

Comment by Indrasan Yadav [ 13/Jan/26 ]

Latest patch deployed on server, to be check data on staging-DB.

Comment by Indrasan Yadav [ 13/Jan/26 ]

Now, all issue has been fixed.

Generated at Wed Apr 15 14:30:50 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.