Knowledge Search


×
 

[MX] FPC crashes when MIC is offlined and brought online after two back-to-back PIC bounces

  [KB34871] Show Article Properties


Summary:

This article explains why the Flexible PIC Concentrator (FPC) may crash when the MIC is taken offline and then brought online after two back-to-back PIC bounces, and indicates what must be done to prevent the crash.

 

Symptoms:

With MIC-3D-16CHE1-T1-CE, if IFDs change within an interval of 2 minutes when configuring framing, the FPC might crash after the MIC is taken offline and brought online again:

delete interfaces ce1-x/x/x no-partition interface-type e1          <<<  Framing E1 removed 

set interfaces ce1-x/x/x partition 1 timeslots 1 interface-type ds  <<< Framing DS configured within 2 mins interval
set interfaces ce1-x/x/x partition 2 timeslots 2 interface-type ds
set interfaces ce1-x/x/x partition 3 timeslots 3-4 interface-type ds
set interfaces ce1-x/x/x partition 4 timeslots 5-8 interface-type ds

To check the crash, use the following:

router@mx480 > show system core-dumps
-rw-r--r--  1 root  wheel   66258182 Jul 23 16:33 /var/crash/core-NGMPC2.gz.core.0

 

Cause:

This issue arises because enough time has not been given between two PIC bounces. Ideally, while performing framing configuration, the IFDs should be allowed to come up before another PIC bounce is executed. This issue is seen if IFD creation is not done properly before the MIC is taken offline.

 

Solution:

The recommendation is to give an interval of 5 minutes or more between two back-to-back PIC bounces for IFD creation.

 

Related Links: