Support Support Downloads Knowledge Base Case Manager My Juniper 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: 'FPCx QX-chip(1): Q index(18800) is not allocated'

0

0

Article ID: KB36043 KB Last Updated: 08 Jul 2020Version: 1.0
Summary:
This document explains the meaning of the Syslog Message 'FPCx QX-chip(x): Q index(xxxxxx) is not allocated' and explains the affect of the error on the device.
Symptoms:

Syslog Messages:

Feb  9 05:30:16  fpc0 QX-chip(1): Q index(16120) is not allocated
Mar 28 06:28:07  fpc0 QX-chip(1): Q index(18800) is not allocated
Mar 28 06:28:27  fpc0 QX-chip(1): Q index(18800) is not allocated
Mar 28 06:28:27  re1 re0 fpc0 QX-chip(1): Q index(18800) is not allocated
Mar 28 06:28:50  fpc0 QX-chip(1): Q index(18800) is not allocated
Mar 28 06:29:54  fpc0 QX-chip(1): Q index(18800) is not allocated
Mar 28 06:30:14  fpc0 QX-chip(1): Q index(18800) is not allocated
Solution:

Check Active Alarms:

user@host> show chassis alarms
Aug 17 23:23:53

No alarms currently active

 There won't be any alarm generated due to this error message. If you any QX chip alarm matching the timestamp of Syslog, please move to the last step.

Check subscribers:

[MASTER]
user@host> show subscribers summary
Aug 17 23:23:58
 
Subscribers by State
   Active: 18579
   Total: 18579
 
Subscribers by Client Type
   DHCP: 9212
   VLAN: 9212
   Static: 155
   Total: 18579

Verify if the above outputs display correct subscribers. If there is any discrepancy, please move to the last step.

Check DHCP bindings output:

user@host> show dhcp server binding summary
Aug 17 23:24:55
 
5884 clients, (0 init, 5884 bound, 0 selecting, 0 requesting, 0 renewing, 0 releasing)

Verify the above output, if there is any discrepancy that wasn't expected, then move to the last step.

Check the FPC types:

user@host> show chassis hardware | match FPC 
Aug 17 23:29:35
FPC 0            REV 45   750-031090   x           MPC Type 2 3D EQ
FPC 1            REV 45   750-031090   x           MPC Type 2 3D EQ
FPC 7            REV 41   750-028467   x           MPC 3D 16x 10GE
FPC 8            REV 41   750-028467   x           MPC 3D 16x 10GE
FPC 10           REV 25   750-024064   x           MS-DPC
FPC 11           REV 25   750-024064   x           MS-DPC

This output will be required in case you decide to go forward with the last step.

Detailed Logs:

[MASTER]
Aug 17 01:52:07  fpc0 vbf_ifl_bind_change_var_walker:369 ifl .demux.32641 (1073774465): FILTER (28) Bind change notify ran for 276701162891 us
Aug 17 21:55:27  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 21:55:48  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 21:56:24  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 21:56:42  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 21:59:36  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:00:02  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:00:31  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:00:51  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:00:31  re1 re0 fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:01:01  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:01:57  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:02:12  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:03:08  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:03:19  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:03:30  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:03:41  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:05:30  fpc0 QX-chip(0): Q index(7256) is not allocated
Aug 17 22:05:49  fpc0 QX-chip(0): Q index(7256) is not allocated

The above log messages indicate that QX-Chip is trying to query or locate an index (IFL index) which was not present. These log messages are non-impacting and do not affect any services or subscribers so you can safely ignore them. In case there is any impact while these messages are being seen in logs, please move to the last step.

JTAC Support (Last Step):

In an ideal scenario, this error message is non-impacting. But in case it is coupled with additional problems along with the targeted log, there could be issues with services running on subscribers. An example error would be the number of active subscribers is seen to be less than the number of total subscribers in 'show subscriber summary' output.  This may not necessarily be due to the error message explained in this document. In that case, please collect the above outputs and contact JTAC Support for detailed analysis.

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