Optimizing Routing Updates

INFO-5081

Agenda

1. Redistribution 2. Administrative Distances 3. Controlling Routing Updates

Redistribution

Multiple Routing Protocols

Redistribution Steps
! ! ! ! Identify whats going to happen Identify where its going to happen Identify the Core / Edge protocols Identify the routes to redistribute
! One way (Edge into Core) ! Two way ! Summarization

! Seed Metrics ! Filtering

Redistribution

! One Way ! Two Way

(Recommended )

Metrics

Default Seed Metrics

Into This Protocol

RIP EIGRP OSPF

Default Seed Metrics

Infinity Infinity Type 2, 20 for all except BGP, which is 1

Metrics
Into: EIGRP
Bandwidth (Kbps) Delay (ms) Load (0-255) MTU Size

! redistribute ospf 1 metric 10000 100 255 1 1500

Reliability (1-255)

Into: RIP
! redistribute eigrp 24 metric 2
Hop Count E1 or E2 Type Routes E2: Cost will never change

Into: OSPF
Cost (1-65000)

! redistribute eigrp 1 metric 30 metric-type 1 subnets

Include Subnets

Redistributing Into RIP

! Default Metric going into RIP is infinity

Redistribution Into OSPF

! Default metric is 20. ! Default metric type is 2. (E2) ! Sub-neted networks do not redistribute by default.
! Use the keyword subnets

Redistributing Into OSPF

Redistributing Into EIGRP

!! !! !! !! !!

Bandwidth in kilobytes = 10000 Delay in tens of microseconds = 100 Reliability = 255 (maximum) Load = 1 (minimum) MTU = 1,500 bytes

Redistribution Example

Before Redistribution:

Before Redistrib: Routing Tables

Redistribution at Router B

After Route Redistribution

With Summarization

Redistributing Static Routes

RIP

Administrative Distance

Administrative Distance
! If there is more than one route to a destination then:
1) Choose the one with the lowest Administrative distance 2) If the Admin Distance is the same choose the one with the least cost

! A routing protocols administrative distance rates its trustworthiness as a source of routing information.
! Integer value from 0 to 255. ! The lowest administrative distance has the highest trust rating.

! Default values normally work, however you might have to skew the values.

Default Administrative Distances

Route Source Directly Connected Interface Static Route EIGRP Summary Route External BGP EIGRP OSPF RIP EIGRP External Route Internal BGP

Default Distance 0 1 5 20 90 110 120 170 200

Admin Distance Example

! Router A learns about 10.0.0.0 from B (RIP) and C (OSPF) ! Which route will A enter into the routing table?

Specifying Admin Distance

RIP
router rip R1(config-router)# distance 100
R1(config)#

EIGRP
router eigrp 109 R1(router-config)# distance eigrp 80 130
R1(config)#

Internal External

Specifying Admin Distance

OSPF
! Default AD is 110 or all types
router ospf 1 R3(config-router)# distance ospf intra-area 105 inter-area 115 external 175
R3(config)#

Specifying Admin Distance

OSPF
router ospf 1 R1(config-router)# distance 85 192.168.100.0 0.0.0.255
R1(config)# Modify AD For routes being advertised from routers with RIDs in the range of: 192.168.100.1 - .254

Controlling Routing Updates

Controlling Routing Updates

! Passive Interfaces ! Route Filters
! Distribute Lists ! Prefix Lists

! Route Maps

Passive Interfaces

Configuring Passive Interfaces

RIP: Interfaces receive - but dont send updates EIGRP/OSPF: No hellos, therefore no neighbours

Passive-Interface Default

Route Filters Distribute List

Distribute List
Step 1
! Create an ACL to identify the routes that you want to filter.

Step 2
! Assign the ACL to filter outgoing / incoming routing updates

Inbound Route Filters

Applies to all interfaces

Outbound Route Filters

Applies to all interfaces

** Note: This does not permit/deny packets from entering the routers, only what routes a router will send or receive updates about.

Outbound Route Filters

RTA(config)# router rip RTA(config-router)# network 10.0.0.0 RTA(config-router)# distribute-list 16 out S2 RTA(config)# access-list 16 deny 10.1.1.0 0.0.0.255 RTA(config)# access-list 16 permit any

Applies only to S2

Route Filters Prefix List

Prefix List
! Used for more granular identification mechanism than an ACL ! Checks the:
! route prefix length and ! subnet mask for a match condition

! Match condition:
! equal ! le ! ge

Prefix List
! Can have multiple lines ! Permit or Deny ! Evaluation of the list is sequential:
! Top down and ends as soon as a match is found ! Implicit Deny All

! Used in Distribute lists or Route Maps

Example 1
ip prefix-list TEST seq 10 permit 10.0.0.0/8

Sequence 10: does not have a ge or le value, so only an exact match will be permitted. (network and mask: 8bits) ! ie: exactly 10.0.0.0/8

Example: 2
ip prefix-list TEST seq 20 deny 10.0.0.0/8 ge 24

Sequence 20: specifies that the first 8 bits must match, and the mask must be 24 bits or more. ! Ie: 10.2.2.0/24, 10.254.255.0/25, 10.0.0.1/32, etc

Example: 3

ip prefix-list TEST seq 30 permit 10.0.0.0/8

ge 12

le 16

Sequence 30: specifies that the first 8 bits must match, and the mask must be between 12 and 16 bits. ! ie: 10.0.0.0/12, 10.16.0.0/14, 10.99.0.0/16, etc

Example: 4

ip prefix-list TEST seq 40 deny

10.128.0.0/8

le 24

