Config Router

  • Google Sheets
  • CCNA Online training
    • CCNA
  • CISCO Lab Guides
    • CCNA Security Lab Manual With Solutions
    • CCNP Route Lab Manual with Solutions
    • CCNP Switch Lab Manual with Solutions
  • Juniper
  • Linux
  • DevOps Tutorials
  • Python Array
You are here: Home / Juniper / CHASSISD_PEM_INPUT_BAD

CHASSISD_PEM_INPUT_BAD

May 14, 2016 by Marques Brownlee

The

CHASSISD_PEM_INPUT_BAD

message reports that the chassis process (chassisd) detected the indicated error condition for the indicated power entry module (PEM).

When a  CHASSISD_PEM_INPUT_BAD event occurs, messages similar to the following are reported:

chassisd[18661]: CHASSISD_PEM_INPUT_BAD: status failure for power supply 5 (status bits: 0x0); check circuit breaker
chassisd[18661]: CHASSISD_PEM_INPUT_BAD: Input failure for power supply 14 (status bits: 0x4); check circuit breaker
chassisd[3784]: %DAEMON-4-CHASSISD_PEM_INPUT_BAD: Input failure for power supply 0 (status bits: 0x6); check circuit breaker

These logs indicate a problem with the input voltage to the PEM, which may be due to a flipped circuit breaker, an uncabled PEM, a seating problem with the PEM unit, an incorrect voltage setting, or an actual hardware failure.

Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.

1. Collect the show command output.

Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

show log messages
show log chassisd
show chassis craft-interface
show chassis alarms
show chassis environment
show chassis environment pem
show chassis power (MX-series)

2. Analyze the show command output.

In the ‘show log messages’ output, review the events that occurred at or just before the appearance of the

CHASSISD_PEM_INPUT_BAD

message. Frequently these events help identify the cause.

3. During a maintenance window, as it will impact transit traffic, try the following:

  • Check if the chassis requires redundant PEM units to be present. If so, ensure that they are present and inserted in the correct slots. For example, certain platforms may allow four PEM modules, but only two are required. However, if only two are used, they need to be in specific slots. The number of available slots, minimum PEM units required, and which slots must be populated first are all platform-dependent information. See the Hardware Documentation for your product in the Technical Documentation for more information.
  • Check the voltage type and verify that the value is correct for that PEM unit (that is, 120 volt vs. 240 volt, DC vs. AC).
  • Verify that the circuit breaker has not been tripped. You may need to purposely flip it off and on again to make sure that it is on. Note that these alarms and logs might be seen if the circuit breaker is turned off, or if there is no power feed connected.
  • Try reseating the PEM unit.
  • Try swapping with a spare, if available, or try swapping two PEM units in their respective slots to see if the message follows the unit or the slot.

Related

Filed Under: Juniper Tagged With: CHASSISD_PEM_INPUT_BAD

Recent Posts

  • How do I give user access to Jenkins?
  • What is docker volume command?
  • What is the date format in Unix?
  • What is the difference between ARG and ENV Docker?
  • What is rsync command Linux?
  • How to Add Music to Snapchat 2021 Android? | How to Search, Add, Share Songs on Snapchat Story?
  • How to Enable Snapchat Notifications for Android & iPhone? | Steps to Turn on Snapchat Bitmoji Notification
  • Easy Methods to Fix Snapchat Camera Not Working Black Screen Issue | Reasons & Troubleshooting Tips to Solve Snapchat Camera Problems
  • Detailed Procedure for How to Update Snapchat on iOS 14 for Free
  • What is Snapchat Spotlight Feature? How to Make a Spotlight on Snapchat?
  • Snapchat Hack Tutorial 2021: Can I hack a Snapchat Account without them knowing?

Copyright © 2025 · News Pro Theme on Genesis Framework · WordPress · Log in