Details
-
Type:
Bug
-
Status:
Open Bug
(View Workflow)
-
Priority:
Urgent
-
Resolution: Unresolved
-
Component/s: NEP
-
Labels:None Labels
-
Customer:Airtel India
Description
The RB process for the UE circle was triggered on 2026-01-10 at 21:27, after the RB cron was enabled at 19:00 on Saturday, and it is still in progress. This issue has been escalated multiple times every week; however, no resolution has been provided so far.
Upon reviewing the 11 January logs, the latest entries related to the RB process are as follows:
buildRoute Monitoring data ***
2026-01-11 23:50:17,038 INFO End Building Routes
2026-01-11 23:50:23,222 INFO Route capacity fixer ...
2026-01-11 23:50:24,458 INFO Apply circuit routes ...
2026-01-11 23:50:25,835 INFO start of importNodeCircuit
2026-01-11 23:50:25,841 INFO Starting Import of 1,187,125 Enodeb Circuits for Version FULL_UE_PROD
2026-01-11 23:51:17,217 INFO start of endDocument nodecircuitservercsvhandler inside importnode circuit
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
i have restarted the NEP application for the UE circle, because delay RB import completed .
-
- Time Spent:
- 2 hours
-
i have triggered RB on UE circle ater patch deployment. monitored logs and shared on mail
-
- Time Spent:
- 1 hour
-
i have shared logs form UE circle .
-
- Time Spent:
- 1 hour
-
i have shared logs from UE circle .
-
- Time Spent:
- 1 hour, 54 minutes
-
update the property nep.npt.rb.Redimension_After_Route from false to true in nep-server-config.xml and restart the NEP application across all production servers
