hi all!
recently, i'm facing a strange problem. i have updated my servers from esx 3.0.1 to 3.0.2 ... now whenever my servers exit maintanance mode ... i can not recognise my san ... to put it this way ... it does not list my SAN as a storage in the summary page ... only shows the storage present on the physical server ... i have to manually rescan all vmfs and hba to get it working ???
anyone else has faced this problem??? can this be rectified ???
There seems to be a bug in ESX 3.0.2 that affects iSCSI and ping latency.
Check this thread
http://www.vmware.com/community/thread.jspa?threadID=97117&messageID=722556#722556
Message was edited by:
oreeh
Link corrected
That is strange. I am not sure I can help but I will give it a shot. Give me some config details, what kind of SAN, servers, etc. And, tell me what you did to troubleshoot so far, rebooted SAN, Host server, etc.?
servers:
dell poweredge 6850 (intel tulsa processor) - esx server 1
dell poweredge 2950 (intel dual core) - esx server 2 and 3
dell poweredge 1950 (intel quadcore) - virtual center host
runnning:
esx server 3.0.2 and vi 3 ...
san:
emc san model - ax150 series ... iscsi protocol ...
... the problem rose to surface when we upgraded the esx servers to 3.0.2 ...
to troubleshoot, i manually rescan all vmfs and hba ... it then finds the san ...
but i have to do it every time the servers exit maintanance mode
would that b enuf ... or do u need more info ?
regards,
ahmed
There seems to be a bug in ESX 3.0.2 that affects iSCSI and ping latency.
Check this thread
http://www.vmware.com/community/thread.jspa?threadID=97117&messageID=722556#722556
Message was edited by:
oreeh
Link corrected
thanx a lot
I'm not sure, but this might be already fixed in one of the newest 3.0.2 patches.