Lab Manager

Similar Questions

• Why move them to the bottom of empty in VMware Lab Manager when you use Firefox 4 +?

  When using Mozilla Firefox 4.0 or later, drop boxes in VMware Lab Manager are populated is more if it is not possible to deploy new virtual machines.

  It turns out that VMware has released a Lab Manager in August (4.0.4) update that resolves this problem. I upgraded to LM 4.0.4 and dropdown lists are now met again.

• VCenter Lab Manager 4.1 Linked mode

  Hello

  What is someone using a vCenter Lab Manager 4 configured in bound mode?  I would like to activate the connected mode, searching for traps that everyone can share.

  Thanks in advance

  No traps.  Bound Mode is independent of Lab Manager.

  Please be aware, Lab Manager works with exactly a vCenter and a data center object inside this vCenter.

  So once you activate the bound mode, you won't see all the resources here.

• vCenter Lab Manager 4.0.4 5?

  I know that there is no support for Lab Manager 4.0.4 and vCenter 5, but it's going to work? Or when it will be supported? I see no reason why there would be a problem if I leave my host ESX 4.1 cluster.

  Has anyone tried this before?

  vCenter 5 + Lab Manager 4.0.4 won't work.  There, questions that I saw people who did the upgrade without checking compatibility.  Since Lab Manager is abandoned, I'm not expecting a major update to support vCenter 5.0.

  One option is to divide it into 2 environments... 1 specially for vCenter to LabManager and then a 2nd which will vCenter 5 which is a new installation you can grow out.

  Best regards

  Jon Hemming

• Lab Manager 4 will not release the license after the removal of host.

  Hey there,

  I am running Lab Manager 4 in my infrastructure.  I recently added a lot of CPU 2 and licensed.  Shortly after, I removed the host of Lab Manager, but he has not published the 2CPUs of licensing - which means that I am able to use my license 2CPU part to add new hosts.

  No idea how I can get the license for free?

  Thank you!

  You must "unprepare" this ESX host in the laboratory Manager.

  The 'prepare' function consumes your license, and similarly "unprepare" frees.

  This ESX host appears in the overall organization > resources > Hosts?

  Best regards

  Jon Hemming

• Configuration Lab Manager - error: not supported operating system

  I try to install vCenter Lab Manager 4.0.4.1406 but I get error: unsupported on OS when I run the Setup file.

  It is Windows Server 2008 R2 x 64 on an ESXi 5.0 machine.

  IIS and the .net Framework 4.0 is installed.

  Uninstalled AD.

  Looks like all the system requirements are met, but I am still getting the same error (and no more detailed error message then not supported operating system)

  
  

  I don "t think that Windows 2008 R2 is supported for Lab Manager server, only Windows 2003 and Windows 2008 are mentioned in the Manual of Installation.

  For guests, it has made experimental support for Windows 7 and Windows 2008 R2.

• Lab Manager and VMFS 5?

  I know Lab Manager only is not supported in vSphere 5 but I have a cluster where some hosts run LabManager.  I've updated vCenter and LabManager still works very well.  I want to spend the VMFS, so there are 2 possible scenarios

  -Put level all VMFS volumes, will be this LM break?

  -Upgrade only the LUNS than regular machinery of the host and leave the LUNS that are dedicated to LM as VMFS3.  This will cause any type of conflict?

  Hello.

  I don't think that you can actually get these 5 VMFS volumes, as all the guests, access to the database must support VMFS-5. This means that only 5 ESXi hosts will work.

  Good luck!

• vCenter 4.1 update level & Lab Manager

  Hello

  I upgraded to vcenter 4.1 and have begun upgrading our 4.1 esx host.  We have a Lab Manager cluster and I got to spend 2 to 3 hosts for ESX4.1... Currently, all Lab manager VMs are running on the ESX host 4.0 remaining in the cluster of Lab Manager.  I'm unable to migrate virtual machines to host 4.0 to ESX 4.1 two other guests offshore in this cluster to improve this host to esx 4.1.  When I select a VM to migrate, I get the following after error message select a host ESX4.1:

  "A general system error.  The virtual machine requires labmanagerhostserver/system.service.vmware.vsla labmanagerhostserver service, which is not available on this host "."

  Before the upgrade to vcenter 4.1, Director of the laboratory has been upgraded to 4.0.2

  Any hellp to resolve the above error is much appreciated.

  Sorry to hear that.

  I myself have strange problems with 4.1.

  I have stopped using 4.1 at the moment and re - install 4.0 on all new blades instead.

