JUNOS Internet Software Network Operations Guide: Hardware
190 ! Verifying PIC Failure
Step 2: Display Error Messages in the System Log File
Action To display PIC error messages in the system log file, use the following CLI
command:
user@host> show log messages | match PIC
Sample Output
user@host>
show log messages | match PIC
Apr 8 10:01:20 aspirin scb CM: PIC 0/2, ID 0x0206, hardware error, offlined
Apr 8 10:01:20 aspirin alarmd[2671]: Alarm set: FPC color=RED, class=CHASSIS,
reason=PIC 0/2 failed to initialize
Apr 8 10:01:20 aspirin fpc0 PIC: PIC 2 discovery error (1)
Apr 8 10:01:20 aspirin fpc0 CMFPC: Hardware error discovering PIC 2, ID 0x0206
Apr 8 10:01:21 aspirin scb CM: ALARM SET: (Major) Slot 0: PIC 0/2 failed to
initialize
What It Means When a PIC fails, the messages system log file records the time the failure or event
occurred, the severity level, a code, and a message description. Use the
show log
messages
command to browse error messages that are generated at least 5
minutes before and after a PIC event. You can also use the
show log messages |
match PIC
command to view specific PIC error messages with common
information. Use this information to diagnose a PIC problem and to let the Juniper
Networks Technical Assistance Center (JTAC) know what error messages were
generated and the router events prior to the problem. For more information about
system log messages, see the JUNOS System Log Messages Reference.
Verifying PIC Failure
Steps To Take To verify PIC failure, follow these steps:
1. Perform a PIC Swap Test on page 190
2. Display PIC Hardware Information on page 191
3. Locate the PIC Serial Number ID Label on page 192
Step 1: Perform a PIC Swap Test
Action To perform a swap test on a PIC, follow these steps:
1. Ensure that the PIC is firmly seated in the FPC or the FPC slot.
2. If the PIC is firmly seated and still fails, remove it from the FPC. Follow the PIC
removal procedure in the appropriate router PIC guide.
To Next Page
Loading...
Need help?
General
