Achieve this with a single command.Īdd a summary route on R5 for all the directly connected networks on R1. Ensure reachability over the shortest possible path from R5 to all directly connected networks on R1. Tracing route to 10.1.3.2 over a maximum of 30 hops:ģ. (You can hit Ctrl-C on the keyboard to break out of the command.) Traceroute will show replies from R1 > R2 > R3 > R4 before failing. The summary route on R1 to 10.1.0.0/16 will provide a route to R5 over the path R1 > R2 > R3 > R4 > R5, but R5 does not have a route back to PC1.Ī ping from PC1 to 10.1.3.2 on R5 will fail. Does PC1 have reachability to the FastEthernet 0/0 interface on R5? If so, which path will the traffic take? Configure IP addresses on R5 according to the Lab Topology diagram.Minimum = 0ms, Maximum = 0ms, Average = 0ms Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Īpproximate round trip times in milli-seconds: Ensure that connectivity is restored between PC1 and PC3. L 10.0.2.1/32 is directly connected, FastEthernet1/0ĥ. L 10.0.1.1/32 is directly connected, FastEthernet0/1Ĭ 10.0.2.0/24 is directly connected, FastEthernet1/0 L 10.0.0.1/32 is directly connected, FastEthernet0/0Ĭ 10.0.1.0/24 is directly connected, FastEthernet0/1 + - replicated route, % - next hop overrideġ0.0.0.0/8 is variably subnetted, 7 subnets, 3 masksĬ 10.0.0.0/24 is directly connected, FastEthernet0/0 O - ODR, P - periodic downloaded static route, H - NHRP, l - LISP Ia - IS-IS inter area, * - candidate default, U - per-user static route I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 Verify the routing table on R1 does not contain /24 routes to remote subnets.Ĭodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area Restore connectivity to all subnets with a single command on R1.Ī summary route to 10.1.0.0/16 will add all remote subnets with one command. Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)ģ. Reply from 10.0.1.1: Destination host unreachable. Verify that PC1 loses connectivity to PC3 You can be a bit tighter with your summarization like in the example below. Maybe we don't want to have all of those subnets available behind R2, maybe some of them are within the 10.1.0.0 range but are available through a different path. It covers routes all the way from 10.1.0.0 to 10.1.255.255, which is a pretty big range. In our example, I summarised the routes using the classful boundary for a class B address. So that's how we configure summarization. This route will be good for all subnets that begin with 10.1, such as 10.1.0.0, 10.1.1.0, 10.1.2.0, and so on. Rather than having separate routes for 10.1.0.0, 10.1.1.0, and 10.1.2.0, which are all with a /24 subnet mask, I've configured one route for 10.1.0.0 with a subnet mask of 255.255.0.0. When our subnets are in contiguous ranges like this, it's usually possible to summarise them. We can have a summary route on R1 instead of the traditional way of having separate routes for the 10.1.0.0/24, 10.1.1.0/24, and the 10.1.2.0/24 networks, which are all pointing to the same next hop, 10.0.0.2. It isn't much of a difference but in large environments, it can make a big difference. In our example, we're going down from three routes to one route. It also lessens the memory usage on the routers. For static routing, summary routes lessen the administrative overhead.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |