Live iSCSI SAN upgrade production network (Dell MD3000i and PowerConnect & ESXi 4)

Similar Questions

• Reference Dell MD3000i and vSphere 5.5

  Actually I'm on vSphere 5.1. Running two servers of 5.1 on Dell R805 ESX and storage on a Dell MD3000i.

  Did anyone out there running vSphere 5.5 in combination with a Dell MD3000i SAN?

  Since the MD3000i is also not compatible with version 5.1 that I use.

  We run from separate md3000i 2 with of Dell R710.  I ran on vsphere 5.0, 5.1 and 5.5.
  The current host of 5.5 runs DR Veeam, so it has e/s of Veeam jobs but hosts only 2 running virtual machines.
  We spend 2 hosts of production 5.5 soon, do not anticipate any problems.

  Be sure to have the new firmware on the md3000i itself - the update of the firmware, I'm pretty sure that is very important for compatibility above 4.5.

  Rumors that I've heard of compatibility have been on failover - I still need to test the failover using network cables and forcing a failover to ensure that vmware panic.

• Reference Dell M620 and M820 ESXi 5.1 installation

  I'm relatively new to VMware on Dell hardware. The closest thing that I believe to a custom image is 'VMware ESXi 5.1 update 1 Image Recovery"(http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=RD5JN). I assumed it to be ESXi 5.1 update 1 with favorite Dell specifc driver packages. I had planned to use this new installs feeling that it would include the latest drivers for my Dell M620 and M820s and would be preferable to base VMware image.

  1. It is the support for the installation of these blades?
  2. The description says « Ce ISO image should only be used to restore/reinstall VMware ESXi on image for SD Card/USB Key on the supported Dell platforms. »
     • I am confused by the specification 'only' restore/reinstall and not install.
     • Also confused by the mention of the only card SD and USB to the apparent exclusion of standard hard drives.

  I installed with it as a test and it looks good, but I'm uncomfortable with the description. I would be grateful for any additional information or insight to those who support ESXi in Dell stores.

  Hi vmproteau,

  Here are my answers to your question based on my experience. I have no experience with the M620 or M820 I manages around 240 M610, 60 R710, the R720 10, so I am familiar with Dells ESXi 5.1 servers update 1.

  (1) Yes, I would recommend using the ISO provided Dell printer if you are not familiar with creating your own package with the necessary drivers and firmware.

  (2) this ISO standard will include all drivers for supported Dell servers and some customizations of Dell and can be used for new installations regardless of the storage (SD, USB or HD Local) option. I would like to look out for is mainly to make sure that you update the firmware on all of your blades with the most recent available by Dell that ESXi is very picky with the pilot and also incompatible firmware Dell CMC with thanks to a few mistakes from time to time.

  Kind regards

  CROD

• Reference Dell MD3000i and degraded physical disk channel

  Nice day

  We have a Dell MD 3000i with an extra box storage. And today, there are two mistakes in the journal:

  1 physical disk channel set to gradient

  Date/time: 30.04.13 10:56:14
  Sequence number: 9783
  Type of event: 1209
  Description: Physical disk set to gradient channel
  Specific event codes: 0/0/0
  Event category: error
  Component type: channel
  Location of components: side physical disk: channel 1
  Recorded by: Module to slot 1 RAID controller

  2. each physical disk - gradient path

  Date/time: 30.04.13 10:56:14
  Sequence number: 9784
  Type of event: 1513
  Description: Individual physical disk - gradient path
  Specific event codes: 0/0/0
  Event category: error
  Component type: channel
  Location of components: side physical disk: channel 1
  Recorded by: Module to slot 1 RAID controller

  In this case recovery guru say "you must contact your technical support representative to correct this defect. Do NOT try to fix this problem yourself. So, how we can receive technical support recommendations and try to repair this failure?

  If you need more details, we can put any storage array profile output.

  Hello UtkinE,

  Yes, you will need to stop all iSCSI traffic so that you can update the NVSRAM.  With the timeout error you get all came from controller 1 & he had only discs 1 & 5.  The current version of NVSRAM you version 4 and the last one which is for the MD3000i is version 13.  With who have older firmware it was improvements to correct your problem in the latest versions of firmware.  I also had one of our analysts will confirm as well just to make sure that it is the best fix for your problem.

  Please let us know if you have any other questions.

• 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

