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

Possible cause of ENOMEM / ENOENT errors seen under the command "show krt queue"

0

0

Article ID: KB15192 KB Last Updated: 25 Mar 2010Version: 1.0
Summary:
This KB discusses one possible cause of ENOMEM / ENOENT errors.
Symptoms:
Topology:
                        R1  -------------   R2

R1 and R2 are directly connected, running MP-eBGP and exchanging labeled unicast routes.

Symptoms:
On router R1, the krt queue was stuck with 'MPLS add queue' showing changes that could not be added to the forwarding table. It was also showing ENOMEM errors as seen below:

user@R1> show krt queue
Routing table add queue: 0 queued

Interface add/delete/change queue: 0 queued

Indirect next hop add/change: 0 queued

MPLS add queue: 148 queued

                ADD gf 3 inst id 0 711449 /52 nexthop

                <prefix>, ge-1/2/0.0

                   Swap 308543

                                                 (8)
                error 'ENOMEM -- Cannot allocate memory'
                ADD gf 3 inst id 0 711452 /52 nexthop

                <prefix>, ge-1/2/0.0

                Swap 304352

                (8)

Solution:
R2 had 'family mpls' enabled on the interface towards R1.  However, R1 was missing 'family mpls' on the interface towards the router R2.  The absence of this command was creating a problem because the routes being received on R1 were labeled while the next-hop associated with it was not enabled for MPLS.  This was not allowing labeled routes to be associated with a next-hop since the interface did not have MPLS enabled and there was a mismatch with address families of NLRI received and the next hop associated with them.

This scenario could also show "ENOENT -- Item not found" errors along with a stuck krt queue.

Essentially, configuration mistakes are more often the cause for these messages. Check the configuration thoroughly if you do encounter these errors. If these errors are being seen even when everything in the configuration looks fine, please contact JTAC.

Related Links

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