This article provides the steps to troubleshoot a DPC/MPC (FPC) on an MX device that is reporting errors.
This series of steps is a subr outine that is called multiple times from KB23173 - Resolution Guide - Troubleshoot Fabric Plane [juniper.net] .
Perform the following steps for MX DPC/MPC Troubleshooting:
Note: For the flowchart version of these steps, click the flowchart icon:
[Collect logs.]
[Identify the FPC with errors.]
In the output of " show chassis fabric plane ," which DPC (PFE) / MPC (PFE) has link errors?
show chassis fabric plane
Note: If you already identified the faulty DPC/MPC in KB23173 - Resolution Guide - Troubleshoot Fabric Plane [juniper.net] , then you can continue to Step 3 .
user@router> show chassis fabric plane Fabric management PLANE state Plane 0 Plane state: ACTIVE FPC 0 PFE 0 :Links ok PFE 1 :Links ok PFE 2 :Links ok PFE 3 :Links ok FPC 1 PFE 0 :Links ok PFE 1 :Link error FPC 0 PFE 0 :Links ok PFE 1 :Links ok PFE 2 :Links ok PFE 3 :Links ok
In the above example, Plane 0 is reporting an error on FPC1 (PFE1) (which is a type2 MPC card). Example outputs of a single plane reporting errors and multiple planes reporting errors are shown in KB23384 - Example outputs for Fabric reporting errors [juniper.net] .
Note: The number of PFEs under each FPC will vary according to the card type present in that slot. MPC type1 cards have one PFE. MPC type2 cards have 2 PFEs. MPC 16x10GE and DPC have 4 PFEs.
[Offline / Online the DPC with errors.]
Offline and then Online the corresponding DPC/MPC, which is reporting errors (in Step 2).
CAUTION : It is strongly recommended to perform this step during a Maintenance Window, because turning off the line card will cause service impact in the interfaces related to the FPC.
To Offline/Online a DPC/MPC, use " request chassis fpc slot <slot_no> offline|online ." For more information about this command, refer to request chassis fpc . Example: user@router> request chassis fpc slot <slot_no> offlineWait for few seconds and then do user@router> request chassis fpc slot <slot_no> online Continue to Step 4.
To Offline/Online a DPC/MPC, use " request chassis fpc slot <slot_no> offline|online ."
request chassis fpc slot <slot_no> offline|online
For more information about this command, refer to request chassis fpc .
Example:
user@router> request chassis fpc slot <slot_no> offlineWait for few seconds and then do user@router> request chassis fpc slot <slot_no> online
Continue to Step 4.
Observe the outputs of " show chassis alarms " and " show chassis fabric planes ."
show chassis alarms
show chassis fabric planes
Has the link error reported in Step 2 been corrected, and are the alarms cleared (after performing Offline/Online of the DPC)? No - Continue to Step 5 . Yes - If this is the first occurrence of any link errors on this DPC/MPC, then monitor the DPC/MPC for a period of time. If the errors reappear or if this has happened before on this DPC/MPC, collect the information specified in KB22637 - [M, MX, T Routers] Data Collection Checklist [juniper.net] under the "MX Fabric Plane" section, and open a case with your technical support representative .
Has the link error reported in Step 2 been corrected, and are the alarms cleared (after performing Offline/Online of the DPC)?
No - Continue to Step 5 .
Yes - If this is the first occurrence of any link errors on this DPC/MPC, then monitor the DPC/MPC for a period of time. If the errors reappear or if this has happened before on this DPC/MPC, collect the information specified in KB22637 - [M, MX, T Routers] Data Collection Checklist [juniper.net] under the "MX Fabric Plane" section, and open a case with your technical support representative .
[Re-seat the DPC/MPC with errors.]
Physically re-seat the DPC/MPC.
CAUTION : It is strongly recommended that you perform this step during a Maintenance Window, because turning off the line card will cause service impact in the interfaces related to the FPC. For guidelines, refer to the following: Replacing an MX960 MPC (can be used for replacing DPC cards too) Replacing an MX480 MPC Replacing an MX240 MPC Continue to Step 6.
CAUTION : It is strongly recommended that you perform this step during a Maintenance Window, because turning off the line card will cause service impact in the interfaces related to the FPC.
For guidelines, refer to the following:
Replacing an MX960 MPC (can be used for replacing DPC cards too)
Replacing an MX480 MPC
Replacing an MX240 MPC
Continue to Step 6.
Have the link errors and alarms been cleared (after re-seating the DPC/MPC)? Yes - If this is the first occurrence of any link errors on this DPC/MPC, then monitor the DPC/MPC for a period of time. If the errors reappear or if this has happened before on this DPC/MPC, collect the information specified in KB22637 - [M, MX, T Routers] Data Collection Checklist [juniper.net] under the "MX Fabric Plane" section, and open a case with your technical support representative . No - Do one of the following: Perform the steps detailed in KB23068 - MX SCB Troubleshooting Subroutine [juniper.net] if the instructions in KB23173 - Resolution Guide - MX - Troubleshoot Fabric Planes [juniper.net] instructed you to (that is, the Fabric is reporting the error in " show log messages ", and only one plane is reporting the error for a single DPC/MPC). If the issue is not resolved, collect the information specified in KB22637 - [M, MX, T Routers] Data Collection Checklist [juniper.net] under the "MX Fabric Plane" section, and open a case with your technical support representative .
Have the link errors and alarms been cleared (after re-seating the DPC/MPC)?
No - Do one of the following:
Perform the steps detailed in KB23068 - MX SCB Troubleshooting Subroutine [juniper.net] if the instructions in KB23173 - Resolution Guide - MX - Troubleshoot Fabric Planes [juniper.net] instructed you to (that is, the Fabric is reporting the error in " show log messages ", and only one plane is reporting the error for a single DPC/MPC).
show log messages
If the issue is not resolved, collect the information specified in KB22637 - [M, MX, T Routers] Data Collection Checklist [juniper.net] under the "MX Fabric Plane" section, and open a case with your technical support representative .
2022-03-06: Article reviewed and updated to reflect current information