ESXi

 View Only
  • 1.  Vmware ESX 4 (208167) - iSCSI issues.

    Posted Oct 27, 2011 11:23 AM

    Hello,
    I have been ripping my hair out over this over the last couple of hours.

    Run down of the Setup and tests
    * We have a production box ESX 4.0 (208167) box at Site A.  It connects to Dell Equallogic iSCSI storage at Site A fine (subnet 192.168.66.0/23)
    * We have a production box ESX 4.0 box at Site B.  It connects to a Buffalo Terrastation III iSCSI box located at Site B (subnet 192.168.58.0/23)
    * I attempted to connect the ESX box at Site A to the storage box at Site B.  Added the IP address to dynamic discovery.  It locates the storage device and fills in the static discovery for me fine.  It fails to show any discs from that storage device
    * I setup a quick test ESXi box at Site A and mapped the drive perfect first time - to prove that the storage can be mapped over the subnet.  This was using a single iSCSI connector.
    *The production box at Site A is configured with 2x iSCSI management ports for multi pathing (setup by a previous engineer).  Both connected to the same vSwitch and each mapped to an individual pNic and are on the Site A's subnet.
    * I can ping and trace route to the storage box from the console of Site A's ESX box.

    I have obtained this from the vmiscsid.log from the Site A production server after doing a scan:
    [quote]
    2011-10-27-12:00:08: iscsid: Login failed to authenticate with target
    2011-10-27-12:00:08: iscsid: discovery login to 192.168.58.62 rejected: initiator error (02/01), non-retryable, giving up
    2011-10-27-12:00:08: iscsid: cannot make connection to 192.168.58.62:3260 (101)
    2011-10-27-12:00:08: iscsid: connection to discovery address 192.168.58.62 failed
    2011-10-27-12:00:08: iscsid: connection login retries (reopen_max) 5 exceeded
    2011-10-27-12:00:08: iscsid: cannot make connection to 192.168.58.62:3260 (101)
    2011-10-27-12:00:08: iscsid: connection to discovery address 192.168.58.62 failed
    2011-10-27-12:00:08: iscsid: connection login retries (reopen_max) 5 exceeded
    2011-10-27-12:00:09: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:10: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:11: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:12: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:13: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array3,vmk0,192.168.58.62,3260,1,conn=0 Reason: 00040000
    2011-10-27-12:00:13: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:14: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:15: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:16: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:17: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array3,vmk1,192.168.58.62,3260,1,conn=0 Reason: 00040000
    2011-10-27-12:00:17: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:18: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:19: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:20: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:21: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array2,vmk0,192.168.58.62,3260,1,conn=0 Reason: 00040000
    2011-10-27-12:00:21: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:22: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:23: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:24: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:25: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array2,vmk1,192.168.58.62,3260,1,conn=0 Reason: 00040000
    2011-10-27-12:00:25: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:26: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:27: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:28: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:29: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array1,vmk0,192.168.58.62,3260,1,conn=0 Reason: 00040000
    2011-10-27-12:00:29: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:30: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:31: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:32: iscsid: cannot make a connection to 192.168.58.62:3260 (101,Network is unreachable)
    2011-10-27-12:00:33: iscsid: Login Failed: iqn.2004-08.jp.buffalo:iSCSI-STORAGE-SITE-B-4CE67648636C:TS03-Array1,vmk1,192.168.58.62,3260,1,conn=0 Reason: 00040000
    [/quote]

    And this is from the vmkernel log file:
    [quote]
    Oct 27 12:00:08 ESX-SiteA vmkernel: 0:16:33:46.775 cpu2:4107)ScsiScan: 843: Path 'vmhba0:C0:T0:L0': Vendor: 'DELL    '  Model: 'PERC 6/i        '  Rev: '1.11'
    Oct 27 12:00:08 ESX-SiteA vmkernel: 0:16:33:46.775 cpu2:4107)ScsiScan: 846: Path 'vmhba0:C0:T0:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
    Oct 27 12:00:08 ESX-SiteA vmkernel: 0:16:33:46.879 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:08 ESX-SiteA vmkernel: 0:16:33:46.879 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:09 ESX-SiteA vmkernel: 0:16:33:47.025 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:10 ESX-SiteA vmkernel: 0:16:33:48.026 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:11 ESX-SiteA vmkernel: 0:16:33:49.028 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:12 ESX-SiteA vmkernel: 0:16:33:50.029 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:13 ESX-SiteA vmkernel: 0:16:33:51.055 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:14 ESX-SiteA vmkernel: 0:16:33:52.056 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:15 ESX-SiteA vmkernel: 0:16:33:53.058 cpu2:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:16 ESX-SiteA vmkernel: 0:16:33:54.060 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:17 ESX-SiteA vmkernel: 0:16:33:55.083 cpu1:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:18 ESX-SiteA vmkernel: 0:16:33:56.083 cpu1:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:19 ESX-SiteA vmkernel: 0:16:33:57.084 cpu1:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:20 ESX-SiteA vmkernel: 0:16:33:58.085 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:21 ESX-SiteA vmkernel: 0:16:33:59.117 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:22 ESX-SiteA vmkernel: 0:16:34:00.118 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:23 ESX-SiteA vmkernel: 0:16:34:01.120 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:24 ESX-SiteA vmkernel: 0:16:34:02.122 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:25 ESX-SiteA vmkernel: 0:16:34:03.145 cpu2:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:26 ESX-SiteA vmkernel: 0:16:34:04.146 cpu2:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:27 ESX-SiteA vmkernel: 0:16:34:05.148 cpu2:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:28 ESX-SiteA vmkernel: 0:16:34:06.149 cpu0:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk0 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:29 ESX-SiteA vmkernel: 0:16:34:07.175 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:30 ESX-SiteA vmkernel: 0:16:34:08.176 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:31 ESX-SiteA vmkernel: 0:16:34:09.178 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:32 ESX-SiteA vmkernel: 0:16:34:10.179 cpu3:4238)Tcpip_Vmk: 165: cannot honor socket binding with vmk1 (src_subnet=0xc0a84200, dst_subnet=0xc0a83a00)
    Oct 27 12:00:33 ESX-SiteA vmkernel: 0:16:34:11.247 cpu3:4105)ScsiScan: 843: Path 'vmhba33:C1:T0:L0': Vendor: 'OPNFILER'  Model: 'VIRTUAL-DISK    '  Rev: '0   '
    Oct 27 12:00:33 ESX-SiteA vmkernel: 0:16:34:11.247 cpu3:4105)ScsiScan: 846: Path 'vmhba33:C1:T0:L0': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)
    Oct 27 12:00:33 ESX-SiteA vmkernel: 0:16:34:11.248 cpu3:4105)ScsiScan: 843: Path 'vmhba33:C0:T0:L0': Vendor: 'OPNFILER'  Model: 'VIRTUAL-DISK    '  Rev: '0   '
    Oct 27 12:00:33 ESX-SiteA vmkernel: 0:16:34:11.248 cpu3:4105)ScsiScan: 846: Path 'vmhba33:C0:T0:L0': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)
    Oct 27 12:00:36 ESX-SiteA vmkernel: 0:16:34:14.052 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x410005047f40) to NMP device "mpx.vmhba1:C0:T0:L0" failed on physical path "vmhba1:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    Oct 27 12:00:36 ESX-SiteA vmkernel: 0:16:34:14.052 cpu1:4097)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)Vol3: 1488: Could not open device '4b583fe2-5234b320-871b-001b212f6111' for probing: No such target on adapter
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)Vol3: 608: Could not open device '4b583fe2-5234b320-871b-001b212f6111' for volume open: No such target on adapter
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)FSS: 3702: No FS driver claimed device '4b583fe2-5234b320-871b-001b212f6111': Not supported
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)Vol3: 1488: Could not open device '48dd2e35-9a7c9490-bf68-001d0968fb86' for probing: No such target on adapter
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)Vol3: 608: Could not open device '48dd2e35-9a7c9490-bf68-001d0968fb86' for volume open: No such target on adapter
    Oct 27 12:00:40 ESX-SiteA vmkernel: 0:16:34:18.172 cpu2:4105)FSS: 3702: No FS driver claimed device '48dd2e35-9a7c9490-bf68-001d0968fb86': Not supported
    [/quote]




  • 2.  RE: Vmware ESX 4 (208167) - iSCSI issues.

    Posted Oct 27, 2011 11:48 AM

    I think I may have answered my own question

    Am I right in thinking (digging back through my brains after reading a few books!), that in the configuration of Site A ESX box, in which we have 2x iSCSI kernal ports, mapped to individual pNIC's that they are no longer able to route traffic from one subnet to another?   This would explain that when testing using the ESXi test box, I only had a single iSCSI kernal port which can route.

    In which case, I would need to create a seperate vSwitch with a kernal port connected to the subnet of Site B to use stotage there?