Support Support Downloads Knowledge Base Case Manager My Juniper 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

[MX] Syslog message. *Cmerror Op Set: PLL Error: SI5345*

0

0

Article ID: KB35993 KB Last Updated: 29 Oct 2020Version: 2.0
Summary:

This article describes the error message "Cmerror Op Set: PLL Error: SI5345", which may be seen on MX FPCs: MPC7E.

Note: This is a troubleshooting article for a PFE ASIC Syslog Event. To view other documented Syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, refer to KB31893 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events.
Symptoms:

When the "​Cmerror Op Set: PLL Error: SI5345​" occurs, the following chassis alarm and log messages are reported.

Chassis Alarm:

root@MX960-01-re0> show chassis alarms no-forwarding

10 alarms currently active
Alarm time               Class  Description
2020-02-17 12:18:10 CET  Major  FPC 9 Major Errors - PLL Error code: 0x170011​

Log messages:

Feb 17 12:18:10.065 2020  MX960-01-re0 alarmd[20130]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 9 Major Errors - PLL Error code: 0x170011
Feb 17 12:18:10.065 2020  MX960-01-re0 chassisd[18625]: %DAEMON-3: FPC 9 sent action 0x44 that is not configured 0x2
Feb 17 12:18:10.065 2020  MX960-01-re0 craftd[18628]: %DAEMON-4:  Major alarm set, FPC 9 Major Errors - PLL Error code: 0x170011
Feb 17 12:18:39.357 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-0
Feb 17 12:18:39.358 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-1
Feb 17 12:18:39.359 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: ZL30362 0 synth 0 
Feb 17 12:21:39.526 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-0 
Feb 17 12:21:39.529 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-1 
Feb 17 12:21:39.530 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: ZL30362 0 synth 0 
Feb 17 12:24:39.993 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-0 
Feb 17 12:24:39.995 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-1 
Feb 17 12:24:39.995 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: ZL30362 0 synth 0
Feb 17 12:27:40.474 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-0 
Feb 17 12:27:40.476 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: SI5345-1 
Feb 17 12:27:40.476 2020  MX960-01-re0 : %PFE-3: fpc9 Cmerror Op Set: PLL Error: ZL30362 0 synth 0 

Indications:

  • Traffic impact or PFE packet forwarding is permanently compromised if errors are seen repeatedly.

  • A major alarm will be raised.

Cause:

The PLL error message is related to an issue with the MPC not being able to synchronize with the system clock. During boot time, an MPC7E card may report this major error alarm. This is caused by the insufficient time allowed for the MPC to lock on the clocking source.  A clock component supplied from a particular vendor may fail to clock an MPC7 reliably, which may result in a packet forwarding engine (PFE) not functioning.

Solution:
Perform the following steps to determine the cause and resolve the problem (if any).
  1. Collect the following show command outputs to investigate further.​​​

    Capture the output to a file (in case you need to open a Technical Service Request). To do this, configure each SSH client/terminal emulator to log your session.
      show log messages
      show log chassisd
      start shell pfe network <fpc#>
      show nvram
      show syslog messages
  1. Analyze the 'show' command output.

In the 'show log messages' file, review the events that occurred at or just before the appearance of the "Cmerror Op Set: PLL Error: SI5345" message.

  1. If the above message is a single-time occurrence, restart the FPC during a maintenance window to fix the issue. Restarting the FPC is seen to resolve the issue in most cases.

request chassis fpc slot <slot number> restart
  1. If the issue is seen repeatedly even after restarting the FPC, open a Technical Service Request for further investigation and assistance. Traffic or permanent packet forwarding on the Packet Forwarding Engine (PFE) may be impacted If the message is continuously logged and it could be a major issue in hardware and RMA'd.

    Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of Syslog messages. The first error message is usually the cause of all follow-on error messages. The subsequent collateral damage error messages can be ignored usually.

Modification History:
2020-10-28: Fixed typo in Solution item 1 (start shell network pfe <fpc#> To: start shell pfe network <fpc#>)
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