Category Archives: Cisco

Squeeze me

What to do if you accidentally fill up your bootflash with txt files!

The institute where I work currently employs VMPS to dynamically assign VLANs to end user devices. This system runs on a Cisco 6513 switch running a hybrid setup (IOS & CatOS). (Yes, it is a dated system! and yes, we are trying to get rid of it!)

When a new device is added to the network, a static text file is edited to add the new MAC Address to VLAN mapping, and the file is uploaded via TFTP to the bootflash of the Cisco 6513, MSFC card. The VMPS service actually runs on the PFC in CatOS, but the vmps.txt file can be stored on a tftp server, or in our case, on the MSFC running IOS.

The commands on the system to complete this are:

copy tftp bootflash

Address or name of remote host []? 172.19.0.66

Source filename []? vmps.txt

Destination filename [vmps.txt]? vmps.txt

%Warning:There is a file already existing with this name

Do you want to over write? [confirm] <return>

Accessing tftp://172.19.0.66/vmps.txt…

Loading vmps.txt from 172.19.0.66 (via Vlan4): !!!!!!!!!!!!!!!!

[OK – 79895 bytes]

 

This shows a successful upload to the bootflash area of the Cisco 6513. I have highlighted the line where we specify to “overwrite” the existing vmps.txt file.

This process was being followed by one of my colleagues when all of a sudden, he was faced with the “Bootflash full” error and was unable to upload the file to the switch. This was odd, the file is merely kb in size and is overwritten everytime we upload a new one….. or is it….

A quick Show bootflash: displayed literally hundreds of vmps.txt files still resident in memory.

 Cisco6513#sho bootflash:
-#- ED —-type—- –crc— -seek– nlen -length- ———date/time——— n
ame
1   .. image        AACC1263 1934E44   41 25906628 Feb 8 2006 14:40:07 +00:00 c6
msfc3-ipservices_wan-mz.122-18.SXF2.bin
2   .. ascii text   D2760983 194834C    1    78984 Aug 2 2007 12:45:46 +00:00 #
3   .. ascii text   C43C5C48 195E534    1    90471 Feb 1 2008 08:43:16 +00:00 n
4   .. ascii text   D7304249 19754C8    1    93970 May 2 2008 13:29:45 +00:00 q
5   .. ascii text   40CC2736 198D9F8    8    99501 Aug 12 2008 13:58:22 +00:00 VMPS.TXT
6   .. ascii text   2F1A58E3 19A64E0    5   100965 Aug 29 2008 13:52:23 +00:00 boot#
7   .. ascii text   280E6196 19C0750    3   106991 Nov 25 2008 14:32:41 +00:00 bot
8   .D ascii text   E9CE7F63 19DAF1C    8   108361 Jan 7 2009 15:06:02 +00:00 vmps.txt
9   .D ascii text   060B72F4 19F5710    8   108402 Jan 7 2009 15:20:36 +00:00 vmps.txt
10  .D ascii text   2F00FF69 1A0FF30    8   108446 Jan 7 2009 16:04:11 +00:00 vmps.txt
11  .D ascii text   83914AFB 1A2A7A8    8   108534 Jan 8 2009 09:26:29 +00:00 vmps.txt
12  .D ascii text   433C1D43 1A451A0    8   108920 Jan 8 2009 11:00:16 +00:00 vmps.txt
13  .D ascii text   183A4746 1A5FB44    8   108834 Jan 8 2009 13:31:14 +00:00 vmps.txt
14  .D ascii text   740DF43E 1A7A510    8   108876 Jan 8 2009 13:54:58 +00:00 vmps.txt
15  .D ascii text   1815DE6B 1A94F08    8   108918 Jan 8 2009 16:11:54 +00:00 vmps.txt
16  .D ascii text   87341A2B 1AAF900    8   108918 Jan 9 2009 08:59:53 +00:00 vmps.txt
17  .D ascii text   B83A9B8F 1ACA224    8   108705 Jan 9 2009 11:09:54 +00:00 vmps.txt

In order to rectify this and get the VMPS system up and running again as soon as possible, we discovered the Squeeze command. This allows you to purge all previously deleted files, a bit like emptying the Windows Recycling bin.

Cisco6513#squeeze bootflash:

We now know to periodically run the command against the bootflash to ensure that we always have enough space to upload our files.