Similar Questions

• The FRU for the LSI 9260-8i cable?

  Recently, I got the LSI 9260-8i on a D20. I need to find number of RUF for cable of Lenovo, who will work on this map?

  Parts catalog descriptions are very vague. I don't know what to order.

  Can someone help me. If I can buy it. The Raid on the MB controller is very slow.

  I was out this slow pos. So I turned off and thought I update for better HD and keep only the raid controller.

  Thank you very much

  
  

• Cache SSD c2100 & LSI 9260-8i

  Hello

  On a C2100 with a LSI 9260-8i, what are the requirements for cache ssd work? I would add 2 SSDS (internally) to activate this feature, but I don't know if in addition the SSDS, I need nothing else, or if he is still supported on this server with the 9260-8i

  Thank you

  Asempris,

  I apologize, the C2100 does not support the Cachecade, which is the feature you describe using the SSD for the cache. You can also find more information on the C2100 here - http://ftp.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_cloud_products/poweredge-c2100_Owner%27s%20Manual_en-us.pdf

  Let me know how it goes.

• Use of LSI MegaCli tool in ESX 4

  We currently have a server ESX 4 use local storage provided by an LSI MegaRAID SAS 8888ELP

  In ESX 3.5, you can use the tool provided by LSI MegaCli to ensure control of hardward the RAID controller command line. In ESX 4, the application indicates that it is impossible to find controllers. Does anyone have an expierence with it?

  Thank you

  Will Turner

  ESX 4.0.0 build-164009-2009-04-30

  MegaCLI version 3.6, v4.00.11

  11.0.1 - 0013 (package) RAID controller; 1.40.42 - 0615 (Fw); 2009-04-06

  Hi Will,

  I have the same problems with ESX 4.0 and MegaCLI.

  The machine has a Dell PERC6 and LSI MegaRAID SAS 8880EM2 / i (LSI card) based.

  If I boot the same machine (Dell R710) using CentOS 5.3 LiveCD MegaCli can see two cards.  Not really the most beautiful tests like the LiveCD is 32-bit and 64-bit vSphere, but nevertheless still shows that LSI chipset driver provided with vSphere does not support using MegaCli.

  Have you tried to install the LSI MSM (MegaRAID Storage Manager) java tool based on the host at all?  Unfortunately, I was on the tight and this server has gone live (after removing the LSI card due to the lack of management), so I don't have the chance to try the MSM.

  Kind regards

• Application of LSI 9260-4i cache size

  Hello

  Running a Cisco UCS C - 200, I noticed the reports as 349 MB cache size but I was under the impression that it should be 512 MB

  This normal?

  

  Hello

  The number displayed under the MMIC is for the cache lines rather than the size of the global cache.  If you SSH into the MMIC and run the following commands look for the size of the memory and it should say 512 MB for 9260-4i.

  UCS c200 m2 /chassis # see the storageadapter

  PCI Slot valid Product Info name serial number of the firmware Build product ID battery status Memory Cache Size

  -------- ---------- ---------------------------------- -------------- ----------                                                                                ------------------------ -------------- -------------- --------------

  SLOT-7 Yes LSI MegaRAID SAS 9260-4i S1000 12.12.0 - 01 49 LSI Logic fully charged 346 MB

  UCS c200 m2 /chassis # storageadapter SLOT-7 scope

  UCS-c200-m2/chassis/storageadapter # see the hw-config detail

  7 PCI Slot SLOT:

  Valid Info: Yes

  Info invalid Cause:

  SAS address 0: 5000c 50021567829

  SAS address 1: 5000c5002133f3b5

  SAS 2 c address: 5000 50021567389

  SAS address 50021567431 3 c: 5000

  SAS address 4:

  SAS address 5:

  SAS address 6:

  SAS address 7:

  Present BBU: true

  Present NVRAM: true

  Debugger present series: true

  This memory: true

  This Flash: true

  Memory size: 512 MB<-- actual="" total="">

  Memory cache size: 346 MB

  Number of Backend Ports: 4

