- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Failed to allocate new Neighbor Table entry
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2015 08:11 AM
09-02-2015 08:11 AM
Failed to allocate new Neighbor Table entry
Our 5412zl with firmware K.15.14.0012 sometimes generates the following message:
IpAddrMgr: Failed to allocate new Neighbor Table entry, will LRU oldest host FIB entry (vrf:0 10.4.174.182/32)
What is the neighbor table and how can I query it?
What can cause this message to appear?
Please note that we use static routes exclusively. I am also somewhat perplexed by the IP address in the message since it is not valid for our network.
Thank you in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2015 08:02 AM
09-21-2015 08:02 AM
Re: Failed to allocate new Neighbor Table entry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2015 08:18 PM
09-21-2015 08:18 PM
Re: Failed to allocate new Neighbor Table entry
Hello. IP address manager also manages "local" route (ARP & IPv6 neighbor) entries on the system. You should only get that log message when you're trying to add an ARP entry and the table is full. When it's full it will try and removed the LRU (Least Recently Used) route in order to make room. That table is a shared resource with connected/VLAN routes, static routes, and protocol routes.
So either the table is really full or something else is wrong and the message is printed in error. How many ARP entries are on the system? There's no "show arp count" unfortunately so you might have to cut & paste into a text editor. Also, how many IP routes are in use (show ip route summary)?
As for the second post you should not have to clear the ARP table to get routing working. Perhaps the LRU mechanism isn't working or routes are not aging out as they should.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2015 01:28 PM
09-25-2015 01:28 PM
Re: Failed to allocate new Neighbor Table entry
Hello Michael,
The message has not reappeared since I reconfigured a printer usage monitoring software used by a collegue which scanned a couple of 16-bit subnets, generating over a hundred thousand broadcast/arp packets once a day, every day. Of course the great majority of those scanned adresses were non-existant. It seems that the ARP table can be overwhelmed with ARPs for non-existant IPs?!
To answer your original question:
I've been monitoring the only two tables I'm aware of. The forwarding table which holds MAC/Port averages 480 records and the ARP table which holds IP/MAC/Port averages 186 records. All IP entries for both tables are valid IPv4 addresses for our network, we do not use IPv6 yet. I have no idea how many records the ARP table can hold before it gets full.
The result of a show ip route command shows a total of 26 routes, 9 are of type connected and the rest are static.