Files
weave/site/ipam/troubleshooting-ipam.md
T
Matthias Radestock 3453972ac4 banish ~~~bash
Just use indenting, which is much easier on the eye.
2016-03-29 10:30:51 +01:00

1.5 KiB

title, layout
title layout
Troubleshooting the IP Allocator default

The command

weave status

reports on the current status of the weave router and IP allocator:

...
       Service: ipam
        Status: awaiting consensus (quorum: 2, known: 0)
         Range: 10.32.0.0-10.47.255.255
 DefaultSubnet: 10.32.0.0/12
...

The first section covers the router; see the troubleshooting guide for full details.

The 'Service: ipam' section displays the consensus state as well as the total allocation range and default subnet. Columns are as follows:

  • 'Status' - allocator state
    • 'idle' - no allocation requests or claims have been made yet; consensus is deferred until then
    • 'awaiting consensus' - an attempt to achieve consensus is ongoing, triggered by an allocation or claim request; allocations will block. This state persists until a quorum of peers are able to communicate amongst themselves successfully
    • 'ready' - consensus achieved; allocations proceed normally
    • 'waiting for IP range grant from peers' - peer has exhausted its agreed portion of the range and is waiting to be granted some more
    • 'all IP ranges owned by unreachable peers' - peer has exhausted its agreed portion of the range but cannot reach anyone to ask for more
  • 'Range' - total allocation range set by --ipalloc-range
  • 'DefaultSubnet' - default subnet set by --ipalloc-default-subnet