Modifying NetApp space plans from non-ALUA to ALUA

Modifying NetApp space plans from non-ALUA to ALUA

My personal most recent client was still operating on VMware ESX 3.5 and digital heart 2.5 and questioned me to upgrade their own planet. Their own entire conditions was running on NetApp storage space and also for ESX there is a change in the Storage selection kind coverage (SATP) therefore the route Selection rules (PSP) when transferring from ESX 3.5 to 4.1.

We going because of this blogpost by Nick Triantos: vSphere: improving from non-ALUA to ALUA. We have added some extra’s We encountered during improvement and can reveal how changes can be carried out with the brand new NetApp Virtual space Console (VSC).

Very first action is obviously the improve (in fact i did so a reinstall) of Virtual Center to vCenter 4.1, with a new apply from the ESX hosts. I changed from ESX 3.5 boot from SAN, to ESXi 4.1 booting from USB sticks. Whenever all your valuable VMs include running on the newly installed ESXi 4.1 hosts, the storage coverage can be your after that concern.

Per NetApp records and VMware HCL, the most preferred policy for ESXi 4.1 offers connected to NetApp FAS3020, is utilizing ALUA with a game Robin policy. Usually i’d made certain that after installations the most suitable storing rules was actually put. However, during the storage build which was already existing, there is one larger amount focused on VMware and that quantity holds some LUNs being presented to the ESX offers. This quantity has a-one to 1 mapping towards the ESX iGroup. On NetApp ALUA can simply getting triggered at iGroup levels, which means that ALUA is actually triggered for the LUNs at the same time. Would You will find enabled ALUA following the very first number was actually run ESXi 4.1, the ESX 3.5 offers (pending improve) would have received the ALUA policy. …