PowerVault MD3000i - HDD Guasto [DS]

Similar Questions

• ITA - PowerVault MD3000i undetected

  Hello

  My server ITA is not detecting my MD3000i, the audit of prereq that I need to install PowerVault Modular Disk Storage Manager, however I can't find it to download on the Dell website?

  Could someone provide a link to download it please?

  Thank you

  Rich

  
  

• Offerta batteria Dell Powervault MD3000i [DS]

  Buongiorno,

  sewn questo post per ricevere UN preventivo price batteria by Dell MD3000i. Service etiquette: D33BD4J

  Grazie

  Dear client,

  Con passing it mouse sopra identifier c Supporto Dell'e the voce "private message", it could mandarmi UN message privato.

  Nel caso in cui as aver need di assistenza telefonica is Pagaré a ticket di Assistenza.

  SE if need di una delle quotazione left in sostituzione can rates UN preventivo senza Pagaré the assistenza.

  By request, we have our o di need any it client codice di vecchia quotazione o.

  Nel caso in cui non his di queste information times need che compilasse i seguenti campi:

  By the spedizione:

  1. company name:

  2 address:

  3 City:

  4 Provincia:

  5 cap:

  6 name/last name/number phone/e-mail del referent in loco:

  With the fatturazione (is different)

  1 nome società (is it client code):

  2 via:

  3 City:

  4 Provincia:

  Heading 5:

  Name/last name/number 6 telephone/e-mail del referent by the fatturazione:

  7 partita IVA

  Speaking saluti

  Domenico Severino

