VLAN between two hosts ESXi

Similar Questions

• Travel/cloning between two hosts ESXI VM

  Hello

  I have two hosts ESXI 4.1 with VSphere Essentials for VCenter license. I'm not able to move the virtual machine to one ESXI host to another (power off). It is not supported with VSphere Essentials license? Data warehouses can be shared between the two ESXI hosts?

  What is the size of your virtual machine, what is the speed of the network and how your local storage looks like? Using RAID? How many disks and RAID level? You have a battery attached to the RAID controller write buffer cache?

  The waiting period does not necessarily mean the tasks does not work. Often it is only a delay in the vCenter Server GUI, but the process is still running and you just need to be patient. You see the files being created on the target data store?

  André

• vMotion between two hosts with different version?

  
  Hello

  Can I vMotion VM between two hosts with different version? For example, a virtual machine of esxi 6.0 5.5 esxi and esxi esxi 6.0 5.5 vMotion.

  Thank you.

  Yes, it will avoid you to move.

• vMotion (without shared storage) between two hosts with different vSwitches standard s VM

  I can VM vMotion (without shared storage) between two hosts with different vSwitches standard? The vSwitches on these two hosts have different names and number of NIC, but have the same name of portgroup.

  
  Thank you.

  Yes, you can in a Storage VMotion to one Esxi to another with no shared storage...

  It is important the portgroup bears the same name... This is the reference for the VM...

• Move a virtual machine to turn off between two hosts, shared storage

  Dear Experts,

  Please guide me for the next case. There are two hosts of Esxi, host 1 is Esxi 4.0 and host 2 is Esxi 4.1. There are store data SAN storage that is visible to both hosts.

  I watched solard winds VM monitor utility that hosting 2 consumes 90% of the memory while its processor is ok. On host 1 is normal. So, I want to spend only a few VM of to host 1. So please correct me if what I think are OK. I will turn off the virtual machine to be moved from host 2. Then I it will remove host 2 inventory. Then on host 1, I'll go to the data store in the folder that VM and do a right click on the file 'say add to the inventory' and now I'm going to see this virtual machine in the inventory of the host list, just turn on and everything is perfect, is this correct?

  Second question on the same hosts, there are a few other data stores that are visible to a host. As if this is the case there is a virtual machine on a data store that is visible to host 2 and I want to spend this VM to host 1 to reduce load on host 2. How to move this virtual machine because this data store is not visible to host 1? Will I have to copy this VM files in a data store that is visible to host 1? If YES then what real required to copy files?

  Kindly help me.

  Kind regards

  From your description I m assuming that you use not vCenter to manage your hosts, correct?

  If you have a store of data shared between two hosts you can do the steps you descripte (power off, remove the inventory etc.).

  For your second case there are several ways, it depends on where you want to place the virtual machine in the future. Wouldn't be on the shared data store that already exists or can in the local data store on the other host? Or is there an option to also display the current data store to host 1?

  If you want to copy the VM files copy the whole folder of it.

  Kind regards

  Mario

• The traffic between a host ESXi and vCenter Server is secure?

  Dear team,

  You pray let me know is traffic between a host ESXi and vCenter server (vice versa) is secure?

  The VC and ESXi version is 5.1U1a

  concerning

  Mr. VMware

  Default SSL certificates are installed automatically. However, you can configure the third-party SSL certificates to make the environment more secure.

  Please see:

  VSphere Documentation Centre

  http://pubs.VMware.com/vSphere-51/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-51-Security-Guide.PDF

• Communication between two hosts on the host only

  I have a host ESXi 5.5 with two reviews, a Linux / Centos 6.5 comments and a guest Server R2 2012.

  I've muddled through many questions - time zone, being the biggest problem, but am confused on how to get these guests to see one another, not even sure what to put in Google.

  My goal is to be able to share files between the two guests and access their consoles with putty and RDP, but I can't make them one ping to another. Everyone on the LAN can connect these two guests, but they cannot see.

  A kind soul told me that I forgot?

  Thank you

  Hey katycomputersystems,

  Could you give us a quick screenshot of your vSwitch / Port groups.

  Of the IP information you should be able to ping to each of the systems if they are on the same vSwitch / Portgroup / VLAN.

  Try this

  vSwitch0

  VM Network - Port Group - VLAN 110 - physical Nic don't matter we will keep all the VMS on this port group

  Configure all your VMS on the port network of VM group.  As long as all the VM living on the same port group vlan and vSwitch traffic should never leave this vSwitch and each VM must be able to communicate with each other.  If not you can always ping each other take off the VLAN and try again.  Make sure also that you have no firewall or tables ip enabled on the operating systems that could prevent communication.

  Let us know how it goes

