Unable to boot UCS blade from SAN

[samtech]

I have cloned an existing profile and attached to a B200M3 blade in UCS 5108 chassis. The initiators seems to register fine on SAN. However, unable to see boot LUN's configured.

* There are no local drives

* First boot order is SAN and Second is cd-rom

Any pointers please.

[samtech]

Hi Walter

Please find below the output of steps to check zoning and SAN response.

adapter 1/1/1 (top):1# attach-fls
No entry for terminal type "dumb";
using dumb terminal settings.
adapter 1/1/1 (fls):1# vnic
---- ---- ---- ------- -------
vnic ecpu type state lif
---- ---- ---- ------- -------
13 1 fc active 3
14 2 fc active 4
adapter 1/1/1 (fls):2# lun
lunlist lunmap

adapter 1/1/1 (fls):2# lunlist 13
vnic : 13 lifid: 3
- FLOGI State : flogi est (fc_id 0x270302)
- PLOGI Sessions
- WWNN 50:06:01:69:3e:e0:3e:9e WWPN 50:06:01:69:3e:e0:3e:9e fc_id 0x270600
- LUN's configured (SCSI Type, Version, Vendor, Serial No.)
LUN ID : 0x0000000000000000 (0x0, 0x4, DGC , FCN00131500079)
- REPORT LUNs Query Response
LUN ID : 0x0000000000000000
- WWNN 50:06:01:60:3e:e0:3e:9e WWPN 50:06:01:60:3e:e0:3e:9e fc_id 0x270500
- LUN's configured (SCSI Type, Version, Vendor, Serial No.)
LUN ID : 0x0000000000000000 (0x0, 0x4, DGC , FCN00131500079)
- REPORT LUNs Query Response
LUN ID : 0x0000000000000000
- Nameserver Query Response
- WWPN : 50:06:01:60:3e:e0:3e:9e
- WWPN : 50:06:01:69:3e:e0:3e:9e

[Walter Dey]

Hi

Is your VSAN configuration correct ? eg. are the vhba in the proper VSAN ? do you see on the switch the flogi / fcns for the proper VSAN ?

[mojafri · Accepted solution]

Hi @samtech,

This shouldn't be related to SAN as of now, since we can see the LUN clearly under PLOGI session. Please follow the steps I'm attaching(Its for hyper-v but would be same for server edition) to install the FNIC driver during OS installation using driver ISO and let me know if you are able to see the LUN/disk or not. 

BTW, what is the BIOS mode? legacy or UEFI? Can you give below output? 

During the install (when it asks where to install Windows) try the following:

Format the drive seen in the windows setup

1. press SHIFT-F10 to open a command prompt
2. type 'diskpart'
3. type 'list disk'

Other way would be to use ESXi Cisco custom ISO and try to boot it - see if you are able to see the LUN (Just to confirm if end-to-end everything is good).

Regards,

MJ

[samtech · Accepted solution]

Updates...Booting with ESXi ISO shows boot LUN.

In the mean time I tried the steps as per Windows Server 2016-Install.pdf and was able to see the LUN and install Windows

Great document, however there is one minor error. The section where it points to install the FCoe drive is not under "Network" folder but "Storage folder". Rest of the path is same.

Thanks to everyone for helping me out here..