M5300 Firmware Version 11.0.0.23 Release Notes
Applicable Models:
All M5300 series
- M5300-28G(GSM7228Sv1h1)
- M5300-52G(GSM7252Sv1h1)
- M5300-28G3(GSM7328Sv2h2)
- M5300-52G3(GSM7352Sv2h2)
- M5300-28G-PoE+(GSM7228PSv1h2)
- M5300-52G-PoE+(GSM7252PSv1h2)
- M5300-28GF3(GSM7328FSv2h1)
Bug Fixes since 11.0.0.18
- Changing VLAN Tag in Port PVID Config does not change presentation in VLAN membership.
- The command "show fiber-ports optics-info" will not display the transceiver type when plugged into the first 20 ports on on M5300-28GF3.
- The command "show interface status all" is showing media type as 1000BASE-X for LX transceiver.
- LLDP Management Address won't be adjusted to the IPv4 Management VLAN Interface.
- When the link flaps, mac drain timeout messages appear and the traffic forwarding stops.
- The switch is not using the configured radius source- interface while sending the radius packets.
- M5300 stack is crashing when one of the ASBR routers is rebooted.
Download
Using the Download Link below, download and extract the new firmware to a convenient place such as your desktop.The filename after extracting is m5300v11.0.0.23.stk.
Download Link: http://www.downloads.netgear.com/files/GDC/M5300/M5300_V11.0.0.23.zip
Changes and Restrictions
-
While 10.0.0 supports both M5300 and older GSM73xxSv1h2 such that the two series can stack together, the new 11.0.0 does not support mixed stacking of these two, only M5300 models.
-
If the network is configured as DHCP mode on the previous version, after it upgrades to 11.0, the "network" interface protocol mode will change to "none," its IP will be set to "0.0.0.0" and DHCP mode is enabled on management VLAN instead.
-
M5300 will not support IPv6 management if L3 license (routing and multicast) was not previously installed.
-
The auto install cannot apply a config file if the startup-config file contains commands related to the "network" interface which are supported on 11.0
-
If a user configures the ports as protected port, routing mode is not allowed to configure on the VLAN in which those protected port are added.
-
SDM changes on M5300 -
- The number of maximum VLANs changed in the default SDM ("Dual-IPv4-and-IPv6 data-center-enterprise") mode, from 4K to 1K VLANs. If M5300 with 10.0.0 firmware is using more than 1K VLANs, then all of the configured VLANs will be lost after the upgrade from 10.0 to 11.0. User will need to reconfigure VLANs manually after the upgrade.
- The 4K VLAN maximum is retained in SDM "Dual-IPv4-and-IPv6 data-center-enterprise" mode and "IPv4-routing-enterprise" mode.
- When using the default SDM mode, the following features are not supported. If user would like to enable them, please use other SDM template.
-
IP Source Guard
-
DHCP Snooping
-
Dynamic ARP Inspection
-
-
PVST/PVST+ in M5300 only supports VLAN ID range from 1 to 1024 . If user enables the PVST, make sure all of VLAN IDs are in the range of 1 to 1024.
Before Upgrading
-
Make sure you are running on the 10.0.0.53 firmware if you upgrade the switch from 10.0.0.x to 11.0. Updating to the 11.0 firmware will require you to be on the 10.0.0.53 firmware.
-
This firmware will not work on a mixed stack of M5300 and non-M5300 switches. If you are updating a stack, please be advised that this firmware only applies to the M5300 series. Compatible models are listed above in Applicable Models.
Upgrade Procedure
-
Save the current configuration data. Normally, the firmware will preserve the original configuration in the switch. However, because this is a major firmware upgrade, you may want to save a copy of current running configuration, just in case something goes wrong during the upgrade. To do so, go to "Maintenance -> Upload" page, and select Text Configuration option and click the Apply button to save the configuration file.

-
Download the new firmware from the NETGEAR product support page and store it in a PC, and remember its location in the PC’s file system.
-
There are two ways to download the new firmware from PC to the switch:
-
One is using TFTP which requires a TFTP server be installed on the PC where the firmware is stored from step #2. If you preferred to use TFTP method, or you're using telnet session to perform firmware upgrade, continue to step #5.
-
The second method is to use web browser for downloading which requires of no TFTP server. Continue to the next step to use HTTP file download.
-
-
To use HTTP method, go to the following web GUI page (Maintenance -> Download -> HTTP File Download), select the location of the new firmware via the Choose File button, and click the Apply button to start firmware upgrade. The upgrade will take about 12 minutes. Do not power cycle the switch before the process is complete.

After the Apply button is clicked, the file transfer will start, and followed by writing the new image to the Flash memory. Do not power cycle or reboot the switch before the process is complete, and the success message will show up as below.

After the successful completion the upgrade, proceed to step #8 to restart the switch. -
To use the TFTP method, start a TFTP server on the PC where the new images are stored. If you do not have a TFTP server, we recommend using free tools such as PumpKIN or TFTPD32.
-
You can use either web interface or CLI interface to perform upgrade using TFTP. To use web interface, go to "Maintenance -> Download -> File Download," select Transfer Mode as TFTP, complete the text fields on the page and hit Apply to start. To use CLI, either telnet into the switch or use console port and follow these steps below.
-
On the switch console, type the following command:
a. # copy tftp://<tftp server IP address>/<image name> system:image
b. It will ask for confirm with input data displayed. Hit enter if all parameters look correct.
c. The download should take a minute or two. After that, the code will be checked for possible corruption, if not, it will report firmware successfully upgraded.
d. Reboot the switch by typing "reload" command or power cycle the switch. -
To use GUI to restart the switch, go to web page "Maintenance -> Reset" page, Device Reboot table.

Make sure that "All" is selected in "Reboot Unit No" drop down menu box. If it is shown with some other value like "1", then only unit 1 in the stack will be rebooted, and this may result in stack failure after the stack is rebooted. You may select "Save prior to reboot" option if you feel there are changes that may not have being saved. Click the Apply button to start the reboot process. -
After the switch is restarted, type the following CLI command to verify the version is correct.
a. # show hardware
b. Or, go to GUI System main page (System -> Management -> System Information, under Device Status) to confirm the switch firmware is the one downloaded. -
Verify the switch running configuration by issuing "show running-config" command. The output should match the configuration file saved on step #1. If they are not, please call NETGEAR customer support on discrepancy and manually reapply the missing configuration commands back to the switch.
-
You can now make additional configuration changes for other applications, and be sure to use "save" command to save the configuration after you're done.