Cisco Cisco Digital Service Access Node (DSAN) 8211 Troubleshooting Guide

 

4032301 Rev A 

71 

 

3  Verify that the eCM configuration file for docsDevSwAdminStatus is set to 

allowProvisioningUpgrade (for automatic upgrades). 

4  Verify that the file specified in the eCM configuration file (for automatic 

upgrades) or in the docsDevSwFilename MIB ojects (for manual upgrades) is 
correct and present on the specified TFTP server. 

5  Verify that the DSAN can reach the TFTP server by pinging the DSAN eCM IP 

address shown on CLI diag page 4.0 from the TFTP server. For example: 

# ping 192.168.18.69

 

6  Verify that the correct signed image is being used. The images provided by Cisco 

are signed with the manufacturer CVC. If cosigning is required, the subsequently 
cosigned image must be used. 

A download may successfully complete, but the actual upgrade may still fail. This 
can occur when: 

 

The downloaded image does not match the target DSAN model (i.e., software 
downloaded to an 8200 is for 8250). 

 

A CRC error occurs in the file, possibly as a result of an error during download 
or flash write. 

The above conditions will cause the upgrade status to be reported as Invalid Image 
or Upgrade Incomplete on the CLI diag page 12.0 and in the 
saDsanSwImageDownloadStatus MIB object. Additionally, the error will be logged 
to dsanlog. 

To correct these conditions, perform the following steps. 
1  Verify that the file specified in the eCM configuration file (for automatic 

upgrades) or in the docsDevSwFilename MIB ojects (for manual upgrades) is for 
the proper platform. 
8200 platforms should use a filename in the following format: 

DSAN_w_x_y_zzz_PKEY_DOC.simg

 

2  If you suspect a CRC error, retry the download.