NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MKBKC
Nov 13, 2017Aspirant
M5300 stack firmware upgrade
Hello, My firm currently utilizes Netgear M5300-28G_POE+ switches in a stacked group of 10 devices. We are currently at firmware level 10.0.0.44, and I've been tasked to: a) Update to latest firmw...
- Nov 14, 2017
Hi again,
The process you are describing should be the correct process. I suggest reading the release notes instead, when it comes to firmware upgrades. The release notes explain the process from start to finish.
https://kb.netgear.com/000038811/M5300-Firmware-Version-11-0-0-31You simply update the stack and reboot. This should update all members in the stack. But yes, it requires a full reboot of the whole stack.
There is an important note here. When going from version 10.x to 11.x firmwares we changed the management VLAN. On 10.x the management VLAN IP address was on the CPU (network parms), but in 11.x firmwares the management VLAN IP address is now on the VLAN itself. This means you might have management VLAN IP address issues after the upgrade. It is easy to fix via CLI/console though. Let me assume VLAN 1 is your management VLAN, then after firmware upgrade you run these commands from CLI:
(M4300-28G-PoE+) >en
(M4300-28G-PoE+) #configure
(M4300-28G-PoE+) (Config)#interface vlan 1
(M4300-28G-PoE+) (Interface vlan 1)#ip address 192.168.1.254 255.255.255.0
(M4300-28G-PoE+) (Interface vlan 1)#endOf course, substitute IP address and subnetmask to your needs.
If something happens during the upgrade, the stack members don't upgrade properly, etc. then do let me know. It is important to schedule downtime in case there are some things to sort out. Also, I suggest doing it sometime in the week days (Mon-Fri) as pro support is available then. Again, just in case! And remember to backup the config first.
But generally speaking, follow the release note instructions closely and you should be just fine!
Cheers
MKBKC
Nov 14, 2017Aspirant
Good Morning ,
Thank you for your thoughtful response.
- I actually agree with you regarding the certificate, no worries here, this is a management request.
- I am not 100% clear regarding upgrading stack members when the manager switch is upgraded. Page 470 of the Software administration manual seems to suggest that after upgrading the manager switch, stack members are automatically upgraded: “Once the firmware is successfully loaded on the supervisor, it automatically propagates to the other members in the chassis.” http://www.downloads.netgear.com/files/GDC/M5300/M5300-M6100-M7100_SWA_v11_30Oct2015.pdf
Does this mean when the manager switch is rebooted, the entire stack will also reboot and upgrade? I need to fully understand this as it will certainly affect production.
Thank you,
Hopchen
Nov 14, 2017Prodigy
Hi again,
The process you are describing should be the correct process. I suggest reading the release notes instead, when it comes to firmware upgrades. The release notes explain the process from start to finish.
https://kb.netgear.com/000038811/M5300-Firmware-Version-11-0-0-31
You simply update the stack and reboot. This should update all members in the stack. But yes, it requires a full reboot of the whole stack.
There is an important note here. When going from version 10.x to 11.x firmwares we changed the management VLAN. On 10.x the management VLAN IP address was on the CPU (network parms), but in 11.x firmwares the management VLAN IP address is now on the VLAN itself. This means you might have management VLAN IP address issues after the upgrade. It is easy to fix via CLI/console though. Let me assume VLAN 1 is your management VLAN, then after firmware upgrade you run these commands from CLI:
(M4300-28G-PoE+) >en
(M4300-28G-PoE+) #configure
(M4300-28G-PoE+) (Config)#interface vlan 1
(M4300-28G-PoE+) (Interface vlan 1)#ip address 192.168.1.254 255.255.255.0
(M4300-28G-PoE+) (Interface vlan 1)#end
Of course, substitute IP address and subnetmask to your needs.
If something happens during the upgrade, the stack members don't upgrade properly, etc. then do let me know. It is important to schedule downtime in case there are some things to sort out. Also, I suggest doing it sometime in the week days (Mon-Fri) as pro support is available then. Again, just in case! And remember to backup the config first.
But generally speaking, follow the release note instructions closely and you should be just fine!
Cheers
- MKBKCNov 14, 2017Aspirant
Perfect,
Thank you, and really appreciate the VLAN management headsup. I can not create a change request listing everything that needs to happen, and request a maintenance window from management.
Very Best Regards!
- MKBKCNov 15, 2017Aspirant
Hello,
I'm posting again today this time regarding a NETGEAR GS724TP, currently at firmware version 00.01.02
I'd like to get it to the latest firmware version, which is v5.2.0.11. There are no special features (other than the IP address of the unit!) installed, No VLANS or anything of that nature.
Can I jump directly to v5.2.0.11 (I know, in my dreams, right!) from v00.01.02?
Can you provide the correct upgrade path, and I figure from reading several posts, one or more of the firmware updates will wipe the existing configuration.
- HopchenNov 16, 2017Prodigy
Hi again,
The release notes will always warm you if there is problem in updating, coming from a certain version. From what I can see, you need to go to firmware V3.0.6.1 first, then V5.0.0.15 and lastly V5.2.0.11.
Have a look here:
https://kb.netgear.com/25328/GS724TP-GS748TP-Switch-Firmware-Version-5-2-0-11
Cheers
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!