• Reference Dell backup and restore (Premium Edition) 1.7.5.63

  Since upgrading my software Dell backup and restore to version 1.7.5.63, I now have problems to make it past the "Dell backup and recovery Please Wait" screen.

  I'm not leaving this option to run for more than 8 hours, but found that this process is not always successful. The only way I could find to block this process to run is to click on the? at the top right of the screen, then select "activity log". At this time, I clicked on the home button to take back me to the Dell Backup and Recovery Premium Edition home page and close the application. However, when I tried to re - open the application again, it brings back me to the screen "Dell backup and recovery Please Wait".

  To solve this problem, I tried to restore from a previous backup I made of the Dell Backup and Recovery application but it failed miserably and corrupted my hard drive and operating system (Windows 8.1). So the only way I could get back to who had to go back to my backup bootable disks that I created when I arrived to my laptop Dell Latitude E6530.

  Then I had re-installed all the 100 + updates of Windows for upgrade to Windows Pro 8.1 by the Windows store. From there, I upgraded my software "Dell backup and restore (Premium Edition)" at 1.7.5.63 and had the same problem again.

  In any case to have a fix for this or tell me how I can raise an incident with Dell, because this is so ignorant and frustrating.

  If I uninstall my Dell Backup and recovery software (Premium Edition) and reinstall the version found in http://www.dellbackupandrecovery.com/en-us/Index.html , but the last time I did, it installed the basic edition and not the Premium edition.

  All right enough the last time I had problems with my Dell backup and recovery (Premium Edition) software, it seems to settle on the other updated after a few months, but I don't don't want really to go back to an earlier backup with an older version of the recovery (Premium Edition) software and backup Dell.

  Any help or advice, you would be extremely grateful.

  I'm shocked that Dell is detrimental to Windows backup in Windows 7 Professional.  Your comments here persuade me not to pay for the premium edition.  Various people on other internet research said Dell had a great program backup, 6 months ago, but weakened while it is able to sell a version Premium, also hobble the program backup Windows.  You might try a free backup software like Comodo as I suspect that you can not use the Windows backup which makes a backup with files image.  It was a very simple approach that Dell seems to have stuck in their new versions of Windows 7 Professional.  I restarted my computer because of this kind of game.  Since I bought it at Costco, I have 90 days to return it.  I also started watching a series of online backups.  Carbonite seems terribly clutter my computer, and while highly recommended, it is slow, slow, slow.  I am CrashPlan that seems to work much much much faster.  Both of these are paid services.  CrashPlan has a lot of versatility to accommodate beginners to evolve into something much more powerful.  They have free versions for recording to hard drives and other computers.  The online version has Unlimited storage, much versatility, without the limits other plans have, and it's only 4-6 dollars per month, depending on the current sales and payment terms.

• To access ESXi 4 Update 1 custom server from dell MD3000i iSCSI SAN

  Hello

  I'm brand new on VMware ESX/ESXi products and for the most part, no.  I configured several machines virtual with server 1 and 2.  I am trying to connect a virtual ESXi 4 server in a SAN and starts to become very confused about what I can or not do.  I hope that someone here can break it down for me because I couldn't find the answer to my specific questions.

  Here's how I'm Setup:

  I have a Dell PowerEdge R710 with ESXi 4 Update 1 'Custom Dell' (whatever that means) is installed.

  I have a Dell MD3000i SAN using iSCSI with a pre-configured dedicated virtual disk.

  I would like to create virtual machines on virtual disk said.

  I think that ESXi 4 is completely free.

  It seems that to manage the server, I need to use 1 of the 2 products.  The Vsphere client or web application of VMware Go.

  If I use Vsphere:

  I have the ability to add a type of storage through the user interface.

  I'm on a 60-day trial. I thought that it was free.

  If I configure my iSCSI via Vsphere and then the eval expires... what happens?  All jump on me and then I have to purchase a license to get it back?

  If I use VMware go:

  It seems I don't really have any options to do any kind of configuration iSCSI in VMware Go.  I do?

  I also have a XenServer that is configured in this way and it's all free. I wanted to try the bare metal of VMware solution, but now I wonder if I'll have to go back to Xen.

  Can someone please relieve me of my confusion until I have to pull the plug on this experience.  Maybe direct me to the proper documentation on how to configure what I need with what I have at the cost free-is possible.

  Thanks a lot for your comments and have a wonderful weekend!

  I'd go by QuickStart Webcast and Webcast ESXi Webstart to help get a better understanding.

  Here is a configuration to the MD3000i http://www.dell.com/downloads/global/solutions/esx_storage_deployment_guide_v1.pdf guide

