try this link
http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04677033Document ID: c04677033
Version: 1
Advisory: HP Virtual Connect - Any VC Domain Running VC Firmware Versions 3.30 through 4.01 May Not Properly Load the Virtual Connect Manager (VCM) Web User Interface After 5 May 2015
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.
Release Date: 2015-05-08
Last Updated: 2015-05-08
DESCRIPTION
Any Virtual Connect domain running VC Firmware Version 3.30 through 4.01 may no longer load the Virtual Connect Manager (VCM) Web User Interface (UI) properly. Virtual Connect Firmware Version 4.10 (or later) does not exhibit this issue. In addition, all versions of the VCM Command-Line Interface (CLI) function properly. The VCM Command-Line Interface is NOTaffected by this issue.
IMPORTANT : This is a management issue only. NO traffic outage of any type occurs as a result of this issue.
The initial indication of the problem is exhibited after logging into VCM and being directed to the homepage. The left frame will be blank or will stop responding on "Loading Libraries". When navigating to other pages, the center frame may also be blank or stop responding.
This issue will occur because the Virtual Connect Web UI requires the use of Adobe Flash Player and the digitally signed files used by Adobe Flash Player expired on 5 May 2015. After this date, any VC Web UI flash components will not load due to the expiration of the digitally signed files.
SCOPE
Any Virtual Connect (VC) domain configured with the following Virtual Connect Modules and running VC firmware versions 3.30 through 4.01:
HP 1/10Gb Virtual Connect Ethernet Module for c-Class BladeSystem
HP Virtual Connect 1/10Gb-F Ethernet Module for c-Class BladeSystem
HP Virtual Connect Flex-10 10Gb Ethernet Module for c-Class BladeSystem
HP Virtual Connect Flex-10/10D Module for c-Class BladeSystem
HP Virtual Connect FlexFabric 10Gb/24-port Module for c-Class BladeSystem
RESOLUTION
As a workaround, perform the actions described below to restore the ability for a client system to use the VCM Web UI on affected VC firmware versions. This workaround addresses the issue on a single client system and is specific to each user; therefore, if there are multiple client systems or multiple users, the workaround must be performed for each instance.
IMPORTANT: HP is currently developing an efficient solution to this issue and this advisory will be updated in the near future to provide a simpler set of download and file naming changes. The following workaround is being provided as an interim solution for customers who need to make immediate changes.
Download the following seven (7) files directly from Adobe:
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/framework_4.1.0.21490.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/framework_4.1.0.16076.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/osmf_flex.4.0.0.13495.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/rpc_4.1.0.16076.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/spark_4.1.0.16076.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/sparkskins_4.1.0.16076.swz Non-HP site
http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz Non-HP site
Disclaimer :
Note : One or more of the links above will take you outside the Hewlett-Packard web site. HP does not control and is not responsible for information outside of the HP web site.
Copy the files into a temporary directory. Open a command window in the directory containing the downloaded files and use the following commands to rename the files:
For Windows systems:
ren framework_4.1.0.16076.swz => 871F12AF0853C06E4EB80A1CCAB295CEADBB817A.swz
ren framework_4.1.0.21490.swz => F78F74378B1552FF9A1725155D1B43BA54BE9094.swz
ren osmf_flex.4.0.0.13495.swz => C3306B26751D6A80EB1FCB651912469AE18819AB.swz
ren rpc_4.1.0.16076.swz => 6DDB94AE3365798230849FA0F931AC132FE417D1.swz
ren spark_4.1.0.16076.swz => 6344DCC80A9A6A3676DCEA0C92C8C45EFD2F3220.swz
ren sparkskins_4.1.0.16076.swz => 440AE73B017A477382DEFF7C0DBE4896FED21079.swz
ren textLayout_1.1.0.604.swz => 381814F6F5270FFBB27E244D6138BC023AF911D5.swz
For Linux systems:
mv framework_4.1.0.16076.swz 871F12AF0853C06E4EB80A1CCAB295CEADBB817A.swz
mv framework_4.1.0.21490.swz F78F74378B1552FF9A1725155D1B43BA54BE9094.swz
mv osmf_flex.4.0.0.13495.swz C3306B26751D6A80EB1FCB651912469AE18819AB.swz
mv rpc_4.1.0.16076.swz 6DDB94AE3365798230849FA0F931AC132FE417D1.swz
mv spark_4.1.0.16076.swz 6344DCC80A9A6A3676DCEA0C92C8C45EFD2F3220.swz
mv sparkskins_4.1.0.16076.swz 440AE73B017A477382DEFF7C0DBE4896FED21079.swz
mv textLayout_1.1.0.604.swz 381814F6F5270FFBB27E244D6138BC023AF911D5.swz
For Windows systems, copy the renamed files to the following directory. When prompted, select the option to overwrite the destination file(s):
%appdata%\Adobe\Flash Player\AssetCache\(dir)
For Linux systems, copy the files to the following target path:
/<user homedir>/.adobe/Flash_Player/AssetCache/<dir>
Note: the (dir) listed in the path above will be a randomly generated directory name. An example directory name would be: SAHK46GQ. If there are multiple directories, copy the files to the first alphabetically-ordered directory.
Close and restart your browser
Note: If the Adobe Flash Player Cache (this is different from the browser cache) is cleared or if Adobe Flash Player is reinstalled, the above steps must be repeated.