Mobile vcenter server in existing farm to new esx host

Similar Questions

• New ESX host cannot see SAN fiber - Clariion

  Hello

  I spent about two hours, passing through communities and have tried various things without success... basically, I have a new ESX host that I've built, configured, and networked, but I can't see our existing SAN.

  The SAN is a Clariion CX3 - 10 c and it hosts all of our existing VMs (we currently have two hosts attached to the SAN)

  I have installed the CLI and Navisphere agent on the new host

  I have started to host and that you have ENABLED the two adapters Emulex HBA (host contains two HBAs installed) because they showed as disabled by default BIOS

  I have one of the HBAs connected to the fibre switch

  On the fibre switch, I have a flickering green light where I plugged the fiber cable, which makes me think, it is connected OK

  On the HBA, I have a green light and an orange light blink, which still makes me think the wiring is correct

  BUT I do not see the front Navisphere host, and the host cannot see all storage even after re-reading.

  Any ideas what to try next? I suspect that it is perhaps something to do with zoning - I must say the Emulex HBA how to find storage processors? If so, how can I go about it? From the BIOS by restarting the host and pressing ALT - E?

  Any help or advice appreciated...

  Assuming that hard zoning this site should provide you with some

  Help

  http://TechNotes.twosmallcoins.com/?p=16

  Also once the switch is zoned if the host is not listed on

  the Clariion Navisphere agent system has a config file that needs to be updated

  with the IP addresses of the SPs.

  You can also manually enter the host if necessary, but your

  probably zoning question.

• Problem with VCenter server on VM - how to upgrade the host

  Hello.

  I have VM on VCenter.

  I can't update the host with patches critical host because he can not enter maintenance mode.

  Is it possible to do this?

  Thank you

  Best practices so that a VC Server VM on a host of multi with SAN storage environment must be available for the use of compatible hardware for VMotion or VCA VMotion.  If you do not have an environment that allow VCA to then I would say that the best practice is to have the VC server on a physical server - it can even be installed on XP.

• Compatibility of VMware vCenter Server 4 Foundation to vSphere with ESX 3 Standard VI

  We are already use VMware ESX Server 3.5 VI.

  Our intention is to buy VMware vCenter Server 4 Foundation for vSphere addition VI ESX 3.5 Server running on a separate server. Our concern is;

  1. is VMware vCenter Server 4 Foundation for backward compatible product vSphere with VMware ESX Server 3.5?

  2 If no, then is it a similar product of VMware, which is compatible with VMware ESX Server 3.5?

  Please notify.

  VMware vCenter Server Foundation 4.0 can handle up to 3 vSphere or legacy hosts.  If you need to manage more than 3 guests, you should definitely consider vCenter Server Standard edition.

  ESG-VMware

  VMware communities user moderator

• Install new ESX hosts.  Cannot Ping.

  Hi all

  I'm building a test lab which so far consists of:

  ESX1: 20.1.1.10 255.255.255.0

  vCenter: 20.1.1.100 255.255.255.0

  Openfiler iscsi: 20.1.1.40 255.255.255.0

  I had all these configured devices and can ping throughout (with a little help from you friendly people, of course). I just tried to install my second esx host and I have a few problems to get to communicate with the rest. During installation I assigned an IP address of 20.1.1.80 255.255.255.0 so its on the same network. Rattling of the evil machine returns "destination host unreachable". Ping to it from any other device returns the same. esxcfg-NICS - l is the network card. Route - n shows exactly the same output as my other work esx host.

  This workshop is entirely on its own network. All devices are networked through a simple switch 16-port Dell 2216 with any VLAN or whatever it is.

  I tried all sorts of troubleshooting a layer on my switch ports, including the passage of the cables, and finally pulling up the entire hard drive and put it in a same laptop to rule out a bad network card. I also went into the bios and adapted settings my host to work to avoid any possible problem of allocation of resources.

  One strange thing I noticed. When I run esxcfg-nics command on my network card work esx host is displayed. When I pull on the cable and run the command, it displays down. Plug it in again, almost immediately goes back to the top. However, when I try the same process on this machine of boredom, the NIC appears whether or not the cable is connected some sort of funny business going on here. What Miss me?

  EDIT: I could have taken the lead on this one.  I see now that speed is 0MBPS and is half-duplex.  I gave the esxcfg-NICS-s-100 d full vmnic0 command but esxcfg-NICS-l does not reflect them.  I'll try a reboot, but I think this is probably my problem.

  Faulty network card causes a problem of driver especially problem run miit-tool to check the duplex speed and also his ping locally? stop the firewall during the tests of time and running tcpdump on interface to control icmp traffic.

  ifconfig - a vswif0 control is in place and the correct ip address?

  Thank you

  Pitoux

  -Path to the virtual world.

