08-06-2014 06:54 AM - edited 03-04-2019 11:29 PM
I am trying to replace the startup configuration on Cisco Nexus device using a file on remote server. I tried the instructions given at this page:
So, I tried running command copy tftp://<server-ip-address>/nexus-startup.cfg startup-config and got the following error:
sysmgr_copy_nvram_dest_action: src uri_type = 2 is not supported yet
I tried to copy the file using all the four remote server protocol and got the same error with different URI type. 1 for FTP, 128 for SCP and 512 for SFTP.
The device is a Cisco Nexus 7000 series device with following details:
Software
BIOS: version 3.22.0
kickstart: version 6.1(3)
system: version 6.1(3)
Hardware
cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")
Intel(R) Xeon(R) CPU with 8251588 kB of memory.
Please let me know what am I doing wrong and how can I rectify this error.
Thanks in advance!
-Varun
08-09-2014 12:34 AM
Hi,
Can you verify if there is any startup config locks? If so unlock the same and the try it out.
08-10-2014 06:57 AM
The website you cited was for NXOS 4.x code. I looked up the 6.x version (see link below), and there are differences. The first step is to erase your startup config (write erase), then reload, then try the copying steps. Or is you cannot reload your box at the moment, maybe you try downloading your remote config to a regular file on your flash, not the startup-config itself. Then somehow work from that file locally. HTH, paul
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/fundamentals/configuration/guide/b_Cisco_Nexus_7000_Series_NX-OS_Fundamentals_Configuration_Guide_Release_6-x/b_Cisco_Nexus_7000_Series_NX-OS_Fundamentals_Configuration_Guide_Release_6-x_chapter_01000.html#task_1236980
02-27-2017 02:21 PM
I know this is very old thread but i ran into same issue.
First check if startup config has any locks if so please remove it.
N7K-1# show system internal sysmgr startup-config locks
There are no startup-config locks acquired. (No Locks)
N7K-1#system startup-config unlock (To Unlock )
Drop the configs to bootflash: or flash: and copy it over to startup config.
This works for me. Thanks
11-21-2017 11:57 PM
Hi Tuyuq,
While removing that startup config lock, can we expect any operational impact? Does it requires/provoke a reload of the system?
Or should it be safe to launch the command during business hours?
Thank you in advance!
11-22-2017 04:26 AM
Hello,
there is no operational impact.
Do you actually have any locks ? What is the output of:
show system internal sysmgr startup-config locks
11-22-2017 04:37 AM
Thanks for feedback.
Below the actual output:
show system internal sysmgr startup-config locks
There is 1 acquired startup-config lock:
ID UUID REASON
--------------------
743388735 81 Vshd generic error
11-22-2017 08:45 AM
Hello,
system startup-config unlock 743388735
should fix this...
11-23-2017 12:39 AM
09-01-2020 02:16 AM
I know this is a very old thread, but it was filed as bug CSCun19522 recently. There is a workaround listed, that is, you copy the file to the bootflash, then from there copy it to the startup-config.
On the up side, you also have a backup of the config on the device bootflash for later!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide