I've run into a problem where upgrading a remote device from an APE fails, and it appears that it might be caused by the SFTP directory not being properly recognized or referenced by the APE.
I've placed the upgrade image in a folder in the NCM Archive, which is available to all APE's. I've verified the folder is shared with the same permissions as the NCM Archive folder.
I suspect the upgrade would work properly from the Main Instance of NPM, but since it's failing when running from a different APE that's managing a node, I suspect a problem with the ability of that APE to properly reference the upgrade image on the Main Poller's share.
When the upgrade fails, NCM sends this e-mailed message to me:
Upgrade Operation
Started at 2/7/2018 11:00:05 AM
_______________________________________________________________________________
Upgrading node
(Node Name)
Writing config to
NvRAM...
write memory
Building
configuration...
Cryptochecksum:
(obscured intentionally by me for security)
7454 bytes copied
in 1.480 secs (7454 bytes/sec)
[OK]
Uploading Firmware
Image (obscured intentionally by me for security)
copy
tftp://(obscured intentionally by me for security)
Address or name
of remote host (obscured intentionally by me for security)
Source filename
[(obscured intentionally by me for security)]?
Destination
filename [(obscured intentionally by me for security)]?
Accessing
tftp://(obscured intentionally by me for security)...
WARNING: TFTP
download incomplete!
%Error reading
tftp://(obscured intentionally by me for security) (Unspecified Error)
dir disk0:/
${SuccessRegEx:(obscured intentionally by me for security)}
Directory of
disk0:/
total (58257408 bytes free)
ERROR Process
could not continue because execution results do not match expected pattern:
(upgrade image name was here)
_______________________________________________________________________________
Upgrade Error on
node (device name obscured intentionally) Operation interrupted
_______________________________________________________________________________
What troubleshooting tools can I bring to bear on this? Turn on Session Traces to see what's happening and why it fails?