[Contents] [Prev] [Next] [Index] [Report an Error]

Disabling Distributed Periodic Packet Management on the Packet Forwarding Engine

Periodic packet management (PPM) runs on the Routing Engine and Packet Forwarding Engine by default. PPM is responsible for periodic transmission of packets on behalf of its various client processes, such as Bidirectional Forwarding Detection (BFD). PPM also receives packets on behalf of client processes. By default, PPM handles time-sensitive periodic processing and performs such processes as the gathering of statistics and the sending of process-specific packets. Distributing PPM to the Packet Forwarding Engine allows you to run such processes as BFD on the Packet Forwarding Engine.

You can disable PPM on the Packet Forwarding Engine only. To disable distributed PPM, include the ppm statement:




ppm {
no-delegate-processing;
}

Note: You cannot disable PPM on the Routing Engine.

For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.

Note: Distributed PPM is supported only on the M120, M320, MX-series, T-series, and TX Matrix routing platforms.

The following types of sessions are not supported by distributed PPM:

Protocols other than BFD
Multihop BFD session
BFD session over a label-switched path
Any protocol session that does not explicitly specify that the adjacency and periodic sends must be distributed

In addition, on the M120 routing platform, when Forwarding Engine Board (FEB) redundancy is configured and a FEB fails over, PPM sessions do not automatically switch over to the newly active FEB. For more information about FEB redundancy, see the JUNOS System Basics Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]