MS ESXi 4.1 cluster storage paths

Similar Questions

• ESXi 4.1 storage path

  Hi all

  I want to install 2 Server ESXi 4.1 and a Bay EMC Clariion CX4.

  In the storage management interface (Unisphere), each server registered with 4 storage (2 SPA and SPB 2) ports. The failover policy is ALUA 4 active/active.

  It comes to ESXi on server1 watch 4 storage path (see: Server1_Path.jpg), but ESXi on server 2 showing only 1 way (see: server2_path.jpg).

  The question is: why 2 server showing only 1 storage path, and how to trace this issue?

  Thank you very much

  Andarwen

  Why 2 server showing only 1 storage path, and how to trace this issue?

  There are ONLY 2 reasons.

  Zoning and Configuration.  either you area Server 2 in the same way you configure interfaces on server 2.  If they are of the same configuration, they will work the same.

• How to reach esxi host 5 on storage area network

  I have a Dell PS6000E on my network.  I would like to create a volume on it and use it as a shared storage for a new configuration of esxi5 with 2 hosts.  The PS6000 already contains 2 volumes in use by other servers (physical).  To access the PS6000 via my regular local network hosts.  Is this possible, and is there a documentation on how to put in place?

  Thank you

  Welcome to the community - I guess you access the PS6000E are configured for iSCSI or NAS/NFS, you will be able to access as shared storage long ESXi hosts can reach the unit. Because ESXi hosts will not be able to share the LUNS in use by other servers, you're going to create a new LUN for ESXi hosts. This storage of ESXi - http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf - guide that has information on how to configure your ESXi servers to access the storage.

• Not visible in the shared disk Cluster Storage Configuration dialog box

  When installing the 10 g to Oracle clusterware dialog "Cluster Storage Configuration" shows no shared disks.
  
  We use:
  
  Windows Server 2003
  
  HP Eva 4400

  Glad you liked the doc - Please feed back any info on the doc direct me

  they do not need to be logical for OCR devices and vote - I'm not 100% sure devices ASM - but a best practice is to create the logical volumes for all

  Philip...

• Having trouble getting the correct strategy of the ESXi 5.1 Compellent Lun path selection

  Here's the FCoE connections to a Compellent table. I was looking for in fact as expected on some new 5.1 ESXi hosts. I changed the default home setting "esxcli storage set - default-psp VMW_PSP_RR - ATAS VMW_SATP_DEFAULT_AA ATAS nmp. The LUN showed 2 paths, Type of storage array showed VMW_SATP_DEFAULT_AA and path selection has been set for the Round Robin.

  I finished rebuilding my hosts with ESXi 5.1 update 1 and made the same change but now the LUN show as VMW_SATP_LOCAL and fixed and I can see only one way? I do not understand why it reacts differently now. Does anyone have any suggestions?

  ~ # esxcli storage nmp ATAS list

  Description of default name PSP

  -------------------  -------------  ------------------------------------------

  VMW_SATP_MSA VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_ALUA VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_DEFAULT_AP VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EQL VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_INV VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EVA VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_ALUA_CX VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_SYMM VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_CX VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_LSI VMW_PSP_MRU placeholder (not loaded plugin)

  Non-specific bays of VMW_SATP_DEFAULT_AA VMW_PSP_RR Supports active/active

  VMW_SATP_LOCAL VMW_PSP_FIXED direct support of connected devices

  Thanks for the reply. I found the problem. I had to add a rule esxcli storage nmp ATAS FCoE add - transport fcoe - ATAS VMW_SATP_DEFAULT_AA - description 'Fibre Channel over Ethernet devices' I forgot to note that I did it on the first generation and completely forgotten. Once I added this to the existing a new LUN all show type and path of the storage of table selection.

