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 <michael.howard@...>
|
| To:
| Julian Satran/Haifa/IBM@IBMIL
|
| Cc:
| ips@..., 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
_______________________________________________
Ips mailing list
Ips@...
https://www.ietf.org/mailman/listinfo/ips
