Need help with CCNA2 configuration

[spree]

Hello!

 

So basically I am setting up a topology, see screenshot: 

 

And I want the following adresses:

 

 

With ground configuration and static routes so they can communicate. With a static default route from R2 to internet.

 

But I cannot get it to work. The PC's wont ping to each other. Can someone help me? 

 

Kind regards!

[Windows7ge]

*Forms a pentagram on the floor using networking cables. Cracks open a CISCO 1941 router as a blood sacrifice.*

 

*Open to page 327 of the CISCO manual*

 

*Inhales...*

 

@Lurick

 

Spoiler

I would help you myself but too much time has passed since i did this last. All I remember are the fundamental commands. (en, config t, show run, etc.) 

 

Doesn't this assignment come with step by step instructions? They usually do. Sometimes you have to look up a couple commands in the class material if they're testing your memorization skills.

 

[spree]

1 minute ago, Windows7ge said:

*Forms a pentagram on the floor using networking cables. Cracks open a CISCO 1941 router as a blood sacrifice.*

 

*Open to page 327 of the CISCO manual*

 

*Inhales...*

 

@Lurick

 

  Hide contents

I would help you myself but too much time has passed since i did this last. All I remember are the fundamental commands. (en, config t, show run, etc.) 

 

Doesn't this assignment come with step by step instructions? They usually do. Sometimes you have to look up a couple commands in the class material if they're testing your memorization skills.

 

I feel like it should be working. I have googled like a maniac.

 

I belive there is something wrong in my configuration when trying to make the static routes. 

 

No further instructions... This pandemic is making CCNA2 so hard...

[The_russian]

Without seeing the configuration of all 3 routers and the PCs there’s only so much I can help, but just a suggestion check the static routes on R2. Sometimes you can focus too hard on the routers directly connected to the PCs and overlook the interconnecting routers.

 

Edit: Also double check your addressing for all devices, it’s easy to accidentally mistype a number and not notice it.

[spree]

22 minutes ago, The_russian said:

Without seeing the configuration of all 3 routers and the PCs there’s only so much I can help, but just a suggestion check the static routes on R2. Sometimes you can focus too hard on the routers directly connected to the PCs and overlook the interconnecting routers.

 

Edit: Also double check your addressing for all devices, it’s easy to accidentally mistype a number and not notice it.

Router1: 

Current configuration : 1322 bytes

!

version 15.4

no service timestamps log datetime msec

no service timestamps debug datetime msec

service password-encryption

!

hostname R1

!

!

!

enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1

!

!

!

!

!

aaa new-model

!

!

!

!

!

!

!

!

no ip cef

no ipv6 cef

!

!

!

username admin privilege 15 secret 5 $1$mERr$gl671C./OJRCi058hruuW/

!

!

!

!

!

!

!

!

ip domain-name tbschool.se

!

!

spanning-tree mode pvst

!

!

!

!

!

!

interface GigabitEthernet0/0/0

ip address 192.168.1.1 255.255.255.224

duplex auto

speed auto

!

interface GigabitEthernet0/0/1

no ip address

duplex auto

speed auto

shutdown

!

interface GigabitEthernet0/0/2

no ip address

duplex auto

speed auto

shutdown

!

interface Serial0/1/0

description "Connected to R2"

ip address 10.1.1.1 255.255.255.252

!

interface Serial0/1/1

no ip address

clock rate 2000000

shutdown

!

interface Serial0/2/0

no ip address

clock rate 2000000

shutdown

!

interface Serial0/2/1

no ip address

clock rate 2000000

shutdown

!

interface Vlan1

no ip address

shutdown

!

ip classless

ip route 172.16.31.0 255.255.255.224 10.1.1.2

ip route 10.2.2.0 255.255.255.252 10.1.1.2

!

ip flow-export version 9

!

!

!

banner motd ^Ctest^C

!

!

!

!

!

line con 0

