The chassisd process (chassisd) encountered an error during the In Service Software Upgrade (ISSU) Process.
When a CHASSISD_ISSU_ERROR event occurs, a message similar to the following is reported:
|
1 2 3 4 5 |
chassisd[1179]: CHASSISD_ISSU_ERROR: Daemon ISSU Abort -1(NSR sync not complete: PIM) chassisd[6511]: CHASSISD_ISSU_ERROR: Daemon ISSU Abort -1(chassisd restarted) chassisd[6511]: CHASSISD_ISSU_ERROR: GENCFG_ISSU DELETE 2(No such file or directory) CHASSISD_ISSU_ERROR: GENCFG_ISSU DELETE 55(No buffer space available) chassisd[18084]: CHASSISD_ISSU_ERROR: Daemon ISSU Abort -1(NSR sync not complete: BGP) |
This is usually due to the configuration not matching the requirements of doing ISSU. However it may also be due to an FPC or PIC that is not compatible with ISSU. The exact cause will have to be determined by an examination of the associated log data.
Examine the following outputs to help determine the cause of this message:
|
1 2 3 |
show log messages show log chassisd show configuration |
Look for any related events that occurred at or just before the CHASSISD_ISSU_ERROR message in the syslog and chassisd outputs. Also check the configuration to verify that it meets the requirements for doing ISSU. (i.e. NSR disabled, etc.)
Perform these steps:
- If all the requirements of ISSU have been met, then check the hardware being used, as some hardware (FPC/PIC) may not be compatible with ISSU.
- If the log messages continue, open a case with your technical support representative to investigate the issue further.
Leave a Reply