Hi,
We have the following configuration:
IBM x3650 running ESX 4 (Cluster)
IBM x3650 running ESX 4 (Cluster)
IBM DS3400 SAN
Each IBM server has 2 direct attached Fiber connection through to the san for SPA and SPB
In the SAN RAID Array we have a few LUNs setup from 0 - 10, each Lun has or had a virtual machine running in it.
The virtual machine running on Lun 0 was decommissioned and therefore we removed the vmfs volume and the datastore from ESX and lastly removed LUN 0 from the SAN.
Now, in my /var/logs/vmkernel logs it seems that ESX is constantly looking for Lun 0 and is searching every few minutes on one HBA and then the other. It is doing this on both hosts.
Here is an extract of the log file:
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.463 cpu6:4245)ScsiScan: 839: Path 'vmhba1:C0:T0:L0': Vendor: 'IBM ' Model: '1726-4xx FAStT ' Rev: '0617'
@
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.463 cpu6:4245)ScsiScan: 842: Path 'vmhba1:C0:T0:L0': Type: 0x1f, ANSI rev: 5, TPGS: 0 (none)
@
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.463 cpu6:4245)ScsiScan: 105: Path 'vmhba1:C0:T0:L0': Peripheral qualifier 0x3 not supported
@
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.466 cpu6:4260)ScsiScan: 839: Path 'vmhba3:C0:T0:L0': Vendor: 'IBM ' Model: '1726-4xx FAStT ' Rev: '0617'
@
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.466 cpu6:4260)ScsiScan: 842: Path 'vmhba3:C0:T0:L0': Type: 0x1f, ANSI rev: 5, TPGS: 0 (none)
@
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.466 cpu6:4260)ScsiScan: 105: Path 'vmhba3:C0:T0:L0': Peripheral qualifier 0x3 not supported
Oct 30 12:34:10 vmcluster1 vmkernel: 1:15:45:02.466 cpu6:4260)ScsiScan: 105: Path 'vmhba3:C0:T0:L0': Peripheral qualifier 0x3 not supported
How do I remove this lun from ESX so that it doesn't search for it any longer ?
Note: Both the SAN and hosts have been rebooted and LUN 0 currently sits as free space on the SAN.