NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300 VLAN routing interface gets down with stack master
My simplified lab setup is two M4300-12X12F, stacked up. All ports, except stack ones, are set as follow: interface x/x/x
switchport mode trunk
vlan acceptframe vlanonly
vlan ingressfilter
exit
T...
I've have some issues on a mixed stack of 1x M4300-12X12F (same as yours) and a M4300-52G-PoE+ with this firmware version where initiating a failover between master and standby master (configure; stack; initiate failover) would render a stack management inaccessible. Although not exactly the same thing, a manual failover or a power off event on the master leads to the same situation where the standby master will take over the stack master role.
Could you check that when you initiate a failover like me that the new master has some ports in DETACH state when you issue the 'show port status all' command? If you lose access over SSH, try the serial console, it remained working in my situation.
I'm currently working with Netgear on an issue with this specific version and testing a beta release after they have done some preliminary testing internally. I don't do any inter-VLAN routing on the M4300's so my use case is not entirely compareable to yours, additionnaly this only happened on that mixed stack but not on another stack with 2 M4300-52G-PoE+'s.
If you see the same behaviour load 12.0.7.10 into the other firmware bank and start it. In my case failover was still rather slow and causing some packet loss, but overall working. If things are similar I could send you my case number in private so you could point the Netgear support to potentially give you access to that release. (I am not permitted to do so by the beta agreement which I had to accept for this support case)
Good to hear WojtekC - I couldn't have helped if I hadn't run into the very same issue 2 weeks ago.
For other readers: It seems to be a bug applying only in certain specific combinations of M4300 models stacked together and running 12.0.7.15, but not all are affected by this bug. If you are affected by this, downgrading to 12.0.7.10 seems to be a viable workaround as of writing.
I can say that I have been positively surprised by Netgear's L2 and L3 support while working with them on this issue and can tell that they have done a good job at analyzing and pinpointing and reproducing this particular issue. Based on that it looks like a matter of time when a next firmware release should be published, that includes a proper fix.
I have different point of view about company. It seems that NETGEAR software is released without testing even basic functionality, and that not looks good. I wasted much time for this problem, and now afraid to use any more complex functionality.
I'll filled support ticket for that issue, so maybe i'll get better experience.
I guess it depends on what you compare it against. :-) Considering that Netgear gives lifetime warranty and chat support for nothing more than the initial price of the device: They were able to pinpoint the issue within 1.5 days and follow up with a workaround after 3 in my case.
To many vendors first want an expensive support contract before even talking to you or even lock access to software updates based on contracts for each and every device, topped by feature licenses to unlock when you require specific features. (There are worse companies, don't get me started on that topic) ;-)It is also a pretty specific issue and as I wrote: I have another stack where this does not happen at all. Based on that, it looks like this actually has slipped through in testing since there are a couple of models in the M4300 line but not all combinations might have been tested before shipping this firmware.
Hi WojtekC
I am Laurent Masia, the Product Line Manager for M4300 series and while I want to thank you for reporting your issue, it is quite disappoiting to hear you talking about NETGEAR in these terms. I am inviting you to do some research on this Community forum about M4300 switches and I hope you will notice that the entire team, including PLM, Engineering and Tech Support do care about the quality of your products, our software and our service. Could you let everyone know the details about your Company, your Role in your organization, the activities of your Company? This way, you could let a chance to the other users to understand you better.
Back to your point, please be assured that any new maintenance release for M4300 series is thoroughly developed. Before any public release, we have deep Q.A. testing including regression testing to ensure none of the previous features got impacted by the changes made in our software. At NETGEAR, we strive to deliver best-in-class networking service with the M4300 series.
Now, interoperability issues on specific use cases in customers' environments are something, we, Networking Vendors, are working on all the time. If you read the release notes for any of our maintenance releases, we are addressing interoperability issues, this is how our products and our solutions get always better. In your case, I can confirm this is not a known bug at this stage. By logging a ticket at our Tech-Support organization, you will be asked to export a Tech-Support file out of your stack when the problem is visible (Maintenance/Export/HTTP File Export/ tech-support in the dropdown menu list) and send it to us. The file is containing all the logs, debugging commands and other parameters that will let us understand the root cause. This way, we will either modify your configuration if this is a misconfiguration, or work on a rapid Engineering build to fix your issue. If this Engineering build is fixing your issue, we will integrate these changes into our next maintenance release project, and again we will go through a complete Q.A. cycle to run regression tests before ultimately publishing a new maintenance release.
Logging many posts in a topic like yours on the Community isn't the fatest way for receiving Tech-Support from our L3 Tech-Support organization. This forum is a Community forum. As a M4300 customer, you are entitled to lifetime technical support. When such obvious issue, after posting once on the Community, it is wise to open a ticket at NETGEAR technical support.
Please be sure that we shall fix your issue asap. Thank you for your cooperation and thank you for using the NETGEAR M4300 switch series.
Regards,
I want to apologize all, who might be disappointed or even offended by my previous post.
I've done some research before buying these products (M4300-12X12F, and couple M4300-28G, M4300-28GPoE+). After research i came to conclusion that these are great products, high class at good price (best i can find), and greatest possible warranty. That's why I was very disappointed when found some errors in software, and write last post maybe too quickly.
I already filled support ticket and got quick answer (although basically the same as in forum). Hope that new firmware will be released soon (not too soon ;).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