• Replication between two hosts

  I have everyone,

  I have two hosts on the same site, in stand-alone mode, but within the same vcenter with licensing standards

  Each host has 3 VMS.

  Is it possible to replicate virtual machines each other on the same VirtualCenter and without cluster?

  Home 1 = VM1 + VM2 + VM3 & [+ VM4 VM5 + VM6 replication]

  Host 2 = VM4 VM5 + VM6 & [VM1 + VM2 + VM3 replication]

  I have enough drive and it will be very safe to run the replicates in minutes in case of problems with a single host.

  Thank you,

  Hello

  If you are using vSphere 5.1, yes you can use Standalone VMware vSphere replication, since vSphere that replication is included in the standard Lincenes.

  http://www.VMware.com/products/Datacenter-Virtualization/vSphere/compare-kits.html

  Short video on the replication of vSphere

  http://blogs.VMware.com/vSphere/tag/vSphere-replication

  See this link for configuration

  http://www.yellow-bricks.com/2012/09/17/back-to-basics-install-configure-and-use-vSphere-replication/

  Concerning

  Mohammed

• VLAN between two routers

  Hello. I am trying to solve a practical problem and I can't seem to deliver the VLAN. The presentation is as follows:

  You have two two routers connected to each other. Each router has a switch and each switch has four related generic PC. Each PC on this switch belongs on its own VIRTUAL local network. Thus,.

  Switch 1	Switch 2
  PC A - VLAN 10	PC E - VLAN 10
  PC B - VLAN 20	PC F - VLAN 20
  PC C - VLAN 30	PC G - VLAN 30
  PC D - VLAN 40	PC H - VLAN 40

  So A PC on the router/switch 1 1 can ping ROUTER2/switch 2 E PC and it cannot ping all the others. So on and so forth.

  So I tried to adjust the C VLAN 10 PC to check if the configuration of my work, and it does. But then I tie my router and sub interfaces, set the fa0/1 interface on my switch such as trunk and permit VLAN 10, 20, 30 and 40. Now, all PC on the router can ping each other! That should not happen. Now I don't know what the problem is. Can someone help me?

  I have attached the docx and the tracer file package.

  Sorry that I just realized you don't want connectivity between all computers.

  Which is a relief, because watching your Setup, I didn't see why they wouldn't be able to :-)

  You must use the ACLs on your subinterfaces to allow only the traffic you want.

  If you want to allow any PC from any other PC on the same site to ping but only the PC in the same vlan on the other site, then use an outbound acl on the router serial interfaces.

  If you only want to allow ping between the PC in the same vlan ACL use traffic entering on the subinterfaces.

  Jon

• Two hosts ESXi vs 1 NAS

  Hello

  You can connect two 5.5 esxi hosts to the same LUN on 1 NAS?

  Hey,.

  Looks like you need to configure your QNAP to allow multiple iSCSI connections to the same LUN. Can be disabled by default.

  Concerning

  Tim

• Having a problem with vmotion between two hosts with processors Intel E5640

  Hi all.

  We organize a group of 14 guests, each with ESX 4.0, build 261974 installed.

  They are managed through vCenter 4.0.0 and construction 258672, vSphere client 4.0.0 builf 258672.

  The hosts are blades from IBM, in a BladecenterH.

  Some of the blades are older model HS21 (type 7995) with processors Intel Xeon E5440.

  The rest of the blades are more recent model HS22V (type 7871) with processors Intel Xeon E5640.

  We are currently replacing old HS21 blades with more the HS22 blades, so we just bought 7 HS22s, all with the same Intel E5640 processors located in the blades currently in service. One of the things that this transition will happen for us is allowing us to have the same processor type in all of our blades and remove vMotion compatibility problems we had in the past. We were unable to turn on CVS, because we would have had to shut down a cluster of virtual machines on the latest hosts and could not take this kind of failure. We will turn VCA after that.

  Here's the question:

  We just installed the first new knives, and when turn on us and try to vMotion VMs to it, it fails. He gives us the error standard vMotion on CPU register incompatibilities, and that we should read kb1993. The thing is, they all have the same processor. Same identifier type, same everything, yet for some reason vCenter is convinced they are incompatible. We checked things in BIOS, and they are all the same.

  We are ideas, other than the new knives have a later rev BIOS than the old ones.

  Any thoughts?

  Thank you!

  -Tim

  According to the missing pieces, http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5086963 should help you solve the problem.

  André

• Cannot migrate VM between 5.5 ESXi versions: the version of the product to the destination host does not support one or several CPU features

  We receive an error message that I am trying to make sense. I understand very well the notion of compatibility, CPU, CPUID, masking and so on, after working on a competitor hypervisor. However, this error seems wrong (or needs better wording) based on my understanding:

  Here is the message:

  ----

  A general error occurred: the version of the product to the destination host does not support one or several features of the CPU currently use by the virtual machine.

  Characteristics of CPUID level 0 x 1 'ecx' register are indicated with a '1' bit: x00x:xxx0:xx0x:x 000: x 0 11xx:00: 00xx:11xx

  ----

  
  

  This happened during the migration between two hosts ESXi with the same physical processors - in this case, a Westmere X 5650.

  
  

  The source host is on ESXi build 2068190 (5.5). The destination host is on ESXi build 1474528.

  
  

  The bits it seems to complain are:

  
  

  DTES64

  Monitor/MWait

  Cx16

  PDCM

  The punch line seems to be: "the product version of the destination host. However, I have trouble believing that support for these features have been added to ESXi between the two versions. If it were, VMware has been certainly silent about.

  For what it's worth, explicitly set us the CPUID masks in our virtual machines (no, CVS is not an option for us at this time.) This is the mask:

  CPUID.1.EAX = "00000000000000100000011001010001".

  CPUID.1.ECX = "00000010100110001110001000111111".

  CPUID.1.EDX = "10001111111010111111101111111111".

  CPUID.80000001.ECX = "00000000000000000000000000000001.

  CPUID.80000001.EDX = "00101000000100000000100000000000".

  cpuid.d.EAX = "00000000000000000000000000000000".

  cpuid.d.ECX = "00000000000000000000000000000000".

  cpuid.d.EDX = "00000000000000000000000000000000".

  Note that the bits of the message complains (2, 3, 14, 15) * are * in fact forced to '1' in our mask of cpuid.1.ecx. That means (if I understand correctly), ESXi does not have the virtual machine unless the host processor supports the feature. And in our case, the virtual machine will start with happiness on nodes, with both versions. It will be not simply migrate between them.

  So, long story short, is this a bug of ESXi? The error message is misleading? I understand something?

  Thank you

  
  Matt

  To use the masks feature VM in this way, you must replace all the 1 to your masks with-'s:

  CPUID.1.EAX = "00000000000000-000000 - 00-0 - 000-

  CPUID.1.ECX = "000000-0-00--000---000-000---".

  CPUID.1.EDX = '-000 - 0-0 - 0-

  CPUID.80000001.ECX = "0000000000000000000000000000000 -"

  CPUID.80000001.EDX = "00-0-000000-00000000-00000000000.

  cpuid.d.EAX = "00000000000000000000000000000000".

  cpuid.d.ECX = "00000000000000000000000000000000".

  cpuid.d.EDX = "00000000000000000000000000000000".

  Zeros erases the features that are not available on your hosts Westmere, and dashes will leave the other one features.  The problem with those masks was forced to you certain features on who would have normally been off.

• VMotion on two hosts

  We have two hosts and are currently using the same network/vswitch vmotion and vm management.

  I understand that it is best to separate the network for vmotion management.

  (1) may simply run a straight cable between two hosts?

  (2) should the vmotion switch be in a separate network?

  Based on the number of physical network interface cards in your host, instead of connecting the two hosts directly without switch, allows to isolate the vMotion traffic and management VLAN and given that you're going to use a VLAN different you will need a different subnet (network).

