General
attributes
|
failover-pair-name
|
The name of
the failover pair object used to manage this server.
|
current-time
|
Current
time on the server returning this object.
|
comm-state
|
None, OK,
or Interrupted.
|
smoothed-time-delta
|
The time
difference between the local server and the partner server. If the local server
time is ahead of the partner server time, the attribute value is positive. If
the local server time is behind the partner server time, the attribute value is
negative. If the servers are not communicating, the last known attribute value
is recorded.
|
maximum-client-lead-time
|
Current
maximum client lead time (MCLT) on this system.
|
sequence-number
|
Sequence
number unique across failover objects, if different from the sequence in the
lease, the lease is considered “not up to date” independent of the
sf-up-to-date lease flag.
|
load-balancing-backup-pct
|
The
current failover load balancing backup percentage. If the backup percentage is
zero, failover load balancing is not in use (disabled).
|
Local
server
information
|
our-ipaddr
|
IPv4
address of the interface to this server.
|
our-ip6address
|
IPv6
address of the interface to this server.
|
role
|
Failover
role of the server returning this object—None, Main, or Backup.
|
state
|
State of the local server—None, Startup, Normal, Communications- interrupted, Partner-down, Potential-conflict, Recover,
Paused, or Recover-done.
|
start-time-of-state
|
Time at
which the current failover state began.
|
start-of-comm-interrupted
|
Time at
which this partner most recently went into communications- interrupted state.
This is valid across reloads, while the start-time-of-state never has a time
earlier than the most recent server reload.
|
est-end-recover-time
|
Valid if
update-request-in-progress is not set to None. If it
appears, the time at which the server enters the recover- done state if the
update request outstanding is complete. If it does not appear, then the server
enters recover-done whenever update-request is completed.
|
use-other-available
|
If false
or unset, then this server cannot use other-available leases. If true, then the
server can use other-available leases. Valid at all times, but should only be
true if in partner-down state.
|
use-other-available-time
|
If, in
partner-down state, the
use-other-available is false or unset, the time when
use-other-available will go to true.
|
safe-period-remaining
|
Duration
in seconds remaining in safe-period. If not set to 0, then this server is
currently running down a safe period with respect to its partner.
|
load-balancing-local-hba
|
The
current hash bucket assignment of the local server, usually shown as a range of
the hash bucket numbers. (See RFC 3074.)
|
request-buffers-in-use
|
The
number of failover request buffers the DHCP server is using at the time the
statistics are calculated.
|
decaying-max-request-buffers-in-use
|
The
maximum number of failover request buffers that have recently been in use.
|
request-buffers-allocated
|
The
number of request buffers that the server has allocated to support the failover
capability.
|
connection-start-time
|
The time
at which the most recent connection started. This value is set whenever a
connection is started, and it not cleared when a connection ended.
|
connection-end-time
|
The time
at which the most recent connection ended. This value is set whenever a
connection is ended, and it not cleared when a new connection starts.
|
Partner
server
information
|
ipaddr
|
IP
address of the partner server.
|
ip6address
|
IPv6
address of the partner server.
|
partner-role
|
Failover
role of the partner of the server returning this object—None, Main, or Backup.
|
partner-state
|
Last known state which the partner end of the failover relationship is in—None, Startup, Normal, Communications-interrupted,
Partner-down, Potential-conflict, Recover, Paused, or Recover-done.
|
start-time-of-partner-state
|
Time at
which the partner current failover state began.
|
est-partner-end-recover- time
|
If the
partner-state is Recover, an estimated prediction of when
the partner will time out its MCLT and finish being in recover state.
|
last-comm-ok-time
|
Time at
which this server last found communications to be OK.
|
load-balancing-partner-
hba
|
The
current hash bucket assignment of the partner server, usually shown as a range
of the hash bucket numbers. (See RFC 3074.)
|
partner-vendor-major-
version
|
The
vendor ID major version from the partner server.
|
partner-vendor-minor-
version
|
The
vendor ID minor version from the partner server.
|
Update
requests
sent
to
partner
|
update-request- outstanding
|
If None
or unset, then the server does not have an update request queued for its
partner. If not set to None, then it does have an update request queued for its
failover partner. Valid values are None, Update, and Update-all.
|
update-request-start-time
|
Time at
which any
update-request-outstanding request was started.
|
update-request-done-time
|
Time at
which the last of any update request completed.
|
v6-update-response-in-progress
|
The type
and origin of the response.
|
v6-update-response-percent-complete
|
The
percent complete of the current IPv6 update response.
|
v6-update-response-start-time
|
The time
that the IPv6 update response mentioned in v6-update-response-in-progress was
started.
|
v6-update-response-done-time
|
The time
that the most recent IPv6 update response sent an update done to the partner
server.
|
Update
requests
processed
for
partner
|
update-response-in- progress
|
If this
server is processing an update response, gives information about the type and
origin of the response.
|
update-response-percent- complete
|
If
update-response-outstanding appears, the percent complete of
the current update response.
|
update-response-start- time
|
Time that
the update response mentioned in
update-response-in-progress was started.
|
update-response-done- time
|
Time that
the most recent update response sent an update done to the partner server.
|
Load
Balancing
Counters
|
load-balancing-processed-
requests
|
The
number of server processed requests, both IPv4 and IPv6, subject to load
balancing. This counter includes only the requests made after the latest
transition of server to NORMAL state.
|
load-balancing-dropped-
requests
|
The
number of server dropped requests, both IPv4 and IPv6, subject to load
balancing. This counter includes only the requests made after the latest
transition of server to NORMAL state.
|
load-balancing-processed-
total
|
The
number of server processed requests, both IPv4 and IPv6, subject to load
balancing. This counter includes the requests since this server was last
started or reloaded.
|
load-balancing-dropped-
total
|
The
number of server dropped requests, both IPv4 and IPv6, subject to load
balancing. This counter includes the requests since this server was last
started or reloaded.
|
Binding
Update
or
Ack
Counters
(this
connection)
|
binding-updates-sent
|
The
number of binding update (BNDUPD) messages sent to the failover partner.
|
binding-acks-received
|
The
number of binding acknowledgement (BNDACK) messages received from the failover
partner.
|
binding-updates-received
|
The
number of binding update (BNDUPD) messages received from the failover partner.
|
binding-acks-sent
|
The
number of binding acknowledgement (BNDACK) messages sent to the failover
partner.
|
v6-binding-updates-sent
|
The
number of IPv6 binding updates (BNDUPD6) messages received from the failover
partner since the start of the most recently established connection.
|
v6-binding-acks-received
|
The
number of IPv6 binding acknowledgements (BNDACK6) messages received from the
failover partner since the start of the most recently established connection.
|
v6-binding-updates-received
|
The
number of IPv6 binding updates (BNDUPD6) messages received from the failover
partner since the start of the most recently established connection.
|
v6-binding-acks-sent
|
The
number of IPv6 binding acknowledgements (BNDACK6) messages sent to the failover
partner since the start of the most recently established connection.
|
Binding Update/Ack Counters Totals
|
binding-updates-sent-total
|
The
number of IPv4 binding updates (BNDUPD) messages sent to the failover partner
since the most recent statistics reset.
|
binding-acks-received-total
|
The
number of IPv4 binding acknowledgements (BNDACK) messages received from the
failover partner since the most recent statistics reset.
|
binding-updates-received-total
|
The
number of IPv4 binding updates (BNDUPD) messages received from the failover
partner since the most recent statistics reset.
|
binding-acks-sent-total
|
The
number of IPv4 binding acknowledgements (BNDACK) messages sent to the failover
partner since the most recent statistics reset.
|
v6-binding-updates-sent-total
|
The
number of IPv6 binding updates (BNDUPD6) messages sent to the failover partner
since the most recent statistics reset.
|
v6-binding-acks-received-total
|
The
number of IPv6 binding acknowledgements (BNDACK6) messages received from the
failover partner since the most recent statistics reset.
|
v6-binding-updates-received-total
|
The
number of IPv6 binding updates (BNDUPD6) messages received from the failover
partner since the most recent statistics reset.
|
v6-binding-acks-sent-total
|
The
number of IPv6 binding acknowledgements (BNDACK6) messages sent to the failover
partner since the most recent statistics reset.
|
Flow Control Counters (this connection)
|
current-binding-updates-in-flight
|
The
current number of binding updates (both IPv4 and IPv6) that are currently
in-flight (sent).
|
current-binding-updates-queued
|
The
current number of binding updates (both IPv4 and IPv6) that are queued at
present.
This number should typically be small (as a percentage of total leases), but can grow large if there are many leases needing
updates (such as if the partners were integrated after an outage of one of them) or the partner is slow to process updates.
This number will not exceed the total number of leases.
It is a cause for concern if the number is greater than 1000 or 10% of the leases (whichever is larger), and even more so
if it is continuing to grow. Typically this means that the failover partner is experiencing high latency in processing requests
(usually disk latency is the primary issue).
|
maximum-binding-updates-in-flight
|
The
maximum number of binding updates (both IPv4 and IPv6) that were in-flight
(sent) at one time.
|
maximum-binding-updates-queued
|
The
maximum number of binding updates (both IPv4 and IPv6) that were queued at one
time.
|
last-binding-update-sent-time
|
The time
the last binding update (either IPv4 or IPv6) was sent.
|
last-binding-ack-received-time
|
The time
the last IPv4 or IPv6 binding acknowledgement (whether NAKed or not) was
received.
|
last-binding-update-received-time
|
The time
the last binding update (either IPv4 or IPv6) was received.
|
last-binding-ack-sent-time
|
The time
the last IPv4 or IPv6 binding acknowledgement (whether NAKed or not) was sent.
|