• Storage for Lab Manager

  My client needs storage for Lab Manager running on 100 servers. Is it recommended to use the NAS or SAN for Lab Manager running and what type of e/s that you wait for the same thing?

  I did a little bit with storage of LM in recent years.

  I have a development/test environment on LM 600 machine, using 2 Sun 7210 storage devices (is no longer available) on NFS shares. We have 2 links 1 G servile vmKernel traffc as well as links to more vmnetwork, management, etc.  The devices are related to links of 4 x 1 G each.

  I don't know what are the current constraints of LM/ESX, but whenever we revisit the decision 'block vs NAS' we end up selecting NFS (our Sun boxes can present the iSCSI as easily).

  As Jon says, what storage you need certainly depend on your VMS and load.  NOTE: my experience is * NOT * in a production environment, where I am squeezing virtual machines performance.  It's more about the functionality and "adequate" performance (where "adequate" is a measure based on the user experience topic).

  Some things we have learned over the years:

  • IOPS / s are kings, and most of them are entries.  (Written at the moment, I have a few heavy ready operations push me down to about 65 percent.)  I saw > 80% of entries maintained for days.)
  • Latency does not seem as important - VMs run about the same at 10ms latency and latency 250ms NFS NFS.  When latencies above 750ms grows, they will be noticiable users and if they go more than a second over 1000 ms you will begin to see the impact on the guest OSes, especially Solaris x 86.
  • Normal operations don't care about bandwidth - just current execution machines don't even fill a link 1 G
  • Deployment operations * could * start filling to the top of the bandwidth, maybe
  • Betware storm IO.  Often people think the storm IO deployment/boot, but 400 RedHat machines all the kickoff of their 'updatedb' cron job at 04:00 can produce any IO storm as well.  NOTE: IMHO if you buy storage to handle this kind of thing, you're overpaying storage.  I've spread my cron through the night and now can not see on the graphs of storage performance.
  • There is * NOT * a good correlation between guest OS IOPS / s as shown, for example, iostat and PAHO are / s NFS presented to the storage system.  I'm guessing that ESX made a lot of caching.

  Most storage vendors I spoke last year does not seem to find it.  They think in terms of bandwdith and it accelerates with read cache, so unimportant in my environment - I had to push really hard to get sellers to think in the right conditions and some of them really seem out of their depth there.

  I think that this state of mind is important: consider the IOPS / s as you consider CPU: how much should I give to each machine?  How much should I oversubsubscribe?

  Like CPU, a physical machine which IO a lot more available that he needs and you can consolidate - but don't know how.  A physical machine with a pair of 15 k drives RAID1 has about 200 IOPS / s available and readers spend most of time inactive (a bit like the CPU).

  That will boost the machines and when?  Right now I'm on average 9 inputs/outputs by VM, which in my opinion is quite small.  My storage system can go higher under request, but I have enough machines that it is fairly constant.

  In my quest for the perfect storage of LM, I found the usual: good, not expensive or fast, you can choose any two.  How we use LM (lots and lots of shared models) we would really like a unique namespace shared (i.e. 1 data store). I have yet to find the 'perfect' - storage, the Suns are very profitable for the performance and space, but their management takes too much of my time and my 72XX are not expandable - the 74 might be a different experience.  I am currently looking to add some SSD storage, but the ideal configuration would be automated migratino between levels (for example, EMC QUICKLY) and if I bought only from EMC I would triple my cost per VM.

  I talked to people who have a pattern of use of different models that are quite happy on several data stores.  If you can move your load through many warehouses of data then Isilon looks like interesting storage.

  So, in summary:

  • Watch IOPS / s 1st, 2nd and 3rd, then the latency time, then (maybe) bandwidth
  • Manage the budget or the ability of the IOPS / s as you CPU
  • You may not use comments IOPS / s to provide shared storage IOPS / s

  I'm hoping to have a better storage solution in the next 6 months or more.

  --

  Dewey

• Black Lab Manager VM Console under IE

  We start just our use of Lab Manager. Under IE8, windows 7 x 64, the console within EI, or separate window is black.

  Go to full screen displays the virtual machine properly.

  Under Firefox no problem?

  > > What is needed to make IE work?

  Thank you

  Hello

  I had the same problem and found this KB article which helped me to solve it: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020474

  Hope it works.

  Kind regards.

• Shutdown for Lab Manager

  We are conducting a data center power down and I would like to confirm my judgment for Lab Manager procedure:

  Stop order:

  1. Shutdown VMs LM
  2. Virtual routers (for closed configurations) stop by VC
  3. Stop VMwareLM-ServiceVM (by distributed switch) by VC
  4. Stop LM Server (VM, but not running on the ESX host cluster managed LM)
  5. Shutdown LM managed ESX host
  6. Shutdown VC Server

  Boot order:

  1. Power on server VC
  2. Power on managed LM of the ESX host
  3. Power on LM Server
  4. Power on virtual LM VMs, routers & VMwareLM-ServiceVM by VC

  My questions:

  Are the steps in the proper order?

  What I have to cancel the deployment of my configurations or they may just be in an engine out of State? I like to keep the configurations deployed to maintain external if possible IP addresses.

  just closed down going also to extend the process of closing, it would be: ESX hosts SAN switch SAN storage reverse order to start upward.

