
UNSOLVED
iSM in netns
Greetings. I am looking forward running iSM on my Poweredge R640. I notice that iSM by default, will create a 169.254.0.2/16 "idrac" interface. This is really not ideal because the 169.254.0.0/16 range conflicts with my other interfaces and really, there is no IPv4 range on these hosts that are guaranteed not to conflict (so changing the IP on the iDRAC is not a solution)
I notice that I can just
systemctl stop dcismeng
then move the idrac interface in a dedicated netns and run the daemon there:
ip netns add drac
ip link set idrac netns drac
ip netns exec drac ip address add 169.254.0.2/30 dev idrac
ip netns exec drac ip link set idrac up
ip netns exec drac /opt/dell/srvadmin/iSM/sbin/dsm_ism_srvmgrd
which seems to work (well the network interfaces of the server are not displayed anymore in the iDRAC, but at least there is something working. My goal is primarily to get hostname and osversion in there, lifecycle logs on the OS would be great too!)
I see other folks (https://hub.docker.com/r/jdelaros1/ism/) tried to containerize iSM - but the networking part, the one that really blocks me, was never tackled it seems.
Would there be a way to get iSM work in a dedicated network namespace?
Responses (0)
Solutions (0)
