Files
weave/site/ipam/stop-remove-peers-ipam.md
T
2016-03-08 12:14:27 -06:00

1.7 KiB

title, layout
title layout
Starting, Stopping and Removing Peers default

You may wish to weave stop and re-launch to change some config or to upgrade to a new version. Provided that the underlying protocol hasn't changed, Weave Net picks up where it left off and learns from peers in the network which address ranges it was previously using.

If, however, you run weave reset this removes the peer from the network so if Weave Net is run again on that node it will start from scratch.

For failed peers, the weave rmpeer command can be used to permanently remove the ranges allocated to said peer. This allows other peers to allocate IPs in the ranges previously owned by the removed peer, and as such should be used with extreme caution - if the removed peer had transferred some range of IP addresses to another peer but this is not known to the whole network, or if it later rejoins the Weave network, the same IP address may be allocated twice.

Assume you had started the three peers in the example earlier, and then host3 caught fire, you can go to one of the other hosts and run:

host1$ weave rmpeer host3

Weave Net takes all the IP address ranges owned by host3 and transfers them to be owned by host1. The name "host3" is resolved via the 'nickname' feature of Weave Net, which defaults to the local host name. Alternatively, you can supply a peer name as shown in weave status.

See Also