NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300 CARP packet support
Have a M4300 24x24; just tried upgrading to Firmware .10, but it appears both .9 and .10 have bugs where the 'ports' menu isn't functioning (404 missing).
That said, I am utilizing 2 copper 10gbe cables from a NAS that supports HA. The CARP packet isn't apparently being sent appropriately or handled, as even a simple ICMP ping from a windows host to that machine is unreachable about 30% of the time.
Everything is on the same subnet.
the HA units are 0.10, 0.11, and 0.12 where .12 is the HA IP address. .10 and .11 are pining fine now, but .12 is completely forsaken.
Help greatly appreciate or we're RMA'ing the switch to go back to Cisco. This should just 'work' but the vendor is insisting it's a switch problem and I've already burned a ton of $$ diagnosing it.
3 Replies
Sorry about this issue. Bear with me, I'm only the product line manager for M4300 series, not Tech Support. But the symptoms you are describing are clear to me.
1. There is no bug in 12.0.7.9 or .10 in Switching \ Ports in the GUI that we know of - it would mean the CPU is overloaded with some unregistered traffic bombarding it and the HTML can't display properly
2. In general, Tech Support teams would require the Tech-Support file for logs investigation and troubleshooting. When the problem is happening, you would be asked to log onto the CLI, do Enable and enter the command show tech-support. This would create a file in the flash. Then you would use the GUI (Maintenance \ Export \ HTTP File Export and select Tech Support in the dropdown list) to get the file and send it to us.
3. But even without it, I think I know what is going on. We don't support this Common Address Redundancy Protocol (CARP) that allows multiple hosts to share the same IP address. All the features supported in M4300 series are described in M4300 datasheet (PDF file or MS Excel file). High Availability sections describe NSF stacking and other distributed link aggregation techniques - but if you search for CARP you won't find it. This traffic seems to literally kill the CPU. Not sure which Cisco switch line you are mentioning, but I know that with Nexus series, it can be supported with some configuration.
Please send the Tech Support file for a more complete analysis (you can use Private Message with me for instance). Again, sorry for this issue. We don't support CARP "group of redundancy" switching.
Regards,
That is a very painful answer to learn. After searching and trying to contact pre-sales support, finding out now that CARP isn't supported (as it is really just multicast and needs to be re-broadcast) when VRRP is supported ... ouch.
That said, here is a screenshot I forgot I saved. The firmware loaded is either .9 or .10. When you attempt to navigate via the switching, then ports, menus the page returns 404. I did not roll back any further. Right clicking and manually entering th port menu may have been working but I was trying to diagnose other issues.
-You can also see the .13 HA interface failing to respond to a ping, whereas the others were still working.
Thank you, the team is willing to diagnose it with more details. Our Tech Support team sent you a PM yesterday asking for the tech-support file, too. Please send the tech-support file either way (to me, or to the Tech Support team). With it, we will be able to exactly find out what's wrong.
In looking at your management IP address (192.168.0.0 scheme), I am assuming you are using the OOB service port. If you are managing the switch from the in-band, then you possibly have a conflict with the OOB service port IP scheme. The OOB service port IP scheme should be changed from 192.168.0.0 to something else, like 192.168.100.0 before you can use 192.168.0.0 scheme on the Management VLAN through the in-band.
Thank you,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
