karo2k4
Contributor
Contributor

iSCSI volumes missing after last updates (1. September 2009)

Hi!

I have a cluster of 3 ESX 3.5 u4 Servers with SAN and iSCSI Connections (Software).

Yesterday I have updated two of them with the latest patches and both have no more connection to the iSCSI luns! VMWare does not see them anymore.

The settings have not changed and as far as i can see there are no error messages.

Are there any other admins with the same problem ? I can't imagine why this happened.

Thanks for any advice!

Karo

0 Kudos
5 Replies
vmw-sfraser
Enthusiast
Enthusiast

Hi Karo2k4,

What is the iSCSI array, and are there any errors in the vmkernel log when you do a rescan? Can you post a snippit? Also, the exact patch you applied would be helpful!

Cheers!






There are 10 types of people in this world. Those who understand binary, and those who do not.

There are 10 types of people in this world. Those who understand binary, and those who do not.
karo2k4
Contributor
Contributor

Hi !

I just get the following iSCSI related messages in the VMKernel log after a adapter rescan:

Sep 3 08:13:48 vmware07 vmkernel: 0:16:13:44.236 cpu2:1039)SCSI: 861: GetInfo for adapter vmhba32, , max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad001f

Sep 3 08:13:49 vmware07 vmkernel: 0:16:13:44.244 cpu3:1040)SCSI: 861: GetInfo for adapter vmhba32, , max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad001f

I applied all Patches for ESX 3.5 with the release date "31.08.2009"

The iSCSI array is "open-e" based.

ping and vmkping to the iSCSI Array is working

Thanks for your help!

Karo

Edit:

Sep 3 11:08:49 vmware07 vmkiscsid[4527]: login failed to authenticate with target

Sep 3 11:08:49 vmware07 vmkiscsid[4527]: discovery login to 10.2.9.1 rejected: initiator error (02/01), non-retryable, giving up

which means the Logininformations are not correct. But all should be right. Nothing have been changed. Tried a new user as well.

0 Kudos
karo2k4
Contributor
Contributor

After a rescan on the "old" Server i got "login failures" too but the LUN's appear.

Sep 3 12:07:45 gui-vmware05 vmkiscsid[26589]: Connected to Discovery Address 10.2.9.1

Sep 3 12:07:45 gui-vmware05 vmkiscsid[26589]: login failed to authenticate with target

Sep 3 12:07:45 gui-vmware05 vmkiscsid[26589]: discovery login to 10.2.9.1 rejected: initiator error (02/01), non-retryable, giving up

Sep 3 12:07:50 gui-vmware05 kernel: scsi singledevice 3 0 0 0

Sep 3 12:07:50 gui-vmware05 kernel: Vendor: iSCSI Model: DISK Rev: 0

Sep 3 12:07:50 gui-vmware05 kernel: Type: Direct-Access ANSI SCSI revision: 04

Sep 3 12:07:50 gui-vmware05 kernel: VMWARE SCSI Id: Supported VPD pages for sdd : 0x0 0x80 0x83

Sep 3 12:07:50 gui-vmware05 kernel: VMWARE SCSI Id: Device id info for sdd: 0x1 0x1 0x0 0x18 0x69 0x53 0x43 0x53 0x49 0x0 0x0 0x0 0x78 0x42 0x56 0x4b 0x59 0x6f 0x76 0x33 0x30 0x42 0x71 0x63 0x65 0x72 0x7a 0x4c

Sep 3 12:07:50 gui-vmware05 kernel: VMWARE SCSI Id: Id for sdd 0x20 0x20 0x20 0x20 0x44 0x49 0x53 0x4b 0x20 0x20

Sep 3 12:07:50 gui-vmware05 kernel: VMWARE: Unique Device attached as scsi disk sdd at scsi3, channel 0, id 0, lun 0

Sep 3 12:07:50 gui-vmware05 kernel: Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0

Sep 3 12:07:50 gui-vmware05 kernel: scan_scsis starting finish

Sep 3 12:07:50 gui-vmware05 kernel: SCSI device sdd: 1886918656 512-byte hdwr sectors (966102 MB)

Sep 3 12:07:50 gui-vmware05 kernel: sdd: sdd1

Sep 3 12:07:50 gui-vmware05 kernel: scan_scsis done with finish

Sep 3 12:07:50 gui-vmware05 kernel: scsi singledevice 3 0 0 1

Sep 3 12:07:51 gui-vmware05 kernel: Vendor: iSCSI Model: DISK Rev: 0

Sep 3 12:07:51 gui-vmware05 kernel: Type: Direct-Access ANSI SCSI revision: 04

Sep 3 12:07:51 gui-vmware05 kernel: VMWARE SCSI Id: Supported VPD pages for sde : 0x0 0x80 0x83

Sep 3 12:07:51 gui-vmware05 kernel: VMWARE SCSI Id: Device id info for sde: 0x1 0x1 0x0 0x18 0x69 0x53 0x43 0x53 0x49 0x0 0x0 0x0 0x79 0x6d 0x79 0x66 0x4a 0x78 0x61 0x76 0x68 0x73 0x38 0x62 0x63 0x75 0x32 0x33

Sep 3 12:07:51 gui-vmware05 kernel: VMWARE SCSI Id: Id for sde 0x20 0x20 0x20 0x20 0x44 0x49 0x53 0x4b 0x20 0x20

Sep 3 12:07:51 gui-vmware05 kernel: VMWARE: Unique Device attached as scsi disk sde at scsi3, channel 0, id 0, lun 1

Sep 3 12:07:51 gui-vmware05 kernel: Attached scsi disk sde at scsi3, channel 0, id 0, lun 1

Sep 3 12:07:51 gui-vmware05 kernel: scan_scsis starting finish

Sep 3 12:07:51 gui-vmware05 kernel: SCSI device sde: 2146953216 512-byte hdwr sectors (1099240 MB)

Sep 3 12:07:51 gui-vmware05 kernel: sde: sde1

Sep 3 12:07:51 gui-vmware05 kernel: scan_scsis done with finish

Sep 3 12:07:51 gui-vmware05 kernel: scsi singledevice 3 0 0 2

Sep 3 12:07:51 gui-vmware05 kernel: Vendor: iSCSI Model: DISK Rev: 0

Sep 3 12:07:51 gui-vmware05 kernel: Type: Direct-Access ANSI SCSI revision: 04

In my opinion, this is a strange behaviour

After i have disabled the CHAP auth. on the iSCSI array. all is working as before...

wording

0 Kudos
karo2k4
Contributor
Contributor

... Problem solved. It was a misconfiguration on the iSCSI array side.

Thanks for your help!

0 Kudos
vmw-sfraser
Enthusiast
Enthusiast

Glad to hear! CHAP can be a pain at the best of times. Smiley Happy

Cheers!






There are 10 types of people in this world. Those who understand binary, and those who do not.

There are 10 types of people in this world. Those who understand binary, and those who do not.
0 Kudos