• ESXi 5.1 cluster moving to new hardware

  I have a 5.1 ESXi cluster consisting of 2 servers of Sun I want to retire - Sun #2 is the best of the 2 servers.   I all 2 new Dell R620 stretched upward, wired and pre-loaded with 5.1 U1.  My license is for 4 and vCenter is a virtual machine in the cluster, I want all moved to new hardware with little or no interruption of service.

  This would be the way to go?

  1. set up Dell and storage server configuration networking properly (I am comfortable with this part).

  2 migrate all virtual machines to Sun 2.

  3. close the Sun 1 and remove the cluster

  4. Add 1 Dell to the cluster

  5 move the VM to Dell 1

  6. switch off the Sun Deceiver 2 and remove the cluster

  7. Add 2 Dell and move virtual machines as you wish.

  Sun servers were not identical, then the VCA mode is Intel "Penryn".    The specs say that future Intel processors can join to this group, so it is not a problem running 1 Dell and 1 Sun temporarily, correct?  The r.620 are the same, so as soon as they are both in the cluster can / disable CVS mode?    I have to restart each VM later so he would see the new processor features, correct?

  Is this what I need to look at.

  Thanks in advance for your answers.

  You can do a lot of ways, but I would recommend not to remove the beam #1 sunlight until you are 100% made to the migration. Which leaves you exposed from the point of view HA (assuming that it is production, since you want little downtime), and is an unnecessary step. RELATIVE to the issuance of licenses, since this is a migration of right, keep the r.620 in eval mode and change the licensing of more later. Which allows to rotate the environment MUCH easier.

  Here's what I'd do (emulation of your list)

  (1) Networking Setup / storage on r.620, to be compatible with the old SUN servers.

  (2) to present the cluster r.620

  (3) to migrate a low priority / test VM networking, testing vMotion and new hosts.

  (4) to migrate most of the virtual machine the new hosts.

  (5) migrate vCenter last VM (just to be safe)

  (6) put SUN 1 and 2 in maintenance mode. Leave them in the cluster for a few days just in case

  (7) remove SUN 1/2 cluster once everything works well, remove the former hosts of vCenter and closed. Clean a network configuration and storage, respectively (be careful here).

  (8) stimulus EVC Mode at the highest level appropriate (Sandy Bridge, I guess).

  (9) it is important, read closely. If you want to increase the level of CEV, after former guests are completely gone and dead, completely off each VM, a power back on. This will raise the functional level of CVS to the new level. Simply restart the guest OS won't do it. You can check by going to display hosts and clusters > VMS > add column EVC.

  Jon

• ESXi installation process and storage CF

  Hi all

  It's been a while since I worked with the CF based storage so forgive me if this is a silly question!

  I remember at the time of ESX 3.5 when a host is created, it is strongly recommended that you unplug your HBA as the installer ESX 3.5 was inclined to wipe your FC LUNS during installation.

  Is this always the case? If I add a bright new ESX5.1 host in a cluster existing I have to disconnect from the connected FC SAN for the generation?

  Thank you

  Chris

  No, during the installation of ESXi, it scans all the storage controller and storage/LUN connected to the server. Setup ESXi offer screen user input to select the storage that you want to install ESXi and installation takes place on the selected disk.

  If you are using a scripted installation, make sure that mention you the right VMHBA device in the KS file and remove the firstdisk option. For even if the device driver of the CF charged first by ESXi, KS file controller resumes the VMHBA right for installation.

• Add the VSA Cluster storage

  Hi all

  I read somewhere that its does not seem possible to upgrade the size of storage for the cluster of VSA in ver1.0? For example, if install us with HDD 6 and thereafter wanted to add another hard drive 2 or more to enlarge the data store, it is not possible?

  It looks like the poster others updated the link to the correct article KB http://kb.vmware.com/kb/2001339

  VSA 1.0 does not support add more storage to a VSA cluster after installation. You cannot add additional hard disks to the ESXi hosts and you cannot add multiple members of the cluster VSA. Make sure that your VSA cluster has enough storage to meet your needs of environment before you install the cluster VSA.

  To increase the capacity of its VSA 1.0, you must re-create the cluster.

  André

