Hi all,
I already posted this on the forum but thought the list would also be a
good place to get feedback.
So, below the same as on the forum:
Last night I had to install some extra memory in our esx server. After
restarting the server the target on OF wasnt discovered any more.
My OF exports 3 volumes; 2 to the esx, one to a M$ file server.
The Windows server discovered and mounted its target without problems
and also discovered the other 2.
On esx the target with some vm's on it didnt show up and therefor I
couldnt start the servers.
Mind you, nothing was changed on OF and it always worked flawlessly the
way it was configured.
I reconfigured the esx initiator several times and rebooted the server
hoping the target would reappear, but to no avail.
After several hours of trying to locate and debug the possible cause I
started checking config files.
In initiators.allow I saw that the target were noted correctly and in
initiators.deny the targets were also there, followed by ALL...just as
it should be.
Not understanding why my fileserver discovered the target, but esx didnt
I remarked the line of the target in question, and what do you think?
After a rescan in esx the target appeared again!
I'm glad that this resolved the issue because the servers are running
happily again, but it still doesnt feel good.
How is it possible that the targets that were created using the gui
stopped working all of a sudden?
Is there a difference in the inner workings or method of target
discovery of the Microsoft initiator and Vmware?
How can it be that MS initiator sees the target while esx doesnt?
Once again, nothing changed in the config and the esx firewall was
disabled. I had to manually remove a line in initiators.deny to make esx
discover it again. Before the reboot all worked fine.
I'd like to discuss this, so any ideas??
-Patrick
_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users
