Description

Users may see the "Failed to read CPLD mdio optics present" error on MX-960 and MX2020 routers that have 1X100GE CFP Physical Interface Cards (PICs).

This article explains what you can do to resolve this error.

Symptoms

The following alarm and logs are seen:

user@router> show chassis alarms | no-more
1 alarms currently active
Alarm time               Class  Description
2022-02-22 09:19:41 UTC  Major  FPC 17 PIC 0 Failure

[Feb 22 09:19:41.405 LOG: Err] CMT: Error initializing PIC 0, ID 0x0a53
[Feb 22 09:22:03.785 LOG: Err] cmic_i2cs_cpld_get_opt_present:CMIC(17/1) - Failed to read CPLD mdio optics present
[Feb 22 09:22:03.785 LOG: Err] cmic_cfp_check_presence():CMIC(17/1) Failed to probe CFP present
[Feb 22 09:22:03.785 LOG: Err] cmic_optic_periodic:CMIC(17/1) - MIC cfp fails to check presence (15)
[Feb 22 09:22:03.785 LOG: Err] XMCHIP(0): xmchip_xxlce_mtip_cge_inst_mdio_c45_read: Couldn't get the XXLCE MAC handler - mdio_control_num 0
[Feb 22 09:22:03.785 LOG: Err] cmic_i2cs_cfp_los_latch: Failed to read CPLD's mdio (mic 1, addr 4)
[Feb 22 09:22:03.785 LOG: Err] XMCHIP(0): xmchip_xxlce_mtip_cge_inst_mdio_c45_read: Couldn't get the XXLCE MAC handler - mdio_control_num 0

Solution

The "Failed to read CPLD mdio optics present" error points that there is loss of management keepalives between the FPC and the PIC (CFP). Also, I2C errors point to hardware issues in the CFP module or the MIC card.

MDIO is the management interface between the host (FPC for Juniper MX devices) and the CFP (PIC) for control and diagnostics. The host uses this interface to control and monitor the startup, shutdown, and normal operation of the CFP modules that it manages.

MDIO was originally defined in Clause 22 of IEEE RFC802.3 as a single MDIO interface to access registers. These registers provide status and control information such as link status, speed ability and selection, power down for low-power consumption, duplex mode (full or half), auto-negotiation, fault signaling, and loopback.

Steps to Resolve Error

  1. Restart the PIC.

  2. If restarting the PIC does not help/cannot be done, then restart the FPC.

  3. If restarting the PIC or FPC does not help, then replace the PIC or FPC.

FPC 1            REV 09   ***-******   ********          MPC4E 3D 2CGE+8XGE
  PIC 0                   BUILTIN      BUILTIN           4x10GE SFPP
  PIC 1                   BUILTIN      BUILTIN           1X100GE CFP
  PIC 2                   BUILTIN      BUILTIN           4x10GE SFPP
  PIC 3                   BUILTIN      BUILTIN           1X100GE CFP

In the above output, the PIC is builtin on the FPC. Hence the command to restart the PIC is not executed.

user@router> request chassis pic pic-slot 1 fpc-slot 1 offline
FPC slot 1 does not support this command

If the PIC is not builtin on the FPC, then the following command to restart can be executed.

request chassis pic pic-slot 1 fpc-slot 1 offline

Modification History

2023-05-30: Initial version
2025-05-06 : Removed sensitive info and make it public.