How to check why a UCS blade server can’t boot from san

UCS-LAB-A# connect adapter 1/4/1
adapter 1/4/1 # 
adapter 1/4/1 # connect
adapter 1/4/1 (top):1# 
adapter 1/4/1 (top):1# attach-fls
adapter 1/4/1 (fls):1# 
adapter 1/4/1 (fls):1# vnic
---- ---- ---- ------- -------
vnic ecpu type state   lif
---- ---- ---- ------- -------
7    1    fc   active  4
8    2    fc   active  5
adapter 1/4/1 (fls):2# 
adapter 1/4/1 (fls):2# lunlist 7
vnic : 7 lifid: 4
  - FLOGI State : flogi est (fc_id 0x910001)
  - PLOGI Sessions
     - WWNN 50:0a:09:81:88:dd:97:bf WWPN 50:0a:09:81:88:dd:97:bf fc_id 0x910003
       - LUN's configured (SCSI Type, Version, Vendor, Serial No.)
           LUN ID : 0x000a000000000000 (0x0, 0x4, NETAPP  , P4DsRoviYRlA)
       - REPORT LUNs Query Response
           LUN ID : 0x0004000000000000
           LUN ID : 0x000a000000000000
  - Nameserver Query Response
     - WWPN : 50:0a:09:81:88:dd:97:bf

 

 

You can see that:

• The vnic command shows Server’s vHBAs (7 & 8, one for each fabric)
• the configuration at the UCS is to boot from WWPN 50:0a:09:81:88:dd:97:bf, LUN 10 (0x10) (Marked yellow)
• The server has access to WWPN 50:0a:09:81:88:dd:97:bf, Luns 4 & 10 (Marked brown)
    so Zonning (At the  MDS) and Lun masking (At NetApp) are OK, and the server will Boot