Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Resolution: Duplicate
-
Component/s: NEP
-
Customer:Airtel India
Description
data is available in XML but the IP are not getting parsed in NEP the error ss attached from JK circle.. the issue is observed in all the circle
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
issue analysis and script executed and post result check
-
- Time Spent:
- 1 hour
-
i have shared logs from jk circle to dev team for some ipdata and ipv6 data deletion .
-
- Time Spent:
- 7 hours, 30 minutes
-
tested the scenerio for generating duplicates at local before code change not able to reoccur with available xml..found duplicates ip in xml..shared with marwan and bessem checked another case where ip present in db but not reflecting in nep checked logs and condstructed updation queries and deletion
-
- Time Spent:
- 4 hours
-
checked the prod data for changes and updation checked the report at prod discussed with integartion regarding script excution requested latestest logs checked logs still the exception during load of logical interface regiving scripts.
-
- Time Spent:
- 1 hour
-
DATA VALIDATION FOR DUPLICATE IP ENTRY
-
- Time Spent:
- 6 hours, 30 minutes
-
checked logs contacted integration for exact time of query execution last and activity description happend during that time..had discussion with bessem reviewed script..reupdated the script found ipdatav6id missing reupdated script tested at local double checked with bessem and re released for execution on PROD
-
- Time Spent:
- 1 hour
-
i have run deletion queries on JK prod after that restarted the services .
-
- Time Spent:
- 30 minutes
-
Internal discussion with team for the issue.
-
- Time Spent:
- 3 hours
-
checked prod for if the blanks and ip not reflecting error solved after query execution checked logs aswell as prod data had discussion with marwan for further testing of root cause and its solvation process asked the telco for two small xml with same sample node diff ip config
-
- Time Spent:
- 1 hour
-
we have Executed the SQL queries on the DL and JK databases after that restated the services then shared logs with priyasha
-
- Time Spent:
- 1 hour
-
we have triggred xml on .37 server
-
- Time Spent:
- 1 hour
-
copied dumps and generated xml for IP Count Mismatch in DL Circle IN IP Report
-
- Time Spent:
- 1 hour
-
xml generated and shared with priyasha for Count Mismatch in DL Circle IN IP Report
-
- Time Spent:
- 1 hour
-
shared static sheet from JK circle for IP Count Mismatch in DL Circle IN IP Report
-
- Time Spent:
- 3 hours
-
XML shared with sample cases whose interface ,phy conifg are changing
-
- Time Spent:
- 6 hours
-
checked the issue and xml working on it
-
- Time Spent:
- 2 hours, 30 minutes
-
had discussion with marwan require a new small xml with full physical config as the shared one have only logical config ...checked the related config on prod if the sample case shared have proper info or not
-
- Time Spent:
- 3 hours
-
new sample case to L3 as requested
-
- Time Spent:
- 1 hour
-
i have extract FSCT564 node from JK circle logical IP and shared on mail .
-
- Time Spent:
- 3 hours
-
coordinating with AI team for XML file for single node of ericssion
-
- Time Spent:
- 1 hour
-
i shared dumps from jk prod server
-
- Time Spent:
- 30 minutes
-
checked the xml shared by telco not proper re requested again xml shared in evening as checked is ok
-
- Time Spent:
- 1 hour
-
internal and call and validating the sample case with l3 team
-
- Time Spent:
- 4 hours
-
checking the xml shared last importing in local checking the flow for saving of nodeinterface and ipdata debugging on that
-
- Time Spent:
- 2 hours
-
checking the on reimport the flow debugging
-
- Time Spent:
- 1 hour
-
CALL WITH l2 AND l3 FOR DELETION SCRIPT
-
- Time Spent:
- 4 hours
-
migrated the code and give it to srishti to test it
-
- Time Spent:
- 2 hours, 30 minutes
-
applied patch shared by marwan for ip added attribute in DB and manipulated xml ...some regression in code not building correcting workspace