Description

It can be seen during a MX-VC (Virtual-Chassis) ISSU upgrade that the following syslog errors.


Sep 26 05:41:35  keekar1 chassisd[29704]: CHASSISD_VERSION_MISMATCH: Version mismatch:   chassisd message version 2   FPC 5 message version 2   local IPC version $Revision: 1366881 $   remote IPC version $Revision: 1363201 $
Sep 26 05:41:36  keekar1 chassisd[29704]: CHASSISD_VERSION_MISMATCH: Version mismatch:   chassisd message version 2   FPC 2 message version 2   local IPC version $Revision: 1366881 $   remote IPC version $Revision: 1363201 $

Symptoms

During ISSU for MX-VC (Virtual-Chassis) the VCBm (Backup protocol master) is upgraded first.  During the ISSU, a GRES is automtically peformed.  At this point the following logs will be seen on the new VCMm (protocol master).

Sep 26 05:41:35  keekar1 chassisd[29704]: CHASSISD_VERSION_MISMATCH: Version mismatch:   chassisd message version 2   FPC 5 message version 2   local IPC version $Revision: 1366881 $   remote IPC version $Revision: 1363201 $
Sep 26 05:41:36  keekar1 chassisd[29704]: CHASSISD_VERSION_MISMATCH: Version mismatch:   chassisd message version 2   FPC 2 message version 2   local IPC version $Revision: 1366881 $   remote IPC version $Revision: 1363201 $

Solution

These log messages are not an issue and are not impacting.  During the ISSU there is a time period that the two systems are running different version of code.  These logs are only seen on the MX-VC ISSU because the ISSU process on the VCBm is upgraded to a newer release while the FPC's are still running the older release.  This is the only time when these logs will be seen.

Modification History

Changing font
08/26/2024 - Adding EX4600

Related Information

1764794 [Confidential] - JDI-RCT:M/Mx: during ISSU in MXVC , observed errors @ CHASSISD_VERSION_MISMATCH: Version mismatch: chassisd message version 2 FPC 5 message version 2 local IPC version $Revision: 1366881 $ remote IPC version $Revision: 1363201 $