Skip to main content

Route Summerization

 Manual Summarization with Any Routing Protocol

Manual summarization allows administrators to consolidate routes by summarizing smaller networks into a single summary route, helping to reduce the size of the routing table and speed up convergence. Each routing protocol has its own method of summarization.

EIGRP Summarization

EIGRP automatically performs summarization at classful network boundaries, but it can also perform manual summarization at any interface. EIGRP’s classless behavior allows the advertisement of both a prefix and a mask with each route, and summarization is critical for scalability in larger networks.

  • Technical Tip: Disabling automatic summarization is often preferred as it provides more control over route advertisements, especially in discontiguous networks. Summarization should be done both upstream and downstream for optimized traffic flow.
  • Summarization is configured in interface configuration mode, making it specific to certain neighbors. When summarization is applied, EIGRP generates a discard route (route to null0) to prevent routing loops.

Example:

R2(config)# interface serial1/3

R2(config-if)# ip summary-address eigrp 100 2.2.4.0 255.255.252.0

  • Technical Tip: Summarization triggers EIGRP to bring down and bring back up all neighbors on that interface, forcing them to relearn the network topology.

To create a summary that covers all Class A, B, and C networks:

R1(config)# interface serial1/2

R1(config-if)# ip summary-address eigrp 100 0.0.0.0 0.0.0.0

  • Administrative Distance (AD): When a summary is created, the route to null0 is assigned an AD of 5, helping in loop prevention.

OSPF Summarization

OSPF summarization occurs only on ABRs (Area Border Routers) or ASBRs (Autonomous System Boundary Routers). Summarization is essential to reduce the complexity of routing tables and improve the speed of Shortest Path First (SPF) calculations.

  • Technical Tip: Summarization works only for Type 1 LSAs and helps by limiting the scope of LSAs in the network. A well-summarized OSPF network will improve the efficiency of SPF calculations.

OSPF can summarize routes between areas using the area area-id range command on an ABR, or summarize external routes on an ASBR using summary-address.

Example for ABR summarization:

router ospf 1

area 12 range 172.16.0.0 255.255.0.0 cost 45

  • Technical Tip: When inter-area summarization occurs, the ABR creates a discard route (route to null0) to avoid routing loops if no specific route exists for the summary.
  • Discard Route Metrics: The AD for an OSPF discard route is 110 for internal networks and 254 for external networks. This prevents unwanted traffic looping in areas where summarized routes might not be fully covered.

Default Route Advertisement: OSPF can also advertise a default route into the domain using the default-information originate command. The always keyword ensures the advertisement of a default route even if one does not exist in the local routing table.

Example:

router ospf 1

default-information originate always metric 5 metric-type 1

  • Technical Tip: OSPF assigns a default metric of 1 for default route advertisements, and the metric-type option allows customization of the metric for external routes.

Summary of Technical Tips:

  • EIGRP Summarization: Manual summarization is essential for scaling, but be mindful of how EIGRP handles neighbors during this process. Discard routes are crucial for loop prevention.
  • OSPF Summarization: Only occurs at ABRs or ASBRs, and discard routes are also essential to avoid routing loops. Efficient summarization improves SPF performance significantly.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...
Post a Comment
Read more