• You can restart nfs storage WITHOUT having to reboot ESX host?

  Hi community

  I wanted to know what your experience has been reset to the nfs storage devices WITHOUT having to restart the ESX servers. I can stop the virtual machines that use the storage, but would like to avoid off ESX hosts as they require a visit to the data center for put in operation and I can do all the rest of the House.

  My options are either then restart the ESX host (that I can do it remotely of course) or the ESX Server restores in the nfs storage when it is up?

  This is the first time such a restart will be required so I use

  this as a learning experience and the VMs on those ESX hosts are not

  criticism.  (although don't tell users which.) )

  Thanks in advance

  Yes, of course you can.

  ESXes automatically reverts to the storage.

  ---

  MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

  http://blog.vadmin.ru

• LSI MegaRAID Storage Manager on VMware ESXi 4.0

  Hi guys,.

  We tried to install on VMware ESXi 4.0 MegaRAID Storage Manager (IBM x 3550 M2) and it uses Controller RAID MegaRAID SAS 8808E to monitor the hard disk status but could not be able to install and it returned the error as attaché

  We followed the procedure as shown in the following ibm Web site

  1.6 MegaRAID Manager storage system to a VMWare ESX Server

  Follow these steps to install the on a MegaRAID Storage Manager

  VMWare ESX Server:

  1. download the latest MSM to ibm.com

  2 unzip the and copy MSM_linux_installer - 501.01.tar.gz on a USB key.

  3. from the ESX Server, in the console root, type the following command

  to identify the USB device: fdisk-l

  4. type the following command: mount/mnt/dev / {name of the USB device}

  5. type the following command: cd/mnt

  6. type the following command to copy MSM_linux_installer - 501.01.tar.gz in the occupied Palestinian territories

  file: cp MSM_linux_installer - 501.01.tar.gz / opt

  7. type the following command to decompress the package gunzip MSM_linux_installer - 501.01.tar.gz

  8 type the following command to unzip the package tar - vxf MSM_linux_installer - 501.01.tar

  9. replace the directories with the path/opt/disk

  10 tapez./vmware_install.sh to install MSM

  11. Select version of VMware

  a. enter 1 to install Vmware 3.5

  b enter 2 for VMware 4.0 install

  12. Select the storlib option

  a. Enter n If you want to use the Inbox storlib driver

  b. Enter y if you want to install the storlib delivered with MSM

  IBM recommends 'y' is selected for use packed with MSM, storlib by selecting "n" can

  cause some features of MSM does not function properly

  I would like to know if I use the correct version of the Storage Manager Application MegaRAID for VMware ESXi 4.0

  
  

  If not could someone please advise on how to proceed with the installation and troubleshooting

  Please find the file of errors as attaché

  
  

  Greatly appreciate your help

  
  

  Thanks in advance,

  Vignesh
  

  Check if help: vSphere unknown health status ' vSphere ' eMware »»

• Sensor data store

  Hi all

  We have a HP Proliant DL380 G7 with Vnware ESXI 5.0.0.

  In the State of health we do not see the sensor for the data store.

  Processor, memory, power, temperature, fan, are there software components.

  I hope I can get support with this.

  There is no sensor for the store of data... instead you can find sensor for storage... If there is any sensor storage you're talking about, check this thread another: storage sensor is disappear in vCenter Client - State of the Hardware tab

• LSI Megaraid SAS 9271-4i for vmware vsa

  Hello world

  I have a hardware vendor build 3 5.1 production esxi hosts based on Asus RS700-E7 with 32 GB of ram each.

  They will support up to 24 vm in an environment of low IOPS / s.

  They will run the VSA for vmware appliance in raid 10 on the sata drives.

  The seller offers the LSI 9260-4i Megarid. I'm not sure.

  What LSI Megaraid controller recommended by those who have used them in the past for vmware VSA?

  I am also looking at the LSI Megaraid SAS 9271-4i. Whichever is faster on vsa for vmware using WD drives and raid 10.

  I use 4 drives per host, so I'm also cureous why some people use 8i controllers.

  Thanks in advance.

  I actually went with SAS 15 k drives in raid 5. I already answered my own question on the raid controller, so I'll mark this as answered. Thank you.

• Migrating from ESX 3.5 to ESXi 4.1

  I am planning a migration of ESX 3.5 Uptade 2 to ESXi 4.1 Update 1 in September.  Material welcomes VI environment is in place for renewal of the lease.  I build the new environment vSphere and attach to the same storage shared as the existing ESX VI 3.5.  My plan is the following...

  1. Get and install a new hardware server (C3000 and BL460C G7).
     
  2. Installing vCenter 4.1 (leave vCenter in demo mode to expose all the features)
     
  3. Configure the plugin Update Manager vCenter
     
  4. Install ESXi 4.1 Update 1 on new hosts and add to vCenter 4.1
     
  5. Configure the new Cluster and configure HA and vMotion. (We are allowed for vSphere 4.1 Standard Edition)
     
  6. Linking hosts to Update Manager and sanitize with all updates.
     
  7. Configure virtual networks (host profiles are an option while in demo mode).
     
  8. Fix new hosts of VMFS existing databases.  (Data banks are VMFS version 3.31)
     
  9. Disconnect the Virtual Center 2.5 3.5 ESX host and add them to the new vCenter 4.1.
     
  10. Cold migrate VM ESX 3.5 hosts ESXi 4.1 bed and breakfast hosts
      
  11. Upgrade VMware tools on all guests.
      
  12. Upgrade all the guests computer virtual from version 4 to version 7.
      
  13. Detach the ESX host 3.5 since VMFS data warehouses.
      
  14. Remove the ESX 3.5 hosts vCenter 4.1
      
  15. Install all keys in license vSphere 4.1 (vSphere Standard Edition)
      
  16. Start the VM guests.
      
  17. Close and dismantle the old ESX 3.5 hosts.
      

  Any feedback is most appreciated.  Please let me know if I'm missing something.

  Then, you'd weigh your losses.  Do you have the characteristics of the hardware virtual v7 for these virtual machines or can you live with material v4?  Personally, I needed the changed block tracking which requires hardware v7.  It really comes down to what you need.  I recommend bringing them up to v7 but that's just my opinion.

• Transfer a Virtual Machine in Esx 2.5 to an ESX 4.1

  Hi all

  For a client, I need to transfer 3 virtual machines on an ESX 2.5 in stand-alone mode (local storage / VMFS2) for a new ESX 4.1 (local storage / VMFS3)

  I'm looking for a solution but without success. I see two ways to to do, but I can't test it before the migration, so could you give me your advice.

  (1) I copy all virtual machines in ESX 2.5 to the new storage to ESX 4.1 with scp.

  I create the virtual machine with the vmdk

  I put the last VmTools

  Upgrade virtual hardware

  (2) I have try the VmConverter username but I don'k know if he recognizes the VM Esx 2.5

  Is there another solution?

  Thanks for your help!

  Kind regards

  Franck

  the best solution in my opnion is with converter http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vcenter_converter_standalone/4_0?hl=pt-BR&sourceid=gd&rlz=1Q1GGLD_pt-BRBR411BR412

  After the conversion to put vmware tools and after upgrade virtual HW.

  Verification procedure «how improve HW» virtual

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

  Please, do not forget the points of call of the "useful" or "correct" answers

  Mauro Bonder - moderator

• Make a single LUN can be used by multiple ESX hosts

  Is it possible for a single LUN to be made usable by multiple ESX hosts at the same time?  For example, if you have an image or used by a vSphere environment requiring other vSphere environments in the data center access, you can put the image on a storage place where completely separate ESX hosts vSphere environments completely separate can see the same lun and clone the image or necessary?

  If the logic unit number is locked by accessed by an ESX host will be lock expires when the ESX host is not an another ESX host in another environment vSphere allowing access to the logical unit number, or is the lock, as it is usable by a single ESX host, until the storage is reconfigured to make it usable by a different host?

  Is there a better solution to this scenario?

  Thank you

  You can deploy both at the same time.  Locking occurs only for changes to metadata and only for the shooting of subsecond.  It is not required for the entire deployment process.

  -Matt

  VCP, VCDX #52, Unix Geek, Nerd of storage

• Failover storage and a new analysis while running virtual machines?

  The guys from storage must update the firmware on our HP EVA 8000 without. Currently, all my LUN is replicated to another EVA. The guys from storage you want to switch on the other EVA LUN so that they can make updates of the firmware without changing anything. I planned a complete failure of all my virtual machines and hosts so that they can make the switch. Basically stop all virtual machines, stop the hosts, making failover LUNs and then turn everything back.

  My question is there anything that can be done online? We tried it a couple of weeks, and we were hoping to have just the storage team launch the failover and a new analysis on the ESX hosts. All ESX hosts that had run VMs on those LUNS could would not fail on Mon after a new analysis. I have another cluster which can also display these LUNs. They were able to rescan and see the failure on Lun without problem. The only difference is that these other hosts have not the virtual machines running on these LUNs.

  If this working or is this the behavior that we should expect to see? This change in all with vSphere?

  Management has come back and asked why we must take a complete failure and whether it can be avoided in the future.

  > do failover LUNs and then turn everything back. My question is there anything that can be done online?

  Depends on your storage space.  If the LUNS are replicated really, they are up to date and your paths are correct on the ESX AND you use alternating (unfixed) it should work fine.

  This really isn't a function of VM Ware, because technically, storage is really transparent to ESX.  If you can find a valid path to the data, it will use it.  Just to make sure that is not the FIXED path.

• install ESX/ESXi on faster disks increases performance of the guest OS?

  for example, if you have installed ESX/ESXi on a faster local SSD or HARD disk, would be the overall performance of the ESXi and hosted OS be improved?

  Or ESX works completely in memory even after the start, so it does not improve a lot?

  If you have an iSCSI storage, I suggest you install ESX (i) on the local disk and attach (s) your storage iSCSI LUN as a VMFS data warehouses.

  André

• Best method to move vCenter VM to another ESX host?

  Update Manager has refused to allow us to stage an update for our ESX host our vCenter VM running on. So we have to move the other host our vCenter ESX just update this ESX host. But as we use vSphere Standard that does not come with vMotion and storage vMotion, we must stop vCenter and make a manual transfer.

  Did you guys a better method to do that in order to copy files from local storage ESX VM vCenter to the PC running the VI Client on and then copy the file vCenter VM from the PC to the local storage of the other local ESX storage? Because we do not have a usable for the moment SAN storage.

  BTW, we tried Storage vMotion with the year evaluation license last to move vCenter and it failed.

  We use mainly use the converter for the conversion or 'movement' of VMs from one region to the other because it is a GUI based process.  We have quite a few movements/conversions per week, so we have standardized on the converter.  If we have problems with converter (several failures, etc.) we will perform a dorsal scp of the actual VM files.  I agree that this method is faster, but in our case, we did not want to open the console for jobs like that, it seemed a more dangerous process from the console (deleting files etc...).  We used the converter to convert physical movement to virtual, virtual virtual clone, convert virtual from one version to another (workstation to esx for example).  I also like that the sysprep process can be automated in the process, but also some virtual machine configurations.  If we say PCS had a virtual machine to another location and we created a clone in the new location, we would have to scp, starting the virtual machine and then treat the sysprep (Windows) and rename, configuring ip etc...