Release notes Version 1.8.2 Applicable models: GigaCore O26-I / GigaCore 30i / GigaCore 20t / GigaCore 18t / GigaCore 16t GigaCore 16tf / GigaCore 16i / GigaCore 10t / GigaCore 10i / GigaCore 10t-IP With this release, we introduce support for a new model, new features, improvements, and bug fixes. Applicable Models: • GigaCore O26-I • GigaCore 30i • GigaCore 20t • GigaCore 18t • GigaCore 16t • GigaCore 16tf • GigaCore 16i • GigaCore 10t • GigaCore 10i • GigaCore 10t-IP New models: This firmware introduces support for GigaCore O26-I, an all-SFP 40-Gigabit switch. New features: It is now possible to configure the GigaCore as the PTPv2 grandmaster clock. An option is available in PTPv2 Boundary clock mode to make the GigaCore ‘grandmaster capable’ [Fig 1] and configure a priority1 value. Note that a PTPv2 profile must be selected, a GigaCore operating in Boundary Clock mode with the ‘Auto’ profile cannot be grandmaster capable. *This option is NOT available on GigaCore 10t, 10i and 10t-IP. With this release, it is now possible to change the priority1 field of a PTPv2 clock when GigaCore is in replicate mode. This feature is useful in situations where the source clock is using a certain priority1 value (X) but a ‘rough’ end device has been set to a lower priority1 value (Y) and is therefore not willing to accept the priority1 value of the replicated clock. With this feature, the replicated clovariousd to use a priority1 value that is below Y. Additionally, various ‘replicating’ clocks referencing the same clock source can be configured to use different priority1 values. *This option is NOT available on GigaCore 10t, 10i and 10t-IP. Silent fans: Two fan operating modes can be selected from the WebUI and/or controlled remotely via API: Silent mode (=default) where, on supported models, fans can be temporarily set to 0 RPM to be completely silent in performance passages that require this. Or Normal mode where the fans are being controlled according to the most optimal algorithm and maintain a continuous airflow. HTTPS: The GigaCore web UI can be configured to use HTTPS instead of HTTP. This enhances communication security to the GigaCore. Araneo GigaCore v1.10.1 (or higher) is required to configure and monitor GigaCores with HTTPS enabled. When HTTPS is enabled, browsers may show a “Not Secure” warning. This occurs if the certificate used for HTTPS is not recognized by the browser or device, or if it is not signed by a certificate authority (CA) trusted by the browser or device. Milan redundancy operating mode: GigaCore can now detect and flag wiring issues in a redundant Milan-AVB network. Configuration is done in the web interface [Fig. 5] when AVB is enabled. A new LED mode indicates the selected or detected Milan mode on the port LEDs. For example, when a primary MILAN/AVB connection is connected to a secondary defined port, an error will be indicated on the mode LED of that port, making troubleshooting very efficient. DHCP: DHCP leases can be exported to a CSV file. The DHCP page now includes an optional shortcut button to create static reservations for all visible dynamic leases at once. A new API function has been added to create custom SNMP communities. This can be configured through the API under /api/snmp. Improvements: The default IGMP querier version has been set to v2 (previously v3). Based on customer feedback, we learned that many end device implementations experienced issues with queries from IGMPv3 queriers. Configuration to v3 remains possible. Note that this new default will only take effect after a factory reset has been performed. Improved “Talker Failed” issue recognition and prevention mechanisms. When using multiple groups with MILAN/AVB enabled, there was a small chance that streams across those groups could use the same multicast destination, resulting in “Talker Failed” errors. This behavior has now been addressed and improved. GigaCore now supports unicast replies to mDNS requests, greatly improving the discovery process in larger networks. The Web UI now displays the GigaCore device name in the top-right corner [Fig. 6] of the webpage. This makes it easier to identify the correct device when multiple browser tabs are open for different physical units. Bug fixes: An issue was addressed where the delay between timeTransmitter and timeReceiver could become too large. Specifically, a bug was fixed where the delay between the Grandmaster and timeReceiver would increase when the switch operated in boundary clock mode and the GM was in one-step operation. The API documentation for the oper_idle_slope field has been corrected, as it previously displayed the wrong unit. A bug was resolved where the Web UI sometimes did not show all configuration options or failed to update status information when a password was enabled on the GigaCore. Fixed a bug where gPTP (for AVB) did not function correctly when toggling AVB while PTPv2 clock mode was set to disabled for that group. In IGMPv3 querier mode, “Leave” requests from certain devices were not handled correctly when these devices used the block source functionality. This has now been resolved. A bug was addressed where the DHCP server in Layer 3–capable GigaCore switches would not accept configuration changes to the IP address or subnet mask.