• Cannot ping port host MD3000i on RC0

  Hello

  I have set up my iSCSI network, as suggested in this post:

  http://en.community.Dell.com/TechCenter/storage/w/wiki/MPIO-to-PowerVault-MD3000i-with-Microsoft-iSCSI-initiator.aspx

  I can only ping the ports of controller RAID 1 (two ports). All of my iSCSI traffic is drunk through the controller. Windows Server 2008R2 (R710/810), but also an ESXi 4.1 cluster (R610 and PE2950) access the dedicated iSCSI network. I contacted the support a few weeks ago, and they have replaced the MD3000i RAID controllers as well as the background. They are insistent that there is a configuration problem and would not assist any more beyond to send me links suggested configs. I went through the Setup on the R810 (Windows 2008R2) from scratch. This has not produced different results. Then I updated all drivers (BCM5709Cs) NETWORK card and software on all hosts, successfully restarted the MD3000i and the two MD1000s bike powered two switches HP Procurve 1400 and restarted all hosts. I can't always ping RC0. I Putty and captured RC0 boot logs, but it was not obvious to me. Here are the logs of boot:

  -=<###>=-
  Set the interface lo0... done

  Autonomous 9768 symbols added.
  Error
  03/26/13-16:44:29 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00

  ATTENTION: Reset by spare controller

  Current date: 26/03/13 time: 09:26:15

  Send Change Service Interface rate or baud
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: sequence SOD is Normal, 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: SOD: removed host SAS from index 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: in iscsiIOQLIscsiInitDq.  iscsiIoFstrBase = 0 x 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: turn on seeing failure summary tray
  03/26/13-16: 44:48 (GMT) (NCDB): NOTE: SYMBOL: SYMbolAPI registered.
  esmc0: event LinkUp
  03/26/13-16: 44:50 (GMT) (tNetCfgInit): NOTE: the loan network
  03/26/13-16: 44:51 (GMT) (NCDB): NOTE: channel initiating Drive: ioc:0 bringup
  03/26/13-16: 44:54 (GMT) (NCDB): NOTE: the Firmware Version of the IOC: 00-24-63-00
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 0 phy:0 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 0 phy:1 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 1 phy:2 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16:45:18 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 1 phy:3 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16:45:18 (GMT) (tSasCfg021): NOTE: path of the Alt up - chan: 0 phy:18 itn:1 controller
  03/26/13-16:45:18 (GMT) (tSasCfg022): NOTE: path of the Alt up - chan: 1 phy:16 itn:2 controller
  03/26/13-16:45:18 (GMT) (IOSched): NOTE: discoveredEncl: enclosure: 1, enclProp: x2c50104, trayId: slotCount 2:15
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: IonMgr: Drive Interface enabled
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: SOD: instantiation Phase complete
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: controller between open Communication channels
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: initiator of news: 1 - channel: 1, devHandle: x2c, SAS address: 590b11c41a9d8b00
  03/26/13-16: 45:19 (GMT) (tSasDiscCom): NOTE: complete a discovery SAS task created
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: LockMgr role is slave
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: discoveredEncl: enclosure: 1, enclProp: x2c9516c, trayId: slotCount 2:15
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: new initiator: 2 - channels: 0, devHandle: x1a, SAS address: 590b11c41a9d8b01
  03/26/13-16: 45:21 (GMT) (IOSched): NOTE: discoveredEncl: Speaker: 2, enclProp: x2c8f730, trayId: 1, slotCount: 15
  03/26/13-16: 45:21 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
  03/26/13-16: 45:21 (GMT) (sasCheckExpanderSet): NOTE: address SAS Expander: salvation = Low = xf6ac8d10 x5848f694
  03/26/13-16: 45:21 (GMT) (tSasDiscCom): WARN: SAS: Initial full time of discovery: 33 seconds
  03/26/13-16: 45:21 (GMT) (IOSched): NOTE: discoveredEncl: Speaker: 2, enclProp: x2c66ad4, trayId: 1, slotCount: 15
  03/26/13-16: 45:22 (GMT) (NCDB): NOTE: spmEarlyData: from alternate data
  03/26/13-16: 45:22 (GMT) (NCDB): NOTE: WWN baseName (valid ==> SigMatch) 00040026-b95795de
  03/26/13-16: 45:23 (GMT) (NCDB): NOTE: ionEnableHostInterfaces is waiting for a channel lends itself
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: ionEnableHostInterfaces expected 3800ms for a channel lends itself
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: IonMgr: Host Interface enabled
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: SOD: pre to complete initialization Phase
  03/26/13-16: 45:47 (GMT) (NCDB): NOTE: ACS: autoCodeSync(): beginning of the process. Comm mode: 0, State: 1
  03/26/13-16: 45:47 (GMT) (NCDB): NOTE: SOD: complete Phase initialization Code synchronization
  03/26/13-16: 45:48 (GMT) (NvpsPersistentSyncM): NOTE: persistent storage NVSRAM updated successfully
  03/26/13-16: 45:48 (GMT) (NCDB): NOTE: initialization complete USM Mgr with 0 records.
  03/26/13-16: 45:49 (GMT) (NCDB): NOTE: BDU - received 1 small files
  03/26/13-16: 45:49 (GMT) (NCDB): NOTE: BDU - received 0 records of great
  03/26/13-16: 45:50 (GMT) (NCDB): NOTE: acquire 0.035 dry
  03/26/13-16: 45:53 (GMT) (NCDB): NOTE: QLStartFw: FW drive download image 03.00.01.47 033eab00 4c0c8 bytes, result 0
  03/26/13-16:45:55 (GMT) (tRAID): NOTE:  ********************************************************************************
  03/26/13-16:45:55 (GMT) (NCDB): NOTE: Application target QLogic, 2.01.08 Version 2005-06-13 (W2K)
  03/26/13-16:45:55 (GMT) (NCDB): NOTE: iSCSI Target Application
  03/26/13-16:45:55 (GMT) (tRAID): NOTE:   ********************************************************************************
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: iSNS Server 0.0.0.0:3205
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: ISNSServerIPv6Addr 00:00:00:00:00:00:00:00: 3205
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: iSCSI name iqn.1984 - 05.com.dell:powervault.md3000i.60026b90005795de000000004b2ae7b6
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: port = 0, turn on IPv4 = 1, turn on IPv6 = 0
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: 10.182.233.250:3260 IP address
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: Firmware waiting for DHCP lease.  State 18
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: 18 FwState 000/010 of time
  03/26/13-16: 45:57 (GMT) (NCDB): NOTE: QLInitializeFW: 10/01/00 18 FwState of time
  03/26/13-16: 45:58 (GMT) (NCDB): NOTE: QLInitializeFW: 10/02/00 18 FwState of time
  03/26/13-16: 45:58 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 0 bind upward.
  03/26/13-16: 45:59 (GMT) (NCDB): NOTE: QLInitializeFW: 10/03/00 FwState time 0
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: port = 1, turn on IPv4 = 1, turn on IPv6 = 0
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: 10.182.232.250:3260 IP address
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: Firmware waiting for DHCP lease.  State 18
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: 18 FwState 000/010 of time
  03/26/13-16: 46:01 (GMT) (NCDB): NOTE: QLInitializeFW: 10/01/00 18 FwState of time
  03/26/13-16: 46:02 (GMT) (NCDB): NOTE: QLInitializeFW: 10/02/00 18 FwState of time
  03/26/13-16: 46:03 (GMT) (NCDB): NOTE: QLInitializeFW: 10/03/00 FwState 18 time
  03/26/13-16: 46:03 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 1 link up.
  03/26/13-16: 46:04 (GMT) (NCDB): NOTE: QLInitializeFW: 10/04/00 FwState time 0
  03/26/13-16: 46:05 (GMT) (NCDB): NOTE: PM - reading DB (record 1.0)
  03/26/13-16: 46:08 (GMT) (t1): NOTE: QLTA_HandleTeb: Connect ports 0
  03/26/13-16: 46:08 (GMT) (t3): NOTE: QLTA_HandleTeb: port 1 link up
  03/26/13-16: 46:09 (GMT) (t2): WARN: QLTA_Handleteb: 72 event Code.
  03/26/13-16: 46:09 (GMT) (t4): WARN: QLTA_Handleteb: 72 event Code.
  03/26/13-16: 46:09 (GMT) (NCDB): NOTE: CCM: sodMirrorCheckIn() waiting alt cache check in mirror...
  03/26/13-16: 46:10 (GMT) (NCDB): WARN: CCM: initMirrorAltChkIn() may not reflect
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: CCM: initialize(): cache configuration
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: from UWManager::initialize, 510, the invalid index - 1 entries
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: NVSRAM IW queue size is 0
  03/26/13-16: 46:16 (GMT) (NCDB): NOTE: RTR: IO released
  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: SOD: initialization Phase complete
  ==============================================
  Title: Disk Array Controller
  Copyright 2005 - 2011 LSI Logic Corporation, all rights reserved.

  Name: RC
  Version: 07.35.39.64
  Date: 16/08/2011
  Time: 14:24:32 CDT
  Models: 1532
  Manager: devmgr.v1035api01.Manager
  ==============================================

  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: sodMain of the sequence is complete, elapsed time = 90 seconds
  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: complete sodMain
  03/26/13-16: 46:17 (GMT) (EventGateManager): WARN: GMOS: 8 events of creation for objects that already exist

  IPs I can ping: 10.182.232.251 and 10.182.233.251 (both on RC1). I can even ping all other iSCSI host initiator ports! I hope I gave enough information about me for some answers. Please advise!

  Thank you.

  What are the 4 IP addresses and subnets for the 4 the MD3000i iSCSI ports?

  ISCSI controller 0 port 0?: (guess 10.182.232.250/24)

  ISCSI 0 1 controller port?: (guess 10.182.233.250/24)

  Controller 1 iSCSI port 0: 10.182.232.251 24 (hypothesis on the mask)

  Port of iSCSI controller 1 1: 10.182.233.251 24 (hypothesis on the mask)

  Wiring must be:

  iSCSI 1 Switch / VLAN:

  ISCSI controller 0 port 0

  ISCSI controller 1 port 0

  Server 1 iSCSI port 0 (in the subnet 10.182.232.x 24)

  etc.

  iSCSI Switch 2 / VLAN:

  ISCSI 0 1 controller port

  ISCSI 1 1 controller port

  Server 1 iSCSI port 0 (in the subnet 10.182.233.x 24)

  etc.

  To test iSCSI on controller 0 port, take a cell phone with a Gbit ethernet port (any modern laptop should have it), connect the ethernet controller iSCSI 0 0, 10.182.232.100 port value IP from the laptop and try to ping 10.182.232.250 (assuming that it comes to the INVESTIGATION period on this port). If it works, change the IP of the laptop to 10.182.233.100 and move the cable to the iSCSI port 1 and try to ping 10.182.233.250 and see if you can ping the IP address.

  If these two are working, the first thing that comes to mind is that the port 0 and 1 have their swapped cables.

