Filter
Top Products
208 MPCMM0001 Chassis Management Module Software Technical Product Specification
Updating CMM Software
Note: Performing an update to an earlier version of the firmware will cause a loss of some configuration
data (such as SNMP trap address configuration which is stored in /etc/cmm.cfg) because files with
a priority of 2 are not synchronized on updates to earlier versions.
23.6 Update Mode
To perform the update, the CMM will enter an update mode to prevent interference from other
processes that may write to the flash and unmount the JFFS2 drives that may need to be re
partitioned.
In the update mode, all CMM applications will be stopped. Any user-defined processes that are
running must also be stopped. Hooks in the update process will be provided to allow these
processes to be stopped by calling user scripts located in /home/update/scripts/ if they exist. The
update process will execute any scripts that match the following pattern: /home/update/scripts/K*.
Scripts will be execute in alpha-numeric sort order. Getting a directory listing using the “ls”
command will display the order the scripts will run. User scripts should follow the convention of
returning a “0” if successful and a non-zero for failure. The update process will not fail if a script
returns a failure; however, the update process will fail if the flash drives can not be unmounted
when necessary.
Before unmounting the JFFS2 drives (/etc and /home), /etc will be copied to ram disk /usr/local/
cmm/temp/update/etc to retain user and system configuration information.
Because all CMM applications are stopped, systems running with redundant CMMs will lose
redundancy during the firmware update process.
Table 97. SaveList Items and Their Priorities
File Priority
/etc/passwd 1
/etc/shadow 1
/etc/cmm/sel_* 1
/etc/cmm/cmm_sel 1
/etc/snmp*.conf 1
/etc/ifcfg-eth* 1
/etc/HOSTNAME 1
/etc/ftp* 1
/etc/group 1
/etc/profile 1
/etc/versions* 1
/etc/issue 1
/etc/issue.net 1
/etc/pump.conf 1
/etc/*.cfg 2
/etc/cmm/sensors.ini 2
/etc/cmm/fantray.cfg 2