File name: ibm_fw_scsw_en4093r-7.5.5_anyos_noarch.chg
****************************************************************
| |
| IBM Flex System Fabric EN4093 / EN4093R 10Gb Scalable Switch|
| Firmware Update |
| |
| Revision/Build ID: 7.5.5.0 |
| |
| (C) Copyright International Business Machines Corporation |
| January, 2012. All rights reserved. |
| |
| US Government Users Restricted Rights -- Use, duplication |
| or disclosure restricted by GSA ADP Schedule Contract with |
| IBM Corp. |
| |
| Note: Before using this information and the product it |
| supports, read the general information under "NOTICES AND |
| TRADEMARKS" in this document. |
| |
| Updated <31 July 2013> |
****************************************************************
FIRMWARE CHANGE HISTORY
-----------------------
7.5.5.0
-------
IBM Flex System Fabric EN4093R 10Gb ScSw firmware version 7.5.5.0 (Released July 2013)
** Changes since the 7.5.3.0 release **
Enhancements:
None.
Changes:
None.
Fixes:
- A prolonged period of high CPU utilization would occur after an STP
topology change in the network (e.g., new Root Bridge election),
which could lead to protocol-thread starvation, if a large number of
Spanning Tree groups are configured on the switch. In one such case,
STP BPDUs were not being sent by the switch, resulting in a longer
than usual network convergence time.
(66881)
- 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).
- High CPU utilization would occur as the result of a prolonged series
of events that resulted in the generation of Syslog messages.
Sometimes this condition would result in Syslog messages being sent
without a timestamp.
(64681)
- If a vLAG switch was rebooted while the peer switch was unavailable
(e.g., operationally down), all of its vLAG ports would go into the
Error-disabled state (and remain there indefinitely).
(65056, 70698)
- A crash would occur while rebooting if a Syslog server was configured
on an IPv6 interface.
(66399)
- An old SSH version ("SSH-1.99-IBM") would be displayed when logging
into the switch, even though the switch fully supports SSHv2.
(68327)
- A hang of the Switch's I2C bus could occur, leading to a prolonged
period of high CPU utilization as retries are attempted. This could
result in the starvation of time-sensitive protocol threads, and eventual
failure of protocols to maintain their normal operating state.
(70887)
- A prolonged period of high CPU utilization can lead to protocol-thread
starvation. In one such case, LACP PDUs were not being sent by the CPU,
leading to the break down of the LACP trunk forming the ISL in a vLAG
topology. The ISL trunk ports that had previously been in the
STP Discarding state would then errantly go into the Forwarding state,
resulting in flooding of STP BPDUs into the network, and the inevitable
network loop.
(70887)
=======================================================================================
IBM Flex System Fabric EN4093R 10Gb ScSw firmware version 7.5.3.0 (Released April 2013)
** Changes since the 7.5.1.0 release **
Enhancements:
None.
Changes:
None.
Fixes:
- After upgrading to the 7.5.1 release, the Switch would no longer be
reachable from the CMM via the internal management port using an
IPv6 interface.
(65792, 67489)
- In a Stacking topology, NTP configuration settings would not be
applied to the new Master Switch after a failover of the Master.
(66311)
- An IGMP Multicast Router could errantly be configured via SNMP
on a port that was a member of isolated VLAN.
(66447)
- 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)
- SSH sessions would be terminated when configuring the Switch over IPv6.
(66631, 66657)
- With two mrouter ports configured, IGMP reports for the same multicast
group would be forwarded to both mrouter ports indefinitely, if the
primary mrouter interface had gone down momentarily.
(66673)
- Ping requests initiated from Telnet or SSH sessions would be prematurely
canceled (i.e., before the designated repeat count), if the System Idle
value had been set to '0'.
(66684)
- A crash would occur when booting if the "logging synchronous"
command was in the startup configuration.
(66885)
- Enabling CEE while the Switch ASIC is processing traffic could
cause CPU-bound control packets to be lost, possibly resulting
in protocols (e.g., LACP) going down.
(66920)
- FTP sessions establisehed over an IPv6 interface could close
unexpectedly during data transfer.
(67076)
- A conflict in the SNMP vmGroupInfo object in the would prevent
the Enterprise MIB from loading successfully in HP Open View.
(67157)
- 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)
- A Watchdog timeout could occur in a Stacking configuration with Teaming enabled.
(68142)
- 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)
- The switch would sometimes not receive the Management IP address assigned by the CMM
(XB141759)