• 5.1 ESXi host rest disconnected when it is connected to the new vCenter Server 6

  Hello

  I created a new version of vCenter Server 6.

  I have e vCenter Server 5.1 connect my 5.1 hosts.

  I want to connect hosts to the new vCenter and then upgrade to ESXi 6 guests.

  I disconnect hosts on the old vCenter.

  The I connect hosts to the new vCenter, and it happens with all the vm´s, etc..

  But it is disconnected.

  And it keeps beeing disconnected even when you try to connect again.

  If anyone has experienced this?

  Thank you

  Thomas

  Have you added these hosts in your new server vCenter along with their licenses?

  Otherwise, if please add host license in your vCenter license inventory and assign to those of your hosts and then try to re - connect.

• New server vCenter Server

  I am running a 3.5 environment, and I want to get to sphere.

  I'll create a new vSphere vCenter server to manage my boxes of esx 3.5 and possibly update these boxes to sphere.

  Currently, vCenter 3.5 I manage my esx boxes, and this same server is the license server.

  Can I simply create a new server and then add my esx boxes in its inventory of management?

  Do I have to remove these boxes on the other server vCenter esx?

  Can the two vCenters be running at the same time?

  And have point to the new server cVenter to the old server vCenter for licenses, or simply keep the old server up?

  justinscanlon wrote:

  Can I simply create a new server and then add my esx boxes in its inventory of management?

  Yes, unplug and remove hosts from the old environment of vCenter and add a host in the new

  Do I have to remove these boxes on the other server vCenter esx?

  Yes

  Can the two vCenters be running at the same time?

  No.... not if they use the same DB instance.  If you use a different instance of DB, then Yes. But you can't manage the same ESX host in both environments.

  And have point to the new server cVenter to the old server vCenter for licenses, or simply keep the old server up?

  You can use your old license for your VI3 hosts server.  Home - vCenter Server Settings.  Or you can install a standalone license server.

• Two vCenter - migration to vCenter Server 5

  Hello world.  I have a vCenter Server 4.1 to exsiting v4.1u1 hosts and production/DEV Essentials Enterprise production management.

  I want to build a new vCenter Server 5.  This new vCenter facility will also have the new databases and vcenter Update Manager, on a separate SQL Server.  I'm not worried about the loss of existing data as each of my existing hosts is also rebuilt to ESXi 5.

  My question is about licensing.  On the this server vCenter, all my license keys are exhausted.  If I build a new server vCenter, how can I add my existing ESX/ESXi servers to the new server vCenter without licenses available?  I realize that if I remove Let's said ESX01 since the existing vCenter server, these licenses go back in the pool on SERVER.  If I can't add ESX01 on the new vCenter server, I used this same license key?  In other words, have the same active key on two vCenter servers, which are not connected or even the same version?

  Clear as mud right?

  Thanks for your time.

  -Dave

  Using the same license key on both instances of vCenter server is actually the only way that you can migrate hosts on the new vCenter Server. I do not think that there is a problem of legal license if you disconnect a host of the "old" vCenter Server - releasing upward CPU licenses - and then assign the license to host again when you connect it to the new vCenter Server.

  In regards to your first sentence. Probably, you break the EULA if you manage Essentials through an instance other than the Server vCenter vCenter server for Essentials.

  André

