06-10-2016 07:57 PM - edited 03-08-2019 06:09 AM
Hello forum community. I'm new to Cisco configuring and can't figure out why in the attached packet tracer file I can't get my SW! switch to ping the gi0/1 interface on the Branch router and beyond. I also can't figure out why I can ping the gi0/0 interface on the Branch router from the HQ router, but can't ping the SW1 switch and beyond.
Ideally I'm trying to set the network up so that PC1 can ping 172.16.1.100, which is a loopback set on the HQ router. I can ping the loopback from the Branch router, but not the SW1 switch. I can't even ping the gi0/1 interface on the Branch router from the SW1 switch and don't understand why. I can also ping the gi0/0 interface on the Branch router from the HQ router, but can't ping the SW1 switch from the HQ router.
PC1 - 10.1.1.100 255.255.255.0
SW1 - VLAN 1 - 10.1.1.11
Branch - gi0/0 - 10.1.1.1 255.255.255.0, gi0/1 - dhcp assigned as 209.165.201.1 255.255.255.224, dynamic NAT enabled with access-list 1 (permit 10.1.1.0 0.0.0.255), pool name is NAT_POOL with address range of 209.165.201.5 - 10 255.255.255.224 as NAT address range. I can see it working with debug ip nat turned on when I ping from the HQ router the 10.1.1.1 address, although I've test the pinging without NAT and it's still successful. gi0/0 inside nat, g0/1 outside nat.
HQ - gi0/0 - 209.165.201.2 255.255.255.224, dhcp server enabled in order to provide an address to the Branch router gi0/1. I had to add a static ip route of 10.1.1.0 0.0.0.255 209.165.201.1 in order to be able to get the ping from HQ router to Branch router gi0/0 to work. Not sure if there is a better way to do this, but it's the only way I could get it to work so far.
You'll have to rename the .txt file attached to .pkt.
Thanks for any help!
Solved! Go to Solution.
08-04-2016 05:03 PM
Hello
Does the switch have ip routing enabled, if so disable this and give it a default-gateway instead
no ip routing
ip default-gateway x.x.x.x
res
Paul
08-04-2016 05:03 PM
Hello
Does the switch have ip routing enabled, if so disable this and give it a default-gateway instead
no ip routing
ip default-gateway x.x.x.x
res
Paul
08-05-2016 10:00 AM
That was the problem, a lack of a default gateway. Thanks.
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