All iSCSI IPs go down after removing 1 iSCSI target
sniffus
20 Posts
January 16, 2018, 3:08 pmQuote from sniffus on January 16, 2018, 3:08 pmGood <time_of_day>
In my 1.4 Lab, I was cleaning up some iSCSI targets I no longer needed. Suddenly, on my Windows 2016, Hyper-V, VM 2012R2 went down... Mystery... Nah... iSCSI target disconnected. Cannot be pinged.
I tried all the other targets, same. I had to stop and start all of them to be available again.
This is bad. I need to be able to remove a target while the rest of the system goes chugging along.
Are you aware of this? Is there a magic fix known on 1.5? Am I alone in a dream world and it's a problem on my side ?
Thank you kindly one and all, Love the product !
Marc
Senior IT Dude @ work.
Good <time_of_day>
In my 1.4 Lab, I was cleaning up some iSCSI targets I no longer needed. Suddenly, on my Windows 2016, Hyper-V, VM 2012R2 went down... Mystery... Nah... iSCSI target disconnected. Cannot be pinged.
I tried all the other targets, same. I had to stop and start all of them to be available again.
This is bad. I need to be able to remove a target while the rest of the system goes chugging along.
Are you aware of this? Is there a magic fix known on 1.5? Am I alone in a dream world and it's a problem on my side ?
Thank you kindly one and all, Love the product !
Marc
Senior IT Dude @ work.
admin
2,930 Posts
January 16, 2018, 5:17 pmQuote from admin on January 16, 2018, 5:17 pmHi Marc,
We did hit this problem and is fixed in version 1.5. When removing your first target, it will also remove secondary ips on the subnet.
To fix: add the following line to /etc/sysctl.conf on every node:
ipv4.conf.all.promote_secondaries=1
then run
sysctl --system
An upgrade to 1.5 will also add this line to your existing installation.
Glad you like the product. /Hatem.
Hi Marc,
We did hit this problem and is fixed in version 1.5. When removing your first target, it will also remove secondary ips on the subnet.
To fix: add the following line to /etc/sysctl.conf on every node:
ipv4.conf.all.promote_secondaries=1
then run
sysctl --system
An upgrade to 1.5 will also add this line to your existing installation.
Glad you like the product. /Hatem.
Last edited on January 16, 2018, 5:20 pm by admin · #2
sniffus
20 Posts
January 17, 2018, 2:08 pmQuote from sniffus on January 17, 2018, 2:08 pmI so love it when a question as a solution !!!
Doesn't happen often. 😉 yeah... I'm that good 😉
Thank you, our lab is going fairly well, other than crappy hardware issues. back to fight with management to get real hardware !
M.
I so love it when a question as a solution !!!
Doesn't happen often. 😉 yeah... I'm that good 😉
Thank you, our lab is going fairly well, other than crappy hardware issues. back to fight with management to get real hardware !
M.
All iSCSI IPs go down after removing 1 iSCSI target
sniffus
20 Posts
Quote from sniffus on January 16, 2018, 3:08 pmGood <time_of_day>
In my 1.4 Lab, I was cleaning up some iSCSI targets I no longer needed. Suddenly, on my Windows 2016, Hyper-V, VM 2012R2 went down... Mystery... Nah... iSCSI target disconnected. Cannot be pinged.
I tried all the other targets, same. I had to stop and start all of them to be available again.
This is bad. I need to be able to remove a target while the rest of the system goes chugging along.
Are you aware of this? Is there a magic fix known on 1.5? Am I alone in a dream world and it's a problem on my side ?
Thank you kindly one and all, Love the product !
Marc
Senior IT Dude @ work.
Good <time_of_day>
In my 1.4 Lab, I was cleaning up some iSCSI targets I no longer needed. Suddenly, on my Windows 2016, Hyper-V, VM 2012R2 went down... Mystery... Nah... iSCSI target disconnected. Cannot be pinged.
I tried all the other targets, same. I had to stop and start all of them to be available again.
This is bad. I need to be able to remove a target while the rest of the system goes chugging along.
Are you aware of this? Is there a magic fix known on 1.5? Am I alone in a dream world and it's a problem on my side ?
Thank you kindly one and all, Love the product !
Marc
Senior IT Dude @ work.
admin
2,930 Posts
Quote from admin on January 16, 2018, 5:17 pmHi Marc,
We did hit this problem and is fixed in version 1.5. When removing your first target, it will also remove secondary ips on the subnet.
To fix: add the following line to /etc/sysctl.conf on every node:
ipv4.conf.all.promote_secondaries=1
then run
sysctl --system
An upgrade to 1.5 will also add this line to your existing installation.
Glad you like the product. /Hatem.
Hi Marc,
We did hit this problem and is fixed in version 1.5. When removing your first target, it will also remove secondary ips on the subnet.
To fix: add the following line to /etc/sysctl.conf on every node:
ipv4.conf.all.promote_secondaries=1
then run
sysctl --system
An upgrade to 1.5 will also add this line to your existing installation.
Glad you like the product. /Hatem.
sniffus
20 Posts
Quote from sniffus on January 17, 2018, 2:08 pmI so love it when a question as a solution !!!
Doesn't happen often. 😉 yeah... I'm that good 😉
Thank you, our lab is going fairly well, other than crappy hardware issues. back to fight with management to get real hardware !
M.
I so love it when a question as a solution !!!
Doesn't happen often. 😉 yeah... I'm that good 😉
Thank you, our lab is going fairly well, other than crappy hardware issues. back to fight with management to get real hardware !
M.