• Drivers for Windows Server 2008 R2

  PE1950, 2950 and MD3000i MPIO on Windows Server 2008 R2

  We're trying to nail a few dates to migrate our W2K8 R2 platform and plan the project.  We have most of our technical plans in place, and we have the code.  We have no Dell drivers however and there are several suspicious communications from Dell on this topic...

  Case #1: http://en.community.dell.com/blogs/insideit/archive/2009/08/10/ready-for-the-transition-dell-provides-support-for-windows-server-2008-r2.aspx

  Note:

  • Our engineers have missed on countless piano recitals, songs and episodes of American Idol while spending thousands of hours of testing and validation to make sure that dy products Dell running Windows Server 2008 R2 are the business-rea.
  • We have pilot complete support for Windows Server 2008 R2 for Dell hardware so you can deploy, run and manage easily. You can go here to download the drivers.

  If you view the service labels in our support of similar product groups, you will find an R2 option for servers... but the only public services on the PowerVault MD3000i you don't find any reference to R2 at all.

  Case #2: http://www.delltechcenter.com/page/Supportted+Dell+PowerEdge+Systems+for+Microsoft+Windows+Server+2008+R2+Beta

  This is a list of Beta for PE obviously compatible servers, however it would make sense If Microsoft has included natively the right drivers for the Dell hardware in the distribution of Microsoft R2 RTM so, just can't find any supporting documentation and do not know if the network drivers are compatible with MD3000i.

  #3: There are a few hacks to get drivers Windows 2008 MPIO inherited working with the RC R2 & MD3000i on this forum, but no reference to R2 in the MD3000i matrix and nothing on the site... it's why, we have wondering again where are the good drivers for R2 RTM?

  Can you be it someone from Dell and or this forum please send information on these issues?

  #1: driver compatibility of matrix for Windows Server 2008 R2 running on PE1950 and connected to an MD3000i PE2950 is a supported configuration?  (Code R2 RTM was released to Microsoft volume license customers)

  #2: the network drivers for the host machines included in the support of Windows Server 2008 R2 RTM?  If this is true, are the drivers MPIO for MD3000i and iSCSI Dell other platforms included in the support of Windows Server 2008 R2 RTM as well then?

  #3: If all the answers are not questions #1 and #2... could someone PLEASE contact people of pilot certification on Dell to see if they are same in QA at this point, if they plan to update and display an estimated date of implementation?  We have contacted tech support, but received very vague answers on anything with R2 at this stage.  There is a business directory and a path to escelation for support tickets, but the midrange as this makes it much easier to share information for the masses, we just have not yet found.

  Thanks for your information, comments and your support!

  OptimalState

  I was finally sent to someone who could give me some information on this within Dell, here's what they said:

  PE 1950/2950 drivers:

  The pilot should be included natively in Windows Server 2008 R2 media, and if so, would these drivers would be supported by Dell in a production scenario.

  MD3000i:

  I know that we will not issue a new MDSM which will fund 2008 R2 until sometimes in October. The MD3000i requires MPIO to the MD3000i and Dell drivers driver installation to work properly. I'll see if there is other information that I can find. I understand your frustration and engineer told me that this has been corrected in the next MDSM and MD3000i firmware version in October.

  So, it looks like October before MD3000i will be supported.

  OptimalState

