5.0 to 5.5 with iSCSI ESXi ESXi

Similar Questions

• Big problem with installing ESXi 5.5 on Cisco UCS M200 B3

  Hello

  I have a problem with installing esxi 5.5 on SDcard mounted in Cisco UCS B200 m3.

  ESXi Show map SD but when to start partitioning I question (attachment).

  If I install ESXi on HDD I don't see SDcard (even from the console).

  Thanks for any help

  h

  Marcel

  Hello

  Thanks for the reply but SDcard are clear. map of are new directly from Cisco.

  The good news is that I found a solution. I install the old version of ESXi (5.5 U1) and everything works fine

  Concerning

• Hot migration is possible with VMWare ESXi 5.1.0 without an ESX server management

  Hot migration is possible with VMWare ESXi 5.1.0 without an ESX server management?
  I wonder for a future issue, a scenario where a system administrator must build a Win2008 + DC on local storage, server
  then, once the physical box is integrated into the class network, the physical box is connected to the classified SAN storage.
  Is it possible to hot - migrate the server Win2008 + CC local storage to SAN storage at this time, with only the
  free version of VMWare ESXi 5.1.0?

  Welcome to the community - I guess that you are looking to do this, while the virtual machine is currently running - this is not possible without a management server, also called vCenetr, but all is not lost because you would be able spend the VM local storage to the San with the VM posered using the client storage management features

• Problem with my ESXI

  I have problem with my Esxi 5.0.when, I installed whenever I got a message.like like NO ADAPTER NETWORK NOT FOUND error in my ESXi software.

  How reslove it .or how to upgrade the lan installation software. Please give the correct soluction.

  A tried

  I activated the lan in the bios

  It could also be that your NETWORK adapter driver is included in the ISO file.

  If you NIC are supported (on the HCL) then you can simply load the appropriate driver or create an ISO custom (with the help of the image generator) with the correct driver added.

  Here are some links that you can check:

  Image generator:

  http://www.YouTube.com/watch?v=AfjEyB2FTwc

  http://virtualbill.WordPress.com/2011/08/19/VMware-vSphere-5using-Image-Builder-for-custom-installation/

  http://pubs.VMware.com/vSphere-50/index.jsp?topic=/com.VMware.vSphere.install.doc_50/GUID-C84C5113-3111-4A27-9096-D61EED29EF45.html

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2005205

  Custom ISO

  http://www.ivobeerens.nl/2011/12/13/VMware-ESXi-5-whitebox-NIC-support/

  Drivers:

  http://downloads.VMware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere_hypervisor_esxi/5_0#drivers_tools

  BR

  A. Mikkelsen

• VCenter Server with VMWare ESXi free 5 5

  Hi all

  Test the VCenter Server 5 Evaluation (60 day trial) to management all my 5 of VMWare ESXi (free license). It works with restrictions. These restrictions aren´t a problem for me. I need only to move (power off of virtual machines), clone, create templates for and organize my servers in a single interface VSphere Client. So, I would like to know what type of license of VCenter Server 5 woks if VMWare ESXi 5 free. Buy the VCenter Server 5 Standard?

  Another doubt is if VStorage works with VMWare ESXi free license I.

  Best regards

  Fabio Sobral

  Unfortunately the free ESXi hosts in vCenter management is not possible (except for the eval). The hosts of ESXi need a vCenter Server Agent license that is only available in editions 'paid' of ESXi.

  André

• VMotion with ISCSI

  Hi all

  I do my first vSphere deployment and I have a question about the network requirements for VMotion. I currently have 1 physical switch with iSCSI traffic THAT VLAN has had to reduce the broadcast storms. We will get a second switch at a later date.

  I have one EqualLogic PS4000XV SAN she has 2 ethernet ports 1 Gbps active on this issue.  And 1 management port. I read that it is preferable to assign another VLAN to dedicate to VMotion, my question is, I have to assign 1 port on the VLAN ISCSI SAN and another port on the SAN to the VLAN VMotion? Because I prefer to keep them on the same VLAN so I can set for some extra speed LAG.

  I suggest using different VLAN and if possible, also different NICS for iSCSI and VMotion.

  See also: best practices for design vSwitches and NIC cards

  André

