Re: no DHCP-assigned InitiatorName

This is a multipart message in MIME format.
--===============1277100288==
Content-Type: multipart/alternative; boundary="=_alternative 005F3552852574CC_="

This is a multipart message in MIME format.
--=_alternative 005F3552852574CC_=
Content-Type: text/plain; charset="US-ASCII"

Michael,

I will have to defer to boot RFC authors. My 2 cents is that DHCP 
"practice" has already several mechanisms to name the initiator (most 
based on what the DHCP agents present to the DHCP server - like the real 
of "fake" (for VMs) MAC address. And I don't know how the iBFT interacts 
(or is supposed to) with a DHCP server.

Regards,
Julo



From:
Michael Howard <[email protected]>
To:
Julian Satran/Haifa/IBM@IBMIL
Cc:
[email protected], Sivan Tal/Haifa/IBM@IBMIL
Date:
09/22/2008 11:42
Subject:
Re: [Ips] no DHCP-assigned InitiatorName





Julian Satran wrote:
> Michael,
> 
> I think that some of the OSs have the initiator name wired into the 
> image and boot providers will have to set this name.

I do not understand what you are trying to say.

On x86 architectures the iBFT (iSCSI Boot Firmware Table) is used to 
pass iSCSI boot parameters to the OS. The iSCSI boot parameters include 
target information and InitiatorName ... so that a new session 
(attaching to the same LUN) can be established by the OS driver.

> I am not sure how what exactly is required for each version.
> The boot RFC defines where the image comes from but very little else.

I am arguing that "very little else" is actually too little ;)

> Sivan may give you a pointer to CbCS.

OK


Michael




--=_alternative 005F3552852574CC_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Michael,</font>
<br>
<br><font size=2 face="sans-serif">I will have to defer to boot RFC authors.
My 2 cents is that DHCP &quot;practice&quot; has already several mechanisms
to name the initiator (most based on what the DHCP agents present to the
DHCP server - like the real of &quot;fake&quot; (for VMs) MAC address.
And I don't know how the iBFT interacts (or is supposed to) with a DHCP
server.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Michael Howard &lt;[email protected]&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Julian Satran/Haifa/IBM@IBMIL</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">[email protected], Sivan Tal/Haifa/IBM@IBMIL</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">09/22/2008 11:42</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [Ips] no DHCP-assigned InitiatorName</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
<br>
Julian Satran wrote:<br>
&gt; Michael,<br>
&gt; <br>
&gt; I think that some of the OSs have the initiator name wired into the
<br>
&gt; image and boot providers will have to set this name.<br>
<br>
I do not understand what you are trying to say.<br>
<br>
On x86 architectures the iBFT (iSCSI Boot Firmware Table) is used to <br>
pass iSCSI boot parameters to the OS. The iSCSI boot parameters include
<br>
target information and InitiatorName ... so that a new session <br>
(attaching to the same LUN) can be established by the OS driver.<br>
<br>
&gt; I am not sure how what exactly is required for each version.<br>
&gt; The boot RFC defines where the image comes from but very little else.<br>
<br>
I am arguing that &quot;very little else&quot; is actually too little ;)<br>
<br>
&gt; Sivan may give you a pointer to CbCS.<br>
<br>
OK<br>
<br>
<br>
Michael<br>
</font></tt><br>
<br>
<br>
--=_alternative 005F3552852574CC_=--

--===============1277100288==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ips mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ips

--===============1277100288==--