can not able to save running-config of C93108TC-EX switch

[AbhishekNanda]

can not able to save running-config of C93108TC-EX switch

show version output:

*****************************************************************

Software
BIOS: version 07.59
NXOS: version 7.0(3)I4(8b)
BIOS compile time: 08/26/2016
NXOS image file is: bootflash:///nxos.7.0.3.I4.8b.bin
NXOS compile time: 10/19/2018 23:00:00 [could not extract timestamp: Corrupted image]

Hardware
cisco Nexus9000 C93108TC-EX chassis
Intel(R) Xeon(R) CPU @ 1.80GHz with 24633900 kB of memory.
Processor Board ID FDO22381HN7

Device name: BBSNOOB07231032
bootflash: 7906304 kB
Kernel uptime is 1508 day(s), 1 hour(s), 29 minute(s), 13 second(s)

Last reset
Reason: Unknown
System version: 7.0(3)I4(8b)
Service:

plugin
--More--Could not match packages: Cannot retrieve repository metadata (repomd.xml) for repository: localdb. Please verify its path and try again
Core Plugin, Ethernet Plugin

************************************************************************

[M02@rt37]

Hello @AbhishekNanda,

What is the error message when you try to save the running-config ?

[AbhishekNanda]

#copy running-config startup-config
[########################################] 100%
Configuration update aborted: request was aborted

[M02@rt37]

Hello @AbhishekNanda,

Thanks for the output.

Cisco Bug: CSCvc77151

https://quickview.cloudapps.cisco.com/quickview/bug/CSCvc77151

Workaround

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc77151

[AbhishekNanda]

Hi M02@rt37 ,

As I can see from the output of storage usage, the /nxos/dme_logs partition has sufficient space available. Should I proceed to delete some files? Below is the output log for your reference.

root@BBS32#ls -l -h
total 29M
-rw-r--r-- 2 root root 4.6M Jun 7 11:25 nginx.13700.log
-rw-r--r-- 2 root root 4.6M Jun 7 11:25 nginx.13700.log.41
-rw-rw-rw- 1 root root 2 Apr 20 2019 nginx.13700.log.PRESERVED
-rw-rw-rw- 1 root root 0 Apr 20 2019 nginx.13700.log.stderr
-rw-r--r-- 2 root root 4.2M Jun 7 11:25 svc_ifc_confelem.13770.log
-rw-r--r-- 2 root root 4.2M Jun 7 11:25 svc_ifc_confelem.13770.log.34
-rw-rw-rw- 1 root root 2 Apr 20 2019 svc_ifc_confelem.13770.log.PRESERVED
-rw-rw-rw- 1 root root 209 Apr 20 2019 svc_ifc_confelem.13770.log.stderr
-rw-r--r-- 2 root root 1.2M Jun 7 11:25 svc_ifc_eventmgr.13650.log
-rw-r--r-- 2 root root 1.2M Jun 7 11:25 svc_ifc_eventmgr.13650.log.2
-rw-rw-rw- 1 root root 2 Apr 20 2019 svc_ifc_eventmgr.13650.log.PRESERVED
-rw-r--r-- 2 root root 4.3M Jun 7 11:25 svc_ifc_policyelem.13651.log
-rw-r--r-- 2 root root 4.3M Jun 7 11:25 svc_ifc_policyelem.13651.log.57
-rw-rw-rw- 1 root root 2 Apr 20 2019 svc_ifc_policyelem.13651.log.PRESERVED
-rw-rw-rw- 1 root root 6.3K Jun 6 14:11 svc_ifc_policyelem.13651.log.stderr
root@BB32#df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 8.9G 983M 7.9G 11% /
none 40M 2.2M 38M 6% /nxos/tmp
none 80M 15M 66M 18% /nxos/dme_logs
none 50M 13M 38M 25% /var/volatile/log
none 5.0M 24K 5.0M 1% /var/home
none 300M 2.4M 298M 1% /var/volatile/tmp
none 4.0G 244K 4.0G 1% /var/sysmgr
none 1.0G 134M 891M 14% /var/sysmgr/ftp
none 100M 0 100M 0% /var/sysmgr/srv_logs
none 10M 0 10M 0% /var/sysmgr/ftp/debug_logs
none 4.0G 350M 3.7G 9% /dev/shm
none 2.0G 0 2.0G 0% /volatile
none 5.0M 164K 4.9M 4% /debug
none 1.0G 744K 1.0G 1% /mnt/ifc/cfg/db
/dev/loop1 54M 54M 0 100% /isan_lib_ro
/dev/loop2 59M 59M 0 100% /isan_bin_ro
/dev/loop3 640K 640K 0 100% /isan_lib_n9k_ro
/dev/loop4 128K 128K 0 100% /isan_bin_n9k_ro
unionfs 8.9G 983M 7.9G 11% /isan/bin
unionfs 8.9G 983M 7.9G 11% /isan/lib
/dev/sda5 60M 5.9M 51M 11% /mnt/cfg/0
/dev/sda6 60M 5.9M 51M 11% /mnt/cfg/1
/dev/sda4 7.5G 3.4G 4.1G 46% /bootflash
/dev/sda2 3.8G 73M 3.5G 2% /mnt/plog
none 400M 6.3M 394M 2% /var/sysmgr/startup-cfg
/dev/loop5 33M 33M 0 100% /lc_ro
/dev/loop6 36M 36M 0 100% /lc_n9k_ro
unionfs 8.9G 983M 7.9G 11% /lc
/dev/sda3 119M 7.0M 106M 7% /mnt/pss
/dev/sda7 12G 608M 11G 6% /logflash
/dev/loop7 57M 1.2M 53M 3% /bootflash/.rpmstore/patching

[Flavio Miranda]

Hi

 Copy running-config startup-config will repalce the config currently stored on the memory for the running config. Did you try to change something and repeat the command. It may hapen because both config are identical

[AbhishekNanda]

Hi @Flavio Miranda ,

I have already tried it but result is same.

[ranirani]

Hello @AbhishekNanda,

Based on the information provided, it appears that you are experiencing issues saving the running configuration of your Cisco Nexus 9000 C93108TC-EX switch. Here are a few steps you can try to resolve the problem:

1. Check file system status: Run the following command to verify the file system status:

show file systems

1. Make sure that the bootflash file system is writable and has sufficient space available. If the file system is full or read-only, you may need to free up space or resolve any underlying issues.

2. Check file permissions: Ensure that the appropriate file permissions are set to allow writing the running configuration. You can use the following command to check the permissions:

show running-config

1. If you encounter any permission-related errors, you might need to adjust the file permissions accordingly.

2. Try a different filename: By default, the running configuration is saved as "running-config." However, if there are any issues with that filename, you can try using a different filename using the following command:

copy running-config <filename>

1. Replace <filename> with the desired name for the configuration file.

2. Check for any error messages: Review the output of the copy running-config command for any error messages or warnings that might provide more insight into the issue.

3. Consider a software update: The output shows that the NX-OS image may be corrupted or outdated. Consider updating the software to a more recent and stable version. Ensure that you have the appropriate software package for your device and follow the upgrade process outlined in the Cisco documentation.

If the above steps do not resolve the issue, it may be necessary to consult Cisco technical support or the network administrator for further assistance. They can provide guidance specific to your device and help troubleshoot the problem effectively.