NETGEAR M4200-10MG-PoE+ Managed Switch Firmware 12.0.0.15

Bug Fixes

- Fixed the issue where the packets might be dropped if DAC cable is used in fiber ports.

Limitations

- M4200 does not support 100M Half Duplex.

- M4200 doesn't support IPv6 tunnel and lookback interface.

Upgrade procedure

- Save the current configuration data. Normally the firmware will preserve the original configuration in the switch, however, just in case something went wrong during the upgrade, you may want to save a copy of current running configuration. To do so, go to ‘Maintenance->Upload’ page, and select Text Configuration option and click Apply button to save the configuration file.

- Download and extract the new firmware to a convenient place such as your desktop.

- The switch support dual image which means it has two firmware images calls ‘image1’ and ‘image2’. Before upgrading either one with the new firmware, check which image is active. You can check it using either web UI or CLI. In the following web example, the active image is image1 and backup image is image2. That means if the switch rebooted, it will use image1. Therefore if you upgrade image1, then upon reboot, the new firmware will be used.

To check the same with CLI, issue the following command:

show bootvar

The output will show which image is used for next reboot. It is best practice to upgrade the one not being used for next reboot (“Next Active Image”).

- 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. The second method is to use web browser which requires of no TFTP server. If you preferred to use TFTP method, or you’re using telnet session to perform firmware upgrade, continue to step #6.

- To use web method, go to the following web GUI page, and select the location of the new firmware via browse button, then click Apply button to start firmware upgrade. The upgrade will take about 2 minutes. Do not power cycle the switch before the process is complete. Assume image2 is backup image.

- Start a TFTP server on the PC where the new images are stored. If you do not have a TFTP server, you may want to try the following public domain TFTP servers

- On the switch console, type the following command on the console or telnet session window:

copy tftp:// image1 or image2

“” is the IP address where the TFTP server is running. The “” is the new firmware to upgrade to, and make sure the file is stored in the TFTP root directory. Select either to upgrade the image1 or image2.

The switch will ask to confirm with input data displayed. Hit enter if all parameters look correct.The file transfer process should take about two minutes, then the new firmware will be checked for possible corruption, if all checked out, it will report firmware successfully upgraded.

- At this point if you just reboot the switch, since the switch is not using the one you upgraded, then reboot will still using the old firmware. Follow the step below to change it to the new version.

- To use GUI to change the backup image to active, go to web page 'Maintenance->File Management -> Dual Image Configuration' page.

Assume image2 is the one upgraded. Select image2 on every unit in the stack (if you’re using a stack), and select ‘True’ in ‘Next Active Image’. Click ‘Apply’ button to make the change. If the new image is downloaded to the active image directly, please skip this step.

To use CLI to change the image to be used in the next reboot, type the following command:

boot system

And issue the following command to reboot:

reload

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

Or go to GUI System main page 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 there are not, please call Netgear customer support on discrepancy, or submit a trouble ticket from ‘my.netgear.com’. And manually reapply the missing configuration commands back to the switch.

- You can now make additional configuration change for another other application need. And be sure to use “save” command to save the configuration after you’re done.

About Switch Firmware:

Given the large variety of models and different methods for upgrading the switch, if you wish to apply this package, we recommend that you read and understand the installation steps before you install a new firmware, even if you are a power user.

Usually the update procedure isn’t much of a hassle as manufacturers try to make it as simple as possible; however, there are cases that are exceptions to this rule. First off, go to the system information page of the switch to check that the currently installed version isn’t either newer or matching this release.

Applying a new firmware can decrease the security vulnerabilities, enhance overall performance and compatibility, improve various power management functions, resolve different errors, and add support for newly developed technologies and protocols.

It is recommended that you perform this step in a steady power environment such as the one ensured by a UPS unit, and that you don’t interrupt the upgrade in any way, because this might cause the switch to malfunction.

That being said, click the download button, get and apply the new version, and check back with our website constantly to stay up to speed with the latest releases.