Hi boospy,
Aren't (DHCP) dynamic range pool versus (DHCP) static-bind pool mutually exclusive when defined togheter inside the same DHCP Pool?
I mean that if you require static-bind mapping(s) then you should define another separate DHCP Server Pool without IP Address range as an option but with static-bind as option(s), so de-facto keeping separated the static-bind pool from the range pool by using two (or more) DHCP Server Pools.
At least that is what I understand reading the documentation (basically manual bindings should be just special address pools, as reported).
From the HPE Switch Software Management and Configuration Guide WB.16.01:
IP pools
A DHCP server is configured with IP pools. The server is then instructed to use IP addresses falling into the specified range of IP while offering leases. Multiple IP pools are configured to not have duplicate or overlapping IP subnets. You can also configure a DHCP server with multiple IP ranges within an IP subnet; this confines the allocatable IP addresses within the configured IP pool.
An IP pool will be claimed valid only if it is either:
• Dynamic pool - Has a network address, subnet mask and IP range(s),
• Static pool - Should have a static IP-to-MAC binding.
The DHCP server will discard the invalid and incomplete pools and will only operate on the valid IP pools.
The DHCP server will require at least one valid pool to start.