Gateway of last resort is not set In Cisco Router

Gateway of last resort is not set In Cisco Router or Switch

You may notice the Line “gateway of last resort is not set” in output when you use the cisco command Show IP Route. This short article will explain that why you are getting this message.

Cisco router gateway of last resort

"Gateway of Last Resort is not set” means that there is no default route for IP packets which have no match with routing table. Gateway of last resort are routes use to avoid your router from dropping packets with unknown networks those are not exist in routing table

Routing table have the list of all known routes. Every time when a router receives a packet, router matches it with routing table entries if it present in routing table then it forward to that path and if route not present in routing table then it is forwarded to default gateway or default route.

How to set Gateway of last resort in router

You can configure or set a default gateway, or route of last resort with following commands:

•  ip default-network    
• ip default-gateway    
• ip route 0.0.0.0 0.0.0.0

ip default-gateway

The ip default-gateway command is used when ip routing is disabled on Cisco-router. Following example defines the default route on router to 172.16.15.4:

ip default-gateway 172.16.15.4

ip default-network

Instead of ip default-gateway command, you can use ip default-network when ip routing is enabled on Cisco-router. When you configure ip default-network the router considers routes to that network for installation as the gateway of last resort on the router. Gateways of last resort selected using the ip default-network command are advertised differently depending on which routing protocol is advertise the default route. For IGRP/EIGRP to propagate the route, the network specified by the ip default-network command must be known to IGRP or EIGRP.

RIP advertises a route to 0.0.0.0 if a gateway of last resort is selected using the ip default-network command.

The default route advertised with the ip default-network command is not propagated by IS-IS and OSPF.

IP Route 0.0.0.0

Creating a static-route to unknown network is another way to set the gateway of last resort on a router. IGRP does not recognize a route advertise with static route command to 0.0.0.0. You are required to use the ip default-network command in case of IGRP. EIGRP advertise a route to network 0.0.0.0, but the static route must beredistributed into the routing protocol.

RIP routers running Cisco IOS 12.0T and later does not advertise the default route where as in earlier version it automatically create a default route 0.0.0.0.

Summary:

Use the ip default-gateway command if the ip routing is disabled on Cisco-router and Use the ip default-network and ip route 0.0.0.0 0.0.0.0 commands to set the gateway of last resort on Cisco routers that have ip routing enabled. The way in which routing-protocols advertise the default route differs for each protocol.

Quick Tip:

For setting network of last resort like use the following command:

ip default-network <IP address of gateway>

Redistribute static route into EIGRP re-distribute Static Lab

Redistribute static route into EIGRP

In an inter-network environment, normally you have a single routing-protocol for ease of controlling your network. But when you are connecting the multiple networks, branch office with each other then there may be the different routing protocol.

Route Redistribution permits routes from one routing-protocol to be advertised in-to another routing-protocol. The routing protocol which receives these redistributed-routes are normally marked the routes as external-routes. External-routes are generally less preferred than locally originated-routes.

You can redistribute routes from one routing protocol to same routing protocol, like two separate OSPF with different process ID’s.

Redistribute static route into EIGRP

Similarly you can redistribute static routes and connected interfaces into a routing protocol as well. This article is about the redistributing the static routes into EIGRP process. For simplicity and clear understanding I have designed a lab in GNS3.

Lab Objectives

We have three routers R1, R2 and R3. R1 and R3 are running with EIGRP and our objective is to redistribute the static routes from R2 into EIGRP so that these can be available at R3 as external routes.

I have configured this lab on GNS3 with following configurations:

Configurations on R2

R2(config)#interface f0/0

R2(config-if)#ip address 50.0.0.1 255.255.255.0

R2(config-if)#no shut

R2(config-if)#exit

R2(config)#interface loopback 1

R2(config-if)#ip address 10.10.10.1 255.255.255.0

R2(config-if)#interface loopback 2

R2(config-if)#ip address 20.10.10.1 255.255.255.0

R2(config-if)#interface loopback 3

R2(config-if)#ip address 30.10.10.1 255.255.255.0

R2(config-if)#interface loopback 4

R2(config-if)#ip address 40.10.10.1 255.255.255.0

Configuration of static routes for not directly connected routes:

For static route configurations you are required to advertise destination network with next hop address via static route command as following:

R2(config)#ip route 150.0.0.0 255.255.255.0 50.0.0.2

R2(config)#ip route 100.10.10.0 255.255.255.0 50.0.0.2

R2(config)#ip route 200.10.10.0 255.255.255.0 50.0.0.2

