Hello,try this command after - Page 2

brandonlucas · ‎06-23-2015

Hi All -

I am trying to configure boot from SAN for a Windows 2012 R2 server running on a B22 M3. I have previously configured Cisco blades running ESXi 5.5 with no issues in regards to boot from SAN. However, I just can't get this to work. I have seen several posts on this issue but no one has had a solution.

I am using ONE iSCSI vNIC. Here is the output after initial boot to the ISO which I believe looks to be normal:

adapter 2/8/1 (mcp):9# iscsi_get_config

vnic iSCSI Configuration:
----------------------------

vnic_id: 15
link_state: Up

       Initiator Cfg:
     initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
                vlan: 0
         dhcp status: false
                 IQN: iqn:ucspd01:29
             IP Addr: removed
         Subnet Mask: 255.255.255.0
             Gateway: removed

          Target Cfg:
          Target Idx: 0
               State: ISCSI_TARGET_LUN_INITIALIZE
          Prev State: ISCSI_TARGET_DISABLED
        Target Error: ISCSI_TARGET_LUN_INIT_ERROR
                 IQN: iqn.1992-04.com.emc:cx.apm00130724582.a4
             IP Addr: removed
                Port: 3260
            Boot Lun: 0
          Ping Stats: Success (3000.365ms)
          Target Idx: 1
               State: ISCSI_TARGET_LUN_INITIALIZE
          Prev State: ISCSI_TARGET_DISABLED
        Target Error: ISCSI_TARGET_LUN_INIT_ERROR
                 IQN: iqn.1992-04.com.emc:cx.apm00130724582.b4
             IP Addr: removed
                Port: 3260
            Boot Lun: 0
          Ping Stats: Success (3009.012ms)

I see the initiators logged in and registered on the SAN. When I install the drivers, Windows just doesn't find the LUNs. My environment is running on 2.2(1d), but I have tried the 2.2.1 drivers and the 2.2.5 drivers. Both do not make a difference.

I have tried running the LUNLIST command but it seems to not work when using attach-mcp. attach-fls does not provide any output. Any ideas?

gregnewuk · ‎08-04-2015

Hi Brandon,

Did you get this resolved? I have a very similar issue.

B200 M4 with VIC 1340
1 x iSCSI vNIC, with 1 path to storage
NetApp FAS 8040, 60GB LUN, iGroup set to Windows 2008 or later and zoned in to the correct IQN
UCS firmware is 2.2(5a)
Windows Server 2012 R2 Standard (eval)

I can see the LUN, once I've messed about mapping the driver (enic6x64.inf) and then mapping the Server 2012 R2 CD back in again, but Windows will NOT install.

I've tried this, https://support.microsoft.com/en-us/kb/2826787, and after the second boot I got an error about it failing to initialise the partition on disk 2, see attached image.

I note that I can create partitions and delete them but I can't format them!

I've got 10 ESXi 6 hosts booting from SAN with no issues at all.

Any help greatly appreciated:-)

Cheers,

Greg

adapter 2/6/1 (mcp):4# iscsi_get_config

vnic iSCSI Configuration:
----------------------------

vnic_id: 17
link_state: Up

Initiator Cfg:
initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
vlan: 0
dhcp status: false
IQN: iqn.2015-07.com.abc:ldnprd-c-win-a:1
IP Addr: 10.0.201.141
Subnet Mask: 255.255.255.0
Gateway: 10.0.201.254

Target Cfg:
Target Idx: 0
State: ISCSI_TARGET_READY
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: iqn.1992-08.com.netapp:ldnprd-iscsi01
IP Addr: 10.0.201.22
Port: 3260
Boot Lun: 0
Ping Stats: Success (19.674ms)

Session Info:
session_id: 0
host_number: 0
bus_number: 0
target_id: 0

Walter Dey · ‎08-04-2015

Hi Greg

Are you aware of the 2.2.5a and B200-M4 caveat ? see https://supportforums.cisco.com/discussion/12568331/225a-caveat

This is however not your problem.

I can confirm, that I have exactly your configuration up and running.

Walter.

gregnewuk · ‎08-05-2015

Hi Walter,

Thanks for the heads up! I've only got 19 of those Blades due to go live in the next few days! I'll have a proper read up on it and might be in touch directly about it!

I've resolved the issue installing Server 2012 R2:-) It was completely my fault and so moronic that I'm embarrassed to actually say what it was, but I'm going to just in case some other poor soul that shouldn't be touching storage makes the same stupid mistake as me....

I had configured the Volume for Unix rather than NTFS.

Yes, that's many hours of my life I won't be getting back but it's a mistake I WON'T make again.

Cheers,
Greg

brandonlucas · ‎06-26-2015

I have a TAC case open now. Our UCS config looks good and we have confirmed the connectivity with the SAN is fine. It does look like perhaps a timeout issue or something is occurring, perhaps related to the high latency. Continuing to troubleshoot.

isaac anish · ‎06-24-2015

Hello,

try this command after connect attach-fls and check lunmap and lunlist...

Server 2012 R2 Boot from SAN with ISCSI - Can't recognize