rule of the VM host affinity Vcloud managed cluster.

Similar Questions

• Manual VMotion circumvents the rules of the DRS anti-Affinity

  Hello

  just a really Basic... I know DRS rests on the idea that he leans on the cluster and then resources place virtual machines... BUT, if you configure a rule anti-xxx to say VM1 cannot be kept the same host that VM2 - can I still manually vMotion VM1 to the same host only a VM02 on?

  OK... Let me rephrase that. After having just... I asked myself why I cannot vmotion 2 virtual machines to be on the same host, even if there is an anti-home rule?

  My hypothesis is one of the following:

  1. I have not configured the anti-home rule correctly, or

  2 DRS is a retrospective resource, monitoring tool. so he will ignore my action, but when it checks the environment, it will then search the vm 2 is on the same host and then applies the rule of the anti-xxx.

  Let me know that if you can...

  Thank you

  Aaron

  Welcome to the community - Yes, you can manually vmotion a virtual machine that would violate the rule of the affinity of the DRS but if you DRS in partially or entirely automatice mode it will vmotion virtual machine don't not to violate the anti-home rule.

• Rule of the Tomcat host State

  Alarms Tomcat host unrecoverable state and Normal are now show the following:

  "'UnclusteredTomcatHosts' / 'localhost'": Tomcat host unrecoverable state "and"Tomcat host 'localhost' in 'UnclusteredTomcatHosts' cannot run. " "Please use the following URL for details of the alarm:

  "UnclusteredTomcatHosts/localhost: host Tomcat Normal State" and "the State of Tomcat host 'localhost' in 'UnclusteredTomcatHosts' is normal."

  I tried to figure out where the variable is bad. Here's my setup.

  Additional accessories:

  • screenshot. PNG
  • screen shot1. PNG

  That's what I was afraid of, all servers exist as localhost.

  Check the release notes http://edocs.quest.com/foglight/562/files/CartridgeForJavaEE_574_ReleaseNotes.html it seems that this has been officially corrected in version 5.7.4 but I see that some of your agents are 5.7.1 and 5.7.3 so I'm not 100% sure what version you are using on your FMS and what are your upgrade delays.

  The release notes mention the name of the server in the server.xml file, you can try to set this value in the file server.xml for one of your test/dev servers, restart the JAVA virtual machine and see if it does the trick (if it isn't that, to change the name of the server in the file server.xml can be a good solution in the meantime.

  Article corrected one thing, it seems that the version is optional and that there is a lot of flexibility with the settings.

  Golan

• DRS Rule for Host affinity check names of datatore that they match to the hosts

  DRSRules - list of host affinity rules

  Host affinity rules

  Cluster	Activated	Name	Solidarity	VM	Host of the rule	Running
  Cluster-SA1	True	Cluster2-SA1-VMsHosts	Fake	SMV - SA1	SA1	sa1_host3
  Cluster-SB2	True	CLUSTER1-SB2-VMsHosts	Fake	SMV - SB2	SB2	sb2_host2

  This module of vCheck will show me if one of my virtual machines are not running according to the rules, but I want to look deeper.

  DRS Rule for Host affinity check names of datatore that they match to the hosts

  Our guests all start with three characters make the difference between SiteA1 and SiteB1, that is sa1host1 sa1host2... sa1host9 and sb2host1, sb2host2, sb2host9, etc.

  Our warehouses are the names "sa1_exch01", "sa1_sql_01", sa1_data_01"for all data stores that are found on the Site1.  While the warehouses of data named 'sb2_exch01', 'sb2_sql_01', sb2_data_01' for all data stores that are found on the Site2.

  Can help you with a script that will check all virtual machines on the hosts on Site1 and report those who have warehouses of data does begin with 'sa1' and similarly all virtual machines on the hosts on the Site2 but give report of those who have warehouses of data that do not begin with "sb2.

  See you soon

  KC

  Try something like this

  $vms = Get-View -ViewType VirtualMachine -Property Name,Datastore,"Runtime.Host"
  
  foreach($vm in $vms){    $esx = Get-View $vm.Runtime.Host -Property Name    $ds = Get-View $vm.Datastore -Property Name    if($ds | where {$_.Name.Substring(0,3) -notmatch $esx.Name.Substring(0,3)}){        $vm | Select Name,            @{N="Site";E={if($esx.Name.Substring(0,3) -eq "sa1"){"SiteA1"}else{"SiteB1"}}},            @{N="Host";E={$esx.Name.Split('.')[0]}},            @{N="DS";E={[string]::Join(',',($ds | %{$_.Name}))}}    }}
  

  It should list all the virtual machines that do not follow the rule.

• SQL 2012 still on the use of affinity rules

  Hey guys,.

  I use SQL 2012 alwaya time on in a virtual, but so far, it is not configured as best practices and environment I wanted to change that.

  At the moment I have no DRS rules in place so it can happen that two virtual machines running on the same host and it's something I want to avoid.

  However, my big problem is that I only got a SQL license for two hypervisors and best practices talked about four hosts who are needed to achieve my goal.

  Here is what I intend to implement:

  -Affinity rule machine virtual-VM to separate two virtual machines

  -Affinity VM host rule which VM1 MUST run on ESX1

  -Affinity VM host rule that VM2 MUST run on ESX2

  This configuration is a good idea or could / should I do something different?

  What I found that all the features how for example the evacuation and HA should still work?

  There are many more ESX servers in this group and they will be used in the case of an outtage, right?

  Also there is a dev environment that looks the same. I could include the hosts in the same VM-Host affinity rules or should I create new ones?

  BTW. I am using vCenter and ESX 5.5.0.

  Thank you very much!

  See you soon

  Nicolai

  Affinity rules those you intend to sense. These rules will not be those virtual machines to be on the same host most of the time.

  Note:

  1 rule of VM host is configured as "SHOULD", in extreme cases, DRS can break these rules. However, in the next invocation of DRS, DRS will try to resolve the violations.

  2. Note that: when you keep either the host in maintenance (ESX1 or ESX2) mode, you must manually migrate the VM to another host due to the virtual-VM anti rule machine affinity. DRS even in full auto mode, VM will not be migrated automatically. This will apply only if there are only 2 host in the cluster.

  3. Yes, HA should well with that: however HA is not aware of the rules 'EXPECTED' and in the case of host failure it can not respect 'SHOULD' rule.

  4 rule anti-affinite VM - VM can be sensitized HA using the advanced option. Let me know if you want to help with that.

  5. Yes, failure of other hosts in the cluster will be used but please updated on impact due to rules & licenses.

  6. "There is also an environment-dev which looks the same." I did not follow what exactly you mean here:

  7 migration threshold settings DRS is also important.

  8 DRS gives priority to the prevention of violations of anti-affinity rules machine virtual-VM that violations of rules of affinity. (it's just for your info.)

  Nevertheless,.

  1. If ESX1 falls down or affinity rule VM host that VM1 MUST run on ESX1 gets violated: VM1 can be migrated to other hosts in the cluster. As you have no licenses (more than 2) SQL, how it would be dealt with (I'm not very updated on the SQL licenses)

  2 point above applies to the second rule of VM HOST as well.

• VShield service Manager installation and vShield app to the same host ESXi

  Hello, I'm planning on vCloud Director assessment in a laboratory with only a single ESXi host.  When I try to install the app vShield service I get the following warning: do not install on a host or a cluster where the VC or the vShield Manager resides. This can cause network problems. The following IP address must be a unique IP address assigned to this unit of App vShield. Please do not use an IP address that is assigned to another machine, including the VC, vShield Manager or any ESX host. Using an incorrect IP address you will need to uninstall and reinstall App vShield on this host. My question is: is it is absolutely impossible to install vShield manager on the same host ESXi as the vShield Manager resides?  Or is it just a bad practice?  What are the ramifications of installing?

  It is a general practice to separate management and resources. What you see is just a warning. When there are very fewer resources available you can do. Make sure that you exclude from the required VM by referring to this post

  http://www.yellow-bricks.com/2012/03/17/excluding-your-vCenter-server-from-VShield-app-protection/

• How to configure Enterprise Manager Database Control (MCCD) to make it work on 2 servers (primary and standby) work according to the rules of the DG

  Hello everyone I use Oracle Database EE 11.2.0.4 with DG.

  In these cases, I need to get Enterprise Manager Database Control running against DB with no CARS and no DG I do the following:

  I have SQLPLUS logon as user SYS or SYSTEM and drop the account sysman and business objects:

  DECLARE

  CURSOR c1 IS

  SELECT master, synonym_name name

  OF dba_synonyms

  WHERE table_owner = "SYSMAN";

  BEGIN

  TO r1 c1 LOOP

  IF r1.owner = "PUBLIC" THEN

  RUN IMMEDIATELY "DROP PUBLIC SYNONYM ' |" R1. Name;

  ON THE OTHER

  RUN IMMEDIATELY "DROP SYNONYM ' |" R1. Owner: '. ' || R1. Name;

  END IF;

  END LOOP;

  END;

  /

  Mgmt_view DROP USER CASCADE;

  /

  DROP ROLE mgmt_user;

  /

  Sysman DROP USER CASCADE;

  /

  After that, I run

  EMCA - config dbcontrol db-rest recreate

  But what do I do in case I have 2 servers (primary and standby) work according to the rules of the DG?

  Hello

  It is not possible to monitor and administer a basic physical or logical standby, IE using Enterprise Manager Database Control Data Guard.  This is mainly due to the fact that Database Control is designed to monitor the 1-database and an environment Data Guard, by definition, includes more than 1 database.

  If you attempt to run emca against a database of pending, you will get an error like (i.e. ORA-01219: database is not open).

  Of course, database Control, can be used to monitor the current main database (with no capacity to administer or control Data Guard related features).  In such a case, failover Database Control needs to be reconfigured to run on the new primary database using the commands described in detail in Note 278100.1 how to remove, create and recreate DB Control In A Database, section c. recreate/ReConfig DB control, Option 2 10 g. recreate the control DB Configuration files and repository.

  Enterprise Manager Grid Control or Cloud control provides the functionality for display, monitor, and administer the primary and standby databases in a Data Guard configuration.

  Reference: It is Possible to configure the database for a logical or physical Standby Database command? (Doc ID 315116.1)

  You can effectively use EM 12 c cloud control to monitor and manager ensures DB

  Ref to the link for more details below

  Set up and manage to Oracle Data Guard with Oracle Enterprise Manager Cloud control 12 c

  Kind regards

  Rahul

• Update Manager upgrade of the ESXi host that he is running in a virtual machine does

  That is the question.  Here is some information.  We were a completely virtualized environment for several years.  2 guests ESXi collocated 5.5 to different data centers connected of course by a VPN site-to site.  The VPN itself is provided by VMs and vCenter runs in a VM to one of the sites as Update Manager is to proceed with installing it. If the vCenter and/or VPN VMs are down, we have a very cool backup method to gain access to and manage ESXi and its console.   Some of you who read the rest of the present will be tempted to suggest to architecting our environment differently, but we are very pleased with the way it is thank you very much :-)  Appreciate all the answers but really just responded to this specific question.

  The reason why we want to Update Manager is really just to be able to upgrade easily ESXi in the future without enter in the console and the execution of orders, etc.  I realize the documentation and blogs on this topic that ESXi may need to go into maintenance mode and stop the virtual machines running on it (not a cluster if no migration) how ESXi is lose connection to the Update Manager (if the remote host) or a stop Update Manager (if the local host).  So the question is, is that the process of updating managed by Update Manager an atomic operation at that crucial moment or a sequence of operations depend on continuous connectivity and control of Update Manager.  Ddoes ESXi, then perform the upgrade and restart regardless - that would be great - or he'll just stand there in maintenance mode to learn more about disconnected now / stop Manager update pending.

  Your answers are greatly appreciated.

  Please, tell me if I understand you:

  Ask yourself if you can upgrade the host running Update Manager VM? And you cannot migrate the virtual to another host machine because there is no cluster in place and no shared storage?

  If your answer is YES to both questions, I can tell you that you cannot use Update Manager, since you must put your host in Maintenance Mode and therefore you will need to stop all virtual machines running, including the VM Manager Update.

• Manager Update on the VMware host updated

  I have two VMware hosts with vCenterServer running in a virtual machine on a host.  Manager of update is loaded and it works very well.

  I would like to be updated (install patches) the host who has VCenterServer on this.  Technical support said that he could not tell me that it was OK to make a staging of the update with UpdateManager on the host.  My plan was to push updates on, then use vSphere client to manually restart the host that is home to the VCenterServer.  It makes sense that it would work, but the tech told me to create a second vCenterServer on the other host.  It's a lot of work.

  Anyone has successfully done what I was planning to do?  I look at UpdateManager patch the first host, it seems that Update Manager pushes updates to the host, and then goes into maintenance mode and restarts.  Why not push updates, then restart manually?

  Any other suggestions or ways to do from the console?

  You can update the hosts through command-line if you stop vcenter.

  http://blogs.VMware.com/vSphere/2012/02/quickest-way-to-patch-an-esxesxi-using-the-command-line.html

• vCenter Server and Manager on the same virtual machine and on the same host ESXi update that they manage

  Hi all

  I have a question to which I did not respond.

  I have an ESXi 5 on Proliant DL380 G7 server host. I want to install vCenter Server and Manager Update on one of the Server 2008 R2 VM on the same host. I know it's possible, but my question is how Update manager will provide updates to the same ESXi host it will run on? The update is applied every time host must spend in maintenance mode and power off the virtual computer running on this subject which means he'll kill VM where vCenter Server and Update Manager is running and the update will fail right?

  Is that possible at all or the VCS and UM such as a virtual computer operating point is updated to other guests if you have them or vMotion as VM to another host when you want to update the VCS and UM host is running?

  Thanks in advance.

  It will not work.  You will need at least two hosts.  This way you can vMotion the vCenter VM to another host.  From there, you can use VUM.  Otherwise, you will need to patch the host as a stand-alone host.

  See below for patching a standalone host

  http://communities.VMware.com/people/vmroyale/blog/2011/09/15/updating-ESXi-5--single-use-esxcli-how-to

• Unable to prepare the host to Vcloud Director

  Hi all

  Hope you guys can help me. I try to install the track of vcloud Director version, and I got most of this work. The problem I have now is that I cannot prepare a host. I installing the server in a cluster, I have no shared but only storage using local disks (wondering if this isn't the problem). I added my vcenter server, which is a virtual machine on a host, but I'm still unable to activate the host for its use.

  I read somewhere on the forums that it must be in maintenance mode, but it does not work. In fact if I do this, the host gets a Red Cross in the available column. On the only host I get an error saying connection refused. The other, they say just can't prepare host.

  Any help would be welcome.

  KettieKop

  You need to meet the prerequisites first, specifically to have active DRS.  For the active DRS on the Cluster of hosts in vCenter, for the DRS, you need to have more than one ESX host AND the shared storage.

  Shared storage is a requirement for vMotion (as the DRS is on your virtual machines for load balancing)

  Several hosts is necessary to allow pools of resources (you need a place to load their balance)

  Once you meet the requirements, then you should be able to view the ESX host, when you try to prepare them for vCloud Director.

  Best regards

  Jon Hemming

• I can't power on a virtual machine (with linked disks) after the addition of new hosts of Lab Manager

  ENVIRONMENT

  -Lab Manager 3 using VC 3.5

  -Initially the 2 hosts in a cluster and managed by LM

  -Added new cluster with 2 new hosts in VC

  -Two bunches pointing to the same NFS storage

  PROBLEM

  -When you try to turn on a computer in new cluster, I get a "requested file" "not found" error

  RESULTS

  -This seems to happen only when creating a virtual machine that has virtual disks of parent; most of our VMS is linked clones

  -When you look at the log file, please see attachment, we found the following:

  It is the location of the new virtual machine in the new host:

  /vmfs/volumes/fabdf38d-beff047d/LMW2K3/2909/002909-T_XP_SP3_32b.VMDK

  When you look at the hard, it points to the parent disk, but it seems that it does not:

  /vmfs/volumes/6586c772-53eee1bb/LMW2K3/2904/002904-T_XP_SP3_32b.VMDK

  Please note th volumen IDS are different and can not get the disc parent of the new machine.

  SOLUTIONS?

  Thank you

  Jose

  You should immediately stop using the new hosts otherwise creating new virtual machines can spoil the vmdk channels. Try http://kb.vmware.com/kb/1005930.

• Best way to manage the accessible host check after restart

  vCO newbie here...

  I'm building a workflow for (a) take an array of clusters, (b) the loop through a cluster and take a picture of the armed forces, (c) using the table of the host, in Maint Mode on first host... run a script, restart (d) check host reconnects and move then to the next host... until all hosts have been completed.  I'm looking for the best way or an example of verification of accessibility of the host and to wait for the host is accessible before you continue.  Any help is greatly appreciated!

  Hello Carlos, you certainly came to the right place for this question vCO is ideal for this kind of thing... I got to play a little before I restart something that resembled what you're asking for is basically a host and wait for it to be reconnected.

  Well, the workflow "Reboot Host" indicates indeed vCenter API to restart a host, but it does not wait for the host to come back to the top, she finished just all right because that's what indicates the API... Therefore, we must introduce a timer to wait a few minutes and to give a chance of him having turned off as part of resetting to the host. Then we check the connectionState of the host to see if it is 'connected' - otherwise, wait a few minutes and repeat the loop until the host is connected again. See example attached workflow. I recommend a MINIMUM of 3 minutes for the wait time. Test this several times in your environment to see what still works for you and adjust as necessary.

• MSSQL server VM cluster should be in the same host or different hosts with RDM

  Could someone me on how to place the code SQL cluster s VM with RDMs in ESXi hosts for advice.

  What is the best practice to place the SQL VM s in ESXi hosts.

  Affinity or an anti-affinite...?

  Appreciated your valuable answers.

  Depends entirely on the use case.

  • 2 MS SQL nodes on the same host to see the availability of the software
  • 2 nodes on different hosts to see the availability of the equipment

  I'd say MS Clusters on the same host (at the time of HA and vSMP FT) are redundant VMware features and represent an increase in management fees. The MS cluster on hosts provide something in addition to what VMware vSphere alone can provide!

• PowerCLi script to check if 2 virtual machines are on the same host

  Hello

  I'm nubby on PowerCLI and I would like to help in the construction of a script.

  The script should check if two virtual machines (named test1 and test2) are running on the same host in a vCenter and send a notification (email), if they do.

  Something similar with affinity / anti-affinite DRS rules (but not through the DRS enabled on vCenter).  My focus is on the affinity. In case this happens, I need vMotion one of them on an another ESXi host(manually or automated).

  What I have done until now is the following:

  Get - VM | Select Name, @{N = 'Cluster'; {E = {Get-Cluster - VM $_}}, '

  @{N = "ESX host"; {E = {Get-VMHost - VM $_}}, '

  @{N = 'vCenter'; E={$_. "(ExtensionData.CLient.ServiceUrl.Split('/') [2]}}, '"

  @{N = "Datastore"; {E = {Get-Datastore - VM $_}} | `

  Export-Csv - NoTypeInformation C:\Scripts\file.csv

  That becomes all the VMS and export a CSV file information:

  Name	Cluster	ESX host	vCenter	Data store
  test2	cluster_test	ESXi_test1	vCenter_test1:443	datastore1
  Test1	cluster_test	ESXi_test1	vCenter_test1:443	datastore1
  For1.local	cluster_test	ESXi_test1	vCenter_test1:443	datastore1
  VM1.local	cluster_test2	ESXi_test2	vCenter_test1:443	datastore1
  VM2.local	cluster_test3	ESXi_test3	vCenter_test1:443	datastore1
  VM31.local	cluster_test3	ESXi_test3	vCenter_test1:443	datastore1

  Thank you.

  Try like this.

  $tgtVM = "test1", "test2".

  Get-VM-name $tgtVM | Group-object - property VMHost | %{

  if($_.) County - gt 1) {}

  $vm = $_. Group | Get-Random

  $esx = $vm. VMHost

  $tgtEsx = get-Cluster - $vm VM | Get-VMHost | where {$_.} Name - not $esx. Name} | Get-Random

  Move-VM - $vm - Destination $tgtEsx VM - confirm: $false

  }

  }