Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: filter.pf0_1.alpha[0].protect

0

0

Article ID: KB32137 KB Last Updated: 12 Oct 2021Version: 3.0
Summary:

The "filter.pf0_1.alpha[0].protect" message reports for EACHIP or XLCHIP a transient memory hardware issue

This is a Troubleshooting Article for a PFE ASIC Syslog Event.
To view other documented syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.

.

Symptoms:

When a "filter.pf0_1.alpha[0].protect" event occurs, messages similar to the following is reported and separated for XLCHIP or EACHIP. The error messages, "Errors sync xtxn error" will always be reported along with one or more of the protect events.

XLCHIP:

Sep 22 07:30:10 router0 : %PFE-3: fpc2 XL[0:0]_PPE 16 Errors sync xtxn error

One of those messages below can reported in syslog
Sep 22 07:30:11 router0 : %PFE-3: fpc2 XL[0:0].filter.pf0_1.alpha[0].protect BFT MEM MASK at address 0x02000000 (mult 0x8)
Sep 22 07:30:11 router0 : %PFE-3: fpc2 XL[0:0].filter.pf0_1.alpha[0].protect KHT MEM HT3 BANK0 CELL0 at address 0x00001075 (mult 0x0)
Sep 22 07:30:11 router0 : %PFE-3: fpc2 XL[0:0].filter.pf0_1.alpha[0].protect NEXT PLT MEM at address 0x00000001 (mult 0x0)
Sep 22 07:30:11 router0 : %PFE-3: fpc2 XL[0:0].filter.pf0_1.alpha[0].protect PLT MEM err_addr NA (mult 0x0)

EACHIP:

Sep 22 07:30:12 router0 : %PFE-3: fpc2 EA[0:0]_PPE 16 Errors sync xtxn error

One of those messages below can reported in syslog​
Sep 22 07:30:13 router0 : %PFE-3: fpc2 EA[0:0].filter.pf0_1.alpha[0].protect BFT MEM MASK at address 0x02000000 (mult 0x8)
Sep 22 07:30:13 router0 : %PFE-3: fpc2 EA[0:0].filter.pf0_1.alpha[0].protect KHT MEM HT3 BANK0 CELL0 at address 0x00001075 (mult 0x0)
Sep 22 07:30:13 router0 : %PFE-3: fpc2 EA[0:0].filter.pf0_1.alpha[0].protect NEXT PLT MEM at address 0x00000001 (mult 0x0)
Sep 22 07:30:13 router0 : %PFE-3: fpc2 EA[0:0].filter.pf0_1.alpha[0].protect PLT MEM err_addr NA (mult 0x0)

Indications:

  • Service impact can be low or high depending on the traffic flow hitting the affecting firewall filter using fast-lookup-filter knob

 
Cause:

This is due to a transient hardware SRAM error on the filter block of XLCHIP or EACHIP

Solution:



Perform these steps to determine the cause and resolve the problem (if any).  Continue through each step until the problem is resolved.

  1. Collect the show command output.

    Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

    show log messages
    show log chassisd
    start shell network pfe <fpc#>
    show nvram
    show syslog messages
    exit

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "filter.pf0_1.alpha[0].protect" message. Frequently these events help identify the cause.

  • No RMA is required

  • If you deactivate this "fast-lookup-filter" feature under the filter stanza and the error message stops, you have uncovered the exposed filter index. After this, activate the fast-lookup-filter knob again to recover from this condition.

  • Contact your technical support representative for further guidance if the error did not stop after manual recovery attempt.

  • Junos OS software changes done within PR1266879 perform automatic recovery from such error conditions.

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag EACHIPTSG XLCHIPTSG

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.
 
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search