user1999: I believe we are missing something.  Earlier I asked a question on how to reregister the stake pool from the new hosts.  However, apparently I had not asked the entire question - which is, how do you go about moving the node?  As in, what are the steps?  The documentation on this has been pretty hard to find.  What I did was to set up the node on the new hosts, transfer the keys, and then re-register the stake pool using the SPOS scripts.  But, the IP addresses of the relays aren't being updated on the net - so how do I update the topology file?  I found a Topology Updater script, but I can't just download and run it - it appears that a set of very specific prerequisites needs to be set up, and I don't see where that is documented.  So how exactly do I take my updated topology file and submit it to the network to supersede the old one?

user382: In general, there's nothing in the protocol itself that cares where your node made blocks, but here's some best practices on what you would do:

Create your new relays in the new hosting center
Setup bi-directional connections between your old/new relays in your topology files
Notify any pools you're pairing with of your new relays so they can add them to their topology files as well
Re-register the new relays for your pool so IOHK and other pools getting information from db-sync to generate their topology files can find your relays
Sync a new "relay" against your new relays in your new hosting center. This will eventually become your block producing node
Identify a time when your node will not produce a block that's a good maintenance window (ideally a few hours in case anything goes wrong)
cleanly stop both the old block producing node and the new one (that's currently a relay) with a SIGINT signal so the database is cleanly shutdown.
(optional but good practice) generate a new KES key an opcert
restart your new block producing node with the VRF skey and new KES/opcert.
Ensure your relays have adequate incoming relay connections from outside prior to shutting down your old relays.
remove old relays from your new relay topology and restart them


1999: <p>I believe we are missing something.  Earlier I <a href="https://cardano.stackexchange.com/questions/6989/how-to-move-cardano-node-stake-pool-to-new-ip-address">asked a question</a> on how to reregister the stake pool from the new hosts.  However, apparently I had not asked the entire question - which is, how do you go about moving the node?  As in, what are the steps?  The documentation on this has been pretty hard to find.  What I did was to set up the node on the new hosts, transfer the keys, and then re-register the stake pool using the SPOS scripts.  But, the IP addresses of the relays aren't being updated on the net - so how do I update the topology file?  I found a <a href="https://cardano-community.github.io/guild-operators/Scripts/topologyupdater/" rel="nofollow noreferrer">Topology Updater script</a>, but I can't just download and run it - it appears that a set of very specific prerequisites needs to be set up, and I don't see where that is documented.  So how exactly do I take my updated topology file and submit it to the network to supersede the old one?</p>
 382: <p>In general, there's nothing in the protocol itself that cares where your node made blocks, but here's some best practices on what you would do:</p>
<ol>
<li>Create your new relays in the new hosting center</li>
<li>Setup bi-directional connections between your old/new relays in your topology files</li>
<li>Notify any pools you're pairing with of your new relays so they can add them to their topology files as well</li>
<li>Re-register the new relays for your pool so IOHK and other pools getting information from db-sync to generate their topology files can find your relays</li>
<li>Sync a new &quot;relay&quot; against your new relays in your new hosting center. This will eventually become your block producing node</li>
<li>Identify a time when your node will not produce a block that's a good maintenance window (ideally a few hours in case anything goes wrong)</li>
<li>cleanly stop both the old block producing node and the new one (that's currently a relay) with a SIGINT signal so the database is cleanly shutdown.</li>
<li>(<em>optional</em> but good practice) generate a new KES key an opcert</li>
<li>restart your new block producing node with the VRF skey and new KES/opcert.</li>
<li>Ensure your relays have adequate incoming relay connections from outside prior to shutting down your old relays.</li>
<li>remove old relays from your new relay topology and restart them</li>
</ol>
