Need Help with Lab 4.4.1 Routing Loops

What exactly is said to not be correct in the assessment?

It doesn't tell me it says "This activity is incomplete, please try again." and when I click on the assessment tab it tell me my "routes are incomplete". So everything looks good?

Packet tracer is very picky. if they expect you to use default routes with the correct interface, you may want to stick to that. I see that you didn't use default routes but specific static routes.

jtdk985

mind uploading the lab, or posting a link to where you got it?

and yes codeblox is right, packet tracer likes exit interface most of the time, instead of the next hop ip

jtdk985 wrote: »

mind uploading the lab, or posting a link to where you got it?

and yes codeblox is right, packet tracer likes exit interface most of the time, instead of the next hop ip

Is it like this one the exams as well?

jtdk985

no idea! testing 640-802 tuesday, so ill let you know

assuming the test simulates the full IOS, i couldnt see it being like this. if the command does the same thing, just uses a different format, it should except it either way.

Yeah but they tend to disable stuff... Making you do something in a specific way. Best to know more than one way to do things.

I tried it both ways using the next hop router and using the exit interface and it made no difference. The lab didn't specify what kind of route to use. I'm only on the second semester and into chapter 4 so I don't remember covering default routes yet. Looks like default routes are covered in the next chapter (5). Hopefully the CCNA will not be this picky?

It won’t allow me to upload the lab using the manage attachments. When I get off from work I will host it on a web server.

Thanks

In the text in your first post, they mentioned that you should see a few routes "ip route 0.0.0.0 0.0.0.0 s0/1" and "ip route 0.0.0.0 0.0.0.0 s0/0" Those are default routes. perhaps the only change needed was to swap the serial interface. I'd imagine those default routes should point to the ISP router...

CodeBlox wrote: »

In the text in your first post, they mentioned that you should see a few routes "ip route 0.0.0.0 0.0.0.0 s0/1" and "ip route 0.0.0.0 0.0.0.0 s0/0" Those are default routes. perhaps the only change needed was to swap the serial interface. I'd imagine those default routes should point to the ISP router...

That's the only case we have covered is the "ip route 0.0.0.0 0.0.0.0". Aren't there more cases than that?

Each router has 3 interfaces. If I just swap the serial interface how will it know to reach the other network on the other interface. By putting in the "ip route 0.0.0.0 0.0.0.0 s0/0" its pretty much saying all trafic will go out that interface I specify, correct?

That is correct. But listen, your images serial interfaces aren't labeled and i'm not sure if these are the original running-configs. Could you post those as well as a labeled image?

The configs I posted are my corrected ones to get everything to ping.

Below are the original configs. Thanks for the help.

*******Branch 1 Running Config************
Building configuration...

Current configuration : 520 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname BRANCH1
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
ip address 172.16.4.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
ip address 192.168.1.6 255.255.255.252
!
interface Serial0/1
ip address 192.168.2.1 255.255.255.252
clock rate 56000
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/1
!
!
!
!
!
!
!
line con 0
line vty 0 4
login
!
!
!
end

**************Branch 2****************

Building configuration...

Current configuration : 503 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname BRANCH2
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
ip address 172.16.15.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
ip address 192.168.2.2 255.255.255.252
!
interface Serial0/1
ip address 192.168.3.9 255.255.255.252
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0
!
!
!
!
!
!
!
line con 0
line vty 0 4
login
!
!
!
end

***************ISP********************

Building configuration...

Current configuration : 683 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname ISP
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
ip address 10.10.0.1 255.255.0.0
duplex auto
speed auto
!
interface Serial0/0
ip address 192.168.1.5 255.255.255.252
clock rate 56000
!
interface Serial0/1
ip address 192.168.3.10 255.255.255.252
clock rate 56000
!
ip classless
ip route 172.16.4.0 255.255.255.0 Serial0/0
ip route 172.16.15.0 255.255.255.0 Serial0/1
ip route 192.168.2.0 255.255.255.252 Serial0/0
ip route 192.168.2.0 255.255.255.252 Serial0/1
!
!
!
!
!
!
!
line con 0
line vty 0 4
login
!
!
!
end

I went and grabbed the PT assignment you were doing (Routing Protocols and Concepts - 4.4.1.2). You need to start with the lowest common denominator. Thats ping and trace route. If you ping PC0 to PC2 or PC3 the packets get dropped at the ISP router. So there is an issue with the ISP router connecting.

Then if you trace route from PC2 to PC3 it works fine. This says that the connection if fine between Branch 1 and 2. Next trace route from PC2 and 3 to PC0. the hops fail after you exit the Branch routers, telling us that there is a connection issue between Branch 1/2 and the ISP.

The PT instructions tell you that the static routes are set incorrectly. If you run a "sh ip int brief" and compare that to the trace routes you can see that the branch routers static routes are set to the int. connecting to the opposite branch router (branch 1 set route to Branch 2 and vise versa). So remove the static route from the incorrect interface and add a new static route to the correct interface to set the route to the ISP router.

onesaint wrote: »

I went and grabbed the PT assignment you were doing (Routing Protocols and Concepts - 4.4.1.2). You need to start with the lowest common denominator. Thats ping and trace route. If you ping PC0 to PC2 or PC3 the packets get dropped at the ISP router. So there is an issue with the ISP router connecting.

Then if you trace route from PC2 to PC3 it works fine. This says that the connection if fine between Branch 1 and 2. Next trace route from PC2 and 3 to PC0. the hops fail after you exit the Branch routers, telling us that there is a connection issue between Branch 1/2 and the ISP.

The PT instructions tell you that the static routes are set incorrectly. If you run a "sh ip int brief" and compare that to the trace routes you can see that the branch routers static routes are set to the int. connecting to the opposite branch router (branch 1 set route to Branch 2 and vise versa). So remove the static route from the incorrect interface and add a new static route to the correct interface to set the route to the ISP router.

Ok thanks I might have rushed that one a little bit. I will go over it again tommorrow.

dan87951 wrote: »

Ok thanks I might have rushed that one a little bit. I will go over it again tommorrow.

No worries. That stuff can all be a pain with the specifics to get it right. Just wait till you have to do ACLs. =^)

Interesting that your on the Exploration as opposed to Discovery path. Ive been told that Exploration is more in depth. None the less, I didnt find the writing in either to be all that great. Its abstract, yet they have detailed expectations.

Thanks, got it! I went over the lab again and my problem was I was not treating the ISP router as the ISP router. I wanted to route all other traffic other than the specified traffic to the ISP router which I had not done hence the not complete. Plus I was thinking to much into it. I didn't want all the local traffic to route through the ISP router as that would make 2 hops so I put in a static route on each of the branch 1 and branch 2 routers so traffic could be directed in 1 hop. Anyways, Thanks for the quick help.

I'm using the online Cisco Academy training which is kinda an over view.