Configurations on R3

R3(config)#int f0/0

R3(config-if)#ip address 150.0.0.2 255.255.255.0

R3(config-if)#no shut

R3(config)#int loopback 1

R3(config-if)#ip address 100.10.10.1 255.255.255.0

R3(config-if)#exit

R3(config)#int loopback 2

R3(config-if)#ip address 200.10.10.1 255.255.255.0

R3(config-if)#exit

R3(config)#router eigrp 10

R3(config-router)#network 150.0.0.0 0.0.0.255

R3(config-router)#network 100.10.10.0 0.0.0.255

R3(config-router)#network 200.10.10.0 0.0.0.255

Configurations on R1

R1(config)#int f1/0

R1(config-if)#ip address 50.0.0.2 255.255.255.0

R1(config-if)#no shutdown

R1(config)#interface fastEthernet 0/0

R1(config-if)#ip address 150.0.0.1 255.255.255.0

R1(config)#router eigrp 10

R1(config-router)#network 150.0.0.0 0.0.0.255

R1(config-router)#network 50.0.0.0 0.0.0.255

R1(config)#ip route 10.10.10.0 255.255.255.0 50.0.0.1

R1(config)#ip route 20.10.10.0 255.255.255.0 50.0.0.1

R1(config)#ip route 30.10.10.0 255.255.255.0 50.0.0.1

R1(config)#ip route 40.10.10.0 255.255.255.0 50.0.0.1

Static Routes redistribution into EIGRP Configurations

For Static Routes redistribution into EIGRP you need to permit all the static routes with a route map which you want to redistribute into EIGRP. For this you are required a access-list with all IP which are going to redistribute in EIGRP.

R1(config)#access-list 7 permit 10.10.10.1

R1(config)#access-list 7 permit 20.10.10.1

R1(config)#access-list 7 permit 30.10.10.1

R1(config)#access-list 7 permit 40.10.10.1

R1(config)#route-map static-to-eigrp permit 10

R1(config-route-map)#match ip address 7

Redistribution Commands:

R1(config)#router eigrp 10

R1(config-route-map)# R1(config-router)#redistribute static route map static-to-eigrp

R1(config-route-map)# R1(config-router)#redistribute static metric 10000 1 255 1 1500 (not compulsory in case of static routes)

Testing and verification of configurations:

After the successful configurations you will find the static routes in R3’s routing table as the external routes:

Network 10.10.10.0, 20.10.10.0, 30.10.10.0 and 40.10.10.0 are the interfaces configured at R1 and after complete configuration you can find these routes in R3 routing table.

You can also perform an end to end ping for testing. Following are some other redistribution labs you can visit these as reference and learning.

• Route redistribution RIP into OSPF And OSPF into RIP
• EIGRP Redistribution of Different AS
• EIGRP OSPF Redistribution 

Cisco Static Routing Lab on GNS3 | Static Routes with GNS3

How to configure the static routes on GNS3

 Static routing is a core technology that any network engineer must understand.  With static Routing you can configure your network without using any dynamic routing protocol like RIP, OSPF etc. Commonly static routes are used for floating routes and a default route. A well designed network should have very few static routes because when you configure a static routes and in case of network changes, you’ll then potentially need to reassess and reconfigure the static route to ensure network connectivity.
With static routes, for successful IP communication it is necessarily you configure bi-directional static routes on each router. Consider the following figure, suppose you want to access R3 from R1, in such case you need two static routes one from R1 to R3 and other R3 to R1.
Static routing configuration is very simple and easy, you just need to advertise the remote network with defining the next hope address. Syntax of static route Cisco command is as under:
Router(config)#ip route <destination network> <mask> <next hope address>

Learn more Basic Cisco commands from here.

In above Gns3 lab you  have three routers on which we will configure routing using static routes. All required configuration are as following, you all also download the full configurations of these routers from links which are given under the configuration of each router.

R1 Configuration:

On router R1 one we have one directly connected network (11.11.11.0/24) and two remote networks 22.22.22.0/24 &  33.33.33.0/24. For static routing you need to configure two static routes for remote network and next hope address will interface f0/0 of R2 which have the IP address 11.11.11.2. Next hope address is like a gateway and IP address of neighbor router which is connected to remote network, if you want to access R3 from R1 you will access it through next hope address 11.11.11.2. 

R1#conf t

R1(config)#interface f0/0

R1(config-if)#ip address 11.11.11.1 255.255.255.0

R1(config-if)#no shut

