From: <br...@v3...> - 2012-08-23 04:09:42
|
ih does SCST support NAA Id's for FC Luns? I guess the real question is does SCST SRP support NAA ID's??? Specifically for ESXi 4.1 U2 "This behavior is prevented through the support and use of NAA for SAN LUNs with VMware ESX 3.5 Update 5 and later. We introduced the supportability for NAA ID's with ESX 3.5 GA. However, we stopped using the LUN ID to reference the device from Update 5 onward." trudging through the VMWARE logs for LVM i found some errors that suggest "First, the device is shared with a different SCSI ID. This might be due to a simple mistake in the array config. You thought the LUN is the same but it isn't. In this case the second ESX will protect the volume by refusing to present it. " 2012-08-23T03:13:13.947Z cpu3:2051)ScsiDeviceIO: 2322: Cmd(0x412400746a40) 0x93, CmdSN 0xb3528 from world 3844 to dev "eui.3262653765663939" failed H:0x7 D:0x2 P:0x0 Possible sense data: 0x5 0x20 0x0. 2012-08-23T03:13:13.947Z cpu3:2051)ScsiDeviceIO: 2322: Cmd(0x41240079e8c0) 0x93, CmdSN 0xb3527 from world 3844 to dev "eui.3262653765663939" failed H:0x7 D:0x2 P:0x0 Possible sense data: 0x5 0x20 0x0. 2012-08-23T03:13:13.948Z cpu3:2051)lpfc820 0000:09:00.0: 0:(0):0720 FCP command x93 residual overrun error. Data: x200 x0 WARNING: LinSCSI: 4371: The physical media represented by vmhba1:0:1 has changed and the device is in use. The device cannot be re-synchronized with the system. This is a critical error. we noticed that when we have this problem, and the vmware host wants to re-signature the Lun, if we release the server that has access to the Lun. Then the other node can then re scan and attach to the Lun. So its being locked, as suggested by vmware. Is there any easy fix in SCST at all? we notice the same problem via any transport iSCSI, FC or SRP. in otherwords its not the transport causing this, its the Lun/LVM Guid causing Vmware to lock the partition. if we dis-conenct SRP from Node2 then node 1 can see the Lun and not insist on re-signature. Regards Bruce m ESX I NODE 1 VIA FIBRE CHANNEL ~ # ls -l /vmfs/volumes drwxr-xr-x 1 root root 8 Jan 1 1970 2d6e5aef-5c4dcd72-94ff-8d0189b942b9 drwxr-xr-x 1 root root 8 Jan 1 1970 502872a6-e9c713df-38e8-0007e911a051 drwxr-xr-t 1 root root 1680 Aug 23 03:13 5028a56a-86bf1885-df3b-0007e911a051 drwxr-xr-t 1 root root 1260 Aug 15 08:20 5028a818-1b2f3c16-e756-0007e911a051 drwxr-xr-t 1 root root 1120 Aug 16 03:52 502c6e8b-cbcf9760-7b23-00151787ba15 drwxr-xr-t 1 root root 1260 Aug 23 01:32 5034b286-b2a7c657-dfd2-0017a4772400 drwxr-xr-t 1 root root 1260 Aug 23 02:55 503598f6-8eb416f7-82fb-0017a477240a drwxr-xr-t 1 root root 1400 Aug 15 08:20 507239f4-b5c7cec8-c7e2-00151787ba15 drwxr-xr-x 1 root root 8 Jan 1 1970 6ec6f1e6-31b30738-4fbb-5c95160b7653 lrwxr-xr-x 1 root root 35 Aug 23 03:24 CloudS_WEBLB -> 5028a818-1b2f3c16-e756-0007e911a051 lrwxr-xr-x 1 root root 17 Aug 23 03:24 ISO1 -> df9ba2b7-d1a4ee3b lrwxr-xr-x 1 root root 17 Aug 23 03:24 ISO2 -> c637379a-e0f598c8 lrwxr-xr-x 1 root root 35 Aug 23 03:24 MYSQLMS -> 507239f4-b5c7cec8-c7e2-00151787ba15 lrwxr-xr-x 1 root root 35 Aug 23 03:24 V365_CoreAPPS -> 5028a56a-86bf1885-df3b-0007e911a051 drwxrwxrwx 1 root root 73 Aug 15 00:07 c637379a-e0f598c8 drwxrwxrwx 1 root root 4096 Aug 21 05:52 df9ba2b7-d1a4ee3b lrwxr-xr-x 1 root root 35 Aug 23 03:24 test2 -> 503598f6-8eb416f7-82fb-0017a477240a lrwxr-xr-x 1 root root 35 Aug 23 03:24 testsas -> 5034b286-b2a7c657-dfd2-0017a4772400 lrwxr-xr-x 1 root root 35 Aug 23 03:24 v365DNS_DATA -> 502c6e8b-cbcf9760-7b23-00151787ba15 ESXI NODE 1 (BLADE) VIA SRP drwxr-xr-x 1 root root 8 Jan 1 1970 2da668ef-40e5d96b-90bf-855ddb9c5547 drwxr-xr-x 1 root root 8 Jan 1 1970 34f290e9-e510916c-438c-17eedaa964c5 drwxr-xr-t 1 root root 1540 Aug 23 01:54 502e4b9e-ca297b56-f781-0017a4772402 drwxr-xr-t 1 root root 1400 Aug 20 17:47 502e4bf1-10747ca2-fa33-0017a4772402 drwxr-xr-t 1 root root 1260 Aug 23 01:32 5034b286-b2a7c657-dfd2-0017a4772400 drwxr-xr-t 1 root root 1260 Aug 23 02:55 503598f6-8eb416f7-82fb-0017a477240a lrwxr-xr-x 1 root root 35 Aug 23 03:36 CloudOS1 -> 502e4b9e-ca297b56-f781-0017a4772402 lrwxr-xr-x 1 root root 35 Aug 23 03:36 Cloud_T1 -> 502e4bf1-10747ca2-fa33-0017a4772402 lrwxr-xr-x 1 root root 35 Aug 23 03:36 Hypervisor1 -> 34f290e9-e510916c-438c-17eedaa964c5 lrwxr-xr-x 1 root root 35 Aug 23 03:36 Hypervisor2 -> a2f206ec-1ece952b-3ccc-a6dfc62854cc lrwxr-xr-x 1 root root 35 Aug 23 03:36 Hypervisor3 -> 2da668ef-40e5d96b-90bf-855ddb9c5547 lrwxr-xr-x 1 root root 17 Aug 23 03:36 ISO -> f27f3ceb-977e1c50 drwxr-xr-x 1 root root 8 Jan 1 1970 a2f206ec-1ece952b-3ccc-a6dfc62854cc drwxrwxrwx 1 root root 4096 Aug 21 05:52 f27f3ceb-977e1c50 lrwxr-xr-x 1 root root 35 Aug 23 03:36 test2 -> 503598f6-8eb416f7-82fb-0017a477240a lrwxr-xr-x 1 root root 35 Aug 23 03:36 testsas -> 5034b286-b2a7c657-dfd2-0017a4772400 3RD Blade via SRP drwxr-xr-x 1 root root 8 Jan 1 1970 2da668ef-40e5d96b-90bf-855ddb9c5547 drwxr-xr-x 1 root root 8 Jan 1 1970 34f290e9-e510916c-438c-17eedaa964c5 drwxr-xr-t 1 root root 1540 Aug 23 01:54 502e4b9e-ca297b56-f781-0017a4772402 drwxr-xr-t 1 root root 1400 Aug 20 17:47 502e4bf1-10747ca2-fa33-0017a4772402 drwxr-xr-t 1 root root 1260 Aug 23 01:32 5034b286-b2a7c657-dfd2-0017a4772400 lrwxr-xr-x 1 root root 35 Aug 23 03:43 CloudOS1 -> 502e4b9e-ca297b56-f781-0017a4772402 lrwxr-xr-x 1 root root 35 Aug 23 03:43 Cloud_T1 -> 502e4bf1-10747ca2-fa33-0017a4772402 lrwxr-xr-x 1 root root 35 Aug 23 03:43 Hypervisor1 -> 34f290e9-e510916c-438c-17eedaa964c5 lrwxr-xr-x 1 root root 35 Aug 23 03:43 Hypervisor2 -> a2f206ec-1ece952b-3ccc-a6dfc62854cc lrwxr-xr-x 1 root root 35 Aug 23 03:43 Hypervisor3 -> 2da668ef-40e5d96b-90bf-855ddb9c5547 lrwxr-xr-x 1 root root 17 Aug 23 03:43 ISO1 -> f27f3ceb-977e1c50 drwxr-xr-x 1 root root 8 Jan 1 1970 a2f206ec-1ece952b-3ccc-a6dfc62854cc drwxrwxrwx 1 root root 4096 Aug 21 05:52 f27f3ceb-977e1c50 lrwxr-xr-x 1 root root 35 Aug 23 03:43 testsas -> 5034b286-b2a7c657-dfd2-0017a4772400 SO IT CANT MOUNT 35 AUG 23 03:36 TEST2 -> 503598F6-8EB416F7-82FB-0017A477240A if i try to add it i get the ole message asking to resignature it. please help |