Hi all,
I tried various combination of destroying the ssvm first, console proxy
first, also testing the behaviour of the global configs, namely
"system.vm.public.ip.reservation.mode.strictness" and
"systemvm.release.control.ip.on.stop". None of these works; the only
workaround in my case was to update the nic table and edit the IP of the
secondary storage vm. After destroying the system vm, the problem was
solved. From the black box point of view, it seems like there is no
validation if the public IP is already reserved?
Mevludin
Am Freitag, 17. Oktober 2025 um 11:14:42 MESZ hat Prashanth Reddy
<[email protected]> Folgendes geschrieben:
Hi Mevludin,
Based on the global setting you mentioned these are systemVM's right?
If yes, try destroying the systemVM's , new ones will be created
automatically in few mins. Once they are up check if you still have the
issue.
Thanks
Prashanth
________________________________
From: Mevludin Blazevic <[email protected]>
Sent: Friday, October 17, 2025 9:08 AM
To: [email protected] <[email protected]>
Subject: Console Proxy and Secondary Storage System VM have the same
public IP
Dear all,
after an energy outage I am witnessing a strange behaviour: After both
vms could not start because of (what I think) the
"system.vm.management.ip.reservation.mode.strictness" flag was set on
true and after setting this to false, the vms were able to start,
However, now both VMs have exactly the same public IP. How to fix that?
Best, Mevludin
