NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300 v12.0.7.10 - EIGRP multicast is filtered
We have a stack of 2 x M4300-12X12F and 2 x M4300-28G switches with 4 ports configured as untagged members of an isolated layer 2 broadcast domain (no routing). EIGRP would not establish between two Cisco switches after upgrading from 12.0.7.9 to 12.0.7.10 until we globally disabled IGMP.
NB: Whilst IGMP was globally enabled it was not set to run on the ports or VLAN which are members of this isolated VLAN.
Ports 3/0/19 and 4/0/19 are two Cisco routers running EIGRP:
(M4300-12X12F) #show mac-addr-table vlan 21
Address Entries Currently in Use............... 203
MAC Address Interface Status
----------------- ----------------------- ------------
00:00:0C:07:AC:01 3/0/19 Learned
00:E0:20:11:0A:36 3/0/20 Learned
70:D3:79:97:B0:91 4/0/19 Learned
70:D3:79:EC:E1:91 3/0/19 Learned
NB: Multicast forwarding for OSPF continued to work, after upgrading from 12.0.7.9 to 12.0.7.10, only EIGRP was affected. We had also disabled bonjor ('no bonjour run', I believe this option was introduced in 12.0.7.9):
The following configuration command restored connectivity:
no set igmp
To make this crystal clear:
- All Multicast settings are set to their defaults (IGMP & MLD)
- Ports are access ports for VLAN 21 for which IGMP is not enabled by default (only enabled for VLAN 1 by default)
- There are zero members in VLAN 1 (we completely isolate unused ports)
- All interface IGMP settings are shown to be administratively disabled by default
- Bonjour had been disabled
- EIGRP multicast working on previous versions and also after upgrading to 12.0.7.9
- EIGRP multicast did not work after upgrading to 12.0.7.10 until we issued 'no set igmp' to globally disable IGMP
Hi bbs2web
Thank you for your post and sorry about your issue. We have reproduced it and I confirm the kind of regression with 12.0.7.10 that broke some of these packet handlings. We already started fixing it and next M4300 release, 12.0.7.12 should be ready by this Friday. The "no set igmp" command won't be necessary anymore with 12.0.7.12, as it was with 12.0.7.9. Thank you for spotting this.
Our technical support teams will be able to provide 12.0.7.12 to you early after it's internally available here, you can send me your details by PM if you want. Per our processes, the new firmware will be posted online shortly after.
Regards
2 Replies
Hi bbs2web
Thank you for your post and sorry about your issue. We have reproduced it and I confirm the kind of regression with 12.0.7.10 that broke some of these packet handlings. We already started fixing it and next M4300 release, 12.0.7.12 should be ready by this Friday. The "no set igmp" command won't be necessary anymore with 12.0.7.12, as it was with 12.0.7.9. Thank you for spotting this.
Our technical support teams will be able to provide 12.0.7.12 to you early after it's internally available here, you can send me your details by PM if you want. Per our processes, the new firmware will be posted online shortly after.
Regards
Many thanks for your prompt response, we've already received 12.0.7.12 and will be scheduling a maintenance event to apply and test the new firmware.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