• change the configuration

  Hello

  We have a MD3000i that is almost 3 years of work, the equipment in its current configuration, connected to a server (with a cable UTP ISCSI), made us add more than 6 player (disc dan the oraginal of different size), and now we want to create a new arrary with these new drives and connect them to a different server. I heard that it's possible, could someone tell me if we can change the current configuration from one server to 2 servers without downtime? and also I here if you could point me to any caraa on how to do this.

  Thank you

  If you have already added the readers, use the Dell MD Storage Manager (compatible download link 32xx/MD3000/36xx here: ftp.dell.com/.../DELL_MDSS_Consolidated_RDVD_4_1_2_29.iso ) and do an auto-detection. If the software detects your large table, otherwise you will need to find the ip addresses of the management. If its not written anywhere, you can retrieve this with the serial cable.

  I hope that the new disks appear as compatible. New readers will have a dell PPID on them but not all readers of Dell will the logo.

  Here is an example of a seagate drive with no dell logo but has a ppid.

  dellfirmware.Seagate.com/.../drive_sn_ppid.gif

  Once in the software and with work records, go to the configuration tab and create a new group record with disks, also a new virtual disk on the new raid group. Set up your iscsi sessions since the new server to the MD3000i and then go back to the software manager of storage and in the configuration tab, create a host to virtual disk mapping to point to your new drive to your new server.  Rescan storage on your Server adapters and see if the disks appear.  If your server is windows or linux, you will need to run the software on the server cd and install the host Party Multipathing to work properly.  In the case of esx that you won't need to do it.

  If you happen to use ESX here is a guide to the correct configuration.

  en.Community.Dell.com/.../3043.aspx

  For all other documents, use this link

  www.Dell.com/.../PowerVault-MD3000i

