SoftHub

Bug Fixes:

- Fixed the issue where the IP address assigned by using EZconfig could be lost.

- Fixed the issue where the SNMP agent sometime would time out when collecting MIB objects.

- Fixed the issue where the EzConfig won't allow assigning a static IP address which is used when switch was in DHCP mode before running ezconfig.

- Fixed the issue where the EZConfig won't disable global routing.

- Fixed the issue where the no warning error message when reaching hardware limit in adding ACL.

- Fixed the issue where the SNTP configure question in EZConfig does not allow user NOT to configure SNTP.

- Fixed the issue where there is an Error 404 when upload startup-config to PC.

- Fixed LLDP/LLDP-MED problems with inventory display.

- Fixed the DHCP Issues with DHCP IP address conflict that takes too long to age out and exhaust the DHCP pool prematurely.

- Fixed i2c error in some M4100-50G-POE+.

- Fixed the issue where the MAC address table counter shows wrong value after enabling GVRP.

- Fixed the issue where the the password for RADIUS account server changed after rename the RADIUS account server's name through GUI.

Changes and Restrictions:

- If the network is configured as DHCP mode on the version 10.0.1, after it upgrades to 10.0.2, the “network” interface protocol mode will change to ‘none’ and its IP will be set to ‘0.0.0.0’. And DHCP mode will be enabled on management VLAN instead.

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

- M4100 will not support IPv6 management on management VLAN.

- 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

- When M4100-D12G-POE+ / GSM5212P is powered up through PD ports 1 and 2, and ports 3 to 12 to be used as PSE ports, the maximum POE power budget delivered by ports 3 to 12 will be only 25W. In order for ports 3 to 12 to deliver the power, either configure the power limit type as ‘user-defined’ and configure the maximum power as 25W or configure the power limit type as ‘class-based’ and disable the high power Mode.

- If the switch model is a POE switch, since the new release comes with a new POE controller firmware that it will take a few extra minutes to perform the POE firmware upgrade. During that time, please don’t power off the switch. If upgrade fails somehow, please plug out all of the cable from the port and power cycle the switch.

- Do not use USB flash port to perform firmware upgrade if the switch model is a POE model.

Applicable Models:

- M4100-26G (GSM7224v2h2)

- M4100-50G (GSM7248v2h2)

- M4100-26G-POE (GSM7226LP)

- M4100-50G-POE+ (GSM7248P)

- M4100-50-POE (FSM7250P)

- M4100-D12G (GSM5212)

- M4100-12GF (GSM7212F)

- M4100-D12G-POE+ (GSM5212P)

- M4100-24G-POE+ (GSM7224P)

- M4100-12G-POE+ (GSM7212P)

- M4100-26-POE (FSM7226P)

- M4100-D10-POE (FSM5210P)

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

2. Download and extract the new firmware to a convenient place such as your desktop.

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

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