M5300 Firmware Version 11.0.0.11

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.11

• Fixed the issue where 'show network' doesn’t show the IP address for the management VLAN. Since 11.0.0.11, ‘show network’ shows the IP address for management VLAN. But if user specifies an IP address on previous 10.0 image and then upgrade it to 11.0.0.11, this command will show the IP address for the network interface.
• Fixed the issue where it is unable to set an IP address through EZCONFIG
• Fixed the issue where 'show msg-queue' causes switch crash When RPS5412 is used with AC power, Other fault(power denied) or AP rebooting on GSM7228PSv1h2
• Fixed the issue where packets received with error counters are not incremented when jumbo frames with CRC errors are sent
• The counter ‘Packets received with errors’ should not be incremented on all LAGs after upgrade to 11.0.0.10
• The counter ‘Packets with errors counter’ should not be incremented when packets with 1518 + tagging are sent

Changes and Restrictions

• While 10.0.0.x supports both M5300 and older GSM73xxSv1h2 such that the two series can stack together, the new 11.0.0.10 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.0.10, 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.0.10.

• 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 –

1. 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.x firmware is using more than 1K VLANs, then all of the configured VLANs will be lost after the upgrade from 10.0.0.53 to 11.0.0.10. User will need to reconfigure VLANs manually after the upgrade.
   
2. The 4K VLAN maximum is retained in SDM "Dual-IPv4-and-IPv6 data-center-enterprise" mode and "IPv4-routing-enterprise" mode.
   
3. 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. Updating to the 11.0.0.11 firmware requires that you are running 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.

To upgrade your firmware:

1. 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  and select the Text Configuration option. Click the Apply button to save the configuration file.
   

2. Download the new firmware from the NETGEAR product support page and store it in a PC. Remember its location in the PC's file system.

3. There are two ways to download the new firmware from PC to the switch:

   • Use TFTP which requires that a TFTP server is installed on the PC where the firmware is stored from Step 2. To use the TFTP method, or if you're using a telnet session to perform the firmware upgrade, continue to Step 5.

   • Use a web browser for downloading. This method does not require a TFTP server. Continue to Step 4 to use HTTP file download.

4. To use the HTTP method, go to Maintenance > Download > HTTP File Download. Click the Browse button and select the location of the new firmware. 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 you click the Apply button, the file transfer begins, followed by writing the new image to the flash memory. Do not power cycle or reboot the switch before the process is complete. The following message displays after completion.
   
   After completion , proceed to Step 8 to restart the switch.

5. 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.

6. You can use either the web interface or the CLI interface to perform upgrade using TFTP. To use web interface, go to Maintenance > File Download  and select Transfer Mode as TFTP. Complete the text fields on the page and click the Apply button to start. To use the CLI, either telnet into the switch or use the console port and follow these steps below.

7. 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.

8. To use the GUI to restart the switch, go to Maintenance > Reset > Device Reboot.
   

Make sure that All is selected from the Reboot Unit No. drop down menu. 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. Select the Save prior to reboot option if there are changes that may not have been saved. Click the Apply button to start the reboot process.

9. 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 to confirm the switch firmware is the one downloaded.

10. 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.

11. You can now make additional configuration changes for other applications, and be sure to use the save command to save the configuration when you are done.