Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Major Errors - BCM8238X Error code: 0x490001

0

0

Article ID: KB37440 KB Last Updated: 14 Dec 2021Version: 2.0
Summary:

This article explains the root cause, symptoms, and solution for the major alarm "BCM8238X_CMERROR_FW_TUNING_STOPPED (0x490001), severity: major, module: BCM8238X, type: BCM8238X SerDes firmware did not complete tuning" that is seen on all EX/MX/PTX/QFX/SRX Series platforms running Junos OS.

Symptoms:

In some cases, the alarm persists in the show chassis alarms output and in some cases the alarm sets and clears itself continuously. 

This alarm can be a genuine transient software issue or it can be a false positive. 

In case of a genuine transient issue, the alarm may persist and interfaces on the FPC might remain DOWN. 

The following logs could be seen during an issue:

[Jun 26 22:25:21.009 LOG: Err] bcm8238x_fw_mon_run_sm: t6e-bcm82381-3/0-PHY1-QuadA - BCM SerDes firmware is now bad for [et-3/0/2 lane:0xf]
[Jun 26 22:25:21.030 LOG: Info] Error: /fpc/3/pfe/0/cm/0/BCM8238X/0/BCM8238X_CMERROR_FW_TUNING_STOPPED (0x490001), severity: major, module: BCM8238X, type: BCM8238X SerDes firmware did not complete tuning
[Jun 26 22:25:21.185 LOG: Err] Cmerror Op Sub Set: BCM8238X: t6e-bcm82381-3/0-PHY1-QuadA: SerDes firmware did not complete tuning for [et-3/0/2 lane:0xf]. Chip reset is needed; this will affect [et-3/0/2 lane:0xf]  and [et-3/0/3 lane:0xf]. Run VTY cmd 'test bcm8238x 3 chip-re[Jun 26 22:25:27.015 LOG: Info] bcm8238x_fw_mon_run_sm: t6e-bcm82381-3/0-PHY1-QuadA - BCM SerDes firmware is now good for [et-3/0/2 lane:0xf]
[Jun 26 22:25:27.033 LOG: Err] Cmerror Op Sub Clear: BCM8238X: t6e-bcm82381-3/0-PHY1-QuadA: SerDes firmware tuning is now good for [et-3/0/2 lane:0xf]
[Jun 26 22:30:36.046 LOG: Err] t6e_dfe_tuning_state:et-3/0/2 - Failed to dfe tuning count 10
[Jun 26 22:32:27.128 LOG: Err] t6e_dfe_tuning_state:et-3/0/3 - Failed to dfe tuning count 10
[Jun 26 22:51:36.205 LOG: Err] t6e_dfe_tuning_state:et-3/0/5 - Failed to dfe tuning count 10
[Jun 26 22:53:15.275 LOG: Err] t6e_dfe_tuning_state:et-3/0/3 - Failed to dfe tuning count 10
[Jun 26 23:05:16.296 LOG: Err] t6e_dfe_tuning_state:et-3/0/2 - Failed to dfe tuning count 10
[Jun 26 23:12:45.422 LOG: Err] t6e_dfe_tuning_state:et-3/0/3 - Failed to dfe tuning count 10

A corresponding alarm will be generated as well:

Jun 26 22:25:22 alarmd[2636]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 3 Major Errors - BCM8238X Error code: 0x490001
Jun 26 22:25:22 craftd[2375]: %DAEMON-4: Major alarm set, FPC 3 Major Errors - BCM8238X Error code: 0x490001
Jun 26 22:25:27 : %PFE-3: fpc3 Cmerror Op Sub Clear: BCM8238X: t6e-bcm82381-3/0-PHY1-QuadA: SerDes firmware tuning is now good for [et-3/0/2 lane:0xf]
Jun 26 22:25:27 alarmd[2636]: %DAEMON-4: Alarm cleared: FPC color=RED, class=CHASSIS, reason=FPC 3 Major Errors - BCM8238X Error code: 0x490001
Jun 26 22:25:27 craftd[2375]: %DAEMON-4: Major alarm cleared, FPC 3 Major Errors - BCM8238X Error code: 0x490001
Cause:

On MX Series routers, an event where the BCM8238X SerDes firmware has stopped and not completed tuning generates the corresponding alarm and error logs.

In most cases, these alarms could be false positives. The software is too quick to declare the fault and take the corresponding action.

In some rare cases, when the BCM8238x retimer is reset with the test command, the retimer resets fine and the firmware loads into the retimer but the required initialization parameters, such as repeater mode, reference power voltage, and PHY mode, do not get initialized in the software.

Solution:

Before declaring a CMError indicating that the BCM82381 SerDes firmware has stopped tuning, wait for a couple of periodics to confirm the error condition. This is to avoid false positives (bogus chassis major alarms).

The genuine software issue is addressed in Junos OS releases 18.4R3-S9 and later. The false positive issue is addressed in Junos OS releases 17.4R3-S4 and later.

Modification History:
2021-12-13: Added QFX series.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search