CF Memory Cards and the Squeeze Command

Im currently upgrading some devices for a customer all over the world, nothing I didnt do before but today I ran into something suprising, at least for me. The C2811 I was going to upgrade was not having enough flash space to hold the old and the new IOS (my prefered way for upgrades) so I had to delete the old IOS to be able to upload the new one.

But after the IOS was deleted, the router did not free the flash space, this was something I was used to on older devices (C2600 for example) but not with the newer ISR routers. Quick check on google did approve what I thought, I have to use the squeeze command to free up the flash after the IOS was deleted.

I´ve found the reason after another lookup, it seems that there are 2 different file systems installed in ISR routers (guess its not for ISR2 routers but I´m not sure) a Class B and a Class C file systems. The troubleshooting guide writes the following about those two types:

Cisco 3800 series routers, Cisco 2800 series routers, and Cisco 1800 series routers use external CompactFlash (CF) memory cards to store the system image, some software feature data, and configuration files. The CF memory cards use the following file systems. The file system that is supported depends on router mode

Class B flash file system, also known as the low-end file system (LEFS)

Class C flash file system, similar to the standard DOS file system

If the router uses a Class C file system deleted files will free the space on the flash (the one I was used to) while Class B file systems require a manual intervention to free up this space. Freeing up the space on those Class B file systems is done with the squeeze command:

Router# squeeze flash:
Squeeze operation may take a while. Continue? [confirm]
squeeze in progress...
sssssssssssssssssssssssseeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Rebuild file system directory...
Squeeze complete

If you are using a Class B flash file system, after you enter the delete flash: command, the memory space of the deleted file remains occupied, although the deleted file cannot be recovered. To reclaim the memory space occupied by a deleted file, enter the squeeze flash: command, in privileged EXEC mode.

Which Class is used on the router can be checked with the command show flash all, the Class B file system will not show any geometry and format information while the Class C file system will. Examples are shown below and are taken from the guide Troubleshooting and Maintenance: Using CompactFlash Memory Cards

Class B file system

Router# show flash: all
Partition   Size    Used      Free      Bank-Size  State          Copy
Mode
1        125184K  20390K    104793K        0K      Read/Write
Direct

System Compact Flash directory:
File  Length   Name/status
addr      fcksum  ccksum
1   6658376  c28xx-i-mz
0x40      0xE0FF  0xE0FF
2   14221136  c2800-telcoent-mz
0x6599C8  0x5C3D  0x5C3D

[20879640 bytes used, 107308776 available, 128188416 total]
125184K bytes of ATA System Compact Flash (Read/Write)

Class C file system

Router# show flash: all
-#- --length-- -----date/time------ pat
1      6658376 Mar 01 2004 04:27:46 c28xx-i-mz
25268224 bytes available (6664192 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:      4
Number of Cylinders    490
Sectors per Cylinder   32
Sector Size            512
Total Sectors          62720
ATA CARD FORMAT
Number of FAT Sectors  31
Sectors Per Cluster    8
Number of Clusters     7796
Number of Data Sectors 62560
Base Root Sector       155
Base FAT Sector        93
Base Data Sector       187

Cat4500-E Sup 6/7-E Etherchannel Egress Queueing

QoS on Cat4500-E with a Sup 6/7-E is more aligned to the Modular QoS CLI (MQC) known from router platforms then on a Cat6500, even though it still got restrictions based on the architecture compared to routers. The Cat4500-E switches perform all QoS actions on the supervisor engine, therefore the line cards do not add to the QoS complexity with their own queueing structure. The whole chassis uses an 1P7Q1T (1 Priority queue, 7 normal Queues, 1 Threshold) queueing structure. But there is a gotcha for QoS on Etherchannel (how surprising ;) ), the QoS documentation shows the following restrictions:

  • Queuing actions are only allowed in the egress direction and only on the physical port.
  • Percentage-based actions like policer cannot be configured on a VLAN, Port and VLAN (PV) and EtherChannel.
  • Port channel or VLAN configuration can only have a policing or a marking action, not a queueing action.

The example configuration below shows what this means in terms of configuration. The priority queue has to be defined on the physical ports while the policing action is configured on the port-channel interface.

Example Configuration

class-map match-any PRIORITY-QUEUE
 match  dscp ef
!
policy-map EGRESS-QUEUING-PHYSICAL
 class PRIORITY-QUEUE
  priority
 class class-default
policy-map EGRESS-QUEUING-LOGICAL
 class PRIORITY-QUEUE
  police cir 2g
!
int po 1
 service-policy output EGRESS-QUEUING-LOGICAL
!
int te1/1
 service-policy output EGRESS-QUEUING-PHYSICAL
!
int te1/2
 service-policy output EGRESS-QUEUING-PHYSICAL

Cat6500-E Sup2T Etherchannel Egress QoS

Cisco is now using a more MQC like QoS configuration with the Sup2T Supervisor Engine which is called C3PL (Cisco Common Classification Policy Language). C3PL is not only used for QoS configuration but also for other tasks:

Cisco Common Classification Policy Language is a structured replacement for feature-specific configuration commands. C3PL allows you to create traffic policies based on events, conditions, and actions

If you know MQC you´ll find it more confortable to use the new C3PL instead of the old mls QoS configuration but the Cat6500 architecture still plays a role. If you want to configure egress QoS on an etherchannel, you have to configure the egress queuing policies on the physical port members of the etherchannel, it cannot be configured on the logical Etherchannel interface. If you try to, you´ll get an error message like this:

MQC features are not supported in output direction for this interface

