Filter
Top Products
206 MPCMM0001 Chassis Management Module Software Technical Product Specification
Updating CMM Software
The update package can be placed locally on the CMM in the /usr/local/cmm/temp directory, or it
can reside on a server on the network.
The files and directories that make up the Update Package are packaged and delivered as a .zip file.
Associated with the .zip file is a file containing the md5 sum of the .zip file. For example:
• [PackageFileName].zip file containing all files and subdirectories of the update package
• [PackageFileName].md5 file containing md5 checksum of PackageFileName.zip
Arguments for the location of the update package will be given in the CLI command, which can be
used to point to a remote server or a local directory. The update script will then remove the /usr/
local/cmm/temp/update/package directory and recreate it with the new package files.
Note: If an NFS server is mounted to the CMM, the argument in the update script will be similar to a file
located locally on the CMM.
If the package fails to copy or transfer to /usr/local/cmm/temp/update/package, then the update
process will terminate.
23.4.1 Update Package File Validation
The first level of update package validation is checking that the md5sum of the zip file matches the
md5sum in the [PackageFileName].md5 file of the update package.
Update packages are validated during the update process by computing the md5sum of each file
and comparing against the checksums stored in the checksums stored in the validation_file
included with the update package.
The update package is also checked to ensure it is valid for the platform where it is being used. For
example, an update package with firmware for a CompactPCI* CMM will not work on an
AdvancedTCA* CMM.
Table 96. Contents of the Update Package
File Name Description
CMM_RB.bin Redboot image to be stored in flash
CMM_FPGA.bin FPGA image
CMM_FFS.bin /etc image
CMM_OS.bin OS image
README Text file containing release notes for the update package
Update_Metadata File containing info on the update package and how it should be installed on the CMM
Utilities Sub-directory containing any utilities that might be required for the install.
validationfile File containing MD5 checksums for the files and scripts present in the update package.
saveList List of configuration files in /etc to be preserved across software updates.
Other Other components such as FRU files that may be necessary for the update.
version_history
List of all versions of firmware available for the platform in sequential order, with the
newest versions at the end of the list.
mpcmm0001.mib MIB file for SNMP.