cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
79
Views
0
Helpful
1
Replies
khgrant
Cisco Employee

check-sync unsupported

Hi Team,

 

Apologies if this has been asked before, I looked through the archives and the only similar cases was solved by exciting sync-from first<—not in our case

 

When performing device check-sync we get result unsupported, we did sync-from before issuing check-sync. We are using NSO 4.0.3, XR NED and XRv in VIRL. Customer claims that with 4.0.1, check-sync was fine.

 

Compare-config doesn’t report anything i.e. Everything is actually in sync

 

From the user guide:

 

check-sync Check if the NSO copy of the device configuration is in sync with the actual device configuration. This operation is cheap as it only compares a signature of the configuration from the device rather than comparing the entire configuration. Depending on the device the signature is implemented as a transaction-id, time-stamp, hash-sum or not at all. The capability must be supported by the corresponding NED. The output might say unsupported, and then the only way to perform this would be to do a full device compare-config command.

 

How do we know exactly what’s causing this behaviour and if there is a way to troubleshoot?

 

1 ACCEPTED SOLUTION

Accepted Solutions
khgrant
Cisco Employee

Hi,

 

"The capability must be supported by the corresponding NED. The output might say unsupported, and then the only way to perform this would be to do a full device compare-config command."

 

 

Unsupported means the NED code does not support that functionality. It has nothing to do with the version of NSO but it might well be affected by the version of the NED.

 

Take a look at the state of the devices in oper mode, '-' means there is no such thing as 'transaction-id' implemented in the NED the 'check-sync' is not supported.

 

 

admin@ncs> show devices device * state

 

OPER

 

STATE

 

       OPER      ERROR TRANSACTION

 

NAME  STATE     TAG MODE            LAST TRANSACTION ID

 

-------------------------------------------------------------------------

 

ex0   disabled  -      lock-candidate 1454-946919-308854

 

ex1   disabled  - lock-candidate 1454-946919-323263

 

ex2   disabled  - ned -

 

ex3   disabled  - ned -

 

ex4   disabled  - ned bab271b20d4abf5538780a52a9c01cc3

 

ex5   disabled  - ned a1f24df80a69f2f2da9b2cec369d5f2c

View solution in original post

1 REPLY 1
khgrant
Cisco Employee

Hi,

 

"The capability must be supported by the corresponding NED. The output might say unsupported, and then the only way to perform this would be to do a full device compare-config command."

 

 

Unsupported means the NED code does not support that functionality. It has nothing to do with the version of NSO but it might well be affected by the version of the NED.

 

Take a look at the state of the devices in oper mode, '-' means there is no such thing as 'transaction-id' implemented in the NED the 'check-sync' is not supported.

 

 

admin@ncs> show devices device * state

 

OPER

 

STATE

 

       OPER      ERROR TRANSACTION

 

NAME  STATE     TAG MODE            LAST TRANSACTION ID

 

-------------------------------------------------------------------------

 

ex0   disabled  -      lock-candidate 1454-946919-308854

 

ex1   disabled  - lock-candidate 1454-946919-323263

 

ex2   disabled  - ned -

 

ex3   disabled  - ned -

 

ex4   disabled  - ned bab271b20d4abf5538780a52a9c01cc3

 

ex5   disabled  - ned a1f24df80a69f2f2da9b2cec369d5f2c

View solution in original post

Create
Recognize Your Peers
Content for Community-Ad