GNS3 – Can’t Save ASA Config – ‘%Error copying system:/running-config (Not enough space on device)’

KB ID 0000987

Problem

I love GNS3, it is a brilliant piece of software, I use it for bench testing and proof of concept work. Yes is can be a bit clunky sometimes, but it’s FREE! I had a project open with about four ASA’s on it, and it would not save the config on just one of them.

[box]

HostName(config)# copy running-config startup-config

Source filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)#

[/box]

[box]

HostName(config)# write mem
Building configuration...
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
Error executing command
[FAILED]
HostName(config)# 

[/box]

[box]

HostName(config)# copy running-config disk0:

Source filename [running-config]?

Destination filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)# 

[/box]

Solution

At first I simply deleted the ASA and added a new one, which annoyingly did the same. Then I read a post that said, do the following;

1. Open the configuration for the affected ASA.

2. Change the NIC Model to pcnet > Apply > OK > Stop the firewall > Start the Firewall.

HOWEVER, in my case the problem persisted, I eventually fixed it by formatting the virtual ASA’s flash drive.

3. Execute the following command;

[box]

HostName# format flash 

 

Format operation may take a while. Continue? [confirm]

Format operation will destroy all data in "flash:". Continue? [confirm]{Enter}
Initializing partition - hda: hda1
done!
mkdosfs 2.11 (12 Mar 2005)

System tables written to disk

Format of disk0 complete
HostName# 

[/box]

4. Power off, then power on the firewall, problem fixed.

Related Articles, References, Credits, or External Links

NA

Backup and Restore Cisco IOS (Switches and Routers)

KB ID 0000538 

Problem

It’s been a long time since I ran through setting up a TFTP server, but I still use 3CDeamon. Below I’ll run though the simple commands to back up, and restore the devices configuration.

Solution

Backing up a Cisco IOS Device

1. First you have to setup a TFTP server, and know the IP address of the machine it’s on!

2. Connect to the device, either via console cable, Telnet or SSH.

3. Log in > Go to enable mode > issue a “copy running-config tftp”* command > Supply the IP address of the TFTP server > Give the backup file a name.

Note: You can also use startup-config to copy the config saved in NVRAM rather than the running-config.

[box]

User Access Verification

Username: username
Password:*******

PeteRouter#enable
PeteRouter#copy running-config tftp
Address or name of remote host []? 10.10.0.1
Destination filename [PeteRouter-confg]? PeteRouter_Backup
!!
7400 bytes copied in 0.548 secs (13504 bytes/sec)

PeteRouter#

[/box] 4. If you keep an eye on the TFTP server you can see the file coming in.

Restoring a Cisco Cisco IOS Device

1. As above have your TFTP server up and running with the file you want to restore in its root directory.

2. Connect to the device either via console cable, Telnet or SSH.

3. Log in > Go to enable mode > issue a “copy tftp running-config”* command > Supply the IP address of the TFTP server > Give the backup file a name.

Note: You can also use startup-config to restore the config saved in NVRAM rather than the running-config.

[box]

User Access Verification

Username: username
Password: *******

PeteRouter#enable
PeteRouter#copy tftp running-config
Address or name of remote host []? 10.10.0.1
Source filename []? PeteRouter_Backup
Destination filename [running-config]? {Enter}
Accessing tftp://10.10.0.1/PeteRouter_Backup...
Loading PeteRouter_Backup from 10.10.0.1 (via GigabitEthernet0/0): !
[OK - 7400 bytes]

7400 bytes copied in 0.440 secs (16818 bytes/sec)

PeteRouter#

[/box]

4. Remember you have restored the running-config you would need to issue a “copy run start” command to make this config persistent (i.e. after a restart or reload of the router). If you issued a “copy tftp startup-config”, you would need to reboot for the restored config to be loaded into memory.

Related Articles, References, Credits, or External Links

Install and Use a TFTP Server

Backup and Restore a Cisco Firewall