password 7 0822455D0A16

!

line aux 0

!

line vty 0 4

password 7 0822455D0A16

line vty 5 15

password 7 0822455D0A16

!

!

!

end

 

 

 

 

 

 

--------------------------------------------------------------------------------------------------------------------------------

 

Router 2: 

 

Building configuration...

 

Current configuration : 1125 bytes

!

version 15.4

no service timestamps log datetime msec

no service timestamps debug datetime msec

service password-encryption

!

hostname R2

!

!

!

enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1

!

!

!

!

!

!

no ip cef

no ipv6 cef

!

!

!

!

!

!

!

!

!

!

!

!

spanning-tree mode pvst

!

!

!

!

!

!

interface GigabitEthernet0/0/0

no ip address

duplex auto

speed auto

shutdown

!

interface GigabitEthernet0/0/1

no ip address

duplex auto

speed auto

shutdown

!

interface GigabitEthernet0/0/2

no ip address

duplex auto

speed auto

shutdown

!

interface Serial0/1/0

ip address 10.1.1.2 255.255.255.252

clock rate 2000000

!

interface Serial0/1/1

description "Connected to R3"

ip address 10.2.2.2 255.255.255.252

!

interface Serial0/2/0

no ip address

clock rate 2000000

shutdown

!

interface Serial0/2/1

no ip address

clock rate 2000000

shutdown

!

interface Vlan1

no ip address

shutdown

!

ip classless

!

ip flow-export version 9

!

!

!

banner motd ^Ctest2^C

!

!

!

!

!

line con 0

password 7 0822455D0A16

login

!

line aux 0

!

line vty 0 4

password 7 0822455D0A16

login

line vty 5 15

password 7 0822455D0A16

login

!

!

!

end

 

 

 

 

 

--------------------------------------------------------------------------------------------------------------------------------

 

Router 3: 

Building configuration...

 

Current configuration : 1149 bytes

!

version 15.4

no service timestamps log datetime msec

no service timestamps debug datetime msec

service password-encryption

!

hostname R3

!

!

!

enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1

!

!

!

!

!

!

no ip cef

no ipv6 cef

!

!

!

!

!

!

!

!

!

!

!

!

spanning-tree mode pvst

!

!

!

!

!

!

interface GigabitEthernet0/0/0

description "Connected to PCB"

ip address 172.16.31.1 255.255.255.224

duplex auto

speed auto

!

interface GigabitEthernet0/0/1

no ip address

duplex auto

speed auto

shutdown

!

interface GigabitEthernet0/0/2

no ip address

duplex auto

speed auto

shutdown

!

interface Serial0/1/0

no ip address

clock rate 2000000

shutdown

!

interface Serial0/1/1

ip address 10.2.2.1 255.255.255.252

clock rate 2000000

!

interface Serial0/2/0

no ip address

clock rate 2000000

shutdown

!

interface Serial0/2/1

no ip address

clock rate 2000000

shutdown

!

interface Vlan1

no ip address

shutdown

!

ip classless

!

ip flow-export version 9

!

!

!

banner motd ^Ctest3^C

!

!

!

!

!

line con 0

password 7 0822455D0A16

login

!

line aux 0

!

line vty 0 4

password 7 0822455D0A16

login

line vty 5 15

password 7 0822455D0A16

login

!

!

!

end

[Lurick]

Router 2 and Router 3 have no static routes either direction.

Router 2 needs statics to get to the PC behind R3

R3 needs statics to get back to R1 through R2

[kasugatei]

3 minutes ago, spree said:

snip

I am a bit rusty with Cisco, but I don't see any routing on routers 2 and 3. No protocols defined or static routes defined.

[spree]

2 minutes ago, Lurick said:

Router 2 and Router 3 have no static routes either direction.

Router 2 needs statics to get to the PC behind R3

R3 needs statics to get back to R1 through R2

Do you mind explaining how I would go on to set that up? 

 