• Query - moving from ESX 4.0 (cluster) to ESXi 4.1 (cluster) license

  Hi all

  Am very new to VMware, please bear with me.

  We have in our existing Production cluster, consisting of three (3) 4.0 ESX servers and the intention is to replace them with ESXi 4.1 (U1) (under license).

  The plan should gradually slide each ESX 4.0 Server and install ESXi 4.1 (U1) of an image from HP directly on top.

  No drama it (?), but what about the licenses...

  I have a few questions I have to date not been able to acqurie myself.

  1. With each of the VH in the Production cluster, are we able to move a server in the cluster, upgrade to ESXi 4.1 and go back to the same cluster?
     
     
  2. If NO to question 1, which would be the recommended upgrade path where there is one (1) cluster, three VH (currently ESX 4.0) and we replace with ESXi 4.1 (U1).
     
     We have x 1 vCenter Server Foundation 4 license and three(x3) vShpere4 licenses advanced.
     
     Must these licenses be updated too?

  Am deparate to find answers to these questions.

  Kind regards

  Cameron

  HI - welcome to the community.

  The answer to your question is YES - you can re - allocate your ESX 4.0 license to your hosts updated. the license is generic and can be removed from a host and added to the other using the License Manager.

• Slow iSCSI-IP connection between ESXi and DataCore Virtual storage via 10 Gbit cards

  Hi all

  at the moment, I have test the following configuration:

  Site #1: DELL PowerEdge R730xd with 10 Gbit NIC and DataCore-V DataCore Virtual Storage under ESXi (vSphere 6.0.0 build Standard, 3380124)

  Site #2: Apple MacPro6, 1 with 10 Gbit NIC and ESXi (6.0.0 vSphere Standard, build of 3380124)

  DataCore # 1 server has a disk via iSCSI to ESXi on #2. The connection is running. Up here, so good, but for example when I start a Storage vMotion on #2 of local SSD on the iSCSI disk, speed is exactly 1 Gbps. interesting is that the speed increase when I start a second Storage vMotion and still when I start a third Storage vMotion etc. This behavior is clearly visible in my attached screenshot.

  To me that sounds like to it no matter what iSCSI-IP connection is limited to 1 Gbps.

  
  

  All the components used are certified VMware.
  

  Any ideas that I can check for this problem?

  Thank you very much

  Migo

  The reason for this behavior is that the MacPro6, 1 has two interfaces of iSCSI software that points to a DataCore frontend. It is not allowed. After you have disabled the second interface of software iSCSI, growth up to full 10 Gbps speed.

• With the help of ESXi 5.5 with storage controller HP DL120 Gen9 (HP H240 FIO active host Bus Adapter)

  Hi guys, I'm new to virtualization, but I couldn't find a solution for this. Feel free to correct my text because I'm not very experienced with this sort of thing.

  Background: I have a couple of servers and the end of the game will be left to create a San and run other systems within this SAN (providing network-level RAID). While in one data center I could decides to make a RAID at the level of the material in addition to RAID level network, now I want to save money on storage for this test so I want to do simple split disks (RAID/JBOD) at the hardware level. Because of the OS, we will virtualize later we use ESXi 5.5, 6.0 not.

  In fact, I had a small server supermicro I already installed ESXi 5.5 on that doesn't have lots of storage which will be the 3rd Member voting left.

  So I put the 2 servers (HP ProLiant DL120 Gen9 E5-2630v3 8 GB-R H240 8SFF 550W PS entry Server (777425-B21)) and I went into the BIOS/CMOS settings mode AHCI Mode smart-table (I don't remember the wording of it, I'm not in front of the machine). Then I went in the smart supply and went to the intelligent storage administrator part and I had to select "disable the RAID", or something like that. After the reboot, I went back and now my two drives appear as "Unassigned" which seemed reasonable to me. I tried to see if I could 'assign' but in mode no RAID, there is no means to assign what whatsoever because the paintings exist not primarily in mode non-RAID. I was not sure if there is a way to "initialize" them or something like that, but I couldn't find the parameters like this. My hope was that a BONE would now see these drives natively as a simple readers without the layer of abstraction to a storage controller.

  This does not work and when I run ESXi 5.5 from a USB it will boot, but when it gets to the part where you are supposed to select the ESXi installation disc on it only shows the USB itself and none of my SSD.

  Does anyone know how to configure the adapter HBA H240 with ESXi 5.5? I could really use some help from someone who has done this before.

  Thanks for any help!

  I thought her guy after a few hours of playing with it. I had to pull on the site of HP storage controller driver and group with the ISO (I used experience before VMware: ESXi-Customizer). After having done that, I am sure that AHCI (instead of HP Dynamic Smart Array RAID) has been activated (in the configuration of the BIOS) and disabled by RAID in the HPSSA (intelligent storage administrator). Then, I could see the SSD in the ESXi 5.5.

  Jürgen Vervoort, ESXi 5.5 does not recognize the SSD when I had the active RAID and configured 1 table for each disk (make an effective JBOD). I also tried a single RAID 0 array with two SSDS inside and ESXi does not always detect them. I think that the underlying issue is that the driver is not supported natively by 5.5 ESXi. Right now I'm sure that if I went and configured RAID this would work because the storage controller driver is loaded in ESXi.

  In any case, I hope this will help others with the same issues.

  -GNS

