Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 178257

Problem with HP P2000 G3 SAS and HP BL460c Gen8 Servers

$
0
0

Hello

We have 2 HP BL460c Gen8 Servers connected through 2 6GB SAS switches to an HP P2000 G3 (SFF) SAS Enclosure with dual sas controllers. We have connected a total of 4 sas cables to the enclosure (2 from each switch to each storage controller). We have created 2 volumes in the P2000, one with 10K sas disks and one with 15K sas disks, with each volume assigned to a different storage controller. Both volumes are successfully presented to both ESXi hosts (BL 460c Gen8 with ESXi 5 Build 914586). The problem was observed when we tried to deploy our first VM and we saw that the time that took for the VM to power-on (with no OS installed) was extremely long (about 3 min.). The same delay was also observed when a change was made in the parameters of the VM during the reconfiguration process. Checking the logs of both ESXi hosts the following events were repeatedly logged:

 

Successfully restored access to volume 50a96ca7-2161af34-b576-6c3be5a9a134 (P2000-RAID10-15K) following connectivity issues.      info                21/3/2013 3:24:58 μμ                       esxi3.elpen.elp

Lost access to volume 50a96ca7-2161af34-b576-6c3be5a9a134 (P2000-RAID10-15K) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.              info         21/3/2013 3:24:58 μμ                       P2000-RAID10-15K

 

The above logs were in both hosts and for both datastores. The VAAI plugin is installed on both hosts and and I have tried both MRU and Round Robin multipathing policies with the same result. I have restarted all the devices (sas switches – P2000 – ESXi hosts) with no result.

Any ideas?

May be someone with a similar configuration facing similar issues?

Thank you


Viewing all articles
Browse latest Browse all 178257

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>