Sunday 27 December 2015

Route Based on Originating Virtual Port ID

The virtual switch selects uplinks based on the virtual machine port IDs on the vSphere Standard Switch or vSphere Distributed Switch.
Each virtual machine running on an ESXi host has an associated virtual port ID on the virtual switch. To calculate an uplink for a virtual machine, the virtual switch uses the virtual machine port ID and the number of uplinks in the NIC team. After the virtual switch selects an uplink for a virtual machine, it always forwards traffic through the same uplink for this virtual machine as long as the machine runs on the same port. The virtual switch calculates uplinks for virtual machines only once, unless uplinks are added or removed from the NIC team.
The port ID of a virtual machine is fixed while the virtual machine runs on the same host. If you migrate, power off, or delete the virtual machine, its port ID on the virtual switch becomes free. The virtual switch stops sending traffic to this port, which reduces the overall traffic for its associated uplink. If a virtual machine is powered on or migrated, it might appear on a different port and use the uplink, which is associated with the new port.


Advantages

  • An even distribution of traffic if the number virtual NICs is greater than the number of physical NICs in the team.
  • Low resource consumption, because in most cases the virtual switch calculates uplinks for virtual machines only once.
  • No changes on the physical switch are required.



    Disadvantages

  •     The virtual switch is not aware of the traffic load on the uplinks and it does not load balance the traffic to uplinks that are less used.
  •     The bandwidth that is available to a virtual machine is limited to the speed of the uplink that is associated with the relevant port ID, unless the virtual machine has more than one virtual NIC.

Wednesday 2 December 2015

Horizon Mirage 5.0 Requirements


The Mirage Server and Mirage Management Server can be installed on the same machine or separate machines, depending on your design configuration, but they need to meet the following requirements:
  • Windows Server 2008 R2 (Standard or Enterprise) 64-bit
  • Windows Server 2012 Standard Edition 64-bit
  • Microsoft .NET Framework 3.5 SP1
  • Must be Domain member


Mirage Database
The Mirage Server and the Management Server both need to connect to a database. Mirage supports the following database engines:
  • SQL Server 64-bit R2 Express, Standard, and Enterprise
  • SQL 2012 SP1 Express, Standard, and Enterprise



Friday 13 November 2015

vCloud Air as Disaster Recovery



 VMware vCloud® Air™ Disaster Recovery is a recovery-as-a-service (RaaS) solution that offers VMware vSphere® customers the ability to protect their onsite business and mission-critical workloads and recover them in the cloud in the event of a disaster or disruptive event. vCloud Air Disaster Recovery core subscription can scale up to 500 VMs.

VMware vCloud Air Disaster Recovery