R1(config-if)#exit

R1(config)#ip route 22.22.22.0 255.255.255.0 11.11.11.2

R1(config)#ip route 33.33.33.0 255.255.255.0 11.11.11.2
Download R1 configuration

R2 Configuration:

On router R2 we have two directly connected network 22.22.22.0/24 &  11.11.11.0/24 and remote network 33.33.33.0/24. Therefore you need to configure the only static route for 33.33.33.0/24 with next hope address 22.22.22.2.

R2#configure terminal

R2(config)#interface f0/0

R2(config-if)#ip address 11.11.11.2 255.255.255.0

R2(config-if)#no shutdown

R2(config-if)#exit

R2(config)#interface f1/0

R2(config-if)#ip address 22.22.22.1 255.255.255.0

R2(config-if)#no shutdown

R2(config-if)#exit

R2(config)#ip route 33.33.33.0 255.255.255.0 22.22.22.2

R2(config)#exit

Download R2 configuration:

R3 Configuration

Remote Network=11.11.11.0/24
Directly connected networks=22.22.22.0/24 &  33.33.33.0/24
Next hope address= 22.22.22.1

R3#configure terminal

R3(config)#interface f0/0

R3(config-if)#ip address 22.22.22.2 255.255.255.0

R3(config-if)#no shutdown

R3(config-if)#exit

R3(config)#interface loopback 1

R3(config-if)#ip address 33.33.33.1 255.255.255.0

R3(config-if)#no shutdown

R3(config-if)#exit

R3(config)#ip route 11.11.11.0 255.255.255.0 22.22.22.1

R3(config)#exit

Download R3 configuration

After the successful configuration show ip route on R1 will have the following output.

Single area OSPF Configuration in JunOS on GNS3 | Lab Example

How to configure Open Shortest Path First on juniper:

OSPF is an IGP which mean it will route packets within a single autonomous system. OSPF is a link-state routing protocol, OSPF make routing decisions using the SPF algorithm (also known as the Dijkstra algorithm). You can configure OSPF version 2 and version 3 with JunOS. For OSPF configuration on JunOS you need to identify the interfaces that will participate in OSPF. You must enable OSPF on all interfaces within the network on which OSPF traffic is to travel. OSPF uses a router identifier for originating packets from device.  

Lab Details:

Gns3 version= Gns3 1.1
Junos version=  JunOS Olive 12.1 VM image
VM VirtualBox version=  4.2.4 
System OS= Windows 8.1

Lab Tasks:

We have three JunOS routers in our topology, our task is to configure all the routers in same OSPF area 0.

Few commands are required for the configuration of OSPF on juniper but  if you want to explore how to configure IP addresses to JunOS interfaces you can visit IP & static routing on JunOS.

Configuration of OSPF on JunOS2:

login: root

root@% Cli

root > configure

[edit]

root # set interfaces em0 unit 0 family inet address 172.16.1.1/24

root # set protocols ospf area 0.0.0.0 interface em0

root #Commit
Having issue with commit command visit missing mandatory statement'root-authentication'
learn more about the configuration of junos in gns3 you can see how to configure junos on gns3 and Juniper commands.

Configuration of OSPF on JunOS3:

login: root

root@% Cli

root > configure

[edit]

root # set interfaces em0 unit 0 family inet address 172.16.1.2/24

root # set interfaces em1 unit 0 family inet address 192.168.1.1/24
OSPF Configurations commands
root # set protocols ospf area 0.0.0.0 interface em0
root # set protocols ospf area 0.0.0.0 interface em1
root #Commit

Configuration of OSPF on JunOS4:

login: root

root@% Cli

root > configure

[edit]

root # set interfaces em0 unit 0 family inet address 192.168.1.2/24

root # set protocols ospf area 0.0.0.0 interface em0

How to test lab configuration:

You can ping 192.168.1.2 from JunOS2 and it will be successful in case of correct configurations, also find the show route command output on JunOS2 which is showing some OSPF routes in routing table.

Other Lab Example : Configuration of RIP on Juniper
End  

RIP Configuration between Cisco and Juniper Routers on Gns3 1.1

How to Configure RIP among different vendor routers:

This article is about configuration of RIP routing protocol between Cisco and juniper. RIP is an open standard protocol that's mean you can configure it among different vendors router. RIP have two versions i.e. version 1 & version 2 (which the most advance & standard version of routing information protocol). On Cisco when you enable RIP, by default its run the version 1 and you manually have to configure the version 2. On the other hand junOS enables the version 2 by default.