• ESXi 3.5 4 problem to upgrade by adding the VMFS partition existing on iSCSI SAN

  Hi all

  I've got 2 x Dell PowerEdge 2950 III linked directly with Dell MD3000i iSCSI-SAN and today I had once hard to improve my production ESXi 3.5 u 4 ESXi 4.0,.

  First is that the upgrade is failed miserably after following this thread: url = http://communities.vmware.com/thread/211413;jsessionid=47217F9BCCA2DF1325DBE7A266D48A8D?tstart=0VMware communities: error on upgrade the host: this host is not compatible with this upgrade. [url]

  with the following error message: ERROR: unsupported boot disk

  The layout of boot device on the host computer does not support the upgrade.

  That's why I did a clean reinstall of ESXi 4 on top of ESXi 3.5 u 4 and lost all unique settings on my ESXi host. I am now stuck in SAN iSCSI partition mapping after following the guide from: http://support.dell.com/support/edocs/software/eslvmwre/AdditionalDocs/cnfigrtnguide/storage_guide.pdf [/ URL]

  See the following attachment.

  I wonder how people make their upgrade in ESXi 4.0 in the production system running ESXi 3.5 u 4 filled with hundreds of VM? The reason why I use 2 x ESXi server connected to unique SAN server, is that I can just start the virtual machine on the SAN from the other ESXi - & gt; that's fine and tested, but then when I rebuild the failed server, I need to delete all the data inside the shared partition that contains my VMs.

  So in conclusion after one of the ESXi server failed, mapping of iSCSI would eventually destroy all data in the partition?

  CMIIW, any idea and suggestion would be gladly appreciated

  Kind regards

  AWT

  The configuration-> tab cards storage, you should be able to recrawl and find existing VMFS volumes.  You shouldn't need to add storage.

  Andy

• VMware vsphere essentials more and Dell MD3000i iSCSI - virtual disk not on preferred path

  Hello world

  I am trying to set up our new vmware vsphere essentials plus the facility. We have 2 x Dell R710 servers running vmware esx4 and have a md3000i SAN.

  Each server has a network cable to connect to a network SAN controller.

  vmserver1 a vmnic6 IP 192.168.130.110 the IP controller connection 0 192.168.130.101

  vmserver1 has IP 192.168.130.111 vmnic4 connection to controller 1 IP 192.168.130.102

  vmserver2 a vmnic 6 IP 192.168.131.110 the IP controller connection 0 192.168.131.101

  vmserver2 has IP 192.168.131.111 vmnic4 connection to controller 1 IP 192.168.131.102

  Whenever I start a virtual server it causes the dell md3000i start flashes orange, and management tool says disc not on favorite virtual path.

  After entering the tool configuration and affecting the path preferred, from the commencement to vmware, even with a single connected server it causes the error.

  I tried to configure vmware to use direct fixed and alternate paths.

  I did a quick search on Google and found these sites:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  http://en.community.Dell.com/support-forums/storage/f/1216/t/19269507.aspx

  Strange configuration.

  Looks like you are using some cross cable?

  Each host must have 2 vSwitches, each with a port vmkernel on one of the two iSCSI network.

  Each host must reach all 4 of the MD3000i (test with the vmkping command) interface.

  See also:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  André

