[LS-663] Error Regarding Channel Bandwidths While 4G Cells Are Importing (Huawei) Created: 17/Sep/25  Updated: 26/Sep/25  Due: 30/Sep/25  Resolved: 25/Sep/25

Status: Closed
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Indrasan Yadav Assignee: Indrasan Yadav
Resolution: Fixed Votes: 0
Labels: AI_All_incidents, Huawei_RAN_OO
Remaining Estimate: 0 minutes
Time Spent: 1 day, 3 hours, 30 minutes
Original Estimate: Not Specified

Attachments: PNG File Capture.PNG     File HuaweiRanOoredoo_17-09.rar     PNG File NEP error sniipet.png     PNG File XML enodebbandwidths snippet.png     PNG File XML_Channelbandwidth snippet.png     PNG File XML_Radio channel _freq band snippet.png     File server.tgz    
Customer:
Ooreedo Tunisia
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Dear @Khaled Khalil,

Could you please assign a NEP DEV resource to check and fix the following issue:

(I) XML File: 2025-09-17-11.04.12_Ooredoo
(II) Import Date: 17-09-2025
(III) Platform: .102

Issue Description:

Although channel bandwidths are available in the XML, an error still appears during import. All 4G cells are successfully imported in NEP, but the error persists. For reference, I am sharing an example below.

References Attached:

NEP Error Snippet:

Snippet of “enodebandwidths” from XML:

Snippet of “radiochannelbandwidths” xml:

XML-Radio channel frequency band snippet:

Thank you
Indrasan

 Comments   
Comment by Mustapha Al-Hage [ 23/Sep/25 ]

Dear @Indrasan Yadav, 

If we take this example:

The following band(s) 'TDD_42' should support at least one channel bandwidth for eNodeB (BARF026). 

When we search for this eNodeB in the error report, we find the following message: "Wrong Channel Bandwidth format (42.0) for EnodeB BARF026"

The implemented logic uses a specific pattern to validate channel-bandwidth formats. This pattern was modified to accept the 42.0 channel bandwidth, patch is needed: 3.7.0.1352.

In addition, a script has already been applied to the schema to add the 42.0 channel bandwidth.

Please ensure the server is restarted after applying the patch.

Regards, 
Mustapha

Comment by Indrasan Yadav [ 24/Sep/25 ]

Dear @Khaled Khalil,

Kindly release the NEP patch version 3.7.0.1352, as the same issue has already been fixed by @Mustapha Al-Hage.

Thank you
Indrasan

Comment by Indrasan Yadav [ 24/Sep/25 ]

Dear @Basant Kumar,

Kindly deploy the NEP patch on server .102. After the deployment, please ensure the server is restarted. Once the activity is completed, kindly provide an update.

Build SUCCESS
Project: NEP_OMANTEL
Release Version: 3.7.0.1352
Build URL: http://ciserver.mobinets.local:8080/job/NEP_OMANTEL/1813/

Date of build: Wed, 24 Sep 2025 08:18:00 +0300
Build duration: 10 min

Thank you,
Indrasan

Comment by Indrasan Yadav [ 24/Sep/25 ]

Dear indrasan ,

Latest NEP 3.7.0.1352 patch has been deployed on 102 . Kindly check and update

Regards,
Basant

Comment by Indrasan Yadav [ 25/Sep/25 ]

Dear @Mustapha Al-Hage,

Thank you for your email.

After applying the patch you shared, I imported the same XML, and I am pleased to inform you that the issue has now been resolved.

Regards,
Indrasan

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