• Intel® PRO/1000 PT Dual Port Server adapt (PCI Express) with ESX/ESXi 4?

  Hello

  I try to work to the next with VMWare ESXi 4 card worsk.

  The card is the

  Intel® PRO/1000 PT Dual Port Server adapt (PCI Express)

  Who uses the: Intel® Gigabit controller 82571 GB

  However, in the VMWare HCL, he mentions the Intel 82571EB Gigabit Ethernet controller

  These are two elements compatibile, if VMware ESXi will work with this card?

  I am hoping that someone out there has tried it can give me an idea.

  Thank you

  Ward.

  Virtually all Intel devices are supported...

• Anyone run a Terminal servers virtual with VMware ESXi 3.5 If Yes please share your experiences?

  Hello guys,.

  We are runnig Terminal Server with Windows Server 2003 Ent in a cluster environment (TS 7), we plan to go with VMware ESXi 3.5 to virtualize the TS. Does anyone have any kind of experiences that can help make a decision?

  Thank you.

  Keep an eye on the side esxtop ESX and see your % RDY meters in this output.  Don't forget, as underlined chamon, with high vSMP values do not match always the best performance.  Typical scenarios citrix/ts use 1-2 vCPU for more effective results.  If you bump up to a larger number of users, you also want to watch the overcommitt on your processors and vCPUs in the box.  Many users a lot of switching and use heavy context on the processors for the management of the OS and the user.  1-2 vCPU seems to be the sweet spot.  What kind of applications are underway within the environment?

  -KjB

  VMware vExpert

• Nested ESXi 5.5 lab for the SRM demo with iSCSI

  Hi all

  I was wondering if it is possible to install ESXi in ESXi 5.5 5.5 make recovery of the Server Tier - 1 Microsoft with Site Recovery manager?

  So level 1 server applications are: Exchange Server, SQL Server, SharePoint Server and AD DC servers with 5 x test Win 7 desktop.

  The external data store to the VMFS will take place by iSCSI NAS connected to the physical server.

  Any suggestion and input would be greatly appreciated.

  Thank you

  One thing you'll want to do is to make sure that use you VSphere switches distributed on your cluster nested to ESXi hosts so that you can use the network i/o control (NIOC). For me, I put iSCSI to high priority traffic and everything to normal priority.

  With the help of the NIOC will allow your cluster nested in order to operate more fluidly than without it.

  My SRM 5.x laboratory is fully nested - probably not supported in a production environment where supported VMware should however.

  Here's a blog post of Ather Beg on its results by using the nested NIOC and ESXi hosts - it is the reduction of the spikes that Ather blog article shows that made work nested ESXi hosts networks so much better:

  http://atherbeg.com/2014/02/04/why-enabling-NIOC-network-IO-control-in-a-home-lab-is-a-good-idea/

  Datto

• ESXi 4.1 or ESXi 5.0 with iSCSI SAN

  Hello

  I'm trying to establishing an environment that is / will be an iSCSI SAN backend entirely.  I know of a lot of reading that the best practice is to config the ESXi host with:

  VMKernel > vmnic > physical network adapter > switch ports > port on SAN (config 1:1 - no grouping of vmnic)

  Environment:

  ESXi 4.1 & 5.0

  Force10 switches

  EqualLogic iSCSI SAN (PS4000 & 6000)

  Here's my real question (playing the Devil's advocate):

  Why I shouldn't team 3-4 vnmics on a vswitch with multiple vmkernel ports?

  Given my environment.  Can someone point me to a technical document that explains what will / could happen if I set up the environment ESXi in this way?

  Thank you

  BDAboy22

  So, basically, we want the SAN to take full responsibility for the failover instead of the network and/or the SAN for who should resolve the failure (which could lead to the time of restitutio in integrum longer session).   I understand that correctly?

  Yes, that's right, we want to stack storage for vSphere manage with path selection and tipping - and by connecting each vmknic directly to the physical vmnic map we sort of "simulate" how to CF cards and also ignores the network failover mechanisms. As you probably know you also need to "bind" the iSCSI Software to the two vmnic (GUI now in 5.0, esxcli in 4.x)

