Verifying Fpc Failure; Document Events Prior To The Fpc Failure - Juniper M Series Monitoring And Troubleshooting Manual

M Series and T Series Routers Monitoring and Troubleshooting Guide
Meaning
Related
Documentation

Verifying FPC Failure

Document Events Prior to the FPC Failure

Purpose
Action
224
idx=4, tnpaddr=19
Nov 11 15:59:06 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 3 restart
Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener
idx=5, tnpaddr=22
Nov 11 15:59:07 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 6 restart
Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener
idx=6, tnpaddr=20
Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 4 restart
Nov 11 15:59:08 m40-2 /kernel: pfe_listener_connect: conn established: listener
idx=7, tnpaddr=23
Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 7 restart
Nov 11 15:59:09 m40-2 /kernel: pfe_listener_connect: conn established: listener
idx=8, tnpaddr=21
Nov 11 15:59:09 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 5 restart
The log file is a database that provides the date, time, and a component status
chassisd
message. The chassisd database is dynamic. It is initialized at router startup and is updated
when components are added or removed. The sample command output shows the
results of a multiple item search in the log file (
the FPC, kernel, and Trivial Networking Protocol (TNP) that indicate communication
issues between the Routing Engine and the Packet Forwarding Engine components.
Checklist for Monitoring FPCs on page 213
To verify an FPC failure:
Document Events Prior to the FPC Failure on page 224
1.
Checking the FPC Installation on page 225
2.
Checking the FPC fuses on page 225
3.
Take the FPC Offline on page 227
4.
5. Perform an FPC Swap Test on page 227
Displaying the FPC Software Version Information on page 227
6.
Display the FPC Hardware Information on page 228
7.
Locating the FPC Serial Number ID Label on page 228
8.
To determine the reason for an FPC failure by documenting events that occurred prior
to the failure.
To document an FPC failure, record any events that may have led to the FPC failure, such
as a software upgrade, hardware upgrade, or a reset. Capture system log file error
messages 5 minutes before and after a failure event by using the
command and use the time and date stamp to browse the file. You can use the
messages | match command to view certain common error messages and help identify
why an FPC failure occurred.
): error messages for
"fpc | kernel | tnp"
show log messages
Copyright © 2012, Juniper Networks, Inc.
show log