05-17-2024 03:39 PM - edited 05-18-2024 03:38 AM
Hello,
I'm working on a lab assignment in packet tracer and when go into any of my devices and switch from static to DHCP it shows a message stating "DHCP failed. APIPA is being used."
I have no idea what this means and I'm not getting any feedback from anyone. I attached .pkt file for what I have done. If someone can help in anyway that would be great. If you need anything from me just let me know and I'll share it with you as soon as I can. Thank you.
Solved! Go to Solution.
05-18-2024 01:02 AM
Hello @Josh KR ,
on the multilayer switch Fed, you should correct the following:
1. interface Gi1/0/24 has a /8 subnet mask configured which prohibits other subnets of network 10.0.0.0 to be configured on the switch. Change it to ip address 10.0.0.1 255.255.255.0
2. the switch Fed is configured as a DHCP server for vlans 10, 20, 30 but the SVI's for this vlans do not have an IP address configured. Add the following to the Fed config:
interface Vlan10
ip address 10.156.1.1 255.255.255.0
!
interface Vlan20
ip address 10.156.2.1 255.255.255.0
!
interface Vlan30
ip address 10.156.3.1 255.255.255.0
That should take care of your DHCP problem.
One more thing - on the RV, change the subnet mask for the Gi0/0 interface to match the one on interface Gi1/0/24 on Fed:
interface GigabitEthernet0/0
ip address 10.0.0.2 255.255.255.0
Hope this helps.
05-19-2024 04:16 AM
Updated PT file.
05-21-2024 11:57 AM
Hello @Josh KR ,
The issue with the ping not working over the VPN tunnel between Meknes and Rabat is caused by a faulty VPN-ACL on the RMekens router - as soon as you change it to
permit ip 172.16.0.0 0.0.255.255 10.0.0.0 0.255.255.255
the VPN tunnel starts working.
The NAT in Rabat is working ok - because you configured the VPN tunnel between Meknes and Rabat, your NAT access list excludes traffic between these two sites, IP's 10.0.0.0/8 and 172.16.0.0/16, from being NAT-ed.
Your NAT works for other source/destination pairs, for example from the Management vlan to DMZ, 82.156/0/0/29, or any of the interfaces in the WAN, R1 - R4, as can be seen in the following output on RIV with traffic generated from one of the Management hosts to the link between R2 and R3:
RIV#sho ip nat tra
Pro Inside global Inside local Outside local Outside global
icmp 82.156.0.1:379 10.156.1.11:379 62.156.0.9:379 62.156.0.9:379
icmp 82.156.0.1:380 10.156.1.11:380 62.156.0.9:380 62.156.0.9:380
icmp 82.156.0.1:381 10.156.1.11:381 62.156.0.9:381 62.156.0.9:381
icmp 82.156.0.1:382 10.156.1.11:382 62.156.0.9:382 62.156.0.9:382
icmp 82.156.0.1:383 10.156.1.11:383 62.156.0.9:383 62.156.0.9:383
icmp 82.156.0.1:384 10.156.1.11:384 62.156.0.9:384 62.156.0.9:384
icmp 82.156.0.1:385 10.156.1.11:385 62.156.0.9:385 62.156.0.9:385
icmp 82.156.0.1:386 10.156.1.11:386 62.156.0.9:386 62.156.0.9:386
icmp 82.156.0.1:387 10.156.1.11:387 62.156.0.9:387 62.156.0.9:387
icmp 82.156.0.1:388 10.156.1.11:388 62.156.0.9:388 62.156.0.9:388
05-17-2024 09:16 PM
checkout this post and youtube video, hope this helps.
05-18-2024 01:02 AM
Hello @Josh KR ,
on the multilayer switch Fed, you should correct the following:
1. interface Gi1/0/24 has a /8 subnet mask configured which prohibits other subnets of network 10.0.0.0 to be configured on the switch. Change it to ip address 10.0.0.1 255.255.255.0
2. the switch Fed is configured as a DHCP server for vlans 10, 20, 30 but the SVI's for this vlans do not have an IP address configured. Add the following to the Fed config:
interface Vlan10
ip address 10.156.1.1 255.255.255.0
!
interface Vlan20
ip address 10.156.2.1 255.255.255.0
!
interface Vlan30
ip address 10.156.3.1 255.255.255.0
That should take care of your DHCP problem.
One more thing - on the RV, change the subnet mask for the Gi0/0 interface to match the one on interface Gi1/0/24 on Fed:
interface GigabitEthernet0/0
ip address 10.0.0.2 255.255.255.0
Hope this helps.
05-18-2024 03:37 AM
Thank you a lot, your reply solved my problem and now dhcp is working perfectly, thanks again.
05-18-2024 03:38 AM
You are welcome.
05-19-2024 04:16 AM
05-21-2024 02:01 AM - edited 05-21-2024 05:03 PM
@liviu.gheorghe Thank you for your help,
I hope everything is good for you. I finished the ACL and it works because of your assistance. However, there is one small issue that prevents my work from being flawless: I configured the VPN and NAT, but I have two things that do not work for some reason. If you could please assist me, dear Liviu,
The issue at hand pertains to the VPN tunnel between Meknes and Rabat, which is causing ping issues between the two locations. Additionally, the translation NAT in Rabat is malfunctioning. These are the only remaining issues I am facing at work. If you have the time, please assist me in identifying the mistake I made.
Much obliged, my dear Liviu.
05-21-2024 11:57 AM
Hello @Josh KR ,
The issue with the ping not working over the VPN tunnel between Meknes and Rabat is caused by a faulty VPN-ACL on the RMekens router - as soon as you change it to
permit ip 172.16.0.0 0.0.255.255 10.0.0.0 0.255.255.255
the VPN tunnel starts working.
The NAT in Rabat is working ok - because you configured the VPN tunnel between Meknes and Rabat, your NAT access list excludes traffic between these two sites, IP's 10.0.0.0/8 and 172.16.0.0/16, from being NAT-ed.
Your NAT works for other source/destination pairs, for example from the Management vlan to DMZ, 82.156/0/0/29, or any of the interfaces in the WAN, R1 - R4, as can be seen in the following output on RIV with traffic generated from one of the Management hosts to the link between R2 and R3:
RIV#sho ip nat tra
Pro Inside global Inside local Outside local Outside global
icmp 82.156.0.1:379 10.156.1.11:379 62.156.0.9:379 62.156.0.9:379
icmp 82.156.0.1:380 10.156.1.11:380 62.156.0.9:380 62.156.0.9:380
icmp 82.156.0.1:381 10.156.1.11:381 62.156.0.9:381 62.156.0.9:381
icmp 82.156.0.1:382 10.156.1.11:382 62.156.0.9:382 62.156.0.9:382
icmp 82.156.0.1:383 10.156.1.11:383 62.156.0.9:383 62.156.0.9:383
icmp 82.156.0.1:384 10.156.1.11:384 62.156.0.9:384 62.156.0.9:384
icmp 82.156.0.1:385 10.156.1.11:385 62.156.0.9:385 62.156.0.9:385
icmp 82.156.0.1:386 10.156.1.11:386 62.156.0.9:386 62.156.0.9:386
icmp 82.156.0.1:387 10.156.1.11:387 62.156.0.9:387 62.156.0.9:387
icmp 82.156.0.1:388 10.156.1.11:388 62.156.0.9:388 62.156.0.9:388
05-21-2024 05:08 PM
@liviu.gheorghe Thank you a lot for your help and assitance, everything is working now thanks again
05-21-2024 10:52 PM
You are welcome.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide