topic RE: error ipv4 multicast entry in ExtremeSwitching (Other)

error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 02:52:00 GMT

I open a GTAC case, I just put in this x440 stack (today first day of production) and I got the ipv4 multicast entry error any suggestions?

RE: error ipv4 multicast entry

Bill_Stritzinge — Tue, 29 Dec 2015 03:01:00 GMT

The following GTAC knowledge article should fix your issues:

https://gtacknowledge.extremenetworks.com/articles/How_To/Multicast-Entry-not-Added-Hardware-Table-F...

Bill

Admin edit: Fixed link

RE: error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 03:01:00 GMT

Thanks for your response Bill but the article is not available 😞

The article referenced is currently unavailable

RE: error ipv4 multicast entry

davidj_cogliane — Tue, 29 Dec 2015 03:01:00 GMT

440s have very small tables and you are probably exceeding the limit. Can you post a snip of the log messages?

RE: error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 03:01:00 GMT

12/28/2015 11:04:36.01 Slot-1: IPv4 multicast entry not added. Hardware Group Table full.
12/28/2015 10:04:15.69 Slot-1: IPv4 multicast entry
not added. Hardware Group Table full.

RE: error ipv4 multicast entry

Yusuf_Kabbara — Tue, 29 Dec 2015 03:01:00 GMT

How does ... command change the amount of multicast entries? I didn't understand the command well!

RE: error ipv4 multicast entry

Bill_Stritzinge — Tue, 29 Dec 2015 03:09:00 GMT

Sorry... Here is the full article:

Procedure:

Option conserves usage of the hardware Layer 3 multicast forwarding table:

configure igmp snooping filters per-vlan

(to set it back to default set it to per-port)

After changing the IGMP snooping filters from per-port (default) to per-vlan you can disable IGMP snooping on VLAN's where IGMP snooping is not required:

disable igmp snooping vlan

Stores multicast entries in the format (* AnySourceIP, GroupIP, VlanId), which is also referred to as (*, G):

configure igmp snooping forwarding-mode group-vlan

(to set it back to default configure it to source-group-vlan)

Routes with longer network masks might not be necessary if they are a subset of other routes with shorter network masks using the same gateway(s). When IP route compression is enabled, these unnecessary routes are not provided to the Forwarding information Base (FIB).
enable iproute compression

Additional notes:

Beginning in EXOS 15.4, the command configure igmp snooping forwarding-mode group-vlan was replaced with configure forwarding ipmc lookup-key group-vlan.

Hope it helps!

Bill

RE: error ipv4 multicast entry

davidj_cogliane — Tue, 29 Dec 2015 03:15:00 GMT

This does work very well. I have not seen the error messages on any of our stacks after making the changes Bill suggests.

RE: error ipv4 multicast entry

Bill_Stritzinge — Tue, 29 Dec 2015 03:16:00 GMT

Either of the last commands here will fix your issue:

If pre 15.4 - "configure igmp snooping forwarding-mode group-vlan" and if 15.4 or later "configure forwarding ipmc lookup-key group-vlan"

Bill

RE: error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 03:16:00 GMT

Thanks for your quick response, I enter the second one, (ver 15.7.1.4) and I'll monitor to see how it responds

Thanks

RE: error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 03:16:00 GMT

Bill, so far, after applying the instruction, no log error since yesterday 12:04pm, thanks

RE: error ipv4 multicast entry

Stephane_Grosj1 — Tue, 29 Dec 2015 04:19:00 GMT

To add a bit to it: EXOS stores, by default, multicast entries in HW as (S,G,V) in L3 Table resources, even if operating in L2. Your issue was typical of the x440 L3 scale, which is limited. What Bill gave you was a way to better optimize the L3 Multicast resources. IF you don't need L3, but only L2, and IF you still encounter your issue in the future, you may want to try switching to L2 learning for multicast. Scale will be way higher.

configure forwarding ipmc lookup-key mac-vlan

other options are: group-vlan (what Bill gave you), source-group-vlan (default) and mixed-mode

mixed-mode may be interesting if you have a mix of L3 and L2.

RE: error ipv4 multicast entry

Kar_Del_Moral — Tue, 29 Dec 2015 04:19:00 GMT

Thanks for the information

RE: error ipv4 multicast entry

Paul_Poyant — Wed, 30 Dec 2015 02:15:00 GMT

A consolidated KB article is available at
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-prevent-IPv4-multicast-entry-not-added-Hardware-L3-table-full-log-messages.

RE: error ipv4 multicast entry

davidj_cogliane — Thu, 31 Dec 2015 00:43:00 GMT

Sort of related to this,

I am working on new configs for a network refresh for one of our customers.
Code version: 15.7.2.9
Our current default multicast config for mixed networks (440/460) is:

enable igmp snooping forward-mcrouter-only vr VR-Default
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan

The customer has distributed routing from the the building MDF closets I started working on some of the IDFs and the above config worked fine.

When I got to the MDF I found the current gear has:

enable ipmcforwarding vlan "ADDAMSD100"
enable ipmcforwarding vlan "RO_AES_HS_link"
enable ipmcforwarding vlan "RO_AES_SVR"
enable ipmcforwarding vlan "RO_AES_USR"

This does not work with in conjunction with our current default config. So I am trying to determine how to proceed. The MDF stacks are all 460s so they should be fine with the modifications to the table entries.
My concern is will things work with modified entries in the IDF and default entries in the MDF? Or should we use the default multicast table entry method everywhere and just deal with the error messages in the IDFs?

Thanks,

RE: error ipv4 multicast entry

Kar_Del_Moral — Wed, 06 Jan 2016 06:46:00 GMT

The error appear again,

Slot-1 MDF-U-st.1 # sh log sev war
01/05/2016 14:14:07.07 Slot-1: IPv4 multicast entry not added. Hardware Group Table full.
01/05/2016 08:17:16.70 Slot-1: Previous message repeated 3 additional times in the last 9511 second(s)

maybe last resort will be to put only L2, will this impact current traffic? do I need a maintenance window?

RE: error ipv4 multicast entry

Stephane_Grosj1 — Wed, 06 Jan 2016 06:46:00 GMT

Hi,

do you have any requirement or protocol needing L3 IPMC? This include PIM, MVR IGMPv3 and Private VLAN. If so, you'll need to turn on mixed-mode instead of mac-vlan as they cannot work in L2 mode. You should have a message saying that from the CLI.

The User Guide is a helpful resource for the details.

RE: error ipv4 multicast entry

Bill_Stritzinge — Wed, 06 Jan 2016 08:22:00 GMT

Did the switch reboot and possibly without the configuration being saved? Assuming that is the case I would to refer to Stephane's post above and put it into L2 only, most likely based on your config as you have shared it most likely wont cause you any issue.
That command would be: "configure forwarding ipmc lookup-key mac-vlan"

RE: error ipv4 multicast entry

Bill_Stritzinge — Wed, 06 Jan 2016 08:22:00 GMT

You can check to make sure that the configuration is there by doing the command, "show config mcmgr" - It should show you the configuration that you are using assuming it is there.

RE: error ipv4 multicast entry

Kar_Del_Moral — Wed, 06 Jan 2016 08:22:00 GMT

Thanks.. No reboot I check

Slot-1 MDF-U-st.2 # sh config "mcmgr"
#
# Module mcmgr configuration.
#
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan