Alcatel Carrier Internetworking Solutions omniswitch User Manual
Managing CMM Directory Content
CMM Files
OmniSwitch 6600 Family Switch Management Guide
March 2005
page 4-3
CMM Files
The management of a stack or single switch is controlled by three types of files:
• Image files, which are proprietary code developed by Alcatel to run the hardware. 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.
as archive files, as they are really the repository of several smaller files grouped together under a
common heading.
• A configuration file, named boot.cfg, which is an ASCII-based text file that 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 boot.cfg. It uses this file to set various
switch parameters defined by the image files.
by the user. When the switch boots, it looks for the file called boot.cfg. It uses this file to set various
switch parameters defined by the image files.
• A boot file, named boot.slot.cfg, which is an ASCII-based text file that numbers the switches in a
stack. The boot.slot.cfg file and how to configure it is discussed more thoroughly in the OmniSwitch
6600 Family Getting Started Guide.
6600 Family Getting Started Guide.
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 configura-
tion files from the Flash into the RAM. When changes are made to the configuration file, the changes are
first stored in RAM. The procedures for saving these changes via the CLI are detailed in the sections to
follow.
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 configura-
tion files from the Flash into the RAM. When changes are made to the configuration file, the changes are
first stored in RAM. The procedures for saving these changes via the CLI are detailed in the sections to
follow.
CMM Software Directory Structure
The directory structure that stores the image and configuration files is divided into two parts:
• The certified directory contains files that have been certified by an authorized user as the default files
for the switch. Should the switch reboot, it would reload the files in the certified directory to reactivate
its functionality.
its functionality.
• The working directory contains files that may or may not be altered from the certified directory. The
working directory is a holding place for new files. Files in the working directory must be tested before
committing them to the certified directory. You can save configuration changes to the working direc-
tory. You can reboot the switch from the working directory using the reload working command as
described in
committing them to the certified directory. You can save configuration changes to the working direc-
tory. You can reboot the switch from the working directory using the reload working command as
described in
.
The running configuration is the current operating parameters of the switch, obtained from information
from the image and configuration files. The running configuration is in the RAM memory.
from the image and configuration files. The running configuration is in the RAM memory.