OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Managing CMM Directory Content
CMM Files
CMM Files
The management of a switch is controlled by the following types of files:
• Image files, which are proprietary code developed by Alcatel-Lucent. These files are not configurable
by the user, but may be upgraded from one release to the next. These files are also known as archive
files as they are really the repository of several smaller files grouped together under a common heading.
• A configuration file, named vcboot.cfg, which is an ASCII-based text file, sets and controls the configurable
functions inherent in the image files provided with the switch. This file can be modified by the
user. When the switch boots, it looks for the file called vcboot.cfg. It uses this file to set various switch
parameters defined by the image files.
Modifications to the switch parameters affect or change the configuration file. The image files are static
for the purposes of running the switch (though they can be updated and revised with future releases or
enhancements). Image and configuration files are stored in the Flash memory (which is equivalent to a
hard drive memory) in specified directories. When the switch is running, it loads the image and configuration
files from the Flash memory into the RAM. When changes are made to the configuration file, the
changes are first stored in the RAM. The procedures for saving these changes via the CLI are detailed in
the sections to follow.
Available Files
This table lists the image and configuration files for the OmniSwitch. Most of the files listed here are part
of the base switch configuration. Files that support an optional switch feature are noted in the table.
OmniSwitch 6860/6860E
File Name Base or Optional Software Description
Uos.img Base Software CMM Operating System
Urescue.img Optional Software Disaster Recovery file (used on USB flash drive)
vcboot.cfg
Switch Configuration File
vcsetup.cfg
Virtual Chassis Setup File
boot.md5
An automatically created checksum file used to ensure
the image files in the running directory cannot be
certified until the switch has booted from the running
directory with those image files. The boot.md5 file is
created in the current running directory from the image
files immediately after the switch boots. If new image
files are copied into that directory and the “copy running
certified” command is attempted, the command will be
rejected since the switch has not yet booted with the new
image files. This prevents possibly corrupted image files
from becoming certified.
OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 3-3