####################################################################### SuperMicro Switch Firmware Release 3.1.4.2-0006 ####################################################################### Date: April 7th, 2025 ####################################################################### Products Related ####################################################################### This firmware is applicable for the following switch products. SSE-T7132S/SSE-T7132SR/SSE-T7132D/SSE-T7132DR ####################################################################### Recommendation ####################################################################### This is the GA firmware release version. We recommend strongly to upgrade to this firmware version. ####################################################################### New Features and Improvements ####################################################################### Improvements: ------------------------------- Fix bugs as below list: 1. [ACL] It could not create the IPv6 ACL table with egress direction. 2. [AUTONEGO] The link is not always coming up when autoneg is enabled. 3. [VxLAN] 'show vxlan counters' does not work. 4. [MCLAG] Sometimes docker crash after mclag teardown. 5. [MCLAG] Swss crash when rebooting a peer switch and the detail as below list: Overview: SONiC MCLAG is designed to provides redundancy and load balancing between the MCLAG peers. When deploying SONiC MCLAG in a network, special care should be taken to ensure optimal configuration and to avoid common pitfalls. Recommended Deployment: SONiC MCLAG should be deployed primarily at the Top-of-Rack (TOP) or T0 switch layer. This configuration supports high availability and load balancing for servers and hosts connected to the network. Link Partner Consideration: The link partner of an MCLAG port-channel should be a single switch or a host with multiple NICs. This ensures that the network remains stable and that traffic is distributed efficiently across the aggregated links. Avoiding Back-to-Back Topology: Configuring MCLAG in a back-to-back topology (where two MCLAG-enabled switches are directly connected to each other via MCLAG port-channels) is strongly discouraged. This setup can easily lead to network loops, which can cause broadcast storms, packet loss, and network instability. There is a known issue that causes a swss crash when rebooting a peer switch. To avoid this issue, it is recommended to separate the keepalive and peerlink interfaces and not configure an IP address on the peerlink VLAN interface. 6. [WATCHDOG] sonic-mgmt add watchdog timeout event test fail. 7. [SNMP] Snmpagentaddress config did not work for link local ip address. 8. [PLATFORM] Sfp eeprom with option dom is not working on Xcvrs. 9. [PLATFORM] Release information should not none in sonic_version.yml file. 10. [BREAKOUT] Unable to breakout interface when eth0(mgmt port) is configured with static IP. 11. [VLAN] Cross-VNI traffic in Asymmetric EVPN IRB topology only reaches 0.002% of port speed. 12. [BGP] [bgp vrf ]Docker crash after spine-1 reboot in system integration test environment. 13. [AUTONEGO] Auto-negotiation takes long time to complete when all ports are set to auto-negotiation. 14. [MCLAG] Standby device docker crashes when reboot active device. 15. [IPv6] After add ipv6 interface to vrf, dut can not ping link-local address. 16. [MCLAG] mac is still learnt dynamically after shutdown portchannel (mclag member port). Known issues and limitations: ------------------------------- 1. [VxLAN] The unknown L3 packet can not flood to the corresponding VLAN member of the peer switch. 2. [BGP/VRF]The spine’s neighbor cannot re-establish within minutes after reboot. 3. [VxLAN] Docker crash after VXLAN MAC movement. ####################################################################### OTHER INFORMATION ####################################################################### The firmware is based on - The source code of sonic-buildimage branch: 202405 commit: 3a7ff52 on the github. - The Marvell iSAI version: 4.0.0.1.0.1. Installaion/Upgrade Steps: ========================== The SONiC image can be installed in 2 ways. (A) Installation from ONIE: Note: All the configurations/settings will be lost if the switch is upgraded from ONIE. Please backup your configurations before proceeding. 1) Interrupt the boot during countdown by pressing any key. And then pressing down key to select "ONIE" and enter key to enter ONIE bootloader. GNU GRUB version 2.04 +----------------------------------------------------------------------------+ | SONiC-OS-3.1.4.2-0006 | |*ONIE | | | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ 2) Pressing up key to select "ONIE: Install OS" and enter key to enter Install OS mode. GNU GRUB version 2.04 +----------------------------------------------------------------------------+ |*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | Supermicro SSE-T7132S DIAG | | | | | | | | | | | | | +----------------------------------------------------------------------------+ 3) Install the SONiC OS from ONIE as shown below. ONIE:/# onie-stop ONIE:/# onie-nos-install http:/// (B) Installation from SONiC prompt: 1) Install the SONiC OS as shown below. sonic-installer install http:/// If you have other problems, please refer the detail in the below web page: https://github.com/sonic-net/SONiC/blob/master/doc/SONiC-User-Manual.md#323-upgrade-or-downgrade-version ####################################################################### The information in this readme file has been carefully reviewed and is believed to be accurate. The vendor assumes no responsibility for any inaccuracies that may be contained in this document, makes no commitment to update or to keep current the information in this manual, or to notify any person or organization of the updates. Super Micro Computer, Inc. ("Supermicro") reserves the right to make changes to the product described in this manual at any time and without notice. This product, including software and documentation, is the property of Supermicro and/or its licensors, and is supplied only under a license. Any use or reproduction of this product is not allowed, except as expressly permitted by the terms of said license. IN NO EVENT WILL SUPERMICRO BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, SPECULATIVE OR CONSEQUENTIAL DAMAGES ARISING FROM THE USE OR INABILITY TO USE THIS PRODUCT OR DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN PARTICULAR, SUPERMICRO SHALL NOT HAVE LIABILITY FOR ANY HARDWARE, SOFTWARE, OR DATA STORED OR USED WITH THE PRODUCT, INCLUDING THE COSTS OF REPAIRING, REPLACING, INTEGRATING, INSTALLING OR RECOVERING SUCH HARDWARE, SOFTWARE, OR DATA. Any disputes arising between manufacturer and customer shall be governed by the laws of Santa Clara County in the State of California, USA. The State of California, County of Santa Clara shall be the exclusive venue for the resolution of any such disputes. Super Micro's total liability for all claims will not exceed the price paid for the hardware product. Copyright 2025 by SUPER MICRO COMPUTER INC. All rights reserved.