<html aria-label="message body">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>On Jun 24, 2026, at 06:25, Jonathan Buzzard via gpfsug-discuss <gpfsug-discuss@gpfsug.org> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>On 19/06/2026 18:23, Nicolas CALIMET wrote:<br>
<blockquote type="cite">Hi,<br>
The recommendation is likely originating from environments where<br>
switch ports and cabling may be too constrained if using the<br>
dedicated LOM/OCP port. There is also a correlation with setting up<br>
the Confluent environment.<br>
</blockquote>
<br>
I just don't get what that correlation might be. Noting I having setup the servers with dedicated connections for the XCC using confluent without issue. I guess that is my fault for presuming that because they came configured in dedicated mode that is what
I should be using.<br>
<br>
Are we an outlier having a dedicated management network? I would have thought that was the norm/best practice?<br>
</div>
</div>
</blockquote>
<div><br>
</div>
We use shared networking for everything. Less of a hassle overall, less money spent in switches, etc. I know the support was at one time a bit shoddy for VLANs on the BMCs, but these days I think it\u2019s pretty good. We do use the dedicated ports for our PHI/secure
system, but I think if we were speccing it today, we\u2019d have used VLANs instead. Dedicated doesn\u2019t necessarily mean physical.</div>
<div><br>
</div>
<div>This has also been a hiccup in our setup, just because the delivery default is now different. Lenovo Confluent actually has a script called configbmc that you can use with genesis, and so we set up the machines and boot them, genesis fixes the setting,
and we continue on.</div>
<div><br>
<blockquote type="cite">
<div>
<div><br>
<blockquote type="cite">So to answer your question - I'm assuming you're dealing with a V3<br>
server (SR655 V3), which indeed may have the dedicated port enabled<br>
by default:<br>
$ nodeconfig dss45 -c IMM.SharedNicMode dss45: IMM.SharedNicMode:<br>
Dedicated (Default: Dedicated)<br>
$ nodeconfig dss45 IMM.SharedNicMode=jnk dss45: jnk is not a valid<br>
value for IMM.SharedNicMode<br>
(Shared:nic0,Shared,Dedicated,Shared:nic3,Shared:nic4,Shared:nic5,Shared:nic6,Shared:nic7,Shared:nic8)<br>
So if you want to stick to the recommendation, "nodeconfig <nodes><br>
IMM.SharedNicMode=Shared" should be what you're looking for if you<br>
pick up the correct physical OCP port as documented.<br>
</blockquote>
<br>
Is there a support issue with just staying with the dedicated NIC for the XCC connection?<br>
<br>
I was about to start the migration off our old DSS-G but if I need to rejig this then now is the time.<br>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
I believe the most you\u2019re likely to run into is the scripts expecting a \u201cshared\u201d connection. I can\u2019t recall as to whether they will try to enforce it these days. I
<i>think</i> no?
<div><br>
</div>
<div>
<div>
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
-- <br>
#BlackLivesMatter</div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
____<br>
|| \\UTGERS, |---------------------------*O*---------------------------<br>
||_// the State<span class="Apple-tab-span" style="white-space: pre;"> </span> | Ryan Novosielski (he/him) - novosirj@rutgers.edu<br>
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus<br>
|| \\ of NJ<span class="Apple-tab-span" style="white-space: pre;"> </span> | Office of Advanced Research Computing - Newark<br>
`'</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div>
<blockquote type="cite"></blockquote>
</div>
</div>
</body>
</html>