Cisco UCS iSCSI boot question

joeharb · ‎08-02-2012

I am having trouble with getting this to work. I don't control the iSCSI side of the equation so I am just trying to make sure everything is correct on the UCS side. When we boot we get an the "Initialize error 1"

If I attach to FI via ssh I am able to ping the target ip's. The SAN administrator says that the UCS has to register before itself (which isn't occuring) prior to him giving it space. Everything I have seen the LUN's and Mask are created prior to boot...is this required?

Thanks,

Joe

anil.gumadavalli · ‎08-02-2012

Get to the boot policy, you will see at the bottom of the screen, saying set iscsi boot parameters, set the iscsi pool and initiator and target, you will be all set.

Follow this link to configure correctly:

http://wwtvirtualization.files.wordpress.com/2011/12/flexpod-iscsi-boot-fixed.pdf

thank you,

AK G

padramas · ‎08-02-2012

Hello Joe,

A few questions

UCSM version ?

Does any other blades work ?

What storage array is being used here ?

SSH into FI , connect to the adapter and please provide the following output

connect adapter x/y/z
connect
attach-mcp
iscsi_get_config

Padma

joeharb · ‎08-03-2012

UCSM version

2.0(2r)

We have another blade the other chasis that has ESX installed on the local drive and is using the iSCSI SAN as it datastore, therefore I know I connectivity to the SAN. The storage array is a emc CX4-120.

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

vnic iSCSI Configuration:

----------------------------

vnic_id: 5

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.1992-04.com.cisco:2500

IP Addr: 192.168.0.109

Subnet Mask: 255.255.255.0

Gateway: 192.168.0.2

Target Cfg:

Target Idx: 0

State: INVALID

Prev State: ISCSI_TARGET_GET_SESSION_INFO

Target Error: ISCSI_TARGET_LOGIN_ERROR

IQN: iqn.1992-04.com.emc:cx.apm00101701431:a2

IP Addr: 192.168.0.2

Port: 3260

Boot Lun: 0

Ping Stats: Success (19.297ms)

Target Idx: 1

State: INVALID

Prev State: ISCSI_TARGET_GET_SESSION_INFO

Target Error: ISCSI_TARGET_LOGIN_ERROR

IQN: iqn.1992-04.com.emc:cx.apm00101701431:b2

IP Addr: 192.168.0.3

Port: 3260

Boot Lun: 0

Ping Stats: Success (18.229ms)

adapter 2/1/1 (mcp):2#

joeharb · ‎08-03-2012

Update I have changed the iqn for the target and now I getting different output, but still inialize error 1.

nic_id: 6

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.1992-04.com.cisco:2500

IP Addr: 192.168.0.109

Subnet Mask: 255.255.255.0

Gateway: 192.168.0.2

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.apm00101701431.a2

IP Addr: 192.168.0.2

Port: 3260

Boot Lun: 0

Ping Stats: Success (18.543ms)

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.apm00101701431.b2

IP Addr: 192.168.0.3

Port: 3260

Boot Lun: 0

Ping Stats: Success (18.489ms)

kg6itcraig · ‎08-03-2012

Try giving the LUN an ID of 1.

Also I see:

initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR

vlan: 0

Do you have the vNIC in a VLAN?

Have a nice doc and video on my side of the great stuggle iSCSI was to get working.

http://realworlducs.com/cisco-ucs-iscsi-boot-appliance-ports/

Craig

My UCS Blog http://realworlducs.com

joeharb · ‎08-03-2012

Craig,

I used your docs and video for most of my setup (Good Stuff). The SAN administrator has said that he needs my initiators to be registered before he can mask them, is this true or does the actual SAN stuff need to be completed prior to boot? I have checked vnic and it has vlan 2000 set to native. I have also found other instance where the

iscsi_get_config shows a vlan value of 0, on your setup did it show the actual vlan? After I made some changes to the target I did get different results as stated above:

initiator_state: ISCSI_INITIATOR_READY

initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR

vlan: 0

dhcp status: false

IQN: iqn.1992-04.com.cisco:2500

IP Addr: 192.168.0.109

Subnet Mask: 255.255.255.0

Gateway: 192.168.0.2

Target Cfg:

Target Idx: 0

State: ISCSI_TARGET_LUN_INITIALIZE

Prev State: ISCSI_TARGET_DISABLED

Target Error: ISCSI_TARGET_LUN_INIT_ERROR

Is this better as in have I attached to the SAN but just don't have any luns avaialble?

Thanks,

Joe