Utilities to host ESX NetApp - questions?

Similar Questions

• Questions about connecting to a host ESX 3.5 to vCenter 4.1

  I need to migrate 7 hosts 3.5.x ESX ESX 4.1. I did not have a test environment and will work with live on committed production systems (not clustered). vCenter 4.1 and two new 4.1 ESX hosts have been configured to handle live Vmotion (cluster will come later). I activated the license point server towards the old VirtualCenter 2.5 in the hope of being able to disconnect a host ESX 3.5 live the old virtualcenter and reconnect to the new vCenter 4.1 without rebooting the host ESX 3.5. VUM is not an option at the present time, so I intend to do a full install base upgrade.

  (1) I know that I can disconnect the ESX 3.5 server the old virtualcenter without problem. My first question is, if I try to join the new vCenter (config pointing to the old license server) box of 3.5 will be vCenter 4.1 need to install the new management agent in the box of 3.5 and therefore require the host restarts?

  (2) if the agent of 4.1 management is not installed on the host ESX 3.5, its virtual machines can be migrated (cold) to one of the new servers?

  I should add that the licenses are not a problem, we are migrating to the latest keys but have sufficient old licenses to manage the transition. The VMs are on SAN LUNs that are visible to guests old and new.

  Especially, I want to know what to expect through are exactly what will to restart is required and have not been able to locate that particular point.

  Thanks in advance.

  hensonj7

  When we went from 3.5 to vSphere, is that big of a deal.  Just disconnected the vCenter server host and updated the vCenter keeping the existing license server, and then re-attached to the new Victoria Cross.  It will establish links with the new 4.1 software, but it shouldn't require a reboot at all.  I did mine with all virtual machines out of it, but I think you can do all this live... Since a little while I did this upgrade

  -Kyle

  «"RParker wrote: I guess I was mistaken, everything CAN be virtualized"»

• GROUP hosts ESX (impossible to find in correlation of events through Insight Log)

  We have several ESXi 5.0 hosts who are restarting unexpectedly (GROUP) and want to use Log Insight to quickly assess how rampant it is through the fleet and the frequency of occurrence.

  Unfortunately we have not been able to generate a successful via interactive analysis query to return any success.

  Here is a sample of the actual events, through the vobd.log on a given host:

  2013-07 - 01 T 14: 29:21.790Z: [UserLevelCorrelator] 96423176us: [esx.audit.host.boot] host has started.

  2013-07 - 01 T 14: 29:22.469Z: [UserLevelCorrelator] 97102185us: [vob.user.host.coredump] a unread host kernel core dump was found.

  Tried to set exclusions specifically for the name of the host in question, do a search for 'core dump', etc. all without success.

  Ignorance of the user?

  If you have configured the ESXi host (s) in question to send Remote Insight log syslog after the GROUP occurred then it would be expected behavior. Configuration of any device to send remote syslog applies only to events that occur after the configuration has been implemented. The next time that event occurs that you should be able to get him in Insight Journal (you could even create a dashboard or set up an alert beforehand). Log messages would be removed only in the case of the network connectivity issues or hitting a maximum on the target remote syslog. In terms of ESXi, the only thing to keep in mind is the remote syslog bug. I hope this helps!

