Details
-
Type:
Task
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Labels:
-
Customer:Ooreedo Tunisia
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours, 30 minutes
-
Take the cabinet/shelf/board/antenna serial number count for Huawei RAN
-
- Time Spent:
- 30 minutes
-
Take a teams call with Basant to discuss the issue regarding XML is not generating on server due to properties file path mismatch.
-
- Time Spent:
- 1 hour
-
AI patch deployed on Ooredoo and XML generated
-
- Time Spent:
- 30 minutes
-
Checked for latest patch and requested to Integration to deploy it on .102 and generate the XML for Huawei RAN then upload the CSV output to Staging-DB. and taken followed up for the same.
-
- Time Spent:
- 30 minutes
-
Validated the brief XML after shared by @Jharna and now issue fixed. and shared the same XML to @Basant to copy it on .102.
-
- Time Spent:
- 30 minutes
-
After imported the XML in NEP it was found that the header "Duplexing mode" is missing in CSV "ltecell". raised to @Jharna to fix the same.
-
- Time Spent:
- 1 hour, 30 minutes
-
Validate the XML again after fix the issues as confirmed to @Jharna over teams call, now it has been fixed and shared the same XML to @Basant to copy it on .102 to import the same.
-
- Time Spent:
- 1 hour
-
Validated the XML as shared by @Jharna after fix the issue of
LS-662. Still issue is persist for some cases so taken a call with her and explain the same.
-
- Time Spent:
- 4 hours, 42 minutes
-
implementing the new rule
-
- Time Spent:
- 1 hour
-
"All code committed up to 19-09-2025 has been requested to @Khaled for AI patch release. After the release, requested to Integration to deploy it on .102 and share the XML, which along with the CSV will be uploaded to S-DB."
-
- Time Spent:
- 1 hour
-
working on csv to db configuration
-
- Time Spent:
- 1 hour, 30 minutes
-
I found some minor issues during NEP data validation and raised it to @Jharna, she fixed it & shared me XML & I validated the same. now issue has been fixed.
-
- Time Spent:
- 3 hours, 12 minutes
-
working on feedback from previous shared xml
-
- Time Spent:
- 30 minutes
-
Requested to Jharna to shared updated XML with using of latest "site data information" as she didn't used it earlier for BSC/RNC.
-
- Time Spent:
- 1 hour
-
Checked updated xml which shared by @Jharna over teams after fix the issues of parent enodeb in "ltecell" and "enodebandwidths" and it is fixed now. but still IP data issue persist which I will confirm after import the XML.
-
- Time Spent:
- 5 hours
-
Validate the complete xml and still some issue which are not fixed and IP data parsing incorrect, discussed with Jharna and she fixed it but again a single IP Data csv is generating instead of 2 ip data csv. and still enodeb is not defined in "ltecell" and "enodebbandwidth" raised to Jharna. for IP data I will import the xml in NEP them confirm that it should be fixed or it can be acceptable.
I tried to import the XML in .102 but there is an issue and same is raised to integration and they found some error and highlighted to NEP DEV.
-
- Time Spent:
- 2 hours
-
Huawei RAN full XML Validation started and partially completed.
-
- Time Spent:
- 4 hours, 30 minutes
-
working on feedback
-
- Time Spent:
- 2 hours
-
working on feedback
-
- Time Spent:
- 6 hours
-
Completed the XML validation of Huawei RAN and share the feedback to #Jharna.
-
- Time Spent:
- 2 hours
-
working on feedback and testing
-
- Time Spent:
- 3 hours, 30 minutes
-
partially XML validation for Huawei RAN as latest xml shared by @Jharna after fixing the given issues.
-
- Time Spent:
- 5 hours
-
Logical data validation completed for Huawei RAN and shared feedback to @Jharna for the same.
-
- Time Spent:
- 4 hours, 30 minutes
-
Worked on full XML validation for node level & related physical data which was shared by @Jharna after fixing the raised issues. and taken a teams call with her and explain the issues.
-
- Time Spent:
- 30 minutes
-
Explain the site id parsing rule to @Jharna.
-
- Time Spent:
- 1 day
-
working on feedback for 4h after working on running all the connectors through command line
-
- Time Spent:
- 3 hours
-
issue identification and changes
-
- Time Spent:
- 1 day
-
XML validation done and remarks shared to @Jharna over an email.
-
- Time Spent:
- 5 hours
-
full XML validation of Huawei RAN based on dump received from Ooredoo.
-
- Time Spent:
- 3 hours, 30 minutes
-
XML validation for Huawei RAN based on dump received from Ooredoo. (Around 3230 physical nodes & 10-12 logical nodes)
-
- Time Spent:
- 1 hour
-
Compile the latest dump & share it to @Jharna to generate the XML.
-
- Time Spent:
- 1 hour, 30 minutes
-
Sample xml validation for Huawei, still some data not fixed but it will be check & confirm based on full xml.
-
- Time Spent:
- 2 hours
-
XML validation and feedback reverted to @Jharna.
-
- Time Spent:
- 2 hours
-
Analysed and given rule to parse "Start RU" in "nodeshelf" to @Jharna. (Given rule as per available in OmanTel)
-
- Time Spent:
- 4 hours
-
code modification based on feedback
-
- Time Spent:
- 1 hour, 30 minutes
-
XML validation which was shared by @Jharna over teams. and share validation remarks.
-
- Time Spent:
- 1 day
-
requirement review and code modification