Lab details:

Gns3: Gns3 version 1.1.X
VitualBox: 4.2.4 
Cisco IOS: Cisco 7200 series
Junos version=  JunOS Olive 12.1 VM image

Beginner and want to learn about JunOS then you can see how to configure junos on gns3 and Juniper commands.

In our topology we have three router j2, j4 & R1, junos2 & junos4 are juniper routers and R1 is Cisco router.
Lab objective:
Configure RIP on all the routers so that they can communicate with each other.
Lab configurations:
You need to perform the following configurations for achieving the above objective.
JUNOS 2 Configuration:
On JUNOS 2 device, both interfaces em0 and lo0 will be configured for RIP. They will be in the same RIP group called rip-routes.

set interface em0 unit 0 family inet 172.16.1.1/24

set interface lo0 unit 0 family inet 111.0.0.1/32

set protocols rip group rip-routes neighbor em0

set policy-option policy-statement advertise-RIProutes from protocol direct

set policy-option policy-statement advertise-RIProutes from protocol rip

set policy-option policy-statement advertise-RIProutes then accept  

set protocols rip group rip-routes export advertise-RIProutes

 "advertise-RIProutes" is the name of policy for RIP, you can learn more about the configuration of RIP on juniper.

Output of run show configuration | display set on JunOS 2:

JUNOS 4 Configuration:
Similarly you will be configure both interfaces em0 & lo0 for RIP with similar RIP group i.e. rip-routes.

set interface em0 unit 0 family inet 192.168.1.2/24

set interface lo0 unit 0 family inet 222.0.0.1/32

set protocols rip group rip-routes neighbor em0

set policy-option policy-statement advertise-RIProutes from protocol direct

set policy-option policy-statement advertise-RIProutes from protocol rip

set policy-option policy-statement advertise-RIProutes then accept  

set protocols rip group rip-routes export advertise-RIProutes

Output of run show configuration | display set on JunOS 4:

R1 Configuration:
On cisco router you need to advertise both network 192.168.1.0 & 172.16.1.0 In RIP routing

interface FastEthernet0/0
 ip address 172.16.1.2 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 ip address 192.168.1.1 255.255.255.0
 duplex auto
 speed auto
!
router rip
 version 2
 network 172.16.0.0
 network 192.168.1.0
 no auto-summary

How to test your configurations:
After the correct configuration ping from JunOS2 to 222.0.0.1 should be successful.

Output of Cisco Routing Table:

Output of Routing Table on JunOS 2:

How to Configure RIP on Juniper in GNS3 1.1

Run Routing Information Protocol on JunOS 12.1 in GNS3:

In this article i will show you how to run the RIP (Routing Information Protocol) among juniper routers. when you configure the RIP on junos by default it will enable RIP v2 & this is one of the difference from Cisco where you need to configure version2 manually.
I have simulated this lab on gns3 which is one famous network simulator. For juniper simulation i have used junos olive only for study purpose and junos olive is not suitable for any type of commercial use. Gns3 Labs detail are as mention below but you can use any versions of these software.

Gns3 version= Gns3 1.1
Junos version=  JunOS Olive 12.1 VM image
VM VirtualBox version=  4.2.4 

If you want learn more about the configuration of junos in gns3 you can visit how to configure junos on gns3 and Juniper commands.

Lab Requirements:
There are three Junos routers in given topology which are connected with each other and already configured with correct IP addresses according to topology. If you want to explore how to configure IP addresses to JunOS interfaces you can visit IP & static routing on JunOS. We have the following task for this Gns3 Lab:

• Configure RIP routing protocol on all these routers

Explanation:
Configuration of RIP on junOS is very simple, you need only few commands and then good to go..:).
By default JunOS don't advertise RIP routes & the routes received from neighbors, so we need to define a routing policy for advertisement of RIP routes.

Configuration of RIP on JunOS2:  

You can start configuring JunOS2 in following way.

login: root

root@% Cli

root > configure

[edit]

root # set protocols rip group rip-routes neighbor em0 

where rip-routes is the group name, which you can set it of own choice and em0 is the connected interface of Junos2.

root #set policy-options policy-statement advertise-RIProutes from protocol direct
root #set policy-options policy-statement advertise-RIProutes from protocol rip
root #set policy-options policy-statement advertise-RIProutes then accept

Where "advertise-RIProutes" is the name of policy. now you need to apply this policy with following command.
root # set protocols rip group rip-routes export advertise-RIProutes
root # commit
Useful link: how to save current configuration in junos.