Sequence 40: specifies that the first 8 bits must match, and the mask must be less than or equal to 24. ! ie: 10.128.0.0/9, 10.255.0.0/16, 10.199.99.0/24, etc

Example: 5

ip prefix-list TEST seq 50 permit 10.255.0.0/16

le 32

Sequence 50: specifies that the first 16 bits must match, and the mask must be less than or equal to 32. ! ie: 10.255.0.0/16, 10.255.45.0/24, 10.255.60.0/30, 10.255.1.1/32, etc

Whats it doing?
ip prefix-list RIP-OUT seq 10 deny 192.168.48.0/22 le 24 ip prefix-list RIP-OUT seq 20 permit 0.0.0.0/0 le 32

R1(config)# R1(config)#

router rip R1(config-router)# distribute-list prefix RIP-OUT out Fa0/0

R1(config)#

Route Maps

Route Maps
! They work like a more sophisticated access list:
! Top-down processing ! Once there is a match, leave the route map

! Lines are sequence-numbered for easier editing:

! Insertion of lines ! Deletion of lines

! Route maps are named rather than numbered for easier documentation. ! Match criteria and set criteria can be used

Route Maps
! Each route-map command has a list of match and set commands associated with it
! Similar to: IF / THEN statements

! The match commands specify the conditions that should be tested to determine whether or not to take action. ! The set commands specify the actions to perform if the match criteria are met.

Permit / Deny
! Each line has a permit or deny statement
! Permit
! the router sets the metrics or other defined conditions and permits the redistribution of that route. ! The route map stops processing at the first match.

! Deny
! the router stops at the matched line in the map and does not redistribute that route. ! Routes are filtered by this method.

! There is always an implicit deny at the end of a route map

Route Map Operation

! ! ! ! A list of statements composes a route map. The list is processed top-down like an access list. The first match found for a route is applied. The sequence number is used for inserting or deleting specific route map statements.
route-map my_map permit 10 { match statements } { match statements } { set statements } { set statements } route-map my_map deny 20 :: :: :: :: :: :: route-map my_map permit 30 :: :: :: :: :: ::

Route Map Operation (Cont.)

!! The match statement may contain multiple references. !! Multiple match criteria in the same line use a logical OR. !! At least one reference must permit the route for it to be a candidate for redistribution.

!! Each vertical match uses a logical AND. !! All match statements must permit the route for it to remain a candidate for redistribution. !! Route map permit or deny determines if the candidate will be redistributed.

match commands
Command
match community match interface match ip address match ip next-hop match ip routesource match length match metric match route-type match tag

Description
Matches a BGP community Matches any routes that have the next hop out of one of the interfaces specified Matches any routes that have a destination network number address that is permitted by a standard or extended ACL Matches any routes that have a next-hop router address that is passed by one of the ACLs specified Matches routes that have been advertised by routers and access servers at the address that is specified by the ACLs Matches based on the layer 3 length of a packet Matches routes with the metric specified Matches routes of the specified type Matches tag of a route

set commands
Command
set as-path set automatic-tag set community set default interface set interface set ip default nexthop set ip next-hop set level set local-preference set metric set metric-type set tag set weight

Description
Modifies an AS path for BGP routes Computes automatically the tag value Sets the BGP communities attribute Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination Indicates where to output packets that pass a match clause of a route map for policy routing Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination Indicates where to output packets that pass a match clause of a route map for policy routing Indicates where to import routes for IS-IS and OSPF Specifies a BGP local preference value Sets the metric value for a routing protocol Sets the metric type for the destination routing protocol Sets tag value for destination routing protocol Specifies the BGP weight value

Route Map: Example

Router(config)# router ospf 10 Router(config-router)# redistribute rip route-map redis-rip

!! 10: Routes matching either access list 23 or 29 are redistributed with an OSPF cost of 500, external type 1. !! 20: Routes permitted by access list 37 are not redistributed. !! 30: All other routes are redistributed with an OSPF cost metric of 5000, external type 2.
Router(config)# Router(config)#

route-map redis-rip permit 10 match ip address 23 29 set metric 500 set metric-type type-1 route-map redis-rip deny 20 match ip address 37 route-map redis-rip permit 30 set metric 5000 set metric-type type-2

access-list 23 permit 10.1.0.0 0.0.255.255 access-list 29 permit 172.16.1.0 0.0.0.255 access-list 37 permit 10.0.0.0 0.255.255.255

Tagging Routes: Example

! ! ! Tag routes as they get redistributed Prevent them from being redistributed back EIGRP - OSPF

route-map OSPF_EIGRP deny 10 match tag 2 route-map OSPF_EIGRP permit 20 set tag 1 route-map EIGRP_OSPF deny 10 match tag 1 route-map EIGRP_OSPF permit 20 set tag 2 router eigrp 123 Router(config-router)# redistribute ospf 234 route-map OSPF_EIGRP metric 1 1 1 1 1500
Router(config)#

router ospf 234 Router(config-router)# redistribute eigrp 123 route-map EIGRP_OSPF subnets
Router(config-router)#

To Do
! Study for:
! Test 1: ! Thursday, 06-Mar-2014, G2010, 15:00 16:30 (3:00 - 4:30) ! Practical Test 1: ! Tuesday, 04-Mar-2014 ! Using GNS3

! Labs:
! ! ! ! 4-1: Redistribution Between RIP and OSPF 4.2: Redistribution EIGRP OSPF 4-3: Manipulating Administrative Distances 4.4: EIGRP OSPF Case Study
! Marked: submit GNS3 files to FOL ! Project File: Your Lastname ! Due: Friday, 21-Feb-2014 at 18:00 (6:00pm)