• Planning of the names of the dns infrastructure and host esx (FQHN)

  Greetings,

  We plan our virtual environment for ESX 3.5 on IBM xSeries hardware. The environment will be made up (initially for short term) of two ESX host machines and a server that is running Microsoft Windows Server 2003 for virtual center and VCB to backup proxy functions. My questions and concerns, consider installing the management network and the host names of the servers themselves.

  I want to ensure the safety of the ESX servers and management functions by choosing a servo for all ESX hosts IP subnet and the virtual Center. Anyone done this? The back of the draw are more limited communication with the "machines" or more complicated infrastructure network that you need to add an interface on a router or an internal firewall for proper computers can access the host ESX and virtual Center. - What someone else? Are there better ways?

  I also have questions about a naming convention good/responsible for all vmware hosts. We have example.com as a public domain. Someone also created a domain in active directory (who did not understand what they were doing) in the same domain, so my structure active directory looks like "host.example.example.com" - silly, I know. I guess that it is more appropriate to not place ESX or other host vmware in the same logical domain/dns as members active directory. While the leaves creating a separate field or using the public domain from example.com (esx.example.com). I thought for security and separation, it may be more appropriate to use "esx.example.local". This command removes any way for virtual infrastructure mingle in the public domain. All comments, thoughts, carries on this?

  I also intended to appoint guests something like the following: ESX1.something.tld, ESX2.something.tld, etc. and virtual center something like VC.something.tld. Since virtual center needs to be a member of active directory to allow the mapping to user accounts, those who cause any issies with the ESX host with different domain names complete? Are there other ways to connect to active directory without being a domain member machine? Is anyone doing or having problems with it from a security point?

  ccandia wrote:

  fhrivers,

  Thank you. I suppose that by 'local management LAN', you hear the internal local production lan do you use?

  We actuallu use 2 subnets now, private, internal, and a DMZ for guests in public (although it's hard to keep everything under this distinction more). I assume that your recommendation is just to meet the host ESX and virtual center under the internal local subnets, even as the other hosts internal and access control on virtual Center allows to regulate access to the VI3. Certainly address more easily. You have concerns the fact that VC is running on a windows platform and is therefore vulnerable as such? I was trying to come up with a good armor for VC. I guess that windows firewall is always an option, or stop the services and other standard precautions. What is your opinion of securing virtual Center?

  You're right, I want to talk about the normal subnet that all servers and users are connected to.  This works in my environment, but may not work in environments more serious questions of internal security.

  I actually run VCenter as a virtual machine in a HA cluster to eliminate the scenario of hardware failure, but I do not see why the vCenter running Windows makes it more vulnerable than any computer on your network.  Like any other essential service, I would make sure that running the server vCenter vCenter only and that essential services only run including a client anti-malware.  I tend to take an approach more inside-out security and not an outside in approach.  I'm more concerned with security at the application layer to the edge of the network.  Again, which works best for my environment.

• Host ESX HD stuff?

  Couple of questions about the ESX host and storage for it.  Keep in mind, I have only a few ESX hosts.  My main problem is not not the purchase of hard drives, but the shortage of places in my background to put them.

  Given HA/DRS/etc. are always people mirrored the ESX host if there is no virtual machines on the same axis?  Why bother if HA/DRS is involved you would have time to rebuild the ESX host.  Worst case, you will lose the second HD until you can get the first host ESX rebuilt (probably not, and if it happens you are probably looking for a problem bigger than a dead HD).

  OR

  It would be better to reflect a couple of HDs, create the required virtual 36 GB drives and load each ESX in it's own 36 GB vd on the same mirror HDs?

  Thank you

  Bob

  Yes I see it now. Have been home all day with my kids watching Yo Gabba Gabba again and again. Brain is mush

  No RAID is logical if you clusters that can tolerate loss of a host without overloading the remaining hosts. I work in a hosting environment and we tend to be very concerned about ALS, so anything that prevents downtime is good (although I think some of it is just inertia on our part, we just do things with virtual systems that they made us things with physical systems).

• Presentation of ID host ESX host LUN to the VCB Proxy Server

  I have a typical scenario where I have 3 ESX servers with 3 x 800 GB LUNS in a storage group separate on a CX 310 SAN box. The host LUN., of these 3 LUN Ids are 0, 1 and 2.

  I have a specific host that starts from SAN, from the same box of CX 310 SAN. At this point of time, I have no choice to use this server as a Server Proxy VCB. As far as my knowledge goes, LUNS of the ESX servers must be made visible to VCB Proxy Server, as they are presented to the ESX servers.

  My question here is, as the designated Proxy VCB server is booting from the SAN, he already has a host LUN 0 to Id the logic unit number this is the start of. The Id to host ONE of the first 800 GB LUN in the ESX Server storage group is also Host Id 0. Now, if I try to make the LUNS in storage group visible on the VCB Proxy Server ESX, is there not a shock of the VCB Proxy 0 host Id and Id host ESX Lun 0? I'm confused, I don't have a test envirinment where I could try this before I could actually go forward with any solution.

  My intention is to perform a backup outside LAN of the VMDK.

  Any help is that this respect is very much appreciated. Thanks in advance.

  (1) Yes, you can have different host for VCB then for your ESX host LUN ID

  (2) Yes, you can use the identifiers of naa, it will automatically use the identifiers of naa, no need to configure anything at all.

  Duncan

  VMware communities user moderator

  -

• Copy files from my computer to a host ESX 3.5

  Hello

  Relatively new to the naked ESX Server with me on this one. I built on an ESX host with the intent to use it to restore an Exchange mailbox for one of our users. I have 3 comments of the machine (a domain controller, an exchange server and a vista client to reconnect the mailbox). I have those 3 vms on a single internal vSwitch. The problem is that the Exchange database files that I restored are sitting in a folder on our production network. My question is, how do I copy these files to the vm of the exchange on my host ESX Server? Thanks in advance for any ideas.

  There are two ways you could do this.

  You can add a second vnic to the Vista client. the vnic would uplink for a vswitch with access to the network of prod. Give the client Vista a static IP from the network of production on the new vnic and copy files on via SMB (i.e.
  prodserver\c$ \somepathwheremyfilesare\)

  You can also set up a temporary virtual router (http://communities.vmware.com/docs/DOC-9617)

  Or I guess you can burn the files to an ISO then transfer the ISO in a data store on the ESX host and then mount the ISo as a CD image (don't forget to clear the bit read only)

• Trying to increase the capacity of virtual resource Flash, no host esx and no SSD is located

  In vSphere 5.5 WebClient, click host esx-> settings-> virtual Flash Resource Management.

  Then click on the button 'Add ability '. Empty the list of hosts/SSD devices.

  I followed the instructions with this announcement, but the list of hosts/SSD devices remains empty.

  https://communities.VMware.com/thread/464660

  Anyone know how to get around this problem? Thank you!

  It works indeed. You need to do some CLI commands to mark the device as a local and an SSD, but I outlined the steps in a post on my blog:

  http://tomverhaeg.nl/VMware-ESXi/VMware-ESXi-tag-a-device-as-local-and-SSD/

• Adding new host ESX in VCD 1.0

  Hi all

  I wanted to know the procedure to add the new host Esx VCD and how to increase resources for the installation of the existing cloud.

  Thanks in advance
  Ashok

  Add the host to the Cluster support required in vCenter provider vDC, ensure that networks and required data warehouses configured on this host, and finally as a system administrator in vCD under surveillance & -> resources vSphere management-> Hosts, prepare the new host ESX (i).

• Host ESX 4.1 VC does not

  Hello

  I installed VC 4.1.0 in a virtual machine Windows 2003. Installation and setup went smoothly. Now, when I add a host (ESX) to the VC, the host indicates that does not respond within a few seconds. Is this something known? I found a similar thread http://communities.vmware.com/message/1347953, where it was mentioned that it is a known problem with old buildings.

  In addition, when add it this host to an another similar VC it works fine. Not able to understand the problem with this configuration of VC.

  Waiting for a response from VC experts.

  Thanks in advance

  ~ Nesrine

  Email: [email protected]

  Is there a firewall between ESX & VC? If Yes can you confirm if port 902 TCP & UDP is allowed bi-directional?

• How patch a stand-alone host ESX 4.1

  Can someone tell me how patch a host ESX 4.1 autonomous without the help of the Update Manager?  I have created the vSphere Management Assistant VA and have downloaded patches ESX host on my desk.  I'm looking for the process or the required commands to install the updates of patches to the host once I have put the uploaded file in a directory on the host computer.

  Thank you!

  A step by step guide

  http://communities.VMware.com/blogs/vmroyale/2009/10/12/single-use-esxupdate-how-to-for-ESX-4

• Time synchronization with host ESX to Windows start even if disabled in VMware Tools?

  Hello

  just got in trouble with a freshly installed Windows XP SP3 VM do not apply Active Directory group policies. After some research, I discovered that this happened only with VMware Tools installed.

  With VMware Tools installed, Windows events 1030 and 1097 were generated at each start (the events say that group policy processing has been abandoned and that there is a time difference between the server and the client) and group policies have been applied.

  Without VMware tools, everything was fine.

  After some additional debugging I discovered that the ESXi (4.1) server was not configured with a valid NTP server and the host time was 10 minutes behind. However, as time synchronization between the guest OS and the ESX host has been disabled in VMware tools, I couldn't imagine it was really the cause of the problem. But strangely it turned out that this was indeed the case! At every Windows startup time has been at the time of the host ESX - but only for a few seconds. This can be seen in the attached photo: initially, there are guest operating system time, and then you see the jump both ESX and then jump back to the guest operating system.

  Why does this happen? Hard, I could solve the problem in the first place by configuring the NTP server on the host, I would like to know why VMware tools change the time of the guest OS, even if it is disabled!

  Thank you

  When he put the VM must draw from somewhere and since the AI network time form more that probably not started it must draw from the host, but once the networking appears he died in the NTP source - that's why it is recommended to configure your ESXi (and ESX) to synchronize the time with NTP source.

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

• Host ESX 4.0 to 4.1 upgrade

  Hi all

  In my organization I have assigned to a task of the Host ESX 4.0 to 4.1 upgrade.  I came through the VM KB documents.  Y at - it videos available that shows the upgradation via the Service Console.

  Thanks for all the entries...

  Thank you.

  Hello

  You don't need a video, its very simple.

  1. simply download: upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

  2 use VUM guests 4.0 to 4.1.

  In addition, you can do command line...

  1. download: pre-upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

  2. download: upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

  3 using esxupdate

  Thank you

• Not able to connect to the host ESX 3.5 by VC so customer VI

  The host ESX 3.5 has been disconnected from the VC, and we are not able to connect customer using VI as well. The virtual machines on the host are running without any problem.

  Got the message when tried to restart/start services of Mgmt. below

  # Service mgmt-vmware restart

  stopping VMware ESX Server management services:

  VMware ESX Server Host Agent Watchdog

  VMware ESX Server host agent

  Starting VMware ESX Server management services:

  Agent Host VMware ESX Server (background)

  Availability report startup (background)/etc/init.d/mgmt-vmware: fork: Resource temporarily unavailable.)

  # Start of Service mgmt-vmware

  From the VMware ESX Server management services:

  VMware ESX servre Agent Host (background)

  Availability report startup (background)

  status of service mgmt-vmware #.

  VMware-pass is stopped

  hostd.log - entries

  /etc/init.d/sshd command failed

  Didn't the /etc/init.d/sshd fork: Resource temporarily unavailable.

  Let us know the fix for this problem other than restarting the host.

  To know how to clean it, please read KB1007887 - defunct cimservera of process on VMware ESX 3.5 hardware management agents run and follow the instructions.

  André

• How will I know when my host ESX 3.5 license expires?

  How will I know when my host ESX 3.5 license expires?

  Check here, http://www.vmware.com/checklicense/ , he'll tell you.

  Copy and paste the content of your license file and click to be valid.