GSM7224R, GSM7248R Firmware Version 7.2.1.6

Published Nov 11, 2008

New Features/Enhancements:

1. Extend IP ACL rule configuration for including TCP flag field as filtering criteria
2. Add Protected Ports Feature
3. Remove GSM72xxR system boot menu option for deleting the operational code
4. GSM7224R/48R: show hardware temperature, fan status, and RPS status are slow to get updated after switch rebooted

Bug Fixes:

1. If configuration steps contain command lines to set the same PVID for a port multiple times, the configuration file may not be saved when the save command is issued.
2. Traffic destine to a VRRP virtual MAC address will stop being forwarded after the VRRP master is rebooted. No response on console and from GUI while modify MSTP port path cost thru GUI
3. The switch would fail in using xmodem protocol to download file to the switch by serial port
4. GUI MSTP: VLAN 24 can not be associated with MST instance.
5. OSPF GUI configuration page is missing “external-lsdb-limit” field
6. HTTP firmware download failed while using GUI with HTTPS mode

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: