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

[Archive] [SRX] Chassisd logs showing errors for cards that do not exist

0

0

Article ID: KB24222 KB Last Updated: 10 Jul 2020Version: 2.0
Summary:

This article describes the issue of SRX chassisd logs showing errors for cards that do not exist.

 

Symptoms:

The Chassisd process is shown as high and the Chassisd logs are showing messages for the PIM Slots, which do not have a PIM card; that is the PIM Card is placed in only PIM Slot 2.

root> show system processes extensive | match chassisd 
 1018 root         1  84    0 32472K 16420K RUN    0 193.1H  8.25% chassisd

This process is high for SRX650, which has only 1 IOC. Compare this to a fully populated chassis of SRX3600 and notice the chassisd process:

1138 root        1 102    0 30324K 12484K select  22.8H  6.59% chassisd

root> show log chassisd

May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 1
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 3  < Notice PIM 2 is missing. That is the existing slot.
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 4
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 5
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 6
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 7
May  4 17:33:31  mbus_srxmr_handle_interrupts: Error -1 in reading existing status of PIM 8

 

Cause:
  • This might be a CPLD issue. CPLD is the programmable logic, which is on a chip on the motherboard, that detects the presence of PIM/FPC and various other PIM/FPC hardware conditions; in addition to the handling of power and configuration button, and so on.

  • This can be caused by the contact of the FPC/Card, which is in slot 2, with the midplane connector.

  • The errors in the chassisd logs are due to the interrupt vector in CPLD indicating that some of interrupt bits to have to be set; however the corresponding i2c read for the FPC was not going through, as there was no FPC present.

  • This kind of situation is very rare; but due to some changes on the device (that is enabling chassis traceoptions and so on) can trigger this issue.

 

Solution:
  1. Check if you have set chassis traceoptions flag cmb configured; if so, delete chassis traceoptions and see if there is any improvement.

  2. Also, remove the card in slot 2 and reboot to see if the issue goes away. Then replace the same card in slot 2 and check again.

 

Modification History:

2020-07-10: Archived due to reference to EOL FW

 

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