SoftHub

Release Notes

Enhancements and Fixes in 2.2.5.2

The following is a list of fixes in version 2.2.5.2

- Firmware version 2.2.5.2 adds support for TN OTDR SFPs

- Firmware version 2.2.5.2 corrects the handling of Link OAM traps

- The issue where VLAN port configuration retained previous vlan ids and mode when changed from Web UI is now fixed

- Reload defaults should now clear DDMI receive power threshold

- Multiple SNMP fixes

- Industry Standard CLI

- Text Config file

- TACACS+ Accounting

Known Feature Limitations:

The following is a list of currently known issues for these devices with the 2.2.5 firmware.

- PTP over 10G ports running in 1G mode is not supported

- Synchronous Ethernet (SyncE) is currently not supported

- DHCP Relay is not fully supported

- TACACS+ Command Authorization does not allow config cmd execution

- When using TACACS+ accounting, command level filtering does not work - The Command Privilege Levels only works for Web users at this time.

- Service Activation Testing with the S4140, S4224, S4212 as the Loopback Device is not functional at this time.

- If PTP is configured on a 10G port of a S4224 as a Master unit and sync’d up with a Slave unit, if the Master unit is rebooted using a “reload cold” command, the Master unit may hang. PTP must be disabled on both Master and Slave unit before a reboot is done on the Master unit.

- Upon upgrading to 2.2.5.2, in the Web UI under Maintenance->Software->Image Select, sometimes the correct version of firmware may not show up. It can be resolved after waiting for a few minutes and doing refresh or with another reboot of the device.

- The maximum frame size available on the port configuration page is 10056 bytes. However, unless traffic is sent over an EVC, any frame larger than 6376 bytes is dropped.

- When setting up Carrier Ethernet services, it should be noted that for frame sizes larger than 4776 bytes, all yellow frames will be dropped.

WARNING

- If you are upgrading a device with 1.9.x or earlier firmware, after upgrading to the 2.2.5.2 firmware, the device configuration will be reset to factory defaults. This includes defaulting of IP address. The default IP address settings in 2.2.5.2 are DHCP enabled, with a 60 second fall back to 192.168.0.1

- If you want the option to revert back to 1.9.x you MUST backup your configuration file

config backup binary <hostname> <file_name>

- If you revert back to 1.9.x or earlier firmware, after upgrading to 2.2.5.2, you must run the following:

config default (to clear out any residual configuration)

config restore binary <hostname> <file_name> (to restore the 1.9.4 configuration you backed prior to the upgrade process)

Copper SFPs may need to be reseated for links to come up

About Switch Firmware:

Given the large variety of models and different methods for upgrading the switch, if you wish to apply this package, we recommend that you read and understand the installation steps before you install a new firmware, even if you are a power user.

Usually the update procedure isn’t much of a hassle as manufacturers try to make it as simple as possible; however, there are cases that are exceptions to this rule. First off, go to the system information page of the switch to check that the currently installed version isn’t either newer or matching this release.

Applying a new firmware can decrease the security vulnerabilities, enhance overall performance and compatibility, improve various power management functions, resolve different errors, and add support for newly developed technologies and protocols.

It is recommended that you perform this step in a steady power environment such as the one ensured by a UPS unit, and that you don’t interrupt the upgrade in any way, because this might cause the switch to malfunction.

That being said, click the download button, get and apply the new version, and check back with our website constantly to stay up to speed with the latest releases.

It is highly recommended to always use the most recent driver version available

Do not forget to check with