[LS-664] Virtual Interface IP Not Imported (Huawei) Created: 18/Sep/25  Updated: 26/Sep/25  Due: 30/Sep/25  Resolved: 25/Sep/25

Status: Rejected
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: Cannot Reproduce 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 Error Snippet for virtual interface IP not imported.png     File HuaweiRanOoredoo_17-09.rar     PNG File NEP Error_All Cases for virtual interface IP not imported.png     PNG File Virtual Interface Error_25-09-2025.png     PNG File XML Snippet_Virtual Interface IP not imported.png     File server.tgz    
Customer:
Ooreedo Tunisia
Planned Start:
Planned End:
Rejected By: Mustapha Al-Hage
Actual Start:
Date of Baselining:

 Description   

Dear @Khaled Khalil,

Could you please assign a NEP DEV resource to investigate the following issue regarding IP addresses not being imported?

Issue Description:

Virtual Interface IPs are not being imported for the nodes listed below. For other nodes with the same interface name, the IPs are successfully imported. However, errors appear in all cases.

IPs Not Imported:

ipAddress mask parentXmlElement parentId
10.97.173.34 255.255.255.0 virtualInterfaces MBTS-Sidi_Mahrsi_NAB1111_10.97.173.34_255.255.255.0
10.97.126.79 255.255.255.0 virtualInterfaces MBTS-TIERET_TAT1065_10.97.126.79_255.255.255.0
10.97.126.74 255.255.255.0 virtualInterfaces MBTS-S_RELAIS _LAARICHE_TAT1064_10.97.126.74_255.255.255.0
10.97.41.44 255.255.255.0 virtualInterfaces MBTS-Ste_SOPAT_MAH2010_10.97.41.44_255.255.255.0
10.97.68.9 255.255.255.0 virtualInterfaces MBTS-Aeroport TABARKA_JEN2001_10.97.68.9_255.255.255.0

Error Snippet & XML Snippet

Attached

Same error occurs in all cases:

Attached

List of IPs Imported for your reference:

gateway ipAddress mask parentXmlElement parentId
10.191.0.54 255.255.255.240 virtualInterfaces BSCNAB51_10.191.0.54_255.255.255.240
10.203.23.118 255.255.255.240 virtualInterfaces RNCMNB51_10.203.23.118_255.255.255.240
10.204.19.6 255.255.255.240 virtualInterfaces RNCSOS53_10.204.19.6_255.255.255.240
10.203.29.198 255.255.255.240 virtualInterfaces RNCMNB52_10.203.29.198_255.255.255.240
10.91.0.54 255.255.255.240 virtualInterfaces BSCTOZ51_10.91.0.54_255.255.255.240
10.103.3.246 255.255.255.240 virtualInterfaces BSCMNB55_10.103.3.246_255.255.255.240
10.104.4.54 255.255.255.240 virtualInterfaces BSCSBO51_10.104.4.54_255.255.255.240
10.70.0.54 255.255.255.240 virtualInterfaces BSCMED51_10.70.0.54_255.255.255.240
10.34.0.54 255.255.255.240 virtualInterfaces BSCNAB52_10.34.0.54_255.255.255.240
10.59.0.54 255.255.255.240 virtualInterfaces BSCSIL51_10.59.0.54_255.255.255.240
10.204.20.6 255.255.255.240 virtualInterfaces RNCSOS54_10.204.20.6_255.255.255.240
10.202.29.6 255.255.255.240 virtualInterfaces RNCSFX52_10.202.29.6_255.255.255.240
10.18.0.54 255.255.255.240 virtualInterfaces BSCBIZ51_10.18.0.54_255.255.255.240
10.207.22.54 255.255.255.240 virtualInterfaces BSCZAG51_10.207.22.54_255.255.255.240
10.202.13.134 255.255.255.240 virtualInterfaces RNCSFX51_10.202.13.134_255.255.255.240
10.104.4.86 255.255.255.240 virtualInterfaces BSCSOS55_10.104.4.86_255.255.255.240
10.204.4.6 255.255.255.240 virtualInterfaces RNCSOS55_10.204.4.6_255.255.255.240
10.121.221.54 255.255.255.240 virtualInterfaces BSCKEB51_10.121.221.54_255.255.255.240
10.103.1.54 255.255.255.240 virtualInterfaces BSCKAS51_10.103.1.54_255.255.255.240
10.68.0.54 255.255.255.240 virtualInterfaces BSCJEN52_10.68.0.54_255.255.255.240

Thank you
Indrasan

 Comments   
Comment by Indrasan Yadav [ 25/Sep/25 ]

Dear @Mustapha Al-Hage,

As discussed yesterday, after reimporting the same XML, the raised IPs have been imported successfully. However, an unexpected error is now appearing.
(Snippet-Attached with today date)
I checked the sample with the highlighted entry, and it seems that the same is not available in the XML.

Thank you
Indrasan

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

After discussions with Indrasan via teams, he re-imported the XML file and now issue is solved. However, regarding new error, a new ticket is required.

Generated at Wed Apr 15 16:10:59 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.