• The upgrade to ESXi 4.1 with storage iSCSI software to ESXi 5.5

  I intend to upgrade ESXi 4.1 with which I have attached to ESXi 5.5 iSCSI software storage

  I've updated all my guests who were on the SAN storage with no problems.

  I would like to know that if it there's nothing I should take care before I update the host connected iSCSI to ESXi 5.5, as for the hosts with SAN attached storage I made to remove the cables of SAN before upgrading the host.

  Also, if all known problems, you will be informed during the upgrade to ESXi 4.1 to ESXi 5.5 with iSCSI Software storage, please let me know?

  If there is no different process to upgrade coz in ESXi 4.1 I do not see this link ports of iSCSI vmkernel ports software iSCSI but I know in ESXi5.5 we have to or I just launch a procedure of standard upgrade via the Update Manager and everything will be taken care?

  Thanks in advance

  With ESXi prior to version 5, linking ports had to be done via command line. However, if it has been configured correctly, you should be able to upgrade to ESXi 5.5 (assuming that the host has not been previously updated since version 3). BTW. the last time that I disconnected the host of storage for an upgrade has been with ESX 3.0.

  André

• VSA 5.5 warning increase VSA Cluster storage capacity - at a standstill

  I work on a VSA cluster to increase the storage capacity, but have hit a snag.

  The wizard of storage increase all the SBA has traveled each off, expanded the size of storage on local server data warehouses and looked like there finish but got stuck in this 'warning' and does not increase the actual sizes of VSA data store.

  "Increase storage caution: finished the VMDK extension and waited 300 seconds for storage entities to come online." Please stop i/o to data AUV for the increase in storage warehouses continue. »

  I have the opportunity to literally close all VM to stop all i/o over the weekend, but he didn't need to take a breakdown to make this work. Is it possible to do the work to finish?

  I'm not too entrust all e/s was arrested, would take right up and finishing, so looking to see if there are other options.

  Anyone running something similar or have ideas on how to help (services to bounce, if it is safe, etc.)?

  Just an update:

  After spending some time with the technical support of VMware, we determined how fast was 'clean' and involved no resolution and window of failure of the whole environment was just rebuild the ASB. Fundamental cause was never determined, but he questions when fsck was the race, if possible corruption any.

  I spent the time to move the virtual machine to local disk space, shoot the ASB and rebuild and it seems OK. However, an increase in storage has been attempted not again.

• Storage path details power Cli need script

  Hi, I need output to below command in excel as a script file unique powercli someone help me

  1 esxcfg-mpath - l

  2 list of esxcli storage base path

  3 list of nmp esxcli storage device

  Try like this

  & {Get-VMhost | %{}

  $esxcli = get-esxcli - VMHost $_

  $esxcli.storage.core.path.list)

  }} | Export-Csv-path c:\test.csv

• raw device mapping partition ESXi 5.0 virtual storage can be a snapshot?

  ESXI version is 5.0, storage EMC CX-480.

  A virtual machine to map a raw partition of the material, the virtual function cannot be cloned or instant?

  Thank you!

  Hello and welcome to the communities.

  See http://kb.vmware.com/kb/1005241 for all the details here.