NVME-oF TCP - management nic lost on reboot
Posted: Wed Dec 10, 2025 8:53 pm
We have two Dell R660xs servers directly running the NVME-of TCP Technical preview, now v1.7.794.7576. That is, there is no virtualization between Starwind and the metal.
When either starwind system is rebooted, the designated management NIC changes. This affects the Starwind management ip and the ability of the two appliances to talk to each other.
Starwind does load after a reboot, but the local console screen shows the wrong management IP on the screen.
The Starwind has defaulted to a different nic, in this case, eno12399np0. This nic is a data "role" nic port, not management, and the physical port is connected directly to a compute host. We can't use that nic port as management without moving things around, which we would prefer not to do.
The workaround right now is to use the console to set the eno8303 nic as the management port.
We would like to reboot and still have a web/ssh management option, and to not make the appliances show as "offline" on the other node.
-Jeff
When either starwind system is rebooted, the designated management NIC changes. This affects the Starwind management ip and the ability of the two appliances to talk to each other.
Starwind does load after a reboot, but the local console screen shows the wrong management IP on the screen.
The Starwind has defaulted to a different nic, in this case, eno12399np0. This nic is a data "role" nic port, not management, and the physical port is connected directly to a compute host. We can't use that nic port as management without moving things around, which we would prefer not to do.
The workaround right now is to use the console to set the eno8303 nic as the management port.
We would like to reboot and still have a web/ssh management option, and to not make the appliances show as "offline" on the other node.
-Jeff