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

[MX/PTX] Alarm 'CB X CPU Die Temp Sensor Access Failed' is seen after a reboot

0

1

Article ID: KB37363 KB Last Updated: 20 Sep 2021Version: 1.0
Summary:

The alarm, 'CB 1 CPU Die Temp Sensor Access Failed' is seen after a reboot.

Symptoms:

The following alarm appears on the chassis once a system (usually on VMhost based platforms) comes up after a reboot (for Junos upgrade) and the temp sensor on the CB is not detected correctly.

@router-name> show chassis alarms
3 alarms currently active
Alarm time               Class  Description
2021-03-29 16:23:13 PDT  Major  CB 1 CPU Die Temp Sensor Access Failed
2021-03-29 16:23:13 PDT  Major  CB 0 CPU Die Temp Sensor Access Failed
Solution:
  1. Restart the LCMD process by logging into the host prompt

    > start shell user root
    # vhclient -s    <--- This will take you to the vmhost prompt.
    root@router-node:~#  cd /var/tmp
    
    root@router-node:/var/tmp# systemctl status lcmd
    ● lcmd.service - lcmd service
       Loaded: loaded (/usr/sbin/lcmd; static; vendor preset: enabled)
       Active: active (running) since Wed 2021-07-28 05:33:12 SAST; 2 days ago
    Main PID: 4421 (lcmd)
       CGroup: /system.slice/lcmd.service
       └─4421 lcmd
    
    root@router-01-node:/var/tmp# systemctl restart lcmd
    
    root@router-01-node:/var/tmp# systemctl status lcmd
    ● lcmd.service - lcmd service
       Loaded: loaded (/usr/sbin/lcmd; static; vendor preset: enabled)
       Active: active (running) since Fri 2021-07-30 07:13:01 SAST; 36s ago
      Process: 26495 ExecStop=/etc/init.d/lcmd stop (code=exited, status=0/SUCCESS)
      Process: 26510 ExecStart=/etc/init.d/lcmd restart (code=exited, status=0/SUCCESS)
    Main PID: 26524 (lcmd)
       CGroup: /system.slice/lcmd.service
       └─26524 lcmd
  2. If the step above does not clear the alarm, try the following:

    1. Toggle the primary role. For example, if RE0 is primary and RE1 is backup, force RE1 to become the new primary. Check if the alarms get cleared.
    2. Reboot the previous primary RE (RE0 which is the new backup now).
    3. Toggle back the primary role so that RE0 becomes the new primary.
  3. If the alarms are still not cleared, collect the RSI, var/log and contact your JTAC Representative for further investigation.

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