action (chassis error)
Syntax
action {
alarm;
get-state;
log;
trap;
(reset | offline | reset-pfe | disable-pfe);
}Hierarchy Level
[edit chassis fpc slot-number error fatal]
[edit chassis fpc slot-number error major]
Description
Depending on the severity level of an error, you can configure one or more actions
for the router to perform. For example, if the severity level of an error is major,
you can configure the system to raise an alarm and restart the FPC. You can use
offline-pfe and reset-pfe options to map
errors belonging to pfe category.
Options
| alarm |
Raise an FPC alarm. |
| disable-pfe |
(PTX routers) Disable Packet Forwarding Engine interfaces on an FPC. (MX240, MX480, MX960, MX2020 PTX10008 routers). Disables the interface associated with the ASIC that raised the error. Disables all PFE interfaces, alarms and logs. On MX Series routers, an MPC can have multiple ASICs handled by a single PFE. Disabling the PFE in such cases, is not the optimal way to handle the error. |
| get-state |
The system starts collecting statistics counters and other data from the affected FPC. The data is written and saved to a file under /var on the routing engine. |
| offline | Disables the alarms, logs, and shuts down the affected FPC, allowing traffic to be re-routed through interfaces on other FPC in the device. |
| reset | The system takes the affected FPC offline and resets to online, enables the alarms and logs. |
| offline-pfe | Disables the alarms, logs, and shuts down the affected PFE. |
| reset-pfe | Powers-off the PFE, disables the alarms and logs, then, powers-on the PFE, enables the alarms and logs. |
| log | Log occurrences to the system log file. |
| trap |
The system raises traps for the FPC errors. |
Usage
The usage guidelines are as follows:
- The specified PFE is disabled automatically if
offline-pfeorreset-pfeis configured. For details, see Configuring FPC Error Levels and Actions.
Required Privilege Level
| interface |
To view this statement in the configuration. |
| interface-control |
To add this statement to the configuration. |
Release Information
Statement introduced for PTX Series routers in Junos OS Release 13.3.
Statement introduced for MX240, MX480, MX960 routers in Junos OS Release 14.2.