NCM capture error

[Anon Anon]

Hi All,

 

We've face a "The operation timed out. The device may not be responding." error on some devices, TFTP timeout is set to 600 sec.

Even it gives this error on oneclick I saw that it copies the capture file to tftp root directory with a naming like "SCM_0x5f02490" ,  this file can be opened fine, by the way these devices can be captured few days ago, these devices in on Cisco IOS and Cisco SSH device family classes.

what is the reason for this?

thanks for your time and help.

[mwegner]

Have you tried using wireshark or something similar to watch the tftp traffic?  Usually when I have NCM problems like that, it turns out that there is something obvious once you start looking at the traffic, and if not, it should at least help you figure out if it is a problem on the Spectrum side or the device side.

[FRANK ELLIGER]

I agree. The files in the tftp root directory are only a symptom, that something goes wrong. Capture the  communication with the device on your spectrum server and (if it is not the same) on your TFTP-Server could help to see, what is wrong.

[Anon Anon]

Hello Tepe,

 

Does this help?

 

There was a known issue with TFTP timeouts in early 9.3 that I believe was fixed in 9.3 h02.

 

Symptom: NCM TFTP file transfer is timed out for medium to large sized configurations

        and not considering configured TFTP timeout value.

 

Resolution: NCM will be take configured value as TFTP file transfer time out and

        successfully capture the configuration.

        (309133, 21805741-1)

[Anon Anon]

thanks for your help, this patch fixes the issue.

[Kamal Manchanda]

I am using CA Spectrum 10.2 and facing same issue. TFTP shows that file is downloaded successfully however Firmware upload tasks states that 'NCM File Transfer timeout'

[Matthew_Gay]

This could be a device latency problem too.

Try increasing the DCM Timeout value on that device to see if the problem continues.

You can also try increasing the overall timeout value for TFTP in the TFTP Configuration settings.

[Kamal Manchanda]

I had tried setting timeout to 50 and even 5000 as well. However still it gives error: NCM File Transfer Timeout.

 

Network administrator informed that he is getting firmware.bin file placed on server however firmware is not getting installed and NCM is giving timeout.

[FRANK ELLIGER]

Maybe, your issue is  the  same as descipred here:

https://communities.ca.com/thread/241737658?sr=inbox

The workaround is increasing DCM Timeout value of the device, as Matthew wrote too.

We have some devices, for which we need more than 20 seconds!

[Kamal Manchanda]

I validated with Network admin and got the information that user already have privilege 15, still we are facing the same issue.

[FRANK ELLIGER]

Sorry, I should have written a little bit more.

I'm sure, there is no problem with privileges.

We had  an issue with some IOS-XE devices and NCM using SNMP/TFTP.

Because of a bug (?) these devices send the response to the write request after finishing the file transfer.

This may result in timeouts and an error message.

Our workaround was setting the DCM timeout to 10.000ms, sometimes up to 20.000.

Changing the TFTP timeout had no effect in our case.

We have anlyzed  this by capturing the communication between

 - SS and the device

- TFTP server and the device

- SS and  TFTP server

Normally comes the SNMP response to the SS before the file transfer starts.