Supported Platforms
Configuring Sanity Polling for FPCs on T Series Routers
T Series routers running Junos OS Release 11.4 and later support the sanity polling feature. You can configure the sanity-poll statement for a particular FPC to start a periodic sanity check for that FPC. The periodic sanity check includes checking for FPC error conditions such as “register sanity issues,” “high temperature,” “hardware failure,” and so on. If you do not configure the sanity-poll statement, then sanity polling is disabled.
 | Note: Currently, periodic sanity check is performed only on the routing chip register. |
Sanity polling periodically checks for an error condition in an FPC and performs the appropriate actions in case of an error.
To configure sanity polling for an FPC, include the sanity-poll statement and its substatements at the [edit chassis fpc slot-number] hierarchy level:
| Note: On a TX Matrix or TX Matrix Plus router, you can configure the sanity-poll statement at the [edit chassis lcc number fpc number] hierarchy level. |
The sanity-poll statement comprises the following substatements:
- The retry-count statement specifies the number
of rechecks to be performed after the occurrence of a particular error
condition. If an error exists in all the periodic checks, then sanity
polling reports an error and proceeds to perform the appropriate actions
(described as options of the on-error statement).
For example, if the periodic sanity check detects an error in the FPC and if you configure the retry count number to 15, sanity polling does not report the error immediately. Sanity polling checks 15 times for the same error condition. If an error persists in all 15 rechecks, then it reports an error and takes the appropriate actions.
If you do not configure the retry-count statement, then by default, the sanity-poll statement rechecks the detected error 10 times before reporting an error condition.
- If sanity polling detects an error condition, the on-error statement performs the appropriate actions to eliminate
the error.
The following actions are common to all kinds of error conditions:
- To generate a chassis alarm, configure the raise-alarm statement. The chassis alarm is displayed in the front panel of the chassis.
- To reboot the FPC after generating a core file, configure the power cycle statement. This statement is useful for temporary software errors that are eliminated after reboot.
- To halt the FPC, configure the power off statement.
This statement is useful in case of permanent hardware failure.
Caution: The power off statement halts the FPC. Ensure that you have backup paths through a different FPC to avoid service outage.
Note: The power cycle and power off statements are mutually exclusive: You can configure either the power cycle or the power off action for an error.
- To trigger the core file, configure the write-coredump statement.
You can configure multiple actions for a given FPC. If you do not configure any actions, the sanity-poll statement generates only FPC system log messages.