• PS4100X - Set Initial configuration (vSphere 5)

  Hi all

  We just bought a PS4100X with 12 x 600 GB 10 K SAS (7.2 to RAW)

  This unit is due to replace our existing Powervault MD3000I device is used in a Vmware ESX environment.

  What RAID / Datastore ESX configuration would people recommend.

  Currnently, we have implemented for example what follows.

  2 x Raid 10 groups of drives with 1 TB of virtual disks on each.

  Records 1 to 2 are then presented to the ESX and used by 2 data warehouses.

  Congratulations in advance.

  I suggest you cut up TB volumes smaller. That is 600GB (depending on the size and the number of virtual machines on each datastore) each volume has a queue queue defined, usually 32.   More medium-sized volumes most exceptional IOs may be running.   Also there are times when ESX must block (reserve) a volume, so that reserved no other node may make the e/s to this volume.  So more volumes reduces the question and other volumes have current IOs.

  Here are some best practices

  People with DISABILITIES ACK delayed 1.)

  2.) large receive Offload DISABLED

  3.) make sure, they use VMware Round Robin (with IOs through changed to 3), or preferably MEM 1.1.0.

  (4.) if they have multiple needs of VMDK (or ROW) in their VM, each of them (up to 4) its own virtual SCSI adapter.

  5.) updated latest version of ESX, to get the latest NIC drivers.

  6.) too little volumes for the number of virtual machines that they have.

  This is a material source for the delayed acknowledgement

  KB.VMware.com/.../Search.do

  virtualgeek.typepad.com/.../a-Multivendor-post-on-using-iSCSI-with-VMware-vSphere.html

  How to disable LRO

  Solution title HOWTO: disable large receive unloading (LRO) in ESX v4/v5

  Details of the solution in VMware, the following command queries the current value of LRO.

  # esxcfg - advcfg - g/Net/TcpipDefLROEnabled

  To set to zero (disabled) LRO value:

  # esxcfg - advcfg - s 0/Net/TcpipDefLROEnabled

  NOTE: a server restart is required.

  Info on LRO change in the feedback network.

  docwiki.cisco.com/.../Disable_LRO

  How to add virtual SCSI adapter:

  KB.VMware.com/.../Search.do

