HP Virtual Connect Version 3.18 Release Notes
Resolved issues  13 
when the aggregation group dissolved and was reformed. This resulted from all legs of the LAG not 
properly being reenabled in association with the Private Network. The servers that could experience the 
disruption where those whose transmissions were distributed (load balanced) to a leg of the LAG that 
was not reenabled for the Private Network. 
•  Resolved an issue where the stacking links showed a failed status after a module recovered from a 
NO-COMM state, even though no operational problem existed. Perform a VCM reset to update the 
stacking link status. 
•  Resolved a memory leak found in VCM during UI network reviews and profile assignments. This leak 
caused VCM to restart unexpectedly when prolonged. 
•  An adjustment was made for the limits used by VCM in monitoring its memory utilization so as to avoid 
conflict with the limits being used by the more general memory resource usage monitor for all 
applications running on the module. This adjustment ensures that when memory usage exceeds an 
expected, normal operational range, the VC management process can gracefully shut down. If 
configuration changes are made at the same time that the memory limit is exceeded, all configuration 
changes are saved. 
The following issues have been resolved in the VC 3.15 release: 
•  Resolved an issue where a profile with multiple networks defined in a connection had no configured 
network. If the profile was edited without making any changes, and then the profile was applied to a 
server with a Flex-10 LOM, a VCM failure and restart would occur. 
•  Resolved an issue where creating a profile with duplicate multiple networks could result in a network 
outage. 
•  Resolved an issue where VCM would reset modules that had port mirroring enabled when VCM 
restarted, causing an outage. 
•  Resolved an issue where VC modules did not provide server blade information, such as the part number 
and CPU data, through the CLI. 
•  Resolved an issue where when using the VC CLI, a user was unable to add LDAP groups with names 
containing spaces. 
•  Resolved an issue where a profile was created with multiple networks that use a Shared Uplink Set (SUS) 
and no networks were selected. If the profile was applied to a server with Flex NICs, a VCM failure and 
restart would occur. 
•  Resolved an issue where the "About" HP VCM popup window caused IE8 to crash, resulting in the 
About window not being displayed. 
•  Resolved an issue where the left navigation tree in the VCM GUI showed the incorrect status for 
Uplinkset. 










