PreviousNext

Juniper Networks, Inc.

JunosE 15.1.0 Release Notes


Prevent Reporting of Corrupted User and Policy Accounting Statistics by Detecting Parity Error

This appendix describes the support to prevent reporting of corrupted user and policy accounting statistics to RADIUS or SRC server by detecting parity error.

If you have issued the fpga-stats-monitoring-enable command and parity error is detected by the FPGA with the help of parity error check mechanism, the E series router performs the following actions for both user and policy accounting statistics:

If you have issued the fpga-stats-monitoring-enable command and parity error is detected by the FPGA, the show ip interface and show ipv6 interface commands display an error message instead of the policy accounting statistics details for the policies whose statistics are corrupted.

Informational Note: The parity error check mechanism is supported only on ES2 4G LMs (with any IOA combination) and is applicable for both PPP and L2TP subscribers. The parity check mechanism restricts the available number of bits of a 64 bits packet/byte counter to 60 bits and 32 bits packet counter to 30 bits.

The JunosE software performs actions (such as subscriber termination) only during interim update or during logout of the subscriber but not during subscriber login.

If you have not enabled E series router to perform various actions (such as subscriber termination) by using the fpga-stats-monitoring-enable command, after the FPGA detects the parity error, the subscribers are not terminated. But, the router sends the older uncorrupted user and policy statistics to the RADIUS or SRC server in all subsequent interim records and also in final accounting record during subscriber log out. Also, the JunosE software displays an error message in the output of the show ppp interface command instead of the corrupted user accounting statistics details.

Informational Note: The configuration settings for this feature is preserved across unified ISSU, router reload, and line module re-insertion. Whereas the corrupted slot information is not retained after the unified ISSU, router reload, and line module re-insertion. However, the corrupted slot information is retained after line module reload.

The parity error check mechanism is triggered to check for parity error during the following events:


Copyright © 2014, Juniper Networks, Inc.
Report An Error
PreviousNext