04-19-2015 07:08 PM - edited 03-01-2019 12:08 PM
I cannot boot my blade to the iscsi boot lun after a patch and reboot.
running esxi 5.5 and b200 m2
iqn is correct. any idea? I am stuck here.
here is what I got from ucsm
adapter 1/1/1 # connect
No entry for terminal type "dumb";
using dumb terminal settings.
adapter 1/1/1 (top):1# attach-mcp
No entry for terminal type "dumb";
using dumb terminal settings.
adapter 1/1/1 (mcp):1# iscsi_get_config
vnic iSCSI Configuration:
----------------------------
vnic_id: 13
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-01.com.cisco:1000:ESXi:2
IP Addr: 10.60.3.101
Subnet Mask: 255.255.0.0
Gateway: 10.60.0.5
Target Cfg:
Target Idx: 0
State: INVALID
Prev State: ISCSI_TARGET_GET_SESSION_INFO
Target Error: ISCSI_TARGET_LOGIN_ERROR
IQN: iqn.2007-11.com.nimblestorage:esx1-bootvol-v53e2c6 e4ade1c307.00000032.fe0305e3
IP Addr: 10.60.1.21
Port: 3260
Boot Lun: 0
Ping Stats: Success (18.963ms)
Target Idx: 1
State: INVALID
Prev State: ISCSI_TARGET_GET_SESSION_INFO
Target Error: ISCSI_TARGET_LOGIN_ERROR
IQN: iqn.2007-11.com.nimblestorage:esx1-bootvol-v53e2c6 e4ade1c307.00000032.fe0305e3
IP Addr: 10.60.1.22
Port: 3260
Boot Lun: 0
Ping Stats: Success (18.933ms)
vnic_id: 14
link_state: Up
Initiator Cfg:
initiator_state: ISCSI_INITIATOR_FAILED
initiator_error_code: ISCSI_BOOT_NIC_DHCP_ERROR
vlan: 0
dhcp status: true
IQN: iqn.2015-01.com.cisco:1000:ESXi:3
IP Addr: 0.0.0.0
Subnet Mask: 0.0.0.0
Gateway: 0.0.0.0
Target Cfg:
Target Idx: 0
State: ISCSI_TARGET_DISABLED
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: iqn.2007-11.com.nimblestorage:esx1-bootvol-v53e2c6 e4ade1c307.00000032.fe0305e3
IP Addr: 10.60.1.21
Port: 3260
Boot Lun: 0
Ping Stats: Not issued
Target Idx: 1
State: ISCSI_TARGET_DISABLED
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: iqn.2007-11.com.nimblestorage:esx1-bootvol-v53e2c6 e4ade1c307.00000032.fe0305e3
IP Addr: 10.60.1.22
Port: 3260
Boot Lun: 0
Ping Stats: Not issued
04-20-2015 09:32 AM
Hi,
have you locked down the initiator group in nimble storage to the specific iqn?
also have you check that the boot volume iqn target is correct? i had a similar issue before, where i putty'd into nimble storage to get the iqn target info, and i had smaller putty window. the iqn target info was wrapped to the next line & i only copied part of it & i got a similar error to the above.
hope this helps.
04-20-2015 10:48 AM
yes this was working just fine prior to vmware patch updates. I dont think vmware patches would have anything to do with the boot from san to the nimble.
Still cannot boot. IQN looks fine
from iscsi_get_config
I see this error
ISCSI_TARGET_LOGIN_ERROR
IQN matches up with the one in nimble
IQN: iqn.2007-11.com.nimblestorage:esx1-bootvolv53e2c6e4ade1c307.00000032.fe0305e3
check the initiator group on nimble and the IQNs have full access to this bootvol
iqn.2015-01.com.cisco:1000:ESXi:2
iqn.2015-01.com.cisco:1000:ESXi:3
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide