http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-489 L3 Support <p>Dear @Abir Messaikeh, @Khaled Khalil,<br/> We've found that some vendor tickets aren't being created because of an "Empty Description" error. We inserted CF_Pull into the Description template in the NEP_KQI table when these KQIs were created. Please review and let us know your recommendations.<br/> Logs and NEP_KQI table exported sheet attached in link for your reference.</p> <p> server.log.2025-06-30.gz</p> <p>server.log.2025-06-30.gz:2025-06-30 22:22:05,549 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5) Error While Creating UttTicket for kqi name Huawei CPE Outdated dumps data, Diplay Name Huawei IP CPE Outdated dumps data , Empty Description</p> <p>server.log.2025-06-30.gz:2025-06-30 22:21:21,773 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5) Error While Creating UttTicket for kqi name Cisco CPE Outdated dumps data, Diplay Name Cisco IP CPE Outdated dumps data , Empty Description</p> <p>server.log.2025-06-30.gz:2025-06-30 20:20:58,480 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4) Error While Creating UttTicket for kqi name Cisco CPE Outdated dumps data, Diplay Name Cisco IP CPE Outdated dumps data , Empty Description</p> LS-489

KQI - Empty description

Bug Normal Reopened Not Fixed Marwan Kanaan Abir Messaikeh Mon, 7 Jul 2025 07:06:35 +0300 Thu, 9 Apr 2026 11:13:30 +0300 Wed, 17 Sep 2025 15:24:32 +0300 NEP Thu, 31 Jul 2025 00:00:00 +0300 0 2 0 minutes 1 week, 2 hours <p>Please find below the formal technical guidelines to be strictly adhered to during the process of creating Key Quality Indicators (KQIs) to ensure system consistency and to prevent known issues such as empty description errors.<br/> 1. KQI Main Categories<br/> During the KQI creation process, the following three primary KQI categories are to be used:<br/> OutdatedDumpsData<br/> AbnormalDumpsFilesCount<br/> SFTP_SSHConnectionFailure<br/> 2. Configuration Guidelines for Each Category<br/> 2.1. OutdatedDumpsData<br/> When working under the OutdatedDumpsData category:<br/> The Description Template must be explicitly set to one of the following:<br/> PhyLogNotSeparated<br/> PhyLogSeparated<br/> This is mandatory to avoid empty description generation, as the process relies on the template to determine the description format.<br/> Additional Configuration:<br/> If the template is set to PhyLogSeparated, it is imperative to configure the NEP_DUMPS_KQI_KEY table such that the KQI_FILE_TYPE column is set to either Logical or Physical.<br/> If using PhyLogNotSeparated, this additional configuration is not required.<br/> 2.2. SFTP_SSHConnectionFailure<br/> When working under the SFTP_SSHConnectionFailure category:<br/> The Description Template must be one of the following:<br/> CF_Push<br/> CF_Pull<br/> CF_WithAttachment<br/> Note:<br/> There is no requirement to set the KQI_FILE_TYPE column in the NEP_DUMPS_KQI_KEY table for this category.<br/> 2.3. AbnormalDumpsFilesCount<br/> When working under the AbnormalDumpsFilesCount category:<br/> The Description Template must be strictly set to:<br/> PhyLogSeparated<br/> Additional Configuration:<br/> As with OutdatedDumpsData, it is mandatory to configure the NEP_DUMPS_KQI_KEY table such that the KQI_FILE_TYPE column is set to either Logical or Physical to ensure proper operation.<br/> 3. Important Notes<br/> Failure to comply with the above configuration standards will result in empty descriptions due to the dependency of the description generation process on the correctly set templates and corresponding data in the database.<br/> Please ensure these requirements are reviewed and implemented carefully during each KQI creation to maintain data integrity and prevent processing failures.<br/> Should you require any clarifications or technical assistance regarding these configurations, please do not hesitate to reach out.</p> <p>No Patch Need For This Bug </p> <p>Best regards,</p> <p>Dear @Mohan Singh Rathor,</p> <p>I hope this message finds you well.<br/> I would like to inform you that the issue has been identified and will be resolved in the upcoming patch, version 3.7.0.1325. The root cause of the problem has been traced to unnecessary validation, which has now been addressed.<br/> Please let me know if you require any further details or assistance.</p> <p>Best Regards,</p> <p>a regression has been shown as KQI with 0 Outdated files is generating now -<a href="http://jira.mobinets.com/jira/browse/LS-569" title="KQI Created even for 0 outdated dumps" class="issue-link" data-issue-key="LS-569"><del>LS-569</del></a> is created for same </p> <p>so we are reverting this change and will check empty description status accordingly</p> <p>Still empty description is showing as reported by Mohan</p> <p>related logs </p> <p><a href="https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EfTeuKk2M3hPhCshILR8wykBiHWvMVaxngXMgL38tQ8NLw" class="external-link" rel="nofollow">https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EfTeuKk2M3hPhCshILR8wykBiHWvMVaxngXMgL38tQ8NLw</a></p> <p>2025-09-16 03:22:02,713 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei U2000 RAN Outdated dumps data, Diplay Name Huawei U2000 RAN Outdated dumps data , Empty Description<br/> 2025-09-16 03:23:39,074 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei Core Outdated dumps data, Diplay Name Huawei Core Outdated dumps data , Empty Description<br/> 2025-09-16 03:24:37,502 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name IntraCom MW Outdated dumps data, Diplay Name IntraCom MW Outdated dumps data , Empty Description<br/> 2025-09-16 03:26:19,936 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Fiber-Home Fixed Access Outdated dumps data, Diplay Name Fiber-Home Fixed Access Outdated dumps data , Empty Description<br/> 2025-09-16 03:27:16,751 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name SDWAN IP Outdated dumps data, Diplay Name SDWAN IP Outdated dumps data , Empty Description<br/> 2025-09-16 03:28:45,205 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Redline MW Outdated dumps data, Diplay Name Redline MW Outdated dumps data , Empty Description<br/> 2025-09-16 03:29:11,949 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei NCE FAN Outdated dumps data, Diplay Name Huawei NCE FAN Outdated dumps data , Empty Description</p> <p>2025-12-08 03:59:49,953 ERROR <span class="error">&#91;com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler&#93;</span> (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-10) Error While Creating UttTicket for kqi name Tellabs DXX Outdated dumps data, Diplay Name Tellabs DXX Outdated dumps data , Empty Description</p> <p>Dear @Mohan Singh Rathor,</p> <p>Kindly find the solution for the reported issue included in patch 3.7.0.1411.</p> <p>Please note that the attached script must be executed prior to applying the patch to ensure proper behavior.</p> <p>Best Regards,<br/> Marwan Kanaan I Software Developer</p> <p>Dear @Mohan Singh Rathor,</p> <p>Kindly ensure that the script is executed before applying the patch.<br/> Please ignore the previously attached script and consider the script attached to this email as the correct one to be executed.</p> <p>Best Regards,<br/> Marwan Kanaan I Software Developer</p> <p>no more error empty description showing but</p> <p>I have verified the system status following the recent database script execution and patch updates. Unfortunately, there has been no change in behaviour; discovery tickets have not been generated since November 12, 2025, on either server (10.164.168.11 or 10.164.168.12).<br/> Please find the attached server logs for your review and investigation.<br/> serverlogs_12nov_02Feb.rar</p> <p>And we got one exceptional discovery ticket IM3577717 but not able to see in the logs on both server.</p> <p>Dear @Mohan Singh Rathor,</p> <p>As discussed on Teams, the issue causing the dumps process not to work is related to the nep-server-config.xml configuration.</p> <p>On the production environment, the dumps trouble ticket flag is currently set to false. Kindly change it to true.</p> <p>Additionally, please confirm with @Abir whether the engineering flag should be false on .11.</p> <p>SS</p> <p>Best Regards,<br/> Marwan Kanaan I Software Developer</p> <p>Dears<br/> As per previous recommendation from Nazih as per <br/> nep.troubleTicket.executor.isEnabled shall be true only on one node as it is the process responsible to open tickets with UTT for items stored in DB as per my understanding<br/> having it running on both nodes is causing the duplication</p> <p>Regards<br/> Abir</p> <p>Still some KQI dumps are not generating which dashboard showing red and needs to be checked with MOhan </p> Actual Start Thu, 2 Oct 2025 00:00:00 +0300 Baseline End Thu, 31 Jul 2025 00:00:00 +0300 Baseline Start Thu, 31 Jul 2025 00:00:00 +0300 Customer Date of Baselining Tue, 7 Oct 2025 13:42:55 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Thu, 31 Jul 2025 00:00:00 +0300 Planned Start Thu, 31 Jul 2025 00:00:00 +0300 Product Rank 0|xtio01: Rank (Obsolete) 9223372036854775807 VTDirections