• 5.1 E30931 POS could not launch a backup

  Hello

  I have a problem with backups of POS.

  Yesterday, I rebooted my server ESXi and my SAN. We use Dell PowerEdge R805 2 x for the hosts and a Dell PowerVault MD3000i SAN.

  Because we are changing to a PowerVault MD3600i, I unplugged some cables iSCSI (while the server was closed). Now, each host is connected with 1 single cable iSCSI SAN.

  After launching the servers, everything worked very well, wait for backups of POS.

  POS displays the following error message:

  E30931 could not start a backup or restore of a virtual machine because no proxy has been found to maintain the virtual machine

  Unfortunately I have not found something about this error, so I hope someone here can help me!

  My understanding of the error >

  POS has 8 proxy backup internally, making the backup. Unfortunately, the poxies are not initialized in your case.

  Have you tried to reboot the device?

• How to enlarge VMDK?

  I have a Dell Powervault MD3000i storage offering an ESX Server 3.5 and Windows 2008 Server (functioning as a file server) on the ESX Server. Server 2008 is complete so I bought a new drive for the MD3000i extend the capacity of the data on Server 2008 drive. I followed this guide:

  http://jacobackerman.blogspot.com/2009/06/Dell-MD-3000i-expandng-virtual-disk.html

  So now (several merged physical disks in a virtual disk) drives on the MD300i show a total of 1.36 TB, but Server 2008 is only showing 1 TB of space on the data drive, it is not recognizing the new 300 GB space. After some research and asking around on other forums I learned that I need to extend the VMDK file to the new size (1.36 TB) then use windows diskpart to extend the drive. I tried to follow this tutorial:

  http://communities.VMware.com/thread/15593 (2nd post in particular)

  but I don't know the drive name or the name of fs. I looked on the VMware infrastructure client under the virtual machine settings and drives hard found3. The first is a virtual disk 60 GB in size, it is the Windows operating system, the second is the man I am interested. It's a Raw LUN mapped with these properties:

  Logic unit number physical and database mapping file:

  vmhba32:0:0:0

  DC02/DC02_2.vmdk

  Virtual device node:

  SCSI (0:1) hard disk 2

  How to expand the vmdk to see the new space?

  Hi Dexter,

  Please follow below

  Instruction.

  1.
  Right-click on the storage of data

  2.
  Click on properties

  3.
  There you can get Option to store the data to add, increase

  or Extend.

  If this problem is not solve d thanks for posting again with

  error.

  Thank you

  Philippe

• Creating a virtual file server on ESXi. Limit of 2 TB will be a problem?

  Hello

  I'm planning to virtualize a couple of my servers, but some have

  questions about the size limit of 2 TB for volumes on ESXi. I guess that let

  me tell you what I want to do and you would be grateful if you can tell me

  If it's possible or not, and if yes, what is the best way to implement.

  I'm new to VM is so patient with me if I do not use terminology

  correctly.

  I want to virtualize my file server. For now, it is a physical

  Server that connects to an iSCSI SAN (Dell PowerVault MD3000i) network, and the

  LUNS assigned to it is about 5 TBs. To be more precise, the server has a

  F: drive, which is a volume of 5 TB on the SAN. This disc has an action

  This is useful to our main file server.

  I wonder if I create a computer virtual on ESXi server, can I attach this same

  Volume 5 to for this virtual machine in the same way I have such that it is connected to the physical

  box (if the virtual machine will have the same drive F:, which is actually the 5 TB

  LUN on the SAN)? This new virtual machine would replace the old physical box, if

  they would not both connected at the same time, in case that

  questions. I know it of just the 2 TB limit, but is it just for

  data warehouses? Which means, I have no need of virtual on files

  This volume, they will be on local storage, I want just the virtual machine itself

  have this volume mounted as a drive inside the BONE, so it acts as a

  file server (I hope I explained this right). Is this possible, or

  always do in the 2 TB limit in this case?

  Any help would be greatly appreciated.

  Thank you

  Josh

  The 2 TB limit reference itself VMFS partitions.  What you want to do is possible and the road ahead