• How many network adapters I - ESXi 4.1 with iSCSI

  I was wondering if someone could help me give a sense the news I read on # NIC for ESXi 4.1.  I came across the following article, but I'm not sure I understand all parts of traffic that he speaks:

  http://livingonthecloud.blogspot.com/2009/09/ESXi-networking-best-practices.html

  At the moment I have 6 cards 1 GB on each of my 3 servers.  I connect to my SAN via iSCSI, so I know I'm going to need at least 2 of these network adapters for that traffic. I know I'll need at least 2 NICs for connection between my ESXi server and my switch to the network of the VM.  What I don't understand is what I really need for the VMKernel FT, VMkernal Vmotion and VMKernal the Network Administration.  I do not plan on using Vmotion very often at all, so I'm not concerned about its impact on my network.

  Any advice?  I need to replace my double NICs with Quad NIC card or is it exaggerated?

  The management doesn't have a dedicated network card. It can share the network with virtual machines cards.

  In this case the following configuration would be interesting:

  vSwitch0: (3 NIC uplinks) (assuming vmnic0, vmnic1 vmnic2)

  Port group 1 - networking (vmnic0 and vmnic1-> active vmnic2,-> stand-by)

  Port group 2 - network of the VM (vmnic0 and vmnic1-> active vmnic2,-> stand-by)

  Port 3 - VM Network Group (vmnic0 and vmnic1-> stand-by, vmnic2-> active)-for the "Pervasive SQL.

  vSwitch1: (1 NIC/uplink)

  Port group 1 - VMkernel for vMotion on a separate network (192.168.x.x)

  vSwitch2: (2 cards network/links rising)

  configuration by following the best practices of your iSCSI storage provider

  In this way the "Pervasive SQL" would have a dedicated NIC (vmnic2) and may switch to another NETWORK card in the event of disruption of the network.

  André

• SMB ESXi with iSCSI SAN

  I'm looking for make a SMB deployment for the clients of mine. The new features offered by 4.1 for SMB as VMotion and HA are now in their budget. I've seen DELl offering some broadcom with TOE and ISCSI unloading cards. I know that 4.1 now supports TOE cards, but these broadcom cards actually iSCSI HBAs or just TOE cards Motors iSCSI? VSphere 4.1 will support this card? Its much cheaper than buying full host bus adapters blown for a small business.

  I'd go with the R710 mainly because of the experience with the model and how strong they are. You will save all the money using the R610, so you could spec on a solid R710 for the host. In addition, the R710 has four GB of NETWORK map (with the option of TOE on the four) and four open expansion for multiple network interface cards and other slot. With the R610, you will have only two expansion slots. So if you want to add more cards later (more than two), you must either delete that you installed to make room, or do the purchase.

  I would always use the SAS drives on board to install ESX/ESXi on. You will save money by not getting NOT the HBA you can use to boot from SAN with the same (or similar) performance level. It also helps to isolate the questions when you're starting from local disks... I would go with a pair of 10 k / 15 k RPM SAS drives (2.5 "or 3.5", your choice there) on the RAID controller (using RAID 1 on them) support. Confirm with either your VAR or rep Dell to make sure that the controller is 100% compatible with VMware (or you check the HCL). They list the 146 GB drives in the Configurator (normal site of SMB) fairly cheap price.

  I'd also go with processors Xeon E5620 (get a pair inside the host) so you'll have plenty of CPU power. Get as much RAM as you can, using not more than 12 sticks (multiple of six).

  In fact, I have configured a R610 and R710 a using the SMB website... The R710 has the 146 GB (10 k RPM) drives the R610 has 73 GB 15 k RPM drives. The R610 comes out to almost $300 more than the R710. We're talking same memory (24 GB), TOE enabled on the built-in NETWORK interface, no additional NIC at build time (they would get another provider, getting Intel NIC, NOT of Broadcom), redundant power supplies, kits of rapid-rail (without the wire management arm), two-processor Xeon E5620, iDRAC 6 Enterprise (so you can do it all remotely, no need to use any KVM don't setup once configured the iDRAC 6). Both versions include the 5 x 10 hardware only (NBD onsite) support. I also put the hard drives RAID 1, so you have redundancy here.

  Seen readers on board, for ESX/ESXi is on will also configure the host much easier and will not require something special on the side storage. Otherwise, you need to configure up to the MD3000i to present the solitary start-up LUN to a host for ESXi. Everyone that I spoke with who implements guests, always with local disks. Especially if you are looking to save the ~ 1 k $ the HBA adds to the build (not to mention the extra complexity to things). I was talking with some people in charge of a large IBM virtual data center not long there. They were forced to boot from SAN on their hosts fear. They were forced to do so by higher ranking people within the company. It was decided that because it sounded good on paper, it would be good in practice. Initial tests have shown how much pain he would be, and they were not happy about the extra work required so that it can happen. Until VMware clearly indicates that booting from THE SAN is recommended to local disk (properly configured on either) I will continue to use local drives for ESX/ESXi reside opon. Even in this case, we have a significant performance win by going to the boot of model SAN. Maybe when 10 GB is on the environment as a whole, it will make sense. As it is, you get new SAS disks that are 6 GB, everything in-house, and you still beat the trunk of the SAN performance model. In addition, you don't need to worry about someone making something accidentily to the LUN you are booting from...

  Network administrator

  VMware VCP4

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

