asked integration to run the configuration cleanup on the DL circle and restart the service.

@Priyasha Tiwari, please check the system post-cleanup and restart. Also, verify whether the related nodes are being imported successfully or not.

As requested, please check whether the related nodes are being imported, as the initial data provided is limited and lacks sufficient detail.
If the nodes are not importing, and the import errors are unclear, kindly share a few sample cases to help me analyse the situation further from my end.

all required details shared on email on 23-04-2025

deletion script not working as required.. the deleted data is reoccurring after a week again .. need to validate the cronjob output and share that with L3 team.

Srishti shall review the API execution to check why IPs are left blank in IP data
As we observed that they belong to deleted RAN nodes

Cronjob -

1. XML generation and run
   00 20 * * 1,2,3,4,6,7 /product/Airtel/scripts/XML_GENSAV/xmlGenSaveSeq.sh > /product/Airtel/scripts/logs/xml-gen-and-save-$(date +%d-%m-%Y-%H-%M).log

#During DELETION PROCEDURE Import Process

00 21 * * 5 /product/Airtel/scripts/XML_GENSAV/xmlGenSaveSeq.sh > /product/Airtel/scripts/logs/xml-gen-and-save-$(date +%d-%m-%Y-%H-%M).log

As per discussion with Basant, Other deletion procedures are running than API during week end , need to Stop them and monitor if API deletion is not causing such behavior

deletion procedure stopped after that script was run on MP Circle prod , then it was found that node details for some of the ip is getting blank may be due the parent node is getting deleted, l3 will check again how this node are getting deleted when all the deletion procedure are paused.. apart form this point the deletion script is not cleaning the whole data at once

requested small xml small xml containing all related data(interface,ipdata) for these nodes:RJUBRDHO016,RJUBRHPSC2400 from RJ circle. xml shared doesnt have related ips in ipdatav6 requested again

requested XML shared on email , awaiting the update on resolution.

Build 3.7.71.482 released with change in checking used ipv6 in repo, previously ipv4 is being checked in code and if not found error being thrown and ipdataV6 being set to null wrt to virtual interface.Also the code was Updating oldManagementInterface1 with the new (ipData orV6) — then immediately it sets the same virtualInterfaceToSave again causing the inconsistency.

under testing, testing involves mutliple import of XML in test DB timeline -04-09

in test server the script executed , all blank IP was removed then after this we re imported the new XML to check if the blank entries are occuring or not.. so the result is that after xml import the balnk entry are appering for same report are attched for working.

also attach the updated script that was shared on mail for both ipv4 and v6

Build 3.7.71.486 is released containing file committed with changes.

not on customer priority list, will check this after service routing topic are closed

new ticket ls-788 for this issue