• Question about VMKernel iSCSI traffic and VLANS

  Hello

  This is a very fundamental question that I'm sure I know the answer too, but I want to ask him anyway just to reassure myself.  As a precursor to my question, the configuration of my ESX infrastructure is best described here: http://www.delltechcenter.com/page/VMware+ESX+4.0+and+PowerVault+MD3000i.  Or more precisely, we have two controllers MD3000i.  Each controller has two ports and each port is configured on two different subnets, with every subnet connected to the different switch.  ESX host are connected to two switches.  The only difference for the guide, is we have two MD3000i configured the same, connection to the same switches.  Each MD ports is configured on the same subnet, but different IP addresses.

  At present, we are in the process of upgrading our two iSCSI switches of humble Dlink DGS - 1224T to Cisco 2960 T of.  The switches have been and continue to be dedicated to iSCSI traffic, however, I'm trying to set up VLAN s on the side of the switch.  Originally, we used the default VLANS on switches, however, after you have added an another MD3000i, noted the Support Dell best practices is to separate each on its own subnet and VLAN MD3000i iSCSI traffic. This would result in iSCSI 4 VLANS, two on each switch and two for each MD3000i.  Firstly, is this in fact of good practices?

  Second, if I migrate preceding 4 iSCSI VLANS, as each switch port will actually be an access port, will there need to complete the VLAN ID field in the VMKernel configuration page? Presumably, this field is used when the tagging VLAN is used, but as our switches do not need any other rocking trunk (as they are dedicated to iSCSI traffic), there should be no need to fill?  I guess it would be prudent to keep the two existing subnets, create two new subnets and make changes to an MD3000i and connection of the ESX host.  Provided the switch and switch ports has been appropriate configured with VLAN on the right, the rest should be transparent and he wouldn't be Intel VLAN in all ESX hosts?

  Would be nice to get answers and thank you in advance!

  Gene

  (1) Yes, it is best practice for ESX iscsi, having an independent network and vlan for iscsi traffic.

  (2) No, there is no need to mention anything in the area of vlan, if you use an access port. Its a mandatory thing than a choice. If you supply the id vland with access port, it loses connectivity.

  Please explain a bit why you need to create two different virtual local networks for each MD3000i. You are going to use several on the same ESX box iscsi storage? Alternatively, you use only a single iscsi and use these 4 ports for the same single VMkernel interface?

  NUTZ

  VCP 3.5

  (Preparation for VCP 4)

• 3.5 or 4?

  When I ordered VI3 Enterprise, vSphere was not available.  I just received my licenses for vCenter 4 and VI3 today. (Apparently you can manage VI3 with vCenter Server 4)  My question is, should I go with 3.5 or simply start by 4?  It is a brand new facility.  My setup is 2 servers Dell R710 and a Powervault MD3000i.  I intend install ESXi on a USB key in the servers. The new features of vSphere did take on the stability and the age of 3.5? Thanks for the review!

  Don't forget that another product could not (yet) work con vSphere, also of VMware (View Composer, SRM,...).

  Reference Dell OMSA does ' t work as well (yet).

  PS: MD3000i works very well with the new ESX.

  André

