infoblox_uddi:dhcp
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_uddi:dhcp [2026/03/08 17:51] – [DNS Suffix] bstafford | infoblox_uddi:dhcp [2026/03/25 00:09] (current) – [Split Scope] bstafford | ||
|---|---|---|---|
| Line 84: | Line 84: | ||
| * If DHCP server gets a ping response, Infoblox Portal marks the IP as ABANDONED. | * If DHCP server gets a ping response, Infoblox Portal marks the IP as ABANDONED. | ||
| + | ===== Split Scope ===== | ||
| + | * General use case for Split Scope is IPv6 and also Microsoft Migration. | ||
| + | * Infoblox manages DHCP on other vendors like Versa networks and which only support split scopes (or vendors like Microsoft which support split scope and can be managed by Universal DDI) - so Universal DDI must support Split Scopes. | ||
| + | * With IPv6 you can divide a /64 into two /65 subnets | ||
| + | * Split Scope has no lease sharing or heatbeat so it is simpler. | ||
| + | * DDNS Expirations can be an issue for Fixed Address objects in Split Ranges. | ||
| + | * Both servers in split scope will get any fixed address object in that range. | ||
| + | * You cannot adjust the split. It is always 50/50. Possibly off by 1. If Exclusion ranges block a large section of one half of the range, that server will only serve the bits it can. The system doesn' | ||
| + | * Don't convert split range to Active/ | ||
| + | * Resizing pool (e.g. 100-120) can also cause confusion because PartA doing 1-50 and PartB doing 51-100 is now PartA doing 1-60 and PartB doing 61 - 120 | ||
| + | * When you REPLACE a box, the new one will get the old leases from portal. | ||
| + | * If client got lease from ServerA and then ServerA fails, when client comes back for IP. If client has " | ||
infoblox_uddi/dhcp.1772992310.txt.gz · Last modified: by bstafford
