LatticeLattice

Not generally available. Product and docs are public. Sales are closed.

Docs / Troubleshoot

Client got a NAK

Request committed only if the IP is still yours to have. Logs say request nak.

lattice-dhcpd NAKs a Request when:

  • The packet has no requested IP.
  • Commit fails: IP not in a pool, excluded, reserved for someone else, wrong subnet for this giaddr, inventory not free, or license refusing new allocations.

JSON log: "msg":"request nak" with err, xid, mac, ip, subnet_id.

Checklist

  1. Leases search by MAC. If they already have a row in another subnet, release it or fix the relay giaddr.
  2. Utilization on the subnet — free near 0 → pool exhaustion.
  3. A reservation for that IP with a different MAC.
  4. An exclude covering the requested IP.
  5. License over cap: existing leases still renew; a brand-new Request for a new IP NAKs. License.

Server-identifier mismatch is not a NAK. Shared-store HA ignores it so a VIP can land Request on a different node. HA.