Syslog message: XQSS.*CPQW Freelist Manager run out of available fl pointers

Description

The "Freelist Manager run out of available fl pointers" message reports an internal software state issue in the EACHIP related to pointer management.

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 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] .

.

Symptoms

When a "Freelist Manager run out of available fl pointers" event occurs, a message similar to the following is reported:

Jul 25 15:52:05.568 router0: %PFE-3: fpc8 Cmerror Op Set: XQSS(0): XQ-SS[0]: CPQW Freelist Manager run out of avaliable fl pointers

Indications:

Traffic impact or permanent impact on traffic forwarding might be see if errors are seen repeatedly
Alarm will be raised

Solution

This is due to a transient software issue in the EACHIP. An internal reset resets the software state to correct this condition.

{DIDYOUKNOWSERVICENOWTOKEN.EN_US}

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

Collect the show command output.
{SYSLOGSERVICENOWTOKEN.EN_US}
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
Analyze the show command output.

In the 'show log messages', review the events that occurred at or just before the appearance of the "Freelist Manager run out of available fl pointers" message. Frequently these events help identify the cause.

No RMA is required
Collect debugging information using KB31922 - shell script collecting data if packet forwarding at Packet Forwarding Engine is compromised [juniper.net]
FPC restart during a maintenance window should clear this error
Contact your technical support representative if this issue is seen repeatedly.

This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag EACHIPTSG

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.

Modification History

2019-10-01: Article reviewed for accuracy; no changes required