The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 807 - File: showthread.php PHP 7.3.15 (Linux)
File Line Function
/showthread.php 807 errorHandler->error





Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
initiator-iqn not getting set
2015-02-09, 23:36
Post: #1
initiator-iqn not getting set
Hello,

I'm having some troubles getting a newly purchased machine to boot from an iSCSI LUN served from a NetApp filer.

I can do a network install of CentOS6 or CentOS7 to a fresh LUN. The CentOS installer is able to find the iSCSI target and install the OS. Now my problems begin, as I cannot get the new machine to boot off the remote LUN.

Here is the relevant portion of my dhcpd.conf file:

Code:
host blah-iscsi {
     hardware ethernet 00:25:90:fc:3a:af;
     fixed-address 192.168.20.23;
     option root-path "iscsi:192.168.20.11:::1:iqn.1992-08.com.netapp:sn.1234:vs.4";
     option iscsi-initiator-iqn "iqn.2015-02.blah:1234";
}

During boot I see the following in my dhcp log files:


Code:
Feb  9 14:01:39 dhcpd: DHCPDISCOVER from 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:39 dhcpd: DHCPOFFER on 192.168.20.23 to 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:39 dhcrelay: packet to bogus giaddr 192.168.20.1.
Feb  9 14:01:41 dhcpd: DHCPREQUEST for 192.168.20.23 (192.168.1.5) from 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:41 dhcpd: DHCPACK on 192.168.20.23 to 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:41 dhcrelay: packet to bogus giaddr 192.168.20.1.
Feb  9 14:01:41 in.tftpd[27549]: tftp: client does not accept options

and if I interrupt the boot process and enter the iPXE command line ping does not work until I type "dhcp" on the command line.

[Image: pre-dhcp_ipxe_ping.jpg]


if I inspect the config settings prior to manually issing a dhcp command it appears that most values are set except for the iqn-iniiator value.

[Image: pre-dhcp_ipxe_config1.jpg]
page2.
[Image: pre-dhcp_ipxe_config2.jpg]

it looks like the iqn-initiator value is not properly set. So clearly dhcp is partially working

if I manually issue the dhcp command from iPXE, then inspect the config settings the iqn-initiator value IS getting properly set:

[Image: post-dhcp_ipxe_config1.jpg]
page2.
[Image: post-dhcp_ipxe_config2.jpg]

But back on the iPXE command line, issuing an autoboot still fails.

I'm at a bit of a loss. What to try next?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
initiator-iqn not getting set - classen - 2015-02-09 23:36



User(s) browsing this thread: 1 Guest(s)