Description

This article explains why the "DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(13)" log message may be seen on VC-Mm or the new Primary routing engine (RE) for empty FPC slots, after a local switchover or a global switchover on MX-VC devices.

It also clarifies that these logs are expected after local or global switchover, and have no service impact.

 

Symptoms

On VC-Bs, execute local primary role switchover: 

{local:member1-re0}
root@router-re0> request chassis routing-engine master switch         
Jul 17 19:32:46
Toggle mastership between routing engines ? [yes,no] (no) yes
Jul 17 19:32:47

On VC-Mm, the following log is observed: 

Jul 17 19:34:29.176  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(17)
Jul 17 19:34:29.184  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(18)
Jul 17 19:34:29.190  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(19)
Jul 17 19:34:29.197  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(20)
Jul 17 19:34:29.204  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(21)
Jul 17 19:34:29.211  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(22)
Jul 17 19:34:29.217  jtac-mx480-r2040-re0 scchassisd[14343]: %DAEMON-5-CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(23)

In the above output, FPC 17 to FPC 23 are empty slots in MX-VC.

When doing a global switchover, the same logs will also show on the new primary Routing Engine. 

 

Solution

During a local or global switchover on MX-VC, the chassisd daemon needs to fall back to a clean start, and therefore, cycles through all potential line cards, whether they are present or not. The above log message is reported for a potential line card when the daemon cycles through the cards.

This is expected behavior, and has no service impact on MX-VC. The device is functioning as per design.

This log will also appear when the RE reboots, because the chassisd daemon cycles through all potential line cards when the RE reboots.

 

No action is required because these logs are expected during VC local and global switchover, and there is no service impact. They can be safely ignored.

 

Modification History

2021-04-06: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives