Error "registering INACTIVE_PERIODIC_TIMER" during bi-weekly maintenance schedules in DX NetOps Spectrum

Products

• Network Observability

Issue/Introduction

Recurring bi-weekly maintenance schedules fail to exit maintenance mode when created under conditions where the start date has already passed or the start period is the current day ․​​​​‌​‍

ERROR MESSAGE: "registering INACTIVE_PERIODIC_TIMER (missing/failed execution)"

SYMPTOMS:

• Devices successfully enter maintenance mode at the scheduled start time

• Devices fail to exit maintenance mode at the scheduled end time

• Devices remain stuck in maintenance indefinitely, suppressing monitoring and critical alarms

CONTEXT: Occurs when creating a recurring schedule where the start date is the current day or in the past

IMPACT: Devices stuck in maintenance misrepresent network state and cause potential outages to go unnoticed

Environment

DX NetOps Spectrum 24.3.x,25.4.1-25.4.6

Cause

When a schedule is created within an active window, the determineWeeklyDayBitMaskActiveStateAndRegisterTimers function incorrectly forces the state to SCHEDULE_INACTIVE ․ The system triggers the activation timer but skips registering the exit condition because it assumes the schedule is already inactive

Resolution

STEPS:

1. UPGRADE DX NETOPS SPECTRUM

   Path: Upgrade to Spectrum version 25.4.7 /25.4.8 - The fix will be rolled into either of the releases. Please check the release notes.

   EXPECTED: The deactivation timer registers correctly and devices exit maintenance mode NOTE: A code fix addresses the logic failure in the determineWeeklyDayBitMaskActiveStateAndRegisterTimers function

VERIFY SUCCESS:

• Create a bi-weekly schedule starting on the current day

• Observe the device enter maintenance mode

• Observe the device successfully exit maintenance mode at the scheduled end time