×

Message

PLG_KUNENADISCUSS_DEPENDENCY_FAIL

CONFIGURING THE CISCO ASA AS A DHCP SERVER

NETWORK TOPOLOGY

 

 

 

N.B EVEN THOUGH THE DHCP SERVER IS SHOWN IN THE ABOVE NETWORK TOPOLOGY IN THE DMZ, IT WILL NOT BE USED TO GIVE OUT IP ADDRESSES, INSTEAD WE WILL HAVE THE ASA FIREWALL DO THAT.

 

In some cases, a network might not have a dedicated DHCP server. You can configure an ASA to act as a DHCP server, assigning IP addresses dynamically to requesting clients. The DHCP server can also generate dynamic DNS information, allowing DNS records to be updated dynamically as hosts acquire an IP address.

 

An ASA will return its own interface address for the client to use as the default gateway. The interface subnet mask is returned for the client to use as well. You can define and enable DHCP servers on more than one interface, if clients are located there.

 

As an example in this demonstration, we are going to configure the ASA firewall to issue IP address in the following DHCP Pools/networks.

 

ICT Network:

Network Range: 10.0.10.100 – 10.0.10.254

Default Gateway: 10.0.10.1

DNS server: 172.16.0.5

Domain Name: MOIGETECH.KENYA

 

HR Network:

Network Range: 10.0.20.100 – 10.0.20.254

Default Gateway: 10.0.20.1

DNS server: 172.16.0.5

Domain Name: MOIGETECH.KENYA

 

FINANCE Network:

Network Range: 10.0.30.100 – 10.0.30.254

Default Gateway: 10.0.30.1

DNS server: 172.16.0.5

Domain Name: MOIGETECH.KENYA

 

PROCUREMENT Network:

Network Range: 10.0.40.100 – 10.0.40.254

Default Gateway: 10.0.40.1

DNS server: 172.16.0.5

Domain Name: MOIGETECH.KENYA

 

PC1 is in the ICT Network, PC2 is in the HR network, PC3 is in the FINANCE network and PC4 is in the PROCUREMENT network.

 


 

 

DHCP CONFIGURATIONS ON THE ASA

 

 

 

VERIFICATION ON THE DHCP CLIENTS

 

PC1

 

 

 

From the figure above you can see that PC1 has received its IP address through DHCP from the ASA which happens to be the DHCP server. It has received the correct IP address (10.0.10.100) from the correct DHCP Pool (10.0.10.100 – 10.0.10.254). PC1 has also received the correct domain name which is MOIGETECH.KENYA.

 

PC2

 

 

 

From the figure above you can see that PC2 has received its IP address through DHCP from the ASA which happens to be the DHCP server. It has received the correct IP address (10.0.20.100) from the correct DHCP Pool (10.0.20.100 – 10.0.20.254). PC2 has also received the correct domain name which is MOIGETECH.KENYA.

 

PC3

 

 

 

From the figure above you can see that PC3 has received its IP address through DHCP from the ASA which happens to be the DHCP server. It has received the correct IP address (10.0.30.100) from the correct DHCP Pool (10.0.30.100 – 10.0.30.254). PC3 has also received the correct domain name which is MOIGETECH.KENYA.

 

PC4

 

 

 

From the figure above you can see that PC4 has received its IP address through DHCP from the ASA which happens to be the DHCP server. It has received the correct IP address (10.0.40.100) from the correct DHCP Pool (10.0.40.100 – 10.0.40.254). PC4 has also received the correct domain name which is MOIGETECH.KENYA.

 

DHCP SERVER VERIFICATION ON THE ASA

 

 

 

THE END.

 

 

Go to top