<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div id="yiv1484919732"><table id="yiv1484919732bodyDrftID" class="yiv1484919732" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td id="yiv1484919732drftMsgContent" style="font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit; font-family: arial; font-size: 10pt;">Hello,<br><br>I need to explain the San boot sequence(procedure) & compare it to the boot from a local HDD.<br><br>with a local HDD it goes this way: Power Good > POST > secondary BIOSs >OS boot from HDD.<br><br>With a local (physical) hard drive connected to the HDD controller (ATA/SCSI) it's the BIOS that accesses the HDD before the OS's HDD driver is loaded, but how about AoE SAN boot ?<br><br>I know that before gPXE quits it registers the SAN target (AoE or iSCSI) as a BIOS drive, what does that
really mean ? How does the BIOS know how (the protocol) to access the BIOS drive over AoE ? Where is the driver responsible for this step ?<br><br>I might be completely wrong or missing an important part of the process so, please, be kind & explain me what is happening in the background.<br><br>Thanks !<br>TheMadOne.<br><br></td></tr></tbody></table></div></td></tr></table><br>