From f5f9bab77c74e3a9e67a8b95f5602e6f17b036d0 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Thu, 14 Dec 2017 10:17:40 +0000 Subject: [PATCH] Add meaning of 'active' in 'weave status ipam' --- site/tasks/ipam/troubleshooting-ipam.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/site/tasks/ipam/troubleshooting-ipam.md b/site/tasks/ipam/troubleshooting-ipam.md index 34f46277..bddffb53 100644 --- a/site/tasks/ipam/troubleshooting-ipam.md +++ b/site/tasks/ipam/troubleshooting-ipam.md @@ -50,7 +50,7 @@ peers and their reachability can be obtained with ``` $ weave status ipam -00:00:00:00:00:01(one) 349526 IPs (33.3% of total) +00:00:00:00:00:01(one) 349526 IPs (33.3% of total) (2 active) 00:00:00:00:00:02(two) 349525 IPs (33.3% of total) 00:00:00:00:00:03(three) 349525 IPs (33.3% of total) - unreachable! ``` @@ -59,6 +59,8 @@ Columns are as follows: * Peer Name and Nickname * Absolute quantity/percentage of allocation range managed by peer +* Active - number of IP addresses in use on that peer - this is only + available for the peer where you run the status command. * Indication of unreachability. This means that the peer is not visible (directly or indirectly) to the peer on which `weave status ipam` was run; whilst this could be a transient condition due to a