Release 9.0.1.37 Firmware

Bug Fixes since 9.0.1.29:

  1. Stack issues (reboot backup unit caused the traffic got forwarded to CPU)
  2. Error message showed up after delete/add default IP route on XSM7224S
  3. Using URL http://x.x.x.x/filesystem/startup-config, user can download the config file without login
  4. Even if the user "logs out" using the "LOGOUT" button, the file can be downloaded
  5. No link on SFP module in combo slot after firmware upgrade
  6. Switch will crash when trying to copy command and using scp for destination
  7. Unable to negotiate 10Gb link with BCM57810
  8. Loss of connectivity when stack member reboots
  9. sFlow Data not being transmitted when configured on a LAG
  10. IDEA Informatique - Loss of connectivity when stack member reboots
  11. 100M mode doesn't work on copper port on XSM7224S with some ports configured as stack ports
  12. Add the IP address to the ARP collision message
  13. After enable ping debug, the XSM7224S hang somehow
  14. Ping to Loopback Interface Can't Go Through When There are ARP Requests going on the switch
  15. Unable to ping the VRRP virtual IP address from a routed interface
  16. Stack reboots when Customer enable NFS
  17. Packetcounters in gui and snmp do not match for certain values
  18. XSM Stack hangs up
  19. Running out of DHCP IP addresses
  20. Online case: 3rd party HW not working
  21. Packets loss and IP routing
  22. Switch crashed when setting up VRRP
  23. Collector log entries
  24. DHCP pool stops providing new lease after few weeks.
  25. Getting power supply state change in logs
  26. Spam in logs about interface out of range.
  27. ACls with source port defined don't work when Source and Dest not on same switch

Upgrade procedure

  1. 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 o 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.

Image

  1. Download and extract the new firmware to a convenient place such as your desktop.
  2. 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 for downloading 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 #5.
  3. To use HTTP 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 12 minutes. Do not power cycle the switch before the process is complete.
Image

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 show up as below.

Image

After the successful completion the upgrade, proceed to step #8 to restart the switch.

  1. 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:

PumpKIN - http://kin.klever.net/pumpkin/

  1. 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.
  2. 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.

  1. To use GUI to restart the switch, go to web page 'Maintenance->Reset' page, Device Reboot table.

Image

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.

  1. 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.

  1. Verify the switch running configuration by issuing "show running-config change" command. The output should match the configuration file saved on step #1. If there are not, please call Netgear customer support on discrepancy. And manually reapply the missing configuration commands back to the switch.
  2. 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.