New answers tagged storage-area-network
This is entirely dependent on the software you are using. Exchange, for example, does not support NAS protocols such as NFS or CIFS/SMB for its databases; only SAN and DAS solutions like iSCSI or Fibre Channel. There is also general confusion about what constitutes NAS and SAN. Many new products are what is called "unified storage"; a combination of NAS ...
Answering to your question about setting disks in fault state: the Storage Manager Client allows you to maually fail a disk. In the main menu, go to "Advanced" -> "Recovery" -> "Fail drive"
ewwhite was right. For those how want to see how i get the values in PRTG (Networkmonitoring) here are my scripts. I know the following is NOT very nice and seems to be very "froggy", but for me it works and i only need values over a periode of about a week... The ssh connection is established via "plink.exe" a smart comand line tool as a part of the SSH ...
You're really not going to be able to get this information out of an MSA or P2000 storage array. At least, no historical information. You could parse the output from the SSL CLI at regular intervals, but that's not ideal. This is just a disadvantage of the platform. You may want to check with the OEM, DotHill to see if anything is available from their ...
You can download HP MSA2000 Monitoring Management Pack, msacli.exe is the part of this pack. Also you can use SNMP for monitor perfomance of HP MSA.
I'd check the following in order Verify HBA adapters on second servers are connected to Brocade switch(s). Verify WWPN's from 2nd server are logged into Brocade switch ports. Verify HBA WWPN's on second server are zoned correctly in Brocade switch(s). Verify WWPN's from 2nd server are visible from DS8000. Verify LUN's on DS8000 are assigned to the correct ...
From My experience you should login to the System Insight Management Page https://xxx.xxx.xxx:2381 x= ip address of the nodes user "sanmon" password "sanmon" Check the disks status and the raid controllers status. My guess you will find there your problem.
Put it on a dedicated storage-specific VLAN, chances are there won't be a need to route at all if you run all of your storage and servers into the same switches. This gives you the option to monitor JUST the SAN traffic and potentially to traffic-manage it if needed.
I don't believe this question has been answered, I recently found another article that discusses this issue and a work around for 5.5 users. http://blog.igics.com/2014/07/heads-up-vmware-sioc-virtual-disk-iops.html
Top 50 recent answers are included