JUNOS Internet Software Network Operations Guide: Hardware
122 ! Verifying Router Component Failure
Step 3: Display Component Errors in the Chassis Daemon Log File
Action To display component error messages in the chassis daemon (chassisd) log file, use
the following CLI command:
user@host> show log chassisd
Sample Output
user@host>
show log chassisd
Jun 11 20:45:08 *** inventory change ***
Jun 11 20:45:08 CIP set alarm 0x1
Jun 11 20:45:08 alarm op fru 34 op 1 reason 1
Jun 11 20:45:08 send: red alarm set, class 100 obj 112 reason 1
Jun 11 20:45:08 CIP removed
What It Means The chassisd database provides the date, time, and a component status message.
The
chassisd database is dynamic. It is initialized at router startup and is
maintained when components are added or removed. The command output
displays error messages that are generated when a Connector Interface Panel (CIP)
fails or is removed.
Verifying Router Component Failure
Action To verify router component failure, perform a swap test on a component as follows:
1. Replace a failed component with one that you know works.
2. Verify the component status by using the appropriate
show chassis
component-name
command. If the replaced component works, the original
component is defective.
3. If the replaced component does not work, remove it and check the component
midplane connector for bent pins. If the replaced component still does not
work, contact JTAC, and see “Return the Failed Component” on page 86.
Replacing a Failed Component
Action To return the router chassis, you need to know the chassis serial number. To display
the midplane serial number, use the following CLI command:
user@host> show chassis hardware
Sample Output
m160@host> show chassis hardware
Item Version Part number Serial number Description
Chassis 101 M160
Midplane REV 02 710-001245 S/N AB4107
FPM CMB REV 01 710-001642 S/N AA2911
FPM Display REV 01 710-001647 S/N AA2999
[...Output truncated...]
CAUTION: Before performing a swap test, always check for bent pins in the
midplane and check the component for stuck pins in the connector. Pins stuck in
the component connector can damage other good slots during a swap test.