• ESX 3.5 machines comments can't see more than one disk virtual iSCSI

  Hello

  In our environment, we currently have two guest computers (running Windows server 2003) on a single host ESX 3.5 (dell PowerEdge 2950). Virtual machines are stored on our SAN (Dell PowerVault MD3000i). There are other mounting virtual disks on the San that we want to connect directly via an inititator iSCSI on each of the host machines. However, when you try to do this, we see that the a disk LUN at a time. Physical servers can access all LUNS without no problem, these two cannot.

  We prefer not to make use of RDM, as told me he is not slender and outdated (please tell me if is is not the case). The SAN has the last firmware update. The esx itself host can see all LUNS. On the SAN 'host type' for both virtual computers is configured as windows Server 2003/2008 in clusters.

  Is that all that I'm missing/maybe badly configured?

  Kind regards

  Marc

  I'm not sure I understand.

  You have your MD3000i certain VMFS LUNS and other 'firsts' (to be used with NTFS). Is this ok?

  If you go to a 'gross' LUN using iSCSI initiator of sw inside a virtual machine you can see as a single logical unit number?

  Your goal is to create a Microsoft Cluster? 2003 or 2008?

  You want to use a cluster 2008 install the MD3000i tools in virtual machines.

  André

• Can't see the iSCSI data warehouses after reboot

  I have 2 ESX 3.5.0 u3 hosts running on Dell PowerEdge 2950 servers and connect to a Dell PowerVault MD3000i. Recently, I upgraded the MD3000i gen.2 firmware, and after the upgrade, one of the MD3000i controllers began to experience extremely slow (3-4 MB/s) write to its LUNS assigned speed. Dell support reviewed my setup and said I have a configuration problem - all 4 of the MD3000i ports are on the same subnet, while according to them, they should be divided into two subnets. I have interruption scheduled for this Saturday, close all virtual machines, added an additional VMkernel port and a service console for the new subnet on each host, removed addresses for two of the ports of discovery dynamic and restarted the two hosts. When they restarted, I changed the IP address on a single port on each controller. The servers came, restored 4-port iSCSI sessions and can see two LUNS defined on the MD3000i, but cannot see data warehouses - it's like they went, and LUN are naked. Creating new data warehouse will wipe away their own, and while I have current backups, I would rather jump restore all this from scratch. Is there anything that can be done here?

  -Very well, could be a problem of will:

  http://KB.VMware.com/selfservice/viewContent.do?externalId=9453805&sliceId=1

  André

  * If you found this device or any other answer useful please consider awarding points for correct or helpful answers

• Installation of VmWare HA

  Hello

  We're building a small scale data center.   Our facility will be 2 nodes cluster for now.  We have 2 servers dell poweredge 1950 III.  We plan get vmware ESX 3.5 with HA.   The two servers will be connected to a San (dell powervault MD3000i) via the iSCSI interface.  We will host 2 VMs - IIS and Server MS SQL 2008, both running on Windows Server 2008.

  I have two specific questions to our facility:

  1. each server has 2 ports of gigabit ethernet integrated (the one that will be used for vCenter and the other for the clients to connect to the web server).  Additional 2 gigabit ports with TOE and iSCSI to connect to the MD3000i SAN network with redundant links.  Do we need another port gigabit for pulse HA?

  2. from what I understand in the vmware white paper HA does not shift smoothly since it only restarts the virtual machine on the physical server mode standby when the main physical server is out of service.  Do we need to DRS + VMotion to shift smoothly?

  3 cards Broadcom 5708 NIC works in virtual machine environment to take advantage of unloading TCP & iSCSI features unloading?  Windows 2008 supports the iSCSI initiator based on the material.

  Cold standby, it probably an appropriate term.

  Take a look at this article:

  http://www.virtualization.info/2008/10/VMware-fault-tolerance-overview-and.html

  It's supposed to be a new feature in the next version

  Jase McCarty, VCP, vExpert

  http://www.jasemccarty.com

  Co-author of VMware ESX Essentials in the virtual data center

  (ISBN:1420070274) Auerbach

  _{Please consider awarding points if this post was helpful or appropriate}