need to supernet the datacenter network PetaSAN resides on
R3LZX
50 Posts
March 4, 2021, 5:11 pmQuote from R3LZX on March 4, 2021, 5:11 pmwe currently have a 10.10.21.xx / 24 in the datacenter and need to supernet it by changing the subnet from 255.255.255.0 to 255.255.252.0 and going to a 10.10.24.xxxwill the Ceph cluster just come back up and populate after we change the ips? I have the following steps outlined
three server cluster residing on latest build of petasan, two 10gig ethernet being used each server
shutdown and disconnect all iscsi
log into console and manually change all ips
reboot all servers and change iscsi paths to new ips
I am going to follow these instructions and if there is anything you want to add let me know, again thank you for all you do here, this is an amazing storage environment
edit:
cluster_info.json
node_info.json
/etc/network/interfaces
To change /etc/hosts, you need to work through more steps as this file is synced automatically by a background sync service
# stop auto sync service
systemctl stop petasan-file-sync
# manual change hosts file
nano /etc/hosts
# sync the hosts file to all nodes:
/opt/petasan/scripts/util/sync_file.py /etc/hosts
# restart the sync service on current node
systemctl start petasan-file-sync
we currently have a 10.10.21.xx / 24 in the datacenter and need to supernet it by changing the subnet from 255.255.255.0 to 255.255.252.0 and going to a 10.10.24.xxxwill the Ceph cluster just come back up and populate after we change the ips? I have the following steps outlined
three server cluster residing on latest build of petasan, two 10gig ethernet being used each server
shutdown and disconnect all iscsi
log into console and manually change all ips
reboot all servers and change iscsi paths to new ips
I am going to follow these instructions and if there is anything you want to add let me know, again thank you for all you do here, this is an amazing storage environment
edit:
cluster_info.json
node_info.json
/etc/network/interfaces
To change /etc/hosts, you need to work through more steps as this file is synced automatically by a background sync service
# stop auto sync service
systemctl stop petasan-file-sync
# manual change hosts file
nano /etc/hosts
# sync the hosts file to all nodes:
/opt/petasan/scripts/util/sync_file.py /etc/hosts
# restart the sync service on current node
systemctl start petasan-file-sync
Last edited on March 4, 2021, 5:17 pm by R3LZX · #1
admin
2,930 Posts
March 4, 2021, 6:48 pmQuote from admin on March 4, 2021, 6:48 pmagain thank you for all you do here, this is an amazing storage environment
Thank you, this is nice to hear 🙂
But unfortunately changing the backend ip is not straightforward. this specific ip is used by Ceph mons, Gluster and Consul services and changing their ips is not a simple operations, you may read their docs on how to do it. You could also buy support from us if you wish and we would take care of this. Changing other ips, subnets, interfaces, bonds...etc should not be a problem.
again thank you for all you do here, this is an amazing storage environment
Thank you, this is nice to hear 🙂
But unfortunately changing the backend ip is not straightforward. this specific ip is used by Ceph mons, Gluster and Consul services and changing their ips is not a simple operations, you may read their docs on how to do it. You could also buy support from us if you wish and we would take care of this. Changing other ips, subnets, interfaces, bonds...etc should not be a problem.
Last edited on March 4, 2021, 6:49 pm by admin · #2
R3LZX
50 Posts
March 5, 2021, 1:00 amQuote from R3LZX on March 5, 2021, 1:00 amok thank you I will take this into consideration
ok thank you I will take this into consideration
need to supernet the datacenter network PetaSAN resides on
R3LZX
50 Posts
Quote from R3LZX on March 4, 2021, 5:11 pmwe currently have a 10.10.21.xx / 24 in the datacenter and need to supernet it by changing the subnet from 255.255.255.0 to 255.255.252.0 and going to a 10.10.24.xxxwill the Ceph cluster just come back up and populate after we change the ips? I have the following steps outlined
three server cluster residing on latest build of petasan, two 10gig ethernet being used each server
shutdown and disconnect all iscsi
log into console and manually change all ips
reboot all servers and change iscsi paths to new ips
I am going to follow these instructions and if there is anything you want to add let me know, again thank you for all you do here, this is an amazing storage environment
edit:
cluster_info.json
node_info.json
/etc/network/interfaces
To change /etc/hosts, you need to work through more steps as this file is synced automatically by a background sync service
# stop auto sync service
systemctl stop petasan-file-sync
# manual change hosts file
nano /etc/hosts
# sync the hosts file to all nodes:
/opt/petasan/scripts/util/sync_file.py /etc/hosts
# restart the sync service on current node
systemctl start petasan-file-sync
we currently have a 10.10.21.xx / 24 in the datacenter and need to supernet it by changing the subnet from 255.255.255.0 to 255.255.252.0 and going to a 10.10.24.xxxwill the Ceph cluster just come back up and populate after we change the ips? I have the following steps outlined
three server cluster residing on latest build of petasan, two 10gig ethernet being used each server
shutdown and disconnect all iscsi
log into console and manually change all ips
reboot all servers and change iscsi paths to new ips
I am going to follow these instructions and if there is anything you want to add let me know, again thank you for all you do here, this is an amazing storage environment
edit:
cluster_info.json
node_info.json
/etc/network/interfaces
To change /etc/hosts, you need to work through more steps as this file is synced automatically by a background sync service
# stop auto sync service
systemctl stop petasan-file-sync
# manual change hosts file
nano /etc/hosts
# sync the hosts file to all nodes:
/opt/petasan/scripts/util/sync_file.py /etc/hosts
# restart the sync service on current node
systemctl start petasan-file-sync
admin
2,930 Posts
Quote from admin on March 4, 2021, 6:48 pmagain thank you for all you do here, this is an amazing storage environment
Thank you, this is nice to hear 🙂
But unfortunately changing the backend ip is not straightforward. this specific ip is used by Ceph mons, Gluster and Consul services and changing their ips is not a simple operations, you may read their docs on how to do it. You could also buy support from us if you wish and we would take care of this. Changing other ips, subnets, interfaces, bonds...etc should not be a problem.
again thank you for all you do here, this is an amazing storage environment
Thank you, this is nice to hear 🙂
But unfortunately changing the backend ip is not straightforward. this specific ip is used by Ceph mons, Gluster and Consul services and changing their ips is not a simple operations, you may read their docs on how to do it. You could also buy support from us if you wish and we would take care of this. Changing other ips, subnets, interfaces, bonds...etc should not be a problem.
R3LZX
50 Posts
Quote from R3LZX on March 5, 2021, 1:00 amok thank you I will take this into consideration
ok thank you I will take this into consideration