SoftHub

Bug Fixes:

- Issue error reply when user attempt to configure sFlow on LAG due to hardware limitation.
- Web accepting special characters but CLI is not accepting for port description.
- MLAG secondary device STP port states showing incorrect even spanning tree disabled in topology.
- Client was not able to obtain IP address from DHCP pool, the service is no longer working after running for a short time.

Changes and Restrictions:

- 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," and its IP will be set to "0.0.0.0" and DHCP mode is enabled on management VLAN instead.
- M7100 will not support IPv6 management if L3 license (routing and multicast) was not installed.
- The auto install is not allowed to apply a config file if the startup-config file contain the commands related to the "network" interface which is not supported on 11.0.
- If user configures the ports as protected port, routing mode is not allowed to configure on the VLAN in which those protected port are added.
- PVST/PVST+ M7100 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.

Upgrade Procedure:

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" page, and select Text Configuration option and 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, and remember its location in the PC’s file system.
3) 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.
4) 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.
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 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.
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 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.
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, under Device Status) to confirm the switch firmware is the one downloaded.
10) Verify the switch running configuration by issuing "show run