GSM7328S/GSM7352S/GSM7228PS/GSM7252PS firmware version v8.0.3.11

Applicable Models:

GSM7328S, GSM7352S, GSM7328FS, GSM7228PS, GSM7252PS, GSM7328S-200, GSM7352S-200

Release 8.0.3.11 Firmware

Release date: 7/16/2010

Major Changes from v8.0.2.x and older releases

1. Allow GSM7328S (v1), GSM7352S (v1), GSM7328FS, GSM7228PS, GSM7252PS, GSM7328S-200 (v2), and GSM7352S-200 (v2), to be used in the same stack.
   
2. One firmware image to be used for all GSM7328S (v1), GSM7352S (v1), GSM7328FS, GSM7228PS, GSM7252PS, GSM7328S-200 (v2), and GSM7352S-200 (v2).
   
3. Provide IPv6 Routing and IP Multicast upgrade capability to GSM7328S (v1), GSM7352S (v1), and GSM7328FS via software license.
   
4. Provide IPv4 and IPv6 dynamic routing, and IP multicast routing upgrade capability to GSM7228PS and GSM7252PS via software license.
   
5. Allow SFP+ front panel ports on GSM7228PS, GSM7252PS, GSM7328S-200, and GSM7352S-200 to be used for stacking application.

Open Issues:

1. The GUI fails to show the MLD proxy entry
   Description:  The GUI page "IPv6 Multicast->MLD->Proxy Memebership" will not show a table for the membership of the MLD proxy.
   Workaround:  From the CLI, use the command "show ipv6 mld-proxy groups" to see the membership table.
2. In the web GUI device view, the ports' status and unit numbers fail to show for the full8 units stack.
   Description:  When the switches are installed in the full 8 unit stack, the device view page in the web GUI might have difficulty showing all the ports' link statuses in real-time; i.e., the link state is not updated immediately.
   Workaround:  There is currently no workaround for this issue.
3. The list for OSPF route redistribution in the GUI can not be removed.
   Description:  After configuring the OSFP route Distribution List through the Routing > OSPF > Advanced > Route Redistribution GUI page, the Distribution List cannot be removed by selecting the blank in the Distribute List filed.
   Workaround:  Disable the Redistribute Option and click the Apply button.
4. ISDPs with blank device IDs do not appear in the GUI.
   Description:  The switch doesn't show ISDP neighbor information in the GUI if the neighbor's device ID is blank.
   Workaround:  There is currently no workaround on GUI; use the CLI to view neighbor information with blank device IDs.
5. Auto Install:  After downloading the bootfile.cfg file successfully, an error appears in the GUI.
   Description:  After downloading the bootfile.cfg file successfully, the following Transfer Status error message is displayed in the GUI:  "Auto Install Script file download through TFTP. Reason: Transfer direction is unknown."
   
   
   Workaround:  There is currently no workaround in the GUI, please use the CLI to view the Auto Install status.
6. The GUI does not show the saved QoS Policy configuration and displays the default configuration instead.
   Description:  When viewing the  QoS > Diffserv > Advanced > Policy Configuration page, the GUI only displays the default configuration instead of the last saved configuration.
   Workaround:  There is currently no workaround in the GUI; use the CLI to see the configured policy settings.
7. The switch console port does not display the user login prompt after setting the switch priority as 0 and rebooting.
   Description:  If the switch priority for stacking mastership is changed to 0 and the switch is rebooted, the console will not display the user login prompt.
   Workaround:  To resolve this issue, go into the utility menu and restore the configuration to factory default.
8. Some IPv6 ACL CLI commands are missing from the CLI.
   Description:  The command 'ipv6 traffic-filter' under interface and 'show ipv6 access-lists' are missing from the CLI.
   Workaround:  There is currently no workaround in the CLI; these will need to be configured through the GUI.
9. Some P-Bridge MIB objects are not getting populated.
   Description:The dot1dTpHCPortInDiscards, dot1dTpHCPortInFrames, and dot1dTpHCPortOutFrames objects are not returning anything.
   Workaround:  There is currently no workaround for this issue.

Upgrade procedure

