HP Virtual Connect Firmware manual Fixes, VC 4.31 release resolves the following issues

Fixes

VC 4.31 release resolves the following issues:

•Any In-Use networks created in VC firmware version 4.2x or earlier may experience a one-time interruption when assigned to a server profile for the first time in VC 4.30. For additional information, see Customer Advisory c04492888 (http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-c044928 88).

•After updating Flex-10/10D modules to VC firmware 4.30, one or more modules might shut down due to a single instance of a high temperature reading from one of eight sensors on the module. For additional information, see Customer Advisory c04459474 (http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04459474).

•Networks are incorrectly marked as not in-use because of incorrect use of network ID parameters. This is only relevant to VC 4.30 which uses those ID parameters to enable the correct set of VLANs out of the total set of 4K VLANs supported. For additional information, see Customer Advisory c04422904 (http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04422904).

•Server ports continuously transmitting excessive priority pause frames on FCoE connections may not be shutdown by enabling Pause Flood Protection in VCM, causing VC and server communication loss.

•Unable to login to Virtual Connect Manager CLI even though the web GUI is available

VC 4.30 release resolves the following issues:

•A restore from a configuration backup fails in a multiple enclosure environment after upgrading from VC 2.xx to VC 4.20 or later versions.

•VCM displays a profile is pending when a VC module is removed and inserted.

•After configuring LDAP authentication, users accounts that do not have Domain role permissions receive an error when attempting to access the Local Users page. The error is only a notification because Local Users settings cannot be modified by users who do not possess Domain role permissions.

•If an iLO is in an unresponsive state when VCM performs an enclosure import, that blade may experience LAN/SAN disconnection.

•The Virtual Connect Manager process may restart unexpectedly causing a temporary inability to log in to Virtual Connect Manager through the browser or CLI.

•When a Virtual Connect FlexFabric module is re-inserted or power-cycled via Onboard Administrator there is a rare timing issue during initialization that could result in the module not passing FCoE traffic.

•LLDP DCBX is sent on FCoE-capable VC uplinks even if FCoE is not defined on the Shared Uplink Set.

•After updating from VC 4.01 or earlier to 4.10 or later with any blades containing SR-IOV capable NICs and any converged network adapters connecting to non-VC modules, the MAC addresses for CNAs connecting to non-VC modules could be changed to virtual connect assigned MACs instead of factory assigned MACs, causing loss of FCoE SAN connectivity.

•The backup and restore page does not load correctly when a user navigates from one tab to another on the Domain settings page.

Fixes 6