The Change Management execution node currently sends commands at a fixed time interval, or waits out a configured sleep timer, without evaluating whether the prior command has actually finished executing based on its output. This approach is unreliable for long-running operations, such as large file uploads or unzip operations during device image upgrades, where actual completion time can vary significantly and exceed a fixed wait period. This enhancement would introduce execution logic that inspects command output to determine whether a command has completed before issuing the next one, similar to behavior already used by device drivers. This would reduce failed or incomplete command sequences during long-running change operations and remove the need for administrators to manually tune sleep timers to accommodate worst-case execution durations.
Open
Output-Based Command Completion Detection for Change Management Execution
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain Universityor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
