GSM7224R, GSM7248R Firmware Version 7.3.1.7

New Features/Enhancements:

1. Support Private Group that allows creation an isolated group of ports that its member ports can talk to each other or ports that does not belong to any group, but not to another isolated group members.
2. Support IEEE 802.1ab LLDP and LLDP-MED for discovery service. For instructions how to use the feature, please download the new “7.3 Command Reference Manual” from NETGEAR product support web site.
3. Log the event when the firmware upgrade is completed
4. Add support for erasing the password without erasing the configuration
5. Support CPU port mirroring to allow monitoring of traffic in and out of the management CPU
6. Improve the firmware upgrade process to reduce the chance of the upgrade failure which might be corrupting the boot up code
7. Event log is no longer supported
8. Change the default priority queue mapping for CoS queue and DSCP to the range of zero to two. 

Bug Fixes:

1. The switch might crash when Force10 switch SSH clients is used to login the switch
2. Sometime static ARP table entry can not be deleted
3. Device view is not displayed when using https in SSL v3 mode
4. Multicast: multicast entry is not aged out when unknown multicast filtering is enabled
5. Sometime during upgrade the configuration file may be corrupted
6. Mis-configured port channel might cause packet buffer leak
7. SNMPV3: SNMPV3 commands are not under 'show running config' after setting
8. If the ports PVID is configured as non existing VLAN,  CPU don't see the STP BPDU's through the port 

Important Note:

1. This version will support configuration migration from all previous to this version. However, if you decided, after the upgrade, to revert back to the version 6.x or older from this version, the configuration of the switch will be lost. For this reason, you may want to save your current configuration before the upgrade.
2. If you are upgrading a GSM72xxR with beta firmware version 7.2.1.2, you cannot upgrade to this firmware using TFTP or HTTP. You have to load the new firmware using the serial console.

Upgrade Instructions:

1. Save the current configuration data. If you have not setup any special functions on the existing switch other than the management IP address, or you have saved a copy of the configuration in a text file, proceed to the next step.
   • On the existing switch, use capture mode in Hyperterminal to capture the output from the switch console to a file.
   • On the switch console, type “show run”. The output of current running configuration will be captured in the file.
   • Open the file and review the content. If there is any changes to the configuration but not present in the file, manually add them. Save the file after it is done.
   Note: If you’re running Microsoft Vista and there is no Hyper Terminal communication program for serial port, then you might consider downloading a public program called Tera Term in this web site (http://hp.vector.co.jp/authors/VA002416/teraterm.html).
2. Using the button below, download the firmware file.
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. The second method is to use HTTP which requires of no additional TFTP server program on a host PC. To use HTTP method, simply goes to file utility page on the web session, and select the firmware download page. Then just follow the screen display to perform the firmware upgrade. If you preferred to use TFTP tool to perform firmware upgrade, continue to the next step.
4. 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 either of the following public domain tftp servers: 
   PumpKIN - http://kin.klever.net/pumpkin/ 
   Solarwind - http://support.solarwinds.net/updates/New-customerFree.cfm
5. You can use either web interface or CLI interface to perform upgrade using TFTP. To use web interface, just go to file utility page on the web and follow the screen instruction to complete the firmware upgrade. To use CLI, either telnet into the switch or use console port and follow these steps below.
6. On the switch console, type the following command:
   • # copy tftp://<tftp server IP address>/<image name> system:image
   • It will ask for confirm with input data displayed. Hit enter if all parameters look correct.
   • 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.
   • Reboot the switch by typing “reload” command or power cycle the switch.
7. After the switch is restarted, type the following command to verify the version is correct.
   • # show hardware
8. .If you did not skip step #1, now you can use the saved “show run” output file to restore the switch to your configuration, otherwise skip this step.
   • First enter exec mode, by enable command after you logged in.
   • Once in exec mode, paste the content of that file to the console. If there is any error during such operation, please report it to NETGEAR tech support.
   • Do a “show run” command on the console and make sure everything you expect to be there is present. If not, please report the problem to the tech support and manually add your configuration back.
9. You can now make additional configuration change for your application need. And be sure to use “copy” command to save the configuration after you’re done.

Document Type:

This product includes software code developed by third parties, including software code subject to the GNU General Public License ("GPL") or GNU Lesser General Public License ("LGPL"). As applicable, the terms of the GPL and LGPL, and information on obtaining access to the GPL Code and LGPL Code used in this product, are available to you at NETGEAR's Open Source Code Web page. The GPL Code and LGPL Code used in this product is distributed WITHOUT ANY WARRANTY and is subject to the copyrights of one or more authors. For details, see the GPL Code and LGPL Code for this product and the terms of the GPL and LGPL.