NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Firmware Update
8 TopicsM4300-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 Misal10Views0likes1CommentM4300 - 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?46Views0likes1CommentM5300-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.21Views0likes0CommentsM4300-12X12F unstable on 12.0.19.x
We have approximately 15 Netgear M4300 stacks where we hit a problem upgrading firmware. We've subsequently paused updating the others. The following stacks upgraded without problem and remain stable afterwards: 2 x M4300-24X24F + 2 x M4300-28G 2 x M4300-8X8F 2 x M4300-24X We however had a problem with the following stack, where the 2nd unit was rebooting regularly (between 1-5 hours of update between restarts): 2 x M4300-12X12F Unit 1 has remained stable but unit 2 reports the following issue: May 23 02:54:40 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25321 %% CPLD(0x30): Unable to read @reg(0x50). May 23 02:54:40 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25322 %% CPLD(0x30): Unable to read @reg(0x02). May 23 02:54:40 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1322) 25323 %% CPLD(0x30): Unable to write data(0xa5)@reg(0x02). May 23 02:54:40 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25324 %% CPLD(0x30): Unable to read @reg(0x10). May 23 02:54:41 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25325 %% CPLD(0x30): Unable to read @reg(0x11). May 23 02:54:41 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25326 %% CPLD(0x30): Unable to read @reg(0x19). May 23 02:54:41 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25327 %% CPLD(0x30): Unable to read @reg(0x50). May 23 02:54:41 zanjnb01-swd1l5-02-1 BOXSERV[boxs Req]: boxs.c(1452) 25328 %% Unit 2 power supply 1 FAILURE event (4) occurred. May 23 02:54:41 zanjnb01-swd1l5-02-1 TRAPMGR[boxs Req]: traputil.c(795) 25329 %% Power supply state change alarm: Power Supply Unit: 2 ID: 1 Event: 4 - Failure May 23 02:54:41 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_utils.c(1294) 25330 %% CPLD(0x30): Unable to read @reg(0x1a). May 23 02:54:41 zanjnb01-swd1l5-02-2 BSP[unitMgrTask]: cpu_boxs.c(1259) 25331 %% FAN Module interrupt received on the unit 2 fan 1 fail We interpreted the above as a bad PSU in unit 2 and replaced the PSU with a spare, replaced the power cable and move it to another socket on a different PDU after it still restarted. The above message about the PSU having failed is however most probably a red herring, in that the FAN is also reported as having failed. My gut tells me that the stack master looses sync with the unit which sporadically reboots and then reports the various components as having failed. The configuration on this problematic switch stack is fairly simple, in that it defines a variety of LAGs balanced between the two stack members, defines a couple of layer 2 VLANs that are distributed over LAGs and has two interfaces configured to do VLAN stacking (double VLAN). The other stacks all have a similar configuration. We are not doing layer 3 on these switch stacks, except for management of the devices themselves. Is this a known issue?50Views0likes3CommentsCannot access admin page
Updated several RNAS 312's with firmware 6.9.3. -Also updated a 212 with 6.9.3. After the update, RAIDar application 6.3.0 can no longer access the 312's on the internal network through login. Can access the shares via "browse" and thru ReadyCloud....but not thru local or Cloud admin page login. Did not affect the RNAS 212. Ideas? Suggestions on restoring local login with RAIDar app?7.2KViews0likes20CommentsReadyNAS 314 - Firmware update from version 6.1.6 to 6.6.1 Issues
Will there be an issue when we update the firmware of the ReadyNAS from version 6.1.6 to 6.6.1? We have encountered an issue with another Netgear ReadyNAS losing the volume when we update to the latest firmware. We had logged a case with Netgear support to recover the data for that issue. We are planning to update the firmware on the NAS to see if it will fix the folder permission issue we are having. Currently we have a shared folder (UserProfile) that we cannot see the contents inside via the webui. We are able to see the contents inside if we access the shared folder via SMB on a Windows 7 PC. Please advise if anyone experience any issues updating a very old firmware on the NAS to the latest.3.5KViews0likes3CommentsRate limit by MB's for Netgear WC9500
Dear Netgear, I'm struggeling with rate limits which I would like to configure on a Wifi network which is currently installed at one of our clients. We're using a Netgear WC9500 in combination with Netgear WNDAP360 AP's. I've configured multiple SSID's, one of them is for guests. I would like to limit this SSID by MB usage instead of a percentage of the bandwith. This way I can prevent guests from hijacking the entire Internet connection. please consider this feauture in the next firmware. regards, Frank14KViews2likes1Comment