• with vSphere and Dell MD3000i iSCSI design

  I installed a server ESX 4 (the first of three for this cluster), and a SAN Dell MD3000i iSCSI connected through two switches Dell PowerConnect 2816.

  Now I read the VMware 'iSCSI SAN configuration guide', and I wanted to just make sure I did the design correcly.

  I have connected a Teddy ESX (vmnic1) to one of the pSwitch and another (vmnic5) in the second. This pSwitch SAN iSCSI ports are connected, so that one of the switches carry the 10.10.10.x subnet and the other the 10.10.11.x (see IP plan below)

  The two natachasery have a vSwitch each (a do not share), a portgroup each and are configured on different subnets, IP (see attached screenshot)

  Plan of intellectual property:

  Port iSCSI-10 group (VMkernel): 10.10.10.1

  Port group iSCSI-11 (VMkernel): 10.10.11.1

  0-0 SAN controller: 10.10.10.10

  SAN 0-1 controller: 10.10.11.10

  Controller 1-0 San: 10.10.10.11

  SAN 1-1 controller: 10.10.11.11

  By using this configuration, I could see four different paths for each LUN. and I was able to make the ESX Server will switch to different switches/controllers as I unplug the vmnic1 network cables and vmnic5, one at a time.

  Then I found the section on 'esxcli' configuration guide and multipathing configuration, which I carried out in accordance with the instructions ("esxcli swiscsi nic add - n vmk0 d vmhba34" and "esxcli swiscsi nic add - n vmk1 vmhba34 d ')

  Now I have eight different paths for each logic unit number, three of whom are 'Active' and an 'active (i/o)' (see my screen attached the capture).

  So, my questions are:

  1. the eight paths to each LUN really normal in designs of iSCSI?

  2. is my vSwitch/Teddy/pSwitch correct design choices?

  Thanks in advance!

  / Anders

  @hennish,

  As long as your new design continues to meet your needs of failover and workload, your infrastructure design should be fine.

  But you might want to take a look at this design Dell. In particular, step 12 that configures multiple paths in round-robin policy using the VI GUI client, for

  Each LUN exposed to the ESX Server. This allows balancing on two

  Active paths to the LUN. After completing this step, you should see2 "IO Active" paths.

  Kind regards

  KongY@Dell Inc.

• question put on the vSphere iSCSI SAN infrastructure network

  Hi all

  We are a small company with a small virtualized environment (3 ESX servers) and are about to buy an AX-5 SAN EMC (model Ethernet not CF) to implement some of the features of high availability of vSphere. My question is related to the networking of the SAN: we switch dual Cisco 2960 G Gigabit and dual Cisco ASA 5510 firewalls in a redundant configuration.

  I understand that the best practice is to implement iSCSI traffic on a separate from all other traffic LAN switch. However, I do not have the knowledge and experience to determine the real difference than a separate switch would really vs the plan to create a separate VLAN on the switches Cisco dedicated to iSCSI traffic only. I would ensure that the iSCSI traffic has been on a VLAN dedicated Physics (not just a logic) with any other VLAN logical (subinterfaces) on the same VLAN). It is difficult for me to understand how a port gigabit on a VLAN isolated on kit Cisco will perform much poorer than on a dedicated Cisco switch somehow. But then again, I don't know what I don't know...

  The thoughts and the input would be appreciated here: I'm (very) hard not to drop another $6 + in another pair of Cisco switches, at least that this decision will significantly compromised performance iSCSI SAN.

  Enjoy your time,

  Rob

  You have 2 SP each with 2 iSCSI, for example:

  SPA: 10.0.101.1 101 VLANS and VLAN 102 10.0.102.1

  SPB: 10.0.101.2 101 VLANS and VLAN 102 10.0.102.2

  On your ESX to create 2 vSwithes, each with a port vmkernel on an iSCSI network and each with a single physical NIC.

  See also:

  http://www.DG.com/microsites/CLARiiON-support/PDF/300-003-807.PDF

  André

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

• Make Accessible iSCSI SAN-VM via Windows iSCSI initiator

  I have a "total newbie" question that I hope can respond quickly enough.

  I added a new DELL MD3000i SAN to my storage network in order to use this SAN exclusively for Windows virtual machines. I have the vdisks large (2) 4 to 7 to each (Yes, I REALLY need unique and large volumes) defined on the MD3000i. (4) the MD3000i ports are connected to my iSCSI VLANS and have the id default host port 192.168.130.101/102 and 192.168.131.101/102.

  I have a MD3220i installed in the network and working with hosts ESXi 4.1 (2) (192.168.230.101/102, 192.168.231.101/102 of the subnets). I am quite familiar with how to make the storage available to the host via the initiator of the iSCCI, but I know not how to make accessible storage for virtual machines WITHOUT using the host to connect to the iSCSI SAN, create a data store, and then add a new virtual disk to the virtual machine.

  Only the vmnic dedicated to the iSCSI initiator have physical links to iSCSI VLANS (vSwitch01). The network switch has (2) network adapters connected to the network via vSwitch0 "inside".

  Any ideas on the best way to "get there from here"?

  Hello.

  You will need to create a group of ports in virtual machine on the same vSwitch created in your iSCSI ports group.  Give the virtual machine a 2nd NETWORK card and then assign it to the created virtual machine port group previously.

  Good luck!

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

• Promise VTrak M310i iSCSI SAN

  RE: Promise VTrak M310i iSCSI SAN

  This unit is located in the 3.5 but a solution to budget.  Someone there had positive results with this SAN and ESX3.5i?

  The M310i has 2 x 1 Gigabit NIC.  We expect 30 VM on the device hosting and their running on the network of private storage.  Two gigabit NIC will provide enough flow to run the number of virtual machines?  Connection to Dell 2900 series 3.

  M310i product page

  Thank you in advance...

  It is really difficult to give a definitive answer one way or another how this will work.  The real answer is that it depends on what are these virtual machines.  If you use just 30 virtual machines that run background services, do a lot of disk i/o, etc., then you're probably fine.  If you use more than a couple of servers to database or by e-mail on these boxes and consider storing discs on which these virtual machines on this device, 2 GigE interfaces may be too limited for this environment.