• The Lab Manager Ldap integration

  I, ve configured a vSphere/ESX environment of OTA in a subnet of 172.10.1.0/24.

  Open ports on our firewall to manage OTA from our direct environment. Online subnet: 10.128.0.0/16

  Installed Labmanager 4.0 and add it to the field in the environment of the OTA.

  Everything works fine. After you open the port 389, I want to synchronize LDAP.

  When I do "Test LDAP settings" I get the following error:

  

  I read that it is not best practice to place a LM server in a domain.

  http://blog.aarondelp.com/2010/03/VMware-Lab-Manager-install-notes-and.html

  I tried the Ldap synchronization with the server of LM in a working group, but also, it does not work.

  Tried with the domain admin user, manually add the ldap port, it was left empty, different DN, nothing worked.

  Read also in the article is not to name the server labmanager LM, and that's exactly what I did...

  Also the lab Manager folder described in the article was not created in vCenter.

  I think uninstall LM, rename the virtual computer and reinstall LM. I don't know if it will solve this problem.

  I hope someone has a solution...

  Thank you...

  the 'test' LDAP settings actually trying to find the account provided credentials.  It's like a back loop... I should be able to find me before as I find other people.

  If the test account is not in the basic DN path of research, but can locate other accounts then it should.

  Best regards

  Jon Hemming

• Lab Manager licensing during the merger of vSphere environments

  Is there a small vSphere environment that is available for Lab Manager and a great environment vSphere and both are now completely separated (different vcenter servers, groups separated from ESX, etc.), and they are merged into one, what happens to the Lab Manager licenses?  Should be updated to take account of the increase in the number of ESX host in the new environment?  Environments can be merged without buying additional licenses?  If so, would be half the environment allowed for lab manager and others are not allowed?  How would the lab manager-under license, and lab-manager-without sections allowed environmental stands / separated?

  Thanks for your comments

  "Prepared" you went in in the section resources, hosts tab and see that the host is ready (green check mark), this means that there has been a 'prepare' to the host.  Prepare installs the agent LM, then she will deduct your license (settings > license).

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Relationship of Lab Manager and vSphere

  My shop starts to think about his Lab Manager architecture design, and we have some questions about the relationship between vSphere and Lab Manager.

  (1) can Lab Manager leverage of resources defined outside its host vSphere environment?

  (2) must LM be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features?  In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

  The reason we ask is because we already have production environment vSphere, and we plan to install vCenter Lab Manager within this environment or install LM in a separate vSphere environment.

  Thank you.

  Tim

  (1) the laboratory director can leverage resources defined outside its host vSphere environment?

  All used 'resources' must be inside a vCenter server, and all objects must be contained within a single "Data center" object in the hierarchy.

  > LM (2) done must be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features? In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

  If the vCenter for production is not the same as Lab Manager, you must export the Configuration of LM in an SMB share (requires a classic ESX host in the middle of LM), and then import it to the appropriate location.

  I did not notice problems with Lab Manager VMs-by-side with use of regular production.  Just separate the ESX hosts in a dedicated Cluster or a Pool of resources.

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• I can point my Lab Manager 4.0.2 to point to another new vCenter Server?

  Hi guys,.

  I have a client with a LM4.0.2 production and we are considering moving to one another new/a vCenter server.

  It is important to note that the new vCenter will NOT have the same DB or FULL of the old domain name. It's a completely different vCenter with other ESX hosts.

  Now the questions:

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  What of the ESX (resource) on the old vcenter?

  Is it possible to do this without downtime for laboratories? If this is not the case, how can I minimize downtime? cancel the deployment will be enough?

  Does anyone have this done successfully?

  Any comments would be much appreciated.

  Eyal

  etamir,

  There are some excellent discussions within this forum on the same topic.  I strongly suggest to read first, and I'll see if I can find an example.

  Before going further, data warehouses used in the new vCenter/ESX environment will be exactly the same as the current one?  If you want to keep all of your configurations, I need to know that the UUID of the LUN does not change during this process.

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  You can change the IP/domain FULL name vCenter in the settings section of the Lab Manager site... now on the problems that could result.

  You will need to remove anything from the GUI of Lab Manager that has to do with the current vCenter (unedploy, unprepare host esx, resource pools, configurations etc.).  There will be more on this in the dedicated thread

  What of the ESX (resource) on the old vcenter?

  ESX doesn't really matter, it's the data UUID store that matters.  ESX is just virtual machines.  Note: you'll want to throw all States/suspend points on the VMS where processors are different on the ESX hosts.

  > Is it possible to do this without downtime for laboratories?

  No, there will be a form any downtime.  Either that LM site will be useless (no resources with Betclic, consoles will does not work until the guests are prepared, etc.).

  > If not, how can I reduce downtime? cancel the deployment will be enough?

  Yes, to cancel the deployment of will help... but there will be some lag as you reconfigure Manager of laboratory to use the new vCenter.

  > Has anyone successfully done this?

  Yes.  I saw others to do this.

  Subjects in the sample: http://communities.vmware.com/message/1592762

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Tutorial or CBT on VMware Lab Manager

  Hi all

  I would like to get knowledge on VMLabmanager, can someone shareme vmware labmanager cbt link or ppt, tutorials.

  Thanks in advance

  
  
  Thanks and greetings

  Riadh Gunnal

  http://rajugunnal.blogspot.com

  VMware Self paced e-learning: http://mylearn.vmware.com/mgrreg/courses.cfm?ui=www_edu&a=one&id_subject=15589

  CBT Planet: http://www.cbtplanet.com/vmware-vcenter-lab-manager.htm

  Scott.

  -