<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="RU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<div>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Hi Sunitha!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">>> I also believe that in production environments the BMC shall not be connected to the same network segment using multiple interfaces.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">>> If that is needed for failover, then we should think about adding the bridging and bonding support instead</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">> Do you have more details on this please?
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Sure. Honestly, I haven’t dealt with either technique for quite many years now, and when I had, my experience was far from being vast, but I still remember those things do exist.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">So here are some resources that I found that look relevant:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://developers.redhat.com/articles/2022/04/06/introduction-linux-bridging-commands-and-features">https://developers.redhat.com/articles/2022/04/06/introduction-linux-bridging-commands-and-features</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="https://www.learnitguide.net/2015/07/what-is-bonding-how-to-configure.html">https://www.learnitguide.net/2015/07/what-is-bonding-how-to-configure.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">>> P.S. I also believe that it is VERY wrong that we still allow setting per-interface gateways as BMC is not a router device and doesn’t (and shouldn’t) allow for configuring policy
routing or any routing whatsoever.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">> I believe this was done purposefully some years ago. </span>
@Ravi please share the details if you have the history.<o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I you can provide any rationale for that, I’d be grateful. We’ve been having all sorts of trouble due to that for quite a long time.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">WBR, Alexander.<o:p></o:p></span></p>
</div>
</div>
</body>
</html>