ESX 3.5 compatibility with FasT700

[hblade]

Recently we upgraded from esx 3.02 to 3.5. It was only after this was completed that we discovered that our SAN was no lnger supported. Does anyone have any idea what the potential problems are if we do not revert back? we are currently recieving the following messages.

Dec 23 22:59:21 <servername> vmkernel: 5:07:04:27.622 cpu15:1334)StorageMonitor: 196: vmhba1:0:2:0 status = 24/0 0x0 0x0 0x0

[kjb007]

Those are not bad messages, per se. You're just getting additional information you didn't have before.

Not supported means that VMware won't guarantee that the device will work. If it does, great.

-KjB

[hblade]

We are also recieving these messages.

Jan 7 10:21:30 <servername> vmkernel: 18:22:11:14.847 cpu4:1069)VSCSI: 3019: Resetting handle 8271

Jan 7 10:21:30 <servername> vmkernel: 18:22:11:14.847 cpu4:1069)VSCSI: 2871: Completing reset on handle 8271

do they have a more serious significance?

[kjb007]

That looks like it's for a particular vm, and without more information, I would say probably not. If you want an official answer, I'd just open a support case.

-KjB

-Don't forget to leave points and mark helpful/correct posts

[mike_laspina · Accepted solution]

Hi,

I'm running about 4 hosts on a FastT700. Its at 3.5.0-110268 for the past few months and there are no issues at all.

[hblade]

Have you seen any of the errors that I posted on your ESX boxes?

[mike_laspina]

Yes. And it's not a issue.

They commonly add new log messaging in VMware releases. Wish they would document the messages and changes.

If you see vmkwarnings then thats something you should address as an issue.