Cisco Support in Morocco After End of Life

An Upgrade Needs Somewhere to Land

Before a Cisco device can load a new software image it has to copy that image into its own flash storage. That storage is finite, and it accumulates: every image ever staged on the device tends to remain unless somebody removed it. A platform upgraded several times across a decade can be holding most of its own version history, leaving no room for the next one.

Free Memory Is Not Free Flash

The confusion is common and reasonable. A device reporting ample free memory is describing working memory, not the storage an image is staged into. Moroccan operators reading a healthy memory figure quite fairly conclude there is space, and the upgrade fails minutes into a window that was sized for the upgrade itself.

Deleting images is not a quick job

Three things must survive: the image currently running, the image the boot variable names, and on a redundant chassis whatever each engine needs to run. Remove the wrong file and the device is fine until the next reload, at which point it has nothing to boot. So the clean-up is careful work, and it is now happening unplanned, on a device carrying production traffic, inside a window already partly spent.

Audit the flash before the window, not during it

Listing the images and their sizes takes a minute and tells you whether the upgrade can be staged at all. On an estate past its support date, where devices have accumulated the most history and are least likely to have been tidied, it is worth doing as a standing check rather than a reaction.

What ICD Supplies for Cisco Estates in Morocco

Flash and storage modules, supervisor engines whose capacity bounds what can be staged, access and distribution switching, UCS server and fabric parts, and optics picked for the slot standard and the run being lit. Morocco is named on the published North Africa card, giving a 2 to 4 day door-to-door lane from Cairo. Each module is bench-run under load, entered against its serial, and backed one to three years.