From 18ddf50b4c5d6fa8c4ad5e1b3d4e37bf5dc4f372 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Sun, 20 Mar 2016 15:43:55 +0000 Subject: [PATCH] cosmetic --- site/ipam/stop-remove-peers-ipam.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/site/ipam/stop-remove-peers-ipam.md b/site/ipam/stop-remove-peers-ipam.md index 433b8148..a8bc4e9e 100644 --- a/site/ipam/stop-remove-peers-ipam.md +++ b/site/ipam/stop-remove-peers-ipam.md @@ -6,19 +6,20 @@ layout: 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. +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. +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 +For failed peers, the `weave rmpeer` command can be invoked 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. +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: @@ -37,4 +38,3 @@ status`. * [Address Allocation with IP Address Management (IPAM)](/site/ipam/overview-init-ipam.md) * [Automatic Allocation Across Multiple Subnets](/site/ipam/allocation-multi-ipam.md) * [Isolating Applications on a Weave Network](/site/using-weave/isolating-applications.md) -