From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on071b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe44::71b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0A3B91A1DF6 for ; Tue, 23 Aug 2016 06:30:57 -0700 (PDT) Received: from DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.COM (10.162.192.143) by DF4PR84MB0044.NAMPRD84.PROD.OUTLOOK.COM (10.162.192.146) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.587.9; Tue, 23 Aug 2016 13:30:54 +0000 Received: from DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.COM ([10.162.192.143]) by DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.COM ([10.162.192.143]) with mapi id 15.01.0557.027; Tue, 23 Aug 2016 13:30:54 +0000 From: "Subramanian, Sriram (EG Servers Platform SW)" To: Ye Ting , Fu Siyuan , Wu Jiaxin CC: "Zimmer, Vincent" , "Li, Ruth" , "edk2-devel@lists.01.org" Thread-Topic: Question on iBFT for iSCSI Thread-Index: AdH9QR6zDnA28uVXTFKT5bgxfDPeIA== Date: Tue, 23 Aug 2016 13:30:54 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=sriram-s@hpe.com; x-originating-ip: [49.207.52.144] x-ms-office365-filtering-correlation-id: 7f3ddf61-98c8-4a14-83a4-08d3cb59b572 x-microsoft-exchange-diagnostics: 1; DF4PR84MB0044; 6:7IyRZton6JTIMGw73vE0pdogQgAt3zgfS8/4lIm6zQ0kZ5akIZYHJUslMg6C9AhPVAmTAjegsMlLDA/iIPhLT8PrBE+s7xSYBkmSo6x6K2Amt3TZoPoZBlWyBxSiP+0cdu3+0G2o9UL33G69xcixFz6dNrgJ4dkndncAJmlpAyaS11AzPahyLTEYYAJef0tS4xAKgbj+P3hLbyRroDj1DjnFSw3fB/1noqnteejPqx635Sw8ETKUwll0tDqM17dlQNFG6nbZM0h4CfHwEN4YV2R/+rZEIW4unRg9jtdpyzyG8MzQaAkwWCpOsW1AiDknyJEQKuey0PjAs2wKJAo3aA==; 5:q3xgQYJDeMbsP9/y6aVLTKK5RTXbd8QGop3mkyulu+Wv/QeWLEUPVxk4f4dr61erVd1EBbLJ6nLxSHTGQReixwfWcXZdIpCayQE26k65Sf5etJGfWyxhiDOHpBzfq6ffZcqkIMr+VunXW6dieECa1g==; 24:hMJwQOSrVvp5l27aPcRpMYOzdht38yDW+2owPpAPFoXoA5Ql9apa1K8FnP8sVncih5YAIdorerq2MUtSBFvBfuBkpgsyl3vMi0ZVNIAZFtc=; 7:BQCADQu0CX1aH3yNZU/2PedU1Pq7qzi4QTW2r6/EnON/SpWOzDZrxgNfdICRjoDzqB0EVRCEqkDxkHloYlZBbCJnAjDokcxGV8Yz4+j5SnAUOeowhRhd9A2C87TuveIdG9YPwPMRwYtBHykPF8urfB4SuXzGndUeSubGRKaBsH2GUCn8ZWkrVo3jHkvpkaaj6s3XktcBfX3A0jUxbtNKLebvQIqlppGb7d5zfENPSmpsgsiJSjKA1R7ksd5GwWYS x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DF4PR84MB0044; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:DF4PR84MB0044; BCL:0; PCL:0; RULEID:; SRVR:DF4PR84MB0044; x-forefront-prvs: 004395A01C x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(189002)(52054003)(77096005)(87936001)(9686002)(86362001)(5001770100001)(66066001)(97736004)(54356999)(50986999)(105586002)(229853001)(101416001)(99286002)(106356001)(4326007)(3280700002)(68736007)(122556002)(2906002)(2900100001)(10400500002)(6116002)(3660700001)(102836003)(3846002)(586003)(11100500001)(92566002)(33656002)(7736002)(7696003)(305945005)(74316002)(8676002)(189998001)(5002640100001)(7846002)(5660300001)(8936002)(81166006)(81156014); DIR:OUT; SFP:1102; SCL:1; SRVR:DF4PR84MB0044; H:DF4PR84MB0041.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: hpe.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hpe.com X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2016 13:30:54.3878 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-Transport-CrossTenantHeadersStamped: DF4PR84MB0044 Subject: Question on iBFT for iSCSI X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2016 13:30:57 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, The IScsiDxe implementation in EDK2 publishes the iBFT with the target IP a= ddress to which it connected to, and not the configured IP. These IPs will = be the same if there is no iSCSI redirection. However, if the configured ta= rget redirects the initiator to another target (as part of iSCSI Login resp= onse), the Session data is updated to the new target IP. To my knowledge, there doesn't look to be any standard/specification govern= ing this, so I believe this is open to debate.=20 The reason for this question is that the configured IP address may be that = of a server that's doing the redirect to achieve load balancing or high ava= ilability in the cluster. Now if we set the Target IP address in the iBFT to the final IP to which we= connected, we lose the redirection capability in case the target at the fi= nal IP goes down, and the OS wants to re-establish the connection.=20 If we published the original configured IP, then the OS will attempt to rec= onnect to the configured IP in the iBFT, and will get redirected to another= target which is up. So do you think it makes sense to publish the original configured static IP= (or the original IP provided via DHCP) instead of the redirected IP? What = are your thoughts on this? Thanks, Sriram.