RIP Configuration  on JunOS3: 

root

Cli

configure

set protocols rip group rip-routes neighbor em0 

set protocols rip group rip-routes neighbor em1

Set policy-options policy-statement advertise-RIProutes from protocol direct

set policy-options policy-statement advertise-RIProutes from protocol rip

set policy-options policy-statement advertise-RIProutes then accept

set protocols rip group rip-routes export advertise-RIProutes

 commit

RIP Configuration  on JunOS4: 

root

Cli

configure

set protocols rip group rip-routes neighbor em0

Set policy-options policy-statement advertise-RIProutes from protocol direct

set policy-options policy-statement advertise-RIProutes from protocol rip

set policy-options policy-statement advertise-RIProutes then accept

set protocols rip group rip-routes export advertise-RIProutes

 commit
How to verify configuration:

You can test your configuration by ping from junos2 to 222.0.0.1 which is a loopback address on junos4. Also "show route" will show all routes on all routers. An output of show route command will have the following routes:

How to Configure Static routing on juniper router in gns3

Junos static route configuration:

In this article i will show you how to configure static routing with junier router on gns3. For configuring static routing you need to define the route as static and with a next-hop address with it. 

Please note this lab is performed only for study and practice purposes using Junos olive , which is unsupported and unsupportable platform & it is not suitable for any type of commercial use.
Lab Requirements

You have three juniper routers connected with each other, you have the following tasks to perform:

• Configure all the interfaces with right IP address (According to figure)
• Configure static routes between all routers so that they can communicate with each other.

Other Detail:

Junos image version= JunOS Olive image 12.1 
Gns3 version= Gns3 1.1 (you can use any version)
VM VirtualBox version=  4.2.4 (you can use any version)

you can visit how to configure junos on gns3 and Basic JunOS commands.

Set IP addresses of all interfaces of juniper router:

For setting ip address of interface you need the following commands.

JunOs2 configuration:

login: root

root@% Cli

root > configure

[edit]

root # set interfaces em0 unit 0 family inet address 172.16.1.1/24

You can also configure some loopback with these commands:

root # set interfaces lo0 unit 55 family inet address 111.0.0.1/32

root # commit

Having issue with commit command visit missing mandatory statement'root-authentication'

JunOs3 configuration:

Cli

configure

set interfaces em0 unit 0 family inet address 172.16.1.2/24

set interfaces em1 unit 0 family inet address 192.168.1.1/24

commit

JunOs4 configuration:

Cli

configure

set interfaces em0 unit 0 family inet address 192.168.1.2/24

You can also configure some loopback with these commands:

set interfaces lo0 unit 55 family inet address 222.0.0.1/32

commit

Configure static routing on Juniper routers:

For configuration of static routing you need next hope addresses:

Static routing on JunOs2 

On junos2 111.0.0.1/32 and 172.16.1.0/24 are directly connected networks whereas 192.168.1.1/24 and 222.0.0.1/32 are remote or destination networks and inaccessible from junos2 . You need to configure static routes for making these routes accessible on junos2. Nex-hop address is 172.16.1.2 for all these routes.          

Cli
configure

set routing-options static route 192.168.1.0/24 next-hop 172.16.1.2

set routing-options static route 222.0.0.0/32 next-hop 172.16.1.2

Static routing on JunOs3

111.0.0.1/32 and 222.0.0.1/32 are inaccessible networks on junos3 and need static routes. Nex-hop addresses are 172.16.1.1 for 111.0.0.1/32 and 192.168.1.2 for 222.0.0.1/32.

Cli

configure

set routing-options static route 222.0.0.0/32 next-hop 172.16.1.1

set routing-options static route 111.0.0.0/32 next-hop 192.168.1.2

Static routing on JunOs4

Nex-hop address for all routes on junos4 is 192.168.1.1.          

Cli

configure

set routing-options static route 172.16.1.0/24 next-hop 192.168.1.1

set routing-options static route 111.0.0.0/32 next-hop 192.168.1.1

Testing:

You can verify your configurations with following results:

Ping from junos2 to 222.0.0.1 should be successful.

Show route brief on JunOS 4 will have following output 

CCNA RIPv2 Exam SIM and basic password configuration on Cisco Router in GNS3

CCNA RIPv2 Exam SIM and basic password configuration on Cisco Router in GNS3:

This is most basic and simple lab for preparing ICND1 exam, which will test your skills related to different password configurations and RIPv2 on Cisco router.