• IPsec VPN between two routers - mode ESP Transport and Tunnel mode

  Hi experts,

  I have this question about the Transport mode and Tunnel mode for awhile.

  Based on my understanding of 'Transport' mode is not possible because you always original "internal" private in the IP headers or IP addresses. They are always different as public IP on interfaces enabled with Crypto Card addresses. When encapsulated in the VPN tunnel, the internal IP addresses must be included or the remote VPN router won't know where to forward the packet.

  To test, I built a simple GNS3 with three routers laboratory. R1 and R3 are configured as VPN routers and the R2 must simulate Internet.

  My configs are also very basic. The R2 is routing between 1.1.1.0/24 and 2.2.2.0/24. It is defined as the gateway of R1 and R3.

  R1:

  crypto ISAKMP policy 100
  BA aes
  preshared authentication
  Group 2
  ISAKMP crypto key 123456 address 2.2.2.2
  !
  Crypto ipsec transform-set ESP_null null esp esp-sha-hmac
  !
  10 map ipsec-isakmp crypto map
  defined peer 2.2.2.2
  transformation-ESP_null game
  match address VPN

  !

  list of IP - VPN access scope
  ip permit 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.255
  !

  R3:

  crypto ISAKMP policy 100
  BA aes
  preshared authentication
  Group 2
  ISAKMP crypto key 123456 address 1.1.1.2
  !
  !
  Crypto ipsec transform-set ESP_null null esp esp-sha-hmac
  !
  10 map ipsec-isakmp crypto map
  defined peer 1.1.1.2
  transformation-ESP_null game
  match address VPN

  !

  list of IP - VPN access scope
  Licensing ip 10.0.0.0 0.0.0.255 192.168.1.0 0.0.0.255

  I configured transform-"null" value, while it will not encrypt the traffic.

  Then I tried the two 'transport' mode and mode "tunnel". I ping a host in the internal network of the R1 to another host in the internal network of the R3. I also tried 'telnet'. I also captured packets and carefully compared in both modes.

  Packets encapsulated in exactly the same way!

  It's just SPI + sequence No. + + padding

  I will attach my screenshots here for you guys to analyze it. I would be grateful for any explanation. I confused maybe just when it comes to the NAT...

  I guess my next step is to check if the two modes to make the difference when the GRE is used.

  Thank you

  Difan

  Hi Difan,

  As you point out the mode of transport is not always applicable (i.e. applicable if IP source and destination is equal to corresnpoding proxy IDs).

  A typical scenario in this mode of transport is used:

  -Encryption between two hosts

  -GRE tunnels

  -L2TP over IPsec

  Even if you set "transport mode" this does not mean that it will be used. IOS routers and I blieve also ASA will perform backup even if the mode of transport is configured but does not apply in tunnel mode.

  I can take a look at your traces to sniff, but all first can you please check if you transport mode on your ipsec security associations? "See the crypto ipsec his" exit you will show the tunnel or transport mode.

  HTH,

  Marcin

• VMotion between 2 Hosts with different processors

  Hallo,

  I have a server in my homelab I use for studies of VMsphere and I want to get a second machine to test advanced features such as HA, Vmotion etc.

  My first server has a map of X9SCM-9 with processor Xeon E3-1230V2 (Ivy Bridge). I am currently running ESX 5.0 U2 on it.

  I was counting on obtaining of material quality for the second host consumers because I don't want to spend a lot on it, so I thought that I need any CPU generation Ivy Bridge.

  I tested today with a second machine with a Pentium G2020 Ivy Bridge, but when I try to Vmotion he says "the virtual machine requires physical features that are not available or disabled on the host... ».

  So I figure there must be a difference in architecture regardless of the CPU beeing an Ivy Bridge CPU.

  When I try to activate CVS it just me are going to the 'Nehalem' Version so my virtual machines running on host 1 would not be able to use all the features of the CPU since the Xeon.

  So the question boils down to: what is the processor less which offer compatibility VCA L5?

  Or is there something else to consider in VMotion between two hosts with different processors?

  I got a shared storage, etc. of the same network configuration.

  Thank you

  Benjamin

  Hi Benjamin,

  For compatibility VCA L5 want to look at one of the following models, Intel CPU:

  • Ivy Bridge: Series E3-1200-v2
  • HASWELL

  I would recommend mental health that before rushing and a CPU purchase, check if a cheaper option would be, as Jon mentions in suppresss some fo the CPU compatibility checks so obviously, this is not desirable in a production environment, and must be applied in your study of VMware Lab to the home address.

  Hope this helps,

  Simon

  TechHead

  http://techhead.co