[gpfsug-discuss] [External] DSS-G sharing IPMI network

Ryan Novosielski novosirj at rutgers.edu
Wed Jun 24 17:37:11 BST 2026


On Jun 24, 2026, at 06:25, Jonathan Buzzard via gpfsug-discuss <gpfsug-discuss at gpfsug.org> wrote:

On 19/06/2026 18:23, Nicolas CALIMET wrote:
Hi,
The recommendation is likely originating from environments where
switch ports and cabling may be too constrained if using the
dedicated LOM/OCP port. There is also a correlation with setting up
the Confluent environment.

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.

Are we an outlier having a dedicated management network? I would have thought that was the norm/best practice?

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’s pretty good. We do use the dedicated ports for our PHI/secure system, but I think if we were speccing it today, we’d have used VLANs instead. Dedicated doesn’t necessarily mean physical.

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.


So to answer your question - I'm assuming you're dealing with a V3
server (SR655 V3), which indeed may have the dedicated port enabled
by default:
$ nodeconfig dss45 -c IMM.SharedNicMode dss45: IMM.SharedNicMode:
Dedicated (Default: Dedicated)
$ nodeconfig dss45 IMM.SharedNicMode=jnk dss45: jnk is not a valid
value for IMM.SharedNicMode
(Shared:nic0,Shared,Dedicated,Shared:nic3,Shared:nic4,Shared:nic5,Shared:nic6,Shared:nic7,Shared:nic8)
So if you want to stick to the recommendation, "nodeconfig <nodes>
IMM.SharedNicMode=Shared" should be what you're looking for if you
pick up the correct physical OCP port as documented.

Is there a support issue with just staying with the dedicated NIC for the XCC connection?

I was about to start the migration off our old DSS-G but if I need to rejig this then now is the time.

I believe the most you’re likely to run into is the scripts expecting a “shared” connection. I can’t recall as to whether they will try to enforce it these days. I think no?

--
#BlackLivesMatter
____
|| \\UTGERS,     |---------------------------*O*---------------------------
||_// the State  |     Ryan Novosielski (he/him) - novosirj at rutgers.edu
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
||  \\    of NJ  |      Office of Advanced Research Computing - Newark
     `'

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20260624/34030257/attachment-0001.html>


More information about the gpfsug-discuss mailing list