You need to complete the configuration on newly installed router “Florida” in below network-diagram, RIPv2 is running on other router so you need to complete following configuration for making communication possible among Florida and newyork router:

1. Set the name of router to Florida
2. Set the enable-secret password of Florida to icnd1
3. Set the global configuration password to icndpass
4. Configure vty password (telnet) to ICND1VTY
5. Assign the first useable IP address to Ethernet interface Fa0/0 from subnet 192.168.1.0/27 
6. Assign the last IP address to serial interface S1/0 from subnet 200.1.1.128/28 
7. Advertise above two subnets via RIPv2 routing protocol on Florida.

Solution:

If you want to practice this lab in GNS3 then you can download router (newyork) configurations  from here and can complete the remaining lab according to following configurations.

1. Change Host name of Router to Florida:

R1#enable

R1#config t

R1(config)#hostname Florida

2. Set the enable-secret password of Florida to icnd1:

Florida(config)#enable secret icnd1

3. Set the global configuration password of router:

Florida(config)#line console 0

Florida(config-line)#password icndpass

Florida(config-line)#login

Florida(config-line)#exit

4. Configure vty password (telnet) of router:

Florida(config)#line vty 0 4

Florida(config-line)#password ICND1VTY

Florida(config-line)#login

Florida(config-line)#exit

5. Configure Ethernet interface f0/0 of Router:

For assigning the first useable IP address to Ethernet interface from subnet 192.168.1.0/27 you need to find subnet-mask and IP ranges (increment):

Subnetting for Class C address
Bit# in 4th octet	25	26	27	28	29	30	31	32
IP ranges/ increment	128	64	32	16	8	4	2	1

Since the first three bits are ‘1’ or "on" in 4th octet for given 192.168.1.0/27 and we know that the default subnet-mask for class-C is 255.255.255.0 you can find the subnet-mask for this subnet by adding first three bits i.e. 128+62+32=224 so

Subnetmask=255.255.255.224 

From above table you can find that IP range for /27 is 32 so we have following subnetwork for this subnet with a difference of 32:

Subnetwork1= 192.168.1.0 to 192.168.1.31

Subnetwork2= 192.168.1.32 to 192.168.1.63

.

.

.

.

Our give subnet belong to Subnetwork1= 192.168.1.0 to 192.168.1.31 so we have

Subnet ID = 192.168.1.0

Broadcast address=192.168.1.31

Useable IP range= 192.168.1.1 to 192.168.1.30

From above calculation we have the first useable IP address 192.168.1.1 and subnet-mask 255.255.255.224 so let assign this IP address to router interface:

Florida(config)#interface f0/0

Florida(config-if)#ip address 192.168.1.1 255.255.255.224

Florida(config-if)#no shu

6. Configure serial interface s0/0 of Router:

For finding the last IP address for 200.1.1.128/28 you can use the following table:

Subnetting for Class C address
Bit# in 4th octet	25	26	27	28	29	30	31	32
IP ranges/ increment	128	64	32	16	8	4	2	1

128+62+32+16=240

By adding the first 28 bit you can get the subnet-mask= 255.255.255.240

For find IP last IP address you need to have the all useable IP address for subnet200.1.1.128/28, with /28 you have the following sub-network with increment of 16.

Subnetwork1=200.1.1.0

Subnetwork2=200.1.1.16

Subnetwork3=200.1.1.32

Subnetwork4=200.1.1.48

Subnetwork5=200.1.1.64

Subnetwork6=200.1.1.80

Subnetwork7=200.1.1.96

Subnetwork8=200.1.1.112

Subnetwork9=200.1.1.128 to 200.1.1.143

Subnetwork10=200.1.1.144

From above calculation we find that our network belong to Subnetwork9=200.1.1.128 to 200.1.1.143 with following details:

Subnet ID= 200.1.1.128

Broadcasar Address= 200.1.1.143

Useable IP addresses= 200.1.1.129 to 200.1.1.142

So last IP address is 200.1.1.142 and subnet-mask is 255.255.255.240

So configuration for serial interface is as following:

Florida(config)#interface s1/0

Florida(config-if)#ip address 200.1.1.142 255.255.255.240

Florida(config-if)#no shut

7. Configure RIPv2 on router:

Florida(config)#router rip

Florida(config-router)#version 2

Florida(config-router)#network 192.168.1.0

Florida(config-router)#network 200.1.1.128

You can test your configuration by ping from florida-router to 10.1.1.10 which should be successful.

Test you ICND1 Skill by Taking ICND1 Quiz Questions and Answers