NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300-12X12F replacing M7100-24X - Wireless Access Points not working
Hi Everyone, I'm attempting to replace our ageing M7100-24X with a M4300-12X12F (XSM4324S) which I bought just over two weeks ago. I haven't contacted support yet as I'm hoping that perhaps someon...
Paul,
As you mentioned the data is flowing over that MiNT tunnel between AP and controller - that is making use of 24577/UDP (wally brain is awake again) - I guess trouble with discovery and management is more on that special ether-type 0x8783 for L2 than on UDP used for L3 (routed connections).
Some sniffing would easily proof if the switch does fail to deal with ether-type 0x8783. That's why I point on the Netgear switch engineering resp. fellow Laurent Masia. 8-)
Regards,
-Kurt
Thanks for you reply.
Yes, that makes sense and reading the document that you linked to confirms what you've said about the unusual way WING works with regards to AP discovery and control.
Based upon that (and I realise I'm putting you on the spot here); if you had to hazard a guess, would you say the M4300 is more likely to be "falling down" on passing the specific Layer 3 UDP port 24576 traffic or the Layer 2 ether-type 0x8783?
Or is that something only the Switch Engineering team would know?
Many thanks,
Paul
Paul,
As you mentioned the data is flowing over that MiNT tunnel between AP and controller - that is making use of 24577/UDP (wally brain is awake again) - I guess trouble with discovery and management is more on that special ether-type 0x8783 for L2 than on UDP used for L3 (routed connections).
Some sniffing would easily proof if the switch does fail to deal with ether-type 0x8783. That's why I point on the Netgear switch engineering resp. fellow Laurent Masia. 8-)
Regards,
-Kurt
Kurt,
Apologies for the delay in replying.
Further investigation; prompted by your suggestion, did indeed point to the Switch not correctly processing/deciphering the MiNT protocol ether-type 0x8783 at Level 2. I had to change our entire AP estate over to UDP Level 3 adoption even though we are a single non-routed site (albeit quite a large one). This had the desired effect and all APs are now discovered & adopted correctly through the XSM4324S.
I still consider this as a fault/issue (which I've reiterated to Netgear Support), as no other Netgear (or HP/Dell/D-Link etc) switches we've ever had or used over the past 15 years have behaved in this way and I don't think it's unreasonable to expect a £2300/US $2800/EU 2700 switch to have consistency of features & performance with previous models in the Enterprise range.
Despite this, and thanks to your advice; I've managed to successfully circumvent this issue. Your help and advice is very much appreciated. Thanks also to everyone else who took the time to reply/comment.
All I need to do now is contact Netgear Support about the faulty M7100-24X that forced me to buy this XSM4324S in the first place. No doubt they'll expect me to have a Purchase order/Invoice from 2012 for it!!
Kind Regards,
Paul
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
