Wired Intelligent Edge

Hello!

I have 00901 IpAddrMgr warning msg. on logs.

IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

On post http://h30499.www3.hp.com/t5/ProCurve-ProVision-Based/5406zl-IpAddrMgr-Failed-to-allocate-new-Arp-Cache-Mac-Hash/td-p/2306561#.VN33OKLWiig

I see 00901 IpAddrMgr  but with different description:

00901 IpAddrMgr: Failed to allocate new Arp Cache Mac Hash Pointer entry

Can anyone tell me what this means?

What does this warning?

Hi, we just had the same on our 8212zl core...

W 06/25/15 11:39:37 00901 IpAddrMgr: AM2: Failed to allocate new L2 MAC tracker,
L3 FIB may ignore L2 MAC moves FIB entry

Aug 7 2013 16:48:38
K.15.12.0010

We upgraded the network to K.15.17.0008.

00901 IpAddrMgr: AM2: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Not sure if I ever saw this before.

Same for me.

40 devices 5400/8200 models

All on firmware K15.16.0005

Only 1 device has this message in its eventlog.

exactly once every day, but every day a few minutes later.

Thu Aug 06 15:39:51 CEST 2015

W 08/06/15 13:39:46 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Wed Aug 05 15:35:46 CEST 2015

W 08/05/15 13:35:38 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Tue Aug 04 15:34:50 CEST 2015

W 08/04/15 13:34:52 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Mon Aug 03 15:31:43 CEST 2015

W 08/03/15 13:31:34 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sun Aug 02 15:22:27 CEST 2015

W 08/02/15 13:22:28 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sat Aug 01 14:50:50 CEST 2015

W 08/01/15 12:50:52 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Fri Jul 31 14:40:35 CEST 2015

W 07/31/15 12:40:27 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Thu Jul 30 14:34:24 CEST 2015

W 07/30/15 12:34:14 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Wed Jul 29 14:34:16 CEST 2015

W 07/29/15 12:34:07 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Tue Jul 28 14:33:23 CEST 2015

W 07/28/15 12:33:11 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Mon Jul 27 14:31:15 CEST 2015

W 07/27/15 12:31:11 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sun Jul 26 14:25:02 CEST 2015

W 07/26/15 12:25:02 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sat Jul 25 13:32:00 CEST 2015

W 07/25/15 11:31:49 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Fri Jul 24 12:48:46 CEST 2015

W 07/24/15 10:48:50 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Thu Jul 23 12:47:27 CEST 2015

W 07/23/15 10:47:30 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Wed Jul 22 12:46:48 CEST 2015

W 07/22/15 10:46:41 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Tue Jul 21 12:45:03 CEST 2015

W 07/21/15 10:45:06 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Mon Jul 20 12:42:19 CEST 2015

W 07/20/15 10:42:12 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sun Jul 19 12:39:02 CEST 2015

W 07/19/15 10:39:04 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Sat Jul 18 12:39:00 CEST 2015

W 07/18/15 10:39:02 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Fri Jul 17 10:29:35 CEST 2015

W 07/17/15 08:29:27 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Thu Jul 16 10:24:53 CEST 2015

W 07/16/15 08:24:55 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

Wed Jul 15 10:22:41 CEST 2015

W 07/15/15 08:22:43 00901 IpAddrMgr: Failed to allocate new L2 MAC tracker, L3 FIB may ignore L2 MAC moves FIB entry

All devices will reboot coming weekend for a firmware upgrade to K15.17.0007

When L3 (IpAddrMgr) adds a route for local host it asks L2 to track the mac address for it in case of a move.  When the L2 mactracker add fails you get this cryptic log message.

Do you have lots of clients moves in the network?  A transient loop perhaps?

Or something else is going on...

For me the daily repeating message is now gone.

updated to newer firmware and rebooted, i expect the reboot "fixed" this.

This is normaly one of the busiest buildings with alot of Wireless clients roaming trough the building.

Last weeks where summer holidays so no load at all.

Message still persisted daily.

I will check the device logs to see if the message returns after a few busy days.