The documentation for this can be found in the Cat6500 Supervisor 2T Qos Design At-a-Glance  Guide.

Conclusion

As explained above you have to configure egress queueing policies on the physical port members to make use of egress queueing policies on an etherchannel:

class-map type lan-queuing PRIORITY-QUEUE
match dscp ef
!
policy-map type lan-queueing EGRESS-QUEUING-PHYSICAL
 class PRIORITY-QUEUE
 priority
class class-default
!
int te1/1
 channel-group 10 mode active
 service-policy type lan-queueing output EGRESS-QUEUING-PHYSICAL
!
int te1/2
 channel-group 10 mode active
 service-policy type lan-queueing output EGRESS-QUEUING-PHYSICAL

Interesting Links 13.05.2013

SDN

Packetlife´s What the Hell is SDN?A short overview from Packetlife about the SDN topic which kinda floods the networking news at the moment:

If you follow any number of news feeds or vendor accounts on Twitter, you’ve no doubt noticed the term “software-defined networking” or SDN popping up more and more lately. Depending on whom you believe, SDN is either the most important industry revolution since Ethernet or merely the latest marketing buzzword (the truth, of course, probably falls somewhere in between)

Build your own free IOS-XE lab

Cisco recently made a virtual CSR available which allows (amongst the real use) to create a virtual lab based on the CSR 1000v. Please take care on this, the CSR 1000V requires at least 4 GB of memory, it wont work with less!

Miroslaw Burnejko´s Build IOS-XE Lab for Free
INE´s Installing the cloud services router 1000v in ESXi 5.1

Nexus 1000v

Cisco´s Capture Traffic on Nexus 1000V Series Switches

This document describes the use of the vempkt command in order to capture traffic on Nexus 1000V Series Switches.

It is difficult to troubleshoot issues on the Nexus 1000V Series Switches because there is no physical switch to put your hands on. Much of the time, a packet capture is necessary in order to determine if the packets are sent upstream.

Technical Document Updates

Cisco´s Technical Documentation Updates

You should check out this link if you want to get an overview on the Cisco technical documentation updates.

VSS and QoS on Cat6500 SUP2T


I really don’t like QoS on Cisco Switches, its too complicated and totally depends on the chassis or even on the line card in chassis based switches. What made things worse is how QoS and VSS is implemented on the Cat6500 (and documented). I recently had to create a QoS design for a customer which had VSS on Cat6500 with SUP2T and 16-port 10GE line cards. The VSL Links were on the SUP using the two 10GE ports and I had to configure QoS towards the WAN on two out of the three 1GE ports on the SUP.

Continue reading

Interesting Links 11.02.2013

I try to get this up again (once more), on a weekly, bi-weekly or monthly base (depends on how much time I get to actually read something out there in the internet). Hope it works out better this time ;)

Cisco´s CiscoLive365
This has probably become one of my number one ressources for knowledge (not sure if Google is in front or directly behind it).  Cisco offers a direct access to (nearly) all presentations from the different Cisco Live meetings across the world, and its for free. Whenever I´m in need for information on a new topic (which happens quite often) or have to review something I´ve learned somewhen, this is the place I go first.

Cisco´s SMART Business Architecture

Another usesfull ressource from Cisco is their SMART Business Architecture which contains Borderless Networks, Data Center and Colaboration Design Support and Guidelines. I currently use it as a base to refresh my Design/Best Practice knowledge, to prepare for Design Workshops with customer and as a base for an Assessment I am developing.

PacketPushers: 15 Reasons You’re Technical Documentation Sucks

A nice overview on how a documentation should/could be written and what points you should have a lookt at.

Packet Pushers: 5 Tips for Escaping Troubleshooting Hell

This article is not discussing on how to do troubleshooting itself, its more about a few key points to remember during troubleshooting. The one I like most is to write down what you have done to not loop yourself into checking the same thingthing over and over.

Installing Virtual Riverbed Steelhead Appliances

Im currently creating a lab for internal testing purposes and proof of concepts for Riverbed WAN optimizations. A few years ago, I did install quite some Riverbed Steelhead Appliances (Hardware) and the installation (not configuration) was quite straight forward ( if you dont mess up the cabling :)). But its a bit different now with virtual Appliances, we got licenses (amongst others) for two virtual Steelhead Appliance for the lab. Installing the Appliance itself is not too hard (if you know vSphere and I dont, but I got a nice coleague which did give me a little Howto). Choose the .ova file from the Riverbed page and put it into the ESX/vSphere and start the Appliance, go to the console and use the startup wizard to configure the basic settings for the system. The virtual Appliance can now be accessed over the GUI.

What got me was the licensing and the assigned hardware for the appliance ( I dont like to read installation manuals ;)).
There are currently two different virtual Steelhead appliances:

Virtual Steelhead xx50 Models
Virtual Steelhead CX xx55 Models

The former line is now end of life and the CX xx55 models are now new available since about a month or two. Both lines do have only one installation file, the specifications of the different models within the line are activated over the corresponding license key. Crossupgrading between the two lines does not work.

The license I got is one for a VCX1555H, the virtuall appliance with the highest throughput and concurrent connections but the base installation is the one for a VCX555M (smallest appliance) and thats what the installation file does request from vSphere. To be able to use the virtual Appliance as a VCX1555H vSphere has to assign more CPUs, RAM and Disk Space for the Datastore. The corresponding values can be taken from the table below:

Riverbed vSHA Hardware Requirements

The license for a 1555H can be installed even if the appliance does not have enough hardware, but it cannot be activated.