![]() ![]() Verify your configuration by viewing the routing table on R2 and ensuring that R2 is learning the summary route and not four /24 subnets.Configure a RIP summary route to be advertised to R2 via Serial0/0.322 summarizing the 4 new networks into a single route.Disable auto-summarization on all routers in the network topology R1, R2 and R3.!# Free CCNA Workbook Lab 7-8 R3 Initial Config # !# Free CCNA Workbook Lab 7-8 R2 Initial Config #ĭescription # FRAME RELAY LINK TO R1 #ĭescription # FRAME RELAY LINK TO R3 # !# Free CCNA Workbook Lab 7-8 R1 Initial Config #ĭescription # PHYSICAL FRAME RELAY INTERFACE #ĭescription # FRAME RELAY LINK TO R2 # Establish a console session with devices R1, R2 and R3 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start devices R1, R2 and R3. ![]() ![]() This command is executed in interface configuration mode to advertise a summary address out that particular interface. In this lab you will disable auto-summarization on all routers and configure R3 with 4 new loopback interfaces with the IP addresses of 10.30.0.0/24, 10.30.1.0/24, 10.30.2.0/24 and 10.30.3.0/24 and create a summary route that is sent to R2 via the point-to-point frame-relay link between R3 and R2.įamiliarize yourself with the following new command(s) Command This lab will continue to build upon the same logical topology used previously in Lab 7-7 as shown below So then you would need to send that summary address out the interface using the command ip summary-address rip 10.30.0.0 255.255.252.0 How would you accomplish this?įirst off you would need to subnet the 4 address ranges, in this case 10.30.0.0/22 would cover all 4 networks that are directly connected. So lets say you have 4 directly connected interfaces on R3 as 10.30.0.0/24, 10.30.1.0/24, 10.30.2.0/24 and 10.30.3.0/24 and you want to advertise these 4 routes as a single route to R2 to save memory and CPU cycles. On a Cisco router you have the ability to summarize particular subnets into a single larger subnet which can be used to save router resources upstream on the network such as memory and CPU cycles. On the other hand summarization is a good thing! Just not auto-summarization. ![]() In nearly every router you will see in production as a network engineer you will see “no auto-summary” under the routing process in the running-configuration to prevent such classful auto summarization. In today’s networks this would be unacceptable as few organizations own a full class A subnet. If you lab this scenario and ping an address directly connected to R1 from R2 then you’ll see the pings from R2 are intermittent and have a 50% successful delivery. However the downfall of this scenario is that if 10.70.10.0/24 is directly connected to R1 and 10.70.30.0/24 is directly connected to R3 any traffic sourced from a network directly connected to R2 destined to the 10.70.10.0/24 network will be load balanced between R1 and R2 thus causing half of the traffic to fail. R1 and R2 both have networks directly attached that fall into the 10.0.0.0/8 classful subnet so both R1 and R3 will advertise they have a route to the 10.0.0.0/8 network and in this case R2 will install two routes into the routing table and load balance between R1 and R2 to reach the 10.0.0.0/8 classful network. R1 is connected to R2 via a serial link using the 172.16.12.0/24 network and R2 is connected to R3 via a serial link using the 172.16.23.0/24 network. Auto summarization will summarize routes on a router to their classful networks between major networks, i.e class a, b, c etc… So with that being said lets say for example you have three routers connected together in a linear bus R1, R2 and R3. First lets take a look at auto-summarization. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |