VSA 5.5: Storage increase VSA Cluster fails

Similar Questions

• 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.

• 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é

• Cannot create the VSA cluster: Cluster subnet is invalid. Should not be "network address".

  Hello world!  I had two questions on a configuration current VSA that I'm doing for a client.  Installation of urban contaminated sites brownfield version 5.1.1 = Live, running Virtual machines.     Have everything configured, I'm facing 2 problems that may be a common issue throughout the community.

  1. in the configuration of the cluster initial when you are ready to configure the drives of VSA, the wipeout disc around or just what has been configured space wise. My guess is he running virtual machines on the local data store that it will not write on this part but still format how much disk space has been used.

  2. I received, during the vsa cluster configuration, the error message:

  Cannot create the VSA cluster: Cluster 192.168.12.0 subnet is invalid. Must not be 192.168.12.0

  Now, I saw the article on what it could probably be.  The gateway appears and is correct.  The problem is that I know that the default gateway is not the ping requests.  I corrected it but have not begun installation because of the question #1 above.  Since the gateway is now who responded, what would be the possible resolution.  Thanks in advance to all those who support!

  Hey Nate,

  You're right about the behavior of the cluster wizard.  It does not consume space and leave the space used by the existing virtual machines.  Once that adjust you network settings (an adresse.0 may be the entry door?)  You should be able to proceed with the creation of cluster.

  IKE

• 5.1 VSA running vCenter and VSA cluster service

  I read that you can run in 5.1 VSA vCenter who is also true on the VSA cluster service?

  It seems that you can accomplish # 2 more easily.  You can simply

  1. Stop server old VCS
  2. Install the VCS on the new host application (without first adding the old address of VCS)
  3. Run "Reconfigure the network" in the VSA Manager, change address VCS to the host of the new address.

• Addition of storage SAN to Cluster

  Hey, Im new to VMWare, so I apologize if this seems to be a silly question to some.

  I've got ESX 4.1 in a cluster host, and the hosts are connected to my network SAN.  I can add storage through each host and to create a store of data, but it shows as a local data store, which I assume means don't get no HA for VMs on this LUN.

  How can I add the storage to the cluster, so that it is available for all guests?

  Thank you.

  Anton way described, it is how it works - if the logic unit number on your San is presented to each host that it prove - I have never create a cluster with just one host so I can't talk about that how it displays in the client vSphere - the way that I would check is open the configuration for your host tab and check the storage adapters and if the number Logic unit is hsowing upwards under the FC HBA than it is on the SAN.

  Since there is no data on the LUN I would go ahead and expose him to another host - the host doesn't have to make part of the cluster for it - and see if changes in the description.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Storage shared between cluster hosts

  Hello

  I have a number of hosts managed under a VC server clusters. I want to downgrade the ESX 3.5 cluster and spend all my virtual machines to my vSphere cluster. I intend to move the storage currently used by ESX 3.5 clusters as well.

  Is this OK (or supported) or even possible for me to do the following?

  1. attach the storage used by the cluster cluster vSphere ESX 3.5 (so it is folded in TWO clusters).

  2. the servers from ESX3.5 to vSphere vMotion cluster cluster.

  3. turn off the cluster of ESX 3.5.

  I guess it boils down to two questions.

  1. can you be shared between host cluster storage two?

  2. If you can, is it possible to vMotion between cluster hosts, assuming that all the vMotion compatibility checks are successful?

  If the above is not possible, I'm guessing that a V2V of VMS ESX 3.5 would be the way to go, and I have to find new storage for the cluster of vSphere.

  Thank you

  G

  Hello

  If you have a SAN vSphere-taking in charge, so there is no problem.

  According to the CRA on your 3.5/vSphere ESX CPU hosts, you might have problems with storage vmotion/vmotion. One way would be to enable CVS, however requiring all virtual machines to be powered off.

  But present the LUN 3.5 4.x guests and make a svmotion is not a problem if you have taken care of storage. (www.vmware.com/go/hcl).

  Then you can just vmotion (if you do not have CPU incompatibility) virtual machines to new hosts, or stop and move.

  VCP3/VCP4/VSP/VTSP/MCTS: Virtualization

• VSA cluster host to have the motherboard replaced including integrated NIC. The traps?

  Hello

  One of the hosts of our cluster is to have the motherboard replaced on Monday. The fault is the idrac, the host is always more or less of work and remained in production until then

  I fear that the network interfaces integrated on MB are used for the VSA and HA clustering will be modified. What I have to do preparatory work with regard to this, or any config after swap before returning the system back into production after the swap?

  We have 5.1 VSA running on Esxi 5.5

  Thank you

  PIP.

  Ok

  VMware back advising me that as long as the replacement warranty is a Board of Directors of the specification the same then there is no problem and no post necessary config replacement.

  Edge arrived yesterday and everything worked beautifully after the swap. The only thing I had to do was to connect the ports I had put in place previously.

  Thank you

• Bay of cluster fails to initialize constantly

  I have a program where I have a table of cluster that enters a while loop like a shift register, and then is then indexed in a loop for to act on each item individually.  To do this, the Bay of cluster must be initialized before the while loop, otherwise an array of length zero is indexed, preventing the for loop execution and an empty array is sent for the shift register to start over the mess.  My problem is that the table does not initialize whenever I run the program, leading to repeated failure I have just described.  This issue is particularly worrying because of its inconsistent nature.  To save you the headache to interpret my entire code, I have summarized the situation in the attached example.  This example seems to work properly, adding to my frustration.  Is there a fundamental flaw in this design that could become more visible in a code more complex?

  After further analysis, I found my problem.  In my program, I have several tables that are all indexed to the nested for loop.  While the Bay of cluster attached to a registry change perpetuates the error, a different picture suffers from a race condition that triggers the error.  During the first iteration, this table might have length zero, preventing execution loop and causing the cluster Bay correctly initialized in the shift register with a length of zero.  In troubleshooting, the obvious symptom was the Bay of empty cluster but the cause was elsewhere.  Thanks for your comments.

• Registry HFM application servers / Cluster failed

  Hello

  I was setup HFM and was able to set up all but one - "registry Application servers / Cluster. Version 11.1.2.1

  When I looked at the newspapers, the warning I see is "unable to save server XXXXX: 1553 IDispatch error."

  All HFM including Web services are in the same server. Is based on another server.

  Thanks in advance,

  AJ

  Hi AJ,.

  Please cross check if Instance Oracle (folder user_projects) is on a shared drive and the user permissions are correctly set up to access. Best practice is to install on the local disks.

  In order to reconfigure the Oracle EPM Instance on a local drive, follow these steps:

  1. Launch the EPM system (located in % HYPERION_HOME%\common\config\11.1.2.0\configtool.bat)
  2. On the 'Oracle Instance' page, select 'Edit an existing Instance of Oracle EMP'
  3. Change the path of "Home Directory for EMP Instances Oracle" on a local disk using the 'Browse' button
  4. On the "Configuration" page, select financial management-> register application server / Cluster
  5. Click next
  6. Select the Cluster / Server to be registered
  7. Click next
  8. Click Next again.

  Kind regards

  Madhu.

• VSA 5.5.1 stuck in 'increase in storage VSA.

  Hello community,

  Another question about VSA 5.5.1.

  Since it's for testing purposes, I'd not too spend time in it.

  The VSA Assistant to increase storage capacity stucks VSA in (last) step 'increase in storage VSA. vSphere Client and Web Client with the same problem, restart of vCenter Server (reboot) does not help.

  VSA is configured in the configuration of brownfield by using 2 host with the local data store with the Cluster Service on a third host/VM. VSA-store data is always accessible and failover works also.

  Found a similar problem in this forum, but no detailed response: 5.5 VSA: increase the storage capacity of Cluster VSA fails

  Concerning

  Recreate the data center solved the problem.

  Steps to follow:

  -create a new data center

  -move the hosts in the new data center

  -remove the old data center

  -Rename the new Datacenter original name

  -VSA Manager is now showing initial dialogue

• VSA installed, you cannot create the cluster "VSA unavailable Cluster"

  Hi guys

  At home, I have 2 servers ESXi with a vCenter 5 virtual running on one of these hosts (I know this is not supported or the best practice, because failure of the host with vCenter, only remains of the hosts and it doesn't have the majority because of the loss of VSA service and a host). However, I think that I have an error or an obstacle not related to this.

  Also, I plan on cold migration (first storage vMotion, deleting the VM of the inventory, adding to another host) the vCenter, so this problem should be addressed in the near future...

  Currently, I have installed the Manager of VSA on the vCenter server and when I open on my client vSphere client, I get the VSA Manager tab but when I open it, it says "Loading" and then a Flash-style/VMware View management console style dialog box pops up saying "the VSA cluster is unavailable: VC Session creation has failed." with a title "VSA Cluster unavailable."

  What I am doing wrong? I can't find much documentation on the installation of a VSA, so a little help would be appreciated by a Belgian engineer VMware junior and learning

  I have enough available storage. One of the hosts I have a 160 GB SSD and 2 TB of available HARD drive, on the other a 80 GB SSD and a volume of 320GB RAID 1 presented by a LSI Logic Controller. All of them are mounted...

  VSA Manager has the same error as reported before

  2011-12-12 16:29:28, 141 338 [SessionService] [http - 127.0.0.1 - 8080-6] ERROR - cannot get the link of the extension
  org. Apache.Axis2.AxisFault: cantTunnel00: 192.168.8.23:80 HTTP/1.1 404 Not Found

  Your screenshot also indicated that vCenter is installed on port 8081. It's conssistent with the PuTTY test done before. You probably have something else listening on port 80. VSA 1.0 release requires that vCenter is Installer to the default HTTP port, port 80, which should be fixed in later versions.

• VSA configuration and storage before installation of VSA on ESXi

  Is someone can you please remind me how storage should be configured on ESXi until I'll start building VSA?

  VSA is use the local storage of the ESXi hosts.  Should I use local data warehouses already formatted vmfs or raw devices (volumes) and formats?

  Is it true, that, before the installation of VSA, you can no more data VMFS (local) 1 store? If so, this means that VSA will use (use) all available space on the Local data store on the left after installing ESXi (if I'm installing ESXi on local DS as well)?

  Thank you very much!

  VSA manager uses the data store local vmfs to create VSA data warehouses. During the creation of the VSA cluster, you can specify the size of the VSA data store. For example if you have the local data store of 500 GB, you can build cluster VSA using 100 GB of space, so you can have several virtual machines on VSA datastore and a few virtual machines on the local data store. There is an option to extend the VSA data store after creation.

• VSA 5.1 storage planning

  We plan 5.1 VSA deployment on two servers ML350p Gen8 with two cages of HARD drive: HDD first cage 6 x 600 GB 15K RAID 10 for storage, second cage 6 x 2 TB SAS 7.2 K RAID10 for VM shared cluster VSA and backup.

  Here, I have several questions for the deployment of VSA 5.1:

  1. Can use us first cage to HARD drive for storage of shared cluster VSA, second cage of disk for backup and standalone VM?
     
  2. Install VMware ESXi 5.1 on 5.1 VSA deployment USB flash is a security?
     
  3. What happens with ESXI VSA cluster host if USB flash goes down? After changing the USB failure it is necessary to reinstall ESXI?
     

  1. If you build a VMFS on the first HARD drive cage, but do not format disks in the 2nd cage, the ASB should only use this cage VMFS 1 for the device. Once AUV is deployed, you can format the second cage as an another VMFS and use it as local. * WARNING - I tried it myself, but I think that's how it should work *.

  2. my understanding is that used in making ESXi supported cluster VSA same standard as ESXi host deployment mechanisms. It would be good to check with the technical support, however.

  3. There is a procedure of node to replace you need to run after installing ESXi. Refer to the documentation on how to do it.

  I invite you to spend some time trials 1 & 3. I do not know 1 will work, but have not tried. Node to replace in article 3 is a proven procedure, but it would be good to be familiar with the steps rather than try them for the first time at 03:00 on Sunday night! ;-)

  HTH

  Cormac

• Recovery of the cluster VSA problems

  Hello

  A power outage left our vcenter server machine somehow a mess (or at least the DB used by vcenter is)

  So, given my complete lack of knowledge DBA and try to get things back running, I went to control panel and uninstalled) 1 vcenter, 2) unit of vsa, 3) the vcenter client and 4) sqserverl-express from Microsoft of the machine software. I assumed that to uninstall this way, any possible trace of the installation must be deleted or substituted at least when reinstalling. (can someone please confirm/deny this hypothesis, thanks!)

  I continued to reinstall all the software and then tried the recovery procedure 'retrieve an existing Cluster of VSA", as described in the documentation centre 5 vsphere.

  At first glance, this seems to work.

  But now it seems that the recovery has not reproduced the "VSA HA Cluster" self, but simple imported all VM directly under the recreated VSA Datacenter. If I look at the 0 VSA, VSA-1 and VSA-2 VMs now, then the vSphere HA protection seems State "n/a".

  Also two other virtual machines that I had installed under the cluster work but aren't protected HA anymore.

  Trying to create a new cluster fails because my ESX 3 hosts are already known to the system under the data center...

  I did something wrong during the recovery and is it possible to repair the damage, or am I better take a return of my 2 virtual machines (using standalone converter tool?) and simply reinstall my 3 servers ESX and vcenter again, as I described at the beginning of this message?

  Thanks for any help on this.

  Hi David,

  At this point, the best thing to do is probably to create the HA Cluster yourself. The steps are not too complex:

  1. right-click on the domain controller where the hosts/vms resident => New Cluster...

  2. Enter the name

  3. check 'Turn on vSphere HA' (you could also turn on vSphere DRS if you have the useful, likely license)

  4 @ VM Options:

  -Activate the tracking host

  -Enable admission control

  -Set the control strategy for admission to 33 percent of the cluster resounces reserved as space failover capability (50% if you have a 2 cluster nodes)

  -Click next and the VM Restart priority average value and response of isolation to "shut down the computer.

  5 @ VM followed, define "VM Monitoring" to "Followed only VM" and "control of sensitivity to the average value.

  6 @ VMware EVC window, I would say that allows EVC (but this is not necessary). This will ensure that all hosts in your cluster are able to Vmotion. Please, make the selections of approirate (v.s. intel amd and so on) and then proceed.

  7 @ location of VM swap file, please select 'store the swap file in the same directory as the virtual machine (recommended).

  8 @ ready to fill, review your selections and click "Finish".

  9. with the created Cluster HA, just drag and drop your ESXi in the cluster hosts.

  10. go back into the settings of Cluster HA. Right-click on the cluster-online 'change settings '.

  -Under vSphere HA-online virtual Machien Options, please disable VM priority Restart for all virtual machines of VSA

  That's all. You should be all set.

  FYI: @ step 9, if you can't drag and drop your ESXi host, and he complains about your CVS settings, you can go into the HA Cluster settings and change the CVS options as your hosts will be allowed in the cluster.

  I hope that this solves the problem for you. If you have any other questions, feel free to ask.