NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Firmware Update
23 TopicsM4300 Switch Stack Upgrade Path
Hi, I have inherited a M4300 stack cluster of 3 24 port switches, which are having issues where one of the stack seems to crash/latchup & is unresponsive They are running old software 12.9.0.3 Now whilst i would love to upgrade the firmware to latest 12.0.19.21 im finding conflicting information, if we can go from 12.9.0.3 -> 12.0.19.21 or if we need to stagger with something like this: [v12.0.9.3] ──> [v12.0.11.16] ──> [v12.0.17.6] ──> [v12.0.19.21 (Latest)] Reasons i see for stagger is 17.6X breaks admin passwords & possible 15.8+ fixes that looking for clarification from support or other users, the correct upgrade path. currently have no access to usb console, & fully remote from these devices..10Views0likes0CommentsMemory leak M4300 12.0.19.21
Hello We upgraded to 12.0.19.21 in hope that if fixes random crashes of our M4300 stacks, we now observer memory leak in SCRIPT process. We took output of "show process memory" in hourly intervals on friday and extra output on Monday morning Time SCRIPT CurrentAllocated Δ from baseline 11:15 4,527,712 baseline 12:15 4,539,920 +12,208 13:15 4,553,808 +26,096 14:30 4,571,840 +44,128 15:20 4,582,144 +54,432 3 days later 10:15 5,480,944 +953,232 There is slow leak and no memory is Freed. Is there a way to restart/disable this single process to stop switches from crashing eventually? Regards151Views0likes1CommentM4300 memory leak
Upgraded to 12.0.19.19 (from 12.0.19.4) yesterday morning. Now the ram usage increases until the switch crashes and reboots :/ Any advice here? Seen the same behaviour on M4300-28G-PoE+ and M4300-8X8F and a M4300-52G-PoE+ . Haven't upgraded any others for now.278Views0likes2CommentsNetgear ProSafe GS752TP Poe Switch
Hallo Ich habe oben genannten Switch bei dem garnichts mehr geht , er fährt hoch macht den LED Test und danach nichts mehr . Die Ports werden nicht mehr erkannt , man kann keinen Reset durchführen und auf die Oberfläche kommt man auch nicht mehr. Was kann ich da noch machen? MfG MikePOST Issues GSM4248UX
Hi, the power on start of self teset on my GSM4248UX is failing. I power on the switch and it starts with the test. All of the ports in the back of the unit light up for a few seconds. The power LED blinks a number of times then stays on red solid light. The switch is not accessible via the OBB or any of the ports. The switch was working fine for a day or tow, but then we updated the software to the latest firmware. V13.0.5.24 Then we started having this issue. I have tried the paper clip reset multiple times, but there are no indications that this is working at all. Any comments will be greatly appreciated.357Views0likes5CommentsM4300 only boots when TFTPD connected
Hello, I posted a previous post and got some great help but it looks like there is a part 2 and I jumped the gun on thinking I had it all figured out. I had to reset a switch to the beginning and followed this article after getting some help here. https://community.netgear.com/discussions/business-managed-switches/m4300-52g-poe-stuck-in-u-boot---error-cant-get-kernel-image/2179070 The unit boots and I can use the web interface and I can make changes and save it. However if I reboot and don't have the TFPD server running it just goes to the in a loop until I interrupt M4300> prompt and it is unusable. The first part is the boot after TPFP - the second part is when I disconnect the TFTP cable. My guess is I have to tell it to stop trying to boot from the TFTP or fix an image or something. I reboot after it loads properly but turn off the TFTP server but it looks like it isn't using the onboard config. Reboot without TFTP server437Views0likes1CommentM4300-24X24F ProSAFE 24-port 10GBASE-T and 24-port 10G SFP+ Firmware Upgrade
Dear Team, I have purchase new Switch and found fimrware version is very old (12.0.17.8) and current firmware version on website (12.0.19.12). Can i directly update latest firmware or need to update step by step. Thanks & Regards, Anil Mahadev Misal212Views0likes1CommentM4300 - OpenSSH < 9.3p2 Vulnerability
Hello all, Currently using Firmware version 12.0.19.7 on a fleet of M4300 switches. Against a independent vulnerability scan of these, it has shown up they are showing having SSH-2.0-OpenSSH_8.0 installed and it would require at least 9.3p2 / 9.4 installed to resolve this. Due to this, I have had to disable SSH for the time being which means I no longer have access into the command line easily. Looking at future firmware releases, there is no mention of this being fixed and as such I cannot update my fleet unless I know this issue will be resolved. Does anyone at Netgear/ Community member know about this problem and its resolution path?189Views0likes1CommentM5300-52g slow start up when using v11 firmware
Hi During a deployment of a stack to replace an existing one, I ran into a problem. Instead of lift and shift of both units, the 52 port switch running v11 firmware (pre configured) was plugged into a live older switch (running v10). This then sent both switches into a tailspin and broke the configuration of both old and new hardware. The old stack has been restored, however I still need to replace with the 5300 stack. The new M5300 52g switch is showing some VERY strange behaviour even after factory reset and multiple firmware updates and factory resets. Initially after the incident, I had to force a reset using the CLI and to perform a hardware reset from there. Incidentally, all the ports apart from the USB, on the switch just weren't working or detecting any cables. Once I eventually got into the GUI, I could see that it was showing both elements of the v10 AND v11 firmware together. Having followed advice from within this forum, I have loaded v.10.0.0.53 to the switch. This then boots up fine and the ports on the front become live within 90 seconds. However, if I upgrade the same switch to v11.0.0.40 and reboot, It then takes 7 minutes before I can ping it and get access to the GUI. I'm simply not willing to rebuild and deploy this switch until I get this behaving as it was prior to the incident. Please note. I'm pinging the default private addressing 169.254.100.100 and I'm not worried about the config as it's going to need a fresh build. Old kit GSM7228PS and a GSM7352Sv2. Running v10.0.0.53 New kit M5300 52g and M5300-28g-PoE+. Desired firmware V11.0.0.40 I feel I have exhausted all my options and would welcome any other suggestions. Thanks in advance.115Views0likes0Comments