Unable to Recognize New SAN LUNs After Rescan (Vmware ESX server)

After you scan the SAN for the currently presented LUNs, the service console needs to be made aware of the LUN changes.

If your ESX Server version is less than 2.5, you need to perform the following three steps. If your ESX Server version is 2.5 or greater, you need to perform only the third step.

The first step flushes the cache in the HBA (fiber host bus adapter). The second step scans the SAN for presented LUNs. The third step creates device nodes required to partition the available LUNS into VMFS volumes.

Note: The first step applies to QLogic HBAs only, not to Emulex HBAs.

1. If you have Emulex HBAs, skip this step. Otherwise, for QLogic HBAs only, run wwpn.pl with the -s option for each HBA through which the LUN is accessed. For example:
   wwpn.pl -s vmhba1
2. Run vmkfstools with the -s option for each HBA through which the LUN is accessed. For example:
   vmkfstools -s vmhba1
3. Run cos-rescan.sh on the same HBA as in the step above. For example:
   cos-rescan.sh vmhba1