vSphere 4 - Support on the Way?

[1parkplace]

my VMKernel logs have been fairly clean since I changed my iSCSI Daemon tuning options to what Todd recommended.

I am still getting these messages though in my VMKernel logs on ESX4.0:

Jun 5 11:08:57 vmhost-1 vmkernel: 6:01:50:02.470 cpu6:5337)ScsiScan: 105: Path 'vmhba33:C0:T2:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.469 cpu4:5340)ScsiScan: 839: Path 'vmhba33:C0:T1:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.469 cpu4:5340)ScsiScan: 842: Path 'vmhba33:C0:T1:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.469 cpu4:5340)ScsiScan: 105: Path 'vmhba33:C0:T1:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.470 cpu4:5340)ScsiScan: 839: Path 'vmhba33:C0:T2:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.470 cpu4:5340)ScsiScan: 842: Path 'vmhba33:C0:T2:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:13:57 vmhost-1 vmkernel: 6:01:55:02.470 cpu4:5340)ScsiScan: 105: Path 'vmhba33:C0:T2:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.469 cpu6:4171)ScsiScan: 839: Path 'vmhba33:C0:T1:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.469 cpu6:4171)ScsiScan: 842: Path 'vmhba33:C0:T1:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.469 cpu6:4171)ScsiScan: 105: Path 'vmhba33:C0:T1:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.470 cpu6:4171)ScsiScan: 839: Path 'vmhba33:C0:T2:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.470 cpu6:4171)ScsiScan: 842: Path 'vmhba33:C0:T2:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:18:57 vmhost-1 vmkernel: 6:02:00:02.470 cpu6:4171)ScsiScan: 105: Path 'vmhba33:C0:T2:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.701 cpu7:5341)ScsiScan: 839: Path 'vmhba33:C0:T1:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.701 cpu7:5341)ScsiScan: 842: Path 'vmhba33:C0:T1:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.701 cpu7:5341)ScsiScan: 105: Path 'vmhba33:C0:T1:L0': Peripheral qualifier 0x3 not supported
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.702 cpu7:5341)ScsiScan: 839: Path 'vmhba33:C0:T2:L0': Vendor: 'iSCSI ' Model: 'DISK ' Rev: '0 '
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.702 cpu7:5341)ScsiScan: 842: Path 'vmhba33:C0:T2:L0': Type: 0x1f, ANSI rev: 4, TPGS: 0 (none)
Jun 5 11:23:57 vmhost-1 vmkernel: 6:02:05:02.702 cpu7:5341)ScsiScan: 105: Path 'vmhba33:C0:T2:L0': Peripheral qualifier 0x3 not supported

[cschiff]

We are running DSS Build 3511 with ESX 3.5 U4. I have 2 DSS SANs each configured the same with 1 RAID 10 volume. Each SAN has 6 x 1 Gbps NIC ports. 2 are Bonded using Round-Robin for the GUI and 4 are Bonded using Round-Robin for iSCSI. These SANs only have 1 iSCSI target with multiple LUNs, each exposed only to a 3 ESX host Cluster.

[cschiff]

Drew,

I found an interesting VMware forum on you latest ESX logs.

http://communities.vmware.com/thread/212783

I would read this because even though things seem ok and the errors have stopped. I have as run into the issue when we first got our DSS SAN and they had not received VMware Certification for 3.5 either, where I had complete LUNs disappear or just the data within the LUNs disappears. Be very cautious if there is any critical data on these SANs. I know I got pretty freaked out when a 1/4 of my VMs disappeared into thin air.

Just curious, do any of you LUNs have an ID of 0?

[1parkplace]

Yea, I had actually read over that post early yesterday.

I had the same problem where my LUNs would disappear in a sense that when I browsed the Datastore on ESX all data was gone.

I had to reboot the ESX hosts and the DSS about 2 times before anything showed back up.

I later found that logging into the DSS and managing the target, that unmapping and remapping the LUN quickly fixes the problem and all of the VMs show back up and continue operating properly.

[To-M]

cschiff - I sent you an email on your forum account on obtaining our new DSS product version. I am only sending this to all VMware users now to test the new version as we have a new target sw package. Engineers cannot test every environment and we are hoping for some feedback and see if this fixes so many issues.

1parkplace has already received it.

Any one else willing to provide feedback before we release please ask me but provide feedback - please!

[cschiff]

Todd,

I never received your email???

We do have a 2nd SAN that I would be willing to load with the test copy of DSS. Once I have upgraded the backup SAN, I will upgrade 1 of my ESX server to vSphere 4.0 and provide you with detail positive and negative on how my testing is going.

Thx,

Christian

[To-M]

Check your forum email account - just sent it again. If you dont get i will send using your other email address.

[jsinclair]

I am willing to test out the new release. In fact, I have just started testing with 2 - DSS servers, iSCSI failover, and Volume Sync with ESX 3.5. I'm glad I saw this post, as we are planning on upgrading our VMware enviornment to vSphere 4 in the next week. Please let me know if I can participate in the Beta.

Thanks,
Jason

Info: 2x Dell PE 2950 with Perc 6/i and MD1000 split on 2x Perc 6/e
(4TB total with 15k SAS drives)

[To-M]

Many thanks Jason!

Please provide any comments that would help our engineers. Sometimes the customers see things we cannot.

Check your forum email.

[cschiff]

Todd,

I got the fille. I will update my backup SAN tonight and upgrade one of our ESX servers on Monday. I should hopefully have some feedback for you later on Monday or Tuesday at the latest.

Thx,

Christian