Hello,
What is the SKU/Product number of your device?
Thanks!
Hello jaysta,
You have to apply extended address pool to the vlan as it is mentioned under the L3 command guide for HP830 on page 21:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04568105
"If you execute the dhcp server apply ip-pool command on an interface, when a client's request arrives at the interface, the server attempts to assign the client the statically bound IP address first, and then an IP address from this extended address pool. Only an extended address pool can be applied on an interface. The address pool to be referenced must already exist."
Hope this helps!
Hello jaysta,
If your point is to just provide dynamic ip addresses and static bind you can use only common pools why you need dynamic. The pool is detemined by the ip address of the receiving interface. Please check the following which is found on page 26:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04568065
DHCP address pool DHCP address pools include common and extended address pools:
•Common address pool—Supports both static binding and dynamic allocation.
•Extended address pool—Supports only dynamic allocation.
DHCP address pool
DHCP address pools include common and extended address pools:
• Common address pool—Supports both static binding and dynamic allocation.
• Extended address pool—Supports only dynamic allocation.
Common address pool structure
The organization of the common address pool database can be compared to a tree. The root of the tree
is the address pool for natural networks, branches are address pools for subnets, and leaves are
addresses statically bound to clients. For the same level address pools, a previously configured pool has
a higher selection priority than a new one.
At the very beginning, subnets inherit network parameters and clients inherit subnet parameters.
Therefore, common parameters (for example, a DNS server address) should be configured at the highest
(network or subnet) level of the tree.
The new configuration at the higher level (parent) of the tree is:
• Inherited if the lower level (child) has no such configuration.
IP address lease durations are not inherited.
• Overridden if the lower level (child) has such configuration.
NOTE:
The extended address pools on a DHCP server are independent of each other, and no inheritance
relationship exists among them.
Principles for selecting an address pool
The DHCP server observes the following principles to select an address pool when assigning an IP
address to a client:
1. If there is an address pool where an IP address is statically bound to the MAC address or ID of the
client, the DHCP server selects this address pool and assigns the statically bound IP address to the
client. For the configuration of this address pool, see "Configuring static address allocation."
2. If the receiving interface has an extended address pool referenced, the DHCP server assigns an IP
address from this address pool. If no IP address is available in the address pool, the DHCP server
fails to assign an address to the client. For the configuration of such an address pool, see
"Configuring dynamic address allocation for an extended address pool."
3. Otherwise, the DHCP server selects the smallest common address pool that contains the IP address
of the receiving interface (if the client and the server reside on the same subnet), or the smallest
common address pool that contains the IP address specified in the giaddr field of the client's
request (if a DHCP relay agent is in-between). If no IP address is available in the address pool, the
DHCP server fails to assign an address to the client because it cannot assign an IP address from the
parent address pool to the client. For the configuration of such an address pool, see "Configuring
dynamic address allocation."
For example, two common address pools, 1.1.1.0/24 and 1.1.1.0/25, are configured on the DHCP server.
If the IP address of the interface receiving DHCP requests is 1.1.1.1/25, the DHCP server selects IP
addresses for clients from address pool 1.1.1.0/25. If no IP address is available in the address pool, the
DHCP server fails to assign addresses to clients. If the IP address of the interface receiving DHCP requests
is 1.1.1.130/25, the DHCP server selects IP addresses for clients from the 1.1.1.0/24 address pool.
NOTE:
To make sure correct IP address allocation, keep the IP addresses for dynamic allocation within the subnet
where the interface of the DHCP server or DHCP relay agent resides.
Hope this helps!
Hello jaysta,
I do not know the other part of the network and the firewall but you may just create pools - not extended and they will work without assigning them to the interface the most specific one will be chosen and this is based on the interface which receives the request. Please check my previous post which includes the following example:
"For example, two common address pools, 1.1.1.0/24 and 1.1.1.0/25, are configured on the DHCP server.
If the IP address of the interface receiving DHCP requests is 1.1.1.1/25, the DHCP server selects IP
addresses for clients from address pool 1.1.1.0/25. If no IP address is available in the address pool, the
DHCP server fails to assign addresses to clients. If the IP address of the interface receiving DHCP requests
is 1.1.1.130/25, the DHCP server selects IP addresses for clients from the 1.1.1.0/24 address pool.
NOTE:
To make sure correct IP address allocation, keep the IP addresses for dynamic allocation within the subnet
where the interface of the DHCP server or DHCP relay agent resides."
You already know how to create the rules just create dynamic for the range but not extended.
Please note that there could be some specifics in your network which we do not know.