Filter
Top Products
MPCMM0001 Chassis Management Module Software Technical Product Specification 209
Updating CMM Software
23.7 Update_Metadata File
The Update_Metadata file included in the update package is used by the update process to
determine the platform, firmware package version, files, sequence, update method, location, and
any other data required to update the individual components in the update package.
23.8 Firmware Update Synchronization/Failover Support
The following CMM versions and corresponding update directions will include support for
heterogeneous synchronization.The CMM will continue to support behavior from firmware prior to
version 5.2 for scenarios where a pre-configured newer CMM is introduced in a chassis with an
older CMM.
The CMM will seamlessly synchronize all data items irrespective of version differences. User
scripts (/home/scripts/*) is configurable to control its synchronization between differing CMM
versions. Between same versions, this data will be synchronized.
Failover to a newer CMM firmware version (after an update and any other redundancy
establishment) is configurable - automatic/manual.
The CMM also allows a build independent failover, allowing failover even to older firmware
versions.
23.9 Automatic/Manual Failover Configuration
The CMM firmware now provides the user control over CMM failover when redundancy is
established following a firmware update. The user can now decide if the CMM should or should
not automatically failover to a newer CMM firmware version.
A new failover configuration flag - -"FailoverOnRedundancy" in the CMM configuration file (/etc/
cmm.cfg) decides if an automatic or manual failover is desired. The configuration flag can be
modified using the cmmget/cmmset commands. This flag can be read/set through any of the CMM
interfaces (i.e., CLI, SNMP and RPC).
The setting of this flag will be in effect only starting the next time redundancy is established.
Note: The regular CMM health monitoring failover will continue to be in effect irrespective of the value
of this flag. Other conditions such as CMM health, switch health (CompactPCI only), network
connectivity that determine an automatic failover will continue to be in effect. This means that
Table 98. CMM Update Directions
CMM Versions Update Direction Supported
4.x – 5.1 Upgrade/Downgrade with behavior prior to 5.2
4.x – 5.2
Upgrade only
Note: the corresponding downgrade scenario (5.2->4.x), though
possible from a CMM update point of view does not guarantee
stable data synchronization behavior
5.1 – 5.2 Upgrade/Downgrade
5.2 – 6.1 (+/-) Upgrade/Downgrade