Boot from SAN problem

[mhyde]

I am having a problem getting boot from SAN working.  I have a UCS B series.  I have configured fiber channel and it is up and working.  If I boot from a vmware CD, I can see the SAN and install to the proper LUN.  When I try to setup the system to boot from it, I get an access failure.  Any ideas?

adapter 1/7/1 (fls):5# lunlist

vnic : 15 lifid: 4

  - FLOGI State : flogi est (fc_id 0x0f0041)

  - PLOGI Sessions

     - WWNN 21:00:00:24:ff:2f:fa:dc WWPN 21:00:00:24:ff:2f:fa:dc fc_id 0x0f0020

       - LUN's configured (SCSI Type, Version, Vendor, Serial No.)

           LUN ID : 0x0004000000000000  access failure

       - REPORT LUNs Query Response

           LUN ID : 0x0000000000000000

  - Nameserver Query Response

     - WWPN : 21:00:00:24:ff:2f:fa:dc

zoneset name zs_vsan100 vsan 100

  zone name zone_vsan_100 vsan 100

    pwwn 20:00:00:25:b5:10:10:01

    pwwn 20:00:00:25:b5:10:10:02

    pwwn 20:00:00:25:b5:10:10:03

  * fcid 0x0f0041 [pwwn 20:00:00:25:b5:10:10:04]

  * fcid 0x0f0020 [pwwn 21:00:00:24:ff:2f:fa:dc]

The SAN is a freenas server.

[amarino2]

You have your Boot Policy configured for LUN 4, but you're actually using LUN 0

- LUN's configured (SCSI Type, Version, Vendor, Serial No.)

           LUN ID : 0x0004000000000000  access failure

REPORT LUNs Query Response

           LUN ID : 0x0000000000000000

[mhyde]

The LUN is actually on 4.  If I change it to 0, then I get this:

adapter 1/7/1 (fls):8# lunlist

vnic : 15 lifid: 4

  - FLOGI State : flogi est (fc_id 0x0f0041)

  - PLOGI Sessions

     - WWNN 21:00:00:24:ff:2f:fa:dc WWPN 21:00:00:24:ff:2f:fa:dc fc_id 0x0f0020

       - LUN's configured (SCSI Type, Version, Vendor, Serial No.)

           LUN ID : 0x0000000000000000  access failure

       - REPORT LUNs Query Response

  - Nameserver Query Response

     - WWPN : 21:00:00:24:ff:2f:fa:dc

And if I wait long enough:

adapter 1/7/1 (fls):10# lunlist

vnic : 15 lifid: 4

  - FLOGI State : flogi est (fc_id 0x0f0041)

  - PLOGI Sessions

     - WWNN 21:00:00:24:ff:2f:fa:dc WWPN 21:00:00:24:ff:2f:fa:dc fc_id 0x0f0020

       - LUN's configured (SCSI Type, Version, Vendor, Serial No.)

           LUN ID : 0x0000000000000000  access failure

       - REPORT LUNs Query Response

           LUN ID : 0x0000000000000000

  - Nameserver Query Response

     - WWPN : 21:00:00:24:ff:2f:fa:dc

[Walter Dey]

I assume you could see the lun, and install ESXi; therefore FC zoning is ok.

Btw. did you use the Cisco OEM iso ? if not you need to install the proper enic/fnic drivers, according to http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

If boot fails, something is worng with the boot policy !

http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b-series-blade-servers/115764-ucs-san-tshoot-00.html

What is the actual resp. configured boot order

[mhyde]

If I boot the vmware ISO (cisco oem), it sees the fiber channel storage and all the LUNs.  I am able to install onto the proper LUN.  When I reboot, the HBA driver does not install on UCS, and the logs show the access failure.

[Walter Dey]

Is your vhba name in the service profile "fc0" resp. "fc1"; your lun id is 2 ?

By default, the Boot Policy enforces vnic/vhba/iscsi name; therefore the name in the SP and in the boot policy have to match

[mhyde]

They are.  The LUN I am connecting too has been changing as I work on trying to make it work.  It currently is at 2.

[Walter Dey]

Please post configured and actual boot order !

[mhyde]

Here it is.  Lun was changed to 0 this time.

[Walter Dey]

Do I see this correctly ?

WWNN 21:00:00:24:ff:2f:fa:dc WWPN 21:00:00:24:ff:2f:fa:dc

pwwn=nwwn ??

I would change that asap ! are you using a MDS or a N5k as fc switch ?

[mhyde]

I am using an MDS 9222i.  21:00:00:24:ff:2f:fa:dc is the freenas storage array.  It  does not look like I can change either the pwwn or nwwn.

[Walter Dey]

What brand of HBA does your freenas use ? Qlogic ? Emulex ?

[mhyde]

Qlogic QLW2462

[Walter Dey]

I assume this is a dual port hba, therefore it should have one nwwn and 2 pwwn. They have embedded values, but can be changed.

[mhyde]

It is a dual port:

INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc1/10 100 0x0f0020 21:00:00:24:ff:2f:fa:dc 20:00:00:24:ff:2f:fa:dc
fc1/11 200 0x5c0000 21:00:00:24:ff:2f:fa:dd 20:00:00:24:ff:2f:fa:dd