• Best practices for Exchange 2003 with VMWare ESXi 3.5 and iSCSI SAN

  Hello guys,.

  Here's the Q? We have 1 physical Exchange 2003, the HOST of 4 and 1 iSCSI SAN with LUN 3, 1 for data, 1 for VMWare and 1 for SQL, if we're going to virtualize it, I don't know where to put data Exchage and newspapers. I do not think that that is a good practice to put together the data but I do not have another SAN. So, what can I do?

  Thank you.

  We have 813 mailbox.

  I agree with cainics, start an average size and go from there.  I know it's a production mail server and you can not exactly 'play' with the settings because this requires time, but if you do the VM too big, you would have nothing left for other virtual machines.

  I would go 2 vCPU and at least 4 GB of RAM, maybe 8GB.  There must be parameters for the Exchange mailbox 813 and X users # to implement your environments in order to get an idea of the amount of RAM that will be... 4GB seems minimal to me, but 8 GB would probably be better like that.

• 2808 LAG for use with VMware ESXi and Linux collage

  I posted the month last about setting up my work with groups LAG http://en.community.dell.com/support-forums/network-switches/f/866/t/19537080.aspx servers (I'll effectively implementing implement this Saturday)

  I decided to buy a 2808 for my ESXi server get more aggregated connections to my staff iSCSI Linux server but now I'm worried I might have made a mistake to buy the 2808.

  After looking in the manual before I realized I could have been mistakenly assuming that the 2808 had STP and LACP, as I can't find LACP anywhere in the PDF file. I guess that the configuration of my Linux machine for 802.3ad is out (a hope to make mode 4), so now for the configuration of my house, I wonder (* 1 *) that I have to configure my VMware NIC team like and what mode of binding should I use on my Linux host? As for the section at the top (my working configuration) (* 2 *) I don't know what to do about the road other than the leave as 'route based on originating virtual port ID "? (This is how our other data centers are configured, but I'm waiting for my admin network as agglomerates ESXi hosts are configured with the channels of port on our cisco switches)

  For the House, I want to try to increase the bandwidth by using three NICs in each server, I was hoping that it works:
  VMware: Route of IP hash function?
  w/Linux: balance-alb?

  -VMware:
  Before you begin:

  • The default load balancing strategy is route based on the port virtual origin ID. If the physical switch uses the aggregation of links, route based on the IP hash load balancing should be used. For more information, see host requirements for the aggregation of links for ESX and ESXi (1001938) and the guide of VMware Virtual Networking Concepts .
  • LACP support was introduced in vSphere 5.1 on distributed vSwitches and requires additional configuration. For more information, see activation or deactivation of LACP on a group of ports Uplink using the vSphere Client Web (2034277).
  • Ensure that the Protocol of aggregation VLAN and link (if any) are correctly configured on the physical switch ports.

  -Linux:
  * Descriptions of bonding modes *.
  + Mode 0 balance-rr: Round-robin policy: transmit packets in the sequential order of the first available through the last high school. This mode provides load balancing and fault tolerance.

  + 1 active-backup mode: Active-backup policy: only one slave in the link is active. A different slave becomes active if and only if, the active slave fails. MAC address of the binding is visible from the outside on a single port (NIC) to avoid confusion between the switch. This mode provides fault tolerance. The first option affects the behavior of this mode.

  + 2 balance-xor mode: XOR policy: transmit based [(adresse MAC XOR avec destination MAC traiterait de source) modulo County slave]. This selects the slave even for each destination MAC address. This mode provides load balancing and fault tolerance.

  + 3 broadcast mode: broadcasting policy: transmits everything on all slave interfaces. This mode provides fault tolerance.

  + Mode 4 802.3ad: IEEE 802.3ad dynamic aggregation of links. Creates aggregation groups who share the same speed and duplex settings. Use all the slaves in the active aggregator according to the 802.3ad specification.

  -Prerequisite:
  -1.Ethtool support in the base drivers to retrieve the speed and duplex of each slave.
  -Switch 2.A which takes care of IEEE 802.3ad dynamic aggregation of links. Most of the switches will require some type of configuration to activate 802.3ad mode.

  + Mode 5 balance-tlb: Adaptive load balancing transmission: Channel link that doesn't require any special switch support. Outgoing traffic is distributed according to the intensity of the current (relative speed) on each slave. Inbound traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.

  -Prerequisite:
  -1.Ethtool support in the base drivers to retrieve the speed of each slave.

  + 6 balance-alb mode: Adaptive load balancing: includes balance-tlb plus receive balancing (rlb) for IPV4 traffic and doesn't require any special switch support. Receive load balancing is achieved by ARP negotiation. Link driver intercepts the ARP replies sent by the local system on their way and replaces the hardware address of source with the unique hardware address of one of the slaves in the bond as different counterparts use different physical addresses for the server.

  The topic dell nearest you, I have found a useful was: http://en.community.dell.com/techcenter/networking/f/4454/t/19415629.aspx

  my previous post was more concerned with VLAN tagging and spanning tree issues, but now I see I should have feared groups LAG it as well.

  Any help would be appreciated, thanks in advance all :)

  -

  PS. http://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/dell-powerconnect-2800-series-spec_sheet.pdf said that the 2800 series supports LACP, so if I'm worried about anything on my iSCSI side slap me please in the face, but I guess even in this case, I'm still not sure how to configure the ESXi host because it does not support LACP without vSphere and my original configuration is a free version , so I have no web vSphere management needed to make the LACP allow the change.

  Not sure if it is of no use: example configuration of EtherChannel / switches control protocol LACP (Link Aggregation) with ESXi/ESX and Cisco/HP (1004048), but that's where I was to base the choice on IP hash from.

  It must have the support of layer 3 to achieve IP hash, IP addressing is a 3-layer technology, so a 6200 series or higher or the soon to be released N3000 series.

