Invalid Source Name or Destination Name when doing firmware upload for Cisco devices
search cancel

Invalid Source Name or Destination Name when doing firmware upload for Cisco devices

book

Article ID: 207122

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

When trying to upload firmware using NCM (network configuration manager) the error Invalid Source Name or Invalid Destination Name is received.

Environment

Release : 10.4

Component : Spectrum Core / SpectroSERVER

Resolution

"Invalid Source Name" is a response from the device as well as Destination Name.

This is not a Spectrum problem, but a device one.

You can run a wireshark capture to see the response.

ciscoFlashCopySourceName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1 .. 255))
ACCESS read-create
STATUS current

DESCRIPTION
"Source file name, either in Flash or on a server,
depending on the type of copy command. Mandatory.

For a copy from Flash:
File name must be of the form
[device>:][:]
where is a value obtained from FlashDeviceName,
is obtained from FlashPartitionName
and is the name of a file in Flash.
A management station could derive its own partition name
as per the description for the ciscoFlashPartitionName
object.
If is not specified, the default Flash device
will be assumed.
If is not specified, the default partition
will be assumed. If a device is not partitioned into 2
or more partitions, this value may be left out.

For a copy to Flash, the file name will be as per
the file naming conventions and path to the file on
the server."
::= { ciscoFlashCopyEntry 5 }

-- 1.3.6.1.4.1.9.9.10.1.2.1.1.5

We are getting back a "5" or "6" on the below from the device:

ciscoFlashCopyStatus OBJECT-TYPE
SYNTAX INTEGER {
copyOperationPending(0),
copyInProgress(1),
copyOperationSuccess(2),
copyInvalidOperation(3),
copyInvalidProtocol(4),
copyInvalidSourceName(5),
copyInvalidDestName(6),
copyInvalidServerAddress(7),
copyDeviceBusy(8),
copyDeviceOpenError(9),
copyDeviceError(10),
copyDeviceNotProgrammable(11),
copyDeviceFull(12),
copyFileOpenError(13),
copyFileTransferError(14),
copyFileChecksumError(15),
copyNoMemory(16),
copyUnknownFailure(17),
copyInvalidSignature(18),
copyProhibited(19)
}

ACCESS read-only
STATUS current

DESCRIPTION
"The status of the specified copy operation.

copyOperationPending :
operation request is received and
pending for validation and process

copyInProgress :
specified operation is active

copyOperationSuccess :
specified operation is supported and
completed successfully

copyInvalidOperation :
command invalid or command-protocol-device
combination unsupported

copyInvalidProtocol :
invalid protocol specified

copyInvalidSourceName :
invalid source file name specified
For the copy from flash to lex operation, this
error code will be returned when the source file
is not a valid lex image.

copyInvalidDestName :
invalid target name (file or partition or
device name) specified
For the copy from flash to lex operation, this
error code will be returned when no lex devices
are connected to the router or when an invalid
lex interface number has been specified in
the destination string.

copyInvalidServerAddress :
invalid server address specified

copyDeviceBusy :
specified device is in use and locked by
another process

copyDeviceOpenError :
invalid device name

copyDeviceError :
device read, write or erase error

copyDeviceNotProgrammable :
device is read-only but a write or erase
operation was specified

copyDeviceFull :
device is filled to capacity

copyFileOpenError :
invalid file name; file not found in partition

copyFileTransferError :
file transfer was unsuccessfull; network failure

copyFileChecksumError :
file checksum in Flash failed

copyNoMemory :
system running low on memory

copyUnknownFailure :
failure unknown

copyProhibited:
stop user from overwriting current boot image file."
::= { ciscoFlashCopyEntry 8 }

-- 1.3.6.1.4.1.9.9.10.1.2.1.1.8



Reach out to Cisco or device owner on this as this is not a problem with Spectrum since the response being received is an error from the device.