• vCenter Server upgrade to version 5.0

  Hello

  I would like to know during the upgrade to vCenter Server 5.0 calls a new license key or he use of the existing version license key.

  I have vCenter Server 4.1 installed so Standard 6 hosts ESXi 4.1 installed with vSphere Enterprise Plus licenses each with 2 CPU. I plan to upgrade my environment of virtualization to vCenter Server 5.0 and vSphere Enterprise Plus 5.0, please someone can me brief on conditions of license - can I use the vCenter 4.1 existing licenses vSphere 4.1 upgrade to version 5.0, so I don't want to buy new licenses.

  Hoping to receive information about my queries.

  Kind regards

  Nikhil

  No, not if you have a valid support and subscription.

  You must visit the portal of licenses to upgrade the license (I think).

  I myself did last week and I'm sure that even if I already had a job entirely vCenter 4.1, I was required to enter the new license v5.0 file.

• Backup of VM best practices using vCenter Server

  Hi all

  I currently plan to backup my virtual machine in VMWare ESXi 4, I have

  installed the trial vCenter Server 4.0 administration server.

  My 2 x ESXi 4 server connected to a San and sharing a single LUN so

  in this case, I would like to create another LUN in the SAN to

  Hold the Backed up SAN. (see attachment)

  and I'm still not sure about which license should I get for this question? between essential or Foundation

  My goal is to be able to do:

  1 backup and restore using VCB

  2. ease of management of VM creation and the cloned VM management, models and migration (moving between SAN and SATA Local data store) offline.

  HA and VMotion is not important at the moment.

  any suggestions and comments will be greatly appreciated.

  Thank you

  Kind regards

  AWT

  There is no way to "upgrade to ESX ESXi" without a complete reinstallation of the product.  If you really want instead of ESXi ESX, you should be able to just install ESX, ESXi over and tell him to keep all existing partitions intact VMFS.  You will lose all your settings (vSwitches, etc.), but you shouldn't lose all virtual machines.  In fact if the ESX host is SAN attached so you can just blow everything about ESXi installation and install ESX and reattach the VMFS LUNS to the new ESX host.  You shouldn't lose anything it. Make sure that the ESX host is not attached to the SAN when installing ESX (unplug the cable) than who has been known to cause problems.

  You will get no reduction in functionality if you stay with ESXi.  Once an appropriate license, ESX and ESXi work exactly the same.  The main differences lie in the way you manage servers with the absence of a Service Console on ESXi.  Given that VMware intends to get rid of the Service Console completely in future versions, it might be logical just to go in that direction now and stay with ESXi.

• Locking ESXi 4.1 mode access confirmation no access to the vCenter Server

  Hello

  ESXi 4.1.  I see options in conflict with access to a crowd that had lockdown normal mode activated via a server vCenter VM on a host in the cluster.  The vCenter server that sits on one of the hosts in the cluster lockeddown then became inaccessible or unresponsive connectivity wise.  So no connectivity between vCenter VM or VM vCenter and hosts.  Is someone can confirm if you can connect to this host lockedown by DCUI with root and disable lockdown configuration to allow the vSphere client to then connect to the host with root and troubleshoot the server vCenter VM?

  I read in some messages that this is only possible if the vCenter VM is in place and the communication to the host.  I also read that it is possible no matter what the State of the vCenter server once Total lockdown (disabling DCUI) is not enabled.

  I have this reference of the 'The new lock in ESXi 4.1 Mode' blog http://blogs.vmware.com/vsphere/2010/09/the-new-lockdown-mode-in-esxi-41.html

  "With active locking Mode, the only direct access to the host that remains open is through the DCUI. This allows to perform administrative tasks limited outside vCenter Server, such as restarting the management agents and the display of the log files. In addition, you can also disable Mode of Lockdown since the DCUI. This can be useful if vCenter Server is down or unavailable, and you want to return to a direct management of the host. Normally, without locking Mode, any user to the Administrator role can open a session in the DCUI.  However, in lock Mode, the root password is necessary; no other user can connect.

  Can anyone confirm.

  Any other person who may not be sure these questions, I can confirm that with root credentials, you can connect to the host directly and disable the lock mode regardless of the availability of vCenter.  Only if the Total lock mode turned on, or should I say DCUI is disabled, then you have no choice but to go through vCenter or reinstall and reconfigure the network.  VM would be always available if local or have to be reassembled and re inventoried etc.