• Can I use a custom with iSCSI TCP/IP stack?

  We have a group of 3 guests identical at each connection to the network through 2 natachasery using 2 vmks SAN. Each vmk resides on a separate broadcast domain so they belong to separate vswitches. No link is used in accordance with the guide of vSphere.

  Thus, as the title suggests, should I use a separate TCP/IP stack custom for iSCSI vmks? or leave them in the stack by default (even if it is not an option to mark the vmks as IP storage)

  As long as your vmkernel iSCSI cards and their respective iSCSI targets are in the same subnet of layer 3, i.e. you are not routing iSCSI traffic (vmkX<->TargetSPX vmkY<->TargetSPY separate subnet design iSCSI does not, apply as never before the traffic is routed between networks), OR you do not want to configure static routes customized for iSCSI targets in other subnets then there is no point in using a separate TCP/IP stack.

  The main point to use the new functionality of ESXi 6 with several TCP/IP stacks is to have a completely separate battery routing table. Most of the admins were not able to handle very basic layer 3 static routing with itineraries dedicated by subnet, so they assigned default gateways on several vmkernel NIC and I wondered why things broke or has never worked.

  It also allows better control what interfaces to send data when you have several paths of layer 3 or subnets to communicate with, but it's largely irrelevant and already a point an integral part of an iSCSI network fine grain.