The EqualLogic you have listed uses 10GBe ports.
What config are you going to run the Storwize in?
1 Gbps iSCSI - Standard or optional 8 Gb Fibre Channel or 10 Gbps iSCSI/Fibre Channel over Ethernet host ports?
Also, Dell isn't listing the PS4110X on their site anymore... Are you going with 7.2 or 15K drives?
Hello!
Setup:
HP Proliant DL380p g8
HP 785GB Multi Level Cell G2 PCIe ioDrive2 for ProLiant Servers
ESXi 5.1.0 799733
HP IO Accelerator for ProLiant Install Package for VMware ESXi 5.0
The System was built around OCT'12
server performing stable and very fast - never any purples
but today, last friday and about 1.5 months ago the VMs did not repsond.
connecting with vsphere client. is ok - internal SAS storage is also ok - VMs using internal SAS are storage up and running
VMs using the fusion IO are halted - unable to access the disk.
browsing the storage shows the fusion io to be "empty" - no error only the root folder existing.
power down the machine, reboot successfull - fusion io storage is back - directory containing all folders, VMs up and runnning
the log displays:
"info : due connectivity issues no access to volume < .... > (datastore ssd) possible. trying to reconnect. result soon"
(sorry for chunky translation - the installation language is not english)
there are no newer drivers für the fusion IO, the patchnotes from esx updates dont show any storage related stuff, firmware should be also up to date.
anyhow - im going to update this weekend.
has anyone any ideas / help for my problem
こんにちは。
提示いただいたコマンドの実行結果を見たところ、iSCSI環境のようなので、
単純にiqn（iSCSIイニシエータの持つ名前）を見てどちらの経路がアクティブか確認してもよい気がしました。
たとえば、Get-ScsiLunPath の Nameや LunPathといったあたりを見ると
ESX側のiqn「iqn.1998-01.com.vmware:～」の末尾数字が、経路によって異なるはずです。
（ただし採番は 1.2.3...とならないこともあります。）
RuntimeNameを見たい場合は、下記のようにすれば見られます。
ScsiLunPathの戻すオブジェクトにScsiLunオブジェクトがあるので、それを直接指定してとってきています。
ただし、なぜか両系で同じランタイム名になってしまいました。
取得の仕方が悪いだけかもしれませんが・・・
PS> (Get-VMHost|Get-ScsiLun)[2] | Get-ScsiLunPath | select Name,LunPath,State,{$_.ScsiLun.RuntimeName} | fl
Name : iqn.1998-01.com.vmware:esx01-0f6076c0-00023d000001,iqn
.1991-05.com.microsoft:winstg1-target1-target,t,1-naa.
60003ff64b8d19e98313399cda15e62d
LunPath : iqn.1998-01.com.vmware:esx01-0f6076c0-00023d000001,iqn
.1991-05.com.microsoft:winstg1-target1-target,t,1-naa.
60003ff64b8d19e98313399cda15e62d
State : Active
$_.ScsiLun.RuntimeName : vmhba33:C0:T0:L0
Name : iqn.1998-01.com.vmware:esx01-0f6076c0-00023d000006,iqn
.1991-05.com.microsoft:winstg1-target1-target,t,1-naa.
60003ff64b8d19e98313399cda15e62d
LunPath : iqn.1998-01.com.vmware:esx01-0f6076c0-00023d000006,iqn
.1991-05.com.microsoft:winstg1-target1-target,t,1-naa.
60003ff64b8d19e98313399cda15e62d
State : Standby
$_.ScsiLun.RuntimeName : vmhba33:C0:T0:L0 ★なぜか同じRuntimeNameが表示された。
★一応、別のコマンドラインでも確認。
PS> (Get-VMHost|Get-ScsiLun)[2] | Get-ScsiLunPath | % {$_.ScsiLun.RuntimeName}
vmhba33:C0:T0:L0
vmhba33:C0:T0:L0★やっぱり同じRuntimeNameが表示された。
※確認した環境は、ESXi 5.0.0 build-623860 & Windows Storage Server 2008 なのでちょっと古いです。
参考にしたリファレンスはこちら
ScsiLunPath のなかに
http://www.vmware.com/support/developer/PowerCLI/PowerCLI51/html/ScsiLunPath.html
ScsiLun があります。
http://www.vmware.com/support/developer/PowerCLI/PowerCLI51/html/ScsiLun.html
あと、ちょっと気になったのですが、Windowsの場合iSCSIターゲット側のiqnは、
マルチパス構成でも両系で同じ名前になることが多い気がします。
iSCSIターゲット側(Windows Server?)の設定で、一つのターゲットに対して
ESXiの2つのIP（もしくはiqn）を接続許可する感じです。
以上です。参考になりますでしょうか。
remember that the is a 2GB limit on Express DB's, check your DB sizing. but for small deployments it will work, however if you are deploying a full SQL environment for vCenter why not create a new instance on the same SQL box and just use that.
Anyone ever solved this issue?
I'm having exactly the same with one of the servers here. Clean install did not help...
I'm also getting the following error several times before the snmp service quits with "out of memory".
PowerCLI Version
----------------
VMware vSphere PowerCLI 5.0 build 435427
---------------
Snapin Versions
---------------
VMWare AutoDeploy PowerCLI 5.0 build 575
VMWare ImageBuilder PowerCLI 5.0 build 575
VMware License PowerCLI 5.0 build 395016
VMWare vSphere PowerCLI 5.0 build 435427
That is not the latest PowerCLI build, perhaps you can try to upgrade to 5.1 and check if that makes a difference.
Avevo trovato anche io tempo fa questa cosa. Infatti e' gia' da un po' di tempo che avevo rimosso la chiave di registro indicata.
Il porblema pero' rimane. Ed al riavvio del server la chiave torna ad esistere nel registro.
Ma a questo punto non credo che il problema sia questo.
Credo sia piu' questo:
Errore del servizio Copia Shadow del volume: errore imprevisto DeviceIoControl(\\?\fdc#generic_floppy_drive#6&3b4c39bd&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000680,0x00560000,0000000000000000,0,000000000038B420,4096,[0]). hr = 0x80070001, Funzione non corretta. . Operazione: Esposizione dei volumi ripristinati Individuazione dei LUN delle copie shadow in corso Evento PostSnapshot Esecuzione operazione asincrona Contesto: Dispositivo: \\?\fdc#generic_floppy_drive#6&3b4c39bd&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} Analisi del volume rilevato: Existing - \\?\fdc#generic_floppy_drive#6&3b4c39bd&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} Contesto di esecuzione: Provider Nome provider: VMware Snapshot Provider Versione provider: 1.0.0 ID provider: {564d7761-7265-2056-5353-2050726f7669} Stato corrente: DoSnapshotSet
If in storage vMotion source datastore is created from one storage array and and destination datastore is created from another storage array and both storage array supports VAAI. So storage vMotion will use VAAI or not?
Great to hear it works now and thanks for the feedback.
André
oops.. I am guessing that the esx-imageprofiles that end in an 'S' are stateless?
and once I used one of these the script ran ok...
Just wondering if that is actually documented somwhere ? I haven't been able to find much info about the software depots online - maybe I'm not looking in the right place I guess. Everyday I learn more - and realise how much more I don't know :-(
Uhm, vedo che invoca il virtual floppy.
Lo usi? Io solitamente lo rimuovo sempre dalle virtual machine che faccio. Magari è una prova stupida, ma prova a rimuoverlo…
Ciao,
Luca.
No non lo uso. Ora lo tolgo e ti aggiorno.
Ciao.
Hello...
in your case i would consider creating many luns especially for exchange server and the DB server (sql server?)
exchange server will have 3 luns on for OS one for DB and one for logs. i dont know for the specific storage if there are best practices to create the luns. beware lun misaligment cause it will cost you in performace and follow the best practices for exchange server and db especially when you create the partitions (not from disk mamagement) create them through disk part with create partition primary align=x (when x is the value of the starting partition offset)
consider also that 1 big raid whith many disks has more spindles so more performance.
there are many many scenarios you can follow to achieve max perf and reliability.
Did you update the Host before installing VMware Player?
You could also try using Player 3 or 4.
hmm, the S bit isn't true either, still get the warning at the end of download/upload of all the VIBs - and while I guess it will still boot up, it says it will be like a fresh install?
It also doesn't contain the vmware-fdm so HA won/t be available.
I'm guessing I need to clone the imageprofile, identifiy and remove the VIBs that are not stateless, add the vmware-fdm VIB to it and then process it.
nope, VAAI will not be used for migration between different arrays. Legacy datamovers, FS3DM (if failed) followed byFSDM will be used.
http://frankdenneman.nl/vmotion/vaai-hw-offload-and-storage-vmotion-between-two-storage-arrays/
...hth!
not really no. if you disable management traffic, then you disable the ability to manage the host. What you need to do is separate the traffic and have at least the two ports connected to the switch. and configure you posts in failover mode.
I manage to find a dirty way 
Log into vsphere web client
administration
SSO
configuration
hit the plus sign
add your ad but with LDAP:// xxx:3268 no LDAPS://
(apparently this issue is mainly a cert issue)
then proceed as usual with this settings (http://communities.vmware.com/people/Mike_Laverick/blog/2012/09/24/vcenter-server-appliance--single-sign-on)
test the connection
it works ...
VCP5-DV is just a rebranding of VCP5, so you are a VCP5-DV now.
