HP Virtual Connect Version 2.34 Release Notes

Resolved issues 9
Resolved issues
The following issues have been resolved in VC 2.34:
• Resolved an issue where IGMP Joins were only processed by VC on the first VLAN when a PF has
multiple mapped VLANs.
• Resolved an issue where IGMP Joins to grp 01:00:5e:00:00:01 would cause IGMP Query Tx
problems.
• Resolved an issue where the VCM daemon process would occasionally terminate and cause a
network outage due to a Segmentation Violation after a failover processing. This fix also resolved the
issue documented by Customer Advisory c02463297, which can be found on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c
02463297).
• Resolved an issue where a VC crash would occur while assigning a server profile to a server bay.
• Resolved an issue where a VC network outage would occur due to the inability to detect the state of
physical servers.
• Resolved an issue where when a VC-FC 4/8Gb 20-Port module renewed its DHCP lease and
received an IP address of the DNS server in the DHCP response, it attempted to register with the
DNS server. When the DNS server update request failed, the VC-FC module wrote an entry in the
one of the system logs indicating this failure. After some period of time and depending on the
frequency of the DHCP lease expiration, this log could cause the root file system to fill up to 100
percent capacity. VC-FC firmware 1.41 prevents the error log message from filling up the root file
system.
• Resolved an issue where changing the auto power options on the iLO and then shutting down or
starting up the blade server would cause VCM to display a connection reset or connection timeout
message.
• Resolved an issue where VC Ethernet modules running v2.30 or later may unexpectedly lose
stacking link connectivity due to CPU-generated data traffic, such as LACP and Link Layer Discovery
Protocol (LLDP), no longer transmitting.
• Resolved an issue where when taking a support dump, some older SFP module models were affected
and would result in a link down situation. This fix also addresses Customer Advisory c02465022,
which can be found on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c
02465022).
The following issue has been resolved in VC 2.33:
• Resolved an issue with Virtual Connect Flex-10 modules and NICs, where IGMP Snooping is
enabled. The IGMP snooping might stop working after a VC-Enet module is reset, restarted, or
power-cycled.
The following issues have been resolved in VC 2.32:
• Resolved an issue when un-initialized servers were installed and continuously attempted to PXE boot.
Each server was generating multiple Ethernet port state events, which could result in sluggish VCM
GUI responses.