search cancel

NCM Load Firmware task does NOT start through FTP

book

Article ID: 230126

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

We have some Cisco devices which we want to configure firmware uploads but we are not successful. We can run TFTP uploads but in our environment, TFTP is unstable, hence why we want FTP to function. 

We checked NCM logs and TCPDUMP of the transfer but was not able to determine the cause. 

Environment

Release : 20.2

Component : Spectrum Applications

Cause

The device does not support FTP

Resolution

Spectrum checked the following OID for device FTP support

 

ciscoFlashCopyEntryStatus(1.3.6.1.4.1.9.9.10.1.2.1.1.11),

ciscoFlashCopyCommand( 1.3.6.1.4.1.9.9.10.1.2.1.1.2),

and ciscoFlashCopyProtocol ( 1.3.6.1.4.1.9.9.10.1.2.1.1.3 )

 

Enable .vnmrc NCM debugging to check device protocol supportability: 

%SPECROOT/SS/.vnmrc: 

Add the line ncm_debug=true

Restart SS or use CLI command to reload .vnmrc: https://knowledge.broadcom.com/external/article?articleId=190121

Reproduce the issue and check VNM.OUT log for errors. 

If device is not supporting, you may see messages like the following: 

Dec 08 12:37:44 NCM_HOST_CONFIG TRACE at IHHostConfig.cc(1088): Action to determine device support has started
The device Opera_SW_241.misrbank.com (0x4021060) does not support the default family protocol of Unknown
Device 0x4021060 (Opera_SW_241.misrbank.com) Supports MIB or Script Firmware Upload: FALSE

 

- this is not a Spectrum issue

- problem must be resolved on the device-side

 

You can check the snmpset failure reason with the help of wireshark . The error-status and  error-index  in get_response from the device  after snmp_set packet gives the reason for snmp_set request failure . The error-status and error-index may not help fully understand snmp-set request rejection at the device side.