Thank you for the reply. 

[Lurick]

Just now, spree said:

Do you mind explaining how I would go on to set that up? 

 

Thank you for the reply. 

Think of static routes like non-GPS directions. You need to specify routes for each subnet you need to reach on each router.

So R2 needs to know how to get to all the networks and R3 needs to know how to get to the networks on R1 via R2.

You've got two statics on R1 and those are fine so similar routes need to go on R3 and then2 routes need to go on R2, one pointing to each router for the subnet the PCs are on.

 

Example:

On r2

ip route 172.16.31.0 255.255.255.254 10.2.2.1

[spree]

7 minutes ago, Lurick said:

Think of static routes like non-GPS directions. You need to specify routes for each subnet you need to reach on each router.

So R2 needs to know how to get to all the networks and R3 needs to know how to get to the networks on R1 via R2.

You've got two statics on R1 and those are fine so similar routes need to go on R3 and then2 routes need to go on R2, one pointing to each router for the subnet the PCs are on.

 

Example:

On r2

ip route 172.16.31.0 255.255.255.254 10.2.2.1

So just to make sure I'm on the right path, on R3 to go to R1 I need:

 

ip route 192.168.1.0 255.255.255.224 10.2.2.2?

[Lurick]

Just now, spree said:

So just to make sure I'm on the right path, on R3 to go to R1 I need:

 

ip route 192.168.1.1 255.255.255.224 10.2.2.2?

You need one of two things:

1) R2 needs to know how to get to those subnets via the connected devices

2) R1 needs to know how to get to that subnet you listed AND how to get to 10.2.2.2 since that's not locally connected.

 

Ideally since you don't need communication between the R1 <> R2 link on the R3 side then you could do it like this:

R1:

static route to PC subnet behind R3 via R2 interface IP

 

R2:

static route to PC subnet behind R3 va R3 interface IP

static route to PC subnet behind R1 via R1 interface IP

 

R3:

static route to PC subnet behind R1 via R2 interface IP

 

 

If you want to go beyond that then a second route on R1 and R3 for the other subnets would be needed but I don't think that's needed here.

[spree]

8 minutes ago, Lurick said:

You need one of two things:

1) R2 needs to know how to get to those subnets via the connected devices

2) R1 needs to know how to get to that subnet you listed AND how to get to 10.2.2.2 since that's not locally connected.

 

Ideally since you don't need communication between the R1 <> R2 link on the R3 side then you could do it like this:

R1:

static route to PC subnet behind R3 via R2 interface IP

 

R2:

static route to PC subnet behind R3 va R3 interface IP

static route to PC subnet behind R1 via R1 interface IP

 

R3:

static route to PC subnet behind R1 via R2 interface IP

 

 

If you want to go beyond that then a second route on R1 and R3 for the other subnets would be needed but I don't think that's needed here.

On R1, 

Ip route 172.16.31.0 255.255.255.224 10.1.1.2

 

the 172 address is the adress which R1 needs to get to R3's LAN, correct?

 

What does 10.1.1.2 address represent? The connection which R1 is connected to R2? 

[Lurick]

1 minute ago, spree said:

On R1, 

Ip route 172.16.31.0 255.255.255.224 10.1.1.2

 

the 172 address is the adress which R1 needs to get to R3's LAN, correct?

 

What does 10.1.1.2 address represent? The connection which R1 is connected to R2? 

ip route (destination network) (destination mask) (next hop)

 

172.16.30.0 255.255.255.224 is the subnet you're trying to reach

10.1.1.2 is the next hop, in this case the IP address of the directly connected interface on the next router

[spree]

5 minutes ago, Lurick said:

ip route (destination network) (destination mask) (next hop)

 

172.16.30.0 255.255.255.224 is the subnet you're trying to reach

10.1.1.2 is the next hop, in this case the IP address of the directly connected interface on the next router

Thank you for the informative answers.

 

I sent you a PM.