I’ve been having trouble getting our ESX 3.5 to see an iSCSI target.
It has not been set up previously to use iSCSI on our ESX host. I have followed the directions in VMWare’s documentation using the VI Client with no success.
I’ve also redone it using the command line. Still nothing when I rescan several times in VIC.
So, I might have traced it down to a problem with the VMKernel NIC: it responds to pings using vmkping on the host. However, should I be able to see it from the LAN? From my workstation it does not respond.
The list of IPs:
10.1.0.80 – our SATABeast which is configured to be the target
10.1.0.81 – the VMKernel NIC on vSwitch2
10.1.0.82 – the service console on vSwitch2
I can see the target at 10.1.0.80 and the service console at 10.1.0.82, but not the VMKernel NIC.
Any tips? I’ve had a couple of weeks trying to figure this out and following the directions over and over but still no result.
Or is there a chance that something was set up originally (several years ago – before my time with it) with the ESX host that is preventing any of this?
You must be logged in to reply to this topic.
Create a free account today to participate in forum conversations, comment on posts and more.