RackSwitch G8316 Firmware Release Version 7.6.6.0 (Released July 2013) ** Changes since the 7.6.5.0 release ** Enhancements: None. Changes: None. Fixes: - A Security vulnerability existed in the OSPFv2 Routing Protocol that is used in IBM System Networking Ethernet Switches (CVE-2013-0149) - A Security vulnerability existed in IBM Switches which support Fibre Channel over Ethernet (FCoE), in that data frames were being flooded out of every port if the destination address was not in the MAC table. (CVE-2013-0570) ======================================================================= RackSwitch G8316 Firmware Release Version 7.6.5.0 (Released April 2013) ** Changes since the 7.6.3.0 release ** Enhancements: None. Changes: - Added the ability in Hotlinks configurations to enable STP on non-Hotlinks ports, thus removing the previous restriction that STP be globally disabled whenever the Hotlinks feature was enabled. (67161) Fixes: - With Putty SSH client version v0.61 or later, if the amount of data being transferred is larger than the Putty Channel Window (16KB), the client will send an SSH channel request to the server. The issue was that the switch would misinterpret this request and erroneously close the session, and display the "ERROR in processing the SSH message(payload too large)" message at the terminal. (65974) - Polling the Forwarding Database via SNMP would result in prolonged high CPU utilization if the same MAC addresses were learned in multiple VLANs. This would make it difficult for the CPU to process BPDUs in a timely manner, possibly resulting in an STP topology change. (66621) - A crash would occur when booting if the "logging synchronous" command was in the startup configuration. (66885) - FTP sessions establisehed over an IPv6 interface could close unexpectedly during data transfer. (67076) - A crash would occur during reboot if the "no tacacs-server enable-bypass" command was present the start-up configuration, but the "tacacas-server enable" command was not. (67376) - A crash could occur when polling the Forwarding Database via SNMP. (67410) - With Hotlinks configured, the STP configuration would be lost when the mode was changed from RSTP to MSTP. (67522) - After disabling the Virtual Router group, the "show running" command would erroneously display the factory default information for the group. (67667) - If the LACP member port for which the PBR next-hop ARP entry was associated went down, traffic destined for the next-hop router would temporarily be lost. (68150) - After a VRRP fail-over (i.e., the Master switch goes down), the route to the PBR next-hop Router would not always be reestablished after the Backup switch became the Master, and traffic would not resume. (68352) - In a Hotlinks topology, copying either the active or backup configuration to the running configuration could lead to the HotLinks standby interface being put into the forwarding state, resulting in a network loop. (68596) - When uploading a configuration file via a Microsoft Windows SCP client, and/or if the file had been previously saved in the Windows file format, the error message "Warning : Switch type not specified. Configuration may not load properly" would be displayed. This was actually a benign error, since the upload would actually complete successfully. (69045) - Removing a VLAN from a Spanning Tree Group (STG) other than the Default STG (STG 1) would inadvertently trigger a topology change in the Default STG. (69303) - After a failover in a Hotlinks topology with more than 500 VLANs, some MAC entries would not be re-programmed in the new Master switch's Forwarding Database (FDB), resulting in flooding within the associated VLANs. (69413) - With STP disabled, MAC entries associated with a physical port would not be removed from the Forwarding Database (FDB) after adding the port to portchannel. (69571) - After changing the LACP key using the "lacp key xxx" command, the peer switch would generate a syslog recording the change, but the trunk number referenced in the syslog message would be invalid. (69590) - After a failover in a Hotlinks topology the with uplinks configured as portchannels, some MAC entries would not removed from the new Backup switch's Forwarding Database (FDB), resulting in flooding within the associated VLANs. (69917) - A crash would occur when sequentially executing the "interface [port | portchannel] shut" and "interface [port | portchannel] no shut" commands, after sFlow packets had previously been received. (70199) =============================================================================== Version 7.6.3.0 (Released February 2013) ** Changes since the 7.6.1.0 release ** Enhancements: None. Changes: - Added support for power supplies that meet the new China Compulsory Certificate (CCC) requirements for altitude and humidity. (68356) Fixes: None =============================================================================== Version 7.6.1.0 (Released December 2012) New and Updated Features ======================== BGP Route-reflector support: -------------------- Route Reflection is a technique to avoid a large number of sessions between IBGP peers. In this release, support for RFC4456 (BGP Route Reflection - An Alternative to Full Mesh Internal BGP (IBGP)) has been added. SNMP: Support for 8 Read-Only and Read-Write communities: --------------------------------------------------------- This release adds support for 8 read-community names(Read-Only), and 8 write-community names(Read-Write) with SNMPv1 and SNMPv2. RFC5340: OSPF For IPv6: ----------------------- The switch was previously compliant with RFC2740. Starting with this release, the switch is compliant with RFC5340, which supersedes RFC2740. VLAG and PIM Support: --------------------- Previous releases supported IP Multicast routing through the PIM protocol. Also previously supported was the VLAG (Virtual Link Aggregation) protocol. This release adds support for PIM over a vLAG topology, so that the most efficient multicast routing can be achieved in a vLAG topology. NTP Client Display Improvements: --------------------------------- The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet. With the NTP service enabled, the switch can accurately update its internal clock to be consistent with other devices on the network. In this release, the "show ntp" command has been updated with such details as clock offset, stratum, and reference clock. Also in this release is a dampening of the number of syslog messages generated when the system clock is updated or if NTP synchronization fails. Cisco like CLI: --------------- As part of this change, some existing ISCLI commands have been modified to look more like those in Cisco's IOS. The commands chosen for modification in this release are ones frequently used for VLAN, Port, and STP configuration. With these changes, those familiar with Cisco-IOS CLI can more readily configure the IBM-NOS VLAN, Port, and STP modules. Support for 4K VLANS: ----------------- Increased the scalability of VLANS from 2K to 4K