Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Resolution: Fixed
-
Component/s: NEP
-
Customer:Airtel India
-
Classification:Query
Description
MW nodes with node types IP-20C, IP-20G, and IP-20GX are present in the XML but are not parsing into NEP.
Sample node 10.64.85.20_BR, no error for this node in error report .
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
i have executed deletion script on BR circle then restart the services
-
- Time Spent:
- 2 hours
-
validation on prod and call with L3 and L2 for script
-
- Time Spent:
- 2 hours, 30 minutes
-
discussed with bessem the findingdings..explained same to priyasha the nodes going in autocreation because they dont have slots and boards in xml hence code using defaulttemplate during physical configuration and assigning idu nodes as auto created..mailed and updated on jira
-
- Time Spent:
- 1 hour
-
i have shared xml from bihar circle with dev team.
-
- Time Spent:
- 1 hour
-
i have shared server log from BR circle
-
- Time Spent:
- 6 hours, 30 minutes
-
requested the logs..checked logs..checked code..checked data on prod platform..xml too large bot opnening in application requested xml from integration checked xml slots boards missing need to discuss with priyasha and bessem
-
- Time Spent:
- 5 hours
-
checked the sample cases again for releated configuration and links and in code for autocreation atrribute adding logs finally and releasing it to track
-
- Time Spent:
- 1 hour, 30 minutes
-
i have copied BR dumps to .177 then generated xml and shared on mail .
-
- Time Spent:
- 3 hours
-
static sheet analysis and import after patch applied and validation
-
- Time Spent:
- 3 hours, 30 minutes
-
checking issue configuration report db
-
- Time Spent:
- 2 hours
-
testing and validation the static sheet for this bug, and call with L3 team
-
- Time Spent:
- 2 hours
-
i have executed the deletion script on BR circle and that i have restated the server .
-
- Time Spent:
- 30 minutes
-
reissue thequery for mw-models to shift into autocreated
-
- Time Spent:
- 2 hours, 30 minutes
-
checked the reports and db discussion with marwan script made shared to integration
-
- Time Spent:
- 7 hours, 30 minutes
-
imported xml again in clean version xml imported correctly nodes reflecting in idu checking for error in error report no error found requesting db permission again checking in error report in db no error found for sample not in idu..discussed with marwan checked in db idu is availabale for version but in autocreation category..discussed same with telco to provide info which idu need to be removed from autocreated..discussed the autocreationscenerio with bessem nodes by xml import by importer are not considered as autocreated ..asked telecom if any process is done for autocreation or static sheet imported.
-
- Time Spent:
- 7 hours
-
checked the code got sample xml by putting logs found the code is in error alarms of xml related to ai part, imported the xml..found error..catalogue missing for sample node..creating the catalogue wrt to PROD
-
- Time Spent:
- 2 hours
-
CALL WITH L3, CUSTOMER AND BUG ANALYSIS .
-
- Time Spent:
- 2 hours
-
CORDINATING WITH BASANT FOR XML
-
- Time Spent:
- 1 hour
-
downloaded xml put logs imported xml no issue found, xml doesnt contain sample case which issue persist informed telco rerequested xml file.
-
- Time Spent:
- 4 hours
-
WORKING TO PROVIDE A SMALL XML TO L3 ,CORDINATING WITH L2 TOOK MUCH TIME
-
- Time Spent:
- 1 hour, 30 minutes
-
i have generated XML for OSS IP - 172.27.75.85, Nokia/CM Dump form BR circle on .37 test server and shared on mail .
-
- Time Spent:
- 2 hours, 30 minutes
-
checked the problem checked the prod xml checked in the code requested for xml of sample case not parsing due mismatch of neid between networkelemnts map and fetching after regex.
-
- Time Spent:
- 4 hours
-
bug analysis, internal call with team for understand the bug and screensharing session with customer
-
- Time Spent:
- 2 hours
-
validation on prod