Hello all: Here is the issue which requires clarification. Issue Synopsis: When there are more than one iSCSI target configured and Ibft table published with the connected and aborted attempt details, all the targets are not seen in ESXi and SLES OS. But in Windows it can see the targets connected. Use case: Target 1: IP : 192.xx.xx.31 Target 2 : IP : 192.xx.xx.1 NIC 1 configured with attempts Target 1 & Target 2 NIC 2 configured with attempts Target 1 Connection
Login Ibft Block Device in UEFI Shell SLES / Esx OS Windows NIC1 Target1 Success Published Mounted Target Seen NIC1 Target2 Success Published Mounted Target Seen NIC1 Target1 NIC1 Target2 NIC2 Target1 Individual Login success Published for all attempts (3) NIC1 Target 1 NIC2 Target 1 None Seen NIC1 Target 1 NIC2 Target 1 When the attempts which are login success but Aborted by ISCSI Driver are present in ibft table SLES and ESX not able to see the targets during Installation. If the ISCSI Driver not adding the ibft entry for the aborted attempts then the targets are seen in Esx and SLES. So it requires clarification that If the driver need to SKIP adding the aborted attempt entry to ibft or its OS responsibility to handle the invalid entries in ibft. -Siva _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
