ESXi 4.1 or ESXi 5.0 with iSCSI SAN

Similar Questions

• 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.

• The use of frames with iscsi SAN

  Hello

  We are moving our warehouses of local DAS to a SAN iscsi in common.

  We will have two physical hosts (1 ESX 3.5 and an ESXi 3.5) with two iscsi devices (1 DELL MD3000i and 1 openfiler 2.2 "in the home-built') and two dedicated switches (a 16 ports GBit 1216T one one port 8 Gbps unmanaged Linksys Dlink).

  Both iscsi devices have connections ethernet redundand (Dell has 4 ports on 2 different controllers, openfiler has 2 ports), so I planned to distribute connections on two switches for redundancy.

  each ESX and ESXi physical hosts have 2 ethernet NIC dedicated to iscsi

  My doubts/questions are:

  -is the switch 'Office' of linksys OK for this configuration? Or should I get a second Dlink 1216 T?

  -J' need to have the Dell MD3000i to least performance that we conduct with the local SAS DAS storage.

  Can I activate "frames" switch and Dell MD300i? What ESX and ESXi? and linksys switch (will it work with thaat jumbo mtu)?

  -If I DO NOT activate the Jumbo on openfiles iscsi, will it work with standard MTU even if it is connected to the switches with active Jumbo?

  -should I 'team' toghether both connections ethernet in iscsi on the physical ESX/ESXi hosts?

  an another question I have is:

  -We currently have a LUN iscsi on device openfiler which is accessible using the initiator Microsoft iscsi sw inside a win2k03 virtual machine on the host ESX 3.5. Can I disable initiator Microsoft iscsi inside the virtual machine, log on to this LUN using ESX iscsi sw and have win2k03 to find all the data?

  Thanks in advance

  Guido

  Take a lok at it to your specific questions

  http://communities.VMware.com/thread/107173

  And for an overview of ISCSI on ESX reading this, when you get a chance.

  http://virtualgeek.typepad.com/virtual_geek/2009/01/a-multivendor-post-to-help-our-mutual-iSCSI-customers-using-VMware.html#more

• Config network initial ESX with iSCSI SAN

  Hi all

  I want to install 2 ESX 3.5 servers which will be connected to an EqualLogic iSCSI SAN.

  The SAN is on a VIRTUAL, 10.x.x.200 with a 255.255.255.224 LAN Gateway.  This VLAN is not routable, DNS servers, etc.

  What I am trying to understand, it's for the initial setup of ESX, when I set the config network (console), should I register the IP address for the VIRTUAL LAN, example was:

  IP address: 10.x.x.201

  Gateway: 255.255.255.224

  Primary DNS: white

  Secondary DNS: white

  Or, for example B, should I use our 'public' speaking:

  IP Adress:129.x.x.201

  Gateway: 255.255.255.0

  Primary DNS:129.x.x.1

  Secondary DNS: 129.x.x.2

  I know that with the VIC, I can later add vSwitches, etc., but at least for the initial installation, I want the configuration to provide smoother operation. Thanks for any idea that you can provide!

  Chad

  Hello and welcome to the forums.

  What I am trying to understand, it's for the initial setup of ESX, when I set the config network (console), should I register the IP address for the VIRTUAL LAN, example was:

  Use example B (129.x.x.x) for the Service Console (management functions), and after that the system is in place to add an another vSwitch used to connect to the SAN VLAN.

  Good luck!

• 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.

• The upgrade to ESXi 4.1 with storage iSCSI software to ESXi 5.5

  I intend to upgrade ESXi 4.1 with which I have attached to ESXi 5.5 iSCSI software storage

  I've updated all my guests who were on the SAN storage with no problems.

  I would like to know that if it there's nothing I should take care before I update the host connected iSCSI to ESXi 5.5, as for the hosts with SAN attached storage I made to remove the cables of SAN before upgrading the host.

  Also, if all known problems, you will be informed during the upgrade to ESXi 4.1 to ESXi 5.5 with iSCSI Software storage, please let me know?

  If there is no different process to upgrade coz in ESXi 4.1 I do not see this link ports of iSCSI vmkernel ports software iSCSI but I know in ESXi5.5 we have to or I just launch a procedure of standard upgrade via the Update Manager and everything will be taken care?

  Thanks in advance

  With ESXi prior to version 5, linking ports had to be done via command line. However, if it has been configured correctly, you should be able to upgrade to ESXi 5.5 (assuming that the host has not been previously updated since version 3). BTW. the last time that I disconnected the host of storage for an upgrade has been with ESX 3.0.

  André

• 5.0 to 5.5 with iSCSI ESXi ESXi

  I have some servers ESXi 5.0 with iSCSI configured for my storage. If I'm on 5.5 ESXi, should I reconfigure the iSCSI? If so, how differente different is the configuration? I know that we had to set up when we went from 4.x to 5.0 ESXi ESXi and the configuration options are very different. Is this the case with the new version?

  No, you stay within the same major version and it should work without any problems. ESX ESXi (i) 4-5 were important steps, they are smaller. Made this upgrade in environments of production before without any problem or reconfiguration.

• Connect two VSphere ESXi 5.0 with crossover cable

  Hi all! A newbie in the ESXi 5.0

  I configured both servers of VSphere ESXi 5.0 with two network adapters on each server, the first NETWORK card acts as a virtual Internet switch, and the other NETWORK adapter serves only the link of communication (Heartbeat) between two VSphere Esxi 5.0 using crossover cable.

  My question is, how can I create such change in VSphere in a problem of communication between these 2 servers with a crossover cable? I would like to connect my (CentOS 6) VMs on each server via this network adapter with cable modem Simulator for the purposes of the communication of pulsation. I know how to create a normal vSwitch who can communicate with the Internet, but I have no idea how to create a switch for the NICs connected with a crossover cable.

  Please drop me a line if you know how.

  P.S. The idea to use the crossover cable rather than use the simple ethernet cable is the cable eliminates the overhead and to avoid the lack of packages due to the processing time of the switch.

  I know not how to create one with ordinary vSwitch to establish a connection with the Internet, but not this vSwitch with crossover cable.

  There is no difference. Build a vSwitch as your normally would, including the NETWORK card that is connected via a crossover as your uplink cable.

• Implementation of storage fibre channel (ESXi 4.1) with jumbo frames

  I'm looking for 'official' instructions for the activation of the jumbo on a host ESXi 4.1 with storage fibre channel frames. I don't know if the instructions are different, or if anything else needs to be adjusted according to your storage space.

  I looked at the instructions from this page here and it seems simple enough. It also seems that you can keep your groups of existing ports rather than having to delete and then recreate. If these good enough instructions apply it for the side host?

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1003712 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 322680138 & StateID = 1% 200% 20322684038

  I saw this page for iSCSI storage so that made me think if the procedure differs according to the storage.

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1007654

  Wasisnt wrote:

  What is the reason for having to recreate them?

  If you are in 4.1 that you don't need to recreate anything, just activate via the CLI.

  And you can enable frames on a standard port group or is it just for VMkernel port groups?

  You can turn on the VM and vmkernel exchanges. Together you must also make the "virtual cards", i.e.: on the Vmkernel virtual network cards and cards of virtual network in the guest operating systems. On the Windows 2003 server, I think you have to use VMXNET3, but on Windows 2008 the e1000 should support frames too.

  As has been noted before just make sure that any layer two devices in the path is configured to allow the large frames. You can use this to confirm both Vmkernel and invited: http://rickardnobel.se/archives/992

• DataCore DataCore-V with ESXi, vSphere 4.1 iSCSI running

  I have looked everywhere and come short on my problem, if this is a problem?  In the past, I have always connected all ESX / ESXi host through corn and now I work more with iSCSI.  I always try to get a handle on it.  It's one thing to read about iSCSI and he put in place of the other.  OK, now that I have that came down my chest, here is my question.

  Should the two iSCSI connections in DataCore-V show ready if I have both connected?

  Here's a high level race down the environment.

  1. a single node of DataCore

  2. a single ESXi host

  3. the two dual iSCSI ports

  4. on the DataCore node, only one port shows ready

  5. on the ESXi host two connections show connected

  

  Help, please

  Hello

  To meet ask you: It will say connected when a host 'iSCSI IQN init' is connected, simply because he says tell-connected does not necessarily mean that the 'network' is down... The host/s are not, cannot connected. (or none have been configured).

  More information about your configuration will be useful, however check over the info / recommendations below (Simple config)

  1. you set the "Port" Type for the two iSCSI ports on the DataCore for "FE" "Front End" Server?

  2. you have defined two separate IP addresses for the iSCSI on DataCore iSCSI ports ports?

  3 for simplicity on the ESX host, you have two distinct vSwitches for iSCSI with a NIC each with a vmKernel configured with IP to talk to the DataCore "target Ports.

  Therefore to confirm you can test the interfaces between them... now connect connection to DataCore target ports

  If you use software iSCSI Init, enable it on the ESX host... then you will need to "Discover" ports "targets" (static or dynamic)

  Once you add the two DataCore target Port IP please make sure that you "Login" for them to the ESX host. (BOTH)!

  If it worked, now you can join the 'Host' ESX in DataCore-V interface and assign the "iSCSI initiator" (from the ESX host) to it. (Only will be there for iSCSI Software...

  Now, remember, there is that a single iSCSI Software initiator, the important thing is to make sure this initiator is recorded in the TWO ports of DataCore target... Check the DataCore-V 'Remote Ports"tab on each port of 'target' for the IQN of the ESX host name.

  NOTE: DataCore servers don't support not multiple sessions to the same IQN to a vSphere Host to a unique DataCore iSCSI Target

  XXXXXXXXXXXXXXXXXXXXXX

  Also, please see best practice information about DataCore for your settings of the NETWORK adapter on the server of DataCore.

  the iSCSI traffic should be strictly separated from the public network (user).
  Use a separate hardware (LAN switches) to traffic storage iSCSI or less different virtual LAN (VLAN).
  Use separate NICs for iSCSI and inter-stockage server and communication management.
  Disable any other protocol or service except for "Protocol Internet (TCP/IP)" on the network adapters used for iSCSI. See help guide for detailed instructions.
  3260 port must be open on the firewall to allow the iSCSI traffic.
  On storage servers DataCore as well as disable Application servers/hosts these settings because they can cause disconnections and performance problems:
  Disable AutoTuning on W2K8: netsh interface tcp set global autotuninglevel = disabled
  disable RSS feeds: netsh interface tcp set global rss = disabled
  disable the TOE: netsh int tcp set global chimney = disabled

  Let us know how you and perhaps give a bit of monitoring more than info...

  Best regards

  Bernie.

• Cannot Connect to Host ESXi 4.1 with browser or Client VI

  Hi, I have a strange problem which has persisted since I first installed ESXi 4.1 on a server. First my setup:

  • ESXi Installable on a HP DL380 G6 server, 32 GB of RAM, 4xEmbedded NETWORK ports, Port NIC, 2 iSCSI x QLogic QLE4060C HBAs 1xDual adapter

  • HBAs configured for Jumbo and static IP frames but except that all the settings are default

  We have installed ESXi 4.1 with only the built-in port #1 connected to the switch. Everything went well and we were allocated the only active NIC (vmnic0) as the management interface. Once installation is complete, we were able to connect to the management interface using a browser and the VI client.

  We then connected NETWORK card and remaining HBA ports to the switch without loss of connectivity to the management interface. During our next restart we could no longer connect directly to the host using a browser or the VI client but could still ping the IP.

  We tried to restart the management agents, but it did not help.

  Here are the different startup scenarios, we tested and the results:

  Scenario #1 - Boot with built-in NICs, DP adapter cards, network and HBAs connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = NO

  Even if we try to unplug the adapter DP and HBA ports after starting we still cannot connect to the management using the Explorer or the VI Client interface. A reboot is required, and the script #2 or #3 must be followed.

  Scenario #2 - start with only the embedded and DP adapter NIC connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = NO

  If disconnect us the two ports of adapter DP we can then connect to the host via the browser or the VI client without having to restart. We can reconnect them and we continue to have access to the host, and everything is fine.

  Scenario n ° 3 -Boot with only the NIC integrated, including the Mgmt NIC connected to the switch.

  • Can we ping the IP of host of Mgmt? = Yes

  Can • we consult to the IP host of Mgmt or connect using the VI Client? = Yes

  Then we connected the DP adapter and the adapter port HBAS to the switch and all the connectivity was very good. This scenario is our solution for now.

  Other information

  The QLE6xxx ESXi module takes about 5 minutes to load during startup, when the HBAs are connected to the switch, but it loads successfully. Not sure if this is normal or not.

  Thank you in advance for your help!

  Paul

  This looks like a very unusual network for me configuration.

  Could you post a screenshot of virtual network configuration and add a few comments on the different configuration of the vSwitches and uplink connected.

  If I understand correctly that you have at least 3 vSwitches (management, virtual machines, and iSCSI), however, from what you wrote so far I do not completely understand how implement you.

  André

• VMware ESXi 4.0 with customization of Dell

  VMware this displayed on the download page of ESXi VMware ESXi 4.0 with Dell' customization 'yesterday. I installed it on a test server, a Dell m600.

  I use the free ESXi license at this time.

  I expect this version will include Dell OpenManage 6.1 as well as Dell custom drivers. After installation, I am unable to connect to https://esxi_server:1311 (i.e. port OpenManage).

  Issues related to the:

  1. Nobody knows exactly what is in this custom version? Is it drivers and OpenManage?

  2. Assuming that OM is part of the customization, what should I do to make it work?

  3. When I finally get my license for vSphere Essentials (maybe more), it'll work with this ESXi installation (just change the license number to authorize a vSphere Essentials managed node? or is it a completely separate ESXi install media for this product)?

  See further discussions on http://communities.vmware.com/thread/220783?tstart=0

  It contains all the necessary information to configure OpenManage 6.1 on ESXi 4.0.

  Earlier with ESXi 3.5, OpenManage component has been incorporated into the ISO image

  but leaving ESXi 4.0, VMware has introduced a new concept called Vsphere Bundle (VIB) Installation and allows end users download files VIB and install it on ESXi 4.0. If Dell has begun to post their OpenManage as a VIB component in support.dell.com.

  All these information as download OpenManage, OpenManage configure and get Web page OpenManage are discussed above mentioned thread in detail. Let me know if you have trouble with running Openmanage on ESXi 4.0

• Problem with ESXi 3.5 host or our iSCSI SAN

  Hello

  Last week, twice we came into work and notice that some virtual machines on a host somehow the bomb and break the connection or work habit and are turned off.  It happens with mutiple errors, but we are not sure if it's the host itself or iSCSI SAN is too connected a NETgear ReadyNAS.  All the vmdk and vmx VM files are on the SAN storage are loacted here for targets.  Your opinion on this if someone could help determine what may be the question, please, thank you?

  Welcome to the forums

  I edit your images and delete the business credentials. There is a security risk that you should not expose.

  Take a look at the following.

  http://communities.VMware.com/message/1333118#1333118

• ESXi 5.5u1 added iscsi storage adapter - reboot and now vSphere Client could not connect to "my ip" an unknown error has occurred.  The server could not interpret the customer's request.  The remote server returned an error (503) server unavailable

  I have not yet connect to an iSCSI target device.

  I can ping my host

  when I open http:// "hostip" in a web browser, I get a 503 service not available.

  restart the host gets me nowhere.

  SSH opens somehow, but can not connect

  Console seems OK

  vSphere Client can not connect

  If I reset to the default values of the console it is ok, but when I reconfigure the host, this error will be returned.

  I tried to reinstall from DVD

  I'm completely corrected to date via SSH esxcli

  This happens on both my hosts, although they are almost identical Lenovo thinkserver TS140s with broadcom 10Gig NIC and intel NETWORK card integrated

  It almost always seems to happen the next time I reboot after enabling iscsi support

  The only weird thing I have is that my Integrated NIC is a processor intel 217's and I have to use a special VIB so that it can be used in ESXi

  Customer's winning 8.1

  Here is my installation notes

  Install on USB/SSD stick with custimized ISO i217 NIC driver, reset the configuration and reboot

  Management NIC set to NIC0:1Gig

  IP management: hostIP/24 GW: my gateway

  DNS:DNS on windows vm1, vm2 Windows dns

  HostName:ESXi1.Sub.myregistereddomainname custom DNS Suffixes: sub.myregistereddomainname

  Reset

  Patch to date (https://www.youtube.com/watch?v=_O0Pac0a6g8)

  Download the VIB and .zip in a data store using the vSphere Client

  To get them (https://www.vmware.com/patchmgr/findPatch.portal)

  Start the SSH ESXi service and establish a Putty SSH connection to the ESXi server.

  Put the ESXi server in maintenance mode,

  example of order: software esxcli vib install /vmfs/volumes/ESXi2-2/patch/ESXi550-201404020.zip d

  Re install the Intel 217 NIC driver if removed by patch

  Change acceptance ESXi host sustained community level,

  command: esxcli software - acceptance-level = CommunitySupported

  Install the VIB

  command:esxcli vib software install - v /vmfs/volumes/datastore1/net-e1000e-2.3.2.x86_64.vib

  command: restart

  Connect via VSphere client

  -Storage

  Check/fix/create local storage. VMFS5

  -Networking

  vSwitch0

  Check vmnic0 (1)

  Network port group rename VM to the 'essential '.

  Rename management group of network ports for management of basic-VMkernel traffic.

  -Configuration time

  Enable NTP Client to start and stop the host. ntp.org set 0-3 time servers

  DNS and routing

  Start the virtual machine and stop

  -enable - continue immediately if tools start - stop - prompted action Shutdown - the two delay to 10 seconds

  Security profile

  Services

  SSH - startup - enable the start and stop with host

  Cache host configuration

  -Properties to start SSD - allocate 40GB for the cache host.

  Flashing warnings SSH:

  Advanced settings, UserVars, UserVars.SuppressShellWarning, change from 0 to 1.

  Storage adapters

  -Add - add-in adapter software iSCSI

  I think I saw that I was wrong.  In fact, I applied two patches when only suited. I started with 5.5u1rollup2 and then applied the ESXi550-201404001 and ESXi550-201404020.  Strangely I did not t o had problems until I worked with iSCSI.