• vCenter Server Linked Mode or not?

  Hello

  I had the following scenario: I have an existing with 8 physical ESX host Esx environment and virtualized 1 vCenter server for all direction and 1 Cluster. Now (for Oracle license costs) my company advised me to create a second group of Esx with 4 physical ESX host.

  My question is related to the vCenter for the management of the two clusters. It is recommended to install a second vCenter Server for the Oracle VM Cluster and server vCenter link the two together (linked modes) or let them operate separately or use only 1 vCenter Server for the management of the cluster 2?

  In your opinion, what are the ADVANTAGES and DISADVANTAGES?

  Thank you!

  Just bound mode will not give you solution Dr. bound Mode is used when there are two vcenters and they are linked together to achieve centralized management. It will all show you the inventory in both the vCenters. The first vcenter will both his and 2nd vCenters inventory and the second will have its own and inventory of 1.

  But using a UNIQUE multi-site authentication users/permissions will be replicated and since you have the replication table both of them should work together and give you DR.

• Errors in the charge installing vcenter Server 5.5 with respect to the SQL database

  I do a new install of vCenter Server 5.5 on a new Windows 2008 R2 server. The database for this facility is pointing at a 32-bit Windows 2003 SP2 server. I installed SQL Native Client 10.0 on server vCenter Server 64-bit, and then I could make my DSN ODBC 64-bit connection. The vCenter Server install could very well recognize it, but after the installation got going he wrong on the database with the following error:

  Error 25003.Setup cannot create vCenter Server repository. The main reasons for this failure are:

  -The database is installed using insensitive case.

  -The database is remote and the client database version does not match the database version. If this problem continues to persist, see KB 1003960 for further assistance.

  Well, I know that the version of the client and the version of database do not match. SQL native client on the sql server is 9.00.5000.00 and the version on the server vCenter Server is 10.50.1600.1.

  I know that this version of vCenter is compatible with an installation of 32-bit sql server 2005 on a 32-bit server, 2003.

  I am not familiar too if they want upgrade me sql native client on the sql server, but is not compatible with the version of sql server on this server and there are several database for other applications on this server, so I don't want to jump into something like that.

  Any help would be greatly appreciated.

  Thank you.

  I install the native client SQL 2005 and give a shot.

• Migrate from vCenter Server 5.1 again cluster

  I have my server vCenter Server (v5.1) VM on a former cluster of servers ESXi 4.1/5.0. I only have vSwitches on each of these hosts. I now have a new 5.1 ESXi hosts managed by this same vCenter Server cluster. However, this new cluster has a with completely different dvSwitch VLAN is configured. I have already created several new VM in this new cluster with the new VLAN / port groups.

  I would spend my vCenter Server the old the new cluster and I can't understand how to do this since I can't access my dvSwitch when adding my vCenter Server VM to a new host.

  Any ideas?

  Thank you

  BM

  Is not possible. For a migration live to work, you need the source networks and applications available in both environments.

  I just create a new server vCenter in the 5.1 environment and migrate new hosts to the new vCenter server.

• Process of upgrading 3.5 host with vCenter server Virtual

  Hi I have recently updated my old server from client to vCenter 4.1 virtualized VI, sitting on my 3.5 cluster.  I intend to use the Update Manager to upgrade my guests, but I don't know how the virtual vCenter server is going to face?  The plan was: 1. move all the virtual machines off-host 1.  2 put the host in maintenance mode 1. 3. on the vCenter server, create a base, then line at host level 1 to 4.1. 4. now - at this point add this host in the cluster? And migrate the server vCenter top, so I can upgrade the other two hosts?  If the works above, then it should be quite a nice update, if you cannot add the new version of the host of back in, how you vMotion the vCenter server off so you can keep control of the cluster.

  IMO, it should work. To upgrade from 3.5 to 4.1, your ESX host must be in 5 update (see http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf) already.

  If VMotion or migrate the server vCenter Server - for some reason-does not work, you can delete vCenter Server of the inventory of the old host and add to the inventory of the new host.

  André