cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1387
Views
5
Helpful
2
Replies

/ncs:devices/commit-queue/completed failed

Chris Wang
Cisco Employee
Cisco Employee

For checking devel.log, we found below errors. Can someone help with issue?

<ERR> 17-Feb-2019::22:10:19.791 apsj1nso001 ncs[16648]: devel-snmpa snmp not enabled. send notification not possible: tfAlarmClear
<ERR> 17-Feb-2019::22:11:38.882 apsj1nso001 ncs[16648]: devel-snmpa snmp not enabled. send notification not possible: tfAlarmMajor
<ERR> 17-Feb-2019::22:11:41.792 apsj1nso365 ncs[16648]: devel-snmpa snmp not enabled. send notification not possible: tfAlarmClear
<ERR> 17-Feb-2019::22:12:34.225 apsj1nso365 ncs[16648]: devel-snmpa snmp not enabled. send notification not possible: tfAlarmMajor
<ERR> 17-Feb-2019::22:12:42.636 apsj1nso365 ncs[16648]: devel-snmpa snmp not enabled. send notification not possible: tfAlarmClear
<ERR> 18-Feb-2019::00:00:00.294 apsj1nso365 ncs[16648]: ncs scheduled task: purge on /ncs:devices/commit-queue/completed failed: Error when parsing params: End-of-file reached in XML stream

1 Accepted Solution

Accepted Solutions

We finally to find that it is the schedule action params default set is not correct, as well as the exec-default is deny.

View solution in original post

2 Replies 2

joepak
Cisco Employee
Cisco Employee

Just a couple of suggestions:

 

-match these commit-queue settings if not already configured:
ncs# show full-configuration devices global-settings commit-queue | details
devices global-settings commit-queue enabled-by-default false
devices global-settings commit-queue atomic true
devices global-settings commit-queue connection-failure-reconnect-timer 30
devices global-settings commit-queue connection-failure-reconnect-retries unlimited

-Restart NSO instance, perform a ‘devices commit-queue clear’ to clean the entire queue, perform a sync-from, provide check-sync/compare-config outputs, reproduce the issue (please share all this data).

The error alone is vague, but this should provide more clarity to what's going on. The first option are just settings while the second option is more intuitive.

 

Also, reasons for this issue could be:

 

 1.  If a device rejects the proposed change, NSO and the device are now out of sync until any error recovery is performed. Whenever this happens, an NSO alarm (called commit-through-queue-failed) is generated. 

  2.  locked - This queue item is locked and will not be processed until it has been unlocked, see the action /ncs:devices/commit-queue/queue-item/unlock. A locked queue item will block all subsequent queue items which are using any device in the locked queue item. 


We finally to find that it is the schedule action params default set is not correct, as well as the exec-default is deny.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the NSO Developer community:

Recognize Your Peers