1. Always make a backup copy of your current configuration before attempting a firmware upgrade. To save a copy of the current running configuration, go to Maintenance > Upload page, select the Text Configuration option and click Apply.
   
   

   Note 1-1:  Switches running firmware version 6.1.0.8 or older must upgrade to the intermediate firmware version 6.2.0.6 ( download here) prior to upgrading to firmware version 8.0.3.11

   
   Note 1-2:Temporary files may accumulate in the switch, filling the memory and preventing firmware upgrade.  Follow the instruction here  to clean up the temporary file.

   
   Note 1-3:  If your existing firmware is of release 7.x or older, the following page will show a different option for "File Type."  Select the file type desired and backup the file to your PC.

   

2. Download the new firmware and store it in a PC. Be sure to note the file's location in the file system.
3. Upgrade the firmware.  There are two ways to load the firmware from a PC to the switch:  TFTP through the PC’s TFTP server or HTTP through a web browser. 
   
4. Upgrade using TFTP through the console copy command (Recommended)

   This requires a TFTP server to be installed on a PC that is on the same network as, and accessible to, the Switch.

   1. Copy the downloaded firmware to the TFTP root directory.
   2. Start the TFTP server.
   3. From the switch console, execute the commands as pictured below.
      Note:  Do not reboot or power cycle the switch until it has downloaded the firmware and returned to the prompt.  Doing so may render the switch unbootable.
      
      
   4. Reboot the switch once it completes downloading the firmware and returns to the EXEC prompt.
      
5. pgrade using the Switch Web GUI
   1. Use any web browser to access the Switch management IP address.
   2. Go to the Maintenance > Download page, select HTTP File Download, and set the File Type to "Archive."
   3. If the current switch firmware is version 7.x:

      

      • Click the Apply button to start the download.  Do not power cycle or reboot until the switch completes the download and the Select File box becomes blank
      • Connect the PC's serial port to the switch console port using a DB9 cable (shipped with the switch). If your PC does not have a DB9 serial port, you'd need to get a USB to serial adapter to connect the PC to the switch's console port.
      • Start a terminal emulater on the PC such as Hyperterminal.
      • Reboot the switch and watch for the console output on the terminal emulator.
      • When the console outputs prompt you to enter boot menu, enter 2

      • 
        

      • We need to update the boot code. Select the option to update the boot code (usually it is option#8 depends on the firmware version). It should take less than a minute. Once completed, the prompt will return to [boot menu].
      • Enter command option#1 to start operation code.
      • The switch should be operational with the new firmware.
   4. If the current switch firmware is version 8.x:

      

      • Click the Apply button to start the download; a window will open to display the download progress.  There will be a new notification window once the download has successfully completed.
      • Access the command line interface of the switch using Telnet.
      • Login to the switch and enter "enable" to access the privileged mode.
      • Enter the command: update bootcode to update the switch's bootcode
      • Enter the command: reload to reboot the switch.
      • The switch should boot up with the new firmware.

 

After upgrading the firmware:

1. After the switch has restarted, verify the firmware version is correct.
   • From the CLI, use the command # show hardware
   • From the GUI, go to the System main page
2. Verify the switch running configuration by issuing the “show running-config change” command. The output should match the configuration file saved on step #1. If not, please call NETGEAR customer support and manually reapply the missing configuration commands back to the switch.
3. You can now make additional configuration change for your application need. And be sure to use "save" command to save the configuration after you're done.
4. If a stack of switches is being upgraded, each switch should automatically upgrade.  However, if the switch stack cannot boot up after the upgrade, try upgrading each individual switch before rebooting the stack.
5. If an older image (predating the upgrade) appears after rebooting, it may be the backup image if your previous version supported dual image.  To resolve this:
   • Determine the what image the switch is using:
     #show bootvar
     The output will indicate which image is in use; if it is image2, the newly loaded image should be image1.
     
   • Activate the new image:
     #boot system image1
     
   • Reboot the system.
6. In rare instance, after upgrading from a pre-8.0 release, the switch may stop at the boot menu during boot up:
   

   If this occurred, select menu option#11 to restore the configuration to factory default. Then, select option#1 to start the operational code. If this still do allow the switch to completely booted up, contact Netgear technical support for assistance.

Downloads > Driver/Software/Firmware