cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
222
Views
0
Helpful
10
Replies

Cant ping to next hop

kennylee88
Level 1
Level 1

Hello all,

 I just started playing with the Cisco Packet Tracer.. I created a simple 3 routers and layers 3 switch with VLAN in each network respectfully.  I cannot for life figure out why my VLANs computers can not even ping out to the next hop (next nearest router).

I have IP route 0.0.0.0 0.0.0.0 200.100.10.10.2 still no dice.  I have attached a zip PKT file.  Any kind help I greatly appreciate.

 

 

10 Replies 10

 

@kennylee88 

 If you want to have PC on network 20.x.x.x and 10.10.10.x, you need to create those on the L3 switch. You need to create interface vlans to serve as gateways for this PCs.

int vlan x

ip add 10.10.10.1 255.255.255.0

int vlan y

ip add 20.20.20.1 255.255.255.0

then, assign the vlans the PCs are connected properly. And add the interface vlan IP address as gateway on PCs.

FlavioMiranda_0-1727790206718.png

 

Hello,

Yes i configured those too. I will post the sh run here.   


interface FastEthernet0/1
no switchport
ip address 100.10.10.2 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface Vlan1
no ip address
shutdown
!
interface Vlan10
mac-address 0001.c990.9d01
ip address 10.10.10.1 255.255.255.0
!
interface Vlan20
mac-address 0001.c990.9d02
ip address 20.20.20.1 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 100.10.10.1
!
ip flow-export version 9
!
!
!
!
!
!
!
!
line con 0
!
line aux 0
!
line vty 0 4


!
interface FastEthernet0/1
no switchport
ip address 200.10.10.2 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/2
switchport access vlan 40
!
interface FastEthernet0/3
switchport access vlan 30
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface Vlan1
no ip address
shutdown
!
interface Vlan30
mac-address 0001.425c.9c01
ip address 30.30.30.1 255.255.255.0
!
interface Vlan40
mac-address 0001.425c.9c02
ip address 40.40.40.1 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/1

You may created the interface vlan but did not create the vlan on the switch.

Take a look on this file. The PC 20.20.20.2 can ping the router.

Hello Favio,

  I download that file.  Looks the same as mine.  No new configuration was done to it.. Maybe you uploaded the wrong file?

Try this one. It is possible I attached the wrong file

Hi Favio,

Im going try do OSPF instead of static route.   Probably the OSPF is much easier to configure  than static route.  Thanks again brother!

Yeah, go for it.

Joseph W. Doherty
Hall of Fame
Hall of Fame

Responding from my phone, so cannot, at the moment, view your lab, but links connecting routers, their interface IPs are on the same network (and link is up)?  If so, you should be able to ping adjoining router's directly connecting interface IP.

To ping beyond a shared network, you need a correctly populated route table.

You mentioned using a default route, which can lead packets to some common point, but opposite direction traffic will need other than a default route.  The latter might be specific networks and/or aggregates.

As you also mention L3 switches, there are a couple of ways to share network between them and other L3 switches or routers.

Ah, have your lab openned in PT.

Starting with your central router, Router1, it only knows of its two directly connected interfaces.  So, it doesn't know where to send any other destination traffic.

Router0 and Router2 also knows only of their directly connected interface networks, but Router2 has a default route to a down interface.

Switch0 is missing much.  Switch1 looks like it has enough to be functional, but other network device missing configuration information precludes access to the rest of the network.

BTW, it's better to define a next hop IP when defining static routes, including for the default route.

As just one example, from PC1, it can ping PC2 or Switch1's f0/1 IPs, but cannot ping Router2's f0/0 IP.  The reason for that is, Router2 doesn't know where PC1's subnet is.

You can get you whole network to work but providing all the needed static routes, but even for as few as 5 routing network devices, using a dynamic routing protocol might be a better way.

i will try do the OSPF tonight.  Unless you can give me a hand   thx for the help.

Review Cisco Networking for a $25 gift card