Conflicting build # reported by ESX and VCenter

I've recently updated some hosts to the 2011 Rollup pack v3.5.0 (using "esx - 3.5.0_June2011Rollup - 391406.iso").

They point to build 317866 in VCenter and build 391406 when I use 'vmware - v' of the shell.

Before this update, they reported build 153875 (not me remember not for sure if I got this VCenter or ESX, based on my history of shell commands, I think it was the first).

This could be the cause?  I have attached the result of "esxupdate query" to one of the servers.

My apologies if this is the wrong forum; as I don't really know if there is a problem of VCenter or ESX, but as VCenter is that which appears in the account of the 'bad' thing, I think I would start here.

That is what I see in VCenter.  How do I change this?

N ° there is no need to update the version pass. There is no problem with him.  You can continue your work. Once vmware releases the latest patches, you can go ahead and install it: as he has a difficulty and RPM is included. Who should replace the old version with the most recent.

I hope this helps.

Tags: VMware

Similar Questions

  • Using VMotion with 2 ESX and VCenter

    Hi all

    I just installed with ESX 2 VSphere and & VCenter. I can't use VMotion to migrate a virtual machine running one ESX towards each other.

    My setup is as follows:

    the iSCSI Software initiator.

    data store even shared by 2 facilitators.

    same conf network on the 2 hosts, none vlan used (set to 0):

    • vSwitch0 for the Service console, connected to the network of the company (vmnik0)

    • vSwitch1 for virtual machine network (connected to the company network vmnic1) and VMkernel (for vmotion, connected to the production network: san, vmnic2).

    Error displayed (at 10%): a general error occurred: the VMotion failed because the ESX host failed to connect to the VMotion network, please check your physical network configuration and settings network VMotion.

    vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

    vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

    Thanks for help

    alelievre wrote:

    vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

    vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

    Two VLAN different connection to the iSCSI SAN. You should have the same subnet, but a different IP addresses (if any) connecting to the San from each host (depends on the SAN)... For example 192.168.130.25 for ESX1 and 192.168.130.30 for ESX2. Unless your SAN network covers actually two subnets on your local network, you create a question where you don't need to. I would also use separate NETWORK card for vMotion traffic and another for iSCSI. Separate them VM traffic too (makes everything cleaner and less chance of collisions and too load performance causing one issues for each other. This is why it is a good idea to have at least four, if not six, physical NIC (or ports) within an ESX/ESXi server.

    VMware VCP4

    Review the allocation of points for "useful" or "right" answers.

  • Firewall between ESX and vCenter vLAN & Production vLAN

    Hello

    Scenario:

    2 ESX hosts with Teddy bear 6. 2 to vLAN S.C. & VMotion, 2 to vLAN DMZ and 2 for the Production of vLAN.

    There are 2 pSwitches to battery-Mode Cluster, having 4 VLANS.

    1. Production of vLAN1

    2. vLAN2 DMZ

    3. Service vLAN3 console

    4. vLAN4 VMotion

    Connectivity is fine no problem. All VLAN works them very well. Service console and VMotion they fold each other so pSwitch failure failure or Teddy bear.

    Requirements:

    Service console is connected in vLAN3 which is 172.16.20.0/24 network under vSwitch0 contains 2pNICs & 3 exchanges.  Service Console PortGroup, VMotion PortGroup & vCenter PortGroup. vCenter PortGroup I want to place the VirtualCenter VM & I'll put the virtual computer's firewall.

    Currently, the Center Virtual under vCenter PortGroup, which is 172.16.20.55. Communication to ESX all very well.

    How I connect to VirtualCenter & ESX host while I am putting in the Production vLAN? I added a static Route in my P.C. 172.16.20.0 to go via 128.104.145.149 "this is the IP address pSwitch" I connect very well without any problems. Of course that does not protect the farm ESX and virtual Center.

    I want to secure the connection between the Production vLAN & Console of service of VMotion vLAN & get rid of the Static Route in the computers in the Admin.

    Bypass the Options:

    1. Physics MS ISA Server with 2 natachasery one be connected in the vCenter PortGroup & to be connected in the Production vLAN & open ports to demand it.

    2. Physical firewall of Teddy 2 a be connected in the vCenter PortGroup & to be connected in the Production vLAN and open ports require.

    3. Virtual Firewall 'SmoothWall or ISA Server' with 2 teddy bears that are connected in the vCenter PortGroup & to be connected in the Production vLAN and open ports require.

    Please take a look at the diagram attached & tips.

    Best regards

    Hussain Al Sayed

    Hello

    On your diagram, I would change your colors. Orange traditionally involves a DMZ not green, but it is up to you. I use Smoothwall for exactly the same behavior.

    Network <-> pNIC1 <-> vSwitch1 <-> vFW (smoothwall) <-> DMZ Network
    ....................................................<-> Green Network
    

    If your front firewall controls access to everything. You can use 'two' firewalls so if you just want to have a set of Red<->Green Networks. On the first, the Red network is outside, green is the demilitarized zone, in the second, red is the demilitarized zone and the ESX hosts are green.

    To grant access to your ESX hosts from a system outside the firewall, you must enable and redirect port 443 to the appropriate location. In fact, I wouldn't do that, create a virtual machine or physical box that is inside the firewall, use the VPN and OpenVPN Tarek Smoothwall addon in the internal location or create a pinhole that allows RDP access to this host/VM and then use the VIC of in the "green network". You must put the kingpins holes in your firewall to grant access you need, so a VPN works much better. You want to limit the number of holes of PIN you use.

    What you describe is quite feasible, but without the holes of the kingpins and proper routing through the firewall is not possible.

    Best regards

    Edward L. Haletky

    VMware communities user moderator

    ====

    Author of the book "VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.»

    Blue gears and SearchVMware Pro Articles: http://www.astroarch.com/wiki/index.php/Blog_Roll

    Security Virtualization top of page links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

  • How to configure ESX and vCenter with two areas virtualized?

    Hi all

    I'm quite new to VMware please bare with me, I'll try to get to the point.

    I am building a new infrastructure for a customer which will look something like the image below...

    My questions concern vCenter and the best way to install it and configure it, taking into account the environment below.

    (a) is it possible for vCenter to manage these two areas, even if they are completely separate?

    (b) how to configure the physical server Win 2008 in what concerns an area? If both virtual areas have their own domain controllers is to say 'Live-domain' and 'Test-domain' box Win 2008 won't belong to one, so what do I do with it? I can't join the party to another area because it is not a. And I can't let a working group.

    Any advice would be much appreciated

    CMA_MAP.PNG

    That sounds right. Yes, the ESX host will meet your virtual domain controller's DNS information. DNS is very important in an active VMware with HA cluster.

    Virtual domain controllers (and, as a result, DNS) are fairly mundane, no worries, I designed / management of environments that were 100% virtual (incudling vCenter).

    Make sure that you do not enable the option "synchronize time with host" on the virtual domain controller VMware tools. Otherwise, you will have a loop (with VM, VM host synchronization synchronizes with host). The option is disabled by default.

  • I installed ESX and vCenter.  Now what...

    I graduated from Workstation to vSphere.  My ultimate goal is to get Lab Manager operational.  I've got VMWare ESX 4.1.0 operational.  I installed vCenter.  I can connect and create a Resource Pool by using the vSphere Client.  But it doesn't seem to be a vCenter running.  I took the default values during the installation of vCenter.  Since my start & gt; Programs & gt; VMWare:

    Generate vCenter Server log bundle

    Generate vCenter Server log Bundle - Extended

    vCenter Orchestrator Client

    vCenter Orchestrator Configuration

    vCenter Orchestrator README

    vCenter Server Linked Mode Configuration

    VMware vSphere Client

    VMware Tomcat

    They are all trial editions.  I don't know what to do next.

    Thank you

    the screenshot, it seems you are not connected to vCenter, but rather just connect to your ESX host.  vCenter would have been installed on a Windows operating system. Using the vSphere client to connect to the IP/hostname of the host operating system, assuming that your added your vCenter OS host to an AD domain, you can connect using the credentials of the AD.

    Once, it will be blank, here, you can create a data center and add your host to vCenter inventory.

  • Cmdlet to find ESX and vCenter

    Hi all

    I use the following cmdlet to connect to ESX/vCenter.

    $vcServer = Connect-VIServer-server: $global: ipAddress-user: $global: vcUser-password: $global: vcPass

    I want to know if I connected to vCenter or ESX after login. Please help me.

    Kind regards

    Bharath

    The ProductLine property will tell you if it's a (vpx) vCenter or ESX (i) (esx) Server

    $vcServer | Select ProductLine

  • No cluster after esx and vcenter 4.0 to 4.1 upgrade

    Hello

    I installed my vcenter (4.0) server to a new server (4.1) with the new ip address and the new host name. I used the datamigration tool and there is no error in the log of the backup and the restore.

    Start all services, but when I connect with the new client, I see only the server vcenter and nothing under

    You have an idea?

    see if the item is useful

    http://KB.VMware.com/kb/1024380

  • 4.1 and vCenter ESX only allows to use 1 Fibre Channel LUNS

    Hello

    I have 8 blades ESX 4.1 (build 348481) in a Cisco UCS 5108 chassis. Each blade has 2 x HBAs available. I also have a fiber channel storage array that is configured to provide 2 1.8 to LUN (for now and in the future).

    When I go in vCenter and select one of the ESX servers under "Configuration"-> "Storage adapters"-> "Rescan all...» "each server detects the table (and several paths towards it) but only shows a single available LUNS (LUN 0) when 2 LUNS should be available (LUNS 0 and 1 logical unit number). See the image below.

    esx1_singlelun.png

    Now, the thing that confuses me is that when I get on the command-line of the ESX via SSH server and run "esxcfg-mpath - b", I see a list of all the paths including the paths to the LUNS 0 and 1 logical unit number (see output below). Any ideas on why ESX and vCenter authorizes me to LUN 1?

    esxcfg-mpath - b:

    NAA.600508e0000000001e10a036bc3f5601: FREE Serial Attached SCSI Disk (naa.600508e0000000001e10a036bc3f5601)
    vmhba0:C1:t0:l0 LUN:0 Status: active sas adapter: 5c84c75ed0910000 target: 1563fbc36a0101e

    MPX.vmhba32:C0:t0:l0: Local USB CD-ROM (mpx.vmhba32:C0:T0:L0)
    vmhba32:C0:t0:l0 LUN:0 Status: Active Local HBA vmhba32 channel target 0 0

    EUI.706f636c6162766f: disc SCST_FIO Fibre Channel (eui.706f636c6162766f)
    vmhba2:C0:T1:L1 LUN:1 status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00:1e target: WWNN: 20:00:00:24: ff: 32:10:f2 WWPN: 21:00:00:24: ff: 32:10:f2
    vmhba2:C0:T1:l0 LUN:0 Status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00:1e target: WWNN: 20:00:00:24: ff: 32:10:f2 WWPN: 21:00:00:24: ff: 32:10:f2
    vmhba1:C0:t0:L1 LUN:1 status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00: target: WWNN: 20:00:00:24: ff: 32:45:c2 WWPN: 21:00:00:24: ff: 32:45:c2
    vmhba1:C0:t0:l0 LUN:0 Status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00: target: WWNN: 20:00:00:24: ff: 32:45:c2 WWPN: 21:00:00:24: ff: 32:45:c2
    vmhba1:C0:T1:L1 LUN:1 status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00: target: WWNN: 20:00:00:24: ff: 32:45:c3 WWPN: 21:00:00:24: ff: 32:45:c3
    vmhba1:C0:T1:l0 LUN:0 Status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00: target: WWNN: 20:00:00:24: ff: 32:45:c3 WWPN: 21:00:00:24: ff: 32:45:c3
    vmhba2:C0:t0:L1 LUN:1 status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00:1e target: WWNN: 20:00:00:24: ff: 32:10:f3 WWPN: 21:00:00:24: ff: 32:10:f3
    vmhba2:C0:t0:l0 LUN:0 Status: active CF adapter: WWNN: 20:00:00:25:b5:00:00:ae WWPN: 20:00:00:25:b5:00:00:1e target: WWNN: 20:00:00:24: ff: 32:10:f3 WWPN: 21:00:00:24: ff: 32:10:f3

    MPX.vmhba32:C0:t0:L1: USB Direct-access locally (mpx.vmhba32:C0:T0:L1)
    vmhba32:C0:t0:L1 LUN:1 status: Active Local HBA vmhba32 channel target 0 0

    MPX.vmhba32:C0:t0:L2: USB Direct-access locally (mpx.vmhba32:C0:T0:L2)
    vmhba32:C0:t0:L2 LUN:2 status: Active Local HBA vmhba32 channel target 0 0

    Its because the table shows two LUNS have the same value of ID of Page 83, ESX both think you have 2 paths to the same LUN.  Paths multiple ESX driver uses the value of the ID of Page 83 to determine if 2 LUNS are the same device.

    It was a problem with that code, that it resembles yours-based Solaris beginning according to the tables and other tables that used code based on Solaris pre-COMSTAR, as well as tables that use SCWIST.

    There is really nothing you can do about it, because it is a bug in the software of the array (it shouldn't be exporting 2 LUNS different with the same ID value of Page 83 - it is a violation of the standard).

  • Is there a "ESXi and vCenter Setup Guide" available?

    I downlaed 'ESX and vCenter Server Installation Guide 4.1 ESX' PDF, but I need an ESXi version as I want to know rather than ESX ESXi score structure.  Is there a same doc for ESXi avaiable?

    Thank you!

    You can find a great description of Rickard Nobel at http://rickardnobel.se/archives/776

    André

  • Need a powercli script to create a new account a local administrator on all ESX and ESXi hosts in the vcenter

    Hi all

    If someone can help me with a powercli script to create a new account a local administrator on all ESX and ESXi hosts in the vcenter, create a role called admin and give all access except the root. This shoulb be past by a virtual centre.

    Very much appreciated to help him.

    Kind regards

    MelLvin

    I suspect that you posted your question to the wrong thread

    This requires only a minor change to the script above actually.

    Something like that

    $groupName = "group"$accountName = "user"$accountPswd = "password"$accountDescription = "A user"
    
    $esxlist = Get-VMHostforeach($esx in $esxlist){    Connect-VIServer -Server $esx -User root -Password "password"
    
        Try {      Get-VMHostAccount -Id $groupName -Group -ErrorAction Stop | Out-Null    }    Catch {      New-VMHostAccount -Id $groupName -GroupAccount | Out-Null    }
    
        $rootFolder = Get-Folder -Name ha-folder-root    Try{        $account = Get-VMHostAccount -Id $accountName -ErrorAction Stop |        Set-VMHostAccount -Password $accountPswd -Description $accountDescription -AssignGroups $groupName    }    Catch{        $account = New-VMHostAccount -Id $accountName -Password $accountPswd -Description $accountDescription -UserAccount -GrantShellAccess -AssignGroups $groupName    }
    
        $rootFolder = Get-Folder -Name ha-folder-root    New-VIPermission -Entity $rootFolder -Principal $account -Role admin
    
        Disconnect-VIServer -Confirm:$false}
    
  • Known issues with running ESX, vSphere and vCenter Lab Manager on a Windows Server?

    I'm on a project that is currently planned to install ESX, vSphere and vCenter Lab Manager on a Windows 2003 R2 Enterprise x 64.  Anyone know if there are known problems with their performance on a beefy Server?

    http://communities.VMware.com/community/VMTN/vSphere?view=overview and take a look at podcasting.

  • ESX, ESXi and vCenter and virtual machines

    Hello all - I need to re - certify my VCP this month so I decided to sit down this weekend to set up a virtual lab.  I managed to get ESX, ESXi and vCenter working all in s vm on my laptop in less than 4 GB.  I use Player version 3 for now.  I have Workstation 6.5 but I have to spend my VCP to get a key of 7 workstations and improve it.

    The manual is a bit long, but here is the link if you are interested.  I'll update everything to Workstation 7 after my review.  I hope that some of you find it useful!

    http://blog.aarondelp.com/2009/11/VMware-data-center-in-box-using-VMware.html

    Aaron Delp

    http://blog.aarondelp.com

    http://blog.scottlowe.org/author/adelp/

    Nice - Thanks for posting.

    I doubt that you must update for Workstation 7 as VMplayer 3 is nothing else than a torn Workstation 7. It has the same basic functionality.

    So, nothing will be different if you use Workstation

    By the way - Starwind is really nice simulate a San.

    Another interesting thing, that you know may not...

    It is possible to assign up to 8 GB of RAM to your virtual ESXs, even if the host itself has only 4 GB of RAM.

    For this I have

    prefvmx.useRecommendedLockedMemSize = 'TRUE '.

    prefvmx.minVmMemPct = '5 '.

    in the file config.ini from the host. Do not run and then

    Using this trick, I was able to run 4 ESX virtual machines on my laptop 4 GB RAM running 2 k 3-32 bit host

    Ulli

    ___________________________________

    VMX-settings- VMware-liveCD - VM-infirmary

  • Is it possible to use GPFS or another build is a SAN storage shared for multiple ESX and ESXi hosts?

    We have a license GPFS and SAN storage. I am trying to create a storage shared for multiple ESX and ESXi hosts share existing virtual machines. We tried once NFS, it of a little slow and consume too much bandwidth LAN.

    Anyone can help answer? Thank you very much in advance!

    It depends on your storage space.

    You must connect all hosts to the same San, then follow the configuration guide of ESXi and specific documentation for your storage space (for sharing LUNS on multiple hosts).

    André

  • vSphere and vCenter

    Hello world

    I'm new on this and am frustrated at this point because most of the time, the documentation is not exhaustive. After a week that I managed to install my drive of vSphere ESX, create a vm Server 2008 and install vCenter then install and configure Orchestrator. Had a little trouble with SQL "surprise surprise" then comes into conflict with the server web and IIS. Now that things are settled nothing seems obvious or apparent.

    ESX was installed directly on the server with any Microsoft OS, as I learned its more effective this way. I can't find anything on how to make backups and, especially, the converter. It is installed but is not found. Click right on the host and no Assistant import, according to the inventory tab/host anything. So again I have ESX 4.1 installed directly on my server with any MS OS, I connect via vSphere client and a virtual machine called vCenter. On this vm Orchestrator is installed and SQLEXPRESS. I saw all the tutorial there, video making repeat and I installed and configured but don't see not what Im supposed to see HELP!

    Thank you for reading my rant and hiope someone can shed some light on my situation

    Looks like you need to install the converter on your vCenter server.  Just insert or attach the vCenter vCenter VM media you created.  Launch the installation and you should see an option like this:

    Once it is installed, you should be able to see it in the plugins section as follows:

    Right-click on it and select activate.

    If you have found this helpful at all prices please points using the correct or useful!  Thank you!

  • who can tell me the most recent version number of the Client vSphere and vCenter.

    who can tell me the latest version number of vShpere customer and vCenter?

    The previous issue are the latest version (4.0U1).

    A way of knowing the last build number (for a version of Ux) is to check the download site (in the Download details):

    http://downloads.VMware.com/d/info/datacenter_downloads/vmware_vsphere_4/4

    For works build and see also version number:

    Version number and compile ESX

    André

Maybe you are looking for